Method and apparatus for stopping CSI / SRS transmission

Abstract

A method includes receiving, by a user equipment (UE), a first message from a network apparatus, the first message including configuration information for autonomous cancellation of sounding reference signal (SRS) reporting, determining, by the UE, upon an SRS reporting instance approaching, to transmit an SRS report to the network apparatus based on one or more conditions for cancelling SRS reporting included in the configuration information, the one or more conditions based on an exchanged traffic prediction model, and transmitting, by the UE, an SRS report to the network apparatus based upon the one or more conditions not being met.

Description

METHOD AND APPARATUS FOR STOPPING CSI / SRS TRANSMISSIONFIELD

[0001] Various example embodiments relate generally to wireless networks and, more particularly, for a method and apparatus for stopping CSI / SRS transmission.BACKGROUND

[0002] A user equipment (UE) provides reports that anticipate or predict bytes before the arrive to a buffer. These reports, in some cases, take the form of a channel state information (CSI) report and / or a sounding reference signal (SRS) report.SUMMARY

[0003] According to some aspects, there is provided the subject matter of the independent claims. Some further aspects are defined in the dependent claims.

[0004] In accordance with aspects of the disclosure, a method includes receiving, by a user equipment (UE), a first message from a network apparatus, the first message including configuration information for autonomous cancellation of sounding reference signal (SRS) reporting, determining, by the UE, upon an SRS reporting instance approaching, to transmit an SRS report to the network apparatus based on one or more conditions for cancelling SRS reporting included in the configuration information, the one or more conditions based on an exchanged traffic prediction model, and transmitting, by the UE, an SRS report to the network apparatus based upon the one or more conditions not being met.

[0005] In an aspect of the method, the one or more conditions may include a confidence level of a predicted traffic pattern, a buffer size threshold, and / or a prohibit internal time to not skip SRS reporting.

[0006] In an aspect of the method, the autonomous cancellation of SRS reporting may configure a transmission prohibit timer.

[0007] In an aspect of the method, the autonomous cancellation of SRS reporting may configure a data volume threshold.

[0008] In an aspect of the method, SRS reporting may be cancelled if a buffer size is predicted to be less than the data volume threshold.

[0009] In an aspect of the method, the method may further include receiving, by the UE, a second message from a network apparatus, the second message including buffer occupancy information for autonomous cancellation of SRS reporting.

[0010] In an aspect of the method, the method may further include updating the exchanged traffic prediction model based on the second message.

[0011] In an aspect of the method, the method may further include reevaluating, by the UE, the one or more conditions based on the updated traffic prediction model.

[0012] In accordance with aspects of the disclosure, a processor-readable medium stores instructions which, when executed by at least one processor of a UE apparatus, cause the UE apparatus at least to perform a method as in any one of the preceding aspects.

[0013] In accordance with aspects of the disclosure, a network apparatus includes at least one processor and at least one memory storing instructions which, when executed by the at least one processor, causes the network apparatus at least to perform a method as in any one of the preceding aspects.

[0014] In accordance with aspects of the disclosure, a user equipment (UE) apparatus includes at least one processor and at least one memory storing instructions which, when executed by the at least one processor, causes the UE apparatus at least to perform receiving, by a user equipment (UE), a first message from a network apparatus, the first message including configuration information for autonomous cancellation of sounding reference signal (SRS) reporting, determining, by the UE, upon an SRS reporting instance approaching, to transmit an SRS report to the network apparatus based on one or more conditions for cancelling SRS reporting included in the configuration information, the one or more conditions based on an exchanged traffic prediction model, and transmitting, by the UE, an SRS report to the network apparatus based upon the one or more conditions not being met.

[0015] In an aspect of the UE apparatus, the one or more conditions may include a confidence level of a predicted traffic pattern, a buffer size threshold, and / or a prohibit internal time to not skip SRS reporting.

[0016] In an aspect of the UE apparatus, the autonomous cancellation of SRS reporting may configure a transmission prohibit timer.

[0017] In an aspect of the UE apparatus, the autonomous cancellation of SRS reporting may configure a data volume threshold.

[0018] In an aspect of the UE apparatus, SRS reporting may be cancelled if a buffer size is predicted to be less than the data volume threshold.

[0019] According to some aspects, there is provided the subject matter of the independent claims. Some further aspects are defined in the dependent claims.BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Some example embodiments will now be described with reference to the accompanying drawings.

[0021] FIG. 1 is a diagram of an example embodiment of wireless networking between a network system and a user equipment (UE), according to one illustrated aspect of the disclosure;

[0022] FIG. 2 is a diagram of example components of a network system, according to one illustrated aspect of the disclosure;

[0023] FIG. 3 is a diagram of an example embodiment of signals and operations among a gNB and a UE, according to one illustrated aspect of the disclosure;

[0024] FIG. 4 is a diagram of an example embodiment of signals and operations among a gNB and a UE, according to one illustrated aspect of the disclosure; and

[0025] FIG. 5 is a diagram of an example block diagram of a wireless station or node (e.g., network node (such as gNB), user node or UE, relay node, or other node), according to one illustrated aspect of the present disclosure.DETAILED DESCRIPTION

[0026] In the following description, certain specific details are set forth in order to provide a thorough understanding of disclosed aspects. However, one skilled in the relevant art will recognize that aspects may be practiced without one or more of these specific details or with other methods, components, materials, etc. In other instances, well-known structures associated with transmitters, receivers, or transceivers have not been shown or described in detail to avoid unnecessarily obscuring descriptions of the aspects.

[0027] Reference throughout this specification to “one aspect” or “an aspect” means that a particular feature, structure, or characteristic described in connection with the aspect is included in at least one aspect. Thus, the appearances of the phrases “in one aspect” or “in an aspect” in various places throughout this specification are not necessarily all referring to the same aspect.Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more aspects.

[0028] Embodiments described in the present disclosure may be implemented in wireless networking apparatuses, such as, without limitation, apparatuses utilizing Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile communications (GSM, 2G), GSM EDGE radio access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, 3G) based on basic wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), Long Term Evolution (LTE), LTE- Advanced, enhanced LTE (eLTE), 5G New Radio (5G NR), 5G Advance, 6G (and beyond) and 802.1 lax (Wi-Fi 6), among other wireless networking systems. The term ‘eLTE’ here denotes the LTE evolution that connects to a 5G core. LTE is also known as evolved UMTS terrestrial radio access (EUTRA) or as evolved UMTS terrestrial radio access network (EUTRAN).

[0029] The present disclosure may use the term “serving network device” to refer to a network node or network device (or a portion thereof) that services a UE. As used herein, the terms “transmit to,” “receive from,” and “cooperate with,” (and their variations) include communications that may or may not involve communications through one or more intermediate devices or nodes. The term “acquire” (and its variations) includes acquiring in the first instance or reacquiring after the first instance. The term “connection” may mean a physical connection or a logical connection.

[0030] The present disclosure uses 5G NR as an example of a wireless network and may use smartphones and / or extended reality headsets as an example of UEs. It is intended and shall be understood that such examples are merely illustrative, and the present disclosure is applicable to other wireless networks and user equipment.

[0031] FIG. 1 is a diagram depicting an example of wireless networking between a network system 100 and a user equipment (UE) 150. The network system 100 may include one or more network nodes 120, one or more servers 110, and / or one or more network equipment 130 (e.g., test equipment). The network nodes 120 will be described in more detail below. As used herein, the term “network apparatus” may refer to any component of the network system 100, such as the server 110, the network node 120, the network equipment 130, any component(s) of the foregoing, and / or any other component(s) of the network system 100. Examples of network apparatuses include, without limitation, apparatuses implementing aspects of 5G NR, among others. The present disclosure describes embodiments related to 5GNR and embodiments that involve aspectsdefined by 3rd Generation Partnership Project (3GPP). However, it is contemplated that embodiments relating to other wireless networking technologies are encompassed within the scope of the present disclosure.

[0032] The following description provides further details of examples of network nodes. In a 5G NR network, a gNodeB (also known as gNB) may include, e.g., a node that provides new radio (NR) user plane and control plane protocol terminations towards the UE and that is connected via a NG interface to the 5G core (5GC), e.g., according to 3GPP TS 38.300 V16.6.0 (2021-06) section 3.2, which is hereby incorporated by reference herein.

[0033] A gNB supports various protocol layers, e.g., Layer 1 (LI) - physical layer, Layer 2 (L2), and Layer 3 (L3).

[0034] The layer 2 (L2) of NR is split into the following sublayers: Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP) and Service Data Adaptation Protocol (SDAP), where, e.g.: o The physical layer offers to the MAC sublayer transport channels; o The MAC sublayer offers to the RLC sublayer logical channels; o The RLC sublayer offers to the PDCP sublayer RLC channels; o The PDCP sublayer offers to the SDAP sublayer radio bearers; o The SDAP sublayer offers to 5GC quality of service (QoS) flows; o Control channels include broadcast control channel (BCCH) and physical control channel (PCCH).

[0035] Layer 3 (L3) includes, e.g., radio resource control (RRC), e.g., according to 3GPP TS 38.300 V16.6.0 (2021-06) section 6, which is hereby incorporated by reference herein.

[0036] A gNB central unit (gNB-CU) includes, e.g., a logical node hosting, e.g., radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB or RRC and PDCP protocols of the en-gNB, that controls the operation of one or more gNB distributed units (gNB-DUs). The gNB-CU terminates the Fl interface connected with the gNB-DU. A gNB-CU may also be referred to herein as a CU, a central unit, a centralized unit, or a control unit.

[0037] A gNB Distributed Unit (gNB-DU) includes, e.g., a logical node hosting, e.g., radio link control (RLC), media access control (MAC), and physical (PHY) layers of the gNB or en- gNB, and its operation is partly controlled by the gNB-CU. One gNB-DU supports one or multiplecells. One cell is supported by only one gNB-DU. The gNB-DU terminates the Fl interface connected with the gNB-CU. A gNB-DU may also be referred to herein as DU or a distributed unit.

[0038] As used herein, the term “network node” may refer to any of a gNB, a gNB-CU, or a gNB-DU, or any combination of them. A RAN (radio access network) node or network node such as, e.g., a gNB, gNB-CU, or gNB-DU, or parts thereof, may be implemented using, e.g., an apparatus with at least one processor and / or at least one memory with processor-readable instructions (“program”) configured to support and / or provision and / or process CU and / or DU related functionality and / or features, and / or at least one protocol (sub-)layer of a RAN (radio access network), e.g., layer 2 and / or layer 3. Different functional splits between the central and distributed unit are possible. An example of such an apparatus and components will be described in connection with FIG. 5 below.

[0039] The gNB-CU and gNB-DU parts may, e.g., be co-located or physically separated. The gNB-DU may even be split further, e.g., into two parts, e.g., one including processing equipment and one including an antenna. A central unit (CU) may also be called baseband unit / radio equipment controller / cloud-RAN / virtual-RAN (BBU / REC / C-RAN / V-RAN), open-RAN (O- RAN), or part thereof. A distributed unit (DU) may also be called remote radio head / remote radio unit / radio equipment / radio unit (RRH / RRU / RE / RU), or part thereof. Hereinafter, in various example embodiments of the present disclosure, a network node, which supports at least one of central unit functionality or a layer 3 protocol of a radio access network, may be, e.g., a gNB-CU. Similarly, a network node, which supports at least one of distributed unit functionality or a layer 2 protocol of the radio access network, may be, e.g., a gNB-DU.

[0040] A gNB-CU may support one or multiple gNB-DUs. A gNB-DU may support one or multiple cells and, thus, could support a serving cell for a user equipment (UE) or support a candidate cell for handover, dual connectivity, and / or carrier aggregation, among other procedures.

[0041] The user equipment (UE) 150 may be or include a wireless or mobile device, an apparatus with a radio interface to interact with a RAN (radio access network), a smartphone, an in-vehicle apparatus, an loT device, or a M2M device, among other types of user equipment. Such UE 150 may include: at least one processor; and at least one memory including program code; where the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform certain operations, such as, e.g., RRCconnection to the RAN. An example of components of a UE will be described in connection with FIG. 5. In embodiments, the UE 150 may be configured to generate a message (e.g., including a cell ID) to be transmitted via radio towards a RAN (e.g., to reach and communicate with a serving cell). In embodiments, the UE 150 may generate and transmit and receive RRC messages containing one or more RRC PDUs (packet data units). Persons skilled in the art will understand RRC protocol as well as other procedures a UE may perform.

[0042] With continuing reference to FIG. 1, in the example of a 5G NR network, the network system 100 provides one or more cells, which define a coverage area of the network system 100. As described above, the network system 100 may include a gNB of a 5G NR network or may include any other apparatus configured to control radio communication and manage radio resources within a cell. As used herein, the term “resource” may refer to radio resources, such as a resource block (RB), a physical resource block (PRB), a radio frame, a subframe, a time slot, a sub-band, a frequency region, a sub-carrier, a beam, etc. In embodiments, the network node 120 may be called a base station.

[0043] FIG. 1 provides an example and is merely illustrative of a network system 100 and a UE 150. Persons skilled in the art will understand that the network system 100 includes components not illustrated in FIG. 1 and will understand that other user equipment may be in communication with the network system 100.

[0044] FIG. 2 is a block diagram of example components of the network system 100 of FIG. 1. A 5G NR network may be described as an example of the network system 100, and it is intended that aspects of the following description shall be applicable to other types of network systems, as well. The network system may operate in accordance with the signals and connections shown in FIG. 1 such that the UE 150 is in communication with the network system 100 through the radio access network 225. Additionally, the network system may be divided into user plane components and functions and control plane components and functions, as shown and described herein. Unless indicated otherwise, the terms “component”, “function”, and “service” may be used interchangeably herein, and they may refer to and be implemented by instructions executed by one or more processors.

[0045] Example functions of the components are described below. The example functions are merely illustrative, and it shall be understood that additional operations and functions may be performed by the components described herein. Additionally, the connections betweencomponents may be virtual connections over service-based interfaces such that any component may communicate with any other component. In this manner, any component may act as a service “producer,” for any other component that is a service “consumer,” to provide services for network functions.

[0046] For example, a core network 210 is described in the control plane of the network system. The core network 210 may include an authentication server function (AUSF) 211, an access and mobility function (AMF) 212, and a session management function (SMF) 213. The core network 210 may also include a network slice selection function (NSSF) 214, a network exposure function (NEF) 215, a network repository function (NRF) 216, and a unified data management function (UDM) 217, which may include a uniform data repository (UDR) 224.

[0047] Additional components and functions of the core network 210 may include an application function 218, policy control function (PCF) 219, network data analytics function (NWDAF) 220, analytics data repository function (ADRF) 221, management data analytics function (MDAF) 222, and operations and management function (0AM) 223.

[0048] The user plane includes the UE 150, a radio access network (RAN) 225, a user plane function (UPF) 226, and a data network (DN) 227. The RAN 225 may include one or more components described in connection with FIG. 1, such as one or more network nodes. However, the RAN 225 may not be limited to such components. The UPF 226 provides connection for data being transmitted over the RAN 225. The DN 226 identifies services from service providers, Internet access, and third party services, for example.

[0049] The AMF 212 processes connection and mobility tasks. The AUSF 211 receives authentication requests from the AMF 212 and interacts with UDM 217 to authenticate and validate network responses for determination of successful authentication. The SMF 213 conducts packet data unit (PDU) session management, as well as manages session context with the UPF 226.

[0050] The NSSF 214 may select a network slicing instance (NSI) and determine the allowed network slice selection assistance information (NSSAI). This selection and determination is utilized to set the AMF 212 to provide service to the UE 150. The NEF 215 secures access to network services for third parties to create specialized network services. The NRF 216 acts as a repository to store network functions to allow the functions to register with and discover each other.

[0051] The UDM 217 generates authentication vectors for use by the AUSF 211 and ADM 212 and provides user identification handling. The UDM 217 may be connected to the UDR 224 which stores data associated with authentication, applications, or the like. The AF 218 provides application services to a user (e.g., streaming services, etc.). The PCF 219 provides policy control functionality. For example, the PCF 219 may assist in network slicing and mobility management, as well as provide quality of service (QoS) and charging functionality.

[0052] The NWDAF 220 collects data (e.g., from the UE 150 and the network system) to perform network analytics and provide insight to functions that utilize the analytics in the providing of services. The ADRF 221 allows the storage, retrieval, and removal of data and analytics by consumers. The MDAF 222 provides additional data analytics services for network functions. The 0AM 223 provides provisioning and management processing functions to manage elements in or connected to the network (e.g., UE 150, network nodes, etc.).

[0053] FIG. 2 is merely an example of components of a network system, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the network system may include other components not illustrated in FIG. 2. In embodiments, the network system may not include every component illustrated in FIG. 2. In embodiments, the components and connections may be implemented with different connections than those illustrated in FIG. 2. Such and other embodiments are contemplated to be within the scope of the present disclosure.[1] As mentioned above, a user equipment (UE) provides reports to maintain the knowledge about the radio channel. These reports, in some cases, take the form of a channel state information (CSI) report and / or a sounding reference signal (SRS) report. In various embodiments, efficiency of signaling may be increased between the gNB and UE by avoiding excess signals.

[0054] In various embodiments, the UE transmits CSI / SRS in specific cases, even though the gNB may not require that information in those cases (e.g., in some cases, that information has no value for the network). By avoiding low value CSI and SRS UE transmission, various improvements may be attained (e.g., RF performance for other UEs due to less interference, saves UE battery, avoids wasted gNB processing and energy).

[0055] If the UE entirely avoids transmitting CSI / SRS then the network doesn't have the option to start processing the prior queued CSI / SRS when new data arrives after an interval without any data traffic.

[0056] Accordingly, described herein is a method to enable the NW and UE to more dynamically, with a decreased amount of signaling, exploit the model of the traffic pattern expected to further improve UE / NW performance. In other words, this invention exploits mutual knowledge of the NW and UE of the traffic pattern and proposes methods to apply autonomous UE (and NW) behavior to minimize NW coordination and signaling for CSI / SRS.

[0057] In various embodiments, described herein is a method for CSI SRS Prohibit / Skipping Policy based on Exchanged artificial intelligence machine learning (AIML) Traffic Prediction, so the NW can more precisely and dynamically adapt the UE configuration in response to the predicted traffic pattern while both avoiding excess signaling and benefitting from a more timely CSI, SRS reporting configuration.

[0058] In various embodiments, the gNB configures the UE with a set of rules that guide the UE on autonomously canceling / skipping of CSI and / or SRS reporting based on traffic prediction model exchange.[2] In various embodiments, these autonomous actions are known (e.g., implicitly) at the gNB and thus, the gNB can reuse the freed-up signaling and other resources (from the UE’s cancellation action) for example, for other UEs in the NW.

[0059] FIG. 3 is a diagram of an example embodiment of signals and operations among a gNB and a UE, according to one illustrated aspect of the disclosure. In various embodiments, the components depicted in FIG. 3 may correspond to similar components described above in FIGS. 1-2. It will be understood that a described signal may have associated operations and a described operation may have associated signals.

[0060] At operation 301, the NW and / or UE is configured to receive downlink (DL) (and / or uplink (UL)) data pattern or prediction information, In various embodiments, the gNB configures the UE to send an (Al) Anticipated Buffer Occupancy Report, where based on the report both gNB and / or UE can predict the future traffic pattern until a certain time (T) and with a certain confidence level (C). Alternatively, a fixed periodic reporting interval can be configured for sending this report.

[0061] In various embodiments, the signaling type used for this message is of semi-static type, (e.g., RRC message or MAC CE). In various embodiments, the interval time T shows how long the model will still have the confidence level greater or equal to C. In other words,the configuration tries to force the UE to send an updated report when the existing model starts to become invalid and diverge from the experienced traffic pattern (of a given traffic type).

[0062] At operation 302, the policy for autonomous cancellation of CSI reporting is configured. In various embodiments, the gNB sends the UE a policy set for autonomous cancellation of CSI reporting. This policy clarifies a set of rules and conditions to cancel less important CSI reporting at the UE side with implicit knowledge of the gNB. The policy may include (but not limited to) information of the confidence level of the predicted traffic pattern, rules for CSI report transmission skipping, prohibit interval time to not to skip CSI reporting.

[0063] At operation 303, the gNB transmits a CSI reporting configuration message to the UE and the UE receives the CSI reporting configuration message. In various embodiments, the gNB configures certain rules for CSI reporting (e.g. periodicity for a periodic CSI reporting scheme) with possible UL resource allocation for reporting them.

[0064] At operation 304, the gNB and the UE will exchange DL pattern information. For example, the gNB may transmit a DL data pattern information message to the UE and the UE receives the DL data pattern information message. In various embodiments, the gNB informs the UE of its latest Al Anticipated DL data pattern. This report maybe triggered by a timer or a change in a previous traffic pattern state. In another example, the UE may transmit a DL data pattern information message to the gNB and the gNB receives the UL data pattern information message. In various embodiments, the UE informs the gNB of its latest Al Anticipated DL data pattern. This report maybe triggered by a timer or a change in a previous traffic pattern state.

[0065] At operation 305, the UE updates the gNB’s pattern predication model. In various examples, the UE processes the gNB’s report and updates its local gNB’s pattern prediction model to enhance its accuracy. In aspects, the gNB may also update the DL pattern information and CSI reporting based on the pattern so that the NW knows if the NW can or cannot receive a CSI report at that time.

[0066] At operation 306, the UE determines a CSI reporting instance is approaching based upon the CSI reporting configuration. Accordingly, at operation 307, the UE checks the conditions of the autonomous CSI report cancellation policy for the upcoming reporting instance.

[0067] At operation 308, if the conditions for autonomous skipping are met, the UE skips the upcoming CSI measurement and consequently the UE autonomously skips CSI reporting. Invarious embodiments, the gNB is implicitly aware of the UE’s decision and may cancel any preallocated resources for the UE’s data reception purposes.

[0068] In various embodiments, the autonomous CSI reporting cancellation policy may configure a measurement prohibit timer that forbids the UE from doing CSI measurements and reporting them. Such a timer may start after the gNB Al Anticipated DL data Report or any other preconfigured condition / event.

[0069] In various embodiments, the autonomous CSI reporting cancellation policy may configure a data volume threshold where if the Al predictions is predicting a buffer size of less than the configured threshold, the CSI measurement and reporting can be cancelled.

[0070] In various embodiments, the gNB may configure the UE with additional rules allowing the UE to do CSI measurements and reporting in case the Al predictions fail / not accurate enough based on parameters from operation 301.

[0071] In various embodiments, the gNB may reconfigure the CSI reporting configuration after operation 305 (when it updates its local DL pattern prediction model) to better fit the updated traffic pattern and may be performed similar to the message sent at operation 303.

[0072] The operations of FIG. 3 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include other operations not illustrated in FIG. 3. In embodiments, the operations may not include every operation illustrated in FIG. 3. In embodiments, the operations may be implemented in a different order than that illustrated in FIG. 3. Such and other embodiments are contemplated to be within the scope of the present disclosure. Persons of skill in the art will appreciate that, although various example components are described as perform various functions, other components may perform those functions described in FIG. 3.

[0073] FIG. 4 is a diagram of an example embodiment of signals and operations among a gNB and a UE, according to one illustrated aspect of the disclosure. In various embodiments, the components depicted in FIG. 4 may correspond to similar components described above in FIGS. 1-2. It will be understood that a described signal may have associated operations and a described operation may have associated signals.

[0074] At operation 401, the UE is configured to send buffer occupancy pattern information. In various embodiments, the gNB configures the UE to send an Al Anticipated Buffer Occupancy Report, where based on the report both gNB and / or UE can predict the future traffic pattern untila certain time (T) and with a certain confidence level (C). In various embodiments, a fixed periodic reporting interval can be configured for sending this report. In various embodiments, a fixed periodic reporting interval can be configured for sending this report. In various embodiments, the signaling type used for this message is of semi-static type, e.g., RRC message. In various embodiments, the interval time T shows how long the model with still have the confidence level greater or equal to C. In other words, the configuration tries to force the UE to send an updated report when the existing model starts to become invalid and diverge from the experienced traffic pattern.

[0075] At operation 402, the policy for autonomous cancellation of SRS transmission is configured. In various embodiments, the gNB sends a policy set for autonomous cancellation of SRS transmission. This policy clarifies a set of rules and conditions to cancel one or more of the upcoming SRS transmission occasions at the UE side with implicit knowledge of the gNB. The policy may include (and not limited to) information of the confidence level of the predicted traffic pattern, Buffer size threshold, prohibit timer.

[0076] At operation 403, the gNB transmits an SRS transmission configuration message to the UE and the UE receives the SRS transmission configuration message. In various embodiments, the gNB configures the UE with SRS transmission configurations.

[0077] At operation 404, the UE transmits a buffer occupancy pattern information message to the gNB and the gNB receives the buffer occupancy pattern information message. In various embodiments the UE informs the gNB of its latest Al Anticipated Buffer Occupancy Report. This report maybe triggered by a timer or a change in a previous traffic pattern state. In aspects, a message prediction of UL or DL traffic may also be generated by either or both of the UE and the gNB.

[0078] At operation 405, the gNB processes the UE’s report and updates its local UE’s pattern prediction model to enhance its accuracy.

[0079] At operation 406, the UE determines SRS transmission event is approaching based upon the SRS transmission configuration. Accordingly, at operation 407, the UE checks the conditions of the autonomous SRS transmission cancellation policy for the upcoming SRS transmission.

[0080] At operation 408, if the conditions for skipping are met, the UE autonomously cancels the SRS transmission. In various embodiments, the UE cancels the transmission autonomouslyand refrains from sending data in the granted UL resources, and the gNB is implicitly aware of the UE’s decision.

[0081] In various embodiments, the autonomous cancellation of SRS transmission policy may configure a transmission prohibit timer that forbids the UE from sending SRS. Such a timer may start after the UE Al Anticipated UL data Report or any other preconfigured condition / event.

[0082] In various embodiments, the autonomous cancellation of SRS transmission policy may configure a data volume threshold where if the Al predictions is predicting a buffer size of less than the configured threshold, the SRS transmission can be cancelled.

[0083] In various embodiments, the gNB may configure the UE with additional rules allowing the UE to send SRS in case the Al predictions fail / not accurate enough based on operation 401 parameters.

[0084] In various embodiments, the gNB may configure the UE with additional rules for skipping SRS in case no scheduling request was sent within a preconfigured period of time T.

[0085] In various embodiments, the gNB may reconfigure the SRS transmission configuration after operation 405 (when it updates its local UL pattern prediction model) to better fit the updated traffic pattern. This can be done similar to the message sent at operation 403.

[0086] The operations of FIG. 4 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include other operations not illustrated in FIG. 4. In embodiments, the operations may not include every operation illustrated in FIG. 4. In embodiments, the operations may be implemented in a different order than that illustrated in FIG. 4. Such and other embodiments are contemplated to be within the scope of the present disclosure. Persons of skill in the art will appreciate that, although various example components are described as perform various functions, other components may perform those functions described in FIG. 4.

[0087] The following describes operations from the perspective of a UE. From such a perspective, a method may include: receiving, by a user equipment (UE), a first message from a network apparatus, the first message including configuration information for autonomous cancellation of sounding reference signal (SRS) reporting; determining, by the UE, upon an SRS reporting instance approaching, to transmit an SRS report to the network apparatus based on one or more conditions for cancelling SRS reporting included in the configuration information, the oneor more conditions based on an exchanged traffic prediction model; and transmitting, by the UE, an SRS report to the network apparatus based upon the one or more conditions not being met.

[0088] FIG. 5 is a block diagram of a wireless station or node (e.g., UE, user device, AP, BS, eNB, gNB, RAN node, network node, TRP, or other node) 500, according to one illustrated aspect of the present disclosure. The wireless station 500 may include, for example, one or more (e.g., two as shown in FIG. 5) RF (radio frequency) or wireless transceivers 502A, 502B, where each wireless transceiver includes a transmitter to transmit signals and a receiver to receive signals. The wireless station also includes a processor or control unit / entity (controller) 504 to execute instructions or software and control transmission and receptions of signals, and a memory 506 to store data and / or instructions.

[0089] Processor 504 may also make decisions or determinations, generate frames, packets or messages for transmission, decode received frames or messages for further processing, and other tasks or functions described herein. Processor 504, which may be a baseband processor, for example, may generate messages, packets, frames or other signals for transmission via wireless transceiver 602 (502A or 502B). Processor 504 may control transmission of signals or messages over a wireless network, and may control the reception of signals or messages, etc., via a wireless network (e.g., after being down-converted by wireless transceiver 602, for example). Processor 504 may be programmable and capable of executing software or other instructions stored in memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above. Processor 504 may be (or may include), for example, hardware, programmable logic, a programmable processor that executes software or firmware, and / or any combination of these. Using other terminology, processor 504 and transceiver 602 together may be considered as a wireless transmitter / receiver system, for example.

[0090] In addition, referring to FIG. 5, a controller (or processor) 508 may execute software and instructions, and may provide overall control for the station 500, and may provide control for other systems not shown in FIG. 5, such as controlling input / output devices (e.g., display, keypad), and / or may execute software for one or more applications that may be provided on wireless station 500, such as, for example, an email program, audio / video applications, a word processor, a Voice over IP application, or other application or software.

[0091] In addition, a storage medium may be provided that includes stored instructions, whichwhen executed by a controller or processor may result in the processor 504, or other controller or processor, performing one or more of the functions or tasks described above.

[0092] According to another example embodiment, RF or wireless transceiver(s) 502A / 502B may receive signals or data and / or transmit or send signals or data. Processor 504 (and possibly transceivers 502A / 502B) may control the RF or wireless transceiver 502A or 502B to receive, send, broadcast or transmit signals or data.

[0093] Example embodiments are provided or described for each of the example methods, including: An apparatus (e.g., 500, FIG. 5) including means (e.g., processor 504, RF transceivers 502A and / or 502B, and / or memory 506, in FIG. 5) for carrying out any of the methods; a non- transitory computer-readable storage medium (e.g., memory 506, FIG. 5) comprising instructions stored thereon that, when executed by at least one processor (processor 504, FIG. 5), are configured to cause a computing system (e.g., 500, FIG. 5) to perform any of the example methods; and an apparatus (e.g., 500, FIG. 5) including at least one processor (e.g., processor 504, FIG. 5), and at least one memory (e.g., memory 506, FIG. 5) including computer program code, the at least one memory (506) and the computer program code configured to, with the at least one processor (504), cause the apparatus (e.g., 500) at least to perform any of the example methods.

[0094] Further embodiments of the present disclosure include the following examples.

[0095] Example 1.1 A user equipment (UE), comprising: means for receiving, by a user equipment (UE), a first message from a network apparatus, the first message including configuration information for autonomous cancellation of sounding reference signal (SRS) reporting; means for determining, by the UE, upon an SRS reporting instance approaching, to transmit an SRS report to the network apparatus based on one or more conditions for cancelling SRS reporting included in the configuration information, the one or more conditions based on an exchanged traffic prediction model; and means for transmitting, by the UE, an SRS report to the network apparatus based upon the one or more conditions not being met.

[0096] Example 1.2. The UE of Example 1.1, wherein the one or more conditions include at least one of: a confidence level of a predicted traffic pattern, a buffer size threshold, and a prohibit internal time to not skip SRS reporting.

[0097] Example 1.3. The UE of any of Examples 1.1 or 1.2, wherein the autonomous cancellation of SRS reporting configures a transmission prohibit timer.

[0098] Example 1.4. The UE of any of Examples 1.1 to 1.3, wherein the autonomous cancellation of SRS reporting configures a data volume threshold.

[0099] Example 1.5. The UE of Example 1.4, wherein SRS reporting is cancelled if a buffer size is predicted to be less than the data volume threshold.

[0100] Example 1.6. The UE of any of Examples 1.1 to 1.5, further comprising: means for receiving, by the UE, a second message from a network apparatus, the second message including buffer occupancy information for autonomous cancellation of SRS reporting.

[0101] Example 1.7. The UE of Example 1.8, further comprising: means for updating the exchanged traffic prediction model based on the second message.

[0102] Example 1.8. The UE Example 1.7, further comprising: means for reevaluating, by the UE, the one or more conditions based on the updated exchanged traffic prediction model.

[0103] Example 1.9. A processor-readable medium storing instructions which, when executed by at least one processor of a UE apparatus, cause the UE apparatus at least to perform a method as in any one of the Examples 1.1 to 1.8.

[0104] Example 1.10. A network apparatus, comprising: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, causes the network apparatus at least to perform a method as in any one of Examples 1.1 to 1.8.

[0105] The embodiments and aspects disclosed herein are examples of the present disclosure and may be embodied in various forms. For instance, although certain embodiments herein are described as separate embodiments, each of the embodiments herein may be combined with one or more of the other embodiments herein. Specific structural and functional details disclosed herein are not to be interpreted as limiting, but as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present disclosure in virtually any appropriately detailed structure. Like reference numerals may refer to similar or identical elements throughout the description of the figures.

