Communication method and device

Abstract

An embodiment of the present application provides a communication method and apparatus to meet the QoS requirements of services of different communication types. The method comprises: an application layer entity of a first terminal device submits communication type information and a target side identifier to a control layer entity of the first terminal device, and the control layer entity of the first terminal device establishes a radio bearer group of a side link corresponding to the communication type according to the communication type information, and the radio bearer group of the side link corresponds to the target side identifier. Subsequently, after the application layer entity of the first terminal device submits a data packet and a first target side identifier to the SDAP layer entity of the first terminal device, the SDAP layer entity of the first terminal device can submit the data packet to the first radio bearer group corresponding to the first target side identifier for processing according to the correspondence between the radio bearer group of the side link and the target side identifier.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and in particular to a communication method and apparatus. Background Art

[0002] In the vehicle-to-everything (V2X) communication system, the transmitting and receiving devices maintain a set of sidelink radio barriers (SLRBs) for each type of V2X service. Each set of SLRBs includes one or more SLRBs, each of which corresponds to a packet data convergence protocol (PDCP) layer entity, a radio link control (RLC) layer entity, and a sidelink logical channel (SL LCH). The configuration of each SLRB (including PDCP entity configuration, RLC entity configuration, and LCH configuration, etc.) is the same.

[0003] When the application layer entity of the transmitting device generates a data packet corresponding to a certain type of V2X service and submits it to the lower layer entity, the data packet may carry a V2X service identifier (such as a destination layer 2 identifier (destination layer-2id)) and priority parameters for identifying the type of V2X service. The lower layer entity of the transmitting device can submit the data packet to the SLRB corresponding to the V2X service identifier and priority parameters in the transmitting device based on the mapping relationship between the V2X service identifier and priority parameters and the SLRB; the SLRB in the transmitting device processes the received data packet and submits the processed data to the media access control (MAC) layer entity of the transmitting device; the MAC layer entity of the transmitting device processes the data packet processed by the SLRB, generates a MAC protocol data unit (PDU) including a source layer 2 identifier (source layer-2ID), a destination layer-2id and a logical channel identity (LCID) of the SL LCH, and submits the MAC PDU to the physical layer entity (PHY layer entity) of the transmitting device; the PHY layer entity of the transmitting device The PDU is sent to the receiving device through a direct connection channel between the transmitting device and the receiving device (such as the PC5 port). After the PHY layer entity of the receiving device receives the MAC PDU, it delivers the MAC service data unit (SDU) contained in the MAC PDU to the SLRB corresponding to the V2X service in the receiving device for processing based on the source layer-2 ID, destination layer-2 ID, and LCID carried in the MAC PDU.

[0004] Since the configurations of the SLRBs maintained by the transmitting and receiving devices are the same, all types of V2X services are processed using the same SLRB configuration during transmission. However, the quality of service (QoS) requirements of different V2X services may be different. For example, some V2X services require low latency and high reliability, while some V2X services have low latency requirements. In this case, if all V2X services are processed using the same SLRB configuration, it is impossible to control and guarantee the service quality of different V2X services, that is, it is impossible to meet the QoS requirements of different V2X services. Summary of the Invention

[0005] The embodiments of the present application provide a communication method and apparatus to meet the QoS requirements of services of different communication types.

[0006] To achieve the above objectives, the present invention provides the following technical solutions:

[0007] In a first aspect, an embodiment of the present application provides a communication method, the method comprising: an application layer entity of a first terminal device submits communication type information and a target side identifier to a control layer entity of the first terminal device, and the control layer entity of the first terminal device establishes a wireless bearer group of a side link corresponding to the communication type according to the communication type information; wherein the communication type information includes or is used to indicate the communication type to be performed by the first terminal device, the communication type is unicast communication or multicast communication, the target side identifier is used to identify unicast communication or multicast communication, the wireless bearer group of the side link corresponds to the target side identifier, and the side link is a wireless communication link between the first terminal device and the second terminal device.

[0008] Optionally, the configuration information of different radio bearer groups in the sidelink radio bearer group may be different, for example, the configuration information of the radio bearer group corresponding to multicast communication may be different from the configuration of the radio bearer group corresponding to unicast communication.

[0009] Based on the method provided in the first aspect, different wireless bearer groups can be established for different communication types. Subsequently, when data of a certain communication type is sent downward, the data can be processed by the wireless bearer group corresponding to the communication type, so that data of different communication types can be processed by different wireless bearer groups, and the service quality requirements of data of different communication types can be controlled and guaranteed.

[0010] In one possible design, the configuration information of the sidelink radio bearer group is pre-stored on the first terminal device; alternatively, the method further includes: the first terminal device receiving the configuration information of the sidelink radio bearer group sent by the radio access network device. Based on this method, the terminal device can obtain the configuration information of the established radio bearer group from the pre-stored configuration information of the sidelink radio bearer group, or dynamically obtain the configuration information of the radio bearer group from the radio access network device, resulting in a flexible and simple acquisition method.

[0011] In one possible design, the control layer entity of the first terminal device sends a first message to the control layer entity of the second terminal device, and receives a first response sent by the second terminal device. The first terminal device and the second terminal device are currently conducting or are about to conduct unicast communication or multicast communication, and the first message includes the configuration information of the radio bearer group of the side link. Based on this method, the terminal device can send the configuration information of the radio bearer group of the side link it has established to other members with whom it is currently conducting or is about to conduct unicast communication or multicast communication, so that other members do not need to obtain the configuration information of the radio bearer group through other means when establishing the radio bearer group of the side link corresponding to the communication type, thereby reducing the signaling overhead caused by other members obtaining the configuration information of the radio bearer group.

[0012] In one possible design, the method further includes: if the control layer entity of the first terminal device does not receive the first response for a period greater than or equal to a set time, the control layer entity of the first terminal device resends the first message to the control layer entity of the second terminal device. Based on this method, it can be ensured that the terminal device sends the configuration information of the radio bearer group to other members of the unicast communication or multicast communication.

[0013] In one possible design, the method further includes: a control layer entity of the first terminal device determines a security mode configuration, sends a first message and the security mode configuration to a PDCP layer entity of the first terminal device, and the PDCP layer entity of the first terminal device performs confidentiality protection and integrity protection on the first message according to the security mode configuration and then sends the message to the control layer entity of the second terminal device. The security mode configuration includes relevant configurations for the first terminal device to perform confidentiality protection and integrity protection on the first message. Based on this method, the security of the configuration information of the wireless bearer group sent by the terminal device to other members in unicast communication or multicast communication can be guaranteed.

[0014] In one possible design, the method also includes: the application layer entity of the first terminal device submits a data packet and a first target side identifier to the SDAP layer entity of the first terminal device, the SDAP layer entity of the first terminal device determines the first radio bearer group of the side link corresponding to the first target side identifier based on the correspondence between the radio bearer group of the side link and the target side identifier, submits the data packet to the PDCP layer entity corresponding to the first radio bearer group of the side link, the PDCP layer entity processes the data packet to obtain a PDCP protocol data unit PDU, submits the PDCP PDU to the radio link control RLC layer entity corresponding to the first radio bearer group of the side link, the RLC layer entity processes the PDCP PDU to obtain an RLC PDU, submits the RLC PDU to the media access control MAC layer entity of the first terminal device, the MAC layer entity of the first terminal device processes the RLC PDU to obtain a MAC PDU, and submits the MAC PDU to the physical PHY layer entity of the first terminal device.

[0015] Exemplarily, the data packet submitted by the application layer entity of the first terminal device to the SDAP layer entity of the first terminal device may be a data packet under unicast communication or a data packet under multicast communication. The first target side identifier may be used to identify the communication type corresponding to the data packet. The first target side identifier may be included in the data packet submitted to the SDAP layer entity of the first terminal device, or may be included in other messages other than the data packet submitted to the SDAP layer entity of the first device, without limitation.

[0016] Based on this method, it can be ensured that the data packets transmitted in unicast communication (or multicast communication) are delivered to the wireless bearer group corresponding to the unicast communication (or multicast communication) for processing, that is, different wireless bearer groups are used to process data packets under different communication types, thereby ensuring the QoS requirements of data packets of different communication types.

[0017] In one possible design, the method further includes: an application layer entity of the first terminal device submitting a first quality of service QoS parameter to an SDAP layer entity of the first terminal device; the SDAP layer entity of the first terminal device determines the first radio bearer corresponding to the first QoS parameter in the first radio bearer group of the side link based on the correspondence between the QoS parameter and the radio bearer of the side link, and submits the data packet to the PDCP layer entity corresponding to the first radio bearer. Based on this method, the radio bearer groups and different QoS parameters within the radio bearer group can be used to distinguish the radio bearers that process the data packets based on the granularity of QoS requirements. When the data packet is processed by the radio bearer group, the radio bearer corresponding to the QoS parameter of the data packet within the radio bearer group is used for processing to meet the QoS requirements of the data packet.

[0018] In one possible design, the method further includes: a MAC layer entity of the first terminal device submitting any one or more of a first target side identifier, a first QoS parameter, and communication type information to a PHY layer entity of the first terminal device. Based on this method, the opposite device can determine whether a received data packet is its own data packet, determine the communication type to which the received data packet belongs, and configure a radio bearer group corresponding to the QoS parameters of the received data packet based on the target side identifier, QoS parameters, and communication type information.

[0019] In one possible design, the method further includes: an application layer entity of the first terminal device broadcasting a request to establish unicast communication or multicast unicast communication or a multicast communication establishment request, and receiving a setup response for indicating the establishment of unicast communication or multicast communication with the first terminal device. Based on this method, unicast communication or multicast communication can be established based on the application layer entity.

[0020] In one possible design, the method further includes: a control layer entity of the first terminal device receiving a request message for requesting to establish unicast communication or multicast communication with the first terminal device, and sending a response message for instructing the first terminal device to determine to establish unicast communication or multicast communication. Based on this method, unicast communication or multicast communication can be established through the control layer entity.

[0021] In one possible design, the method further includes: an application layer entity of the first terminal device or a control layer entity of the first terminal device broadcasting a discovery message for discovering the first terminal device; illustratively, the discovery message is an RRC message. Based on this method, other devices in the network can be informed of the existence of the terminal device, facilitating other devices in the network to send the terminal device.

[0022] In a second aspect, the present application provides a communication device, which may be a first terminal device or a chip or system on chip in the first terminal device. The communication device can implement the functions performed by the first terminal device in the above aspects or possible designs, and the functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. For example, the communication device may include: a processing module and a sending module; illustratively, the processing module has the functions of the application layer entity, control layer entity, SDAP layer entity, PDCP layer entity, RLC layer entity, and MAC layer entity in the first terminal device. The sending module has the functions of the PHY layer entity in the first terminal device, such as the sending module can send data or information to other devices outside the communication device.

[0023] A processing module is used to generate a target side identifier for identifying unicast communication or multicast communication, and establish a wireless bearer group of a side link corresponding to the communication type, wherein the wireless bearer group of the side link corresponds to the target side identifier, and the side link is a wireless communication link between a first terminal device and a second terminal device; the communication type is unicast communication or multicast communication.

[0024] For example, the specific implementation of the communication device can refer to the behavior function of the first terminal in the communication method provided in the first aspect or any possible design of the first aspect, and will not be repeated here. Therefore, the provided communication device can achieve the same beneficial effects as the first aspect or any possible design of the first aspect.

[0025] In a third aspect, a communication device is provided, comprising: a processor and a memory; the memory is used to store computer-executable instructions, and when the communication device is running, the processor executes the computer-executable instructions stored in the memory to enable the communication device to perform the communication method described in the first aspect or any possible design of the first aspect.

[0026] In a fourth aspect, a computer-readable storage medium is provided, which stores instructions. When the computer-readable storage medium is run on a computer, the computer can execute the communication method described in the first aspect or any possible design of the above aspects.

[0027] In a fifth aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute the communication method described in the first aspect or any possible design of the above aspects.

[0028] In a sixth aspect, a chip system is provided, which includes a processor and a communication interface, and is used to support a communication device to implement the functions involved in the above aspects. For example, the processor generates a target side identifier for identifying unicast communication or multicast communication, and establishes a radio bearer group for the side link corresponding to the communication type. In one possible design, the chip system also includes a memory, which is used to store program instructions and data necessary for the communication device. The chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0029] For example, the technical effects brought about by any design method in the third to sixth aspects can refer to the technical effects brought about by the above-mentioned first aspect or any possible design of the first aspect, and will not be repeated here.

[0030] In a seventh aspect, a communication method is provided, which also includes: an application layer entity of a first terminal device submits a data packet and a first target side identifier to an SDAP layer entity of the first terminal device, the SDAP layer entity of the first terminal device determines the first wireless bearer group of the side link corresponding to the first target side identifier based on the correspondence between the wireless bearer group of the side link and the target side identifier, and submits the data packet to the PDCP layer entity corresponding to the first wireless bearer group of the side link, the PDCP layer entity processes the data packet to obtain a PDCP protocol data unit PDU, and submits the PDCP PDU to the radio link control RLC layer entity corresponding to the first wireless bearer group of the side link, the RLC layer entity processes the PDCP PDU to obtain an RLC PDU, and submits the RLC PDU to the media access control MAC layer entity of the first terminal device, the MAC layer entity of the first terminal device processes the RLC PDU to obtain a MAC PDU, and submits the MAC PDU to the physical PHY layer entity of the first terminal device. Based on this method, it can be ensured that the data packets transmitted in unicast communication (or multicast communication) are delivered to the wireless bearer group corresponding to the unicast communication (or multicast communication) for processing, that is, different wireless bearer groups are used to process data packets under different communication types, thereby ensuring the QoS requirements of data packets of different communication types.

[0031] In one possible design, the method further includes: the application layer entity of the first terminal device submits a first quality of service QoS parameter to the SDAP layer entity of the first terminal device, determines the first radio bearer corresponding to the first QoS parameter in the first radio bearer group of the side link based on the correspondence between the QoS parameter and the radio bearer of the side link, and submits the data packet to the PDCP layer entity included in the first radio bearer. Based on this method, the radio bearer groups and different QoS parameters within the radio bearer group can be used to distinguish the radio bearers that process the data packets based on the granularity of QoS requirements. When the data packet is processed by the radio bearer group, the radio bearer corresponding to the QoS parameter of the data packet within the radio bearer group is used for processing to meet the QoS requirements of the data packet.

[0032] In one possible design, the method further includes: a MAC layer entity of the first terminal device submitting any one or more of a first target side identifier, a first QoS parameter, and communication type information to a PHY layer entity of the first terminal device. Based on this method, the opposite device can determine whether a received data packet is its own data packet, determine the communication type to which the received data packet belongs, and configure a wireless bearer corresponding to the QoS parameters of the received data packet based on the target side identifier, QoS parameters, and communication type information.

[0033] In an eighth aspect, the present application provides a communication device, which may be a first terminal device or a chip or system on chip in the first terminal device. The communication device may implement the functions performed by the first terminal device in the seventh aspect or each possible design of the seventh aspect. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. For example, the communication device may include: a processing module and a sending module; illustratively, the processing module integrates the functions of the application layer entity, the control layer entity, the SDAP layer entity, the PDCP layer entity, the RLC layer entity, and the MAC layer entity in the first terminal device, such as the processing module may include the application layer entity, the control layer entity, the SDAP layer entity, the PDCP layer entity, the RLC layer entity, and the MAC layer entity. The sending module has the functions of the PHY layer entity in the first terminal device.

[0034] The processing module is used to determine the first radio bearer group of the side link corresponding to the first target side identifier according to the correspondence between the radio bearer group of the side link and the target side identifier, and deliver the data packet to the Packet Data Convergence Protocol PDCP layer entity corresponding to the first radio bearer group of the side link; the PDCP layer entity processes the data packet to obtain a PDCP PDU, and delivers the PDCP PDU to the RLC layer entity corresponding to the first radio bearer group of the side link; the RLC layer entity processes the PDCP PDU to obtain an RLC PDU, and delivers the RLC PDU to the MAC layer entity of the first terminal device; the MAC layer entity of the first terminal device processes the RLC PDU to obtain a MAC PDU, and delivers the MAC PDU to the PHY layer entity of the first terminal device.

[0035] For example, the specific implementation of the communication device can refer to the behavior function of the first terminal device in the communication method provided in the seventh aspect or any possible design of the seventh aspect, and will not be repeated here. Therefore, the provided communication device can achieve the same beneficial effects as the seventh aspect or any possible design of the seventh aspect.

[0036] In the ninth aspect, a communication device is provided, comprising: a processor and a memory; the memory is used to store computer-executable instructions, and when the communication device is running, the processor executes the computer-executable instructions stored in the memory to enable the communication device to perform the communication method described in the seventh aspect or any possible design of the seventh aspect.

[0037] In the tenth aspect, a computer-readable storage medium is provided, which stores instructions. When the computer-readable storage medium is run on a computer, the computer can execute the communication method described in the seventh aspect or any possible design of the above aspects.

[0038] In the eleventh aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute the communication method described in the seventh aspect or any possible design of the above aspects.

[0039] In the twelfth aspect, a chip system is provided, which includes a processor and a communication interface, and is used to support the communication device to implement the functions involved in the above aspects. For example, the processor determines the first radio bearer group of the side link corresponding to the first target side identifier based on the correspondence between the radio bearer group of the side link and the target side identifier, and delivers the data packet to the first radio bearer group of the side link. In one possible design, the chip system also includes a memory, and the memory is used to store program instructions and data necessary for the communication device. The chip system can be composed of chips, and can also include chips and other discrete devices.

[0040] Among them, the technical effects brought about by any design method in the ninth to twelfth aspects can be referred to the technical effects brought about by the above-mentioned seventh aspect or any possible design of the seventh aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 A principle block diagram provided for an embodiment of the present application;

[0042] Figure 2 A schematic diagram of a system architecture provided in an embodiment of the present application;

[0043] Figure 3a A schematic diagram of unicast communication provided in an embodiment of the present application;

[0044] Figure 3b A schematic diagram of multicast communication provided in an embodiment of the present application;

[0045] Figure 4 A schematic diagram of the protocol stack provided in an embodiment of the present application;

[0046] Figure 5 A schematic diagram of the composition of a communication device provided in an embodiment of the present application;

[0047] Figure 6 A flow chart of a communication method provided in an embodiment of the present application;

[0048] Figure 7 A flow chart of another communication method provided in an embodiment of the present application;

[0049] Figure 8 A schematic diagram of another communication method provided in an embodiment of the present application;

[0050] Figure 9A flowchart for establishing unicast or multicast communication provided in an embodiment of the present application;

[0051] Figure 10 This invention provides a communication device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0052] The principle block diagram of the embodiment of the present application is as follows Figure 1 As shown, it can include: the transmitting device and the receiving device maintain different sidelink radio bearer groups for different communication types (unicast communication or multicast communication). The sidelink can be a wireless communication link between the transmitting device and the receiving device, and each radio bearer group has a different configuration. Subsequently, when the transmitting device transmits a data packet corresponding to unicast communication to the receiving device, the transmitting device uses the radio bearer group corresponding to unicast communication to process the data packet and then sends it to the receiving device. After the receiving device receives the data packet, it also uses the radio bearer group corresponding to unicast communication to process the data packet. Similarly, when the transmitting device transmits a data packet corresponding to multicast communication to the receiving device, the transmitting device uses the radio bearer group corresponding to multicast communication to process the data packet and then sends it to the receiving device. After the receiving device receives the data packet, it also uses the radio bearer group corresponding to multicast communication to process the data packet. In this way, data packets of different communication types are processed using radio bearer groups with different configurations, which can control and ensure the quality of service of data packets transmitted under different communication types.

[0053] Optionally, in an embodiment of the present application, a sending device and a receiving device are relative concepts. A sending device may refer to a device that sends a data packet, and a receiving device may refer to a device that receives a data packet.

[0054] Optionally, in the embodiments of the present application, the communication type may be other types of communication besides unicast communication or multicast communication, such as broadcast communication. The embodiments of the present application are described using unicast communication and multicast communication as examples. For other types of communication, the methods provided in the embodiments of the present application can be used to configure an appropriate radio bearer group for such communication.

[0055] Optionally, the wireless bearer group of the side link can be called an SLRB group or SLRBs or a wireless bearer group or an RB group. The communication method provided in the embodiment of the present application is introduced below by taking the wireless bearer group of the side link as an SLRB group or SLRBs as an example.

[0056] First, to facilitate understanding of the embodiments of the present application, some terms involved in the embodiments of the present application are described:

[0057] SLRBs: may include one or more independent radio bearers, which may be referred to as SLRBs. Each SLRB corresponds to a PDCP layer entity, one or more RLC layer entities, one or more LCHs, etc., or may be described as each SLRB including a PDCP layer entity, one or more RLC layer entities, and one or more LCHs, etc. In an embodiment of the present application, each SLRB adopts an independent set of configurations, and the configuration of each SLRB varies according to the 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 identifier, PDCP entity configuration, RLC entity configuration, LCH configuration, etc. Exemplarily, the SLRB identifier may be used to identify the SLRB, which may be the index number of the SLRB. The configurations of the SLRBs included in the same SLRBs may be the same or different. For example, an SLRB group includes 8 SLRBs, and the IDs of the LCHs corresponding to these 8 SLRBs may be different.

[0058] PDCP entity configuration: Regarding the configuration of the PDCP layer entity, the PDCP entity configuration may include but is not limited to any one or more of the following configuration parameters: the timing duration (discardTimer) of the timer used to control the storage time of a PDCP SDU in the PDCP cache, the sequence number (SN) length used by the PDCP layer PDU, the security configuration used by the PDCP layer entity (including whether encryption and / or integrity protection is used), the security algorithm (integrity protection algorithm and encryption algorithm) and / or key used by the PDCP layer entity, whether the PDCP layer entity uses a duplication mechanism, and related configurations of the PDCP layer entity header compression algorithm.

[0059] RLC entity configuration: For the configuration of the RLC layer entity, the RLC entity configuration may include but is not limited to any one or more of the following configuration parameters: the mode adopted by the RLC layer entity: transparent mode (TM) / 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: the SN length of the RLC layer PDU, the timing duration of the timer for controlling the initiation of poll retransmission (t-PollRetransmit), the parameter controlling the number of RLC PDUs to be sent before poll is initiated (poll PDU), the parameter controlling the number of bytes of RLC PDUs to be sent before poll is initiated (pollByte), and the maximum number of RLC layer retransmissions (maxRetxThreshold). For example, poll may refer to the RLC layer entity in the sending device instructing the RLC layer entity adopting the AM mode in the receiving device 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 further includes at least one of the following items: the SN length of the RLC layer PDU.

[0060] LCH configuration: The configuration of the LCH may include, but is not limited to, any one or more of the following configuration parameters: LCH identifier, identifier of the logical channel group to which the LCH belongs, parameters related to logical channel priority processing (priority, prioritized bit rate (PBR) and token bucket size duration (bucket size duration, BSD), etc.), carrier information that can be used to transmit data in the LCH, numerical information of resources that can be used to transmit data in the LCH (such as one or more of the subcarrier spacing, cyclic prefix length, resource time domain duration, whether it can be configured as a granted resource, etc.), a parameter (SR-mask) that controls whether the LCH can trigger a scheduling request (SR), a parameter (SR-DelayTimerApplied) that controls whether the LCH can delay triggering an SR, etc. For example, the LCH identifier is the index number of the LCH, which can be used to identify the LCH, and 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, which can be used to identify the logical channel group to which the LCH belongs.

[0061] Application layer entity: A protocol layer entity in a device, which can be called an application layer or application entity. It is mainly used to generate application (APP) messages or data packets corresponding to V2X services.

[0062] Non-access stratum (NAS) layer entity: a protocol layer entity in the device, which can be called NAS layer or NAS entity. It is mainly used to handle the transmission of information between the terminal and the core network equipment. The content of the transmission can be 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 users and networks), and billing, etc.

[0063] RRC layer entity: A protocol layer entity in the device, primarily responsible for generating RRC messages, measurement configuration, and reporting. It may also be responsible for other functions, such as sending dedicated NAS messages and transmitting terminal (user equipment, UE) access capability information and other parameters that reflect the quality of service of data packets / data flows.

[0064] SDAP layer entity: A protocol layer entity in a device, which can be called SDAP layer or SDAP entity, is mainly used to maintain the mapping relationship between QoS parameters and SLRB. For example, the QoS parameters can be the fifth generation (5 th generation, 5G) service quality identifier (5G QoS identifier, 5QI) or service quality flow identifier (QoS flow identifier, QFI) or short-range communication data packet priority (prose per packet priority, PPPP) or short-range communication data packet reliability (prose per packet reliability, PPPR), etc.

[0065] PDCP layer entity: A protocol layer entity in a device, also known as the PDCP layer or PDCP entity. It primarily 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, and reordering and retransmission processing. Each PDCP layer entity has one or two corresponding RLC layer entities.

[0066] RLC layer entity: A protocol layer entity in the device, which can be called the RLC layer or RLC entity. It is mainly responsible for segmenting / concatenating and reassembling RLC service data units (SDUs), performing error correction through automatic repeat request (ARQ), reordering RLC protocol data units (PDUs), duplicate packet detection, and resegmenting RLC PDUs.

[0067] MAC layer entity: A protocol layer entity in the device, which can be called the MAC layer or MAC entity. It is mainly responsible for matching logical channels and transport channels, multiplexing multiple MAC SDUs belonging to one or different logical channels into the same MAC PDU, and submitting it to the PHY (physical) layer entity, performing error correction, scheduling processing, logical channel priority processing, scheduling information reporting, random access process processing, etc. through hybrid automatic repeat request (HARQ).

[0068] A PHY layer entity is a protocol layer entity within a device. It provides the mechanical, electrical, functional, and regulatory characteristics for creating, maintaining, and dismantling the physical links required for data transmission. Simply put, the PHY layer entity ensures that raw data can be transmitted across various physical media.

[0069] The technical solutions in the embodiments of the present application are described below in conjunction with the drawings in the embodiments of the present application.

[0070] The communication method provided in the embodiments of the present application can be used in any communication system that directly communicates between devices, such as a device-to-device (D2D) communication system, a machine-to-machine (M2M) communication system, or a V2X communication system. The communication method provided in the embodiments of the present application is described below using a V2X communication system as an example. The implementation of this communication method in other communication systems can refer to the description of the embodiments of the present application.

[0071] Figure 2 A V2X communication system is provided in an embodiment of the present application, such as Figure 2 As shown, the V2X communication system may include: multiple vehicles (such as Figure 2Vehicle 1, vehicle 2, vehicle 3, ... are shown. A vehicle can establish direct communication links with surrounding vehicles to achieve direct communication, such as vehicle 1 and vehicle 2. For example, the direct communication link established between vehicles can be defined as a sidelink or sidelink (SL), and the interface for direct communication between a vehicle and surrounding vehicles can be called a PC5 port. Figure 2 The V2X communication system shown may also include a wireless access network device. A vehicle may use the wireless access network device to transmit a V2X message to the other vehicle or access the network through the wireless access network device. For example, vehicle 1 may send a V2X message to the wireless access network device, and the wireless access network device may send the V2X message to vehicle 2. For example, the interface between the vehicle and the wireless access network device may be called a Uu interface. Optionally, Figure 2 The network architecture shown is only an exemplary architecture diagram, and the embodiments of this application are not limited to Figure 2 The number of network elements included in the V2X communication system shown. Figure 2 In addition to the network functional entities shown, Figure 2 The network shown may also include other functional entities, such as application servers, core network equipment, etc., without limitation.

[0072] For example, Figure 2 The vehicle in the V2X communication system is not limited to any type of vehicle such as a car, bicycle, electric vehicle, airplane, ship, train, or high-speed rail. The vehicle may include an onboard device that can directly communicate with other devices. The onboard device may be called a user equipment (UE) or a terminal. The vehicle may have a one-to-one connection with other vehicles in the V2X communication system, i.e., unicast communication, or may perform multicast communication with multiple other vehicles in the V2X communication system. For example, Figure 3a A schematic diagram of unicast communication provided in an embodiment of the present application is shown in FIG. Figure 3a As shown, vehicle 1 can connect one-to-one with vehicle 2 for unicast communication. Figure 3b A schematic diagram of multicast communication provided in an embodiment of the present application is shown in FIG. Figure 3b As shown, vehicle 1 can form a communication group with three other vehicles (vehicle 2, vehicle 3, and vehicle 4), and the vehicles in the communication group can perform multicast communication. In the embodiment of the present application, the vehicle is used as an example for description. The device for realizing the function of the terminal device can be the terminal device itself, or it can be a device that can support the terminal device to realize the function, such as a chip system. In the embodiment of the present application, the chip system can be composed of chips, or it can include chips and other discrete devices.

[0073] Figure 2The wireless access network equipment is mainly used to implement wireless physical control functions, resource scheduling and wireless resource management, wireless access control and mobility management functions. The wireless access network equipment can be an access network (AN) / radio access network (RAN) equipment, or it can be a device composed of multiple 5G-AN / 5G-RAN nodes, or it can be any one of a base station (nodeB, NB), an evolved base station (evolution nodeB, eNB), a next generation base station (gNB), a transmission receive point (TRP), a transmission point (TP) and some other access nodes. In the embodiment of the present application, the device for implementing the function of the wireless access network device can be a wireless access network device, or it can be a device that can support the wireless access network device to implement the function, such as a chip system. In the technical solution provided in the embodiment of the present application, the technical solution provided in the embodiment of the present application is described by taking the device for implementing the function of the wireless access network device as an example of a wireless access network device.

[0074] For example, Figure 2 Each vehicle shown may include Figure 4 The protocol layer entities shown include: application layer entity, NAS layer entity, RRC layer entity, PDCP layer entity, RLC layer entity, MAC layer entity, PHY layer entity, and may also include SDAP layer entity, V2X layer entity or other newly added protocol layer entities ( Figure 4 The relevant functions and configurations of each protocol layer entity are as described above and will not be repeated here. Among them, the MAC layer entity, RLC layer entity and PDCP layer entity can form a data link entity, called layer 2 (layer 2, L2). The vehicle can Figure 4 The protocol layer entities shown process the transmitted signaling messages or data packets. Figure 4Taking the transmission of data packets between vehicle 1 and vehicle 2 as an example, the RRC layer entities of vehicle 1 and vehicle 2 can establish corresponding SLRBs for multicast communication and unicast communication respectively, and maintain the corresponding relationship between unicast communication / multicast communication and SLRBs. When vehicle 1 sends a data packet corresponding to multicast communication to vehicle 2, vehicle 1 can submit the data packet to the SLRBs corresponding to multicast communication for processing based on the corresponding relationship, and send the processed data packet to vehicle 2 through the PC5 port. After receiving the data packet, the MAC layer entity of vehicle 2 submits it to the SLRBs corresponding to multicast communication in vehicle 2 for processing. The process of vehicle 1 sending a data packet corresponding to unicast communication to vehicle 2 is similar and will not be repeated here. Correspondingly, as the reverse process of vehicle 1 sending a data packet to vehicle 2, when vehicle 2 sends a data packet to vehicle 1, vehicle 2 can submit the data packet to the SLRBs corresponding to unicast communication / multicast communication for processing according to the correspondence between unicast communication / multicast communication and SLRBs, and send the processed data packet to vehicle 1 through PC5 port. After the MAC layer entity of vehicle 1 receives the data packet, it submits it to the SLRBs corresponding to unicast communication / multicast communication in vehicle 1 for processing. Specifically, this method can refer to Figure 6 shown.

[0075] Optional, above Figure 2 The naming of the network elements in the architecture, the interface names between the network elements, and the protocol layer entities is only an example. In the specific implementation, the network elements, the interface names between the network elements, and the protocol layer entities can also be other names, and the embodiments of the present application do not specifically limit this.

[0076] For example, Figure 2 The vehicles in Figure 5 The communication device shown may include Figure 5 The communication device shown. Figure 5 Schematic diagram of the composition of a communication device 500 provided in an embodiment of the present application, which can be used to implement the communication method provided in an embodiment of the present application. Figure 5 As shown, the communication device 500 includes at least one processor 501, a communication circuit 502, and at least one communication interface 503; further, it may also include a memory 504. For example, the processor 501, the memory 504, and the communication interface 503 may be connected via the communication circuit 502. In the embodiment of the present application, the at least one may be one, two, three, or more, and the embodiment of the present application is not limited thereto.

[0077] In the embodiment of the present application, the processor 501 may be a central processing unit (CPU), a general-purpose processor, a network processor (NP), a digital signal processor (DSP), a microprocessor, a microcontroller, a programmable logic device (PLD), or any combination thereof. The processor may also be any other device having processing functionality, such as a circuit, a device, or a software module.

[0078] In the embodiment of the present application, the communication line 502 may include a path for transmitting information between components included in the communication device.

[0079] In the embodiment of the present application, the communication interface 503 is used to communicate with other vehicles or communication networks (such as Ethernet, radio access network (RAN), wireless local area network (WLAN), etc.). The communication interface 503 can be a module, circuit, transceiver, or any device capable of achieving communication.

[0080] In the embodiment of the present application, the memory 504 can be a read-only memory (ROM) or other types of static storage devices that can store static information and / or instructions, or a random access memory (RAM) or other types of dynamic storage devices that can store information and / or instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited to these.

[0081] In one possible design, the memory 504 can exist independently of the processor 501, that is, the memory 504 can be a memory external to the processor 501. In this case, the memory 504 can be connected to the processor 501 via the communication line 502 for storing instructions or program codes. When the processor 501 calls and executes the instructions or program codes stored in the memory 504, the communication method provided in the following embodiments of the present application can be implemented. In another possible design, 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. For example, the memory 504 is a cache that can be used to temporarily store some data and / or instruction information.

[0082] As an implementation method, the processor 501 may include one or more CPUs, such as Figure 5 As another implementation, the communication device 500 may include multiple processors, such as Figure 5 As another implementation, the communication device 500 may further include an output device 505 and an input device 506. For example, the input device 506 may be a microphone or a joystick, and the output device 505 may be a display screen, a speaker, or the like.

[0083] The following combination Figures 2 to 4 , the communication method provided in the embodiment of the present application is specifically described. Optionally, the message names between the network elements or the names of the parameters in the message in the following embodiment of the present application are only examples, and other names may also be used in the specific implementation, and the embodiment of the present application does not specifically limit this.

[0084] Figure 6 A flow chart of a communication method provided in an embodiment of the present application is shown in FIG. Figure 6 As shown, the method may include:

[0085] Step 601: The application layer entity of the first terminal device submits communication type information and a target side identifier to the control layer entity of the first terminal device.

[0086] For example, the first terminal device may be Figure 2 Any vehicle in the V2X system can establish a Figure 3a Unicast communication as shown or Figure 3b The first terminal device may include Figure 4The control layer entity of the first terminal device may be an RRC layer entity of the first terminal device, or a functional module in the RRC layer entity of the first terminal device specifically used to control SL interface communication, or a control layer entity newly added to implement SL interface communication (such as a PC5-C entity). Optionally, step 601 may also be performed by other protocol layer entities of the first terminal device, such as the process described in step 601 may be performed by a NAS layer entity of the first terminal device.

[0087] Exemplarily, the communication type message may include or be used to indicate the type of communication to be performed by the first terminal device. In various embodiments of the present application, the communication type may be Figure 3a Unicast communication as shown or Figure 3b In the embodiment of the present application, the communication type message may be a binary bit number "0" or "1" to indicate the type of communication to be performed by the first terminal device, such as "1" to indicate unicast communication and "0" to indicate multicast communication.

[0088] The target side identifier may be target_id, which may be used to identify the unicast communication or multicast communication to be performed by the first terminal device. The target side identifier may be allocated by the application layer entity of the lead vehicle that initiates the unicast communication or multicast communication or by other protocol layer entities (such as NAS layer entities) of the lead vehicle that initiates the unicast communication or multicast communication. The target side identifiers allocated for different communication types are different. In an embodiment of the present application, the lead vehicle that initiates the unicast communication or multicast communication may be the first terminal device. Optionally, if the communication type is unicast communication, the target side identifier may not be limited to the identifier allocated by the application layer entity or other protocol layer entity of the lead vehicle that initiates the unicast communication or multicast communication, but may also be the identifier of the opposite device that unicasts with the first terminal device, such as the source layer 2 identifier (source layer-2id) of the opposite device that unicasts with the first terminal device. For example, assuming that vehicle 1 is the lead vehicle that initiates the unicast communication, and vehicle 1 and vehicle 2 form a unicast communication, then for vehicle 1, the target side identifier corresponding to the unicast communication may be target_id1 allocated by the application layer entity of vehicle 1, or may be the identifier of vehicle 2.

[0089] Optionally, the application layer entity of the first terminal device submits the communication type information and the target side identifier to the control layer entity of the first terminal device, including: after the application layer entity of the first terminal device determines that the first terminal device is in unicast communication or multicast communication with other vehicles, the application layer entity of the first terminal device assigns a target side identifier to the unicast communication or multicast communication, and directly submits the communication type information and the target side identifier to the control layer entity of the first terminal device; or, the application layer entity of the first terminal device submits the communication type information and the target side identifier to the NAS layer entity of the first terminal device, and the NAS layer entity of the first terminal device submits the communication type information and the target side identifier to the control layer entity of the first terminal device, that is, the application layer entity of the first terminal device can submit the communication type information and the target side identifier to the control layer entity of the first terminal device through the NAS layer entity of the first terminal device.

[0090] Another optional method is that the application layer entity of the first terminal device submits the communication type information to the NAS layer entity of the first terminal device. After receiving the communication type information, the NAS layer entity of the first terminal device determines the target side identifier corresponding to the unicast communication or multicast communication indicated by the communication type information, and the NAS layer entity of the first terminal device submits the communication type information and the target side identifier to the control layer entity of the first terminal device. Alternatively, the NAS layer entity of the first terminal device can also be a newly added V2X layer entity in the first terminal device, and the V2X layer entity is mainly responsible for transmitting messages or data packets between the application layer entity of the first terminal device and the control layer entity of the first terminal device. Optionally, the process by which the application layer entity of the first terminal device determines whether the first terminal device performs unicast communication or multicast communication with other vehicles can be referred to. Figures 7 to 9 As shown in . Optionally, after the application layer entity or NAS layer entity of the first terminal device determines the target side identifier corresponding to the unicast communication or multicast communication, it can maintain the correspondence between the unicast communication or multicast communication and the target side identifier, and send the correspondence between the unicast communication or multicast communication and the target side identifier to other member vehicles in the unicast communication or multicast communication, so that other member vehicles can synchronously know the target side identifier corresponding to the unicast communication or multicast communication, and maintain the correspondence between the target side identifier and the SLRBs.

[0091] In addition to the communication type information and the target side identifier, the application layer entity (or NAS layer entity) of the first terminal device may also deliver service information and / or lead vehicle information to the control layer entity of the first terminal device. The service information may be a destination layer-2 ID, which is used to identify the V2X service type. The lead vehicle information may be used to indicate whether the first terminal device is the lead vehicle initiating unicast or multicast communication (unicast / multicast communication). Exemplarily, the lead vehicle information can be a 1-bit lead vehicle indication (header_indicator), header_indicator = 1 indicates that the first terminal device is the lead vehicle, and header_indicator = 0 indicates that the first terminal device belongs to a member vehicle (i.e., other vehicles other than the lead vehicle in unicast communication or multicast communication); or, the lead vehicle information can be the identifier of the lead vehicle, such as: the source layer-2id of the lead vehicle. If the identifier of the lead vehicle is the same as the identifier of the first terminal device (such as the source layer 2 identifier of the first terminal device), the control layer entity of the first terminal device determines that the first terminal device is the lead vehicle for establishing unicast communication / multicast communication, otherwise, it is determined that the first terminal device belongs to a member vehicle.

[0092] Optionally, the application layer entity of the first terminal device may submit the communication type information and the target side identifier to the control layer entity of the first terminal device while submitting the data packet to be sent to the opposite device downward. In this case, the communication type information and the target side identifier may be carried downward together with the data packet; alternatively, the application layer entity of the first terminal device may also submit the communication type information and the target side identifier to the control layer entity of the first terminal device before sending the data packet.

[0093] Step 602: The control layer entity of the first terminal device establishes an SLRB group corresponding to the communication type according to the communication type information.

[0094] Exemplarily, the SLRB group corresponds to the target side identifier, and the control layer entity of the first terminal device can save and maintain the correspondence between the SLRB group and the target side identifier, or save the correspondence between the SLRB group and the target side identifier in other protocol layer entities of the first terminal device (such as: the SDAP layer entity of the first terminal device).

[0095] The control layer entity of the first terminal device establishes an SLRB group corresponding to the communication type according to the communication type information, which may include: the control layer entity of the first terminal device identifies the communication type to be performed by the first terminal device according to the communication type information, and for different communication types, establishes multiple SLRBs that meet the service quality requirements for data packet transmission under the communication type, and determines the configuration of the PDCP layer entity, RLC layer entity and LCH included in each SLRB, such as: for unicast communication, the RLC entity configuration may be AM mode, and for multicast communication, the RLC entity configuration may be UM mode. For unicast communication, the PDCP SN length may be 5 bits, and for multicast communication, the PDCP SN length may be 12 bits, or both unicast communication and multicast communication may be configured as 12 bits. Optionally, the configuration of each SLRB in the SLRB group corresponding to unicast communication is made different from the configuration of each SLRB in the SLRB group corresponding to multicast communication as much as possible to ensure the service quality requirements for data packet transmission under different communication types.

[0096] Exemplarily, the PDCP entity configuration, RLC entity configuration and LCH configuration corresponding to unicast communication or multicast communication can be pre-saved on the first terminal device, or obtained by the first terminal device from the wireless access network device, such as: the first terminal device can receive the configuration information of the SLRR group sent by the wireless access network device, or obtained by the first terminal device from other member vehicles in the unicast communication or multicast communication, without restriction.

[0097] Optionally, after the control layer entity of the first terminal device establishes the SLRB group, it can also send the configuration information of each SLRB in the SLRB group to the control layer entities of other devices in unicast communication or multicast communication, that is, to inform other member vehicles of the configuration of the SLRB group corresponding to unicast communication or multicast communication. Figure 8 As shown in .

[0098] Subsequently, when the application layer entity of the first terminal device sends a data packet, the data packet can be delivered to the corresponding SLRB group for processing according to the SLRB group corresponding to the communication type established in step 602. For example, Figure 6 As shown, the process may include steps 603 to 605:

[0099] Step 603: The application layer entity of the first terminal device delivers the data packet and the first target side identifier to the SDAP layer entity of the first terminal device.

[0100] Exemplarily, the application layer entity of the first terminal device can directly submit a data packet and a first target side identifier to the SDAP layer entity of the first terminal device. The data packet can be a data packet for unicast communication or a data packet for multicast communication, and the first target side identifier can be used to identify the communication type corresponding to the data packet. For example, if the application layer entity of the first terminal device determines to conduct unicast communication with other terminal devices, the first target side identifier is used to identify the unicast communication; if the application layer entity of the first terminal device determines to conduct multicast-unicast communication with other terminal devices, the first target side identifier is used to identify the multicast communication.

[0101] In addition to the data packet and the first target side identifier, the application layer entity of the first terminal device can also submit service information (destination layer-2id), QoS parameters, communication type information and other information of the service type to which the data packet belongs to to the SDAP layer entity of the first terminal device without restriction.

[0102] Step 604: The SDAP layer entity of the first terminal device determines the first SLRB group corresponding to the first target side identifier based on the correspondence between the SLRB group and the target side identifier, and delivers the data packet to the media access control MAC layer entity of the first terminal device after processing by the first SLRB group.

[0103] Exemplarily, the correspondence between the SLRB group and the target side identifier can be sent by the control layer entity of the first terminal device to the SDAP layer entity of the first terminal device, and the SDAP layer entity of the first terminal device receives and saves the correspondence. Optionally, the correspondence between the SLRB group and the target side identifier is saved in the SDAP layer entity of the first terminal device in the form of a list.

[0104] For example, Table 1 is a list of correspondences between SLRB groups and target side identifiers. As shown in Table 1, targetd_id1 corresponds to SLRBs1, and targetd_id2 corresponds to SLRBs2. Assuming that the first target side identifier is targetd_id1, the SDAP layer entity of the first terminal device can determine that the SLRB group corresponding to targetd_id1 is SLRBs1 by looking up Table 1.

[0105] Table 1

[0106] Target side identification SLRB group targetd_id1 SLRBs1 targetd_id2 SLRBs2

[0107] Exemplarily, delivering a data packet to a media access control MAC layer entity of a first terminal device after being processed by a first SLRB group may include: an SDAP layer entity of the first terminal device delivering an SDAP PDU including the data packet to a PDCP layer entity corresponding to a certain SLRB included in the first SLRB group; the PDCP layer entity receives the SDAP PDU, processes the SDAP SDU included in the SDAP PDU to generate a PDCP PDU, and delivers the PDCP PDU to an RLC layer entity in the SLRB; the RLC layer entity receives the PDCP PDU, processes the PDCP SDU included in the PDCP PDU to generate an RLC PDU, and delivers the RLC PDU to the MAC layer entity of the first terminal device through an LCH corresponding to the SLRB. Optionally, if the first SLRB includes multiple SLRBs, the SDAP layer entity of the first terminal device may randomly select an SLRB from the first SLRB group and deliver the SDAP PDU to the SLRB; or, the SDAP layer entity of the first terminal device delivers the SDAP PDU to the SLRB corresponding to the QoS parameters of the data packet based on the correspondence between the QoS parameters and the SLRB. Exemplarily, the process may include:

[0108] The application layer entity of the first terminal device submits a first QoS parameter to the SDAP layer entity of the first terminal device. The SDAP layer entity of the first terminal device determines the first SLRB corresponding to the first QoS parameter in the first SLRB group based on the correspondence between the QoS parameter and the SLRB, and submits the data packet to the MAC layer entity of the first terminal device after processing by the first SLRB. The first QoS parameter is used to indicate the QoS of the data packet.

[0109] Exemplarily, the way in which the first terminal device determines the correspondence between QoS parameters and SLRB can be the same as the method in which the first terminal device obtains the SLRB configuration in step 602. It can be pre-stored on the first terminal device, or obtained by the first terminal device from a wireless access network device, or obtained by the first terminal device from other member vehicles in unicast communication or multicast communication, without restriction. Furthermore, the correspondence between QoS parameters and SLRB can be part of the SDAP configuration. In this case, the SDAP configuration can be pre-stored on the first terminal device, or obtained by the first terminal device from the wireless access network device, or obtained by the first terminal device from other member vehicles in unicast communication or multicast communication, without restriction; or, there is no SDAP layer entity in the first terminal device, and the correspondence between QoS parameters and SLRB can be part of the NAS configuration, pre-defined by the protocol, or pre-stored on the first terminal device. The application layer entity of the first terminal device can send a data packet, a first target side identifier and a first QoS parameter to the NAS layer entity of the first terminal device. After receiving the data packet, the NAS layer entity of the first terminal device submits the data packet to the PDCP layer entity in the corresponding SLRB for processing according to the correspondence between the target side identifier and SLRBs, and the correspondence between the QoS parameters and the SLRB in the SLRBs.

[0110] In addition, the SDAP layer entity of the first terminal device may also receive communication type information sent by the application layer entity of the first terminal device.

[0111] Step 605: The MAC layer entity of the first terminal device processes the RLC SDU included in the RLC PDU to obtain a MAC PDU, and delivers the MAC PDU to the physical PHY layer entity of the first terminal device.

[0112] Exemplarily, the process of the MAC layer entity of the first terminal device processing the RLC SDU included in the RLC PDU to obtain the MAC PDU can refer to the existing technology and will not be repeated here.

[0113] Optionally, while the MAC layer entity of the first terminal device delivers the MAC PDU to the PHY layer entity of the first terminal device, it can also deliver any one or more of the first target side identifier, first QoS parameter and communication type information to the PHY layer entity of the first terminal device.

[0114] based on Figure 6The method shown can establish corresponding wireless bearer groups for different communication types. Subsequently, when data of a certain communication type is sent downward, the data can be processed by the wireless bearer group corresponding to the communication type, thereby realizing the processing of data of different communication types through different wireless bearer groups, controlling and ensuring the service quality requirements of data of different communication types.

[0115] In the following example, the first terminal device is vehicle 1, the second terminal device is vehicle 2, and vehicle 1 and vehicle 2 establish unicast communication / multicast communication. Figure 6 The process is described as follows. A wireless communication link is established between vehicle 1 and vehicle 2.

[0116] Figure 7 A flow chart of another communication method provided in an embodiment of the present application is shown in FIG. Figure 7 As shown, the method may include:

[0117] S701 : The application layer entity of vehicle 1 wishes to perform unicast communication / multicast communication with vehicle 2 .

[0118] For example, when executing a platooning service, an application layer entity in vehicle 1 may wish to perform unicast or multicast communication with vehicle 2, which is traveling in the same direction and at a relatively close distance. Optionally, unicast or multicast communication corresponds to a specific communication service (e.g., V2X service). For example, unicast communication requires lower latency and higher reliability for V2X services, while multicast communication allows for relatively longer latency and lower reliability requirements for V2X services.

[0119] S702: The application layer entity of vehicle 1 broadcasts a set-up request.

[0120] Exemplarily, the assembly request can be used to request the establishment of unicast communication / multicast communication. The assembly request can be an APP message. The assembly request can include a V2X service identifier (destination layer-2id) and can also include other auxiliary information, such as: the driving direction, destination, driving speed, etc. of vehicle 1. Optionally, if the assembly request is used to request the establishment of unicast communication, the V2X service identifier included in the assembly request can be the identifier of the vehicle that has one-to-one unicast communication with vehicle 1, such as: the source layer-2id of the vehicle. Taking the establishment of unicast communication between vehicle 1 and vehicle 2 as an example, at this time, the application layer entity broadcasting the assembly request of vehicle 1 can also be described as the application layer entity of vehicle 1 sending a assembly request to the application layer entity of vehicle 2.

[0121] Optionally, the application layer entity of vehicle 1 broadcasts a build request, including: the application layer entity of vehicle 1 generates a build request, submits the build request downward to the PDCP layer entity, RLC layer entity, MAC layer entity, and PHY layer entity for processing, and then broadcasts it.

[0122] S703: The application layer entity of vehicle 2 receives the establishment request and determines whether to establish unicast communication / multicast communication with vehicle 1. If it is determined to establish unicast communication / multicast communication with vehicle 1, S704 is executed.

[0123] Exemplarily, the PHY layer entity of vehicle 2 receives a setup request from the wireless communication link (e.g., PC5 port) established between vehicle 1 and vehicle 2, and determines whether it is interested in the service of this type based on the destination layer-2 ID of the service type carried in the setup request. If interested, the setup request is received and submitted to the application layer of the vehicle; otherwise, the setup request is not received. The application layer entity of vehicle 2 determines whether to establish unicast communication / multicast communication with vehicle 1, which may include: the application layer entity of vehicle 2 determines whether to join the unicast communication or multicast communication of vehicle 1 based on the auxiliary information included in the setup request, such as: if the driving direction, destination, and driving speed are consistent with those of vehicle 1, and the distance from vehicle 1 is relatively close, then it is determined to establish unicast communication / multicast communication with vehicle 1; otherwise, it is determined not to establish unicast communication / multicast communication with vehicle 1.

[0124] Optionally, if the establishment request is used to request the establishment of unicast communication, the application layer entity of vehicle 2 can also determine whether to establish unicast communication with vehicle 1 based on whether the vehicle identifier carried in the establishment request is its own identifier. For example: if the vehicle identifier carried in the establishment request is its own identifier, it is determined to establish unicast communication with vehicle 1; otherwise, it is determined not to establish unicast communication with vehicle 1.

[0125] S704: The application layer entity of vehicle 2 sends a build response to the application layer entity of vehicle 1.

[0126] Exemplarily, the assembly response is used to indicate the establishment of unicast communication / multicast communication with vehicle 1. The assembly response may include the identification of vehicle 2 itself, such as: source layer-2id, and may also include communication type information so that vehicle 1 knows which type of communication (unicast communication or multicast communication) the assembly response is for.

[0127] For example, the application layer entity of vehicle 2 can send a setup response to vehicle 1 through its own PDCP layer entity, RLC layer entity, MAC layer entity, and PHY layer entity. After the PHY layer entity of vehicle 1 receives the setup response, it can upload the setup response to the application layer entity of vehicle 1 through the MAC layer entity, RLC layer entity, and PDCP layer entity of vehicle 1.

[0128] S705: The application layer entity of vehicle 1 receives the establishment response, determines to establish unicast communication / multicast communication with vehicle 2, and submits the communication type information and the target side identifier to the control layer entity of vehicle 1.

[0129] For example, the description of the communication type information and the target side identifier and the specific implementation of S705 can be referred to that in step 601 and will not be repeated here.

[0130] S706: The control layer entity of vehicle 1 establishes an SLRB group corresponding to the communication type according to the communication type information.

[0131] Specifically, S706 may refer to step 602 and will not be described in detail.

[0132] S707: The application layer entity of vehicle 1 sends communication type information and target side identifier to the application layer entity of vehicle 2.

[0133] The application layer entity of vehicle 1 sends the communication type information and the target side identifier to the application layer entity of vehicle 2, which may include: the application layer entity of vehicle 1 processes the communication type information and the target side identifier through the PDCP layer entity, RLC layer entity, MAC layer entity, and PHY layer entity of vehicle 1, and then sends them to vehicle 2 through the PC5 port interface; the PHY layer entity of vehicle 2 receives the communication type information and the target side identifier, and sends the communication type information and the target side identifier to the application layer entity of vehicle 2 through the MAC layer entity, RLC entity, and PDCP layer entity of vehicle 2.

[0134] Optionally, if vehicle 1 and vehicle 2 form a multicast communication, the application layer entity of vehicle 1 also needs to send the identifiers (source layer-2id) of all member vehicles in the multicast communication except vehicle 2 to the application layer entity of vehicle 2, so that the control function entity of vehicle 2 can establish corresponding SLRBs for each member vehicle.

[0135] S708: The application layer entity of vehicle 2 delivers the communication type information and the target side identifier to the control layer entity of vehicle 2.

[0136] For example, the process of the application layer entity of vehicle 2 submitting communication type information and target side identification to the control layer entity of vehicle 2 can refer to the process of the application layer entity of vehicle 1 submitting communication type information and target side identification to the control layer entity of vehicle 2, and will not be repeated.

[0137] If the application layer entity of vehicle 1 sends the identifiers (source layer-2id) of all member vehicles in the multicast communication except vehicle 2 to the application layer entity of vehicle 2, then the application layer entity of vehicle 2 submits the communication type information and the target side identifier to the control layer entity of vehicle 2, and can also send the identifiers (source layer-2id) of all other member vehicles in the multicast communication to the control layer entity of vehicle 2, so that the control function entity of vehicle 2 can establish corresponding SLRBs for each member vehicle.

[0138] S709: The control layer entity of vehicle 2 establishes an SLRB group corresponding to the communication type according to the communication type information.

[0139] For example, the process in which the control layer entity of vehicle 2 establishes the SLRB group corresponding to the communication type according to the communication type information can refer to the process in which the control layer entity of vehicle 1 establishes the SLRB group corresponding to the communication type according to the communication type information, and no further details are given.

[0140] In the embodiment of the present application, the configuration of the SLRB established by the receiving device may be different from the configuration of the SLRB established by the sending device, for example: Figure 7 In the illustrated embodiment, vehicle 1 may be a transmitting device, and vehicle 2 may be a receiving device. The configuration of the SLRB established by vehicle 2 is slightly different from the configuration of the SLRB established by vehicle 1. For example, in the configuration of the SLRB established by vehicle 2, in addition to some configuration parameters included in the PDCP entity configuration described above, it may also include a parameter indicating whether delivery is in order (outOfOrderDelivery) and a PDCP layer reordering timer duration (t-Reordering); for the RLC entity configuration, it only includes any one or more of the following configuration parameters: RLC mode, the SN length used by the RLC PDU, the timer duration for controlling the RLC layer to perform RLC SDU reassembly (t-Reassembly), the timer duration for controlling the RLC layer to perform status report feedback (t-StatusProhibit), etc.; for the LCH configuration, it only includes the LCH identifier.

[0141] S710: The application layer entity of vehicle 1 delivers a data packet and a first target side identifier to the SDAP layer entity of vehicle 1.

[0142] Specifically, S710 may refer to S603 and will not be described in detail. In addition, the application layer entity of vehicle 1 may also send other information such as QoS parameters and communication type information corresponding to the data packet to the SDAP layer entity of vehicle 1.

[0143] Optionally, in an embodiment of the present application, S710 can be combined with S705 and S706 for execution, such as: the application layer entity of vehicle 1 receives the establishment response, determines to establish unicast communication / multicast communication with vehicle 2, and submits the data packet, the first target side identifier, the communication type information and the target side identifier downward. Vehicle 1 establishes a corresponding SLRB group based on the communication type information and the target side identifier. The SDAP layer entity of vehicle 1 receives the data packet and the first target side identifier and executes S711, that is, when vehicle 1 submits the data packet downward, it establishes the SLRB group corresponding to the unicast communication or multicast communication corresponding to the data packet. It is not necessary to establish the SLRB group before sending the data packet. Subsequently, when another data packet arrives, the data packet is submitted to the SLRB group corresponding to the unicast communication or multicast communication for processing.

[0144] S711: The SDAP layer entity of vehicle 1 determines the first SLRB group corresponding to the first target side identifier in vehicle 1 based on the correspondence between the SLRB group and the target side identifier, and delivers the data packet to the media access control MAC layer entity of vehicle 1 after processing by the first SLRB group in vehicle 1.

[0145] For example, S711 can refer to step 604 and will not be described in detail.

[0146] S712: The MAC layer entity of vehicle 1 processes the received data packet to obtain a MAC PDU, and delivers the MAC PDU to the physical PHY layer entity of vehicle 1.

[0147] For example, S712 can refer to step 605 and will not be described in detail. In addition, the MAC layer entity of vehicle 1 can also submit other information such as the first target side identifier, QoS parameters corresponding to the data packet, and communication type information to the physical PHY layer entity of vehicle 1.

[0148] S713: The PHY layer entity of vehicle 1 delivers the MAC PDU to the PHY layer entity of vehicle 2.

[0149] For example, the PHY layer entity of vehicle 1 may deliver the MAC PDU to the PHY layer entity of vehicle 2 via the PC5 port between vehicle 1 and vehicle 2. Simultaneously, the PHY layer entity of vehicle 1 also sends the first target side identifier, QoS parameters, and communication type information to the PHY layer entity of vehicle 2.

[0150] S714: The PHY layer entity of vehicle 2 delivers the MAC PDU to the MAC layer entity of vehicle 2.

[0151] Exemplarily, while the PHY layer entity of vehicle 2 receives the MAC PDU, it can also receive any one or more of the information such as the first target side identifier, QoS parameters, and communication type information, and filter the received MAC PDU according to the first target side identifier. For example: if the first target side identifier corresponds to the unicast communication or multicast communication to which it has joined, it determines that the MAC PDU is sent to itself, receives the MAC PDU and delivers it to the MAC layer entity of vehicle 2. Otherwise, it determines that the MAC PDU is not sent to itself and discards it.

[0152] In addition, the PHY layer entity of vehicle 2 can also determine the communication type based on the communication type information and adopt an appropriate transmission mechanism according to the communication type. For example, if the communication type is unicast communication, the HARQ feedback mechanism is adopted; otherwise, the HARQ feedback mechanism is not required for transmission.

[0153] S715: The MAC layer entity of vehicle 2 receives the MAC SDU and the first target side identifier, determines the first SLRB group corresponding to the first target side identifier in vehicle 2 according to the correspondence between the SLRB group and the target side identifier, and delivers the data packet to the application layer entity of vehicle 2 after processing by the first SLRB group in vehicle 2.

[0154] Optionally, the above S707 to S709 may not be executed. In this case, when vehicle 1 submits the MAC PDU to the PHY layer entity of vehicle 2, it may also submit the communication type information and the target side identifier to the PHY layer entity of vehicle 2. Optionally, the communication type information and / or the target side identifier may be carried in the MAC PDU. Vehicle 2 establishes an SLRB group corresponding to the communication type according to the communication type information, and maintains the correspondence between the SLRB group and the target side identifier. That is, when vehicle 2 receives a data packet sent by the opposite device, it establishes a corresponding SLRB group for different communication types. There is no need to establish the SLRB group in advance. Subsequently, when another data packet arrives, the data packet will be submitted to the corresponding SLRB group for processing.

[0155] based on Figure 7 The method shown can establish different SLRBs for different communication types, and use SLRBs with different configurations to process data packets transmitted in unicast or multicast communications, thereby controlling and ensuring the service quality of data transmitted in unicast or multicast communications.

[0156] Figure 8 A flow chart of another communication method provided in an embodiment of the present application is as follows: Figure 8 As shown, the method may include:

[0157] S801: The application layer entity of vehicle 1 wishes to establish unicast communication / multicast communication with vehicle 2.

[0158] For example, S801 may refer to S701 and will not be described in detail.

[0159] S802: The application layer entity of vehicle 1 broadcasts a setup request.

[0160] For example, S802 may refer to S702 and will not be described in detail.

[0161] S803: The application layer entity of vehicle 2 receives the establishment request and determines whether to establish unicast communication / multicast communication with vehicle 1. If it is determined to establish unicast communication / multicast communication with vehicle 1, S804 is executed.

[0162] For example, S803 may refer to S703 and will not be described in detail.

[0163] S804: The application layer entity of vehicle 2 sends a build response to the application layer entity of vehicle 1.

[0164] For example, S804 may refer to S704 and will not be described in detail.

[0165] S805: The application layer entity of vehicle 1 receives the establishment response, determines to establish unicast communication / multicast communication with vehicle 2, and submits the communication type information and the target side identifier to the control layer entity of vehicle 1.

[0166] For example, S805 may refer to S705 and will not be described in detail.

[0167] S806: The control layer entity of vehicle 1 receives the communication type information and the target side identifier, and establishes an SLRB group corresponding to the communication type according to the communication type information.

[0168] For example, S806 may refer to S706 and will not be described in detail.

[0169] Optionally, in S806, if the control layer entity of vehicle 1 determines that it is the lead vehicle based on the lead vehicle information sent by the application layer entity of vehicle 1, and vehicle 1 maintains connection with the wireless access network device, then when the control layer function of vehicle 1 establishes the SLRB group corresponding to the communication type, the configuration of the SLRB it adopts can be obtained from the wireless access network device through radio resource control (RRC) dedicated signaling or system message.

[0170] S807: The control layer entity of vehicle 1 sends a first message to the control layer entity of vehicle 2.

[0171] Exemplarily, the first message may be an SLRB configuration message (SLRB_Config message), and the first message includes configuration information of the SLRB group corresponding to the communication type. The control layer entity of vehicle 1 may send the first message to the control layer entity of vehicle 2 through a control plane bearer specifically used to send the first message. The control plane bearer used to send the first message is composed of a PDCP layer entity, an RLC layer entity, and an LCH, and the configuration of the control plane bearer may be predefined by the protocol or preconfigured in vehicle 1, or may be configured to vehicle 1 by a wireless access network device through a control message. For example, for unicast communication, the configuration of the control plane bearer is as follows: the RLC entity is configured to AM mode, the LCH identifier in the LCH configuration is 0, etc.; for multicast communication, the configuration of the control plane bearer is as follows: the RLC entity is configured to UM mode, etc.

[0172] For unicast communication, the first message may also include at least one of the following: SDAP configuration, target side identifier (target_id). Exemplarily, the target side identifier (target_id) may be included in the first message or obtained by the control plane entity of vehicle 2 from elsewhere. For multicast communication, the first message may also include at least one of the following: SDAP configuration, target_id, and an identifier list including the identifiers of all member vehicles receiving the SLRB_Config message. The SDAP configuration may include a mapping relationship between QoS parameters and SLRBs.

[0173] It is understandable that in an embodiment of the present application, if there is no SDAP layer entity in each vehicle, the NAS layer entity can adopt a mapping of pre-configured QoS parameters to SLRB identifiers, and the first message may not include the SDAP configuration.

[0174] S808: The control layer entity of vehicle 2 receives the first message and sends a first response to the control layer entity of vehicle 1

[0175] Exemplarily, the first response may be an SLRB configuration response.

[0176] For unicast communication, the first response may include at least one of the following: target_id, source layer-2id of the member vehicle (such as the identifier of vehicle 2), or may not include these two pieces of information.

[0177] For multicast communication, the first response may include at least one of the following: target_id, source layer-2_id of the member vehicle (such as the identifier of vehicle 2), or may not include these two pieces of information.

[0178] S809: The control layer entity of vehicle 1 receives the first response.

[0179] Optionally, if the control layer entity of vehicle 1 does not receive the first response sent by the control layer entity of vehicle 2 when the time duration is greater than or equal to the set time duration, the control layer entity of vehicle 1 resends the first message to the control layer entity of vehicle 2. For example, the preset time duration can be set as needed and is not limited.

[0180] At this time, the "identity list including the identifiers of all member vehicles that received the SLRB_Config message" in the resent first message can be replaced with "the identity list including all member vehicles that did not feedback the SLRB_Config response", and specify the member vehicles that did not feedback the SLRB_Config response. It should be noted that if the SLRB_Config message does not indicate "member vehicles that did not feedback the SLRB_Config response", it means that all member vehicles are required to receive the SLRB_Config message and feedback the SLRB_Config response.

[0181] S810: The application layer entity of vehicle 1 delivers a data packet and a first target side identifier to the SDAP layer entity of vehicle 1.

[0182] For example, S810 may refer to S710 and will not be described in detail.

[0183] S811: The SDAP layer entity of vehicle 1 receives the data packet and the first target side identifier, determines the first SLRB group corresponding to the first target side identifier based on the correspondence between the SLRB group and the target side identifier, and delivers the data packet to the media access control MAC layer entity of vehicle 1 after processing by the first SLRB group.

[0184] For example, S811 may refer to S711 and will not be described in detail.

[0185] S812: The MAC layer entity of vehicle 1 processes the received data packet to obtain a MAC PDU, and delivers the MAC PDU to the physical PHY layer entity of vehicle 1.

[0186] For example, S812 may refer to S712 and will not be described in detail.

[0187] S813: The PHY layer entity of vehicle 1 receives the MAC PDU and sends the MAC PDU to the PHY layer entity of vehicle 2 through the PHY layer entity of vehicle 1.

[0188] For example, S813 may refer to S713 and will not be described in detail.

[0189] S814: The PHY layer entity of vehicle 2 receives the MAC PDU and delivers the MAC PDU to the MAC layer entity of vehicle 2.

[0190] For example, S814 may refer to S714 and will not be described in detail.

[0191] S815: The MAC layer entity of vehicle 2 receives the MAC SDU and the first target side identifier, determines the first SLRB group corresponding to the first target side identifier based on the correspondence between the SLRB group and the target side identifier, and delivers the data packet to the application layer entity of vehicle 2 after being processed by the first SLRB group.

[0192] For example, S815 may refer to S715 and will not be described in detail.

[0193] Optional, in Figure 8 In the method shown, in order to ensure the security of SLRB configuration information transmission, the method further includes: the control layer entity of vehicle 1 and the control layer entity of vehicle 2 determine a security mode configuration, and the security mode configuration can be used to define: some rules to be followed by the PDCP layer entity corresponding to the control plane bearer in vehicle 1 and vehicle 2 when performing protection processing on the first message, the protection processing includes confidentiality protection and integrity protection, and the security mode configuration may include any one or more information of a security algorithm, a key index, and a data protection input parameter;

[0194] Exemplarily, the safety mode configuration may be pre-configured on vehicle 1, or determined by vehicle 1 based on a safety mode message (or safety mode command) sent by a wireless access network device, or determined based on a safety mode message (or safety mode command) sent by another vehicle (e.g., another vehicle engaging in unicast or multicast communication with vehicle 1). Similarly, vehicle 2 determines the safety mode configuration in the same manner as vehicle 1, and will not be further described. Optionally, the safety mode message (or safety mode command) may include the safety mode configuration.

[0195] When the control layer entity of vehicle 1 sends a first message to the control layer entity of vehicle 2, the first message is protected and processed by the PDCP layer entity of vehicle 1 according to the security mode configuration and then sent to vehicle 2; the PDCP layer entity of vehicle 2 receives the processed first message, decrypts and integrity-checks the SLRB first message according to the security mode configuration, and delivers the decrypted and integrity-checked SLRB first message to the control layer entity of vehicle 2.

[0196] based on Figure 8The method shown can be used by a vehicle to send its configured SLRB configuration to other members in a unicast or multicast communication, so that other members in the unicast or multicast communication use the received SLRB configuration to process data packets. In this way, not only can the SLRB configuration adopted by the devices in the unicast or multicast communication be guaranteed to be consistent, but also the signaling overhead caused by the configuration of SLRB by members in the unicast or multicast communication can be reduced. At the same time, different SLRBs can be established for different communication types, and SLRBs with different configurations can be used to process data packets transmitted in different unicast or multicast communications, thereby controlling and ensuring the service quality of data transmitted in different unicast or multicast communications.

[0197] Figure 7 、 Figure 8 The description above only uses the example of vehicle 1 sending a data packet to vehicle 2, i.e., vehicle 1 as the transmitter and vehicle 2 as the receiver. It is understood that vehicle 2 can also serve as the transmitter and vehicle 1 as the receiver, i.e., vehicle 2 sending a data packet to vehicle 1. When vehicle 2 sends a data packet to vehicle 1, the processing of the data packet by vehicle 2 can refer to S710-S713, and the processing of the data packet by vehicle 1 can refer to S714-S715 described above. Alternatively, the processing of the data packet by vehicle 2 can refer to S810-S813, and the processing of the data packet by vehicle 1 can refer to S814-S815 described above.

[0198] Different from the above-mentioned method of establishing unicast communication or multicast communication in S701 to S705 or S801 to S805, the embodiment of the present application also provides a method of establishing unicast communication or multicast communication. Figure 9 As shown, this may include:

[0199] S901 : The application layer entity of vehicle 1 wishes to establish unicast communication / multicast communication with vehicle 2 .

[0200] If available, S901 can refer to S701 and will not be described in detail.

[0201] S902: The control layer entity of vehicle 1 broadcasts a discovery message.

[0202] Exemplarily, the application layer entity of the vehicle 1 may instruct the control layer entity of the vehicle 1 to broadcast a discovery message (discoveryMsg).

[0203] The discovery message may be an RRC message used to discover vehicle 1. The message may include the identifier (source address) and destination address of vehicle 1, and the destination address may be the destination layer-2 ID of the service type. Depending on the communication type, the discovery message may be a unicast discovery message or a multicast discovery message. For example, a one-bit communicationType field may be included in the DiscoveryMsg, where communicationType=1 indicates a unicast discovery message, and communicationType=0 indicates a multicast discovery message.

[0204] Optionally, the control layer entity of vehicle 1 can be broadcast through a special control plane bearer, which can be composed of a PDCP layer entity, an RLC layer entity and an LCH. The control plane bearer adopts configuration parameters predefined / preconfigured by the protocol, such as: the RLC entity is configured as TM mode, the LCH is configured as LCH identifier 0, etc.

[0205] Optionally, the control layer entity broadcast discovery message of vehicle 1 may also be replaced by the application layer entity broadcast discovery message of vehicle 1 , that is, the broadcast message may be an APP message.

[0206] S903: The application layer entity of vehicle 2 receives the discovery message and determines whether to establish unicast communication / multicast communication with vehicle 1. If it is determined to establish unicast communication / multicast communication with vehicle 1, S904 is executed.

[0207] Specifically, S903 may refer to S703 and will not be described in detail.

[0208] S904: The control layer entity of vehicle 2 sends a request message to the control layer entity of vehicle 1.

[0209] The request message may be used to request the establishment of unicast or multicast communication with vehicle 1. The request message may include the identifier (source address) of vehicle 2 and the identifier (destination address) of vehicle 1. Optionally, the identifier (source address) of vehicle 2 and the identifier (destination address) of vehicle 1 may not be included in the request message, but may be included in sidelink control information (SL control information, SCI) or a MAC PDU sent to a control layer entity of vehicle 1.

[0210] For example, the application layer entity of vehicle 2 may instruct the control layer entity of vehicle 2 to send a request message. The control layer entity of vehicle 2 may send the request message through a special control plane bearer. The control plane bearer may be composed of a PDCP layer entity, an RLC layer entity, and an LCH. The control plane bearer uses configuration parameters predefined / preconfigured by the protocol, such as: the RLC entity is configured in AM mode, the LCH identifier in the LCH configuration is 1, etc.

[0211] Optionally, vehicle 2 may send the request message via unicast, multicast, or broadcast. When the request message is sent via broadcast, the destination address in the request message may be destinationlayer-2id.

[0212] S905: The control layer entity of vehicle 1 receives the request message and determines whether to establish unicast communication / multicast communication with vehicle 2. If it is determined to establish unicast communication / multicast communication with vehicle 2, S906 is executed.

[0213] For example, S905 may refer to S903 and will not be described in detail.

[0214] S906: The control layer entity of vehicle 1 sends a response message to the control layer entity of vehicle 2.

[0215] This response message can be used to instruct vehicle 1 to determine whether to establish unicast communication or multicast communication. The response message may include the identifier (source address) of vehicle 1, the destination address (identifier of vehicle 2), etc. Optionally, the identifier (source address) of vehicle 1 and the destination address (identifier of vehicle 2) may not be included in the response message, but may be included in the SCI or the MAC PDU sent to the control layer entity of vehicle 2.

[0216] For example, the control layer entity of vehicle 1 can send a response message to the control layer entity of vehicle 2 through a special control plane bearer. The control plane bearer can be composed of a PDCP layer entity, an RLC layer entity and an LCH. The control plane bearer adopts configuration parameters predefined / preconfigured by the protocol, such as: the RLC entity is configured as AM mode, the LCH identifier in the LCH configuration is 1, etc.

[0217] Optionally, the vehicle 1 may send the response message via unicast, multicast or broadcast.

[0218] S907: The control layer entity of vehicle 2 receives the response message and determines that unicast communication or multicast communication has been established with vehicle 1 according to the response message. At this time, the control layer entity of vehicle 2 can maintain the correspondence between target_id and communication type.

[0219] Optional, in Figure 9In the illustrated method, S902 may not be performed. If S902 is not performed, vehicle 2 needs to obtain information such as the identification of vehicle 1 before performing S903. For example, vehicle 2 may obtain information such as the identification of other members with which it is establishing unicast or multicast communication from a network device or through other means.

[0220] based on Figure 9 According to the method shown, unicast communication or multicast communication can be established between devices through the control layer entity.

[0221] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the interaction between various network elements. It can be understood that in order to realize the above functions, the above-mentioned first terminal device, second terminal device and wireless access network device include hardware structures and / or software modules corresponding to the execution of each function. It should be easy for those skilled in the art to realize that, in combination with the units and algorithm S of each example described in the embodiment disclosed in this document, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0222] In the embodiments of the present application, the first terminal device, the second terminal device, and the wireless access network device can be divided into functional modules according to the above-mentioned method examples. For example, each functional module can be divided according to each function, or two or more functions can be integrated into a processing module. The above-mentioned integrated modules can be implemented in the form of hardware or software functional modules. Optionally, the division of modules in the embodiments of the present application is illustrative and is only a logical functional division. In actual implementation, other division methods may be used.

[0223] Figure 10 The figure shows a schematic diagram of the composition of a communication device 100, which can be a first terminal device or a chip or system on chip in the first terminal device. The communication device 100 can be used to perform the functions of the first terminal device involved in the above embodiment. As an implementation method, Figure 10 The communication device 100 shown includes: a processing module 101, a sending module 102;

[0224] Exemplarily, the processing module 101 has the functions of the application layer entity, control layer entity, SDAP layer entity, PDCP layer entity, RLC layer entity, and MAC layer entity in the first terminal device. For example, the processing module 101 may include the application layer entity, control layer entity, SDAP layer entity, PDCP layer entity, RLC layer entity, and MAC layer entity in the communication device 100. The processing module 101 may use different configurations to process data packets of different communication types to meet the QoS requirements of data packets of different communication types. The sending module 102 has the functions of the PHY layer entity in the first terminal device and can receive data or information sent by other devices outside the communication device 100.

[0225] Processing module 101 is configured to establish a sidelink radio bearer group corresponding to the communication type based on the communication type information. Exemplarily, the sidelink radio bearer group corresponds to a target side identifier. The sidelink is a wireless communication link between communication device 100 and a second terminal device. The communication type is unicast communication or multicast communication. For example, processing module 101 has the functionality of the control layer functional entity of the first terminal device described above and can support communication device 100 in executing steps 602, S706, and S806.

[0226] In one possible design, the configuration information of the radio bearer group of the sidelink is pre-stored on the communication device 100; or Figure 10 As shown, the communication apparatus may further include: a receiving module 103, configured to receive configuration information of a radio bearer group of a sidelink sent by a radio access network device.

[0227] In one possible design, the method further includes: processing module 101 sending a first message to a control layer entity of the second terminal device via sending module 102, and receiving a first response sent by the second terminal device via receiving module 103; the communication device 100 is currently or will be conducting unicast communication or multicast communication with the second terminal device, and the first message includes configuration information of a radio bearer group of a sidelink. For example, processing module 101 may support communication device 100 in executing S807 and S808.

[0228] In one possible design, the method also includes: when the time is greater than or equal to the set time, if the processing module 101 does not receive the first response through the receiving module 103, the processing module 101 re-sends the first message to the control layer entity of the second terminal device through the sending module 102.

[0229] In one possible design, the method also includes: the processing module 101 determines the security mode configuration, performs confidentiality protection and integrity protection on the first message according to the security mode configuration, and then sends it to the control layer entity of the second terminal device through the sending module 102; wherein, the security mode configuration is used to instruct the communication device 100 to perform confidentiality protection and integrity protection on the first message.

[0230] Further optionally, the processing module 101 is also used to determine the first wireless bearer group of the side link corresponding to the first target side identifier based on the correspondence between the wireless bearer group of the side link and the target side identifier, and deliver the data packet to the first wireless bearer group of the side link and send it out through the sending module 102.

[0231] In one possible design, the method also includes: the processing module 101 submits any one or more of the first target side identifier, the first QoS parameter and the communication type information to the sending module 102, so that the sending module 102 sends any one or more of the first target side identifier, the first QoS parameter and the communication type information to other devices for unicast communication or multicast communication.

[0232] In one possible design, the method further includes: processing module 101 broadcasting a set-up request via sending module 102, and receiving a set-up response via receiving module 103; wherein the set-up request is used to request establishment of unicast communication or multicast communication, and the set-up response is used to indicate establishment of unicast communication or multicast communication with communication device 100. For example, processing module 101 may support communication device 100 in executing S702 and S704.

[0233] In one possible design, the method further includes: processing module 101 receiving a request message via receiving module 103, and sending a response message via sending module 102; wherein the request message is used to request establishment of unicast communication or multicast communication with communication device 100; and the response message is used to instruct communication device 100 to determine whether to establish unicast communication or multicast communication. For example, processing module 101 may support communication device 100 in executing S904 and S905.

[0234] In one possible design, the method further includes: the processing module 101 broadcasting a discovery message via the sending module 102; wherein the discovery message is a radio resource control RRC message, and the discovery message is used to discover the communication device 100. For example, the processing module 101 can support the communication device 100 to execute S902.

[0235] Optionally, all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here. The communication device provided in the embodiment of the present application is used to perform the function of the first terminal device in the above communication method, and thus can achieve the same effect as the above communication method.

[0236] Exemplarily, the processing module 101 may be one or more processors, and the sending module 102 and the receiving module 103 may be communication interfaces for interacting with other network elements or devices outside the communication device. When the processing module 101 is one or more processors, and the sending module 102 and the receiving module 103 are integrated into a communication interface, the communication device 100 may be Figure 5 The communication device shown.

[0237] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using a software program, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The 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. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that can be accessed by a computer or may include one or more servers, data centers, or other data storage devices that can be integrated with the medium. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0238] Although the present application is described herein in conjunction with various embodiments, in the process of implementing the claimed application, those skilled in the art can understand and implement other changes to the disclosed embodiments by reviewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple situations. A single processor or other unit can implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0239] Although the present application has been described with reference to specific features and embodiments thereof, it is apparent that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Accordingly, this specification and the drawings are merely illustrative of the present application as defined by the appended claims and are deemed to cover any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, those skilled in the art may make various modifications and variations to the present application without departing from the spirit and scope of the present application. Thus, the present application is intended to include such modifications and variations as fall within the scope of the claims of the present application and their equivalents.

