WO2021189462A1 - Method, device and computer storage medium of communication - Google Patents

Method, device and computer storage medium of communication Download PDF

Info

Publication number
WO2021189462A1
WO2021189462A1 PCT/CN2020/081817 CN2020081817W WO2021189462A1 WO 2021189462 A1 WO2021189462 A1 WO 2021189462A1 CN 2020081817 W CN2020081817 W CN 2020081817W WO 2021189462 A1 WO2021189462 A1 WO 2021189462A1
Authority
WO
WIPO (PCT)
Prior art keywords
uplink data
terminal device
inactive state
network device
transmission
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2020/081817
Other languages
English (en)
French (fr)
Inventor
Gang Wang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NEC Corp
Original Assignee
NEC Corp
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 NEC Corp filed Critical NEC Corp
Priority to JP2022558192A priority Critical patent/JP7540502B2/ja
Priority to PCT/CN2020/081817 priority patent/WO2021189462A1/en
Priority to CN202080099120.5A priority patent/CN115552961B/zh
Priority to EP20926571.9A priority patent/EP4128876A4/en
Priority to US17/914,698 priority patent/US20230379815A1/en
Publication of WO2021189462A1 publication Critical patent/WO2021189462A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/20—Selecting an access point
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • Embodiments of the present disclosure generally relate to the field of telecommunication, and in particular, to methods, devices and computer storage media of communication for small data transmission (SDT) control.
  • SDT small data transmission
  • a terminal device in an inactive state may still have small and infrequent data traffic to be transmitted (also referred to as SDT hereinafter) .
  • SDT small and infrequent data traffic to be transmitted
  • 3GPP third generation partnership project
  • 3GPP Release 17 has approved SDT based on a random access channel (RACH) and pre-configured physical uplink shared channel (PUSCH) resources in the inactive state.
  • RACH random access channel
  • PUSCH physical uplink shared channel
  • embodiments of the present disclosure provide methods, devices and computer storage media of communication for SDT control.
  • a method of communication comprises: determining, at a terminal device and based on characteristics of traffic associated with uplink data, whether the uplink data is to be transmitted in an inactive state of the terminal device; and in accordance with a determination that the uplink data is to be transmitted in the inactive state, resuming radio bearers for the transmission of the uplink data in the inactive state; and transmitting, based on the radio bearers, the uplink data to the network device while the terminal device is in the inactive state.
  • a method of communication comprises: receiving, at a network device, uplink data associated with a traffic, the uplink data being transmitted by a terminal device in an inactive state based on characteristics of the traffic; and transmitting, to the terminal device, a response to the reception of the uplink data.
  • a terminal device comprising a processor and a memory coupled to the processor.
  • the memory stores instructions that when executed by the processor, cause the terminal device to perform the method according to the first aspect of the present disclosure.
  • a network device comprising a processor and a memory coupled to the processor.
  • the memory stores instructions that when executed by the processor, cause the network device to perform the method according to the second aspect of the present disclosure.
  • a computer readable medium having instructions stored thereon.
  • the instructions when executed on at least one processor, cause the at least one processor to perform the method according to the first aspect of the present disclosure.
  • a computer readable medium having instructions stored thereon.
  • the instructions when executed on at least one processor, cause the at least one processor to perform the method according to the second aspect of the present disclosure.
  • FIG. 1 illustrates an example communication network in which some embodiments of the present disclosure can be implemented
  • FIG. 2 illustrates a schematic diagram illustrating a process of communication for SDT control according to some embodiments of the present disclosure
  • FIG. 3 illustrates an example method of communication implemented at a terminal device in accordance with some embodiments of the present disclosure
  • FIG. 4 illustrates an example method of transmission of uplink data in an inactive state in accordance with some embodiments of the present disclosure
  • FIG. 5 illustrates another example method of transmitting uplink data based on a random access procedure in accordance with some embodiments of the present disclosure
  • FIG. 6 illustrates an example method of determining whether subsequent transmission is supported in accordance with some embodiments of the present disclosure
  • FIG. 7 illustrates an example method of communication implemented at a network device in accordance with some embodiments of the present disclosure
  • FIG. 8 illustrates another example method of communication implemented at a network device in accordance with some embodiments of the present disclosure
  • FIG. 9 illustrates another example method of communication implemented at a network device in accordance with some embodiments of the present disclosure.
  • FIG. 10 is a simplified block diagram of a device that is suitable for implementing embodiments of the present disclosure.
  • terminal device refers to any device having wireless or wired communication capabilities.
  • the terminal device include, but not limited to, user equipment (UE) , personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs) , portable computers, tablets, wearable devices, internet of things (IoT) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, device on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure/network, or image capture devices such as digital cameras, gaming devices, music storage and playback appliances, or Internet appliances enabling wireless or wired Internet access and browsing and the like.
  • UE user equipment
  • PDAs personal digital assistants
  • IoT internet of things
  • IoE Internet of Everything
  • MTC machine type communication
  • X means pedestrian, vehicle, or infrastructure/network
  • image capture devices such as digital cameras, gaming devices, music storage and playback appliances, or Internet appliances enabling wireless or wired Internet access and browsing and the like.
  • terminal device can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal or a wireless device.
  • network device refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate.
  • Examples of a network device include, but not limited to, a Node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNB) , a transmission reception point (TRP) , a remote radio unit (RRU) , a radio head (RH) , a remote radio head (RRH) , a low power node such as a femto node, a pico node, and the like.
  • NodeB Node B
  • eNodeB or eNB evolved NodeB
  • gNB next generation NodeB
  • TRP transmission reception point
  • RRU remote radio unit
  • RH radio head
  • RRH remote radio head
  • a low power node such as a femto node, a pico node, and the like.
  • the terminal device may be connected with a first network device and a second network device.
  • One of the first network device and the second network device may be a master node and the other one may be a secondary node.
  • the first network device and the second network device may use different RATs.
  • the first network device may be a first RAT device and the second network device may be a second RAT device.
  • the first RAT device is eNB and the second RAT device is gNB.
  • Information related with different RATs may be transmitted to the terminal device from at least one of the first network device and the second network device.
  • first information may be transmitted to the terminal device from the first network device and second information may be transmitted to the terminal device from the second network device directly or via the first network device.
  • information related with configuration for the terminal device configured by the second network device may be transmitted from the second network device via the first network device.
  • Information related with reconfiguration for the terminal device configured by the second network device may be transmitted to the terminal device from the second network device directly or via the first network device.
  • the singular forms ‘a’ , ‘an’ and ‘the’ are intended to include the plural forms as well, unless the context clearly indicates otherwise.
  • the term ‘includes’ and its variants are to be read as open terms that mean ‘includes, but is not limited to. ’
  • the term ‘based on’ is to be read as ‘at least in part based on. ’
  • the term ‘one embodiment’ and ‘an embodiment’ are to be read as ‘at least one embodiment. ’
  • the term ‘another embodiment’ is to be read as ‘at least one other embodiment. ’
  • the terms ‘first, ’ ‘second, ’ and the like may refer to different or same objects. Other definitions, explicit and implicit, may be included below.
  • values, procedures, or apparatus are referred to as ‘best, ’ ‘lowest, ’ ‘highest, ’ ‘minimum, ’ ‘maximum, ’ or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.
  • FIG. 1 illustrates a schematic diagram of an example communication network 100 in which embodiments of the present disclosure can be implemented.
  • the communication network 100 may include a network device 110 and a terminal device 120 served by the network device 110.
  • the network device 110 and the terminal device 120 may communicate with each other via a channel such as a wireless communication channel.
  • the terminal device 120 may transmit data packets (i.e., uplink data) to the network device 110, and the network device 110 may transmit a response to reception of the uplink data to the terminal device 120.
  • data packets i.e., uplink data
  • the communication network 100 may include any suitable number of network devices and/or terminal devices adapted for implementing implementations of the present disclosure. Further, the communication network 100 may include any other devices than the network devices and the terminal devices, such as a core network element, but they are omitted here so as to avoid obscuring the present invention.
  • the communications in the communication network 100 may conform to any suitable standards including, but not limited to, Global System for Mobile Communications (GSM) , Long Term Evolution (LTE) , LTE-Evolution, LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , Code Division Multiple Access (CDMA) , GSM EDGE Radio Access Network (GERAN) , Machine Type Communication (MTC) and the like.
  • GSM Global System for Mobile Communications
  • LTE Long Term Evolution
  • LTE-Evolution LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • CDMA Code Division Multiple Access
  • GERAN GSM EDGE Radio Access Network
  • MTC Machine Type Communication
  • the communications may be performed according to any generation communication protocols either currently known or to be developed in the future.
  • Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols.
  • the terminal device 120 in an inactive state may still have small and infrequent data traffic to be transmitted (also referred to as SDT hereinafter) .
  • the small and infrequent data traffic may include smartphone applications such as traffic from instant messaging (IM) services (whatsapp, QQ, wechat etc. ) , heart-beat/keep-alive traffic from IM/email clients and other applications, and push notifications from various applications.
  • the small and infrequent data traffic may include non-smartphone applications such as traffic from wearables (periodic positioning information etc. ) , sensors (Industrial Wireless Sensor Networks transmitting temperature, pressure readings periodically or in an event triggered manner etc. ) , and smart meters and smart meter networks sending periodic meter readings.
  • Embodiments of the present disclosure provide a solution of communication for SDT control.
  • the solution can achieve the control of SDT in the inactive state of the terminal device.
  • FIG. 2 illustrates a schematic diagram illustrating a process 200 of communication for SDT control according to some embodiments of the present disclosure. For the purpose of discussion, the process 200 will be described with reference to FIG. 1. The process 200 may involve the terminal device 120 and the network device 110 as illustrated in FIG. 1.
  • the terminal device 120 may determine 201 whether the uplink data is to be transmitted in the inactive state. That is, the terminal device 120 may decide to whether perform SDT for transmission of the uplink tata.
  • the triggering of SDT is based on different traffic or services that trigger the transmission of the uplink data.
  • the terminal device 120 may initiate SDT when at least the following conditions are fulfilled: 1) the terminal device 120 is in radio resource control (RRC) inactive state, and the transmission is for mobile originating calls (i.e., uplink traffic) ; 2) the terminal device 120 supports SDT, and the system information of the network device 110 also indicates supporting SDT; 3) a fallback indication is not received from a media access control (MAC) layer of the terminal device 120; and 4) the traffic triggering the transmission supports SDT.
  • RRC radio resource control
  • MAC media access control
  • the terminal device 120 may determine at least one of an access category and an access identity of the traffic; and in accordance with a determination that the at least one of an access category and an access identity supports the transmission of the uplink data in the inactive state, determining that the uplink data is to be transmitted in the inactive state.
  • the access category or the access identity that supports SDT may be predefined.
  • the access category or the access identity that supports SDT may be broadcasted by system information from the network device 110.
  • the access category or the access identity that supports SDT may be configured to the terminal device 120 dedicatedly by a RRC message, for example, a RRCRelease message or any other suitable messages.
  • a certain access category or access identity for SDT may be introduced.
  • the value of the certain access category or access identity may be 10 or any other suitable numbers.
  • a set of access categories or access identities may be considered to support SDT.
  • potential access categories or access identities that can be considered to support SDT may be 11-15 or any other suitable numbers.
  • the terminal device 120 may determine a quality of service (QoS) parameter (i.e., 5QI) of a QoS flow of the traffic; and in accordance with a determination that the QoS parameter supports the transmission of the uplink data in the inactive state, determining that the uplink data is to be transmitted in the inactive state.
  • QoS quality of service
  • the 5QI value that supports SDT may be predefined.
  • the 5QI value that supports SDT may be broadcasted by system information from the network device 110.
  • the 5QI value that supports SDT may be configured to the terminal device 120 dedicatedly by a RRC message, for example, a RRCRelease message or any other suitable messages.
  • a certain 5QI value for SDT may be introduced.
  • potential 5QI value that can be considered to support SDT may be 66 or any other suitable numbers.
  • the terminal device 120 may determine one or more data radio bearers (DRBs) for the traffic; and in accordance with a determination that the one or more DRBs support the transmission of the uplink data in the inactive state, determining that the uplink data is to be transmitted in the inactive state.
  • DRBs data radio bearers
  • the support of SDT by one DRB may be found in a stored UE context, as SDT is initiated for UE in an inactive state, and the configuration used for SDT is based on the stored UE context.
  • the support of SDT of one DRB may be configured during a RRC connected state, i.e. by RRCReconfiguration message or any other suitable messages.
  • the support of one DRB may be configured upon the terminal device 120 is caused to be in the inactive sate, for example, by a RRCRelease message or any other suitable messages with a suspend indication.
  • the terminal device 120 may receive, at a RRC layer of the terminal device 120 and from a non-access stratum (NAS) layer of the terminal device 120, a first indication about whether the uplink data is to be transmitted in the inactive state; and determine, based on the first indication from the NAS layer, whether the uplink data is to be transmitted in the inactive state.
  • NAS non-access stratum
  • the terminal device 120 may further determine a size of buffered content associated with the traffic; and in accordance with a determination that the size of the buffered content is less than a threshold size, determining that the uplink data is to be transmitted in the inactive state.
  • the buffered content may refer to total uplink data and signaling available for transmission plus MAC header and where required, MAC control elements (CE) .
  • the threshold size may be broadcasted by system information from the network device 110. In some alternative embodiments, the threshold size may be a predetermined value. In some alternative embodiments, the threshold size that support SDT may be configured to the terminal device 120 dedicatedly by a RRC message, for example, a RRCRelease message.
  • the size of the buffered content can be used in combined with one or more of access categories, access identities, 5QIs and DRBs.
  • different access categories, access identities, 5QIs or DRBs may be associated with different values of the threshold size. So far, when the conditions for initiating the SDT are satisfied, the RRC layer of the terminal device 120 can initiate SDT procedure, instead of normal data transmission (also referred to as NDT hereinafter) .
  • the terminal device 120 may resume 202 radio bearers for the transmission of the uplink data in the inactive state.
  • the RRC layer of the terminal device 120 may resume one or more DRBs that are needed to support the transmission of the uplink data in the inactive state.
  • the RRC layer of the terminal device 120 may resume a signaling radio bearer 1 (SRB1) and a signaling radio bearer 2 (SRB2) . Thereafter, the terminal device 120 may transmit the uplink data in the inactive state based on the resumed configuration.
  • the terminal device 120 may determine 203 whether configured grant information is stored for the transmission of the uplink data in the inactive state. In accordance with a determination that the configured grant information is stored, the terminal device 120 may determine 204 whether a time advance (TA) associated with the transmission of the uplink data is valid. In accordance with a determination that the TA is valid, the terminal device 120 may transmit 205, with the configured grant information, the uplink data in the inactive state.
  • TA time advance
  • the terminal device 120 may decide to transmit, based on a random access procedure, the uplink data in the inactive state.
  • the RRC layer of the terminal device 120 may configured the lower layer (i.e., MAC layer) to perform random access based SDT.
  • the terminal device 120 may determine 206, at the RRC layer, whether subsequent transmission (i.e., subsequent SDT) is supported. In other words, the terminal device may determine whether only one shot SDT or the subsequent SDT is supported. In some embodiments, the RRC layer of the terminal device 120 may determine whether subsequent transmission is supported, and then inform the lower layer (i.e., MAC layer) whether the subsequent transmission is supported. In some embodiments, the RRC layer may inform the MAC layer of the threshold size used in initiation of SDT for later comparison with a size of buffered content associated with the uplink data.
  • the RRC layer of the terminal device 120 may determine whether the subsequent transmission of the uplink data is supported by both the terminal device 120 and the network device 110.
  • two types of subsequent SDT can be supported: configured grant based subsequent SDT and dynamic grant based subsequent SDT.
  • the configured grant based subsequent SDT refers to transmission of uplink small data on pre-configured PUSCH resources (i.e., reusing the configured grant type 1 when a time advance (TA) associated with the transmission is valid) .
  • TA time advance
  • the dynamic grant based subsequent SDT refers to transmission of uplink small data on dynamically scheduled PUSCH resources.
  • information about at least one of whether the subsequent transmission can be supported by the network device 110 and which types of the subsequent transmission can be supported by the network device 110 may be broadcasted by system information from the network device 110.
  • information about whether subsequent transmission can be supported by the terminal device 120 and which types of the subsequent transmission can be supported by the terminal device 120 may be configured to the terminal device 120 by a RRC message from the network device 110, for example, RRCRelease message or any other suitable messages.
  • whether the subsequent transmission can be supported and which types of the subsequent transmission can be supported may be associated with the access category, the access identity, 5QI or DRB.
  • the terminal device 120 may further determine whether the traffic supports the subsequent transmission of the uplink data.
  • the support by the traffic for the subsequent transmission may be broadcasted by system information from the network device 110. It should be noted that any other suitable forms are also feasible.
  • the terminal device 120 may further determine an uplink resource configuration type for the subsequent transmission supported by the traffic. For example, the terminal device 120 may determine whether the traffic supports dynamic grant or configured grant. In accordance with a determination that the terminal device does not support the uplink resource configuration type, the terminal device 120 may determine that the subsequent transmission is not supported, and in accordance with a determination that the terminal device supports the uplink resource configuration type, the terminal device 120 may determine that the subsequent transmission is supported.
  • the terminal device 120 may determine that the subsequent transmission is not supported.
  • the terminal device 120 may determine 207, at the MAC layer, whether a size of buffered content associated with the traffic is larger than a threshold size.
  • the buffered content may refer to total uplink data and signaling available for transmission plus MAC header and where required, MAC CE.
  • the threshold size may be informed by the RRC layer to the MAC layer, and may be similar with that described in 210 with reference to FIG. 2.
  • the terminal device 120 may determine 208 whether there is a dedicated resource having a size larger than or equal to the threshold size. In accordance with a determination that there is the dedicated resource having a size larger than or equal to the threshold size, the terminal device 120 may transmit 209, with the dedicated resource, the uplink data in the inactive state.
  • the terminal device 120 may cancel the transmission of the uplink data in the inactive state.
  • the MAC layer of the terminal device 120 may inform the upper layer (i.e., RRC layer) that SDT is cancelled. In this way, NDT will be performed for transmission of the uplink data.
  • the terminal device 120 may determine an uplink resource configuration for the transmission of the uplink data, and transmitting the uplink data on the uplink resource configuration.
  • the determination and transmission can be carried out in any suitable ways.
  • the terminal device 120 may generate a RRC message indicating that the uplink data is transmitted in the inactive state, and transmit the RRC message and the uplink data to the network device 110 in the random access procedure.
  • the terminal device 120 may set, at the RRC layer, a resume cause IE in RRCConnectionResumeRequest message as a new one which indicates SDT, and submit the RRCConnectionResumeRequest message to the lower layer (i.e., MAC layer) for the transmission.
  • the lower layer i.e., MAC layer
  • the terminal device 120 may provide, from RRC layer to the lower layer (i.e., MAC layer) of the terminal device 120, a MAC CE carrying an identity (for example, an inactive radio network temporary identifier (I-RNTI) ) of the terminal device 120, and transmit, to the network device 110, the MAC CE and the uplink data in the random access procedure.
  • RRC layer i.e., MAC layer
  • MAC CE carrying an identity (for example, an inactive radio network temporary identifier (I-RNTI) ) of the terminal device 120, and transmit, to the network device 110, the MAC CE and the uplink data in the random access procedure.
  • I-RNTI inactive radio network temporary identifier
  • the network device 110 may transmit 210 a response to the reception of the uplink data.
  • the network device 110 may reply the terminal device 120 with a first RRC message that informs the terminal device 120 to suspend the radio bearers for the transmission of the uplink data in the inactive state.
  • the first RRC message may be a RRCRelease message.
  • the first RRC message may be a RRCReject message. It should be noted that any other suitable messages are also feasible.
  • the first RRC message may comprise suspend configuration.
  • the second network device is a network device serving the terminal device 120 immediately before the terminal device 120 changes from a connected state to the inactive state, i.e., a last serving network device.
  • the terminal device 120 may suspend 211 the radio bearers for the transmission of the uplink data in the inactive state. For example, the terminal device 120 may suspend one or more DRBs for transmission of the uplink data in the inactive state. In addition, the terminal device 120 may further suspend SRB1 and SRB2. In this way, the terminal device 120 returns to a normal inactive state without data transmission.
  • the network device 110 may reply the terminal device 120 with a second RRC message that comprises an uplink resource configuration for the subsequent transmission.
  • the uplink resource configuration may be associated with dynamic grant for the subsequent transmission.
  • the uplink resource configuration may be associated with configured grant for the subsequent transmission.
  • the second RRC message may be a RRCRelease message.
  • the second RRC message may be a RRCReject message. It should be noted that any other suitable messages are also feasible.
  • the second RRC message may comprise suspend configuration.
  • the second network device is a network device serving the terminal device 120 immediately before the terminal device 120 changes from a connected state to the inactive state, i.e., a last serving network device.
  • the terminal device 120 may perform 212, with the uplink resource, the subsequent transmission of the uplink data in the inactive state. For example, the terminal device 120 may maintain at the inactive state, maintain one or more current active SRBs and DRBs, maintain a packet data convergence protocol (PDCP) status variable, and maintain a security key. In this way, the terminal device 120 may start the subsequent transmission.
  • PDCP packet data convergence protocol
  • the terminal device 120 in the inactive state, if reselecting from a first cell served by the network device 110 to a second cell served by a third network device (not shown) while a timer T319 is running (i.e., a RRCResumeRequest message is sent but no response is received) , the terminal device 120 would enter an idle state.
  • the network device 110 is not aware of that the terminal device 120 has moved to other cells, and may continue allocating resource for the terminal device 120, especially in case of configured grant based subsequent SDT, which result in radio resource waste.
  • embodiments of the present disclosure provide network control of SDT upon state transition.
  • the terminal device 120 may enter an idle state, and retransmit the uplink data to the third network device.
  • the terminal device 120 may enter an idle state, and releasing an uplink resource configuration for the transmission of the uplink data in the inactive state.
  • the terminal device 120 may stop the subsequent transmission, but remain at the inactive state.
  • the terminal device 120 may suspend the radio bearers for the transmission of the uplink data in the inactive state.
  • the terminal device 120 may suspend all SRBs and DRBs for SDT except SRB0, and indicate from the RRC layer to the lower layer (i.e., MAC layer) of PDCP suspend.
  • the terminal device 120 may further release an uplink resource configuration for the transmission of the uplink data in the inactive state.
  • the terminal device 120 may further reevaluate the validity of SDT and reinitiate SDT if needed.
  • the terminal device 120 may generate a second indication about the reselection, and transmit the second indication to the network device 110. For example, the terminal device 120 may send a bye message to inform the network device 110 of the cell reselection, so that the network device 110 can stop providing uplink grant for the terminal device 120 for subsequent SDT.
  • the terminal device 120 may transmit the second indication via a RRC message.
  • the RRC message may be a UEAssistanceInfomation message or any other suitable messages.
  • the terminal device 120 may transmit the second indication via a MAC CE.
  • the MAC CE may have a fixed size of zero bits. It should be noted that any other suitable forms of the MAC CE are also feasible.
  • the terminal device 120 may transmit the second indication via a physical (PHY) layer indication.
  • PHY physical
  • the terminal device 120 may use a dedicated scheduling request (SR) configuration to indicate the cell reselection during the subsequent SDT or configured grant based SDT.
  • SR dedicated scheduling request
  • the terminal device 120 will changes from the inactive state to an idle state.
  • the terminal device 120 in the inactive state receives core network (CN) paging
  • the terminal device 120 will changes from the inactive state to an idle state.
  • the terminal device 120 in case of inability to comply with RRCResume, the terminal device 120 will changes from the inactive state to an idle state.
  • the timer T319 expiry or integrity check failure from lower layers while the timer T319 is running, the terminal device 120 will changes from the inactive state to an idle state.
  • the terminal device 120 in case of cell re-selection while the timer T319 or T302 is running, the terminal device 120 will changes from the inactive state to an idle state. In some embodiments, when the terminal device 120 failed to trigger RNA due to AC barring, the terminal device 120 will changes from the inactive state to an idle state.
  • the terminal device 120 may generate a third indication about the change, transmitting the third indication to the network device 110, and release an uplink resource configuration for the transmission of the uplink data in the inactive state.
  • the terminal device 120 may send a bye message to inform the network device 110 of the change, so that the network device 110 can stop providing uplink grant for the terminal device 120 for subsequent SDT.
  • the third indication can be carried out in a similar way as the second indication, and its details are not repeated here.
  • embodiments of the present disclosure also provide methods of communication implemented at a terminal device and a network device respectively. It will be described in more details with reference to FIGs. 3-9.
  • FIG. 3 illustrates an example method 300 of communication implemented at a terminal device in accordance with some embodiments of the present disclosure.
  • the method 300 may be performed at the terminal device 120 as shown in FIG. 1.
  • the method 300 will be described with reference to FIG. 1. It is to be understood that the method 300 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
  • the terminal device 120 determines, based on characteristics of traffic associated with uplink data, whether the uplink data is to be transmitted in an inactive state of the terminal device 120. That is, the validity of SDT is evaluated.
  • the terminal device 120 may determine at least one of an access category and an access identity of the traffic, and in accordance with a determination that the at least one of an access category and an access identity supports the transmission of the uplink data in the inactive state, determine that the uplink data is to be transmitted in the inactive state.
  • the terminal device 120 may determine a QoS parameter of a QoS flow of the traffic, and in accordance with a determination that the QoS parameter supports the transmission of the uplink data in the inactive state, determine that the uplink data is to be transmitted in the inactive state.
  • the terminal device 120 may determine one or more DRBs for the traffic, and in accordance with a determination that the one or more DRBs support the transmission of the uplink data in the inactive state, determine that the uplink data is to be transmitted in the inactive state.
  • the terminal device 120 may receive, at a RRC layer of the terminal device 120 and from a NAS layer of the terminal device 120, a first indication about whether the uplink data is to be transmitted in the inactive state, and determine, based on the first indication, whether the uplink data is to be transmitted in the inactive state.
  • the terminal device 120 may further determine a size of buffered content associated with the traffic, and in accordance with a determination that the size of the buffered content is less than a threshold size, determine that the uplink data is to be transmitted in the inactive state. Other details about the determination on whether the uplink data is to be transmitted in the inactive state are similar with that described in 201 with reference to FIG. 2, and thus are not repeated here.
  • the terminal device 120 resumes radio bearers for the transmission of the uplink data in the inactive state.
  • the terminal device 120 may resume one or more DRBs that are needed to support the transmission of the uplink data in the inactive state.
  • the operations at block 320 are similar with that described in 202 with reference to FIG. 2 and other details are omitted here.
  • FIG. 4 illustrates an example method 400 of transmission of uplink data in an inactive state in accordance with some embodiments of the present disclosure.
  • the method 400 may be performed at the terminal device 120 as shown in FIG. 1.
  • the method 400 will be described with reference to FIG. 1. It is to be understood that the method 400 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
  • the terminal device 120 may determine whether configured grant information is stored for the transmission of the uplink data in the inactive state. If determining that the configured grant information is stored, at block 420, the terminal device 120 may determine whether a TA associated with the transmission of the uplink data is valid. If determining that the TA is valid, at block 430, the terminal device 120 may transmit, with the configured grant information, the uplink data in the inactive state.
  • the terminal device 1210 may transmit, based on a random access procedure, the uplink data in the inactive state.
  • FIG. 5 illustrates an example method 500 of transmitting uplink data based on a random access procedure in accordance with some embodiments of the present disclosure.
  • the method 500 may be performed at the terminal device 120 as shown in FIG. 1.
  • the method 500 will be described with reference to FIG. 1. It is to be understood that the method 500 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
  • This embodiment considers whether subsequent SDT (also referred to as subsequent transmission herein) is supported and provides corresponding network control scheme.
  • the terminal device 120 may determine, at a RRC layer, whether subsequent transmission of the uplink data is supported. Its details will be described below with reference to FIG. 6.
  • FIG. 6 illustrates an example method 600 of determining whether subsequent transmission is supported in accordance with some embodiments of the present disclosure.
  • the method 600 may be performed at the terminal device 120 as shown in FIG. 1.
  • the method 600 will be described with reference to FIG. 1. It is to be understood that the method 600 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
  • the terminal device 120 may determine whether subsequent transmission of the uplink data is supported by both the terminal device 120 and the network device 110. If determining at block 610 that the subsequent transmission is not supported by both the terminal device 120 and the network device 110, the process may enter block 650. At block 650, the terminal device 120 may determine that the subsequent transmission is not supported.
  • the terminal device 120 may determine whether the traffic supports the subsequent transmission. If determining at block 620 that the traffic does not support the subsequent transmission, the process may also enter block 650. At block 650, the terminal device 120 may determine that the subsequent transmission is not supported.
  • the terminal device 120 may determine, at block 630, whether the terminal device 120 supports an uplink resource configuration type for the subsequent transmission supported by the traffic. If determining at block 630 that the terminal device 120 does not support the uplink resource configuration type, the process may also enter block 650. At block 650, the terminal device 120 may determine that the subsequent transmission is not supported.
  • the terminal device 120 may determine, at block 640, that the subsequent transmission is supported. Other details for determining whether the subsequent transmission is supported are similar with that described in 206 with reference to FIG. 2, and thus are not repeated here.
  • the terminal device 120 may determine whether a size of buffered content associated with the traffic is larger than a threshold size.
  • the buffered content may refer to total uplink data and signaling available for transmission plus MAC header and where required, MAC CE.
  • the buffered content may refer to total uplink data and signaling available for transmission plus MAC header and where required, MAC CE.
  • the details about the threshold size are similar with that described in 201 with reference to FIG. 2, and are not repeated here.
  • the terminal device 120 may determine whether there is a dedicated resource having a size larger than or equal to the threshold size. If determining at block 530 that there is the dedicated resource, at block 540, the terminal device 120 may transmit the uplink data in the inactive state.
  • the process enters block 550.
  • the terminal device 120 may cancel the transmission of the uplink data in the inactive state.
  • the terminal device 120 may determine an uplink resource configuration for the transmission of the uplink data, and at block 570, the terminal device 120 may transmit the uplink data based on the uplink resource configuration.
  • the operations at block 560 and 570 may be carried out by the method 400 described above. It should be noted that, any other suitable methods are also feasible.
  • the terminal device 120 may receive from the network device 110, a first RRC message that informs the terminal device 120 to suspend the radio bearers for the transmission of the uplink data in the inactive state, and suspend the radio bearers in response to receiving the first RRC message.
  • the RRC message may comprise suspend configuration.
  • the second network device is a network device serving the terminal device 120 immediately before the terminal device 120 changes from a connected state to the inactive state, i.e., a last serving network device for the terminal device 120.
  • the terminal device 120 may receive, from the network device, a second RRC message comprising an uplink resource configuration for subsequent transmission of the uplink data, and perform, with the uplink resource configuration, the subsequent transmission in the inactive state.
  • the terminal device 120 may enter an idle state. In addition, the terminal device 120 may retransmit the uplink data to the third network device.
  • the terminal device 120 may enter an idle state, and release an uplink resource configuration for the transmission of the uplink data in the inactive state.
  • the terminal device 120 may stop the subsequent transmission, suspend the radio bearers for the transmission of the uplink data and release an uplink resource configuration for the transmission of the uplink data in the inactive state.
  • the terminal device 120 may redetermine whether the uplink data is to be transmitted in the inactive state, and in accordance with a redetermination that the uplink data is to be transmitted in the inactive state, reinitiate the transmission of the uplink data. For example, the terminal device 120 may repeat the processes described in FIG. 3 to reevaluate the validity of SDT and reinitiate the SDT if needed.
  • the terminal device 120 may generate a second indication about the reselection, and transmit the second indication to the network device 110.
  • the terminal device 120 may generate a third indication about the change, transmit the third indication to the network device 110, and release an uplink resource configuration for the transmission of the uplink data in the inactive state.
  • FIG. 7 illustrates an example method 700 of communication implemented at a network device in accordance with some embodiments of the present disclosure.
  • the method 700 may be performed at the network device 110 as shown in FIG. 1.
  • the method 700 will be described with reference to FIG. 1. It is to be understood that the method 700 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
  • the network device 110 receives uplink data associated with a traffic.
  • the uplink data is transmitted by the terminal device 120 in an inactive state based on characteristics of the traffic.
  • the network device 110 may receive the uplink data based on the configured grant information.
  • the network device 110 may receive, from the terminal device 120, the uplink data and a RRC message in a random access procedure.
  • the RRC message may indicate that the uplink data is transmitted in the inactive state.
  • the network device 110 may transmit, to the terminal device 120, a response to the reception of the uplink data.
  • the network device 110 may transmit, in the response, a first RRC message that informs the terminal device 120 to suspend radio bearers for the transmission of the uplink data in the inactive state.
  • the first RRC message may comprise suspend configuration.
  • the second network device is a network device serving the terminal device immediately before the terminal device 120 changes from a connected state to the inactive state, i.e., a last serving network device.
  • the network device 110 may transmit, in the response, a second RRC message comprising an uplink resource configuration for subsequent transmission of the uplink data.
  • the uplink resource configuration may be associated with dynamic grant subsequent SDT.
  • the uplink resource configuration may be associated with configured grant subsequent SDT.
  • the second RRC message may comprise suspend configuration.
  • the second network device is a network device serving the terminal device immediately before the terminal device 120 changes from a connected state to the inactive state, i.e., a last serving network device.
  • the network device 110 may transmit information about whether the network device 110 supported subsequent transmission of the uplink data. For example, the network device 110 may broadcast the information via system information. Alternatively, the network device 110 may configure the information to the terminal device 120 via a RRC message.
  • FIG. 8 illustrates another example method 800 of communication implemented at a network device in accordance with some embodiments of the present disclosure.
  • the method 800 may be performed at the network device 110 as shown in FIG. 1.
  • the method 800 will be described with reference to FIG. 1. It is to be understood that the method 800 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
  • This embodiment describes the behavior upon cell reselection.
  • the network device 110 may receive, from the terminal device 120, a second indication about a reselection of the terminal device 120 from a first cell served by the network device 110 to a second cell served by a third network device (not shown) during subsequent transmission of the uplink data or during transmission of the uplink data based on configured grant information.
  • the network device 110 may receive the second indication via a RRC message.
  • the network device 110 may receive the second indication via a MAC CE.
  • the network device 110 may receive the second indication via a PHY layer indication. Other details are similar with that described in connection with the transmission of the second indication, and are not repeated here.
  • the network device 110 may stop scheduling an uplink resource to the terminal device 120 for the subsequent transmission of the uplink data. In this way, resource waste can be avoided.
  • FIG. 9 illustrates another example method 900 of communication implemented at a network device in accordance with some embodiments of the present disclosure.
  • the method 900 may be performed at the network device 110 as shown in FIG. 1.
  • the method 900 will be described with reference to FIG. 1. It is to be understood that the method 900 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
  • This embodiment describes the behavior upon transition from an inactive state to an idle state.
  • the network device 110 may receive, from the terminal device 120, a third indication about a change of the terminal device 120 from the inactive state to an idle state.
  • the network device 110 may receive the third indication via a RRC message.
  • the network device 110 may receive the third indication via a MAC CE.
  • the network device 110 may receive the third indication via a PHY layer indication. Other details are similar with that described in connection with the transmission of the third indication, and are not repeated here.
  • the network device 110 may stop scheduling an uplink resource to the terminal device 120 for the subsequent transmission of the uplink data. In this way, resource waste can be avoided.
  • FIG. 10 is a simplified block diagram of a device 1000 that is suitable for implementing embodiments of the present disclosure.
  • the device 1000 can be considered as a further example implementation of the network device 110 or the terminal device 120 as shown in FIG. 1. Accordingly, the device 1000 can be implemented at or as at least a part of the network device 110 or the terminal device 120.
  • the device 1000 includes a processor 1010, a memory 1020 coupled to the processor 1010, a suitable transmitter (TX) and receiver (RX) 1040 coupled to the processor 1010, and a communication interface coupled to the TX/RX 1040.
  • the memory 1010 stores at least a part of a program 1030.
  • the TX/RX 1040 is for bidirectional communications.
  • the TX/RX 1040 has at least one antenna to facilitate communication, though in practice an Access Node mentioned in this application may have several ones.
  • the communication interface may represent any interface that is necessary for communication with other network elements, such as X2/Xn interface for bidirectional communications between eNBs/gNBs, S1/NG interface for communication between a Mobility Management Entity (MME) /Access and Mobility Management Function (AMF) /SGW/UPF and the eNB/gNB, Un interface for communication between the eNB/gNB and a relay node (RN) , or Uu interface for communication between the eNB/gNB and a terminal device.
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • RN relay node
  • Uu interface for communication between the eNB/gNB and a terminal device.
  • the program 1030 is assumed to include program instructions that, when executed by the associated processor 1010, enable the device 1000 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to FIGs. 1 to 9.
  • the embodiments herein may be implemented by computer software executable by the processor 1010 of the device 1000, or by hardware, or by a combination of software and hardware.
  • the processor 1010 may be configured to implement various embodiments of the present disclosure.
  • a combination of the processor 1010 and memory 1020 may form processing means 1050 adapted to implement various embodiments of the present disclosure.
  • the memory 1020 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory 1020 is shown in the device 1000, there may be several physically distinct memory modules in the device 1000.
  • the processor 1010 may be of any type suitable to the local technical network, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • the device 1000 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
  • various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representation, it will be appreciated that the blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • the present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium.
  • the computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the process or method as described above with reference to FIGs. 2 to 9.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or split between program modules as desired in various embodiments.
  • Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
  • Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented.
  • the program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
  • the above program code may be embodied on a machine readable medium, which may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • the machine readable medium may be a machine readable signal medium or a machine readable storage medium.
  • a machine readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
  • machine readable storage medium More specific examples of the machine readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • RAM random access memory
  • ROM read-only memory
  • EPROM or Flash memory erasable programmable read-only memory
  • CD-ROM portable compact disc read-only memory
  • magnetic storage device or any suitable combination of the foregoing.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/CN2020/081817 2020-03-27 2020-03-27 Method, device and computer storage medium of communication Ceased WO2021189462A1 (en)

Priority Applications (5)

Application Number Priority Date Filing Date Title
JP2022558192A JP7540502B2 (ja) 2020-03-27 2020-03-27 端末装置及び基地局
PCT/CN2020/081817 WO2021189462A1 (en) 2020-03-27 2020-03-27 Method, device and computer storage medium of communication
CN202080099120.5A CN115552961B (zh) 2020-03-27 2020-03-27 用于通信的方法、设备和计算机存储介质
EP20926571.9A EP4128876A4 (en) 2020-03-27 2020-03-27 METHOD, DEVICE AND COMPUTER STORAGE MEDIUM FOR COMMUNICATION
US17/914,698 US20230379815A1 (en) 2020-03-27 2020-03-27 Method, device and computer storage medium of communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/081817 WO2021189462A1 (en) 2020-03-27 2020-03-27 Method, device and computer storage medium of communication

Publications (1)

Publication Number Publication Date
WO2021189462A1 true WO2021189462A1 (en) 2021-09-30

Family

ID=77891519

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/081817 Ceased WO2021189462A1 (en) 2020-03-27 2020-03-27 Method, device and computer storage medium of communication

Country Status (5)

Country Link
US (1) US20230379815A1 (https=)
EP (1) EP4128876A4 (https=)
JP (1) JP7540502B2 (https=)
CN (1) CN115552961B (https=)
WO (1) WO2021189462A1 (https=)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021232305A1 (en) 2020-05-20 2021-11-25 Nec Corporation Method, device and computer readable medium for communications
WO2023134409A1 (zh) * 2022-01-14 2023-07-20 荣耀终端有限公司 数据传输方法、装置及系统
WO2023133333A3 (en) * 2022-01-10 2023-08-10 Google Llc Managing measurement in small data transmission

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
BR112022020496A2 (pt) * 2020-04-08 2023-01-10 Nokia Technologies Oy Relatório de feixe acionado por transmissão de dados
CN116250353B (zh) * 2020-07-21 2025-02-07 高通股份有限公司 通过随机接入或专用上行链路资源的上行链路数据传送
WO2022028461A1 (en) * 2020-08-05 2022-02-10 Essen Innovation Company Limited Wireless communication method for data transmission in inactive state and related devices
EP4229921A1 (en) * 2020-10-16 2023-08-23 Nokia Technologies Oy Small data transmission control
US12133201B2 (en) * 2020-12-21 2024-10-29 Samsung Electronics Co., Ltd. Method and apparatus for handling configured grant resources for small data transmission in wireless communication system

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120281566A1 (en) 2011-04-01 2012-11-08 Interdigital Patent Holdings, Inc. Method and apparatus for controlling connectivity to a network
US20180049244A1 (en) * 2016-08-12 2018-02-15 Electronics And Telecommunications Research Institute State transition method based on random access procedure in communication system
WO2018084762A1 (en) * 2016-11-04 2018-05-11 Telefonaktiebolaget Lm Ericsson (Publ) Methods, computer program, carrier, computer program product and apparatus for managing small data transmissions from user equipments
US20180227961A1 (en) 2017-02-03 2018-08-09 Motorola Mobility Llc Configuration information for an inactive state
EP3361820A1 (en) * 2017-02-10 2018-08-15 Samsung Electronics Co., Ltd. Method and apparatus for inactive mode operation in wireless communication system
WO2018174427A1 (en) * 2017-03-24 2018-09-27 Samsung Electronics Co., Ltd. Method and device for controlling data transmission state
CN108924964A (zh) * 2017-04-07 2018-11-30 中兴通讯股份有限公司 保证通信连续性的方法和用户设备
US20190037447A1 (en) 2017-07-27 2019-01-31 Lg Electronics Inc. Method and apparatus for performing edt
WO2021136474A1 (en) 2019-12-31 2021-07-08 FG Innovation Company Limited Method of small data transmission and related device
WO2021179317A1 (en) 2020-03-13 2021-09-16 Lenovo (Beijing) Limited Method and apparatus for small data transmission

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10164693B2 (en) * 2013-05-09 2018-12-25 Intel IP Corporation Reduction of buffer overflow
US20170099660A1 (en) * 2015-10-01 2017-04-06 Electronics And Telecommunications Research Institute Method and apparatus for transmitting uplink data
CN106792608B (zh) * 2016-09-29 2018-11-16 展讯通信（上海）有限公司 小数据包传输方法、装置及终端
KR102685320B1 (ko) * 2017-02-10 2024-07-17 삼성전자 주식회사 이동 통신 시스템에서 다중연결을 사용한 핸드오버 시 보안키를 처리하는 방법 및 장치
CN109309968B (zh) * 2017-07-28 2022-03-08 华硕电脑股份有限公司 无线通信系统中恢复无线电资源控制连接的方法和设备
EP4156783B1 (en) * 2018-04-05 2024-08-28 Samsung Electronics Co., Ltd. Method and apparatus for operating protocol layer of terminal in inactive mode in next-generation mobile communication system
JP6741882B1 (ja) * 2018-04-16 2020-08-19 テレフオンアクチーボラゲット エルエム エリクソン（パブル） 非アクティブ状態からのｒｒｃ再開のためのセキュリティ処理
EP4018765A4 (en) * 2019-08-20 2023-05-03 Qualcomm Incorporated DATA GENERATED BY A MOBILE DEVICE VIA A DEDICATED PRE-CONFIGURED UPLINK RESOURCE IN A SLEEP MODE OR IN A SLEEP MODE
WO2021141329A1 (en) * 2020-01-06 2021-07-15 Samsung Electronics Co., Ltd. Method and apparatus for performing communication in wireless communication system
EP4079094B1 (en) * 2020-02-27 2025-01-15 Sharp Kabushiki Kaisha User equipment and method for small data transmission
JP7511016B2 (ja) * 2020-03-24 2024-07-04 鴻穎創新有限公司 Ｃｏｎｆｉｇｕｒｅｄ Ｇｒａｎｔ設定のための方法及びユーザ機器
EP4233377A4 (en) * 2020-10-21 2024-07-03 Nokia Technologies Oy Small data transmission procedure to random access procedure fallback

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120281566A1 (en) 2011-04-01 2012-11-08 Interdigital Patent Holdings, Inc. Method and apparatus for controlling connectivity to a network
US20180049244A1 (en) * 2016-08-12 2018-02-15 Electronics And Telecommunications Research Institute State transition method based on random access procedure in communication system
WO2018084762A1 (en) * 2016-11-04 2018-05-11 Telefonaktiebolaget Lm Ericsson (Publ) Methods, computer program, carrier, computer program product and apparatus for managing small data transmissions from user equipments
US20180227961A1 (en) 2017-02-03 2018-08-09 Motorola Mobility Llc Configuration information for an inactive state
EP3361820A1 (en) * 2017-02-10 2018-08-15 Samsung Electronics Co., Ltd. Method and apparatus for inactive mode operation in wireless communication system
WO2018174427A1 (en) * 2017-03-24 2018-09-27 Samsung Electronics Co., Ltd. Method and device for controlling data transmission state
CN108924964A (zh) * 2017-04-07 2018-11-30 中兴通讯股份有限公司 保证通信连续性的方法和用户设备
US20190037447A1 (en) 2017-07-27 2019-01-31 Lg Electronics Inc. Method and apparatus for performing edt
WO2021136474A1 (en) 2019-12-31 2021-07-08 FG Innovation Company Limited Method of small data transmission and related device
WO2021179317A1 (en) 2020-03-13 2021-09-16 Lenovo (Beijing) Limited Method and apparatus for small data transmission

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON (RAPPORTEUR: "Report of [108#19] When to resume DRBs in UP optimization for 5GC", 3GPP DRAFT; R2-2000982, 3RD GENERATION PARTNERSHIP
See also references of EP4128876A4

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021232305A1 (en) 2020-05-20 2021-11-25 Nec Corporation Method, device and computer readable medium for communications
EP4154633A4 (en) * 2020-05-20 2023-09-06 NEC Corporation Method, device and computer readable medium for communications
US12588104B2 (en) 2020-05-20 2026-03-24 Nec Corporation Method, device and computer readable medium for communications
WO2023133333A3 (en) * 2022-01-10 2023-08-10 Google Llc Managing measurement in small data transmission
WO2023134409A1 (zh) * 2022-01-14 2023-07-20 荣耀终端有限公司 数据传输方法、装置及系统

Also Published As

Publication number Publication date
EP4128876A4 (en) 2023-04-26
CN115552961B (zh) 2025-04-29
JP7540502B2 (ja) 2024-08-27
EP4128876A1 (en) 2023-02-08
CN115552961A (zh) 2022-12-30
JP2023519587A (ja) 2023-05-11
US20230379815A1 (en) 2023-11-23

Similar Documents

Publication Publication Date Title
WO2021189462A1 (en) Method, device and computer storage medium of communication
JP7655401B2 (ja) ユーザ装置およびユーザ装置の方法
JP7704446B2 (ja) 端末デバイスによって実行される方法、及び端末デバイス
CN116114332B (zh) 用于通信的方法、设备和计算机存储介质
US12507306B2 (en) Method, device and computer storage medium of communication
JP2023519587A5 (https=)
US11849497B2 (en) Methods, devices, and medium for handling of non-SDT data
JP2024113129A (ja) 端末装置、通信のための方法、基地局及び基地局の方法
JP7697597B2 (ja) 端末装置、通信装置及び端末装置の方法
US12581562B2 (en) Methods, devices, and medium for communication
US20250142658A1 (en) Method, device and computer storage medium of communication
WO2022120632A1 (en) Method, device and computer storage medium of communication

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202217054325

Country of ref document: IN

ENP Entry into the national phase

Ref document number: 2022558192

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2020926571

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2020926571

Country of ref document: EP

Effective date: 20221027

NENP Non-entry into the national phase

Ref country code: DE

WWG Wipo information: grant in national office

Ref document number: 202080099120.5

Country of ref document: CN

WWG Wipo information: grant in national office

Ref document number: 202217054325

Country of ref document: IN