Method and apparatus for providing power preference information in a wireless communication system

Abstract

Methods and apparatuses for providing power preference information in a wireless communication system are disclosed. A terminal according to one embodiment of the present disclosure identifies necessity of transition from a radio resource control (RRC) connected mode, and transmits a connection release request message including state information of a terminal preference to a base station, wherein the state information of the terminal preference includes information indicating whether a state of the terminal preference is an idle mode, an inactive mode, a connected mode, or a random mode, and the random mode can indicate a mode in which the terminal wants connection release but has no preference among the idle mode and the inactive mode.

Description

Technical Field

[0001] This disclosure relates to techniques for managing power in wireless communication systems, and more specifically, to methods and apparatus for providing power preference information in wireless communication systems. Background Technology

[0002] To meet the growing demand for wireless data traffic following the commercialization of fourth-generation (4G) communication systems, efforts have been made to develop fifth-generation (5G) or pre-5G communication systems. For this reason, 5G or pre-5G communication systems are referred to as "super-4G network" communication systems or "post-Long Term Evolution (post-LTE)" systems. To achieve high data rates, the implementation of 5G communication systems in ultra-high frequency (UHF) or millimeter-wave (mmWave) bands (e.g., the 60 GHz band) is being considered. To reduce path loss of radio waves and increase the transmission distance of 5G communication systems in the UHF band, various technologies such as beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO are being researched. To improve the system network of 5G communication systems, various technologies such as evolved small cells, advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multipoint (CoMP), and interference cancellation have been developed. In addition, for 5G communication systems, advanced coding and modulation (ACM) technologies such as hybrid frequency shift keying (FSK) with orthogonal amplitude modulation (QAM) (FQAM) and sliding window superposition coding (SWSC) have been developed, as well as advanced access technologies such as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA).

[0003] The internet has evolved from a human-based network of connections where humans generate and consume information to the Internet of Things (IoT), in which distributed elements, such as objects, exchange information to process it. The Internet of Everything (IoE) technology has emerged, where IoT technology is combined with technologies for processing big data, such as those connected to cloud servers. To realize IoT, various technological elements are required, such as sensing technologies, wired / wireless communication and network infrastructure, service interface technologies, and security technologies. In recent years, technologies related to sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC) for connecting objects have been studied. In the IoT environment, intelligent internet technology (IT) services can be provided to collect and analyze data obtained from connected objects to create new value in human life. As existing information technology (IT) merges and integrates with various industries, IoT can be applied to a wide range of fields such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0004] Therefore, various attempts have been made to apply 5G communication systems (or New Radio (NR)) to IoT networks. For example, technologies related to sensor networks, M2M communication, and MTC are being implemented using 5G communication technologies including beamforming, MIMO, and array antennas. The application of cloud RAN as a big data processing technology can be an example of the convergence of 5G communication technology and IoT technology. Summary of the Invention

[0005] Technical issues

[0006] This disclosure provides methods and apparatus for efficiently managing power in a wireless communication system when a terminal switches to a connected mode.

[0007] Solution to the problem

[0008] According to an embodiment, a method performed by a terminal for providing power preference information in a wireless communication system may include: receiving configuration information about a connection release request from a base station; identifying transmission conditions for a connection release request message based on the received configuration information about the connection release request; and sending a connection release request message based on the identified conditions, the connection release request message including whether there is a terminal preference mode or a terminal preference mode in idle mode and inactive mode. Attached Figure Description

[0009] Figure 1 This is a diagram illustrating the operation of a terminal sending a connection release request message to a base station.

[0010] Figure 2 This is a diagram used to describe a connection release request message according to an embodiment.

[0011] Figure 3 This is a diagram used to describe a connection release request message according to another embodiment.

[0012] Figure 4 This is a diagram illustrating a method for disabling a timer for an operation connection release request message according to an embodiment.

[0013] Figure 5 This is a diagram illustrating a method for disabling a timer in response to an operation connection release request message according to another embodiment.

[0014] Figure 6 This is a diagram illustrating the operation of sending a connection release request message according to an embodiment.

[0015] Figure 7 This is a diagram illustrating the operation of sending a connection release request message according to another embodiment.

[0016] Figure 8 This is a diagram illustrating the operation of sending a connection release request message according to another embodiment.

[0017] Figure 9 This is a diagram illustrating the structure of a base station according to an embodiment.

[0018] Figure 10 This is a diagram illustrating the structure of a terminal according to an embodiment. Detailed Implementation