Claims

1. A communication method for a first terminal device or a chip of the first terminal device, applied to a sidelink communication scenario, wherein the sidelink is a wireless communication link between the first terminal device and a second terminal device, characterized in that: The method comprises: The first protocol layer entity of the first terminal device submits communication type information and a target side identifier to the second protocol layer entity of the first terminal device; wherein the communication type information includes or is used to indicate a type of communication to be performed by the first terminal device, the communication type being unicast communication or multicast communication, and the target side identifier is used to identify the unicast communication or multicast communication; The second protocol layer entity of the first terminal device establishes a radio bearer group of the side link corresponding to the communication type according to the communication type information, wherein the radio bearer group of the side link corresponds to the target side identifier.

2. The method according to claim 1, characterized in that Configuration information of the radio bearer group of the sidelink is pre-stored on the first terminal device; or, The method also includes: the first terminal device receives configuration information of the radio bearer group of the side link sent by a radio access network device.

3. The method according to claim 1, characterized in that The method further comprises: The second protocol layer entity of the first terminal device sends a first message to the second protocol layer entity of the second terminal device, where the first terminal device and the second terminal device are performing or are about to perform the unicast communication or the multicast communication, and the first message includes configuration information of the radio bearer group of the sidelink; The second protocol layer entity of the first terminal device receives the first response sent by the second terminal device.

