WO2020063521A1 - Procédé et appareil de signalement de capacité - Google Patents

Procédé et appareil de signalement de capacité Download PDF

Info

Publication number
WO2020063521A1
WO2020063521A1 PCT/CN2019/107245 CN2019107245W WO2020063521A1 WO 2020063521 A1 WO2020063521 A1 WO 2020063521A1 CN 2019107245 W CN2019107245 W CN 2019107245W WO 2020063521 A1 WO2020063521 A1 WO 2020063521A1
Authority
WO
WIPO (PCT)
Prior art keywords
information unit
identifier
capability
frequency band
parameter
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2019/107245
Other languages
English (en)
Chinese (zh)
Inventor
邝奕如
王丁
王键
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2020063521A1 publication Critical patent/WO2020063521A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/02—Resource partitioning among network components, e.g. reuse partitioning
    • 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

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a method and device for reporting capabilities.
  • Capability parameters include, for example, Packet Data Convergence Protocol (PDCP) parameters, physical layer parameters, radio frequency parameters, and measurement parameters.
  • PDCP Packet Data Convergence Protocol
  • the terminal can support multiple levels of capability parameters.
  • the following capability ie, the terminal's capability in the downlink direction
  • the terminal is in one of a frequency band of a frequency band combination.
  • This capability parameter includes a capability parameter at a frequency band level and a capability parameter at a carrier level.
  • the identity of the information element (FeatureSetDownlinkPerCC, FeatureSetDownlinkPerCC) corresponding to the capability parameter at the frequency band level and the carrier level capability parameter is included in the FeatureSetDownlinkPerCCIE, so that it can be indexed to The capability parameter of the corresponding carrier level.
  • FeatureSetDownlinkPerCC FeatureSetDownlinkPerCC
  • the embodiments of the present application provide a method and a device for reporting a capability, so as to reduce signaling overhead in the capability reporting process.
  • an embodiment of the present application provides a capability reporting method, which is applied to a terminal device or a chip of a terminal device.
  • the method includes: the terminal device sends a capability message to a network device, and the capability message includes a first information unit and a first Two information units, and an association relationship between the first information unit and a second information unit.
  • the first information unit includes a capability parameter at a frequency band level
  • the second information unit includes a capability parameter at a carrier level. It can be seen that when the terminal reports the capability parameter, it is not necessary to report the capability parameter of each carrier level (such as multiple capability parameters indicated by dashed box 501 in FIG.
  • the terminal may report only one type of band-level capability parameter at a time, and reduce the capability of the band-level by reporting the identifier of the band-level capability parameter associated with the carrier-level capability parameter. Probability of repeated reporting of parameters, thereby reducing signaling overhead when the terminal is reporting capabilities.
  • an embodiment of the present application provides a terminal.
  • the terminal includes a transceiver and a processor.
  • a processor for determining whether the terminal is in a connected state, and if so, controlling the transceiver to send a capability message to the network device; if not, establishing a connection with the network device, and then using the established RRC connection to send the capability to the network device Message.
  • a transceiver for sending a capability message to a network device includes a first information unit and a second information unit, and an association relationship between the first information unit and the second information unit, and the first information unit includes a capability parameter at a frequency band level,
  • the second information element contains a carrier level capability parameter.
  • an embodiment of the present application provides a capability reporting method, which is applied to a terminal or a chip of a terminal.
  • the method includes:
  • the terminal device establishes a connection with the network device, or the terminal device communicates with the network device.
  • the terminal device sends a capability message to the network device.
  • a terminal device in an idle state performs a Radio Resource Control (RRC) connection and establishes an RRC connection with a network device.
  • RRC Radio Resource Control
  • the connected terminal device can use the existing RRC connection to send a capability message to the network device.
  • the capability message includes a first information unit and a second information unit, and an association relationship between the first information unit and the second information unit.
  • the first information unit includes a capability parameter at a frequency band level
  • the second information unit includes a capability parameter at a carrier level. .
  • the first information unit does not include a second identifier
  • the second identifier is an identifier corresponding to the second information unit. That is, the first information unit is decoupled from the second identifier.
  • the capability message further includes a third information unit.
  • the capability parameter is a downlink capability parameter
  • the first information unit may be a FeatureSetDownlinkIE
  • the second information unit may be an information unit corresponding to the carrier-level capability parameter (FeatureSetDownlinkPerCCIE)
  • the third information unit (FeatureSetIE) corresponds to one of the terminals.
  • the association relationship between the first information unit and the second information unit is an association relationship between the first identifier and at least one second identifier
  • the first identifier is an identifier corresponding to the first information unit
  • the second identifier is a second information unit. The corresponding ID.
  • the third information unit includes an association relationship between the first identifier and at least one second identifier.
  • the capability message further includes a third information unit and a fourth information unit.
  • the capability parameter is a downlink capability parameter
  • the first information unit is a newly defined information unit, which is referred to as FeatureSetDownlinkParaIE
  • the second information unit is FeatureSetDownlinkPerCCIE
  • the third information unit is FeatureSetIE
  • the fourth information unit is FeatureSetDownlinkIE.
  • the fourth information unit includes at least one second identifier, and the second identifier is an identifier corresponding to the second information unit.
  • the association relationship between the first information unit and the second information unit is the association relationship between the first identifier and the fourth identifier
  • the first identifier is an identifier corresponding to the first information unit
  • the fourth identifier is an identifier corresponding to the fourth information unit.
  • the third information unit includes an association relationship between the first identifier and the fourth identifier.
  • the capability message includes a first information unit, a second information unit, a third information unit, and a fourth information unit.
  • the first information unit is FeatureSetDownlinkParaieIE
  • the second information unit is FeatureSetDownlinkPerCCIE
  • the third information unit is FeatureSetIE
  • the fourth information unit is LinkSetElement (FeatureSetDownlinkIE).
  • the association relationship between the first information unit and the second information unit is an association relationship between the first identifier and at least one second identifier.
  • the association between the first identifier and the at least one second identifier is included in a fourth information unit.
  • the third information unit contains a fourth identifier.
  • an embodiment of the present application provides a capability reporting method, which is applied to a terminal or a chip of a terminal.
  • the method includes:
  • the terminal device establishes a connection with the network device, or the terminal device communicates with the network device. For example, a terminal device in an idle state performs a Radio Resource Control (RRC) connection and establishes an RRC connection with a network device.
  • RRC Radio Resource Control
  • the connected terminal device can use the existing RRC connection to send a capability message to the network device.
  • the terminal device sends a capability message to the network device.
  • the capability message includes a first information unit and a second information unit, and an association relationship between the first information unit and the second information unit.
  • the first information unit includes a frequency band.
  • Level capability parameter the second information element contains a carrier level capability parameter.
  • the first information unit further includes a carrier level parameter set
  • the carrier level parameter set includes at least two second identifiers
  • the second identifier is an identifier corresponding to the second information unit.
  • the capability message further includes a third information unit corresponding to a capability parameter of a frequency band in a frequency band combination of the terminal.
  • the third information unit includes a first identifier, and the first identifier is the first information.
  • the association relationship between the first information unit and the second information unit is an association relationship between a band-level capability parameter and a second identifier.
  • the FeatureSet IE includes a first identifier, and the first identifier is an identifier corresponding to the first information unit (ie, FeatureSetDownlinkId).
  • FeatureSetDownlink IE includes a downlink capability parameter and a carrier level parameter set at a frequency band level.
  • the carrier level parameter set includes at least two second identifiers, and the second identifier is an identifier corresponding to the second information unit (ie, FeatureSetDownlinkPerCCId).
  • the association between the first information unit and the second information unit is carried in the first information unit through the second identifier.
  • FeatureSetDownlinkPerCC contains capability parameters at the carrier level.
  • an embodiment of the present application provides a communication method, and the method is applied to a network device or a chip of a network device.
  • the method includes:
  • the network device receives a capability message sent by the terminal device.
  • the capability message includes a first information unit and a second information unit, and an association relationship between the first information unit and a second information unit.
  • the first information unit includes a capability parameter at a frequency band level.
  • the information element contains the capability parameters at the carrier level.
  • the first information unit does not include a second identifier
  • the second identifier is an identifier corresponding to the second information unit. That is, the first information unit is decoupled from the second identifier.
  • the capability message further includes a third information unit.
  • the capability parameter is a downlink capability parameter
  • the first information unit may be a FeatureSetDownlinkIE
  • the second information unit may be an information unit corresponding to the carrier-level capability parameter (FeatureSetDownlinkPerCCIE)
  • the third information unit (FeatureSetIE) corresponds to one of the terminals.
  • the association relationship between the first information unit and the second information unit is an association relationship between the first identifier and at least one second identifier
  • the first identifier is an identifier corresponding to the first information unit
  • the second identifier is a second information unit. The corresponding ID.
  • the third information unit includes an association relationship between the first identifier and at least one second identifier.
  • the capability message further includes a third information unit and a fourth information unit.
  • the capability parameter is a downlink capability parameter
  • the first information unit is a newly defined information unit, which is referred to as FeatureSetDownlinkParaIE
  • the second information unit is FeatureSetDownlinkPerCCIE
  • the third information unit is FeatureSetIE
  • the fourth information unit is FeatureSetDownlinkIE.
  • the fourth information unit includes at least one second identifier, and the second identifier is an identifier corresponding to the second information unit.
  • the association relationship between the first information unit and the second information unit is the association relationship between the first identifier and the fourth identifier
  • the first identifier is an identifier corresponding to the first information unit
  • the fourth identifier is an identifier corresponding to the fourth information unit.
  • the third information unit includes an association relationship between the first identifier and the fourth identifier.
  • the association relationship between the first information unit and the second information unit is an association relationship between the first identifier and at least one second identifier.
  • the association between the first identifier and the at least one second identifier is included in a fourth information unit.
  • the third information unit contains a fourth identifier.
  • an embodiment of the present application provides a capability reporting method, which is applied to a network device or a chip of a network device.
  • the method includes:
  • the network device receives a capability message sent by the terminal device.
  • the capability message includes a first information unit and a second information unit, and an association relationship between the first information unit and the second information unit.
  • the first information unit includes Band-level capability parameters
  • the second information element contains a carrier-level capability parameter.
  • the first information unit further includes a carrier level parameter set
  • the carrier level parameter set includes at least two second identifiers
  • the second identifier is an identifier corresponding to the second information unit.
  • the capability message further includes a third information unit corresponding to a capability parameter of a frequency band in a frequency band combination of the terminal.
  • the third information unit includes a first identifier, and the first identifier is the first information.
  • the association relationship between the first information unit and the second information unit is an association relationship between a band-level capability parameter and a second identifier.
  • the capability message includes a first information unit (FeatureSetDownlinkIE), a second information unit (FeatureSetDownlinkPerCCIE), and a third information unit (FeatureSetIE).
  • FeatureSetDownlinkIE a first information unit
  • FeatureSetDownlinkPerCCIE a second information unit
  • FeatureSetIE a third information unit
  • the FeatureSet IE includes a first identifier, and the first identifier is an identifier corresponding to the first information unit (ie, FeatureSetDownlinkId).
  • FeatureSetDownlink IE includes a downlink capability parameter and a carrier level parameter set at a frequency band level.
  • the carrier level parameter set includes at least two second identifiers, and the second identifier is an identifier corresponding to the second information unit (ie, FeatureSetDownlinkPerCCId).
  • the association between the first information unit and the second information unit is carried in the first information unit through the second identifier.
  • FeatureSetDownlinkPerCC contains capability parameters at the carrier level.
  • a capability parameter of a frequency band in a frequency band combination of a terminal device includes a capability parameter in a first information unit and a capability parameter in a second information unit.
  • an embodiment of the present application provides a terminal having a function of implementing the capability reporting method of any one of the first aspect, the second aspect, or the third aspect or the fourth aspect.
  • This function can be realized by hardware, and can also be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • a terminal including: a processor and a memory; the memory is configured to store a computer execution instruction, and when the terminal is running, the processor executes the computer execution instruction stored in the memory, so that the terminal executes a program such as The capability reporting method of any one of the first aspect, the second aspect, or the third aspect described above.
  • an embodiment of the present application provides a network device, and the terminal has a function of implementing the capability reporting method in any one of the fifth aspect or the sixth aspect.
  • This function can be realized by hardware, and can also be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions.
  • a network device including: a processor and a memory; the memory is configured to store computer execution instructions, and when the network device is running, the processor executes the computer execution instructions stored in the memory to enable the network
  • the device performs the capability reporting method according to any one of the fifth aspect or the sixth aspect.
  • a computer-readable storage medium stores instructions that, when run on a computer, enable the computer to execute the capability reporting method of any one of the above aspects.
  • a computer program product containing instructions which, when run on a computer, enables the computer to execute the capability reporting method of any of the above aspects.
  • a circuit system includes a processing circuit configured to execute the capability reporting method according to any one of the above aspects.
  • a chip includes a processor, the processor is coupled to a memory, and the memory stores program instructions.
  • the program instructions stored in the memory are executed by the processor, the method for reporting a capability of any one of the foregoing aspects is implemented. .
  • the technical effects brought by any one of the design methods in the second aspect to the fourteenth aspect may refer to the technical effects brought by the different design methods in the first aspect, and will not be repeated here.
  • FIG. 1 is a first structural diagram of a capability message in the prior art
  • FIG. 2 is a second structural diagram of a capability message in the prior art
  • FIG. 3 is a schematic structural diagram of a communication system according to an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a terminal according to an embodiment of the present application.
  • FIG. 5 is a flowchart of a capability reporting method according to an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a capability message according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a capability message according to an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a capability message according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a capability message according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a capability message according to an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a capability message according to an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a capability message according to an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a capability message according to an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of a capability message according to an embodiment of the present application.
  • 15 is a schematic structural diagram of a capability message according to an embodiment of the present application.
  • FIG. 16 is a schematic structural diagram of a terminal according to an embodiment of the present application.
  • a terminal may use a carrier aggregation (CA) technology or a dual carrier (DC) technology to combine two or more carriers, and then communicate through a combined frequency band to improve the terminal's service capabilities.
  • CA carrier aggregation
  • DC dual carrier
  • a terminal sends a capability message to a network device, and the capability message carries a capability parameter of the terminal.
  • the structure of the capability message may be as shown in FIG. 1, and the capability message carries multiple IEs.
  • the content in the solid line boxes 1 to 5 in FIG. 1 is an IE, and each IE corresponds to an identifier.
  • the terminal may index one or more capability parameters of the terminal on a frequency band of a combination of frequency bands through different levels of IE.
  • FeatureSetCombinationIE is a band combination level information unit, and FeatureSetCombinationIE contains one or more bandlevel information units (FeatureSetsPerBandIE) in the band combination.
  • FeatureSetsPerBandIE bandlevel information units
  • FeatureSetsPerBand IE which contains information elements (FeatureSet IE) corresponding to one or more capability parameters of a frequency band in a frequency band combination.
  • FeatureSetIE a capability parameter corresponding to a frequency band in a frequency band combination.
  • FeatureSetIE includes an identification of a downlink capability parameter (FeatureSetDownlinkIE) of a capability parameter of a frequency band in a frequency band combination.
  • the identifier of FeatureSetDownlinkIE can be recorded as FeatureSetDownlinkId, and FeatureSetDownlinkId is used to index to the corresponding FeatureSetDownlinkIE .
  • FeatureSetIE also includes an identifier of an uplink parameter (FeatureSetUplinkIE) of a capability parameter of a frequency band combination.
  • FeatureSetUplinkIE can be recorded as FeatureSetUplinkId, and FeatureSetUplinkId is used to index to the corresponding FeatureSetUplinkIE.
  • the above-mentioned downlink capability parameter part (FeatureSetDownlink) and the above-mentioned uplink capability parameter (FeatureSetUplink) part constitute a kind of capability parameter of a frequency band in a complete frequency band combination.
  • FeatureSetDownlink IE which includes the identification of the information element (FeatureSetDownlinkPerCC) corresponding to the frequency-level capability parameter and the carrier-level capability parameter.
  • the identifier of FeatureSetDownlinkPerCC and IE can be recorded as FeatureSetDownlinkPerCCId, which is used to index the capability parameter to the carrier level.
  • FeatureSetUplinkIE which includes the identification of the information element (FeatureSetUplinkPerCC) of the frequency-level capability parameter and the carrier-level capability parameter.
  • the identifier of FeatureSetUplinkPerCC IE can be recorded as FeatureSetUplinkPerCCId, which is used to index the capability parameter to the carrier level.
  • FeatureSetDownlinkPerCC ie, contains downlink capability parameters at the carrier level.
  • FeatureSetUplinkPerCC ie, contains uplink capability parameters at the carrier level.
  • the frequency-level capability parameters included in FeatureSetDownlink (such as multiple capability parameters in dashed box 401 in Figure 1) can be indexed with the carrier-level capability parameters indexed by FeatureSetDownlinkPerCCId included in FeatureSetDownlink
  • a plurality of capability parameters in a dashed box 501) constitutes a type of downlink capability parameter on a frequency band in a frequency band combination of a terminal.
  • FeatureSetIE contains FeatureSetDownlinkId and FeatureSetUplinkId.
  • the IE corresponding to FeatureSetDownlinkId contains the capability parameters at the frequency band level (corresponding to multiple capability parameters in the dashed box 401 in Figure 1) and FeatureSetDownlinkPerCCId.
  • the five capability parameters in dashed box 501 in 1 correspond to 5); similarly, the IE corresponding to FeatureSetUplinkId includes the capability parameter at the frequency band level and FeatureSetUplinkPerCCId, and the capability parameter at the carrier level included in the IE corresponding to FeatureSetUplinkPerCCId.
  • the communication system includes an access network device (only one is shown as an example in the figure), a plurality of terminal devices (such as terminal 1 to terminal 6 in FIG. 3) that communicate with the access network device, Core network equipment (only one is shown as an example in the figure) for communication with the access network equipment.
  • an access network device only one is shown as an example in the figure
  • a plurality of terminal devices such as terminal 1 to terminal 6 in FIG. 3
  • Core network equipment only one is shown as an example in the figure
  • the communication system shown in FIG. 3 can be applied to a current Long Term Evolution (LTE) or an advanced Long Term Evolution (LTE-A) system, and can also be applied to a 5G network currently being developed or a future In other networks, of course, it can also be applied to a system of LTE and 5G mixed networking, which is not specifically limited in the embodiment of the present application.
  • LTE Long Term Evolution
  • LTE-A advanced Long Term Evolution
  • 5G network currently being developed or a future
  • LTE and 5G mixed networking which is not specifically limited in the embodiment of the present application.
  • the core network equipment, access network equipment, and terminal equipment in the communication system may correspond to different names. Those skilled in the art can understand that the name does not constitute a limitation on the equipment itself.
  • the core network device referred to in the embodiments of the present application is a device deployed in the core network to provide services to terminals.
  • the names of core network devices with similar wireless communication functions may be different.
  • the core network device may be an access and mobility management function (AMF, Access and Mobility Management Function).
  • AMF Access and Mobility Management Function
  • MME Mobility Management Entity
  • the core network equipment For the convenience of description only, in the embodiments of the present application, the foregoing devices that can provide services to terminals are collectively referred to as core network equipment.
  • An access network device is a device that is deployed in a wireless access network to provide wireless communication functions.
  • the access network equipment involved in the embodiments of the present application may include, for example, but not limited to, various types of macro base stations, micro base stations (also referred to as small stations), relay stations, transmission and reception points (TRP), and the next generation.
  • Network nodes gNodeB, gNB
  • evolved NodeB ng-eNB
  • WLAN wireless local area network
  • Terminal equipment is mainly used to receive or send data.
  • the terminals involved in the embodiments of the present application may include, for example, but not limited to, various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem; also Can include subscriber unit, cellular phone, smart phone, wireless data card, personal digital assistant (PDA) computer, tablet computer, handheld device, knee A laptop computer, a machine type communication (MTC) terminal, a user equipment (UE), and the like.
  • PDA personal digital assistant
  • MTC machine type communication
  • UE user equipment
  • the terminal device may also be referred to as a terminal, which will be collectively described herein and will not be described in detail hereinafter.
  • the terminal device, access network device, and core network device in FIG. 3 may be implemented by multiple devices, respectively, or the access network device and core network device may also be implemented by one device, for example, may be implemented in one device.
  • Different functional modules which are not specifically limited in the embodiments of the present application. It can be understood that the foregoing function module may be a network element in a hardware device, a software function running on a hardware device, or a virtualization function instantiated on a platform (for example, a cloud platform).
  • FIG. 4 is a schematic diagram of a hardware structure of a communication device according to an embodiment of the present application.
  • the communication device 400 includes at least one processor 401, a communication line 402, a memory 403, and at least one communication interface 404.
  • the processor 401 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more processors for controlling the execution of the program of the solution of the present application. integrated circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication line 402 may include a path for transmitting information between the aforementioned components.
  • the communication interface 404 uses any device such as a transceiver to communicate 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 403 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types that can store information and instructions
  • the dynamic storage device can also be electrically erasable programmable read-only memory (EEPROM-ready-only memory (EEPROM)), compact disc (read-only memory (CD-ROM)) or other optical disk storage, optical disk storage (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 used by a computer Any other media accessed, but not limited to this.
  • the memory may exist independently, and is connected to the processor through the communication line 402. The memory can also be integrated with the processor.
  • the memory 403 is configured to store computer execution instructions for executing the solutions in the embodiments of the present application, and the execution is controlled by the processor 401.
  • the processor 401 is configured to execute computer execution instructions stored in the memory 403, so as to implement the capability reporting method provided in the following embodiments of the present application.
  • the computer-executable instructions in the embodiments of the present application may also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.
  • the processor 401 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 4.
  • the communication device 400 may include multiple processors, such as the processor 401 and the processor 405. Each of these processors may be a single-CPU processor or a multi-CPU processor.
  • a processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).
  • the above-mentioned communication device 400 may be a general-purpose device or a special-purpose device.
  • the communication device 400 may be a device having a similar structure as in FIG. 4.
  • the embodiment of the present application does not limit the type of the communication device 400.
  • a network device needs to make some network decisions based on the capabilities of the terminal. For example, the network device can deliver the resource configuration corresponding to the terminal to the terminal according to the terminal capability, so that the terminal uses the configured available resources for communication.
  • the network device may send a capability request message to the terminal, and receive the capability message fed back by the terminal, so as to execute a network decision according to the capability message.
  • boxes 1 to 9 each represent an IE.
  • FeatureSetDownlinkPerCCId is included in FeatureSetDownlinkIE, generally, every time a FeatureSetDownlinkPerCC is reported, it is reported at least A FeatureSetDownlink IE.
  • multiple FeatureSetDownlink IEs also include band-level capability parameters. When the parameters in FeatureSetDownlinkPerCC are changed, FeatureSetDownlinkPeriod's band-level capability parameters may not change.
  • FeatureSetDownlinkPerCC As long as FeatureSetDownlinkPerCC is changed, it is necessary to report FeatureSetDownlinkIE, and the reported FeatureSetDownlinkIE may cause the same band-level capability parameters. , Resulting in repeated reporting of capability parameters at this frequency band level, increasing the signaling overhead when the terminal reports capabilities.
  • an embodiment of the present application provides a capability reporting method.
  • the capability reporting method provided by the embodiment of the present application will be specifically described below with reference to FIGS. 5 to 13.
  • the capability reporting method in the embodiment of the present application is applied to a process in which a terminal reports a capability to a network device.
  • the method includes the following steps:
  • the network device sends a capability request message (UECapabilityEnquiry) to the terminal device.
  • UECapabilityEnquiry a capability request message
  • the terminal device receives the capability request message sent by the network device.
  • the network device may be an access network device shown in FIG. 3.
  • the capability request message is used to request the capability of the terminal in one or more radio access technologies (Radio Access Technology, RAT).
  • RAT includes but is not limited to: New Radio (NR) technology, Evolved-Universal Mobile Telecommunications System, Terrrestrial Radio Access, E-UTRA technology, and Evolved Universal Mobile Communication System terrestrial Wireless access and new wireless (Evolved-Universal Mobile Telecommunications System Terrestrial Radio Access New Radio, E-UTRA-NR) dual connection technology, universal mobile communication system terrestrial wireless access (Universal Mobile Telecommunications System Terrestrial Radio Access, UTRA) technology, Enhanced data rate global mobile communication system evolution wireless access network (Enhanced Data Rate Global System, Mobile Communication, Evolution Radio Access Network, GERAN) technology and code division multiple access 2000 technology (CDMA2000-1XRTT).
  • NR New Radio
  • Evolved-Universal Mobile Telecommunications System Terrrestrial Radio Access
  • E-UTRA-NR Evolved Universal Mobile Communication System terrestrial Wireless access and new wireless
  • Universal Mobile communication system terrestrial wireless access Universal Mobile communication system
  • the network when the network needs to know the terminal capabilities, it can initiate a capability request message to a connected terminal to request the required terminal capabilities.
  • the network device receives the capability message sent by the terminal device.
  • the capability message includes at least one first information unit and at least one second information unit, and an association relationship between the first information unit and the second information unit.
  • the first information unit includes a capability parameter at a frequency band level.
  • the second information element contains a carrier level capability parameter.
  • a capability parameter of a frequency band in a frequency band combination of a terminal device includes a capability parameter in a first information unit and a capability parameter in a second information unit.
  • the capability message structure may be different according to the types of the first information unit and the second information unit. The following is a detailed description of each message structure in four cases.
  • the capability message includes a first information unit, a second information unit, and a third information unit.
  • the first information unit may be FeatureSetDownlinkIE
  • the second information unit may be FeatureSetDownlinkPerCCIE.
  • the FeatureSetDownlinkPerCCId and the FeatureSetDownlinkIE are decoupled, that is, the FeatureSetDownlinkIE is deleted from the FeatureSetDownlinkPerCCId, so that the FeatureSetDownlinkIE only includes the downlink capability parameter at the frequency band level and does not include the FeatureSetDownlinkPerCCId.
  • FeatureSetDownlinkPerCC includes downlink capability parameters at the carrier level.
  • the third information unit corresponds to a type of downlink capability parameter of a frequency band in a frequency band combination of the terminal, that is, a FeatureSetIE.
  • FeatureSetIE includes an association relationship between a first identifier and at least one second identifier.
  • the first identifier is an identifier corresponding to FeatureSetDownlink, ie, it may be a FeatureSetDownlinkId
  • the second identifier is an identifier corresponding to FeatureSetDownlinkPerCC, which may be a FeatureSetDownlinkPerCCId.
  • the association relationship between FeatureSetDownlinkIE and FeatureSetDownlinkPerCC may be the association relationship between FeatureSetDownlinkId and FeatureSetDownlinkPerCCI, that is, the association relationship between the first identifier and at least one second identifier is used to indicate the association relationship between FeatureSetDownlinkIE and at least one FeatureSetDownlinkPerCCIE.
  • the following row capability parameters are taken as an example for description.
  • the specific form of the uplink capability parameters refer to the related description of the downlink capability parameters.
  • the form of the uplink capability parameter in the capability message is specifically:
  • the first information unit may be FeatureSetUplinkIE
  • the second information unit may be FeatureSetUplinkPerCCIE.
  • the FeatureSetUplinkPerCCId and the FeatureSetUplinkIE are decoupled, that is, the FeatureSetUplinkPerCCId in the FeatureSetUplinkIE is deleted, so that the FeatureSetUplinkIE only includes the uplink capability parameter at the frequency level and does not include the FeatureSetUplinkPerCCId.
  • FeatureSetUplinkPerCC contains uplink capability parameters at the carrier level.
  • the third information unit corresponds to an uplink capability parameter of a frequency band in a frequency band combination of the terminal, that is, it may be a FeatureSetIE.
  • FeatureSetIE includes an association relationship between a first identifier and at least one second identifier.
  • the first identifier is an identifier corresponding to FeatureSetUplink, ie, it may be a FeatureSetUplinkId
  • the second identifier is an identifier corresponding to FeatureSetUplinkPerCC, which may be a FeatureSetUplinkPerCCId.
  • the association relationship between FeatureSetUplinkIE and FeatureSetUplinkPerCC may be the association relationship between FeatureSetUplinkId and FeatureSetUplinkPerCCI, that is, the association relationship between the first identifier and at least one second identifier is used to indicate the association relationship between FeatureSetUplinkIE and at least one FeatureSetUplinkPerCCIE.
  • FIG. 6 shows a capability message reported by a terminal according to an embodiment of the present application.
  • the capability message includes two FeatureSet IEs, and the capability message also includes two FeatureSetDownlink IEs, which characterize the terminal. Supports two types of downlink capability parameters at the frequency band level.
  • the capability message also includes three FeatureSetDownlinkPerCCIEs, indicating that the terminal supports three types of carrier level downlink capability parameters.
  • FeatureSet IE1 includes the association relationship between FeatureSetDownlinkId1 and FeatureSetDownlinkPerCCId1, FeatureSetDownlinkPerCCId2, FeatureSetDownlinkPerCCId3, which means that a downlink capability parameter of a frequency band in a frequency band combination of the terminal includes the downlink capability parameter of the frequency band included in IE corresponding to FeatureSetDownlinkId1
  • the downlink capability parameter of the carrier level included in the IE corresponding to FeatureSetDownlinkPerCCId1 includes the downlink capability parameter of the frequency band included in the IE corresponding to FeatureSetDownlinkId1 and the IE corresponding to FeatureSetDownlinkPerCCId2.
  • a type of downlink capability parameter for one frequency band in another frequency band combination of the terminal includes downlink-level capability parameters of the frequency band contained in the IE corresponding to FeatureSetDownlinkId1 and carrier-level downlink capability parameters of the IE corresponding to FeatureSetDownlinkPerCCId3 .
  • the IE corresponding to FeatureSet IE2 includes the relationship between FeatureSetDownlinkId2 and FeatureSetDownlinkPerCCId1, FeatureSetDownlinkPerCCId2, FeatureSetDownlinkPerCCId3, and is used to characterize the terminal's three other downlink capability parameters.
  • each IE in FIG. 7 (such as the IEs indicated by the solid-line boxes 1 to 5) and the capability parameters included in each IE can refer to the description in FIG. 6, and will not be repeated here.
  • the horizontal line in the FeatureSetDownlinkIE indicates that the FeatureSetDownlinkIE is decoupled from the FeatureSetDownlinkPerCCId, that is, the FeatureSetDownlinkPerCCId is deleted in the FeatureSetDownlinkIE.
  • FIG. 6 exemplarily shows carrier-level downlink capability parameters 1, carrier-level downlink capability parameters 2, carrier-level downlink capability parameters 3, and FIG.
  • FIG. 7 does not show downlink capability parameters of all three carrier levels. Only the carrier level downlink capability parameter 1 included in the IE corresponding to FeatureSetDownlinkPerCCId1 is shown (see multiple capability parameters shown by dashed box 501 in FIG. 7 and other carrier level capability parameters not shown), and the downlink capability Parameter 1 is only a part of the downlink capability parameters at the carrier level. Similarly, FIG. 6 exemplarily shows the downlink capability parameter 1 at the frequency band level and the downlink capability parameter 2 at the frequency band level, and FIG. 7 only shows the downlink capability parameter 1 at the frequency level included in the IE corresponding to FeatureSetDownlinkId1 (including the figure) A plurality of capability parameters shown by a dashed box 401 in FIG.
  • FIG. 6 shows the IE corresponding to FeatureSet IE1 and FeatureSet IE2
  • FIG. 7 shows only FeatureSet IE1.
  • the number of IEs included in the capability message may have other conditions, which is not limited in the embodiment of the present application.
  • a new information unit is defined to indicate a capability parameter of a frequency band level.
  • the capability message includes a first information unit (ie, a new information unit, for example, as FeatureSetDownlinkParaIE), a second information unit (FeatureSetDownlinkPerCCIE), a third information unit (FeatureSetIE), and a first information unit.
  • FeatureSetDownlink IE Four information units (FeatureSetDownlink IE).
  • the newly defined information unit is an exemplary information unit. In practical applications, the specific name and form of the new information unit may be set separately, which is not limited in the embodiment of the present application. The new information elements appearing below are similar.
  • the FeatureSet IE includes an association relationship between the first identifier and the fourth identifier.
  • the first identifier is the identifier of FeatureSetDownlinkPara, ie, it is recorded as FeatureSetDownlinkParaId
  • the fourth identifier is the identifier of FeatureSetDownlink, ie, FeatureSetDownlinkId.
  • the relationship between FeatureSetDownlinkPara IE and FeatureSetDownlink IE may be the relationship between FeatureSetDownlinkParaId and FeatureSetDownlinkId, that is, the relationship between the first identifier and the fourth identifier may indicate the relationship between FeatureSetDownlinkParaIE and FeatureSetDownlinkIE.
  • FeatureSetDownlinkPara IE includes downlink capability parameters at the frequency band level and does not include the second identifier.
  • the second identifier is the identifier of FeatureSetDownlinkPerCC, ie, it can be FeatureSetDownlinkPerCCId.
  • FIG. 8 shows an exemplary structure of a capability message when the FeatureSetDownlink IE contains a FeatureSetDownlinkPerCCId.
  • FIG. 9 illustrates an exemplary structure of a capability message when the FeatureSetDownlinkIE contains 3 FeatureSetDownlinkPerCCIds.
  • the number of FeatureSetDownlinkPerCCIds specifically included in the FeatureSetDownlink IE can be flexibly set according to the application scenario, and this embodiment of the present application does not limit this.
  • FeatureSetDownlinkPerCC IE contains downlink capability parameters at the carrier level.
  • the capability message includes the IEs shown in blocks 1 to 14, and the downlink capability parameters of the terminal on a frequency band of a frequency band combination include the following:
  • the first type of downlink capability parameters includes: FeatureSetDownlinkParaId1 and FeatureSetDownlinkId1 contained in FeatureSet1 are indexed to the corresponding IE, the downlink capability parameter 1 of the frequency band contained in the IE corresponding to FeatureSetDownlinkParaId1 and the downlink capability parameter 1 at the carrier level indexed by FeatureSetDownlinkId1
  • the first type of downlink capability parameter includes: FeatureSetDownlinkParaId1 and FeatureSetDownlinkId1 contained in FeatureSet1 are indexed to the corresponding IE, the downlink capability parameter 1 of the frequency band contained in the IE corresponding to FeatureSetDownlinkParaId1 and the downlink capability parameter 1 at the carrier level indexed by FeatureSetDownlinkId1
  • the first type of downlink capability parameter includes: FeatureSetDownlinkParaId1 and FeatureSetDownlinkId1 contained in FeatureSet1 are indexed to the corresponding IE, the downlink capability parameter
  • the second type of downlink capability parameter includes: FeatureSetDownlinkParaId1 and FeatureSetDownlinkId2 included in the IE corresponding to FeatureSet2 are indexed to the corresponding IE, and the IE corresponding to FeatureSetDownlinkParaId1 contains the frequency-level capability parameter 1 and the carrier-level capability parameter 2 indexed by FeatureSetDownlinkId2 Forms the second type of downlink capability parameter.
  • the third type of downlink capability parameters includes: FeatureSetDownlinkParaId1 and FeatureSetDownlinkId3 contained in the IE corresponding to FeatureSet3 are indexed to the corresponding IE, and the IE corresponding to FeatureSetDownlinkParaId1 contains the frequency-level capability parameter 1 contained in the IE corresponding to FeatureSet3 and the carrier-level capability parameter 3 indexed by FeatureSetDownlinkId3.
  • the fifth type of downlink capability parameters includes: FeatureSetDownlinkParaId2 and FeatureSetDownlinkId2 included in the IE corresponding to FeatureSet5 are indexed to the corresponding IE, and the IE corresponding to FeatureSetDownlinkParaId2 corresponds to the bandwidth level capability parameter 2 and the carrier level capability parameter 2 indexed by FeatureSetDownlinkId2. Forms the fifth type of downlink capability parameter.
  • the capability message structure of FIG. 8 may also be represented by FIG. 10. Among them, only the IE corresponding to FeatureSetDownlinkParaId1 and the IE corresponding to FeatureSetDownlinkPerCCId1 are shown in FIG. 10. Similarly, the capability message structure shown in FIG. 9 can also be expressed in other forms, as shown in the related descriptions of FIG. 8 and FIG. 10, and each downlink capability parameter in FIG. 9 specifically includes a carrier-level downlink capability parameter and a frequency band. For the downlink capability parameter of the level, refer to the description of FIG. 8 described above, which will not be repeated here.
  • Case 3 The same type of IE included in the capability message in Case 2 above.
  • the following row capability parameters are taken as an example.
  • the capability message includes a first information unit (FeatureSetDownlinkParaIE), a second information unit (FeatureSetDownlinkPerCCIE), a third information unit (FeatureSetIE), and a fourth information unit (FeatureSetDownlinkIE).
  • FeatureSetDownlinkParaIE a first information unit
  • FeatureSetDownlinkPerCCIE a second information unit
  • FeatureSetIE third information unit
  • FeatureSetDownlinkIE fourth information unit
  • the capability parameters included in FeatureSetDownlinkPerCC and FeatureSetDownlinkPara IE can refer to the description in Case 2, and will not be repeated here.
  • FeatureSetDownlinkIE includes a first identifier and a second identifier.
  • the first identifier is the identifier corresponding to FeatureSetDownlinkPara, ie, it may be a FeatureSetDownlinkParaId
  • the second identifier is the identifier corresponding to FeatureSetDownlinkPerCC, and may be the featureSetDownlinkPerCCId.
  • the relationship between FeatureSetDownlinkPara IE and FeatureSetDownlinkPerCC IE may be the relationship between FeatureSetDownlinkParaId and FeatureSetDownlinkPerCCId.
  • the first identifier and at least one second identifier have an association relationship, and the association relationship is used to indicate the relationship between FeatureSetDownlinkPara and IE and FeatureSetDownlinkPerCC.
  • each FeatureSetDownlinkParaId corresponds to at least one FeatureSetDownlinkPerCCId.
  • FIG. 11 shows the structure of a capability message when one FeatureSetDownlinkParaId corresponds to one FeatureSetDownlinkPerCCId
  • FIG. 12 shows the structure of a capability message when one FeatureSetDownlinkParaId corresponds to three FeatureSetDownlinkPerCCIds.
  • the number of FeatureSetDownlinkPerCCId corresponding to each FeatureSetDownlinkParaId can be set separately, which is not limited here.
  • FeatureSetIE includes a fourth identifier, and the fourth identifier is FeatureSetDownlinkId.
  • the capability parameters of the terminal on one frequency band of one frequency band combination include the following:
  • the first capability parameter includes: the IE index corresponding to FeatureSetDownlinkId1 to the corresponding FeatureSetDownlinkIE, and then the IE index corresponding to FeatureSetDownlinkId1 to the carrier level capability parameter 1 and the band level capability parameter 1, the carrier level capability parameter 1 and the frequency band
  • the capability parameter 1 of the level constitutes the first capability parameter.
  • the second type of capability parameter includes the carrier level capability parameter 2 and the frequency band level capability parameter 1 which are indexed by the IE index corresponding to FeatureSetDownlinkId2.
  • the fourth type of capability parameter includes: a carrier level capability parameter 1 and a frequency band level capability parameter 2 to which the IE index corresponding to FeatureSetDownlinkId4 corresponds.
  • the fifth capability parameter includes: a carrier-level capability parameter 2 and a band-level capability parameter 2 that are indexed by the IE index corresponding to FeatureSetDownlinkId5.
  • the sixth capability parameter includes: a carrier-level capability parameter 3 and a band-level capability parameter 2 which are indexed by the IE index corresponding to FeatureSetDownlinkId1.
  • the capability message structure of FIG. 11 may also be represented by FIG. 13.
  • the capability message structure shown in FIG. 12 may also be expressed in other forms. For details, refer to the related descriptions of FIG. 11 and FIG. 12, and details are not described herein again.
  • Case 4 The following row capability parameters are taken as an example.
  • the capability message includes a first information unit (FeatureSetDownlinkIE), a second information unit (FeatureSetDownlinkPerCCIE), and a third information unit (FeatureSetIE).
  • FeatureSetIE The downlink capability parameters included in the FeatureSetDownlinkPerCCIE can be referred to the descriptions in the above cases 1, 2, and 3, and are not repeated here.
  • FeatureSetIE contains a first identifier, and the first identifier is an identifier corresponding to the first information unit (ie, FeatureSetDownlinkId).
  • FeatureSetDownlink IE includes a downlink capability parameter and a carrier level parameter set at a frequency band level.
  • the carrier level parameter set includes at least two second identifiers, and the second identifier is an identifier corresponding to the second information unit (ie, FeatureSetDownlinkPerCCId).
  • the association between the first information unit and the second information unit is carried in the first information unit through the second identifier.
  • FIG. 14 is a schematic structural diagram of a capability message. Therefore, the downlink capability parameters of the terminal on one frequency band of one frequency band combination include the following:
  • the first type of downlink capability parameter includes: FeatureSetDownlink IE1 index to the corresponding FeatureSetDownlink IE, and then the IE index corresponding to FeatureSetDownlinkId1 to the carrier-level downlink capability parameter 1 and the band-level downlink capability parameter 1, and the carrier-level downlink capability parameter 1 And the downlink capability parameter 1 of the frequency band level constitutes the first downlink capability parameter.
  • the second type of downlink capability parameter includes: a downlink capability parameter 2 of the carrier level and a downlink capability parameter 1 of a frequency band indexed by the IE index corresponding to FeatureSetDownlinkId1.
  • the third type of downlink capability parameter includes: a downlink capability parameter 3 of a carrier level and a downlink capability parameter 1 of a frequency band indexed by the IE index corresponding to FeatureSetDownlinkId1.
  • the capability message of FIG. 14 can also be represented by FIG. 15.
  • FIG. 15 For a detailed description of the capability message, refer to the descriptions of cases 1, 2, and 3, and details are not described herein again.
  • the terminal before sending a capability message to the access network device, the terminal needs to establish an RRC connection with the access network device, so as to send the capability message to the access network device through the RRC connection.
  • the RRC connection can be used to send the capability message to the access network device directly. If the terminal is in an idle state, the terminal may first establish an RRC connection with the access network device, and then send a capability message to the access network device.
  • the capability message when the terminal reports its capabilities in NR and E-UTRA, the capability message carries a container of NR and an E-UTRA container.
  • the container of the NR includes an IE having any of the structures shown in FIG. 6 to FIG. 13.
  • the capabilities supported by the terminal in the NR are reported.
  • the E-UTRA container includes the The IE of any structure reports the capabilities supported by the terminal in E-UTRA.
  • Band-level capability parameters indicated by dashed box 401 that is, the terminal can report multiple carrier-level capability parameters at the same time as reporting a band-level capability parameter, reducing band-level capability parameters Probability of repeated reporting, thereby reducing signaling overhead when the terminal reports capabilities.
  • the terminal in the embodiments of the present application includes a hardware structure and / or a software module corresponding to each function.
  • the embodiments of this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is performed by hardware or computer software-driven hardware depends on the specific application of the technical solution and design constraints. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the technical solutions of the embodiments of the present application.
  • FIG. 16 shows a schematic block diagram of a communication device provided in an embodiment of the present application.
  • the communication device 1600 may be an independent device or a chip that can be used for the device.
  • the communication device 1600 may be the foregoing terminal or a network device.
  • the communication device 1600 includes a processing unit 1602 and a communication unit 1603.
  • the processing unit 1602 may be used to support the terminal to determine whether it is in a connected state / idle state, thereby determining whether to establish an RRC connection with the access network device, and / or for the scheme described herein. Other processes.
  • the communication unit 1603 is used to support communication between the terminal and other network elements (such as the access network device described above), for example, to support the terminal to perform S501 and S502 in FIG. 5 and / or other processes used in the scheme described herein. .
  • the processing unit 1602 may be configured to support the network device for the process described herein, for example, allocate corresponding communication resources to the terminal.
  • the communication unit 1603 is used to support communication between a network device and other network elements (such as the above-mentioned terminal, etc.), for example, to support the network device to perform S501 and S502 in FIG. 5 and / or other processes used in the scheme described herein.
  • the communication device 1600 may further include a storage unit 1601 for storing program code and data of the communication device 1600.
  • the data may include, but is not limited to, original data or intermediate data.
  • the processing unit 1602 may be a controller or the processor 401 or the processor 405 shown in FIG. 4, for example, it may be a central processing unit (Central Processing Unit), a general-purpose processor, and digital signal processing ( Digital Signal Processing (DSP), Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any of them combination. It may implement or execute various exemplary logical blocks, modules, and circuits described in connection with the present disclosure.
  • a processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
  • the communication unit 1603 may be a transceiver, a transceiver circuit, or the communication interface 404 shown in FIG. 4 and the like.
  • the storage unit 1601 may be a memory 403 shown in FIG. 4.
  • a person of ordinary skill in the art may understand that in the foregoing embodiments, all or part may be implemented by software, hardware, firmware, or any combination thereof.
  • software When implemented in software, it may be implemented in whole or in part in the form of a computer program product.
  • a computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are wholly or partially generated.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server, or data center via a wired (e.g., Coaxial cable, optical fiber, Digital Subscriber Line (DSL) or wireless (such as infrared, wireless, microwave, etc.) transmission to another website site, computer, server or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, and the like including one or more available medium integration.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a Digital Video Disc (DVD)), or a semiconductor medium (for example, a solid state disk (Solid State Disk, SSD)), etc. .
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, a Digital Video Disc (DVD)
  • DVD Digital Video Disc
  • semiconductor medium for example, a solid state disk (Solid State Disk, SSD)
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of units is only a logical function division.
  • multiple units or components may be combined or integrated.
  • 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, and may be electrical or other forms.
  • a unit described as a separate component may or may not be physically separated, and a component displayed as a unit may or may not be a physical unit, which may be located in one place, or may be distributed to multiple network devices (such as terminal devices). )on. 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 functional unit may exist independently, or two or more units may be integrated into one unit.
  • the above integrated unit may be implemented in the form of hardware, or in the form of hardware plus software functional units.

Landscapes

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

Abstract

La présente invention concerne un procédé et un appareil de signalement de capacité, se rapportant au domaine des technologies de communication et susceptibles de résoudre le problème, rencontré dans l'état de la technique, d'importants surdébits de signalement dus au signalement de la capacité par un terminal. Ledit procédé comprend les étapes suivantes : un dispositif terminal envoie à un dispositif de réseau un message de capacité, le message de capacité comprenant une première unité d'informations et une seconde unité d'informations, et une relation d'association entre la première unité d'informations et la seconde unité d'informations, la première unité d'informations comprenant un paramètre de capacité d'un niveau de bande de fréquence et la seconde unité d'informations comprenant un paramètre de capacité d'un niveau de porteuse. Le procédé s'applique au processus de signalement d'un message de capacité par un terminal.
PCT/CN2019/107245 2018-09-27 2019-09-23 Procédé et appareil de signalement de capacité Ceased WO2020063521A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811137734.9 2018-09-27
CN201811137734.9A CN110958603B (zh) 2018-09-27 2018-09-27 能力上报方法及装置

Publications (1)

Publication Number Publication Date
WO2020063521A1 true WO2020063521A1 (fr) 2020-04-02

Family

ID=69949550

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/107245 Ceased WO2020063521A1 (fr) 2018-09-27 2019-09-23 Procédé et appareil de signalement de capacité

Country Status (2)

Country Link
CN (1) CN110958603B (fr)
WO (1) WO2020063521A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230209577A1 (en) * 2020-09-30 2023-06-29 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Signaling transmitting method, signaling receiving method, apparatus, device, and storage medium

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116137949A (zh) * 2021-09-17 2023-05-19 北京小米移动软件有限公司 终端设备的天线切换能力的上报方法及其装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102223638A (zh) * 2010-04-19 2011-10-19 中兴通讯股份有限公司 一种传输终端支持双频段多载波能力的方法及系统
CN102348212A (zh) * 2010-08-03 2012-02-08 普天信息技术研究院有限公司 一种载波能力上报方法
WO2018085723A1 (fr) * 2016-11-04 2018-05-11 Intel IP Corporation Systèmes et procédés pour optimiser la notification de paramètres de capacité physique dans un réseau de télécommunication
CN108055698A (zh) * 2017-11-13 2018-05-18 深圳市万普拉斯科技有限公司 载波聚合中射频能力上报的控制方法和装置

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101888646B (zh) * 2009-05-12 2013-03-13 中国移动通信集团公司 一种信道质量反馈信息获得方法、系统以及基站
CN101959251A (zh) * 2009-07-21 2011-01-26 鼎桥通信技术有限公司 一种支持多载波频段能力的上报方法
US9001750B2 (en) * 2010-04-05 2015-04-07 Qualcomm Incorporated Method and apparatus for signaling user equipment capabilities
US8750807B2 (en) * 2011-01-10 2014-06-10 Mediatek Inc. Measurement gap configuration in wireless communication systems with carrier aggregation
KR20130126427A (ko) * 2012-05-11 2013-11-20 주식회사 팬택 다중 요소 반송파 시스템에서 단말의 성능정보의 전송장치 및 방법
CN103580781B (zh) * 2012-07-23 2019-01-04 中兴通讯股份有限公司 能力信息处理方法、装置及基站
US9392505B2 (en) * 2012-11-01 2016-07-12 Lg Electronics Inc. Method for reporting information on multiband capability to network at user equipment in wireless communication system and an apparatus therefor
CN104144447B (zh) * 2013-05-08 2018-06-26 中国移动通信集团公司 一种信息传输方法和设备
WO2015142278A1 (fr) * 2014-03-20 2015-09-24 Telefonaktiebolaget L M Ericsson (Publ) Noeud et procédé pour l'établissement de rapport de capacité
CN106878980B (zh) * 2017-02-16 2020-05-19 深圳市万普拉斯科技有限公司 载波聚合能力更新方法、装置及用户终端

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102223638A (zh) * 2010-04-19 2011-10-19 中兴通讯股份有限公司 一种传输终端支持双频段多载波能力的方法及系统
CN102348212A (zh) * 2010-08-03 2012-02-08 普天信息技术研究院有限公司 一种载波能力上报方法
WO2018085723A1 (fr) * 2016-11-04 2018-05-11 Intel IP Corporation Systèmes et procédés pour optimiser la notification de paramètres de capacité physique dans un réseau de télécommunication
CN108055698A (zh) * 2017-11-13 2018-05-18 深圳市万普拉斯科技有限公司 载波聚合中射频能力上报的控制方法和装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"R2-1811680, [I720]Draft CR on proposal of reporting SCS and BW in Featu- reSetPerCC", 3GPP TSG-RAN WG2 MEETING #103, 24 August 2018 (2018-08-24), XP051521320 *
LG ELECTRONICS INC: "R2-1810609, NR UE Capability Size Reductio", 3GPP TSG-RAN WG2 MEETING NR AH#2, 6 July 2018 (2018-07-06), XP051467759 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230209577A1 (en) * 2020-09-30 2023-06-29 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Signaling transmitting method, signaling receiving method, apparatus, device, and storage medium
US12452892B2 (en) * 2020-09-30 2025-10-21 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Signaling transmitting method, signaling receiving method, apparatus, device, and storage medium

