WO2018039974A1 - 一种用户设备能力信息的上报方法及装置 - Google Patents

一种用户设备能力信息的上报方法及装置 Download PDF

Info

Publication number
WO2018039974A1
WO2018039974A1 PCT/CN2016/097532 CN2016097532W WO2018039974A1 WO 2018039974 A1 WO2018039974 A1 WO 2018039974A1 CN 2016097532 W CN2016097532 W CN 2016097532W WO 2018039974 A1 WO2018039974 A1 WO 2018039974A1
Authority
WO
WIPO (PCT)
Prior art keywords
capability information
network side
request message
capability
split
Prior art date
Application number
PCT/CN2016/097532
Other languages
English (en)
French (fr)
Inventor
权威
陈斌
李秉肇
许斌
张戬
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP21185706.5A priority Critical patent/EP3962161B1/en
Priority to CN202111220654.1A priority patent/CN114125822B/zh
Priority to CN202111220085.0A priority patent/CN114125821A/zh
Priority to EP16914540.6A priority patent/EP3499954B1/en
Priority to CN201680088778.XA priority patent/CN109644372B/zh
Priority to PCT/CN2016/097532 priority patent/WO2018039974A1/zh
Publication of WO2018039974A1 publication Critical patent/WO2018039974A1/zh
Priority to US16/287,958 priority patent/US10887758B2/en
Priority to US17/127,330 priority patent/US11528596B2/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
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/183—Processing at user equipment or user record carrier
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices

Definitions

  • the present invention relates to the field of wireless communication technologies, and in particular, to a method and an apparatus for reporting user equipment capability information.
  • FIG. 1 is a schematic diagram of an LTE air interface protocol stack.
  • the UE side includes a NAS (Non-access stratum) layer, an RRC (Radio Resource Control) layer, and a PDCP (Packet Data Convergence Control) layer, RLC. (Radio Link Control) layer, MAC (Medium Access Control) layer and PHY (Physical Layer) layer.
  • NAS Non-access stratum
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Control
  • RLC Radio Link Control
  • MAC Medium Access Control
  • PHY Physical Layer
  • the main services and functions of the RRC layer include broadcast and system-related non-access stratum (NAS) information, mobility management, paging, and establishment, reconstruction, maintenance, and release of RRC connections between UEs and eNBs; on the UE side, RRC
  • NAS non-access stratum
  • the data packets generated by the layer need to be processed by the PDCP layer and then transmitted to other protocol layers such as the RLC layer, the MAC layer, and the PHY layer.
  • the PDCP layer provides services for the upper layer such as the RRC layer, including data transmission for the control plane and the user plane, compression, encryption, and integrity protection for the IP data header.
  • the UE capability information is the radio access capability and the wireless function that can be supported by the UE.
  • the UE sends a UE Capability Enquiry message to the UE in the connected state. After receiving the capability request message, the UE reports the capability information of the UE.
  • the network side is provided to enable the network side to understand the capabilities of the UE, thereby providing better services for the UE.
  • the capacity of the data packet that the PDCP layer can handle during the packet processing process is limited.
  • the maximum tolerance of the data packet that the PDCP layer can process in the LTE protocol is 8188 octets, and as the LTE technology continues to evolve, more and more features For example, LAA (licensed-assisted access) and Massive CA are introduced, resulting in more and more capability information that the UE needs to report. Therefore, the UE capability information generated by the RRC layer on the UE side will become larger and larger, even More than 8188octets.
  • the PDCP layer when the data packet of the RRC layer is transmitted to the PDCP layer, if the maximum tolerance of the data packet processed by the PDCP layer is exceeded, the PDCP layer cannot be processed. Processing, causing errors, and thus affecting the reporting of UE capability information.
  • a method and a device for reporting user equipment capability information are provided in the embodiment of the present application, to solve the problem that when the RRC layer data packet is transmitted to the PCDP layer, the data packet size exceeds the maximum tolerance that the PDCP layer can handle. problem.
  • the embodiment of the present application provides a method for reporting user equipment UE capability information, where the method includes: the UE acquires its own UE capability information; and determines whether the UE capability information size exceeds that of the UE's PDCP layer. Maximum capacity of the UE; if the maximum tolerance that can be processed by the PDCP layer of the UE is exceeded, the UE capability information is split into at least two partial UE capability information, and the capability information of each part of the UE after splitting is not Exceeding the maximum tolerance that can be processed by the PDCP layer; reporting the split capability of the at least one part of the UE to the network side.
  • the PDCP layer on the UE side determines and splits the generated UE capability information, and splits the UE capability information that exceeds the maximum tolerance that can be processed by the PDCP layer, so that it is smaller than the maximum PDCP layer. Handling the tolerance, and avoiding the error caused by the excessive capability information of the UE, and ensuring the normal operation of the UE capability information reporting process.
  • the method before the splitting the at least one part of the UE capability information is reported to the network side, the method further includes: receiving, by the UE, a capability that is sent by the network side and needs to report the UE capability.
  • a request message, the first request message includes a system broadcast message and a radio resource control RRC message.
  • the splitting the UE capability information into the at least two partial UE capability information includes: splitting the UE capability information according to a RAT system division principle, or Splitting according to the importance of the capability of the UE, or splitting according to the priority order of reporting of the UE capability, or splitting according to the principle of the protocol version, or split according to the principle of reporting the number of times on the network side.
  • the method further includes: detecting, by the UE, whether the second request of the network side feedback is received a message; if the second request message is detected, the UE sends at least one of remaining partial UE capability information to the network side.
  • the UE reports the partial UE capability information to the network side for the second time, if the third request message sent by the network side is also received, the UE further reports the partial UE capability information until the UE transmits all the split partial UE capability information. The report is sent to the network side, or the network side sends the indication information for stopping the reporting of the UE capability information to the UE.
  • splitting the UE capability information into at least two partial UE capability information includes: splitting the UE capability information into at least one detailed UE capability information and Corresponding coarse UE capability information, where a coarse UE capability information may be corresponding to a plurality of detailed UE capability information, where the detailed UE capability information is used to provide a reference basis for the network side to configure a wireless parameter for the UE.
  • the coarse UE capability information is used to indicate that the network side sends a third request message to the UE, and the reporting the at least one partial UE capability information to the network side includes: the coarse UE capability information Reporting to the network side; if the third request message fed back by the network side according to the coarse UE capability information is received, part or all of the detailed UE capability information corresponding to the coarse UE capability information is received. Send to the network side.
  • the UE capability information is firstly split into the detailed UE capability information and the coarse UE capability information, and then the coarse UE capability information is reported to the network side, and the network side feedback is used to determine whether to report the rough UE capability.
  • Detailed UE capability information corresponding to the information, and which detailed UE capability information is reported.
  • the present embodiment can prevent the UE from transmitting more than the PDCP layer processing capability when the UE capability information is too large.
  • the UE can report a certain part of the detailed UE capability information according to the network side requirement, and can avoid reporting all detailed UE capability information. , thereby saving air interface wireless resources.
  • the reporting, by the network side, the splitting of the at least one part of the UE capability information includes: sorting all the split partial UE capability information; If the first request message carries the priority sequence reported by the part of the UE capability information, the part of the UE capability information is reported to the network side according to the priority order.
  • splitting the UE capability information into at least two parts includes: an RRC layer of the UE or The PDCP layer splits the UE capability information into at least two parts.
  • the processor or other layer of the UE is further split into packets that exceed the maximum processing tolerance of its PDCP layer.
  • the splitting the at least one part of the UE capability information to the network side includes: the UE The RLC layer receives and buffers all split partial UE capability information in a data packet form; performs segmentation and concatenation processing on all the partial UE capability information data packets to form a data packet to be transmitted; and passes the to-be-transmitted data packet The RRC message is reported to the network side.
  • all the UE capability information processed by the PDCP layer is combined on the UE side, and then reported to the base station or the network side device at one time, and only needs to be reported once, thereby avoiding multiple reporting and causing The signaling interaction of the network is frequent, which saves network overhead.
  • the indication information is used to indicate any one of the following: whether the UE has remaining part of the UE capability information, and the remaining part of the UE capability information needs to be reported. The number of times, the order of the currently reported partial UE capability information in all partial UE capability information.
  • the implementation of the present aspect carries the indication information in the RRC message sent by the UE, so that the network side can obtain the partial UE capability information status of the UE side to determine whether to send the UE capability information request message to the UE.
  • the embodiment of the present application provides a UE capability information receiving method, which is applied to a network side device, where the method includes: the network side sends a first request message that needs to report UE capability information to the UE; a first RRC message that is sent by the first request message, where the first RRC message carries at least one partial UE capability information formed by splitting UE capability information; and determining the UE according to the partial UE capability message. Whether there is any remaining UE capability information, or whether the UE is required to report partial UE capability information; if yes, generate and send a second request message to the UE; if not, generate a stop indication, and The stop indication sends the UE, or no more indication is sent to the UE.
  • the part of the UE capability information received by the network side is the coarse UE capability information
  • the method further includes: receiving, by the network side, the RRC message reported by the UE, and combining, for example, part of the UE capability information corresponding to the RRC message, to generate The total UE capability information of the UE is sent to the MME, so that after the MME saves the UE capability information, the network side can directly obtain the capability information of the UE from the MME, to avoid The UE reports again, which saves network air interface resources.
  • the first request message includes a system broadcast message and a radio resource control RRC message
  • the first request The message is used to notify the UE of the need to select the reported UE capability information, so that the UE can know which UE capability information is reported to the network side when receiving the first request message.
  • the first request message further includes a priority order indicating that the UE reports partial UE capability information. The UE is reported in the order of priority.
  • the embodiment of the present application further provides a method for extending a processing tolerance of a PCDP layer, where the method includes: setting a maximum tolerance value of a data packet that can be processed by a PDCP layer on a UE side and/or a network side to Not less than 8188octets. That is, the packet size that can be processed by the PDCP layer is extended, and the value is expanded to be greater than 8188 octets, and further, the processing tolerance of the PDCP layer is extended to the wireless size.
  • the processing tolerance of the PDCP layer is extended to the wireless size.
  • the embodiment of the present application further provides a user equipment (UE), including: a receiving unit, a processing unit, and a sending unit, where the receiving unit is configured to acquire UE capability information of the UE, and the processing unit is configured to determine Whether the size of the UE capability information exceeds a maximum tolerance that can be processed by the PDCP layer of the UE; if the maximum tolerance that can be processed by the PDCP layer of the UE is exceeded, the UE capability information is split into at least two parts. UE capability information, and each part of the UE capability information after the split does not exceed the maximum tolerance that can be processed by the PDCP layer; the sending unit is configured to report the split at least one partial UE capability information Give the network side.
  • UE user equipment
  • the method provided by the present invention improves the judgment and segmentation function of the UE capability information size by the RRC layer of the UE, and the mechanism of reporting the UEs when the UE capability information is too large, thereby preventing the data packets transmitted to the PDCP layer from exceeding the capability.
  • the maximum tolerance of processing affects the reporting process of UE capability information.
  • the UE is also used to implement various implementations of the first aspect described above.
  • the embodiment of the present application further provides a base station, which is applied to a network side, where the base station includes: a sending unit, a receiving unit, and a processing unit, where the sending unit is configured to send, to the UE, information about the capability of the UE to be reported.
  • a first request message the receiving unit, configured to receive a first RRC message that is sent by the UE according to the first request message, where the first RRC message carries at least one formed by splitting UE capability information.
  • the processing unit configured to determine, according to the part of the UE capability message, whether the UE has remaining UE capability information, or whether the UE is required to report part of the UE capability information; if yes, And generating a second request message, where the sending unit is further configured to send the second request message to the UE.
  • the base station is also used to implement various implementations of the second aspect described above.
  • the embodiment of the present application further provides a mobility management entity MME, configured to receive and save all or part of UE capability information sent by the network side, and when the network side needs capability information of the UE, The saved UE capability information is sent to the network side, so that the UE does not report the UE capability information again, and the air interface resource is saved.
  • MME mobility management entity
  • the embodiment of the present application further provides a user equipment, including: a receiver, a processor, and a sending
  • the receiver is configured to obtain the UE capability information of the UE.
  • the processor is configured to determine whether the UE capability information size exceeds a maximum tolerance that can be processed by the PDCP layer of the UE.
  • the maximum tolerance that can be processed by the PDCP layer, the UE capability information is split into at least two partial UE capability information, and the capability information of each part of the UE after splitting does not exceed the maximum that can be processed by the PDCP layer.
  • the transmitter is configured to report the split capability of the at least one part of the UE to the network side.
  • the receiver is further configured to receive a first request message that is sent by the network side and needs to report the capability of the UE, where the first request message includes a system broadcast message and an RRC message. .
  • the processor is further configured to split the UE capability information according to a RAT system division principle, or split according to the importance of the UE capability, or Split according to the principle of the protocol version, or split according to the principle of reporting the number of times on the network side.
  • the processor is further configured to detect whether a second request message fed back by the network side is received, and the transmitter is further configured to detect In the second request message, the UE sends at least one of the remaining partial UE capability information to the network side.
  • the processor is further configured to split the UE capability information into at least one detailed UE capability information and coarse UE capability information corresponding thereto, the detailed UE
  • the capability information is used to provide a reference for the network side to configure a radio parameter for the UE, where the coarse UE capability information is used to indicate that the network side sends a third request message to the UE; And reporting the coarse UE capability information to the network side; and if the third request message fed back by the network side according to the coarse UE capability information is received, the coarse UE capability information is corresponding to Part or all of the detailed UE capability information is sent to the network side.
  • the processor is further configured to: sort all the split partial UE capability information; the transmitter is further configured to: The first request message carries the priority sequence reported by the part of the UE capability information, and the partial UE capability information is reported to the network side according to the priority order.
  • the RRC layer or the PDCP layer of the UE splits the UE capability information into at least two parts. .
  • the receiver is further configured to receive and buffer all split part UE capability information in a data packet form.
  • the processor is further configured to perform a split and concatenation process on the data packets of all the part of the UE capability information to form a data packet to be transmitted, and the transmitter is further configured to pass the to-be-transmitted data packet to the RRC.
  • the message is reported to the network Collateral side.
  • the embodiment of the present application further provides a base station, which is applied to a network side, and includes: a transmitter, a receiver, and a processor, where the transmitter is configured to send, to the UE, a first request that needs to report UE capability information.
  • the receiver is configured to receive a first RRC message that is sent by the UE according to the first request message, where the first RRC message carries at least one partial UE capability formed by splitting UE capability information.
  • the processor is configured to determine, according to the part of the UE capability message, whether the UE has remaining UE capability information, or whether the UE is required to report partial UE capability information; if yes, generate The second request message; the sender is further configured to send the second request message to the UE.
  • the processor is further configured to determine, if the partial UE capability information received by the network side is coarse UE capability information, determine whether the rough UE is required The detailed UE capability information corresponding to the capability information; if the detailed UE capability information is required, generating a third request message; the sender is further configured to send the third request message to the UE.
  • the receiver is further configured to receive an RRC message that is reported by the UE, where the processor is further configured to: The UE capability information is combined to generate total UE capability information of the UE, and the transmitter is further configured to send the combined total UE capability information to the MME.
  • the first request message includes a system broadcast message and an RRC message, where the first request message is used The UE is notified of the need to select the reported UE capability information.
  • the first request message further includes a priority order indicating that the UE reports partial UE capability information. The UE is reported in the order of priority.
  • the embodiment of the present application further provides a computer storage medium, wherein the computer storage medium may store a program, and the program may be implemented in each implementation manner of the method for reporting user equipment capability information. Part or all of the steps.
  • FIG. 1 is a schematic diagram of an LTE air interface protocol stack according to an embodiment of the present application
  • FIG. 2 is a schematic structural diagram of an LTE network according to an embodiment of the present disclosure
  • FIG. 3 is a schematic flowchart of a method for reporting UE capability information according to an embodiment of the present disclosure
  • FIG. 4 is a signaling flowchart of a method for reporting UE capability information according to an embodiment of the present disclosure
  • FIG. 5 is a signaling flowchart of another method for reporting UE capability information according to an embodiment of the present disclosure
  • FIG. 6 is a signaling flowchart of still another method for reporting UE capability information according to an embodiment of the present disclosure
  • FIG. 7 is a structural block diagram of a UE according to an embodiment of the present application.
  • FIG. 8 is a structural block diagram of a base station according to an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a hardware of a UE according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of hardware of a base station according to an embodiment of the present disclosure.
  • the technical solutions provided by the present application are mainly applied to various wireless communication systems, such as an LTE system, a UMTS, an LTE-like system, or a 5G system.
  • the specific architecture of the foregoing wireless communication system is not limited.
  • This application takes the LTE network architecture shown in Figure 2 as an example to describe the application scenario of the technical solution of the present application.
  • the LTE network architecture shown in FIG. 2 includes: at least one MME (Mobility Management Entity) or S-GW (Serving Gateway), at least one base station (eNodeB, abbreviated eNB), and at least one user equipment (User Equipment, UE) or E-UTRAN (Evolved UMTS Terrestrial Radio Access Network).
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • eNodeB base station
  • UE User Equipment
  • E-UTRAN Evolved UMTS Terrestrial Radio Access Network
  • Each base station is also referred to as an access device for communicating with the UE.
  • the MME is a mobility management entity and is responsible for the positioning and paging process of the UE.
  • the MME is also used for signaling processing and the like.
  • the MME/S-GW communicates with the eNB through the S1 communication interface, and the two eNBs communicate through the X2 communication interface.
  • the data packet of the UE capability information generated by the RRC layer on the UE side is processed by the PDCP layer, passes through the layers of the UE from top to bottom, and finally passes through the PHY layer and then is sent to the eNB, and the PHY of the eNB.
  • the layer After receiving the information or data packet sent by the UE, the layer processes the received information according to the structure level of the LTE air interface protocol stack from bottom to top.
  • the UE capability information or the data packet passes through the PDCP layer of the UE or the eNB, if the packet is larger than the PDCP.
  • the maximum tolerance of 8188octets that the layer can handle will cause an error, which in turn affects the transmission of packets of UE capability information.
  • the method for reporting user equipment UE capability information is used to solve the problem that when the data packet of the UE capability information of the RRC layer is transmitted to the PCDP layer, the error is caused by exceeding the maximum tolerance that the PDCP layer can handle. .
  • the UE capability information described in the present application refers to the radio access capability possessed by the UE itself and the wireless function features that can be supported.
  • a method for reporting UE capability information of a user equipment includes the following steps:
  • Step S301 The UE acquires its own UE capability information.
  • the first request message also referred to as a UE Capbility Enquiry message, or an RRC message
  • the first request message may be a system broadcast message, and may also be a dedicated RRC message.
  • the first request message is used to notify the UE that the UE capability information to be reported is selected.
  • the UE After receiving the message, the UE generates the capability information of the UE, so that the UE obtains its own UE capability information.
  • the UE capability information may also be the UE's fixed capability information, which is stored on the UE side. When the network side needs the capability information of the UE, it is reported.
  • Step S302 Determine whether the size of the UE capability information exceeds a maximum tolerance that can be processed by the PDCP layer of the UE.
  • the maximum tolerance of data packets that can be processed by the PDCP layer of the UE is 8188 octets, that is, the maximum PDCP SDU is 8188 octets.
  • the UE determines whether the generated UE capability information exceeds 8188 octets.
  • octet is a computer language, meaning that the Internet standard uses octets.
  • 1 byte (bytes) 8 bits (bits).
  • Step S303 If the maximum tolerance that can be processed by the PDCP layer of the UE is exceeded, the UE capability information is split into at least two partial UE capability information, and the capability information of each part of the UE after splitting does not exceed The maximum tolerance that the PDCP layer can handle.
  • the UE capability information is split according to a RAT (Radio Access Technology) system division principle, or is split according to the importance of the UE capability. Alternatively, split according to the reporting priority of the UE capability, or split according to the principle of protocol version, or split according to the principle of reporting the number of times on the network side. Regardless of the splitting method, it is guaranteed that each part of the UE capability information after splitting does not exceed the maximum tolerance that the PDCP layer can handle.
  • RAT Radio Access Technology
  • the RRC layer of the UE may directly split and generate the first part UE Capability Information, the second part UE capability information, the third part UE capability information, and the like.
  • the UE capability information may be split by the RRC layer of the UE, or may be split by the PDCP layer, or performed by other processing units of the UE. If the RRC layer of the UE performs splitting, the UE first encapsulates the split UE capability information into several data packets, and sends each data packet to the PDCP layer.
  • Step S304 The at least one partial UE capability information of the split is reported to the network side.
  • the UE reports the split UE capability information to the network side by means of an RRC message.
  • the embodiment of the present application provides a manner for the UE to report the UE capability information, and optionally, one of the UE capability information is reported. The process is as follows:
  • the user equipment UE judges and splits the UE capability information (S402), and reports the split first UE capability information by using the first RRC message.
  • the first RRC message further includes indication information, where the indication information is used to indicate or inform the base station/network side whether the remaining part of the UE capability information needs to be reported, and/or The remaining part of the UE capability information, and/or the remaining part of the UE capability information, and/or the UE capability information is split into several parts in total, and the current part is the first part, or the currently reported first part of the UE. The ratio of capability information to total UE capability information.
  • the base station/network side If the base station/network side receives the first RRC message, and according to the indication information contained therein, the UE side still has some UE capability information remaining, or the UE capability information is not all reported, the base station/network side generates a second request (the Second UE) The message is sent to the UE (S404), where the second request message is used to indicate that the UE continues to report part of the UE capability information. After receiving the second request message, the UE reports the split second part of the UE capability information to the base station/network side by using the second RRC message (S405), and the second RRC message also includes indication information, and is used to notify the base station. Whether there is any remaining UE capability information.
  • the base station/network side combines all the received partial UE capability information (S406), and saves the merged UE. Capability information for subsequently providing services to the UE based on UE capability information.
  • step S403 if the first RRC message sent by the UE to the base station/network side does not include the indication information, the base station/network side needs to determine whether the UE needs to continue to report the UE capability information. In addition, if the base station/network side determines that the UE capability information sent by all the UEs has been received, or does not need to send the UE capability information, the UE sends a stop indication to the UE to stop the UE from continuing to report the UE capability information, or Any indication is sent to the UE.
  • the network side after the step S406, after receiving the UE capability information, the network side sends the UE capability information. Saved to the Mobile Management Entity (MME). After the MME saves all the capability information of the UE, after the UE returns to the idle state and enters the connection state again, the network side may obtain the capability of the UE from the MME, so that the UE does not need to report the UE capability information again, saving Empty resources.
  • MME Mobile Management Entity
  • the base station/network side may combine all the UE capability information and send it to the MME to save, or each part of the UE capability information is directly forwarded to the MME device each time the partial UE capability information reported by the UE is received. Merging and saving by the MME device.
  • the PDCP layer on the UE side determines and splits the generated UE capability information, and splits the UE capability information that exceeds the maximum tolerance that can be processed by the PDCP layer, so that it is smaller than the PDCP layer.
  • the maximum processing tolerance which avoids the error caused by the excessive capability information of the UE, ensures the normal operation of the UE capability information reporting process.
  • the first step S501 and the second step S502 of the method are the same as S401 and S402 in the first embodiment, respectively.
  • the RRC layer or the PDCP layer of the UE splits the capability information of the UE into a plurality of partial UE capability information, and the capability information of each split UE does not exceed the maximum of the PDCP layer. Handling tolerances.
  • Step S503 After the split UE UE capability information is processed by the PDCP layer, all the processed UE capability information is combined. Optionally, the processed UE UE capability information is segmented and cascaded at the RLC layer. Or after the MAC layer is multiplexed, merge into one UE capability information and encapsulate it into an RRC message.
  • Step S504 The encapsulated RRC message is reported to the base station/network side device in one time. Further, the RRC message carries the total capability information of the UE, and further includes information indicating that the UE has no remaining part of the UE capability information.
  • Step S505 The base station/network side device receives the RRC message, and according to the LTE air interface protocol stack, the UE capability information is transmitted from the top, and the PDCP layer of the base station/network side device determines whether the UE capability information exceeds the The maximum tolerance that can be processed, that is, 8188 octets, if the maximum tolerance is exceeded, the UE capability information is split into at least two partial UE capability information to ensure that the PDCP layer can be processed normally to avoid errors.
  • the maximum tolerance that can be processed that is, 8188 octets
  • Step S506 After all the partial UE capability information is processed by the PDCP layer of the base station/network side device, the processed partial UE capability information is combined and saved. Optionally, the base station/network side device sends the combined total UE capability information to the MME.
  • the method provided in this embodiment combines the partial UE capability information processed by the PDCP layer on the UE side, and then reports the information to the base station/network side device at one time, and only needs to report once, thereby avoiding the occurrence of multiple reporting processes. Interact with the signaling of the network to save network overhead.
  • step S601 is the same as the first step in the foregoing embodiment.
  • Step S602 The UE determines that the UE capability information of the UE is greater than the maximum tolerance that can be processed by the PDCP layer, and the UE capability information is split into at least one detailed UE capability information and coarse UE capability information corresponding thereto.
  • the UE capability information is used to configure a radio parameter for the network side, where the coarse UE capability information is used to instruct the network side to send a third request message to the UE.
  • the so-called coarse UE capability information means that the network side can obtain certain capabilities of the UE according to the coarse UE capability information, but cannot determine the specific capability information of the UE.
  • the coarse UE capability information is the UE supporting carrier aggregation CA. (Carrier Aggregation), the network side can only obtain the UE to support the CA according to the coarse UE capability information, but can not know which bandwidths or carriers are supported by the UE for aggregation. In this case, the UE needs to report the detailed information again.
  • UE capability information so that the network side configures multi-carrier aggregation function for the UE.
  • the network side can only obtain, according to the coarse UE capability information, that the UE may support the CA, or the Relay or the CoMP (Coordinated Multiple Points).
  • the multi-point cooperation technology such as the feature of version 10, but does not know which version 10 features the UE supports.
  • the UE needs to report the detailed UE capability information again.
  • the so-called rough capability information includes information that the network side can obtain the overall UE function according to a certain classification manner, and does not include specific UE capability information.
  • the important or necessary UE capability information may be divided into detailed UE capability information portions, and the secondary UE capability is divided into the coarse UE capability information; or according to the LTE protocol version, the previous The version information is divided into detailed UE capability information, and the capability of the later newer version is divided into coarse UE capability information; or if the RAT is divided according to the RAT, the capability information of the current RAT is divided into detailed UE capability information, and the capability information of other RATs is used as Rough UE capability information, etc.
  • Step S603 After the division, first report the coarse UE capability information to the network side device;
  • Step S604 The base station/network side device receives the coarse UE capability information, and determines whether the UE needs to report the detailed UE capability information, if necessary, generates a third request message, and sends a third request message to the UE.
  • Step S605 If the UE receives the third request message that is sent by the network side according to the detailed UE capability information, send part or all of the detailed UE capability information corresponding to the coarse UE capability information to The network side device.
  • the UE may report the detailed UE capability information multiple times according to the indication of the network side.
  • the detailed UE capability information reported by the UE to the network side may also carry indication information, which is used to inform the network side whether there is remaining detailed UE capability information, and which detailed UE capability information remains.
  • Step S606 The base station/network side device combines and stores the received coarse UE capability information and the detailed UE capability information, and sends the information to the mobility management entity MME. This step is the same as steps S406 and S506 in the foregoing embodiment, so Narration.
  • the UE divides the UE capability information of the UE into two parts, one part is detailed UE capability information, the other part is coarse UE capability information, and the detailed UE capability information is The coarse UE capability information is corresponding, so the UE first reports the coarse UE capability information according to the requirements of the network side when reporting, and if the detailed UE capability information is required, the UE continues to report the detailed UE capability information corresponding to the coarse UE capability information.
  • the UE capability information is too large, the PDCP layer processing capability can be sent at one time.
  • the detailed capability information of a certain part can be reported according to the network requirements, and it is not necessary to report all the detailed capability information, thereby saving air interface radio resources.
  • This embodiment is an improvement of the first step in the foregoing embodiment, and specifically, the improvement is that
  • the base station or the network side device broadcasts a first request message (UE Capability Enquiry) to all the UEs in the coverage area, where the first request message carries indication information, which is used to indicate which UEs in the coverage area
  • the UE capability information needs to be reported, and the priority order of the UEs to report their UE capability information is required.
  • the broadcast may be to notify the UE by sending a system message.
  • the RRC layer of the UE determines, according to the received first request message, which UE capability information needs to be reported.
  • the UE sends the UE capability information to be sent to the PDCP layer in the form of a data packet, and then reports the data packet to the network side through the RRC message.
  • the part of the UE capability information is reported to the network side according to the priority order.
  • the network side receives the RRC message reported by the UE, and determines, according to the indication information in the RRC message, whether the UE needs to continue to report the UE capability information, and if necessary, sends a second request message to the UE, where the second request message is sent.
  • a UE capability information for indicating the message for the remaining portion may be included.
  • the remaining part of the UE capability information is sent to the PDCP layer, and is processed and reported to the network side; If the information is still greater than the maximum processing tolerance of the PDCP layer, the UE capability information is split and reported to the network side device in the same manner as the previous embodiment.
  • the network side After receiving all the partial UE capability information, the network side combines and saves the UE capability information, so as to provide services for the UE according to the UE capability information.
  • the network side after receiving the UE capability information, the network side sends the capability information to the MME.
  • the MME saves all the UE capability information of the UE
  • the network side may obtain the capability of the UE from the MME, so that the UE does not need to report again. Saved air interface resources.
  • the network side or the base station sends a broadcast message in the coverage area, and the broadcast message carries the indication information of the capability of the UE that is required to be reported by the UE, so that the UE that receives the broadcast message is ready for the UE capability.
  • the information when the request message sent by the network side is received again, reports the UE capability information to the network side.
  • the method of using the broadcast message can prevent the network side from carrying a large amount of indication information when the request message for reporting the capability of the UE is to be sent, and occupies a large amount of time-frequency resources.
  • the network side broadcasts the message periodically, and can avoid sending a UE capability request message carrying the indication information when a new UE accesses the network side, which further saves network overhead.
  • the embodiment provides a method for extending the processing tolerance of the PCDP layer, and the method includes: processing the data packet that can be processed by the PDCP layer.
  • the minimum number is set to 8188 octal octets, which expands the processing power of the PDCP layer, enabling PDCP to process data above 8188octets.
  • the specific extension may be that the size of the data packet that can be processed by the extended PDCP is limited to a value greater than 8188 octets, or expanded to an infinite size.
  • the method for extending the processing tolerance of the PCDP layer is not limited by the size of the capability information of the UE, and the maximum capability that the UE capability information exceeds the maximum processing capacity of the PDCP layer when the UE capability information is too large is avoided. In turn, an error is caused.
  • the present application further provides a user equipment UE.
  • the user equipment includes: a receiving unit 701, a processing unit 702, and a sending unit 703.
  • the receiving unit 701 is configured to acquire the UE capability information of the UE.
  • the UE capability information may be generated and stored in advance, and may also be generated by receiving a request for reporting the capability information of the UE.
  • the receiving unit 701 is further configured to receive, by the network side, the first request cancellation that needs to report the UE capability.
  • the first request message includes a system broadcast message and a dedicated or normal RRC message.
  • the processing unit 702 is configured to determine whether the UE capability information size exceeds a maximum tolerance that can be processed by the PDCP layer of the UE; if the maximum tolerance that can be processed by the PDCP layer of the UE is exceeded, the UE capability information is used. Splitting into at least two partial UE capability information, and each part of the UE capability information after splitting does not exceed the maximum tolerance that the PDCP layer can handle.
  • the processing unit 702 is further configured to split the UE capability information according to the RAT system division principle, or split according to the importance of the UE capability, or split according to the protocol version principle. Or, split according to the principle of reporting the number of times on the network side.
  • the processing unit 702 is further configured to send the split partial UE capability information to the PDCP layer of the UE by using a data packet, and process the split UE capability information data packet.
  • the sending unit 703 is configured to report the split capability information of the at least one part of the UE to the network side.
  • the processing unit 702 is further configured to detect whether the second request message fed back by the network side is received; if the second request message is detected, The UE transmits at least one of the remaining partial UE capability information to the network side by the sending unit 703.
  • processing unit 702 is further configured to split the UE capability information into at least one detailed UE capability information and coarse UE capability information corresponding thereto, where the detailed UE capability information is used to configure wireless for the network side. a parameter, the coarse UE capability information is used to indicate that the network side sends a third request message to the UE;
  • the sending unit 703 is further configured to report the coarse UE capability information to the network side, and if the third request message fed back by the network side according to the coarse UE capability information is received, Part or all of the detailed UE capability information corresponding to the coarse UE capability information is sent to the network side.
  • the sending unit 703 is further configured to report the part of the UE capability information according to the priority order. Give the network side.
  • the receiving unit 701 is further configured to receive and buffer all split partial UE capability information in a data packet form; the processing unit 702 is further configured to perform segmentation and cascading of all the partial UE capability information data packets. Processing, forming a data packet to be transmitted; the sending unit 703 is further configured to report the data transmission packet to the network side by using an RRC message.
  • the user equipment further includes a storage unit, where the storage unit is configured to store UE capability information, and a received request message.
  • the embodiment provides a base station, which is applied to the network side.
  • the base station includes: a receiving unit 801, a sending unit 803, and a processing unit 802. .
  • the sending unit 803 is configured to send, to the UE, a first request message that needs to report the UE capability
  • the receiving unit 801 is configured to receive a first RRC message that is sent by the UE according to the first request message, where the first RRC message carries at least one partial UE capability information that is formed after the UE capability information is split.
  • the processing unit 802 is configured to determine, according to the part of the UE capability message, whether the UE has remaining UE capability information, or whether the UE still needs to report partial UE capability information; if yes, generate a second request message. ; if no, generate a stop indication;
  • the sending unit 803 is further configured to send the second request message to the UE; or send the stop indication to the UE.
  • processing unit 802 is further configured to: if the partial UE capability information received by the network side is the coarse UE capability information, determine whether the detailed UE capability information corresponding to the coarse UE capability information is required; The detailed UE capability information generates a third request message; and the sending unit 803 sends the third request message to the UE.
  • the receiving unit 801 is further configured to receive all the RRC messages reported by the UE; after receiving all the RRC messages, the processing unit 802 combines the partial UE capability information corresponding to the RRC messages to generate a total UE of the UE.
  • the capability information is sent to the MME by the sending unit 803.
  • the base station provided by the application further includes a storage unit, configured to store UE capability information reported by the UE, and the generated request message.
  • each base station and terminal device includes: a processor, a transmission bus, a receiver, a transmitter, and a memory.
  • the functions of the receiver 903 and the transmitter 904 are respectively equivalent to the receiving unit 701 and the sending unit 703 in the foregoing apparatus embodiment, and are used for transmitting and receiving messages between the base station and the user equipment.
  • the function of the processor 901 is equivalent to the processing unit 702, wherein the processor 901 of the user equipment is mainly used for determining and splitting UE capability information, so as to ensure that the size of the UE capability information data packet transmitted to the PDCP layer does not exceed The maximum tolerance.
  • the functions of the receiver 1003 and the transmitter 1004 are respectively equivalent to the receiving unit 801 and the transmitting unit 803 in the foregoing apparatus embodiment, wherein the base station or the processor on the network side is configured to send the required information to the UE.
  • the first request message for reporting the UE capability information is received, and the RRC message of the UE is received, and it is determined whether the UE needs to report the UE capability information again. If the UE needs to report, the second request message is generated and sent to ensure that the base station or the network side can acquire the required UE. Capability information.
  • the processor may be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more programs for controlling the execution of the program of the present invention. integrated circuit.
  • CPU general purpose central processing unit
  • ASIC application-specific integrated circuit
  • Communication bus 902 or 1002 can include a path for communicating information between the components described above.
  • the receiver and transmitter include devices using any transceiver for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), etc. .
  • RAN Radio Access Network
  • WLAN Wireless Local Area Networks
  • the memory 905 or 1005 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or a device that can store information and instructions.
  • Other types of dynamic storage devices may also be Electrically Erasable Programmable Read-Only Memory (EEPROM), Compact Disc Read-Only Memory (CD-ROM) or other optical disk storage.
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • CD-ROM Compact Disc Read-Only Memory
  • Optical disc 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 capable of carrying or storing desired program code in the form of instructions or data structures and capable of Any other medium accessed by a computer, but is not limited thereto.
  • the memory can exist independently or be integrated with the processor. Wherein, the memory is used to store application code for executing the solution of the present invention, and is controlled by a processor
  • the user equipment of the present application is used to implement all or part of the function of the reporting method of the UE capability information in the foregoing embodiment, and the base station/network side device is used to implement one UE capability information receiving method in the foregoing embodiment. All or part of the function is implemented.
  • the terminal device described in this application includes a user equipment (abbreviation: UE), a user terminal, a client, and the like. Specifically, the terminal device further includes: a mobile phone, a tablet computer, a palmtop computer, or a mobile internet device.
  • UE user equipment
  • the terminal device further includes: a mobile phone, a tablet computer, a palmtop computer, or a mobile internet device.
  • a “unit” in the above embodiments may refer to an application-specific integrated circuit (ASIC), a circuit, a processor and memory that executes one or more software or firmware programs, integrated logic circuits, and/or the like.
  • a device that can provide the above functions.
  • the embodiment of the present invention further provides a computer storage medium for storing the computer software instructions used for the reporting method of the user equipment capability information shown in FIG. 9 or FIG. 10, which includes an embodiment for performing the foregoing method.
  • the transmission of feedback parameters can be implemented by executing a stored program.
  • embodiments of the present invention can be provided as a method, apparatus (device), or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the computer program is stored/distributed in a suitable medium, provided with other hardware or as part of the hardware, or in other distributed forms, such as over the Internet or other wired or wireless telecommunication systems.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

公开一种用户设备能力信息的上报方法及装置，所述方法包括：UE获取自身的UE能力信息；判断所述UE能力信息大小是否超过UE的PDCP层所能处理的最大容限；如果超过，则将UE能力信息拆分成至少两个部分UE能力信息，且拆分后每个部分UE能力信息不超过所述PDCP层所能处理的的最大容限；将所述拆分后的至少一个部分UE能力信息上报给网络侧。本方法在UE侧通过对UE能力信息大小进行判断和拆分，并且将拆分的UE能力信息分次上报给网络侧，进而避免了UE能力信息超过PDCP层所能处理的最大容限而引发错误，保证UE能力信息上报流程的正常运转。

Description

一种用户设备能力信息的上报方法及装置 技术领域
本发明涉及无线通讯技术领域，特别是涉及一种用户设备能力信息的上报方法及装置。
背景技术
在LTE(Long Time Evolution，长期演进)系统中，用户设备(User Equipment，UE)和基站(eNB)之间的信息传输通过LTE协议实现，如图1所示为LTE空中接口协议栈的示意图，其中，UE侧由上至下依次包括NAS(Non-access stratum，非接入)层，RRC(Radio Resource Control，无线资源控制)层，PDCP(Packet Data Convergence Control，分组数据汇聚控制)层，RLC(Radio Link Control，无线链路控制)层，MAC(Medium Access Control，媒质接入控制)层和PHY(Physical Layer，物理)层。RRC层的主要服务和功能包括广播和系统相关的非接入层(NAS)信息，移动性管理，寻呼以及建立、重建、维持和释放UE和eNB之间RRC连接等；在UE侧，RRC层产生的数据包需要先经过PDCP层的处理，然后再向其他协议层如RLC层、MAC层和PHY层传输。PDCP层对于RRC层等上层提供的服务内容包括针对控制面和用户面的数据传输，对IP数据报头进行压缩、加密以及完整性保护等。
在需要PDCP层处理的RRC信息中一类重要的信息是UE能力信息，所述UE能力信息是指UE自身具备的无线接入能力和能够支持的无线功能特性，用于为网络侧在对UE做无线配置时提供参考，当网络侧需要获取UE能力信息时，会向处于连接态的UE发送UE能力请求(UE Capability Enquiry)消息，UE收到该能力请求消息后，将UE自身能力信息上报给网络侧，以使网络侧了解UE的能力，进而更好地为UE提供服务。
但是在数据包处理过程中PDCP层能够处理的数据包容量有限，例如在LTE协议中PDCP层能够处理的数据包的最大容限是8188octets，而随着LTE技术不断演进，越来越多的特性比如LAA(licensed-assisted access，授权辅助接入)、Massive CA被引入，导致UE需要上报的能力信息越来越多，所以UE侧的RRC层生成的UE能力信息也会越来越大，甚至超过8188octets。按照现有流程，当RRC层的数据包传输到PDCP层的时候，如果超过PDCP层处理数据包的最大容限，会导致PDCP层无法 处理，引发错误，进而影响UE能力信息的上报。
发明内容
本申请实施例中提供了一种用户设备能力信息的上报方法及装置，以解决当RRC层数据包传输到PCDP层的时候，由于数据包大小超过PDCP层能够处理的最大容限而引发错误的问题。
第一方面，本申请实施例提供了一种用户设备UE能力信息的上报方法，所述方法包括：UE获取自身的UE能力信息；判断所述UE能力信息大小是否超过UE的PDCP层所能处理的最大容限；如果超过所述UE的PDCP层所能处理的最大容限，则将所述UE能力信息拆分成至少两个部分UE能力信息，且拆分后每个部分UE能力信息不超过所述PDCP层所能处理的最大容限；将所述拆分后的至少一个部分UE能力信息上报给网络侧。
本方面提供的方法，UE侧的PDCP层通过对生成的UE能力信息进行判断和拆分，将超过PDCP层所能处理的最大容限的UE能力信息进行拆分，使其小于PDCP层的最大处理容限，进而避免了UE能力信息过大而引发的错误，保证UE能力信息上报流程的正常运转。
结合第一方面，在第一方面第一种实现中，将所述拆分后的至少一个部分UE能力信息上报给网络侧之前还包括：所述UE接收网络侧发送的需要上报UE能力的第一请求消息，所述第一请求消息包括系统广播消息和无线资源控制RRC消息。
结合第一方面，在第一方面第二种实现中，将所述UE能力信息拆分成至少两个部分UE能力信息包括：将所述UE能力信息按照RAT系统划分原则进行拆分，或者，按照UE能力的重要性进行拆分，或者，按照UE能力的上报优先级顺序进行拆分，或者，按照协议版本先后原则进行拆分，或者，按照上报网络侧次数最少原则进行拆分。
结合第一方面，在第一方面第三种实现中，将所述拆分后的至少一个部分UE能力信息上报给网络侧之后还包括：UE检测是否接收到所述网络侧反馈的第二请求消息；如果检测到所述第二请求消息，则所述UE将剩余的部分UE能力信息中的至少一个发送给所述网络侧。所述UE第二次向网络侧上报部分UE能力信息之后，如果还接收到网络侧下发的第三请求消息，则再继续上报部分UE能力信息，直到UE将所有拆分的部分UE能力信息上报给网络侧为止，或者，网络侧给UE下发停止上报UE能力信息的指示信息为止。
结合第一方面，在第一方面第四种实现中，将所述UE能力信息拆分成至少两个部分UE能力信息包括：将所述UE能力信息拆分成至少一个详细UE能力信息和与其对应的粗略UE能力信息，其中，一个粗略UE能力信息可以对应多个详细UE能力信息，所述详细UE能力信息用于为所述网络侧在给所述UE配置无线参数时提供参考依据，所述粗略UE能力信息用于指示所述网络侧向所述UE发送第三请求消息；所述将所述拆分后的至少一个部分UE能力信息上报给网络侧包括：将所述粗略UE能力信息上报给所述网络侧；如果接收到所述网络侧根据所述粗略UE能力信息反馈的所述第三请求消息，则将所述粗略UE能力信息所对应的详细UE能力信息中的部分或全部发送至所述网络侧。
在本方面的实现中，通过先将UE能力信息拆分成详细UE能力信息和粗略UE能力信息，再上报粗略UE能力信息给网络侧，根据网络侧的反馈决定是否上报与所述粗略UE能力信息对应的详细UE能力信息，以及上报哪些详细UE能力信息。采用本实现方式一方面能够避免UE能力信息过大的时候一次性发送超过PDCP层处理能力；另一方面，UE可以根据网络侧需求上报某部分详细UE能力信息，可以避免上报所有详细UE能力信息，进而节省空口无线资源。
结合第一方面第二种实现，在第一方面第五种实现中，将所述拆分后的至少一个部分UE能力信息上报给网络侧包括：对所有拆分的部分UE能力信息进行排序；如果所述第一请求消息中携带所述部分UE能力信息上报的优先级顺序，则按照所述优先级顺序将所述部分UE能力信息上报给所述网络侧。
结合第一方面以及第一方面第五种实现中的任意一种，在第一方面第六种实现中，将所述UE能力信息拆分成至少两个部分包括：所述UE的RRC层或PDCP层将所述UE能力信息拆分成至少两个部分。此外，还包括UE的处理器或其它层对超过其PDCP层最大处理容限的数据包进行拆分。
结合第一方面以及第一方面第五种实现中的任意一种，在第一方面第七种实现中，将所述拆分后的至少一个部分UE能力信息上报给网络侧包括：所述UE的RLC层以数据包形式接收并缓冲所有拆分部分UE能力信息；对所有所述部分UE能力信息的数据包进行分割级联处理，形成待传输的数据包；将所述待传输数据包通过RRC消息上报给所述网络侧。在本方面的实现中，在UE侧将PDCP层处理后的所有部分UE能力信息进行合并，然后一次性地上报给基站或网络侧设备，由于只需要上报一次，进而避免了多次上报导致与网络的信令交互频繁，节约网络开销。
结合第一方面以及第一方面第七种实现中的任意一种，在第一方面第八种实现 中，每个所述部分UE能力信息中还包括指示信息，所述指示信息用于指示以下任意一种内容：是否UE有剩余的部分UE能力信息，所述剩余的部分UE能力信息需要上报的次数，当前上报的部分UE能力信息在所有部分UE能力信息中的顺序。本方面的实现通过在UE发送的RRC消息中携带指示信息，以使得网络侧能够获取UE侧的部分UE能力信息状况，以决定是否发送UE能力信息的请求消息给UE。
第二方面，本申请实施例提供了一种UE能力信息接收方法，应用于网络侧设备，所述方法包括：网络侧向UE发送需要上报UE能力信息的第一请求消息；接收所述UE根据所述第一请求消息反馈的第一RRC消息，所述第一RRC消息中携带有UE能力信息经过拆分后形成的至少一个部分UE能力信息；根据所述部分UE能力消息，判断所述UE是否还有剩余部分UE能力信息，或者，是否还需要所述UE上报部分UE能力信息；如果是，则生成并发送第二请求消息给所述UE；如果否，则生成停止指示，并将所述停止指示发送所述UE，或者，不再发送任何指示给所述UE。本方面提供的方法，网络侧通过向UE下方请求消息以指示所述UE上报UE能力信息，以及上报哪些UE能力信息，还包括指示UE停止上报等，进而实现了与UE之间的能力信息的上报过程。
结合第二方面，在第二方面第一种实现中，如果所述网络侧接收到的部分UE能力信息是粗略UE能力信息，则判断是否需要与所述粗略UE能力信息对应的详细UE能力信息；如果需要所述详细UE能力信息，则生成并发送第三请求消息给所述UE，以使所述UE继续上报详细UE能力信息。
结合第二方面，在第二方面第二种实现中，所述方法还包括：网络侧接收所述UE上报的RRC消息；将所有所述RRC消息所对应的部分UE能力信息进行合并处理，生成所述UE的总UE能力信息；将所述合并后的总UE能力信息发送给MME，以使所述MME保存所述UE能力信息之后，网络侧可以直接从MME中获得UE的能力信息，避免UE再次上报，进而节省了网络空口资源。
结合第二方面以及第二方面第二种实现中的任意一种，在第二方面第三种实现中，所述第一请求消息包括系统广播消息和无线资源控制RRC消息，所述第一请求消息用于通知所述UE需要选择上报的UE能力信息，以使UE能在接收到第一请求消息时获知上报给网络侧哪些UE能力信息。
结合第二方面以及第二方面第二种实现中的任意一种，在第二方面第四种实现中，所述第一请求消息中还包括指示所述UE上报部分UE能力信息的优先级顺序，以使所述UE按照所述优先级顺序上报。
第三方面，本申请实施例还提供了一种扩展PCDP层处理容限的方法，方法包括：将UE侧和/或网络侧的PDCP层所能处理的数据包的的最大容限值设置为不小于8188octets。即扩展PDCP层所能处理的数据包大小，将其扩展为大于8188octets的数值，进一步地，将PDCP层的处理容限扩展为无线大小。本方面通过提升PDCP层的处理能力，进而能够解决由于PDCP层接收的数据包过大导致无法处理，出现错误的问题。
第三方面，本申请实施例还提供了一种用户设备UE，包括：接收单元，处理单元和发送单元，所述接收单元，用于获取自身的UE能力信息；所述处理单元，用于判断所述UE能力信息大小是否超过UE的PDCP层所能处理的最大容限；如果超过所述UE的PDCP层所能处理的最大容限，则将所述UE能力信息拆分成至少两个部分UE能力信息，且拆分后每个部分UE能力信息不超过所述PDCP层所能处理的的最大容限；所述发送单元，用于将所述拆分后的至少一个部分UE能力信息上报给网络侧。
本方面提供的方法，通过增加UE的RRC层对UE能力信息大小的判断和分割功能，以及在UE能力信息过大的时候分次上报的机制，进而避免传输到PDCP层的数据包超过其能够处理的最大容限，影响UE能力信息的上报流程。
此外，所述UE还用于实现上述第一方面中的各种实现。
第四方面，本申请实施例还提供了一种基站，应用于网络侧，所述基站包括：发送单元，接收单元和处理单元，所述发送单元，用于向UE发送需要上报UE能力信息的第一请求消息；所述接收单元，用于接收所述UE根据所述第一请求消息反馈的第一RRC消息，所述第一RRC消息中携带有UE能力信息经过拆分后形成的至少一个部分UE能力信息；所述处理单元，用于根据所述部分UE能力消息，判断所述UE是否还有剩余部分UE能力信息，或者，是否还需要所述UE上报部分UE能力信息；如果是，则生成第二请求消息；所述发送单元，还用于发送所述第二请求消息给所述UE。
此外，所述基站还用于实现上述第二方面中的各种实现。
第五方面，本申请实施例还提供了一种移动性管理实体MME，用于接收和保存网络侧发送的全部或者部分UE能力信息，以及当所述网络侧需要UE的能力信息时，将所述保存的UE能力信息发送给所述网络侧，从而避免UE再次上报UE能力信息，节约了空口资源。
第六方面，本申请实施例还提供了一种用户设备，包括：接收机，处理器和发送 机，所述接收机，用于获取自身的UE能力信息；所述处理器，用于判断所述UE能力信息大小是否超过UE的PDCP层所能处理的最大容限；如果超过所述UE的PDCP层所能处理的最大容限，则将所述UE能力信息拆分成至少两个部分UE能力信息，且拆分后每个部分UE能力信息不超过所述PDCP层所能处理的的最大容限；所述发送机，用于将所述拆分后的至少一个部分UE能力信息上报给网络侧。
结合第六方面，在第六方面第一种实现中，所述接收机还用于接收网络侧发送的需要上报UE能力的第一请求消息，所述第一请求消息包括系统广播消息和RRC消息。
结合第六方面，在第六方面第二种实现中，所述处理器还用于将所述UE能力信息按照RAT系统划分原则进行拆分，或者，按照UE能力的重要性进行拆分，或者，按照协议版本先后原则进行拆分，或者，按照上报网络侧次数最少原则进行拆分。
结合第六方面，在第六方面第三种实现中，所述处理器，还用于检测是否接收到所述网络侧反馈的第二请求消息；所述发送机，还用于如果检测到所述第二请求消息，则所述UE将剩余的部分UE能力信息中的至少一个发送给所述网络侧。
结合第六方面，在第六方面第四种实现中，所述处理器还用于将所述UE能力信息拆分成至少一个详细UE能力信息和与其对应的粗略UE能力信息，所述详细UE能力信息用于为所述网络侧给所述UE配置无线参数时提供参考，所述粗略UE能力信息用于指示所述网络侧向所述UE发送第三请求消息；所述发送机，还用于将所述粗略UE能力信息上报给所述网络侧；以及，如果接收到所述网络侧根据所述粗略UE能力信息反馈的所述第三请求消息，则将所述粗略UE能力信息所对应的详细UE能力信息的部分或全部发送至所述网络侧。
结合第六方面第二种实现，在第六方面第五种实现中，所述处理器，还用于对所有拆分的部分UE能力信息进行排序；所述发送机，还用于如果所述第一请求消息中携带所述部分UE能力信息上报的优先级顺序，则按照所述优先级顺序将所述部分UE能力信息上报给所述网络侧。
结合第六方面以及第六方面第五种实现中的任意一种，在第六方面第七种实现中，所述UE的RRC层或PDCP层将所述UE能力信息拆分成至少两个部分。
结合第六方面以及第六方面第五种实现中的任意一种，在第六方面第八种实现中，所述接收机，还用于以数据包形式接收并缓冲所有拆分部分UE能力信息；所述处理器，还用于对所有所述部分UE能力信息的数据包进行分割级联处理，形成待传输的数据包；所述发送机，还用于将所述待传输数据包通过RRC消息上报给所述网 络侧。
第七方面，本申请实施例还提供了一种基站，应用于网络侧，包括：发送机，接收机和处理器，所述发送机，用于向UE发送需要上报UE能力信息的第一请求消息；所述接收机，用于接收所述UE根据所述第一请求消息反馈的第一RRC消息，所述第一RRC消息中携带有UE能力信息经过拆分后形成的至少一个部分UE能力信息；所述处理器，用于根据所述部分UE能力消息，判断所述UE是否还有剩余部分UE能力信息，或者，是否还需要所述UE上报部分UE能力信息；如果是，则生成第二请求消息；所述发送机，还用于发送所述第二请求消息给所述UE。
结合第七方面，在第七方面第一种实现中，所述处理器，还用于如果所述网络侧接收到的部分UE能力信息是粗略UE能力信息，则判断是否需要与所述粗略UE能力信息对应的详细UE能力信息；如果需要所述详细UE能力信息，则生成第三请求消息；所述发送机，还用于发送所述第三请求消息给所述UE。
结合第七方面，在第七方面第二种实现中，所述接收机，还用于接收所述UE上报的RRC消息；所述处理器，还用于将所有所述RRC消息所对应的部分UE能力信息进行合并处理，生成所述UE的总UE能力信息；所述发送机，还用于将所述合并后的总UE能力信息发送给MME。
结合第七方面以及第七方面第二种实现中的任意一种，在第七方面第三种实现中，所述第一请求消息包括系统广播消息和RRC消息，所述第一请求消息用于通知所述UE需要选择上报的UE能力信息。
结合第七方面以及第七方面第二种实现中的任意一种，在第七方面第四种实现中，所述第一请求消息中还包括指示所述UE上报部分UE能力信息的优先级顺序，以使所述UE按照所述优先级顺序上报。
第八方面，本申请实施例还提供一种计算机存储介质，其中，该计算机存储介质可存储有程序，该程序执行时可实现本申请提供一种用户设备能力信息的上报方法的各实现方式中的部分或全部步骤。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1为本申请实施例提供的一种LTE空中接口协议栈示意图；
图2为本申请实施例提供的一种LTE网络架构示意图；
图3为本申请实施例提供的一种UE能力信息的上报方法的流程示意图；
图4为本申请实施例提供的一种UE能力信息的上报方法的信令流程图；
图5为本申请实施例提供的另一种UE能力信息的上报方法的信令流程图；
图6为本申请实施例提供的又一种UE能力信息的上报方法的信令流程图；
图7为本申请实施例提供的一种UE的结构框图；
图8为本申请实施例提供的一种基站的结构框图；
图9为本申请实施例提供的一种UE的硬件结构示意图；
图10为本申请实施例提供的一种基站的硬件结构示意图。
具体实施方式
为了使本技术领域的人员更好地理解本发明中的技术方案，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。
本申请提供的技术方案主要应用于各种无线通信系统，例如LTE系统，UMTS,类似LTE系统，或者5G系统，其中，上述无线通信系统的具体架构不做限定。本申请以图2所示的LTE网络架构为例，介绍本申请技术方案的应用场景。图2所示的LTE网络架构包括：至少一个MME(Mobility Management Entity，移动管理实体)或者S-GW(Serving Gateway，服务网关)，至少一个基站(eNodeB，缩写eNB)，至少一个用户设备(User Equipment，UE)或E-UTRAN(Evolved UMTS Terrestrial Radio Access Network，演进的UMTS陆地无线接入网)。其中，每个基站也称为接入设备，用于与UE进行通信。MME为移动管理实体，用于负责UE的定位和寻呼过程，此外，MME还用于信令处理等。MME/S-GW与eNB之间通过S1通信接口实现通信，两两eNB之间通过X2通信接口实现通信。
如图1所示，在UE侧的RRC层产生的UE能力信息的数据包经过PDCP层处理之后，自上而下经过所述UE的各个层，最后经过PHY层之后发送至eNB，eNB的PHY层接收UE发送的信息或者数据包之后，按照LTE空口协议栈的结构层级从下到上，对接收的信息进行处理，当UE能力信息或者数据包经过UE或者eNB的PDCP层时，如果大于PDCP层所能够处理的最大容限8188octets，则会引发错误，进而影响UE能力信息的数据包的传输。
本申请提供的一种用户设备UE能力信息的上报方法，用于解决当RRC层的UE能力信息的数据包传输到PCDP层的时候，由于超过PDCP层能够处理的最大容限而引发错误的问题。
本申请所述的UE能力信息是指UE自身具备的无线接入能力和能够支持的无线功能特性。
实施例一
如图3所示，一种用户设备UE能力信息的上报方法，所述方法包括如下步骤：
步骤S301：UE获取自身的UE能力信息。
可选的，当网络侧需要UE的能力信息时，向与其处于连接态的UE发送第一请求消息，也称UE Capbility Enquiry消息，或者RRC消息。其中，所述第一请求消息可以是系统广播消息，还可以是专用RRC消息。所述第一请求消息用于通知所述UE需要选择上报的UE能力信息。UE接收到该消息后，生成UE自身能力信息，使UE获得自身的UE能力信息。所述UE能力信息还可以是UE固定的能力信息，存储在UE侧，当网络侧需要该UE的能力信息时，将其上报。
步骤S302：判断所述UE能力信息大小是否超过UE的PDCP层所能处理的最大容限。
一般的，在UE的PDCP层能够处理的数据包的最大容限是8188octets，即PDCP SDU最大为8188octets。步骤S302中，UE判断其生成的UE能力信息是否超过8188octets。
其中，octet是一种计算机语言，意思是因特网标准使用八位组。在二进制数字概念中，1byte(字节)＝8bit(位)，进一步地，本申请实施例中的octet可定义为1octet＝8bit。
步骤S303：如果超过所述UE的PDCP层所能处理的最大容限，则将所述UE能力信息拆分成至少两个部分UE能力信息，且拆分后每个部分UE能力信息不超过所述PDCP层所能处理的的最大容限。
具体地，如果判断UE的能力信息超过8188octets，则将所述UE能力信息按照RAT(Radio Access Technology，无线接入技术)系统划分原则进行拆分，或者，按照UE能力的重要性进行拆分，或者，按照UE能力的上报优先级进行拆分，或者，按照协议版本先后原则进行拆分，或者，按照上报网络侧次数最少原则进行拆分。无论才有哪种拆分方法，都保证拆分后的每个部分UE能力信息不超过所述PDCP层所能处理的的最大容限。
还可以是UE的RRC层直接拆分并生成第一部分UE能力信息(英文：the First part UE Capability Information)，第二部分UE能力信息，第三部分UE能力信息等。本申请中可以通过UE的RRC层对UE能力信息进行拆分，还可以是PDCP层拆分，或者UE的其它处理单元执行。如果是UE的RRC层进行拆分，那么UE先将拆分后的UE能力信息封装成若干个数据包，在将每个数据包发送给PDCP层。
步骤S304：将所述拆分后的至少一个部分UE能力信息上报给网络侧。
具体地UE将拆分后的部分UE能力信息通过RRC消息的方式上报给网络侧，本申请的实施例提供了各种UE上报UE能力信息的方式，可选的，其中一种上报UE能力信息的过程如下：
如图4所示，用户设备UE接收到第一请求消息之后，对自身UE能力信息进行判断和拆分(S402)，并将拆分后的第一部分UE能力信息通过第一RRC消息的方式上报给基站/网络侧(S403)，可选的，所述第一RRC消息中还包括指示信息，该指示信息用于指示或告知基站/网络侧是否有剩余部分UE能力信息需要上报，和/或还剩余几部分UE能力信息，和/或剩余的是哪几部分UE能力信息，和/或总共将UE能力信息拆分成几部分，当前上报的是第几部分，或者当前上报的第一部分UE能力信息占总UE能力信息的比例等。
如果基站/网络侧接收到第一RRC消息后，根据其中包含的指示信息，UE侧还剩余部分UE能力信息，或者UE能力信息未全部上报，则基站/网络侧生成第二请求(the Second UE Capbility Enquiry)消息，并将该第二请求消息发送给UE(S404)，其中，该第二请求消息用于指示UE继续上报部分UE能力信息。UE接收到第二请求消息之后将拆分的第二部分UE能力信息通过第二RRC消息上报给基站/网络侧(S405)，并且所述第二RRC消息中也包含指示信息，用于告知基站是否还有剩余UE能力信息，如果指示UE已经将所有UE能力信息都上报给基站/网络侧，则基站/网络侧对接收的所有部分UE能力信息进行合并(S406)，并且保存合并后的UE能力信息，以便后续根据UE能力信息为UE提供服务。
可选的，在步骤S403中，如果UE给基站/网络侧发送的第一RRC消息中不包含指示信息，则基站/网络侧需要判断是否需要UE继续上报UE能力信息。此外，基站/网络侧如果判断已经接收了所有UE发送的UE能力信息，或者不需要UE发送UE能力信息时，会向UE下发停止指示，使UE停止继续上报UE能力信息的动作，或者不再发送任何指示给所述UE。
另外，在步骤S406之后，网络侧接收UE能力信息以后，将UE能力信息发送 给移动管理实体(MME)保存。MME保存所述UE的所有能力信息后，在UE返回空闲态后，再次进入连接态时，所述网络侧可以从MME中获得所述UE的能力，从而不需要UE再次上报UE能力信息，节省了空口资源。
具体的，基站/网络侧可以将所有UE能力信息合并后发送给MME保存，或者每次接收到来自所述UE上报的部分UE能力信息时，就将该部分UE能力信息直接转发给MME设备，由MME设备进行合并以及保存。
本实施例提供的方法，UE侧的PDCP层通过对生成的UE能力信息进行判断和拆分，将超过PDCP层所能处理的最大容限的UE能力信息进行拆分，使其小于PDCP层的最大处理容限，进而避免了UE能力信息过大而引发的错误，保证UE能力信息上报流程的正常运转。
实施例二
如图5所示，提供了另一种UE能力信息的上报方法，该方法的第一个步骤S501和第二个步骤S502分别与实施例一中的S401和S402相同。
可选的，在步骤S502中，UE的RRC层或PDCP层将UE的能力信息平均地拆分成若干个部分UE能力信息，且每个拆分后的部分UE能力信息不超过PDCP层的最大处理容限。
步骤S503：拆分后的部分UE能力信息经过PDCP层处理后，对所有处理后的部分UE能力信息进行合并，可选的，在RLC层对这些处理后的部分UE能力信息进行分割级联处理或者在MAC层经过复用之后，合并为一个UE能力信息，并将其封装成RRC消息。
步骤S504：将该封装后的RRC消息一次性地上报给基站/网络侧设备，进一步地，所述RRC消息中携带UE的总能力信息，还包括指示在UE无剩余部分UE能力信息的信息。
步骤S505：基站/网络侧设备接收该RRC消息，并按照LTE空中接口协议栈的规定将UE能力信息由下自上传输，在基站/网络侧设备的PDCP层判断所述UE能力信息是否超过其所能处理的最大容限，即8188octets，如果超过所述最大容限，则将UE能力信息拆分成至少两个部分UE能力信息，以保证PDCP层能够正常处理，避免出现错误。
步骤S506：当基站/网络侧设备的PDCP层处理完所有部分UE能力信息之后，在将这些处理后的部分UE能力信息进行合并和保存。可选的，基站/网络侧设备将合并后的总UE能力信息发送给MME。
本实施例提供的方法，在UE侧将PDCP层处理后的部分UE能力信息进行合并，然后一次性地上报给基站/网络侧设备，由于只需要上报一次，避免了多次上报过程中产生的与网络的信令交互，节约网络开销。
实施例三
在本实施中，如图6所示，步骤S601与前述实施例中的第一个步骤相同。
步骤S602：UE判断其自身的UE能力信息如果大于PDCP层所能处理的最大容限时，将所述UE能力信息拆分成至少一个详细UE能力信息和与其对应的粗略UE能力信息，所述详细UE能力信息用于为所述网络侧配置无线参数，所述粗略UE能力信息用于指示所述网络侧向所述UE发送第三请求消息。
进一步地，所谓粗略UE能力信息，是指网络侧能根据该粗略的UE能力信息能够获得UE具有某些能力，但不能确定UE的具体能力信息，例如，粗略UE能力信息为UE支持载波聚合CA(Carrier Aggregation，载波聚合)能力时，网络侧只能根据该粗略UE能力信息获得UE可能支持CA，但不能获知该UE支持哪些带宽(band)或载波进行聚合，此时需要UE再次上报详细的UE能力信息，以便网络侧为UE配置多载波聚合功能。再另一例子中，如果该粗略UE能力信息为UE支持LTE协议版本10能力时，网络侧只能根据该粗略UE能力信息获得UE可能支持CA，或Relay(中继)或CoMP(Coordinated Multiple Points，多点协作技术)等版本10的特性，但不知道UE支持具体哪些版本10的特性等，此时需要UE再次上报详细的UE能力信息。所谓粗略的能力信息包括按照某种分类方式，只能使网络侧获取总体UE功能的信息，不包括具体的UE能力信息。
进一步地，拆分UE能力信息时，可以将重要或者必要的UE能力信息划分为详细UE能力信息部分，相对次要的UE能力划分在粗略UE能力信息当中；或者按照LTE协议版本先后，将早先版本的信息划分在详细UE能力信息，将后期较新版本的能力划分为粗略UE能力信息；或者如果按照RAT划分，则将当前RAT的能力信息划分为详细UE能力信息，其它RAT的能力信息作为粗略UE能力信息等。
步骤S603：划分后，首先将所述粗略UE能力信息上报给所述网络侧设备；
步骤S604：基站/网络侧设备接收所述粗略UE能力信息，并判断是否需要UE上报详细UE能力信息，如果需要，则生成第三请求消息，并将第三请求消息发送给所述UE。
步骤S605：如果UE接收到所述网络侧根据所述详细UE能力信息反馈的第三请求消息，则将所述粗略UE能力信息所对应的详细UE能力信息的部分或全部发送至 所述网络侧设备。
可选的，如果所述粗略UE能力信息对应多个详细UE能力信息，则UE可根据网络侧的指示，分多次上报详细UE能力信息。UE上报给网络侧的详细UE能力信息中也可以携带指示信息，用于告知网络侧是否还有剩余的详细UE能力信息，剩余哪些详细UE能力信息等内容。
步骤S606：基站/网络侧设备将接收的粗略UE能力信息和详细UE能力信息进行合并和保存，以及发送给移动管理实体MME，该步骤与前述实施例中的步骤S406和S506相同，所以不再赘述。
本实施例与上述实施例一和实施例二相比，将UE自身的UE能力信息划分为两部分，一部分为详细UE能力信息，另一部分为粗略UE能力信息，并且所述详细UE能力信息与粗略UE能力信息相对应，所以UE在上报时根据网络侧要求，先上报粗略UE能力信息，如果需要详细UE能力信息，则继续上报与该粗略UE能力信息对应的详细UE能力信息，一方面，避免UE能力信息过大的时候一次性发送超过PDCP层处理能力；另一方面，可以按照网络需要上报某部分详细能力信息，可能不必上报所有详细能力信息，进而节省空口无线资源。
实施例四
本实施例是对前述实施例中的第一个步骤进行改进，具体地，改进之处在于，
第一步，基站或网络侧设备向其覆盖范围内的所有UE广播第一请求消息(UE Capability Enquiry)，所述第一请求消息中携带指示信息，用于指示所述覆盖范围内的哪些UE需要上报UE能力信息，以及不同的UE上报其UE能力信息的优先级顺序。可选的，所述广播可以是通过发送系统消息来通知UE；第二步，UE的RRC层根据收到的第一请求消息，判断自己需要上报哪些UE能力信息。
第三步，UE将所要上报的UE能力信息作为通过数据包形式先发送给PDCP层，再将所述数据包通过RRC消息上报给网络侧。
进一步地，如果所述第一请求消息中携带所述部分UE能力信息上报的优先级顺序，则按照所述优先级顺序将所述部分UE能力信息上报给所述网络侧。
第四步，网络侧接收UE上报的RRC消息，根据RRC消息中的指示信息确定是否需要UE继续上报UE能力信息，如果需要，则下发第二请求消息给UE，其中该第二请求消息中可以包括用于指示该消息针对剩余部分的UE能力信息。
第五步，如果UE收到针对剩余部分UE能力信息的第二请求消息，则将剩余部分UE能力信息发送给PDCP层，经过处理后上报给所述网络侧；如果剩余部分能力 信息仍然大于PDCP层的最大处理容限，8188octets，则采用与前述实施例相同的方法拆分UE能力信息，并分次上报给网络侧设备。
第六步，网络侧接收所有的部分UE能力信息以后，对这些UE能力信息进行合并和保存，以便后续根据UE能力信息为UE提供服务。
可选的，第七步，网络侧接收UE能力信息以后，将能力信息发送给MME。MME保存所述UE的所有的UE能力信息后，在UE返回空闲态后，再次进入连接态时，所述网络侧可以从所述MME中获得所述UE的能力，从而不需要UE再次上报，节省了空口资源。
在本实施例中，网络侧或基站通过在其覆盖范围内发送广播消息，所述广播消息中携带需要UE上报的UE能力的指示信息，以使接收到广播消息的UE准备好各自的UE能力信息，当再次接收到网络侧下发的请求消息时，将各自的UE能力信息上报给网络侧。采用这种广播消息的方式，可以避免网络侧在下发需要上报UE能力的请求消息时携带大量的指示信息，占用大量时频资源。此外，网络侧周期性地广播消息，可以避免每个当有新的UE接入网络侧时，都发送携带指示信息的UE能力请求消息，进一步地节省了网络开销。
实施例五
为了避免UE侧或者网络侧获取的UE能力信息超过其能够处理的最大容限，本实施例提供了一种扩展PCDP层处理容限的方法，方法包括：将PDCP层所能处理的数据包的最小数量设置为8188八进制octets，即对PDCP层的处理能力进行扩展，使PDCP能够处理8188octets以上的数据。
具体的扩展方式可以是，扩大PDCP所能处理的数据包大小限制为某个大于8188octets的数值，或者扩展为无限大小等。
本实施例提供的拓展PCDP层处理容限的方法，拓展后不受UE能力信息大小的限制，避免UE能力信息过大的时候，一次性发送UE能力信息超过PDCP层所能处理的最大容限进而引发错误。
实施例六
对应于上述方法的实施例，本申请还提供了一种用户设备UE，如图7所示，该用户设备包括：接收单元701，处理单元702和发送单元703。
接收单元701，用于获取自身的UE能力信息；所述UE能力信息可以预先生成并存储，还可以通过接收上报UE能力信息的请求后再生成。
其中，接收单元701，还用于接收网络侧发送的需要上报UE能力的第一请求消 息，所述第一请求消息包括系统广播消息和专用或普通RRC消息。
处理单元702，用于判断所述UE能力信息大小是否超过UE的PDCP层所能处理的最大容限；如果超过所述UE的PDCP层所能处理的最大容限，则将所述UE能力信息拆分成至少两个部分UE能力信息，且拆分后每个部分UE能力信息不超过所述PDCP层所能处理的的最大容限。
具体地，所述处理单元702，还用于将所述UE能力信息按照RAT系统划分原则进行拆分，或者，按照UE能力的重要性进行拆分，或者，按照协议版本先后原则进行拆分，或者，按照上报网络侧次数最少原则进行拆分。
处理单元702，还用于将所述拆分后的部分UE能力信息通过数据包发送给所述UE的PDCP层，处理所述拆分的UE能力信息数据包。
发送单元703，用于将所述拆分后的至少一个部分UE能力信息上报给网络侧。
进一步地，在UE第一次上报完部分UE能力信息之后，所述处理单元702还用于检测是否接收到所述网络侧反馈的第二请求消息；如果检测到所述第二请求消息，则所述UE通过发送单元703将剩余的部分UE能力信息中的至少一个发送给所述网络侧。
进一步地，处理单元702，具体还用于将所述UE能力信息拆分成至少一个详细UE能力信息和与其对应的粗略UE能力信息，所述详细UE能力信息用于为所述网络侧配置无线参数，所述粗略UE能力信息用于指示所述网络侧向所述UE发送第三请求消息；
所述发送单元703，还用于将所述粗略UE能力信息上报给所述网络侧；以及，如果接收到所述网络侧根据所述粗略UE能力信息反馈的所述第三请求消息，则将所述粗略UE能力信息所对应的详细UE能力信息的部分或全部发送至所述网络侧。
可选的，如果UE接收的基站/网络侧发送的请求消息中指示发送部分UE能力信息的优先级顺序，则发送单元703，还用于按照所述优先级顺序将所述部分UE能力信息上报给所述网络侧。
可选的，所述接收单元701，还用于以数据包形式接收并缓冲所有拆分部分UE能力信息；处理单元702，还用于对所有所述部分UE能力信息的数据包进行分割级联处理，形成待传输的数据包；发送单元703，还用于将所述带传输数据包通过RRC消息上报给所述网络侧。
此外，所述用户设备还包括存储单元，所述存储单元用于存储UE能力信息，以及接收的请求消息。
在另一个实施例中，对应于前述的用户设备，本实施例提供了一种基站，应用于网络侧，如图8所示，所述基站包括：接收单元801，发送单元803和处理单元802。
发送单元803，用于向UE发送需要上报UE能力的第一请求消息；
接收单元801，用于接收所述UE根据所述第一请求消息反馈的第一RRC消息，所述第一RRC消息中携带有UE能力信息经过拆分后形成的至少一个部分UE能力信息；
处理单元802，用于根据所述部分UE能力消息，判断所述UE是否还有剩余部分UE能力信息，或者，是否还需要所述UE上报部分UE能力信息；如果是，则生成第二请求消息；如果否，则生成停止指示；
发送单元803，还用于发送所述第二请求消息给所述UE；或者，将所述停止指示发送所述UE。
进一步地，所述处理单元802，还用于如果所述网络侧接收到的部分UE能力信息是粗略UE能力信息，则判断是否需要与所述粗略UE能力信息对应的详细UE能力信息；如果需要所述详细UE能力信息，则生成第三请求消息；以及，发送单元803发送所述第三请求消息给所述UE。
进一步地，接收单元801还用于接收所述UE上报的所有RRC消息；处理单元802接收所有RRC消息后，将这些RRC消息所对应的部分UE能力信息进行合并处理，生成所述UE的总UE能力信息；并通过发送单元803将合并后的总UE能力信息发送给MME。
此外，本申请提供的基站还包括存储单元，用于存储UE上报的UE能力信息，和生成的请求消息。
在具体硬件的实施例中，如图9和图10所示分别表示一种用户设备和基站的示意图。对应于前述UE能力信息的上报方法和UE能力信息接收方法的实施例，每个基站和终端设备都包括：处理器，传输总线，接收机，发送机和存储器。
在用户设备中，接收机903和发送机904的功能分别相当于前述装置实施例中的接收单元701和发送单元703，用于实现基站与用户设备之间消息的收发。处理器901的功能相当于处理单元702，其中，用户设备的处理器901主要用于判断和拆分UE能力信息，以保证传输到PDCP层的UE能力信息数据包的大小不超过其所能处理的最大容限。
在基站或网络侧，接收机1003和发送机1004的功能分别相当于前述装置实施例中的接收单元801和发送单元803，其中，基站或网络侧的处理器用于向UE发送需 要上报UE能力信息的第一请求消息，接收UE的RRC消息，判断是否需要UE再次上报UE能力信息，如果需要上报，则生成并发送第二请求消息以保证基站或网络侧能够获取需要的UE能力信息。
进一步地，所述处理器可以是一个通用中央处理器(CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本发明方案程序执行的集成电路。
通信总线902或1002可包括一通路，在上述组件之间传送信息。所述接收机和发送机包括使用任何收发器一类的装置，用于与其他设备或通信网络通信，如以太网，无线接入网(RAN)，无线局域网(Wireless Local Area Networks，WLAN)等。
存储器905或1005可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、只读光盘(Compact Disc Read-Only Memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，也可以和处理器集成在一起。其中，所述存储器用于存储执行本发明方案的应用程序代码，并由处理器来控制执行。所述处理器用于执行所述存储器中存储的应用程序代码。
本申请所述的用户设备用于实现上述实施例中的一种UE能力信息的上报方法的全部或部分功能实现，基站/网络侧设备用于实现上述实施例中的一种UE能力信息接收方法的全部或部分功能实现。
本申请所述的终端设备包括用户设备(简称：UE)，用户终端，客户端等。具体地，所述终端设备还包括：手机、平板电脑、掌上电脑或者移动互联网设备等。
在上述实施例中的“单元”可以指特定应用集成电路(application-specific integrated circuit，ASIC)，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。
本发明实施例还提供了一种计算机存储介质，用于储存为上述图9或图10所示的一种用户设备能力信息的上报方法所用的计算机软件指令，其包含用于执行上述方法实施例所设计的程序。通过执行存储的程序，可以实现反馈参数的发送。
尽管在此结合各实施例对本发明进行了描述，然而，在实施所要求保护的本发明 过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
本领域技术人员应明白，本发明的实施例可提供为方法、装置(设备)、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。计算机程序存储/分布在合适的介质中，与其它硬件一起提供或作为硬件的一部分，也可以采用其他分布形式，如通过Internet或其它有线或无线电信系统。
本发明是参照本发明实施例的方法、装置(设备)和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管结合具体特征及其实施例对本发明进行了描述，显而易见的，在不脱离本发明的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本发明的示例性说明，且视为已覆盖本发明范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本发明进行各种 改动和变型而不脱离本发明的精神和范围。这样，倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (28)

  1. 一种用户设备UE能力信息的上报方法，其特征在于，所述方法包括：
    UE获取自身的UE能力信息；
    判断所述UE能力信息大小是否超过UE的分组数据汇聚控制PDCP层所能处理的最大容限；
    如果超过所述UE的PDCP层所能处理的最大容限，则将所述UE能力信息拆分成至少两个部分UE能力信息，且拆分后每个部分UE能力信息不超过所述PDCP层所能处理的的最大容限；
    将所述拆分后的至少一个部分UE能力信息上报给网络侧。
  2. 根据权利要求1所述的方法，其特征在于，将所述拆分后的至少一个部分UE能力信息上报给网络侧之前还包括：
    所述UE接收网络侧发送的需要上报UE能力的第一请求消息，所述第一请求消息包括系统广播消息和无线资源控制RRC消息。
  3. 根据权利要求1所述的方法，其特征在于，将所述UE能力信息拆分成至少两个部分UE能力信息包括：
    将所述UE能力信息按照无线接入技术RAT系统划分原则进行拆分，或者，
    按照UE能力的重要性进行拆分，或者，
    按照协议版本先后原则进行拆分，或者，
    按照上报网络侧次数最少原则进行拆分。
  4. 根据权利要求1所述的方法，其特征在于，将所述拆分后的至少一个部分UE能力信息上报给网络侧之后还包括：
    UE检测是否接收到所述网络侧反馈的第二请求消息；
    如果检测到所述第二请求消息，则所述UE将剩余的部分UE能力信息中的至少一个发送给所述网络侧。
  5. 根据权利要求1所述的方法，其特征在于，将所述UE能力信息拆分成至少两个部分UE能力信息包括：
    将所述UE能力信息拆分成至少一个详细UE能力信息和与其对应的粗略UE能力信息，所述详细UE能力信息用于为所述网络侧给所述UE配置无线参数时 提供参考，所述粗略UE能力信息用于指示所述网络侧向所述UE发送第三请求消息；
    所述将所述拆分后的至少一个部分UE能力信息上报给网络侧包括：
    将所述粗略UE能力信息上报给所述网络侧；
    如果接收到所述网络侧根据所述粗略UE能力信息反馈的所述第三请求消息，则将所述粗略UE能力信息所对应的详细UE能力信息中的部分或全部发送至所述网络侧。
  6. 根据权利要求2所述的方法，其特征在于，将所述拆分后的至少一个部分UE能力信息上报给网络侧包括：
    对所有拆分的部分UE能力信息进行排序；
    如果所述第一请求消息中携带所述部分UE能力信息上报的优先级顺序，则按照所述优先级顺序将所述部分UE能力信息上报给所述网络侧。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，将所述UE能力信息拆分成至少两个部分包括：
    所述UE的RRC层或PDCP层将所述UE能力信息拆分成至少两个部分。
  8. 根据权利要求1-6任一项所述的方法，其特征在于，将所述拆分后的至少一个部分UE能力信息上报给网络侧包括：
    所述UE的无线链路控制RLC层以数据包形式接收并缓冲所有拆分部分UE能力信息；
    对所有所述部分UE能力信息的数据包进行分割级联处理，形成待传输的数据包；
    将所述待传输数据包通过RRC消息上报给所述网络侧。
  9. 根据权利要求1-8任一项所述的方法，其特征在于，每个所述部分UE能力信息中还包括指示信息，所述指示信息用于指示以下任意一种内容：UE是否有剩余的部分UE能力信息，所述剩余的部分UE能力信息需要上报的次数，当前上报的部分UE能力信息在所有部分UE能力信息中的顺序。
  10. 一种UE能力信息接收方法，应用于网络侧，其特征在于，方法包括：
    网络侧向UE发送需要上报UE能力信息的第一请求消息；
    接收所述UE根据所述第一请求消息反馈的第一RRC消息，所述第一RRC消息中携带有UE能力信息经过拆分后形成的至少一个部分UE能力信息；
    根据所述部分UE能力消息，判断所述UE是否还有剩余部分UE能力信息，或者，是否还需要所述UE上报部分UE能力信息；
    如果是，则生成并发送第二请求消息给所述UE；
    如果否，则生成停止指示，并将所述停止指示发送所述UE，或者，不再发送任何指示给所述UE。
  11. 根据权利要求10所述的方法，其特征在于，
    如果所述网络侧接收到的部分UE能力信息是粗略UE能力信息，则判断是否需要与所述粗略UE能力信息对应的详细UE能力信息；
    如果需要所述详细UE能力信息，则生成并发送第三请求消息给所述UE。
  12. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    网络侧接收所述UE上报的RRC消息；
    将所有所述RRC消息所对应的部分UE能力信息进行合并处理，生成所述UE的总UE能力信息；
    将所述合并后的总UE能力信息发送给移动管理实体MME。
  13. 根据权利要求10-12任一项所述的方法，其特征在于，所述第一请求消息包括系统广播消息和无线资源控制RRC消息，所述第一请求消息用于通知所述UE需要选择上报的UE能力信息。
  14. 根据权利要求10-12任一项所述的方法，其特征在于，所述第一请求消息中还包括指示所述UE上报部分UE能力信息的优先级顺序，以使所述UE按照所述优先级顺序上报。
  15. 一种扩展PCDP层处理容限的方法，其特征在于，方法包括：
    将PDCP层所能处理的数据包的的最大容限值设置为不小于8188octets。
  16. 一种用户设备UE，其特征在于，包括：接收机，处理器和发送机，
    所述接收机，用于获取自身的UE能力信息；
    所述处理器，用于判断所述UE能力信息大小是否超过UE的PDCP层所能处理的最大容限；如果超过所述UE的PDCP层所能处理的最大容限，则将所述UE能力信息拆分成至少两个部分UE能力信息，且拆分后每个部分UE能力信息不超过所述PDCP层所能处理的的最大容限；
    所述发送机，用于将所述拆分后的至少一个部分UE能力信息上报给网络侧。
  17. 根据权利要求16所述的UE，其特征在于，
    所述接收机，还用于接收网络侧发送的需要上报UE能力的第一请求消息，所述第一请求消息包括系统广播消息和RRC消息。
  18. 根据权利要求16所述的UE，其特征在于，
    所述处理器，还用于将所述UE能力信息按照RAT系统划分原则进行拆分，或者，按照UE能力的重要性进行拆分，或者，按照协议版本先后原则进行拆分，或者，按照上报网络侧次数最少原则进行拆分。
  19. 根据权利要求16所述的UE，其特征在于，
    所述处理器，还用于检测是否接收到所述网络侧反馈的第二请求消息；
    所述发送机，还用于如果检测到所述第二请求消息，则所述UE将剩余的部分UE能力信息中的至少一个发送给所述网络侧。
  20. 根据权利要求16所述的UE，其特征在于，
    所述处理器，还用于将所述UE能力信息拆分成至少一个详细UE能力信息和与其对应的粗略UE能力信息，所述详细UE能力信息用于为所述网络侧给所述UE配置无线参数时提供参考，所述粗略UE能力信息用于指示所述网络侧向所述UE发送第三请求消息；
    所述发送机，还用于将所述粗略UE能力信息上报给所述网络侧；以及，如果接收到所述网络侧根据所述粗略UE能力信息反馈的所述第三请求消息，则将所述粗略UE能力信息所对应的详细UE能力信息的部分或全部发送至所述网络侧。
  21. 根据权利要求17所述的UE，其特征在于，
    所述处理器，还用于对所有拆分的部分UE能力信息进行排序；
    所述发送机，还用于如果所述第一请求消息中携带所述部分UE能力信息上 报的优先级顺序，则按照所述优先级顺序将所述部分UE能力信息上报给所述网络侧。
  22. 根据权利要求17-21任一项所述的UE，其特征在于，
    所述UE的RRC层或PDCP层将所述UE能力信息拆分成至少两个部分。
  23. 根据权利要求17-21任一项所述的UE，其特征在于，
    所述接收机，还用于以数据包形式接收并缓冲所有拆分部分UE能力信息；
    所述处理器，还用于对所有所述部分UE能力信息的数据包进行分割级联处理，形成待传输的数据包；
    所述发送机，还用于将所述待传输数据包通过RRC消息上报给所述网络侧。
  24. 一种基站，应用于网络侧，其特征在于，包括：发送机，接收机和处理器，
    所述发送机，用于向UE发送需要上报UE能力信息的第一请求消息；
    所述接收机，用于接收所述UE根据所述第一请求消息反馈的第一RRC消息，所述第一RRC消息中携带有UE能力信息经过拆分后形成的至少一个部分UE能力信息；
    所述处理器，用于根据所述部分UE能力消息，判断所述UE是否还有剩余部分UE能力信息，或者，是否还需要所述UE上报部分UE能力信息；如果是，则生成第二请求消息；
    所述发送机，还用于发送所述第二请求消息给所述UE。
  25. 根据权利要求24所述的基站，其特征在于，
    所述处理器，还用于如果所述网络侧接收到的部分UE能力信息是粗略UE能力信息，则判断是否需要与所述粗略UE能力信息对应的详细UE能力信息；如果需要所述详细UE能力信息，则生成第三请求消息；
    所述发送机，还用于发送所述第三请求消息给所述UE。
  26. 根据权利要求24所述的基站，其特征在于，
    所述接收机，还用于接收所述UE上报的RRC消息；
    所述处理器，还用于将所有所述RRC消息所对应的部分UE能力信息进行合并处理，生成所述UE的总UE能力信息；
    所述发送机，还用于将所述合并后的总UE能力信息发送给MME。
  27. 根据权利要求24-26任一项所述的基站，其特征在于，
    所述第一请求消息包括系统广播消息和RRC消息，所述第一请求消息用于通知所述UE需要选择上报的UE能力信息。
  28. 根据权利要求24-26任一项所述的基站，其特征在于，
    所述第一请求消息中还包括指示所述UE上报部分UE能力信息的优先级顺序，以使所述UE按照所述优先级顺序上报。
PCT/CN2016/097532 2016-08-31 2016-08-31 一种用户设备能力信息的上报方法及装置 WO2018039974A1 (zh)

Priority Applications (8)

Application Number Priority Date Filing Date Title
EP21185706.5A EP3962161B1 (en) 2016-08-31 2016-08-31 Method for reporting user equipment capability information and apparatus
CN202111220654.1A CN114125822B (zh) 2016-08-31 2016-08-31 一种用户设备能力信息的上报方法及装置
CN202111220085.0A CN114125821A (zh) 2016-08-31 2016-08-31 一种用户设备能力信息的上报方法及装置
EP16914540.6A EP3499954B1 (en) 2016-08-31 2016-08-31 Method and apparatus for reporting user equipment capability information
CN201680088778.XA CN109644372B (zh) 2016-08-31 2016-08-31 一种用户设备能力信息的上报方法及装置
PCT/CN2016/097532 WO2018039974A1 (zh) 2016-08-31 2016-08-31 一种用户设备能力信息的上报方法及装置
US16/287,958 US10887758B2 (en) 2016-08-31 2019-02-27 Method for reporting user equipment capability information and apparatus
US17/127,330 US11528596B2 (en) 2016-08-31 2020-12-18 Method for reporting user equipment capability information and apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/097532 WO2018039974A1 (zh) 2016-08-31 2016-08-31 一种用户设备能力信息的上报方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/287,958 Continuation US10887758B2 (en) 2016-08-31 2019-02-27 Method for reporting user equipment capability information and apparatus

Publications (1)

Publication Number Publication Date
WO2018039974A1 true WO2018039974A1 (zh) 2018-03-08

Family

ID=61299759

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/097532 WO2018039974A1 (zh) 2016-08-31 2016-08-31 一种用户设备能力信息的上报方法及装置

Country Status (4)

Country Link
US (2) US10887758B2 (zh)
EP (2) EP3499954B1 (zh)
CN (3) CN114125821A (zh)
WO (1) WO2018039974A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110944389A (zh) * 2018-09-21 2020-03-31 华为技术有限公司 用户终端的能力信息传输方法和相关装置
WO2020063961A1 (en) * 2018-09-28 2020-04-02 Mediatek Inc. Radio resource control (rrc) message segmentation
WO2020063852A1 (zh) * 2018-09-27 2020-04-02 维沃移动通信有限公司 终端设备能力信息处理方法、终端设备及网络侧设备
US10805823B2 (en) * 2017-09-29 2020-10-13 Apple Inc. Device, system, and method for enhanced user equipment and network capability for LTE and new radio
JP2022520926A (ja) * 2019-02-14 2022-04-04 テレフオンアクチーボラゲット エルエム エリクソン（パブル） 能力情報を送信する方法及び装置
US20230164546A1 (en) * 2021-11-24 2023-05-25 At&T Intellectual Property I, L.P. Adaptive user equipment capability reporting

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190053042A1 (en) * 2017-08-11 2019-02-14 Qualcomm Incorporated Signaling user equipment capability information
CN110958709A (zh) * 2018-09-27 2020-04-03 维沃移动通信有限公司 数据传输方法及通信设备
EP3852435A4 (en) * 2018-09-29 2021-10-06 Guangdong Oppo Mobile Telecommunications Corp., Ltd. SIGNALING PROCESSING METHOD, DEVICE AND STORAGE MEDIUM
US11070971B2 (en) * 2019-07-10 2021-07-20 At&T Intellectual Property I, L.P. Self optimizing aggregation for 5G or other next generations wireless network
CN111342946B (zh) * 2020-02-27 2022-05-27 深圳市广和通无线股份有限公司 频带组合上报方法、装置、计算机设备和存储介质
CN114079869A (zh) * 2020-08-13 2022-02-22 维沃移动通信有限公司 上报能力的方法、终端设备和网络设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101883389A (zh) * 2009-05-07 2010-11-10 大唐移动通信设备有限公司 一种指示rlc sdu长度的方法和装置
CN103155632A (zh) * 2010-10-05 2013-06-12 三星电子株式会社 在无线网络环境中向基站提供最小化驱动测试测量信息的方法和系统
CN103460751A (zh) * 2011-02-14 2013-12-18 瑞典爱立信有限公司 协议层字段的向后兼容方案
CN103907365A (zh) * 2013-12-17 2014-07-02 华为技术有限公司 一种用户设备能力获取方法及系统、设备
CN105792280A (zh) * 2015-01-12 2016-07-20 联发科技股份有限公司 无线通信方法和装置

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FI20002890A (fi) * 2000-12-29 2002-06-30 Nokia Corp Kompression määrittäminen pakettivälitteisessä tiedonsiirrossa
CN103974234B (zh) * 2007-03-19 2017-09-12 华为技术有限公司 用户设备能力信息传输方法、用户设备及网络设备
EP4290933A3 (en) * 2009-04-28 2024-02-28 Mitsubishi Electric Corporation Mobile transmission system, base station and mobile terminal
WO2012021003A2 (en) * 2010-08-12 2012-02-16 Lg Electronics Inc. Apparatus and method of reporting logged measurement in wireless communication system
KR101990134B1 (ko) * 2011-08-10 2019-06-17 삼성전자주식회사 듀얼 모드 단말의 성능 정보 보고 방법 및 장치
CN103516565A (zh) * 2012-06-20 2014-01-15 中兴通讯股份有限公司 业务数据的处理方法及装置
CN105103646B (zh) * 2013-02-04 2019-09-20 瑞典爱立信有限公司 装置-锚基站选择和检测
US9160515B2 (en) * 2013-04-04 2015-10-13 Intel IP Corporation User equipment and methods for handover enhancement using scaled time-to-trigger and time-of-stay
US9756531B2 (en) * 2013-09-30 2017-09-05 Lg Electronics Inc. Method for determining radio resource control configuration in a wireless communication system supporting dual connectivity and apparatus thereof
CN105830530B (zh) * 2013-12-24 2019-09-10 索尼公司 无线电通信装置、通信控制装置、无线电通信方法和通信控制方法
CN104834649B (zh) * 2014-02-12 2018-08-07 中国科学院声学研究所 能够实现多设备协同的智能设备与多设备协同工作方法
CN104936296B (zh) 2014-03-21 2019-07-05 中兴通讯股份有限公司 一种上报和接收缓冲区状态的方法和装置
CN105338572B (zh) * 2014-06-23 2020-07-31 北京三星通信技术研究有限公司 一种双连接中分割承载的数据分配方法和装置
KR20160021626A (ko) * 2014-08-18 2016-02-26 한국전자통신연구원 스몰 셀 환경에서의 자원 관리 방법 및 그 장치
EP3222072B1 (en) * 2014-11-17 2022-04-20 Nokia Solutions and Networks Oy Capability signaling for dual connectivity
US10219256B2 (en) * 2015-01-13 2019-02-26 Qualcomm Incorporated Control information feedback for eCC on PCell
KR101985772B1 (ko) * 2015-02-05 2019-09-03 후아웨이 테크놀러지 컴퍼니 리미티드 M2m 데이터 처리 방법, 디바이스, 및 시스템

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101883389A (zh) * 2009-05-07 2010-11-10 大唐移动通信设备有限公司 一种指示rlc sdu长度的方法和装置
CN103155632A (zh) * 2010-10-05 2013-06-12 三星电子株式会社 在无线网络环境中向基站提供最小化驱动测试测量信息的方法和系统
CN103460751A (zh) * 2011-02-14 2013-12-18 瑞典爱立信有限公司 协议层字段的向后兼容方案
CN103907365A (zh) * 2013-12-17 2014-07-02 华为技术有限公司 一种用户设备能力获取方法及系统、设备
CN105792280A (zh) * 2015-01-12 2016-07-20 联发科技股份有限公司 无线通信方法和装置

Cited By (25)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10805823B2 (en) * 2017-09-29 2020-10-13 Apple Inc. Device, system, and method for enhanced user equipment and network capability for LTE and new radio
CN115022972A (zh) * 2018-09-21 2022-09-06 华为技术有限公司 用户终端的能力信息传输方法和相关装置
CN110944389B (zh) * 2018-09-21 2023-11-14 华为技术有限公司 用户终端的能力信息传输方法和相关装置
CN110944389A (zh) * 2018-09-21 2020-03-31 华为技术有限公司 用户终端的能力信息传输方法和相关装置
CN115022972B (zh) * 2018-09-21 2023-04-07 华为技术有限公司 用户终端的能力信息传输方法和相关装置
KR20210060583A (ko) * 2018-09-27 2021-05-26 비보 모바일 커뮤니케이션 컴퍼니 리미티드 단말 장치 기능 정보 처리 방법, 단말 장치 및 네트워크측 장치
KR102589689B1 (ko) * 2018-09-27 2023-10-13 비보 모바일 커뮤니케이션 컴퍼니 리미티드 단말 장치 기능 정보 처리 방법, 단말 장치 및 네트워크측 장치
CN110958644A (zh) * 2018-09-27 2020-04-03 维沃移动通信有限公司 一种终端设备能力信息处理方法及相关设备
CN110958644B (zh) * 2018-09-27 2021-09-03 维沃移动通信有限公司 一种终端设备能力信息处理方法及相关设备
EP3860210A4 (en) * 2018-09-27 2021-12-01 Vivo Mobile Communication Co., Ltd. METHOD OF PROCESSING CAPACITY INFORMATION OF A TERMINAL DEVICE, TERMINAL DEVICE, AND NETWORK-SIDED DEVICE
JP2022501963A (ja) * 2018-09-27 2022-01-06 維沃移動通信有限公司Vivo Mobile Communication Co., Ltd. 端末機器の能力情報処理方法、端末機器及びネットワーク側機器
RU2767521C1 (ru) * 2018-09-27 2022-03-17 Виво Мобайл Комьюникэйшн Ко., Лтд. Способ обработки информации о возможностях оконечного устройства, оконечное и сетевое устройства
WO2020063852A1 (zh) * 2018-09-27 2020-04-02 维沃移动通信有限公司 终端设备能力信息处理方法、终端设备及网络侧设备
JP7208370B2 (ja) 2018-09-27 2023-01-18 維沃移動通信有限公司 端末機器の能力情報処理方法、端末機器及びネットワーク側機器
AU2019348064B2 (en) * 2018-09-27 2022-08-04 Vivo Mobile Communication Co., Ltd. Method for Processing Terminal Device Capability Information, Terminal Device, and Network-Side Device
CN112753270B (zh) * 2018-09-28 2023-04-07 联发科技股份有限公司 无线电资源控制消息分段的方法及装置
TWI772688B (zh) * 2018-09-28 2022-08-01 聯發科技股份有限公司 無線電資源控制訊息分段
US11102678B2 (en) 2018-09-28 2021-08-24 Mediatek Inc. Radio resource control (RRC) message segmentation
US11671871B2 (en) 2018-09-28 2023-06-06 Mediatek Inc. Radio resource control (RRC) message segmentation
CN112753270A (zh) * 2018-09-28 2021-05-04 联发科技股份有限公司 无线电资源控制消息分段
WO2020063961A1 (en) * 2018-09-28 2020-04-02 Mediatek Inc. Radio resource control (rrc) message segmentation
JP7245914B2 (ja) 2019-02-14 2023-03-24 テレフオンアクチーボラゲット エルエム エリクソン（パブル） 能力情報を送信する方法及び装置
JP2022520926A (ja) * 2019-02-14 2022-04-04 テレフオンアクチーボラゲット エルエム エリクソン（パブル） 能力情報を送信する方法及び装置
US11888961B2 (en) 2019-02-14 2024-01-30 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatus for transmitting capability information
US20230164546A1 (en) * 2021-11-24 2023-05-25 At&T Intellectual Property I, L.P. Adaptive user equipment capability reporting

Also Published As

Publication number Publication date
EP3499954B1 (en) 2021-07-28
US20210105610A1 (en) 2021-04-08
CN114125821A (zh) 2022-03-01
EP3499954A4 (en) 2019-08-14
EP3962161A1 (en) 2022-03-02
US20190200212A1 (en) 2019-06-27
CN114125822B (zh) 2022-09-23
CN114125822A (zh) 2022-03-01
CN109644372A (zh) 2019-04-16
EP3962161B1 (en) 2023-11-01
US11528596B2 (en) 2022-12-13
US10887758B2 (en) 2021-01-05
CN109644372B (zh) 2021-10-22
EP3499954A1 (en) 2019-06-19

Similar Documents

Publication Publication Date Title
WO2018039974A1 (zh) 一种用户设备能力信息的上报方法及装置
CN112425202B (zh) 下一代移动通信系统中分类和处理sdap控制pdu的方法及相关装置
KR102364867B1 (ko) 무선 통신 시스템에서 사이드링크 통신을 구성하기 위한 방법 및 장치
WO2018027988A1 (zh) 网络切片的选择方法、无线接入设备和终端
KR20190143782A (ko) 차세대 이동 통신 시스템에서 rrc 비활성화 모드 단말의 이중 접속을 지원하는 방법 및 장치
WO2020165697A1 (en) Master cell group failure handling by a master node
EP3761681B1 (en) Multi-connection data amount reporting method
KR20190097983A (ko) 이동통신 시스템에서 셀 재선택을 수행하는 방법 및 장치
EP3412069A1 (en) Core network node, radio network node, wireless device and methods performed therein
EP3847844B1 (en) Transport of data flows over cellular networks
EP3480989B1 (en) Method and device for data transmission
US20230189084A1 (en) Wireless communication method, network node, and device
WO2020165624A1 (en) Master cell group failure handling by a secondary node
US20230188249A1 (en) Method and apparatus for signaling suspension and resumption of network coding operation
US20230188973A1 (en) Method and apparatus for signalling network coding capabilities
KR20150110259A (ko) 복수의 캐리어들을 지원하는 이동 통신 시스템에서 신호 송/수신 방법 및 장치
KR20150110281A (ko) 복수의 캐리어들을 지원하는 이동 통신 시스템에서 신호 송/수신 방법 및 장치
WO2023287337A1 (en) Access control for dual connectivity

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2016914540

Country of ref document: EP

Effective date: 20190315