BR112018013931B1 - DATA SCHEDULING METHOD, BASE STATION AND SYSTEM - Google Patents

Abstract

The present invention discloses a mode of data scheduling, including: obtaining, by a base station, UE user equipment capability information, wherein a time of obtaining the UE capability information is prior to receipt, by the base station , the complete RRC radio control resource connection establishment signaling that is sent by the UE to the base station; and allocating, by the base station, a data scheduling resource to the UE in accordance with the capability information of the UE. Using embodiments of the present invention, resource utilization can be increased.

Description

[001] This application claims priority to International Patent Application PCT/CN2016/070440, filed with the International Patent Office on January 7, 2016 and entitled "DATA SCHEDULING METHOD, BASE STATION, AND SYSTEM", which is incorporated herein document in its entirety for reference purposes.

FIELD OF TECHNIQUE

[002] The present invention relates to the field of communication technologies and, in particular, to a data scheduling method, a base station and a system.

FUNDAMENTALS

[003] With the rapid development of wireless communications, people are no longer fully satisfied with human-to-human communication, and an Internet of Things (IOT) technology emerges. Machine-to-Machine (M2M) communication refers to the transfer of information and data between machines through the use of a wireless network, and is an important development direction of IoT. An M2M device is generally a relatively compact battery-powered system, such as a smart metering system, that needs to periodically monitor and report a usage status of water, electricity, gas or the like.

[004] Generally, a smart metering service is mainly a small data packet reporting service with a small volume of data. There are mainly two transmission solutions for this service. One is a Control Plane-based transmission solution (CP), and the other is a User Plane-based transmission solution (UP). An existing method for obtaining User Equipment (UE) capability information is as follows: After a base station establishes a connection with a Mobility Management Entity (MME), if the MME stores the UE capability information, the MME sends the UE capability information to the base station; or if the MME does not store the UE's capability information, the base station asks the UE for the UE's capability information and sends the UE's capability information to the MME. However, in a CP-based data transmission solution, if the existing method is used to obtain the UE's capability information, the base station does not have the UE's capability information when the UE sends data. As such, the base station cannot properly allocate a data scheduling resource to the UE according to the capacity information of the UE, and the resource utilization is reduced.

SUMMARY

[005] Embodiments of the present invention provide a data scheduling method, a base station, and a system, intended to increase resource utilization.

[006] A first aspect of embodiments of the present invention provides a data scheduling method, including: obtaining, by a base station, user equipment (UE) capacity information, where a time of obtaining the UE capacity information is prior to that of receiving, by the base station, radio resource control connection (RRC) complete establishment signaling that is sent by the UE to the base station; and allocating, by the base station, a data scheduling resource to the UE in accordance with the capacity information of the UE.

[007] With reference to the first aspect of the present invention, in a first possible implementation of the first aspect, obtaining, by a base station, UE capability information includes: receiving, by the base station, an RRC connection request that is sent by the UE and carrying the UE's capacity information; or receive, by the base station, a paging message that is sent by a network core and that carries the UE's capacity information; or receiving, by the base station, a first paging message sent by a network core; if the first paging message does not carry the UE's capability information, send, by the base station to the UE, a second paging message that carries indication information, where the indication information is used to instruct the UE to report the information of UE capacity; and receiving, by the base station, an RRC connection request that is sent by the UE and that carries the capability information of the UE.

[008] With reference to the first aspect of the present invention, in a second possible implementation of the first aspect, the capacity information is the first capacity information, and after obtaining, by a base station, capacity information from the user equipment (UE), method further includes: receiving, by the base station, an initial context establishment request that is sent by a network core and that carries the second capacity information; or sending, by the base station, a request to obtain capability information from the UE to the UE and receiving, by the base station, the third capability information that is sent by the UE in response to the request to obtain capability information from the UE; or receiving, by the base station, downlink non-access stratum (NAS) transport signaling that are sent by a network core and that carry the fourth capacity information; or receive, by the base station, the RRC connection complete establishment signaling that is sent by the UE and which carries the fifth capacity information.

[009] With reference to the first aspect of the present invention, in a third possible implementation of the first aspect, obtaining, by a base station, UE capability information includes: receiving, by the base station, an RRC connection request sent by the UE, wherein the RRC connection request carries auxiliary routing information from a first network core, and the first network core is a network core that stores context information of the UE; determining, by the base station according to the auxiliary routing information of the first network core, a network core and identification information for identifying the UE by the network core; send, by the base station, a request to obtain UE capability information to the given network core, wherein the request to obtain UE capability information carries the identification information to identify the UE by the network core, the identification information to identifying the UE by the network core is used by the determined network core to obtain the context information of the UE, and the context information of the UE includes the capability information of the UE; and receiving, by the base station, the capability information that is from the UE and that is sent by the determined network core in response to the request to obtain capability information from the UE.

[010] With reference to the third possible implementation of the first aspect of the present invention, in a fourth possible implementation of the first aspect, after obtaining, by a base station, UE capacity information, the method further includes: sending, by the base station base, UE capacity usage indication information for the UE, where the UE capacity usage indication information is used to indicate a UE capacity used in data scheduling, and the UE capacity usage indication information is used to indicate a UE capacity used in data scheduling, and the UE capacity usage indication information is used to indicate a UE capacity usage indication information for UE includes indication information to indicate whether a multiple HARQ process is used in data scheduling, and/or indication information to indicate whether a large transport block size (TBS) is used in data scheduling.

[011] With reference to the third possible implementation of the first aspect of the present invention, in a fifth possible implementation of the first aspect, the determination, by the base station according to the auxiliary routing information of the first network core, a network core and identification information to identify the UE by the network core includes: determining, by the base station in accordance with the auxiliary routing information of the first network core, a globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core and the identification information for identifying the UE by the network core; determining, by the base station in accordance with GUMMEI, whether the network cores that can be selected by the base station include the first network core; and selecting, by the base station, the first network core, if the network cores that can be selected by the base station include the first network core; or if the network cores that can be selected by the base station do not include the first network core, select, by the base station, any of the network cores that can be selected by the base station.

[012] With reference to the fifth possible implementation of the first aspect of the present invention, in a sixth possible implementation of the first aspect, the auxiliary routing information of the first network core includes a Temporary Mobile Subscriber Identity (S-TMSI) of the Evolution of System Architecture (SAE).

[013] With reference to the sixth possible implementation of the first aspect of the present invention, in a seventh possible implementation of the first aspect, the auxiliary routing information of the first network core further includes at least one of the following: a mobile network address index selected public land/public land mobile network (PLMN) ID address or a mobility management entity (MME) group identifier (MMEGI).

[014] With reference to the seventh possible implementation of the first aspect of the present invention, in an eighth possible implementation of the first aspect, the auxiliary routing information of the first network core includes the S-TMSI and the public land mobile network address index selected/PLMN ID, and the determination, by the base station in accordance with the auxiliary routing information of the first network core, of a globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core and the identification information to identify the UE by the network core includes: obtaining, by the base station, the MMEGI of the base station's first network core according to the S-TMSI and the selected public land mobile network address index/PLMN ID ; and determining, by the base station in accordance with the S-TMSI, the selected public land mobile network address index/PLMN ID and the MMEGI, the globally unique mobility management entity (MME) identifier (GUMMEI) of the first core network and identification information to identify the UE by the network core.

[015] With reference to the sixth possible implementation of the first aspect of the present invention, in a ninth possible implementation of the first aspect, the determination, by the base station in accordance with the auxiliary routing information of the first network core, of an entity identifier globally unique mobility management (MME) ID of the first network core and identification information to identify the UE by the network core includes: determining, by the base station, an MMEGI and a PLMN ID of the first network core of according to S-TMSI; and determining, by the base station in accordance with the S-TMSI, the MMEGI and the PLMN ID, the globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core and the identification information to identify the UE by the network core.

[016] With reference to the seventh possible implementation of the first aspect of the present invention, in a tenth possible implementation of the first aspect, the auxiliary routing information of the first network core includes the S-TMSI and the MMEGI, and the determination, by the station basis according to the auxiliary routing information of the first network core, a globally unique mobility management entity identifier (MME) of the first network core, and the identification information to identify the UE by the network core includes: determining, by the base station, the PLMN ID of the first network core according to S-TMSI; and determining, by the base station in accordance with the S-TMSI, the MMEGI and the PLMN ID, the globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core and the identification information to identify the UE by the network core.

[017] With reference to the seventh possible implementation of the first aspect of the present invention, in an eleventh possible implementation of the first aspect, the auxiliary routing information of the first network core includes the S-TMSI, the MMEGI, and the address index of selected public land mobile network/PLMN ID, and the determination, by the base station in accordance with the auxiliary routing information of the first network core, of a globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core and identification information to identify the UE by the network core includes: determining, by the base station according to the S-TMSI, the MMEGI, and the selected public land mobile network address index/PLMN ID, the globally unique mobility management entity identifier (MME) (GUMMEI) of the first network core and the identification information to identify the UE by the network core.

[018] With reference to any of the third to eleventh possible implementations of the first aspect of the present invention, in a twelfth possible implementation of the first aspect, after determination, by the base station in accordance with the auxiliary routing information of the first core of a network core, a network core, and identification information to identify the UE by the network core, the method further includes: if a network core connected to the base station is modified, sending, by the base station, the identification information to identifying the UE by the network core for a modified network core, wherein the identification information for identifying the UE by the network core is used by the modified network core to ask the first network core for the context information of the UE.

[019] With reference to the first aspect of the present invention, in a thirteenth possible implementation of the first aspect, obtaining, by a base station, UE capability information includes: receiving, by the base station, a connection establishment request or a connection re-establishment request sent by the UE and which carries auxiliary routing information from a first base station, wherein the first base station is a base station that stores auxiliary routing information from a second network core, and the second base station is a base station that stores auxiliary routing information from a second network core, and the second base station is a network is a network core that stores UE context information; requesting, by the base station, the first base station for the auxiliary routing information of the second network core in accordance with the auxiliary routing information of the first base station; determining, by the base station in accordance with the auxiliary routing information of the second network core, a network core and identification information for identifying the UE by the network core; sending, by the base station, a request to obtain UE context information for the given network core, wherein the request to obtain UE context information carries the identification information to identify the UE by the network core, the identification information to identify the UE by the network core is used by the determined network core to obtain the context information of the UE, and the context information of the UE includes the capability information of the UE; and receiving, by the base station, context information that is from the UE and that is sent by the determined network core in response to the request to obtain UE context information.

[020] With reference to any one of the first aspect, or the first to thirteenth possible implementations of the first aspect of the present invention, in a fourteenth possible implementation of the first aspect, the capability information includes at least one of the following: employment single-band/multi-band deployment, single-tone/multi-tone indication, a control plane/user plane indication, CP/UP ), a UE-category, a radio capability, a subscriber profile identifier (SPID), access stratum release information, a multi-process HARQ capability, a large TBS capacity, a new energy type, an indication of mobility improvement, a control plane reestablishment capability, or a reestablishment indication.

[021] With reference to the fourteenth possible implementation of the first aspect of the present invention, in a fifteenth possible implementation of the first aspect, the UE-category, includes UE that supports or needs a multi-process HARQ and/or or UE that support or need a large TBS.

[022] With reference to the fourteenth or fifteenth possible implementation of the first aspect of the present invention, in a sixteenth possible implementation of the first aspect, the new power type is included in a data unit control element of the MAC protocol ( MAC CE) that carries the request to establish RRC connection.

[023] With reference to any of the fourteenth to sixteenth possible implementations of the first aspect of the present invention, in a seventeenth possible implementation of the first aspect, the reestablishment includes an indication of user plane reestablishment (UP) and/or a control plane (CP) reestablishment indication, the UP reestablishment indication is an indication used to indicate whether mobility improvement is supported after reestablishment, and the CP reestablishment indication is used to indicate that the reestablishment of connection is used for CP reestablishment, or is used to distinguish between CP indication and UP indication.

[024] With reference to any of the fourteenth to seventeenth possible implementations of the first aspect of the present invention, in an eighteenth possible implementation of the first aspect, the restoration indication is carried in a message sent by the UE to the base station, and the message includes a request to reestablish the RRC connection.

[025] With reference to the eighteenth possible implementation of the first aspect of the present invention, in a nineteenth possible implementation of the first aspect, the reestablishment indication is further used as an establishment cause value for indication.

[026] With reference to any of the fourteenth to nineteenth possible implementations of the first aspect of the present invention, in a twentieth possible implementation of the first aspect, prior to obtaining, by a base station, UE capacity information, the method further includes: broadcasting, by the base station, an indication that the base station supports mobility enhancement.

[027] A second aspect of embodiments of the present invention provides a data scheduling method, including: receiving, by a base station, downlink NAS transport signaling that is sent by a network core and that carries system capacity information. HUH; or receive, by a base station, uplink information transport signaling that is sent by the UE and that carries UE capability information and send, by the base station to a network core, uplink NAS transport signaling that carries the UE capability information; and allocating, by the base station, a data scheduling resource to the UE in accordance with the capacity information of the UE.

