METHOD AND APPARATUS FOR INTERACTION BETWEEN TERMINAL AND CORE NETWORK

[0001] This application is the U.S. national phase application of International Application No. PCT/CN2021/129145, filed on Nov. 5, 2021, the entire contents of which are incorporated herein by reference for all purposes.

[0002] The disclosure relates to the field of mobile communication technologies, and in particular, to a method and apparatus for interaction between a terminal and a core network.

[0003] For IoT (Internet of Things) terminals, including NB (Narrow Band)—IoT terminals and eMTC (Enhanced Machine Type Communications) terminals, in order to save power for this type of terminals, the network can configure parameters such as DRX (Discontinuous Reception), eDRX (Extended Discontinuous Reception) and PSM (Power Save Mode) to the terminals, thereby achieving the goal of power saving of the terminals.

[0004] In related technologies, the above types of terminals can access NTNs (non-terrestrial networks), which can be satellite networks. For IoT NTN networks, there are discontinuous coverage scenarios, such that as satellites or terminals move, the terminals sometimes have network coverage and sometimes do not have network coverage. When the terminals do not have IoT NTN coverage, they can stop behaviors such as searching for cells and monitoring paging messages, thereby saving power consumption. However, when the core network device configures eDRX/PSM for the terminal, even if the UE does not have network coverage, the terminal needs to monitor paging messages or perform tracking area updates (TAU) based on the configuration of eDRX/PSM. It can be seen that if the terminal performs according to the configuration of the core network at this time, it will increase the power consumption of the terminal. Therefore, achieving the goal of power saving of the terminals while ensuring their normal behavior has become an urgent problem to be solved.

[0005] In a first aspect, embodiments of the present disclosure provide a method for interaction between a terminal and a core network. The method is applied to an IoT-NTN discontinuous coverage scenario. The method is performed by a terminal, and the method includes:

• • [0006] sending discontinuous coverage information to a core network device.

[0007] In a second aspect, embodiments of the present disclosure provide another method for interaction between a terminal and a core network. The method is applied in a discontinuous coverage scenario of an Internet of Things (IoT) Non-Terrestrial Network (NTN), the method is performed by a core network device, and includes:

• • [0008] sending instruction information to a terminal based on discontinuous coverage information.

[0009] In a third aspect, embodiments of the present disclosure provide a terminal. The terminal includes a transceiver. The transceiver is configured to send discontinuous coverage information to a core network device.

[0010] In a fourth aspect, embodiments of the present disclosure provide a core network device. The core network device includes a transceiver. The transceiver is configured to send instruction information to a terminal based on discontinuous coverage information.

[0022] Embodiments of the present disclosure are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein identical or similar labels throughout represent identical or similar components or components with identical or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain the present disclosure, but cannot be understood as limiting the present disclosure. In the description disclosed herein, unless otherwise specified, “/” represents or. For example, A/B may represent A or B; The “and/or” in this disclosure is only a description of the association relationship between related objects, indicating that there can be three types of relationships, such as A and/or B, which can represent the existence of A alone, the coexistence of A and B, and the existence of B alone.

[0023] For ease of understanding, first introduce the terms involved in this disclosure.

[0024] DRX related parameters are configured by the base station (gNB) to the terminal, mainly including DRX cycle and other parameters. The terminal monitors the paging channel based on DRX parameters to determine if there is any downlink service.

[0025] In order to further save power for the terminal, eDRX has been introduced. During each eDRX cycle, the terminal can only receive downlink data within the set paging time window (PTW), while remaining in a sleep state and not receiving downlink data for the rest time. During each eDRX cycle, there is a paging time window (PTW), during which the terminal monitors the paging channel according to the DRX cycle (the DRX cycle time is short, which can be considered as the terminal not sleeping and always reachable) in order to receive downlink data, while the terminal remains in the sleep time for the rest of the time. As shown in FIG. 1, there are two important parameters for eDRX, one is the eDRX cycle length and the other is PTW. The core network device configures eDRX parameters to the terminal during the attach process and TAU (tracking area updates) process of the terminal. In addition, the core network device can also send the parameters to gNB through S1's paging message, that is, when the core network device pages the terminal, it will also send the eDRX parameters to gNB.

[0026] In order to further save power, PSM (power saving mode) has been introduced. In PSM mode, downlink data is unreachable and the terminal is in the sleep state. There are two ways for waking up the terminal: the first is when uplink data needs to be sent, and the second is when the TAU timer times out. After entering the PSM mode, the terminal no longer receives paging messages and downlink data. As shown in FIG. 2, T3412 is the TAU timer, and T3324 is the activation timer. DRX is the time for periodic paging, and it also supports periodic paging when idle. The values of the T3324 and T3412 timers are configured by the core network device to the terminal. Usually, when the terminal attaches to the network and performs TAU, the core network device configures the above parameters to the terminal. For PSM, if the terminal enters the PSM state, it will not receive downlink data and will not perform any measurements on the serving and neighboring cells.

[0027] For IoT terminals, including NB-IoT terminals and eMTC terminals, this type of terminals can access an NTN, which can be a satellite network. For IoT-NTN networks, there are discontinuous coverage scenarios, such that as satellites or terminals move, terminals sometimes have network coverage and sometimes do not have network coverage. When terminals do not have IoT-NTN coverage, they can stop searching for cells, monitoring paging messages, and other behaviors, thereby saving power consumption.

[0028] However, when the core network device configures eDRX/PSM for the terminal, even if the UE does not have network coverage, the terminal needs to monitor paging messages or perform tracking area updates (TAU) based on the configuration of eDRX/PSM. It can be seen that if the terminal performs according to the core network configuration at this time, it will increase the power consumption of the terminal. Therefore, how to achieve the goal of power saving of terminals while ensuring their normal behavior has become an urgent problem to be solved.

[0029] Based on the above problem, embodiments of the present disclosure provide a method and apparatus for interaction between a terminal and a core network, which can be applied to an IoT-NTN discontinuous coverage scenario. The terminal sends discontinuous coverage information to the core network device, so that the terminal can interact with the core network device about the discontinuous coverage information, thereby making behavior of the terminal be consistent with definition of the core network device, to avoid the core network device thinking that the terminal is in an abnormal situation, and to achieve the goal of saving power for the terminal while ensuring normal behavior of the terminal.

[0030] In order to better understand the method for interaction between a terminal and a core network disclosed in embodiments of the present disclosure, the following will first describe the communication system applicable to embodiments of the present disclosure.

[0031] Please refer to FIG. 3, which is a schematic diagram of a communication system provided in an embodiment of the present disclosure. The communication system may include, but is not limited to, a core network device, a base station, a satellite, and a terminal. The number and form of devices shown in FIG. 3 are for illustrative purposes only and do not constitute limitations to the embodiments of the present disclosure. In practical applications, it may include two or more core network devices, two or more base stations, two or more terminals, and two or more base stations, where information exchange between terminals and core network devices can be forwarded through satellites and base stations. The communication system shown in FIG. 3 includes a core network device 301, a terminal 302, a base station 303, and a satellite 304 as an example. It should be noted that the technical solution of embodiments of the present disclosure can be applied to the NTN communication system. NTN is an important technology introduced by 5G, which provides wireless resources through satellites (or drones) instead of ground stations.

[0032] It should also be noted that the technical solution of embodiments of the present disclosure can be applied to various communication systems, for example, Long term evolution (LTE) systems, fifth generation (5G) mobile communication systems, 5G new radio (NR) systems, or other future new mobile communication systems. It should also be noted that the sidelink in embodiments of the present disclosure can also be referred to as a side link or a direct link.

[0033] The core network device 301 in embodiments of the present disclosure may be a 5G core network device and/or a 4G core network device. The 5G core network device may include Access and Mobility Management Function (AMF), Session Manager Function (SMF), etc. The 4G core network device may include Mobility Management Entity (MME). The system may also include CS domain core network devices. CS domain core network devices may be 2G core network devices or 3G core network devices.

[0034] Further, the CS domain core network devices may include: Mobile Switching Center (MSC) and/or Visitor Location Register (VLR). CS domain core network devices can establish interfaces with 4G core network devices to enable 4G core network devices to interact with 2G core network devices/3G core network devices, thereby enabling terminals to directly fall back from the 4G network to the 2G/3G network, which are not limited here.

[0035] The terminal 302 in embodiments of the present disclosure is an entity on the user side for receiving or transmitting signals, such as a mobile phone. Terminals may also be referred to as terminal devices, user equipment (UE), mobile stations (MS), mobile terminals (MT), etc. Terminals may include cars with communication capabilities, smart cars, mobile phones, wearable devices, tablets, computers with wireless transmission and reception capabilities, virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, Wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, and so on. The specific technology and device form adopted by the terminal is note limited in embodiments of the present disclosure.

[0036] It can be understood that the communication system described in the embodiments of the present disclosure is intended to provide a clearer explanation of the technical solution of the embodiments of the present disclosure, and does not constitute a limitation on the technical solution provided in the embodiments of the present disclosure. It is known to those skilled in the art that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided in the embodiments of the present disclosure is also applicable to similar technical problems.

[0037] The following provides a detailed introduction to the method and apparatus for interaction between the terminal and the core network provided in this application, in conjunction with the accompanying drawings.

[0038] Please refer to FIG. 4, which is a flowchart of a method for interaction between a terminal and a core network provided in an embodiment of the present disclosure. It should be noted that, the method for interaction between the terminal and the core network can be applied to IoT-NTN discontinuous coverage scenarios. The method for interaction between the terminal and the core network in the present embodiment can be performed by the terminal. As shown in FIG. 4, this method may include but is not limited to the following steps:

• • [0039] step S401, sending discontinuous coverage information to a core network device.

[0040] Optionally, when the terminal is in an IoT-NTN discontinuous coverage scenario, the terminal can interact with the core network device to send the discontinuous coverage information to the core network device. That is to say, when the terminal is in an IoT-NTN discontinuous coverage scenario, it needs to interact with the core network device for discontinuous coverage information. This can enable the core network device to understand the current network coverage situation of the terminal, such as when the UE enters non-IoT-NTN network coverage, and when the UE enters an IoT-NTN network coverage scenario from non-IoT-NTN network coverage.

[0041] With implementing the present embodiment, the terminal sends the discontinuous coverage information to the core network device, so that the terminal can interact with the core network device about the discontinuous coverage information, thereby making behavior of the terminal be consistent with definition of the core network device, to avoid the core network device thinking that the terminal is in an abnormal situation, and to achieve the goal of saving power for the terminal while ensuring normal behavior of the terminal.

[0042] Please refer to FIG. 5, which is a flowchart of another method for interaction between a terminal and a core network provided in an embodiment of the present disclosure. It should be noted that, the method for interaction between the terminal and the core network can be applied to IoT-NTN discontinuous coverage scenarios. The method for interaction between the terminal and the core network in the present embodiment can be performed by the terminal. As shown in FIG. 5, this method may include but is not limited to the following steps:

• • [0043] step S501, sending discontinuous coverage information to a core network device.

[0044] Optionally, when the terminal is in an IoT-NTN discontinuous coverage scenario, the terminal can interact with the core network device to send the discontinuous coverage information to the core network device. That is to say, when the terminal is in an IoT-NTN discontinuous coverage scenario, it needs to interact with the core network device for discontinuous coverage information. This can enable the core network device to understand the current network coverage situation of the terminal, such as when the UE enters non-IoT-NTN network coverage, and when the UE enters an IoT-NTN network coverage scenario from non-IoT-NTN network coverage.

[0045] In an implementation, the discontinuous coverage information may include, but is not limited to, any of following items 1) and 2):

• • [0046] 1) providing time information of IoT-NTN network coverage and/or of non-IoT-NTN network coverage for the terminal.
  • [0047] 2) the terminal being enter non-IoT-NTN network coverage. Optionally, the core network device can send first indication information to the core network device, and the core network device can determine that the UE will enter non-IoT-NTN network coverage according to the first indication information.

[0048] In an implementation, providing time information of IoT-NTN network coverage and/or of non-IoT-NTN network coverage for the terminal may be at least one time period, or may be time of entering non-IoT-NTN network coverage, or may be time of leaving non-IoT-NTN network coverage, or may be time of returning to non-IoT-NTN network coverage. As an example, providing time information of IoT-NTN network coverage and/or of non-IoT-NTN network coverage for the terminal may include any one of following:

• • [0049] 1) time when the terminal enters non-IoT-NTN network coverage, and/or leaves non-IoT-NTN network coverage;
  • [0050] 2) time when the terminal enters non-IoT-NTN network coverage, and/or returns to IoT-NTN network coverage;
  • [0051] 3) a plurality of time periods, each time period including time when the terminal enters non-IoT-NTN network coverage, and/or leaves non-IoT-NTN network coverage, or each time period including time when the terminal enters non-IoT-NTN network coverage, and/or returns to IoT-NTN network coverage; for example, time period (T1, T2), time period (T3, T4), wherein T1 is the time of entering non-IoT-NTN network coverage, T2 is the time of leaving non-IoT-NTN network coverage, T3 is the time of entering a next non-IoT-NTN network coverage, and T4 is the time of leaving the next non-IoT-NTN network coverage, the time period from T2 to T3 represents the time in which there is the IoT-NTN network coverage.

[0052] It should be noted that in some embodiments of the present disclosure, the terminal may predict discontinuous coverage scenarios based on auxiliary information sent by the base station. For example, a base station sends auxiliary information to the terminal. When the terminal receives the auxiliary information sent by the base station, it can predict the IoT-NTN discontinuous coverage scenario based on the auxiliary information, for example, it can predict that the terminal is currently or will be in the IoT-NTN discontinuous coverage scenario. The auxiliary information may be ephemeris information, for example, the terminal can predict that the terminal is currently or will be in an IoT-NTN discontinuous coverage scenario based on the ephemeris information sent by the base station. For example, the terminal can predict the current network coverage situation of the terminal based on the ephemeris information provided by the base station, such as when the UE enters non-IoT-NTN network coverage, and when the UE enters IoT-NTN network coverage from non-IoT-NTN network coverage.

[0053] It should also be noted that in some embodiments of the present disclosure, there are many ways in which the terminal can send the discontinuous coverage information to the core network device. For example, the discontinuous coverage information can be sent through the attach process or the tracking area update process. Alternatively, the discontinuous coverage information can be sent when the base station provides auxiliary information for the terminal to predict discontinuous coverage scenarios. Alternatively, the discontinuous coverage information can be sent when the core network device configures eDRX and/or PSM for the terminal. Below are three examples to describe the implementation of sending discontinuous coverage information.

[0054] In one possible implementation example, the terminal may send the discontinuous coverage information to the core network device through the attach process or tracking area update process. For example, the terminal can send the discontinuous coverage information in an Attach request message, or the terminal can also send the discontinuous coverage information in a Tracking area update (TAU) request message.

[0055] In one possible implementation example, the terminal may send the discontinuous coverage information to the core network device upon receiving auxiliary information sent by the base station for predicting discontinuous coverage scenarios. For example, when the base station provides auxiliary information for the terminal to predict discontinuous coverage scenarios, the terminal can predict the discontinuous coverage information and send it to the core network device.

[0056] In one possible implementation example, the terminal may send the discontinuous coverage information to the core network device when the core network device configures eDRX parameters and/or PSM parameters for the terminal. For example, when the core network device configures eDRX and/or PSM for the terminal, the terminal can send the discontinuous coverage information to the core network device.

[0057] step S502, receiving instruction information sent by the core network device based on the discontinuous coverage information.

[0058] Optionally, the terminal sends discontinuous coverage information to the core network device when predicting the IoT-NTN discontinuous coverage scenario based on the auxiliary information provided by the base station. When the core network device receives the discontinuous coverage information sent by the terminal, it can send instruction information to the terminal based on the discontinuous coverage information, so that the terminal can receive the instruction information sent by the core network device.

[0059] In one implementation, the instruction information may include, but is not limited to any one of following items 1)-3):

• • [0060] 1) instructing the terminal to ignore an extended discontinuous reception (eDRX) configuration parameter and/or a power save mode (PSM) configuration parameter;
  • [0061] 2) instructing the terminal to stop using an eDRX mode and/or a PSM mode when entering non-IoT-NTN network coverage, and to continue to perform according to an eDRX configuration and/or a PSM configuration when entering an IoT-NTN network coverage scenario;
  • [0062] 3) instructing the terminal to use a new eDRX configuration parameter and/or a new PSM configuration parameter.

[0063] That is to say, when the core network device receives the discontinuous coverage information sent by the terminal, it may include the following behavior: instructing the terminal to ignore eDRX configuration parameters and/or PSM configuration parameters; or, instructing the terminal to stop using eDRX/PSM mode in scenarios without IoT-NTN network coverage, and continue to perform according to eDRX/PSM configuration in scenarios with IoT-NTN network coverage, for example, assuming time period (T1, T2) and time period (T3, T4), where T1 is the time of entering non-IoT-NTN network coverage, T2 is the time of leaving non-IoT-NTN network coverage, T3 is the time of entering the next non-IoT-NTN network coverage, T4 is the time of leaving the next non-IoT-NTN network coverage, where the time period from T2 to T3 represents the time in which there is IoT-NTN network coverage, the core network device can instruct the terminal to stop eDRX/PSM during the time periods (T1, T2) and (T3, T4), and perform eDRX/PSM during the time period (T2, T3); or, updating the eDRX/PSM parameters, and instructing the terminal to use the new eDRX/PSM configuration parameters.

[0064] Optionally, in some embodiments of the present disclosure, as shown in FIG. 5, the method may further include: step S503, the terminal may also perform corresponding operations based on the instruction information sent by the core network device.

[0065] Optionally, when the terminal receives the above instruction information sent by the core network device, it can perform corresponding operations based on the instruction information.

[0066] In one possible implementation, it is assumed that the instruction information includes instructing the terminal to ignore eDRX configuration parameters and/or PSM configuration parameters. When the terminal receives the instruction message, it is instructed to ignore the eDRX and/or PSM parameters configured by the core network when the terminal is in the discontinuous coverage scenario, based on the instruction information.

[0067] That is to say, the terminal can ignore eDRX and/or PSM configuration when receiving instruction information. For example, when the T3412 timer expires, the terminal does not perform TAU; when it is within PTW, the terminal does not monitor paging messages.

[0068] In one possible implementation, it is assumed that the instruction information includes instructing the terminal to stop using eDRX and/or PSM mode when entering non-IoT-NTN network coverage, and to continue to perform according to eDRX and/or PSM configuration when entering an IoT-NTN network coverage scenario. When the terminal receives the instruction message, it is instructed to ignore the eDRX and/or PSM parameters configured by the core network when entering non-IoT-NTN network coverage, and continue to perform eDRX and/or PSM configuration when entering an IoT-NTN network coverage scenario.

[0069] For example, assuming time period (T1, T2) and time period (T3, T4), where T1 is the time of entering non-IoT-NTN network coverage, T2 is the time of leaving non-IoT-NTN network coverage, T3 is the time of entering the next non-IoT-NTN network coverage, T4 is the time of leave the next non-IoT-NTN network coverage, where the time period from T2 to T3 represents the time in which there is IoT-NTN network coverage. When receiving the instruction information from the core network device, the terminal can ignore eDRX/PSM configuration and remain the sleep state in the scenarios without IoT-NTN network coverage, such as during periods (T1, T2), (T3, T4), and continue to perform eDRX/PSM, i.e., monitor paging messages and perform TAU according to the configuration, during the time period (T2, T3) in which there is the IoT-NTN network coverage.

[0070] In one possible implementation, it is assumed that the instruction information includes instructing the terminal to use new eDRX configuration parameters and/or new PSM configuration parameters. When the terminal receives the instruction message, it is instructed to use the new eDRX configuration and/or new PSM configuration configured by the core network based on the instruction information.

[0071] That is to say, when the core network device receives discontinuous coverage information sent by the terminal, it can update the eDRX/PSM parameters, instructing the terminal to use the new eDRX/PSM configuration parameters. In this way, when the terminal receives the instruction message sent by the core network device, it can be instructed to use the new eDRX/PSM configuration parameters based on the instruction information.

[0072] By implementing the embodiments of the present disclosure, the terminal sends the discontinuous coverage information to the core network device and receives instruction information sent by the core network device based on the discontinuous coverage information, and performs corresponding operations according to the instruction information. For example, the terminal can be instructed to ignore eDRX and/or PSM configuration, or the terminal can be instructed to stop eDRX/PSM in a non-network coverage scenario and continue to perform according to eDRX/PSM configuration in a network coverage scenario, or the terminal can be instructed to use new eDRX/PSM configuration parameters. From this, it can be seen that the present disclosure ensures that the behavior of the terminal is consistent with the definition of the core network device by enabling the discontinuous coverage information interaction between the terminal and the core network device, in order to avoid the core network device believing that the terminal is in an abnormal situation. This can not only achieve the goal of saving power for the terminal, but also ensure the normal behavior of the terminal.

[0073] In In some embodiments of the present disclosure, as shown in FIG. 6, the method for interaction between the terminal and the core network may include but is not limited to the following steps.

[0074] Step S601, the terminal receives instruction information.

[0075] In an implementation, the terminal may receive the instruction information sent by the core network device.

[0076] In one possible implementation, the instruction information may include but is not limited to any of following items 1)-3):

• • [0077] 1) instructing the terminal to ignore an extended discontinuous reception (eDRX) configuration parameter and/or a power save mode (PSM) configuration parameter;
  • [0078] 2) instructing the terminal to stop using an eDRX mode and/or a PSM mode when entering non-IoT-NTN network coverage, and to continue to perform according to an eDRX configuration and/or a PSM configuration when entering an IoT-NTN network coverage scenario;
  • [0079] 3) instructing the terminal to use a new eDRX configuration parameter and/or a new PSM configuration parameter.

[0080] That is to say, when the core network device receives the discontinuous coverage information sent by the terminal, it may include the following behavior: instructing the terminal to ignore eDRX configuration parameters and/or PSM configuration parameters; or, instructing the terminal to stop using eDRX/PSM mode in scenarios without IoT-NTN network coverage, and continue to perform according to eDRX/PSM configuration in scenarios with IoT-NTN network coverage, for example, assuming time period (T1, T2) and time period (T3, T4), where T1 is the time of entering non-IoT-NTN network coverage, T2 is the time of leaving non-IoT-NTN network coverage, T3 is the time of entering the next non-IoT-NTN network coverage, T4 is the time of leaving the next non-IoT-NTN network coverage, where the time period from T2 to T3 represents the time in which there is IoT-NTN network coverage, the core network device can instruct the terminal to stop eDRX/PSM during the time periods (T1, T2) and (T3, T4), and perform eDRX/PSM during the time period (T2, T3); or, updating the eDRX/PSM parameters, and instructing the terminal to use the new eDRX/PSM configuration parameters.

[0081] Optionally, in some embodiments of the present disclosure, as shown in FIG. 6, the method for interaction between the terminal and the core network may further include step S602, the terminal performs corresponding operations according to the instruction information.

[0082] In one possible implementation, it is assumed that the instruction information includes instructing the terminal to ignore eDRX configuration parameters and/or PSM configuration parameters. When the terminal receives the instruction message, it is instructed to ignore the eDRX and/or PSM parameters configured by the core network when the terminal is in the discontinuous coverage scenario, based on the instruction information.

[0083] That is to say, the terminal can ignore eDRX and/or PSM configuration when receiving instruction information. For example, when the T3412 timer expires, the terminal does not perform TAU; when it is within PTW, the terminal does not monitor paging messages.

[0084] In one possible implementation, it is assumed that the instruction information includes instructing the terminal to stop using eDRX and/or PSM mode when entering non-IoT-NTN network coverage, and to continue to perform according to eDRX and/or PSM configuration when entering an IoT-NTN network coverage scenario. When the terminal receives the instruction message, it is instructed to ignore the eDRX and/or PSM parameters configured by the core network when entering non-IoT-NTN network coverage, and continue to perform eDRX and/or PSM configuration when entering an IoT-NTN network coverage scenario.

[0085] For example, assuming time period (T1, T2) and time period (T3, T4), where T1 is the time of entering non-IoT-NTN network coverage, T2 is the time of leaving non-IoT-NTN network coverage, T3 is the time of entering the next non-IoT-NTN network coverage, T4 is the time of leave the next non-IoT-NTN network coverage, where the time period from T2 to T3 represents the time in which there is IoT-NTN network coverage. When receiving the instruction information from the core network device, the terminal can ignore eDRX/PSM configuration and remain the sleep state in the scenarios without IoT-NTN network coverage, such as during periods (T1, T2), (T3, T4), and continue to perform eDRX/PSM, i.e., monitor paging messages and perform TAU according to the configuration, during the time period (T2, T3) in which there is the IoT-NTN network coverage.

[0086] In one possible implementation, it is assumed that the instruction information includes instructing the terminal to use new eDRX configuration parameters and/or new PSM configuration parameters. When the terminal receives the instruction message, it is instructed to use the new eDRX configuration and/or new PSM configuration configured by the core network based on the instruction information.

[0087] For example, when the core network device receives discontinuous coverage information sent by the terminal, it can update the eDRX/PSM parameters, instructing the terminal to use the new eDRX/PSM configuration parameters. In this way, when the terminal receives the instruction message sent by the core network device, it can be instructed to use the new eDRX/PSM configuration parameters based on the instruction information.

[0088] By implementing the embodiments of the present disclosure, the terminal receives instruction information, and performs corresponding operations according to the instruction information. For example, the terminal can be instructed to ignore eDRX and/or PSM configuration, or the terminal can be instructed to stop eDRX/PSM in a non-network coverage scenario and continue to perform according to eDRX/PSM configuration in a network coverage scenario, or the terminal can be instructed to use new eDRX/PSM configuration parameters. From this, it can be seen that, in the present disclosure, the core network sends the instruction information to the terminal to ensure that the behavior of the terminal is consistent with the definition of the core network device, in order to avoid the core network device believing that the terminal is in an abnormal situation. This can not only achieve the goal of saving power for the terminal, but also ensure the normal behavior of the terminal.

[0089] It can be understood that the above embodiments describes the implementation of the method for interaction between the terminal and the core network of embodiments of the present disclosure from the terminal side. Embodiments of the present disclosure also proposes a method for interaction between a terminal and a core network. The following will describe the implementation of the method for interaction between the terminal and the core network from the core network device side. Please refer to FIG. 7, which is a flowchart of another method for interaction between a terminal and a core network provided in an embodiment of the present disclosure. It should be noted that the method for interaction between the terminal and the core network in the present embodiment is applied to the IoT-NTN discontinuous coverage scenario. The method for interaction between the terminal and the core network in the present embodiment can be performed by the core network device. As shown in FIG. 7, this method may include but is not limited to the following steps.

[0090] Step S701, sending instruction information to the terminal based on discontinuous coverage information.

[0091] In one implementation, the discontinuous coverage information may be pre-configured. For example, the core network can send instruction information to the terminal based on pre-configured discontinuous coverage information.

[0092] In another implementation, the discontinuous coverage information may be obtained through a base station. For example, the core network can send instruction information to the terminal based on the discontinuous coverage information obtained through the base station.

[0093] In yet another implementation, the discontinuous coverage information may be the information sent by the terminal to the core network device when the terminal predicts that the terminal is in a discontinuous coverage scenario based on the auxiliary information provided by the base station.

[0094] Optionally, in some embodiments, the core network device can receive the discontinuous coverage information sent by the terminal, and send the instruction information to the terminal based on the discontinuous coverage information.

[0095] For example, a base station provides auxiliary information (such as ephemeris information). When the terminal receives auxiliary information sent by the base station, it can predict discontinuous coverage scenarios based on this auxiliary information. The terminal can send discontinuous coverage information to the core network device, so that the core network device can send instruction information to the terminal based on this discontinuous coverage information. For example, the core network device can send the instruction information to the terminal in an Attach accept message or in a Tracking area update accept message.

[0096] In an implementation, the discontinuous coverage information may include, but is not limited to, any of following items 1) and 2):

• • [0097] 1) providing time information of IoT-NTN network coverage and/or of non-IoT-NTN network coverage for the terminal.
  • [0098] 2) the terminal being enter non-IoT-NTN network coverage. Optionally, the core network device can send first indication information to the core network device, and the core network device can determine that the UE will enter non-IoT-NTN network coverage according to the first indication information.

[0099] In an implementation, providing time information of IoT-NTN network coverage and/or of non-IoT-NTN network coverage for the terminal may be at least one time period, or may be time of entering non-IoT-NTN network coverage, or may be time of leaving non-IoT-NTN network coverage, or may be time of returning to non-IoT-NTN network coverage. As an example, providing time information of IoT-NTN network coverage and/or of non-IoT-NTN network coverage for the terminal may include any one of following:

