Small data transmission control

Abstract

Apparatuses, methods, and computer program products are provided. According to embodiments, a method is disclosed that includes determining whether to allow initiation of transmission of a signaling message using a small data transmission procedure in an inactive state of a user equipment; based on the determination, causing the user equipment to perform: transmitting the signaling message using the small data transmission procedure in the inactive state; or transmitting the signaling message using a procedure other than the small data transmission procedure.

Description

TECHNICAL FIELD

[0001] The present invention relates to a method and apparatus for controlling transmission of small amounts of data from a user equipment to a wireless network when the user equipment is in an inactive state. BACKGROUND

[0002] This section is intended to provide background information to facilitate a better understanding of the invention as set forth in the claims. The description herein can include concepts that can be sought, but it need not be prior to the conception or seeking of the concepts. Thus, unless the prior art described herein explicitly identifies such information as being prior art to the present application, it is not to be construed as being prior art to the present application merely because it is included herein. The description herein is intended as a prelude to the detailed description of the application.

[0003] 5G-NR (Fifth Generation New Radio) is a new radio access technology that has been developed by the Third Generation Partnership Project (3GPP) for the fifth generation of mobile networks. 5G-NR has been specified within 3GPP to be able to coexist with 4G-LTE (Long Term Evolution) in the same spectrum. In a 5G system, a mobile communication device can also be referred to as a user equipment (UE) and can be in different states depending on whether it is connected to the network or not. For example, when a mobile communication device does not have an active data communication connection, the mobile communication device can be in a so-called inactive state or idle state. If the mobile communication device has a message to send when the mobile communication device is in the inactive state, the mobile communication device should typically change state to a connected state and only after the connected state can the message or messages be sent.

[0004] The message to send can not always be long. Therefore, changing state before sending the message results in transmission of a control message for the state change and increases the latency. Furthermore, this signaling also increases the power consumption of the mobile communication device.

[0005] For small data packets, the signaling overhead from the inactive state can be a problem and due to more user equipments in NR, this signaling overhead can become a critical issue not only for network performance and efficiency but also for UE battery performance.

[0006] Therefore, a mechanism that enables transmission of relatively short messages in the inactive state without changing state can solve the increased power consumption and latency. SUMMARY

[0007] Some embodiments provide a method and apparatus for sending small amounts of data from a user equipment to a wireless network when the user equipment is in an inactive state.

[0008] Some embodiments are implemented in the context of a 5G communication system and relate to network implementation of mechanisms for determining which messages can be sent without changing the state of a user equipment from an inactive state to a connected state. In particular, some embodiments relate to controlling which radio resource control (RRC) messages are allowed to use small data transmission (SDT). According to embodiments, the network indicates the RRC messages that are allowed to use SDT, including whether the RRC message is sent using a dedicated RRC container or using an existing message. This can also include using a different signaling radio bearer (SRB) than usual, e.g. SRB2 for the message, or including the data in a container of a type indicated via the message.

[0009] According to embodiments, the network decides and controls which RRC messages can use SDT and indicates this to the UE via dedicated signaling or via broadcast. The following information can be indicated to the UE:

[0010] Which RRC messages are allowed to use SDT (also referred to as inactive state data transmission in this specification);

[0011] Whether a dedicated RRC container or an existing message is used;

[0012] Whether any UE-initiated signaling (i.e. data without mobile direction, MO-data) is allowed;

[0013] Whether size thresholds are defined for “UL data” and “RRC message(s)” or any priority.

[0014] A separate SRB can be introduced to use SDT in RRC_INACTIVE.

[0015] According to some aspects, the subject matter of the independent claims is provided. Some further aspects are defined in the dependent claims. Embodiments not falling under the scope of the claims are to be interpreted as examples helpful for understanding the present disclosure.

[0016] According to a first aspect, a user equipment is provided, comprising means for:

[0017] determining whether transmission of a signaling message using a small data transmission procedure is allowed to be initiated in an inactive state of the user equipment;

[0018] based on the determination, causing the user equipment to perform:

[0019] transmitting the signaling message in the inactive state using the small data transmission procedure; or

[0020] transmitting the signaling message using a procedure other than the small data transmission procedure.

[0021] According to a second aspect, there is provided a method comprising:

[0022] determining whether transmission of a signalling message using a small data transmission procedure is allowed to be initiated in an inactive state of the user equipment;

[0023] based on the determination, causing the user equipment to perform:

[0024] transmitting the signalling message using the small data transmission procedure in the inactive state; or

[0025] transmitting the signalling message using a procedure other than the small data transmission procedure.

[0026] According to a third aspect, there is provided an apparatus comprising: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform:

[0027] determining whether transmission of a signalling message using a small data transmission procedure is allowed to be initiated in an inactive state of the user equipment;

[0028] based on the determination, causing the apparatus to perform:

[0029] transmitting the signalling message using the small data transmission procedure in the inactive state; or

[0030] transmitting the signalling message using a procedure other than the small data transmission procedure.

[0031] According to a fourth aspect, there is provided an apparatus comprising:

[0032] first circuitry configured to obtain one or more messages for transmission, the one or more messages having an indication of a cause of the message;

[0033] second circuitry configured to determine whether transmission of a signalling message using a small data transmission procedure is allowed to be initiated in an inactive state of the user equipment;

[0034] third circuitry configured to, based on the determination, cause the user equipment to perform:

[0035] transmitting the signalling message using the small data transmission procedure in the inactive state; or

[0036] transmitting the signalling message using a procedure other than the small data transmission procedure.

[0037] According to a fifth aspect, there is provided a computer program comprising computer readable program code which, when executed by at least one processor, causes an apparatus to perform at least the following:

[0038] determining whether to allow initiation of transmission of a signalling message using a small data transmission procedure in an inactive state of the user equipment;

[0039] based on the determination, causing the apparatus to:

[0040] transmit the signalling message using the small data transmission procedure in the inactive state; or

[0041] transmit the signalling message using a procedure other than the small data transmission procedure.

[0042] According to a sixth aspect, there is provided an apparatus comprising means for:

[0043] determining whether to enable transmission of a signalling message using a small data transmission procedure in an inactive state of the user equipment by the user equipment;

[0044] based on the determination, causing the apparatus to provide an indication to one or more user equipment whether transmission of a signalling message using a small data transmission procedure in an inactive state of the user equipment is enabled by the user equipment.

[0045] According to a seventh aspect, there is provided a method comprising:

[0046] determining whether to enable transmission of a signalling message using a small data transmission procedure in an inactive state of the user equipment by the user equipment;

[0047] based on the determination, causing the apparatus to provide an indication to one or more user equipment whether transmission of a signalling message using a small data transmission procedure in an inactive state of the user equipment is enabled by the user equipment.

[0048] According to an eighth aspect, there is provided an apparatus comprising: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to:

[0049] determining whether to enable transmission of a signalling message using a small data transmission procedure in an inactive state of the user equipment by the user equipment;

[0050] based on the determination, causing the apparatus to provide an indication to one or more user equipment whether transmission of a signalling message using a small data transmission procedure in an inactive state of the user equipment is enabled by the user equipment.

[0051] According to a ninth aspect, there is provided an apparatus comprising:

[0052] first circuitry configured to determine whether to enable transmission of a signalling message using a small data transmission procedure in an inactive state of the user equipment by the user equipment;

[0053] second circuitry configured to, based on the determination, cause the apparatus to provide an indication to one or more user equipments whether transmission of a signaling message by the user equipment using a small data transmission procedure in an inactive state of the user equipment is enabled.

[0054] According to a tenth aspect, there is provided a computer program comprising computer readable program code which, when executed by at least one processor, causes an apparatus to perform at least the following:

[0055] determining whether transmission of a signaling message by a user equipment using a small data transmission procedure in an inactive state of the user equipment is enabled;

[0056] based on the determination, causing the apparatus to provide an indication to one or more user equipments whether transmission of a signaling message by the user equipment using a small data transmission procedure in an inactive state of the user equipment is enabled. BRIEF DESCRIPTION OF DRAWINGS

[0057] For a more complete understanding of example embodiments of the present application, reference is now made to the following descriptions taken in connection with the accompanying drawings in which:

[0058] Figure 1 a block diagram showing one possible and non-limiting example in which these examples can be practiced;

[0059] Figure 2 a portion of a wireless network with several base stations and exemplary user equipments is shown;

[0060] Figure 3a an example of small data transmission with 2-step RACH transmission is shown;

[0061] Figure 3b an example of small data transmission with 4-step RACH transmission is shown;

[0062] Figure 4 an exemplary flow diagram according to an embodiment is shown, illustrating operation of a user equipment when sending a message as small data;

[0063] Figure 5 a flow diagram indication of network element data reasons that are allowed to be sent by a user equipment with a small data transmission mechanism according to an embodiment is shown;

[0064] Figure 6 a block diagram of an apparatus according to at least some embodiments is shown; and

[0065] Figure 7 a portion of an exemplary wireless communication access network according to at least some embodiments is shown. DETAILED DESCRIPTION

[0066] The following examples are illustrative. Although the specification can contain many specific embodiments, these are not intended to be exhaustive or limiting of the scope of the application, as described in the following examples. The examples are not intended to limit the scope of the claims to the specific examples described. The specification, examples, and data provide a description of the features of the present application. The description is not intended to be exhaustive or to be limited to the precise forms disclosed. The examples provide specific structure for one or more aspects of the application and should not be construed as limiting the scope of the application.

[0067] It should be noted here that in this specification the term "base station" refers to a logical element comprising logical communication system layers (e.g. LI, L2, L3). Base stations of different RATs can be implemented in the same hardware or in separate hardware. It should also be mentioned that although the expressions "each base station" and "each mobile station" or "each user equipment" can be used, these terms do not need to mean each and every existing base station, mobile station or user equipment, but rather base stations, mobile stations or user equipments in a certain area or set. For example, each base station can mean all base stations within a certain geographical area, or all base stations of a wireless communication network operator, or a subset of base stations of a wireless communication network operator.

[0068] Figure 1 A block diagram of one possible and non-limiting example in which these examples can be practiced is shown. A user equipment (UE) 110, a radio access network (RAN) node 170, and a network element 190 are illustrated. In Figure 1In the example, user equipment 110 wirelessly communicates with wireless network 100. User equipment is a wireless device that can access wireless network 100. User equipment 110 includes one or more processors 120, one or more memories 125, and one or more transceivers 130 interconnected via one or more buses 127. Each of the one or more transceivers 130 includes a receiver (Rx) 132 and a transmitter (Tx) 133. The one or more buses 127 may be address, data, or control buses and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optics, or other optical communication devices. The one or more transceivers 130 are connected to one or more antennas 128. The one or more memories 125 include computer program code 123. User equipment 110 includes a module 140 that can be implemented in various ways. Module 140 may be implemented in hardware as module 140-1, for example, as part of one or more processors 120. Module 140-1 may also be implemented as an integrated circuit or through other hardware such as a programmable gate array. In another example, module 140 may be implemented as module 140-2, which is implemented as computer program code 123 and executed by one or more processors 120. For example, one or more memories 125 and computer program code 123 may be configured, together with one or more processors 120, to cause user equipment 110 to perform one or more operations described herein. User equipment 110 communicates with RAN node 170 via wireless link 111. Modules 140-1 and 140-2 may be configured to implement the functions of the user equipment as described herein.

[0069] In this example, RAN node 170 is a base station that provides access to wireless network 100 for wireless devices such as user equipment 110. Therefore, RAN node 170 (and the base station) can also be referred to as an access point for the wireless communication network. RAN node 170 can be, for example, a base station for 5G (also known as New Radio (NR)). In 5G, RAN node 170 can be an NG-RAN node, defined as a gNB or ng-eNB. A gNB is a node that provides NR user plane and control plane protocol termination to the UE and connects to the 5GC (such as, for example, network element 190) via an NG interface. An ng-eNB is a node that provides E-UTRA user plane and control plane protocol termination to the UE and connects to the 5GC via an NG interface. An NG-RAN node can include multiple gNBs, and can also include a central unit (CU) (gNB-CU) 196 and a distributed unit (DU) (gNB-DU), where DU 195 is shown. Note that DU 195 can include a radio unit (RU) or be coupled to and control a RU. gNB-CU 196 is a logical node that hosts the Radio Resource Control (RRC), SDAP, and PDCP protocols of the gNB or the en-gNB for controlling the operation of one or more gNB-DUs. gNB-CU 196 terminates the F1 interface connected to gNB-DU 195. The F1 interface is illustrated as numeral 198, although numeral 198 also illustrates links between remote elements and centralized elements of RAN node 170, such as the link between gNB-CU 196 and gNB-DU 195. gNB-DU 195 is a logical node that hosts the RLC, MAC, and PHY layers of the gNB or en-gNB, and its operation is partially controlled by gNB-CU 196. One gNB-CU 196 supports one or more cells. A cell is supported by only one gNB-DU 195. gNB-DU 195 terminates the F1 interface 198 connected to gNB-CU 196. Note that DU 195 is considered to include, for example, transceiver 160 as part of an RU, but some examples may allow transceiver 160 to be part of a separate RU, for example, under the control of DU 195 and connected to DU 195. RAN node 170 may also be an eNB (evolved NodeB) base station for LTE (Long Term Evolution), or any other suitable base station or node.

[0070] RAN node 170 includes one or more processors 152, one or more memories 155, one or more network interfaces (N / WI / F) 161, and one or more transceivers 160 interconnected via one or more buses 157. Each of the one or more transceivers 160 includes a receiver (Rx) 162 and a transmitter (Tx) 163. The one or more transceivers 160 are connected to one or more antennas 158. The one or more memories 155 include computer program code 153. CU 196 may include processor(s) 152, memory(s) 155, and network interface 161. Note that DU 195 may also contain its own one or more memories and processor(s), and / or other hardware, but these are not shown.

[0071] RAN node 170 includes module 150, which includes one or both of portions 150-1 and / or 150-2. Modules 150-1 and / or 150-2 can be implemented in various ways. Module 150 can be implemented in hardware as module 150-1, for example, as part of one or more processors 152. Module 150-1 can also be implemented as an integrated circuit or by other hardware such as a programmable gate array. In another example, module 150 can be implemented as module 150-2, which is implemented as computer program code 153 and executed by one or more processors 152. For example, one or more memories 155 and computer program code 153 are configured, together with one or more processors 152, to cause RAN node 170 to perform one or more operations described herein. Note that the functionality of module 150 can be distributed, for example, distributed between DU 195 and CU 196, or implemented only in DU 195. Modules 150-1 and 150-2 can be configured to implement the functionality of the base station described herein. This functionality of the base station may include a location management function (LMF) implemented based on the functionality of the LMF described herein. This LMF may also be implemented as a location management component (LMC) within the RAN node 170.

[0072] One or more network interfaces 161 communicate on the network, for example, via links 176 and 131. Two or more gNBs 170 can communicate using, for example, link 176. Link 176 can be wired, wireless, or both, and can implement, for example, an Xn interface for 5G, an X2 interface for LTE, or other suitable interfaces for other standards.

[0073] One or more buses 157 may be address, data, or control buses and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optic or other optical communication equipment, wireless channels, etc. For example, one or more transceivers 160 may be implemented as a Remote Radio Header (RRH) 195 for LTE or a Distributed Unit (DU) 195 for a gNB implementation of 5G. Other elements of the RAN node 170 may be physically located differently from the RRH / DU 195, and one or more buses 157 may be partially implemented as, for example, optical fiber or other suitable network connections to connect other elements of the RAN node 170 (e.g., Central Unit (CU), gNB-CU) to the RRH / DU 195. Reference numeral 198 also indicates those suitable network links(s).

[0074] It should be noted that the description in this document indicates that a "unit" performs functions; however, it should be clear that the equipment forming the unit can perform these functions. Cells constitute part of a base station. That is, each base station can have multiple cells. For example, for a single carrier frequency and associated bandwidth, there can be three cells, each covering one-third of a 360-degree area, such that the coverage area of ​​a single base station covers an approximately elliptical or circular area. Furthermore, each cell can correspond to a single carrier, and a base station can use multiple carriers. Therefore, if each carrier has three 120-degree cells and two carriers, the base station has a total of six cells.

[0075] Wireless network 100 may include one or more network elements 190, which may include core network functions and provide connectivity to another network, such as a telephone network and / or a data communication network (e.g., the Internet), via one or more links 181. Such core network functions for 5G may include location management functions (LMF) and / or access and mobility management functions (AMF) and / or user plane functions (UPF) and / or session management functions (SMF). Such core network functions for LTE may include MME (Mobility Management Entity) / SGW (Serving Gateway) functions. These are merely example functions that can be supported by network elements 190, and note that both 5G and LTE functions can be supported. RAN node 170 is coupled to network element 190 via link 131. Link 131 may be implemented as, for example, an NG interface for 5G, or an S1 interface for LTE, or other suitable interfaces for other standards. Network element 190 includes one or more processors 175 / one or more memories 171 interconnected via one or more buses 185, and one or more network interfaces (N / WI / F) 180. The one or more memories 171 include computer program code 173. The one or more memories 171 and computer program code 173 are configured, together with the one or more processors 175, to cause network element 190 to perform one or more operations, such as the functionality of the LMF described herein. In some examples, a single LMF can serve a large area covered by hundreds of base stations.

[0076] Wireless network 100 can implement network virtualization, which is the process of combining hardware and software network resources and functions into a single software-based managed entity (virtual network). Network virtualization involves platform virtualization, often combined with resource virtualization. Network virtualization is categorized as external, combining many networks or parts of networks into virtual units, or internal, providing network-like functionality to software containers on a single system. Note that the virtualized entities created by network virtualization are still implemented at some level using hardware such as processors 152 or 175 and memories 155 and 171, and these virtualized entities also produce technical effects.

[0077] Computer-readable storage devices 125, 155, and 171 can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic storage devices and systems, optical storage devices and systems, fixed storage, and removable storage. Computer-readable storage devices 125, 155, and 171 can be components for performing storage functions. As a non-limiting example, processors 120, 152, and 175 can be of any type suitable for the local technical environment and can include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Processors 120, 152, and 175 can be components for performing functions such as controlling UE 110, RAN node 170, network element 190, and other functions described herein.

[0078] Typically, various embodiments of user equipment 110 may include, but are not limited to, cellular phones (e.g., smartphones), tablet computers, personal digital assistants (PDAs) with wireless communication capabilities, portable computers with wireless communication capabilities, image capture devices such as digital cameras with wireless communication capabilities, gaming devices with wireless communication capabilities, music storage and playback devices with wireless communication capabilities, network devices that allow wireless network access and browsing, tablet computers with wireless communication capabilities, and portable units or terminals that combine these functions.

[0079] Modules 150-1 and / or 150-2 can implement the functions and signaling of the gNB or radio node described herein. Computer program code 173 can implement the functions and signaling of the AMF or network unit described herein.

[0080] Figure 2 The illustration shows a portion of a wireless network 100 having several base stations 170 and an exemplary user equipment 110. Figure 2 In this context, it is assumed that when the user equipment (UE) is in a connected state, the base station labeled S-BS is the serving base station, and when the UE is not in a connected state, it is the base station where the UE camps. Some neighboring base stations... Figure 2 The N-BS is marked as such. In practice, such as when a user equipment moves, or if the signal strength from different base stations changes (e.g., the signal from a neighboring N-BS becomes stronger than the signal from the currently serving base station), the serving base station and the base station where the user is based may change.

[0081] When User Equipment 110 is in an inactive state (RRC_INACTIVE), data transmission from User Equipment 110 to the cell is typically blocked. Therefore, User Equipment 110 should restore the connection, i.e., change its state to a connected state (RRC_CONNECTED) to be able to receive data from the network (Mobile-Terminated MT, Downlink DL) and send data to the network (Mobile-Initiated MO, Uplink UL). Thus, connection establishment and subsequent release to an inactive state typically occur with each data transmission, regardless of how small or infrequent the data packets are. This results in unnecessary power consumption and signaling overhead.

[0082] The term "signaling radio bearer" (SRB) is defined for NR as a radio bearer (RB) that can be used to transmit certain types of messages, such as RRC or NAS (non-access stratum) messages. The following signaling radio bearers are defined as an example:

[0083] - SRB0 is used for RRC messages that use the common control channel (CCCH logical channel);

[0084] - SRB1 is used for RRC messages, which may include piggybacked NAS messages, as well as NAS messages before SRB2 is established, all using a dedicated control channel (DCCH logical channel);

[0085] - SRB2 is used for NAS messages and uses the DCCH logical channel exclusively. SRB2 has a lower priority than SRB1 and can be configured by the network after AS security activation;

[0086] -SRB3 is a specific RRC message used when the UE is in NG-RANE-UTRA-NR dual connectivity ((NG)EN-DC) or NR-NR dual connectivity (NR-DC), and all use the DCC logical channel.

[0087] In the following description, some embodiments are provided in which relatively short (small) messages can be transmitted even when the user equipment 110 is in an inactive state and no connection is established, i.e., the user equipment remains in an inactive state. This transmission is also referred to in this specification as inactive state message transmission.

[0088] According to some embodiments, the network determines whether to allow the transmission of small data from the user equipment during inactivity, and if so, what type of message is allowed. Furthermore, the network can also determine, for example, the maximum length for small data messages. These decisions can be made by the network operator who inputs parameters related to small data transmission into the wireless communication network, or they can be determined by the manufacturer of the wireless communication network components and / or by some other entity.

[0089] In other words, the network controls which RRC messages are allowed to use the Small Data Transfer Mechanism / Procedure (SDT). The network indicates which RRC messages are allowed to use SDT, including whether the RRC message is sent using a dedicated RRC container or using an existing message. This may also include the use of signaling radio bearers that differ from the usual practice. For example, signaling radio bearer 2 (SRB2) may be used for messages, or data may be included in a container whose type is indicated by the message.

[0090] On the other hand, if small data transmission from user equipment is not permitted during inactivity, the network may or may not provide any indication that small data transmission from user equipment is not permitted during inactivity.

[0091] According to an embodiment, a separate signaling radio bearer may be introduced, wherein when the user equipment is in an inactive state RRC_INACTIVE, the signaling radio bearer will be allowed to use small data transmission, and only a set of known messages (i.e., a configured set) will be allowed on the signaling radio bearer.

[0092] The configuration for which RRC information to send can be given in a dedicated manner or via broadcast information (i.e., in the System Information Block (SIB)). Both methods can also be used, where the broadcast information can supersede the dedicated configuration after a known time or whenever the UE changes serving cell. Alternatively, the network can allow any UE-initiated signaling (i.e., no mobile-initiated data) to use an SDT with a single flag.

[0093] According to embodiments, the network can configure the UE using the RRC procedures executed by the UE in the RRC_INACTIVE state. In some examples, this allows the transmission of any RRC message triggered by the UE based on an RRC procedure on the SDT. In some examples, the NW can also indicate which RRC procedures are allowed to use the SDT. As an example, the NW can configure the UE to provide assistance information when the UE is in the inactive state RRC_INACTIVE, and in some examples, the UE assistance information can use the SDT procedure.

[0094] According to embodiments, the network can configure the UE to allow at least one SRB to use SDT. In some examples, this can be an SRB-specific configuration or a simple configuration allowing SDT for all SRBs. In some examples, any RRC message sent via at least one SRB can be allowed to use the SDT procedure. In some examples, RRC and NAS messages can be allowed separately, and the UE can be allowed to send only RRC or NAS messages or both on SDT. In some examples, NAS messages are embedded in RRC messages. In some examples, the NW can configure permission for the UE using dedicated RRC signaling or by means of system information broadcasting. In some examples, the UE determines permission in a predefined manner (e.g., written into technical specifications), and in this case, the NW may not configure permission for the UE.

[0095] The following text provides some examples of messages that can be sent using small data transfer mechanisms:

[0096] UE Assistance Information allows user equipment to notify the network of UE delay budget reports, overheating assistance information, Multicast Broadcast Message Service (MBMS) interests, or RRC state preference information (such as IDLE or CONNECTED).

[0097] SidelinkUEInformationNR (e.g., related to the V2X (vehicle to anything) frequency of interest)

[0098] UL Information Transfer

[0099] RRC connection recovery process for RAN area update

[0100] Any control messages related to MBMS counting or MBMS error correction processes

[0101] Recorded measurement reports

[0102] Measurement Report.

[0103] Additional criteria for recording measurement reports can be configured to specify when recorded measurements can be reported via SDT, such as timers or report quantity thresholds, both of which can depend on the measurement target, i.e., whether WLAN, BT, NR, etc., are being measured. This can be used for both MDT and IDLE mode measurement purposes.

[0104] Regarding measurement reports, the network can establish an RRC connection immediately after SDT transmission, and the measurement report can include information about serving and neighboring cell measurements. The measurement report may also include, for example, EMR (Early Measurement Report) measurement results.

[0105] It should be noted that a network may allow all possible message reasons or only a subset thereof. Furthermore, the permitted message reasons may differ at different times, in different situations, in different areas of the network, and / or for different user devices.

[0106] A size threshold can also be configured so that SDT used for control plane signaling is only applied to RRC messages that are less than or equal to that threshold. Additional indications can also convey whether RRC segmentation is allowed to indicate multiple uses of RRC messages with SDT procedures.

[0107] In one example, the network can configure a size threshold for each SRB.

[0108] In one example, the allowed SRBs for SDT can be configured by the network. If no allowed SRBs(s) are configured, the UE is not allowed to use SDT for RRC messages.

[0109] According to an embodiment, the size threshold parameter is valid for data transmission to the network other than RRC messages (uplink data, "UL data") and (multiple) RRC messages. In this option, it is possible to define (or configure) whether uplink data or RRC data has a higher priority, i.e., which one is sent first in case both cannot be sent simultaneously. For example, this may occur if the combined size of uplink data and (multiple) RRC messages exceeds the size threshold.

[0110] According to another embodiment, separate size threshold parameters are defined for uplink data and (multiple) RRC messages.

[0111] According to an embodiment, a size threshold parameter and a list of messages that can be sent are combined, wherein both conditions must be met before the small data transfer mechanism is allowed. In other words, a message can only be sent if it is allowed and only if the message is less than (or equal to) the threshold.

[0112] If more than one pending message satisfies this criterion, a priority criterion can be introduced, where only the highest priority message is sent. If a size threshold is also configured, only the highest priority message that is less than (or equal to) the threshold when combined is sent.

[0113] Priorities can be configured along with the list of allowed messages. If only one message is configured, the priority configuration can be optional.

[0114] According to an embodiment, RAN node 170 forms a configuration message in which parameters related to small message transmission are sent to one or more user equipments. For example, the configuration message could be an RRCRelease message, which RAN node 170 can use to push a user equipment into an inactive state. Such a message can be considered a message dedicated to a specific receiver. As another example, the configuration message could be a broadcast message, such as a cell selection information message, which does not have a dedicated receiver and can be received and interpreted by all user equipments within the service area of ​​RAN node 170. Other messages can also be used to send parameters to user equipment.

[0115] The example structure of the RRCRelease message is shown below, but parts unnecessary for understanding the concept of transmitting these specific parameters are omitted:

[0116]

[0117]

[0118] In this example, the underlined portion at the end describes the parameters related to enabling small data transmission in an inactive state. The meaning of the signaling example definition is described below.

[0119] SDT-RRC-Config-r17 defines a signaling element that includes a sequence of parameters. The first element in this signaling element is a list of allowed causes (SDT-RRC-CauseList-r17) for small data that can be transmitted in an inactive state. This list includes zero or one cause (SDT-Cause). Causes can be indicated by predefined values, each defining a cause for the small data.

[0120] maxSDT-RRC-Causes-r17 indicates the maximum allowed number of SDT-Causes in the list.

[0121] The parameter sizeThreshold-r17 can be used to indicate the maximum size of small data that is allowed to be transmitted using this mechanism. According to one embodiment, the maximum size is an integer between 1 and 256 (inclusive). According to another embodiment, the maximum size is indicated as an integer between 0 and 255 (inclusive), where the actual maximum size is 1 greater than the indication, i.e., sizeThreshold-r17+1.

[0122] A parameter `allowRRC-Segmentation` may also be present, indicating whether it is permissible to segment a message into multiple smaller messages, which can then be sent as multiple small data packets. If the `allowRRC-Segmentation` parameter is present, it can have a true or false value. True indicates that segmentation is allowed, while false indicates that segmentation is not allowed. According to another embodiment, the `allowRRC-Segmentation` parameter only appears when segmenting the message into multiple smaller messages is permitted.

[0123] It should be noted that the expressions Need R (Release) and Need N (No action) in the above examples indicate that if the specific field does not exist, the previous value of the parameter should be released (Need R) or it is a one-time parameter (Need N), where the user device does not take any action regarding the parameter when the field does not exist.

[0124] Below is another example of a configuration message. In this example, the configuration is sent as broadcast signaling in SIB1 using the structure described above:

[0125]

[0126]

[0127]

[0128] According to an embodiment, small data transmission is performed using a so-called two-step RACH transmission, namely, a (first) message (MSGA) from the user equipment to the network and a second (acknowledgment) message (MSGB) from the network to the user equipment. In this case, small data, such as..., is inserted into the first message from the user equipment to the network. Figure 3a As shown in the signaling diagram.

[0129] According to another embodiment, small data transmission is performed using a so-called 4-step RACH transmission, namely two messages (first and third) (MSG1, MSG3) from the user equipment to the network, and two messages (second and fourth) (MSG2, MSG4) from the network to the user equipment. In this case, small data is inserted into the third message, such as... Figure 3b As shown in the signaling diagram.

[0130] According to another embodiment, small data transmission is performed using a secondary cell group (SCG) via a configuration permission. In this case, the small data is sent in a configuration permission message.

[0131] RRC messages can also be restricted to using a specific small data transmission mechanism, which can be a configured RRC message or an SRB.

[0132] According to an embodiment, when used for small data transmission, the user equipment can always apply the default configuration specified for the SRB.

[0133] The following describes an example of a signaling mechanism for sending a single RRC message via a small data transmission mechanism. Sending multiple RRC messages is a direct extension of this. In this example, SRB0 is used, but another SRB could also be used.

[0134] The following RRCSmallDataRequest message can be used to send data to the network using the SDT procedure.

[0135]

[0136] In this example, the request includes the user equipment's identity, SDT-UE-identity, and the payload field includes the reason for the small data (one of mo-data, NAS-transfer, rnau, and measReport) and an indication of the actual small data in the data field.

[0137] When the network receives a request, it can obtain (among other things) small amounts of data from the message and, for example, store it in memory and / or perform certain tasks related to the data.

[0138] Figure 4 This is a flowchart illustrating some actions of a user equipment when the user equipment intends to send a small amount of data, according to an embodiment.

[0139] User equipment 110 receives an indication of the reason for allowing transmission using the small data transmission mechanism. Figure 4 (See box 400 in the image). This instruction can be sent to user equipment 110 by a network element (e.g., RAN node 170) as a broadcast message or in a private message. Such an instruction can be sent before user equipment 110 has a small message to be transmitted, whereby the user equipment has already stored the corresponding information in its memory for later use.

[0140] When, for example, a message 119 to be transmitted exists in memory 125, it can be transmitted by the message writer 112 of the user equipment. Figure 6An RRC message is formed (box 402). The cause comparator 113 checks the cause of the message and compares it with allowed causes (box 404). If the cause is among the allowed causes, the length comparator 114 compares the message length with the maximum length parameter SDT_limit (box 406), and if the length is less than or equal to the maximum length, a small data transfer procedure (408) is triggered, where certain signaling is performed between the user equipment and the network. Flags or other indicators can be set to indicate that the small data transfer procedure can be used for message transmission. The message is provided to the sender 133 for transmission (box 410). The sender 133 checks the value of the flags and determines that transmission can be performed without changing the state from inactive to connected. Therefore, the sender 133 and the network exchange appropriate signals to deliver the small message to the network (box 410). The details of the signaling depend on, for example, the cause of the message exchange procedure selected for the small data transfer. For example, the 2-step or 4-step RACH transmission mechanism described above can be used.

[0141] However, if the cause is not among the allowed causes, or the message length exceeds the maximum length, a normal RRC recovery procedure can be triggered (box 412), where a flag or other indicator is set to indicate that the normal message transmission procedure should be used. The transmitter 133 checks the value of the flag and determines that the state should change from inactive to connected during message transmission. Therefore, the user equipment's state changes from inactive to connected (RRC_Connected), and the transmitter 133 and the network exchange appropriate signals to deliver the message to the network (box 410).

[0142] According to an embodiment, user equipment 110 may have a priority checker 116 that can check the possible priority indicators of messages when there are more than one message to be sent using the small data transmission mechanism. The priority checker 116 can then arrange the messages to be transmitted in the order indicated by the priority, wherein the messages are provided to the sender 133 in this order.

[0143] According to an embodiment, user equipment 110 may have a message segmenter 117 that can divide messages longer than the maximum length into segments with lengths less than or equal to the maximum length. In this case, message segments can be provided to transmitter 133 one after another, so that transmitter 133 sends each segment using a small data transmission mechanism.

[0144] According to an embodiment, user equipment 110 may have a message combiner 118 that can combine two or more messages shorter than the maximum length into a single message, such that the length of the combined message is shorter than or equal to the maximum length. Therefore, a small data transmission mechanism can be used to send the combined message.

[0145] According to an embodiment, if the message length is shorter than or equal to the maximum length, a small data transfer mechanism is allowed for each cause of the message. Therefore, the cause comparator 113 does not need to check the cause of the message, but the length comparator 114 compares the message length with the maximum length parameter SDT_limit, and if the length is less than or equal to the maximum length, the small data transfer process can be triggered.

[0146] Figure 5 The diagram illustrates a flowchart of actions that, according to an embodiment, can be performed by a network element (e.g., RAT 170) to indicate the reasons for data transmission permitted by a user equipment using the small data transmission mechanism. The network element determines (box 500) which types of data will be permitted to be transmitted via the small data transmission mechanism and forms a list, or some other information element, including those message reasons (box 502). An example of such a list is the allowedSDT-RRC-CauseList-r17 SEQUENCE(1..maxSDT-RRC-Causes-r17) OF SDT-Cause, previously presented in this specification. The network element can form a broadcast message (box 504) including details of the permitted reasons and some other information, such as the information described above in the example for signaling configuration of SIB1. This message can then be sent (box 506).

[0147] In 5G, the first frequency range FR1 is 450MHz-6000MHz, and the second frequency range FR2 is 24250MHz-52600MHz. However, in some other wireless communication systems, these frequency ranges may be different from those used in 5G, and it is also possible to use only one frequency range or more than two separate frequency ranges.

[0148] In the following description, radio access architectures based on Long Term Evolution Advanced (LTE-A) or New Radio (NR, 5G) will be used as examples of access architectures to which the embodiments can be applied to describe different exemplary embodiments. However, the embodiments are not limited to such architectures. It will be apparent to those skilled in the art that these embodiments can also be applied to other types of communication networks with suitable components by appropriately adjusting parameters and processes. Some examples of other options for suitable systems are Universal Mobile Telecommunications (UMTS) Radio Access Network (UTRAN or E-UTRAN), Long Term Evolution (LTE, essentially the same as E-UTRA), Wireless Local Area Network (WLAN or WiFi), and Global Microwave Access Interoperability (WiMax). Personal Communication Services (PCS) Wideband Code Division Multiple Access (WCDMA), systems using Ultra Wideband (UWB) technology, sensor networks, Mobile Ad Hoc Networks (MANET), and Internet Protocol Multimedia Subsystem (IMS), or any combination thereof.

[0149] Figure 7 An example of a simplified system architecture is shown, depicting only some components and functional entities, which are logical units whose implementations may differ from those shown. Figure 7 The connections shown are logical connections; the actual physical connections may differ. It will be apparent to those skilled in the art that the system typically includes, in addition to... Figure 7 Other functions and structures besides those shown.

[0150] However, the embodiments are not limited to the system given as an example, but those skilled in the art can apply this solution to other communication systems with the necessary characteristics.

[0151] Figure 7 The example illustrates a portion of an exemplary radio access network.

[0152] Figure 7 The illustration shows user equipment 110a and 110b configured to wirelessly connect to an access node (e.g., an (e / g)NodeB) 104 providing the cell on one or more communication channels within the cell. The physical link from the user equipment to the (e / g)NodeB is referred to as an uplink or reverse link, while the physical link from the (e / g)NodeB to the user equipment is referred to as a downlink or forward link. It should be understood that the (e / g)NodeB or its functionality can be implemented using any entity suitable for such use, such as a node, host, server, or access point.

[0153] A communication system typically includes more than one (e / g)NodeB. In this case, (e / g)NodeBs can also be configured to communicate with each other via wired or wireless links designed for this purpose. These links can be used for signaling purposes. The (e / g)NodeB is a computing device configured to control the radio resources of the communication system to which it is coupled. A NodeB can also be referred to as a base station, access point, access node, or any other type of interface device, including relay stations capable of operating in a wireless environment. The (e / g)NodeB includes or is coupled to a transceiver. From the transceiver of the (e / g)NodeB, a connection is provided to an antenna element that establishes a bidirectional radio link to the user equipment. The antenna element may include multiple antennas or antenna elements. The (e / g)NodeB is also connected to the core network 109 (CN or Next Generation Core NGC). Depending on the system, the counterpart on the CN side may be a Serving Gateway (S-GW, which routes and forwards user data packets), a Packet Data Network Gateway (P-GW) for providing connectivity of user equipment (UE) to external packet data networks, or a Mobility Management Entity (MME), etc. A network entity (CN) can include network entities or nodes that may be referred to as management entities. Examples of network entities include at least an Access Management Function (AMF).

[0154] User equipment (also known as user equipment, user terminal, terminal equipment, wireless equipment, mobile station (MS), etc.) illustrates a type of device to which resources on the air interface are allocated and assigned, and therefore any features described herein using user equipment can be implemented using corresponding network devices such as relay nodes, eNBs, and gNBs. An example of such a relay node is a Layer 3 relay (self-backhaul relay) toward a base station.

[0155] User equipment (UE) generally refers to a portable computing device that includes wireless mobile communication devices, with or without a Subscriber Identity Module (SIM), including but not limited to the following types of devices: mobile station (mobile phone), smartphone, personal digital assistant (PDA), handset, device using a wireless modem (alarm or measuring device, etc.), portable computer and / or touchscreen computer, tablet, game console, laptop, and multimedia device. It should be understood that UE can also be an exclusive or nearly exclusive uplink-only device, an example of which is a camera or camcorder that loads images or video clips onto a network. UE can also be a device capable of operating in an Internet of Things (IoT) network, in which objects are provided with the ability to transmit data over the network without human-to-human or human-to-computer interaction. UE can also utilize the cloud. In some applications, UE may include a small portable device with radio components (such as a watch, headset, or glasses), and computation is performed in the cloud. UE (or in some embodiments, a Layer 3 relay node) is configured to perform one or more of the UE functions. UE may also be referred to as a user unit, mobile station, remote terminal, access terminal, user terminal, or user equipment (UE), with only a few names or devices mentioned.

[0156] The various techniques described in this paper can also be applied to cyber-physical systems (CPS) (systems that collaboratively control computing elements of physical entities). CPS can realize and utilize a large number of interconnected ICT devices (sensors, actuators, processors, microcontrollers, etc.) embedded in different locations within physical objects. Mobile cyber-physical systems, in which the physical systems discussed have inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robots and electronic devices transported by humans or animals.

[0157] Furthermore, although the device is described as a single entity, different units, such as processors and / or memory units, can be implemented. Figure 7 (Not all of them are shown in the image).

[0158] 5G supports the use of multiple-input multiple-output (MIMO) antennas, far more base stations or nodes than LTE (the so-called small cell concept), including macro sites that cooperate with smaller base stations and employ multiple radio technologies, depending on service requirements, use cases, and / or available spectrum. 5G mobile communications support a wide range of use cases and related applications, including video streaming, augmented reality, different data sharing methods, and various forms of machine-type applications (such as massive machine-type communications (mMTC), including vehicle safety, different sensors, and real-time control). 5G is expected to have multiple radio interfaces: sub-6 GHz, centimeter wave (cmWave), and millimeter wave (mmWave), and can be integrated with existing conventional radio access technologies such as LTE. Integration with LTE can be achieved, at least in the early stages, as a system where macro coverage is provided by LTE and 5G radio interface access originates from small cells via aggregation to LTE. In other words, 5G is planned to simultaneously support inter-RAT interoperability (such as LTE-5G) and inter-RI interoperability (inter-radio interface interoperability, such as sub-6 GHz-cmWave and sub-6 GHz-cmWave-mmWave). One concept considered for use in 5G networks is network slicing, where multiple independent and dedicated virtual subnets (network instances) can be created within the same infrastructure to run services with different requirements for latency, reliability, throughput, and mobility.

[0159] The current architecture in LTE networks is entirely distributed across the radio and entirely centralized in the core network. Low-latency applications and services in 5G may require bringing content closer to the radio, potentially leading to localized bursts and multiple access edge computing (MEC). 5G enables analytics and knowledge generation to occur at the data source. This approach requires leveraging resources that may not be continuously connected to the network, such as laptops, smartphones, tablets, and sensors. MEC provides a distributed computing environment for hosting applications and services. It also has the ability to store and process content near cellular subscribers to accelerate response times. Edge computing encompasses a wide range of technologies, such as wireless sensor networks, mobile data acquisition, mobile signature analytics, collaborative distributed peer-to-peer self-organizing networks and processing (which can also be categorized as local cloud / fog computing and grid / mesh computing), dew computing, mobile edge computing, cloudlets, distributed data storage and retrieval, autonomous self-healing networks, remote cloud services, augmented and virtual reality, data caching, the Internet of Things (IoT) (massive connectivity and / or latency critical), and critical communications (autonomous vehicles, traffic safety, real-time analytics, time-critical control, healthcare applications).

[0160] The communication system is also capable of communicating with other networks, such as the public switched telephone network or the Internet, and / or utilizing the services provided by them. The communication network may also be able to support the use of cloud services; for example, at least a portion of the core network operation can function as a cloud service (this is in...). Figure 7 The communication system may also include a central control entity that provides facilities for different operators' networks to collaborate, for example, in spectrum sharing. (Described by "cloud" 102)

[0161] Edge cloud can be introduced into the radio access network (RAN) by leveraging Network Functions Virtualization (NFV) and Software-Defined Networking (SDN). Using edge cloud means that access node operations are performed at least partially within a server, host, or node, coupled to a remote radio head or base station, including the radio portion. Node operations can also be distributed across multiple servers, nodes, or hosts. The application of the cloudRAN architecture enables real-time RAN functions to be executed on the RAN side (in the distributed unit DU 104), while non-real-time functions can be executed centrally (in the centralized unit CU108).

[0162] It should also be understood that the workload allocation between core network operations and base station operations may differ from, or even not exist at all, in LTE. Other technologies that can be used include, for example, big data and all-IP, which could change how networks are built and managed. 5G (or New Radio, NR) networks are designed to support multiple hierarchical structures, where MEC servers can be placed between the core and base stations or nodeBs (gNBs). It should be understood that MEC can also be applied to 4G networks. A gNB is a next-generation nodeB (or new nodeB) that supports 5G networks (i.e., NR).

[0163] 5G can also leverage satellite communications to enhance or supplement the coverage of 5G services, for example, by providing backhaul. Possible use cases include providing service continuity for machine-to-machine (M2M) or Internet of Things (IoT) devices or for passengers on board vehicles, or ensuring the availability of critical communications and future rail / maritime / aviation communications. Satellite communications can utilize geostationary Earth orbit (GEO) satellite systems or low Earth orbit (LEO) satellite systems, particularly mega-constellations (systems deploying hundreds of (nano) satellites). Each satellite 106 in a mega-constellation can cover several satellite-enabled network entities that create a ground cell. Ground cells can be created via ground relay nodes 104 or gNBs located on the ground or in satellites.

[0164] It will be apparent to those skilled in the art that the described system is merely an example of a portion of a radio access system, and in practice, the system may include multiple (e / g)NodeBs, user equipment may access multiple radio cells, and the system may also include other devices, such as physical layer relay nodes or other network elements. At least one of the (e / g)NodeBs may be a home (e / g)NodeB. Furthermore, multiple different types of radio cells and multiple radio cells may be provided within the geographical area of ​​the radio communication system. Radio cells may be macrocells (or umbrella cells), which are large cells typically tens of kilometers in diameter, or smaller cells such as micro, femtocells, or picocells. Figure 7 An (e / g)NodeB can provide any type of these cells. Typically, in a multi-layer network, one access node provides one or more cells, thus requiring multiple (e / g)NodeBs to provide this network structure.

