WO2017211276A1

WO2017211276A1 - Entity management method, mac entity, system, and computer storage medium

Info

Publication number: WO2017211276A1
Application number: PCT/CN2017/087344
Authority: WO
Inventors: 孙军帅; 王莹莹; 黄学艳; 陈卓; 易芝玲
Original assignee: 中国移动通信有限公司研究院; 中国移动通信集团公司
Priority date: 2016-06-07
Filing date: 2017-06-06
Publication date: 2017-12-14

Abstract

Disclosed in the present application are an entity management method, fast control media access control (MAC) entity, system, and storage medium. The method comprises: a fast control MAC entity determines a scheduling instruction for at least one real-time MAC entity; and the fast control MAC entity sends the scheduling instruction to the at least one real-time MAC entity.

Description

Entity management method, MAC entity, system and computer storage medium

Cross-reference to related applications

The present application is filed on the basis of the Chinese Patent Application No. 201610403739.6, filed on Jun.

The present application is filed on the basis of the Chinese Patent Application No. PCT Application No.

The present application is filed on the basis of the Chinese Patent Application No. PCT Application No. No.

Technical field

The present application relates to entity management technologies in the field of communications, and in particular, to an entity management method, a fast control medium access control (MAC) entity and system, and a computer storage medium.

Background technique

For the requirements of 5G, the access network protocol stack scheme shown in Figure 1a, 1b is proposed. The control plane is Radio Resource Control (RRC) and the user plane is Packet Data Convergence Protocol (PDCP). / Radio Link Layer Control Protocol (RLC) / Media Access Control (MAC) / Physical (PHY). The following new definitions have been made for the distributed network architecture: the new intra-cell (Inter Cell) MAC function module is added, and the real-time control is higher than the RRC control; the new data sorting and control (DRC, Data Reordering & Control) function module is in charge of the radio bearer. (RB, Radio Bearer) data distribution and reception And RLC center/RLC remote control; RRC adds air interface signaling function, and flexibly configures PDCP/RLC or DRC functions according to different access network architectures to adaptively and ideally and non-ideal access network architecture. However, the above architecture cannot guarantee fast related control processing through air interface signaling.

Summary of the invention

In view of this, the purpose of the present application is to provide an entity management method, a fast control MAC entity, and a system, which can at least solve the above problems existing in the prior art.

In order to achieve the above object, the technical solution of the present application is implemented as follows:

The application provides an entity management method, the method comprising:

The fast control MAC entity determines a scheduling instruction for the at least one real-time MAC entity;

The fast control MAC entity sends the scheduling instruction to the at least one real-time MAC entity.

The application also provides a fast control MAC entity, including:

An instruction generating unit, configured to determine a scheduling instruction for the at least one real-time MAC entity;

And an information sending unit, configured to send the scheduling instruction to the at least one real-time MAC entity.

The application also provides an entity management system, the system comprising: a fast control MAC entity and at least one real-time MAC entity; wherein

Quickly controlling a MAC entity, configured to determine a scheduling instruction for the at least one real-time MAC entity; transmitting the scheduling instruction to the at least one real-time MAC entity;

a real-time MAC entity, configured to receive a scheduling instruction sent by the fast control MAC entity, and process according to the scheduling instruction.

The application also provides a fast control MAC entity, comprising: a processor and a memory for storing a computer program capable of running on the processor,

Wherein the processor is configured to perform the method described above when the computer program is executed step.

The present application also provides a storage medium having stored thereon a computer program, wherein the computer program is executed by a processor to implement the steps of the foregoing method.

The present application provides an entity management method, a fast control MAC entity, a system, and a storage medium. The MAC protocol entity can be divided into two types, namely, a fast control MAC entity and at least one real-time MAC entity, and is targeted by the fast control MAC entity. At least one real-time MAC entity performs scheduling. Therefore, the scheduling and control of the at least one MAC entity can be completed at the MAC layer, thereby ensuring the rapid completion of the air interface signaling and improving the processing speed of the overall architecture.

DRAWINGS

Figure 1a is a schematic diagram 1 of a structure between protocol entities in the prior art;

Figure 1b is a schematic diagram 2 of the structure between the protocol entities in the prior art;

Figure 2a is a schematic flow chart 1 of the entity management method of the present application;

2b is a schematic flowchart 2 of the entity management method of the present application;

FIG. 3a is a schematic diagram of functional division of a MAC entity according to an embodiment of the present application;

FIG. 3b is a schematic structural diagram of a setting location of a MAC entity according to an embodiment of the present application;

Figure 4a is a schematic diagram 1 of the structure between the entities of the present application;

Figure 4b is a schematic diagram 2 of the structure between the entities of the present application;

Figure 5a is a schematic diagram 1 of signaling transmission of the present application;

Figure 5b is a schematic diagram 2 of signaling transmission of the present application;

Figure 5c is a schematic diagram 3 of signaling transmission of the present application;

Figure 6a is a schematic diagram 1 of MAC function partitioning;

6b is a schematic diagram 1 of function division of FC-MAC and RT-MAC according to an embodiment of the present application;

FIG. 6c is a schematic diagram 2 of MAC function division;

6d is a schematic diagram 2 of function division of FC-MAC and RT-MAC according to an embodiment of the present application;

7a is a schematic diagram 1 of a structure of a fast control MAC entity according to the present application;

FIG. 7b is a schematic diagram 2 of a structure of a fast control MAC entity according to the present application;

8a is a schematic diagram 3 of the structure of the MAC entity of the fast control of the present application;

FIG. 8b is a schematic diagram 4 of a structure of a fast control MAC entity according to the present application;

9 is a schematic structural diagram 1 of a composition management system of the present application;

10 is a schematic structural diagram 2 of the entity management system of the present application;

Figure 11 is a schematic structural diagram 3 of the entity management system of the present application;

12 is a schematic flow chart of an embodiment of the present application;

13 is a schematic structural diagram of a wireless air interface cell according to the present application;

14 is a schematic diagram 1 of a relationship between a single cell, an air interface, and a user according to the present application;

15 is a schematic diagram 2 of a relationship between a multi-cell, an air interface, and a user according to the present application;

16 is a schematic structural view of an apparatus embodiment of the present application.

detailed description

The present application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

Embodiment 1

The application provides an entity management method, as shown in FIG. 2a, the method includes:

Step 2011: The fast control MAC entity determines a scheduling instruction for the at least one real-time MAC entity;

Step 2012: The fast control MAC entity sends the scheduling instruction to the at least one real-time MAC entity.

This application proposes a total fractional MAC scheme with air interface fast signaling capability for the distributed architecture and air interface feature requirements of the 5G access network and the limitations of the current MAC protocol entity function. The basis of the MAC protocol stack functionality adds new processing capabilities.

The overall scheme of the MAC protocol entity function is shown in Figure 3a. MAC protocol in this embodiment The entity function is divided into two functional modules: a fast control (FC)-MAC entity and a real-time (RT)-MAC entity.

Among them, FC-MAC is divided into three functions: Fast Signaling Control, Flow Control, and RT-MAC Control. RT-MAC is the current or current traditional MAC protocol entity function and its subsequent evolution function.

In order to ensure the compatibility of the protocol stack, the traditional MAC function including the evolution function is uniformly defined as an RT-MAC, and the control for the intra-cell user scheduling, the intra-cell radio resource allocation, the intra-cell user and the radio resource corresponding process is completed. The RT-MAC function only focuses on the corresponding MAC function within the cell.

The FC-MAC function is a new MAC function, and the relationship between the fast signaling (RC)-MAC entity and the RT-MAC entity is: all MAC entities are jointly composed of an FC MAC entity and an RT MAC entity; and the FC MAC entity And there is no intersection between RT MAC entities. The FC-MAC does not change the basic functions of the RT-MAC to ensure full compatibility of the MAC scheme of the total fraction with the original MAC.

Specifically, as shown in FIG. 3a, the FC-MAC mainly includes three major functions: a fast control function that is assumed, that is, a control process that is traditionally performed through RRC signaling, and sinks to the MAC to perform fast control through air interface scheduling. Function; RB flow control function for the user data link, controlling the number of data allocated on the PDCP/DRC/RLC through the air interface information of the user; scheduling control process for the RT-MAC (excluding the signaling control function), the function Emphasis is placed on the scheduling of RT-MACs and the non-signaling control functions required to complete the scheduling.

The various functions of the FC MAC entity and their implementation are specifically described below with reference to FIG. 4a, FIG. 5a, FIG. 5b and FIG. 5c:

The first,

Determining, by the fast control MAC entity, scheduling for the at least one real-time MAC entity Instructions, including at least:

The fast control MAC entity acquires content of the RRC signaling from the radio resource control RRC entity; the fast control MAC entity generates a scheduling instruction for the at least one real-time MAC entity based on the content of the RRC signaling.

Alternatively, the fast control MAC entity may further generate corresponding air interface control according to user behavior (such as the channel quality of the user, the capability of the user, and the service feature required by the user), and then generate a scheduling instruction in combination with the air interface control.

The generating the scheduling instruction for the at least one real-time MAC entity may include: the fast control MAC entity encapsulating the scheduling instruction by using a preset special PDCCH or a defined MAC control element (CE, Control Element) .

Specifically, for example, referring to FIG. 4a, the fast control MAC entity performs the RRC protocol signaling function, including: the signaling function of the original RRC protocol entity needs to implement fast control and sink to the MAC.

The RRC signaling includes, but is not limited to, air interface switching signaling and/or radio link reconfiguration signaling, and other signaling control for the physical link, such as a change of the air interface format and a change of the air interface physical channel.

That is to say, by sinking the relevant signaling of the air interface handover to the fast control MAC entity, the original control by RRC air interface signaling can now send a special PDCCH or a defined MAC control element (CE) through the FC-MAC. , Control Element) for quick control.

For example, in order to implement seamless switching of the air interface, the FC-MAC sends link control signaling to replace the radio link reconfiguration signaling of the original RRC protocol entity.

Further, in conjunction with FIG. 5a, a description is given of a signaling procedure for RRC sinking, that is, packaging the information acquired at the RRC entity, and generating a scheduling instruction to be sent to the RT-MAC entity.

Step 51-1: The RRC entity of the base station (Base Station) decides according to the corresponding algorithm, and needs to generate corresponding signaling, and generates FC-MAC transmission control information (Control Indication) sent to the Base Station according to the signaling, and only the Control Indication in the Control Indication The specific content of the specific signaling is included, and the content of the signaling is clearly defined, and the binary stream of the format (ASN.1 format) that does not need to be converted into RRC air interface signaling is not required. The generated signaling may be a specified signaling that needs to be sinked, for example, the related signaling of the air interface switching in the above example, and the related signaling of the seamless handover. In addition, the specific signaling is only an example, and the actual During the processing, you can set it according to actual needs.

Step 51-2: The FC-MAC of the Base Station generates a scheduling instruction according to the control information sent by the RRC of the Base Station, and further sends a scheduling instruction (Scheduling Ind) to the RT-MAC, and indicates the RT-MAC of the Base Station by using the scheduling instruction. Sending control information air interface signaling to the corresponding terminal device. Here, it should be noted that, in this step, in addition to the above-described control information, the scheduling instruction may be combined with the feature information of the terminal device and the load of the RT-MAC entity to generate a corresponding scheduling instruction. For details on how to generate a scheduling instruction in combination with other information, refer to the description of other functions in this embodiment, and no further details are provided herein.

So far, the fast processing between the MAC function and the RT MAC entity of the first function described above is completed.

The interaction process between the RT-MAC entity and the terminal device side is further described below in conjunction with FIG. 5a:

Step 51-3: The RT-AMC on the base station side determines, according to the foregoing scheduling information, control information to be sent to the terminal device (UE), and generates a data packet, and further performs information transmission data packets with the UE, so that the UE-side RT-MAC The air interface HARQ process of the MAC is started, and the data packet is sent and received and confirmed.

Step 51-4: After the RT-MAC of the UE correctly receives the MAC packet (Packet), The data packet is parsed to obtain control information, and the control information is reported to the FC-MAC entity on the UE side.

Step 51-5: After receiving the reporting control information, the FC-MAC of the UE completes the corresponding operation according to the control information, and sends an application for application control information (Control Apply) to the RRC of the UE to apply for signaling authorization of the RRC. .

Step 51-6: The RRC of the UE sends feedback information of the control information (Control Indication) to the FC-MAC of the UE, that is, the authorization information is sent to the FC-MAC.

Step 51-7: The FC-MAC of the UE sends feedback information of the control information to the RT-MAC of the UE to indicate the signaling process.

Step 51-8: The RT-MAC of the UE uses the HARQ process of the MAC to complete the signaling of the air interface for signaling transmission.

Step 51-9: After receiving the confirmation of the RT-MAC of the Base Station, the FC-MAC sends an acknowledgement information (Scheduling ACK) for the scheduling information to confirm.

Step 51-10: The FC-MAC of the Base Station sends a control information confirmation control information confirmation Control ACK to the RRC of the Base Station, and confirms that the air interface signaling process ends.

Step 51-11: The RT-MAC of the UE sends a control information confirmation control acknowledgement message Control ACK to the FC-MAC of the UE, indicating that the signaling process air interface transmission is successful.

Step 51-12: The FC-MAC of the UE sends a control acknowledgement Control ACK to the RRC of the UE, indicating that the signaling process is completed.

Second,

The fast control medium access control MAC entity determines a scheduling instruction for the at least one real-time MAC entity, and includes at least:

Obtaining a processing load and a spatial coverage condition of the at least one real-time MAC entity, and a feature parameter of the terminal device; and the terminal is based on a processing load of the at least one real-time MAC entity and a spatial coverage condition and a feature parameter of the terminal device Device allocation target in real time The MAC entity as a first allocation result; generating a scheduling instruction for the target real-time MAC entity based at least on the first allocation result.

The real-time MAC entity is used in this function for real-time mapping scheduling control of cell-level and user-level signaling/data carried.

Specifically, the processing load and the spatial coverage of the at least one real-time MAC entity and the characteristic parameters of the terminal device may be:

Acquiring processing load, corresponding spatial coverage in at least one real-time MAC entity that is managed by itself, and acquiring various air interface feature parameters, cell feature parameters, such as air interface quality, neighboring air interface quality, and moving direction reported by at least one terminal device And user feature parameters.

Assigning the target real-time MAC entity to the terminal device as the first allocation result may be: assigning a corresponding target real-time MAC entity to each of the at least one terminal device, and using the allocated target real-time MAC entity as each of the foregoing The first allocation result corresponding to the terminal device.

It can be understood that, in this function, at least one terminal device may be multiple; further, each terminal device may be a terminal device that has selected a target cell to which it is to be accessed; that is, this function The method is mainly for selecting a corresponding target real-time MAC entity for at least one terminal device in the cell.

Specifically, the method for selecting the target real-time MAC entity for the terminal device may be a combination of the cell served by each real-time MAC entity, the service type of the supported terminal device, and the current load of the real-time MAC entity, and then combined with the terminal device. The quality of the air interface, the quality of the air interface in the neighboring area, and the direction of movement, select the appropriate RT-MAC for each user to send and receive data.

In addition, in the implementation of the function, the number of the terminal devices that determine the bearer of each real-time MAC entity and the type of the carried service may also be included, as follows:

The fast control medium access control MAC entity determines a scheduling instruction for the at least one real-time MAC entity, and at least further includes:

Obtaining a processing load and a spatial coverage condition of the at least one real-time MAC entity, and a feature parameter of the terminal device;

Determining, for each of the at least one real-time MAC entity, the number of terminal devices and/or supported by the real-time MAC entity of the at least one real-time MAC entity based on a processing load of the at least one real-time MAC entity and a spatial coverage condition and a characteristic parameter of the terminal device business type;

The number of terminal devices carried by the at least one real-time MAC entity and/or the type of service supported are used as scheduling instructions.

That is to say, if the current RT-MAC entity has a large load, it is determined that the number of users that it can carry is small, and vice versa. Further, if the load of an RT-MAC entity is large, it can be allocated a service type for carrying a small load demand. Therefore, it is possible to select a reasonable number of users or user service types for each RT-MAC (to ensure the QoS requirements of the service).

For the connection between the MAC entity and the real-time MAC entity, the connection between the MAC function and the real-time MAC entity can be seen in Figure 4a. Through the above functions, the control of the bidirectional dynamic real-time mapping between the user, that is, the terminal device and the real-time MAC entity, by the fast control MAC can be realized.

Third,

The fast control medium access control MAC entity determines a scheduling instruction for the at least one real-time MAC entity, and further includes:

Determining, for each of the at least one real-time MAC entity, a data transmission type; wherein the data transmission type comprises a data transmission of a control plane, and/or a data transmission of a user plane;

Generating the scheduling instruction based on a data transmission type corresponding to the at least one real-time MAC entity.

Specifically, for example, see FIG. 4a, dynamic scheduling control of the RT-MAC real-time function. According to the overall control of RRC signaling (RRC through signaling configuration function optional set, MAC is The function set selects a specific function for the RT-MAC), and performs scheduling control on the RT-MAC function, including whether to perform only the control plane (Control Plane) or the user plane (User Plane) corresponding data to be sent or received, or at the same time, the Control can be performed. Send and receive data of Plane and User Plane.

Fourth,

The fast control MAC entity selects an air interface bearer mode for the terminal device;

The fast control MAC entity generates a scheduling instruction for the target real-time MAC entity of the terminal device based on the air interface bearer mode selected by the terminal device.

Specifically, the fast control MAC entity selects an air interface bearer mode for the terminal device, and the determining manner may be: using various measurement information of each terminal device reported by the RT-MAC and the physical layer (PHY), The measurement information of the terminal device accurately senses the transmission resource requirement of each terminal device in the air interface; acquires the content of the signaling of the RRC entity; combines the transmission resource requirements of the air interface of each terminal device with the signaling content of the RRC entity, Each terminal device selects an air interface bearer mode.

The content of the signaling of the RRC entity is obtained, and the RRC entity still performs the allocation of the air interface bearer mode for the terminal device, but does not generate the specific signaling, but sends the air interface bearer mode to the fast control MAC entity, which finally makes the fast The control MAC entity generates a scheduling instruction based on its assigned air interface bearer mode. The specific implementation process can be seen in Figure 5a, and details are not described herein.

The selected air interface bearer mode may use the OFDM+CDMA mode to carry user data and signaling, or use non-orthogonal physical layer technology to enable fast data transmission and reception of some users. In this embodiment, the air interface carrying mode of the terminal device is not exhaustive.

Fifth,

The fast control medium access control MAC entity determines scheduling instructions for the at least one real-time MAC entity, including:

The fast control medium access control MAC entity determines a target cell to which the terminal device is to access;

And acquiring, according to the at least one real-time MAC entity corresponding to the target cell, a second allocation result of allocating a target real-time MAC entity to the terminal device, according to the target cell that is accessed by the terminal device;

A scheduling instruction for the target real-time MAC entity is generated based at least on the second allocation result.

The specific manner of obtaining the second allocation result of the target real-time MAC entity for the terminal device may be: performing matching according to the cell served by the real-time MAC entity and the target cell to be accessed by the terminal device, and determining based on the matching result. Target real-time MAC entity.

Further, the allocation of the target real-time MAC entity to the terminal device may also refer to at least one of the foregoing second-fourth functions, that is, the air interface bearer mode of each real-time MAC entity may also be combined. The supported service type, the number of terminal devices that can be carried, and the target cell to be served in this function jointly generate scheduling instructions.

This function is mainly for RRC to add air interface signaling or control procedures in the protocol. According to the classification standard of the LTE system, the foregoing mapping process for determining the cell for the terminal device belongs to the RRC protocol entity according to the classification standard of the LTE system. In the specific implementation, the air interface signaling that should be implemented by the RRC protocol entity is sinked, and the MAC can be directly controlled quickly. In this way, cross-cell control is implemented to further ensure the efficiency of the execution control of the solution.

In addition, the specific processing signaling process and the information interaction process for implementing the above-mentioned new function of sinking the RRC entity can be referred to FIG. 5b, as follows:

About the new fast signaling process:

Step 52-1: The FC-MAC of the base station determines, according to the corresponding decision algorithm, that a fast control process needs to be initiated to generate control signaling corresponding to the fast control process, and the FC-MAC of the Base Station is based on the control of the RT-MAC of the Base Station. The information generates and sends a scheduling instruction Scheduling Ind to instruct the base station's RT-MAC to send the air interface signaling. Further, the generating the scheduling instruction may include, according to the control information generated by the FC-MAC entity itself, a load based on each RT-MAC entity, and an air interface measurement and feature information of each terminal device reported by the physical layer. Wait.

Step 52-2: After receiving the scheduling instruction, the RT-MAC entity of the Base Station generates a packet for the UE peer according to the scheduling instruction and the control information included therein, and then starts an air interface HARQ process of the MAC by the RT-MAC. This packet is sent and received and acknowledged.

Step 52-3: After receiving the MAC data packet Packet, the RT-MAC of the UE sends a report control signaling Control Report to the FC-MAC of the UE.

Step 52-4: After receiving the control report signaling Control Report, the FC-MAC of the UE completes the corresponding operation of the control signaling, and sends a control signaling response to the RT-MAC of the UE, indicating that the signaling is performed. the result of.

Step 52-5: The RT-MAC of the UE uses the HARQ process of the MAC to complete the air interface transmission of the signaling confirmation.

Step 52-6: After the RT-MAC of the Base Station receives the confirmation, it sends an acknowledgement to the FC-MAC.

Step 52-7: The RT-MAC of the UE sends a control acknowledgement Control ACK to the FC-MAC of the UE, indicating that the air interface transmission of the signaling process is successful.

Sixth,

The method further includes:

The fast control MAC entity performs at least one of at least one entity in the data link layer Adjustment of the function.

Specifically, the at least one entity may have at least one of the following functions:

Compression, decompression: header compression and decompression of IP packets;

Security: encryption, decryption or integrity protection of data packets, including maintenance of data packet numbers;

Re-establishment process: data forwarding and in-order delivery;

Packets are sent in order and delivered in order;

Sending segmentation and concatenation of the data packet;

Reassembly of data packets, retransmission (ARQ process), re-segmentation (segment transmission of retransmitted data packets);

Re-establishment process: the out-of-order delivery of data;

Flow control and distribution of multiple RLC or sub-link packets, distributed in FIFO order, and maintaining the SN number of the corresponding data packet;

The ordering of multiple RLC or sub-link data packets, and the data on each sub-link is delivered in order.

Specifically, compression, decompression, header compression and decompression of IP packets; security, encryption, decryption or integrity protection of data packets, including maintenance of packet sequence numbers; re-establishment process, data forwarding and Submit in order; packets are sent in order and delivered in sequence, which can be implemented by PDCP entities in the data link layer.

Packets are sent in order and delivered in order; segmentation and concatenation of transmitted packets; reassembly of data packets, retransmission (ARQ process), re-segmentation (segment transmission of retransmission packets) Re-establishment process: data is delivered in an out-of-order manner, which can be implemented by RLC entities in the data link layer.

The flow control and distribution of multiple RLC or sub-link data packets are distributed according to the FIFO sequence, and the SN number of the corresponding data packet is maintained; the multiple RLC or sub-link data packet is sorted, and the data on each sub-link is sequentially performed. submit. This can be done with a DRC entity in the data link layer.

However, it should be understood that the PDCP entity, the DRC entity, and the RLC entity are only one specific type. The implementation may be implemented by other entities in the implementation, and the entity that specifically implements the foregoing functions is not limited in this embodiment.

The fast control MAC entity performs at least one function adjustment on the PDCP entity;

The fast control MAC entity performs at least one function adjustment on the DRC entity;

The fast control MAC entity performs at least one function adjustment on the RLC entity.

For example, referring to FIG. 4a, the fast control MAC entity establishes a connection with the PDCP entity, the DRC entity, and the RLC entity, and performs functional adjustment on the foregoing entities based on the connection.

Specifically, the fast control MAC entity performs at least one function adjustment on the DRC entity, including: controlling whether to enable the DRC function;

The fast control MAC entity performs at least one function adjustment on the radio link layer control protocol RLC entity, including: controlling whether the RLC entity starts the centralized distributed mode;

The fast control MAC entity performs at least one function adjustment on the packet data convergence protocol PDCP entity, including: controlling whether the PDCP entity starts the centralized distributed mode.

Dynamic scheduling control of PDCP/DRC/RLC functional entity functions. According to the overall control of RRC signaling (RRC through the signaling configuration function optional set, the MAC selects a specific function for the PDCP/DRC/RLC in the function set), the PDCP/DRC/RLC function is dynamically fine-tuned.

For example, it may include: whether the DRC function is required, that is, whether the DRC can be transparently transmitted; whether the PDCP/RLC enables the centralized-distributed mode or the like.

The DRC function module is mainly used to complete the distribution of data received from the PDCP to the RLC center/RLC remote, and receive and retransmit the RLC center/RLC remote and then submit the control to the PDCP and the RLC center/RLC remote.

The RLC entity may include the RLC center and the RLC remote function entity, and the two functional entities are Mutually-exclusive RLC Entity, that is, when the RLC center exists, there is no RLC remote, and similarly, the RLC exists. When remote, There will be no RLC center.

It should be understood that this function is also added to the RRC entity in the 5G protocol. This solution sinks this function into the RC-MAC entity, so that the control for entities such as PDCP, DRC, and RLC can be implemented. Faster.

Seventh,

The fast control MAC maps the radio bearer RB to the at least one real-time MAC entity within a preset time period.

PDCP/DRC/RLC radio bearer (RB, Radio Bearer) real-time mapping scheduling control function. Based on the air interface measurement information of the terminal device reported by each RT-MAC, and/or the physical layer (PHY), the FC-MAC determines to map the PDCP/DRC/RLC RB to a specific RT-MAC in a certain period of time. Data is sent and received. That is, a specific radio bearer is set for the RT-MAC entity. The length of the above-mentioned preset time period can also be dynamically adjusted by the FC-MAC.

The eighth kind,

The fast control MAC entity determines flow control information for data sent and received by the RB, and sends the flow control information for the RB to at least one entity in the data link layer;

The traffic control information for the RB is used by at least one entity in the data link layer to control traffic of an RB mapped to at least one real-time MAC entity.

For the functions of at least one entity in the data link layer, refer to the description in the sixth function, and details are not described herein again.

The fast control MAC entity determines flow control information for data sent and received by the RB, and sends the flow control information for the RB to at least one of a PDCP entity, a DRC entity, and an RLC entity;

The traffic control information for the RB is used to notify at least one of a PDCP entity, a DRC entity, and an RLC entity to control traffic of an RB mapped to at least one real-time MAC entity.

It can be understood that this function can be combined with the seventh function for processing, that is, after performing the seventh function, that is, determining the RB allocated for each RT-MAC entity, this function can be used to perform RB specific Traffic control;

This function may also be used in combination with the seventh item. The specific usage may be determined according to actual conditions, and is not limited in this embodiment.

Specifically, referring to FIG. 4a, the PDCP/DRC/RLC has a flow control function for the RB. The specific implementation of this function can be:

Obtaining the quality and throughput of each terminal device in the air interface, the maximum throughput of the cell, the service characteristics of each terminal device, the bearer capacity of the cell, and the characteristics of the cell (for example, the data carrying the user at a high rate) Various quantized feature values, such as a cell, a cell carrying a signalling, or a cell of a dedicated function, and related information of each channel managed by the physical layer; the relevant channel may include a PDCCH/PDSCH/PUSCH/PUCCH;

In addition, resource allocation information between cells sent by the RRC entity, resource allocation information in the cell, and related information stored in the system of each terminal device may also be acquired;

The related information reported by the RT-MAC may be combined, for example, the load information and the type of service that can be carried, the resource in the cell corresponding to the RT-MAC, and the currently connected terminal device;

The flow control of the data sent and received by the RB is performed by combining the foregoing multiple information, and the flow control information for each RB is sent to the PDCP/DRC/RLC, so that the PDCP/DRC/RLC completes the flow control.

In the following, in conjunction with FIG. 5c, the above functions 7 and 8 are added with regard to the added fast control. Introduction of the process:

Step 53-1: The RRC of the Base Station sends a control information Control Info to the FC-MAC of the Base Station according to a corresponding algorithm, for example, may include intra-cell resources and inter-cell resources indicating RRC control, and save in the system. Information about each UE.

Step 53-2: The RT-MAC of the Base Station sends a control information Control Info to the FC-MAC of the Base Station according to a corresponding algorithm, indicating the intra-cell resources controlled by the RT-MAC of the Base Station and establishing a connection with the base station. Information about the UE, such as identification information of the UE.

Step 53-3: The PHY of the Base Station sends a control information Control Info to the FC-MAC of the Base Station according to a corresponding algorithm, and is used to indicate real-time related information of the physical layer (PHY), for example, each physical layer management Information about a channel.

Step 53-4: The FC-MAC of the Base Station is determined according to the corresponding algorithm, and a corresponding fast control process is required to send a control information Control Ind to the PDCP/DRC/RLC of the Base Station, indicating that the FC-MAC requirement of the Base Station is fast. Control process. Here, the flow control information of the RB may be sent to at least one entity in the PDCP/DRC/RLC entity. Of course, in actual processing, the FC-MAC entity may also send other control information, such as at least one entity in the foregoing entity. This embodiment is not exhaustive.

Step 53-5: The FC-MAC of the Base Station needs to generate a corresponding fast control process according to the corresponding decision, and sends a scheduling instruction to the RT-MAC of the Base Station, instructing the RT-MAC of the Base Station to send the air interface according to the scheduling instruction. make.

Step 53-6: The base station and the RT-MAC of the UE peer start the air interface HARQ process of the MAC, and complete the sending, receiving, and confirming of the packet.

Step 53-7: After receiving the MAC packet correctly, the RT-MAC of the UE sends the control information Control Info to the FC-MAC of the UE.

Step 53-8: After receiving the Control Report, the FC-MAC of the UE completes the corresponding operation, and sends a Control Info to the PDCP/DRC/RLC of the UE to indicate the fast control process.

It can be seen that, by adopting the foregoing solution, the MAC protocol entity can be divided into two types, namely, a fast control MAC entity and at least one real-time MAC entity, and the fast control MAC entity performs scheduling for at least one real-time MAC entity. Therefore, the scheduling and control of the at least one MAC entity can be completed at the MAC layer, thereby ensuring the rapid completion of the air interface signaling and improving the processing speed of the overall architecture.

In addition, since the foregoing solution performs a part of the functions of the RRC protocol entity that needs to be quickly executed by the fast control MAC entity, the signaling processing is further ensured quickly; and the resource coordination between the cells can be performed by rapidly controlling the MAC entity, thereby It ensures that the terminal device can quickly complete the handover process of joining other cells.

Finally, since this solution does not need to modify the function of the MAC entity set in the original protocol, it has good scalability and can quickly support a large number of users. In addition, it is still based on the functions specified in the original protocol. Functional adjustment between different protocol entities, so better compatibility, compatible with multiple protocol entities in 4G/5G networks.

Embodiment 2

On the basis of the foregoing embodiment, the embodiment further provides that, according to the foregoing fast control MAC generation and issuing a scheduling instruction, a control instruction may also be sent; specifically, as shown in FIG. 2b, the method includes:

Step 2021: Generate control signaling by using a fast control medium access control MAC entity, where the fast control MAC entity is set in a central control unit;

Step 2022: The fast control MAC entity set in the central control unit sends the control signaling to at least one real-time MAC entity, where each real-time MAC entity in the at least one real-time MAC entity is set in a distribution unit, and A real-time MAC entity or a plurality of real-time MAC entities can be set in each of the distribution units.

In this embodiment, the function of the central control unit is to enable big data operation, and after completing the big data operation, generate a corresponding operation result, and send the generated operation result to the distribution unit;

Each of the distribution units may be configured to correspond to a cell, and each of the distribution units may be configured to perform resource allocation of the air interface in the cell according to the operation result. In addition, each of the distribution units may collect information from the air interface and report the information to the central control unit.

In addition, since one distribution unit corresponds to one cell and one or more real-time MAC entities correspond to one cell, one or more real-time MAC entities may be disposed in one distribution unit.

In this embodiment, the central control unit may be a wireless cloud center (RCC), and the plurality of distribution units may be a plurality of remote radio systems (RRS). Aiming at the RCC-RRS distributed architecture of the 5G access network and the multi-level MAC function, a total fraction placement scheme of the MAC on the distributed base station architecture is proposed. The scheme passes the multi-level MAC function on the RCC-RRS. Reasonable placement, the combination of multi-level MAC and RCC-RRS architecture can effectively support the various scenarios of 4G/5G.

The overall scheme of the MAC protocol entity function is shown in FIG. 3a. In this embodiment, the MAC protocol entity function is divided into two functional modules: a fast control (FC)-MAC entity and a real-time (RT)-MAC entity. Among them, FC-MAC is divided into two functions: Fast Signaling Control (RT) and RT-MAC Control (RT-MAC Control). RT-MAC is the current or current traditional MAC protocol entity function.

Based on the total fractional relationship between the fast control MAC entity and the at least one real-time MAC entity, the fast control MAC entity may be set in the central control unit, and the real-time MAC entity is set in the distribution unit. For details, see FIG. 3b. .

Specifically, in this embodiment, referring to FIG. 4b, the fast control MAC entity is set in the RCC, and the real-time MAC entity is set in the RRS. FC-MAC is all placed on the RCC. The RT-MAC is placed on the RRS. One RCC can correspond to multiple RRSs (1...m), one R-MAC on each RRS, and one FC-MAC can correspond to multiple RT-MACs at the same time.

First, in this embodiment, an implementation of a fast signaling control function for a fast control MAC entity is introduced:

First, the generating the control signaling by using the fast control MAC entity set in the RCC, including:

Acquiring, by the fast control MAC entity set in the RCC, the content of the RRC signaling from the radio resource control RRC entity;

The fast control MAC entity generates control signaling based on the content of the RRC signaling.

Specifically, the fast control MAC entity performs the RRC protocol signaling function, and the signaling function of the original RRC protocol entity needs to implement fast control and sink to the MAC.

The RRC signaling includes: air interface switching signaling and/or radio link reconfiguration signaling.

That is to say, by sinking the relevant signaling of the air interface handover to the fast control MAC entity, the original control by RRC air interface signaling can now send a special PDCCH or a defined MAC CE (MAC Control) through the FC-MAC. Element) for quick control.

Second, the method further includes: performing functional adjustment on at least one entity at the data link layer by using a fast control MAC entity.

The at least one entity of the data link layer may be at least one of a PDCP entity, a DDR entity, and an RLC entity.

Specifically, it includes at least one of the following:

The fast control MAC entity performs at least one function adjustment on the DDR entity;

For example, the fast control MAC entity establishes a connection with the PDCP entity, the DDR entity, and the RLC entity, and performs functional adjustment on the above entities based on the connection.

The fast control MAC entity performs at least one function adjustment on the DDR entity, including: controlling whether to enable the DDR function;

Dynamic scheduling control of PDCP/DDR/RLC functional entity functions. According to the overall control of the RRC signaling (the RRC through the signaling configuration function optional set, the MAC selects a specific function for the PDCP/DDR/RLC in the function set), the PDCP/DDR/RLC function is dynamically fine-tuned.

For example, it may include: whether a DDR function is required, that is, whether the DDR can be transparently transmitted; whether the PDCP/RLC enables the centralized-distributed mode or the like.

The DDR function module is mainly used for completing the distribution of data received from the PDCP to the RLCcenter/RLCremote, and receiving the reorganization from the RLCcenter/RLCremote, and then submitting the control to the PDCP and the RLCcenter/RLCremote in sequence;

The RLC entity may include the RLCcenter and the RLCremote functional entity, and the two functional entities are Mutually-exclusive RLC Entity, that is, when the RLCcenter exists, the RLCremote does not exist. Similarly, when the RLCremote exists, There is RLCcenter. RLCcenter/RLCremote.

It should be understood that sinking this function into the fast control MAC entity, Controls for entities such as PDCP, DDR, and RLC can be made faster.

Secondly, the following describes the implementation of the fast control MAC entity to control at least one real-time MAC entity in the RRS:

In the existing LTE architecture, the function of the MAC can be seen in Figure 6a. It can be seen that in the LTE architecture, the functions of radio resource management, channel quality management, and PDU control are currently performed by the MAC, and further based on the foregoing management functions. The cell allocation of the terminal device is determined, and then each terminal device is scheduled. In this embodiment, the function of the MAC is further divided based on the foregoing architecture, and the MAC address is added to the MAC for the overall processing of the MAC, so that the solution provided in this embodiment can complete the MAC layer at the MAC layer. Scheduling and control, which ensures the rapid completion of air interface signaling and improves the processing speed of the overall architecture.

Specifically, based on FIG. 6b, it can be seen that for the downlink MAC, the functions of the FC-MAC include Unicast Scheduling/Priority Handling among Cells for UEs, and a cell. Multiplexing UEs in Cell, Cell's Radio Quality Manager, PDU Controller, Channel Quality Manager, Radio Resource Manager, Signaling Control (Siganling Controller), Unicast Scheduling/, Priority Handling among Carriers for UEs in Cell, Multiplexed UEs in CC, etc. Function, these protocol functions include control and bearer signaling control functions for RT-MAC.

Correspondingly, the real-time (RT)-MAC entity includes performing unicast scheduling (Unicast Scheduling)/Priority Handling among UEs, multiplexing multiplexed UEs of the terminal device, and HARQ according to control signaling sent by the FC-MAC entity. .

Further explain the above functions:

The method further includes:

Obtaining air interface resource information by quickly controlling a terminal device radio resource management function in the MAC entity;

and / or,

Obtaining channel quality information by quickly controlling a channel quality management function of a terminal device in a MAC entity;

and / or,

The wireless air interface quality information of each cell is obtained by quickly controlling the inter-cell wireless air interface quality management function in the MAC entity.

Specifically, the radio resource management function for the terminal device is used to complete occupation management of the historical air interface resource of the UE and use management of the current air interface resource. The module manages two aspects of resources, one is a semi-static UE-dedicated radio resource configured by RRC, such as SRS, PUCCH, and the like; and the other is an air interface resource dynamically allocated by each TTI of the MAC, such as PRB, PDCCH, etc., used as a UE channel. Smooth measurement.

The channel quality management function for the terminal device is used to manage the channel quality of the UE on the available cells, including broadband and sub-band channel quality. The module receives the channel measurement parameters of the physical layer and performs calculation according to a certain algorithm, and is used as the channel quality monitoring of the UE in each corresponding cell. Each time the MAC schedules the UE, the radio resource allocation is performed according to the channel quality of the UE.

The wireless quality management function of the small interval is used to manage the quality of the wireless air interface of each cell and provide parameter support for the cooperation between the cells. The function module uses a correlation algorithm according to the channel quality of each UE in the cell to calculate the average air interface quality and related interference of each cell to determine the load capacity of the cell. When the MAC schedules a specific UE that each cell can support, it needs to make a decision according to the radio quality of the cell.

Further, based on the above several functions, the generating control by the MAC entity is controlled quickly Signaling, including:

The fast control MAC entity allocates a target cell to the terminal device according to at least one of air interface resource information, channel quality information, and wireless air interface quality information of each cell;

Allocating a target real-time MAC entity to the terminal device based on a target cell allocated for the terminal device, and allocating, for the terminal device, a size of a data unit to be transmitted in the target cell;

Taking the target real-time MAC entity and the size of the data unit as the first allocation result;

A control instruction for the target real-time MAC entity is generated based at least on the first allocation result.

Specifically, refer to the function of Unicast Scheduling/Priority Handling among Cells for UEs in FIG. 6b, according to the channel quality of the UE (Channel Quality Manager), the air interface quality of the cell (Cells' Radio Quality Manager), information of the service (RRC configuration) and other information, complete the cell allocation used by the UE. The function module completes the set of cells available to each UE according to various air interface qualities, that is, completes mapping of the logical channel to the cell of the UE.

Through the PDU control function for the terminal device, when the packets transmitted by the UE meet the size indicated by the MAC, it is ensured that the RLC does not have any influence, and the SN number of the RLC cannot be violently changed, and the RLC is removed from the traditional function. New features, etc. After the downlink FC-MAC completes the scheduling of the UE in each cell, the size of the SDU sent by the UE in the cell is determined. Then, the PDU Controller obtains the packet from the RLC, and the PDU Controller ensures the PDU sent by multiple cells according to the corresponding algorithm. Does not affect the RLC.

The method further includes allocating a radio bearer (RB) to the terminal device through a fast control MAC entity set in the RCC; mapping the allocated RB to the target real-time MAC entity.

Specifically, refer to FIG. 6b, through unicast scheduling (Unicast Scheduling) / to the cell The function of the user in the cell (Multiplexing UEi in CC) is performed, and the user-to-carrier scheduling in the cell is completed, and the UE is completed from the carrier to the cell. Mapping of transport channels carried by the inner carrier.

On this basis, the UEs that can be supported by each cell are completed according to the scheduling result of the Unicast Scheduling/Priority Handling among Cells for UEs by the multiplex processing (Multiplexing UEs in Celli) function in the cell, that is, within the TTI. The UE is scheduled in the cell to complete mapping of the UE from the carrier in the cell-cell.

Corresponding to the functions of the above-mentioned FC-MAC entity, in each real-time MAC entity, by accepting Unicast Scheduling/Priority Handling among UEs and user resource multiplexing (Multiplexing) The UEi) and other control information completes the user scheduling in the cell, and completes the mapping of the physical channel carried by the carrier in the transport channel-cell carried by the carrier in the cell of the UE.

In addition, based on the above FIG. 6b, the embodiment further provides the following functions:

BCH function: BCH data is still transmitted in the traditional way on each cell.

The downlink CCCH function: The most suitable air interface channel for each UE can be selected according to the channel quality of each UE on each cell, so the CCCH needs to be scheduled by the cell and the UE.

PCH function: According to the channel quality of each UE on each cell, the most suitable air interface channel of each UE can be selected and combined into an appropriate PCH to be sent in the air interface. Therefore, the PCH needs to be scheduled by the cell and the UE.

The generating the control signaling by using the fast control MAC entity set in the RCC, further includes:

And the fast control MAC entity generates a control instruction for the target real-time MAC entity of the terminal device in the air port based on the air interface bearer mode selected by the terminal device.

The content of the signaling of the RRC entity is obtained, and the RRC entity can still perform the allocation of the air interface bearer mode for the terminal device, but the specific signaling is not generated, but the air interface bearer mode is sent to the fast control MAC entity, and finally The fast control MAC entity generates a scheduling instruction based on the air interface bearer mode allocated by the device. The specific implementation process can be seen in Figure 6a, and details are not described herein.

The generating control signaling by using the fast control MAC entity includes:

Generating the control instruction based on a data transmission type corresponding to the at least one real-time MAC entity.

Specifically, the dynamic scheduling control of the RT-MAC real-time function. According to the overall control of the RRC signaling (the RRC is configured by the signaling configuration function, the MAC selects a specific function for the RT-MAC in the function set), and performs scheduling control on the RT-MAC function, including whether only the control plane is performed. (Control Plane) or user plane (User Plane) corresponding data transmission and reception, or control Plane and User Plane data can be sent and received at the same time.

On the basis of the foregoing generation and transmission of the downlink information, the embodiment may further describe the transmission and processing of the uplink signaling. Specifically, the method further includes:

Acquiring, by the fast control MAC entity set in the RCC, the uplink signaling uploaded by the at least one terminal device from the at least one real-time MAC entity, and parsing and processing the uplink signaling.

The traditional MAC can be seen in Figure 6c, the function of the 5G upstream MAC. For the structure and function of the uplink total fractional MAC in this embodiment, refer to FIG. 6b. For the uplink MAC, the processing function of the FC-MAC for the uplink signaling corresponds to the downlink, that is, the Scheduling/Priority Handling is also included. Among Cells for UE, Multiplexed UEs in Cell, PDU Controller, Scheduling/Priority Handling in Cell, Multiplex in CC, etc. RT-MAC includes functions such as Scheduling/Priority Handling, Multiplexing, and HARQ. It should be understood that the processing functions of the uplink signaling are based on receiving uplink signaling that is actively reported by the terminal device on the basis of the downlink signaling control, or feedback information for downlink signaling, and for these uplinks. The processing of signaling and the generation of downlink signaling may be mutually reversible processing.

The packets of the UE's uplink PDU Controller module complete the UE transmission are guaranteed to have no impact on the RLC when the packets indicated by the MAC (Scheduling/Priority Handling among Cells for UE and Unicast Scheduling/Priority Handling function modules are provided), including the SN number of the RLC. There can be no violent jumps, and RLC brings new functions beyond the traditional functions. After the MAC PDU received by the uplink MAC obtains the SDU through the MAC unpacking function, the PDU Controller sends the RLC for subsequent processing. The PDU Controller ensures that the PDUs sent by multiple cells do not affect the RLC according to the corresponding algorithm.

The Scheduling/Priority Handling among Cells for the UE configures the cells allocated by the UE according to the selected channels of the multiple cells of the UE on the network side. For example, the network side of each cell of the multiple cells configures the periodic SR for the UE. , UE can be empty Channel channel quality, select the appropriate cell to send the SR. For example, the resource allocated by the SPS, the CQI reported periodically, and the like, thereby completing the mapping of the logical channel to the cell of the UE.

Multiplexing UE in Cellm completes the RB that each cell can send, that is, the data content sent by the UE in the cell within this TTI.

The Scheduling/Priority Handling among in Cell completes the scheduling of the UE in the cell according to the scheduling result of the Scheduling/Priority Handling among Cells for UE, thereby completing the selection of the UE in the cell, and realizing the mapping of the UE from the cell to the carrier in the cell.

The multiplexed UE in CC completes the data that can be sent by each carrier, that is, the data content sent by the UE in the cell in the TTI, and completes the mapping of the UE from the carrier-bearing transport channel in the cell-cell.

The Unicast Scheduling/Priority Handling and the Multiplexing UE complete the scheduling of the UE in the carrier, and the function is the same as the traditional MAC function, and completes the mapping of the physical channel carried by the carrier in the carrier channel of the UE in the cell.

Uplink CCCH function: The UE can select the most suitable air interface channel to send to the network side according to the channel quality (measurement from the physical layer) on each cell. That is, the UE can be on different cells during the random access process. The Msg1/Msg3 is sent separately, so the CCCH needs to be scheduled by the cell and the UE.

During scheduling, the fast control MAC first performs cell-level scheduling, and according to the quality information of the cell (including the load, the number of PRBs of the edge, etc.) and the quality of the air interface of each UE on its associated cell, the MAC is quickly controlled to complete one UE and several cells. The mapping process determines that each UE can send and receive data on several cells, and configures a plurality of most suitable cells according to the requirements of the UE to complete data transmission in the air interface. Secondly, the real-time MAC completes the mapping function of the radio resources of the UE and the cell according to the specific requirements of the UE, and completes the calculation of the packet size sent by the UE. Finally, if it is downlink processing, the data is requested from the RLC according to the packet size; if it is the uplink data, it is waiting for the UE to send.

It can be seen that, by adopting the foregoing solution, the MAC protocol entity can be divided into two types, namely, a fast control MAC entity and at least one real-time MAC entity, and the fast control MAC entity is set in the RCC, and the real-time MAC entity is set in the RRS, and The transmission of control signaling is performed by the fast control MAC entity for at least one real-time MAC entity. Therefore, it is ensured that even in the scenario where the number of cells in the 5G increases a lot, the cloud center can ensure its computing capability by adding a fast control MAC entity, and the control of multiple real-time MAC entities through a fast control MAC entity ensures effective Supporting large-scale MAC, improving the processing efficiency of the system.

Embodiment 3

The application provides a fast control MAC entity, as shown in FIG. 7a, including:

An instruction generating unit 71, configured to determine a scheduling instruction for the at least one real-time MAC entity;

The information sending unit 72 is configured to send the scheduling instruction to the at least one real-time MAC entity.

In this application, for the distributed architecture and air interface feature requirements of the 5G access network, and the limitations of the current MAC protocol entity function, a total fractional MAC scheme with air interface fast signaling capability is proposed, and the scheme is compatible. The basis for the MAC protocol stack function adds new processing capabilities.

The first,

As shown in FIG. 7b, the fast control MAC entity further includes:

An information acquiring unit 73, configured to acquire, by the radio resource control RRC entity, content of the RRC signaling;

Correspondingly, the instruction generating unit 71 is configured to generate a scheduling instruction for the at least one real-time MAC entity based on the content of the RRC signaling.

The instruction generating unit 71 is configured to encapsulate, by the fast control MAC entity, a scheduling instruction by using a preset special PDCCH or a defined MAC control element (CE, Control Element).

That is to say, by sinking the relevant signaling of the air interface handover to the fast control MAC entity, the original control by RRC air interface signaling can now be performed by the FC-MAC to send a special PDCCH or a defined MAC CE for fast control. .

Second,

An information acquiring unit, configured to acquire a processing load and a spatial coverage of the at least one real-time MAC entity, and a feature parameter of the terminal device;

Correspondingly, the instruction generating unit is configured to allocate, according to a processing load of the at least one real-time MAC entity and a spatial coverage situation and a feature parameter of the terminal device, a target real-time MAC entity to the terminal device as a first allocation result; A scheduling instruction for the target real-time MAC entity is generated based on the first allocation result.

Specifically, the information acquiring unit is configured to obtain a processing load, a corresponding spatial coverage, and an air interface quality, a neighboring air interface quality, a moving direction, and the like, which are reported by the at least one real-time MAC entity that is managed by the terminal device. Various air interface characteristic parameters, cell characteristic parameters and user characteristic parameters.

The command generating unit is configured to allocate a corresponding target real-time MAC entity to each of the at least one terminal device, and use the allocated target real-time MAC entity as the first allocation result corresponding to each of the terminal devices.

Specifically, the manner in which the target real-time MAC entity is selected for the terminal device may be a combination of a cell served by each real-time MAC entity, a service type of the supported terminal device, and a current load thereof, and combined with the air interface quality of the terminal device. The quality of the air interface in the neighboring area and the direction of movement, and select the appropriate RT-MAC for each user to send and receive data.

The instruction generating unit is configured to acquire a processing load and a spatial coverage condition of the at least one real-time MAC entity, and a feature parameter of the terminal device;

The number of terminal devices and/or supported industries carried by the at least one real-time MAC entity The transaction type is used as a scheduling instruction.

Third,

The instruction generating unit is configured to determine a data transmission type for each real-time MAC entity in the at least one real-time MAC entity, where the data transmission type includes data transmission of a control plane, and/or data transmission of a user plane And generating the scheduling instruction based on a data transmission type corresponding to the at least one real-time MAC entity.

Specifically, for example, see FIG. 4a, dynamic scheduling control of the RT-MAC real-time function. According to the overall control of the RRC signaling (the RRC is configured by the signaling configuration function, the MAC selects a specific function for the RT-MAC in the function set), and performs scheduling control on the RT-MAC function, including whether only the control plane is performed. (Control Plane) or user plane (User Plane) corresponding data transmission and reception, or control Plane and User Plane data can be sent and received at the same time.

Fourth,

The command generating unit is configured to select an air interface bearer mode for the terminal device, and generate a scheduling instruction for the target real-time MAC entity of the terminal device based on the air interface bearer mode selected by the terminal device.

Specifically, the fast control MAC entity selects an air interface bearer mode for the terminal device, The determining manner may be: the various measurement information of each terminal device reported by the RT-MAC and the physical layer (PHY), and the transmission resource requirements of each terminal device in the air interface are accurately perceived by the measurement information of the respective terminal devices; The content of the signaling to the RRC entity; the air interface bearer mode is selected for each terminal device in combination with the transmission resource requirements of the respective terminal devices in the air interface and the signaling content of the RRC entity.

Fifth,

The instruction generating unit is configured to determine a target cell that the terminal device is to access, and obtain, according to the target cell that the terminal device accesses, the at least one real-time MAC entity corresponding to the target cell, to obtain the terminal device. Allocating a second allocation result of the target real-time MAC entity; generating a scheduling instruction for the target real-time MAC entity based at least on the second allocation result.

Further, the allocation of the target real-time MAC entity to the terminal device may also refer to at least one of the foregoing second-fourth functions, that is, the air interface bearer mode of each real-time MAC entity may also be combined. , the types of services supported, and the number of terminal devices that can be carried The quantity, and the target cell to be served in this function, jointly generate scheduling instructions.

Sixth,

As shown in FIG. 8a, the fast control MAC entity further includes:

The adjusting unit 74 is configured to perform at least one function adjustment on at least one entity in the data link layer.

Compression, decompression: header compression and decompression of IP packets;

Re-establishment process: data forwarding and in-order delivery;

Packets are sent in order and delivered in order;

Sending segmentation and concatenation of the data packet;

Re-establishment process: data is delivered in random order;

Specifically, compression, decompression, header compression and decompression of IP packets; security, encryption, decryption or integrity protection of data packets, including maintenance of data packet sequence numbers; re-establishment process, data Data forwarding and in-order delivery; data packets are sent sequentially and in order, and can be implemented by PDCP entities in the data link layer.

It is to be understood that the PDCP entity, the DRC entity, and the RLC entity are only one specific implementation manner, and may be implemented by other entities in the implementation. In this embodiment, the entity that specifically implements the foregoing functions is not limited.

For example, the specific processing may be at least one of the following:

Performing at least one function adjustment on the packet data convergence protocol PDCP entity;

Performing at least one function adjustment on the DRC entity;

At least one function adjustment is performed on the radio link layer control protocol RLC entity.

Specifically, the fast control MAC entity performs at least one function adjustment on the DRC entity, where the function adjustment unit is configured to control whether the DRC function is enabled; and/or whether the RLC entity is enabled to be centralized. The distributed mode performs control; and/or controls whether the PDCP entity enables the centralized distributed mode.

Dynamic scheduling control of PDCP/DRC/RLC functional entity functions. According to the overall control of the RRC signaling (the RRC is configured by the signaling configuration function, the MAC selects a specific function for the PDCP/DRC/RLC in the function set), and the PDCP/DRC/RLC function is Fine-tuning of the line.

The RLC entity may include the RLC center and the RLC remote function entity, and the two functional entities are Mutually-exclusive RLC Entity, that is, when the RLC center exists, there is no RLC remote, and similarly, the RLC exists. When remote, there is no RLC center.

Seventh,

The adjusting unit is configured to map the radio bearer RB to the at least one real-time MAC entity in a preset time period.

PDCP/DRC/RLC radio bearer (Radio Bearer) real-time mapping scheduling control function. Based on the air interface measurement information of the terminal device reported by each RT-MAC, and/or the physical layer (PHY), the FC-MAC determines to map the PDCP/DRC/RLC RB to a specific RT-MAC in a certain period of time. Data is sent and received. That is, a specific radio bearer is set for the RT-MAC entity.

The length of the above-mentioned preset time period can also be dynamically adjusted by the FC-MAC.

The eighth kind,

The adjusting unit is configured to determine flow control information for data sent and received by the RB, and send the flow control information for the RB to at least one entity in the data link layer;

Specifically, referring to FIG. 4a, the PDCP/DRC/RLC has a radio bearer (Radio Bearer) flow control function. The specific implementation of this function can be:

Embodiment 4

The embodiment of the present application is based on the foregoing third embodiment, and the present embodiment further describes the function of each unit module according to FIG. 8b. Specifically:

a signaling generating unit 71, configured to generate control signaling;

The signaling sending unit 72 is configured to send the control signaling to at least one real-time MAC entity.

For the RCC-RRS distributed architecture of the 5G access network and the multi-level MAC function, this patent proposes a total fraction placement scheme of the MAC on the distributed base station architecture, which adopts the multi-level MAC function in the RCC- Reasonable placement on the RRS enables a combination of multi-level MAC and RCC-RRS architectures to effectively support the 4G/5G scenarios.

First, the signaling generating unit is configured to control the MAC entity from the wireless resource by quickly controlling The RRC entity acquires the content of the RRC signaling; and generates control signaling based on the content of the RRC signaling.

The signaling generating unit is configured to encapsulate the scheduling instruction by using a preset special PDCCH or a defined MAC control element (CE, Control Element).

Second, the signaling generating unit is configured to perform function adjustment on at least one entity in the data link layer by using a fast control MAC entity set in the RCC.

The at least one entity of the data link layer may be at least one of a PDCP entity, a DDR entity, and an RLC entity. Specifically, at least one of the following is included:

Performing at least one function adjustment on the PDCP entity;

Performing at least one function adjustment on the DDR entity;

Performing at least one function adjustment on the RLC entity.

The signaling generating unit is configured to control whether the RLC entity starts a centralized distributed mode;

The signaling generating unit is configured to control whether the PDCP entity starts the centralized distributed mode.

It is to be understood that this function is sinked into the RC-MAC entity to enable control of entities such as PDCP, DDR, and RLC to be faster.

In the existing LTE architecture, the function of the MAC can be seen in Figure 5a. It can be seen that in the LTE architecture, the functions of radio resource management, channel quality management, and PDU control are currently performed by the MAC, and further based on the foregoing management functions. The cell allocation of the terminal device is determined, and then each terminal device is scheduled.

In this embodiment, the function of the MAC is divided, and the MAC is quickly added to the MAC for overall processing, so that the application can be completed at the MAC layer. The scheduling and control of at least one MAC entity ensures fast completion of air interface signaling and improves the processing speed of the overall architecture.

Based on FIG. 6b, it can be seen that for the downlink MAC, the functions of the FC-MAC include Unicast Scheduling/Priority Handling among Cells for UEs, and multiplexing of terminal devices in the cell (Multiplexing) UEs in Cell), Cellular's Radio Quality Manager, PDU Controller, Channel Quality Manager, Radio Resource Manager, Siganling Controller, Unicast Scheduling (Unicast Scheduling)/Priority Handling Carriers for UEs in Cell, Multiplexed UEs in CC, etc. These protocol functions include RT-MAC. Control and assume signaling control functions.

Correspondingly, the real-time (RT)-MAC entity includes functions such as Unicast Scheduling/Priority Handling among UEs, multiplexing Multiplexing UE of the terminal device, and HARQ according to control signaling sent by the FC-MAC entity.

Further explain the above functions:

The fast control MAC entity further includes:

a radio resource management unit 75, configured to acquire air interface resource information;

and / or,

a channel quality management unit 76, configured to acquire channel quality information;

and / or,

The small-area wireless air interface quality management unit 77 is configured to acquire wireless air interface quality information of each cell.

Specifically, the radio resource management function for the terminal device is used to complete occupation management of the historical air interface resource of the UE and use management of the current air interface resource. This module manages two parties The resources of the surface, one is a semi-static UE-specific radio resource configured by the RRC, such as SRS, PUCCH, etc.; one is an air interface resource dynamically allocated by each TTI of the MAC, such as a PRB, a PDCCH, etc., and is used as a smooth measurement of the UE channel.

Further, based on the foregoing functions, the signaling generating unit is configured to: the at least one of the fast control MAC entity set in the RCC, according to the air interface resource information, the channel quality information, and the wireless air interface quality information of each cell. a message for assigning a target cell to the terminal device;

Assigning, by the terminal device, a target real-time MAC entity to the terminal device, and assigning, by the terminal device, a size of a data unit transmitted in the target cell as a first allocation result;

Specifically, refer to the function of Unicast Scheduling/Priority Handling among Cells for UEs in FIG. 6b, according to the channel quality of the UE (Channel Quality Manager), the air interface quality of the cell (Cells' Radio Quality Manager), characteristics of the service (RRC configuration), and other information, complete the cell allocation used by the UE. The function module completes the set of cells available to each UE according to various air interface qualities, that is, completes mapping of the logical channel to the cell of the UE.

Through the PDU control function for the terminal device, when the packets transmitted by the UE meet the size indicated by the MAC, it is ensured that the RLC does not have any influence, and the SN number of the RLC cannot be violently changed, and the RLC is removed from the traditional function. New features, etc. After the downlink FC-MAC completes the scheduling of the UE in each cell (via Unicast Scheduling/Priority Handling among Cells for UEs, Unicast Scheduling/Priority Handlingamong Carriers for UEs in Cell1, Unicast Scheduling/Priority Handlingamong among UEi and Multiplexing UEiin celli, Multiplexing The UEi function module performs scheduling to determine the size of the SDU sent by the UE in the cell. Then, the PDU Controller obtains the packet from the RLC. The PDU Controller ensures that the PDUs sent by the multiple cells do not affect the RLC according to the corresponding algorithm.

The signaling generating unit is configured to allocate a radio bearer (RB) to the terminal device; and map the allocated RB to the target real-time MAC entity.

Specifically, referring to FIG. 6b, the unicast scheduling (Unicast Scheduling)/Priority Handling for UEs in cell and the function of Multiplexing UEi in CC in the component carrier are completed. The user-to-carrier scheduling in the cell completes the mapping of the UE from the carrier to the transport channel carried by the carrier in the cell.

On the basis of this, the UEs that can be supported by each cell are completed according to the scheduling result of the Unicast Scheduling/Priority Handling among Cells for UEs, which is the TTI in this TTI. The UE is scheduled in the cell to complete the mapping of the UE from the carrier in the cell-cell.

Corresponding to the function of the above FC-MAC entity, in each real-time MAC entity, by accepting unicast scheduling (Unicast Scheduling) / terminal device resource allocation (Priority Handling among UEs) and control information such as resource multiplexing (Multiplexing UEi) of the terminal device, complete user scheduling in the cell, and complete mapping of the physical channel carried by the carrier in the transport channel-cell carried by the carrier in the cell of the UE.

The signaling generating unit is configured to select an air interface bearer mode for the terminal device, and generate a control instruction for the target real-time MAC entity of the terminal device in the air port bearer mode selected by the terminal device.

The content of the signaling of the RRC entity is obtained, and the RRC entity can still perform the allocation of the air interface bearer mode for the terminal device, but the specific signaling is not generated, but the air interface bearer mode is sent to the fast control MAC entity, and finally The fast control MAC entity generates a scheduling instruction based on the air interface bearer mode allocated by the device. The specific implementation process can be seen in Figure 5a, and details are not described herein.

The signaling generating unit is configured to determine a data transmission type for each real-time MAC entity in the at least one real-time MAC entity, where the data transmission type includes data transmission of a control plane, and/or data of a user plane Transmitting; generating the control instruction based on a data transmission type corresponding to the at least one real-time MAC entity.

Based on the foregoing generation and transmission of downlink information, the method further includes:

The signaling processing unit 78 is configured to acquire uplink signaling uploaded by the at least one terminal device from the at least one real-time MAC entity by using a fast control MAC entity that is set in the RCC, and parse and process the uplink signaling.

The traditional MAC can be seen in Figure 6c. The uplink MAC of 5G adds the MAC PDU controller function for the UE and the scheduling/priority handling among UEs and the Multiplexing UE in cell, scheduling/ for the UE and cell level and carrier level radio resource mapping. Priority handling in cell and Multiplexing UE in CC function.

For the structure and function of the uplink total fractional MAC in this embodiment, refer to FIG. 6d. For the uplink MAC, the function provided by the FC-MAC function corresponds to the downlink, that is, the Scheduling/Priority Handling among Cells are also included. For UE, Multiplexing UEs in Cell, PDU Controller, Scheduling/Priority Handling in Cell, Multiplex in CC, etc. These protocol functions include RT-MAC control. System and bear the signaling control function. RT-MAC includes functions such as Scheduling/Priority Handling, Multiplexing, and HARQ. It should be understood that the processing functions of the uplink signaling are based on receiving uplink signaling that is actively reported by the terminal device on the basis of the downlink signaling control, or feedback information for downlink signaling, and for these uplinks. The processing of signaling and the generation of downlink signaling may be mutually reversible processes.

The Scheduling/Priority Handling among Cells for the UE configures the cells allocated by the UE according to the selected channels of the multiple cells of the UE on the network side. For example, the network side of each cell of the multiple cells configures the periodic SR for the UE. The UE can select an appropriate cell to send the SR according to the quality of the air interface channel. For example, the resource allocated by the SPS, the CQI reported periodically, and the like, thereby completing the mapping of the logical channel to the cell of the UE.

When scheduling, the MAC first performs cell-level scheduling. According to the quality information of the cell (including the load, the number of PRBs of the edge, etc.) and the quality of the air interface of each UE on its associated cell, the MAC completes mapping processing of one UE and several cells, and determines that each UE can be on several cells. The data is sent and received, and a number of most suitable cells are configured according to the requirements of the UE to complete the transmission of data in the air interface. Secondly, the MAC completes the mapping function of the radio resources of the UE and the cell according to the specific requirements of the UE, and completes the calculation of the packet size sent by the UE. Finally, if it is downlink processing, the data is requested from the RLC according to the packet size; if it is the uplink data, it is waiting for the UE to send.

It can be seen that, by adopting the foregoing solution, the MAC protocol entity can be divided into two types, namely, a fast control MAC entity and at least one real-time MAC entity, and the fast control MAC entity is set in the RCC, and the real-time MAC entity is set in the RRS, and The transmission of control signaling is performed by the fast control MAC entity for at least one real-time MAC entity. Therefore, even in the scenario where the number of cells in the 5G increases a lot, the cloud base station can provide more computing power and can effectively support a large-scale MAC.

Embodiment 5

The present application provides an entity management system. As shown in FIG. 9, the system includes: a fast control MAC entity 91 and at least one real-time MAC entity 92;

a fast control MAC entity 91 for determining for the at least one real-time MAC entity Scheduling an instruction; transmitting the scheduling instruction to the at least one real-time MAC entity;

The real-time MAC entity 92 is configured to receive a scheduling instruction sent by the fast control MAC entity, and perform processing according to the scheduling instruction.

The overall scheme of the MAC protocol entity function is shown in Figure 3. In this embodiment, the MAC protocol entity function is divided into two functional modules: a fast control (FC)-MAC entity and a real-time (RT)-MAC entity. Among them, FC-MAC is divided into two functions: Fast Signaling Control (RT) and RT-MAC Control (RT-MAC Control). RT-MAC is the current or current traditional MAC protocol entity function.

In order to ensure the compatibility of the protocol stack, the traditional MAC function is uniformly defined as RT-MAC, and the control for the intra-cell user scheduling, the intra-cell radio resource allocation, the intra-cell user and the radio resource corresponding process is completed, and the RT-MAC function only focuses. The corresponding MAC function within the cell.

Specifically, as shown in FIG. 3, the FC-MAC mainly includes two major functions: a fast control function that is assumed, that is, a control process that is traditionally performed through RRC signaling, and sinks to the MAC to perform fast control through air interface scheduling. Function; scheduling control process for RT-MAC (excluding signaling control function), this function focuses on the scheduling of RT-MAC and the non-signaling control functions required to complete the scheduling.

The following describes the various functions that the system can perform and its specific implementation:

The first,

As shown in FIG. 10, the system further includes:

An RRC entity 93, configured to provide RRC signaling content for the fast control MAC entity;

Correspondingly, the fast control MAC entity 91 is configured to generate a scheduling instruction for the at least one real-time MAC entity 92 based on the content of the RRC signaling.

The fast control MAC entity encapsulates the scheduling instruction by using a preset special PDCCH or a defined MAC control element (CE, Control Element).

Second,

The fast control medium access control MAC entity acquires processing load and spatial coverage of the at least one real-time MAC entity, and characteristic parameters of the terminal device; based on processing load and spatial coverage of the at least one real-time MAC entity, and the terminal a feature parameter of the device, the target real-time MAC entity is allocated to the terminal device as a first allocation result; and a scheduling instruction for the target real-time MAC entity is generated based on at least the first allocation result.

Obtaining processing load, corresponding spatial coverage, and obtaining air interface quality and neighboring air quality of at least one real-time MAC entity managed by the terminal device Various air interface characteristic parameters, cell characteristic parameters and user characteristic parameters, such as quantity, moving direction, and the like.

It can be understood that at least one terminal device in the function may be multiple; further, each terminal device may be a terminal device that has selected a target cell to which it is to be accessed; that is, in this function The method is mainly for selecting a corresponding target real-time MAC entity for at least one terminal device in the cell.

In addition, in the implementation of the function, the number of the terminal devices that determine the bearer of each real-time MAC entity and the type of the bearer service may be further included. Specifically, the fast control medium access control MAC entity determines that the at least one The scheduling instruction of the real-time MAC entity includes at least:

In other words, if the current RT-MAC entity has a large load, then it is determined It can carry fewer users, and vice versa. Further, if the load of an RT-MAC entity is large, it can be allocated a service type for carrying a small load demand. Therefore, it is possible to select a reasonable number of users or user service types for each RT-MAC (to ensure the QoS requirements of the service).

Third,

a fast control MAC entity 91, configured to determine a data transmission type for each real-time MAC entity of the at least one real-time MAC entity; wherein the data transmission type includes data transmission of a control plane, and/or data transmission of a user plane And generating the scheduling instruction based on a data transmission type corresponding to the at least one real-time MAC entity.

Fourth,

The fast control MAC entity 91 is configured to select an air interface bearer mode for the terminal device, and generate a scheduling instruction for the target real-time MAC entity of the terminal device based on the air interface bearer mode selected by the terminal device.

Specifically, the fast control MAC entity selects an air interface bearer mode for the terminal device, and the determining manner may be: using various measurement information of each terminal device reported by the RT-MAC and the physical layer (PHY), The measurement information of the terminal device accurately senses each The transmission resource requirement of the terminal device in the air interface; the content of the signaling of the RRC entity is obtained; and the air interface bearer mode is selected for each terminal device in combination with the transmission resource requirement of the air interface of each terminal device and the signaling content of the RRC entity.

Fifth,

a fast control MAC entity 91, configured to determine a target cell to which the terminal device is to be accessed; and based on the at least one real-time MAC entity corresponding to the target cell, the target cell that is accessed by the terminal device is obtained as the terminal device Allocating a second allocation result of the target real-time MAC entity; generating a scheduling instruction for the target real-time MAC entity based at least on the second allocation result.

This function is mainly for RRC to add air interface signaling or control procedures in the protocol. Follow For the classification standard of the LTE system, the above-mentioned mapping process for determining the cell for the terminal device belongs to the RRC protocol entity according to the classification standard of the LTE system. In the specific implementation, the air interface signaling that should be implemented by the RRC protocol entity is sinked, and the MAC can be directly controlled quickly. In this way, cross-cell control is implemented to further ensure the efficiency of the execution control of the solution.

Sixth,

The fast control MAC entity is specifically configured to perform at least one function adjustment on at least one entity in the data link layer.

Compression, decompression: header compression and decompression of IP packets;

Re-establishment process: data forwarding and in-order delivery;

Packets are sent in order and delivered in order;

Sending segmentation and concatenation of the data packet;

Re-establishment process: data is delivered in random order;

Packets are sent in order and delivered in order; segmentation and concatenation of transmitted packets; reassembly of data packets, retransmission (ARQ process), re-segmentation (retransmissions) According to the segmentation of the packet); the re-establishment process: the data is delivered in an out-of-order manner, which can be implemented by the RLC entity in the data link layer.

Flow control and distribution of multiple RLC or sub-link packets, distributed in FIFO order, and maintaining the SN number of the corresponding data packet; multi-RLC or sub-link data packet ordering, and sequentially submit data on each sub-link give. This can be done with a DRC entity in the data link layer.

As shown in FIG. 11, the system further includes: a PDCP entity 94, a DRC entity 95, and an RLC entity 96;

The PDCP entity 94 is configured to receive the flow control information of the RB sent by the MAC entity.

The DRC entity 95 is configured to receive the flow control information of the RB sent by the MAC entity.

The RLC entity 96 is configured to receive the flow control information of the RB sent by the MAC entity.

Specifically, the fast control MAC entity controls whether the DRC function is enabled.

The fast control MAC entity controls whether the RLC entity starts the centralized distributed mode;

The fast control MAC entity controls whether the PDCP entity starts the centralized distributed mode.

Dynamic scheduling control of PDCP/DRC/RLC functional entity functions. According to the overall control of RRC signaling (RRC through signaling configuration function optional set, MAC in the feature set Hezhong selects specific functions for PDCP/DRC/RLC) and dynamically fine-tunes PDCP/DRC/RLC functions.

Seventh,

The MAC entity 91 is fast controlled to map the radio bearer RB to the at least one real-time MAC entity within a preset time period.

PDCP/DRC/RLC radio bearer (Radio Bearer) real-time mapping scheduling control function. Based on the air interface measurement information of the terminal device reported by each RT-MAC, and/or the physical layer (PHY), the FC-MAC determines to map the PDCP/DRC/RLC RB to a specific RT-MAC in a certain period of time. Data is sent and received. That is, a specific radio bearer is set for the RT-MAC entity. The length of the above-mentioned preset time period can also be dynamically adjusted by the FC-MAC.

The eighth kind,

The fast control MAC entity 91 is configured to determine flow control information for data sent and received by the RB, and send the flow control information for the RB to at least one of a PDCP entity, a DRC entity, and an RLC entity; The flow control information for the RB is used to notify at least one of a PDCP entity, a DRC entity, and an RLC entity to control traffic of an RB mapped to at least one real-time MAC entity.

Obtaining the quality and throughput of each terminal device in the air interface, the maximum throughput of the cell, the service characteristics of each terminal device, the bearer capacity of the cell, and the characteristics of the cell (for example, the data carrying the user at a high rate) Various quantized feature values, such as a cell, a cell carrying a signalling, or a cell of a dedicated function, and related information of each channel managed by the physical layer; the relevant channel may include PDCCH/PDSCH/PUSCH/PUCCH; The resource allocation information between the cells sent by the RRC entity, the resource allocation information in the cell, and the related information stored in the system of each terminal device may also be acquired; and related information reported by the RT-MAC may be combined, for example, the load. Information and the type of service that can be carried, the resources in the cell corresponding to the RT-MAC, the currently connected terminal device, and the like; the traffic control of the data transmitted and received by the RB in combination with the foregoing multiple information, and the flow control information for each RB Send to PDCP/DRC/RLC to enable PDCP/DRC/RLC to complete flow control.

Finally, since this solution does not need to modify the function of the MAC entity set in the original protocol, it has good scalability and can quickly support a large number of users. In addition, it is still based on the functions specified in the original protocol. Between different protocol entities Tuning, so better compatibility, compatible with multiple protocol entities in 4G/5G networks.

Example VII.

Based on the foregoing embodiment, the function of the central control unit is to be able to perform big data operations, and after completing the big data operation, generate corresponding operation results, and send the generated operation results to the distribution unit;

That is, it can be understood that one fast control MAC entity can manage multiple cells; one real-time MAC entity can manage one cell; or one fast control MAC entity can correspond to one cell; and manage multiple internal real-time MAC entities.

A flow diagram of a user-centric service providing method according to an embodiment of the present application. As shown in FIG. 12, the user-centric service providing method includes the following steps:

Step 1201: The cell provides a unified physical resource application interface for the user for different service service requirements of each user.

Step 1202: The cell selects a corresponding air interface pattern and air interface resource for each user's different service service requirements, and performs the requested service for each user.

In this embodiment, the cell includes a physical layer PHY layer functional entity and a medium access control MAC layer functional entity; the PHY layer functional entity provides a physical resource for the cell, and the MAC functional entity pairs the PHY Layer functional entities are managed and controlled to provide users with a unified wireless resource and data interaction interface.

In the embodiment of the present application, the MAC function entity provides a unified radio resource interface for the user. Supporting the user with the amount of data that the user can send, and the form of the wireless resource is hidden from the user.

The user that determines the service request can send and receive data on the PHY layer function entity of multiple cells or the PHY layer function entity of multiple cells can select to send and receive data according to the user on the PHY layer function entity of each cell. The air interface signal quality dynamically selects one or more cells to support the user's data transmission and reception.

After the cell determines that the user of the service request can send and receive data on the PHY layer function entity of the multiple cells, the MAC layer function entity manages and controls the cell-level radio resources in units of cells. Specifically, the MAC layer function entity manages and controls cell-level radio resources in units of cells, including:

Setting a first MAC layer functional entity (that is, the fast control MAC entity in the foregoing embodiment), the first MAC layer functional entity and the intra-cell MAC layer functional entity (ie, the real-time MAC entity of the foregoing embodiment) are The user provides a unified cell level and intra-cell radio resource interface to jointly manage inter-cell and intra-cell radio resources.

Alternatively, the MAC layer function entity manages and controls cell-level radio resources in units of cells, including:

Selecting a second MAC layer functional entity (ie, the real-time MAC entity of the foregoing embodiment) in multiple cells, the second MAC layer functional entity and each other intra-cell MAC layer functional entity jointly provide a unified cell level for the user and The radio resource interface in the small area jointly manages the radio resources between cells and within the cell.

The essence of the technical solution of the embodiment of the present application is further clarified by specific examples below.

The user-centered service is provided in the embodiment of the present application, so that the cell becomes a user-centered cell, the cell provides a unified air interface resource form to the high-layer protocol stack, and the diversity of the air interface is shielded; the cell provides a clear service requirement for the air interface. The user-centered management of air interface radio resources.

As shown in FIG. 13 , in the user-centric wireless air interface cell scheme of the embodiment of the present application, The cell is located between the user and the air interface, and the cell serves various services applied by each user, and the cell manages various radio resources of the air interface. The cell is only responsible for providing the wireless resource service user with the sole objective of satisfying the user's business needs, and there is no mutual affiliation or management relationship between the cell and the user. Different from the 4G cell, the data link of the user in this application is decoupled from the cell, and does not generate any binding relationship.

Users are a variety of business services and a set of functions to support these services, such as voice, high-speed data services, burst packet services, interactive services, etc., support functions such as user plane and signaling plane of the protocol stack, security, mobile Sex management and so on.

An air interface is a collection of physical coverage patterns of various wireless signals. The form of the air interface is various, and may be a wireless beam (Beam), which may be a sector. A cell may be a wireless signal physical coverage form, and may be a mixture of multiple wireless signal physical coverage patterns.

Cell-to-user: Facing the different service requirements of each user, the cell provides a unified physical resource application interface for the user and provides the user with appropriate physical resources.

Cell-to-air interface: Facing a variety of air interface forms, the cell manages air interface resources, and appropriately selects appropriate air interface patterns and air interface resources according to user needs to meet user needs.

As shown in FIG. 14, the relationship between the cell, the user, and the air interface in the present solution will be described below.

Cell: In the 4G system, the PHY (Physical Layer) and the MAC (Medium Access Control) represent the radio resources and the control of the radio resources, respectively, based on the definition of the traditional PHY and MAC. New PHY and new MAC:

The PHY of this embodiment includes three parts functions: 1. Basic functions of the inherited 4G PHY and radio resource related features, such as modulation/demodulation, encoding/decoding, detection power control, and other basic physical functions, and time-frequency domain resources. , physical control channel and data channel, various reference symbols, radio resource related features; 2, 5G, enhanced part of the existing functions of the 4G PHY, such as enhancements to modulation/demodulation, encoding/decoding, etc.; New features and radio resource-related features for 5G, including airspace radio resources characterized by spatial multiplexing (such as Massive MIMO) Airspace radio resources, or Beam, or other airspace radio resources), new physical layer processing (such as adding primary filtering), new physical layer control channels, and data channels (data and control for special services) Channel), as well as various new reference symbols. In summary, the PHY represents a set of feature parameters that characterize the wireless air interface, ie all radio resources available for the air interface.

The MAC (MACcell) in the small area includes three functions: 1. The inherited 4G MAC has existing functional parts, such as basic functions including traditional radio resource control and packet processing; 2. For 5G, for 4G MAC Enhancements to functions, such as enhancements to scheduling, enhancements to packet processing capabilities; 3. New features for 5G, including the addition of various controls and processes for new PHYs, and new formats for user features Packet sending and receiving and parsing functions.

The cell has two basic functions of providing a unified radio resource application interface and managing radio resources to the air interface. The cell is a physical resource and various management and control sets for these resources. Therefore, the cell has two core features: 1. physical resources; 2. management and control for these physical resources. At the same time, the cell also needs corresponding cell-level signaling to complete the control of the air interface, such as cell broadcast, cell establishment, deletion, reconfiguration, blocking, and the like. Based on defining the PHY and the MAC within the cell, the cell is defined as:

The PHY layer function entity is the physical resource in the cell, and one PHY layer function entity uniquely determines one cell. One cell has only one PHY layer function entity, and the MAC function entity in the cell completes management and control of the PHY, and completes providing the user with the PHY layer. Unified wireless resource and data interaction interface. The PHY layer functional entity and the MAC function in the cell together form a cell. On this basis, the signaling control function of the cell itself is also included.

The PHY layer functional entity of the cell is a collection of air interface radio resources. All forms of air interfaces are embodied in the PHY of the community. The air interface may adopt various forms of antennas to bring about the diversity of air interface patterns. For example, the air interface may be a 360-degree coverage area of the omnidirectional antenna, or a 120-degree coverage area of the 8 antennas, or a large-scale antenna. a sub-antenna array of arrays A larger coverage of a 16-antenna sub-array of a large-scale antenna of 128 antennas may also be a narrow coverage of a sub-antenna array in a large-scale antenna (such as a small wireless beam), etc. Whether it is an air interface form or a combination of several air interface forms, it is a spatial domain part of a radio resource characterized by a PHY.

The MAC in the cell implements the unified interface service for the user, including providing the user with a unified radio resource interface support. Regardless of the PHY configuration, the MAC only provides the user with the amount of data that can be sent by the user. The specific radio resource form is invisible to the user. You only need to supply data according to the sending data requirements provided by the MAC. The interaction between the MAC and the user in the cell is only the data related to the service data that the user needs to send, and the data that can be sent at one time.

For the user, in order to serve the user's service, it is necessary to have relevant user signaling and control of the user, such as establishment, reconfiguration, establishment, etc. of the user, and related control of the user service data, such as flow control, Security control, etc.

Through the complete separation of user signaling and control and cell signaling, and the unified interface definition of the MAC, the complete decoupling of the user and the cell on the control plane is realized. Through the improvement of the user security algorithm (the specific algorithm improvement is not within the scope of this patent), the security mechanism of the user is independent of the cell, and the cell is only for the user to complete the air interface radio resource bearer of various data transceiving, realizing the user. Complete decoupling of the cell from the data plane; complete decoupling of the user and the cell by decoupling the control plane and the data plane. When the user needs to send data, the application is initiated to the MAC in the cell to obtain the corresponding radio resource. After receiving the user's application, the MAC in the cell selects an appropriate air interface resource based on the user service quality assurance requirement, thereby realizing User-centric wireless cell (radio resource) service.

In order to better serve the service requirements of the user, the user needs to select the radio resource in the cell according to the quality of the air interface channel of the user, that is, the cell needs to be selected.

As shown in FIG. 15, a cell definition supporting multi-cell cooperation is given based on the definition of a single cell. There are multiple cells when there are multiple PHYs.

When the user can send and receive data on multiple PHYs or multiple PHYs can choose to send and receive data, it is necessary to dynamically select the appropriate one or more cell supports according to the air interface signal quality (air interface channel quality) of the user on each PHY. User data is sent and received. At the same time, because the cell can be dynamically selected, it needs to notify the receiving end to correctly accept it. Therefore, based on the principle that the cell provides a unified radio resource interface to the user, the cross-cell MAC function is added.

Cross-cell MAC: manages and controls cell-level radio resources in units of cells, including interference coordination between cells, anti-collision scheduling between cells, dynamically scheduling available cells to users, and providing users with cell-level radio resource interfaces.

The cross-cell MAC and the intra-cell MAC jointly provide the user with a unified cell-level and intra-cell radio resource interface; and jointly manage the inter-cell and intra-cell radio resources.

The cross-cell MAC and the intra-cell MAC may be unified into one MAC functional entity, that is, the MAC functional entity has two functions of cross-cell scheduling and intra-cell scheduling.

In the user-centric wireless air interface cell scheme, after the cell level function is added, the functions of the cell include the control/management function in the cell and the cooperation function of the inter-cell, all of which belong to the MAC function. There is no change to the PHY's radio resource definition and the user refers to the definition of the included service.

As shown in FIG. 15, the technical solution of the embodiment of the present application further supports a multi-cell based cross-cell scheduling function, and the user-centered cell scheme fully implements a user-centric target:

1. For the user, the cell is quickly scheduled by the cross-carrier MAC, and the receiving and receiving data can be selected to select one or more cells with good channel quality; and when the user moves, the fast relay scheduling of the cell can be realized through fast scheduling, so that the user can be made without perception. .

2. Decoupling between the user and the used cell, there is no binding relationship. The cell is only the physical resource for the user to send and receive data. The two-level MAC is the cross-cell MAC (for example, it can be a specific implementation of the MAC entity). Mode) and intra-cell MAC (may be the foregoing embodiment Real-time scheduling of a real-time MAC entity, the radio resources in the scheduling cell and the scheduling cell do not have any impact on the user's service bearer (Serve Bearer), and can be selected in real time according to the channel quality of the user in the air interface. The radio resource that satisfies the user's service quality requirements transmits and receives data, and realizes that the cell completely serves the user.

3. Through the PHY to manage various forms of air interface, through MAC fast scheduling, the user can select the appropriate air interface shape to carry the user's data according to the user's air interface quality, and can serve the user more accurately and quickly.

Correspondingly, the device corresponding to the foregoing method includes the following modules, as shown in FIG.

An interface providing unit is configured to provide a unified physical resource application interface for the user for different service service requirements of each user;

The service development unit is configured to select a corresponding air interface configuration and air interface resources for each user's different service service requirements, and perform the requested service for each user.

The interface providing unit may be a specific implementation manner of the information acquiring unit described in the foregoing Embodiments 3 and 4;

The service development unit may be a specific implementation manner of the foregoing third and fourth signaling generation units.

Specifically, in the embodiment of the present application, the physical layer PHY layer functional entity and the medium access control MAC layer functional entity are included in the cell;

The PHY layer function entity provides physical resources for the cell, and the MAC function entity manages and controls the PHY layer function entity to provide a unified wireless resource and data interaction interface for the user.

In the embodiment of the present application, the MAC function entity provides a unified wireless resource interface support for the user, and provides the user with the amount of data that the user can send, and the wireless resource form is hidden from the user.

a determining unit, configured to determine whether a user of the service request can send and receive data on a PHY layer function entity of multiple cells, or a PHY layer function entity with multiple cells can select to send and receive data, The first selection unit is triggered when the PHY layer function entity of the multiple cells sends or receives data or the PHY layer function entity of the multiple cells is available for receiving and transmitting data;

The first selecting unit is configured to dynamically select one or more cells to support data transmission and reception of the user according to the air interface signal quality of the user on the PHY layer function entity of each cell.

After the determining unit determines that the user of the service request can send and receive data on the PHY layer function entity of the multiple cells,

The MAC layer functional entity manages and controls radio resources at the cell level in units of cells.

The method further includes: a setting unit, configured to set a first MAC layer function entity, where the first MAC layer function entity and the MAC layer function entity in each cell jointly provide a unified cell level and a radio resource interface in the cell, and complete together Small interval and management of radio resources in the cell.

a second selecting unit, configured to select a second MAC layer functional entity in multiple cells, where the second MAC layer functional entity and each other intra-cell MAC layer functional entity jointly provide a unified cell level and intra-cell wireless for the user The resource interface performs the management of radio resources between cells and within the cell.

The determining unit, the first selecting unit, the setting unit, and the second selecting unit may be one specific implementation manner of the signaling processing unit in the foregoing Embodiments 3 and 4.

In the embodiment of the present application, the cell provides a wireless resource service for the user to meet the service requirement of the user, and the cell and the user do not have any mutual affiliation or management relationship.

It should be understood by those skilled in the art that the foregoing functions of the interface providing unit 50 and the service developing unit 51 are implemented by the MAC layer function entity and the PHY layer function entity separately or in cooperation. The technical solutions described in the embodiments of the present application can be arbitrarily combined without conflict.

In addition, based on the description of the above embodiment,

The fast control MAC entity is set in a central control unit for generating control signaling; Transmitting the control signaling to at least one real-time MAC entity;

The real-time MAC entity is disposed in a distribution unit, configured to receive and process a control command sent by the fast control MAC entity.

The function of the foregoing fast control MAC entity is the same as that of the second embodiment, and details are not described herein.

The application provides a storage medium comprising a set of instructions that, when executed, cause at least one processor to perform operations including:

a fast control MAC entity determining a scheduling instruction for the at least one real-time MAC entity;

It should be noted that the storage medium provided herein can perform all the processing procedures in the foregoing method embodiments, and details are not described herein.

In addition, the embodiment further provides a fast control MAC entity, including: a processor and a memory for storing a computer program capable of running on the processor,

The processor, when the processor is configured to execute the computer program, performs a fast control MAC entity to determine a scheduling instruction for the at least one real-time MAC entity;

It should be understood that the functions performed by the foregoing processor may be described in the foregoing method embodiments, and details are not described herein.

The integrated modules described herein may also be stored in a computer readable storage medium if implemented in the form of software functional modules and sold or used as separate products. Base In this understanding, the technical solution of the present application, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium, including a plurality of instructions for making a A computer device (which may be a personal computer, a network device, or a network device, etc.) performs all or part of the methods described in various embodiments of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. . Thus, the application is not limited to any particular combination of hardware and software.

The above is only the preferred embodiment of the present application and is not intended to limit the scope of the present application.

Claims

An entity management method, the method comprising:

The fast control medium access control MAC entity determines a scheduling instruction for the at least one real-time MAC entity;

The fast control MAC entity sends the scheduling instruction to the at least one real-time MAC entity.
The method of claim 1, wherein the fast control MAC entity determines scheduling instructions for the at least one real-time MAC entity, including:

Obtaining, by the fast control MAC entity, the content of the RRC signaling from the radio resource control RRC entity;

The fast control MAC entity generates a scheduling instruction for the at least one real-time MAC entity based on the content of the RRC signaling.
The method of claim 2, wherein the RRC signaling comprises: air interface handover signaling, and/or, radio link reconfiguration signaling.
The method of claim 1, wherein the fast control MAC entity determines scheduling instructions for the at least one real-time MAC entity, including:

Obtaining a processing load and a spatial coverage condition of the at least one real-time MAC entity, and a feature parameter of the terminal device;

Assigning, by the terminal device, a target real-time MAC entity as a first allocation result, based on a processing load of the at least one real-time MAC entity and a spatial coverage condition and a feature parameter of the terminal device;

A scheduling instruction for the target real-time MAC entity is generated based at least on the first allocation result.
The method of claim 1, wherein the fast control MAC entity determines a scheduling instruction for the at least one real-time MAC entity, further comprising:

Obtaining processing load and spatial coverage of the at least one real-time MAC entity;

Determining, for each of the at least one real-time MAC entity, a number of terminal devices and/or supported service types for each of the at least one real-time MAC entity based on a processing load and a spatial coverage of the at least one real-time MAC entity;

The number of terminal devices carried by the at least one real-time MAC entity and/or the type of service supported are used as scheduling instructions.
The method of claim 1, wherein the fast control MAC entity determines a scheduling instruction for the at least one real-time MAC entity, further comprising:

Determining, for each of the at least one real-time MAC entity, a data transmission type; wherein the data transmission type comprises a data transmission of a control plane, and/or a data transmission of a user plane;

Generating the scheduling instruction based on a data transmission type corresponding to the at least one real-time MAC entity.
The method of claim 1, wherein the fast control MAC entity determines a scheduling instruction for the at least one real-time MAC entity, further comprising:

The fast control MAC entity selects an air interface bearer mode for the terminal device;

The fast control MAC entity generates a scheduling instruction for the target real-time MAC entity of the terminal device based on the air interface bearer mode selected by the terminal device.
The method of claim 1, wherein the fast control MAC entity determines scheduling instructions for the at least one real-time MAC entity, including:

Determining, by the fast control MAC entity, a target cell to which the terminal device is to be accessed;

Determining, according to the at least one real-time MAC entity corresponding to the target cell, a second allocation result of the target real-time MAC entity, according to the target cell that is accessed by the terminal device;

Generating a schedule for the target real-time MAC entity based at least on the second allocation result instruction.
The method of any of claims 1-8, wherein the method further comprises:

The fast control MAC entity performs at least one function adjustment on at least one entity in the data link layer.
The method according to any one of claims 1-8, wherein the fast control MAC entity determines a scheduling instruction for the at least one real-time MAC entity, further comprising:

The fast control MAC maps the radio bearer RB to the at least one real-time MAC entity within a preset time period.
The method of claim 10, wherein the method further comprises:

The fast control MAC entity determines flow control information for data sent and received by the RB, and sends the flow control information for the RB to at least one entity in the data link layer;

The traffic control information for the RB is used by at least one entity in the data link layer to control traffic of an RB mapped to at least one real-time MAC entity.
The method of claim 1 wherein the method further comprises:

Generating control signaling by rapidly controlling the MAC entity; wherein the fast control MAC entity is set in the central control unit;

The fast control MAC entity sends the control signaling to at least one real-time MAC entity; wherein each of the at least one real-time MAC entity is disposed in a distribution unit, and each of the distribution units can be set A real-time MAC entity or multiple real-time MAC entities.
The method of claim 12, wherein the generating control signaling by the fast control MAC entity comprises:

The content of the RRC signaling is obtained from the radio resource control RRC entity by the fast control MAC entity; the fast control MAC entity generates control signaling based on the content of the RRC signaling.
The method of claim 12, wherein the method further comprises:

Obtaining air interface resource information by quickly controlling a terminal device radio resource management function in the MAC entity;

and / or,

Obtaining channel quality information by quickly controlling a channel quality management function of a terminal device in a MAC entity;

and / or,

The wireless air interface quality information of each cell is obtained by quickly controlling the inter-cell wireless air interface quality management function in the MAC entity.
The method of claim 14, wherein the generating control signaling by the fast control MAC entity comprises:

The fast control MAC entity allocates a target cell to the terminal device according to at least one of air interface resource information, channel quality information, and wireless air interface quality information of each cell;

Allocating a target real-time MAC entity to the terminal device based on a target cell allocated for the terminal device, and allocating, for the terminal device, a size of a data unit to be transmitted in the target cell;

Taking the target real-time MAC entity and the size of the data unit as a third allocation result;

A control instruction for the target real-time MAC entity is generated based at least on the third allocation result.
The method of claim 15 wherein the method further comprises:

Assigning a radio bearer RB to the terminal device by using a fast control MAC entity;

The assigned RBs are mapped to the target real-time MAC entity.
The method of claim 15, wherein the generating the control signaling by the fast control MAC entity further comprises:

The fast control MAC entity selects an air interface bearer mode for the terminal device;

The fast control MAC entity is based on an air interface bearer mode selected for the terminal device. A control instruction for a target real-time MAC entity of the terminal device in the said terminal device.
The method of claim 12, wherein the generating control signaling by the fast control MAC entity comprises:

Determining, for each of the at least one real-time MAC entity, a data transmission type; wherein the data transmission type comprises a data transmission of a control plane, and/or a data transmission of a user plane;

Generating the control instruction based on a data transmission type corresponding to the at least one real-time MAC entity.
The method of claim 12, wherein the method further comprises:

The function adjustment is performed on at least one entity at the data link layer by the fast control MAC entity.
The method of any of claims 12-19, wherein the method further comprises:

And obtaining, by the fast control MAC entity, the uplink signaling uploaded by the at least one terminal device from the at least one real-time MAC entity, and parsing and processing the uplink signaling.
A fast control MAC entity, the fast control MAC entity, including:

An instruction generation unit configured to determine a scheduling instruction for the at least one real-time MAC entity;

And an information sending unit, configured to send the scheduling instruction to the at least one real-time MAC entity.
The fast control MAC entity according to claim 21, wherein the fast control MAC entity further comprises:

An information acquiring unit, configured to acquire content of the RRC signaling from the radio resource control RRC entity;

Correspondingly, the instruction generating unit is configured to generate a scheduling instruction for the at least one real-time MAC entity based on the content of the RRC signaling.
The fast control MAC entity according to claim 22, wherein said RRC letter The commands include: air interface switching signaling and/or radio link reconfiguration signaling.
The fast control MAC entity according to claim 21, wherein the fast control MAC entity further comprises:

An information acquiring unit, configured to acquire a processing load and a spatial coverage of the at least one real-time MAC entity, and a feature parameter of the terminal device;

Correspondingly, the instruction generating unit is configured to allocate the target real-time MAC entity as the first allocation result to the terminal device based on the processing load of the at least one real-time MAC entity and the spatial coverage and the feature parameter of the terminal device; A scheduling instruction for the target real-time MAC entity is generated based on the first allocation result.
The fast control MAC entity according to claim 21, wherein the fast control MAC entity further comprises:

An information acquiring unit, configured to acquire a processing load and a spatial coverage of the at least one real-time MAC entity;

Correspondingly, the instruction generating unit is configured to determine, according to processing load and spatial coverage of the at least one real-time MAC entity, the number of terminal devices that are carried by each real-time MAC entity in the at least one real-time MAC entity. And/or a type of service supported; the number of terminal devices carried by the at least one real-time MAC entity and/or the type of service supported is used as a scheduling instruction.
The fast control MAC entity according to claim 21, wherein

The instruction generating unit is configured to determine a data transmission type for each real-time MAC entity of the at least one real-time MAC entity, where the data transmission type includes data transmission of a control plane, and/or data transmission of a user plane And generating the scheduling instruction based on a data transmission type corresponding to the at least one real-time MAC entity.
The fast control MAC entity according to claim 21, wherein

The command generating unit is configured to select an air interface bearer mode for the terminal device; And generating, for the air interface bearer mode of the terminal device, a scheduling instruction for the target real-time MAC entity of the terminal device.
The fast control MAC entity according to claim 21, wherein the instruction generating unit is configured to determine a target cell to which the terminal device is to be accessed; and to correspond to the target cell according to the target cell accessed by the terminal device And at least one real-time MAC entity obtains a second allocation result of allocating a target real-time MAC entity to the terminal device; and generates a scheduling instruction for the target real-time MAC entity based at least on the second allocation result.
The fast control MAC entity according to any one of claims 21 to 28, wherein the fast control MAC entity further comprises:

The adjusting unit is configured to perform at least one function adjustment on at least one entity in the data link layer.
The fast control MAC entity according to any one of claims 21-28, wherein the fast control MAC entity further comprises:

And an adjusting unit configured to map the radio bearer RB to the at least one real-time MAC entity within a preset time period.
The fast control MAC entity according to claim 30, wherein the adjusting unit is configured to determine flow control information for data transmitted and received by the RB, and send the flow control information for the RB to a data link layer At least one entity;

The traffic control information for the RB is used by at least one entity in the data link layer to control traffic of an RB mapped to at least one real-time MAC entity.
The fast control MAC entity according to claim 21, wherein

The signaling generating unit is configured to generate control signaling by using

The signaling sending unit is configured to send the control signaling to at least one real-time MAC entity.
A fast control MAC entity according to claim 32, wherein

The signaling generating unit is configured to acquire content of the RRC signaling from the radio resource control RRC entity, and generate control signaling based on the content of the RRC signaling.
The fast control MAC entity according to claim 32, wherein the fast control MAC entity further comprises:

a radio resource management unit configured to obtain air interface resource information;

and / or,

a channel quality management unit configured to acquire channel quality information;

and / or,

The small-area wireless air interface quality management unit is configured to obtain wireless air interface quality information of each cell.
A fast control MAC entity according to claim 32, wherein

The signaling generating unit is configured to allocate a target cell to the terminal device according to at least one of the air interface resource information, the channel quality information, and the wireless air interface quality information of each cell; and the target cell allocated for the terminal device is the The terminal device allocates a target real-time MAC entity, and allocates, to the terminal device, a size of a data unit that is transmitted in the target cell; and uses the target real-time MAC entity and the size of the data unit as a first allocation result; The first allocation result generates a control instruction for the target real-time MAC entity.
The fast control MAC entity according to claim 35, wherein the signaling generating unit is configured to allocate a radio bearer RB for the terminal device; and map the allocated RB to the target real-time MAC entity.
The fast control MAC entity according to claim 35, wherein the signaling generating unit is configured to select an air interface bearer mode for the terminal device, and generate an air interface bearer mode selected by the terminal device, The control instruction of the target real-time MAC entity of the terminal device.
A fast control MAC entity according to claim 32, wherein said a signaling generating unit, configured to determine, for each real-time MAC entity in the at least one real-time MAC entity, a data transmission type, where the data transmission type includes data transmission of a control plane, and/or data transmission of a user plane; Generating the control instruction based on a data transmission type corresponding to the at least one real-time MAC entity.
The fast control MAC entity according to claim 32, wherein the signaling generating unit is configured to perform function adjustment on at least one entity at a data link layer.
The fast control MAC entity according to any one of claims 32 to 39, wherein the fast control MAC entity further comprises:

The signaling processing unit is configured to acquire uplink signaling uploaded by the at least one terminal device from the at least one real-time MAC entity, and parse and process the uplink signaling.
An entity management system, the system comprising: a fast control MAC entity and at least one real-time MAC entity; wherein

Quickly controlling a MAC entity, configured to determine a scheduling instruction for the at least one real-time MAC entity; transmitting the scheduling instruction to the at least one real-time MAC entity;

The real-time MAC entity is configured to receive a scheduling instruction sent by the fast control MAC entity, and process according to the scheduling instruction.
The system of claim 41 wherein said system further comprises:

An RRC entity configured to provide RRC signaling content for a fast control MAC entity;

Correspondingly, the fast control MAC entity is configured to generate a scheduling instruction for the at least one real-time MAC entity based on the content of the RRC signaling.
The system of claim 41, wherein

The fast control MAC entity, configured in the central control unit, configured to generate control signaling; and send the control signaling to at least one real-time MAC entity;

The real-time MAC entity, configured in a distribution unit, configured to receive and process a control command sent by the fast control MAC entity
A fast control MAC entity comprising: a processor and a memory for storing a computer program capable of running on the processor,

Wherein the processor is operative to perform the steps of the method of any one of claims 1-20 when the computer program is run.
A storage medium having stored thereon a computer program, wherein the computer program is executed by a processor to perform the steps of the method of any of claims 1-20.