WO2021026739A1

WO2021026739A1 - Radio network temporary identifier (rnti) update method and device

Info

Publication number: WO2021026739A1
Application number: PCT/CN2019/100269
Authority: WO
Inventors: 王宏; 李秉肇; 王学龙; 陈磊; 许斌
Original assignee: 华为技术有限公司
Priority date: 2019-08-12
Filing date: 2019-08-12
Publication date: 2021-02-18

Abstract

An RNTI update method and device. In the method, after informing a terminal device of a first RNTI used for performing data transmission in an RRC idle state, a network device can also inform the terminal device of a second RNTI used for performing data transmission after switching to an RRC connected state. By means of the method, a network device can update the RNTI of a terminal device, and the terminal device can be prevented from using the same RNTI in an RRC idle state and an RRC connected state, such that the phenomenon of a plurality of terminal devices that perform data transmission in the RRC idle state having an RNTI conflict can be avoided, and finally, normal resource scheduling and data transmission for the terminal device can be ensured.

Description

Method and equipment for updating wireless network temporary identification RNTI

Technical field

This application relates to the field of communication technology, and in particular to an RNTI update method and equipment.

Background technique

With the increase in the diversity of communication services, some services do not pursue data transmission rates, multi-frequency bands, multi-antennas, and full-duplex transmission, but pursue longer terminal equipment battery life and lower terminal equipment costs. Terminal equipment is required to achieve low power consumption and low cost, such as machine type communication (MTC) services, narrowband internet of things (NB-IoT) services, etc. .

Currently, different states of radio resource control (Radio Resource Control, RRC) connections are defined between terminal equipment and network equipment. Generally, when the terminal device has no uplink data or downlink data to transmit, the terminal device is in the RRC idle state (RRC idle) or RRC inactive state (RRC inactive); when the terminal device has uplink data or downlink data to transmit, the terminal device It is in RRC connected state (RRC connected).

Generally, the terminal device needs to go through a random access process to switch from the RRC idle state or the RRC inactive state to the RRC connected state. In the random access process, the terminal device establishes/recovers through the RRC connection establishment/recovery process. The RRC connection with the network device is restored, so that the terminal device enters the RRC connected state. In the RRC connection state, the terminal device and the network device can perform uplink and downlink data transmission. The traditional random access process includes four steps:

S1: The terminal device sends a random access preamble (also called message 1 (message1, msg1)) to the network device.

S2: The network device sends a random access response (RAR) message (also called message 2 (message 2, msg2)) to the terminal device. Wherein, the message 2 carries uplink timing advance (TA) and uplink grant (UL Grant) information, and a radio network temporary identifier (RNTI) allocated to the terminal device. It should be noted that in the subsequent S3, S4, and the terminal equipment entering the RRC connection state through this random access process to perform data transmission with the network equipment, the RNTI is used for transmission scheduling, that is, during the data transmission process The medium network device no longer updates the RNTI of the terminal device.

S3: The terminal device sends a message 3 (message3, msg3) to the network device according to the TA and uplink authorization information, where the message 3 is scrambled using the RNTI.

S4: The network device sends a contention resolution message (also called message 4 (message 4, msg4)) to the terminal device.

In some services, terminal devices only need to transmit a small amount of data. In order to further improve the data transmission efficiency of these terminal devices, the terminal devices can perform data transmission in the RRC idle state.

For example, when the amount of downlink data is small, the network device can transmit the downlink data to the terminal device through S2 similar to the above-mentioned random access process.

For another example, the communication system introduces early data transmission (EDT) technology. Through EDT technology, the terminal device can complete data transmission in the random access process without establishing/resuming the RRC connection. That is, the uplink data of the terminal device can be carried in message 3 for transmission, and the downlink data can be carried in message Msg4 for transmission. transmission.

For another example, a method in which a terminal device sends uplink data on a preconfigured uplink resource (PUR). For MTC and NB-IoT terminal devices, especially some low-mobility or stationary terminal devices (for example, water meters, electricity meters, street lights, etc.), their data transmission volume is small and has a certain periodicity. In order to further improve the data transmission efficiency of these low-mobility terminal devices, based on the above-mentioned EDT technology, the above-mentioned method of sending uplink data on PUR is proposed, which does not require the two steps S1 and S2 in the random access process. It can directly carry out the process similar to S3 and S4 for uplink and downlink data transmission. In this method, the network device will send the configuration information of the pre-configured uplink resource to the terminal device when the terminal device is in the RRC connected state, so that the terminal device can use the above-mentioned pre-configured uplink resource for data after entering the RRC idle state later. transmission.

In the above method, since the network equipment needs to use the RNTI to schedule the data transmission of the terminal equipment, the network equipment will pre-allocate an RNTI for the terminal equipment for the terminal equipment to perform data transmission in the RRC idle state. Since the number of available RNTIs is limited and the RNTI is pre-allocated, the network device may allocate the same RNTI to multiple terminal devices. Generally, the amount of data transmitted by terminal equipment is small, so the time for terminal equipment to use this RNTI for data transmission is shorter. Even if multiple terminal equipment is assigned the same RNTI, multiple terminal equipment uses the same RNTI at the same time. The probability of data transmission (ie, RNTI collision) is low.

However, in some cases, when the terminal device uses the foregoing method to perform data transmission in the idle state, the network device may have a large amount of data to be sent to the terminal device. At this time, the terminal device needs to enter the RRC connection state for data transmission. Since the network device may allocate the same RNTI to multiple terminal devices, if at least one terminal device of the multiple terminal devices needs to enter the RRC connected state, it will appear that the at least one terminal device is always used in the RRC connected state The phenomenon that the RNTI uses the same RNTI at a certain moment with other terminal devices also assigned the RNTI, that is, an RNTI conflict occurs, which will further cause the transmission scheduling of the at least one terminal device to conflict with other terminal devices that use the same RNTI , Thereby affecting the data transmission of the terminal equipment using the RNTI.

Summary of the invention

The embodiments of the present application provide an RNTI update method and device, which are used to update the RNTI of a terminal device that can perform data transmission in an RRC idle state, so as to avoid RNTI conflict.

In the first aspect, the embodiments of the present application provide an RNTI update method, which can be applied to the communication system as shown in FIG. 1. The method includes: a network device sends a first message to a terminal device, where the first message is used to notify the terminal device of a first RNTI allocated by the network device to the terminal device, and the first RNTI is used for The terminal device performs data transmission in the radio resource control RRC idle state; afterwards, the network device sends a second message to the terminal device in the RRC idle state of the terminal device, where the second message is used to notify The second RNTI allocated to the terminal device by the terminal device and the network device, where the second RNTI is used for the terminal device to perform data transmission after switching from the RRC idle state to the RRC connected state.

In the above method, after notifying the terminal device of the first RNTI used for data transmission in the RRC idle state, the network device may also notify the terminal device of the second RNTI used for data transmission after switching to the RRC connected state. With this method, the network device can update the RNTI of the terminal device, which can prevent the terminal device from using the same RNTI in the RRC idle state and the RRC connected state, thereby avoiding multiple terminal devices capable of data transmission in the RRC idle state The occurrence of RNTI conflicts can ultimately ensure normal resource scheduling and data transmission for terminal equipment.

In a possible design, the first message includes the first RNTI; or, the first message includes first indication information, and the first indication information is used to indicate the first RNTI. With this design, the network device can notify the terminal device of the first RNTI in multiple ways.

In a possible design, the first indication information indicates that the first RNTI is the RNTI used when the network device sends the first message; or, the first indication information indicates the first RNTI Is the third RNTI, which is allocated by the network device to the terminal device before sending the first message to the terminal device, and the third RNTI is used when the terminal device is idle in RRC Or, the first indication information indicates that the first RNTI is the RNTI used in the current RRC connected state, or the first indication information indicates that the first RNTI is the terminal device and the The RNTI currently used by the network equipment. Through this design, the network device can improve the flexibility of indicating the first RNTI.

In a possible design, the first message further includes configuration information of a target resource, and the target resource is a resource used by the terminal device during data transmission in an RRC idle state. Through this design, the signaling interaction between the network device and the terminal device can be reduced.

In a possible design, after the network device sends the first message to the terminal device, the network device receives a third message sent by the terminal device using the first RNTI in the RRC idle state , The third message carries uplink data. Through this design, the network device can send uplink data in the RRC idle state of the terminal device.

In a possible design, the second message includes the second RNTI; or, the second message includes second indication information, and the second indication is used to indicate the second RNTI. With this design, the network device can notify the terminal device of the second RNTI in a variety of ways.

In a possible design, the second indication information indicates that the second RNTI is the first RNTI; or, the second indication information indicates that the second RNTI is the network device sending the first RNTI; The fourth RNTI used in the second message. Through this design, the network device can improve the flexibility of indicating the second RNTI.

In a possible design, the network device uses the first RNTI to send the second message to the terminal device.

In a possible design, the network device determines the fourth RNTI corresponding to the target resource according to the target resource and the mapping relationship between the resource and the RNTI, where the mapping relationship between the resource and the RNTI is the Agreed upon by the network device and the terminal device; the network device uses the fourth RNTI to send the second message to the terminal device.

In a possible design, after the network device sends the second message to the terminal device, the network device sends a fourth message to the terminal device, where the fourth message includes uplink authorization information, The uplink grant information is used by the terminal device to perform uplink data transmission when switching from the RRC idle state to the RRC connected state. Through this design, the network device can send uplink authorization information to the terminal, so that the terminal device can use the authorized resource indicated by the uplink authorization information to perform uplink data transmission in the RRC connected state.

In a possible design, the network device uses the second RNTI to send the fourth message to the terminal device; or, the network device uses the first RNTI to send the fourth message to the terminal device A fourth message; or alternatively, the network device uses the fourth RNTI to send the fourth message to the terminal device. It should be noted that the RNTI used for sending the fourth message is stipulated in advance or agreed between the network device and the terminal device.

In a possible design, the second message includes uplink grant information, and the uplink grant information is used by the terminal device to perform uplink data transmission after switching from the RRC idle state to the RRC connected state. In some cases, the network device may erroneously decode the NACK sent by the terminal device for the second message into an ACK. At this time, the network device determines that the terminal device successfully received the TB corresponding to the second message, resulting in the terminal device not successfully receiving The second message, the second RNTI cannot be determined. In order to prevent the network device from erroneously decoding the NACK sent by the terminal device into an ACK, causing the terminal device to fail to successfully receive the second message and thus fail to determine the second RNTI, the network device may The uplink authorization information is carried in the second message. In this way, it can be ensured that the RNTI used by the terminal device and the network device can be synchronized, and the problem of scheduling failure caused by non-synchronization of the RNTI can be avoided. In this process, the network device sends a second message to the terminal device. The second message includes downlink data (optional), uplink authorization information, and second indication information/second RNTI, where the second indication information is used to indicate The second RNTI. In this implementation manner, the terminal device and the network device may also start to use the second RNTI for data transmission when the terminal device enters the RRC connected state.

In a possible design, after the network device sends the second message to the terminal device, the network device receives that the terminal device uses the first message after switching from the RRC idle state to the RRC connected state. 2. The fourth message sent by RNTI.

In a possible design, the first message is a paging message, and the first message includes a random access preamble indicating early data transmission and the first RNTI used for early data transmission. Through this design, the network device can notify the terminal device of the first RNTI in the MT-EDT scenario, and notify the terminal device to perform early data transmission.

In a possible design, after the network device sends the first message to the terminal device, the network device receives the random access sent by the terminal device in the RRC idle state of the terminal device. Entering the preamble indicates that the terminal device is ready for early data transmission.

In a possible design, after the network device sends the second message to the terminal device, the network device uses the first RNTI to receive a fourth message from the terminal device; After the device switches from the RRC idle state to the RRC connected state, the network device and the terminal device use the second RNTI for data transmission. Through this design, the network device and the terminal device use the first RNTI to transmit a fourth message. After the fourth message transmission is completed, the network device and the terminal device start to use the second RNTI for data Transmission can ensure that the RNTI used by the network device and the terminal device are the same, and avoid the phenomenon that the RNTI used by the network device and the terminal device are different.

In a possible design, the second message further includes uplink authorization information. In this way, when the network device receives the third message sent by the terminal device on the time-frequency resource indicated by the uplink authorization information, the network device can determine that the terminal device successfully receives the second message Since the second message carries the second RNTI/second indication information, the network device can determine that the terminal device successfully determines the second RNTI. Then, the network device sends ACK feedback information to the terminal device, so that the terminal device can determine that the network device successfully receives the third message, and the terminal device and the network device can start to use the second RNTI. In this way, it can be ensured that the RNTI used by the terminal device and the network device can be synchronized (that is, the same RNTI is used), and the problem of scheduling failure caused by the unsynchronized RNTI (that is, using different RNTI) can be avoided.

In the second aspect, embodiments of the present application provide an RNTI update method, which may be applicable to the communication system shown in FIG. 1. The method includes:

The terminal device receives a first message from the network device, where the first message is used to notify the terminal device of the first RNTI allocated by the network device to the terminal device, and the first RNTI is used for the terminal device Data transmission is performed in the radio resource control RRC idle state; the terminal device receives a second message from the network device in the RRC idle state, where the second message is used to notify the terminal device that the network device is allocated to all The second RNTI of the terminal device, where the second RNTI is used for the terminal device to perform data transmission after switching from the RRC idle state to the RRC connected state.

In a possible design, the first message includes the first RNTI; or, the first message includes first indication information, and the first indication information is used to indicate the first RNTI.

In a possible design, the first indication information indicates that the first RNTI is the RNTI used when the network device sends the first message; or, the first indication information indicates the first RNTI Is the third RNTI, which is allocated by the network device to the terminal device before sending the first message to the terminal device, and the third RNTI is used when the terminal device is idle in RRC Or the first indication information indicates that the first RNTI is the RNTI used in the current RRC connected state; or, the first indication information indicates that the first RNTI is the terminal device and the The RNTI currently used by the network device.

In a possible design, the first message further includes configuration information of a target resource, and the target resource is a resource used by the terminal device during data transmission in an RRC idle state.

In a possible design, after the terminal device receives the first message from the network device, the terminal device is in the RRC idle state and uses the first RNTI to send a third message to the network device , The third message carries uplink data.

In a possible design, the second message includes the second RNTI; or, the second message includes second indication information, and the second indication is used to indicate the second RNTI.

In a possible design, the second indication information indicates that the second RNTI is the first RNTI; or, the second indication information indicates that the second RNTI is the network device sending the first RNTI; The fourth RNTI used in the second message.

In a possible design, the terminal device uses the first RNTI to receive the second message from the network device.

In a possible design, the terminal device determines the fourth RNTI corresponding to the target resource according to the target resource and the mapping relationship between the resource and the RNTI, where the mapping relationship between the resource and the RNTI is the Agreed upon by the network device and the terminal device; the terminal device uses the fourth RNTI to receive the second message from the network device.

In a possible design, after the terminal device receives the second message from the network device, the terminal device receives a fourth message from the network device, where the fourth message includes uplink authorization information, The uplink grant information is used for the terminal equipment to perform uplink data transmission after switching from the RRC idle state to the RRC connected state.

In a possible design, the terminal device uses the second RNTI to receive the fourth message from the network device; or, the terminal device uses the first RNTI to receive the fourth message from the network device A fourth message; or, the terminal device uses the fourth RNTI to receive the fourth message from the network device.

In a possible design, the second message includes uplink grant information, and the uplink grant information is used by the terminal device to perform uplink data transmission after switching from the RRC idle state to the RRC connected state.

In a possible design, after the terminal device receives the second message from the network device, after the terminal device switches from the RRC idle state to the RRC connected state, it uses the second RNTI to send the The network device sends the fourth message.

In a possible design, the first message is a paging message, and the first message includes a random access preamble and the first RNTI.

In a possible design, after the terminal device receives the first message from the network device, the method further includes: the terminal device sends the random access to the network device in the RRC idle state. Enter the preamble.

In a possible design, after the terminal device receives the second message from the network device, the terminal device uses the first RNTI to send a fourth message to the network device, and the fourth message The message is used to indicate that the terminal device has established or resumed an RRC connection; after the terminal device switches from the RRC idle state to the RRC connected state, the terminal device uses the second RNTI to perform data transmission with the network device.

In a third aspect, an embodiment of the present application provides a communication device, which includes a unit for executing each step in the above first aspect or second aspect.

In a fourth aspect, an embodiment of the present application provides a communication device, including at least one processing element and at least one storage element, wherein the at least one storage element is used to store programs and data, and the at least one processing element is used to execute the first The method provided in one aspect or the second aspect.

In a fifth aspect, an embodiment of the present application also provides a communication system, including a network device used to implement the method provided in the first aspect of the present application, and a terminal device used to implement the method provided in the second aspect of the present application.

In a sixth aspect, the embodiments of the present application also provide a computer program, which when the computer program runs on a computer, causes the computer to execute the method provided in any of the foregoing aspects.

In a seventh aspect, an embodiment of the present application also provides a computer storage medium in which a computer program is stored, and when the computer program is executed by a computer, the computer is caused to execute the method provided in any of the above aspects .

In an eighth aspect, an embodiment of the present application also provides a chip, which is used to read a computer program stored in a memory and execute the method provided in any one of the foregoing aspects.

In a ninth aspect, an embodiment of the present application also provides a chip system, which includes a processor, and is configured to support a computer device to implement the method provided in any one of the foregoing aspects. In a possible design, the chip system further includes a memory, and the memory is used to store necessary programs and data of the computer device. The chip system can be composed of chips, or can include chips and other discrete devices.

Description of the drawings

FIG. 1 is an architecture diagram of a communication system provided by an embodiment of this application;

Figure 2 is a flow chart for establishing an RRC connection provided by an embodiment of the application;

FIG. 3 is a flowchart of restoring an RRC connection provided by an embodiment of the application;

FIG. 4 is an example flow chart of a terminal device performing data transmission in an RRC idle state (that is, an UP MO-EDT method) according to an embodiment of the application;

FIG. 5 is an example flowchart of a terminal device performing data transmission in an RRC idle state (that is, a CP MO-EDT method) according to an embodiment of the application;

FIG. 6 is an example flow chart of a terminal device performing data transmission in an RRC idle state (that is, PUR-based data transmission) according to an embodiment of the application;

FIG. 7 is an example flow chart of a terminal device performing data transmission in an RRC idle state (that is, an MT-EDT method) according to an embodiment of the application;

FIG. 8 is a flowchart of an RNTI update method provided by an embodiment of the application;

FIG. 9 is a flowchart of an RNTI update example provided by an embodiment of the application;

FIG. 10 is a flowchart of an RNTI update example provided by an embodiment of this application;

FIG. 11 is a flowchart of an RNTI update example provided by an embodiment of this application;

FIG. 12 is a flowchart of an RNTI update example provided by an embodiment of the application;

FIG. 13 is a schematic diagram of the effective time of the target resource provided by an embodiment of the application;

14 is a schematic diagram of the effective number of target resources provided by an embodiment of the application;

15 is a structural diagram of a communication device provided by an embodiment of this application;

FIG. 16 is a structural diagram of a communication device provided by an embodiment of this application;

FIG. 17 is a structural diagram of a network device provided by an embodiment of this application;

FIG. 18 is a structural diagram of a terminal device provided by an embodiment of this application.

detailed description

This application provides an RNTI update method and device, which are used for terminal equipment capable of data transmission in the RRC idle state to update the RNTI, so as to avoid RNTI conflict. Among them, the method and the device are based on the same inventive concept. Since the principles of the method and the device to solve the problem are similar, the implementation of the device and the method can be referred to each other, and the repetition will not be repeated.

Hereinafter, some terms in this application are explained to facilitate the understanding of those skilled in the art.

1) Terminal equipment is a device that provides users with voice and/or data connectivity. Terminal equipment may also be called user equipment (UE), mobile station (MS), mobile terminal (MT), and so on.

For example, the terminal device may be a handheld device with a wireless connection function, a vehicle-mounted device, a smart meter, a smart water meter, infrastructure, multimedia equipment, streaming media equipment, etc. At present, some examples of terminal devices are: mobile phones (mobile phones), tablet computers, notebook computers, handheld computers, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented Augmented reality (AR) equipment, wireless terminals in industrial control (industrial control), wireless terminals in self-driving (self-driving), wireless terminals in remote medical surgery, and smart grid (smart grid) Wireless terminals in transportation safety, wireless terminals in transportation safety, wireless terminals in smart cities, and wireless terminals in smart homes, such as street lights, monitors, etc.

2) Network equipment is the equipment that connects terminal equipment to the wireless network in the mobile communication system. As a node in a radio access network, the network device may also be referred to as a base station, or may also be referred to as a radio access network (RAN) node (or device).

At present, some examples of network equipment are: gNB, transmission reception point (TRP), evolved Node B (evolved Node B, eNB), radio network controller (RNC), Node B (Node B) B, NB), access point (access point, AP) base station controller (BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), or baseband unit (BBU), etc.

In addition, in a network architecture, the network device may include a centralized unit (CU) node and a distributed unit (DU) node. This structure splits the protocol layer of the eNB in the long-term evolution (LTE) system. Some of the protocol layer functions are placed under the centralized control of the CU, and some or all of the protocol layer functions are distributed in the DU. Centralized control of DU.

3) RNTI, used for network equipment scheduling terminal equipment data transmission, can also be used to identify terminal equipment. Optionally, the communication system may define different RNTIs according to specific communication procedures between the terminal equipment and the network equipment. The following are several specific examples of RNTIs.

a. Paging RNTI (paging RNTI, P-RNTI), used to schedule paging messages.

b. System information RNTI (system information RNTI, SI-RNTI), used for scheduling system information (such as SIB).

c. Random access RNTI (random access RNTI, RA-RNTI), used to schedule RAR messages.

d. A cell-specific RNTI (cell-specific RNTI, C-RNTI) is used to schedule terminal equipment for data transmission.

e. The RNTI (temporary C-RNTI, TC-RNTI) specific to the temporary cell is carried in the RAR and used to determine the C-RNTI.

At present, when the communication process between the terminal equipment and the network equipment changes, the terminal equipment and the network equipment can use the RNTI in the previous communication process in the latter communication process, and the network equipment can also allocate a new one to the terminal equipment. RNTI. For example: in the random access process, the terminal device will select a random access preamble and use the time-frequency resource corresponding to the random access preamble to send the random access preamble (ie msg1); the network device is receiving After the random access preamble of the terminal equipment is received, the RA-RNTI is calculated according to the time-frequency resource location corresponding to the random access preamble, and the PDCCH is scrambled with the RA-RNTI, and the PDCCH is sent to the terminal equipment for scheduling RAR message (ie msg2), where the RAR message contains TC-RNTI, which is a temporary scheduling ID allocated by the network device to the terminal device, which can be used for further communication between the terminal device and the network device; After the random access of the terminal equipment succeeds, the TC-RNTI can be used as the C-RNTI for subsequent service data transmission scheduling.

4) "and/or" describes the association relationship of the associated objects, indicating that there can be three types of relationships, for example, A and/or B, which can mean: A alone, A and B at the same time, and B alone Happening. The character "/" generally indicates that the associated objects are in an "or" relationship.

It should be noted that the multiple involved in this application refers to two or more.

In addition, it should be understood that in the description of this application, words such as “first” and “second” are only used for the purpose of distinguishing description, and cannot be understood as indicating or implying relative importance, nor can it be understood as indicating Or imply the order.

The embodiments of the present application will be described below in conjunction with the drawings.

FIG. 1 shows the architecture of a possible communication system to which the communication method provided by the embodiment of the present application is applicable. Referring to FIG. 1, the communication system includes: a network device 101 and a terminal device 102.

The network device 101 is responsible for providing wireless access-related services for the terminal device 102, realizing physical layer functions, resource scheduling and wireless resource management, quality of service (QoS) management, wireless access control, and mobility Sexual management functions.

The terminal device 102 is a device that accesses the network through the network device 101 to provide voice or data services for users.

As shown in FIG. 1, the network device 101 and the terminal device 102 are connected through an air interface (such as a Uu) interface, so as to realize the communication between the terminal device 102 and the network device 101.

It should also be pointed out that the communication system shown in FIG. 1 is taken as an example, and does not constitute a limitation on the communication system to which the method provided in the embodiment of the present application is applicable. The embodiments of the present application can also be applied to communication systems of various types and standards, such as: the fifth generation (The 5th Generation, 5G) communication system, the Long Term Evolution (LTE) communication system, and the vehicle to everything (vehicle to everything). everything, V2X), Long Term Evolution-Internet of Vehicles (LTE-vehicle, LTE-V), Vehicle to Vehicle (V2V), Internet of Vehicles, Machine Type Communications (MTC), Internet of Things (Internet of Things) things, IoT), narrowband Internet of Things (narrowband IoT, NB-IoT) long-term evolution-machine-to-machine (LTE-machine to machine, LTE-M), long-term evolution machine communication (LTE-MTC), machine-to-machine ( The machine to machine (M2M), enterprise LTE discrete spectrum aggregation (eLTE-DSA) system, etc., are not limited in the embodiment of this application.

Generally, in the mobile communication system shown in Figure 1, in order to save power consumption, the terminal device is in the RRC idle state when there is no data transmission, and when the terminal device needs to perform data transmission, it switches from the RRC idle state to the RRC idle state. In the connected state, after the RRC connection of the terminal device is established or restored, the terminal device may perform uplink and downlink data transmission with the network device. Among them, the terminal device needs to go through a contention-based random access process to transition from the RRC idle state to the RRC connected state. In the random access process, the terminal device establishes/restores the relationship with the network device through the RRC connection establishment/recovery process For the RRC connection between each other, refer to the flowchart shown in Figure 2 or Figure 3 for the specific process.

In this application, the RRC idle state can be replaced by the RRC inactive state (RRC Inactive). For example, the RRC idle state in the function and process descriptions in this application can be replaced by the RRC inactive state.

The following describes the establishment process of the RRC connection shown in FIG. 2.

First, the terminal device performs a random access process, that is, S201-S204. For a specific description, please refer to the description of S1-S4 of the random access process in the background art, which will not be repeated here.

It should be noted that msg3 can carry an RRC connection establishment request (RRC connection request) message, and msg4 can carry an RRC connection setup (RRC connection setup) message.

In addition, the network device carries the contention resolution identity of the terminal device in msg4. After the terminal device receives the msg4, if it detects that the conflict resolution identity in the msg4 is in the msg3 sent by the terminal device If the first 48 bits of information of the CCCH SDU is determined, it is determined that the random access is successful; otherwise, it is determined that the random access fails, and the terminal device may wait for a period of time before performing the random access process again.

S205: The terminal device sends an RRC connection setup complete (RRC connection setup complete) message to the network device, where the message may carry a non-access stratum (Non-Access Stream, NAS) service request (service request) message.

S206-S207: The network device requests the mobile management entity (MME) in the core network to initialize the context of the terminal device.

S208-S209: The network device performs security settings on the terminal device.

S210-S211: The network device configures a bearer of the terminal device, and the bearer is used to transmit signaling and data.

S212-S214: The network device, the MME, and a serving gateway (SGW) in the core network establish or modify the bearer on the core network side for the terminal device.

S215-S216: The terminal device sends uplink data (UL data) to the SGW. It should be noted that this process can be executed after step S211.

S217-S218: The SGW sends downlink data (DL data) to the terminal device.

When the terminal device transitions from the RRC connected state to the RRC idle state, the terminal device will release the configuration information of the terminal device, such as the context of the terminal device, etc., and the network device will also release the context of the terminal device. The context of the terminal device includes the identification of the terminal device, resource configuration information, encryption algorithm, capability information, etc. In this way, each time the RRC connection of the terminal device is established, the network device needs to reinitialize the context of the terminal device and reconfigure the terminal device. In order to reduce the message exchange overhead during the RRC connection establishment process, the terminal device may suspend the RRC connection when entering the RRC idle state, that is, the network device releases the RRC connection with the terminal device, but does not release the terminal The context of the device, the terminal device also saves the configuration information of the terminal device. The communication system may adopt the RRC connection restoration procedure shown in FIG. 3 to restore the RRC connection.

In Figure 3, data is transmitted via terminal equipment, network equipment, and service gateway. This method is also called a user plane solution (UP Solution). The following describes the restoration process of the RRC connection shown in Figure 3.

S301-S302 are the same as S1-S2 of the random access process, and will not be repeated here.

S303: The terminal device sends an RRC connection resume request (RRC connection resume request) message to the network device, requesting to resume the RRC connection.

Wherein, the RRC connection recovery request message carries a resume ID (resume ID), a resume cause (resume cause), and a short resume MAC-I. The resume ID is used to identify the suspended terminal device; the resume cause is used to indicate the reason why the terminal device resumes the RRC connection, including emergency call (emergency), high priority access (high rriority access), and called ( mt-access), caller signaling (mo-signalling), caller data (mo-data), delay tolerant access (delay tolerant access), caller voice (mo-voice call), etc. The short resume MAC-I is used to protect the integrity of msg3 to prevent msg3 from being tampered with.

S304: The network device sends an RRC connection resume (RRC connection resume) message to the terminal device to restore the context of the UE. Wherein, the RRC connection recovery message carries a next hop chaining count (NCC) used to derive a security key.

S305: After receiving the RRC connection recovery message, the terminal device restores its own context. Then, the terminal device enters the RRC connected state.

S306: The terminal device sends an RRC connection resume complete (RRC connection resume complete) message to the network device to notify the network device that the terminal device has resumed the RRC connection.

S307: The network equipment sends a UE context resume request (UE context resume request) message to the MME.

S308: MME and SGW exchange bearer modification messages.

S309: The MME sends a UE context resume response (UE context resume response) message to the network device.

After that, the terminal device may send the uplink data to the network device, and send it to the SGW through the network device. Of course, the SGW may also send downlink data to the terminal device through the network device. After the data transmission is completed, the terminal device enters the RRC idle state through the release procedure.

In another example, data can be transmitted through terminal equipment, network equipment, MME, and service gateway. This method is also called a control plane solution (CP Solution). The specific steps can be referred to as shown in Figure 2. The difference is that the The terminal device may carry the uplink data in an RRC connection setup complete message and send it to the network device, and the network device may send the downlink data to the terminal device through a downlink information conversion (DL information tranfer) message.

Since in some services, terminal devices only need to transmit a small amount of data, in order to further improve the data transmission efficiency of these terminal devices, the terminal devices can perform data transmission in the RRC idle state. The current communication system can be implemented in a variety of methods, such as EDT technology, PUR method, etc. Figures 4 to 7 are scenarios where the above methods are used. EDT technology includes mobile originated-EDT (MO-EDT) technology triggered by uplink data and mobile terminated-EDT (MT-EDT) technology triggered by downlink data. Among them, MO-EDT technology includes UP MO-EDT based on the UP scheme and CP MO-EDT based on the CP scheme. MT-EDT includes UP MT-EDT based on the UP scheme and CP MT-EDT based on the CP scheme.

Figure 4 shows the UP scheme of MO-EDT technology. The specific process includes:

Before the implementation of the solution, the network device may send a random access preamble indicating early transmission (that is, for MO-EDT) to the terminal device.

S401: When the terminal device determines that there is a small amount of uplink data to be sent, the terminal device sends to the network device a random access preamble indicating early transmission.

S402: After receiving the random access preamble indicating advance transmission, the network device sends an RAR message to the terminal device. Wherein, the RAR message includes uplink grant (UL Grant) information, TA, and RNTI allocated to the terminal device, and more transmission resources are configured in the uplink grant information.

S403: After the terminal device receives the RAR message and determines that the transmission resource configured in the uplink authorization information can transmit current uplink data, the terminal device sends msg3 to the network device. Optionally, the msg3 carries uplink data.

Optionally, the msg3 may carry an RRC connection resume request (RRC connection resume request) message. The RRC connection recovery request message is carried on a common control channel (CCCH), which is signaling radio bearer 0 (SRB0), and the RRC connection recovery request message is encapsulated to form a CCCH SDU, The uplink data is carried on a dedicated traffic channel (DTCH), which is a data radio bearer (DRB), and the uplink data is encapsulated to form a DTCH SDU. The above-mentioned CCCH SDU and DTCH SDU are multiplexed at the MAC layer to form a MAC PDU.

The RRC connection recovery request message may also carry a resume ID (resume ID), resume cause (resume cause), and short resume MAC-I.

S404-S406 are the same as S307-S309 and will not be repeated here.

S407: After receiving the context recovery response (UE context resume) message of the terminal device sent by the MME, the network device sends uplink data to the SGW.

S408: If the SGW has a small amount of downlink data to be sent to the terminal device, the downlink data is sent to the network device after S407. It should be noted that this step is optional.

S409: The network device initiates a suspension process after sending the uplink data to the SGW or after receiving the downlink data sent by the SGW, requesting to suspend the context of the terminal device.

S410: The network device sends an RRC connection release (RRC connection release) message to the terminal device. Wherein, if the network device receives downlink data, the network device also sends the downlink data while sending the RRC connection release message.

Wherein, the RRC connection release message is carried on a dedicated control channel (DCCH), which is Signaling Radio Bearer 1 (SRB1). The RRC connection release message is encapsulated to form a DCCH SDU, and the RRC connection release message can also be Carry release cause, resume ID, NCC, etc. The downlink data is carried on the DTCH, and the downlink data is encapsulated to form a DTCH SDU, and the DTCH SDU can be multiplexed with the aforementioned DCCH SDU to form a MAC PDU.

In the above procedure, the terminal device is always in the RRC idle state and has not entered the RRC connected state.

Figure 5 shows the CP scheme of MO-EDT technology. The specific process includes:

S501-S502 are the same as S401-S402 and will not be repeated here.

S503: After the terminal device receives the RAR message and determines that the transmission resource configured in the uplink authorization information can transmit the current uplink data, the terminal device sends an RRC early data transmission request to the network device (RRC early data request) message.

Wherein, the RRC early transmission data request message carries the S-TMSI used to identify the terminal device, the establishment cause used to indicate the reason for initiating the request, and the dedicated Info NAS (dedicated Info NAS).

The NAS dedicated information is used to carry the uplink data, that is, the uplink data can be encapsulated in the form of NAS messages at the NAS layer.

S504: The network device sends a terminal device initialization message (Initial UE message) to the MME. Wherein, the terminal device initialization message carries a NAS message containing the uplink data.

S505: The MME and the SGW exchange a bearer modification message.

S506: The MME sends the uplink data to the SGW.

S507: If the SGW has a small amount of downlink data to be sent to the terminal device, the downlink data is sent to the MME after S506. It should be noted that this step is optional.

S508: The MME sends a NAS message to the network device. When the MME receives the downlink data, it carries the downlink data in the NAS message and indicates the size of the downlink data.

S509: If the network device does not receive downlink data or receives less downlink data, the network device sends an RRC early data complete (RRC early data complete) message to the terminal device. Wherein, when the network device receives downlink data, the RRC early data transmission complete message carries NAS-specific information that carries the downlink data.

S510: The network device initiates a suspension process, requesting to suspend the context of the terminal device.

The above-mentioned EDT methods shown in Figs. 4 and 5 are both referred to as the MO-EDT method (that is, the method in which the msg3 of the terminal device carries the uplink data in the random access process).

Fig. 6 is a scheme in which the communication system adopts the PUR method (that is, the method of using the pre-configured uplink resource PUR to send uplink data). The specific process includes:

S601: In the RRC connected state or the RRC idle state of the terminal device, the network device sends to the terminal device the configuration information of the preconfigured uplink resource (Preconfigured Uplink Resource, PUR), the RNTI and the TA allocated to the terminal device.

Wherein, the RNTI is used for the terminal device to use PUR for data transmission, and the PUR is a resource used by the terminal device for data transmission in an RRC idle state, or the PUR is used for transmitting Msg3.

The terminal device saves the configuration information of the PUR, the RNTI and the TA.

S602: When the terminal device has uplink data arriving in the RRC idle state, the terminal device uses the PUR, TA and the RNTI to send a target message to the network device. Wherein, the target message carries the uplink data. The target message is similar to msg3 in the random access process.

S603: After receiving the target message, the network device sends the uplink data to the SGW or MME, and sends an RRC connection release (RRC connection release) message or RRC early data completion (RRC early data) to the terminal device. complete) message. The target message can carry downlink data.

Optionally, the network device may also send PUR, RNTI, and TA configuration information to the terminal device through the RRC connection release message or the RRC early data transmission complete message.

FIG. 7 is a method for a network device to send a small amount of downlink data from a certain terminal device to the terminal device in the RRC idle state of the terminal device when the small amount of downlink data arrives. The method shown in Figure 7 is also called the MT-EDT method (that is, the method of transmitting downlink data after the random access preamble is transmitted). The specific process of the method includes:

S701: When receiving a first paging message sent by a core network device, a network device sends a second paging message to the terminal device, where the second paging message may carry random access for early downlink data transmission Preamble and RNTI for early transmission of downlink data.

In the embodiment of this application, the RNTI used for early transmission of downlink data is the RNTI corresponding to the random access preamble used for early transmission of downlink data. In this application, the RNTI corresponding to the random access preamble can be understood to mean that the random access preamble and the RNTI are allocated to the same terminal device, and the network device can determine the terminal device through the random access preamble , And then determine the RNTI, that is, the RNTI can be determined by the random access preamble, which is a correspondence.

The second paging message may carry a random access resource for early transmission of downlink data, and the random access resource includes the random access preamble.

The second paging message may not carry the random access preamble, but may carry random access time-frequency resources.

S702: The terminal device sends a random access preamble for early transmission of downlink data to the network device.

In a possible implementation manner, the terminal device may send a random access preamble for early transmission of downlink data to the network device after receiving the second paging message.

In a possible implementation manner, the terminal device sends the random access preamble carried in the second paging message to the network device.

In a possible implementation manner, the terminal device uses the random access time-frequency resource carried in the second paging message to send a random access preamble to the network device.

S703: The network device uses the RNTI to send downlink data to the terminal device.

In a possible implementation manner, after receiving the random access preamble sent by the terminal device, the network device uses the RNTI to send downlink data to the terminal device.

In a possible implementation manner, the network device sends the PDCCH scrambled by the RNTI to the terminal device, where the PDCCH is used to schedule a second message, and the second message carries downlink data. The message can be a MAC PDU.

Correspondingly, the terminal device uses the RNTI to receive the second message, thereby receiving the downlink data.

In a possible implementation manner, the network device determines the RNTI corresponding to the random access preamble, and uses the RNTI as the RNTI used for communication between the network device and the terminal device; the network device uses The RNTI sends a RAR message to the terminal device, and carries the downlink data in the RAR message. Correspondingly, the terminal device uses the RNTI to receive the RAR message, thereby receiving the downlink data.

S704: The terminal device performs uplink transmission to the network device.

In a possible implementation manner, the uplink transmission includes an RRC message, and the RRC message is used to end early downlink data transmission.

In a possible implementation manner, the uplink transmission includes an RRC message, and the RRC message includes uplink data. For example, the uplink data is encapsulated in a NAS PDU, and the NAS PDU is carried in the RRC message. The RRC message is encapsulated as CCCH SDU, and then encapsulated as MAC PDU, and the uplink transmission is the transmission of the MAC PDU.

In a possible implementation manner, the uplink transmission includes RRC messages and uplink data. For example, the RRC message is encapsulated in a DCCH SDU, the uplink data is encapsulated in a DTCH SDU, the DCCH SDU and the DTCH SDU are multiplexed into a MAC PDU, and the uplink transmission is to transmit the MAC PDU.

From the description of Figures 4 to 7 above, it can be seen that when a network device and a terminal device perform data transmission, an RNTI needs to be allocated to the terminal device in advance, so that the network device schedules the terminal device data transmission through the PDCCH. For the RRC connected state, the network device allocates an RNTI to the terminal device through the RAR message; for the RRC idle state, the network device needs to allocate an RNTI to the terminal device in advance through other messages or signaling. Since the RNTI is pre-allocated and the number of available RNTIs is limited, the network device may allocate the same RNTI to multiple terminal devices. Since the amount of data transmitted by a terminal device in the idle state is small, even if multiple terminal devices are assigned the same RNTI, the probability of multiple terminal devices using the same RNTI for data transmission at the same time (ie, RNTI conflict) is relatively high. low.

However, in some cases, when the terminal device uses the above method (denoted as the PUR method) for data transmission in the idle state, the network device may have a large amount of data to be sent to the terminal device, and the terminal device needs to enter the RRC connection. Data transmission mode. For example, in the communication system shown in Figure 1, when the network equipment pre-allocates the same RNTI to the terminal equipment a and the terminal equipment b, if the terminal equipment a needs to enter the RRC connection state, and the terminal equipment a continues to use For the RNTI, when the terminal device a uses the RNTI in the RRC connection state, if the terminal device b uses the PUR method for data transmission, the problem of RNTI conflict will occur, which further affects the resource scheduling and resource scheduling of the two terminal devices. data transmission. For example, when scheduling terminal equipment a, terminal equipment b cannot be scheduled, and when scheduling terminal equipment b, terminal equipment a cannot be scheduled.

In order to solve the aforementioned RNTI conflict problem, the embodiment of the present application provides an RNTI update method, which can be applied to the communication system as shown in FIG. 1. Referring to Figure 8, the method specifically includes the following steps:

S801: The network device sends the first message to the terminal device. The first message is used to notify the terminal device of the first RNTI allocated by the network device to the terminal device, and the first RNTI is used for the terminal device to perform data transmission in the radio resource control RRC idle state .

Exemplarily, the first RNTI is used for the terminal equipment to perform data transmission in the RRC idle state, which may be understood as the first RNTI used for the terminal equipment to use the PUR method, the MT-EDT method, or the MO-EDT method. data transmission.

It should be noted that the network device may send the first message in the RRC idle state or the RRC connected state of the terminal device, which is not limited in the embodiment of the present application.

In an implementation manner, the first message may, but is not limited to, notify the first RNTI in the following manner:

Manner 1: The first message includes the first RNTI.

Manner 2: The first message includes first indication information, and the first indication information is used to indicate the first RNTI. Exemplarily, the first indication information may, but is not limited to, indicate the first RNTI through the following method:

a. The first indication information indicates that the first RNTI is the RNTI used when the network device sends the first message, that is, the current RNTI used by the terminal device is used as the first RNTI.

b. The first indication information indicates that the first RNTI is a third RNTI, and the third RNTI is allocated by the network device to the terminal device before sending the first message to the terminal device, The third RNTI is used for the terminal equipment to perform data transmission in the RRC idle state. In other words, the first indication information indicates that the first RNTI is the RNTI pre-configured to the terminal device before being used. Exemplarily, the network device first configures the PUR and the third RNTI for the terminal device, and then the terminal device enters the RRC connected state, the terminal device may save the configuration information of the PUR and the third RNTI, and then, in the terminal device When the network device releases the terminal device to the RRC idle state, configure the PUR and the first RNTI for the terminal device again. At this time, the network device may instruct the terminal device to continue (continue to use) the previously configured PUR And/or RNTI, that is, the third RNTI is used as the first RNTI. This can reduce the signaling overhead caused by the network equipment reconfiguring the terminal equipment.

c. The first indication information indicates that the first RNTI is the RNTI used in the current RRC connected state.

d. The first indication information indicates that the first RNTI is the RNTI currently used by the terminal equipment and the network equipment.

Manner 3: The first message does not include the first RNTI, and the first RNTI is the RNTI used when the network device sends the first message, that is, the current RNTI used by the terminal device is used As the first RNTI, or, the first RNTI is the third RNTI (the description of the third RNTI is as above), or the first RNTI is the RNTI used in the current RRC connection state, or the first indication information Indicates that the first RNTI is the currently used RNTI.

In an implementation manner, in a scenario where the communication system uses the PUR method, the first message also includes PUR configuration information, and the PUR is the resource used by the terminal device for data transmission in the RRC idle state . Optionally, the first message may also include information such as TA.

In an implementation manner, when the terminal device is in the RRC idle state, the terminal device and the network device use the first RNTI for data transmission. When the first message also includes PUR configuration information, the terminal device uses the PUR and the first RNTI to send data to the network device.

S802: The network device sends a second message to the terminal device. The second message is used to notify the terminal device of the second RNTI allocated by the network device to the terminal device, and the second RNTI is used for the terminal device to switch from the RRC idle state to the RRC connected state Data transfer afterwards.

In a possible implementation manner, the second RNTI is used for data transmission after the terminal device rolls back from the process of using the PUR method to transmit data to the RRC connected state.

In a possible implementation manner, the second RNTI is used for data transmission after the terminal device rolls back from the process of using the MT-EDT method to transmit data to the RRC connected state.

In a possible implementation manner, the network device sends the second message to the terminal device in the RRC idle state of the terminal device.

In some possible implementation manners, the second message may, but is not limited to, notify the second RNTI in the following manner:

Manner 1: The second message includes the second RNTI;

Manner 2: The second message includes second indication information, and the second indication is used to indicate the second RNTI. Exemplarily, the second indication information may, but is not limited to, indicate the second RNTI through the following method:

a. The second indication information indicates that the second RNTI is the first RNTI.

b. The second indication information indicates that the second RNTI is the fourth RNTI used when the network device sends the second message.

Manner 3: The second message does not include the second RNTI, then the second RNTI is the first RNTI, or the second RNTI is used when the network device sends the second message Fourth RNTI.

In an implementation manner, the network device may send the second message to the terminal device through the following steps:

The network device uses the first RNTI to send the second message to the terminal device; or,

In the scenario where the communication system uses the PUR method, the network device determines the fourth RNTI corresponding to the target resource according to the target resource and the mapping relationship between the resource and the RNTI, where the mapping between the resource and the RNTI The relationship is agreed upon by the network device and the terminal device; the network device uses the fourth RNTI to send the second message to the terminal device.

In an implementation manner, the terminal device and the network device may start to use the second RNTI for data transmission when the terminal device enters the RRC connected state.

In another implementation manner, after the terminal device receives the transport block (TB) corresponding to the second message, it sends feedback information to the network device according to the reception of the TB (take ACK and NACK as Example to explain). For example, if the terminal device successfully verifies the TB, it sends an ACK to the network device, otherwise, it sends a NACK. In some cases, the network device may erroneously decode the ACK sent by the terminal device into a NACK, and then the network device will retransmit the TB. In order to prevent the network device from erroneously decoding the ACK sent by the terminal device into NACK and retransmitting the TB corresponding to the second message, the terminal device may start after receiving the uplink authorization information sent by the network device Use the second RNTI for data command transmission. In this implementation manner, the terminal equipment and the network equipment still use the uplink authorization information sent by the first RNTI. The process is that the network device uses the first RNTI to first send a second message to the terminal device. If the terminal device successfully receives the second message, the terminal device sends an ACK to the network device, and then the network device uses the first RNTI to send it to the terminal device. After the uplink authorization information, the terminal equipment and the network equipment start to use the second RNTI for data transmission. In this way, if the network device decodes the ACK sent by the terminal device into a NACK, the network device will not send the uplink authorization information to the terminal device, and the network device and the terminal device continue to use the first RNTI until the network device successfully sends the uplink authorization to the terminal device Information, network equipment and terminal equipment only start to use the second RNTI.

In another implementation manner, after the terminal device receives the TB corresponding to the second message, it sends feedback information to the network device according to the reception of the TB (taking ACK and NACK as examples for illustration) . In some cases, the network device may erroneously decode the NACK sent by the terminal device into an ACK. At this time, the network device determines that the terminal device has successfully received the TB corresponding to the second message, resulting in the terminal device not successfully receiving the second message, and then Unable to determine the second RNTI. In order to prevent the network device from erroneously decoding the NACK sent by the terminal device into an ACK, causing the terminal device to fail to successfully receive the second message and thus fail to determine the second RNTI, the network device may The uplink authorization information is carried in the second message. In this way, it can be ensured that the RNTI used by the terminal device and the network device can be synchronized, and the problem of scheduling failure caused by non-synchronization of the RNTI can be avoided. In this process, the network device sends a second message to the terminal device. The second message includes downlink data (optional), uplink authorization information, and second indication information/second RNTI, where the second indication information is used to indicate The second RNTI. In this implementation manner, the terminal device and the network device may also start to use the second RNTI for data transmission when the terminal device enters the RRC connected state.

It should be noted that, in an implementation manner, in a scenario where the communication system uses the method shown in FIG. 7, the first message may be a paging message, wherein the first message contains indication data The random access preamble transmitted early, and the RNTI corresponding to the random access preamble (that is, the first RNTI). At this time, the network device can determine through the random access preamble that the terminal device can use the MT-EDT method for data transmission. In this way, the network device and the terminal device can use the first RNTI to transmit the second message (msg2). In an example, when the network device determines that the amount of downlink data of the terminal device is large, the network device may send a second message in S703, where the second message carries an instruction to establish or restore the RRC connection. For example, the second message may be a RAR message; when the second message carries an indication of establishing or resuming an RRC connection, the second message may be an RRC Connection Setup message or an RRC Connection Resume message. The second message is also used to notify the terminal device of the second RNTI used after the RRC connection is restored or established. For example, the second message carries the second RNTI. In this way, the terminal device can use the second RNTI for data transmission after restoring or establishing an RRC connection and entering the RRC connected state.

In an example of the foregoing implementation manner, after the network device sends the second message to the terminal device, the network device may also use the first RNTI to send the DCI carrying uplink authorization information to the terminal device , The uplink authorization information is used by the terminal device to send a third message. The third message may be used to switch the terminal device from the RRC idle state to the RRC connected state. In this way, after the terminal device switches from the RRC idle state to the RRC connected state, the terminal device and the network device can use the second RNTI for data transmission.

In another example of the foregoing implementation manner, after the terminal device receives the TB corresponding to the second message, it sends feedback information to the network device according to the reception of the TB (taking ACK and NACK as examples) Description). In some cases, the network device may erroneously decode the NACK sent by the terminal device into an ACK. At this time, the network device determines that the terminal device has successfully received the TB corresponding to the second message, resulting in the terminal device not successfully receiving the second message, and then Unable to determine the second RNTI. In order to prevent the network device from erroneously decoding the NACK sent by the terminal device into an ACK, causing the terminal device to fail to successfully receive the second message and thus fail to determine the second RNTI, the network device may The uplink authorization information is carried in the second message. In this way, when the network device receives the third message sent by the terminal device on the time-frequency resource indicated by the uplink authorization information, the network device can determine that the terminal device successfully receives the second message, Since the second message carries the second RNTI/second indication information, the network device can determine that the terminal device successfully determines the second RNTI. Then, the network device sends ACK feedback information to the terminal device, so that the terminal device can determine that the network device successfully receives the third message, and the terminal device and the network device can start to use the second RNTI. In this way, it can be ensured that the RNTI used by the terminal device and the network device can be synchronized, and the problem of scheduling failure caused by non-synchronization of the RNTI can be avoided. In this process, the network device sends a second message to the terminal device. The second message includes downlink data (optional), uplink authorization information, and second indication information/second RNTI, where the second indication information is used to indicate The second RNTI. In this implementation manner, the terminal device and the network device may also start to use the second RNTI for data transmission when the terminal device enters the RRC connected state.

The embodiment of the present application provides an RNTI update method. In this method, after notifying the terminal device of the first RNTI used for data transmission in the RRC idle state, the network device may also notify the terminal device to switch to the RRC connected state. The second RNTI used for data transmission. With this method, the network device can update the RNTI of the terminal device, which can prevent the terminal device from using the same RNTI in the RRC idle state and the RRC connected state, thereby avoiding multiple terminal devices capable of data transmission in the RRC idle state The occurrence of RNTI conflicts can ultimately ensure normal resource scheduling and data transmission for terminal equipment.

Based on the embodiment shown in FIG. 8, the embodiment of the present application provides an RNTI update example. As shown in FIG. 9, the process of this example includes the following steps:

S901: The network device sends a first message to the terminal device. The first message may be an idle state transmission configuration message, wherein the idle state transmission configuration message carries configuration information of the target resource, and the idle state transmission configuration message is also used to notify the terminal device of the network device allocation The first RNTI for the terminal device.

In a possible implementation manner, the idle state transmission configuration message may be one of the following:

(1) RRC connection release message (RRC Connection Release);

(2) RRC early data completion message (RRC Early Data Complete);

(3) RRC Connection Reconfiguration message (RRC Connection Reconfiguration);

(4) RRC Connection Setup message (RRC Connection Setup);

(5) RRC Connection Reestablishment message (RRC Connection Reestablishment).

In a possible implementation manner, the target resource may be a pre-configured uplink resource used for uplink data transmission

(Preconfigured Uplink Resource, PUR). The configuration information of the target resource is PUR configuration information.

In a possible implementation manner, the first RNTI is used for the terminal device to perform data transmission in a radio resource control RRC idle state.

In a possible implementation manner, the first RNTI is used by the terminal device to send uplink data using PUR.

In a possible implementation manner, the first RNTI is used by the terminal device to monitor the downlink control information DCI after the PUR sends uplink data.

In a possible implementation manner, in addition to the aforementioned "network device in the RRC connected state of the terminal device", the network device may also send an idle state transmission configuration message to the terminal device in the downlink transmission before S902, for example, The network device can send the RRC connection release message or the RRC early data complete message in the last message of the MO-EDT method, or send the last downlink RRC message in the PUR method to all The terminal device sends the idle state transmission configuration message. That is, S901 may also send the idle state transmission configuration message to the terminal device when the network device is in the RRC idle state of the terminal device.

In a possible implementation manner, the aforementioned "RRC connection state of the network device in the terminal device" may be the RRC connection state of the network device in the terminal device, and the RRC connection release message is sent to the terminal device. The configuration message is transmitted in the idle state.

The target resource is a resource used when the terminal device performs data transmission in an RRC idle state. Optionally, the first message may also include information such as TA.

After receiving the idle state transmission configuration message, the terminal device saves the configuration information of the target resource and the first RNTI.

S902: When uplink data arrives in the RRC idle state, the terminal device uses the first RNTI and the target resource to send the uplink data to the network device.

Optionally, the uplink data may be encapsulated in a non-access layer protocol data unit (NAS PDU), or encapsulated in a MAC SDU, such as a DTCH SDU.

In a possible implementation manner, S902 may be performed after the network device sends the first message to the terminal device, that is, after the network device sends the first message to the terminal device, The network device receives a third message sent by the terminal device using the first RNTI in the RRC idle state, where the third message carries uplink data. Correspondingly, after the terminal device receives the first message from the network device, the terminal device uses the first RNTI and the target resource to send the third message to the network device, and The third message carries uplink data.

Optionally, the third message may also include an RRC Early Data Request (RRC Early Data Request) message, or an RRC PUR request (request) message, or a PUR transmission (transmission) message, or an RRC connection recovery request (RRC connection Resume Request).

In a possible implementation manner, the third message may only include an RRC message, such as an RRC Connection Request (RRC Connection Request) message, or an RRC Connection Resume Request (RRC Connection Resume Request) message.

S903: The network device sends a second message to the terminal device. The second message may be an RNTI update message, and the RNTI update message is used to notify the terminal device of the second RNTI allocated by the network device to the terminal device, and the second RNTI is used for the terminal device Data transmission is performed after switching from the RRC idle state to the RRC connected state.

Exemplarily, the RNTI update message may be an RRC connection setup (RRC connection setup) message, or an RRC connection resume (RRC connection resume) message, or an RRC connection reconfiguration (RRC connection reconfiguration) message, or may carry a C-RNTI MAC Downlink message of CE.

In a possible implementation manner, the second message includes the second RNTI; or, the second message includes second indication information, and the second indication is used to indicate the second RNTI, specifically See S802 for instructions.

In a possible implementation manner, that the second RNTI is used for the terminal device to perform data transmission after switching from the RRC idle state to the RRC connected state may be that after the terminal device receives the RNTI update message, The second RNTI is used to monitor the downlink physical control channel PDCCH.

Optionally, the network device sends the RNTI update message to the UE according to the first RNTI. When the first RNTI is the fourth RNTI, the network device may send the RNTI update message to the terminal device according to the fourth RNTI, and the fourth RNTI may be when the network device sends the second message The used RNTI or the fourth RNTI is the RNTI generated by the network device according to the target resource. It should be noted that in the communication system, a method for generating the fourth RNTI according to the target resource is agreed between the network device and the terminal device. Correspondingly, the terminal device uses the first RNTI or the fourth RNTI to monitor the PDCCH, and then receives the RNTI update message.

S903a: After successfully receiving the RNTI update message, the terminal device sends HARQ-ACK to the network device. This step is optional.

Optionally, the terminal device uses the first RNTI to send the HARQ-ACK to the network device.

After S903 or S903a, the terminal device switches from the RRC idle state to the RRC connected state. In S903 or

After S903a or S903b, the second RNTI is used for data transmission between the network device and the terminal device, and accordingly, the terminal device starts to monitor the PDCCH using the second RNTI.

S903b: The network device uses the second RNTI to send a PDCCH to the terminal device.

Optionally, the PDCCH carries uplink grant (UL grant) information.

Correspondingly, the terminal device uses the second RNTI to receive the PDCCH.

In a possible implementation manner, the network device uses the first RNTI to send the PDCCH to the terminal device; accordingly, the terminal device uses the first RNTI to receive the PDCCH. After that, the network device and the terminal device use the second RNTI for data transmission.

S904: The terminal device sends a fourth message to the network device according to the second RNTI.

Optionally, the fourth message may be an RRC connection setup complete (RRC connection setup complete) message, or an RRC connection resume complete (RRC connection resume complete) message, or an RRC connection confirmation (RRC connection confirm) message.

In a possible implementation manner, the terminal device uses the uplink resource indicated by the uplink grant information and the second RNTI to send a fourth message to the network device.

In a possible implementation manner, the terminal device sending the fourth message to the network device according to the second RNTI may be the terminal device sending the PUSCH scrambled by the second RNTI to the network device, The PUSCH carries the fourth message.

It should be noted that when the second RNTI is carried in the MAC CE, the MAC CE corresponds to an LCID of a DL-SCH. For example, the LCID may be one of 10001, 01011-01111.

Based on the embodiment shown in FIG. 8, the embodiment of the present application provides an RNTI update example. As shown in FIG. 10, the process of this example includes the following steps:

S1001: The network device sends a first idle state transmission configuration message to the terminal device. Wherein, the first idle state transmission configuration message includes the configuration information of the target resource, and informs the terminal device of the first RNTI allocated by the network device to the terminal device.

Refer to S901 for this step, and use the first idle state transmission configuration message to replace the idle state transmission configuration message in S901.

S1001 may occur in the RRC connected state, for example, the first idle state transmission configuration message may be an RRC connection release (RRC connection release) message; S1001 may also occur in the RRC idle state, for example, the first idle state transmission configuration message may be an RRC connection release message (RRC connection release) message or RRC data early transmission complete (RRC early data complete) message.

After S1001, the terminal device enters the RRC idle state.

When the terminal device enters the RRC connected state again, the network device can configure PUR resources and RNTI again. The steps are as follows:

S1001a: The network device sends a second idle state transmission configuration message to the terminal device. The second idle state transmission configuration message may indicate that the terminal device can continue to use the previous configuration (for example, the first idle state transmission configuration in S1001). The target resource configured by the message and/or the first RNTI, or the second idle state transmission configuration message may instruct the terminal device to use the currently saved target resource and/or the first RNTI.

In a possible implementation manner, when the terminal device enters the RRC connected state, the terminal device deactivates the PUR configuration (that is, the configuration of the target resource and the first RNTI), and when the terminal device switches to RRC In the idle state, the terminal device activates the PUR configuration.

The subsequent S1002-S1004 are the same as S902-S904.

Because after the terminal device receives the second idle state transmission configuration message, it will send feedback information to the network device according to the reception of the second idle state transmission configuration message (taking ACK and NACK as examples for illustration ). In some cases, the terminal device successfully receives the second idle state transmission configuration message and sends an ACK to the network device, but the network device may incorrectly decode the ACK as a NACK and retransmit the second idle state. State transmission configuration message. In this way, if the terminal device starts to use the second RNTI after sending the ACK, and the network device incorrectly decodes the ACK into a NACK, and therefore cannot use the second RNTI, this will further cause the terminal device and The RNTI used by the network device is not synchronized, which causes the network device to continue to fail to retransmit the second idle transmission configuration message, causing a problem that subsequent steps cannot be implemented.

In order to avoid the problem of inconsistency between the RNTI used by the network device and the terminal device due to the network device erroneously decoding the ACK into NACK, in the embodiment of the present application, the terminal device receives the PDCCH uplink or downlink scheduling After that, start to use the updated second RNTI.

Based on the embodiment shown in FIG. 8, the embodiment of the present application provides an RNTI update example. As shown in FIG. 11, the process of this example includes the following steps:

S1101-S1104 are the same as S901-S904, except that the RNTI notification message sent by the network device in S1103 can also carry uplink authorization information.

After the terminal device receives the idle-state transmission configuration message, it will send feedback information to the network device according to the reception of the idle-state transmission configuration message (taking ACK and NACK as examples for illustration). In some cases, the terminal device does not successfully receive the idle state transmission configuration message and sends a NACK to the network device, but the network device may erroneously decode the NACK into an ACK instead of retransmitting the idle state. Transmit configuration messages. As a result, the terminal device cannot successfully receive the idle state transmission configuration message, and thus cannot determine the second RNTI.

In order to prevent the network device from erroneously decoding the NACK sent by the terminal device into an ACK, the terminal device cannot successfully receive the idle state transmission configuration message and thus cannot determine the second RNTI problem, in this embodiment of the application In S1103, the network device simultaneously sends the updated RNTI and uplink authorization information to the terminal device.

Based on the embodiment shown in FIG. 8, the embodiment of this application provides an RNTI update example. As shown in FIG. 12, the process of this example includes the following steps:

S1201: The network device sends a first message to the terminal device, the first message may be a paging message, and the paging message is used to notify the terminal device of the first RNTI allocated by the network device to the terminal device, The first RNTI is used for the terminal equipment to perform data transmission in a radio resource control RRC idle state.

The paging message also carries configuration information of random access resources, the configuration information is used to indicate random access resources, and the random access resources include random access preambles and/or random access time-frequency resources. The random access resource is used for early transmission of downlink data.

In a possible implementation manner, the first RNTI is used for the terminal equipment to perform data transmission in the RRC idle state. The first RNTI may be used for the terminal equipment to receive downlink data after sending a random access preamble. data.

In a possible implementation manner, the paging message is used to notify the terminal device that the first RNTI allocated by the network device to the terminal device includes, and the paging message includes the first RNTI or includes RNTI index, where the RNTI index is used to indicate the first RNTI.

S1202: The terminal device uses the random access resource to send a random access preamble to the network device.

Specifically, the terminal device determines the configuration information of the random access resource according to the received paging message, and determines the random access resource according to the configuration information, and the random access resource includes a random access preamble and/or random access. Access time-frequency resources.

S1203: The network device sends a second message to the terminal device. The second message may be an RNTI update message, and the RNTI update message is used to notify the terminal device of the network device allocated to the terminal device. The second RNTI, the second RNTI is used for the terminal device to perform data transmission after switching from the RRC idle state to the RRC connected state.

In a possible implementation manner, the network device sends the RNTI update message to the terminal device in the RRC idle state of the terminal device.

In a possible implementation manner, the RNTI update message carries downlink data.

In a possible implementation manner, the RNTI update message may also include an RRC Connection Setup (RRC Connection Setup) message or an RRC Connection Resume (RRC Connection Resume) message.

In a possible implementation manner, the RNTI update message is used to notify the terminal device that the second RNTI allocated by the network device to the terminal device includes that the RNTI update message includes the second RNTI, or The RNTI update message includes a second indication, the second indication is used to indicate that the second RNTI is the first RNTI, or the RNTI update message includes C-RNTI MAC CE, and the C-RNTI MAC CE Carry the second RNTI.

S1203a to S1204: Same as S903a to S904.

In the MT-EDT process, the paging message carries the first RNTI. When the network device determines in S1203 that it needs to switch to the connected state of the terminal device, it may need to update the first RNTI, that is, all the terminals used by the terminal device. The update of the first RNTI to the second RNTI avoids the problem of RNTI conflicts due to the possibility of the first RNTI being used by multiple terminal devices, thereby avoiding the problem of scheduling conflicts.

It should be noted that, in the embodiment shown in FIG. 8 to FIG. 11, the configuration information of the target resource includes time-frequency resource location information of the target resource. For example, narrowband information (narrowband) information, carrier (carrier) information, or the number of physical resource blocks (PRB).

In an implementation manner, the configuration information of the target resource may further include: the use period of the target resource and the start time information of the first use period, or the use time information of the target period.

The unit of the use period of the target resource may be subframe, system frame, superframe, millisecond, second, minute, hour, day, etc., which is not limited in this application. Optionally, the start time information of the first use period may include: a reference time point and an offset value (offset). Optionally, the reference time point may be the moment when the terminal device receives the configuration information of the target resource (for example, the moment when the idle state transmission configuration information is received), or the moment when the RRC connection of the terminal device is released Etc., this application does not limit this.

The time information of the target resource may be specific time information, such as 12:00-1:00 every day. Optionally, the foregoing time information may be accurate to milliseconds.

In an implementation manner, the configuration information of the target resource may further include: validity information of the target resource. For example, valid time timer or valid times counter.

In the following, the effective time timer or the effective count counter is described by taking the network device configured with the use period for the target resource as an example.

Referring to FIG. 13, if the terminal device starts to use the target resource at the time indicated by the arrow, the terminal device starts the effective time timer counting, and the terminal device may not overflow the effective time timer In the case of using the target resource, when the valid time timer expires, the terminal device cannot use the target resource (the target resource is released, disabled, configured or deactivated).

Referring to FIG. 14, it is assumed that the valid times counter takes a value of 3. If the terminal device starts to use the target resource at the time indicated by the arrow, the terminal device activates the valid count counter to start counting, and the terminal device can use it when the valid count counter does not overflow For the target resource, when the valid times counter overflows, the terminal device cannot use the target resource (the target resource is released, disabled, configured, or deactivated).

Based on the same technical concept, an embodiment of the present application also provides a communication device. The structure of the device is shown in FIG. 15 and includes a communication unit 1501 and a processing unit 1502. The apparatus 1500 can be applied to network equipment or terminal equipment, and can implement the RNTI update method in the above embodiment. Wherein, the terminal device and the network device may be applicable to the communication system as shown in FIG. 1.

Optionally, when the apparatus 1500 is applied to a network device, the functions of each unit are as follows:

The communication unit 1501 is used to receive and send data;

The processing unit 1502 is configured to send a first message to the terminal device through the communication unit 1501, where the first message is used to notify the terminal device of the first RNTI allocated by the network device to the terminal device, and The first RNTI is used for the terminal device to perform data transmission in the radio resource control RRC idle state; and in the RRC idle state of the terminal device to send a second message to the terminal device through the communication unit 1501, wherein, The second message is used to notify the terminal device of the second RNTI allocated by the network device to the terminal device, and the second RNTI is used by the terminal device to perform data after switching from the RRC idle state to the RRC connected state transmission.

In a possible implementation manner, the first message includes the first RNTI; or, the first message includes first indication information, and the first indication information is used to indicate the first RNTI.

In a possible implementation manner, the first indication information indicates that the first RNTI is the RNTI used when the network device sends the first message; or, the first indication information indicates that the first RNTI The RNTI is the third RNTI, and the third RNTI is allocated to the terminal device by the network device before the first message is sent to the terminal device, and the third RNTI is used by the terminal device in the RRC Data transmission in the idle state; or, the first indication information indicates that the first RNTI is the RNTI used in the current RRC connected state, or the first indication information indicates that the first RNTI is the terminal device and The RNTI currently used by the network device.

In a possible implementation manner, the first message further includes configuration information of a target resource, and the target resource is a resource used by the terminal device when performing data transmission in an RRC idle state.

In a possible implementation manner, the processing unit 1502 is further configured to: after sending the first message to the terminal device, receive through the communication unit 1501 that the terminal device uses the terminal device in the RRC idle state. A third message sent by the first RNTI, where the third message carries uplink data.

In a possible implementation manner, the second message includes the second RNTI; or, the second message includes second indication information, and the second indication is used to indicate the second RNTI.

In a possible implementation manner, the second indication information indicates that the second RNTI is the first RNTI; or, the second indication information indicates that the second RNTI is the network device sending the The fourth RNTI used in the second message.

In a possible implementation manner, when the processing unit 1502 sends the second message to the terminal device through the communication unit 1501, it is specifically configured to:

Use the first RNTI to send the second message to the terminal device through the communication unit 1501.

Determine the fourth RNTI corresponding to the target resource according to the target resource and the mapping relationship between the resource and the RNTI, where the mapping relationship between the resource and the RNTI is agreed upon by the network device and the terminal device;

Use the fourth RNTI to send the second message to the terminal device through the communication unit 1501.

In a possible implementation manner, the processing unit 1502 is further configured to:

After sending the second message to the terminal device, a fourth message is sent to the terminal device through the communication unit 1501, where the fourth message contains uplink authorization information, and the uplink authorization information is used for the The terminal device switches from the RRC idle state to the RRC connected state for uplink data transmission.

In a possible implementation manner, when the processing unit 1502 sends the fourth message to the terminal device through the communication unit 1501, it is specifically configured to:

Use the second RNTI to send the fourth message to the terminal device through the communication unit 1501; or,

Use the first RNTI to send the fourth message to the terminal device through the communication unit 1501.

In a possible implementation manner, the second message includes uplink grant information, and the uplink grant information is used by the terminal device to perform uplink data transmission after switching from the RRC idle state to the RRC connected state.

After sending the second message to the terminal device, the communication unit 1501 receives the fourth message sent by the terminal device using the second RNTI after switching from the RRC idle state to the RRC connected state.

In a possible implementation manner, the first message is a paging message, and the first message includes a random access preamble and the first RNTI.

After sending the first message to the terminal device, the communication unit 1501 receives the random access preamble sent by the terminal device in the RRC idle state of the terminal device.

When the processing unit 1502 sends the second message to the terminal device through the communication unit 1501, it is specifically configured to:

After sending the second message to the terminal device, use the first RNTI to receive a fourth message from the terminal device through the communication unit 1501.

Optionally, when the apparatus 1500 is applied to a terminal device, the functions of each unit are as follows:

The communication unit 1501 is used to receive and send data;

The processing unit 1502 is configured to receive a first message from a network device through the communication unit 1501, where the first message is used to notify the terminal device of the first RNTI allocated by the network device to the terminal device, so The first RNTI is used for the terminal device to perform data transmission in the radio resource control RRC idle state; and in the RRC idle state to receive a second message from the network device through the communication unit 1501, wherein the second message is used Informing the terminal device of the second RNTI allocated by the network device to the terminal device, the second RNTI is used for the terminal device to perform data transmission after switching from the RRC idle state to the RRC connected state.

In a possible implementation manner, the first indication information indicates that the first RNTI is the RNTI used when the network device sends the first message; or, the first indication information indicates that the first RNTI The RNTI is the third RNTI, and the third RNTI is allocated to the terminal device by the network device before the first message is sent to the terminal device, and the third RNTI is used by the terminal device in the RRC Data transmission in the idle state; or the first indication information indicates that the first RNTI is the RNTI used in the current RRC connected state, or the first indication information indicates that the first RNTI is the terminal device and the The RNTI currently used by the network equipment.

After receiving the first message from the network device, in an RRC idle state, use the first RNTI to send a third message to the network device through the communication unit 1501, the third message carrying uplink data.

In a possible implementation manner, when the processing unit 1502 receives the second message from the network device through the communication unit 1501, it is specifically configured to: use the first RNTI to pass the communication unit 1501 Receiving the second message from the network device.

In a possible implementation manner, when the processing unit 1502 receives the second message from the network device through the communication unit 1501, it is specifically configured to:

Use the fourth RNTI to receive the second message from the network device through the communication unit 1501.

After receiving the second message from the network device, a fourth message is received from the network device through the communication unit 1501, the fourth message contains uplink authorization information, and the uplink authorization information is used for the terminal The device switches from the RRC idle state to the RRC connected state for uplink data transmission.

In a possible implementation manner, the processing unit 1502, when receiving the fourth message from the network device through the communication unit 1501, is specifically configured to:

Use the second RNTI to receive the fourth message from the network device through the communication unit 1501; or use the first RNTI to receive the fourth message from the network device through the communication unit 1501.

In a possible implementation manner, the processing unit 1502, when receiving the fourth message from the network device through the communication unit 1501, is specifically configured to: use the fourth RNTI to pass the communication unit 1501 receives the fourth message from the network device.

In a possible implementation manner, the processing unit 1502 is further configured to: after switching from the RRC idle state to the RRC connected state, use the second RNTI to send the fourth RNTI to the network device through the communication unit 1501 news.

In a possible implementation manner, the processing unit 1502 is further configured to: after receiving the first message from the network device, send the communication unit 1501 to the network device in the RRC idle state through the communication unit 1501 Random access preamble.

After receiving the second message from the network device, use the first RNTI to send a fourth message to the network device through the communication unit 1501.

It should be noted that the division of modules in the above embodiments of this application is illustrative, and is only a logical function division. In actual implementation, there may be other division methods. In addition, each function in each embodiment of this application The unit can be integrated into one processing unit, or it can exist alone physically, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solution of this application essentially or the part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , Including a number of instructions to make a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

Based on the same technical concept, an embodiment of the present application also provides a communication device, which can be applied to a network device or a terminal device, and can implement the RNTI update method in the above embodiment. Wherein, the terminal device and the network device may be applicable to the communication system as shown in FIG. 1. Referring to FIG. 16, the communication device 1600 includes: a transceiver 1601, a processor 1602, and a memory 1603. Wherein, the transceiver 1601, the processor 1602, and the memory 1603 are connected to each other.

Optionally, the transceiver 1601, the processor 1602, and the memory 1603 are connected to each other through a bus 1604. The bus 1604 may be a peripheral component interconnect standard (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, only one thick line is used in FIG. 16, but it does not mean that there is only one bus or one type of bus.

The transceiver 1601 is used to receive and send signals to realize communication with other devices in the communication system. Optionally, the transceiver 1601 may be implemented by a radio frequency device and an antenna.

In an implementation manner, the communication device 1600 may be applied to a network device. The processor 1602 is configured to implement the functions of the network device in the RNTI update method in the above figures. For details, reference may be made to the description in the above embodiment, which will not be repeated here.

In an implementation manner, the communication device 1600 may be applied to a terminal device. The processor 1602 is configured to implement the functions of the terminal device in the RNTI update method in the above figures. For details, reference may be made to the description in the above embodiment, which will not be repeated here.

The processor 1602 may be a central processing unit (CPU), a network processor (NP), or a combination of CPU and NP, and so on. The processor 1602 may further include a hardware chip. The aforementioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof. When the processor 1602 implements the above functions, it may be implemented by hardware, and of course, it may also be implemented by hardware executing corresponding software.

The memory 1603 is used to store program instructions and the like. Specifically, the program instructions may include program code, and the program code includes computer operation instructions. The memory 1603 may include a random access memory (RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory. The processor 1602 executes the program instructions stored in the memory 1603 to realize the above-mentioned functions, thereby realizing the RNTI update method provided in the above-mentioned embodiment.

Based on the above embodiments, the embodiments of the present application also provide a network device. As shown in FIG. 17, the network device can be applied to the system shown in FIG. 1 to perform the functions of the network device in the foregoing method embodiment. As shown in FIG. 17, the network equipment includes: an antenna 1710, a radio frequency device 1720, and a baseband device 1730. The antenna 1710 is connected to the radio frequency device 1720. In the uplink direction, the radio frequency device 1720 receives the information sent by the terminal device through the antenna 1710, and sends the information sent by the terminal device to the baseband device 1730 for processing. In the downlink direction, the baseband device 1730 processes the information to be sent and sends it to the radio frequency device 1720, and the radio frequency device 1720 processes the information and sends it out via the antenna 1710.

The baseband device 1730 may be a physical device, or may include at least two physically separated devices, such as a CU and at least one DU. The DU and the radio frequency device 1720 can be integrated into one device or physically separated. There is no restriction on the division of the protocol layer between at least two devices physically separated by the baseband device 1730. For example, the baseband device 1730 is used to perform RRC, PDCP, RLC, MAC, and physical layer processing at the protocol layers, and can Divide between any two protocol layers, so that the baseband device includes two physically separated devices, which are respectively used to process the protocol layers for which they are responsible. For example, divide between RRC and PDCP, and for example, divide between PDCP and RLC. In addition, it can also be divided within the protocol layer, for example, a certain protocol layer part and the protocol layer above the protocol layer are divided into one device, and the remaining part of the protocol layer and the protocol layer below the protocol layer are divided into another device . The above network equipment may be located on one of at least two physically separated devices of the baseband device 1730.

The network device may include multiple baseband boards, and multiple processing elements may be integrated on the baseband boards to achieve required functions. The baseband device 1730 may include at least one baseband board.

In one implementation, each unit shown in FIG. 15 is implemented in the form of a processing element scheduler. For example, the baseband device 1730 includes a processing element 1731 and a storage element 1732. The processing element 1731 calls a program stored in the storage element 1732 to execute the above method. The method executed by the network device in the embodiment. In addition, the baseband device 1730 may also include an interface 1733 for exchanging information with the radio frequency device 1720. The interface is, for example, a common public radio interface (CPRI). When the baseband device 1730 and the radio frequency device 1720 are physically arranged At the same time, the interface 1731 can be an intra-board interface or an inter-board interface, where the board refers to a circuit board.

In another implementation, each unit shown in FIG. 15 may be one or more processing elements configured to implement the method executed by the above network device. These processing elements are provided on the baseband device 1730, where the processing elements may be Integrated circuits, such as: one or more ASICs, or, one or more DSPs, or, one or more FPGAs, etc. These integrated circuits can be integrated together to form a chip.

For example, the units shown in FIG. 15 may be integrated together and implemented in the form of a system-on-a-chip (SOC). For example, the baseband device 1730 includes an SOC chip for implementing the above method. The processing element 1731 and the storage element 1732 can be integrated in the chip, and the processing element 1731 calls the stored program of the storage element 1732 to implement the method executed by the above network device or the function of each unit shown in FIG. 15. Alternatively, at least one integrated circuit may be integrated in the chip to implement the method executed by the above network device or the function of each unit shown in FIG. 15. Alternatively, the above implementation manners may be combined, and the functions of some units are implemented in the form of calling programs by processing elements, and the functions of some units are implemented in the form of integrated circuits.

Regardless of the method used, in short, the above network device includes at least one processing element and a storage element, wherein at least one processing element is used to execute the method performed by the network device provided in the above method embodiment. The processing element can execute part or all of the steps performed by the network device in the above method embodiments in the first way: that is, by executing the program stored by the storage element; or in the second way: that is, through the hardware in the processor element. The integrated logic circuit combines instructions to execute part or all of the steps performed by the network device in the above method embodiments; of course, it is also possible to combine the first and second methods to execute part or all of the steps performed by the network device in the above method embodiments. .

The processing element here is the same as the above description, and it can be a general-purpose processor, such as a central processing unit (CPU), or one or more integrated circuits configured to implement the above methods, such as one or more specific Integrated Circuit (Application Specific Integrated Circuit, ASIC), or, one or more microprocessors (digital digital processor, DSP), or, one or more Field Programmable Gate Array (FPGA), etc.

The storage element can be a memory or a collective term for multiple storage elements.

Based on the above embodiments, the embodiments of the present application also provide a terminal device. As shown in FIG. 18, the terminal device can be applied to the system shown in FIG. 1 to perform the functions of the terminal device in the above method embodiment. As shown in FIG. 18, the terminal equipment includes: an antenna 1810, a radio frequency device 1820, and a baseband device 1830. The antenna 1810 is connected to the radio frequency device 1820. In the downlink direction, the radio frequency device 1820 receives the information sent by the network device through the antenna 1810, and sends the information sent by the network device to the baseband device 1830 for processing. In the upstream direction, the baseband device 1830 processes the information to be sent and sends it to the radio frequency device 1820. The radio frequency device 1820 processes the information of the terminal equipment and sends it to the network equipment via the antenna 1810.

The baseband device 1830 may include a modulation and demodulation subsystem for processing data at various communication protocol layers. The terminal device may also include a central processing subsystem for processing the terminal device operating system and application layer. In addition, the terminal equipment can also include other subsystems, such as multimedia subsystems, peripheral subsystems, etc., where the multimedia subsystem is used to control the terminal equipment camera, screen display, etc., and the peripheral subsystem is used to realize the connection with other devices. . The modem subsystem can be a separate chip. Optionally, the functions of the above terminal equipment can be implemented on the modem subsystem.

In one implementation, each unit shown in FIG. 15 is implemented in the form of a processing element scheduler. For example, a certain subsystem of the baseband device 1830, such as a modem subsystem, includes a processing element 1831 and a storage element 1832, and a processing element 1831. The program stored in the storage element 1832 is called to execute the method executed by the terminal device in the above method embodiment. In addition, the baseband device 1830 may also include an interface 1833 for exchanging information with the radio frequency device 1820.

In another implementation, each unit shown in FIG. 15 may be one or more processing elements configured to implement the method executed by the above terminal device. These processing elements are provided on a certain subsystem of the baseband device 1830, such as modulation On the demodulation subsystem, the processing elements here may be integrated circuits, such as: one or more ASICs, or, one or more DSPs, or, one or more FPGAs, etc. These integrated circuits can be integrated together to form a chip.

For example, the various units shown in FIG. 15 may be integrated together and implemented in the form of a system-on-a-chip (SOC). For example, the baseband device 1830 includes an SOC chip for implementing the above method. The processing element 1831 and the storage element 1832 can be integrated in the chip, and the processing element 1831 calls the stored program of the storage element 1832 to implement the method executed by the above terminal device or the function of each unit shown in FIG. 15; or, the chip can be Integrate at least one integrated circuit to implement the method executed by the above terminal device or the function of each unit shown in Figure 15; or, it can be combined with the above implementation. The functions of some units are implemented in the form of processing element call programs, and the functions of some units Realized in the form of integrated circuits.

Regardless of the method used, in short, the above-mentioned terminal device includes at least one processing element and a storage element, wherein at least one processing element is used to execute the method performed by the terminal device provided in the above method embodiment. The processing element can execute part or all of the steps performed by the terminal device in the above method embodiments in the first way: that is, by executing the program stored in the storage element; or in the second way: that is, through the hardware in the processor element. The integrated logic circuit combines instructions to execute part or all of the steps performed by the terminal device in the above method embodiments; of course, it is also possible to combine the first and second methods to execute part or all of the steps performed by the terminal device in the above method embodiments. .

The processing element here is the same as the above description, and it can be a general-purpose processor, such as a central processing unit (CPU), or one or more integrated circuits configured to implement the above methods, such as one or more specific Integrated circuit (Application Specific Integrated Circuit, ASIC), or, one or more microprocessors (digital digital processor, DSP), or, one or more Field Programmable Gate Array (Field Programmable Gate Array, FPGA), etc.

Based on the above embodiments, the embodiments of the present application also provide a computer program, which when the computer program runs on a computer, causes the computer to execute the RNTI update method provided in the above embodiments.

Based on the above embodiments, the embodiments of this application also provide a computer storage medium in which a computer program is stored. When the computer program is executed by a computer, the computer executes the RNTI update method provided in the above embodiment.

Based on the above embodiments, an embodiment of the present application also provides a chip, which is used to read a computer program stored in a memory to implement the RNTI update method provided in the above embodiment.

Based on the above embodiments, an embodiment of the present application provides a chip system, which includes a processor, and is used to support a computer device to implement the RNTI update method provided in the above embodiment. In a possible design, the chip system further includes a memory, and the memory is used to store necessary programs and data of the computer device. The chip system can be composed of chips, or include chips and other discrete devices.

In summary, the embodiment of the present application provides an RNTI update method. In this method, the network device may notify the terminal device to switch after notifying the terminal device of the first RNTI used for data transmission in the RRC idle state. The second RNTI used for data transmission after reaching the RRC connected state. With this method, the network device can update the RNTI of the terminal device, which can prevent the terminal device from using the same RNTI in the RRC idle state and the RRC connected state, thereby avoiding multiple terminal devices capable of data transmission in the RRC idle state The occurrence of RNTI conflicts can ultimately ensure normal resource scheduling and data transmission for terminal equipment.

Those skilled in the art should understand that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

This application is described with reference to flowcharts and/or block diagrams of methods, equipment (systems), and computer program products according to the embodiments of this application. It should be understood that each process and/or block in the flowchart and/or block diagram, and the combination of processes and/or blocks in the flowchart and/or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing equipment to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing equipment are generated It is a device that realizes the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device. The device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment. The instructions provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.

Obviously, those skilled in the art can make various changes and modifications to the embodiments of the present application without departing from the scope of the embodiments of the present application. In this way, if these modifications and variations of the embodiments of this application fall within the scope of the claims of this application and their equivalent technologies, this application is also intended to include these modifications and variations.

Claims

A method for updating RNTI of a wireless network temporary identifier, which is characterized in that it includes:

The network device sends a first message to the terminal device, where the first message is used to notify the terminal device of the first RNTI allocated by the network device to the terminal device, and the first RNTI is used for the terminal device Perform data transmission in the radio resource control RRC idle state;

The network device sends a second message to the terminal device in the RRC idle state of the terminal device, where the second message is used to notify the terminal device of the second message that the network device is assigned to the terminal device RNTI, the second RNTI is used for the terminal device to perform data transmission after switching from the RRC idle state to the RRC connected state.
The method according to claim 1, wherein the first message includes the first RNTI; or, the first message includes first indication information, and the first indication information is used to indicate the first RNTI One RNTI.
The method of claim 2, wherein:

The first indication information indicates that the first RNTI is the RNTI used when the network device sends the first message; or,

The first indication information indicates that the first RNTI is a third RNTI, and the third RNTI is allocated by the network device to the terminal device before sending the first message to the terminal device, the The third RNTI is used for the terminal equipment to perform data transmission in the RRC idle state; or,

The first indication information indicates that the first RNTI is the RNTI used in the current RRC connected state.
The method according to any one of claims 1 to 3, wherein the first message further contains configuration information of a target resource, and the target resource is used by the terminal device for data transmission in an RRC idle state Resources.
The method according to any one of claims 1 to 4, wherein after the network device sends the first message to the terminal device, the method further comprises:

The network device receives a third message sent by the terminal device using the first RNTI in the RRC idle state, where the third message carries uplink data.
The method according to any one of claims 1-5, wherein the second message includes the second RNTI; or, the second message includes second indication information, and the second indication is used for Indicates the second RNTI.
The method according to claim 6, wherein the second indication information indicates that the second RNTI is the first RNTI; or,

The second indication information indicates that the second RNTI is the fourth RNTI used when the network device sends the second message.
7. The method according to any one of claims 1-7, wherein the network device sending the second message to the terminal device comprises:

The network device uses the first RNTI to send the second message to the terminal device.
The method according to claim 1, wherein the first message is a paging message, and the first message includes a random access preamble and the first RNTI.
The method of claim 9, wherein:

After the network device sends the first message to the terminal device, the method further includes: the network device receives the random access preamble sent by the terminal device in the RRC idle state of the terminal device code;

The sending of the second message by the network device to the terminal device includes:

The network device uses the first RNTI to send the second message to the terminal device.
A method for updating RNTI of a wireless network temporary identifier, which is characterized in that it includes:

The terminal device receives a first message from the network device, where the first message is used to notify the terminal device of the first RNTI allocated by the network device to the terminal device, and the first RNTI is used for the terminal device Perform data transmission in the radio resource control RRC idle state;

The terminal device receives a second message from the network device in the RRC idle state, where the second message is used to notify the terminal device of the second RNTI allocated by the network device to the terminal device, and the first The second RNTI is used for the terminal equipment to perform data transmission after switching from the RRC idle state to the RRC connected state.
The method of claim 11, wherein the first message includes the first RNTI; or, the first message includes first indication information, and the first indication information is used to indicate the first RNTI. One RNTI.
The method of claim 12, wherein:

The first indication information indicates that the first RNTI is the RNTI used when the network device sends the first message; or,

The first indication information indicates that the first RNTI is a third RNTI, and the third RNTI is allocated by the network device to the terminal device before sending the first message to the terminal device, the The third RNTI is used for the terminal equipment to perform data transmission in the RRC idle state; or

The first indication information indicates that the first RNTI is the RNTI used in the current RRC connected state.
The method according to any one of claims 11-13, wherein the first message further contains configuration information of a target resource, and the target resource is used by the terminal device for data transmission in the RRC idle state Resources.
The method according to any one of claims 11-14, wherein after the terminal device receives the first message from the network device, the method further comprises:

In the RRC idle state, the terminal device uses the first RNTI to send a third message to the network device, where the third message carries uplink data.
The method according to any one of claims 11-15, wherein the second message includes the second RNTI; or, the second message includes second indication information, and the second indication is used for Indicates the second RNTI.
The method according to claim 16, wherein the second indication information indicates that the second RNTI is the first RNTI; or,

The second indication information indicates that the second RNTI is the fourth RNTI used when the network device sends the second message.
The method according to any one of claims 11-17, wherein the terminal device receiving the second message from the network device comprises:

The terminal device uses the first RNTI to receive the second message from the network device.
The method according to claim 11, wherein the first message is a paging message, and the first message includes a random access preamble and the first RNTI.
The method of claim 19, wherein:

After the terminal device receives the first message from the network device, the method further includes: the terminal device sends the random access preamble to the network device in an RRC idle state;

The terminal device receiving the second message from the network device includes:

The terminal device uses the first RNTI to receive the second message from the network device.
A communication device, characterized by comprising:

Transceiver, used to receive and send signals;

Memory, used to store program instructions;

The processor is configured to read and run program instructions from the memory, and execute the method according to any one of claims 1-20 through the transceiver.
A computer program, characterized in that when the computer program runs on a computer, the computer executes the method according to any one of claims 1-20.
A computer storage medium, characterized in that a computer program is stored in the computer storage medium, and when the computer program is executed by a computer, the computer is caused to execute the method according to any one of claims 1-20.
A chip, characterized in that the chip is used to read a computer program stored in a memory, and execute the method according to any one of claims 1-20.