[0165] To meet the needs of improving the deployment and performance of communication systems, the concept of "plug and play" (e / g) NodeB was introduced. Typically, networks capable of using "plug and play" (e / g) NodeBs include not only home (e / g) NodeBs (H(e / g) nodeBs), but also home node B gateways or HNB-GWs ( Figure 7 (Not shown in the image). HNB gateways (HNB-GWs), typically installed within a carrier's network, can aggregate services from a large number of HNBs back to the core network.

[0166] Figure 9 illustrates an example block diagram of an apparatus 110 according to at least some embodiments of the present invention. Apparatus 110 may, for example, be part of a resource manager. Apparatus 110 includes a processor 1022, a memory 1024, and a transceiver 1024. The processor is operatively connected to the transceiver for controlling the transceiver. The apparatus may include a memory 1026. The memory is operatively connected to the processor. It should be understood that the memory may be a separate memory or included in the processor and / or transceiver. Memory 1026 may be used to store information such as maximum length, allowed reasons, default values ​​for certain parameters, and / or certain other information.

[0167] Figure 9 also illustrates operational units as computer code stored in memory, but they can also be implemented using hardware components or as a mixture of computer code and hardware components.

[0168] According to an embodiment, the processor is configured to control the transceiver and / or perform one or more functions utilizing the method described in the embodiment.

[0169] The memory can be a non-transitory computer-readable medium. The memory can be of any type suitable for the local technology environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. As a non-limiting example, the data processor can be of any type suitable for the local technology network and can include one or more of general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), and processors based on multi-core processor architectures.

[0170] Implementations may be carried out using software, hardware, application logic, or a combination of software, hardware, and application logic. The software, application logic, and / or hardware may reside in memory or any computer medium. In example embodiments, the application logic, software, or instruction set is maintained on any of a variety of conventional computer-readable media. In the context of this document, "memory" or "computer-readable medium" can be any medium or component capable of containing, storing, transmitting, propagating, or transmitting instructions used by or in connection with an instruction execution system, apparatus, or device (e.g., a computer).

[0171] Where applicable, references to “computer-readable storage medium,” “computer program product,” “tangibly embodied computer program,” or “processor” or “processing circuit system” should be understood to include not only computers with different architectures (e.g., single / multiprocessor architectures and sequencer / parallel architectures) but also special-purpose circuits (e.g., field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), signal processing devices, and other devices). References to computer-readable program code components, computer programs, computer instructions, computer code, etc., should be understood to express software for programmable processor firmware (e.g., programmable content of hardware devices) as instructions for a processor or as configurations or configuration settings for fixed-function devices, gate arrays, programmable logic devices, etc.

[0172] While the examples described above illustrate embodiments of the invention operating in a wireless device or gNB, it should be understood that the invention described above can be implemented as part of any apparatus including a circuit system in which radio frequency signals are transmitted and / or received. Therefore, for example, embodiments of the invention can be implemented in mobile phones, base stations, or computers such as desktop or tablet computers that include radio frequency communication components (e.g., wireless LAN, cellular radio, etc.).

[0173] Generally, various embodiments of the present invention can be implemented in hardware or dedicated circuitry or any combination thereof. While various aspects of the invention may be shown and described as block diagrams or using some other graphical representation, it is well understood that the blocks, apparatuses, systems, techniques or methods described herein can be implemented as non-limiting examples in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices or some combination thereof.

[0174] Embodiments of the present invention can be practiced in a variety of components, such as integrated circuit modules, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), microcontrollers, microprocessors, and combinations of such modules. The design of integrated circuits is largely a highly automated process. Complex and powerful software tools can be used to transform logic-level designs into semiconductor circuit designs ready for etching and formation on semiconductor substrates.

[0175] Programs such as those offered by Synopsys in Mountain View, California, and CadenceDesign in San Jose, California, automatically route conductors and position components on semiconductor chips using well-established design rules and pre-stored libraries of design modules. Once the semiconductor circuit design is complete, the resulting design in a standardized electronic format (such as Opus, GDSII, etc.) can be transferred to a semiconductor manufacturing facility or "fab" for fabrication.

[0176] As used in this application, the term "circuit system" may refer to one or more or all of the following:

[0177] (a) Pure hardware circuit implementation (such as implementation using only analog and / or digital circuit systems), and

[0178] (b) A combination of hardware circuitry and software, such as (if applicable):

[0179] (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and

[0180] (ii) Any part of a hardware processor(s) having software, including (multiple) digital signal processors, software, and (multiple) memories, which work together to cause a device (such as a mobile phone or server) to perform various functions, and

[0181] (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (e.g., firmware) to operate, but may be absent when operation is not required.

[0182] This definition of "circuit" applies to all uses of the term in this application, including in any claim. As another example, as used in this application, the term "circuit system" will also cover an implementation of only one processor (or multiple processors) or a portion of a processor and its accompanying software and / or firmware. The term "circuit" also covers (e.g., and if applicable to elements of a particular claim) baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.

[0183] The foregoing description has provided a complete and informative description of exemplary embodiments of the invention through exemplary and non-limiting examples. However, various modifications and adaptations will become apparent to those skilled in the art when read in conjunction with the accompanying drawings and appended claims, given the foregoing description. Nevertheless, all such modifications and similar alterations taught in this invention will still fall within the scope of this invention.

Claims

1. A user equipment comprising components for: Determine whether the transmission of signaling messages using the small data transmission procedure is permitted during the inactive state of the user equipment; and Based on the determination, the user equipment performs the following: The signaling message is sent using the small data transmission procedure during the inactive state; or The signaling message is sent using a procedure other than the small data transmission procedure described above; The user equipment further includes components for the following: Obtain from the wireless communication network an indication of the availability and transmission order of each of more than one signaling radio bearers, which will be used in the transmission of the message utilizing the small data transmission process; and Based on the instructions, the transmission order between uplink data and radio resource control data is selected according to the priorities defined for uplink data and radio resource control data.

2. The user equipment according to claim 1, further comprising components for: Obtain one or more messages for transmission to a wireless communication network, wherein the one or more messages have a reason for the message; The reason is used in the determination, wherein if the reason belongs to the set of reasons that allow the use of the small data transmission procedure in the inactive state, the message is included in the signaling message to be sent.

3. The user equipment according to claim 1 or 2, wherein the user equipment includes a message segmenter for dividing the signaling message longer than a maximum length into segments having a length less than or equal to the maximum length.

4. The user equipment according to claim 1 or 2, further comprising components for: Obtain an indication of the type of the container in which the message is included for transmission.

5. The user equipment of claim 1, wherein the signaling element further comprises at least one of the following conditions satisfied by the message, the message being used for transmissions performed by the small data transmission process in the inactive state: The maximum length of the message; The priority of the message; Enable or disable segmenting the message into smaller pieces.

6. The user equipment according to claim 1, further comprising components for: Information about one or more reasons for obtaining a message from the wireless communication network in the signaling element that causes the user equipment to change to the inactive state.

7. The user equipment according to claim 1, further comprising components for: Check the flag, which indicates whether any signaling initiated by a user equipment is allowed to use the small data transmission procedure.

8. The user equipment according to claim 1, comprising components for: The message is transmitted as a radio resource control message using the signaling radio bearer instructed to be used in the transmission of the message; and The reason for the message is included in the radio resource control message.

9. A method for communication, comprising: Determine whether the transmission of signaling messages using the small data transmission procedure is permitted while the user equipment is inactive; as well as Based on the determination, the user equipment performs the following: The signaling message is sent using the small data transmission procedure during the inactive state. or The signaling message is sent using a procedure other than the small data transmission procedure described above; The method further includes: Obtain an indication from the wireless communication network regarding the availability and transmission order of each of more than one signaling radio bearers, which will be used in the transmission of the message utilizing the small data transmission process; as well as Based on the instructions, the transmission order between uplink data and radio resource control data is selected according to the priorities defined for uplink data and radio resource control data.

10. The method of claim 9, further comprising: Obtain one or more messages for transmission to a wireless communication network, wherein the one or more messages have a reason for the message; The reason is used in the determination, wherein if the reason belongs to the set of reasons that allow the use of the small data transmission procedure in the inactive state, the message is included in the signaling message to be sent.

11. The method according to claim 9 or 10, further comprising: Information is obtained from the wireless communication network for one or more reasons for the message being allowed to be transmitted by the user equipment to the wireless communication network during the user equipment's inactive state.

12. The method of claim 9 or 10, wherein the user equipment includes a message segmenter for dividing the signaling message longer than a maximum length into segments having a length less than or equal to the maximum length.

13. The method of claim 9, further comprising: Obtain an indication of the type of the container in which the message is included for transmission.

14. The method of claim 9, wherein at least one condition is one or more of the following: The maximum length of the message; The priority of the message; Enable or disable segmenting the message into smaller pieces.

15. The method of claim 9, further comprising: The message that causes the user equipment to change to the inactive state includes information about one or more reasons for the message obtained from the wireless communication network.

16. The method of claim 9, further comprising: Check the flag, which indicates whether any signaling initiated by a user equipment is allowed to use the small data transmission procedure.

17. The method of claim 9, comprising: The message is transmitted as a radio resource control message using the signaling radio bearer instructed to be used in the transmission of the message; as well as The reason for the message is included in the radio resource control message.

18. The method of claim 9, comprising: Receive a release message from the wireless communication network, the release message being used to change the state of the user equipment from a state different from the inactive state to the inactive state; as well as The release message provides at least one of the following: information about one or more permitted message reasons, and at least one of the conditions.

19. The method of claim 9, wherein the combined size of the uplink data and the radio resource control data is greater than a maximum length defined for the inactive state.

20. An apparatus for communication, comprising at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code being configured, together with the at least one processor, such that the apparatus performs at least the following: Determine whether to allow the transmission of signaling messages using small data transmission procedures during the inactive state of the user equipment; and Based on the determination, the device performs the following: The signaling message is sent using the small data transmission procedure during the inactive state; or The signaling message is sent using a procedure other than the small data transmission procedure described above; The device is further configured to: Obtain from the wireless communication network an indication of the availability and transmission order of each of more than one signaling radio bearers, which will be used in the transmission of the message utilizing the small data transmission process; and Based on the instructions, the transmission order between uplink data and radio resource control data is selected according to the priorities defined for uplink data and radio resource control data.

21. An apparatus for communication, comprising components for: Determine whether to enable the initiation of signaling message transmission for the small data transmission procedure using the user equipment in the inactive state of the user equipment; as well as Based on the determination, the device provides an indication to one or more user equipments as follows: whether the initiation of the transmission of signaling messages for the small data transmission procedure is enabled by the user equipment in the inactive state of the user equipment; The device further includes components for the following: Indications regarding the availability and transmission order of each of more than one signaling radio bearers will be transmitted from the wireless communication network in the transmission of the message utilizing the small data transmission process; and Based on the indicated sequence of events, the transmission order between the uplink data and the radio resource control data is selected according to the priorities defined for uplink data and radio resource control data.

22. The apparatus of claim 21, comprising components for: At least one of the multiple message reasons is classified as being permitted for transmission by the user equipment using the small data transmission process when the user equipment in the wireless communication network is inactive. Send an indication of the reason for at least one message to one or more user equipment.

23. The apparatus according to claim 21 or 22, comprising components for: For messages that are permitted to be transmitted using the small data transmission process during the inactive state, at least one condition is defined.

24. The apparatus of claim 23, wherein the at least one other condition includes one or more of the following: The maximum length of the message; The priority of the message; Enable or disable segmenting the message into smaller pieces.

25. The apparatus of claim 21, comprising components for: An indication of the type of container to be sent, wherein the message should be included in the container for transmission by the small data transmission process.

26. The apparatus of claim 21, comprising components for: Receive signaling messages sent by the user equipment during the inactive state; Inspect the indication of the reason for the message attached to the signaling message; The indication of the cause of the message is compared with at least one classified message cause, which is permitted for use in transmissions utilizing small data transfer processes during inactivity; and If the message reason is among those allowed for inactive state transmission, then data is obtained from the message.

27. The apparatus of claim 21, comprising components for: Send a release message to the user equipment to change the state of the user equipment from a state different from the inactive state to the inactive state; and The release message shall include at least one of the following: information on one or more permitted message reasons, and at least one of the conditions.

28. The apparatus of claim 21, further comprising a component for notifying one or more of the following: Which radio resource control messages are permitted to use inactive state data transmission; Is a dedicated radio resource control container being used, or is an existing message being used? Whether to allow signaling initiated by any user equipment.

29. The apparatus of claim 21, wherein the message reason permitted for inactive state transmission includes one or more of the following: Auxiliary information regarding the user equipment; Side link information; Uplink information transmission; RRC connection recovery procedure for RAN area update; Control messages related to multicast / broadcast message service counting or multicast / broadcast message service error correction processes; Recorded measurements must be reported. Measurement report.

30. A method for communication, comprising: Determine whether to enable the initiation of signaling message transmission for the small data transmission procedure using the user equipment in the inactive state of the user equipment; as well as Based on the determination, an indication is provided to one or more user equipments as follows: whether the initiation of the transmission of signaling messages for the small data transmission procedure is enabled by the user equipment in the inactive state of the user equipment; The method further includes: Indications regarding the availability and transmission order of each of more than one signaling radio bearers will be transmitted from the wireless communication network in the transmission of the message utilizing the small data transmission process; and Based on the aforementioned instructions, and based on the priorities defined for uplink data and radio resource control data, the transmission order between uplink data and radio resource control data is selected.

31. The method of claim 30, comprising: At least one of the multiple message reasons is classified as being permitted for transmission by the user equipment using the small data transmission process when the user equipment in the wireless communication network is inactive. Send an indication of the reason for at least one message to one or more user equipment.

32. The method according to claim 30 or 31, comprising: For messages that are permitted to be transmitted using the small data transmission process during the inactive state, at least one condition is defined.

33. The method of claim 32, wherein the at least one other condition includes one or more of the following: The maximum length of the message; The priority of the message; Enable or disable segmenting the message into smaller pieces.

34. The method of claim 30, comprising: An indication of the type of container to be sent, wherein the message should be included in the container for transmission by the small data transmission process.

35. The method of claim 30, comprising: Send a release message to the user equipment to change the state of the user equipment from a state different from the inactive state to the inactive state; as well as The release message shall include at least one of the following: information on one or more permitted message reasons, and at least one of the conditions.

36. The method of claim 30, further comprising notifying one or more of the following: Which RRC messages are allowed to use inactive state data transmission; Is a dedicated RRC container being used, or are existing messages being used? Whether to allow signaling initiated by any user equipment.

37. An apparatus for communication, comprising at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code being configured, together with the at least one processor, such that the apparatus performs at least the following: Determine whether to enable the initiation of signaling message transmission for the small data transmission procedure using the user equipment during the user equipment's inactive state; and Based on the determination, the device provides an indication to one or more user equipments as follows: whether the initiation of the transmission of signaling messages for the small data transmission procedure is enabled by the user equipment in the inactive state of the user equipment; The device is further configured to: Indications regarding the availability and transmission order of each of more than one signaling radio bearers will be transmitted from the wireless communication network, said more than one signaling radio bearer being used in the transmission of the message utilizing the small data transmission process; and Based on the aforementioned instructions, and based on the priorities defined for uplink data and radio resource control data, the transmission order between uplink data and radio resource control data is selected.

Images