WO2019192439A1 - 通信能力上报方法、设备及系统 - Google Patents

通信能力上报方法、设备及系统 Download PDF

Info

Publication number
WO2019192439A1
WO2019192439A1 PCT/CN2019/080903 CN2019080903W WO2019192439A1 WO 2019192439 A1 WO2019192439 A1 WO 2019192439A1 CN 2019080903 W CN2019080903 W CN 2019080903W WO 2019192439 A1 WO2019192439 A1 WO 2019192439A1
Authority
WO
WIPO (PCT)
Prior art keywords
communication device
capability
communication
capability identifier
terminal
Prior art date
Application number
PCT/CN2019/080903
Other languages
English (en)
French (fr)
Inventor
王达
王键
王洪跃
刘海涛
Original Assignee
华为技术有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP19780912.2A priority Critical patent/EP3761688A4/en
Publication of WO2019192439A1 publication Critical patent/WO2019192439A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/22Processing or transfer of terminal data, e.g. status or physical capabilities
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/22Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24Transfer of terminal data
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W60/00Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a communication capability reporting method, device, and system.
  • RRC radio resource control
  • eNB evolved NodeB
  • LTE long term evolution
  • Scene 1 The terminal transitions from an idle state to a connected state
  • Scenario 2 The terminal switches from one eNB to another eNB;
  • Scenario 3 The terminal is initially registered to the network.
  • the MME can send the communication capability of the terminal to the eNB because the communication capability of the terminal is stored in the mobility management entity (MME). The terminal does not need to report the communication capability of the terminal.
  • the MME sends a capability report request to the terminal, so that the terminal reports the communication capability of the terminal.
  • the communication capability of the terminal is reported. There are many parameters required, and the amount of reported data is much larger than that of LTE. Therefore, the prior art proposes a method for associating the communication capability of the terminal with the capability identification of the terminal, so that the access device or the network device is based on the capability of the terminal. Identification, you can determine the communication capabilities of the terminal.
  • the capability identifier of the terminal is determined according to an international mobile equipment identity (IMEI) of the terminal, and may be, for example, a type assignment code (type) in an international mobile equipment identity (IMEI) of the terminal. Allocation code, TAC) and software version number (SVN).
  • the above solution has the following problem: if the software of the terminal is refreshed, the hardware does not change (that is, the IMSI of the terminal does not change), but the communication capability of the terminal changes, and the capability identification of the terminal does not occur at this time. Changes, so the terminal will not be able to update its communication capabilities. For example, when the software version upgrade of the terminal causes the communication capability of the terminal to be changed; or, for example, the global certification forum (GCF)/protocol authentication/modification software version causes the communication capability of the terminal to occur. In the case of a change; or, in the case where the software maintenance of the terminal causes a change in the communication capability of the terminal, etc., if the terminal capability reporting method is used, the terminal cannot update its communication capability.
  • GCF global certification forum
  • how to provide a communication capability reporting method is such that when the communication capability of the communication device is associated with the capability identification of the communication device, the communication device can update its communication capability in time, which is a technical problem to be solved.
  • the embodiment of the present application provides a communication capability reporting method, device, and system, so that the communication device can update its communication capability in time when the communication capability of the communication device is associated with the capability identification of the communication device.
  • the first aspect provides a method for reporting a communication capability, where the first communication device determines a capability identifier of the first communication device, where the capability identifier of the first communication device is a corresponding one of the first communication device or One of the plurality of capability identifiers; the first communication device transmits the capability identifier of the first communication device to the second communication device, the capability identifier of the first communication device is used to determine the communication capability of the first communication device. Based on the solution, the capability of the first communication device sent by the first communication device to the second communication device is identified as one of the one or more capability identifiers corresponding to the first communication device.
  • different capability identifiers may be used for the first communication device, so in the case of associating the communication capability of the first communication device with the capability identifier of the first communication device, the first communication The device may update its communication capabilities in time using the capability identification determined from one or more capability identifiers corresponding to the first communication device.
  • the capability identification of the first communication device includes at least one component of the first international mobile device identification code IMEI.
  • the capability identifier of the first communications device includes a type allocation code TAC in the first IMEI; or the capability identifier of the first communications device includes a TAC and a sequence number SNR in the first IMEI; or, the first The capability identifier of the communication device includes a TAC, an SNR, and a software version number SVN in the first IMEI; or the capability identifier of the first communication device includes a TAC, an SNR, and a verification code CD in the first IMEI, etc.
  • the application examples are not specifically limited thereto.
  • At least one component of the capability identifier of the first communication device is different from at least one component of the second IMEI, wherein the second IMEI is an IMEI of the first communication device.
  • the capability identification of the first communication device can be distinguished from the IMEI of the first communication device.
  • the first IMEI is an IMEI used by a vendor to which the first communication device belongs.
  • the second communication device or the network device in the core network can distinguish communication devices of different vendors according to the capability identifier of the communication device, thereby achieving differentiated competition.
  • the capability identifier of the first communication device is different from the capability identifier of the third communication device, wherein the third communication device and the first communication device are communication devices of different vendors. That is to say, the capability identifiers of the communication devices maintained by different vendors are different, so that the second communication device or the network devices in the core network can distinguish communication devices of different vendors according to the capability identifier of the communication device, thereby achieving differentiated competition.
  • the first communications device sends the capability identifier of the first communications device to the second communications device, including: the first communications device sends a first radio resource control RRC message or the first communications device to the second communications device
  • the non-access stratum NAS message, the first RRC message or the first NAS message includes a capability identifier of the first communications device. That is to say, the first communication device can report the capability identifier of the first communication device to the second communication device by using an existing RRC message or a NAS message, without adding new signaling, thereby saving system resources.
  • the first communications device determines the capability identifier of the first communications device, including: in the case that the first communications device supports reporting the capability identifier of the first communications device, the first communications device Determining the capability identification of the first communication device. In this way, the solution cannot be implemented when the first communication device does not support the capability identification of the first communication device.
  • the first communication device in a case where the first communication device does not support reporting the capability identifier of the first communication device, the first communication device sends the indication information to the second communication device, and the indication is used by the second communication device Information is sent to network devices in the core network.
  • the indication information is used to indicate that the first communication device does not support the capability identifier for reporting the first communication device.
  • the network device in the core network can learn that the first communication device does not support the capability identification of the first communication device, so that the communication capability of the corresponding first communication device is not searched according to the capability identifier of the first communication device.
  • the communication capability of the first communication device is queried to the first communication device, so that the first communication device reports the The communication capability of the first communication device. That is to say, based on the scheme, it is possible to implement reporting of the communication capability of the communication device that does not support the capability identification of the communication device.
  • the first communications device sends the indication information to the second communications device, including: the first communications device sends 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. That is to say, the first communication device can send the indication information to the second communication device by using an existing RRC message or a NAS message, without adding new signaling, thereby saving system resources.
  • the second aspect provides a method for reporting a communication capability, where the second communication device receives the capability identifier of the first communication device that is sent by the first communication device, where the capability identifier of the first communication device is the first One of the one or more capability identifiers corresponding to the communication device; the second communication device sends the capability identifier of the first communication device to the network device, where the capability identifier of the first communication device is used to determine the first communication device Communication ability. Based on the solution, the capability of the first communication device sent by the first communication device to the second communication device is identified as one of the one or more capability identifiers corresponding to the first communication device.
  • different capability identifiers may be used for the first communication device, so in the case of associating the communication capability of the first communication device with the capability identifier of the first communication device, the first communication The device may update its communication capabilities in time using the capability identification determined from one or more capability identifiers corresponding to the first communication device.
  • the capability identification of the first communication device includes at least one component of the first international mobile device identification code IMEI.
  • the capability identifier of the first communications device includes a type allocation code TAC in the first IMEI; or the capability identifier of the first communications device includes a TAC and a sequence number SNR in the first IMEI; or, the first The capability identifier of the communication device includes a TAC, an SNR, and a software version number SVN in the first IMEI; or the capability identifier of the first communication device includes a TAC, an SNR, and a verification code CD in the first IMEI, etc.
  • the application examples are not specifically limited thereto.
  • At least one component of the capability identifier of the first communication device is different from at least one component of the second IMEI, wherein the second IMEI is an IMEI of the first communication device.
  • the capability identification of the first communication device can be distinguished from the IMEI of the first communication device.
  • the first IMEI is an IMEI used by a vendor to which the first communication device belongs.
  • the second communication device or the network device in the core network can distinguish communication devices of different vendors according to the capability identifier of the communication device, thereby achieving differentiated competition.
  • the capability identifier of the first communication device is different from the capability identifier of the third communication device, wherein the third communication device and the first communication device are communication devices of different vendors. That is to say, the capability identifiers of the communication devices maintained by different vendors are different, so that the second communication device or the network devices in the core network can distinguish communication devices of different vendors according to the capability identifier of the communication device, thereby achieving differentiated competition.
  • the communication capability reporting method provided by the embodiment of the present application may further include: receiving, by the second communications device, the communication capability of the first communications device that is sent by the network device. That is, the communication capability of the first communication device corresponding to the capability identifier of the first communication device may be stored in the network device, and after the network device acquires the capability identifier of the first communication device, the network device may perform the query according to the capability identifier of the first communication device. The communication capability of the first communication device, in turn, transmits the communication capability of the first communication device to the second communication device.
  • the communication capability reporting method provided by the embodiment of the present application may further include: receiving, by the second communications device, the first message sent by the network device, where the first message is used to request the communication capability of the first communications device.
  • the second communication device sends a second message to the first communication device, the second message is used to request the communication capability of the first communication device; and the second communication device receives the communication capability of the first communication device sent by the first communication device . That is, if the communication capability of the first communication device corresponding to the capability identifier of the first communication device is not stored in the network device, the network device may query the first communication device for the communication capability of the first communication device by using the second communication device. The first communication device can report the communication capability of the first communication device to the second network device.
  • the first message in the embodiment of the present application may carry the capability identifier of the first communication device, which is not specifically limited in this embodiment.
  • the second message in the embodiment of the present application may carry the capability identifier of the first communication device, which is not specifically limited in this embodiment of the present application.
  • the communication capability reporting method provided by the embodiment of the present application may further include: the second communication device sends the communication capability of the first communication device to the network device, where the network device stores the first communication device A correspondence between the capability identifier and the communication capability of the first communication device. In this way, if the first communication device or the other communication device reports the capability identifier, the network device can directly determine the corresponding capability identifier according to the capability identifier and the stored correspondence between the capability identifier and the communication capability. Communication ability.
  • the communication capability reporting method provided by the embodiment of the present application may further include: the second communication device receiving, by the first communication device, the capability identifier of the first communication device corresponding to the communication capability of the first communication device . That is, in the embodiment of the present application, when the first communication device reports the communication capability, the communication capability can be reported together with the capability identifier, so that the second communication device or the subsequent network device can know which communication identifier the communication capability is. Corresponding communication capabilities.
  • the communication capability reporting method provided by the embodiment of the present application may further include: the second communication device sends, to the network device, a communication capability of the first communication device and a communication capability corresponding to the communication capability of the first communication device.
  • a capability identifier of a communication device wherein the network device stores a correspondence between a capability identifier of the first communication device and a communication capability of the first communication device. In this way, if the first communication device or the other communication device reports the capability identifier, the network device can directly determine the corresponding capability identifier according to the capability identifier and the stored correspondence between the capability identifier and the communication capability. Communication ability.
  • the second communications device receives the capability identifier of the first communications device sent by the first communications device, including: in the case that the first communications device supports reporting the capability identifier of the first communications device, the second The communication device receives the capability identifier of the first communication device sent by the first communication device. In this way, the solution cannot be implemented when the first communication device does not support the capability identification of the first communication device.
  • the communication capability reporting method provided by the embodiment of the present application may further include: when the first communication device does not support reporting the capability identifier of the first communication device, the second communication device receives the first communication.
  • the indication information sent by the device is sent to the network device in the core network.
  • the indication information is used to indicate that the first communication device does not support the capability identifier for reporting the first communication device.
  • the network device in the core network can learn that the first communication device does not support the capability identification of the first communication device, so that the communication capability of the corresponding first communication device is not searched according to the capability identifier of the first communication device.
  • the communication capability of the first communication device is queried to the first communication device, so that the first communication device reports the The communication capability of the first communication device. That is to say, based on the scheme, it is possible to implement reporting of the communication capability of the communication device that does not support the capability identification of the communication device.
  • the second communications device receives the indication information sent by the first communications device, where the second communications device receives the first RRC message or the first non-access stratum sent by the first communications device.
  • the NAS message, the first RRC message or the first NAS message includes the indication information. That is to say, the first communication device can send the indication information to the second communication device by using an existing RRC message or a NAS message, without adding new signaling, thereby saving system resources.
  • the second communications device receives the capability identifier of the first communications device that is sent by the first communications device, and the second communications device receives the second RRC message or the second NAS message that is sent by the first communications device.
  • the second RRC message or the second NAS message includes a capability identifier of the first communications device. That is to say, the first communication device can report the capability identifier of the first communication device to the second communication device by using an existing RRC message or a NAS message, without adding new signaling, thereby saving system resources.
  • a first communication device having the functionality to implement the method of any of the preceding aspects.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the first communication device includes: a processing module and a transceiver module; the processing module is configured to determine a capability identifier of the first communication device, where the capability identifier of the first communication device is corresponding to the first communication device One of the one or more capability identifiers; the transceiver module is configured to send the capability identifier of the first communication device to the second communication device, where the capability identifier of the first communication device is used to determine the first communication device Communication ability.
  • the capability identification of the first communication device includes at least one component of the first international mobile device identification code IMEI.
  • the capability identifier of the first communications device includes at least one component of the first IMEI, including: the capability identifier of the first communications device includes a type allocation code TAC in the first IMEI; or The capability identifier of the first communications device includes a TAC and a sequence number SNR in the first IMEI; or the capability identifier of the first communications device includes a TAC, an SNR, and a software version number SVN in the first IMEI; or The capability identification of the first communication device includes a TAC, an SNR, and a verification code CD in the first IMEI.
  • At least one component of the capability identifier of the first communication device is different from at least one component of the second IMEI, wherein the second IMEI is an IMEI of the first communication device.
  • the first IMEI is an IMEI used by a vendor to which the first communication device belongs.
  • the capability identifier of the first communication device is different from the capability identifier of the third communication device, wherein the third communication device and the first communication device are communication devices of different vendors.
  • the transceiver module is specifically configured to: send, to the second communications device, a first radio resource control RRC message or a first non-access stratum NAS message, where the first RRC message or the first NAS message includes The capability identification of the first communication device.
  • the processing module is specifically configured to determine a capability identifier of the first communication device if the first communication device supports reporting the capability identifier of the first communication device.
  • the transceiver module is further configured to: when the first communication device does not support reporting the capability identifier of the first communication device, send the indication information to the second communication device, where the second communication is The device sends the indication information to the network device in the core network.
  • the indication information is used to indicate that the first communication device does not support the capability identifier for reporting the first communication device.
  • the transceiver module is configured to send the indication information to the second communications device, including: sending, by the second communications device, a second RRC message or a second NAS message, or the second RRC message or The second NAS message includes the indication information.
  • a first communication device comprising: a processor and a memory; the memory is configured to store a computer execution instruction, and when the first communication device is in operation, the processor executes the computer execution instruction stored in the memory
  • the first communication device performs the communication capability reporting method according to any one of the above first aspects.
  • a first communication device comprising: a processor; the processor is configured to couple with a memory, and after reading an instruction in the memory, perform any one of the foregoing first aspects according to the instruction The communication capability reporting method.
  • a computer readable storage medium having stored therein instructions that, when executed on a computer, cause the computer to perform the communication capabilities of any of the above first aspects Reporting method.
  • a computer program product comprising instructions which, when run on a computer, cause the computer to perform the communication capability reporting method of any of the above first aspects.
  • the first communication device in the third to seventh aspects may be a terminal, or may be a chip system or a circuit in the terminal.
  • the chip system may be composed of a chip, and may also include a chip and other discrete devices. The embodiment of the present application does not specifically limit this.
  • a second communication device having the function of implementing the method of any of the above second aspects.
  • This function can be implemented in hardware or in hardware by executing the corresponding software.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the second communication device includes a receiving module and a sending module, where the receiving module is configured to receive a capability identifier of the first communications device sent by the first communications device, where the capability identifier of the first communications device is the first One of the one or more capability identifiers corresponding to the communication device; the sending module, configured to send the capability identifier of the first communication device to the network device, where the capability identifier of the first communication device is used to determine the first Communication capabilities of communication devices.
  • the capability identification of the first communication device includes at least one component of the first international mobile device identification code IMEI.
  • the capability identifier of the first communications device includes at least one component of the first IMEI, including: the capability identifier of the first communications device includes a type allocation code TAC in the first IMEI; or The capability identifier of the first communications device includes a TAC and a sequence number SNR in the first IMEI; or the capability identifier of the first communications device includes a TAC, an SNR, and a software version number SVN in the first IMEI; or The capability identification of the first communication device includes a TAC, an SNR, and a verification code CD in the first IMEI.
  • At least one component of the capability identifier of the first communication device is different from at least one component of the second IMEI, wherein the second IMEI is an IMEI of the first communication device.
  • the first IMEI is an IMEI used by a vendor to which the first communication device belongs.
  • the capability identifier of the first communication device is different from the capability identifier of the third communication device, wherein the third communication device and the first communication device are communication devices of different vendors.
  • the receiving module is further configured to receive a communication capability of the first communications device sent by the network device.
  • the receiving module is further configured to receive a first message sent by the network device, where the first message is used to request communication capability of the first communications device, and the sending module is further configured to The first communication device sends a second message, where the second message is used to request the communication capability of the first communication device, and the receiving module is further configured to receive the communication capability of the first communication device sent by the first communication device.
  • the first message in the embodiment of the present application may carry the capability identifier of the first communication device, which is not specifically limited in this embodiment.
  • the second message in the embodiment of the present application may carry the capability identifier of the first communication device, which is not specifically limited in this embodiment of the present application.
  • the sending module is further configured to send, to the network device, a communication capability of the first communications device, where the network device stores a capability identifier of the first communications device and communications of the first communications device The correspondence of capabilities.
  • the receiving module is further configured to receive a capability identifier of the first communications device that is sent by the first communications device and corresponds to the communications capability of the first communications device.
  • the sending module is further configured to send, to the network device, a communication capability of the first communication device and a capability identifier of the first communication device corresponding to the communication capability of the first communication device, where the network device stores Correspondence between the capability identifier of the first communication device and the communication capability of the first communication device.
  • the receiving module is configured to receive the capability identifier of the first communications device that is sent by the first communications device, and is configured to: when the first communications device supports reporting the capability identifier of the first communications device In case, the capability identifier of the first communication device sent by the first communication device is received.
  • the receiving module is further configured to: when the first communications device does not support reporting the capability identifier of the first communications device, receive the indication information sent by the first communications device, and The indication information is sent to the network device in the core network, and the indication information is used to indicate that the first communication device does not support reporting the capability identifier of the first communication device.
  • the receiving module is configured to receive the indication information sent by the first communications device, including: receiving, by the first communications device, a first radio resource control RRC message or a first non-access stratum
  • the NAS message, the first RRC message or the first NAS message includes the indication information.
  • the receiving module is configured to receive the capability identifier of the first communications device that is sent by the first communications device, and includes: receiving, by the first communications device, a second RRC message or a second NAS message.
  • the second RRC message or the second NAS message includes a capability identifier of the first communications device.
  • a second communication device comprising: a processor and a memory; the memory is configured to store a computer execution instruction, and when the second communication device is in operation, the processor executes the computer execution instruction stored in the memory
  • the second communication device performs the communication capability reporting method according to any one of the above second aspects.
  • a second communication device includes: a processor; the processor is configured to couple with a memory, and after reading an instruction in the memory, perform any one of the foregoing second aspects according to the instruction The communication capability reporting method.
  • a computer readable storage medium having stored therein instructions that, when run on a computer, cause the computer to perform the communication of any of the above second aspects Ability reporting method.
  • a computer program product comprising instructions which, when run on a computer, cause the computer to perform the communication capability reporting method of any of the above second aspects.
  • the second communication device in the eighth to twelfth aspects may be a terminal, a chip system or a circuit in the terminal, or an access device, or a chip in the access device.
  • the system or the circuit, the chip system may be composed of a chip, and may also include a chip and other discrete devices, which are not specifically limited in this embodiment of the present application.
  • a thirteenth aspect a communication system is provided, the communication system comprising a network device, the second communication device of any of the above aspects, and the first communication device of any one or more of the above aspects.
  • FIG. 1 is a schematic structural diagram of a communication system according to an embodiment of the present application.
  • FIG. 2 is a schematic structural diagram of hardware of an access device and a communication device according to an embodiment of the present disclosure
  • FIG. 3 is a schematic flowchart 1 of a method for reporting a communication capability according to an embodiment of the present application
  • FIG. 4 is a schematic diagram of maintenance of a capability identifier of a terminal and a communication capability of a terminal according to an embodiment of the present disclosure
  • FIG. 5 is a format 1 of an IMEI according to an embodiment of the present application.
  • Figure 6 is a format 2 of an IMEI according to an embodiment of the present application.
  • FIG. 7 is an example of a first IMEI and a second IMEI according to an embodiment of the present application.
  • FIG. 8 is a second schematic flowchart of a communication capability reporting method according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a first communications device according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of a second communication device according to an embodiment of the present application.
  • the words “first”, “second”, and the like are used to distinguish the same items or similar items whose functions and functions are substantially the same. Those skilled in the art can understand that the words “first”, “second” and the like do not limit the number and execution order, and the words “first”, “second” and the like are not necessarily limited.
  • the network architecture and the service scenario described in the embodiments of the present application are for the purpose of more clearly illustrating the technical solutions of the embodiments of the present application, and are not limited to the technical solutions provided by the embodiments of the present application.
  • the technical solutions provided by the embodiments of the present application are equally applicable to similar technical problems.
  • the communication system 10 includes a second communication device 101, a network device 103 connected to the second communication device 101, and one or more first communication devices 102 connected to the second communication device 101.
  • the following is an example in which the second communication device 101 interacts with the network device 103 and any of the first communication devices 102 as an example.
  • the first communication device 102 is configured to determine a capability identifier of the first communication device 102, where the capability identifier of the first communication device 102 is one of the one or more capability identifiers corresponding to the first communication device 102.
  • the first communication device 102 is further configured to send the capability identifier of the first communication device 102 to the second communication device 101.
  • the second communication device 101 is configured to receive the capability identifier of the first communication device 102 sent by the first communication device 102, and send the capability identifier of the first communication device 102 to the network device 103.
  • the network device 103 is configured to receive the capability identifier of the first communications device 102 sent by the second communications device 101, and determine the communications capability of the first communications device 102 according to the capability identifier of the first communications device 102.
  • the communication capability in the embodiment of the present application may include, for example, an access capability, or a processing capability, and the like.
  • the first communication device 102 and the second communication device 101 in the embodiment of the present application may directly communicate with each other, and may also perform communication by forwarding of other devices, which is not specifically limited in this embodiment of the present application.
  • the network device 103 and the second communication device 101 in the embodiment of the present application may directly communicate with each other, and may also perform communication by forwarding of other devices, which is not specifically limited in this embodiment of the present application.
  • the first communication device 102 in the embodiment of the present application may be a chip system or a circuit in the terminal or the terminal, which is not specifically limited in this embodiment of the present application.
  • the chip system in the embodiment of the present application may be composed of a chip, and may also include a chip and other discrete devices.
  • the second communication device 101 in the embodiment of the present application may be a terminal, a chip system or a circuit in the terminal, an access device, or a chip system or a circuit in the access device. limited.
  • the network device 103 in the embodiment of the present application may be a mobility management network element or a chip system or a circuit in the mobility management network element, which is not specifically limited in this embodiment of the present application.
  • the terminal involved in the embodiment of the present application may include an NR system or various handheld devices and in-vehicle devices with wireless communication functions in a public land mobile network (PLMN) in a future evolution.
  • a wearable device, a computing device, or other processing device connected to a wireless modem may also include a subscriber unit, a cellular phone, a smart phone, a wireless data card, a personal digital assistant (personal digital) Assistant, PDA) computer, tablet, wireless modem, handheld, laptop computer, cordless phone, or wireless local loop (WLL) , machine type communication (MTC) terminal, user equipment (UE), mobile station (MS), terminal device or relay user equipment.
  • the relay user equipment may be, for example, a 5G residential gateway (RG).
  • RG 5G residential gateway
  • the access device involved in the embodiment of the present application refers to a device that accesses the core network, and may be, for example, a 5G NR system or a base station in a future PLMN, and a broadband network gateway (BNG). Switches, non-3GPP access devices, etc.
  • the base station may include various types of base stations, such as a micro base station (also referred to as a small station), a macro base station, a relay station, an access point, or an NR Node B (NRBB) in a 5G NR system, etc., in the embodiment of the present application. This is not specifically limited.
  • the mobility management network element involved in the embodiment of the present application may be, for example, an access and mobility management function (AMF) network element in a 5G NR system or other mobile in a future evolved PLMN.
  • AMF access and mobility management function
  • the management network element is not specifically limited in this embodiment.
  • the capability identifier of the first communication device sent by the first communication device to the second communication device is one or more capability identifiers corresponding to the first communication device, when the capability report is required.
  • One of the logos that is to say, in the embodiment of the present application, different capability identifiers may be used for the first communication device, so in the case of associating the communication capability of the first communication device with the capability identifier of the first communication device, the first communication The device may update its communication capabilities in time using the capability identification determined from one or more capability identifiers corresponding to the first communication device.
  • the first communication device or the second communication device in the embodiment of the present disclosure may be implemented by one device, or may be implemented by multiple devices, or may be a functional module in a device.
  • This example does not specifically limit this. It can be understood that the above functions can be either a network component in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform).
  • FIG. 2 is a schematic diagram showing the hardware structure of a communication device according to an embodiment of the present application.
  • the communication device 200 includes at least one processor 201, a communication line 202, a memory 203, and at least one communication interface 204.
  • the processor 201 can be a general central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more for controlling the execution of the program of the present application. integrated circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • Communication line 202 can include a path for communicating information between the components described above.
  • the communication interface 204 uses devices such as any transceiver for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .
  • devices such as any transceiver for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. .
  • RAN radio access network
  • WLAN wireless local area networks
  • the memory 203 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type that can store information and instructions.
  • the dynamic storage device can also be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, and a disc storage device. (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and can be Any other media accessed, but not limited to this.
  • the memory may be stand-alone and connected to the processor via communication line 202. The memory can also be integrated with the processor.
  • the memory 203 is used to store computer execution instructions for executing the solution of the present application, and is controlled by the processor 201 for execution.
  • the processor 201 is configured to execute a computer execution instruction stored in the memory 203, thereby implementing the communication capability reporting method provided by the following embodiments of the present application.
  • the computer-executed instructions in the embodiment of the present application may also be referred to as an application code, which is not specifically limited in this embodiment of the present application.
  • processor 201 may include one or more CPUs, such as CPU0 and CPU1 in FIG.
  • communication device 200 can include multiple processors, such as processor 201 and processor 208 in FIG. Each of these processors can be a single-CPU processor or a multi-core processor.
  • processors herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • the communication device 200 can also include an output device 205 and an input device 206.
  • Output device 205 is in communication with processor 201 and can display information in a variety of ways.
  • the output device 205 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait.
  • Input device 206 is in communication with processor 201 and can receive user input in a variety of ways.
  • input device 206 can be a mouse, keyboard, touch screen device or sensing device, and the like.
  • the communication device 200 described above may be a general purpose device or a dedicated device.
  • the communication device 200 may be the above-described terminal, access device, chip system, or device having a similar structure in FIG.
  • the embodiment of the present application does not limit the type of the communication device 200.
  • the communication system shown in FIG. 1 is applied to the current 5G NR system
  • the first communication device is a terminal in the 5G NR system
  • the second communication device is the gNB in the 5G NR system.
  • the network device is an AMF network element in the 5G NR system, and the method for reporting the communication capability provided by the embodiment of the present application is described.
  • a capability reporting method provided by the embodiment of the present application includes the following steps:
  • the terminal sends a random access preamble to the gNB, so that the gNB receives the random access preamble sent by the terminal.
  • S302 The gNB sends a random access response to the terminal, so that the terminal receives the random access response sent by the gNB.
  • the terminal determines the capability identifier of the terminal, where the capability identifier of the terminal is one of the one or more capability identifiers corresponding to the terminal.
  • the one or more capability identifiers corresponding to the terminal may be pre-stored on the terminal, or may be calculated by the terminal according to an algorithm when the communication capability needs to be reported, or may be a terminal.
  • the embodiment of the present application does not specifically limit this.
  • the communication capability of the terminal in the case that the communication capability of the terminal is associated with the capability identifier of the terminal, in order to avoid conflicts between terminal capabilities of different terminal vendors, multiple terminals are usually allocated to different terminal vendors.
  • the ability identification is different. That is, for each terminal manufacturer, it is required to maintain a plurality of capability identifiers of terminals different from other terminal vendors, and communication capabilities of terminals corresponding to the capability identifiers of each terminal, so that the gNB or AMF network element can be based on the terminal.
  • the capability identification distinguishes the terminals of different vendors to achieve differentiated competition.
  • the one or more capability identifiers in the embodiment of the present application may constitute a capability identifier set or a capability identifier list, and the like, which is not specifically limited in this embodiment.
  • the A terminal manufacturer can maintain the capability identifier of one or more terminals, for example, the capability identifier A1, the capability identifier A2, the capability identifier A3, ..., the capability identifier An;
  • the capability identifier of one or more terminals is maintained, for example, the capability identifier B1, the capability identifier B2, the capability identifier B3, ..., the capability identifier Bn.
  • the communication capability of the terminal corresponding to the capability identifier of each terminal maintained by the A terminal manufacturer may be: the capability identifier A1 corresponding to the communication capability A11, the capability identifier A2 corresponding to the communication capability A21, the capability identifier A3 corresponding to the communication capability A31, ..., the capability identifier An corresponding communication capability An1;
  • the communication capability of the terminal corresponding to the capability identifier of each terminal maintained by the B terminal manufacturer may be: the capability identifier B1 corresponding to the communication capability B11, the capability identifier B2 corresponding to the communication capability B21, and the capability identifier B3 corresponding to the communication capability B31 , ..., the capability identifier Bn corresponds to the communication capability Bn1.
  • the capability identifier A1, the capability identifier A2, the capability identifier A3, ..., the capability identifier An and the capability identifier B1, the capability identifier B2, the capability identifier B3, ..., the capability identifier Bn are different; the communication capability A11 corresponding to the capability identifier A1
  • the communication capability Bn1 corresponding to the communication capability B31, ..., and the capability identifier Bn of the identifier B3 may be the same or may not be the same, which is not specifically limited in this embodiment of the present application.
  • the gNB or the AMF network element can distinguish terminals of different vendors according to the capability identifiers of different terminals, thereby achieving differentiated competition. For example, if the gNB obtains the capability identifier of a terminal as B1, it can learn that the terminal is a terminal of the B terminal manufacturer according to the capability identifier B1 of the terminal.
  • the capability identifier of one or more terminals and the communication capability of the terminal corresponding to the capability identifier of each terminal are also required to be maintained.
  • the capability identifier of one or more terminals maintained by the terminal is an identifier in the capability identifier of one or more terminals maintained by the terminal manufacturer to which the terminal belongs. That is, assuming that one or more capability identifiers can form a capability identifier set, the set of capability identifiers of one or more terminals corresponding to the terminal is usually a capability identifier set of the terminal maintained by the terminal manufacturer to which the terminal belongs. Subset.
  • the capability identifiers of one or more terminals maintained by different terminals of the same terminal manufacturer may be overlapped or may not be overlapped, which is not specifically limited in this embodiment of the present application.
  • the terminal 1 of the A terminal manufacturer can maintain the capability identifier A1 and the capability identifier A2; the terminal 2 of the A terminal manufacturer can maintain the capability identifier A2 and the capability identifier A3, wherein the terminal 1 and the A terminal of the A terminal manufacturer
  • the capability identifiers of the terminals maintained by the terminal 2 of the manufacturer overlap, and are the capability identifiers 2.
  • the terminal 3 of the B terminal manufacturer can maintain the capability identification B1 and the capability identification B2; the terminal 4 of the B terminal manufacturer can maintain the capability identification B3, ..., wherein the terminal 3 and the B terminal manufacturer of the B terminal manufacturer The capability identifiers of the terminals maintained by the terminal 4 do not overlap.
  • each terminal manufacturer maintains a plurality of capability identifiers of terminals different from other terminal vendors, and one or more capability identifiers corresponding to terminals of the terminal manufacturer are in one or more capability identifiers maintained by the terminal vendor. Therefore, in order to distinguish terminals of different vendors, one or more capability identifiers corresponding to terminals of different terminal vendors do not overlap, and are collectively described herein, and are not described below.
  • one or more capability identifiers corresponding to a terminal of a certain terminal manufacturer and communication capabilities of the terminal corresponding to the capability identifier of each terminal may be software-updated, for example,
  • the software version upgrade of the terminal causes the communication capability of the terminal to be changed; or, in the case where the GCF/protocol authentication/modification software version causes the communication capability of the terminal to be changed; or, the software maintenance is caused in the later stage.
  • the one or more capability identifiers corresponding to the terminal and the communication capability of the terminal corresponding to the capability identifier of each terminal may be updated.
  • the original maintenance capability identifier A1 and the capability identifier A2 in the terminal 1 of the A terminal manufacturer when the software version upgrade of the terminal 1 causes the communication capability of the terminal 1 to be changed; or
  • the GCF/protocol authentication/modification software version causes the communication capability of the terminal 1 to be changed; or, in the case where the post-software maintenance causes the communication capability of the terminal 1 to be changed, etc.
  • the capability identifier A1 and the capability identifier A2 maintained by the terminal 1 of the terminal manufacturer are updated, for example, updated to the terminal 1 maintenance capability identifier A3 and the capability identifier An, wherein the capability identifier update behavior capability identifier A3 maintained at the terminal 1 of the A terminal manufacturer
  • the communication capability of the terminal maintained by the terminal 1 of the A terminal manufacturer is also updated to the communication capability A31 corresponding to the capability identifier A3 and the communication capability An1 corresponding to the capability identifier An, respectively. No longer.
  • the capability identifier of the terminal may be in multiple characterization forms.
  • the capability identifier of the terminal includes at least one component of the first IMEI.
  • the capability identifier of the terminal includes at least one component of the first IMEI, including: the capability identifier of the terminal includes a TAC in the first IMEI; or the capability identifier of the terminal includes a TAC and an SNR in the first IMEI; or, the capability of the terminal
  • the identifier includes the TAC, the SNR, and the CD in the first IMEI, which is not specifically limited in this embodiment of the present application.
  • the capability identifier of the terminal includes at least one of the first IMEI.
  • the component includes: the capability identifier of the terminal includes a 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
  • the embodiment of the present application does not specifically limit this.
  • the TAC in FIG. 5 or FIG. 6 is a code for distinguishing the brand and model of the terminal, and the code is allocated by the global system for mobile communications assembly (GSMA) and its authorized organization; FIG. 5 or FIG.
  • the SNR is the serial number of the terminal manufacturer's production line; the CD in Figure 5 is usually determined by the TAC and SNR to verify the correctness of the TAC and SNR; the SVN in Figure 6 is usually the terminal's factory-to-communication communication.
  • the software version number obtained in the relevant part of the test, the detailed description of the first IMEI related field can refer to the existing description of the IMEI, and details are not described herein again.
  • the at least one component of the capability identifier of the terminal may be the same as the at least one component of the second IMEI, and may not be the same.
  • the second IMEI is an IMEI of the terminal.
  • the format of the IMEI of the terminal is as shown in FIG. 6.
  • the IMEI of the terminal is specifically 10000000100000 10 as shown in (a) of FIG. 7, that is, 8 of the TAC field in the second IMEI.
  • the bit number is 10000000
  • the 6-digit number of the SNR field is 100000
  • the 2 digits of the SVN field is 10, in the case where the first IMEI is specifically as shown in (b) of FIG. 7 and is 10000000 100001 10:
  • the capability identifier of the terminal includes the TAC in the first IMEI, that is, the capability identifier of the terminal is 10000000, that is, the capability identifier of the terminal is the same as the TAC part in the second IMEI;
  • the capability identifier of the terminal includes the TAC and the SNR in the first IMEI, and the capability identifier of the terminal is 10000000 100001
  • the TAC part in the capability identifier of the terminal is the same as the TAC part in the second IMEI, and the capability identifier in the terminal is The SNR portion is different from the SNR portion of the second IMEI;
  • the capability identifier of the terminal includes the TAC, SNR, and SVN in the first IMEI, and the capability identifier of the terminal is 10000000 100001 10
  • the TAC part in the capability identifier of the terminal is the same as the TAC part in the second IMEI, and the capability of the terminal
  • the SNR portion in the identity is not the same as the SNR portion in the second IMEI
  • the SVN portion in the capability identification of the terminal is the same as the SVN portion in the second IMEI.
  • FIG. 7 is only an exemplary description, and the first IMEI and the second IMEI may also be other identifiers, which are not specifically limited in this embodiment of the present application.
  • the first IMEI and the second IMEI in the embodiment of the present application may be the same or different, and the embodiment of the present application does not specifically limit this.
  • the first IMEI in the embodiment of the present application is an IMEI used by the terminal device manufacturer corresponding to the foregoing terminal, that is, the first IMEI and the second IMEI in the embodiment of the present application are the same terminal device manufacturer.
  • the IMEIs used are, for example, the IMEIs in the IMEI resource pool allocated to the same terminal manufacturer. This is a unified description, and is not mentioned here.
  • step S303 there is no necessary sequence of execution between the step S303 and the step S301 in the embodiment of the present application, and the step S301 may be performed first, and then the step S303 may be performed; or the step S303 may be performed first, and then the step S301 is performed; It is also possible to perform the steps S301 and S303 at the same time, which is not specifically limited in this embodiment of the present application.
  • the terminal sends an 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 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 message to the gNB, so that the gNB receives the RRC connection setup complete message sent by the terminal.
  • the RRC connection request message in the step S304 or the RRC connection setup complete message in the step S306 may carry the capability identifier of the terminal determined in the step S303, which is not specifically limited in this embodiment of the present application.
  • the capability identifier of the terminal may be carried in a non-access stratum (NAS) message, for example, the NAS in the RRC connection setup complete message in step S306.
  • the message carries the capability identifier of the above terminal.
  • the gNB can transparently transmit the NAS message to the AMF network element, which is not specifically limited in this embodiment.
  • step S306 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 determined in step S303, there is no necessity between step S303 and step S304.
  • the execution sequence may be performed by performing step S303 and then performing step S304.
  • the step S304 may be performed first, and then the step S303 may be performed, and the step S303 and the step S304 may be performed at the same time. .
  • the communication capability reporting method may further include the following steps:
  • the gNB sends an initial 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.
  • the initial terminal message at this time includes the NAS message, which is not specifically limited in this embodiment of the present application.
  • the AMF network element may search for the communication capability of the terminal corresponding to the capability identifier of the terminal in the AMF network element, and assume that the terminal corresponding to the capability identifier of the terminal is not stored in the AMF network element.
  • the communication capability reporting method provided by the embodiment of the present application may further include the following steps S308-S314:
  • the AMF network element sends a UE 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 establishment request in the embodiment of the present application may further carry the capability identifier of the terminal determined in the foregoing step S303, which is not specifically limited in this embodiment of the present application.
  • the gNB sends a UE context setup response to the AMF network element, so that the AMF network element receives the terminal context establishment response sent by the gNB.
  • the gNB sends a terminal capability query (UE capability enquiry) to the terminal, so that the terminal receives the terminal capability query sent by the gNB.
  • UE capability enquiry UE capability enquiry
  • the terminal capability query in the embodiment of the present application may further carry the capability identifier of the terminal, which is not specifically limited in this embodiment of the present application.
  • the terminal sends the UE capability information to the gNB, so that the gNB receives the terminal capability information from the terminal.
  • the capability information of the terminal includes the communication capability of the terminal.
  • the capability information of the terminal may further include a capability identifier of the terminal corresponding to the communication capability of the terminal, which is not specifically limited in this embodiment of the present 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.
  • UE capability information indication UE capability information indication
  • the terminal capability information indication includes the communication capability of the terminal.
  • the terminal capability information indication in the embodiment of the present application may further include a capability identifier of the terminal corresponding to the communication capability of the terminal, which is not specifically limited in this embodiment of the present application.
  • the AMF network element stores a correspondence between the capability identifier of the terminal and the communication capability of the terminal.
  • the correspondence between the capability identifier of the terminal and the communication capability of the terminal that is stored by the AMF network element may include the capability identifier of the terminal and the communication capability corresponding to the capability identifier of the terminal.
  • the multiple groups of correspondence stored in the AMF network element can be as shown in Table 1:
  • Table 1 is merely exemplary to provide a storage manner of the correspondence between the communication capability of the terminal and the capability identifier of the terminal, and other storage forms may be present, which is not specifically limited in this embodiment of the present application.
  • the method for reporting the communication capability may further include the following steps S315-S317, if the AMF network element stores the communication capability of the terminal corresponding to the capability identifier of the terminal.
  • the AMF network element determines the communication capability of the terminal according to the capability identifier of the terminal and the correspondence between the stored capability identifier of the terminal and the communication capability of the terminal.
  • the AMF network element sends a terminal context establishment request to the gNB, so that the gNB receives the terminal context establishment request sent by the AMF network element.
  • the terminal context establishment request carries the communication capability of the terminal.
  • the gNB stores the communication capability of the terminal.
  • Steps S308-S314 may be applied to the initial registration of the terminal to the network process; steps S315-S317 may be applied to the process of the terminal transitioning from the idle state to the connected state; or, steps S315-S317 may be applied to the terminal switching from one gNB to In another gNB process, the embodiment of the present application does not specifically limit this.
  • the communication capability reporting method provided by the embodiment of the present application may further include the following steps:
  • the gNB sends an RRC reconfiguration message to the terminal, so that the terminal receives the RRC reconfiguration message sent by the gNB.
  • step S318 can refer to the existing implementation manner, and details are not described herein again.
  • the capability identifier of the terminal sent by the terminal to the gNB is one of the one or more capability identifiers corresponding to the terminal. That is, in the embodiment of the present application, different capability identifiers may be used for one terminal. Therefore, in a case where the communication capability of the terminal is associated with the capability identifier of the terminal, the terminal may use one or more corresponding to the slave terminal.
  • the capability identifier identified in the capability identifier updates its communication capabilities in a timely manner.
  • the action of the terminal or the gNB in the foregoing steps S301 to S318 can be performed by the processor 201 in the communication device 200 shown in FIG. 2 to call the application code stored in the memory 203.
  • This embodiment does not impose any limitation.
  • the embodiment shown in FIG. 3 is described by taking as an example a case where the communication capability of the terminal is associated with the capability identifier of the terminal, that is, the terminal supports the capability identification of the terminal.
  • the terminal manufacturer if the terminal manufacturer does not maintain the correspondence between the capability identifier of the terminal and the communication capability of the terminal, the terminal of the terminal manufacturer cannot report the capability identifier of the terminal by using an RRC message or a NAS message.
  • the communication capability reporting method provided by the embodiment of the present application may be as shown in FIG. 8 and includes the following steps:
  • S803-S805 is similar to the steps S303-S306.
  • the RRC message in the embodiment of the present application such as the RRC connection request message or the RRC connection setup complete message
  • the indication information is used to indicate that the terminal does not support the capability identifier of the reporting terminal; or the NAS message in the RRC connection setup complete message does not carry the capability identifier of the terminal, but
  • the indication information is used to indicate that the terminal does not support the capability identifier of the reporting terminal.
  • the indication information may be indicated by one or more bits. For example, a value of 0 indicates that the terminal does not support the capability identifier of the reporting terminal; or a value of 1 indicates that the terminal does not support the capability identifier of the reporting terminal.
  • the capability identifier field of the terminal is all set to 0 to represent that the terminal does not support the capability identifier of the reporting terminal, and the implementation manner of the indication information is not specifically limited in this embodiment of the present application. .
  • the method for reporting the capability of the terminal that does not support the capability of the reporting terminal to the gNB in the RRC connection establishment process is further provided in the step S801-S805. Further, the method for reporting the communication capability provided by the embodiment of the present 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.
  • the initial terminal message at this time includes the NAS message, which is not specifically limited in this embodiment of the present application.
  • the initial terminal message in the embodiment of the present application may further carry the identifier of the terminal, and after the AMF network element learns that the terminal does not support the capability identifier of the reporting terminal, the AMF network element may query the communication capability of the corresponding terminal according to the identifier of the terminal.
  • the communication capability reporting method provided by the embodiment of the present application may further include the following steps S807-S813:
  • the AMF network element sends a 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 UE context setup response to the AMF network element, so that the AMF network element receives the terminal context establishment response sent by the gNB.
  • the gNB sends a terminal capability query (UE capability enquiry) to the terminal, so that the terminal receives the terminal capability query sent by the gNB.
  • UE capability enquiry UE capability enquiry
  • the terminal sends the UE capability information to the gNB, so that the gNB receives the terminal capability information from the terminal.
  • the capability information of the terminal includes the communication capability of the terminal.
  • S811 and gNB store 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.
  • UE capability information indication UE capability information indication
  • the terminal capability information indication includes the communication capability of the terminal.
  • the AMF network element stores the communication capability of the terminal.
  • the communication capabilities of multiple terminals stored by the AMF network element can be as shown in Table 2:
  • Table 2 is only an exemplary way of providing a communication capability of the terminal, and may also have other storage modes. This embodiment of the present application does not specifically limit this.
  • the method for reporting the communication capability may further include the following steps S814-S815:
  • the AMF network element sends a terminal context establishment request to the gNB, so that the gNB receives the terminal context establishment request sent by the AMF network element.
  • the terminal context establishment request carries the communication capability of the terminal.
  • S815 and gNB store the communication capability of the terminal.
  • Steps S807-S813 can be applied to the initial registration of the terminal to the network process; steps S814-S815 can be applied to the process of the terminal transitioning from the idle state to the connected state; or, steps S814-S815 can be applied to the terminal switching from one gNB to In another gNB process, the embodiment of the present application does not specifically limit this.
  • the communication capability reporting method provided by the embodiment of the present application may further include the following steps:
  • the gNB sends an RRC reconfiguration message to the terminal, so that the terminal receives the RRC reconfiguration message sent by the gNB.
  • the terminal if the terminal does not support the capability identification of the reporting terminal, the terminal sends the capability of the terminal not supporting the reporting terminal to the AMF network element in the core network through the gNB. Logo.
  • the AMF network element can learn that the terminal does not support the capability identifier of the reporting terminal, and thus does not search for the communication capability of the corresponding terminal according to the capability identifier of the terminal, but not knows that the terminal is not stored in the AMF network element according to the identifier of the terminal.
  • the terminal is queried for the communication capability of the terminal, so that the terminal reports the communication capability of the terminal. Based on the solution, the reporting of the communication capability of the terminal that is not supported by the capability identifier of the terminal can be implemented.
  • the action of the terminal or the gNB in the above steps S801 to S816 can be performed by the processor 201 in the communication device 200 shown in FIG. 2 to call the application code stored in the memory 203, which is not limited in this embodiment.
  • FIG. 3 and FIG. 8 are both a first communication device being a terminal in the 5G NR system, and the second communication device is a gNB in the 5G NR system as an example.
  • the second The communication device may also be a terminal in the 5G NR system, such as a relay user equipment.
  • the corresponding communication capability reporting method is similar to the above FIG. 3 or FIG. 8 , and the difference is, for example, equivalent to FIG. 3 or FIG. 8 .
  • a forwarding device is inserted, and the second communication device mainly forwards the capability identifier of the received terminal or the communication capability of the terminal, and the related descriptions may refer to the embodiment shown in FIG. 3 or FIG. This embodiment of the present application will not be described again.
  • the first communication device or the second communication device includes a hardware structure and/or a software module corresponding to each function.
  • the present application can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.
  • the embodiment of the present application may perform the division of the function module on the first communication device or the second communication device according to the foregoing method example.
  • each function module may be divided according to each function, or two or more functions may be integrated into one.
  • Processing module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of the module in the embodiment of the present application is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • FIG. 9 shows a schematic structural diagram of the first communication device 90.
  • the first communication device 90 may be the terminal in the foregoing embodiment, or may be the chip system or circuit in the terminal in the foregoing embodiment, which is not specifically limited in this embodiment of the present application.
  • the first communication device 90 includes a processing module 902 and a transceiver module 901.
  • the processing module 902 is configured to determine a capability identifier of the first communications device 90, where the capability identifier of the first communications device 90 is one of the one or more capability identifiers corresponding to the first communications device 90; the transceiver module 901, A capability identifier for transmitting the first communication device 90 to the second communication device, the capability identification of the first communication device 90 being used to determine the communication capability of the first communication device 90.
  • the capability identifier of the first communication device 90 includes at least one component of the first IMEI.
  • the capability identifier of the first communications device 90 includes at least one component of the first IMEI, including: the capability identifier of the first communications device 90 includes a TAC in the first IMEI; or the capability identifier of the first communications device 90 Include the TAC and the sequence number SNR in the first IMEI; or, the capability identifier of the first communication device 90 includes the TAC, SNR, and SVN in the first IMEI; or the capability identifier of the first communication device 90 includes the first IMEI TAC, SNR and CD.
  • At least one component of the capability identifier of the first communication device 90 is different from at least one component of the second IMEI, wherein the second IMEI is an IMEI of the first communication device 90.
  • the first IMEI is an IMEI used by a vendor of the first communication device 90.
  • the capability identifier of the first communication device 90 is different from the capability identifier of the third communication device, where the third communication device and the first communication device 90 are communication devices of different vendors.
  • the transceiver module 901 is specifically configured to: send the first RRC message or the 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 90.
  • the processing module 902 is specifically configured to: when the first communication device 90 supports reporting the capability identifier of the first communication device 90, determine the capability identifier of the first communication device 90.
  • the transceiver module 901 is further configured to: when the first communication device 90 does not support reporting the capability identifier of the first communication device 90, send the indication information to the second communication device, where the indication information is used to indicate the first communication device.
  • the capability flag for reporting the first communication device 90 is not supported.
  • the sending and receiving module 901 is configured to send the indication information to the second communications device, where the method includes: sending, by the second communications device, a second RRC message or a second NAS message, where the second RRC message or the second NAS message includes the indication information.
  • the first communication device 90 is presented in a form that divides the various functional modules in an integrated manner.
  • a “module” herein may refer to a particular ASIC, circuitry, processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other devices that provide the functionality described above.
  • the first communication device 90 can take the form shown in FIG.
  • the processor 201 in FIG. 2 can execute the instruction by calling the computer stored in the memory 203, so that the first communication device 90 executes the communication capability reporting method in the above method embodiment.
  • the function/implementation process of the processing module 902 and the transceiver module 901 in FIG. 9 can be implemented by the processor 201 in FIG. 2 calling a computer execution instruction stored in the memory 203.
  • the function/implementation process of the processing module 902 in FIG. 9 can be implemented by the processor 201 in FIG. 2 calling the computer execution instruction stored in the memory 203, and the function/implementation process of the transceiver module 901 in FIG.
  • the communication interface 204 in 2 is implemented.
  • the memory 203 may be a memory unit in a chip or a circuit, such as a register, a cache, or the like.
  • the memory 203 may be a storage unit located outside the chip in the terminal, which is not specifically limited in this embodiment of the present application.
  • the first communication device provided by the embodiment of the present application can be used to perform the above-mentioned communication capability reporting method. Therefore, the technical effects that can be obtained by reference to the foregoing method embodiments are not described herein.
  • FIG. 10 shows a schematic structural diagram of a second communication device 100.
  • the second communication device 100 may include the terminal in the foregoing embodiment, or may be the chip or circuit in the terminal in the foregoing embodiment, or may be the access device (such as gNB) in the foregoing embodiment, or may be the above
  • the chip system or circuit in the access device in the embodiment is not specifically limited in this embodiment of the present application.
  • the second communication device 100 includes: a receiving module 1001 and a sending module 1002.
  • the receiving module 1001 is configured to receive, by the first communications device, a capability identifier of the first communications device, where the capability identifier of the first communications device is one of the one or more capability identifiers corresponding to the first communications device;
  • the module 1002 is configured to send, to the network device, a capability identifier of the first communications device, where the capability identifier of the first communications device is used to determine a communication capability of the first communications device.
  • the capability identifier of the first communications device includes at least one component of the first IMEI.
  • the capability identifier of the first communications device includes at least one component of the first IMEI, including: 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 the first TAC and SNR in IMEI; or, the capability identification of the first communication device includes TAC, SNR, and SVN in the first IMEI; or, the capability identification of the first communication device includes TAC, SNR, and CD in the first IMEI.
  • the at least one component of the capability identifier of the first communications device is different from the at least one component of the second IMEI, wherein the second IMEI is an IMEI of the first communications device.
  • the first IMEI is an IMEI used by a vendor of the first communication device.
  • the capability identifier of the first communications device is different from the capability identifier of the third communications device, where the third communications device and the first communications device are communications devices of different vendors.
  • the receiving module 1001 is further configured to receive a communication capability of the first communications device that is sent by the network device.
  • the receiving module 1001 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, and the sending module 1002 is further configured to send the second message to the first communications device. a message, the second message is used to request the communication capability of the first communication device, and the receiving module 1001 is further configured to receive the communication capability of the first communication device sent by the first communication device.
  • the first message in the embodiment of the present application may carry the capability identifier of the first communication device, which is not specifically limited in this embodiment.
  • the second message in the embodiment of the present application may carry the capability identifier of the first communication device, which is not specifically limited in this embodiment of the present application.
  • the sending module 1002 is further configured to send, by the network device, a communication capability of the first communication device, where the network device stores a correspondence between the capability identifier of the first communication device and the communication capability of the first communication device.
  • the receiving module 1001 is further configured to receive a capability identifier of the first communications device that is sent by the first communications device and that corresponds to the communications capability of the first communications device.
  • the sending module 1002 is further configured to send, by the network device, the communication capability of the first communication device and the capability identifier of the first communication device corresponding to the communication capability of the first communication device, where the network device stores the first communication Correspondence between the capability identification of the device and the communication capability of the first communication device.
  • the receiving module 1001 is configured to receive the capability identifier of the first communications device that is sent by the first communications device, and is configured to: when the first communications device supports reporting the capability identifier of the first communications device, receiving the first communications The capability identifier of the first communication device sent by the device.
  • the receiving module 1001 is further configured to: when the first communications device does not support reporting the capability identifier of the first communications device, receive the indication information sent by the first communications device, where the indication information is used to indicate the first communications device.
  • the capability identification of the first communication device is not supported.
  • the receiving module 1001 is configured to receive the indication information sent by the first communications device, where the method includes: receiving, by the first communications device, a first RRC message or a first NAS message, where the first RRC message or the first NAS message includes Instructions.
  • the receiving module 1001 is configured to receive, by the first communications device, the capability identifier of the first communications device, where the method includes: receiving, by the first communications device, a second RRC message or a second NAS message, where the second RRC message is received.
  • the second NAS message includes a capability identifier of the first communication device.
  • the second communication device 100 is presented in a form that divides the various functional modules in an integrated manner.
  • a “module” herein may refer to a particular ASIC, circuitry, processor and memory that executes one or more software or firmware programs, integrated logic circuitry, and/or other devices that provide the functionality described above.
  • the second communication device 100 can take the form shown in FIG.
  • the processor 201 in FIG. 2 can execute the instruction by calling the computer stored in the memory 203, so that the second communication device 100 executes the communication capability reporting method in the foregoing method embodiment.
  • the function/implementation process of the receiving module 1001 and the transmitting module 1002 in FIG. 10 can be implemented by the processor 201 in FIG. 2 calling a computer executing instruction stored in the memory 203.
  • the function/implementation process of the receiving module 1001 and the transmitting module 1002 in FIG. 10 can be implemented by the communication interface 204 in FIG.
  • the memory 203 may be a memory unit in a chip or a circuit, such as a register, a cache, or the like.
  • the memory 203 may be a storage unit located outside the chip in the access device, which is not specifically limited in this embodiment of the present application.
  • the second communication device provided by the embodiment of the present application can be used to perform the above-mentioned communication capability reporting method. Therefore, the technical effects that can be obtained can be referred to the foregoing method embodiments, and details are not described herein again.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • a software program it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server or data center via wired (eg coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device that includes one or more servers, data centers, etc. that can be integrated with the media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)) or the like.
  • a magnetic medium eg, a floppy disk, a hard disk, a magnetic tape
  • an optical medium eg, a DVD
  • a semiconductor medium such as a solid state disk (SSD)

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供通信能力上报方法、设备及系统,使得在将通信设备的通信能力与通信设备的能力标识相关联的情况下,通信设备可以及时更新自己的通信能力。方法包括:第一通信设备确定该第一通信设备的能力标识,其中,该第一通信设备的能力标识为该第一通信设备对应的一个或多个能力标识中的其中一个标识;第一通信设备向第二通信设备发送该第一通信设备的能力标识,该第一通信设备的能力标识用于确定该第一通信设备的通信能力。