[0019] Best mode

[0020] Embodiments of this disclosure may provide a terminal for transmitting status information in a wireless communication system. The terminal may include a transceiver and at least one processor, and the at least one processor may be configured to identify the necessity of a transition from a Radio Resource Control (RRC) connection mode and send a connection release request message including terminal preference status information to a base station. The terminal preference status information may include information indicating whether the terminal preference status is an idle mode, an inactive mode, a connected mode, or a random mode, and a random mode may indicate that the terminal preference is released from the connected mode, but has no preferred mode in the idle mode or inactive mode.

[0021] According to an embodiment, when the terminal preference status information includes information indicating that the terminal preference status is in connection mode, the terminal preference status information can be sent in the case of an earlier indication that the terminal preference has been reverted from the RRC connection mode.

[0022] According to an embodiment, at least one processor can be configured to start a connection release request disable timer and initiate the transmission of a connection release request message including terminal preference status information, and can send the connection release request message including terminal preference status information even when the connection release request disable timer is not running.

[0023] According to an embodiment, the connection release request disable timer can be stopped when initiating an RRC connection reconstruction or an RRC connection recovery.

[0024] According to the embodiments, the necessity of switching from RRC connection mode can be identified to reduce the power consumption of the terminal.

[0025] According to an embodiment, at least one processor may be configured to receive configuration information associated with a connection release request message from a base station, and the configuration information associated with the connection release request message may include configuration information indicating whether terminal preference status information can be reported and configuration information associated with a connection release request disable timer.

[0026] According to an embodiment, the configuration information indicating whether terminal preference status information can be reported may include an indicator indicating whether terminal preference status information can be reported when the terminal is in a connected state.

[0027] Another embodiment of this disclosure provides a base station for receiving status information in a wireless communication system. The base station may include a transceiver and at least one processor, and the at least one processor may be configured to receive a connection release request message including status information of the terminal preferences from a terminal, and to send configuration information associated with the status information to the terminal based on the received connection release request message. The status information of the terminal preferences may include information indicating whether the state of the terminal preferences is an idle mode, an inactive mode, a connected mode, or a random mode, and a random mode may indicate that the terminal preferences are released from the connected mode, but not in the idle mode or inactive mode.

[0028] According to an embodiment, when the terminal preference status information includes information indicating that the terminal preference status is in connection mode, the terminal preference status information can be sent if the terminal preference revokes an earlier indication indicating a change from Radio Resource Control (RRC) connection mode.

[0029] According to an embodiment, at least one processor may be configured to send configuration information associated with a connection release request message to a terminal, and the configuration information associated with the connection release request message may include configuration information indicating whether terminal preference status information can be reported and configuration information associated with a connection release request disable timer.

[0030] According to an embodiment, a connection release request message including terminal preference status information can be received even when the connection release request prohibition timer is not running.

[0031] According to an embodiment, the connection release request disable timer can be stopped when initiating an RRC connection reconstruction or an RRC connection recovery.

[0032] According to an embodiment, the configuration information indicating whether terminal preference status information can be reported may include an indicator indicating whether terminal preference status information can be reported when the terminal is in a connected state.

[0033] Another embodiment of this disclosure provides a method for operating a terminal for transmitting status information in a wireless communication system. The method may include: identifying the necessity of transitioning from a Radio Resource Control (RRC) connection mode; and sending a connection release request message to a base station including status information of the terminal preference, wherein the status information of the terminal preference may include information indicating whether the state of the terminal preference is an idle mode, an inactive mode, a connected mode, or a random mode, and a random mode may indicate that the terminal preference is released from the connected mode, but has no preferred mode in the idle mode or inactive mode.

[0034] Another embodiment of this disclosure provides a method for operating a base station for receiving status information in a wireless communication system. The method may include: receiving a connection release request message from a terminal, including status information of terminal preferences; and sending configuration information associated with the status information to the terminal based on the received connection release request message, wherein the status information of the terminal preferences may include information indicating whether the terminal preference is in an idle mode, an inactive mode, a connected mode, or a random mode, and a random mode may indicate that the terminal preference is released from the connected mode, but has no preferred mode in the idle mode or inactive mode.

[0035] Open model

[0036] In the following description of this disclosure, detailed descriptions of well-known functions or configurations will be omitted as they would unnecessarily obscure the subject matter of this disclosure. Embodiments of this disclosure will be described below with reference to the accompanying drawings.

[0037] In the following description, for ease of description, terms used to identify access nodes, to refer to network entities, to refer to messages, to refer to interfaces between network entities, and to refer to various types of identification information are used. Therefore, this disclosure is not limited to the terms described below, and other terms that refer to objects with equivalent technical meanings may be used.

[0038] In the following description, for ease of description, terms and names defined in the 3GPP LTE standard may be used. However, this disclosure is not limited to such terms and names, and may be similarly applied to systems based on other standards.

[0039] As a representative example of a broadband wireless communication system, the LTE system employs Orthogonal Frequency Division Multiplexing (OFDM) for the downlink (DL) and Single-Carrier Frequency Division Multiple Access (SC-FDMA) for the uplink (UL). The uplink can refer to the radio link used to transmit data or control signals from a terminal (e.g., a User Equipment (UE) or Mobile Station (MS)) to a base station (e.g., an eNode B (eNB) or Base Station (BS)), and the downlink can refer to the radio link used to transmit data or control signals from the base station to the terminal. These multiple access schemes distinguish the data or control information of different users by allocating non-overlapping time-frequency resources (i.e., achieving orthogonality between them) for the users' data or control information.

[0040] As a post-LTE system, 5G systems may need to support services that can simultaneously meet a variety of requirements, as they may need to freely reflect the diverse needs of users, service providers, and others. Services considered for 5G systems may include enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC).

[0041] According to some embodiments, eMBB can be designed to provide improved data rates compared to those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, from the base station's perspective, eMBB should be able to provide a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink. Furthermore, 5G communication systems may need to provide increased user-perceived data rates while delivering peak data rates. To meet this requirement, 5G communication systems may require improvements to various transmit / receive technologies, including more advanced multiple-input multiple-output (MIMO) transmission technologies. Additionally, 5G communication systems can meet the required data rates by using a wider frequency bandwidth than 20 MHz in the 2 GHz band used in current LTE, while simultaneously transmitting signals using a transmission bandwidth of up to 20 MHz in the 3 GHz to 6 GHz band, or 6 GHz or higher.

[0042] Simultaneously, mMTC is being considered to support application services such as the Internet of Things (IoT) within 5G communication systems. To efficiently deliver IoT, mMTC may require support for large-scale terminal access within a cell, improved terminal coverage, improved battery life, and reduced terminal costs. Since IoT is attached to various sensors and devices to provide communication capabilities, it should be able to support a large number of terminals within a cell (e.g., 1,000,000 terminals / square kilometer). Furthermore, because mMTC-enabled terminals are likely to be located in shadowed areas not covered by the cell, such as basements of buildings, due to the nature of the service, it may require a wider coverage area than other services offered by 5G communication systems. mMTC-enabled terminals should be configured as low-cost terminals, and due to the difficulty in frequently replacing terminal batteries, a very long battery life of approximately 10 to 15 years may be required.

[0043] Finally, URLLC can be used for remote control services in robotics or machinery, industrial automation, unmanned aerial vehicles, remote healthcare, emergency alarms, etc., as a cellular-based wireless communication service for mission-critical purposes. Therefore, communication provided by URLLC may need to offer very low latency (ultra-low latency) and very high reliability (ultra-high reliability). For example, services supporting URLLC should meet an air interface latency of less than 0.5 milliseconds and may simultaneously have 10 -5 Or a lower packet error rate requirement. Therefore, for services supporting URLLC, 5G systems should provide shorter transmission time intervals (TTIs) than other services, and can also have the design requirement to allocate wide resources in the frequency band to ensure the reliability of the communication link.

[0044] The three services considered in the above-described 5G communication system—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. In this case, different transmission / reception technologies and parameters can be used between services to meet their varying requirements. However, the aforementioned mMTC, URLLC, and eMBB are merely examples of different service types, and the service types applicable to this disclosure are not limited to these.

[0045] Furthermore, although embodiments of this disclosure will be described below using LTE, LTE-A, LTE Pro, or 5G (or NR, next-generation mobile communications) as examples, embodiments of this disclosure can also be applied to other communication systems with similar technical backgrounds or channel types. Moreover, based on the judgment of those skilled in the art, embodiments of this disclosure can be applied to other communication systems with modifications without departing from the scope of this disclosure.

[0046] Figure 1This is a diagram illustrating the operation of a terminal sending a connection release request message to a base station.

[0047] In connected mode (RRC_CONNECTED), terminal 100 can establish a connection with base station 110 to perform data transmission / reception operations with base station 110. Furthermore, terminal 100 in connected mode should monitor the Physical Downlink Control Channel (PDCCH), which includes resource allocation by base station 110, and perform signal measurements for data communication. Because this operation results in power consumption for terminal 100, it may be inefficient for terminal 100 to remain in connected mode when no data is being generated. If terminal 100 determines to release connected mode to reduce power consumption, terminal 100 can send a connection release request message 120 to base station 110. For example, if a terminal transmitting / receiving data in connected mode fails to transmit / receive data for some reason or for a certain period of time, the base station can send a connection release request message to the terminal.

[0048] The connection release request message may include at least one of the following: information about whether terminal 100 prefers connection release, information about which RRC mode terminal 100 prefers to switch to, and information about whether terminal 100 revokes connection release.

[0049] If terminal 100, which is in connected mode (RRC_CONNECTED), prefers to switch to an idle mode (RRC_IDLE) or inactive mode (RRC_INACTIVE), which is not connected mode, a connection release request message can be triggered. However, this is merely one embodiment. In another embodiment, the statement that terminal 100 prefers to switch to an idle mode or inactive mode can mean that there is no expected data transmission / reception for a short period of time. When base station 110 receives the connection release request message, base station 110 can recognize that terminal 100 prefers connection release for purposes such as power consumption. Furthermore, through the connection release request message, base station 100 can identify the preferred mode of terminal 100 (e.g., idle mode or inactive mode) and can instruct it to switch to the corresponding mode. When terminal 100 withdraws the connection release request message, terminal 100 can continue to operate in connected mode.

[0050] Figure 2 This is a diagram used to describe a connection release request message according to an embodiment.

[0051] Reference Figure 2The connection release request message can include information instructing the terminal to switch to either idle or inactive mode. Furthermore, the terminal can use the connection release request message to specify which mode it prefers to switch to. When the terminal prefers to switch to idle mode, it can provide the base station with information indicating its preferred power mode is idle (RRC_IDLE). When the terminal prefers to switch to inactive mode, it can provide the base station with information indicating its preferred power mode is inactive (RRC_INACTIVE). However, this is merely an example, and according to another example, when the terminal prefers to switch to either idle or inactive mode (which is not connected mode), but has no preferred mode, the terminal can provide the base station with information indicating its preferred power mode is idle or inactive. Additionally, if the terminal is not experiencing power issues or if there is a possibility of recovery and therefore the terminal prefers to remain in connected mode, the terminal can provide the base station with information indicating its preferred power mode is connected (RRC_CONNECTED).

[0052] Reference Figure 2 The connection release request message can be included in and sent within a UE (User Equipment) Assistance Information message. Each piece of terminal information can be sent to the base station via the UE Assistance Information message, and the connection release request message can be one of these pieces of terminal information.

[0053] In addition, Figure 2 In the embodiments described, sending a connection release request message in the powerSavingInfo-r16 field is depicted; however, this is merely an example, and the names of fields including the connection release request message are not limited to this. Sending the powerSavingInfo-r16 field likely means that a connection release request message has been sent. The powerSavingInfo-r16 field may include a preferredMode field, and the preferredMode field may have one of four values.

[0054] Connected: The terminal prefers to remain in connected mode. This value can be used if the terminal requests to switch to a mode other than connected mode and then cancels the request.

[0055] Idle: The terminal prefers to release the connection, and its preferred mode is idle mode.

[0056] Inactive: The terminal prefers to release the connection, and its preference mode is inactive.

[0057] idleOrInactive: The terminal prefers to release the connection and has no preferred mode among idle and inactive modes.

[0058] However, this is merely an example, and according to another embodiment, when the UE assistance information message includes a preference mode field having one of the four values ​​described above, the transmission of the UE assistance information message may signify the transmission of a connection release request message. If the connection release request message is sent while the terminal is not in connected mode, then in this case the Connected value may indicate that the terminal prefers to switch to connected mode.

[0059] Figure 3 This is a diagram used to describe a connection release request message according to another embodiment.

