CN114793357A - Synchronous transmission method and device, storage medium, sending end equipment and receiving end equipment - Google Patents

Abstract

A synchronous transmission method and device, storage medium, sending end equipment and receiving end equipment are provided, the synchronous transmission method comprises: acquiring a data packet to be transmitted in one or more types of data streams; and synchronously transmitting the data packets in the same data block, wherein the data packets belonging to the same data block have the same block sequence number. The technical scheme of the invention can realize the synchronous transmission of the multi-mode service in the communication system so as to meet the service requirement of the user.

Description

Synchronous transmission method and device, storage medium, sender device, and receiver device

technical field

The present invention relates to the field of communication technologies, and in particular, to a synchronous transmission method and device, a storage medium, a sending end device, and a receiving end device.

Background technique

There are multiple QoS flows (flows) with different quality of service (QoS) in multimodal services.

Multiple data streams are included in the same service, and multiple data streams have different QoS requirements. For example, the data stream can be video, such as video/audio media; data obtained by sensors, such as brightness ), temperature, humidity; tactile data such as pressure, texture, vibration, temperature, gravity, pull forces, sense of position ( sense of position awareness), etc. Multiple data streams belonging to the same service need to be synchronously transmitted to the receiving end of the data stream for processing by the receiving end.

However, in a variety of data streams that need to be transmitted synchronously, the data packet generation rate of each data stream is different, and how to perform synchronization is a problem that needs to be solved.

SUMMARY OF THE INVENTION

The technical problem solved by the present invention is how to realize the synchronous transmission of multi-modal services in the communication system, so as to meet the service requirements of users.

In order to solve the above technical problem, an embodiment of the present invention provides a synchronous transmission method. The synchronous transmission method includes: acquiring data packets to be transmitted in one or more types of data streams; For synchronous transmission, data packets belonging to the same data block have the same block sequence number.

Optionally, the block sequence number is carried in the packet header of the synchronously transmitted data packet.

Optionally, the synchronous transmission of the data packets in the same data block includes: transmitting the data packets in the same data block by using transmission resources located within a preset time length.

Optionally, before the synchronous transmission of the data packets in the same data block, the method further includes: determining the first transmitted data packet and the last transmitted data packet in each data block; The data packet generates a block start transmission indication and carries it in the data packet header of the first transmitted data packet, and generates a block end transmission indication for the last transmitted data packet and carries it in the last transmitted data packet. in the packet header.

Optionally, the determining the first transmitted data packet and the last transmitted data packet in each data block includes: determining, in each data block, the first transmitted data packet in various types of data streams and The last transmitted packet.

Optionally, the synchronous transmission method further includes: if there is a data packet in the data block that needs to be transmitted in its entirety that has not been successfully sent, terminating the sending of the data packet that has not been successfully sent in the data block that needs to be transmitted in its entirety.

Optionally, the synchronous transmission method further includes: if there is a data packet that is not successfully sent in the data block that needs to be transmitted as a whole within a preset time length, then stop sending the data that is not successfully sent in the data block that needs to be transmitted as a whole. Bag.

Optionally, before the synchronous transmission of the data packets in the same data block, the method further includes: receiving indication information from a core network element, where the indication information is used to indicate whether the data block needs to be transmitted as a whole.

Optionally, the reported buffer status report includes block transmission status indication information, where the block transmission status indication information is used to indicate whether there is a data packet to be transmitted in the data block that needs to be transmitted as a whole in the buffer.

Optionally, the block transmission status indication information further includes the block sequence number of the data block that needs to be transmitted in its entirety.

Optionally, the buffer status report includes the block transmission status indication information corresponding to each logical channel or logical channel group.

Optionally, before the synchronous transmission of the data packets in the same data block, the method further includes: receiving block sequence number configuration information 1, where the block sequence number configuration information 1 is used to indicate whether to generate a block sequence number.

Optionally, the block sequence number configuration information 1 is used to indicate whether a single DRB, a PDU session or a data packet in a data stream generates a block sequence number.

Optionally, the receiving block sequence number configuration information 1 includes: if the data packet to be transmitted is an uplink data packet, receive the block sequence number configuration information 1 through message 1; if the data packet to be transmitted is a sidelink data packet, then The block sequence number configuration information one is received through downlink signaling.

Optionally, before the synchronous transmission of the data packets in the same data block, the method further includes: receiving block sequence number configuration information 2, where the block sequence number configuration information is used to indicate whether the received data packet contains a block sequence number.

Optionally, the sending the second block sequence number configuration information includes: if the data packet to be transmitted is a downlink data packet, sending the second block sequence number configuration information through message 2.

Optionally, the data packet header is selected from PDCP header, SDAP header and PDU headers of other protocol layers.

In order to solve the above technical problem, an embodiment of the present invention also discloses a synchronous transmission method. The synchronous transmission method includes: receiving data packets in one or more types of data streams; synchronously transmitting data packets in the same data block , packets belonging to the same data block have the same block sequence number

Optionally, the data packet is an uplink data packet, and the method further includes: sending the received data packet to the core network user plane network element or user equipment, and the block sequence number of the data packet is carried in the PDU headers of different protocol layers. middle.

Optionally, the synchronous transmission method further includes: delivering the data packet to an upper-layer protocol entity or an application-layer protocol entity according to the block sequence number.

Optionally, the synchronous transmission method further includes: if there is a data packet in the data block that needs to be transmitted as a whole and the data packet is not successfully received, discarding the received data packet.

Optionally, the synchronous transmission method further includes: if there is a data packet in the data block that needs to be transmitted as a whole within a preset time length and the data packet is not successfully received, discarding the received data packet.

Optionally, before the receiving data packets in one or more types of data streams, the method further includes: receiving indication information from a core network element, where the indication information is used to indicate whether the data block needs to be transmitted in its entirety.

Optionally, before receiving the data packets in one or more types of data streams, the method further includes: receiving block sequence number configuration information 2, where the block sequence number configuration information is used to indicate whether the received data packets contain block sequence numbers or not.

The embodiment of the present invention also discloses a synchronous transmission device. The synchronous transmission device includes: a data acquisition module for acquiring data packets to be transmitted in one or more types of data streams; a synchronous transmission module for converting the same data The data packets in the block are transmitted synchronously, and the data packets belonging to the same data block have the same block sequence number.

The embodiment of the present invention also discloses a synchronous transmission device. The synchronous transmission device includes: a data receiving module for receiving data packets in one or more types of data streams; a data block transmission module for transferring the same data block The data packets in the data block are transmitted synchronously, and the data packets belonging to the same data block have the same block sequence number.

The embodiment of the present invention also discloses a storage medium on which a computer program is stored, and the computer program executes the steps of the synchronous transmission method when the computer program is run by a processor.

An embodiment of the present invention further discloses a sending device, including a memory and a processor, the memory stores a computer program that can be run on the processor, and the processor executes the synchronization when the processor runs the computer program The steps of the transfer method.

An embodiment of the present invention further discloses a receiving device, including a memory and a processor, the memory stores a computer program that can be run on the processor, and the processor executes the synchronization when the processor runs the computer program The steps of the transfer method.

Compared with the prior art, the technical solutions of the embodiments of the present invention have the following beneficial effects:

In the technical scheme of the present invention, for data packets to be transmitted in various types of data streams, block sequence numbers can be generated for them, so that data packets with the same block sequence numbers can be transmitted synchronously; at the same time, the block sequence numbers are carried in the data packet header. , so that the receiving end can also determine the synchronously transmitted data packets through the block sequence number in the packet header for unified processing. The technical scheme of the present invention realizes the synchronous transmission of multi-modal services in the communication system.

Further, determine the first transmitted data packet and the last transmitted data packet in each data block; generate a block start transmission instruction for the first transmitted data packet, and carry it in the first transmitted data packet. In the data packet header of the data packet, a block end transmission indication is generated for the last transmitted data packet, and carried in the data packet header of the last transmitted data packet. In the technical solution of the present invention, by generating a block start transmission indication and a block end transmission indication in the data block, the receiver can specify the start and end of the data block transmission, avoid unnecessary waiting, and improve the efficiency of synchronous transmission.

Further, if there is a data packet in the data block that needs to be transmitted as a whole and the data packet is not successfully sent, then stop sending the data packet that is not successfully sent in the data block that needs to be transmitted as a whole; or, if there is a data packet in the data block that needs to be transmitted as a whole. If it is not received successfully, the received packet is discarded. The technical scheme of the present invention can realize the discarding operation of the data packets at the block level by terminating the sending of the data packets that are not successfully sent or discarding the received data packets when some data packets in the data block are not successfully sent or received. Improved transmission efficiency.

Further, block sequence number configuration information is received, where the block sequence number configuration information is used to indicate whether to generate a block sequence number. The technical scheme of the present invention instructs the sender to generate a block sequence number through the block sequence number configuration information, and enables the receiver to perform correct decoding according to the block sequence number configuration information, thereby further improving communication efficiency.

Description of drawings

1 is a flowchart of a method for synchronous transmission according to an embodiment of the present invention;

2 is a flowchart of another method for synchronous transmission according to an embodiment of the present invention;

3 is a schematic diagram of a specific application scenario of an embodiment of the present invention;

4 is a schematic diagram of another specific application scenario of an embodiment of the present invention;

5 is a schematic structural diagram of a synchronous transmission device according to an embodiment of the present invention;

FIG. 6 is a schematic structural diagram of another synchronous transmission apparatus according to an embodiment of the present invention.

Detailed ways

As described in the background art, in a variety of data streams that need to be transmitted synchronously, the data packet generation rate of each data stream is different, and how to perform synchronization is a problem that needs to be solved.

In the technical solution of the present invention, for the data packets to be transmitted in one or more types of data streams, a block sequence number can be generated for them, so that the data packets with the same block sequence number can be transmitted synchronously; at the same time, the block sequence number is carried in the In the data packet header, the receiving end can also determine the synchronously transmitted data packet through the block sequence number in the packet header for unified processing. The technical scheme of the present invention realizes the synchronous transmission of multi-modal services in the communication system.

The technical solution of the present invention can be applied to 5G (5Generation) communication systems, 4G and 3G communication systems, and various new communication systems in the future, such as 6G and 7G.

In order to make the above objects, features and advantages of the present invention more clearly understood, the specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

FIG. 1 is a flowchart of a synchronous transmission method according to an embodiment of the present invention.