Description

通信能力上报方法、设备及系统 技术领域
本申请涉及通信技术领域,尤其涉及通信能力上报方法、设备及系统。
背景技术
目前,在现有的长期演进(long term evolution,LTE)中建立终端与演进的基站(evolved NodeB,eNB)之间的无线资源控制((radio resource control,RRC)连接通常包括以下三种场景:
场景一:终端从空闲(idle)态转换为连接(connected)态;
场景二:终端从一个eNB切换到另一个eNB;
场景三:终端初始注册到网络。
其中,对于场景一和场景二,在建立RRC连接之后,由于移动管理实体(mobility management entity,MME)中存储有该终端的通信能力,因此MME可以将该终端的通信能力发给eNB,此时终端不需要上报该终端的通信能力。对于场景三,在建立RRC连接之后,由于MME中未存储该终端的通信能力,因此MME会向该终端发起能力上报请求,以使得终端上报该终端的通信能力。
然而,在第三代合作伙伴计划(英文全称:The 3rd Generation Partnership Project,英文缩写:3GPP)第五代(5th generation,5G)新空口(new radio,NR)系统中,终端的通信能力上报所需要的参数很多,上报的数据量比LTE要大很多,因此现有技术中提出了一种将终端的通信能力与终端的能力标识相关联的方法,使得接入设备或者网络设备根据终端的能力标识,即可确定终端的通信能力。其中,该终端的能力标识根据终端的国际移动设备识别码(international mobile equipment identity,IMEI)确定,比如可以为终端的国际移动设备识别码(international mobile equipment identity,IMEI)中的类型分配码(type allocation code,TAC)和软件版本号(software version number,SVN)。
但是,上述方案存在如下问题:若终端的软件刷新,硬件并未发生改变(也就是说终端的IMSI未发生改变),但是终端的通信能力发生了变化,此时由于终端的能力标识并未发生变化,因此终端将无法更新自己的通信能力。比如,在终端的软件版本升级导致了终端的通信能力发生了改变的情况下;或者,比如,在全球认证论坛(global certification forum,GCF)/协议认证/修改软件版本导致了终端的通信能力发生了改变的情况下;或者,在后期软件维护导致了终端的通信能力发生了改变的情况下,等等,若采用上述终端能力上报方法,均导致终端无法更新自己的通信能力。
因此,如何提供一种通信能力上报方法,使得在将通信设备的通信能力与通信设备的能力标识相关联的情况下,通信设备可以及时更新自己的通信能力,是目前亟待解决的技术问题。
发明内容
本申请实施例提供通信能力上报方法、设备及系统,使得在将通信设备的通信能力与通信设备的能力标识相关联的情况下,通信设备可以及时更新自己的通信能力。
为达到上述目的,本申请的实施例采用如下技术方案:
第一方面,提供了一种通信能力上报的方法,包括:第一通信设备确定该第一通信设备的能力标识,其中,该第一通信设备的能力标识为该第一通信设备对应的一个或多个能力标识中的其中一个标识;第一通信设备向第二通信设备发送该第一通信设备的能力标识,该第一通信设备的能力标识用于确定该第一通信设备的通信能力。基于该方案,由于在需要进行能力上报时,第一通信设备向第二通信设备发送的第一通信设备的能力标识为第一通信设备对应的一个或者多个能力标识中的其中一个标识。也就是说, 本申请实施例中,对于第一通信设备,可以使用不同的能力标识,因此在将第一通信设备的通信能力与第一通信设备的能力标识相关联的情况下,第一通信设备可以使用从第一通信设备对应的一个或者多个能力标识中确定的能力标识及时更新自己的通信能力。
在一种可能的设计中,该第一通信设备的能力标识包括第一国际移动设备识别码IMEI的至少一个组成部分。比如,该第一通信设备的能力标识包括该第一IMEI中的类型分配码TAC;或者,该第一通信设备的能力标识包括该第一IMEI中的TAC和序列号SNR;或者,该第一通信设备的能力标识包括该第一IMEI中的TAC、SNR以及软件版本号SVN;或者,该第一通信设备的能力标识包括该第一IMEI中的TAC、SNR以及验证码CD,等等,本申请实施例对此不作具体限定。
在一种可能的设计中,该第一通信设备的能力标识的至少一个组成部分与第二IMEI的至少一个组成部分不同,其中,该第二IMEI为该第一通信设备的IMEI。这样,可以将第一通信设备的能力标识与第一通信设备的IMEI进行区分。
在一种可能的设计中,该第一IMEI是该第一通信设备所属厂商使用的IMEI。这样,在不同厂商维护的IMEI不同的情况下,第二通信设备或者核心网中的网络设备可以根据通信设备的能力标识区分不同厂商的通信设备,从而做到差异化竞争。
在一种可能的设计中,该第一通信设备的能力标识与第三通信设备的能力标识不同,其中,该第三通信设备和该第一通信设备为不同厂商的通信设备。也就是说,不同厂商维护的通信设备的能力标识不同,这样第二通信设备或者核心网中的网络设备可以根据通信设备的能力标识区分不同厂商的通信设备,从而做到差异化竞争。
在一种可能的设计中,第一通信设备向第二通信设备发送该第一通信设备的能力标识,包括:第一通信设备向该第二通信设备发送第一无线资源控制RRC消息或第一非接入层NAS消息,该第一RRC消息或第一NAS消息包括该第一通信设备的能力标识。也就是说,第一通信设备可以通过现有的RRC消息或NAS消息将第一通信设备的能力标识上报给第二通信设备,不需要增加新的信令,从而节省了系统资源。
在一种可能的设计中,该第一通信设备确定该第一通信设备的能力标识,包括:在该第一通信设备支持上报该第一通信设备的能力标识的情况下,该第一通信设备确定该第一通信设备的能力标识。这样可以避免第一通信设备不支持上报该第一通信设备的能力标识时方案无法实现。
在一种可能的设计中:在第一通信设备不支持上报该第一通信设备的能力标识的情况下,第一通信设备向该第二通信设备发送指示信息,由第二通信设备将该指示信息发送给核心网中的网络设备。其中,该指示信息用于指示该第一通信设备不支持上报该第一通信设备的能力标识。这样,核心网中的网络设备可以获知该第一通信设备不支持上报第一通信设备的能力标识,从而不会根据该第一通信设备的能力标识查找对应的第一通信设备的通信能力,而是在根据第一通信设备的标识获知该网络设备中未存储该第一通信设备的通信能力时,向该第一通信设备查询该第一通信设备的通信能力,使得第一通信设备再上报该第一通信设备的通信能力。也就是说,基于该方案,可以实现不支持通信设备的能力标识上报的通信设备的通信能力的上报。
在一种可能的设计中,第一通信设备向该第二通信设备发送指示信息,包括:第一通信设备向第二通信设备发送第二RRC消息或第二NAS消息,该第二RRC消息或第二NAS消息包括该指示信息。也就是说,第一通信设备可以通过现有的RRC消息或NAS消息将上述指示信息给第二通信设备,不需要增加新的信令,从而节省了系统资源。
第二方面,提供了一种通信能力上报的方法,包括:第二通信设备接收第一通信设备发送的该第一通信设备的能力标识,其中,该第一通信设备的能力标识为该第一通信设备对应的一个或多个能力标识 中的其中一个标识;第二通信设备向网络设备发送该第一通信设备的能力标识,该第一通信设备的能力标识用于确定该第一通信设备的通信能力。基于该方案,由于在需要进行能力上报时,第一通信设备向第二通信设备发送的第一通信设备的能力标识为第一通信设备对应的一个或者多个能力标识中的其中一个标识。也就是说,本申请实施例中,对于第一通信设备,可以使用不同的能力标识,因此在将第一通信设备的通信能力与第一通信设备的能力标识相关联的情况下,第一通信设备可以使用从第一通信设备对应的一个或者多个能力标识中确定的能力标识及时更新自己的通信能力。
在一种可能的设计中,该第一通信设备的能力标识包括第一国际移动设备识别码IMEI的至少一个组成部分。比如,该第一通信设备的能力标识包括该第一IMEI中的类型分配码TAC;或者,该第一通信设备的能力标识包括该第一IMEI中的TAC和序列号SNR;或者,该第一通信设备的能力标识包括该第一IMEI中的TAC、SNR以及软件版本号SVN;或者,该第一通信设备的能力标识包括该第一IMEI中的TAC、SNR以及验证码CD,等等,本申请实施例对此不作具体限定。
在一种可能的设计中,该第一通信设备的能力标识的至少一个组成部分与第二IMEI的至少一个组成部分不同,其中,该第二IMEI为该第一通信设备的IMEI。这样,可以将第一通信设备的能力标识与第一通信设备的IMEI进行区分。
在一种可能的设计中,该第一IMEI是该第一通信设备所属厂商使用的IMEI。这样,在不同厂商维护的IMEI不同的情况下,第二通信设备或者核心网中的网络设备可以根据通信设备的能力标识区分不同厂商的通信设备,从而做到差异化竞争。
在一种可能的设计中,该第一通信设备的能力标识与第三通信设备的能力标识不同,其中,该第三通信设备和该第一通信设备为不同厂商的通信设备。也就是说,不同厂商维护的通信设备的能力标识不同,这样第二通信设备或者核心网中的网络设备可以根据通信设备的能力标识区分不同厂商的通信设备,从而做到差异化竞争。
在一种可能的设计中,本申请实施例提供的通信能力上报方法还可以包括:第二通信设备接收网络设备发送的该第一通信设备的通信能力。也就是说,网络设备中可以存储与第一通信设备的能力标识对应的第一通信设备的通信能力,进而网络设备获取第一通信设备的能力标识之后,可以根据第一通信设备的能力标识查询第一通信设备的通信能力,进而将第一通信设备的通信能力发送给第二通信设备。
在一种可能的设计中,本申请实施例提供的通信能力上报方法还可以包括:第二通信设备接收网络设备发送的第一消息,该第一消息用于请求该第一通信设备的通信能力;第二通信设备向第一通信设备发送第二消息,该第二消息用于请求该第一通信设备的通信能力;第二通信设备接收第一通信设备发送的该第一通信设备的通信能力。也就是说,若网络设备中未存储与第一通信设备的能力标识对应的第一通信设备的通信能力,则网络设备可以通过第二通信设备向第一通信设备查询第一通信设备的通信能力,进而第一通信设备可以将第一通信设备的通信能力上报给第二网络设备。
可选的,本申请实施例中的第一消息中可以携带第一通信设备的能力标识,本申请实施例对此不作具体限定。
可选的,本申请实施例中的第二消息中可以携带第一通信设备的能力标识,本申请实施例对此不作具体限定。
在一种可能的设计中,本申请实施例提供的通信能力上报方法还可以包括:第二通信设备向网络设备发送该第一通信设备的通信能力,由该网络设备存储该第一通信设备的能力标识和该第一通信设备的通信能力的对应关系。这样,后续若有该第一通信设备或者其他通信设备上报该能力标识,则网络设备可以直接根据该能力标识、以及存储的该能力标识和通信能力的对应关系,确定出与该能力标识对应的通信能力。
在一种可能的设计中,本申请实施例提供的通信能力上报方法还可以包括:第二通信设备接收第一通信设备发送的与第一通信设备的通信能力对应的第一通信设备的能力标识。也就是说,本申请实施例中,在第一通信设备上报通信能力时,可以将通信能力与能力标识一起上报,以使得第二通信设备或者后续的网络设备可以获知该通信能力为哪个通信标识对应的通信能力。
在一种可能的设计中,本申请实施例提供的通信能力上报方法还可以包括:第二通信设备向网络设备发送第一通信设备的通信能力和与该第一通信设备的通信能力对应的第一通信设备的能力标识,由网络设备存储该第一通信设备的能力标识和该第一通信设备的通信能力的对应关系。这样,后续若有该第一通信设备或者其他通信设备上报该能力标识,则网络设备可以直接根据该能力标识、以及存储的该能力标识和通信能力的对应关系,确定出与该能力标识对应的通信能力。
在一种可能的设计中,第二通信设备接收第一通信设备发送的第一通信设备的能力标识,包括:在第一通信设备支持上报该第一通信设备的能力标识的情况下,第二通信设备接收第一通信设备发送的该第一通信设备的能力标识。这样可以避免第一通信设备不支持上报该第一通信设备的能力标识时方案无法实现。
在一种可能的设计中,本申请实施例提供的通信能力上报方法还可以包括:在第一通信设备不支持上报该第一通信设备的能力标识的情况下,第二通信设备接收第一通信设备发送的指示信息,并将该指示信息发送给核心网中的网络设备。其中,该指示信息用于指示第一通信设备不支持上报该第一通信设备的能力标识。这样,核心网中的网络设备可以获知该第一通信设备不支持上报第一通信设备的能力标识,从而不会根据该第一通信设备的能力标识查找对应的第一通信设备的通信能力,而是在根据第一通信设备的标识获知该网络设备中未存储该第一通信设备的通信能力时,向该第一通信设备查询该第一通信设备的通信能力,使得第一通信设备再上报该第一通信设备的通信能力。也就是说,基于该方案,可以实现不支持通信设备的能力标识上报的通信设备的通信能力的上报。
在一种可能的设计中,第二通信设备接收该第一通信设备发送的指示信息,包括:第二通信设备接收第一通信设备发送的第一无线资源控制RRC消息或第一非接入层NAS消息,该第一RRC消息或第一NAS消息包括该指示信息。也就是说,第一通信设备可以通过现有的RRC消息或NAS消息将上述指示信息给第二通信设备,不需要增加新的信令,从而节省了系统资源。
在一种可能的设计中,第二通信设备接收第一通信设备发送的该第一通信设备的能力标识,包括:第二通信设备接收第一通信设备发送的第二RRC消息或第二NAS消息,该第二RRC消息或第二NAS消息包括该第一通信设备的能力标识。也就是说,第一通信设备可以通过现有的RRC消息或NAS消息将第一通信设备的能力标识上报给第二通信设备,不需要增加新的信令,从而节省了系统资源。
第三方面,提供了一种第一通信设备,该第一通信设备具有实现上述第一方面任一项所述的方法的功能。该功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
示例性的,第一通信设备包括:处理模块和收发模块;该处理模块,用于确定该第一通信设备的能力标识,其中,该第一通信设备的能力标识为该第一通信设备对应的一个或多个能力标识中的其中一个标识;该收发模块,用于向第二通信设备发送该第一通信设备的能力标识,该第一通信设备的能力标识用于确定该第一通信设备的通信能力。
在一种可能的设计中,该第一通信设备的能力标识包括第一国际移动设备识别码IMEI的至少一个组成部分。
在一种可能的设计中,该第一通信设备的能力标识包括第一IMEI的至少一个组成部分,包括:该第一通信设备的能力标识包括该第一IMEI中的类型分配码TAC;或者,该第一通信设备的能力标识包 括该第一IMEI中的TAC和序列号SNR;或者,该第一通信设备的能力标识包括该第一IMEI中的TAC、SNR以及软件版本号SVN;或者,该第一通信设备的能力标识包括该第一IMEI中的TAC、SNR以及验证码CD。
在一种可能的设计中,该第一通信设备的能力标识的至少一个组成部分与第二IMEI的至少一个组成部分不同,其中,该第二IMEI为该第一通信设备的IMEI。
在一种可能的设计中,该第一IMEI是该第一通信设备所属厂商使用的IMEI。
在一种可能的设计中,该第一通信设备的能力标识与第三通信设备的能力标识不同,其中,该第三通信设备和该第一通信设备为不同厂商的通信设备。
在一种可能的设计中,该收发模块具体用于:向该第二通信设备发送第一无线资源控制RRC消息或第一非接入层NAS消息,该第一RRC消息或第一NAS消息包括该第一通信设备的能力标识。
在一种可能的设计中,该处理模块具体用于:在该第一通信设备支持上报该第一通信设备的能力标识的情况下,确定该第一通信设备的能力标识。
在一种可能的设计中,该收发模块,还用于在该第一通信设备不支持上报该第一通信设备的能力标识的情况下,向该第二通信设备发送指示信息,由第二通信设备将该指示信息发送给核心网中的网络设备。其中,该指示信息用于指示该第一通信设备不支持上报该第一通信设备的能力标识。
在一种可能的设计中,该收发模块用于向该第二通信设备发送指示信息,包括:用于向该第二通信设备发送第二RRC消息或第二NAS消息,该第二RRC消息或第二NAS消息包括该指示信息。
第四方面,提供了一种第一通信设备,包括:处理器和存储器;该存储器用于存储计算机执行指令,当该第一通信设备运行时,该处理器执行该存储器存储的该计算机执行指令,以使该第一通信设备执行如上述第一方面中任一项所述的通信能力上报方法。
第五方面,提供了一种第一通信设备,包括:处理器;所述处理器用于与存储器耦合,并读取存储器中的指令之后,根据所述指令执行如上述第一方面中任一项所述的通信能力上报方法。
第六方面,提供了一种计算机可读存储介质,该计算机可读存储介质中存储有指令,当其在计算机上运行时,使得计算机可以执行上述第一方面中任一项所述的通信能力上报方法。
第七方面,提供了一种包含指令的计算机程序产品,当其在计算机上运行时,使得计算机可以执行上述第一方面中任一项所述的通信能力上报方法。
可选的,第三方面至第七方面中的第一通信设备可以为终端,也可以为终端内的芯片系统或者电路等,该芯片系统,可以由芯片构成,也可以包含芯片和其他分立器件,本申请实施例对此不作具体限定。
其中,第三方面至第七方面中任一种设计方式所带来的技术效果可参见第一方面中不同设计方式所带来的技术效果,此处不再赘述。
第八方面,提供了一种第二通信设备,该第二通信设备具有实现上述第二方面任一项所述的方法的功能。该功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块。
示例性的,第二通信设备包括接收模块和发送模块;该接收模块,用于接收第一通信设备发送的该第一通信设备的能力标识,其中,该第一通信设备的能力标识为该第一通信设备对应的一个或多个能力标识中的其中一个标识;该发送模块,用于向网络设备发送该第一通信设备的能力标识,该第一通信设备的能力标识用于确定该第一通信设备的通信能力。
在一种可能的设计中,该第一通信设备的能力标识包括第一国际移动设备识别码IMEI的至少一个组成部分。
在一种可能的设计中,该第一通信设备的能力标识包括第一IMEI的至少一个组成部分,包括:该 第一通信设备的能力标识包括该第一IMEI中的类型分配码TAC;或者,该第一通信设备的能力标识包括该第一IMEI中的TAC和序列号SNR;或者,该第一通信设备的能力标识包括该第一IMEI中的TAC、SNR以及软件版本号SVN;或者,该第一通信设备的能力标识包括该第一IMEI中的TAC、SNR以及验证码CD。
在一种可能的设计中,该第一通信设备的能力标识的至少一个组成部分与第二IMEI的至少一个组成部分不同,其中,该第二IMEI为该第一通信设备的IMEI。
在一种可能的设计中,该第一IMEI是该第一通信设备所属厂商使用的IMEI。
在一种可能的设计中,该第一通信设备的能力标识与第三通信设备的能力标识不同,其中,该第三通信设备和该第一通信设备为不同厂商的通信设备。
在一种可能的设计中,该接收模块,还用于接收该网络设备发送的该第一通信设备的通信能力。
在一种可能的设计中,该接收模块,还用于接收该网络设备发送的第一消息,该第一消息用于请求该第一通信设备的通信能力;该发送模块,还用于向该第一通信设备发送第二消息,该第二消息用于请求该第一通信设备的通信能力;该接收模块,还用于接收该第一通信设备发送的该第一通信设备的通信能力。
可选的,本申请实施例中的第一消息中可以携带第一通信设备的能力标识,本申请实施例对此不作具体限定。
可选的,本申请实施例中的第二消息中可以携带第一通信设备的能力标识,本申请实施例对此不作具体限定。
在一种可能的设计中,该发送模块,还用于向该网络设备发送该第一通信设备的通信能力,由该网络设备存储该第一通信设备的能力标识和该第一通信设备的通信能力的对应关系。
在一种可能的设计中,该接收模块,还用于接收第一通信设备发送的与第一通信设备的通信能力对应的第一通信设备的能力标识。
在一种可能的设计中,该发送模块,还用于向网络设备发送第一通信设备的通信能力和与该第一通信设备的通信能力对应的第一通信设备的能力标识,由网络设备存储该第一通信设备的能力标识和该第一通信设备的通信能力的对应关系。
在一种可能的设计中,该接收模块用于接收第一通信设备发送的该第一通信设备的能力标识,包括:用于在该第一通信设备支持上报该第一通信设备的能力标识的情况下,接收第一通信设备发送的该第一通信设备的能力标识。
在一种可能的设计中,该接收模块,还用于在该第一通信设备不支持上报该第一通信设备的能力标识的情况下,接收该第一通信设备发送的指示信息,并将该指示信息发送给核心网中的网络设备,该指示信息用于指示该第一通信设备不支持上报该第一通信设备的能力标识。
在一种可能的设计中,该接收模块用于接收该第一通信设备发送的指示信息,包括:用于接收该第一通信设备发送的第一无线资源控制RRC消息或第一非接入层NAS消息,该第一RRC消息或第一NAS消息包括该指示信息。
在一种可能的设计中,该接收模块用于接收第一通信设备发送的该第一通信设备的能力标识,包括:用于接收该第一通信设备发送的第二RRC消息或第二NAS消息,该第二RRC消息或第二NAS消息包括该第一通信设备的能力标识。
第九方面,提供了一种第二通信设备,包括:处理器和存储器;该存储器用于存储计算机执行指令,当该第二通信设备运行时,该处理器执行该存储器存储的该计算机执行指令,以使该第二通信设备执行如上述第二方面中任一项所述的通信能力上报方法。
第十方面,提供了一种第二通信设备,包括:处理器;所述处理器用于与存储器耦合,并读取存储器中的指令之后,根据所述指令执行如上述第二方面中任一项所述的通信能力上报方法。
第十一方面,提供了一种计算机可读存储介质,该计算机可读存储介质中存储有指令,当其在计算机上运行时,使得计算机可以执行上述第二方面中任一项所述的通信能力上报方法。
第十二方面,提供了一种包含指令的计算机程序产品,当其在计算机上运行时,使得计算机可以执行上述第二方面中任一项所述的通信能力上报方法。
可选的,第八方面至第十二方面中的第二通信设备可以为终端,也可以为终端内的芯片系统或者电路等,也可以为接入设备,也可以为接入设备内的芯片系统或者电路,该芯片系统,可以由芯片构成,也可以包含芯片和其他分立器件,本申请实施例对此不作具体限定。
其中,第八方面至第十二方面中任一种设计方式所带来的技术效果可参见第一方面中不同设计方式所带来的技术效果,此处不再赘述。
第十三方面,提供了一种通信系统,该通信系统包括网络设备、上述任一方面所述的第二通信设备、以及一个或者多个上述任一方面所述的第一通信设备。相关描述可参考上述实施例,在此不再赘述。
本申请的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
图1为本申请实施例提供的一种通信系统的结构示意图;
图2为本申请实施例提供的接入设备和通信设备的硬件结构示意图;
图3为本申请实施例提供的通信能力上报方法流程示意图一;
图4为本申请实施例提供的终端的能力标识与终端的通信能力的维护示意图;
图5为本申请实施例提供的IMEI的格式一;
图6为本申请实施例提供的IMEI的格式二;
图7为本申请实施例提供的第一IMEI和第二IMEI的示例;
图8为本申请实施例提供的通信能力上报方法流程示意图二;
图9为本申请实施例提供的第一通信设备的结构示意图;
图10为本申请实施例提供的第二通信设备的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行描述。其中,在本申请的描述中,除非另有说明,“/”表示或的意思,例如,A/B可以表示A或B;本文中的“和/或”仅仅是一种描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。并且,在本申请的描述中,除非另有说明,“多个”是指两个或多于两个。另外,为了便于清楚描述本申请实施例的技术方案,在本申请的实施例中,采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定,并且“第一”、“第二”等字样也并不限定一定不同。
此外,本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案,并不构成对于本申请实施例提供的技术方案的限定,本领域普通技术人员可知,随着网络架构的演变和新业务场景的出现,本申请实施例提供的技术方案对于类似的技术问题,同样适用。
如图1所示,为本申请实施例提供的一种通信系统10。该通信系统10包括第二通信设备101,与第二通信设备101连接的网络设备103、以及与第二通信设备101连接的一个或多个第一通信设备102。下 面以第二通信设备101与网络设备103、以及任一第一通信设备102进行交互为例进行说明。
其中,第一通信设备102,用于确定该第一通信设备102的能力标识,该第一通信设备102的能力标识为第一通信设备102对应的一个或多个能力标识中的其中一个标识。
第一通信设备102,还用于向第二通信设备101发送该第一通信设备102的能力标识。
第二通信设备101,用于接收第一通信设备102发送的第一通信设备102的能力标识,并向网络设备103发送该第一通信设备102的能力标识。
网络设备103,用于接收第二通信设备101发送的该第一通信设备102的能力标识,并根据该第一通信设备102的能力标识,确定该第一通信设备102的通信能力。
可选的,本申请实施例中的通信能力例如可以包括接入能力、或者处理能力等,在此统一说明,以下不再赘述。
可选的,本申请实施例中的第一通信设备102与第二通信设备101之间可以直接通信,也可以通过其他设备的转发进行通信,本申请实施例对此不作具体限定。
可选的,本申请实施例中的网络设备103与第二通信设备101之间可以直接通信,也可以通过其他设备的转发进行通信,本申请实施例对此不作具体限定。
可选的,本申请实施例中的第一通信设备102可以是终端或者终端内的芯片系统或电路等,本申请实施例对此不作具体限定。其中,本申请实施例中的芯片系统,可以由芯片构成,也可以包括芯片和其他分立器件,在此统一说明,本申请实施例对此不作具体限定。
可选的,本申请实施例中的第二通信设备101可以是终端、终端内的芯片系统或电路、接入设备或者接入设备内的芯片系统或电路等,本申请实施例对此不作具体限定。
可选的,本申请实施例中的网络设备103可以是移动管理网元或者该移动管理网元内的芯片系统或电路等,本申请实施例对此不作具体限定。
其中,本申请实施例中所涉及到的终端(terminal)可以包括NR系统或者未来演进的公共陆地移动网络(public land mobile network,PLMN)中的各种具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备;还可以包括用户单元(subscriber unit)、蜂窝电话(cellular phone)、智能电话(smart phone)、无线数据卡、个人数字助理(personal digital assistant,PDA)电脑、平板型电脑、无线调制解调器(modem)、手持设备(handheld)、膝上型电脑(laptop computer)、无绳电话(cordless phone)或者无线本地环路(wireless local loop,WLL)台、机器类型通信(machine type communication,MTC)终端、用户设备(user equipment,UE),移动台(mobile station,MS),终端设备(terminal device)或者中继用户设备等。其中,中继用户设备例如可以是5G家庭网关(residential gateway,RG)。为方便描述,本申请中,上面提到的设备统称为终端。
其中,本申请实施例中所涉及到的接入设备指的是接入核心网的设备,例如可以是5G NR系统或者未来PLMN中的基站,宽带网络业务网关(broadband network gateway,BNG),汇聚交换机、非3GPP接入设备等。基站可以包括各种形式的基站,例如:微基站(也称为小站),宏基站,中继站,接入点或者5G NR系统中的NR节点B(NR NodeB,gNB)等,本申请实施例对此不作具体限定。
其中,本申请实施例中所涉及到的移动管理网元例如可以是5G NR系统中的接入和移动性管理功能(access and mobility management function,AMF)网元或者未来演进的PLMN中的其他移动管理网元,本申请实施例对此不作具体限定。
此外,上述方案的具体实现将在下述实施例中详细阐述,在此不再赘述。
基于本申请实施例提供的通信系统,由于在需要进行能力上报时,第一通信设备向第二通信设备发送的第一通信设备的能力标识为第一通信设备对应的一个或者多个能力标识中的其中一个标识。也就是 说,本申请实施例中,对于第一通信设备,可以使用不同的能力标识,因此在将第一通信设备的通信能力与第一通信设备的能力标识相关联的情况下,第一通信设备可以使用从第一通信设备对应的一个或者多个能力标识中确定的能力标识及时更新自己的通信能力。
可选的,本申请实施例图1中的第一通信设备或者第二通信设备可以由一个设备实现,也可以由多个设备共同实现,还可以是一个设备内的一个功能模块,本申请实施例对此不作具体限定。可以理解的是,上述功能既可以是硬件设备中的网络元件,也可以是在专用硬件上运行的软件功能,或者是平台(例如,云平台)上实例化的虚拟化功能。
例如,本申请实施例图1中的第一通信设备或者第二通信设备可以通过图2中的通信设备来实现。图2所示为本申请实施例提供的通信设备的硬件结构示意图。该通信设备200包括至少一个处理器201,通信线路202,存储器203以及至少一个通信接口204。
处理器201可以是一个通用中央处理器(central processing unit,CPU),微处理器,特定应用集成电路(application-specific integrated circuit,ASIC),或一个或多个用于控制本申请方案程序执行的集成电路。
通信线路202可包括一通路,在上述组件之间传送信息。
通信接口204,使用任何收发器一类的装置,用于与其他设备或通信网络通信,如以太网,无线接入网(radio access network,RAN),无线局域网(wireless local area networks,WLAN)等。
存储器203可以是只读存储器(read-only memory,ROM)或可存储静态信息和指令的其他类型的静态存储设备,随机存取存储器(random access memory,RAM)或者可存储信息和指令的其他类型的动态存储设备,也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory,EEPROM)、只读光盘(compact disc read-only memory,CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质,但不限于此。存储器可以是独立存在,通过通信线路202与处理器相连接。存储器也可以和处理器集成在一起。
其中,存储器203用于存储执行本申请方案的计算机执行指令,并由处理器201来控制执行。处理器201用于执行存储器203中存储的计算机执行指令,从而实现本申请下述实施例提供的通信能力上报方法。
可选的,本申请实施例中的计算机执行指令也可以称之为应用程序代码,本申请实施例对此不作具体限定。
在具体实现中,作为一种实施例,处理器201可以包括一个或多个CPU,例如图2中的CPU0和CPU1。
在具体实现中,作为一种实施例,通信设备200可以包括多个处理器,例如图2中的处理器201和处理器208。这些处理器中的每一个可以是一个单核(single-CPU)处理器,也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中,作为一种实施例,通信设备200还可以包括输出设备205和输入设备206。输出设备205和处理器201通信,可以以多种方式来显示信息。例如,输出设备205可以是液晶显示器(liquid crystal display,LCD),发光二级管(light emitting diode,LED)显示设备,阴极射线管(cathode ray tube,CRT)显示设备,或投影仪(projector)等。输入设备206和处理器201通信,可以以多种方式接收用户的输入。例如,输入设备206可以是鼠标、键盘、触摸屏设备或传感设备等。
上述的通信设备200可以是一个通用设备或者是一个专用设备。在具体实现中,通信设备200可以是上述的终端、接入设备、芯片系统或有图2中类似结构的设备。本申请实施例不限定通信设备200的类型。
下面将结合图1和图2,以图1所示的通信系统应用于目前的5G NR系统,第一通信设备为5G NR系统中的一个终端,第二通信设备为5G NR系统中的gNB,网络设备为5G NR系统中的AMF网元为例,对本申请实施例提供的通信能力上报方法进行展开说明。
需要说明的是,本申请下述实施例中各个网元之间的消息名字或消息中各参数的名字等只是一个示例,具体实现中也可以是其他的名字,本申请实施例对此不作具体限定。
如图3所示,为本申请实施例提供的一种能力上报方法,该能力上报方法包括如下步骤:
S301、终端向gNB发送随机接入前导(random access preamble),以使得gNB接收终端发送的随机接入前导。
S302、gNB向终端发送随机接入响应(random access response),以使得终端接收gNB发送的随机接入响应。
其中,步骤S301和S302的相关实现可参考现有的实现方式,在此不再赘述。
S303、终端确定该终端的能力标识,其中,该终端的能力标识为该终端对应的一个或多个能力标识中的其中一个标识。
可选的,本申请实施例中,终端对应的一个或多个能力标识可以是预先存储在终端上的,也可以是在需要进行通信能力上报时,终端根据算法计算出来的,还可以是终端通过其他方式获取的,本申请实施例对此不作具体限定。
可选的,本申请实施例中,在将终端的通信能力与终端的能力标识相关联的情况下,为了避免不同终端厂商之间的终端能力相冲突,通常给不同终端厂商分配的多个终端的能力标识是不同的。也就是说,对于每个终端厂商,需要维护多个不同于其它终端厂商的终端的能力标识、以及与每个终端的能力标识对应的终端的通信能力,这样gNB或者AMF网元可以根据终端的能力标识区分不同厂商的终端,从而做到差异化竞争。
可选的,本申请实施例中的一个或者多个能力标识可以构成一个能力标识集合或者一个能力标识列表等,本申请实施例对此不作具体限定。
示例性的,如图4所示,A终端厂商可以维护一个或多个终端的能力标识,例如可以包括能力标识A1、能力标识A2、能力标识A3、……、能力标识An;B终端厂商可以维护一个或多个终端的能力标识,例如可以包括能力标识B1、能力标识B2、能力标识B3、……、能力标识Bn。A终端厂商维护的每个终端的能力标识对应的终端的通信能力可以分别为:能力标识A1对应通信能力A11、能力标识A2对应通信能力A21、能力标识A3对应通信能力A31、……、能力标识An对应通信能力An1;B终端厂商维护的每个终端的能力标识对应的终端的通信能力可以分别为:能力标识B1对应通信能力B11、能力标识B2对应通信能力B21、能力标识B3对应通信能力B31、……、能力标识Bn对应通信能力Bn1。其中,能力标识A1、能力标识A2、能力标识A3、……、能力标识An与能力标识B1、能力标识B2、能力标识B3、……、能力标识Bn不相同;能力标识A1对应的通信能力A11、能力标识A2对应的通信能力A21、能力标识A3对应的通信能力A31、……、能力标识An对应的通信能力An1与能力标识B1对应的通信能力B11、能力标识B2对应的通信能力B21、能力标识B3对应的通信能力B31、……、能力标识Bn对应的通信能力Bn1可能相同,也可能不相同,本申请实施例对此不作具体限定。这样,在将终端的通信能力与终端的能力标识相关联的情况下,gNB或者AMF网元可以根据不同的终端的能力标识区分不同厂商的终端,从而做到差异化竞争。比如,若gNB获取到某一终端的能力标识为B1,则 可以根据该终端的能力标识B1获知是该终端为B终端厂商的终端。
可选的,本申请实施例中,对于某一个终端厂商的每个终端,也需要维护一个或多个终端的能力标识、以及与每个终端的能力标识对应的终端的通信能力。其中,终端维护的一个或者多个终端的能力标识为终端所属的终端厂商所维护的一个或者多个终端的能力标识中的标识。也就是说,假设一个或者多个能力标识可以构成一个能力标识集合,则该终端对应的一个或多个终端的能力标识构成的集合通常为该终端所属的终端厂商维护的终端的能力标识集合的子集。此外,对于同一个终端厂商的不同终端维护的一个或多个终端的能力标识可以有重叠,也可以没有重叠,本申请实施例对此不作具体限定。
比如,在图4中,A终端厂商的终端1可以维护能力标识A1和能力标识A2;A终端厂商的终端2可以维护能力标识A2和能力标识A3,其中,A终端厂商的终端1和A终端厂商的终端2维护的终端的能力标识有重叠,为能力标识2。
或者,在图4中,B终端厂商的终端3可以维护能力标识B1和能力标识B2;B终端厂商的终端4可以维护能力标识B3、……,其中,B终端厂商的终端3和B终端厂商的终端4维护的终端的能力标识没有重叠。
综上,由于每个终端厂商均维护多个不同于其它终端厂商的终端的能力标识,而终端厂商的终端对应的一个或多个能力标识为该终端厂商维护的一个或多个能力标识中的标识,因此,为了区分不同厂商的终端,不同终端厂商的终端对应的一个或多个能力标识是不重叠的,在此统一说明,以下不再赘述。
可选的,本申请实施例中,对于某一个终端厂商的某一个终端对应的一个或多个能力标识以及与每个终端的能力标识对应的终端的通信能力是可以软件更新的,比如,在终端的软件版本升级导致了终端的通信能力发生了改变的情况下;或者,在GCF/协议认证/修改软件版本导致了终端的通信能力发生了改变的情况下;或者,在后期软件维护导致了终端的通信能力发生了改变的情况下,等等,均可以更新该终端对应的一个或多个能力标识以及与每个终端的能力标识对应的终端的通信能力。
示例性的,假设如图4所示,A终端厂商的终端1中原来维护能力标识A1和能力标识A2,在终端1的软件版本升级导致了终端1的通信能力发生了改变的情况下;或者,在GCF/协议认证/修改软件版本导致了终端1的通信能力发生了改变的情况下;或者,在后期软件维护导致了终端1的通信能力发生了改变的情况下,等等,均可以导致A终端厂商的终端1维护的能力标识A1和能力标识A2进行更新,比如更新为终端1维护能力标识A3和能力标识An,其中,在A终端厂商的终端1维护的能力标识更新行为能力标识A3和能力标识An的情况下,A终端厂商的终端1维护的终端的通信能力也分别更新为与能力标识A3对应的通信能力A31和与能力标识An对应的通信能力An1,在此统一说明,以下不再赘述。
可选的,本申请实施例中,该终端的能力标识可以有多种表征形式,下面对该终端的能力标识的表征形式进行说明如下:
比如,该终端的能力标识包括第一IMEI的至少一个组成部分。
假设第一IMEI的格式可以如图5所示,包括8位数字的TAC字段、6位数字的序列号(serial number,SNR)字段和1位数字的验证码(check digit,CD)字段,则该终端的能力标识包括第一IMEI的至少一个组成部分,包括:终端的能力标识包括第一IMEI中的TAC;或者,终端的能力标识包括第一IMEI中的TAC和SNR;或者,终端的能力标识包括第一IMEI中的TAC、SNR和CD,本申请实施例对此不作具体限定。
或者,假设第一IMEI的格式可以如图6所示,包括8位数字的TAC字段、6位数字的SNR字段和2位数字的SVN字段,则该终端的能力标识包括第一IMEI的至少一个组成部分,包括:终端的能力标识包括第一IMEI中的TAC;或者,终端的能力标识包括第一IMEI中的TAC和SNR;或者,终端的能力标识包括第一IMEI中的TAC、SNR和SVN,本申请实施例对此不作具体限定。
其中,图5或者图6中的TAC是用于区分终端品牌和型号的编码,该编码由全球移动通信协会(global system for mobile communications assembly,GSMA)及其授权机构分配;图5或者图6中的SNR是终端厂商的产线出来的序列号;图5中的CD通常是由TAC和SNR共同确定的,用于验证TAC和SNR的正确性;图6中的SVN通常为终端出厂前向通信相关部分测试时得到的软件版本号,第一IMEI相关字段的详细说明可参考现有的关于IMEI的描述,在此不再赘述。
可选的,本申请实施例中,终端的能力标识中的至少一个组成部分与第二IMEI的至少一个组成部分可以相同,也可以不相同,本申请实施例对此不作具体限定。其中,该第二IMEI为该终端的IMEI。
示例性的,假设该终端的IMEI的格式如图6所示,该终端的IMEI具体如图7中的(a)所示,为10000000 100000 10,即上述的第二IMEI中的TAC字段的8位数字为10000000,SNR字段的6位数字为100000,SVN字段2位数字为10,则在第一IMEI具体如图7中的(b)所示,为10000000 100001 10的情况下:
若该终端的能力标识包括第一IMEI中的TAC,即该终端的能力标识为10000000,即该终端的能力标识与第二IMEI中的TAC部分相同;
若该终端的能力标识包括第一IMEI中的TAC和SNR,该终端的能力标识为10000000 100001,则终端的能力标识中的TAC部分与第二IMEI中的TAC部分相同,终端的能力标识中的SNR部分与第二IMEI中的SNR部分不相同;
若该终端的能力标识包括第一IMEI中的TAC、SNR和SVN,该终端的能力标识为10000000 100001 10,则终端的能力标识中的TAC部分与第二IMEI中的TAC部分相同,终端的能力标识中的SNR部分与第二IMEI中的SNR部分不相同,终端的能力标识中的SVN部分与第二IMEI中的SVN部分相同。
当然,图7仅是一个示例性说明,第一IMEI和第二IMEI也可能是其他的标识,本申请实施例对此不作具体限定。
可选的,本申请实施例中的第一IMEI和第二IMEI可以相同,也可以不同,本申请实施例对此不作具体限定。
可选的,本申请实施例中的第一IMEI为上述的终端对应的终端设备厂商使用的IMEI,也就是说,本申请实施例中的第一IMEI和第二IMEI为同一个终端设备厂商可使用的IMEI,比如均是分配给同一个终端厂商的IMEI资源池中的IMEI,在此统一说明,以下不再赘述。
需要说明的是,本申请实施例中的步骤S303与步骤S301之间没有必然的执行先后顺序,可以是先执行步骤S301,再执行步骤S303;也可以是先执行步骤S303,再执行步骤S301;还可以是同时执行步骤S301和S303,本申请实施例对此不作具体限定。
S304、终端向gNB发送RRC连接请求(RRC connection request)消息,以使得gNB接收终端发送的RRC连接请求消息。
S305、gNB向终端发送RRC连接建立(RRC connection setup)消息,以使得终端接收gNB发送的RRC连接建立消息。
S306、终端向gNB发送RRC连接建立完成(RRC connection setup complete)消息,以使得gNB接收终端发送的RRC连接建立完成消息。
其中,本申请实施例中可以在步骤S304中的RRC连接请求消息或者步骤S306中的RRC连接建立完成消息中携带步骤S303中确定出的终端的能力标识,本申请实施例对此不作具体限定。
或者,可选的,本申请实施例中可以在非接入层(non-access stratum,NAS)消息中携带上述终端的能力标识,比如,可以在步骤S306中的RRC连接建立完成消息中的NAS消息中携带上述终端的能力 标识。其中,gNB可以将该NAS消息透传给AMF网元,本申请实施例对此不作具体限定。
其中,若在步骤S306中的RRC连接建立完成消息或步骤S306中的RRC连接建立完成消息中的NAS消息中携带步骤S303中确定出的终端的能力标识,则步骤S303与步骤S304之间没有必然的执行先后顺序,可以是先执行步骤S303,再执行步骤S304;还可以是先执行步骤S304,再执行步骤S303,还可以是同时执行步骤S303与步骤S304,本申请实施例对此不作具体限定。
其中,步骤S301-S306给出了RRC连接建立过程中终端向gNB上报终端的能力标识的具体实现。可选的,本申请实施例提供的通信能力上报方法还可以包括如下步骤:
S307、gNB向AMF网元发送初始终端消息(initiate UE message),以使得AMF网元接收gNB发送的初始终端消息。
其中,该初始终端消息中携带上述终端的能力标识。
可选的,若终端发送给gNB的上述终端的能力标识是携带在NAS消息中的,则此时的初始终端消息中包括该NAS消息,本申请实施例对此不作具体限定。
在AMF网元接收到gNB发送的初始终端消息之后,可以查找AMF网元中是否存储上述终端的能力标识对应的终端的通信能力,假设AMF网元中未存储有上述终端的能力标识对应的终端的通信能力,则本申请实施例提供的通信能力上报方法还可以包括如下步骤S308-S314:
S308、AMF网元向gNB发送终端上下文建立请求(UE context setup request),以使得gNB接收AMF网元发送的终端上下文建立请求。
可选的,本申请实施例中的终端上下文建立请求中还可以携带上述步骤S303中确定出的终端的能力标识,本申请实施例对此不作具体限定。
S309、gNB向AMF网元发送终端上下文建立响应(UE context setup response),以使得AMF网元接收gNB发送的终端上下文建立响应。
S310、gNB向终端发送终端能力查询(UE capability enquiry),以使得终端接收gNB发送的终端能力查询。
可选的,本申请实施例中的终端能力查询还可以携带该终端的能力标识,本申请实施例对此不作具体限定。
S311、终端向gNB发送终端能力信息(UE capability information),以使得gNB接收来自终端的终端能力信息。
其中,该终端的能力信息中包括该终端的通信能力。
可选的,该终端的能力信息中还可以包括与该终端的通信能力对应的终端的能力标识,本申请实施例对此不作具体限定。
S312、gNB存储该终端的通信能力。
S313、gNB向AMF网元发送终端能力信息指示(UE capability information indication),以使得AMF网元接收gNB发送的终端能力信息指示。
其中,该终端能力信息指示中包括该终端的通信能力。
可选的,本申请实施例中的终端能力信息指示中还可以包括与该终端的通信能力对应的终端的能力标识,本申请实施例对此不作具体限定。
S314、AMF网元存储该终端的能力标识与该终端的通信能力的对应关系。
需要说明的是,本申请实施例中,AMF网元存储的该终端的能力标识与该终端的通信能力的对应关系中可以包括该终端的能力标识以及与该终端的能力标识对应的通信能力。比如,AMF网元存储的多组对应关系可以如表一所示:
表一
能力标识 通信能力
标识1 通信能力1
标识2 通信能力2
标识3 通信能力3
…… ……
当然,表一仅是示例性的提供了一种终端的通信能力与终端的能力标识的对应关系的存储方式,还可能存在其他的存储形式,本申请实施例对此不作具体限定。
或者,可选的,假设AMF网元中存储有上述终端的能力标识对应的终端的通信能力,则本申请实施例提供的通信能力上报方法还可以包括如下步骤S315-S317:
S315、AMF网元根据终端的能力标识,以及存储的终端的能力标识与终端的通信能力的对应关系,确定终端的通信能力。
S316、AMF网元向gNB发送终端上下文建立请求,以使得gNB接收AMF网元发送的终端上下文建立请求。
其中,该终端上下文建立请求中携带终端的通信能力。
S317、gNB存储该终端的通信能力。
其中,步骤S308-S314可以应用在终端初始注册到网络流程中;步骤S315-S317可以应用在终端从空闲态转换为连接态流程中;或者,步骤S315-S317可以应用在终端从一个gNB切换到另一个gNB流程中,本申请实施例对此不作具体限定。
可选的,本申请实施例提供的通信能力上报方法还可以包括如下步骤:
S318、gNB向终端发送RRC重配置消息(RRC reconfiguration message),以使得终端接收gNB发送的RRC重配置消息。
其中,步骤S318的相关实现可参考现有的实现方式,在此不再赘述。
基于本申请实施例提供的通信能力上报方法,由于在需要进行能力上报时,终端向gNB发送的该终端的能力标识为该终端对应的一个或者多个能力标识中的其中一个标识。也就是说,本申请实施例中,对于一个终端,可以使用不同的能力标识,因此在将终端的通信能力与终端的能力标识相关联的情况下,终端可以使用从终端对应的一个或者多个能力标识中确定的能力标识及时更新自己的通信能力。
其中,上述步骤S301至S318中的终端或者gNB的动作可以由图2所示的通信设备200中的处理器201调用存储器203中存储的应用程序代码来执行,本实施例对此不作任何限制。
图3所示的实施例以将终端的通信能力与终端的能力标识相关联,即终端支持上报终端的能力标识的情况为例进行说明。可选的,本申请实施例中,若终端厂商未维护终端的能力标识与终端的通信能力的对应关系,则该终端厂商的终端则无法通过RRC消息或NAS消息上报终端的能力标识,此时,本申请实施例提供的通信能力上报方法可以如图8所示,包括如下步骤:
S801-S802、同步骤S301-S302,相关描述可参考图3所示的实施例,在此不再赘述。
S803-S805、与步骤S303-S306类似,区别比如在于:本申请实施例中的RRC消息,如RRC连接请求消息或者RRC连接建立完成消息中不携带上述终端的能力标识,而是可以携带一个指示信息,该指示信息用于指示该终端不支持上报终端的能力标识;或者,本申请实施例中的NAS消息,如RRC连接建立完成消息中的NAS消息中不携带上述终端的能力标识,而是可以携带一个指示信息,该指示信息用于指示该终端不支持上报终端的能力标识,相关描述可参考图3所示的实施例,在此不再赘述。
可选的,一种可能的实现方式中,该指示信息可以通过1个或多个比特位进行指示。比如,为0表 示该终端不支持上报终端的能力标识;或者,为1表示该终端不支持上报终端的能力标识。
可选的,另一种可能的实现中,也可以通过将终端的能力标识字段全部置为0来表征该终端不支持上报终端的能力标识,本申请实施例对指示信息的实现方式不作具体限定。
其中,步骤S801-S805给出了RRC连接建立过程中终端向gNB上报终端不支持上报终端的能力标识的指示信息的具体实现,进一步的,本申请实施例提供的通信能力上报方法还可以包括如下步骤:
S806、gNB向AMF网元发送初始终端消息,以使得AMF网元接收gNB发送的初始终端消息。
其中,该初始终端消息中携带上述指示信息。
可选的,若终端发送给gNB的上述指示信息是携带在NAS消息中的,则此时的初始终端消息中包括该NAS消息,本申请实施例对此不作具体限定。
进一步的,本申请实施例中的初始终端消息中还可以携带终端的标识,AMF网元在获知该终端不支持上报终端的能力标识之后,可以根据该终端的标识查询对应的终端的通信能力。
假设AMF网元中未存储有该终端的通信能力,则本申请实施例提供的通信能力上报方法还可以包括如下步骤S807-S813:
S807、AMF网元向gNB发送终端上下文建立请求(UE context setup request),以使得gNB接收AMF网元发送的终端上下文建立请求。
S808、gNB向AMF网元发送终端上下文建立响应(UE context setup response),以使得AMF网元接收gNB发送的终端上下文建立响应。
S809、gNB向终端发送终端能力查询(UE capability enquiry),以使得终端接收gNB发送的终端能力查询。
S810、终端向gNB发送终端能力信息(UE capability information),以使得gNB接收来自终端的终端能力信息。
其中,该终端的能力信息中包括该终端的通信能力。
S811、gNB存储该终端的通信能力。
S812、gNB向AMF网元发送终端能力信息指示(UE capability information indication),以使得AMF网元接收gNB发送的终端能力信息指示。
其中,该终端能力信息指示中包括该终端的通信能力。
S813、AMF网元存储该终端的通信能力。
示例性的,AMF网元存储的多个终端的通信能力可以如表二所示:
表二
终端标识 通信能力
标识1 通信能力1
标识2 通信能力2
标识3 通信能力3
…… ……
当然,表二仅是示例性的提供了一种终端的通信能力的存储方式,还可能存在其他的存储形式,本申请实施例对此不作具体限定。
或者,可选的,假设AMF网元中存储有上述终端的通信能力,则本申请实施例提供的通信能力上报方法还可以包括如下步骤S814-S815:
S814、AMF网元向gNB发送终端上下文建立请求,以使得gNB接收AMF网元发送的终端上下文建立请求。
其中,该终端上下文建立请求中携带终端的通信能力。
S815、gNB存储该终端的通信能力。
其中,步骤S807-S813可以应用在终端初始注册到网络流程中;步骤S814-S815可以应用在终端从空闲态转换为连接态流程中;或者,步骤S814-S815可以应用在终端从一个gNB切换到另一个gNB流程中,本申请实施例对此不作具体限定。
可选的,本申请实施例提供的通信能力上报方法还可以包括如下步骤:
S816、gNB向终端发送RRC重配置消息,以使得终端接收gNB发送的RRC重配置消息。
本申请实施例提供的通信能力上报方法中,在需要进行能力上报时,若终端不支持上报终端的能力标识,则终端通过gNB向核心网中的AMF网元发送该终端不支持上报终端的能力标识。这样,AMF网元可以获知该终端不支持上报终端的能力标识,从而不会根据该终端的能力标识查找对应的终端的通信能力,而是在根据终端的标识获知AMF网元中未存储该终端的通信能力时,向该终端查询该终端的通信能力,使得终端再上报该终端的通信能力。基于该方案,可以实现不支持终端的能力标识上报的终端的通信能力的上报。
其中,上述步骤S801至S816中的终端或者gNB的动作可以由图2所示的通信设备200中的处理器201调用存储器203中存储的应用程序代码来执行,本实施例对此不作任何限制。
需要说明的是,图3和图8均是以第一通信设备为5G NR系统中的一个终端,第二通信设备为5G NR系统中的gNB为例进行说明,当然,如上所述,第二通信设备也可以为5G NR系统中的一个终端,比如中继用户设备,此时,对应的通信能力上报方法与上述图3或者图8类似,区别比如在于:相当于在图3或者图8所示的终端与gNB之间插入一个转发设备,该第二通信设备主要转发接收到的终端的能力标识或者终端的通信能力等信息,其余相关描述可参考图3或者图8所示的实施例,本申请实施例对此不再赘述。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是,上述第一通信设备或者第二通信设备为了实现上述功能,其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对第一通信设备或者第二通信设备进行功能模块的划分,例如,可以对应各个功能划分各个功能模块,也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。需要说明的是,本申请实施例中对模块的划分是示意性的,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式。
比如,以采用集成的方式划分各个功能模块的情况下,图9示出了一种第一通信设备90的结构示意图。该第一通信设备90可以为上述实施例中的终端,也可以是上述实施例中的终端内的芯片系统或电路,本申请实施例对此不作具体限定。其中,该第一通信设备90包括:处理模块902和收发模块901。处理模块902,用于确定第一通信设备90的能力标识,其中,第一通信设备90的能力标识为第一通信设备90对应的一个或多个能力标识中的其中一个标识;收发模块901,用于向第二通信设备发送第一通信设备90的能力标识,第一通信设备90的能力标识用于确定第一通信设备90的通信能力。
可选的,第一通信设备90的能力标识包括第一IMEI的至少一个组成部分。
可选的,第一通信设备90的能力标识包括第一IMEI的至少一个组成部分,包括:第一通信设备90的能力标识包括第一IMEI中的TAC;或者,第一通信设备90的能力标识包括第一IMEI中的TAC和序 列号SNR;或者,第一通信设备90的能力标识包括第一IMEI中的TAC、SNR以及SVN;或者,第一通信设备90的能力标识包括第一IMEI中的TAC、SNR以及CD。
可选的,第一通信设备90的能力标识的至少一个组成部分与第二IMEI的至少一个组成部分不同,其中,第二IMEI为第一通信设备90的IMEI。
可选的,第一IMEI是第一通信设备90所属厂商使用的IMEI。
可选的,第一通信设备90的能力标识与第三通信设备的能力标识不同,其中,第三通信设备和第一通信设备90为不同厂商的通信设备。
可选的,收发模块901具体用于:向第二通信设备发送第一RRC消息或第一NAS消息,第一RRC消息或第一NAS消息包括第一通信设备90的能力标识。
可选的,处理模块902具体用于:在第一通信设备90支持上报第一通信设备90的能力标识的情况下,确定第一通信设备90的能力标识。
进一步的,收发模块901,还用于在第一通信设备90不支持上报第一通信设备90的能力标识的情况下,向第二通信设备发送指示信息,该指示信息用于指示第一通信设备90不支持上报第一通信设备90的能力标识。
可选的,收发模块901用于向第二通信设备发送指示信息,包括:用于向第二通信设备发送第二RRC消息或第二NAS消息,第二RRC消息或第二NAS消息包括该指示信息。
其中,上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述,在此不再赘述。
在本实施例中,该第一通信设备90以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC,电路,执行一个或多个软件或固件程序的处理器和存储器,集成逻辑电路,和/或其他可以提供上述功能的器件。
在一个简单的实施例中,本领域的技术人员可以想到第一通信设备90可以采用图2所示的形式。
比如,图2中的处理器201可以通过调用存储器203中存储的计算机执行指令,使得第一通信设备90执行上述方法实施例中的通信能力上报方法。
具体的,图9中的处理模块902和收发模块901的功能/实现过程可以通过图2中的处理器201调用存储器203中存储的计算机执行指令来实现。或者,图9中的处理模块902的功能/实现过程可以通过图2中的处理器201调用存储器203中存储的计算机执行指令来实现,图9中的收发模块901的功能/实现过程可以通过图2中的通信接口204来实现。
可选的,当该第一通信设备90是芯片或电路时,存储器203可以为芯片或电路内的存储单元,如寄存器、缓存等。当然,当该第一通信设备90是终端时,存储器203可以是终端内的位于芯片外部的存储单元,本申请实施例对此不作具体限定。
由于本申请实施例提供的第一通信设备可用于执行上述通信能力上报方法,因此其所能获得的技术效果可参考上述方法实施例,在此不再赘述。
比如,以采用集成的方式划分各个功能模块的情况下,图10示出了一种第二通信设备100的结构示意图。该第二通信设备100可以包括上述实施例中的终端,也可以是上述实施例中的终端内的芯片或者电路,也可以是上述实施例中的接入设备(如gNB),也可以是上述实施例中的接入设备内的芯片系统或电路,本申请实施例对此不作具体限定。其中,该第二通信设备100包括:接收模块1001和发送模块1002。接收模块1001,用于接收第一通信设备发送的第一通信设备的能力标识,其中,第一通信设备的能力标识为第一通信设备对应的一个或多个能力标识中的其中一个标识;发送模块1002,用于向网络设备发送第一通信设备的能力标识,第一通信设备的能力标识用于确定第一通信设备的通信能力。
可选的,第一通信设备的能力标识包括第一IMEI的至少一个组成部分。
可选的,第一通信设备的能力标识包括第一IMEI的至少一个组成部分,包括:第一通信设备的能力标识包括第一IMEI中的TAC;或者,第一通信设备的能力标识包括第一IMEI中的TAC和SNR;或者,第一通信设备的能力标识包括第一IMEI中的TAC、SNR以及SVN;或者,第一通信设备的能力标识包括第一IMEI中的TAC、SNR以及CD。
可选的,第一通信设备的能力标识的至少一个组成部分与第二IMEI的至少一个组成部分不同,其中,第二IMEI为第一通信设备的IMEI。
可选的,第一IMEI是第一通信设备所属厂商使用的IMEI。
可选的,第一通信设备的能力标识与第三通信设备的能力标识不同,其中,第三通信设备和第一通信设备为不同厂商的通信设备。
可选的,接收模块1001,还用于接收网络设备发送的第一通信设备的通信能力。
可选的,接收模块1001,还用于接收网络设备发送的第一消息,该第一消息用于请求第一通信设备的通信能力;发送模块1002,还用于向第一通信设备发送第二消息,该第二消息用于请求第一通信设备的通信能力;接收模块1001,还用于接收第一通信设备发送的第一通信设备的通信能力。
可选的,本申请实施例中的第一消息中可以携带第一通信设备的能力标识,本申请实施例对此不作具体限定。
可选的,本申请实施例中的第二消息中可以携带第一通信设备的能力标识,本申请实施例对此不作具体限定。
可选的,发送模块1002,还用于向网络设备发送第一通信设备的通信能力,由网络设备存储第一通信设备的能力标识和第一通信设备的通信能力的对应关系。
可选的,接收模块1001,还用于接收第一通信设备发送的与第一通信设备的通信能力对应的第一通信设备的能力标识。
可选的,发送模块1002,还用于向网络设备发送第一通信设备的通信能力和与该第一通信设备的通信能力对应的第一通信设备的能力标识,由网络设备存储该第一通信设备的能力标识和该第一通信设备的通信能力的对应关系。
可选的,接收模块1001用于接收第一通信设备发送的第一通信设备的能力标识,包括:用于在第一通信设备支持上报第一通信设备的能力标识的情况下,接收第一通信设备发送的第一通信设备的能力标识。
可选的,接收模块1001,还用于在第一通信设备不支持上报第一通信设备的能力标识的情况下,接收第一通信设备发送的指示信息,该指示信息用于指示第一通信设备不支持上报第一通信设备的能力标识。
可选的,接收模块1001用于接收第一通信设备发送的指示信息,包括:用于接收第一通信设备发送的第一RRC消息或第一NAS消息,第一RRC消息或第一NAS消息包括指示信息。
可选的,接收模块1001用于接收第一通信设备发送的第一通信设备的能力标识,包括:用于接收第一通信设备发送的第二RRC消息或第二NAS消息,该第二RRC消息或第二NAS消息包括第一通信设备的能力标识。
其中,上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述,在此不再赘述。
在本实施例中,该第二通信设备100以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC,电路,执行一个或多个软件或固件程序的处理器和存储器,集成逻辑电路,和/或 其他可以提供上述功能的器件。
在一个简单的实施例中,本领域的技术人员可以想到第二通信设备100可以采用图2所示的形式。
比如,图2中的处理器201可以通过调用存储器203中存储的计算机执行指令,使得第二通信设备100执行上述方法实施例中的通信能力上报方法。
具体的,图10中的接收模块1001和发送模块1002的功能/实现过程可以通过图2中的处理器201调用存储器203中存储的计算机执行指令来实现。或者,图10中的接收模块1001和发送模块1002的功能/实现过程可以通过图2中的通信接口204来实现。
可选的,当该第二通信设备100是芯片或电路时,存储器203可以为芯片或电路内的存储单元,如寄存器、缓存等。当然,当该第二通信设备100是接入设备时,存储器203可以是接入设备内的位于芯片外部的存储单元,本申请实施例对此不作具体限定。
由于本申请实施例提供的第二通信设备可用于执行上述通信能力上报方法,因此其所能获得的技术效果可参考上述方法实施例,在此不再赘述。
在上述实施例中,可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时,可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时,全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中,或者从一个计算机可读存储介质向另一个计算机可读存储介质传输,例如,所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line,DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如,软盘、硬盘、磁带),光介质(例如,DVD)、或者半导体介质(例如固态硬盘(solid state disk,SSD))等。
尽管在此结合各实施例对本申请进行了描述,然而,在实施所要求保护的本申请过程中,本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书,可理解并实现所述公开实施例的其他变化。在权利要求中,“包括”(comprising)一词不排除其他组成部分或步骤,“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施,但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述,显而易见的,在不脱离本申请的精神和范围的情况下,可对其进行各种修改和组合。相应地,本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明,且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然,本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样,倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内,则本申请也意图包含这些改动和变型在内。

Claims (38)

  1. 一种第一通信设备,其特征在于,所述第一通信设备包括:处理模块和收发模块;
    所述处理模块,用于确定所述第一通信设备的能力标识,其中,所述第一通信设备的能力标识为所述第一通信设备对应的一个或多个能力标识中的其中一个标识;
    所述收发模块,用于向第二通信设备发送所述第一通信设备的能力标识,所述第一通信设备的能力标识用于确定所述第一通信设备的通信能力。
  2. 根据权利要求1所述的第一通信设备,其特征在于,所述第一通信设备的能力标识包括第一国际移动设备识别码IMEI的至少一个组成部分。
  3. 根据权利要求2所述的第一通信设备,其特征在于,所述第一通信设备的能力标识包括第一IMEI的至少一个组成部分,包括:
    所述第一通信设备的能力标识包括所述第一IMEI中的类型分配码TAC;
    或者,所述第一通信设备的能力标识包括所述第一IMEI中的TAC和序列号SNR;
    或者,所述第一通信设备的能力标识包括所述第一IMEI中的TAC、SNR以及软件版本号SVN;
    或者,所述第一通信设备的能力标识包括所述第一IMEI中的TAC、SNR以及验证码CD。
  4. 根据权利要求2或3所述的第一通信设备,其特征在于,所述第一通信设备的能力标识的至少一个组成部分与第二IMEI的至少一个组成部分不同,其中,所述第二IMEI为所述第一通信设备的IMEI。
  5. 根据权利要求2-4任一项所述的第一通信设备,其特征在于,所述第一IMEI是所述第一通信设备所属厂商使用的IMEI。
  6. 根据权利要求1-5任一项所述的第一通信设备,其特征在于,所述第一通信设备的能力标识与第三通信设备的能力标识不同,其中,所述第三通信设备和所述第一通信设备为不同厂商的通信设备。
  7. 根据权利要求1-6任一项所述的第一通信设备,其特征在于,所述收发模块具体用于:
    向所述第二通信设备发送第一无线资源控制RRC消息或第一非接入层NAS消息,所述第一RRC消息或所述第一NAS消息包括所述第一通信设备的能力标识。
  8. 根据权利要求1-7任一项所述的第一通信设备,其特征在于,所述处理模块具体用于:
    在所述第一通信设备支持上报所述第一通信设备的能力标识的情况下,确定所述第一通信设备的能力标识。
  9. 根据权利要求8所述的第一通信设备,其特征在于,
    所述收发模块,还用于在所述第一通信设备不支持上报所述第一通信设备的能力标识的情况下,向所述第二通信设备发送指示信息,所述指示信息用于指示所述第一通信设备不支持上报所述第一通信设备的能力标识。
  10. 根据权利要求9所述的第一通信设备,其特征在于,所述收发模块用于向所述第二通信设备发送指示信息,包括:用于向所述第二通信设备发送第二RRC消息或第二NAS消息,所述第二RRC消息或所述第二NAS消息包括所述指示信息。
  11. 一种通信能力上报的方法,其特征在于,包括:
    第一终端设备确定所述第一通信设备的能力标识,其中,所述第一通信设备的能力标识为所述第一通信设备对应的一个或多个能力标识中的其中一个标识;
    所述第一终端设备向第二通信设备发送所述第一通信设备的能力标识,所述第一通信设备的能力标识用于确定所述第一通信设备的通信能力。
  12. 根据权利要求11所述的方法,其特征在于,第一通信设备确定所述第一通信设备的能力标识,其中,所述第一通信设备的能力标识包括第一国际移动设备识别码IMEI的至少一个组成部分。
  13. 根据权利要求12所述的方法,其特征在于,所述第一通信设备的能力标识包括第一IMEI的至少一个组成部分,包括:
    所述第一通信设备的能力标识包括所述第一IMEI中的类型分配码TAC;
    或者,所述第一通信设备的能力标识包括所述第一IMEI中的TAC和序列号SNR;
    或者,所述第一通信设备的能力标识包括所述第一IMEI中的TAC、SNR以及软件版本号SVN;
    或者,所述第一通信设备的能力标识包括所述第一IMEI中的TAC、SNR以及验证码CD。
  14. 根据权利要求12或13所述的方法,其特征在于,所述第一通信设备的能力标识的至少一个组成部分与第二IMEI的至少一个组成部分不同,其中,所述第二IMEI为所述第一通信设备的IMEI。
  15. 根据权利要求12-14任一项所述的方法,其特征在于,所述第一IMEI是所述第一通信设备所属厂商使用的IMEI。
  16. 根据权利要求11-15任一项所述的方法,其特征在于,所述第一通信设备的能力标识与第三通信设备的能力标识不同,其中,所述第三通信设备和所述第一通信设备为不同厂商的通信设备。
  17. 根据权利要求11-16任一项所述的方法,其特征在于,所述方法还包括:
    所述第一终端设备向所述第二通信设备发送第一无线资源控制RRC消息或第一非接入层NAS消息,所述第一RRC消息或所述第一NAS消息包括所述第一通信设备的能力标识。
  18. 根据权利要求11-17任一项所述的方法,其特征在于,所述方法还包括:
    在所述第一通信设备支持上报所述第一通信设备的能力标识的情况下,所述第一终端设备确定所述第一通信设备的能力标识。
  19. 根据权利要求18所述的方法,其特征在于,所述方法还包括:
    在所述第一通信设备不支持上报所述第一通信设备的能力标识的情况下,所述第一终端设备向所述第二通信设备发送指示信息,所述指示信息用于指示所述第一通信设备不支持上报所述第一通信设备的能力标识。
  20. 根据权利要求19所述的方法,其特征在于,所述方法还包括:
    所述第一终端设备向所述第二通信设备发送指示信息,包括:用于向所述第二通信设备发送第二RRC消息或第二NAS消息,所述第二RRC消息或所述第二NAS消息包括所述指示信息。
  21. 一种通信能力上报的方法,其特征在于,包括:
    第二通信设备接收第一通信设备发送的所述第一通信设备的能力标识,其中,该第一通信设备的能力标识为该第一通信设备对应的一个或多个能力标识中的其中一个标识;
    所述第二通信设备向网络设备发送所述第一通信设备的能力标识,所述第一通信设备的能力标识用于确定该第一通信设备的通信能力。
  22. 根据权利要求21所述的方法,其特征在于,还包括:所述第二通信设备接收网络设备发送的该第一通信设备的通信能力。
  23. 根据权利要求22所述的方法,其特征在于,还包括:
    所述第二通信设备接收所述网络设备发送的第一消息,所述第一消息用于请求所述第一通信设备的通信能力;
    所述第二通信设备向所述第一通信设备发送第二消息,所述第二消息用于请求所述第一通信设备的通信能力;
    所述第二通信设备接收所述第一通信设备发送的所述第一通信设备的通信能力。
  24. 根据权利要求23所述的方法,其特征在于,所述第一消息中携带所述第一通信设备的能力标识。
  25. 根据权利要求23或24所述的方法,其特征在于,所述第二消息中可以携带所述第一通信设备的能力标识。
  26. 根据权利要求22-25中任一项所述的方法,其特征在于,其特征在于,还包括:
    所述第二通信设备向所述网络设备发送所述第一通信设备的通信能力。
  27. 根据权利要求22-26中任一项所述的方法,其特征在于,其特征在于,还包括:
    所述第二通信设备接收所述第一通信设备发送的与所述第一通信设备的通信能力对应的所述第一通信设备的能力标识。
  28. 根据权利要求22-27中任一项所述的方法,其特征在于,其特征在于,还包括:
    所述第二通信设备向所述网络设备发送所述第一通信设备的通信能力和与所述第一通信设备的通信能力对应的第一通信设备的能力标识。
  29. 根据权利要求22-28中任一项所述的方法,其特征在于,所述第二通信设备接收第一通信设备发送的第一通信设备的能力标识,包括:在所述第一通信设备支持上报所述第一通信设备的能力标识的情况下,所述第二通信设备接收所述第一通信设备发送的该第一通信设备的能力标识。
  30. 根据权利要求22-28中任一项所述的方法,其特征在于,还包括:在第一通信设备不支持上报所述第一通信设备的能力标识的情况下,所述第二通信设备接收所述第一通信设备发送的指示信息,并将所述指示信息发送给核心网中的网络设备。
  31. 根据权利要求22-28中任一项所述的方法,其特征在于,所述第二通信设备接收该第一通信设备发送的指示信息,包括:
    所述第二通信设备接收第一通信设备发送的第一无线资源控制RRC消息或第一非接入层NAS消息,所述第一RRC消息或第一NAS消息包括该指示信息。
  32. 根据权利要求22-28中任一项所述的方法,其特征在于,所述第二通信设备接收第一通信设备发送的该第一通信设备的能力标识,包括:
    所述第二通信设备接收第一通信设备发送的第二RRC消息或第二NAS消息,所述第二RRC消息或第二NAS消息包括所述第一通信设备的能力标识。
  33. 一种第一通信设备,其特征在于,包括:处理器和存储器;所述存储器用于存储计算机执行指令,当所述第一通信设备运行时,所述处理器执行该存储器存储的所述计算机执行指令,以使所述第一通信设备执行如权利要求11-20的通信能力上报方法。
  34. 如权利要求33所述的第一通信设备,其特征在于,第一通信设备为终端、终端内的芯片系统或者电路。
  35. 一种第二通信设备,其特征在于,包括:处理器和存储器;所述存储器用于存储计算机执行指令,当所述第一通信设备运行时,所述处理器执行该存储器存储的所述计算机执行指令,以使所述第一通信设备执行如权利要求21-32的通信能力上报方法。
  36. 根据权利要求33所述的第二通信设备,其特征在于,所述第二通信设备为网络设备、网络设备内的芯片系统或者电路。
  37. 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质中存储有指令,当其在计算机上运行时,使得计算机可以执行如权利要求11-32的通信能力上报方法。
  38. 一种包含指令的计算机程序产品,其特征在于,当其在计算机上运行时,使得计算机如权利要求11-32的通信能力上报方法。
