CN112995958B

CN112995958B - Data scheduling method, base station and system

Info

Publication number: CN112995958B
Application number: CN202110142439.8A
Authority: CN
Inventors: 李晨琬; 于映辉; 黄正磊; 王燕; 单宝堃
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2016-01-07
Filing date: 2016-11-04
Publication date: 2022-10-04
Anticipated expiration: 2036-11-04
Also published as: CN107534987A; CN108551667B; CN108260121B; CN107231623A; CN107534987B; CN107231623B; CN113613215A; CN108260121A; CN112995958A; CN108551667A

Abstract

The invention discloses a data scheduling method, which comprises the following steps: a base station acquires the capability information of User Equipment (UE), wherein the time of acquiring the capability information of the UE is before the base station receives a Radio Resource Control (RRC) connection establishment completion signaling sent by the UE to the base station; and the base station allocates data scheduling resources for the UE according to the capability information of the UE. The embodiment of the invention can improve the utilization rate of resources.

Description

Data scheduling method, base station and system

Technical Field

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

Background

With the rapid development Of wireless communication, people have not satisfied communication limited to people, and Internet Of Things (IOT) technology has come into operation. Machine-to-Machine (M2M) communication is a short term for information and data transmission between machines via wireless networks, and is an important direction for IOT development. Most of the M2M devices are relatively small and battery-powered systems, such as an intelligent meter reading system, and the usage conditions of water, electric gas and the like need to be periodically monitored and reported.

The intelligent copy-table type service is mainly a small data packet reporting service, and has a small data volume, and for such services, there are two transmission schemes, one is a Control Plane (CP) based transmission scheme, and the other is a User Plane (UP) based transmission scheme. In a conventional method for acquiring capability information of a User Equipment (UE), after a base station establishes a connection with a Mobility Management Entity (MME), if the MME stores capability information of the UE, the MME sends the capability information to the base station, or if the MME does not store capability information of the UE, the base station requests the UE and sends the capability information to the MME. Thus, the base station may not be able to reasonably allocate data scheduling resources to the UE according to the capability information of the UE, thereby reducing the utilization rate of the resources.

Disclosure of Invention

The embodiment of the invention provides a data scheduling method, a base station and a system, aiming at improving the utilization rate of resources.

A first aspect of an embodiment of the present invention provides a data scheduling method, including:

a base station acquires the capability information of User Equipment (UE), wherein the time of acquiring the capability information of the UE is before the base station receives a Radio Resource Control (RRC) connection establishment completion signaling sent by the UE to the base station;

and the base station allocates data scheduling resources to the UE according to the capability information of the UE.

With reference to the first aspect of the present invention, in a first possible implementation manner of the first aspect, the acquiring, by the base station, capability information of the UE includes:

a base station receives an RRC connection request which is sent by UE and carries the capability information of the UE;

alternatively, the first and second liquid crystal display panels may be,

a base station receives a paging message which is sent by a core network and carries the capability information of the UE;

alternatively, the first and second electrodes may be,

a base station receives a first paging message sent by a core network; if the first paging message does not carry the capability information of the UE, the base station sends a second paging message carrying indication information to the UE, wherein the indication information is used for indicating the UE to report the capability information of the UE; and the base station receives an RRC connection request which is sent by the UE and carries the capability information of the UE.

With reference to the first aspect of the present invention, in a second possible implementation manner of the first aspect, after the capability information is first capability information and the base station acquires capability information of a user equipment UE, the method further includes:

the base station receives an initial context establishment request which is sent by a core network and carries the second capability information;

or the base station sends a UE capability information acquisition request to the UE; the base station receives the third capability information sent by the UE in response to the UE capability information acquisition request;

or, the base station receives a downlink non-access stratum (NAS) transmission signaling which is sent by a core network and carries the fourth capability information;

or, the base station receives an RRC connection setup complete signaling carrying the fifth capability information sent by the UE.

With reference to the first aspect of the present invention, in a third possible implementation manner of the first aspect, the acquiring, by the base station, capability information of the UE includes:

a base station receives an RRC connection request sent by UE, wherein the RRC connection request carries routing auxiliary information of a first core network, and the first core network is a core network in which the UE context information is stored;

the base station determines the core network and the identification information of the core network for identifying the UE according to the routing auxiliary information of the first core network;

the base station sends a capability information acquisition request of the UE to a determined core network, wherein the capability information acquisition request of the UE carries identification information of the core network for identifying the UE, the identification information of the core network for identifying the UE is used for the determined core network to acquire the UE context information, and the UE context information comprises the capability information of the UE;

and the base station receives the capability information of the UE, which is sent by the determined core network in response to the capability information acquisition request of the UE.

With reference to the third possible implementation manner of the first aspect of the present invention, in a fourth possible implementation manner of the first aspect, after the base station acquires the capability information of the UE, the method further includes:

and the base station sends indication information used by the UE capability to the UE, wherein the indication information used by the UE capability is used for indicating the UE capability used by data scheduling, and the indication information used by the UE capability comprises indication information indicating whether the data scheduling uses multi-process HARQ and/or indication information indicating whether the data scheduling uses a large-capacity transport block TBS.

With reference to the third possible implementation manner of the first aspect of the present invention, in a fifth possible implementation manner of the first aspect, the determining, by the base station, identification information of a core network and a UE identified by the core network according to the routing assistance information of the first core network includes:

the base station determines a globally unique Mobile Management Entity (MME) identifier GUMMEI of the first core network and identifier information of core network identification (UE) according to the routing auxiliary information of the first core network;

the base station determines whether the core network selectable by the base station comprises the first core network or not according to the GUMMEI;

if the core network selectable by the base station includes the first core network, the base station selects the first core network;

if the core network selectable by the base station does not include the first core network, the base station selects any one of the core networks selectable by the base station.

With reference to the fifth possible implementation manner of the first aspect of the present invention, in a sixth possible implementation manner of the first aspect, the first core network routing assistance information includes a system architecture evolution SAE temporary mobile subscriber identity S-TMSI.

With reference to the sixth possible implementation manner of the first aspect, in a seventh possible implementation manner of the first aspect, the first core network routing assistance information further includes at least one of the following: selected public land mobile network address index/public land mobile network address PLMN ID or mobility management entity MME group identity MMEGI.

With reference to the seventh possible implementation manner of the first aspect, in an eighth possible implementation manner of the first aspect, the routing assistance information of the first core network includes S-TMSI and a selected public land mobile network address index/PLMN ID, and the base station determines, according to the routing assistance information of the first core network, identification information of a globally unique mobility management entity MME identity GUMMEI and a core network identity UE of the first core network, and the base station includes:

the base station acquires the MMEGI of the first core network from the base station according to the S-TMSI and the selected public land mobile network address index/the PLMN ID;

and the base station determines a globally unique Mobile Management Entity (MME) identifier GUMMEI of the first core network and identifier information of core network identification (UE) according to the S-TMSI, the selected public land mobile network address index/the PLMN ID and the MMEGI.

With reference to the sixth possible implementation manner of the first aspect, in a ninth possible implementation manner of the first aspect, the determining, by the base station, the globally unique MME identity GUMMEI and the identity information of the core network identification UE of the first core network according to the routing assistance information of the first core network includes:

the base station determines the MMEGI and the PLMN ID of the first core network according to the S-TMSI;

and the base station determines a globally unique Mobile Management Entity (MME) identifier GUMMEI of the first core network and identifier information of core network identification (UE) according to the S-TMSI, the MMEGI and the PLMN ID.

With reference to the seventh possible implementation manner of the first aspect of the present invention, in a tenth possible implementation manner of the first aspect, the routing assistance information of the first core network includes S-TMSI and MMEGI, and the determining, by the base station, the globally unique mobility management entity MME identity GUMMEI and the identity information of the core network identity UE of the first core network according to the routing assistance information of the first core network includes:

the base station determines the PLMN ID of the first core network according to the S-TMSI;

and the base station determines a globally unique Mobile Management Entity (MME) identifier (GUMMEI) of the first core network and identifier information of core network identification (UE) according to the S-TMSI, the MMEGI and the PLMN ID.

With reference to the seventh possible implementation manner of the first aspect of the present invention, in an eleventh possible implementation manner of the first aspect, the routing assistance information of the first core network includes S-TMSI, MMEGI, and a selected public land mobile network address index/PLMN ID, and the base station determines, according to the routing assistance information of the first core network, identification information of a globally unique mobility management entity MME identity GUMMEI and a core network identity UE of the first core network, including:

and the base station determines a globally unique Mobile Management Entity (MME) identifier (GUMMEI) of the first core network and identifier information of core network identification (UE) according to the S-TMSI, the MMEGI and the selected public land mobile network address index/the PLMN ID.

With reference to any one of the third to eleventh possible implementation manners of the first aspect of the present invention, in a twelfth possible implementation manner of the first aspect, after the determining, by the base station, the identification information of the core network and the UE identified by the core network according to the routing assistance information of the first core network, the method further includes:

if the core network connected with the base station changes, the base station sends identification information of the core network identification UE to the changed core network, and the identification information of the core network identification UE is used for the changed core network to ask the first core network for the context information of the UE.

With reference to the first aspect of the present invention, in a thirteenth possible implementation manner of the first aspect, the obtaining, by the base station, capability information of the UE includes:

a base station receives a connection establishment request or a link reestablishment request which is sent by UE and carries routing auxiliary information of a first base station, wherein the first base station is a base station which stores the routing auxiliary information of a second core network, and the second core network is a core network which stores the context information of the UE;

the base station requests the routing auxiliary information of a second core network to the first base station according to the routing auxiliary information of the first base station;

the base station determines the core network and the identification information of the core network for identifying the UE according to the routing auxiliary information of the second core network;

the base station sends the UE context information acquisition request to a determined core network, the capability information of the UE acquires identification information carrying UE identified by the core network, the identification information of the UE identified by the core network is used for the determined core network to acquire the UE context information, and the UE context information comprises the capability information of the UE;

and the base station receives the UE context information sent by the core network responding to the UE context information acquisition request after the determination.

With reference to the first aspect and any one of the first to the thirteenth possible implementation manners of the first aspect, in a fourteenth possible implementation manner of the first aspect, the capability information includes at least one of the following: the method comprises the steps of deploying One band/multi-band deployment, indicating Single-tone/multi-tone by Single carrier/multi-carrier, indicating control plane/user plane (CP/UP indication), indicating UE type (UE-Category), radio capability, signing attribute identifier (SPID), access layer-version information (Access Stratum) Release, multi-process Hybrid Automatic Repeat (HARQ) capability, large TBS capability, new power type, mobility enhancement indication, control plane reestablishment capability and reestablishment indication.

With reference to the fourteenth possible implementation manner of the first aspect of the present invention, in a fifteenth possible implementation manner of the first aspect, the UE Category UE-Category includes a UE that supports or needs multi-process HARQ and/or a UE that supports or needs a large TBS.

With reference to the fourteenth or fifteenth possible implementation manners of the first aspect, in a sixteenth possible implementation manner of the first aspect, the new power type is included in a control element (MAC CE) of a MAC protocol data unit carrying the RRC connection establishment request.

With reference to any one of the fourteenth to the sixteenth possible implementation manners of the first aspect of the present invention, in a seventeenth possible implementation manner of the first aspect, the re-establishment includes a re-establishment indication of a User Plane (UP) and/or a re-establishment indication of a Control Plane (CP), the re-establishment indication of the UP is used to distinguish whether mobility enhancement is supported after re-establishment, and the re-establishment indication of the CP is used to indicate whether a re-establishment connection is used for re-establishment of the CP or to distinguish whether the CP indication is used for UP.

With reference to any one of the fourteenth to the seventeenth possible implementation manners of the first aspect of the present invention, in an eighteenth possible implementation manner of the first aspect, 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.

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

With reference to any one of the fourteenth to nineteenth possible implementation manners of the first aspect of the present invention, in a twentieth possible implementation manner of the first aspect, before the obtaining, by the base station, the capability information of the UE, the method further includes:

the base station broadcasts an indication of whether the base station supports mobility enhancement.

A second aspect of the embodiments of the present invention provides a method for scheduling data, including:

a base station receives a downlink NAS transmission signaling which is sent by a core network and carries the capability information of UE;

or, the base station receives an uplink information transmission signaling which is sent by the UE and carries the capability information of the UE; the base station sends an uplink NAS transmission signaling carrying the UE capability information to a core network;

A third aspect of an embodiment of the present invention provides a connection release method, including:

a base station receives a downlink NAS transmission signaling which is sent by a core network and carries a connection release indication;

the base station sends a downlink information transmission signaling carrying the connection release indication to the UE;

and the base station releases the connection between the base station and the UE and sends a release signaling to the core network, so that the core network releases the S1 interface after receiving the release signaling.

A fourth aspect of the embodiments of the present invention provides a base station, where the base station has a function of implementing a base station behavior in the above method design. The functions may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above. The modules may be software and/or hardware. The base station comprises an obtaining unit and an allocating unit, and is configured to perform relevant steps of the method for scheduling data provided by the first aspect.

A fifth aspect of the embodiments of the present invention provides a base station, where the base station includes a transceiver and a processor, and the processor is configured to support the base station to perform corresponding functions in the foregoing method. The transceiver is used to support communication between the base station and the mobile network server. The base station may also include a memory, coupled to the processor, that retains program instructions and data necessary for the base station. The base station may also include a communication interface for the base station to communicate with other devices or communication networks.

A sixth aspect of the embodiments of the present invention provides a computer storage medium for storing computer software instructions for the base station, which includes a program designed to execute the above aspects.

A seventh aspect of the embodiments of the present invention provides a communication system, including a base station, a UE and a core network, where: the base station is configured to acquire capability information of the UE, where a time of acquiring the capability information of the UE is before the base station receives a radio resource control RRC connection setup complete signaling sent by the UE to the base station; and allocating data scheduling resources to the UE according to the capability information of the UE.

With reference to the seventh aspect, in a first possible implementation manner of the seventh aspect, the UE is configured to send, to the base station, an RRC connection request carrying capability information of the UE; the specific implementation manner of the base station for acquiring the capability information of the User Equipment (UE) is as follows: the base station is configured to receive an RRC connection request that is sent by a UE and carries capability information of the UE;

alternatively, the first and second electrodes may be,

the core network is configured to send a paging message carrying capability information of the UE to the base station; the specific implementation manner of the base station for acquiring the capability information of the User Equipment (UE) is as follows: the base station is configured to receive a paging message that is sent by a core network and carries the capability information of the UE;

alternatively, the first and second electrodes may be,

the core network is configured to send a first paging message to the base station; the base station is used for receiving a first paging message sent by a core network; the base station is further configured to send, to the UE, a second paging message carrying indication information if the first paging message does not carry the capability information of the UE, where the indication information is used to indicate the UE to report the capability information of the UE; the UE is configured to receive a second paging message that carries indication information and is sent by the base station; the UE is further configured to send an RRC connection request carrying capability information of the UE to the base station; the specific implementation manner of acquiring the capability information of the user equipment UE by the base station is as follows: the base station is configured to receive an RRC connection request that is sent by a UE and carries capability information of the UE.

With reference to the seventh aspect of the present invention, in a second possible implementation manner of the seventh aspect, after the base station acquires the capability information of the UE,

the core network is configured to send an initial context establishment request carrying the second capability information to the base station; the base station is further configured to receive an initial context establishment request carrying the second capability information and sent by a core network;

or, the base station is further configured to send a UE capability information acquisition request to the UE; the UE is further configured to receive a UE capability information acquisition request sent by the base station; the UE is further configured to send the third capability information to the base station in response to the UE capability information obtaining request; the base station is further configured to receive the third capability information sent by the UE in response to the UE capability information acquisition request;

or, the core network is configured to send, to the base station, a downlink non-access stratum NAS transport signaling that carries the fourth capability information; the base station is further configured to receive a downlink non-access stratum NAS transport signaling carrying the fourth capability information and sent by a core network;

or, the UE is further configured to send an RRC connection setup complete signaling carrying the fifth capability information to the base station; the base station is further configured to receive an RRC connection setup complete signaling that is sent by the UE and carries the fifth capability information.

With reference to the seventh aspect, in a third possible implementation manner of the seventh aspect, the UE is configured to send an RRC connection request to the base station, where the RRC connection request carries routing assistance information of a first core network, and the first core network is a core network in which the UE context information is stored; the specific implementation manner of the base station for acquiring the capability information of the User Equipment (UE) is as follows:

the base station is configured to receive an RRC connection request sent by the UE; the base station is further configured to determine, according to the routing assistance information of the first core network, identification information of the core network and the UE identified by the core network; sending a capability information acquisition request of the UE to a determined core network, wherein the capability information acquisition request of the UE carries identification information of the core network for identifying the UE, the identification information of the core network for identifying the UE is used for the determined core network to acquire the UE context information, and the UE context information comprises the capability information of the UE; and receiving the capability information of the UE, which is sent by the determined core network in response to the capability information acquisition request of the UE.

With reference to the third possible implementation manner of the seventh aspect of the present invention, in a fourth possible implementation manner of the seventh aspect, after the base station receives the capability information of the UE, which is sent by the determined core network in response to the capability information acquisition request of the UE,

the base station is further configured to send UE capability use indication information to the UE, where the UE capability use indication information is used to indicate UE capability used for data scheduling, and the UE capability use indication information includes indication information indicating whether data scheduling uses multi-process HARQ and/or indication information indicating whether data scheduling uses a large-capacity transport block TBS.

With reference to the third possible implementation manner of the seventh aspect of the present invention, in a fifth possible implementation manner of the seventh aspect, a specific implementation manner of determining, by the base station, the core network and the identifier information of the UE identified by the core network according to the routing assistance information of the first core network is:

the base station is configured to determine, according to the routing assistance information of the first core network, a globally unique MME identity GUMMEI of the first core network and identity information of a core network identity UE; determining whether the core network selectable by the base station includes the first core network according to the GUMMEI; if the core network selectable by the base station comprises the first core network, selecting the first core network; and if the core network selectable by the base station does not comprise the first core network, selecting any one of the core networks selectable by the base station.

With reference to the fifth possible implementation manner of the seventh aspect, in a sixth possible implementation manner of the seventh aspect, the first core network routing assistance information includes a system architecture evolution SAE temporary mobile subscriber identity S-TMSI.

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

With reference to the seventh possible implementation manner of the seventh aspect of the present invention, in an eighth possible implementation manner of the seventh aspect, the routing assistance information of the first core network includes S-TMSI and a selected public land mobile network address index/PLMN ID, and a specific implementation manner of the base station determining, according to the routing assistance information of the first core network, the globally unique mobility management entity MME identity GUMMEI of the first core network and the identity information of the core network identity UE is as follows:

the base station is configured to obtain the MMEGI of the first core network from the base station according to the S-TMSI and the selected PLMN ID; and determining a globally unique MME (mobility management entity) identifier GUMMEI of the first core network and identifier information of core network identification UE (user equipment) according to the S-TMSI, the selected PLMN ID/the selected PLMN address index and the MMEGI.

With reference to the sixth possible implementation manner of the seventh aspect, in a ninth possible implementation manner of the seventh aspect, a specific implementation manner of determining, by the base station, the globally unique mobility management entity MME identifier GUMMEI and the identifier information of the core network identity UE of the first core network according to the routing assistance information of the first core network is:

the base station is configured to determine an MMEGI and a PLMN ID of the first core network according to the S-TMSI; and determining a globally unique Mobile Management Entity (MME) identifier (GUMMEI) of the first core network and identifier information of core network identification (UE) according to the S-TMSI, the MMEGI and the PLMN ID.

With reference to the seventh possible implementation manner of the seventh aspect of the present invention, in a tenth possible implementation manner of the seventh aspect, the routing assistance information of the first core network includes S-TMSI and MMEGI, and a specific implementation manner of the base station determining, according to the routing assistance information of the first core network, the globally unique mobility management entity MME identifier GUMMEI and the identifier information of the core network identifier UE, by using the base station, is:

the base station is configured to determine a PLMN ID of the first core network according to the S-TMSI; and determining a globally unique Mobile Management Entity (MME) identifier GUMMEI of the first core network and identifier information of core network identification (UE) according to the S-TMSI, the MMEGI and the PLMN ID.

With reference to the seventh possible implementation manner of the seventh aspect of the present invention, in an eleventh possible implementation manner of the seventh aspect, the routing assistance information of the first core network includes S-TMSI, MMEGI, and selected public land mobile network address index/PLMN ID, and a specific implementation manner of the base station determining, according to the routing assistance information of the first core network, the globally unique mobility management entity MME identity GUMMEI of the first core network and the identity information of the core network identity UE is as follows:

the base station is configured to determine, according to the S-TMSI, the MMEGI, and the selected PLMN ID, a globally unique MME identity GUMMEI of the first core network and identity information of a core network identity UE.

With reference to any one of the third to eleventh possible implementation manners of the seventh aspect of the present invention, in a twelfth possible implementation manner of the seventh aspect, after the base station determines, according to the routing assistance information of the first core network, identification information of a core network and a core network identity UE,

the base station is further configured to: and if the core network connected with the base station changes, sending identification information of the core network identification UE to the changed core network, wherein the identification information of the core network identification UE is used for the changed core network to request the context information of the UE from the first core network.

With reference to the seventh aspect, in a thirteenth possible implementation manner of the seventh aspect, the UE is configured to send a connection establishment request or a link reestablishment request that carries routing auxiliary information of a first base station to the base station, where the first base station is a base station that stores routing auxiliary information of a second core network, and the second core network is a core network that stores context information of the UE; the specific implementation manner of acquiring the capability information of the user equipment UE by the base station is as follows:

the base station is configured to receive a connection establishment request or a link reestablishment request that is sent by the UE and carries the routing assistance information of the first base station;

the base station is further configured to request, to the first base station, routing assistance information of a second core network according to the routing assistance information of the first base station; determining the core network and the identification information of the core network for identifying the UE according to the routing auxiliary information of the second core network; sending the UE context information acquisition request to a determined core network, wherein the capability information of the UE acquires identification information carrying UE identified by the core network, the identification information of the UE identified by the core network is used for the determined core network to acquire the UE context information, and the UE context information comprises the capability information of the UE; and receiving the UE context information sent by the determined core network responding to the UE context information acquisition request.

With reference to the seventh aspect, any one of the first to thirteenth possible implementation manners of the seventh aspect, and the fourteenth possible implementation manner of the seventh aspect, the capability information includes at least one of: the method comprises the steps of deploying One band/multi-band deployment, indicating Single-tone/multi-tone by Single carrier/multi-carrier, indicating control plane/user plane (CP/UP indication), indicating UE type (UE-Category), radio capability, signing attribute identifier (SPID), access layer-version information (Access Stratum) Release, multi-process Hybrid Automatic Repeat (HARQ) capability, large TBS capability, new power type, mobility enhancement indication, control plane reestablishment capability and reestablishment indication.

With reference to the fourteenth possible implementation manner of the seventh aspect, in a fifteenth possible implementation manner of the seventh aspect, the UE Category UE-Category includes a UE that supports or needs multi-process HARQ and/or a UE that supports or needs a large TBS.

With reference to the fourteenth or fifteenth possible implementation manners of the seventh aspect, in a sixteenth possible implementation manner of the seventh aspect, the new power type is included in a control element (MAC CE) of a MAC protocol data unit carrying the RRC connection setup request.

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 re-establishment includes a re-establishment indication of a User Plane (UP) and/or a re-establishment indication of a Control Plane (CP), where the re-establishment indication of the UP is used to distinguish whether mobility enhancement is supported after re-establishment, and the re-establishment indication of the CP is used to indicate whether a re-established connection is used for re-establishment of the CP, or to distinguish whether the CP is used for indication of UP or indication of re-establishment.

With reference to the fourteenth to seventeenth possible implementation manners of the seventh aspect of the present invention, in an eighteenth possible implementation manner of the seventh aspect, 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.