• • [0100] 1) time when the terminal enters non-IoT-NTN network coverage, and/or leaves non-IoT-NTN network coverage;
  • [0101] 2) time when the terminal enters non-IoT-NTN network coverage, and/or returns to IoT-NTN network coverage;
  • [0102] 3) a plurality of time periods, each time period including time when the terminal enters non-IoT-NTN network coverage, and/or leaves non-IoT-NTN network coverage, or each time period including time when the terminal enters non-IoT-NTN network coverage, and/or returns to IoT-NTN network coverage; for example, time period (T1, T2), time period (T3, T4), wherein T1 is the time of entering non-IoT-NTN network coverage, T2 is the time of leaving non-IoT-NTN network coverage, T3 is the time of entering a next non-IoT-NTN network coverage, and T4 is the time of leaving the next non-IoT-NTN network coverage, the time period from T2 to T3 represents the time in which there is the IoT-NTN network coverage.

[0103] It should be noted that in some embodiments of the present disclosure, the terminal may predict discontinuous coverage scenarios based on auxiliary information sent by the base station. For example, a base station sends auxiliary information to the terminal. When the terminal receives the auxiliary information sent by the base station, it can predict the IoT-NTN discontinuous coverage scenario based on the auxiliary information, for example, it can predict that the terminal is currently or will be in the IoT-NTN discontinuous coverage scenario. The auxiliary information may be ephemeris information, for example, the terminal can predict that the terminal is currently or will be in an IoT-NTN discontinuous coverage scenario based on the ephemeris information sent by the base station. For example, the terminal can predict the current network coverage situation of the terminal based on the ephemeris information provided by the base station, such as when the UE enters non-IoT-NTN network coverage, and when the UE enters IoT-NTN network coverage from non-IoT-NTN network coverage.

[0104] It should also be noted that in some embodiments of the present disclosure, there are many ways in which the terminal can send the discontinuous coverage information to the core network device. For example, the discontinuous coverage information can be sent through the attach process or the tracking area update process. Alternatively, the discontinuous coverage information can be sent when the base station provides auxiliary information for the terminal to predict discontinuous coverage scenarios. Alternatively, the discontinuous coverage information can be sent when the core network device configures eDRX and/or PSM for the terminal. Below are three examples to describe the implementation of sending discontinuous coverage information.

[0105] In one possible implementation example, the terminal may send the discontinuous coverage information to the core network device upon receiving auxiliary information sent by the base station for predicting discontinuous coverage scenarios. For example, when the base station provides auxiliary information for the terminal to predict discontinuous coverage scenarios, the terminal can predict the discontinuous coverage information and send it to the core network device.

[0106] In one possible implementation example, the terminal may send the discontinuous coverage information to the core network device when the core network device configures eDRX parameters and/or PSM parameters for the terminal. For example, when the core network device configures eDRX and/or PSM for the terminal, the terminal can send the discontinuous coverage information to the core network device. in this way, when the core network receives the discontinuous coverage information, it can send the instruction information to the terminal. In one implementation, the instruction information may include, but is not limited to any one of following items 1)-3):

• • [0107] 1) instructing the terminal to ignore an extended discontinuous reception (eDRX) configuration parameter and/or a power save mode (PSM) configuration parameter;
  • [0108] 2) instructing the terminal to stop using an eDRX mode and/or a PSM mode when entering non-IoT-NTN network coverage, and to continue to perform according to an eDRX configuration and/or a PSM configuration when entering an IoT-NTN network coverage scenario;
  • [0109] 3) instructing the terminal to use a new eDRX configuration parameter and/or a new PSM configuration parameter.

[0110] In embodiments of the present disclosure, when the core network device receives the discontinuous coverage information sent by the terminal, it may include the following behavior: instructing the terminal to ignore eDRX configuration parameters and/or PSM configuration parameters; or, instructing the terminal to stop using eDRX/PSM mode in scenarios without IoT-NTN network coverage, and continue to perform according to eDRX/PSM configuration in scenarios with IoT-NTN network coverage, for example, assuming time period (T1, T2) and time period (T3, T4), where T1 is the time of entering non-IoT-NTN network coverage, T2 is the time of leaving non-IoT-NTN network coverage, T3 is the time of entering the next non-IoT-NTN network coverage, T4 is the time of leaving the next non-IoT-NTN network coverage, where the time period from T2 to T3 represents the time in which there is IoT-NTN network coverage, the core network device can instruct the terminal to stop eDRX/PSM during the time periods (T1, T2) and (T3, T4), and perform eDRX/PSM during the time period (T2, T3); or, updating the eDRX/PSM parameters, and instructing the terminal to use the new eDRX/PSM configuration parameters.

[0111] When the terminal receives the above instruction information sent by the core network device, it can perform corresponding operations based on the instruction information.

[0112] In one possible implementation, it is assumed that the instruction information includes instructing the terminal to ignore eDRX configuration parameters and/or PSM configuration parameters. When the terminal receives the instruction message, it is instructed to ignore the eDRX and/or PSM parameters configured by the core network when the terminal is in the discontinuous coverage scenario, based on the instruction information.

[0113] That is to say, the terminal can ignore eDRX and/or PSM configuration when receiving instruction information. For example, when the T3412 timer expires, the terminal does not perform TAU; when it is within PTW, the terminal does not monitor paging messages.

[0114] In one possible implementation, it is assumed that the instruction information includes instructing the terminal to stop using eDRX and/or PSM mode when entering non-IoT-NTN network coverage, and to continue to perform according to eDRX and/or PSM configuration when entering an IoT-NTN network coverage scenario. When the terminal receives the instruction message, it is instructed to ignore the eDRX and/or PSM parameters configured by the core network when entering non-IoT-NTN network coverage, and continue to perform eDRX and/or PSM configuration when entering an IoT-NTN network coverage scenario.

[0115] For example, assuming time period (T1, T2) and time period (T3, T4), where T1 is the time of entering non-IoT-NTN network coverage, T2 is the time of leaving non-IoT-NTN network coverage, T3 is the time of entering the next non-IoT-NTN network coverage, T4 is the time of leave the next non-IoT-NTN network coverage, where the time period from T2 to T3 represents the time in which there is IoT-NTN network coverage. When receiving the instruction information from the core network device, the terminal can ignore eDRX/PSM configuration and remain the sleep state in the scenarios without IoT-NTN network coverage, such as during periods (T1, T2), (T3, T4), and continue to perform eDRX/PSM, i.e., monitor paging messages and perform TAU according to the configuration, during the time period (T2, T3) in which there is the IoT-NTN network coverage.

[0116] In one possible implementation, it is assumed that the instruction information includes instructing the terminal to use new eDRX configuration parameters and/or new PSM configuration parameters. When the terminal receives the instruction message, it is instructed to use the new eDRX configuration and/or new PSM configuration configured by the core network based on the instruction information.

[0117] That is to say, when the core network device receives discontinuous coverage information sent by the terminal, it can update the eDRX/PSM parameters, instructing the terminal to use the new eDRX/PSM configuration parameters. In this way, when the terminal receives the instruction message sent by the core network device, it can be instructed to use the new eDRX/PSM configuration parameters based on the instruction information.

[0118] In one implementation, the core network device can confirm that the terminal does not perform eDRX configuration and/or PSM configuration when there is no IoT-NTN network coverage. For example, the core network device can confirm that the terminal does not perform eDRX/PSM when there is no IoT-NTN network coverage, that is, the core network device believes that paging cannot reach the terminal, and the terminal does not perform TAU are not abnormal situations.

[0119] In one implementation, in response to the terminal being in non-IoT-NTN network coverage and requiring a paging message to be sent to the terminal, the paging message for the terminal is saved. For example, if there is a paging message for a terminal in non-IoT-NTN network coverage, the core network device saves the paging message for the terminal.

[0120] By implementing the embodiments of the present disclosure, the core network device sends the instructions information to the terminal based on the discontinuous coverage information sent by the terminal, so that the terminal performs corresponding operations according to the instruction information. For example, the terminal can be instructed to ignore eDRX and/or PSM configuration, or the terminal can be instructed to stop eDRX/PSM in a non-network coverage scenario and continue to perform according to eDRX/PSM configuration in a network coverage scenario, or the terminal can be instructed to use new eDRX/PSM configuration parameters. From this, it can be seen that the present disclosure ensures that the behavior of the terminal is consistent with the definition of the core network device by enabling the discontinuous coverage information interaction between the terminal and the core network device, in order to avoid the core network device believing that the terminal is in an abnormal situation. This can not only achieve the goal of saving power for the terminal, but also ensure the normal behavior of the terminal.

[0121] In order to facilitate those skilled in the art to have a clearer understanding of the present disclosure, the following will describe the method for interaction between the terminal and the core network from both sides of the core network device and the terminal, combined with FIG. 8.

[0122] As shown in FIG. 8, in some embodiments of the present disclosure, the core network device configures eDRX/PSM parameters for the terminal (S801). The terminal monitors paging messages or performs tracking area updates (TAU) based on the eDRX/PSM parameters configured by the core network device (S802). When the base station provides auxiliary information for the terminal to predict discontinuous coverage scenarios, the terminals can predict discontinuous coverage information and send the discontinuous coverage information to the core network device (S803). The discontinuous coverage information may include but is not limited to any of the following items 1) to 2):

• • [0123] 1) providing time information of IoT-NTN network coverage and/or of non-IoT-NTN network coverage for the terminal.
  • [0124] 2) the terminal being enter non-IoT-NTN network coverage. Optionally, the core network device can send first indication information to the core network device, and the core network device can determine that the UE will enter non-IoT-NTN network coverage according to the first indication information.

[0125] In an implementation, providing time information of IoT-NTN network coverage and/or of non-IoT-NTN network coverage for the terminal may be at least one time period, or may be time of entering non-IoT-NTN network coverage, or may be time of leaving non-IoT-NTN network coverage, or may be time of returning to non-IoT-NTN network coverage. As an example, providing time information of IoT-NTN network coverage and/or of non-IoT-NTN network coverage for the terminal may include any one of following:

• • [0126] 1) time when the terminal enters non-IoT-NTN network coverage, and/or leaves non-IoT-NTN network coverage;
  • [0127] 2) time when the terminal enters non-IoT-NTN network coverage, and/or returns to IoT-NTN network coverage;
  • [0128] 3) a plurality of time periods, each time period including time when the terminal enters non-IoT-NTN network coverage, and/or leaves non-IoT-NTN network coverage, or each time period including time when the terminal enters non-IoT-NTN network coverage, and/or returns to IoT-NTN network coverage; for example, time period (T1, T2), time period (T3, T4), wherein T1 is the time of entering non-IoT-NTN network coverage, T2 is the time of leaving non-IoT-NTN network coverage, T3 is the time of entering a next non-IoT-NTN network coverage, and T4 is the time of leaving the next non-IoT-NTN network coverage, the time period from T2 to T3 represents the time in which there is the IoT-NTN network coverage.

[0129] In some embodiments of the present application, as shown in FIG. 8, the core network device may receive the discontinuous coverage information sent by the terminal and send the instruction information to the terminal based on the discontinuous coverage information (S804). The instruction information may include but is not limited to any one of the following items 1) to 3):

• • [0130] 1) instructing the terminal to ignore an extended discontinuous reception (eDRX) configuration parameter and/or a power save mode (PSM) configuration parameter;
  • [0131] 2) instructing the terminal to stop using an eDRX mode and/or a PSM mode when entering non-IoT-NTN network coverage, and to continue to perform according to an eDRX configuration and/or a PSM configuration when entering an IoT-NTN network coverage scenario;
  • [0132] 3) instructing the terminal to use a new eDRX configuration parameter and/or a new PSM configuration parameter.

[0133] In some embodiments of the present disclosure, as shown in FIG. 8, the terminal may receive the instruction information sent by the core network, and performing corresponding operations according to the instruction information (S805).

[0134] In one possible implementation, it is assumed that the instruction information includes instructing the terminal to ignore eDRX configuration parameters and/or PSM configuration parameters. When the terminal receives the instruction message, it is instructed to ignore the eDRX and/or PSM parameters configured by the core network when the terminal is in the discontinuous coverage scenario, based on the instruction information.

[0135] That is to say, the terminal can ignore eDRX and/or PSM configuration when receiving instruction information. For example, when the T3412 timer expires, the terminal does not perform TAU; when it is within PTW, the terminal does not monitor paging messages.

[0136] In one possible implementation, it is assumed that the instruction information includes instructing the terminal to stop using eDRX and/or PSM mode when entering non-IoT-NTN network coverage, and to continue to perform according to eDRX and/or PSM configuration when entering an IoT-NTN network coverage scenario. When the terminal receives the instruction message, it is instructed to ignore the eDRX and/or PSM parameters configured by the core network when entering non-IoT-NTN network coverage, and continue to perform eDRX and/or PSM configuration when entering an IoT-NTN network coverage scenario.

[0137] For example, assuming time period (T1, T2) and time period (T3, T4), where T1 is the time of entering non-IoT-NTN network coverage, T2 is the time of leaving non-IoT-NTN network coverage, T3 is the time of entering the next non-IoT-NTN network coverage, T4 is the time of leave the next non-IoT-NTN network coverage, where the time period from T2 to T3 represents the time in which there is IoT-NTN network coverage. When receiving the instruction information from the core network device, the terminal can ignore eDRX/PSM configuration and remain the sleep state in the scenarios without IoT-NTN network coverage, such as during periods (T1, T2), (T3, T4), and continue to perform eDRX/PSM, i.e., monitor paging messages and perform TAU according to the configuration, during the time period (T2, T3) in which there is the IoT-NTN network coverage.

[0138] In one possible implementation, it is assumed that the instruction information includes instructing the terminal to use new eDRX configuration parameters and/or new PSM configuration parameters. When the terminal receives the instruction message, it is instructed to use the new eDRX configuration and/or new PSM configuration configured by the core network based on the instruction information.

[0139] That is to say, when the core network device receives discontinuous coverage information sent by the terminal, it can update the eDRX/PSM parameters, instructing the terminal to use the new eDRX/PSM configuration parameters. In this way, when the terminal receives the instruction message sent by the core network device, it can be instructed to use the new eDRX/PSM configuration parameters based on the instruction information.

[0140] In the above embodiments provided in this disclosure, the methods provided are introduced from the perspectives of the terminal and the core network device. In order to achieve the various functions of the methods provided in the embodiments of the present disclosure, the terminal and the core network device may include hardware structures and software modules, which are implemented in the form of hardware structures, software modules, or hardware structures plus software modules. One of the above functions can be performed in the form of hardware structure, software module, or hardware structure plus software module.

