Methods for user equipment, user equipment, and integrated circuits

Abstract

This disclosure relates to a method, user equipment (UE), and integrated circuit for receiving data transmitted via a wireless network. The method includes: executing an application for receiving data from the network; sending UE assistance information to the network, wherein the UE assistance information corresponds to a traffic pattern of the data received from the network for the application; entering a Radio Resource Control (RRC) inactive state; and receiving the data from the network while in the RRC inactive state.

Description

Background Technology

[0001] User equipment (UE) can connect to networks (e.g., LTE networks, 5G New Radio (NR) networks, etc.). When connected to a network, the UE can receive data related to various applications running on the UE. In some cases, this data can be real-time audio or video HTTP traffic. In fact, current estimates suggest that 40%–50% of cellular data traffic is this type of traffic, and it is estimated that this number will grow over time as more users stream audio and video content to their mobile devices.

[0002] To support this traffic, the UE continuously uses power to maintain channel readiness in anticipation of new data arrivals. Specifically, the UE must monitor the Physical Downlink Control Channel (PDCCH) to determine when the network is transmitting DL traffic. Several techniques have been developed to attempt to conserve power, such as DRX (Discontinuous Receive). However, these techniques do not significantly extend UE battery life during streaming operations. Furthermore, 5G NR is expected to use significantly more power during these operations, as the UE will have to monitor a wider frequency range. Summary of the Invention

[0003] According to some exemplary embodiments, a method is performed by a user equipment (UE) connected to a network. The method includes: executing an application to receive data from the network; sending UE assistance information to the network, wherein the UE assistance information corresponds to a traffic pattern of the data received from the network for the application; entering a Radio Resource Control (RRC) inactive state; and receiving the data from the network while in the RRC inactive state.

[0004] Another exemplary embodiment includes a user equipment (UE) having a transceiver and a processor. The transceiver is configured to communicate with a network. The processor is configured to perform operations including: executing an application to receive data from the network; sending UE assistance information to the network, wherein the UE assistance information corresponds to a traffic pattern of the data received from the network for the application; entering a Radio Resource Control (RRC) inactive state; and receiving the data from the network while in the RRC inactive state.

[0005] Other exemplary embodiments include an integrated circuit having: circuitry configured to transmit UE assistance information to a network, wherein the UE assistance information corresponds to a traffic pattern for data received from the network by an application; circuitry configured to enter a Radio Resource Control (RRC) inactive state; and circuitry configured to receive the data from the network while in the RRC inactive state. Attached Figure Description

[0006] Figure 1 Exemplary network arrangements according to various exemplary implementations are shown.

[0007] Figure 2 Exemplary UEs according to various exemplary implementations are shown.

[0008] Figure 3 The data traffic pattern and an example of current PDCCH monitoring for that traffic pattern are shown.

[0009] Figure 4 A first exemplary signaling diagram is shown, illustrating how a UE can receive DL traffic from the network while in an RRC inactive state, according to various exemplary implementations.

[0010] Figure 5 A second exemplary signaling diagram is shown, illustrating how a UE can receive DL traffic from the network while in an RRC inactive state, according to various exemplary implementations.

[0011] Figure 6 A third exemplary signaling diagram is shown, illustrating how a UE can receive DL traffic from the network while in an RRC inactive state, according to various exemplary implementations.

[0012] Figure 7 A fourth exemplary signaling diagram is shown, illustrating how a UE can receive DL traffic from the network while in an RRC inactive state, according to various exemplary implementations.

[0013] Figure 8 A fifth exemplary signaling diagram is shown, illustrating how a UE can receive DL traffic from the network while in an RRC inactive state, according to various exemplary implementations.

[0014] Figure 9 A sixth exemplary signaling diagram is shown, illustrating a UE receiving DL traffic from the network while in an RRC inactive state, according to various exemplary implementations. Detailed Implementation

[0015] The exemplary embodiments can be further understood with reference to the following description and related figures, wherein similar elements have the same reference numerals. The exemplary embodiments relate to receiving data from the network without requiring monitoring of the Physical Downlink Control Channel (PDCCH). More specifically, the exemplary embodiments allow the UE to remain in an RRC inactive state while receiving DL data. Because the UE remains in an RRC inactive state, the UE does not need to monitor the PDCCH, thereby saving power associated with monitoring.

[0016] Throughout this specification, the terms "DL data" and "streaming data" are used interchangeably to refer to data being transmitted from the network to the UE. While exemplary embodiments are described with respect to audio and / or video streaming data, those skilled in the art will understand that the exemplary embodiments can be used for any type of data during downlink (DL). The exemplary embodiments can be used when DL data traffic patterns are generally predictable, as will be described in more detail below.

[0017] Furthermore, throughout this specification, exemplary embodiments are described with reference to downlink (DL) data (e.g., data transmitted from the network to the UE). However, those skilled in the art will understand that exemplary embodiments can also be applied to uplink (UL), such as data transmitted from the UE to the network. Those skilled in the art will understand modifications to implement exemplary embodiments into the UL.

[0018] The exemplary embodiments are described with respect to the UE. However, the use of the UE is provided for illustrative purposes only. The exemplary embodiments can be used with any electronic component configured with hardware, software, and / or firmware for exchanging information (e.g., control information) and / or data with a network. Therefore, the UE described herein is used to represent any suitable electronic device.

[0019] Furthermore, exemplary implementations are described with reference to networks serving as LTE or 5G NR networks. However, it should be understood that, based on the operating principles described herein for LTE and / or 5G NR networks, the exemplary implementations can be implemented in any network (cellular or non-cellular).

[0020] The exemplary implementation is also described with reference to PDCCH. In LTE and 5G NR, PDCCH carries downlink control information (DCI) from the network to the UE. For example, PDCCH provides the UE with information to understand when (time) and where (frequency) DL traffic is being sent to the UE. It should be understood that the term PDCCH is used as a reference to the exemplary implementation being described with reference to LTE and / or 5G networks. Other types of networks may have similar concepts described with different names. In the context of the exemplary implementation, monitoring of PDCCH for DL ​​data is being eliminated or significantly reduced.

[0021] Figure 1An exemplary network arrangement 100 according to various exemplary embodiments is shown. The exemplary network arrangement 100 includes a UE 110. Those skilled in the art will understand that the UE 110 can be any type of electronic component configured to communicate via a network, such as components of a connected car, a mobile phone, tablet, smartphone, phablet, embedded device, wearable device, Internet of Things (IoT) device, etc. It should also be understood that a practical network arrangement can include any number of UEs used by any number of users. Therefore, for illustrative purposes, only an example with one UE 110 is provided.

[0022] UE 110 can communicate directly with one or more networks. In the example of network configuration 100, the networks with which UE 110 can communicate wirelessly are 5G NR radio access network (5G NR-RAN) 120, LTE radio access network (LTE-RAN) 122, and wireless local area network (WLAN) 124. UE 110 can also communicate with other types of networks, and UE 110 can also communicate with networks via wired connections. Therefore, UE 110 may include a 5G NR chipset communicating with 5G NR-RAN 120, an LTE chipset communicating with LTE-RAN 122, and an ISM chipset communicating with WLAN 124.

[0023] 5G NR-RAN 120 and LTE-RAN 122 can be parts of cellular networks that can be deployed by cellular providers (e.g., Verizon, AT&T, Sprint, T-Mobile, etc.). These networks 120, 122 can include, for example, cells or base stations (NodeB, eNodeB, HeNB, eNB, gNB, gNodeB, macrocell base stations, microcell base stations, small cell base stations, femtocell base stations, etc.) configured to send and receive traffic from UEs equipped with appropriate cellular chipsets. WLAN 124 can include any type of wireless local area network (WiFi, hotspot, IEEE 802.11x network, etc.).

[0024] UE 110 can connect to the 5G NR-RAN via gNB 120A. gNB 120A can be configured with the necessary hardware (e.g., antenna array), software, and / or firmware to perform massive MIMO functionality. Massive MIMO can refer to a base station configured to generate multiple beams for multiple UEs. Reference to a single gNB 120A is for illustrative purposes only. Exemplary implementations can be applied to any suitable number of gNBs. UE 110 can also connect to LTE-RAN 122 via eNB 122A.

[0025] Those skilled in the art will understand that any relevant process can be performed to connect UE 110 to 5G NR-RAN 120 and LTE-RAN 122. For example, as discussed above, 5G NR-RAN 120 and LTE-RAN 122 can be associated with specific cellular providers where UE 110 and / or its users have contract and credential information (e.g., stored on a SIM card). Upon detecting the presence of 5G NR-RAN 120, UE 110 can transmit the corresponding credential information to associate with 5G NR-RAN 120. More specifically, UE 110 can be associated with specific base stations (e.g., gNB 120A of 5G NR-RAN 120 and eNB 122A of LTE-RAN 122).

[0026] In addition to networks 120, 122, and 124, network deployment 100 also includes a cellular core network 130, an Internet 140, an IP Multimedia Subsystem (IMS) 150, and a network services backbone 160. The cellular core network 130 can be viewed as an interconnected set of components that manage the operation and traffic of the cellular network. The cellular core network 130 also manages the traffic flowing between the cellular network and the Internet 140. The IMS 150 can generally be described as an architecture for delivering multimedia services to the UE 110 using IP protocols. The IMS 150 can communicate with the cellular core network 130 and the Internet 140 to provide multimedia services to the UE 110. The network services backbone 160 communicates directly or indirectly with the Internet 140 and the cellular core network 130. The network services backbone 160 can generally be described as a set of components (e.g., servers, network storage deployments, etc.) that implement a set of services that can be used to extend the functionality of the UE 110 to communicate with various networks.

[0027] UE 110 can be configured to be in one of several different operating states. One operating state can be characterized as an RRC idle state, another as an RRC inactive state, and yet another as an RRC connected state. RRC refers to the Radio Resource Control (RRC) protocol. Those skilled in the art will understand that when UE 110 is in the RRC connected state, UE 110 and 5G NR-RAN 120 and / or LTE-RAN 122 can be configured to exchange information and / or data. The exchange of information and / or data allows UE 110 to perform functionality available via the network connection. Furthermore, those skilled in the art will understand that when UE 110 is in the RRC idle state, UE 110 is typically not exchanging data with the network, and radio resources are not being allocated to UE 110 within the network. In the RRC inactive state, UE 110 maintains the RRC connection while minimizing signaling and power consumption. However, when UE 110 is in an RRC idle state or an RRC inactive state, UE 110 can monitor information and / or data transmitted by the network. Throughout this specification, these terms are generally used to describe the states that UE 110 can be in when connected to any network and the states exhibiting the aforementioned characteristics of RRC idle, RRC connected, and RRC inactive states. As will be described in more detail below, an exemplary embodiment may allow UE 110 to receive DL traffic when in an RRC inactive state.

[0028] Figure 2 An exemplary UE 110 according to various exemplary embodiments is shown. Reference will be made to... Figure 1 The network layout 100 is used to describe UE 110. UE 110 may include a processor 205, a memory layout 210, a display device 215, an input / output (I / O) device 220, a transceiver 225, and other components 230. Other components 230 may include, for example, a SIM card, an embedded SIM (eSIM), an audio input device, an audio output device, a power source, a data acquisition device, and ports for electrically connecting UE 110 to other electronic devices.

[0029] Processor 205 can be configured to execute multiple engines of UE 110. For example, an engine may include DL traffic engine 235. DL traffic engine 235 can be used to coordinate DL traffic with the network, thereby allowing UE 110 to remain in an RRC inactive state and receive DL traffic without needing to monitor the PDCCH. Several signaling diagrams are provided below to illustrate various exemplary signaling between UE 110 and the network (5G NR-RAN 120 or LTE-RAN 122) that facilitate UE 110 receiving DL traffic while in an RRC inactive state. As part of the signaling, UE 110 (e.g., DL traffic engine 235) can provide UE assistance information to the network to help the network format DL data for download, enabling UE 110 to receive DL data in an RRC inactive state. UE assistance information will be described in more detail below when describing the signaling diagrams.

[0030] The engines described above, each acting as an application (e.g., a program) executed by processor 205, are merely exemplary. The functionality associated with the engines may also be represented as a separate integrated component of UE 110, or as a modular component coupled to UE 110, such as an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. Engines may also be embodied as a single application or multiple separate applications. Furthermore, in some UEs, the functionality described for processor 205 is distributed among two or more processors, such as a baseband processor and an application processor. Exemplary implementations can be implemented according to any of these or other configurations of the UE.

[0031] Memory arrangement 210 may be a hardware component configured to store data related to operations performed by UE 110. Display device 215 may be a hardware component configured to display data to a user, while I / O device 220 may be a hardware component enabling user input. Display device 215 and I / O device 220 may be separate components or may be integrated together (such as a touchscreen). Transceiver 225 may be a hardware component configured to establish connections with 5G NR-RAN 120, WLAN 122, etc. Therefore, transceiver 225 may operate on multiple different frequencies or channels (e.g., consecutive frequency groups).

[0032] Figure 3 An example of data traffic pattern 300 and current PDCCH monitoring 340 for this traffic pattern is shown. As mentioned above, this data traffic pattern is an example of audio and / or video data being streamed to UE 110. However, as mentioned above, the exemplary implementation is not limited to this type of data. Figure 3The upper curve 300 shows the initial large download for buffering purposes, as indicated by region 310 of curve 300. Data is then downloaded in a prescribed pattern based on radio conditions. This traffic pattern is typically a short burst of data followed by a period of no data transmission. Data bursts can have various characteristics. For example, the first set of data bursts 320 is the longest-lasting data burst. In terms of data volume, data burst 330 is a peak data burst. The remainder of the data burst varies in both duration and volume.

[0033] Bottom graph 340 illustrates PDCCH monitoring in the typical manner of downloading data during RRC connected state. As can be seen from this bottom graph 340, even when DRX is in use, UE 110 continuously monitors the PDCCH, thus consuming significant power. In contrast, the exemplary implementation minimizes the need for UE 110 to monitor the PDCCH while receiving DL data. For example, when UE 110 is in an RRC inactive state (regardless of whether UE 110 is receiving DL data or not), UE 110 is not monitoring the PDCCH. By reducing the amount of time spent monitoring the PDCCH, UE 110 is reducing the power consumption associated with this monitoring.

[0034] Figure 4 A first exemplary signaling diagram 400 is shown, according to various exemplary embodiments, allowing UE 110 to receive DL traffic from network 405 in an RRC inactive state. Figure 4 In signaling diagram 400, network 405 can be considered as 5G NR-RAN 120 or LTE-RAN 122, and UE 110 can connect to one of gNB 120A or eNB 122A. (Refer to...) Figure 4 In the exemplary implementation described, UE assistance information is provided to network 405 during a random access channel (RACH) procedure performed between network 405 and UE 110.

[0035] UE 110 can be considered initially in RRC inactive state 410. As described below, UE 110 may be receiving DL traffic while in this state. Network 405 will send a paging 420 to UE 110. Paging 410 may be sent in response to a specified action (e.g., network 405 has a voice call to UE 110, UE 110 has sent a scheduling request (SR) to network 405, etc.) or at a predetermined scheduled time. Because network 405 will understand that DL data was sent while UE 110 is in RRC inactive state, network 405 may periodically request UE 110 to enter RRC connected state to ensure that the parameters used to deliver DL data during RRC inactive state (e.g., UE assistance information) are correct. UE assistance information and the manner in which it is provided to network 405 will be discussed in more detail below.

[0036] In response to paging 410, UE 110 will send a RACH request 430 to network 405. RACH request 430 is a request from UE 110 to establish an RRC connection state with network 405. Those skilled in the art will understand the information typically provided in RACH request 430. However, in addition to the information typically provided in RACH request 430, additional information may be provided to network 405 to allow network 405 to continue streaming data to UE 110 when UE 110 transitions back to an RRC inactive state. Throughout this specification, this additional information will be referred to as UE auxiliary information. UE auxiliary information is a set of data describing the characteristics of the traffic pattern of DL data. As described above, the exemplary embodiment relates to network 405 sending DL data when UE 110 is in an RRC inactive state. For these transmissions to be successful, network 405 should send DL data in a manner that UE 110 expects DL data to be sent. UE 110 will understand the traffic pattern for the specific application being executed on UE 110, for example, for... Figure 3 The graph 300 shows an exemplary traffic pattern for a streaming application. UE 110 can then provide network 405 with UE assistance information corresponding to the known traffic pattern, allowing network 405 to deliver DL data based on the UE assistance information. An exemplary method for determining the traffic pattern for an application will be described in more detail below.

[0037] UE assistance information may be included in, for example, the Media Access Control (MAC) control element (CE) included in RACH request 430. UE assistance information may include minimum license size, minimum license frequency, and minimum license duration. It should be understood that these parameters are merely exemplary, and other types of information may also be included in the UE assistance information to provide network 405 with information regarding the transmission of DL data. (See above reference...) Figure 3 As described, UE 110 is generally aware of the DL traffic pattern. Therefore, UE 110 can provide UE assistance information to network 405, enabling the network to format DL data transmission in a manner that allows UE 110 to receive DL data when in an RRC inactive state.

[0038] Before discussing UE assistance information in more detail, it should be noted that traffic patterns can be determined in various ways. In the first example, UE 110 may have experience with a specific application (e.g., a video streaming service) and understand the traffic patterns that will occur based on the application's previous usage. In the second example, UE 110 may allow the application to stream data in a normal manner (e.g., using RRC connection status, including monitoring PDCCH) over a period of time to determine the traffic pattern currently used by the application, and after determining the current traffic pattern, UE 110 may switch to use an exemplary implementation. In the third example, applications may be grouped into multiple application types (e.g., a video streaming application may be of type one, an audio streaming application (podcast, music streaming) may be of type two, etc.), and UE 110 may understand the traffic pattern for each application type. Therefore, when an application is launched, UE 110 may understand the associated application type and the traffic pattern associated with that application type. In the fourth example, UE 110 may concentrate resources on the traffic pattern of the currently running application. Furthermore, other factors such as the quality of the current radio connection and network type can also affect the traffic pattern for an application.

[0039] Therefore, once UE 110 knows the traffic pattern, UE 110 can provide UE assistance information to network 405, for example, via MAC CE of RACH request 430. Also as described above, the UE assistance information may include minimum grant size, minimum grant frequency, and minimum grant duration. Providing these parameters allows network 405 to send streaming data to UE 110 in a manner that allows UE 110 to listen for and receive data when UE 110 is in an RRC inactive state. Providing a minimum grant size allows network 405 to understand the minimum grant size required to provide streaming data to UE 110. For example, if the exemplary traffic pattern shown in graph 300 is considered the current traffic pattern, UE 110 can set the minimum grant size to adapt to... Figure 3 The maximum data burst is shown as data burst 330. The minimum grant frequency can be based on the time between each data burst. The minimum grant duration can be based on the longest duration of a data burst. For example, as... Figure 3 As shown, data bursts 320 have peak durations, even though these bursts are not the largest bursts in terms of data.

[0040] In response to RACH request 430, network 405 can provide RACH response 440, which includes uplink (UL) authorization for UE 110 to send data to the network. Upon receiving RACH response 440, UE 110 can use the UL authorization provided in RACH response 440 to send data 450 to network 405. Network 405 can provide HARQ ACK 460 to indicate that network 405 has received data 450. Data 450 and HARQ ACK 460 are shown in dashed lines because multiple exchanges of data and HARQ ACK may occur when UE 110 is in RRC connected state. After sending and acknowledging UL data 450, UE 110 can transition back to RRC inactive state 470.

[0041] However, even though UE 110 is in RRC inactive state 470, network 405 can continue to send DL data (e.g., streaming data) to UE 110 based on the information provided to the network in RACH request 430. As described above, in RRC inactive state, UE 110 can continue to monitor network 405 in a more passive manner compared to when it is in RRC connected state or RRC idle state. This monitoring may include monitoring the data channel but not the PDCCH. Because UE 110 has already provided UE assistance information to network 405 (e.g., in RACH request 430), UE 110 will understand when data bursts for streaming data will be sent by network 405. Therefore, UE 110 can receive DL data in RRC inactive state without wasting power by constantly monitoring the PDCCH.

[0042] Furthermore, while the exemplary embodiments described above have been referenced to UE 110 executing a single streaming application, it should be understood that UE 110 can operate other applications simultaneously. For example, UE 110 may have a mail application, a navigation application, etc., active concurrently with the streaming application. These other applications may also receive DL data, including foreground or background data. UE 110 may align these other running applications with the streaming application, such that DL data for these applications is also received during RRC inactivity. It should be understood that UE 110 may modify the UE assistance information provided in the MAC CE to accommodate these other applications (e.g., change the minimum license size, etc.).

[0043] It should also be understood that, when receiving DL data, the exemplary implementation does not require UE 110 to remain in an RRC inactive state. For example, there may be a situation where UE 110 transitions to an RRC connected state to receive DL data because one or more of the applications being executed require an RRC connected state for DL ​​data.

[0044] Additionally, UE 110 can modify UE auxiliary information while a streaming application is running. For example, radio conditions may change over time while a streaming application is running, altering the traffic pattern. UE 110 can determine this altered traffic pattern and send updated additional data to network 405 during the next available RACH request to change how network 405 delivers DL data. Therefore, the delivery method of DL data does not need to be static once the streaming application has started.

[0045] Figure 5 A second exemplary signaling diagram 500 is shown, according to various exemplary embodiments, allowing UE 110 to receive DL traffic from network 505 during RRC inactivity. Similarly, network 405 can be considered as 5G NR-RAN 120 or LTE-RAN 122, and UE 110 can be connected to one of gNB 120A or eNB 122A. Signaling diagram 500 is similar to signaling diagram 400 because UE assistance information is provided to network 405 during the RACH procedure performed between network 405 and UE 110. The signaling for RRC inactivity 510, paging 520, and RACH request 530 are similar to the corresponding signals in signaling diagram 400. RACH request 530 will include UE assistance information, which network 505 will use to provide DL data during UE 110's RRC inactivity.

[0046] However, in this example, UE 110 does not receive the RACH response 540. Those skilled in the art will understand that there could be various reasons why UE 110 does not receive the RACH response 540, such as radio channel degradation, interference, or the network 505 not having received the original RACH request 530. Figure 5 In the example, UE 110 will resend the RACH request 550 to network 505. This retransmission will include the same information as the original RACH request 530, including, for example, a MAC CE with UE assistance information. UE 110 can then receive the RACH response 560, and the signaling will be as described above. Figure 4The same procedure described continues. Similarly, since network 505 has already received UE assistance information from UE 110, network 505 can send DL data during RRC inactivity state 590.

[0047] Figure 6 A third exemplary signaling diagram 600 is shown, according to various exemplary embodiments, allowing UE 110 to receive DL traffic from network 605 in an RRC inactive state. Similarly, network 605 can be considered as 5G NR-RAN 120 or LTE-RAN 122, and UE 110 can be connected to one of gNB 120A or eNB 122A. (Refer to...) Figure 6 In the exemplary implementation described, when UE 110 is in an RRC connection state with network 605, UE assistance information is provided to network 605.

[0048] exist Figure 6 In this context, UE 110 can be considered to initially be in an RRC connection state with network 605. While in the RRC connection state, UE 110 can exchange data with network 605. As part of this data exchange, UE 110 can provide UE assistance information to network 605 in UE assistance information message 610. However, it should be understood that UE 110 can provide UE assistance information as part of any message exchanged with network 605 during the RRC connection state. The UE assistance information can be the same as described above with reference to signaling diagram 400, but it is delivered at a different time, for example, during the RRC connection state, rather than at [other time]. Figure 4 During the RACH process.

[0049] Then, UE 110 can transition to the RRC inactive state 620. During the RRC inactive state, network 605 can send DL data to UE 110 based on UE assistance information provided during the previous RRC connected state. At a later time, UE 110 may want to enter the RRC connected state to exchange additional information with network 605. To enter the RRC connected state, UE 110 will send a RACH request 630 to network 605. Since the UE assistance information was previously sent during the last RRC connected state, the RACH request 630 may not include the UE assistance information, as done in signaling diagram 400.

[0050] Network 605 will send a RACH response 640 including uplink grant for UE 110, and UE 110 will enter the RRC connected state. During the RRC connected state, UE 110 will send data 650 to network 605 and receive a HARQ ACK 660 to acknowledge that network 605 has received data 650. When data 650 transmission is complete, UE 110 will transition back to the RRC inactive state 670. Similarly, while in the RRC inactive state 670, UE 110 can continue to receive DL data from network 605 based on UE assistance information.

[0051] It should be understood that in this example, UE 110 did not send any additional UE assistance information (e.g., associated with data 650) during the most recent RRC connection state. Therefore, network 605 will continue to send DL data based on the UE assistance information received in UE assistance information message 610. However, UE 110 may send additional UE assistance information messages (e.g., corresponding to data exchange 650) during the most recent RRC connection state to change the UE assistance information. Therefore, when network 605 sends DL data during RRC inactivity state 670, network 605 can send DL data based on newly received UE assistance information.

[0052] Figure 7 A fourth exemplary signaling diagram 700 is shown, according to various exemplary embodiments, allowing UE 110 to receive DL traffic from network 705 in an RRC inactive state. Similarly, network 705 can be considered as 5G NR-RAN 120 or LTE-RAN 122, and UE 110 can be connected to one of gNB 120A or eNB 122A. Signaling diagram 700 is similar to signaling diagram 600 because UE assistance information is provided to network 705 when UE 110 is in an RRC connected state with network 705.

[0053] exist Figure 7In this context, UE 110 can be considered to initially be in an RRC connected state with network 705. While in the RRC connected state, UE 110 can exchange data with network 705. As part of this data exchange, UE 110 can provide UE assistance information to network 705 in a UE assistance information message 710. Then, UE 110 can transition to an RRC inactive state 720. During the RRC inactive state, network 705 can send DL data to UE 110 based on the UE assistance information provided during the previous RRC connected state. At a later time, UE 110 may want to enter the RRC connected state to exchange additional information with network 705. To enter the RRC connected state, UE 110 will send a RACH request 730 to network 705. Since the UE assistance information was previously sent during the last RRC connected state, the RACH request 730 may not include the UE assistance information.

[0054] However, in this example, UE 110 does not receive RACH response 740. Figure 7 In the example, UE 110 will resend the RACH request 750 to network 705. Then, UE 110 can receive the RACH response 760, and the signaling will be in accordance with the above reference. Figure 6 The same manner described continues. Similarly, because network 705 has already received UE assistance information from UE 110 during the previous RRC connected state (e.g., UE assistance information message 710), network 705 can send DL data during the RRC inactive state 790.

[0055] Figure 8 A fifth exemplary signaling diagram 800 is shown, according to various exemplary embodiments, allowing UE 110 to receive DL traffic from network 805 in an RRC inactive state. Similarly, network 805 can be considered as 5G NR-RAN 120 or LTE-RAN 122, and UE 110 can be connected to one of gNB 120A or eNB 122A. Signaling diagram 800 is similar to signaling diagram 400 because UE assistance information is provided to network 805 during the RACH procedure performed between network 405 and UE 110. The signaling for 810 to 860 is similar to the corresponding signals 410 to 460 in signaling diagram 400 and will not be described further.

[0056] As described above, data 850 and HARQ ACK 860 can include multiple exchange messages between UE 110 and network 805. A Tracking Area Code (TAC) can be included in each HARQ ACK sent. UE 110 can also include a Time Alignment Timer (TAT). The TAT is reset each time a TAC is received. When the TAT expires, if UE 110 has not received a message from network 805 within the duration of the TAT, UE 110 assumes it is now out of sync with network 805. Signaling diagram 800 shows that UE 110 can also implement an additional timer 870, the timing of which can be negotiated between UE 110 and network 805. Even if UE 110 is out of sync with network 805 880, network 805 can still send data to UE 110. In other words, even if UE 110 loses synchronization at 880 during the active period of timer 870, UE 110 will remain in the RRC connected state, allowing UE 110 to receive additional data from network 805. For example, UE 110 can monitor the PDCCH during this period to receive information about additional DL data from network 805. When timer 870 expires, UE 110 will transition back to the RRC inactive state at 890 and can continue to receive DL data, as described above.

[0057] Figure 9 A sixth exemplary signaling diagram 900 is shown, according to various exemplary embodiments, allowing UE 110 to receive DL traffic from network 905 in an RRC inactive state. Similarly, network 905 can be considered as 5G NR-RAN 120 or LTE-RAN 122, and UE 110 can be connected to one of gNB 120A or eNB 122A. Signaling diagram 900 is similar to signaling diagram 600 in that UE assistance information is provided to network 905 when UE 110 and network 905 are in an RRC connected state. The signaling for 910 to 960 is similar to the corresponding signals 610 to 660 in signaling diagram 600 and will not be described further.

[0058] Similar to signaling diagram 800, signaling diagram 900 shows that UE 110 can also implement an additional timer 970, the timing of which can be negotiated between UE 110 and network 905. This timer starts when UE 110 loses synchronization with network 905 at 980. As described above, even if UE 110 loses synchronization at 980 while timer 970 is active, UE 110 will remain in RRC connected state, allowing UE 110 to receive additional data from network 905. For example, UE 110 can monitor PDCCH during this period to receive information about additional DL data from network 905. When timer 970 expires, UE 110 will transition back to RRC inactive state 990 and can continue receiving DL data, as described above.

[0059] Signaling diagrams 400 to 900 illustrate various signaling methods that can be used by the UE and the network to allow the network to send DL data to the UE when the UE is in an RRC inactive state. When the UE receives data in an RRC inactive state, the UE does not need to monitor the PDCCH, which means that the UE does not have to consume the energy associated with continuous monitoring of the PDCCH in the usual way.

[0060] Those skilled in the art will understand that the exemplary embodiments described above can be implemented with any suitable software or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, and mobile devices with operating systems such as iOS, Android, etc. In other examples, exemplary embodiments of the methods described above may be embodied as programs comprising lines of code stored on a non-transitory computer-readable storage medium, which, at compile time, can be executed on a processor or microprocessor.

[0061] Although this patent application describes various combinations of various embodiments, each with different features, those skilled in the art will understand that any feature of an embodiment can be combined with features of other embodiments or features that are not functionally or logically inconsistent with the operation or function of the device of the disclosed embodiment of the invention in any manner not explicitly denied.

[0062] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0063] It will be apparent to those skilled in the art that various modifications can be made to this disclosure without departing from its spirit or scope. Therefore, this disclosure is intended to cover all modifications and variations thereof, provided that such modifications and variations are within the scope of the appended claims and their equivalents.

Claims

1. A method for using a user equipment (UE), comprising: At the UE connected to the network: Execute the application that receives data from the network; The UE assistance information is sent to the network, wherein the UE assistance information corresponds to the traffic pattern of the data received by the application from the network, and wherein the UE assistance information includes one of minimum license size, minimum license frequency and minimum license duration; Enter Radio Resource Control (RRC) inactive state; as well as When the RRC is inactive, the data is received from the network based on the UE assistance information without monitoring the Physical Downlink Control Channel (PDCCH).

2. The method of claim 1, wherein the UE assistance information is sent in a random access channel (RACH) request.

3. The method according to claim 1, wherein when the UE is in an RRC connection state with the network, the UE auxiliary information is sent.

4. The method according to claim 1, further comprising: Determine the traffic patterns associated with the application.

5. The method according to claim 1, wherein the application is a streaming application.

6. The method according to claim 1, further comprising: Execute the second application; as well as When the UE is in the RRC inactive state, the incoming data transmission for the second application is aligned with the reception of the data for the application.

7. The method according to claim 1, further comprising: It is determined that the UE has lost synchronization with the network; When the UE loses synchronization with the network, a timer is started, wherein the UE remains in an RRC connection state during the duration of the timer; For downlink data transmission from the network, the control channel is monitored during the duration of the timer; as well as When the timer expires, the system transitions to the RRC inactive state.

8. A user equipment (UE), comprising: A transceiver configured to communicate with a network; as well as A processor configured to perform operations including: Execute the application that receives data from the network; The UE assistance information is sent to the network, wherein the UE assistance information corresponds to the traffic pattern of the data received by the application from the network, and wherein the UE assistance information includes one of minimum license size, minimum license frequency and minimum license duration; Entering the Radio Resource Control (RRC) inactive state; and When the RRC is inactive, the data is received from the network based on the UE assistance information without monitoring the Physical Downlink Control Channel (PDCCH).

9. The UE of claim 8, wherein the UE auxiliary information is transmitted in a random access channel (RACH) request.

10. The UE according to claim 8, wherein when the UE is in an RRC connection state with the network, the UE auxiliary information is sent.

11. The UE according to claim 8, wherein the operation further comprises: Determine the traffic pattern associated with the application.

12. The UE of claim 8, wherein the processor comprises an application processor and a baseband processor, wherein the application processor executes the application program.

13. The UE of claim 8, wherein the operation further comprises: Execute the second application; as well as When the UE is in the RRC inactive state, the incoming data transmission for the second application is aligned with the reception of the data for the application.

14. The UE of claim 8, wherein the operation further comprises: It is determined that the UE has lost synchronization with the network; When the UE loses synchronization with the network, a timer is started, wherein the UE remains in an RRC connection state during the duration of the timer; For downlink data transmission from the network, the control channel is monitored during the duration of the timer; as well as When the timer expires, the system transitions to the RRC inactive state.

15. An integrated circuit, comprising: A circuit configured to send UE assistance information to a network, wherein the UE assistance information corresponds to a traffic pattern for data received from the network by an application, wherein the UE assistance information includes one of a minimum grant size, a minimum grant frequency, and a minimum grant duration; Circuits configured to enter the Radio Resource Control (RRC) inactive state; as well as A circuit configured to receive data from the network based on the UE assistance information when in the RRC inactive state without monitoring the Physical Downlink Control Channel (PDCCH).

16. The integrated circuit of claim 15, wherein the UE assistance information is transmitted in a random access channel (RACH) request.

17. The integrated circuit of claim 15, wherein the UE assistance information is transmitted during an RRC connection state with the network.

Images