CN115769662A

CN115769662A - Wireless communication method and terminal device

Info

Publication number: CN115769662A
Application number: CN202080102224.7A
Authority: CN
Inventors: 卢前溪
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2020-08-05
Filing date: 2020-08-05
Publication date: 2023-03-07
Also published as: WO2022027341A1

Abstract

A wireless communication method and a terminal device are provided, the method comprising: determining a first quality of service flow, qoS, parameter for the end-to-end communication; a second QoS parameter for the point-to-point communication is determined based on the first QoS parameter. By constructing the second QoS parameter, it is equivalent to converting the QoS parameter for the end-to-end communication into the QoS parameter for the point-to-point in the process of converting the end-to-end communication into the point-to-point communication, whereby the communication quality of the end-to-end communication can be ensured even if the end-to-end communication is converted into the point-to-point communication.

Description

Wireless communication method and terminal device

Technical Field

The present embodiments relate to the field of communications, and in particular, to a wireless communication method and a terminal device.

Background

End-to-end communication refers to terminal-to-terminal communication. For example, vehicle to Vehicle (V2V), vehicle to other devices (V2X), terminal to terminal (D2D), etc. Specifically, the sending end sends a Direct Communication Request (DCR) message to the receiving end, and if the receiving end responds to the DCR message, the receiving end and the sending end can directly communicate with each other.

If the distance between the sending end and the request end is too far, the end-to-end communication between the sending end and the request end needs to be realized through the relay terminal, but the communication quality cannot be ensured by the end-to-end communication realized through the relay terminal.

Disclosure of Invention

A wireless communication method and terminal equipment are provided, which not only can realize end-to-end communication, but also can ensure the communication quality of the end-to-end communication.

In a first aspect, a wireless communication method is provided, including:

determining a first quality of service flow, qoS, parameter for the end-to-end communication;

determining a second QoS parameter for the point-to-point communication based on the first QoS parameter.

In a second aspect, a terminal device is provided, which is configured to perform the method in the first aspect or each implementation manner thereof. Specifically, the terminal device includes a functional module configured to execute the method in the first aspect or each implementation manner thereof.

In a third aspect, a terminal device is provided that includes a processor and a memory. The memory is configured to store a computer program, and the processor is configured to call and execute the computer program stored in the memory to perform the method in the first aspect or each implementation manner thereof.

In a fourth aspect, a chip is provided for implementing the method in the first aspect or its implementation manners. Specifically, the chip includes: a processor, configured to call and run a computer program from a memory, so that a device in which the chip is installed performs the method in any one of the first aspect to the second aspect or the implementation manners thereof.

In a fifth aspect, a computer-readable storage medium is provided for storing a computer program, the computer program causing a computer to execute the method of the first aspect or its implementation modes.

A sixth aspect provides a computer program product comprising computer program instructions for causing a computer to perform the method of the first aspect or its implementations.

In a seventh aspect, a computer program is provided, which, when run on a computer, causes the computer to perform the method of the implementations of the first aspect.

Based on the above technical solution, by constructing the second QoS parameter, it is equivalent to that the QoS parameter for the peer-to-peer communication is converted into the QoS parameter for the peer-to-peer communication also in the process of converting the peer-to-peer communication into the peer-to-peer communication, and thereby, even if the peer-to-peer communication is converted into the peer-to-peer communication, the communication quality of the peer-to-peer communication can be ensured.

Drawings

Fig. 1 is an example of a system framework provided in an embodiment of the present application.

Fig. 2 is a schematic flow chart of a wireless communication method according to an embodiment of the present application.

Fig. 3 is a schematic block diagram of a terminal device according to an embodiment of the present application.

Fig. 4 is another schematic block diagram of a terminal device according to an embodiment of the present application.

Fig. 5 is a schematic block diagram of a chip provided in an embodiment of the present application.

Detailed Description

The technical solution in the embodiments of the present invention will be described below with reference to the accompanying drawings.

Fig. 1 is an example of a system framework 100 provided by an embodiment of the present application.

As shown in fig. 1, the system framework 100 may include a first remote terminal 110, a first relay terminal 120, a second relay terminal 130, and a second remote terminal 140, the first remote terminal 110 may communicate with The second remote terminal 140 through The first relay terminal 120 and The second relay terminal 130, and The first remote terminal 110, the first relay terminal 120, the second relay terminal 130, and The second remote terminal 140 all support a New Radio (NR) PC5 interface protocol of The third Generation Partnership project (3 gpp).