[0141] Please refer to FIG. 9, which is a block diagram of a communication device 90 provided in an embodiment of the present disclosure. The communication device 90 shown in FIG. 9 may include a transceiver module 902 and a processing module 901. The transceiver module 902 may include a sending module and/or a receiving module, the sending module for implementing the sending function, the receiving module for implementing the receiving function, and the transceiver module 902 can implement the sending and/or receiving function.

[0142] The communication device 90 may be a terminal, a device within the terminal, or a device that can be matched and used with the terminal. Alternatively, the communication device 90 may be a network device, a device within the network device, or a device that can be matched and used with the network device. It should be noted that the communication device 90 is applied to IoT-NTN discontinuous coverage scenarios.

[0143] The communication device 90 is the terminal. In embodiments of the present disclosure, the transceiver module 902 is configured to send discontinuous coverage information to a core network device.

[0144] In an implementation, the transceiver module 902 is further configured to receive instruction information sent by the core network device based on the discontinuous coverage information; the processing module is configured to perform corresponding operations according to the instruction information.

[0145] In an implementation, the instruction information includes any of following items:

• • [0146] 1) instructing the terminal to ignore an extended discontinuous reception (eDRX) configuration parameter and/or a power save mode (PSM) configuration parameter;
  • [0147] 2) instructing the terminal to stop using an eDRX mode and/or a PSM mode when entering non-IoT-NTN network coverage, and to continue to perform according to an eDRX configuration and/or a PSM configuration when entering an IoT-NTN network coverage scenario;
  • [0148] 3) instructing the terminal to use a new eDRX configuration parameter and/or a new PSM configuration parameter.

[0149] In an implementation, the processing module 901 is specifically configured to instruct the terminal to ignore the eDRX configuration parameter and/or the PSM configuration parameter configured by the core network device when the terminal enters the discontinuous coverage scenario, according to the instruction information.

[0150] In a possible implementation, the processing module 901 is specifically configured to instruct the terminal to ignore the eDRX configuration parameter and/or the PSM configuration parameter configurated by the core network when entering non-IoT-NTN network coverage, and to continue to perform the eDRX configuration and/or the PSM configuration when entering the IoT-NTN network coverage scenario, according to the instruction information.

[0151] In a possible implementation, the processing module 901 is specifically configured to instruct the terminal to use a new eDRX configuration and/or a new PSM configuration configured by the core network, according to the instruction information.

[0152] In a possible implementation, the transceiver module 902 is specifically configured to send the discontinuous coverage information to the core network device through an attach process or a tracking area update process.

[0153] In a possible implementation, the transceiver module 902 is specifically configured to send the discontinuous coverage information to the core network device in response to receiving auxiliary information sent by a base station for the terminal to predict the discontinuous coverage scenario.

[0154] In a possible implementation, the transceiver module 902 is specifically configured to send the discontinuous coverage information to the core network device in case that the core network device configures an eDRX parameter and/or a PSM parameter for the terminal.

[0155] In a possible implementation, the discontinuous coverage information includes any one of following items:

• • [0156] providing time information of IoT-NTN network coverage and/or of non-IoT-NTN network coverage for the terminal; and
  • [0157] the terminal being enter non-IoT-NTN network coverage.

[0158] In a possible implementation, providing time information of IoT-NTN network coverage and/or of non-IoT-NTN network coverage for the terminal includes any of following items:

• • [0159] 1) time when the terminal enters non-IoT-NTN network coverage, and/or leaves non-IoT-NTN network coverage;
  • [0160] 2) time when the terminal enters non-IoT-NTN network coverage, and/or returns to IoT-NTN network coverage;
  • [0161] 3) a plurality of time periods, each time period including time when the terminal enters non-IoT-NTN network coverage, and/or leaves non-IoT-NTN network coverage, or each time period including time when the terminal enters non-IoT-NTN network coverage, and/or time returns to IoT-NTN network coverage; for example, time period (T1, T2), time period (T3, T4), wherein T1 is the time of entering non-IoT-NTN network coverage, T2 is the time of leaving non-IoT-NTN network coverage, T3 is the time of entering a next non-IoT-NTN network coverage, and T4 is the time of leaving the next non-IoT-NTN network coverage, the time period from T2 to T3 represents the time in which there is the IoT-NTN network coverage.

[0162] The communication device 90 is the core network device. In embodiments of the present disclosure, the transceiver module 902 is configured to send instruction information to the terminal based on discontinuous coverage information.

[0163] In an implementation, the transceiver module 902 is specifically configured to receive the discontinuous coverage information sent by the terminal; and send the instruction information to the terminal based on the discontinuous coverage information.

[0164] In an implementation, the instruction information may include any of following items:

• • [0165] instructing the terminal to ignore an extended discontinuous reception (eDRX) configuration parameter and/or a power save mode (PSM) configuration parameter;
  • [0166] instructing the terminal to stop using an eDRX mode and/or a PSM mode when entering non-IoT-NTN network coverage, and to continue to perform according to an eDRX configuration and/or a PSM configuration when entering an IoT-NTN network coverage scenario;
  • [0167] instructing the terminal to use a new eDRX configuration parameter and/or a new PSM configuration parameter.

[0168] In an implementation, the processing module 901 is configured to determine that the terminal does not perform the eDRX configuration and/or the PSM configuration in non-IoT-NTN network coverage.

[0169] In an implementation, the processing module 901 is configured to, in response to the terminal being in non-IoT-NTN network coverage and requiring a paging message to be sent to the terminal, save the paging message for the terminal.

[0170] In an implementation, the transceiver module 902 is specifically configured to send the instruction information to the terminal in an attach accept message or a tracking area update accept message.

[0171] In an implementation, the discontinuous coverage information includes any of following items:

• • [0172] providing time information of IoT-NTN network coverage and/or of non-IoT-NTN network coverage for the terminal; and
  • [0173] the terminal being enter non-IoT-NTN network coverage.

[0174] In a possible implementation, providing time information of IoT-NTN network coverage and/or of non-IoT-NTN network coverage for the terminal includes any of following items:

• • [0175] 1) time when the terminal enters non-IoT-NTN network coverage, and/or leaves non-IoT-NTN network coverage;
  • [0176] 2) time when the terminal enters non-IoT-NTN network coverage, and/or returns to IoT-NTN network coverage;
  • [0177] 3) a plurality of time periods, each time period including time when the terminal enters non-IoT-NTN network coverage, and/or leaves non-IoT-NTN network coverage, or each time period including time when the terminal enters non-IoT-NTN network coverage, and/or returns to IoT-NTN network coverage; for example, time period (T1, T2), time period (T3, T4), wherein T1 is the time of entering non-IoT-NTN network coverage, T2 is the time of leaving non-IoT-NTN network coverage, T3 is the time of entering a next non-IoT-NTN network coverage, and T4 is the time of leaving the next non-IoT-NTN network coverage, the time period from T2 to T3 represents the time in which there is the IoT-NTN network coverage.

[0178] Regarding the device in the above embodiments, the specific ways in which each module performs operations have been described in detail in the embodiments related to the method, and will not be elaborated here.

[0179] Please refer to FIG. 10, which is a block diagram of another communication device 100 provided in an embodiment of the present disclosure. It should be noted that, the communication device 100 can be applied to the IoT-NTN discontinuous coverage scenario. The communication device 100 may be a core network device or a may be a terminal, or may be a chip, chip system, processor, etc. that supports the core network device in implementing the above method, or may be a chip, chip system, processor, etc. that supports the terminal in implementing the above method. This device can be configured to implement the methods described in the above method embodiments, as described in the above method embodiments.