[0060] Reference Figure 3 The connection release request message can include information instructing the terminal to switch to either idle or inactive mode. Furthermore, the terminal can use the connection release request message to specify which mode it prefers to switch to. When the terminal prefers to switch to idle mode, it can provide the base station with information indicating its preferred power mode is idle (RRC_IDLE). When the terminal prefers to switch to inactive mode, it can provide the base station with information indicating its preferred power mode is inactive (RRC_INACTIVE). However, this is merely an example. According to another example, when the terminal prefers to switch to either idle or inactive mode (which is not connected mode), but neither is the preferred mode, the terminal can provide the base station with information indicating its preferred power mode is not in idle or inactive mode. Additionally, when the terminal is not experiencing power issues or when there is a possibility of recovery and therefore the terminal prefers to remain in connected mode, the terminal can provide the base station with information indicating its preferred power mode is connected (RRC_CONNECTED).

[0061] Reference Figure 3 The connection release request message can be sent via UE auxiliary information messages. Each piece of terminal information can be sent to the base station via UE auxiliary information messages, and the connection release request message can be one of these pieces of terminal information. Furthermore, in Figure 3In the embodiments described, a connection release request message is sent in the releaseRequest-r16 and powerSavingInfo-r16 fields; however, this is merely an example, and the names of the fields that include the connection release request message are not limited to this. Sending the releaseRequest-r16 field likely means that a connection release request message has been sent. The releaseRequest-r16 field may include whether the terminal prefers connection release or whether the terminal prefers to remain in connected mode (RRC_CONNECTED), which can be determined by information from the releasePreference field. In this case, the releasePreference field may have one of the following two values.

[0062] Connected: The terminal prefers to remain in connected mode. This value can be used when a terminal requests to switch to a mode other than connected mode and then cancels the request.

[0063] Release: Terminal preference connection release.

[0064] However, this is merely one example, and according to another embodiment, when the releaseRequest-r16 value is configured to True, the base station can interpret the terminal's preference for connection release. If a connection release request message is sent while the terminal is not in connected mode, then in this case the connection value might imply that the terminal prefers to switch to connected mode.

[0065] In addition, the powerSavingInfo-r16 field can include the preferred mode when the terminal prefers to release the connection. The preferred mode can be included in the powerSavingInfo-r16 field as the preferredMode field, and the preferredMode field can have one of the following two values.

[0066] Idle: The terminal prefers to release the connection and the preference mode is set to idle mode.

[0067] Inactive: The terminal prefers to release the connection, and the preference mode is inactive.

[0068] In this case, the absence of the preferredMode field may mean that the terminal has no preferred mode in idle mode and inactive mode.

[0069] Figure 4This is a diagram illustrating a method for disabling a timer for a connection release request message according to an embodiment. Excessive execution of the terminal sending connection release request messages (410) may waste radio resources. Therefore, the terminal can configure (420) a "connection release request message disabling timer" to disable the sending of connection release request messages. The connection release request message disabling timer can start at one of the following times: when the connection release request message is triggered, started, or sent. According to an embodiment, the terminal may not send a connection release request message when the connection release request message disabling timer is running. However, this is merely an embodiment, and according to another embodiment, a message for canceling the connection release request message sent by the terminal or a message indicating that the terminal prefers to remain in connected mode can be sent, regardless of whether the connection release request message disabling timer is running. Furthermore, a connection release request message triggered when the connection release request message disabling timer expires can be sent.

[0070] When initiating an RRC connection re-establishment, the running Connection Release Request Message Disable Timer (430) can be stopped. When performing an RRC connection re-establishment, the applied configuration related to the Connection Release Request Message can be released. This is likely because the running Connection Release Message Disable Timer and the configuration related to the Connection Release Request Message are no longer valid when performing an RRC connection re-establishment. Furthermore, when initiating an RRC connection recovery, the running Connection Release Message Disable Timer can be stopped. When performing an RRC connection recovery, the applied configuration related to the Connection Release Request Message can be released. This is likely because the running Connection Release Message Disable Timer and the configuration related to the Connection Release Request Message are no longer valid. The timer value of the Connection Release Message Disable Timer can be configured and can be included in the base station's RRC configuration message.

[0071] Figure 5 This is a diagram illustrating a method for disabling a timer in response to an operation connection release request message according to another embodiment.

[0072] Sending connection release request messages (510) too frequently may waste radio resources. Therefore, the terminal can configure (520) a "connection release request message disable timer" to disable the sending of connection release request messages. The connection release request message disable timer can start at one of the times when the connection release request message is triggered, started, or sent. According to an embodiment, the terminal may not send connection release request messages when the connection release request message disable timer is running. However, this is only one embodiment, and according to another embodiment, a message to cancel a connection release request message previously sent by the terminal or a message indicating that the terminal prefers to remain in connected mode can be sent, regardless of whether the connection release request message disable timer is running. In addition, a connection release request message triggered when the connection release request message disable timer expires can be sent.

[0073] When performing an RRC connection release, the in-operation connection release request message disable timer (530) can be stopped. When the RRC connection is released, the applied configuration associated with the connection release request message can be released. This is likely because the in-operation connection release message disable timer and the configuration associated with the connection release request message are no longer valid when performing an RRC connection release. The timer value of the connection release message disable timer can be configured and can be included in the base station's RRC configuration message.

[0074] Figure 6 This is a diagram illustrating the operation of sending a connection release request message according to an embodiment. When the transmission of a connection release request message is configured in the terminal (610), the terminal can send a connection release request message to the base station when pre-configured conditions are met. The configuration of the connection release request message may include at least one of the following: information about whether the base station allows the sending of the connection release request message to the terminal, a timer value for a connection release message prohibition timer, and information about whether the prohibition timer should be applied to a connection release cancellation (preference remains in connection mode) message. The terminal can determine whether 1) the terminal currently wants to release the connection when the message has never been sent since the transmission of the connection release request message was configured, or 2) whether the terminal's preference mode has changed (620). When at least one of these two conditions is met in operation 620, the terminal can send a connection release request message to the base station when the connection release message prohibition timer is not running (630). Figure 2 or Figure 3The message format described herein can be applied to connection release request messages sent to a base station. A connection release request message may include information about whether the terminal prefers to remain in connected mode, whether the terminal prefers to release the connection and wants to switch to idle mode, whether the terminal prefers to release the connection and prefers to switch to inactive mode, or whether the terminal prefers to release the connection but has preferences in both idle and inactive modes. However, this is merely an embodiment, and according to another embodiment, a connection release request message may include information about whether the terminal prefers to remain in connected mode or prefers to release the connection, and whether, when the terminal prefers to release the connection, the terminal prefers idle mode, prefers inactive mode, or has no preference in either idle or inactive mode.

[0075] Figure 7 This is a diagram illustrating the operation of sending a connection release request message according to another embodiment. When the transmission of a connection release request message is configured in the terminal (710), the terminal can send a connection release request message to the base station when pre-configured conditions are met. The configuration of the connection release request message may include at least one of the following: information about whether the base station allows the transmission of the connection release request message to the terminal, a timer value for a connection release message prohibition timer, and information about whether the prohibition timer should be applied to a connection release cancellation (wanting to remain in connected mode) message. The terminal can determine whether 1) the terminal currently prefers connection release when the message has never been sent since the transmission of the connection release request message was configured, or 2) whether the terminal currently prefers to remain in connected mode again (720) when the terminal has already preferred connection release and therefore preferred RRC release (preferential switch to idle mode, inactive mode, or a mode that is not connected mode) has been indicated and sent in the connection release request message. This situation may be where the terminal prefers to be in connected mode due to immediate power supply, etc. When at least one of these two conditions is met in operation 720, the terminal may send a connection release request message to the base station (730) when the connection release message prohibition timer is not running. Figure 2 or Figure 3 The message format described herein can be applied to connection release request messages sent to a base station. A connection release request message may include information about whether the terminal wants to remain in connected mode, whether the terminal wants to release the connection and switch to idle mode, whether the terminal wants to release the connection and switch to inactive mode, and whether the terminal wants to release the connection but has a preference between idle mode and inactive mode. However, this is merely an embodiment, and according to another embodiment, a connection release request message may include information about whether the terminal wants to remain in connected mode or wants to release the connection, and whether, when the terminal wants to release the connection, the terminal wants idle mode or inactive mode, or has no preference between idle mode and inactive mode.

[0076] Figure 8 This is a diagram illustrating the operation of sending a connection release request message according to another embodiment. When the transmission of a connection release request message is configured in the terminal (810), the terminal can send a connection release request message to the base station if pre-configured conditions are met. The configuration of the connection release request message may include at least one of the following: information about whether the base station allows the sending of the connection release request message to the terminal, a timer value for a connection release message prohibition timer, and information about whether the prohibition timer should be applied to a connection release cancellation (wanting to remain in connected mode) message. The terminal can determine whether it currently prefers to remain in connected mode again (820) when a connection release preference has already been indicated and sent in a connection release request message, and therefore a preference for RRC release (preferential switch to idle mode, inactive mode, or a mode that is not connected mode). This can be applied when the terminal wants to be in connected mode due to immediate power supply, etc. When the conditions of operation 820 are met, the terminal can send a connection release request message to the base station regardless of the operation of the connection release message prohibition timer (830). This might allow the terminal to remain in connected mode if there are no further issues with the power supply to the terminal, as a terminal in connected mode is efficient for data transmission / reception. (Reference) Figure 2 or Figure 3 The format of the described message can be applied to connection release request messages sent to a base station. A connection release request message may include information indicating that the terminal prefers to remain in connected mode. Furthermore, this is merely an embodiment, and according to another embodiment, the connection release request message may include information indicating that the terminal's preferred mode is connected mode.

[0077] Figure 9 This is a diagram illustrating the structure of a base station according to an embodiment.

[0078] Reference Figure 9 The base station may include a transceiver 910, a controller 920, and a storage device 930. In this disclosure, the controller 920 may be defined as a circuit, an application-specific integrated circuit, or at least one processor.

[0079] Transceiver 910 can exchange signals with other network entities. For example, transceiver 910 can send system information to a terminal and can send synchronization signals or reference signals to it.

[0080] According to embodiments of this disclosure, controller 920 can control the overall operation of the base station. For example, controller 920 can control the signal flow between corresponding blocks to perform operations according to the flowchart described above.

[0081] The storage device 930 can store at least one of the information sent / received by the transceiver 910 and the information generated by the controller 920.

[0082] Figure 10 This is a diagram illustrating the structure of a terminal according to an embodiment.

[0083] Reference Figure 10 The terminal may include a transceiver 1010, a controller 1020, and a storage device 1030. In this disclosure, the controller 1020 may be defined as a circuit, an application-specific integrated circuit, or at least one processor.

[0084] Transceiver 1010 can exchange signals with other network entities. For example, transceiver 1010 can receive system information from a base station and can receive synchronization signals or reference signals from it.

[0085] According to embodiments of this disclosure, controller 1020 can control the overall operation of the terminal. For example, controller 1020 can control the signal flow between corresponding blocks to perform operations according to the flowchart described above.

[0086] Storage device 1030 can store at least one of information sent / received by transceiver 1010 and information generated by controller 1020.

[0087] The methods described in the specification or claims according to embodiments of this disclosure can be implemented by hardware, software, or a combination thereof.

[0088] When these methods are implemented in software, a computer-readable storage medium may be provided to store one or more programs (software modules). The one or more programs stored in the computer-readable storage medium may be configured to be executed by one or more processors in an electronic device. The one or more programs may include instructions for causing the electronic device to perform methods according to embodiments of this disclosure as described in the specification or claims.

[0089] These programs (software modules or software) can be stored in random access memory (RAM), including flash memory, read-only memory (ROM), electrically erasable programmable ROM (EEPROM), disk storage devices, optical disc ROM (CD-ROM), digital versatile disc (DVD), other types of optical storage devices, or magnetic tape non-volatile memory. Alternatively, the programs can be stored in any combination of some or all of these. Furthermore, each of the memory components can be provided in multiples.

[0090] Furthermore, the program can be stored in an attachable storage device that can be accessed via a communication network such as the Internet, intranet, local area network (LAN), wide area network (WLAN), or storage area network (SAN), or via a communication network including any combination thereof. Such a storage device can be connected to an apparatus executing embodiments of this disclosure via an external port. Additionally, a separate storage device on the communication network can be connected to an apparatus executing embodiments of this disclosure.

[0091] In the specific embodiments described above, the components included in this disclosure are expressed in a singular or plural form according to the specific embodiments of this disclosure. However, for ease of description, the singular or plural expression is appropriately selected according to the presented situation, but this disclosure is not limited to singular or plural components, and components expressed in a plural form can even be configured in a singular form or vice versa.

[0092] Although specific embodiments of this disclosure have been described above, it will be understood that various modifications may be made therein without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the embodiments described herein, but should be defined by the appended claims and their equivalents.

Claims

1. A terminal in a wireless communication system in Radio Resource Control (RRC) connection mode, the terminal comprising: transceiver; as well as At least one processor, coupled to the transceiver, is configured to: The terminal receives configuration information from the base station to indicate its preferred mode, wherein the configuration information includes a value for disabling a timer. Determine the preference mode field, which has a first value indicating one of Idle, Inactive, Connected, or IdleOrInactive, and Send a message including a preference pattern field to the base station. Among them, Idle indicates that the terminal prefers RRC idle mode from RRC connection mode. Inactive indicates that the terminal prefers the RRC inactive mode from the RRC connection mode. Specifically, IdleOrInactive indicates that the terminal preference is released from RRC connected mode and that the terminal has no preference between RRC idle mode and RRC inactive mode. Wherein, Connected indicates that the terminal indicates a second value of one of Idle, Inactive, or IdleOrInactive and then prefers to revoke the indication of the second value, and The at least one processor is further configured to: If the disable timer is not running and the terminal prefers to revoke the second value, a message including the first value indicating Connected is sent.

