Reports that a provisioned uplink transmission failed

Abstract

Embodiments of the present disclosure relate to reporting preconfigured uplink transmission failures. According to embodiments of the present disclosure, a terminal device records failures and failure causes associated with transmissions on preconfigured resources. The terminal device transmits this recorded information to a network device. In this way, the network device is informed of the occurrence and cause of the failure. The network device can use this information more efficiently to configure uplink resources, and the resources can be efficiently allocated for other purposes or other terminal devices.

Description

Technical Field

[0001] Embodiments of the present disclosure relate generally to communication technology, and more particularly to methods, devices, and computer-readable media for reporting pre-configured uplink transmission failures. Background Art

[0002] With the development of communication systems, more and more technologies are proposed. Prior to Release 16, terminal devices could not transmit small amounts of / infrequent data to network devices in the Radio Resource Control (RRC) inactive state. It has been agreed to introduce uplink data transmission on pre-configured Physical Uplink Shared Channel (PUSCH) resources (i.e., reuse configured Grant Type 1) in the inactive state. Such resources may be configured for the UE using dedicated or broadcast signaling. In order to transmit small amounts of / infrequent data, the terminal device may need to transition to the RRC Connected state and back to the RRC Inactive state for each transmission. Summary of the Invention

[0003] Generally, embodiments of the present disclosure relate to a method and corresponding apparatus for reporting a pre-configured uplink transmission failure.

[0004] In a first aspect, a method is provided. The method includes receiving, at a first device, first information from a second device indicating a set of resources preconfigured for transmission. The method also includes generating, based on determining that a predetermined number of transmission failures have occurred on the set of resources, second information indicating at least the predetermined number of transmission failures and reasons for the predetermined number of transmission failures. The method also includes transmitting the second information to the second device.

[0005] In a second aspect, a method is provided. The method includes transmitting first information indicating a set of resources preconfigured for transmission to a first device. The method also includes receiving second information from the first device indicating at least a predetermined number of transmission failures detected on the set of resources and reasons for the predetermined number of transmission failures. The method also includes reallocating the set of resources based on the second information.

[0006] In a third aspect, a first device is provided. The first device includes 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 to, with the at least one processor, cause the first device to receive, from a second device, first information indicating a set of resources preconfigured for transmission. The first device is further caused to generate, based on determining that a predetermined number of transmission failures have occurred on the set of resources, second information indicating at least a predetermined number of transmission failures and causes of the predetermined number of transmission failures. The first device is further caused to transmit the second information to the second device.

[0007] In a fourth aspect, a second device is provided. The second device includes 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 to, with the at least one processor, cause the second device to transmit, to a first device, first information indicating a set of resources preconfigured for transmission. The second device is further caused to receive, from the first device, second information indicating at least a predetermined number of transmission failures detected on the set of resources and reasons for the predetermined number of transmission failures. The second device is further caused to reallocate the set of resources based on the second information.

[0008] In a fifth aspect, an apparatus is provided. The apparatus includes means for receiving, at a first device, from a second device, first information indicating a set of resources preconfigured for transmission; means for generating, based on determining that a predetermined number of transmission failures have occurred on the set of resources, second information indicating at least a predetermined number of transmission failures and causes of the predetermined number of transmission failures; and means for transmitting the second information to the second device.

[0009] In a sixth aspect, an apparatus is provided. The apparatus includes means for transmitting first information indicating a set of resources preconfigured for transmission to a first device; means for receiving second information from the first device indicating at least a predetermined number of transmission failures detected on the set of resources and reasons for the predetermined number of transmission failures; and means for reallocating the set of resources based on the second information.

[0010] In a seventh aspect, a computer-readable medium is provided, comprising program instructions for causing an apparatus to at least execute the method according to the first aspect or the second aspect.

[0011] In an eighth aspect, a computer program product is provided, which is stored on a computer-readable medium and includes machine-executable instructions, wherein the machine-executable instructions, when executed, cause the machine to perform the method according to the first aspect or the second aspect above.

[0012] It should be understood that the invention summary is not intended to determine the key or essential features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Some example embodiments will now be described with reference to the accompanying drawings, in which:

[0014] Figure 1 A schematic diagram illustrating a communication system according to an embodiment of the present disclosure is shown;

[0015] Figure 2 A schematic diagram illustrating interactions between devices according to some embodiments of the present disclosure is shown;

[0016] Figure 3 A flowchart of a method according to an embodiment of the present disclosure is shown;

[0017] Figure 4 A flowchart of a method according to an embodiment of the present disclosure is shown;

[0018] Figure 5 shows a simplified block diagram of an apparatus suitable for implementing embodiments of the present disclosure; and

[0019] Figure 6 A block diagram of an example computer-readable medium is shown, according to some example embodiments of the present disclosure.

[0020] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0021] The principles of the present disclosure will now be described with reference to some exemplary embodiments. It should be understood that the description of the exemplary embodiments is merely for the purpose of illustrating and helping those skilled in the art to understand and implement the present disclosure, and does not represent any limitation on the scope of the present disclosure. The disclosure described herein can be implemented in various other ways in addition to the way described below.

[0022] 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 skill in the art to which this disclosure belongs.

[0023] References in this disclosure to "one embodiment," "an embodiment," "an example embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an example embodiment, it is considered within the knowledge of those skilled in the art to effect such feature, structure, or characteristic in conjunction with other embodiments (whether or not explicitly described).

[0024] It should be understood that although the terms "first" and "second" etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element without departing from the scope of the example embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0025] The terms used herein are for the purpose of describing particular embodiments only and are not intended to limit the example embodiments. 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. It will be further understood that the terms "comprises," "comprising," "has," "having," "includes," and / or "including" when used herein specify the presence of stated features, elements, and / or components, etc., but do not preclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

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

[0027] (a) a pure hardware circuit implementation (such as an implementation using only analog and / or digital circuitry), and

[0028] (b) a combination of hardware circuitry and software such as (as applicable):

[0029] (i) a combination of analog and / or digital hardware circuits and software / firmware, and

[0030] (ii) any portion of hardware processor(s) (including digital signal processor(s)) with software, software and memory(s) that work together to cause a device (such as a mobile phone or server) to perform various functions, and

[0031] (c) Hardware circuit(s) and / or processor(s), such as microprocessor(s) or portion(s) of microprocessor(s), which requires software (e.g., firmware)

[0032] The software can be operated but not exist when the operation is not needed.

[0033] This definition of circuitry applies to all uses of the term in this application, including in any claims. As another example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. For example, if applicable to the particular claim element, the term circuitry also covers a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0034] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard, such as Long Term Evolution (LTE), Advanced LTE (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), New Radio (NR), etc. In addition, the communication between the terminal equipment and the network equipment in the communication network can be performed according to the communication protocol of any suitable generation, including but not limited to the first generation (1G), second generation (2G), 2.5G, 2.55G, third generation (3G), fourth generation (4G), 4.5G, future fifth generation (5G) communication protocol, and / or any other protocol currently known or developed in the future. The embodiments of the present disclosure can be applied to various communication systems. In view of the rapid development of communication, there will certainly be future types of communication technologies and systems that can embody the present disclosure. It should not be considered that the scope of the present disclosure is limited to the above-mentioned systems.

[0035] As used herein, the term "network device" refers to a node in a communication network via which a terminal device accesses the network and receives services from it. A network device may refer to a base station (BS) or an access point (AP), such as a NodeB (NodeB or NB), an evolved NodeB (eNodeB or eNB), a NR NB (also known as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, an integrated access and backhaul (IAB) node, a low-power node (such as a femto, pico), etc., depending on the terminology and technology applied.

[0036] The term "terminal device" refers to any terminal device that can perform wireless communication. As an example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS) or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smart phones, voice over IP (VoIP) phones, wireless local loop phones, tablet computers, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image acquisition terminal devices such as digital cameras, game terminal devices, music storage and playback devices, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless client equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated process chain environments), consumer electronic devices, devices operating on commercial and / or industrial wireless networks, etc. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.

[0037] As mentioned above, in order to transmit small amounts of / infrequent data, the terminal device needs to transition to the RRC connected state and back to the RRC inactive state for each transmission. This results in wasteful power consumption and signaling overhead, which is particularly important for Internet of Things (IoT) and Machine Type Communication (MTC) use cases.

[0038] One solution to this problem is to transmit uplink data on pre-configured PUSCH resources (eg, reusing configured grant type 1 resources, such as RRC setup / recovery messages).

[0039] In practice, uplink transmissions to network devices on pre-configured uplink resources may fail for a variety of reasons. However, the terminal device does not notify the network device of such failures. Because the network device is unaware of the failures, it cannot optimally configure / reconfigure uplink resources for the terminal device. Receiving such feedback would enable the network device to better configure uplink resources and provide a more SON-friendly solution.

[0040] According to an embodiment of the present disclosure, a terminal device records failures and failure reasons associated with transmissions on pre-configured resources. The terminal device transmits this recorded information to a network device. In this way, the network device can be informed of the occurrence and cause of the failure. The network device can use this information more efficiently to configure uplink resources, and resources can be efficiently allocated for other purposes or other terminal devices.

[0041] Figure 1 Schematic diagram of a communication system in which embodiments of the present disclosure may be implemented is shown. The communication system 100, as part of a communication network, includes devices 110-1, 110-2, ..., 110-N (which may be collectively referred to as "(a plurality of) first devices 110"). The communication system 100 also includes a second device 120. One or more devices are associated with a cell and are covered by the cell. It should be understood that Figure 1 The number of devices and cells shown is provided for illustrative purposes and does not represent any limitation. The communication system 100 may include any suitable number of devices and cells. In the communication system 100, the first device 110 and the second device 120 can transmit data and control information to each other. In the case where the first device 110 is a terminal device and the second device 120 is a network device, the link from the second device 120 to the first device 110 is called a downlink (DL), and the link from the first device 110 to the second device 120 is called an uplink (UL). Figure 1 The number of devices shown is given for illustrative purposes and does not represent any limitation. The second device 120 and the first device 110 are interchangeable.

[0042] Communications in the communication system 100 may be implemented according to any (multiple) appropriate communication protocols, including but not limited to first generation (1G), second generation (2G), third generation (3G), fourth generation (4G), and fifth generation (5G) cellular communication protocols, wireless local area network communication protocols such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocols currently known or developed in the future. Furthermore, communications may utilize any appropriate wireless communication technology, including but not limited to: code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplexer (FDD), time division duplexer (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiple access (OFDMA), and / or any other technology currently known or developed in the future.

[0043] Figure 2Schematic diagram of interaction 200 between devices according to some embodiments of the present disclosure is shown. Interaction 300 can be implemented at any suitable device. For illustrative purposes only, interaction 300 is described as being implemented at first device 110-1 and second device 120.

[0044] The second device 120 may generate 2005 first information. The first information indicates a set of resources preconfigured for transmission. The set of resources may be a set of PUSCH resources. In other embodiments, the set of resources may be a configured grant. Alternatively or additionally, the set of resources may be periodic uplink resources (PURs). In some embodiments, the set of resources may be resources with a preconfigured time periodicity. In other embodiments, the first information may implicitly instruct the first device 110-1 to record transmission failures on the set of resources. Alternatively, the first information may explicitly instruct the first device 110-01 to record transmission failures on the set of resources.

[0045] Second device 120 transmits 2010 the first information to first device 110-1. In some embodiments, second device 120 may broadcast the first information to first device 110-1. In other embodiments, first device 110-1 may be in an RRC connected state and receive the first information in RRC signaling (e.g., an RRC release message or an RRC release with a suspend indication).

[0046] In some embodiments, the first device 110-1 may transition 2015 to the RRC inactive state.In other embodiments, the first device 110-1 may transition 2015 to the idle state.

[0047] The first device 110-1 may perform an uplink transmission on the set of resources. In some embodiments, the uplink transmission may include traffic from an instant messaging service (e.g., WhatsApp, QQ, WeChat, LINE). In other embodiments, the uplink transmission may include heartbeat / keep-alive traffic. In one example, the uplink transmission may include push notifications from various applications. Alternatively, the uplink transmission may include traffic from a wearable device. In other embodiments, the uplink transmission may include indications from sensors, such as an industrial wireless sensor network that periodically transmits temperature and pressure readings.

[0048] The first device 110-1 may determine 2020 whether a predetermined number of transmission failures have been detected on the set of resources. In some embodiments, the first device 110-1 may detect a transmission failure by determining whether there is a lack of available data. If so, a transmission failure is determined to have occurred.

[0049] Alternatively, in other embodiments, first device 110-1 may determine that a transmission failure has occurred if a certain type of available data (e.g., suitable for a preconfigured uplink transmission) is lacking. In still other embodiments, a transmission failure is detected if no acknowledgment (ACK) is received from second device 120. Alternatively or additionally, in some embodiments, first device 110-1 may determine that a transmission failure has occurred if a configuration for uplink transmission is unavailable.

[0050] In some embodiments, a timing advance prior to transmission may be used for transmission failure detection. That is, a transmission failure occurs if a valid timing advance is missing. Alternatively or additionally, first device 110-1 may determine that a transmission failure occurs if listen-before-talk (LBT) fails during a transmission attempt.

[0051] The first device 110-1 may detect the transmission failure by determining the RRC state of the first device 110-1. For example, if the first device 110-1 is in the RRC idle state, the first device 110-1 may detect the transmission failure on the PUR. Alternatively, if the first device 110-1 is in the RRC inactive state, the first device 110-1 may detect the transmission failure on the preconfigured resources. In other embodiments, when the first device is in the RRC connected state, the first device 110-1 may detect the transmission failure on the configured grant.

[0052] According to an embodiment of the present disclosure, if the first device 110-1 detects a predetermined number of transmission failures, the second information is generated 2025. In some embodiments, the second information may be generated if any one transmission failure is detected on the set of resources. Alternatively, in other embodiments, the predetermined number may be greater than 1. That is, the second information is generated if a predetermined number of multiple transmission failures have been detected.

[0053] The second information indicates at least a predetermined number of transmission failures and the reasons for the predetermined number of transmission failures. For example, as described above, the reasons may include one or more of the following: lack of available uplink data, lack of certain available uplink data (suitable for preconfigured UL transmission), lack of ACK received from the second device 120, lack of available configuration for transmission, lack of valid timing advance, LBT failure. In some embodiments, the second information can be generated per RRC state. For example, if the first device 110-1 is in an RRC inactive state, the first device 110-1 can generate the second information. If the first device 110-1 switches to an RRC idle state, the first device 110-1 can also generate second information related to the RRC idle state.

[0054] In some embodiments, the second information may include one or more timestamps associated with the predetermined number of transmission failures. Alternatively or additionally, the second information may include the location of first device 110-1. In other embodiments, the second information may include one or more RRC states associated with the predetermined number of transmission failures. The second information may include one or more transmission failures and one or more corresponding causes of the transmission failures.

[0055] First device 110-1 transmits 2035 the second information to second device 120. First device 110-1 may transmit the second information immediately. Alternatively, first device 110-1 may transmit the second information after receiving a request from second device 120. For example, after second device 120 may transmit 2030 a request for the second information to first device 110-1, first device 110-1 transmits the second information to second device 120. In some embodiments, the request may instruct first device 110-1 to report a transmission failure specific to a failure reason.

[0056] In some embodiments, first device 110-1 may transmit the second information to second device 120 via dedicated signaling. For example, the second information may be transmitted via RRC signaling. In some embodiments, first device 110-1 may transmit the second information in a current RRC connection between first device 110-1 and second device 120. Alternatively, first device 110-1 may transmit the second information in a subsequent RRC connection. In other embodiments, first device 110-1 may transmit the second information during the next uplink transmission.

[0057] First device 110-1 may include the second information in an RRC setup request and transmit the RRC setup request to second device 120. In an example embodiment, the second information may be included in an RRC recovery request and first device 110-1 may transmit the RRC recovery request to second device 120. Alternatively, first device 110-1 may include the second information in an RRC setup complete message and transmit the RRC setup complete message to second device 120. In other embodiments, first device 110-1 may include the second information in an RRC recovery complete message and transmit the RRC recovery complete message to second device 120. In some embodiments, the second information may be included in an RRC message for uplink transmission on the set of preconfigured resources. Alternatively, in some embodiments, first device 110-1 may include the second information in a UE assistance information message.

[0058] In some embodiments, first device 110-1 may transmit availability information to second device 120 to indicate that the second information is available. Based on the availability information, network device 120 may determine to obtain a portion of the second information related to a failure cause. For example, second device 120 may request a portion of the second information based on the failure cause.

[0059] Figure 3 FIG3 is a flow chart of a method 300 according to an embodiment of the present disclosure. The method 300 may be implemented at any suitable device. For example, the method may be implemented at the first device 110 - 1 .

[0060] At block 310, first device 110-1 receives first information from second device 120. In some embodiments, first device 110-1 may be in an RRC connected state and receive the first information in RRC signaling (e.g., an RRC release message or an RRC release with a suspend indication). Alternatively, the first information may be broadcast.

[0061] First device 110-1 may perform an uplink transmission on the set of resources. In some embodiments, before performing the uplink transmission, first device 110-1 may transition to an RRC inactive state. In other embodiments, first device 110-1 may transition to an idle state before performing the uplink transmission.

[0062] In some embodiments, the uplink transmission may include traffic from instant messaging services (e.g., WhatsApp, QQ, WeChat, LINE). In other embodiments, the uplink transmission may include heartbeat / keep-alive traffic. In an example embodiment, the uplink transmission may include push notifications from various applications. Alternatively, the uplink transmission may include traffic from wearable devices. In yet other embodiments, the uplink transmission may include indications from sensors, such as industrial wireless sensor networks that periodically transmit temperature and pressure readings.

[0063] In some embodiments, first device 110-1 may determine whether a predetermined number of transmission failures have been detected on the set of resources. In some embodiments, a transmission is determined to have occurred if there is a lack of available data. In other embodiments, first device 110-1 determines that a transmission failure has occurred if there is a lack of available data of a certain type (e.g., suitable for a preconfigured uplink transmission). Alternatively, in other embodiments, a transmission failure is detected if no ACK is received from second device 120. Alternatively or additionally, first device 110-1 may determine that a transmission failure has occurred if the configuration for the transmission is unavailable.

[0064] In some embodiments, the timing advance before the transmission can be used to detect a transmission failure. For example, if a valid timing advance is missing, a transmission failure is determined to have occurred. Alternatively, if LBT fails during a transmission attempt, the first device 110-1 can detect that a transmission failure has occurred.

[0065] The first device 110-1 may detect the transmission failure by determining the RRC state of the first device 110-1. For example, if the first device 110-1 is in the RRC idle state, the first device 110-1 may detect the transmission failure on the PUR. Alternatively, if the first device 110-1 is in the RRC inactive state, the first device 110-1 may detect the transmission failure on the preconfigured resources. In other embodiments, when the first device is in the RRC connected state, the first device 110-1 may detect the transmission failure on the configured grant.

[0066] At block 320, first device 110-1 generates second information if a predetermined number of transmission failures are detected on the set of resources. In some embodiments, the second information may be generated if any one transmission failure is detected on the set of resources. Alternatively, in other embodiments, the predetermined number may be greater than one. In other words, the second information is generated if a predetermined number of transmission failures have been detected.

[0067] The second information indicates at least a predetermined number of transmission failures and reasons for the predetermined number of transmission failures. For example, as described above, the reasons may include one or more of the following: lack of available uplink data, lack of certain available uplink data (suitable for pre-configured UL transmission), lack of an ACK from the second device 120, lack of an available configuration for transmission, lack of a valid timing advance, and LBT failure. In some embodiments, the second information may be generated per RRC state.

[0068] In some embodiments, the second information may include one or more timestamps for a predetermined number of transmission failures. Alternatively or additionally, the second information may include the location of first device 110-1. The second information may include one or more transmission failures and one or more corresponding causes for the transmission failures. The second information may also include one or more RRC states associated with the predetermined number of transmission failures.

[0069] At block 330 , first device 110 - 1 transmits the second information to second device 120 . First device 110 - 1 may transmit the second information immediately. In other embodiments, first device 110 - 1 may transmit the second information after receiving a request from second device 120 .

[0070] In some embodiments, first device 110-1 may transmit the second information to second device 120 via dedicated signaling. For example, the second information may be transmitted via RRC signaling. In some embodiments, first device 110-1 may transmit the second information in a current RRC connection. Alternatively, first device 110-1 may transmit the second information in a subsequent RRC connection. In other embodiments, first device 110-1 may transmit the second information in a subsequent uplink transmission.

[0071] First device 110-1 may include the second information in an RRC establishment request and transmit the RRC establishment request to second device 120. In an example embodiment, first device 110-1 may include the second information in an RRC recovery request and transmit the RRC recovery request to second device 120. Alternatively, first device 110-1 may include the second information in an RRC setup complete message and transmit the RRC setup complete message to second device 120. In yet another embodiment, first device 110-1 may include the second information in an RRC recovery complete message and transmit the RRC recovery complete message to second device 120. In some embodiments, the second information may be included in an RRC message for uplink transmission on the set of preconfigured resources. Alternatively, the second information may be included in a UE assistance information message.

[0072] In some embodiments, first device 110-1 may transmit availability information to second device 120 to indicate that the second information is available.First device 110-1 may receive a request to report a portion of the second information based on the failure cause and transmit the portion of the second information to second device 120.

[0073] Figure 4 4. A flow chart of method 400 is shown. Method 400 can be implemented at any suitable device. For example, the method can be implemented at second device 120.

[0074] In some embodiments, the second device 120 may generate first information. The first information indicates a set of resources preconfigured for transmission. The set of resources may be a set of PUSCH resources. In other embodiments, the set of resources may be a configured grant. Alternatively or additionally, the set of resources may be a PUR. In some embodiments, the set of resources may be resources with a preconfigured time periodicity. In other embodiments, the first information may implicitly instruct the first device 110-1 to log transmission failures on the set of resources. Alternatively, the first information may explicitly instruct the first device 110-01 to log transmission failures on the set of resources.

[0075] At block 410, second device 120 transmits first information to first device 110-1. In some embodiments, second device 120 may broadcast the first information to first device 110-1. In other embodiments, second device 120 may transmit the first information in dedicated signaling.

[0076] At block 420, the second device 120 receives second information indicating at least a predetermined number of transmission failures detected on the set of resources and a cause of the predetermined number of transmission failures. For example, as described above, the cause may include one or more of: a lack of available uplink data, a lack of certain available uplink data (suitable for preconfigured UL transmissions), a lack of an ACK from the second device 120, a lack of an available configuration for transmission, a lack of a valid timing advance, or a failure of LBT during a transmission attempt (in unlicensed spectrum). In some embodiments, the second information may be generated per RRC state.

[0077] In some embodiments, the second information may include one or more timestamps associated with the predetermined number of transmission failures. Alternatively or additionally, the second information may include the location of first device 110-1. The second information may include one or more transmission failures and one or more corresponding causes of the transmission failures. In other embodiments, the second information may include one or more RRC states associated with the predetermined number of transmission failures.

[0078] In some embodiments, the second information may be transmitted via dedicated signaling (e.g., RRC signaling). In some embodiments, the second information may be transmitted in the current RRC connection between first device 110-1 and second device 120. Alternatively, the second information may be transmitted in a subsequent RRC connection between first device 110-1 and second device 120. In other embodiments, the second information may be transmitted on the next uplink transmission.

[0079] The second information may be transmitted in an RRC setup request. In an example embodiment, the second information may be transmitted in an RRC resume request. Alternatively, the second information may be transmitted in an RRC setup complete message. In other embodiments, the second information may be transmitted in an RRC resume complete message. In some embodiments, the second information may be transmitted in an RRC message for uplink transmission on the set of preconfigured resources.

[0080] In some embodiments, second device 120 may receive availability information from first device 110-1 indicating that the second information is available.Second device 120 may transmit a request for a portion of the second information based on the failure cause and receive the portion of the second information from first device 110-1.

[0081] In block 430, the second device 120 reallocates the set of resources based on the second information. For example, if the second information indicates that most transmission failures are caused by a lack of data, the second device 120 may reallocate fewer resources for transmission. In other embodiments, if the second information indicates that most transmission failures are caused by a lack of a certain type of data, the second device 120 may reallocate fewer resources for a certain type of service that requires a certain type of data. In some embodiments, if the second information indicates that configuration is unavailable, the second device 120 may reallocate more resources. In this way, the second device 120 can use the information more efficiently to configure uplink resources. PUSCH resources can be efficiently allocated for other purposes or other UEs.

[0082] In an embodiment, an apparatus for performing method 300 (e.g., first device 110-1) may include corresponding components for performing corresponding steps in method 300. These components may be implemented in any suitable manner, such as by a circuit system or a software module.

[0083] In some embodiments, the apparatus includes a component for receiving first information indicating a set of resources preconfigured for transmission from a second device; a component for generating second information indicating at least a predetermined number of transmission failures and reasons for the predetermined number of transmission failures based on determining that a predetermined number of transmission failures have occurred on the set of resources; and a component for transmitting the second information to the second device.

[0084] In some embodiments, the second information further indicates at least one of: one or more timestamps associated with the predetermined number of transmission failures, a location of the first device, or one or more radio resource control (RRC) states associated with the predetermined number of transmission failures.

[0085] In some embodiments, the apparatus further comprises means for detecting a predetermined number of transmission failures by detecting at least one of: a lack of available data, a lack of an ACK from the second device 120, a lack of an available configuration for transmission, a lack of a valid timing advance, or a listen-before-talk failure.

[0086] In some embodiments, means for transmitting the second information to the second device includes means for transmitting at least a portion of the second information to the second device in response to a request received from the second device.

[0087] In some embodiments, the means for transmitting the second information to the second device comprises means for transmitting the second information via radio resource control (RRC) signaling.

[0088] In some embodiments, the means for transmitting the second information via RRC signaling includes means for transmitting the second information in a current RRC connection between the first device and the second device or in a subsequent RRC connection between the first device and the second device.

[0089] In some embodiments, the means for transmitting the second information via RRC signaling comprises means for including the second information into at least one of: an RRC establishment request, an RRC resume request, an RRC establishment complete message, an RRC resume complete message, or a UE assistance information message.

[0090] In some embodiments, means for transmitting the second information to the second device comprises means for transmitting the second information via dedicated signaling.

[0091] In some embodiments, the set of resources includes at least one of: physical uplink shared channel (PUSCH) resources, configured grants, or periodic uplink resources.

[0092] In some embodiments, the apparatus further comprises means for detecting a transmission failure by determining whether the first device is in one of: an RRC idle state, an RRC inactive state, or an RRC connected state.

[0093] In some embodiments, the second information includes a plurality of transmission failures and corresponding reasons causing the plurality of failures.

[0094] In some embodiments, the first device comprises a terminal device and the second device comprises a network device.

[0095] In an embodiment, an apparatus for performing method 400 (e.g., second device 120) may include corresponding components for performing corresponding steps in method 400. These components may be implemented in any suitable manner. For example, they may be implemented by a circuit system or a software module.

[0096] In some embodiments, the apparatus includes a component for transmitting first information indicating a set of resources preconfigured for transmission to a first device; a component for receiving second information from the first device indicating at least a predetermined number of transmission failures detected on the set of resources and a reason for the predetermined number of transmission failures; and a component for reallocating the set of resources based on the second information.

[0097] In some embodiments, the second information further indicates at least one of: one or more timestamps associated with the predetermined number of transmission failures, a location of the first device, or one or more radio resource control (RRC) states associated with the predetermined number of transmission failures.

[0098] In some embodiments, the cause includes at least one of: lack of available data, lack of acknowledgement from the second device, lack of valid timing advance, lack of available configuration for transmission, or failure of listen-before-talk.

[0099] In some embodiments, the apparatus further comprises means for transmitting a request to the first device to report the second information.

[0100] In some embodiments, the request indicates that at least a portion of the second information is to be reported based on a reason.

[0101] In some embodiments, the means for receiving the second information comprises means for receiving the second information via RRC signaling.

[0102] In some embodiments, the means for receiving the second information via RRC signaling includes means for receiving the second information in a current RRC connection between the first device and the second device or in a subsequent RRC connection between the first device and the second device.

[0103] In some embodiments, the means for receiving the second information comprises means for obtaining the second information from at least one of: an RRC setup request, an RRC resume request, an RRC setup complete message, an RRC resume complete message, or a UE information response message.

[0104] In some embodiments, the means for receiving the second information comprises means for receiving the second information via dedicated signaling.

[0105] In some embodiments, the set of resources includes at least one of: physical uplink shared channel (PUSCH) resources, configured grants, or periodic uplink resources.

[0106] In some embodiments, the second information includes a plurality of transmission failures and corresponding reasons causing the plurality of failures.

[0107] In some embodiments, the first device comprises a terminal device and the second device comprises a network device.

[0108] Figure 5 is a simplified block diagram of a device 500 suitable for implementing embodiments of the present disclosure. The device 500 may be provided to implement a communication device, such as Figure 1 The first device 110 or the second device 120 is shown. As shown, the device 500 includes one or more processors 510, one or more memories 520 coupled to the processor 510, and one or more communication modules 540 coupled to the processor 510.

[0109] The communication module 540 is used for two-way communication. The communication module 540 has at least one antenna to facilitate communication. The communication interface can represent any interface necessary to communicate with other network elements.

[0110] Processor 510 can be of any type suitable for the local technology network and, as non-limiting examples, can include one or more of the following: 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. Device 500 can have multiple processors, such as application-specific integrated circuit chips that are time-slave to a clock synchronized with a main processor.

[0111] The memory 520 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 524, electrically programmable read-only memory (EPROM), flash memory, hard disks, compact disks (CDs), digital video disks (DVDs), and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 522 and other volatile memories that do not persist during power outages.

[0112] Computer program 530 includes computer-executable instructions that are executed by associated processor 510. Program 530 may be stored in ROM 524. Processor 510 may perform any suitable actions and processes by loading program 530 into RAM 522.

[0113] The embodiments of the present disclosure may be implemented by the program 520 so that the device 500 may execute the following steps: Figure 2 and Figure 4 The embodiments of the present disclosure may also be implemented by hardware or a combination of software and hardware.

[0114] In some example embodiments, program 530 may be tangibly embodied in a computer-readable medium that may be included in device 500 (such as memory 520) or other storage device accessible to device 500. Device 500 may load program 530 from the computer-readable medium to RAM 522 for execution. The computer-readable medium may include any type of tangible, non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Figure 6 An example of a computer readable medium 600 in the form of a CD or DVD is shown. The computer readable medium has a program 530 stored thereon.

[0115] It will be appreciated that future networks may utilize network function virtualization (NFV), which is a network architecture concept that proposes virtualizing network node functions into "building blocks" or entities that can be operationally connected or linked together to provide services. A virtualized network function (VNF) may include one or more virtual machines that use standard or general-purpose types of servers rather than customized hardware to run computer program code. Cloud computing or data storage may also be used. In radio communications, this may mean that node operations are at least partially performed in a central / centralized unit CU (e.g., a server, host, or node) that is operationally coupled to a distributed unit DU (e.g., a radio head / node). Node operations may also be distributed across multiple servers, nodes, or hosts. It will also be appreciated that the distribution of work between core network operations and base station operations may vary depending on the implementation.

[0116] In one embodiment, the server can generate a virtual network through which the server communicates with the distributed units. In general, virtual networking can involve the process of combining hardware and software network resources and network functions into a single software-based management entity (virtual network). Such a virtual network can provide flexible distribution of operations between the server and the radio head / node. In practice, any digital signal processing task can be performed in the CU or DU, and the boundary of the transfer of responsibilities between the CU and DU can be selected according to the implementation.

[0117] Thus, in one embodiment, a CU-DU architecture is implemented. In this case, the device 500 may be included in a central unit (e.g., a control unit, an edge cloud server, a server) that is operably coupled (e.g., via a wireless or wired network) to a distributed unit (e.g., a remote radio head / node). That is, the central unit (e.g., an edge cloud server) and the distributed units may be independent devices that communicate with each other via a radio path or via a wired connection. Alternatively, they may be in the same entity that communicates via a wired connection, etc. The edge cloud or edge cloud server may serve multiple distributed units or radio access networks. In one embodiment, at least some of the described processes may be performed by the central unit. In another embodiment, the device 500 may instead be included in a distributed unit, and at least some of the described processes may be performed by the distributed unit.

[0118] In one embodiment, the execution of at least some of the functions of the device 500 can be shared between two physically separate devices (DU and CU) forming an operational entity. Therefore, the device can be regarded as depicting an operational entity comprising one or more physically separate devices for performing at least some of the described processes. In one embodiment, such a CU-DU architecture can provide a flexible distribution of operations between the CU and the DU. In practice, any digital signal processing task can be performed in the CU or the DU, and the boundary of the transfer of responsibilities between the CU and the DU can be selected according to the implementation. In one embodiment, the device 500 controls the execution of the process regardless of the location of the device and where the process / function is performed.

[0119] In general, various embodiments of the present disclosure may be implemented using hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented using hardware, while other aspects may be implemented using firmware or software that may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are illustrated and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented using hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or a controller or other computing device, or some combination thereof.

[0120] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer executable instructions, such as instructions included in program modules, which are executed in a device on a target real or virtual processor to perform the above-referenced Figure 3 and Figure 4 Methods 300 and 400 are described. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of program modules can be combined or split between program modules as needed. The machine-executable instructions of program modules can be executed on local or distributed devices. In distributed devices, program modules can be located in both local and remote storage media.

[0121] The program code for executing the disclosed method can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that the program code causes the function / operation specified in the flow chart and / or block diagram to be realized when executed by the processor or controller. The program code can be executed entirely on the machine, partially on the machine, as an independent software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0122] In the context of the present disclosure, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of carriers include signals, computer-readable media, etc.

[0123] Computer readable media can be computer readable signal media or computer readable storage media.Computer readable media can include but are not limited to electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the foregoing.More specific examples of computer readable storage media will include electrical connections with one or more wires, portable computer floppy disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disc read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0124] In addition, although operations are described in a particular order, this should not be understood as requiring such operations to be performed in the particular order shown or in sequence or performing all of the operations shown to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details have been included in the above discussion, these should not be interpreted as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.

[0125] Although the disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A method for communication, comprising: At a first device, receiving first information from a second device indicating a set of resources preconfigured for transmission; generating, based on determining that a predetermined number of transmission failures have occurred on the set of resources, second information indicating at least the predetermined number of transmission failures and a cause of the predetermined number of transmission failures; as well as Transmitting the second information to the second device for reallocating the set of resources, wherein transmitting the second information to the second device includes: transmitting the second information via radio resource control (RRC) signaling; Transmitting the second information via the RRC signaling includes: Including the second information into at least one of the following: an RRC establishment request, an RRC recovery request, an RRC establishment complete message, an RRC recovery complete message, or a user equipment UE assistance information message; detecting the predetermined number of transmission failures by detecting at least one of: a lack of available data, a lack of an acknowledgement from the second device, a lack of an available configuration for the transmission, a lack of a valid timing advance, or a listen-before-talk failure; wherein the second information further indicates: one or more radio resource control (RRC) states associated with the predetermined number of transmission failures; and The predetermined number of transmission failures is detected by determining whether the first device is in one of: an RRC idle state, an RRC inactive state, or an RRC connected state. 2 . The method of claim 1 , wherein the second information further indicates at least one of: one or more timestamps associated with the predetermined number of transmission failures, or a location of the first device.

3. The method according to claim 1 , wherein transmitting the second information to the second device comprises: At least a portion of the second information is transmitted to the second device in response to a request received from the second device.

4. The method of claim 1, wherein the set of resources comprises at least one of: physical uplink shared channel (PUSCH) resources, configured grants, or periodic uplink resources.

5. A first device for communication, comprising: at least one processor; as well as at least one memory including computer program code; The at least one memory and the computer program code are configured to, with the at least one processor, cause the first device to: receiving, from a second device, first information indicating a set of resources preconfigured for transmission; generating, based on determining that a predetermined number of transmission failures have occurred on the set of resources, second information indicating at least the predetermined number of transmission failures and a cause of the predetermined number of transmission failures; as well as Transmitting the second information to the second device for reallocating the set of resources, wherein transmitting the second information to the second device includes: transmitting the second information via radio resource control (RRC) signaling; Transmitting the second information via the RRC signaling includes: Including the second information into at least one of the following: an RRC establishment request, an RRC recovery request, an RRC establishment complete message, an RRC recovery complete message, or a user equipment UE assistance information message; detecting the predetermined number of transmission failures by detecting at least one of: a lack of available data, a lack of an acknowledgement from the second device, a lack of an available configuration for the transmission, a lack of a valid timing advance, or a listen-before-talk failure; wherein the second information further indicates: one or more radio resource control (RRC) states associated with the predetermined number of transmission failures; and The predetermined number of transmission failures is detected by determining whether the first device is in one of: an RRC idle state, an RRC inactive state, or an RRC connected state. 6 . The first device of claim 5 , wherein the second information further indicates at least one of: one or more timestamps associated with the predetermined number of transmission failures, or a location of the first device.

7. The first device according to claim 5, wherein the first device is caused to transmit the second information to the second device by: At least a portion of the second information is transmitted to the second device in response to a request received from the second device.

8. The first device of claim 5, wherein the set of resources comprises at least one of: physical uplink shared channel (PUSCH) resources, configured grants, or periodic uplink resources.

9. A second device for communication, comprising: at least one processor; as well as at least one memory including computer program code; The at least one memory and the computer program code are configured to, with the at least one processor, cause the second device to: transmitting, to the first device, first information indicating a set of resources preconfigured for transmission; receiving, from the first device, second information indicating at least a predetermined number of transmission failures detected on the set of resources and a cause of the predetermined number of transmission failures; as well as reallocating the set of resources based on the second information, wherein receiving the second information from the first device comprises: receiving the second information via radio resource control (RRC) signaling; Receiving the second information via the RRC signaling includes: receiving the second information from at least one of the following: an RRC establishment request, an RRC resume request, an RRC establishment complete message, an RRC resume complete message, or a user equipment (UE) assistance information message; The second information further indicates: one or more radio resource control (RRC) states associated with the predetermined number of transmission failures.

10. The second device of claim 9, wherein the second information further indicates at least one of: one or more timestamps associated with the predetermined number of transmission failures, or a location of the first device.

Images