CN101527935B

CN101527935B - Processing method and device in scheduling of resources

Info

Publication number: CN101527935B
Application number: CN2008101013291A
Authority: CN
Inventors: 张娟; 熊春山; 姜怡华; 汪颖
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: China Academy of Telecommunications Technology CATT; Datang Mobile Communications Equipment Co Ltd
Priority date: 2008-03-04
Filing date: 2008-03-04
Publication date: 2011-02-23
Anticipated expiration: 2028-03-04
Also published as: CN101527935A

Abstract

The invention provides a processing method in scheduling of resources, which comprises that: an MME allocates a bearer related ID used for indicating PDN connection to each established PDN; and when bearer information is transmitted, a message for transmitting the bearer information is added with the bearer related ID corresponding to the PDN connection belonging to a bearer. The invention also provides a device for realizing the scheduling of resources. The method and the device can indicate the PDN connection corresponding to the bearer for eNode B.

Description

Processing method and device in resource scheduling

Technical Field

The present invention relates to a resource scheduling technique in a System Architecture Evolution (SAE) system, and in particular, to a processing method and apparatus in resource scheduling.

Background

In the SAE system, a Packet Data Network (PDN) connection is always associated with a maximum aggregate bit rate (AMBR), which is stored as a quality of service (QoS) parameter for the bearer in the evolved base station eNode B, which uses the same AMBR for scheduling for all non-GBR bearers of a PDN connection. In current SAE systems, the network allows a terminal (UE) to initiate a multiple PDN connection request.

In the current SAE system, a UE initiates an ATTACH (ATTACH) procedure by sending a non-access stratum (NAS) message ATTACH REQUEST to a Mobile Management Entity (MME), where the MME acquires subscription information of the UE from a Home Subscriber Server (HSS), where the subscription information includes Access Point Names (APNs) that the UE is allowed to access and subscription QoS parameters of each APN that can be accessed. Meanwhile, a default apn (default apn) of the UE is also indicated in the subscription information. The UE establishes a default bearer with the default APN during Attach. As shown in fig. 1, each line represents a PDN connection bearer, and if the UE allows access to PDN network 1, PDN network 2, PDN network 3, and PDN network 4, PDN network 1 is the default APN for the UE, and at Attach, the UE establishes the default bearer indicated by the short dashed line with PDN network 1.

In the Attach procedure, the MME sends and stores the AMBR1 corresponding to the PDN network 1 to the eNode B through an initial context setup message of the S1 interface. If after Attach procedure, the PDN network 1 and the UE establish multiple dedicated bearers, as shown by the solid line between the UE and the PDN network 1 in the figure, the eNode B uses AMBR1 for scheduling all non-GBR bearers established from the PDN network 1.

After that, when the UE desires to access other PDN networks, the UE also sends a PDN connection establishment request by providing APN and the like information. The connection establishment can be completed through a PDN interface Gateway (GW)1 selected in the initial Attach procedure or other PDN GWs, and the selection of the PDN GW is determined by the MME according to the contents of the UE's location information, subscription data, and the like. For each PDN network to which the UE is connected, the UE has a default bearer, as indicated by the long dashed line. When default bearers are established for the

PDN networks

2, 3, and 4, the MME sends the AMBR corresponding to each PDN connection to the eNode B, where the eNode B stores four parameters, i.e., AMBR1, AMBR2, AMBR3, and AMBR 4.

For each PDN network connection, not only a default bearer may be established between the UE and the PDN GW, but also multiple dedicated bearers may be established between the UE and the PDN GW according to the PCC policy, as shown by the solid lines in fig. 1.

In the prior art, for a non-GBR bearer corresponding to each PDN connection, an eNode B uses the same AMBR for scheduling, the eNode B does not know information about the UE and the PDN connection, and the MME does not indicate to which PDN connection the bearer corresponds when initiating bearer establishment. When the UE is connected with the PDN network 1, only the AMBR1 is stored in the eNode B, and the eNode B directly uses the AMBR1 for all non-GBR bearers. However, when the UE establishes a connection with each of the

