Patent Description:
Currently, establishing a radio resource control (radio resource control, RRC) connection between a terminal and an evolved NodeB (evolved NodeB, eNB) in existing long term evolution (long term evolution, LTE) usually includes the following three scenarios:.

In the scenario <NUM> and the scenario <NUM>, after the RRC connection is established, because a mobility management entity (mobility management entity, MME) stores a communication capability of the terminal, the MME may send the communication capability of the terminal to the eNB. In this case, the terminal does not need to report the communication capability of the terminal. In the scenario <NUM>, after the RRC connection is established, because an MME does not store a communication capability of the terminal, the MME initiates a capability reporting request to the terminal, so that the terminal reports the communication capability of the terminal.

However, in a 3rd generation partnership project (English full name: The 3rd Generation Partnership Project, 3GPP for short) 5th generation (5th generation, <NUM>) new radio (new radio, NR) system, many parameters are required for reporting a communication capability of a terminal, and a volume of reported data is much greater than that in LTE. Therefore, a method for associating a communication capability of a terminal with a capability identifier of the terminal is proposed in the prior art, so that an access device or a network device can determine the communication capability of the terminal based on the capability identifier of the terminal. The capability identifier of the terminal is determined based on an international mobile equipment identity (international mobile equipment identity, IMEI) of the terminal. For example, the capability identifier of the terminal may be a type allocation code (type allocation code, TAC) and a software version number (software version number, SVN) in the international mobile equipment identity (international mobile equipment identity, IMEI) of the terminal.

However, the foregoing solution has the following problem: If software of the terminal is refreshed and hardware does not change (in other words, an IMSI of the terminal does not change), but the communication capability of the terminal changes, the terminal cannot update its own communication capability because the capability identifier of the terminal does not change. For example, when a software version upgrade of the terminal causes a change of the communication capability of the terminal, or software version authentication or modification by the global certification forum (global certification forum, GCF) or in a protocol causes a change of the communication capability of the terminal, or subsequent software maintenance causes a change of the communication capability of the terminal, the terminal cannot update its own communication capability if the foregoing communication capability reporting method is used.

Therefore, a technical problem that urgently needs to be resolved currently is how to provide a communication capability reporting method, so that a communications device can update its own communication capability in a timely manner when the communication capability of the communications device is associated with a capability identifier of the communications device. <CIT> describes systems and methods for operating a mobile device in a mobile communication network. The method comprises transmitting a mobile device component identifier to a network node within the mobile communication network. The mobile device component identifier identifies at least one hardware or software component of the mobile device. The mobile device component identifier is indicative of capability information specifying at least one capability of the mobile device for communication with the mobile communication network. The article by <NPL> refers to a UE capability retrieval framework in NR. The <CIT> refers to a signalling procedure for UE capability ID report.

Embodiments of this application provide a communication capability reporting method, a device, and computer-executable instructions, so that a communications device can update its own communication capability in a timely manner when the communication capability of the communications device is associated with a capability identifier of the communications device.

The present application is defined in the appended independent claims. Further implementations are disclosed in the pending independent claims. In the following, implementations not falling within the scope of the claims are to be understood as examples useful for understanding the application.

In description of this application, "/" means "or" unless otherwise specified. For example, A/B may represent A or B. In this specification, "and/or" describes only an association relationship for describing associated objects and represents that three relationships may exist. In addition, in the descriptions of this application, "a plurality of" means two or more than two. In addition, to clearly describe the technical solutions in the embodiments of this application, terms such as "first" and "second" are used in the embodiments of this application to distinguish between same items or similar items that have a basically same function and usage. A person skilled in the art can understand that the terms such as "first" and "second" are not intended to limit a quantity or an execution sequence, and the terms such as "first" and "second" do not indicate a definite difference.

In addition, a network architecture and a service scenario described in the embodiments of this application are intended to describe the technical solutions in the embodiments of this application more clearly, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. A person of ordinary skill in the art may know that: With the evolution of the network architecture and the emergence of new service scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

<FIG> shows a communications system <NUM> according to an embodiment of this application. The communications system <NUM> includes a second communications device <NUM>, a network device <NUM> connected to the second communications device <NUM>, and one or more first communications devices <NUM> connected to the second communications device <NUM>. An example in which the second communications device <NUM> interacts with the network device <NUM> and any first communications device <NUM> is used below for description.

The first communications device <NUM> is configured to determine a capability identifier of the first communications device <NUM>, where the capability identifier of the first communications device <NUM> is one of one or more capability identifiers corresponding to the first communications device <NUM>.

The first communications device <NUM> is further configured to send the capability identifier of the first communications device <NUM> to the second communications device <NUM>.

The second communications device <NUM> is configured to receive the capability identifier of the first communications device <NUM> that is sent by the first communications device <NUM>, and send the capability identifier of the first communications device <NUM> to the network device <NUM>.

The network device <NUM> is configured to receive the capability identifier of the first communications device <NUM> that is sent by the second communications device <NUM>, and determine a communication capability of the first communications device <NUM> based on the capability identifier of the first communications device <NUM>.

Optionally, the communication capability in this embodiment of this application may include, for example, an access capability or a processing capability. This is uniformly described herein, and details are not described below again.

Optionally, the first communications device <NUM> and the second communications device <NUM> in this embodiment of this application may directly communicate with each other, or may communicate with each other through forwarding by another device. This is not specifically limited in this embodiment of this application.

Optionally, the network device <NUM> and the second communications device <NUM> in this embodiment of this application may directly communicate with each other, or may communicate with each other through forwarding by another device. This is not specifically limited in this embodiment of this application.

Optionally, the first communications device <NUM> in this embodiment of this application may be a terminal, a chip system or a circuit in a terminal, or the like. This is not specifically limited in this embodiment of this application. The chip system in this embodiment of this application may include a chip, or may include a chip and another discrete device. This is uniformly described herein, and this is not specifically limited in this embodiment of this application.

Optionally, the second communications device <NUM> in this embodiment of this application may be a terminal, a chip system or a circuit in a terminal, an access device, a chip system or a circuit in an access device, or the like. This is not specifically limited in this embodiment of this application.

Optionally, the network device <NUM> in this embodiment of this application may be a mobility management network element, a chip system or a circuit in a mobility management network element, or the like. This is not specifically limited in this embodiment of this application.

The terminal (terminal) in this embodiment of this application may include various devices with a wireless communication function in an NR system or a future evolved public land mobile network (public land mobile network, PLMN), for example, a handheld device, an in-vehicle device, a wearable device, a computing device, or another processing device connected to a wireless modem; or may include a subscriber unit (subscriber unit), a cellular phone (cellular phone), a smartphone (smartphone), a wireless data card, a personal digital assistant (personal digital assistant, PDA) computer, a tablet computer, a wireless modem (modem), a handheld (handheld) device, a laptop computer (laptop computer), a cordless phone (cordless phone) or a wireless local loop (wireless local loop, WLL) station, a machine type communication (machine type communication, MTC) terminal, user equipment (user equipment, UE), a mobile station (mobile station, MS), a terminal device (terminal device), relay user equipment, or the like. For example, the relay user equipment may be a <NUM> residential gateway (residential gateway, RG). For ease of description, the devices mentioned above are collectively referred to as terminals in this application.

The access device in this embodiment of this application is a device that accesses a core network. For example, the access device may be a base station in the <NUM> NR system or the future PLMN, a broadband network gateway (broadband network gateway, BNG), an aggregation switch, or a non-3GPP access device. The base station may include base stations in various forms, for example, a micro base station (also referred to as a small cell), a macro base station, a relay station, an access point, or an NR NodeB (NR NodeB, gNB) in the <NUM> NR system. This is not specifically limited in this embodiment of this application.

The mobility management network element in this embodiment of this application may be, for example, an access and mobility management function (access and mobility management function, AMF) network element in the <NUM> NR system or another mobility management network element in the future evolved PLMN. This is not specifically limited in this embodiment of this application.

In addition, specific implementation of the foregoing solution is described in detail in the following embodiments, and details are not described herein.

Based on the communications system provided in this embodiment of this application, when the communication capability needs to be reported, the capability identifier of the first communications device that is sent by the first communications device to the second communications device is one of the one or more capability identifiers corresponding to the first communications device. In other words, in this embodiment of this application, different capability identifiers may be used for the first communications device. Therefore, when the communication capability of the first communications device is associated with the capability identifier of the first communications device, the first communications device may update its own communication capability in a timely manner by using the capability identifier determined in the one or more capability identifiers corresponding to the first communications device.

Optionally, the first communications device or the second communications device in <FIG> in this embodiment of this application may be implemented by one device, or may be implemented jointly by a plurality of devices, or may be a functional module in a device. This is not specifically limited in this embodiment of this application. It can be understood that the foregoing function may be a network element in a hardware device, or may be a software function running on dedicated hardware, or may be a virtualized function instantiated on a platform (for example, a cloud platform).

For example, the first communications device or the second communications device in <FIG> in this embodiment of this application may be implemented by a communications device in <FIG> is a schematic diagram of a hardware structure of a communications device according to an embodiment of this application. The communications device <NUM> includes at least one processor <NUM>, a communications line <NUM>, a memory <NUM>, and at least one communications interface <NUM>.

The processor <NUM> may be a general-purpose central processing unit (central processing unit, CPU), a microprocessor, an application-specific integrated circuit (application-specific integrated circuit, ASIC), or one or more integrated circuits configured to control execution of programs of the solutions of this application.

The communications line <NUM> may include a channel that transmits information between the foregoing components.

The communications interface <NUM> is configured to communicate, by using any apparatus like a transceiver, with another device or a communications network, for example, Ethernet, a radio access network (radio access network, RAN), or a wireless local area network (wireless local area networks, WLAN).

The memory <NUM> may be a read-only memory (read-only memory, ROM), another type of static storage device that can store static information and instructions, a random access memory (random access memory, RAM), or another type of dynamic storage device that can store information and instructions; or may be an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), a compact disc read-only memory (compact disc read-only memory, CD-ROM) or another optical disk storage, an optical disc storage (including a compact optical disc, a laser disc, an optical disc, a digital versatile disc, a Blu-ray disc, or the like), a magnetic disk storage medium or another magnetic storage device, or any other medium that can be configured to carry or store expected program code in a form of an instruction or a data structure and that can be accessed by a computer. However, this does not constitute a limitation herein. The memory may exist independently and is connected to the processor by using the communications line <NUM>. Alternatively, the memory may be integrated with the processor.

The memory <NUM> is configured to store a computer executable instruction for executing the solutions of this application, and the processor <NUM> controls execution of the computer executable instruction. The processor <NUM> is configured to execute the computer executable instruction stored in the memory <NUM>, so as to implement a communication capability reporting method provided in the following embodiments of this application.

Optionally, the computer executable instruction in this embodiment of this application may also be referred to as application program code. This is not specifically limited in this embodiment of this application.

In specific implementation, in an embodiment, the processor <NUM> may include one or more CPUs, for example, a CPU <NUM> and a CPU <NUM> in <FIG>.

In specific implementation, in an embodiment, the communications device <NUM> may include a plurality of processors, for example, a processor <NUM> and a processor <NUM> in <FIG>. Each of the processors may be a single-CPU (single-CPU) processor, or may be a multi-CPU (multi-CPU) processor. The processor herein may be one or more devices, a circuit, and/or a processing core configured to process data (for example, a computer program instruction).

In specific implementation, in an embodiment, the communications device <NUM> may further include an output device <NUM> and an input device <NUM>. The output device <NUM> communicates with the processor <NUM>, and may display information in a plurality of manners. For example, the output device <NUM> may be a liquid crystal display (liquid crystal display, LCD), a light emitting diode (light emitting diode, LED) display device, a cathode ray tube (cathode ray tube, CRT) display device, or a projector (projector). The input device <NUM> communicates with the processor <NUM>, and may receive a user input in a plurality of manners. For example, the input device <NUM> may be a mouse, a keyboard, a touchscreen device, or a sensing device.

The communications device <NUM> may be a general-purpose device or a dedicated device. In specific implementation, the communications device <NUM> may be the terminal, the access device, the chip system, or a device with a structure similar to that in <FIG>. A type of the communications device <NUM> is not limited in this embodiment of this application.

With reference to <FIG> and <FIG>, the following describes in detail the communication capability reporting method provided in the embodiments of this application by using an example in which the communications system shown in <FIG> is applied to a current <NUM> NR system, the first communications device is a terminal in the <NUM> NR system, the second communications device is a gNB in the <NUM> NR system, and the network device is an AMF network element in the <NUM> NR system.

It should be noted that names of messages between network elements in the following embodiments of this application, names of parameters in messages, or the like are merely examples, and there may be other names in specific implementation. This is not specifically limited in the embodiments of this application.

<FIG> and <FIG> show a communication capability reporting method according to an embodiment of this application. The capability reporting method includes the following steps.

A terminal sends a random access preamble (random access preamble) to a gNB, so that the gNB receives the random access preamble sent by the terminal.

The gNB sends a random access response (random access response) to the terminal, so that the terminal receives the random access response sent by the gNB.

For related implementations of steps S301 and S302, refer to an existing implementation.

The terminal determines a capability identifier of the terminal, where the capability identifier of the terminal is one of one or more capability identifiers corresponding to the terminal.

Optionally, in this embodiment of this application, the one or more capability identifiers corresponding to the terminal may be prestored on the terminal, or may be calculated by the terminal based on an algorithm when the terminal needs to report a communication capability, or may be obtained by the terminal in another manner. This is not specifically limited in this embodiment of this application.

Optionally, in this embodiment of this application, when a communication capability of a terminal is associated with a capability identifier of the terminal, a plurality of terminal capability identifiers allocated to different terminal vendors are usually different, to avoid a terminal capability collision between different terminal vendors. In other words, each terminal vendor needs to maintain a plurality of terminal capability identifiers different from those of other terminal vendors, and a terminal communication capability corresponding to each terminal capability identifier. In this way, the gNB or an AMF network element may distinguish between terminals of different vendors based on capability identifiers of the terminals, thereby implementing differentiated competition.

Optionally, the one or more capability identifiers in this embodiment of this application may form a capability identifier set, a capability identifier list, or the like. This is not specifically limited in this embodiment of this application.

For example, as shown in <FIG>, a terminal vendor A may maintain one or more terminal capability identifiers, which may include, for example, a capability identifier A1, a capability identifier A2, a capability identifier A3,. , and a capability identifier An; a terminal vendor B may maintain one or more terminal capability identifiers, which may include, for example, a capability identifier B1, a capability identifier B2, a capability identifier B3,. , and a capability identifier Bn. A terminal communication capability corresponding to each terminal capability identifier maintained by the terminal vendor A may be as follows: The capability identifier A1 corresponds to a communication capability A11, the capability identifier A2 corresponds to a communication capability A21, the capability identifier A3 corresponds to a communication capability A31,. , and the capability identifier An corresponds to a communication capability An1. A terminal communication capability corresponding to each terminal capability identifier maintained by the terminal vendor B may be as follows: The capability identifier B1 corresponds to a communication capability B11, the capability identifier B2 corresponds to a communication capability B21, the capability identifier B3 corresponds to a communication capability B31,. , and the capability identifier Bn corresponds to a communication capability Bn1. The capability identifier A1, the capability identifier A2, the capability identifier A3,. , and the capability identifier An are different from the capability identifier B1, the capability identifier B2, the capability identifier B3,. , and the capability identifier Bn. The communication capability A11 corresponding to the capability identifier A1, the communication capability A21 corresponding to the capability identifier A2, the communication capability A31 corresponding to the capability identifier A3,. , and the communication capability An1 corresponding to the capability identifier An may be the same as or different from the communication capability B11 corresponding to the capability identifier B1, the communication capability B21 corresponding to the capability identifier B2, the communication capability B31 corresponding to the capability identifier B3,. , and the communication capability Bn1 corresponding to the capability identifier Bn. This is not specifically limited in this embodiment of this application. In this way, when a communication capability of a terminal is associated with a capability identifier of the terminal, the gNB or the AMF network element may distinguish between terminals of different vendors based on different capability identifiers of the terminals, thereby implementing differentiated competition. For example, if the gNB learns that a capability identifier of a terminal is B <NUM>, the gNB may learn, based on the capability identifier B1 of the terminal, that the terminal is a terminal of the terminal vendor B.

Optionally, in this embodiment of this application, each terminal of a terminal vendor also needs to maintain one or more terminal capability identifiers, and a terminal communication capability corresponding to each terminal capability identifier. The one or more terminal capability identifiers maintained by the terminal are identifiers in one or more terminal capability identifiers maintained by the terminal vendor to which the terminal belongs. In other words, assuming that one or more capability identifiers may form a capability identifier set, a set formed by the one or more terminal capability identifiers corresponding to the terminal is usually a subset of a terminal capability identifier set maintained by the terminal vendor to which the terminal belongs. In addition, one or more terminal capability identifiers maintained by different terminals of a same terminal vendor may overlap, or may not overlap. This is not specifically limited in this embodiment of this application.

For example, in <FIG>, a terminal <NUM> of the terminal vendor A may maintain the capability identifier A1 and the capability identifier A2, and a terminal <NUM> of the terminal vendor A may maintain the capability identifier A2 and the capability identifier A3. The terminal capability identifiers maintained by the terminal <NUM> of the terminal vendor A overlap those maintained by the terminal <NUM> of the terminal vendor A, and an overlapping part is the capability identifier <NUM>.

Alternatively, in <FIG>, a terminal <NUM> of the terminal vendor B may maintain the capability identifier B1 and the capability identifier B2, and a terminal <NUM> of the terminal vendor B may maintain the capability identifiers B3, and so on. The terminal capability identifiers maintained by the terminal <NUM> of the terminal vendor B do not overlap those maintained by the terminal <NUM> of the terminal vendor B.

To sum up, each terminal vendor maintains a plurality of terminal capability identifiers different from those of other terminal vendors, and one or more capability identifiers corresponding to a terminal of the terminal vendor are identifiers in one or more capability identifiers maintained by the terminal vendor. Therefore, to distinguish between terminals of different vendors, one or more capability identifiers corresponding to terminals of different terminal vendors do not overlap. This is uniformly described herein, and details are not described below again.