PCT/CN2019/080903 2018-04-04 2019-04-02 通信能力上报方法、设备及系统 WO2019192439A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP19780912.2A EP3761688A4 (en) 2018-04-04 2019-04-02 METHOD, DEVICE AND SYSTEM FOR REPORTING COMMUNICATION SKILLS

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810299983.1A CN110351712B (zh) 2018-04-04 2018-04-04 通信能力上报方法、设备及系统
CN201810299983.1 2018-04-04

Publications (1)

Publication Number Publication Date
WO2019192439A1 true WO2019192439A1 (zh) 2019-10-10

Family

ID=68099947

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/080903 WO2019192439A1 (zh) 2018-04-04 2019-04-02 通信能力上报方法、设备及系统

Country Status (3)

Country Link
EP (1) EP3761688A4 (zh)
CN (1) CN110351712B (zh)
WO (1) WO2019192439A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114630314A (zh) * 2020-12-10 2022-06-14 中移(苏州)软件技术有限公司 终端信息库的更新方法、装置、设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102573070A (zh) * 2010-12-13 2012-07-11 中兴通讯股份有限公司 一种无线资源分配方法及系统
CN103079194A (zh) * 2011-10-25 2013-05-01 中兴通讯股份有限公司 业务适配方法、装置及系统
EP2613596A1 (en) * 2012-01-05 2013-07-10 TeliaSonera AB Network selection in a shared network environment

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101990134B1 (ko) * 2011-08-10 2019-06-17 삼성전자주식회사 듀얼 모드 단말의 성능 정보 보고 방법 및 장치
GB2542770B (en) * 2015-09-25 2020-01-08 Samsung Electronics Co Ltd Mobile device capability identifier

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102573070A (zh) * 2010-12-13 2012-07-11 中兴通讯股份有限公司 一种无线资源分配方法及系统
CN103079194A (zh) * 2011-10-25 2013-05-01 中兴通讯股份有限公司 业务适配方法、装置及系统
EP2613596A1 (en) * 2012-01-05 2013-07-10 TeliaSonera AB Network selection in a shared network environment

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"Study on optimisations of UE radio capability signalling (Release 16)", 3GPP TR 23.743 V2.0.0, 31 March 2019 (2019-03-31), pages 20 - 23, XP051722775 *
HUAWEI ET AL.: "Signalling procedure for UE capability ID report", R2-1814604, NO. 3GPP TSG-RAN WG2 # 103BIS, 12 October 2018 (2018-10-12), XP051524028 *
NTT DOCOMO: "UE capability retrieval framework in NR", R2-1801355, NO. 3GPP TSG-RAN WG2 NR ADHOC, 26 January 2018 (2018-01-26), pages 1, 2, XP051386767 *
See also references of EP3761688A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114630314A (zh) * 2020-12-10 2022-06-14 中移(苏州)软件技术有限公司 终端信息库的更新方法、装置、设备及存储介质
CN114630314B (zh) * 2020-12-10 2023-09-05 中移(苏州)软件技术有限公司 终端信息库的更新方法、装置、设备及存储介质

Also Published As

Publication number Publication date
EP3761688A4 (en) 2021-04-21
CN110351712A (zh) 2019-10-18
EP3761688A1 (en) 2021-01-06
CN110351712B (zh) 2020-12-08

Similar Documents

Publication Publication Date Title
US11445569B2 (en) Session establishment method and system, and device
US20230164644A1 (en) Session Establishment Method And System, And Device
US20230209655A1 (en) Data Transmission Method, Device, and System
JP7184922B2 (ja) Ueのためにポリシーを構成するための方法、装置、及びシステム
EP3641365B1 (en) Device access method, device and system
US11457489B2 (en) Terminal interaction with different user plane function entities
RU2763159C1 (ru) Способ и устройство связи
US11432218B2 (en) Handover method and system, and device
CN111200810B (zh) 终端的能力信息的获取方法、装置及系统
CN110266826B (zh) 地址管理方法、设备及系统
WO2019120073A1 (zh) 数据传输方法、设备及系统
WO2019033967A1 (zh) 安全接入方法、设备及系统
US10897699B2 (en) Subscription update method, device, and system
WO2019184723A1 (zh) 策略和计费控制规则获取方法、装置及系统
US20240206012A1 (en) Method and apparatus for inter-device communication
WO2019192439A1 (zh) 通信能力上报方法、设备及系统
WO2018191867A1 (zh) 终端监控信息的同步方法、设备及系统
CN116746188A (zh) 使用允许性指示来支持应用认证和密钥管理(akma)的方法和系统
WO2022094899A1 (zh) 通信方法及装置
WO2016090933A1 (zh) 应用通告资源的创建方法及装置
WO2019105156A1 (zh) 一种通信方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19780912

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019780912

Country of ref document: EP

Effective date: 20201001