WO2020192777A1 - 通信方法及设备 - Google Patents

通信方法及设备 Download PDF

Info

Publication number
WO2020192777A1
WO2020192777A1 PCT/CN2020/081882 CN2020081882W WO2020192777A1 WO 2020192777 A1 WO2020192777 A1 WO 2020192777A1 CN 2020081882 W CN2020081882 W CN 2020081882W WO 2020192777 A1 WO2020192777 A1 WO 2020192777A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
communication
communication type
configuration information
information
Prior art date
Application number
PCT/CN2020/081882
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 EP20777503.2A priority Critical patent/EP3937577A4/en
Publication of WO2020192777A1 publication Critical patent/WO2020192777A1/zh
Priority to US17/487,729 priority patent/US20220022168A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/02—Selection of wireless resources by user or terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058—Allocation criteria
    • H04L5/0064—Rate requirement of the data, e.g. scalable bandwidth, data priority
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/44—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/46—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for vehicle-to-vehicle communication [V2V]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/52—Allocation or scheduling criteria for wireless resources based on load
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup

Definitions

  • This application relates to the field of wireless communication, and in particular to communication methods and devices.
  • V2X vehicle to everything
  • V2X in the long term evolution (LTE) system only supports broadcast communication
  • V2X in the new radio (NR) system, V2X not only supports broadcast communication, but also supports unicast communication and multicast communication.
  • LTE long term evolution
  • NR new radio
  • V2X communication method that enables the receiving device to receive data of the corresponding communication type, so as to reduce the packet error rate of the receiving device, and thereby improve the packet receiving efficiency of the receiving device.
  • the embodiments of the present application provide a communication method and device, which can enable a receiving device to receive data of a corresponding communication type, so as to reduce the packet error reception rate of the receiving device, thereby improving the packet receiving efficiency of the receiving device.
  • an embodiment of the present application provides a communication method.
  • the method includes: a first terminal device sends side link control information SCI and service data to a second terminal device; wherein the SCI includes a second target side identifier and The type of communication, or include the type of communication.
  • the second terminal device can receive the service data of the corresponding communication type, so as to reduce the packet error reception rate of the second terminal device, thereby improving the packet receiving efficiency of the second terminal device.
  • the first terminal device determines the service data according to the second target side identifier and the communication type, and the second target side identifier is used to identify the service data. Based on this solution, the first terminal device can determine the service data to be sent according to the second target side identifier and the communication type, and send the SCI corresponding to the service data to the second terminal device, so that the second terminal device can receive the corresponding communication type
  • the service data is used to reduce the rate of incorrect packet reception of the second terminal device, thereby improving the packet receiving efficiency of the second terminal device.
  • the first terminal device receives the first configuration information sent by the network device; or, the first terminal device stores the first configuration information, where the first configuration information includes the second target side identifier And the communication type, and second configuration information corresponding to the second target side identifier and the communication type, wherein the second target side identifier is used to identify the service data, and the second configuration information includes a side line Link configuration information and/or scheduling resources, the side link configuration information is used to indicate synchronization configuration, transmission mode, or the location of transmission resources, and the scheduling resources include identification with the second target side and/or the The transmission resource corresponding to the communication type; or, the first configuration information includes the communication type and the second configuration information corresponding to the communication type, wherein the second target side identifier is used to identify the service data, so
  • the second configuration information includes side link configuration information and/or scheduling resources, the side link configuration information is used to indicate synchronization configuration, transmission mode, or location of transmission resources, and the scheduling resources include side link configuration information and/or scheduling resources.
  • the first configuration information includes the communication type, second configuration information corresponding to the communication type, quality of service information, and configuration information of the side link radio bearer corresponding to the quality of service information , Wherein the second target side identifier is used to identify the service data, the second configuration information includes side link configuration information and/or scheduling resources, and the side link configuration information is used to indicate synchronization
  • the first terminal device can obtain the synchronization configuration, the transmission mode, or the location of the transmission resource according to the second configuration information, and the first terminal device can also configure the side line according to the configuration information of the side link radio bearer sent by the network device.
  • Link radio bearer
  • the first configuration information is system information block, radio resource control signaling, medium access control signaling, downlink control information, non-access stratum signaling, or interface message.
  • the first terminal device can send the first configuration information through system information block, radio resource control signaling, medium access control signaling, downlink control information, non-access stratum signaling, or V3 interface message.
  • the first terminal device sends service information to the network device; where the service information includes: the communication type. Based on this solution, the first terminal device can obtain the transmission resource for sending the service data by sending the service information to the network device.
  • the first terminal device sends a buffer status report to the network device; wherein, the buffer status report includes the second target side identifier and the communication type, or the communication type, the second target side The identifier is used to identify the business data. Based on this solution, the first terminal device can obtain the transmission resource for sending the service data by sending the BSR to the network device.
  • the first terminal device sends auxiliary information to the network device; where the auxiliary information includes service model information and the communication type. Based on this solution, the first terminal device can obtain the transmission resource for sending the service data by sending the auxiliary information to the network device.
  • the first terminal device sends the service quality information to the network device; wherein the service quality information includes the second target side identifier and the communication type, or includes the communication type. Based on this solution, the first terminal device can obtain configuration information of the side link radio bearer by sending service quality information to the network device.
  • the first terminal device receives the configuration information of the side link radio bearer sent by the network device; wherein, the configuration information of the side link radio bearer includes the identification of the second target side And/or the side link radio bearer configuration corresponding to the communication type; the side link radio bearer configuration includes the mapping relationship between the quality of service flow to the side link data radio bearer SL-DRB, and the PDCP configuration of the packet data convergence protocol, At least one of radio link control RLC configuration and logical channel LCH configuration. Based on this solution, the first terminal device can configure the side link radio bearer according to the configuration information of the side link radio bearer sent by the network device.
  • the first terminal device sends the configuration information of the side link radio bearer to the second terminal device.
  • the second terminal device can obtain the side-link radio bearer configuration according to the configuration information of the side-link radio bearer sent by the first terminal device, and determine the received service according to the side-link radio bearer configuration. Data is processed.
  • the first terminal device if the first terminal device does not establish a first connection corresponding to the second target side identifier and/or the communication type with the second terminal device, the first terminal device establishes the first connection ; Wherein, the first connection is an access layer AS connection and/or a side link radio bearer connection.
  • the second terminal device can receive service data of the corresponding communication type, so as to reduce the packet error reception rate of the second terminal device, thereby improving the first terminal device. 2. Packet receiving efficiency of terminal equipment.
  • an embodiment of the present application provides a communication method.
  • the method includes: a second terminal device receives side link control information and service data from a first terminal device; wherein the side link control information includes the first Target side identification and communication type, or including communication type.
  • the second terminal device can receive the service data of the corresponding communication type, so as to reduce the packet error reception rate of the second terminal device, thereby improving the packet receiving efficiency of the second terminal device.
  • the second terminal device determines to receive the service data according to the communication type included in the sidelink control information and the ability of the second terminal device to support the communication type; or The second terminal device determines to receive the service data according to the first target side identifier and the communication type included in the side link control information, and the first target side identifier and the capacity of the communication type supported by the second terminal device .
  • the second terminal device can be based on the communication type included in the side link control information and the capability of the communication type supported by the second terminal device, or the second terminal device can be based on the side link control information.
  • the second terminal device receives the first configuration information from the network device; wherein, the first configuration information includes the second target side identifier and the communication type, and the second target side identifier
  • the information is used to indicate the synchronization configuration, the transmission mode, or the location of the transmission resource, the scheduling resource includes the transmission resource corresponding to the second target side identifier and/or the communication type; or, the first configuration information includes the communication type, And second configuration information corresponding to the communication type, where the second target side identifier is used to identify the service data, the second configuration information includes side link configuration information and/or scheduling resources, and the side link
  • the configuration information is used to indicate the synchronization configuration, the transmission mode, or the location of the transmission resource, the scheduling resource includes the transmission resource corresponding to the second target side identifier and/or the communication type; or, the
  • the second terminal device can obtain the synchronization configuration, the transmission mode, or the location of the transmission resource according to the second configuration information sent by the network device, and the second terminal device can also obtain the configuration of the side link radio bearer sent by the network device.
  • Information acquisition side link radio bearer configuration can be obtained.
  • the first configuration information is system information block, radio resource control signaling, medium access control signaling, downlink control information, non-access stratum signaling, or V3 interface message.
  • the second terminal device can obtain the first configuration information through system information blocks, radio resource control signaling, medium access control signaling, downlink control information, non-access stratum signaling, or V3 interface messages.
  • the second terminal device receives the configuration information of the side link radio bearer from the first terminal device; wherein, the configuration information of the side link radio bearer includes the identification of the second target side And/or the side link radio bearer configuration corresponding to the communication type; the side link radio bearer configuration includes the mapping relationship between the quality of service flow to the side link data radio bearer, the packet data convergence protocol configuration, and the radio link control At least one of configuration and logical channel configuration.
  • the second terminal device can obtain the side link radio bearer configuration according to the configuration information of the side link radio bearer sent by the first terminal device, and pair the received service data according to the side link radio bearer configuration. To process.
  • the second terminal device if the second terminal device does not establish a first connection corresponding to the second target side identifier and/or the communication type with the first terminal device, the second terminal device establishes the first connection
  • the second target side identifier is used to identify the service data
  • the first connection is an access layer AS connection and/or a side link radio bearer side link radio bearer connection.
  • the second terminal device can receive the service data of the corresponding communication type after establishing the first connection with the first terminal device, so as to reduce the packet error reception rate of the second terminal device, thereby improving the packet reception of the second terminal device effectiveness.
  • the present application provides a communication method.
  • the method includes: a network device sends first configuration information to a first terminal device and/or a second terminal device, where the first configuration information includes the second target side Identification and the communication type, and second configuration information corresponding to the second target-side identification and the communication type, wherein the second target-side identification is used to identify service data, and the second configuration information includes a sideline link Path configuration information and/or scheduling resources, the side link configuration information is used to indicate synchronization configuration, transmission mode, or the location of transmission resources, and the scheduling resources include transmissions corresponding to the second target side identifier and/or communication type Resource; or, the first configuration information includes the communication type and the second configuration information corresponding to the communication type, wherein the second target side identifier is used to identify service data, and the second configuration information includes side Uplink configuration information and/or scheduling resources, the side uplink configuration information is used to indicate synchronization configuration, transmission mode, or location of transmission resources, and the scheduling resources include corresponding to the second target side identifier and
  • the first configuration information includes service quality information and configuration information of the side link radio bearer corresponding to the service quality information.
  • the first terminal device and/or the second terminal device can obtain the synchronization configuration, the transmission mode, or the location of the transmission resource according to the second configuration information sent by the network device, and the first terminal device and/or the second terminal device also
  • the configuration of the side-link radio bearer may be obtained according to the configuration information of the side-link radio bearer sent by the network device.
  • the first configuration information is system information block, radio resource control signaling, medium access control signaling, downlink control information, non-access stratum signaling, or V3 interface message.
  • the network device can communicate to the first terminal device and/or the second terminal device through system information block, radio resource control signaling, medium access control signaling, downlink control information, non-access stratum signaling, or V3 interface messages. Send the first configuration information.
  • the network device receives service information from the first terminal device; where the service information includes: the communication type. Based on this solution, the network device can allocate transmission resources for the first terminal device according to the service information sent by the first terminal device.
  • the network device receives a buffer status report from the first terminal device; wherein the buffer status report includes the second target side identifier and the communication type, or the communication type. Based on this solution, the network device can allocate transmission resources for the first terminal device according to the BSR sent by the first terminal device.
  • the network device receives the auxiliary information sent by the first terminal device; wherein the auxiliary information includes the service model and the communication type. Based on this solution, the network device can allocate transmission resources for the first terminal device according to the auxiliary information sent by the first terminal device.
  • the network device receives service quality information from the first terminal device; wherein the service quality information includes the second target side identifier and the communication type, or includes the communication type. Based on this solution, the network device can obtain the communication type of the service data according to the service quality information sent by the first terminal device.
  • the network device sends configuration information of the side link radio bearer to the first terminal device according to the service quality information; wherein, the configuration information of the side link radio bearer includes the configuration information of the side link radio bearer.
  • the network device can send the sidelink radio bearer configuration information to the first terminal device according to the quality of service information sent by the first terminal device.
  • an embodiment of the present application provides a first terminal device that has the method and function described in the first aspect.
  • This function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • an embodiment of the present application provides a second terminal device that has the method and function described in the second aspect.
  • This function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the embodiments of the present application provide a network device that has the method and function described in the third aspect.
  • This function can be realized by hardware, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the present application provides a communication device, which may include: at least one processor, and related program instructions are executed in the at least one processor to implement the method according to the first aspect and any design thereof
  • the first terminal device in the function may further include at least one memory, and the memory stores related program instructions.
  • the communication device may be the method of the first aspect and the first terminal device in any design thereof.
  • the present application provides a communication device, the communication device may include: at least one processor, and related program instructions are executed in the at least one processor to implement the method according to the second aspect and any design thereof The function of the second terminal device in.
  • the communication device may further include at least one memory, and the memory stores related program instructions.
  • the communication device may be the method of the second aspect and the second terminal device in any design thereof.
  • the present application provides a communication device, which may include: at least one processor, and related program instructions are executed in the at least one processor to implement the method according to the third aspect and any design thereof The function of the network device in the.
  • the communication device may further include at least one memory, and the memory stores related program instructions.
  • the communication device may be the method of the third aspect and the network equipment in any design thereof.
  • the present application provides a system chip that can be used in a communication device.
  • the system chip includes: at least one processor, and related program instructions are executed in the at least one processor to implement The method of one aspect and the function of the first terminal device in any design thereof; or, the method according to the second aspect and the function of the second terminal device in any design thereof; or, the method according to the third aspect And the functions of network devices in any design.
  • the system chip may further include at least one memory, and the memory stores related program instructions.
  • this application provides a computer storage medium that can be used in a communication device.
  • the computer-readable storage medium stores program instructions. When the program instructions are run, The method of the aspect and the function of the first terminal device in any design thereof; or, the method according to the second aspect and the function of the second terminal device in any design thereof; or the method according to the third aspect and The function of a network device in any of its designs.
  • this application provides a computer program product that contains program instructions.
  • the program instructions involved are executed, the method according to the first aspect and any design of the first terminal device Function; or, implement the method according to the second aspect and the function of the second terminal device in any design; or, implement the method according to the third aspect and the function of the network device in any design.
  • this application provides a communication system, which may include any one or more of the following: such as the first terminal device in the fourth aspect, or the second terminal device in the fifth aspect, Or as the network device in the sixth aspect, or as the communication device in the seventh, eighth or ninth aspect, or as the system chip in the tenth aspect, or as the computer storage medium in the eleventh aspect, Or as the computer program product in the twelfth aspect.
  • Figure 1 is a functional block diagram provided by an embodiment of the application.
  • Figure 2 is a schematic diagram of a system architecture provided by an embodiment of the application.
  • FIG. 3a is a schematic diagram of unicast communication provided by an embodiment of this application.
  • Figure 3b is a schematic diagram of multicast communication provided by an embodiment of the application.
  • FIG. 3c is a schematic diagram of broadcast communication provided by an embodiment of this application.
  • Figure 4 is a schematic diagram of a protocol stack provided by an embodiment of the application.
  • FIG. 5 is a schematic diagram of the composition of a communication device provided by an embodiment of this application.
  • FIG. 6 is a first schematic flowchart of a communication method provided by an embodiment of this application.
  • FIG. 7 is a second schematic diagram of the flow of a communication method provided by an embodiment of this application.
  • FIG. 8 is a third schematic flowchart of a communication method provided by an embodiment of this application.
  • FIG. 9 is a fourth flowchart of a communication method provided by an embodiment of this application.
  • FIG. 10 is a fifth schematic flowchart of a communication method provided by an embodiment of this application.
  • FIG. 11 is a sixth flowchart of a communication method provided by an embodiment of this application.
  • FIG. 12 is a seventh schematic flowchart of a communication method provided by an embodiment of this application.
  • FIG. 13 is an eighth flowchart of a communication method provided by an embodiment of this application.
  • FIG. 14 is a ninth flowchart of a communication method provided by an embodiment of this application.
  • FIG. 15 is a first structural diagram of a first terminal device according to an embodiment of the application.
  • FIG. 16 is a second structural diagram of a first terminal device provided by an embodiment of this application.
  • FIG. 17 is a third structural diagram of a first terminal device provided by an embodiment of this application.
  • FIG. 18 is a fourth structural diagram of a first terminal device provided by an embodiment of this application.
  • FIG. 19 is a fifth structural diagram of a first terminal device provided by an embodiment of this application.
  • FIG. 20 is a first structural diagram of a second terminal device according to an embodiment of this application.
  • FIG. 21 is a second structural diagram of a second terminal device according to an embodiment of this application.
  • FIG. 22 is a third structural diagram of a second terminal device according to an embodiment of this application.
  • FIG. 23 is a first structural diagram of a network device provided by an embodiment of this application.
  • FIG. 24 is a second structural diagram of a network device provided by an embodiment of this application.
  • the process of transmitting data between the originating device and the receiving device can include: when the application layer entity of the originating device generates a data packet corresponding to a certain type of V2X service and delivers it to the lower entity, the data packet may carry To identify the second target side identifier of this type of V2X service (such as destination layer-2 id) and/or communication type and other information, the lower-layer entity of the originating device can be based on the second target side identifier and/or The mapping relationship between the communication type and other information and the sidelink radio barrier (SLRB) groups (SLRBs for short), and the data packet is delivered to the sending device corresponding to the second target side identification and/or communication type and other information SLRB;
  • the SLRB in the sending device processes the received data packet and submits the processed data to the media access control (MAC) layer entity of the sending device; the MAC layer entity pair of the sending device passes through the SLRB
  • the processed data packet may carry
  • the sending end device can send the sidelink control information (SCI) corresponding to the MAC PDU to the receiving end device, and the SCI can include the corresponding MAC PDU
  • the first destination side identifier for example: destination layer-1 id
  • communication type for example: communication type
  • the receiving device can determine whether to receive the MAC PDU according to the first target side identifier included in the SCI and/or the communication type; or, the PHY layer entity of the receiving device is receiving After the MAC PDU, it is possible to determine whether to deliver the MAC service data unit (SDU) contained in the MAC PDU to the receiving device according to the second target side identifier and/or the communication type carried in the MAC PDU.
  • SDU MAC service data unit
  • the receiving device may determine whether to receive the MAC PDU according to the first target side identifier and/or communication type included in the SCI, including: if the first target side identifier and/or the SCI includes The communication type is the first target side identifier and/or communication type supported by the receiving device itself, and the receiving device receives the MAC PDU; if the first target side identifier and/or communication type included in the SCI is not supported by the receiving device itself The first target side identifier and/or communication type, the receiving device does not receive the MAC PDU.
  • the PHY layer entity of the receiving device can determine whether to include the MAC PDU according to the second target side identifier carried in the MAC PDU and/or the communication type.
  • the MAC SDU is submitted to the SLRB corresponding to this type of V2X service in the receiving device for processing, including: the PHY layer entity of the receiving device can submit the MAC PDU to the MAC entity after receiving the MAC PDU, if the MAC The second target side identifier and/or communication type carried in the PDU is the second target side identifier and/or communication type supported by the receiving device MAC entity, and the receiving device submits the MAC SDU contained in the MAC PDU to the receiving device
  • the SLRB corresponding to this type of V2X service is processed; if the second target side identifier and/or communication type carried in the MAC PDU is not the second target side identifier and/or communication type supported by the receiving end device MAC entity, the receiving end The device discards the MAC
  • the first target side identifier and/or communication type, the second target side identifier and/or communication type may also be one or more of the following information: public land mobile Network (public land mobile network, PLMN) identification information, side link/Uu interface communication information, side link/Uu interface information, carrier/frequency identification information, network equipment/cell/core network element identification information, Service identification information, terminal equipment identification information, quality of service (QoS) identification information, connection identification information in unicast connections, group identification information in multicast connections, service identification in unicast ⁇ multicast ⁇ broadcast Information, communication mode identification information, part of the bandwidth (band with part, BWP) identification information, logical channel group (logical channel group, LCG) identification information, LCH identification information, SLRB identification information, communication source identification information, communication target identification information, Hybrid automatic repeat request (HARQ) process identification information.
  • PLMN public land mobile Network
  • side link/Uu interface communication information side link/Uu interface information
  • carrier/frequency identification information network equipment/cell/core network element identification information
  • the PLMN identification information is used to identify the PLMN;
  • the side link/Uu communication system information is used to identify the communication system where the side link/Uu link is located (for example: LTE system, NR system or next-generation communication system) ;
  • Side link/Uu interface information is used to identify side link/Uu interface;
  • Carrier/frequency identification information is used to identify carrier/frequency;
  • Network equipment/cell/core network element identification information is used to identify network equipment /Cell/core network element; service identification information (for example: service id) is used to identify service information, so that network equipment can configure parameters for the originating device, configure resource pools, or send scheduling information based on the service identification information;
  • terminal The device identification information can be one or more identifications of the terminal device itself, or the terminal device acts as a proxy terminal device to send the identification of other terminal devices that belong to a group in multicast (for example: the IP address of the terminal device, the MAC of the terminal device) Address, side link layer 2 ID of the terminal device,
  • the sending device and the receiving device are relative concepts
  • the sending device may refer to a device that sends a data packet
  • the receiving device may refer to a device that receives the data packet.
  • the communication type may be other types of communication in addition to unicast communication, multicast communication, or broadcast communication.
  • the embodiments of this application only take unicast communication, multicast communication, and broadcast communication as examples for description.
  • the communication method provided in the embodiments of this application can be used for reference.
  • the application layer (APP layer) entity and/or V2X layer entity of the receiving device can communicate to the access layer (access stratum) of the receiving device.
  • AS The entity sends a notification message.
  • the notification message may include the corresponding second source side identifier of the unicast/multicast/broadcast connection (for example: Source Layer-2 Id of the originating device), the second target side identifier, and the communication Type so that the AS entity of the receiving device can filter the data packet.
  • the application layer entity of the originating device and the application layer entity of the receiving device establish a unicast connection, and the application layer entity of the receiving device communicates to the access layer of the receiving device
  • the entity sends a notification message, the notification message includes the second source side identifier, the second target side identifier and the communication type corresponding to the unicast connection, and the receiving end device can receive the second source side identifier, the second target side identifier and the communication type.
  • the application layer entity and/or V2X layer entity of the receiving device may send a notification message to the access layer entity of the receiving device .
  • the notification message includes the second source side identifier, the second target side identifier, and the communication type corresponding to the group connection, and the receiving end device can receive the same as the second source side identifier, the second target side identifier, and the communication type.
  • Business data includes the second source side identifier, the second target side identifier, and the communication type.
  • the application layer entity of the receiving device sends a notification message to the access layer entity of the receiving device, and the notification message includes the second source side identifier corresponding to the broadcast communication, The second target side identifier and the communication type, the receiving end device can receive the same service data as the second source side identifier, the second target side identifier, and the communication type.
  • the radio bearer group of the side link may be referred to as SLRB group or SLRBs or radio bearer group or RB group.
  • the communication method is introduced.
  • SLRBs can include one or more independent radio bearers, which can be called SLRBs.
  • the one or more independent radio bearers may be sidelink signaling radio bearers (SL-SRB) or sidelink data radio bearers (SL-DRB).
  • SL-SRB sidelink signaling radio bearers
  • SL-DRB sidelink data radio bearers
  • Each SLRB corresponds to a packet data convergence protocol (PDCP) layer entity, one or more radio link control (RLC) layer entities, one or more LCH, etc., or can be described as
  • SLRB includes one PDCP layer entity, one or more RLC layer entities, one or more LCHs, and so on.
  • each SLRB adopts a set of independent configurations, and the configuration of each SLRB is different according to the second target side identifier and/or communication type corresponding to the SLRBs.
  • the configuration information of SLRBs may include the configuration of each SLRB in the SLRBs, and the configuration of the SLRB may include: SLRB identification, PDCP entity configuration, RLC entity configuration, LCH configuration, etc.
  • the SLRB identifier may be used to identify the SLRB, and may be the index number of the SLRB.
  • the configuration of SLRBs included in the same SLRBs may be the same or different.
  • an SLRB group includes 8 SLRBs, and the IDs of the LCHs corresponding to the 8 SLRBs may be different.
  • the configuration information of the SLRB may further include: mapping relationship information from QoS flow to SL-DRB.
  • each QoS flow can have the same QoS parameters, which can be 5G quality of service identifier (5G QoS identifier, 5QI) or quality of service flow identifier (QoS flow identifier, QFI) or V2X quality of service identifier (V2X QoS identifier, 5QI) , VQI), or other QoS parameters that can reflect service reliability, delay, priority, and transmission rate.
  • the PDCP entity configuration can include, but is not limited to, any one or more of the following configuration parameters: the timing length of the timer used to control the storage time of a PDCP SDU in the PDCP buffer (discardTimer), the timing length of the timer used to wait for out-of-order data packets in the reordering function (t-Reordering), whether the PDCP layer can deliver data packets out of order to the upper layer, and whether the PDCP layer adopts side link data compression , And related configuration information for side link data compression, the length of the sequence number (SN) used by the PDCP layer PDU, the security configuration used by the PDCP layer entity (including whether to use encryption and/or integrity protection), the PDCP layer The security algorithm (integrity protection algorithm and encryption algorithm) and/or key used by the entity, whether the PDCP layer entity adopts the duplication mechanism and the configuration of the duplication (if the duplication mechanism is adopted, the PDCP entity can
  • the configuration information related to sidelink data compression may include the size of the compression buffer (buffer), the dictionary used for compression, etc.; the above duplication mechanism refers to the PDCP entity duplicating the PDCP PDU, and A mechanism that is submitted to two or more RLC entities associated for processing and transmission.
  • the RLC entity configuration can include but is not limited to any one or more of the following configuration parameters: Mode adopted by the RLC layer entity: transparent mode (TM)/non-acknowledged mode (unacknowledged mode, UM)/acknowledged mode (AM); if the RLC layer entity is configured to adopt the AM mode, the RLC entity configuration also includes at least one or more of the following: SN length of the RLC layer PDU, control initiation of poll repetition The timing duration of the transmitted timer (t-PollRetransmit), the parameters that need to initiate poll after controlling how many RLC PDUs are sent (poll PDU), the parameters that need to initiate poll after controlling how many bytes of RLC PDUs are sent (poll Byte), RLC Maximum number of layer retransmissions (maxRetxThreshold).
  • TM transparent mode
  • UM unacknowledged mode
  • AM acknowledgenowledged mode
  • the RLC entity configuration also includes at least one or more of the following: SN length of the RLC layer P
  • poll may refer to the RLC layer entity in the sending device instructing the RLC layer entity in the receiving device that adopts the AM mode to perform status report feedback through the poll bit in the MAC PDU. If the RLC layer entity is configured to adopt the UM mode, the RLC entity configuration also includes at least one of the following: the SN length of the RLC layer PDU.
  • the RLC configuration also includes at least one or more of the following: the SN length of the RLC layer PDU, the timing duration of the timer that controls the RLC layer to wait for segmentation (t-Reassembly), or, Control the timing duration (t-StatusProhibit) of the timer that controls the RLC layer to avoid frequently sending status reports.
  • the RLC entity configuration further includes: the SN length of the RLC layer PDU, and/or the timing duration (t-Reassembly) of the timer that controls the RLC layer to wait for the segment.
  • LCH configuration For the configuration of the LCH, it can include, but is not limited to, any one or more of the following configuration parameters: the LCH identifier, the identifier of the logical channel group to which the LCH belongs, and the relevant parameters for logical channel priority processing (priority ), priority bit rate (prioritisedBitRate, PBR) and token bucket size duration (bucket size duration, BSD, etc.), carrier information that can be used to transmit data in the LCH, and resources that can be used to transmit data in the LCH Mode information (for example, mode 1 (mode 1) or mode 2 (mode 2), where mode 1 corresponds to the base station scheduling resource mode, and mode 2 corresponds to the scheduling mode of the terminal device itself), which can be used to transmit the
  • the parameter set (numerology) information of the resource of the data in the LCH (such as subcarrier interval, cyclic prefix length, resource time domain duration, whether it can be one or more of the parameters such as configuring authorized resources), and controlling whether the LCH can be triggered
  • the LCH identifier is the index number of the LCH, which can be used to identify the LCH
  • the identifier of the logical channel group to which the LCH belongs can be the index number of the logical channel group to which the LCH belongs, and can be used to identify the logical channel group to which the LCH belongs.
  • Application layer entity It is a protocol layer entity in the device, which can be called application layer or application entity, and is mainly used to generate application (APP) messages or data packets corresponding to V2X services.
  • APP application
  • Non-access (non-access stratum, NAS) layer entity It is a protocol layer entity in the device, which can be called the NAS layer or NAS entity. It is mainly used to process the transmission of information between the terminal and the core network device. The content of the transmission can be It is user information or control information (such as service establishment, release or mobility management information).
  • the NAS entity has the following functions: session management (including session establishment, modification, release and QoS negotiation), user management (including user data management, and Attachment, detachment, etc.) security management (including authentication and encryption initialization between the user and the network) and billing.
  • RRC layer entity a protocol layer entity in the device, which is mainly responsible for generating RRC messages, measuring configuration and reporting, and can also be responsible for other functions: such as sending dedicated NAS messages, transmitting terminal (user equipment, UE) access capability information, etc.
  • Service data adaptation protocol (SDAP) layer entity is a protocol layer entity in the device, which can be called SDAP layer or SDAP entity, and is mainly used to maintain the mapping relationship between QoS parameters and SLRB.
  • the QoS parameter may be the fifth generation (5G) quality of service identifier (5G QoS identifier, 5QI) or the quality of service flow identifier (QoS flow identifier, QFI) or the proximity communication packet priority (prose per packet priority, PPPP) or near-field communication data packet reliability (prose per packet reliability, PPPR), etc.
  • 5G QoS identifier 5QI
  • QoS flow identifier QoS flow identifier
  • QFI proximity communication packet priority
  • PPPP near-field communication data packet reliability
  • PPPR near-field communication data packet reliability
  • PDCP layer entity It is a protocol layer entity in the device, which can be called PDCP layer or PDCP entity. It mainly processes RRC messages from the control plane and Internet protocol (IP) packets from the data plane. Its functions include : Header compression and decompression, encryption/decryption, integrity protection, transmission of user data and control plane data, reordering and retransmission processing, etc. Each PDCP layer entity has 1 or 2 corresponding RLC layer entities.
  • RLC layer entity It is a protocol layer entity in the device, which can be called RLC layer or RLC entity, which is mainly responsible for segmentation/cascading and reorganization of RLC service data unit (SDU), and through automatic retransmission request (automatic retransmission request). repeat request, ARQ) to perform error correction, reorder RLC protocol data unit (protocol data unit, PDU), repeat packet detection, and re-segment RLC PDU.
  • SDU segmentation/cascading and reorganization of RLC service data unit
  • ARQ automatic retransmission request
  • MAC layer entity It is a protocol layer entity in the device, which can be called MAC layer or MAC entity. It is mainly responsible for matching logical channels and transmission channels, multiplexing multiple MAC SDUs belonging to one or different logical channels to the same MAC On the PDU, and submitted to the PHY (physical) layer entity, through the hybrid automatic repeat request (HARQ) for error correction, scheduling processing, logical channel priority processing, scheduling information reporting, random access process processing Wait.
  • HARQ hybrid automatic repeat request
  • PHY layer entity It is a protocol layer entity in the device, which can be called PHY layer entity or PHY entity, which can create, maintain, and tear down the physical link needed to transmit data, and provide mechanical, electronic, and functional And standard features. Simply put, the PHY layer entity ensures that the original data can be transmitted on various physical media.
  • the communication method provided in the embodiments of this application can be used in any communication system for direct communication between devices, such as: it can be applied to device-to-device (D2D) communication systems or machine-to-machine (M2M) Communication system or V2X communication system, etc.
  • D2D device-to-device
  • M2M machine-to-machine
  • V2X communication system etc.
  • V2X communication system uses a V2X communication system as an example to describe the communication method provided in the embodiment of the present application.
  • Fig. 2 is a V2X communication system provided by an embodiment of the application.
  • the V2X communication system may include: multiple vehicles (vehicle 1, vehicle 2, vehicle 3 as shown in Fig. 2).
  • a direct communication link can be established between the vehicle and surrounding vehicles to realize direct communication.
  • vehicle 1 and vehicle 2 can communicate directly.
  • the direct communication link established between the vehicle and the vehicle may be defined as a side link or a side link (sidelink, SL), and the interface for direct communication between the vehicle and the surrounding vehicles may be called a PC5 port.
  • the V2X communication system shown in FIG. 2 may also include wireless access network equipment. Vehicles can use wireless access network equipment to send V2X messages to the opposite vehicle or access the network through wireless access network equipment.
  • vehicle 1 can send V2X messages to wireless access network equipment, and the wireless access network The device sends a V2X message to vehicle 2.
  • the interface between the vehicle and the wireless access network device may be referred to as a Uu interface.
  • the network architecture shown in FIG. 2 is only an exemplary architecture diagram, and this embodiment of the present application does not limit the number of network elements included in the V2X communication system shown in FIG. 2.
  • the network shown in FIG. 2 may also include other functional entities, such as application servers, core network equipment, etc., which are not limited.
  • the vehicle in FIG. 2 is not limited to any type of vehicle such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed rails, etc.
  • the vehicle may include on-board equipment that can directly communicate with other equipment.
  • the vehicular equipment may be called user equipment (UE) or terminal equipment (terminal).
  • UE user equipment
  • terminal equipment terminal
  • the vehicle can be connected one-to-one with other vehicles in the V2X communication system, that is, unicast communication, it can also perform multicast communication with multiple other vehicles in the V2X communication system, and it can also communicate with multiple other vehicles in the V2X communication system. Broadcast communication.
  • FIG. 3a is a schematic diagram of unicast communication provided by an embodiment of this application. As shown in FIG.
  • FIG. 3a the vehicle 1 and the vehicle 2 can be connected one-to-one for unicast communication.
  • Figure 3b is a schematic diagram of multicast communication provided by an embodiment of the application.
  • vehicle 1 can form a communication group with three other vehicles (vehicle 2, vehicle 3, and vehicle 4).
  • Fig. 3c is a schematic diagram of broadcast communication provided by an embodiment of the application.
  • vehicle 1 can broadcast data to three other vehicles (vehicle 2, vehicle 3, and vehicle 4).
  • a vehicle is used as a terminal device as an example for description.
  • the device for realizing the function of the terminal device may be the terminal device itself, or a device capable of supporting the terminal device to realize the function, such as a chip system.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the radio access network equipment in Figure 2 is mainly used to implement functions such as radio physical control functions, resource scheduling and radio resource management, radio access control, and mobility management.
  • the radio access network device can be an access network (AN)/radio access network (RAN) device, or a device composed of multiple 5G-AN/5G-RAN nodes, and It can be a base station (nodeB, NB), an evolved base station (evolution nodeB, eNB), a next-generation base station (generation nodeB, gNB), a transmission receiving point (TRP), a transmission point (TP), and some Any of the other access nodes.
  • AN access network
  • RAN radio access network
  • a device composed of multiple 5G-AN/5G-RAN nodes and It can be a base station (nodeB, NB), an evolved base station (evolution nodeB, eNB), a next-generation base station (generation nodeB, gNB), a transmission receiving point (TRP), a transmission point (TP), and some Any
  • the device used to implement the function of the wireless access network device may be a wireless access network device, or a device capable of supporting the wireless access network device to implement the function, such as a chip system.
  • the technical solutions provided by the embodiments of the present application are described by taking as an example the apparatus for realizing the functions of the wireless access network equipment being the wireless access network equipment.
  • each vehicle shown in FIG. 2 may include the protocol layer entities shown in FIG. 4: application layer entities, non-access (non-access stratum, NAS) layer entities, and radio resource control (radio resource control, RRC) layer entities , Packet Data Convergence Protocol (PDCP) layer entity, radio link control (RLC) layer entity, MAC layer entity, PHY layer entity, and may also include SDAP layer entity, V2X layer entity or other
  • the newly-added protocol layer entities (not shown in FIG. 4), etc., the related function introduction and configuration of each protocol layer entity are as described above, and will not be repeated.
  • the three entities of the MAC layer entity, the RLC layer entity and the PDCP layer entity can form a data link entity, which is called layer 2 (layer 2, L2).
  • the vehicle can process the transmitted signaling message or data packet through the protocol layer entity shown in Figure 4.
  • the RRC layer entities of vehicle 1 and vehicle 2 can respectively establish corresponding SLRBs for multicast communication, unicast communication, and broadcast communication, and maintain the order Correspondence between broadcast communication/multicast communication/broadcast communication and SLRBs.
  • vehicle 1 When vehicle 1 sends a data packet corresponding to the multicast communication to vehicle 2, vehicle 1 can submit the data packet to the SLRBs corresponding to the multicast communication for processing according to the corresponding relationship, and send the processed data packet to the PC5 port through the PC5 port.
  • the MAC layer entity of vehicle 2 After vehicle 2, the MAC layer entity of vehicle 2 receives the data packet and submits it to the SLRBs corresponding to the multicast communication in vehicle 2 for processing.
  • the process of vehicle 1 sending the data packet corresponding to unicast communication to vehicle 2 and the process of vehicle 1 broadcasting the corresponding data packet to vehicle 2 are similar to this, and will not be repeated.
  • vehicle 2 can send the data according to the correspondence relationship between unicast communication/multicast communication/broadcast communication and SLRBs
  • the packet is submitted to the SLRBs corresponding to unicast communication/multicast communication/broadcast communication for processing, and the processed data packet is sent to vehicle 1 through the PC5 port.
  • the MAC layer entity of vehicle 1 After the MAC layer entity of vehicle 1 receives the data packet, it is delivered to vehicle 1 SLRBs corresponding to unicast communication/multicast communication are processed.
  • the network element, the interface name between each network element, and the name of each protocol layer entity in the above-mentioned Figure 2 architecture are just an example.
  • the specific implementation of the network element, the interface name between the network elements and the protocol layer entity also It may be other names, which are not specifically limited in the embodiments of the present application.
  • FIG. 5 is a schematic diagram of the composition of a communication device 500 provided by an embodiment of the application, and the communication device may be used to implement the communication method provided by the embodiment of the application.
  • the communication device 500 includes at least one processor 501, a communication line 502, and at least one communication interface 503; further, it may also include a memory 504.
  • the processor 501, the memory 504, and the communication interface 503 may be connected through a communication line 502.
  • at least one may be one, two, three, or more, which is not limited in the embodiments of the present application.
  • the communication line 502 may include a path for transmitting information between components included in the communication device.
  • the communication interface 503 is used to communicate with other vehicles or communication networks (such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc.).
  • the communication interface 503 may be a module, a circuit, a transceiver or any device capable of implementing communication.
  • the memory 504 may be a read-only memory (read-only memory, ROM) or other types of static storage devices that can store static information and/or instructions, or a random access memory (random access memory). , RAM) or other types of dynamic storage devices that can store information and/or instructions, and can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (EEPROM) only memory, CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store The desired program code in the form of instructions or data structures and any other medium that can be accessed by the computer, but not limited to this.
  • EEPROM electrically erasable programmable read-only memory
  • CD-ROM compact disc read-only memory
  • optical disc storage including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.
  • the memory 504 may exist independently of the processor 501, that is, the memory 504 may be a memory external to the processor 501. At this time, the memory 504 may be connected to the processor 501 through a communication line 502 for storing instructions Or program code.
  • the processor 501 calls and executes the instructions or program codes stored in the memory 504, it can implement the communication method provided in the following embodiments of the present application.
  • the memory 504 can also be integrated with the processor 501, that is, the memory 504 can be an internal memory of the processor 501.
  • the memory 504 is a cache that can be used to temporarily store some data and/ Or instruction information, etc.
  • the processor 501 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 5.
  • the communication device 500 may include multiple processors, such as the processor 501 and the processor 507 in FIG. 5.
  • the communication apparatus 500 may further include an output device 505 and an input device 506.
  • the input device 506 may be a device such as a microphone or a joystick
  • the output device 505 may be a device such as a display screen and a speaker.
  • the terminal device and/or the network device can perform some or all of the operations in the embodiments of the present application. These operations or operations are only examples. The embodiments of the present application may also perform other operations or various operations. Deformation of operation. In addition, various operations may be performed in a different order presented in the embodiments of the present application, and it may not be necessary to perform all the operations in the embodiments of the present application.
  • Fig. 6 is a flowchart of a communication method provided by an embodiment of the application. As shown in Fig. 6, the method may include steps 601-602.
  • Step 601 The first terminal device sends the SCI to the second terminal device.
  • the first terminal device may be any vehicle in the V2X system shown in FIG. 2, and may establish unicast communication as shown in FIG. 3a, multicast communication as shown in FIG. 3b, or as shown in FIG. 3c with other vehicles. Broadcast communication.
  • the first terminal device may include the protocol layer entity shown in FIG. 4.
  • the PHY entity of the first terminal device when the first terminal device sends service data to the second terminal device, the PHY entity of the first terminal device generates an SCI corresponding to the service data and sends the SCI to the second terminal device.
  • the SCI may include: A target-side identification and communication type.
  • the SCI may include a communication type, or the SCI may include a first source-side identification, a first target-side identification, and a communication type.
  • the first source-side identifier may be the source layer 1 identifier of the first terminal device.
  • the first source-side identifier may be the Source layer 1 Id of the first terminal device.
  • the first target side identifier may be a destination layer 1 identifier, for example: destination layer-1 id.
  • the communication type may be unicast communication as shown in FIG. 3a, multicast communication as shown in FIG. 3b, or broadcast communication as shown in FIG. 3c.
  • the communication type can be a binary bit number "00", "01” or "10", which is used to indicate the type of communication to be performed by the first terminal device, for example, "00" can be used to indicate unicast communication , Use "01” to indicate multicast communication, and "10" to indicate broadcast communication.
  • the first terminal device determines the service data according to the second target side identifier and the communication type.
  • the second target side identifier can be used to identify the service data.
  • the first target side identifier may be the lower 8 bits of the second target side identifier.
  • the second target side identifier may be target_id, group_id, or service_id.
  • the second target side identifier can be assigned by the application layer entity of the leader that initiates unicast communication, multicast communication, or broadcast communication, or by other protocol layer entities of the leader that initiates unicast communication, multicast communication, or broadcast communication (such as: NAS layer entity), the second target side identifiers assigned by different communication types are different; in the embodiment of the present application, the leader that initiates unicast communication, multicast communication, or broadcast communication may be the first terminal device.
  • the second target side identifier is target_id.
  • vehicle 1 is the lead vehicle that initiates unicast communication
  • vehicle 1 and vehicle 2 form unicast communication.
  • the second target side identifier corresponding to the unicast communication may be the application layer of vehicle 1.
  • the target_id1 assigned by the entity.
  • the second target side identifier is group_id.
  • vehicle 1 is the lead vehicle that initiates multicast communication, and that vehicle 1 and vehicle 2, vehicle 3, and vehicle 4 communicate in multicast
  • the second target side corresponding to the multicast communication is The identifier may be group_id1 allocated by the application layer entity of vehicle 1.
  • vehicle 3 and vehicle 4 the second target side identifier corresponding to the multicast communication may be group_id2 allocated by the application layer entity of vehicle 1.
  • the second target side identifier is service_id.
  • the second target side identifier corresponding to the broadcast communication may be service_id1 allocated by the communication system (for example, the 3GPP communication system).
  • the application layer entity of the first terminal device generates one or more data packets with a second target side identifier and a different communication type, and the first terminal device obtains the first LCH, and the first LCH is each second target Among the LCHs corresponding to the data packets with the same side identifier and communication type, the LCH with the highest priority, for the one or more first LCHs, the first terminal device determines that the service data includes the one or more first LCHs, and the priority The data packet corresponding to the first LCH with the highest level.
  • Table 1 shows the second target side identifier, communication type, and priority corresponding to multiple data packets generated by the application layer entity of the first terminal device.
  • the second target side is identified as target_id1.
  • the data packets whose communication type is unicast communication are data packet 1, data packet 4 and data packet 7, and their corresponding priorities are 1, 2 and 3 respectively;
  • the second target side is identified as group_id1
  • the data packets whose communication type is multicast communication include data packet 2 and data packet 5, and their corresponding priority is 2; the second target side identifier is service_id1, and the data packet whose communication type is broadcast communication has data packet 3.
  • the corresponding priority is 3; the second target side identifier is service_id2, and the data packet whose communication type is broadcast communication has data packet 6, and the corresponding priority is 4.
  • the LCH with the highest priority is the LCH corresponding to data packet 1, and its priority is 1;
  • the communication type is For multicast communication data packets, the priority of the LCH of data packet 2 and data packet 5 are both 2, and the second target side identifier is service_id1, and the communication type is broadcast communication.
  • the LCH with the highest priority is data packet 3.
  • the corresponding LCH has a priority of 3; for a data packet whose second target side identifier is service_id2 and the communication type is broadcast communication, the LCH with the highest priority is the LCH corresponding to data packet 6, and its priority is 4. The LCH with the highest priority is the LCH corresponding to data packet 1. Therefore, the first terminal device can determine that the service data includes data packet 1.
  • the first terminal device may allocate the transmission resources according to the second target side identifier, the communication type and the priority. Specifically, if there are transmission resources remaining after the transmission resources are allocated to the first LCH with the highest priority, the first terminal device sorts the data packets with the same second target side identifier and communication type in descending order of priority, and according to the Allocate transmission resources for the remaining data packets in sequence.
  • the service data may also include data packet 4. If the first terminal device allocates transmission resources for data packet 1 and data packet 4, there are still remaining transmission resources, the service data may also include data packet 7.
  • the priority is the priority of the LCH, the priority corresponding to the proximity communication packet priority (prose per packet priority, PPPP), and the proSe per packet reliability (PPPR)
  • the corresponding priority the priority corresponding to the QoS flow identifier (QFI), the priority corresponding to the 5G quality of service identifier (5QI), and the vehicles QoS identifier, VQI) corresponding priority, and PQI corresponding priority.
  • the MAC layer entity of the first terminal device encapsulates the LCH with the second target side identifier and the same communication type in a transport block (TB) for transmission.
  • TB transport block
  • the MAC layer entity of the first terminal device may encapsulate the LCH corresponding to data 1, data 4, and data 7 in one TB for transmission.
  • the MAC layer entity of the first terminal device encapsulates the second source side identifier, the second target side identifier, and the LCH with the same communication type in a transport block (TB) Send in.
  • TB transport block
  • Step 602 The first terminal device sends service data to the second terminal device.
  • the application layer entity of the first terminal device generates the service data and submits it to the lower layer.
  • the lower layer entity processes the service data to generate the MAC PDU corresponding to the service data, and finally passes the PHY entity of the first terminal device Sent to the PHY entity of the second terminal device.
  • the business data is business data associated with the SCI.
  • the service data is included in the MAC PDU.
  • the MAC PDU includes the second target side identifier and the communication type, or the MAC PDU includes the communication type, or the MAC PDU includes the second source side identifier, the second target side identifier and the communication type.
  • the second source-side identifier may be used to identify the first terminal device, and may be the source layer 2 identifier of the first terminal device.
  • the first source-side identifier may be Source Layer-2 of the first terminal device. Id.
  • the second source-side identifier may be the lower 8 bits of the second source-side identifier.
  • the second terminal device determines to receive the service data according to the communication type included in the SCI and the capability of the communication type supported by the second terminal device; or, the second terminal device determines to receive the service data according to the first target side included in the SCI Identification and communication type, and the capability of the first target side identifier and communication type supported by the second terminal device to determine to receive the service data; or, the second terminal device determines to receive the service data according to the first source side identification and the first target The side identification and communication type, and the capabilities of the first source side identification, first target side identification, and communication type supported by the second terminal device determine to receive the service data.
  • the second terminal device receives the service data, and if the communication type supported by the second terminal device itself is different from the communication type included in the SCI , The second terminal device does not receive the service data; or, if the first target side identifier and communication type supported by the second terminal device itself are the same as the first target side identifier and communication type included in the SCI, the second terminal device receives the For service data, if the first target side identifier and communication type supported by the second terminal device itself are different from the first target side identifier and communication type included in the SCI, the second terminal device does not receive the service data; or, if the second terminal device The first source-side identifier, first target-side identifier, and communication type supported by the terminal device itself are the same as the first source-side identifier, first target-side identifier, and communication type included in the SCI, and the second terminal device receives the service data, if The first source-side identifier, first target-side identifier, and communication type supported by the terminal device itself are the same
  • the second terminal device receives the service data, and if the communication type supported by the PHY layer of the second terminal device is the same as that of the SCI The included communication types are not the same, and the second terminal device does not receive the service data; or, if the first target side identifier and communication type supported by the PHY layer of the second terminal device are different from the first target side identifier and communication type included in the SCI Similarly, the second terminal device receives the service data.
  • the second terminal device If the first target side identifier and communication type actually supported by the PHY layer of the second terminal device are different from the first target side identifier and communication type included in the SCI, the second terminal device is not Receive the service data; or, if the first source-side identifier, first target-side identifier, and communication type supported by the PHY layer of the second terminal device and the first source-side identifier, first target-side identifier, and communication type included in the SCI Similarly, the second terminal device receives the service data.
  • first source side identifier, first target side identifier, and communication type supported by the PHY layer of the second terminal device are the same as the first source side identifier and first target side identifier included in the SCI The identifier and the communication type are different, and the second terminal device does not receive the service data.
  • the second terminal device determines to receive the service data according to the communication type included in the MAC PDU and the capability of the communication type supported by the second terminal device; or, the second terminal device determines to receive the service data according to the second communication type included in the MAC PDU.
  • the target side identifier and communication type, as well as the second target side identifier and communication type supported by the second terminal device determine the ability to receive the service data; or, the second terminal device according to the second source side identifier included in the MAC PDU,
  • the second target side identifier and the communication type, and the second source side identifier, the second target side identifier, and the capability of the communication type supported by the second terminal device determine to receive the service data.
  • the second terminal device receives the service data, and if the communication type supported by the second terminal device itself is the same as the communication type included in the MAC PDU Is not the same, the second terminal device does not receive the service data; or, if the second target side identifier and communication type supported by the second terminal device itself are the same as the second target side identifier and communication type included in the MAC PDU, the second terminal The device receives the service data, and if the second target side identifier and communication type supported by the second terminal device itself are not the same as the second target side identifier and communication type included in the MAC PDU, the second terminal device does not receive the service data; or If the second source side identifier, second target side identifier, and communication type supported by the second terminal device itself are the same as the second source side identifier, second target side identifier, and communication type included in the MAC PDU, the second terminal device receives
  • the second terminal device receives the service data, and if the communication type actually supported by the MAC layer of the second terminal device is the same as that The communication type included in the MAC PDU is not the same, and the second terminal device does not receive the service data; or, if the second target side identifier and communication type supported by the MAC layer of the second terminal device are the same as the second target side identifier included in the MAC PDU Same as the communication type, the second terminal device receives the service data.
  • the first The second terminal device does not receive the service data; or, if the second source side identifier, the second target side identifier, and the communication type supported by the MAC layer of the second terminal device and the second source side identifier and second target included in the MAC PDU The side identifier and the communication type are the same, and the second terminal device receives the service data.
  • the second source side identifier, the second target side identifier, and the communication type supported by the MAC layer of the second terminal device are the same as the second source side included in the MAC PDU
  • the identifier, the second target side identifier, and the communication type are different, and the second terminal device does not receive the service data.
  • the second terminal device determines to receive the service data according to the communication type included in the SCI, the communication type included in the MAC PDU, and the capability of the communication type supported by the second terminal device; or The first target side identifier and communication type included in the SCI, the second target side identifier and communication type included in the MAC PDU, and the first target side identifier, second target side identifier, and communication type supported by the second terminal device Ability to determine to receive the service data; or, the second terminal device according to the first source side identifier, first target side identifier and communication type included in the SCI, and the second source side identifier and second target side identifier included in the MAC PDU And the communication type, and the capabilities of the first source-side identifier, first target-side identifier, second source-side identifier, second target-side identifier, and communication type supported by the second terminal device to determine to receive the service data.
  • the second terminal device receives the service data Or, if the first target side identifier and communication type supported by the second terminal device itself are the same as the first target side identifier and communication type included in the SCI, and the second target side identifier and communication type supported by the second terminal device itself The second terminal device receives the service data the same as the second target side identifier and communication type included in the MAC PDU; or, if the first source side identifier, first target side identifier, and communication type supported by the second terminal device itself are the same as The first source-side identifier, first target-side identifier, and communication type included in the SCI are the same, and the second source-side identifier, second target-side identifier, and communication type supported by the second terminal device itself are the same as those included in the MAC PDU.
  • the communication type supported by the PHY layer entity of the second terminal device is the same as the communication type included in the SCI, and the communication type supported by the MSC layer entity of the second terminal device is the same as the communication type included in the MAC PDU
  • first The second terminal device receives the service data; or, if the first target side identifier and communication type actually supported by the PHY layer of the second terminal device are the same as the first target side identifier and communication type included in the SCI, and the second terminal device MAC layer
  • the second target side identifier and communication type actually supported are the same as the second target side identifier and communication type included in the MAC PDU, and the second terminal device receives the service data; or, if the second terminal device PHY layer actually supports the first
  • the source-side identifier, the first target-side identifier, and the communication type are the same as the first source-side identifier, the first target-side identifier, and the communication type included in the SCI, and the second source-side identifier and the second
  • the second terminal device sends feedback information to the first terminal device.
  • the feedback information is used to indicate whether the service data is successfully sent. For example, if the feedback information is ACK, it means that the service data is sent successfully; if the feedback information is NACK, it means that the service data has failed to be sent.
  • the second terminal device receives the SCI sent by the first terminal device, if the SCI includes the first target side identification and/or communication type, and the second terminal device itself supports If the target side identifier and/or communication type are the same, the second terminal device receives the service data and sends feedback information to the first terminal device.
  • the second terminal device may receive data corresponding to the communication type, so as to reduce the rate of incorrect packet reception of the second terminal device, thereby improving the packet receiving efficiency of the second terminal device.
  • the network device may send the first configuration information to the first terminal device, and the first terminal device may obtain the synchronization configuration, the sending mode, or the side chain according to the first configuration information.
  • the first terminal device may also configure the second target side identifier and the SLRB corresponding to the communication type according to the first configuration information, or configure the SLRB corresponding to the communication type.
  • the communication method further includes step 701.
  • Step 701 The first terminal device receives first configuration information from the network device.
  • the first configuration information received by the PHY entity of the first terminal device from the PHY entity of the network device is not limited
  • the first configuration information is system information blocks (SIB), radio resource control (radio resource control, RRC) signaling, MAC signaling, downlink control information (DCI), and NAS information.
  • SIB system information blocks
  • RRC radio resource control
  • MAC media access control
  • DCI downlink control information
  • NAS NAS information
  • the first configuration information is SIB or RRC signaling
  • the first configuration information is generated by the RRC layer entity of the network device
  • the first configuration information is MAC signaling
  • the first configuration information is Generated by the MAC layer entity of the network device
  • the first configuration information is DCI
  • the first configuration information is generated by the PHY layer entity of the network device
  • the first configuration information is NAS signaling or a V3 interface message
  • the first configuration information is obtained by the network device from the core network device.
  • the first configuration information includes a second target side identifier and the communication type, and second configuration information corresponding to the second target side identifier and the communication type, wherein the second configuration information includes a side chain Route configuration information and/or scheduling resources.
  • the side link configuration information is used to indicate synchronization configuration, transmission mode, or location of transmission resources.
  • the scheduling resource includes a transmission resource corresponding to the second target side identifier and/or communication type.
  • the synchronization configuration may include: V2X UE synchronization signal configuration information (for example: v2x-SyncConfig) and/or V2X UE synchronization configuration information (for example: typeTxSync).
  • the transmission mode may include a frequency division duplex mode or a time division duplex mode.
  • the location of the transmission resource can be the range of the transmission resource in the resource pool.
  • the transmission resource is a time-frequency resource used to transmit the service data.
  • the scheduling resource may be a semi-static scheduling resource or a dynamic scheduling resource.
  • the side link configuration information may include one or more of the following information: V2X UE’s receiving resource pool configuration information (for example: v2x-CommRxPool), V2X UE’s sending resource pool configuration information (for example, : V2x-CommTxPoolNormalCommon), P-UE to everything (P2X) UE’s sending resource pool configuration information (for example: p2x-CommTxPoolNormalCommon), V2X UE’s temporary sending resource pool configuration information (for example: v2x- CommTxPoolExceptional), V2X UE's synchronization signal configuration information (for example: v2x-SyncConfig), V2X UE's inter-frequency information (for example: v2x-InterFreqInfoList), V2X UE's resource selection configuration information (for example: v2x-ResourceSelectionConfig), area configuration information (E.g.
  • V2X UE s synchronization configuration information (e.g. typeTxSync), SL/UL (uplink) transmission priority (e.g. thresSL-TxPrioritization, anchor frequency list configuration information (e.g. anchorCarrierFreqList), base station time slot and The GPS time offset (for example: offsetDFN) and the SL channel busyness and idleness measured by the UE determine the parameter configuration information (for example: cbr-CommonTxConfigList) for SL data transmission.
  • synchronization configuration information e.g. typeTxSync
  • SL/UL (uplink) transmission priority e.g. thresSL-TxPrioritization
  • anchor frequency list configuration information e.g. anchorCarrierFreqList
  • base station time slot e.g. anchorCarrierFreqList
  • the GPS time offset for example: offsetDFN
  • the parameter configuration information for example: cbr-CommonTxConfigList
  • the configuration information of the V2X UE's temporary sending resource pool may be in radio link failure (RLF), radio link handover failure (HOF), or when the first terminal device is competing for resources, the measurement data starts to the end of the measurement data When used.
  • RLF radio link failure
  • HAF radio link handover failure
  • the resource selection configuration information of the V2X UE may be used when the first terminal device is in an autonomous resource competition mode.
  • the area configuration information is used when the first terminal device is in an autonomous resource competition mode, calculates a zone ID according to its GPS position, and then applies the sending/receiving resource pool corresponding to the zone ID.
  • the first configuration information may be SIB21, and the first configuration information may include the second target side identifier and the communication type, and the side link configuration corresponding to the second target side identifier and the communication type information.
  • the first terminal device may obtain synchronization configuration, transmission mode, or location of transmission resources according to the side link configuration information.
  • the synchronization configuration information of the V2X UE is used to indicate the priority order of GPS, network equipment, terminal equipment, etc.
  • the SL/UL transmission priority is used to indicate whether to send SL data or UL data preferentially. For example, if the highest PPPP value of the SL sent data is less than the preset threshold, the SL data is sent first, and if the highest PPPP value of the SL sent data is greater than or equal to the preset threshold, the UL data is sent first.
  • the network device allocates resources in the resource pool according to the foregoing configuration information of each side link, the second target side identifier, and the communication type. Specifically, the network device allocates resources to each of the foregoing side link configuration information in the resource pool, and for each of the foregoing resources of side link configuration information, the network device allocates resources to each second target side identifier and communication type. Or, the network device allocates resources to each second target side identification and communication type, and for each resource of the second target side identification and communication type, the network device allocates resources to each side link configuration information described above.
  • the first configuration information may be SIB21, and the first configuration information may include a second target side identifier, a communication type, side link configuration information, and resource pool mapping information, where the second target side identifier, The communication type, side link configuration information, and resource pool mapping information are used to indicate the mapping relationship between the second target side identifier, the communication type, the side link configuration information, and the resource pool.
  • the mapping information of the second target side identifier, communication type, side link configuration information and resource pool includes the second target side identifier, the communication type, and the side link corresponding to the second target side identifier and the communication type Path configuration information
  • the first terminal device may obtain the transmission resource corresponding to the second target side identifier and the communication type according to the second target side identifier, communication type, side link configuration information, and resource pool mapping information, or
  • the terminal device may obtain the location of the transmission resource corresponding to the second target side identifier and the communication type according to the second target side identifier, the communication type, the side link configuration information, and the mapping information of the resource pool. If what the first terminal device acquires is the location of the transmission resource corresponding to the second target side identifier and the communication type, the first terminal device may compete for the resource at the location of the transmission resource through a competitive resource acquisition method.
  • the first configuration information may be RRC signaling
  • the first configuration information may include a second target side identifier and the communication type, and a second configuration corresponding to the second target side identifier and the communication type Information
  • the second configuration information may be a semi-persistent scheduling resource
  • the first terminal device may send the same service as the second target side identifier and the communication type on the semi-persistent scheduling resource data.
  • the first terminal device may send the same service data as the second target side identifier and the communication type on the semi-persistent scheduling resource; or, the first terminal device receives the After the RRC signaling, after receiving the DCI, the same service data as the second target side identifier and the communication type may be sent on the semi-persistent scheduling resource, and the DCI is used to activate the semi-persistent scheduling resource.
  • the first configuration information includes the communication type and the second configuration information corresponding to the communication type.
  • the network device allocates resources in the resource pool according to the foregoing configuration information and communication type of each side link. Specifically, the network device allocates resources to each of the foregoing side link configuration information in the resource pool, and for the resources of each of the foregoing side link configuration information, the network device allocates resources to each communication type; or, the network device allocates resources to each communication type; or Resources are allocated for each communication type, and for the resources of each communication type, the network device allocates resources for each side link configuration information mentioned above.
  • the first configuration information may be SIB21, and the first configuration information may include communication type, side link configuration information, and resource pool mapping information, where the communication type, side link configuration information, and resource pool
  • the mapping information of is used to indicate the mapping relationship between communication type, side link configuration information and resource pool.
  • the communication type, side link configuration information, and resource pool mapping information include the communication type and side link configuration information corresponding to the communication type.
  • the first terminal device can be based on the communication type, side link configuration information and The mapping information of the resource pool obtains the transmission resource corresponding to the communication type, or the first terminal device may obtain the location of the transmission resource corresponding to the communication type according to the communication type, side link configuration information, and mapping information of the resource pool. If what the first terminal device acquires is the location of the transmission resource corresponding to the communication type, the first terminal device may compete for the resource at the location of the transmission resource in a way of acquiring resources through competition.
  • the first configuration information may be RRC signaling
  • the first configuration information includes the communication type and second configuration information corresponding to the communication type
  • the second configuration information may be semi-persistent scheduling resources.
  • a terminal device may send the same service data as the communication type on the semi-persistent scheduling resource.
  • the first configuration information may be RRC signaling
  • the first configuration information includes the communication type and second configuration information corresponding to the communication type
  • the second configuration information may be a dynamic scheduling resource, the dynamic scheduling resource It can be activated only after the first terminal device receives the DCI sent by the network device.
  • the first configuration information includes the second target side identifier and the communication type, the second configuration information corresponding to the second target side identifier and the communication type, QoS information, and the side chain corresponding to the QoS information
  • the configuration information of the SLRB is carried by the radio.
  • the first configuration information may be SIB21
  • the first configuration information may include the second target side identifier and the communication type, second configuration information corresponding to the second target side identifier and the communication type, and
  • the mapping information between the QoS information and the configuration information of the side link radio bearer SLRB is used to indicate the mapping relationship between the QoS information and the configuration information of the SLRB, and the QoS information and the configuration information of the SLRB
  • the mapping information of may include QoS information and configuration information of the SLRB corresponding to the QoS information.
  • the second configuration information may include side link configuration information and/or scheduling resources, the side link configuration information is used to indicate synchronization configuration, transmission mode, or the location of transmission resources, and the scheduling resource includes information related to the second target Side ID and the transmission resource corresponding to the communication type.
  • the first terminal device may obtain the synchronization configuration, the transmission mode, or the location of the transmission resource according to the side link configuration information, the first terminal device may obtain the transmission resource according to the scheduling resource, and the first terminal device may obtain the transmission resource according to the SLRB corresponding to the QoS information.
  • the configuration information obtains the configuration of SLRB.
  • the first configuration information includes the communication type, second configuration information corresponding to the communication type, QoS information, and configuration information of the side link radio bearer SLRB corresponding to the QoS information.
  • the first configuration information may be SIB21, and the first configuration information may include the communication type, the second configuration information corresponding to the communication type, the QoS information and the configuration information of the side link radio bearer SLRB. Mapping information.
  • the mapping information between the QoS information and the SLRB configuration information is used to indicate the mapping relationship between the QoS information and the SLRB configuration information.
  • the mapping information between the QoS information and the SLRB configuration information may include QoS information and SLRB corresponding to the QoS information Configuration information.
  • the second configuration information may include side link configuration information and/or scheduling resources, the side link configuration information is used to indicate synchronization configuration, transmission mode, or the location of transmission resources, and the scheduling resources include transmission corresponding to the communication type. Resources.
  • the first terminal device may obtain the synchronization configuration, the transmission mode, or the location of the transmission resource according to the side link configuration information, the first terminal device may obtain the transmission resource according to the scheduling resource, and the first terminal device may obtain the transmission resource according to the SLRB corresponding to the QoS information.
  • the configuration information obtains the configuration of SLRB.
  • the first configuration information includes QoS information and configuration information of the side link radio bearer SLRB corresponding to the QoS information.
  • the first configuration information may be SIB21
  • the first configuration information may include mapping information between QoS information and configuration information of the sidelink radio bearer SLRB
  • the mapping information between the QoS information and the configuration information of the SLRB is used for Indicate the mapping relationship between the QoS information and the configuration information of the SLRB.
  • the mapping information between the QoS information and the configuration information of the SLRB may include QoS information and configuration information of the SLRB corresponding to the QoS information.
  • the first terminal device may obtain the configuration of the SLRB according to the configuration information of the SLRB corresponding to the QoS information.
  • the first terminal device after receiving the first configuration information sent by the network device, the first terminal device sends feedback information to the network device, where the feedback information is used to indicate whether the first terminal device successfully receives the first configuration information. For example, if the feedback information is ACK, it means that the first terminal device successfully receives the first configuration information; if the feedback information is NACK, it means that the first terminal device fails to receive the first configuration information.
  • the feedback information is ACK, it means that the first terminal device successfully receives the first configuration information; if the feedback information is NACK, it means that the first terminal device fails to receive the first configuration information.
  • the first terminal device stores the first configuration information, where the first configuration information includes the second target side identifier and the communication type, and the information corresponding to the second target side identifier and the communication type Second configuration information; or, the first configuration information includes the communication type and the second configuration information corresponding to the communication type; or, the first configuration information includes the second target side identifier and the communication type, and The second target side identifier and the second configuration information corresponding to the communication type, QoS information, and configuration information of the sidelink radio bearer SLRB corresponding to the QoS information; or, the first configuration information includes the communication type, The second configuration information corresponding to the communication type, the QoS information, and the configuration information of the side link radio bearer SLRB corresponding to the QoS information; or, the first configuration information includes QoS information and the side corresponding to the QoS information Configuration information of the uplink radio bearer SLRB; wherein, the second configuration information includes side link configuration information and/or scheduling resources, and the side link configuration information is used to indicate
  • the first terminal device may receive the first configuration information sent by the network device, the first configuration information includes the second configuration information, and/or the configuration information of the sidelink radio bearer SLRB.
  • the first terminal device may obtain the synchronization configuration, the transmission mode, or the location of the transmission resource according to the second configuration information, and the first terminal device may also configure the SLRB according to the configuration information of the sidelink radio bearer SLRB sent by the network device.
  • the first terminal device may send service information to the network device, and the service information is used by the first terminal device to send the communication type to the network device, so that the network device is based on the communication type.
  • the first terminal device allocates the side link transmission resource corresponding to the communication type.
  • the communication method further includes step 801.
  • Step 801 The first terminal device sends service information to the network device.
  • the RRC layer entity of the first terminal device generates the service information, and then the PHY entity of the first terminal device sends the service information to the PHY entity of the network device.
  • the business information includes: communication type.
  • Example 1 The first terminal device sends service information to the network device; where the service information includes: the communication type.
  • the network device may allocate transmission resources to the first terminal device according to the communication type.
  • the first terminal device sends service information to the network device, and the service information includes the communication type.
  • the network device allocates transmission resources to the first terminal device according to the pre-stored correspondence between the communication type and the transmission resource, or the network device allocates transmission resources to the first terminal device according to the correspondence between the communication type and the transmission resource received from the core network device .
  • Example 2 The first terminal device sends service information to the network device; where the service information includes: the second target side identifier and the communication type.
  • the network device may allocate transmission resources to the first terminal device according to the second target side identifier and the communication type.
  • the first terminal device sends service information to the network device, where the service information includes the second target side identifier and the communication type.
  • the network device allocates transmission resources to the first terminal device according to the pre-stored correspondence between the second target side identification, communication type, and transmission resource, or the network device allocates transmission resources to the first terminal device according to the second target side identification, communication type, and transmission received from the core network device.
  • the resource correspondence information allocates transmission resources for the first terminal device.
  • Example 3 The first terminal device sends service information to the network device; where the service information includes: the communication type and the frequency corresponding to the communication type.
  • the network device may allocate transmission resources to the first terminal device on the frequency point corresponding to the communication type according to the communication type and the frequency point corresponding to the communication type.
  • the first terminal device sends service information to the network device, and the service information includes the communication type and the frequency corresponding to the communication type.
  • the network device allocates transmission resources to the first terminal device according to the pre-stored correspondence between the communication type, frequency point information and transmission resources, or the network device according to the correspondence between the communication type, frequency point information and transmission resources received from the core network equipment
  • the information allocates transmission resources for the first terminal device.
  • the frequency point information is used to indicate the frequency point corresponding to a certain communication type.
  • the first terminal device sends service information to the network device; where the service information includes: the second target side identifier and the communication type, and the second target side identifier and the frequency corresponding to the communication type.
  • the network device may, according to the second target-side identifier and the communication type, and the frequency corresponding to the second target-side identifier and the communication type, be the first at the frequency corresponding to the second target-side identifier and the communication type.
  • the terminal equipment allocates transmission resources. For example, the first terminal device sends service information to the network device, where the service information includes the second target side identifier and the communication type, and the second target side identifier and the frequency corresponding to the communication type.
  • the network device allocates transmission resources to the first terminal device according to the pre-stored correspondence between the second target side identification, communication type, frequency point information, and transmission resources, or the network device allocates transmission resources to the first terminal device according to the second target side identification received from the core network device, Correspondence information between the communication type, frequency point information and transmission resources allocates transmission resources for the first terminal device.
  • the frequency point information is used to indicate a frequency point corresponding to a certain second target side and the communication type.
  • the network device after receiving the service information sent by the first terminal device, the network device sends feedback information to the first terminal device, where the feedback information is used to indicate whether the network device successfully receives the service information.
  • the network device after receiving the service information sent by the first terminal device, the network device sends transmission resource configuration information to the first terminal device, where the transmission resource configuration information includes the transmission resource of the side link used to send the service data .
  • the first terminal device can send the service information to the network device, and the service information can include the communication type.
  • the network device can allocate the communication type corresponding to the first terminal device according to the communication type.
  • the transmission resource for sending the business data can be used to allocate the communication type corresponding to the first terminal device according to the communication type.
  • the first terminal device may send a buffer status report (BSR) to the network device.
  • BSR buffer status report
  • the BSR is used by the first terminal device to request a side link from the network device. Transmission resources.
  • the communication method further includes steps 901 and 902.
  • Step 901 The first terminal device sends a buffer status report BSR to the network device.
  • the MAC entity of the first terminal device generates the BSR, and the PHY entity of the first terminal device sends the BSR to the PHY entity of the network device.
  • the BSR includes the second target side identifier and the communication type, or includes the communication type.
  • Example 1 The first terminal device sends a BSR to the network device; where the BSR includes: the second target side identifier and the communication type.
  • the network device may allocate transmission resources to the first terminal device according to the second target side identifier and the communication type.
  • the first terminal device sends a BSR to the network device, where the BSR includes the second target side identifier and the communication type.
  • the network device may allocate transmission resources to the first terminal device according to the pre-stored correspondence between the second target side identification, communication type, and transmission resource, or the network device may allocate transmission resources to the first terminal device according to the second target side identification and communication type received from the core network device.
  • the corresponding relationship information with the transmission resource allocates transmission resources for the first terminal device, or the network device may include the second target side identifier, the communication type, and the second target side identifier according to the service information reported by the first terminal device, and The frequency point corresponding to the communication type allocates transmission resources to the first terminal device on the frequency point.
  • Example 2 The first terminal device sends a BSR to the network device; where the BSR includes: the communication type.
  • the network device allocates transmission resources to the first terminal device according to the communication type.
  • the first terminal device sends a BSR to the network device, where the BSR includes the communication type.
  • the network device may allocate transmission resources to the first terminal device according to the pre-stored correspondence between the communication type and the transmission resource, or the network device may allocate the first terminal device according to the correspondence between the communication type received from the core network device and the transmission resource Transmission resources, or, the network device may allocate transmission resources to the first terminal device on the frequency point according to the service information reported by the first terminal device including the communication type and the frequency corresponding to the communication type.
  • the network device after receiving the BSR sent by the first terminal device, the network device sends feedback information to the first terminal device, where the feedback information is used to indicate whether the network device successfully receives the BSR.
  • Step 902 The first terminal device receives the transmission resource configuration information sent by the network device.
  • the transmission resource configuration information is DCI.
  • the PHY entity of the network device After the network device receives the BSR, the PHY entity of the network device generates the corresponding DCI and sends it to the first terminal device.
  • the transmission resource configuration information includes the transmission resource of the side link used to send the service data.
  • the first terminal device may send the BSR to the network device, and the BSR may include the second target side identifier and the communication type, or the BSR may include the communication type, and the network device may according to the second target
  • the side identifier and the communication type allocate the transmission resource corresponding to the communication type to the first terminal device for sending the service data; or, the network device may allocate the first terminal device corresponding to the communication type according to the communication type.
  • the transmission resource for sending the business data may be sent to the business data.
  • the first terminal device may send auxiliary information to the network device, and the auxiliary information may include service model information and communication type, so that the network device can allocate the first terminal device according to the auxiliary information Scheduling resources.
  • the communication method further includes steps 1001 and 1002.
  • Step 1001 The first terminal device sends auxiliary information to the network device.
  • the NAS entity, SDAP entity, RRC entity, PDCP entity, RLC entity, MAC entity, or PHY entity of the first terminal device generates the auxiliary information, and the PHY entity of the first terminal device sends the auxiliary information to the PHY entity of the network device.
  • the auxiliary information is not limited to, but not limited
  • the auxiliary information includes business model information and communication types.
  • the service model information may include one or more of the following parameters: service period (for example: trafficPeriodicity), time offset between the arrival time of the data packet and the base station system frame (for example: timingOffset), SL data packet priority (for example: priorityInfoSL ), Uu port LCH identifier (for example: logicalChannelIdentityUL), message packet size (for example: messageSize), service identifier (for example: trafficDestination), SL data packet reliability identifier (for example: reliabilityInfoSL).
  • service period for example: trafficPeriodicity
  • time offset between the arrival time of the data packet and the base station system frame for example: timingOffset
  • SL data packet priority for example: priorityInfoSL
  • Uu port LCH identifier for example: logicalChannelIdentityUL
  • message packet size for example: messageSize
  • service identifier for example: trafficDestination
  • SL data packet reliability identifier for example: reliabilityInfoSL.
  • the first terminal device may send the auxiliary information to the network device, where the auxiliary information includes service model information and communication type.
  • the network device may allocate transmission resources to the first terminal device according to the auxiliary information; or, the network device may allocate scheduling resources to the first terminal device according to the auxiliary information.
  • the network device may use the pre-stored second target side ID, communication type, and The correspondence of transmission resources allocates transmission resources to the first terminal device, or the network device may allocate transmission resources to the first terminal device according to the correspondence information between the second target side identifier, the communication type, and the transmission resource received from the core network device, Alternatively, the network device may include the second target side identifier, the communication type and the second target side identifier, and the frequency point corresponding to the communication type according to the service information reported by the first terminal device, where the frequency point is the first The terminal equipment allocates transmission resources.
  • the first terminal device may determine that the LCH corresponding to the second target side identifier and the communication type has the highest priority, and the first terminal device preferentially sends the service data corresponding to the second target side identifier and the communication type, or the first terminal device A terminal device may send the same service data as the second target side identifier and communication type on the transmission resource.
  • the network device may allocate scheduling resources to the first terminal device according to the pre-stored correspondence between the communication type and the transmission resource, or the network device may allocate scheduling resources to the first terminal device according to the The corresponding relationship between the communication type and the transmission resource is the first terminal device to allocate scheduling resources, or the network device may include the communication type and the frequency corresponding to the communication type on the frequency point according to the service information reported by the first terminal device Allocate scheduling resources for the first terminal device.
  • the scheduling resource can be a semi-static scheduling resource or a dynamic scheduling resource. Then, the first terminal device may send service data of the same communication type on the scheduling resource within the service period (for example, 20 milliseconds).
  • the service identifier includes the second target side identifier (for example: destination layer-2 id)
  • the network device can be based on the pre-stored second target side identifier
  • the correspondence between the communication type and the transmission resource allocates scheduling resources for the first terminal device, or the network device can be the first terminal device according to the correspondence information between the second target side identifier, the communication type and the transmission resource received from the core network device Allocate scheduling resources, or, the network device may include the second target side identifier, the communication type and the second target side identifier, and the frequency corresponding to the communication type on the frequency point based on the service information reported by the first terminal device Allocate scheduling resources for the first terminal device.
  • the scheduling resource can be a semi-static scheduling resource or a dynamic scheduling resource. Then, the first terminal device may send the same service data as the second target side identifier and the communication type on the scheduling resource within the service period (for example: 50 milli
  • the first terminal device sends the auxiliary information to the network device, where the auxiliary information includes service model information and communication type.
  • the network device may allocate transmission resources for transmitting data and feedback resources for sending feedback information to the first terminal device according to the auxiliary information.
  • the network device may allocate a transmission resource for transmitting data and a feedback resource for sending feedback information to the first terminal device according to the auxiliary information; if the communication type is In multicast communication, the network device can allocate transmission resources for transmitting data and multiple feedback resources for sending feedback information to the first terminal device according to the auxiliary information; if the communication type is broadcast communication, the network device can according to the auxiliary information The information allocates transmission resources for transmitting data to the first terminal device, and the network device may not allocate feedback resources for the first terminal device.
  • the network device after receiving the auxiliary information sent by the first terminal device, the network device sends feedback information to the first terminal device, where the feedback information is used to indicate whether the network device successfully receives the auxiliary information.
  • Step 1002 The first terminal device receives scheduling resources from the network device.
  • the RRC entity of the network device After the network device receives the auxiliary information, the RRC entity of the network device generates configuration information including the scheduling resource, and sends the configuration information to the first terminal device.
  • the scheduling resource may include the transmission resource of the side link used to send the service data.
  • the first terminal device may send the auxiliary information to the network device.
  • the auxiliary information may include service model information and communication type.
  • the network device may assign the first terminal to the first terminal according to the service model information and the communication type.
  • the device allocates scheduling resources corresponding to the communication type.
  • the first terminal device may also send QoS information to the network device, and the QoS information may include the second target side identifier and the communication type, or, The communication type is included, so that the network device sends the SLRB configuration information to the first terminal device according to the QoS information.
  • the communication method further includes step 1101.
  • Step 1101 The first terminal device sends QoS information to the network device.
  • the upper layer entity or AS entity of the first terminal device generates the QoS information, and the PHY entity of the first terminal device sends the QoS information to the PHY entity of the network device, where the upper layer entity includes Application layer entity, V2X layer entity and NAS entity.
  • the QoS information may include the second target side identifier and the communication type, or include the communication type.
  • the QoS information further includes at least one of the following information: the connection identifier of the unicast or multicast connection (for example: ConnId), the connection group identifier of the multicast connection (for example: GroupId), and the second source side identifier (For example: layer 2Id of the first terminal device), service quality information.
  • the service quality information may be PPPP, PPPR, QFI, 5QI, VQI, PQI and other service quality information.
  • the service quality information may include delay, reliability, communication distance, rate, packet size, packet interval, etc.
  • the first terminal device may send the QoS information to the network device, and the network device may send the SLRB configuration information to the first terminal device according to the correspondence between the pre-stored QoS information and the SLRB configuration information, or the network device may send the SLRB configuration information according to the slave core network
  • the correspondence between the QoS information received by the device and the configuration information of the SLRB sends the configuration information of the SLRB to the first terminal device.
  • the network device after receiving the QoS information sent by the first terminal device, the network device sends feedback information to the first terminal device, where the feedback information is used to indicate whether the network device successfully receives the QoS information.
  • the first terminal device may send the QoS information to the network device.
  • the QoS information may include the second target side identifier and the communication type, or, including the communication type, the network device may send the QoS information according to the QoS
  • the information sends the SLRB configuration information to the first terminal device.
  • the first terminal device may also receive the SLRB configuration information sent by the network device, and configure the SLRB corresponding to the service data according to the SLRB configuration information.
  • the communication method further includes step 1201.
  • Step 1201 The first terminal device receives SLRB configuration information from a network device.
  • the PHY entity of the first terminal device receives SLRB configuration information from the PHY entity of the network device.
  • the configuration information of the SLRB may be generated by a network device.
  • the configuration information of the SLRB may include the SLRB configuration corresponding to the second target side identifier and/or the communication type; the SLRB configuration includes the mapping relationship between the quality of service flow QoS flow and the side link data radio bearer SL-DRB , PDCP configuration, at least one of RLC configuration and LCH configuration.
  • the first terminal device configures the second target side identifier and the SLRB corresponding to the communication type according to the configuration information of the SLRB, or the first terminal device configures the SLRB corresponding to the communication type according to the configuration information of the SLRB.
  • the first terminal device after receiving the SLRB configuration information sent by the network device, the first terminal device sends feedback information to the network device, where the feedback information is used to indicate whether the first terminal device successfully receives the SLRB configuration information. For example, if the feedback information is ACK, it indicates that the first terminal device successfully received the configuration information of the SLRB; if the feedback information is NACK, it indicates that the first terminal device failed to receive the configuration information of the SLRB.
  • the first terminal device may configure the SLRB configuration information sent by the network device, and configure the second target side identifier and/or the SLRB corresponding to the communication type according to the SLRB configuration information.
  • the first terminal device may also send SLRB configuration information to the second terminal device, so that the second terminal device can process the received SLRB configuration information according to the SLRB configuration information.
  • Business data may also send SLRB configuration information to the second terminal device, so that the second terminal device can process the received SLRB configuration information according to the SLRB configuration information.
  • the communication method further includes step 1301.
  • Step 1301 The first terminal device sends SLRB configuration information to the second terminal device.
  • the PHY entity of the first terminal device sends the SLRB configuration information to the PHY entity of the second terminal device.
  • the first terminal device after receiving the SLRB configuration information sent by the network device, the first terminal device sends the SLRB configuration information to the second terminal device.
  • the second terminal device may process the received service data according to the configuration information of the SLRB.
  • the second terminal device receives the SLRB configuration information sent by the first terminal device, and sends feedback information to the first terminal device, where the feedback information is used to indicate whether the second terminal device successfully receives the SLRB configuration information. For example, if the feedback information is ACK, it indicates that the second terminal device successfully received the configuration information of the SLRB; if the feedback information is NACK, it indicates that the second terminal device failed to receive the configuration information of the SLRB.
  • the second terminal device can receive the SLRB configuration information sent by the first terminal device, and process the received service data according to the SLRB configuration information.
  • the first terminal device may establish a first connection with the second terminal device, so that the second terminal device can receive the service data.
  • the communication method further includes step 1401.
  • Step 1401 The first terminal device establishes a first connection with the second terminal device.
  • the first terminal device before the first terminal device sends the SCI, if the first terminal device does not establish a first connection corresponding to the second target side identifier and/or the communication type with the second terminal device, the first terminal device and The second terminal device establishes the first connection.
  • the first terminal device sends the SCI, if the first terminal device does not establish a first connection with the second terminal device corresponding to the second source side identifier, the second target side identifier, and the communication type, The first terminal device establishes a first connection with the second terminal device.
  • the second terminal device before the second terminal device receives the service data, if the second terminal device does not establish a first connection with the first terminal device corresponding to the second target side identifier and/or the communication type, the second terminal device and The first terminal device establishes a first connection.
  • the second terminal device before the second terminal device receives the service data, if the second terminal device does not establish a first connection with the first terminal device corresponding to the second source-side identifier, the second target-side identifier, and the communication type, The second terminal device establishes a first connection with the first terminal device.
  • the second terminal device when the second terminal device receives the service data, if the second terminal device does not establish a first connection with the first terminal device corresponding to the second target side identifier and/or the communication type, the second terminal device and The first terminal device establishes a first connection.
  • the second terminal device when the second terminal device receives the service data, if the second terminal device does not establish a first connection with the first terminal device corresponding to the second source-side identifier, the second target-side identifier, and the communication type, The second terminal device establishes a first connection with the first terminal device.
  • the second terminal device receives the service data, if the second terminal device does not establish a first connection corresponding to the second target side identifier and/or the communication type with the first terminal device, the second terminal device and The first terminal device establishes a first connection.
  • the second terminal device receives the service data, if the second terminal device does not establish a first connection with the first terminal device corresponding to the second source-side identifier, the second target-side identifier, and the communication type, The second terminal device establishes a first connection with the first terminal device.
  • the first connection is an AS connection and/or an SLRB connection.
  • the first terminal device After the first terminal device establishes the first connection with the second terminal device, it sends the SCI and the service data corresponding to the SCI to the second terminal device, and the SCI includes the first target side identifier And the communication type, or the SCI includes the communication type, the second terminal device can receive the service data of the corresponding communication type, so as to reduce the packet error receiving rate of the second terminal device, thereby improving the packet receiving efficiency of the second terminal device.
  • the foregoing mainly introduces the solution provided by the embodiment of the present application from the perspective of interaction between various network elements.
  • the first terminal device, the second terminal device, or the network device, etc. include hardware structures and/or software modules corresponding to each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.
  • the embodiments of the present application can divide the first terminal device, the second terminal device, or the network device into functional modules according to the above method examples.
  • each functional module can be divided corresponding to each function, or two or more functions can be divided.
  • the above-mentioned integrated modules can be implemented in the form of hardware or software functional modules. It should be noted that the division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 15 shows a schematic structural diagram of a first terminal device 1500.
  • the first terminal device 1500 includes: a communication module 1501 and a sending module 1502.
  • the communication module 1501 is used to communicate with the network device and the second terminal;
  • the sending module 1502 is used to send the side link control information SCI and service data to the second terminal device; wherein, the SCI includes the first target side Identifies and communication type, or includes the communication type.
  • the first terminal device 1500 further includes a determining module 1503.
  • the determining module 1503 is configured to determine the service data according to the second target side identifier and the communication type, the second target side identifier is used to identify the service data, the second target side identifier and the first target There is a corresponding relationship between the side identifiers.
  • the first terminal device 1500 further includes a receiving module 1504.
  • the receiving module 1504 is configured to receive first configuration information from a network device; wherein, the first configuration information includes a second target side identifier and the communication type, and a second target side identifier and the communication type corresponding to the second target side identifier. 2.
  • the second target side identifier is used to identify the service data
  • the second configuration information includes side link configuration information and/or scheduling resources
  • the side link configuration information is used to indicate synchronization configuration
  • the transmission mode or the location of the transmission resource, the scheduling resource includes the transmission resource corresponding to the second target side identifier and/or the communication type; or, the first configuration information includes the communication type and the communication type corresponding to the Second configuration information
  • the second target side identifier is used to identify the service data
  • the second configuration information includes side link configuration information and/or scheduling resources
  • the side link configuration information is used to indicate synchronization configuration
  • the transmission mode or the location of the transmission resource, the scheduling resource includes the transmission resource corresponding to the second target side identifier and/or the communication type; or, the first configuration information includes the second target side identifier and the communication type,
  • the first configuration information is system information block SIB, radio resource control RRC signaling, medium access control MAC signaling, downlink control information DCI, non-access stratum NAS signaling, or V3 interface message.
  • the first terminal device 1500 further includes a storage module 1505.
  • the storage module 1505 is configured to store first configuration information; wherein, the first configuration information includes a second target side identifier and the communication type, and second configuration information corresponding to the second target side identifier and the communication type , wherein the second target side identifier is used to identify the service data, the second configuration information includes side link configuration information and/or scheduling resources, and the side link configuration information is used to indicate synchronization configuration, transmission mode or The location of the transmission resource, the scheduling resource includes the transmission resource corresponding to the second target side identifier and/or the communication type; or, the first configuration information includes the communication type and the second configuration corresponding to the communication type Information, wherein the second target side identifier is used to identify the service data, the second configuration information includes side link configuration information and/or scheduling resources, and the side link configuration information is used to indicate synchronization configuration and transmission mode Or the location of the transmission resource, the scheduling resource includes the transmission resource corresponding to the second target side identifier and/
  • the second configuration information includes side link configuration information and/or scheduling resources, the side link configuration information is used to indicate synchronization configuration, transmission mode, or the location of the transmission resource, and the scheduling resource includes identification with the second target side.
  • the first configuration information includes the communication type, the second configuration information corresponding to the communication type, QoS information, and the side link radio bearer corresponding to the QoS information SLRB configuration information, where the second target side identifier is used to identify the service data, the second configuration information includes side link configuration information and/or scheduling resources, and the side link configuration information is used to indicate synchronization configuration ,
  • the transmission mode or the location of the transmission resource, the scheduling resource includes the transmission resource corresponding to the second target side identifier and/or the communication type; or the first configuration information includes QoS information and the side corresponding to the QoS information
  • the uplink radio bears the configuration information of the SLRB.
  • the sending module 1502 is further configured to send service information to the network device; where the service information includes: the communication type.
  • the sending module 1502 is further configured to send a buffer status report BSR to the network device; wherein, the BSR includes the second target side identifier and the communication type, or includes the communication type.
  • the sending module 1502 is also used to send auxiliary information to the network device; wherein the auxiliary information includes service model information and the communication type.
  • the sending module 1502 is further configured to send the QoS information to the network device; wherein, the QoS information includes the second target side identifier and the communication type, or includes the communication type.
  • the receiving module 1504 is further configured to receive SLRB configuration information from the network device; wherein, the SLRB configuration information includes the SLRB configuration corresponding to the second target side identifier and/or the communication type; the SLRB The configuration includes at least one of the mapping relationship between the quality of service flow QoS flow to the side link data radio bearer SL-DRB, the packet data convergence protocol PDCP configuration, the radio link control RLC configuration and the logical channel LCH configuration.
  • the sending module 1502 is further configured to send configuration information of the SLRB to the second terminal device.
  • the first terminal device 1500 further includes an establishment module 1506.
  • the establishment module 1506 is configured to establish a first connection by the first terminal device if the first terminal device has not established a first connection corresponding to the second target side identifier and/or the communication type with the second terminal device;
  • the first connection is an access layer AS connection and/or a side link radio bearer SLRB connection.
  • the first terminal device 1500 is presented in the form of dividing various functional modules in an integrated manner.
  • the "module” here can refer to a specific ASIC, circuit, processor and memory that executes one or more software or firmware programs, integrated logic circuit, and/or other devices that can provide the above-mentioned functions.
  • the first terminal device 1500 may adopt the form shown in FIG. 5.
  • the processor 501 in FIG. 5 may invoke the computer execution instructions stored in the memory 504 to enable the first terminal device 1500 to execute the communication method in the foregoing method embodiment.
  • the functions/implementation processes of the communication module 1501, the sending module 1502, the determining module 1503, the receiving module 1504, the storage module 1505, and the establishment module 1506 in FIG. 19 can be stored in the memory 504 through the processor 501 in FIG.
  • the computer executes instructions to achieve.
  • the functions/implementation processes of the communication module 1501, the determination module 1503, the storage module 1505, and the establishment module 1506 in FIG. 19 can be implemented by the processor 501 in FIG. 5 calling the computer execution instructions stored in the memory 504, as shown in FIG.
  • the functions/implementation process of the sending module 1502 and the receiving module 1504 can be implemented through the communication interface 503 in FIG. 5.
  • the first terminal device 1500 provided in this embodiment can execute the above-mentioned communication method, the technical effects that can be obtained can refer to the above-mentioned method embodiment, which will not be repeated here.
  • FIG. 20 shows a schematic structural diagram of a second terminal device 2000.
  • the second terminal device 2000 includes: a communication module 2001 and a receiving module 2002.
  • the communication module 2001 is used to communicate with the network device and the first terminal device;
  • the receiving module 2002 is used to receive the side link control information SCI and service data sent by the first terminal device; wherein, the SCI includes the first target Side identification and communication type, or including communication type.
  • the second terminal device 2000 further includes: a determining module 2003.
  • the determining module 2003 is configured to determine to receive the service data according to the communication type included in the SCI and the capability of the communication type supported by the second terminal device; or, the determining module 2003 is configured to determine to receive the service data according to the first included in the SCI.
  • the target side identifier and communication type, and the capability of the first target side identifier and communication type supported by the second terminal device determine to receive the service data.
  • the receiving module 2002 is further configured to receive first configuration information from a network device; wherein, the first configuration information includes a second target side identifier and the communication type, as well as the second target side identifier and the The second configuration information corresponding to the communication type, wherein the second target side identifier is used to identify the service data, the second configuration information includes side-link configuration information and/or scheduling resources, and the side-link configuration information is used
  • the scheduling resource includes the transmission resource corresponding to the second target side identifier and/or the communication type; or, the first configuration information includes the communication type, and The second configuration information corresponding to the communication type, where the second target side identifier is used to identify the service data, the second configuration information includes side uplink configuration information and/or scheduling resources, and the side uplink configuration information Used to indicate synchronization configuration, transmission mode, or location of transmission resources, the scheduling resource includes a transmission resource corresponding to the second target side identifier and/or the communication type; or,
  • the first configuration information is system information block SIB, radio resource control RRC signaling, MAC signaling, downlink control information DCI, non-access stratum NAS signaling, or V3 interface message.
  • the receiving module 2002 is further configured to receive configuration information of a side-link radio bearer SLRB from the first terminal device; wherein, the configuration information of the SLRB includes the identification with the second target side and/or the communication type Corresponding SLRB configuration; the SLRB configuration includes at least one of the mapping relationship between the quality of service flow QoS flow to the side link data radio bearer SL-DRB, the packet data convergence protocol PDCP configuration, the radio link control RLC configuration and the logical channel LCH configuration One.
  • the second terminal device 2000 further includes: an establishment module 2004.
  • the establishment module 2004 is configured to establish a first connection if the second terminal device does not establish a first connection corresponding to the second target side identifier and/or the communication type with the first terminal device; wherein, the first connection For the access layer AS connection and/or side link radio bearer SLRB connection.
  • the second terminal device 2000 is presented in the form of dividing various functional modules in an integrated manner.
  • the "module” here can refer to a specific ASIC, circuit, processor and memory that executes one or more software or firmware programs, integrated logic circuit, and/or other devices that can provide the above-mentioned functions.
  • the second terminal device 2000 may adopt the form shown in FIG. 5.
  • the processor 501 in FIG. 5 may invoke the computer-executable instructions stored in the memory 504 to cause the second terminal device 2000 to execute the communication method in the foregoing method embodiment.
  • the functions/implementation processes of the communication module 2001, the receiving module 2002, the determining module 2003, and the establishing module 2004 in FIG. 22 may be implemented by the processor 501 in FIG. 5 calling the computer execution instructions stored in the memory 504.
  • the function/implementation process of the determining module 2003 and the establishing module 2004 in FIG. 22 may be implemented by the processor 501 in FIG. 5 calling the computer execution instructions stored in the memory 504, and the communication module 2001 and the receiving module 2002 in FIG.
  • the function/realization process of can be realized through the communication interface 503 in FIG. 5.
  • the second terminal device 2000 provided in this embodiment can execute the above-mentioned communication method, the technical effects that can be obtained can refer to the above-mentioned method embodiment, which will not be repeated here.
  • FIG. 23 shows a schematic structural diagram of a network device 2300.
  • the network device 2300 includes: a communication module 2301 and a sending module 2302.
  • the communication module 2301 is used to communicate with the first terminal device and the second terminal device;
  • the sending module 2302 is used to send the first configuration information to the first terminal device and/or the second terminal device, wherein the first configuration
  • the information includes a second target-side identifier and the communication type, and second configuration information corresponding to the second target-side identifier and the communication type.
  • the second target-side identifier is used to identify the service data
  • the second The configuration information includes side link configuration information and/or scheduling resources, the side link configuration information is used to indicate synchronization configuration, transmission mode, or location of transmission resources, and the scheduling resources include identification and/or scheduling resources associated with the second target side.
  • the transmission resource corresponding to the communication type; or, the first configuration information includes the communication type and second configuration information corresponding to the communication type, wherein the second target side identifier is used to identify the service data, and the first configuration information
  • the second configuration information includes side link configuration information and/or scheduling resources, the side link configuration information is used to indicate synchronization configuration, transmission mode, or location of transmission resources, and the scheduling resources include identification and/or scheduling resources related to the second target side.
  • the first configuration information includes a second target side identifier and the communication type, second configuration information corresponding to the second target side identifier and the communication type, QoS information, and The configuration information of the side link radio bearer SLRB corresponding to the QoS information, wherein the second target side identifier is used to identify the service data, and the second configuration information includes side link configuration information and/or scheduling resources.
  • the side link configuration information is used to indicate the synchronization configuration, the transmission mode, or the location of the transmission resource
  • the scheduling resource includes the transmission resource corresponding to the second target side identifier and/or the communication type; or, in the first configuration information Including the communication type, second configuration information corresponding to the communication type, QoS information, and configuration information of the side link radio bearer SLRB corresponding to the QoS information, wherein the second target side identifier is used to identify the service data ,
  • the second configuration information includes side link configuration information and/or scheduling resources, the side link configuration information is used to indicate synchronization configuration, transmission mode, or the location of transmission resources, and the scheduling resources include side link configuration information and/or scheduling resources.
  • the identification and/or the transmission resource corresponding to the communication type; or, the first configuration information includes QoS information and configuration information of the side link radio bearer SLRB corresponding to the QoS information.
  • the first configuration information is system information block SIB, radio resource control RRC signaling, medium access control MAC signaling, downlink control information DCI, non-access stratum NAS signaling, or V3 interface message.
  • the network device further includes: a receiving module 2303.
  • the receiving module 2303 is configured to receive service information from the first terminal device; where the service information includes: the communication type.
  • the receiving module 2303 is further configured to receive a buffer status report BSR from the first terminal device; wherein, the BSR includes the second target side identifier and the communication type, or includes the communication type.
  • the receiving module 2303 is further configured to receive auxiliary information from the first terminal device; wherein, the auxiliary information includes the service model and the communication type.
  • the receiving module 2303 is further configured to receive QoS information from the first terminal device; wherein, the QoS information includes the second target side identifier and the communication type, or includes the communication type.
  • the sending module 2302 is further configured to send configuration information of a side-link radio bearer SLRB to the first terminal device according to the QoS information; wherein, the configuration information of the SLRB includes the identification and the second target side identification / Or SLRB configuration corresponding to the communication type; the SLRB configuration includes the mapping relationship between the quality of service flow QoS flow to the side link data radio bearer SL-DRB, the packet data convergence protocol PDCP configuration, the radio link control RLC configuration, and the logical channel At least one of the LCH configurations.
  • the network device 2300 is presented in the form of dividing various functional modules in an integrated manner.
  • the "module” here can refer to a specific ASIC, circuit, processor and memory that executes one or more software or firmware programs, integrated logic circuit, and/or other devices that can provide the above-mentioned functions.
  • the network device 2300 may adopt the form shown in FIG. 5.
  • the processor 501 in FIG. 5 may invoke the computer execution instructions stored in the memory 504 to cause the network device 2300 to execute the communication method in the foregoing method embodiment.
  • the functions/implementation processes of the communication module 2301, the sending module 2302, and the receiving module 2303 in FIG. 24 may be implemented by the processor 501 in FIG. 5 calling the computer execution instructions stored in the memory 504.
  • the function/implementation process of the communication module 2301 in FIG. 24 can be implemented by the processor 501 in FIG. 5 calling a computer execution instruction stored in the memory 504, and the functions/implementation of the sending module 2302 and the receiving module 2303 in FIG. 24 The process can be implemented through the communication interface 503 in FIG. 5.
  • the network device 2300 provided in this embodiment can execute the above-mentioned communication method, the technical effects that can be obtained can refer to the above-mentioned method embodiment, and will not be repeated here.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • a software program it may be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application are generated in whole or in part.
  • the computer can be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices.
  • Computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • computer instructions may be transmitted from a website, computer, server, or data center through a cable (such as Coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL) or wireless (such as infrared, wireless, microwave, etc.) transmission to another website site, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or may include one or more data storage devices such as a server or a data center that can be integrated with the medium.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

Landscapes

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

Abstract

本申请实施例提供通信方法及装置，涉及无线通信领域。其中，通信方法包括：第一终端设备的媒体接入控制MAC实体选择一个通信类型对应的目标侧标识；所述第一终端设备的MAC实体获取第一逻辑信道LCH，所述第一LCH为所述目标侧标识和所述通信类型对应的有数据的LCH中，优先级最高的LCH；所述第一终端设备的MAC实体为所述第一LCH中的数据分配传输资源。

Description

通信方法及设备
“本申请要求于2019年3月28日提交国家知识产权局、申请号为201910245325.9、发明名称为“通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。”
技术领域
本申请涉及无线通信领域，尤其涉及通信方法及设备。
背景技术
车联网(vehicle to everything，V2X)被认为是物联网体系中最有产业潜力、市场需求最为明确的领域之一，具有应用空间广、产业潜力大、社会效益强的特点。对促进汽车和信息通信产业创新发展，构建汽车和交通服务新模式新业态，推动自动驾驶技术创新和应用，提高交通效率和安全水平具有重要意义。V2X是指通过装载在车上的传感器、车载终端等提供车辆信息，并通过各种通信技术实现车与车、车与人、车与路边基础设施、车与网络之间进行相互通信。
长期演进(long term evolution，LTE)***中的V2X只支持广播通信，而在新空口(new radio，NR)***中，V2X不仅支持广播通信，还支持单播通信和组播通信。目前，针对NR***，还没有一种V2X的通信方法，使收端设备可以接收对应通信类型的数据，以降低收端设备的误收包率，进而提高收端设备的收包效率。
发明内容
本申请实施例提供通信方法及设备，可以使收端设备接收对应通信类型的数据，以降低收端设备的误收包率，进而提高收端设备的收包效率。
为达到上述目的，本申请的实施例采用如下技术方案：
第一方面，本申请实施例提供一种通信方法，该方法包括：第一终端设备向第二终端设备发送侧行链路控制信息SCI和业务数据；其中，该SCI包括第二目标侧标识和通信类型，或包括该通信类型。基于此方案，第二终端设备可以接收对应通信类型的业务数据，以降低第二终端设备的误收包率，进而提高第二终端设备的收包效率。
在一种可能的实现方式中，该第一终端设备根据第二目标侧标识和该通信类型确定该业务数据，该第二目标侧标识用于标识该业务数据。基于此方案，第一终端设备可以根据第二目标侧标识和通信类型确定要发送的业务数据，并向第二终端设备发送该业务数据对应的SCI，以使得第二终端设备接收对应通信类型的业务数据，以降低第二终端设备的误收包率，进而提高第二终端设备的收包效率。
在一种可能的实现方式中，该第一终端设备接收网络设备发送的第一配置信息；或，第一终端设备存储第一配置信息，其中，该第一配置信息中包括第二目标侧标识和该通信类型、以及与该第二目标侧标识和该通信类型对应的第二配置信息，其中，所述第二目标侧标识用于标识所述业务数据，所述第二配置信息包括侧行链路配置信息和/或调度资源，所述侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，所述调度资源包括与所述第二目标侧标识和/或所述通信类型对应的传输资源； 或者，该第一配置信息中包括该通信类型、以及与该通信类型对应的第二配置信息，其中，所述第二目标侧标识用于标识所述业务数据，所述第二配置信息包括侧行链路配置信息和/或调度资源，所述侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，所述调度资源包括与所述第二目标侧标识和/或所述通信类型对应的传输资源；或者，该第一配置信息中包括第二目标侧标识和该通信类型、与该第二目标侧标识和该通信类型对应的第二配置信息、服务质量信息、以及与服务质量信息对应的侧行链路无线承载的配置信息，其中，所述第二目标侧标识用于标识所述业务数据，所述第二配置信息包括侧行链路配置信息和/或调度资源，所述侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，所述调度资源包括与所述第二目标侧标识和/或所述通信类型对应的传输资源；或者，该第一配置信息中包括该通信类型、与该通信类型对应的第二配置信息、服务质量信息、以及与服务质量信息对应的侧行链路无线承载的配置信息，其中，所述第二目标侧标识用于标识所述业务数据，所述第二配置信息包括侧行链路配置信息和/或调度资源，所述侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，所述调度资源包括与所述第二目标侧标识和/或所述通信类型对应的传输资源；或者，该第一配置信息中包括与服务质量信息、以及服务质量信息对应的侧行链路无线承载的配置信息。基于此方案，第一终端设备可以根据该第二配置信息获取同步配置、发送方式或传输资源的位置，第一终端设备还可以根据网络设备发送的侧行链路无线承载的配置信息配置侧行链路无线承载。
在一种可能的实现方式中，该第一配置信息为***信息块、无线资源控制信令、媒介访问控制信令、下行控制信息、非接入层信令或接口消息。基于此方案，第一终端设备可以通过***信息块、无线资源控制信令、媒介访问控制信令、下行控制信息、非接入层信令或V3接口消息发送该第一配置信息。
在一种可能的实现方式中，该第一终端设备向该网络设备发送业务信息；其中，该业务信息包括：该通信类型。基于此方案，第一终端设备可以通过向网络设备发送该业务信息，获取用于发送该业务数据的传输资源。
在一种可能的实现方式中，该第一终端设备向该网络设备发送缓存状态报告；其中，该缓存状态报告包括第二目标侧标识和该通信类型，或该通信类型，该第二目标侧标识用于标识该业务数据。基于此方案，第一终端设备可以通过向网络设备发送该BSR，获取用于发送该业务数据的传输资源。
在一种可能的实现方式中，该第一终端设备向该网络设备发送辅助信息；其中，该辅助信息中包括业务模型信息及该通信类型。基于此方案，第一终端设备可以通过向网络设备发送该辅助信息，获取用于发送该业务数据的传输资源。
在一种可能的实现方式中，该第一终端设备向网络设备发送该服务质量信息；其中，该服务质量信息中包括该第二目标侧标识和该通信类型，或者，包括该通信类型。基于此方案，第一终端设备可以通过向网络设备发送服务质量信息，获取侧行链路无线承载的配置信息。
在一种可能的实现方式中，该第一终端设备接收该网络设备发送的侧行链路无线承载的配置信息；其中，该侧行链路无线承载的配置信息包括与该第二目标侧标识和/或该通信类型对应的侧行链路无线承载配置；该侧行链路无线承载配置包括服务质量 流到侧行链路数据无线承载SL-DRB的映射关系、包数据汇聚协议PDCP配置，无线链路控制RLC配置和逻辑信道LCH配置中的至少一个。基于此方案，第一终端设备可以根据网络设备发送的侧行链路无线承载的配置信息配置侧行链路无线承载。
在一种可能的实现方式中，该第一终端设备向该第二终端设备发送该侧行链路无线承载的配置信息。基于此方案，该第二终端设备可以根据第一终端设备发送的侧行链路无线承载的配置信息获取侧行链路无线承载配置，并根据该侧行链路无线承载配置对接收到的业务数据进行处理。
在一种可能的实现方式中，若该第一终端设备没有与该第二终端设备建立与第二目标侧标识和/或该通信类型对应的第一连接，该第一终端设备建立第一连接；其中，该第一连接为接入层AS连接和/或侧行链路无线承载连接。基于此方案，第一终端设备在建立了与第二终端设备的第一连接后，第二终端设备可以接收对应通信类型的业务数据，以降低第二终端设备的误收包率，进而提高第二终端设备的收包效率。
第二方面，本申请实施例提供一种通信方法，该方法包括：第二终端设备从第一终端设备接收侧行链路控制信息和业务数据；其中，该侧行链路控制信息包括第一目标侧标识和通信类型，或包括通信类型。基于此方案，第二终端设备可以接收对应通信类型的业务数据，以降低第二终端设备的误收包率，进而提高第二终端设备的收包效率。
在一种可能的实现方式中，该第二终端设备根据该侧行链路控制信息包括的通信类型、以及该第二终端设备支持该通信类型的能力，确定接收该业务数据；或者，该第二终端设备根据该侧行链路控制信息包括的该第一目标侧标识和该通信类型、以及该第二终端设备支持的该第一目标侧标识和该通信类型的能力，确定接收该业务数据。基于此方案，第二终端设备可以根据侧行链路控制信息包括的通信类型、以及该第二终端设备支持的通信类型的能力，或者，第二终端设备可以根据侧行链路控制信息包括的第一目标侧标识和通信类型、以及该第二终端设备支持的第一目标侧标识和通信类型的能力，接收对应通信类型的业务数据，以降低第二终端设备的误收包率，进而提高第二终端设备的收包效率。
在一种可能的实现方式中，该第二终端设备从网络设备接收第一配置信息；其中，该第一配置信息中包括第二目标侧标识和该通信类型、以及与该第二目标侧标识和该通信类型对应的第二配置信息，其中，该第二目标侧标识用于标识该业务数据，该第二配置信息包括侧行链路配置信息和/或调度资源，该侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，该调度资源包括与该第二目标侧标识和/或该通信类型对应的传输资源；或者，该第一配置信息中包括该通信类型、以及与该通信类型对应的第二配置信息，其中，该第二目标侧标识用于标识该业务数据，该第二配置信息包括侧行链路配置信息和/或调度资源，该侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，该调度资源包括与该第二目标侧标识和/或该通信类型对应的传输资源；或者，该第一配置信息中包括第二目标侧标识和该通信类型、与该第二目标侧标识和该通信类型对应的第二配置信息、服务质量信息、以及与服务质量信息对应的侧行链路无线承载的配置信息，其中，该第二目标侧标识用于标识该业务数据，该第二配置信息包括侧行链路配置信息和/或调度资源，该侧行链路配置信息用于指示 同步配置、发送方式或传输资源的位置，该调度资源包括与该第二目标侧标识和/或该通信类型对应的传输资源；或者，该第一配置信息中包括该通信类型、与该通信类型对应的第二配置信息、服务质量信息、以及与服务质量信息对应的侧行链路无线承载的配置信息，其中，该第二目标侧标识用于标识该业务数据，该第二配置信息包括侧行链路配置信息和/或调度资源，该侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，该调度资源包括与该第二目标侧标识和/或该通信类型对应的传输资源；或者，该第一配置信息中包括服务质量信息、以及与服务质量信息对应的侧行链路无线承载的配置信息。基于此方案，第二终端设备可以根据网络设备发送的该第二配置信息获取同步配置、发送方式或传输资源的位置，第二终端设备还可以根据网络设备发送的侧行链路无线承载的配置信息获取侧行链路无线承载配置。
在一种可能的实现方式中，该第一配置信息为***信息块、无线资源控制信令、媒介访问控制信令、下行控制信息、非接入层信令或V3接口消息。基于此方案，第二终端设备可以通过***信息块、无线资源控制信令、媒介访问控制信令、下行控制信息、非接入层信令或V3接口消息获取第一配置信息。
在一种可能的实现方式中，该第二终端设备从该第一终端设备接收侧行链路无线承载的配置信息；其中，该侧行链路无线承载的配置信息包括与第二目标侧标识和/或该通信类型对应的侧行链路无线承载配置；该侧行链路无线承载配置包括服务质量流到侧行链路数据无线承载的映射关系、包数据汇聚协议配置，无线链路控制配置和逻辑信道配置中的至少一个。基于此方案，第二终端设备可以根据第一终端设备发送的侧行链路无线承载的配置信息获取侧行链路无线承载配置，并根据该侧行链路无线承载配置对接收到的业务数据进行处理。
在一种可能的实现方式中，若该第二终端设备没有与该第一终端设备建立与第二目标侧标识和/或该通信类型对应的第一连接，该第二终端设备建立第一连接；其中，该第二目标侧标识用于标识所述业务数据该第一连接为接入层AS连接和/或侧行链路无线承载侧行链路无线承载连接。基于此方案，第二终端设备可以在与第一终端设备建立第一连接后，接收对应通信类型的业务数据，以降低第二终端设备的误收包率，进而提高第二终端设备的收包效率。
第三方面，本申请提供了一种通信方法，该方法包括：网络设备向第一终端设备和/或第二终端设备发送第一配置信息，其中，该第一配置信息中包括第二目标侧标识和该通信类型、以及与该第二目标侧标识和该通信类型对应的第二配置信息，其中，所述第二目标侧标识用于标识业务数据，所述第二配置信息包括侧行链路配置信息和/或调度资源，所述侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，所述调度资源包括与第二目标侧标识和/或通信类型对应的传输资源；或者，该第一配置信息中包括该通信类型、以及与该通信类型对应的第二配置信息，其中，所述第二目标侧标识用于标识业务数据，所述第二配置信息包括侧行链路配置信息和/或调度资源，所述侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，所述调度资源包括与第二目标侧标识和/或通信类型对应的传输资源；或者，该第一配置信息中包括第二目标侧标识和该通信类型、与该第二目标侧标识和该通信类型对应的第二配置信息、服务质量信息、以及与服务质量信息对应的侧行链路无线承载的配置信息， 其中，所述第二目标侧标识用于标识业务数据，所述第二配置信息包括侧行链路配置信息和/或调度资源，所述侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，所述调度资源包括与第二目标侧标识和/或通信类型对应的传输资源；或者，该第一配置信息中包括该通信类型、与该通信类型对应的第二配置信息、服务质量信息、以及与服务质量信息对应的侧行链路无线承载的配置信息，其中，所述第二目标侧标识用于标识业务数据，所述第二配置信息包括侧行链路配置信息和/或调度资源，所述侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，所述调度资源包括与第二目标侧标识和/或通信类型对应的传输资源；或者，该第一配置信息中包括服务质量信息、以及与服务质量信息对应的侧行链路无线承载侧行链路无线承载的配置信息。基于此方案，第一终端设备和/或第二终端设备可以根据网络设备发送的该第二配置信息获取同步配置、发送方式或传输资源的位置，第一终端设备和/或第二终端设备还可以根据网络设备发送的侧行链路无线承载的配置信息获取侧行链路无线承载配置。
在一种可能的实现方式中，该第一配置信息为***信息块、无线资源控制信令、媒介访问控制信令、下行控制信息、非接入层信令或V3接口消息。基于此方案，网络设备可以通过***信息块、无线资源控制信令、媒介访问控制信令、下行控制信息、非接入层信令或V3接口消息向第一终端设备和/或第二终端设备发送该第一配置信息。
在一种可能的实现方式中，该网络设备从该第一终端设备接收业务信息；其中，该业务信息包括：该通信类型。基于此方案，网络设备可以根据第一终端设备发送的业务信息为第一终端设备分配传输资源。
在一种可能的实现方式中，该网络设备从该第一终端设备接收缓存状态报告；其中，该缓存状态报告中包括第二目标侧标识和该通信类型，或该通信类型。基于此方案，网络设备可以根据第一终端设备发送的BSR为第一终端设备分配传输资源。
在一种可能的实现方式中，该网络设备接收该第一终端设备发送的辅助信息；其中，该辅助信息中包括业务模型及该通信类型。基于此方案，网络设备可以根据第一终端设备发送的辅助信息为第一终端设备分配传输资源。
在一种可能的实现方式中，网络设备从该第一终端设备接收服务质量信息；其中，该服务质量信息中包括该第二目标侧标识和该通信类型，或者，包括该通信类型。基于此方案，网络设备可以根据第一终端设备发送的服务质量信息获取业务数据的通信类型。
在一种可能的实现方式中，网络设备根据该服务质量信息，向该第一终端设备发送侧行链路无线承载的配置信息；其中，该侧行链路无线承载的配置信息包括与该第二目标侧标识和/或该通信类型对应的侧行链路无线承载配置；该侧行链路无线承载配置包括服务质量流到侧行链路数据无线承载SL-DRB的映射关系、包数据汇聚协议PDCP配置，无线链路控制RLC配置、逻辑信道LCH配置中的至少一个。基于此方案，网络设备可以根据第一终端设备发送的服务质量信息向第一终端设备发送侧行链路无线承载的配置信息。
第四方面，本申请实施例提供了一种第一终端设备，该第一终端设备具有实现上述第一方面所述的方法和功能。该功能可以通过硬件实现，也可以通过硬件执行相应 的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第五方面，本申请实施例提供了一种第二终端设备，该第二终端设备具有实现上述第二方面所述的方法和功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第六方面，本申请实施例提供了一种网络设备，该网络设备具有实现上述第三方面所述的方法和功能。该功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
第七方面，本申请提供了一种通信装置，该通信装置可以包括：至少一个处理器，涉及的程序指令在该至少一个处理器中执行，以实现根据第一方面的方法及其任一设计中的第一终端设备的功能。可选的，该通信装置还可以包括至少一个存储器，该存储器存储有涉及的程序指令。该通信装置可以是第一方面的方法及其任一设计中的第一终端设备。
第八方面，本申请提供了一种通信装置，该通信装置可以包括：至少一个处理器，涉及的程序指令在该至少一个处理器中执行，以实现根据第二方面的方法及其任一设计中的第二终端设备的功能。可选的，该通信装置还可以包括至少一个存储器，该存储器存储有涉及的程序指令。该通信装置可以是第二方面的方法及其任一设计中的第二终端设备。
第九方面，本申请提供了一种通信装置，该通信装置可以包括：至少一个处理器，涉及的程序指令在该至少一个处理器中执行，以实现根据第三方面的方法及其任一设计中的网络设备的功能。可选的，该通信装置还可以包括至少一个存储器，该存储器存储有涉及的程序指令。该通信装置可以是第三方面的方法及其任一设计中的网络设备。
第十方面，本申请提供了一种***芯片，该***芯片可以应用在通信装置中，该***芯片包括：至少一个处理器，涉及的程序指令在该至少一个处理器中执行，以实现根据第一方面的方法及其任一设计中的第一终端设备的功能；或者，实现根据第二方面的方法及其任一设计中的第二终端设备的功能；或者，实现根据第三方面的方法及其任一设计中的网络设备的功能。可选的，该***芯片还可以包括至少一个存储器，该存储器存储有涉及的程序指令。
第十一方面，本申请提供了一种计算机存储介质，该计算机存储介质可以应用在通信装置中，该计算机可读存储介质中存储有程序指令，涉及的程序指令运行时，以实现根据第一方面的方法及其任一设计中的第一终端设备的功能；或者，实现根据第二方面的方法及其任一设计中的第二终端设备的功能；或者，实现根据第三方面的方法及其任一设计中的网络设备的功能。
第十二方面，本申请提供了一种计算机程序产品，该计算机程序产品包含程序指令，涉及的程序指令被执行时，以实现根据第一方面的方法及其任一设计中第一终端设备的功能；或者，实现根据第二方面的方法及其任一设计中的第二终端设备的功能；或者，实现根据第三方面的方法及其任一设计中的网络设备的功能。
第十三方面，本申请提供了一种通信***，该***可以包括如下任一种或任几种：如第四方面中的第一终端设备，或者如第五方面中的第二终端设备，或者如第六方面 中的网络设备，或者如第七方面、第八方面或第九方面中的通信装置，或者如第十方面中的***芯片，或者如第十一方面中的计算机存储介质，或者如第十二方面中的计算机程序产品。
可以理解的，上述提供的任一种装置、***芯片、计算机存储介质、计算机程序产品或通信***等均用于执行上文所提供的对应的方法，因此，其所能达到的有益效果可参考对应的方法中的有益效果，此处不再赘述。
附图说明
图1为本申请实施例提供的一种原理框图；
图2为本申请实施例提供的一种***架构示意图；
图3a为本申请实施例提供的单播通信示意图；
图3b为本申请实施例提供的组播通信示意图；
图3c为本申请实施例提供的广播通信示意图；
图4为本申请实施例提供的协议栈示意图；
图5为本申请实施例提供的一种通信装置的组成示意图；
图6为本申请实施例提供的通信方法的流程示意图一；
图7为本申请实施例提供的通信方法的流程示意图二；
图8为本申请实施例提供的通信方法的流程示意图三；
图9为本申请实施例提供的通信方法的流程示意图四；
图10为本申请实施例提供的通信方法的流程示意图五；
图11为本申请实施例提供的通信方法的流程示意图六；
图12为本申请实施例提供的通信方法的流程示意图七；
图13为本申请实施例提供的通信方法的流程示意图八；
图14为本申请实施例提供的通信方法的流程示意图九；
图15为本申请实施例提供的第一终端设备的结构示意图一；
图16为本申请实施例提供的第一终端设备的结构示意图二；
图17为本申请实施例提供的第一终端设备的结构示意图三；
图18为本申请实施例提供的第一终端设备的结构示意图四；
图19为本申请实施例提供的第一终端设备的结构示意图五；
图20为本申请实施例提供的第二终端设备的结构示意图一；
图21为本申请实施例提供的第二终端设备的结构示意图二；
图22为本申请实施例提供的第二终端设备的结构示意图三；
图23为本申请实施例提供的网络设备的结构示意图一；
图24为本申请实施例提供的网络设备的结构示意图二。
具体实施方式
首先，结合图1介绍本申请实施例的原理。如图1所示，发端设备与收端设备传输数据的过程，可以包括：当发端设备的应用层实体产生某类V2X业务对应的数据包，并向下层实体递交时，该数据包可能携带用于标识该类V2X业务的第二目标侧标识(如：目的层2标识(destination layer-2 id))和/或通信类型等信息，发端设备的下层实体可以根据第二目标侧标识和/或通信类型等信息与侧行链路的无线承载(sidelink  radio barrier，SLRB)组(简称SLRBs)的映射关系，将数据包递交给发送设备中与第二目标侧标识和/或通信类型等信息对应的SLRB；发送设备中的SLRB对接收到数据包进行处理，并将处理后的数据递交给发送设备的媒体接入控制(media access control，MAC)层实体；发送设备的MAC层实体对经过SLRB处理的数据包进行处理，生成包括第二目标侧标识和/或通信类型，以及侧行链路逻辑信道(sidelink logical channel，SL LCH)的逻辑信道标识(logical channel identity，LCID)的MAC协议数据单元(protocol data unit，PDU)，并将MAC PDU递交给发送设备的物理层(physical layer，PHY)实体；发送设备的PHY层实体将MAC PDU通过发端设备与收端设备之间的直连通道(如：PC5口)发送给收端设备。发端设备在PHY层实体向收端设备发送该MAC PDU时，可以向收端设备发送该MAC PDU对应的侧行链路控制信息(sidelink control information，SCI)，该SCI可以包括该MAC PDU对应的第一目标侧标识(如：目的层1标识(destination layer-1id))和/或通信类型。后续，收端设备接收并解析该SCI后，收端设备可以根据该SCI包括的第一目标侧标识和/或通信类型确定是否接收该MAC PDU；或者，收端设备的PHY层实体在接收到该MAC PDU后，可以根据该MAC PDU中携带的第二目标侧标识和/或通信类型确定是否将该MAC PDU中包含的MAC业务数据单元(service data unit，SDU)递交给收端设备中与该类V2X业务对应的SLRB进行处理。
在一种可能的实现方式中，收端设备可以根据该SCI包括的第一目标侧标识和/或通信类型确定是否接收该MAC PDU，包括：若该SCI包括的第一目标侧标识和/或通信类型是收端设备自身支持的第一目标侧标识和/或通信类型，收端设备接收该MAC PDU；若该SCI包括的第一目标侧标识和/或通信类型不是收端设备自身支持的第一目标侧标识和/或通信类型，收端设备不接收该MAC PDU。
在一种可能的实现方式中，收端设备的PHY层实体在接收到该MAC PDU后，可以根据该MAC PDU中携带的第二目标侧标识和/或通信类型确定是否将该MAC PDU中包含的MAC SDU递交给收端设备中与该类V2X业务对应的SLRB进行处理，包括：收端设备的PHY层实体在接收到该MAC PDU后，可以将该MAC PDU递交给MAC实体，若该MAC PDU中携带的第二目标侧标识和/或通信类型是收端设备MAC实体支持的第二目标侧标识和/或通信类型，收端设备将该MAC PDU中包含的MAC SDU递交给收端设备中与该类V2X业务对应的SLRB进行处理；若该MAC PDU中携带的第二目标侧标识和/或通信类型不是收端设备MAC实体支持的第二目标侧标识和/或通信类型，收端设备丢弃该MAC SDU。
可选的，在本申请实施例中，该第一目标侧标识和/或通信类型、该第二目标侧标识和/或通信类型还可以是以下信息中的一种或多种：公共陆地移动网络(public land mobile network，PLMN)标识信息、侧行链路/Uu口通信信息、侧行链路/Uu接口信息、载波/频点标识信息、网络设备/小区/核心网网元标识信息、服务标识信息、终端设备标识信息、服务质量(quality of service，QoS)标识信息、单播连接中的连接标识信息、组播连接中的组标识信息、单播\组播\广播中的业务标识信息、通信模式标识信息、部分带宽(band with part，BWP)标识信息、逻辑信道组(logical channel group，LCG)标识信息、LCH标识信息、SLRB标识信息、通信源标识信息、通信目标标识信息、 混合自动重传请求(hybridautomatic repeat request，HARQ)进程(process)标识信息。本申请实施例仅以该第一目标侧标识和/或通信类型、该第二目标侧标识和/或通信类型为例进行说明，对于其他类型的信息，可以借鉴本申请实施例提供的通信方法通信。
其中，PLMN标识信息用于标识PLMN；侧行链路/Uu口通信***信息用于标识侧行链路/Uu链路的所在的通信***(例如：LTE***、NR***或下一代通信***)；侧行链路/Uu接口信息用于标识侧行链路/Uu接口；载波/频点标识信息用于标识载波/频点；网络设备/小区/核心网网元标识信息用于标识网络设备/小区/核心网网元；服务标识信息(例如：service id)用于用于标识业务信息，以便网络设备可以根据该服务标识信息为发端设备配置参数、配置资源池或发送调度信息等；终端设备标识信息可以是终端设备自身的一个或多个标识，或该终端设备作为代理终端设备发送组播中通属于一个组的其他终端设备的标识(例如：终端设备的IP地址、终端设备的MAC地址、终端设备的侧行链路层2标识、终端设备的侧行链路层2地址、终端设备的侧行链路层1标识、终端设备的侧行链路层1地址、用户业务标识(C-RNTI)、寻呼标识(P-RNTI)、用于识别半静态调度/配置资源/免调度的终端设备的标识(CS-RNTI)、用户发随机接入前导所使用的资源块标识(RA-RNTI)、国际移动用户识别码(international mobile subscriber identification number，IMSI)、临时移动用户标识(temporary mobile subscriber identity，TMSI)等)；QoS标识信息可以包括第五代(5th generation，5G)服务质量标识(5G QoS identifier，5QI)、服务质量流标识(QoS flow identifier，QFI)、近距通信数据包优先级(prose per packet priority，PPPP)、近距通信数据包可靠性(prose per packet reliability，PPPR)、QoS流标识、车通信服务质量标识(vechical QoS identifier，VQI)标识或PC5接口的服务质量标识(PC5 QoS identifier，PQI)；单播连接中的连接标识信息用于标识单播连接中的连接(如：connection id)；组播连接中的组标识信息用于标识组播连接中的组(如：group connection id、group Uu/SL L1/L2 Id、group Id)；单播\组播\广播中的业务标识信息用于标识单播\组播\广播中的业务；通信模式标识信息用于标识通信模式(如：网络设备调度模式或者终端设备竞争模式)；部分带宽(band with part，BWP)标识信息用于标识BWP；LCG标识信息用于标识LCG；LCH标识信息用于标识LCH；SLRB标识信息用于标识SLRB；通信源标识信息用于标识通信源(如：source Uu/SL id或source L2/L1 id)；通信目标标识信息用于标识通信目标(如：destination Uu/SL id或destination L2/L1 id)、HARQ进程标识信息用于标识HARQ process(如：HARQ process id)。
可选的，本申请实施例中，发送设备与接收设备为相对概念，发送设备可以指发送数据包的设备，接收设备可以指接收数据包的设备。
可选的，在本申请实施例中，通信类型除单播通信、组播通信或广播通信外，还可以为其他类型的通信。本申请实施例仅以单播通信、组播通信、广播通信为例进行说明，对于其他类型的通信可以借鉴本申请实施例提供的通信方法通信。
可选的，若收端设备与发端设备通过单播/组播/广播通信，收端设备的应用层(APP layer)实体和/或V2X层实体可以向收端设备的接入层(access stratum，AS)实体发送通知消息，该通知消息可以包括该单播/组播/广播连接的对应的第二源侧标识(例如：发端设备的Source Layer-2 Id)、第二目标侧标识和通信类型，以便该收端设备的AS 实体进行数据包过滤。
示例性的，若发端设备与收端设备通过单播通信，发端设备的应用层实体和收端设备的应用层实体建立单播连接，收端设备的应用层实体向收端设备的接入层实体发送通知消息，该通知消息包括该单播连接对应的第二源侧标识、第二目标侧标识和通信类型，收端设备可以接收与该第二源侧标识、该第二目标侧标识和该通信类型相同的业务数据。
示例性的，若发端设备与收端设备通过组播通信，收端设备加入该组时，收端设备的应用层实体和/或V2X层实体可以向收端设备的接入层实体发送通知消息，该通知消息包括该组接对应的第二源侧标识、第二目标侧标识和通信类型，收端设备可以接收与该第二源侧标识、该第二目标侧标识和该通信类型相同的业务数据。
示例性的，若发端设备与收端设备通过广播通信，收端设备的应用层实体向收端设备的接入层实体发送通知消息，该通知消息包括该广播通信对应的第二源侧标识、第二目标侧标识和通信类型，收端设备可以接收与该第二源侧标识、该第二目标侧标识和该通信类型相同的业务数据。
可选的，侧行链路的无线承载组可以称为SLRB组或者或者SLRBs或者无线承载组或者RB组，下面以侧行链路的无线承载组为SLRB组或SLRBs为例对本申请实施例提供的通信方法进行介绍。
首先，为了便于理解本申请实施例，对本申请实施例涉及的一些名词进行描述：
SLRBs：可以包括一个或多个独立的无线承载，无线承载可以称为SLRB。其中，该一个或多个独立的无线承载可以是侧行链路的信令无线承载(sidelink signaling radio bearers，SL-SRB)或侧行链路的数据无线承载(sidelink data radio bearers，SL-DRB)。每个SLRB对应一个包数据汇聚协议(packet data convergence protocol，PDCP)层实体、一个或多个无线链路控制(radio link control，RLC)层实体、一个或多个LCH等，或者，可以描述为每个SLRB包括一个PDCP层实体、一个或多个RLC层实体以及一个或多个LCH等。本申请实施例中，每个SLRB采用一套独立的配置，每个SLRB的配置根据该SLRBs对应的第二目标侧标识和/或通信类型的不同而不同。SLRBs的配置信息可以包括SLRBs中各个SLRB的配置，SLRB的配置可以包括：SLRB标识、PDCP实体配置、RLC实体配置、LCH配置等。示例性的，SLRB标识可以用于标识SLRB，可以为SLRB的索引号。同一SLRBs包括的SLRB的配置可以是相同或不同的。比如一个SLRB组包括8个SLRB，这8个SLRB对应的LCH的ID可以各不相同。若该SLRB是SL-DRB，该SLRB的配置信息还可以包括：QoS流到SL-DRB的映射关系信息。其中，每个QoS流可以有相同的QoS参数，该QoS参数可以是5G服务质量标识(5G QoS identifier，5QI)或者服务质量流标识(QoS flow identifier，QFI)或者V2X服务质量标识(V2X QoS identifier，VQI)，或者其他能够反映业务可靠性、时延、优先级、传输速率等的QoS参数。
PDCP实体配置：针对于PDCP层实体的配置，PDCP实体配置可以包括但不限于下述任一种或者多种配置参数：用于控制一个PDCP SDU在PDCP缓存中可存储时间的定时器的定时时长(discardTimer)、用于在重排序功能中等待乱序数据包的定时器的定时时长(t-Reordering)、PDCP层是否可以向上层乱序递交数据包、PDCP层是否 采用侧行链路数据压缩，以及侧行链路数据压缩的相关配置信息、PDCP层PDU采用的序列号(sequence number，SN)长度、PDCP层实体采用的安全配置(包括是否采用加密和/或完整性保护)、PDCP层实体采用的安全算法(完整性保护算法和加密算法)和/或密钥等、PDCP层实体是否采用复制(duplication)机制以及复制的配置(如果采用复制机制，则该PDCP实体可以对应两个或多个RLC实体和LCH)、PDCP层头压缩算法的相关配置(例如：是否采取头压缩等)等。示例性的，侧行链路(sidelink)数据压缩的相关配置信息可以包括压缩缓存(buffer)的大小，压缩采用的字典等；上述复制(duplication)机制是指PDCP实体对PDCP PDU进行复制，并递交到关联的两个/多个RLC实体进行处理和传输的机制。
RLC实体配置：针对于RLC层实体的配置，RLC实体配置可以包括但不限于下述任一种或者多种配置参数：RLC层实体采用的模式：透明模式(transparent mode，TM)/非确认模式(unacknowledged mode，UM)/确认模式(acknowledged mode，AM)；如果RLC层实体被配置采用AM模式，RLC实体配置还包括以下至少一项或者多项：RLC层PDU的SN长度、控制发起poll重传的定时器的定时时长(t-PollRetransmit)、控制发送多少个RLC PDU后需要发起poll的参数(poll PDU)、控制发送多少字节的RLC PDU后需要发起poll的参数(poll Byte)、RLC层最大重传次数(maxRetxThreshold)。示例性的，poll可以指发送设备中的RLC层实体通过MAC PDU中的poll bit指示接收设备中的采用AM模式的RLC层实体进行状态报告反馈。如果RLC层实体被配置采用UM模式，RLC实体配置还包括以下至少一项：RLC层PDU的SN长度。如果接收RLC实体被配置为采用AM模式，RLC配置还包括以下至少一项或者多项：RLC层PDU的SN长度，控制RLC层等待分段的定时器的定时时长(t-Reassembly)，或者，控制RLC层避免频繁发送状态报告的定时器的定时时长(t-StatusProhibit)。如果接收RLC实体被配置为采用UM模式，RLC实体配置还包括：RLC层PDU的SN长度，和/或，控制RLC层等待分段的定时器的定时时长(t-Reassembly)。
LCH配置：针对于LCH的配置，可以包括但不限于下述任一种或者多种配置参数：LCH标识、LCH所属逻辑信道组的标识、进行逻辑信道优先级处理的相关参数(优先级(priority)，优先比特速率(prioritisedBitRate，PBR)以及令牌桶大小持续时间(bucket size duration，BSD)等)、可以用于传输该LCH中数据的载波信息、可以用于传输该LCH中的数据的资源模式(mode)信息(例如，模式1(mode 1)或者模式2(mode 2)，其中，模式1对应基站调度资源方式，模式2对应终端设备自身选择资源的调度方式)、可以用于传输该LCH中数据的资源的参数集(numerology)信息(如子载波间隔，循环前缀长度，资源时域持续时间、是否可以是配置授权资源等参数中的一个或多个)、控制该LCH是否可以触发调度请求(scheduling request，SR)的参数(SR-mask)、控制该LCH是否可以延迟触发SR的参数(SR-DelayTimerApplied)等。示例性的，LCH标识为LCH的索引号，可以用于标识LCH，LCH所属逻辑信道组的标识可以为LCH所属逻辑信道组的索引号，可以用于标识LCH所属逻辑信道组。
应用层实体：为设备中的一个协议层实体，可以称为应用层或者应用实体，主要用于生成应用(application，APP)消息或者V2X业务对应的数据包等。
非接入(non-access stratum，NAS)层实体：为设备中的一个协议层实体，可以 称为NAS层或者NAS实体，主要用于处理终端和核心网设备间信息的传输，传输的内容可以是用户信息或控制信息(如业务的建立、释放或者移动性管理信息)，NAS实体具有如下功能如下：会话管理(包括会话建立、修改、释放及QoS协商)、用户管理(包括用户数据管理以及附着、去附着等)安全管理(包括用户与网络之间的鉴权及加密初始化)以及计费等。
RRC层实体：为设备中的一个协议层实体，主要负责生成RRC消息、测量配置和上报，还可以负责其他功能：如发送专用的NAS消息、传输终端(user equipment，UE)接入能力信息等体现数据包/数据流服务质量的参数。
服务数据适配层(service data adaptation protocol，SDAP)层实体：为设备中的一个协议层实体，可以称为SDAP层或者SDAP实体，主要用于维护QoS参数与SLRB间的映射关系。示例性的，QoS参数可以为第五代(5th generation，5G)服务质量标识(5G QoS identifier，5QI)或者服务质量流标识(QoS flow identifier，QFI)或者近距通信数据包优先级(prose per packet priority，PPPP)或者近距通信数据包可靠性(prose per packet reliability，PPPR)等。
PDCP层实体：为设备中的一个协议层实体，可以称为PDCP层或者PDCP实体，主要对来自控制面的RRC消息和来自数据面的因特网协议(internet protocol，IP)包进行处理，其功能包括：头部压缩和解压缩、加密/解密、完整性保护、传输用户数据和控制面数据、重排序和重传处理等。每个PDCP层实体都有1个或2个对应的RLC层实体。
RLC层实体：为设备中的一个协议层实体，可以称为RLC层或者RLC实体，主要负责分段/级联和重组RLC业务数据单元(service data unit，SDU)、通过自动重传请求(automatic repeat request，ARQ)来进行纠错、对RLC协议数据单元(protocol data unit，PDU)进行重排序、重复包检测、对RLC PDU进行重分段等。
MAC层实体：为设备中的一个协议层实体，可以称为MAC层或者MAC实体，主要负责匹配逻辑信道和传输信道、将属于一个或不同的逻辑信道的多个MAC SDU复用到同一个MAC PDU上，并递交给PHY(physical)层实体、通过混合自动重传请求(hybrid automatic repeat request，HARQ)来进行纠错、调度处理、逻辑信道优先级处理、调度信息上报、随机接入过程处理等。
PHY层实体：为设备中的一个协议层实体，可以称为PHY层实体或者PHY实体，可以为传输数据所需要的物理链路创建、维持、拆除，而提供具有机械的，电子的，功能的和规范的特性。简单的说，PHY层实体确保原始的数据可在各种物理媒体上传输。
下面结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。
本申请实施例提供的通信方法可用于设备与设备间直连通信的任何通信***，如：可以适用于设备到设备(device to device，D2D)通信***或者机器对机器(machine to machine，M2M)通信***或者V2X通信***等。下面以V2X通信***为例对本申请实施例提供的通信方法进行说明，该通信方法在其他通信***的实现过程可参照本申请实施例所述。
图2为本申请实施例提供的一种V2X通信***，如图2所示，该V2X通信*** 可以包括：多个车辆(如图2所示的车辆1、车辆2、车辆3……)。车辆与周围车辆之间可以进行建立直连通信链路，实现直连通信，如：车辆1与车辆2之间可以直连通信。示例性的，车辆与车辆间建立的直连通信链路可以被定义为侧行链路或者侧链(sidelink，SL)，车辆与周围车辆直连通信的接口可以称为PC5口。图2所示V2X通信***还可以包括无线接入网设备。车辆可以采用无线接入网设备中转的方式向对端车辆发送V2X消息或者通过无线接入网设备接入网络，如：车辆1可以将V2X消息发送给无线接入网设备，由无线接入网设备将V2X消息发送给车辆2。示例性的，车辆与无线接入网设备之间的接口可以称为Uu接口。可选的，图2所示网络架构仅为示例性架构图，本申请实施例不限定图2所示V2X通信***包括的网元的数量。此外，虽然未示出，但除图2所示网络功能实体外，图2所示网络还可以包括其他功能实体，如：应用服务器(application server)、核心网设备等，不予限制。
示例性的，图2中的车辆不限定于为汽车、自行车、电动车、飞机、船舶、火车、高铁等任一类型的车辆，该车辆可以包括能够与其他设备直连通信的车载设备，该车载设备可以称为用户设备(user equipment，UE)或者终端设备(terminal)。该车辆可以与V2X通信***中的其他车辆一对一连接，即单播通信，也可以与V2X通信***中的其他多个车辆进行组播通信，还可以与V2X通信***中其他多个车辆进行广播通信。例如，图3a为本申请实施例提供的单播通信的示意图，如图3a所示，车辆1可以与车辆2一对一连接进行单播通信。图3b为本申请实施例提供的组播通信的示意图，如图3b所示，车辆1可以与其他三个车辆(车辆2、车辆3、车辆4)为一个通信组，该通信组内车辆进行组播通信。图3c为本申请实施例提供的广播通信的示意图，如图3c所示，车辆1可向其他三个车辆(车辆2、车辆3、车辆4)广播数据。本申请实施例中，以车辆为终端设备为例进行描述，用于实现终端设备的功能的装置可以是终端设备本身，也可以是能够支持终端设备实现该功能的装置，例如芯片***。本申请实施例中，芯片***可以由芯片构成，也可以包括芯片和其他分立器件。
图2中的无线接入网设备主要用于实现无线物理控制功能、资源调度和无线资源管理、无线接入控制以及移动性管理等功能。该无线接入网设备可以为接入网(access network，AN)/无线接入网(radio access network，RAN)设备，还可以为由多个5G-AN/5G-RAN节点组成的设备，又可以为者基站(nodeB，NB)、演进型基站(evolution nodeB，eNB)、下一代基站(generation nodeB，gNB)、收发点(transmission receive point，TRP)、传输点(transmission point，TP)以及某种其它接入节点中的任一节点。本申请实施例中，用于实现无线接入网设备的功能的装置可以是无线接入网设备，也可以是能够支持无线接入网设备实现该功能的装置，例如芯片***。在本申请实施例提供的技术方案中，以用于实现无线接入网设备的功能的装置是无线接入网设备为例描述本申请实施例提供的技术方案。
示例性的，图2所示各车辆可以包括图4所示协议层实体：应用层实体、非接入(non-access stratum，NAS)层实体、无线资源控制(radio resource control，RRC)层实体、包数据汇聚协议(packet data convergence protocol，PDCP)层实体、无线链路控制(radio link control，RLC)层实体、MAC层实体、PHY层实体，还可以包括SDAP层实体、V2X层实体或者其他新增的协议层实体(图4中未示出)等，各协议层实体 的相关功能介绍和配置如前所述，不再赘述。其中MAC层实体、RLC层实体以及PDCP层实体三个实体可以组成数据链路实体，称为层2(layer2，L2)。车辆可以通过图4所示协议层实体对传输的信令消息或者数据包进行处理。例如，以图4所示的车辆1和车辆2间传输数据包为例，车辆1、车辆2的RRC层实体可以对组播通信、单播通信、广播通信分别建立对应的SLRBs，并维护单播通信/组播通信/广播通信与SLRBs的对应关系。当车辆1向车辆2发送组播通信对应的数据包时，车辆1可以根据该对应关系将该数据包递交给组播通信对应的SLRBs进行处理，并将处理后的数据包通过PC5口发送给车辆2，车辆2的MAC层实体接收到数据包后，递交给车辆2中组播通信对应的SLRBs进行处理。车辆1向车辆2发送单播通信对应的数据包过程、车辆1向车辆2广播对应的数据包过程与此类似，不再赘述。相对应的，作为车辆1向车辆2发送数据包的逆过程，当车辆2向车辆1发送数据包时，车辆2可以根据单播通信/组播通信/广播通信与SLRBs的对应关系将该数据包递交给单播通信/组播通信/广播通信对应的SLRBs进行处理，并将处理后的数据包通过PC5口发送给车辆1，车辆1的MAC层实体接收到数据包后，递交给车辆1中单播通信/组播通信对应的SLRBs进行处理。
可选的，上述图2架构中的网元、各个网元之间的接口名字以及各个协议层实体的命名只是一个示例，具体实现中网元、网元之间的接口名字以及协议层实体还可以为其他名字，本申请实施例对此不作具体限定。
示例性的，图2中的车辆可以看做为图5所示通信装置或者包括图5所示通信装置。图5为本申请实施例提供的一种通信装置500的组成示意图，该通信装置可以用于实现本申请实施例提供的通信方法。如图5所示，该通信装置500包括至少一个处理器501、通信线路502以及至少一个通信接口503；进一步的，还可以包括存储器504。示例性的，处理器501，存储器504以及通信接口503三者之间可以通过通信线路502连接。在本申请实施例中，至少一个可以是一个、两个、三个或者更多个，本申请实施例不做限制。
在本申请实施例中，处理器501可以是中央处理器(central processing unit，CPU)，通用处理器网络处理器(network processor，NP)、数字信号处理器(digital signal processing，DSP)、微处理器、微控制器、可编程逻辑器件(programmable logic device，PLD)或它们的任意组合。处理器还可以是其它任意具有处理功能的装置，例如电路、器件或软件模块。
在本申请实施例中，通信线路502可包括通路，用于在通信装置包括的部件之间传送信息。
在本申请实施例中，通信接口503用于与其他车辆或通信网络通信(如以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)等)。通信接口503可以是模块、电路、收发器或者任何能够实现通信的装置。
在本申请实施例中，存储器504可以是只读存储器(read-only memory，ROM)或可存储静态信息和/或指令的其他类型的静态存储设备，也可以是随机存取存储器(random access memory，RAM)或者可存储信息和/或指令的其他类型的动态存储设 备，还可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。
一种可能的设计中，存储器504可以独立于处理器501存在，即存储器504可以为处理器501外部的存储器，此时，存储器504可以通过通信线路502与处理器501相连接，用于存储指令或者程序代码。处理器501调用并执行存储器504中存储的指令或程序代码时，能够实现本申请下述实施例提供的通信方法。又一种可能的设计中，存储器504也可以和处理器501集成在一起，即存储器504可以为处理器501的内部存储器，例如，该存储器504为高速缓存，可以用于暂存一些数据和/或指令信息等。
作为一种可实现方式，处理器501可以包括一个或多个CPU，例如图5中的CPU0和CPU1。作为另一种可实现方式，通信装置500可以包括多个处理器，例如图5中的处理器501和处理器507。作为再一种可实现方式，通信装置500还可以包括输出设备505和输入设备506。示例性地，输入设备506可以是麦克风或操作杆等设备，输出设备505可以是显示屏、扬声器(speaker)等设备。
下面结合图2～图4，对本申请实施例提供的通信方法进行具体阐述。可选的，本申请下述实施例中各个网元之间的消息名字或消息中各参数的名字等只是一个示例，具体实现中也可以是其他的名字，本申请实施例对此不作具体限定。
可以理解的，本申请实施例中，终端设备和/或网络设备可以执行本申请实施例中的部分或全部操作，这些操作或操作仅是示例，本申请实施例还可以执行其它操作或者各种操作的变形。此外，各个操作可以按照本申请实施例呈现的不同的顺序来执行，并且有可能并非要执行本申请实施例中的全部操作。
图6为本申请实施例提供的一种通信方法的流程图，如图6所示，该方法可以包括步骤601-602。
步骤601、第一终端设备向第二终端设备发送SCI。
示例性的，第一终端设备可以为图2所示V2X***中的任一车辆，可以与其他车辆建立图3a所示的单播通信、图3b所示的组播通信或者图3c所示的广播通信。第一终端设备可以包括图4所示的协议层实体。
可选的，第一终端设备向第二终端设备发送业务数据时，第一终端设备的PHY实体生成与该业务数据对应的SCI，并向第二终端设备发送该SCI，该SCI可以包括：第一目标侧标识和通信类型，或者，该SCI可以包括通信类型，或者，该SCI可以包括第一源侧标识、第一目标侧标识和通信类型。
其中，该第一源侧标识可以是第一终端设备的源层1标识，例如，该第一源侧标识可以是第一终端设备的Source layer1 Id。
其中，该第一目标侧标识可以是目的层1标识，例如：destination layer-1 id。
其中，在本申请各实施例中，通信类型可以为图3a所示的单播通信、图3b所示的组播通信或图3c所示的广播通信。本申请各实施例中，通信类型可以为二进制比特数“00”、“01”或“10”，用于指示第一终端设备所要执行的通信类型，如：可以用“00” 指示单播通信，用“01”指示组播通信，用“10”指示广播通信。
可选的，第一终端设备根据第二目标侧标识和通信类型确定该业务数据。其中，该第二目标侧标识可以用于标识该业务数据。该第二目标侧标识和该第一目标侧标识存在对应关系，例如：该第一目标侧标识可以是该第二目标侧标识的低8位。
可选的，该第二目标侧标识可以是target_id、group_id或者service_id。第二目标侧标识可以由发起单播通信、组播通信或广播通信的头车的应用层实体分配或者由发起单播通信、组播通信或广播通信的头车的其他协议层实体(如：NAS层实体)分配，不同通信类型分配的第二目标侧标识是不同的；本申请实施例中，发起单播通信、组播通信或广播通信的头车可以为第一终端设备。
可选的，若通信类型为单播通信，该第二目标侧标识是target_id。例如，假设车辆1为发起单播通信的头车，且车辆1与车辆2组成单播通信，则对于车辆1而言，该单播通信对应的第二目标侧标识可以为车辆1的应用层实体分配的target_id1。
可选的，若通信类型为组播通信，该第二目标侧标识是group_id。例如，假设车辆1为发起组播通信的头车，且车辆1与车辆2、车辆3、车辆4组播通信，则对于车辆1与车辆2而言，该组播通信对应的第二目标侧标识可以为车辆1的应用层实体分配的group_id1，对于车辆1、车辆3和车辆4而言，该组播通信对应的第二目标侧标识可以为车辆1的应用层实体分配的group_id2。
可选的，若通信类型为广播通信，该第二目标侧标识是service_id。例如，假设车辆1发起广播通信，则对于车辆1而言，该广播通信对应的第二目标侧标识可以为通信***(例如：3GPP通信***)分配的service_id1。
需要说明的是，第一终端设备的应用层实体产生第二目标侧标识和通信类型不同的一个或多个数据包，第一终端设备获取第一LCH，该第一LCH是每个第二目标侧标识和通信类型相同的数据包对应的LCH中，优先级最高的LCH，对于该一个或多个第一LCH，第一终端设备确定该业务数据包括该一个或多个第一LCH中，优先级最高的第一LCH对应的数据包。
例如，表1示出了第一终端设备的应用层实体产生的多个数据包对应的第二目标侧标识、通信类型和优先级。第二目标侧标识为target_id1，通信类型为单播通信的数据包有数据包1、数据包4和数据包7，其对应的优先级分别为1、2和3；第二目标侧标识为group_id1，通信类型为组播通信的数据包有数据包2和数据包5，其对应的优先级都为2；第二目标侧标识为service_id1，通信类型为广播通信的数据包有数据包3，其对应的优先级为3；第二目标侧标识为service_id2，通信类型为广播通信的数据包有数据包6，其对应的优先级为4。对于第二目标侧标识为target_id1，通信类型为单播通信的数据包，优先级最高的LCH是数据包1对应的LCH，其优先级是1；对于第二目标侧标识为group_id1，通信类型为组播通信的数据包，数据包2和数据包5的LCH的优先级都是2，对于第二目标侧标识为service_id1，通信类型为广播通信的数据包，优先级最高的LCH是数据包3对应的LCH，其优先级是3；对于第二目标侧标识为service_id2，通信类型为广播通信的数据包，优先级最高的LCH是数据包6对应的LCH，其优先级是4。优先级最高的LCH为数据包1对应的LCH，因此，该第一终端设备可以确定该业务数据包括数据包1。
表1
数据包 第二目标侧标识 通信类型 优先级
数据包1 target_id1 单播通信 1
数据包2 group_id1 组播通信 2
数据包3 service_id1 广播通信 3
数据包4 target_id1 单播通信 2
数据包5 group_id1 组播通信 2
数据包6 service_id2 广播通信 4
数据包7 target_id1 单播通信 3
可选的，若将传输资源分配给优先级最高的第一LCH后还有剩余的传输资源，第一终端设备可以根据第二目标侧标识、通信类型和优先级分配传输资源。具体的，若将传输资源分配给优先级最高的第一LCH后还有剩余的传输资源，第一终端设备将第二目标侧标识和通信类型相同的数据包按优先级降序排序，并按照该顺序为剩余的数据包分配传输资源。
例如，若第一终端设备为数据包1分配了传输资源后还有剩余的传输资源，对于第二目标侧标识为target_id1，通信类型为单播通信的数据包还有数据包4和数据包7，数据包4对应的优先级为2，数据包7对应的优先级为3，优先级最高的LCH是数据包4对应的LCH，因此，该业务数据还可以包括数据包4。若第一终端设备为数据包1和数据包4分配了传输资源后还有剩余的传输资源，该业务数据还可以包括数据包7。
可选的，该优先级是LCH的优先级、与近距通信数据包优先级(prose per packet priority，PPPP)对应的优先级、与近距通信数据包可靠性(proSe per packet reliability，PPPR)对应的优先级、与服务质量流标识(QoS flow identifier，QFI)对应的优先级、与5G服务质量标识(5G quality of service identifier，5QI)对应的优先级、与车通信服务质量标识(vechical QoS identifier，VQI)对应的优先级、与PQI对应的优先级。
可选的，对于与该SCI关联的MAC PDU，第一终端设备的MAC层实体将第二目标侧标识和通信类型相同的LCH封装在一个传输块(transport block，TB)中发送。
例如，第一终端设备的MAC层实体可以将数据1、数据4和数据7对应的LCH封装在一个TB中发送。
可选的，对于与该SCI关联的MAC PDU，第一终端设备的MAC层实体将第二源侧标识、第二目标侧标识和通信类型相同的LCH封装在一个传输块(transport block，TB)中发送。
步骤602、第一终端设备向第二终端设备发送业务数据。
可选的，第一终端设备的应用层实体产生该业务数据，并向下层递交，由下层实体对该业务数据进行处理，生成该业务数据对应的MAC PDU，最终经第一终端设备的PHY实体发送给第二终端设备的PHY实体。其中，该业务数据是与该SCI关联的业务数据。该业务数据包括在MAC PDU中。
可选的，该MAC PDU包括第二目标侧标识和通信类型，或该MAC PDU包括通信类型，或该MAC PDU包括第二源侧标识、第二目标侧标识和通信类型。
可选的，该第二源侧标识可以用于标识第一终端设备，可以是第一终端设备的源 层2标识，例如，该第一源侧标识可以是第一终端设备的Source Layer-2 Id。该第二源侧标识和该第一源侧标识存在对应关系，例如：该第一源侧标识可以是该第二源侧标识的低8位。可选的，第二终端设备根据该SCI包括的通信类型、以及该第二终端设备支持的通信类型的能力，确定接收该业务数据；或者，第二终端设备根据该SCI包括的第一目标侧标识和通信类型、以及该第二终端设备支持的第一目标侧标识和通信类型的能力，确定接收该业务数据；或者，第二终端设备根据该SCI包括的第一源侧标识、第一目标侧标识和通信类型、以及该第二终端设备支持的第一源侧标识、第一目标侧标识和通信类型的能力，确定接收该业务数据。
具体的，若第二终端设备自身支持的通信类型与该SCI包括的通信类型相同，第二终端设备接收该业务数据，若第二终端设备自身支持的通信类型与该SCI包括的通信类型不相同，第二终端设备不接收该业务数据；或者，若第二终端设备自身支持的第一目标侧标识和通信类型与该SCI包括的第一目标侧标识和通信类型相同，第二终端设备接收该业务数据，若第二终端设备自身支持的第一目标侧标识和通信类型与该SCI包括的第一目标侧标识和通信类型不相同，第二终端设备不接收该业务数据；或者，若第二终端设备自身支持的第一源侧标识、第一目标侧标识和通信类型与该SCI包括的第一源侧标识、第一目标侧标识和通信类型相同，第二终端设备接收该业务数据，若第二终端设备自身支持的第一源侧标识、第一目标侧标识和通信类型与该SCI包括的第一源侧标识、第一目标侧标识和通信类型不相同，第二终端设备不接收该业务数据。
示例性的，若第二终端设备PHY层实体支持的通信类型与该SCI包括的或通信类型相同，第二终端设备接收该业务数据，若第二终端设备PHY层实支持的通信类型与该SCI包括的通信类型不相同，第二终端设备不接收该业务数据；或者，若第二终端设备PHY层实支持的第一目标侧标识和通信类型与该SCI包括的第一目标侧标识和通信类型相同，第二终端设备接收该业务数据，若第二终端设备PHY层实支持的第一目标侧标识和通信类型与该SCI包括的第一目标侧标识和通信类型不相同，第二终端设备不接收该业务数据；或者，若第二终端设备PHY层实支持的第一源侧标识、第一目标侧标识和通信类型与该SCI包括的第一源侧标识、第一目标侧标识和通信类型相同，第二终端设备接收该业务数据，若第二终端设备PHY层实支持的第一源侧标识、第一目标侧标识和通信类型与该SCI包括的第一源侧标识、第一目标侧标识和通信类型不相同，第二终端设备不接收该业务数据。
可选的，第二终端设备根据该MAC PDU包括的通信类型、以及该第二终端设备支持的通信类型的能力，确定接收该业务数据；或者，第二终端设备根据该MAC PDU包括的第二目标侧标识和通信类型、以及该第二终端设备支持的第二目标侧标识和通信类型，确定接收该业务数据的能力；或者，第二终端设备根据该MAC PDU包括的第二源侧标识、第二目标侧标识和通信类型、以及该第二终端设备支持的第二源侧标识、第二目标侧标识和通信类型的能力，确定接收该业务数据。
具体的，若第二终端设备自身支持的通信类型与该MAC PDU包括的通信类型相同，第二终端设备接收该业务数据，若第二终端设备自身支持的通信类型与该MAC PDU包括的通信类型不相同，第二终端设备不接收该业务数据；或者，若第二终端设 备自身支持的第二目标侧标识和通信类型与该MAC PDU包括的第二目标侧标识和通信类型相同，第二终端设备接收该业务数据，若第二终端设备自身支持的第二目标侧标识和通信类型与该MAC PDU包括的第二目标侧标识和通信类型不相同，第二终端设备不接收该业务数据；或者，若第二终端设备自身支持的第二源侧标识、第二目标侧标识和通信类型与该MAC PDU包括的第二源侧标识、第二目标侧标识和通信类型相同，第二终端设备接收该业务数据，若第二终端设备自身支持的第二源侧标识、第二目标侧标识和通信类型与该MAC PDU包括的第二源侧标识、第二目标侧标识和通信类型不相同，第二终端设备不接收该业务数据。
示例性的，若第二终端设备MAC层实体支持的通信类型与该MAC PDU包括的或通信类型相同，第二终端设备接收该业务数据，若第二终端设备MAC层实支持的通信类型与该MAC PDU包括的通信类型不相同，第二终端设备不接收该业务数据；或者，若第二终端设备MAC层实支持的第二目标侧标识和通信类型与该MAC PDU包括的第二目标侧标识和通信类型相同，第二终端设备接收该业务数据，若第二终端设备MAC层实支持的第二目标侧标识和通信类型与该MAC PDU包括的第二目标侧标识和通信类型不相同，第二终端设备不接收该业务数据；或者，若第二终端设备MAC层实支持的第二源侧标识、第二目标侧标识和通信类型与该MAC PDU包括的第二源侧标识、第二目标侧标识和通信类型相同，第二终端设备接收该业务数据，若第二终端设备MAC层实支持的第二源侧标识、第二目标侧标识和通信类型与该MAC PDU包括的第二源侧标识、第二目标侧标识和通信类型不相同，第二终端设备不接收该业务数据。
可选的，第二终端设备根据该SCI包括的通信类型、该MAC PDU包括的通信类型、以及该第二终端设备支持的通信类型的能力，确定接收该业务数据；或者，第二终端设备根据该SCI包括的第一目标侧标识和通信类型、该MAC PDU包括的第二目标侧标识和通信类型、以及该第二终端设备支持的第一目标侧标识、第二目标侧标识和通信类型的能力，确定接收该业务数据；或者，第二终端设备根据该SCI包括的第一源侧标识、第一目标侧标识和通信类型，该MAC PDU包括的第二源侧标识、第二目标侧标识和通信类型，以及该第二终端设备支持的第一源侧标识、第一目标侧标识、第二源侧标识、第二目标侧标识和通信类型的能力，确定接收该业务数据。
具体的，若第二终端设备自身支持的通信类型与该SCI包括的通信类型相同，且第二终端设备自身支持的通信类型与该MAC PDU包括的通信类型相同，第二终端设备接收该业务数据；或者，若第二终端设备自身支持的第一目标侧标识和通信类型与该SCI包括的第一目标侧标识和通信类型相同，且第二终端设备自身支持的第二目标侧标识和通信类型与该MAC PDU包括的第二目标侧标识和通信类型相同，第二终端设备接收该业务数据；或者，若第二终端设备自身支持的第一源侧标识、第一目标侧标识和通信类型与该SCI包括的第一源侧标识、第一目标侧标识和通信类型相同，且第二终端设备自身支持的第二源侧标识、第二目标侧标识和通信类型与该MAC PDU包括的第二源侧标识、第二目标侧标识和通信类型相同，第二终端设备接收该业务数据。
示例性的，若第二终端设备PHY层实体支持的通信类型与该SCI包括的或通信类 型相同，且第二终端设备MSC层实体支持的通信类型与该MAC PDU包括的或通信类型相同，第二终端设备接收该业务数据；或者，若第二终端设备PHY层实支持的第一目标侧标识和通信类型与该SCI包括的第一目标侧标识和通信类型相同，且第二终端设备MAC层实支持的第二目标侧标识和通信类型与该MAC PDU包括的第二目标侧标识和通信类型相同，第二终端设备接收该业务数据；或者，若第二终端设备PHY层实支持的第一源侧标识、第一目标侧标识和通信类型与该SCI包括的第一源侧标识、第一目标侧标识和通信类型相同，且第二终端设备MAC层实支持的第二源侧标识、第二目标侧标识和通信类型与该MAC PDU包括的第二源侧标识、第二目标侧标识和通信类型相同，第二终端设备接收该业务数据。
可选的，第二终端设备接收该业务数据后，第二终端设备向第一终端设备发送反馈信息。该反馈信息用于指示该业务数据是否发送成功。例如，若反馈信息为ACK，表示该业务数据发送成功；若反馈信息为NACK，表示该业务数据发送失败。
基于图6所示的方法，第二终端设备在接收到第一终端设备发送的SCI后，若该SCI包括的第一目标侧标识和/或通信类型，以及该第二终端设备自身支持的第一目标侧标识和/或通信类型相同，第二终端设备接收该业务数据，并向该第一终端设备发送反馈信息。第二终端设备可以接收对应通信类型的数据，以降低第二终端设备的误收包率，进而提高第二终端设备的收包效率。
进一步地，第一终端设备在发送该SCI之前，网络设备可以给该第一终端设备发送第一配置信息，该第一终端设备可以根据该第一配置信息获取同步配置、发送方式或侧行链路的传输资源的位置，第一终端设备还可以根据该第一配置信息配置第二目标侧标识和该通信类型对应的SLRB，或者，配置该通信类型对应的SLRB。
如图7所示，在步骤601之前，该通信方法还包括步骤701。
步骤701、第一终端设备从网络设备接收第一配置信息。
可选的，第一终端设备的PHY实体从网络设备的PHY实体接收的第一配置信息。
可选的，第一配置信息为***信息块(system information blocks，SIB)、无线资源控制(radio resource control，RRC)信令、MAC信令、下行控制信息(downlink control information，DCI)、NAS信令或V3接口消息。
可选的，若该第一配置信息是SIB或RRC信令，该第一配置信息是该网络设备的RRC层实体生成的；若该第一配置信息是MAC信令，该第一配置信息是该网络设备的MAC层实体生成的；若该第一配置信息是DCI，该第一配置信息是该网络设备的PHY层实体生成的；若该第一配置信息是NAS信令或V3接口消息，该第一配置信息是该网络设备从核心网设备获取的。
示例1，该第一配置信息中包括第二目标侧标识和该通信类型、以及与该第二目标侧标识和该通信类型对应的第二配置信息，其中，该第二配置信息包括侧行链路配置信息和/或调度资源。
其中，该侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置。该调度资源包括与该第二目标侧标识和/或通信类型对应的传输资源。同步配置可以包括：V2X UE的同步信号配置信息(例如：v2x-SyncConfig)和/或V2X UE的同步配置信息(例如：typeTxSync)。发送方式可以包括频分双工方式或时分双工方式。传输资 源的位置可以是传输资源在资源池中的范围。该传输资源是用于传输该业务数据的时频资源。该调度资源可以是半静态调度资源或者动态调度资源。
可选的，该侧行链路配置信息可以包括以下信息中的一个或多个：V2X UE的接收资源池的配置信息(例如：v2x-CommRxPool)、V2X UE的发送资源池的配置信息(例如：v2x-CommTxPoolNormalCommon)、行人终端互联通信(P-UE to everything，P2X)UE的发送资源池的配置信息(例如：p2x-CommTxPoolNormalCommon)、V2X UE的临时发送资源池的配置信息(例如：v2x-CommTxPoolExceptional)、V2X UE的同步信号配置信息(例如：v2x-SyncConfig)、V2X UE的异频信息(例如：v2x-InterFreqInfoList)、V2X UE的资源选择配置信息(例如：v2x-ResourceSelectionConfig)、区域配置信息(例如：zoneConfig)、V2X UE的同步配置信息(例如：typeTxSync)、SL/UL(uplink)传输优先级(例如：thresSL-TxPrioritization、anchor频点列表配置信息(例如：anchorCarrierFreqList)、基站时隙与GPS时间偏差(例如：offsetDFN)、基于UE测量的SL信道忙闲程度决定SL数据发送的参数配置信息(例如：cbr-CommonTxConfigList)。
示例性的，V2X UE的临时发送资源池的配置信息可以在无线链路失败(RLF)、无线链路切换失败(HOF)或在第一终端设备在竞争资源时，测量数据开始到测量数据结束时使用。
示例性的，V2X UE的资源选择配置信息可以在第一终端设备处于自主竞争资源模式时使用。
示例性的，区域配置信息用于第一终端设备处于自主竞争资源模式时，根据自己的GPS位置计算区域标识(zone id)，然后适用该区域标识对应的发送/接收资源池。
示例性的，该第一配置信息可以是SIB21，该第一配置信息可以包括该第二目标侧标识和该通信类型、以及与该第二目标侧标识和该通信类型对应的侧行链路配置信息。该第一终端设备可以根据该侧行链路配置信息获取同步配置、发送方式或传输资源的位置。
示例性的，V2X UE的同步配置信息用于指示GPS、网络设备、终端设备等的优先级顺序。
示例性的，SL/UL传输优先级用于指示优先发送SL的数据还是UL的数据。例如，若SL发送数据的最高PPPP值小于预设阈值，优先发送SL的数据，若SL发送数据的最高PPPP值大于等于预设阈值，优先发送UL的数据。
可选的，网络设备根据上述每个侧行链路配置信息、第二目标侧标识和通信类型分配资源池中的资源。具体的，网络设备在资源池中给上述每个侧行链路配置信息分配资源，针对上述每个侧行链路配置信息的资源，网络设备给每个第二目标侧标识和通信类型分配资源；或者，网络设备给每个第二目标侧标识和通信类型分配资源，针对每个第二目标侧标识和通信类型的资源，网络设备给上述每个侧行链路配置信息分配资源。
示例性的，该第一配置信息可以是SIB21，该第一配置信息可以包括第二目标侧标识、通信类型、侧行链路配置信息和资源池的映射信息，其中，第二目标侧标识、通信类型、侧行链路配置信息和资源池的映射信息用于指示第二目标侧标识、通信类 型、侧行链路配置信息和资源池的映射关系。第二目标侧标识、通信类型、侧行链路配置信息和资源池的映射信息包括该第二目标侧标识、该通信类型、以及与该第二目标侧标识和该通信类型对应的侧行链路配置信息，第一终端设备可以根据第二目标侧标识、通信类型、侧行链路配置信息和资源池的映射信息获取该第二目标侧标识和通信类型对应的传输资源，或者，第一终端设备可以根据第二目标侧标识、通信类型、侧行链路配置信息和资源池的映射信息获取该第二目标侧标识和通信类型对应的传输资源的位置。若第一终端设备获取的是该第二目标侧标识和通信类型对应的传输资源的位置，该第一终端设备可以通过竞争的资源获取方式在该传输资源的位置上竞争资源。
示例性的，该第一配置信息可以是RRC信令，该第一配置信息中可以包括第二目标侧标识和该通信类型、以及与该第二目标侧标识和该通信类型对应的第二配置信息，该第二配置信息可以是半静态调度资源，第一终端设备接收到该第一配置信息后，可以在该半静态调度资源上发送与该第二目标侧标识和该通信类型相同的业务数据。具体的，该第一终端设备接收该RRC信令后，可以在该半静态调度资源上发送与该第二目标侧标识和该通信类型相同的业务数据；或者，该第一终端设备接收到该RRC信令后，可以在接收到DCI后，在该半静态调度资源上发送与该第二目标侧标识和该通信类型相同的业务数据，该DCI用于激活该半静态调度资源。
示例2，第一配置信息中包括该通信类型，以及与该通信类型对应的第二配置信息。
其中，该第二配置信息的相关介绍可以参考示例1中对应的介绍，此处不再赘述。
可选的，网络设备根据上述每个侧行链路配置信息和通信类型分配资源池中的资源。具体的，网络设备在资源池中给上述每个侧行链路配置信息分配资源，针对上述每个侧行链路配置信息的资源，网络设备给每个通信类型分配资源；或者，网络设备给每个通信类型分配资源，针对每个通信类型的资源，网络设备给上述每个侧行链路配置信息分配资源。
示例性的，该第一配置信息可以是SIB21，该第一配置信息可以包括通信类型、侧行链路配置信息和资源池的映射信息，其中，通信类型、侧行链路配置信息和资源池的映射信息用于指示通信类型、侧行链路配置信息和资源池的映射关系。通信类型、侧行链路配置信息和资源池的映射信息包括该通信类型、以及与该通信类型对应的侧行链路配置信息，第一终端设备可以根据通信类型、侧行链路配置信息和资源池的映射信息获取该通信类型对应的传输资源，或者，第一终端设备可以根据通信类型、侧行链路配置信息和资源池的映射信息获取该通信类型对应的传输资源的位置。若第一终端设备获取的是该通信类型对应的传输资源的位置，该第一终端设备可以通过竞争的资源获取方式在该传输资源的位置上竞争资源。
示例性的，该第一配置信息可以是RRC信令，第一配置信息中包括该通信类型，以及与该通信类型对应的第二配置信息，该第二配置信息可以是半静态调度资源，第一终端设备接收到该第一配置信息后，可以在该半静态调度资源上发送与该通信类型相同的业务数据。或者，该第一配置信息可以是RRC信令，第一配置信息中包括该通信类型，以及与该通信类型对应的第二配置信息，该第二配置信息可以是动态调度资 源，该动态调度资源可以在该第一终端设备接收到网络设备发送的DCI后才能启用。
示例3，第一配置信息中包括该第二目标侧标识和该通信类型、与该第二目标侧标识和该通信类型对应的第二配置信息、QoS信息、以及与QoS信息对应的侧行链路无线承载SLRB的配置信息。
其中，该第二配置信息的相关介绍可以参考示例1中对应的介绍，此处不再赘述。
示例性的，该第一配置信息可以是SIB21，该第一配置信息可以包括该第二目标侧标识和该通信类型、与该第二目标侧标识和该通信类型对应的第二配置信息、以及QoS信息与侧行链路无线承载SLRB的配置信息的映射信息，该QoS信息与SLRB的配置信息的映射信息用于指示QoS信息与SLRB的配置信息的映射关系，该QoS信息与SLRB的配置信息的映射信息可以包括QoS信息、与QoS信息对应的SLRB的配置信息。该第二配置信息可以包括侧行链路配置信息和/或调度资源，该侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，该调度资源包括与所述第二目标侧标识和通信类型对应的传输资源。第一终端设备可以根据该侧行链路配置信息获取同步配置、发送方式或传输资源的位置，第一终端设备可以根据调度资源获取传输资源，第一终端设备可以根据与QoS信息对应的SLRB的配置信息获取SLRB的配置。
示例4，第一配置信息中包括该通信类型、与该通信类型对应的第二配置信息、QoS信息、以及与QoS信息对应的侧行链路无线承载SLRB的配置信息。
其中，该第二配置信息的相关介绍可以参考示例1中对应的介绍，此处不再赘述。
示例性的，该第一配置信息可以是SIB21，该第一配置信息可以包括该通信类型、与该通信类型对应的第二配置信息、以及QoS信息与侧行链路无线承载SLRB的配置信息的映射信息，该QoS信息与SLRB的配置信息的映射信息用于指示QoS信息与SLRB的配置信息的映射关系，该QoS信息与SLRB的配置信息的映射信息可以包括QoS信息、与QoS信息对应的SLRB的配置信息。该第二配置信息可以包括侧行链路配置信息和/或调度资源，该侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，该调度资源包括与通信类型对应的传输资源。第一终端设备可以根据该侧行链路配置信息获取同步配置、发送方式或传输资源的位置，第一终端设备可以根据调度资源获取传输资源，第一终端设备可以根据与QoS信息对应的SLRB的配置信息获取SLRB的配置。
示例5，第一配置信息中包括QoS信息、以及与QoS信息对应的侧行链路无线承载SLRB的配置信息。
示例性的，该第一配置信息可以是SIB21，该第一配置信息可以包括QoS信息与侧行链路无线承载SLRB的配置信息的映射信息，该QoS信息与SLRB的配置信息的映射信息用于指示QoS信息与SLRB的配置信息的映射关系，该QoS信息与SLRB的配置信息的映射信息可以包括QoS信息、与QoS信息对应的SLRB的配置信息。第一终端设备可以根据与QoS信息对应的SLRB的配置信息获取SLRB的配置。
可选的，第一终端设备在接收到网络设备发送的第一配置信息后，向网络设备发送反馈信息，该反馈信息用于指示该第一终端设备是否成功收到该第一配置信息。例如，若反馈信息为ACK，表示第一终端设备接收该第一配置信息成功；若反馈信息为NACK，表示第一终端设备接收该第一配置信息失败。
可选的，第一终端设备存储有该第一配置信息，其中，该第一配置信息中包括该第二目标侧标识和该通信类型、以及与该第二目标侧标识和该通信类型对应的第二配置信息；或者，该第一配置信息中包括该通信类型、以及与该通信类型对应的第二配置信息；或者，该第一配置信息中包括第二目标侧标识和该通信类型、与该第二目标侧标识和该通信类型对应的第二配置信息、QoS信息、以及与QoS信息对应的侧行链路无线承载SLRB的配置信息；或者，该第一配置信息中包括该通信类型、与该通信类型对应的第二配置信息、QoS信息、以及与QoS信息对应的侧行链路无线承载SLRB的配置信息；或者，该第一配置信息中包括QoS信息、以及与QoS信息对应的侧行链路无线承载SLRB的配置信息；其中，该第二配置信息包括侧行链路配置信息和/或调度资源，该侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，该调度资源包括与该第二目标侧标识和/或通信类型对应的传输资源。
基于图7所示的方法，第一终端设备可以接收网络设备发送的第一配置信息，该第一配置信息中包括第二配置信息，和/或侧行链路无线承载SLRB的配置信息。第一终端设备可以根据该第二配置信息获取同步配置、发送方式或传输资源的位置，第一终端设备还可以根据网络设备发送的侧行链路无线承载SLRB的配置信息配置SLRB。
进一步地，第一终端设备在发送该SCI之前，第一终端设备可以向网络设备发送业务信息，该业务信息用于第一终端设备向网络设备发送通信类型，以便该网络设备根据该通信类型为第一终端设备分配该通信类型对应的侧行链路传输资源。
如图8所示，步骤601之前，该通信方法还包括步骤801。
步骤801、第一终端设备向网络设备发送业务信息。
可选的，第一终端设备的RRC层实体生成该业务信息，再由该第一终端设备的PHY实体向网络设备的PHY实体发送该业务信息。
其中，该业务信息包括：通信类型。
示例1，第一终端设备向网络设备发送业务信息；其中，该业务信息包括：该通信类型。网络设备可以根据该通信类型为该第一终端设备分配传输资源。例如，第一终端设备向网络设备发送业务信息，该业务信息包括该通信类型。网络设备根据预存储的通信类型和传输资源的对应关系为第一终端设备分配传输资源，或者，网络设备根据从核心网设备接收的通信类型和传输资源的对应关系为第一终端设备分配传输资源。
示例2，第一终端设备向网络设备发送业务信息；其中，该业务信息包括：该第二目标侧标识和该通信类型。网络设备可以根据该第二目标侧标识和该通信类型为该第一终端设备分配传输资源。例如，第一终端设备向网络设备发送业务信息，该业务信息包括该第二目标侧标识和该通信类型。网络设备根据预存储的第二目标侧标识、通信类型和传输资源的对应关系为第一终端设备分配传输资源，或者，网络设备根据从核心网设备接收的第二目标侧标识、通信类型和传输资源的对应关系信息为第一终端设备分配传输资源。
示例3，第一终端设备向网络设备发送业务信息；其中，该业务信息包括：该通信类型和该通信类型对应的频点。网络设备可以根据该通信类型和该通信类型对应的频点在该通信类型对应的频点上为该第一终端设备分配传输资源。例如，第一终端设 备向网络设备发送业务信息，该业务信息包括该通信类型和该通信类型对应的频点。网络设备根据预存储的通信类型、频点信息和传输资源的对应关系为第一终端设备分配传输资源，或者，网络设备根据从核心网设备接收的通信类型、频点信息和传输资源的对应关系信息为第一终端设备分配传输资源。其中，频点信息用于指示某一个通信类型对应的频点。
示例4，第一终端设备向网络设备发送业务信息；其中，该业务信息包括：该第二目标侧标识和该通信类型，以及该第二目标侧标识和该通信类型对应的频点。网络设备可以根据该第二目标侧标识和该通信类型，以及该第二目标侧标识和该通信类型对应的频点在该第二目标侧标识和该通信类型对应的频点上为该第一终端设备分配传输资源。例如，第一终端设备向网络设备发送业务信息，该业务信息包括该第二目标侧标识和该通信类型，以及该第二目标侧标识和该通信类型对应的频点。网络设备根据预存储的第二目标侧标识、通信类型、频点信息和传输资源的对应关系为第一终端设备分配传输资源，或者，网络设备根据从核心网设备接收的第二目标侧标识、通信类型、频点信息和传输资源的对应关系信息为第一终端设备分配传输资源。其中，频点信息用于指示某一个第二目标侧和通信类型对应的频点。
可选的，网络设备在接收到第一终端设备发送的业务信息后，向第一终端设备发送反馈信息，该反馈信息用于指示网络设备是否成功接收到该业务信息。
可选的，网络设备在接收到第一终端设备发送的业务信息后，向第一终端设备发送传输资源配置信息，该传输资源配置信息包括用于发送该业务数据的侧行链路的传输资源。
基于图8所示的方法，第一终端设备可以向网络设备发送该业务信息，该业务信息可以包括通信类型，网络设备可以根据该通信类型为该第一终端设备分配该通信类型对应的用于发送该业务数据的传输资源。
进一步地，第一终端设备在发送该SCI之前，第一终端设备可以向网络设备发送缓存状态报告(buffer status report，BSR)，该BSR用于第一终端设备向网络设备请求侧行链路的传输资源。
如图9所示，在步骤601之前，该通信方法还包括步骤901和902。
步骤901、第一终端设备向网络设备发送缓存状态报告BSR。
可选的，第一终端设备的MAC实体生成该BSR，并由该第一终端设备的PHY实体向网络设备的PHY实体发送该BSR。
其中，该BSR中包括该第二目标侧标识和该通信类型，或包括通信类型。
示例1，第一终端设备向网络设备发送BSR；其中，该BSR包括：该第二目标侧标识和该通信类型。网络设备可以根据该第二目标侧标识和该通信类型为该第一终端设备分配传输资源。例如，第一终端设备向网络设备发送BSR，该BSR包括该第二目标侧标识和该通信类型。网络设备可以根据预存储的第二目标侧标识、通信类型和传输资源的对应关系为第一终端设备分配传输资源，或者，网络设备可以根据从核心网设备接收的第二目标侧标识、通信类型和传输资源的对应关系信息为第一终端设备分配传输资源，或者，网络设备可以根据第一终端设备上报的业务信息中包括该第二目标侧标识、该通信类型和该第二目标侧标识以及该通信类型对应的频点在该频点上为 第一终端设备分配传输资源。
示例2，第一终端设备向网络设备发送BSR；其中，该BSR包括：该通信类型。网络设备根据该通信类型为该第一终端设备分配传输资源。例如，第一终端设备向网络设备发送BSR，该BSR包括该通信类型。网络设备可以根据预存储的通信类型和传输资源的对应关系为第一终端设备分配传输资源，或者，网络设备可以根据从核心网设备接收的通信类型和传输资源的对应关系为第一终端设备分配传输资源，或者，网络设备可以根据第一终端设备上报的业务信息中包括该通信类型和该通信类型对应的频点在该频点上为第一终端设备分配传输资源。
可选的，网络设备在接收到第一终端设备发送的BSR后，向第一终端设备发送反馈信息，该反馈信息用于指示网络设备是否成功接收到该BSR。
步骤902、第一终端设备接收网络设备发送的传输资源配置信息。
可选的，该传输资源配置信息是DCI。
可选的，网络设备接收到该BSR后，该网络设备的PHY实体生成对应的DCI，并发送给第一终端设备。
其中，该传输资源配置信息包括用于发送该业务数据的侧行链路的传输资源。
基于图9所示的方法，第一终端设备可以向网络设备发送该BSR，该BSR可以包括第二目标侧标识和通信类型，或者，该BSR可以包括通信类型，网络设备可以根据该第二目标侧标识和该通信类型为该第一终端设备分配该通信类型对应的用于发送该业务数据的传输资源；或者，网络设备可以根据该通信类型为该第一终端设备分配该通信类型对应的用于发送该业务数据的传输资源。
进一步地，第一终端设备在发送该SCI之前，第一终端设备可以向网络设备发送辅助信息，该辅助信息可以包括业务模型信息及通信类型，以便网络设备根据该辅助信息为第一终端设备分配调度资源。
如图10所示，在步骤601之前，该通信方法还包括步骤1001和1002。
步骤1001、第一终端设备向网络设备发送辅助信息。
可选的，第一终端设备的NAS实体、SDAP实体、RRC实体、PDCP实体、RLC实体、MAC实体或PHY实体生成该辅助信息，并由第一终端设备的PHY实体向网络设备的PHY实体发送该辅助信息。
其中，辅助信息中包括业务模型信息及通信类型。
其中，业务模型信息可以包括以下参数中的一个或多个：业务周期(例如：trafficPeriodicity)、数据包到达时刻与基站***帧的时间偏差(例如：timingOffset)、SL数据包优先级(例如：priorityInfoSL)、Uu口LCH标识(例如：logicalChannelIdentityUL)、消息包大小(例如：messageSize)、业务标识(例如：trafficDestination)、SL数据包可靠性标识(例如：reliabilityInfoSL)。
第一终端设备可以向网络设备发送该辅助信息，其中，该辅助信息中包括业务模型信息和通信类型。网络设备可以根据该辅助信息为第一终端设备分配传输资源；或者，网络设备可以根据该辅助信息为第一终端设备分配调度资源。
示例性的，若辅助信息包括：业务标识和通信类型，该业务标识包括第二目标侧标识(例如：destination layer-2 id)，网络设备可以根据预存储的第二目标侧标识、通 信类型和传输资源的对应关系为第一终端设备分配传输资源，或者，网络设备可以根据从核心网设备接收的第二目标侧标识、通信类型和传输资源的对应关系信息为第一终端设备分配传输资源，或者，网络设备可以根据第一终端设备上报的业务信息中包括该第二目标侧标识、该通信类型和该第二目标侧标识以及该通信类型对应的频点，在该频点上为第一终端设备分配传输资源。则该第一终端设备可以确定该第二目标侧标识和通信类型对应的LCH的优先级最高，该第一终端设备优先发送该第二目标侧标识和通信类型对应的业务数据，或者，该第一终端设备可以在该传输资源上发送与该第二目标侧标识和通信类型相同的业务数据。
示例性的，若辅助信息包括：业务周期和通信类型，网络设备可以根据预存储的通信类型和传输资源的对应关系为第一终端设备分配调度资源，或者，网络设备可以根据从核心网设备接收的通信类型和传输资源的对应关系为第一终端设备分配调度资源，或者，网络设备可以根据第一终端设备上报的业务信息中包括该通信类型和该通信类型对应的频点在该频点上为第一终端设备分配调度资源。该调度资源可以是半静态调度资源，也可以是动态调度资源。则第一终端设备可以在该业务周期内(例如：20毫秒)，在该调度资源上发送与该通信类型相同的业务数据。
示例性的，若辅助信息包括：业务周期、业务标识和通信类型，该业务标识包括第二目标侧标识(例如：destination layer-2 id)，根据网络设备可以根据预存储的第二目标侧标识、通信类型和传输资源的对应关系为第一终端设备分配调度资源，或者，网络设备可以根据从核心网设备接收的第二目标侧标识、通信类型和传输资源的对应关系信息为第一终端设备分配调度资源，或者，网络设备可以根据第一终端设备上报的业务信息中包括该第二目标侧标识、该通信类型和该第二目标侧标识以及该通信类型对应的频点在该频点上为第一终端设备分配调度资源。该调度资源可以是半静态调度资源，也可以是动态调度资源。则第一终端设备可以在该业务周期内(例如：50毫秒)，在该调度资源上发送与该第二目标侧标识和该通信类型相同的业务数据。
可选的，第一终端设备向网络设备发送该辅助信息，其中，该辅助信息中包括业务模型信息和通信类型。网络设备可以根据该辅助信息为第一终端设备分配用于传输数据的传输资源和用于发送反馈信息的反馈资源。
示例性的，若该通信类型为单播通信，网络设备可以根据该辅助信息为第一终端设备分配用于传输数据的传输资源和1个用于发送反馈信息的反馈资源；若该通信类型为组播通信，网络设备可以根据该辅助信息为第一终端设备分配用于传输数据的传输资源和多个用于发送反馈信息的反馈资源；若该通信类型为广播通信，网络设备可以根据该辅助信息为第一终端设备分配用于传输数据的传输资源，网络设备可以不用为第一终端设备分配反馈资源。
可选的，网络设备在接收到第一终端设备发送的辅助信息后，向第一终端设备发送反馈信息，该反馈信息用于指示网络设备是否成功接收到该辅助信息。
步骤1002、第一终端设备从网络设备接收调度资源。
可选的，网络设备接收到该辅助信息后，该网络设备的RRC实体生成包括该调度资源的配置信息，并向该第一终端设备发送该配置信息。
其中，该调度资源可以包括用于发送该业务数据的侧行链路的传输资源。基于图 10所示的方法，第一终端设备可以向网络设备发送该辅助信息，该辅助信息可以包括业务模型信息及通信类型，网络设备可以根据该业务模型信息及该通信类型为该第一终端设备分配该通信类型对应的调度资源。
进一步地，在第一终端设备向第二终端设备发送该SCI之前，该第一终端设备还可以向网络设备发送QoS信息，该QoS信息可以包括该第二目标侧标识和该通信类型，或者，包括该通信类型，以便网络设备根据该QoS信息向该第一终端设备发送SLRB的配置信息。
如图11所示，在步骤601之前，该通信方法还包括步骤1101。
步骤1101、第一终端设备向网络设备发送QoS信息。
可选的，第一终端设备的上层(upper layer)实体或AS实体生成该QoS信息，并由该第一终端设备的PHY实体向网络设备的PHY实体发送该QoS信息，其中，该上层实体包括应用层实体、V2X层实体和NAS实体。
其中，该QoS信息中可以包括该第二目标侧标识和该通信类型，或者，包括该通信类型。
可选的，该QoS信息还包括以下信息中的至少一种：单播或组播连接的连接标识(例如：ConnId)、组播连接的连接组标识(例如：GroupId)、第二源侧标识(例如：第一终端设备的层2Id)、业务质量信息。其中，业务质量信息可以是PPPP、PPPR、QFI、5QI、VQI、PQI等业务质量信息，具体的，该业务质量信息可以包括时延、可靠性、通信距离、速率、包大小、包间隔等。
第一终端设备可以向网络设备发送该QoS信息，网络设备可以根据预存储的QoS信息和SLRB的配置信息的对应关系向第一终端设备发送SLRB的配置信息，或者，网络设备可以根据从核心网设备接收的QoS信息和SLRB的配置信息的对应关系向第一终端设备发送SLRB的配置信息。
可选的，网络设备在接收到第一终端设备发送的QoS信息，向第一终端设备发送反馈信息，该反馈信息用于指示网络设备是否成功接收到该QoS信息。
基于图11所示的方法，第一终端设备可以向网络设备发送该QoS信息，该QoS信息可以包括该第二目标侧标识和该通信类型，或者，包括该通信类型，网络设备可以根据该QoS信息向该第一终端设备发送SLRB的配置信息。
进一步地，在第一终端设备向第二终端设备发送SCI之前，第一终端设备还可以接收网络设备发送的SLRB的配置信息，并根据该SLRB的配置信息配置该业务数据对应的SLRB。
如图12所示，在步骤601之前，该通信方法还包括步骤1201。
步骤1201、第一终端设备从网络设备接收SLRB的配置信息。
可选的，第一终端设备的PHY实体从网络设备的PHY实体接收SLRB的配置信息。
其中，该SLRB的配置信息可以是网络设备生成的。
其中，该SLRB的配置信息可以包括与该第二目标侧标识和/或该通信类型对应的SLRB配置；该SLRB配置包括服务质量流QoS flow到侧行链路数据无线承载SL-DRB的映射关系、PDCP配置，RLC配置和LCH配置中的至少一个。
可选的，第一终端设备根据该SLRB的配置信息配置该第二目标侧标识和该通信类型对应的SLRB，或，第一终端设备根据该SLRB的配置信息配置该通信类型对应的SLRB。
可选的，第一终端设备在接收到网络设备发送的SLRB的配置信息，向网络设备发送反馈信息，该反馈信息用于指示该第一终端设备是否成功接收该SLRB的配置信息。例如，若该反馈信息是ACK，标识该第一终端设备成功接收该SLRB的配置信息；若该反馈信息是NACK，表示该第一终端设备接收该SLRB的配置信息失败。
基于图12所示的方法，第一终端设备可以网络设备发送的SLRB的配置信息，并根据该SLRB的配置信息配置该第二目标侧标识和/或该通信类型对应的SLRB。
进一步地，在第一终端设备向第二终端设备发送SCI之前，该第一终端设备还可以向第二终端设备发送SLRB的配置信息，以便第二终端设备可以根据该SLRB的配置信息处理接收到的业务数据。
如图13所示，在步骤601之前，该通信方法还包括步骤1301。
步骤1301、第一终端设备向第二终端设备发送SLRB的配置信息。
可选的，第一终端设备的PHY实体向第二终端设备的PHY实体发送该SLRB的配置信息。
可选的，第一终端设备接收到网络设备发送的SLRB的配置信息后，向第二终端设备发送该SLRB的配置信息。
需要说明的是，第二终端设备可以根据该SLRB的配置信息处理接收到的业务数据。
可选的，第二终端设备接收到第一终端设备发送的SLRB的配置信息，向第一终端设备发送反馈信息，该反馈信息用于指示该第二终端设备是否成功接收该SLRB的配置信息。例如，若该反馈信息是ACK，标识该第二终端设备成功接收该SLRB的配置信息；若该反馈信息是NACK，表示该第二终端设备接收该SLRB的配置信息失败。
基于图13所示的方法，第二终端设备可以接收第一终端设备发送的SLRB的配置信息，并根据该SLRB的配置信息处理接收到的业务数据。
进一步地，在第一终端设备向第二终端设备发送SCI之前，第一终端设备可以与第二终端设备建立第一连接，以便第二终端设备接收该业务数据。
如图14所示，在步骤601之前，该通信方法还包括步骤1401。
步骤1401、第一终端设备与第二终端设备建立第一连接。
可选的，第一终端设备在发送该SCI前，若第一终端设备没有与第二终端设备建立与该第二目标侧标识和/或该通信类型对应的第一连接，第一终端设备与第二终端设备建立第一连接。
可选的，第一终端设备在发送该SCI前，若第一终端设备没有与第二终端设备建立与该第二源侧标识、该第二目标侧标识和该通信类型对应的第一连接，第一终端设备与第二终端设备建立第一连接。
可选的，第二终端设备接收该业务数据前，若第二终端设备没有与第一终端设备建立与该第二目标侧标识和/或该通信类型对应的第一连接，第二终端设备与第一终端设备建立第一连接。
可选的，第二终端设备接收该业务数据前，若第二终端设备没有与第一终端设备建立与该第二源侧标识、该第二目标侧标识和该通信类型对应的第一连接，第二终端设备与第一终端设备建立第一连接。
可选的，第二终端设备接收该业务数据时，若第二终端设备没有与第一终端设备建立与该第二目标侧标识和/或该通信类型对应的第一连接，第二终端设备与第一终端设备建立第一连接。
可选的，第二终端设备接收该业务数据时，若第二终端设备没有与第一终端设备建立与该第二源侧标识、该第二目标侧标识和该通信类型对应的第一连接，第二终端设备与第一终端设备建立第一连接。
可选的，第二终端设备接收该业务数据后，若第二终端设备没有与第一终端设备建立与该第二目标侧标识和/或该通信类型对应的第一连接，第二终端设备与第一终端设备建立第一连接。
可选的，第二终端设备接收该业务数据后，若第二终端设备没有与第一终端设备建立与该第二源侧标识、该第二目标侧标识和该通信类型对应的第一连接，第二终端设备与第一终端设备建立第一连接。
可选的，该第一连接是AS连接和/或SLRB连接。
基于图14所示的方法，第一终端设备在建立了与第二终端设备的第一连接后，向第二终端设备发送该SCI和该SCI对应的业务数据，该SCI包括第一目标侧标识和通信类型，或该SCI包括通信类型，第二终端设备可以接收对应通信类型的业务数据，以降低第二终端设备的误收包率，进而提高第二终端设备的收包效率。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，上述第一终端设备、第二终端设备或者网络设备等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法操作，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对第一终端设备、第二终端设备或网络设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
比如，以采用集成的方式划分各个功能模块的情况下，图15示出了一种第一终端设备1500的结构示意图。该第一终端设备1500包括：通信模块1501和发送模块1502。该通信模块1501，用于与网络设备和第二终端通信；该发送模块1502，用于向第二终端设备发送侧行链路控制信息SCI和业务数据；其中，所述SCI包括第一目标侧标识和通信类型，或包括所述通信类型。
可选的，如图16所示，该第一终端设备1500还包括确定模块1503。该确定模块 1503，用于根据所述第二目标侧标识和所述通信类型确定所述业务数据，该第二目标侧标识用于标识该业务数据，该第二目标侧标识和该第一目标侧标识存在对应关系。
可选的，如图17所示，该第一终端设备1500还包括接收模块1504。该接收模块1504，用于从网络设备接收第一配置信息；其中，该第一配置信息中包括第二目标侧标识和该通信类型、以及与该第二目标侧标识和该通信类型对应的第二配置信息，其中，该第二目标侧标识用于标识该业务数据，该第二配置信息包括侧行链路配置信息和/或调度资源，该侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，该调度资源包括与该第二目标侧标识和/或该通信类型对应的传输资源；或者，该第一配置信息中包括该通信类型、以及与该通信类型对应的第二配置信息，其中，该第二目标侧标识用于标识该业务数据，该第二配置信息包括侧行链路配置信息和/或调度资源，该侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，该调度资源包括与该第二目标侧标识和/或该通信类型对应的传输资源；或者，该第一配置信息中包括第二目标侧标识和该通信类型、与该第二目标侧标识和该通信类型对应的第二配置信息、QoS信息、以及与QoS信息对应的侧行链路无线承载SLRB的配置信息，其中，该第二目标侧标识用于标识该业务数据，该第二配置信息包括侧行链路配置信息和/或调度资源，该侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，该调度资源包括与该第二目标侧标识和/或该通信类型对应的传输资源；或者，该第一配置信息中包括该通信类型、与该通信类型对应的第二配置信息、QoS信息、以及与QoS信息对应的侧行链路无线承载SLRB的配置信息，其中，该第二目标侧标识用于标识该业务数据，该第二配置信息包括侧行链路配置信息和/或调度资源，该侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，该调度资源包括与该第二目标侧标识和/或该通信类型对应的传输资源；或者，该第一配置信息中包括QoS信息、以及与QoS信息对应的侧行链路无线承载SLRB的配置信息。
可选的，该第一配置信息为***信息块SIB、无线资源控制RRC信令、媒介访问控制MAC信令、下行控制信息DCI、非接入层NAS信令或V3接口消息。
可选的，如图18所示，该第一终端设备1500还包括存储模块1505。该存储模块1505，用于存储第一配置信息；其中，该第一配置信息中包括第二目标侧标识和该通信类型、以及与该第二目标侧标识和该通信类型对应的第二配置信息，其中，该第二目标侧标识用于标识该业务数据，该第二配置信息包括侧行链路配置信息和/或调度资源，该侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，该调度资源包括与该第二目标侧标识和/或该通信类型对应的传输资源；或者，该第一配置信息中包括该通信类型、以及与该通信类型对应的第二配置信息，其中，该第二目标侧标识用于标识该业务数据，该第二配置信息包括侧行链路配置信息和/或调度资源，该侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，该调度资源包括与该第二目标侧标识和/或该通信类型对应的传输资源；或者，该第一配置信息中包括第二目标侧标识和该通信类型、与该第二目标侧标识和该通信类型对应的第二配置信息、QoS信息、以及与QoS信息对应的侧行链路无线承载SLRB的配置信息，其中，该第二目标侧标识用于标识该业务数据，该第二配置信息包括侧行链路配置信息和/或调度资源，该侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，该调度 资源包括与该第二目标侧标识和/或该通信类型对应的传输资源；或者，该第一配置信息中包括该通信类型、与该通信类型对应的第二配置信息、QoS信息、以及与QoS信息对应的侧行链路无线承载SLRB的配置信息，其中，该第二目标侧标识用于标识该业务数据，该第二配置信息包括侧行链路配置信息和/或调度资源，该侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，该调度资源包括与该第二目标侧标识和/或该通信类型对应的传输资源；或者，该第一配置信息中包括QoS信息、以及与QoS信息对应的侧行链路无线承载SLRB的配置信息。
可选的，该发送模块1502，还用于向该网络设备发送业务信息；其中，该业务信息包括：该通信类型。
可选的，该发送模块1502，还用于向该网络设备发送缓存状态报告BSR；其中，该BSR中包括该第二目标侧标识和该通信类型，或包括该通信类型。
可选的，该发送模块1502，还用于向该网络设备发送辅助信息；其中，该辅助信息中包括业务模型信息及该通信类型。
可选的，该发送模块1502，还用于向该网络设备发送该QoS信息；其中，该QoS信息中包括该第二目标侧标识和该通信类型，或者，包括该通信类型。
可选的，该接收模块1504，还用于从该网络设备接收SLRB的配置信息；其中，该SLRB的配置信息包括与该第二目标侧标识和/或该通信类型对应的SLRB配置；该SLRB配置包括服务质量流QoS flow到侧行链路数据无线承载SL-DRB的映射关系、包数据汇聚协议PDCP配置，无线链路控制RLC配置和逻辑信道LCH配置中的至少一个。
可选的，该发送模块1502，还用于向该第二终端设备发送该SLRB的配置信息。
可选的，如图19所示，该第一终端设备1500还包括建立模块1506。该建立模块1506，用于若该第一终端设备没有与该第二终端设备建立与该第二目标侧标识和/或该通信类型对应的第一连接，该第一终端设备建立第一连接；其中，该第一连接为接入层AS连接和/或侧行链路无线承载SLRB连接。
其中，上述方法实施例涉及的各操作的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该第一终端设备1500以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到该第一终端设备1500可以采用图5所示的形式。
比如，图5中的处理器501可以通过调用存储器504中存储的计算机执行指令，使得第一终端设备1500执行上述方法实施例中的通信方法。
示例性的，图19中的通信模块1501、发送模块1502、确定模块1503、接收模块1504、存储模块1505和建立模块1506的功能/实现过程可以通过图5中的处理器501调用存储器504中存储的计算机执行指令来实现。或者，图19中的通信模块1501、确定模块1503、存储模块1505和建立模块1506的功能/实现过程可以通过图5中的处理器501调用存储器504中存储的计算机执行指令来实现，图19中的发送模块1502和接收模块1504的功能/实现过程可以通过图5中的通信接口503来实现。
由于本实施例提供的第一终端设备1500可执行上述的通信方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
或者，比如，以采用集成的方式划分各个功能模块的情况下，图20示出了一种第二终端设备2000的结构示意图。该第二终端设备2000包括：通信模块2001和接收模块2002。该通信模块2001，用于与网络设备和第一终端设备通信；该接收模块2002，用于接收第一终端设备发送的侧行链路控制信息SCI和业务数据；其中，该SCI包括第一目标侧标识和通信类型，或包括通信类型。
可选的，如图21所示，该第二终端设备2000还包括：确定模块2003。该确定模块2003，用于根据该SCI包括的通信类型、以及该第二终端设备支持的通信类型的能力，确定接收该业务数据；或者，该确定模块2003，用于根据该SCI包括的第一目标侧标识和通信类型、以及该第二终端设备支持的第一目标侧标识和通信类型的能力，确定接收该业务数据。
可选的，该接收模块2002，还用于从网络设备接收第一配置信息；其中，该第一配置信息中包括第二目标侧标识和该通信类型、以及与该第二目标侧标识和该通信类型对应的第二配置信息，其中，该第二目标侧标识用于标识该业务数据，该第二配置信息包括侧行链路配置信息和/或调度资源，该侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，该调度资源包括与该第二目标侧标识和/或该通信类型对应的传输资源；或者，该第一配置信息中包括该通信类型、以及与该通信类型对应的第二配置信息，其中，该第二目标侧标识用于标识该业务数据，该第二配置信息包括侧行链路配置信息和/或调度资源，该侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，该调度资源包括与该第二目标侧标识和/或该通信类型对应的传输资源；或者，该第一配置信息中包括第二目标侧标识和该通信类型、与该第二目标侧标识和该通信类型对应的第二配置信息、QoS信息、以及与QoS信息对应的侧行链路无线承载SLRB的配置信息，其中，该第二目标侧标识用于标识该业务数据，该第二配置信息包括侧行链路配置信息和/或调度资源，该侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，该调度资源包括与该第二目标侧标识和/或该通信类型对应的传输资源；或者，该第一配置信息中包括该通信类型、与该通信类型对应的第二配置信息、QoS信息、以及与QoS信息对应的侧行链路无线承载SLRB的配置信息，其中，该第二目标侧标识用于标识该业务数据，该第二配置信息包括侧行链路配置信息和/或调度资源，该侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，该调度资源包括与该第二目标侧标识和/或该通信类型对应的传输资源；或者，该第一配置信息中包括QoS信息、以及与QoS信息对应的侧行链路无线承载SLRB的配置信息。
可选的，该第一配置信息为***信息块SIB、无线资源控制RRC信令、MAC信令、下行控制信息DCI、非接入层NAS信令或V3接口消息。
可选的，该接收模块2002，还用于从该第一终端设备接收侧行链路无线承载SLRB的配置信息；其中，该SLRB的配置信息包括与第二目标侧标识和/或该通信类型对应的SLRB配置；该SLRB配置包括服务质量流QoS flow到侧行链路数据无线承载SL-DRB的映射关系、包数据汇聚协议PDCP配置，无线链路控制RLC配置和逻辑信 道LCH配置中的至少一个。
可选的，如图22所示，该第二终端设备2000还包括：建立模块2004。该建立模块2004，用于若该第二终端设备没有与该第一终端设备建立与第二目标侧标识和/或该通信类型对应的第一连接，建立第一连接；其中，该第一连接为接入层AS连接和/或侧行链路无线承载SLRB连接。
其中，上述方法实施例涉及的各操作的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该第二终端设备2000以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到该第二终端设备2000可以采用图5所示的形式。
比如，图5中的处理器501可以通过调用存储器504中存储的计算机执行指令，使得第二终端设备2000执行上述方法实施例中的通信方法。
示例性的，图22中的通信模块2001、接收模块2002、确定模块2003和建立模块2004的功能/实现过程可以通过图5中的处理器501调用存储器504中存储的计算机执行指令来实现。或者，图22中的确定模块2003和建立模块2004的功能/实现过程可以通过图5中的处理器501调用存储器504中存储的计算机执行指令来实现，图22中的通信模块2001、接收模块2002的功能/实现过程可以通过图5中的通信接口503来实现。
由于本实施例提供的第二终端设备2000可执行上述的通信方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
或者，比如，以采用集成的方式划分各个功能模块的情况下，图23示出了一种网络设备2300的结构示意图。该网络设备2300包括：通信模块2301和发送模块2302。该通信模块2301，用于与第一终端设备和第二终端设备通信；该发送模块2302，用于向第一终端设备和/或第二终端设备发送第一配置信息，其中，该第一配置信息中包括第二目标侧标识和该通信类型、以及与该第二目标侧标识和该通信类型对应的第二配置信息，其中，该第二目标侧标识用于标识该业务数据，该第二配置信息包括侧行链路配置信息和/或调度资源，该侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，该调度资源包括与该第二目标侧标识和/或该通信类型对应的传输资源；或者，该第一配置信息中包括该通信类型、以及与该通信类型对应的第二配置信息，其中，该第二目标侧标识用于标识该业务数据，该第二配置信息包括侧行链路配置信息和/或调度资源，该侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，该调度资源包括与该第二目标侧标识和/或该通信类型对应的传输资源；或者，该第一配置信息中包括第二目标侧标识和该通信类型、与该第二目标侧标识和该通信类型对应的第二配置信息、QoS信息、以及与QoS信息对应的侧行链路无线承载SLRB的配置信息，其中，该第二目标侧标识用于标识该业务数据，该第二配置信息包括侧行链路配置信息和/或调度资源，该侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，该调度资源包括与该第二目标侧标识和/或该通信类型对应的传输资源；或者，该第一配置信息中包括该通信类型、与该通信类型对应的第二配置信息、 QoS信息、以及与QoS信息对应的侧行链路无线承载SLRB的配置信息，其中，该第二目标侧标识用于标识该业务数据，该第二配置信息包括侧行链路配置信息和/或调度资源，该侧行链路配置信息用于指示同步配置、发送方式或传输资源的位置，该调度资源包括与该第二目标侧标识和/或该通信类型对应的传输资源；或者，该第一配置信息中包括QoS信息、以及与QoS信息对应的侧行链路无线承载SLRB的配置信息。
可选的，该第一配置信息为***信息块SIB、无线资源控制RRC信令、媒介访问控制MAC信令、下行控制信息DCI、非接入层NAS信令或V3接口消息。
可选的，如图24所示，该网络设备还包括：接收模块2303。该接收模块2303，用于从该第一终端设备接收业务信息；其中，该业务信息包括：该通信类型。
可选的，该接收模块2303，还用于从该第一终端设备接收缓存状态报告BSR；其中，该BSR中包括第二目标侧标识和该通信类型，或包括该通信类型。
可选的，该接收模块2303，还用于从该第一终端设备接收辅助信息；其中，该辅助信息中包括业务模型及该通信类型。
可选的，该接收模块2303，还用于从该第一终端设备接收QoS信息；其中，该QoS信息中包括第二目标侧标识和该通信类型，或者，包括该通信类型。
可选的，该发送模块2302，还用于根据该QoS信息，向该第一终端设备发送侧行链路无线承载SLRB的配置信息；其中，该SLRB的配置信息包括与第二目标侧标识和/或该通信类型对应的SLRB配置；该SLRB配置包括服务质量流QoS flow到侧行链路数据无线承载SL-DRB的映射关系、包数据汇聚协议PDCP配置，无线链路控制RLC配置、逻辑信道LCH配置中的至少一个。
其中，上述方法实施例涉及的各操作的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该网络设备2300以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到该网络设备2300可以采用图5所示的形式。
比如，图5中的处理器501可以通过调用存储器504中存储的计算机执行指令，使得网络设备2300执行上述方法实施例中的通信方法。
示例性的，图24中的通信模块2301、发送模块2302和接收模块2303的功能/实现过程可以通过图5中的处理器501调用存储器504中存储的计算机执行指令来实现。或者，图24中的通信模块2301的功能/实现过程可以通过图5中的处理器501调用存储器504中存储的计算机执行指令来实现，图24中的发送模块2302和接收模块2303的功能/实现过程可以通过图5中的通信接口503来实现。
由于本实施例提供的网络设备2300可执行上述的通信方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例的流程或功能。计算机可以是通用计算机、 专用计算机、计算机网络、或者其他可编程装置。计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看附图、公开内容、以及所附权利要求书，可理解并实现公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或操作，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (18)

  1. 一种通信方法，其特征在于，所述方法包括：
    第一终端设备的媒体接入控制MAC实体选择一个通信类型对应的目标侧标识；
    所述第一终端设备的MAC实体获取第一逻辑信道LCH，所述第一LCH为所述目标侧标识和所述通信类型对应的有数据的LCH中，优先级最高的LCH；
    所述第一终端设备的MAC实体为所述第一LCH中的数据分配传输资源。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一终端设备的MAC实体将目标侧标识和通信类型相同的LCH封装在一个传输块TB中发送。
  3. 根据权利要求1或2所述的方法，其特征在于，所述方法还包括：
    若所述第一终端设备的MAC实体将传输资源分配给所述第一LCH后还有剩余的传输资源，所述第一终端设备将目标侧标识和通信类型相同的LCH按逻辑信道优先级降序排序，并按照该顺序为剩余的LCH中的数据包分配传输资源。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述第一终端设备的MAC实体选择一个通信类型对应的目标侧标识，包括：
    所述第一终端设备的MAC实体确定具有最高优先级的有数据的LCH所对应的通信类型以及目标侧标识；
    所述第一终端设备的MAC实体将确定的所述目标侧标识，作为所述通信类型对应的目标侧标识。
  5. 根据权利要求1-4任一项所述的方法，其特征在于，所述通信类型包括单播通信、组播通信或广播通信；所述目标侧标识包括目的层2标识和/或目的层1标识。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述方法还包括：
    所述第一终端设备向网络设备发送辅助信息，所述辅助信息指示业务模型信息及通信类型；
    所述第一终端设备从所述网络设备接收调度资源，所述调度资源包括用于发送业务数据的侧行链路的传输资源。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，所述方法还包括：
    所述第一终端设备向第二终端设备发送侧行链路控制信息和业务数据，其中，所述侧行链路控制信息包括第一目标侧标识和通信类型，或包括所述通信类型。
  8. 一种通信装置，其特征在于，包括：
    用于选择一个通信类型对应的目标侧标识的模块；
    用于获取第一逻辑信道LCH的模块，所述第一LCH为所述目标侧标识和所述通信类型对应的有数据的LCH中，优先级最高的LCH；
    用于为所述第一LCH中的数据分配传输资源的模块。
  9. 根据权利要求8所述的通信装置，其特征在于，所述通信装置还包括：
    用于将目标侧标识和通信类型相同的LCH封装在一个传输块TB中发送的模块。
  10. 根据权利要求8或9所述的通信装置，其特征在于，若将传输资源分配给所述第一LCH后还有剩余的传输资源，所述通信装置还包括用于将目标侧标识和通信类型相同的LCH按逻辑信道优先级降序排序，并按照该顺序为剩余的LCH中的数据包 分配传输资源的模块。
  11. 根据权利要求8-10任一项所述的通信装置，其特征在于，所述通信装置还包括：
    用于确定具有最高优先级的有数据的LCH所对应的通信类型以及目标侧标识的模块；
    用于将确定的所述目标侧标识，作为所述通信类型对应的目标侧标识的模块。
  12. 根据权利要求8-11任一项所述的通信装置，其特征在于，所述通信类型包括单播通信、组播通信或广播通信；所述目标侧标识包括目的层2标识和/或目的层1标识。
  13. 根据权利要求8-12任一项所述的通信装置，其特征在于，所述通信装置还包括：
    用于向网络设备发送辅助信息的模块，所述辅助信息指示业务模型信息及通信类型；
    用于从所述网络设备接收调度资源的模块，所述调度资源包括用于发送业务数据的侧行链路的传输资源。
  14. 根据权利要求8-13任一项所述的通信装置，其特征在于，所述通信装置还包括：
    用于向第二终端设备发送侧行链路控制信息和业务数据的模块，其中，所述侧行链路控制信息包括第一目标侧标识和通信类型，或包括所述通信类型。
  15. 一种通信装置，包括：至少一个处理器，至少一个存储器以及通信接口，其特征在于，
    所述通信接口、所述至少一个存储器与所述至少一个处理器耦合；所述第一终端设备通过所述通信接口与其他设备通信，所述至少一个存储器用于存储计算机程序，使得所述计算机程序被所述至少一个处理器执行时实现如权利要求1-7中任一项所述的方法。
  16. 一种计算机存储介质，其特征在于，所述计算机可读存储介质中存储有程序指令，所述程序指令运行时，以实现权利要求1至7中任一所述的方法。
  17. 一种计算机程序产品，所述计算机程序产品中包括计算机程序代码，其特征在于，当所述计算机程序代码在计算机上运行时，使得计算机实现权利要求1至7中任一项所述的方法。
  18. 一种芯片，其特征在于，包括：处理器，所述处理器与存储器耦合，所述存储器用于存储程序或指令，当所述程序或指令被所述处理器执行时，使得所述芯片执行如权利要求1至7中任一项所述的方法。
PCT/CN2020/081882 2019-03-28 2020-03-27 通信方法及设备 WO2020192777A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20777503.2A EP3937577A4 (en) 2019-03-28 2020-03-27 METHOD AND COMMUNICATION DEVICE
US17/487,729 US20220022168A1 (en) 2019-03-28 2021-09-28 Communication method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910245325.9A CN111757513B (zh) 2019-03-28 2019-03-28 通信方法及设备
CN201910245325.9 2019-03-28

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/487,729 Continuation US20220022168A1 (en) 2019-03-28 2021-09-28 Communication method and device

Publications (1)

Publication Number Publication Date
WO2020192777A1 true WO2020192777A1 (zh) 2020-10-01

Family

ID=72608611

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/081882 WO2020192777A1 (zh) 2019-03-28 2020-03-27 通信方法及设备

Country Status (4)

Country Link
US (1) US20220022168A1 (zh)
EP (1) EP3937577A4 (zh)
CN (1) CN111757513B (zh)
WO (1) WO2020192777A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023107858A1 (en) * 2021-12-10 2023-06-15 Qualcomm Incorporated Techniques for indicating a sidelink receiver

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111918401B (zh) * 2019-05-10 2024-02-20 华硕电脑股份有限公司 报告侧链路承载配置的用户设备能力信息的方法和设备
US11304102B2 (en) * 2019-07-16 2022-04-12 Hannibal Ip Llc Method and apparatus for sidelink operation
EP3981216A4 (en) * 2019-08-15 2022-08-17 LG Electronics Inc. ASSIGNMENT OF LOWER AND UPPER IDENTIFIERS FOR SIDELINK TRANSMISSION
US12022413B2 (en) * 2020-08-27 2024-06-25 Qualcomm Incorporated Receiver timing adjustment
CN114448576A (zh) * 2020-11-03 2022-05-06 ***通信有限公司研究院 一种数据重传的方法、装置及设备
CN116548035A (zh) * 2021-03-26 2023-08-04 Oppo广东移动通信有限公司 侧行链路通信方法和终端设备
CN115347989B (zh) * 2021-05-14 2024-02-27 维沃移动通信有限公司 资源确定方法、装置及通信设备
CN113810921B (zh) * 2021-09-18 2024-04-09 杭州阿里云飞天信息技术有限公司 数据传输方法、设备及存储介质
WO2023155096A1 (en) * 2022-02-17 2023-08-24 Huawei Technologies Co.,Ltd. Method and apparatus for reporting physical layer information

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107079530A (zh) * 2015-01-30 2017-08-18 松下电器（美国）知识产权公司 用于侧行链路逻辑信道的逻辑信道优先级排序过程
US20180368167A1 (en) * 2017-06-16 2018-12-20 Samsung Electronics Co., Ltd. Method for supporting multiple scheduling requests in next-generation mobile communication system

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102130296B1 (ko) * 2013-07-31 2020-07-08 삼성전자주식회사 단말 대 단말 통신을 지원하는 단말 및 그 동작 방법
EP3206452B1 (en) * 2016-02-10 2019-10-16 Panasonic Intellectual Property Corporation of America Priority-optimized sidelink data transfer in the case of autonomous resource allocation in lte prose communication
CN110178435B (zh) * 2017-01-06 2022-10-04 Lg电子株式会社 用于发送数据单元的方法和用户设备
CN108633074B (zh) * 2017-03-23 2022-05-13 华硕电脑股份有限公司 无线通信***中报告侧链路服务的辅助信息的方法和设备
CN109286979B (zh) * 2017-07-19 2021-05-07 电信科学技术研究院 一种资源分配方法、装置及终端
US11051304B2 (en) * 2017-07-25 2021-06-29 Lg Electronics Inc. Method and apparatus for selecting carrier for sidelink transmission in wireless communication system
US11452015B2 (en) * 2018-08-10 2022-09-20 Lg Electronics Inc. Method and apparatus for triggering transmission carrier reselection procedure for deactivated duplication in wireless communication system
WO2020076071A1 (ko) * 2018-10-08 2020-04-16 삼성전자 주식회사 무선 통신 시스템에서 단말 간 유니캐스트 전송을 지원하기 위한 장치 및 방법
WO2020091443A1 (en) * 2018-11-01 2020-05-07 Lg Electronics Inc. Deactivation of configured grant and initiation of connection request upon detection of sidelink failure

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107079530A (zh) * 2015-01-30 2017-08-18 松下电器（美国）知识产权公司 用于侧行链路逻辑信道的逻辑信道优先级排序过程
US20180368167A1 (en) * 2017-06-16 2018-12-20 Samsung Electronics Co., Ltd. Method for supporting multiple scheduling requests in next-generation mobile communication system

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
MEDIATEK INC.: "3GPP TSG-RAN WG2 Meeting #108 R2-1914654", REMAINING ISSUES OF SL LCP, 8 November 2019 (2019-11-08), XP051816676, DOI: 20200519103529PX *
OPPO: "3GPP TSG-RAN WG2 Meeting #104 R2-1816340", DISCUSSION ON UP ASPECTS OF UNICAST AND GROUP-CAST FOR NR-V2X, 2 November 2018 (2018-11-02), XP051480309, DOI: 20200519101432Y *
See also references of EP3937577A4 *
ZTE: "3GPP TSG-RAN WG2 Meeting #101bis R2-1804509", DISCUSSION ON LCP PROCEDURE FOR PC5 CA, 6 April 2018 (2018-04-06), XP051415540, DOI: 20200519101344Y *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023107858A1 (en) * 2021-12-10 2023-06-15 Qualcomm Incorporated Techniques for indicating a sidelink receiver

Also Published As

Publication number Publication date
EP3937577A1 (en) 2022-01-12
EP3937577A4 (en) 2022-06-22
CN111757513B (zh) 2022-03-29
CN111757513A (zh) 2020-10-09
US20220022168A1 (en) 2022-01-20

Similar Documents

Publication Publication Date Title
WO2020192777A1 (zh) 通信方法及设备
US12010592B2 (en) Sidelink communications method and apparatus
US10411789B2 (en) Scheduling mechanism for prose relays serving remote UEs
US10356758B2 (en) Method and apparatus for requesting and modifying resource configuration in a wireless communication system
RU2728541C1 (ru) Улучшенная поддержка качества обслуживания для передач v2x
EP3422789B1 (en) Method for transmitting downlink control information for sidelink scheduling in wireless communication system and terminal using same
EP3437402B1 (en) Improved semi-persistent resource allocation for v2v traffic
US10716165B2 (en) Methods and apparatus for releasing a sidelink radio bearer for D2D communication system
US10154425B2 (en) Method for a configuration error management for a sidelink radio bearer and device therefor
WO2019153935A1 (zh) 传输方式确定方法及装置，存储介质和电子装置
KR20210135336A (ko) V2x(vehicle-to-everything) 통신을 위한 rrc(radio resource control) 연결을 개시하는 방법 및 장치
WO2020087365A1 (zh) 边链路数据的发送和配置方法以及装置
WO2020199957A1 (zh) 一种重传资源的调度方法及设备
WO2018059518A1 (zh) 一种数据传输方法、装置和***
CN112703716B (zh) 共享无线承载以及终端设备无线标识和无线接入网路径的管理
US20230370902A1 (en) Relay UE Selection for Transmission Over Sidelink
EP3849237B1 (en) Method and apparatus for requesting sidelink transmission resources in a wireless communication system
WO2020119013A1 (zh) 侧链通信方法和装置
US20210315053A1 (en) Method and device for transmitting and receiving data in wireless communication system
KR20200072522A (ko) 셀룰러 통신을 위한 개선된 지원형 재전송 기법
WO2013159678A1 (zh) 数据传输方法、用户设备、基站和***
WO2021161602A1 (ja) 端末及び通信方法
WO2023185956A1 (zh) 基于侧行链路的通信方法、装置、存储介质和芯片***
WO2022170545A1 (zh) 一种无线链路的重建方法和装置
WO2023213267A1 (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: 20777503

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020777503

Country of ref document: EP

Effective date: 20211005