With reference to the eighteenth possible implementation manner of the seventh aspect of the present invention, in a nineteenth possible implementation manner of the seventh aspect, the reestablishment indication is further used as an establishment cause value for indicating.

With reference to the thirteenth to nineteenth possible implementation manners of the seventh aspect of the present invention, in a twentieth possible implementation manner of the seventh aspect, before the base station acquires the capability information of the user equipment UE,

the base station is further configured to broadcast an indication of whether the base station supports mobility enhancement.

It can be seen that, in the embodiment of the present invention, the base station acquires the capability information of the UE, where the time when the base station acquires the capability information of the UE is before the base station receives a RRC connection setup complete signaling sent by the UE to the base station, and since data is carried in an NAS message carried in the RRC connection setup complete signaling sent by the UE to the base station when data transmission is performed based on the CP transmission scheme, the base station acquires the capability information of the UE before the UE data is sent, so that the base station can reasonably allocate data scheduling resources to the UE according to the capability information of the UE, thereby improving the utilization rate of resources.

These and other aspects of the invention will be apparent from and elucidated with reference to the embodiments described hereinafter.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.

Fig. 1 is a network architecture according to an embodiment of the present invention;

fig. 2 is a schematic structural diagram of a base station according to an embodiment of the present invention;

fig. 3 is a schematic flowchart of a data scheduling method according to an embodiment of the present invention;

fig. 3.A is a schematic diagram of an MAC CE for reporting data volume and power headroom according to an embodiment of the present invention;

fig. 3.1 is a schematic flow chart of another data scheduling method disclosed in the embodiment of the present invention;

fig. 3.2 is a schematic flowchart of another data scheduling method according to the embodiment of the present invention;

fig. 3.3 is a schematic flow chart of another data scheduling method disclosed in the embodiment of the present invention;

FIG. 3.3b is a schematic diagram illustrating the GUTI component in a data scheduling method of FIG. 3.3;

fig. 3.4 is a schematic flow chart of another data scheduling method disclosed in the embodiment of the present invention;

fig. 4 is a schematic flowchart of another data scheduling method according to an embodiment of the present invention;

fig. 5 is a schematic flowchart of a connection releasing method according to an embodiment of the present invention;

fig. 6 is a schematic structural diagram of another base station disclosed in the embodiment of the present invention;

fig. 7 is a schematic structural diagram of a communication system according to an embodiment of the present invention.

Detailed Description

In order to make those skilled in the art better understand the technical solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The following are detailed descriptions.

The terms "first," "second," "third," and "fourth," etc. in the description and claims of the invention and in the accompanying drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.

Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the invention. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein may be combined with other embodiments.

In order to better understand a data scheduling method, a base station and a system disclosed in the embodiments of the present invention, a network architecture to which the embodiments of the present invention are applicable is described below. Referring to fig. 1, fig. 1 is a schematic diagram of a network architecture according to an embodiment of the present invention. In the network architecture shown in fig. 1, a base station, a UE, and a core network may be included. In the network architecture shown in fig. 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 an intelligent wearable Device (e.g., an intelligent watch and an intelligent bracelet), which is not limited in the embodiment of the present invention. The base station may be a base station in an LTE or LTE evolved System, or may also be a base station in a Universal Mobile Telecommunications System (UMTS), and the embodiment of the present invention is not limited thereto. The core network may be an MME. The data scheduling method provided by the invention is applied to communication of various systems, such as M2M, IOT and the like.

Fig. 2 is a schematic diagram of a base station according to an embodiment of the present invention. The base station 200 comprises at least one processor 201, a communication bus 202, a memory 203, at least one communication interface 204, a transceiver 205.

The processor 201 may be a general purpose Central Processing Unit (CPU), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of programs in accordance with the inventive arrangements.

The communication bus 202 may include a path that conveys information between the aforementioned components. The communication interface 204 may be any device, such as a transceiver, for communicating with other devices or communication Networks, such as ethernet, radio Access Network (RAN), wireless Local Area Network (WLAN), etc.

The Memory 203 may be a Read-Only Memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that can store information and instructions, an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical Disc storage, optical Disc storage (including Compact Disc, laser Disc, optical Disc, digital versatile Disc, blu-ray Disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to these. The memory may be self-contained and coupled to the processor via a bus. The memory may also be integrated with the processor.

The memory 203 is used for storing application program codes for executing the scheme of the invention, and the processor 501 controls the execution. The processor 201 is configured to execute application program code stored in the memory 203.

The code stored in the memory 203 of the base station shown in fig. 2 may perform the method for scheduling data provided by the present invention, such as obtaining the capability information of the UE, and then allocating data scheduling resources to the UE according to the capability information of the UE.

In one implementation, the base station 200 may further include a transceiver 205. The transceiver 205 is in communication with the processor 201 and may display information in a variety of ways. The transceiver 205 is in communication with the processor 201 and may receive signaling sent by an application server or a service layer device in a variety of ways.

Consistent with the above-described technical solution, as a specific embodiment, fig. 3 is a flowchart illustrating a data scheduling method including a specific implementation procedure of a base station. Although the data scheduling method described herein is executed based on the base station shown in fig. 2, it should be noted that the specific operating environment of the data scheduling method disclosed in the embodiment of the present invention is not limited to the base station described above.

As shown in fig. 3, the data scheduling method disclosed in the embodiment of the present invention specifically includes the following steps:

s301, a base station acquires the capability information of User Equipment (UE), wherein the time for acquiring the capability information of the UE is before the base station receives a Radio Resource Control (RRC) connection establishment completion signaling sent by the UE to the base station.

Optionally, the capability information of the UE may include at least one of: UE priority, (Single-band/multi-band deployment) One band/multi-band deployment, single-carrier/multi-carrier indication Single-tone/multi-carrier indication (indication of scheduling unit, which may specifically refer to Single subcarrier, carrier, etc.), (control plane/user plane indication) CP/UP indication, (UE type) UE-Category, subscription attribute Identifier (subscription Profile Identifier, SPID), (Radio capability) Radio capability, (Access layer-version information) Access Stratum Release, multi-process Hybrid-automatic repeat request (Hybrid-ARQ, HARQ) capability, large-capacity Transport Block (TBS) capability, new Power type (New Power Class), mobility enhancement indication, and re-establishment indication.

Illustratively, the UE Category UE-Category includes UEs supporting or requiring multi-process HARQ and/or UEs supporting or requiring a large TBS.

Illustratively, the re-establishment indication includes a re-establishment indication of UP (user plane) and/or a re-establishment indication of CP (control plane).

Illustratively, the re-establishment indication of UP is used to distinguish an indication of whether mobility enhancement is supported after re-establishment.

Illustratively, the reestablishment indication of the CP is used to indicate whether the reestablishment connection is for reestablishment of the CP scheme or for distinguishing between an indication of the CP and an indication of the UP.

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

For example, the reestablishment indication is carried in a message sent by the UE to the base station, and this message may be an RRC connection reestablishment request, an RRC connection establishment request, or an RRC connection recovery request.

For example, the reestablishment indication may be indicated in the message as the establishment cause value, or the reestablishment indication may be an indication information element in the message.

For the CP scheme, the re-establishment procedure is not supported in R13, but after R14 is introduced, a distinguishing indication of the CP scheme or the UP scheme needs to be performed. The re-establishment indication may be a re-establishment indication for only the CP scheme or an indication message for distinguishing whether it is a CP re-establishment or an UP scheme re-establishment. The rebuild indication may also distinguish between indications of different versions UP rebuilds. The CP scheme refers to optimization of the control plane, and the UP scheme refers to optimization of the user plane.

NB-IoT UP UEs in release R13 do not support mobility enhancement, i.e., PDCP STATUS REPORT flow and X2 port data and UE context transfer in re-establishment flow. In R14, the UE performs mobility enhancement, so as to be able to consider supporting PDCP STATUS REPORT procedure or uplink data retransmission, and X2 port data and UE context transfer, where uplink data retransmission refers to: when the UE has uplink data to send out in the previous connection, but does not receive the acknowledgement that the receiving party receives the data before changing the cell, a STATUS REPORT (PDCP STATUS REPORT) of the receiving PDCP layer needs to be supported in the reestablishment process, so as to know which uplink PDCP SN number corresponds to the data that is not sent to the base station, and perform retransmission. Because R13 does not support PDCP STATUS REPORT, the UE cannot perform uplink data retransmission.

Mobility enhancement indication as a capability of the UE is mainly used for: when the UE has mobility, for example, an RRC connection re-establishment process (such as cell change, cell handover, or cell reselection) triggered by the RLF, when the UE using the UP scheme sends an RRC connection re-establishment request to the target base station, the base station may know that the UE can support at least one of context, data, and PDCP status report procedures transferred between base stations after receiving the indication information. The UE herein may be a UE using an UP scheme in NB-IoT.

The indication information may represent a mobility enhancement capability indication, or a version information indication, or other information.

If the target base station receives the relevant indication information, the indication information can be transmitted at the X2 port, so that the source base station can conveniently perform corresponding processing, and the UE context and the data can be forwarded to the target base station. The indication information includes at least one of a mobility enhancement indication, a reestablishment indication of UP, a reestablishment indication, or a reestablishment indication of CP.

Optionally, the base station broadcasts an indication whether the base station supports mobility enhancement.

Mobility enhancement from the perspective of the base station, it may be considered as a capability of the base station, and the capabilities of different base stations for mobility support of the UE may be different, for example, the base station of the R13 version may not support a reestablishment procedure for a CP or an UP scheme X2 port data forwarding. But the base stations of R14 may all be supported, or be partially supported. The base station may indicate whether or not it supports mobility enhancement, may indicate separately whether or not it supports CP re-establishment or UP mobility enhancement for different capabilities, or may indicate as a whole mobility enhancement, such as broadcasting in a system message. Specifically, when the base station supports the mobility enhancement capability, the base station indicates through system broadcast, may use a 1-bit overall indication or multiple bits to individually indicate multiple specific capabilities included in the mobility enhancement, and may select whether to access according to an indication message when the UE is establishing an RRC connection or reestablishing an RRC connection. If the base station does not support the broadcast support or the broadcast support, the UE may choose not to access the cell. After the UE accesses, the base station may perform different operations according to the UE capability, such as low priority processing, rejecting or releasing connection, and transmitting capability information to other nodes.

Optionally, the base station may also notify the UE whether it supports the mobility enhancement capability through dedicated signaling, and after the UE accesses the cell, the base station may notify through dedicated signaling, such as RRC connection establishment, RRC connection re-establishment, RRC connection rejection or release message, or other messages.

Specifically, when the UE accesses the target cell, and after the UE sends the RRC connection reestablishment request, if the target base station does not have an available UE context and does not support the mobility enhancement capability, the target base station notifies the UE through dedicated signaling.

Optionally, when the UE selects or reselects a cell, the cell may be selected in consideration of the factor. Alternatively, the base station broadcasts cells supporting mobility enhancement, and the base station may broadcast an offset with mobility enhancement capability (offset) in the system broadcast, which may be used for cell selection or reselection for UEs supporting mobility enhancement capability. Alternatively, the reselection or selection may be performed only for the cell supporting the mobility enhancement capability, and a ranking mechanism or a priority mechanism may be used. Or for the UE supporting mobility enhancement, the cell supporting mobility enhancement may be considered as a high priority, and may be preferentially selected during selection. Optionally, if the base station learns whether the other cells support the mobility enhancement capability, the base station may set offset of cell specific to the cell supporting the mobility enhancement capability.

When a UE has accessed a cell supporting mobility enhancement, when mobility occurs, such as handover, or RLF triggers a re-establishment procedure, or reselection of a connected cell, if a target base station accessed by the UE does not support mobility enhancement, which may be understood as not supporting UE context, inter-base station forwarding of data, and other operations, the target base station may reject or release the connection of the UE, or redirect to other cells supporting the feature or reestablish the connection. Or the target base station may indicate to the source base station, and the source base station may transmit the UE context according to the indication information, or notify the source base station to delete and store the UE context and data.

If the base station to which the UE starts accessing does not support mobility enhancement, and after mobility occurs, the target base station of the access cell supports forwarding data and a UE context, optionally, the UE may indicate to the target base station that the base station of the connection established before does not support mobility enhancement, and the target base station may reject or release the connection or reestablish the connection if there is no UE context, or when the target base station receives a UE reestablishment request and generates an RLF indication or reacquires a context request or other indication messages to the source base station, the source base station may reply an indication message including rejection or non-support of the operation, or only transfer the UE context, not transfer data, and indicate. The specific bearer message is not limited, and may be an existing X2 port message or a new message.

The base station broadcasts an indication of the UE category or UE capabilities used for multicast traffic of the base station. For multicast services, such as Single Cell Point To multipoint (SC-PTM) services in NB-IoT, due To different UE types and capabilities, a base station needs To broadcast an indication of the UE type or capability To which such multicast service transmission is directed, so that the UE determines whether To accept the multicast service according To its type or capability. For example, the indication may include: the indication of whether a normal TBS or a large TBS is used for multicast service transmission, the indication of whether a single HARQ process or multiple HARQ processes are used, the indication of the type of the UE, and the like. In addition, since there are multiple SC-PTM services simultaneously in the network, the above indication may be for all SC-PTM services in the current cell. The base station may also perform the above indication separately for each SC-PTM service for flexible control.

It should be noted that the time position of the indication of the UE type or the UE capability used by the base station for broadcasting the multicast service of the base station may be before step S301 or may not be before step S301, and the idle UE may also receive the indication, which is not limited in the present invention.

Optionally, the new power type is included in a control element (MAC CE) of a MAC protocol data unit (MAC PDU) carrying the RRC connection establishment request. For example, as shown in fig. 3.A, the MAC CE of Data Volume and Power Headroom Report (Data Headroom and Power Headroom Report) indicates the new Power type of the UE. The specific manner may be that, the existing reserved bit R is used to indicate the new power type, the number of the used reserved bits depends on the number of the new power types to be indicated, and if only one new power type is supported in the network, only one reserved bit may be used as the new power type indication; if two or three new power types are supported in the network, two reserved bits need to be used as the new power type indication. And the reserved bits in the existing MAC CE are used for indicating the new power type, so that the design of the new MAC CE can be avoided, and meanwhile, the new power type and other information are reported to the base station together, and the signaling overhead can be reduced.

For example, please refer to fig. 3.1, and fig. 3.1 is a schematic flow chart of another data scheduling method according to an embodiment of the present invention.

Optionally, a specific implementation manner of the base station acquiring the capability information of the UE is as follows: and the base station receives an RRC connection request which is sent by the UE and carries the capability information of the UE. Specifically, the RRC connection request sent by the UE to the base station carries capability information of the UE, where the capability information may be all capability information of the UE or part of capability information of the UE, and specifically depends on the size of the signaling capacity of the RRC connection request. If the RRC connection request signaling capacity is sufficient, the RRC connection request signaling carries all capability information of the UE, and if the RRC connection request signaling capacity is limited, the RRC connection request signaling carries part of necessary capability information of the UE, such as UE priority, single-tone/multi-tone indication, and CP/UP indication. Optionally, the capability information of some UEs may be divided into groups, and a protocol is written, and only an index number of a certain UE capability information group is carried in the RRC connection request signaling, which does not need to carry the capability information of the UE.

Optionally, a specific implementation manner of acquiring the capability information of the UE by the base station is as follows: and the base station receives a paging message which is sent by a core network and carries the capability information of the UE. Specifically, when the core network issues a paging message to the base station, if the core network stores the UE context information, the core network carries the capability information of the UE in the paging message sent to the base station, where the UE context information includes the capability information of the UE, and after receiving the capability information of the UE, the base station stores the capability information of the UE, so as to be used after being connected to the UE subsequently.

Optionally, a specific implementation manner of the base station acquiring the capability information of the UE is as follows: a base station receives a first paging message sent by a core network; if the first paging message does not carry the capability information of the UE, the base station sends a second paging message carrying indication information to the UE, wherein the indication information is used for indicating the UE to report the capability information of the UE; and the base station receives the RRC connection request which is sent by the UE and carries the capability information of the UE. Specifically, if the core network does not store the UE context information, a first paging message sent by the core network to the base station does not carry the capability information of the UE, at this time, the base station adds indication information in a second paging message sent to the UE, where the indication information is used to indicate that a subsequent UE needs to report the capability information of the UE to the base station, and the UE may carry the capability information of the UE in an RRC connection request signaling sent to the base station subsequently. In other embodiments, the UE may also carry the capability information of the UE in other signaling sent to the base station in the following, for example, RRC connection setup complete signaling and the like.

For example, please refer to fig. 3.2, and fig. 3.2 is a schematic flowchart of another data scheduling method according to an embodiment of the present invention.

Optionally, the capability information includes first capability information, and the capability information further includes second capability information, third capability information, a fourth capability information component, or fifth capability information; the base station acquires the capability information of the UE, and the method comprises the following steps: a base station receives an RRC connection request which is sent by UE and carries first capability information; a base station receives an initial context establishment request which is sent by a core network and carries second capability information; or, the base station acquiring capability information of the user equipment UE includes: a base station receives an RRC connection request which is sent by UE and carries first capability information; a base station sends a UE capability information acquisition request to the UE; the base station receives third capability information sent by the UE in response to the UE capability information acquisition request; or, the base station acquiring capability information of the user equipment UE includes: a base station receives an RRC connection request which is sent by UE and carries first capability information; the base station receives a downlink Access Stratum (NAS) transmission signaling which is sent by a core network and carries fourth capability information; or, the base station acquiring capability information of the user equipment UE includes: a base station receives an RRC connection request which is sent by UE and carries first capability information; and the base station receives the RRC connection establishment completion signaling which is sent by the UE and carries the fifth capability information.

Specifically, since the capacity of the RRC connection request signaling sent by the UE to the base station is limited, at this time, the RRC connection request signaling may only carry part of necessary capability information (first capability information) of the UE, such as UE priority, single-tone/multi-tone indication, CP/UP indication, and the like. If the subsequent UE still has data to be uploaded, in order that the base station can allocate data scheduling resources to the UE more reasonably, after the UE sends the first capability information to the base station, the base station needs to acquire the remaining capability information of the UE, and the acquiring method specifically includes the following steps: 1. the core network may carry the second capability information in the initial context establishment request signaling sent to the base station (or other signaling sent by the core network to the base station), and optionally, before the initial context establishment request signaling sent by the core network to the base station (or other signaling sent by the core network to the base station), the base station may carry indication information in the initial UE information signaling sent by the core network to indicate which capability information of the UE is sent by the core network to the base station; 2. a base station sends a capability information acquisition request of the UE to the UE (specifically, the base station can be realized by a UE capability information acquisition signaling sent to the UE or other signaling sent by the base station to the UE), the capability information acquisition request of the UE can carry indication information to indicate the UE to send which capability information of the UE to the base station, and the UE responds to the capability information acquisition request of the UE and sends third capability information to the base station; 3. when the core network issues downlink data, the core network can carry fourth capability information in a downlink NAS transmission signaling sent to the base station; 4. optionally, before the RRC connection setup complete signaling sent by the UE to the base station, the base station may carry indication information in an RRC connection setup request signaling sent to the UE to indicate which capability information of the UE is sent to the base station by the core network.

Optionally, the second capability information, the third capability information, the fourth capability information, and the fifth capability information may be the same capability information or different capability information, and the present invention is not limited thereto.

Optionally, the first capability information, the second capability information, the third capability information, the fourth capability information, or the fifth capability information may be in an inclusive relationship, an intersecting relationship, an incompatible relationship, or the like, and the present invention is not limited thereto.

For example, please refer to fig. 3.3, and fig. 3.3 is a schematic flow chart of another data scheduling method according to an embodiment of the present invention.

Optionally, a specific implementation manner of the base station acquiring the capability information of the UE is as follows: a base station receives an RRC connection request sent by UE, wherein the RRC connection request carries routing auxiliary information of a first core network, and the first core network is a core network in which the UE context information is stored; the base station determines the core network and the identification information of the core network for identifying the UE according to the routing auxiliary information of the first core network; the base station sends a capability information acquisition request of the UE to a determined core network, wherein the capability information acquisition request of the UE carries identification information of the core network for identifying the UE, the identification information of the core network for identifying the UE is used for the determined core network to acquire the UE context information, and the UE context information comprises the capability information of the UE; and the base station receives the capability information of the UE, which is sent by the determined core network in response to the capability information acquisition request of the UE.

For example, when the base station sends a capability information acquisition request of the UE to the core network, the base station carries identification information of the core network identification UE (where the identification information of the core network identification UE is used by the core network to find context information of the UE stored in the core network according to the identification information), the identification information of the core network identification UE may be a Globally Unique Temporary UE Identity (GUTI), or may be a combination of a Globally Unique mobility management entity MME Identity (GUMMEI) and a System Architecture Evolution (SAE) Temporary mobile subscriber Identity S-TMSI, or eNB MME UE S1AP ID, or S1AP UE ID pair (S1-AP UE ID pair), and the like), and is used to verify whether the determined core network is a core network (or a core network previously registered by the UE) having the UE context information, if the determined core network is a core network ID pair (S1-AP UE ID pair), the base station may then send the UE carrying the context information directly obtained by the core network to the core network according to the context information, and if the UE is a UE is not connected to the UE which is the first UE which is not previously obtained by the core network.

Alternatively, the GUTI consists of PLMN ID, MMEI and M-TMSI, the specific composition of which is shown in fig. 3.3 a.

Optionally, the sending, by the base station, the capability information acquisition request of the UE to the determined core network may be implemented by a UE capability information request signaling sent by the base station to the core network, or may be implemented by other signaling sent by the base station to the core network, which is not limited in the present invention.

Optionally, as shown in fig. 3.4, after the base station acquires the capability information of the user equipment UE in step S301, the method further includes: and the base station sends indication information used by the UE capability to the UE, wherein the indication information used by the UE capability is used for indicating the UE capability used by data scheduling, and the indication information used by the UE capability comprises indication information indicating whether the data scheduling uses multi-process HARQ and/or indication information indicating whether the data scheduling uses TBS.

For example, the 3GPP organization has currently completed standardization of the Rel-13 release of NB-IoT, and enhancements to NB-IoT are being made in the Rel-14 release. The method is characterized in that due to the fact that the rate supported by an NB-IoT terminal in Rel-13 is low, application scenarios are limited, rel-14 release NB-IoT introduces two new characteristics, double HARQ processes (Rel-13 only has a single process) and a larger TBS, and the transmission rate of the NB-IoT terminal is enhanced. Currently, the base station does not include the newly introduced 2HARQ process capability or the large TBS capability in the UE capability, and the base station cannot schedule the UE using these two new characteristics in the RRC connection establishment message or in the subsequent data scheduling. Which in turn affects the performance of the scheduling.

The base station acquires the UE capability first, and then indicates whether the UE supports the new characteristics of the multi-process HARQ capability and the large TBS capability, if the acquired UE capability supports the two new characteristics, the base station can indicate whether the UE uses the two new characteristics in the subsequent data scheduling in the RRC connection establishment message. Wherein, the UE supports these two features, respectively, to indicate, for example, whether to support multi-process HARQ with a single indication (e.g. 1 bit), and another single indication to indicate whether to support large TBS; of course, a unified indication may be used to indicate whether the UE supports both features (since both features are for high data rate, the unified indication is less overhead). In addition, the name of the indication may be UE capability or UE type. In addition, the indication of the base station to the UE may be two separate indications as well, or may be one unified indication.

In addition, the base station needs to indicate to the UE that: both new features provide higher transmission rates, while NB-IoT first guarantees the coverage of the network. When the coverage of the UE is poor, the high transmission rate itself cannot be achieved due to the need to send a large number of repetitions to enhance the coverage. That is, although some new or more capable UEs have the capability to support these two new features, in some cases (e.g., poor UE coverage), the base station does not necessarily use these two new features to schedule the UE. Since whether to use these two characteristics is related to the Downlink Control Information (DCI) format of the UE, the discontinuous reception behavior timing relationship, and the like, in order to avoid the problem of scheduling failure or reduced transmission efficiency, the base station needs to indicate whether the UE uses these two capabilities for subsequent scheduling.