4. The method according to claim 3, characterized in that The method further comprises: If the second protocol layer entity of the first terminal device does not receive the first response when the time is greater than or equal to the set time, the second protocol layer entity of the first terminal device resends the first message to the second protocol layer entity of the second terminal device.

5. The method according to claim 4, characterized in that The method further comprises: The second protocol layer entity of the first terminal device determines a security mode configuration; wherein the security mode configuration includes relevant configurations of the first terminal device performing confidentiality protection and integrity protection on the first message; The second protocol layer entity of the first terminal device sends a first message to the second protocol layer entity of the second terminal device, including: the second protocol layer entity of the first terminal device sends the first message and the security mode configuration to the Packet Data Convergence Protocol PDCP layer entity of the first terminal device, and the PDCP layer entity of the first terminal device performs confidentiality protection and integrity protection on the first message according to the security mode configuration and then sends it to the second protocol layer entity of the second terminal device.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: The first protocol layer entity of the first terminal device delivers a data packet and a first target side identifier to a Service Data Adaptation Protocol (SDAP) layer entity of the first terminal device; The SDAP layer entity of the first terminal device determines the first radio bearer group of the side link corresponding to the first target side identifier according to the correspondence between the radio bearer group of the side link and the target side identifier, and delivers the data packet to the Packet Data Convergence Protocol PDCP layer entity corresponding to the first radio bearer group of the side link; The PDCP layer entity processes the data packet to obtain a PDCP protocol data unit (PDU), and delivers the PDCP PDU to a radio link control (RLC) layer entity corresponding to the first radio bearer group of the sidelink; The RLC layer entity processes the PDCP PDU to obtain an RLC PDU, and delivers the RLC PDU to a media access control MAC layer entity of the first terminal device; The MAC layer entity of the first terminal device processes the RLC PDU to obtain a MAC PDU, and delivers the MAC PDU to the physical PHY layer entity of the first terminal device.