The synchronous transmission method shown in FIG. 1 can be used for a sender, that is, a device that sends data packets. For example, it may be a user equipment (User Equipment, UE), a base station, a core network, and the like. The specific application scenarios of the synchronous transmission method may be uplink transmission, downlink transmission, or side link (SideLink, SL) transmission, etc., wherein, in the uplink transmission scenario, the transmitting end is the UE, the receiving end is the base station and the Core network; in the downlink transmission scenario, the sender is the core network, and the receiver is the base station and the UE; in the SL transmission scenario, the sender is the UE, and the receiver is also the UE. The user equipment includes but is not limited to terminal equipment such as mobile phones, computers, and tablet computers.

Specifically, the synchronous transmission method may include the following steps:

Step S101: Acquire data packets to be transmitted in one or more types of data streams;

Step S102 : synchronously transmit the data packets in the same data block, and the data packets belonging to the same data block have the same block sequence number.

It should be noted that the sequence numbers of the steps in this embodiment do not represent limitations on the execution order of the steps.

The one or more types of data flows referred to in the embodiments of the present invention may refer to data flows with different qualities of service (Quality of Service, QoS), and may also be referred to as QoS flows.

In the specific implementation of step S101, the sending end can obtain data packets to be transmitted in one or more types of data streams, and the multiple types of data streams may be Internet Protocol (IP) data streams, or is a non-IP data stream.

In a specific implementation, the sending end may generate a block sequence number for each data packet to be transmitted. Specifically, when acquiring the data packets to be transmitted, the transmitting end simultaneously acquires the value of the block sequence number of each data packet. For example, the block sequence number of each data packet is directly obtained, or the block sequence number of the data packet is determined according to the sampling rate, sampling time, sampling frequency of the data packet, or the service type to which the data packet belongs. The block sequence number of the data packet may be carried in the data packet header. The data transmission between the terminal and the base station is called air interface data transmission, and the data transmission between the base station and the network elements of the core network is called ground-side data transmission.

Specifically, when the transmitting end is the UE, the upper-layer application of the UE or the non-access stratum entity may generate the corresponding block sequence number (block sequence number) of the data packet, and notify the access stratum of the UE. The access layer protocol entity carries the block sequence number in the uplink data packet of the air interface. Specifically, it can be in the packet data convergence layer protocol (Packet Data Convergence Protocol, PDCP), service data adaptation protocol (Service Data Adaptation Protocol, SDAP) or The header of the protocol data unit (Protocol Data Unit, PDU) of other protocol layers carries the block sequence number corresponding to the data packet. Correspondingly, the receiving end is the base station and the core network.

The base station receives the uplink data packet from the UE, and the base station sends the received uplink data packet to the user plane network element of the core network, such as UPF (User Plane Function), and the data packet sent by the base station carries the block sequence number. Specifically, the base station may carry the block sequence number in the PDU header of the User Plane Protocol (User Plane Protocol, UPP) of the PDU session (Session). The user plane network element of the core network receives the data packet from the base station, and delivers it to the upper layer protocol entity or the application layer protocol entity according to the block sequence number.

Further, a possible implementation is: carrying the block sequence number in any one of the two transmission segments of air interface data transmission and ground side data transmission, or in the uplink data packet corresponding to the comprehensive transmission segment.

Specifically, when the sender is the core network, the user plane function (UPF) of the core network may receive the data packets of the application layer protocol entity or the upper layer protocol entity, and the application layer protocol entity or the upper layer protocol entity or the core The user plane network element of the network generates the block sequence number corresponding to the data packet. The block sequence number may be carried in the PDU header of the User Plane Protocol (User Plane Protocol, UPP) of the PDU session (Session). Correspondingly, the receiving end is the base station and the UE, the base station receives the data packet from the user plane network element of the core network, and the access layer protocol entity of the base station carries the corresponding block sequence number in the downlink data packet of the air interface. The block sequence number is carried in the PDU header of the , SDAP or other protocol layers. The UE receives the data packet from the base station and delivers it to the upper-layer protocol entity or the application-layer protocol entity according to the block sequence number.

Further, a possible implementation is as follows: the block sequence number is carried in any one of the two transmission segments of air interface data transmission, ground side data transmission, or a downlink data packet corresponding to the full transmission segment.

The data packets that need to be transmitted synchronously can be determined by the block sequence numbers of the data packets, that is, the data packets in the same data block need to be transmitted synchronously. Furthermore, in the specific implementation of step S102, when transmitting each data packet to be transmitted, the transmitting end performs synchronous transmission of the data packets in the same data block.

For example, packet 1, packet 2, packet 3, packet 4, packet 5, packet 6, packet 7, and packet 8 in QoS flow1 have block number x, while in QoSflow2, packet 12, packet 7, and packet 8 The block number of packet 13, packet 14, and packet 15 is also x. Then it means packet 1, packet 2, packet 3, packet 4, packet 5, packet 6, packet 7, packet 8 in QoS flow1 and packet 12, packet 13, packet in QoSflow2 14. The data packet 15 needs to be transmitted synchronously, that is, the above-mentioned data packets belong to the same data block.

The embodiments of the present invention can realize synchronous transmission of data streams with different QoS.

In a non-limiting embodiment of the present invention, step S102 shown in FIG. 1 may include the following steps: using transmission resources located within a preset time length to transmit data packets in the same data block.

In this embodiment, in order to achieve synchronization of data packet transmission, it is necessary to select transmission resources within a preset time length for transmission, that is, the sender transmits on transmission resources that are relatively close in time.

In a non-limiting embodiment of the present invention, after step S102 shown in FIG. 1, the following steps may be further included: determine the first transmitted data packet and the last transmitted data packet in each data block; A transmitted data packet generates a block start transmission indication and is carried in the data packet header of the first transmitted data packet, and a block end transmission indication is generated for the last transmitted data packet and is carried in the in the packet header of the last transmitted packet.

In this embodiment, in addition to generating the block sequence number, the sender may also carry a block transmission indication in the header of the data packet, indicating that the data packet is a data packet at the beginning of the data block to which it belongs. The sender may also include an end-of-block transmission indication in the header of the data packet, indicating that the data packet is a data packet at the end of the data block to which it belongs.

Further, the first transmitted data packet and the last transmitted data packet in various types of data streams are determined in each data block.

In this embodiment, the indication of the start of a block or the indication of the end of a block may be indicated according to a QoS flow, that is, the start or end of a block is indicated in a data packet of a single QoS flow.

In a non-limiting embodiment of the present invention, the synchronous transmission method may further include the following steps: if there is a data packet in the data block that needs to be transmitted as a whole and the data packet has not been sent successfully, terminating the transmission of the data block in the data block that needs to be transmitted as a whole. Packets that were not sent successfully.

Further, if there is a data packet that is not successfully sent in the data block that needs to be transmitted as a whole within a preset length of time, the sending of the data packet that is not successfully sent in the data block that needs to be transmitted as a whole is terminated.

Correspondingly, if there is a data packet in the data block that needs to be transmitted in its entirety and the data packet is not successfully received, the received data packet is discarded. Or, if there is a data packet in the data block that needs to be transmitted as a whole within a preset time length and the data packet is not successfully received, the received data packet is discarded.

In this embodiment, the preset time length may be configured by the network, or may be indicated by a QoS parameter. For example, the QoS parameter indicates that the transmission delay of the air interface is 20ms. If the sending is successful, the sending end considers that the sending fails; if the data packets in the data block are not received within 20ms, the receiving end considers that the data packets in the data block have failed to receive.

In a non-limiting embodiment of the present invention, before step S102 shown in FIG. 1 , the following step may be further included: receiving indication information from a core network element, where the indication information is used to indicate whether the data block needs to be transmitted in its entirety.

In this embodiment, both the sending end and the receiving end may receive the indication information of the core network element. The indication information may be carried in the QoS parameter information. Specifically, the QoS parameter information of the QoS flow indicated by the core network element includes an indication of whether the data packets in the same block need to be transmitted as a whole, that is, if some data packets in the data block are lost, whether the entire data block is lost. packets are discarded.

In a specific implementation, the core network element indicates the above-mentioned indication information to the base station, and the base station indicates the above-mentioned indication information to the terminal indicating whether the data packets in the same data block need to be transmitted as a whole. Alternatively, the core network element directly indicates the indication information to the terminal.

If the sending end or the receiving end is instructed that the data packets in the same data block need to be transmitted as a whole, the data packets are discarded according to the methods described in the above methods.

In a non-limiting embodiment of the present invention, the synchronous transmission method shown in FIG. 1 may further include the following steps: when reporting the buffer status report, carry the block transmission status indication information in the buffer status report and send it out, The block transmission status indication information is used to indicate whether there is a data packet to be transmitted in the data block that needs to be transmitted in its entirety in the buffer. Further, the block transmission status indication information further includes the block sequence number of the data block that needs to be transmitted in its entirety.

In this embodiment, for an uplink service, when a terminal reports a buffer status report (BSR), the BSR includes the block transmission status indication information of the data packet, and the block transmission status indication information of the data packet includes the buffered data. An indication of whether there are remaining packets to be sent in the data block that needs to be transmitted in its entirety. For example, if there are 10 data packets in a data block that needs to be transmitted as a whole, 4 data packets have been sent successfully, and there are 6 data packets in the buffer to be sent, the block transmission status indication information can be carried in the BSR to indicate that the whole data packet needs to be transmitted. The transmitted data block has packets that were not sent successfully. Further, it can also be represented by whether the buffer contains the start data packet of the block.

Further, the sender may also carry the block transmission status indication information corresponding to each logical channel or logical channel group in the buffer status report and send it out. Specifically, the block transmission state indication information of the data packet may indicate a buffered data packet corresponding to a logical channel or a logical channel group. Specifically, in the BSR reported by the terminal, the block transmission state indication information of the data packet may be reported according to a logical channel or a logical channel group. The base station may allocate and schedule Uu interface resources according to the block transmission state indication information of the data packets contained in the BSR.

In another specific scenario, in sidelink communication between terminals, the sender will report the BSR on the sidelink link, where the BSR includes the block transmission status indication information of the data packet. The base station can allocate and schedule resources on the sidelink link according to the block transmission state indication information of the data packet contained in the BSR.

In a non-limiting embodiment of the present invention, step S102 shown in FIG. 1 may include the following steps: the terminal receives block sequence number configuration information 1, where the block sequence number configuration information 1 is used to indicate whether to generate a block sequence number. Wherein, the block sequence number configuration information 1 is used to indicate whether a single DRB, a PDU session or a data packet in a data stream generates a block sequence number.

In a specific embodiment of the present invention, if the data packet to be transmitted is an uplink data packet, the block sequence number configuration information 1 is received through message 1; if the data packet to be transmitted is a sidelink data packet, it is received through downlink signaling The block serial number configuration information is one.

In a non-limiting embodiment of the present invention, the base station may also send block sequence number configuration information 2. In a specific embodiment of the present invention, if the data packet to be transmitted is a downlink data packet, the second block sequence number configuration information is sent through message 2.

Through the above embodiments, the sender and the receiver can know whether the block sequence number is carried in the data packet.

Specifically, for uplink data packets, the base station includes block sequence number configuration information 1 in message 1 sent to the UE; the block sequence number configuration information 1 refers to whether the data packet needs to carry the block sequence number, which can indicate a data packet in a DRB Whether the block sequence number needs to be carried, and it can also indicate whether the data packets in the PDU session or QoS flow need to carry the block sequence number. For example, if the base station indicates that a data packet in a certain DRB carries a block sequence number, the terminal carries the block sequence number in the data packet of the DRB.

For downlink services, the base station includes block sequence number configuration information 2 in message 2 sent to the UE; the block sequence number configuration information 2 refers to whether the data packet carries the block sequence number. It can indicate whether a data packet in a DRB needs to carry a block sequence number, and it can also indicate whether a data packet in a PDU session or a QoS flow needs to carry a block sequence number. For example, if the base station indicates that a data packet in a certain DRB carries a block sequence number, the terminal reads the block sequence number in the received data packet of the DRB.

It should be noted that in addition to message 1 and message 2, it can also be any other implementable message, including but not limited to RRC configuration information (RRCReconfiguration), RRC recovery message (RRCResume), RRC setup message (RRCSetup), etc. , which is not limited in this embodiment of the present invention.

For sidelink communication, the base station may indicate whether the sent data packet carries the block sequence number, and further, the sending end may indicate whether the data packet sent by the receiving end carries the block sequence number.

Please refer to FIG. 2. The synchronous transmission method shown in FIG. 2 can be used for a receiving end, that is, a device that receives data packets. For example, it may be a UE, a base station, a core network, and the like. Specifically, in the uplink transmission scenario, the sender is the UE, the receiver is the base station and the core network; in the downlink transmission scenario, the sender is the core network, and the receiver is the base station and the UE; in the SL transmission scenario, the sender is The UE and the receiving end are also UEs, which are not limited in this embodiment of the present invention.

Specifically, the synchronous transmission method may include the following steps:

Step S201: Receive data packets in one or more types of data streams;

Step S202: synchronously transmit the data packets in the same data block, and the data packets belonging to the same data block have the same block sequence number;

The sending end obtains the data packets to be transmitted in one or more types of data streams, the multiple data streams have different quality of service; generates a block sequence number for each data packet to be transmitted; The data packets of the same data block are transmitted synchronously, the data packets belonging to the same data block have the same block sequence number, and the block sequence number of each data packet is carried in the data packet header.

In a non-limiting embodiment, the data packet is an uplink data packet, the receiving end may send the received data packet to the core network user plane network element or user equipment, and the block sequence number of the data packet is carried in the PDU header.

In a non-limiting embodiment, the receiving end is the core network or the UE, and the receiving end may also deliver the data packet to the upper-layer protocol entity or the application-layer protocol entity according to the block sequence number.

In a specific application scenario of the present invention, the data packets to be transmitted are uplink data packets. The transmitting end is the UE, and the receiving end is the base station and the core network.

In step S31, the base station 32 sends a message 1 to the UE 33, and the message 1 includes the block sequence number configuration information one. The block sequence number configuration information one instructs the UE 33 to carry the block sequence number in the data packet.

In step S32, the upper layer application and/or non-access stratum entity of the UE33 generates the corresponding block sequence number of the data packet, and notifies the access stratum of the UE.

In step S33, the UE33 sends an uplink data packet, and the access layer protocol entity carries the block sequence number in the packet header of the uplink data packet of the air interface.

In step S34, for the data block 1, if the UE33 fails to send all the data packets in the data block 1 successfully within a preset time length, the UE33 stops sending the data packets that are not successfully sent in the data block 1. Other data blocks are sent successfully.

In step S35 , the base station 32 sends the successfully received uplink data packet to the core network 31 . The data packet sent by the base station 32 carries the block sequence number.

In step S36, for the data block 1, if the base station 32 fails to successfully receive all the data packets in the data block 1 within a preset time period, the base station 32 discards the successfully received data packets in the data block 1.

In step S37, the core network 31 delivers the received data packets to the upper-layer protocol entity or the application-layer protocol entity according to the block sequence number.

In another specific application scenario of the present invention, the data packets to be transmitted are downlink data packets. The transmitting end is the core network, and the receiving end is the base station and the UE.

In step S41, the upper-layer application and/or non-access stratum entity of the core network 41 generates the corresponding block sequence number of the data packet.

In step S42, the core network 41 sends a downlink data packet, and the header of the downlink data packet carries the block sequence number.

In step S43, for the data block 1, if the core network 41 fails to send all the data packets in the data block 1 successfully within a preset time period, the core network 41 stops sending the unsuccessfully sent data packets in the data block 1. Other data blocks are sent successfully.

In step S44, the base station 42 sends the successfully received uplink data packet to the UE43. The data packet sent by the base station 42 carries the block sequence number.