Optionally, in this embodiment of this application, one or more capability identifiers corresponding to a terminal of a terminal vendor, and a terminal communication capability corresponding to each terminal capability identifier may be updated by using software. For example, when a software version upgrade of the terminal causes a change of a communication capability of the terminal, or software version authentication or modification by the GCF or in a protocol causes a change of a communication capability of the terminal, or subsequent software maintenance causes a change of a communication capability of the terminal, the one or more capability identifiers corresponding to the terminal, and the terminal communication capability corresponding to each terminal capability identifier may be updated.

For example, as shown in <FIG>, assuming that the terminal <NUM> of the terminal vendor A originally maintains the capability identifier A1 and the capability identifier A2, when a software version upgrade of the terminal <NUM> causes a change of a communication capability of the terminal <NUM>, or software version authentication or modification by the GCF or in a protocol causes a change of a communication capability of the terminal <NUM>, or subsequent software maintenance causes a change of a communication capability of the terminal <NUM>, the capability identifier A1 and the capability identifier A2 maintained by the terminal <NUM> of the terminal vendor A may be updated. For example, after the update, the terminal <NUM> maintains the capability identifier A3 and the capability identifier An. When the capability identifiers maintained by the terminal <NUM> of the terminal vendor A are updated to the capability identifier A3 and the capability identifier An, terminal communication capabilities maintained by the terminal <NUM> of the terminal vendor A are also updated to the communication capability A31 corresponding to the capability identifier A3 and the communication capability An1 corresponding to the capability identifier An. This is uniformly described herein, and details are not described below again.

Optionally, in this embodiment of this application, the capability identifier of the terminal may be represented in a plurality of forms. The following describes a representation form of the capability identifier of the terminal.

For example, the capability identifier of the terminal includes at least one component of a first IMEI.

It is assumed that a format of the first IMEI may be shown in <FIG>, and the first IMEI includes an eight-digit TAC field, a six-digit serial number (serial number, SNR) field, and a one-digit check digit (check digit, CD) field. In this case, that the capability identifier of the terminal includes at least one component of a first IMEI includes: the capability identifier of the terminal includes the TAC in the first IMEI; or the capability identifier of the terminal includes the TAC and the SNR in the first IMEI; or the capability identifier of the terminal includes the TAC, the SNR, and the CD in the first IMEI. This is not specifically limited in this embodiment of this application.

Alternatively, it is assumed that a format of the first IMEI may be shown in <FIG>, and the first IMEI includes an eight-digit TAC field, a six-digit SNR field, and a two-digit SVN field. In this case, that the capability identifier of the terminal includes at least one component of a first IMEI includes: the capability identifier of the terminal includes the TAC in the first IMEI; or the capability identifier of the terminal includes the TAC and the SNR in the first IMEI; or the capability identifier of the terminal includes the TAC, the SNR, and the SVN in the first IMEI. This is not specifically limited in this embodiment of this application.

The TAC in <FIG> is a code used to distinguish a brand and a model of the terminal, and the code is allocated by the global system for mobile communications association (global system for mobile communications assembly, GSMA) and its authorized organization. The SNR in <FIG> is a serial number generated by a production line of a terminal vendor. The CD in <FIG> is usually determined by using both the TAC and the SNR, and is used to verify correctness of the TAC and the SNR. The SVN in <FIG> is usually a software version number obtained during a test on a part related to forward communication before the terminal is delivered. For detailed descriptions about the fields related to the first IMEI, refer to existing descriptions about an IMEI.

Optionally, in this embodiment of this application, at least one component of the capability identifier of the terminal may be the same as or different from at least one component of a second IMEI. This is not specifically limited in this embodiment of this application. The second IMEI is an IMEI of the terminal.

For example, it is assumed that a format of the IMEI of the terminal is shown in <FIG>, and the IMEI of the terminal is specifically shown in (a) in <FIG>, and is <NUM><NUM><NUM>. To be specific, in the second IMEI, eight digits of a TAC field are <NUM>, six digits of an SNR field are <NUM>, and two digits of an SVN field are <NUM>. When the first IMEI is specifically shown in (b) in <FIG>, and is <NUM><NUM><NUM>:.

Certainly, <FIG> is merely an example for description. The first IMEI and the second IMEI may be alternatively other identifiers. This is not specifically limited in this embodiment of this application.

Optionally, the first IMEI and the second IMEI in this embodiment of this application may be the same, or may be different. This is not specifically limited in this embodiment of this application.

Optionally, the first IMEI in this embodiment of this application is an IMEI used by a terminal device vendor corresponding to the terminal. To be specific, the first IMEI and the second IMEI in this embodiment of this application are IMEIs available for a same terminal device vendor. For example, both are IMEIs in an IMEI resource pool allocated to a same terminal vendor. This is uniformly described herein, and details are not described below again.

It should be noted that there is no necessary execution sequence between step S303 and step S301 in this embodiment of this application. Step S301 may be performed before step S303, or step S303 may be performed before step S301, or steps S301 and S303 may be performed simultaneously. This is not specifically limited in this embodiment of this application.

The terminal sends an RRC connection request (RRC connection request) message to the gNB, so that the gNB receives the RRC connection request message sent by the terminal.

The gNB sends an RRC connection setup (RRC connection setup) message to the terminal, so that the terminal receives the RRC connection setup message sent by the gNB.

The terminal sends an RRC connection setup complete (RRC connection setup complete) message to the gNB, so that the gNB receives the RRC connection setup complete message sent by the terminal.

In this embodiment of this application, the RRC connection request message in step S304 or the RRC connection setup complete message in step S306 may carry the capability identifier of the terminal that is determined in step S303. This is not specifically limited in this embodiment of this application.

Alternatively, optionally, in this embodiment of this application, the capability identifier of the terminal may be carried in a non-access stratum (non-access stratum, NAS) message. For example, the capability identifier of the terminal may be carried in a NAS message in the RRC connection setup complete message in step S306. The gNB may transparently transmit the NAS message to the AMF network element. This is not specifically limited in this embodiment of this application.

If the RRC connection setup complete message in step S306 or the NAS message in the RRC connection setup complete message in step S306 carries the capability identifier of the terminal that is determined in step S303, there is no necessary execution sequence between step S303 and step S304. Step S303 may be performed before step S304, or step S304 may be performed before step S303, or step S303 and step S304 may be performed simultaneously. This is not specifically limited in this embodiment of this application.

Steps S301 to S306 provide specific implementation of reporting, by the terminal, the capability identifier of the terminal to the gNB in an RRC connection setup process. Optionally, the communication capability reporting method provided in this embodiment of this application may further include the following step:.

The gNB sends an initial terminal message (initiate UE message) to the AMF network element, so that the AMF network element receives the initial terminal message sent by the gNB.

The initial terminal message carries the capability identifier of the terminal.

Optionally, if the capability identifier of the terminal that is sent by the terminal to the gNB is carried in the NAS message, the initial terminal message in this case includes the NAS message. This is not specifically limited in this embodiment of this application.

After receiving the initial terminal message sent by the gNB, the AMF network element may search whether the AMF network element stores a communication capability of the terminal that corresponds to the capability identifier of the terminal. Assuming that the AMF network element does not store the communication capability of the terminal that corresponds to the capability identifier of the terminal, the communication capability reporting method provided in this embodiment of this application may further include the following steps S308 to S314.

The AMF network element sends a terminal context setup request (UE context setup request) to the gNB, so that the gNB receives the terminal context setup request sent by the AMF network element.

Optionally, the terminal context setup request in this embodiment of this application may further carry the capability identifier of the terminal that is determined in step S303. This is not specifically limited in this embodiment of this application.

The gNB sends a terminal context setup response (UE context setup response) to the AMF network element, so that the AMF network element receives the terminal context setup response sent by the gNB.

The gNB sends a terminal capability enquiry (UE capability enquiry) to the terminal, so that the terminal receives the terminal capability enquiry sent by the gNB.

Optionally, the terminal capability enquiry in this embodiment of this application may further carry the capability identifier of the terminal. This is not specifically limited in this embodiment of this application.

The terminal sends terminal capability information (UE capability information) to the gNB, so that the gNB receives the terminal capability information from the terminal.

The terminal capability information includes the communication capability of the terminal.

Optionally, the terminal capability information may further include the capability identifier of the terminal that corresponds to the communication capability of the terminal. This is not specifically limited in this embodiment of this application.

The gNB stores the communication capability of the terminal.

The gNB sends a terminal capability information indication (UE capability information indication) to the AMF network element, so that the AMF network element receives the terminal capability information indication sent by the gNB.

The terminal capability information indication includes the communication capability of the terminal.

Optionally, the terminal capability information indication in this embodiment of this application may further include the capability identifier of the terminal that corresponds to the communication capability of the terminal. This is not specifically limited in this embodiment of this application.

The AMF network element stores a correspondence between the capability identifier of the terminal and the communication capability of the terminal.

It should be noted that, in this embodiment of this application, the correspondence that is between the capability identifier of the terminal and the communication capability of the terminal and that is stored on the AMF network element may include the capability identifier of the terminal, and the communication capability corresponding to the capability identifier of the terminal. For example, a plurality of correspondences stored on the AMF network element may be shown in Table <NUM>.

Certainly, Table <NUM> merely provides an example manner of storing a correspondence between a communication capability of a terminal and a capability identifier of the terminal, and there may be another storage form. This is not specifically limited in this embodiment of this application.

Alternatively, optionally, assuming that the AMF network element stores the communication capability of the terminal that corresponds to the capability identifier of the terminal, the communication capability reporting method provided in this embodiment of this application may further include the following steps S315 to S317.

The AMF network element determines the communication capability of the terminal based on the capability identifier of the terminal and the stored correspondence between the capability identifier of the terminal and the communication capability of the terminal.

The AMF network element sends a terminal context setup request to the gNB, so that the gNB receives the terminal context setup request sent by the AMF network element.

The terminal context setup request carries the communication capability of the terminal.

The gNB stores the communication capability of the terminal.

Steps S308 to S314 may be applied to a procedure in which the terminal initially registers with a network. Steps S315 to S317 may be applied to a procedure in which the terminal switches from an idle state to a connected state, or steps S315 to S317 may be applied to a procedure in which the terminal is handed over from one gNB to another gNB. This is not specifically limited in this embodiment of this application.

Optionally, the communication capability reporting method provided in this embodiment of this application may further include the following step:
S318. The gNB sends an RRC reconfiguration message (RRC reconfiguration message) to the terminal, so that the terminal receives the RRC reconfiguration message sent by the gNB.

For a related implementation of step S318, refer to an existing implementation.

According to the communication capability reporting method provided in this embodiment of this application, when the communication capability needs to be reported, the capability identifier of the terminal that is sent by the terminal to the gNB is one of the one or more capability identifiers corresponding to the terminal. In other words, in this embodiment of this application, different capability identifiers may be used for one terminal. Therefore, when the communication capability of the terminal is associated with the capability identifier of the terminal, the terminal may update its own communication capability in a timely manner by using the capability identifier determined in the one or more capability identifiers corresponding to the terminal.

The actions of the terminal or the gNB in the foregoing steps S301 to S318 may be performed by the processor <NUM> in the communications device <NUM> shown in <FIG> by invoking the application program code stored in the memory <NUM>. This is not limited in this embodiment.

The embodiment shown in <FIG> and <FIG> is described by using an example in which the communication capability of the terminal is associated with the capability identifier of the terminal, in other words, the terminal supports reporting the capability identifier of the terminal. Optionally, in this embodiment of this application, if the terminal vendor does not maintain the correspondence between the capability identifier of the terminal and the communication capability of the terminal, the terminal of the terminal vendor cannot report the capability identifier of the terminal by using an RRC message or a NAS message. In this case, the communication capability reporting method provided in this embodiment of this application may include the following steps, as shown in <FIG> and <FIG>.

S801 and S802 are the same as steps S301 and S302. For related descriptions, refer to the embodiment shown in <FIG> and <FIG>.

