WO2018161702A1

WO2018161702A1 - Method for processing data service in long term evolution (lte) base station and base station

Info

Publication number: WO2018161702A1
Application number: PCT/CN2017/119495
Authority: WO
Inventors: 郑丹平; 黄勇; 吴伟锋
Original assignee: 京信通信系统（中国）有限公司; 京信通信系统（广州）有限公司; 京信通信技术(广州)有限公司; 天津京信通信系统有限公司
Priority date: 2017-03-06
Filing date: 2017-12-28
Publication date: 2018-09-13
Also published as: CN107018531A; CN107018531B

Abstract

The present invention discloses a method for processing a data service in a long term evolution (LTE) base station and a base station. The method comprises: upon detecting that a preset condition for adding a trigger event is met, adding a trigger event to at least one event queue preset in an LTE base station, the trigger event comprising at least an identifier of a bearer entity and an identifier of the trigger event; and then processing, according to the trigger event acquired from the event queue, a data service on the bearer entity indicated by the trigger event. In this way, in order to process the data service on the bearer entity indicated by the trigger event, it is only necessary to acquire the trigger event from the event queue and it is not necessary to traverse all bearer entities during data processing, such that processing is performed only when there is data in the bearer entity, reducing time spent traversing different bearer entities. Thus, data processing delays can be shortened, improving system performance.

Description

Method and base station for processing data service in long-term evolution LTE base station

The present application claims priority to Chinese Patent Application, filed on March 6, 2017, to the Chinese Patent Office, Application No. 201710129351.6, entitled "A Method and Base Station for Processing Data Services in Long Term Evolution LTE Base Stations", all of which The content is incorporated herein by reference.

Technical field

The embodiments of the present invention relate to the field of communications, and in particular, to a method and a base station for processing data services in a long term evolution LTE base station.

Background technique

In the LTE (Long Term Evolution) system, an RB (Radio Bearer) is a logical channel that carries signaling or data between a base station and a User Equipment (UE).

In an LTE system, an air interface (Uu interface) can be divided into three protocol layers: a physical layer (L1), a data link layer (L2), and a network layer (L3), and in an LTE system, data processing is performed according to an air interface protocol stack. The hierarchy completes the data processing and sending layer by layer.

In the prior art, the patent application CN201180000839.X provides a transmission method for data processing in an LTE system by setting at least one in a PDCP (Packet Data Convergence Protocol) entity of an LTE base station. The queue is buffered to buffer the downlink data of at least one data service to be transmitted via one bearer, and each cache queue has its own priority, and the patent with the application number CN201180000839.X implements the QoS of the LTE system (Quality of Service) ,) Differentiated without shortening the latency of data processing in the LTE system.

In summary, the current transmission method of processing data in the LTE system only realizes the service QoS differentiation, and does not shorten the delay of data processing, so a corresponding solution is urgently needed.

Summary of the invention

The embodiments of the present invention provide a method and a base station for processing data services in a long term evolution LTE base station, which are used to shorten the delay of processing data in the LTE system.

An embodiment of the present invention provides a method for processing a data service in a long term evolution LTE base station, including:

Adding a trigger event to at least one event queue preset in the LTE base station, where the trigger event includes at least: a bearer entity identifier and the trigger event identifier; The preset condition is that the bearer entity has a data service to be processed;

The processing of the data service is performed on the bearer entity indicated by the trigger event according to the trigger event obtained from the event queue.

Preferably, when the preset condition that meets the adding trigger event is detected, adding a trigger event to at least one event queue preset in the LTE base station, including:

After storing the received data to the corresponding bearer entity according to different bearers, adding a trigger event to at least one event queue preset in the LTE base station; or

In the packet data convergence protocol PDCP, when there is a bearer entity whose data has not been processed in the current transmission time interval TTI, a trigger event is added to at least one event queue preset in the LTE base station; or

In the radio link RLC, when there is a bearer entity whose data has not been processed in the current transmission time interval TTI, a trigger event is added to at least one event queue preset in the LTE base station; or

When there is a bearer entity that needs to perform data switching processing in the handover process, a trigger event is added to at least one event queue preset in the LTE base station; or

When there is a bearer entity that needs to perform data processing in the re-establishment process, a trigger event is added to at least one event queue preset in the LTE base station.

Preferably, each event queue has its own priority;

When a trigger event is added, a trigger event is added to the event queue according to the priority of each event queue;

When the trigger event is processed, the event queue to be processed is selected according to the priority of each event queue.

Preferably, the processing of the data service by the bearer entity indicated by the triggering event according to the triggering event obtained from the event queue includes:

Determining, according to the trigger event identifier in the event queue, a trigger event corresponding to the trigger event identifier;

Determining, by the triggering event, the bearer entity identifier corresponding to the triggering event, and processing data stored in the bearer entity corresponding to the bearer entity identifier.

Preferably, after performing the data service processing on the bearer entity indicated by the triggering event, the method further includes:

The trigger event is deleted in the event queue.

The embodiment of the invention provides a long-term evolution LTE base station, including:

And a adding module, configured to add a trigger event to at least one event queue preset in the LTE base station, where the trigger event includes at least: a bearer entity identifier and the Triggering an event identifier; the preset condition is that the bearer entity has a data service to be processed;

The processing module is configured to perform data service processing on the bearer entity indicated by the trigger event according to the trigger event obtained from the event queue.

Preferably, the adding module is specifically configured to:

Preferably, each event queue has its own priority;

Preferably, the processing module is specifically configured to:

Preferably, the processing module is further configured to:

After performing the processing of the data service on the bearer entity indicated by the triggering event, the triggering event is deleted in the event queue.

The embodiment of the present application further provides a long-term evolution LTE base station, including: a memory in which at least one processor, a transceiver, and the at least one processor are communicatively connected;

The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform in a long term evolution LTE base station of an embodiment of the present application A method of processing data services.

The embodiment of the present application further provides a non-volatile computer storage medium storing computer-executable instructions for causing the computer to execute claim 1 A method of processing data traffic in a Long Term Evolution (LTE) base station according to any of the preceding claims.

The embodiment of the present application further provides a computer program product, the computer program product comprising a computing program stored on a non-volatile computer storage medium, the computer program comprising the computer executable instructions, when the computer is The method of causing the computer to perform the processing of data traffic in a Long Term Evolution LTE base station according to any one of claims 1-5 when the execution of the instructions is performed by a computer.

The method and the base station for processing a data service in a long term evolution LTE base station provided by the foregoing embodiment include: adding, when a preset condition that matches an add trigger event is detected, adding to at least one event queue preset in the LTE base station a triggering event, the triggering event includes at least: a bearer entity identifier and a triggering event identifier; the preset condition is that the bearer entity has a data service to be processed; and then, according to the triggering event obtained from the event queue, the triggering event is indicated The bearer entity processes the data service. It can be seen that only the trigger event is obtained from the event queue, and the data service processing can be performed on the bearer entity indicated by the trigger event, instead of traversing all the bearer entities when processing the data, so as to reach the data in the bearer entity. Processing is performed to reduce the time spent traversing different bearer entities. Therefore, data processing delay can be shortened, thereby improving system performance.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present invention, Those skilled in the art can also obtain other drawings based on these drawings without paying for inventive labor.

FIG. 1 is a schematic flowchart of a method for processing a data service in a long term evolution LTE base station according to an embodiment of the present disclosure;

2 is a schematic flowchart of a method for performing data service processing on a bearer entity indicated by a trigger event according to an embodiment of the present invention;

FIG. 3 is a schematic structural diagram of a long-term evolution LTE base station according to an embodiment of the present disclosure;

FIG. 4 is a schematic structural diagram of a long-term LTE base station according to an embodiment of the present application.

detailed description

The present invention will be further described in detail with reference to the accompanying drawings, in which . All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

In the embodiment of the present invention, the term "base station" includes but is not limited to a node, a station controller, an access point (AP), or any other type of interface device capable of working in a wireless environment.

Embodiments of the invention describe various aspects in connection with a terminal and/or a base station. A terminal, a device that provides voice and/or data connectivity to a user, including a wireless terminal or a wired terminal. The wireless terminal can be a handheld device with wireless connectivity, or other processing device connected to a wireless modem, and a mobile terminal that communicates with one or more core networks via a wireless access network. For example, the wireless terminal can be a mobile phone (or "cellular" phone) and a computer with a mobile terminal. As another example, the wireless terminal can also be a portable, pocket, handheld, computer built-in or in-vehicle mobile device. For another example, the wireless terminal can be part of a mobile station, an access point, or a user equipment (UE).

FIG. 1 exemplarily illustrates a method for processing data services in a long term evolution LTE base station according to an embodiment of the present invention. As shown in FIG. 1, the method may include:

S101. Add a triggering event to at least one event queue that is preset in the LTE base station, where the triggering event includes at least: a bearer entity identifier and the trigger event identifier. The preset condition is that the bearer entity has a data service to be processed.

S102: Perform data service processing on the bearer entity indicated by the trigger event according to the trigger event obtained from the event queue.

Wherein, multiple event queues may be set in advance in the LTE base station, and priority is set for each event queue. For example, four event queues may be set in advance in the LTE base station, and the event queues 1, event queues 2, event queues 2, and event queues 4 may be assumed. The priority of event queue 3 and event queue 4 are set to 4, 3, 2, and 1, respectively, where 4 is the highest priority and 1 is the lowest priority.

When multiple event queues are set in the LTE base station and priority is set for each event queue, when a trigger event is added to the event queue, a trigger may be added to the event queue according to the priority of each event queue. Event; when processing the trigger event in the event queue, according to the priority of each event queue, first select the event queue to be processed, and after selecting the event queue, obtain the trigger event from the selected event queue, and The bearer entity indicated by the obtained trigger event performs data service processing.

Optionally, the trigger event added to the event queue may further include: a trigger event identifier, a terminal identifier, a cell identifier, and a bearer entity identifier.

In the foregoing step S101, when a preset condition that meets the adding trigger event is detected, adding a trigger event to at least one event queue preset in the LTE base station may include, but is not limited to, the following situations:

Situation one

After storing the received data to the corresponding bearer entity according to different bearers, a trigger event is added to at least one event queue preset in the LTE base station.

The case of adding a trigger event described in the above scenario 1 is explained in detail below by a specific example.

For example, suppose that the downlink event queue set in the base station A is QA, and further assume that the network side sends the data packet 1 for the UE1 to the bearer entity DRB1 (Data Radio Bearer) in the base station A, and then on the network side After the data packet 1 of the UE1 is sent to the bearer entity DRB1 of the base station A, the trigger event 11 may be added to the downlink event queue QA of the base station A, and the added trigger event 11 may include: the identifier of the trigger event 11, the identifier of the UE1, The identifier of the base station A, which carries the identifier of the entity DRB1.

Then, in the PDCP entity of the base station A, the trigger event 11 is directly removed from the event queue QA, and the trigger event 11 is triggered, that is, the PDCP processes the data stored in the DRB1, and then the processed data is sent. To the RLC entity, data can be processed in the bearer entity, which reduces the time taken by the PDCP entity to traverse different bearer entities. Therefore, the data processing delay can be shortened, thereby improving system performance.

Situation 2

In the packet data convergence protocol PDCP entity, when there is a bearer entity whose data has not been processed within the current transmission time interval (TTI), a trigger event is added to at least one event queue preset in the LTE base station. .

The following is a detailed explanation of the case where the trigger event is added as described in the second case by a specific example.

For example, suppose that the downlink event queue set in the base station B is QB, and further assume that the network side transmits the data packet 2 for the UE2 to the bearer entity DRB8 of the base station B, and then sends the data packet 2 for the UE2 to the network side to the network side. After the bearer entity DRB8 of the base station B, the triggering event 21 can be added to the downlink event queue QB of the base station B, and the added triggering event 21 can include: the identifier of the triggering event 21, the identifier of the UE2, the identifier of the base station B, and the bearer entity DRB8. Logo.

Then, in the PDCP entity of the base station B, the trigger event 21 is directly removed from the event queue QB, and the trigger event 21 is triggered, that is, the PDCP entity processes the data stored in the DRB8.

It is assumed that the PDCP entity of the base station B does not process the data stored in the bearer entity DRB8 within one transmission time interval TTI when the data stored in the bearer entity DRB8 is encrypted and header compressed, and may continue to the base station B at this time. The trigger event 22 is continuously added to the downlink event queue QB, and the added trigger event 22 may include: an identifier of the trigger event 22, an identifier of the UE2, an identifier of the base station B, and an identifier of the bearer entity DRB8.

Then, in the PDCP entity of the base station B, the triggering event 22 is directly removed from the event queue QB, and the triggering event 22 is triggered, that is, the PDCP entity encrypts and compresses the data stored in the DRB8, and so on. The PDCP entity of the base station B processes the data stored in the DRB8, and then sends the processed data to the RLC (Radio Link Control) entity of the base station B, so that data can be obtained in the bearer entity. The processing is performed, which reduces the time taken by the PDCP entity to traverse different bearer entities. Therefore, the data processing delay can be shortened, thereby improving system performance.

