WO2022151068A1 - Procédé et appareil pour un traitement de secours pour des données disponibles - Google Patents

Procédé et appareil pour un traitement de secours pour des données disponibles Download PDF

Info

Publication number
WO2022151068A1
WO2022151068A1 PCT/CN2021/071546 CN2021071546W WO2022151068A1 WO 2022151068 A1 WO2022151068 A1 WO 2022151068A1 CN 2021071546 W CN2021071546 W CN 2021071546W WO 2022151068 A1 WO2022151068 A1 WO 2022151068A1
Authority
WO
WIPO (PCT)
Prior art keywords
sdt
drb
srb
rrc
serving
Prior art date
Application number
PCT/CN2021/071546
Other languages
English (en)
Inventor
Jie Shi
Lianhai WU
Haiming Wang
Ran YUE
Jing HAN
Original Assignee
Lenovo (Beijing) Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo (Beijing) Limited filed Critical Lenovo (Beijing) Limited
Priority to PCT/CN2021/071546 priority Critical patent/WO2022151068A1/fr
Publication of WO2022151068A1 publication Critical patent/WO2022151068A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment

Definitions

  • Embodiments of the present application generally relate to wireless communication technology, especially to a method and apparatus for fallback process for available data.
  • a user equipment (UE) in RRC_INACTIVE state (also called an inactive mode UE)
  • UE user equipment
  • PUSCH physical uplink shared channel
  • RACH random access channel
  • a small data transmission (SDT) procedure is generally used to transmit data for a data radio bearer (DRB) for SDT, if a DRB for non-SDT is available in a UE in the SDT procedure, the UE needs to fallback to connected mode. Therefore, how to define the UE fallback mechanism needs to be discussed.
  • DRB data radio bearer
  • Embodiments of the present application provide a method and apparatus for fallback process for available data.
  • Some embodiments of the present application provide a method, performed by a user equipment (UE) .
  • the method may include at least one of: transmitting non-SDT available information to a serving base station (BS) in a case that a data radio bearer (DRB) or a signaling radio bearer (SRB) for non-small data transmission (SDT) is available in a SDT procedure or receiving a non-SDT available information; receiving a radio resource control (RRC) response message from the serving BS; and transitioning to an RRC connected mode, inactive mode or idle mode based on the RRC response message.
  • DRB data radio bearer
  • SRB signaling radio bearer
  • RRC radio resource control
  • the UE could send a radio resource control (RRC) resume request message to network.
  • the response message could be one of the RRC resume message, RRC Release message with or without the suspended indication.
  • the message including the dedicated or enabled UL grant or RACH resource for UE transmit the RRC resume request message, or the message which makes UE move to connected mode.
  • the UE could move to an RRC connected mode upon receiving the RRC resume message.
  • the UE could move to an idle mode upon receiving the RRC Release message without the suspended indication.
  • the response message could be RRC resume message for SDT transmission, UE will be in inactive mode to perform the data transmission for SDT DRB and or SDT SRB if UE receive this RRC resume message for SDT transmission, or UE will be in inactive mode to perform the subsequent data transmission for SDT DRB and or SDT SRB if UE receives this RRC resume message for SDT transmission, or UE will be in inactive mode to perform the subsequent data transmission for SDT DRB and or SDT SRB and or not suspend the SDT DRB and or SDT SRB if UE receives this RRC resume message for SDT transmission.
  • RRC resume message for SDT could be named as the RRCResumeSDT or a new RRC message.
  • RRC resume message for SDT transmission to indicate UE perform the subsequent data transmission for SDT DRB and or SDT SRB in inactive mode.
  • An explicit or implicit indication could be included in RRC resume message for SDT transmission to indicate UE perform the subsequent data transmission for SDT DRB and or SDT SRB in inactive mode and or be without suspending the SDT DRB and or SDT SRB.
  • a base station will transmit the RRC response message to UE.
  • UE will monitor the PDCCH addressed by the TC-RNTI, C-RNTI or SDT-RNTI after UE receives the RRC resume message for SDT.
  • C-RNTI could be the C-RNTI based on the successful contention resolution in RACH based SDT or in CG based SDT.
  • the non-SDT available information includes: non-SDT data available indication information for indicating the DRB or the SRB for non-SDT being available, or non-SDT service being available; a buffer status report (BSR) for non-SDT; or a BSR for a separate logical channel group (LCG) for non-SDT.
  • the non-SDT available information could be received from the NAS layer.
  • the method may further include: starting a timer upon the non-SDT available information is transmitted to the serving BS or upon the non-SDT available information is transmitted to a lower layer.
  • the method may further include: running the timer in a MAC layer of the UE and indicating expiry of the timer to an RRC layer of the UE; indicating the RRC layer of the UE to start the timer upon non-SDT available information in MAC layer is transmitted; or starting or running the timer in the RRC layer of the UE upon the non-SDT data available indication information in RRC layer is transmitted.
  • the method may further include: performing a random access channel (RACH) procedure to transmit an RRC resume request message if the UE does not receive the RRC response message from the BS before the timer expires.
  • RACH random access channel
  • the method may further include: receiving an uplink (UL) grant for SDT transmission for an RRC resume request message or an indication to enable a UL grant resource for SDT transmission for an RRC resume request message from the serving BS, after transmitting the non-SDT available information; and transmitting the RRC resume request message for resuming the DRB or the SRB for non-SDT on the UL grant resource to the serving BS.
  • UL uplink
  • the RRC resume request message comprises at least one of inactive-radio network temporary identifier (I-RNTI) of the UE, a resume cause, an authentication token and C-RNTI in RACH based SDT procedure or C-RNTI in CG based SDT procedure; or the RRC resume request message comprises at least one of resume cause for non-SDT transmission or with legacy information, null of I-RNTI, null of an authentication token, and null content of this message.
  • I-RNTI inactive-radio network temporary identifier
  • the method may further include: resuming the SRB or the DRB for non-SDT or the suspended SRB or DRB by using security keys used in the SDT procedure.
  • the resuming of the SRB or the DRB for non-SDT or the suspended the SRB or the DRB could be performed before UE sends the RRC resume request or after UE receives the RRC resume message.
  • the method may further include: multiplexing the data for SDT DRB or SDT SRB with the RRC resume request message if the UL grant resource is allowed or transmitting only RRC resume request message in the UL grant resource.
  • the method may further include: multiplexing the data for DRB or the SRB for non-SDT with the RRC resume request message and/or data for a DRB or a SRB for SDT if the UL grant resource is allowed.
  • the method may further include: receiving a dedicated RACH preamble for a 2-step RACH procedure or a 4-step RACH procedure from the serving BS after transmitting the non-SDT available information, and transmitting an RRC resume request message to a serving BS by using the RACH preamble.
  • the method may further include: transmitting an explicit or implicit indication to suspend the DRB or the SRB for SDT to the serving BS.
  • the method may further include: transmitting an RRC resume request message for resuming the DRB or the SRB for non-SDT or for resuming the suspended DRB or SRB in the 2-step RACH procedure or the 4-step RACH procedure.
  • the DRB or the SRB for SDT will be not suspended and the transmission of the DRB or the SRB for SDT will be continued to perform when the RRC resume request message is transmitted in the 2-step RACH procedure, the 4-step RACH procedure, or a CG based SDT procedure.
  • the method may further include: receiving an explicit or implicit indication to suspend the DRB or the SRB for SDT from the serving BS after transmitting the non-SDT available information, or suspending the DRB or the SRB for SDT after transmitting the non-SDT available information or receiving the RRC resume request or non-SDT available information from the upper layer; and transmitting an RRC resume request message for resuming the DRB or the SRB for non-SDT in the 2-step RACH procedure, the 4-step RACH procedure, or a CG based SDT procedure.
  • the method may further include: transmitting an RRC resume request message for resuming the DRB or the SRB for non-SDT multiplexed with the DRB or the SRB for SDT on a UL grant resource to the serving BS.
  • the method may include: transmitting an RRC resume request message for resuming the DRB or the SRB for non-SDT or resuming the suspended DRB or SRB.
  • the RRC resume request message it could include the non-SDT available information.
  • the RRC resume request message is transmitted by using a security key used in the SDT procedure.
  • the method may further include: after transitioning to RRC connected mode, transmitting an RRC resume complete message multiplexed with the DRB or the SRB for SDT on a UL grant resource to the serving BS.
  • Some other embodiments of the present application provide a method performed by a distributed unit (DU) of a serving base station (BS) .
  • the method may include at least one of: receiving non-SDT available information from a user equipment (UE) in the case that a data radio bearer (DRB) or a signaling radio bearer (SRB) for non-small data transmission (SDT) is available in the UE in a SDT procedure; and transmitting the non-SDT available information to a central unit (CU) of a serving BS.
  • DRB data radio bearer
  • SRB signaling radio bearer
  • the non-SDT available information includes: non-SDT data available indication information for indicating the DRB or the SRB for non-SDT being available or non-SDT service being available; a buffer status report (BSR) for non-SDT; or a BSR for a separate logical channel group (LCG) for non-SDT.
  • non-SDT data available indication information for indicating the DRB or the SRB for non-SDT being available or non-SDT service being available
  • BSR buffer status report
  • LCG separate logical channel group
  • Some other embodiments of the present application provide a method performed by a central unit (CU) of a serving base station (BS) .
  • the method may include: receiving non-SDT available information from a distributed unit (DU) of the serving BS in the case that a data radio bearer (DRB) or a signaling radio bearer (SRB) for non-SDT is available in a user equipment (UE) in a SDT procedure; and transmitting the non-SDT available information to an anchor BS.
  • DU distributed unit
  • DRB data radio bearer
  • SRB signaling radio bearer
  • the non-SDT available information includes: non-SDT data available indication information for indicating the DRB or the SRB for non-SDT being available or non-SDT service being available; a buffer status report (BSR) for non-SDT; or a BSR for a separate logical channel group (LCG) for non-SDT.
  • non-SDT data available indication information for indicating the DRB or the SRB for non-SDT being available or non-SDT service being available
  • BSR buffer status report
  • LCG separate logical channel group
  • the method may further include: receiving an indication to resume the DRB or the SRB for non-SDT or suspended DRB or SRB from the anchor BS; and transmitting a radio resource control (RRC) resume message to the UE.
  • RRC radio resource control
  • the method may further include: receiving an anchor relocation indication from the anchor BS; and transmitting an RRC response message to the UE after a path switching is finished.
  • the method may further include: transmitting an indication to enable a UL grant resource for SDT transmission for an RRC resume request message to the UE, after receiving the non-SDT available information; and receiving the RRC resume request message for resuming the DRB or the SRB for non-SDT or suspended DRB or SRB on the UL grant resource from the UE.
  • the method may further include: identifying the RRC resume request message for resuming the DRB or the SRB for non-SDT or suspended DRB or SRB after receiving the RRC resume request message by at least one of the following: determining whether the RRC resume request message comprises at least one of inactive-radio network temporary identifier (I-RNTI) of the UE, a resume cause, an authentication token and C-RNTI in RACH based SDT procedure or C-RNTI in CG based SDT procedure; determining whether the RRC resume request message comprises at least one of a resume cause for non-SDT transmission or with legacy information, null of I-RNTI, null of an authentication token, and null content of this message; determining whether the RRC resume request message is transmitted in the SDT procedure; and determining whether the RRC resume request message is transmitted without any DRB or the SRB for SDT.
  • I-RNTI inactive-radio network temporary identifier
  • the method may further include: receiving an RRC resume request message for resuming the DRB or the SRB for non-SDT or suspended DRB or SRB from the UE; transmitting the RRC resume request message for resuming the DRB or the SRB for non-SDT or suspended DRB or SRB to an anchor BS; and receiving an RRC response message from the anchor BS.
  • the method may further include: transmitting a suspend request message on an SRB or a DRB for SDT to an anchor BS; and receiving a response message to the suspend request message from the anchor BS.
  • Any one of the RRC resume request message, the suspend request message, the RRC response message, and the response message to the suspend request message is an Xn interface message including at least one of UE context retrieve messages.
  • Some other embodiments of the present application provide a method performed by a central unit (CU) of an anchor base station (BS) .
  • the method may include: receiving non-SDT available information from a serving BS in the case that a DRB or the SRB for non-SDT is available in the UE; determining to resume the DRB or the SRB for non-SDT; and transmitting an indication to resume the DRB or the SRB for non-SDT to the serving BS and a distributed unit (DU) of the anchor BS.
  • CU central unit
  • BS anchor base station
  • the method may further include: determining anchor relocation after receiving non-SDT available information; transmitting an anchor relocation indication to the serving BS.
  • the method may further include: receiving an RRC resume request message for resuming the DRB or the SRB for non-SDT or a suspended DRB or SRB from a serving BS; and transmitting an indication to resume DRB or the SRB for non-SDT or the suspended DRB or SRB to the serving BS and a DU of the anchor BS.
  • the method may further include: receiving a suspend request message on an SRB or a DRB for SDT from a serving BS; determining to suspend the an SRB or a DRB for SDT; and transmitting an indication to suspend the an SRB or a DRB for SDT to the serving BS and a DU of the anchor BS.
  • Transmitting of the indication to suspend the SRB or the DRB for SDT or the indication to resume the DRB or the SRB for non-SDT to the DU of the anchor BS is performed by a UE context management message in an F1 interface.
  • Transmitting of the indication to suspend the SRB or the DRB for SDT or the indication to resume DRB or the SRB for non-SDT is transmitted by a CU-control plane (CP) of the anchor BS to a CU-user plane (UP) of the anchor BS, and is performed by a bear management message in an E1 interface.
  • CP CU-control plane
  • UP CU-user plane
  • Transmitting of the indication to suspend the SRB or the DRB for SDT or the indication to resume the DRB or the SRB for non-SDT to the serving BS is performed by an Xn interface message including at least one of UE context retrieve messages.
  • the apparatus may include at least one non-transitory computer-readable medium having computer executable instructions stored therein; at least one receiver; at least one transmitter; and at least one processor coupled to the at least one non-transitory computer-readable medium, the at least one receiver and the at least one transmitter.
  • the computer executable instructions are programmed to implement the above method with the at least one receiver, the at least one transmitter and the at least one processor.
  • the embodiments of the present application can make the UE fallback to an RRC connected mode in a case that a DRB or SRB for non-SDT is available in a SDT procedure.
  • FIG. 1 illustrates a wireless communication system according to some embodiments of the present application
  • FIG. 2 illustrates another wireless communication system according to some embodiments of the present application
  • FIG. 3 is a schematic diagram illustrating an internal structure of a BS according to some embodiments of the present application.
  • FIG. 4 is a schematic diagram illustrating an internal structure of a BS according to some other embodiments of the present application.
  • FIG. 5 illustrates a flow chart of a method for fallback process for available data according to an embodiment of the present application
  • FIG. 6 illustrates a flow chart of another method for fallback process for available data according to an embodiment of the present application
  • FIG. 7 illustrates a flow chart of yet another method for fallback process for available data according to some embodiments of the present application
  • FIG. 8 illustrates an apparatus according to some embodiments of the present application.
  • FIG. 9 illustrates another apparatus according to some other embodiments of the present application.
  • FIG. 1 illustrates a wireless communication system according to some embodiments of the present application.
  • the wireless communication system can include at least one BS, at least one UE, and a CN node.
  • BSs and UEs e.g., a BS (e.g., BS 102) and a UE (UE 101) are depicted in FIG. 1, one skilled in the art will recognize that any number of the BSs and UEs may be included in the wireless communication system.
  • the wireless communication system can include at least one base station (BS) 102, at least one UE 101, and a core network (CN) node 103.
  • BS base station
  • UE 101 UE
  • CN core network
  • the BS 102 may be distributed over a geographic region and may communicate with the CN node 103 via an interface.
  • the UE 101 could be in a RRC_IDLE state or in a RRC_INACTIVE state.
  • the UE 101 transmits small data to the BS 102, and the BS 102 transmits the small data to the CN node 103 via the interface.
  • FIG. 2 illustrates another wireless communication system according to some embodiments of the present application.
  • the wireless communication system can include at least one BS, at least one UE, and a CN node.
  • BSs and UEs e.g., two BSs (e.g., BS 202a and BS 202b) and a UE (UE 201) are depicted in FIG. 2, one skilled in the art will recognize that any number of the BSs and UEs may be included in the wireless communication system.
  • the BS 202a and the BS 202b may be distributed over a geographic region, and they may communicate with each other via an interface Xn.
  • the BS 202a and the BS 202b may communicate with a CN node 203 via an interface NG.
  • the CN node 203 in FIG. 2 or the CN node 103 in FIG. 1 can be a mobility management function (AMF) or a user plane function (UPF) .
  • the CN node 203 in FIG. 2 or the CN node 103 in FIG. 1 can be a mobility management function (AMF) or a user plane function (UPF) .
  • the BS 202a or the BS 202b in FIG. 2 or the BS102 in FIG. 1 may also be referred to as an access point, an access terminal, a base, a base unit, a macro cell, a Node-B, an evolved Node B (eNB) , a gNB, a Home Node-B, a relay node, or a device, or described using other terminology used in the art.
  • the BS 202a or the BS 202b is generally part of a radio access network that may include one or more controllers communicably coupled to one or more corresponding BS (s) .
  • the UE 201 in FIG. 2 or the UE 101 in FIG. 1 may be a computing device, such as a desktop computer, a laptop computer, a personal digital assistant (PDA) , a tablet computer, a smart television (e.g., a television connected to the Internet) , a set-top box, a game console, a security system (including security cameras) , a vehicle on-board computer, a network device (e.g., router, switch, and modem) , or the like.
  • a computing device such as a desktop computer, a laptop computer, a personal digital assistant (PDA) , a tablet computer, a smart television (e.g., a television connected to the Internet) , a set-top box, a game console, a security system (including security cameras) , a vehicle on-board computer, a network device (e.g., router, switch, and modem) , or the like.
  • PDA personal digital assistant
  • a tablet computer such as a
  • the UE 201 may be a portable wireless communication device, a smart phone, a cellular telephone, a flip phone, a device having a subscriber identity module, a personal computer, a selective call receiver, or any other device that is capable of sending and receiving communication signals on a wireless network.
  • the UE 201 in FIG. 2 or the UE 101 in FIG. 1 may be a wearable device, such as a smart watch, a fitness band, an optical head-mounted display, or the like.
  • 1 may be referred to as a subscriber unit, a mobile, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal, or a device, or described using other terminology used in the art.
  • the wireless communication system may be compatible with any type of network that is capable of sending and receiving wireless communication signals.
  • the wireless communication system can be compatible with a wireless communication network, a cellular telephone network, a time division multiple access (TDMA) -based network, a code division multiple access (CDMA) -based network, an orthogonal frequency division multiple access (OFDMA) -based network, a long term evolution (LTE) network, a 3rd generation partnership project (3GPP) -based network, a 3GPP 5G network, a satellite communications network, a high altitude platform network, and/or other communications networks.
  • TDMA time division multiple access
  • CDMA code division multiple access
  • OFDMA orthogonal frequency division multiple access
  • LTE long term evolution
  • 3GPP 3rd generation partnership project
  • 3GPP 5G 3rd generation partnership project
  • the wireless communication system can be compatible with 5G new radio of the 3GPP protocol, wherein BS 102 transmits data using an OFDM modulation scheme on the downlink (DL) and UE 101 transmits data on the uplink (UL) using a single-carrier frequency division multiple access (SC-FDMA) or OFDM scheme. More generally, however, the wireless communication system may implement some other open or proprietary communication protocols, for example, WiMAX, WiFi, among other protocols.
  • the BS may communicate using other communication protocols, such as the IEEE 802.11 family of wireless communication protocols. Further, in some embodiments of the present application, the BS may communicate over licensed spectrums, whereas in other embodiments the BS may communicate over unlicensed spectrums. Embodiments of the present application are not intended to be limited to the implementation of any particular wireless communication system architecture or protocol. In yet some embodiments of the present application, the BS may communicate with a UE using 3GPP 5G protocols.
  • the UE 201 is in a RRC_INACTIVE state (or inactive mode) .
  • the BS 202a and the BS 202b are gNB.
  • RRC_INACTIVE state is a state where a UE remains in connection management (CM) -CONNECTED and can move within an area configured by next generation-radio access network (NG-RAN) (that is, RAN notification area (RNA) ) without notifying NG-RAN.
  • NG-RAN connection management
  • RNA RAN notification area
  • the UE 201 can move within the RNA 222.
  • the BS 202b is the last serving BS of UE 201, and the UE 201 is currently in the cell covered by the BS 202a.
  • the BS 202b keeps the context of the UE 201 and the associated NG connection with the CN node 203.
  • the BS 202b may be also referred to as "anchor BS" .
  • the UE 201 in inactive mode may transmit uplink data.
  • the UE 201 may perform small data transmission.
  • the BS 202a may transmit the data from the UE 201 to the BS 202b via the interface Xn, and then the BS 202b transmits the data to the CN node 203.
  • the BS 202a when performing the small data transmission, the BS 202a knows that there is data from the UE 201 to be transmitted, the BS 202a first obtains the context of the UE 201 from the BS 202b and then transmits the data from the UE 201 to the CN node 203.
  • the data transmission or small data transmission may mean that a UE in an inactive state/mode or an idle state/mode could transmit the data to the network side (or network) , or receive the data from the network side.
  • SDT small data transmission
  • An inactive UE may have a CN connection in a cell (e.g., cell A) associated with its last serving BS (also referred to as "anchor BS" ) . However, in some scenarios, the inactive UE may perform data transmission via another cell (cell B) .
  • the data transmission may include at least one of an uplink data transmission and downlink data transmission.
  • the inactive UE may initiate an uplink data transmission via cell B, establish a RAN connection with cell B, enter the connected mode, and then perform the data transmission.
  • the inactive UE may initiate an uplink data transmission via cell B and still stay in inactive mode in the data transmission procedure.
  • An idle UE may act similarly.
  • the inactive or idle UE may receive a suspend message or release message from cell B and then go back to the inactive or idle mode. Or, after the completion of the data transmission, the inactive or idle UE may receive a suspend message or release message from cell B and the UE still stay in inactive or idle mode in the data transmission procedure.
  • the suspend message or release message can be an RRC message.
  • the data size in such data transmission may be not greater than the maximum transport block (TB) size that can be applied in one transmission, as defined in standard protocols. Small data transmission is one of such scenarios.
  • TB maximum transport block
  • a UE in inactive mode could perform a small data transmission over configured grant type 1 resources, Msg. Afor 2-step RACH, or Msg. 3 in normal RACH from INACTIVE state.
  • a work item description (WID) on small data transmission (SDT) in a RRC_INACTIVE state is as follows:
  • FIG. 3 is a schematic diagram illustrating an internal structure of a BS according to some embodiments of the present application.
  • the internal structure of a BS may be split into a central unit (CU) and at least one distributed unit (DU) (e.g., two DUs shown in FIG. 3) .
  • DU distributed unit
  • FIG. 3 the internal structure of a BS may be split into a central unit (CU) and at least one distributed unit (DU) (e.g., two DUs shown in FIG. 3) .
  • CU central unit
  • DU distributed unit
  • the CU and DU are connected with each other by an interface called F1 as specified in 3GPP standard documents.
  • the radio resource control (RRC) layer functionality, service data adaptation protocol (SDAP) functionality, and the packet data convergence protocol (PDCP) layer functionality are included in the CU.
  • the radio link control (RLC) layer functionality, medium access control (MAC) layer functionality, and the physical (PHY) layer functionality are included in the DU.
  • the CU may be separated into a CU-control plane (CP) unit and at least one CU-user plane (UP) unit.
  • CP CU-control plane
  • UP CU-user plane
  • FIG. 4 is a schematic diagram illustrating an internal structure of a BS according to some other embodiments of the present application.
  • the CU may be separated into a CU-CP unit and at least one CU-UP unit.
  • the CU-CP unit and the CU-UP unit may be connected with each other by an interface called E1 as specified in 3GPP standard documents.
  • the CU-CP unit and the DU are connected by an interface called F1-C as specified in 3GPP documents.
  • the CU-UP unit and the DU are connected by an interface called F1-U as specified in 3GPP standard documents.
  • a SDT procedure is generally used to transmit data for a DRB for SDT, if a DRB for non-SDT (also be called “non-SDT DRB” is available in a UE in the SDT procedure, the UE needs to fallback to connected mode.
  • non-SDT DRB also be called “non-SDT DRB”
  • a buffer status report (BSR) for reporting non-SDT DRB is considered as one way to let the network side (a BS) know the arrival of a non-SDT DRB in UE side, then the network side could send a RRC resume message to the UE even not receiving the legacy RRC resume request message. That is, the BSR for reporting non-SDT DRB is a kind of implicit way to request for the UE fallback to the RRC connected mode, thus some details need to be specified so that this procedure can achieve the same performance as the legacy RRC resume request or RRC resume procedure.
  • FIG. 5 illustrates a flow chart of a method for fallback process for available data according to an embodiment of the present application.
  • the method is performed among a UE (such as, the UE 201 in FIG. 2) , a serving BS (such as, the BS 202a in FIG. 2) and a last serving BS (such as, the BS 202b in FIG. 2) .
  • a UE such as, the UE 201 in FIG. 2
  • a serving BS such as, the BS 202a in FIG. 2
  • a last serving BS such as, the BS 202b in FIG. 2 .
  • the UE transmits non-SDT available information to the serving BS (such as, DU of the serving BS, that is, serving BS DU as shown in FIG. 5) when a DRB or a SRB for non-SDT is available in a SDT procedure.
  • the serving BS such as, DU of the serving BS, that is, serving BS DU as shown in FIG. 5
  • the non-SDT available information may be non-SDT data available indication information for indicating the DRB or the SRB for non-SDT being available, or indicating non-SDT service being available.
  • the non-SDT data available indication information could be a message in RRC layer or in MAC layer. It could be a MAC CE.
  • the non-SDT available information may be a buffer status report (BSR) for non-SDT.
  • BSR buffer status report
  • the BSR for non-SDT may be a new MACCE.
  • the non-SDT available information may be a BSR for a separate logical channel group (LCG) for non-SDT.
  • LCG logical channel group
  • the non-SDT available information could be received from the NAS layer.
  • the UE may start a timer upon the non-SDT available information is transmitted to the serving BS or upon the non-SDT available information is transmitted to a lower layer.
  • the UE runs the timer in a MAC layer of the UE, and indicates expiry of the timer to an RRC layer of the UE.
  • the meaning of running here may include the starting and/or stopping.
  • An indication of stopping the timer could be received from the RRC layer if the RRC layer of the UE receives a RRC response message.
  • the UE may indicate the RRC layer of the UE to start the timer upon non-SDT available information in MAC layer is transmitted.
  • the UE may start or run the timer in the RRC layer of the UE upon the non-SDT data available indication information in RRC layer is transmitted.
  • the UE may stop the timer if the RRC layer of the UE receives a RRC response message or response message in MAC or PDCCH.
  • the UE may perform a RACH procedure to transmit an RRC resume request message to the serving BS.
  • the RACH procedure to transmit an RRC resume request message will apply the legacy RACH resource that is not the RACH resource for SDT.
  • the timer will stop if the UE receives the response message from the network.
  • the serving BS DU transmits the non-SDT available information to a CU of a serving BS (that is, the serving BS CU in FIG. 5) .
  • the serving BS CU transmits the non-SDT available information to the last serving BS (that is, CU of the last serving BS) .
  • the last serving BS is an anchor BS
  • the anchor BS is a BS which has connection with core network.
  • the CU of the last serving BS may determine to resume the DRB or the SRB for non-SDT (or resume the suspended DRB or SRB) , and transmit an indication to resume the DRB or the SRB for non-SDT or an indication to let the UE enter a RRC connected mode to the serving BS (such as, the serving BS CU) .
  • the last serving BS CU may firstly transmit the indication to resume the DRB or the SRB for non-SDT or an indication to let the UE enter a RRC connected mode to last serving BS DU, and then the lasting serving BS DU transmits the indication to the serving BS CU.
  • the transmission of the indication to resume the DRB or the SRB for non-SDT or an indication to let the UE enter a RRC connected mode to the last serving BS DU could be performed by UE context management message in an F1 interface. It could be UE Context Modification request or response, UE Context Setup request or response, UE Context Release request or response.
  • the last serving BS CU CP may transmit the indication to resume the DRB or the SRB for non-SDT or an indication to let the UE enter a RRC connected mode to last serving BS CU UP.
  • the transmission of the indication could be performed by Bear management message in an E1 interface. It could be Bearer Context Modification request or response, Bearer Context Setup request or response, Bearer Context Release request or response.
  • the serving BS CU may transmit the indication to resume the DRB or the SRB for non-SDT or an indication to let the UE enter a RRC connected mode to the serving BS DU, and in step 506, the serving BS DU transmits a RRC response message to the UE.
  • the RRC response message may be a RRC resume message, or a message which makes the UE enter the RRC connected mode.
  • the UE After receiving the RRC response message from the serving BS DU, the UE may enter the RRC connected mode and then in step 507 transmits RRC Resume Complete message to the serving BS DU.
  • the UE will perform at least one of the procedure, initiate the RACH procedure or CG based SDT, or move into idle mode.
  • a timer will be started or restarted if a BSR for SDT and or BSR for non-SDT is assembled or generated.
  • the RACH procedure could be one of the 2-step based SDT procedure, 4-step based SDT procedure, normal 2-step RACH procedure, normal 4-setp RACH procedure.
  • the normal RACH procedure could be legacy or non-ST procedure.
  • the last serving BS may could determine to trigger an anchor relocation, then it will send an anchor relocation indication to the serving BS.
  • the serving BS will determine to move the UE in a RRC connected mode, for example, transmit an RRC resume message to the UE after the path switching is finished.
  • Another method is to let the UE send a RRC resume request message for non-SDT in the UL granted resources for SDT.
  • FIG. 6 illustrates a flow chart of another method for fallback process for available data according to an embodiment of the present application.
  • the method is performed among a UE (such as, the UE 201 in FIG. 2) , a serving BS (such as, the BS 202a in FIG. 2) and a last serving BS (such as, the BS 202b in FIG. 2) .
  • a UE such as, the UE 201 in FIG. 2
  • a serving BS such as, the BS 202a in FIG. 2
  • a last serving BS such as, the BS 202b in FIG. 2 .
  • the UE transmits non-SDT available information to the serving BS (such as, DU of the serving BS, that is, serving BS DU as shown in FIG. 6) when a DRB or a SRB for non-SDT is available in a SDT procedure.
  • the serving BS such as, DU of the serving BS, that is, serving BS DU as shown in FIG. 6
  • the serving BS DU transmits the non-SDT available information to a CU of a serving BS (that is, the serving BS CU in FIG. 6) .
  • the serving BS transmits an indication to enable a UL grant resource for SDT transmission for an RRC resume request message to the UE.
  • the serving BS CU may transmit the indication to the UE via the serving BS DU.
  • the UE may transmit the RRC resume request message for resuming the DRB or the SRB for non-SDT on the UL grant resource to the serving BS.
  • the serving BS may transmit a UL grant resource for an RRC resume request message to the UE, and the UE may transmit the RRC resume request message on the UL grant resource.
  • the RRC resume request message comprises at least one of inactive-radio network temporary identifier (I-RNTI) of the UE, a resume cause, an authentication token and C-RNTI in RACH based SDT procedure or C-RNTI in CG based SDT procedure.
  • I-RNTI inactive-radio network temporary identifier
  • the RRC resume request message comprises at least one of resume cause for non-SDT transmission or with legacy information, null of I-RNTI, null of an authentication token, and null content of this message.
  • the resume cause is for non-SDT transmission.
  • the UE may resume the SRB or the DRB for non-SDT or the suspended SRB or DRB by using security keys used in the SDT procedure. For example, resuming of the SRB or the DRB for non-SDT or the suspended SRB or DRB could be performed before the UE sends the RRC resume request or after UE receives the RRC resume message.
  • the UE may multiplex the data for SDT DRB or SDT SRB with the RRC resume request message if the UL grant resource is allowed. In another embodiment, only the RRC resume request message could be transmitted in the UL grant resource.
  • the UE may multiplex the data for DRB or the SRB for non-SDT with the RRC resume request message and/or data for a DRB or a SRB for SDT if the UL grant resource is allowed.
  • the data for DRB or the SRB for non-SDT has a lower priority than that of the RRC resume request message and/or data for a DRB or a SRB for SDT.
  • the serving BS may identify the RRC resume request message for resuming the DRB or the SRB for non-SDT or suspended DRB or SRB by determining whether the RRC resume request message comprises at least one of I-RNTI of the UE, a resume cause, an authentication token and C-RNTI in RACH based SDT procedure or C-RNTI in CG based SDT procedure.
  • the serving BS may identify the RRC resume request message for resuming the DRB or the SRB for non-SDT or suspended DRB or SRB by determining whether the RRC resume request message comprises at least one of a resume cause for non-SDT transmission or with legacy information, null of I-RNTI, null of an authentication token, and null content of this message.
  • the serving BS will send a response message to UE.
  • the response message could be RRC resume message for SDT transmission, UE will be in inactive mode to perform the data transmission for SDT DRB and or SDT SRB if UE receive this RRC resume message for SDT transmission, or UE will be in inactive mode to perform the subsequent data transmission for SDT DRB and or SDT SRB if UE receives this RRC resume message for SDT transmission, or UE will be in inactive mode to perform the subsequent data transmission for SDT DRB and or SDT SRB and or not suspend the SDT DRB and or SDT SRB if UE receives this RRC resume message for SDT transmission.
  • RRC resume message for SDT could be named as the RRCResumeSDT or a new RRC message.
  • An explicit or implicit indication could be included in RRC resume message for SDT transmission to indicate UE perform the subsequent data transmission for SDT DRB and or SDT SRB in inactive mode.
  • An explicit or implicit indication could be included in RRC resume message for SDT transmission to indicate UE perform the subsequent data transmission for SDT DRB and or SDT SRB in inactive mode and or be without suspending the SDT DRB and or SDT SRB.
  • a base station will transmit the RRC response message to UE.
  • UE will monitor the PDCCH addressed by the TC-RNTI, C-RNTI or SDT-RNTI after UE receives the RRC resume message for SDT.
  • C-RNTI could be the C-RNTI based on the successful contention resolution in RACH based SDT or in CG based SDT.
  • the serving BS may identify the RRC resume request message for resuming the DRB or the SRB for non-SDT or suspended DRB or SRB by determining whether the RRC resume request message is transmitted in the SDT procedure.
  • the serving BS may identify the RRC resume request message for resuming the DRB or the SRB for non-SDT or suspended DRB or SRB by determining whether the RRC resume request message is transmitted without any DRB or the SRB for SDT.
  • the serving BS may transmit the RRC resume request message to the last serving BS (the last serving BS CU) .
  • the last serving BS is an anchor BS
  • the anchor BS is a BS which has connection with core network.
  • the RRC resume request message could be transmitted in UE context retrieve request message.
  • the last serving BS (such as, last serving BS CU) may determine to resume the DRB or the SRB for non-SDT (or resume the suspended DRB or SRB) , and transmit an indication to resume the DRB or the SRB for non-SDT or an indication to let the UE enter a RRC connected mode to the serving BS (such as, the serving BS CU) .
  • the last serving BS CU may firstly transmit the indication to resume the DRB or the SRB for non-SDT or an indication to let the UE enter a RRC connected mode to last serving BS DU, and then the lasting serving BS DU transmits the indication to the serving BS CU.
  • the transmission of the indication to resume the DRB or the SRB for non-SDT or an indication to let the UE enter a RRC connected mode to the last serving BS DU could be performed by UE context management message in an F1 interface. It could be UE Context Modification request or response, UE Context Setup request or response, UE Context Release request or response.
  • the last serving BS CU CP may transmit the indication to resume the DRB or the SRB for non-SDT or an indication to let the UE enter a RRC connected mode to last serving BS CU UP.
  • the transmission of the indication could be performed by Bear management message in an E1 interface. It could be Bearer Context Modification request or response, Bearer Context Setup request or response, Bearer Context Release request or response.
  • the serving BS CU may transmit the indication to resume the DRB or the SRB for non-SDT or an indication to let the UE enter a RRC connected mode to the serving BS DU, and in step 608, the serving BS DU transmits a RRC response message to the UE.
  • the RRC response message may be a RRC resume message, or a message which makes the UE enter the RRC connected mode.
  • the UE After receiving the RRC response message from the serving BS DU, the UE may enter the RRC connected mode and then in step 609 transmits RRC Resume Complete message to the serving BS DU.
  • the UE it is possible for the UE to use the legacy 2-step or 4-step RACH procedure to transmit an RRC resume request message for non-SDT DRB to the serving BS.
  • the legacy 2-step or 4-step RACH procedure to transmit an RRC resume request message for non-SDT DRB to the serving BS.
  • FIG. 7 illustrates a flow chart of another method for fallback process for available data according to an embodiment of the present application.
  • the method is performed among a UE (such as, the UE 201 in FIG. 2) , a serving BS (such as, the BS 202a in FIG. 2) and a last serving BS (such as, the BS 202b in FIG. 2) .
  • a UE such as, the UE 201 in FIG. 2
  • a serving BS such as, the BS 202a in FIG. 2
  • a last serving BS such as, the BS 202b in FIG. 2 .
  • step 701 the UE transmits non-SDT available information to (such as, serving BS DU as shown in FIG. 7) when a DRB or a SRB for non-SDT is available in a SDT procedure.
  • non-SDT available information such as, serving BS DU as shown in FIG. 7
  • step 702 after receiving the non-SDT available information from a user equipment (UE) , the serving BS DU transmits the non-SDT available information to a CU of a serving BS (that is, the serving BS CU in FIG. 7) .
  • a serving BS that is, the serving BS CU in FIG. 7
  • the serving BS transmits dedicated RACH preamble for a 2-step RACH procedure or a 4-step RACH procedure to the UE.
  • the serving BS CU transmits the dedicated RACH preamble to the serving BS DU, and then the serving BS DU transmits it to the UE.
  • the UE will suspend the DRB for SDT, and this also means that the serving BS and the last serving BS (which is also an anchor BS of the UE in this embodiment) also suspend the DRB for SDT in UE side.
  • the UE After receiving the dedicated RACH preamble, in step 704, the UE transmits an RRC resume request message for resuming the DRB or the SRB for non-SDT or suspended DRB or SRB to the serving BS by using the received RACH preamble.
  • the serving BS CU transmits the RRC resume request message to the last serving BS (the last serving BS CU) .
  • the last serving BS is an anchor BS
  • the anchor BS is a BS which has connection with core network.
  • the RRC resume request message could be transmitted in UE context retrieve request message.
  • the last serving BS (such as, last serving BS CU) may determine to resume the DRB or the SRB for non-SDT (or resume the suspended DRB or SRB) , and transmit an RRC response message (such as, an indication to resume the DRB or the SRB for non-SDT or an indication to let the UE enter a RRC connected mode) to the serving BS (such as, the serving BS CU) .
  • an RRC response message such as, an indication to resume the DRB or the SRB for non-SDT or an indication to let the UE enter a RRC connected mode
  • the last serving BS CU may firstly transmit the RRC response message to the last serving BS DU, and then the lasting serving BS DU transmits the RRC response message to the serving BS CU.
  • the transmission of the RRC response message to the last serving BS DU could be performed by a UE context management message in an F1 interface. It could be UE Context Modification request or response, UE Context Setup request or response, UE Context Release request or response.
  • the last serving BS CU CP may transmit the RRC response message to last serving BS CU UP.
  • the transmission of the RRC response message could be performed by Bear management message in an E1 interface. It could be Bearer Context Modification request or response, Bearer Context Setup request or response, Bearer Context Release request or response.
  • the serving BS CU may transmit the RRC response to the serving BS DU, and in step 708, the serving BS DU transmits a RRC response message to the UE.
  • the RRC response message may be a RRC resume message, or a message which makes the UE enter the RRC connected mode.
  • the UE After receiving the RRC response message from the serving BS DU, the UE may enter the RRC connected mode and then in step 709 transmits RRC Resume Complete message to the serving BS DU.
  • the UE after transmitting the non-SDT available information to the serving BS, the UE transmits an explicit or implicit indication to suspend the DRB or the SRB for SDT to the serving BS. And then the serving BS may transmit the indication to suspend (or a suspend request message) to the last serving BS, and then receive a response message to the indication to suspend (or the suspend request message) from the last serving BS.
  • the serving BS may send a suspend request on SRB or DRB for SDT (or release request on SDT SRB) to last serving BS (last serving BS CU) . It could be transmitted in UE context retrieve request message.
  • the serving BS may receive a response message to the suspend request on SRB or DRB for SDT (or release request on SDT SRB) to last serving BS (last serving BS CU) . It could be transmitted in a UE context retrieve response message.
  • the UE After transmitting the indication to suspend to the serving BS, the UE transmits an RRC resume request message.
  • the procedure of transmitting the RRC resume request message among the UE, the serving BS and the last serving BS is the same as the above description, which will not be described here.
  • the indication on resume request on SRB or DRB for non-SDT (SRB or DRB in UE RRC connected mode) and/or the suspend request on SRB or DRB for SDT (release request on SDT SRB) could be performed by the Xn interface message including as least one of UE context retrieve message, such as the UE context retrieve request message and UE context retrieve response message.
  • the UE after transmitting the non-SDT available information to the serving BS, transmits an RRC resume request message for resuming the DRB or the SRB for non-SDT or for resuming the suspended DRB or SRB in the 2-step RACH procedure or the 4-step RACH procedure, or a CG based SDT procedure.
  • the DRB or the SRB for SDT will not be suspended and the UE will continue to perform the transmission of the DRB or the SRB for SDT.
  • the UE may receive an explicit or implicit indication to suspend the DRB or the SRB for SDT from the serving BS; or after transmitting the non-SDT available information to the serving BS or receiving the RRC resume request or non-SDT available information from the upper layer, the UE may suspend the DRB or the SRB for SDT, and then the UE may transmit an RRC resume request message for resuming the DRB or the SRB for non-SDT in the 2-step RACH procedure, the 4-step RACH procedure, or a CG based SDT procedure (the procedure of transmitting the RRC resume request message among the UE, the serving BS and the last serving BS is the same as the above description, which will not be described here) .
  • the UE may transmit an RRC resume request message for resuming the DRB or the SRB for non-SDT multiplexed with the DRB or the SRB for SDT on a UL grant resource to the serving BS (the procedure of transmitting the RRC resume request message among the UE, the serving BS and the last serving BS is the same as the above description, which will not be described here) .
  • the UE may transmit an RRC resume request message for resuming the DRB or the SRB for non-SDT or resuming the suspended DRB or SRB.
  • RRC resume request message it could include the non-SDT available information.
  • the UE may transmit an RRC resume complete message multiplexed with the DRB or the SRB for SDT on a UL grant resource to the serving BS.
  • the RRC resume request message is transmitted by using a security key used in the SDT procedure.
  • the last serving BS CU For the last serving BS CU, in the above some embodiments, it will receive the non-SDT available information or a resume request message for the SRB or DRB for non-SDT (SRB or DRB in UE RRC connected mode) in UE, determine to resume the SRB or DRB for non-SDR (SRB or DRB in UE RRC connected mode) , and send a resume indication to last serving BS DU and serving BS (CU or DU) to resume the SRB or DRB for non-SDT (SRB or DRB in UE RRC connected mode) .
  • the last serving BS CU will receive suspend information for SRB or DRB for SDT, determine to suspend the SRB or DRB for SDT (release the SDT SRB) , and send a suspend indication to last serving BS DU and serving gNB (CU/DU) to suspend the SRB or DRB for SDT (or release the SDT SRB) .
  • the resume indication to resume the SRB or DRB for non-SDT (SRB or DRB in UE RRC connected mode) or the suspend instruction to suspend the SRB or DRB for SDT (or release the SRB or DRB for SDT) to the last serving BS DU could be realized by UE context management message in an F1 interface. It could be UE Context Modification request or response, UE Context Setup request or response, UE Context Release request or response.
  • the resume indication to resume the SRB or DRB for non-SDT (SRB or DRB in UE RRC connected mode) or the suspend instruction to suspend the SRB or DRB for SDT (release the SDT SRB) from last serving CU CP to last serving BS CU UP could be realized by Bear management message in an E1 interface. It could be Bearer Context Modification request or response, Bearer Context Setup request or response, Bearer Context Release request or response.
  • the SDT SRB (or the SRB for SDT) means the SRB established for SDT procedure.
  • the SDT SRB is used to transmit a RRC resume request (RRCResumeRequest) for SDT DRB or receive the corresponding response message, or the RRC message for CG resource request or configuration in SDT procedure, or the RRC release message for SDT procedure.
  • RRC resume request RRCResumeRequest
  • non-SDT SRB means the SRB established to transmit the RRC message for non-SDT DRB, or the legacy SRB for UE in connected mode.
  • the non-SDT SRB is used to transmit the RRC resume request (RRCResumeRequest) initiated by non-SDT DRB arriving.
  • the non-SDT DRB or DRB for non-SDT means the DRB should be transmitted in RRC connected mode.
  • the SDT DRB or DRB for SDT means the DRB could be transmitted in UE inactive mode or UE idle mode.
  • the embodiments of the present application can make the UE fallback to an RRC connected mode in a case that a DRB or SRB for non-SDT is available in a SDT procedure.
  • FIG. 8 illustrates an apparatus according to some embodiments of the present application.
  • the apparatus 1000 may be the UE 101 as illustrated in FIG. 1, the UE 201 as illustrated in FIG. 2 or other embodiments of the present application.
  • the apparatus 800 may include a receiver 801, a transmitter 803, a processer 805, and a non-transitory computer-readable medium 807.
  • the non-transitory computer-readable medium 807 has computer executable instructions stored therein.
  • the processer 805 is configured to be coupled to the non-transitory computer readable medium 807, the receiver 801, and the transmitter 803.
  • the apparatus 800 may include more computer-readable mediums, receiver, transmitter and processors in some other embodiments of the present application according to practical requirements.
  • the receiver 801 and the transmitter 803 are integrated into a single device, such as a transceiver.
  • the apparatus 800 may further include an input device, a memory, and/or other components.
  • the non-transitory computer-readable medium 807 may have stored thereon computer-executable instructions to cause the processer 805 to implement the method according to embodiments of the present application.
  • FIG. 9 illustrates another apparatus according to some embodiments of the present application.
  • the apparatus 800 may be the BS 102 as illustrated in FIG. 1, the BS 202 as illustrated in FIG. 2 or other embodiments of the present application.
  • the apparatus 900 may include a receiver 901, a transmitter 903, a processer 905, and a non-transitory computer-readable medium 907.
  • the non-transitory computer-readable medium 907 has computer executable instructions stored therein.
  • the processer 905 is configured to be coupled to the non-transitory computer readable medium 907, the receiver 901, and the transmitter 903.
  • the apparatus 900 may include more computer-readable mediums, receiver, transmitter and processors in some other embodiments of the present application according to practical requirements.
  • the receiver 901 and the transmitter 903 are integrated into a single device, such as a transceiver.
  • the apparatus 900 may further include an input device, a memory, and/or other components.
  • the non-transitory computer-readable medium 907 may have stored thereon computer-executable instructions to cause a processor to implement the method according to embodiments of the present application.
  • a software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
  • the steps of a method may reside as one or any combination or set of codes and/or instructions on a non-transitory computer-readable medium, which may be incorporated into a computer program product.
  • the terms “comprises, “ “comprising, “ or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
  • An element proceeded by “a, “ “an, “ or the like does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises the element.
  • the term “another” is defined as at least a second or more.
  • the terms “including, “ “having, “ and the like, as used herein, are defined as “comprising. "

Landscapes

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

Abstract

L'invention concerne un procédé comprenant les étapes suivantes: la transmission d'information de non-disponibilité de transmission de petites quantités données (SDT) à une station de base de desserte (BS) dans le cas où un support radio de transmission données (DRB) ou un support radio de signalisation (SRB) pour une transmission de petites quantités de données (SDT) n'est pas disponible dans une procédure de transmission SDT ou la réception d'une information de transmission SDT non disponible; la réception d'un message de commande de ressource radio (RRC) provenant de la station de base de desserte; et la transition vers un mode connecté de commande RRC, un mode inactif ou un mode repos sur la base du message de réponse de commande RRC.
PCT/CN2021/071546 2021-01-13 2021-01-13 Procédé et appareil pour un traitement de secours pour des données disponibles WO2022151068A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/071546 WO2022151068A1 (fr) 2021-01-13 2021-01-13 Procédé et appareil pour un traitement de secours pour des données disponibles

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/071546 WO2022151068A1 (fr) 2021-01-13 2021-01-13 Procédé et appareil pour un traitement de secours pour des données disponibles

Publications (1)

Publication Number Publication Date
WO2022151068A1 true WO2022151068A1 (fr) 2022-07-21

Family

ID=82446637

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/071546 WO2022151068A1 (fr) 2021-01-13 2021-01-13 Procédé et appareil pour un traitement de secours pour des données disponibles

Country Status (1)

Country Link
WO (1) WO2022151068A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024065641A1 (fr) * 2022-09-30 2024-04-04 Qualcomm Incorporated Gestion de connexion pour petites transmissions de données et transmissions de données non petites

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180139778A1 (en) * 2016-11-11 2018-05-17 Chie-Ming Chou Data packet delivery in rrc inactive state
US20190191483A1 (en) * 2016-08-11 2019-06-20 Samsung Electronics Co., Ltd. Low power rrc operating method and device
US20200128484A1 (en) * 2018-10-18 2020-04-23 Apple Inc. Inactive Mode Operations
US20200162897A1 (en) * 2018-04-16 2020-05-21 Telefonaktiebolaget Lm Ericsson (Publ) Security handling for rrc resume from inactive state
US20200214070A1 (en) * 2017-06-14 2020-07-02 Samsung Electronics Co., Ltd Method and user equipment (ue) for reconnecting rrc connection with radio access network (ran) node

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190191483A1 (en) * 2016-08-11 2019-06-20 Samsung Electronics Co., Ltd. Low power rrc operating method and device
US20180139778A1 (en) * 2016-11-11 2018-05-17 Chie-Ming Chou Data packet delivery in rrc inactive state
US20200214070A1 (en) * 2017-06-14 2020-07-02 Samsung Electronics Co., Ltd Method and user equipment (ue) for reconnecting rrc connection with radio access network (ran) node
US20200162897A1 (en) * 2018-04-16 2020-05-21 Telefonaktiebolaget Lm Ericsson (Publ) Security handling for rrc resume from inactive state
US20200128484A1 (en) * 2018-10-18 2020-04-23 Apple Inc. Inactive Mode Operations

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
EMAIL DISCUSSION RAPPORTEUR (ZTE CORPORATION): "Agreeable details of RRC-based solution for SDT (RACH and CG)", 3GPP DRAFT; R2-2009189, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. e-Meeting; 20201102 - 20201113, 22 October 2020 (2020-10-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051941253 *
SESSION CHAIR (INTERDIGITAL): "Report for Rel-16 (NR-U, Power Savings and 2-step RACH) and IIoT and Small Data", 3GPP DRAFT; R2-2010704, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20201101, 16 November 2020 (2020-11-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051954527 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024065641A1 (fr) * 2022-09-30 2024-04-04 Qualcomm Incorporated Gestion de connexion pour petites transmissions de données et transmissions de données non petites

Similar Documents

Publication Publication Date Title
US20220007426A1 (en) Random access method and device
US20230362881A1 (en) Methods and apparatuses for a relay reselection and data transmission handling procedure in a ue-to-network relay scenario
US20230413207A1 (en) Methods and apparatuses for handling time alignment for a small data transmission procedure
US20230413345A1 (en) Method and apparatus for small data transmission
US20230141380A1 (en) Method and apparatus for sidelink resource re-evaluation
WO2022151068A1 (fr) Procédé et appareil pour un traitement de secours pour des données disponibles
CN116636253A (zh) 小数据传输过程的移动性
EP4175397A1 (fr) Demande de planification et déclenchement d'accès aléatoire pour sdt
WO2022151239A1 (fr) Procédé et appareil de traitement de transmission de données
US20230328835A1 (en) Methods and apparatuses for a data transmission and a rnau procedure of a ue in rrc inactive state
WO2022082522A1 (fr) Procédé et appareil de transmission de données subséquente
WO2021223191A1 (fr) Procédé d'envoi d'informations, procédé de réception d'informations, terminal et dispositif de réseau
WO2022155961A1 (fr) Procédé et appareil pour configurer des temporisateurs et effectuer une transmission de données dans une procédure sdt
JP2023519396A (ja) 端末デバイスによって実行される方法、及び端末デバイス
CN114271015A (zh) 一种信息指示方法及装置、终端设备、网络设备
WO2022104589A1 (fr) Procédé et appareil pour la transmission de petites données
WO2022120570A1 (fr) Procédé et appareil de rapport de ressource d'autorisation configurée
WO2022205266A1 (fr) Procédé et appareil de transmission de données dans un état non connecté
WO2022205344A1 (fr) Procédé et appareil de gestion de l'arrivée d'une transmission de non petites données
WO2022134027A1 (fr) Procédé et appareil pour un traitement d'informations dans une procédure de transmission de petites données
US20240057172A1 (en) Methods and apparatuses for a user equipment (ue) triggered secondary cell group (scg) activation procedure
WO2022082584A1 (fr) Procédés et appareils pour un mécanisme de désactivation de scg et un mécanisme d'activation de scg dans un scénario mr-dc
WO2024065529A1 (fr) Procédés et appareils pour un mécanisme d'amélioration de surveillance de pdcch pour un trafic xr
WO2022193128A1 (fr) Procédés et appareils pour une procédure de traitement de rlf et une procédure de phr en cas de sn désactivé
US20240073968A1 (en) Method and apparatus for handling fallback of data transmission

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 31.10.2023)