In step S45, for the data block 1, if the base station 42 fails to receive all the data packets in the data block 1 successfully within a preset time length, the base station 42 discards the successfully received data packets in the data block 1.

In step S46, the UE43 delivers the received data packet to the upper-layer protocol entity or the application-layer protocol entity according to the block sequence number.

In a specific application scenario of the present invention, the data packet to be transmitted may be a sidelink data packet, the transmitting end is the UE, and the receiving end is also the UE.

In this case, the block sequence number configuration information may be sent by the base station to the transmitter and the receiver. For the interaction process between the transmitting end and the receiving end, reference may be made to the interaction process between the UE and the base station in FIG. 3 , which will not be repeated here.

Referring to FIG. 5 , an embodiment of the present invention further discloses a synchronous transmission device 50 . The synchronous transmission device 50 may include:

A data acquisition module 501, configured to acquire data packets to be transmitted in one or more types of data streams, the multiple data streams having different quality of service;

The synchronous transmission module 502 is configured to synchronously transmit the data packets in the same data block, and the data packets belonging to the same data block have the same block sequence number.

Referring to FIG. 6 , an embodiment of the present invention further discloses a synchronous transmission device 60 . The synchronous transmission device 60 may include:

A data receiving module 601, configured to receive data packets in one or more types of data streams;

The data block transmission module 602 is configured to synchronously transmit the data packets in the same data block, and the data packets belonging to the same data block have the same block sequence number.

For more information on the working principles and working modes of the synchronous transmission device 50 and the synchronous transmission device 60, reference may be made to the relevant descriptions in FIG. 1 to FIG. 2, and details are not repeated here.

The synchronous transmission device 50 and the synchronous transmission device 60 (virtual device) may be, for example, a chip, a chip module, or the like.

Regarding each module/unit included in each device and product described in the above embodiments, it may be a software module/unit, a hardware module/unit, or a part of a software module/unit and a part of a hardware module/unit . For example, for each device or product applied to or integrated in a chip, each module/unit included therein may be implemented by hardware such as circuits, or at least some modules/units may be implemented by a software program. Running on the processor integrated inside the chip, the remaining (if any) part of the modules/units can be implemented by hardware such as circuits; for each device and product applied to or integrated in the chip module, the modules/units contained therein can be They are all implemented by hardware such as circuits, and different modules/units can be located in the same component (such as a chip, circuit module, etc.) or in different components of the chip module, or at least some modules/units can be implemented by software programs. The software program runs on the processor integrated inside the chip module, and the remaining (if any) part of the modules/units can be implemented by hardware such as circuits; for each device and product applied to or integrated in the terminal, each module contained in it The units/units may all be implemented in hardware such as circuits, and different modules/units may be located in the same component (eg, chip, circuit module, etc.) or in different components in the terminal, or at least some of the modules/units may be implemented in the form of software programs Realization, the software program runs on the processor integrated inside the terminal, and the remaining (if any) part of the modules/units can be implemented in hardware such as circuits.

An embodiment of the present invention further discloses a storage medium, which is a computer-readable storage medium, and stores a computer program thereon. When the computer program runs, the synchronous transmission method shown in FIG. 1 or FIG. 2 can be executed. A step of. The storage medium may include ROM, RAM, magnetic or optical disks, and the like. The storage medium may also include a non-volatile memory (non-volatile) or a non-transitory (non-transitory) memory and the like.

An embodiment of the present invention further discloses a sending device, where the sending device may include a memory and a processor, and the memory stores a computer program that can run on the processor. When the processor runs the computer program, the steps of the synchronous transmission method shown in FIG. 1 may be executed.

An embodiment of the present invention further discloses a receiving device, where the receiving device may include a memory and a processor, and the memory stores a computer program that can run on the processor. When the processor runs the computer program, the steps of the synchronous transmission method shown in FIG. 2 can be executed.

The technical solution of the present invention is also applicable to different network architectures, including but not limited to relay network architecture, dual link architecture, Vehicle-to-Everything (vehicle-to-anything communication) architecture and other architectures.

The core network described in the embodiments of the present application may be an evolved packet core (evolved packet core, EPC for short), a 5G Core Network (5G core network), and may also be a new type of core network in a future communication system. The 5G CoreNetwork is composed of a set of devices, and implements the Access and Mobility Management Function (AMF) for functions such as mobility management, and the user plane that provides functions such as packet routing and forwarding and QoS (Quality of Service) management. Function (User Plane Function, UPF), session management function (Session Management Function, SMF) that provides functions such as session management, IP address allocation and management, etc. EPC consists of MME that provides functions such as mobility management and gateway selection, Serving Gateway (S-GW) that provides functions such as packet forwarding, and PDN Gateway (P-GW) that provides functions such as terminal address allocation and rate control.

A base station (base station, BS for short) in this embodiment of the present application, which may also be referred to as base station equipment, is a device deployed in a radio access network (RAN) to provide a wireless communication function. For example, devices that provide base station functions in 2G networks include base transceiver stations (English: base transceiver station, referred to as BTS), devices that provide base station functions in 3G networks include NodeBs (NodeBs), and devices that provide base station functions in 4G networks. Including evolved Node B (evolved NodeB, eNB), in wireless local area networks (wireless local area networks, referred to as WLAN), the device that provides base station functions is an access point (access point, referred to as AP), 5G New Radio (New Radio, Referred to as NR), the equipment gNB that provides base station functions, and the continuously evolved Node B (ng-eNB), wherein the gNB and the terminal use NR technology for communication, and the ng-eNB and the terminal use E-UTRA (Evolved Universal Terrestrial Radio Access) technology to communicate, both gNB and ng-eNB can be connected to the 5G core network. The base station in the embodiment of the present application also includes a device that provides a base station function in a new communication system in the future, and the like.

The base station controller in the embodiments of the present application is a device for managing base stations, such as a base station controller (BSC for short) in a 2G network and a radio network controller (RNC for short) in a 3G network , It can also refer to the device that controls and manages the base station in the new communication system in the future.

The network side network in the embodiment of the present invention refers to a communication network that provides communication services for terminals, including a base station of a wireless access network, a base station controller of a wireless access network, and a device on the core network side.

The terminal in the embodiments of this application may refer to various forms of user equipment (user equipment, UE for short), access terminal, subscriber unit, subscriber station, mobile station, mobile station (mobile station, built as MS), remote station, remote station A terminal, mobile device, user terminal, terminal equipment, wireless communication device, user agent or user equipment. The terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a Wireless communication-capable handheld devices, computing devices, or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in future 5G networks or future evolved Public Land Mobile Networks (PLMN for short) ), which is not limited in this embodiment of the present application.

The embodiment of the present application defines the unidirectional communication link from the access network to the terminal as the downlink, the data transmitted on the downlink is the downlink data, and the transmission direction of the downlink data is called the downlink direction; The unidirectional communication link is the uplink, the data transmitted on the uplink is the uplink data, and the transmission direction of the uplink data is called the uplink direction.

It should be understood that the term "and/or" in this document is only an association relationship to describe associated objects, indicating that there can be three kinds of relationships, for example, A and/or B, which can mean that A exists alone, and A and B exist at the same time , there are three cases of B alone. In addition, the character "/" in this text indicates that the related objects before and after are an "or" relationship.

The "plurality" in the embodiments of the present application refers to two or more.

The descriptions of the first, second, etc. appearing in the embodiments of the present application are only used for illustration and distinguishing the description objects, and have no order. any limitations of the examples.

The "connection" in the embodiments of the present application refers to various connection modes such as direct connection or indirect connection, so as to realize communication between devices, which is not limited in the embodiments of the present application.

It should be understood that in the embodiment of the present application, the processor may be a central processing unit (central processing unit, CPU for short), and the processor may also be other general-purpose processors, digital signal processors (digital signal processors, DSP for short), special-purpose processors An integrated circuit (application specific integrated circuit, ASIC for short), an off-the-shelf programmable gate array (field programmable gate array, FPGA for short) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It should also be understood that the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory may be a read-only memory (ROM for short), a programmable read-only memory (PROM for short), an erasable PROM for short (EPROM) , Electrically Erasable Programmable Read-Only Memory (electrically EPROM, EEPROM for short) or flash memory. The volatile memory may be random access memory (RAM for short), which is used as an external cache memory. By way of example and not limitation, many forms of random access memory (RAM) are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic Random access memory (synchronous DRAM, referred to as SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, referred to as DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, referred to as ESDRAM), synchronous connection Dynamic random access memory (synchlink DRAM, referred to as SLDRAM) and direct memory bus random access memory (direct rambus RAM, referred to as DR RAM).

The above embodiments may be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented in software, the above-described embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or 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, special purpose computer, computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission by wire or wireless to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, or the like that contains one or more sets of available media. The usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media. The semiconductor medium may be a solid state drive.

It should be understood that, in various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.

In the several embodiments provided in this application, it should be understood that the disclosed method, apparatus and system may be implemented in other manners. For example, the device embodiments described above are only illustrative; for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation; for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may be physically included individually, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware, or may be implemented in the form of hardware plus software functional units.

The above-mentioned integrated units implemented in the form of software functional units can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium, and includes several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute some steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, Read-Only Memory (ROM for short), Random Access Memory (RAM for short), magnetic disk or CD, etc. that can store program codes medium.

Although the present invention is disclosed above, the present invention is not limited thereto. Any person skilled in the art can make various changes and modifications without departing from the spirit and scope of the present invention. Therefore, the protection scope of the present invention should be based on the scope defined by the claims.

Claims (29)

1. a synchronous transmission method, is characterized in that, comprises: Get data packets to be transmitted in one or more types of data streams; The data packets in the same data block are transmitted synchronously, and the data packets belonging to the same data block have the same block sequence number. 2 . The synchronous transmission method according to claim 1 , wherein a block sequence number is carried in the packet header of the data packet of the synchronous transmission. 3 . 3. The synchronous transmission method according to claim 1, wherein the synchronous transmission of the data packets in the same data block comprises: Data packets in the same data block are transmitted using transmission resources located within a preset time length. 4. The synchronous transmission method according to claim 1, wherein before the synchronous transmission of the data packets in the same data block, the method further comprises: Determine the first transmitted data packet and the last transmitted data packet in each data block; generating a block start transmission indication for the first transmitted data packet and carrying it in the packet header of the first transmitted data packet, and generating a block end transmission indication for the last transmitted data packet, and It is carried in the data packet header of the last transmitted data packet. 5. The synchronous transmission method according to claim 4, wherein the determining of the first transmitted data packet and the last transmitted data packet in each data block comprises: The first and last transmitted data packets in each type of data stream are determined in each data block. 6. The synchronous transmission method according to claim 1, further comprising: If there is a data packet in the data block that needs to be transmitted in its entirety that has not been successfully sent, the sending of the data packet that has not been successfully transmitted in the data block that needs to be transmitted in its entirety is terminated. 7. The synchronous transmission method according to claim 1, further comprising: If there are data packets that are not successfully sent in the data blocks that require overall transmission within a preset time length, the sending of the data packets that are not successfully sent in the data blocks that require overall transmission is terminated. 8. The synchronous transmission method according to claim 1, wherein before the synchronous transmission of the data packets in the same data block, the method further comprises: Receive indication information from the core network element, where the indication information is used to indicate whether the data block needs to be transmitted in its entirety. 9. The synchronous transmission method according to claim 1, wherein the reported buffer status report includes block transmission status indication information, and the block transmission status indication information is used to indicate whether there is data in the buffer that needs to be transmitted as a whole The packets in the block to be transmitted. 10 . The synchronous transmission method according to claim 9 , wherein the block transmission status indication information further includes the block sequence number of the data block that needs to be transmitted as a whole. 11 . The synchronous transmission method according to claim 9, wherein the buffer status report includes the block transmission status indication information corresponding to each logical channel or logical channel group. 12. The synchronous transmission method according to claim 1, wherein before the synchronous transmission of the data packets in the same data block, the method further comprises: A block sequence number configuration information 1 is received, and the block sequence number configuration information 1 is used to indicate whether to generate a block sequence number. 13 . The synchronous transmission method according to claim 12 , wherein the block sequence number configuration information 1 is used to indicate whether a single DRB, a PDU session or a data packet in a data stream generates a block sequence number. 14 . 14. The synchronous transmission method according to claim 12, wherein the receiving block sequence number configuration information 1 comprises: If the data packet to be transmitted is an uplink data packet, receive the block sequence number configuration information 1 through message 1; If the data packet to be transmitted is a sidelink data packet, the block sequence number configuration information one is received through downlink signaling. 15. The synchronous transmission method according to claim 1, wherein before the synchronous transmission of the data packets in the same data block, the method further comprises: The second block sequence number configuration information is sent, where the block sequence number configuration information is used to indicate whether the received data packet contains the block sequence number. 16. The synchronous transmission method according to claim 15, wherein the sending block sequence number configuration information 2 comprises: If the data packet to be transmitted is a downlink data packet, the block sequence number configuration information 2 is sent through message 2. 17. The synchronous transmission method according to claim 2, wherein the data packet header is selected from PDCP header, SDAP header and PDU headers of other protocol layers. 18. A method for synchronous transmission, comprising: receive packets in one or more types of data streams; The data packets in the same data block are transmitted synchronously, and the data packets belonging to the same data block have the same block sequence number. 19. The synchronous transmission method according to claim 18, wherein the data packet is an uplink data packet, and the method further comprises: The received data packet is sent to the core network user plane network element or user equipment, and the block sequence number of the data packet is carried in the PDU headers of different protocol layers. 20. The synchronous transmission method according to claim 18, further comprising: The data packets are delivered to the upper-layer protocol entity or the application-layer protocol entity according to the block sequence number. 21. The synchronous transmission method according to claim 18, further comprising: If there are data packets in the data blocks that need to be transmitted as a whole, the received data packets are discarded. 22. The synchronous transmission method according to claim 18, further comprising: If there is a data packet in the data block that needs to be transmitted as a whole within a preset time length and the data packet is not successfully received, the received data packet is discarded. 23. The method for synchronous transmission according to claim 18, wherein before the receiving the data packets in one or more types of data streams, the method further comprises: Receive indication information from the core network element, where the indication information is used to indicate whether the data block needs to be transmitted in its entirety. 24. The method for synchronous transmission according to claim 18, characterized in that before said receiving the data packets in one or more types of data streams, the method further comprises: The second block sequence number configuration information is received, where the block sequence number configuration information is used to indicate whether the received data packet contains a block sequence number or not. 25. A synchronous transmission device, characterized in that it comprises: A data acquisition module for acquiring data packets to be transmitted in one or more types of data streams; The synchronous transmission module is used to synchronously transmit the data packets in the same data block, and the data packets belonging to the same data block have the same block sequence number. 26. A synchronous transmission device, characterized in that, comprising: A data receiving module for receiving data packets in one or more types of data streams; The data block transmission module is used for synchronous transmission of data packets in the same data block, and the data packets belonging to the same data block have the same block sequence number. 27. A storage medium on which a computer program is stored, characterized in that, when the computer program is run by a processor, the steps of the synchronous transmission method according to any one of claims 1 to 24 are executed. 28. A sending device, comprising a memory and a processor, wherein a computer program that can be run on the processor is stored on the memory, wherein the processor executes claims 1 to 1 when the processor runs the computer program. Steps of the synchronous transmission method described in any one of 17. 29. A receiving device, comprising a memory and a processor, wherein the memory stores a computer program that can run on the processor, wherein the processor executes claims 18 to 18 when the processor runs the computer program. Steps of the synchronous transmission method described in any one of 24.

Images