TECHNICAL FIELD
5 [0001] 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.
BACKGROUND
10 [0002] Typically, a terminal device in an inactive state may still have small and infrequent
data traffic to be transmitted (also referred to as SDT hereinafter). Until the third
generation partnership project (3GPP) Release 16, the inactive state cannot support data
transmission, and the terminal device has to resume the connection for any downlink and
uplink data. Connection setup and subsequently release to the inactive state happens for
15 each data transmission whatever small and infrequent the data packets are. This will result
in unnecessary power consumption and signaling overhead.
20
[0003] In this event, 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. Thus, how to control SDT has become a hot issue.
SUMMARY
[0004] In general, embodiments of the present disclosure provide methods, devices and
computer storage media of communication for SDT control.
[0005] In a first aspect, there is provided a method of communication. The method
25 compnses: 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
30 network device while the terminal device is in the inactive state.
[0006] In a second aspect, there is provided a method of communication. The method
1
wo 2021/189462 PCT/CN2020/081817
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.
5 [0007] In a third aspect, there is provided a terminal device. The terminal device
comprises 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.
[0008] In a fourth aspect, there is provided a network device. The network device
10 comprises 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.
[0009] In a fifth aspect, there is provided a computer readable medium having instructions
stored thereon. The instructions, when executed on at least one processor, cause the at
15 least one processor to perform the method according to the first aspect of the present
disclosure.
[0010] In a sixth aspect, there is provided 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
20 present disclosure.
[0011] Other features of the present disclosure will become easily comprehensible
through the following description.
BRIEF DESCRIPTION OF THE DRAWINGS
25 [0012] Through the more detailed description of some embodiments of the present
disclosure in the accompanying drawings, the above and other objects, features and
advantages of the present disclosure will become more apparent, wherein:
[0013] FIG. 1 illustrates an example communication network in which some embodiments
of the present disclosure can be implemented;
30 [0014] FIG. 2 illustrates a schematic diagram illustrating a process of communication for
SDT control according to some embodiments of the present disclosure;
2
wo 2021/189462 PCT/CN2020/081817
[0015] FIG. 3 illustrates an example method of communication implemented at a terminal
device in accordance with some embodiments of the present disclosure;
[0016] FIG. 4 illustrates an example method of transmission of uplink data in an inactive
state in accordance with some embodiments of the present disclosure;
5 [0017] 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;
[0018] FIG. 6 illustrates an example method of determining whether subsequent
transmission is supported in accordance with some embodiments of the present disclosure;
[0019] FIG. 7 illustrates an example method of communication implemented at a network
10 device in accordance with some embodiments of the present disclosure;
[0020] FIG. 8 illustrates another example method of communication implemented at a
network device in accordance with some embodiments of the present disclosure;
[0021] FIG. 9 illustrates another example method of communication implemented at a
network device in accordance with some embodiments of the present disclosure; and
15 [0022] FIG. 10 is a simplified block diagram of a device that is suitable for implementing
embodiments of the present disclosure.
[0023] Throughout the drawings, the same or similar reference numerals represent the
same or similar element.
20 DETAILED DESCRIPTION
[0024] Principle of the present disclosure will now be described with reference to some
embodiments. It is to be understood that these embodiments are described only for the
purpose of illustration and help those skilled in the art to understand and implement the
present disclosure, without suggesting any limitations as to the scope of the disclosure.
25 The disclosure described herein can be implemented in various manners other than the ones
described below.
[0025] In the following description and claims, unless defined otherwise, all technical and
scientific terms used herein have the same meaning as commonly understood by one of
ordinary skills in the art to which this disclosure belongs.
30 [0026] As used herein, the term "terminal device" refers to any device having wireless or
wired communication capabilities. Examples of the terminal device include, but not
3
wo 2021/189462 PCT/CN2020/081817
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 (loT) devices, Internet of Everything (IoE) devices,
machine type communication (MTC) devices, device on vehicle for V2X communication
5 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. The term
"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. In addition, the term
10 "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
15 node, a pica node, and the like.
[0027] In one embodiment, 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. In one
20 embodiment, the first network device may be a first RAT device and the second network
device may be a second RAT device.
the second RAT device is gNB.
In one embodiment, the first RAT device is eNB and
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. In one embodiment, first information may be transmitted to the
25 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.
In one embodiment, 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
30 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.
[0028] As used herein, 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'
4
wo 2021/189462 PCT/CN2020/081817
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,'
5 and the like may refer to different or same objects. Other definitions, explicit and implicit,
may be included below.
[0029] In some examples, 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
10 alternatives can be made, and such selections need not be better, smaller, higher, or
otherwise preferable to other selections.
[0030] FIG. 1 illustrates a schematic diagram of an example communication network 100
in which embodiments of the present disclosure can be implemented. As shown in FIG. 1,
the communication network 100 may include a network device 110 and a terminal device
15 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. For example, 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.
20 [0031] It is to be understood that the number and type of devices in FIG. 1 are given for
the purpose of illustration without suggesting any limitations to the present disclosure.
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
25 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.
[0032] 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
30 Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA),
GSM EDGE Radio Access Network (GERAN), Machine Type Communication (MTC) and
the like. Furthermore, the communications may be performed according to any generation
5
wo 2021/189462 PCT/CN2020/081817
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
(lG), the second generation (2G), 2.5G, 2.75G, the third generation (3G), the fourth
generation (4G), 4.5G, the fifth generation (5G) communication protocols.
5 [0033] As mentioned above, 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). In
some embodiments, 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 1M/email clients and other applications, and push
10 notifications from various applications. In some embodiments, 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.
15 [0034] Currently, a RACH-based scheme and transmission on pre-configured PUSCH
have been approved to perform SDT in an inactive of a terminal device. However, no
further detailed solutions on how to control the performance of SDT are proposed.
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
20 device. Principles and implementations of the present disclosure will be described in
detail below with reference to the figures.
[0035] 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
25 process 200 may involve the terminal device 120 and the network device 110 as illustrated
in FIG. 1.
[0036] In case that the terminal device 120 in an inactive state has data packets (i.e.,
uplink data) to be transmitted, as shown in FIG. 2, the terminal device 120 may determine
201 whether the uplink data is to be transmitted in the inactive state. That is, the terminal
30 device 120 may decide to whether perform SDT for transmission of the uplink tata.
According to embodiments of the present disclosure, the triggering of SDT is based on
different traffic or services that trigger the transmission of the uplink data.
6
wo 2021/189462 PCT/CN2020/081817
[0037] In some embodiments, 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
5 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.
[0038] In some embodiments for condition 4 ), the terminal device 120 may determine at
least one of an access category and an access identity of the traffic; and in accordance with
10 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. In some embodiments, the access category or the
access identity that supports SDT may be predefined. In some alternative embodiments,
the access category or the access identity that supports SDT may be broadcasted by system
15 information from the network device 110. In some alternative embodiments, 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.
[0039] In some alternative embodiments, a certain access category or access identity for
20 SDT may be introduced. For example, the value of the certain access category or access
identity may be 10 or any other suitable numbers. In some alternative embodiments, a set
of access categories or access identities may be considered to support SDT. For example,
potential access categories or access identities that can be considered to support SDT may
be 11-15 or any other suitable numbers.
25 [0040] In some alternative embodiments for condition 4 ), 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. In some embodiments, the 5QI value that supports SDT may be predefined.
30 In some alternative embodiments, the 5QI value that supports SDT may be broadcasted by
system information from the network device 110. In some alternative embodiments, 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. In
7
wo 2021/189462 PCT/CN2020/081817
some alternative embodiments, a certain 5QI value for SDT may be introduced. For
example, potential 5QI value that can be considered to support SDT may be 66 or any other
suitable numbers.
[0041] In some alternative embodiments for condition 4), the terminal device 120 may
5 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. In
some embodiments, 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
10 on the stored UE context. In some alternative embodiments, 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. In some alternative embodiments, 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
15 indication.
[0042] In some alternative embodiments for condition 4 ), 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
20 layer, whether the uplink data is to be transmitted in the inactive state.
[0043] As an additional embodiment for the above embodiments about condition 4 ), 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
25 state. In some embodiments, the buffered content may refer to total uplink data and
signaling available for transmission plus MAC header and where required, MAC control
elements (CE).
[0044] In some embodiments, the threshold size may be broadcasted by system
information from the network device 110. In some alternative embodiments, the threshold
30 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.
8
wo 2021/189462 PCT/CN2020/081817
[0045] The size of the buffered content can be used in combined with one or more of
access categories, access identities, 5Qis and DRBs. In some embodiments, 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
5 RRC layer of the terminal device 120 can initiate SDT procedure, instead of normal data
transmission (also referred to as NDT hereinafter).
[0046] Return to FIG. 2, in response to determining 201 that the uplink data is to be
transmitted in the inactive state, the terminal device 120 may resume 202 radio bearers for
the transmission of the uplink data in the inactive state. In some embodiments, the RRC
10 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. In addition, the RRC layer of the
terminal device 120 may resume a signaling radio bearer 1 (SRB 1) 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.
15 [0047] 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
20 120 may transmit 205, with the configured grant information, the uplink data in the inactive
state.
[0048] In accordance with a determination that the configured grant information is not
stored or the TA is not valid, the terminal device 120 may decide to transmit, based on a
random access procedure, the uplink data in the inactive state. For example, the RRC
25 layer of the terminal device 120 may configured the lower layer (i.e., MAC layer) to
perform random access based SDT.
[0049] Upon transmitting the uplink data based on a random access procedure, 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
30 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
9
wo 2021/189462 PCT/CN2020/081817
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.
[0050] In some embodiments, the RRC layer of the terminal device 120 may determine
5 whether the subsequent transmission of the uplink data is supported by both the terminal
device 120 and the network device 110. According to embodiments of the present
disclosure, 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
10 resources (i.e., reusing the configured grant type 1 when a time advance (TA) associated
with the transmission is valid). The dynamic grant based subsequent SDT refers to
transmission of uplink small data on dynamically scheduled PUSCH resources.
[0051] In some embodiments, information about at least one of whether the subsequent
transmission can be supported by the network device 110 and which types of the
15 subsequent transmission can be supported by the network device 110 may be broadcasted
by system information from the network device 110. In some embodiments, 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
20 110, for example, RRCRelease message or any other suitable messages. In some
embodiments, 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.
[0052] In accordance with a determination that the subsequent transmission IS not
25 supported by both the terminal device 120 and the network device 110, determine that the
subsequent transmission is not supported.
[0053] In some additional embodiments, m accordance with a determination that the
subsequent transmission is supported by both the terminal device 120 and the network
device 110, the terminal device 120 may further determine whether the traffic supports the
30 subsequent transmission of the uplink data. In some embodiments, 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.
10
wo 2021/189462 PCT/CN2020/081817
[0054] In some additional embodiments, in accordance with a determination that the
traffic supports the subsequent transmission of the uplink data, 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
5 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
10 is supported.
[0055] In accordance with a determination that the traffic does not support the subsequent
transmission, the terminal device 120 may determine that the subsequent transmission is
not supported.
[0056] Return to FIG. 2 again, upon determining that the subsequent transmission is not
15 supported and informing the MAC layer that the subsequent transmission is not supported
(i.e., only one shot SDT is 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. In some embodiments, the buffered content may refer to total uplink data
and signaling available for transmission plus MAC header and where required, MAC CE.
20 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.
[0057] In accordance with a determination that the size of the buffered content is less than
or equal to the threshold size, 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
25 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.
[0058] In accordance with a determination that the size of the buffered content is larger
than the threshold size or there is no dedicated resource having a size larger than or equal to
30 the threshold size, the terminal device 120 may cancel the transmission of the uplink data in
the inactive state. In some embodiments, 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
11
wo 2021/189462 PCT/CN2020/081817
performed for transmission of the uplink data.
[0059] In response to determining 206 that the subsequent transmission is supported, 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
5 determination and transmission can be carried out in any suitable ways.
[0060] In some additional embodiments where the uplink data is transmitted based on a
random access procedure, 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. For example,
10 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. It should be noted that any other suitable forms are also feasible.
[0061] In some alternative or additional embodiments where the uplink data is transmitted
15 based on a random access procedure, 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. It should be noted that this is merely an example,
20 and any other suitable forms are also feasible.
[0062] Return to FIG. 2 again, upon receiving the uplink data, the network device 110
may transmit 210 a response to the reception of the uplink data. In some embodiments
where the subsequent transmission is not supported, the network device 110 may reply the
terminal device 120 with a first RRC message that informs the terminal device 120 to
25 suspend the radio bearers for the transmission of the uplink data in the inactive state. For
example, the first RRC message may be a RRCRelease message. Alternatively, the first
RRC message may be a RRCReject message. It should be noted that any other suitable
messages are also feasible.
[0063] In some embodiments where anchor relocation occurs from a second network
30 device (not shown) to the network device 110, 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
12
wo 2021/189462 PCT/CN2020/081817
state to the inactive state, i.e., a last serving network device.
[0064] Upon receiving the first RRC message, 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
5 in the inactive state. In addition, the terminal device 120 may further suspend SRB 1 and
SRB2. In this way, the terminal device 120 returns to a normal inactive state without data
transmission.
[0065] In some embodiments where the subsequent transmission IS supported, the
network device 110 may reply the terminal device 120 with a second RRC message that
10 comprises an uplink resource configuration for the subsequent transmission. In some
embodiments, the uplink resource configuration may be associated with dynamic grant for
the subsequent transmission. In some alternative embodiments, the uplink resource
configuration may be associated with configured grant for the subsequent transmission.
For example, the second RRC message may be a RRCRelease message. Alternatively, the
15 second RRC message may be a RRCReject message. It should be noted that any other
suitable messages are also feasible.
[0066] In some embodiments where anchor relocation occurs from a second network
device (not shown) to the network device 110, the second RRC message may comprise
suspend configuration. The second network device is a network device serving the
20 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.
[0067] Upon receiving the second RRC message, 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
25 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.
[0068] Currently, for 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
30 (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. However,
during subsequent SDT, as there is no measurement and report mechanism, the network
13
wo 2021/189462 PCT/CN2020/081817
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.
[0069] In view of the above, embodiments of the present disclosure provide network
5 control of SDT upon state transition. In some embodiments where the cell reselection
occurs during the transmission (first shot SDT) of the uplink data while no response is
received from the network device 110, the terminal device 120 may enter an idle state, and
retransmit the uplink data to the third network device.
[0070] In some embodiments where the cell reselection occurs during the subsequent
10 transmission of the uplink data or during transmission of the uplink data based on
configured grant information, 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.
In some alternative embodiments, the terminal device 120 may stop the subsequent
transmission, but remain at the inactive state. In this case, the terminal device 120 may
15 suspend the radio bearers for the transmission of the uplink data in the inactive state. For
example, the terminal device 120 may suspend all SRBs and DRBs for SDT except SRBO,
and indicate from the RRC layer to the lower layer (i.e., MAC layer) of PDCP suspend. In
some embodiments, the terminal device 120 may further release an uplink resource
configuration for the transmission of the uplink data in the inactive state. In some
20 embodiments, the terminal device 120 may further reevaluate the validity of SDT and
reinitiate SDT if needed.
[0071] In some additional or alternative embodiments where the cell reselection occurs
during the subsequent transmission of the uplink data or during transmission of the uplink
data based on configured grant information, the terminal device 120 may generate a second
25 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.
[0072] In some embodiments, the terminal device 120 may transmit the second indication
30 via a RRC message. For example, the RRC message may be a UEAssistanceinfomation
message or any other suitable messages. In some alternative embodiments, the terminal
device 120 may transmit the second indication via a MAC CE. For example, the MAC
14
wo 2021/189462 PCT/CN2020/081817
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. In some alternative embodiments, the terminal device 120
may transmit the second indication via a physical (PHY) layer indication. For example,
the terminal device 120 may use a dedicated scheduling request (SR) configuration to
5 indicate the cell reselection during the subsequent SDT or configured grant based SDT.
[0073] Generally, there are some cases that the terminal device 120 will changes from the
inactive state to an idle state. In some embodiments, when 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. In some embodiments, in case of inability to
10 comply with RRCResume, the terminal device 120 will changes from the inactive state to
an idle state. In some embodiments, when 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. In some embodiments, in case of cell re-selection
while the timer T319 or T302 is running, the terminal device 120 will changes from the
15 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.
[0074] In these embodiments where the terminal device 120 changes from the inactive
state to an idle state, the terminal device 120 may generate a third indication about the
20 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. For
example, 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
25 similar way as the second indication, and its details are not repeated here.
[0075] With the process described with above, SDT can be well controlled.
Corresponding to the process, 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.
30 [0076] FIG. 3 illustrates an example method 300 of communication implemented at a
terminal device in accordance with some embodiments of the present disclosure. For
example, the method 300 may be performed at the terminal device 120 as shown in FIG. 1.
15
wo 2021/189462 PCT/CN2020/081817
For the purpose of discussion, in the following, 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.
5 [0077] As shown in FIG. 3, at block 310, 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.
[0078] In some embodiments, the terminal device 120 may determine at least one of an
10 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.
[0079] In some alternative embodiments, the terminal device 120 may determine a QoS
15 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.
[0080] In some alternative embodiments, the terminal device 120 may determine one or
more DRBs for the traffic, and in accordance with a determination that the one or more
20 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.
[0081] In some alternative embodiments, 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
25 determine, based on the first indication, whether the uplink data is to be transmitted in the
inactive state.
[0082] In some additional embodiments, 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
30 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.
16
wo 2021/189462 PCT/CN2020/081817
[0083] At block 320, the terminal device 120 resumes radio bearers for the transmission
of the uplink data in the inactive state. In some embodiments, 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
5 202 with reference to FIG. 2 and other details are omitted here.
[0084] At block 330, the terminal device 120 transmits the uplink data to the network
device 110 based on the configuration while the terminal device 120 is in the inactive state.
Its details will be described below with reference to FIG. 4. FIG. 4 illustrates an example
method 400 of transmission of uplink data in an inactive state in accordance with some
10 embodiments of the present disclosure. For example, the method 400 may be performed
at the terminal device 120 as shown in FIG. 1. For the purpose of discussion, in the
following, 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.
15 [0085] As shown in FIG. 4, at block 410, 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
20 120 may transmit, with the configured grant information, the uplink data in the inactive
state.
[0086] If determining at block 410 that the configured grant information is not stored or if
determining at block 420 that the TA is not valid, at block 440, the terminal device 1210
may transmit, based on a random access procedure, the uplink data in the inactive state.
25 [0087] 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.
For example, the method 500 may be performed at the terminal device 120 as shown in FIG.
1. For the purpose of discussion, in the following, the method 500 will be described with
reference to FIG. 1. It is to be understood that the method 500 may include additional
30 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
17
wo 2021/189462 PCT/CN2020/081817
corresponding network control scheme.
[0088] As shown in FIG. 5, at block 510, 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
5 600 of determining whether subsequent transmission is supported in accordance with some
embodiments of the present disclosure. For example, the method 600 may be performed
at the terminal device 120 as shown in FIG. 1. For the purpose of discussion, in the
following, 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
10 some blocks as shown, and the scope of the present disclosure is not limited in this regard.
[0089] As shown in FIG. 6, at block 610, 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
15 enter block 650. At block 650, the terminal device 120 may determine that the subsequent
transmission is not supported.
[0090] If determining at block 610 that the subsequent transmission is supported by both
the terminal device 120 and the network device 110, at block 620, the terminal device 120
may determine whether the traffic supports the subsequent transmission. If determining at
20 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.
[0091] If determining at block 620 that the traffic supports the subsequent transmission,
the terminal device 120 may determine, at block 630, whether the terminal device 120
25 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.
30 [0092] If determining at block 630 that the terminal device 120 supports the uplink
resource configuration type, the terminal device 120 may determine, at block 640, that the
subsequent transmission is supported. Other details for determining whether the
18
wo 2021/189462 PCT/CN2020/081817
subsequent transmission is supported are similar with that described in 206 with reference
to FIG. 2, and thus are not repeated here.
[0093] It should be noted that the above example in FIG. 6 is merely for illustration, and
is not intended to limit the present disclosure. Any other suitable solutions are also
5 feasible for determining whether the subsequent transmission is supported.
[0094] Now return to FIG. 5, if determining at block 510 that the subsequent transmission
is not supported, at block 520, the terminal device 120 may determine whether a size of
buffered content associated with the traffic is larger than a threshold size. In some
embodiments, the buffered content may refer to total uplink data and signaling available for
10 transmission plus MAC header and where required, MAC CE. In some embodiments, 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.
[0095] If determining at block 520 that the size of the buffered content associated with the
15 traffic is not larger than the threshold size, i.e., less than or equal to the threshold size, at
block 530, 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.
20 [0096] If determining at block 530 that there is no dedicated resource having a size larger
than or equal to the threshold size, or if determining at block 520 that the size of the
buffered content is larger than the threshold size, the process enters block 550. At block
550, the terminal device 120 may cancel the transmission of the uplink data in the inactive
state.
25 [0097] If determining at block 510 that the subsequent transmission is supported, at block
560, 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. In some embodiments, the
operations at block 560 and 570 may be carried out by the method 400 described above. It
30 should be noted that, any other suitable methods are also feasible.
[0098] In some embodiments, 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
19
wo 2021/189462 PCT/CN2020/081817
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. In some embodiments where
anchor relocation occurs from a second network device to the network device 110, the RRC
message may comprise suspend configuration. The second network device is a network
5 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.
[0099] In some alternative embodiments, the terminal device 120 may receive, from the
network device, a second RRC message comprising an uplink resource configuration for
10 subsequent transmission of the uplink data, and perform, with the uplink resource
configuration, the subsequent transmission in the inactive state.
[00100] In some embodiments where the terminal device 120 reselects from a first cell
served by the network device 110 to a second cell served by a third network device not
shown during the transmission of the uplink data while no response to the transmission of
15 the uplink data is received from the network device 110, 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.

WHAT IS CLAIMED IS:
1. A method of communication, comprising:
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
5 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
10 the terminal device is in the inactive state.
15
20
25
30
2. The method of claim 1, wherein the determining comprises:
determining 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.
3. The method of claim 1, wherein the determining comprises:
determining a quality of service (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, determining that the uplink data is to be
transmitted in the inactive state.
4. The method of claim 1, wherein the determining comprises:
determining 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.
5. The method of claim 1, wherein the determining comprises:
receiving, at a radio resource control (RRC) layer of the terminal device and from a
non-access stratum (NAS) layer of the terminal device, a first indication about whether the
28
5
10
wo 2021/189462 PCT/CN2020/081817
uplink data is to be transmitted in the inactive state; and
determining, based on the first indication, whether the uplink data IS to be
transmitted in the inactive state.
6. The method of any of claims 2-5, wherein the determining further comprises:
determining 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.
7. The method of claim 1, wherein the resuming comprises:
resuming one or more data radio bearers (DRBs) that are needed to support the
transmission of the uplink data in the inactive state.
8. The method of claim 1, wherein the transmitting comprises:
15 determining whether configured grant information is stored for the transmission of
20
25
the uplink data in the inactive state;
in accordance with a determination that the configured grant information is stored,
determining 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, transmitting, with the
configured grant information, the uplink data in the inactive state; and
in accordance with a determination that the configured grant information is not
stored or the TA is not valid, transmitting, based on a random access procedure, the uplink
data in the inactive state.
9. The method of claim 8, wherein transmitting, based on the random access
procedure, the uplink data in the inactive state comprises:
generating a radio resource control (RRC) message indicating that the uplink data is
transmitted in the inactive state;
30 transmitting the RRC message and the uplink data to the network device in the
random access procedure.
10. The method of claim 8, wherein transmitting, based on the random access
procedure, the uplink data in the inactive state comprises:
29
wo 2021/189462 PCT/CN2020/081817
providing, from a radio resource control (RRC) layer to a media access control
(MAC) layer of the terminal device, a control element of a media access control layer, the
control element carrying an identity of the terminal device; and
transmitting, to the network device, the control element and the uplink data in the
5 random access procedure.
11. The method of claim 8, wherein transmitting, based on the random access
procedure, the uplink data in the inactive state comprises:
determining, at a radio resource control (RRC) layer of the terminal device, whether
10 subsequent transmission of the uplink data is supported;
in accordance with a determination that the subsequent transmission IS not
supported, determining, at a media access control (MAC) layer of the terminal device,
whether a size of buffered content associated with the traffic is larger than a threshold size;
in accordance with a determination that the size is less than or equal to the threshold
15 size, determining whether there is a dedicated resource having a size larger than or equal to
the threshold size; and
20
25
in accordance with a determination that there is the dedicated resource having a size
larger than or equal to the threshold size, transmitting, with the dedicated resource, the
uplink data in the inactive state.
12. The method of claim 11, further comprising:
in accordance with a determination that the size of the buffered content is larger than
the threshold size or there is no dedicated resource having a size larger than or equal to the
threshold value, cancelling the transmission of the uplink data in the inactive state.
13. The method of claim 11, wherein determining whether the subsequent
transmission is supported comprises:
determining whether the subsequent transmission of the uplink data is supported by
both the terminal device and the network device; and
30 m accordance with a determination that the subsequent transmission IS not
supported by both the terminal device and the network device, determining that the
subsequent transmission is not supported.
14. The method of claim 13, further comprising:
30
wo 2021/189462 PCT/CN2020/081817
in accordance with a determination that the subsequent transmission is supported by
both the terminal device and the network device, determining whether the traffic supports
the subsequent transmission of the uplink data; and
in accordance with a determination that the traffic does not support the subsequent
5 transmission, determining that the subsequent transmission is not supported.
15. The method of claim 14, further comprising:
in accordance with a determination that the traffic supports the subsequent
transmission of the uplink data, determining an uplink resource configuration type for the
10 subsequent transmission supported by the traffic;
in accordance with a determination that the terminal device does not support the
uplink resource configuration type, determining that the subsequent transmission is not
supported; and
in accordance with a determination that the terminal device supports the uplink
15 resource configuration type, determining that the subsequent transmission is supported.
16. The method of claim 11, further comprising:
in accordance with a determination that the subsequent transmission is supported,
determining an uplink resource configuration for the transmission of the uplink
20 data; and
transmitting the uplink data based on the uplink resource configuration.
17. The method of claim 1, further comprising:
receiving, from the network device, a first radio resource control (RRC) message
25 that informs the terminal device to suspend radio bearers for the transmission of the uplink
data in the inactive state; and
suspending the radio bearers in response to receiving the first RRC message.
18. The method of claim 1, wherein the RRC message compnses suspend
30 configuration in case of anchor relocation from a second network device to the network
device, the second network device being a network device serving the terminal device
immediately before the terminal device changes from a connected state to the inactive state.
19. The method of claim 1, further comprising:
31
wo 2021/189462 PCT/CN2020/081817
receiving, from the network device, a second radio resource control (RRC) message
comprising an uplink resource configuration for subsequent transmission of the uplink data;
and
performing, with the uplink resource configuration, the subsequent transmission in
5 the inactive state.
20. The method of claim 1, further comprising:
in response to reselecting from a first cell served by the network device to a second
cell served by a third network device during the transmission of the uplink data while no
10 response to the transmission of the uplink data is received from the network device,
entering an idle state; and
retransmitting the uplink data to the third network device.
21. The method of claim 1, further comprising:
15 in response to reselecting from a first cell served by the network device to a second
cell served by a third network device during subsequent transmission of the uplink data or
during transmission of the uplink data based on configured grant information,
entering an idle state; and
releasing an uplink resource configuration for the transmission of the uplink
20 data in the inactive state.
22. The method of claim 1, further comprising:
in response to reselecting from a first cell served by the network device to a second
cell served by a third network device during subsequent transmission of the uplink data or
25 during transmission of the uplink data based on configured grant information,
stopping the subsequent transmission;
suspending the radio bearers for the transmission of the uplink data in the
inactive state;
releasing an uplink resource configuration for the transmission of the uplink
30 data in the inactive state;
redetermining 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, reinitiating the transmission of the uplink data.
32
wo 2021/189462 PCT/CN2020/081817
23. The method of claim 1, further comprising:
in response to reselecting from a first cell served by the network device to a second
cell served by a third network device during subsequent transmission of the uplink data or
5 during transmission of the uplink data based on configured grant information,
10
15
20
25
generating a second indication about the reselection; and
transmitting the second indication to the network device.
24. The method of claim 1, further comprising:
in response to changing from the inactive state to an idle state,
generating a third indication about the change;
transmitting the third indication to the network device; and
releasing an uplink resource configuration for the transmission of the uplink
data in the inactive state.
25. A method of communication, comprising:
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.
26. The method of claim 25, further comprising:
transmitting, to the terminal device, configured grant information for the
transmission of the uplink data in the inactive state; and
wherein the receiving comprises:
receiving the uplink data based on the configured grant information.
27. The method of claim 25, wherein the receiving comprises:
receiving, from the terminal device, a radio resource control (RRC) message and the
30 uplink data in a random access procedure, the RRC message indicating that the uplink data
is transmitted in the inactive state.
28. The method of claim 25, further comprising:
transmitting, to the terminal device, information about whether the network device
33
wo 2021/189462 PCT/CN2020/081817
supports subsequent transmission of the uplink data.
29. The method of claim 25, wherein the transmitting comprises:
transmitting, in the response, a first radio resource control (RRC) message that
5 informs the terminal device to suspend radio bearers for the transmission of the uplink data
in the inactive state.
30. The method of claim 29, wherein the first RRC message comprises suspend
configuration in case of anchor relocation from a second network device to the network
10 device, the second network device being a network device serving the terminal device
immediately before the terminal device changes from a connected state to the inactive state.
31. The method of claim 25, wherein the transmitting comprises:
transmitting, in the response, a second radio resource control (RRC) message
15 comprising an uplink resource configuration for subsequent transmission of the uplink data.
32. The method of claim 31, wherein the second RRC message comprises suspend
configuration in case of anchor relocation from a second network device to the network
device, the second network device being a network device serving the terminal device
20 immediately before the terminal device changes from a connected state to the inactive state.
33. The method of claim 25, further comprising:
receiving, from the terminal device, a second indication about a reselection of the
terminal device from a first cell served by the network device to a second cell served by a
25 third network device during subsequent transmission of the uplink data or during
transmission of the uplink data based on configured grant information; and
30
stopping scheduling an uplink resource to the terminal device for the subsequent
transmission of the uplink data.
34. The method of claim 25, further comprising:
receiving, from the terminal device, a third indication about a change of the terminal
device from the inactive state to an idle state; and
stopping scheduling an uplink resource to the terminal device for subsequent
transmission of the uplink data.
34
wo 2021/189462
35. A terminal device comprising:
a processor; and
PCT/CN2020/081817
a memory coupled to the processor and storing instructions thereon, the instructions,
5 when executed by the processor, causing the terminal device to perform the method
according to any of claims 1 to 24.
36. A network device comprising:
a processor; and
10 a memory coupled to the processor and storing instructions thereon, the instructions,
when executed by the processor, causing the network device to perform the method
according to any of claims 25 to 34.
37. A computer readable medium having instructions stored thereon, the
15 instructions, when executed on at least one processor, causing the at least one processor to
perform the method according to any of claims 1 to 24.
38. A computer readable medium having instructions stored thereon, the
instructions, when executed on at least one processor, causing the at least one processor to
20 perform the method according to any of claims 25 to 34.