CN113543212A - 5G communication data transmission method and device and nonvolatile storage medium - Google Patents
5G communication data transmission method and device and nonvolatile storage medium Download PDFInfo
- Publication number
- CN113543212A CN113543212A CN202110770585.5A CN202110770585A CN113543212A CN 113543212 A CN113543212 A CN 113543212A CN 202110770585 A CN202110770585 A CN 202110770585A CN 113543212 A CN113543212 A CN 113543212A
- Authority
- CN
- China
- Prior art keywords
- rlc entity
- data unit
- data
- program
- request information
- 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
- 238000000034 method Methods 0.000 title claims abstract description 60
- 230000005540 biological transmission Effects 0.000 title claims abstract description 47
- 238000004891 communication Methods 0.000 title claims abstract description 25
- 238000010586 diagram Methods 0.000 description 8
- 230000008569 process Effects 0.000 description 5
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000003993 interaction Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000005457 optimization Methods 0.000 description 2
- 230000011218 segmentation Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 1
- 230000018109 developmental process Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- 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/0215—Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices
-
- 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
Abstract
The application discloses a transmission method and device of 5G communication data and a nonvolatile storage medium. Wherein, the method comprises the following steps: a first RLC entity sends request information for acquiring a data unit to a second RLC entity; the first RLC entity receives a data unit corresponding to the request information returned by the second RLC entity; the first RLC entity analyzes the received data unit to obtain a target data unit. The method and the device solve the technical problem that in the prior art, in the data transmission process of the RLC entity, different data unit request calling schemes need to be compiled for different program interfaces, so that the data transmission efficiency is low.
Description
Technical Field
The present application relates to the field of wireless communication, and in particular, to a method and an apparatus for transmitting 5G communication data, and a non-volatile storage medium.
Background
With the development of 5G white-box, the amount of data to be processed is increasing, and the data types are diversified, which makes information interaction between RLC (Radio Link Control) entities located in a data Link layer in a wireless communication architecture become increasingly complex. Most RLC entities run on X86 servers, and with the increasing demand and optimization, the exchange between procedures within the RLC entities tends to become more complex.
In most cases today, the data exchange between RLC entities is performed by one module sending a request for receiving data units to another module, and the module receiving the request sends the data units to the module according to a certain format. For example, in AM mode, when a data unit arrives in the RLC entity through a logical channel, the sending buffer module will buffer the data unit received first. At this time, the segmented serial module behind the sending cache module sends a request to the sending cache module, and the cached data unit is sent to the input port of the segmented serial module by taking the sending cache module as an output to finish sending.
In the face of increasing updates and optimizations, each time a program in an RLC entity is updated, a call method for a data unit request, a method for return data parsing, and a method for synchronizing data need to be rewritten for the program. Therefore, a large amount of manpower and time are consumed, and the efficiency is not improved.
Therefore, a method for quickly establishing port call between programs in the RLC entity is needed to solve the problem of low data transmission efficiency caused by the fact that different data unit request call schemes need to be written for different program interfaces in the data transmission process of the RLC entity in the prior art.
In view of the above problems, no effective solution has been proposed.
Disclosure of Invention
The embodiment of the application provides a transmission method and device of 5G communication data and a nonvolatile storage medium, which are used for at least solving the technical problem of low data transmission efficiency caused by the fact that different data unit request calling schemes need to be compiled for different program interfaces in the data transmission process of an RLC entity in the prior art.
According to an aspect of the embodiments of the present application, there is provided a method for transmitting 5G communication data, the method being applied between any two radio link control RLC entities, the method including: a first RLC entity sends request information for acquiring a data unit to a second RLC entity; the first RLC entity receives a data unit corresponding to the request information returned by the second RLC entity; the first RLC entity analyzes the received data unit to obtain a target data unit.
Optionally, the sending, by the first RLC entity, request information for acquiring the data unit to the second RLC entity includes: the first RLC entity sends request information for acquiring a data unit to the second RLC entity according to configuration information of a program running in the first RLC entity.
Optionally, the request information includes at least: the length of the data unit, the configuration information, and the data header of the data unit.
Optionally, the analyzing, by the first RLC entity, the received data unit to obtain a target data unit includes: and the first RLC entity analyzes the received data unit according to the configuration information to obtain a data format which can be identified by a program running in the first RLC entity.
Optionally, the method is applied to any one of the following data transmission modes of the RLC entity: transparent mode, unacknowledged mode, and acknowledged mode.
According to another aspect of the embodiments of the present application, there is also provided a transmission apparatus for 5G communication data, including: a sending module, configured to control a first RLC entity to send request information for acquiring a data unit to a second RLC entity; a receiving module, configured to control the first RLC entity to receive a data unit corresponding to the request information, where the data unit is returned by the second RLC entity; and the analysis module is used for controlling the first RLC entity to analyze the received data unit to obtain a target data unit.
Optionally, the sending module is further configured to control the first RLC entity to send, to the second RLC entity, request information for acquiring the data unit according to configuration information of a program running in the first RLC entity.
Optionally, the parsing module is further configured to control the first RLC entity to parse the received data unit according to the configuration information, so as to obtain a data format that can be identified by a program running in the first RLC entity.
According to still another aspect of the embodiments of the present application, there is provided a non-volatile storage medium, where the non-volatile storage medium includes a stored program, and when the program runs, a device in which the non-volatile storage medium is located is controlled to execute the above transmission method of the 5G communication data.
According to still another aspect of the embodiments of the present application, there is provided a processor configured to execute a program stored in a memory, where the program executes the above transmission method of 5G communication data.
In the embodiment of the application, a transmission method of 5G communication data is provided, and the method is applied between any two radio link control RLC entities, and the method includes: a first RLC entity sends request information for acquiring a data unit to a second RLC entity; the first RLC entity receives a data unit corresponding to the request information returned by the second RLC entity; the first RLC entity analyzes the received data unit to obtain a target data unit, and a uniform data unit request calling method is established among the program interfaces in the RLC entity, so that the technical effect of improving the data transmission efficiency among the RLC entities is achieved, and the technical problem that in the data transmission process of the RLC entity in the prior art, different data unit request calling schemes need to be compiled for different program interfaces, and the data transmission efficiency is low is solved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1 is a flowchart of a transmission method of 5G communication data according to an embodiment of the present application;
FIG. 2a is a schematic diagram of a transparent transmission mode of RLC data according to an embodiment of the present application;
FIG. 2b is a schematic diagram of an unacknowledged transmission mode of RLC data according to an embodiment of the application;
FIG. 2c is a schematic diagram of an acknowledged transmission mode of RLC data according to an embodiment of the present application;
fig. 3 is a block diagram of a transmission apparatus for 5G communication data according to an embodiment of the present application.
Detailed Description
In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only partial embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
First, some terms or terms appearing in the description of the embodiments of the present application are applicable to the following explanations:
RLC, Radio Link Control, Radio Link layer Control protocol, provides segmentation and retransmission services for user and Control data.
According to an embodiment of the present application, there is provided a method embodiment of a method for transmitting 5G communication data, where it is noted that the steps shown in the flowchart of the drawings may be executed in a computer system such as a set of computer executable instructions, and that although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in an order different from that shown or described herein.
Fig. 1 is a flowchart of a method for transmitting 5G communication data according to an embodiment of the present application, the method being applied between any two RLC entities, as shown in fig. 1, and the method includes the following steps:
step S102, a first RLC entity sends request information for acquiring a data unit to a second RLC entity;
step S104, the first RLC entity receives a data unit corresponding to the request information returned by the second RLC entity;
step S106, the first RLC entity analyzes the received data unit to obtain a target data unit.
Through the steps, the uniform data unit request calling method is established among the program interfaces in the RLC entities, so that the technical effect of improving the data transmission efficiency among the RLC entities is achieved.
According to an alternative embodiment of the present application, when step S102 is executed, the first RLC entity sends request information for acquiring a data unit to the second RLC entity, and the method is implemented by: the first RLC entity sends request information for acquiring a data unit to the second RLC entity according to configuration information of a program running in the first RLC entity.
According to another alternative embodiment of the present application, the request information at least includes: the length of the data unit, the configuration information, and the data header of the data unit.
In this step, a program within the first RLC entity issues a request to another target program according to the auto-configuration procedure information of the program, asking the target program to send the corresponding data unit to the program so that it performs the corresponding operation on the data unit. The request information contains the length of the requested data unit, the configuration information of the requesting program and the data header of the corresponding data unit.
The target program receives the request, and the autoconfiguration procedure information device associated with the target program interprets the request, accepts the request, and sends the corresponding data unit to the procedure within the first RLC entity (the procedure that sent the request).
In some optional embodiments of the present application, step S106 is executed, and the first RLC entity parses the received data unit to obtain a target data unit, and the method is implemented as follows: and the first RLC entity analyzes the received data unit according to the configuration information to obtain a data format which can be identified by a program running in the first RLC entity.
In this step, the requesting program receives the data unit, and the means for automatically configuring the program information parses the received data unit according to the configuration information of the program, and finally parses the data unit into a data format recognizable by the program.
By the method, the received data unit is analyzed into the data format which can be identified by the request program, so that the problem of low data transmission efficiency caused by the fact that different data unit request calling schemes need to be compiled for different program interfaces in the data transmission process of the RLC entity in the prior art can be solved.
It should be noted that the method provided by the present application is applied between programs of any two RLC entities, so as to solve the problems of low transmission efficiency and increased labor and time costs caused by the need of compiling a set of different request protocols for transmission of data service units between the programs in the RLC. And may be executed as a set of corresponding instructions in a computer system. This flow describes a process in which one program sends a request to another program to transfer a unit of data, and the program that receives the request sends the unit of data as the Output (Output) of the program and becomes the Input (Input) of the requesting program to be sent to the next program, repeating the same process.
In another alternative embodiment of the present application, the above method is applied to any one of the following data transmission modes of the RLC entity: transparent mode, unacknowledged mode, and acknowledged mode.
There are three modes for RLC data transmission, namely TM (transparent mode), UM (unacknowledged mode), and AM (acknowledged mode). TM mode transmission is simple and time delay is small, while UM and AM modes will carry out additional segmented concatenation on data packet transmission, and time delay is relatively large.
Fig. 2a is a schematic diagram of a transparent transmission mode of RLC data according to an embodiment of the present application, as shown in fig. 2a, in a TM transmission mode, a sending-end RLC entity sends a data service unit to a receiving end only by reserving one data service unit buffer, and completes sending with the shortest time delay, there is no data segmentation and there is no need to ensure that data packets arrive in sequence, so that a flow is simple, and information interaction of too many programs in the entity is not involved.
Fig. 2b is a schematic diagram of an unacknowledged transmission mode of RLC data according to an embodiment of the present application, and as shown in fig. 2b, in an UM transmission mode, a transmitting-end RLC entity needs to buffer data service units, concatenate the data service units in segments, add an RLC header, and then transmit the data to a receiving-end RLC entity. The whole process involves more procedures. It is necessary to establish an interface calling device in each program to increase the transmission efficiency.
Fig. 2c is a schematic diagram of an acknowledged transmission mode of RLC data according to an embodiment of the present application, as shown in fig. 2c, in the AM mode, RLC control and error control need to be established, and the transmitting end RLC and the receiving end RLC transmit data simultaneously and establish retransmission buffer, the number of involved program interactions becomes more and more complex, and therefore, data service units received by different programs need to be parsed and synchronized to maintain data mobility and interface efficiency.
Fig. 3 is a block diagram of a transmission apparatus for 5G communication data according to an embodiment of the present application, and as shown in fig. 3, the apparatus includes:
a sending module 30, configured to control a first RLC entity to send request information for acquiring a data unit to a second RLC entity;
a receiving module 32, configured to control the first RLC entity to receive a data unit corresponding to the request information, where the data unit is returned by the second RLC entity;
the parsing module 34 is configured to control the first RLC entity to parse the received data unit to obtain a target data unit.
By the device, the technical effect of improving the data transmission efficiency between the RLC entities is realized by establishing the uniform data unit request calling method between the program interfaces in the RLC entities.
It should be noted that, reference may be made to the description related to the embodiment shown in fig. 1 for a preferred implementation of the embodiment shown in fig. 3, and details are not described here again.
According to an optional embodiment of the present application, the sending module 30 is further configured to control the first RLC entity to send, to the second RLC entity, request information for obtaining the data unit according to configuration information of a program running in the first RLC entity.
A program within the first RLC entity issues a request to another target program according to the auto-configuration procedure information of the program, asking the target program to send the corresponding data unit to the program so that it performs the corresponding operation on the data unit. The request information contains the length of the requested data unit, the configuration information of the requesting program and the data header of the corresponding data unit.
According to an optional embodiment of the present application, the parsing module 34 is further configured to control the first RLC entity to parse the received data unit according to the configuration information, so as to obtain a data format that can be identified by a program running in the first RLC entity.
The requesting program receives the data unit, and the device for automatically configuring the program information analyzes the received data unit according to the configuration information of the program, and finally analyzes the data unit into a data format which can be identified by the program.
By the functions, the received data unit is analyzed into the data format which can be identified by the request program, so that the problem of low data transmission efficiency caused by the fact that different data unit request calling schemes need to be compiled for different program interfaces in the data transmission process of the RLC entity in the prior art can be solved.
The embodiment of the application also provides a nonvolatile storage medium, wherein the nonvolatile storage medium comprises a stored program, and the device where the nonvolatile storage medium is located is controlled to execute the above transmission method of the 5G communication data when the program runs.
The nonvolatile storage medium stores a program for executing the following functions: a first RLC entity sends request information for acquiring a data unit to a second RLC entity; the first RLC entity receives a data unit corresponding to the request information returned by the second RLC entity; the first RLC entity analyzes the received data unit to obtain a target data unit.
According to still another aspect of the embodiments of the present application, there is provided a processor configured to execute a program stored in a memory, where the program executes the above transmission method of 5G communication data.
The processor is used for running a program for executing the following functions: a first RLC entity sends request information for acquiring a data unit to a second RLC entity; the first RLC entity receives a data unit corresponding to the request information returned by the second RLC entity; the first RLC entity analyzes the received data unit to obtain a target data unit.
The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.
In the above embodiments of the present application, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the embodiments provided in the present application, it should be understood that the disclosed technology can be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units may be a logical division, and in actual implementation, there may be another division, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not executed. 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, units or modules, and may be in an electrical 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 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 application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.
The foregoing is only a preferred embodiment of the present application and it should be noted that those skilled in the art can make several improvements and modifications without departing from the principle of the present application, and these improvements and modifications should also be considered as the protection scope of the present application.
Claims (10)
1. A method for transmitting 5G communication data, which is applied between any two Radio Link Control (RLC) entities, the method comprising:
a first RLC entity sends request information for acquiring a data unit to a second RLC entity;
the first RLC entity receives a data unit which is returned by the second RLC entity and corresponds to the request information;
and the first RLC entity analyzes the received data unit to obtain a target data unit.
2. The method of claim 1, wherein the first RLC entity sending request information for obtaining data units to the second RLC entity comprises:
and the first RLC entity sends request information for acquiring data units to the second RLC entity according to the configuration information of the program running in the first RLC entity.
3. The method of claim 2, wherein the request information comprises at least: a length of the data unit, the configuration information, and a data header of the data unit.
4. The method of claim 2, wherein the first RLC entity parsing the received data unit to obtain a target data unit comprises:
and the first RLC entity analyzes the received data unit according to the configuration information to obtain a data format which can be identified by a program running in the first RLC entity.
5. The method according to any of claims 1 to 4, wherein the method is applied to any one of the following data transmission modes of the RLC entity: transparent mode, unacknowledged mode, and acknowledged mode.
6. A transmission apparatus for 5G communication data, comprising:
a sending module, configured to control a first RLC entity to send request information for acquiring a data unit to a second RLC entity;
a receiving module, configured to control the first RLC entity to receive a data unit corresponding to the request information, where the data unit is returned by the second RLC entity;
and the analysis module is used for controlling the first RLC entity to analyze the received data unit to obtain a target data unit.
7. The apparatus of claim 6, wherein the sending module is further configured to control the first RLC entity to send request information for obtaining data units to the second RLC entity according to configuration information of a program running in the first RLC entity.
8. The apparatus of claim 7, wherein the parsing module is further configured to control the first RLC entity to parse the received data unit according to the configuration information, so as to obtain a data format that can be recognized by a program running in the first RLC entity.
9. A non-volatile storage medium, characterized in that the non-volatile storage medium comprises a stored program, and when the program runs, the non-volatile storage medium is controlled to execute the transmission method of the 5G communication data according to any one of claims 1 to 5.
10. A processor, characterized in that the processor is configured to run a program stored in a memory, wherein the program is configured to execute the method for transmitting 5G communication data according to any one of claims 1 to 5 when running.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110770585.5A CN113543212A (en) | 2021-07-07 | 2021-07-07 | 5G communication data transmission method and device and nonvolatile storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110770585.5A CN113543212A (en) | 2021-07-07 | 2021-07-07 | 5G communication data transmission method and device and nonvolatile storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113543212A true CN113543212A (en) | 2021-10-22 |
Family
ID=78098021
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110770585.5A Pending CN113543212A (en) | 2021-07-07 | 2021-07-07 | 5G communication data transmission method and device and nonvolatile storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113543212A (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20020012103A (en) * | 2000-08-04 | 2002-02-15 | 박종섭 | Data transmission method for hybrid ARQ type 2/3 on the uplink of wide-band wireless communication system |
| JP2002271442A (en) * | 2001-03-07 | 2002-09-20 | Matsushita Electric Ind Co Ltd | Rlc communication device and rlc communication type judging processing method |
| KR20050118591A (en) * | 2004-06-14 | 2005-12-19 | 엘지전자 주식회사 | Method for handling radio link control date in mobile communication system |
| CN103138905A (en) * | 2011-11-24 | 2013-06-05 | 华为技术有限公司 | Radio link control (RLC) data package transmission confirmation method and RLC acknowledge mode (AM) entity sender |
| CN109041120A (en) * | 2017-06-12 | 2018-12-18 | 中国移动通信有限公司研究院 | Data transmission method, device and computer readable storage medium |
| CN110383880A (en) * | 2017-08-11 | 2019-10-25 | Lg电子株式会社 | Method and apparatus for sending data cell |
| WO2020167188A1 (en) * | 2019-02-14 | 2020-08-20 | Telefonaktiebolaget Lm Ericsson (Publ) | Pdcp entity, rlc entity and methods performed therein for providing multi connectivity |
| CN112740749A (en) * | 2018-09-21 | 2021-04-30 | 株式会社Kt | Method and device for transmitting data |
| CN112751706A (en) * | 2020-12-24 | 2021-05-04 | 珠海格力电器股份有限公司 | Target data transmission method and device |
-
2021
- 2021-07-07 CN CN202110770585.5A patent/CN113543212A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20020012103A (en) * | 2000-08-04 | 2002-02-15 | 박종섭 | Data transmission method for hybrid ARQ type 2/3 on the uplink of wide-band wireless communication system |
| JP2002271442A (en) * | 2001-03-07 | 2002-09-20 | Matsushita Electric Ind Co Ltd | Rlc communication device and rlc communication type judging processing method |
| KR20050118591A (en) * | 2004-06-14 | 2005-12-19 | 엘지전자 주식회사 | Method for handling radio link control date in mobile communication system |
| CN103138905A (en) * | 2011-11-24 | 2013-06-05 | 华为技术有限公司 | Radio link control (RLC) data package transmission confirmation method and RLC acknowledge mode (AM) entity sender |
| CN109041120A (en) * | 2017-06-12 | 2018-12-18 | 中国移动通信有限公司研究院 | Data transmission method, device and computer readable storage medium |
| CN110383880A (en) * | 2017-08-11 | 2019-10-25 | Lg电子株式会社 | Method and apparatus for sending data cell |
| CN112740749A (en) * | 2018-09-21 | 2021-04-30 | 株式会社Kt | Method and device for transmitting data |
| WO2020167188A1 (en) * | 2019-02-14 | 2020-08-20 | Telefonaktiebolaget Lm Ericsson (Publ) | Pdcp entity, rlc entity and methods performed therein for providing multi connectivity |
| CN112751706A (en) * | 2020-12-24 | 2021-05-04 | 珠海格力电器股份有限公司 | Target data transmission method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11178066B2 (en) | Method for transmitting service stream in flexible ethernet and apparatus | |
| EP3758412B1 (en) | Multichannel data transmission method, apparatus, system and computer-readable medium | |
| CN107395572B (en) | Data processing method and Internet of things gateway | |
| FI106763B (en) | A method of communicating the current protocol to other layers of the protocol stack | |
| US20070133548A1 (en) | Transmission apparatus having a plurality of network interfaces and transmission method using the same | |
| CN101997916B (en) | Method and device for file transmission based on network | |
| CN101534519B (en) | Method for displaying package switching congestion state of wireless communication network | |
| CN1839591B (en) | Method for discarding all segments corresponding to same packet in buffer | |
| CN103945455A (en) | Method and device for sending self-adaptive heartbeat data packets | |
| WO2008002603A2 (en) | Capability exchange between network entities in wimax | |
| CN104471904A (en) | Content optimization based on real time network dynamics | |
| US20180367651A1 (en) | Stream control transmission protocol SCTP-based communications method and system, and appartus | |
| CN107368334B (en) | Business plug-in interaction system and method | |
| US11799576B2 (en) | Data sending method and apparatus, and FlexE switching system | |
| CN109728968B (en) | Method, related equipment and system for obtaining target transmission path | |
| CN104753804A (en) | Data stream transmission control method, device and system | |
| CN115442572A (en) | Data transmission method and device | |
| CN113543212A (en) | 5G communication data transmission method and device and nonvolatile storage medium | |
| CN104798397A (en) | Method and device for hosting application by access node | |
| CN107078837A (en) | A kind of agreement frame transmission method, device, node device and system | |
| EP3896907A1 (en) | Method and apparatus for acquiring network slice identification | |
| CN211630177U (en) | Equipment data acquisition system | |
| CN109495918B (en) | Data transmission method and device | |
| CN113840277A (en) | Download control method, system, terminal and medium for user subscription data | |
| CN107231567A (en) | A kind of message transmitting method, apparatus and system |
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 |