PDN networks

1, 2, 3, and 4, AMBR1, AMBR2, AMBR3, and AMBR4 are stored in the eNode B. For non-GBR bearers to be transmitted, the eNode B does not have enough information to determine which PDN connection it belongs to, and therefore cannot determine which AMBR should be used for scheduling.

Disclosure of Invention

In view of the above, the present invention provides a method and an apparatus for processing in resource scheduling, which can indicate a PDN connection corresponding to a bearer for an eNode B.

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

the invention provides a processing method in resource scheduling.A mobile management entity MME allocates a bearing associated identification code ID for identifying PDN connection for each established packet data network PDN connection, and the method comprises the following steps:

and when the bearing information is transmitted, adding a bearing association ID corresponding to the PDN connection to which the bearing belongs into the message for transmitting the bearing information.

Wherein, when performing an initial context procedure of the terminal UE, the message is: an initial context establishment message sent by the MME to an evolved base station eNode B;

correspondingly, after receiving the message, the eNode B obtains the maximum aggregate bit rate AMBR corresponding to the PDN connection according to the PDN connection indicated by the bearer association ID carried in the message, and uses the AMBR to schedule resources.

When a dedicated bearer is established under one PDN connection, or the UE requests establishment of a PDN connection other than the default PDN connection, the message is: a bearer establishment request message sent by the MME to the eNode B;

correspondingly, after receiving the message, the eNode B obtains the AMBR corresponding to the PDN connection according to the PDN connection indicated by the bearer association ID carried in the message, and uses the AMBR to schedule resources.

When the UE requests to establish PDN connection except default PDN connection, the bearer establishment request message comprises: and AMBR information corresponding to the established PDN connection.

When the UE is switched over the X2 interface, the message is as follows: a handover request message sent by the source eNode B to the target eNode B;

correspondingly, after receiving the message, the target eNode B obtains the AMBR corresponding to the PDN connection according to the PDN connection indicated by the bearer association ID carried in the message, and uses the AMBR to perform resource scheduling.

When the UE is switched over an S1 interface, the MME is a target MME, and the message is: a handover request message sent by the target MME to the target eNode B;

correspondingly, after receiving the message, the target eNode B obtains the AMBR corresponding to the PDN connection according to the PDN connection indicated by the bearer association ID carried in the message, and uses the AMBR to schedule resources.

The handover request message includes: and the UE corresponds to the AMBR information corresponding to the PDN connection.

Before the target MME allocates a bearer association ID for the PDN connection, the method further includes: the source eNode B sends context information of the UE to the target MME.

The handover request message sent by the target MME to the target eNode B further includes: context information of the UE.

The specific method for the source eNode B to send the context information to the target MME is as follows: the source eNode B sends a handover request message containing the context information of the UE to the source MME, and then the source MME sends a forward migration request message containing the context information of the UE to the target MME.

The bearer association ID is: a connection bearer identification LBI, or an EPS bearer ID, or a custom form.

The method further comprises the following steps:

when the bearer established by the UE is released, the eNode B deletes the bearer association ID corresponding to the bearer while deleting the bearer information corresponding to the bearer; or,

when PDN connection is released, the eNode B deletes the stored bearing association ID corresponding to the PDN connection, and meanwhile, the MME recovers the bearing association ID; or,

when UE changes from the connection state to the idle state, eNode B deletes the context information corresponding to the UE and deletes the bearing association ID corresponding to the PDN connection corresponding to the UE.

The invention also provides a device for realizing resource scheduling, which comprises: a bearer association ID assignment module, a message generation module, and a data transmission module, wherein,

a bearer association ID allocation module, configured to allocate a bearer association ID to the established PDN connection, and send the allocated bearer association ID to a message generation module;

the message generating module is used for generating a corresponding message when carrying out transmission of the bearing information, adding a corresponding bearing association ID in the message, and then sending the message to the data sending module;

and the data sending module is used for sending the message outwards.

Wherein the bearer association ID assignment module is further configured to: and when the PDN connection is released, recovering the bearing association ID allocated for the PDN connection.

The invention also provides a device for realizing resource scheduling, which comprises: a data receiving module, a resource scheduling module, wherein,

the data receiving module is used for sending the message containing the bearing association ID to the resource scheduling module after receiving the message;

and the resource scheduling module is used for obtaining the PDN connection to which the bearer needs to be established according to the bearer association ID in the message, further obtaining the AMBR corresponding to the PDN connection, and scheduling related resources according to the AMBR.

The data receiving module is further configured to: sending the message to an information storage module;

correspondingly, the device further comprises:

an information storage module, configured to store a bearer association ID corresponding to a PDN connection and a bearer association ID corresponding to a bearer included in the message; the method is also used for deleting the bearer association ID corresponding to the bearer when the bearer is released; when the UE enters an idle state from a connection state, deleting a bearer association ID corresponding to the PDN connection corresponding to the UE; and when the PDN connection is released, deleting the bearer association ID corresponding to the PDN connection.

The processing method and the device in the resource scheduling allocate a bearing associated identification code (ID) for each PDN connection, when carrying information is transmitted, a corresponding bearing associated ID is added in a message for transmitting the bearing information, and the bearing associated ID is used for indicating the PDN connection corresponding to the bearing for an eNode B when the eNode B carries out the resource scheduling, thereby indicating the AMBR required to be used, and solving the problem of resource scheduling when the UE is connected with multiple PDNs; and the bearing association ID is added into the message for transmitting the bearing information for transmission, so that no new signaling is needed to be added, the implementation is simple, and the burden of the system caused by the addition of excessive signaling is avoided.

In addition, when the bearer, the PDN connection is released, or the UE enters an idle state from the connected state, the eNode B deletes the stored bearer association ID accordingly, and the MME also recovers the bearer association ID allocated to the released PDN connection, thereby reducing redundant information in the system and optimizing system resources.

Drawings

Figure 1 is a schematic diagram of a UE interfacing with multiple PDNs;

FIG. 2 is a schematic diagram of the Attach process of the present invention;

FIG. 3 is a diagram illustrating an initial context establishment procedure of a UE according to the present invention;

fig. 4 is a schematic diagram of a dedicated bearer establishment procedure according to the present invention;

FIG. 5 is a diagram illustrating a process of a UE requesting multiple PDN connections according to the present invention;

FIG. 6 is a diagram illustrating SAE bearer establishment procedures in accordance with the present invention;

FIG. 7 is a schematic diagram illustrating the switching process of the X2 interface according to the present invention;

FIG. 8 is a schematic diagram illustrating a handover procedure when a core network is changed according to the present invention;

FIG. 9 is a schematic structural diagram of an apparatus for implementing resource scheduling according to the present invention;

fig. 10 is a schematic structural diagram of an apparatus for implementing resource scheduling according to the present invention.

Detailed Description

The basic idea of the invention is: the MME allocates a bearer association ID for each PDN connection, and adds a corresponding bearer association ID into a message for transmitting bearer information when the bearer information is transmitted.

The following describes in detail implementation of the processing method and apparatus in resource scheduling according to the present invention with reference to the accompanying drawings.

Fig. 2 is a schematic diagram of an Attach procedure, in which an MME to which a UE is connected is referred to as a new MME and an MME to which the UE is connected is referred to as an old MME, as shown in fig. 2, the procedure includes:

step 201: after the UE sends NAS information of an Attach request to initiate an Attach process, the MME acquires subscription information of the UE from the HSS after receiving the information; the HSS sends the subscription information of the UE to a serving MME, wherein the subscription information comprises: all APNs that the UE is allowed to access, a UE default APN, and an EPS subscription QoS list for each APN that is allowed to access. If all the subscription verification is successful, the MME establishes context information for the UE and requests to establish default load of a default APN; MME selects a service interface gateway (Serving GW) for UE, and allocates EPS bearing ID for the default bearing to be established; the MME sends the information of IMSI, MME context ID, APN, default bearer QoS, AMBR, EPS bearer identification and the like of the UE to Serving GW through establishing a default bearer request message; and when the PDN connection between the Serving GW and the PDN GW is established, the Serving GW returns a response message for establishing the default bearer to the new MME.

Step 202: the new MME sends an Attach accept message to the corresponding eNode B.

In this step, the Attach accept message may be piggybacked in the NAS IE of the initial context setup request message sent by the MME to the eNodeB in step 301 and transmitted together.

Step 203: the eNode B sends a radio bearer establishment request message to the UE, and the UE correspondingly returns a radio bearer establishment response message.

Step 204: and completing the Attach and updating corresponding bearing information and position information.

The Attach process shown in fig. 2 has been described in detail in the protocol TS23.401, and is not described herein again, and the specific implementation method of each step is well known in the prior art and is not described herein again.

Fig. 3 is a schematic diagram of an initial context establishment procedure of a UE, as shown in fig. 3, including:

step 301: in step 201, after the Serving GW returns a response message for establishing a default bearer to the new MME, the MME initiates an initial context establishment procedure of the UE on the S1 interface, allocates a bearer association ID to each PDN connection to be established, adds the bearer association ID to the initial context establishment request message, and then sends the initial context establishment request message to the eNode B.

In the prior art, the initial context setup request message includes: in step 202, the Attach accept message, QoS parameters of bearer, EPS bearer ID, AMBR related to PDN, QoS message of radio bearer to be established, etc.; moreover, if in the Attach procedure, the PDN GW also initiates a dedicated bearer establishment procedure, and the initial context establishment request message further includes: establishment request message of dedicated bearer.

In the invention, the bearer association ID is allocated by the MME when the PDN connection is established, and is used for identifying the PDN connection, and further can be used for indicating the association relationship between the established bearer and the corresponding PDN connection when the bearer association ID is added into the bearer information. Moreover, if the dedicated bearer needs to be established simultaneously in the initial context establishment procedure, for each dedicated bearer requested to be established, the dedicated bearer is associated with the PDN connection to which the dedicated bearer belongs by using the corresponding bearer association ID. Then, according to the bearer association ID, in step 203 shown in fig. 2, the eNode B can select a correct AMBR for resource scheduling for the bearer to be transmitted. The value of the bearer association ID may be set as a default item, indicating that the UE is connected to the default PDN.

Step 302: the eNode B correspondingly returns an initial context setup response message to the MME.

In the step shown in fig. 3, how to send the message is well known in the prior art, and details are not described here. Moreover, step 301 corresponds to step 202 in the Attach procedure shown in fig. 2, and is executed together with step 202; step 302 corresponds to the Attach procedure shown in fig. 2, and in step 204, the eNodeB returns an Attach complete message to the MME.

Fig. 4 is a schematic diagram of a dedicated bearer establishment procedure, and the procedure shown in fig. 4 is executed after the Attach procedure is completed, as shown in fig. 4, the procedure includes:

step 401: and after initiating a dedicated bearer establishment process, sending corresponding bearer establishment requests step by step until an MME sends the bearer establishment request to an eNodeB, and adding a bearer association ID corresponding to the belonging PDN connection in the bearer establishment request according to the PDN connection to which the bearer to be established belongs. The bearer association ID has the same function as the bearer association ID described in fig. 2 and 3, and is used to indicate the association relationship between the established dedicated bearer and the PDN connection.

Step 402: and the eNode B obtains the PDN connection to which the bearer to be established belongs according to the bearer association ID so as to obtain the AMBR corresponding to the PDN connection, performs resource scheduling according to the AMBR, then sends a radio bearer establishment request message to the UE, and the UE correspondingly returns a radio bearer establishment response message.

Step 403: and the eNode B returns corresponding bearer establishment response messages to the MME, the MME to the Serving GW and the Serving GW to the PDN GW step by step.

Fig. 5 is a diagram illustrating a procedure of requesting multiple PDN connections by the UE, and the procedure shown in fig. 5 is also executed after the Attach procedure is completed, as shown in fig. 5, the procedure includes:

step 501: bearer establishment preparation procedures. In the process, the UE sends corresponding bearer establishment request messages to the MME, the MME to the Serving GW, and the Serving GW to the PDN GW step by step.

After the Serving GW returns a response for establishing a default bearer to the MME, the MME allocates a bearer association ID for the PDN connection to be established, and then sends a bearer establishment request message to the eNode B, and adds a corresponding bearer association ID to the bearer establishment request. Meanwhile, the bearer establishment request message must also include AMBR information corresponding to the established PDN connection.

Step 502: and the eNode B obtains the PDN connection to which the bearer to be established belongs according to the bearer association ID so as to obtain an AMBR corresponding to the PDN connection, performs resource scheduling according to the AMBR, sends a radio bearer establishment request message to the UE, and the UE correspondingly returns a radio bearer establishment response message.

Step 503: and (5) completing the connection establishment process. In this process, the bearer information, the location information, and the like are updated.

For specific description of the processes shown in fig. 4 and fig. 5, reference may be made to relevant contents in the protocol TS23.401, which is not described herein again.

Fig. 6 is a schematic diagram of an SAE bearer establishment procedure, which includes:

step 601: the MME sends an SAE bearer setup request message to the eNode B.

Step 602: the eNode B returns an SAE bearer setup response message accordingly.

Wherein, step 601 corresponds to the step of MME sending bearer establishment request message to eNode B in fig. 4 and 5, and step 602 corresponds to the step of eNode B returning bearer establishment response message to MME in fig. 4 and 5.

The SAE bearer establishment procedure is described and defined in both the protocol TS36.413 and the protocol TS 23.401. The SAE bearer establishment request message includes: SAE bearer ID number allocated by MME, SAE bearer level QoS parameter, etc.; moreover, if the UE initiates multiple PDN connections, the AMBR corresponding to each PDN connection is also carried in an SAE bearer setup request message to the eNode B.

Wherein, the bearer association ID added in the SAE bearer establishment request message is also used to indicate the relationship between the established dedicated bearer and the PDN connection. The value of the bearer association ID may be set as a default item, indicating that the UE is connected to the default PDN network.

Fig. 7 is a schematic diagram of the switching process of the X2 interface, as shown in fig. 7, the process includes:

step 701: and switching the measurement judgment process to obtain the target eNode B accessed by the UE after judgment. Since the measurement decision process belongs to the known technology, it is not described herein again.

Step 702: and the source eNode B sends a switching request message to the target eNode B, wherein the switching request message comprises the bearing correlation ID.

Among them, in the related art, when a handover of an X2 interface occurs for a UE, a source eNode B needs to transmit context information of the UE to a target eNode B. The UE context information defined in the protocol TS36.413 includes AMBR, a list of to-be-established SAE bearers, RRC context information, etc., and the list of to-be-established SAE bearers includes information of SAE bearers, SAE bearer level QoS parameters, etc. The handover request message of the present invention adds the bearer association ID on the basis of the content included in the prior art, for indicating the relationship between the established bearer and the PDN connection to the target eNode B.

Step 703: and the target eNode B obtains the PDN connection to which the bearer to be established belongs according to the bearer association ID contained in the switching request message, further obtains an AMBR corresponding to the PDN connection, and then uses the AMBR to carry out resource scheduling.

Step 704: after the resource scheduling is completed, the target eNode B returns a switching request confirmation message to the source eNode B.

Step 705: the execution and completion of the handover. The specific process is shown in fig. 7, and is well known in the art, and will not be described herein.

Fig. 8 is a schematic diagram of a handover process when a core network is changed, at this time, a UE is handed over an S1 interface, an eNode B and an MME corresponding to the UE before handover are respectively referred to as a source eNode B and a source MME, and an eNode B and an MME to be handed over are respectively referred to as a target eNode B and a target MME, as shown in fig. 8, the process includes:

step 801: the source eNode B sends a handover request message to the source MME.

Step 802: and the source MME sends a forwarding migration request message to the target MME.

Wherein, the switching request and the forwarding migration request comprise: context information of the UE in the source eNode B.