As an example, the first remote terminal 110, the first relay terminal 120, the second relay terminal 130, and the second remote terminal 140 may be terminal devices that have been authenticated through a network when there is network coverage. The first Remote terminal 110 and the second Remote terminal 140 may be terminal devices that are authenticated as being accessible to the wireless network through a relay terminal, in other words, the first Remote terminal 110 and the second Remote terminal are authorized to be Remote user equipment (Remote UE). The first relay terminal 120 and the second relay terminal 130 may be terminal devices that are authenticated to be operable as relay nodes. The first remote terminal 110, the first relay terminal 120, the second relay terminal 130, and the second remote terminal 140 may all be authorized to transmit and receive relay discovery related messages, which may include discovery messages and discovery request messages.

The first remote terminal 110, the first relay terminal 120, the second relay terminal 130, and the second remote terminal 140 may be any device or apparatus configured with a physical layer and a media access control layer, and a terminal device may also be referred to as an access terminal. Such as a User Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device having Wireless communication capabilities, a computing device or other linear processing device connected to a Wireless modem, a vehicle mounted device, a wearable device, or the like. The embodiment of the present invention is described by taking a vehicle-mounted terminal as an example, but is not limited thereto.

As shown in fig. 1, the first remote terminal 110 and the second remote terminal 140 may support an end-to-end Protocol stack, where the end-to-end Protocol stack may include a Packet Data Convergence Protocol (PDCP) layer of a 3gpp PC5 interface and an upper Protocol layer above the PDCP layer, and the upper Protocol layer may include a user plane Protocol layer and a control plane Protocol layer. The user plane Protocol layer includes, but is not limited to, a Service Data Adaptation Protocol (SDAP) layer and an Internet Protocol (IP) layer, and the Control plane Protocol layer includes, but is not limited to, a Radio Resource Control (RRC) layer and a non-access stratum (NAS).

As shown in fig. 1, the first remote terminal 110, the first relay terminal 120, the second relay terminal 130, and the second remote terminal 140 may support a point-to-point protocol stack, where the point-to-point protocol stack may include layer 2 (L2) and layer 1 (L1) protocol stacks of a 3gpp PC5 interface, and the L1 and L2 protocol stacks include, but are not limited to, a Radio Link Control (RLC) layer, a Media Access Control (MAC) layer, and a Physical (PHY) layer. In addition, a relay protocol layer may be further included between the PDCP protocol layer and the PC5 layer 1/2 protocol layer. The functions of the relay protocol layer may be used to communicate data packets and related control information between remote terminals through relay terminals.

In the framework 100, the first Remote terminal (Remote UE) 110 may be connected to the second Remote terminal 140 through the first relay terminal 120 and the second relay terminal 130. Specifically, the first remote terminal 110 and the first relay terminal 120, the first relay terminal 120 and the second relay terminal 130, and the second relay terminal and the second remote terminal 140 may be connected or communicate with each other through a PC5 interface of a 3GPP system. The end-to-end connection between the first remote terminal 110 and the second remote terminal 140 may also be performed through a PC5 interface of the 3GPP system.

It should be understood that fig. 1 is only an example of the present application and should not be construed as limiting the present application.

For example, the system framework 100 may be a system framework in which any terminal relays a terminal to another terminal. For example, the frame 100 may be a system frame from a vehicle-mounted terminal to a vehicle-mounted terminal through a relay terminal. For example, a remote vehicle may relay the vehicle to the remote vehicle, the remote vehicle may relay the vehicle to another device, the remote terminal may relay the vehicle to the remote terminal, and so on.

For another example, in the system framework 100, the number of relay terminals is 2, but the present application is not limited thereto. For example, the present application is also applicable to a system framework for inbound peer-to-peer communication through one or more relay terminals.

Fig. 2 shows a schematic flow diagram of a wireless communication method 200 according to an embodiment of the application, which method 200 may be performed by a terminal device. The terminal device may be any one of the first remote terminal 110, the first relay terminal 120, the second relay terminal 130, and the second remote terminal 140 shown in fig. 1. In other words, the method 200 may be applied to a transmitting end, a relay terminal, and a receiving end in end-to-end communication. For convenience of explanation, the method 200 is described below by taking the first remote terminal shown in fig. 1 as a transmitting end and the second remote terminal shown in fig. 1 as a receiving end as an example.

As shown in fig. 2, the method 200 may include some or all of the following:

s210, determining a first Quality of service (QoS) parameter for end-to-end communication.

S220, determining a second QoS parameter for the point-to-point communication based on the first QoS parameter.

For example, after the first remote terminal, the relay terminal, or the second remote terminal determines the first QoS parameter, the second QoS parameter may be determined based on the first QoS parameter, and then the peer-to-peer communication may be performed based on the second QoS parameter.

As an example, the first remote terminal, the relay terminal between the first remote terminal and the second remote terminal, and the second remote terminal all have corresponding identifiers, and the identifiers may be used to uniquely identify terminal devices. In point-to-point communication, a packet sent from one node to another may contain a SOURCE identification (SOURCE ID) and a DESTINATION identification (DESTINATION ID). When two remote terminals of end-to-end communication need to communicate, the two remote terminals can multiplex the identifiers used in the point-to-point communication.

By constructing the second QoS parameter, it is equivalent to converting the QoS parameter for the end-to-end communication into the QoS parameter for the point-to-point in the process of converting the end-to-end communication into the point-to-point communication, whereby the communication quality of the end-to-end communication can be ensured even if the end-to-end communication is converted into the point-to-point communication.

In some embodiments of the present application, the method 200 may further comprise:

establishing a radio bearer for the point-to-point communication based on the second QoS parameter.

For example, the first remote terminal, the relay terminal, or the second remote terminal establishes the PC5 radio bearer of the peer-to-peer communication based on the second QoS parameter. Optionally, one radio bearer may be used to carry at least one QoS flow.

In some embodiments of the present application, the S220 may include:

acquiring the number of PC5 interfaces in the end-to-end communication;

determining the second QoS based on the number of PC5 interfaces in the end-to-end communication and the first QoS parameter.

For example, after the first remote terminal, the relay terminal, or the second remote terminal obtains the number of PC5 interfaces in the end-to-end communication and the first QoS parameter, the second QoS parameter may be determined based on the number of PC5 interfaces in the end-to-end communication and the first QoS parameter, and then, a radio bearer in the point-to-point communication may be established based on the second QoS parameter.

The number of PC5 interfaces in the peer-to-peer communication may also be used to indicate the number of relay terminals between the first remote terminal and the second remote terminal. For example, if the number of PC5 interfaces in the peer-to-peer communication is 3, the number of relay terminals between the first remote terminal and the second remote terminal is 2.

In some embodiments of the present application, a Packet Delay Budget (PDB) in the second QoS parameter is equal to 1/N of the PDB in the first QoS parameter, where N is the number of PC5 interfaces in the end-to-end communication.

In other words, the PDB of the radio bearer in the point-to-point communication is equal to 1/N of the PDB of the radio bearer in the end-to-end communication.

Alternatively, the PDB for point-to-point communication may be determined using the following equation:

PDB(P2P)＝PDB(E2E)/N。

wherein PDB (P2P) represents PDB for point-to-point communication, and said PDB (E2E) represents PDB for end-to-end communication.

For example, the PDB for end-to-end communication may be determined prior to establishing an end-to-end radio bearer between remote terminals. Before a point-to-point radio bearer is established between a remote terminal and a relay terminal or between relay terminals, the PDB for point-to-point communication needs to be determined according to the PDB for end-to-end communication and the number (N) of PC5 interfaces between the remote terminals. For example, the PDB for point-to-point communication is equal to 1/N of the PDB for end-to-end communication.

By constructing the PDB in the second QoS parameter as 1/N of the PDB in the first QoS parameter, the PDB on the PC5 interface in the point-to-point communication can meet the requirement of the PDB on the PC5 interface in the end-to-end communication.

In some embodiments of the present application, a packet loss ratio in the second QoS parameter is equal to 1/N power of a packet loss ratio in the first QoS parameter, where N is the number of PC5 interfaces in the end-to-end communication.

In other words, the packet loss rate of the radio bearer in the peer-to-peer communication is equal to 1/N power of the packet loss rate of the radio bearer in the end-to-end communication.

Alternatively, the packet loss rate for peer-to-peer communication may be determined using the following equation:

PER(P2P)＝(PER(E2E))^(1/N)。

wherein, PER (P2P) represents a packet loss rate for point-to-point communication, PER (E2E) represents a packet loss rate for end-to-end communication, and symbol ^ is a power operator.

For example, the packet loss rate for end-to-end communication is determined before the end-to-end radio bearer is established between the remote terminals. Before a point-to-point radio bearer is established between a remote terminal and a relay terminal or between relay terminals, the packet loss rate for point-to-point communication needs to be determined according to the packet loss rate for end-to-end communication and the number (N) of PC5 interfaces between the remote terminals. For example, the packet loss rate for peer-to-peer communication is equal to 1/N power of the packet loss rate for peer-to-peer communication.

Constructing the packet loss rate in the second QoS parameter to be 1/N power of the packet loss rate in the first QoS parameter, which is equivalent to that the packet loss rate in end-to-end communication is equal to the product of the packet loss rates in each segment of point-to-point communication. For example, the packet loss rate in peer-to-peer communication is 90%, and N =2, the packet loss rate in end-to-end communication is equal to 90% × 90% =81%, so that the packet loss rate on the PC5 interface in peer-to-peer communication can meet the packet loss rate requirement on the PC5 interface in end-to-end communication.

In some embodiments of the present application, parameters other than PDB and packet loss rate in the second QoS parameters are the same as those in the first QoS parameters.

In other words, in the point-to-point communication, other QoS parameters are the same in the point-to-point communication and in the end-to-end communication except for the PDB and the packet loss rate. The remote terminal or the relay terminal may establish a PC5 radio bearer for the point-to-point communication based on the converted QoS parameters for the point-to-point communication.

In some embodiments of the present application, the number of PC5 interfaces in the end-to-end communication is a value obtained by a counter in a relay protocol layer.

In some embodiments of the present application, the counter is configured to count the number of times of sending or receiving a first relay protocol data packet, where the first protocol data packet is a data packet sent by a first remote terminal to a second remote terminal through a relay terminal, and a final count value in the first relay protocol data packet is used to determine the number of PC5 interfaces in the end-to-end communication.

Correspondingly, after receiving the relay protocol data packet, the second remote terminal may determine the number of PC5 interfaces in the end-to-end communication based on a count value in the relay protocol data packet after passing through the relay protocol layer. For example, the number of PC5 interfaces in the end-to-end communication is equal to the final count value in the first relay protocol packet.

For example, the counter is configured to count the number of times of sending the first relay protocol packet, an initial count value in the first relay protocol packet is 1, the count value in the first relay protocol packet is incremented by 1 when the relay protocol packet passes through a relay protocol layer of a relay terminal, and the count value in the relay protocol packet is unchanged when the first relay protocol packet passes through the relay protocol layer of the second remote terminal.

For another example, the counter is configured to count the number of times of receiving the first relay protocol data packet, an initial count value in the relay protocol data packet is 0, and 1 is added when the relay protocol data packet passes through a relay protocol layer of the relay terminal and when the relay protocol data packet passes through a relay protocol layer of the second remote terminal.

Of course, the counter may also be used to count other information, and the present application is not limited to this. For example, the counter may also be configured to count the number of relay terminals between the first remote terminal and the second remote terminal through which the first relay protocol data packet passes, where the number of PC5 interfaces in the end-to-end communication is equal to the number of relay terminals of the first remote terminal and the second remote terminal plus 1.

In some embodiments of the present application, the first relay protocol data packet includes the first QoS parameter. The first QoS parameter may be for a relay terminal between the first remote terminal and the second remote terminal, and the second remote terminal determines the second QoS parameter.

In some embodiments of the present application, the number of PC5 interfaces in the end-to-end communication is a value indicated by a second relay protocol packet including a response message, where the second relay protocol packet is a packet sent by the second remote terminal to the first remote terminal through a relay terminal. Optionally, the second relay protocol data packet further includes the first QoS parameter and/or the second QoS parameter.

In other words, the second remote terminal may indicate the number of PC5 interfaces in the end-to-end communication to the first remote terminal or a relay terminal between the first remote terminal and the second remote terminal through the second relay protocol packet. Optionally, the second remote terminal may further notify the determined first QoS parameter to a relay terminal between the first remote terminal and the second remote terminal through the second relay protocol data packet. Thereby, the relay terminal may determine the second QoS parameter based on the first QoS parameter and the number of PC5 interfaces in the end-to-end communication. Optionally, the second remote terminal may further notify the second QoS parameter to the first remote terminal or a relay terminal between the first remote terminal and the second remote terminal through the second relay protocol data packet, so that the first remote terminal or the relay terminal between the first remote terminal and the second remote terminal directly balances the received second QoS parameter to establish the point-to-point radio bearer.

In some embodiments of the present application, the number of PC5 interfaces or the number of relay terminals in the end-to-end communication is preset, and/or the maximum number of PC5 interfaces or the maximum number of relay terminals in the end-to-end communication is configured.

In other words, the first remote terminal, the relay terminal, and the second remote terminal all know the number of PC5 interfaces in the end-to-end communication or the number of relay terminals in the end-to-end communication. Optionally, the number of relay terminals in the end-to-end communication may be used to determine the number of PC5 interfaces in the end-to-end communication. Based on the method, the first remote terminal can exchange request and response messages of link establishment with the second remote terminal through the relay terminal. In this process, the first remote terminal and the second remote terminal determine an end-to-end QoS parameter of a QoS flow (QoS flow) to be established, i.e. the first QoS parameter; then, the first remote terminal, the relay terminal, and the second remote terminal may determine the second QoS parameter based on the first QoS parameter and the number of PC5 interfaces in the end-to-end communication, and establish a radio bearer based on the second QoS parameter.

Of course, alternatively, the number of PC5 interfaces or the number of relay terminals in the end-to-end communication may also be configured, and/or the maximum number of PC5 interfaces or the maximum number of relay terminals in the end-to-end communication is preset. Presets in this application may also be referred to as predefined, e.g., predefined in a standard protocol. Configuration in this application may refer to network device configuration, e.g., static configuration, semi-static configuration, or dynamic configuration.

In some embodiments of the present application, the number of PC5 interfaces in said peer-to-peer communication is greater than or equal to 2. For example, the number of PC5 interfaces in the peer-to-peer communication is equal to 3.

establishing a communication link for the point-to-point communication.

For example, the first remote terminal, the relay terminal, or the second remote terminal may establish a communication link of the point-to-point communication between the radio bearers.

In some embodiments of the present application, the second QoS parameter is included in a link setup request message for the communication link. Thereby, a radio bearer for point-to-point communication may be established between the first remote terminal and the relay terminal based on said second QoS parameter.

The preferred embodiments of the present application have been described in detail with reference to the accompanying drawings, however, the present application is not limited to the details of the above embodiments, and various simple modifications may be made to the technical solution of the present application within the technical idea of the present application, and these simple modifications all belong to the protection scope of the present application. For example, the various features described in the foregoing detailed description may be combined in any suitable manner without contradiction, and various combinations that may be possible are not described in this application in order to avoid unnecessary repetition. For example, various embodiments of the present application may be arbitrarily combined with each other, and the same should be considered as the disclosure of the present application as long as the concept of the present application is not violated.

It should also be understood that, in the various method embodiments of the present application, the sequence numbers of the above-mentioned processes do not imply any order of execution, and the order of execution of the processes should be determined by their functions and inherent logic, and should not constitute any limitation to the implementation processes of the embodiments of the present application. In addition, in the embodiment of the present application, the terms "downlink" and "uplink" are used to indicate the transmission direction of a signal or data, where "downlink" is used to indicate that the transmission direction of the signal or data is a first direction transmitted from a station to a user equipment of a cell, and "uplink" is used to indicate that the transmission direction of the signal or data is a second direction transmitted from the user equipment of the cell to the station, for example, "downlink signal" indicates that the transmission direction of the signal is the first direction. In addition, in the embodiment of the present application, the term "and/or" is only one kind of association relationship for describing an associated object, and means that three kinds of relationships may exist. Specifically, a and/or B may represent: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter associated objects are in an "or" relationship.

Method embodiments of the present application are described in detail above in conjunction with fig. 2, and apparatus embodiments of the present application are described in detail below in conjunction with fig. 3-5.

Fig. 3 is a schematic block diagram of a terminal device 300 according to an embodiment of the present application. The terminal device may be a transmitting remote terminal, a receiving remote terminal, or a relay terminal. In other words, the terminal device may be any one of the first remote terminal described above, the second remote terminal described above, or a relay terminal between the first remote terminal and the second remote terminal.

As shown in fig. 3, the terminal device 300 may include:

in some embodiments of the present application, a processing unit 310 is included, the processing unit 310 is configured to:

a second QoS parameter for the point-to-point communication is determined based on the first QoS parameter.

In some embodiments of the present application, the processing unit 310 is further configured to:

In some embodiments of the present application, the processing unit 310 is specifically configured to:

acquiring the number of PC5 interfaces in the end-to-end communication;

In some embodiments of the present application, the packet delay budget PDB in the second QoS parameter is equal to 1/N of the PDB in the first QoS parameter, where N is the number of PC5 interfaces in the end-to-end communication.

In some embodiments of the present application, the parameters of the second QoS parameters except for the packet delay budget PDB and the packet loss ratio are the same as those of the first QoS parameters.

In some embodiments of the present application, the counter is configured to count the number of times of sending the first relay protocol packet, an initial count value in the first relay protocol packet is 1, the count value in the first relay protocol packet is increased by 1 when the relay protocol packet passes through a relay protocol layer of a relay terminal, and the count value in the relay protocol packet is unchanged when the first relay protocol packet passes through the relay protocol layer of the second remote terminal.

In some embodiments of the present application, the counter is configured to count the number of times of receiving the first relay protocol data packet, an initial count value in the relay protocol data packet is 0, and the relay protocol data packet is respectively incremented by 1 when passing through a relay protocol layer of a relay terminal and when passing through a relay protocol layer of the second remote terminal.

In some embodiments of the present application, the number of PC5 interfaces in the end-to-end communication is equal to the final count value in the first relay protocol packet.

In some embodiments of the present application, the first relay protocol data packet includes the first QoS parameter.

In some embodiments of the present application, the number of PC5 interfaces in the end-to-end communication is a numerical value indicated by a second relay protocol packet including a response message, where the second relay protocol packet is a packet sent by the second remote terminal to the first remote terminal through the relay terminal.

In some embodiments of the present application, the second relay protocol data packet further comprises the first QoS parameter and/or the second QoS parameter.

In some embodiments of the present application, the number of PC5 interfaces in said peer-to-peer communication is greater than or equal to 2.

establishing a communication link for the point-to-point communication.

In some embodiments of the present application, the second QoS parameter is included in a link establishment request message for the communication link.

It is to be understood that apparatus embodiments and method embodiments may correspond to one another and that similar descriptions may refer to method embodiments. Specifically, the terminal device 300 shown in fig. 3 may correspond to a corresponding main body executing the method 200 in the embodiment of the present application, and the foregoing and other operations and/or functions of each unit in the terminal device 300 are respectively for implementing corresponding flows in each method in fig. 1, and are not described again here for brevity.