S803 to S805 are similar to steps S303 to S306. A difference lies in, for example: An RRC message, for example, an RRC connection request message or an RRC connection setup complete message, in this embodiment of this application does not carry the capability identifier of the terminal, but may carry indication information, where the indication information is used to indicate that the terminal does not support reporting the capability identifier of the terminal; or a NAS message, for example, a NAS message in an RRC connection setup complete message, in this embodiment of this application does not carry the capability identifier of the terminal, but may carry indication information, where the indication information is used to indicate that the terminal does not support reporting the capability identifier of the terminal. For related descriptions, refer to the embodiment shown in <FIG> and <FIG>.

Optionally, in a possible implementation, the indication information may perform indication by using one or more bits. For example, the bit being <NUM> indicates that the terminal does not support reporting the capability identifier of the terminal, or the bit being <NUM> indicates that the terminal does not support reporting the capability identifier of the terminal.

Optionally, in another possible implementation, all fields of the capability identifier of the terminal may be alternatively set to <NUM> to indicate that the terminal does not support reporting the capability identifier of the terminal. An implementation of the indication information is not specifically limited in this embodiment of this application.

Steps S801 to S805 provide specific implementation of reporting, by the terminal to the gNB in an RRC connection setup process, the indication information indicating that the terminal does not support reporting the capability identifier of the terminal. Further, the communication capability reporting method provided in this embodiment of this application may further include the following step:.

The gNB sends an initial terminal message to the AMF network element, so that the AMF network element receives the initial terminal message sent by the gNB.

The initial terminal message carries the indication information.

Optionally, if the indication information sent by the terminal to the gNB is carried in a NAS message, the initial terminal message in this case includes the NAS message. This is not specifically limited in this embodiment of this application.

Further, the initial terminal message in this embodiment of this application may further carry an identifier of the terminal. After learning that the terminal does not support reporting the capability identifier of the terminal, the AMF network element may query for a corresponding communication capability of the terminal based on the identifier of the terminal.

Assuming that the AMF network element does not store the communication capability of the terminal, the communication capability reporting method provided in this embodiment of this application may further include the following steps S807 to S813.

The AMF network element sends a terminal context setup request (UE context setup request) to the gNB, so that the gNB receives the terminal context setup request sent by the AMF network element.

The gNB sends a terminal context setup response (UE context setup response) to the AMF network element, so that the AMF network element receives the terminal context setup response sent by the gNB.

The gNB sends a terminal capability enquiry (UE capability enquiry) to the terminal, so that the terminal receives the terminal capability enquiry sent by the gNB.

The terminal sends terminal capability information (UE capability information) to the gNB, so that the gNB receives the terminal capability information from the terminal.

The gNB stores the communication capability of the terminal.

The gNB sends a terminal capability information indication (UE capability information indication) to the AMF network element, so that the AMF network element receives the terminal capability information indication sent by the gNB.

The AMF network element stores the communication capability of the terminal.

For example, communication capabilities, stored on the AMF network element, of a plurality of terminals may be shown in Table <NUM>.

Certainly, Table <NUM> merely provides an example manner of storing a communication capability of a terminal, and there may be another storage form. This is not specifically limited in this embodiment of this application.

Alternatively, optionally, assuming that the AMF network element stores the communication capability of the terminal, the communication capability reporting method provided in this embodiment of this application may further include the following steps S814 and S815.

The AMF network element sends a terminal context setup request to the gNB, so that the gNB receives the terminal context setup request sent by the AMF network element.

The gNB stores the communication capability of the terminal.

Steps S807 to S813 may be applied to a procedure in which the terminal initially registers with a network. Steps S814 and S815 may be applied to a procedure in which the terminal switches from an idle state to a connected state, or steps S814 and S815 may be applied to a procedure in which the terminal is handed over from one gNB to another gNB. This is not specifically limited in this embodiment of this application.

Optionally, the communication capability reporting method provided in this embodiment of this application may further include the following step:.

The gNB sends an RRC reconfiguration message to the terminal, so that the terminal receives the RRC reconfiguration message sent by the gNB.

In the communication capability reporting method provided in this embodiment of this application, when the communication capability needs to be reported, if the terminal does not support reporting the capability identifier of the terminal, the terminal sends, to the AMF network element in a core network by using the gNB, the indication information indicating that the terminal does not support reporting the capability identifier of the terminal. In this way, the AMF network element may learn that the terminal does not support reporting the capability identifier of the terminal, and therefore does not search for a corresponding communication capability of the terminal based on the capability identifier of the terminal; instead, when learning, based on the identifier of the terminal, that the AMF network element does not store the communication capability of the terminal, the AMF network element queries for the communication capability of the terminal from the terminal, so that the terminal then reports the communication capability of the terminal. According to this solution, the communication capability of the terminal can be reported without supporting reporting the capability identifier of the terminal.

The actions of the terminal or the gNB in the foregoing steps S801 to S816 may be performed by the processor <NUM> in the communications device <NUM> shown in <FIG> by invoking the application program code stored in the memory <NUM>. This is not limited in this embodiment.

It should be noted that <FIG>, <FIG>, <FIG>, and <FIG> are described by using an example in which a first communications device is a terminal in a <NUM> NR system and a second communications device is a gNB in the <NUM> NR system. Certainly, as described above, the second communications device may be alternatively a terminal in the <NUM> NR system, for example, relay user equipment. In this case, a corresponding communication capability reporting method is similar to that in <FIG> and <FIG> or in <FIG> and <FIG>. A difference lies in, for example: An equivalent forwarding device is added between the terminal and the gNB shown in <FIG> and <FIG> or in <FIG> and <FIG>, and the second communications device mainly forwards received information, for example, the capability identifier of the terminal or the communication capability of the terminal. For other related descriptions, refer to the embodiment shown in <FIG> and <FIG> or in <FIG> and <FIG>. Details are not described again in this embodiment of this application.

The foregoing describes the solutions provided in the embodiments of this application mainly from a perspective of interaction between network elements. It can be understood that, to implement the foregoing functions, the first communications device or the second communications device includes corresponding hardware structures and/or software modules for executing the functions. A person skilled in the art should easily be aware that, in combination with units and algorithm steps of the examples described in the embodiments disclosed in this specification, this application may be implemented by hardware or a combination of hardware and computer software. Whether a function is performed by hardware or hardware driven by computer software depends on particular applications and design constraints of the technical solutions.

In the embodiments of this application, functional modules of the first communications device or the second communications device may be divided based on the foregoing method examples. For example, the functional modules may be divided based on the functions, or at least two functions may be integrated in one processing module. The integrated module may be implemented in a form of hardware, or may be implemented in a form of a software functional module. It should be noted that, in this embodiment of this application, module division is exemplary, and is merely a logical function division. In actual implementation, another division manner may be used.

For example, when the functional modules are divided through integration, <FIG> shows a schematic diagram of a structure of a first communications device <NUM>. The first communications device <NUM> may be the terminal in the foregoing embodiments, or may be a chip system or a circuit in the terminal in the foregoing embodiments. This is not specifically limited in this embodiment of this application. The first communications device <NUM> includes a processing module <NUM> and a transceiver module <NUM>. The processing module <NUM> is configured to determine a capability identifier of the first communications device <NUM>, where the capability identifier of the first communications device <NUM> is one of one or more capability identifiers corresponding to the first communications device <NUM>. The transceiver module <NUM> is configured to send the capability identifier of the first communications device <NUM> to a second communications device, where the capability identifier of the first communications device <NUM> is used to determine a communication capability of the first communications device <NUM>.

Optionally, the capability identifier of the first communications device <NUM> includes at least one component of a first IMEI.

Optionally, that the capability identifier of the first communications device <NUM> includes at least one component of a first IMEI includes: the capability identifier of the first communications device <NUM> includes a TAC in the first IMEI; or the capability identifier of the first communications device <NUM> includes a TAC and a serial number SNR in the first IMEI; or the capability identifier of the first communications device <NUM> includes a TAC, an SNR, and an SVN in the first IMEI; or the capability identifier of the first communications device <NUM> includes a TAC, an SNR, and a CD in the first IMEI.

Optionally, at least one component of the capability identifier of the first communications device <NUM> is different from at least one component of a second IMEI, and the second IMEI is an IMEI of the first communications device <NUM>.

Optionally, the first IMEI is an IMEI used by a vendor to which the first communications device <NUM> belongs.

Optionally, the capability identifier of the first communications device <NUM> is different from a capability identifier of a third communications device, and the third communications device and the first communications device <NUM> are communications devices of different vendors.

Optionally, the transceiver module <NUM> is specifically configured to send a first RRC message or a first NAS message to the second communications device, where the first RRC message or the first NAS message includes the capability identifier of the first communications device <NUM>.

Optionally, the processing module <NUM> is specifically configured to: when the first communications device <NUM> supports reporting the capability identifier of the first communications device <NUM>, determine the capability identifier of the first communications device <NUM>.

Further, the transceiver module <NUM> is further configured to: when the first communications device <NUM> does not support reporting the capability identifier of the first communications device <NUM>, send indication information to the second communications device, where the indication information is used to indicate that the first communications device <NUM> does not support reporting the capability identifier of the first communications device <NUM>.

Optionally, that the transceiver module <NUM> is configured to send indication information to the second communications device includes: the transceiver module <NUM> is configured to send a second RRC message or a second NAS message to the second communications device, where the second RRC message or the second NAS message includes the indication information.

For function descriptions of corresponding functional modules, refer to all related content of the steps in the foregoing method embodiments.

In this embodiment, the first communications device <NUM> is presented by dividing the functional modules through integration. Herein, the "module" may be a specific ASIC, a circuit, a processor that executes one or more software or firmware programs, a memory, an integrated logic circuit, and/or another device that can provide the foregoing functions.

In a simple embodiment, a person skilled in the art may figure out that the first communications device <NUM> may be in the form shown in <FIG>.

For example, the processor <NUM> in <FIG> may invoke the computer executable instruction stored in the memory <NUM>, so that the first communications device <NUM> performs the communication capability reporting method in the foregoing method embodiments.

Specifically, functions and implementation processes of the processing module <NUM> and the transceiver module <NUM> in <FIG> may be implemented by the processor <NUM> in <FIG> by invoking the computer executable instruction stored in the memory <NUM>. Alternatively, a function and an implementation process of the processing module <NUM> in <FIG> may be implemented by the processor <NUM> in <FIG> by invoking the computer executable instruction stored in the memory <NUM>; and a function and an implementation process of the transceiver module <NUM> in <FIG> may be implemented by the communications interface <NUM> in <FIG>.

Optionally, when the first communications device <NUM> is a chip or a circuit, the memory <NUM> may be a storage unit in the chip or the circuit, for example, a register or a cache. Certainly, when the first communications device <NUM> is a terminal, the memory <NUM> may be a storage unit that is in the terminal and that is outside a chip. This is not specifically limited in this embodiment of this application.

The first communications device provided in this embodiment of this application may be configured to perform the foregoing communication capability reporting method. Therefore, for a technical effect that can be achieved by the first communications device, refer to the foregoing method embodiments.

For example, when the functional modules are divided through integration, <FIG> shows a schematic diagram of a structure of a second communications device <NUM>. The second communications device <NUM> may include the terminal in the foregoing embodiments, or may be a chip or a circuit in the terminal in the foregoing embodiments, or may be the access device (for example, the gNB) in the foregoing embodiments, or may be a chip system or a circuit in the access device in the foregoing embodiments. This is not specifically limited in this embodiment of this application. The second communications device <NUM> includes a receiving module <NUM> and a sending module <NUM>. The receiving module <NUM> is configured to receive a capability identifier of a first communications device that is sent by the first communications device, where the capability identifier of the first communications device is one of one or more capability identifiers corresponding to the first communications device. The sending module <NUM> is configured to send the capability identifier of the first communications device to a network device, where the capability identifier of the first communications device is used to determine a communication capability of the first communications device.

Optionally, the capability identifier of the first communications device includes at least one component of a first IMEI.

Optionally, that the capability identifier of the first communications device includes at least one component of a first IMEI includes: the capability identifier of the first communications device includes a TAC in the first IMEI; or the capability identifier of the first communications device includes a TAC and an SNR in the first IMEI; or the capability identifier of the first communications device includes a TAC, an SNR, and an SVN in the first IMEI; or the capability identifier of the first communications device includes a TAC, an SNR, and a CD in the first IMEI.