Step 803: the target MME sends a request message for establishing the load to the target Serving GW, and then the Serving GW correspondingly returns a response message for establishing the load to the target MME.

Step 804: the target MME reallocates a new bearer association ID for the bearer that needs to be established and adds it to the handover request message sent to the target eNode B.

Wherein, the handover request message needs to include AMBR information for indicating an AMBR corresponding to a PDN connection corresponding to the UE, and the handover request message may further include: context information of the UE in the source eNode B carried in the messages of step 801 and step 802.

Wherein the AMBR information can be added in the context information by the source eNode B, and forwarded by the source MME and the target MME for final transmission to the target eNode B. Or, since the forwarding migration request message sent by the source MME to the target MME may carry the AMBR information, the context information does not need to carry the AMBR information, but at this time, the AMBR information needs to be added to the handover request message. Therefore, there are several implementation methods for the final transmission of the AMBR information to the target eNode B: when adding the AMBR information to the context information, in the handover request message sent by the target MME to the target eNode B in step 804, the AMBR information may be additionally added while the context information is forwarded, or the AMBR information may not be added; the other is when the AMBR information is not added to the context information, in this case, the AMBR information must be added to the handover request message sent by the target MME to the target eNode B in step 804. However, regardless of the way this is done, the AMBR information must be included in the handover request message.

Step 805: the target eNode B creates context information of the UE, including bearer information, security information, and the like, and completes a corresponding handover execution and completion procedure.

In the processes shown in fig. 2 to 8, when each MME allocates a bearer association ID for its corresponding PDN connection, the bearer association ID may be in the same form or may be in different forms defined by itself, that is, the bearer association ID allocated by the MME for the bearer only needs to be identifiable by its subordinate eNode B, and different PDN connections can be distinguished.

Moreover, the bearer association ID may be a connection bearer identification (LBI), an EPS bearer ID, or other additionally allocated association indication. However, there are some disadvantages to using LBI and EPS bearer ID, both of which are used in EPS bearer level, and LBI is equal to EPS bearer ID of default bearer, on one hand, the identifier of EPS bearer level is not very suitable for EPS access bearer level, on the other hand, the two parameters have large value range and occupy more transmission space. Whereas the further allocation of an association may mask the association between different levels and save memory space, it is preferred that the bearer is further allocated the bearer association ID.

Fig. 2 to 8 illustrate the allocation, transmission and usage process of the bearer association ID. When the established bearer is released, correspondingly, when deleting the bearer information corresponding to the bearer, the eNode B may delete the bearer association ID corresponding to the bearer. Similarly, when a certain PDN connection is released, the eNodeB deletes the stored bearer association ID corresponding to the PDN connection, and the MME may also retrieve the bearer association ID and allocate the bearer association ID to another newly-established PDN connection. Or, if the UE enters the idle state from the connected state, the eNode B deletes the context information of the UE, and the association indication ID stored in the eNode B and corresponding to the PDN connection of the UE is also deleted.

Fig. 9 is a schematic structural diagram of an apparatus for implementing resource scheduling according to the present invention, and the apparatus may be used as a part of an MME in practical application, as shown in fig. 9, the apparatus includes: a bearer association ID assignment module 910, a message generation module 920, and a data transmission module 930, wherein,

a bearer association ID allocating module 910, configured to allocate a bearer association ID for the established PDN connection, and send the allocated bearer association ID to a message generating module 920; and also used for recovering the bearing association ID allocated for the PDN connection when the PDN connection is released.

The message generating module 920 is configured to generate a corresponding message when carrying information is transmitted, add a corresponding carrying association ID to the message, and then send the message to the data sending module 930.

The corresponding message changes correspondingly according to the different procedures in which the MME is located, for example, when the MME is in the initial context setup procedure of the UE, the message is: an initial context setup request message; when the MME establishes a dedicated bearer under a certain PDN connection, the message is as follows: a bearer establishment request message; the specific messages generated in other processes are not described in detail herein.

A data sending module 930, configured to send the message outwards.

The present invention also provides another apparatus for implementing resource scheduling, which can be used as a part of an eNode B in practical applications, as shown in fig. 10, and the apparatus includes: a data receiving module 1010, a resource scheduling module 1020, and an information storage module 1030, wherein,

a data receiving module 1010, configured to send a message containing a bearer association ID to a resource scheduling module 1020 after receiving the message; and also for sending the message to the information storage module 1030.

And a resource scheduling module 1020, configured to obtain, according to the bearer association ID in the message, a PDN connection to which the bearer to be established belongs, further obtain an AMBR corresponding to the PDN connection, and use the AMBR to perform scheduling on related resources.

An information storage module 1030, configured to connect to a bearer association ID corresponding to the PDN connection and a bearer association ID corresponding to a bearer included in the message; the method is also used for deleting the bearer association ID corresponding to the bearer when the bearer is released; the method is also used for deleting the bearer association ID corresponding to the PDN connection corresponding to the UE when the UE enters an idle state from a connection state; and the method is also used for deleting the bearer association ID corresponding to the PDN connection when the PDN connection is released.

In practical applications, the information storage module may further need to store context information, bearer information, and the like, which is not described herein again.

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 processing method in resource scheduling is characterized in that a mobile management entity MME allocates a bearer association identification code ID for identifying PDN connection for each established packet data network PDN connection, and the method comprises the following steps:

when carrying information is transmitted, adding a carrying association ID corresponding to PDN connection to which a carrying belongs into a message for transmitting the carrying information;

and after receiving the message, the eNode B obtains the maximum aggregation bit rate AMBR corresponding to the PDN connection according to the PDN connection indicated by the bearing association ID carried in the message, and uses the AMBR to schedule resources.

2. The method of claim 1, wherein when performing an initial context procedure of a terminal UE, the message is: an initial context establishment message sent by the MME to an evolved base station eNode B;

3. The method of claim 1, wherein when a dedicated bearer is established under one PDN connection or a UE requests to establish a PDN connection other than a default PDN connection, the message is: a bearer establishment request message sent by the MME to the eNode B;

4. The method of claim 3, wherein when the UE requests to establish a PDN connection other than the default PDN connection, the bearer establishment request message comprises: and AMBR information corresponding to the established PDN connection.

5. The method of claim 1, wherein when the UE performs an X2 interface handover, the message is: a handover request message sent by the source eNode B to the target eNode B;

6. The method of claim 1, wherein when the UE performs S1 interface handover, the MME is a target MME, and the message is: a handover request message sent by the target MME to the target eNode B;

7. The method of claim 6, wherein the handover request message comprises: and the UE corresponds to the AMBR information corresponding to the PDN connection.

8. The method of claim 6 or 7, wherein before the target MME allocates a bearer association ID for the PDN connection, the method further comprises: the source eNode B sends context information of the UE to the target MME.

9. The method of claim 8, wherein the handover request message sent by the target MME to the target eNode B further comprises: context information of the UE.

10. The method of claim 8, wherein the specific method for the source eNode B to send the context information to the target MME is as follows: the source eNode B sends a handover request message containing the context information of the UE to the source MME, and then the source MME sends a forward migration request message containing the context information of the UE to the target MME.

11. The method according to any of claims 1 to 7, wherein the bearer association ID is: a connection bearer identification LBI, or an EPS bearer ID, or a custom form.

12. The method of any one of claims 1 to 7, further comprising:

13. An apparatus for implementing resource scheduling, the apparatus comprising: a bearer association ID assignment module, a message generation module, and a data transmission module, wherein,

and the data sending module is used for sending the message outwards.

14. The apparatus of claim 13, wherein the bearer association ID assignment module is further configured to: and when the PDN connection is released, recovering the bearing association ID allocated for the PDN connection.

15. An apparatus for implementing resource scheduling, the apparatus comprising: a data receiving module, a resource scheduling module, wherein,

16. The apparatus of claim 15, wherein the data receiving module is further configured to: sending the message to an information storage module;

correspondingly, the device further comprises: