WO2020029191A1 - 能力上报的方法和设备 - Google Patents

能力上报的方法和设备 Download PDF

Info

Publication number
WO2020029191A1
WO2020029191A1 PCT/CN2018/099688 CN2018099688W WO2020029191A1 WO 2020029191 A1 WO2020029191 A1 WO 2020029191A1 CN 2018099688 W CN2018099688 W CN 2018099688W WO 2020029191 A1 WO2020029191 A1 WO 2020029191A1
Authority
WO
WIPO (PCT)
Prior art keywords
capability
terminal device
capabilities
network device
information
Prior art date
Application number
PCT/CN2018/099688
Other languages
English (en)
French (fr)
Inventor
杨宁
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to AU2018436322A priority Critical patent/AU2018436322B2/en
Priority to JP2021504385A priority patent/JP7385648B2/ja
Priority to EP18929253.5A priority patent/EP3833070B1/en
Priority to PCT/CN2018/099688 priority patent/WO2020029191A1/zh
Priority to CN201880096329.9A priority patent/CN112602343A/zh
Priority to KR1020217004114A priority patent/KR102513163B1/ko
Priority to PCT/CN2018/104863 priority patent/WO2020029362A1/zh
Publication of WO2020029191A1 publication Critical patent/WO2020029191A1/zh
Priority to US17/167,596 priority patent/US20210160686A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0096—Indication of changes in allocation
    • H04L5/0098—Signalling of the activation or deactivation of component carriers, subcarriers or frequency bands
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/25—Maintenance of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast

Definitions

  • Embodiments of the present application relate to the field of communications, and more specifically, to a method and device for capability reporting.
  • a terminal device When a terminal device enters a network such as an attachment or tracking area update (TAU), if the network device does not store the capability information of the terminal device, the terminal device needs to report its capability information to the network device.
  • the network may store the capability information of the terminal equipment in a core network entity such as a mobility management entity (MME), an authentication management function (AMF) entity, and the like.
  • MME mobility management entity
  • AMF authentication management function
  • the core network will transmit the corresponding capabilities to the access network when the terminal equipment accesses next time, thereby preventing the terminal equipment from repeatedly reporting its own capability information.
  • the embodiments of the present application provide a method and a device for capability reporting, which can reduce a signaling overhead for reporting capability information of a terminal device.
  • a method for capability reporting including: a terminal device reporting to a network device an identifier of at least one capability group to which the capability supported by the terminal device belongs.
  • a method for capability reporting including: a network device receiving an identifier of at least one capability group to which a capability supported by the terminal device reported by a terminal device belongs.
  • a terminal device can execute the foregoing first aspect or the method in any optional implementation manner of the first aspect.
  • the terminal device may include a functional module for executing the foregoing first aspect or the method in any possible implementation manner of the first aspect.
  • a network device can execute the foregoing second aspect or the method in any optional implementation manner of the second aspect.
  • the network device may include a functional module for performing the foregoing second aspect or the method in any possible implementation manner of the second aspect.
  • a terminal device including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the foregoing first aspect or the method in any possible implementation manner of the first aspect.
  • a network device including a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the second aspect or the method in any possible implementation manner of the second aspect.
  • a chip for implementing the foregoing first aspect or the method in any possible implementation manner of the first aspect.
  • the chip includes a processor for invoking and running a computer program from the memory, so that the device installed with the chip executes the method in the first aspect or any possible implementation manner of the first aspect.
  • a chip for implementing the foregoing second aspect or the method in any possible implementation manner of the second aspect.
  • the chip includes a processor for invoking and running a computer program from the memory, so that the device installed with the chip executes the method in the second aspect or any possible implementation manner of the second aspect.
  • a computer-readable storage medium for storing a computer program that causes a computer to execute the foregoing first aspect or the method in any possible implementation manner of the first aspect.
  • a computer-readable storage medium for storing a computer program that causes a computer to execute the foregoing second aspect or the method in any possible implementation manner of the second aspect.
  • a computer program product including computer program instructions that cause a computer to execute the foregoing first aspect or a method in any possible implementation manner of the first aspect.
  • a computer program product including computer program instructions that cause a computer to perform the foregoing second aspect or a method in any possible implementation manner of the second aspect.
  • a computer program that, when run on a computer, causes the computer to execute the above-mentioned first aspect or the method in any possible implementation manner of the first aspect.
  • a computer program is provided that, when run on a computer, causes the computer to execute the second aspect or the method in any possible implementation manner of the second aspect.
  • a communication system including a terminal device and a network device.
  • the terminal device is configured to report to the network device an identifier of at least one capability group to which the capabilities supported by the terminal device belong.
  • the network device is configured to receive an identifier of at least one capability group to which a capability supported by the terminal device belongs, which is reported by the terminal device.
  • the terminal device is configured to execute the foregoing first aspect or the method in any possible implementation manner of the first aspect
  • the network device is configured to implement the foregoing second aspect or any possible implementation manner in the second aspect.
  • the terminal device reports the identity of the capability group to which the capabilities it supports belong to the network device, so that the network device determines the capabilities supported by the terminal device according to the received capability group identification. Since the terminal device can report the identity of the capability group to which the supported capabilities belong to the network device, it is not necessary to separately report each supported capability information to the network device, thereby reducing the signaling overhead generated when the terminal device reports the capability information. .
  • FIG. 1 is a schematic diagram of a wireless communication system according to an embodiment of the present application.
  • FIG. 2 is a flow interaction diagram of a terminal device reporting capability information.
  • FIG. 3 is a flowchart interaction diagram of a capability reporting method according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of reporting an additional capability according to an embodiment of the present application.
  • FIG. 5 is a schematic block diagram of a terminal device according to an embodiment of the present application.
  • FIG. 6 is a schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a communication system according to an embodiment of the present application.
  • GSM Global System for Mobile
  • CDMA Code Division Multiple Access
  • Wideband Code Division Multiple Access Wideband Code Division Multiple Access
  • General Packet Radio Service GPRS
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • LTE-A Advanced Long-Term Evolution
  • NR New Radio
  • NR Universal Mobile Telecommunication System
  • UMTS Universal Mobile Telecommunication System
  • D2D Device to Device
  • M2M machine-to-machine
  • MTC machine-type communication
  • V2V vehicle-to-vehicle
  • the communication system in the embodiment of the present application may be applied to a Carrier Aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) deployment.
  • CA Carrier Aggregation
  • DC dual connectivity
  • SA standalone
  • the wireless communication system 100 may include a network device 110.
  • the network device 110 may be a device that communicates with a terminal device.
  • the network device 110 may provide communication coverage for a specific geographic area, and may communicate with terminal devices located within the coverage area.
  • the network device 100 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, or a base station (NodeB, NB) in a WCDMA system, or an evolved base station in an LTE system.
  • BTS Base Transceiver Station
  • NodeB NodeB
  • Evolutional NodeB, eNB or eNodeB or a network-side device in an NR system, or a wireless controller in a Cloud Radio Access Network (CRAN), or the network device may be a relay station, an access point Point of entry, vehicle-mounted equipment, wearable equipment, network-side equipment in the next generation network, or network equipment in a public land mobile network (PLMN) that will evolve in the future.
  • PLMN public land mobile network
  • the wireless communication system 100 further includes at least one terminal device 120 located within a coverage area of the network device 110.
  • terminal equipment used herein includes, but is not limited to, connection via wired lines, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cable, direct cable connection ; And / or another data connection / network; and / or via a wireless interface, such as for cellular networks, Wireless Local Area Networks (WLAN), digital television networks such as DVB-H networks, satellite networks, AM- FM broadcast transmitter; and / or another terminal device configured to receive / transmit communication signals; and / or Internet of Things (IoT) devices.
  • a terminal device configured to communicate through a wireless interface may be referred to as a “wireless communication terminal”, a “wireless terminal”, or a “mobile terminal”.
  • the terminal device 120 may be mobile or fixed.
  • the terminal device 120 may refer to an access terminal, user equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication Device, user agent, or user device.
  • the access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Processing (PDA), and wireless communication.
  • terminal devices 120 may also perform terminal direct device (D2D) communication.
  • D2D terminal direct device
  • the network device 110 may provide services for a cell, and the terminal device 120 communicates with the network device 110 through a transmission resource (for example, a frequency domain resource or a spectrum resource) used by the cell, and the cell may be the network device 110 (
  • a cell corresponding to a base station may belong to a macro base station or a small cell (small cell).
  • the small cell may include: a city cell (micro cell), a micro cell (micro cell), a pico cell ( Pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
  • FIG. 1 exemplarily shows one network device and two terminal devices.
  • the wireless communication system 100 may include multiple network devices and the coverage range of each network device may include other numbers of terminal devices.
  • the application example does not limit this.
  • the wireless communication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like in this embodiment of the present application is not limited thereto.
  • a network device may send a UE Capability Request message (UECapabilityEnquiry) to the terminal device. After receiving the capability request message, the terminal device reports its UE to the network device. Capability information (UECapabilityInformation).
  • the network can store the capability information of the terminal equipment in a core network entity such as an MME, an AMF entity, and the like.
  • the core network will transmit the corresponding capabilities to the access network when the terminal equipment accesses next time, thereby preventing the terminal equipment from repeatedly reporting its own capability information.
  • the capabilities of the terminal equipment are related to the various software and hardware capabilities of the terminal equipment, which is very complicated and the signaling overhead is very large.
  • the embodiment of the present application proposes to group various capabilities that the terminal device may support.
  • the terminal device reports to the network device the identity of the capability group to which the supported capability belongs, so that the network device may The identification determines the capabilities supported by the terminal device. Since the terminal device can report the identity of the capability group to which the supported capabilities belong to the network device, it is not necessary to separately report each supported capability information to the network device, thereby reducing the signaling overhead generated when the terminal device reports the capability information. .
  • FIG. 3 is a process interaction diagram of a capability reporting method 300 according to an embodiment of the present application.
  • the method shown in FIG. 3 may be executed by a terminal device and a network device.
  • the terminal device may be, for example, the terminal device 120 shown in FIG. 1
  • the network device may be, for example, the network device shown in FIG. 1.
  • the method 300 for reporting the capability includes:
  • the terminal device reports to the network device an identifier of at least one capability group to which the capabilities supported by the terminal device belong.
  • the network device receives an identifier of the at least one capability group to which the capability supported by the terminal device reported by the terminal device belongs.
  • various capability information may be grouped, and each capability group has its own unique identifier, and the identifier may be, for example, a name, an index, and the like of the capability group.
  • the terminal device determines the capability groups to which these capabilities belong according to the supported capabilities, and reports the identifiers of these capability groups to the network device, so that the network device can determine the capabilities supported by the terminal device according to the received capability group identifier.
  • the combination of capabilities in the capability group indicated by these identifiers is the capability supported by the terminal device.
  • the method further includes: obtaining, by the terminal device, information about the capability group.
  • the information of the capability group includes a plurality of capability groups and the capabilities included in each capability group.
  • the network device may send the capability group information to the terminal device, so that the terminal device receives the capability group information sent by the network device, that is, the capability group information is configured by the network device.
  • the network device sends non-access stratum (NAS) signaling or access stratum (AS) signaling to the terminal device, where the NAS signaling or AS signaling carries the information of the capability packet Therefore, the terminal device obtains the information of the capability packet by receiving non-access layer NAS signaling or access layer AS signaling sent by the network device.
  • NAS non-access stratum
  • AS access stratum
  • the terminal device may obtain information of the capability group pre-stored in the terminal device, that is, the information of the capability group is preset.
  • the information of the capability grouping may be predetermined in the protocol.
  • the multiple capability groups may include capability groups divided for wireless capabilities (such as capabilities related to wireless access), and may also include capabilities divided for core network capabilities (such as capabilities related to the core network). group.
  • capability groups divided for wireless capabilities such as capabilities related to wireless access
  • core network capabilities such as capabilities related to the core network. group.
  • the at least one capability group may include at least one of the following capabilities: Carrier Aggregation (CA) capability, Evolved Multimedia Broadcast Multicast Service (eMBMS) capability, supported frequency range ( Frequency (Range, Range, FR), Internet of Vehicles (Everything, V2X) communication capabilities, and beam transmission capabilities.
  • CA Carrier Aggregation
  • eMBMS Evolved Multimedia Broadcast Multicast Service
  • FR Frequency
  • V2X Internet of Vehicles
  • beam transmission capabilities beam transmission capabilities.
  • the carrier aggregation capability includes, for example, a two-carrier aggregation (CC) capability (2CC), a three-carrier aggregation capability (3CC) in carrier aggregation, a four-carrier aggregation (4CC) in carrier aggregation, and the like.
  • the frequency range includes, for example, FR1 (for example, a frequency band below 6 GHz), FR (for example, a millimeter wave frequency band), and the like.
  • Beam transmission capabilities include, for example, support for 8-beam transmission and 4-beam transmission.
  • the at least one capability group also includes capability groups divided for other wireless capability information (UE Radio Capability Information) and core network capability information (UE Core Network Capability Information), such as supported antenna ports, supported wireless access types (Radio Access Type, RAT), power level, packet service handover (PSHO) capabilities, supported security algorithms, whether to support single radio voice call continuity (SRVCC), and so on.
  • UE Radio Capability Information UE Radio Capability Information
  • UE Core Network Capability Information UE Core Network Capability Information
  • supported antenna ports such as supported antenna ports, supported wireless access types (Radio Access Type, RAT), power level, packet service handover (PSHO) capabilities, supported security algorithms, whether to support single radio voice call continuity (SRVCC), and so on.
  • UE Radio Capability Information UE Radio Capability Information
  • UE Core Network Capability Information such as supported antenna ports, supported wireless access types (Radio Access Type, RAT), power level, packet service handover (PSHO) capabilities, supported security algorithms, whether to support single radio voice call continuity (SRVCC), and so on.
  • the terminal device reports to the network device an identification 0, indicating that the terminal device has the capability of 2CC CA; the terminal device reports to the network device
  • the identifier 1 indicates that the terminal device has the capability of 3CC CA; the terminal device reports the identifier 2 to the network device, indicating that the terminal device has the capability of 4CCCA; the terminal device reports the identifier 3 to the network device, which indicates that the terminal device has eMBMS capability; the terminal device
  • the identity 4 is reported to the network equipment, indicating that the terminal equipment has V2X communication capability;
  • the identity 5 is reported to the network equipment, indicating that the terminal equipment supports transmission in the FR1 band;
  • the identity 6 is reported to the network equipment, indicating that the terminal equipment supports Transmission in the FR 2 band;
  • the terminal device reports ID 7 to the network device, indicating that the terminal device supports a maximum of 8 beam transmission; the terminal device reports ID 8 to the network device, indicating that the terminal device supports a maximum of 4 beam
  • this capability group may also include more subdivided capabilities, such as shown in Table 2 or Table 3.
  • the following uses 2CC CA, 3CC CA, and V2X communication capabilities in the carrier aggregation capability as examples for illustration.
  • the available frequency bands (band, B) under 2CC CA include B1 + B7, B1 + B5, B5 + B7, etc .
  • the available frequency bands under 3CC CA include B1 + B5 + B7, B1 + B5 + B8, B5 + B7 + B8, etc .
  • V2X communication capabilities include Uu interface-based communication capabilities and Sidelink (SL) -based communication capabilities, and further, Uu interface-based communication capabilities include semi-static Scheduling (Semi-Persistent Scheduling, SPS) capabilities, resource sensing capabilities, etc.
  • the frequency bands available under 2CC CA include B1, B5, B7, etc .
  • the frequency bands available under 3CC CA include B1, B5, B7, B8, etc .
  • V2X communication capabilities include communication capabilities based on Uu interface.
  • the communication capability based on the side link, and further, the communication capability based on the Uu interface includes a semi-static scheduling capability, a resource listening capability, and the like.
  • the terminal device if the terminal device reports the identifier 100, it means that the terminal device supports all frequency band combinations under 2CC CA, that is, supports all frequency band combinations such as B1 + B5, B1 + B7, and B5 + B7; if the terminal If the device reports ID 110, it only supports B1 + B5; if the terminal device reports ID 110 and 120, it supports B1 + B5 and B1 + B7; if the terminal device reports ID 210, it supports B1 + B5 + B7.
  • the terminal device reports the identifier 320, it indicates that the terminal device supports side-link transmission in V2X; if the terminal device reports the identifiers 321 and 322, it indicates that the terminal device supports the side-link transmission.
  • the terminal device reports the identifier 110, which indicates that the terminal device can support all frequency band combinations including B1, such as B1 + B5, B1 + B7, and so on;
  • the terminal device reports the identifier 120, which indicates that the terminal device can support all frequency band combinations including B5, such as B1 + B5, B5 + B7, and so on.
  • the method of dividing the capability groups shown in Tables 1 to 3 is only an example, and the embodiments of the present application may also adopt other method of dividing the capability groups, and the granularity of the capability division is not limited. Other methods capable of achieving the capability group division should fall into the protection scope of the embodiments of this application.
  • the method may further include 330.
  • the terminal device reports the information of the additional capability and the additional instruction information to the network device.
  • the additional instruction information is used to instruct the terminal device to add the additional capability or decrease the additional capability based on the at least one capability group.
  • the additional capability may include at least one capability.
  • the terminal device after the terminal device reports the identities of capability group 1, capability group 2, and capability group 3, it can also report additional capabilities 1 to additional capabilities n.
  • the capabilities included in these capability groups are added to or subtracted from these additional capabilities. Can finally constitute the capabilities of the terminal equipment.
  • the terminal device After the terminal device reports the identity of the capability group to which some of its capabilities belong, it may still have some capabilities that cannot find the appropriate capability group to which it belongs. At this time, this part of the capability can be reported separately, and this part of the capability information that needs to be added is directly reported to the network device.
  • the terminal device reports ID 210 to the network device to indicate that the terminal device can support all frequency bands including B1 Combinations, such as B1 + B5 + B7, B1 + B5 + B8, B5 + B7 + B8, and so on.
  • B1 Combinations such as B1 + B5 + B7, B1 + B5 + B8, B5 + B7 + B8, and so on.
  • the terminal device also separately supports B5 + B7 + B8, then the terminal device can report its own additional capability, namely B5 + B7 + B8, to the network device in the manner of 220 in FIG. 2 and indicate to the network device
  • the additional capability is an increased capability, so that the network device determines that the capability of the terminal device includes each capability in the capability group indicated by the identifier 210 and the capabilities B5 + B7 + B8.
  • the terminal device can directly report to the network device in a separate reporting manner. This part of the ability needs to be subtracted.
  • the terminal device reports ID 210 to the network device to indicate that the terminal device can support all frequency bands including B1 Combinations, such as B1 + B5 + B7, B1 + B5 + B8, B5 + B7 + B8, and so on.
  • B1 Combinations such as B1 + B5 + B7, B1 + B5 + B8, B5 + B7 + B8, and so on.
  • the terminal device also reports an additional capability information and additional instruction information, and the additional instruction information indicates that the terminal device does not support B5 + B7 + B8, then the network device will determine that the terminal device's capabilities include the Individual capabilities in the capability group but need to exclude capabilities B5 + B7 + B8.
  • the method further includes: the network device sends a capability request message to the terminal device, where the capability request message is used to instruct the terminal device to report the identity of the at least one capability group.
  • the method further includes: the terminal device receives a capability request message sent by the network device, and the capability request message is used to instruct the terminal device to report the identity of the at least one capability group.
  • the terminal device can autonomously report the identity of the capability group to which the capability belongs, or it can send the identity of the capability group according to the capability request message sent by the network device at the request of the network device.
  • the size of the sequence numbers of the above processes does not mean the order of execution.
  • the execution order of each process should be determined by its function and internal logic, and should not deal with the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • FIG. 5 is a schematic block diagram of a terminal device 500 according to an embodiment of the present application.
  • the terminal device 500 includes a transceiver unit 510, which is configured to report to the network device an identifier of at least one capability group to which the capability supported by the terminal device belongs.
  • the various capabilities that the terminal device may support are grouped.
  • the terminal device reports to the network device the identity of the capability group to which the supported capability belongs, so that the network device determines the terminal device support according to the received capability group identification.
  • Ability Since the terminal device does not need to report each supported capability information to the network device, the signaling overhead generated when the terminal device reports the capability information is reduced.
  • the terminal device further includes an obtaining unit 520, configured to obtain information of a capability group, where the information of the capability group includes multiple capability groups and capabilities included in each capability group.
  • an obtaining unit 520 configured to obtain information of a capability group, where the information of the capability group includes multiple capability groups and capabilities included in each capability group.
  • the acquiring unit 520 is specifically configured to: receive the capability group information sent by a network device through the transceiver unit 510; or acquire the capability group information pre-stored in the terminal device.
  • the transceiver unit 510 is specifically configured to: receive non-access layer NAS signaling or access layer AS signaling sent by the network device, and the NAS signaling or AS signaling carries the capability packet Information.
  • the transceiver unit 510 is further configured to report the additional capability information and the additional indication information to the network device, where the additional indication information is used to instruct the terminal device on the basis of the at least one capability group
  • the additional capability is increased or decreased, and the additional capability includes at least one capability.
  • the transceiver unit 510 is further configured to receive a capability request message sent by the network device, where the capability request message is used to instruct the terminal device to report an identifier of the at least one capability group.
  • the at least one capability group includes at least one of the following capabilities: two-carrier aggregation capability 2CC CA in carrier aggregation, three-carrier aggregation capability 3CA CA in carrier aggregation, four-carrier aggregation capability in carrier aggregation 5CC CA, frequency range FR1, frequency range FR2, enhanced multimedia broadcast multicast eMBMS capability, vehicle networking V2X communication capability, and beam transmission capability.
  • terminal device 500 may perform corresponding operations performed by the terminal device in the foregoing method 300, and for brevity, details are not described herein again.
  • FIG. 6 is a schematic block diagram of a network device 600 according to an embodiment of the present application.
  • the network device 600 includes a transceiver unit 610, which is configured to receive an identifier of at least one capability group to which a capability supported by the terminal device reported by the terminal device belongs.
  • the various capabilities that the terminal device may support are grouped.
  • the terminal device reports to the network device the identity of the capability group to which the supported capability belongs, so that the network device determines the terminal device support according to the received capability group identification.
  • Ability Since the terminal device does not need to report each supported capability information to the network device, the signaling overhead generated when the terminal device reports the capability information is reduced.
  • the network device further includes a processing unit 620, configured to determine a capability supported by the terminal device according to the at least one capability group.
  • the transceiver unit 610 is further configured to send information of a capability group to the terminal device, where the capability group information includes multiple capability groups and capabilities included in each capability group.
  • the transceiver unit 610 is specifically configured to send NAS signaling or AS signaling to the terminal device, and the NAS signaling or AS signaling carries information of the capability packet.
  • the transceiver unit 610 is further configured to receive information about additional capabilities and additional indication information reported by the terminal device, where the additional indication information is used to indicate that the terminal device is in the at least one capability group.
  • the additional capability is increased or decreased on the basis, and the additional capability includes at least one capability.
  • the transceiver unit 610 is further configured to send a capability request message to the terminal device, where the capability request message is used to instruct the terminal device to report an identifier of the at least one capability group.
  • the capability group includes at least one of the following capabilities: two-carrier aggregation capability 2CC CA in carrier aggregation, three-carrier aggregation capability 3CC CA in carrier aggregation, four-carrier aggregation capability 4CC CA in carrier aggregation, Frequency range FR1, frequency range FR2, enhanced multimedia broadcast multicast eMBMS capability, V2X communication capability of the car network, and beam transmission capability.
  • the network device 600 may perform corresponding operations performed by the network device in the foregoing method 300. For brevity, details are not described herein again.
  • FIG. 7 is a schematic structural diagram of a communication device 700 according to an embodiment of the present application.
  • the communication device 700 shown in FIG. 7 includes a processor 710, and the processor 710 may call and run a computer program from a memory to implement the method in the embodiment of the present application.
  • the communication device 700 may further include a memory 720.
  • the processor 710 may call and run a computer program from the memory 720 to implement the method in the embodiment of the present application.
  • the memory 720 may be a separate device independent of the processor 710, or may be integrated in the processor 710.
  • the communication device 700 may further include a transceiver 730, and the processor 710 may control the transceiver 730 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other information. Information or data sent by the device.
  • the transceiver 730 may include a transmitter and a receiver.
  • the transceiver 730 may further include antennas, and the number of antennas may be one or more.
  • the communication device 700 may specifically be a terminal device in the embodiment of the present application, and the communication device 700 may implement a corresponding process implemented by the terminal device in each method in the embodiments of the present application. .
  • the communication device 700 may specifically be a network device according to an embodiment of the present application, and the communication device 700 may implement a corresponding process implemented by a network device in each method in the embodiments of the present application. .
  • FIG. 8 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • the chip 800 shown in FIG. 8 includes a processor 810, and the processor 810 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
  • the chip 800 may further include a memory 820.
  • the processor 810 may call and run a computer program from the memory 820 to implement the method in the embodiment of the present application.
  • the memory 820 may be a separate device independent of the processor 810, or may be integrated in the processor 810.
  • the chip 800 may further include an input interface 830.
  • the processor 810 may control the input interface 830 to communicate with other devices or chips. Specifically, the processor 810 may obtain information or data sent by other devices or chips.
  • the chip 800 may further include an output interface 840.
  • the processor 810 may control the output interface 840 to communicate with other devices or chips. Specifically, the processor 810 may output information or data to the other devices or chips.
  • the chip may be applied to the terminal device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the terminal device in each method of the embodiment of the present application.
  • the chip may implement the corresponding process implemented by the terminal device in each method of the embodiment of the present application.
  • the chip may be applied to the network device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the chip may be applied to the network device in the embodiment of the present application, and the chip may implement the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-level chip, a system chip, a chip system, or a system-on-chip.
  • the processor in the embodiment of the present application may be an integrated circuit chip and has a signal processing capability.
  • each step of the foregoing method embodiment may be completed by using an integrated logic circuit of hardware in a processor or an instruction in a form of software.
  • the above processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (Field, Programmable Gate Array, FPGA), or other Programming logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA off-the-shelf programmable gate array
  • Various methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
  • the steps of the method disclosed in combination with the embodiments of the present application may be directly implemented by a hardware decoding processor, or may be performed by using a combination of hardware and software modules in the decoding processor.
  • the software module may be located in a mature storage medium such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, and the like.
  • the storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the foregoing method in combination with its hardware.
  • the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), and an electronic memory. Erase programmable read-only memory (EPROM, EEPROM) or flash memory.
  • the volatile memory may be Random Access Memory (RAM), which is used as an external cache.
  • RAM Static Random Access Memory
  • DRAM Dynamic Random Access Memory
  • Synchronous Dynamic Random Access Memory Synchronous Dynamic Random Access Memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double SDRAM, DDR SDRAM enhanced synchronous dynamic random access memory
  • Enhanced SDRAM, ESDRAM synchronous connection dynamic random access memory
  • Synchronous DRAM Synchronous Dynamic Random Access Memory
  • Enhanced SDRAM Enhanced SDRAM, ESDRAM
  • synchronous connection dynamic random access memory Synchrobus RAM, SLDRAM
  • Direct Rambus RAM Direct Rambus RAM
  • the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (Double SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct RAMbus RAM, DR RAM) and so on. That is, the memories in the embodiments of the present application are intended to include, but not limited to, these and any other suitable types of memories.
  • FIG. 9 is a schematic block diagram of a communication system 900 according to an embodiment of the present application.
  • the communication system 900 includes a terminal device 910 and a network device 920.
  • the terminal device 910 is configured to report to the network device an identifier of at least one capability group to which the capabilities supported by the terminal device belong.
  • the network device 920 is configured to receive an identifier of at least one capability group to which a capability supported by the terminal device reported by the terminal device belongs.
  • the terminal device 910 may be used to implement the corresponding functions implemented by the terminal device in the method 300 described above, and the composition of the terminal device 910 may be shown in the terminal device 400 in FIG. 4. .
  • the network device 920 may be used to implement the corresponding functions implemented by the network device in the foregoing method 300, and the composition of the network device 920 may be shown in the network device 500 in FIG. .
  • An embodiment of the present application further provides a computer-readable storage medium for storing a computer program.
  • the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method in the embodiment of the present application.
  • the computer-readable storage medium can be applied to the terminal device in the embodiments of the present application, and the computer program causes the computer to execute the corresponding processes implemented by the terminal device in each method of the embodiments of the present application. For simplicity, here No longer.
  • An embodiment of the present application further provides a computer program product, including computer program instructions.
  • the computer program product can be applied to the network device in the embodiment of the present application, and the computer program instruction causes the computer to execute a corresponding process implemented by the network device in each method in the embodiment of the present application. More details.
  • the computer program product can be applied to the terminal device in the embodiment of the present application, and the computer program instruction causes the computer to execute a corresponding process implemented by the terminal device in each method in the embodiment of the present application. More details.
  • the embodiment of the present application also provides a computer program.
  • the computer program may be applied to a network device in the embodiment of the present application.
  • the computer program When the computer program is run on a computer, the computer is caused to execute a corresponding process implemented by the network device in each method in the embodiment of the present application. , Will not repeat them here.
  • the computer program may be applied to the terminal device in the embodiment of the present application.
  • the computer program When the computer program is run on a computer, the computer is caused to execute a corresponding process implemented by the terminal device in each method in the embodiment of the present application. , Will not repeat them here.
  • B corresponding to (corresponding to) A means that B is associated with A, and B can be determined according to A.
  • determining B based on A does not mean determining B based on A alone, but also determining B based on A and / or other information.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the unit is only a logical function division.
  • multiple units or components may be combined or may be combined. Integration into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, may be located in one place, or may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each of the units may exist separately physically, or two or more units may be integrated into one unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of this application is essentially a part that contributes to the existing technology or a part of the technical solution can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in the embodiments of the present application.
  • the aforementioned storage media include: U disks, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks or compact discs, and other media that can store program codes .

Landscapes

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

Abstract

本申请公开了一种能力上报的方法和设备，能够减小终端设备的能力信息上报的信令开销。该方法包括：终端设备确定所述终端设备所支持的能力所属的至少一个能力组；所述终端设备向网络设备上报所述至少一个能力组的标识。

Description

能力上报的方法和设备 技术领域
本申请实施例涉及通信领域，并且更具体地，涉及能力上报的方法和设备。
背景技术
终端设备进入网络例如附着或跟踪区更新(Tracking Area Update，TAU)时，如果网络设备没有存储终端设备的能力信息，则终端设备需要向网络设备上报自己的能力信息。网络可以把终端设备的能力信息存储在核心网实体例如移动性管理实体(Mobility Management Entity，MME)、认证管理功能(Authentication Management Function，AMF)实体等。核心网在下次终端设备接入时会把相应的能力传送给接入网，从而避免终端设备重复上报自己的能力信息。
然而，终端设备的能力信息的上报引入了极大的信令开销，如何减小终端设备的能力信息上报的信令开销，称为亟待解决的问题。
发明内容
本申请实施例提供了一种能力上报的方法和设备，能够减小终端设备的能力信息上报的信令开销。
第一方面，提供了一种能力上报的方法，包括：终端设备向网络设备上报所述终端设备所支持的能力所属的至少一个能力组的标识。
第二方面，提供了一种能力上报的方法，包括：网络设备接收终端设备上报的所述终端设备所支持的能力所属的至少一个能力组的标识。
第三方面，提供了一种终端设备，该终端设备可以执行上述第一方面或第一方面的任意可选的实现方式中的方法。具体地，该终端设备可以包括用于执行上述第一方面或第一方面的任意可能的实现方式中的方法的功能模块。
第四方面，提供了一种网络设备，该网络设备可以执行上述第二方面或第二方面的任意可选的实现方式中的方法。具体地，该网络设备可以包括用于执行上述第二方面或第二方面的任意可能的实现方式中的方法的功能模块。
第五方面，提供了一种终端设备，包括处理器和存储器。该存储器用于 存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述第一方面或第一方面的任意可能的实现方式中的方法。
第六方面，提供了一种网络设备，包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述第二方面或第二方面的任意可能的实现方式中的方法。
第七方面，提供了一种芯片，用于实现上述第一方面或第一方面的任意可能的实现方式中的方法。具体地，该芯片包括处理器，用于从存储器中调用并运行计算机程序，使得安装有该芯片的设备执行如上述第一方面或第一方面的任意可能的实现方式中的方法。
第八方面，提供了一种芯片，用于实现上述第二方面或第二方面的任意可能的实现方式中的方法。具体地，该芯片包括处理器，用于从存储器中调用并运行计算机程序，使得安装有该芯片的设备执行如上述第二方面或第二方面的任意可能的实现方式中的方法。
第九方面，提供了一种计算机可读存储介质，用于存储计算机程序，该计算机程序使得计算机执行上述第一方面或第一方面的任意可能的实现方式中的方法。
第十方面，提供了一种计算机可读存储介质，用于存储计算机程序，该计算机程序使得计算机执行上述第二方面或第二方面的任意可能的实现方式中的方法。
第十一方面，提供了一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行上述第一方面或第一方面的任意可能的实现方式中的方法。
第十二方面，提供了一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行上述第二方面或第二方面的任意可能的实现方式中的方法。
第十三方面，提供了一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面或第一方面的任意可能的实现方式中的方法。
第十四方面，提供了一种计算机程序，当其在计算机上运行时，使得计算机执行上述第二方面或第二方面的任意可能的实现方式中的方法。
第十五方面，提供了一种通信系统，包括终端设备和网络设备。
其中，所述终端设备用于：向网络设备上报所述终端设备所支持的能力所属的至少一个能力组的标识。
其中，所述网络端设备用于：接收终端设备上报的所述终端设备所支持的能力所属的至少一个能力组的标识。
其中，所述终端设备用于执行上述第一方面或第一方面的任意可能的实现方式中的方法，以及所述网络设备用于执行上述第二方面或第二方面的任意可能的实现方式中的方法。
基于上述技术方案，终端设备将自己所支持的能力所属的能力组的标识上报给网络设备，从而网络设备根据接收到的能力组的标识确定终端设备所支持的能力。由于终端设备可以将自己所支持的能力所属的能力组的标识上报给网络设备，而无需将所支持的各个能力信息分别上报给网络设备，从而降低了终端设备上报能力信息时产生的信令开销。
附图说明
图1是根据本申请实施例的无线通信系统的示意图。
图2是终端设备上报能力信息的流程交互图。
图3是本申请实施例的能力上报的方法的流程交互图。
图4是本申请实施例的附加能力上报的示意图。
图5是本申请实施例的终端设备的示意性框图。
图6是本申请实施例的网络设备的示意性框图。
图7是本申请实施例的通信设备的示意性结构图。
图8是本申请实施例的芯片的示意性结构图。
图9是本申请实施例的通信系统的示意性结构图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)系统、先进的长期演进(Advanced long term evolution，LTE-A)系统、新无线(New Radio，NR)系统、NR系统的演进系统、非授权频谱上的LTE(LTE-based access to unlicensed spectrum，LTE-U)系统、非授权频谱上的NR(NR-based access to unlicensed spectrum，NR-U)系统、 通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信系统、无线局域网(Wireless Local Area Networks，WLAN)、无线保真(Wireless Fidelity，WiFi)、下一代通信系统或其他通信系统等。
通常来说，传统的通信系统支持的连接数有限，也易于实现，然而，随着通信技术的发展，移动通信系统将不仅支持传统的通信，还将支持例如，设备到设备(Device to Device，D2D)通信，机器到机器(Machine to Machine，M2M)通信，机器类型通信(Machine Type Communication，MTC)，以及车辆间(Vehicle to Vehicle，V2V)通信等，本申请实施例也可以应用于这些通信系统。
可选地，本申请实施例中的通信系统可以应用于载波聚合(Carrier Aggregation，CA)场景，也可以应用于双连接(Dual Connectivity，DC)场景，还可以应用于独立(Standalone，SA)布网场景。
示例性的，本申请实施例应用的通信系统100如图1所示。该无线通信系统100可以包括网络设备110。网络设备110可以是与终端设备通信的设备。网络设备110可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端设备进行通信。可选地，该网络设备100可以是GSM系统或CDMA系统中的基站(Base Transceiver Station，BTS)，也可以是WCDMA系统中的基站(NodeB，NB)，还可以是LTE系统中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者是NR系统中的网络侧设备，或者是云无线接入网络(Cloud Radio Access Network，CRAN)中的无线控制器，或者该网络设备可以为中继站、接入点、车载设备、可穿戴设备、下一代网络中的网络侧设备或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)中的网络设备等。
该无线通信系统100还包括位于网络设备110覆盖范围内的至少一个终端设备120。作为在此使用的“终端设备”包括但不限于经由有线线路连接，如经由公共交换电话网络(Public Switched Telephone Networks，PSTN)、数字用户线路(Digital Subscriber Line，DSL)、数字电缆、直接电缆连接；和/或另一数据连接/网络；和/或经由无线接口，如，针对蜂窝网络、无线局域网(Wireless Local Area Network，WLAN)、诸如DVB-H网络的数字电视网络、卫星网络、AM-FM广播发送器；和/或另一终端设备的被设置成接收/发送通信信号的装置；和/或物联网(Internet of Things，IoT)设备。被设置成通过无线接口通信的终端设备可以被称为“无线通信终端”、“无线终端”或“移动终端”。
终端设备120可以是移动的或固定的。可选地，终端设备120可以指接入终端、用户设备(User Equipment，UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、未来5G网络中的终端设备或者未来演进的PLMN中的终端设备等。其中，可选地，终端设备120之间也可以进行终端直连(Device to Device，D2D)通信。
具体地，网络设备110可以为小区提供服务，终端设备120通过该小区使用的传输资源(例如，频域资源，或者说，频谱资源)与网络设备110进行通信，该小区可以是网络设备110(例如基站)对应的小区，小区可以属于宏基站，也可以属于小小区(Small cell)对应的基站，这里的小小区可以包括：城市小区(Metro cell)、微小区(Micro cell)、微微小区(Pico cell)、毫微微小区(Femto cell)等，这些小小区具有覆盖范围小、发射功率低的特点，适用于提供高速率的数据传输服务。
图1示例性地示出了一个网络设备和两个终端设备，可选地，该无线通信系统100可以包括多个网络设备并且每个网络设备的覆盖范围内可以包括其它数量的终端设备，本申请实施例对此不做限定。可选地，该无线通信系统100还可以包括网络控制器、移动管理实体等其他网络实体，本申请实施例对此不作限定。
终端设备进入网络例如附着或TAU时，如果网络设备没有存储终端设备的能力信息，则终端设备需要向网络设备上报自己的能力信息。例如图2所示的终端设备上报能力信息的示意性流程图，网络设备可以向终端设备发送UE能力请求消息(UECapabilityEnquiry)，终端设备接收到该能力请求消息后，会向网络设备上报自己的UE能力信息(UECapabilityInformation)。网络可以把终端设备的能力信息存储在核心网实体例如MME、AMF实体等。核心网在下次终端设备接入时会把相应的能力传送给接入网，从而避免终端设备重复上报自己的能力信息。然而，终端设备的能力涉及终端设备的各个软硬件能力，非常复杂，信令开销非常大。
因此，本申请实施例提出，对终端设备可能支持的各种能力进行分组，终端设备通过将自己所支持的能力所属的能力组的标识上报给网络设备，使得网络设备根据接收到的能力组的标识确定终端设备所支持的能力。由于终 端设备可以将自己所支持的能力所属的能力组的标识上报给网络设备，而无需将所支持的各个能力信息分别上报给网络设备，从而降低了终端设备上报能力信息时产生的信令开销。
图3是本申请实施例的能力上报的方法300的流程交互图。图3所示方法可以由终端设备和网络设备执行，该终端设备例如可以为图1中所示的终端设备120，该网络设备例如可以为图1中所示的网络设备。如图3所示，该能力上报的方法300包括：
在310中，终端设备向网络设备上报终端设备所支持的能力所属的至少一个能力组的标识。
在320中，网络设备接收终端设备上报的终端设备所支持的能力所属的该至少一个能力组的标识。
具体地，可以对各种能力信息进行分组，并且每个能力组具有自己唯一的标识，该标识例如可以是该能力组的名称、索引等等。终端设备根据所支持的能力，确定这些能力分别所属的能力组，并将这些能力组的标识上报给网络设备，从而网络设备根据接收到的能力组的标识，可以确定该终端设备所支持的能力，这些标识所指示的能力组中的能力的组合即为该终端设备所支持的能力。
可选地，在310之前，该方法还包括：终端设备获取能力分组的信息。该能力分组的信息包括多个能力组以及每个能力组中包括的能力。
其中，可选地，网络设备可以向终端设备发送能力分组的信息，从而终端设备接收网络设备发送的该能力分组的信息，即该能力分组的信息是网络设备配置的。例如，网络设备向终端设备发送非接入层(Non Access Stratum，NAS)信令或接入层(Access Stratum，AS)信令，其中该NAS信令或AS信令中携带该能力分组的信息，从而终端设备通过接收网络设备发送的非接入层NAS信令或接入层AS信令来获取该能力分组的信息。
或者，可选地，终端设备可以获取预存在该终端设备中的该能力分组的信息，即该能力分组的信息是预设的。例如，该能力分组的信息可以是协议中事先约定的。
本申请实施例中，该多个能力组可以包括针对无线能力(例如与无线接入相关的能力)划分的能力组，也可以包括针对核心网能力(例如与核心网相关的能力)划分的能力组。本申请实施例对此不作任何限定，终端设备的任何能力的上报均可以采用本申请实施例所描述的方法。
例如，该至少一个能力组可以分别包括以下能力中的至少一个能力：载波聚合(Carrier Aggregation，CA)能力、增强型多媒体广播多播(Evolved  Multimedia Broadcast Multicast Service，eMBMS)能力、支持的频率范围(Frequency Range，FR)、车联网(Vehicle to Everything，V2X)通信能力、以及波束(beam)传输能力。
其中，载波聚合能力例如包括两载波聚合(Carrier Component，CC)能力(2CC CA)、载波聚合中的三载波聚合能力3CC CA、载波聚合中的四载波聚合4CC CA等。频率范围例如包括FR 1(例如6GHz以下频段)、FR 2(例如毫米波频段)等。波束传输能力例如包括支持8波束传输、4波束传输等。
此外，该至少一个能力组还包括针对其他无线能力信息(UE Radio Capability Information)和核心网能力信息(UE Core Network Capability Information)划分的能力组，例如所支持的天线端口、支持的无线接入类型(Radio Access Type，RAT)、功率等级、分组业务切换(Packet Service Handover，PSHO)能力、支持的安全算法、是否支持单一无线语音呼叫连续性(Single Radio Voice Call Continuity，SRVCC)等等。
举例来说，如表一所示的各个能力组中包括的能力以及该能力组的标识，终端设备向网络设备上报了标识0，表示终端设备具备2CC CA的能力；终端设备向网络设备上报了标识1，表示终端设备具备3CC CA的能力；终端设备向网络设备上报了标识2，表示终端设备具备4CC CA的能力；终端设备向网络设备上报了标识3，表示终端设备具有eMBMS能力；终端设备向网络设备上报了标识4，表示终端设备具有V2X通信能力；终端设备向网络设备上报了标识5，表示终端设备支持FR 1频段的传输；终端设备向网络设备上报了标识6，表示终端设备支持FR 2频段的传输；终端设备向网络设备上报了标识7，表示终端设备支持最大8波束传输；终端设备向网络设备上报了标识8，表示终端设备支持最大4波束传输。
表一
能力组 能力组的标识
2CC CA 标识0
3CC CA 标识1
4CC CA 标识2
eMBMS 标识3
V2X 标识4
FR 1 标识5
FR 2 标识6
8波束传输 标识7
4波束传输 标识8
…… ……
实际应用中，该能力组中还可以包括更细分的能力，例如表二或表三所示，下面以载波聚合能力中的2CC CA、3CC CA、以及V2X通信能力为例进行说明。
其中，在表二中，2CC CA下可使用的频段(band，B)包括B1+B7、B1+B5和B5+B7等；3CC CA下可使用的频段包括B1+B5+B7、B1+B5+B8、B5+B7+B8等；V2X通信能力中包括基于Uu接口的通信能力和基于侧行链路(Sidelink，SL)的通信能力，并且，进一步地，基于Uu接口的通信能力包括半静态调度(Semi-Persistent Scheduling，SPS)能力、资源侦听(sensing)能力等。
其中，在表三中，2CC CA下可使用的频段包括B1、B5、B7等；3CC CA下可使用的频段包括B1、B5、B7、B8等；V2X通信能力中包括基于Uu接口的通信能力和基于侧行链路的通信能力，并且，进一步地，基于Uu接口的通信能力包括半静态调度能力和资源侦听能力等。
终端设备具备哪些能力，则向网络设备上报这些能力所属的能力组的标识，从而网络设备根据从该终端设备接收到的能力组的标识，确定终端设备的能力。
例如，如表二所示，如果终端设备上报了标识100，则表示该终端设备支持2CC CA下的所有频段组合，即支持B1+B5、B1+B7和B5+B7等所有频段组合；如果终端设备上报了标识110，则表示仅支持B1+B5；如果终端设备上报了标识110和120，则表示支持B1+B5和B1+B7；如果终端设备上报了标识210，则表示支持B1+B5+B7。
又例如，如表二所示，如果终端设备上报了标识320，表示终端设备支持V2X中的侧行链路传输；如果终端设备上报了标识321和322，表示终端设备支持侧行链路中的半静态调度传输和资源侦听。
又例如，如表三所示，只要终端设备能够支持2CC CA下的频带B1，则终端设备上报标识110，表示终端设备能够支持包括B1的所有频带组合例如B1+B5、B1+B7等等；只要终端设备能够支持2CC CA下的频带B5，则终端设备上报标识120，表示终端设备能够支持包括B5的所有频带组合例如B1+B5、B5+B7等等。
表二
Figure PCTCN2018099688-appb-000001
Figure PCTCN2018099688-appb-000002
表三
Figure PCTCN2018099688-appb-000003
Figure PCTCN2018099688-appb-000004
表一至表三所示的能力组的划分方式仅仅为一个示例，本申请实施例也可以采用其他能力组划分方式，并且对能力划分的粒度也不做限定。其他能够实现能力组划分的方式均应落入本申请实施例的保护范围。
可选地，如图3所示，该方法还可以包括330。
在330中，终端设备向网络设备上报附加能力的信息以及附加指示信息。
其中，该附加指示信息用于指示该终端设备在该至少一个能力组的基础上增加该附加能力或者减少该附加能力。
其中，该附加能力可以包括至少一个能力。
例如图4所示，终端设备上报能力组1、能力组2和能力组3的标识之后，还可以上报附加能力1至附加能力n，这些能力组中包括的能力加上或减去这些附加能力，最终可以构成终端设备的能力。
终端设备在上报自己的部分能力所属的能力组的标识后，可能还剩余一些能力找不到其所属的合适的能力组。此时，这部分能力可以采用单独上报的方式，直接向网络设备上报需要增加的这部分能力信息。
例如，参考上述表三，如果终端设备支持3CC CA，并且支持3CC CA中的频带B1，这时，终端设备会向网络设备上报标识210，以表示该终端设备能够支持包括B1在内的所有频带组合，例如B1+B5+B7、B1+B5+B8、B5+B7+B8等。但是，如果终端设备另外还单独支持B5+B7+B8，那么终端设备可以采用例如图2中的220中的方式，向网络设备上报自己的附加能力即B5+B7+B8，并向网络设备指示该附加能力为增加的能力，从而网络设备会确定终端设备的能力包括标识210指示的能力组中的各个能力以及能力B5+B7+B8。
或者，终端设备在上报自己具备的部分能力所属的能力组的标识后，发现上报的能力组中的某些能力不支持时，此时，终端设备可以采用单独上报的方式，直接向网络设备上报需要减去的这部分能力。
例如，参考上述表三，如果终端设备支持3CC CA，并且支持3CC CA中的频带B1，这时，终端设备会向网络设备上报标识210，以表示该终端设备能够支持包括B1在内的所有频带组合，例如B1+B5+B7、B1+B5+B8、B5+B7+B8等。但是，如果终端设备还上报了一个附加能力信息和附加指示信息，并且该附加指示信息指示该终端设备不支持B5+B7+B8，那么，网络设备则会确定终端设备的能力包括标识210指示的能力组中的各个能力但是需要排除能力B5+B7+B8。
可选地，在310之前，该方法还包括：网络设备向终端设备发送能力请求消息，该能力请求消息用于指示终端设备上报该至少一个能力组的标识。
相应地，在310之前，该方法还包括：终端设备接收网络设备发送的能力请求消息，该能力请求消息用于指示终端设备上报该至少一个能力组的标识。
也就是说，终端设备可以自主地上报自己的能力所属的能力组的标识，也可以在网络设备的请求下，根据网络设备发送的能力请求消息发送该能力组的标识。
需要说明的是，在不冲突的前提下，本申请描述的各个实施例和/或各个实施例中的技术特征可以任意的相互组合，组合之后得到的技术方案也应落入本申请的保护范围。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
上文中详细描述了根据本申请实施例的通信方法，下面将结合图4至图8，描述根据本申请实施例的装置，方法实施例所描述的技术特征适用于以下装置实施例。
图5是根据本申请实施例的终端设备500的示意性框图。如图5所示，该终端设备500包括收发单元510，该收发单元510用于：向网络设备上报所述终端设备所支持的能力所属的至少一个能力组的标识。
因此，对终端设备可能支持的各种能力进行分组，终端设备通过将自己所支持的能力所属的能力组的标识上报给网络设备，使得网络设备根据接收到的能力组的标识确定终端设备所支持的能力。由于终端设备无需将所支持的各个能力信息分别上报给网络设备，从而降低了终端设备上报能力信息时产生的信令开销。
可选地，所述终端设备还包括获取单元520，用于：获取能力分组的信息，所述能力分组的信息包括多个能力组以及每个能力组中包括的能力。
可选地，所述获取单元520具体用于：通过所述收发单元510接收网络设备发送的所述能力分组的信息；或者，获取预存在所述终端设备中的所述能力分组的信息。
可选地，所述收发单元510具体用于：接收所述网络设备发送的非接入层NAS信令或接入层AS信令，所述NAS信令或AS信令中携带所述能力分组的信息。
可选地，所述收发单元510还用于：向所述网络设备上报附加能力的信 息以及附加指示信息，所述附加指示信息用于指示所述终端设备在所述至少一个能力组的基础上增加所述附加能力或者减少所述附加能力，所述附加能力包括至少一个能力。
可选地，所述收发单元510还用于：接收所述网络设备发送的能力请求消息，所述能力请求消息用于指示所述终端设备上报所述至少一个能力组的标识。
可选地，所述至少一个能力组分别包括以下能力中的至少一种：载波聚合中的两载波聚合能力2CC CA、载波聚合中的三载波聚合能力3CC CA、载波聚合中的四载波聚合能力5CC CA、频率范围FR 1、频率范围FR 2、增强型多媒体广播多播eMBMS能力、车联网V2X通信能力、以及波束传输能力。
应理解，该终端设备500可以执行上述方法300中由终端设备执行的相应操作，为了简洁，在此不再赘述。
图6是根据本申请实施例的网络设备600的示意性框图。如图6所示，该网络设备600包括收发单元610，该收发单元610用于：接收终端设备上报的所述终端设备所支持的能力所属的至少一个能力组的标识。
因此，对终端设备可能支持的各种能力进行分组，终端设备通过将自己所支持的能力所属的能力组的标识上报给网络设备，使得网络设备根据接收到的能力组的标识确定终端设备所支持的能力。由于终端设备无需将所支持的各个能力信息分别上报给网络设备，从而降低了终端设备上报能力信息时产生的信令开销。
可选地，所述网络设备还包括处理单元620，用于：根据所述至少一个能力组，确定所述终端设备所支持的能力。
可选地，所述收发单元610还用于：向所述终端设备发送能力分组的信息，所述能力分组的信息包括多个能力组以及每个能力组中包括的能力。
可选地，所述收发单元610具体用于：向所述终端设备发送NAS信令或AS信令，所述NAS信令或AS信令中携带所述能力分组的信息。
可选地，所述收发单元610还用于：接收所述终端设备上报的报附加能力的信息以及附加指示信息，所述附加指示信息用于指示所述终端设备在所述至少一个能力组的基础上增加所述附加能力或者减少所述附加能力，所述附加能力包括至少一个能力。
可选地，所述收发单元610还用于：向所述终端设备发送能力请求消息，所述能力请求消息用于指示所述终端设备上报所述至少一个能力组的标识。
可选地，所述能力组包括以下能力中的至少一种：载波聚合中的两载波 聚合能力2CC CA、载波聚合中的三载波聚合能力3CC CA、载波聚合中的四载波聚合能力4CC CA、频率范围FR 1、频率范围FR 2、增强型多媒体广播多播eMBMS能力、车联网V2X通信能力、以及波束传输能力。
应理解，该网络设备600可以执行上述方法300中由网络设备执行的相应操作，为了简洁，在此不再赘述。
图7是本申请实施例提供的一种通信设备700示意性结构图。图7所示的通信设备700包括处理器710，处理器710可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图7所示，通信设备700还可以包括存储器720。其中，处理器710可以从存储器720中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器720可以是独立于处理器710的一个单独的器件，也可以集成在处理器710中。
可选地，如图7所示，通信设备700还可以包括收发器730，处理器710可以控制该收发器730与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器730可以包括发射机和接收机。收发器730还可以进一步包括天线，天线的数量可以为一个或多个。
可选地，该通信设备700具体可为本申请实施例的终端设备，并且该通信设备700可以实现本申请实施例的各个方法中由终端设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该通信设备700具体可为本申请实施例的网络设备，并且该通信设备700可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
图8是本申请实施例的芯片的示意性结构图。图8所示的芯片800包括处理器810，处理器810可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图8所示，芯片800还可以包括存储器820。其中，处理器810可以从存储器820中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器820可以是独立于处理器810的一个单独的器件，也可以集成在处理器810中。
可选地，该芯片800还可以包括输入接口830。其中，处理器810可以控制该输入接口830与其他设备或芯片进行通信，具体地，可以获取其他设 备或芯片发送的信息或数据。
可选地，该芯片800还可以包括输出接口840。其中，处理器810可以控制该输出接口840与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
可选地，该芯片可应用于本申请实施例中的终端设备，并且该芯片可以实现本申请实施例的各个方法中由终端设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该芯片可应用于本申请实施例中的网络设备，并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片、系统芯片、芯片系统或片上系统芯片等。
应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或者可以包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存 取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，上述存储器为示例性但不是限制性说明，例如，本申请实施例中的存储器还可以是静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
图9是根据本申请实施例的通信系统900的示意性框图。如图9所示，该通信系统900包括终端设备910和网络设备920。
其中，该终端设备910用于：向网络设备上报所述终端设备所支持的能力所属的至少一个能力组的标识。
其中，该网络设备920用于：接收终端设备上报的所述终端设备所支持的能力所属的至少一个能力组的标识。
其中，该终端设备910可以用于实现上述方法300中由终端设备实现的相应的功能，以及该终端设备910的组成可以如图4中的终端设备400所示，为了简洁，在此不再赘述。
其中，该网络设备920可以用于实现上述方法300中由网络设备实现的相应的功能，以及该网络设备920的组成可以如图5中的网络设备500所示，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机可读存储介质，用于存储计算机程序。可选的，该计算机可读存储介质可应用于本申请实施例中的网络设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。可选地，该计算机可读存储介质可应用于本申请实施例中的终端设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由终端设备实现的相应流程，为了简洁，在此不 再赘述。
本申请实施例还提供了一种计算机程序产品，包括计算机程序指令。可选的，该计算机程序产品可应用于本申请实施例中的网络设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。可选地，该计算机程序产品可应用于本申请实施例中的终端设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序。可选的，该计算机程序可应用于本申请实施例中的网络设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。可选地，该计算机程序可应用于本申请实施例中的终端设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由终端设备实现的相应流程，为了简洁，在此不再赘述。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
还应理解，在本发明实施例中，“与A相应(对应)的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，该单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的 耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (39)

  1. 一种能力上报的方法，其特征在于，所述方法包括：
    终端设备向网络设备上报所述终端设备所支持的能力所属的至少一个能力组的标识。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述终端设备获取能力分组的信息，所述能力分组的信息包括多个能力组以及每个能力组中包括的能力。
  3. 根据权利要求2所述的方法，其特征在于，所述终端设备获取能力分组的信息，包括：
    所述终端设备接收网络设备发送的所述能力分组的信息；或者，
    所述终端设备获取预存在所述终端设备中的所述能力分组的信息。
  4. 根据权利要求3所述的方法，其特征在于，所述终端设备接收网络设备发送的所述能力分组的信息，包括：
    所述终端设备接收所述网络设备发送的非接入层NAS信令或接入层AS信令，所述NAS信令或AS信令中携带所述能力分组的信息。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备向所述网络设备上报附加能力的信息以及附加指示信息，所述附加指示信息用于指示所述终端设备在所述至少一个能力组的基础上增加所述附加能力或者减少所述附加能力，所述附加能力包括至少一个能力。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备接收所述网络设备发送的能力请求消息，所述能力请求消息用于指示所述终端设备上报所述至少一个能力组的标识。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，所述至少一个能力组分别包括以下能力中的至少一种：
    载波聚合中的两载波聚合能力2CC CA、载波聚合中的三载波聚合能力3CC CA、载波聚合中的四载波聚合能力4CC CA、频率范围FR 1、频率范围FR 2、增强型多媒体广播多播eMBMS能力、车联网V2X通信能力、以及波束传输能力。
  8. 一种能力上报的方法，其特征在于，所述方法包括：
    网络设备接收终端设备上报的所述终端设备所支持的能力所属的至少一个能分组的标识。
  9. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述网络设备根据所述至少一个能力组，确定所述终端设备所支持的能力。
  10. 根据权利要求8或9所述的方法，其特征在于，所述方法还包括：
    所述网络设备向所述终端设备发送能力分组的信息，所述能力分组的信息包括多个能力组以及每个能力组中包括的能力。
  11. 根据权利要求10所述的方法，其特征在于，所述网络设备向所述终端设备发送能力分组的信息，包括：
    所述网络设备向所述终端设备发送非接入层NAS信令或接入层AS信令，所述NAS信令或AS信令中携带所述能力分组的信息。
  12. 根据权利要求8至11中任一项所述的方法，其特征在于，所述方法还包括：
    所述网络设备接收所述终端设备上报的报附加能力的信息以及附加指示信息，所述附加指示信息用于指示所述终端设备在所述至少一个能力组的基础上增加所述附加能力或者减少所述附加能力，所述附加能力包括至少一个能力。
  13. 根据权利要求8至12中任一项所述的方法，其特征在于，所述方法还包括：
    所述网络设备向所述终端设备发送能力请求消息，所述能力请求消息用于指示所述终端设备上报所述至少一个能力组的标识。
  14. 根据权利要求8至13中任一项所述的方法，其特征在于，所述能力组包括以下能力中的至少一种：
    载波聚合中的两载波聚合能力2CC CA、载波聚合中的三载波聚合能力3CC CA、载波聚合中的四载波聚合能力4CC CA、频率范围FR 1、频率范围FR 2、增强型多媒体广播多播eMBMS能力、车联网V2X通信能力、以及波束传输能力。
  15. 一种终端设备，其特征在于，所述终端设备包括：
    收发单元，用于向网络设备上报所述终端设备所支持的能力所属的至少一个能力组的标识。
  16. 根据权利要求15所述的终端设备，其特征在于，所述终端设备还包括获取单元，用于：
    获取能力分组的信息，所述能力分组的信息包括多个能力组以及每个能力组中包括的能力。
  17. 根据权利要求16所述的终端设备，其特征在于，所述获取单元具 体用于：
    通过所述收发单元接收网络设备发送的所述能力分组的信息；或者，
    获取预存在所述终端设备中的所述能力分组的信息。
  18. 根据权利要求17所述的终端设备，其特征在于，所述收发单元具体用于：
    接收所述网络设备发送的非接入层NAS信令或接入层AS信令，所述NAS信令或AS信令中携带所述能力分组的信息。
  19. 根据权利要求15至18中任一项所述的终端设备，其特征在于，所述收发单元还用于：
    向所述网络设备上报附加能力的信息以及附加指示信息，所述附加指示信息用于指示所述终端设备在所述至少一个能力组的基础上增加所述附加能力或者减少所述附加能力，所述附加能力包括至少一个能力。
  20. 根据权利要求15至19中任一项所述的终端设备，其特征在于，所述收发单元还用于：
    接收所述网络设备发送的能力请求消息，所述能力请求消息用于指示所述终端设备上报所述至少一个能力组的标识。
  21. 根据权利要求15至20中任一项所述的终端设备，其特征在于，所述至少一个能力组分别包括以下能力中的至少一种：
    载波聚合中的两载波聚合能力2CC CA、载波聚合中的三载波聚合能力3CC CA、载波聚合中的四载波聚合能力4CC CA、频率范围FR 1、频率范围FR 2、增强型多媒体广播多播eMBMS能力、车联网V2X通信能力、以及波束传输能力。
  22. 一种网络设备，其特征在于，所述网络设备包括：
    收发单元，用于接收终端设备上报的所述终端设备所支持的能力所属的至少一个能力组的标识。
  23. 根据权利要求22所述的网络设备，其特征在于，所述网络设备还包括处理单元，用于：
    根据所述至少一个能力组，确定所述终端设备所支持的能力。
  24. 根据权利要求22或23所述的网络设备，其特征在于，所述收发单元还用于：
    向所述终端设备发送能力分组的信息，所述能力分组的信息包括多个能力组以及每个能力组中包括的能力。
  25. 根据权利要求24所述的网络设备，其特征在于，所述收发单元具体用于：
    向所述终端设备发送非接入层NAS信令或接入层AS信令，所述NAS信令或AS信令中携带所述能力分组的信息。
  26. 根据权利要求22至25中任一项所述的网络设备，其特征在于，所述收发单元还用于：
    接收所述终端设备上报的报附加能力的信息以及附加指示信息，所述附加指示信息用于指示所述终端设备在所述至少一个能力组的基础上增加所述附加能力或者减少所述附加能力，所述附加能力包括至少一个能力。
  27. 根据权利要求22至26中任一项所述的网络设备，其特征在于，所述收发单元还用于：
    向所述终端设备发送能力请求消息，所述能力请求消息用于指示所述终端设备上报所述至少一个能力组的标识。
  28. 根据权利要求22至27中任一项所述的网络设备，其特征在于，所述能力组包括以下能力中的至少一种：
    载波聚合中的两载波聚合能力2CC CA、载波聚合中的三载波聚合能力3CC CA、载波聚合中的四载波聚合能力4CC CA、频率范围FR 1、频率范围FR 2、增强型多媒体广播多播eMBMS能力、车联网V2X通信能力、以及波束传输能力。
  29. 一种终端设备，其特征在于，所述终端设备包括处理器和存储器，所述存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，以执行权利要求1至7中任一项所述的方法。
  30. 一种网络设备，其特征在于，所述网络设备包括处理器和存储器，所述存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，以执行权利要求8至14中任一项所述的方法。
  31. 一种芯片，其特征在于，所述芯片包括处理器，所述处理器用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行权利要求1至7中任一项所述的方法。
  32. 一种芯片，其特征在于，所述芯片包括处理器，所述处理器用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行权利要求8至14中任一项所述的方法。
  33. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，所述计算机程序使得计算机执行权利要求1至7中任一项所述的方法。
  34. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，所述计算机程序使得计算机执行权利要求8至14中任一项所述的方法。
  35. 一种计算机程序产品，其特征在于，包括计算机程序指令，所述计 算机程序指令使得计算机执行权利要求1至7中任一项所述的方法。
  36. 一种计算机程序产品，其特征在于，包括计算机程序指令，所述计算机程序指令使得计算机执行权利要求8至14中任一项所述的方法。
  37. 一种计算机程序，其特征在于，所述计算机程序使得计算机执行权利要求1至7中任一项所述的方法。
  38. 一种计算机程序，其特征在于，所述计算机程序使得计算机执行权利要求8至14中任一项所述的方法。
  39. 一种通信系统，其特征在于，包括如权利要求15至21中任意一项所述的终端设备以及如权利要求22至28中任意一项所述的网络设备。
PCT/CN2018/099688 2018-08-09 2018-08-09 能力上报的方法和设备 WO2020029191A1 (zh)

Priority Applications (8)

Application Number Priority Date Filing Date Title
AU2018436322A AU2018436322B2 (en) 2018-08-09 2018-08-09 Capability report method and device
JP2021504385A JP7385648B2 (ja) 2018-08-09 2018-08-09 能力報告の方法及びデバイス
EP18929253.5A EP3833070B1 (en) 2018-08-09 2018-08-09 Method and device for reporting capability
PCT/CN2018/099688 WO2020029191A1 (zh) 2018-08-09 2018-08-09 能力上报的方法和设备
CN201880096329.9A CN112602343A (zh) 2018-08-09 2018-08-09 能力上报的方法和设备
KR1020217004114A KR102513163B1 (ko) 2018-08-09 2018-08-09 능력 리포팅 방법 및 장치
PCT/CN2018/104863 WO2020029362A1 (zh) 2018-08-09 2018-09-10 能力上报的方法和设备
US17/167,596 US20210160686A1 (en) 2018-08-09 2021-02-04 Method and Device for Reporting Capability

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/099688 WO2020029191A1 (zh) 2018-08-09 2018-08-09 能力上报的方法和设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/167,596 Continuation US20210160686A1 (en) 2018-08-09 2021-02-04 Method and Device for Reporting Capability

Publications (1)

Publication Number Publication Date
WO2020029191A1 true WO2020029191A1 (zh) 2020-02-13

Family

ID=69413650

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2018/099688 WO2020029191A1 (zh) 2018-08-09 2018-08-09 能力上报的方法和设备
PCT/CN2018/104863 WO2020029362A1 (zh) 2018-08-09 2018-09-10 能力上报的方法和设备

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/104863 WO2020029362A1 (zh) 2018-08-09 2018-09-10 能力上报的方法和设备

Country Status (7)

Country Link
US (1) US20210160686A1 (zh)
EP (1) EP3833070B1 (zh)
JP (1) JP7385648B2 (zh)
KR (1) KR102513163B1 (zh)
CN (1) CN112602343A (zh)
AU (1) AU2018436322B2 (zh)
WO (2) WO2020029191A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114223230A (zh) * 2021-11-15 2022-03-22 北京小米移动软件有限公司 波束能力上报方法、装置、设备及存储介质

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11758388B2 (en) * 2020-04-23 2023-09-12 Qualcomm Incorporated Configurations for complexities of carriers
CN114698154A (zh) * 2020-12-31 2022-07-01 华为技术有限公司 确定终端的特性的方法和通信装置
CN115516909A (zh) * 2022-07-22 2022-12-23 北京小米移动软件有限公司 能力上报方法和装置
CN115669033A (zh) * 2022-08-31 2023-01-31 北京小米移动软件有限公司 一种终端处理能力的上报方法、数据处理方法及其装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101626363A (zh) * 2008-07-07 2010-01-13 华为技术有限公司 聚合业务装置、系统、聚合业务创建及使用方法
WO2012019550A1 (zh) * 2010-08-13 2012-02-16 电信科学技术研究院 一种载波聚合能力的处理方法和设备
CN102469611A (zh) * 2010-11-17 2012-05-23 中兴通讯股份有限公司 一种上报终端载波聚合能力的方法、系统和终端
CN105813202A (zh) * 2014-12-30 2016-07-27 中国移动通信集团公司 一种信道带宽配置方法及装置
CN107484251A (zh) * 2016-06-08 2017-12-15 中国移动通信有限公司研究院 终端能力信息的上报方法、获取方法、终端及网络侧设备

Family Cites Families (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6029065A (en) * 1997-05-05 2000-02-22 Nokia Mobile Phones, Ltd. Remote feature code programming for mobile stations
CN101146346A (zh) * 2006-09-13 2008-03-19 华为技术有限公司 设备能力信息上报方法及终端设备
KR20100017328A (ko) * 2007-05-01 2010-02-16 가부시키가이샤 엔티티 도코모 이동통신시스템에 있어서의 유저장치, 기지국장치 및 통신제어방법
CN101370164B (zh) * 2007-08-17 2012-07-18 中兴通讯股份有限公司 一种在高速分组接入信道上传输信令无线承载的方法
TWI445368B (zh) * 2010-06-25 2014-07-11 Htc Corp 適用於無線通訊能力傳訊之行動通訊裝置
US9072072B2 (en) * 2011-04-29 2015-06-30 Qualcomm Incorporated Methods and apparatuses for managing simultaneous unicast and multicast/broadcast services in a wireless communication system
US9692539B2 (en) * 2011-11-04 2017-06-27 Qualcomm Incorporated Incremental interference cancelation capability and signaling
GB2501937B (en) * 2012-05-11 2014-08-06 Broadcom Corp Capability reporting
US20130322370A1 (en) * 2012-06-01 2013-12-05 Qualcomm Incorporated Signaling reduced user equipment performance in wireless communication systems
US9253809B2 (en) * 2012-10-05 2016-02-02 Qualcomm Incorporated Apparatus and methods for improved user equipment (UE) capability signaling
EP2993937B1 (en) * 2013-05-31 2017-09-27 Huawei Technologies Co., Ltd. Communication method, base station and user equipment
US9524156B2 (en) * 2014-01-09 2016-12-20 Ford Global Technologies, Llc Flexible feature deployment strategy
US11350348B2 (en) * 2014-03-13 2022-05-31 Intel Corporation Method for the transfer of radio capability information
WO2015142278A1 (en) * 2014-03-20 2015-09-24 Telefonaktiebolaget L M Ericsson (Publ) Node and method for capability reporting
EP3120487B3 (en) * 2014-03-20 2019-09-18 Telefonaktiebolaget LM Ericsson (publ) Apparatuses and methods for carrier aggregation capability reporting
CN105099638B (zh) * 2014-05-09 2020-08-28 三星电子株式会社 在移动通信系统中收发用户设备性能信息的方法和装置
US20160242072A1 (en) * 2015-02-18 2016-08-18 Qualcomm Incorporated Handling over-sized call setup messages
US10148332B2 (en) * 2015-05-28 2018-12-04 Futurewei Technologies, Inc. System and method for multi-level beamformed non-orthogonal multiple access communications
WO2017027057A1 (en) * 2015-08-13 2017-02-16 Intel IP Corporation User equipment capability reporting
US20180227971A1 (en) * 2015-08-13 2018-08-09 Ntt Docomo, Inc. User equipment and d2d signal transmission method
GB2542770B (en) * 2015-09-25 2020-01-08 Samsung Electronics Co Ltd Mobile device capability identifier
EP3371992B1 (en) * 2015-11-02 2021-10-06 Telefonaktiebolaget LM Ericsson (PUBL) Handling device capabilities
BR112018013812A2 (zh) * 2016-01-05 2018-12-11 Huawei Technologies Co., Ltd. Mobile communication method, device and device
CN109196915B (zh) * 2016-06-30 2021-01-29 华为技术有限公司 频带处理方法及装置
CN108307489A (zh) * 2016-08-11 2018-07-20 中兴通讯股份有限公司 信息处理方法、装置、用户设备及基站
US20180084539A1 (en) * 2016-09-21 2018-03-22 Qualcomm Incorporated User equipment capability determination for multiple radio capability groups
US10568092B2 (en) * 2017-02-17 2020-02-18 Qualcomm Incorporated Scheduling and/or scheduling configuration
WO2018230983A1 (en) * 2017-06-15 2018-12-20 Lg Electronics Inc. Method for reporting ue capability and device supporting the same

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101626363A (zh) * 2008-07-07 2010-01-13 华为技术有限公司 聚合业务装置、系统、聚合业务创建及使用方法
WO2012019550A1 (zh) * 2010-08-13 2012-02-16 电信科学技术研究院 一种载波聚合能力的处理方法和设备
CN102469611A (zh) * 2010-11-17 2012-05-23 中兴通讯股份有限公司 一种上报终端载波聚合能力的方法、系统和终端
CN105813202A (zh) * 2014-12-30 2016-07-27 中国移动通信集团公司 一种信道带宽配置方法及装置
CN107484251A (zh) * 2016-06-08 2017-12-15 中国移动通信有限公司研究院 终端能力信息的上报方法、获取方法、终端及网络侧设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "On UE Capability #2 Processing Time,", 3 GPP TSG-RAN WG1 MEETING #93 R1-1807365, vol. RAN WG1, 20 May 2018 (2018-05-20), XP051442557 *
See also references of EP3833070A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114223230A (zh) * 2021-11-15 2022-03-22 北京小米移动软件有限公司 波束能力上报方法、装置、设备及存储介质

Also Published As

Publication number Publication date
US20210160686A1 (en) 2021-05-27
AU2018436322A1 (en) 2021-02-18
KR102513163B1 (ko) 2023-03-23
EP3833070B1 (en) 2024-05-01
JP2022501857A (ja) 2022-01-06
EP3833070A1 (en) 2021-06-09
WO2020029362A1 (zh) 2020-02-13
EP3833070A4 (en) 2021-08-25
JP7385648B2 (ja) 2023-11-22
KR20210042914A (ko) 2021-04-20
AU2018436322B2 (en) 2024-05-16
CN112602343A (zh) 2021-04-02

Similar Documents

Publication Publication Date Title
WO2020029191A1 (zh) 能力上报的方法和设备
WO2021163938A1 (zh) 天线切换方法、终端设备和通信设备
WO2020087524A1 (zh) 非授权频段上ssb的传输方法和设备
US11252557B2 (en) Capability identifier distribution method and device
US20220070661A1 (en) Method for determining terminal capability message format, network device and server
US20220394461A1 (en) Sidelink capability sending method and terminal device
WO2020051892A1 (zh) 无线通信的方法、终端设备和网络设备
US20220124521A1 (en) Method and device for information transmission
WO2020097928A1 (zh) 网络接入方法和设备
WO2022160123A1 (zh) 接入方式选择方法、终端设备和网络设备
KR20210008358A (ko) 다운링크 채널의 수신 방법 및 단말기
WO2020258051A1 (zh) 小区接入的方法和设备
WO2019210517A1 (zh) 无线通信方法、通信设备、芯片和系统
WO2021237623A1 (zh) 切片选择的方法和终端设备
WO2020019182A1 (zh) 一种信号传输方法及装置、终端设备、网络设备
WO2020147040A1 (zh) 数据复制传输配置方法、装置、芯片及计算机程序
KR20220120449A (ko) 무선 통신 방법 및 단말 장치
WO2020087541A1 (zh) 下行控制信息的传输方法和设备
WO2020051767A1 (zh) 传输信息、接收信息的方法和通信设备
WO2020087546A1 (zh) 一种网络信息传输方法、获取方法、网络设备及终端设备
WO2022183317A1 (zh) 一种获取切片信息的方法和终端设备
US20230388879A1 (en) Wireless communication method, terminal device, and storage medium
WO2022147681A1 (zh) 辅助路由方法、终端设备和网络设备
WO2022213779A1 (zh) 参数配置方法、终端设备和网络设备
WO2022151427A1 (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: 18929253

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021504385

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018436322

Country of ref document: AU

Date of ref document: 20180809

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018929253

Country of ref document: EP

Effective date: 20210305