[028] A third aspect of embodiments of the present invention provides a connection release method, including: receiving, by a base station, downlink NAS transport signaling that is sent by a base network and which carries a release indication of connection; send, by the base station to the UE, downlink information transport signaling carrying the connection release indication; and releasing, by the base station, a connection between the base station and the UE, and sending release signaling to the network core, such that the network core releases an S1 interface after receiving the release signaling.

[029] A fourth aspect of embodiments of the present invention provides a base station, and the base station has a function of implementing the base station behavior in the design of the previous method. The function can be implemented using hardware, or it can be implemented by hardware by running the corresponding software. The hardware or software includes one or more modules corresponding to the function. Modules can be software and/or hardware. The base station includes a getting unit and an allocating unit so as to perform related steps of the data scheduling method provided in the first aspect.

[030] A fifth aspect of embodiments of the present invention provides a base station, the base station includes a transceiver and a processor, and the processor is configured to support the base station in performing a corresponding function in the previous method. The transceiver is configured to support communication between the base station and a mobile network server. The base station may further include a memory, and the memory is configured to be coupled to the processor, and stores a required program instruction and base station data. The base station may further include: a communications interface, used for communication between the base station and another communications device or network.

[031] A sixth aspect of embodiments of the present invention provides a computer storage medium, configured to store a computer software instruction used by the base station, and the computer storage medium includes a program designed to execute the foregoing aspects.

[032] A seventh aspect of embodiments of the present invention provides a communications system, including a base station, user equipment (UE), and a network core, where the base station is configured to: obtain capability information from the UE, where a time of obtaining the capability information of the UE is prior to that of receiving, by the base station, radio resource control connection (RRC) complete establishment signaling that is sent by the UE to the base station; and allocating a data scheduling resource to the UE according to the capacity information of the UE.

[033] With reference to the seventh aspect of the present invention, in a first possible implementation of the seventh aspect, the UE is configured to send, to the base station, an RRC connection request that carries the UE's capability information; and a specific implementation of obtaining the user equipment (UE) capability information by the base station is: the base station is configured to receive the RRC connection request that is sent by the UE and which carries the UE capability information; or the network core is configured to send, to the base station, a paging message that carries the UE's capability information; and a specific implementation of obtaining the user equipment (UE) capability information by the base station: the base station is configured to receive the paging message that is sent by the network core and which carries the UE capability information; or the network core is configured to send a first paging message to the base station; the base station is configured to receive the first paging message sent by the network core; the base station is further configured to: if the first paging message does not carry UE capability information, send to the UE a second paging message that carries indication information, where the indication information is used to instruct the UE reporting UE capability information; the UE is configured to receive the second paging message that is sent by the base station and which carries the indication information; the UE is further configured to send, to the base station, an RRC connection request that carries the UE's capability information; and a specific implementation of obtaining user equipment (UE) capability information by the base station: the base station is configured to receive the RRC connection request that is sent by the UE and which carries the UE capability information.

[034] With reference to the seventh aspect of the present invention, in a second possible implementation of the seventh aspect, the capacity information is first capacity information, and then the base station obtains the capacity information from the user equipment (UE), the network core is configured to send, to the base station, an initial context establishment request that carries the second capability information; and the base station is further configured to receive the initial context establishment request that is sent by the network core and which carries the second capability information; or the base station is further configured to send a request to obtain capability information from the UE to the UE; the UE is further configured to receive the request to obtain UE capability information sent by the base station; the UE is further configured to send the third capability information to the base station in response to the request to obtain capability information from the UE; and the base station is further configured to receive the third capability information that is sent by the UE in response to the request to obtain capability information from the UE; or the network core is configured to send, to the base station, downlink non-access stratum (NAS) transport signaling that carries the fourth capacity information; and the base station is further configured to receive downlink non-access stratum (NAS) transport signaling that are sent by the network core and which carries the fourth capacity information; or the UE is further configured to send, to the base station, RRC connection complete establishment signaling that carries the fifth capacity information; and the base station is further configured to receive the RRC connection complete establishment signaling that is sent by the UE and which carries the fifth capacity information.

[035] With reference to the seventh aspect of the present invention, in a third possible implementation of the seventh aspect, the UE is configured to send an RRC connection request to the base station, where the RRC connection request carries auxiliary routing information from a first network core and the first network core is a network core that stores context information of the UE; and a specific implementation of obtaining the user equipment (UE) capability information by the base station: the base station is configured to receive the RRC connection request sent by the UE; the base station is further configured to: determine, in accordance with auxiliary routing information of the first network core, a network core and identification information for identifying the UE by the network core; send a request to obtain UE capability information to the given network core, wherein the request to obtain UE capability information carries the identification information to identify the UE by the network core, the identification information to identify the UE by the network core is used by the given network core to obtain the context information of the UE, and the context information of the UE includes the capability information of the UE; and receiving the capability information which is from the UE and which is sent by the given network core in response to the request to obtain capability information from the UE.

[036] With reference to the third possible implementation of the seventh aspect of the present invention, in a fourth possible implementation of the seventh aspect, after the base station receives the capacity information that is from the UE and that is sent by the determined network core in response to the request to obtain UE capacity information, the base station is further configured to send UE capacity usage indications information to the UE, where the UE capacity usage indications information is used to indicate a used UE capacity in data scheduling, and the UE capacity usage indication information includes indication information to indicate whether a multi-process HARQ is used in data scheduling, and/or indication information to indicate whether a transport block size Large (TBS) is used in data scheduling.

[037] With reference to the third possible implementation of the seventh aspect of the present invention, in a fifth possible implementation of the seventh aspect, a specific implementation of determining, by the base station in accordance with the auxiliary routing information of the first network core, the core The base station is configured to: determine, in accordance with the auxiliary routing information of the first network core, a Mobility Management Entity Identifier (MME) ) globally unique (GUMMEI) of the first network core and the identification information to identify the UE by the network core; determining, in accordance with GUMMEI, whether the network cores that can be selected by the base station include the first network core; and selecting the first network core if the network cores that can be selected by the base station include the first network core; or if the network cores that can be selected by the base station do not include the first network core, select any of the network cores that can be selected by the base station.

[038] With reference to the fifth possible implementation of the seventh aspect of the present invention, in a sixth possible implementation of the seventh aspect, the auxiliary routing information of the first network core includes a temporary mobile subscriber identity (S-TMSI) of the Evolution of System Architecture (SAE).

[039] With reference to the sixth possible implementation of the seventh aspect of the present invention, in a seventh possible implementation of the seventh aspect, the auxiliary routing information of the first network core further includes at least one of the following: a public network address index selected land mobile/public land mobile network address (PLMN ID) or a Mobility Management Entity (MME) Group Identifier (MMEGI).

[040] With reference to the seventh possible implementation of the seventh aspect of the present invention, in an eighth possible implementation of the seventh aspect, the auxiliary routing information of the first network core includes the S-TMSI and the public land mobile network address index selected ID/PLMN ID, and a specific implementation of determining, by the base station according to the auxiliary routing information of the first network core, the globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core. network and identification information to identify the UE by the network core is: the base station is configured to obtain the MMEGI of the first network core from the base station according to the S-TMSI and the network address index public land mobile/PLMN ID selected; and determine, according to the S-TMSI, the selected public land mobile network address index/PLMN ID, and the MMEGI, the globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core and identification information to identify the UE by the network core.

[0041] With reference to the sixth possible implementation of the seventh aspect of the present invention, in a ninth possible implementation of the seventh aspect, a specific implementation of determining, by the base station in accordance with the auxiliary routing information of the first network core, the identifier of globally unique mobility management entity (MME) (GUMMEI) of the first network core and the identification information to identify the UE by the network core is: the base station is configured to determine an MMEGI and a PLMN ID of the first core network according to S-TMSI; and determine, in accordance with the S-TMSI, the MMEGI and the PLMN ID, the globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core and the identification information to identify the UE by the core network.

[042] With reference to the seventh possible implementation of the seventh aspect of the present invention, in a tenth possible implementation of the seventh aspect, the auxiliary routing information of the first network core includes the S-TMSI and the MMEGI, and a specific implementation of determining , by the base station according to the auxiliary routing information of the first network core, the globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core, and the identification information to identify the UE by the core network is: the base station is configured to determine the PLMN ID of the first network core according to the S-TMSI; and determining, in accordance with the S-TMSI, the MMEGI, and the PLMN ID, the globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core and the identification information to identify the UE by network core.

[043] With reference to the seventh possible implementation of the seventh aspect of the present invention, in an eleventh possible implementation of the seventh aspect, the auxiliary routing information of the first network core includes the S-TMSI, the MMEGI, and the land mobile device selected public, and the network address index/PLMN ID, and a specific deployment of determining, by the base station according to the auxiliary routing information of the first network core, the mobility management entity (MME) identifier globally unique (GUMMEI) of the first network core and the identification information to identify the UE by the network core is: the base station is configured to determine, according to the S-TMSI, the MMEGI, and the network address index selected public land mobile/PLMN ID, the globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core, and the identification information to identify the UE by the network core.

[044] With reference to any of the third to eleventh implementations of the seventh aspect of the present invention, in a twelfth possible implementation of the seventh aspect, after the base station determines, in accordance with the auxiliary routing information of the first core of network, the network core and the identification information to identify the UE by the network core, the base station is further configured to: if a network core connected to the base station is modified, send the identification information to identify the UE by the network core to a modified network core, wherein identification information for identifying the UE by the network core is used by the modified network core to request the first network core for context information of the UE.

[045] With reference to the seventh aspect of the present invention, in a thirteenth possible implementation of the seventh aspect, the UE is configured to send, to the base station, a connection establishment request or a connection reestablishment request that carries information routing auxiliaries of a first base station, wherein the first base station is a base station that stores auxiliary routing information of a second network core, and the second network core is a network core that stores context information of the UE; and a specific implementation of obtaining the user equipment (UE) capability information by the base station is: the base station is configured to receive the connection establishment request or the connection reestablishment request that is sent by the UE and which port the auxiliary routing information of the first base station; and the base station is further configured to: request the first base station for auxiliary routing information from the second network core in accordance with the auxiliary routing information of the first base station; determining, in accordance with the auxiliary routing information of the second network core, a network core and identification information for identifying the UE by the network core; send a request to obtain UE context information to the given network core, wherein the request to obtain UE context information carries the identification information to identify the UE by the network core, the identification information to identify the UE by the network core is used by the given network core to obtain the context information of the UE, and the context information of the UE includes the capability information of the UE; and receiving the context information that is from the UE and that is sent by the given network core in response to the request to obtain context information from the UE.

[046] With reference to any one of the seventh aspect, or the first to thirteenth possible implementations of the seventh aspect of the present invention, in a fourteenth possible implementation of the seventh aspect, the capability information includes at least one of the following: employment single-band/multi-band deployment, a single-tone/multi-tone indication, a control plane/user plane indication, CP/ UP), a UE-category, a radio capability, a subscriber profile identifier (SPID), access stratum release information, a multi-process HARQ capability , a large TBS capability, a new power type, a mobility improvement indication, a control plane reset capability, or a reset indication.

[047] With reference to the fourteenth possible implementation of the seventh aspect of the present invention, in a fifteenth possible implementation of the seventh aspect, the UE-category includes UE that supports or needs a multi-process HARQ and/or UE that supports or needs a large TBS.

[048] With reference to the fourteenth or fifteenth possible implementations of the seventh aspect of the present invention, in a sixteenth possible implementation of the seventh aspect, the new power type is included in a data unit control element of the MAC protocol ( MAC CE) that carries the RRC connection establishment request.

[049] With reference to the fourteenth to sixteenth possible implementations of the seventh aspect of the present invention, in a seventeenth possible implementation of the seventh aspect, the restoration includes an indication of reestablishment of the user plane (UP) and/or an indication of control plane (CP) reestablishment, the UP reestablishment indication is an indication used to indicate whether mobility improvement is supported after reestablishment, and the CP reestablishment indication is used to indicate that connection reestablishment is used for the reestablishment of CP, or is used to distinguish between the indication of CP and the indication of UP.

[050] With reference to the fourteenth to seventeenth possible implementations of the seventh aspect of the present invention, in an eighteenth possible implementation of the seventh aspect, the restoration indication is carried in a message sent by the UE to the base station, and the message includes an RRC connection reestablishment request.

[051] With reference to the eighteenth possible implementation of the seventh aspect of the present invention, in a nineteenth possible implementation of the seventh aspect, the reinstatement indication is further used as an establishment cause value for indication.

[052] With reference to the thirteenth to nineteenth possible implementations of the seventh aspect of the present invention, in a twentieth possible application of the seventh aspect, before the base station obtains the user equipment (UE) capability information, the base station is further configured to broadcast an indication of whether or not the base station supports the mobility enhancement.

[053] It can be learned that in embodiments of the present invention, a base station obtains UE capability information, where the time of obtaining the UE capability information by the base station is prior to that of receiving, by the base station, establishment signaling. complete radio resource control (RRC) connection that is sent by the UE to the base station. When data transmission is performed based on a CP transmission solution, the data is carried in a NAS message that is carried in the RRC connection establishment complete signaling sent by the UE to the base station. Therefore, the base station obtains the UE's capacity information before the UE sends the data, so that the base station can appropriately allocate a data scheduling resource to the UE according to the UE's capacity information, and the utilization of resource is increased.

[054] Aspects or other aspects of the present invention are clearer and more understandable in the descriptions of the embodiments below.

BRIEF DESCRIPTION OF THE DRAWINGS

[055] To describe the technical solutions in the embodiments of the present invention more clearly, the following briefly describes the attached drawings required to describe the embodiments or prior art. Of course, the attached drawings in the following description merely show some embodiments of the present invention, and persons of average skill in the art can still derive other drawings from these attached drawings without creative efforts.

[056] Figure 1 shows a network architecture according to an embodiment of the present invention;

[057] Figure 2 shows a schematic structural diagram of a base station according to an embodiment of the present invention;

[058] Figure 3 shows a schematic flowchart of a data scheduling method in accordance with an embodiment of the present invention

[059] Figure 3a shows a schematic diagram of a Data Volume and Energy Space Report in accordance with an embodiment of the present invention;

[060] Figure 3.1 shows a schematic flowchart of another data scheduling method in accordance with an embodiment of the present invention

[061] Figure 3.2 shows a schematic flowchart of another data scheduling method in accordance with an embodiment of the present invention.

[062] Figure 3.3 shows a schematic flowchart of another data scheduling method in accordance with an embodiment of the present invention

[063] Figure 3.b shows a schematic composition diagram of a GUTI in the data scheduling method in Figure 3.3;

[064] Figure 3.4 shows a schematic flowchart of another data scheduling method in accordance with an embodiment of the present invention

[065] Figure 4 shows a schematic flowchart of another mode of data scheduling in accordance with an embodiment of the present invention;

[066] Figure 5 shows a schematic flowchart of a connection release method in accordance with an embodiment of the present invention;

[067] Figure 6 shows a schematic structural diagram of another base station according to an embodiment of the present invention; It is

[068] Figure 7 shows a schematic structural diagram of a communications system according to an embodiment of the present invention.

DESCRIPTION OF MODALITIES

[069] To make people skilled in the art better understand the technical solutions in the present invention, the following clearly describes the technical solutions in the embodiments of the present invention with reference to the attached drawings in the embodiments of the present invention. Of course, the described embodiments are merely some of and not all embodiments of the present invention. All other embodiments obtained by persons of ordinary skill in the art based on embodiments of the present invention without creative efforts will fall within the scope of protection of the present invention.

[070] Detailed descriptions are provided separately below.

[071] In the description, claims and accompanying drawings of the present invention, the terms "first", "second", "third", "fourth" and so on are intended to distinguish between different objects, but do not indicate particular order. Furthermore, the terms "including", "including", or any other variant, are intended to cover a non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the steps or units listed, but optionally includes an unlisted step or unit, or optionally includes plus another step or inherent unit of the process, the method, product or device.

[072] The "modality" mentioned in this specification means that a particular functionality, structure, or characteristic described with reference to the embodiments can be included in at least one embodiment of the present invention. Such phrases that appear everywhere in the specification are not necessarily the same modality nor an independent or alternative modality that is mutually exclusive from another modality. Persons skilled in the art should explicitly and implicitly understand that the embodiments described in the specification may be in combination with another embodiment.

[073] To better understand a data scheduling method, a base station, and a system disclosed in embodiments of the present invention, the following first describes a network architecture that is applicable to embodiments of the present invention. With reference to Figure 1, Figure 1 is a schematic diagram of a network architecture in accordance with an embodiment of the present invention. The network architecture shown in Figure 1 may include a base station, UE and a network core. In the network architecture shown in Figure 1, the UE may include various terminal devices, such as a mobile phone, a tablet computer, a Personal Digital Assistant (PDA), a Mobile Internet Device, MID) and a smart device that can be worn on the body (such as a smart wristwatch and a smart band). This is not limited to this embodiment of the present invention. The base station can be an evolved NodeB in an LTE system or an LTE-Advanced system, or it can be a NodeB in a Universal Mobile Telecommunication System (UMTS). This is not limited to this embodiment of the present invention. The network core can be an MME. The data scheduling method provided in the present invention is applied to communication in various systems, such as M2M and IoT.

[074] Figure 2 is a schematic diagram of a base station according to an embodiment of the present invention. The base station 200 includes at least one processor 201, a communications bus 202, a memory 203, at least one communications interface 204, and a transceiver 205.

[075] The processor 201 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits that are configured to control the program execution of the solutions in the present invention.

[076] Communications bus 202 may include a channel through which information is transmitted between preceding components. Communication interface 204 uses any device of a transceiver type to communicate with another device or communications network, such as an Ethernet, a radio access network (RAN), or a Wireless Local Area Networks. , WLAN).

[077] Memory 203 may be a read-only memory (ROM) or another type of static storage device that can store static information and a static instruction or a random access memory (RAM). , or other type of dynamic storage device that can store information and instructions; or may be an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM), or other optical disk storage or optical disc (including a compact disc, a laser disc, an optical disc, a digital versatile disc, a Blu-ray disc, and the like), a disc storage medium or other magnetic storage device, or any other medium that can be used to carry or store expected program code in the form of an instruction or data structure and which can be accessed by a computer. However, this is not limited in this document. Memory can exist independently and be connected to the processor through the use of a bus. Alternatively, the memory can be integrated with the processor.

[078] Memory 203 is configured to store application program code that executes the solutions of the present invention, and processor 201 controls execution. Processor 201 is configured to execute application program code stored in memory 203.

[079] The code stored in memory 203 of the base station shown in Figure 2 can be executed to perform the data scheduling method provided in the present invention, for example, obtaining UE capacity information, and then allocating a data scheduling resource. data to the UE according to the UE's capability information.

[080] In specific implementation, in one embodiment, the base station 200 may further include the transceiver 205. The transceiver 205 communicates with the processor 201, and may display information in multiple ways. The transceiver 205 communicates with the processor 201, and can receive, in multiple ways, signaling sent by an application server or a service layer device.

[081] According to the technical solution described above, in a specific embodiment, Figure 3 is a schematic flowchart of a data scheduling method, including a specific execution process of a base station. Although the data scheduling method described herein is performed by the base station shown in Figure 2, it should be noted that a specific execution environment of the data scheduling method disclosed in this embodiment of the present invention is not limited to the base station.

[082] As shown in Figure 3, the data scheduling method disclosed in this method embodiment of the present invention specifically includes the following steps.

[083] S301. A base station obtains capability information from the user equipment (UE), where the time of obtaining the UE capability information is prior to that of receiving, by the base station, radio resource control connection establishment complete (RRC) signaling. ) which is sent by the UE to the base station.

[084] Optionally, the UE capability information may include at least one of the following: a UE priority, (single-band/multi-band deployment) a single-band/multi-band deployment, a single/multi-band indication single-tone/multi-tone indication (an indication of a scheduling unit, which may specifically be a single subcarrier, a carrier or the like), a CP/UP (control plane/user plane indication), a UE category, a Subscribe Profile Identifier (SPID), a radio capability, access stratum release information, a hybrid autoretry request capability of multiple processes (Hybrid-ARQ, HARQ), a large Transport Block Size (TBS) capacity, a new power type (New Power Class), an indication of improved mobility, or an indication of restoration.

[085] For example, the UE-category includes the UE that supports or needs a multi-process HARQ and/or the UE that supports or needs a large TBS.

[086] For example, the reset indication includes a UP (user plane) reset indication and/or a CP (control plane) reset indication.

[087] For example, the UP reestablishment indication is an indication used to indicate whether or not mobility improvement is supported after reestablishment.

[088] For example, the CP reestablishment indication is used to indicate that the connection reestablishment is used for CP reestablishment solution, or it is used to distinguish between the CP indication and the UP indication.

[089] For example, the reestablishment indication is carried in a message sent by the UE to the base station, and the reestablishment indication is used as an establishment cause value for indication.

[090] For example, the reestablishment indication is carried in a message sent by the UE to the base station, and the message may be an RRC connection reestablishment request, an RRC connection establishment request, a connection resumption request RRC, or similar.

[091] For example, the reestablishment indication may be used as an establishment cause value in the message for indication, or the reestablishment indication may be used as an indication information element in the message.

[092] For a CP solution, a reset procedure is not supported in R13. However, after the introduction of R14, a distinctive indication needs to be given for a CP solution and a UP solution. The reestablishment indication may be a reestablishment indication used only for a CP solution, or an indication message used to distinguish between CP reestablishment and UP solution reestablishment. Alternatively, the reinstatement indication may be an indication to distinguish between UP reinstatement in different releases. The CP solution refers to optimization in a control plane, and the UP solution is an optimization solution in a user plane.

[093] In R13, NB-IoT UP UE does not support mobility enhancement, that is, it does not support a PDCP STATUS REPORT procedure, or X2 interface data transfer and a UE context in the reestablishment procedure. In R14, the UE supports mobility enhancement. Therefore, mobility improvement is used as a capability, and the UE may consider supporting a PDCP STATUS REPORT procedure or uplink data retransmission and X2 interface data transfer and a UE context. Uplink data retransmission means that when the UE sends uplink data during a previous connection, but before a cell handover, does not receive an acknowledgment that a receiver has received the data, the UE needs to support a receive capability a PDCP status report (PDCP STATUS REPORT) in a reestablishment procedure, so as to learn an uplink PDCP SN corresponding to data that is not sent to a base station, and perform retransmission. Since PDCP STATUS REPORT is not supported in R13, the UE cannot perform uplink data retransmission.

[094] As a UE capability, mobility enhancement is mainly used when the UE moves, for example, during an RRC connection re-establishment procedure (such as a cell change, a cell transfer, or new cell selection). cell) triggered by an RLF. When the UE using a UP solution sends an RRC connection reestablishment request to a target base station, after receiving the indication information, the base station may learn that the UE can support at least one procedure or transfer of a PDCP STATUS REPORT of context and data between base stations. The UE in this document may be UE using a UP solution in an NB-IoT.

[095] The indication information may represent an indication of mobility improvement capability, or other information such as an indication of release information.

[096] After receiving related indication information, a target base station can transfer the indication information on an X2 interface, so that a source base station performs corresponding processing, and forwards a UE context and data to the station target base. The indication information includes at least one mobility improvement indication, a UP reestablishment indication, a reestablishment indication, or a CP reestablishment indication.

[097] Optionally, the base station broadcasts an indication of whether or not the base station supports the mobility improvement.

[098] From a base station perspective, mobility improvement can be considered as a base station capability. Different base stations may have different capabilities to support UE mobility. For example, a base station on R13 may not support a reset procedure used for a CP, or may not support X2 interface data forwarding in a UP solution. However, a base station on R14 may support one or both of a reestablishment procedure used for a CP or X2 interface data forwarding in a UP solution. The base station may indicate whether the base station supports mobility enhancement, and may separately indicate different capabilities, for example, whether CP reestablishment or UP mobility enhancement is supported, or may uniformly indicate capabilities related to mobility enhancement, e.g. For example, it may broadcast an indication using a system message. Specifically, when the base station supports a mobility enhancement capability, the base station provides an indication via a system broadcast. The base station may use 1 bit to indicate or uniformly use multiple bits to separately indicate multiple specific capabilities included in mobility enhancement. When performing RRC connection establishment or RRC connection reestablishment, the UE can choose, according to an indication message, whether or not to access a cell or a base station. For example, when the base station broadcasts an indication of supporting a mobility enhancement capability, the UE supporting the mobility enhancement may choose to access a cell; or if the base station does not support a mobility enhancing capability, that is, the base station does not broadcast an indication of supporting a mobility enhancing capability, or an indication of not supporting a mobility enhancing capability, the UE You can choose not to access the cell. After the UE accesses the cell, the base station can perform different operations according to the UE capabilities, for example, handling low priority, rejecting or releasing a connection, and transferring capability information to another node.

[099] Optionally, the base station may notify, through the use of dedicated signaling, the UE of whether a base station supports a mobility enhancement capability. After the UE accesses the cell, the base station may notify the UE by using dedicated signaling, such as an RRC connection establishment, RRC connection reestablishment, RRC connection rejection or release message, or other message.

[0100] Specifically, for example, after the UE sends an RRC connection reestablishment request when the UE accesses a target cell, if the target base station does not have an available UE context, and does not support a mobility enhancement capability , the target base station notifies the UE by using dedicated signaling.

[0101] Optionally, when selecting or reselecting a cell, the UE may consider this factor for cell selection. Optionally, the base station broadcasts some cells that support mobility enhancement, and the base station may broadcast, in a system broadcast, an offset of a cell that supports mobility enhancement capability. mobility. The UE supporting a mobility enhancement capability may use shifting for cell selection or reselection. In another optional manner, reselection or selection is performed only on cells that support a mobility improvement capability, and a sorting mechanism or a priority mechanism may be used. Alternatively, the UE supporting mobility enhancement may consider that a cell supporting mobility enhancement has a high priority and may preferentially select the cell during selection. Optionally, when the base station learns whether another cell supports a mobility-enhancing capability, the base station may set a cell-specific offset for a cell that supports a mobility-enhancing capability.

[0102] For the UE that has accessed a cell that supports mobility enhancement, when the UE moves, for example, when the UE is transferred, when an RLF triggers a reestablishment procedure, or when the connected mode UE performs reselection of cells, if a target base station accessed by the UE does not support mobility enhancement, that is, the target base station does not support an operation such as forwarding a UE context and data between base stations, the target base station may reject or release a UE connection, or redirect the UE to another cell that supports this functionality, or reestablish a connection. Alternatively, the target base station may give an indication to a source base station, and the source base station may only transfer a UE context according to the indication information; or the target base station may instruct the source base station to delete a stored UE context and stored data.

[0103] If a base station initially accessed by the UE does not support mobility enhancement, but a target base station of a cell accessed by the UE supports forwarding data and a UE context after the UE moves, optionally, the UE may give a indication to the target base station, to indicate that the base station that previously establishes a connection with the UE does not support mobility enhancement. If the target base station does not have a UE context, the target base station may reject or release a connection, or reestablish a connection. Alternatively, when the target base station receives a reset request from the UE, the target base station sends an RLF indication, a get context request or other indication message to a source base station, and the source base station may return information indication to reject or not support this operation, or you can transfer just a UE context without transferring data, and give an indication. A specific support message is not limited and can be an existing X2 interface message or can be a new message.

[0104] The base station broadcasts an indication of a UE category or a UE capability used specific to a multicast service of the base station. For a multicast service, such as a Single Cell Point To Multipoint (SC-PTM) service in NB-IoT, because different UEs have different categories and capabilities, the base station needs to broadcast an indication of a specific UE category or UE capability for such type of multicast service transmission, so that the UE determines, according to the UE category or UE capability, whether or not to accept the multicast service. For example, the indication may include an indication of whether a common TBS or large TBS is used in multicast service transmission, an indication of whether a single-process HARQ or a multi-process HARQ is used in multicast service transmission, an indication of the EU category, and the like. Furthermore, since multiple SC-PTM services are performed in a network at the same time, the previous indication may be for all SC-PTM services in a current cell. To implement flexible control, the base station can also separately provide the previous indication for each SC-PTM service.

[0105] It should be noted that a time where the base station broadcasts the UE category indication or UE used capacity specific to the base station multicast service may or may not be prior to step S301. Furthermore, the UE in idle mode can also receive the indication. There is no limitation on this in the present invention.

[0106] Optionally, the new power type is included in a control element (MAC CE) of the MAC protocol data unit (MAC PDU) that carries the RRC connection establishment request. For example, a new UE power type is indicated in a MAC CE Data Volume and Power Headroom Report shown in Figure 3.a. A specific way might be as follows: An existing reserved bit R is used to provide an indication of a new energy type. A number of reserved bits used depends on a number of new energy types that need to be indicated. If only one new power type is supported on a network, only one reserved bit need be used to indicate the new power type; or if two or three new energy types are supported on a network, two reserved bits need to be used to indicate the new energy types. Designing a new MAC CE can be avoided by using a reserved bit in an existing MAC CE to provide an indication of a new power type. Furthermore, signaling overheads can be reduced by communicating the new energy type and other information to the base station.

[0107] For example, with reference to Figure 3.1, Figure 3.1 is a schematic flowchart of another data scheduling method in accordance with an embodiment of the present invention.

[0108] Optionally, a specific implementation of obtaining user equipment (UE) capability information by the base station is: the base station receives an RRC connection request that is sent by the UE and which carries the UE capability information. Specifically, the RRC connection request sent by the UE to the base station carries the UE's capability information. The capability information may be all UE capability information, or it may be some UE capability information. This specifically depends on an RRC connection request signaling capability. If the capacity of the RRC connection request signaling is sufficient, the RRC connection request signaling carries all the capacity information of the UE; or if the capacity of the RRC connection request signaling is limited, the RRC connection request signaling carries some necessary capability information from the UE, for example, a UE priority, a single-tone/multi-tone indication, or a CP/ UP. Optionally, some UE capability information can be grouped and written to a protocol. The RRC connection request signaling only needs to carry an index number of a group of UE capability information without carrying the UE capability information.

[0109] Optionally, a specific implementation of obtaining the user equipment (UE) capability information by the base station is: the base station receives a paging message that is sent by a network core and which carries the UE capability information. HUH. Specifically, when the network core delivers the paging message to the base station, if the network core stores UE context information, the network core adds the UE's capability information to the paging message sent to the base station, and the UE context information includes UE capability information. After receiving the capability information from the UE, the base station stores the UE capability information for subsequent use after a connection to the UE.

[0110] Optionally, a specific implementation of obtaining user equipment (UE) capability information by the base station is: the base station receives a first paging message sent by a network core; If the first paging message does not carry the UE's capability information, the base station sends, to the UE, a second paging message that carries indication information, where the indication information is used to instruct the UE to report the information of UE capacity; and the base station receives an RRC connection request which is sent by the UE and which carries the capability information of the UE. Specifically, if the network core does not store UE context information, the first paging message sent by the network core to the base station does not carry the UE capability information, and the base station adds the indication information to the second message paging number sent to the UE. The indication information used to indicate that the UE needs to subsequently report the UE capability information to the base station, and the UE may add the UE capability information to the RRC connection request signaling subsequently sent to the base station. In another embodiment, the UE may also add the UE capability information to other signaling subsequently sent to the base station, e.g., RRC connection establishment complete signaling.

[0111] For example, with reference to Figure 3.2, Figure 3.2 is a schematic flowchart of another data scheduling method in accordance with an embodiment of the present invention.

[0112] Optionally, the capacity information includes the first capacity information, and the capacity information further includes second capacity information, third capacity information, fourth capacity information, or fifth capacity information. A base station obtaining capability information from the user equipment (UE) includes: the base station receives an RRC connection request that is sent by the UE and which carries the first capability information; and the base station receives an initial context establishment request that is sent by a network core and which carries the second capability information. Alternatively, a base station obtaining capability information from user equipment (UE) includes: the base station receiving an RRC connection request that is sent by the UE and carrying the first capability information; the base station sends a request to obtain capability information from the UE to the UE; and the base station receives the third capability information that is sent by the UE in response to the request to obtain capability information from the UE. Alternatively, a base station obtaining capability information from user equipment (UE) includes: the base station receiving an RRC connection request that is sent by the UE and carrying the first capability information; and the base station receives uplink Non Access Stratum (NAS) transport signaling that is sent by a network core and which carries the fourth capacity information. Alternatively, a base station obtaining capability information from the user equipment (UE) includes: the base station receiving an RRC connection request that is sent by the UE and carrying the first capability information; and the base station receives the RRC connection establishment complete signaling that is sent by the UE and which carries the fifth capacity information.

[0113] Specifically, since the capacity of the RRC connection request signaling provided by the UE to the base station is limited, the RRC connection request signaling can only carry some necessary capacity information (the first capacity information) of the UE, e.g. example, a UE priority, a single-tone/multi-tone indication, and a CP/UP indication. If the UE still needs to transmit uplink data subsequently, so that the base station can more appropriately allocate a data scheduling resource to the UE, after the UE sends the first capacity information to the base station, the base station needs to obtain UE remaining capacity information. Specific methods of obtaining the remaining capacity information may include the following: 1. The network core may add the second capacity information to the initial context establishment request signaling delivered to the base station (or other signaling delivered by the network core to the base station). Optionally, before the network core sends the initial context establishment request signaling to the base station (or the network core sends another signaling to the base station), the base station may add indication information to signaling information. Initial UE sent to the network core, to indicate capability information that is from the UE and should be sent by the network core to the base station. 2. The base station sends the request to obtain UE capability information (specifically, the base station may send UE capability information obtain signaling to the UE, or the base station may deliver other signaling to the UE) to the UE . The request for obtaining UE capability information may carry indication information, to indicate UE capability information, which is sent by the UE to the base station, and the UE sends the third capability information to the base station in response to the request to obtain UE capability information. 3. When the network core needs to deliver uplink data, the network core can add the fourth capacity information to the downlink NAS transport signaling sent to the base station. 4. The UE sends the RRC connection establishment complete signaling to the base station, and the signaling carries the fifth capability information of the UE. Optionally, before the UE sends the RRC connection establishment complete signaling to the base station, the base station may add indication information to the RRC connection establishment request signaling sent to the UE, to indicate capability information that is from the UE and which are sent by the network core to the base station. Optionally, as a capacity of the RRC complete connection establishment signaling is relatively large, the signaling can carry all the capability information of the UE. In this case, the fifth capacity information may include the first capacity information.

[0114] Optionally, the second capacity information, the third capacity information, the fourth capacity information, and the fifth capacity information may be the same capacity information, or may be different capacity information. There is no limitation on this in the present invention.

[0115] Optionally, a relationship between the first capacity information and each of the second capacity information, the third capacity information, the fourth capacity information, or the fifth capacity information may be an inclusion relationship, or may be an intersection relationship, or they may be an incompatibility relationship, or the like. There is no limitation on this in the present invention.

[0116] For example, with reference to Figure 3.3, Figure 3.3 is a schematic flowchart of another data scheduling method in accordance with an embodiment of the present invention.

[0117] Optionally, a specific implementation of obtaining the user equipment (UE) capability information by the base station is: the base station receives an RRC connection request sent by the UE, where the RRC connection request carries auxiliary routing information of a first network core, and the first network core is a network core that stores context information of the UE; the base station determines, according to the auxiliary routing information of the first network core, a network core and identification information for identifying the UE by the network core; the base station sends a request to obtain UE capability information to the given network core, where the request to obtain UE capability information carries the identification information to identify the UE by the network core, the identification information to identify the UE by the network core is used by the given network core to obtain the context information of the UE, and the context information of the UE includes the capability information of the UE; and the base station receives the capability information that is from the UE and that is sent by the given network core in response to the request to obtain capability information from the UE.

[0118] For example, when sending a request to obtain UE capability information to the network core, the base station adds the identification information to identify the UE by the network core (the identification information to identify the UE by the network core network are used by the network core to find, according to the identification information, the context information that is from the UE and which is stored in the network core, and the identification information to identify the UE by the network core can be a globally unique temporary UE identity (GUTI), or a combination of a globally unique mobility management entity (MME) identifier (Globally Unique MME Identity, GUMMEI) and a temporary mobile subscriber identity ( System Architecture Evolution (SAE) S-TMSI, or an S-TMSI, or an eNB MME ID S1AP ID, or an S1AP UE ID pair, or similar ) for the request to obtain UE capability information in order to verify whether the given network core is a network core that stores the UE's context information (or a network core with which the UE is previously registered) . If the given network core is the network core that stores the UE's context information (or the network core with which the UE is previously registered), the given network core can directly obtain the pre-stored context information of the UE according to the identification information to identify the UE by the network core; or if the given network core is not the network core that stores the UE's context information (or the network core with which the UE is previously registered), the given network core obtains, according to the identification to identify the UE by the network core, the context information of the UE from a network core (the first network core) that is previously connected to the UE, and then the determined network core adds the capability information of the UE to the signaling sent to the base station, to send the capability information of the UE to the base station.

[0119] Optionally, the GUTI includes a PLMN ID, an MMEI, and an M-TMSI. A specific composition of GUTI is shown in Figure 3b.

[0120] Optionally, the base station sending the request to obtain UE capability information to the given network core may be implemented by using UE capability information request signaling sent by the base station to the network core, or can be implemented by using other signaling sent by the base station to the network core. There is no limitation on this in the present invention.

[0121] Optionally, as shown in Figure 3.4, after step S301 where the base station obtains the user equipment (UE) capacity information, the method further includes: the base station sends UE capacity usage indication information for the UE, where the UE capacity usage indication information is used to indicate a UE capacity used in data scheduling, and the UE capacity usage indication information includes indication information to indicate whether a HARQ of multiple processes is used in data scheduling, and/or indication information to indicate whether a TBS is used in data scheduling.

[0122] For example, currently, the 3GPP organization has completed the standardization of the NB-IoT of Rel-13, and is improving the NB-IoT of Rel-14. In Rel-13, a rate supported by an NB-IoT terminal is low, and an application scenario is limited. Two new features: a dual-process HARQ (there is only a single-process HARQ in Rel-13) and a higher TBS are introduced in the NB-IoT of Rel-14, to increase the transmission rate of the NB-IoT terminal. Currently, a UE capability obtained by the base station does not include a newly introduced dual-process HARQ capability or a large TBS capability, and the base station cannot use both capabilities in an RRC connection establishment message or in scheduling. subsequent data, to perform scheduling for the UE. As a result, scheduling performance is affected.

[0123] In this embodiment of the present invention, the base station first obtains a UE capability, and then indicates whether the UE supports new features that include a multi-process HARQ capability and a large TBS capability. If the obtained UE capability supports the two new features, the base station may indicate in the RRC connection establishment message whether the two new features are used in subsequent data scheduling for the UE. The UE separately indicates support for the two features. For example, a separate indication (e.g., 1 bit) is used to indicate whether multi-process HARQ is supported, and another separate indication is used to indicate whether large TBS is supported. Of course, a uniform indication can also be used to indicate whether the UE supports both two functionalities (because the two functionalities are to implement a high data rate, the uniform indication results in less overheads). Additionally, a name of an indication can be a UE capability or can be a UE type. Furthermore, in the same way, for an indication to the UE, the base station may use two separate indications, or it may use a uniform indication.

[0124] Furthermore, the base station needs to give an indication to the UE, because both of the two new features are to provide a higher transmission rate, and the NB-IoT needs to ensure network coverage first. When the UE is in relatively poor coverage, a large amount of repeated transmissions need to be performed to improve coverage, and therefore high transmission rate cannot be implemented. That is, although some new UEs or UEs with a relatively strong capacity have the ability to support both new features, in some cases (e.g., when the UE is in weak coverage), the base station does not necessarily perform scheduling for the EU for the use of both functionalities. If the two features are used, it affects a UE's Downlink Control Information (DCI) format, a discontinuous reception behavior time sequence relationship, and so on. Therefore, to avoid a scheduling failure or a reduction in transmission efficiency, the base station needs to indicate whether the two capabilities are used for subsequent scheduling to the UE.

[0125] Optionally, a specific deployment of determining, by the base station according to the auxiliary routing information of the first network core, the network core and the identification information for identifying the UE by the network core is: the base station determines, in accordance with the auxiliary routing information of the first network core, a GUMMEI of the first network core and the identification information for identifying the UE by the network core; the base station determines, in accordance with GUMMEI, whether network cores that can be selected by the base station include the first network core; and the base station selects the first network core if the network cores that can be selected by the base station include the first network core; or the base station selects any of the network cores that can be selected by the base station if the network cores that can be selected by the base station do not include the first network core.

[0126] For example, the RRC connection request signaling sent by the UE to the base station carries the auxiliary routing information of the first network core, and the base station can determine, according to the auxiliary routing information of the first core network core, the GUMMEI of the first network core, and the identification information to identify the UE by the network core. The base station determines, according to GUMMEI, whether the base station can be connected to the first network core. The base station selects the first network core if the first network core exists in the network cores that can be connected to the base station; or if the first network core does not exist in the network cores that can be connected to the base station, the base station selects any of the network cores that can be connected to the base station.

[0127] Optionally, the auxiliary routing information of the first network core includes an S-TMSI.

[0128] Optionally, the auxiliary routing information of the first network core includes at least one of the following: a selected public land mobile network (PLMN) address index ID or a mobility management entity (MME) group identifier (MME group ID, MMEGI).

[0129] Optionally, the auxiliary routing information of the first network core includes the S-TMSI and the selected public land mobile network address index/PLMN ID. A specific deployment of determining, by the base station according to the auxiliary routing information of the first network core, the globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core and the identification information for identifying the UE by the network core is: the base station obtains the MMEGI of the first network core of the base station according to the S-TMSI and the selected public land mobile network address index/PLMN ID; and determines, in accordance with the S-TMSI, the selected public land mobile network address index/PLMN ID and the MMEGI, the globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core and the identification information to identify the UE by the network core.

[0130] Specifically, a group of network cores that are previously connected to some specific UEs are not modified. That is, the MMEGIs of the network cores that are connected to the UEs are not modified. The base station can store information such as MMMEIs and S-TMSIs of the UEs. In this case, the RRC connection request sent by the UE to the base station needs to carry only the selected public land mobile network address index or PLMN ID and S-TMSI without carrying information such as the MMEGI of the UE. The base station can obtain information such as the pre-stored MMEGI according to the selected public land mobile network address index/PLMN-ID and the S-TMSI and form, according to the PLMN-ID, the S-TMSI and the MMEGI, GUMMEI and identification information to identify the UE by the network core. The base station is used to store auxiliary routing information for some network cores. The base station can obtain the auxiliary routing information by using the S-TMSI as an identification code. After the S-TMSI is updated, the network core can add the updated S-TMSI to the downlink signaling sent to the base station, or it can add the updated S-TMSI to some new signaling, for example, a suspend RRC connection, S1-AP: a deactivate context ACK from UE S1 in S1-AP and an initial context establishment request. There is no limitation on this in the present invention. Of course, the S-TMSI in this embodiment of the present invention can also be another UE identifier, such as a C-RNTI. It should be noted that a method for storing information by a base station is not limited to the aforementioned method, and another method for storing information by a base station, and the use of, as an identification code, the S-TMSI or other information updated during interaction between the UE and a network core can be the aforementioned method.

[0131] Optionally, the auxiliary routing information of the first network core includes the S-TMSI and the selected public land mobile network address index/PLMN ID. A specific deployment of determining, by the base station according to the auxiliary routing information of the first network core, the globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core and the identification information for identify the UE by the network core: the base station determines the MMEGI of the first network core according to the S-TMSI and the selected public land mobile network address index/PLMN ID; and determines, in accordance with the S-TMSI, the selected public land mobile network address index/PLMN ID and the MMEGI, the globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core and the identification information to identify the UE by the network core.

[0132] Specifically, for some specific UEs, it is assumed that the base station belongs to only one type of network core group, that is, an MMEGI of a network core that is connected to the base station is unmodified and unique . When the UE switches from an idle mode to a connected mode, the UE adds the selected public land mobile network address index/PLMN-ID and the S-TMSI to RRC connection request signaling sent to the base station. When the base station connected to the UE is the same as a base station previously connected to the UE, as the MMEGI of the network core connected to the base station is unique, the base station can determine, according to the selected public land mobile network, the address index and the S-TMSI, the MMEGI of the network core previously connected to the UE and the base station may form, according to the PLMN-ID, the S-TMSI and the MMEGI, the GUMMEI of the previously connected network core to the UE and the identification information to identify the UE by the network core. Subsequently, the base station can obtain UE capability information and UE context information using the network core. For a specific deployment, reference the deployment described in Figure 3.3. Details are not described in this document again.

[0133] Optionally, when the base station connected to the UE is not a base station previously connected to the UE, it needs to be indicated that the network core does not need to send the UE's capability information to the base station. A specific indication way is as follows: 1. 1-bit indication information can be carried in the RRC connection request signaling sent by the UE to the base station, and the indication information is used to indicate that the base station does not need obtain the UE capability information according to the manner described in Figure 3.3 to obtain the UE capability information. 2. Alternatively, the base station may determine, by use of the information carried by the UE, whether the base station needs to obtain the UE's capability information using the method described in Figure 3.3 for obtaining the UE's capability information. If the aforementioned obtaining method is not used, a method in another embodiment of the present invention or similar may be used.

[0134] Optionally, the auxiliary routing information of the first network core includes the S-TMSI. A specific implementation of determining, by the base station according to the auxiliary routing information of the first network core, the globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core is: the base station determines an MMEGI and a PLMN ID of the first network core according to S-TMSI; and the base station determines, in accordance with the S-TMSI, the MMEGI and the PLMN ID, the globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core and the identification information to identify the UE by the network core.

[0135] Specifically, a group of network cores that are previously connected to some specific UEs are not modified. That is, MMEGIs of the network cores that are connected to the UEs are not modified, and the UE supports only one PLMN. In this case, the RRC connection request signaling sent by the UE to the base station only carries the S-TMSI, and the base station can determine the MMEGI and PLMN ID of the first network core according to the S-TMSI, and then determine, according to the S-TMSI, the MMEGI, and the PLMN ID, the MME GUMMEI identifier of the first network core and the identification information for identifying the UE by the network core.

[0136] Optionally, the auxiliary routing information of the first network core includes the S-TMSI and the MMEGI. The base station determines, according to the auxiliary routing information of the first network core, a globally unique mobility management entity identifier (MME) of the first network core includes: the base station determines the PLMN ID of the first network core according to S-TMSI; and the base station determines, according to the S-TMSI, the MMEGI and the PLMN ID, the GUMMEI of the first network core and the identification information for identifying the UE by the network core. Specifically, when the UE supports only one PLMN, the RRC connection request signaling sent by the UE to the base station only carries the S-TMSI and MMEGI, and the base station can determine the PLMN ID of the first network core accordingly. with the S-TMSI, and then determine, according to the S-TMSI, the MMEGI and PLMN ID, the MME GUMMEI identifier of the first network core, and the identification information to identify the UE by the network core.

[0137] Optionally, the auxiliary routing information of the first network core includes the S-TMSI, the MMEGI, and the selected public land mobile network address index/PLMN ID, and the base station determines, in accordance with the information routing aids of the first network core, a globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core, and the identification information to identify the UE by the network core includes: the base station determines, according to the S-TMSI, the MMEGI and the selected public land mobile network address index/PLMN ID, the GUMMEI of the first network core and the identification information to identify the UE by the network core.

[0138] Optionally, the request for obtaining UE capability information sent by the base station to the given network core may carry the S-TMSI, so that the network core identifies the UE. Optionally, the request for UE capability information sent by the base station to the given network core may carry the S-TMSI, a UE S1AP eNB ID, an LTE Tracking Area Identity (TAI), an evolved UMTS terrestrial radio access network (Evolved UMTS Terrestrial Radio Access Network, E-UTRAN CGI), an RRC establishment cause and the like. When the network core sends the UE capability information to the base station, the UE capability information, a unique UE identifier of the S1 interface on the MME side (UE S1 MME Application Protocol ID, UE S1AP MME ID) , a unique UE identifier of the S1 interface on the eNB side (eNB UE S1 application protocol ID, eNB UE S1AP ID), a UE aggregate maximum bit rate, and the like are ported at the same time. In this way, only one NAS PDU is carried in the initial UE information signaling, subsequently sent by the base station to the network core. The initial UE information signaling can be modified to NAS transport signaling uplink and a signaling name is not limited herein. Of course, after the UE sends the RRC connection request to the base station, the UE capability request signaling that is sent by the base station to the network core can also be modified to the initial UE information/information signaling. uplink NAS transmission network. A flag name is not limited in this document, and the content carried in the flag is the same as that described above.

[0139] Optionally, after the base station determines, according to the auxiliary routing information of the first network core, the network core and identification information for identifying the UE by the network core, whether a connected network core to the base station is modified, the base station sends, to a modified network core, the identification information to identify the UE by the network core, and the identification information to identify the UE by the network core is used by the network core modified to ask the first network core for the UE context information.

[0140] For example, with reference to Figure 3.4, Figure 3.4 is a schematic flowchart of another data scheduling method in accordance with an embodiment of the present invention.

[0141] Optionally, a specific implementation of obtaining the user equipment (UE) capability information by the base station is: the base station receives a connection establishment request or a connection reestablishment request that is sent by the UE and which carries auxiliary routing information from a first base station, wherein the first base station is a base station that stores auxiliary routing information from a second network core, and the second network core is a network core that stores context information of the HUH; the base station requests the auxiliary routing information of the second network core from the first base station in accordance with the auxiliary routing information of the first base station; the base station determines, according to the auxiliary routing information of the second network core, a network core and identification information to identify the UE by the network core; the base station sends a request to obtain context information from the UE to the given network core, where the request to obtain context information from the UE carries the identification information to identify the UE by the network core, the identification information to identify the UE by the network core is used by the given network core to obtain the context information of the UE, and the context information of the UE includes the capability information of the UE; and the base station receives the context information that is from the UE and that is sent by the given network core in response to the request to obtain context information from the UE.

[0142] The auxiliary routing information of the first base station includes a Cell Radio Network Temporary Identifier (C-RNTI), a physical cell identifier, and an S-TMSI.

[0143] For example, when a connection between the UE and a base station connected to the UE fails, a connection reestablishment operation is performed between the UE and a new base station. The UE carries the C-RNTI, the physical cell identifier, and the S-TMSI, and initiates a connection reestablishment procedure with the new base station, so that the new base station finds, according to the previous information, the base station previously connected to the UE, obtains, through the use of an X2 interface from the base station previously connected to the UE, routing auxiliary information from a network core (the second network core) previously connected to the UE, such as an MMEGI of the network core, obtains information about the network core previously connected to the UE, and further obtains the context information of the UE by using the network core previously connected to the UE, thus implementing the connection re-establishment procedure. The UE context information includes the UE capability information. For a specific process of obtaining UE context information by the base station, refer to the method described in Figure 3.3, and details are not described in this document again. If a base station that is currently connected to the UE is the same as the base station previously connected to the UE, the procedures for obtaining the context information from the UE are the same.

[0144] S302. The base station allocates a data scheduling resource to the UE according to the capacity information of the UE.

[0145] Specifically, after receiving the capability information of the UE, the base station allocates the data scheduling resource to the UE according to the capability information of the UE, and sends RRC connection establishment signaling to the UE. The RRC connection establishment signaling ports the data scheduling resource allocated by the base station to the UE. After receiving the RRC connection establishment signaling, the UE sends RRC connection establishment complete signaling and, according to the data scheduling resource allocated by the base station to the UE, adds data that needs to be reported to a network by the UE for a NAS message sent at this time.

[0146] For example, UE capability information includes a CP/UP indication. The base station correspondingly sets a PDCP header in the subsequent data transmission or signaling transmission. For example, a PDCP header is short when a CP is used for data transmission, while a PDCP header is long when a UP transmission solution is used. The CP/UP indication includes the following: 1. An indication is provided by use of a Packet Data Convergence Protocol (PDCP) header of the RRC connection establishment complete signaling sent by the UE to the station base. A PDCP header with fewer bytes (e.g., 1 byte) does not have MAC-I, and is used to indicate that a CP is used for data transmission, and a PDCP header with more bytes (e.g., 5 bytes) has a MAC -I, and is used to indicate that a UP is used for data transmission. 2. If a base station connected to the UE is the same as a base station previously connected to the UE, a PDCP short header will be used to send an RRC connection request. If there is a UE context on a base station side, it indicates that a UP is used for data transmission, and the base station performs a subsequent related configuration according to a UP functionality. If there is no UE context on a base station side, the base station performs subsequent related configuration according to a CP functionality. 3. If a base station connected to the UE is different from a base station previously connected to the UE, a short PDCP header is still used to send RRC connection complete establishment signaling. If there is no UE context information on one side of the base station, the base station still uses the related CP configuration. After the UE sends the RRC connection establishment complete signaling, the base station can determine, according to a size of a NAS packet, whether a CP or a UP is used, and perform the subsequent configuration. 4. Similarly, a long PDCP header can also be used for the second and third CP/UP indication, and the subsequent UP/CP configuration for using the long PDCP header for the second and third CP/UP indication is the same as that for the second and third CP/UP indication, and details are not described in this document again. 5. If a CP or a UP is used cannot be recognized according to a size of a data packet, after receiving the packet, the network core notifies the base station by using uplink signaling, to perform the subsequent data transmission. That is, after the UE exchanges information with the network core, and whether a CP or a UP is specifically selected is learned, the network core delivers downlink signaling to the base station, to notify the base station of whether a CP or a UP is used.

[0147] It can be learned that in this embodiment of the present invention, a base station obtains capability information from the UE. A time of obtaining the UE capability information by the base station is before that of receiving, by the base station, radio resource control connection (RRC) complete establishment signaling, which is sent by the UE to the base station. When data transmission is performed based on a CP transmission solution, data is carried in a NAS message that is carried in the RRC connection complete establishment signaling sent by the UE to the base station. Therefore, the base station obtains the UE's capacity information before the UE sends data, so that the base station can appropriately allocate a data scheduling resource to the UE according to the UE's capacity information, and the utilization resource is increased.

[0148] Consistent with the technical solution described above, in a specific embodiment, Figure 4 is a schematic flowchart of a data scheduling method including a specific execution process of a base station. Although the data scheduling described herein is performed by the base station shown in Figure 2, it should be noted that a specific execution environment of the data scheduling method disclosed in this embodiment of the present invention is not limited to the base station.

[0149] As shown in Figure 4, the data scheduling method disclosed in this embodiment of the method of the present invention specifically includes the following steps:

[0150] S401. A base station receives downlink NAS transport signaling that is sent by a network core and carries UE capability information; or a base station receives uplink information transport signaling that is sent by UE and that carries UE capacity information, and the base station sends, to a network core, uplink NAS transport signaling that carries the information of UE capacity.

[0151] S402 The base station allocates a data scheduling resource to the UE according to the capacity information of the UE.

[0152] Specifically, this embodiment of the present invention is mainly applied to a CP data transmission background. After a connection between the UE and one side of the network (the base station or the network core) is completed, and a connection between the base station and the network core is completed, if the network core needs to deliver link data Downlink, the network core can add not only a NAS PDU but also a new information element (IE) to the downlink NAS transport signaling sent to the base station to transmit the UE capability information. In this way, the network core sends the downlink data together with the UE capability information to the base station, thereby reducing the use of dedicated signaling, for example, initial context establishment request signaling. Alternatively, after the UE is connected to a network side, when the UE has uplink data to be transmitted to the base station, the UE adds the UE's capability information to the uplink information transport signaling and a NAS PDUs that are sent to the base station, and transfer the capability information from the UE to the base station. The base station sends the UE capability information to the network core. This process can be used as a process of updating the UE's capability information.

[0153] Optionally, after the establishment of the RRC is complete, the base station may add indication information and an identifier to fetch a UE context for an initial UE context sent to the network core, and the indication information is used to instruct the network core to deliver UE capability information to the base station. After receiving the indication information, the network core can send the UE capability information to the base station by using downlink signaling subsequently sent to the base station by the network core, and a name of the signaling is not limited in the present invention.

[0154] Optionally, after the base station sends the initial UE context to the network core, the base station may ask the network core for UE capability information, by using signaling sent to the network core. UE capability information can be sent to the base station by using downlink signaling subsequently sent to the base station by the network core, and a name of the signaling is not limited in the present invention.

[0155] Optionally, the network core may add the UE capability information to downlink data sent to the base station.

[0156] Optionally, the base station does not need to instruct the network core to send the UE capability information to the base station, and the network core can directly add the UE capability information to the signaling.

[0157] It can be learned that in this embodiment of the present invention, capability information that is from the UE and that is obtained by a base station is carried in uplink transport signaling sent by the UE to the base station, or is carried in other data or signaling sent by a network core to the base station. In contrast, in the prior art, UE capability information is carried in dedicated signaling (such as initial context establishment request signaling) sent by a network core to a base station. It can be learned that in this embodiment of the present invention, the capability information of the UE is carried in data transmission. This reduces dedicated signaling, and further reduces energy consumption.

[0158] Consistent with the technical solution described above, in a specific embodiment, Figure 5 is a schematic flowchart of a connection release method including a UE-specific execution process, a base station, and a network core. Although the data scheduling described in this document is performed based on the UE, the base station, and the network core shown in Figure 1, it should be noted that a specific execution environment of the connection release method disclosed in this embodiment of the The present invention is not limited to the UE, the base station and the network core.

[0159] As shown in Figure 5, the connection release method disclosed in this method embodiment of the present invention specifically includes the following steps:

[0160] S501. A base station receives downlink NAS transport signaling that is sent by a network core and which carries a connection release indication.

[0161] S502. The base station sends, to the UE, downlink information transport signaling that carries the connection release indication.

[0162] S503. The base station releases a connection between the base station and the UE, and sends release signaling to the network core, so that the network core releases an S1 interface after receiving the release signaling.

[0163] Specifically, when uplink data transmission is completed, release auxiliary information may be added to the NAS information finally sent, to indicate whether downlink data feedback is necessary. When downlink feedback is not required, after the network core receives data, the network core triggers an S1 interface release procedure. If uplink data transmission indicates that downlink feedback information is required, an IE can be added to the downlink NAS transport signaling sent by the network core to the base station, to instruct the base station to perform release after data transmission is completed, and a connection release indication is added to a NAS PDU transmitted during data transmission. After receiving the information, the base station performs a release operation after learning that the transmission is complete. The base station sends, to the UE, the downlink information transport signaling that carries the connection release indication. The UE receives a downlink direct handover message sent by the base station, and performs release according to the indication information in the PDU of the NAS. After sending the downlink information transport signaling carrying the connection release indication to the UE, the base station sends the release signaling to the network core, so that the network core releases the S1 interface after receiving the release signal. A specific name of the release flag is not limited.

[0164] Optionally, the connection release indication sent by the network core to the base station may be added to an air interface signaling MAC header.

[0165] Optionally, in uplink data transmission, if an indication that a downlink feedback that includes release indication information is required is not provided in an uplink packet, and if there is no data transmission in an period of time, the base station or network core may trigger connection release. If the base station triggers a release procedure, the base station sends release indication information to the UE and then sends an S1 interface release confirmation (indication) to the network core. If the network core triggers a release procedure, the release procedure is the same as an existing UE context release procedure, and the details are not described in this document.

[0166] Optionally, in downlink transmission, if the network core has transmitted a data packet, a timer is enabled, and if the timer expires, a network side enters a normal connection release procedure. If uplink feedback is required, the release procedure can also be performed. If the timer does not expire, the UE has a connection packet to send, and the release procedure can also be applied in this document. That is, the UE can trigger the network side at any time to release the connection, or the network core can continue to wait for the timer to expire after completing data transmission. If the network side learns that a data packet transmitted by the UE is the last data packet, the network side can add a field to the downlink NAS transport signaling to instruct the base station to release a connection, and add the release indication information to the NAS PDU, and the base station transfers the release indication information through downlink information transmission.

[0167] It can be learned that in this embodiment of the present invention, a connection release indication sent by a network core to a base station is carried in the downlink NAS transport signaling sent by the network core to the base station. In contrast, in the prior art, a connection release indication is carried in dedicated signaling sent by a network core to a base station. It can be learned that in this embodiment of the present invention, the connection release indication is carried in the data transmission. This reduces dedicated signaling, and further reduces energy consumption.

[0168] Figure 6 is a schematic structural diagram of a base station in accordance with an embodiment of the present invention. The base station 600 includes a getting unit 601 and an allocating unit 602.

[0169] The obtaining unit 601 is configured to obtain capacity information from the user equipment (UE), where the time of obtaining the UE capacity information is prior to that of receiving, by the base station, connection complete establishment signaling radio resource control (RRC) message that is sent by the UE to the base station

[0170] The allocation unit 602 is configured to allocate a data scheduling resource to the UE according to the capacity information of the UE.

[0171] Optionally, the obtaining unit 601 is specifically configured to: receive an RRC connection request that is sent by the UE and which carries the UE's capability information; or receiving a paging message that is sent by a network core and that carries the UE's capability information; or receiving a first paging message sent by a network core; If the first paging message does not carry the UE's capability information, send to the UE a second paging message that carries indication information, where the indication information is used to instruct the UE to report the UE's capability information. HUH; and receiving an RRC connection request that is sent by the UE and that carries the capability information of the UE.

[0172] Optionally, after the obtaining unit 601 obtains the capacity information from the user equipment (UE), the base station further includes a third receiving unit and a fourth sending unit.

[0173] The third receiving unit is configured to: when the capability information is first capability information, receive an initial context establishment request that is sent by a network core and which carries the second capability information; or receiving downlink non-access stratum (NAS) transport signaling that is sent by a network core and that carries fourth capacity information; or receive the RRC connection establishment complete signaling that is sent by the UE and which carries the fifth capacity information.

[0174] The fourth sending unit is configured to: when the capability information is the first capability information, send a request to obtain capability information from the UE to the UE, and receive the third capability information that is sent by the UE in response to the request to obtain UE capability information.

[0175] Optionally, the capability information includes first capability information, and the capability information further includes second capability information, third capability information, fourth capability information, or fifth capability information.

[0176] The obtaining unit 601 is specifically configured to receive an RRC connection request that is sent by the UE and which carries the first capacity information; and receiving an initial context establishment request that is sent by a network core and that carries the second capability information.

[0177] Alternatively, the obtaining unit 601 is specifically configured to: receive an RRC connection request that is sent by the UE and which carries the first capability information; send a request to obtain UE capability information to the UE; and receiving the third capability information that is sent by the UE in response to the request to obtain capability information from the UE.

[0178] Alternatively, the obtaining unit 601 is specifically configured to: receive an RRC connection request that is sent by the UE and which carries the first capability information; and receiving downlink non-access stratum (NAS) transport signaling that is sent by a network core and that carries the fourth capacity information.

[0179] Alternatively, the obtaining unit 601 being specifically configured to obtain the capability information from the user equipment (UE) includes: the base station receives an RRC connection request that is sent by the UE and which carries the first capability information ; and receives RRC connection complete establishment signaling that is sent by the UE and which carries the fifth capacity information.

[0180] Optionally, the obtaining unit 601 includes: a first receiving unit, configured to receive an RRC connection request sent by the UE, wherein the RRC connection request carries auxiliary routing information from a first network core, and the first network core is a network core that stores context information of the UE; a first determination unit, configured to determine, in accordance with auxiliary routing information of the first network core, a network core and identification information for identifying the UE by the network core; and a first sending unit configured to send a request to obtain UE capability information to the given network core, wherein the request to obtain UE capability information carries the identification information to identify the UE by the network core, the identification information to identify the UE by the network core is used by the given network core to obtain the context information of the UE, and the context information of the UE includes the capability information of the UE, where the first receiving unit is further configured to receive the capability information that is from the UE and that is sent by the determined network core in response to the request to obtain capability information from the UE.

[0181] Optionally, after the first receiving unit receives the capability information that is from the UE and that is sent by the determined network core in response to the request to obtain capability information from the UE, the base station further includes a fifth receiving unit sending, configured to send UE capacity usage indication information to the UE, where the UE capacity usage indication information is used to indicate a UE capacity used in data scheduling, and the usage indication information of UE capacity includes indication information to indicate whether a multi-process HARQ is used in data scheduling and/or indication information to indicate whether a large transport block size (TBS) is used in data scheduling.

[0182] Optionally, the first determination unit includes: a second determination unit, configured to determine, in accordance with auxiliary routing information from the first network core, a globally unique mobility management entity (MME) identifier ( GUMMEI) of the first network core and the identification information to identify the UE by the network core; a third determination unit configured to determine, in accordance with the GUMMEI, whether network cores that can be selected by the base station include the first network core; and a first selection unit, configured to select the first network core if the network cores that can be selected by the base station include the first network core, wherein the first selection unit is further configured to: if the network cores that can be selected by the base station does not include the first network core, select any of the network cores that can be selected by the base station.

[0183] Optionally, the auxiliary routing information of the first network core includes a System Architecture Evolution (SAE) temporary mobile subscriber identifier (S-TMSI).

[0184] Optionally, the auxiliary routing information of the first network core further includes at least one of the following: a selected public land mobile network address index/public land mobile network address (PLMN ID) or a network group identifier. mobility management entity (MME) MMEGI.

[0185] Optionally, the auxiliary routing information of the first network core includes the S-TMSI and the selected public land mobile network address index/PLMN ID, and the second determination unit is specifically configured to: obtain the MMEGI of the first base station network core according to the S-TMSI and the selected public land mobile network address index/PLMN ID; and determine, in accordance with the S-TMSI, the selected public land mobile network address index/PLMN ID and the MMEGI, the globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core, and the identification information to identify the UE by the network core.

[0186] Optionally, the auxiliary routing information of the first network core includes the S-TMSI, and the second determination unit is specifically configured to: determine an MMEGI and a PLMN ID of the first network core in accordance with the S- TMSI; and determining, in accordance with the S-TMSI, the MMEGI, and the PLMN ID, the globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core and the identification information to identify the UE by network core.

[0187] Optionally, the auxiliary routing information of the first core network includes the S-TMSI and the MMEGI, and the second determination unit is specifically configured to: determine the PLMN ID of the first core network in accordance with the S -TMSI; and determine, in accordance with the S-TMSI, the MMEGI and the PLMN ID, the globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core and the identification information to identify the UE by the core network.

[0188] Optionally, the auxiliary routing information of the first network core includes the S-TMSI, the MMEGI, and the selected public land mobile network address index/PLMN ID, and the second determination unit is specifically configured to: determine , according to the S-TMSI, the MMEGI and the selected public land mobile network address index/PLMN ID, the globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core and the information identification code to identify the UE by the network core.

[0189] Optionally, the base station described in Figure 6 further includes: a second sending unit, configured to: if a network core connected to the base station is modified, send identification information to identify the UE by the network core to a modified network core, wherein the identification information for identifying the UE by the network core is used by the modified network core to ask the first network core for context information of the UE.

[0190] Optionally, the obtaining unit 601 includes: a second receiving unit, configured to receive a connection establishment request or a connection reestablishment request sent by the UE and which carries auxiliary routing information from a first base station, wherein the first base station is a base station that stores auxiliary routing information of a second network core, and the second network core is a network core that stores context information of the UE; a request unit configured to request auxiliary routing information from the second network core from the first base station in accordance with auxiliary routing information from the first base station; a fourth determination unit, configured to determine, in accordance with auxiliary routing information of the second network core, a network core and identification information for identifying the UE by the network core; and a third sending unit configured to send a request to obtain UE context information to the given network core, wherein the request to obtain UE context information carries the identification information to identify the UE by the network core, the identification information for identifying the UE by the network core is used by the given network core to obtain the context information of the UE, and the context information of the UE includes the capability information of the UE, where the second receiving unit is further configured to receive context information that is from the UE and that is sent by the given network core in response to the request to obtain UE context information.

[0191] Optionally, the capability information includes at least one of the following: one band/multi-band deployment, a single-tone/multi-tone indication ), a control plane/user plane indication, (CP/UP) indication, a UE-category, a radio capability, a subscriber profile identifier (SPID), release access stratum release, a multi-process HARQ capability, a large TBS capability, a new power type, an indication of improved mobility, a control plane reset capability, or an indication of restoration.

[0192] Optionally, the UE-category includes UE that supports or needs a multi-process HARQ and/or UE that supports or needs a large TBS.

[0193] Optionally, the new power type is included in a MAC protocol data unit (MAC CE) control element that carries the RRC connection establishment request.

[0194] Optionally, the reset includes a user plane (UP) reset indication and/or a control plane (CP) reset indication, the UP reset indication is an indication used to indicate whether the improvement of mobility is supported after reestablishment, and CP reestablishment indication is used to indicate that connection reestablishment is used for CP reestablishment, or is used to distinguish between CP indication and UP indication.

[0195] Optionally, the reestablishment indication is carried in a message sent by the UE to the base station, and the message includes an RRC connection reestablishment request.

[0196] Optionally, the reinstatement indication is further used as an establishment cause value for indication.

[0197] Optionally, before the obtaining unit 601 obtains the capacity information from the user equipment (UE), the base station further includes a processing unit.

[0198] The processing unit is configured to broadcast an indication of whether the base station supports mobility enhancement.

[0199] In this embodiment, the base station 600 may be presented in the form of a functional unit. The "unit" in this document may be an application-specific integrated circuit (ASIC), a circuit, a processor that executes one or more software programs or firmware and a memory, an integrated logic circuit, and /or other device that can provide the aforementioned functions. In a simple embodiment, those skilled in the art can imagine that the base station 600 can be in a form shown in Figure 2. The get unit 601 and the allocation unit 602 can be deployed by using the processor and memory in Figure 2 .

[0200] Figure 7 is a schematic structural diagram of a communications system in accordance with an embodiment of the present invention. As shown in Figure 7, the communications system includes UE, a network core, and a base station.

[0201] The base station is configured to obtain capability information from the UE, wherein a time of obtaining the UE capability information is prior to that of receiving, by the base station, radio resource control connection complete establishment signaling ( RRC) which is sent by the UE to the base station; and allocating a data scheduling resource to the UE according to the capacity information of the UE.

[0202] In one embodiment, the UE is configured to send, to the base station, an RRC connection request that carries the UE's capability information. A specific implementation of obtaining the user equipment (UE) capability information by the base station is: the base station is configured to receive the RRC connection request that is sent by the UE and which carries the UE capability information.

[0203] Alternatively, the network core is configured to send, to the base station, a paging message carrying UE capability information. A specific implementation of obtaining the user equipment (UE) capability information by the base station is: the base station is configured to receive the paging message that is sent by the network core and which carries the UE capability information.

[0204] Alternatively, the network core is configured to send a first paging message to the base station; the base station is configured to receive the first paging message sent by the network core; the base station is further configured to: if the first paging message does not carry the UE capability information, send, to the UE, a second paging message that carries indication information, where the indication information is used to instruct the UE reporting UE capability information; the UE is configured to receive the second paging message that is sent by the base station and which carries the indication information; the UE is further configured to send, to the base station, an RRC connection request that carries the UE's capability information. A specific implementation of obtaining the user equipment (UE) capability information by the base station is: the base station is configured to receive the RRC connection request that is sent by the UE and which carries the UE capability information.

[0205] In one embodiment, the capacity information is first capacity information, and after the base station obtains the capacity information from the user equipment (UE), the network core is configured to send, to the base station, an initial context establishment request that carries the second capability information; and the base station is further configured to receive the initial context establishment request that is sent by the network core and which carries the second capability information.

[0206] Alternatively, the base station is further configured to send a request to obtain capability information from the UE to the UE; the UE is further configured to receive the request to obtain UE capability information sent by the base station; the UE is further configured to send the third capability information to the base station in response to the request to obtain capability information from the UE; and the base station is further configured to receive the third capability information that is sent by the UE in response to the request to obtain capability information from the UE.

[0207] Alternatively, the network core is configured to send, to the base station, downlink non-access stratum (NAS) transport signaling that carries the fourth capacity information; and the base station is further configured to receive the downlink non-access stratum (NAS) transport signaling that is sent by the network core and which carries the fourth capacity information.

[0208] Alternatively, the UE is further configured to send, to the base station, RRC connection complete establishment signaling that carries the fifth capacity information; and the base station is further configured to receive the RRC connection establishment complete signaling that is sent by the UE and which carries the fifth capacity information.

[0209] In one embodiment, the capability information includes first capability information, and the capability information further includes second capability information, third capability information, fourth capability information, or fifth capability information.

[0210] The UE is configured to send, to the base station, an RRC connection request that carries the first capacity information; the network core is configured to send, to the base station, an initial context establishment request that carries the second capability information. A specific implementation of obtaining the user equipment (UE) capability information by the base station is: the base station is configured to receive the RRC connection request that is sent by the UE and which carries the first capability information; and the base station is further configured to receive the initial context establishment request that is sent by the network core and which carries the second capability information.

[0211] Alternatively, the UE is configured to send, to the base station, an RRC connection request that carries the first capacity information; the base station is configured to send a request to obtain capability information from the UE to the UE; the UE is further configured to receive the request to obtain UE capability information sent by the base station; the UE is further configured to send the third capability information to the base station in response to the request to obtain capability information from the UE. A specific implementation of obtaining the user equipment (UE) capability information by the base station is: the base station is configured to receive the RRC connection request that is sent by the UE and which carries the first capability information; and the base station is further configured to receive the third capability information that is sent by the UE in response to the request to obtain capability information from the UE.

[0212] Alternatively, the UE is configured to send, to the base station, an RRC connection request that carries the first capacity information; the network core is configured to send, to the base station, uplink non-access stratum (NAS) transport signaling that carries the fourth capacity information. A specific implementation of obtaining the user equipment (UE) capability information by the base station is: the base station is configured to receive the RRC connection request that is sent by the UE and which carries the first capability information; and the base station is further configured to receive the downlink non-access stratum (NAS) transport signaling that is sent by the network core and which carries the fourth capacity information.

[0213] Alternatively, the UE is configured to send, to the base station, an RRC connection request that carries the first capacity information; the UE is further configured to send, to the base station, RRC connection complete establishment signaling that carries the fifth capacity information. A specific implementation of obtaining user equipment (UE) capability information by the base station is: the base station is configured to receive the RRC connection request that is sent by the UE and which carries the first capability information; and the base station is further configured to receive the RRC connection complete establishment signaling that is sent by the UE and which carries the fifth capacity information.

[0214] In one embodiment, the UE is configured to send an RRC connection request to the base station, where the RRC connection request carries auxiliary routing information from a first network core, and the first network core is a core network that stores UE context information. A specific implementation of obtaining the user equipment (UE) capability information by the base station is: the base station is configured to receive the RRC connection request sent by the UE; the base station is further configured to: determine, in accordance with auxiliary routing information of the first network core, a network core and identification information for identifying the UE by the network core; send a request to obtain UE capability information to the given network core, wherein the request to obtain UE capability information carries the identification information to identify the UE by the network core, the identification information to identify the UE by the network core is used by the given network core to obtain the context information of the UE, and the context information of the UE includes the capability information of the UE; and receiving the capability information which is from the UE and which is sent by the given network core in response to the request to obtain capability information from the UE.

[0215] In one embodiment, after the base station receives the capability information that is from the UE and that is sent by the determined network core to respond to the request to obtain capability information from the UE, the base station is further configured to send information of UE capacity usage indications for the UE, wherein the UE capacity usage indications information is used to indicate a UE capacity used in scheduling data, and the UE capacity usage indications information includes information indication information to indicate whether or not multi-process HARQ is used in data scheduling, and/or indication information to indicate whether a large TBS transport block size is used in data scheduling.

[0216] In one embodiment, a specific implementation of determining, by the base station according to the auxiliary routing information of the first network core, the network core and the identification information for identifying the UE by the network core is: base station is configured to: determine, according to the auxiliary routing information of the first network core, a globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core and the identification information to identify the UE by the network core; determining, in accordance with GUMMEI, whether the network cores that can be selected by the base station include the first network core; and selecting the first network core if the network cores that can be selected by the base station include the first network core; or if the network cores that can be selected by the base station do not include the first network core, select any of the network cores that can be selected by the base station.

[0217] In one embodiment, the auxiliary routing information of the first network core includes a temporary System Architecture Evolution (SAE) S-TMSI mobile subscriber identity.

[0218] In one embodiment, the auxiliary routing information of the first network core further includes at least one of the following: a selected public land mobile network address index/public land mobile network address PLMN ID or a group identifier of mobility management entity (MME) (MMEGI).

[0219] In one embodiment, the auxiliary routing information of the first network core includes the S-TMSI and the selected public land mobile network address index/PLMN ID. A specific deployment of determining, by the base station according to the auxiliary routing information of the first network core, the globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core and the identification information for identifying the UE by the network core is: the base station is configured to obtain the MMEGI of the first network core from the base station according to the selected S-TMSI and public land mobile network address index/PLMN ID; and determine, in accordance with the S-TMSI, the selected public land mobile network address index/PLMN ID and the MMEGI, the globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core, and the identification information to identify the UE by the network core.

[0220] In one embodiment, a specific implementation of determining, by the base station in accordance with the auxiliary routing information of the first network core, the globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core. network and identification information for identifying the UE by the network core is: the base station is configured to determine an MMEGI and a PLMN ID of the first network core in accordance with the S-TMSI; and determine, in accordance with the S-TMSI, the MMEGI and the PLMN ID, the globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core and the identification information to identify the UE by the core network.

[0221] In one embodiment, the auxiliary routing information of the first network core includes the S-TMSI and the MMEGI. A specific deployment of determining, by the base station according to the auxiliary routing information of the first network core, the globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core and the identification information for identifying the UE by the network core is: the base station is configured to determine the PLMN ID of the first network core according to the S-TMSI; and determine, in accordance with the S-TMSI, the MMEGI and the PLMN ID, the globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core and the identification information to identify the UE by the core network.

[0222] In one embodiment, the auxiliary routing information of the first network core includes the S-TMSI, the MMEGI, and the selected public land mobile network address index/PLMN ID. A specific deployment of determining, by the base station according to the auxiliary routing information of the first network core, the globally unique mobility management entity (MME) identifier (GUMMEI) of the first network core and the identification information for identifying the UE by the network core is: the base station is configured to determine, according to the S-TMSI, the MMEGI, and the selected public land mobile network address index/PLMN ID, the network management entity identifier globally unique mobility (MME) (GUMMEI) of the first network core and the identification information for identifying the UE by the network core.

[0223] In one embodiment, after the base station determines, according to the routing auxiliary information of the first network core, the network core and the identification information to identify the UE by the network core, the base station is further configured to: If a network core connected to the base station is modified, sending the identification information for identifying the UE by the network core to a modified network core, where the identification information for identifying the UE by the network core is used by the modified network core to ask the first network core for UE context information.

[0224] In one embodiment, the UE is configured to send, to the base station, a connection establishment request or a connection reestablishment request that carries auxiliary routing information from a first base station, where the first base station is a base station that stores auxiliary routing information of a second network core, and the second network core is a network core that stores context information of the UE. A specific implementation of obtaining the user equipment (UE) capability information by the base station is: the base station is configured to receive the connection establishment request or the connection reestablishment request that is sent by the UE and which port the auxiliary routing information from the first base station; and the base station is further configured to: request the first base station for auxiliary routing information from the second network core in accordance with the auxiliary routing information of the first base station; determining, in accordance with the auxiliary routing information of the second network core, a network core and identification information for identifying the UE by the network core; send a request to obtain context information from the UE to the given network core, wherein the request to obtain context information from the UE carries the identification information to identify the UE by the network core, the identification information to identify the UE by the network core is used by the given network core to obtain the context information of the UE, and the context information of the UE includes the capability information of the UE; and receiving context information that is from the UE and that is sent by the given network core in response to the request to obtain context information from the UE.

[0225] In one embodiment, the capability information includes at least one of the following: single-band/multi-band deployment, a single-tone/multi-band deployment, a single-tone/multi-band tone indication), a control plane/user plane indication, (CP/UP) indication, a UE-category, a radio capability, a subscriber profile identifier (SPID) ), access stratum release information, a multi-process HARQ capability, a large TBS capability, a new power type, an indication of mobility improvement, a control plane reset capability , or an indication of restoration.

[0226] In one embodiment, the UE-category includes UE that supports or needs a multi-process HARQ and/or UE that supports or needs a large TBS.

[0227] In one embodiment, the new power type is included in a MAC protocol data unit (MAC CE) control element that carries the RRC connection establishment request.

[0228] In one embodiment, the reset includes a user plane (UP) reset indication and/or a control plane (CP) reset indication, the UP reset indication is an indication used to indicate whether the mobility improvement is supported after reestablishment, and CP reestablishment indication is used to indicate that connection reestablishment is used for CP reestablishment, or is used to distinguish between CP indication and UP indication.

[0229] In one embodiment, the reestablishment indication is carried in a message sent by the UE to the base station, and the message includes an RRC connection reestablishment request.

[0230] In one embodiment, the reinstatement indication is subsequently used as an establishment cause value for indication.

[0231] In one embodiment, prior to obtaining user equipment (UE) capability information from the base station, the base station is further configured to broadcast an indication of whether the base station supports mobility enhancement.

[0232] It can be understood that the UE, the network core, and the base station that are included in the communications system in this embodiment can be deployed specifically in accordance with the method embodiment in Figure 3. For a specific deployment process, refer to the descriptions listed in the method embodiment in Figure 3, and details are not described herein again.

[0233] An embodiment of the present invention further provides a computer storage medium. Computer storage media can store a program. When executed, the program includes some or all of the steps of any data scheduling method and a connection release method that are registered in the embodiments of the previous method.

[0234] It should be noted that, for brief description, the modalities of the previous method are expressed as a series of actions. However, persons skilled in the art should note that the present invention is not limited to the sequence of action described, and because, according to the present invention, some steps can be performed in other sequences or performed simultaneously. Furthermore, persons skilled in the art should also note that all embodiments described in the specification are embodiments, and related actions and modules are not necessarily mandatory for the present invention.

[0235] In the aforementioned modalities, the description of each modality has its respective focuses. For a part that is not described in detail in one embodiment, refer to related descriptions in other embodiments.

[0236] In the various embodiments provided in this application, it is to be understood that the disclosed apparatus may be implanted in other ways. For example, the described apparatus embodiment is merely an example. For example, unit division is merely logical function division and may be another division in an effective deployment. For example, multiple units or components may be combined or integrated into another system, or some functionality may be ignored or not performed. Furthermore, the mutual couplings or direct couplings or communication connections shown or discussed may be implemented through the use of some interfaces. Indirect couplings or communication connections between devices or units can be implemented in electronic or other forms.

[0237] Units described as separate parts may or may not be physically separated, and parts shown as units may or may not be physical units, may be located in one position, or may be distributed across multiple network units. Some or all of the units may be selected according to the actual requirements to achieve the solution objectives of the modalities.

[0238] Furthermore, the functional units in embodiments of the present invention may be integrated into a processing unit, or each of the units may physically exist alone, or two or more units are integrated into one unit. The integrated unit may be deployed in a hardware form, or it may be deployed in the form of a software functional unit.

[0239] When the integrated unit is implemented in the form of a software functional unit and sold or used as a stand-alone product, the integrated unit may be stored in computer-readable memory. Based on this understanding, the technical solutions of the present invention essentially, or the part that contributes to the prior art, or all or some of the technical solutions can be implemented in the form of a software product. The computer software product is stored in a memory and includes various instructions for instructing a computer device (which may be a personal computer, a server, a network device, or the like) to perform all or some of the steps of the described methods in the embodiments of the present invention. The aforementioned memory includes: any medium that can store program code, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a removable hard disk , a magnetic disk, or an optical disk.

[0240] Persons of ordinary skill in the art can understand that all or some of the steps of the methods in the embodiments can be implemented by a program that instructs the relevant hardware. The program can be stored in computer-readable memory. The memory may include flash memory, read-only memory, ROM for short, random access memory, random access memory, magnetic disk, optical disk, and the like.

[0241] Embodiments of the present invention are described in detail above. The principle and implementation of the present invention are described in this document through specific examples. The description of embodiments is merely provided to help understand the method and main ideas of the present invention. Furthermore, persons of ordinary skill in the art can make modifications in terms of specific implementations and scopes of application in accordance with the ideas of the present invention. In conclusion, the content of the specification should not be understood as a limit to the present invention.

Claims (16)

1. Data scheduling method for data transmission based on a control plane transmission solution, CP, CHARACTERIZED by the fact that it comprises: obtaining (S301), by a base station, user equipment capacity information ( UE), allocate (S302), by the base station, a data scheduling resource to the UE according to the capacity information of the UE; sending, by the base station, the data scheduling resource allocated by the base station to the UE; and receiving, by the base station, a complete RRC connection establishment signaling that is sent by the UE to the base station, wherein a moment of the obtaining step is prior to that of the receiving step; wherein according to the data scheduling resource allocated by the base station to the UE, data that needs to be reported to a network by the UE is carried in a no-access stratum message, NAS, which is carried in the full signaling of establishment of RRC connection sent by the UE to the base station. 2. Method, according to claim 1, CHARACTERIZED by the fact that obtaining, by a base station, UE capacity information comprises: receiving, by the base station, an RRC connection request that is sent by the UE and that carries the UE capability information. 3. Method, according to claim 1, CHARACTERIZED by the fact that obtaining, by a base station, UE capacity information comprises: receiving, by the base station, an RRC connection request signaling from the UE, wherein the RRC connection request includes a terminal device identifier; determining, by the base station, a network core device according to the identifier; sending, by the base station, UE obtaining request capability information to the network core apparatus, wherein the UE obtaining request capability information carries the identifier; receiving, by the base station, UE capability information from the network core apparatus. 4. Method according to any one of claims 1 to 3, CHARACTERIZED by the fact that after obtaining, by a base station, user equipment (UE) capacity information, the method further comprises: sending, by base station, UE capacity usage indication information for the UE, wherein the UE capacity usage indication information is used to indicate a UE capacity used when data scheduling is performed for the UE, and the information UE capacity usage indication information comprises indication information to indicate whether a multi-process HARQ is used in data scheduling, and/or indication information to indicate whether a large transport block size, TBS, is used in scheduling. of data. 5. Method, according to any one of claims 1 to 4, CHARACTERIZED by the fact that the capacity information comprises at least one of the following: single band/multi-band deployment, a single-tone/multi-tone indication, a control plane/user plane (CP/UP) indication, a UE category, a radio capability (radio capability), a subscriber profile identifier (SPID), access stratum release information, a multi-process HARQ capability, a large TBS capability, a new power type, an indication of mobility improvement, a control plane reestablishment capability, or an indication of reestablishment. 6. Method, according to claim 5, FEATURED by the fact that the category of UE comprises UE that supports or requires a multi-process HARQ and/or UE that supports or requires a large TBS. 7. Base station, CHARACTERIZED by the fact that it comprises means for carrying out the steps of the method as defined in any one of claims 1 to 6. 8. Computer-readable storage media, CHARACTERIZED by the fact that it comprises instructions that when executed by a base station, cause the base station to perform the steps of the method as defined in any one of claims 1 to 6. 9. Method of data scheduling performed by a terminal device, CHARACTERIZED in that it comprises: sending, a radio resource control connection request comprising an identifier from the terminal device to a base station, wherein the identifier indicates a network core apparatus for obtaining first capability information from the terminal device; receiving an allocation of a data scheduling resource that satisfies the first capacity information from the base station; and sending a complete radio resource control connection configuration message to the base station in accordance with the data scheduling resource, wherein the complete radio resource control connection configuration message comprises a radio resource control stratum message. non-access comprising data from the terminal device. 10. Method, according to claim 9, CHARACTERIZED by the fact that the first capacity information comprises at least one of the following: single tone indication; multiple tone indication; single carrier indication; indication of multiple carriers; or user equipment (UE) priority. 11. Method, according to claim 9, CHARACT ERIZED by the fact that the identifier is temporary mobile subscriber identity. 12. The method of claim 9, characterized by the fact that the complete radio resource control connection configuration message further comprises second terminal device capability information; wherein the second capacity information comprises at least one of the following: user plan indication; indication of control plan; radio capability; or multi-process hybrid auto-retry request capability. 13. Device, CHARACTERIZED by the fact that it comprises at least one processor; and a computer-readable storage medium that stores a set of instructions for execution by at least one processor, wherein the instruction set, when executed by the at least one processor, instructs the at least one processor to: send a connection request a radio resource control device comprising an identifier from a terminal device to a base station, wherein the identifier indicates a network core apparatus to obtain first capability information from the terminal device; receiving an allocation of a data scheduling resource that satisfies the first capacity information from the base station; and sending a complete radio resource control connection configuration message to the base station in accordance with the data scheduling resource, wherein the complete radio resource control connection configuration message comprises a radio resource control stratum message. non-access comprising data from the terminal device. 14. Apparatus according to claim 13, CHARACTERIZED by the fact that the first capacity information comprises at least one of the following: single tone indication; multiple tone indication; single carrier indication; indication of multiple carriers; or user equipment (UE) priority. 15. Apparatus, according to claim 13, CHARACT ERIZED by the fact that the identifier is temporary mobile subscriber identity. 16. The apparatus of claim 13, CHARACTERIZED by the fact that the complete radio resource control connection configuration message further comprises second terminal device capability information; wherein the second capacity information comprises at least one of the following: user plan indication; indication of control plan; radio capability; or multi-process hybrid auto-retry request capability.