2. The terminal as described in claim 1, wherein, The at least one processor is configured to start the disable timer if the disable timer used for reporting the preference mode field is not running.

3. The terminal as described in claim 2, wherein, In the event of initiating an RRC connection reconstruction or initiating an RRC connection recovery, the disable timer is stopped.

4. The terminal as described in claim 1, wherein, Identify the necessity of switching from RRC connection mode to reduce terminal power consumption.

5. The terminal as described in claim 1, wherein, The configuration information also includes an indicator that allows the preference mode field to be reported when the terminal preference remains in RRC connection mode.

6. A base station in a wireless communication system, the base station comprising: transceiver; as well as At least one processor, coupled to the transceiver, is configured to: The system sends configuration information to the terminal, indicating the terminal's preferred mode, wherein the configuration information includes a value for disabling a timer. Receive a message from the terminal indicating a preference pattern field, and The preference pattern field has a first value indicating one of Idle, Inactive, Connected, or IdleOrInactive. Among them, Idle indicates that the terminal prefers the RRC idle mode from the Radio Resource Control (RRC) connection mode. Inactive indicates that the terminal prefers the RRC inactive mode from the RRC connection mode. Specifically, IdleOrInactive indicates that the terminal preference is released from RRC connected mode and that the terminal has no preference between RRC idle mode and RRC inactive mode. Wherein, Connected indicates that the terminal indicates a second value of one of Idle, Inactive, or IdleOrInactive and then prefers to revoke the indication of the second value, and The at least one processor is further configured to: If the disable timer is not running and the terminal prefers to revoke the second value, a message including the first value indicating Connected is received.

7. The base station as described in claim 6, wherein, If the timer is not running, start the timer on the terminal.

8. The base station as described in claim 7, wherein, In the event of initiating an RRC connection reconstruction or initiating an RRC connection recovery, the disable timer is stopped.

9. The base station as described in claim 6, wherein, The configuration information also includes an indicator that shows whether the preference mode field can be reported when the terminal preference remains in RRC connection mode.

10. A method for operating a terminal in a Radio Resource Control (RRC) connection mode in a wireless communication system, the method comprising: The terminal receives configuration information from the base station to indicate its preferred mode, wherein the configuration information includes a value for disabling a timer. Determine the preference mode field, which has a first value indicating one of Idle, Inactive, Connected, or IdleOrInactive; as well as Send a message including a preference pattern field to the base station. Among them, Idle indicates that the terminal prefers RRC idle mode from RRC connection mode. Inactive indicates that the terminal prefers the RRC inactive mode from the RRC connection mode. Specifically, IdleOrInactive indicates that the terminal preference is released from RRC connected mode and that the terminal has no preference between RRC idle mode and RRC inactive mode. Wherein, Connected indicates that the terminal indicates a second value of one of Idle, Inactive, or IdleOrInactive and then prefers to revoke the indication of the second value, and The sending of the message includes: If the disable timer is not running and the terminal prefers to revoke the second value, a message including the first value indicating Connected is sent.

11. A method for operating a base station in a wireless communication system, the method comprising: The system sends configuration information to the terminal, indicating the terminal's preferred mode, wherein the configuration information includes a value for disabling a timer. Receive messages from the terminal, including preference pattern fields; as well as The preference pattern field has a first value indicating one of Idle, Inactive, Connected, or IdleOrInactive. Among them, Idle indicates that the terminal prefers the RRC connection mode to the RRC idle mode. Inactive indicates that the terminal prefers the RRC inactive mode from the RRC connection mode. Specifically, IdleOrInactive indicates that the terminal preference is released from RRC connected mode and that the terminal has no preference between RRC idle mode and RRC inactive mode. Wherein, Connected indicates that the terminal indicates a second value of one of Idle, Inactive, or IdleOrInactive and then prefers to revoke the indication of the second value, and The receipt of the message includes: If the disable timer is not running and the terminal prefers to revoke the second value, a message including the first value indicating Connected is sent.

Images