CN114793357A - Synchronous transmission method and device, storage medium, sending end equipment and receiving end equipment - Google Patents
Synchronous transmission method and device, storage medium, sending end equipment and receiving end equipment Download PDFInfo
- Publication number
- CN114793357A CN114793357A CN202110106473.XA CN202110106473A CN114793357A CN 114793357 A CN114793357 A CN 114793357A CN 202110106473 A CN202110106473 A CN 202110106473A CN 114793357 A CN114793357 A CN 114793357A
- Authority
- CN
- China
- Prior art keywords
- data
- block
- data packet
- transmitted
- sequence number
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 230000005540 biological transmission Effects 0.000 title claims abstract description 176
- 230000001360 synchronised effect Effects 0.000 title claims abstract description 96
- 238000000034 method Methods 0.000 title claims abstract description 78
- 238000004590 computer program Methods 0.000 claims description 22
- 230000011664 signaling Effects 0.000 claims description 3
- 102100022734 Acyl carrier protein, mitochondrial Human genes 0.000 claims 1
- 101000678845 Homo sapiens Acyl carrier protein, mitochondrial Proteins 0.000 claims 1
- 238000004891 communication Methods 0.000 abstract description 26
- 230000006870 function Effects 0.000 description 21
- 238000007726 management method Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000005070 sampling Methods 0.000 description 3
- 230000002452 interceptive effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 230000001052 transient effect Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 230000005484 gravity Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008447 perception Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W56/00—Synchronisation arrangements
- H04W56/001—Synchronization between nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0205—Traffic management, e.g. flow control or congestion control at the air interface
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
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
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a synchronous transmission method and apparatus, a storage medium, a sending end device, and a receiving end device.
Background
There are many different Quality of Service (QoS) flows (flows) for multimodal services.
Multiple data streams are contained in the same service, wherein the multiple data streams have different QoS requirements, for example, the data streams may be Video, such as Video/Audio media (Video/Audio media); data acquired by the sensors, such as brightness (brightness), temperature (temperature), humidity (humidity); tactile data such as pressure, texture, vibration, temperature, gravity, pull force, position perception, etc. Multiple data streams belonging to the same service need to be synchronously transmitted to a receiving end of the data streams and processed by the receiving end.
However, in many data streams requiring synchronous transmission, the generation rate of data packets of each data stream is different, and how to perform synchronization is a problem to be solved.
Disclosure of Invention
The technical problem solved by the invention is how to realize the synchronous transmission of the multi-mode service in the communication system so as to meet the service requirement of a user.
In order to solve the foregoing technical problem, an embodiment of the present invention provides a synchronous transmission method, where the synchronous transmission method includes: 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.
Optionally, the packet header of the data packet transmitted synchronously carries the block sequence number.
Optionally, the performing synchronous transmission on the data packets in the same data block includes: and transmitting the data packets in the same data block by using the transmission resources within the preset time length.
Optionally, before performing synchronous transmission on the data packets in the same data block, the method further includes: determining a first transmitted data packet and a last transmitted data packet in each data block; generating a block start transmission indication for the first transmitted data packet and carrying the block start transmission indication in the data packet header of the first transmitted data packet, and generating a block end transmission indication for the last transmitted data packet and carrying the block end transmission indication in the data packet header of the last transmitted data packet.
Optionally, the determining a first transmitted data packet and a last transmitted data packet in each data block includes: the first transmitted data packet and the last transmitted data packet in the various types of data streams are determined in each data block.
Optionally, the synchronous transmission method further includes: and if the data packets which are not successfully transmitted exist in the data blocks which need to be integrally transmitted, terminating the transmission of the data packets which are not successfully transmitted in the data blocks which need to be integrally transmitted.
Optionally, the synchronous transmission method further includes: and if the data packets in the data blocks needing to be integrally transmitted exist in the preset time span and are not successfully transmitted, terminating the transmission of the data packets which are not successfully transmitted in the data blocks needing to be integrally transmitted.
Optionally, before performing synchronous transmission on the data packets in the same data block, the method further includes: and receiving indication information from a core network element, wherein the indication information is used for indicating whether the data block needs to be transmitted in a whole manner.
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 integrally in the buffer.
Optionally, the block transmission status indication information further includes a 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 performing synchronous transmission on the data packets in the same data block, the method further includes: and receiving first block sequence number configuration information, wherein the first block sequence number configuration information is used for indicating whether a block sequence number is generated or not.
Optionally, the block sequence number configuration information 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 first configuration information of the received block sequence number includes: if the data packet to be transmitted is an uplink data packet, receiving the block sequence number configuration information I through a message 1; and if the data packet to be transmitted is a sidelink data packet, receiving the block sequence number configuration information I through a downlink signaling.
Optionally, before performing synchronous transmission on the data packets in the same data block, the method further includes: and receiving block sequence number configuration information II, wherein the block sequence number configuration information is used for indicating whether the received data packet contains a block sequence number.
Optionally, the second sending block sequence number configuration information includes: and if the data packet to be transmitted is a downlink data packet, sending the block sequence number configuration information II through a message 2.
Optionally, the data packet header is selected from a PDCP header, an SDAP header, and a PDU header of another protocol layer.
In order to solve the above technical problem, an embodiment of the present invention further discloses a synchronous transmission method, where the synchronous transmission method includes: receiving data packets in one or more types of data streams; 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
Optionally, the data packet is an uplink data packet, and the method further includes: and sending the received data packet to a core network user plane network element or user equipment, wherein the block sequence number of the data packet is carried in PDU heads of different protocol layers.
Optionally, the synchronous transmission method further includes: and 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: and if the data packet which needs to be transmitted in the whole is not successfully received, the received data packet is discarded.
Optionally, the synchronous transmission method further includes: and if the data block to be integrally transmitted has data packet non-reception success in the preset time length, discarding the received data packet.
Optionally, before receiving the data packets in the one or more types of data streams, the method further includes: and receiving indication information from a network element of a core network, wherein the indication information is used for indicating whether the data block needs to be transmitted integrally.
Optionally, before receiving the data packets in the one or more types of data streams, the method further includes: and receiving second block sequence number configuration information, wherein the second block sequence number configuration information is used for indicating whether the received data packet contains a block sequence number or not.
The embodiment of the invention also discloses a synchronous transmission device, which comprises: the data acquisition module is used for acquiring data packets to be transmitted in one or more types of data streams; and the synchronous transmission module is used for synchronously transmitting 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 embodiment of the invention also discloses a synchronous transmission device, which comprises: the data receiving module is used for receiving data packets in one or more types of data streams; and the data block transmission module is used for synchronously transmitting 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 embodiment of the invention also discloses a storage medium, wherein a computer program is stored on the storage medium, and the computer program executes the steps of the synchronous transmission method when being executed by a processor.
The embodiment of the invention also discloses a sending device, which comprises a memory and a processor, wherein the memory is stored with a computer program capable of running on the processor, and the processor executes the steps of the synchronous transmission method when running the computer program.
The embodiment of the invention also discloses a receiving device, which comprises a memory and a processor, wherein the memory is stored with a computer program capable of running on the processor, and the processor executes the steps of the synchronous transmission method when running the computer program.
Compared with the prior art, the technical scheme of the embodiment of the invention has the following beneficial effects:
in the technical scheme of the invention, the data packets to be transmitted in various types of data streams can be synchronously transmitted by generating the block sequence numbers for the data packets to be transmitted, so that the data packets with the same block sequence numbers can be synchronously transmitted; meanwhile, the block sequence number is carried in the data packet header, so that a receiving end can also determine the synchronously transmitted data packet through the block sequence number in the packet header so as to carry out unified processing. The technical scheme of the invention realizes the synchronous transmission of the multi-mode service in the communication system.
Further, determining a first transmitted data packet and a last transmitted data packet in each data block; generating a block start transmission indication for the first transmitted data packet and carried in the data packet header of the first transmitted data packet, and generating a block end transmission indication for the last transmitted data packet and carried in the data packet header of the last transmitted data packet. In the technical scheme of the invention, the start transmission instruction and the end transmission instruction of the block are generated in the data block, so that a receiving party can clearly determine the start and the end of the data block transmission, unnecessary waiting is avoided, and the efficiency of synchronous transmission is improved.
Further, if the data block needing to be transmitted integrally has data packet unsuccessfully sent, stopping sending the data packet unsuccessfully sent in the data block needing to be transmitted integrally; or if the data block needing to be transmitted in the whole mode has data packet non-reception success, discarding the received data packet. According to the technical scheme, under the condition that part of data packets in the data block are not successfully transmitted or successfully received, the data packets which are not successfully transmitted are stopped being transmitted or the received data packets are discarded, the discarding operation of the data packets at the block level can be achieved, and the transmission efficiency is further improved.
Further, receiving block sequence number configuration information, where the block sequence number configuration information is used to indicate whether to generate a block sequence number. According to the technical scheme, the sending end is instructed to generate the block serial number through the block serial number configuration information, and the receiving end is enabled to carry out correct decoding according to the block serial number configuration information, so that the communication efficiency is further improved.
Drawings
Fig. 1 is a flowchart of a synchronous transmission method according to an embodiment of the present invention;
FIG. 2 is a flow chart of another method of synchronous transmission according to an embodiment of the present invention;
FIG. 3 is a diagram illustrating an exemplary application scenario according to an embodiment of the present invention;
FIG. 4 is a diagram illustrating another exemplary application scenario of the present invention;
fig. 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 device according to an embodiment of the present invention.
Detailed Description
As described in the background, in a plurality of data streams requiring synchronous transmission, the generation rate of data packets of each data stream is different, and how to perform synchronization is a problem to be solved.
In the technical scheme of the invention, for the data packets to be transmitted in one or more types of data streams, the block sequence numbers can be generated for the data packets, so that the data packets with the same block sequence numbers can be synchronously transmitted; meanwhile, the block sequence number is carried in the data packet header, so that a receiving end can also determine the synchronously transmitted data packet through the block sequence number in the packet header so as to carry out unified processing. The technical scheme of the invention realizes the synchronous transmission of the multi-mode service in the communication system.
The technical scheme of the invention can be applied to a 5G (5Generation) communication system, a 4G communication system, a 3G communication system and various future new communication systems, such as 6G, 7G and the like.
In order to make the aforementioned objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in detail below.
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 may be used for a transmitting end, that is, a device that transmits a data packet. For example, the UE may be a User Equipment (UE), a base station, a core network, and the like. The specific application scenario of the synchronous transmission method may be uplink transmission, downlink transmission, or Side Link (SL) transmission, where in the uplink transmission scenario, the sending end is a UE, and the receiving end is a base station and a core network; in a downlink transmission scene, a sending end is a core network, and a receiving end is a base station and UE; in an SL transmission scenario, the transmitting end is a UE, and the receiving end is also a UE. The user equipment includes but is not limited to a mobile phone, a computer, a tablet computer and other terminal equipment.
Specifically, the synchronous transmission method may include the steps of:
step S101: acquiring a data packet to be transmitted in one or more types of data streams;
step S102: 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.
It should be noted that, the sequence numbers of the steps in this embodiment do not represent a limitation 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 Quality of Service (QoS), and may also be referred to as QoS flow.
In the specific implementation of step S101, the sending end can obtain a data packet to be transmitted in one or more types of data streams, where the multiple types of data streams may be Internet Protocol (IP) data streams or non-IP data streams.
In specific implementation, the sending end may generate a block sequence number for each data packet to be transmitted. Specifically, when acquiring a data packet to be transmitted, the transmitting end 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 a data packet is determined according to the sampling rate, the sampling time, the sampling frequency, 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. Data transmission between a terminal and a base station is called air interface data transmission, and data transmission between the base station and a network element of a core network is called ground side data transmission.
Specifically, when the sending end is the UE, the corresponding block sequence number (block sequence number) of the data packet may be generated by an upper layer application of the UE and/or a non-access layer entity, and the access layer of the UE is notified. The access layer Protocol entity carries the block sequence number in an uplink Data Packet of an air interface, and specifically, may carry the block sequence number corresponding to the Data Packet in a Packet Data Convergence Protocol (PDCP), a Service Data Adaptation Protocol (SDAP), or a Protocol Data Unit (PDU) header of another Protocol layer. Correspondingly, the receiving end is a base station and a core network.
The base station receives an uplink data packet from the UE, and sends the received uplink data packet to a user Plane network element of a core network, such as a upf (user Plane function), where the data packet sent by the base station carries a block sequence number. Specifically, the base station may carry a block sequence number in a PDU header of a User Plane Protocol (UPP) of a PDU Session (Session). And the user plane network element of the core network receives the data packet from the base station and delivers the data packet to an upper layer protocol entity or an application layer protocol entity according to the block sequence number.
Further, a possible implementation manner is that the block sequence number is carried in an uplink data packet corresponding to any one of two transmission segments of air interface data transmission and ground side data transmission or a complete transmission segment.
Specifically, when the sending end is a core network, a User Plane network element (UPF) of the core network may receive a data packet of an application layer protocol entity or an upper layer protocol entity, and a block sequence number corresponding to the data packet is generated by the application layer protocol entity or the upper layer protocol entity or the User Plane network element of the core network. The block sequence number may be carried in a PDU header of a User Plane Protocol (UPP) of a PDU Session (Session). Correspondingly, the receiving end is a base station and a UE, the base station receives a data packet from a core network user plane network element, and an access layer protocol entity of the base station carries a corresponding block sequence number in a downlink data packet of an air interface, specifically, the block sequence number may be carried in a PDU header of a PDCP, an SDAP or other protocol layer. And the UE receives the data packet from the base station and delivers the data packet to an upper layer protocol entity or an application layer protocol entity according to the block sequence number.
Further, one possible implementation is: and carrying the block sequence number in a downlink data packet corresponding to any one of the two transmission sections of air interface data transmission and ground side data transmission or a comprehensive transmission section.
The data packets that need to be synchronously transmitted can be determined through the block sequence numbers of the data packets, that is, the data packets in the same data block need to be synchronously transmitted. Further, in the specific implementation of step S102, when the sending end transmits each data packet to be transmitted, the sending end performs synchronous transmission on the data packets in the same data block.
For example, the block numbers of data packet 1, data packet 2, data packet 3, data packet 4, data packet 5, data packet 6, data packet 7, and data packet 8 in QoS flow1 are x, and the block numbers of data packet 12, data packet 13, data packet 14, and data packet 15 in QoS flow2 are also x. It means that the data packets 1, 2, 3, 4, 5, 6, 7, 8 and QoSflow2 in QoS flow1 need synchronous transmission, i.e. the data packets belong to the same data block.
The embodiment of the invention can realize synchronous transmission of the data streams with different QoS.
In one non-limiting embodiment of the present invention, step S102 shown in fig. 1 may include the following steps: and transmitting the data packets in the same data block by using the transmission resources within the preset time length.
In this embodiment, in order to implement synchronization of data packet transmission, a transmission resource within a preset time length needs to be selected for transmission, that is, a sending end sends on a transmission resource relatively close in time.
In a non-limiting embodiment of the present invention, step S102 shown in fig. 1 may further include the following steps: determining a first transmitted data packet and a last transmitted data packet in each data block; generating a block start transmission indication for the first transmitted data packet and carried in the data packet header of the first transmitted data packet, and generating a block end transmission indication for the last transmitted data packet and carried in the data packet header of the last transmitted data packet.
In this embodiment, in addition to generating the block sequence number, the sending end may also carry a block transmission start indication in the header of the data packet, which indicates that the data packet is a data packet at which the data block belongs to start. The sending end may further include an end-of-block transmission indication in the header of the data packet, indicating that the data packet is a data packet of the end of the data block to which the data packet belongs.
Further, the first transmitted packet and the last transmitted packet in the various types of data streams are determined in each data block.
In this embodiment, the indication of the start of the block or the indication of the end of the block may be indicated in terms of QoS flow, i.e. the start or end of the block is indicated in a single QoS flow packet.
In one non-limiting embodiment of the present invention, the synchronous transmission method may further include the steps of: and if the data packets in the data blocks needing to be integrally transmitted exist in the data blocks which are not successfully transmitted, terminating the transmission of the data packets which are not successfully transmitted in the data blocks needing to be integrally transmitted.
Further, if the data packets in the data blocks needing to be transmitted in the whole manner are not successfully transmitted within the preset time span, the data packets which are not successfully transmitted in the data blocks needing to be transmitted in the whole manner are stopped from being transmitted.
Accordingly, if there is a packet non-reception success in the data block requiring the entire transmission, the received packet is discarded. Or if the data block needing to be transmitted in the whole within the preset time length has data packet non-reception success, discarding the received data packet.
In this embodiment, the preset time length may be configured by a network, or may be indicated by a QoS parameter, for example, the QoS parameter indicates that the transmission delay of an air interface is 20ms, and if a data packet in a data block is not successfully transmitted within 20ms, the transmitting end considers that transmission is failed; if the data packet in the data block is not received within 20ms, the receiving end considers that the data packet of the data block is received unsuccessfully.
In a non-limiting embodiment of the present invention, the following steps may be further included before step S102 shown in fig. 1: and receiving indication information from a core network element, wherein the indication information is used for indicating whether the data block needs to be transmitted in a whole manner.
In this embodiment, both the sending end and the receiving end may receive the indication information of the network element of the core network. The indication information may be carried in the QoS parameter information. Specifically, the QoS parameter information of the QoS flow indicated by the network element of the core network includes an indication of whether the data packets in the same block need to be transmitted in the whole block, that is, an indication of whether the data packets of the entire data block need to be discarded if some data packets in the data block are lost.
In a specific implementation, the core network element indicates the indication information to the base station, and the base station indicates the indication information to the terminal to indicate whether the data packets in the same data block need to be transmitted integrally. Or, the core network element directly indicates the indication information to the terminal.
And if the sending end or the receiving end is indicated to indicate that the data packets in the same data block need to be transmitted integrally, discarding the data packets according to the description mode in the mode.
In a non-limiting embodiment of the present invention, the synchronous transmission method shown in fig. 1 may further include the following steps: when a buffer status report is reported, carrying block transmission status indication information in the buffer status report and sending the block transmission status indication information, wherein the block transmission status indication information is used for indicating whether a data packet to be transmitted in a data block which needs to be integrally transmitted exists in a buffer. Further, the block transmission status indication information further includes a 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 Reporting (BSR), block transmission Status indication information of a data packet is included in the BSR, where the block transmission Status indication information of the data packet includes an indication of whether there is a remaining data packet to be transmitted in a data block that needs to be transmitted in an entire manner in the buffered data packet. For example, if there are 4 data packets successfully transmitted and there are 6 data packets to be transmitted in the buffer in a total of 10 data packets in a data block that needs to be integrally transmitted, block transmission status indication information may be carried in the BSR to indicate that there are data packets that are not successfully transmitted in the data block that needs to be integrally transmitted. Further, it can be indicated by whether the starting data packet of the block is contained in the cache.
Further, the sending end 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 the block transmission status indication information. Specifically, the block transmission status indication information of the data packet may indicate a buffered data packet corresponding to a logical channel or a logical channel group. Specifically, the block transmission state indication information of the data packet may be reported in the BSR reported by the terminal according to a logical channel or a logical channel group. The base station may perform allocation and scheduling of Uu port resources with the block transmission status indication information of the data packet included in the BSR.
In another specific scenario, in sidelink communication between a terminal and the terminal, a sending end reports a BSR on a sidelink link, where the BSR includes block transmission status indication information of the data packet. The base station may perform resource allocation and scheduling on the sidelink link according to the block transmission status indication information of the data packet included in the BSR.
In one non-limiting embodiment of the present invention, step S102 shown in fig. 1 may include the following steps before: and the terminal receives the first block sequence number configuration information, wherein the first block sequence number configuration information is used for indicating whether a block sequence number is generated or not. The block sequence number configuration information 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 first block sequence number configuration information is received through a message 1; and if the data packet to be transmitted is a sidelink data packet, receiving the block sequence number configuration information I through a downlink signaling.
In a non-limiting embodiment of the present invention, the base station may further send block sequence number configuration information two. 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 the message 2.
By the embodiment, the sending end and the receiving end can know whether the data packet carries the block sequence number or not.
Specifically, for an uplink data packet, a base station includes block sequence number configuration information one in a message 1 sent to a UE; the first block sequence number configuration information is to indicate whether a data packet needs to carry a block sequence number, may indicate whether a data packet in a DRB needs to carry a block sequence number, and may also indicate whether a data packet in a PDU session or Qos flow needs to carry a block sequence number. For example, if the base station indicates that a data packet in a DRB carries a block sequence number, the terminal carries the block sequence number in the data packet of the DRB.
For downlink service, the base station includes block sequence number configuration information II in a message 2 sent to the UE; and the second block sequence number configuration information refers to whether the data packet carries a block sequence number. It may indicate whether the data packet in one DRB needs to carry the block sequence number, and may also indicate whether the data packet in PDU session or Qos flow needs 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 reads the block sequence number in the received data packet of the DRB.
It should be noted that, besides the message 1 and the message 2, the present invention may also be any implementable message, including but not limited to RRC configuration information (RRCReconfiguration), RRC recovery message (rrcresum), RRC setup message (RRCSetup), and the like, which is not limited in this embodiment of the present invention.
For sidelink communication, the base station may indicate whether the block sequence number is carried in the transmitted data packet, and further, the transmitting end may indicate whether the block sequence number is carried in the data packet transmitted by the receiving end.
Referring to fig. 2, the synchronous transmission method shown in fig. 2 can be used at a receiving end, that is, an apparatus for receiving a data packet. For example, a UE, a base station, a core network, etc. Specifically, in an uplink transmission scenario, a sending end is a UE, and a receiving end is a base station and a core network; in a downlink transmission scene, a sending end is a core network, and a receiving end is a base station and UE; in an SL transmission scenario, the sending end is a UE, and the receiving end is also a UE, which is not limited in this embodiment of the present invention.
Specifically, the synchronous transmission method may include the steps of:
step S201: receiving data packets in one or more types of data streams;
step S202: synchronously transmitting data packets in the same data block, wherein the data packets belonging to the same data block have the same block serial number;
the method comprises the steps that a sending end obtains data packets to be transmitted in one or more types of data streams, wherein the multiple types of data streams have different service qualities; generating a block sequence number for each data packet to be transmitted; 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, and the block sequence number of each data packet is carried in a 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 a core network user plane network element or a user equipment, and a block sequence number of the data packet is carried in a PDU header.
In a non-limiting embodiment, the receiving end is a core network or a UE, and the receiving end may also deliver the data packet to an upper layer protocol entity or an 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 is an uplink data packet. The sending end is UE, and the receiving end is a base station and a core network.
In step S31, the bs 32 sends message 1 to the UE33, where the message 1 includes the first block sequence number configuration information. Block sequence number configuration information one indicates that the UE33 carries the block sequence number in the data packet.
In step S32, the upper layer application of the UE33 and/or the non-access stratum entity 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 a packet header of the uplink data packet on the air interface.
In step S34, for data block 1, if the UE33 fails to transmit all the data packets successfully within the preset time period, the UE33 terminates transmitting the unsuccessfully transmitted data packets in data block 1. The other data blocks are successfully sent.
In step S35, the base station 32 transmits the successfully received uplink packet to the core network 31. The data packet transmitted by the base station 32 carries the block sequence number.
In step S36, for data block 1, the base station 32 fails to receive all the data packets successfully within the preset time length, and the base station 32 discards the successfully received data packets in data block 1.
In step S37, the core network 31 delivers the received data packet 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 packet to be transmitted is a downlink data packet. The sending end is a core network, and the receiving end is a base station and UE.
In step S41, the upper layer application and/or the non-access stratum entity of the core network 41 generates a corresponding block sequence number of the data packet.
In step S42, the core network 41 sends a downlink data packet, where the packet header of the downlink data packet carries the block sequence number.
In step S43, for the data block 1, the core network 41 fails to successfully transmit all the data packets within the preset time length, and the core network 41 terminates transmitting the unsuccessfully transmitted data packets in the data block 1. The other data blocks are successfully sent.
In step S44, the base station 42 transmits the successfully received uplink packet to the UE 43. The data packet transmitted by the base station 42 carries the block sequence number.
In step S45, for data block 1, the base station 42 fails to receive all the data packets successfully within the preset time period, and the base station 42 discards the successfully received data packets in data block 1.
In step S46, the UE43 posts the received data packet to an upper layer protocol entity or an application layer protocol entity by 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 UE, and the receiving end is also UE.
In this case, the block sequence number configuration information may be transmitted to the transmitting end and the receiving end by the base station. The interactive process between the sending end and the receiving end may refer to the interactive process between the UE and the base station in fig. 3, which is not described herein again.
Referring to fig. 5, an embodiment of the present invention further discloses a synchronous transmission device 50, where the synchronous transmission device 50 may include:
a data obtaining module 501, configured to obtain a data packet to be transmitted in one or more types of data streams, where the multiple types of data streams have different quality of service;
the synchronous transmission module 502 is configured to perform synchronous transmission on data packets in the same data block, where 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, where 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 perform synchronous transmission on data packets in the same data block, where the data packets belonging to the same data block have the same block sequence number.
For more details of the operation principle and the operation mode 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, or a chip module, etc.
With regard to each module/unit included in each apparatus and product described in the above embodiments, it may be a software module/unit, or may also be a hardware module/unit, or may also be 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 into a chip, each module/unit included in the device or product may be implemented by hardware such as a circuit, or at least a part of the module/unit may be implemented by a software program running on a processor integrated within the chip, and the rest (if any) part of the module/unit may be implemented by hardware such as a circuit; for each device or product applied to or integrated with the chip module, each module/unit included in the device or product may be implemented by using hardware such as a circuit, and different modules/units may be located in the same component (e.g., a chip, a circuit module, etc.) or different components of the chip module, or at least some of the modules/units may be implemented by using a software program running on a processor integrated within the chip module, and the rest (if any) of the modules/units may be implemented by using hardware such as a circuit; for each device and product applied to or integrated in the terminal, each module/unit included in the device and product may be implemented by hardware such as a circuit, different modules/units may be located in the same component (e.g., a chip, a circuit module, etc.) or different components in the terminal, or at least part of the modules/units may be implemented by a software program running on a processor integrated in the terminal, and the rest (if any) part of the modules/units may be implemented by hardware such as a circuit.
The embodiment of the present invention also discloses a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium, and when the computer program runs, the steps of the synchronous transmission method shown in fig. 1 or fig. 2 may be executed. The storage medium may include ROM, RAM, magnetic or optical disks, etc. The storage medium may further include a non-volatile (non-volatile) memory or a non-transient (non-transient) memory, etc.
The embodiment of the invention also discloses a sending device which can comprise a memory and a processor, wherein the memory is stored with a computer program which can run on the processor. The processor, when running the computer program, may perform the steps of the synchronous transmission method shown in fig. 1.
The embodiment of the invention also discloses a receiving device which comprises a memory and a processor, wherein the memory stores a computer program which can run on the processor. The processor, when running the computer program, may perform the steps of the synchronous transmission method shown in fig. 2.
The technical solution of the present invention is also applicable to different network architectures, including but not limited to a relay network architecture, a dual link architecture, a Vehicle-to-electrical (communication from Vehicle to any object) architecture, and the like.
In this embodiment of the present application, the Core Network may be an evolved packet Core (EPC for short), a 5G Core Network (5G Core Network), or may be a novel Core Network in a future communication system. The 5G Core Network is composed of a set of devices, and implements Access and Mobility Management functions (AMF) for Mobility Management and other functions, User Plane Function (UPF) for providing packet routing and forwarding and qos (quality of service) Management functions, Session Management Function (SMF) for providing Session Management, IP address allocation and Management functions, and the like. The EPC may be composed of an MME providing functions such as mobility management, Gateway selection, etc., a Serving Gateway (S-GW) providing functions such as packet forwarding, etc., and a PDN Gateway (P-GW) providing functions such as terminal address allocation, rate control, etc.
A Base Station (BS) in the embodiment of the present application, which may also be referred to as a base station device, is a device deployed in a Radio Access Network (RAN) to provide a wireless communication function. For example, a device providing a base station function in a 2G network includes a Base Transceiver Station (BTS), a device providing a base station function in a 3G network includes a node b (nodeb), apparatuses for providing a base station function in a 4G network include evolved node bs (enbs), which, in a Wireless Local Area Network (WLAN), the devices providing the base station function are Access Point (AP), gNB providing the base station function in New Radio (NR), and node B for continuing evolution (ng-eNB), the gNB and the terminal communicate with each other by adopting NR technology, the ng-eNB and the terminal communicate with each other by adopting E-UTRA (evolved Universal Terrestrial Radio Access) technology, and both the gNB and the ng-eNB can be connected to a 5G core network. The base station in the embodiment of the present application also includes an apparatus and the like for providing a function of the base station in a future new communication system.
The base station controller in the embodiment of the present application is a device for managing a base station, for example, a Base Station Controller (BSC) in a 2G network, a Radio Network Controller (RNC) in a 3G network, or a device for controlling and managing a base station in a future new communication system.
The network on the network side in the embodiment of the present invention refers to a communication network providing a communication service for a terminal, and includes a base station of a radio access network, a base station controller of the radio access network, and a device on the core network side.
A terminal in this embodiment may refer to various forms of User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station (mobile station, MS), a remote station, a remote terminal, a mobile device, a user terminal, a terminal device (terminal equipment), a wireless communication device, a user agent, or a 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 handheld device with a Wireless communication function, a computing device, or other processing devices connected to a Wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a future 5G Network, or a terminal device in a Public Land Mobile Network (PLMN) for future evolution, and the like, which is not limited in this embodiment of the present application.
In the embodiment of the application, a unidirectional communication link from an access network to a terminal is defined as a downlink, data transmitted on the downlink is downlink data, and the transmission direction of the downlink data is called as a downlink direction; the unidirectional communication link from the terminal to the access network is an uplink, the data transmitted on the uplink is uplink data, and the transmission direction of the uplink data is called uplink direction.
It should be understood that the term "and/or" herein is merely one type of association relationship that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" in this document indicates that the former and latter related objects are in an "or" relationship.
The "plurality" appearing in the embodiments of the present application means two or more.
The descriptions of the first, second, etc. appearing in the embodiments of the present application are only for the purpose of illustrating and differentiating the description objects, and do not represent any particular limitation to the number of devices in the embodiments of the present application, and cannot constitute any limitation to the embodiments of the present application.
The term "connection" in the embodiment of the present application refers to various connection manners such as direct connection or indirect connection, so as to implement communication between devices, which is not limited in this embodiment of the present application.
It should be understood that, in the embodiment of the present application, the processor may be a Central Processing Unit (CPU), and the processor may also be other 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. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
It will also be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The nonvolatile 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 may be Random Access Memory (RAM) which acts as external cache memory. By way of example and not limitation, many forms of Random Access Memory (RAM) are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (enhanced SDRAM), SDRAM (SLDRAM), synchlink DRAM (SLDRAM), and direct bus RAM (DR RAM).
The above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. 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. The procedures or functions described in accordance with the embodiments of the present application are produced in whole or in part when the computer instructions or the computer program are loaded or executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire or wirelessly. 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, data center, etc., that contains one or more collections of available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. The semiconductor medium may be a solid state disk.
It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
In the several embodiments provided in the present application, it should be understood that the disclosed method, apparatus and system may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative; for example, the division of the unit is only a logic function division, and there may be another division manner in actual implementation; for example, various elements or components may be combined or may be integrated in another system or some features may be omitted, or not implemented. In addition, the 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 units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be physically included alone, or two or more units may be integrated into one unit. The integrated unit may be implemented in the form of hardware, or in the form of hardware plus a software functional unit.
The integrated unit implemented in the form of a software functional unit may be stored in a computer-readable storage medium. The software functional unit 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 some steps of the methods according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
Although the present invention is disclosed above, the present invention is not limited thereto. Various changes and modifications may be effected by one skilled in the art without departing from the spirit and scope of the invention, as defined in the appended claims.
Claims (29)
1. A method of synchronous transmission, comprising:
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.
2. The synchronous transmission method according to claim 1, wherein the header of the synchronously transmitted data packet carries a block sequence number.
3. The synchronous transmission method according to claim 1, wherein the synchronous transmission of the data packets in the same data block comprises:
and transmitting the data packets in the same data block by using the transmission resources within the 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:
determining a first transmitted data packet and a last transmitted data packet in each data block;
generating a block start transmission indication for the first transmitted data packet and carrying the block start transmission indication in the data packet header of the first transmitted data packet, and generating a block end transmission indication for the last transmitted data packet and carrying the block end transmission indication in the data packet header of the last transmitted data packet.
5. The synchronous transmission method according to claim 4, wherein the determining the first transmitted data packet and the last transmitted data packet in each data block comprises:
the first transmitted data packet and the last transmitted data packet in the various types of data streams are determined in each data block.
6. The synchronous transmission method according to claim 1, further comprising:
and if the data packets in the data blocks needing to be integrally transmitted exist in the data blocks which are not successfully transmitted, terminating the transmission of the data packets which are not successfully transmitted in the data blocks needing to be integrally transmitted.
7. The synchronous transmission method according to claim 1, further comprising:
and if the data packets in the data blocks needing to be integrally transmitted exist in the preset time span and are not successfully transmitted, terminating the transmission of the data packets which are not successfully transmitted in the data blocks needing to be integrally transmitted.
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:
and receiving indication information from a network element of a core network, wherein the indication information is used for indicating whether the data block needs to be transmitted integrally.
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 a data packet to be transmitted in the data block that needs to be transmitted in the whole buffer.
10. The synchronous transmission method according to claim 9, wherein the block transmission status indication information further includes a block sequence number of the data block to be transmitted in its entirety.
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:
and receiving first block sequence number configuration information, wherein the first block sequence number configuration information is used for indicating whether a block sequence number is generated or not.
13. The synchronous transmission method according to claim 12, wherein the block sequence number configuration information is used to indicate whether a data packet in a single DRB, PDU session or data flow generates a block sequence number.
14. The method according to claim 12, wherein the receiving the first block sequence number configuration information comprises:
if the data packet to be transmitted is an uplink data packet, receiving the block sequence number configuration information I through a message 1;
and if the data packet to be transmitted is a sidelink data packet, receiving the block sequence number configuration information I through a 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:
and sending block sequence number configuration information II, wherein the block sequence number configuration information is used for indicating whether the received data packet contains a block sequence number.
16. The synchronous transmission method according to claim 15, wherein the sending the second block sequence number configuration information comprises:
and if the data packet to be transmitted is a downlink data packet, sending the block sequence number configuration information II through a message 2.
17. The synchronous transmission method according to claim 2, wherein the data packet header is selected from the group consisting of a PDCP header, an SDAP header, and a PDU header of other protocol layers.
18. A method of synchronous transmission, comprising:
receiving data packets 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.
19. The synchronous transmission method according to claim 18, wherein the data packet is an uplink data packet, the method further comprising:
and sending the received data packet to a core network user plane network element or user equipment, wherein the block sequence number of the data packet is carried in PDU heads of different protocol layers.
20. The synchronous transmission method according to claim 18, further comprising:
and delivering the data packet to an upper layer protocol entity or an application layer protocol entity according to the block sequence number.
21. The synchronous transmission method according to claim 18, further comprising:
and if the data packet which needs to be transmitted in the whole is not successfully received, the received data packet is discarded.
22. The synchronous transmission method according to claim 18, further comprising:
and if the data block needing to be transmitted in the whole within the preset time length has data packet non-reception success, discarding the received data packet.
23. The synchronous transmission method according to claim 18, wherein the receiving the data packets in the one or more types of data streams further comprises:
and receiving indication information from a core network element, wherein the indication information is used for indicating whether the data block needs to be transmitted in a whole manner.
24. The synchronous transmission method according to claim 18, wherein the receiving the data packets in the one or more types of data streams further comprises:
and receiving second block sequence number configuration information, wherein the second block sequence number configuration information is used for indicating whether the received data packet contains a block sequence number or not.
25. A synchronous transmission device, comprising:
the data acquisition module is used for acquiring data packets to be transmitted in one or more types of data streams;
and the synchronous transmission module is used for synchronously transmitting 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 apparatus, comprising:
the data receiving module is used for receiving data packets in one or more types of data streams;
and the data block transmission module is used for synchronously transmitting the 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 having a computer program stored thereon, wherein the computer program, when executed by a processor, performs the steps of the synchronous transmission method of any of claims 1 to 24.
28. A transmitting device comprising a memory and a processor, the memory having stored thereon a computer program operable on the processor, wherein the processor, when executing the computer program, performs the steps of the synchronous transmission method of any of claims 1 to 17.
29. A receiving device comprising a memory and a processor, said memory having stored thereon a computer program operable on said processor, wherein said processor, when executing said computer program, performs the steps of the synchronous transmission method of any of claims 18 to 24.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110106473.XA CN114793357A (en) | 2021-01-26 | 2021-01-26 | Synchronous transmission method and device, storage medium, sending end equipment and receiving end equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110106473.XA CN114793357A (en) | 2021-01-26 | 2021-01-26 | Synchronous transmission method and device, storage medium, sending end equipment and receiving end equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114793357A true CN114793357A (en) | 2022-07-26 |
Family
ID=82459641
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110106473.XA Pending CN114793357A (en) | 2021-01-26 | 2021-01-26 | Synchronous transmission method and device, storage medium, sending end equipment and receiving end equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114793357A (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101651510A (en) * | 2008-08-14 | 2010-02-17 | 中兴通讯股份有限公司 | Method and device for recovery processing in service data synchronous transmission |
| CN108427982A (en) * | 2018-03-16 | 2018-08-21 | 中国联合网络通信集团有限公司 | A kind of data read-write method and device |
| CN108900580A (en) * | 2018-06-12 | 2018-11-27 | 海南省火蓝数据有限公司 | It is a kind of based on the interactive information processing method for melting media service platform |
| CN109391420A (en) * | 2017-08-11 | 2019-02-26 | 华为技术有限公司 | The instruction of synchronization signal block and determining method, the network equipment and terminal device |
| CN109565715A (en) * | 2017-08-11 | 2019-04-02 | Oppo广东移动通信有限公司 | It is used for transmission method, terminal device and the network equipment of data |
| CN110140301A (en) * | 2019-03-25 | 2019-08-16 | 北京小米移动软件有限公司 | Synchronization signal block transmission method, device and storage medium |
| CN110831075A (en) * | 2018-08-10 | 2020-02-21 | 中兴通讯股份有限公司 | Data transmission method and device and service switching method and device |
| WO2020199397A1 (en) * | 2019-03-29 | 2020-10-08 | Telefonaktiebolaget Lm Ericsson (Publ) | Method, apparatus for synchronization of status of qos flow in communication system |
-
2021
- 2021-01-26 CN CN202110106473.XA patent/CN114793357A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101651510A (en) * | 2008-08-14 | 2010-02-17 | 中兴通讯股份有限公司 | Method and device for recovery processing in service data synchronous transmission |
| CN109391420A (en) * | 2017-08-11 | 2019-02-26 | 华为技术有限公司 | The instruction of synchronization signal block and determining method, the network equipment and terminal device |
| CN109565715A (en) * | 2017-08-11 | 2019-04-02 | Oppo广东移动通信有限公司 | It is used for transmission method, terminal device and the network equipment of data |
| CN108427982A (en) * | 2018-03-16 | 2018-08-21 | 中国联合网络通信集团有限公司 | A kind of data read-write method and device |
| CN108900580A (en) * | 2018-06-12 | 2018-11-27 | 海南省火蓝数据有限公司 | It is a kind of based on the interactive information processing method for melting media service platform |
| CN110831075A (en) * | 2018-08-10 | 2020-02-21 | 中兴通讯股份有限公司 | Data transmission method and device and service switching method and device |
| CN110140301A (en) * | 2019-03-25 | 2019-08-16 | 北京小米移动软件有限公司 | Synchronization signal block transmission method, device and storage medium |
| WO2020199397A1 (en) * | 2019-03-29 | 2020-10-08 | Telefonaktiebolaget Lm Ericsson (Publ) | Method, apparatus for synchronization of status of qos flow in communication system |
Non-Patent Citations (1)
| Title |
|---|
| SAMSUNG: "S2-2000887 "Modification of PDU Session to Always-on PDU Session for URLLC QoS Flow"", 3GPP TSG_SA\\WG2_ARCH, no. 2, 7 January 2020 (2020-01-07) * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10917831B2 (en) | Radio access network slice generation method, radio access network, and slice manager | |
| CN108684073B (en) | It is a kind of registration and session establishment method, terminal and AMF entity | |
| EP4013108A1 (en) | User plane information reporting method and apparatus | |
| US11930391B2 (en) | Wireless communications apparatus and methods | |
| CN108323245A (en) | It is a kind of registration and session establishment method, terminal and AMF entities | |
| EP3493493A1 (en) | Service data transmission method, network device, and terminal device | |
| JP6693572B2 (en) | System, Controller, Exposure Function Entity, and Method | |
| CN113766567A (en) | Communication method and device | |
| WO2019001391A1 (en) | Radio resource scheduling method, video terminal, and access network device | |
| CN108702766A (en) | Communication means, the network equipment and terminal device | |
| US20240031870A1 (en) | Media data transmission method and communication apparatus | |
| CN113286326A (en) | Communication method and device | |
| EP4124047A1 (en) | Media packet transmission method, apparatus and system | |
| CN114793357A (en) | Synchronous transmission method and device, storage medium, sending end equipment and receiving end equipment | |
| CN113709763A (en) | Access control method and device, storage medium and terminal | |
| WO2024067374A1 (en) | Communication method and apparatus | |
| WO2023141816A1 (en) | Ecentral unit, distributed unit, user equipment and method for application data unit based data transmission | |
| US20240305574A1 (en) | Quality of service qos management method and apparatus | |
| EP4460079A1 (en) | Cooperative communication method and apparatus, and computer-readable storage medium | |
| WO2023134410A1 (en) | Communication method, apparatus, and system | |
| EP4401445A1 (en) | Communication method and apparatus | |
| US20230117868A1 (en) | Media packet transmission method, apparatus, and system | |
| US20240129786A1 (en) | Session management method and apparatus | |
| TW202431883A (en) | Communication method and apparatus | |
| CN114828088A (en) | Communication method and device, storage medium, base station, and terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |