US20180255452A1 - Device and Method for Handling a Temporary User Equipment Capability - Google Patents
Device and Method for Handling a Temporary User Equipment Capability Download PDFInfo
- Publication number
- US20180255452A1 US20180255452A1 US15/908,837 US201815908837A US2018255452A1 US 20180255452 A1 US20180255452 A1 US 20180255452A1 US 201815908837 A US201815908837 A US 201815908837A US 2018255452 A1 US2018255452 A1 US 2018255452A1
- Authority
- US
- United States
- Prior art keywords
- capability
- rrc
- temporary
- communication device
- network
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title description 26
- 238000004891 communication Methods 0.000 claims abstract description 60
- 238000012545 processing Methods 0.000 claims abstract description 18
- 230000004044 response Effects 0.000 claims abstract description 8
- 230000008859 change Effects 0.000 claims description 12
- 230000002776 aggregation Effects 0.000 claims description 4
- 238000004220 aggregation Methods 0.000 claims description 4
- 238000005259 measurement Methods 0.000 claims description 4
- 230000008569 process Effects 0.000 description 14
- 239000000969 carrier Substances 0.000 description 9
- 238000010586 diagram Methods 0.000 description 4
- 230000004075 alteration Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000013021 overheating Methods 0.000 description 2
- 230000008901 benefit Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
- H04W36/0085—Hand-off measurements
- H04W36/0088—Scheduling hand-off measurements
-
- 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
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/08—Reselecting an access point
-
- 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/22—Processing or transfer of terminal data, e.g. status or physical capabilities
Definitions
- the present invention relates to a device and a method used in a wireless communication system, and more particularly, to a device and a method of handling a temporary user equipment (UE) capability in a wireless communication system.
- UE user equipment
- the first BS may request the UE to transmit a UE capability.
- the UE may transmit a message to the first BS to indicate a temporary change of the UE capability (e.g., due to an occurrence of an overheating problem in the UE).
- the present invention therefore provides a communication device for handling a temporary UE capability to solve the abovementioned problem.
- a first BS for handling a temporary UE capability comprises at least one storage device for storing instructions and at least one processing circuit coupled to the at least one storage device.
- the at least one processing circuit is configured to execute the instructions stored in the at least one storage device.
- the instructions comprise receiving a UE capability from a communication device, a second BS or a core network (CN); receiving a first message indicating a temporary UE capability from the communication device; transmitting a first configuration to the communication device according to the temporary UE capability, when receiving the message; transmitting a Handover Request message to the second BS to initiate a handover to the second BS, wherein the Handover Request message comprises the UE capability and the temporary UE capability; and receiving a Handover Request Acknowledgement message from the second BS, in response to the Handover Request message, wherein the Handover Request Acknowledgement message comprises a handover command, and the handover command comprises a second configuration determined by the second BS according to the temporary UE capability.
- CN core network
- a communication device for handling a temporary UE capability comprises a storage device for storing instructions and a processing circuit coupled to the storage device.
- the processing circuit is configured to execute the instructions stored in the storage device.
- the instructions comprise transmitting a UE capability to a network, when entering a RRC_CONNECTED state from a RRC_IDLE state or a RRC_INACTIVE state at a first time instant; transmitting a message indicating a temporary UE capability to the network, when entering the RRC_CONNECTED state from the RRC_IDLE state or the RRC_INACTIVE state at a second time instant; and transmitting the message indicating the temporary UE capability to the network, when entering the RRC_CONNECTED state from the RRC_IDLE state or the RRC_INACTIVE state at a third time instant.
- a first BS for handling a temporary UE capability comprises a storage device for storing instructions and a processing circuit coupled to the storage device.
- the processing circuit is configured to execute the instructions stored in the storage device.
- the instructions comprise receiving a UE capability from a communication device, a second BS or a core network; receiving a message indicating a temporary UE capability, from the communication device; transmitting a first configuration to the communication device according to the temporary UE capability; releasing the temporary UE capability, when configuring the communication device to enter a RRC_IDLE state or a RRC_INACTIVE state; and transmitting a second configuration to the communication device according to the UE capability, when configuring the communication device to enter the RRC_CONNECTED state from the RRC_IDLE state or the RRC_INACTIVE state and after releasing the first configuration.
- FIG. 1 is a schematic diagram of a wireless communication system according to an example of the present invention.
- FIG. 2 is a schematic diagram of a communication device according to an example of the present invention.
- FIG. 3 is a flowchart of a process according to an example of the present invention.
- FIG. 4 is a flowchart of a process according to an example of the present invention.
- FIG. 5 is a flowchart of a process according to an example of the present invention.
- FIG. 6 is a flowchart of a process according to an example of the present invention.
- FIG. 1 is a schematic diagram of a wireless communication system 10 according to an example of the present invention.
- the wireless communication system 10 is composed of a network and a plurality of communication devices.
- the network and a communication device may communicate with each other via one or more carriers of licensed band (s) and/or unlicensed band(s).
- the network and the communication device may communicate with each other via one or multiple cells (e.g., multiple carriers) belonging to one or multiple base stations (BSs).
- BSs base stations
- the network and the communication devices are simply utilized for illustrating the structure of the wireless communication system 10 .
- the network may comprise at least one of a long-term evolution (LTE) network and a new radio (NR) network.
- the LTE network may comprise at least one of an evolved universal terrestrial radio access network (E-UTRAN) including at least one evolved Node-B (eNB) and an Evolved Packet Core (EPC).
- E-UTRAN evolved universal terrestrial radio access network
- eNB evolved Node-B
- EPC Evolved Packet Core
- the NR network may comprise a fifth generation (5G) radio access network including at least one 5G BS (called gNB or an evolved eNB (eLTE eNB)) and a Next Generation Core (NGC).
- 5G fifth generation
- gNB evolved eNB
- NGC Next Generation Core
- a communication device maybe a user equipment (UE), a machine type communication (MTC) device, a mobile phone, a laptop, a tablet computer, an electronic book, a portable computer system, a vehicle, or an aircraft.
- the network and the communication device can be seen as a transmitter or a receiver according to direction of transmission (i.e., transmission direction), e.g., for an uplink (UL), the communication device is the transmitter and the network is the receiver, and for a downlink (DL), the network is the transmitter and the communication device is the receiver.
- FIG. 2 is a schematic diagram of a communication device 20 according to an example of the present invention.
- the communication device 20 may be a communication device or the network shown in FIG. 1 , but is not limited herein.
- the communication device 20 may include at least one processing circuit 200 of which each may be a microprocessor or Application Specific Integrated Circuit (ASIC), at least one storage device 210 and at least one communication interfacing device 220 .
- the at least one storage device 210 may be any data storage device that may store program codes 214 , accessed and executed by the at least one processing circuit 200 .
- the at least one storage device 210 examples include but are not limited to a subscriber identity module (SIM), read-only memory (ROM), flash memory, random-access memory (RAM), hard disk, optical data storage device, non-volatile storage device, non-transitory computer-readable medium (e.g., tangible media), etc.
- SIM subscriber identity module
- ROM read-only memory
- RAM random-access memory
- the at least one communication interfacing device 220 comprises at least one transceiver used to transmit and receive signals (e.g., data, messages and/or packets) according to processing results of the at least one processing circuit 200 .
- a UE is used for representing a communication device in FIG. 1 , to simplify the illustration of the embodiments.
- a process 30 as shown in FIG. 3 can be utilized in a first BS, and includes the following steps:
- Step 300 Start.
- Step 302 Receive a UE capability from a UE, a second BS or a core network (CN).
- CN core network
- Step 304 Receive a first message indicating a temporary UE capability from the UE.
- Step 306 Transmit a first configuration to the UE according to the temporary UE capability, when receiving the message.
- Step 308 Transmit a Handover Request message to the second BS to initiate a handover to the second BS, wherein the Handover Request message comprises the UE capability and the temporary UE capability.
- Step 310 Receive a Handover Request Acknowledge message from the second BS, in response to the Handover Request message, wherein the Handover Request Acknowledge message comprises a handover command, and the handover command comprises a second configuration determined by the second BS according to the temporary UE capability.
- Step 312 End.
- the UE transmits a second message to the second BS and the second message indicates to remove the temporary UE capability, if the UE wants (e.g., intends, or is instructed by a user) to remove the temporary UE capability (i.e., indicate to the second BS that the UE wants the second BS to use the UE capability instead of the temporary UE capability).
- a process 40 as shown in FIG. 4 can be utilized in a UE, and includes the following steps:
- Step 400 Start.
- Step 402 Transmit a UE capability to a network, when entering a RRC_CONNECTED state from a RRC_IDLE state or a RRC_INACTIVE state at a first time instant.
- Step 404 Transmit a message indicating a temporary UE capability to the network, when entering the RRC_CONNECTED state from the RRC_IDLE state or the RRC_INACTIVE state at a second time instant.
- Step 406 Transmit the message indicating the temporary UE capability to the network, when entering the RRC_CONNECTED state from the RRC_IDLE state or the RRC_INACTIVE state at a third time instant.
- Step 408 End.
- the UE transmits the message indicating the temporary UE capability to the network (e.g., a first BS) via a first cell of the network, when connecting to the network via the first cell in the RRC_IDLE state or the RRC_INACTIVE state and determining to change the UE capability to the temporary UE capability.
- the UE enters the RRC_IDLE state or the RRC_INACTIVE state, when releasing a RRC connection.
- the UE in the RRC_IDLE state or in the RRC_INACTIVE state selects (or reselects) a second cell of the network (e.g., the first BS or a second BS), after releasing the RRC connection.
- the UE transmits the message indicating the temporary UE capability again, when connecting to the network via the second cell in the RRC_IDLE state or the RRC_INACTIVE state.
- the network is informed of that the UE wants to temporarily change the UE capability.
- the network configures a configuration to the UE according to the temporary UE capability. The UE does not need to worry about whether the network stores the message or not.
- the UE transmits the message indicating the temporary UE capability to the network via a first cell of the network, when connecting to the network via the first cell in the RRC_IDLE state or the RRC_INACTIVE state and determining to change the UE capability to the temporary UE capability.
- the UE enters the RRC_IDLE state or the RRC_INACTIVE state, when releasing a RRC connection.
- the UE still selects the first cell of the network, after releasing the RRC connection.
- the UE transmits the message indicating the temporary UE capability again, when connecting to the network via the first cell in the RRC_IDLE state or the RRC_INACTIVE state again.
- the network is informed twice of that the UE wants to temporarily change the UE capability.
- the network configures a configuration to the UE according to the temporary UE capability. The UE does not need to worry about whether the network stores the message or not.
- the UE transmits the message indicating the temporary UE capability to the network via a first cell of the network, when connecting to the network via the first cell in the RRC_IDLE state or the RRC_INACTIVE state and determining to change the UE capability to the temporary UE capability.
- the UE enters the RRC_IDLE state or the RRC_INACTIVE state, when releasing a RRC connection.
- the UE stops transmitting the message indicating the temporary UE capability, when connecting to the network via the first cell or the second cell in the RRC_IDLE state or the RRC_INACTIVE state and determining not to change the UE capability.
- the UE determines to transmit the message when an event or a condition occurs in the UE.
- the event or the condition may be an overheating problem, a hardware component related to the UE capability is temporarily not available (e.g., the hardware component shared between WiFi and LTE/NR), or a battery capacity is lower than a predetermined threshold.
- a process 50 as shown in FIG. 5 can be utilized in a first BS and includes the following steps:
- Step 500 Start.
- Step 502 Receive a UE capability from a UE, a second BS or a CN.
- Step 504 Receive a message indicating a temporary UE capability, from the UE.
- Step 506 Transmit a first configuration to the UE according to the temporary UE capability.
- Step 508 Release the temporary UE capability, when configuring the UE to enter a RRC_IDLE state or a RRC_INACTIVE state.
- Step 510 Transmit a second configuration to the UE according to the UE capability, when configuring the UE to enter the RRC_CONNECTED state from the RRC_IDLE state or the RRC_INACTIVE state and after releasing the first configuration.
- Step 512 End.
- a process 60 as shown in FIG. 6 can be utilized in a first BS, and includes the following steps:
- Step 600 Start.
- Step 602 Receive a UE capability from a UE, a second BS or a CN.
- Step 604 Receive a first message indicating a temporary UE capability, from the UE.
- Step 606 Transmit a first configuration to the UE according to the temporary UE capability, when receiving the first message.
- Step 608 Transmit a Handover Request message to the second BS to initiate a handover to the second BS, wherein the Handover Request message comprises the UE capability but does not comprise the temporary UE capability.
- Step 610 Receive a Handover Request Acknowledge message, in response to the Handover Request message, wherein the Handover Request Acknowledge message comprises a handover command.
- Step 612 End.
- the handover command comprises a second configuration determined according to the UE capability.
- the second BS may transmit a RRC message configuring the UE according to the UE capability after receiving a handover complete message responding to the handover command from the UE.
- the message indicating the temporary UE capability is a RRC message, is an IE comprised in the RRC message, or is a medium-access-control (MAC) control element comprised in a MAC PDU.
- MAC medium-access-control
- the UE capability may be comprised in a UE-EUTRA-Capability IE or a UE-NR-Capability (or called UE-5G-Capability) IE.
- the UE may transmit the UE-EUTRA-Capability IE or the UE-NR-Capability IE in a radio resource control (RRC) response message (e.g., a UECapabilitylnformation message) to the network (e.g. the first BS) in response to a RRC request message (e.g., a UECapabilityEnquiry message) received from the network.
- RRC radio resource control
- the UE capability comprises at least one of an access stratum release, a UE category, a plurality of physical layer parameters, a plurality of radio frequency (RF) parameters, a plurality of measurement parameters, a multi-input-multi-output (MIMO) capability, a carrier aggregation (CA) capability and an unlicensed access.
- RF radio frequency
- MIMO multi-input-multi-output
- CA carrier aggregation
- the CA capability comprises a list of a plurality of supported band combinations which defines the number of the aggregated carriers (e.g., carrier frequencies) supported by the UE for configurations with inter-band, intra-band non-contiguous, or intra-band contiguous CA and without CA in licensed or unlicensed band.
- the UE provides supported UL and DL CA bandwidth classes.
- the MIMO capability applies to all DL carriers of a bandwidth class in a band combination.
- the UE may also indicate a separate MIMO capability applying to each individual carrier of a bandwidth class in a band combination.
- the temporary UE capability is that the UE indicates to the network that the UE temporarily disables the CA capability. In one example, the temporary UE capability is that the UE indicates to the network that the UE temporarily disables or changes a supported band combination which indicates a maximum number of aggregated carriers the UE is capable of. For example, the UE capability includes a first supported band combination indicating support of 3 DL or UL aggregated carriers and a second supported band combination indicating support of 4 DL or UL aggregated carriers. The temporary UE capability is that the UE temporarily disables the second supported band combination. For example, the UE capability includes a supported band combination indicating a maximum of 3 DL or UL aggregated carriers. The temporary UE capability is that the UE temporarily updates the supported band combination to indicate a maximum of 2 DL or UL aggregated carriers.
- the temporary UE capability is that the UE indicates to the network that the UE temporarily changes the MIMO capability.
- the UE may indicate that the UE supports 4-layer or 4 ⁇ 4 MIMO in the MIMO capability in the UE capability, and may indicate the temporary change of the MIMO capability to 2-layer or 2 ⁇ 2 MIMO.
- the UE capability is the unlicensed access.
- the temporary UE capability is that the UE indicates to the network the unlicensed access is disabled.
- the network indicates in a system information (e.g., a system information block) or a RRC message (e.g., a RRCConnectionSetup message, a RRCConnectionResume message or a RRCConnectionReconfiguration message) that whether the UE is allowed to transmit the temporary UE capability to the network.
- a RRC message e.g., a RRCConnectionSetup message, a RRCConnectionResume message or a RRCConnectionReconfiguration message
- the UE may perform an attach procedure or a tracking area update procedure.
- the UE may perform a detach procedure before the attach procedure or tracking area update procedure.
- the network transmits a UECapabilityEnquiry message to the UE after or during the attach procedure or the tracking area update procedure.
- the UE may change (e.g., update) the UE capability to the network (i.e., indicate the temporary UE capability) in a UECapabilitylnformation message to the
- the present invention provides methods and devices for handling a temporary UE capability.
- a problem that the first BS does not know how long the temporary UE capability takes effect is solved by the present invention.
- the second BS receives the UE capability from the first BS.
- a problem that the second BS does not know that the UE temporarily indicates the change of the UE capability to the first BS is solved by the present invention.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
- This application claims the benefit of U.S. Provisional Application No. 62/465,171 filed on Mar. 1, 2017, which is incorporated herein by reference.
- The present invention relates to a device and a method used in a wireless communication system, and more particularly, to a device and a method of handling a temporary user equipment (UE) capability in a wireless communication system.
- When a UE connects to a first base station (BS), the first BS may request the UE to transmit a UE capability. The UE may transmit a message to the first BS to indicate a temporary change of the UE capability (e.g., due to an occurrence of an overheating problem in the UE).
- The present invention therefore provides a communication device for handling a temporary UE capability to solve the abovementioned problem.
- A first BS for handling a temporary UE capability comprises at least one storage device for storing instructions and at least one processing circuit coupled to the at least one storage device. The at least one processing circuit is configured to execute the instructions stored in the at least one storage device. The instructions comprise receiving a UE capability from a communication device, a second BS or a core network (CN); receiving a first message indicating a temporary UE capability from the communication device; transmitting a first configuration to the communication device according to the temporary UE capability, when receiving the message; transmitting a Handover Request message to the second BS to initiate a handover to the second BS, wherein the Handover Request message comprises the UE capability and the temporary UE capability; and receiving a Handover Request Acknowledgement message from the second BS, in response to the Handover Request message, wherein the Handover Request Acknowledgement message comprises a handover command, and the handover command comprises a second configuration determined by the second BS according to the temporary UE capability.
- A communication device for handling a temporary UE capability comprises a storage device for storing instructions and a processing circuit coupled to the storage device. The processing circuit is configured to execute the instructions stored in the storage device. The instructions comprise transmitting a UE capability to a network, when entering a RRC_CONNECTED state from a RRC_IDLE state or a RRC_INACTIVE state at a first time instant; transmitting a message indicating a temporary UE capability to the network, when entering the RRC_CONNECTED state from the RRC_IDLE state or the RRC_INACTIVE state at a second time instant; and transmitting the message indicating the temporary UE capability to the network, when entering the RRC_CONNECTED state from the RRC_IDLE state or the RRC_INACTIVE state at a third time instant.
- A first BS for handling a temporary UE capability comprises a storage device for storing instructions and a processing circuit coupled to the storage device. The processing circuit is configured to execute the instructions stored in the storage device. The instructions comprise receiving a UE capability from a communication device, a second BS or a core network; receiving a message indicating a temporary UE capability, from the communication device; transmitting a first configuration to the communication device according to the temporary UE capability; releasing the temporary UE capability, when configuring the communication device to enter a RRC_IDLE state or a RRC_INACTIVE state; and transmitting a second configuration to the communication device according to the UE capability, when configuring the communication device to enter the RRC_CONNECTED state from the RRC_IDLE state or the RRC_INACTIVE state and after releasing the first configuration.
- These and other objectives of the present invention will no doubt become obvious to those of ordinary skill in the art after reading the following detailed description of the preferred embodiment that is illustrated in the various figures and drawings.
-
FIG. 1 is a schematic diagram of a wireless communication system according to an example of the present invention. -
FIG. 2 is a schematic diagram of a communication device according to an example of the present invention. -
FIG. 3 is a flowchart of a process according to an example of the present invention. -
FIG. 4 is a flowchart of a process according to an example of the present invention. -
FIG. 5 is a flowchart of a process according to an example of the present invention. -
FIG. 6 is a flowchart of a process according to an example of the present invention. -
FIG. 1 is a schematic diagram of awireless communication system 10 according to an example of the present invention. Thewireless communication system 10 is composed of a network and a plurality of communication devices. The network and a communication device may communicate with each other via one or more carriers of licensed band (s) and/or unlicensed band(s). The network and the communication device may communicate with each other via one or multiple cells (e.g., multiple carriers) belonging to one or multiple base stations (BSs). - In
FIG. 1 , the network and the communication devices are simply utilized for illustrating the structure of thewireless communication system 10. Practically, the network may comprise at least one of a long-term evolution (LTE) network and a new radio (NR) network. The LTE network may comprise at least one of an evolved universal terrestrial radio access network (E-UTRAN) including at least one evolved Node-B (eNB) and an Evolved Packet Core (EPC). The NR network may comprise a fifth generation (5G) radio access network including at least one 5G BS (called gNB or an evolved eNB (eLTE eNB)) and a Next Generation Core (NGC). - A communication device maybe a user equipment (UE), a machine type communication (MTC) device, a mobile phone, a laptop, a tablet computer, an electronic book, a portable computer system, a vehicle, or an aircraft. In addition, the network and the communication device can be seen as a transmitter or a receiver according to direction of transmission (i.e., transmission direction), e.g., for an uplink (UL), the communication device is the transmitter and the network is the receiver, and for a downlink (DL), the network is the transmitter and the communication device is the receiver.
-
FIG. 2 is a schematic diagram of acommunication device 20 according to an example of the present invention. Thecommunication device 20 may be a communication device or the network shown inFIG. 1 , but is not limited herein. Thecommunication device 20 may include at least oneprocessing circuit 200 of which each may be a microprocessor or Application Specific Integrated Circuit (ASIC), at least onestorage device 210 and at least onecommunication interfacing device 220. The at least onestorage device 210 may be any data storage device that may storeprogram codes 214, accessed and executed by the at least oneprocessing circuit 200. Examples of the at least onestorage device 210 include but are not limited to a subscriber identity module (SIM), read-only memory (ROM), flash memory, random-access memory (RAM), hard disk, optical data storage device, non-volatile storage device, non-transitory computer-readable medium (e.g., tangible media), etc. The at least onecommunication interfacing device 220 comprises at least one transceiver used to transmit and receive signals (e.g., data, messages and/or packets) according to processing results of the at least oneprocessing circuit 200. - In the following embodiments, a UE is used for representing a communication device in
FIG. 1 , to simplify the illustration of the embodiments. - A
process 30 as shown inFIG. 3 can be utilized in a first BS, and includes the following steps: - Step 300: Start.
- Step 302: Receive a UE capability from a UE, a second BS or a core network (CN).
- Step 304: Receive a first message indicating a temporary UE capability from the UE.
- Step 306: Transmit a first configuration to the UE according to the temporary UE capability, when receiving the message.
- Step 308: Transmit a Handover Request message to the second BS to initiate a handover to the second BS, wherein the Handover Request message comprises the UE capability and the temporary UE capability.
- Step 310: Receive a Handover Request Acknowledge message from the second BS, in response to the Handover Request message, wherein the Handover Request Acknowledge message comprises a handover command, and the handover command comprises a second configuration determined by the second BS according to the temporary UE capability.
- Step 312: End.
- The following examples may be applied to the
process 30. - In one example, the UE transmits a second message to the second BS and the second message indicates to remove the temporary UE capability, if the UE wants (e.g., intends, or is instructed by a user) to remove the temporary UE capability (i.e., indicate to the second BS that the UE wants the second BS to use the UE capability instead of the temporary UE capability).
- A
process 40 as shown inFIG. 4 can be utilized in a UE, and includes the following steps: - Step 400: Start.
- Step 402: Transmit a UE capability to a network, when entering a RRC_CONNECTED state from a RRC_IDLE state or a RRC_INACTIVE state at a first time instant.
- Step 404: Transmit a message indicating a temporary UE capability to the network, when entering the RRC_CONNECTED state from the RRC_IDLE state or the RRC_INACTIVE state at a second time instant.
- Step 406: Transmit the message indicating the temporary UE capability to the network, when entering the RRC_CONNECTED state from the RRC_IDLE state or the RRC_INACTIVE state at a third time instant.
- Step 408: End.
- The following examples may be applied to the
process 40. - In one example, the UE transmits the message indicating the temporary UE capability to the network (e.g., a first BS) via a first cell of the network, when connecting to the network via the first cell in the RRC_IDLE state or the RRC_INACTIVE state and determining to change the UE capability to the temporary UE capability. The UE enters the RRC_IDLE state or the RRC_INACTIVE state, when releasing a RRC connection. The UE in the RRC_IDLE state or in the RRC_INACTIVE state selects (or reselects) a second cell of the network (e.g., the first BS or a second BS), after releasing the RRC connection. The UE transmits the message indicating the temporary UE capability again, when connecting to the network via the second cell in the RRC_IDLE state or the RRC_INACTIVE state. The network is informed of that the UE wants to temporarily change the UE capability. The network configures a configuration to the UE according to the temporary UE capability. The UE does not need to worry about whether the network stores the message or not.
- In one example, the UE transmits the message indicating the temporary UE capability to the network via a first cell of the network, when connecting to the network via the first cell in the RRC_IDLE state or the RRC_INACTIVE state and determining to change the UE capability to the temporary UE capability. The UE enters the RRC_IDLE state or the RRC_INACTIVE state, when releasing a RRC connection. The UE still selects the first cell of the network, after releasing the RRC connection. The UE transmits the message indicating the temporary UE capability again, when connecting to the network via the first cell in the RRC_IDLE state or the RRC_INACTIVE state again. The network is informed twice of that the UE wants to temporarily change the UE capability. The network configures a configuration to the UE according to the temporary UE capability. The UE does not need to worry about whether the network stores the message or not.
- In one example, the UE transmits the message indicating the temporary UE capability to the network via a first cell of the network, when connecting to the network via the first cell in the RRC_IDLE state or the RRC_INACTIVE state and determining to change the UE capability to the temporary UE capability. The UE enters the RRC_IDLE state or the RRC_INACTIVE state, when releasing a RRC connection. The UE stops transmitting the message indicating the temporary UE capability, when connecting to the network via the first cell or the second cell in the RRC_IDLE state or the RRC_INACTIVE state and determining not to change the UE capability.
- In one example, the UE determines to transmit the message when an event or a condition occurs in the UE. The event or the condition may be an overheating problem, a hardware component related to the UE capability is temporarily not available (e.g., the hardware component shared between WiFi and LTE/NR), or a battery capacity is lower than a predetermined threshold.
- A
process 50 as shown inFIG. 5 can be utilized in a first BS and includes the following steps: - Step 500: Start.
- Step 502: Receive a UE capability from a UE, a second BS or a CN.
- Step 504: Receive a message indicating a temporary UE capability, from the UE.
- Step 506: Transmit a first configuration to the UE according to the temporary UE capability.
- Step 508: Release the temporary UE capability, when configuring the UE to enter a RRC_IDLE state or a RRC_INACTIVE state.
- Step 510: Transmit a second configuration to the UE according to the UE capability, when configuring the UE to enter the RRC_CONNECTED state from the RRC_IDLE state or the RRC_INACTIVE state and after releasing the first configuration.
- Step 512: End.
- A
process 60 as shown inFIG. 6 can be utilized in a first BS, and includes the following steps: - Step 600: Start.
- Step 602: Receive a UE capability from a UE, a second BS or a CN.
- Step 604: Receive a first message indicating a temporary UE capability, from the UE.
- Step 606: Transmit a first configuration to the UE according to the temporary UE capability, when receiving the first message.
- Step 608: Transmit a Handover Request message to the second BS to initiate a handover to the second BS, wherein the Handover Request message comprises the UE capability but does not comprise the temporary UE capability.
- Step 610: Receive a Handover Request Acknowledge message, in response to the Handover Request message, wherein the Handover Request Acknowledge message comprises a handover command.
- Step 612: End.
- The following examples may be applied to the
process 60. - In one example, the handover command comprises a second configuration determined according to the UE capability. In another example, the second BS may transmit a RRC message configuring the UE according to the UE capability after receiving a handover complete message responding to the handover command from the UE.
- The following examples may be applied to the processes 30-60.
- In one example, the message indicating the temporary UE capability is a RRC message, is an IE comprised in the RRC message, or is a medium-access-control (MAC) control element comprised in a MAC PDU.
- In one example, the UE capability may be comprised in a UE-EUTRA-Capability IE or a UE-NR-Capability (or called UE-5G-Capability) IE. The UE may transmit the UE-EUTRA-Capability IE or the UE-NR-Capability IE in a radio resource control (RRC) response message (e.g., a UECapabilitylnformation message) to the network (e.g. the first BS) in response to a RRC request message (e.g., a UECapabilityEnquiry message) received from the network.
- In one example, the UE capability comprises at least one of an access stratum release, a UE category, a plurality of physical layer parameters, a plurality of radio frequency (RF) parameters, a plurality of measurement parameters, a multi-input-multi-output (MIMO) capability, a carrier aggregation (CA) capability and an unlicensed access.
- In one example, the CA capability comprises a list of a plurality of supported band combinations which defines the number of the aggregated carriers (e.g., carrier frequencies) supported by the UE for configurations with inter-band, intra-band non-contiguous, or intra-band contiguous CA and without CA in licensed or unlicensed band. In a band combination, the UE provides supported UL and DL CA bandwidth classes.
- In one example, the MIMO capability applies to all DL carriers of a bandwidth class in a band combination. In one example, the UE may also indicate a separate MIMO capability applying to each individual carrier of a bandwidth class in a band combination.
- In one example, the temporary UE capability is that the UE indicates to the network that the UE temporarily disables the CA capability. In one example, the temporary UE capability is that the UE indicates to the network that the UE temporarily disables or changes a supported band combination which indicates a maximum number of aggregated carriers the UE is capable of. For example, the UE capability includes a first supported band combination indicating support of 3 DL or UL aggregated carriers and a second supported band combination indicating support of 4 DL or UL aggregated carriers. The temporary UE capability is that the UE temporarily disables the second supported band combination. For example, the UE capability includes a supported band combination indicating a maximum of 3 DL or UL aggregated carriers. The temporary UE capability is that the UE temporarily updates the supported band combination to indicate a maximum of 2 DL or UL aggregated carriers.
- In one example, the temporary UE capability is that the UE indicates to the network that the UE temporarily changes the MIMO capability. For example, the UE may indicate that the UE supports 4-layer or 4×4 MIMO in the MIMO capability in the UE capability, and may indicate the temporary change of the MIMO capability to 2-layer or 2×2 MIMO.
- In one example, the UE capability is the unlicensed access. The temporary UE capability is that the UE indicates to the network the unlicensed access is disabled.
- In one example, the network indicates in a system information (e.g., a system information block) or a RRC message (e.g., a RRCConnectionSetup message, a RRCConnectionResume message or a RRCConnectionReconfiguration message) that whether the UE is allowed to transmit the temporary UE capability to the network. If the UE is not allowed to transmit the temporary UE capability, the UE may perform an attach procedure or a tracking area update procedure. The UE may perform a detach procedure before the attach procedure or tracking area update procedure. The network transmits a UECapabilityEnquiry message to the UE after or during the attach procedure or the tracking area update procedure. Thus, the UE may change (e.g., update) the UE capability to the network (i.e., indicate the temporary UE capability) in a UECapabilitylnformation message to the UE in response to the UECapabilityEnquiry message.
- Those skilled in the art should readily make combinations, modifications and/or alterations on the abovementioned description and examples. For example, the skilled person easily makes new embodiments of the network based on the embodiments and examples of the UE, and makes new embodiments of the UE based on the embodiments and examples of the network. The abovementioned description, steps and/or processes including suggested steps can be realized by means that could be hardware, software, firmware (known as a combination of a hardware device and computer instructions and data that reside as read-only software on the hardware device), an electronic system, or combination thereof. An example of the means may be the
communication device 20. Any of the above processes and examples above may be compiled into theprogram code 214. - To sum up, the present invention provides methods and devices for handling a temporary UE capability. A problem that the first BS does not know how long the temporary UE capability takes effect is solved by the present invention. In addition, when the UE connects to a second BS from the first BS, the second BS receives the UE capability from the first BS. A problem that the second BS does not know that the UE temporarily indicates the change of the UE capability to the first BS is solved by the present invention.
- Those skilled in the art will readily observe that numerous modifications and alterations of the device and method may be made while retaining the teachings of the invention. Accordingly, the above disclosure should be construed as limited only by the metes and bounds of the appended claims.
Claims (14)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US15/908,837 US10887761B2 (en) | 2017-03-01 | 2018-03-01 | Device and method for handling a temporary user equipment capability |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US201762465171P | 2017-03-01 | 2017-03-01 | |
| US15/908,837 US10887761B2 (en) | 2017-03-01 | 2018-03-01 | Device and method for handling a temporary user equipment capability |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| US20180255452A1 true US20180255452A1 (en) | 2018-09-06 |
| US10887761B2 US10887761B2 (en) | 2021-01-05 |
Family
ID=61569067
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US15/908,837 Active US10887761B2 (en) | 2017-03-01 | 2018-03-01 | Device and method for handling a temporary user equipment capability |
Country Status (4)
| Country | Link |
|---|---|
| US (1) | US10887761B2 (en) |
| EP (1) | EP3370448B1 (en) |
| CN (1) | CN108541033B (en) |
| TW (1) | TWI709348B (en) |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111770573A (en) * | 2019-04-01 | 2020-10-13 | 普天信息技术有限公司 | Method and device for reporting terminal capability |
| WO2021072425A1 (en) * | 2019-10-10 | 2021-04-15 | Qualcomm Incorporated | Power-saving mode indication |
| US11259175B2 (en) * | 2017-08-09 | 2022-02-22 | Beijing Xiaomi Mobile Software Co., Ltd. | Overheating protection method for user equipment, device, user equipment, and base station |
| US11291069B2 (en) * | 2017-09-21 | 2022-03-29 | Huawei Technologies Co., Ltd. | Connection management method, user equipment, core network entity, and system |
| US20220141728A1 (en) * | 2019-03-06 | 2022-05-05 | Ntt Docomo, Inc. | Network node |
| EP4044715A4 (en) * | 2019-09-30 | 2022-09-07 | Huawei Technologies Co., Ltd. | COMMUNICATION METHOD AND APPARATUS |
| CN116347427A (en) * | 2021-12-25 | 2023-06-27 | 华为技术有限公司 | Method and communication device for configuration |
| US11956729B2 (en) * | 2021-01-21 | 2024-04-09 | Google Llc | Uplink power and resource allocation enhancement for user devices |
| US12028741B2 (en) * | 2018-05-10 | 2024-07-02 | Qualcomm Incorporated | Dynamic control channel management |
| WO2025195062A1 (en) * | 2024-03-18 | 2025-09-25 | 联想(北京)有限公司 | Communication method and apparatus, and access network device |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111491342B (en) * | 2019-06-28 | 2021-06-04 | 维沃移动通信有限公司 | Terminal capability identification operation method, communication device and storage medium |
| US11503522B1 (en) | 2020-11-24 | 2022-11-15 | Sprint Communications Company Lp | Handover based on wireless user equipment (UE) capabilities |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100113024A1 (en) * | 2008-10-31 | 2010-05-06 | Chih-Hsiang Wu | Method of handling an inter rat handover in wireless communication system and related communication device |
| US20120224561A1 (en) * | 2011-03-02 | 2012-09-06 | Zte (Usa) Inc. | Methods and apparatus for radio configuration indication |
| US20140199996A1 (en) * | 2013-01-17 | 2014-07-17 | Broadcom Corporation | Wireless Communication System Utilizing Enhanced Air-Interface |
| US20140254559A1 (en) * | 2013-03-08 | 2014-09-11 | Futurewei Technologies, Inc. | Systems and Methods for Interference Cancellation Capability Reporting and User Equipment Offloading in Heterogeneous Networks |
| US20150117400A1 (en) * | 2013-10-31 | 2015-04-30 | Qualcomm Incorporated | Signaling network capabilities for a wireless device |
| US20150341837A1 (en) * | 2013-01-31 | 2015-11-26 | Huawei Technologies Co., Ltd. | Access processing method, apparatus and system |
| US20150382257A1 (en) * | 2012-02-06 | 2015-12-31 | Samsung Electronics Co., Ltd. | In-device coexistence interference report control method and apparatus of network in mobile communication system |
| US20160029275A1 (en) * | 2013-04-03 | 2016-01-28 | Huawei Technologies Co., Ltd. | Method for Acquiring UE Capability, Terminal, and Base Station |
| US20160323800A1 (en) * | 2015-05-01 | 2016-11-03 | Qualcomm Incorporated | Handoff for satellite communication |
| US20170215065A1 (en) * | 2014-08-15 | 2017-07-27 | Intel IP Corporation | Methods and apparatus of evolved node b and user equipment for capability information setting |
| US20180063785A1 (en) * | 2016-08-25 | 2018-03-01 | Mediatek Singapore Pte. Ltd. | Device-Driven Power Scaling In Advanced Wireless Modem Architectures |
| US20180227816A1 (en) * | 2017-02-09 | 2018-08-09 | Htc Corporation | Device and Method for Handling Evolved Long-Term Evolution Network |
| US20190274076A1 (en) * | 2016-10-25 | 2019-09-05 | Lg Electronics Inc. | Method for supporting ue mobility in wireless communication system and device therefor |
Family Cites Families (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8090369B2 (en) | 2007-05-01 | 2012-01-03 | Qualcomm Incorporated | User equipment capability handling in long-term evolution systems |
| CN101730058A (en) | 2008-10-30 | 2010-06-09 | 华为技术有限公司 | Method, device and system for updating wireless capability |
| US8515363B2 (en) | 2009-06-19 | 2013-08-20 | Sharp Kabushiki Kaisha | Systems and methods for providing a reduced power amplifier transmission mode |
| CN102340772B (en) | 2010-07-15 | 2014-04-16 | 华为技术有限公司 | Security processing method, device and system in conversion process |
| US10728870B2 (en) | 2012-10-08 | 2020-07-28 | Qualcomm Incorporated | Methods and systems for avoiding transitions between radio access technologies when packet data networks are inaccessible |
| US9894547B2 (en) | 2014-04-29 | 2018-02-13 | Qualcomm Incorporated | Dynamic update of UE capability for inter-frequency and inter-RAT measurements |
| US10172172B2 (en) | 2014-08-07 | 2019-01-01 | Qualcomm Incorporated | Device-to-device capability signaling |
| US20160157228A1 (en) * | 2014-11-28 | 2016-06-02 | Lg Electronics Inc. | Method for signaling ue capability change and apparatus therefor |
| US10708920B2 (en) * | 2015-03-03 | 2020-07-07 | Qualcomm Incorporated | Method and apparatus for dynamic device capability signaling in wireless communications |
| US9813896B2 (en) * | 2015-04-22 | 2017-11-07 | Verizon Patent And Licensing Inc. | Reconfiguring wireless device capability and performance |
| WO2018012904A1 (en) * | 2016-07-13 | 2018-01-18 | Samsung Electronics Co., Ltd. | Access control method and apparatus for use in mobile communication |
-
2018
- 2018-03-01 TW TW107106767A patent/TWI709348B/en active
- 2018-03-01 CN CN201810172673.3A patent/CN108541033B/en active Active
- 2018-03-01 US US15/908,837 patent/US10887761B2/en active Active
- 2018-03-01 EP EP18159563.8A patent/EP3370448B1/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100113024A1 (en) * | 2008-10-31 | 2010-05-06 | Chih-Hsiang Wu | Method of handling an inter rat handover in wireless communication system and related communication device |
| US20120224561A1 (en) * | 2011-03-02 | 2012-09-06 | Zte (Usa) Inc. | Methods and apparatus for radio configuration indication |
| US20150382257A1 (en) * | 2012-02-06 | 2015-12-31 | Samsung Electronics Co., Ltd. | In-device coexistence interference report control method and apparatus of network in mobile communication system |
| US20140199996A1 (en) * | 2013-01-17 | 2014-07-17 | Broadcom Corporation | Wireless Communication System Utilizing Enhanced Air-Interface |
| US20150341837A1 (en) * | 2013-01-31 | 2015-11-26 | Huawei Technologies Co., Ltd. | Access processing method, apparatus and system |
| US20140254559A1 (en) * | 2013-03-08 | 2014-09-11 | Futurewei Technologies, Inc. | Systems and Methods for Interference Cancellation Capability Reporting and User Equipment Offloading in Heterogeneous Networks |
| US20160029275A1 (en) * | 2013-04-03 | 2016-01-28 | Huawei Technologies Co., Ltd. | Method for Acquiring UE Capability, Terminal, and Base Station |
| US20150117400A1 (en) * | 2013-10-31 | 2015-04-30 | Qualcomm Incorporated | Signaling network capabilities for a wireless device |
| US20170215065A1 (en) * | 2014-08-15 | 2017-07-27 | Intel IP Corporation | Methods and apparatus of evolved node b and user equipment for capability information setting |
| US20160323800A1 (en) * | 2015-05-01 | 2016-11-03 | Qualcomm Incorporated | Handoff for satellite communication |
| US20180063785A1 (en) * | 2016-08-25 | 2018-03-01 | Mediatek Singapore Pte. Ltd. | Device-Driven Power Scaling In Advanced Wireless Modem Architectures |
| US20190274076A1 (en) * | 2016-10-25 | 2019-09-05 | Lg Electronics Inc. | Method for supporting ue mobility in wireless communication system and device therefor |
| US20180227816A1 (en) * | 2017-02-09 | 2018-08-09 | Htc Corporation | Device and Method for Handling Evolved Long-Term Evolution Network |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11711688B2 (en) | 2017-08-09 | 2023-07-25 | Beijing Xiaomi Mobile Software Co., Ltd. | Overheating protection method for user equipment, device, user equipment, and base station |
| US11259175B2 (en) * | 2017-08-09 | 2022-02-22 | Beijing Xiaomi Mobile Software Co., Ltd. | Overheating protection method for user equipment, device, user equipment, and base station |
| US11291069B2 (en) * | 2017-09-21 | 2022-03-29 | Huawei Technologies Co., Ltd. | Connection management method, user equipment, core network entity, and system |
| US12028741B2 (en) * | 2018-05-10 | 2024-07-02 | Qualcomm Incorporated | Dynamic control channel management |
| US20220141728A1 (en) * | 2019-03-06 | 2022-05-05 | Ntt Docomo, Inc. | Network node |
| US12047822B2 (en) * | 2019-03-06 | 2024-07-23 | Ntt Docomo, Inc. | Base station, radio communication method, and radio communication system for MR-DC |
| CN111770573A (en) * | 2019-04-01 | 2020-10-13 | 普天信息技术有限公司 | Method and device for reporting terminal capability |
| EP4044715A4 (en) * | 2019-09-30 | 2022-09-07 | Huawei Technologies Co., Ltd. | COMMUNICATION METHOD AND APPARATUS |
| US12185319B2 (en) | 2019-09-30 | 2024-12-31 | Huawei Technologies Co., Ltd. | Communication method and apparatus |
| US11589303B2 (en) | 2019-10-10 | 2023-02-21 | Qualcomm Incorporated | Power-saving mode indication |
| WO2021072425A1 (en) * | 2019-10-10 | 2021-04-15 | Qualcomm Incorporated | Power-saving mode indication |
| US11956729B2 (en) * | 2021-01-21 | 2024-04-09 | Google Llc | Uplink power and resource allocation enhancement for user devices |
| CN116347427A (en) * | 2021-12-25 | 2023-06-27 | 华为技术有限公司 | Method and communication device for configuration |
| JP2025500987A (en) * | 2021-12-25 | 2025-01-15 | 華為技術有限公司 | Configuration method and communication device |
| EP4440166A4 (en) * | 2021-12-25 | 2025-03-26 | Huawei Technologies Co., Ltd. | METHOD FOR CONFIGURATION AND COMMUNICATION DEVICE |
| WO2025195062A1 (en) * | 2024-03-18 | 2025-09-25 | 联想(北京)有限公司 | Communication method and apparatus, and access network device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108541033B (en) | 2021-04-20 |
| US10887761B2 (en) | 2021-01-05 |
| TW201834482A (en) | 2018-09-16 |
| CN108541033A (en) | 2018-09-14 |
| EP3370448A1 (en) | 2018-09-05 |
| EP3370448B1 (en) | 2020-10-28 |
| TWI709348B (en) | 2020-11-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10887761B2 (en) | Device and method for handling a temporary user equipment capability | |
| US10397891B2 (en) | Device and method of handling multiple cellular radio operations | |
| US20180227737A1 (en) | Device and Method for Handling New Radio Capabilities | |
| US10492108B2 (en) | Device and method of handling transferring of a state | |
| US10470199B2 (en) | Device and method of handling a PDU session in inter-system mobility between a LTE system and a NR/5G system | |
| US10575349B2 (en) | Device and method for handling a new radio connection in inter-system mobility | |
| US20170127331A1 (en) | Device and Method of Handling Communication Failure | |
| US10292078B1 (en) | Device and method of handling an evolved packet system bearer context | |
| US10321374B2 (en) | Device and method for handling user equipment configuration | |
| US11006331B2 (en) | Device and method of handling pre-allocated uplink grant | |
| US10218474B2 (en) | Device and method of handling scheduling request transmission | |
| US10462695B2 (en) | Device and method for handling measurement configuration in dual connectivity | |
| US11516870B2 (en) | Device and method of handling a cell selection procedure | |
| EP3091790B1 (en) | Device and method of receiving system information | |
| US10708929B2 (en) | Device and method of handling scheduling request for logical channel | |
| US9668185B2 (en) | Device and method of handling system information |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
| AS | Assignment |
Owner name: HTC CORPORATION, TAIWAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:WU, CHIH-HSIANG;REEL/FRAME:045101/0224 Effective date: 20180305 |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: AWAITING TC RESP., ISSUE FEE NOT PAID |
|
| STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
| STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
| MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |