Device and method for processing narrowband Internet of Things communications
By receiving and processing SystemInformationBlockType2-NB messages in a communication device of a narrow frequency IoT user, responding to RRCConnectionReconfiguration-NB messages using timers and constant values, and selecting narrow frequency or long-term evolution cells for wireless resource control connection reconstruction when necessary, solve the problem of rebuilding the wireless resource control connection. The problem of the failure of the narrow-band IoT user side cannot receive system messages and wireless links, which improves communication stability and efficiency.
Patent Information
- Application Number
- CN202110420780.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2017-08-08
- Filing Date
- 2017-08-09
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2037-08-09
AI Technical Summary
In a long-term evolution (LTE) system, the Narrow-band Internet of Things (NB-IoT) user cannot receive SystemInformationBlockType2-NB messages, resulting in the inability to perform wireless resource control connection reconstruction and time alignment, and the inability to perform wireless resource control in a long-term evolution cell Connection reconstruction affects communication stability.
Design a communication device, including processing circuits and storage devices, execute instructions to receive SystemInformationBlockType2-NB messages of narrow-frequency IoT cells, respond to RRCConnectionReconfiguration-NB messages using timers and constant values, and when initializing the wireless resource control connection reconstruction program Select the narrow frequency or long-term evolution cell and terminate the wireless resource control connection reconstruction program to enter idle mode.
It effectively solves the problem of wireless resource control connection reconstruction between narrow frequency and long-term evolution cells of narrow frequency IoT users, improves communication stability and efficiency, and saves time in wireless resource control connection reconstruction.
Smart Images

Figure CN112929990B_ABST
Abstract
Description
[0001] This divisional application is a divisional application of the invention patent application with the application date of August 9, 2017, application number 201710676469.0, and invention name “Device and method for processing narrowband Internet of Things communications”. Technical Field
[0002] The present invention relates to a device and method for a wireless communication system, and more particularly to a device and method for processing narrowband Internet of Things communications in a wireless communication system. Background Art
[0003] In the Long-Term Evolution (LTE) system, the radio access network is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) consisting of at least one evolved Node-B (eNB), which communicates with a user equipment (UE) on the one hand and with the core network on the other hand. The core network may include a Mobility Management Entity (MME) and Quality of Service (QoS) control for the user equipment. Summary of the invention
[0004] The present invention provides a communication device and method for processing narrowband internet of things (NB-IoT) communication to solve the above problems.
[0005] The present invention discloses a communication device for processing a narrowband Internet of Things communication, the communication device comprising a storage device for storing instructions, and a processing circuit coupled to the storage device. The processing circuit is configured to execute instructions stored in the storage device. The instructions include receiving a SystemInformationBlockType2-NB message broadcast by a base station (BS) on a narrowband Internet of Things cell; receiving an RRCConnectionReconfiguration-NB message indicating a full configuration from the base station on the narrowband Internet of Things cell; and using multiple values for timers T301, T310, T311 and constants N310, N311 to respond to the RRCConnectionReconfiguration-NB message, wherein the multiple values are included in the SystemInformationBlockType2-NB message.
[0006] The present invention further discloses a communication device for processing a narrowband Internet of Things communication, the communication device comprising a storage device for storing instructions, and a processing circuit coupled to the storage device. The processing circuit is configured to execute instructions stored in the storage device. The instructions include initializing a radio resource control connection reestablishment procedure for a narrowband Internet of Things communication; when initializing the radio resource control connection reestablishment procedure, selecting a narrowband Internet of Things cell; receiving a SystemInformationBlockType2-NB message broadcast by the narrowband Internet of Things cell; and using a timeAlignmentTimerCommon contained in the SystemInformationBlockType2-NB message for an uplink (UL) transmission.
[0007] The present invention further discloses a communication device for processing a narrowband Internet of Things communication, the communication device comprising a storage device for storing instructions, and a processing circuit coupled to the storage device. The processing circuit is configured to execute instructions stored in the storage device. The instructions include initializing a radio resource control connection reestablishment procedure for a narrowband Internet of Things communication; when initializing the radio resource control connection reestablishment procedure, selecting a long term evolution (LTE) cell; and when selecting the LTE cell, terminating the radio resource control connection reestablishment procedure and entering an idle mode. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] Figure 1 FIG. 1 is a schematic diagram of a wireless communication system according to an embodiment of the present invention.
[0009] Figure 2 FIG. 1 is a schematic diagram of a communication device according to an embodiment of the present invention.
[0010] Figure 3 The figure is a flow chart of a process of an embodiment of the present invention.
[0011] Figure 4 The figure is a flow chart of a process of an embodiment of the present invention.
[0012] Figure 5 The figure is a flow chart of a process of an embodiment of the present invention.
[0013] Figure 6 The figure is a flow chart of a process of an embodiment of the present invention.
[0014] Figure 7 The figure is a flow chart of a process of an embodiment of the present invention. DETAILED DESCRIPTION
[0015] Figure 1 FIG. 1 is a schematic diagram of a wireless communication system 10 according to an embodiment of the present invention. The wireless communication system 10 may be simply composed of a network and a plurality of communication devices. The network and the communication devices may communicate with each other through a cell on one or more carriers.
[0016] exist Figure 1In the figure, the network and the communication device are used to illustrate the architecture of the wireless communication system 10. The network may include a radio access network (RAN), which includes at least one base station (BS). The radio access network may be a Universal Terrestrial Radio Access Network (UTRAN), which includes at least one evolved Node-B (eNB). The radio access network may be a fifth generation (5G) network, which includes at least one fifth generation base station (e.g., gNB). The fifth generation base station may utilize orthogonal frequency-division multiplexing (OFDM) and / or non-OFDM, and a transmission time interval (TTI) of less than 1 millisecond (ms) (e.g., 100 ms or 200 ms) to communicate with the communication device. Generally speaking, the base station (BS) can be any one of an evolved base station and a fifth generation base station. In addition, the network end can include a core network, wherein the core network includes network entities connected to a radio access network.
[0017] The communication device may be a user equipment (UE), a narrowband Internet of Things (NB-IoT) user terminal, a machine type communication (MTC) device, a mobile phone, a notebook computer, a tablet computer, an e-book, a portable computer system, a vehicle, and an aircraft. In addition, according to the transmission direction, the network end and the communication device may be regarded as a transmitter or a receiver, respectively. For example, for an uplink (UL), the communication device is the transmitter and the network end is the receiver; for a downlink (DL), the network end is the transmitter and the communication device is the receiver.
[0018] Figure 2 FIG. 2 is a schematic diagram of a communication device 20 according to an embodiment of the present invention. The communication device 20 may be Figure 1. The communication device 20 may include a processing circuit 200, a storage device 210, and a communication interface device 220. The processing circuit 200 may be a microprocessor or an application-specific integrated circuit (ASIC). The storage device 210 may be any data storage device for storing a program code 214, and the processing circuit 200 may read and execute the program code 214 through the storage device 210. For example, the storage device 210 may be a subscriber identity module (SIM), a read-only memory (ROM), a flash memory, a random-access memory (RAM), a hard disk, an optical data storage device, a non-volatile storage device, a non-transitory computer-readable medium (such as a tangible media), etc., but is not limited thereto. The communication interface device 220 may be a wireless transceiver, which is used to transmit and receive signals (such as data, messages and / or packets) according to the processing results of the processing circuit 200 .
[0019] To simplify the description, in the following embodiments, the user terminal is used to represent Figure 1 The communication device in.
[0020] The following describes a scenario assumed according to an embodiment of the present invention. A NB-IoT user terminal is configured with a radio resource control connection by a base station. When the NB-IoT user terminal receives an RRCConnectionReconfiguration-NB message indicating a complete configuration but not including a mobilityControlInfo, the user terminal uses the values for timers T301, T310, T311 and constants N310, N311 included in ue-TimersAndConstants received in SystemInformationBlockType2. However, because the NB-IoT user terminal is unable to perform long-term evolution communication, the NB-IoT user terminal cannot receive SystemInformationBlockType2. Therefore, the user terminal does not have values for timers T301, T310, T311 and constants N310, N311.
[0021] Figure 3 30 is a flow chart of a process 30 according to an embodiment of the present invention. The process 30 is used in a user terminal (such as a narrowband Internet of Things user terminal) to communicate with a base station (such as Figure 1 Process 30 may include the following steps:
[0022] Step 300: Start.
[0023] Step 302: Receive a SystemInformationBlockType2-NB message broadcast by a base station in a narrowband IoT cell.
[0024] Step 304: Receive an RRCConnectionReconfiguration-NB message indicating a full configuration from the base station on the NB-IoT cell.
[0025] Step 306: Use multiple values for timers T301, T310, T311 and constants N310, N311 to respond to the RRCConnectionReconfiguration-NB message, where the multiple values are included in the SystemInformationBlockType2-NB message.
[0026] Step 308: End.
[0027] According to process 30, the user end receives a SystemInformationBlockType2-NB message broadcasted by a base station on a narrowband IoT cell. The user end receives an RRCConnectionReconfiguration-NB message indicating a full configuration from a base station on the narrowband IoT cell. The user end uses (e.g., applies) multiple values for timers T301, T310, T311 and constants (e.g., for counters) N310, N311 to respond to the RRCConnectionReconfiguration-NB message, wherein the multiple values are included in the SystemInformationBlockType2-NB message. Therefore, the problem occurring in the above scenario can be solved.
[0028] The implementation of process 30 is not limited to the above. The following embodiments may be used for process 30.
[0029] When starting the timer, the UE uses the values included in the SystemInformationBlockType2-NB message. When counting the number of consecutive "out-of-sync" indications for the NB-IoT cell, the UE uses the constant for N310 in the SystemInformationBlockType2-NB. When counting the number of consecutive "in-sync" indications for the NB-IoT cell, the UE uses the constant for N311 in the SystemInformationBlockType2-NB. In one embodiment, when N310 consecutive "out-of-sync" indications for the NB-IoT cell are detected, the UE starts the timer T310. When the timer T310 expires, the UE starts the timer T311. When the timer T311 is running and the UE selects the NB-IoT cell, the UE starts the timer T301. When N311 consecutive "in-sync" indications for the NB-IoT cell are detected, the UE stops the timer T310.
[0030] The following describes a scenario assumed according to an embodiment of the present invention. A NB-IoT UE is configured with a radio resource control connection and a data radio bearer (DRB) by a base station. The NB-IoT UE can detect a failure (e.g., radio link failure (RLF)) on a radio link with the base station, and can initiate a radio resource control connection reestablishment procedure. When the NB-IoT UE selects a NB-IoT cell, the NB-IoT UE fails to receive SystemInformationBlockType2 which is broadcast only in the LTE cell. Therefore, the NB-IoT UE fails to apply timeAlignmentTimerCommon included in SystemInformationBlockType2.
[0031] Figure 4 40 is a flow chart of a process 40 according to an embodiment of the present invention. The process 40 is used in a user terminal (such as a narrowband Internet of Things user terminal) to communicate with a base station (such as Figure 1 The process 40 may include the following steps:
[0032] Step 400: Start.
[0033] Step 402: Initiate a radio resource control connection reestablishment procedure for a narrowband IoT communication.
[0034] Step 404: When initializing the RRC connection reestablishment procedure, a narrowband IoT cell is selected.
[0035] Step 406: Receive a SystemInformationBlockType2-NB message broadcast by the narrowband IoT cell.
[0036] Step 408: Use a timeAlignmentTimerCommon included in the SystemInformationBlockType2-NB message for an uplink transmission.
[0037] Step 410: End.
[0038] According to process 40, the user end initializes the radio resource control connection reestablishment procedure for narrowband Internet of Things communication. When initializing the radio resource control connection reestablishment procedure, the user end selects a narrowband Internet of Things cell. The user end receives the SystemInformationBlockType2-NB message broadcast by the narrowband Internet of Things cell. The user end uses (for example, applies) the timeAlignmentTimerCommon contained in the SystemInformationBlockType2-NB. Then, the user end transmits RRCConnectionReestablishmentRequest-NB to the narrowband Internet of Things cell, receives RRCConnectionReestablishment-NB from the narrowband Internet of Things cell, and transmits RRCConnectionReestablishmentRequest-NB to the narrowband Internet of Things cell. Therefore, the problems occurring in the above scenario can be solved.
[0039] The implementation of process 40 is not limited to the above. The following embodiments may be used for process 40.
[0040] In one embodiment, the step of using timeAlignmentTimerCommon includes, when applying a timing advance command received from the narrowband IoT cell, the user terminal starts a time alignment timer according to (for example, using) a value in timeAlignmentTimerCommon. In addition, the narrowband IoT cell transmits a random access response including a time advance command to the user terminal in response to a random access preamble received from the user terminal. After receiving the random access response, the user terminal transmits an RRCConnectionReestablishmentRequest-NB. In one embodiment, after performing a radio resource control connection reestablishment procedure with the user terminal, the narrowband IoT cell transmits a media access control (MAC) protocol data unit (PDU) including a timing advance command to the user terminal. In the above embodiments, the operation of the narrowband IoT cell may imply the corresponding operation of the user terminal, which is not repeated here.
[0041] In one embodiment, process 30 may be combined with process 40. After completing the radio resource control connection reestablishment procedure with the narrowband IoT cell, the user terminal receives an RRCConnectionReconfiguration-NB message indicating a complete configuration from the narrowband IoT cell. The user terminal responds to the RRCConnectionReconfiguration-NB message using the values for timers T301, T310, T311 and constants N310, N311, wherein the values are included in the SystemInformationBlockType2-NB message.
[0042] The following describes a scenario assumed according to an embodiment of the present invention. A narrowband IoT user terminal is configured with a radio resource control connection and a data radio bearer by a first base station. The narrowband IoT user terminal may detect a failure in a radio link with the first base station (e.g., a radio link failure), and may initiate a radio resource control connection reestablishment procedure in response to the radio link failure. The narrowband IoT user terminal may select a long-term evolution cell of a second base station, and if the narrowband IoT user terminal supports long-term evolution communication in addition to narrowband IoT communication, may send an RRCConnectionReestablishmentRequest message to the long-term evolution cell. However, because the second base station does not have the long-term evolution context of the narrowband IoT user terminal, the second base station may send an RRCConnectionReestablishmentReject message to the narrowband IoT user terminal on the long-term evolution cell. It should be noted that the first base station and the second base station may be the same base station or different base stations.
[0043] Figure 5 is a flow chart of a process 50 according to an embodiment of the present invention. The process 50 is used in a user terminal (such as a narrowband Internet of Things user terminal) to communicate with a base station (such as Figure 1 Process 50 may include the following steps:
[0044] Step 500: Start.
[0045] Step 502: Initialize a radio resource control connection reestablishment procedure for a narrowband IoT communication.
[0046] Step 504: When the RRC connection reestablishment procedure is initiated, a LTE cell is selected.
[0047] Step 506: When the LTE cell is selected, terminate the RRC connection reestablishment procedure and enter an idle mode.
[0048] Step 508: End.
[0049] In one embodiment, the UE initiates a RRC connection reestablishment procedure due to detecting a radio link failure on a NB-IoT cell. The UE selects a LTE cell (e.g., because the UE cannot find any NB-IoT cell) in response to the RRC connection reestablishment procedure.
[0050] In one embodiment, when a long-term evolution cell is selected, the user end initiates a radio resource control connection reestablishment procedure by transmitting an RRCConnectionRequest message to the long-term evolution cell. That is, the user end transmits an RRCConnectionRequest message to the long-term evolution cell instead of an RRCConnectionReestablishmentRequest message. The user end receives an RRCConnectionSetup message from the long-term evolution cell in response to the RRCConnectionRequest message. Therefore, the user end does not need to perform a radio resource control connection reestablishment procedure for long-term evolution communication. The time for performing the radio resource control connection reestablishment procedure can be saved.
[0051] The following describes a scenario assumed according to an embodiment of the present invention. A user terminal is configured with a radio resource control connection and a data radio bearer by a first base station through long-term evolution communication. The user terminal can detect a failure in the radio link with the first base station (e.g., a radio link failure), and can initialize a radio resource control connection reestablishment procedure in response to the radio link failure. The user terminal can select a narrowband IoT cell of a second base station, and if the user terminal supports narrowband IoT communication, can send an RRCConnectionReestablishmentRequest message to the narrowband IoT cell. However, because the second base station does not have the narrowband IoT background setting of the user terminal, the second base station can send an RRCConnectionReestablishmentReject message to the user terminal on the narrowband IoT cell. It should be noted that the first base station and the second base station can be the same base station or different base stations.
[0052] Figure 6 60 is a flow chart of a process 60 according to an embodiment of the present invention. The process 60 is used in a user terminal (such as a narrowband Internet of Things user terminal) to communicate with a base station (such as Figure 1 Process 60 may include the following steps:
[0053] Step 600: Start.
[0054] Step 602: Initiate a radio resource control connection reestablishment procedure for a long term evolution communication.
[0055] Step 604: When initializing the RRC connection reestablishment procedure, select a narrowband IoT cell.
[0056] Step 606: When the narrowband IoT cell is selected, terminate the radio resource control connection reestablishment procedure and enter an idle mode.
[0057] Step 608: End.
[0058] In one embodiment, the UE initiates a RRC connection reestablishment procedure due to detecting a radio link failure on the LTE cell. The UE selects a narrowband IoT cell (e.g., because the UE cannot find any LTE cell) in response to the RRC connection reestablishment procedure.
[0059] In one embodiment, when a narrowband IoT cell is selected, the user terminal initializes the radio resource control connection reestablishment procedure by sending an RRCConnectionRequest-NB message to the narrowband IoT cell. That is, the user terminal sends an RRCConnectionRequest-NB message to the narrowband IoT cell instead of an RRCConnectionReestablishmentRequest-NB message. The user terminal receives an RRCConnectionSetup-NB message from the narrowband IoT cell in response to the RRCConnectionRequest-NB message. Therefore, the user terminal does not need to perform the radio resource control connection reestablishment procedure for narrowband IoT communication. The time for performing the radio resource control connection reestablishment procedure can be saved.
[0060] The following describes a scenario assumed according to an embodiment of the present invention: Because NB-IoT communication does not support mobility in connected mode, a NB-IoT UE in connected mode cannot be handed over from one cell to another.
[0061] Figure 7 70 is a flow chart of a process 70 according to an embodiment of the present invention. The process 70 is used in a user terminal (such as a narrowband Internet of Things user terminal) to communicate with a base station (such as Figure 1 Process 70 may include the following steps:
[0062] Step 700: Start.
[0063] Step 702: In a first NB-IoT cell, receive a handover command indicating a handover to a second NB-IoT cell.
[0064] Step 704: Synchronize to a downlink of the second narrowband IoT cell.
[0065] Step 706: When synchronizing to the downlink of the second narrowband IoT cell, decode a narrowband physical broadcast channel (NPBCH) and obtain a MasterInformationBlock-NB on the narrowband physical broadcast channel.
[0066] Step 708: Determine at least one time-frequency resource according to a random access configuration in the handover command and according to a system frame number (SFN) including a first plurality of bits and a second plurality of bits, wherein the first plurality of bits are included in the MasterInformationBlock-NB, and the second plurality of bits are derived by the user terminal according to a result of decoding the narrowband physical broadcast channel.
[0067] Step 710: Send a random access preamble to the second narrowband IoT cell on the at least one time-frequency resource.
[0068] Step 712: Receive a random access response including an uplink grant from the second NB-IoT cell.
[0069] Step 714: Send a handover completion message to the second narrowband IoT cell according to the uplink grant.
[0070] Step 716: End.
[0071] According to process 70 , the problem occurring in the above scenario can be solved.
[0072] In order to synchronize to the downlink of the second NB-IoT cell, the UE may synchronize to at least one downlink transmission or at least one downlink reference signal.
[0073] In one embodiment, the narrowband physical broadcast channel carries the MasterInformationBlock-NB and is transmitted in subframe #0 of each frame through the base station on the narrowband IoT cell. The MasterInformationBlock-NB remains unchanged over the transmission time interval of 640 milliseconds (e.g., 64 radio frames). The base station scrambles Mbit, which represents the number of bits transmitted on the narrowband physical broadcast channel (e.g., the encoded MasterInformationBlock-NB). In radio frames that meet the system frame number mode 64=0, the scrambling sequence should be Initialization. After performing scrambling, the base station uses Quadrature Phase Shift Keying (QPSK) modulation to modulate the scrambled Mbits into complex symbols. Then, the base station maps the complex symbols to resource elements as follows.
[0074] The complex symbol y for each antenna port (p)(0),...,y (p) (M symb -1) When n is satisfied f mod64=0 is transmitted in subframe 0 during 64 consecutive radio frames starting from each radio frame, and can be transmitted from y (p) (0) to a sequence of resource elements (k, l). The mapping relationship of resource elements (k, l) not reserved for transmission of reference signals may be in an ascending order of first index k and then index l. After mapping to a subframe, the subframe may be repeated in subframe 0 of the next 7 radio frames before continuing to be mapped to subframe 0 in the following radio frame. The first three OFDM signals in the subframe are not used in the mapping process.
[0075] In one embodiment, based on the result of decoding the narrowband physical broadcast channel, the user end derives the second plurality of bits as follows. The user end identifies the boundary of 80 milliseconds (e.g., 8 radio frames) by decoding at least one of a narrowband primary synchronization signal (NPSS) and a narrowband secondary synchronization signal (NSSS), and identifies the position of the 80 millisecond period in the 640 millisecond transmission time interval by descrambling the narrowband physical broadcast channel according to (e.g., using) the scrambling sequence. That is, based on the position, the user end knows the boundary in the 640 millisecond transmission time interval. The user end derives the second plurality of bits (e.g., the least significant 6 bits) from the boundary in the 640 millisecond transmission time interval. When the user end obtains the MasterInformationBlock-NB, the user end obtains the first plurality of bits (e.g., the most significant 4 bits), and constructs the system frame number as these 10 bits (e.g., 4 bits plus 6 bits).
[0076] When the UE receives a handover command in the first LTE cell indicating a handover to the second LTE cell, the UE does not need to obtain the system frame number of the second LTE cell when determining the time-frequency resources for random access preamble transmission on the second LTE cell. When the UE is synchronized to the second LTE cell (e.g., frame synchronization), the UE determines the time and frequency resources (e.g., only) according to the random access configuration in the handover command. After receiving the random access response or after transmitting the handover complete message, after transmitting the random access preamble, the UE may obtain the system frame number.
[0077] A person skilled in the art can combine, modify or change the above-described embodiments according to the spirit of the present invention, but is not limited thereto. The above-described statements, steps and / or processes (including the suggested steps) can be implemented through a device, which can be hardware, software, firmware (a combination of a hardware device and computer instructions and data, and the computer instructions and data are read-only software on a hardware device), an electronic system, or a combination of the above devices. The device in the above-described embodiment can be a communication device 20. The above-described processes and embodiments can be compiled into program code 214.
[0078] In summary, the present invention provides an apparatus and method for processing narrowband IoT communications. By receiving system messages, the selection and handover procedures of narrowband IoT cells or long-term evolution cells can be correctly processed by the user end (or narrowband IoT user end).
[0079] The above description is only a preferred embodiment of the present invention. All equivalent changes and modifications made according to the scope of the patent application of the present invention should fall within the scope of the present invention.
[0080] [Explanation of symbols]
[0081] 10 Wireless Communication Systems
[0082] 20 Communication devices
[0083] 200 Processing circuit
[0084] 210 Storage Device
[0085] 214 Program code
[0086] 220 Communication interface device
[0087] 30, 40, 50, 60, 70 Process 300, 302, 304, 306, 308, 400, 402, 404, 406, 408, 410, 500,
[0090] 502, 504, 506, 508, 600, 602, Steps 604, 606, 608, 700, 702, 704, 706, 708, 710, 712, 714, 716
Claims
1. A communication device for processing a narrowband internet of things (NB-IoT) communication, the communication device comprising: A storage device, used to store the following instructions: Initializing a radio resource control connection reestablishment for a narrowband IoT communication (reestablishment) procedure; When initiating the RRC connection reestablishment procedure, selecting a narrowband IoT cell; Receive a SystemInformationBlockType2-NB message broadcast by the narrowband IoT cell; Sending an RRCConnectionReestablishmentRequest-NB to the NB-IoT cell; and using a timeAlignmentTimerCommon included in the SystemInformationBlockType2-NB message for an uplink (UL) transmission; and a processing circuit coupled to the storage device and configured to execute the instructions stored in the storage device; The instructions using the timeAlignmentTimerCommon include: When a timing advance command is received from the NB-IoT cell, a timing alignment timer is started according to a value in the timeAlignmentTimerCommon; The instruction also includes: Transmitting a random access preamble to the narrowband IoT cell; receiving a random access response including the timing advance command from the NB-IoT cell in response to the transmission of the random access preamble; and After receiving the random access response, the RRCConnectionReestablishmentRequest-NB.
2. The communication device as claimed in claim 1, wherein the The timeAlignmentTimerCommon directive contains: After executing the radio resource control connection reestablishment procedure with the narrowband IoT cell, a medium access control (MAC) protocol data unit (PDU) including the timing advance command is received from the narrowband IoT cell.
3. A communication method for processing a narrowband internet of things (NB-IoT) communication, the method comprising: Initializing a radio resource control connection reestablishment for a narrowband IoT communication (reestablishment) procedure; When initiating the RRC connection reestablishment procedure, selecting a narrowband IoT cell; Receive a SystemInformationBlockType2-NB message broadcast by the narrowband IoT cell; Sending an RRCConnectionReestablishmentRequest-NB to the NB-IoT cell; Using a timeAlignmentTimerCommon included in the SystemInformationBlockType2-NB message for an uplink (UL) transmission; The timeAlignmentTimerCommon used here includes: When a timing advance command is received from the NB-IoT cell, a timing alignment timer is started according to a value in the timeAlignmentTimerCommon; Transmitting a random access preamble to the narrowband IoT cell; receiving a random access response including the timing advance command from the NB-IoT cell in response to the transmission of the random access preamble; and After receiving the random access response, the RRCConnectionReestablishmentRequest-NB.
4. The communication method as claimed in claim 3, wherein the timeAlignmentTimerCommon includes: After executing the radio resource control connection reestablishment procedure with the narrowband IoT cell, a medium access control (MAC) protocol data unit (PDU) including the timing advance command is received from the narrowband IoT cell.