The communication device of the embodiments of the present application is described above from the perspective of functional modules in conjunction with the drawings. It should be understood that the functional modules may be implemented by hardware, by instructions in software, or by a combination of hardware and software modules.

Specifically, the steps of the method embodiments in the present application may be implemented by integrated logic circuits of hardware in a processor and/or instructions in the form of software, and the steps of the method disclosed in the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor.

Alternatively, the software modules may be located in random access memory, flash memory, read only memory, programmable read only memory, electrically erasable programmable memory, registers, and the like, as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps in the above method embodiments in combination with hardware thereof.

For example, the processing unit and the communication unit referred to above may be implemented by a processor and a transceiver, respectively.

Fig. 4 is a schematic structural diagram of a communication device 400 according to an embodiment of the present application.

As shown in fig. 4, the communication device 400 may include a processor 410.

From which processor 410 may invoke and execute a computer program to implement the methods in the embodiments of the present application.

With continued reference to fig. 4, the communication device 400 may also include a memory 420.

The memory 420 may be used for storing indication information, and may also be used for storing codes, instructions, and the like executed by the processor 410. From the memory 420, the processor 410 may call and run a computer program to implement the method in the embodiment of the present application. The memory 420 may be a separate device from the processor 410 or may be integrated into the processor 410.

With continued reference to fig. 4, the communication device 400 may also include a transceiver 430.

The processor 410 may control the transceiver 430 to communicate with other devices, and specifically, may transmit information or data to the other devices or receive information or data transmitted by the other devices. The transceiver 430 may include a transmitter and a receiver. The transceiver 430 may further include antennas, and the number of antennas may be one or more.

It should be understood that the various components in the communication device 400 are connected by a bus system that includes a power bus, a control bus, and a status signal bus in addition to a data bus.

It should also be understood that the communication device 400 may be configured to implement the corresponding processes implemented by the terminal device in the methods of the embodiments of the present application, that is, the communication device 400 of the embodiments of the present application may correspond to the terminal device 300 in the embodiments of the present application, and may correspond to the corresponding main body in executing the method 200 according to the embodiments of the present application, and for brevity, no further description is provided here.

In addition, the embodiment of the application also provides a chip.

For example, the chip may be an integrated circuit chip having signal processing capabilities and capable of implementing or executing the methods, steps and logic blocks disclosed in the embodiments of the present application. The chip may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc. Alternatively, the chip may be applied to various communication devices, so that the communication device mounted with the chip can execute the methods, steps and logic blocks disclosed in the embodiments of the present application.

Fig. 5 is a schematic block diagram of a chip 500 according to an embodiment of the present application.

As shown in fig. 5, the chip 500 includes a processor 510.

From which processor 510 may invoke and execute computer programs to implement the methods of the embodiments of the present application.

With continued reference to fig. 5, the chip 500 may further include a memory 520.

From the memory 520, the processor 510 may call and run a computer program to implement the method in the embodiment of the present application. The memory 520 may be used to store instructions, codes, instructions, etc. that are executed by the processor 510. The memory 520 may be a separate device from the processor 510 or may be integrated into the processor 510.

With continued reference to fig. 5, the chip 500 may further include an input interface 530.

The processor 510 may control the input interface 530 to communicate with other devices or chips, and in particular, may obtain information or data transmitted by other devices or chips.

With continued reference to fig. 5, the chip 500 may further include an output interface 540.

The processor 510 may control the output interface 540 to communicate with other devices or chips, and may particularly output information or data to the other devices or chips.

It should be understood that the chip 500 may be applied to a network device in this embodiment, and the chip may implement a corresponding process implemented by the network device in each method in this embodiment, and may also implement a corresponding process implemented by a terminal device in each method in this embodiment, which are not described herein again for brevity.

It will also be appreciated that the various components in the chip 500 are connected by a bus system that includes a power bus, a control bus, and a status signal bus in addition to a data bus.

The processors referred to above may comprise, but are not limited to:

general purpose processors, digital Signal Processors (DSPs), application Specific Integrated Circuits (ASICs), field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and the like.

The processor may be used to implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present application. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules may be located in ram, flash, rom, prom, eprom, registers, etc. storage media as is known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.

The memories referred to above include, but are not limited to:

volatile memory and/or non-volatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), enhanced Synchronous SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

It should be noted that the memory described herein is intended to comprise these and any other suitable types of memory.

The embodiment of the application also provides a computer readable storage medium for storing the computer program. The computer readable storage medium stores one or more programs, the one or more programs comprising instructions, which when executed by a portable electronic device comprising a plurality of application programs, enable the portable electronic device to perform the method of the illustrated embodiment of method 200.

