WO2023001149A1 - 一种控制传输的方法及相关装置 - Google Patents

一种控制传输的方法及相关装置 Download PDF

Info

Publication number
WO2023001149A1
WO2023001149A1 PCT/CN2022/106522 CN2022106522W WO2023001149A1 WO 2023001149 A1 WO2023001149 A1 WO 2023001149A1 CN 2022106522 W CN2022106522 W CN 2022106522W WO 2023001149 A1 WO2023001149 A1 WO 2023001149A1
Authority
WO
WIPO (PCT)
Prior art keywords
timer
rrc
terminal
sdt
running
Prior art date
Application number
PCT/CN2022/106522
Other languages
English (en)
French (fr)
Inventor
张梦晨
徐海博
阿鲁瓦利亚贾格迪普•辛格
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN202110897870.3A external-priority patent/CN115696644A/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP22845314.8A priority Critical patent/EP4366378A1/en
Publication of WO2023001149A1 publication Critical patent/WO2023001149A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a method for controlling transmission and a related device.
  • a communication protocol stack between a terminal and a network device may include a radio resource control (radio resource control, RRC) layer.
  • RRC radio resource control
  • RRC idle RRC IDLE
  • RRC INACTIVE RRC inactive
  • RRC CONNECTED RRC connected
  • the RAN-based notification area can be managed by the radio access network (RAN), for example, the terminal can trigger RNA update (RNA update, RNAU), execute It is used in the RRC connection recovery process of the RNAU to notify the network equipment of the current RNA of the terminal.
  • RAN-based notification area RNA
  • RNAU RNA update
  • the terminal When the terminal performs SDT, it may trigger the execution of RNAU. In this case, the terminal may stop the current SDT and execute RNAU, thereby affecting the transmission of small data, such as increasing the transmission delay, and subsequent SDT will also increase the power. consumption and signaling overhead.
  • the embodiment of the present application discloses a method for controlling transmission and a related device, which can avoid affecting the transmission of small packet data and unnecessary power consumption and signaling overhead.
  • the embodiment of the present application provides a method for controlling transmission, which is applied to a terminal in a non-radio resource control RRC connection state, and the method includes: when the first preset condition is met, performing The notification area of the network updates the RRC connection recovery process of RNAU; wherein, the first preset condition includes that the second timer expires and the first timer is not running; or, the first preset condition includes that the terminal receives The system information block SIB1 of the first serving cell, the first serving cell does not belong to the configured notification area RNA based on the radio access network, and the first timer is not running; wherein the first timer is in the The terminal is started when the RRC connection recovery process for small packet data transmission SDT is initiated, and the second timer is started when the terminal receives the RRC release message including the duration of the second timer.
  • the RRC connection recovery process for the RNAU includes sending an RRC request message, in which the resumeCause information element IE is rna-Update.
  • the second timer is T380.
  • RNAU when the first timer is running (that is, in the process of SDT), RNAU will not be executed.
  • SDT is executed, the network device can obtain the RNA where the terminal is located. Not executing RNAU will not only affect the acquisition of the terminal by the network device state, and can avoid affecting the small packet data transmitted by the SDT process, such as avoiding increasing the transmission delay, and subsequently re-initiating SDT to increase unnecessary signaling overhead and power consumption.
  • the not running of the first timer means that the first timer is not started.
  • the first timer not being started indicates that there is no need for SDT.
  • the method further includes: initiating the user In the RRC connection recovery process of SDT, the first timer is started; cell reselection occurs, and the first timer is stopped; the first preset condition includes that the first timer is not running and the terminal's The serving cell does not belong to the configured RNA, the first timer is not running because the first timer is stopped, and the serving cell of the terminal is the serving cell after cell reselection of the terminal.
  • the RRC connection recovery process for SDT includes sending an RRC request message, where the resumeCause IE in the RRC request message is mo-data.
  • the first preset condition further includes: the terminal is in an RRC inactive state; and/or, the terminal cannot perform an SDT process in the serving cell.
  • the terminal cannot perform the SDT process in the serving cell, including: the terminal cannot continue the previous SDT process in the serving cell. In some embodiments, the terminal cannot perform the SDT process in the serving cell, including: the terminal cannot initiate a new SDT process in the serving cell.
  • the method further includes: when the first timer is running, if an RRC reject message is received, stopping the first timer; if the second timer is not running, A first variable is set to a first value indicating that there is a pending RNA update process.
  • the terminal will not execute RNAU, nor will the first variable be set to the first value, so as to avoid affecting the current SDT process.
  • the terminal can set the first variable to the first value, so that RNAU can be normally executed subsequently.
  • the method further includes: when the first timer is running, if an RRC reject message is received, stopping the first timer; if the second timer is not running, Execute the radio resource control RRC connection recovery procedure for the RNAU.
  • the terminal will not execute the RNAU, so as to avoid affecting the current SDT process.
  • the terminal executes the RNAU again to ensure normal execution of the RNAU.
  • the method further includes: when the first timer is running, if an RRC reject message is received, stopping the first timer; if the second timer is not running, Start a third timer, and when the third timer expires, if the first timer is not running, execute the RRC connection recovery process for the RNAU.
  • the duration of the third timer is the same as that of the second timer.
  • the duration of the third timer is different from that of the second timer.
  • the non-radio resource control RRC connection state is an RRC inactive state; after the terminal receives an RRC rejection message, the terminal is in the RRC inactive state.
  • the terminal will not execute the RNAU, nor will it start the third timer, so as to avoid affecting the current SDT process.
  • the terminal can start the third timer, and when the third timer times out and the first timer is not running, execute
  • the radio resource control RRC connection restoration process used for RNAU ensures the normal execution of RNAU.
  • the method further includes: when the first timer expires, if the second timer is not running, setting the first variable to a first value, and the first variable is The first value indicates that there is a pending RNA renewal process.
  • the method further includes: when the first timer expires, if the second timer is not running, executing the radio resource control RRC connection recovery procedure for the RNAU.
  • the method further includes: when the first timer expires, if the second timer is not running, start a third timer, and when the third timer expires, if The first timer is not running, and the RRC connection recovery process for RNAU is executed.
  • the duration of the third timer is the same as that of the second timer.
  • the duration of the third timer is different from that of the second timer.
  • the non-radio resource control RRC connection state is an RRC inactive state; after the first timer expires, the terminal is in the RRC inactive state.
  • the method further includes: when the first timer is running, if cell reselection occurs, stopping the first timer; receiving the SIB1 of the second serving cell, and the first The second serving cell is the serving cell after cell reselection of the terminal; when receiving the SIB1 of the second serving cell, if the second serving cell belongs to the configured RNA and the second timer is not running , setting the first variable to a first value, the first value indicating that there is a pending RNA update process.
  • the method further includes: when the first timer is running, if cell reselection occurs, stopping the first timer; receiving the SIB1 of the second serving cell, and the first The second serving cell is the serving cell after cell reselection of the terminal; when receiving the SIB1 of the second serving cell, if the second serving cell belongs to the configured RNA and the second timer is not running , executing the radio resource control RRC connection recovery procedure for the RNAU.
  • the method further includes: when the first timer is running, if cell reselection occurs, stopping the first timer; receiving the SIB1 of the second serving cell, and the first The second serving cell is the serving cell after cell reselection of the terminal; when receiving the SIB1 of the second serving cell, if the second serving cell belongs to the configured RNA and the second timer is not running , start a third timer, and when the third timer times out, if the first timer is not running, execute the RRC connection recovery process for RNAU.
  • the duration of the third timer is the same as that of the second timer.
  • the duration of the third timer is different from that of the second timer.
  • the non-radio resource control RRC connection state is an RRC inactive state; after cell reselection occurs in the terminal, the terminal is in the RRC inactive state.
  • the method further includes: if the access barring is eased and the non-access NAS layer does not request the RRC layer to perform RRC connection recovery, if The first variable is the first value, and the RRC connection recovery procedure for RNAU is executed.
  • the non-radio resource control RRC connection state is an RRC inactive state.
  • the embodiment of the present application provides another method for controlling transmission, which is applied to a terminal in a non-RRC connection state, and the method includes: when the first preset condition is met, setting the first variable to the first value , the first variable is the first value indicating that there is a pending RNA update process, the first preset condition includes that the first timer is not running, and the first timer is received by the terminal including the It is turned on when the RRC release message with the first timer duration.
  • the first timer is T380.
  • the first preset condition further includes that the terminal receives an RRC rejection message when the second timer is running; It is started during the RRC connection recovery process, and the second timer is stopped when the terminal receives the RRC rejection message.
  • the first preset condition further includes that a second timer expires, and the second timer is started when the terminal initiates an RRC connection recovery process for SDT.
  • the non-RRC connected state is an RRC inactive state; after the second timer expires, the terminal is in the RRC inactive state.
  • the first preset condition further includes that the terminal receives the SIB1 of the first serving cell, and the first serving cell belongs to the configured RNA; the first preset condition is met , before setting the first variable to the first value, the method further includes: when the second timer is running, if cell reselection occurs, stopping the second timer, and the second timer is in the It is turned on when the terminal initiates the RRC connection recovery process for SDT; and receives the SIB1 of the first serving cell, where the first serving cell is the serving cell after cell reselection of the terminal.
  • the method further includes: if the access barring is eased and the non-access NAS layer does not request the RRC layer to perform RRC connection recovery, if The first variable is the first value, and an RRC connection recovery procedure for RNAU is performed.
  • the non-RRC connected state is an RRC inactive state.
  • the terminal will not execute RNAU, nor will the first variable be set to the first value, so as to avoid affecting the current SDT process.
  • the terminal can set the first variable to the first value, so that RNAU can be normally executed subsequently.
  • the embodiment of the present application provides another method for controlling transmission, which is applied to a terminal in a non-RRC connection state, and the method includes: starting a first timer; initiating an RRC connection recovery process for SDT; In the RRC connection recovery process for SDT, the bottom layer indicates first information to the upper layer, and the first information indicates that the RRC connection recovery process for SDT is successful; based on the first information, stop the first timing device.
  • the terminal starts the first timer when receiving the RRC release message including the duration of the first timer.
  • the first timer is T380.
  • the first timer when the terminal performs the SDT process, the first timer may be stopped, so as to avoid triggering the RNAU when the first timer expires.
  • the network device can obtain the RNA of the terminal. If RNAU is not triggered, it will not affect the state of the terminal obtained by the network device, but also avoid affecting the small packet data transmitted during the SDT process.
  • the initiating the RRC connection recovery process for SDT includes: the terminal sends an RRC request message to a network device, and the bottom layer of the terminal receives a response from the network device to the The first response message sent by the RRC request message: the bottom layer indicates the first information to the upper layer, including: based on the first response message, the bottom layer indicates the first information to the upper layer.
  • the RRC connection recovery process for SDT includes: the terminal sends an RRC request message to the network device during the random access process; the bottom layer indicates the first information to the upper layer, including: The medium access control MAC layer indicates first information to the RRC layer, and the first information indicates that contention resolution is successful; the stopping the first timer based on the first information includes: the RRC layer receives the the first information indicated by the MAC layer, and stop the first timer.
  • the terminal sending the RRC request message to the network device includes: the terminal sending the RRC request message to the network device during a random access process, and the first response message indicates Competition resolved successfully.
  • the first response message is a contention resolution message.
  • the RRC connection recovery process for SDT includes: the terminal sends an RRC request message to the network device based on pre-configured uplink resources; the first information indicates that the RRC request message is sent success.
  • the bottom layer indicates the first information to the upper layer, including: the medium access control MAC layer indicates the first information to the RRC layer; based on the first information, stopping the first timing
  • the device includes: the RRC layer receives the first information indicated by the MAC layer, and stops the first timer; or, the bottom layer indicates the first information to the upper layer, including: the physical layer indicates the RRC layer First information; the stopping the first timer based on the first information includes: the RRC layer receives the first information indicated by the physical layer, and stops the first timer; or Before the bottom layer indicates the first information to the upper layer, the method further includes: the physical layer indicates second information to the MAC layer, and the second information indicates that the RRC request message is successfully sent; the bottom layer indicates the first information to the upper layer.
  • the information includes: the MAC layer receives the second information indicated by the physical layer, and indicates the first information to the RRC layer; the stopping of the first timer based on the first information includes: the The RRC layer receives the first information indicated by the MAC layer, and stops the first timer.
  • the terminal sending the RRC request message to the network device includes: the terminal sending the RRC request message to the network device based on preconfigured uplink resources, and the first response message indicates The RRC request message is sent successfully.
  • the initiating the RRC connection recovery process for SDT includes: initiating the RRC connection recovery process for SDT, and starting a second timer.
  • the method further includes: when the second timer is running, if an RRC rejection message is received, stopping the second timer ; If the first timer is not running, set the first variable to a first value, where the first value of the first variable indicates that there is a pending RNA update process.
  • the terminal can set the first variable to the first value when the SDT process ends abnormally (such as the second timer stops or times out), so that the subsequent Continue to trigger RNAU to ensure the normal execution of RNAU.
  • the method further includes: when the second timer is running, if an RRC rejection message is received, stopping the second timer ; If the first timer is not running, execute the radio resource control RRC connection recovery process for RNAU.
  • the terminal can execute the RNAU again when the SDT process ends abnormally (such as the second timer stops or times out), so as to ensure the normal execution of the RNAU.
  • the method further includes: when the second timer is running, if an RRC rejection message is received, stopping the second timer ; If the first timer is not running, start a third timer, and when the third timer expires, if the second timer is not running, execute the RRC connection recovery process for RNAU.
  • the duration of the third timer is the same as that of the first timer.
  • the duration of the third timer is different from that of the first timer.
  • the non-radio resource control RRC connection state is an RRC inactive state; after the terminal receives an RRC rejection message, the terminal is in the RRC inactive state.
  • the terminal can start the third timer when the SDT process ends abnormally (such as the second timer stops or times out), and when the third timer times out and the first When the second timer is not running, execute RNAU again to ensure the normal execution of RNAU.
  • the method further includes: when the second timer expires, if the first timer is not running, setting the first variable to a first value, and the first variable is The first value indicates that there is a pending RNA renewal process.
  • the method further includes: when the second timer expires, if the first timer is not running, executing the radio resource control RRC connection recovery procedure for the RNAU.
  • the method further includes: when the second timer expires, if the first timer is not running, start a third timer, and when the third timer expires, if The second timer is not running, and the RRC connection recovery process for RNAU is executed.
  • the duration of the third timer is the same as that of the first timer.
  • the duration of the third timer is different from that of the first timer.
  • the non-radio resource control RRC connection state is an RRC inactive state; after the first timer expires, the terminal is in the RRC inactive state.
  • the method further includes: when the second timer is running, if cell reselection occurs, stopping the second timer; receiving the SIB1 of the first serving cell, and the first A serving cell is the serving cell after cell reselection of the terminal; when receiving the SIB1 of the first serving cell, if the first serving cell belongs to the configured RNA and the first timer is not running , setting the first variable to a first value, the first value indicating that there is a pending RNA update process.
  • the method further includes: when the second timer is running, if cell reselection occurs, stopping the second timer; receiving the SIB1 of the first serving cell, and the first A serving cell is the serving cell after cell reselection of the terminal; when receiving the SIB1 of the first serving cell, if the first serving cell belongs to the configured RNA and the first timer is not running , executing the radio resource control RRC connection recovery procedure for the RNAU.
  • the method further includes: when the second timer is running, if cell reselection occurs, stopping the second timer; receiving the SIB1 of the first serving cell, and the first A serving cell is the serving cell after cell reselection of the terminal; when receiving the SIB1 of the first serving cell, if the first serving cell belongs to the configured RNA and the first timer is not running , start a third timer, and when the third timer expires, if the second timer is not running, perform an RRC connection recovery process for the RNAU.
  • the duration of the third timer is the same as that of the second timer.
  • the duration of the third timer is different from that of the second timer.
  • the non-radio resource control RRC connection state is an RRC inactive state; after cell reselection occurs in the terminal, the terminal is in the RRC inactive state.
  • the method further includes: if the access barring is eased and the non-access NAS layer does not request the RRC layer to perform RRC connection recovery, if The first variable is the first value, and an RRC connection recovery procedure for RNAU is performed.
  • the non-RRC connected state is an RRC inactive state.
  • an embodiment of the present application provides a terminal, including a transceiver, a processor, and a memory; the memory is used to store computer program codes, the computer program codes include computer instructions, and the processor invokes the computer instructions to make the above
  • the user equipment executes the method for controlling transmission provided by the first aspect to the third aspect of the embodiments of the present application, and any implementation manner of the first aspect to the third aspect.
  • the embodiment of the present application provides a communication device, which may be a terminal or a chip in the terminal, and the communication device includes a processing unit, and the processing unit is used to implement the first aspect to the third aspect of the embodiment of the present application, And the method for controlling transmission provided by any one of the implementation manners from the first aspect to the third aspect.
  • the embodiment of the present application provides a computer storage medium, the computer storage medium stores a computer program, the computer program includes program instructions, and when the program instructions are executed by a processor, it is used to execute the first Aspect to the third aspect, and any implementation manner of the first aspect to the third aspect provides a control transmission method.
  • the embodiment of the present application provides a computer program product, which, when the computer program product is run on the communication device, enables the communication device to execute the first aspect to the third aspect, and the first aspect to the third aspect of the embodiment of the present application.
  • a method for controlling transmission provided by any implementation manner of the third aspect.
  • the embodiments of the present application provide an electronic device, where the electronic device includes executing the method or apparatus introduced in any embodiment of the present application.
  • the aforementioned electronic device is, for example, a chip.
  • FIG. 1 is a schematic structural diagram of a communication system provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of a communication protocol stack of a user plane of a new wireless access NR;
  • Fig. 3 is a schematic diagram of the architecture of the communication protocol stack of the control plane of NR;
  • FIG. 4 is a schematic diagram of transition of a radio resource control RRC state of a user equipment UE
  • FIGS. 5-10 are schematic flowcharts of some small packet data transmission SDTs provided by the embodiments of the present application.
  • FIG. 11 is a schematic flowchart of a method for controlling transmission provided in an embodiment of the present application.
  • Fig. 12 is a timing diagram provided by the embodiment of the present application.
  • Fig. 18 is another timing diagram provided by the embodiment of the present application.
  • FIG. 19 is a schematic flowchart of another method for controlling transmission provided by an embodiment of the present application.
  • the network device may be a device for sending or receiving information.
  • the network device is an access network device, such as but not limited to: base station, user equipment (user equipment, UE) , wireless access point (access point, AP), transceiver point (transmission and receiver point, TRP), relay equipment, or other network equipment with the function of a base station, etc.
  • the base station is a device deployed in a radio access network (radio access network, RAN) to provide a wireless communication function.
  • radio access network radio access network
  • the names of base stations may be different, such as but not limited to: global system for mobile communications (global system for mobile communications, GSM) or code division multiple access (code division multiple access, CDMA)
  • GSM global system for mobile communications
  • CDMA code division multiple access
  • BTS Base transceiver station
  • node B node B (node B, NB) in wideband code division multiple access (WCDMA)
  • WCDMA wideband code division multiple access
  • LTE long term evolution
  • evolved node B, eNodeB evolved node B, eNodeB
  • 5G fifth generation mobile communication technology
  • the terminal may be a device with a wireless communication function.
  • the terminal is a UE.
  • the terminal may also be called a mobile station, an access terminal, or a user agent.
  • the terminal is a terminal in the form of a handheld device, a wearable device, a computing device, a portable device, or a vehicle-mounted device.
  • the terminal is specifically a device such as a cellular phone, a smart phone, smart glasses, a laptop computer, a personal digital assistant, or a cordless phone. The following embodiments are described by taking the terminal as a UE as an example.
  • FIG. 1 is a schematic structural diagram of a communication system provided by an embodiment of the present application.
  • the communication system can be, but not limited to, GSM, CDMA, wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), universal mobile communication system (universal mobile telecommunications system, UMTS), LTE, NR, or other future network systems.
  • the communication system may include a core network 110 , a network device 120 and a UE 130 .
  • the core network 110 may be connected to at least one network device 120, the network device 120 may provide wireless communication services for at least one UE 130, and the UE 130 may be connected to at least one network device 120 through an air interface.
  • the core network 110 is a key control node in the communication system, and is mainly responsible for signaling processing functions, such as but not limited to functions such as access control, mobility management, and session management.
  • network device 120 is a base station.
  • the core network 110 may be called a 5G core network (5G Core, 5GC) 110, and the network device 120 may be called a gNB120.
  • At least one base station may constitute a next generation-radio access network (NG-RAN) node.
  • the NG-RAN node may include at least one gNB120 connected to the 5GC110 through the NG interface, and at least one gNB120 in the NG-RAN node may be connected and communicated through the Xn-C interface.
  • UE130 can connect to gNB120 through Uu interface.
  • the core network 110 can send downlink data to the UE 130 through the network device 120 , and the UE 130 can also send uplink data to the core network 110 through the connected network device 120 .
  • the shapes and quantities of the core network 110, the network device 120, and the UE 130 shown in FIG. 1 are only for example, and are not limited in this embodiment of the present application.
  • the embodiments of the present application mainly use LTE and/or NR as an applied communication system, network equipment as a base station, and an NG-RAN including at least one base station as an example for illustration.
  • FIG. 2 is a schematic diagram of an architecture of a user plane protocol stack of NR.
  • the user plane protocol stack may include a physical (physical, PHY) layer, a medium access control (medium access control, MAC) layer, a radio link control (radio link control, RLC) layer, a packet data convergence protocol (packet data convergence protocol) , PDCP) layer, service data adaptation protocol (service data adaptation protocol, SDAP) layer.
  • PHY physical
  • MAC medium access control
  • RLC radio link control
  • RLC radio link control
  • packet data convergence protocol packet data convergence protocol
  • PDCP packet data convergence protocol
  • SDAP service data adaptation protocol
  • FIG. 3 is a schematic diagram of an architecture of a control plane protocol stack of NR.
  • the control plane protocol stack may include a PHY layer, a MAC layer, an RLC layer, a PDCP layer, a radio resource control (radio resource control, RRC) layer, and a non-access stratum (non access stratum, NAS).
  • RRC radio resource control
  • NR's user plane protocol stack adds a new SDAP layer, but the architecture of other layers is the same, and the specific description is similar. LTE is more mature, so I won't repeat it here.
  • the lower layer of the PDCP layer includes the RLC layer.
  • the PDCP layer can process RRC messages on the control plane, and the PDCP layer can perform IP packet header compression to reduce the number of bits transmitted on the radio interface.
  • the PDCP layer can also be responsible for the encryption of the control plane and the integrity protection of the transmitted data.
  • the PDCP layer performs the corresponding decryption and decompression operations.
  • One PDCP entity can be configured for each radio bearer.
  • the RLC layer is responsible for splitting/cascading, retransmission control, and duplicate detection.
  • the RLC layer provides services for the PDCP layer.
  • One RLC entity can be configured for each radio bearer.
  • the MAC layer controls multiplexing of logical channels, retransmission of HARQ, scheduling of uplink and downlink, etc.
  • the MAC layer provides services for the RLC layer in the form of logical channels.
  • the PHY layer load manages encoding/decoding, modulation/demodulation, multi-antenna mapping, and other types of physical layer functions.
  • the PHY layer provides services for the MAC layer in the form of transmission channels.
  • the MAC layer can provide services for higher layers (such as the RLC layer) via a logical channel (logical channel, LCH).
  • Logical channels can be classified into control channels used to transmit control information on a control plane and traffic channels used to transmit user data on a user plane according to the type of transmitted information.
  • the control channel may include but not limited to a common control channel (common control channel, CCCH) and a dedicated control channel (dedicated control channel, DCCH).
  • the traffic channel may include but not limited to a dedicated traffic channel (dedicated traffic channel, DTCH).
  • the CCCH can exist all the time, and the UE that has no RRC connection with the RAN node can also use the CCCH to transmit information.
  • DCCH can be used to transmit dedicated control information between UE and RAN nodes.
  • DTCH can be used to transmit user data between UE and RAN nodes.
  • DCCH and DTCH do not exist all the time, but after the base station connected to the UE restores the UE context (UE context), the DCCH and DTCH can be used for communication between the UE and the base station.
  • UE context includes but not limited to terminal identification, radio bearer (radio bearer, RB) related configuration, security related configuration of integrity protection and encryption, quality of service related configuration, etc.
  • RB may be a connection format set between UE and RAN node, and may include related configurations of physical channels, transport channels and logical channels.
  • the RB can be divided into a signaling radio bearer (signaling radio bearer, SRB) used to transmit control information on the control plane and a data radio bearer (data radio bearer, DRB) used to transmit user data on the user plane.
  • a DRB may include a PDCP layer entity (PDCP entity for short), an RLC layer entity (RLC entity for short), and a logical channel.
  • the RRC layer can be used to transmit RRC messages between the UE and the base station.
  • the RRC resume request (RRCResumeRequest) in NR can be used for the UE to request to resume the suspended RRC connection, so as to transmit data with the base station.
  • the RRC layer belongs to the access stratum (AS).
  • RRC layer there are currently three UE RRC states, which are RRC IDLE state, RRC INACTIVE state and RRC CONNECTED state.
  • RRC states the UE performs mostly different operations.
  • the three states and the transition process please refer to the example in Figure 4 below.
  • an RRC connection is established between the UE and the base station.
  • a UE connection can be established between the 5GC and the NG-RAN
  • the connection between the user plane and the control plane, NG-RAN and UE can retain the UE context of the AS layer, NG-RAN can obtain the cell to which the UE belongs, the UE can send or receive unicast data, and the network (such as NG-RAN) can control the UE mobility, for example, the UE can measure the channel with the base station, and can report the measurement result to the base station, and the base station can determine whether to switch the cell to which the UE belongs according to the measurement result.
  • the UE and the base station can not only transmit data normally, but the base station can also manage the UE.
  • the UE in the RRC CONNECTED state wants to send uplink data to the base station, it needs to maintain synchronization with the base station according to timing advance (TA).
  • TA timing advance
  • the UE in the RRC CONNECTED state has not obtained uplink synchronization, the UE can initiate a random access (RA) to the base station.
  • TA timing advance timer
  • TAT timing advance timer
  • the base station can allocate configured grant (CG) resources for the UE.
  • CG configured grant
  • the base station may configure CG resources for the UE through an RRC message, and the configured information may include time-frequency position and period. Compared with dynamically scheduling transmission resources, this way of transmitting data through CG resources can reduce signaling overhead and transmission delay.
  • the UE in the RRC CONNECTED state can trigger a buffer status report (buffer status reporting, BSR) to request the base station to schedule uplink resources.
  • BSR buffer status reporting
  • the BSR can be used to indicate the amount of data currently to be transmitted in the data buffer (buffer) of the UE.
  • the amount of data can be different at different times.
  • the UE is a smart phone. Users can send messages to other users through social applications installed on the UE, but the types and quantities of messages sent by users at different times can be different. Sometimes the messages sent It may be just a text message, and sometimes the message sent may include multiple videos. Therefore, the size of the BSR sent by the UE to the base station at different times may also be different.
  • the resources for the UE to send the BSR to the base station (referred to as BSR resources) may be dynamically scheduled by the base station to the UE.
  • the UE When the UE is in the RRC IDLE state, no RRC connection is established between the UE and the base station.
  • the UE may select a public land mobile network (PLMN), receive system information broadcast by the base station, and perform cell re-selection. , called paging (Paging) initiated by 5GC for downlink transmission, and discontinuous reception (DRX) configured by the NAS layer for core network paging, etc.
  • PLMN public land mobile network
  • Paging paging
  • DRX discontinuous reception
  • the RRC INACTIVE state is a new RRC state in NR.
  • the base station usually keeps the UE in the RRC INACTIVE state.
  • the UE can select a PLMN, receive system information broadcast by the base station, cell reselection occurs, and the called paging (Paging) is initiated by the NG-RAN, and the NG-RAN Manage the RAN-based notification area (RAN-based Notification Area, RNA), for example, UE triggers RNA update (RNA update, RNAU) to notify the base station of the UE's current RNA, and NG-RAN configures DRX for RAN paging , 5GC and NG-RAN can establish a connection between the user plane and the control plane of the UE, the NG-RAN and the UE can retain the UE context of the AS layer, and the NG-RAN can obtain the RNA where the UE is located
  • RNA update RNA update
  • the UE after the UE establishes an RRC connection with the base station, the UE enters the RRC CONNECTED state. If the UE in the RRC CONNECTED state has no data transmission requirements with the base station within a preset period of time, the base station can instruct the UE to enter the RRC INACTIVE state. For example, the base station can send an RRC release (RRCRelease with suspend indication) message carrying a suspend indication to the UE. After the UE receives the RRC Release with suspend indication message, the UE retains its own context and enters the RRC INACTIVE state.
  • RRC release RRCRelease with suspend indication
  • the above three states in the RRC layer can be converted to each other, as shown in Figure 4, in some embodiments, when the UE is in the RRC IDLE state or the RRC INACTIVE state (which can be collectively referred to as the non-RRC connection state), if it is necessary to perform data transmission, an RRC connection establishment process or an RRC connection recovery process may be performed.
  • a UE in the RRC IDLE state can send an RRC Setup Request (RRCSetupRequest) message to the base station, and then receive the RRC Setup (RRCSetup) message sent by the base station. After receiving the RRCSetup message, the UE can establish an RRC connection with the base station and enter the RRC CONNECTED state.
  • RRCSetupRequest RRC Setup Request
  • RRCSetup RRC Setup
  • a UE in the RRC INACTIVE state can send an RRCResumeRequest message to the base station, and then receive an RRC resume (RRCResume) message sent by the base station. After receiving the RRCResume message, the UE can enter the RRC CONNECTED state.
  • the UE when the UE is in the non-RRC connected state, it can also execute the RRC connection establishment process or the RRC connection recovery process in response to the paging message from the base station.
  • the core network can instruct the base station to send The UE sends a paging message.
  • the UE can enter the RRC INACTIVE state or the RRC IDLE state from the RRC CONNECTED state under the instruction of the base station.
  • the base station may release the UE to enable the UE to enter the RRC INACTIVE state or the RRC IDLE state, and specific examples are as follows.
  • Example 1 the UE enters the RRC INACTIVE state from the RRC CONNECTED state under the instruction of the base station.
  • the base station can send a release message with a suspend indication to the UE, such as a RRCRelease with suspend indication message, so that the UE enters the RRC INACTIVE state.
  • the RRC connection between the UE and the base station will be suspended, but at least one RAN node retains the UE context of the UE.
  • Example 2 the UE enters the RRC IDLE state from the RRC CONNECTED state under the instruction of the base station.
  • the base station can send a release message to the UE, such as an RRC release (RRCRelease) message, so that the UE enters the RRC IDLE state.
  • RRC release RRCRelease
  • the RRC connection between the UE and the base station will be stopped, and the RAN node will delete the UE context of the UE.
  • the UE can also enter the RRC IDLE state from the RRC INACTIVE state under the instruction of the base station. For example, after the UE in the RRC INACTIVE state sends an RRC connection recovery request, the base station can release the UE so that the UE enters the RRC IDLE state . Understandably, compared with entering the RRC CONNECTED state from the RRC IDLE state, the UE enters the RRC CONNECTED state from the RRC INACTIVE state faster.
  • the RRC connection establishment process or the RRC connection recovery process may be performed to request to enter the RRC CONNECTED state to transmit data, wherein, if in the RRC IDLE
  • the UE in the RRC INACTIVE state or RRC INACTIVE has no resources to send the RRCSetupRequest message or the RRCResumeRequest message, the UE needs to initiate a random access (RA) process.
  • RA random access
  • the UE can obtain the RA configuration of the current cell from the system information broadcast by the base station, for example, the configuration includes the available random access preamble (random access preamble) and the RA resource for sending the random access preamble, for example, sending
  • the RA resource of the random access preamble is the time-frequency resource for the UE to send the random access preamble, and may also be called a random access occasion (random access occasion, RO).
  • RA may include 4-step random access (4-step RA for short) and 2-step random access (2-step RA for short).
  • the base station can broadcast the RA configuration corresponding to the 4-step RA and the RA configuration corresponding to the 2-step RA in the system message, or only broadcast the RA configuration corresponding to the 4-step RA in the system message, or only broadcast the RA configuration corresponding to the 2-step RA in the system message.
  • the base station may broadcast the RA configuration corresponding to the 4-step RA and the RA configuration corresponding to the 2-step RA in the system message.
  • the UE can base on the currently measured reference signal receiving power (reference signal receiving power, RSRP) and the relative size of the preset RSRP threshold, Determine to initiate 4-step RA or 2-step RA. For example, when the currently measured RSRP is greater than or equal to the preset RSRP threshold, the UE can initiate 2-step RA. When the currently measured RSRP is less than the preset RSRP threshold, the UE can initiate 4-step RA.
  • RSRP reference signal receiving power
  • the message sent by the UE to the base station in the third step of the 4-step RA may be called message 3, or msg3 for short.
  • the message sent by the UE to the base station can be called message A, or msgA for short.
  • the above msg3 or msgA may include an RRC message.
  • the RRC messages may be different when the UE is in different RRC states and in different service scenarios.
  • the msg3 sent by the UE to the base station may include the RRCResumeRequest message, so as to request to resume the suspended RRC connection and enter the RRC CONNECTED state to transmit data with the base station.
  • the UE in the non-RRC connection state has uplink data to send to the base station, or receives a paging (Paging) message sent by the base station, and the paging message is used by the base station to indicate that there is downlink data to send to the UE , the UE needs to re-establish or restore the RRC connection and enter the RRC CONNECTED state, and then transmit data with the base station in the RRC CONNECTED state.
  • Paging paging
  • this type of data packet can be called small data packet, and the signaling required for the UE switching state process is even larger than the small packet data, resulting in unnecessary power consumption and signaling overhead of the UE. Therefore, it is necessary to transmit small packet data to the base station when the UE is not in the RRC connection state. For example, when the UE in the RRC INACTIVE state has the transmission requirement of uplink small packet data, it can transmit the uplink small packet data to the base station.
  • small packet data may include, but is not limited to, data packets whose data volume is less than a preset threshold (such as the size of the transmission block indicated by the base station), data packets whose data label is small packet data, and data packets whose data type belongs to small packet data Wait.
  • the data packets of non-small packet data can be called large packet data, which can include but not limited to data packets whose data volume is greater than or equal to the preset threshold, data packets whose data label is large packet data, and data packets whose data type belongs to large packet data, etc.
  • the above-mentioned data label and/or the above-mentioned data type may be jointly negotiated by the UE and the network device.
  • data tags may include large and small packets of data.
  • data whose data type is heartbeat packet is small packet data
  • data whose data type is file, video or audio is large packet data.
  • the small packet data is an instant messaging message of an application program (application, APP) of the UE, a heartbeat packet of an APP or a push message of an APP, etc.
  • the small packet data is periodic data of a wearable device, etc.
  • the small packet data is the Internet of Things ( Internet of things, IoT) device business data, etc.
  • the above-mentioned transmission of small packet data to the base station when the UE is in the non-RRC connected state may include that the UE transmits small data during the RA process without entering the RRC CONNECTED state before transmitting small data.
  • the above transmission process may be referred to as RA-based small data transmission (small data transmission, SDT), referred to as RA-SDT.
  • RA can include 4-step RA and 2-step RA
  • SDT can also include SDT based on 4-step RA (abbreviated as 4-step SDT) and SDT based on 2-step RA (abbreviated as 2-step RA).
  • the process example of 4-step SDT can be seen in Figure 5 and Figure 6 below
  • the process example of 2-step SDT can be seen in Figure 7 and Figure 8 below.
  • the implementation of RA-SDT is similar to that of RA.
  • the UE can obtain the configuration of RA-SDT from the system information broadcast by the base station, and the UE can determine to initiate 4 based on the relative size of the currently measured RSRP and the preset RSRP threshold.
  • -step SDT or 2-step SDT.
  • transmitting the small packet data to the base station may also include that the UE transmits small data through pre-allocated CG resources or preconfigured uplink resources (preconfigured uplink resource, PUR) without Enter the RRC CONNECTED state and then transmit small data.
  • pre-allocated CG resources or preconfigured uplink resources preconfigured uplink resource, PUR
  • PUR preconfigured uplink resource
  • the SDT has multiple different application scenarios, and SDTs with different implementation manners, such as RA-SDT or CG-SDT, can be used according to the application scenarios.
  • SDTs with different implementation manners such as RA-SDT or CG-SDT, can be used according to the application scenarios.
  • a specific example is as follows:
  • Example 1 In CG-SDT, the resources indicated by the CG-SDT configuration (such as CG resources or PUR) are issued by the base station to the UE through dedicated control signaling, so the CG-SDT configuration is applicable to the UE in the cell covered by the base station For UEs, the CG-SDT configuration provided in one cell cannot be reused by UEs in another cell. If the UE moves to the coverage of other network devices, the resources indicated by the CG-SDT configuration cannot be used anymore.
  • the resources indicated by the CG-SDT configuration such as CG resources or PUR
  • UEs For IoT applications, UEs have limited mobility, and usually establish all connections in the same cell to send data, and rarely change cells, so UEs in the IoT field can preferentially use CG-SDT .
  • Example 2 RA-SDT configuration
  • the relevant RA configuration can be provided by the system information sent by the base station. Whenever the UE reselects to a new cell, the UE can read and apply the configuration broadcasted by the system information. Based on such characteristics, for example, it can It is applied to the following scenarios: For applications such as instant messaging messages on smart phones, the mobility of the UE is relatively strong, and the UE may move from the coverage area of one base station to the coverage area of another base station.
  • the UE moves from the coverage area of base station A to the coverage area of base station B, and is within the coverage area of base station B, it uses the resources indicated by the CG-SDT configuration sent by base station A before moving to perform SDT, and cannot transmit data due to RA -
  • the resources for sending the random access preamble in the SDT are broadcast by the base station in real time. Therefore, RA-SDT can be preferentially used for UEs with strong mobility.
  • the UE adopts the CG-SDT or the RA-SDT is not limited by the scenario, and it can be determined which way to use for the SDT based on the implementation of the UE.
  • the success rate of the UE performing CG-SDT is relatively high.
  • the random access resources of RA-SDT are broadcast by network equipment, and UEs that can receive the broadcast message can initiate RA-SDT on the random access resources, and multiple UEs will compete for resources, which may lead to the failure of the competition, so , the success rate of RA-SDT is not as high as that of CG-SDT, and CG-SDT may be more effective than RA-SDT.
  • the UE prefers to select CG-SDT, and the UE needs to meet certain conditions when selecting CG-SDT.
  • the UE can select RA-SDT. For example, whether there are resources indicated by the CG-SDT configuration within the range covered by the normal uplink (NUL) carrier or the supplementary uplink (SUL) carrier where the UE is currently located, if there is a resource indicated by the CG-SDT configuration If there are valid resources in the resources indicated by the CG-SDT configuration, the UE can select CG-SDT; otherwise, it can select RA-SDT.
  • NUL normal uplink
  • SUL supplementary uplink
  • the base station may first configure a DRB for carrying data for the UE, and the UE may transmit data after recovering the context (including the DRB).
  • the DRB configured by the base station for the UE may include a DRB for carrying small packet data (SDT DRB for short), and a DRB for carrying large packet data (non-SDT DRB (non-SDT DRB for short)). Only when the small packet data carried by SDT DRB arrives, the UE can initiate SDT. If the large packet data carried by non-SDT DRB arrives, the UE cannot initiate SDT. When UE initiates SDT, it needs to restore UE context, which can include SDT DRB.
  • the state of the SDT can be determined by the state of the first timer.
  • the first timer can be represented as T3XX, where X is a non-negative integer less than 10.
  • the first timer can be called the SDT failure detection timing A timer (SDT failure detection timer), the first timer may be a timer of the RRC layer.
  • the first timer when the UE initiates the RRC connection recovery procedure for SDT, the first timer may be started. In some embodiments, when the UE initiates the RRC connection recovery procedure for SDT, the UE initializes the first timer for For the RRC connection recovery process of SDT, the first timer can be started. In other embodiments, when the UE initiates the RRC connection recovery process for SDT, the UE sends a message to the base station for initiating the RRC connection recovery process for SDT. When receiving an RRC request message, the first timer may be started. In some embodiments, the condition for starting the first timer includes: initiating an RRC connection recovery procedure for SDT.
  • the condition for starting the first timer includes: sending an RRC request message for initiating an RRC connection recovery procedure for SDT.
  • the above RRC request message is the RRC request message in msg3 or msgA sent by the UE to the base station based on RA-SDT
  • the above RRC request message is an RRC request message sent by the UE to the base station based on CG-SDT.
  • the UE may stop the first timer when receiving the RRC response message or cell reselection occurs.
  • the condition for stopping the first timer may include receiving the RRC response message Or cell reselection occurs, wherein the above-mentioned RRC response message is, for example, RRCResume message, RRCSetup message, RRCRelease message, RRCRelease with suspend indication message, RRC rejection (RRCReject) message or other 3rd generation partnership project (3rd generation partnership) with the same function project, 3GPP) unstandardized RRC message, where the UE receives the RRCRelease message, RRCRelease with suspend indication message or other RRC messages with the same function but not standardized by 3GPP, the UE can consider this SDT successful and stop the first timer.
  • the UE When the UE receives the RRCResume message, RRCSetup message or other RRC messages with the same function but not standardized by 3GPP, the UE can consider the SDT successful and stop the first timer, or the UE can consider the SDT successful and transfer to Continue data transmission after the RRC CONNECTED state, and stop the first timer.
  • the UE receives the RRCReject message or other RRC messages with the same function but not standardized by 3GPP, the UE may consider that the SDT fails this time, and stop the first timer.
  • the UE may consider that the SDT fails and automatically end the SDT. Understandably, the first timer can avoid the situation that the base station does not respond to the UE for a long time after the UE sends a request message or data to the base station.
  • contention resolution contention resolution
  • RRC response message RRC response message
  • FIG. 5 exemplarily shows a schematic flowchart of a 4-step SDT process under the user plane.
  • the process shown in Figure 5 may include but not limited to the following steps:
  • S111 The UE sends a random access preamble to the base station.
  • the base station may send a broadcast message to the UE, where the broadcast message includes first resource configuration information, and the first resource configuration information is used to indicate the random access resource for sending the random access preamble.
  • the first resource configuration information may specifically indicate the first random access resource used to initiate normal random access.
  • the first resource configuration information may specifically indicate the first random access resource used to send random access resources during the RA-SDT process.
  • the second random access resource of the preamble may be generated by the UE according to specific rules, but the base station can recognize the random access preamble generated by the UE.
  • the random access preamble for the UE to send RA-SDT may be different from the random access preamble for the UE to initiate normal RA without performing RA-SDT. That is to say, the base station can use different random access preambles to distinguish the intention of the UE, for example, the intention of the UE is to perform RA-SDT or to initiate RA.
  • the random access preamble for the UE to send RA-SDT may also be the same as the random access preamble for the UE to initiate normal RA without performing RA-SDT.
  • the UE can send the random access preamble on different random access resources based on different intentions, so that the base station can use different resources for receiving the random access preamble to distinguish the intention of the UE. For example, when the UE intends to initiate RA, it sends a random access preamble on the first random access resource, and when the base station receives the random access preamble through the first random access resource, it can determine that the UE intends to initiate RA.
  • the UE When the UE intends to perform RA-SDT, it sends a random access preamble on the second random access resource, and when the base station passes the second random access resource random access preamble, it can determine that the UE intends to perform RA-SDT.
  • the random access resource for the UE to perform RA-SDT to send the random access preamble may also be the same as the random access resource for the UE to initiate normal RA without performing RA-SDT.
  • the base station In response to the random access preamble, the base station sends a random access response (random access response, RAR) to the UE.
  • RAR random access response
  • the UE may monitor a physical downlink control channel (physical downlink control channel, PDCCH) within the RAR time window to receive the RAR sent by the base station. If the UE does not receive the RAR sent by the base station within the RAR time window, the UE may determine that the RA fails this time.
  • the RAR is used to schedule uplink resources (uplink grant, UL grant) for the UE, so that the UE can send msg3 (including the RRC request message in S113 ) on the resources scheduled by the RAR.
  • the RAR may further include at least one of a temporary cell radio network temporary identifier (temporary cell radio network temporary identifier, TC-RNTI) and a timing advance (timing advance, TA).
  • TA is used for UE to learn uplink synchronization.
  • the UE sends the uplink small packet data and the RRC request message to the base station on the resources allocated by the RAR.
  • the RRC request message may carry intent information
  • the intent information is used to indicate the intention of the UE to send the RRC request message, for example, the intention of the UE is to perform RA-SDT or to initiate RA.
  • the random access preamble sent by the UE to initiate RA-SDT is the same as the random access preamble for the UE to initiate normal RA without performing RA-SDT, or the random access resource used by the UE to initiate RA-SDT to send the random access preamble is the same as
  • the random access resources are the same.
  • the RRC request message sent by the UE to perform RA-SDT can carry intent information.
  • the intent information is used to indicate that the UE wants to initiate RA. - the intent of the SDT, not the intent to initiate a normal RA.
  • the UE may send a BSR when sending msg3 to the base station, and the base station may obtain the intention of the UE through the BSR sent by the UE, for example, the intention of the UE is to perform RA-SDT or to initiate RA.
  • the random access preamble for the UE to send RA-SDT is the same as the random access preamble for the UE to initiate normal RA without performing RA-SDT
  • the random access resource for the UE to send the random access preamble for RA-SDT can also be It is the same as the random access resource for UE to initiate normal RA without RA-SDT.
  • UE wants to perform RA-SDT, it can send BSR when sending msg3 to the base station.
  • the BSR is used to indicate the data volume of small packet data.
  • the base station can The intention of the UE obtained through the received BSR is to initiate RA-SDT instead of normal RA.
  • the RRC request message in msg3 may be different when the UE is in different RRC states and in different service scenarios.
  • the RRC request message sent by the UE in the RRC IDLE state (optionally, at this time, the UE may store UE contexts such as configuration information for obtaining the key for encrypting the above-mentioned uplink packet data, or the terminal may not store its context) It may include RRC Connection Request (RRCConnectionRequest) message, RRC Connection Resume Request (RRCConnectionResumeRequest) message, RRC Data Early Data Request (RRCEearlyDataRequest) message, RRCResumeRequest message, RRCResumeRequest1 message, RRCSetupRequest message or other RRC messages that have the same function but are not standardized by 3GPP.
  • the RRC request message sent by the UE in the RRC INACTIVE state can be RRCConnectionRequest message, RRCConnectionResumeRequest message, RRCEearlyDataRequest message, RRCResumeRequest message, RRCResumeRequest1 message, RRCSetupRequest message or other RRC messages with the same function but not standardized by 3GPP.
  • the UE may send uplink packet data and an RRC request message to the base station to initiate the RRC connection recovery process for 4-step SDT, in some embodiments, for initiating RRC for 4-step SDT
  • the RRC request message of the connection recovery process includes an information element (information element, IE) of a resumeCause (resumeCause), and the resumeCause IE can be set to mo-data.
  • the UE first initiates the RRC connection recovery procedure for SDT, and then sends an RRC request message to the base station based on 4-step SDT.
  • the first timer is started.
  • the timer is started. First timer.
  • msg3 may include the identifier of the UE, for example, the unique identifier of the UE at the core network. In some embodiments, msg3 may include information about a connected base station on the UE, such as an inactive temporary cell radio network temporary identifier (I-RNTI). In some embodiments, msg3 may include information for encryption and integrity protection.
  • I-RNTI inactive temporary cell radio network temporary identifier
  • the above-mentioned uplink packet data can be transmitted on the DTCH, and the above-mentioned RRC message can be transmitted on the CCCH.
  • the MAC layer can encapsulate the small packet data and the RRC request message, and send it to the base station through the PHY layer.
  • the base station After receiving the RRC request message, the base station sends a contention resolution message to the UE.
  • the base station after receiving the uplink small packet data and the RRC request message, the base station can restore the UE context, and send the received uplink small packet data to the core network.
  • the contention resolution message is actually a contention resolution identity media access layer control element (contention resolution Identity MAC control element, contention resolution Identity MAC control element, contention resolution Identity MAC CE), and the contention resolution Identity MAC CE may indicate that the UE contention resolution is successful.
  • the UE can determine whether the contention resolution Identity MAC CE is consistent with the msg3 sent by S113, and if they are consistent, determine that the contention resolution corresponding to the current RA-SDT process is successful, or determine that the current RA-SDT process is successful.
  • S115 The base station sends an RRC response message to the UE.
  • the core network may send the downlink small packet data to the base station. Then, the base station can send the downlink packet data to the UE when sending the RRC response message.
  • the downlink packet data can be transmitted on the DTCH, and multiplexed with the RRC response message transmitted on the DCCH at the MAC layer.
  • the UE may determine whether the uplink packet data is successfully transmitted according to the RRC response message, and a specific example is as follows:
  • the RRC response message sent by the base station is an RRC Connection Release (RRCConnectionRelease) message, an RRC Connection Resume (RRCConnectionResume) message, an RRC Connection Setup (RRCConnectionSetup) message, an RRCRelease message, an RRCResume message, or an RRCSetup message, or other messages that have the same function but are not included in 3GPP. Standardized RRC messages.
  • the RRC response message sent by the base station is an RRC Connection Reject (RRCConnectionReject) message, an RRCReject message or other RRC messages that have the same function but are not standardized by 3GPP.
  • RRCConnectionReject RRC Connection Reject
  • RRCReject message RRCReject message
  • the UE may remain in the current RRC state or enter another RRC state according to the RRC response message, and specific examples are as follows:
  • the RRC response message sent by the base station is RRC Early Data Complete (RRCEearlyDataComplete) message, RRCConnectionRelease message, RRCRelease with suspend config message, RRCRelease message or other messages with the same function but not standardized by 3GPP RRC message.
  • the UE may consider that the SDT transmission process is successful, and stop the first timer.
  • the UE may remain in the current non-RRC connected state in response to the above RRC response message.
  • the above RRC response message (such as RRCRelease message) may include the next hop chaining count (NCC) of UE encrypted packet data when UE initiates SDT next time.
  • NCC next hop chaining count
  • Example 2 If the core network has a need for further data transmission, the core network can trigger the connection establishment indication process, and the above RRC response message sent by the base station is RRCConnectionSetup message, RRCConnectionResume message, RRCSetup message, RRCResume message or other with the same function but not 3GPP Standardized RRC messages.
  • the UE receives the above RRC response message, it may consider that the SDT transmission process is successful, and stop the first timer. In addition, the UE may enter the RRC CONNECTED state in response to the above RRC response message.
  • the UE if the UE does not receive the RRC response message in S115, it is considered that the transmission of the small packet data in S113 has failed, for example, the first timer expires, and the UE has not received the RRC response message, it is considered that the small packet data in S113 Transfer failed. If the UE receives the RRC response message in S115, it considers that the small packet data transmission in S113 is successful. That is to say, the UE can determine whether the small packet data in S113 is successfully transmitted by using whether the RRC response message is received.
  • FIG. 6 exemplarily shows a schematic flowchart of a 4-step SDT process under the control plane.
  • the process shown in Figure 6 may include but not limited to the following steps:
  • S121 The UE sends a random access preamble to the base station.
  • the base station In response to the random access preamble, the base station sends a RAR to the UE.
  • S121-S122 are similar to S111-S112 in FIG. 5 and will not be repeated here.
  • the UE sends an RRC request message carrying uplink small packet data to the base station on the resources allocated by the RAR.
  • S123 is similar to S113 in FIG. 5 , the difference is that the uplink small packet data is not sent after being encapsulated with msg3 at the MAC layer, but carried in msg3 and sent.
  • the above-mentioned uplink small packet data can carry In msg3 and transmitted on CCCH.
  • the above-mentioned uplink packet data can be carried in the NAS layer-related IE (such as dedicated information NAS (dedicatedInfoNAS) IE) included in the RRCEearlyDataRequest message, and transmitted on the CCCH.
  • the NAS layer-related IE such as dedicated information NAS (dedicatedInfoNAS) IE
  • the base station After receiving the RRC request message, the base station sends a contention resolution message to the UE.
  • S124 is similar to S114 in FIG. 5, except that the RRC request message received by the base station includes uplink packet data, and in some embodiments, the base station may send the above-mentioned uplink packet data to the core network through the above-mentioned msg3 carrying the uplink packet data .
  • the base station may send the above-mentioned uplink packet data to the core network by forwarding the IE related to the NAS layer included in the above-mentioned msg3.
  • S125 The base station sends an RRC response message to the UE.
  • S125 is similar to S115 in FIG. 5 , and will not be repeated here.
  • FIG. 5 and FIG. 6 illustrate by taking the UE to execute S111 and/or S121 when there is uplink small packet data sent to the base station, that is, the UE actively initiates the transmission process of small packet data.
  • the UE passively initiates the transmission process of the small packet data under the instruction of the base station, for example, the terminal terminated (mobile terminated, MT) EDT (abbreviated as MT-EDT) in LTE.
  • MT mobile terminated
  • MT-EDT mobile terminated
  • the transmission process in this case is similar to the transmission process shown in Figure 5 and Figure 6, and the differences are as follows:
  • the core network may send a paging message to the base station.
  • the paging message may carry data volume information of the downlink small packet data.
  • the base station can send a paging message to the UE, and the UE determines to initiate a 4-step SDT based on the relative size of the currently measured RSRP and the preset RSRP threshold.
  • the base station can trigger MT-EDT, and send a paging message carrying an MT-EDT indication to the UE, so that the UE triggers MO-EDT for MT-EDT.
  • the difference from the above UE initiatively initiating the transmission process of small packet data is that in S113, the UE may only send the RRC message to the base station without sending the uplink small packet data, and optionally, may also carry the reason information for triggering MT-EDT.
  • the base station may receive the downlink packet data sent by the core network, and in S115 the base station may send the RRC response message and the downlink packet data to the UE.
  • the core network may send a paging message to the base station.
  • the paging message may carry data volume information of the downlink small packet data.
  • the base station may send a paging message to the UE, and the UE determines to initiate a 4-step SDT based on the relative size of the currently measured RSRP and the preset RSRP threshold, wherein the transmission process of small packet data is actively initiated with the above UE.
  • the base station can receive the downlink packet data sent by the core network.
  • the RRC response message sent by the base station to the UE may carry downlink packet data.
  • FIG. 7 exemplarily shows a schematic flowchart of a 2-step SDT process on the user plane.
  • the process shown in Figure 7 may include but not limited to the following steps:
  • S211 UE sends random access preamble, RRC request message and uplink packet data to the base station.
  • the transmission resource for the UE to perform S211 can be obtained through information broadcast by the base station.
  • the UE can use the RA resource broadcast by the base station to send a random access preamble, and the UE can use the PUSCH resource broadcast by the base station to send an RRC request message.
  • the base station can use different random access preamble to distinguish the intention of the UE. In other embodiments, the base station can use different resources for receiving the random access preamble to distinguish the intention of the UE. In other embodiments, The base station can obtain the intention of the UE through the BSR sent by the UE. In other embodiments, the RRC request message can carry intention information, and the intention information is used to indicate the intention of the UE to send the RRC request message. For example, the intention of the UE is to perform For RA-SDT or for initiating RA, refer to the examples of S111 and S113 in Figure 5 above for details, and details will not be repeated here.
  • the above RRC request message in msgA may be different.
  • the above RRC request message in msgA may be different.
  • the above-mentioned RRC request message and uplink packet data may be carried in a physical uplink shared channel (physical uplink share channel, PUSCH) payload.
  • the above-mentioned uplink packet data can be transmitted on the DTCH, and the above-mentioned RRC message can be transmitted on the CCCH.
  • the MAC layer can encapsulate the small packet data and the RRC request message, and send it to the base station through the PHY layer.
  • the UE may send uplink packet data and an RRC request message to the base station to initiate the RRC connection recovery process for 2-step SDT, in some embodiments, for initiating RRC for 2-step SDT
  • the resumeCause IE can be set to mo-data.
  • the UE first initiates the RRC connection recovery procedure for SDT, and then sends an RRC request message to the base station based on 2-step SDT.
  • the first timer is started.
  • the timer is started. First timer.
  • the base station After receiving the RRC request message, the base station sends a message B to the UE.
  • the base station after receiving the uplink small packet data and the RRC request message, the base station can restore the UE context, and send the received uplink small packet data to the core network.
  • the message sent by the base station to the UE in the second step of the 2-step RA may be called message B (message B), msgB for short.
  • message B messages B
  • msgB includes success RAR (successRAR) or fallback RAR (fallbackRAR).
  • msgB includes successRAR
  • successRAR includes a contention resolution field, such as the content included in contention resolution MAC CE
  • the UE receives successRAR, then determines that the contention resolution corresponding to the current RA-SDT process is successful, or determines the current RA-SDT process success.
  • the contention resolution field in successRAR may indicate that the UE contention resolution is successful.
  • the UE may determine whether the contention resolution field in successRAR is consistent with the msgA sent by S211, and if they are consistent, determine the contention resolution field corresponding to the current RA-SDT process. The solution is successful, or the current RA-SDT process is determined to be successful.
  • msgB includes fallbackRAR, and after receiving the fallbackRAR, the UE sends msg3 and the uplink packet data to the base station again.
  • the base station sends an RRC response message to the UE.
  • the core network may send the downlink small packet data to the base station. Then, the base station can send the downlink packet data to the UE when sending the RRC response message.
  • FIG. 8 exemplarily shows a schematic flowchart of a 2-step SDT process under the control plane.
  • the process shown in Figure 8 may include but not limited to the following steps:
  • S221 The UE sends a random access preamble and an RRC request message carrying uplink packet data to the base station.
  • S221 is similar to S211 in FIG. 7, the difference is that the uplink small packet data is not sent together with the RRC request message in msgA, but is sent in the RRC request message in msgA.
  • carrying The RRC request message of the uplink packet data can be carried in the physical uplink shared channel (physical uplink share channel, PUSCH) load, and can be transmitted on the CCCH.
  • PUSCH physical uplink share channel
  • the base station After receiving the RRC request message, the base station sends msgB to the UE.
  • S222 is similar to S212 in FIG. 7, except that the RRC request message received by the base station includes uplink packet data.
  • the base station may send the above-mentioned uplink request message to the core network through the above-mentioned RRC request message carrying the uplink packet data.
  • Small packets of data For example, the base station may send the above-mentioned uplink small packet data to the core network by forwarding the RRCResumeRequest message carrying the uplink small packet data.
  • the base station sends an RRC response message to the UE.
  • S223 is similar to S213 in FIG. 7 , and will not be repeated here.
  • FIG. 7 and FIG. 8 illustrate by taking the UE as an example to perform S211 and/or S221 when there is uplink small packet data to be sent to the base station, that is, the UE actively initiates the transmission process of small packet data.
  • the UE passively initiates the transmission process of the small packet data under the instruction of the base station.
  • the transmission process in this case is similar to the transmission process shown in Figure 7 and Figure 8, and the differences are as follows:
  • the core network may send a paging message to the base station.
  • the paging message may carry data volume information of the downlink small packet data.
  • the base station can send a paging message to the UE, and the UE determines to initiate a 2-step SDT based on the relative size of the currently measured RSRP and the preset RSRP threshold.
  • the base station can trigger MT-EDT, and send a paging message carrying an MT-EDT indication to the UE, so that the UE triggers MO-EDT for MT-EDT.
  • the difference from the above UE initiating the transmission process of small packet data is that in S211, the UE can only send random access preamble and RRC request message to the base station, and does not send uplink small packet data.
  • the base station may receive the downlink packet data sent by the core network, and in S213 the base station may send the RRC response message and the downlink packet data to the UE.
  • the core network may send a paging message to the base station.
  • the paging message may carry data volume information of the downlink small packet data.
  • the base station may send a paging message to the UE, and the UE determines to initiate a 2-step SDT based on the relative size of the currently measured RSRP and the preset RSRP threshold, wherein the transmission process of small packet data is actively initiated with the above UE The difference is: the RRC message sent by the UE to the base station in S221 may not carry the uplink small packet data, and optionally, may also carry the reason information for triggering the MT-EDT.
  • the base station can receive the downlink packet data sent by the core network.
  • the RRC response message sent by the base station to the UE may carry downlink packet data.
  • the base station may also send the msgB and the RRC response message to the UE together.
  • the base station executes before sending the RRC response message to the UE, such as between S114 and S115 in Figure 5 above, and between S212 and S213 in Figure 7 above.
  • RRC response message such as between S114 and S115 in Figure 5 above, and between S212 and S213 in Figure 7 above.
  • Example 1 The RA-SDT currently initiated by the UE is used to transmit a small data (such as an instant messaging message).
  • a small data such as an instant messaging message.
  • the UE initiates a 4-step SDT the UL grant indicated by the base station in the RAR is smaller than the UL grant for transmitting small data and RRC request messages.
  • the sum of resources, or when the UE initiates 2-step SDT the transmission resources obtained by the UE from the broadcast message are less than the sum of the resources for transmitting random access preamble, small data and RRC request messages.
  • the UE can first send part of the small data through msg3 or msgA, and then transmit the remaining data of the small data through subsequent transmission.
  • the base station can dynamically schedule uplink resources for the UE after sending the contention resolution to the UE. Carry out subsequent transmission.
  • Example 2 The RA-SDT currently initiated by the UE is used to transmit multiple small data.
  • the UE can initiate a 4-step SDT or 2-step SDT to transmit small data through msg3 or msgA, but in this SDT During the process, the UE acquires new small data, and the UE can transmit the new small data through subsequent transmission.
  • the base station can dynamically schedule uplink resources for the UE to perform subsequent transmission after sending contention resolution to the UE.
  • FIG. 9 exemplarily shows a flow chart of a CG-SDT process in the user plane.
  • the process shown in Figure 9 may include but not limited to the following steps:
  • S311 The UE sends an RRC request message and uplink packet data to the base station on pre-configured resources.
  • the pre-configured resources are configured grants type 1 (configured grants type 1, CG Type 1) or PUR.
  • CG Type 1 may be an uplink resource directly configured by the RRC layer, which may include but not limited to the time-frequency resource location and resource period of the uplink resource.
  • the UE may perform S311 without performing RA.
  • Conditions for using CG-SDT include, for example: the UE is in a non-RRC connection state, the UE has a need for uplink packet data transmission, the UE has pre-configured resources, meets RSRP conditions, and has a valid TA.
  • the conditions for the UE to determine to use CG-SDT include at least one of the following:
  • Condition 1 The TAT is running, that is, the TA of the UE is valid, and the UE and the base station are in an uplink synchronization state, which can indicate that the CG-SDT is valid, otherwise it is invalid.
  • the current RSRP of the UE is greater than the preset first RSRP threshold (referred to as RSRP 1), which can indicate that the CG-SDT is valid.
  • the RSRP1 may be an RSRP for which the UE can initiate SDT transmission. That is to say, if the current RSRP of the UE is greater than the preset RSRP 1, it means that the UE is closer to the base station and the channel quality is better. If CG-SDT is performed, the success rate is higher and CG-SDT is effective. If the UE's current RSRP is less than or equal to the preset RSRP 1, it means that the UE is far away from the base station and the channel quality is poor. If CG-SDT is performed, the success rate is low.
  • RSRP 1 can be configured by the base station for both CG-SDT and RA-SDT.
  • Condition 3 During the preset time period when the last TA was valid, the increase or decrease of the UE's RSRP is less than or equal to the preset second RSRP threshold (referred to as RSRP 2), which can indicate that the CG-SDT is valid. That is to say, it can be determined whether the UE has moved according to the increase or decrease of the UE's RSRP. If the increase or decrease of the RSRP is greater than or equal to RSRP 2, it means that the UE has moved within the valid period relative to the last TA. Or if the moving distance is large, if CG-SDT is performed, the success rate is low and CG-SDT is invalid.
  • RSRP 2 preset second RSRP threshold
  • Condition 4 If the base station configures CG-SDT on the SUL and/or NUL, the UE needs to compare the current RSRP with the third RSRP threshold preset by the base station (RSRP 3 for short), so as to determine whether the CG-SDT configured on the SUL is valid or not. CG-SDT configured on NUL is valid.
  • the UE compares the current RSRP with RSRP 3, and if the current RSRP is less than RSRP 3, selects CG-SDT on SUL; if the current RSRP is greater than or equal to RSRP 3 chooses CG-SDT on NUL.
  • the base station when the base station is configured with CG-SDT on both SUL and NUL, if the current RSRP of the UE is less than RSRP 3, it means that the UE is far away from the base station, and CG-SDT configured on SUL should be used, that is, SUL The CG-SDT on the NUL is valid, and the CG-SDT on the NUL is invalid. If the current RSRP of the UE is greater than or equal to RSRP 3, it means that the UE is close to the base station, and the CG-SDT configured on the NUL should be used, that is, the CG-SDT on the NUL is valid, and the CG-SDT on the SUL is invalid.
  • the UE compares the current RSRP with RSRP 3, and if the current RSRP is less than RSRP 3, then selects the CG-SDT on the SUL. At this time, the CG-SDT is valid, if If the current RSRP is greater than or equal to RSRP 3, CG-SDT cannot be used, that is, CG-SDT on SUL is invalid, that is to say, the base station is configured with CG-SDT on SUL, and when the UE is far away from the base station, SUL can be used. CG-SDT on SUL, otherwise CG-SDT on SUL is invalid.
  • the UE compares the current RSRP with RSRP 3. If the current RSRP is less than RSRP 3, CG SDT cannot be used. If the current RSRP is greater than or equal to RSRP 3, select CGSDT on NUL, that is, CG-SDT on NUL is valid, that is to say, the base station is configured with CG-SDT on NUL. When the UE is relatively close to the base station, it can use CG-SDT on NUL. CG-SDT is invalid.
  • Condition five the UE is in the range covered by the base station, and the base station has configured CG resources for CG-SDT for the UE.
  • the UE may also request the base station to configure pre-configured resources for initiating CG-SDT. For example, the UE sends a CG-SDT resource request message to the base station in the RRC CONNECTED state.
  • the CG-SDT resource request message is used to request the base station to configure the CG-SDT.
  • the UE sends a PUR request configuration information (PURConfigurationRequest) message to the base station.
  • PUR request configuration information PUR request configuration information
  • the UE can send a CG-SDT resource request message to the base station at any time in the RRC CONNECTED state.
  • the UE in the RRC CONNECTED state, the UE can determine that there may be small packets of data in the future, and then it can send a CG-SDT resource request message to the base station.
  • the UE is in the RRC CONNECTED state, and the UE has no need to transmit data with the base station within a preset period of time. The UE determines that it may soon enter the non-RRC connected state. In order to transmit small packet data in the non-RRC connected state, the UE can Send a CG-SDT resource request message to the base station.
  • the base station after the base station receives the request configuration information (such as a CG-SDT resource request message or a PURConfigurationRequest message), when the base station instructs the UE to switch from the RRC CONNECTED state to a non-RRC connected state, the base station sends the RRC response message to the UE It may carry detailed CG-SDT configuration information.
  • the base station instructs the UE to switch from the RRC CONNECTED state to the RRC INACTIVE state
  • the above RRC response message is an RRCRelease message
  • the RRCRelease message may carry detailed CG resource configuration information.
  • the above RRC response message is an RRCRelease message
  • the RRCRelease message may carry detailed PUR configuration information.
  • the base station may send an RRC response message carrying release instruction information to the UE to release the configured CG-SDT.
  • the RRCRelease message may carry CG resource release instruction information.
  • the RRCConnectionRelease message may carry PUR release indication information.
  • the UE may not send a CG-SDT resource request message to the network device, and the network device may directly configure CG-SDT resources for the UE. -SDT resources.
  • the UE may send uplink packet data and an RRC request message to the base station to initiate the RRC connection recovery process for CG-SDT, in some embodiments, for initiating the RRC connection recovery process for CG-SDT
  • the resumeCause IE can be set to mo-data.
  • the UE first initiates the RRC connection recovery procedure for SDT, and then sends the RRC request message to the base station based on CG-SDT.
  • the first timer is started.
  • the first timer is started. a timer.
  • the UE may only send small packet data during the CG-SDT process, for example, the resource indicated by the CG-SDT configuration is a unique resource configured by the network device to the UE , non-shared resources, the UE can only send small packet data in the resources indicated by the CG-SDT configuration during the CG-SDT process. In this way, the network device can identify the UE sending the small packet data according to the resource receiving the small packet data.
  • the UE may send small packet data and RRC request messages on the resources indicated by the CG-SDT configuration during the SDT process, In this way, the network device can use the RRC message to identify the UE.
  • S312 The base station sends a feedback response message to the UE.
  • the base station sends a feedback response message to the UE in response to the RRC request message sent by the UE.
  • the feedback response message is used to indicate that the transmission of the RRC request message is successful.
  • the feedback response message is used to indicate that the transmission of the RRC request message and the uplink packet data sent together with the RRC request message is successful.
  • the feedback response message is used to indicate that the uplink small packet data transmission is successful.
  • the feedback response message is a Layer 1 Acknowledgment message (Layer 1 Acknowledgment, Layer 1 Ack), that is, a physical layer ACK.
  • Layer 1 Acknowledgment Layer 1 Ack
  • the feedback response message is downlink feedback information (DFI), that is, CG-DFI.
  • DFI downlink feedback information
  • the feedback response message is a MAC CE of the MAC layer.
  • the feedback response message is an RRC message of the RRC layer.
  • the base station sends an RRC response message to the UE.
  • the core network may send the downlink small packet data to the base station. Then, the base station can send the downlink packet data to the UE when sending the RRC response message.
  • the RRC response message may include CG-SDT configuration, for example, the CG-SDT configuration in S311 is used for the UE to transmit the small packet data in S311, and the CG-SDT configuration indicated by the RRC response message in S313 is used for UE Transfer small packets of data at a time.
  • the feedback response message in S312 when the feedback response message in S312 is an RRC message of the RRC layer, the feedback response message in S312 and the RRC response message in S313 may be the same message, that is, the above-mentioned feedback response message may be the above-mentioned The RRC response message, that is, S312 and S313 are the same step.
  • FIG. 10 exemplarily shows a flowchart of a CG-SDT process under the control plane.
  • the process shown in Figure 10 may include but not limited to the following steps:
  • S321 The UE sends an RRC request message carrying uplink small packet data to the base station on pre-configured resources.
  • S321 is similar to S311 in FIG. 9 , except that the uplink small packet data is not sent together with the RRC request message, but carried in the RRC request message.
  • the base station sends a feedback response message to the UE.
  • the base station sends an RRC response message to the UE.
  • S322-S323 are similar to S312-S313 in FIG. 9 and will not be repeated here.
  • FIG. 9 and FIG. 10 illustrate by taking the UE as an example to perform S311 and/or S321 when there is uplink small packet data to be sent to the base station, that is, the UE actively initiates the transmission process of small packet data.
  • the UE passively initiates the transmission process of the small packet data under the instruction of the base station.
  • the transmission process in this case is similar to the transmission process shown in Figure 9 and Figure 10, and the differences are as follows:
  • the core network may send a paging message to the base station.
  • the paging message may carry data volume information of the downlink small packet data.
  • the base station may send a paging message to the UE, so that the UE initiates CG-SDT.
  • the difference from the above-mentioned UE initiatively initiating the transmission of small packet data is that in S311, the UE can only send the RRC request message to the base station without sending the uplink small packet data, and optionally, it can also carry the reason information for triggering MT-EDT .
  • the base station may receive the downlink packet data sent by the core network, and in S313 the base station may send the RRC response message and the downlink packet data to the UE.
  • the core network may send a paging message to the base station.
  • the paging message may carry data volume information of the downlink small packet data.
  • the base station may send a paging message to the UE, so that the UE initiates CG-SDT.
  • the difference from the above UE initiating the small packet data transmission process is that the RRC message sent by the UE to the base station in S321 may not carry the uplink small packet data, and optionally, may also carry the reason information for triggering MT-EDT.
  • the base station can receive the downlink packet data sent by the core network.
  • the RRC response message sent by the base station to the UE may carry downlink packet data.
  • the UE in the RRC INACTIVE state is managed by the NG-RAN, and the NG-RAN can obtain the RNA of the UE.
  • a UE in the RRC INACTIVE state can be configured with an RNA by the previous serving base station, where one RNA can cover one or more cells, and this RNA can be included in the registration area of the core network. In some embodiments, there are Xn linkages between base stations within the same RNA.
  • the base station can configure RNA related information for the UE, such as a cell list or a RAN area (RAN area ) list.
  • RNA related information for the UE, such as a cell list or a RAN area (RAN area ) list.
  • Case 1 The base station configures a cell list for the UE.
  • the base station explicitly indicates the cell list to the UE, wherein one or more cells included in the cell list constitute the RNA configured by the base station for the UE.
  • Case 2 The base station configures a RAN area list for the UE.
  • one or more RAN area included in the RAN area list constitutes the RNA configured by the base station for the UE.
  • the base station configures a RAN area identification (identity document, ID) (RAN area ID) for the UE.
  • ID RAN area identification
  • each RAN area is a subset of a core network (core network) tracking area (CN tracking area) or equal to a CN tracking area.
  • core network core network
  • CN tracking area CN tracking area
  • Each RAN area is identified by a RAN area ID, and each RAN area includes a tracking area code (tracking area code, TAC), and the TAC is the tracking area to which the RAN area belongs.
  • TAC tracking area code
  • each RAN area may include a RAN area code (RAN area code), and the RAN area code may be used to identify an area within the tracking area range of the RAN area.
  • each cell and corresponding base station may broadcast one or more RAN area IDs in system information.
  • the UE in the RRC INACTIVE state can trigger RNA update (RNA update, RNAU).
  • RNA update RNA update
  • the UE can trigger RNAU after the RNA is configured to notify the network device of the current RNA state of the terminal, such as the current state of the terminal.
  • RNA whether it is in the RNA configured by the base station for the UE, the cell where the UE is currently located, and other mobility-related states of the UE.
  • Case 1 UE can periodically trigger RNAU, and triggering RNAU can be controlled by a second timer, for example, the second timer is T380 specified in 38.321 of the 3GPP protocol, and T380 is used to trigger RNAU when timeout occurs.
  • the base station configures the second timer for the UE when sending the first RRC response message to the UE.
  • the UE starts the second timer.
  • the start condition of the second timer includes that the UE receives the first RRC response message.
  • the first RRC response message is, for example, an RRC Release message , RRC release with suspend configuration (RRCRelease with suspend config) message or other RRC messages with the same function but not standardized by 3GPP.
  • the UE when the second timer expires, the UE triggers RNAU.
  • the UE when the UE receives the second RRC response message sent by the base station, the UE stops the second timer.
  • the stop condition of the second timer includes that the UE receives the second RRC response message.
  • the second RRC response message is, for example, an RRCResume message, an RRCSetup message or an RRCRelease message or other RRC messages that have the same function but are not standardized by 3GPP.
  • RNAU is triggered by a system information block (SIB) 1, and the triggered RNAU is related to the RNA configured by the base station for the UE.
  • SIB system information block
  • the UE may trigger RNAU, for example, when the serving cell of the UE after cell reselection does not belong to the configured RNA, the UE may trigger RNAU, for example, the terminal moves , cell reselection occurs.
  • the UE after the UE reads SIB1 in the serving cell (such as a new serving cell after cell reselection), if the cell provided by SIB1 does not belong to the cell list configured by the base station for the UE, or the RAN area provided by SIB1 does not belong to The RAN area list configured by the base station for the UE, and the UE can trigger RNAU.
  • the UE may trigger RNAU when the cell identity read by the UE from SIB1 does not belong to the cell identity included in the cell list configured by the base station for the UE in the RAN-NotificationAreaInfo IE.
  • the TAC of the cell read by the UE from SIB1 does not belong to the TAC included in the RAN area list configured by the base station for the UE in the RAN-NotificationAreaInfo IE, and the UE can trigger RNAU.
  • the UE when the UE triggers the RNAU, it may initiate the RRC connection recovery process for the RNAU.
  • the UE initiates the RRC connection recovery process for the RNAU may include: the RRC layer of the UE initiates a request for recovery The process of the suspended RRC connection (requests the resume of a suspended RRC connection).
  • the UE initiates the RRC connection recovery process for RNAU may include: the UE sends an RRC request message to the base station, such as RRCResumeRequest message or RRCResumeRequest1 and other RRC recovery request messages, wherein the resumeCause IE in the RRC request message can be set to rna-Update.
  • the UE initiating the RRC connection recovery process for the RNAU may also include initializing the RRC connection recovery process, which may specifically include: if an emergency service is currently in progress, the UE may select the access category (Access Category) as 2 , and set the resumeCause IE in the RRC request message sent during the RRC connection recovery process to emergency (emergency). If no emergency service is currently in progress, the UE can select Access Category as 8.
  • the Access Category can be used for an access barring check, and each access request can be associated with an Access Category, so that the base station can control the UE's access request.
  • the access request may be an RRC connection recovery request initiated by the UE.
  • the UE selects Access Category. Then, the UE can perform a unified access control (unified access control, UAC) process, and then determine whether the access attempt is prohibited, for example, each access attempt corresponds to an Access Category, for example, the access attempt is for the RRC initiated for RNAU Connection recovery process. At this time, the Access Category is 2 or the Access Category is 8. When the access attempt is prohibited, the UE cannot initiate the RRC connection recovery process for RNAU. When the access attempt is not prohibited, the UE can initiate the RRC connection recovery process for RNAU.
  • UAC unified access control
  • the UE may set the first variable as the first value, and stop the access attempt.
  • the UE may start the timer T390, for example, the UE starts the corresponding timer T390 for the Access Category of the prohibited access attempt.
  • the UE considers that the access attempt is prohibited.
  • the T390 of the access attempt times out for example, the T390 of the access attempt is not running, the UE considers the prohibition of the Access Category to be eased, such as the above Access Category is 2 or Access Category is 8.
  • the value of the first variable is the first value or the second value, for example, the first variable indicates whether there is a pending RNA update (pendingRNA-Update), the first value is true (true), and the second value is false (false ).
  • the value of the first variable may indicate that there is a pending RNA update process.
  • the value of the first variable to the second value may indicate that there is no pending RNA renewal process.
  • the value of the first variable is the first value may indicate that the RNAU has been triggered but failed to execute (it can be understood as the unsuccessful execution of the RRC connection recovery process for the RNAU).
  • the UE may continue to perform initialization related to the RRC connection recovery process, such as applying a default physical layer configuration, a default SRB1 configuration, a default MAC layer configuration, etc., and the UE may set the first variable Set to the second value.
  • the UE can initiate the transmission of the RRC request message, for example, re-store the RRC configuration, rebuild the PDCP entity of SRB1, restore SRB1, and the UE can transmit the RRC request message to the bottom layer of the UE (the bottom layer is relative to the RRC layer, for example MAC layer or physical layer), for example, after the RRC layer of the UE performs the above initialization process, the RRC layer transmits the RRC request message to the MAC layer, and then the MAC layer sends the RRC request message.
  • the UE in the non-RRC connection state does not configure transmission resources.
  • the MAC layer When the MAC layer receives the transmission requirement sent by the RRC layer, it can initiate RA to send the RRC request message for RNAU, for example, in the above msg3 or the above msgA Send the RRC request message in.
  • the UE in the non-RRC connection state has pre-configured resources, such as CG resources or PUR, and the description of the pre-configured resources is similar to the description of the pre-configured resources in FIG. 9-FIG. 10 above.
  • the bottom layer When the bottom layer receives the transmission requirement sent by the upper layer, it can send an RRC request message for RNAU on the pre-configured resources.
  • the bottom layer is the MAC layer
  • the upper layer is the RRC layer.
  • the bottom layer is the physical layer
  • the upper layer is the RRC layer.
  • the above-mentioned bottom layer is the physical layer
  • the above-mentioned upper layer is the MAC layer
  • the MAC layer indicates the transmission demand to the physical layer after receiving the transmission demand sent by the RRC.
  • the resumeCause IE in the above RRC request message for RNAU is set to rna-Update.
  • the base station receives the RRC request message for RNAU sent by the UE, and can obtain that the UE is currently requesting RNAU, so as to know the current state of the UE, such as the mobility situation.
  • the base station successfully receives the RRC request message for RNAU sent by the UE, and the base station may send a third RRC response message to the UE after successful contention resolution (for example, after sending a contention resolution message to the UE), the third RRC
  • the response message is, for example, RRCRelease message, RRCRelease with suspend indication message, RRCResume message or other RRC messages that have the same function but are not standardized by 3GPP.
  • the UE may consider that this RNAU is successful.
  • a specific example is as follows:
  • Example 1 The UE performs RNAU under the current base station (which can be called the new station), but the UE context is stored in the previous base station (which can be called the old station), and the old station can send the UE context to the new station through the Xn interface , the new station can send an RRC response message to the UE after obtaining the context of the UE, such as sending an RRCRelease message to make the UE enter the RRC IDLE state, or sending a RRCRelease with suspend indication message to make the UE enter the RRC INACTIVE state, or sending a RRCResume message to make the UE Enter the RRC CONNECTED state.
  • RRC response message such as sending an RRCRelease message to make the UE enter the RRC IDLE state, or sending a RRCRelease with suspend indication message to make the UE enter the RRC INACTIVE state, or sending a RRCResume message to make the UE Enter the RRC CONNECTED state
  • Example 2 The UE initiates RNAU under the current base station (which can be called a new station), but the context of the UE is stored in the previous base station (which can be called the old station), and the old station has not sent the context of the UE to the new station.
  • the RRC state of the UE is controlled by the old station.
  • the old station can indirectly send the RRC response message to the UE through the Xn interface message, that is, send the RRC response message to the new station, and then the new station forwards the RRC response message.
  • forwarding the RRCRelease message uses The UE enters the RRC IDLE state, or forwards the RRCRelease with suspend indication message to make the UE enter the RRCINACTIVE state.
  • the base station sends the fourth RRC response message to the UE. For example, if the base station fails to receive the RRC request message sent by the UE for RNAU, the base station may send the fourth response to the UE after the contention is successfully resolved. information.
  • the fourth RRC response message is, for example, an RRCConnectionReject message, an RRCReject message or other RRC messages that have the same function but are not standardized by 3GPP.
  • the UE may return to the RRCINACTIVE state after receiving the fourth RRC response message.
  • the UE may consider that the RRC recovery request for the RNAU is rejected, and may set the first variable as the first value.
  • the UE after the UE receives the fourth RRC response message, if the fourth RRC response message is configured with a wait time (wait time), the UE starts the timer T302, wherein the duration of the timer T302 is equal to the wait time.
  • the timer T302 is running and the Access Category is not 2 or 0, the UE considers the access attempt to be prohibited.
  • the timer T302 expires, if T390 of the Access Category is not running, the UE considers that the prohibition of the Access Category is eased. It should be noted that what the timer T302 forbids is the request of the UE, and does not distinguish the Access Category of the UE.
  • the UE currently initiates the RRC connection recovery process for RNAU and selects the Access Category as 8. If the access attempt is not prohibited when initializing the RRC connection recovery process for RNAU, the UE will not open If the Access Category is T390 of 8, the UE can continue to perform initialization related to the RRC connection recovery process and send an RRC request message for the RRC connection recovery process of the RNAU. If the base station sends the fourth RRC response message configured with wait time to the UE, the UE starts the timer T302. When the timer T302 expires, T390 with the Access Category of 8 is not running at this time, and the UE considers that the prohibition with the Access Category of 8 is eased.
  • the UE may continue to execute the RNAU by setting the first variable to the first value when the current RNAU has been triggered but failed to execute.
  • the UE can set the first variable to the first value.
  • the UE may continue to attempt to initiate the RRC connection recovery procedure for the RNAU.
  • the UE can continue to initiate the RRC connection recovery process for the RNAU.
  • RNAU may be triggered.
  • the terminal may stop the current SDT and execute RNAU, thereby affecting the transmission of small data of SDT.
  • Example 1 Before the UE and the base station perform RA SDT, the UE receives the RRCRelease message sent by the base station, starts the second timer (such as T380), and then the UE initiates the RRC connection recovery process for SDT, as shown in Figure 5 and Figure 6 above The 4-step SDT shown above, or the 2-step SDT shown in Figure 7 and Figure 8 above, where the second timer can be started before the UE sends the random access preamble.
  • the second timer such as T380
  • RNAU is triggered before the UE receives the contention resolution message sent by the base station
  • this situation can be understood as the RA currently used for SDT is running During the process, a new RA for RNAU is triggered.
  • whether to perform RNAU depends on the UE implementation, that is, the UE implementation decides to continue the current RA procedure for SDT, or perform a new RA for RNAU.
  • the UE may cause the uplink packet data and the downlink packet data to fail or fail to be sent, for example, the uplink packet data sent together with msg3 or msgA, and the downlink packet data sent together with the RRC response message. If the second timer expires after the UE receives the contention resolution message sent by the base station, that is, the RNAU is triggered after the UE receives the contention resolution message sent by the base station.
  • the UE needs to discard the currently running RA SDT process and initiate the RRC connection recovery process for RNAU, which may cause the uplink packet data and downlink packet data to fail or fail to be sent, such as the uplink packet to be transmitted by subsequent transmission Data and/or downlink small packet data, downlink small packet data sent together with the RRC response message.
  • Example 2 Before the UE and the base station perform CG-SDT, the UE receives the RRCRelease message sent by the base station, starts the second timer (such as T380), and then the UE initiates the RRC connection recovery process for SDT, as shown in Figure 9 and Figure 10 above In the shown CG-SDT, the second timer may be started before the UE sends the RRC request message and/or uplink packet data.
  • the second timer such as T380
  • the UE needs to discard the currently running CG-SDT process and initiate the RRC connection recovery process for RNAU, which may cause the uplink packet data and downlink packet data to fail or fail to be sent, such as the subsequent transmission that needs to be transmitted
  • RNAU RRC connection recovery process
  • the embodiment of the present application provides a method for controlling transmission, which can be applied to a communication system.
  • the communication system includes, for example, a terminal and a network device.
  • RNAU may not be triggered, thereby avoiding the impact on the transmission of small data. , such as increasing the transmission delay, subsequent re-initiation of SDT will also increase power consumption and signaling overhead.
  • the network device can obtain the RNA where the terminal is located, and there is no need to additionally perform RNAU to notify the network device of the current state of the terminal.
  • Example 1 The base station where the terminal initiates SDT this time is the same as the base station that the terminal received the RRCRelease message last time, that is, the terminal is in the same The base station receives the RRCRelease message, and initiates the RRC connection recovery process for SDT.
  • the base station that the terminal received the RRCRelease message last time may be the base station that configures the RNA for the terminal, and the base station can configure the relevant information of the RNA for the terminal through the RRCRelease message, that is, the terminal is configured with RNA under the same base station, and initiates SDT.
  • the base station stores the context of the terminal.
  • the base station can know the RNA where the terminal is located.
  • the base station can know the RNA configured for the terminal based on the saved terminal context.
  • the terminal that initiated the SDT has not moved outside the range of the configured RNA, so the base station can It is known that the RNA where the terminal is located is the RNA configured above.
  • Example 2 The base station where the terminal initiates SDT this time (may be called the new base station) is different from the base station where the terminal received the RRCRelease message last time (can be called the old base station), that is, the terminal initiates RRC connection recovery for SDT under the new base station process.
  • the old base station that the terminal received the RRCRelease message last time may be the base station that configures the RNA for the terminal, and the old base station may configure RNA related information for the terminal through the RRCRelease message.
  • the new base station can learn the RNA where the terminal is located.
  • the new base station can acquire the context of the terminal from the old base station, and the new base station can learn whether the terminal exceeds the configuration configured by the old base station based on the acquired context of the terminal and/or the information of the old base station. within the range of RNA. For example, if the RNA configuration acquired by the new base station from the context of the terminal does not include the RNA list or cell list corresponding to the new base station, it can be known that the terminal has exceeded the RNA range of the above configuration, otherwise it can be known that the terminal has not moved to the RNA range of the above configuration outside.
  • the RNA list corresponding to the new base station does not include the RNA list corresponding to the old base station, or the cell list corresponding to the new base station does not include the cell list corresponding to the old base station, it can be known that the terminal has exceeded the RNA range of the above configuration, otherwise it can be known Terminals did not move outside of the RNA range for the above configuration.
  • This method can be applied to the communication system shown in FIG. 1, and the network device and terminal in this method can be the network device 120 and UE130.
  • the RRC connection recovery process for RNAU when the terminal is in the non-RRC connection state, when the first preset condition is met, the RRC connection recovery process for RNAU is executed.
  • the RRC connection recovery process for RNAU please refer to the above execution The description of initiating the RRC connection recovery process for RNAU in the implementation of RNAU.
  • the first preset condition includes that the second timer expires and the first timer is not running.
  • a specific example is shown in FIG. 11 below, wherein the first preset condition is the first condition in FIG. 11 .
  • the first preset condition includes that the terminal receives SIB1 of the first serving cell, the first serving cell does not belong to the configured RNA, and the first timer is not running.
  • FIG. 13 shows the first A preset condition is the second condition in FIG. 13 .
  • An example of the expression for the above situation is as follows:
  • Example 1 When the terminal is in the RRC INACTIVE state, if the first timer (such as T3XX) is not running and the second timer (such as T380) times out, or if the first timer (such as T3XX) is not running and the serving cell of the terminal is not Belonging to the configured RNA, the terminal can initiate the RRC connection recovery process, and set the resumeCause IE in the RRC request message used to initiate the RRC connection recovery process to rna-Update.
  • the terminal can initiate the RRC connection recovery process, and set the resumeCause IE in the RRC request message used to initiate the RRC connection recovery process to rna-Update.
  • Example 2 When the terminal is in the RRC INACTIVE state, if the second timer (such as T380) times out or the serving cell of the terminal does not belong to the configured RNA, if the first timer (such as T3XX) is not running, the terminal can initiate the RRC connection recovery process , and the resumeCause IE in the RRC request message used to initiate the RRC connection recovery process is set to rna-Update.
  • the second timer such as T380 times out or the serving cell of the terminal does not belong to the configured RNA
  • the first timer such as T3XX
  • performing the RRC connection recovery process for RNAU may include in the above example: initiating the RRC connection recovery process, and setting the resumeCause IE in the RRC request message used to initiate the RRC connection recovery process to rna-Update.
  • FIG. 11 is a schematic flowchart of a method for controlling transmission provided by an embodiment of the present application. The method includes but is not limited to the following steps:
  • S401 The terminal starts a second timer.
  • S401 is an optional step.
  • the terminal receives the first RRC response message and starts the second timer.
  • the first RRC response message includes the second timer.
  • the first RRC response The message includes the duration of the second timer.
  • the first RRC response message is, for example, RRCRelease message, RRCRelease with suspend config message or other RRC messages with the same function but not standardized by 3GPP.
  • the RNAU when the terminal is in the non-RRC connected state, the RNAU is triggered when the first condition is met.
  • the non-RRC connected state is the RRC INACTIVE state.
  • the first condition includes that the terminal is in the RRC INACTIVE state.
  • triggering RNAU is to perform an RRC connection recovery process for RNAU.
  • the terminal may send an RRC request message to the network device, and the RRC request message contains resumeCause IE is rna-Update.
  • the first condition includes that the second timer expires and the first timer is not running, and optionally, the first timer is not running being not started.
  • the terminal may determine whether the first timer is running, if the first timer is running, the terminal does not trigger the RNAU, and if the first timer is not running, the terminal triggers the RNAU.
  • the terminal when the second timer expires, and the terminal has no SDT requirement when the second timer is running, the terminal can trigger RNAU.
  • the fact that the first timer is not running may indicate that the terminal has no SDT requirement.
  • the second timer when the second timer is running, the first timer is not running. The specific example is shown in Figure 12 below.
  • FIG. 12 exemplarily shows a timing diagram.
  • the horizontal axis is the time axis (t).
  • the second timer is started (for example, the first RRC response message is received), and at the second moment t 2 , the second timer times out. , t 1 ⁇ t 2 .
  • the second timer runs between the first moment and the second moment, the first timer does not run between the first moment and the second moment, and the first timer does not start between the first moment and the second moment.
  • the second timer expires and the first timer is not running, at this time, the terminal can trigger the RNAU.
  • the above RRC connection recovery process for SDT may include: initiating the RRC connection recovery process, and setting the resumeCause IE in the RRC request message used to initiate the RRC connection recovery process to mo-data.
  • FIG. 13 is a schematic flowchart of another method for controlling transmission provided by an embodiment of the present application. The method includes but is not limited to the following steps:
  • S501 The terminal starts a first timer.
  • S501 is an optional step.
  • the terminal initiates the RRC connection recovery process for SDT, and starts the first timer.
  • the first timer is started, for example In the process shown in Figure 5-8 above, when the terminal sends msg3 or msgA to the network device based on RA-SDT, the first timer is started.
  • the terminal sends the network device based on CG-SDT
  • the first timer is started.
  • S502 is an optional step.
  • cell reselection occurs.
  • the terminal undergoes cell reselection, and the first timer is stopped.
  • the terminal undergoes cell reselection and switches from the first cell to the second cell, that is, the serving cell after cell reselection of the terminal is the second cell, which is subsequently referred to as the first serving cell.
  • the first serving cell of the terminal does not belong to the configured RNA, where the RNA is configured for the terminal by the network device before the terminal undergoes cell reselection.
  • the terminal receives the SIB1 of the current serving cell, and determines the first serving cell according to the SIB1, and the SIB1 indicates the first serving cell. In some embodiments, the terminal determines the first serving cell according to the SIB1.
  • the serving cell does not belong to the configured RNA.
  • the RNA is configured for the terminal by the network device before the terminal undergoes cell reselection. The specific example is as follows:
  • Example 1 The terminal reads the cell identity of the first serving cell from SIB1. When the read cell identity of the first serving cell does not belong to the cell identity included in the cell list configured for the terminal by the network device in the RAN-NotificationAreaInfo IE, The terminal determines that the first serving cell does not belong to the configured RNA.
  • Example 2 The terminal reads the TAC of the first serving cell from SIB1.
  • the terminal determines The first serving cell does not belong to the configured RNA.
  • the terminal after cell reselection occurs in the terminal, the terminal is in a non-RRC connected state, and optionally, the non-RRC connected state is an RRC INACTIVE state.
  • RNAU when the terminal is in a non-RRC connected state, RNAU is triggered when the second condition is met.
  • the non-RRC connected state is an RRC INACTIVE state.
  • the second condition includes that the terminal is in the RRC INACTIVE state after cell reselection occurs.
  • triggering RNAU is to perform an RRC connection recovery process for RNAU.
  • the terminal may send an RRC request message to the network device, and the RRC request message contains resumeCause IE is rna-Update.
  • the second condition includes that the terminal receives the SIB1 of the first serving cell, the first serving cell does not belong to the configured RNA, and the first timer is not running.
  • the first serving cell is the serving cell after the terminal undergoes cell reselection.
  • the first serving cell is the cell indicated by the SIB1 received after the terminal undergoes cell reselection.
  • the terminal uses the first The SIB1 of the serving cell determines that the first serving cell does not belong to the configured RNA, for a specific example, refer to S502.
  • cell reselection occurs when the terminal has no SDT requirement.
  • the first timer in the second condition is not running means that the first timer is not started.
  • the first timer is not running. There is no SDT requirement for characterizing endpoints.
  • cell reselection occurs during the SDT process of the terminal.
  • the first timer runs during the SDT process of the terminal, and cell reselection occurs when the first timer runs.
  • the second condition If the first timer in the terminal is not running, the first timer is stopped.
  • the terminal undergoes cell reselection the first timer is stopped.
  • the terminal is in the RRC INACTIVE state.
  • the second condition further includes that the terminal cannot perform the SDT process in the first serving cell.
  • the fact that the terminal cannot perform the SDT process in the first serving cell means that the terminal cannot continue the previous SDT process in the first serving cell, for example, after the terminal undergoes cell reselection, it cannot continue the RRC for SDT initiated in S501 Connection recovery process.
  • the fact that the terminal cannot perform the SDT process in the first serving cell means that the terminal cannot initiate a new SDT process in the first serving cell, for example, after the terminal undergoes cell reselection, it cannot be the RRC connection for SDT initiated in S501 The recovery process continues to initiate a new SDT process, or cannot initiate a new SDT process for newly acquired small data.
  • the terminal cannot perform the SDT process in the first serving cell because the terminal does not have SDT-related configuration information in the first serving cell, for example, the first serving cell does not support SDT, and optionally, the first serving cell does not support SDT It includes related configuration that the first serving cell does not broadcast SDT in the system information.
  • the first serving cell does not support RA-SDT and/or CG-SDT.
  • the terminal may determine whether the first timer is running. If the first timer runs, the terminal does not trigger RNAU, and continues to perform SDT.
  • the first timer runs as the first timer continues to run, and the terminal can continue the previous SDT process in the serving cell, for example, the terminal undergoes cell reselection Afterwards, the first timer continues to run, and the terminal can continue the RRC connection recovery process for SDT initiated in S501 in the serving cell.
  • the first timer runs when the first timer is started, and the terminal can initiate a new RRC connection recovery process for SDT in the serving cell, for example, after the terminal reselects a cell, initiate a new RRC connection for SDT To resume the process, start the first timer.
  • the terminal triggers RNAU, optionally, the RNAU is triggered by SIB1.
  • the second timer when the terminal performs the SDT, the second timer times out, and the terminal may determine whether the first timer is running. If the first timer is running, the terminal does not trigger the RNAU, and continues to perform the SDT process. After the second timer expires, cell reselection occurs in the terminal, the first timer is stopped, and the terminal is in the RRC INACTIVE state. When the second condition is met, the terminal may execute the RRC connection recovery process for the RNAU.
  • the terminal is in the RRC IDLE state after cell reselection occurs, and the terminal does not trigger RNAU.
  • the terminal may perform the SDT process in the first serving cell, and the terminal does not trigger the RNAU, but performs the SDT process.
  • the situation that the terminal can perform the SDT process in the first serving cell is opposite to the above-mentioned situation that the terminal cannot perform the SDT process in the first serving cell. For details, refer to the above description.
  • the embodiment of the present application adds a trigger condition: the first timer is not running, that is, the terminal does not have an SDT requirement or the SDT process can be completed.
  • Trigger RNAU when the first timer is running (such as in the process of SDT), RNAU will not be triggered.
  • the network device can obtain the RNA of the terminal. If RNAU is not executed, it will not affect the network device's acquisition of the terminal. state, and can avoid affecting the small packet data transmitted by the SDT process, such as avoiding increasing the transmission delay, and subsequently re-initiating SDT to increase unnecessary signaling overhead and power consumption.
  • the terminal receives the RRC rejection message, if the second timer is not running, the terminal can set the first variable to the first value, and the first variable is the first value indicating that there is a pending RNAU, optional Specifically, the value of the first variable is the first value or the second value, for example, the first variable indicates whether there is a pendingRNA-Update, the first value is true, and the second value is false.
  • the first variable and the first value refer to the description of the first variable and the first value in the implementation manner of executing RNAU above, and a specific example is shown in FIG. 14 below.
  • FIG. 14 is a schematic flowchart of another method for controlling transmission provided by an embodiment of the present application. The method includes but is not limited to the following steps:
  • S601 The terminal starts a second timer.
  • S601 is an optional step, and S601 is similar to S401 in FIG. 11 .
  • S602 The terminal starts a first timer.
  • S602 is an optional step, and S602 is similar to S501 in FIG. 13 .
  • the order of execution of S601 and S602 may be that S601 is executed first, followed by S602, or S602 is executed first, followed by S601.
  • S603 The network device sends an RRCReject message to the terminal.
  • S603 is an optional step.
  • the terminal when the first timer is running, the terminal receives the RRCReject message, and stops the first timer.
  • the terminal receives the RRCReject message and is in the RRC INACTIVE state.
  • the terminal when the terminal initiates an RRC connection recovery process for SDT to the network device, the terminal sends an RRC request message to the network device, and the above RRCReject message is sent by the network device in response to the above RRC request message.
  • the above RRC request message is, for example, an RRC resume request message such as RRCResumeRequest message or RRCResumeRequest1.
  • the terminal receives the RRCReject message and is in a non-RRC connected state.
  • the non-RRC connected state is an RRC INACTIVE state.
  • the terminal receives the RRCReject message and considers that the SDT process has failed (rejected), the terminal is in the RRC INACTIVE state, and the terminal still needs to perform periodic RNAU, but since the second timer is not running at this time, the The terminal may set the first variable to a first value.
  • the terminal may set the first variable to the first value if the terminal is in the RRC INACTIVE state after receiving the RRCReject message, and the second timer is not running.
  • the terminal receives the RRCReject message, and the RRCReject message is configured with a wait time. At this time, the terminal can start the timer T302.
  • the RRC connection recovery process of the UE is prohibited when the timer T302 is running. When the timer T302 expires, the RRC connection recovery process prohibited by the UE is eased.
  • the upper layer such as the NAS layer
  • the UE can initiate the RRC connection recovery process again. For example, the upper layer (such as the NAS layer) If there is no request to resume the RRC connection for data transmission, and the first variable is set to the first value, the UE may continue to initiate the RRC connection recovery procedure for RNAU.
  • the second timer expires, and the terminal can determine whether the first timer is running. If the first timer is running, the terminal does not trigger the RNAU, and continues to perform the SDT process. After the second timer expires, the terminal receives the RRCReject message, stops the first timer, and the terminal is in the RRC INACTIVE state. If the second timer is not running, the terminal may set the first variable as the first value. Optionally, the second timer is not running means not running after the second timer expires.
  • the terminal when the terminal receives the RRCReject message and is in the RRC IDLE state, the terminal does not trigger the RNAU, nor does it set the first variable to the first value.
  • RRC rejection message it is not limited to the RRC rejection message illustrated in FIG. 14 , and in some other embodiments, it may also be an RRCConnectionReject message or other RRC messages that have the same function but are not standardized by 3GPP.
  • the terminal receives the RRC rejection message, if the second timer is not running, the terminal can directly execute the RRC connection recovery process for RNAU, the specific example is similar to Figure 14, the difference In FIG. 14 , setting the first variable to the first value is replaced by performing the RRC connection recovery process for RNAU, for example, the RRC layer of the terminal performs the RRC connection recovery process for RNAU.
  • the terminal receives the RRCReject message, and the RRCReject message does not configure a wait time, and the terminal performs the RRC connection recovery process for RNAU, for example, the RRC layer of the terminal directly performs the RRC connection recovery process for RNAU.
  • the terminal may first set the first variable to the first value, and then the terminal performs the RRC connection recovery process for RNAU, for example, the RRC layer of the terminal directly performs the RRC connection recovery process for RNAU.
  • the terminal receives the RRC reject message, if the second timer is not running, the terminal can start the third timer, when the third timer expires, if the first timer is not running, the terminal performs the RNAU
  • the specific example of the RRC connection recovery process is similar to that in FIG. 14 , except that the first variable in FIG. 14 is set to the first value instead of starting the third timer.
  • the method further includes: when the third timer expires, if the first timer is not running, the terminal executes an RRC connection recovery process for RNAU.
  • the third timer is the same as the second timer, for example, the duration of the third timer is equal to the duration of the second timer.
  • the third timer is T380.
  • the third timer is different from the second timer, for example, the duration of the third timer is not equal to the duration of the second timer.
  • the duration of the third timer is shorter than that of the second timer, for example, the duration of the third timer is in milliseconds or seconds.
  • the terminal may wait for whether the NAS layer has a data transmission requirement, for example, whether the NAS triggers the RRC layer to initiate a connection recovery process. If the NAS layer has a data transmission requirement and triggers the RRC layer to initiate a connection recovery process, the terminal will initiate the RRC connection recovery process for data transmission instead of executing the RRC connection recovery process for RNAU.
  • the above RRC connection recovery process for data transmission Recovery procedures include RRC connection recovery procedures for SDT and for non-SDT.
  • the terminal may set the first variable to the first value, where The terminal can request the above recovery by sending the RRCResumeRequest message or the RRCResumeRequest1 message.
  • the above recovery is an RRC connection recovery process for SDT.
  • the terminal may set the first variable to the first value, and the first variable being the first value indicates that there is a pending RNAU.
  • the first variable and the first value refer to the description of the first variable and the first value in the implementation manner of executing RNAU above, and a specific example is shown in FIG. 15 below.
  • FIG. 15 is a schematic flowchart of another method for controlling transmission provided by an embodiment of the present application. The method includes but is not limited to the following steps:
  • S701 The terminal starts a second timer.
  • S701 is an optional step, and S701 is similar to S401 in FIG. 11 .
  • S702 The terminal starts a first timer.
  • S702 is an optional step, and S702 is similar to S501 in FIG. 13 .
  • the execution order of S701 and S702 may be that S701 is executed first, followed by S702, or S702 is executed first, followed by S701.
  • the terminal after the first timer expires, the terminal is in a non-RRC connected state.
  • the non-RRC connected state is an RRC INACTIVE state.
  • the terminal when the terminal is in an RRC INACTIVE state, the terminal sends a message to the network device Initiate an RRC connection recovery process for SDT, and start a first timer. After the first timer expires, the terminal is still in the RRC INACTIVE state.
  • the terminal expires, the terminal is in the RRC INACTIVE state, and the terminal still needs to perform periodic RNAU, but since the second timer is not running at this time, the terminal can set the first variable to the first value .
  • the terminal sets the first variable to the first value if the terminal is in the RRC INACTIVE state after the first timer expires, and the second timer is not running.
  • the second timer expires, and the terminal may determine whether the first timer is running. If the first timer is running, the terminal does not trigger the RNAU, and continues to perform the SDT process. After the second timer expires, if the first timer expires, the terminal is in the RRC INACTIVE state. If the second timer is not running, the terminal may set the first variable as the first value. Optionally, the second timer is not running means not running after the second timer expires.
  • the terminal when the first timer expires and the terminal is in the RRC IDLE state, the terminal does not trigger the RNAU, and does not set the first variable to the first value.
  • the terminal when the first timer expires, if the second timer is not running, the terminal can directly execute the RRC connection recovery process for RNAU, the specific example is similar to that in FIG. 15, The difference is that setting the first variable to the first value in FIG. 15 is replaced by performing the RRC connection recovery process for RNAU, for example, the RRC layer of the terminal performs the RRC connection recovery process for RNAU.
  • the terminal may first set the first variable to the first value, and then the terminal performs the RRC connection recovery process for RNAU, for example, the RRC layer of the terminal directly performs the RRC connection recovery process for RNAU.
  • the terminal when the first timer expires, if the second timer is not running, the terminal can start the third timer, and when the third timer expires, if the first timer is not running, the terminal performs the RNAU
  • the specific example of the RRC connection recovery process is similar to that in FIG. 15, except that in FIG. 15, setting the first variable to the first value is replaced by starting the third timer.
  • the method further includes: when the third timer expires, if the first timer is not running, the terminal executes an RRC connection recovery process for RNAU.
  • the third timer is the same as the second timer, for example, the duration of the third timer is equal to the duration of the second timer.
  • the third timer is T380.
  • the third timer is different from the second timer, for example, the duration of the third timer is not equal to the duration of the second timer.
  • the duration of the third timer is shorter than that of the second timer, for example, the duration of the third timer is in milliseconds or seconds.
  • the terminal may wait for whether the NAS layer has a data transmission requirement, for example, whether the NAS triggers the RRC layer to initiate a connection recovery process. If the NAS layer has a data transmission requirement and triggers the RRC layer to initiate a connection recovery process, the terminal will initiate the RRC connection recovery process for data transmission instead of executing the RRC connection recovery process for RNAU.
  • the above RRC connection recovery process for data transmission Recovery procedures include RRC connection recovery procedures for SDT and for non-SDT.
  • the terminal when receiving the SIB1 of the second serving cell, if the second serving cell belongs to the configured RNA and the second timer is not running, the terminal may set the first variable to the first value,
  • the first variable is the first value indicating that there is a pending RNAU.
  • the terminal may set the first variable to the first value,
  • the first variable is the first value indicating that there is a pending RNAU.
  • the description of the first variable and the first value please refer to the description of the first variable and the first value in the implementation manner of executing RNAU above. A specific example is shown in FIG. 16 below.
  • FIG. 16 is a schematic flowchart of another method for controlling transmission provided by an embodiment of the present application. The method includes but is not limited to the following steps:
  • S801 The terminal starts a second timer.
  • S801 is an optional step, and S801 is similar to S401 in FIG. 11 .
  • S802 The terminal starts a first timer.
  • S802 is an optional step, and S802 is similar to S501 in FIG. 13 .
  • the execution order of S801 and S802 may be that S801 is executed first, followed by S802, or S802 is executed first, followed by S801.
  • S803 The terminal performs cell reselection.
  • S803 is an optional step.
  • cell reselection occurs.
  • the terminal undergoes cell reselection, and the first timer is stopped.
  • the terminal undergoes cell reselection and switches from the third cell to the fourth cell, that is, the serving cell after cell reselection of the terminal is the fourth cell, which is subsequently referred to as the second serving cell.
  • the second serving cell of the terminal belongs to the configured RNA, where the RNA is configured for the terminal by the network device before the terminal undergoes cell reselection.
  • the terminal receives the SIB1 of the current serving cell, and determines the second serving cell according to the SIB1, and the SIB1 indicates the second serving cell. In some embodiments, the terminal determines the second serving cell according to the SIB1.
  • the serving cell belongs to the configured RNA, where the RNA is configured for the terminal by the network device before the terminal undergoes cell reselection. The specific example is similar to S502 in FIG. 11 and will not be repeated here.
  • the terminal after cell reselection occurs in the terminal, the terminal is in a non-RRC connected state, and optionally, the non-RRC connected state is an RRC INACTIVE state.
  • the terminal after cell reselection occurs in the terminal, the terminal is in a non-RRC connected state.
  • the non-RRC connected state is the RRC INACTIVE state.
  • the network device Initiate an RRC connection recovery process for SDT, and start a first timer. When cell reselection occurs while the first timer is running, the terminal is still in the RRC INACTIVE state.
  • the terminal may set the first variable to the first value if the terminal is in the RRC INACTIVE state after cell reselection, and the second serving cell belongs to the configured RNA, and the second timer is not running.
  • the terminal when the terminal is in the RRC INACTIVE state, if the second serving cell belongs to the configured RNA, and the second timer is not running, and the terminal cannot perform the SDT process in the second serving cell, the terminal can set the first variable Set to the first value.
  • the fact that the terminal cannot perform the SDT process in the second serving cell means that the terminal cannot continue the previous SDT process in the second serving cell, for example, after the terminal undergoes cell reselection, it cannot continue the RRC for SDT initiated in S802 Connection recovery process.
  • the fact that the terminal cannot perform the SDT process in the second serving cell means that the terminal cannot initiate a new SDT process in the second serving cell, for example, after the terminal undergoes cell reselection, it cannot be the RRC connection for SDT initiated in S802 The recovery process continues to initiate a new SDT process, or cannot initiate a new SDT process for newly acquired small data.
  • the terminal cannot perform the SDT process in the second serving cell because the terminal does not have SDT-related configuration information in the second serving cell, for example, the second serving cell does not support SDT, and optionally, the second serving cell does not support SDT It includes related configuration that the second serving cell does not broadcast SDT in the system information.
  • the second serving cell does not support RA-SDT and/or CG-SDT.
  • the terminal undergoes cell reselection, the terminal is in the RRC INACTIVE state, and the terminal still needs to perform periodic RNAU, but since the second timer is not running at this time, the terminal can set the first variable to the first value .
  • the second timer expires, and the terminal can determine whether the first timer is running. If the first timer is running, the terminal does not trigger the RNAU, and continues to perform the SDT process.
  • the operation of the first timer means that the first timer continues to run, and the terminal can continue the previous SDT process in the second serving cell.
  • the operation of the first timer means that the first timer is started, and the terminal can Second, the serving cell initiates a new RRC connection recovery procedure for SDT. After the second timer expires, cell reselection occurs in the terminal, the first timer is stopped, and the terminal is in the RRC INACTIVE state. If the second timer is not running, the terminal may set the first variable as the first value.
  • the second timer is not running means not running after the second timer expires.
  • the terminal after cell reselection occurs in the terminal, it is in the RRC IDLE state, then the terminal does not trigger RNA, nor sets the first variable to the first value. In some other embodiments, after cell reselection occurs in the terminal, , the SDT process can be performed in the second serving cell, then the terminal does not trigger the RNA, and does not set the first variable to the first value.
  • the terminal when receiving the SIB1 of the second serving cell, if the second serving cell belongs to the configured RNA and the second timer is not running, the terminal can directly execute the The RRC connection recovery process of RNAU, the specific example is similar to that in Figure 16, the difference is that the first variable in Figure 16 is replaced with the RRC connection recovery process for RNAU, for example, the RRC layer of the terminal is used for RNAU The RRC connection recovery process.
  • the terminal may first set the first variable to the first value, and then the terminal performs the RRC connection recovery process for RNAU, for example, the RRC layer of the terminal directly performs the RRC connection recovery process for RNAU.
  • the terminal when receiving the SIB1 of the second serving cell, if the second serving cell belongs to the configured RNA and the second timer is not running, the terminal starts the third timer.
  • the specific example is similar to that in FIG. 16 , The difference is that in Fig. 16, setting the first variable to the first value is replaced by starting the third timer.
  • the method further includes: when the third timer expires, if the first timer is not running, the terminal executes an RRC connection recovery process for RNAU.
  • the third timer is the same as the second timer, for example, the duration of the third timer is equal to the duration of the second timer.
  • the third timer is T380.
  • the third timer is different from the second timer, for example, the duration of the third timer is not equal to the duration of the second timer.
  • the duration of the third timer is shorter than that of the second timer, for example, the duration of the third timer is in milliseconds or seconds.
  • the terminal may wait for whether the NAS layer has a data transmission requirement, for example, whether the NAS triggers the RRC layer to initiate a connection recovery process. If the NAS layer has a data transmission requirement and triggers the RRC layer to initiate a connection recovery process, the terminal will initiate the RRC connection recovery process for data transmission instead of executing the RRC connection recovery process for RNAU.
  • the above RRC connection recovery process for data transmission Recovery procedures include RRC connection recovery procedures for SDT and for non-SDT.
  • the terminal can set the variable pendingRNA-Update set to true.
  • the terminal may set the first variable to the first value, and the first variable being the first value indicates that there is a pending RNAU
  • the terminal may set the first variable to the first value, and the first variable being the first value indicates that there is a pending RNAU
  • the first variable and the first value please refer to the description of the first variable and the first value in the implementation manner of executing RNAU above, and a specific example is shown in FIG. 17 below.
  • FIG. 17 is a schematic flowchart of another method for controlling transmission provided by an embodiment of the present application. The method includes but is not limited to the following steps:
  • S901 The terminal starts a second timer.
  • S901 is an optional step, and S901 is similar to S401 in FIG. 11 .
  • S902 The terminal starts a first timer.
  • S902 is an optional step, and S902 is similar to S501 in FIG. 13 .
  • the order of execution of S901 and S902 may be that S901 is executed first, followed by S902, or S902 is executed first, followed by S901.
  • the integrity check of the terminal fails.
  • the integrity check failure of the terminal is: the RRC layer of the terminal receives the integrity check failure indicated by the bottom layer of the RRC layer, and the bottom layer of the RRC layer is, for example, the PDCP layer.
  • the terminal after the integrity verification of the terminal fails, the terminal is in the RRC INACTIVE state. In some embodiments, when the terminal is in the RRC INACTIVE state, it initiates an RRC connection recovery process for SDT to the network device, and starts the first timer. After the integrity check of the terminal fails when the first timer is running, the terminal is still in the RRC INACTIVE state.
  • the integrity check of the terminal fails, the terminal is in the RRC INACTIVE state, and the terminal still needs to perform periodic RNAU, but since the second timer is not running at this time, the terminal can set the first variable to the first one value.
  • the second timer expires, and the terminal may determine whether the first timer is running. If the first timer is running, the terminal does not trigger the RNAU, and continues to perform the SDT process. After the second timer expires, if the integrity check of the terminal fails, the terminal is in the RRC INACTIVE state. If the second timer is not running, the terminal may set the first variable as the first value. Optionally, the second timer is not running means not running after the second timer expires.
  • the terminal if the integrity check of the terminal fails and the terminal is in the RRC IDLE state, the terminal does not trigger the RNAU, and does not set the first variable to the first value.
  • the terminal when the integrity check of the terminal fails, if the second timer is not running, the terminal can directly perform the RRC connection recovery process for RNAU, the specific example is the same as that shown in Figure 17 Similarly, the difference is that setting the first variable to the first value in FIG. 17 is replaced by performing the RRC connection recovery process for RNAU, for example, the RRC layer of the terminal performs the RRC connection recovery process for RNAU.
  • the terminal may first set the first variable to the first value, and then the terminal performs the RRC connection recovery process for RNAU, for example, the RRC layer of the terminal directly performs the RRC connection recovery process for RNAU.
  • the terminal when the integrity check of the terminal fails, if the second timer is not running, the terminal can start the third timer, and when the third timer expires, if the first timer is not running, the terminal executes the For the RRC connection recovery process of RNAU, the specific example is similar to that in FIG. 17 , the difference is that in FIG. 17 , the first variable is set to the first value and the third timer is turned on.
  • the method further includes: when the third timer expires, if the first timer is not running, the terminal executes an RRC connection recovery process for RNAU.
  • the third timer is the same as the second timer, for example, the duration of the third timer is equal to the duration of the second timer.
  • the third timer is T380.
  • the third timer is different from the second timer, for example, the duration of the third timer is not equal to the duration of the second timer.
  • the duration of the third timer is shorter than that of the second timer, for example, the duration of the third timer is in milliseconds or seconds.
  • the terminal may wait for whether the NAS layer has a data transmission requirement, for example, whether the NAS triggers the RRC layer to initiate a connection recovery process. If the NAS layer has a data transmission requirement and triggers the RRC layer to initiate a connection recovery process, the terminal will initiate the RRC connection recovery process for data transmission instead of executing the RRC connection recovery process for RNAU.
  • the above RRC connection recovery process for data transmission Recovery procedures include RRC connection recovery procedures for SDT and for non-SDT.
  • RNAU when the SDT process is in progress.
  • the network device can obtain the RNA where the terminal is located. Not executing RNAU will not only not affect the state of the terminal acquired by the network device, but also avoid affecting Small packets of data transmitted by the SDT process.
  • the terminal can set the first variable to the first value, so that subsequent UEs can continue to periodically trigger the RNAU without affecting the normal execution of the RNAU.
  • the terminal may perform the RRC connection recovery process for the RNAU.
  • the terminal if the first variable is set to the first value during the SDT process, and the upper layer (such as the NAS layer) does not request RRC connection recovery, the terminal performs the RRC connection recovery process for RNAU.
  • the terminal if the prohibition that the Access Category of the terminal is 2 or the Access Category is 8 is eased, and the upper layer (such as the NAS layer) does not request to resume the RRC connection, and the first variable is set to the first value, the terminal executes with RRC connection restoration process in RNAU.
  • the terminal if the prohibition of the Access Category of the terminal in the SDT process is eased, and the upper layer (such as the NAS layer) does not request to resume the RRC connection, and the first variable is set to the first value, the terminal performs RRC for RNAU Connection recovery process. In some embodiments, if the access barring is eased and the upper layer (such as the NAS layer) does not request the RRC layer to perform RRC connection recovery, if the first variable is the first value, the terminal can perform an RRC connection for RNAU recovery process.
  • FIG. 18 exemplarily shows another timing diagram.
  • the horizontal axis is the time axis (t).
  • the second timer is turned on (for example, the first RRC response message is received), and at the fourth moment t4, the first timer is turned on. (for example, sending an RRC request message), at the fifth time t 5 , the second timer times out, and at the sixth time t 6 , the first timer stops or times out, t 3 ⁇ t 4 ⁇ t 5 ⁇ t 6 .
  • the second timer runs between the third moment and the fifth moment, the first timer runs between the fourth moment and the sixth moment, and the terminal performs the SDT process between the fourth moment and the sixth moment.
  • the terminal will not trigger the RNAU when the second timer times out, that is, the terminal will not trigger the RNAU when the second timer times out and the first timer is running.
  • the terminal undergoes cell reselection, the first timer stops, and the terminal is in the RRC INACTIVE state. If the serving cell of the terminal does not belong to the configured RNA after cell reselection, and the terminal cannot be in the service When the cell performs the SDT process, the terminal can trigger RNAU.
  • triggering RNAU is to perform the RRC connection recovery process for RNAU. For details, please refer to the description in Figure 13 above.
  • the terminal receives the fourth RRC response message, the first timer stops, and the terminal is in the RRC INACTIVE state. If the second timer is not running, the terminal can trigger RNAU, optionally , to trigger RNAU, the first variable can be set to the first value, for details, please refer to the description of Figure 14 above.
  • the terminal at the sixth moment, the first timer expires, and the terminal is in the RRC INACTIVE state. If the second timer is not running, the terminal can trigger RNAU.
  • triggering RNAU can set the first variable Set it to the first value, for details, please refer to the description of Figure 15 above.
  • the terminal undergoes cell reselection, the first timer stops, and the terminal is in the RRC INACTIVE state. If the serving cell of the terminal belongs to the configured RNA after cell reselection, the terminal cannot be in the serving cell When the SDT process is performed, and the second timer is not running at this time, the terminal can trigger RNAU.
  • triggering RNAU can set the first variable to the first value. For details, refer to the description of FIG. 16 above.
  • the integrity check of the terminal fails, the first timer stops, and the terminal is in the RRC INACTIVE state. If the second timer is not running, the terminal can trigger RNAU.
  • the first variable can be set to the first value. For details, please refer to the description of FIG. 17 above.
  • the second timer may be stopped, and a specific example is shown in FIG. 19 below.
  • FIG. 19 is a schematic flowchart of another method for controlling transmission provided by an embodiment of the present application. The method includes but is not limited to the following steps:
  • S1001 The terminal sends an RRC request message to the network device.
  • S1001 is an optional step.
  • the terminal when it has a requirement for SDT, it may initiate an RRC connection recovery process for SDT, and the RRC connection recovery process may include the terminal sending an RRC request message to the network device based on the SDT.
  • the terminal when it has a requirement for SDT, it can initiate the RRC connection restoration process for 4-step SDT.
  • the RRC connection restoration process for 4-step SDT.
  • the terminal is in the RRC connection recovery process
  • the sent RRC request message is sent based on 4-step SDT, and the RRC request message can be in msg3.
  • the terminal when it has a requirement for SDT, it can initiate the RRC connection recovery process for 2-step SDT.
  • the RRC connection recovery process for this process, refer to the processes shown in Figures 7-8 above, where the terminal is in the RRC connection recovery process.
  • the sent RRC request message is sent based on 2-step SDT, and the RRC request message can be in msgA.
  • the terminal when it has a requirement for SDT, it can initiate the RRC connection recovery process for CG-SDT.
  • the terminal when it has a requirement for SDT, it can initiate the RRC connection recovery process for CG-SDT.
  • the terminal sends during the RRC connection recovery process
  • the RRC request message is sent based on CG-SDT.
  • the terminal when the terminal sends the RRC request message to the network device, it also sends the uplink small packet data together.
  • the specific examples are as shown in the processes shown in FIG. 5 , FIG. 7 , and FIG. 9 above.
  • S1002 The network device sends a first response message to the terminal.
  • S1002 is an optional step.
  • the network device receives the RRC request message sent by the terminal, and may send a first response message to the terminal. In some embodiments, the network device receives the RRC request message and the uplink packet data sent by the terminal, and may send the terminal a response message. Send the first response message.
  • the terminal initiates RA-SDT, and the network device receives the RRC request message sent by the terminal based on RA-SDT, and may send a first response message to the terminal.
  • the first response message may indicate that the contention resolution is successful
  • the first response message may indicate that the random access process is successfully completed.
  • the terminal receives the first response message and determines that the contention resolution is successful.
  • the terminal receives the first response message and determines that the random access process is successfully completed.
  • the first response message is the contention resolution message shown in Figure 5-8 above.
  • the terminal initiates CG-SDT
  • the network device receives the RRC request message sent by the terminal based on CG-SDT, and may send a first response message to the terminal.
  • the first response message may be directed to the RRC request message sent in S1001.
  • RRC request message and/or uplink packet data optionally, the first response message may indicate that the RRC request message is successfully sent, optionally, the first response message may indicate that the uplink packet data is successfully sent, optionally, the first response message
  • the first response message may be downlink control information (downlink control information, DCI) for scheduling retransmission, and optionally, the first response message may be scheduling The newly transmitted DCI.
  • DCI downlink control information
  • the bottom layer of the terminal indicates the first information to the upper layer.
  • S1003 is an optional step.
  • the terminal may include multiple layers.
  • the bottom layer and the upper layer in S1003 are relative concepts.
  • the bottom layer of the terminal in S1003 is the first layer, and the first layer is a layer in the user plane protocol stack or the control plane protocol stack.
  • the first layer is the layer that receives the first response message sent by the network device.
  • the upper layer in S1003 is the second layer, and the second layer is a layer higher than the first layer.
  • the first layer is the MAC layer
  • the second layer is the RRC layer
  • the first layer is the physical layer
  • the second layer is the MAC layer
  • the first layer is the physical layer
  • the second layer is the RRC layer
  • the third layer of the terminal receives the first information indicated by the bottom layer of the third layer, and stops the second timer.
  • the third layer is the RRC layer.
  • the bottom layer of the third layer is the MAC layer, and optionally, the bottom layer of the third layer is the physical layer.
  • the MAC layer of the terminal receives the first response message sent by the network device, and the MAC layer indicates the first information to the RRC layer above the MAC layer.
  • the first information indicates The contention is resolved successfully.
  • the first indication information indicates that the random access process is successfully completed.
  • the RRC layer receives the first information indicated by the MAC layer, and stops the second timer.
  • the bottom layer in S1003 is the MAC layer
  • the upper layer is the RRC layer
  • the one that stops the second timer in S1004 is the RRC layer.
  • the MAC layer of the terminal receives the first response message sent by the network device, the MAC layer indicates the first information to the RRC layer above the MAC layer, and the first information indicates the RRC request message and /or the uplink packet data is sent successfully, the RRC layer receives the first information indicated by the MAC layer, and stops the second timer.
  • the bottom layer in S1003 is the MAC layer
  • the upper layer is the RRC layer
  • the one that stops the second timer in S1004 is the RRC layer.
  • the physical layer of the terminal receives the first response message sent by the network device, the physical layer indicates the first information to the RRC layer above the physical layer, and the first information indicates the RRC request message and /or the uplink packet data is sent successfully, the RRC layer receives the first information indicated by the physical layer, and stops the second timer.
  • the bottom layer in S1003 is the physical layer
  • the upper layer is the RRC layer
  • the one that stops the second timer in S1004 is the RRC layer.
  • the physical layer of the terminal receives the first response message sent by the network device, the physical layer indicates the second information to the MAC layer above the physical layer, and the second information indicates the RRC request message and /or the uplink small packet data is sent successfully.
  • the MAC layer receives the second information indicated by the physical layer, and indicates the first information to the RRC layer above the MAC layer.
  • the first information indicates that the RRC request message and/or the uplink packet data are sent successfully, and the RRC layer receives the first information indicated by the MAC layer. message, stop the second timer.
  • the bottom layer in S1003 is the MAC layer
  • the upper layer is the RRC layer
  • the one that stops the second timer in S1004 is the RRC layer.
  • the second timer before the terminal stops the second timer, the second timer is on, for example, before initiating the RRC connection recovery process for SDT (such as S1001), the terminal starts the second timer.
  • subsequent transmission may be performed based on the current SDT process.
  • subsequent transmission may be performed based on the current SDT process.
  • the second timer has been stopped and will not time out, so RNAU will not be triggered, and thus will not affect the transmission of small data during the SDT process.
  • the terminal stops the second timer it can receive the RRC response message sent by the network device. For details, refer to the description of the RRC response message in FIGS. 5-10 above.
  • the terminal stops the second timer it receives the first RRC response message sent by the network device, such as RRCRelease message, RRCRelease with suspend config message or other RRC messages with the same function but not standardized by 3GPP, the terminal A second timer may be started.
  • situations of starting the second timer described in the above embodiments may include various situations, and two situations are exemplarily shown below:
  • Case 1 When the terminal performs SDT, it receives the first RRC response message, stops the first timer and starts the second timer. Exemplarily, firstly, when the terminal has an SDT requirement, it initiates an RRC connection recovery process for SDT, and starts a first timer. Then, when the second timer expires but the first timer is in the running state, the terminal does not trigger the RNAU and continues to perform SDT. Finally, the terminal receives the first RRC response message, considers that the SDT is successful, stops the first timer, and remains in the non-RRC connection state, and the terminal receives the first RRC response message, starts the second timer, so that the subsequent Periodic triggering of RNAU can continue.
  • Case 2 When the terminal performs SDT, it receives the fifth RRC response message, stops the first timer, and then starts the second timer after receiving the first RRC response message.
  • the fifth RRC response message is, for example, RRCResume message, RRCSetup message or other RRC messages that have the same functionality but are not standardized by 3GPP.
  • the terminal firstly, when the terminal has an SDT requirement, it initiates an RRC connection recovery process for SDT, and starts a first timer. Then, when the second timer expires but the first timer is in the running state, the terminal does not trigger the RNAU and continues to perform SDT.
  • the terminal receives the fifth RRC response message, considers that the SDT is successful, stops the first timer, and can enter the RRC CONNECTED state from the non-RRC connected state. Subsequent terminals receive the first RRC response message, enter the non-RRC connected state from the RRC CONNECTED state, and start the second timer, so that the subsequent periodic triggering of RNAU can continue.
  • the terminal receives the RRC rejection message, and if the second timer is not running, the terminal can set the first variable to the first value.
  • the specific example is similar to that in FIG. 14 , except that the second timing in FIG. 14 If the timer expires, it needs to be replaced by the second timer stop.
  • the second timer stop please refer to Figure 19 above.
  • the terminal receives the RRC rejection message, if the second timer is not running, the terminal can directly execute the RRC connection recovery process for RNAU, the specific example is similar to that in Figure 14, the difference is that S604 can be changed to: If the second timer is not running, execute the RRC connection recovery process for RNAU, and the second timer in Figure 14 needs to be replaced with the second timer stopping when the second timer expires, and the description of the second timer stopping can be found in Figure 19 above.
  • the terminal receives the RRC rejection message, if the second timer is not running, the terminal can start the third timer, when the third timer expires, if the first timer is not running, the terminal executes the The RRC connection recovery process of RNAU, the specific example is similar to Figure 14, the difference is that S604 can be changed to: if the second timer is not running, start the third timer, after S604, the method also includes: when the third timer expires, if The first timer is not running, the terminal executes the RRC connection recovery process for RNAU, and the second timer in Figure 14 needs to be replaced by the second timer stopping when the second timer expires, and the description of the second timer stopping can be found in Figure 19 above.
  • the terminal when the first timer expires, if the second timer is not running, the terminal can set the first variable to the first value.
  • the specific example is similar to that in FIG. 15, except that the second timer in FIG. The timer overtime needs to be replaced by the second timer stop, and the description of the second timer stop can be found in Figure 19 above.
  • the terminal when the first timer expires, if the second timer is not running, the terminal can directly execute the RRC connection recovery process for RNAU, the specific example is similar to that in Figure 15, the difference is that S703 can be changed to :
  • the first timer expires if the second timer is not running, execute the RRC connection recovery process for RNAU, and the second timer in Figure 15 needs to be replaced by the second timer stop, the second timer stop See Figure 19 above for instructions.
  • the terminal when the first timer expires, if the second timer is not running, the terminal can start the third timer, and when the third timer expires, if the first timer is not running, the terminal executes the In the RRC connection recovery process of RNAU, the specific example is similar to Figure 15, the difference is that S703 can be changed to: when the first timer expires, if the second timer is not running, start the third timer, after S703, the method also includes: When the third timer expires, if the first timer is not running, the terminal executes the RRC connection recovery process for RNAU, and the second timer in Figure 15 needs to be replaced with the second timer stopped, the second timer stopped See Figure 19 above for instructions.
  • the terminal when receiving the SIB1 of the second serving cell, if the second serving cell belongs to the configured RNA and the second timer is not running, the terminal may set the first variable to the first value,
  • the specific example is similar to that in Figure 16, except that the second timer in Figure 16 needs to be replaced by the second timer stopping when the second timer expires, and the description of the second timer stopping can be found in Figure 19 above.
  • the terminal when receiving the SIB1 of the second serving cell, if the second serving cell belongs to the configured RNA and the second timer is not running, the terminal can directly perform the RRC connection recovery process for RNAU , the specific example is similar to that in Figure 15, the difference is that S804 can be changed to: if the second serving cell belongs to the configured RNA, and the second timer is not running, execute the RRC connection recovery process for RNAU, and the second timing in Figure 16 If the timer expires, it needs to be replaced by the second timer stop.
  • the second timer stop please refer to Figure 19 above.
  • the terminal when receiving the SIB1 of the second serving cell, if the second serving cell belongs to the configured RNA and the second timer is not running, the terminal starts the third timer, the specific example is as shown in Figure 16 Similarly, the difference is that S804 can be changed to: if the second serving cell belongs to the configured RNA, and the second timer is not running, start the third timer, and after S804, the method also includes: when the third timer expires, if the first The timer is not running, the terminal executes the RRC connection recovery process for RNAU, and the second timer in Figure 16 needs to be replaced with the second timer stopping when the second timer expires, and the description of the second timer stopping can be found in Figure 19 above.
  • the terminal when the integrity check of the terminal fails, if the second timer is not running, the terminal can set the first variable to the first value.
  • the specific example is similar to that in FIG. 17 , except that in FIG. 17
  • the second timer expires, it needs to be replaced by the second timer stop.
  • the second timer stop please refer to Figure 19 above.
  • the terminal when the integrity check of the terminal fails, if the second timer is not running, the terminal can directly execute the RRC connection recovery process for RNAU, the specific example is similar to that in Figure 17, the difference is that S903 can Change to: When the integrity check fails, and the second timer is not running, execute the RRC connection recovery process for RNAU, and the second timer in Figure 17 needs to be replaced by the second timer stop when the second timer expires. See Figure 19 above for instructions on stopping.
  • the terminal when the integrity verification of the terminal fails, if the second timer is not running, the terminal can start the third timer, the specific example is similar to that in Figure 17, the difference is that S903 can be changed to: when the complete If the verification fails and the second timer is not running, start the third timer.
  • the method further includes: when the third timer expires, if the first timer is not running, the terminal performs RRC connection recovery for RNAU The process, and the timeout of the second timer in Figure 17 need to be replaced by the second timer stop, and the description of the second timer stop can be found in Figure 19 above.
  • the terminal may perform RRC connection recovery procedures for RNAU.
  • the SDT process in this application may include the above-mentioned RRC connection recovery process for SDT, optionally, the resumeCause IE in the RRC request message sent for mo-data.
  • the RNAU in the present application (such as the implementation of the RNAU described above) may include the above-mentioned RRC connection recovery process for the RNAU, optionally, the resumeCause IE in the sent RRC request message is rna-Update.
  • RNAU it may be necessary to execute RNAU in the RRC IDLE state.
  • the specific implementation method is similar to the implementation method of the UE in the RRC INACTIVE state above, but the expression may be different.
  • the RRC connection recovery procedure for RNAU can be replaced by the RRC connection establishment procedure for RNAU.
  • the terminal may receive other messages, determine whether the serving cell belongs to the configured RNA according to the message, for example, read the cell ID from the message, and determine whether the read cell ID is It belongs to the cell identity included in the cell list configured by the base station for the UE in the RAN-NotificationAreaInfo IE, and for example reads the TAC of the cell from the message, and determines whether the read TAC belongs to the RAN area configured by the base station for the UE in the RAN-NotificationAreaInfo IE TACs included in the list.
  • the present application does not limit the manner of judging whether the serving cell belongs to the configured RNA.
  • the UE in the RRC INACTIVE state needs to trigger the RRC connection recovery process for RNAU after T380 times out or after receiving SIB1 in a cell outside the UE's current RNA.
  • a UE that is doing SDT data transmission does not actually need to do RNAU because the network settings can know the UE's cell location. Therefore, triggering RNAU during SDT should be avoided.
  • T380 is stopped during SDT. For example, after the SDT process starts, the UE stops T380 when it receives the first response message corresponding to the UE's RRC request message from the network device. For example, the UE stops T380 when receiving the contention resolution MAC CE of RA-SDT, or when receiving the ACK in response to the RRCResumeRequest sent through CG-SDT.
  • an additional condition is introduced, that is, only when the SDT failure detection timer is not running, that is, when the first timer is not running, the RNAU can be triggered if T380 expires.
  • the SDT failure detection timer is started when the UE initiates the RRC connection recovery procedure for SDT, that is, when the SDT failure detection timer is running, the UE is in the process of SDT. Therefore, to avoid periodic RNAU triggered by T380 timeout, an additional condition can be added to the current conditions that trigger periodic RNAU.
  • the processes can be completed by computer programs or hardware related to the computer programs.
  • the computer programs can be stored in computer-readable storage media.
  • the computer programs During execution, it may include the processes of the foregoing method embodiments.
  • the aforementioned storage medium includes: various media capable of storing computer program codes such as read-only memory (ROM) or random access memory (RAM), magnetic disk or optical disk.

