CN112469033B - Reporting and receiving method of terminal capability, terminal and network equipment - Google Patents
Reporting and receiving method of terminal capability, terminal and network equipment Download PDFInfo
- Publication number
- CN112469033B CN112469033B CN201910848258.XA CN201910848258A CN112469033B CN 112469033 B CN112469033 B CN 112469033B CN 201910848258 A CN201910848258 A CN 201910848258A CN 112469033 B CN112469033 B CN 112469033B
- Authority
- CN
- China
- Prior art keywords
- terminal
- version information
- capability
- chip
- release time
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
- H04W8/24—Transfer of terminal data
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephone Function (AREA)
Abstract
The embodiment of the invention provides a reporting and receiving method of terminal capability, a terminal and network equipment. The reporting method of the terminal capability comprises the following steps: reporting the capability version information of the terminal to network equipment, wherein the capability version information of the terminal is different from standard version information supported by the terminal; the capability version information includes at least one of: a terminal manufacturer; terminal model; the terminal release time; terminal version information; terminal software version information; the release time of the terminal software version; terminal chip manufacturer; terminal chip model; terminal chip version information; the release time of the terminal chip; terminal chip software version time; and releasing time of the terminal chip software version. The scheme of the invention reports the capability version information to the network side through the terminal side, so that the network side can know the specific capability supported by the terminal, and accordingly, the terminal is configured correspondingly.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a method for reporting and receiving terminal capability, a terminal, and a network device.
Background
In the prior art, a standard defines terminal capability, the terminal reports the supported capability to a network according to the standard definition, and the network executes processes such as configuration or scheduling for the terminal.
Unpredictable burdens or restrictions on network or operator deployment may be imposed if there is unpredictable or undefined terminal capabilities due to terminal implementation. Typical cases are as follows:
(1) The terminal reports the standard definition capability, but the terminal realizes that only partial functions are supported
In LTE (long term evolution), a certain terminal reports support the B41 band (spanning 25xx to 26xx kHz), but actually only a part of the entire band (e.g., 2575 to 2635 kHz). When the terminal is configured with unsupported measurement objects (e.g. frequencies outside 2575-2635 kHz) this can lead to measurement failures and unpredictable delays. This cannot be avoided unless the network prohibits all reporting B41 enabled terminals from measuring frequencies outside 2575-2635 kHz.
(2) While the entire future set of functions is a mandatory capability, only a portion of the functions of the set of functions are selectively implemented at some stage.
In NR (new radio) some terminal functions are classified as one and the same capability, however a terminal may only implement part of the capability and not report other unrealized functions missing from it, bringing unpredictable limitations to the network, especially when the capability is mandatory. The network has to force exclusion of some operations or scheduling actions to ensure that the terminal is available in the network.
(3) Some preconditions for network deployment are regarded as a matter of course, without deciding on terminal-specific simplified implementations by pre-inspection.
EN-DC (dual connectivity of 5G NR with 4G radio access network) does not require synchronization between LTE and NR per se, but for some band combinations, e.g. 1.9GHz for LTE and 2.6GHz for NR, a certain terminal may use the same radio frequency and transceiver units and thus need to transmit or receive simultaneously. EN-DC network synchronization is required and the same uplink and downlink configuration is adopted when both LTE and NR bands are TDD (time division multiplexing).
Especially in a network, part of the terminals are inconsistent with the understanding of the network equipment due to the implementation of a certain version of the terminals or the implementation of a certain version of the used chips, and the situation often causes the degradation of the network performance or the degradation of the user experience. When other terminals do not have such problems, the network side either shifts to realize the realization of the terminals inconsistent with the understanding of the network device, so as to ensure that the terminals accessing the network still work, and specific constraint needs to be made on the network device, and as a result, the terminals which cannot have problems in other realization cannot achieve the best performance.
Disclosure of Invention
The invention provides a reporting and receiving method of terminal capability, a terminal and network equipment, which solve the problems that in the prior art, when terminal specific capability which cannot be known in advance by a network side occurs in a network, the network side cannot perform specific processing on the terminals so as to avoid performance degradation of the terminals in the network or other terminal involvement.
In order to solve the technical problems, the embodiment of the invention provides the following scheme:
a reporting method of terminal capability is applied to a terminal, and the method comprises the following steps:
reporting the capability version information of the terminal to network equipment or reporting the capability field which is not predefined, wherein the capability field is associated or defined to a preset implementation or flow or capability and reporting the capability version information of the terminal, and the capability version information of the terminal is different from standard version information supported by the terminal; the capability version information includes at least one of: a terminal manufacturer; terminal model; the terminal release time; terminal version information; terminal software version information; the release time of the terminal software version; terminal chip manufacturer; terminal chip model; terminal chip version information; the release time of the terminal chip; terminal chip software version information; and releasing time of the terminal chip software version.
Optionally, reporting the capability version information of the terminal to a network device, including:
when a terminal is randomly accessed or attached to a network, reporting capability version information of the terminal to network equipment; or alternatively, the process may be performed,
when the network equipment needs to know the capability version of the abnormal behavior of the terminal, the terminal reports the capability version information of the terminal to the network equipment through a random access or attachment flow; or alternatively, the process may be performed,
and if the terminal hopes that the network equipment knows the capability version of the abnormal behavior, the terminal reports the capability version information of the terminal to the network equipment through a random access or attachment flow.
Optionally, the abnormal behavior includes at least one of:
one of the characteristics of the terminal should be supported by default with respect to the network device, but is not actually supported and cannot inform the network device that the terminal is not supported;
one function or procedure in the terminal is implemented by the terminal with respect to the network device, differently from one understood by the network device.
The embodiment of the invention also provides a method for receiving the terminal capability, which is applied to the network equipment and comprises the following steps:
Receiving capability version information of a terminal, which is reported by the terminal and is different from standard version information supported by the terminal; the capability version information includes at least one of: a terminal manufacturer; terminal model; the terminal release time; terminal version information; terminal software version information; the release time of the terminal software version; terminal chip manufacturer; terminal chip model; terminal chip version information; the release time of the terminal chip; terminal chip software version information; and releasing time of the terminal chip software version.
Optionally, the method for receiving terminal capability further includes: and receiving at least model allocation code TAC information in an International Mobile Equipment Identity (IMEI) sent by core network equipment, wherein the IMEI is reported to the core network equipment by a terminal.
The embodiment of the invention also provides a device for reporting the terminal capability, which is applied to the terminal and comprises the following steps: the receiving and transmitting module is used for reporting the capability version information of the terminal or reporting the non-predefined capability field to the network equipment, wherein the capability field is associated or defined to a preset implementation or process or capability and reporting, and the capability version information of the terminal is different from the standard version information supported by the terminal; the capability version information includes at least one of: a terminal manufacturer; terminal model; the terminal release time; terminal version information; terminal software version information; the release time of the terminal software version; terminal chip manufacturer; terminal chip model; terminal chip version information; the release time of the terminal chip; terminal chip software version information; and releasing time of the terminal chip software version.
Optionally, the transceiver module is configured to report capability version information of the terminal to a network device when the transceiver module is randomly accessed or attached to a network; or when the network equipment needs to know the capacity version of the abnormal behavior of the terminal, the terminal reports the capacity version information of the terminal to the network equipment through a random access or attachment process; or if the terminal hopes that the network equipment knows the capability version to which the abnormal behavior belongs, the terminal reports the capability version information of the terminal to the network equipment through random access or attachment flow.
Optionally, the abnormal behavior includes at least one of:
one of the characteristics of the terminal should be supported by default with respect to the network device, but is not actually supported and cannot inform the network device that the terminal is not supported;
one function or procedure in the terminal is implemented by the terminal with respect to the network device, differently from one understood by the network device.
The embodiment of the invention also provides a terminal, which comprises:
the transceiver is used for reporting the capability version information of the terminal or reporting the non-predefined capability field to the network equipment, wherein the capability field is associated or defined to a preset implementation or process or capability and reporting, and the capability version information of the terminal is different from the standard version information supported by the terminal; the capability version information includes at least one of: a terminal manufacturer; terminal model; the terminal release time; terminal version information; terminal software version information; the release time of the terminal software version; terminal chip manufacturer; terminal chip model; terminal chip version information; the release time of the terminal chip; terminal chip software version information; and releasing time of the terminal chip software version.
Optionally, the transceiver is configured to report capability version information of the terminal to a network device when the transceiver is randomly accessed or attached to a network; or when the network equipment needs to know the capacity version of the abnormal behavior of the terminal, the terminal reports the capacity version information of the terminal to the network equipment through a random access or attachment process; or if the terminal hopes that the network equipment knows the capability version to which the abnormal behavior belongs, the terminal reports the capability version information of the terminal to the network equipment through random access or attachment flow.
Optionally, the abnormal behavior includes at least one of:
one of the characteristics of the terminal should be supported by default with respect to the network device, but is not actually supported and cannot inform the network device that the terminal is not supported;
one function or procedure in the terminal is implemented by the terminal with respect to the network device, differently from one understood by the network device.
The embodiment of the invention also provides a receiving device of terminal capability, which is applied to network equipment, and comprises:
the receiving and transmitting module is used for receiving the capability version information of the terminal, which is reported by the terminal and is different from the standard version information supported by the terminal; the capability version information includes at least one of: a terminal manufacturer; terminal model; the terminal release time; terminal version information; terminal software version information; the release time of the terminal software version; terminal chip manufacturer; terminal chip model; terminal chip version information; the release time of the terminal chip; terminal chip software version information; and releasing time of the terminal chip software version.
Optionally, the transceiver module is further configured to receive at least model assignment code TAC information in an international mobile equipment identity IMEI sent by a core network device, where the IMEI is reported to the core network device by a terminal.
The embodiment of the invention also provides a network device, which comprises:
the transceiver is used for receiving the capability version information of the terminal, which is reported by the terminal, wherein the capability version information of the terminal is different from the standard version information supported by the terminal; the capability version information includes at least one of: a terminal manufacturer; terminal model; the terminal release time; terminal version information; terminal software version information; the release time of the terminal software version; terminal chip manufacturer; terminal chip model; terminal chip version information; the release time of the terminal chip; terminal chip software version information; and releasing time of the terminal chip software version.
Optionally, the transceiver is further configured to receive at least model assignment code TAC information in an international mobile equipment identity IMEI sent by a core network device, where the IMEI is reported to the core network device by a terminal.
The embodiment of the invention also provides a communication device, which comprises: a processor, a memory storing a computer program which, when executed by the processor, performs the method as described above.
Embodiments of the present invention also provide a computer-readable storage medium comprising instructions which, when executed on a computer, cause the computer to perform a method as described above.
The scheme of the invention at least comprises the following beneficial effects:
according to the scheme, the terminal side reports the capability version information to the network side, so that the network side can know the specific capability supported by the terminal, and specific processing is performed on the terminals to avoid the terminal from degrading the performance in the network or interfering with other terminals, and the terminal can be correspondingly configured.
Drawings
FIG. 1 is a flow chart of a method for reporting terminal capability according to the present invention;
fig. 2 is a flow chart of a method for receiving terminal capability according to the present invention;
FIG. 3 is a schematic diagram of a terminal according to an embodiment of the present invention;
fig. 4 is a schematic architecture diagram of a network device according to the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present invention may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.
As shown in fig. 1, an embodiment of the present invention provides a method for reporting a terminal capability, which is applied to a terminal, where the method includes:
In this embodiment, the case that the terminal associates or defines the undefined capability field to the preset implementation or process or capability is that, in some cases, the terminal is not willing to let the network know the manufacturer to which the own or own used chip belongs, so that the terminal capability version information may not be reported, and the alternative method may be to predefine some reserved capability fields in the standard, where the capability fields do not need to be activated in advance, that is, do not need to be reported or even report do not represent any meaning, but when a problem occurs in the business process or the version development process, one or some of the reserved capability fields may be associated with a specific function or process, and the corresponding fields may be activated to be reported. The specific implementation method comprises the following steps: introducing a plurality of fields with activation indication or not, and if the activation indication information of one field indicates activation, the field indicates a specific meaning; if the activation indication information of a certain field indicates non-activation, the field has no specific meaning.
In an optional embodiment of the present invention, the method for reporting terminal capability may further include:
and step 12, receiving configuration information configured by the network equipment for the terminal.
In the embodiment of the invention, the terminal side reports the capability version information to the network side, so that the network side can know the specific capability supported by the terminal, and specific processing is performed on the terminals to avoid the performance degradation of the terminals in the network or the influence of other terminals, particularly the standardized defined partial capability or the standardized undefined capability, so that the terminal can be further configured correspondingly according to the capability version information of the terminal.
In an alternative embodiment of the present invention, step 11 may include:
step 111, when a terminal is randomly accessed or attached to a network, reporting capability version information of the terminal to network equipment; or alternatively, the process may be performed,
step 112, when the network device needs to know the capability version to which the terminal abnormal behavior belongs, the terminal reports the capability version information of the terminal to the network device through a random access or attachment process; or alternatively, the process may be performed,
in step 113, if the terminal wants the network device to know the capability version to which the abnormal behavior belongs, the terminal reports the capability version information of the terminal to the network device through a random access or attachment process.
Here, the abnormal behavior includes at least one of: the network configures a measurement object which is not supported by the terminal for the terminal; the network configures parameters, functions and/or processes which are not supported by the terminal for the terminal; no synchronization is performed between at least two networks in communication with the terminal. For example, a feature in a terminal should be supported by default with respect to the network device, but in fact not supported and cannot inform the network device that the terminal does not support the feature; one function or procedure in the terminal is implemented by the terminal with respect to the network device, differently from one understood by the network device.
In the above embodiment of the present invention, the configuration information includes at least one of: the network configures a measurement object supported by the terminal for the terminal; the network configures parameters, functions and/or processes supported by the terminal for the terminal; synchronization between at least two networks communicatively coupled to the terminal.
The following describes the specific implementation procedure of the above embodiment:
in one implementation, the method for reporting the terminal capability may include:
step 211, when the terminal randomly accesses or attaches to the network, or when the terminal does not support the configured measurement object, or when the terminal does not support the configured parameter, function or flow, or when the terminal finds that the network is not synchronized, reporting at least one of the following to the network: a terminal manufacturer; terminal model; the terminal release time; terminal version information; terminal software version information; the release time of the terminal software version;
Step 212, the network device receives at least one of the following items reported by the terminal: a terminal manufacturer; terminal model; the terminal release time; terminal version information; terminal software version information; the release time of the terminal software version;
step 213, the network equipment reports according to the terminal manufacturer; terminal model; the terminal release time; terminal version information; terminal software version information; at least one of release time of terminal software version, determining the capability supported by the terminal, configuring the supported measuring object for the terminal, or configuring the supported parameter, function or flow, or synchronizing the dual-connection networks.
In another implementation, the method for reporting the terminal capability may include:
step 311, when the terminal randomly accesses or attaches to the network, or when the terminal does not support the configured measurement object, or when the terminal does not support the configured parameter, function or flow, or when the terminal finds that the network is not synchronized, reporting at least one of the following to the network: terminal chip model; terminal chip version information; the release time of the terminal chip; terminal chip software version information; the release time of the terminal chip software version;
Step 312, the network receives at least one of the following reported by the terminal: terminal chip model; terminal chip version information; the release time of the terminal chip; terminal chip software version information; the release time of the terminal chip software version;
step 313, the network side reports the terminal chip model according to the terminal side; terminal chip version information; the release time of the terminal chip; terminal chip software version information; at least one of the release time of the terminal chip software version, the capability supported by the terminal is determined, and the supported measuring object is configured for the terminal, or the supported parameter, function or flow is configured, or the synchronization between the dual-connection networks is performed.
In the above embodiment of the present invention, the terminal mandatory capability is defined in the standard, which means that the network device considers this mandatory capability, and the terminal must implement, so that the network is correspondingly configured or scheduled based on such capability; or a specific procedure is defined in the standard, which means that the network device will consider that it should be treated as such for the terminal; however, when the capability or flow of the implementation of the terminal is inconsistent with the understanding of the network device, some errors or inefficiency will occur, but these problems often exist only in specific implementation versions, or in specific versions, because once the problem is found, it is generally well-repaired in subsequent versions, so as to ensure that the implementation given in the terminal is consistent with the implementation of the understanding of the network device. These versions may be terminal versions, chip versions used by the terminal, even version information related to the update of the air interface capability of the terminal, such as the software version of the terminal. But the version information here is reported with the version information of the standard that the standard has now supported, since the version information here helps the network side to identify a specific terminal, not just a terminal of a certain standard version. This capability is also different from the reporting of IMEI (International Mobile Equipment Identity ) or IMEISV (International Mobile station Equipment Identity and Software Version number, national mobile terminal equipment identity and software version) in existing mechanisms, because IMEI/IMEISV, although usable to distinguish a specific terminal, is only available to the core network and does not allow the base station to retain and use this information, since IMEI/IMEISV also characterizes the identity information of the terminal. Thus, after a problem in terminal implementation is found in a version, if the network device can use the version information, the network device can identify a specific terminal with a problem (including that the terminal capability or implementation flow is inconsistent with the understanding of the network device), so that the terminal can be specifically treated to reduce the influence of the problem on the terminal and the influence on other normal terminals (that the terminal capability or implementation flow is completely consistent with the understanding of the network device).
The IMEI is an abbreviation of international mobile equipment identity, an international mobile equipment identification is an "electronic serial number" consisting of 15 digits, which corresponds to each handset one-to-one, and the code is unique worldwide: the first 6 digits (TAC) are "model approval numbers", typically representing model, the next 2 digits (FAC) are "final assembly numbers", typically representing the place of production (defined in the standard as broad TAC, meaning tac+fac written here), the next 6 digits (SNR) are "serial numbers", typically representing the production sequence number, and the last 1 digits (SP) are typically "0", as check codes, and are currently ready for use. The IMEI code is attached to a sign on the back of the mobile phone and is read and written in the memory of the mobile phone. It is also the "profile" and "identification number" of the handset at the manufacturer, so this information is not allowed to be fully revealed to the base station for security reasons. However, in order to solve the foregoing problem, the present solution may also require that the core network device at least can notify TAC and/or FAC information, which may represent a model in the IMEI of the core network device, to the network device (e.g. a base station).
According to the embodiment of the invention, the terminal side reports the capability version information to the network side, so that the network side can know the specific capability supported by the terminal, the network side performs specific treatment on the terminals to avoid the performance degradation of the terminals in the network or the connection of other terminals, particularly the standardized defined partial capability or the standardized undefined capability, thereby carrying out corresponding configuration on the terminals according to the capability version information of the terminals and avoiding the burden or limitation on the network caused by unpredictable or undefined terminal capability.
As shown in fig. 2, the embodiment of the present invention further provides a method for receiving terminal capability, which is applied to a network device, and the method includes:
In an optional embodiment of the present invention, the method for receiving terminal capability may further include:
and step 22, sending configuration information of the terminal configuration to the terminal.
Optionally, the configuration information includes at least one of: the network configures a measurement object supported by the terminal for the terminal; the network configures parameters, functions and/or processes supported by the terminal for the terminal; synchronization between at least two networks communicatively coupled to the terminal.
In an optional embodiment of the present invention, the method for receiving terminal capability may further include:
step 23, receiving at least model assignment code TAC information in International Mobile Equipment Identity (IMEI) sent by a core network device, where the IMEI is reported to the core network device by a terminal.
According to the embodiment of the invention, the specific capability supported by the terminal can be known through the capability version information reported by the network side receiving terminal, the network side performs specific treatment on the terminal so as to avoid the terminal from degrading the performance in the network or interfering with other terminals, and the terminal is correspondingly configured according to the capability version information of the terminal, so that the burden or limitation of unpredictable or undefined terminal capability on the network is avoided.
The embodiment of the invention also provides a reporting device of the terminal capability, which is applied to the terminal and comprises the following steps: the receiving and transmitting module is used for reporting the capability version information of the terminal or reporting the non-predefined capability field to the network equipment, wherein the capability field is associated or defined to a preset implementation or flow or capability and reporting, and the capability version information of the terminal is allowed to be known or acquired by the network equipment and is different from the standard version information supported by the terminal; the capability version information includes at least one of: a terminal manufacturer; terminal model; the terminal release time; terminal version information; terminal software version information; the release time of the terminal software version; terminal chip manufacturer; terminal chip model; terminal chip version information; the release time of the terminal chip; terminal chip software version information; and releasing time of the terminal chip software version.
Optionally, the transceiver module is configured to report capability version information of the terminal to a network device when the transceiver module is randomly accessed or attached to a network; or when the network equipment needs to know the capacity version of the abnormal behavior of the terminal, the terminal reports the capacity version information of the terminal to the network equipment through a random access or attachment process; or if the terminal hopes that the network equipment knows the capability version to which the abnormal behavior belongs, the terminal reports the capability version information of the terminal to the network equipment through random access or attachment flow.
Optionally, the abnormal behavior includes at least one of:
one of the characteristics of the terminal should be supported by default with respect to the network device, but is not actually supported and cannot inform the network device that the terminal is not supported;
one function or procedure in the terminal is implemented by the terminal with respect to the network device, differently from one understood by the network device.
Optionally, the transceiver module is further configured to receive configuration information configured by the network device for a terminal.
Optionally, the configuration information includes at least one of: the network configures a measurement object supported by the terminal for the terminal; the network configures parameters, functions and/or processes supported by the terminal for the terminal; synchronization between at least two networks communicatively coupled to the terminal.
It should be noted that the device is a device corresponding to the method shown in fig. 1, and all implementation manners in the method embodiment are applicable to the device embodiment, so that the same technical effects can be achieved.
As shown in fig. 3, an embodiment of the present invention further provides a terminal 30, including:
a transceiver 31, configured to report capability version information of the terminal to a network device or report an undefined capability field, where the capability field is associated with or defined to a preset implementation or flow or capability and reported, and the capability version information of the terminal is allowed to be known or acquired by the network device and is different from standard version information supported by the terminal; the capability version information includes at least one of: a terminal manufacturer; terminal model; the terminal release time; terminal version information; terminal software version information; the release time of the terminal software version; terminal chip manufacturer; terminal chip model; terminal chip version information; the release time of the terminal chip; terminal chip software version information; and releasing time of the terminal chip software version.
Optionally, the transceiver 31 is configured to report capability version information of the terminal to a network device when the terminal is randomly accessed or attached to a network; or when the network equipment needs to know the capacity version of the abnormal behavior of the terminal, the terminal reports the capacity version information of the terminal to the network equipment through a random access or attachment process; or if the terminal hopes that the network equipment knows the capability version to which the abnormal behavior belongs, the terminal reports the capability version information of the terminal to the network equipment through random access or attachment flow.
Optionally, the abnormal behavior includes at least one of:
one of the characteristics of the terminal should be supported by default with respect to the network device, but is not actually supported and cannot inform the network device that the terminal is not supported;
one function or procedure in the terminal is implemented by the terminal with respect to the network device, differently from one understood by the network device.
Optionally, the transceiver 31 is further configured to receive configuration information configured by the network device for a terminal.
Optionally, the configuration information includes at least one of: the network configures a measurement object supported by the terminal for the terminal; the network configures parameters, functions and/or processes supported by the terminal for the terminal; synchronization between at least two networks communicatively coupled to the terminal.
It should be noted that, the terminal is a terminal corresponding to the method shown in fig. 1, and all implementation manners in the method embodiment are applicable to the embodiment of the terminal, so that the same technical effects can be achieved. The terminal may further include: a processor 32, a memory 33; the transceiver 31 and the processor 32, and the transceiver 31 and the memory 33 may be connected through a bus interface, the functions of the transceiver 31 may be implemented by the processor 32, and the functions of the processor 32 may be implemented by the transceiver 31.
The embodiment of the invention also provides a receiving device of terminal capability, which is applied to network equipment, and comprises: the receiving and transmitting module is used for receiving the capability version information of the terminal, which is reported by the terminal, wherein the capability version information of the terminal is allowed to be known or acquired by network equipment and is different from standard version information supported by the terminal; the capability version information includes at least one of: a terminal manufacturer; terminal model; the terminal release time; terminal version information; terminal software version information; the release time of the terminal software version; terminal chip manufacturer; terminal chip model; terminal chip version information; the release time of the terminal chip; terminal chip software version information; and releasing time of the terminal chip software version.
Optionally, the transceiver module is further configured to receive at least model assignment code TAC information in an international mobile equipment identity IMEI sent by a core network device, where the IMEI is reported to the core network device by a terminal.
It should be noted that the device is a device corresponding to the method shown in fig. 2, and all implementation manners in the method embodiment are applicable to the device embodiment, so that the same technical effects can be achieved.
As shown in fig. 4, an embodiment of the present invention further provides a network device 40, including:
a transceiver 41, configured to receive capability version information of a terminal reported by the terminal, where the capability version information of the terminal is allowed to be known or acquired by a network device and is different from standard version information supported by the terminal; the capability version information includes at least one of: a terminal manufacturer; terminal model; the terminal release time; terminal version information; terminal software version information; the release time of the terminal software version; terminal chip manufacturer; terminal chip model; terminal chip version information; the release time of the terminal chip; terminal chip software version information; and releasing time of the terminal chip software version.
Optionally, the transceiver 41 is further configured to receive at least model assignment code TAC information in an international mobile equipment identity IMEI sent by a core network device, where the IMEI is reported to the core network device by a terminal.
Optionally, the transceiver 41 is further configured to send configuration information of the terminal configuration to the terminal.
Optionally, the configuration information includes at least one of: the network configures a measurement object supported by the terminal for the terminal; the network configures parameters, functions and/or processes supported by the terminal for the terminal; synchronization between at least two networks communicatively coupled to the terminal.
It should be noted that, the network device is a network device corresponding to the method shown in fig. 2, and all the implementation manners in the method embodiment are applicable to the embodiment of the network device, so that the same technical effects can be achieved. The network device may further include: a processor 42, a memory 43; the transceiver 41 and the processor 42, and the transceiver 41 and the memory 43 may be connected through a bus interface, and the functions of the transceiver 41 may be implemented by the processor 42, and the functions of the processor 42 may also be implemented by the transceiver 41.
The embodiment of the invention also provides a communication device, which comprises: a processor, a memory storing a computer program which, when executed by the processor, performs the method as described above with reference to fig. 1 or fig. 2. All the implementation manners in the method embodiment are applicable to the embodiment, and the same technical effects can be achieved.
Embodiments of the present invention also provide a computer-readable storage medium comprising instructions which, when executed on a computer, cause the computer to perform the method described above with reference to fig. 1 or fig. 2. All the implementation manners in the method embodiment are applicable to the embodiment, and the same technical effects can be achieved.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown 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 may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk, etc.
Furthermore, it should be noted that in the apparatus and method of the present invention, it is apparent that the components or steps may be disassembled and/or assembled. Such decomposition and/or recombination should be considered as equivalent aspects of the present invention. Also, the steps of performing the series of processes described above may naturally be performed in chronological order in the order of description, but are not necessarily performed in chronological order, and some steps may be performed in parallel or independently of each other. It will be appreciated by those of ordinary skill in the art that all or any of the steps or components of the methods and apparatus of the present invention may be implemented in hardware, firmware, software, or a combination thereof in any computing device (including processors, storage media, etc.) or network of computing devices, as would be apparent to one of ordinary skill in the art after reading this description of the invention.
The object of the invention can thus also be achieved by running a program or a set of programs on any computing device. The computing device may be a well-known general purpose device. The object of the invention can thus also be achieved by merely providing a program product containing program code for implementing said method or apparatus. That is, such a program product also constitutes the present invention, and a storage medium storing such a program product also constitutes the present invention. It is apparent that the storage medium may be any known storage medium or any storage medium developed in the future. It should also be noted that in the apparatus and method of the present invention, it is apparent that the components or steps may be disassembled and/or assembled. Such decomposition and/or recombination should be considered as equivalent aspects of the present invention. The steps of executing the series of processes may naturally be executed in chronological order in the order described, but are not necessarily executed in chronological order. Some steps may be performed in parallel or independently of each other.
While the foregoing is directed to the preferred embodiments of the present invention, it will be appreciated by those skilled in the art that various modifications and adaptations can be made without departing from the principles of the present invention, and such modifications and adaptations are intended to be comprehended within the scope of the present invention.
Claims (11)
1. The method for reporting the terminal capability is characterized by being applied to a terminal, and comprises the following steps:
reporting the capability version information of the terminal to network equipment or reporting an undefined capability field, wherein the capability field is associated with or defined to a preset implementation or process or capability, and the capability version information of the terminal is different from standard version information supported by the terminal; the capability version information includes at least one of: a terminal manufacturer; the terminal release time; terminal version information; terminal software version information; the release time of the terminal software version; terminal chip manufacturer; terminal chip model; terminal chip version information; the release time of the terminal chip; terminal chip software version information; and releasing time of the terminal chip software version.
2. The method for reporting the capability of the terminal according to claim 1, wherein reporting the capability version information of the terminal to the network device comprises:
When a terminal is randomly accessed or attached to a network, reporting capability version information of the terminal to network equipment; or alternatively, the process may be performed,
when the network equipment needs to know the capability version of the abnormal behavior of the terminal, the terminal reports the capability version information of the terminal to the network equipment through a random access or attachment flow; or alternatively, the process may be performed,
and if the terminal hopes that the network equipment knows the capability version of the abnormal behavior, the terminal reports the capability version information of the terminal to the network equipment through a random access or attachment flow.
3. The method for reporting terminal capability according to claim 2, wherein the abnormal behavior includes at least one of:
one of the characteristics of the terminal should be supported by default with respect to the network device, but is not actually supported and cannot inform the network device that the terminal is not supported;
one function or procedure in the terminal is implemented by the terminal with respect to the network device, differently from one understood by the network device.
4. A method for receiving terminal capability, applied to a network device, the method comprising:
receiving capability version information of a terminal, which is reported by the terminal and is different from standard version information supported by the terminal; the capability version information includes at least one of: a terminal manufacturer; the terminal release time; terminal version information; terminal software version information; the release time of the terminal software version; terminal chip manufacturer; terminal chip model; terminal chip version information; the release time of the terminal chip; terminal chip software version information; and releasing time of the terminal chip software version.
5. The method for receiving terminal capability according to claim 4, further comprising:
and receiving at least model allocation code TAC information in an International Mobile Equipment Identity (IMEI) sent by core network equipment, wherein the IMEI is reported to the core network equipment by a terminal.
6. A reporting device for terminal capability, applied to a terminal, the device comprising:
the receiving and transmitting module is used for reporting the capability version information of the terminal or reporting the non-predefined capability field to the network equipment, wherein the capability field is associated with or defines a preset implementation or process or capability, and the capability version information of the terminal is different from the standard version information supported by the terminal; the capability version information includes at least one of: a terminal manufacturer; the terminal release time; terminal version information; terminal software version information; the release time of the terminal software version; terminal chip manufacturer; terminal chip model; terminal chip version information; the release time of the terminal chip; terminal chip software version information; and releasing time of the terminal chip software version.
7. A terminal, comprising:
the transceiver is used for reporting the capability version information of the terminal or reporting the non-predefined capability field to the network equipment, wherein the capability field is associated or defined to a preset implementation or process or capability, and the capability version information of the terminal is different from the standard version information supported by the terminal; the capability version information includes at least one of: a terminal manufacturer; the terminal release time; terminal version information; terminal software version information; the release time of the terminal software version; terminal chip manufacturer; terminal chip model; terminal chip version information; the release time of the terminal chip; terminal chip software version information; and releasing time of the terminal chip software version.
8. A terminal-capable receiving apparatus for use with a network device, the apparatus comprising:
the receiving and transmitting module is used for receiving the capability version information of the terminal, which is reported by the terminal and is different from the standard version information supported by the terminal; the capability version information includes at least one of: a terminal manufacturer; the terminal release time; terminal version information; terminal software version information; the release time of the terminal software version; terminal chip manufacturer; terminal chip model; terminal chip version information; the release time of the terminal chip; terminal chip software version information; and releasing time of the terminal chip software version.
9. A network device, comprising:
the transceiver is used for receiving the capability version information of the terminal, which is reported by the terminal, wherein the capability version information of the terminal is different from the standard version information supported by the terminal; the capability version information includes at least one of: a terminal manufacturer; the terminal release time; terminal version information; terminal software version information; the release time of the terminal software version; terminal chip manufacturer; terminal chip model; terminal chip version information; the release time of the terminal chip; terminal chip software version information; and releasing time of the terminal chip software version.
10. A communication device, comprising: a processor, a memory storing a computer program which, when executed by the processor, performs the method of any one of claims 1 to 3, or the method of any one of claims 4 to 5.
11. A computer readable storage medium comprising instructions which, when executed by a computer, cause the computer to perform the method of any one of claims 1 to 3 or the method of any one of claims 4 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910848258.XA CN112469033B (en) | 2019-09-09 | 2019-09-09 | Reporting and receiving method of terminal capability, terminal and network equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910848258.XA CN112469033B (en) | 2019-09-09 | 2019-09-09 | Reporting and receiving method of terminal capability, terminal and network equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112469033A CN112469033A (en) | 2021-03-09 |
| CN112469033B true CN112469033B (en) | 2023-05-05 |
Family
ID=74807275
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910848258.XA Active CN112469033B (en) | 2019-09-09 | 2019-09-09 | Reporting and receiving method of terminal capability, terminal and network equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112469033B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117062050A (en) * | 2022-05-06 | 2023-11-14 | 中兴通讯股份有限公司 | Image information acquisition and transmission method, device, management unit and network element |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101557634A (en) * | 2008-04-09 | 2009-10-14 | 大唐移动通信设备有限公司 | Method, system and device for reporting and using user equipment capability information |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104765591A (en) * | 2014-01-02 | 2015-07-08 | 腾讯科技（深圳）有限公司 | Method and system for updating software configuration parameter, and terminal server |
| CN105636087B (en) * | 2014-10-31 | 2020-09-04 | 中国移动通信集团公司 | Method and device for distributing network configuration parameters |
| CN108683487B (en) * | 2018-01-12 | 2019-06-11 | 华为技术有限公司 | A kind of method, apparatus and system for terminal unit ability transmission |
-
2019
- 2019-09-09 CN CN201910848258.XA patent/CN112469033B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101557634A (en) * | 2008-04-09 | 2009-10-14 | 大唐移动通信设备有限公司 | Method, system and device for reporting and using user equipment capability information |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112469033A (en) | 2021-03-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11464041B2 (en) | Network node, user device and methods thereof | |
| CN110557835B (en) | Data transmission method, communication device, and storage medium | |
| US20200196289A1 (en) | Data transmission method, network device, and terminal device | |
| CN111641476A (en) | Method and terminal for data transmission | |
| CN110430619B (en) | Narrow-band communication method and device based on cellular network | |
| EP3739913A1 (en) | Data transmission method, related devices, and system | |
| CN111132173B (en) | Uplink signal transmission method, terminal and network equipment | |
| EP3691372B1 (en) | Sps activation determination methods and user equipment | |
| JP7227987B2 (en) | Inter-gNB Xn signaling of NR TDD radio frame structure and CLI sensitivity | |
| CN112469033B (en) | Reporting and receiving method of terminal capability, terminal and network equipment | |
| CN108282323B (en) | Receiving node, transmitting node and communication method | |
| EP4021110A1 (en) | Control channel detection capability determining method and apparatus, device, and medium | |
| CN115002907A (en) | Resource scheduling method and communication device | |
| US11368266B2 (en) | Uplink signal transmission method, and device | |
| CN111867101B (en) | Data transmission method, network equipment, terminal, storage medium and electronic equipment | |
| EP3979748A1 (en) | Communication method and apparatus based on unlicensed spectrum, and storage medium | |
| CN111918397B (en) | Channel monitoring method and device | |
| CN110024469B (en) | Method, device and system for configuring synchronous broadcast block and storage medium | |
| CN111149399B (en) | Terminal, communication method, and base station device | |
| CN107295686B (en) | Interference processing method, related equipment and interference processing system | |
| CN110383922B (en) | Acknowledgement of transmissions in wireless communication system uplink | |
| US20220337371A1 (en) | Method for srs bundling in nru | |
| WO2021239123A1 (en) | Control channels in unlicensed spectrum | |
| US20220103314A1 (en) | Method executed by user equipment, method executed by base station, user equipment, and base station | |
| CN116419404A (en) | Irregular bandwidth configuration method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |