Method, network device, and terminal device

Abstract

To provide a method, a network device, and a medium for reducing unnecessary power / signaling consumption in discontinuous coverage.SOLUTION: In a communication system, a terminal device receives a first setting indicating at least one first period during which the terminal device is located within the coverage of a network, and performs at least one of performing a cell search, performing measurements for cell reselection, or monitoring for paging messages during the at least one first period.SELECTED DRAWING: Figure 8

Description

[Technical Field]

[0001] TECHNICAL FIELD Embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly to methods, apparatus, and media for communication. [Background technology]

[0002] In conventional wireless communications, terminal devices are required to perform measurements and monitor paging messages even when they are idle. Regarding core network (CN) devices, the CN devices are responsible for triggering terminal device paging procedures and maintaining the terminal device's registration status. In recent years, non-terristrial networks (NTNs) have been proposed to provide wide-area coverage. NTNs refer to networks or network segments that use aircraft or spacecraft equipped with transmitting equipment relay nodes and base stations, or that use radio frequency (RF) resources provided by satellites or unmanned aerial system (UAS) platforms.

[0003] It is currently agreed that NTNs will support discontinuous coverage. When a terminal device is out of network coverage, normal operation of the terminal device and CN device (terminal device performs measurements, monitors paging messages, CN device initiates paging procedures, etc.) will result in undesirable power / signal consumption and unexpected registration state transitions. Summary of the Invention [Problem to be solved by the invention]

[0004] In general, exemplary embodiments of the present disclosure provide a communication solution. To the extent that there are embodiments that do not fall within the scope of the claims, they should be construed as examples useful for understanding various embodiments of the present disclosure. [Means for solving the problem]

[0005] In a first aspect, a method for communication is provided, the method including receiving, in a terminal device, a first configuration indicating at least one first time period during which the terminal device is located within coverage of a network, the method further including performing at least one of performing a cell search, performing measurements for cell reselection, or monitoring for paging messages within the at least one first time period.

[0006] In a second aspect, a communication method is provided, the method including receiving, at a CN device, a second configuration indicating at least one second time period during which the terminal device is located within coverage of the network, the method further including clearing or disabling a Paging Proceed Factor (PPF) flag for the terminal device within the at least one second time period.

[0007] In a third aspect, a communication method is provided, the method including, in an access network device serving a terminal device, determining time information when the terminal device is located within the coverage of a network, the method further including, based on the determined time information, transmitting a first configuration to the terminal device, the first configuration indicating at least one first time period to be used by the terminal device, and transmitting a second configuration to the CN device, the second configuration indicating at least one second time period to be used by the CN device.

[0008] In a fourth aspect, there is provided a terminal apparatus comprising a processor unit and a memory coupled to the processor unit and storing instructions that, when executed by the processor unit, cause the apparatus to perform a method according to the first aspect.

[0009] In a fifth aspect, there is provided a CN apparatus, comprising: a processor unit; and a memory, coupled to the processor unit, having instructions stored thereon, the instructions, when executed by the processor unit, causing the apparatus to perform a method according to the second aspect.

[0010] In a sixth aspect, there is provided an access network apparatus comprising: a processor unit; and a memory, coupled to the processor unit, having instructions stored thereon, the instructions, when executed by the processor unit, causing the apparatus to perform a method according to the third aspect.

[0011] In a seventh aspect, there is provided a computer-readable medium having stored thereon instructions that, when executed on at least one processor, cause the at least one processor to perform a method according to the first aspect.

[0012] In an eighth aspect, there is provided a computer-readable medium having stored thereon instructions that, when executed on at least one processor, cause the at least one processor to perform a method according to the second aspect.

[0013] In a ninth aspect, there is provided a computer-readable medium having stored thereon instructions that, when executed on at least one processor, cause the at least one processor to perform a method according to the third aspect.

[0014] It should be understood that this Summary of the Invention is not intended to identify key features or essential features of the embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will be readily apparent through the following description. [Brief explanation of the drawings]

[0015] The above and other objects, features and advantages of the present disclosure will become more apparent through a more detailed description of several exemplary embodiments of the present disclosure in the accompanying drawings. [Figure 1] 1 shows an exemplary pattern of a conventional power saving mode (PSM). [Figure 2] 1 illustrates an exemplary communication environment in which exemplary embodiments of the present disclosure may be practiced. [Figure 3] 1 shows a signaling chart illustrating a communication process according to some embodiments of the present disclosure. [Figure 4] An example of at least one first period or at least one second period is shown. [Figure 5] 10 shows another signaling chart illustrating a communication process according to some embodiments of the present disclosure. [Figure 6] 1 illustrates an exemplary process for maintaining associated timers. [Figure 7] 10 shows an example of the correspondence between the first period and the actual coverage period. [Figure 8] 1 illustrates an exemplary method performed by a terminal device, according to some embodiments of the present disclosure. [Figure 9] 1 illustrates an exemplary method performed by a CN device, according to some embodiments of the present disclosure. [Figure 10] 1 illustrates an exemplary method performed by an access network device, in accordance with some embodiments of the present disclosure. [Figure 11] 1 shows a schematic block diagram of an apparatus suitable for practicing exemplary embodiments of the present disclosure. Throughout the drawings, the same or similar reference numbers represent the same or similar elements. DETAILED DESCRIPTION OF THE INVENTION

[0016] The principles of the present disclosure will be described with reference to several exemplary embodiments. It should be understood that these embodiments are set forth for illustrative purposes only to aid those skilled in the art in understanding and practicing the present disclosure, and are not intended to imply any limitation on the scope of the present disclosure. The embodiments described herein can be implemented in a variety of ways other than those described below.

[0017] In the following description and claims, unless defined otherwise, all technical and scientific terms used have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0018] References in this disclosure to "one embodiment," "embodiment," "exemplary embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but not all embodiments need include such a particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is believed to be within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

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

[0020] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit example embodiments. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. Furthermore, it should be understood that the terms "comprise," "comprising," "having," "having," "including," and / or "including," when used herein, specify the presence of stated features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0021] In some instances, values, procedures, or devices are referred to as "optimum," "lowest," "highest," "minimum," "maximum," etc. It is understood that such descriptions are intended to indicate choices among multiple functional alternatives used, and that such choices are not necessarily better, smaller, higher, or more preferred than other choices.

[0022] As used herein, the term "communication network" refers to a network conforming to any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), or Narrow Band Internet of Things (NB-IoT). Furthermore, communications between terminal devices and network devices in a communication network may be performed using any suitable generation of communication protocols, including, but not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G), 5.5G, 5G-Advanced, or sixth generation (6G) communication protocols, and / or other protocols currently known or developed in the future. Embodiments of the present disclosure may be applied to various communication systems. Considering the rapid development of communications, there will naturally be future communications technologies and systems in which the present disclosure can be embodied, and the scope of the present disclosure should not be deemed to be limited to only the aforementioned systems.

[0023] As used herein, the term "terminal device" refers to any device with wireless or wired communication capabilities. Examples of terminal devices include user equipment (UE), personal computers, desktops, mobile phones, cell phones, smartphones, personal digital assistants (PDAs), portable computers, tablets, wearable devices, Internet of Things (IoT) devices, Ultra-Reliable Low Latency Communications (URLLC) devices, Internet of Everything (IoE) devices, Machine Type Communications (MTC) devices, vehicle-mounted devices for V2X communications (where X represents pedestrian, vehicle, or infrastructure / network), devices for Integrated Access and Backhaul (IAB), spacecraft or aircraft in Non-Terrestrial Networks (NTN) including High Altitude Platforms (HAP) and satellites, including Unmanned Aerial Systems (UAS), and extended reality (XR) including different types of reality such as augmented reality (AR), mixed reality (MR), and virtual reality (VR). Examples of "terminal equipment" include, but are not limited to, Reality devices, unmanned aerial vehicles (UAVs) that do not require a human pilot, commonly known as drones, devices on high-speed trains (HST), imaging devices such as digital cameras, sensors, gaming devices, music storage and playback devices, or internet appliances that enable wireless or wired internet access and browsing. A "terminal equipment" may also have multicast / broadcast capabilities to support public safety and mission-critical applications, V2X applications, transparent IPv4 / IPv6 multicast distribution, IPTV, smart TV, wireless services, wireless software distribution, group communications, and IoT applications. A terminal equipment may also incorporate one or more subscriber identity modules (SIMs), known as multi-SIM. The term "terminal equipment" can be used interchangeably with UE, mobile station, subscriber equipment, mobile terminal, user terminal, or wireless device.

[0024] The term "core network device" / "CN device" refers to any device or entity that provides an Access and Mobility management Function (AMF), a Session Management Function (SMF), a User Plane Function (UPF), etc. By way of example and not limitation, the CN device may be a Mobility Management Entity (MME), an AMF, an SMF, a UPF, etc. In other embodiments, the CN device may be any other suitable device or entity.

[0025] As used herein, the term "access network device" refers to a device capable of providing or hosting a cell or coverage area over which terminal devices can communicate. Examples of network devices include, but are not limited to, satellites, unmanned aerial systems (UAS) platforms, Node Bs (NodeBs or NBs), evolved Node Bs (eNodeBs or eNBs), next-generation Node Bs (gNBs), transmit / receive points (TRPs), remote radio units (RRUs), radio heads (RHs), remote radio heads (RRHs), IAB nodes, low-power nodes (e.g., femto nodes, pico nodes), reconfigurable intelligent surfaces (RISs), etc.

[0026] A terminal device or network device may have artificial intelligence (AI) or machine learning capabilities, which generally include models that can be used to learn from a large amount of data collected for a specific function and predict some information.

[0027] The terminal device or network device may operate in multiple frequency ranges, such as FR1 (410 MHz to 7125 MHz), FR2 (24.25 GHz to 71 GHz), frequency bands above 100 GHz, and terahertz (THz). Furthermore, it can operate in licensed / unlicensed / shared spectrum. The terminal device may have multiple connections with the network device in a multi-radio dual connectivity (MR-DC) application scenario. The terminal device or network device can operate in full duplex, flexible duplex, and cross-division duplex modes.

[0028] Embodiments of the present disclosure may be implemented in test equipment, such as, for example, a signal generator, a signal analyzer, a spectrum analyzer, a network analyzer, a test terminal equipment, a test network equipment, a channel emulator, and the like.

[0029] Embodiments of the present disclosure may be performed in accordance with any generation of communication protocols now known or developed in the future, including, but not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or sixth generation (6G) networks.

[0030] As used herein, the term "circuitry" may refer to a hardware circuit and / or a combination of a hardware circuit and software. For example, a circuit may be a combination of analog and / or digital hardware circuitry with software / firmware. As a further example, a circuit may be any portion of a hardware processor with software, such as a digital signal processor, software, and memory that cooperate to perform various functions in a device, such as a terminal device or network device. In yet another example, a circuit may be a hardware circuit and / or processor, such as a microprocessor or portion of a microprocessor, that requires software / firmware for operation but may be absent when not required for operation. As used herein, the term circuitry also encompasses a simple hardware circuit or processor, or portion of a hardware circuit or processor, and its (or their) accompanying software and / or firmware implementation.

[0031] As mentioned above, NTNs can provide wide network coverage. Currently, NTNs can have different types of satellites (or UAS platforms). Table 1 shows some examples of satellite types.

[0032] Table 1. Types of Satellite / UAS Platforms [Table 1]

[0033] Additionally, NTNs are typically characterized by the following elements: One or more satellite gateways (sat-gateways) connecting the NTN to the public data network - GEO satellites are fed by one or more satellite gateways located across the satellite's target coverage (e.g., regional or continental coverage). UEs within a cell are assumed to be served by only one satellite gateway. - Non-GEO satellites are continuously served by one or more satellite gateways at a time. The system ensures continuity of service and feeder links between the continuously serving satellite gateways with sufficient time to allow mobility anchoring and handover to proceed. Feeder links or radio links between the satellite gateway and the satellite (or UAS platform) Service or radio links between user equipment and satellites (or UAS platforms) A satellite (or UAS platform) that can be equipped with either a transparent payload or a regenerative (with on-board processing) payload. The satellite (or UAS platform) generates a beam, typically multiple beams, over a given serving area limited by its field of view. The beam footprint is typically elliptical. The field of view of the satellite (or UAS platform) depends on the onboard antenna diagram and minimum elevation angle. - Transparent payload: Radio frequency filtering, frequency conversion and amplification, so the waveform signal repeated by the payload remains unchanged. - Regenerative payloads: Radio frequency filtering, frequency conversion and amplification, as well as demodulation / decoding, switching and / or routing, coding / modulation, which effectively equates to putting all or part of a base station function (e.g. gNB) on a satellite (or UAS platform). Inter-Satellite Links (ISLs) are an option for satellite constellations. They require on-board regenerative payloads. ISLs may operate at RF frequencies or in the optical band. The UE is served by a satellite (or UAS platform) within a targeted coverage area.

[0034] Currently, NTNs are being developed to support IoT and enhanced machine-type communication (eMTC) scenarios. Examples of IoT NTNs are shown below. Scenario A: GEO-based non-terrestrial access network Scenario B: LEO-based non-terrestrial access network with steerable beams (altitude 1200km, 600km) Scenario C: LEO-based non-terrestrial access network generating fixed beams with a moving footprint along with the satellite (altitude 1200 km, 600 km). Scenario D: MEO-based non-terrestrial access network generating fixed beams with a footprint that moves with the satellite (altitude 10,000 km)

[0035] As mentioned above, it has been agreed that discontinuous coverage will be supported in the NTN. To date, both the terminal device and the CN device have generally been unable to obtain the coverage status of the network. As a result, for the CN device, the CN device does not realize that the terminal device is out of coverage and still attempts to initiate the necessary paging procedure for the terminal device. This paging failure due to discontinuous coverage is temporary and intermittent. However, the CN device cannot understand that the paging failure is due to discontinuous coverage, so it transitions the terminal device to a deregistered state. In this case, if the terminal device wants to re-enter network coverage and communicate with the network, the terminal device must perform an initial registration or PDU establishment procedure.

[0036] For the terminal, the terminal will continue to make measurements and monitor paging messages since it will not know that it is out of coverage.

[0037] As can be seen, discontinuous coverage scenarios are not handled properly, resulting in undesirable power / signal consumption and unexpected registration state transitions in the terminal and CN devices.

[0038] Although several mechanisms have been proposed to reduce the unwanted power consumption / signaling overhead, these mechanisms are not applicable to discontinuous coverage scenarios. For example, traditional mechanisms to reduce the unwanted power consumption / signaling overhead include Discontinuous Reception (DRX), Extended Discontinuous Reception (eDRX), PSM, and relaxed monitoring.

[0039] Please refer to Figure 1. Figure 1 shows an exemplary pattern 100 of a conventional PSM. In the conventional solution shown in Figure 1, if a UE is capable of adopting PSM and wants to use PSM, the UE must request an active time value and may request a periodic TAU timer value for each Attach and Tracking Area Update (TAU) procedure. Furthermore, if the UE has not requested an active time value, the UE should not request a periodic TAU timer value. Therefore, if the UE has not requested an active time value, the network should not assign an active time value.

[0040] If the network assigns an active time value, the UE and MME start an active timer with the network-assigned active time value when transitioning from connected mode to idle mode. The UE must stop the active timer if it is running when the transition to connected mode is made. When the active timer expires, the UE deactivates the access stratum functionality and enters PSM. In PSM, deactivation of access stratum functionality causes the UE to stop all idle mode procedures, but continues to run any applicable non-access stratum timers, such as the periodic TAU timer.

[0041] Furthermore, the UE must resume access stratum functionality and idle mode procedures, if applicable, before the expiration of the periodic TAU timer for performing the periodic TAU procedure. The UE may resume idle mode procedures and access stratum functionality at any time during PSM, for example, for mobile origination. When the active timer for the UE expires, the MME recognizes that the UE has entered PSM and is unavailable for paging.

[0042] As is apparent, in conventional solutions, the MME assigns a fixed TAU timer value and a fixed active time value without considering the network coverage state at all. Therefore, it is desirable to propose a solution for discontinuous coverage scenarios that can reduce undesired power consumption / signaling overhead and avoid unexpected registration state transitions.

[0043] To address these and other potential issues, embodiments of the present disclosure provide an effective mechanism for dealing with discontinuous coverage scenarios, whereby terminal devices and CN devices can obtain information indicative of network coverage. Such information allows the terminal devices and CN devices to reduce undesirable power consumption / signaling overhead and avoid unexpected registration state transitions.

[0044] The principles and exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings.

[0045] In the following, a satellite is used as an example of an access network device to describe some specific exemplary embodiments of the present disclosure, and it should be noted that the exemplary embodiments described with respect to a satellite are equally applicable to other types of access network devices.

[0046] In the following description, the terms "period," "window," "period," and "interval" may be used interchangeably.

[0047] The term "at least one first period" is incorporated in the description of the terminal device. During the at least one first period, the terminal device considers that the terminal device is located within the coverage of the network. Similarly, the term "at least one second period" is incorporated in the description of the CN device. During the at least one second period, the CN device considers that the terminal device is located within the coverage of the network.

[0048] It should be noted that in this disclosure, the above "at least one first period" and "at least one second period" are associated with coverage conditions in the network and do not necessarily refer to the actual coverage conditions in the network.

[0049] Furthermore, in some exemplary embodiments, "at least one first period" is the same as "at least one second period," while in some other exemplary embodiments, "at least one first period" is different from "at least one second period."

[0050] The terminal device may also obtain the "at least one first period" in various ways. In one exemplary embodiment, the terminal device acquires / collects information (ephemeris, constellation almanac, etc.) and locally calculates / derives the at least one first period. In another exemplary embodiment, the terminal device 210 obtains the at least one first period from a configuration (referred to as a "first configuration") sent from another network device (e.g., an access network device or a CN device).

[0051] Additionally, the procedure by which the CN device obtains the "at least one second period" is similar to the procedure discussed with respect to the terminal device obtaining the "at least one first period." Specifically, the CN device may locally calculate / derive the at least one second period, or may obtain the at least one second period from a configuration (referred to as a "second configuration") sent from another network device (such as an access network device or a terminal device).

[0052] In this disclosure, the term "time information" is used to describe an access network device. "Time information" refers to information associated with the coverage status of a network. As an example of a specific embodiment, an access network device collects information associated with the coverage information of neighboring access network devices via a feeder link with a CN or an ISL with a neighboring access network device, and determines time information based on the collected information and its own coverage information.

[0053] It should be noted that in the present disclosure, "time information," "at least one first period," "at least one second period," "first setting," and "second setting" may be represented / shown in any suitable manner / parameter.

[0054] Furthermore, in this disclosure, the "time information," "at least one first period," and "at least one second period" may also be referred to as a "serving time" / "serving window."

[0055] Example Environment 2 illustrates an exemplary communication environment 200 in which exemplary embodiments of the present disclosure can be implemented. The communication environment 200 includes a terminal device 210, an access network device 230-1 serving the terminal device 210, and a further access network device 230-2. In the following text, the access network devices 230-1 and 230-2 are collectively referred to as access network devices 230 or individually as network devices 230. Furthermore, one or more ISLs may be established between the access network device 230-1 and the access network device 230-2.

[0056] Furthermore, either of the access network devices 230-1 and 230-2 may provide one or more serving areas (sometimes referred to as "cells") to the terminal device 210. In the example of Figure 2, the access network device 230-1 provides the serving area 235-1, and the access network device 230-2 provides the serving area 235-2. Hereinafter, the serving areas 235-1 and 235-2 will be collectively referred to as serving area 235, or will be individually referred to as serving area 235.

[0057] Terminal device 210 may communicate with each access network device 230 via a service link, a wireless link, etc., when the terminal device is within the serving area 235 of each access network device 230. Communication in the direction from terminal device 210 to access network device 230 is referred to as uplink communication, and communication in the reverse direction from access network device 230 to terminal device 210 is referred to as downlink communication.

[0058] 2, both terminal device 210 and access network device 230 may move over time. During movement, terminal device 210 may be located in different serving areas 235 and may even be outside of network coverage.

[0059] In the example of FIG. 2, the terminal device 210 may be in different states (connected, inactive, idle, etc.) and may be operated with power saving mechanisms including, but not limited to, DRX, eDRX, PSM, relaxed supervision, etc.

[0060] The communication environment 200 further includes a CN 225. The CN 225 may further include multiple CN devices (e.g., the CN device 220 shown in FIG. 2). The access network devices 230-1 and 230-2 may be connected to the CN device 220 via a feeder link, a wireless link, or the like.

[0061] Communications within communication environment 200 may conform to any suitable standard, including, but not limited to, Long Term Evolution (LTE), LTE Evolution (LTE-Evolution), LTE Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), and Global System for Mobile Communications (GSM). Furthermore, communications may be performed according to any currently known or future-developed generation of communications protocol. Examples of communications protocols include, but are not limited to, first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), 5.5G, 5G-Advanced, or sixth-generation (6G) communications protocols.

[0062] It should be understood that the number of access network devices, terminal devices, CN devices, CNs, and serving areas and their connections are for illustrative purposes only and do not imply any limitations. Communications environment 200 may include any suitable access network devices, terminal devices, CN devices, CNs, and serving areas suitable for implementing embodiments of the present disclosure. Although not shown, it should be understood that communications environment 200 may include one or more additional network devices, such as earth stations, gateways, etc.

[0063] Example Process The principles and implementations of the present disclosure are described in detail below with reference to Fig. 3. Fig. 3 shows a signaling chart illustrating a process 300 of communication according to some exemplary embodiments of the present disclosure. For discussion purposes, the process 300 will be described with reference to Fig. 2. The process 300 may involve a terminal device 210, a CN device 220, and an access network device 230.

[0064] 3, the communication network is a NTN that supports discontinuous coverage, and the access network device 230 is a satellite or UAS platform.

[0065] During operation, terminal device 210 receives a first configuration indicating at least one first period during which terminal device 210 is within the coverage of the network. In one exemplary embodiment, terminal device 210 receives 350-1 the first configuration from access network device 230. In another exemplary embodiment, terminal device 210 receives 350-2 the first configuration from CN device 220.

[0066] It should be appreciated that, alternatively, in some other exemplary embodiments, terminal device 210 may collect information related to network coverage and then calculate / derive the first period by itself. In this manner, terminal device 210 may obtain network coverage information.

[0067] Similarly, CN device 220 may also receive (350-2) a second configuration indicating at least one second time period during which terminal device 210 is within the coverage of the network. In one exemplary embodiment, CN device 220 receives (330-2) the second configuration from access network device 230. In another exemplary embodiment, CN device 220 receives the second configuration from terminal device 210.

[0068] It should be appreciated that, alternatively, in some other exemplary embodiments, CN device 220 may collect information related to network coverage and then calculate / derive the second period by itself. In this manner, CN device 220 may obtain network coverage information.

[0069] As described above, the first configuration and the second configuration may be transmitted by the access network device 230. Specifically, the access network device 230 may determine time information when the terminal device 210 is located within the coverage of the network (430). Then, the access network device 230 transmits the first configuration to the terminal device 210, while transmitting the second configuration to the CN device 220.

[0070] Furthermore, access network device 230 may transmit the first and second configurations at any appropriate opportunity or in response to some predefined event. In one exemplary embodiment, access network device 230 transmits the first and second configurations in response to terminal device 210 transitioning from a connected state to an idle mode (e.g., an RRC idle state) (e.g., access network device 230 determines (340) that terminal device 210 will transition to an RRC idle state). In another exemplary embodiment, access network device 230 transmits the first and second configurations when terminal device 210 is in a connected state (e.g., an RRC connected state). It should be understood that transitioning from a connected state to an idle mode is provided for illustrative purposes only and does not imply any limitation. In other exemplary embodiments, if other power saving mechanisms are operating in the network, access network device 230 may transmit the first and second configurations in response to other appropriate state transitions. The present disclosure is not limited in this respect.

[0071] In some exemplary embodiments, access network device 230 conditionally transmits the first and second configurations. In one exemplary embodiment, access network device 230 transmits the first and second configurations only if access network device 230 receives a first message requesting the first configuration from terminal device 210. Alternatively, in another exemplary embodiment, access network device 230 transmits the first and second configurations regardless of whether terminal device 210 requests the first configuration.

[0072] In this manner, the access network device 230 may notify both the terminal device 210 and the CN device 220 of network coverage information (i.e., serving time), thereby allowing the terminal device 210 and the CN device 220 to maintain consistency regarding the reachability of the terminal device 210.

[0073] Additionally, in some exemplary embodiments, access network device 230 determines the time information based on information such as the speed of terminal device 210, the direction of movement of terminal device 210, the location of terminal device 210, ephemeris / constellation almanacs of its own and neighboring access network devices, etc. In this manner, the time information may be determined in a terminal-specific manner, and the accuracy of the determined time information is correspondingly improved.

[0074] This functionality / feature may also be optionally enabled or supported in the network. In some example embodiments, the access network device 230 sends 310 an indication that the access network device 230 supports the first configuration. The indication may be used as capability information for the access network device 230 and may further be used as an indication to enable this functionality / feature within the network.

[0075] Furthermore, the indication may be transmitted in any suitable manner. In one exemplary embodiment, the access network device 230 may transmit the indication in a broadcast manner in system information (SI).

[0076] In some exemplary embodiments, terminal device 210 may also send 320 a first message to access network device 230 to request the first configuration. Further, in some exemplary embodiments, terminal device 210 sends the first message only if access network device 230 receives an indication indicating that it supports configuring the first configuration. In this manner, this function / feature may be implemented as an optional function / feature, and terminal device 210 may determine whether to enable the function / feature.

[0077] Furthermore, the first message may include one or more service characteristics or user preferences. In one exemplary embodiment, the first message includes user preference information indicating an expected period for communicating with the network. In this way, the first configuration generated for the terminal device 210 can be more reasonable.

[0078] As already specified, the at least one first time period, the at least one second time period, and the time period corresponding to the time information do not necessarily refer to the actual coverage conditions in the network.

[0079] Please refer to FIG. 4. FIG. 4 illustrates an example of at least one first time period (or at least one second time period). In the example of FIG. 4, three access network devices, such as access network device 230-1 (denoted as "S1" in FIG. 4), access network device 230-2 (denoted as "S2" in FIG. 4), and an additional access network device (denoted as "S3" in FIG. 4), may provide serving areas in a network. Periods 410-1 and 410-2 correspond to serving periods provided by access network device 230-1, periods 420-1 and 420-2 correspond to serving periods provided by access network device 230-2, and periods 430-1 and 430-2 correspond to serving periods provided by the additional access network device. Furthermore, access network device 230-1 is serving terminal device 210.

[0080] Details of the at least one first period will be discussed below with reference to Figure 4. In the specific example of Figure 4, periods 440-1 to 440-4 correspond to the at least one first period.

[0081] In some exemplary embodiments, the at least one first time period may cover only a portion of the access network devices in the network. As shown in Figure 4, the at least one first time period pertains only to access network device 230-1 (i.e., S1) and access network device 230-2 (i.e., S2).

[0082] Alternatively, it should be appreciated that in some exemplary embodiments, at least one first time period is associated only with a particular access network device (eg, serving access network device 230-1).

[0083] In some exemplary embodiments, the at least one first period is periodic. In this case, the at least one first period may be represented by a period of the at least one first period and a respective duration of the at least one first period. Furthermore, either the period or the duration may be set as a default value. In that case, either the period or the duration may be omitted when representing the at least one first period.

[0084] Alternatively, the at least one first period may be aperiodic, in which case the at least one first period may be indicated by information of multiple serving times (e.g., T times, where T is greater than zero) within the next period.

[0085] In some exemplary embodiments, any of the at least one first time period may be provided by a current serving access network device (e.g., S1) or any of its neighboring access network devices (e.g., S2, S3, etc.), and each of the first time periods may be indicated by a start time and an end time.

[0086] It should be understood that the above-described exemplary embodiments of the at least one first time period are provided for illustrative purposes only, and in other exemplary embodiments, the at least one first time period may be in any suitable manner (periodic or non-periodic) and may be represented / indicated by any suitable parameters.

[0087] The at least one second period is similar to the at least one first period, i.e., the above description of the first period is also applicable to the at least one second period, and for the sake of brevity only, identical or similar descriptions will be omitted here.

[0088] It should be understood that the first and second time periods should correspond to one another so that the operations of the terminal device 210 and the CN device are consistent with one another. However, the first and second time periods need not be exactly the same. As noted above, at least one first time period and at least one second time period may be different. In one exemplary embodiment, at least one second time period has a length longer than the corresponding first time period.

[0089] Through the above process, network elements (including the terminal device 210, the CN device 220, and the access network device 230) can obtain the coverage status in the network, and the network elements can behave rationally with higher power efficiency.

[0090] In some exemplary embodiments, terminal device 210 performs normal idle mode operation within at least one first period (360-1) while disabling normal idle mode operation beyond the at least one first period (360-2). One example of normal idle mode operation is performing a cell search. Another example of normal idle mode operation is performing measurements for cell reselection. A further example of idle mode operation is normal monitoring for paging messages. In one specific example, terminal device 210 performs paging message monitoring. Monitoring for paging messages includes first monitoring downlink control information messages and proceeding with receiving paging messages based on the monitoring results.

[0091] In addition to the above examples, normal idle mode operation may include, but is not limited to: Monitor System Information (SI) updates and update SI based on the monitoring results. Performs sending and receiving sidelink communications. Performs Sidelink discovery announcements and monitoring. Performs V2X sidelink communication transmission and reception. Performs NR sidelink communication transmission and reception. Sending and receiving V2X sidelink communications. · Implement Mobile Originated Early Data Transmission (MO-EDT). · Implement Mobile Terminated Early Data Transmission (MO-EDT). · Perform transmission using reconfigured uplink resources (PUR).

[0092] It should be understood that the above examples are not intended to be exhaustive of normal idle mode operation, but rather to provide a better understanding of operations that may be supported within at least one first period.

[0093] Furthermore, the above procedures may be performed in coordination with other mechanisms (DRX, eDRX, PSM, relaxed monitoring, etc.) In one exemplary embodiment, terminal device 210 monitors for paging messages using DRX and / or eDRX within at least one first period.

[0094] In this way, unnecessary operations of the terminal device 210 are avoided when at least one period has been exceeded, and power consumption in the terminal device 210 is reduced.

[0095] With respect to the CN device 220 (such as an MME), the CN device 220 may infer (370-1) that the terminal device 210 is reachable within at least one second period, while inferring (370-2) that the UE is unreachable beyond at least one second period.

[0096] In some exemplary embodiments, if CN device 220 detects a paging failure within at least one second period (e.g., if CN device 220 fails to receive a response to a paging message from terminal device 210), CN device 220 sends a downlink data notification rejection message to notify the SGW about the paging failure.

[0097] Alternatively or additionally, in some exemplary embodiments, if CN device 220 detects expiration of a reachable timer (i.e., a timer corresponding to or similar to a periodic TAU timer), CN device 220 infers that the UE is not reachable. Furthermore, CN device 220 does not immediately delete the bearers of terminal device 210. Instead, CN device 220 clears its PPF flag and starts an implicit detach timer. If the implicit detach timer expires before terminal device 210 contacts the network, CN device 220 implicitly detaches terminal device 210.

[0098] In some exemplary embodiments, after receiving the second configuration, CN device 220 directly indicates to the SGW that terminal device 210 will be unreachable for a certain period of time. That is, CN device 220 notifies the SGW of the coverage interruption along with a predicted suspension time of downlink data. The predicted suspension time may be determined based on at least one second period. Specifically, after receiving the second configuration, CN device 220 transmits first information to the SGW indicating a first available time for receiving downlink data of terminal device 210. Here, the first available time is determined based on the second configuration.

[0099] Alternatively or additionally, in some exemplary embodiments, CN device 220 clears the PPF flag of terminal device 210 for more than at least one second period. Alternatively, in some exemplary embodiments, CN device 220 does not clear the PPF flag, but instead disables the PPF flag of terminal device 210 for more than at least one second period. In some exemplary embodiments, CN device 220 may start a timer (referred to as "Timer A"), and upon expiration of the timer, CN device 220 may consider terminal device 210 unreachable (i.e., out of coverage). Furthermore, upon expiration of Timer A, CN device 220 starts an implicit detach timer.

[0100] In some exemplary embodiments, if CN device 220 receives a downlink data notification for terminal device 210 from the SGW for more than at least a second period, CN device 220 sends a rejection message for the downlink data notification to the SGW. Further, the rejection message indicates a second available time (e.g., indicated by a timer value) for receiving downlink data for terminal device 210, where the second available time is determined based on a second setting. For example, if CN device 220 receives a downlink data notification message from the SGW for more than the second period, CN device 220 does not page terminal device 210 and sends a downlink data notification rejection message to the SGW with / including the setting of timer B (indicating the period during which terminal device 210 may again be reachable).

[0101] Using this second period, CN device 220 may distinguish between different unreachable situations (e.g., situations caused by discontinuous coverage and situations caused by other reasons (such as the terminal device being powered off)). As a result, CN device 220 may take different actions based on the second period when detecting a paging failure or receiving a downlink data notification. Furthermore, terminal device 210 and CN device 220 can maintain consistency regarding reachability between terminal device 210 and CN device 220, thereby avoiding unnecessary power consumption due to frequently performing initial registration when terminal device 210 returns to coverage (i.e., avoiding implicit detach operations when the terminal device is out of coverage due to discontinuous serving).

[0102] It should be noted that the operations at the terminal device 210 and the CN device 220 should be consistent. For illustrative purposes only, one particular process will be described with reference to FIG. 5, which shows another signaling diagram illustrating a communication process 500 according to some embodiments of the present disclosure. For discussion purposes, the process 500 will be described with reference to FIG. 2. The process 500 may involve the terminal device 210, the CN device 220, and an SGW (not shown in FIG. 2).

[0103] During operation, the terminal device 210 and the CN device 220 maintain reachability agreement with each other (510). For example, the terminal device 210 receives at least one first period, and the CN device 220 receives at least one second period.

[0104] Within the reachable period (i.e., within at least one of the first and second periods), terminal device 210 performs normal idle mode operation as described above (520). As for CN device 220, CN device 220 maintains a mobile reachable timer based on the second period. When the mobile reachable timer expires, CN device 220 clears or disables the PPF of terminal device 210 (530). If the mobile reachable timer expires and CN device 220 receives a downlink data notification message from the SGW (540), CN device 220 responds with a downlink data notification rejection message to the SGW (550). Alternatively, if the mobile reachable timer has not expired, terminal device 210 may be paged according to a common paging strategy.

[0105] Within the unreachable period (i.e., exceeding at least one first / second period), terminal device 210 disables unnecessary idle mode operation (560). As for CN device 220, CN device 220 clears or disables the PPF flag for the unreachable period determined based on at least one second period (570). If the mobile reachable timer expires and CN device 220 receives a downlink data notification message from the SGW (580), CN device 220 responds with a downlink data notification rejection message to the SGW (590). Here, the downlink data notification rejection message may include a parameter indicating a period during which terminal device 210 may again be reachable.

[0106] In wireless communications, network elements (including terminal devices 210, CN devices 220, and access network devices 230) may maintain one or more timers to control communications within the network. In some exemplary embodiments, maintenance of associated timers may also be refined as a function of reachability / coverage information (i.e., serving time).

[0107] In some exemplary embodiments, terminal device 210 starts a first timer for controlling communication with the network and further pauses the first timer for at least one first period. When terminal device 210 is in an idle state, the first timer may be associated with a TAU timer. Alternatively, when terminal device 210 is in a connected state, the first timer may be associated with an on-duration timer (onDurationTimer), a discontinuous reception inactivity timer (drx-InactivityTimer), a discontinuous reception retransmission timer (drx-RetransmissionTimer), or a discontinuous reception short cycle timer (drxShortCycleTimer).

[0108] An example of a specific embodiment for maintaining associated timers will be described with reference to Figure 6. Figure 6 shows an exemplary process 600 for maintaining associated timers. For purposes of discussion, process 600 will be described with reference to Figure 4. Like reference numbers used in Figure 6 have the same physical meaning as shown in Figure 4.

[0109] 6, terminal device 210 starts a first timer at time t1. In one exemplary embodiment, if the first timer is associated with a TAU timer, terminal device 210 starts the first timer when terminal device 210 transitions from a connected state to an idle state.

[0110] Next, when the terminal device 210 leaves the coverage of the network (i.e., beyond the first period), the terminal device 210 pauses the first timer. In the specific example of Fig. 6, the terminal device 210 pauses the first timer at time points t2 and t4. Furthermore, when the terminal device 210 returns to the coverage of the network again (i.e., within the first period), the terminal device 210 restarts / continues the first timer. In the specific example of Fig. 6, the terminal device 210 restarts / continues the first timer at time points t3 and t5.

[0111] Thereafter, at time t6, the first timer expires and the terminal device may trigger a corresponding operation, such as initiating a TAU procedure.

[0112] As already stated, the operation at the terminal device must be consistent with that at the network side, i.e., if the timer maintenance procedures at the terminal device 210 are improved, the corresponding timers maintained by the access network device 230 and the CN device 220 must be improved accordingly.

[0113] Specifically, in some exemplary embodiments, CN device 220 starts a second timer for controlling communications with terminal device 210 and pauses the second timer for at least one second period. Further, in some exemplary embodiments, the second timer is associated with a TAU timer (such as a mobile reachable timer).

[0114] With respect to access network device 230, in some exemplary embodiments, access network device 230 starts a third timer for controlling communications with terminal device 210 and pauses the third timer for more than at least one period corresponding to at least one first period. Also, in some exemplary embodiments, the third timer is associated with an on-duration timer (onDurationTimer), a discontinuous reception inactivity timer (drx-InactivityTimer), a discontinuous reception retransmission timer (drx-RetransmissionTimer), or a discontinuous reception short cycle timer (drxShortCycleTimer).

[0115] The maintenance operations of the second and third timers are similar to that of the first timer, and for the sake of brevity, the same or similar descriptions will be omitted here.

[0116] Furthermore, as mentioned above, both the terminal device 210 and the access network device 230 may move over time, which may cause the determined time information / first setting / second setting to become inappropriate / invalid. According to some example embodiments of the present disclosure, the determined time information / first setting / second setting may be dynamically updated.

[0117] In some exemplary embodiments, the access network device 230 may determine the time information and periodically transmit the first configuration and the second configuration to the terminal device 210 and the CN device 220 .

[0118] Alternatively, in some exemplary embodiments, the determined time information / first setting / second setting may be updated according to some specific conditions.

[0119] In some exemplary embodiments, if terminal device 210 determines that the first setting is at least partially invalid, terminal device 210 sends a second message to access network device 230 serving terminal device 210 to update the first setting.

[0120] The second message may be sent to the access network device at any appropriate opportunity. In one exemplary embodiment, terminal device 210 initiates an access procedure (i.e., sends the second message) to update the first configuration upon returning to coverage. In another exemplary embodiment, terminal device 210 initiates the update of the first configuration the next time terminal device 210 accesses the network.

[0121] In some example embodiments, when access network device 230 receives the second message for updating the first setting from terminal device 210, access network device 230-1 determines updated time information for terminal device 210. Then, access network device 230-1 transmits the updated first setting associated with the determined updated time information to terminal device 210 and transmits the updated second setting associated with the determined updated time information to CN device 220.

[0122] Furthermore, terminal device 210 may determine that the first configuration is at least partially invalid according to any suitable criteria. In some exemplary embodiments, terminal device 210 determines that the first configuration is at least partially invalid if the distance traveled by terminal device 210 within an evaluation period (referred to as "T_evaluate") exceeds a distance threshold (referred to as "D_ref"). In one example of a specific embodiment, terminal device 210 infers that the first configuration is no longer appropriate if it finds that its distance from a reference point is not greater than or less than D_ref, where the reference point is the location where terminal device 210 receives the first configuration. In one example of a specific embodiment, terminal device 210 evaluates changes in this distance at least every T_evaluate.

[0123] Alternatively, in some exemplary embodiments, if the time period during which terminal device 210 fails to communicate with the network within one of at least one first time period (referred to as "T_difference") exceeds a time threshold (referred to as "T_ref"), terminal device 210 determines that the first configuration is at least partially invalid. In other words, if T_difference within the first time period exceeds T_ref, terminal device 210 determines that the first configuration is at least partially invalid.

[0124] See Figure 7. Figure 7 shows an example 700 of the correspondence between the first period and the actual coverage period.

[0125] As shown in FIG. 7, the first configuration indicates that coverage begins at time T1, and the actual measurement indicates that coverage begins at time T2. That is, the actual coverage begins later than expected. The time difference is represented as T_difference=T2-T1, i.e., time difference 710, as shown in FIG. 7. In this example, if T_difference=T2-T1>T_ref, terminal device 210 determines that the first configuration is at least partially invalid.

[0126] Terminal device 210 may also recognize that actual coverage starts later than expected and may further determine a delay period (i.e., T_difference), and thus terminal device 210 may extend the first period by T_difference. Furthermore, information about T_difference may also be reported to access network device 230 via a second message for updating the first setting, or the like.

[0127] Continuing with reference to FIG. 7, the first configuration indicates that coverage ends at time T4, while the actual measurement indicates that coverage ends at time T3. That is, the actual coverage starts earlier. As shown in FIG. 7, the time difference is represented as T_difference=T4−T3, i.e., time difference 720. In this example, if T_difference=T4−T3>T_ref, terminal device 210 determines that the first configuration is at least partially invalid.

[0128] Additionally, the parameters and criteria used by the terminal device to determine the validity of the first configuration may be configured by access network device 230. For example, in some exemplary embodiments, access network device 230 transmits a third message to terminal device 210. The third message may include information indicating at least one of a distance threshold, an evaluation period, and a time threshold.

[0129] It should be understood that the above examples for determining whether the first setting is at least partially invalid are for illustrative purposes only and are not intended to imply any limitation. In other exemplary embodiments, terminal device 210 may apply any suitable criteria to determine whether the first setting is at least partially invalid. The present disclosure is not limited in this respect.

[0130] Exemplary Methods 8 illustrates a flowchart of an example method 800 according to some embodiments of the present disclosure. For example, the method 800 may be implemented in the terminal device 210 shown in FIG.

[0131] At block 810, terminal device 210 receives a first configuration indicating at least one first period during which terminal device 210 is within coverage of a network.

[0132] In block 820, terminal device 210 performs at least one of performing a cell search, performing measurements for cell reselection, or monitoring for paging messages within at least one first time period.

[0133] In some exemplary embodiments, terminal device 210 disables at least one of performing cell search, performing measurements for cell reselection, or monitoring for paging messages for more than at least one first period.

[0134] In some exemplary embodiments, terminal device 210 receives an indication from access network device 230 indicating that access network device 230 serving terminal device 210 supports configuration of the first configuration.

[0135] In some exemplary embodiments, terminal device 210 sends a first message to access network device 230 serving terminal device 210 to request a first configuration.

[0136] In some exemplary embodiments, the first message includes user preference information indicating an expected periodicity for communicating with the network.

[0137] In some exemplary embodiments, the at least one first period is periodic, and the first setting indicates a period of the at least one first period or one of each period of the at least one first period.

[0138] In some exemplary embodiments, terminal device 210 starts a first timer for controlling communication with a network and pauses the first timer for at least one first period of time.

[0139] In some exemplary embodiments, the first timer is associated with one of a tracking area update timer (TAU timer), an on-duration timer (onDurationTimer), a discontinuous reception inactivity timer (drx-InactivityTimer), a discontinuous reception retransmission timer (drx-RetransmissionTimer), or a discontinuous reception short cycle timer (drxShortCycleTimer).

[0140] In some exemplary embodiments, terminal device 210 determines that the first setting is at least partially invalid and sends a second message to access network device 230 serving terminal device 210 to update the first setting.

[0141] In some exemplary embodiments, terminal device 210 determines that the first setting is at least partially invalid if the distance traveled by terminal device 210 within the evaluation period exceeds a distance threshold.

[0142] In some exemplary embodiments, if the period during which terminal device 210 fails to communicate with the network within one of at least one first period exceeds a time threshold, terminal device 210 determines that the first setting is at least partially invalid.

[0143] In some exemplary embodiments, terminal device 210 receives a third message from access network device 230. The third message includes information indicating at least one of a distance threshold, an evaluation period, or a time threshold.

[0144] 9 shows a flowchart of an exemplary method 900 according to some embodiments of the present disclosure. For example, the method 900 can be implemented in the CN device 220 as shown in FIG.

[0145] At block 910, the CN device 220 receives a second configuration indicating at least one second period during which the terminal device 210 is located within the coverage of the network.

[0146] In block 920, CN device 220 clears or disables the paging progress element flag for terminal device 210 within at least one second time period.

[0147] In some demonstrative embodiments, the at least one second period is a periodic resource, and the second configuration indicates a period of the at least one second period or one of the respective periods of the at least one second period.

[0148] In some embodiments, after receiving the second setting, the CN device 220 transmits first information to the SGW indicating a first available time for receiving downlink data of the terminal device 210 based on the second setting.

[0149] In some example embodiments, upon receiving a downlink data notification for terminal device 210 from the serving gateway for more than at least one second period, CN device 220 sends a rejection message for the downlink data notification to the SGW. The rejection message indicates a second available time for receiving the downlink data for terminal device 210. The second available time is determined based on a second setting.

[0150] In some exemplary embodiments, CN device 220 starts a second timer for controlling communications with terminal device 210 and pauses the second timer for at least one second period.

[0151] In some exemplary embodiments, the second timer is associated with a tracking area update timer (TAU timer).

[0152] 10 shows a flowchart of an example method 1000 according to some embodiments of the present disclosure. For example, the method 1000 can be implemented in the access network device 230 as shown in FIG.

[0153] In block 1010, the access network device 230 serving the terminal device determines time information when the terminal device 210 is located within the coverage of the network.

[0154] In block 1020, the access network device 230 transmits a first setting to the terminal device 210 indicating at least one first period to be used by the terminal device 210, and transmits a second setting to the CN device 220 indicating at least one second period to be used by the CN device 220, based on the determined time information.

[0155] In some exemplary embodiments, access network device 230 sends an indication to terminal device 210 indicating that access network device 230 supports configuration of the first configuration.

[0156] In some exemplary embodiments, access network device 230 receives a first message from terminal device 210 to request a first configuration.

[0157] In some exemplary embodiments, the first message includes user preference information indicating an expected periodicity for communicating with the network. The access network device 230 determines the time information based on the user preference information.

[0158] In some exemplary embodiments, access network device 230 receives a second message from terminal device 210 for updating the first setting, determines updated time information for terminal device 210, transmits an updated first setting associated with the determined updated time information to terminal device 210, and transmits an updated second setting associated with the determined updated time information to CN device 220.

[0159] In some exemplary embodiments, access network device 230 transmits a third message to terminal device 210 that includes information used by terminal device 210 to determine the validity of the first configuration, the information indicating at least one of a distance threshold, an evaluation period, or a time threshold.

[0160] In some exemplary embodiments, access network device 230 transmits the first configuration and the second configuration in response to terminal device 210 transitioning from a connected state to an idle state.

[0161] In some exemplary embodiments, the access network device 230 starts a third timer for controlling communications with the terminal device 210 and pauses the third timer for more than at least one period corresponding to the at least one first period.

[0162] In some exemplary embodiments, the third timer is associated with one of an on-duration timer (onDurationTimer), a discontinuous reception inactivity timer (drx-InactivityTimer), a discontinuous reception retransmission timer (drx-RetransmissionTimer), or a discontinuous reception short cycle timer (drxShortCycleTimer).

[0163] Exemplary Apparatus In some exemplary embodiments, terminal device 210 comprises circuitry configured to receive a first setting indicating at least one first time period during which terminal device 210 is located within the coverage of the network, and to perform at least one of performing a cell search, performing measurements for cell reselection, or monitoring for paging messages during the at least one first time period.

[0164] In some demonstrative embodiments, the circuitry is further configured to disable at least one of performing a cell search, performing measurements for cell reselection, or monitoring for paging messages beyond at least one first period.

[0165] In some exemplary embodiments, the circuitry is further configured to receive an indication from the access network device 230 indicating that the access network device 230 serving the terminal device 210 supports the configuration of the first setting.

[0166] In some exemplary embodiments, the circuitry is further configured to send a first message to an access network device 230 serving the terminal device 210 to request the first configuration.

[0167] In some exemplary embodiments, the first message includes user preference information indicating an expected periodicity for communicating with the network.

[0168] In some exemplary embodiments, the at least one first period is periodic, and the first setting indicates a period of the at least one first period or one of each of the at least one first period.

[0169] In some exemplary embodiments, the circuitry is further configured to start a first timer for controlling communication with the network and to pause the first timer for more than at least a first period of time.

[0170] In some exemplary embodiments, the first timer is associated with one of a tracking area update timer (TAU timer), an on-duration timer (onDurationTimer), a discontinuous reception inactivity timer (drx-InactivityTimer), a discontinuous reception retransmission timer (drx-RetransmissionTimer), or a discontinuous reception short cycle timer (drxShortCycleTimer).

[0171] In some exemplary embodiments, the circuitry is further configured to determine that the first setting is at least partially invalid and to send a second message to the access network device 230 serving the terminal device 210 to update the first setting.

[0172] In some exemplary embodiments, the circuitry is further configured to determine that the first configuration is at least partially invalid if the distance traveled by the terminal device 210 within the evaluation period exceeds a distance threshold.

[0173] In some demonstrative embodiments, the circuitry is further configured to determine that the first configuration is at least partially invalid if a period during which the terminal device 210 fails to communicate with the network within one of the at least one first period exceeds a time threshold.

[0174] In some exemplary embodiments, the circuitry is further configured to receive a third message from the access network device 230. The third message includes information indicative of at least one of a distance threshold, an evaluation period, or a time threshold.

[0175] In some exemplary embodiments, the CN device 220 includes circuitry configured to receive a second setting indicating at least one second period during which the terminal device 210 is located within the coverage of the network, and to clear or disable a paging progress element flag for the terminal device 210 within the at least one second period.

[0176] In some demonstrative embodiments, the at least one second period is a periodic resource, and the second configuration indicates a period of the at least one second period or one of the respective periods of the at least one second period.

[0177] In some exemplary embodiments, the circuitry is further configured to, after receiving the second setting, send first information to the serving gateway based on the second setting, the first information indicating a first available time for receiving downlink data of the terminal device 210.

[0178] In some exemplary embodiments, the circuitry is further configured to send a rejection message for the downlink data notification to the serving gateway upon receiving the downlink data notification from the serving gateway for more than at least a second time period for terminal device 210. The rejection message indicates a second available time for receiving the downlink data for terminal device 210, the second available time being determined based on the second setting.

[0179] In some exemplary embodiments, the circuitry is further configured to start a second timer for controlling communication with terminal device 210 and to pause the second timer for more than at least one second period.

[0180] In some exemplary embodiments, the second timer is associated with a tracking area update timer (TAU timer).

[0181] In some exemplary embodiments, the access network device 230 serving the terminal device comprises circuitry configured to determine time information when the terminal device is located within the coverage of the network, and based on the determined time information, transmit a first setting to the terminal device 210 indicating at least one first period to be used by the terminal device 210, and transmit a second setting to the CN device 220 indicating at least one second period to be used by the CN device 220.