Situation three

In the radio link RLC entity, when there is a bearer entity whose data has not been processed in the current transmission time interval TTI, a trigger event is added to at least one event queue preset in the LTE base station.

The following is a detailed explanation of the case where the trigger event is added as described in the third case above through a specific example.

For example, if the downlink event queue set in the base station C is QC, and further assume that the network side transmits the data packet 3 for the UE3 to the bearer entity DRB8 of the base station C, the data packet 3 for the UE3 is sent to the network side to the network side. After the bearer entity DRB8 of the base station C, the triggering event 31 can be added to the downlink event queue QC of the base station C, and the added triggering event 31 can include: the identifier of the triggering event 31, the identifier of the UE3, the identifier of the base station C, and the bearer entity DRB8. Logo.

Then, in the PDCP entity of the base station C, the trigger event 31 is directly removed from the event queue QB, and the trigger event 31 is triggered, that is, the PDCP entity processes the data stored in the DRB8, and then processes the processed data. The RLC entity destined for the base station C is sent to the MAC entity of the base station C after being segmented or concatenated by the RLC entity of the base station C.

It is assumed that the RLC entity of the base station C does not process the data stored in the bearer entity DRB8 within one transmission time interval TTI when segmenting or cascading the data stored in the bearer entity DRB8, and then can continue to the base station at this time. The trigger event 32 is added to the downlink event queue QC of C, and the added trigger event 32 may include the identifier of the trigger event 32, the identifier of the UE3, the identifier of the base station C, and the identifier of the bearer entity DRB8.

Then, in the RLC entity of the base station C, the trigger event 32 is directly removed from the event queue QC, and the trigger event 32 is triggered, that is, the RLC entity segments or cascades the data stored in the DRB8, so that the loop After the RLC entity of the base station C processes the data stored in the DRB8, and then sends the processed data to the MAC entity, the data can be processed in the bearer entity, and the RLC entity is reduced by traversing different bearer entities. The time spent, therefore, can shorten the data processing delay, thereby improving the performance of the system.

Situation four

When there is a bearer entity that needs to perform data switching processing in the handover process, a trigger event is added to at least one event queue preset in the LTE base station.

For the sake of simplicity of description, the case of adding a trigger event described in the above case 4 is explained in detail below by the switching process.

It is assumed that the UE4 is switched from the base station S to the base station P, and it is further assumed that there are eight DRBs in the base station S, namely, DRB1S, DRB2S, DRB3S, DRB4S, DRB5S, DRB6S, DRB7S, and DRB8S, and it is assumed that the uplink event queue of the base station S is on the QS. The downlink event queue of the base station S is under the QS.

It is further assumed that there are eight DRBs in the base station P, namely: DRB1P, DRB2P, DRB3P, DRB4P, DRB5P, DRB6P, DRB7P, and DRB8P, and it is assumed that the uplink event queue of the base station P is on the QP, and the downlink event queue of the base station P is the QP. under.

When the UE4 is handed over from the base station S to the base station P, it is assumed that the downlink data of the base station S for the UE4 is stored in the DRB1S, and the data stored in the DRB1S in the base station S needs to be switched to the DRB1P of the base station P.

At this time, the trigger event 41 may be added to the downlink event queue of the source base station S for the QS, and the event 41 may be triggered. The trigger event 41 is: the identifier of the trigger event 41, the identifier of the UE4, the identifier of the source base station S, and the DRB1S. Logo.

In the case that the UE4 is handed over from the base station S to the base station P, the PDCP and the RLC are re-established in the process of configuring the forwarding tunnel for the source base station S, and the RLC can be sent to the source base station S when the uplink data in the DRB2S is not processed. A trigger event 42 is added to the uplink event queue QS. The triggering event 42 includes: an identifier of the triggering event 42, an identifier of the UE4, an identifier of the source base station S, and an identifier of the DRB2S.

In the case that the UE4 is handed over from the base station S to the base station P, the source base station S can also quickly add new and old data to the QS by adding a trigger event to the downlink event queue, so that when switching or retransmitting, The data is processed in the bearer entity, which reduces the time taken by the source base station or the target base station to traverse different bearer entities. Therefore, the data processing delay can be shortened, thereby improving system performance. The data that has not been sent to the user or has been sent to the user after being switched by the PDCP entity of the base station during the handover, but the part of the data that has not been acknowledged by the user may be referred to as old data; The base station, and the part of the data that the base station's PDCP entity can handle in the future, can be called new data.

