CN107484250B

CN107484250B - Entity management method, quick control medium access control entity and system

Info

Publication number: CN107484250B
Application number: CN201610403739.6A
Authority: CN
Inventors: 孙军帅; 王莹莹; 黄学艳; 陈锋; 陈卓; 易芝玲
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Priority date: 2016-06-07
Filing date: 2016-06-07
Publication date: 2020-10-02
Anticipated expiration: 2036-06-07
Also published as: CN107484250A

Abstract

The invention discloses an entity management method, a rapid control Medium Access Control (MAC) entity and a system, wherein the method comprises the following steps: the fast control MAC entity determines a scheduling instruction for the 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, quick control medium access control entity and system

Technical Field

The present invention relates to an entity management technology in the field of communications, and in particular, to an entity management method, a fast control Medium Access Control (MAC) entity, and a system.

Background

An access network Protocol stack scheme as shown in fig. 1 is provided for the requirement of 5G, where the Control plane is Radio Resource Control (RRC), and the user plane is Packet Data Convergence Protocol (PDCP)/Radio Link Control Protocol (RLC)/Media Access Control (MAC)/Physical (PHY). The following new definitions are made for the distributed network architecture: an Inter Cell (Inter Cell) MAC function module is newly added to manage the control with the real-time performance higher than that of RRC; a function module of new Data ordering and Control (DRC) for managing the distribution and reception of Radio Bearer (RB) Data and the Control of RLC center/rlcreate; and the RRC is added with an air interface signaling function, and flexibly configures the PDCP/RLC or DRC function according to different access network architectures so as to adapt to ideal and non-ideal access network architectures. However, the above-mentioned architecture cannot guarantee fast performing related control processing through air interface signaling.

Disclosure of Invention

In view of the above, the present invention provides an entity management method, a fast control MAC entity and a system thereof, which can at least solve the above problems in the prior art.

In order to achieve the purpose, the technical scheme of the invention is realized as follows:

the embodiment of the invention provides an entity management method, which comprises the following steps:

the 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.

The embodiment of the present invention further provides a MAC entity for fast control, including:

an instruction generating unit for determining a scheduling instruction for at least one real-time MAC entity;

and the information sending unit is used for sending the scheduling instruction to the at least one real-time MAC entity.

An embodiment of the present invention further provides an entity management system, where the system includes: a fast control MAC entity and at least one real-time MAC entity; wherein the content of the first and second substances,

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

and the real-time MAC entity is used for receiving the scheduling instruction sent by the quick control MAC entity and processing according to the scheduling instruction.

The embodiment of the invention provides an entity management method, a quick control MAC entity and a system, which can divide MAC protocol entities into two types, namely the quick control MAC entity and at least one real-time MAC entity, and the quick control MAC entity carries out scheduling on the at least one real-time MAC entity. Therefore, the scheduling and control of at least one MAC entity can be completed on the MAC layer, the issue of air interface signaling is guaranteed to be completed quickly, and the processing speed of the whole framework is improved.

Drawings

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

FIG. 2 is a flowchart illustrating an entity management method according to an embodiment of the present invention;

FIG. 3 is a functional partitioning diagram of an FC MAC entity according to an embodiment of the present invention;

FIG. 4 is a schematic diagram of a structure between entities according to an embodiment of the present invention;

fig. 5a is a first schematic diagram illustrating signaling transmission according to an embodiment of the present invention;

fig. 5b is a diagram illustrating signaling transmission according to an embodiment of the present invention;

fig. 5c is a third schematic diagram illustrating signaling transmission according to an embodiment of the present invention;

fig. 6 is a first schematic diagram illustrating a fast control MAC entity structure according to an embodiment of the present invention;

fig. 7 is a schematic diagram illustrating a second structure of a fast control MAC entity according to an embodiment of the present invention;

fig. 8 is a schematic diagram illustrating a third structure of a fast control MAC entity according to an embodiment of the present invention;

FIG. 9 is a first block diagram illustrating an entity management system according to an embodiment of the present invention;

FIG. 10 is a schematic diagram of a second embodiment of the entity management system;

fig. 11 is a third schematic structural diagram of an entity management system according to an embodiment of the present invention.

Detailed Description

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

The first embodiment,

An embodiment of the present invention provides an entity management method, as shown in fig. 2, the method includes:

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

step 202: and the fast control MAC entity sends the scheduling instruction to the at least one real-time MAC entity.

The embodiment of the invention provides a general-split type MAC scheme with air interface rapid signaling capability aiming at the distributed architecture and air interface characteristic requirements of a 5G access network and the limitation problem of the existing MAC protocol entity function, and the scheme adds a new processing function on the basis of being compatible with the existing MAC protocol stack function.

The general scheme of the MAC protocol entity functions is shown in fig. 3. In this embodiment, the MAC protocol entity function is divided into two functional modules: fast Control (FC) -MAC entities and real-time (RT) -MAC entities.

Among them, FC-MAC is divided into three functions of Fast Signaling Control (FAST SIGNALING CONTROL), flow Control (FLOWCONTROL), and RT-MAC scheduling Control (RT-MAC CONTROL). The RT-MAC is the existing or existing conventional MAC protocol entity function and its subsequent evolution function.

In order to ensure the compatibility of a protocol stack, the traditional MAC functions including an evolution function are uniformly defined as RT-MAC, so that the control of corresponding processes of user scheduling in a cell, wireless resource allocation in the cell and users and wireless resources in the cell is completed, and the RT-MAC functions only focus on the corresponding MAC functions in the cell.

The FC-MAC function is a newly added MAC function, and the relationship between the fast signaling (RC) -MAC entity and the RT-MAC entity is as follows: all MAC entities consist of FC MAC entities and RT MAC entities; and there is no intersection between FC MAC entities and RT MAC entities. The FC-MAC does not change the basic function of the RT-MAC so as to ensure the complete compatibility of the total-fraction MAC scheme to the original MAC.

Specifically, as shown in FIG. 3, the FC-MAC essentially comprises three major functions: the assumed fast control function, namely the control process of interaction through RRC signaling, sinks to MAC and carries out fast control function through air interface scheduling; controlling the distribution quantity of data on PDCP/DRC/RLC by the RB flow control function of the user data link through the empty information of the user; scheduling control procedures for RT-MAC (not including signaling control functions) that focus on performing scheduling for RT-MAC and non-signaling control functions needed to perform scheduling.

The following describes various functions and implementations of the FC MAC entity in detail with reference to fig. 4, fig. 5a, fig. 5b, and fig. 5 c:

a first kind,

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

the rapid control MAC entity acquires the content of RRC signaling from a Radio Resource Control (RRC) entity; and the fast control MAC entity generates a scheduling instruction aiming at the at least one real-time MAC entity based on the content of the RRC signaling.

Or, the MAC entity may further generate corresponding air interface control according to a user behavior (e.g., a channel quality of a user, a capability of the user, and a service characteristic required by the user), and further generate a scheduling instruction in combination with the air interface control.

Wherein the generating the scheduling instruction for the at least one real-time MAC entity may include: the rapid Control MAC entity encapsulates the scheduling command through a preset special PDCCH or a defined MAC Control Element (CE).

Specifically, for example, referring to fig. 4, the fast control MAC entity accepts RRC protocol signaling functions, which include: the signaling function of the original RRC protocol entity needs to implement fast control and sink to the MAC function.

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

That is, the related signaling for air interface switching is sunk to the MAC entity for fast Control, and the Control may be performed by sending a special PDCCH or a defined MAC Control Element (CE) through FC-MAC, as in the conventional method of controlling through RRC air interface signaling.

For another example, in order to implement Seamless (Seamless) handover of air interface, the FC-MAC is used to send link control signaling to replace the radio link reconfiguration signaling of the original RRC protocol entity.

Further, with reference to fig. 5a, a description is given of a signaling procedure of RRC sinking, that is, a processing flow of wrapping information acquired by the RRC entity and generating a scheduling instruction to send to the RT-MAC entity:

step 51-1, the RRC entity of the Base Station (Base Station) determines according to the corresponding algorithm that a corresponding signaling needs to be generated, and generates FC-MAC sending Control information (Control Indication) sent to the Base Station according to the signaling, where the Control Indication only contains specific contents inside the specific signaling, and the content of the signaling is clearly described without being converted into a format (asn.1 format) binary stream of an RRC air interface signaling. The generated signaling may be designated signaling that needs to sink, such as the above-mentioned example related signaling for air interface switching and related signaling for seamless switching, and in addition, the specific signaling is only an example, and may be set according to actual needs in an actual processing process.

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 then sends a Scheduling instruction (Scheduling Ind) to the RT-MAC, and the RT-MAC of the Base Station is instructed by the Scheduling instruction to send a control information air interface signaling to the corresponding terminal equipment. Here, it should be noted that, in addition to the above-mentioned control information, the scheduling command generated in this step may be a corresponding scheduling command generated in accordance with information such as the characteristic information of the terminal device and the load of the RT-MAC entity. For specific reference to the processing of generating the scheduling instruction by combining with other information, reference may be made to descriptions of other functions in this embodiment, which are not described herein again.

So far, the interaction process between the fast control MAC entity and the RT MAC entity of the first function is completed.

The following also describes the interaction processing flow between the RT-MAC entity and the terminal device side with reference to fig. 5 a:

and step 51-3, the RT-AMC on the base station side determines control information to be sent to the terminal equipment (UE) according to the scheduling information and generates a data packet, and further performs information transmission on the data packet with the UE, so that the RT-MAC on the UE side starts an air interface HARQ process of the MAC to complete the transceiving and the acknowledgement of the data packet.

And step 51-4, after the RT-MAC of the UE correctly receives the MAC data Packet (Packet), analyzing the data Packet to obtain control information, and reporting the control information to an FC-MAC entity at the UE side.

And step 51-5, after receiving the reported Control information, the FC-MAC of the UE completes a corresponding operation according to the Control information, and sends an application of application Control information (Control application) 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 Control information (Control Indication) to the FC-MAC of the UE, namely, sends authorization information to the FC-MAC.

And 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.

And step 51-8, the RT-MAC of the UE uses the HARQ process of the MAC to complete the transmission of the feedback information by the air interface confirmed by the signaling.

And step 51-9, after receiving the acknowledgement, the RT-MAC of the Base Station sends acknowledgement information (Scheduling ACK) aiming at the Scheduling information to the FC-MAC for acknowledgement.

And step 51-10, the FC-MAC of the Base Station sends Control information acknowledgement Control ACK to the RRC of the Base Station, and confirms that the air interface signaling process is ended.

And 51-11, the RT-MAC of the UE sends control information confirmation control confirmation information ControlACK to the FC-MAC of the UE to indicate that the air interface transmission in the signaling process is successful.

And step 51-12, the FC-MAC of the UE sends a Control acknowledgement (Control ACK) to the RRC of the UE to indicate that the signaling process completes configuration.

A second kind,

The fast control Medium Access Control (MAC) entity determines a scheduling instruction for the at least one real-time MAC entity, and the scheduling instruction at least comprises the following steps:

acquiring the processing load and the space coverage condition of the at least one real-time MAC entity and the characteristic parameters of the terminal equipment; allocating a target real-time MAC entity to the terminal equipment as a first allocation result based on the processing load and the space coverage condition of the at least one real-time MAC entity and the characteristic parameters of the terminal equipment; generating scheduling instructions for the target real-time MAC entity based at least on the first allocation results.

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

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

the method comprises the steps of obtaining processing load and corresponding space coverage in at least one real-time MAC entity managed by the terminal device, and obtaining various air interface characteristic parameters, cell characteristic parameters and user characteristic parameters, such as air interface quality, adjacent cell air interface quality, moving direction and the like reported by at least one terminal device.

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

It is understood that, in the present function, at least one terminal device may be plural; further, each terminal device may be a terminal device that has selected a target cell to which the terminal device is to access; that is, the present function is mainly directed to selecting a corresponding target real-time MAC entity for at least one terminal device in a cell.

Specifically, the method for selecting the target real-time MAC entity for the terminal device may be to select a proper RT-MAC for each user to receive and transmit data by combining the cell served by each real-time MAC entity, the service type of the terminal device supported, and the current load of the real-time MAC entity, and then combining the air interface quality of the terminal device, the air interface quality of the neighboring cell, and the moving direction.

In addition, in the implementation of the function, the method may further include determining the number of terminal devices and the type of service of the bearer of each real-time MAC entity, which are specifically as follows:

the fast control medium access control, MAC, entity determining scheduling instructions for the at least one real-time MAC entity, further comprising at least:

acquiring the processing load and the space coverage condition of the at least one real-time MAC entity and the characteristic parameters of the terminal equipment;

determining the number of terminal devices borne by each real-time MAC entity and/or the type of service supported by the real-time MAC entity based on the processing load and the spatial coverage condition of the at least one real-time MAC entity and the characteristic parameters of the terminal devices;

and taking the number of the terminal devices and/or the supported service types carried by the at least one real-time MAC entity as a scheduling instruction.

That is, if the load of a RT-MAC entity is larger, it is determined that the number of users that it can carry is smaller, and vice versa. Further, if a RT-MAC entity is heavily loaded, it can be allocated a traffic type with less load requirement for carrying. Thereby realizing the selection of a reasonable number of users or user traffic types (capable of ensuring the QoS requirements of the traffic) of the bearer for each RT-MAC.

The connection relationship between the fast control MAC entity and the real-time MAC entity in the second function can be seen in fig. 4. The control of the bidirectional dynamic real-time mapping between the user, i.e. the terminal equipment, and the real-time MAC entity by the fast control MAC can be realized through the functions.

A third one,

The fast control medium access control, MAC, entity determining scheduling instructions for the at least one real-time MAC entity, further comprising:

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

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

In particular, for example, see fig. 4, dynamic scheduling control of RT-MAC real-time functions. According to the overall Control of RRC signaling (RRC configures a function optional set through signaling, and MAC selects a specific function for RT-MAC in the function set), scheduling Control is carried out on the RT-MAC function, including whether only Control Plane (Control Plane) or User Plane (User Plane) corresponding data is transmitted and received or not, or whether Control Plane and User Plane data can be transmitted and received simultaneously.

A fourth step of,

the quick control MAC entity selects an air interface bearing mode for the terminal equipment;

and the quick control MAC entity generates a scheduling instruction aiming at a target real-time MAC entity of the terminal equipment based on the air interface bearing mode selected for the terminal equipment.

Specifically, the fast control MAC entity selects an air interface bearer mode for the terminal device, and the determining mode may be: various measurement information of each terminal device is reported through an RT-MAC and a physical layer (PHY), and the transmission resource requirement of each terminal device at an air interface is accurately sensed through the measurement information of each terminal device; acquiring the content of signaling of an RRC entity; and selecting an air interface bearing mode for each terminal device by combining the transmission resource requirement of each terminal device at the air interface and the content of the signaling of the RRC entity.

The content of the signaling of the RRC entity is obtained, the RRC entity may still perform the allocation of the air interface bearer mode for the terminal device, but no specific signaling is generated, and the air interface bearer mode is sent to the fast control MAC entity, so that the fast control MAC entity generates the scheduling instruction based on the allocated air interface bearer mode. For a specific implementation process, see fig. 5a, which is not described herein again.

The selected air interface bearing mode can use an OFDM + CDMA mode to bear data and signaling of users, or use a non-orthogonal physical layer technology to start rapid data receiving and transmitting of some users. In this embodiment, the air interface bearer modes of the terminal device are not exhaustive.

A fifth step of,

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

the rapid control medium access control MAC entity determines a target cell to which the terminal equipment is accessed;

acquiring a second allocation result of allocating a target real-time MAC entity to the terminal equipment according to at least one real-time MAC entity corresponding to the target cell based on the target cell accessed by the terminal equipment;

generating scheduling instructions for the target real-time MAC entity based at least on the second allocation results.

The specific manner of obtaining the second allocation result of the target real-time MAC entity allocated to the terminal device may be to perform matching according to a cell served by the real-time MAC entity and a target cell to which the terminal device is to access, and determine the target real-time MAC entity based on a matching result.

Further, the allocation of the target real-time MAC entity to the terminal device may refer to at least one of the second to fourth functions, that is, a scheduling instruction may be generated jointly by an air interface bearer mode, a supported service type, the number of terminal devices that can be carried, and a target cell to be served in the function of each real-time MAC entity.

The function is mainly aimed at the new adding of air interface signaling or control process in the protocol by RRC. According to the classification standard of the LTE system, the 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 of the scheme, the air interface signaling which is realized by the RRC protocol entity is sunk, and the MAC directly carries out rapid control. Therefore, cross-cell control is realized, and the control execution efficiency of the scheme is further ensured.

In addition, the specific signaling processing flow and information interaction process for sinking the new function of the RRC entity may be implemented as follows with reference to fig. 5 b:

regarding the new fast signaling procedure:

step 52-1, the FC-MAC of the Base Station determines that a fast control process needs to be started according to a corresponding decision algorithm, generates a control signaling corresponding to the fast control process, and the FC-MAC of the Base Station generates and sends a Scheduling instruction Scheduling Ind to the RT-MAC of the Base Station based on the control information, so as to instruct the RT-MAC of the Base Station to send the air interface signaling. Further, the generated scheduling instruction may include, in addition to the control information generated based on the FC-MAC entity itself, a load based on each RT-MAC entity, and air interface measurement and characteristic information of each terminal device reported by the physical layer.

After receiving the scheduling instruction, the RT-MAC entity in the Base Station in step 52-2 generates a data Packet (Packet) for the UE peer according to the scheduling instruction and the control information contained in the scheduling instruction, and then the RT-MAC starts an air interface HARQ process of the MAC to complete the transceiving and acknowledgement of the Packet of the data Packet.

And step 52-3, after the RT-MAC of the UE correctly receives the MAC data Packet, sending a Report Control signaling Control Report to the FC-MAC of the UE.

And step 52-4, after receiving the Control Report, the FC-MAC of the UE completes the operation corresponding to the Control signaling, and sends a Control rsp response to the Control signaling to the RT-MAC of the UE to indicate the result of the signaling execution.

And step 52-5, the RT-MAC of the UE completes the air interface transmission of the signaling confirmation by using the HARQ process of the MAC.

And step 52-6, after the RT-MAC of the Base Station receives the confirmation, sending the confirmation to the FC-MAC.

And step 52-7, the RT-MAC of the UE sends a Control acknowledgement ACK to the FC-MAC of the UE to indicate that the air interface transmission of the signaling process is successful.

A sixth kind,

The method further comprises the following steps:

the fast control MAC entity performs at least one function adjustment on at least one entity in the data link layer.

In particular, the at least one entity may be provided with at least one of the following functions:

compression and decompression: header compression and decapsulation of the IP packet;

safety: encryption and decryption or integrity protection of data packets, including maintenance of data packet serial numbers;

and (3) reestablishing: data forwarding and in-order delivery;

sending and submitting data packets in sequence;

segmentation and concatenation of the transmission packets (concatenation);

reassembly of data packets, retransmission (ARQ process), re-fragmentation (fragmented transmission of retransmitted data packets);

and (3) reestablishing: out-of-order delivery of data;

flow control and distribution of multiple RLC or sub-link data packets are distributed according to the FIFO sequence, and SN numbers of corresponding data packets are maintained;

and sequencing a plurality of RLC or sub-link data packets, and submitting the data on each sub-link in sequence.

Specifically, compression, decompression, header compression and decompression of an IP packet; security, encryption and decryption or integrity protection of data packets, including maintenance of data packet serial numbers; a reestablishment process, data forwarding and sequential submission; the in-sequence sending and in-sequence delivery of the data packets can be realized by a PDCP entity in the data link layer.

Sending and submitting data packets in sequence; segmentation and concatenation of the transmission packets (concatenation); reassembly of data packets, retransmission (ARQ process), re-fragmentation (fragmented transmission of retransmitted data packets); and (3) reestablishing: the out-of-order delivery of data can be implemented by using an RLC entity in the data link layer.

Flow control and distribution of multiple RLC or sub-link data packets are distributed according to the FIFO sequence, and SN numbers of corresponding data packets are maintained; and sequencing a plurality of RLC or sub-link data packets, and submitting the data on each sub-link in sequence. This may be implemented using DRC entities 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 implementation, and other entities may be used in the implementation, and the specific implementation of the entity is not limited in this embodiment.

The rapid control MAC entity adjusts at least one function of the PDCP entity;

the rapid control MAC entity adjusts at least one function of the DRC entity;

and the rapid control MAC entity adjusts at least one function of the RLC entity.

For example, referring to fig. 4, the MAC entity is controlled to establish a connection with the PDCP entity, the DRC entity, and the RLC entity, and perform a function adjustment on the above entities based on the connection.

Specifically, the adjusting, by the fast control MAC entity, at least one function of the DRC entity includes: controlling whether to turn on the DRC function;

the fast control MAC entity adjusts at least one function of a radio link layer control protocol (RLC) entity, and comprises the following steps: controlling whether the RLC entity starts a centralized distributed mode;

the fast control MAC entity carries out at least one function adjustment on a packet data convergence protocol PDCP entity, and comprises the following steps: controlling whether the PDCP entity starts a centralized distributed mode.

A dynamic scheduling control function of the PDCP/DRC/RLC functional entity function. The PDCP/DRC/RLC functions are dynamically fine-tuned according to the overall control of RRC signaling (RRC configures an optional set of functions in which MAC selects a specific function for PDCP/DRC/RLC).

For example, it may include: whether DRC function is required, i.e. whether DRC can be transmitted transparently; whether PDCP/RLC enables centralized-distributed mode, etc.

The DRC function module is mainly used for completing the control of distributing data received from the PDCP to the RLC center/RLC remote and sequentially submitting the data to the PDCP and the RLC center/RLC remote after receiving and recombining the data from the RLC center/RLC remote;

the RLC Entity may include an RLC center and an RLC remote function Entity, and the two function entities are Mutually exclusive (explicit RLC Entity), that is, when the RLC center exists, the RLC create does not exist, and similarly, when the RLC remote exists, the RLC center does not exist.

It should be understood that the function is also a function added in the RRC entity in the 5G protocol, and the present solution sinks the function into the RC-MAC entity for performing, so that the control on entities such as PDCP, DRC, RLC, and the like can be faster.

A seventh one,

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

Radio Bearer (RB) real-time mapping scheduling control function of PDCP/DRC/RLC. And the FC-MAC decides to map the RB of the PDCP/DRC/RLC to the specific RT-MAC for data receiving and transmitting in a certain time period according to the air interface measurement information of the terminal equipment reported by each RT-MAC and/or a physical layer (PHY). I.e. setting a specific radio bearer for the RT-MAC entity. The FC-MAC can dynamically adjust the length of the preset time period.

The eighth kind,

The fast control MAC entity determines flow control information for data transmitted and received by an RB and transmits the flow control information for the RB to at least one entity in a data link layer;

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

For the functions of at least one entity in the data link layer, reference may be made to the description in the sixth function, which is not described herein again.

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

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

It is understood that this function may be combined with the seventh function for processing, that is, after the 7 th function, that is, after determining the RB allocated to each RT-MAC entity, this function may be used to control the specific flow of the RB;

this function may not be used in combination with the seventh function, and the specific use manner may be determined according to the actual situation, which is not limited in this embodiment.

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

acquiring quality and throughput of each terminal device at an air interface, maximum throughput of a cell, service characteristics of each terminal device, bearing capacity of the cell, characteristics of the cell (such as a cell specially bearing high-rate data of a user, a cell specially bearing signaling, or other cells with special functions) and other various quantitative characteristic values reported by a physical layer, and related information of each channel managed by the physical layer; the related channels can comprise PDCCH/PDSCH/PUSCH/PUCCH;

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

related information reported by the RT-MAC, such as load information, service types capable of being carried, resources in a cell corresponding to the RT-MAC, information of currently connected terminal equipment and the like, can also be combined;

and performing flow control on data transmitted and received by the RBs by combining the plurality of information, and transmitting the flow control information aiming at each RB to the PDCP/DRC/RLC so that the PDCP/DRC/RLC completes flow control.

The seventh function and the eighth function are described below with reference to fig. 5c, with respect to the newly added fast control flow:

step 53-1, the RRC in the Base Station decides to send Control information Control Info to the FC-MAC in the Base Station in a certain manner according to a corresponding algorithm, for example, the Control information Control Info may include information indicating the resources within the cell and the resources between the cells controlled by the RRC, and related information of each UE stored in the system.

And step 53-2, the RT-MAC of the Base Station sends Control information Control Info to the FC-MAC of the Base Station according to a corresponding algorithm decision in a certain mode, and indicates the resources in the cell controlled by the RT-MAC of the Base Station in real time and related information of the UE connected with the resource, such as identification information of the UE.

Step 53-3, the PHY of the Base Station decides to send Control information Control Info to the FC-MAC of the Base Station in a certain manner according to the corresponding algorithm for indicating real-time related information of the physical layer (PHY), for example, related information of each channel managed by the physical layer.

Step 53-4, the FC-MAC of the Base Station judges according to the corresponding algorithm, needs to generate the corresponding fast Control process, sends Control information Control Ind to the PDCP/DRC/RLC of the Base Station, and indicates the fast Control process required by the FC-MAC of the Base Station. Here, the flow control information of the RB may be sent to at least one of the PDCP/DRC/RLC entities, but in the actual processing procedure, the FC-MAC entity may also send other control information like at least one of the above entities, which is not exhaustive in this embodiment.

And step 53-5, the FC-MAC of the Base Station needs to generate a corresponding rapid control process according to the corresponding judgment, sends a scheduling instruction to the RT-MAC of the Base Station, and instructs the RT-MAC of the Base Station to send the air interface signaling according to the scheduling instruction.

And step 53-6, starting an air interface HARQ process of the MAC by the Base Station and the RT-MAC of the opposite end of the UE, and finishing the transceiving and the confirmation of the Packet.

And step 53-7, after the RT-MAC of the UE correctly receives the MAC Packet, sending Control information Control Info to the FC-MAC of the UE.

And step 53-8, after receiving the Control Report, the FC-MAC of the UE completes the corresponding operation and sends Control Info to the PDCP/DRC/RLC of the UE to indicate the rapid Control process.

Therefore, by adopting the scheme, the MAC protocol entities can be divided into two types, namely the quick control MAC entity and the at least one real-time MAC entity, and the quick control MAC entity carries out scheduling on the at least one real-time MAC entity. Therefore, the scheduling and control of at least one MAC entity can be completed on the MAC layer, the issue of air interface signaling is guaranteed to be completed quickly, and the processing speed of the whole framework is improved.

In addition, the scheme further ensures the signaling processing to be carried out quickly because the MAC entity is controlled quickly to execute the functions in part of the RRC protocol entities which need to be executed quickly; and the resource coordination among the cells can be carried out by quickly controlling the MAC entity, thereby ensuring the speed of quickly finishing the switching processing of adding other cells by the terminal equipment.

Finally, the scheme does not need to greatly modify the functions of the MAC entity set in the original protocol, so the scheme has good expansibility and can quickly support massive users, and in addition, the scheme also carries out function adjustment among different protocol entities based on the functions specified in the original protocol, so the scheme has good compatibility and can be compatible with various protocol entities in a 4G/5G network.

Example II,

An embodiment of the present invention provides a MAC entity for fast control, as shown in fig. 6, including:

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

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

a first kind,

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

an information obtaining unit 63, configured to obtain content of an RRC signaling from a radio resource control RRC entity;

correspondingly, the instruction generating unit 61 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 61 is configured to perform encapsulation of a scheduling instruction by the fast Control MAC entity through a preset special PDCCH or a defined MAC Control Element (CE).

Wherein the RRC signaling comprises: air interface switching signaling and/or radio link reconfiguration signaling.

That is, the related signaling for air interface switching is sunk to the MAC entity for fast control, and the control is performed through the RRC air interface signaling, and now a special PDCCH or a defined MAC CE may be sent through the FC-MAC for fast control.

A second kind,

An information obtaining unit, configured to obtain a processing load and a spatial coverage condition of the at least one real-time MAC entity, and a characteristic parameter of a terminal device;

correspondingly, the instruction generating unit is configured to allocate a target real-time MAC entity to the terminal device as a first allocation result based on the processing load and the spatial coverage of the at least one real-time MAC entity and the characteristic parameter of the terminal device; generating scheduling instructions for the target real-time MAC entity based at least on the first allocation results.

Specifically, the information obtaining unit is configured to obtain a processing load and a corresponding spatial coverage in at least one real-time MAC entity managed by the information obtaining unit, and obtain various air interface characteristic parameters, cell characteristic parameters, and user characteristic parameters, such as air interface quality, neighboring air interface quality, and a moving direction, reported by at least one terminal device.

The instruction 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 a first allocation result corresponding to each of the terminal devices.

Specifically, the method for selecting the target real-time MAC entity for the terminal device may be to select a proper RT-MAC for each user to receive and transmit data by combining the cell served by each real-time MAC entity, the service type of the terminal device supported, and the current load of the terminal device, and then combining the air interface quality of the terminal device, the air interface quality of the neighboring cell, and the moving direction of the terminal device.

the instruction generating unit is used for acquiring the processing load and the space coverage condition of the at least one real-time MAC entity and the characteristic parameters of the terminal equipment;

A third one,

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

A fourth step of,

The instruction generating unit is used for selecting an air interface bearing mode for the terminal equipment; and generating a scheduling instruction aiming at a target real-time MAC entity of the terminal equipment based on the air interface bearing mode selected for the terminal equipment.

A fifth step of,

The instruction generating unit is used for determining a target cell to which the terminal equipment is accessed; acquiring a second allocation result of allocating a target real-time MAC entity to the terminal equipment according to at least one real-time MAC entity corresponding to the target cell based on the target cell accessed by the terminal equipment; generating scheduling instructions for the target real-time MAC entity based at least on the second allocation results.

A sixth kind,

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

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

and (3) reestablishing: data forwarding and in-order delivery;

sending and submitting data packets in sequence;

segmentation and concatenation of the transmission packets (concatenation);

and (3) reestablishing: data out-of-order delivery;

For example, the method may specifically be to perform at least one of the following processes:

adjusting at least one function of a packet data convergence protocol PDCP entity;

performing an adjustment of at least one function on the DRC entity;

an adjustment of at least one function is made to a radio link layer control protocol, RLC, entity.

Specifically, the adjusting, by the fast control MAC entity, at least one function of the DRC entity includes: the function adjusting unit is used for controlling whether to start the DRC function; and/or, controlling whether the RLC entity starts a centralized distributed mode; and/or controlling whether the PDCP entity starts a centralized distributed mode.

A seventh one,

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

The Radio Bearer (Radio Bearer) of the PDCP/DRC/RLC maps the scheduling control function in real time. And the FC-MAC decides to map the RB of the PDCP/DRC/RLC to the specific RT-MAC for data receiving and transmitting in a certain time period according to the air interface measurement information of the terminal equipment reported by each RT-MAC and/or a physical layer (PHY). I.e. setting a specific radio bearer for the RT-MAC entity.

The FC-MAC can dynamically adjust the length of the preset time period.

The eighth kind,

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

It is understood that this function may be combined with the seventh function for processing, that is, after the seventh function, that is, after the RB allocated to each RT-MAC entity is determined, this function may be used to control the specific flow of the RB;

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

Example III,

An embodiment of the present invention 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; wherein the content of the first and second substances,

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

and the real-time MAC entity 92 is used for receiving the scheduling instruction sent by the quick control MAC entity and processing according to the scheduling instruction.

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

In order to ensure the compatibility of a protocol stack, the traditional MAC function is uniformly defined as RT-MAC, the control of corresponding processes of user scheduling in a cell, wireless resource allocation in the cell and users and wireless resources in the cell is completed, and the RT-MAC function only focuses on the corresponding MAC function in the cell.

Specifically, as shown in FIG. 3, the FC-MAC essentially comprises two major functions: the assumed fast control function, namely the control process of interaction through RRC signaling, sinks to MAC and carries out fast control function through air interface scheduling; scheduling control procedures for RT-MAC (not including signaling control functions) that focus on performing scheduling for RT-MAC and non-signaling control functions needed to perform scheduling.

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

a first kind,

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

an RRC entity 93, configured to provide content of RRC signaling 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 rapid Control MAC entity encapsulates the scheduling command through a preset special PDCCH or a defined MAC Control Element (CE).

A second kind,

The rapid control Media Access Control (MAC) entity acquires the processing load and the space coverage condition of the at least one real-time MAC entity and the characteristic parameters of the terminal equipment; allocating a target real-time MAC entity to the terminal equipment as a first allocation result based on the processing load and the space coverage condition of the at least one real-time MAC entity and the characteristic parameters of the terminal equipment; generating scheduling instructions for the target real-time MAC entity based at least on the first allocation results.

It is understood that at least one terminal device in the function may be plural; further, each terminal device may be a terminal device that has selected a target cell to which the terminal device is to access; that is, the present function is mainly directed to selecting a corresponding target real-time MAC entity for at least one terminal device in a cell.

In addition, in the implementation of the function, the method may further include determining the number of terminal devices of the bearer and the service type of the bearer of each real-time MAC entity, specifically as follows, the determining, by the fast control MAC entity, a scheduling instruction for the at least one real-time MAC entity further includes at least:

A third one,

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

A fourth step of,

A fast control MAC entity 91, configured to select an air interface bearer mode for the terminal device; and generating a scheduling instruction aiming at a target real-time MAC entity of the terminal equipment based on the air interface bearing mode selected for the terminal equipment.

A fifth step of,

A fast control MAC entity 91, configured to determine a target cell to which the terminal device is to access; acquiring a second allocation result of allocating a target real-time MAC entity to the terminal equipment according to at least one real-time MAC entity corresponding to the target cell based on the target cell accessed by the terminal equipment; generating scheduling instructions for the target real-time MAC entity based at least on the second allocation results.

A sixth kind,

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

and (3) reestablishing: data forwarding and in-order delivery;

sending and submitting data packets in sequence;

segmentation and concatenation of the transmission packets (concatenation);

and (3) reestablishing: data out-of-order delivery;

and sequencing a plurality of RLC or sub-link data packets, and submitting data on each sub-link to the sub-link in sequence.

Flow control and distribution of multiple RLC or sub-link data packets are distributed according to the FIFO sequence, and SN numbers of corresponding data packets are maintained; and sequencing a plurality of RLC or sub-link data packets, and submitting data on each sub-link to the sub-link in sequence. This may be implemented using DRC entities in the data link layer.

As shown in fig. 11, the system further includes: PDCP entity 94, DRC entity 95, and RLC entity 96; wherein the content of the first and second substances,

a PDCP entity 94, configured to receive flow control information of an RB sent by the fast control MAC entity;

DRC entity 95 for receiving the flow control information of the RB sent from the fast control MAC entity;

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

Specifically, the fast control MAC entity controls whether to turn on the DRC function;

the rapid control MAC entity controls whether the RLC entity starts a centralized distributed mode or not;

and the quick control MAC entity controls whether the PDCP entity starts a centralized distributed mode or not.

A seventh one,

A fast control MAC entity 91 for mapping radio bearers RB to the at least one real time MAC entity within a preset time period.

The Radio Bearer (Radio Bearer) of the PDCP/DRC/RLC maps the scheduling control function in real time. And the FC-MAC decides to map the RB of the PDCP/DRC/RLC to the specific RT-MAC for data receiving and transmitting in a certain time period according to the air interface measurement information of the terminal equipment reported by each RT-MAC and/or a physical layer (PHY). I.e. setting a specific radio bearer for the RT-MAC entity. The FC-MAC can dynamically adjust the length of the preset time period.

The eighth kind,

The fast control MAC entity 91 determines flow control information for data transceived by an RB, and transmits the flow control information for the RB to at least one entity of a PDCP entity, a DRC entity, and an RLC entity; wherein the flow control information for the RB is used to inform at least one entity of a PDCP entity, a DRC entity and an RLC entity to control the flow of the RB mapped to at least one real-time MAC entity.

acquiring quality and throughput of each terminal device at an air interface, maximum throughput of a cell, service characteristics of each terminal device, bearing capacity of the cell, characteristics of the cell (such as a cell specially bearing high-rate data of a user, a cell specially bearing signaling, or other cells with special functions) and other various quantitative characteristic values reported by a physical layer, and related information of each channel managed by the physical layer; the related channels can comprise PDCCH/PDSCH/PUSCH/PUCCH; in addition, resource allocation information between cells, resource allocation information in the cells and related information stored in a system of each terminal device sent by the RRC entity can also be acquired; related information reported by the RT-MAC, such as load information, service types capable of being carried, resources in a cell corresponding to the RT-MAC, information of currently connected terminal equipment and the like, can also be combined; and performing flow control on data transmitted and received by the RBs by combining the plurality of information, and transmitting the flow control information aiming at each RB to the PDCP/DRC/RLC so that the PDCP/DRC/RLC completes flow control.

The integrated module according to the embodiment of the present invention may also be stored in a computer-readable storage medium if it is implemented in the form of a software functional module and sold or used as an independent product. Based on such understanding, the technical solutions of the embodiments of the present invention may be essentially implemented or a part contributing to the prior art may be embodied in the form of a software product stored in a storage medium, and including several instructions for enabling a computer device (which may be a personal computer, a network device, or a network device) to execute all or part of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes. Thus, embodiments of the invention are not limited to any specific combination of hardware and software.

The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.

Claims

1. A method of entity management, the method comprising:

a fast control Medium Access Control (MAC) entity determines a scheduling instruction for 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;

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

the rapid control MAC entity acquires the content of RRC signaling from a Radio Resource Control (RRC) entity and generates a scheduling instruction aiming at the at least one real-time MAC entity based on the content of the RRC signaling;

the quick control MAC entity generates corresponding air interface control according to user behavior, and generates a scheduling instruction aiming at the at least one real-time MAC entity based on the air interface control; and/or the presence of a gas in the gas,

acquiring the processing load and the space coverage condition of the at least one real-time MAC entity; determining the number of terminal devices borne by each real-time MAC entity and/or the type of service supported by the real-time MAC entity based on the processing load and the spatial coverage condition of the at least one real-time MAC entity; taking the number of terminal devices and/or supported service types borne by the at least one real-time MAC entity as a scheduling instruction;

the method further comprises the following steps:

the fast control MAC entity receives an RRC signaling function and fast controls at least one entity in a data link layer and/or an MAC layer.

2. The method of claim 1, wherein the RRC signaling comprises: air interface switching signaling and/or radio link reconfiguration signaling.

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

allocating a target real-time MAC entity to the terminal equipment as a first allocation result based on the processing load and the space coverage condition of the at least one real-time MAC entity and the characteristic parameters of the terminal equipment;

generating scheduling instructions for the target real-time MAC entity based at least on the first allocation results.

4. The method of claim 1, wherein the fast control MAC entity determines scheduling instructions for at least one real-time MAC entity, further comprising:

5. The method of claim 1, wherein the fast control MAC entity determines scheduling instructions for at least one real-time MAC entity, further comprising:

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

7. The method according to any one of claims 1-6, further comprising:

8. The method of any of claims 1-6, wherein the fast control MAC entity determines scheduling instructions for the at least one real-time MAC entity, further comprising:

9. The method of claim 8, further comprising:

10. A fast control MAC entity, the fast control MAC entity comprising:

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

an information acquisition unit, configured to acquire content of an RRC signaling from a 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 information acquisition unit is also used for generating corresponding air interface control according to the user behavior; correspondingly, the instruction generating unit is further configured to generate a scheduling instruction for the at least one real-time MAC entity based on air interface control;

the information acquisition unit is further configured to acquire a processing load and a spatial coverage condition of the at least one real-time MAC entity; correspondingly, the instruction generating unit is configured to determine, for each of the at least one real-time MAC entity, the number of terminal devices carried by the real-time MAC entity and/or the supported service type based on the processing load and the spatial coverage of the at least one real-time MAC entity; taking the number of terminal devices and/or supported service types borne by the at least one real-time MAC entity as a scheduling instruction;

the information obtaining unit is further configured to support an RRC signaling function and perform fast control on at least one entity of the data link layer and/or the MAC layer.

11. The fast control MAC entity of claim 10, wherein the RRC signaling comprises: air interface switching signaling and/or radio link reconfiguration signaling.

12. The fast control MAC entity of claim 10, further comprising:

the information acquisition unit is used for acquiring the processing load and the space coverage condition of the at least one real-time MAC entity and the characteristic parameters of the terminal equipment;

13. The fast control MAC entity of claim 10,

14. The fast control MAC entity of claim 10,

15. The MAC entity of claim 10, wherein the instruction generating unit is configured to determine a target cell to which a terminal device is to access; acquiring a second allocation result of allocating a target real-time MAC entity to the terminal equipment according to at least one real-time MAC entity corresponding to the target cell based on the target cell accessed by the terminal equipment; generating scheduling instructions for the target real-time MAC entity based at least on the second allocation results.

16. The fast control MAC entity of any of claims 10-15, further comprising:

an adjusting unit, configured to adjust at least one function of at least one entity in the data link layer.

17. The fast control MAC entity of any of claims 10-15, further comprising:

an adjusting unit, configured to map the RB to the at least one real-time MAC entity within a preset time period.

18. The fast control MAC entity of claim 17, wherein the adjusting unit is configured to determine flow control information for data transceived by an RB, and to send the flow control information for the RB to at least one entity in a data link layer;

19. An entity management system, the system comprising: a fast control MAC entity and at least one real-time MAC entity; wherein the content of the first and second substances,

the real-time MAC entity is used for receiving the scheduling instruction sent by the quick control MAC entity and processing according to the scheduling instruction;

the rapid control MAC entity is also used for carrying the RRC signaling function and rapidly controlling at least one entity of the data link layer and/or the MAC layer;

wherein the determining the scheduling instruction for the at least one real-time MAC entity comprises:

the RRC entity is used for providing the content of RRC signaling for the rapid 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 quick control MAC entity is used for generating corresponding air interface control according to user behavior and generating a scheduling instruction aiming at the at least one real-time MAC entity based on the air interface control; and/or the presence of a gas in the gas,

acquiring the processing load and the space coverage condition of the at least one real-time MAC entity; determining the number of terminal devices borne by each real-time MAC entity and/or the type of service supported by the real-time MAC entity based on the processing load and the spatial coverage condition of the at least one real-time MAC entity; and taking the number of the terminal devices and/or the supported service types carried by the at least one real-time MAC entity as a scheduling instruction.