[0182] In some exemplary embodiments, the circuitry is further configured to send an indication to terminal device 210 indicating that access network device 230 supports configuration of the first configuration.

[0183] In some exemplary embodiments, the circuitry is further configured to receive a first message from terminal device 210 to request the first configuration.

[0184] In some exemplary embodiments, the first message includes user preference information indicating an expected period for communicating with the network, and the circuitry is further configured to determine the time information based on the user preference information.

[0185] In some exemplary embodiments, the circuitry is further configured to receive a second message from terminal device 210 to update the first setting, determine updated time information for terminal device 210, transmit an updated first setting associated with the determined updated time information to terminal device 210, and transmit an updated second setting associated with the determined updated time information to CN device 220.

[0186] In some exemplary embodiments, the circuitry is further configured to transmit a third message to the terminal device 210 that includes information used by the terminal device 210 to determine the validity of the first setting, the information indicating at least one of a distance threshold, an evaluation period, or a time threshold.

[0187] In some exemplary embodiments, the circuitry is further configured to transmit the first configuration and the second configuration in response to terminal device 210 transitioning from a connected state to an idle state.

[0188] In some demonstrative embodiments, the circuitry is further configured to start a third timer for controlling communication with terminal device 210 and to pause the third timer beyond at least one period corresponding to the at least one first period.

[0189] In some exemplary embodiments, the third timer is associated with one of an on-duration timer (onDurationTimer), a discontinuous reception inactivity timer (drx-InactivityTimer), a discontinuous reception retransmission timer (drx-RetransmissionTimer), or a discontinuous reception short cycle timer (drxShortCycleTimer).

[0190] 11 is a schematic block diagram of an apparatus 1100 suitable for implementing embodiments of the present disclosure. The apparatus 1100 can be considered a further exemplary implementation of the terminal apparatus 210, the access network apparatus 230, and the CN apparatus 220 shown in FIG. 2. Thus, the apparatus 1100 can be implemented in, or at least as part of, the terminal apparatus 210, the access network apparatus 230, and the CN apparatus 220.

[0191] As shown, the apparatus 1100 includes a processor 1110, a memory 1120 coupled to the processor 1110, a suitable transmitter (TX) and receiver (RX) 1140 coupled to the processor 1110, and a communication interface coupled to the TX / RX 1140. The memory 1120 stores at least a portion of a program 1130. The TX / RX 1140 is for bidirectional communication. The TX / RX 1140 has at least one antenna to facilitate communication, although in practice, the access nodes described herein may have multiple antennas. The communication interface may represent any interface required for communication with other network elements, such as an X2 interface for bidirectional communication between eNBs, an S1 interface for communication between a mobility management entity (MME) / serving gateway (S-GW) and an eNB, a Un interface for communication between an eNB and a relay node (RN), or a Uu interface for communication between an eNB and a terminal device.

[0192] The program 1130 may be considered to include program instructions that, when executed by an associated processor 1110, enable the device 1100 to operate in accordance with embodiments of the present disclosure, as discussed herein with reference to FIGS. 2-10. The embodiments herein may be implemented by computer software, hardware, or a combination of software and hardware executable by the processor 1110 of the device 1100. The processor 1110 may be configured to implement various embodiments of the present disclosure. Additionally, the combination of the processor 1110 and the memory 1120 may constitute a processing means 1150 suitable for implementing embodiments of the present disclosure.

[0193] The memory 1120 may be of any type suitable for the local technology network and may be implemented using any suitable data storage technology (e.g., but not limited to, computer-readable non-transitory storage media, semiconductor-based storage devices, magnetic storage devices and systems, optical storage devices and systems, fixed and removable memory, etc.). Although only one memory 1120 is shown in the device 1100, the device 1100 may include multiple physically distinct memory modules. The processor 1110 may be of any type suitable for the local technology network and may include, by way of example and not limitation, one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor configuration. The device 1100 may have multiple processors, e.g., application-specific integrated circuit chips time-slaved to a clock synchronized with the main processor.

[0194] Generally, various embodiments of the present disclosure may be implemented by hardware or special purpose circuits, software, logic, or any combination thereof. Some aspects may be implemented by hardware, while other aspects may be implemented by firmware or software that may be executed by a controller, microprocessor, or other computing device. Various aspects of the embodiments of the present disclosure have been shown and described as block diagrams, flowcharts, or illustrated by some other pictorial representation, and it will be understood that the blocks, apparatus, systems, techniques, or methods described herein may be implemented by, for example, but not limited to, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing device, or combinations thereof.

[0195] The present disclosure further provides at least one computer program product tangibly stored on a computer-readable, non-transitory storage medium. The computer program product includes computer-executable instructions, such as instructions included in program modules. The instructions execute on a target real or virtual processor device to perform the processes or methods described above with reference to FIGS. 2 and 4-18. Typically, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. In various embodiments, the functionality of the program modules may be combined or split between program modules as desired. The machine-executable instructions of the program modules may be executed in local or distributed devices. In distributed devices, the program modules may be located in both local and remote storage media.

[0196] Program code for carrying out the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, and when executed by the processor or controller, the functions / operations specified in the flowcharts and / or block diagrams are performed. The program code may run entirely on a machine, partially on a machine, as a separate software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0197] The above-described program code may be embodied on a machine-readable medium, which may be any tangible medium that contains or stores a program used by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Even more specific examples of machine-readable storage media include an electrical connection comprising one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0198] Although operations have been described in a particular order, it should not be understood that performing these operations in the particular order or sequence shown, or performing all of the operations shown, is required to achieve desired results. In some situations, multitasking and parallel processing may be advantageous. Similarly, while the above discussion includes several specific implementation details, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features that may be specific to particular embodiments. Some features that are described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable subcombination.

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

Claims

1. 1. A method performed by a network device, comprising: receiving a first configuration associated with a time period from a terminal device that is assumed to be unreachable within the time period; receiving a message to update the period if the first setting is invalid; Including, method.

2. adjusting a mobile reachable timer in response to the period. The method of claim 1.

3. transmitting a second setting indicating a pause time for the downlink data; The pause time is determined based on the period. The method of claim 1.

4. The network device is a Mobility Management Entity (MME). The method of claim 1.

5. A method performed by a terminal device, comprising: sending a first configuration to a network device relating to a time period during which the terminal device is assumed to be unreachable; If the first setting is invalid, sending a message to update the period; Including, method.

6. receiving a second time period associated with Extended Discontinuous Reception (eDRX); the second period is determined based on time information associated with the period; The method of claim 5.

7. determining a pause time for downlink data based on the period; The method of claim 5.

8. A network device, means for receiving a first configuration related to a time period from a terminal device that is assumed to be unreachable within said time period; means for receiving a message to update the period if the first setting is invalid; Equipped with Network equipment.

9. means for adjusting a mobile reachable timer in response to the period of time; The network device according to claim 8.

10. means for transmitting a second setting indicating a pause time for downlink data; The pause time is determined based on the period. The network device according to claim 8.

11. A terminal device, means for transmitting a first setting to a network device, the first setting being related to a period of time during which the terminal device is assumed to be unreachable; means for sending a message to update the period if the first setting is invalid; Equipped with Terminal device.

12. means for receiving a second time period associated with Extended Discontinuous Reception (eDRX); the second period is determined based on time information associated with the period; The terminal device according to claim 11.

13. determining a pause time for downlink data based on the period; The terminal device according to claim 11.

Images