Optionally, at least one component of the capability identifier of the first communications device is different from at least one component of a second IMEI, and the second IMEI is an IMEI of the first communications device.

Optionally, the first IMEI is an IMEI used by a vendor to which the first communications device belongs.

Optionally, the capability identifier of the first communications device is different from a capability identifier of a third communications device, and the third communications device and the first communications device are communications devices of different vendors.

Optionally, the receiving module <NUM> is further configured to receive the communication capability of the first communications device that is sent by the network device.

Optionally, the receiving module <NUM> is further configured to receive a first message sent by the network device, where the first message is used to request the communication capability of the first communications device; the sending module <NUM> is further configured to send a second message to the first communications device, where the second message is used to request the communication capability of the first communications device; and the receiving module <NUM> is further configured to receive the communication capability of the first communications device that is sent by the first communications device.

Optionally, the first message in this embodiment of this application may carry the capability identifier of the first communications device. This is not specifically limited in this embodiment of this application.

Optionally, the second message in this embodiment of this application may carry the capability identifier of the first communications device. This is not specifically limited in this embodiment of this application.

Optionally, the sending module <NUM> is further configured to send the communication capability of the first communications device to the network device, so that the network device stores a correspondence between the capability identifier of the first communications device and the communication capability of the first communications device.

Optionally, the receiving module <NUM> is further configured to receive the capability identifier of the first communications device that is sent by the first communications device and that corresponds to the communication capability of the first communications device.

Optionally, the sending module <NUM> is further configured to send, to the network device, the communication capability of the first communications device, and the capability identifier of the first communications device that corresponds to the communication capability of the first communications device, so that the network device stores a correspondence between the capability identifier of the first communications device and the communication capability of the first communications device.

Optionally, that the receiving module <NUM> is configured to receive a capability identifier of a first communications device that is sent by the first communications device includes: the receiving module <NUM> is configured to: when the first communications device supports reporting the capability identifier of the first communications device, receive the capability identifier of the first communications device that is sent by the first communications device.

Optionally, the receiving module <NUM> is further configured to: when the first communications device does not support reporting the capability identifier of the first communications device, receive indication information sent by the first communications device, where the indication information is used to indicate that the first communications device does not support reporting the capability identifier of the first communications device.

Optionally, that the receiving module <NUM> is configured to receive indication information sent by the first communications device includes: the receiving module <NUM> is configured to receive a first RRC message or a first NAS message sent by the first communications device, where the first RRC message or the first NAS message includes the indication information.

Optionally, that the receiving module <NUM> is configured to receive a capability identifier of a first communications device that is sent by the first communications device includes: the receiving module <NUM> is configured to receive a second RRC message or a second NAS message sent by the first communications device, where the second RRC message or the second NAS message includes the capability identifier of the first communications device.

In this embodiment, the second communications device <NUM> is presented by dividing the functional modules through integration. Herein, the "module" may be a specific ASIC, a circuit, a processor that executes one or more software or firmware programs, a memory, an integrated logic circuit, and/or another device that can provide the foregoing functions.

In a simple embodiment, a person skilled in the art may figure out that the second communications device <NUM> may be in the form shown in <FIG>.

For example, the processor <NUM> in <FIG> may invoke the computer executable instruction stored in the memory <NUM>, so that the second communications device <NUM> performs the communication capability reporting method in the foregoing method embodiments.

Specifically, functions and implementation processes of the receiving module <NUM> and the sending module <NUM> in <FIG> may be implemented by the processor <NUM> in <FIG> by invoking the computer executable instruction stored in the memory <NUM>. Alternatively, functions and implementation processes of the receiving module <NUM> and the sending module <NUM> in <FIG> may be implemented by the communications interface <NUM> in <FIG>.

Optionally, when the second communications device <NUM> is a chip or a circuit, the memory <NUM> may be a storage unit in the chip or the circuit, for example, a register or a cache. Certainly, when the second communications device <NUM> is an access device, the memory <NUM> may be a storage unit that is in the access device and that is outside a chip. This is not specifically limited in this embodiment of this application.

The second communications device provided in this embodiment of this application may be configured to perform the foregoing communication capability reporting method. Therefore, for a technical effect that can be achieved by the second communications device, refer to the foregoing method embodiments.

All or some of the foregoing embodiments may be implemented by using software, hardware, firmware, or any combination thereof. When a software program is used to implement the embodiments, the embodiments may be implemented completely or partially in a form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the procedure or functions according to the embodiments of this application are all or partially generated. The computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable apparatuses. The computer instructions may be stored in a computer-readable storage medium or may be transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired (for example, a coaxial cable, an optical fiber, or a digital subscriber line (digital subscriber line, DSL)) or wireless (for example, infrared, radio, or microwave) manner. The computer-readable storage medium may be any usable medium accessible by a computer, or a data storage device, such as a server or a data center, integrating one or more usable media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, a DVD), a semiconductor medium (for example, a solid-state drive (solid state disk, SSD)), or the like.

Claim 1:
A first communications device (<NUM>), wherein the first communications device (<NUM>) being a first terminal device comprises a processing module (<NUM>) and a transceiver module (<NUM>);
the processing module is configured to determine a capability identifier of the first communications device, wherein the capability identifier of the first communications device is one of one or more capability identifiers corresponding to the first communications device; and
the transceiver module is configured to send the capability identifier of the first communications device to a second communications device (<NUM>), wherein the capability identifier of the first communications device (<NUM>) is used to determine a communication capability of the first communications device (<NUM>);
wherein the processing module is specifically configured to:
when the first communications device (<NUM>) supports reporting the capability identifier of the first communications device (<NUM>), determine the capability identifier of the first communications device (<NUM>) and send the capability identifier to the second communications device (<NUM>), and wherein
when the first communications device (<NUM>) does not support reporting the capability identifier of the first communications device (<NUM>), the first communications device (<NUM>) is configured to send indication information to the second communications device (<NUM>), wherein the indication information is used to indicate that the first communications device (<NUM>) does not support reporting the capability identifier of the first communications device (<NUM>).