[0180] The communication device 100 may include one or more processor 1001. The processor 1001 may be a general-purpose processor, a dedicated processor, or the like. For example, it may be a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and data, while the central processor can be used to control communication devices (such as base stations, baseband chips, terminals, terminal chips, DU or CU, etc.), execute computer programs, and process data from computer programs.

[0181] Optionally, the communication device 100 may also include one or more memory 1002, on which computer program 1004 may be stored, and the processor 1001 may execute the computer program 1004 to cause the communication device 1000 to execute the method described in the above method embodiments. Optionally, the memory 1002 may also store data. The communication device 100 and the memory 1002 may be set separately or integrated together.

[0182] Optionally, the communication device 100 may also include a transceiver 1005 and an antenna 1006. The transceiver 1005 can be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., used to achieve transceiver functions. The transceiver 1005 may include a receiver and a transmitter, and the receiver can be referred to as a receiving machine or a receiving circuit, etc., for achieving reception functions; the transmitter can be referred to as a transmission machine or transmission circuit, etc., for achieving transmission functions.

[0183] Optionally, the communication device 100 may also include one or more interface circuits 1007. The interface circuit 1007 is configured to receive code instructions and transmit them to the processor 1001. The processor 1001 runs the code instructions to cause the communication device 100 to execute the method described in the above method embodiments.

[0184] The communication device 100 is the terminal. The processor 1001 is configured to execute S503 in FIG. 5; S602 in FIG. 6; S802 and S805 in FIG. 8. The transceiver 1005 is configured to execute step S401 in FIG. 4, steps S501 and S502 in FIG. 5; step S601 in FIG. 6; step S803 in FIG. 8.

[0185] The communication device 100 is the core network device. The processor is configured to execute step S701 in FIG. 7; step S804 in FIG. 8. The processor 1001 is configured to execute S801 in FIG. 8.

[0186] In one implementation, the processor 1001 may include a transceiver for implementing sending and receiving functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuits, interfaces, or interface circuits used to achieve receiving and sending functions can be separate or integrated together. The above-mentioned transceiver circuit, interface or interface circuit can be used for reading and writing code/data, or the aforementioned transceiver circuit, interface or interface circuit can be used for signal transmission or transfer.

[0187] In one implementation, the processor 1001 may store a computer program 1003, which runs on the processor 1001 and can cause the communication device 100 to execute the method described in the above method embodiments. The computer program 1003 may be embedded in the processor 1001, in which case the processor 1001 may be implemented by hardware.

[0188] In one implementation, the communication device 100 may include a circuit that can achieve the functions of sending, receiving, or communicating in the aforementioned method embodiments. The processor and transceiver described in this disclosure may be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed signal ICs, application specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (NMOS), P-type metal oxide semiconductor (PMOS), bipolar junction transistor (BJT) Bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0189] The communication device described in the above embodiments may be a terminal (such as the first-type terminal in the method embodiments described above) or a network device, but the scope of the communication device described in this application is not limited to this, and the structure of the communication device may not be limited by FIG. 10. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be:

• • [0190] (1) independent integrated circuit IC, or chip, or chip system or subsystem;
  • [0191] (2) a set of one or more ICs, optionally including storage components for storing data and computer programs;
  • [0192] (3) ASIC, such as a modem;
  • [0193] (4) a module that can be embedded in other devices;
  • [0194] (5) a receiver, terminal, intelligent terminal, cellular phone, wireless device, handheld device, mobile unit, on-board device, cloud device, artificial intelligence device, etc;
  • [0195] (6) others and so on.

[0196] Those skilled in the art can also understand that the various illustrative logical blocks and steps listed in the embodiments of the present disclosure can be implemented through electronic hardware, computer software, or a combination of the two. Whether such functions are implemented through hardware or software depends on the specific application and design requirements of the whole system. Technicians in this field can use various methods to achieve the described functions for each specific application, but this implementation should not be understood as exceeding the scope of protection in the embodiments of this disclosure.

[0197] Embodiments of the present disclosure further provide a communication system. The system includes the communication device as the terminal and the communication device as the core network device in the aforementioned embodiment of FIG. 9, or the system includes a communication device as a terminal and a communication device as a core network device in the aforementioned embodiment of FIG. 10.

[0198] The present disclosure further provides a readable storage medium on which instructions are stored, which, when executed by a computer, implement the functions of any of the above method embodiments.

[0199] The present disclosure further provides a computer program product, which, when executed by a computer, implement the functions of any of the above method embodiments.

[0200] In the above embodiments, it can be fully or partially implemented through software, hardware, firmware, or any combination thereof. When implemented using software, it can be fully or partially implemented in the form of computer program products. The computer program product includes one or more computer programs. When loading and executing the computer program on the computer, all or part of the processes or functions described in the embodiments of the present disclosure are generated. The computer may be a general-purpose computer, a specialized computer, a computer network, or other programmable devices. The computer program can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another, for example, the computer program may be transmitted from a website, a computer, a server or a data center to another website site, computer, server, or data center through wired (such as coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) methods. The computer-readable storage medium may be any available medium that the computer can access, or a data storage device such as a server or data center that includes one or more available media integrations. The available media may be magnetic media (such as floppy disks, hard drives, magnetic tapes), optical media (such as high-density digital video discs (DVDs)), or semiconductor media (such as solid state disks (SSDs)), etc.

[0201] Ordinary technical personnel in this field can understand that the first, second, and other numerical numbers involved in this disclosure are only for the convenience of description and differentiation, and are not used to limit the scope of the embodiments of this disclosure, but also indicate the order.

[0202] “At least one” in the present disclosure may also be described as “one or more”, and “multiple” may be two, three, four, or more, without limitation in this disclosure. In embodiments of the disclosure, for a kind of technical features, the technical features described in “first”, “second”, “third”, “A”, “B”, “C”, and “D” are distinguished, and there is no order or order of magnitude between the technical features described in “first”, “second”, “third”, “A”, “B”, “C”, and “D”.

[0203] The corresponding relationships shown in each table in this disclosure can be configured or predefined. The values of the information in each table are only examples and can be configured to other values, which is not limited in the disclosure. When configuring the correspondence between information and various parameters, it is not necessary to configure all the correspondence shown in each table. For example, in the table of this disclosure, the corresponding relationships shown in certain rows may not be configured. For example, appropriate deformation adjustments can be made based on the above table, such as splitting, merging, etc. The names of the parameters shown in the titles of the above tables can also use other names that can be understood by the communication device, and the values or representations of their parameters can also be understood by other values or representations that can be understood by the communication device. When implementing the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear tables, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables.

[0204] The term predefined in this disclosure can be understood as defined, defined in advance, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-fired.

[0205] Ordinary technical personnel in this field may realize that the units and algorithm steps of each example described in conjunction with the disclosed embodiments can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on the specific application and design constraints of the technical solution. Professional technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0206] Technicians in the art can clearly understand that for the convenience and conciseness of the description, the specific working processes of the system, device, and unit described above can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here.

[0207] The above is only the specific implementation of this application, but the scope of protection of this application is not limited to this. Any technical personnel familiar with this technical field can easily think of changes or replacements within the scope of technology disclosed in this application, which should be covered within the scope of protection of this application. Therefore, the protection scope of this application should be based on the protection scope of the claims.