Abstract

本申请实施例提供一种控制传输的方法及相关装置，该方法应用于处于非无线资源控制RRC连接态的终端，包括：满足第一预设条件时，执行用于基于无线接入网的通知区域更新RNAU的RRC连接恢复过程；第一预设条件包括第二定时器超时并且第一定时器未运行；或第一预设条件包括终端接收到服务小区的系统信息块SIB1，服务小区不属于配置的基于无线接入网的通知区域，并且第一定时器未运行；第一定时器在终端发起用于小包数据传输SDT的RRC连接恢复过程时开启，第二定时器在终端接收到包括第二定时器时长的RRC释放消息时开启。本申请能够避免SDT过程中触发RNAU，从而避免影响小包数据的传输，以及不必要的功耗和信令开销。

Description

一种控制传输的方法及相关装置
本申请要求于2021年07月21日提交中国专利局、申请号为202110822924.X、申请名称为“一种通信方法、终端及网络设备”的中国专利申请的优先权，本申请要求于2021年08月05日提交中国专利局、申请号为202110897870.3、申请名称为“一种控制传输的方法及相关装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种控制传输的方法及相关装置。
背景技术
在通信系统中，终端与网络设备的通信协议栈中可以包括无线资源控制(radio resource control，RRC)层。目前存在三种终端的RRC状态，分别为RRC空闲(RRC IDLE)态、RRC非激活(RRC INACTIVE)态和RRC连接(RRC CONNECTED)态。处于RRC INACTIVE态的终端可以通过RRC连接恢复过程和网络设备传输小包数据(small data)，可称为进行小包数据传输(small data transmission，SDT)。终端处于RRC INACTIVE态时，可以由无线接入网(radio access network，RAN)管理基于RAN的通知区域(RAN-based notification area，RNA)，例如终端可以触发RNA更新(RNA update，RNAU)，执行用于RNAU的RRC连接恢复过程，以通知网络设备终端当前的所处的RNA。
终端进行SDT时，可能触发执行RNAU，在这种情况下，终端可能停止当前进行的SDT，并执行RNAU，从而影响small data的传输，例如增大传输时延，后续再次发起SDT也会增加功耗和信令开销。
发明内容
本申请实施例公开了一种控制传输的方法及相关装置，能够避免影响小包数据的传输，以及不必要的功耗和信令开销。
第一方面，本申请实施例提供了一种控制传输的方法，应用于处于非无线资源控制RRC连接态的终端，所述方法包括：满足第一预设条件时，执行用于基于无线接入网的通知区域更新RNAU的RRC连接恢复过程；其中，所述第一预设条件包括第二定时器超时并且第一定时器未运行；或，所述第一预设条件包括所述终端接收到第一服务小区的系统信息块SIB1，所述第一服务小区不属于配置的基于无线接入网的通知区域RNA，并且所述第一定时器未运行；其中，所述第一定时器在所述终端发起用于小包数据传输SDT的RRC连接恢复过程时开启，所述第二定时器在所述终端接收到包括所述第二定时器时长的RRC释放消息时开启。
在一些实施例中，用于RNAU的RRC连接恢复过程包括发送RRC请求消息，该RRC请求消息中恢复原因resumeCause信息元素IE为rna-Update。
例如，第二定时器为T380。
本申请中，第一定时器运行时(即进行SDT过程中)，不会执行RNAU，其中进行SDT时，网络设备可以获取到终端所处的RNA，不执行RNAU不仅不会影响网络设备获取终端的状态，而且可以避免影响SDT过程传输的小包数据，例如避免增加传输时延，后续重新发 起SDT增加不必要的信令开销和功耗等。
在一种可能的实现方式中，所述第一定时器未运行为所述第一定时器未开启。
在一些实施例中，第一定时器未开启表征没有SDT的需求。
在一种可能的实现方式中，所述满足第一预设条件时，执行用于基于无线接入网的通知区域更新RNAU的无线资源控制RRC连接恢复过程之前，所述方法还包括：发起用于SDT的RRC连接恢复过程，开启所述第一定时器；发生小区重选，停止所述第一定时器；所述第一预设条件包括所述第一定时器未运行和所述终端的服务小区不属于配置的RNA，所述第一定时器未运行为所述第一定时器停止，所述终端的服务小区为所述终端发生小区重选后的服务小区。
在一些实施例中，用于SDT的RRC连接恢复过程包括发送RRC请求消息，该RRC请求消息中resumeCause IE为mo-data。
在一种可能的实现方式中，所述第一预设条件还包括：所述终端处于RRC非激活态；和/或，所述终端在所述服务小区不可以进行SDT过程。
在一些实施例中，终端在服务小区不可以进行SDT过程，包括：终端在服务小区不可以继续之前的SDT过程。在一些实施例中，终端在服务小区不可以进行SDT过程，包括：终端在服务小区不可以发起新的SDT过程。
在一种可能的实现方式中，所述方法还包括：在所述第一定时器运行时，若接收到RRC拒绝消息，停止所述第一定时器；若所述第二定时器未运行，将第一变量设置为第一值，所述第一变量为所述第一值指示有待定的RNA更新过程。
本申请中，若第一定时器运行时(即进行SDT过程中)，第二定时器超时，终端不会执行RNAU，也不会将第一变量设置为第一值，从而避免影响当前进行的SDT过程。当SDT过程非正常结束(如第一定时器停止或者超时)，并且第二定时器未运行，终端可以将第一变量设置为第一值，以使后续可以正常执行RNAU。
在一种可能的实现方式中，所述方法还包括：在所述第一定时器运行时，若接收到RRC拒绝消息，停止所述第一定时器；若所述第二定时器未运行，执行所述用于RNAU的无线资源控制RRC连接恢复过程。
本申请中，若第一定时器运行时(即进行SDT过程中)，第二定时器超时，终端不会执行RNAU，从而避免影响当前进行的SDT过程。当SDT过程非正常结束(如第一定时器停止或者超时)，并且第二定时器未运行，终端再执行RNAU，保证RNAU的正常执行。
在一种可能的实现方式中，所述方法还包括：在所述第一定时器运行时，若接收到RRC拒绝消息，停止所述第一定时器；若所述第二定时器未运行，开启第三定时器，当所述第三定时器超时，若所述第一定时器未运行，执行所述用于RNAU的RRC连接恢复过程。
在一种可能的实现方式中，第三定时器的时长与第二定时器的时长相同。
在一种可能的实现方式中，第三定时器的时长与第二定时器的时长不同。
在一种可能的实现方式中，所述非无线资源控制RRC连接态为RRC非激活态；所述终端接收到RRC拒绝消息后，所述终端处于所述RRC非激活态。
本申请中，若第一定时器运行时(即进行SDT过程中)，第二定时器超时，终端不会执行RNAU，也不会开启第三定时器，从而避免影响当前进行的SDT过程。当SDT过程非正常结束(如第一定时器停止或者超时)，并且第二定时器未运行，终端可以开启第三定时器，当第三定时器超时并且第一定时器未运行时，再执行用于RNAU的无线资源控制RRC连接恢复过程，保证RNAU的正常执行。
在一种可能的实现方式中，所述方法还包括：当所述第一定时器超时，若所述第二定时器未运行，将第一变量设置为第一值，所述第一变量为所述第一值指示有待定的RNA更新过程。
在一种可能的实现方式中，所述方法还包括：当所述第一定时器超时，若所述第二定时器未运行，执行所述用于RNAU的无线资源控制RRC连接恢复过程。
在一种可能的实现方式中，所述方法还包括：当所述第一定时器超时，若所述第二定时器未运行，开启第三定时器，当所述第三定时器超时，若所述第一定时器未运行，执行所述用于RNAU的RRC连接恢复过程。
在一种可能的实现方式中，第三定时器的时长与第二定时器的时长相同。
在一种可能的实现方式中，第三定时器的时长与第二定时器的时长不同。
在一种可能的实现方式中，所述非无线资源控制RRC连接态为RRC非激活态；所述第一定时器超时后，所述终端处于所述RRC非激活态。
在一种可能的实现方式中，所述方法还包括：在所述第一定时器运行时，若发生小区重选，停止所述第一定时器；接收第二服务小区的SIB1，所述第二服务小区为所述终端发生小区重选后的服务小区；当接收到所述第二服务小区的SIB1时，若所述第二服务小区属于配置的RNA，并且所述第二定时器未运行，将第一变量设置为第一值，所述第一变量为所述第一值指示有待定的RNA更新过程。
在一种可能的实现方式中，所述方法还包括：在所述第一定时器运行时，若发生小区重选，停止所述第一定时器；接收第二服务小区的SIB1，所述第二服务小区为所述终端发生小区重选后的服务小区；当接收到所述第二服务小区的SIB1时，若所述第二服务小区属于配置的RNA，并且所述第二定时器未运行，执行所述用于RNAU的无线资源控制RRC连接恢复过程。
在一种可能的实现方式中，所述方法还包括：在所述第一定时器运行时，若发生小区重选，停止所述第一定时器；接收第二服务小区的SIB1，所述第二服务小区为所述终端发生小区重选后的服务小区；当接收到所述第二服务小区的SIB1时，若所述第二服务小区属于配置的RNA，并且所述第二定时器未运行，开启第三定时器，当所述第三定时器超时，若所述第一定时器未运行，执行所述用于RNAU的RRC连接恢复过程。
在一种可能的实现方式中，第三定时器的时长与第二定时器的时长相同。
在一种可能的实现方式中，第三定时器的时长与第二定时器的时长不同。
在一种可能的实现方式中，所述非无线资源控制RRC连接态为RRC非激活态；所述终端发生小区重选后，所述终端处于所述RRC非激活态。
在一种可能的实现方式中，所述将第一变量设置为第一值之后，所述方法还包括：若接入禁止被缓和并且非接入NAS层没有请求RRC层进行RRC连接恢复，若所述第一变量为所述第一值，执行所述用于RNAU的RRC连接恢复过程。
在一种可能的实现方式中，所述非无线资源控制RRC连接态为RRC非激活态。
第二方面，本申请实施例提供了又一种控制传输的方法，应用于处于非RRC连接态的终端，所述方法包括：满足第一预设条件时，将第一变量设置为第一值，所述第一变量为所述第一值指示有待定的RNA更新过程，所述第一预设条件包括第一定时器未运行，所述第一定时器在所述终端接收到包括所述第一定时器时长的RRC释放消息时开启。
例如，第一定时器为T380。
在一种可能的实现方式中，所述第一预设条件还包括在第二定时器运行时，所述终端接收到RRC拒绝消息；所述第二定时器在所述终端发起用于SDT的RRC连接恢复过程时开启，所述第二定时器在所述终端接收到所述RRC拒绝消息时停止。
在一种可能的实现方式中，所述第一预设条件还包括第二定时器超时，所述第二定时器在所述终端发起用于SDT的RRC连接恢复过程时开启。
在一种可能的实现方式中，所述非RRC连接态为RRC非激活态；所述第二定时器超时后，所述终端处于所述RRC非激活态。
在一种可能的实现方式中，所述第一预设条件还包括所述终端接收到第一服务小区的SIB1，并且所述第一服务小区属于配置的RNA；所述满足第一预设条件时，将第一变量设置为第一值之前，所述方法还包括：在第二定时器运行时，若发生小区重选，停止所述第二定时器，所述第二定时器在所述终端发起用于SDT的RRC连接恢复过程时开启；接收所述第一服务小区的SIB1，所述第一服务小区为所述终端发生小区重选后的服务小区。
在一种可能的实现方式中，所述将第一变量设置为第一值之后，所述方法还包括：若接入禁止被缓和并且非接入NAS层没有请求RRC层进行RRC连接恢复，若所述第一变量为所述第一值，执行用于RNAU的RRC连接恢复过程。
在一种可能的实现方式中，所述非RRC连接态为RRC非激活态。
本申请中，若第二定时器运行时(即进行SDT过程中)，第一定时器超时，终端不会执行RNAU，也不会将第一变量设置为第一值，从而避免影响当前进行的SDT过程。当SDT过程非正常结束(如第二定时器停止或者超时)，并且第一定时器未运行，终端可以将第一变量设置为第一值，以使后续可以正常执行RNAU。
第三方面，本申请实施例提供了又一种控制传输的方法，应用于处于非RRC连接态的终端，该方法包括：开启第一定时器；发起用于SDT的RRC连接恢复过程；在所述用于SDT的RRC连接恢复过程中，底层向上层指示第一信息，所述第一信息指示所述用于SDT的RRC连接恢复过程成功；基于所述第一信息，停止所述第一定时器。
在一些实施例中，所述终端在接收到包括所述第一定时器时长的RRC释放消息时开启第一定时器。例如，第一定时器为T380。
本申请中，终端进行SDT过程时，可以停止第一定时器，从而避免第一定时器超时触发RNAU。其中进行SDT时，网络设备可以获取到终端所处的RNA，不触发RNAU不仅不会影响网络设备获取终端的状态，而且可以避免影响SDT过程传输的小包数据。
在一种可能的实现方式中，所述发起用于SDT的RRC连接恢复过程，包括：所述终端向网络设备发送RRC请求消息，所述终端的所述底层接收所述网络设备响应于所述RRC请求消息发送的第一响应消息；所述底层向上层指示第一信息，包括：基于所述第一响应消息，所述底层向所述上层指示所述第一信息。
在一种可能的实现方式中，所述用于SDT的RRC连接恢复过程包括：所述终端在随机接入过程中向网络设备发送RRC请求消息；所述底层向上层指示第一信息，包括：媒体接入控制MAC层向RRC层指示第一信息，所述第一信息指示竞争解决成功；所述基于所述第一信息，停止所述第一定时器，包括：所述RRC层接收到所述MAC层指示的所述第一信息，停止所述第一定时器。
在一种可能的实现方式中，所述终端向网络设备发送RRC请求消息，包括：所述终端在随机接入过程中向所述网络设备发送所述RRC请求消息，所述第一响应消息指示竞争解决成 功。
例如，第一响应消息为竞争解决消息。
在一种可能的实现方式中，所述用于SDT的RRC连接恢复过程包括：所述终端基于预配置的上行资源向网络设备发送RRC请求消息；所述第一信息指示所述RRC请求消息发送成功。
在一种可能的实现方式中，所述底层向上层指示第一信息，包括：媒体接入控制MAC层向RRC层指示第一信息；所述基于所述第一信息，停止所述第一定时器，包括：所述RRC层接收到所述MAC层指示的所述第一信息，停止所述第一定时器；或，所述底层向上层指示第一信息，包括：物理层向RRC层指示第一信息；所述基于所述第一信息，停止所述第一定时器，包括：所述RRC层接收到所述物理层指示的所述第一信息，停止所述第一定时器；或，所述底层向上层指示第一信息之前，所述方法还包括：物理层向MAC层指示第二信息，所述第二信息指示所述RRC请求消息发送成功；所述底层向上层指示第一信息，包括：所述MAC层接收到所述物理层指示的所述第二信息，向RRC层指示第一信息；所述基于所述第一信息，停止所述第一定时器，包括：所述RRC层接收到所述MAC层指示的所述第一信息，停止所述第一定时器。
在一种可能的实现方式中，所述终端向网络设备发送RRC请求消息，包括：所述终端基于预配置的上行资源向所述网络设备发送所述RRC请求消息，所述第一响应消息指示所述RRC请求消息发送成功。
在一种可能的实现方式中，所述发起用于SDT的RRC连接恢复过程，包括：发起所述用于SDT的RRC连接恢复过程，开启第二定时器。
在一种可能的实现方式中，所述停止所述第一定时器之后，所述方法还包括：在所述第二定时器运行时，若接收到RRC拒绝消息，停止所述第二定时器；若所述第一定时器未运行，将第一变量设置为第一值，所述第一变量为所述第一值指示有待定的RNA更新过程。
本申请中，若第一定时器在SDT过程中被停止，终端可以在SDT过程非正常结束(如第二定时器停止或者超时)时，将第一变量设置为第一值，以使后续可以继续触发RNAU，保证RNAU的正常执行。
在一种可能的实现方式中，所述停止所述第一定时器之后，所述方法还包括：在所述第二定时器运行时，若接收到RRC拒绝消息，停止所述第二定时器；若所述第一定时器未运行，执行所述用于RNAU的无线资源控制RRC连接恢复过程。
本申请中，若第一定时器在SDT过程中被停止，终端可以在SDT过程非正常结束(如第二定时器停止或者超时)时，再执行RNAU，保证RNAU的正常执行。
在一种可能的实现方式中，所述停止所述第一定时器之后，所述方法还包括：在所述第二定时器运行时，若接收到RRC拒绝消息，停止所述第二定时器；若所述第一定时器未运行，开启第三定时器，当所述第三定时器超时，若所述第二定时器未运行，执行所述用于RNAU的RRC连接恢复过程。
在一种可能的实现方式中，第三定时器的时长与第一定时器的时长相同。
在一种可能的实现方式中，第三定时器的时长与第一定时器的时长不同。
在一种可能的实现方式中，所述非无线资源控制RRC连接态为RRC非激活态；所述终端接收到RRC拒绝消息后，所述终端处于所述RRC非激活态。
本申请中，若第一定时器在SDT过程中被停止，终端可以在SDT过程非正常结束(如第二定时器停止或者超时)时，开启第三定时器，当第三定时器超时并且第二定时器未运行 时，再执行RNAU，保证RNAU的正常执行。
在一种可能的实现方式中，所述方法还包括：当所述第二定时器超时，若所述第一定时器未运行，将第一变量设置为第一值，所述第一变量为所述第一值指示有待定的RNA更新过程。
在一种可能的实现方式中，所述方法还包括：当所述第二定时器超时，若所述第一定时器未运行，执行所述用于RNAU的无线资源控制RRC连接恢复过程。
在一种可能的实现方式中，所述方法还包括：当所述第二定时器超时，若所述第一定时器未运行，开启第三定时器，当所述第三定时器超时，若所述第二定时器未运行，执行所述用于RNAU的RRC连接恢复过程。
在一种可能的实现方式中，第三定时器的时长与第一定时器的时长相同。
在一种可能的实现方式中，第三定时器的时长与第一定时器的时长不同。
在一种可能的实现方式中，所述非无线资源控制RRC连接态为RRC非激活态；所述第一定时器超时后，所述终端处于所述RRC非激活态。
在一种可能的实现方式中，所述方法还包括：在所述第二定时器运行时，若发生小区重选，停止所述第二定时器；接收第一服务小区的SIB1，所述第一服务小区为所述终端发生小区重选后的服务小区；当接收到所述第一服务小区的SIB1时，若所述第一服务小区属于配置的RNA，并且所述第一定时器未运行，将第一变量设置为第一值，所述第一变量为所述第一值指示有待定的RNA更新过程。
在一种可能的实现方式中，所述方法还包括：在所述第二定时器运行时，若发生小区重选，停止所述第二定时器；接收第一服务小区的SIB1，所述第一服务小区为所述终端发生小区重选后的服务小区；当接收到所述第一服务小区的SIB1时，若所述第一服务小区属于配置的RNA，并且所述第一定时器未运行，执行所述用于RNAU的无线资源控制RRC连接恢复过程。
在一种可能的实现方式中，所述方法还包括：在所述第二定时器运行时，若发生小区重选，停止所述第二定时器；接收第一服务小区的SIB1，所述第一服务小区为所述终端发生小区重选后的服务小区；当接收到所述第一服务小区的SIB1时，若所述第一服务小区属于配置的RNA，并且所述第一定时器未运行，开启第三定时器，当所述第三定时器超时，若所述第二定时器未运行，执行用于RNAU的RRC连接恢复过程。
在一种可能的实现方式中，第三定时器的时长与第二定时器的时长相同。
在一种可能的实现方式中，第三定时器的时长与第二定时器的时长不同。
在一种可能的实现方式中，所述非无线资源控制RRC连接态为RRC非激活态；所述终端发生小区重选后，所述终端处于所述RRC非激活态。
在一种可能的实现方式中，所述将第一变量设置为第一值之后，所述方法还包括：若接入禁止被缓和并且非接入NAS层没有请求RRC层进行RRC连接恢复，若所述第一变量为所述第一值，执行用于RNAU的RRC连接恢复过程。
在一种可能的实现方式中，所述非RRC连接态为RRC非激活态。
第四方面，本申请实施例提供了一种终端，包括收发器、处理器和存储器；上述存储器用于存储计算机程序代码，上述计算机程序代码包括计算机指令，上述处理器调用上述计算机指令以使上述用户设备执行本申请实施例第一方面至第三方面，以及第一方面至第三方面的任意一种实现方式提供的控制传输的方法。
第五方面，本申请实施例提供了一种通信装置，该装置可以为终端或终端中的芯片，该 通信装置包括处理单元，处理单元用于执行本申请实施例第一方面至第三方面，以及第一方面至第三方面的任意一种实现方式提供的控制传输的方法。
第六方面，本申请实施例提供了一种计算机存储介质，该计算机存储介质存储有计算机程序，该计算机程序包括程序指令，该程序指令被处理器执行时，用于执行本申请实施例第一方面至第三方面，以及第一方面至第三方面的任意一种实现方式提供的控制传输的方法。
第七方面，本申请实施例提供了一种计算机程序产品，当该计算机程序产品在通信设备上运行时，使得该通信设备执行本申请实施例第一方面至第三方面，以及第一方面至第三方面的任意一种实现方式提供的控制传输的方法。
第八方面，本申请实施例提供一种电子设备，该电子设备包括执行本申请任一实施例所介绍的方法或装置。上述电子设备例如为芯片。
附图说明
以下对本申请实施例用到的附图进行介绍。
图1是本申请实施例提供的一种通信系统的架构示意图；
图2是一种新无线接入NR的用户面的通信协议栈的架构示意图；
图3是一种NR的控制面的通信协议栈的架构示意图；
图4是一种用户设备UE的无线资源控制RRC状态的转换示意图；
图5-图10是本申请实施例提供的一些小包数据传输SDT的流程示意图；
图11是本申请实施例提供的一种控制传输的方法的流程示意图；
图12是本申请实施例提供的一种时序图；
图13-图17是本申请实施例提供的又一些控制传输的方法的流程示意图；
图18是本申请实施例提供的又一种时序图；
图19是本申请实施例提供的又一种控制传输的方法的流程示意图。
具体实施方式
下面将结合附图对本申请实施例中的技术方案进行清楚、详尽地描述。本申请实施例的实施方式部分使用的术语仅用于对本申请的具体实施例进行解释，而非旨在限定本申请。
首先介绍本申请涉及的相关装置和通信系统。
本申请实施例中，网络设备可以是一种用于发送或接收信息的设备，在一些实施例中，网络设备为接入网设备，例如但不限于：基站，用户设备(user equipment，UE)，无线接入点(access point，AP)，收发点(transmission and receiver point，TRP)，中继设备，或者具备基站的功能的其他网络设备等。其中，基站是一种部署在无线接入网(radio access network，RAN)中用于提供无线通信功能的设备。在不同的无线接入系统中，基站的名称可能不同，例如但不限于：全球移动通讯系统(global system for mobile communications，GSM)或码分多址接入(code division multiple access，CDMA)中的基站收发台(base transceiver station，BTS)，宽带码分多址(wideband code division multiple access，WCDMA)中的节点B(node B，NB)，长期演进(long term evolution，LTE)中的演进型基站(evolved node B，eNodeB)，还可以是第五代移动通信技术(5th generation mobile networks，5G)，即新无线接入(new radio，NR)中的下一代基站(g node B，gNB)，或者其他未来网络系统中的基站。
本申请实施例中，终端可以是具有无线通信功能的设备，在一些实施例中，终端为UE， 在一些实施例中，终端也可以被称为移动台、接入终端、用户代理等。示例性地，终端为手持设备、可穿戴设备、计算设备、便携式设备或车载设备等形式的终端。示例性地，终端具体为蜂窝电话、智能手机、智能眼镜、膝上型电脑、个人数字助理或无绳电话等设备。以下实施例以终端为UE为例进行说明。
请参见图1，图1是本申请实施例提供的一种通信系统的架构示意图。该通信系统可以但不限于是GSM，CDMA，宽带码分多址(wideband code division multiple access，WCDMA)，时分码分多址(time-division code division multiple access，TD-SCDMA)，通用移动通信系统(universal mobile telecommunications system，UMTS)，LTE，NR，或其他未来网络系统。
如图1所示，该通信系统可以包括核心网110、网络设备120和UE130。其中，核心网110可以连接至少一个网络设备120，网络设备120可以为至少一个UE130提供无线通信服务，UE130可以通过空中接口连接至少一个网络设备120。核心网110为该通信系统中的关键控制节点，主要负责信令处理功能，例如但不限于用于实现接入控制、移动性管理、会话管理等功能。在一些实施例中，网络设备120为基站。在NR中，核心网110可以称为5G核心网(5G Core，5GC)110，网络设备120可以称为gNB120。在一些实施例中，至少一个基站可以构成一个下一代无线接入网(next generation-radio access network，NG-RAN)节点。NG-RAN节点可以包括至少一个通过NG接口连接至5GC110的gNB120，并且，NG-RAN节点中至少一个gNB120可以通过Xn-C接口连接和通信。UE130可以通过Uu接口连接gNB120。
核心网110可以通过网络设备120向UE130发送下行数据，UE130也可以通过连接的网络设备120向核心网110发送上行数据。需要说明的是图1所示的核心网110、网络设备120和UE130的形态和数量仅用于示例，本申请实施例对此不作限定。
为了方便理解，本申请实施例主要以LTE和/或NR为应用的通信系统，网络设备为基站，一个NG-RAN包括至少一个基站为例进行说明。
接下来示例性地介绍NR的通信协议栈进行说明。
请参见图2，图2是一种NR的用户面协议栈的架构示意图。该用户面协议栈可以包括物理(physical，PHY)层、媒体接入控制(medium access control，MAC)层、无线链路控制(radio link control，RLC)层、分组数据汇聚协议(packet data convergence protocol，PDCP)层、服务数据适配协议(service data adaptation protocol，SDAP)层。
请参见图3，图3是一种NR的控制面协议栈的架构示意图。该控制面协议栈可以包括PHY层、MAC层、RLC层、PDCP层、无线资源控制(radio resource control，RRC)层、非接入层(non access stratum，NAS)。
相比LTE的用户面协议栈，NR的用户面协议栈新增了SDAP层，但其他层的架构是一致的，具体说明也类似，LTE较为成熟，不再赘述。
如图2和图3所示，PDCP层的下层包括RLC层。PDCP层可以处理控制面上的RRC消息，PDCP层可以进行IP包头压缩，以减少无线接口上传输的比特数。PDCP层还可以负责控制平面的加密、传输数据的完整性保护。在接收端，PDCP层执行相应的解密和解压缩操作。可以为每个无线承载配置一个PDCP实体。RLC层负责分割/级联、重传控制和重复检测等，RLC层为PDCP层提供服务，可以为每个无线承载配置一个RLC实体。MAC层控制逻辑信道的复用、混合自动重传请求的重传、上行链路和下行链路的调度等。MAC层以逻辑信道的形式为RLC层提供服务。PHY层负载管理编码/解码、调制/解调、多天线的映射以及其他类型的物理层功能，PHY层以传输信道的形式为MAC层提供服务。
如图2和图3所示，MAC层可以经由逻辑信道(logical channel，LCH)为较高层(如RLC层)提供服务。根据发送信息的类型，逻辑信道可以被分类为用于在控制面传输控制信息的控制信道和用于在用户面传输用户数据的业务信道。其中，控制信道可以包括但不限于公共控制信道(common control channel，CCCH)、专用控制信道(dedicated control channel，DCCH)。业务信道可以包括但不限于专用业务信道(dedicated traffic channel，DTCH)。CCCH可以一直存在，与RAN节点之间没有RRC连接的UE也可以使用CCCH传输信息。DCCH可以用于UE与RAN节点之间传输专用控制信息。DTCH可以用于UE与RAN节点之间传输用户数据。通常，DCCH和DTCH不会一直存在，而是在与UE连接的基站恢复UE上下文(UE context)之后，DCCH和DTCH才能用于UE和基站之间进行通信。其中，UE context包括但不限于终端的标识、无线承载(radio bearer，RB)相关配置、完整性保护和加密的安全相关配置、服务质量相关配置等。
RB可以为UE和RAN节点之间的连接格式集，可以包括物理信道、传输信道和逻辑信道的相关配置。RB可以分为用于在控制面传输控制信息的信令无线承载(signaling radio bearer，SRB)和用于在用户面传输用户数据的数据无线承载(data radio bearer，DRB)。一个DRB可以包括一个PDCP层的实体(简称PDCP实体)、一个RLC层的实体(简称RLC实体)和一个逻辑信道。
如图3所示，RRC层可以用于UE和基站之间传输RRC消息。例如但不限于，NR中的RRC恢复请求(RRCResumeRequest)可以用于UE请求恢复已经暂停的RRC连接，以此与基站传输数据。RRC层属于接入层(access stratum，AS)。
对于RRC层，目前存在三种UE的RRC状态，分别为RRC空闲(RRC IDLE)态、RRC非激活(RRC INACTIVE)态和RRC连接(RRC CONNECTED)态。UE在不同的RRC状态下，执行的操作大多不一样，这三种状态和转换过程具体可参见下图4的示例。
如图4所示，当UE处于RRC CONNECTED态时，UE与基站之间建立有RRC连接，在一些实施例中，当UE处于RRC CONNECTED态时，5GC和NG-RAN之间可以建立有UE的用户面和控制面的连接，NG-RAN和UE可以保留AS层的UE context，NG-RAN可以获取到UE所属小区，UE可以发送或接收单播数据，网络(例如NG-RAN)可以控制UE的移动性，示例性地，UE可以对与基站之间的信道进行测量，并可以将测量结果上报给基站，基站可以根据测量结果确定是否切换UE所属的小区。换句话说，在RRC CONNECTED态，UE和基站不仅能够正常的传输数据，基站也能够对UE进行管理。在一些实施例中，处于RRC CONNECTED态的UE若要向基站发送上行数据，需要根据时间提前(timing advance，TA)与基站保持同步。若处于RRC CONNECTED态的UE未获得上行同步，UE可以向基站发起随机接入(random access，RA)。其中，当UE的上行提前定时器(timing advance timer，TAT)保持运行时，UE保持上行同步。当UE的TAT超时时，UE的上行同步失效，如果UE需要向基站再发送上行数据时，则需要发起RA，通过RA获得新的TA。在一些实施例中，当UE处于RRC CONNECTED态时，基站可以为UE分配配置(configured grant，CG)资源。UE有数据传输需求时，可以使用CG资源向基站发送上行数据。在一些实施例中，基站可以通过RRC消息为UE配置CG资源，配置的信息可以包括时频位置和周期。相比动态调度传输资源，这种通过CG资源传输数据的方式可以减少信令开销和传输时延。
当没有上行资源但存在上行数据发送给基站时，处于RRC CONNECTED态的UE可以触发上报缓冲状态报告(buffer status reporting，BSR)，以请求基站调度上行资源。BSR可以用于指示UE的数据缓存区(buffer)中当前待传输的数据量。该数据量在不同时刻可以不同， 例如UE为智能手机，用户可以通过UE上安装的社交应用给其他用户发送消息，但用户在不同时刻发送的消息的类型和数量可以不同，有时候发送的消息可能仅为一条文字消息，有时候发送的消息可能包括多个视频。因此UE在不同时刻向基站发送的BSR的大小也可以不同。UE向基站发送BSR的资源(简称BSR资源)可以是基站动态调度给UE的。
当UE处于RRC IDLE态时，UE与基站之间未建立RRC连接。在一些实施例中，当UE处于RRC IDLE态时，UE可以进行公众陆地移动通信网络(public lands mobile network，PLMN)的选择，接收基站广播的系统信息，发生小区重选(cell re-selection)，由5GC发起的用于下行传输的被叫寻呼(Paging)，以及由NAS层配置用于核心网寻呼的不连续接收(discontinuous reception，DRX)等。
RRC INACTIVE态为NR中新增的RRC状态。在一些实施例中，对于数据传输不频繁的UE，基站通常会让该UE保持在RRC INACTIVE态。在一些实施例中，当UE处于RRC INACTIVE态时，UE可以进行PLMN的选择，接收基站广播的系统信息，发生小区重选，由NG-RAN发起被叫寻呼(Paging)，由NG-RAN管理基于RAN的通知区域(RAN-based Notification Area，RNA)，例如UE触发RNA更新(RNA update，RNAU)，以通知基站UE当前所处的RNA，由NG-RAN配置用于RAN寻呼的DRX，5GC和NG-RAN之间可以建立有UE的用户面和控制面的连接，NG-RAN和UE可以保留AS层的UE context，以及NG-RAN可以获取到UE所在的RNA。在一些实施例中，若UE与基站建立了RRC连接之后，UE进入RRC CONNECTED态。RRC CONNECTED态下的UE在预设时间段内与基站没有数据传输的需求，则基站可以指示UE进入RRCINACTIVE态。例如，基站可以向UE发送携带暂停指示的RRC释放(RRCRelease with suspend indication)消息，UE接收到RRCRelease with suspend indication消息之后，UE保留自身的上下文，进入RRC INACTIVE态。
其中，在RRC层的上述三种状态可以互相转换，如图4所示，在一些实施例中，UE处于RRC IDLE态或RRC INACTIVE态(可以统称为非RRC连接态)时，若需要进行数据传输，则可以执行RRC连接建立过程或者RRC连接恢复过程。例如，处于RRC IDLE态的UE可以向基站发送RRC建立请求(RRCSetupRequest)消息，然后接收基站发送的RRC建立(RRCSetup)消息，UE接收到RRCSetup消息后可以和基站建立RRC连接，进入RRC CONNECTED态。例如，处于RRC INACTIVE态的UE可以向基站发送RRCResumeRequest消息，然后接收基站发送的RRC恢复(RRCResume)消息，UE接收到RRCResume消息后可以进入RRC CONNECTED态。在另一些实施例中，UE处于非RRC连接态时，也可以响应于基站的寻呼消息执行RRC连接建立过程或者RRC连接恢复过程，例如核心网可以在有数据传输给UE时，指示基站向UE发送寻呼消息。
在一些实施例中，UE可以在基站的指示下，从RRC CONNECTED态进入RRC INACTIVE态或RRC IDLE态。在一些实施例中，UE后续无需进行数据时，基站可以将UE释放以使UE进入RRC INACTIVE态或RRC IDLE态，具体示例如下所示。
示例一，UE在基站的指示下，从RRC CONNECTED态进入RRC INACTIVE态。详细地，基站可以向UE发送带有暂停指示的释放消息，例如RRCRelease with suspend indication消息，以使UE进入RRC INACTIVE态。此时，UE与基站之间的RRC连接会被暂停，但至少有一个RAN节点保留了该UE的UE context。
示例二，UE在基站的指示下，从RRC CONNECTED态进入RRC IDLE态。详细地，基站可以向UE发送释放消息，例如RRC释放(RRCRelease)消息，以使UE进入RRC IDLE态。此时，UE与基站之间的RRC连接会被停止，RAN节点会删除该UE的UE context。
在一些实施例中，UE也可以在基站的指示下，从RRC INACTIVE态进入RRC IDLE态，例如处于RRC INACTIVE态的UE发送RRC连接恢复请求后，基站可以将UE释放以使UE进入RRC IDLE态。可以理解地，相比从RRC IDLE态进入RRC CONNECTED态，UE从RRC INACTIVE态进入RRC CONNECTED态的速度更快。
在一些实施例中，UE处于RRC IDLE态或RRC INACTIVE态时，若需要进行数据传输，可以执行RRC连接建立过程或者RRC连接恢复过程，以请求进入RRC CONNECTED态传输数据，其中，如果处于RRC IDLE态或RRC INACTIVE的UE没有发送RRCSetupRequest消息或者RRCResumeRequest消息的资源时，UE需要发起随机接入(random access，RA)过程。接下来示例性介绍RA。
在一些实施例中，UE可以从基站广播的系统信息中获取当前小区的RA配置，例如，该配置包括可用的随机接入前导(random access preamble)和发送随机接入前导的RA资源，例如发送随机接入前导的RA资源为UE发送随机接入前导的时频资源，也可以称为随机接入时机(random access occasion，RO)。在一些实施例中，RA可以包括4步随机接入(简称4-step RA)和2步随机接入(简称2-step RA)。基站可以在系统消息中广播4-step RA对应的RA配置和2-step RA对应的RA配置，也可以在系统消息中只广播4-step RA对应的RA配置，还可以在系统消息中只广播2-step RA对应的RA配置。
在一些实施例中，基站可以在系统消息中广播4-step RA对应的RA配置和2-step RA对应的RA配置。当UE未配置有非竞争随机接入(contention free random access，CFRA)的资源时，UE可以基于当前测量的参考信号接收功率(reference signal receiving power，RSRP)和预设的RSRP门限的相对大小，确定发起4-step RA或2-step RA。例如，当前测量的RSRP大于或等于预设的RSRP门限时，UE可以发起2-step RA。当前测量的RSRP小于预设的RSRP门限时，UE可以发起4-step RA。
其中，4-step RA的第三步中UE向基站发送的消息可以称为message 3，简称为msg3。在2-step RA的第一步中UE向基站发送的消息可以称为message A，简称msgA。在一些实施例中，上述msg3或msgA可以包括RRC消息。UE处于不同的RRC状态和在不同的业务场景下，该RRC消息可以不同。例如，处于RRC INACTIVE态的UE存在数据发送给基站时，UE向基站发送的msg3可以包括RRCResumeRequest消息，以此请求恢复已经暂停的RRC连接并进入RRC CONNECTED态与基站传输数据。
可以理解地，一般情况下，处于非RRC连接态的UE存在上行数据发送给基站，或，接收到基站发送的寻呼(Paging)消息，该寻呼消息用于基站指示存在下行数据发送给UE，UE需重新建立或恢复RRC连接并进入RRC CONNECTED态，在RRC CONNECTED态下再与基站传输数据。但是，上述方法比较适用于UE和基站之间传输的数据量较大的情况。若传输的数据包很小，可以称这类数据包为小包数据(small data)，UE切换状态的过程所需的信令甚至大于小包数据，从而导致UE不必要的功耗和信令开销。因此，有必要在UE处于非RRC连接态时将小包数据传输给基站，例如处于RRC INACTIVE态的UE有上行小包数据的传输需求时，可以将上行小包数据传输给基站。
本申请实施例中，小包数据可以但不限于包括数据量小于预设门限(例如基站指示的传输块的大小)的数据包，数据标签为小包数据的数据包，数据类型属于小包数据的数据包等。非小包数据的数据包可以称为大包数据，可以但不限于包括数据量大于或等于预设门限的数据包，数据标签为大包数据的数据包，数据类型属于大包数据的数据包等。其中，上述数据 标签和/或上述数据类型可以为UE和网络设备共同协商的。例如，数据标签可以包括大包数据和小包数据。例如，数据类型为心跳包的数据为小包数据，数据类型为文件、视频或音频的数据为大包数据。示例性地，小包数据为UE的应用程序(application，APP)的即时通讯消息，APP的心跳包或者APP的推送消息等，小包数据为可穿戴设备的周期性数据等，小包数据为物联网(internet of things，IoT)设备的业务数据等。
在一些实施例中，上述UE处于非RRC连接态时将小包数据传输给基站可以包括，UE在RA过程中传输small data，而无需进入RRC CONNECTED态后再传输small data，上述传输过程可以称为基于RA的小包数据传输(small data transmission，SDT)，简称RA-SDT。在一些实施例中，RA可以包括4-step RA和2-step RA，SDT也可以包括基于4-step RA的SDT(简称4-step SDT)和基于2-step RA的SDT(简称2-step SDT)，4-step SDT的过程示例可参见下图5和图6，2-step SDT的过程示例可参见下图7和图8。其中，RA-SDT的实现方式和RA类似，例如，UE可以从基站广播的系统信息中获取RA-SDT的配置，UE可以基于当前测量的RSRP和预设的RSRP门限的相对大小，确定发起4-step SDT或2-step SDT。
在另一些实施例中，上述UE处于非RRC连接态时将小包数据传输给基站还可以包括，UE通过预先分配的CG资源或预配置上行资源(preconfigured uplink resource，PUR)传输small data，而无需进入RRC CONNECTED态后再传输small data，上述传输过程可以称为基于CG的SDT，简称CG-SDT，具体过程示例可参见下图9和图10。
在一些实施例中，SDT存在多个不同的应用场景，可以根据应用场景使用不同实现方式的SDT，例如RA-SDT或CG-SDT。具体示例如下所示：
示例一：CG-SDT中，CG-SDT配置所指示的资源(例如CG资源或PUR)是基站通过专用控制信令下发给UE的，因此CG-SDT配置适用于该基站覆盖的小区中的UE，在一个小区中提供的CG-SDT的配置不能被另一个小区中的UE重用，如果UE移动到其他的网络设备覆盖范围内，则CG-SDT配置所指示的资源不能再使用，基于这样的特性例如可以应用于以下场景：对于IoT的应用，UE的移动性有限，且通常在同一小区建立所有连接以发送数据，而很少改变小区，因此IoT领域中的UE可以优先采用CG-SDT。
示例二：RA-SDT的配置相关的RA的配置可以由基站发送的系统信息提供，每当UE重新选择到新小区时，UE可以读取和应用系统信息广播的配置，基于这样的特性例如可以应用于以下场景：对于智能手机的即时通信消息等应用，UE的移动性比较强，UE可能会从一个基站的覆盖范围内移动到另一个基站的覆盖范围内。如果UE从基站A的覆盖范围移动到基站B的覆盖范围，处于基站B的覆盖范围内时，采用移动前基站A发送的CG-SDT配置所指示的资源进行SDT，则无法传输数据，由于RA-SDT中发送随机接入前导的资源是基站实时广播的，因此，对于移动性较强的UE，可以优先采用RA-SDT。
当然，UE到底采用CG-SDT还是RA-SDT也可以不受场景的限制，可以基于UE的实现确定采用哪种方式进行SDT。
示例性地，由于进行CG-SDT的资源是基站为UE专门配置的，因此UE进行CG-SDT的成功率较高。RA-SDT的随机接入资源是网络设备广播的，能够接收到广播消息的UE都可以在随机接入资源上发起RA-SDT，多个UE会竞争资源，可能会导致竞争失败的情形，因此，RA-SDT的成功率没有CG-SDT的成功率高，CG-SDT比RA-SDT可能有效。通常情况下，UE优先选择CG-SDT，UE选择CG-SDT也需要满足一定的条件，如果不满足条件，则UE可以选择RA-SDT。例如，UE当前所处的普通上行载波(normal uplink，NUL)载波或者辅助上行(supplementary uplink，SUL)载波覆盖的范围内是否有CG-SDT配置所指示 的资源，如果有CG-SDT配置所指示的资源，且CG-SDT配置所指示的资源中存在有效的资源的情况下，UE可以选择CG-SDT，否则选择RA-SDT。
可以理解地，基站可以先为UE配置用于承载数据的DRB，UE恢复上下文(包括DRB)后才可以传输数据。在一些实施例中，基站为UE配置的DRB可以包括用于承载小包数据的DRB(简称SDT DRB)，以及用于承载大包数据的DRB(简称非SDT DRB(non-SDT DRB))。只有通过SDT DRB承载的小包数据到达时，UE才可以发起SDT，若通过non-SDT DRB承载的大包数据到达时，UE无法发起SDT。UE发起SDT时，需要恢复UE上下文，可以包括SDT DRB。
在一些实施例中，SDT的状态可以通过第一定时器的状态来确定，第一定时器可以表示为T3XX，其中X为小于10的非负整数，第一定时器可以称为SDT失败检测定时器(SDT failure detection timer)，第一定时器可以为RRC层的定时器。
在一些实施例中，当UE发起用于SDT的RRC连接恢复过程时，可以开启第一定时器，在一些实施例中，当UE发起用于SDT的RRC连接恢复过程时，UE初始化该用于SDT的RRC连接恢复过程，可以开启第一定时器，在另一些实施例中，当UE发起用于SDT的RRC连接恢复过程时，UE向基站发送用于发起该用于SDT的RRC连接恢复过程的RRC请求消息时，可以开启第一定时器。在一些实施例中，第一定时器开启的条件包括：初始化用于SDT的RRC连接恢复过程。在另一些实施例中，第一定时器开启的条件包括：发送用于发起用于SDT的RRC连接恢复过程的RRC请求消息。例如，上述RRC请求消息为UE基于RA-SDT向基站发送的msg3或msgA中的RRC请求消息，又例如，上述RRC请求消息为UE基于CG-SDT向基站发送的RRC请求消息。
在一些实施例中，UE可以在接收到RRC响应消息，或者发生小区重选的情况下，停止第一定时器，在一些实施例中，停止第一定时器的条件可以包括接收到RRC响应消息或者发生小区重选，其中上述RRC响应消息例如为RRCResume消息、RRCSetup消息、RRCRelease消息、RRCRelease with suspend indication消息、RRC拒绝(RRCReject)消息或其他具有相同功能但第三代合作伙伴计划(3rd generation partnership project，3GPP)未标准化的RRC消息，其中UE接收到RRCRelease消息、RRCRelease with suspend indication消息或其他具有相同功能但3GPP未标准化的RRC消息的情况下，UE可以认为此次SDT成功，并停止第一定时器。UE接收到RRCResume消息、RRCSetup消息或其他具有相同功能但3GPP未标准化的RRC消息的情况下，UE可以认为此次SDT成功，并停止第一定时器，或者UE可以认为此次SDT成功并转入RRC CONNECTED态后继续进行数据传输，并停止第一定时器。UE接收到RRCReject消息或其他具有相同功能但3GPP未标准化的RRC消息的情况下，UE可以认为此次SDT失败，并停止第一定时器。
在一些实施例中，第一定时器开启到第一定时器超时的这段时间内，UE没有接收到基站发送的任何响应消息，例如竞争解决(contention resolution)消息、RRC响应消息或其他响应消息，则UE可以认为此次SDT失败并自动结束此次SDT。可以理解地，第一定时器可以避免UE向基站发送请求消息或者数据后，基站长时间未响应UE的情况。
接下来示例性介绍SDT的传输过程。
请参见图5，图5示例性示出一种用户面下4-step SDT过程的流程示意图。图5所示过程可以包括但不限于以下步骤：
S111：UE向基站发送random access preamble。
在一些实施例中，基站可以向UE发送广播消息，广播消息包括第一资源配置信息，第 一资源配置信息用于指示发送random access preamble的随机接入资源。可选地，第一资源配置信息具体可以指示用于发起正常随机接入的第一随机接入资源，可选地，第一资源配置信息具体可以指示用于在RA-SDT过程中发送random access preamble的第二随机接入资源。其中，random access preamble可以是UE按照特定的规则生成的，但是基站能够识别UE生成的random access preamble。
在一些实施例中，UE要进行RA-SDT发送的random access preamble可以与UE要发起正常RA而不进行RA-SDT的random access preamble不同。也就是说，基站可以利用不同的random access preamble来区别UE的意图，如UE的意图是为了进行RA-SDT或者为了发起RA。
在另一些实施例中，UE要进行RA-SDT发送的random access preamble也可以与UE要发起正常RA而不进行RA-SDT的random access preamble相同。
在一些实施例中，如果第一资源配置信息具体指示用于发起正常随机接入的第一随机接入资源，以及用于在RA-SDT过程中发送random access preamble的第二随机接入资源。则UE可以基于不同的意图在不同的随机接入资源上发送random access preamble，这样，基站可以利用不同的接收random access preamble的资源来区别UE的意图。例如UE意图发起RA时，在第一随机接入资源上发送random access preamble，基站通过第一随机接入资源接收random access preamble时，可以确定UE的意图为发起RA。UE意图进行RA-SDT时，在第二随机接入资源上发送random access preamble，基站通过第二随机接入资源random access preamble时，可以确定UE的意图为进行RA-SDT。
在另一些实施例中，UE要进行RA-SDT发送random access preamble的随机接入资源也可以与UE要发起正常RA而不进行RA-SDT的随机接入资源相同。
S112：响应于random access preamble，基站向UE发送随机接入响应(random access response，RAR)。
具体地，UE向基站发送random access preamble后，可以在RAR时间窗内监听物理下行控制信道(physical downlink control channel，PDCCH)，以接收基站发送的RAR。若UE在RAR时间窗内未接收到基站发送的RAR，UE可以确定此次RA失败。RAR用于为UE调度上行资源(uplink grant，UL grant)，以使UE可以在RAR调度的资源上发送msg3(包括S113中的RRC请求消息)。
在一些实施例中，RAR还可以包括临时小区无线网络临时标识(temporary cell radio network temporary identifier，TC-RNTI)和时间提前量(timing advance，TA)中的至少一种。TA用于UE获知上行同步。
S113：UE在RAR分配的资源上向基站发送上行小包数据和RRC请求消息。
在一些实施例中，RRC请求消息可以携带意图信息，该意图信息用于指示UE发送RRC请求消息的意图，如UE的意图是为了进行RA-SDT或者为了发起RA。示例性地，如果UE要发起RA-SDT发送的random access preamble与UE发起正常RA而不进行RA-SDT的random access preamble相同，或者UE要发起RA-SDT发送random access preamble的随机接入资源与UE要发起正常RA而不进行RA-SDT所传输random access preamble的随机接入资源相同，UE要进行RA-SDT发送的RRC请求消息可以携带意图信息，该意图信息用于指示UE想要发起RA-SDT的意图，而不是发起正常的RA的意图。
在另一些实施例中，UE可以在向基站发送msg3时发送BSR，基站可以通过UE发送的BSR获取到UE的意图，如UE的意图是为了进行RA-SDT或者为了发起RA。示例性地， UE要进行RA-SDT发送的random access preamble与UE要发起正常RA而不进行RA-SDT的random access preamble相同，UE要进行RA-SDT发送random access preamble的随机接入资源也可以与UE要发起正常RA而不进行RA-SDT的随机接入资源相同，如果UE要进行RA-SDT，可以在向基站发送msg3时发送BSR，该BSR用于指示小包数据的数据量，基站可以通过接收的BSR获取到UE的意图是发起RA-SDT，而不是发起正常的RA。
在一些实施例中，UE处于不同的RRC状态和在不同的业务场景下，msg3中的RRC请求消息可以不同。例如，处于RRC IDLE态的UE(可选地，此时UE可以存储有用于获取加密上述上行小包数据的密钥的配置信息等UE上下文，或者终端还可以未存储其上下文)发送的RRC请求消息可以包括RRC连接请求(RRCConnectionRequest)消息、RRC连接恢复请求(RRCConnectionResumeRequest)消息、RRC数据早传请求(RRCEarlyDataRequest)消息、RRCResumeRequest消息、RRCResumeRequest1消息、RRCSetupRequest消息或其他具有相同功能但3GPP未标准化的RRC消息。处于RRC INACTIVE态的UE发送的RRC请求消息可以是RRCConnectionRequest消息、RRCConnectionResumeRequest消息、RRCEarlyDataRequest消息、RRCResumeRequest消息、RRCResumeRequest1消息、RRCSetupRequest消息或其他具有相同功能但3GPP未标准化的RRC消息。
在一些实施例中，UE可以向基站发送上行小包数据和RRC请求消息，以发起用于4-step SDT的RRC连接恢复过程，在一些实施例中，用于发起用于4-step SDT的RRC连接恢复过程的RRC请求消息包括恢复原因(resumeCause)的信息元素(information element，IE)，resumeCause IE可以被设置为mo-data。
在一些实施例中，UE先初始化用于SDT的RRC连接恢复过程，然后再基于4-step SDT向基站发送RRC请求消息。在一些实施例中，UE初始化用于SDT的RRC连接恢复过程时，开启第一定时器，在另一些实施例中，UE基于4-step SDT向基站发送上行小包数据和RRC请求消息时，开启第一定时器。
在一些实施例中，msg3可以包括UE的标识，例如UE在核心网处的唯一标识。在一些实施例中，msg3可以包括UE上一个连接的基站的相关信息，例如非激活态无线网络临时标识(inactive temporary cell radio network temporary identifier，I-RNTI)。在一些实施例中，msg3可以包括用于加密和完整性保护的信息。
在一些实施例中，上述上行小包数据可以在DTCH上传输，上述RRC消息可以在CCCH上传输。MAC层可以将小包数据和RRC请求消息进行封装，通过PHY层发送给基站。
S114：基站接收到RRC请求消息后，向UE发送contention resolution消息。
在一些实施例中，基站接收到上行小包数据和RRC请求消息后，可以恢复UE上下文，并将接收到的上述上行小包数据发送给核心网。
在一些实施例中，contention resolution消息实际为竞争解决标识媒体接入层控制单元(contention resolution Identity MAC control element，contention resolution Identity MAC CE)，contention resolution Identity MAC CE可以指示UE竞争解决成功。在一些实施例中，UE可以判断contention resolution Identity MAC CE和S113发送的msg3是否一致，若一致则确定当前RA-SDT过程对应的竞争解决成功，或者确定当前RA-SDT过程成功。
S115：基站向UE发送RRC响应消息。
在一些实施例中，若核心网存在下行小包数据发送给UE，核心网可以向基站发送下行小包数据。然后，基站可以在发送RRC响应消息时将下行小包数据一起发送给UE。其中，下行小包数据可以在DTCH上传输，并与在DCCH上传输的RRC响应消息在MAC层多路复 用。
在一些实施例中，UE可以根据RRC响应消息确定上行小包数据是否传输成功，具体示例如下所示：
示例一：基站发送的RRC响应消息为RRC连接释放(RRCConnectionRelease)消息、RRC连接恢复(RRCConnectionResume)消息、RRC连接建立(RRCConnectionSetup)消息、RRCRelease消息、RRCResume消息或RRCSetup消息或其他具有相同功能但3GPP未标准化的RRC消息。UE接收到上述RRC响应消息的情况下，可以确定此次SDT传输成功，并停止第一定时器。
示例二：基站发送的RRC响应消息为RRC连接拒绝(RRCConnectionReject)消息、RRCReject消息或其他具有相同功能但3GPP未标准化的RRC消息。UE接收到上述RRC响应消息的情况下，可以确定此次SDT传输失败，并停止第一定时器。
在一些实施例中，UE可以根据RRC响应消息保持在当前的RRC状态或者进入其他RRC状态，具体示例如下所示：
示例一：若核心网没有进一步传输数据的需求，基站发送的RRC响应消息为RRC数据早传完成(RRCEarlyDataComplete)消息、RRCConnectionRelease消息、RRCRelease with suspend config消息、RRCRelease消息或其他具有相同功能但3GPP未标准化的RRC消息。UE接收到上述RRC响应消息的情况下，可以认为此次SDT传输过程成功，并停止第一定时器。并且，UE可以响应于上述RRC响应消息，保持在当前的非RRC连接态。可选地，上述RRC响应消息(如RRCRelease消息)可以包括UE下一次发起SDT时，UE加密小包数据的下一跳链计算(next hop chaining count，NCC)。
示例二：若核心网有进一步传输数据的需求，核心网可以触发连接建立的指示过程，基站发送的上述RRC响应消息为RRCConnectionSetup消息、RRCConnectionResume消息、RRCSetup消息、RRCResume消息或其他具有相同功能但3GPP未标准化的RRC消息。UE接收到上述RRC响应消息的情况下，可以认为此次SDT传输过程成功，并停止第一定时器。并且，UE可以响应于上述RRC响应消息，进入RRC CONNECTED态。
在一些实施例中，若UE没有接收到S115中的RRC响应消息，则认为S113中小包数据传输失败，例如，第一定时器超时，UE仍未接收到RRC响应消息，则认为S113中小包数据传输失败。若UE接收到S115中的RRC响应消息，则认为S113中的小包数据传输成功。也就是说，UE可以利用是否接收到RRC响应消息，判断S113中的小包数据是否传输成功。
需要说明的是，上述核心网是否有进一步传输数据的需求，不包括基站在S115中发送下行小包数据的需求。
请参见图6，图6示例性示出一种控制面下4-step SDT过程的流程示意图。图6所示过程可以包括但不限于以下步骤：
S121：UE向基站发送random access preamble。
S122：响应于random access preamble，基站向UE发送RAR。
具体地，S121-S122和图5的S111-S112类似，不再赘述。
S123：UE在RAR分配的资源上向基站发送携带上行小包数据的RRC请求消息。
具体地，S123和图5的S113类似，区别在于，上行小包数据不是和msg3一起在MAC层封装后发送的，而是携带于msg3中发送的，在一些实施例中，上述上行小包数据可以携带于msg3中并在CCCH上传输。例如，上述上行小包数据可以携带于RRCEarlyDataRequest消息包含的NAS层相关的IE(如专用信息NAS(dedicatedInfoNAS)IE)中，并在CCCH上 传输。
S124：基站接收到RRC请求消息后，向UE发送contention resolution消息。
具体地，S124和图5的S114类似，区别在于，基站接收到的RRC请求消息包括上行小包数据，在一些实施例中，基站可以通过上述携带上行小包数据的msg3向核心网发送上述上行小包数据。例如，基站可以通过转发上述msg3包含的NAS层相关的IE向核心网发送上述上行小包数据。
S125：基站向UE发送RRC响应消息。
具体地，S125和图5的S115类似，不再赘述。
图5和图6以UE在存在上行小包数据发送给基站的情况下执行S111和/或S121，即UE主动发起小包数据的传输过程为例进行说明。但在具体实现中，还存在UE在基站的指示下被动发起小包数据的传输过程的情况，例如，LTE中的终端终止(mobile terminated，MT)EDT(简称MT-EDT)。该情况的传输过程与图5和图6所示的传输过程类似，区别之处具体如下所述：
在S111之前，当核心网存在下行小包数据发送给UE，核心网可以向基站发送寻呼消息。在一些实施例中，该寻呼消息可以携带下行小包数据的数据量信息。在一些实施例中，基站可以向UE发送寻呼消息，UE基于当前测量的RSRP和预设的RSRP门限的相对大小，确定发起4-step SDT，示例性地，基站可以根据该寻呼消息触发MT-EDT，并向UE发送携带MT-EDT指示的寻呼消息，以使UE触发用于MT-EDT的MO-EDT。其中，与上述UE主动发起小包数据的传输过程不同的是：在S113中，UE可以仅发送RRC消息给基站，不发送上行小包数据，可选地，还可以携带触发MT-EDT的原因信息。相应地，基站可以接收核心网发送的下行小包数据，S115中基站可以向UE发送RRC响应消息和下行小包数据。
类似地，在S121之前，当核心网存在下行小包数据发送给UE，核心网可以向基站发送寻呼消息。在一些实施例中，该寻呼消息可以携带下行小包数据的数据量信息。在一些实施例中，基站可以向UE发送寻呼消息，UE基于当前测量的RSRP和预设的RSRP门限的相对大小，确定发起4-step SDT，其中，与上述UE主动发起小包数据的传输过程不同的是：S123中UE向基站发送的RRC消息可以未携带上行小包数据，可选地，还可以携带触发MT-EDT的原因信息。相应地，基站可以接收核心网发送的下行小包数据。S125中基站向UE发送的RRC响应消息中可以携带有下行小包数据。
请参见图7，图7示例性示出一种用户面下2-step SDT过程的流程示意图。图7所示过程可以包括但不限于以下步骤：
S211：UE向基站发送random access preamble，RRC请求消息和上行小包数据。
在一些实施例中，UE执行S211的传输资源可以通过基站广播的信息获得，例如，UE可以使用基站广播的RA资源发送random access preamble，UE可以使用基站广播的PUSCH资源发送RRC请求消息。
在一些实施例中，基站可以利用不同的random access preamble来区别UE的意图，在另一些实施例中，基站可以利用不同的接收random access preamble的资源来区别UE的意图，在另一些实施例中，基站可以通过UE发送的BSR获取到UE的意图，在另一些实施例中，RRC请求消息可以携带意图信息，该意图信息用于指示UE发送RRC请求消息的意图，如UE的意图是为了进行RA-SDT或者为了发起RA，具体可参见上图5中S111和S113的示例，不再赘述。
在一些实施例中，UE处于不同的RRC状态和在不同的业务场景下，上述msgA中的RRC请求消息可以不同，具体可参见上图5中msg3中的RRC请求消息的示例，不再赘述。
在一些实施例中，上述RRC请求消息和上行小包数据可以携带于物理上行共享信道(physical uplink share channel，PUSCH)负载中。上述上行小包数据可以在DTCH上传输，上述RRC消息可以在CCCH上传输。MAC层可以将小包数据和RRC请求消息进行封装，通过PHY层发送给基站。
在一些实施例中，UE可以向基站发送上行小包数据和RRC请求消息，以发起用于2-step SDT的RRC连接恢复过程，在一些实施例中，用于发起用于2-step SDT的RRC连接恢复过程的RRC请求消息中，resumeCause IE可以被设置为mo-data。
在一些实施例中，UE先初始化用于SDT的RRC连接恢复过程，然后再基于2-step SDT向基站发送RRC请求消息。在一些实施例中，UE初始化用于SDT的RRC连接恢复过程时，开启第一定时器，在另一些实施例中，UE基于2-step SDT向基站发送上行小包数据和RRC请求消息时，开启第一定时器。
其中，RRC请求消息和上行小包数据的说明可参见上图5的S113中RRC请求消息和上行小包数据的说明，不再赘述。
S212：基站接收到RRC请求消息后，向UE发送消息B。
在一些实施例中，基站接收到上行小包数据和RRC请求消息后，可以恢复UE上下文，并将接收到的上述上行小包数据发送给核心网。
在一些实施例中，在2-step RA的第二步中基站向UE发送的消息可以称为消息B(message B)，简称msgB。例如，msgB包括成功RAR(successRAR)或回退RAR(fallbackRAR)。
在一些实施例中，msgB包括successRAR，successRAR包括contention resolution字段，例如contention resolution MAC CE包括的内容，UE接收到successRAR，则确定当前RA-SDT过程对应的竞争解决成功，或者确定当前RA-SDT过程成功。可选地，successRAR中的contention resolution字段可以指示UE竞争解决成功，可选地，UE可以判断successRAR中的contention resolution字段和S211发送的msgA是否一致，若一致则确定当前RA-SDT过程对应的竞争解决成功，或者确定当前RA-SDT过程成功。在另一些实施例中，msgB包括fallbackRAR，UE接收到fallbackRAR后，再次向基站发送msg3和上行小包数据。
S213：基站向UE发送RRC响应消息。
在一些实施例中，若核心网存在下行小包数据发送给UE，核心网可以向基站发送下行小包数据。然后，基站可以在发送RRC响应消息时将下行小包数据一起发送给UE。
其中，RRC响应消息的说明可参见上图5的S115中RRC响应消息的说明，不再赘述。
请参见图8，图8示例性示出一种控制面下2-step SDT过程的流程示意图。图8所示过程可以包括但不限于以下步骤：
S221：UE向基站发送random access preamble，以及携带上行小包数据的RRC请求消息。
具体地，S221和图7的S211类似，区别在于，上行小包数据不是和msgA中的RRC请求消息一起发送的，而是携带于msgA中的RRC请求消息中发送的，在一些实施例中，携带上行小包数据的RRC请求消息可以携带于物理上行共享信道(physical uplink share channel，PUSCH)负载中，并可以在CCCH上传输。
S222：基站接收到RRC请求消息后，向UE发送msgB。
具体地，S222和图7的S212类似，区别在于，基站接收到的RRC请求消息包括上行小包数据，在一些实施例中，基站可以通过上述携带上行小包数据的RRC请求消息向核心网发 送上述上行小包数据。例如，基站可以通过转发携带上行小包数据的RRCResumeRequest消息向核心网发送上述上行小包数据。
S223：基站向UE发送RRC响应消息。
具体地，S223和图7的S213类似，不再赘述。
图7和图8以UE在存在上行小包数据发送给基站的情况下执行S211和/或S221，即UE主动发起小包数据的传输过程为例进行说明。但在具体实现中，还存在UE在基站的指示下被动发起小包数据的传输过程的情况。该情况的传输过程与图7和图8所示的传输过程类似，区别之处具体如下所述：
在S211之前，当核心网存在下行小包数据发送给UE，核心网可以向基站发送寻呼消息。在一些实施例中，该寻呼消息可以携带下行小包数据的数据量信息。在一些实施例中，基站可以向UE发送寻呼消息，UE基于当前测量的RSRP和预设的RSRP门限的相对大小，确定发起2-step SDT，示例性地，基站可以根据该寻呼消息触发MT-EDT，并向UE发送携带MT-EDT指示的寻呼消息，以使UE触发用于MT-EDT的MO-EDT。其中，与上述UE主动发起小包数据的传输过程不同的是：在S211中，UE可以仅发送random access preamble和RRC请求消息给基站，不发送上行小包数据，可选地，还可以携带触发MT-EDT的原因信息。相应地，基站可以接收核心网发送的下行小包数据，S213中基站可以向UE发送RRC响应消息和下行小包数据。
类似地，在S221之前，当核心网存在下行小包数据发送给UE，核心网可以向基站发送寻呼消息。在一些实施例中，该寻呼消息可以携带下行小包数据的数据量信息。在一些实施例中，基站可以向UE发送寻呼消息，UE基于当前测量的RSRP和预设的RSRP门限的相对大小，确定发起2-step SDT，其中，与上述UE主动发起小包数据的传输过程不同的是：S221中UE向基站发送的RRC消息可以未携带上行小包数据，可选地，还可以携带触发MT-EDT的原因信息。相应地，基站可以接收核心网发送的下行小包数据。S223中基站向UE发送的RRC响应消息中可以携带有下行小包数据。
不限于上述所示示例，在另一些实施例中，基站也可以将msgB和RRC响应消息一起发送给UE。
在一些实施例中，UE发起RA-SDT后，无法通过发送一次msg3或者msgA完成small data的传输，UE可以通过后续传输(subsequent transmission)完成后续small data的传输，其中subsequent transmission可以在UE接收到contention resolution之后，基站向UE发送RRC响应消息之前执行，例如上图5中S114和S115之间，上图7中S212和S213之间。具体示例如下所示：
示例一：UE当前发起的RA-SDT用于传输一个small data(例如一条即时通讯消息)，当UE发起4-step SDT时，基站在RAR中指示的UL grant小于传输small data和RRC请求消息的资源之和，或者当UE发起2-step SDT时，UE从广播消息中获取的传输资源小于传输random access preamble、small data和RRC请求消息的资源之和。在这种情况下，UE可以先通过msg3或者msgA发送small data的部分数据，然后通过subsequent transmission传输small data剩余的数据，例如基站可以在向UE发送contention resolution后，可以为UE动态调度上行资源来进行subsequent transmission。
示例二：UE当前发起的RA-SDT用于传输多个small data，当small data到达后，UE可以发起4-step SDT或者2-step SDT，通过msg3或msgA传输small data，但在此次SDT过程中，UE又获取新的small data，则UE可以通过subsequent transmission传输新的small data， 例如基站可以在向UE发送contention resolution后，可以为UE动态调度上行资源来进行subsequent transmission。
请参见图9，图9示例性示出一种用户面下CG-SDT过程的流程示意图。图9所示过程可以包括但不限于以下步骤：
S311：UE在预先配置的资源上向基站发送RRC请求消息和上行小包数据。
示例性地，预先配置的资源为配置资源类型一(configured grants type 1，CG Type 1)或PUR。其中，CG Type 1可以是由RRC层直接配置的上行资源，可以包括但不限于该上行资源的时频资源位置以及资源周期。
在一些实施例中，当基站和UE均支持CG-SDT，并且UE满足使用CG-SDT的条件时，UE可以执行S311而不必执行RA。使用CG-SDT的条件例如包括：UE处于非RRC连接态，UE有上行小包数据的传输需求，UE有预先配置的资源，满足RSRP条件，以及具有有效的TA。
在一些实施例中，UE确定使用CG-SDT的条件包括以下至少一项：
条件一：TAT运行，即UE的TA有效，UE与基站处于上行同步状态，可以表示CG-SDT有效，否则无效。
条件二：在TAT运行的前提下，UE当前的RSRP大于预设的第一RSRP门限(简称为RSRP 1)，可以表示CG-SDT有效。可选地，该RSRP1可以为UE可以发起SDT传输的RSRP。也就是说，UE当前的RSRP大于预设的RSRP 1表示UE离基站较近，信道质量较好，如果进行CG-SDT，则成功率较高，CG-SDT有效。UE当前的RSRP小于或等于预设的RSRP 1表示UE离基站较远，信道质量差，如果进行CG-SDT，则成功率较低。其中，RSRP 1可以为基站为CG-SDT和RA-SDT共同配置的。
条件三：在上次TA有效的预设时间段内，UE的RSRP的增加量或者减少量小于或等于预设的第二RSRP门限(简称为RSRP 2)，可以表示CG-SDT有效。也就是说，可以根据UE的RSRP的增加量或者减少量确定UE是否发生移动，如果RSRP的增加量或者减少量大于或等于RSRP 2，则表示相对于上次TA有效的时段内，UE发生移动或者移动距离较大，如果进行CG-SDT，则成功率较低，CG-SDT无效。如果RSRP的增加量或者减少量小于RSRP2，则表示相对于上次TA有效的时段内，UE没有移动或者移动距离较小，如果进行CG-SDT，则成功率较高，CG-SDT有效。
条件四：若基站在SUL和/或NUL上配置CG-SDT，则UE需要比较当前的RSRP与基站预设的第三RSRP门限(简称RSRP 3)，从而确定SUL上配置的CG-SDT有效还是NUL上配置的CG-SDT有效。可选地，假设SUL和NUL上均配置了CG-SDT，则UE将当前的RSRP与RSRP 3比较，若当前的RSRP小于RSRP 3则选择SUL上的CG-SDT，若当前的RSRP大于或等于RSRP 3则选择NUL上的CG-SDT。也就是说，基站在SUL和NUL上都配置了CG-SDT的情况下，如果UE当前的RSRP小于RSRP 3，则表示UE离基站较远，应采用SUL上配置的CG-SDT，也即SUL上的CG-SDT有效，NUL上的CG-SDT无效。如果UE当前的RSRP大于或等于RSRP 3，则表示UE离基站较近，应采用NUL上配置的CG-SDT，也即NUL上的CG-SDT有效，SUL上的CG-SDT无效。可选地，假设基站仅在SUL上配置CG-SDT，则UE将当前的RSRP与RSRP 3比较，若当前的RSRP小于RSRP 3则选择SUL上的CG-SDT，此时CG-SDT有效，若当前的RSRP大于或等于RSRP 3则无法使用CG-SDT，即SUL上的CG-SDT无效，也就是说基站配置了在SUL上的CG-SDT，UE离基站比较远的情况下，可 以利用SUL上的CG-SDT，否则SUL上的CG-SDT无效。可选地，假设基站仅在NUL上配置CG-SDT，则UE将当前的RSRP与RSRP 3比较，若当前的RSRP小于RSRP 3则无法使用CG SDT，若当前的RSRP大于或等于RSRP 3则选择NUL上的CGSDT，即NUL上的CG-SDT有效，也就是说基站配置了在NUL上的CG-SDT，UE离基站比较近的情况下，可以利用NUL上的CG-SDT，否则NUL上的CG-SDT无效。
条件五：UE处于基站覆盖的范围，且该基站为UE配置过用于CG-SDT的CG资源。
在一些实施例中，在S311之前，UE还可以向基站请求配置用于发起CG-SDT的预配置资源。例如，UE在RRC CONNECTED态向基站发送CG-SDT资源请求消息。CG-SDT资源请求消息用于向基站请求进行CG-SDT的配置。例如LTE中，UE向基站发送PUR请求配置信息(PURConfigurationRequest)消息。
可选地，UE可以在RRC CONNECTED态下的任意时刻可以向基站发送CG-SDT资源请求消息。可选地，UE在RRC CONNECTED态下可以确定未来可能会有小包数据，则可以向基站发送CG-SDT资源请求消息。可选地，UE处于RRC CONNECTED态，UE在预设的时间段内与基站没有传输数据的需求，UE确定自身可能即将进入非RRC连接态，为了在非RRC连接态传输小包数据，则UE可以向基站发送CG-SDT资源请求消息。
在一些实施例中，基站接收到请求配置信息(例如CG-SDT资源请求消息或PURConfigurationRequest消息)后，当基站指示UE从RRC CONNECTED态切换为非RRC连接态时，基站向UE发送的RRC响应消息可以携带有详细的CG-SDT的配置信息。例如，基站指示UE从RRC CONNECTED态切换为RRC INACTIVE态时，上述RRC响应消息为RRCRelease消息，RRCRelease消息可以携带详细的CG资源的配置信息。例如，基站指示UE从RRC CONNECTED态切换为RRC IDLE态时，上述RRC响应消息为RRCRelease消息，RRCRelease消息可以携带详细的PUR的配置信息。
不限于上述列举的情况，在另一些实施例中，基站为UE配置了CG-SDT后，可以向UE发送携带释放指示信息的RRC响应消息，以释放配置的CG-SDT。例如，RRCRelease消息可以携带CG资源的释放指示信息。例如，RRCConnectionRelease消息可以携带PUR的释放指示信息。
在另一些实施例中，UE也可以不向网络设备发送CG-SDT资源请求消息，网络设备可以直接为UE配置CG-SDT资源，例如网络设备可以参考UE历史的通信业务情况，为UE配置CG-SDT资源。
在一些实施例中，UE可以向基站发送上行小包数据和RRC请求消息，以发起用于CG-SDT的RRC连接恢复过程，在一些实施例中，用于发起用于CG-SDT的RRC连接恢复过程的RRC请求消息中，resumeCause IE可以被设置为mo-data。
在一些实施例中，UE先初始化用于SDT的RRC连接恢复过程，然后再基于CG-SDT向基站发送RRC请求消息。在一些实施例中，UE初始化用于SDT的RRC连接恢复过程时，开启第一定时器，在另一些实施例中，UE基于CG-SDT向基站发送上行小包数据和RRC请求消息时，开启第一定时器。
不限于上述示例的情况，在另一些实施例中，UE在进行CG-SDT的过程中可以仅发送小包数据，例如，对于CG-SDT配置所指示的资源是网络设备配置给UE的特有的资源，非共享资源，则UE进行CG-SDT的过程中可以在CG-SDT配置所指示的资源仅发送小包数据。这样，网络设备可以根据接收小包数据的资源识别出来发送小包数据的UE。又例如，若CG-SDT配置所指示的资源是网络设备配置给多个UE的共享资源，则UE进行SDT的过程 中可以在CG-SDT配置所指示的资源上发送小包数据和RRC请求消息，这样，网络设备可以利用RRC消息识别UE。
其中，RRC请求消息和上行小包数据的说明可参见上图5的S113中RRC请求消息和上行小包数据的说明，不再赘述。
S312：基站向UE发送反馈响应消息。
在一些实施例中，基站响应于UE发送的RRC请求消息，向UE发送反馈响应消息。在一些实施例中，反馈响应消息用于指示RRC请求消息传输成功，在一些实施例中，反馈响应消息用于指示RRC请求消息以及与RRC请求消息一起发送的上行小包数据传输成功，在一些实施例中，反馈响应消息用于指示上行小包数据传输成功。
在一些实施例中，反馈响应消息为层一确认消息(Layer 1 Acknowledgement，Layer 1 Ack)，即物理层ACK。
在一些实施例中，反馈响应消息为下行反馈信息(downlink feedback information，DFI)，即CG-DFI。
在一些实施例中，反馈响应消息为MAC层的MAC CE。
在一些实施例中，反馈响应消息为RRC层的RRC消息。
S313：基站向UE发送RRC响应消息。
在一些实施例中，若核心网存在下行小包数据发送给UE，核心网可以向基站发送下行小包数据。然后，基站可以在发送RRC响应消息时将下行小包数据一起发送给UE。
其中，RRC响应消息的说明可参见上图5的S115中RRC响应消息的说明，不再赘述。
在一些实施例中，RRC响应消息可以包括CG-SDT配置，例如，S311中的CG-SDT配置用于UE传输S311中的小包数据，S313中RRC响应消息指示的CG-SDT配置用于UE下次传输小包数据。
在一些实施例中，当S312中反馈响应消息为RRC层的RRC消息时，S312中的反馈响应消息与S313中的RRC响应消息可以为同一条消息，也就是说，上述反馈响应消息可以为上述RRC响应消息，即S312与S313为同一个步骤。
请参见图10，图10示例性示出一种控制面下CG-SDT过程的流程示意图。图10所示过程可以包括但不限于以下步骤：
S321：UE在预先配置的资源上向基站发送携带上行小包数据的RRC请求消息。
具体地，S321和图9的S311类似，区别在于，上行小包数据不是和RRC请求消息一起发送的，而是携带于RRC请求消息中发送的。
S322：基站向UE发送反馈响应消息。
S323：基站向UE发送RRC响应消息。
具体地，S322-S323和图9的S312-S313类似，不再赘述。
图9和图10以UE在存在上行小包数据发送给基站的情况下执行S311和/或S321，即UE主动发起小包数据的传输过程为例进行说明。但在具体实现中，还存在UE在基站的指示下被动发起小包数据的传输过程的情况。该情况的传输过程与图9和图10所示的传输过程类似，区别之处具体如下所述：
在S311之前，当核心网存在下行小包数据发送给UE，核心网可以向基站发送寻呼消息。在一些实施例中，该寻呼消息可以携带下行小包数据的数据量信息。在一些实施例中，基站可以向UE发送寻呼消息，以使UE发起CG-SDT。其中，与上述UE主动发起小包数据的传输过程不同的是：在S311中，UE可以仅发送RRC请求消息给基站，不发送上行小包数据， 可选地，还可以携带触发MT-EDT的原因信息。相应地，基站可以接收核心网发送的下行小包数据，S313中基站可以向UE发送RRC响应消息和下行小包数据。
类似地，在S321之前，当核心网存在下行小包数据发送给UE，核心网可以向基站发送寻呼消息。在一些实施例中，该寻呼消息可以携带下行小包数据的数据量信息。在一些实施例中，基站可以向UE发送寻呼消息，以使UE发起CG-SDT。其中，与上述UE主动发起小包数据的传输过程不同的是：S321中UE向基站发送的RRC消息可以未携带上行小包数据，可选地，还可以携带触发MT-EDT的原因信息。相应地，基站可以接收核心网发送的下行小包数据。S323中基站向UE发送的RRC响应消息中可以携带有下行小包数据。
可以理解地，处于RRC INACTIVE态的UE由NG-RAN管理RNA，以及NG-RAN可以获取到UE所在的RNA。
在一些实施例中，处于RRC INACTIVE态的UE可以被上一个服务基站配置一个RNA，其中一个RNA可以覆盖一个或多个小区，并且这一个RNA可以包含在核心网注册区域内。在一些实施例中，处于同一个RNA内的基站之间存在Xn连接。
在一些实施例中，基站可以通过向UE发送的RRC响应消息(如RRCRelease消息)中RAN通知区域信息(RAN-NotificationAreaInfo)IE，为UE配置RNA的相关信息，例如小区列表或者RAN区域(RAN area)列表。
接下来示例性介绍两种配置RNA的情况：
情况一：基站为UE配置小区列表，在一些实施例中，基站显式地向UE指示小区列表，其中该小区列表包括的一个或多个小区构成基站为UE配置的RNA。
情况二：基站为UE配置RAN area列表，在一些实施例中，该RAN area列表包括的一个或多个RAN area构成基站为UE配置的RNA。在一些实施例中，基站为UE配置RAN area标识(identity document，ID)(RAN area ID)。其中，每个RAN area是一个核心网(core network)跟踪区(CN tracking area)的子集或者等于一个CN tracking area。每个RAN area由一个RAN area ID标识，且每个RAN area包括一个跟踪区域码(tracking area code，TAC)，该TAC为该RAN area所属的tracking area。在一些实施例中，每个RAN area可以包括RAN区域码(RAN area code)，该RAN area code可以用于标识该RAN area在tracking area范围的区域。在一些实施例中，每个小区和对应的基站可以在系统信息中广播一个或多个RAN area IDs。
可以理解地，处于RRC INACTIVE态的UE可以触发RNA更新(RNA update，RNAU)，可选地，UE配置了RNA之后可以触发RNAU，以通知网络设备终端当前的RNA状态，例如终端当前所处的RNA，是否处于基站为UE配置的RNA内，UE当前所处小区等UE的移动性相关的状态。
接下来示例性介绍两种触发RNAU的情况：
情况一：UE可以周期性触发RNAU，触发RNAU可以由第二定时器控制，例如第二定时器为3GPP协议中38.321规定的T380，T380超时用于触发RNAU。在一些实施例中，基站向UE发送第一RRC响应消息时，为UE配置第二定时器。当UE接收到第一RRC响应消息时，UE开启第二定时器，在一些实施例中，第二定时器的开启条件包括UE接收到第一RRC响应消息，第一RRC响应消息例如为RRCRelease消息、带有暂停配置的RRC释放(RRCRelease with suspend config)消息或其他具有相同功能但3GPP未标准化的RRC消息。在一些实施例中，当第二定时器超时时，UE触发RNAU。在一些实施例中，当UE接收到基站发送的第二RRC响应消息时，UE停止第二定时器，在一些实施例中，第二定时器的停止 条件包括UE接收到第二RRC响应消息，第二RRC响应消息例如为RRCResume消息、RRCSetup消息或者RRCRelease消息或其他具有相同功能但3GPP未标准化的RRC消息。
情况二：RNAU由系统信息块(system information block，SIB)1触发，触发的RNAU和基站为UE配置的RNA有关。在一些实施例中，UE的服务小区不属于配置的RNA的情况下，UE可以触发RNAU，例如UE发生小区重选后的服务小区不属于配置的RNA时，UE可以触发RNAU，例如终端进行移动，发生小区重选。在一些实施例中，UE在服务小区(如小区重选后新的服务小区)读取了SIB1后，如果SIB1提供的小区不属于基站为UE配置的小区列表，或者SIB1提供的RAN area不属于基站为UE配置的RAN area列表，UE可以触发RNAU。例如，UE从SIB1中读取的小区标识，不属于RAN-NotificationAreaInfo IE中基站为UE配置的小区列表中包括的小区标识时，UE可以触发RNAU。例如，UE从SIB1中读取的小区的TAC，不属于RAN-NotificationAreaInfo IE中基站为UE配置的RAN area列表中包括的TAC，UE可以触发RNAU。
接下来示例性介绍执行RNAU的实现方式。
在一些实施例中，UE触发RNAU的情况下，可以发起用于RNAU的RRC连接恢复过程，在一些实施例中，UE发起用于RNAU的RRC连接恢复过程可以包括：UE的RRC层发起请求恢复被暂停的RRC连接的过程(requests the resume of a suspended RRC connection)。在一些实施例中，UE发起用于RNAU的RRC连接恢复过程可以包括：UE向基站发送RRC请求消息，例如RRCResumeRequest消息或RRCResumeRequest1等RRC恢复请求消息，其中RRC请求消息中的resumeCause IE可以被设置为rna-Update。
在一些实施例中，UE发起用于RNAU的RRC连接恢复过程还可以包括初始化该RRC连接恢复过程，具体可以包括：如果当前有紧急服务正在进行，UE可以选择接入类别(Access Category)为2，并将该RRC连接恢复过程中发送的RRC请求消息中的resumeCause IE设置为紧急(emergency)。如果当前无紧急服务正在进行，则UE可以选择Access Category为8。其中Access Category可以用于接入禁止检查(access barring check)，每个接入请求可以关联一个Access Category，以使基站可以控制UE的接入请求。在一些实施例中，接入请求可以为UE发起的RRC连接恢复请求。
在一些实施例中，在初始化RRC连接恢复过程中，UE选择了Access Category。然后，UE可以执行统一接入控制(unified access control，UAC)过程，然后判断接入尝试是否被禁止，例如每个接入尝试对应一个Access Category，例如该接入尝试针对发起用于RNAU的RRC连接恢复过程，此时Access Category为2或者Access Category为8，当接入尝试被禁止，UE无法发起用于RNAU的RRC连接恢复过程，当接入尝试未被禁止，UE可以发起用于RNAU的RRC连接恢复过程，具体情况如下所示：
可选地，如果接入尝试被禁止，UE可以将第一变量设置为第一值，并停止此次接入尝试。
可选地，如果接入尝试被禁止，UE可以开启定时器T390，例如，UE为该被禁止的接入尝试的Access Category开启对应的定时器T390。当该Access Category的T390运行时，UE认为该接入尝试被禁止，当该接入尝试的T390超时，例如该接入尝试的T390未运行，UE认为该Access Category的禁止被缓和，例如上述Access Category为2或Access Category为8。
其中，第一变量的取值为第一值或第二值，例如第一变量指示是否存在待定的RNA更新(pendingRNA-Update)，第一值为真(true)，第二值为假(false)。在一些实施例中，第一变量取值为第一值可以指示有待定的RNA更新过程。在一些实施例中，第一变量取值为第二值可以指示没有待定的RNA更新过程。在一些实施例中，第一变量取值为第一值可以指示 RNAU已被触发，但未成功执行(可理解为是未成功执行用于RNAU的RRC连接恢复过程)。
如果接入尝试未被禁止，则UE可以继续执行与该RRC连接恢复过程相关的初始化，例如应用默认的物理层配置、默认的SRB1配置、默认的MAC层配置等，并且UE可以将第一变量设置为第二值。然后，UE可以发起RRC请求消息的传输，例如重存RRC配置、重建SRB1的PDCP实体、恢复SRB1，并且UE可以将RRC请求消息传输至UE的底层(其中底层是相对RRC层而言的，例如为MAC层或物理层)，例如UE的RRC层执行上述初始化过程后，RRC层将RRC请求消息传输至MAC层，接下来由MAC层发送该RRC请求消息。在一些实施例中，处于非RRC连接态的UE没有配置传输资源，MAC层接收到RRC层发送的传输需求时，可以发起RA来发送用于RNAU的RRC请求消息，例如在上述msg3或上述msgA中发送该RRC请求消息。在另一些实施例中，处于非RRC连接态的UE有预先配置的资源，例如CG资源或PUR，预先配置的资源的说明和上图9-图10中预先配置的资源的说明类似。底层接收到上层发送的传输需求时，可以在预先配置的资源上发送用于RNAU的RRC请求消息。例如上述底层为MAC层，上述上层为RRC层。例如上述底层为物理层，上述上层为RRC层。例如上述底层为物理层，上述上层为MAC层，MAC层接收到RRC发送的传输需求后再向物理层指示传输需求。其中，上述用于RNAU的RRC请求消息中的resumeCause IE被设置为rna-Update。在一些实施例中，基站接收到UE发送的用于RNAU的RRC请求消息，可以获取到UE当前正在请求RNAU，从而可以获知UE当前所处状态，例如移动情况。
在一些实施例中，基站成功接收到UE发送的用于RNAU的RRC请求消息，基站可以在竞争解决成功后(例如向UE发送contention resolution消息后)向UE发送第三RRC响应消息，第三RRC响应消息例如为RRCRelease消息、RRCRelease with suspend indication消息、RRCResume消息或其他具有相同功能但3GPP未标准化的RRC消息。可选地，UE接收到第三RRC响应消息，可以认为此次RNAU成功。具体示例如下所示：
示例一：UE在当前基站(可称为新站)下执行RNAU，但是UE的上下文存储在上一个基站(可称为老站)中，老站可以将UE的上下文通过Xn接口发送至新站，新站可以在获得了UE的上下文后，向UE发送RRC响应消息，例如发送RRCRelease消息使UE进入RRC IDLE态，或者发送RRCRelease with suspend indication消息使UE进入RRC INACTIVE态，或者发送RRCResume消息使UE进入RRC CONNECTED态。
示例二：UE在当前基站(可称为新站)下发起RNAU，但是UE的上下文存储在上一个基站(可称为老站)中，老站未将UE的上下文发送至新站，此时UE的RRC状态由老站控制，老站可以通过Xn接口消息间接地向UE发送RRC响应消息，即将RRC响应消息发送给新站，再由新站转发该RRC响应消息，例如，转发RRCRelease消息使UE进入RRC IDLE态，或者转发RRCRelease with suspend indication消息使UE进入RRCINACTIVE态。
在另一些实施例中，基站向UE发送第四RRC响应消息，例如基站未成功接收到UE发送的用于RNAU的RRC请求消息的情况下，基站可以在竞争解决成功后向UE发送第四响应消息。第四RRC响应消息例如为RRCConnectionReject消息、RRCReject消息或其他具有相同功能但3GPP未标准化的RRC消息。可选地，UE接收到第四RRC响应消息，可以回到RRCINACTIVE态。可选地，UE接收到第四RRC响应消息，可以认为用于RNAU的RRC恢复请求被拒绝，可以将第一变量设置为第一值。
在一些实施例中，UE接收到第四RRC响应消息后，若第四RRC响应消息配置了等待时间(wait time)，则UE开启定时器T302，其中定时器T302的时长等于wait time。当定时器 T302运行时并且Access Category不为2或0，UE认为该接入尝试被禁止。当定时器T302超时时，若Access Category的T390未运行，UE认为该Access Category的禁止被缓和。需要说明的是，定时器T302禁止的是该UE的请求，未区分UE的Access Category。
在一些实施例中，UE当前发起用于RNAU的RRC连接恢复过程并选择了Access Category为8，若在初始化该用于RNAU的RRC连接恢复过程时，接入尝试未被禁止，UE不会开启Access Category为8的T390，则UE可以继续执行与该RRC连接恢复过程相关的初始化并发送用于RNAU的RRC连接恢复过程的RRC请求消息。若基站向UE发送配置了wait time的第四RRC响应消息，则UE开启定时器T302。当定时器T302超时，此时Access Category为8的T390未运行，UE认为该Access Category为8的禁止被缓和。
在一些实施例中，UE可以在当前RNAU已被触发，但未成功执行时，通过将第一变量设置为第一值来继续执行RNAU。示例性地，UE触发RNAU后，若接入尝试被禁止，或者在用于RNAU的RRC连接恢复过程中接收到第四RRC响应消息(如RRCReject消息)，UE可以将第一变量设置为第一值。在一些实施例中，在第一变量被设置为第一值的情况下，UE可以继续尝试发起用于RNAU的RRC连接恢复过程。在一些实施例中，如果针对于Access Category为8或者Access Category为2的禁止被缓和，并且上层(如NAS层)没有请求恢复RRC连接，例如上层(如NAS层)没有请求恢复用于传输数据的RRC连接，以及第一变量被设置为第一值，UE可以继续发起用于RNAU的RRC连接恢复过程。
目前，处于非RRC连接态的UE和基站进行SDT时，RNAU可能被触发，在这种情况下，终端可能停止当前进行的SDT，并执行RNAU，从而影响SDT的small data的传输，具体示例如下所示：
示例一：UE和基站进行RA SDT之前，UE接收到基站发送的RRCRelease消息，开启第二定时器(如T380)，然后UE发起用于SDT的RRC连接恢复过程，例如上图5和图6所示的4-step SDT，或上图7和图8所示的2-step SDT，其中第二定时器可以是在UE发送random access preamble之前开启。如果第二定时器是在UE接收到基站发送的contention resolution消息之前超时的，即RNAU是在UE接收到基站发送的contention resolution消息之前触发的，该情况可以理解为在当前用于SDT的RA运行过程中，一个新的用于RNAU的RA被触发了。在这种情况下，是否执行RNAU取决于UE实现，即UE实现决定继续当前用于SDT的RA过程，或者执行新的用于RNAU的RA。若UE执行新的用于RNAU的RA，可能导致上行小包数据和下行小包数据无法发送或者发送失败，例如和msg3或msgA一起发送的上行小包数据，和RRC响应消息一起发送的下行小包数据。如果第二定时器是在UE接收到基站发送的contention resolution消息之后超时的，即RNAU是在UE接收到基站发送的contention resolution消息之后触发的。在这种情况下，UE需丢弃当前运行的RA SDT过程，发起用于RNAU的RRC连接恢复过程，这样可能导致上行小包数据和下行小包数据无法发送或者发送失败，例如subsequent transmission需传输的上行小包数据和/或下行小包数据，和RRC响应消息一起发送的下行小包数据。
示例二：UE和基站进行CG-SDT之前，UE接收到基站发送的RRCRelease消息，开启第二定时器(如T380)，然后UE发起用于SDT的RRC连接恢复过程，例如上图9和图10所示的CG-SDT，其中第二定时器可以是在UE发送RRC请求消息和/或上行小包数据之前开启。如果第二定时器超时，UE需丢弃当前运行的CG-SDT过程，发起用于RNAU的RRC连接恢复过程，这样可能导致上行小包数据和下行小包数据无法发送或者发送失败，例如 subsequent transmission需传输的上行小包数据和/或下行小包数据，和RRC响应消息一起发送的下行小包数据。
本申请实施例提供了一种控制传输的方法，可以应用于通信系统，通信系统例如包括终端和网络设备，终端和网络设备进行SDT时，可以不触发RNAU，从而避免对small data的传输的影响，例如增大传输时延，后续再次发起SDT也会增加功耗和信令开销。其中，终端和网络设备进行SDT时，网络设备可以获取到终端所处的RNA，无需额外执行RNAU来通知网络设备终端当前的状态。
接下来介绍终端和网络设备进行SDT时，网络设备可以获取到终端所处的RNA的示例：示例一：终端此次发起SDT的基站和终端上一次接收到RRCRelease消息的基站相同，即终端在同一基站下接收到RRCRelease消息，并且发起用于SDT的RRC连接恢复过程。可选地，终端上一次接收到RRCRelease消息的基站可以是为终端配置RNA的基站，该基站可以通过RRCRelease消息为终端配置RNA的相关信息，即终端在同一基站下被配置RNA，以及发起SDT。该基站保存了终端的上下文。该基站可以获知终端所处的RNA，例如，该基站可以基于其保存的终端的上下文获知之前为终端配置的RNA，此时发起SDT的终端未移动至配置的RNA范围之外，因此该基站可以获知终端所处的RNA为上述配置的RNA。
示例二：终端此次发起SDT的基站(可称为新基站)和终端上一次接收到RRCRelease消息的基站(可称为旧基站)不同，即终端在新基站下发起用于SDT的RRC连接恢复过程。可选地，终端上一次接收到RRCRelease消息的旧基站可以是为终端配置RNA的基站，旧基站可以通过RRCRelease消息为终端配置RNA的相关信息。新基站可以获知终端所处的RNA，示例性地，新基站可以向旧基站获取终端的上下文，新基站可以基于获取的终端的上下文和/或旧基站的信息获知终端是否超出旧基站为终端配置的RNA范围内。例如，新基站从终端的上下文中获取的RNA配置不包括新基站对应的RNA列表或小区列表，则可以获知终端已超出上述配置的RNA范围内，否则可以获知终端未移动至上述配置的RNA范围之外。又例如，新基站对应的RNA列表不包括旧基站对应的RNA列表，或者新基站对应的小区列表不包括旧基站对应的小区列表，则可以获知终端已超出上述配置的RNA范围内，否则可以获知终端未移动至上述配置的RNA范围之外。
接下来基于上述说明对本申请实施例提供的控制传输的方法进行说明，该方法可以应用于图1所示的通信系统，该方法中的网络设备和终端可以是图1所示的网络设备120和UE130。
以下实施例以用户面协议栈下的传输过程为例进行说明。以下实施例中的第一定时器和第二定时器可参见上述第一定时器和第二定时器的说明。
在一种可能的实现方式中，终端处于非RRC连接态时，在满足第一预设条件时，执行用于RNAU的RRC连接恢复过程，用于RNAU的RRC连接恢复过程的说明可参见上述执行RNAU的实现方式中发起用于RNAU的RRC连接恢复过程的说明。
在一些实施例中，第一预设条件包括第二定时器超时并且第一定时器未运行，具体示例如下图11所示，其中第一预设条件为图11中的第一条件。在一些实施例中，第一预设条件包括终端接收到第一服务小区的SIB1，第一服务小区不属于配置的RNA，并且第一定时器未运行，具体示例如下图13所示，其中第一预设条件为图13中的第二条件。上述情况的表述示例如下所示：
示例一：终端处于RRC INACTIVE态时，如果第一定时器(如T3XX)未运行和第二定时器(如T380)超时，或者如果第一定时器(如T3XX)未运行和终端的服务小区不属于配置的RNA，终端可以发起RRC连接恢复过程，以及将用于发起该RRC连接恢复过程的RRC 请求消息中的resumeCause IE设置为rna-Update。
示例二：终端处于RRC INACTIVE态时，如果第二定时器(如T380)超时或者终端的服务小区不属于配置的RNA，若第一定时器(如T3XX)未运行，终端可以发起RRC连接恢复过程，以及将用于发起该RRC连接恢复过程的RRC请求消息中的resumeCause IE设置为rna-Update。
可选地，执行用于RNAU的RRC连接恢复过程可以包括上述示例中：发起RRC连接恢复过程，以及将用于发起该RRC连接恢复过程的RRC请求消息中的resumeCause IE设置为rna-Update。
请参见图11，图11是本申请实施例提供的一种控制传输的方法的流程示意图。该方法包括但不限于如下步骤：
S401：终端开启第二定时器。
在一些实施例中，S401为可选的步骤。
在一些实施例中，终端接收到第一RRC响应消息，开启第二定时器，在一些实施例中，第一RRC响应消息包括所述第二定时器，在一些实施例中，第一RRC响应消息包括所述第二定时器时长。第一RRC响应消息例如为RRCRelease消息、RRCRelease with suspend config消息或其他具有相同功能但3GPP未标准化的RRC消息。
S402：满足第一条件时，终端触发RNAU。
在一些实施例中，终端处于非RRC连接态时，在满足第一条件时，触发RNAU，可选地，该非RRC连接态为RRC INACTIVE态。
在一些实施例中，第一条件包括终端处于RRC INACTIVE态。
在一些实施例中，触发RNAU为执行用于RNAU的RRC连接恢复过程，可选地，执行用于RNAU的RRC连接恢复过程时，终端可以向网络设备发送RRC请求消息，该RRC请求消息中的resumeCause IE为rna-Update。
具体地，第一条件包括第二定时器超时并且第一定时器未运行，可选地，第一定时器未运行为未开启。
在一些实施例中，当第二定时器超时，终端可以判断第一定时器是否运行，如果第一定时器在运行中，终端不触发RNAU，如果第一定时器未运行，终端触发RNAU。
在一些实施例中，当第二定时器超时，以及第二定时器运行时终端没有SDT需求，终端可以触发RNAU，可选地，第一定时器未运行可以表征终端没有SDT需求，可选地，第二定时器运行时，第一定时器未运行，具体示例如下图12所示。
请参见图12，图12示例性示出一种时序图。
如图12所示，横轴为时间轴(t)，在第一时刻t 1，第二定时器开启(例如接收到第一RRC响应消息)，在第二时刻t 2，第二定时器超时，t 1<t 2。第二定时器在第一时刻和第二时刻之间运行，第一时刻和第二时刻之间第一定时器未运行，第一时刻和第二时刻之间第一定时器未开启。在第二时刻，第二定时器超时并且第一定时器未运行，此时终端可以触发RNAU。
可选地，上述用于SDT的RRC连接恢复过程可以包括：发起RRC连接恢复过程，以及将用于发起该RRC连接恢复过程的RRC请求消息中的resumeCause IE设置为mo-data。
请参见图13，图13是本申请实施例提供的又一种控制传输的方法的流程示意图。该方法包括但不限于如下步骤：
S501：终端开启第一定时器。
在一些实施例中，S501为可选的步骤。
在一些实施例中，终端发起用于SDT的RRC连接恢复过程，开启第一定时器，可选地，终端向网络设备发送RRC请求消息和/或上行小包数据时，开启第一定时器，例如上图5-图8所示流程中，终端基于RA-SDT向网络设备发送msg3或msgA时，开启第一定时器，例如上图9-图10所示流程中，终端基于CG-SDT向网络设备发送RRC请求消息和/或上行小包数据时，开启第一定时器。
S502：终端发生小区重选。
在一些实施例中，S502为可选的步骤。
在一些实施例中，终端和网络设备进行SDT过程中，发生小区重选，在一些实施例中，在第一定时器运行时，终端发生小区重选，停止第一定时器。
在一些实施例中，终端发生小区重选，从第一小区切换为第二小区，即终端发生小区重选后的服务小区为第二小区，后续称为第一服务小区，在一些实施例中，终端的第一服务小区不属于配置的RNA，其中该RNA为终端发生小区重选之前网络设备为终端配置的。
在一些实施例中，终端发生小区重选后，接收当前服务小区的SIB1，根据该SIB1确定第一服务小区，该SIB1指示第一服务小区，在一些实施例中，终端根据该SIB1确定第一服务小区不属于配置的RNA，其中该RNA为终端发生小区重选之前网络设备为终端配置的，具体示例如下所示：
示例一：终端从SIB1中读取第一服务小区的小区标识，当读取的第一服务小区的小区标识不属于RAN-NotificationAreaInfo IE中网络设备为终端配置的小区列表中包括的小区标识时，终端确定第一服务小区不属于配置的RNA。
示例二：终端从SIB1中读取第一服务小区的TAC，当读取的第一服务小区的TAC不属于RAN-NotificationAreaInfo IE中网络设备为终端配置的RAN area列表中包括的TAC时，终端确定第一服务小区不属于配置的RNA。
在一些实施例中，终端发生小区重选后，终端处于非RRC连接态，可选地，该非RRC连接态为RRC INACTIVE态。
S503：满足第二条件时，终端触发RNAU。
在一些实施例中，终端处于非RRC连接态时，在满足第二条件时，触发RNAU，可选地，该非RRC连接态为RRC INACTIVE态。
在一些实施例中，第二条件包括终端发生小区重选后处于RRC INACTIVE态。
在一些实施例中，触发RNAU为执行用于RNAU的RRC连接恢复过程，可选地，执行用于RNAU的RRC连接恢复过程时，终端可以向网络设备发送RRC请求消息，该RRC请求消息中的resumeCause IE为rna-Update。
可选地，第二条件包括终端接收到第一服务小区的SIB1，第一服务小区不属于配置的RNA，并且第一定时器未运行。在一些实施例中，第一服务小区为终端发生小区重选后的服务小区，在一些实施例中，第一服务小区为终端发生小区重选后接收到的SIB1指示的小区，终端根据第一服务小区的SIB1确定第一服务小区不属于配置的RNA，具体示例可参见S502。
在一些实施例中，终端没有SDT需求时发生小区重选，可选地，第二条件中的第一定时器未运行为第一定时器未开启，可选地，第一定时器未运行可以表征终端没有SDT需求。
在另一些实施例中，终端进行SDT过程中发生小区重选，可选地，终端进行SDT过程中第一定时器运行，第一定时器运行时发生小区重选，可选地，第二条件中的第一定时器未运行为第一定时器停止，可选地，终端发生小区重选时，停止第一定时器，可选地，终端发生小区重选后，终端处于RRC INACTIVE态。
在一些实施例中，第二条件还包括终端在第一服务小区不可以进行SDT过程。可选地，终端在第一服务小区不可以进行SDT过程为终端不可以在第一服务小区继续之前的SDT过程，例如终端发生小区重选后，不可以继续S501中发起的用于SDT的RRC连接恢复过程。可选地，终端在第一服务小区不可以进行SDT过程为终端不可以在第一服务小区发起新的SDT过程，例如终端发生小区重选后，不可以为S501中发起的用于SDT的RRC连接恢复过程继续发起新的SDT过程，或者不可以为新获取的small data发起新的SDT过程。可选地，终端在第一服务小区不可以进行SDT过程为终端在第一服务小区没有SDT相关的配置信息，例如，第一服务小区不支持SDT，可选地，第一服务小区不支持SDT包括第一服务小区未在系统信息中广播SDT的相关配置。又例如，第一服务小区不支持RA-SDT和/或CG-SDT。
在一些实施例中，小区重选后终端接收到当前服务小区的SIB1，该SIB1指示的第一服务小区不属于配置的RNA时，终端可以判断第一定时器是否运行。如果第一定时器运行，终端不触发RNAU，继续进行SDT，可选地，第一定时器运行为第一定时器继续运行，终端可以在服务小区继续之前的SDT过程，例如终端发生小区重选后，第一定时器继续运行，终端可以在服务小区继续S501中发起的用于SDT的RRC连接恢复过程。可选地，第一定时器运行为第一定时器开启，终端可以在服务小区发起新的用于SDT的RRC连接恢复过程，例如终端发生小区重选后，发起新的用于SDT的RRC连接恢复过程，开启第一定时器。如果第一定时器未运行，终端触发RNAU，可选地，该RNAU是由SIB1触发的。
在一些实施例中，终端进行SDT时，第二定时器超时，终端可以判断第一定时器是否运行。如果第一定时器运行，终端不触发RNAU，继续进行SDT过程。第二定时器超时后，终端发生小区重选，停止第一定时器，终端处于RRC INACTIVE态。终端可以在满足第二条件时，执行用于RNAU的RRC连接恢复过程。
在另一些实施例中，终端发生小区重选后，处于RRC IDLE态，则终端不触发RNAU。在另一些实施例中，终端发生小区重选后，可以在第一服务小区进行SDT过程，则终端不触发RNAU，进行SDT过程。可选地，终端可以在第一服务小区进行SDT过程的情况和上述终端在第一服务小区不可以进行SDT过程相反，具体可参见上述说明。
可以理解地，相比上述示例的两种触发RNAU的情况，本申请实施例增加了触发条件：第一定时器未运行，也就是说，终端没有SDT需求或者进行的SDT过程结束后，才可以触发RNAU，第一定时器运行时(如进行SDT过程中)，不会触发RNAU，其中进行SDT时，网络设备可以获取到终端所处的RNA，不执行RNAU不仅不会影响网络设备获取终端的状态，而且可以避免影响SDT过程传输的小包数据，例如避免增加传输时延，后续重新发起SDT增加不必要的信令开销和功耗等。
在一种可能的实现方式中，终端接收RRC拒绝消息，若第二定时器未运行，终端可以将第一变量设置为第一值，第一变量为第一值指示有待定的RNAU，可选地，第一变量的取值为第一值或第二值，例如第一变量指示是否存在pendingRNA-Update，第一值为true，第二值为false。第一变量和第一值的说明可参见上述执行RNAU的实现方式中第一变量和第一值的说明，具体示例如下图14所示。
请参见图14，图14是本申请实施例提供的又一种控制传输的方法的流程示意图。该方法包括但不限于如下步骤：
S601：终端开启第二定时器。
在一些实施例中，S601为可选的步骤，S601和图11的S401类似。
S602：终端开启第一定时器。
在一些实施例中，S602为可选的步骤，S602和图13的S501类似。
在一些实施例中，S601和S602的执行顺序可以是S601先执行，S602后执行，也可以是S602先执行，S601后执行。
S603：网络设备向终端发送RRCReject消息。
在一些实施例中，S603为可选的步骤。
在一些实施例中，第一定时器运行时，终端接收到RRCReject消息，停止第一定时器。
在一些实施例中，终端接收到RRCReject消息，处于RRC INACTIVE态。
在一些实施例中，终端向网络设备发起用于SDT的RRC连接恢复过程时，终端向网络设备发送RRC请求消息，上述RRCReject消息是网络设备响应于上述RRC请求消息发送的。上述RRC请求消息例如为RRCResumeRequest消息或RRCResumeRequest1等RRC恢复请求消息。
S604：若第二定时器未运行，终端将第一变量设置为第一值。
在一些实施例中，终端接收到RRCReject消息，处于非RRC连接态，可选地，该非RRC连接态为RRC INACTIVE态。
在一些实施例中，终端接收到RRCReject消息，认为此次SDT过程失败(被拒绝)，终端处于RRC INACTIVE态，终端仍需进行周期性的RNAU，但由于此时第二定时器未运行，因此终端可以将第一变量设置为第一值。
在一些实施例中，如果终端接收到RRCReject消息后处于RRC INACTIVE态，并且第二定时器未运行，终端可以将第一变量设置为第一值。
在一些实施例中，终端接收到RRCReject消息，且该RRCReject消息配置了wait time，此时终端可以开启定时器T302，可选地，该定时器T302运行时UE的RRC连接恢复过程被禁止。当该定时器T302超时，UE被禁止的RRC连接恢复过程被缓和，若此时上层(如NAS层)没有请求恢复RRC连接，则UE可以再次发起RRC连接恢复过程，例如上层(如NAS层)没有请求恢复用于传输数据的RRC连接，以及第一变量被设置为第一值，UE可以继续发起用于RNAU的RRC连接恢复过程。
在一些实施例中，终端进行SDT过程中(如接收到RRCReject消息之前)，第二定时器超时，终端可以判断第一定时器是否运行。如果第一定时器运行，终端不触发RNAU，继续进行SDT过程。第二定时器超时后，终端接收到RRCReject消息，停止第一定时器，终端处于RRC INACTIVE态。若第二定时器未运行，终端可以将第一变量设置为第一值。可选地，第二定时器未运行为第二定时器超时之后不运行。
在另一些实施例中，终端接收到RRCReject消息，处于RRC IDLE态，则终端不触发RNAU，也不将第一变量设置为第一值。
不限于图14示例的RRC拒绝消息，在另一些实施例中，也可以是RRCConnectionReject消息或其他具有相同功能但3GPP未标准化的RRC消息。
不限于图14所示示例，在另一些实施例中，终端接收RRC拒绝消息，若第二定时器未运行，终端可以直接执行用于RNAU的RRC连接恢复过程，具体示例和图14类似，区别在于将图14中将第一变量设置为第一值替换为执行用于RNAU的RRC连接恢复过程，例如终端的RRC层执行用于RNAU的RRC连接恢复过程。可选地，终端接收到RRCReject消息，且该RRCReject消息未配置wait time，终端执行用于RNAU的RRC连接恢复过程，例如终端的RRC层直接执行用于RNAU的RRC连接恢复过程。
在另一些实施例中，终端也可以先将第一变量设置为第一值，然后终端执行用于RNAU的RRC连接恢复过程，例如终端的RRC层直接执行用于RNAU的RRC连接恢复过程。
在另一些实施例中，终端接收RRC拒绝消息，若第二定时器未运行，终端可以开启第三定时器，当第三定时器超时，若第一定时器未运行，终端执行用于RNAU的RRC连接恢复过程，具体示例和图14类似，区别在于将图14中第一变量设置为第一值替换为开启第三定时器。可选地，该方法还包括：当第三定时器超时，若第一定时器未运行，终端执行用于RNAU的RRC连接恢复过程。
可选地，第三定时器与第二定时器相同，例如，第三定时器的时长等于第二定时器的时长。例如第三定时器为T380。
可选地，第三定时器与第二定时器不同，例如，第三定时器的时长不等于第二定时器的时长。例如第三定时器时长小于第二定时器的时长，例如第三定时器时长单位为毫秒或秒。
可选地，第三定时器运行期间，终端可以等待NAS层是否有数据传输需求，例如NAS是否触发RRC层发起连接恢复过程。若NAS层有数据传输需求并且触发RRC层发起连接恢复过程，则终端将发起用于数据传输的RRC连接恢复过程，而不执行用于RNAU的RRC连接恢复过程，上述用于数据传输的RRC连接恢复过程包括用于SDT和用于非SDT的RRC连接恢复过程。
在一些实施例中，
1>else if RRCReject is received in response to an RRCResumeRequest or an RRCResumeRequest1：
2>if resume is triggered due to an SDT procedure,and
2>if T380 expires：
3>set the variable pendingRNA-Update to true.
在一些实施例中，如果终端接收到响应于RRCResumeRequest消息或RRCResumeRequest1消息的RRCReject消息，若恢复是基于SDT过程触发的，并且第二定时器超时，终端可以将第一变量设置为第一值，其中终端可以通过发送RRCResumeRequest消息或RRCResumeRequest1消息请求上述恢复。可选地，上述恢复为用于SDT的RRC连接恢复过程。
在一种可能的实现方式中，当第一定时器超时，若第二定时器未运行，终端可以将第一变量设置为第一值，第一变量为第一值指示有待定的RNAU，第一变量和第一值的说明可参见上述执行RNAU的实现方式中第一变量和第一值的说明，具体示例如下图15所示。
请参见图15，图15是本申请实施例提供的又一种控制传输的方法的流程示意图。该方法包括但不限于如下步骤：
S701：终端开启第二定时器。
在一些实施例中，S701为可选的步骤，S701和图11的S401类似。
S702：终端开启第一定时器。
在一些实施例中，S702为可选的步骤，S702和图13的S501类似。
在一些实施例中，S701和S702的执行顺序可以是S701先执行，S702后执行，也可以是S702先执行，S701后执行。
S703：当第一定时器超时，若第二定时器未运行，终端将第一变量设置为第一值。
在一些实施例中，第一定时器超时后，终端处于非RRC连接态，可选地，该非RRC连 接态为RRC INACTIVE态，在一些实施例中，终端处于RRC INACTIVE态时，向网络设备发起用于SDT的RRC连接恢复过程，开启第一定时器。第一定时器超时后，终端仍然处于RRC INACTIVE态。
在一些实施例中，第一定时器超时，终端处于RRC INACTIVE态，终端仍需进行周期性的RNAU，但由于此时第二定时器未运行，因此终端可以将第一变量设置为第一值。
在一些实施例中，如果第一定时器超时后终端处于RRC INACTIVE态，并且第二定时器未运行，终端将第一变量设置为第一值。
在一些实施例中，终端进行SDT过程中(如第一定时器超时之前)，第二定时器超时，终端可以判断第一定时器是否运行。如果第一定时器运行，终端不触发RNAU，继续进行SDT过程。第二定时器超时后，若第一定时器超时，终端处于RRC INACTIVE态。若第二定时器未运行，终端可以将第一变量设置为第一值。可选地，第二定时器未运行为第二定时器超时之后不运行。
在另一些实施例中，第一定时器超时，终端处于RRC IDLE态，则终端不触发RNAU，也不将第一变量设置为第一值。
不限于图15所示示例，在另一些实施例中，当第一定时器超时，若第二定时器未运行，终端可以直接执行用于RNAU的RRC连接恢复过程，具体示例和图15类似，区别在于将图15中将第一变量设置为第一值替换为执行用于RNAU的RRC连接恢复过程，例如终端的RRC层执行用于RNAU的RRC连接恢复过程。
在另一些实施例中，终端也可以先将第一变量设置为第一值，然后终端执行用于RNAU的RRC连接恢复过程，例如终端的RRC层直接执行用于RNAU的RRC连接恢复过程。
在另一些实施例中，当第一定时器超时，若第二定时器未运行，终端可以开启第三定时器，当第三定时器超时，若第一定时器未运行，终端执行用于RNAU的RRC连接恢复过程，具体示例和图15类似，区别在于将图15中将第一变量设置为第一值替换为开启第三定时器。可选地，该方法还包括：当第三定时器超时，若第一定时器未运行，终端执行用于RNAU的RRC连接恢复过程。
可选地，第三定时器与第二定时器相同，例如，第三定时器的时长等于第二定时器的时长。例如第三定时器为T380。
可选地，第三定时器与第二定时器不同，例如，第三定时器的时长不等于第二定时器的时长。例如第三定时器时长小于第二定时器的时长，例如第三定时器时长单位为毫秒或秒。
可选地，第三定时器运行期间，终端可以等待NAS层是否有数据传输需求，例如NAS是否触发RRC层发起连接恢复过程。若NAS层有数据传输需求并且触发RRC层发起连接恢复过程，则终端将发起用于数据传输的RRC连接恢复过程，而不执行用于RNAU的RRC连接恢复过程，上述用于数据传输的RRC连接恢复过程包括用于SDT和用于非SDT的RRC连接恢复过程。
在一种可能的实现方式中，当接收到第二服务小区的SIB1时，若第二服务小区属于配置的RNA，并且第二定时器未运行，终端可以将第一变量设置为第一值，第一变量为第一值指示有待定的RNAU，第一变量和第一值的说明可参见上述执行RNAU的实现方式中第一变量和第一值的说明，具体示例如下图16所示。
请参见图16，图16是本申请实施例提供的又一种控制传输的方法的流程示意图。该方法包括但不限于如下步骤：
S801：终端开启第二定时器。
在一些实施例中，S801为可选的步骤，S801和图11的S401类似。
S802：终端开启第一定时器。
在一些实施例中，S802为可选的步骤，S802和图13的S501类似。
在一些实施例中，S801和S802的执行顺序可以是S801先执行，S802后执行，也可以是S802先执行，S801后执行。
S803：终端发生小区重选。
在一些实施例中，S803为可选的步骤。
在一些实施例中，终端和网络设备进行SDT过程中，发生小区重选，在一些实施例中，在第一定时器运行时，终端发生小区重选，停止第一定时器。
在一些实施例中，终端发生小区重选，从第三小区切换为第四小区，即终端发生小区重选后的服务小区为第四小区，后续称为第二服务小区，在一些实施例中，终端的第二服务小区属于配置的RNA，其中该RNA为终端发生小区重选之前网络设备为终端配置的。
在一些实施例中，终端发生小区重选后，接收当前服务小区的SIB1，根据该SIB1确定第二服务小区，该SIB1指示第二服务小区，在一些实施例中，终端根据该SIB1确定第二服务小区属于配置的RNA，其中该RNA为终端发生小区重选之前网络设备为终端配置的，具体示例和图11的S502类似，不再赘述。
在一些实施例中，终端发生小区重选后，终端处于非RRC连接态，可选地，该非RRC连接态为RRC INACTIVE态。
S804：若第二服务小区属于配置的RNA，并且第二定时器未运行，终端将第一变量设置为第一值。
在一些实施例中，终端发生小区重选后，终端处于非RRC连接态，可选地，该非RRC连接态为RRC INACTIVE态，在一些实施例中，终端处于RRC INACTIVE态时，向网络设备发起用于SDT的RRC连接恢复过程，开启第一定时器。第一定时器运行时发生小区重选，终端仍然处于RRC INACTIVE态。
在一些实施例中，如果终端发生小区重选后处于RRC INACTIVE态，并且第二服务小区属于配置的RNA，第二定时器未运行，终端可以将第一变量设置为第一值。
在一些实施例中，终端处于RRC INACTIVE态下，若第二服务小区属于配置的RNA，并且第二定时器未运行，以及终端在第二服务小区不可以进行SDT过程，终端可以将第一变量设置为第一值。可选地，终端在第二服务小区不可以进行SDT过程为终端不可以在第二服务小区继续之前的SDT过程，例如终端发生小区重选后，不可以继续S802中发起的用于SDT的RRC连接恢复过程。可选地，终端在第二服务小区不可以进行SDT过程为终端不可以在第二服务小区发起新的SDT过程，例如终端发生小区重选后，不可以为S802中发起的用于SDT的RRC连接恢复过程继续发起新的SDT过程，或者不可以为新获取的small data发起新的SDT过程。可选地，终端在第二服务小区不可以进行SDT过程为终端在第二服务小区没有SDT相关的配置信息，例如，第二服务小区不支持SDT，可选地，第二服务小区不支持SDT包括第二服务小区未在系统信息中广播SDT的相关配置。又例如，第二服务小区不支持RA-SDT和/或CG-SDT。
在一些实施例中，终端发生小区重选，终端处于RRC INACTIVE态，终端仍需进行周期性的RNAU，但由于此时第二定时器未运行，因此终端可以将第一变量设置为第一值。
在一些实施例中，终端进行SDT过程中(如发生小区重选之前)，第二定时器超时，终 端可以判断第一定时器是否运行。如果第一定时器运行，终端不触发RNAU，继续进行SDT过程。可选地，第一定时器运行为第一定时器继续运行，终端可以在第二服务小区继续之前的SDT过程，可选地，第一定时器运行为第一定时器开启，终端可以在第二服务小区发起新的用于SDT的RRC连接恢复过程。第二定时器超时后，终端发生小区重选，停止第一定时器，终端处于RRC INACTIVE态。若第二定时器未运行，终端可以将第一变量设置为第一值。可选地，第二定时器未运行为第二定时器超时之后不运行。
在另一些实施例中，终端发生小区重选后，处于RRC IDLE态，则终端不触发RNA，也不将第一变量设置为第一值，在另一些实施例中，终端发生小区重选后，可以在第二服务小区进行SDT过程，则终端不触发RNA，也不将第一变量设置为第一值。
不限于图16所示示例，在另一些实施例中，当接收到第二服务小区的SIB1时，若第二服务小区属于配置的RNA，并且第二定时器未运行，终端可以直接执行用于RNAU的RRC连接恢复过程，具体示例和图16类似，区别在于将图16中将第一变量设置为第一值替换为执行用于RNAU的RRC连接恢复过程，例如终端的RRC层执行用于RNAU的RRC连接恢复过程。
在另一些实施例中，终端也可以先将第一变量设置为第一值，然后终端执行用于RNAU的RRC连接恢复过程，例如终端的RRC层直接执行用于RNAU的RRC连接恢复过程。
在另一些实施例中，当接收到第二服务小区的SIB1时，若第二服务小区属于配置的RNA，并且第二定时器未运行，终端开启第三定时器，具体示例和图16类似，区别在于将图16中将第一变量设置为第一值替换为开启第三定时器。可选地，该方法还包括：当第三定时器超时，若第一定时器未运行，终端执行用于RNAU的RRC连接恢复过程。
可选地，第三定时器与第二定时器相同，例如，第三定时器的时长等于第二定时器的时长。例如第三定时器为T380。
可选地，第三定时器与第二定时器不同，例如，第三定时器的时长不等于第二定时器的时长。例如第三定时器时长小于第二定时器的时长，例如第三定时器时长单位为毫秒或秒。
可选地，第三定时器运行期间，终端可以等待NAS层是否有数据传输需求，例如NAS是否触发RRC层发起连接恢复过程。若NAS层有数据传输需求并且触发RRC层发起连接恢复过程，则终端将发起用于数据传输的RRC连接恢复过程，而不执行用于RNAU的RRC连接恢复过程，上述用于数据传输的RRC连接恢复过程包括用于SDT和用于非SDT的RRC连接恢复过程。
在一些实施例中，1>if cell reselection occurs while T319 or T302 or T3XX is running:
2>if T380 expires during an SDT procedure or has expired during an SDT procedure:
3>set the variable pendingRNA-Update to true.
在一些实施例中，如果定时器T319、定时器T302或第一定时器T3XX运行时终端发生小区重选，若第二定时器T380在SDT过程中超时或者已经超时，终端可以将变量pendingRNA-Update设置为true。
在一种可能的实现方式中，当终端的完整性校验失败，若第二定时器未运行，终端可以将第一变量设置为第一值，第一变量为第一值指示有待定的RNAU，第一变量和第一值的说明可参见上述执行RNAU的实现方式中第一变量和第一值的说明，具体示例如下图17所示。
请参见图17，图17是本申请实施例提供的又一种控制传输的方法的流程示意图。该方法包括但不限于如下步骤：
S901：终端开启第二定时器。
在一些实施例中，S901为可选的步骤，S901和图11的S401类似。
S902：终端开启第一定时器。
在一些实施例中，S902为可选的步骤，S902和图13的S501类似。
在一些实施例中，S901和S902的执行顺序可以是S901先执行，S902后执行，也可以是S902先执行，S901后执行。
S903：当终端的完整性校验失败，若第二定时器未运行，终端将第一变量设置为第一值。
在一些实施例中，第一定时器运行时，终端的完整性校验失败。在一些实施例中，终端的完整性校验失败为：终端的RRC层接收到RRC层的底层指示的完整性校验失败，RRC层的底层例如为PDCP层。
在一些实施例中，终端的完整性校验失败后，终端处于RRC INACTIVE态，在一些实施例中，终端处于RRC INACTIVE态时，向网络设备发起用于SDT的RRC连接恢复过程，开启第一定时器。第一定时器运行时终端的完整性校验失败后，终端仍然处于RRC INACTIVE态。
在一些实施例中，终端的完整性校验失败，终端处于RRC INACTIVE态，终端仍需进行周期性的RNAU，但由于此时第二定时器未运行，因此终端可以将第一变量设置为第一值。
在一些实施例中，终端进行SDT过程中(如终端的完整性校验失败之前)，第二定时器超时，终端可以判断第一定时器是否运行。如果第一定时器运行，终端不触发RNAU，继续进行SDT过程。第二定时器超时后，若终端的完整性校验失败，终端处于RRC INACTIVE态。若第二定时器未运行，终端可以将第一变量设置为第一值。可选地，第二定时器未运行为第二定时器超时之后不运行。
在另一些实施例中，终端的完整性校验失败，终端处于RRC IDLE态，则终端不触发RNAU，也不将第一变量设置为第一值。
不限于图17所示示例，在另一些实施例中，当终端的完整性校验失败，若第二定时器未运行，终端可以直接执行用于RNAU的RRC连接恢复过程，具体示例和图17类似，区别在于将图17中将第一变量设置为第一值替换为执行用于RNAU的RRC连接恢复过程，例如终端的RRC层执行用于RNAU的RRC连接恢复过程。
在另一些实施例中，终端也可以先将第一变量设置为第一值，然后终端执行用于RNAU的RRC连接恢复过程，例如终端的RRC层直接执行用于RNAU的RRC连接恢复过程。
在另一些实施例中，当终端的完整性校验失败，若第二定时器未运行，终端可以开启第三定时器，当第三定时器超时，若第一定时器未运行，终端执行用于RNAU的RRC连接恢复过程，具体示例和图17类似，区别在于将图17中将第一变量设置为第一值替换为开启第三定时器。可选地，该方法还包括：当第三定时器超时，若第一定时器未运行，终端执行用于RNAU的RRC连接恢复过程。
可选地，第三定时器与第二定时器相同，例如，第三定时器的时长等于第二定时器的时长。例如第三定时器为T380。
可选地，第三定时器与第二定时器不同，例如，第三定时器的时长不等于第二定时器的时长。例如第三定时器时长小于第二定时器的时长，例如第三定时器时长单位为毫秒或秒。
可选地，第三定时器运行期间，终端可以等待NAS层是否有数据传输需求，例如NAS是否触发RRC层发起连接恢复过程。若NAS层有数据传输需求并且触发RRC层发起连接恢复过程，则终端将发起用于数据传输的RRC连接恢复过程，而不执行用于RNAU的RRC连 接恢复过程，上述用于数据传输的RRC连接恢复过程包括用于SDT和用于非SDT的RRC连接恢复过程。
可以理解地，本申请在SDT过程进行时不会触发RNAU，其中进行SDT时，网络设备可以获取到终端所处的RNA，不执行RNAU不仅不会影响网络设备获取终端的状态，而且可以避免影响SDT过程传输的小包数据。
并且，对于SDT非正常结束的情况(例如接收到第四RRC响应消息、发生小区重选，第一定时器超时或者终端的完整性校验失败)，若第二定时器未运行(例如超时之后不运行)，终端可以将第一变量设置为第一值，以便后续UE可以继续周期性触发RNAU，不影响RNAU的正常执行。
在一种可能的实现方式中，如果在SDT过程中第一变量被设置为第一值，终端可以执行用于RNAU的RRC连接恢复过程。在一些实施例中，如果在SDT过程中第一变量被设置为第一值，以及上层(如NAS层)没有请求恢复RRC连接，终端执行用于RNAU的RRC连接恢复过程。在一些实施例中，如果终端的Access Category为2或Access Category为8的禁止被缓和，并且上层(如NAS层)没有请求恢复RRC连接，并且第一变量被设置为第一值，终端执行用于RNAU的RRC连接恢复过程。在一些实施例中，如果终端在SDT过程的Access Category的禁止被缓和，并且上层(如NAS层)没有请求恢复RRC连接，并且第一变量被设置为第一值，终端执行用于RNAU的RRC连接恢复过程。在一些实施例中，若接入禁止被缓和并且上层(如NAS层)没有请求RRC层进行RRC连接恢复，若所述第一变量为所述第一值，终端可以执行用于RNAU的RRC连接恢复过程。
请参见图18，图18示例性示出又一种时序图。
如图18所示，横轴为时间轴(t)，在第三时刻t 3，第二定时器开启(例如接收到第一RRC响应消息)，在第四时刻t 4，第一定时器开启(例如发送RRC请求消息)，在第五时刻t 5，第二定时器超时，在第六时刻t 6，第一定时器停止或者超时，t 3<t 4<t 5<t 6。第二定时器在第三时刻和第五时刻之间运行，第一定时器在第四时刻和第六时刻之间运行，第四时刻和第六时刻之间终端进行SDT过程。在第五时刻，终端进行SDT过程中，第二定时器超时，终端不会触发RNAU，即第二定时器超时以及第一定时器运行时，终端不会触发RNAU。
在一些实施例中，在第六时刻，终端发生小区重选，第一定时器停止，终端处于RRC INACTIVE态，如果小区重选后终端的服务小区不属于配置的RNA，并且终端不可以在服务小区进行SDT过程，则终端可以触发RNAU，可选地，触发RNAU为执行用于RNAU的RRC连接恢复过程，具体可参见上图13的说明。
在另一些实施例中，在第六时刻，终端接收到第四RRC响应消息，第一定时器停止，终端处于RRC INACTIVE态，如果第二定时器未运行，则终端可以触发RNAU，可选地，触发RNAU为可以将第一变量设置为第一值，具体可参见上图14的说明。
在另一些实施例中，在第六时刻，第一定时器超时，终端处于RRC INACTIVE态，如果第二定时器未运行，则终端可以触发RNAU，可选地，触发RNAU为可以将第一变量设置为第一值，具体可参见上图15的说明。
在另一些实施例中，在第六时刻，终端发生小区重选，第一定时器停止，终端处于RRC INACTIVE态，如果小区重选后终端的服务小区属于配置的RNA，终端不可以在服务小区进行SDT过程，并且此时第二定时器未运行，则终端可以触发RNAU，可选地，触发RNAU为可以将第一变量设置为第一值，具体可参见上图16的说明。
在另一些实施例中，在第六时刻，终端的完整性校验失败，第一定时器停止，终端处于RRC INACTIVE态，如果第二定时器未运行，则终端可以触发RNAU，可选地，触发RNAU为可以将第一变量设置为第一值，具体可参见上图17的说明。
在一种可能的实现方式中，终端进行SDT过程时，可以停止第二定时器，具体示例如下图19所示。
请参见图19，图19是本申请实施例提供的又一种控制传输的方法的流程示意图。该方法包括但不限于如下步骤：
S1001：终端向网络设备发送RRC请求消息。
在一些实施例中，S1001为可选的步骤。
在一些实施例中，终端有SDT的需求时，可以发起用于SDT的RRC连接恢复过程，该RRC连接恢复过程可以包括终端基于SDT向网络设备发送RRC请求消息。
在一些实施例中，终端有SDT的需求时，可以发起用于4-step SDT的RRC连接恢复过程，该过程可参见上图5-图6所示流程，其中终端在该RRC连接恢复过程中发送的RRC请求消息是基于4-step SDT发送的，该RRC请求消息可以在msg3中。
在一些实施例中，终端有SDT的需求时，可以发起用于2-step SDT的RRC连接恢复过程，该过程可参见上图7-图8所示流程，其中终端在该RRC连接恢复过程中发送的RRC请求消息是基于2-step SDT发送的，该RRC请求消息可以在msgA中。
在一些实施例中，终端有SDT的需求时，可以发起用于CG-SDT的RRC连接恢复过程，该过程可参见上图9-图10所示流程，其中终端在该RRC连接恢复过程中发送的RRC请求消息是基于CG-SDT发送的。
在一些实施例中，终端向网络设备发送RRC请求消息时，一起发送上行小包数据，具体示例如上图5、图7、图9所示流程。
S1002：网络设备向终端发送第一响应消息。
在一些实施例中，S1002为可选的步骤。
在一些实施例中，网络设备接收到终端发送的RRC请求消息，可以向终端发送第一响应消息，在一些实施例中，网络设备接收到终端发送的RRC请求消息和上行小包数据，可以向终端发送第一响应消息。
在一些实施例中，终端发起RA-SDT，网络设备接收到终端基于RA-SDT发送的RRC请求消息，可以向终端发送第一响应消息，可选地，第一响应消息可以指示竞争解决成功，可选地，第一响应消息可以指示成功完成随机接入过程，可选地，终端接收到第一响应消息，确定竞争解决成功，可选地，终端接收到第一响应消息，确定成功完成随机接入过程，可选地，第一响应消息为上图5-图8所示的contention resolution消息。
在一些实施例中，终端发起CG-SDT，网络设备接收到终端基于CG-SDT发送的RRC请求消息，可以向终端发送第一响应消息，可选地，第一响应消息可以针对S1001中发送的RRC请求消息和/或上行小包数据，可选地，第一响应消息可以指示RRC请求消息发送成功，可选地，第一响应消息可以指示上行小包数据发送成功，可选地，第一响应消息为上图9-图10所示的反馈响应消息，可选地，第一响应消息可以为调度重传的下行控制信息(downlink control information，DCI)，可选地，第一响应消息可以为调度新传的DCI。
S1003：终端的底层向上层指示第一信息。
在一些实施例中，S1003为可选的步骤。
具体地，终端可以包括多个层，具体示例可参见上图2-图3所示的用户面协议栈或控制面协议栈中包括的层。可以理解地，S1003中底层和上层为相对的概念，在一些实施例中，S1003中终端的底层为第一层，第一层为用户面协议栈或控制面协议栈中的一层，在一些实施例中，第一层为接收到网络设备发送的第一响应消息的层。在一些实施例中，S1003中上层为第二层，第二层为第一层以上的层。
例如，第一层为MAC层，第二层为RRC层。
例如，第一层为物理层，第二层为MAC层。
例如，第一层为物理层，第二层为RRC层。
S1004：终端停止第二定时器。
在一些实施例中，终端的第三层接收到第三层的底层指示的第一信息，停止第二定时器，可选地，第三层为RRC层，可选地，第三层的底层为MAC层，可选地，第三层的底层为物理层。
在一些实施例中，在RA-SDT过程中，终端的MAC层接收到网络设备发送的第一响应消息，MAC层向MAC层以上的RRC层指示第一信息，可选地，第一信息指示竞争解决成功，可选地，第一指示信息指示成功完成随机接入过程。RRC层接收到MAC层指示的第一信息，停止第二定时器。可选地，S1003中的底层为MAC层，上层为RRC层，S1004中停止第二定时器的为RRC层。
在一些实施例中，在CG-SDT过程中，终端的MAC层接收到网络设备发送的第一响应消息，MAC层向MAC层以上的RRC层指示第一信息，第一信息指示RRC请求消息和/或上行小包数据发送成功，RRC层接收到MAC层指示的第一信息，停止第二定时器。可选地，S1003中的底层为MAC层，上层为RRC层，S1004中停止第二定时器的为RRC层。
在一些实施例中，在CG-SDT过程中，终端的物理层接收到网络设备发送的第一响应消息，物理层向物理层以上的RRC层指示第一信息，第一信息指示RRC请求消息和/或上行小包数据发送成功，RRC层接收到物理层指示的第一信息，停止第二定时器。可选地，S1003中的底层为物理层，上层为RRC层，S1004中停止第二定时器的为RRC层。
在一些实施例中，在CG-SDT过程中，终端的物理层接收到网络设备发送的第一响应消息，物理层向物理层以上的MAC层指示第二信息，第二信息指示RRC请求消息和/或上行小包数据发送成功。MAC层接收到物理层指示的第二信息，向MAC层以上的RRC层指示第一信息，第一信息指示RRC请求消息和/或上行小包数据发送成功，RRC层接收到MAC层指示的第一信息，停止第二定时器。可选地，S1003中的底层为MAC层，上层为RRC层，S1004中停止第二定时器的为RRC层。
在一些实施例中，终端停止第二定时器之前，第二定时器为开启状态，例如发起用于SDT的RRC连接恢复过程(如S1001)之前，终端开启第二定时器。
在一些实施例中，终端停止第二定时器之后，可以基于此次SDT过程进行subsequent transmission，具体可参见上图5-图10所述的subsequent transmission的说明。第二定时器已被停止，不会超时，因此不会触发RNAU，从而也不会影响SDT过程中small data的传输。
在一些实施例中，终端停止第二定时器之后，可以接收网络设备发送的RRC响应消息，具体可参见上图5-图10中RRC响应消息的说明。在一些实施例中，终端停止第二定时器之后，接收到网络设备发送的第一RRC响应消息，例如为RRCRelease消息、RRCRelease with suspend config消息或其他具有相同功能但3GPP未标准化的RRC消息，终端可以开启第二定时器。
可以理解地，以上实施例所述的开启第二定时器的情况可能包括多种，接下来示例性示出两种情况：
情况一：终端进行SDT时，接收到第一RRC响应消息，停止第一定时器和开启第二定时器。示例性地，首先终端有SDT需求时，发起用于SDT的RRC连接恢复过程，开启第一定时器。然后，当第二定时器超时，但第一定时器处于运行状态时，终端不触发RNAU，继续进行SDT。最后，终端接收到第一RRC响应消息，认为此次SDT成功，停止第一定时器，保持在非RRC连接态，并且，终端接收到第一RRC响应消息，开启第二定时器，以使后续可以继续周期性触发RNAU。
情况二：终端进行SDT时，接收到第五RRC响应消息，停止第一定时器，后续接收到第一RRC响应消息，再开启第二定时器，第五RRC响应消息例如为RRCResume消息、RRCSetup消息或其他具有相同功能但3GPP未标准化的RRC消息。示例性地，首先终端有SDT需求时，发起用于SDT的RRC连接恢复过程，开启第一定时器。然后，当第二定时器超时，但第一定时器处于运行状态时，终端不触发RNAU，继续进行SDT。接下来，终端接收到第五RRC响应消息，认为此次SDT成功，停止第一定时器，并且可以从非RRC连接态进入RRC CONNECTED态。后续终端接收到第一RRC响应消息，从RRC CONNECTED态进入非RRC连接态，开启第二定时器，以便后续可以继续周期性触发RNAU。
在一种可能的实现方式中，终端接收RRC拒绝消息，若第二定时器未运行，终端可以将第一变量设置为第一值，具体示例和图14类似，区别在于图14中第二定时器超时需替换为第二定时器停止，第二定时器停止的说明可参见上图19。
在一种可能的实现方式中，终端接收RRC拒绝消息，若第二定时器未运行，终端可以直接执行用于RNAU的RRC连接恢复过程，具体示例和图14类似，区别在于S604可以更改为：若第二定时器未运行，执行用于RNAU的RRC连接恢复过程，以及图14中第二定时器超时需替换为第二定时器停止，第二定时器停止的说明可参见上图19。
在一种可能的实现方式中，终端接收RRC拒绝消息，若第二定时器未运行，终端可以开启第三定时器，当第三定时器超时，若第一定时器未运行，终端执行用于RNAU的RRC连接恢复过程，具体示例和图14类似，区别在于S604可以更改为：若第二定时器未运行，开启第三定时器，S604之后该方法还包括：当第三定时器超时，若第一定时器未运行，终端执行用于RNAU的RRC连接恢复过程，以及图14中第二定时器超时需替换为第二定时器停止，第二定时器停止的说明可参见上图19。
在一种可能的实现方式中，当第一定时器超时，若第二定时器未运行，终端可以将第一变量设置为第一值，具体示例和图15类似，区别在于图15中第二定时器超时需替换为第二定时器停止，第二定时器停止的说明可参见上图19。
在一种可能的实现方式中，当第一定时器超时，若第二定时器未运行，终端可以直接执行用于RNAU的RRC连接恢复过程，具体示例和图15类似，区别在于S703可以更改为：当第一定时器超时，若第二定时器未运行，执行用于RNAU的RRC连接恢复过程，以及图15中第二定时器超时需替换为第二定时器停止，第二定时器停止的说明可参见上图19。
在一种可能的实现方式中，当第一定时器超时，若第二定时器未运行，终端可以开启第三定时器，当第三定时器超时，若第一定时器未运行，终端执行用于RNAU的RRC连接恢复过程，具体示例和图15类似，区别在于S703可以更改为：当第一定时器超时，若第二定时器未运行，开启第三定时器，S703之后该方法还包括：当第三定时器超时，若第一定时器未运行，终端执行用于RNAU的RRC连接恢复过程，以及图15中第二定时器超时需替换为 第二定时器停止，第二定时器停止的说明可参见上图19。
在一种可能的实现方式中，当接收到第二服务小区的SIB1时，若第二服务小区属于配置的RNA，并且第二定时器未运行，终端可以将第一变量设置为第一值，具体示例和图16类似，区别在于图16中第二定时器超时需替换为第二定时器停止，第二定时器停止的说明可参见上图19。
在一种可能的实现方式中，当接收到第二服务小区的SIB1时，若第二服务小区属于配置的RNA，并且第二定时器未运行，终端可以直接执行用于RNAU的RRC连接恢复过程，具体示例和图15类似，区别在于S804可以更改为：若第二服务小区属于配置的RNA，并且第二定时器未运行，执行用于RNAU的RRC连接恢复过程，以及图16中第二定时器超时需替换为第二定时器停止，第二定时器停止的说明可参见上图19。
在一种可能的实现方式中，当接收到第二服务小区的SIB1时，若第二服务小区属于配置的RNA，并且第二定时器未运行，终端开启第三定时器，具体示例和图16类似，区别在于S804可以更改为：若第二服务小区属于配置的RNA，并且第二定时器未运行，开启第三定时器，S804之后该方法还包括：当第三定时器超时，若第一定时器未运行，终端执行用于RNAU的RRC连接恢复过程，以及图16中第二定时器超时需替换为第二定时器停止，第二定时器停止的说明可参见上图19。
在一种可能的实现方式中，当终端的完整性校验失败，若第二定时器未运行，终端可以将第一变量设置为第一值，具体示例和图17类似，区别在于图17中第二定时器超时需替换为第二定时器停止，第二定时器停止的说明可参见上图19。
在一种可能的实现方式中，当终端的完整性校验失败，若第二定时器未运行，终端可以直接执行用于RNAU的RRC连接恢复过程，具体示例和图17类似，区别在于S903可以更改为：当完整性校验失败，并且第二定时器未运行，执行用于RNAU的RRC连接恢复过程，以及图17中第二定时器超时需替换为第二定时器停止，第二定时器停止的说明可参见上图19。
在一种可能的实现方式中，当终端的完整性校验失败，若第二定时器未运行，终端可以开启第三定时器，具体示例和图17类似，区别在于S903可以更改为：当完整性校验失败，并且第二定时器未运行，开启第三定时器，S903之后该方法还包括：当第三定时器超时，若第一定时器未运行，终端执行用于RNAU的RRC连接恢复过程，以及图17中第二定时器超时需替换为第二定时器停止，第二定时器停止的说明可参见上图19。
在一种可能的实现方式中，终端在SDT过程将第一变量设置为第一值之后，若接入禁止被缓和并且非接入NAS层没有请求RRC层进行RRC连接恢复，若第一变量为第一值，终端可以执行用于RNAU的RRC连接恢复过程。
可以理解地，本申请中的SDT过程(例如上图5-图10所示的SDT过程)可以包括上述用于SDT的RRC连接恢复过程，可选地，其中发送的RRC请求消息中的resumeCause IE为mo-data。本申请中的RNAU(例如上述示例性介绍的执行RNAU的实现方式)可以包括上述用于RNAU的RRC连接恢复过程，可选地，其中发送的RRC请求消息中的resumeCause IE为rna-Update。
不限于上述列举的情况，在另一些实施例中，处于RRC IDLE态可能也许需执行RNAU，具体实现方式和上述RRC INACTIVE态的UE的实现方式类似，只是表述上可能有所不同，例如用于RNAU的RRC连接恢复过程可以替换为用于RNAU的RRC连接建立过程。
不限于上述示例的SIB1，在另一些实施例中，终端可以接收到其他消息，根据该消息确 定服务小区是否属于配置的RNA，例如从该消息中读取小区标识，判断读取的小区标识是否属于RAN-NotificationAreaInfo IE中基站为UE配置的小区列表中包括的小区标识，又例如从该消息中读取小区的TAC，判断读取的TAC是否属于RAN-NotificationAreaInfo IE中基站为UE配置的RAN area列表中包括的TAC。本申请对判断服务小区是否属于配置的RNA的方式不作限定。
在一些实施例中，处于RRC INACTIVE状态的UE需要在T380超时或在UE当前RNA外的小区接收SIB1后触发用于RNAU的RRC连接恢复过程。然而，正在进行SDT数据传输的UE实际上不需要进行RNAU，因为网络设置可以知道UE的小区位置。因此，应避免在SDT过程中触发RNAU。
在一些实施例中，在SDT过程中停止T380。例如，在SDT过程开始后，UE在从网络设备接收到与UE的RRC请求消息对应的第一响应消息时停止T380。例如，UE在接收到RA-SDT的竞争解决MAC CE时，或在接收到响应于通过CG-SDT发送的RRCResumeRequest的ACK时停止T380。
在一些实施例中，引入一个附加条件，即只有在SDT失败检测定时器未运行时，即第一定时器未运行时，若T380超时才能触发RNAU。其中，SDT失败检测定时器在UE发起用于SDT的RRC连接恢复过程时启动，也就是说，当SDT失败检测定时器运行时，UE正在进行SDT过程。因此，为了避免T380超时触发的周期性RNAU，可以在当前触发周期性RNAU的条件中添加一个额外的条件。
可以理解地，本申请描述的通信系统架构以及业务场景是为了更加清楚的说明本申请的技术方案，并不构成对于本申请提供的技术方案的限定，本领域普通技术人员可知，随着通信系统架构的演变和新业务场景的出现，本申请提供的技术方案对于类似的技术问题，同样适用。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，该流程可以由计算机程序来计算机程序相关的硬件完成，该计算机程序可存储于计算机可读取存储介质中，该计算机程序在执行时，可包括如上述各方法实施例的流程。而前述的存储介质包括：只读存储器(read-only memory，ROM)或随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可存储计算机程序代码的介质。

Claims (16)

  1. 一种控制传输的方法，其特征在于，应用于处于非无线资源控制RRC连接态的终端，所述方法包括：
    满足第一预设条件时，执行用于基于无线接入网的通知区域更新RNAU的RRC连接恢复过程；其中，
    所述第一预设条件包括第二定时器超时并且第一定时器未运行；或，
    所述第一预设条件包括所述终端接收到第一服务小区的系统信息块SIB1，所述第一服务小区不属于配置的基于无线接入网的通知区域RNA，并且所述第一定时器未运行；
    其中，所述第一定时器在所述终端发起用于小包数据传输SDT的RRC连接恢复过程时开启，所述第二定时器在所述终端接收到包括所述第二定时器时长的RRC释放消息时开启。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    在所述第一定时器运行时，若接收到RRC拒绝消息，停止所述第一定时器；
    若所述第二定时器未运行，将第一变量设置为第一值，所述第一变量为所述第一值指示有待定的RNA更新过程。
  3. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    在所述第一定时器运行时，若接收到RRC拒绝消息，停止所述第一定时器；
    若所述第二定时器未运行，执行所述用于RNAU的RRC连接恢复过程。
  4. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    在所述第一定时器运行时，若接收到RRC拒绝消息，停止所述第一定时器；
    若所述第二定时器未运行，开启第三定时器；
    当所述第三定时器超时，若所述第一定时器未运行，执行所述用于RNAU的RRC连接恢复过程。
  5. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    当所述第一定时器超时，若所述第二定时器未运行，将第一变量设置为第一值，所述第一变量为所述第一值指示有待定的RNA更新过程。
  6. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    当所述第一定时器超时，若所述第二定时器未运行，执行所述用于RNAU的RRC连接恢复过程。
  7. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    当所述第一定时器超时，若所述第二定时器未运行，开启第三定时器；
    当所述第三定时器超时，若所述第一定时器未运行，执行所述用于RNAU的RRC连接恢复过程。
  8. 如权利要求5-7任一项所述的方法，其特征在于，所述非无线资源控制RRC连接态为RRC非激活态；所述第一定时器超时后，所述终端处于所述RRC非激活态。
  9. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    在所述第一定时器运行时，若发生小区重选，停止所述第一定时器；
    接收第二服务小区的SIB1，所述第二服务小区为所述终端发生小区重选后的服务小区；
    当接收到所述第二服务小区的SIB1时，若所述第二服务小区属于配置的RNA，并且所述第二定时器未运行，将第一变量设置为第一值，所述第一变量为所述第一值指示有待定的RNA更新过程。
  10. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    在所述第一定时器运行时，若发生小区重选，停止所述第一定时器；
    接收第二服务小区的SIB1，所述第二服务小区为所述终端发生小区重选后的服务小区；
    当接收到所述第二服务小区的SIB1时，若所述第二服务小区属于配置的RNA，并且所述第二定时器未运行，执行所述用于RNAU的RRC连接恢复过程。
  11. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    在所述第一定时器运行时，若发生小区重选，停止所述第一定时器；
    接收第二服务小区的SIB1，所述第二服务小区为所述终端发生小区重选后的服务小区；
    当接收到所述第二服务小区的SIB1时，若所述第二服务小区属于配置的RNA，并且所述第二定时器未运行，开启第三定时器；
    当所述第三定时器超时，若所述第一定时器未运行，执行所述用于RNAU的RRC连接恢复过程。
  12. 如权利要求9-11任一项所述的方法，其特征在于，所述非无线资源控制RRC连接态为RRC非激活态；所述终端发生小区重选后，所述终端处于所述RRC非激活态。
  13. 如权利要求2、5或9所述的方法，其特征在于，所述将第一变量设置为第一值之后，所述方法还包括：
    若接入禁止被缓和并且非接入NAS层没有请求RRC层进行RRC连接恢复，若所述第一变量为所述第一值，执行所述用于RNAU的RRC连接恢复过程。
  14. 如权利要求1-13任一项所述的方法，其特征在于，所述非无线资源控制RRC连接态为RRC非激活态。
  15. 一种终端，其特征在于，包括收发器、处理器和存储器，所述存储器用于存储计算机程序，所述处理器调用所述计算机程序，用于执行如权利要求1-14任一项所述的方法。
  16. 一种计算机存储介质，其特征在于，所述计算机存储介质存储有计算机程序，所述计算机程序被处理器执行时，实现权利要求1-14任一项所述的方法。