[0106] The phrases “in an aspect,” “in aspects,” “in various aspects,” “in some aspects,” or “in other aspects” may each refer to one or more of the same or different aspects in accordance with this present disclosure. The phrase “a plurality of’ may refer to two or more.

[0107] In various embodiments, the terms “first message” and “second message”, as well as any subsequent messages may refer to any messages that are transmitted or received in an order and are not necessarily limited to any particular message.

[0108] The phrases “in an embodiment,” “in embodiments,” “in various embodiments,” “in some embodiments,” or “in other embodiments” may each refer to one or more of the same or different embodiments in accordance with the present disclosure. A phrase in the form “A or B” means “(A), (B), or (A and B).” A phrase in the form “at least one of A, B, or C” means “(A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C) ”

[0109] Any of the herein described methods, programs, algorithms or codes may be converted to, or expressed in, a programming language or computer program. The terms “programming language” and “computer program,” as used herein, each include any language used to specify instructions to a computer, and include (but is not limited to) the following languages and their derivatives: Assembler, Basic, Batch files, BCPL, C, C+, C++, Delphi, Fortran, Java, JavaScript, machine code, operating system command languages, Pascal, Perl, PL1, Python, scripting languages, Visual Basic, metalanguages which themselves specify programs, and all first, second, third, fourth, fifth, or further generation computer languages. Also included are database and other data schemas, and any other meta- languages. No distinction is made between languages which are interpreted, compiled, or use both compiled and interpreted approaches. No distinction is made between compiled and source versions of a program. Thus, reference to a program, where the programming language could exist in more than one state (such as source, compiled, object, or linked) is a reference to any and all such states. Reference to a program may encompass the actual instructions and / or the intent of those instructions.

[0110] While aspects of the present disclosure have been shown in the drawings, it is not intended that the present disclosure be limited thereto, as it is intended that the present disclosure be as broad in scope as the art will allow and that the specification be read likewise. Therefore, the above description should not be construed as limiting, but merely as exemplifications of particular aspects. Those skilled in the art will envision other modifications within the scope and spirit of the claims appended hereto.

Claims

WHAT IS CLAIMED IS:

1. A method, comprising: receiving, by a user equipment (UE), a first message from a network apparatus, the first message including configuration information for autonomous cancellation of sounding reference signal (SRS) reporting; determining, by the UE, upon an SRS reporting instance approaching, to transmit an SRS report to the network apparatus based on one or more conditions for cancelling SRS reporting included in the configuration information, the one or more conditions based on an exchanged traffic prediction model; and transmitting, by the UE, an SRS report to the network apparatus based upon the one or more conditions not being met.

2. The method of claim 1, wherein the one or more conditions include at least one of: a confidence level of a predicted traffic pattern, a buffer size threshold, and a prohibit internal time to not skip SRS reporting.

3. The method of any of claims 1 to 2, wherein the autonomous cancellation of SRS reporting configures a transmission prohibit timer.

4. The method of any of claims 1 to 3, wherein the autonomous cancellation of SRS reporting configures a data volume threshold.

5. The method of claim 4, wherein SRS reporting is cancelled if a buffer size is predicted to be less than the data volume threshold.

6. The method of any of claims 1 to 5, wherein the method further comprises receiving, by the UE, a second message from a network apparatus, the second message including buffer occupancy information for autonomous cancellation of SRS reporting.

7. The method of claim 6, wherein the method further comprises updating the exchanged traffic prediction model based on the second message.

8. The method of claim 7, further comprising reevaluating, by the UE, the one or more conditions based on the updated exchanged traffic prediction model.

9. A processor-readable medium storing instructions which, when executed by at least one processor of a UE apparatus, cause the UE apparatus at least to perform a method as in any one of claims 1 to 8.

10. A network apparatus, comprising: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, causes the network apparatus at least to perform a method as in any one of 1 to 8.

11. A user equipment (UE) apparatus, comprising: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, causes the UE apparatus at least to perform: receiving, by a user equipment (UE), a first message from a network apparatus, the first message including configuration information for autonomous cancellation of sounding reference signal (SRS) reporting; determining, by the UE, upon an SRS reporting instance approaching, to transmit an SRS report to the network apparatus based on one or more conditions for cancelling SRS reporting included in the configuration information, the one or more conditions based on an exchanged traffic prediction model; and transmitting, by the UE, an SRS report to the network apparatus based upon the one or more conditions not being met.

12. The UE apparatus of claim 11, wherein the one or more conditions include at least one of: a confidence level of a predicted traffic pattern, a buffer size threshold, and a prohibit internal time to not skip SRS reporting.

13. The UE apparatus of any of claims 11 or 12, wherein the autonomous cancellation of SRS reporting configures a transmission prohibit timer.

14. The UE apparatus of any of claims 11 to 13, wherein the autonomous cancellation of SRS reporting configures a data volume threshold.

15. The UE apparatus of claim 14, wherein SRS reporting is cancelled if a buffer size is predicted to be less than the data volume threshold.

Images