7. The method according to claim 6, characterized in that The method further includes: a first protocol layer entity of the first terminal device submitting a first quality of service QoS parameter to an SDAP layer entity of the first terminal device; The delivering the data packet to the Packet Data Convergence Protocol PDCP layer entity corresponding to the first radio bearer group of the side link includes: determining the first radio bearer corresponding to the first QoS parameter in the first radio bearer group of the side link according to the correspondence between the QoS parameter and the radio bearer of the side link, and delivering the data packet to the PDCP layer entity corresponding to the first radio bearer.

8. The method according to claim 7, characterized in that The method further comprises: The MAC layer entity of the first terminal device delivers any one or more of the first target side identifier, the first QoS parameter and the communication type information to the PHY layer entity of the first terminal device.

9. The method according to any one of claims 1 to 5, characterized in that The method further comprises: The first protocol layer entity of the first terminal device broadcasts a setup request; wherein the setup request is used to request establishment of the unicast communication or the multicast communication; The first protocol layer entity of the first terminal device receives a setup response, wherein the setup response is used to indicate the establishment of the unicast communication or the multicast communication with the first terminal device.

10. The method according to any one of claims 1 to 5, characterized in that The method further comprises: The second protocol layer entity of the first terminal device receives a request message; wherein the request message is used to request to establish the unicast communication or the multicast communication with the first terminal device; The second protocol layer entity of the first terminal device sends a response message; wherein, the response message is used to instruct the first terminal device to determine to establish the unicast communication or the multicast communication.

11. The method according to claim 10, characterized in that The method further comprises: The first protocol layer entity of the first terminal device or the second protocol layer entity of the first terminal device broadcasts a discovery message; wherein, the discovery message is a radio resource control RRC message, and the discovery message is used to discover the first terminal device.

12. A communication device, characterized in that: The communication device includes: a processing module and a sending module, and the processing module and the sending module are used to implement the communication method according to any one of claims 1 to 11.

13. A communication device, characterized in that: The communication device includes one or more processors and one or more memories; the one or more memories are coupled to the one or more processors, and the one or more memories store computer instructions; When the one or more processors execute the computer instructions, the communication device is caused to perform the communication method according to any one of claims 1 to 11.

14. A computer storage medium, characterized in that The computer storage medium includes computer instructions, and when the computer instructions are executed on a computer, the computer is caused to execute the communication method according to any one of claims 1 to 11.

15. A communication system, characterized in that: include: The communication device according to claim 12 or 13.

16. A computer program product, characterized in that The computer program product includes computer instructions, and when the computer instructions are executed on a computer, the computer is caused to execute the communication method according to any one of claims 1 to 11.

Images