PCT/CN2022/106522 2021-07-21 2022-07-19 一种控制传输的方法及相关装置 WO2023001149A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP22845314.8A EP4366378A1 (en) 2021-07-21 2022-07-19 Method for controlling transmission and related apparatus

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202110822924.X 2021-07-21
CN202110822924 2021-07-21
CN202110897870.3 2021-08-05
CN202110897870.3A CN115696644A (zh) 2021-07-21 2021-08-05 一种控制传输的方法及相关装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/418,628 Continuation US20240163957A1 (en) 2021-07-21 2024-01-22 Transmission control method and related apparatus

Publications (1)

Publication Number Publication Date
WO2023001149A1 true WO2023001149A1 (zh) 2023-01-26

Family

ID=84980016

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/106522 WO2023001149A1 (zh) 2021-07-21 2022-07-19 一种控制传输的方法及相关装置

Country Status (2)

Country Link
EP (1) EP4366378A1 (zh)
WO (1) WO2023001149A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190306764A1 (en) * 2018-03-28 2019-10-03 Telefonaktiebolaget Lm Ericsson (Publ) Method for avoiding unnecessary actions in resume procedure
CN110740484A (zh) * 2018-07-20 2020-01-31 夏普株式会社 用户设备的控制方法以及用户设备
CN110831260A (zh) * 2018-08-10 2020-02-21 电信科学技术研究院有限公司 Rrc连接恢复的处理方法、装置及终端
US20200092779A1 (en) * 2018-09-18 2020-03-19 Samsung Electronics Co., Ltd. Method and apparatus for reporting selected plmn of rrc-inactive mode ue in next-generation communication system
CN111132378A (zh) * 2018-10-31 2020-05-08 北京展讯高科通信技术有限公司 非激活态的增强方法、装置、用户设备及存储介质
CN112640529A (zh) * 2018-08-10 2021-04-09 鸿颖创新有限公司 用于rrc状态转换的方法和设备

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190306764A1 (en) * 2018-03-28 2019-10-03 Telefonaktiebolaget Lm Ericsson (Publ) Method for avoiding unnecessary actions in resume procedure
CN110740484A (zh) * 2018-07-20 2020-01-31 夏普株式会社 用户设备的控制方法以及用户设备
CN110831260A (zh) * 2018-08-10 2020-02-21 电信科学技术研究院有限公司 Rrc连接恢复的处理方法、装置及终端
CN112640529A (zh) * 2018-08-10 2021-04-09 鸿颖创新有限公司 用于rrc状态转换的方法和设备
US20200092779A1 (en) * 2018-09-18 2020-03-19 Samsung Electronics Co., Ltd. Method and apparatus for reporting selected plmn of rrc-inactive mode ue in next-generation communication system
CN112715037A (zh) * 2018-09-18 2021-04-27 三星电子株式会社 在下一代通信系统中用于报告rrc非活动模式的ue的所选择的plmn的方法和装置
CN111132378A (zh) * 2018-10-31 2020-05-08 北京展讯高科通信技术有限公司 非激活态的增强方法、装置、用户设备及存储介质

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
LENOVO, MOTOROLA MOBILITY: "Analysis on RA selection and RNAU", 3GPP DRAFT; R2-2009873, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20201102 - 20201113, 23 October 2020 (2020-10-23), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051942675 *
MEDIATEK INC.: "Summary of email discussion [Post111-e][901] Extension scenarios for ToAddMod lists (MediaTek)", 3GPP DRAFT; R2-2009976, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Online; 20201102 - 20201113, 23 October 2020 (2020-10-23), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051942729 *