In addition, in the case that the UE4 is handed over from the base station S to the base station P, for the target base station, the UE accesses the target base station, but when the PDCP SN of the target base station is not configured yet, the UE can be added under the downlink event queue QP of the target base station P. The triggering event is added, and when the target base station processes the downlink switching data or processes the uplink switching data, or the switching queue data has not been processed, the triggering event addition trigger may be added to the downlink event queue QP of the target base station P or the uplink event queue QP. The event is processed until the switching queue data is processed.

In the case that the UE4 is handed over from the base station S to the base station P, in the DRB3S of the source base station S, the new data is switched from the network side to the source base station S. In this case, in the downlink event queue of the source base station S. Add trigger event 43.

Situation five

In the above step S102, when the data service is processed by the bearer entity indicated by the trigger event according to the trigger event acquired from the event queue, the process may be performed by the method flow shown in FIG. 2.

S201. Acquire a trigger event from an event queue.

S202. Determine, according to the trigger event identifier in the event queue, a trigger event corresponding to the trigger event identifier.

S203. Determine, according to the trigger event corresponding to the trigger event identifier, the bearer entity identifier corresponding to the trigger event.

S204: Process data stored in the bearer entity corresponding to the bearer entity identifier according to the bearer entity identifier corresponding to the triggering event.

Optionally, in order to further shorten the processing delay and improve the processing speed of the data, after the data stored in the bearer entity corresponding to the bearer entity identifier is processed, the trigger event may also be deleted in the event queue.

It should be noted that the triggering event in the event queue in the embodiment of the present invention may be applied to the PDCP entity, or may be applied to the RLC entity, and may also be applied to any execution entity that needs to traverse the bearer entity when processing data.

According to the above, it can be seen that only the trigger event is obtained from the event queue, and the data service processing can be performed on the bearer entity indicated by the trigger event, instead of traversing all the bearer entities when processing the data, thereby reaching the bearer entity. The data is processed in the process, which reduces the time spent traversing different bearer entities. Therefore, the data processing delay can be shortened, thereby improving the performance of the system.

Based on the same technical concept, the embodiment of the present invention further provides a long-term evolution LTE base station. As shown in FIG. 3, the base station may include:

The adding module 301 is configured to add a trigger event to at least one event queue preset in the LTE base station, where the trigger event includes at least: a bearer entity identifier and a The trigger event identifier; the preset condition is that the bearer entity has a data service to be processed;

The processing module 302 is configured to perform data service processing on the bearer entity indicated by the trigger event according to the trigger event obtained from the event queue.

Preferably, the module 301 is added, specifically for:

Preferably, each event queue has its own priority;

Preferably, the processing module 302 is specifically configured to:

Preferably, the processing module 302 is further configured to:

In summary, a method and a base station for processing a data service in a long term evolution LTE base station according to an embodiment of the present invention include: when detecting a preset condition that meets an add trigger event, at least one preset in an LTE base station A triggering event is added to the event queue, where the triggering event includes at least: a bearer entity identifier and a triggering event identifier; the preset condition is that the bearer entity has a data service to be processed; and then according to the triggering event obtained from the event queue, The bearer entity that triggered the event indication performs data service processing. It can be seen that only the trigger event is obtained from the event queue, and the data service processing can be performed on the bearer entity indicated by the trigger event, instead of traversing all the bearer entities when processing the data, so as to reach the data in the bearer entity. Processing is performed to reduce the time spent traversing different bearer entities. Therefore, data processing delay can be shortened, thereby improving system performance.

It is worth mentioning that each module involved in the above embodiments is a logic module. In practical applications, a logic module may be a physical module, a part of a physical module, or multiple physical entities. A combination of modules is implemented. In addition, in order to highlight the innovative part of the present application, the present embodiment does not introduce a module that is not closely related to solving the technical problem proposed by the present application, but this does not indicate that there are no other modules in the present embodiment.

Based on the same inventive concept, the embodiment of the present application further provides a long term evolution LTE base station, as shown in FIG. 4, including: at least one processor 400; a transceiver 410; and a memory 420 communicatively coupled to the at least one processor 400. The steps performed by the various functional modules in the foregoing embodiments may be performed by a processor in a long-term LTE base station provided by an embodiment of the present invention.

The processor 400 is configured to read a program in the memory 420 and perform the following process:

Adding a trigger event to at least one event queue set in the LTE base station, the trigger event includes at least: a bearer entity identifier and the trigger event identifier; The preset condition is that the bearer entity has a data service to be processed;

Optionally, the processor 400 is capable of:

Optionally, each event queue has its own priority, and the processor can also:

Optionally, the processor is capable of:

Optionally, after processing the data service by the bearer entity indicated by the trigger event, the processor is further configured to: delete the trigger event in the event queue.

The transceiver 410 is configured to receive and transmit data under the control of the processor 400.

Wherein, in FIG. 4, the bus architecture can include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 400 and various circuits of memory represented by memory 420. The bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein. The bus interface provides an interface. Transceiver 410 can be a plurality of components, including a transmitter and a receiver, providing means for communicating with various other devices on a transmission medium.

The processor 400 is responsible for managing the bus architecture and general processing, and the memory 420 can store data used by the processor 400 when performing operations.

Optionally, the processor 400 may be a CPU (Central Embedded Device), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a CPLD (Complex Programmable Logic Device). , complex programmable logic devices).

Based on the same inventive concept, the present application provides a non-transitory computer storage medium storing computer-executable instructions for causing the computer to perform the above A method of processing data traffic in a Long Term Evolution LTE base station in any of the embodiments.

Based on the same inventive concept, the present application provides a computer program product comprising a computing program stored on a non-transitory computer readable storage medium, the computer program comprising the computer executable instructions When the computer executable instructions are executed by a computer, the computer is caused to perform the method of processing data traffic in a Long Term Evolution LTE base station in any of the above embodiments.

The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located A place, or it can be distributed to multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment. Those of ordinary skill in the art can understand and implement without deliberate labor.

Through the description of the above embodiments, those skilled in the art can clearly understand that the various embodiments can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware. Based on such understanding, the above-described technical solutions may be embodied in the form of software products in essence or in the form of software products, which may be stored in a computer readable storage medium such as ROM/RAM, magnetic Discs, discs, etc., include instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments or portions of the embodiments.

Those skilled in the art will appreciate that embodiments of the present invention can be provided as a method, or a computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.

The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (system), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.

The computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

While the preferred embodiment of the invention has been described, it will be understood that Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and the modifications and

It is apparent that those skilled in the art can make various modifications and variations to the invention without departing from the spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and modifications of the invention

Claims

A method for processing a data service in a long term evolution LTE base station, comprising:

Adding a trigger event to at least one event queue set in the LTE base station, the trigger event includes at least: a bearer entity identifier and the trigger event identifier; The preset condition is that the bearer entity has a data service to be processed;

The processing of the data service is performed on the bearer entity indicated by the trigger event according to the trigger event obtained from the event queue.
The method of claim 1, wherein the triggering event is added to at least one event queue preset in the LTE base station, when the preset condition of the triggering event is detected, including:

After storing the received data to the corresponding bearer entity according to different bearers, adding a trigger event to at least one event queue preset in the LTE base station; or

In the packet data convergence protocol PDCP, when there is a bearer entity whose data has not been processed in the current transmission time interval TTI, a trigger event is added to at least one event queue preset in the LTE base station; or

In the radio link RLC, when there is a bearer entity whose data has not been processed in the current transmission time interval TTI, a trigger event is added to at least one event queue preset in the LTE base station; or

When there is a bearer entity that needs to perform data switching processing in the handover process, a trigger event is added to at least one event queue preset in the LTE base station; or

When there is a bearer entity that needs to perform data processing in the re-establishment process, a trigger event is added to at least one event queue preset in the LTE base station.
The method of claim 1 wherein each event queue has a respective priority;

When a trigger event is added, a trigger event is added to the event queue according to the priority of each event queue;

When the trigger event is processed, the event queue to be processed is selected according to the priority of each event queue.
The method according to claim 1, wherein the processing of the data service by the bearer entity indicated by the triggering event according to the triggering event obtained from the event queue comprises:

Determining, according to the trigger event identifier in the event queue, a trigger event corresponding to the trigger event identifier;

Determining, by the triggering event, the bearer entity identifier corresponding to the triggering event, and processing data stored in the bearer entity corresponding to the bearer entity identifier.
The method of claim 1, after the processing of the data service by the bearer entity indicated by the triggering event, further comprising:

The trigger event is deleted in the event queue.
A long-term evolution LTE base station, comprising:

And a adding module, configured to add a trigger event to at least one event queue preset in the LTE base station, where the trigger event includes at least: a bearer entity identifier and the Triggering an event identifier; the preset condition is that the bearer entity has a data service to be processed;

The processing module is configured to perform data service processing on the bearer entity indicated by the trigger event according to the trigger event obtained from the event queue.
The base station according to claim 6, wherein the adding module is specifically configured to:

After storing the received data to the corresponding bearer entity according to different bearers, adding a trigger event to at least one event queue preset in the LTE base station; or

In the packet data convergence protocol PDCP, when there is a bearer entity whose data has not been processed in the current transmission time interval TTI, a trigger event is added to at least one event queue preset in the LTE base station; or

In the radio link RLC, when there is a bearer entity whose data has not been processed in the current transmission time interval TTI, a trigger event is added to at least one event queue preset in the LTE base station; or

When there is a bearer entity that needs to perform data switching processing in the handover process, a trigger event is added to at least one event queue preset in the LTE base station; or

When there is a bearer entity that needs to perform data processing in the re-establishment process, a trigger event is added to at least one event queue preset in the LTE base station.
The base station according to claim 6, wherein each event queue has a respective priority;

When a trigger event is added, a trigger event is added to the event queue according to the priority of each event queue;

When the trigger event is processed, the event queue to be processed is selected according to the priority of each event queue.
The base station according to claim 6, wherein the processing module is specifically configured to:

Determining, according to the trigger event identifier in the event queue, a trigger event corresponding to the trigger event identifier;

Determining, by the triggering event, the bearer entity identifier corresponding to the triggering event, and processing data stored in the bearer entity corresponding to the bearer entity identifier.
The base station according to claim 6, wherein the processing module is further configured to:

After performing the processing of the data service on the bearer entity indicated by the triggering event, the triggering event is deleted in the event queue.
A long term evolution LTE base station, comprising: a memory in which at least one processor, a transceiver, and the at least one processor are communicatively coupled;

The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

Adding a trigger event to at least one event queue set in the LTE base station, the trigger event includes at least: a bearer entity identifier and the trigger event identifier; The preset condition is that the bearer entity has a data service to be processed;

The data entity is processed by the bearer entity indicated by the trigger event according to the trigger event obtained from the event queue.
The base station of claim 11 wherein said processor is capable of:

After storing the received data to the corresponding bearer entity according to different bearers, adding a trigger event to at least one event queue preset in the LTE base station; or

In the packet data convergence protocol PDCP, when there is a bearer entity whose data has not been processed in the current transmission time interval TTI, a trigger event is added to at least one event queue preset in the LTE base station; or

In the radio link RLC, when there is a bearer entity whose data has not been processed in the current transmission time interval TTI, a trigger event is added to at least one event queue preset in the LTE base station; or

When there is a bearer entity that needs to perform data switching processing in the handover process, a trigger event is added to at least one event queue preset in the LTE base station; or

When there is a bearer entity that needs to perform data processing in the re-establishment process, a trigger event is added to at least one event queue preset in the LTE base station.
The base station of claim 11 wherein each event queue has a respective priority and said processor is further capable of:

When a trigger event is added, a trigger event is added to the event queue according to the priority of each event queue;

When the trigger event is processed, the event queue to be processed is selected according to the priority of each event queue.
The base station of claim 11 wherein said processor is capable of:

Determining, according to the trigger event identifier in the event queue, a trigger event corresponding to the trigger event identifier;

Determining, by the triggering event, the bearer entity identifier corresponding to the triggering event, and processing data stored in the bearer entity corresponding to the bearer entity identifier.
The base station according to claim 11, wherein after the processing of the data service by the bearer entity indicated by the triggering event, the processor is further capable of: deleting the triggering event in the event queue.
A non-volatile computer storage medium, characterized in that the non-volatile computer storage medium stores computer-executable instructions for causing the computer to perform any of claims 1-5 A method of processing data traffic in a Long Term Evolution (LTE) base station as described in the section.
A computer program product, comprising: a computing program stored on a non-volatile computer storage medium, the computer program comprising the computer executable instructions, when the computer executable instructions are The computer, when executed, causes the computer to perform the method of processing data traffic in a Long Term Evolution LTE base station according to any of claims 1-5.