Optionally, the specific implementation manner of determining, by the base station, the core network and the identification information of the core network identifying the UE according to the routing assistance information of the first core network is as follows: the base station determines GUMMEI of the first core network and identification information of the core network identification UE according to the routing auxiliary information of the first core network; the base station determines whether the core network selectable by the base station comprises a first core network or not according to the GUMMEI; if the core network selectable by the base station contains the first core network, the base station selects the first core network; if the core network selectable by the base station does not include the first core network, the base station selects any one of the core networks selectable by the base station.

For example, the RRC connection request signaling sent by the UE to the base station carries routing assistance information of the first core network, and the base station may determine, according to the routing assistance information of the first core network, the GUMMEI of the first core network and the identification information of the core network identification UE. The base station determines whether the base station can be connected with the first core network according to the GUMMEI. The base station selects the first core network if the first core network exists in the core network to which the base station can connect, and selects any one of the core networks to which the base station can connect if the first core network does not exist in the core network to which the base station can connect.

Optionally, the first core network routing assistance information includes S-TMSI.

Optionally, the first core network routing assistance information includes at least one of the following: selected Public Land Mobile Network address index/Public Land Mobile Network address (PLMN) ID, mobility management entity MME group ID (MMEGI).

Optionally, the routing assistance information of the first core network includes S-TMSI and a selected public land mobile network address index/PLMN ID, and the specific implementation manner of the base station determining, according to the routing assistance information of the first core network, the globally unique mobility management entity MME identifier GUMMEI of the first core network and the identifier information of the core network identifier UE is as follows: the base station acquires the MMEGI of the first core network from the base station according to the S-TMSI and the selected public land mobile network address index/PLMN ID; and determining a globally unique mobile management entity MME identification GUMMEI of the first core network and identification information of the core network identification UE according to the S-TMSI, the selected public land mobile network address index/PLMN ID and the MMEGI.

Specifically, for some fixed UEs, the previously connected core network group is not changed, that is, the MMEGI of the core network to which these UEs are connected is not changed, and the base station may store the information of the MMEGI, the S-TMSI, and the like of these UEs, in this case, the UE only needs to carry the selected public land mobile network address index or the PLMN ID and the S-TMSI, and does not need to carry the information of the MMEGI and the like of the UE in the RRC connection request sent to the base station, and the base station may obtain the prestored information of the MMEGI and the like according to the selected public land mobile network address index/PLMN-ID and S-TMSI, and form the identification information of the GUMMEI and the core network identification UE according to the PLMN-ID, the S-TMSI, and the MMEGI. The base station is used for storing the routing auxiliary information of part of the core network, the base station can be used as an identification code to acquire through the S-TMSI, and after the S-TMSI is updated, the core network can be carried through a certain downlink signaling sent to the base station, and can also be a certain new signaling. Such as RRC connection pending response, S1-AP, S1 UE deactivation Context Ack, initial Context setup request, etc., the present invention is not limited. Of course, the S-TMSI in the embodiment of the present invention may also be other UE identifiers, such as C-RNTI. The above method is not limited to the method of using the base station to store information, and any other method may be used that uses the base station to store information and uses S-TMSI or other information updated by the UE interacting with the core network as the identification code.

Optionally, the routing assistance information of the first core network includes S-TMSI and a selected public land mobile network address index/PLMN ID, and the specific implementation manner of the base station determining, according to the routing assistance information of the first core network, the globally unique mobility management entity MME identifier GUMMEI of the first core network and the identifier information of the core network identifier UE is as follows: the base station determines the MMEGI of the first core network according to the S-TMSI and the selected public land mobile network address index/PLMN ID; and determining a globally unique mobile management entity MME identification GUMMEI of the first core network and identification information of the core network identification UE according to the S-TMSI, the selected public land mobile network address index/PLMN ID and the MMEGI.

Specifically, for some fixed UEs, assuming that the base station belongs to only one core network group, that is, the MMEGI of the core network to which the base station is connected is unchanged and unique, when the UE enters the connected state from the idle state, the UE carries the selected public land mobile network address index/PLMN-ID and S-TMSI in the RRC connection request signaling of the sending base station. When the base station connected with the UE is the same as the base station connected with the UE, the base station can determine the MMEGI of the core network connected with the UE before according to the selected public land mobile network address index and the S-TMSI because the MMEGI of the core network connected with the base station is unique, and the base station can form the GUMMEI of the core network connected with the UE before and the identification information of the core network identification UE according to the PLMN-ID, the S-TMSI and the MMEGI. The subsequent base station may obtain the capability information of the UE and the context information of the UE through the core network, and please refer to the implementation described in fig. 3.3 for a specific implementation, which is not described herein.

Optionally, when the base station to which the UE is connected is not the base station connected before, it needs to indicate that the core network does not need to send the capability information of the UE to the base station. The specific indication mode is as follows: 1. the 1-bit indication information may be carried in an RRC connection request signaling sent by the UE to the base station, where the indication information is used to indicate that the base station does not need to acquire the UE capability information according to the method for acquiring the UE capability information described in fig. 3.3; or, 2, the base station may determine, through the information carried by the UE, whether the UE capability information needs to be acquired by the method for acquiring UE capability information described in fig. 3.3. The methods of the other embodiments described in the present invention and so on may be used if the above-described acquisition method is not used.

Optionally, the routing assistance information of the first core network includes S-TMSI, and the specific implementation manner of the base station determining, according to the routing assistance information of the first core network, a globally unique mobility management entity MME identifier GUMMEI of the first core network is as follows: the base station determines the MMEGI and the PLMN ID of the first core network according to the S-TMSI; and the base station determines a globally unique Mobile Management Entity (MME) identifier GUMMEI of the first core network and identifier information of the core network for identifying the UE according to the S-TMSI, the MMEGI and the PLMN ID.

Specifically, for some fixed UEs, the previously connected core network group is unchanged, that is, the MMEGI of the core network to which the UEs are connected is unchanged, and the UE supports only one PLMN, in this case, the RRC connection request signaling sent by the UE to the base station carries only S-TMSI, and the base station may determine the MMEGI and the PLMN ID of the first core network according to the S-TMSI, and then determine the MME identification GUMMEI of the first core network and the identification information of the core network identification UE according to the S-TMSI, the MMEGI, and the PLMN ID.

Optionally, the routing assistance information of the first core network includes S-TMSI and MMEGI, and the base station determines, according to the routing assistance information of the first core network, a globally unique mobility management entity MME identifier GUMMEI of the first core network, including: the base station determines the PLMN ID of the first core network according to the S-TMSI; and the base station determines the GUMMEI of the first core network and the identification information of the core network identification UE according to the S-TMSI, the MMEGI and the PLMN ID. Specifically, when the UE supports only one PLMN, in this case, an RRC connection request signaling sent by the UE to the base station carries only S-TMSI and MMEGI, and the base station may determine, according to the S-TMSI, a PLMN ID of the first core network, and then determine, according to the S-TMSI, the MMEGI, and the PLMN ID, an MME identifier GUMMEI of the first core network and identifier information identifying the UE by the core network.

Optionally, the routing assistance information of the first core network includes S-TMSI, MMEGI, and selected public land mobile network address index/PLMN ID, and the base station determines, according to the routing assistance information of the first core network, the globally unique mobility management entity MME identifier GUMMEI and the identifier information of the core network identifier UE of the first core network, including: and the base station determines the GUMMEI of the first core network and the identification information of the core network identification UE according to the S-TMSI, the MMEGI and the selected public land mobile network address index/PLMN ID.

Optionally, the base station sends, to the determined core network, the S-TMSI that is carried in the capability information acquisition request of the UE, so that the core network identifies the UE. Optionally, the base station sends, to the determined core Network, the capability information acquisition request of the UE, which may carry an S-TMSI, an eNB UE S1AP ID, a Tracking Area Identity (TAI) of the LTE, an Evolved UMTS Terrestrial Radio Access Network (E-UTRAN CGI), and an RRC establishment cause; and the core network may carry the UE capability information, a unique identifier of the UE on the S1 interface of the MME side (MME UE S1 Application Protocol ID, MME UE S1AP ID), a unique identifier of the UE on the S1 interface of the eNB side (eNB UE S1 Application Protocol ID, eNB UE S1AP ID), and a UE aggregation maximum bit rate when transmitting the UE capability information to the base station; and so on. Therefore, the initial UE information signaling sent to the core network by the subsequent base station only carries the NAS PDU, wherein the initial UE information signaling can be changed into uplink NAS transmission signaling, and the signaling name is not limited here. Of course, after the UE sends the RRC connection request to the base station, the signaling that the base station sends the capability request of the UE to the core network may also be changed to the initial UE information signaling/uplink NAS transmission information, where the signaling name is not limited and the carrying content is the same as above.

Optionally, after determining, by the base station, the identification information of the core network and the core network identification UE according to the routing auxiliary information of the first core network, if the core network connected to the base station changes, the base station sends the identification information of the core network identification UE to the changed core network, where the identification information of the core network identification UE is used for the changed core network to request the first core network for the context information of the UE.

For example, please refer to fig. 3.4, and fig. 3.4 is a schematic flow chart of another data scheduling method according to an embodiment of the present invention.

Optionally, a specific implementation manner of the base station acquiring the capability information of the UE is as follows: a base station receives a connection establishment request or a connection reestablishment request which is sent by UE and carries routing auxiliary information of a first base station, wherein the first base station is a base station which stores the routing auxiliary information of a second core network, and the second core network is a core network which stores the UE context information; the base station asks for the routing auxiliary information of a second core network from the first base station according to the routing auxiliary information of the first base station; the base station determines the core network and the identification information of the core network for identifying the UE according to the routing auxiliary information of the second core network; a base station sends a UE context information acquisition request to a determined core network, wherein the UE capability information acquires identification information carrying UE identified by the core network, the identification information of the UE identified by the core network is used for the determined core network to acquire the UE context information, and the UE context information comprises the UE capability information; and the base station receives the UE context information sent by the determined core network responding to the UE context information acquisition request.

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

For example, when the UE fails to connect with the connected base station, the UE performs connection reestablishment operation with the new base station, the UE carries the C-RNTI, the physical cell identifier, and the S-TMSI to initiate a connection reestablishment process to the new base station, so that the new base station finds the base station previously connected with the UE according to the above information, and obtains core network routing auxiliary information such as the MMEGI of the core network (second core network) previously connected with the UE from the base station previously connected with the UE through the X2 interface, thereby obtaining core network information previously connected with the UE, and obtains context information of the UE through the core network previously connected with the UE, and the context information of the UE completing the connection reestablishment process includes capability information of the UE. For a specific process of the base station acquiring the context information of the UE, please refer to the method described in fig. 3.3, which is not described herein. And if the base station currently connected with the UE is communicated with the previous base station, the flow of obtaining the UE context information is the same.

S302, the base station distributes data scheduling resources for the UE according to the capability information of the UE.

Specifically, after receiving the capability information of the UE, the base station allocates a data scheduling resource to the UE according to the capability information of the UE. And sending an RRC connection establishment signaling to the UE, wherein the RRC connection establishment signaling carries data scheduling resources allocated by the base station for the UE, the UE sends an RRC connection establishment completion signaling after receiving the RRC connection establishment signaling, and schedules the resources according to the data allocated to the UE by the base station, and the NAS message sent at the moment carries data of the network to be reported by the UE.

For example, the capability information of the UE includes a CP/UP indication, and the base station sets a header of the PDCP accordingly in subsequent data or signaling transmission, for example, when the CP is used to transmit data, the PDCP header is short, and when the UP transmission scheme is used, the PDCP header is long. CP/UP indications include the following: 1. indicating by using a Packet Data Convergence Protocol (PDCP) header of an RRC connection setup completion signaling sent to a base station by UE, wherein no MAC-I in a short byte (such as 1 byte) represents a CP, and a MAC-I in a long byte (such as 5 bytes) represents an UP; 2. if the base station connected with the UE is the same as the base station connected with the UE, the short PDCP header is used for sending the RRC connection request, if the base station side has the context of the UE, the UE represents UP, the base station carries out subsequent related configuration according to the UP characteristic, and if the base station side does not have the context of the UE, the base station carries out subsequent related configuration according to the CP characteristic. 3. If the base station connected by the UE is different from the previous base station, the short PDCP head is also used for sending the RRC connection establishment completion signaling, the base station side does not have the UE context information, the base station still uses the related configuration of the CP, and after the UE sends the RRC connection establishment completion signaling, the base station can judge whether the CP or the UP is the CP or the UP according to the size of the NAS packet and carry out subsequent configuration. 4. The same second and third CP/UP indications can also use a long PDCP header, and the subsequent UP/CP configuration is the same as the second and third CP/UP indications, which will not be described again; 5. if the CP or the UP can not be identified according to the size of the data packet, after the core network receives the packet, the base station is informed through the downlink signaling for subsequent data transmission. Or after the UE and the core network perform information interaction and know whether the CP or UP is specifically selected, the core network issues downlink signaling of the base station to tell whether the CP or UP is present in the base station.

Consistent with the above-described technical solution, as a specific embodiment, fig. 4 is a flowchart illustrating a data scheduling method including a specific implementation procedure of a base station. Although the data scheduling described herein is performed based on the base station shown in fig. 2, it should be noted that the specific operating environment of the data scheduling method disclosed in the embodiment of the present invention is not limited to the base station described above.

As shown in fig. 4, the data scheduling method disclosed in the embodiment of the present invention specifically includes the following steps:

s401, a base station receives a downlink NAS transmission signaling which is sent by a core network and carries the capability information of UE; or the base station receives an uplink information transmission signaling which is sent by the UE and carries the capability information of the UE; and the base station sends the uplink NAS transmission signaling carrying the UE capability information to a core network.

S402, the base station distributes data scheduling resources for the UE according to the capability information of the UE.

Specifically, the embodiments of the present invention are mainly applied to the background of CP data transmission, after the UE is connected to the network side (base station or core network), and after the base station is connected to the core network, if the core network has downlink data to be issued, a downlink NAS transmission signaling sent to the base station by the core network may include a NAS PDU, and a new cell (information element, IE) may be added to transmit the capability information of the UE, so that the core network sends the capability information of the UE to the base station in sequence when sending the downlink data, thereby reducing the use of dedicated signaling, such as an initial context establishment request signaling. Or, after the UE is connected to the network side and there is uplink data transmission between the UE and the base station, the UE adds the UE capability information in the uplink information transmission signaling and NAS PDU sent to the base station, and transfers the UE capability information to the base station, and the base station sends the UE capability information to the core network.

Optionally, after the RRC establishment is completed, the base station may carry indication information and an identifier for searching for the UE context in the initial UE context sent to the core network, where the indication information is used to indicate the core network to send the UE capability information to the base station. After receiving the indication information, the core network may send the capability information of the UE to the base station in a downlink signaling sent to the base station by the subsequent core network, and the signaling name is not limited in the present invention.

Optionally, after the base station sends the initial UE context to the core network, the base station may ask the core network for the capability information of the UE through a certain signaling sent to the core network. The capability information of the UE may be sent to the base station in a downlink signaling sent to the base station by the subsequent core network, and the signaling name is not limited in the present invention.

Optionally, the core network may be carried in downlink data sent to the base station.

Optionally, the base station does not need to instruct the core network to send the capability information of the UE to the base station, and the core network may be directly carried by a certain signaling.

It can be seen that, in the embodiment of the present invention, the capability information of the UE obtained by the base station is carried in the uplink signaling transmission signaling sent by the UE to the base station, or carried in other data or signaling sent by the core network to the base station, compared with the prior art that the capability information of the UE is carried in a dedicated signaling (such as an initial context establishment request signaling) sent by the core network to the base station, it can be seen that, by carrying the capability information of the UE while transmitting data, the embodiment of the present invention saves the dedicated signaling, and further reduces power consumption.

Consistent with the above-described technical solution, as a specific embodiment, fig. 5 is a flowchart illustrating a connection release method including specific implementation procedures of a UE, a base station, and a core network. Although the data scheduling described herein is performed based on the UE, the base station and the core network shown in fig. 2, it should be noted that the specific operating environment of the connection release method disclosed in the embodiment of the present invention is not limited to the UE, the base station and the core network.

As shown in fig. 5, the connection release method disclosed in the embodiment of the method of the present invention specifically includes the following steps:

s501, the base station receives a downlink NAS transmission signaling which is sent by a core network and carries a connection release indication.

S502, the base station sends a downlink information transmission signaling carrying the connection release indication to the UE.

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

Specifically, when the uplink transmission completes the data transmission, release auxiliary information may be added to the last sent NAS information to indicate whether downlink data feedback is needed, and when the downlink feedback is not needed, after the core network receives the data, the core network triggers the S1 port release procedure. If the uplink indication needs downlink feedback information, an IE may be added to a downlink NAS transmission signaling sent by the core network to the base station to indicate that the base station releases after the data transmission is completed, and a connection release indication is added to the NAS PDU transmitted by the data packet, and after receiving the information, the base station knows that the release operation is performed after the transmission is completed. And the base station sends a downlink information transmission signaling carrying the connection release indication to the UE, and the UE receives the downlink direct transmission message sent by the base station and releases the downlink direct transmission message according to the indication information in the NAS PDU. After sending the downlink information transmission signaling carrying the connection release indication to the UE, the base station sends a release signaling to the core network, so that the core network releases the S1 interface after receiving the release signaling, and the specific name of the release signaling is not limited.

Optionally, the sending, by the core network, the connection release indication to the base station may also be adding the connection release indication to an MAC header of an air interface signaling.

Optionally, when the uplink data is transmitted, if no indication is made in the uplink packet that the downlink feedback including the release indication information is needed, if no data is transmitted within a period of time, the base station or the core network may trigger the release of the connection, and if the release flow is triggered by the base station, after sending the release indication information to the UE, the S1 port release confirmation (indication) is performed to the core network. If the UE is a release procedure triggered by the core network, the procedure is the same as the existing release UE context procedure, and will not be described here.

Optionally, during downlink transmission, if the core network finishes transmitting a data packet, the timer is started, and if the timer overflows, the normal connection release process is performed. If uplink feedback is needed, the release process can be carried out. If the timer does not overflow, the UE sends an uplink packet, and the release procedure is also applicable here, that is, the UE may trigger the network side to release the connection at any time, or may continue to wait for the timer to overflow after the data transmission is completed. If the network side knows that the data packet is the last data packet, a field may be added to the downlink NAS transport signaling to instruct the base station to release the connection, and release instruction information is added to the NAS PDU and is transmitted by the base station through downlink information transport.

It can be seen that, in the embodiment of the present invention, the connection release indication sent by the core network to the base station is carried in the downlink NAS transport signaling sent by the core network to the base station, and compared with the connection release indication carried in the dedicated signaling sent by the core network to the base station in the prior art, the connection release indication is carried in the data transport, so that the embodiment of the present invention saves the dedicated signaling, and further reduces power consumption.

Fig. 6 is a schematic structural diagram of a base station according to an embodiment of the present invention. The base station 600 includes: an acquisition unit 601 and an allocation unit 602.

An obtaining unit 601, configured to obtain capability information of a user equipment UE, where a time when the capability information of the UE is obtained is before a radio resource control RRC connection setup complete signaling sent by the UE to a base station is received by the base station.

An allocating unit 602, configured to allocate data scheduling resources to the UE according to the capability information of the UE.

Optionally, the obtaining unit 601 is specifically configured to:

receiving an RRC connection request which is sent by UE and carries the capability information of the UE;

alternatively, the first and second liquid crystal display panels may be,

receiving a paging message which is sent by a core network and carries the capability information of the UE;

alternatively, the first and second liquid crystal display panels may be,

receiving a first paging message sent by a core network; if the first paging message does not carry the capability information of the UE, sending a second paging message carrying indication information to the UE, wherein the indication information is used for indicating the UE to report the capability information of the UE; and receiving an RRC connection request which is sent by the UE and carries the capability information of the UE.

Optionally, after the obtaining unit 601 obtains the capability information of the user equipment UE, the base station further includes a third receiving unit and a fourth transmitting unit,

the third receiving unit is configured to: when the capability information is first capability information, receiving an initial context establishment request which is sent by a core network and carries the second capability information; or, receiving a downlink non-access stratum (NAS) transmission signaling carrying the fourth capability information and sent by a core network; or, receiving an RRC connection setup complete signaling carrying the fifth capability information sent by the UE;

the fourth sending unit is configured to: when the capability information is first capability information, sending a UE capability information acquisition request to the UE; and receiving the third capability information sent by the UE in response to the UE capability information acquisition request.

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,

the obtaining unit 601 is specifically configured to: receiving an RRC connection request carrying the first capability information and sent by UE; receiving an initial context establishment request which is sent by a core network and carries the second capability information;

alternatively, the first and second electrodes may be,

the obtaining unit 601 is specifically configured to: receiving an RRC connection request which is sent by UE and carries the first capability information; sending a UE capability information acquisition request to the UE; receiving the third capability information sent by the UE in response to the UE capability information acquisition request;

alternatively, the first and second electrodes may be,

the obtaining unit 601 is specifically configured to: receiving an RRC connection request which is sent by UE and carries the first capability information; receiving a downlink non-access stratum (NAS) transmission signaling which is sent by a core network and carries the fourth capability information;

alternatively, the first and second electrodes may be,

the obtaining unit 601 is specifically configured to: acquiring capability information of User Equipment (UE), comprising: the base station receives an RRC connection request which is sent by UE and carries the first capability information; and receiving an RRC connection establishment completion signaling carrying the fifth capability information and sent by the UE.

Optionally, the obtaining unit 601 includes:

a first receiving unit, configured to receive an RRC connection request sent by a UE, where the RRC connection request carries routing assistance information of a first core network, and the first core network is a core network in which context information of the UE is stored; a first determining unit, configured to determine, according to the routing assistance information of the first core network, identification information of the core network and UE identified by the core network; a first sending unit, configured to send a capability information acquisition request of the UE to a determined core network, where the capability information acquisition request of the UE carries identification information of the core network for identifying the UE, and the identification information of the core network for identifying the UE is used for the determined core network to acquire context information of the UE, where the context information of the UE includes the capability information of the UE; the first receiving unit is further configured to receive capability information of the UE, which is sent by the determined core network in response to the capability information obtaining request of the UE.

Optionally, after the first receiving unit receives the capability information of the UE sent by the determined core network in response to the capability information obtaining request of the UE, the base station further includes a fifth sending unit, configured to send UE capability use indication information to the UE, where the UE capability use indication information is used to indicate UE capability used for data scheduling, and the UE capability use indication information includes indication information indicating whether data scheduling uses multi-process HARQ and/or indication information indicating whether data scheduling uses a large-capacity transport block TBS.

Optionally, the first determining unit includes:

a second determining unit, configured to determine, according to the routing assistance information of the first core network, a globally unique MME identity GUMMEI of the first core network and identity information of a core network identification UE; a third determining unit, configured to determine whether the core network selectable by the base station includes the first core network according to the GUMMEI; a first selecting unit, configured to select the first core network if the core network selectable by the base station includes the first core network; the first selecting unit is further configured to select any one of the core networks selectable by the base station if the core network selectable by the base station does not include the first core network.

Optionally, the first core network routing assistance information includes a system architecture evolution SAE temporary mobile subscriber identity S-TMSI.

Optionally, the first core network routing assistance information further includes at least one of the following: selected public land mobile network address index/public land mobile network address PLMN ID or mobility management entity MME group identity MMEGI.

Optionally, the routing assistance information of the first core network includes S-TMSI and selected public land mobile network address index/PLMN ID, and the second determining unit is specifically configured to:

acquiring the MMEGI of the first core network from the base station according to the S-TMSI and the selected public land mobile network address index/the PLMN ID; and determining the globally unique Mobile Management Entity (MME) identification GUMMEI of the first core network and the identification information of the core network identification (UE) according to the S-TMSI, the selected public land mobile network address index/the PLMN ID and the MMEGI.

Optionally, the routing assistance information of the first core network includes S-TMSI, and the second determining unit is specifically configured to:

determining the MMEGI and the PLMN ID of the first core network according to the S-TMSI; and determining a globally unique Mobile Management Entity (MME) identifier GUMMEI of the first core network and identifier information of core network identification (UE) according to the S-TMSI, the MMEGI and the PLMN ID.

Optionally, the routing assistance information of the first core network includes S-TMSI and MMEGI, and the second determining unit is specifically configured to:

determining a PLMN ID of the first core network according to the S-TMSI; and determining a globally unique Mobile Management Entity (MME) identifier GUMMEI of the first core network and identifier information of core network identification (UE) according to the S-TMSI, the MMEGI and the PLMN ID.

Optionally, the routing assistance information of the first core network includes S-TMSI, MMEGI, and selected public land mobile network address index/PLMN ID, and the second determining unit is specifically configured to:

and determining the globally unique Mobile Management Entity (MME) identification GUMMEI of the first core network and the identification information of the core network identification (UE) according to the S-TMSI, the MMEGI and the selected public land mobile network address index/the PLMN ID.

Optionally, the base station in fig. 6 further includes:

a second sending unit, configured to send, to the changed core network, identification information for identifying the UE by the core network if the core network connected to the base station changes, where the identification information for identifying the UE by the core network is used for the changed core network to retrieve context information of the UE from the first core network.

Optionally, the obtaining unit 601 includes:

a second receiving unit, configured to receive a connection establishment request or a link reestablishment request that is sent by a UE and carries routing assistance information of a first base station, where the first base station is a base station that stores routing assistance information of a second core network, and the second core network is a core network that stores context information of the UE; a solicitation unit, configured to solicit, from the first base station, routing assistance information of a second core network according to the routing assistance information of the first base station; a fourth determining unit, configured to determine, according to the routing assistance information of the second core network, identification information of the core network and the UE identified by the core network; a third sending unit, configured to send the UE context information obtaining request to the determined core network, where the capability information of the UE obtains identification information carrying UE identified by the core network, and the identification information of the UE identified by the core network is used for the determined core network to obtain the UE context information, where the UE context information includes the capability information of the UE; the second receiving unit is further configured to receive the UE context information sent by the determined core network in response to the UE context information obtaining request.

Optionally, the capability information includes at least one of: the method comprises the steps of deploying One band/multi-band deployment, indicating Single-tone/multi-tone by Single carrier/multi-carrier, indicating control plane/user plane (CP/UP indication), indicating UE type (UE-Category), radio capability, signing attribute identifier (SPID), access layer-version information (Access Stratum) Release, multi-process Hybrid Automatic Repeat (HARQ) capability, large TBS capability, new power type, mobility enhancement indication, control plane reestablishment capability and reestablishment indication.

Optionally, the UE Category UE-Category includes UEs supporting or requiring multi-process HARQ and/or UEs supporting or requiring a large TBS.

Optionally, the new power type is included in a control element (MAC CE) of a MAC protocol data unit carrying the RRC connection setup request.

Optionally, the reestablishment includes a reestablishment indication of a User Plane (UP) and/or a reestablishment indication of a Control Plane (CP), where the reestablishment indication of the UP is used to distinguish whether mobility enhancement is supported after reestablishment, and the reestablishment indication of the CP is used to indicate whether a reestablishment connection is used for reestablishment of the CP or to distinguish between the indication of the CP and the indication of the UP.

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

Optionally, the reestablishment indication is further used as an establishment cause value for indicating.

Optionally, before the obtaining unit 601 obtains the capability information of the UE, the base station further includes a processing unit:

the processing unit is configured to broadcast an indication whether the base station supports mobility enhancement.

In the present embodiment, the base station 600 is presented in the form of a functional unit. An "element" may refer to an application-specific integrated circuit (ASIC), an electronic circuit, a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other devices that may provide the described functionality. In a simple embodiment, those skilled in the art will appreciate that the base station 600 may take the form shown in FIG. 2. The obtaining unit 601 and the allocating unit 602 may be implemented by a processor and a memory of fig. 2.

Fig. 7 is a schematic structural diagram of a base station according to an embodiment of the present invention. As shown in fig. 7, the communication system includes a UE, a core network, and a base station, wherein:

the base station is used for acquiring the capability information of the UE, wherein the time for acquiring the capability information of the UE is before the base station receives a Radio Resource Control (RRC) connection establishment completion signaling sent by the UE to the base station; and distributing data scheduling resources for the UE according to the capability information of the UE.

In an embodiment, the UE is configured to send, to the base station, an RRC connection request carrying capability information of the UE; the specific implementation mode of the base station for acquiring the capability information of the user equipment UE is as follows: the base station is used for receiving an RRC connection request which is sent by UE and carries the capability information of the UE;

alternatively, the first and second electrodes may be,

the core network is used for sending a paging message carrying the capability information of the UE to the base station; the specific implementation mode of the base station for acquiring the capability information of the user equipment UE is as follows: the base station is used for receiving a paging message which is sent by a core network and carries the capability information of the UE;

alternatively, the first and second electrodes may be,

a core network, configured to send a first paging message to the base station; the base station is used for receiving a first paging message sent by a core network; the base station is further configured to send a second paging message carrying indication information to the UE if the first paging message does not carry the capability information of the UE, where the indication information is used to indicate the UE to report the capability information of the UE; the UE is used for receiving a second paging message which is sent by the base station and carries indication information; the UE is also used for sending an RRC connection request carrying the capability information of the UE to the base station; the specific implementation mode of the base station for acquiring the capability information of the user equipment UE is as follows: the base station is used for receiving an RRC connection request which is sent by the UE and carries the capability information of the UE.

In an embodiment, the capability information is first capability information, after the base station acquires the capability information of the user equipment UE,

or, the core network is configured to send a downlink non-access stratum NAS transport signaling carrying the fourth capability information to the base station; the base station is further configured to receive a downlink non-access stratum NAS transport signaling carrying the fourth capability information and sent by a core network;

In an embodiment, the capability information comprises first capability information, the capability information further comprises second capability information, third capability information, fourth capability information, or fifth capability information,

the UE is used for sending an RRC connection request carrying the first capability information to the base station; the core network is configured to send an initial context establishment request carrying the second capability information to the base station; the specific implementation mode of the base station for acquiring the capability information of the user equipment UE is as follows: the base station is used for receiving an RRC connection request which is sent by UE and carries the first capability information; the base station is further configured to receive an initial context establishment request carrying the second capability information and sent by a core network;

alternatively, the first and second electrodes may be,

the UE is used for sending an RRC connection request carrying the first capability information to the base station; the base station is used for sending a UE capability information acquisition request to the UE; the UE is also used for receiving a UE capability information acquisition request sent by the base station; the UE is further used for responding to the UE capability information acquisition request and sending the third capability information to the base station; the specific implementation mode of the base station for acquiring the capability information of the user equipment UE is as follows: the base station is used for receiving an RRC connection request which is sent by UE and carries the first capability information; the base station is further configured to receive the third capability information sent by the UE in response to the UE capability information obtaining request;

alternatively, the first and second liquid crystal display panels may be,

the UE is used for sending an RRC connection request carrying the first capability information to the base station; the core network is configured to send, to the base station, a downlink non-access stratum NAS transport signaling that carries the fourth capability information; the specific implementation mode of the base station for acquiring the capability information of the user equipment UE is as follows: the base station is used for receiving an RRC connection request which is sent by UE and carries the first capability information; the base station is further configured to receive a downlink non-access stratum NAS transport signaling carrying the fourth capability information and sent by a core network;

alternatively, the first and second liquid crystal display panels may be,

the UE is used for sending an RRC connection request carrying the first capability information to the base station; the UE is further configured to send an RRC connection setup complete signaling carrying the fifth capability information to the base station; the specific implementation mode of the base station for acquiring the capability information of the user equipment UE is as follows: the base station is used for receiving an RRC connection request which is sent by UE and carries the first capability information; the base station is further configured to receive an RRC connection setup complete signaling that carries the fifth capability information and is sent by the UE.

In an embodiment, the UE is configured to send an RRC connection request to the base station, where the RRC connection request carries routing assistance information of a first core network, and the first core network is a core network in which the UE context information is stored; the specific implementation mode of the base station for acquiring the capability information of the user equipment UE is as follows:

the base station is used for receiving the RRC connection request sent by the UE; the base station is further configured to determine, according to the routing assistance information of the first core network, identification information of the core network and the core network for identifying the UE; sending a capability information acquisition request of the UE to the determined core network, wherein the capability information acquisition request of the UE carries identification information of the core network for identifying the UE, the identification information of the core network for identifying the UE is used for the determined core network to acquire context information of the UE, and the context information of the UE comprises the capability information of the UE; and receiving the capability information of the UE, which is sent by the determined core network in response to the capability information acquisition request of the UE.

In an embodiment, after the base station receives the capability information of the UE sent by the determined core network in response to the capability information obtaining request of the UE,

the base station is further configured to send UE capability use indication information to the UE, where the UE capability use indication information is used to indicate UE capability used for data scheduling, and the UE capability use indication information includes indication information indicating whether data scheduling uses multi-process HARQ and/or indication information indicating whether data scheduling uses a large capacity transport block TBS.

In an embodiment, the specific implementation manner of determining, by the base station according to the routing assistance information of the first core network, the identification information of the core network and the globally unique temporary UE identification core network for identifying the UE is as follows:

the base station is configured to determine, according to the routing assistance information of the first core network, a globally unique MME identifier, GUMMEI, of the first core network and identifier information of a core network identifier, UE; determining whether the core network selectable by the base station contains the first core network or not according to the GUMMEI; if the core network selectable by the base station contains the first core network, selecting the first core network; and if the core network selectable by the base station does not comprise the first core network, selecting any one of the core networks selectable by the base station.

In an embodiment, the first core network routing assistance information comprises a system architecture evolution, SAE, temporary mobile subscriber identity, S-TMSI.

In an embodiment, the first core network routing assistance information further includes at least one of: selected public land mobile network address index/public land mobile network address PLMN ID or mobility management entity MME group identity MMEGI.

In an embodiment, the routing assistance information of the first core network includes S-TMSI and selected public land mobile network address index/PLMN ID, and the specific implementation manner of the base station determining, according to the routing assistance information of the first core network, the globally unique mobility management entity MME identifier GUMMEI of the first core network and the identification information of the core network identity UE is as follows:

the base station is used for acquiring the MMEGI of the first core network from the base station according to the S-TMSI and the selected public land mobile network address index/the PLMN ID; and determining the globally unique Mobile Management Entity (MME) identification GUMMEI of the first core network and identification information of core network identification (UE) according to the S-TMSI, the selected public land mobile network address index/the PLMN ID and the MMEGI.

In an embodiment, a specific implementation manner of determining, by the base station according to the routing assistance information of the first core network, the globally unique mobility management entity MME identifier GUMMEI of the first core network and the identifier information of the core network identifier UE is as follows:

the base station is used for determining the MMEGI and the PLMN ID of the first core network according to the S-TMSI; and determining a globally unique Mobile Management Entity (MME) identifier GUMMEI of the first core network and identifier information of core network identification (UE) according to the S-TMSI, the MMEGI and the PLMN ID.

In an embodiment, the routing assistance information of the first core network includes S-TMSI and MMEGI, and the specific implementation manner of the base station determining, according to the routing assistance information of the first core network, the globally unique mobility management entity MME identifier GUMMEI of the first core network and the identifier information of the core network identity UE is as follows:

the base station is used for determining the PLMN ID of the first core network according to the S-TMSI; and determining a globally unique Mobile Management Entity (MME) identifier GUMMEI of the first core network and identifier information of core network identification (UE) according to the S-TMSI, the MMEGI and the PLMN ID.

In an embodiment, the routing assistance information of the first core network includes S-TMSI, MMEGI, and selected public land mobile network address index/PLMN ID, and the specific implementation manner of the base station determining, according to the routing assistance information of the first core network, the globally unique mobility management entity MME identity GUMMEI of the first core network and the identification information of the core network identity UE is as follows:

and the base station is used for determining the globally unique Mobile Management Entity (MME) identifier (GUMMEI) of the first core network and the identifier information of the core network identification (UE) according to the S-TMSI, the MMEGI and the selected public land mobile network address index/the PLMN ID.

In an embodiment, after the base station determines, according to the routing assistance information of the first core network, identification information of a core network and a UE identified by the core network, the base station is further configured to:

and if the core network connected with the base station changes, sending identification information of the core network identification UE to the changed core network, wherein the identification information of the core network identification UE is used for the changed core network to ask the first core network for the context information of the UE.

In an embodiment, the UE is configured to send a connection establishment request or a link reestablishment request carrying routing auxiliary information of a first base station to the base station, where the first base station is a base station storing routing auxiliary information of a second core network, and the second core network is a core network storing context information of the UE; the specific implementation mode of the base station for acquiring the capability information of the user equipment UE is as follows:

the base station is configured to receive a connection establishment request or a link reestablishment request that is sent by the UE and carries the routing assistance information of the first base station; the base station is further configured to request, to the first base station, routing assistance information of a second core network according to the routing assistance information of the first base station; determining the core network and the identification information of the core network for identifying the UE according to the routing auxiliary information of the second core network; sending the UE context information acquisition request to the determined core network, wherein the capability information of the UE acquires identification information carrying the core network identification UE, the identification information of the core network identification UE is used for the determined core network to acquire the UE context information, and the UE context information comprises the capability information of the UE; and receiving the UE context information sent by the determined core network responding to the UE context information acquisition request.

In an embodiment, the capability information includes at least one of: the method comprises the steps of deploying One band/multi-band deployment, single carrier/multi-carrier indication Single-tone/multi-tone indication, control plane/user plane indication CP/UP indication, UE type UE-Category, radio capability, subscription attribute identifier SPID, access layer-version information Access Stratum Release, multi-process HARQ capability, large TBS capability, new power type, mobility enhancement indication, control plane reestablishment capability and reestablishment indication.

In an embodiment, the UE Category UE-Category includes UEs supporting or requiring multi-process HARQ and/or UEs supporting or requiring a large TBS.

In an embodiment, the new power type is included in a control element (MAC CE) of a MAC protocol data unit carrying the RRC connection setup request.

In an embodiment, the re-establishment includes a re-establishment indication of a User Plane (UP) and/or a re-establishment indication of a Control Plane (CP), the re-establishment indication of the UP is used for distinguishing whether mobility enhancement is supported after re-establishment, and the re-establishment indication of the CP is used for indicating whether re-establishment of a connection is used for re-establishment of the CP, or for distinguishing whether the indication of the CP or the indication of the UP.

In an embodiment, the reestablishment indication is carried in a message sent by the UE to the base station, where the message includes an RRC connection reestablishment request.

In an embodiment, the re-establishment indication is also used as an establishment cause value for indication.

In an embodiment, before the base station acquires the capability information of the UE, the base station is further configured to broadcast an indication whether the base station supports mobility enhancement.

It can be understood that the UE, the core network, and the base station included in the communication system of this embodiment may be specifically implemented according to the method in the embodiment of the method described in fig. 3, and a specific implementation process thereof may refer to the description related to the embodiment of the method described in fig. 3, and is not described herein again.

An embodiment of the present invention further provides a computer storage medium, where the computer storage medium may store a program, and when the program is executed, the program includes part or all of the steps of any one of the data scheduling methods and one of the connection releasing methods described in the foregoing method embodiments.

It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the order of acts, as some steps may occur in other orders or concurrently in accordance with the invention. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required by the invention.

In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to the related descriptions of other embodiments.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implementing, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of some interfaces, devices or units, and may be an electric or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented as a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable memory. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a memory and includes several instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned memory comprises: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk, and various media capable of storing program codes.

Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by associated hardware instructed by a program, which may be stored in a computer-readable memory, which may include: flash Memory disks, read-Only memories (ROMs), random Access Memories (RAMs), magnetic or optical disks, and the like.

The above embodiments of the present invention are described in detail, and the principle and the implementation of the present invention are explained by applying specific embodiments, and the above description of the embodiments is only used to help understanding the method of the present invention and the core idea thereof; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in view of the above, the content of the present specification should not be construed as a limitation to the present invention.

Claims

1. A method of data scheduling, comprising:

the terminal provides first capability information of the terminal to a base station; the first capability information is used for allocating data scheduling resources for transmitting data by a control plane of the terminal;

the terminal acquires the data scheduling resource from the base station;

and the terminal sends a radio resource control connection establishment completion signaling to the base station according to the data scheduling resource, wherein a non-access stratum (NAS) message included in the radio resource control connection establishment completion signaling comprises the data of the terminal, and the time for providing the first capability information of the terminal is before the time for sending the radio resource control connection establishment completion signaling.

2. The method of claim 1, wherein the terminal provides the first capability information of the terminal to a base station, and wherein the method comprises:

and the terminal sends a radio resource control connection request to the base station, wherein the radio resource control connection request comprises the first capability information.

3. The method according to claim 1 or 2, wherein the first capability information comprises:

the multi-carrier indication, or alternatively,

the multi-subcarrier indication indicates, or alternatively,

the user plane indicates that, alternatively,

the kind of terminal, or alternatively,

multi-process hybrid automatic repeat request, HARQ, capability, or,

the ability to transport blocks of large capacity, or alternatively,

the new power type, or alternatively,

the re-establishment of the indication, or alternatively,

terminal priority, or

A single-band deployment, or alternatively,

a multi-band deployment, or alternatively,

the control plane indicates the direction of the control plane, or,

the subscription attribute identifier, or alternatively,

access stratum-version information, or alternatively,

the radio capabilities, or alternatively,

a mobility enhancement indication.

4. The method according to claim 1 or 2, wherein the radio resource control connection setup complete signaling further comprises second capability information of the terminal, the second capability information comprising:

the multi-carrier indication, or alternatively,

the multi-subcarrier indication indicates, or alternatively,

the user plane indicates that, alternatively,

terminal class, or multi-process hybrid automatic repeat request, HARQ, capability, or,

the ability to transport blocks of large capacity, or alternatively,

the new power type, or, alternatively,

the re-establishment indication, or alternatively,

terminal priority, or

A single-band deployment, or alternatively,

a multi-band deployment, or alternatively,

the control plane indicates the direction of the control plane, or,

the subscription attribute identifier, or alternatively,

access stratum-version information, or alternatively,

the radio capabilities, or alternatively,

a mobility enhancement indication.

5. The method of claim 1 or 2, further comprising:

the terminal receives indication information whether to use a multi-process hybrid automatic repeat request, HARQ, from the base station.

6. The method of claim 2, wherein the radio resource control connection request further comprises routing assistance information of the first mobility management entity; wherein the routing assistance information is used for acquiring third capability information of the terminal from the first mobility management entity.

7. The method of claim 6, wherein the third capability information comprises:

the multi-carrier indication, or alternatively,

the multi-subcarrier indication indicates, or alternatively,

the user plane indicates that the user is, or,

the kind of terminal, or alternatively,

multi-process hybrid automatic repeat request, HARQ, capability, or,

the ability to transport blocks of large capacity, or alternatively,

the new power type, or, alternatively,

the re-establishment of the indication, or alternatively,

terminal priority, or

A single-band deployment, or alternatively,

a multi-band deployment, or alternatively,

the control plane indicates the direction of the control plane, or,

the subscription attribute identifier, or alternatively,

access stratum-version information, or alternatively,

the radio capabilities, or alternatively,

a mobility enhancement indication.

8. The method of claim 1 or 2, further comprising:

and the terminal receives a paging message carrying indication information from the base station, wherein the indication information is used for indicating the terminal to report the capability information of the terminal.

9. A computer-readable storage medium comprising instructions that, when executed on a computer, cause the computer to perform the method of any one of claims 1-8.

10. A method of data scheduling, comprising:

a base station acquires first capability information of a terminal from the terminal; the first capability information is used for allocating data scheduling resources for transmitting data by a control plane of the terminal;

the base station indicates the data scheduling resource to the terminal;

and the base station receives a radio resource control connection establishment completion signaling from the terminal according to the data scheduling resource, wherein a non-access stratum (NAS) message included in the radio resource control connection establishment completion signaling comprises the data of the terminal, and the time for acquiring the first capability information of the terminal is before the time for receiving the radio resource control connection establishment completion signaling.

11. The method of claim 10, wherein the base station acquires the first capability information of the terminal from the terminal, and comprises:

the base station receives a radio resource control connection request from the terminal, the radio resource control connection request including the first capability information.

12. The method according to claim 10 or 11, wherein the first capability information comprises:

the multi-carrier indication, or alternatively,

the multi-subcarrier indication indicates, or alternatively,

the user plane indicates that, alternatively,

the kind of terminal, or alternatively,

multi-process hybrid automatic repeat request, HARQ, capability, or,

the ability to transport blocks of large capacity, or alternatively,

the new power type, or alternatively,

the re-establishment of the indication, or alternatively,

terminal priority, or

A single-band deployment, or alternatively,

a multi-band deployment, or alternatively,

the control plane indicates the direction of the control plane, or,

the subscription attribute identifier, or alternatively,

access stratum-version information, or alternatively,

the radio capabilities, or alternatively,

a mobility enhancement indication.

13. The method according to claim 10 or 11, wherein the radio resource control connection setup complete signaling further comprises second capability information of the terminal, the second capability information comprising:

the multi-carrier indication, or alternatively,

the multi-subcarrier indication, or alternatively,

the user plane indicates that the user is, or,

the kind of terminal, or alternatively,

multi-process hybrid automatic repeat request, HARQ, capability, or,

the ability to transport blocks of large capacity, or alternatively,

the new power type, or, alternatively,

the re-establishment of the indication, or alternatively,

terminal priority, or

A single-band deployment, or alternatively,

a multi-band deployment, or alternatively,

the control plane indicates the direction of the control plane, or,

the subscription attribute identifier, or alternatively,

access stratum-version information, or alternatively,

the radio capabilities, or alternatively,

a mobility enhancement indication.

14. The method of claim 10 or 11, further comprising:

and the base station sends indication information whether to use the multi-process hybrid automatic repeat request HARQ or not to the terminal.

15. The method of claim 11, wherein the rrc connection request further includes routing assistance information of the first mobility management entity; wherein the routing assistance information is used for the base station to acquire third capability information of the terminal from the first mobility management entity.

16. The method of claim 15, wherein the third capability information comprises:

the multi-carrier indication indicates, or alternatively,

the multi-subcarrier indication indicates, or alternatively,

the user plane indicates that the user is, or,

the kind of terminal, or alternatively,

multi-process hybrid automatic repeat request, HARQ, capability, or,

the ability to transport blocks of large capacity, or alternatively,

the new power type, or alternatively,

the re-establishment indication, or alternatively,

terminal priority, or

A single-band deployment, or alternatively,

a multi-band deployment, or alternatively,

the control plane indicates the direction of the control plane, or,

the subscription attribute identifier, or alternatively,

access stratum-version information, or alternatively,

the radio capabilities, or alternatively,

a mobility enhancement indication.

17. The method of claim 10 or 11, further comprising:

and the base station sends a paging message carrying indication information to the terminal, wherein the indication information is used for indicating the terminal to report the capability information of the terminal.

18. A communications apparatus comprising a processor coupled to a memory, configured to read and execute instructions from the memory to implement the method of any of claims 10-17.

19. A computer-readable storage medium comprising instructions that, when executed on a computer, cause the computer to perform the method of any of claims 10-17.