Also Published As

Publication number Publication date
EP4366378A1 (en) 2024-05-08

Similar Documents

Publication Publication Date Title
JP7352039B2 (ja) 無線リソース制御（ｒｒｃ）インアクティブ状態での小規模データ伝送
US20210126747A1 (en) Method and apparatus for performing light connection in wireless communication system
CN110663284B (zh) 在无线通信系统中执行服务请求过程的方法和设备
CN107360562B (zh) 处理无线资源控制状态改变的装置及方法
US11284346B2 (en) Data transmission method and apparatus
US10225879B2 (en) Device and method of handling a user equipment access stratum context
CN108886748B (zh) 用于减少信令开销和减少终端电池的方法和设备
CN114205920B (zh) 无线通信系统中用于小数据传送程序的方法和设备
CN108271276B (zh) 处理系统间移动中的新无线连接的装置及方法
CN110603829A (zh) 数据传输的方法、终端设备和接入网设备
US20230284329A1 (en) Method and apparatus for handling response timer and cell reselection for small data transmission
US20220225453A1 (en) Method and apparatus for performing dual connectivity in wireless communication system
CN107454636B (zh) 处理用户端存取层上下文的装置及方法
CN114158141A (zh) 无线通信系统中用于连接恢复程序的方法和设备
CN108430070B (zh) 一种无线资源控制连接方法及设备、计算机存储介质
US20220303944A1 (en) Configuration of early downlink payload data transmission
KR20230084509A (ko) 소규모 데이터 전송 절차를 위한 시간 정렬을 처리하기 위한 방법들 및 장치들
WO2023154332A1 (en) Managing small data transmission with a configured grant configuration
US20220159685A1 (en) Data transmission method and apparatus
US10560870B2 (en) Device and method of handling cellular-WLAN aggregation
WO2023001149A1 (zh) 一种控制传输的方法及相关装置
CN115699944A (zh) 终端装置、方法以及集成电路
US20210100037A1 (en) Flexible activation of early data transmission
WO2023051366A1 (zh) 一种控制传输的方法及相关装置
US20240163957A1 (en) Transmission control method and related apparatus

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22845314

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: MX/A/2024/000988

Country of ref document: MX

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112024001037

Country of ref document: BR

WWE Wipo information: entry into national phase

Ref document number: 2022845314

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022845314

Country of ref document: EP

Effective date: 20240131

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 112024001037

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20240118