Also Published As

Publication number Publication date
CN110958603A (zh) 2020-04-03
CN110958603B (zh) 2021-06-29

Similar Documents

Publication Publication Date Title
US11956710B2 (en) Network slice selection method, radio access device, and terminal
US11516704B2 (en) Information transmission method and apparatus
AU2018315286B2 (en) Communication method, source base station, target base station, core network device, and terminal device
US12034821B2 (en) Computing aware-session management method and communication apparatus
US11805394B2 (en) Context management method and apparatus
CN111726808B (zh) 通信方法和装置
KR102708129B1 (ko) 보안 보호 모드 결정 방법 및 장치
US12101838B2 (en) Communications method, apparatus, and system
CN111385830B (zh) 通信方法和装置
US12581285B2 (en) Method for traffic descriptor transmission and related devices
US12507143B2 (en) Allocating candidate cell identifiers for an integrated access and backhaul (IAB) node migrating to a target IAB donor centralized unit
WO2019196811A1 (fr) Procédé de communication, et appareil associé
WO2020019961A1 (fr) Procédé de mesure de flux de réseau, dispositif de mesure de flux de réseau, et dispositif de plan de commande
CN114557124B (zh) 通信方法、设备及系统
US12028756B2 (en) Cell configuration method and apparatus
US20220007240A1 (en) Communication method and apparatus
CN117676916A (zh) 通信资源管理方法、装置、系统及存储介质
WO2020216099A1 (fr) Procédé de communication et dispositif associé
US12574822B2 (en) Method for determining MEC access point and apparatus
WO2020073899A1 (fr) Procédé et appareil de transmission de données
CN116489703B (zh) 感知节点确定方法、感知节点控制方法和相关设备
CN114342468A (zh) 信息更新方法、设备及系统
WO2022237857A1 (fr) Procédé de détermination de mode d'activation de protection de sécurité, procédé de communication et appareil de communication
CN114788403A (zh) 通信方法、设备及系统
EP3813481A1 (fr) Procédé et appareil de transmission d'informations

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: 19865676

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19865676

Country of ref document: EP

Kind code of ref document: A1