WO2022205360A1 - Procédé et appareil de notification de position et de transmission de petites données dans un état inactif de commande de ressources radio - Google Patents

Procédé et appareil de notification de position et de transmission de petites données dans un état inactif de commande de ressources radio Download PDF

Info

Publication number
WO2022205360A1
WO2022205360A1 PCT/CN2021/085067 CN2021085067W WO2022205360A1 WO 2022205360 A1 WO2022205360 A1 WO 2022205360A1 CN 2021085067 W CN2021085067 W CN 2021085067W WO 2022205360 A1 WO2022205360 A1 WO 2022205360A1
Authority
WO
WIPO (PCT)
Prior art keywords
rnau
sdt
rrc
timer
resource
Prior art date
Application number
PCT/CN2021/085067
Other languages
English (en)
Inventor
Lianhai WU
Jie Shi
Ran YUE
Haiming Wang
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/085067 priority Critical patent/WO2022205360A1/fr
Publication of WO2022205360A1 publication Critical patent/WO2022205360A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices

Definitions

  • the present disclosure relates to methods and apparatus for location notification and small data transmission (SDT) when a user equipment (UE) stays in radio resource control (RRC) inactive state.
  • SDT location notification and small data transmission
  • UE user equipment
  • RRC radio resource control
  • RRC_Connected UE will enter RRC_INACTIVE state if the UE receives the RRCRelease message with suspendConfig.
  • RRC_INACTIVE is a state where a UE has a connection with the serving cell and access and the mobility management function (AMF) and can move within an area configured by a radio access network (RAN) without notifying the RAN.
  • AMF mobility management function
  • RAN radio access network
  • the last serving Generalized NodeB (gNB) node keeps the UE context and the UE-associated connection with the serving AMF and the user plane function (UPF) .
  • UPF user plane function
  • the base station may configure the UE with a periodic RAN notification area (RNA) update (RNAU) timer value.
  • RNA RAN notification area
  • the RAN node uses a guard timer with a value longer than the RNAU timer value provided to the UE.
  • the gNB in the RAN shall initiate a release procedure if the periodic RNAU guard timer expires.
  • a UE in the RRC_INACTIVE state will initiate RNA update procedure when it moves out of the configured RNA or when the RNAU timer expires.
  • SDT may be enabled when a UE is in the RRC_INACTIVE state; that is to say, when the UE is in the RRC_INACTIVE state, the UE may send multiple uplink (UL) packets and downlink (DL) packets as part of the same SDT mechanism and without transitioning to the RRC_CONNECTED state on dedicated grant.
  • the UE may perform SDT when it is in the RRC_INACTIVE state or in the RRC_CONNECTED state.
  • SDT may be performed by random access channel (RACH) resource or by configured grant (CG) resource.
  • RACH random access channel
  • CG configured grant
  • a method performed by a UE includes: receiving an RRC Release message including at least a suspend indication and an RNAU timer, starting the RNAU timer, and initiating a SDT procedure and transmitting a RRC resume request in response to UL data arrival associated with data radio bearer (DRB) , wherein the DRB is configured with SDT.
  • RRC Release message including at least a suspend indication and an RNAU timer
  • starting the RNAU timer starting the RNAU timer
  • RRC resume request in response to UL data arrival associated with data radio bearer (DRB) , wherein the DRB is configured with SDT.
  • DRB data radio bearer
  • the UL data is transmitted in RACH resource or in CG resource.
  • the RRC Release message further includes at least one of: specific RACH resource for small data transmission, or CG resource for small data transmission.
  • the method further includes, in response to initiating RACH for SDT and performing random access procedure for SDT, the method further comprises: stopping random access procedure for RNAU.
  • the method further includes, in response to initiating RACH for SDT and performing random access procedure for RNAU, wherein a RRC resume request for RNAU being not transmitted, the method further comprises: stopping random access procedure for RNAU.
  • the method further includes: restarting the RNAU timer in response to transmitting the RRC resume request for SDT, or stopping the RNAU timer in response to transmitting the RRC resume request for SDT.
  • a method performed by a UE includes: receiving a radio resource control (RRC) Release message including at least a suspend indication and a radio access network (RAN) notification area update (RNAU) timer, starting the RNAU timer in response to receiving the RNAU timer, and initiating RNAU procedure in response to RNAU timer expiry.
  • RRC radio resource control
  • RAN radio access network
  • RNAU notification area update
  • the RRC Release message further includes at least one of: specific RACH resource for small data transmission SDT, and CG resource for SDT.
  • the method further includes transmitting a RRC resume request including UL data indication in response to UL data arrival associated with DRB, wherein the DRB is configured for SDT.
  • the method further includes: transmitting a RRC resume request including the cause of RAN notification area (RNA) update using configured grant resource, in response to the RRC Release message including CG resource for SDT.
  • RNA RAN notification area
  • the method further includes: transmitting an RRC resume request including the cause indicating RNA update and UL data using CG resource, in response to the RRC Release message including CG for SDT and UL data arrival associated with DRB, wherein the DRB is configured for SDT.
  • a method performed by a network includes: transmitting an RRC Release message including at least a suspend indication and a radio access network (RAN) notification area update (RNAU) timer, and starting a RNAU guard timer.
  • RRC Release message including at least a suspend indication and a radio access network (RAN) notification area update (RNAU) timer, and starting a RNAU guard timer.
  • RAN radio access network
  • RNAU notification area update
  • the method further includes: receiving data associated with DRB, wherein DRB is configured with SDT, and restarting the RNAU guard timer in response to UL data arrival associated with DRB, wherein DRB is configured with small data transmission from UE.
  • the method further includes: receiving data associated with DRB, wherein DRB is configured with small data transmission, and stopping the RNAU guard timer in response to data arrival associated with DRB, wherein DRB is configured with small data transmission from UE.
  • the method further includes: the data is received in RACH resource or in CG resource.
  • an apparatus includes a non-transitory computer-readable medium having stored thereon computer-executable instructions, a receiving circuitry, a transmitting circuitry, and a processor coupled to the non-transitory computer-readable medium, the receiving circuitry and the transmitting circuitry, and the computer-executable instructions are executable by the processor to cause the apparatus to implement various methods according embodiments of the present application.
  • Figure 1 illustrates an exemplary method 100 performed by a UE according to the present disclosure.
  • Figure 2 illustrates an exemplary signaling sequence according to method 100.
  • Figure 3 illustrates an exemplary signaling sequence according to method 100.
  • Figure 4 illustrates an exemplary method 400 performed by a UE according to the present disclosure.
  • Figure 5 illustrates an exemplary signaling sequence according to method 400.
  • Figure 6 illustrates an exemplary signaling sequence according to method 400.
  • Figure 7 illustrates an exemplary method 700 performed by a base station (BS) or a network according to the present disclosure.
  • BS base station
  • Figure 8 illustrates an exemplary method 800 performed by a BS or a network according to the present disclosure.
  • Figure 9 illustrates an exemplary method 900 performed by a BS or a network according to the present disclosure.
  • Figure 10 illustrates an exemplary method 1000 performed by a BS or a network according to the present disclosure.
  • Figure 11 illustrates an exemplary signaling sequence according to method 1000.
  • Figure 12 illustrates an example apparatus according to some embodiments of the present disclosure.
  • Figure 13 illustrates an example apparatus according to some embodiments of the present disclosure.
  • the present disclosure relates to relates to methods and apparatus for location notification and SDT when a UE stays in RRC inactive state, wherein the location notification includes RNAU.
  • RNAU aims to notify the RAN with the UE location
  • SDT can also be used to notify the RAN instead of RNAU.
  • a UE may be configured with both the RNAU functionality and SDT functionality; accordingly, there may be some factors that need to be considered, such as: whether can the SDT procedure be triggered during RNAU procedure? whether can RNAU be transmitted by CG resource rather than RACH resource if CG resource is configured for an inactive UE? how to handle the RNAU timer in a case of subsequence SDT procedure
  • Figure 1 illustrates an exemplary method 100 performed by a UE configured with both SDT functionality and RNAU functionality.
  • the method 100 includes at least an operation 110, an operation 120, and an operation 130.
  • the operation 110 illustrates receiving an RRC release message including at least a suspend indication and an RNAU timer.
  • the operation 120 illustrates starting the RNAU timer.
  • the operation 130 illustrates initiating an SDT procedure and transmitting an RRC resume request in response to UL data arrival associated with DRB, wherein the DRB is configured for SDT.
  • the UE enters an RRC inactive state upon the reception of RRC release message including at least a suspend indication.
  • the UE may initiate a procedure for RNAU if the RNAU timer expires.
  • the UL data may be transmitted in RACH resource or in CG resource.
  • the RRC release message may further include specific RACH resource for SDT.
  • the RRC release message may further include CG resource for SDT.
  • the RRC release message may further includes both the specific RACH resource for SDT and CG resource for SDT.
  • method 100 in response to initiating RACH for SDT and performing random access (RA) procedure for SDT, further includes stopping RA procedure for RNAU.
  • RA random access
  • the method 100 in response to initiating RACH for SDT and performing RA procedure for SDT, wherein an RRC resume request for RNAU being not transmitted, the method 100 further includes stopping RA procedure for RNAU.
  • the method 100 may further include restarting the RNAU timer in response to transmitting the RRC resume request for SDT.
  • the RRC resume request for SDT includes a cause indicating UL data.
  • One of the advantages is to avoid restarting the RNAU timer frequently, especially in a case of subsequence SDT. Taking into account the case of subsequence SDT, that is, UL data is too large to be transmitted together with the RRC Resume request for SDT, then part of UL data may be transmitted multiplexed with the RRC Resume request, the rest may be transmitted in segments later. Each time the BS receives a part or segment of the UL data, it may send a confirmation to the UE. If the UE restarts the RNAU timer upon reception of the confirmation, the RNAU timer might be started too frequently.
  • the method 100 may further include stopping the RNAU timer in response to transmitting the RRC resume request for SDT.
  • the UE initiates the SDT procedure, it stops the RNAU timer.
  • the UE does not start the RNAU timer, i.e., the RNAU timer is not running. Only after the SDT procedure ends, the RNAU functionality may begin to work.
  • One of the advantages is to avoid start and stop RNAU timer frequently, especially in a case of subsequence SDT.
  • the UE may perform RACH for SDT.
  • the UE may stop the RNAU timer.
  • the UE may perform RA procedure for SDT or RACH for SDT.
  • the UE may stop the RNAU timer.
  • the UE may release the RNAU timer.
  • the BS sends an RRC Release message includes at least the suspend indication and a RNAU timer
  • the UE may start the received RNAU timer.
  • the BS may send an RRC Release message including at least the suspend indication and a RNAU timer.
  • Figure 2 illustrates an exemplary signaling sequence according to method 100, herein the UE is in RRC inactive state in response to receiving an RRC Release message, and the RRC Release message includes at least a suspend indication, and an RNAU timer.
  • CG resource for SDT and/or specific RACH resource for SDT may be included in the RRC Release message.
  • the RNAU timer expires, and the UE may initiate an RA procedure for RNAU in response to the RNAU timer expiry.
  • the UL data arrives in UE before the UE transmits an RRC Resume request for RNAU, and then the UE stops the RA procedure for RNAU, and performs a SDT procedure.
  • the UE stops the RA procedure when performing the SDT; at the end of SDT, if the BS still determines to set the UE in RRC Inactive state, the BS may transmit an RRC Release message including at least an RNAU timer and a Suspend indication. The UE may start the received RNAU timer.
  • the SDT may be performed in RACH resource if the RACH resource is configured.
  • the SDT may be performed in CG resource if the CG resource is configured.
  • At least part of the UL data is multiplexed with the RRC Resume request message.
  • the UL data multiplexed with the RRC Release request message are included in Msg 3 or in Msg A.
  • the UL data multiplexed with the RRC Release request message are transmitted in a preconfigured uplink resource (PUR) without performing an RA procedure.
  • PUR preconfigured uplink resource
  • Figure 2 is an exemplary embodiment according to the present disclosure.
  • the time sequence is not strictly limited as shown in Figure 2. For example, if the RNAU timer expires, and the UL data arrives before the RRC Resume request for RNAU is transmitted, the UE may first stop the RA procedure for RNAU first, and then transmit the RRC Resume request for SDT multiplexed with UL data, or the UE may first transmit the RRC Resume request for SDT multiplexed with UL data, and then stop the RA procedure for RNAU.
  • Figure 2 merely illustrates signaling or procedures that embody the spirit of the present disclosure, it does not illustrates all the signaling or procedures involved.
  • Figure 3 illustrates an exemplary signaling sequence according to method 100, herein the UE is in RRC inactive state in response to receiving an RRC Release message, and the RRC Release message includes at least a Suspend indication and an RNAU timer.
  • the RNAU timer expires, and the UE may initiate an RACH procedure for RNAU.
  • the UE imitates the RACH procedure for RNAU and transmits an RRC Resume request for RNAU.
  • the RRC resume request for RNAU includes a cause indicating RNA update.
  • the UL data arrives; however, the UE continues to perform the RA procedure for RNAU.
  • the BS determines to let the UE to still be in RRC Inactive state, the BS transmits the RRC Resume request including at least a Suspend indication. Then the UE may initiate the procedure for SDT and transmits an RRC Resume request for SDT multiplexed with UL data.
  • the SDT procedure may be performed in RACH resource if the RACH resource is configured, wherein the RACH resource may be included in the RRC Release message.
  • the SDT may be performed in CG resource if the CG resource is configured, wherein the CG resource may be included in the RRC Release message.
  • a solution is provided about how to process UL data before or during an RA procedure for RNAU, that is, whether the UE performs SDT procedure or RNAU procedure depends on a chronological order between the UL data arrival and the transmission of the RRC Resume request for RNAU.
  • the UE may perform SDT procedure instead of RNAU procedure.
  • the SDT may be performed in CG resource or in RACH resource.
  • the UE may continue the RACH procedure for RNAU. After the RACH procedure for RNAU, if the UE still be in RRC Inactive state, the UE may initiate a procedure for SDT.
  • the SDT may be performed in CG resource or in RACH resource.
  • the RNAU procedure may be performed in RACH resource, and the SDT procedure may be performed in RACH resource or in CG resource.
  • the RNAU procedure may be performed in CG resource.
  • Figure 4 illustrates an exemplary method 400 performed by a UE configured with both SDT functionality and RNAU functionality.
  • the method 400 includes at least an operation 410, an operation 420, and an operation 430.
  • the operation 110 illustrates receiving an RRC Release message including at least a suspend indication and an RNAU timer.
  • the operation 120 illustrates starting the RNAU timer in response to receiving the RNAU timer.
  • the operation 130 illustrates initiating RNAU procedure in response to RNAU timer expiry.
  • the RRC Release message further includes at least CG resource for SDT.
  • the RRC Release message includes at least the CG resource.
  • the RRC Release message further includes specific RACH resource for SDT.
  • the UE enters an RRC inactive state upon the reception of RRC release message including at least a suspend indication.
  • the UE may use CG resource to transmit the RRC Resume request indicating at least RNA update and UL data.
  • the time threshold is configured or predefined.
  • the method 400 further includes transmitting an RRC resume request including a cause indicating UL data in response to arrival of UL data associated with DRB, wherein the DRB is configured for SDT.
  • the RRC Release message includes at least an RNAU timer, a Suspend indication, and CG resource for SDT, in response to the RNAU timer expiry, the method 400 further includes transmitting an RRC resume request in CG resource, herein the RRC resume request includes at least a cause indicating RNA update.
  • the RRC Release message includes at least an RNAU timer, a Suspend indication, and CG resource for SDT.
  • the method 400 further includes, after the RNAU time expires and UL data arrives associated with DRB, transmitting an RRC resume request in CG resource, herein the RRC resume request includes a cause indicating both RNA update and UL data.
  • the RRC Release message includes at least an RNAU timer, a Suspend indication, and CG resource for SDT.
  • the method 400 further includes, after the RNAU time expires and UL data arrives associated with DRB, transmitting an RRC resume request in CG resource, herein the RRC resume request includes at least two causes, one indicates RNA update, and another indicates UL data.
  • RNAU may be transmitted in CG resource, or may be transmitted together with UL data in CG resource.
  • Figure 5 illustrates an exemplary signaling sequence according to method 400, herein the UE is in RRC inactive state in response to receiving an RRC Release message, and the RRC Release message includes at least a suspend indication, an RNAU timer, and CG resource.
  • the RNAU timer expires, and the UE may initiate a procedure for RNAU.
  • CG resource is configured, CG is enabled in the serving cell, the UE may transmit an RRC Resume request including a cause in CG resource, wherein the cause indicates RNA update. If the BS decides to let UE to still be in RRC Inactive state, the BS may transmit an RRC Connection Release including a Suspend indication to the UE.
  • the time interval between RNAU timer expiry and the latest CG occasion is less than a time threshold configured or predefined
  • the UE may use CG resource to transmit the RRC Resume request indicating at least the RNA update.
  • the present disclosure provide a solution for transmitting an RNA update in a PUR without performing an RACH procedure.
  • the advantages are, e.g., to reduce signaling overhead and simplifying the RNAU procedure.
  • Figure 6 illustrates an exemplary signaling sequence according to method 400, herein the UE is in RRC inactive state in response to receiving a RRC Release message, and the RRC Release message includes at least a suspend indication, an RNAU timer, and CG resource.
  • the RNAU timer expires, and UL data arrives.
  • CG resource is configured, CG functionality is enabled in the serving cell, the UE may transmit an RRC Resume request indicating both RNA update and UL data in response to UL data arrival and RNAU timer expiry. If the BS decides to let UE to still be in RRC Inactive state, the BS may transmit an RRC Connection Release including a Suspend indication to the UE.
  • the RRC Resume request includes a cause indicating both RNA update and UL data.
  • the RRC Resume request includes two causes, one indicates RNA update, and another indicates UL data.
  • the RNAU timer expiry and the UL data arrival may occur at the same time or are much closed to each other.
  • the RNAU timer may occur before the UL data arrival and the time interval meets certain conditions.
  • the time interval between RNAU timer expiry and the latest CG occasion can be less than a time threshold configured or predefined, then the RNAU procedure may be performed in CG resource.
  • method 400 and embodiments illustrated in Figures 5 and 6 provide a solution for perform RNAU procedure in CG resource. It allows transmitting an RNA update in a preconfigured uplink resource (PUR) of CG resource without performing an RACH procedure.
  • PUR preconfigured uplink resource
  • the BS may send a RNAU timer with a value to the UE via an RRC Release message.
  • the BS uses a periodic RNAU guard timer with a period value longer than the period value of the RNAU timer provided to the UE.
  • the gNB in the RAN shall initiate a release procedure if the periodic RNAU guard timer expires.
  • Figure 7 illustrates an exemplary method 700 performed by a BS (or a network) , herein the CG/SDT functionality and RACH functionality are enabled in the serving cell.
  • the method 700 includes at least an operation 710 and an operation 720.
  • the operation 710 illustrates transmitting an RRC Release message including at least a suspend indication and an RNAU timer.
  • the operation 720 illustrates starting an RNAU guard timer.
  • the UE restarts the RNAU timer in response to perform SDT procedure.
  • the BS receives an RRC Resume request indicating SDT (e.g., including a cause indicating SDT) , it may restart the periodic RNAU guard timer accordingly.
  • Figure 8 illustrates an exemplary method 800 based on method 700.
  • the method 800 includes at least an operation 810 and an operation 820.
  • the operation 810 illustrates receiving data associated with DRB, wherein DRB is configured with SDT.
  • the operation 820 illustrates restarting the RNAU guard timer in response to UL data arrival associated with DRB, wherein DRB is configured with SDT.
  • the UL data is received in RACH resource or in CG resource.
  • an RRC Resume request is also received.
  • the RRC Resume request includes at least one cause, the cause at least indicating the UL data.
  • the at least one cause includes a cause indicating the UL data and a cause indicating an RNA update if the CG resource is used for both SDT and the RNAU.
  • the at least one cause includes a cause indicating both the UL data and an RNA update if the CG resource is used for both SDT and the RNAU.
  • the UE stops the RNAU timer in response to perform SDT procedure.
  • the BS receives an RRC Resume request indicating SDT (e.g., including a cause indicating SDT) , it may stop the periodic RNAU guard timer accordingly.
  • Figure 9 illustrates an exemplary method 900 based on method 700.
  • the method 900 includes at least an operation 910 and an operation 920.
  • the operation 910 illustrates receiving UL data associated with DRB, wherein DRB is configured with SDT.
  • the operation 920 illustrates stop the RNAU guard timer in response to the arrival of the UL data associated with DRB, wherein DRB is configured with SDT.
  • the UL data is received in RACH resource or in CG resource.
  • an RRC Resume request is also received.
  • the RRC Resume request includes at least one cause, the cause at least indicating the UL data.
  • the at least one cause includes a cause indicating the UL data and a cause indicating an RNA update if the CG resource is used for both SDT and the RNAU.
  • the at least one cause includes a cause indicating both the UL data and an RNA update if the CG resource is used for both SDT and the RNAU.
  • the BS may send a RNAU timer to the UE via an RRC Release message (if the SDT is performed in RACH resource) or in RRC Connection Release message (if the SDT is performed in CG resource) , at the same time, the BS may restart the RNAU guard timer.
  • Figure 10 illustrates an exemplary method 1000 based on method 700.
  • the method 1000 includes at least an operation 1010, an operation 1020, an operation 1030, and an operation 1040.
  • the operation 1010 illustrates receiving UL data associated with DRB, wherein DRB is configured with SDT.
  • the operation 1020 illustrates stop the RNAU guard timer in response to arrival of the UL data associated with DRB, wherein DRB is configured with SDT.
  • the operation 1030 illustrates transmitting, at the end of the SDT procedure, an RRC Release (or an RRC Connection Release) which includes at least a Suspend indication and an RNAU timer.
  • the operation 1040 illustrates starting the RNAU guard timer.
  • the UL data is received in RACH resource or in CG resource.
  • the BS in the operation 910, also receives an RRC Resume request.
  • the RRC Resume request includes at least one cause, the cause at least indicating the UL data.
  • the at least one cause includes a cause indicating the UL data and a cause indicating an RNA update if the CG resource is used for both SDT and the RNAU.
  • the at least one cause includes a cause indicating both the UL data and an RNA update if the CG resource is used for both SDT and the RNAU.
  • Figure 11 illustrates an exemplary signaling sequence according to method 1000, herein the UE is in RRC inactive state.
  • the BS receives an RRC Resume request for SDT multiplexed with UL data in CG resource or in RACH resource.
  • the BS stops the RNAU guard timer.
  • the UE stops the RNAU timer in response to transmission of the RRC Resume request multiplexed with UL data.
  • the BS decides to let the US to still be in RRC Inactive state. If CG resource is used for SDT, the BS sends RRC Connection Release including a Suspend indication and a RNAU timer to the UE; or if RACH resource is used for SDT, the BS send RRC Release including a Suspend indication and RNAU timer to the UE.
  • the UE After receiving the RNAU timer, the UE starts the RNAU timer.
  • the BS may not need to send an RNAU timer to UE again when the BS transmits RRC Release at the end of the SDT procedure.
  • Methods 700, 800, 900, and 1000, and Figure 11, and various embodiments provide a solution performed by the BS about handling the RNAU guard timer in SDT case.
  • a mechanism that SDT procedure can be triggered during RNAU is provided.
  • One of the advantages is to save the signaling.
  • the RNAU may be transmitted by CG resource rather than RACH procedure if CG resource is configured for inactive UE.
  • One of the advantages is to avoid initiating an RA procedure so as to reduce the signaling overhead.
  • the RNAU timer may restart or stop in response to transmitting RRC Resume request.
  • This solution performed in UE side avoids restart the RNAU timer too frequently, it is very helpful especially in case of subsequence SDT procedure.
  • One of the advantages is to optimizing the network functionality and simplifying the operations. Meanwhile, the solution about the RNAU guard timer on the BS side is also provided accordingly.
  • Figure 12 illustrates an exemplary apparatus 1200 for performing various methods (e.g., methods 100 and 400) and embodiments performed on UE side.
  • the exemplary apparatus 1200 may be at least a part of a UE.
  • the apparatus 1200 may include at least one receiving circuitry 1210, at least one processor 1220, at least one non-transitory computer-readable medium 1230 with computer-executable program code 1240 stored thereon, and at least one transmitting circuitry 1250.
  • the at least one non-transitory computer-readable medium 1230 and the computer-executable program code 1240 may be configured to, with the at least one processor 1220, cause the apparatus 1200 at least to perform at least the example methods (e.g., methods 100 or 400) and various embodiments described above.
  • Figure 13 illustrates an example apparatus 1300 for performing the method 800, which, for example, may be at least a part of a BS.
  • the apparatus 1300 may include at least one receiving circuitry 1310, at least one processor 1320, at least one non-transitory computer-readable medium 1330 with computer-executable program code 1340 stored thereon, and at least one transmitting circuitry 1350.
  • the at least one non-transitory computer-readable medium 1330 and the computer-executable program code 1340 may be configured to, with the at least one processor 1320, cause the apparatus 1300 at least to perform at least the example methods (e.g., methods 700, 800, 900, and 1000) and various embodiments described above.
  • the at least one processor 1220 or 1320 may include, but not limited to, at least one hardware processor, including at least one microprocessor such as a CPU, a portion of at least one hardware processor, and any other suitable dedicated processor such as those developed based on for example Field Programmable Gate Array (FPGA) and Application Specific Integrated Circuit (ASIC) . Further, the at least one processor 1220 or 1320 may also include at least one other circuitry or element not shown in Figure 12 or Figure 13.
  • at least one hardware processor including at least one microprocessor such as a CPU, a portion of at least one hardware processor, and any other suitable dedicated processor such as those developed based on for example Field Programmable Gate Array (FPGA) and Application Specific Integrated Circuit (ASIC) .
  • FPGA Field Programmable Gate Array
  • ASIC Application Specific Integrated Circuit
  • the at least one non-transitory computer-readable medium 1230 or 1330 may include at least one storage medium in various forms, such as a volatile memory and/or a non-volatile memory.
  • the volatile memory may include, but not limited to, for example, an RAM, a cache, and so on.
  • the non-volatile memory may include, but not limited to, for example, an ROM, a hard disk, a flash memory, and so on.
  • the at least medium 1230 or 1330 may include, but are not limited to, an electric, a magnetic, an optical, an electromagnetic, an infrared, or a semiconductor system, apparatus, or device or any combination of the above.
  • the example apparatus 1200 or 1300 may also include at least one other circuitry, element, and interface, for example antenna element, and the like.
  • the circuitries, parts, elements, and interfaces in the example apparatus 1200 or 1300 may be coupled together via any suitable connections including, but not limited to, buses, crossbars, wiring and/or wireless lines, in any suitable ways, for example electrically, magnetically, optically, electromagnetically, and the like.
  • controllers, flowcharts, and modules may also be implemented on a general purpose or special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit elements, an integrated circuit, a hardware electronic or logic circuit such as a discrete element circuit, a programmable logic device, or the like.
  • any device that has a finite state machine capable of implementing the flowcharts shown in the figures may be used to implement the processing functions of the present disclosure.

Landscapes

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

Abstract

Sont divulgués des procédés et un appareil de notification de position et de transmission de petites données (SDT) lorsqu'un équipement utilisateur (UE) reste dans un état inactif de commande de ressources radio (RRC). Un mode de réalisation de la présente invention concerne un procédé exécuté par un équipement utilisateur. Le procédé comprend les étapes consistant à : recevoir un message de libération de commande de ressources radio (RRC) contenant au moins une indication de suspension et un temporisateur de mise à jour d'une zone de notification d'un réseau d'accès radio (RAN) (RNAU) ; lancer le temporisateur RNAU ; puis initier une procédure de transmission de petites données (SDT) et, en réponse à une arrivée de données de liaison montante (UL) associée à une porteuse radio de données (DRB), la DRB étant configurée avec la SDT, transmettre une demande de reprise de RRC.
PCT/CN2021/085067 2021-04-01 2021-04-01 Procédé et appareil de notification de position et de transmission de petites données dans un état inactif de commande de ressources radio WO2022205360A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/085067 WO2022205360A1 (fr) 2021-04-01 2021-04-01 Procédé et appareil de notification de position et de transmission de petites données dans un état inactif de commande de ressources radio

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/085067 WO2022205360A1 (fr) 2021-04-01 2021-04-01 Procédé et appareil de notification de position et de transmission de petites données dans un état inactif de commande de ressources radio

Publications (1)

Publication Number Publication Date
WO2022205360A1 true WO2022205360A1 (fr) 2022-10-06

Family

ID=83457825

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/085067 WO2022205360A1 (fr) 2021-04-01 2021-04-01 Procédé et appareil de notification de position et de transmission de petites données dans un état inactif de commande de ressources radio

Country Status (1)

Country Link
WO (1) WO2022205360A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190289661A1 (en) * 2018-03-16 2019-09-19 Asustek Computer Inc. Method and apparatus of handling multiple radio resource control (rrc) procedures in a wireless communication system
US20200120477A1 (en) * 2018-05-07 2020-04-16 Telefonaktiebolaget Lm Ericsson (Publ) Methods for Handling Radio Access Network Notification Area (RNA) Update Configuration Upon Reject

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190289661A1 (en) * 2018-03-16 2019-09-19 Asustek Computer Inc. Method and apparatus of handling multiple radio resource control (rrc) procedures in a wireless communication system
US20200120477A1 (en) * 2018-05-07 2020-04-16 Telefonaktiebolaget Lm Ericsson (Publ) Methods for Handling Radio Access Network Notification Area (RNA) Update Configuration Upon Reject

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Summary of email discussion [Post111-e][926][SmallData] Context Fetch", 3GPP DRAFT; R2-2009967, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic meeting; 20201102 - 20201113, 22 October 2020 (2020-10-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051941488 *
HUAWEI, HISILICON: "SDT aspects common for RACH-based and CG-based SDT scheme", 3GPP DRAFT; R2-2009930, 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 , XP051942700 *

Similar Documents

Publication Publication Date Title
TWI711331B (zh) 用於物聯網之使用者設備自動釋放之方法及其裝置
US20200107396A1 (en) User equipment and base station for mobile communication system
CN107079514B (zh) 禁止针对辅小区组失败的失败指示
US11234265B2 (en) Data transmission method and device, search space optimization method and device, and storage medium
EP3552433B1 (fr) Transfert autonome d'un équipement d'utilisateur dans un spectre avec ou sans licence
US20080051091A1 (en) Apparatus, method and computer program product providing enhanced robustness of handover in E-UTRAN with paging of the active UE
CN109561500B (zh) 寻呼方法、装置及可读存储介质
CN107211381B (zh) 用于实现时间对齐保护定时器的方法和装置
EP3739934B1 (fr) Maintenance d'une partie de largeur de bande
KR20090030296A (ko) 무선 액세스 시스템에서 페이징 성능들을 개선하기 위한 방법
WO2022127731A1 (fr) Procédé de changement de cellule et équipement utilisateur
EP2810509A1 (fr) Procédé et appareil pour préserver des ressources de canal de commande de liaison montante physique
US20220078715A1 (en) Methods and apparatuses for using power-saving signal pattern, device and system
US20200367293A1 (en) Method operating on user equipment and user equipment
CN113260089B (zh) 利用多个不连续接收组对活动时间的确定
EP4277423A1 (fr) Procédé de transmission de données, et équipement utilisateur
CN116158147A (zh) 用于使用预配置上行链路资源进行传输的方法及设备
TW201931931A (zh) 處理頻寬部分的裝置及方法
WO2022205360A1 (fr) Procédé et appareil de notification de position et de transmission de petites données dans un état inactif de commande de ressources radio
EP3874809B1 (fr) Robustesse et traitement de la mobilité pour un transfert amélioré
JP2023542393A (ja) Ｒｒｃ非アクティブ状態におけるｕｅのデータ送信およびｒｎａｕ手順の方法および装置
CN116114369A (zh) 数据传输方法、装置、通信设备及存储介质
WO2017028883A1 (fr) Amélioration de temps d'attente dans des scénarios de réception discontinue
CN114450980B (zh) 用于位置区域更新的方法和装置
US11770857B2 (en) Methods and apparatuses for random access procedure

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21934018

Country of ref document: EP

Kind code of ref document: A1