Optionally, the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program enables a computer to execute corresponding processes implemented by the network device in the methods in the embodiment of the present application, which are not described herein again for brevity.

Optionally, the computer-readable storage medium may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

The embodiment of the application also provides a computer program product comprising the computer program.

Optionally, the computer program product may be applied to the network device in the embodiment of the present application, and the computer program enables a computer to execute a corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the computer program product may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

The embodiment of the application also provides a computer program. The computer program, when executed by a computer, enables the computer to perform the methods of the illustrated embodiment of method 200.

Optionally, the computer program may be applied to the network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute a corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.

In addition, an embodiment of the present application further provides a communication system, where the communication system may include the terminal device and the network device mentioned above to form the communication system 100 shown in fig. 1, and details are not described herein for brevity. It should be noted that the term "system" and the like herein may also be referred to as "network management architecture" or "network system" and the like.

It is also to be understood that the terminology used in the description of the embodiments and the appended claims is for the purpose of describing particular embodiments only, and is not intended to be limiting of the embodiments.

For example, as used in the examples of this application and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.

Those of skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the embodiments of the present application.

If implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application, which are essential or part of the technical solutions contributing to the prior art, may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: u disk, removable hard disk, read only memory, random access memory, magnetic or optical disk, etc. for storing program codes.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways.

For example, the division of units or modules or components in the above-described device embodiments is only a logical division, and other divisions may be realized in practice, for example, multiple units or modules or components may be combined or integrated into another system, or some units or modules or components may be omitted, or not executed.

Also for example, the units/modules/components described above as separate/display components may or may not be physically separate, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the units/modules/components can be selected according to actual needs to achieve the purposes of the embodiments of the present application.

Finally, it should be noted that the above shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The above description is only a specific implementation of the embodiments of the present application, but the scope of the embodiments of the present application is not limited thereto, and any person skilled in the art can easily conceive of changes or substitutions within the technical scope of the embodiments of the present application, and all the modifications and substitutions should be covered by the scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application shall be subject to the protection scope of the claims.

Claims

A method of wireless communication, comprising:

determining a first quality of service flow, qoS, parameter for the end-to-end communication;

determining a second QoS parameter for the point-to-point communication based on the first QoS parameter.
The method of claim 1, further comprising:

establishing a radio bearer for the point-to-point communication based on the second QoS parameter.
The method of claim 1 or 2, wherein determining the second QoS parameter for the peer-to-peer communication based on the first QoS parameter comprises:

acquiring the number of PC5 interfaces in the end-to-end communication;

determining the second QoS based on the number of PC5 interfaces in the end-to-end communication and the first QoS parameter.
The method of claim 3, wherein the packet delay budget PDB in the second QoS parameter is equal to 1/N of the PDB in the first QoS parameter, where N is the number of PC5 interfaces in the end-to-end communication.
The method of claim 3, wherein the packet loss ratio in the second QoS parameter is equal to 1/Nth power of the packet loss ratio in the first QoS parameter, where N is the number of PC5 interfaces in the end-to-end communication.
The method of claim 3, wherein the parameters of the second QoS parameters other than the packet delay budget PDB and packet loss ratio are the same as the parameters of the first QoS parameters.
The method according to any of claims 3 to 6, wherein the number of PC5 interfaces in the end-to-end communication is a value obtained by a counter in a relay protocol layer.
The method according to claim 7, wherein the counter is configured to count a number of times of sending or receiving a first relay protocol packet, the first protocol packet is a packet sent by a first remote terminal to a second remote terminal through a relay terminal, and a final count value in the first relay protocol packet is used to determine the number of PC5 interfaces in the end-to-end communication.
The method of claim 8, wherein the counter is configured to count the number of transmissions of the first relay protocol packet, an initial count value in the first relay protocol packet is 1, the count value in the first relay protocol packet is increased by 1 when the relay protocol packet passes through a relay protocol layer of a relay terminal, and the count value in the relay protocol packet is unchanged when the first relay protocol packet passes through the relay protocol layer of the second remote terminal.
The method of claim 8, wherein the counter is configured to count the number of times of receiving the first relay protocol packet, an initial count value in the relay protocol packet is 0, and the relay protocol packet is incremented by 1 when passing through a relay protocol layer of a relay terminal and when passing through a relay protocol layer of the second remote terminal.
The method of claim 8, wherein the number of PC5 interfaces in the end-to-end communication is equal to a final count value in the first relay protocol packet.
The method according to any of claims 8 to 11, wherein the first relay protocol packet comprises the first QoS parameter.
The method according to any one of claims 8 to 12, wherein the number of PC5 interfaces in the end-to-end communication is a value indicated by a second relay protocol packet including a response message, and the second relay protocol packet is a packet sent by the second remote terminal to the first remote terminal through a relay terminal.
The method of claim 13, wherein the second relay protocol packet further comprises the first QoS parameter and/or the second QoS parameter.
The method according to any one of claims 3 to 6, wherein the number of PC5 interfaces or the number of relay terminals in the end-to-end communication is preset, and/or the maximum number of PC5 interfaces or the maximum number of relay terminals in the end-to-end communication is configured.
The method according to any of claims 3 to 15, wherein the number of PC5 interfaces in the peer-to-peer communication is greater than or equal to 2.
The method according to any one of claims 1 to 16, further comprising:

establishing a communication link for the point-to-point communication.
The method of claim 17, wherein the second QoS parameter is included in a link setup request message for the communication link.
A terminal device, comprising a processing unit configured to:

determining a first quality of service flow, qoS, parameter for the end-to-end communication;

determining a second QoS parameter for the point-to-point communication based on the first QoS parameter.
The terminal device of claim 19, wherein the processing unit is further configured to:

establishing a radio bearer for the point-to-point communication based on the second QoS parameter.
The terminal device according to claim 19 or 20, wherein the processing unit is specifically configured to:

acquiring the number of PC5 interfaces in the end-to-end communication;

determining the second QoS based on the number of PC5 interfaces in the end-to-end communication and the first QoS parameter.
The terminal device of claim 21, wherein a Packet Delay Budget (PDB) in the second QoS parameter is equal to 1/N of a PDB in the first QoS parameter, where N is a number of PC5 interfaces in the end-to-end communication.
The terminal device of claim 21, wherein a packet loss ratio in the second QoS parameter is equal to 1/nth power of a packet loss ratio in the first QoS parameter, where N is the number of PC5 interfaces in the end-to-end communication.
The terminal device of claim 21, wherein the parameters of the second QoS parameters other than the packet delay budget PDB and the packet loss ratio are the same as those of the first QoS parameters.
The terminal device according to any of claims 21 to 24, wherein the number of PC5 interfaces in the end-to-end communication is a value obtained by a counter in a relay protocol layer.
The terminal device according to claim 25, wherein the counter is configured to count a number of times of sending or receiving a first relay protocol packet, the first protocol packet is a packet sent by a first remote terminal to a second remote terminal through a relay terminal, and a final count value in the first relay protocol packet is used to determine the number of PC5 interfaces in the end-to-end communication.
The terminal device according to claim 26, wherein the counter is configured to count the number of times of sending the first relay protocol packet, an initial count value in the first relay protocol packet is 1, the count value in the first relay protocol packet is increased by 1 when the relay protocol packet passes through a relay protocol layer of a relay terminal, and the count value in the relay protocol packet is not changed when the first relay protocol packet passes through the relay protocol layer of the second remote terminal.
The terminal device according to claim 26, wherein the counter is configured to count the number of times of receiving the first relay protocol packet, an initial count value in the relay protocol packet is 0, and the relay protocol packet is incremented by 1 when passing through a relay protocol layer of the relay terminal and when passing through a relay protocol layer of the second remote terminal.
The terminal device of claim 26, wherein the number of PC5 interfaces in the end-to-end communication is equal to a final count value in the first relay protocol packet.
A terminal device according to any of claims 26 to 29, wherein the first relay protocol data packet includes the first QoS parameter.
The terminal device according to any one of claims 26 to 30, wherein the number of PC5 interfaces in the end-to-end communication is a value indicated by a second relay protocol packet including a response message, and the second relay protocol packet is a packet sent by the second remote terminal to the first remote terminal through a relay terminal.
A terminal device according to claim 31, wherein the second relay protocol data packet further comprises the first QoS parameter and/or the second QoS parameter.
The terminal device according to any of claims 21 to 24, wherein the number of PC5 interfaces or the number of relay terminals in the end-to-end communication is preset, and/or the maximum number of PC5 interfaces or the maximum number of relay terminals in the end-to-end communication is configured.
The terminal device according to any of claims 19 to 33, wherein the number of PC5 interfaces in the peer-to-peer communication is greater than or equal to 2.
The terminal device of any of claims 19-34, wherein the processing unit is further configured to:

establishing a communication link for the point-to-point communication.
A terminal device according to claim 35, wherein the second QoS parameter is included in a link establishment request message for the communications link.
A terminal device, comprising:

a processor, a memory for storing a computer program, and a transceiver, the processor for invoking and executing the computer program stored in the memory to perform the method of any of claims 1-20.
A chip, comprising:

a processor for calling and running a computer program from a memory so that a device on which the chip is installed performs the method of any one of claims 1 to 18.
A computer-readable storage medium for storing a computer program which causes a computer to perform the method of any one of claims 1 to 18.
A computer program product comprising computer program instructions to cause a computer to perform the method of any one of claims 1 to 18.
A computer program, characterized in that the computer program causes a computer to perform the method according to any of claims 1-18.