Device and wireless communication method

Abstract

The invention provides a device and a wireless communication method. The wireless communication method executed by user equipment (UE) comprises the following steps: executing an energy saving mechanism when the UE is in a discontinuous coverage scene in which a coverage interval and a non-coverage interval appear alternately; wherein, in the energy saving mechanism, the UE is maintained in a dormant state or in a mobile terminal only connection (MICO) mode during the non-coverage interval of the discontinuous coverage scene, and the UE is configured to wake up to monitor paging during the coverage interval of the discontinuous coverage scene. The non-coverage interval is configured based on a service stop time of a service satellite and / or a service start time of a next satellite, and the service stop time of the service satellite and / or the service start time of the next satellite are / is determined based on information from satellites.

Description

Technical Field

[0001] This invention relates to the field of communication systems, and more specifically, to devices and wireless communication methods capable of being used for non-terrestrial communication in the Internet of Things (IoT), and capable of providing energy-saving mechanisms, good communication performance and / or high reliability for discontinuous coverage in IoT non-terrestrial networks (NTN). Background Technology

[0002] The third-generation partnership project (3GPP) Release 18 (Rel-18) has approved the Work Item (WI) for IoT NTN enhancements. According to the objectives of the Rel-18 Work Item Description (WI), enhancing existing power-saving mechanisms, such as discontinuous reception (DRX), power-saving mode (PSM), and extended discontinuous reception (eDRX) for one or more UEs in discontinuous coverage, is a crucial issue that urgently needs to be addressed.

[0003] Therefore, there is a need for devices and wireless communication methods that can be used for Internet of Things (IoT) non-terrestrial communication in order to provide energy-saving mechanisms, good communication performance and / or high reliability in the discontinuous coverage scenarios of IoT non-terrestrial networks (NTN). Summary of the Invention

[0004] The purpose of this invention is to propose a device and wireless communication method that can be used for non-terrestrial communication in the Internet of Things (IoT), and to provide energy-saving mechanisms, good communication performance and / or high reliability in discontinuous coverage scenarios in IoT non-terrestrial networks (NTN).

[0005] In a first aspect of the invention, a wireless communication method performed by user equipment (UE) includes: when the UE is in a discontinuous coverage scenario where coverage areas and non-coverage areas alternate, executing a power-saving mechanism, wherein in the power-saving mechanism, the UE remains in a sleep state or in a mobile initiated connection only (MICO) mode during the non-coverage period of the discontinuous coverage scenario, and is configured to wake up to monitor paging during the coverage period of the discontinuous coverage scenario; wherein the non-coverage period is configured according to the service stop time of the serving satellite and / or the service start time of the next satellite, and the service stop time of the serving satellite and / or the service start time of the next satellite is determined based on information from the satellite.

[0006] In a second aspect of the invention, a wireless communication method performed by a base station includes: sending information to a user equipment (UE) to perform a power-saving mechanism in a discontinuous coverage scenario where coverage and non-coverage areas alternate, such that the UE remains in a dormant state or in a mobile initiated connection only (MICO) mode during the non-coverage period of the discontinuous coverage scenario, and wakes up during the coverage period of the discontinuous coverage scenario to monitor paging; wherein the non-coverage period is configured according to the service stop time of the serving satellite and / or the service start time of the next satellite, and the service stop time of the serving satellite and / or the service start time of the next satellite is determined based on information from the base station.

[0007] In a third aspect of the invention, a user equipment (UE) includes: an actuator configured to execute a power-saving mechanism when the UE is in a discontinuous coverage scenario in which coverage areas and non-coverage areas alternate; wherein, in the power-saving mechanism, the UE remains in a dormant state or in a mobile initiated connection only (MICO) mode during the non-coverage area of ​​the discontinuous coverage scenario, and is configured to wake up during the coverage area of ​​the discontinuous coverage scenario to monitor paging; wherein the non-coverage area is configured according to the service stop time of the serving satellite and / or the service start time of the next satellite, and the service stop time of the serving satellite and / or the service start time of the next satellite is determined based on information from the satellite.

[0008] In a fourth aspect of the invention, a base station includes: a transmitter configured to send information to a user equipment (UE) for performing an energy-saving mechanism in a discontinuous coverage scenario where coverage and non-coverage zones alternate, such that the UE remains in a dormant state or in a mobile initiated connection only (MICO) mode during the non-coverage zone of the discontinuous coverage scenario, and wakes up during the coverage zone to monitor paging; wherein the non-coverage zone is configured according to the service stop time of a serving satellite and / or the service start time of the next satellite, and the service stop time of the serving satellite and / or the service start time of the next satellite is determined based on information from the base station.

[0009] In a fifth aspect of the invention, a user equipment (UE) includes: a memory, a transceiver, and a processor coupled to the memory and the transceiver. The processor is configured to perform the methods described above.

[0010] In a sixth aspect of the invention, a user equipment (UE) includes: a memory, a transceiver, and a processor coupled to the memory and the transceiver. The processor is configured to perform the methods described above.

[0011] In a seventh aspect of the invention, a non-transitory computer-readable storage medium stores instructions that, when executed by a computer, cause the computer to perform the above-described method.

[0012] In an eighth aspect of the invention, a chip includes a processor configured to invoke and run a computer program stored in a memory to cause a device on which the chip is mounted to perform the methods described above.

[0013] In a ninth aspect of the invention, a computer-readable storage medium is provided, wherein a computer program is stored that causes a computer to perform the above-described method.

[0014] In a tenth aspect of the invention, a computer program product includes a computer program that causes a computer to perform the methods described above.

[0015] In an eleventh aspect of the present invention, a computer program causes a computer to perform the above-described method. Attached Figure Description

[0016] To more clearly illustrate the embodiments of the present invention or related technologies, the accompanying drawings, which will be described in the embodiments, are briefly described below. Obviously, these drawings are only some embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings without any creative effort.

[0017] Figure 1A This diagram illustrates a scenario where a UE moves from a covered area to an uncovered area in an NTN network when the cell is a mobile cell.

[0018] Figure 1B This diagram illustrates a scenario where a UE moves from a covered area to an uncovered area in an NTN network when the cell is a quasi-ground fixed cell.

[0019] Figure 2A A schematic diagram illustrating the state switching of a UE between RRC connection state and PSM state according to an embodiment of the present invention is shown.

[0020] Figure 2B A schematic diagram illustrating the state switching of a UE between RRC connection state and MICO state according to an embodiment of the present invention is shown.

[0021] Figure 3 A schematic diagram illustrating the state switching of a UE between RRC connection state and eDRX state according to an embodiment of the present invention is shown.

[0022] Figure 4 A block diagram of a communication network system architecture according to an embodiment of the present invention is shown.

[0023] Figure 5 A flowchart of a wireless communication method performed by a UE according to an embodiment of the present invention is shown.

[0024] Figure 6 A flowchart illustrating a wireless communication method performed by a base station according to an embodiment of the present invention is shown.

[0025] Figure 7 A schematic diagram of the UE's RLF and RRC connection reconstruction process is shown.

[0026] Figure 8 A schematic diagram of a PSM configuration for discontinuous coverage according to an embodiment of the present invention is shown.

[0027] Figure 9 A schematic diagram illustrating the updating of the eDRX / PSM cycle during each coverage interval according to an embodiment of the present invention is shown.

[0028] Figure 10 This illustration shows a UE skipping (omitting) paging opportunities based on the broadcast service start / stop time without modifying the eDRX / PSM cycle, according to an embodiment of the present invention.

[0029] Figure 11 A schematic diagram illustrating multiple eDRX / PSM configuration examples for a UE according to an embodiment of the present invention is shown.

[0030] Figure 12A A schematic diagram of the process of performing initial eDRX / PSM configuration via initial attachment in E-UTRAN is shown according to an embodiment of the present invention.

[0031] Figure 12B A schematic diagram illustrating the process of a 5G UE performing initial eDRX / MICO configuration through a registration process according to an embodiment of the present invention is shown.

[0032] Figure 13A This diagram illustrates the process by which a UE updates its eDRX / PSM configuration in the E-UTRAN via a UE-triggered tracking area update procedure, according to an embodiment of the present invention.

[0033] Figure 13B This is a schematic diagram illustrating the process by which a 5G UE updates its eDRX / MICO configuration through a UE-triggered registration process according to an embodiment of the present invention.

[0034] Figure 14A A schematic diagram of an eDRX / PSM update process initiated by an eNB / MME according to an embodiment of the present invention is shown.

[0035] Figure 14B A schematic diagram of the eDRX / MICO configuration update and release process initiated by gNB / AMF according to an embodiment of the present invention is shown.

[0036] Figure 15 A schematic diagram of the offset values ​​configured for eDRX is shown according to an embodiment of the present invention.

[0037] Figure 16 A schematic diagram of the offset values ​​of the PSM configuration is shown according to an embodiment of the present invention.

[0038] Figure 17A A schematic diagram of the process of updating eDRX / PSM by paging a UE is shown according to an embodiment of the present invention.

[0039] Figure 17B A schematic diagram of the process of updating the eDRX / MICO configuration by paging the UE is shown according to an embodiment of the present invention.

[0040] Figure 17C A schematic diagram illustrating the process of updating the eDRX / PSM configuration by a release procedure initiated by the eNB / MME according to an embodiment of the present invention is shown.

[0041] Figure 17D A schematic diagram illustrating the process of updating the eDRX / PSM configuration by a release procedure initiated by the MME according to an embodiment of the present invention is shown.

[0042] Figure 18 A block diagram of a UE for wireless communication according to an embodiment of the present invention is shown.

[0043] Figure 19 A block diagram of a base station for wireless communication according to an embodiment of the present invention is shown.

[0044] Figure 20 A block diagram of a system for wireless communication according to an embodiment of the present invention is shown. Detailed Implementation

[0045] The embodiments of the present invention will be described in detail with reference to the accompanying drawings, the technical content, structural features, implementation objectives, and effects therein. It should be particularly noted that the terminology used in the embodiments of the present invention is only used to describe the purpose of specific embodiments and should not be considered as a limitation of the present invention.

[0046] The Internet of Things (IoT) non-terrestrial network (NTN) enhancement work item (WI) of 3GPP Release 18 (Rel-18) has been approved. One of the objectives of WID IoT_NTN_enh in RAN2 includes researching and developing, where necessary, mobility management enhancements and power-saving mechanisms for discontinuous coverage, while referencing the conclusions of SA2 research FS_5GSAT_Ph2.

[0047] The progress of the RAN2#121 meeting (February 27 to March 3, 2023) is as follows: RAN2 can continue to evaluate whether dedicated RRC signaling can be used to provide satellite information corresponding to discontinuous coverage.

[0048] RAN2 will support enhanced paging and eDRX, and will be consistent with the work of SA2 and CT1. Specific details are pending further discussion (FFS).

[0049] RAN2 may consider enhancements required for connected UEs that detect discontinuous coverage (e.g., suspending RLM, RLF detection, and RRC reconstruction procedures).

[0050] Companies that support the store and forward method can submit proposals for TEI18 during the plenary session, or submit proposals for updating WID.

[0051] RAN2 will send a liaison letter (LS) to SA2 and CT1 (cc: RAN3) to communicate and coordinate collaborative work that may need to be carried out in their specifications due to support for discontinuous coverage.

[0052] Progress of the RAN2#122 meeting (May 22-26, 2023): Discussions will focus on potential enhancements to discontinuous coverage (e.g., paging enhancements, RRC connection release enhancements, UE behavior in discontinuous coverage) until the next meeting in August 2023.

[0053] In this invention, some embodiments discuss how to handle energy-saving mechanisms, such as DRX, eDRX, and / or PSM for IoT NTN discontinuous coverage scenarios.

[0054] In this invention, the term " / " can be interpreted as "and / or". It should be noted that although an eNB is shown in the description, the disclosed example methods can be implemented by any suitable base station, such as a gNB. The term "cell" refers to a logical communication entity (e.g., via a carrier) used to communicate with a base station and may be associated with identifiers used to distinguish neighboring cells (e.g., physical cell identifier (PCID), virtual cell identifier (VCID)) that operate via the same or different carriers. In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., machine-type communication (MTC), narrowband Internet-of-Things (NB-IoT), enhanced mobile broadband (eMBB), or others) to provide access for different types of devices.

[0055] Figure 1A This illustrates the situation where a UE moves from a coverage area to a non-coverage area in an NTN network when the cell is a mobile cell. Figure 1B This illustrates the situation where a UE moves from a coverage area to a non-coverage area in an NTN network when the cell is a quasi-ground fixed cell. For example... Figure 1A (Mobile cell) and Figure 1BAs shown in the (quasi-earth fixed cell) diagram, when satellite A moves over time, the UE's state may change from a covered area to an uncovered area. It's important to note: a moving cell refers to a satellite whose coverage footprint moves with the satellite relative to a specific geographic location (reference location). A quasi-earth fixed cell refers to a cell whose coverage footprint remains fixed when the satellite moves within a specific elevation angle range relative to a geographic location (reference location) (e.g., from 60° to 120°). When the UE is in an uncovered area, there is no signal interaction between the UE and the satellite. The out-of-coverage interval is uncertain; its length may increase or decrease over time. Failure to accurately predict or configure the out-of-coverage interval may lead to the following two technical problems: 1. The UE is in RRC connection state while moving from a coverage area to an out-of-coverage area. In this situation, when satellite A leaves the UE, the UE may experience radio link failure (RLF). After entering the RLF state, the UE will continuously perform cell selection to attempt to find a new cell and re-establish the RRC connection with the approaching satellite. However, the out-of-coverage area may last for several hours, causing the UE to continuously attempt to connect during this period, resulting in significant unnecessary power consumption.

[0056] 2. The UE is in an RRC Idle / Inactive state when moving from a coverage area to an out-of-coverage area. In this situation, the UE typically configures power-saving mechanisms, such as eDRX or PSM, to periodically wake up and listen for paging (channels) from the eNB / gNB. Due to the uncertainty of the out-of-coverage area, it is impossible to accurately configure the UE's eDRX or PSM, resulting in two possible scenarios: The UE is woken up during the out-of-coverage period: In this case, the UE will attempt to listen for paging (channels) that do not actually exist, thus wasting power. The UE is woken up after the next coverage period: In this case, the UE may miss paging (channels) from the eNB. Therefore, the inability to accurately configure eDRX or PSM will cause the UE to either waste power or miss important paging information.

[0057] Therefore, how to avoid unnecessary measurements during non-coverage periods, and how to accurately configure and / or adjust the eDRX / PSM configuration according to the non-coverage intervals, are the objectives of some embodiments of the present invention.

[0058] Technical issues: 1. How can a UE avoid taking unnecessary measurements during periods of non-coverage? 2. How can eNB / UE precisely configure and / or adjust eDRX / PSM configuration based on non-coverage areas? Technical solution: 1. When the UE is in RRC connection state when moving from a covered area to an uncovered area, perform at least one of the following operations: a. Reduce the measurement latency of the UE to the serving cell.

[0059] b. Avoid the UE continuously performing cell (re)selection before re-establishing the connection, or reduce measurement time.

[0060] c. Reduce the delay in cell (re)selection.

[0061] 2. When the UE is in an RRC idle / inactive state when moving from a covered area to an uncovered area, perform at least one of the following operations: a. The eNB pages the UE to reconfigure the UE's eDRX / PSM parameters.

[0062] b. The service stop time of the eNB broadcast service satellite and / or the service start time of the next satellite.

[0063] c. The eNB configures multiple eDRX / PSM configurations for the UE.

[0064] Beneficial effects: Based on the proposed scheme, the UE can remain in a sleep state in non-coverage areas and wake up in coverage areas to monitor paging.

[0065] Power saving mode (PSM): PSM is a power-saving mechanism introduced in 3GPP Release 12 for enhanced Machine Type Communications (eMTC) or Internet of Things (IoT) UEs. The UE requests activation times (i.e., timers T3324 and T3412) through an attach, tracking area update (TAU), or routing area update (RAU) procedure. When the UE is released from RRC connection state, it enters normal idle mode and starts timers T3324 and T3412. During normal idle mode, the UE performs discontinuous reception (DRX) to monitor for paging until T3324 times out. If the UE is not paging within T3324, it enters power-saving mode and disables all non-critical functions until T3412 times out. During power-saving mode, the UE does not listen for paging (channels), therefore the UE cannot be addressed by the eNB / core network (CN). Figure 2A This illustrates the UE's state transition between RRC connected state and PSM. According to TS 24.008, the maximum value for T3412 is 320 hours × 32 = 10240 hours ≈ 426.67 days. The maximum value for T3324 is 186 minutes.

[0066] Mobile Initiated Connection Only (MICO): MICO is a power-saving mode designed specifically for 5G IoT devices connected to a 5G core network. The UE can request / update the activation time (i.e., timers T3324 and T3512) through a registration procedure or periodically register the timer. When the UE configures the activation time, it enters normal idle mode after being released from RRC connection state and starts timers T3324 and T3512. During normal idle mode, the UE performs discontinuous reception (DRX) to monitor for paging until T3324 times out. If the UE is not paging within T3324, it enters MICO mode and disables all non-critical functions until T3512 times out. During MICO mode, the UE does not listen for paging (channels), therefore the UE cannot be addressed by the gNB / core network (CN). When the UE configures a periodic registration time, it performs a periodic registration update to renegotiate the MICO mode. Figure 2BThe diagram shows the state transition of the UE between RRC connected state and MICO state. The maximum value for T3512 is 320 hours × 32 = 10240 hours ≈ 426.67 days, and the maximum value for T3324 is 186 minutes.

[0067] Extended discontinuous reception (eDRX): eDRX is another power-saving mechanism, primarily introduced for eMTC or NB-IoT UEs in 3GPP Release 12. The UE requests eDRX parameters (i.e., eDRX period, T...) through the attach or TAU / RAU procedure. eDRX,H The timer and paging time window (PTW) length L are defined in TS 24.008. After the UE is released from RRC connected state, it enters normal idle mode at system frame number PTW_start. During PTW, the UE performs DRX to listen for paging until PTW_end. Figure 3 This illustrates the state transition of the UE between RRC connected and eDRX states. According to the parameters specified in TS 24.008: For NB-IoT: T eDRX,H Maximum value = 10.24 seconds (1024 radio frames) × 1024 (maximum 1024 superframes) = 10485.76 seconds ≈ 2.91 hours. PTW maximum length = 40.96 seconds. For eMTC: T eDRX,H Maximum value = 10.24 seconds (1024 wireless frames) × 256 (maximum 256 superframes) = 2621.44 seconds ≈ 43.69 minutes. PTW maximum length = 20.48 seconds.

[0068] System architecture of 4G / 5G communication networks: Figure 4 This is a block diagram of a communication network system architecture according to an embodiment of the present invention.

[0069] Referring to FIG4, UE 10a, UE 10b, base station 200a, and network entity device 300 can execute the method of the embodiments of the present invention. Figure 4The connections between devices and device components are indicated by lines and arrows. UE 10a may include processor 11a, memory 12a, and transceiver 13a. UE 10b may include processor 11b, memory 12b, and transceiver 13b. Base station 200a may include processor 201a, memory 202a, and transceiver 203a. Network entity device 300 may include processor 301, memory 302, and transceiver 303. Processors 11a, 11b, 201a, and 301 may be configured to perform the functions, processes, and / or methods set forth in this specification. The various layers of the wireless interface protocol may be implemented in processors 11a, 11b, 201a, and 301. Memory 12a, 12b, 202a, and 302 are used to operatively store various programs and information for execution by the connected processor. Transceivers 13a, 13b, 203a, and 303 are operatively coupled to their respective processors and perform the transmission and / or reception of wireless signals. Base station 200a may be an eNB, gNB, or other wireless node. Processors 11a, 11b, 201a, and 301 may include a general-purpose central processing unit (CPU), an application-specific integrated circuit (ASIC), other chipsets, logic circuits, and / or data processing devices. Memory 12a, 12b, 202a, and 302 may include read-only memory (ROM), random access memory (RAM), flash memory, memory cards, storage media, other storage devices, and / or any combination of the above memories and storage devices. Transceivers 13a, 13b, 203a, and 303 may include baseband circuitry and radio frequency (RF) circuitry for processing radio frequency signals. When the embodiments are implemented in software, the techniques described herein can perform the functions in the form of modules, processes, functions, entities, etc. These modules can be stored in memory and executed by a processor. The memory can be integrated inside the processor or located outside the processor, and can be communicatively coupled to the processor in various ways known in the art.

[0070] Network entity device 300 can be a node in the core network (CN). The CN can include an LTE CN or a 5G CN (5GC), where the 5GC can include user plane functions (UPF), session management functions (SMF), access and mobility management functions (AMF), unified data management (UDM), policy control functions (PCF), control plane (CP) / user plane (UP) separation (CUPS), authentication server functions (AUSF), network slice selection functions (NSSF), network exposure functions (NEF), and other network entities. In some examples, the CN may also include a 4G core network (4GC). A 4GC can be an example of an evolved packet core (EPC), which may include at least one mobility management entity (MME), at least one serving gateway (SGW), and at least one packet data network (PDN) gateway (PGW). The MME can provide mobility management functions for the 4G network. Nodes within the 4GC can interconnect through one or more core network interfaces.

[0071] In some embodiments, when UE 10a or 10b is in a discontinuous coverage scenario involving alternating in-coverage and out-of-coverage areas, processor 11a or 11b is configured to execute a power-saving mechanism. In this power-saving mechanism, UE 10a or 10b remains in sleep mode or mobile initiated connection only (MICO) mode during out-of-coverage periods and is configured to wake up to listen for paging during coverage periods. The time interval of the out-of-coverage period is configured based on the service stop time of the current serving satellite and / or the service start time of the next satellite, which is determined based on information from the satellites. This solution addresses the problems in the prior art, providing a non-terrestrial communication method for the Internet of Things (IoT), offering a power-saving mechanism for discontinuous coverage in IoT NTN, providing good communication performance and / or high reliability. The UE can remain in sleep mode during out-of-coverage periods and wake up to listen for paging during coverage periods.

[0072] In some embodiments, transceiver 203a is configured to send information to UE 10a or 10b, enabling it to operate in discontinuous coverage scenarios where coverage and non-coverage areas alternate. In this scenario, UE 10a or 10b remains in sleep or MICO mode during non-coverage periods and wakes up during coverage periods to listen for paging; wherein the time interval of the non-coverage period is configured based on the service stop time of the currently serving satellite and / or the service start time of the next satellite, and the service stop time of the serving satellite and / or the service start time of the next satellite are determined based on information from the base station. This solution addresses the problems in the prior art, providing a non-terrestrial communication method for IoT, a power-saving mechanism for discontinuous coverage in IoT NTN, good communication performance, and / or high reliability. The UE can remain in sleep during non-coverage periods and wake up during coverage periods to listen for paging.

[0073] Figure 5A wireless communication method 500 performed by a UE according to some embodiments of the present invention is illustrated. In some embodiments, the method 500 includes: operation 502, executing a power-saving mechanism when the UE is in a discontinuous coverage scenario where coverage areas and non-coverage areas alternate; wherein, in this power-saving mechanism, the UE remains in a sleep state or MICO mode during the non-coverage area and is configured to wake up to listen for paging during the coverage area; wherein the time interval of the non-coverage area is configured based on the service stop time of the serving satellite and / or the service start time of the next satellite, and the service stop time of the serving satellite and / or the service start time of the next satellite is determined according to information from the satellite. The sleep state may refer to the state in which the UE is when there is no data to transmit during the non-coverage area of ​​the discontinuous coverage scenario. This scheme can solve the problems in the prior art, provide non-terrestrial communication for IoT, provide a power-saving mechanism for discontinuous coverage in IoT NTN, and provide good communication performance and / or high reliability. The UE can remain in sleep in the non-coverage area and wake up to listen for paging during the coverage area.

[0074] Figure 6 A wireless communication method 600 performed by a base station according to some embodiments of the present invention is illustrated. In some embodiments, the method 600 includes: operation 602, sending information to a UE to cause the UE to perform a power-saving mechanism in a discontinuous coverage scenario where coverage areas and non-coverage areas alternate; wherein, during the non-coverage area of ​​the discontinuous coverage scenario, the UE remains in a sleep state or MICO mode and wakes up during the coverage area to listen for paging; wherein the time interval of the non-coverage area is configured based on the service stop time of the serving satellite and / or the service start time of the next satellite, and the service stop time of the serving satellite and / or the service start time of the next satellite is determined according to information from the base station. This scheme can solve the problems in the prior art, provide non-terrestrial communication for IoT, provide a power-saving mechanism for discontinuous coverage in IoT NTN, and provide good communication performance and / or high reliability. The UE can remain in sleep in the non-coverage area and wake up during the coverage area to listen for paging.

[0075] Example: The UE remains in RRC connection state when moving from a covered area to an uncovered area.

[0076] In this situation, the UE may be unable to complete data transmission before entering an out-of-coverage area. As the satellite continues to move, the Reference Signal Received Power (RSRP) and Reference Signal Received Quality (RSRQ) measured by the UE will gradually decrease, eventually causing the UE to trigger an RLF. (That is, an RLF is triggered after the UE receives N310 consecutive asynchrony indications from the physical layer, and the value of N310 can be pre-configured by the eNB.) After declaring an RLF, the UE will start timer T310 and attempt to restore the connection with the serving cell before timer T310 expires. Figure 7 As shown. If T310 times out, indicating an inability to re-establish a connection with the serving cell, the UE will execute an RRC re-establishment procedure to select a suitable cell to camp on (i.e., a cell re-selection process) and re-establish an RRC connection with that cell to continue data transmission. Since the non-coverage period can last for several hours, allowing the UE to continuously perform radio restoration and cell (re)selection will result in significant power waste. To avoid this power consumption, some power-saving mechanisms can be applied to the UE.

[0077] Reduce the measurement latency of the UE to the serving cell: Since serving satellites eventually leave the UE's coverage area, continuously measuring the serving cell to attempt to restore the connection would result in unnecessary power consumption. Furthermore, the connection restoration wait time (i.e., the T310 timer) can last for several seconds (up to 8 seconds), so shortening or prematurely stopping the T310 timer based on information transmitted by the satellite is useful. If the cell is a quasi-fixed Earth cell, the information provided might include: service stop time, leaving indication, etc. If the cell is a mobile cell, the information provided might include: ephemeris information, cell reference location (i.e., cell center), cell coverage area size (i.e., cell radius), etc. This information can be sent to the UE via broadcast or unicast messages. Based on this information, the UE can predict when the satellite will leave. In one embodiment, the UE can be configured by the eNB to use a shorter timer, called T310', to shorten the recovery time for a leaving serving cell. In another embodiment, this shorter timer can be a shortened version of the T310 timer. In another embodiment, the UE can send information (e.g., RAN layer indication or NAS layer indication) to the eNB / MME / AMF to indicate impending discontinuous coverage. Upon receiving the RRCRelease message, the UE can enter the RRC_IDLE / RRC_INACTIVE state, thereby avoiding the initiation of the T310 timer. In another embodiment, when the UE detects that a serving satellite is about to leave (e.g., based on a satellite service stop time broadcast by the eNB or a service stop time calculated by the UE itself), it can prematurely stop the T310 timer, send a Releasecause (e.g., Discontinuous coverage) to the upper layer (e.g., the RRC layer), and enter the RRC_IDLE / RRC_INACTIVE state.

[0078] To prevent the UE from continuously performing cell (re)selection or to reduce measurement time before re-establishing a connection: Based on traditional UE behavior, after the T310 timer expires, the UE should continue performing cell (re)selection until one or more available cells are found. Since discontinuous coverage intervals can last for hours, and no discoverable cells may be available during this period, continuous cell (re)selection will significantly impact the UE's power consumption. Therefore, mechanisms can be applied to the UE to reduce power consumption.

[0079] The eNB can provide the UE with the arrival time of the next satellite. This information can be sent to the UE via broadcast or unicast message. After the T310 timer expires, the UE can delay the cell (re)selection operation until a few seconds before the service start time of the next satellite.

[0080] The eNB / MME sends eDRX and / or PSM parameters to the UE. These parameters may include the paging time window (PTW), eDRX period, T3324, T3412, etc. The provided parameters may be updates to previously configured parameters (e.g., new parameters or offsets). These parameters can be transmitted via unicast messages (e.g., RRCConnectionReconfiguration, DLInformationTransfer, or RRCConnectionRelease messages). The eNB / MME should send the eDRX / PSM parameters to the UE before releasing the UE, and then release the UE according to the service stop time. After receiving the RRCConnectionRelease message from the eNB, the UE enters the eDRX / PSM state (i.e., activates eDRX / PSM configuration) and can stop performing cell (re)selection measurements in non-coverage areas with discontinuous coverage. Figure 8 An example of a PSM configuration for non-contiguous coverage is shown.

[0081] Reduce cell (re)selection latency: To reduce the latency of cell (re)selection measurements (the maximum value of the T311 timer is 120 seconds), the eNB can send information about the next satellite to the UE via unicast or broadcast messages. This information may include the cell identifier, satellite identifier, and / or frequency band information of the next satellite. For unicast messages, the eNB can send this information via the RRCConnectionRelease message. For broadcast messages, the eNB can send this information via system information, such as SystemInformationBlockType4, SystemInformationBlockType5, SystemInformationBlockType32, or other system information blocks.

[0082] The UE remains in the RRC Idle / Inactive state when moving from coverage to non-coverage.

[0083] For NB-IoT UEs, the UE spends most of its time in RRC Idle / Inactive state. When the UE is in RRC Idle / Inactive state, it periodically listens for paging (channels) according to the eDRX / PSM configuration. The UE should wake up from sleep mode (power saving mode) during covered periods and enter sleep mode (power saving mode) during non-covered periods. However, non-covered areas may not be completely periodic. The asynchrony between the eDRX / PSM shutdown period and the actual non-covered area may cause the UE to be incorrectly woken up in the non-covered area or incorrectly enter sleep mode in the covered area. Therefore, reconfiguring the eDRX / PSM period to maintain synchronization between the eDRX / PSM shutdown period and the non-covered area is very useful. Several reconfiguration mechanisms can be adopted for the UE.

[0084] eNB / MME reconfigures the UE's eDRX / PSM parameters by paging the UE: In this scenario, the eNB / MME will page the UE within the coverage area, causing the UE to enter the RRC connected state. The eNB / MME can send eDRX and / or PSM parameters to the UE via the RRCConnectionReconfiguration, DLInformationTransfer, or RRCConnectionRelease messages. Here, eNB / MME means that the MME sends paging and / or eDRX / PSM parameters to the UE through the eNB. Furthermore, when the UE determines that it needs to modify the eDRX / PSM configuration based on a timer, the service stop time of the serving satellite, and / or the service start time of subsequent satellites, the UE can request new eDRX and / or PSM parameters (or parameter offsets) from the MME via the RRCConnectionSetupComplete, ULInformationTransfer, or UEAssistanceInformation messages. The eDRX / PSM parameters are controlled by the MME. The offset values ​​of the eDRX / PSM configuration belong to the NAS layer parameters. The advantage of this mechanism is its minimal impact on 3GPP standards. However, this mechanism requires the UE to enter the RRC connected state within each coverage area, thus consuming more power. Figure 9 For example, when the UE is in the coverage area, the eDRX / PSM period will be modified to the initial period p plus the offset δ, so that the on period configured by eDRX / PSM matches the in-coverage area and the off period matches the out-of-coverage area.

[0085] The eNB broadcasts the service stop time of the currently serving satellite and / or the service start time of the next serving satellite.

[0086] In this scenario, the UE remains in RRC Idle / Inactive state and monitors control information from the eNB. The UE can receive broadcast information from the eNB and calculate (update) its eDRX / PSM cycle accordingly. This information may include the service stop time of the currently serving satellite and / or the arrival time of the next satellite. In another embodiment, this information may also be a countdown timer (e.g., 24 hours) for updating the eDRX / PSM configuration. Based on this information, when the UE determines that it needs to modify the eDRX / PSM cycle to match the service stop time of the serving satellite and / or the service start time of the next satellite, the UE requests new eDRX / PSM parameters from the MME via RRCConnectionSetupComplete, ULInformationTransfer, or UEAssistanceInformation messages. Based on this information, the UE may also take appropriate actions, such as ignoring paging opportunities in out-of-coverage intervals to avoid meaningless measurements. Figure 10 For example, by receiving the service start time of the next arrival of satellite A, the UE can delay its wake-up time to monitor the paging channel. Furthermore, by receiving the service stop time of serving satellite A, the UE can also enter sleep mode earlier.

[0087] The MME configures multiple eDRX / PSM configurations for the UE.

[0088] Based on the analysis described above, most non-coverage intervals range from 9 to 13.3 hours, with an average of approximately 11.9 hours, while a very short interval of about 1.6 hours occurs approximately once a month. To handle these very short intervals, multiple eDRX / PSM configurations can be configured for the UE. Figure 11 For example, an 11.9-hour non-coverage interval can be configured as eDRX / PSM #1, while a 1-month non-coverage interval can be configured as eDRX / PSM #2. By combining eDRX / PSM #1 and eDRX / PSM #2 configurations, the UE can be configured for non-periodic non-coverage intervals, such as 1.6 hours, 10.3 hours, and 11.9 hours. It's important to note that eDRX / PSM #1 and eDRX / PSM #2 configurations can be applied to the same satellite or to different satellites with different non-coverage intervals. The advantage of this mechanism is that the UE can remain in the RRC Idle / Inactive state without entering the RRC connected state to modify the eDRX / PSM period, thereby reducing power consumption.

[0089] The eNB broadcasts the offset of the eDRX / PSM configuration.

[0090] Due to a mismatch between the eDRX PTW (or PSM / MICO T3324 timer) and the satellite's coverage area, the UE may initiate paging detection too early (i.e., before the satellite covers the UE's area) or too late (i.e., when the satellite is about to leave the UE's area). While the eDRX / PSM configuration can be reconfigured via the Attach or TAU procedures, the UE needs to enter the RRC connected state, resulting in significant signaling interaction and increased power consumption. If the mismatch is minor (e.g., the eDRX PTW or PSM / MICO T3324 timer still partially overlaps with the coverage area), the eDRX / PSM parameters can be fine-tuned by broadcasting a common offset for UEs in a specific area, thereby improving power efficiency. The common offset can be a time offset for the eDRX PTW or PSM / MICO timer T3324 for the currently serving satellite, or a time offset for the eDRX PTW or PSM / MICO timer T3324 for the next satellite; this time offset can be positive or negative. The common offset can also be the time offset of the service stop time of the serving satellite or the time offset of the service start time of the next satellite. This common offset can be an AS layer parameter, which is different from the NAS layer parameter. Based on the common offset from the serving satellite, UEs within a specific area can extend or shorten the eDRX PTW or PSM / MICO timer T3324 corresponding to the serving satellite without entering the RRC connected state (i.e., the eDRX period or PSM / MICO T3412 remains unchanged). Furthermore, the UE can also extend or shorten the eDRX PTW or PSM / MICO timer T3324 corresponding to the next satellite based on the common offset of the next satellite.

[0091] UE eDRX / PSM configuration process: It is important to note that although the following diagrams show the sequence of steps, the actual steps can be performed in a different order, or steps can be combined in different scenarios (for example, system information broadcasts and paging message broadcasts can be combined). The entities in the following diagrams are based on E-UTRAN examples, but this does not exclude situations in 5G NR networks. When performing the eDRX / PSM configuration procedure in a 5G NR network, the base station is the gNB, and the control entity responsible for eDRX / PSM configuration is the access and mobility management function (AMF).

[0092] Initial configuration of eDRX / PSM: Figure 12A This paper illustrates the initial eDRX / PSM configuration procedure performed via initial attach of the E-UTRAN, according to an embodiment of the present invention. In a 5G NR network, the initial configuration of eDRX / MICO is performed through a registration procedure between the UE, gNB, and AMF, which will be described in the next subsection. The initial eDRX / PSM configuration procedure includes at least one of the following steps.

[0093] Step 0: The UE receives broadcast system information from the eNB.

[0094] Note 1: For quasi-Earth fixed cells, system information may include the service stop time of the serving satellite and the service start time of the next satellite. The format of the service stop time of the current satellite and the service start time of the next satellite is a time offset relative to the start time of the current week (Monday 00:00:00 UTC), in units of 1 second.

[0095] Note 2: For mobile cells, the service stop time of the serving satellite and the service start time of the next satellite may differ for UEs in different locations. System information may include ephemeris information, the cell's reference location (i.e., cell center), elevation angle, maximum distance, and / or cell coverage area (e.g., cell radius).

[0096] Note 3: System information may include the physical cell identifier, satellite identifier, or satellite ephemeris of the serving satellite and the next satellite.

[0097] Step 1: The UE completes the random access procedure based on the service stop time of the serving satellite.

[0098] Note 1: If there is not enough time to complete random access (i.e., the serving satellite is about to leave the UE's coverage area), the UE should avoid initiating the random access process.

[0099] Step 2: The UE sends a Non-Access Stratum (NAS) message to the serving satellite: ATTACHREQUEST. The ATTACH REQUEST message is carried via RRC: RRCConnectionSetupComplete or ULInformationTransfer message. The ATTACH REQUEST message may include eDRX / PSM parameters, such as: for eDRX: PTW (Paging Time Window and T...). eDRX,HFor PSM: T3324 and T3412. The length of PTW or T3324 can be configured to the coverage area of ​​the serving satellites, while T... eDRX,H The length of T3412 can be configured as the coverage area plus the non-coverage area. The non-coverage area can be configured as: the service start time of the next satellite minus the service stop time of the currently serving satellite.

[0100] Note 1: NAS messages: The ATTACH REQUEST message may contain the service stop time of the currently serving satellite and the service start time of the next satellite. The ATTACH REQUEST message may also contain UE location information, cell identifier, satellite identifier, or satellite ephemeris. This information is used by the Mobility Management Entity (MME) to determine the PTW and T of the eDRX. eDRX,H The values, and the values ​​of T3324 and T3412 of PSM.

[0101] Note 1.1: For quasi-Earth fixed cells, the service stop time of the current satellite and the service start time of the next satellite can be the same as those received through system information in step 0.

[0102] Note 1.2: For mobile cells, the service stop time of the current satellite and the service start time of the next satellite can be calculated by the UE based on ephemeris information, the cell's reference location (i.e., cell center), elevation angle, maximum distance and / or cell coverage area (i.e., cell radius).

[0103] Note 1.3: The service stop time of the current satellite and the service start time of the next satellite are in the format of time offset relative to the start time of this week (Monday 00:00:00 UTC), in 1 second.

[0104] Note 2: The ATTACH REQUEST message can contain multiple parameters of the eDRX / PSM configuration.

[0105] Step 3: The satellite forwards the ATTACH REQUEST message to the eNB.

[0106] Note 1: If the satellite is a regenerative satellite (i.e., the eNB is implemented on the satellite), this step can be omitted. If the satellite is a transparent satellite (i.e., the eNB is implemented on the ground and connects to the UE via the satellite), the satellite only forwards the ATTACH REQUEST message to the eNB via the feeder link.

[0107] Step 4: The eNB forwards the ATTACH REQUEST message to the MME. The ATTACH REQUEST message is carried in the S1AP Initial UE message.

[0108] Step 5: The MME replies to the eNB with an ATTACH ACCEPT message. The ATTACH ACCEPT message is carried within the S1AP Initial Context Setup Request message. If the MME accepts the UE's eDRX / PSM request, it includes the eDRX / PSM parameters (e.g., eDRX PTW and T) in the ATTACH ACCEPT message. eDRX,H (PTM's T3324 and T3412).

[0109] Note 1: If the MME is configured with a countdown timer for the validity of the eDRX / PSM configuration, the countdown timer will be sent in the ATTACH ACCEPT message.

[0110] Step 6: The eNB forwards the ATTACH ACCEPT message to the satellite. The ATTACH ACCEPT message can be carried by the RRC's RRCConnectionReconfiguration or DLInformationTransfer message.

[0111] Note 1: This step can be omitted if the satellite is a regenerative satellite.

[0112] Note 2: If the eNB has configured a countdown timer for the validity of the eDRX / PSM configuration, the eNB will send the countdown timer in the RRCConnectionReconfiguration message of the RRC.

[0113] Step 7: The satellite forwards the ATTACH ACCEPT message to the UE. The ATTACH ACCEPT message can be carried by the RRC's RRCConnectionReconfiguration or DLInformationTransfer message. After receiving the ATTACH ACCEPT message, the UE establishes an eDRX / PSM configuration for the default radio bearer.

[0114] Note 1: If the UE requests multiple eDRX / PSM configurations in step 2, the ATTACH ACCEPT message may contain parameters for multiple eDRX / PSM configurations.

[0115] Note 2: When the UE receives a countdown timer for the validity of the eDRX / PSM configuration, the UE will start the eDRX / PSM configuration countdown timer.

[0116] Step 8: After the data transmission is completed, the eNB can send an S1AP:UE CONTEXT RELEASE REQUEST message with the reason value "User Inactivity" to the MME to initiate the release of the UE radio bearer.

[0117] Note 1: This step is optional and can be omitted when the MME actively initiates UE release.

[0118] Note 2: The eNB should send the S1AP:UE CONTEXTRELEASE REQUEST message before the service stop time of the UE's serving satellite.

[0119] Note 3: The S1AP:UE CONTEXT RELEASE REQUEST message can carry the service stop time of the satellite to which the UE belongs.

[0120] Note 4: The cause value can be a new cause (e.g., "Discontinuous Coverage"), rather than any existing cause value.

[0121] Step 9: The MME sends an S1AP: UE CONTEXT RELEASE COMMAND message to the eNB to release the UE.

[0122] Note 1: If the MME has information about the service stop time of the current satellite and the service start time of the next satellite, the MME can initiate an S1AP: UE CONTEXT RELEASE COMMAND message to the UE via the eNB.

[0123] Step 10: The eNB sends an RRCConnectionRelease message to the satellite to release the UE.

[0124] Note 1: The RRCConnectionRelease message may contain ReleaseCause (e.g., "Discontinuous Coverage").

[0125] Step 11: The satellite forwards the RRCConnectionRelease message to the UE.

[0126] Step 12: After receiving the RRCConnectionRelease message, the UE enters the RRC Idle state and starts the eDRX / PSM operation.

[0127] Note 1: During periods of non-coverage, the UE can skip paging monitoring according to the configured eDRX / PSM cycle.

[0128] Initial eDRX / MICO configuration for 5G UE: Figure 12B This paper illustrates a process for performing initial eDRX / MICO configuration for a 5G UE through a registration process according to an embodiment of the present invention. The initial eDRX / MICO configuration process includes at least one of the following steps.

[0129] Step 0: The UE receives broadcast system information from the gNB.

[0130] Note 1: For quasi-Earth fixed cells, system information may include the service stop time of the current satellite and the service start time of the next satellite. The format of the service stop time of the current satellite and the service start time of the next satellite is a time offset based on the current week start time (Monday 00:00:00 UTC), in units of 1 second.

[0131] Note 2: For mobile cells, the service stop time of the current satellite and the service start time of the next satellite may differ for UEs in different locations. System information may include ephemeris information, the cell's reference location (i.e., cell center), elevation angle, maximum distance, and / or cell coverage footprint size (i.e., cell radius).

[0132] Note 3: System information may include the physical cell identifiers of the current satellite and the next satellite.

[0133] Step 1: The UE completes the random access procedure based on the current satellite service downtime.

[0134] Note 1: If there is not enough time to complete random access (i.e., the current satellite is about to leave the UE's coverage area), the UE should avoid initiating the random access process.

[0135] Step 2: The UE sends a NAS message to the current satellite: a Registration Request message, with the registration type set to "initial registration". The Registration Request message is carried within an RRC: RRCSetupComplete or ULInformationTransfer message. The Registration Request message may include relevant eDRX / MICO parameters, such as the eDRX's PTW and T... eDRX,H ; T3324 and T3512 under MICO (Mobile Initiated Connection Only) mode. The duration of PTW or T3324 can be configured to the current satellite's coverage time interval, while T eDRX,H The duration of the T3512 connection can be configured to include the coverage time interval plus the non-coverage time interval. The non-coverage time interval can be configured as: the service start time of the next satellite minus the service stop time of the current satellite.

[0136] Note 1: NAS Message: The Registration Request message may include coverage duration, non-coverage duration, current satellite service stop time, and / or the next satellite service start time. This information is used by the Access and Mobility Management Function (AMF) to determine the eDRX's PTW and T. eDRX,H The values, and the values ​​of T3324 and T3512 in MICO mode.

[0137] Note 1.1: For quasi-Earth fixed cells, the service stop time of the current satellite and the service start time of the next satellite can be the same as the value carried in the system information in step 0.

[0138] Note 1.2: For mobile cells, the service stop time of the current satellite and the service start time of the next satellite can be calculated by the UE based on ephemeris information, the reference position of the cell (i.e., cell center), elevation angle, maximum distance and / or cell coverage footprint size (i.e., cell radius).

[0139] Note 1.3: The format of the current satellite's service stop time and the next satellite's service start time is: time offset relative to the current week start time (Monday 00:00:00 UTC), in 1 second.

[0140] Note 2: The Registration Request message may include multiple parameters of the eDRX / MICO configuration.

[0141] Step 3: The satellite forwards the Registration Request message to the gNB.

[0142] Note 1: This step can be omitted if the satellite is a regenerative satellite (i.e., the gNB is deployed on a satellite). If the satellite is a transparent satellite (i.e., the gNB is deployed on the ground and connects to the UE via the satellite), the satellite only forwards the Registration Request message to the gNB via the feeder link.

[0143] Step 4: The gNB forwards the Registration Request message to the AMF. The Registration Request message is carried in the NGAP: Initial UE message.

[0144] Step 5: The AMF replies to the gNB with a Registration Accept message. The Registration Accept message is carried within the NGAP: Initial Context Setup Request message. If the AMF accepts the UE's eDRX / MICO request, the Registration Accept message contains the eDRX / MICO parameters (i.e., the eDRX's PTW and T). eDRX,H (and T3324 and T3512 in MICO mode).

[0145] Note 1: If the AMF has set a countdown timer for verification in the eDRX / MICO configuration, the AMF will include the countdown timer in the RegistrationAccept message.

[0146] Step 6: The gNB forwards the Registration Accept message to the satellite. The Registration Accept message can be carried in the RRC: RRCReconfiguration or DLInformationTransfer message.

[0147] Note 1: This step can be omitted if the satellite is a regenerative satellite.

[0148] Note 2: If the gNB sets a countdown timer for verification in the eDRX / MICO configuration, the gNB will send the countdown timer in the RRC: RRCReconfiguration message.

[0149] Step 7: The satellite forwards the Registration Accept message to the UE. The Registration Accept message can be carried in an RRC:RRCReconfiguration or DLInformationTransfer message. After receiving the Registration Accept message, the UE will set the eDRX / MICO configuration for the default radio bearer.

[0150] Note 1: If the UE requests multiple eDRX / MICO configurations in step 2, the Registration Accept message may contain parameters for multiple eDRX / MICO configurations.

[0151] Note 2: The UE will start the countdown timer after receiving the countdown timer for eDRX / MICO configuration verification.

[0152] Step 8: After data transmission is complete, the gNB can send an NGAP: UE CONTEXT RELEASE REQUEST message with the cause value "User Inactivity" to the AMF to initiate the release of the radio bearer for the UE.

[0153] Note 1: This step is optional. If the UE release is initiated by the AMF, this step can be omitted.

[0154] Note 2: gNB should send the NGAP:UE CONTEXTRELEASE REQUEST message to AMF before the current satellite service stop time arrives.

[0155] Note 3: NGAP: The UE CONTEXT RELEASE REQUEST message may include the service outage time of the current satellite where the UE is located.

[0156] Note 4: The cause value can be a new cause (e.g., "Discontinuous Coverage"), rather than any existing cause value.

[0157] Step 9: The AMF sends an NGAP: UE CONTEXT RELEASE COMMAND message to the gNB to release the UE.

[0158] Note 1: If the AMF has information such as the length of the coverage period, the length of the non-coverage period, the service stop time of the current satellite, and / or the service start time of the next satellite, the AMF can proactively send an NGAP message to the UE via the gNB: UE CONTEXTRELEASE COMMAND.

[0159] Step 10: gNB sends an RRRCRelease message to the satellite to release the UE.

[0160] Note 1: The RRCRelease message may contain ReleaseCause (e.g., "Discontinuous Coverage").

[0161] Step 11: The satellite forwards the RRCRelease message to the UE.

[0162] Step 12: After receiving the RRC Lease message, the UE enters the RRC Idle state and activates the eDRX / MICO operation.

[0163] Note 1: Based on the configured eDRX / MICO cycle, the UE can skip paging listening during non-coverage periods.

[0164] Update eDRX / PSM configuration: Update the eDRX / PSM configuration on the UE side.

[0165] Figure 13A This illustration shows a procedure for updating the eDRX / PSM configuration of the E-UTRAN using a UE-initiated tracking area update process, according to an embodiment of the present invention. In the 5G NR network scenario, the updated eDRX / MICO configuration is performed through a registration process between the UE, gNB, and AMF, which will be described in the next subsection. The procedure for updating the eDRX / PSM configuration of the E-UTRAN via a UE-initiated tracking area update process includes at least one of the following steps.

[0166] Step 0: The UE receives broadcast system information from the eNB.

[0167] Note 1: For quasi-geostationary cells, the system information may include the current satellite's service stop time and the next satellite's service start time.

[0168] Note 2: For mobile cells, the current satellite service stop time and the next satellite service start time may differ for UEs at different locations. System information may include ephemeris information, the cell's reference location (i.e., cell center), and / or the cell's coverage area (e.g., cell radius).

[0169] Note 3: System information may include the physical cell identifier, satellite identifier, or satellite ephemeris information of the serving satellite and the next satellite.

[0170] Step 1: When the UE determines that the service stop time of the current satellite falls outside the activation time of the current eDRX / PSM cycle (later than) the activation time of the current eDRX / PSM cycle, or the service start time of the next satellite falls outside the activation time of the subsequent eDRX / PSM cycle (earlier than / later than) the activation time of the subsequent eDRX / PSM cycle, the UE may initiate a random access procedure to update the eDRX / PSM configuration.

[0171] Note 1: If there is not enough time to complete random access (i.e., the serving satellite is about to leave the UE's coverage area), the UE can avoid initiating the random access process.

[0172] Note 2: If the UE has configured a countdown timer for eDRX / PSM configuration verification, the UE can initiate a random access procedure to update the eDRX / PSM configuration when the countdown timer reaches zero.

[0173] Step 2: The UE sends a NAS message to the serving satellite: Tracking Area Update Request (TRACKING AREA UPDATEREQUEST) message. This TRACKING AREA UPDATE REQUEST message is carried within an RRC: RRCConnectionSetupComplete or ULInformationTransfer message. The TRACKING AREA UPDATEREQUEST message may include updated eDRX / PSM parameters, such as the eDRX's PTW and T. eDRX,H And the T3324 and T3412 of PSM. The length of PTW or T3324 can be configured to serve satellites during coverage time, while T eDRX,H The length of T3412 can be configured to add the coverage time to the non-coverage time. The non-coverage time can be configured as the service start time of the next satellite minus the service stop time of the currently serving satellite.

[0174] Note 1: The TRACKING AREA UPDATE REQUEST message may include coverage time, non-coverage time (e.g., the service start time of the next satellite minus the service stop time of the current satellite), the service stop time of the current satellite, and / or the service start time of the next satellite. This information is provided to the MME to determine the eDRX PTW and T.eDRX,H And the values ​​of T3324 and T3412 of PSM.

[0175] Note 1.1: For mobile cells, the TRACKING AREA UPDATE REQUEST message may include the UE's location information so that the MME can determine the eDRX / PSM parameters.

[0176] Note 2: The TRACKING AREA UPDATE REQUEST message may include parameters of multiple eDRX / PSM configurations.

[0177] Step 3: The satellite forwards the TRACKING AREA UPDATE REQUEST message to the eNB.

[0178] Note 1: This step can be omitted if the satellite is a regenerative satellite (i.e., the eNB is implemented on the satellite). If the satellite is a transparent satellite (i.e., the eNB is implemented on the ground and connects to the UE via the satellite), the satellite only forwards the TRACKINGAREA UPDATE REQUEST message to the eNB via the feeder link.

[0179] Step 4: The eNB forwards the TRACKING AREA UPDATE REQUEST message to the MME. This TRACKING AREA UPDATE REQUEST message is carried in the S1AP: Initial UE message.

[0180] Step 5: The MME replies with a TRACKING AREA UPDATE ACCEPT message to the eNB. This TRACKING AREA UPDATE ACCEPT message is carried within the S1AP: Initial Context Setup Request message. If the MME accepts an eDRX / PSM request from the UE, the TRACKING AREA UPDATE ACCEPT message will contain the eDRX / PSM parameters (i.e., the PTW and T of the eDRX). eDRX,H (and T3324 and T3412 of PSM). The values ​​of the eDRX / PSM parameters in the TRACKING AREA UPDATE ACCEPT message can be: the same as the parameters requested by the UE in the TRACKING AREA UPDATE REQUEST message; or updated eDRX / PSM parameters, whose values ​​may differ from those in the TRACKING AREA UPDATE REQUEST message.

[0181] Note 1: If the MME has set an authentication countdown for the eDRX / PSM configuration, the MME can update the countdown in the TRACKING AREAUPDATE ACCEPT message.

[0182] Step 6: The eNB forwards the TRACKING AREA UPDATE ACCEPT message to the satellite. This TRACKING AREA UPDATE ACCEPT message is carried in either the RRC: RRCConnectionReconfiguration or DLInformationTransfer message.

[0183] Note 1: If the satellite is a regenerative satellite (i.e., the eNB is implemented on the satellite), this step can be omitted.

[0184] Note 2: If the eNB has set a verification countdown timer for the eDRX / PSM configuration, the eNB can update the countdown timer in the RRC:RRCConnectionReconfiguration message.

[0185] Step 7: The satellite forwards the TRACKING AREA UPDATE ACCEPT message to the UE. This TRACKING AREA UPDATE ACCEPT message is carried in an RRC: RRCConnectionReconfiguration or DLInformationTransfer message. After receiving the TRACKING AREA UPDATE ACCEPT message, the UE updates the eDRX / PSM configuration of the default radio bearer.

[0186] Note 1: If the UE requests multiple eDRX / PSM configurations in step 2, the TRACKING AREA UPDATEACCEPT message may contain parameters for multiple eDRX / PSM configurations.

[0187] Note 2: The UE starts the countdown timer when it receives the (updated) countdown timer for eDRX / PSM configuration verification.

[0188] Step 8: After the data transmission is completed, the eNB can send an S1AP: UE CONTEXT RELEASE REQUEST message to the MME, carrying the reason value "User Inactivity", to initiate the release of the UE's radio bearer.

[0189] Note 1: This step is optional and can be omitted when the MME actively initiates the release of the UE.

[0190] Note 2: The eNB should send the S1AP:UE CONTEXT RELEASEREQUEST message before the service stop time of the UE's serving satellite.

[0191] Note 3: S1AP: The UE CONTEXT RELEASE REQUEST message may contain the service stop time of the satellites used by the UE.

[0192] Note 4: This cause value can be a new cause (e.g., "Discontinuous Coverage"), which is different from any existing cause.

[0193] Step 9: The MME sends an S1AP: UE CONTEXT RELEASE COMMAND message to the eNB to release the UE.

[0194] Note 1: If the MME has information about the service stop time of the currently serving satellite and the service start time of the next satellite, the MME can send an S1AP: UE CONTEXT RELEASE COMMAND message to the UE through the eNB.

[0195] Step 10: The eNB sends an RRCConnectionRelease message to the satellite to release the UE.

[0196] Note 1: The RRCConnectionRelease message can contain a ReleaseCause (e.g., "Discontinuous Coverage").

[0197] Step 11: The satellite forwards the RRCConnectionRelease message to the UE.

[0198] Step 12: After receiving the RRCConnectionRelease message, the UE enters the RRC Idle state and performs eDRX / PSM operations based on the updated eDRX / PSM cycle and the updated eDRX / PSM configuration.

[0199] Note 1: UEs can skip Paging monitoring during non-coverage time intervals.

[0200] Update the eDRX / MICO configuration for 5G UEs: Figure 13BThis is a schematic diagram illustrating a registration process initiated by a 5G UE to update the eDRX / MICO configuration according to an embodiment of the present invention. The eDRX / MICO update process for the 5G UE includes at least one of the following steps.

[0201] Step 0: The UE receives broadcast system information from the gNB.

[0202] Note 1: For quasi-Earth fixed cells, system information may include the current satellite's service stop time and the next satellite's service start time.

[0203] Note 2: For mobile cells, the current satellite service stop time and the next satellite service start time may differ for UEs at different locations. System information may include ephemeris information, cell reference location (i.e., cell center), elevation angle, maximum distance, and / or cell coverage footprint size (i.e., cell radius).

[0204] Note 3: System information may include the physical cell identifiers of the current satellite and the next satellite.

[0205] Step 1: When the UE determines that the service stop time of the current satellite is later than the activation time of the current eDRX / MICO cycle, or the service start time of the next satellite is not earlier than or later than the activation time of the subsequent eDRX / MICO cycle, the UE can initiate a random access procedure to update the eDRX / MICO configuration.

[0206] Note 1: If there is not enough time to complete random access (i.e., the current satellite is about to leave the UE's coverage area), the UE can avoid initiating the random access process.

[0207] Note 2: If the UE has configured a countdown timer for eDRX / MICO configuration verification, the UE can initiate a random access procedure to update the eDRX / MICO configuration when the countdown timer reaches zero.

[0208] Step 2: The UE sends a NAS message to the current satellite: a Registration Request message, with the registration type "mobility registration update". This Registration Request message is carried in the RRC: RRCSetupComplete or ULInformationTransfer message. The Registration Request message may contain updated eDRX / MICO parameters, such as the eDRX PTW and T. eDRX,H And MICO's T3324 and T3512. The length of PTW or T3324 can be configured to the coverage time of the current satellite, while T...eDRX,H The length of T3512 can be configured as the coverage time plus the non-coverage time. The non-coverage time can be configured as the service start time of the next satellite minus the service stop time of the current satellite.

[0209] Note 1: The NAS Registration Request message may include the coverage period length, the non-coverage period length (e.g., the next satellite service start time minus the current satellite service stop time), the current satellite service stop time, and / or the next satellite service start time. This information is used by the AMF to determine the eDRX's PTW and T. eDRX,H The values, as well as the values ​​of MICO's T3324 and T3512.

[0210] Note 1.1: For mobile cells, the NAS Registration Request message may contain the UE's location information so that the AMF can use it to determine the eDRX / MICO parameters.

[0211] Note 2: The Registration Request message may contain multiple parameters configured in the eDRX / MICO.

[0212] Step 3: The satellite forwards the Registration Request message to the gNB.

[0213] Note 1: This step can be omitted if the satellite is a regenerative satellite (i.e., the gNB is implemented on the satellite). If the satellite is a transparent satellite (i.e., the gNB is implemented on the ground and connects to the UE via the satellite), the satellite only forwards the Registration Request message to the gNB through the feeder link.

[0214] Step 4: The gNB forwards the Registration Request message to the AMF. The Registration Request message is carried in the NGAP: Initial UE message.

[0215] Step 5: The AMF replies to the gNB with a Registration Accept message. The Registration Accept message is carried within the NGAP: Initial Context Setup Request message. If the AMF accepts the UE's eDRX / MICO request, the Registration Accept message includes the eDRX / MICO parameters (e.g., eDRX PTW and T). eDRX,H(and T3324 and T3512 in MICO mode). The value of the eDRX / MICO parameter in the Registration Accept message may be the same as the value requested by the UE in the Registration Request, or it may be a value updated by the AMF that is different from the eDRX / MICO parameter in the Registration Request.

[0216] Note 1: If the AMF has set a validity countdown timer for the eDRX / MICO configuration, the AMF can update the countdown timer in the RegistrationAccept message.

[0217] Step 6: The gNB forwards the Registration Accept message to the satellite. The Registration Accept message can be carried in the RRC: RRCReconfiguration or DLInformationTransfer message.

[0218] Note 1: If the satellite is a regenerative satellite (i.e., gNB is implemented on the satellite), this step can be omitted.

[0219] Note 2: If the validity countdown timer for the eDRX / MICO configuration is configured by gNB, gNB can update the countdown timer in the RRC: RRCReconfiguration message.

[0220] Step 7: The satellite forwards the Registration Accept message to the UE. The Registration Accept message can be carried in the RRC: RRCReconfiguration or DLInformationTransfer message. After receiving the Registration Accept message, the UE updates the eDRX / MICO configuration of the default radio bearer.

[0221] Note 1: If the UE requests multiple eDRX / MICO configurations in step 2, the Registration Accept message may contain parameters for multiple eDRX / MICO configurations.

[0222] Note 2: The UE activates the countdown timer when it receives the (updated) countdown timer for the validity of the eDRX / MICO configuration.

[0223] Step 8: After the data transmission is completed, the gNB can send an NGAP: UE CONTEXT RELEASE REQUEST message with the cause value "User Inactivity" to the AMF to initiate the release of the UE radio bearer.

[0224] Note 1: This step is optional. It can be omitted when the AMF actively releases the UE.

[0225] Note 2: gNB should send the NGAP:UE CONTEXT RELEASEREQUEST message before the current satellite service stop time.

[0226] Note 3: NGAP: The UE CONTEXT RELEASE REQUEST message may contain the service outage time of the current satellite where the UE is located.

[0227] Note 4: The cause value can be a new cause (e.g., "Discontinuous Coverage"), rather than one of the existing causes.

[0228] Step 9: The AMF sends an NGAP: UE CONTEXT RELEASE COMMAND message to the gNB to release the UE.

[0229] Note 1: If the AMF knows the service stop time of the current satellite and the service start time of the next satellite, the AMF can send an NGAP: UE CONTEXT RELEASE COMMAND message to the UE through the gNB.

[0230] Step 10: gNB sends an RRC Release message to the satellite to release the UE.

[0231] Note 1: The RRCRelease message may contain a ReleaseCause, such as "Discontinuous Coverage".

[0232] Step 11: The satellite forwards the RRCRelease message to the UE.

[0233] Step 12: After receiving the RRC Release message, the UE enters the RRC Idle state and activates the eDRX / MICO operation based on the updated eDRX / MICO configuration.

[0234] Note 1: According to the updated eDRX / MICO cycle, the UE can skip monitoring paging during non-coverage intervals.

[0235] eNB / MME update eDRX / PSM configuration: Figure 14A The process of updating the eDRX / PSM configuration by a release procedure initiated by the eNB / MME is illustrated according to some embodiments of the present disclosure. Figure 14A This document explains that in some embodiments, modifications to the eDRX / PSM configuration are controlled by the eNB / MME. For quasi-fixed Earth cells, the eNB knows the service outage time of the satellite where the UE is located, therefore the eNB can request the MME to release the UE before the UE enters discontinuous coverage. Therefore, this embodiment is more suitable for UEs covered by quasi-fixed Earth cells. Furthermore, the process of updating the eDRX / MICO configuration by initiating a release procedure by the gNB / AMF can be... Figure 14B The process described in the document includes at least one of the following steps: The eDRX / PSM update procedure initiated by the eNB / MME.

[0236] Step 0: The UE receives broadcast system information from the eNB. In this case, the system information may not include the service stop time of the serving satellite and the service start time of the next satellite, because the eNB / MME controls and initiates the configuration of eDRX / PSM.

[0237] Note 1: System information may include the physical cell identifier, satellite identifier, or satellite ephemeris information of the serving satellite and the next satellite.

[0238] Step 1: The UE completes the random access procedure.

[0239] Step 2: The UE performs data transmission with the eNB.

[0240] Step 3: After the data transmission is completed, the eNB can send an S1AP: UE CONTEXT RELEASE REQUEST message with the cause value "UserInactivity" to the MME to initiate the release of the UE radio bearer.

[0241] Note 1: This step is optional and can be omitted if the release of the UE is initiated by the MME.

[0242] Note 2: The eNB should send the S1AP:UE CONTEXTRELEASE REQUEST message before the service stop time of the satellite serving the UE.

[0243] Note 3: S1AP: The UE CONTEXT RELEASE REQUEST message may include the service stop time of the satellite serving the UE and the service start time of the next satellite. This message may also include the UE's location information, cell identifier, satellite identifier, or satellite ephemeris information.

[0244] Note 3.1: If the eNB obtains the location and / or speed information of the UE at a certain reference time point through the UE's location information report, then the S1AP: UE CONTEXT RELEASE REQUEST message can include the UE's location and / or speed information at the reference time so that the MME can use it to determine the eDRX / PSM parameters.

[0245] Note 4: The cause value can be a new cause (e.g., "Discontinuous Coverage"), rather than any existing cause.

[0246] Step 4: The MME sends an S1AP: UE CONTEXT RELEASE COMMAND message to the eNB to release the UE. If the MME determines that the eDRX / PSM configuration needs to be updated based on the UE's location, cell identifier, satellite identifier, satellite ephemeris information, the service stop time of the UE's serving satellite, and / or the service start time of the next satellite, it can send the updated eDRX / PSM parameters, such as the eDRX PTW and T, in the UE CONTEXT RELEASE COMMAND message. eDRX,H , as well as PSM's T3324 and T3412.

[0247] Note 1: If the MME has the service stop time of the serving satellite and the service start time of the next satellite, it can send the S1AP: UE CONTEXT RELEASE COMMAND message to the UE through the eNB.

[0248] Note 2: S1AP: The UE CONTEXT RELEASE COMMAND message can contain multiple parameters of the eDRX / PSM configuration.

[0249] Note 3: The eDRX parameters carried in the UE CONTEXT RELEASE COMMAND message can be offsets of previously configured eDRX parameters. For example, with Figure 15Here's an example of configuring an offset for eDRX. The offset can be an offset of the supersystem frame number (H-SFN) (e.g., offsetH-SFN), which has a length of 10.24 seconds when H-SFN is incremented by 1; the offset can also be an offset of the system frame number (SFN) (e.g., offsetSFN), which has a length of 10 milliseconds when SFN is incremented by 1; or the offset can be an offset expressed in paging cycles.

[0250] Note 4: The PSM parameters carried in the UE CONTEXT RELEASE COMMAND message can be offsets of previously configured PSM parameters. For example, with Figure 16 Example of configuring an offset for PSM. The offset can be the offset of timer T3324 or T3412 (e.g., offset). T3324 or offset T3412 ).

[0251] Note 5: If the MME is configured with a countdown timer for verifying the eDRX / PSM configuration, the MME can update the countdown timer in the UECONTEXT RELEASE COMMAND message.

[0252] Step 5: The eNB sends an RRCConnectionRelease message to the satellite to release the UE.

[0253] Note 1: This offset value can be a parameter of the Access Stratum (AS) layer, but not a parameter of the NAS layer (i.e., not carried by NAS messages).

[0254] Note 2: The RRCConnectionRelease message may contain ReleaseCause (e.g., discontinuous coverage).

[0255] Note 3: If the eNB is configured with a countdown timer for verifying the eDRX / PSM configuration, the eNB can update the countdown timer in the RRC:RRCConnectionReconfiguration message.

[0256] Step 6: The satellite forwards the RRCConnectionRelease message to the UE.

[0257] Step 7: After receiving the RRCConnectionRelease message, the UE enters the RRC Idle state and starts the eDRX / PSM operation.

[0258] Note 1: When the offset value is an AS layer parameter, the UE may not update the eDRX / PSM configuration. The UE can start a timer based on the received offset value. Before the timer expires, the UE can skip listening to paging.

[0259] Note 2: If the RRCConnectionRelease message contains an offset value for PSM configuration (i.e., the offset value carried by the NAS message), then timers T3324 and T3412 will be based on... Figure 16 Update.

[0260] Note 3: If the RRCConnectionRelease message contains an offset value for eDRX configuration (i.e., the offset value carried by the NAS message), the UE can listen for paging based on this offset value. The paging frame update method is as follows:

[0261] Note 3.1: The offset value in the RRCConnectionRelease message can be the updated UE identifier. This updated UE identifier can be the International Mobile Subscriber Identity (IMSI) modified when the UE registers with the EPC (i.e., the original IMSI and / or IMSI offset), or the 5G Globally Unique Temporary Identifier (5G-GUTI) modified when the UE registers with the 5GC. This modified IMSI or 5G-GUTI may result in changes to the Paging Hyperframe (PH), PTW_start, and / or PTW_end. PH, PTW_start, and PTW_end are given by the following formula: Paging superframe (PH) is an H-SFN that satisfies the following equation: H-SFN new mod T eDRX,H = UE_ID_H new modT eDRX,H .

[0262] UE_ID_H new : The highest 10 or 12 bits of the Hashed ID used to identify the updated UE.

[0263] T eDRX,H : UE's eDRX superframe period (in units of Hyper-frame).

[0264] PTW_start represents the first radio frame in a paging superframe (PH) belonging to PTW, whose SFN satisfies the following equation: SFN new = 256 * i eDRX_new, Among them, i eDRX_new = floor(UE_ID_H new / T eDRX,H ) mod 4.

[0265] PTW_end represents the last radio frame of PTW, and its SFN satisfies the following equation: FN = (PTW_start +L*100 - 1) mod 1024, where L is the PTW length (in seconds) configured by the upper layer.

[0266] Note: UE_ID_H new It must be configured to ensure that the SFN of PTW_end falls within the “coverage range”.

[0267] Note 3.2: In order to modify T eDRX,H_H The offset value in the RRCConnectionRelease message can be the UE's eDRX superframe period, updated based on the service start time of the next satellite. PH, PTW_start, and PTW_end can be determined by the following formula: The paging superframe (PH) is an H-SFN that satisfies the following equation: H-SFN new mod T eDRX,H_new = UE_ID_H modT eDRX,H_new .

[0268] UE_ID_H: The highest 10 or 12 bits of the Hashed ID.

[0269] T eDRX,H_new : The modified eDRX cycle of the UE in the hyper-frame unit.

[0270] PTW_start represents the first radio frame in a paging superframe (PH) belonging to PTW, whose SFN satisfies the following equation: SFN new = 256 * i eDRX_new , where i eDRX_new = floor(UE_ID_H / T eDRX,H_new ) mod 4.

[0271] PTW_end represents the last radio frame of PTW, and its SFN satisfies the following equation: SFN = (PTW_start +L*100 - 1) mod 1024, where L is the PTW duration (in seconds) configured by the upper layer.

[0272] Note: UE_ID_H must be configured to ensure that the SFN of PTW_end falls within the "coverage range".

[0273] Note 3.3: In this embodiment, by adjusting the SFN of PTW_end to within the "coverage interval," the UE is prevented from listening to paging messages during "discontinuous coverage." PH, PTW_start, and PTW_end can be determined by the following formula: The paging superframe (PH) is the H-SFN that satisfies the following equation: H-SFN mod T eDRX,H = UE_ID_H mod T eDRX,H .

[0274] UE_ID_H: The highest 10 or 12 bits of the Hashed ID.

[0275] T eDRX,H : eDRX cycle of UE in hyper-frame unit.

[0276] PTW_start represents the first radio frame in a paging superframe (PH) belonging to PTW, whose SFN satisfies the following equation: SFN = 256 * i eDRX , where i eDRX = floor(UE_ID_H / T eDRX,H ) mod 4.

[0277] PTW_end represents the last radio frame of PTW, whose SFN satisfies the following equation: SFN = (PTW_start +L*100 - 1) mode n, where n is the last radio frame in the "coverage area", and L is the PTW duration (in seconds) configured by the upper layer.

[0278] Note 4: When the UE receives the (updated) countdown timer used to verify the eDRX / PSM configuration, the UE activates the countdown timer.

[0279] Update eDRX / MICO configuration via gNB / AMF: Figure 14B The illustration demonstrates, for illustrative purposes, the process of updating the eDRX / MICO configuration via a release procedure initiated by gNB / AMF according to an embodiment of the present invention. In this embodiment, the modification of the eDRX / MICO configuration is controlled by gNB / AMF. The eDRX / MICO update procedure initiated by gNB / AMF includes at least one of the following steps.

[0280] Step 0: The UE receives broadcast system information from the gNB. Since the configuration of eDRX / MICO is controlled and initiated by the gNB / AMF, the system information may not include the service stop time of the current satellite and the service start time of the next satellite.

[0281] Note 1: System information may include the physical cell identity of the current satellite and the next satellite.

[0282] Step 1: The UE completes the random access procedure.

[0283] Step 2: Data transmission and reception between the UE and gNB.

[0284] Step 3: After data transmission is completed, the gNB can send an NGAP: N2 UE CONTEXT RELEASEREQUEST message to the AMF, carrying the reason value "Discontinuous Coverage", to initiate the release procedure of the UE radio bearer.

[0285] Note 1: This step is optional; if the release of the UE is initiated by the AMF, this step can be omitted.

[0286] Note 2: gNB should send the NGAP:N2 UE CONTEXTRELEASE REQUEST message to AMF before the current satellite service stop time.

[0287] Note 3: NGAP: The UE CONTEXT RELEASE REQUEST message can contain the service stop time of the current satellite where the UE is located and the service start time of the next satellite.

[0288] Note 3.1: If the gNB obtains the UE's location and / or speed information at a certain reference time through the location-related information reported by the UE, then the NGAP: UE CONTEXT RELEASE REQUEST message may contain the UE's location and / or speed information at the reference time for the AMF to use in determining the eDRX / MICO parameters.

[0289] Step 4: The AMF sends an NGAP: N2 UE CONTEXT RELEASE COMMAND message to the gNB to release the UE. If the AMF determines that the eDRX / MICO configuration needs to be updated based on the UE's location, the service stop time of the current satellite where the UE is located, and / or the service start time of the next satellite, the updated eDRX / MICO parameters, such as the eDRX PTW and T, can be included in the N2 UE CONTEXT RELEASE COMMAND message. eDRX,H, as well as MICO's T3324 and T3512.

[0290] Note 1: If the AMF obtains the service stop time of the current satellite and the service start time of the next satellite, it can actively trigger the NGAP: UE CONTEXT RELEASE COMMAND message to the UE through the gNB.

[0291] Note 2: NGAP: The N2 UE CONTEXT RELEASE COMMAND message can contain multiple eDRX / MICO configuration parameters.

[0292] Step 5: The gNB sends an RRRCRelease message to the satellite to release the UE.

[0293] Note 1: The RRCRelease message may contain ReleaseCause (e.g., "discontinuous coverage").

[0294] Step 6: The satellite forwards the RRCRelease message to the UE.

[0295] Step 7: After receiving the RRC Release message, the UE enters the RRC Idle state and initiates the eDRX / MICO operation.

[0296] When the UE is in RRC Idle / Inactive state, the eDRX / PSM configuration is updated by the eNB / MME: Figure 17A The process of updating the eDRX / PSM configuration via paging the UE is demonstrated. In this embodiment, the modification of the eDRX / PSM configuration is controlled by the eNB / MME in the E-UTRAN.

[0297] The process of updating the eDRX / PSM configuration by paging the UE includes at least one of the following steps.

[0298] Step 0: When the eNB determines that the eDRX / PSM period needs to be modified to match the arrival time of the next satellite, the eNB sends an S1AP: ENB CONFIGURATION UPDATE message to the MME. The information that the ENB CONFIGURATION UPDATE message can carry includes: the service stop time of the current satellite, the service start time of the next satellite, and a reason value (e.g., "discontinuous coverage").

[0299] Note 1: The MME can respond by sending the S1AP: ENB CONFIGURATION UPDATE ACKNOWLEDGE message.

[0300] Note 2: If the MME knows the arrival time of the (next) satellite, this step can be omitted.

[0301] Step 1: If the MME confirms that an eDRX / PSM modification is required, the MME sends an S1AP: PAGING message to the eNB. This PAGING message may include the updated paging eDRX cycle, PTW, T3324 timer, and / or T3412 timer.

[0302] Step 2: The eNB uses the original eDRX / PSM configuration to page the UE. RRC: The paging message can carry the paging reason: Discontinuous Coverage.

[0303] Step 3: The satellite forwards the paging message to the UE.

[0304] Step 4: After being paged, the UE initiates a random access procedure to update the eDRX / PSM configuration.

[0305] Step 5: The UE sends a NAS message to the serving satellite: an ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message. This ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message is carried within an RRC: RRCConnectionSetupComplete or ULInformationTransfer message. This ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message may include eDRX / PSM parameters, such as the eDRX's PTW and T. eDRX,H And PSM's T3324 and T3412. The length of PTW or T3324 can be configured as the in-coverage interval of the serving satellite, while T... eDRX,H The length of T3412 can be configured as the coverage interval plus the out-of-coverage interval. The out-of-coverage interval can be configured as the service start time of the next satellite minus the service stop time of the currently serving satellite.

[0306] Note 1: NAS messages: ATTACH REQUEST or TRACKING AREA UPDATE REQUEST messages may include the service stop time of the serving satellite and the service start time of the next satellite. This message may also include the UE location, cell identifier, satellite identifier, or satellite ephemeris information, used by the MME to determine the eDRX PTW and T. eDRX,HAnd the values ​​of T3324 and T3412 of PSM.

[0307] Note 1.1: NAS messages: ATTACH REQUEST or TRACKING AREA UPDATE REQUEST messages may include the UE's position and / or velocity information at a reference time, which the MME can use to determine eDRX / PSM parameters. This position and velocity information can be obtained from the Global Navigation Satellite System (GNSS).

[0308] Note 2: The ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message may include multiple parameters of the eDRX / PSM configuration.

[0309] Step 6: The satellite forwards the ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message to the eNB.

[0310] Note 1: If the satellite is a regenerative satellite (i.e., the eNB is implemented on the satellite), this step can be omitted. If the satellite is a transparent satellite (i.e., the eNB is implemented on the ground and connects to the UE via the satellite), the satellite only forwards the ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message to the eNB via the feeder link.

[0311] Step 7: The eNB forwards the ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message to the MME. This ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message is carried in the S1AP: Initial UE message.

[0312] Step 8: The MME replies to the eNB with an ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT message. This ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT message is carried in the S1AP: Initial ContextSetup Request message. If the MME accepts an eDRX / PSM request from the UE, this ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT message contains the eDRX / PSM parameters (i.e., the PTW and T of the eDRX). eDRX,H(and PSM's T3324 and T3412).

[0313] Note 1: If the MME sets a countdown timer for eDRX / PSM configuration verification, the MME can transmit the (updated) countdown timer in the ATTACHACCEPT or TRACKING AREA UPDATE ACCEPT message.

[0314] Step 9: The eNB forwards the ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT message to the satellite. This ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT message is carried in the RRC: RRCConnectionReconfiguration or DLInformationTransfer message.

[0315] Note 1: If the satellite is a regenerative satellite (i.e., the eNB is implemented on the satellite), this step can be omitted.

[0316] Note 2: If the eNB has set a countdown timer for eDRX / PSM configuration verification, the eNB can transmit the (updated) countdown timer in the RRC:RRCConnectionReconfiguration message.

[0317] Step 10: The satellite forwards the ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT message to the UE. This ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT message is carried in the RRC: RRCConnectionReconfiguration or DLInformationTransfer message. After receiving the ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT message, the UE establishes the eDRX / PSM configuration for the default radiobearer.

[0318] Note 1: If the UE requests multiple eDRX / PSM configurations in step 2, the ATTACH ACCEPT or TRACKINGAREA UPDATE ACCEPT message may contain parameters for multiple eDRX / PSM configurations.

[0319] Step 11: After receiving the ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT message, the UE updates the eDRX / PSM configuration.

[0320] Note 1: When the UE receives the (updated) countdown timer for eDRX / PSM configuration verification, the UE will start the countdown timer.

[0321] Step 12: The MME replies to the eNB using the S1AP: ENB CONFIGURATION UPDATE ACKNOWLEDGE message.

[0322] Step 13: After receiving the ENB CONFIGURATION UPDATE ACKNOWLEDGE message, the eNB updates the eDRX / PSM configuration.

[0323] Note 1: The order of steps 12 and 13 is independent of steps 10 and 11. In other words, steps 12 and 13 can occur before or after steps 10 and 11.

[0324] When the UE is in RRC Idle / Inactive state, the eDRX / MICO configuration is updated by gNB / AMF: Figure 17B This illustrates a procedure for updating the eDRX / MICO configuration via paging a UE, according to an embodiment of the present invention. In this embodiment, the modification of the eDRX / MICO configuration is controlled by the gNB / AMF (applicable to 5G NR networks). Figure 17B In some embodiments, the process of updating the eDRX / MICO configuration by paging the UE may include at least one of the following steps.

[0325] Step 0: When the gNB determines that the eDRX / MICO period needs to be modified to match the arrival time of the next satellite, the gNB sends an NGAP: RAN CONFIGURATION UPDATE message to the AMF. This RAN CONFIGURATION UPDATE message may carry information including the current satellite's service stop time, the next satellite's service start time, and a reason value such as "Discontinuous Coverage".

[0326] Note 1: AMF can reply using the NGAP: RAN CONFIGURATION UPDATE ACKNOWLEDGE message.

[0327] Note 2: If the AMF knows the arrival time of the (next) satellite, this step can be omitted.

[0328] Step 1: If the AMF confirms that the eDRX / MICO needs to be modified, the AMF sends an NGAP: PAGING message to the gNB. This PAGING message may include parameters such as the updated paging eDRX cycle, PTW, T3324 timer, and / or T3512 timer.

[0329] Step 2: The gNB uses the original eDRX / MICO configuration to page the UE. The RRC: paging message can carry a paging reason, such as "Discontinuous Coverage".

[0330] Step 3: The satellite forwards the paging message to the UE.

[0331] Step 4: After the UE is paged, a random access procedure is initiated to update the eDRX / MICO configuration.

[0332] Step 5: The UE sends a NAS message to the current satellite: a Registration Request message. This Registration Request message is carried in the RRC: RRCSetupComplete or ULInformationTransfer message. The Registration Request message may include eDRX / MICO parameters, such as the eDRX's PTW and T. eDRX,H And T3324 and T3512 in MICO mode. The length of PTW or T3324 can be configured to the in-coverage interval of the current satellite, while T... eDRX,H The length of T3512 can be configured to add an out-of-coverage interval to the coverage duration. The out-of-coverage interval can be configured as the service start time of the next satellite minus the service stop time of the current satellite.

[0333] Note 1: NAS Messages: Registration Request messages may include coverage duration, non-coverage duration (e.g., the service start time of the next satellite minus the service stop time of the current satellite), the service stop time of the current satellite, and / or the service start time of the next satellite. This information is used by the AMF to determine the PTW and T of the eDRX. eDRX,H And the T3324 and T3512 in MICO mode.

[0334] Note 1.1: NAS Message: The Registration Request message may include the UE's position and / or velocity information at a reference time so that the AMF can determine the eDRX / MICO parameters. The position and velocity information can be obtained from the Global Navigation Satellite System (GNSS).

[0335] Note 2: The Registration Request message may include multiple parameters configured in the eDRX / MICO.

[0336] Step 6: The satellite forwards the Registration Request message to the gNB.

[0337] Note 1: This step can be omitted if the satellite is a regenerative satellite (i.e., the gNB is deployed on a satellite). If the satellite is a transparent satellite (i.e., the gNB is deployed on the ground and connects to the UE via the satellite), the satellite only forwards the Registration Request message to the gNB via the feeder link.

[0338] Step 7: The gNB forwards the Registration Request message to the AMF. The Registration Request message is carried in the NGAP: Initial UE message.

[0339] Step 8: The AMF replies to the gNB with a Registration Accept message. The Registration Accept message is carried within the NGAP: Initial Context Setup Request message. If the AMF accepts the UE's eDRX / MICO request, the Registration Accept message includes the eDRX / MICO parameters (i.e., the eDRX's PTW and T). eDRX,H (and T3324 and T3512 in MICO mode).

[0340] Note 1: If the AMF has a countdown timer configured to verify the eDRX / MICO configuration, the AMF can send the (updated) countdown timer in the Registration Accept message.

[0341] Step 9: The gNB forwards the Registration Accept message to the satellite. The Registration Accept message is carried in the RRC: RRCReconfiguration or DLInformationTransfer message.

[0342] Note 1: If the satellite is a regenerative satellite (i.e., the gNB is deployed on the satellite), this step can be omitted.

[0343] Note 2: If the gNB is configured with a countdown timer for verifying the eDRX / MICO configuration, the gNB can send the (updated) countdown timer in the RRC:RRCReconfiguration message.

[0344] Step 10: The satellite forwards the Registration Accept message to the UE. The Registration Accept message is carried in the RRC: RRCReconfiguration or DLInformationTransfer message. After receiving the Registration Accept message, the UE sets the eDRX / MICO configuration for the default radio bearer.

[0345] Note 1: If the UE requests multiple eDRX / MICO configurations in step 2, the Registration Accept message may contain parameters for multiple eDRX / MICO configurations.

[0346] Step 11: After receiving the Registration Accept message, the UE updates the eDRX / MICO configuration.

[0347] Note 1: The UE starts the countdown timer when it receives the (updated) countdown timer used to verify the eDRX / MICO configuration.

[0348] Step 12: The AMF replies to the gNB with the NGAP: RAN CONFIGURATION UPDATE ACKNOWLEDGE message.

[0349] Step 13: After receiving the RAN CONFIGURATION UPDATE ACKNOWLEDGE message, the gNB updates the eDRX / MICO configuration.

[0350] Note 1: The order of steps 12 and 13 is independent of steps 10 and 11. In other words, steps 12 and 13 can occur before or after steps 10 and 11.

[0351] Update eDRX / PSM configuration via RAN-based indication from the UE: Figure 17C This illustrates the process of updating the eDRX / PSM configuration via a release procedure initiated by the eNB / MME. In this embodiment, the release procedure initiated by the eNB / MME is triggered by an instruction from the UE based on the Radio Access Network (RAN). In a 5G NR network, the base station is the gNB, and the control entity responsible for eDRX / MICO configuration is the AMF. For moving cells, the eNB / gNB may not be able to accurately know the current service outage time of the UE's satellites. The eNB / gNB may require assistance information from the UE to request the MME / AMF to release the UE before it enters discontinuous coverage. Therefore, this embodiment is more useful for UEs located within moving cell coverage.

[0352] Figure 17C In some embodiments, the eDRX / PSM / MICO update process triggered by the RAN based on an indication issued by the UE includes at least one of the following steps: Step 0: The UE receives broadcast system information from the eNB / gNB. For quasi-earth-fixed cells, the system information may include the service stop time of the current satellite and the service start time of the next satellite. For mobile cells, the system information may include ephemeris data, a reference location (e.g., cell center), and / or cell coverage area size (e.g., cell radius). The system information may also include the physical cell identifiers of the current and next satellites. The system information may also indicate that the cell has the capability to support discontinuous coverage.

[0353] Step 1: The UE completes the random access procedure.

[0354] Step 2: The UE performs data transmission and reception with the eNB / gNB.

[0355] Step 3: After data transmission is complete, the UE can send a RAN-based indication to the eNB / gNB. This RAN-based indication may include: the UE's preferred RRC state (e.g., RRC_IDLE or RRC_INACTIVE), the estimated service stop time for the current satellite, the estimated service start time for the next satellite, notification of impending discontinuous coverage, and / or a request to release the RRC_Connected state. The RAN-based indication can be Uplink Control Information (UCI) to notify of impending discontinuous coverage. It can also be a MAC control element (CE) (e.g., Access Layer Release Auxiliary Indication AS RAI) to request the release of the RRC connection due to impending discontinuous coverage. If an AS RAI MAC CE is used, the codepoint and / or index setting in the AS RAI MAC CE can be set to 11 to indicate discontinuous coverage. If a new MAC CE is used, it can carry the estimated service stop time for the current satellite and the estimated service start time for the next satellite. RAN-based indications can also be RRC messages (e.g., UE Assistance Information), carrying the UE's preferred RRC state, the estimated service stop time for the current satellite, the estimated service start time for the next satellite, and / or a request to release the RRC_Connected state. RRC messages may also contain the UE's position and / or velocity information at a reference time, so that the eNB / gNB can determine the time to release the UE. Position and velocity information can be obtained by the UE from the Global Navigation Satellite System (GNSS).

[0356] Step 4: Upon receiving the RAN-based instruction, the eNB can send an S1AP: UE CONTEXT RELEASE REQUEST message to the MME, carrying the cause value "Discontinuous Coverage," to initiate the release of the UE's radio bearer. This S1AP: UE CONTEXT RELEASE REQUEST message may include the service stop time of the UE's current satellite and the service start time of the next satellite. The message may also include the UE's location and / or velocity information at the reference time, allowing the MME to determine the eDRX / PSM cycle. Location and velocity information can be obtained from GNSS.

[0357] Note 1: For 5G NR networks, gNB can send an NGAP: N2 UE CONTEXT RELEASE REQUEST message to AMF carrying the cause value "Discontinuous Coverage" to initiate the release of the UE's radio bearer.

[0358] Note 2: This step is optional and can be omitted when the MME / AMF actively initiates the release of the UE.

[0359] Note 3: The eNB / gNB should send the UE CONTEXT RELEASEREQUEST message before the service stop time of the UE's current satellite.

[0360] Step 5: The MME sends an S1AP: UE CONTEXT RELEASE COMMAND message to the eNB to release the UE. In the 5G NR network, the AMF sends an NGAP: N2 UE CONTEXT RELEASE COMMAND message to the gNB to release the UE. If the MME / AMF determines that eDRX / PSM / MICO needs to be updated based on the UE's location, the current satellite's service stop time, and / or the next satellite's service start time, the updated eDRX / PSM / MICO parameters can be sent in the UE CONTEXT RELEASE COMMAND / N2 UE CONTEXT RELEASECOMMAND message, for example: for eDRX: PTW and T eDRX,H For PSM: T3324 and T3412; for MICO mode: T3324 and T3512.

[0361] Step 6: The eNB sends an RRCConnectionRelease message to the UE via satellite to release the UE. This RRCConnectionRelease message may contain updated eDRX / PSM parameters and a ReleaseCause (e.g., Discontinuous Coverage).

[0362] Note 1: In a 5G NR network, the gNB sends an RRCRelease message to the UE via satellite to release the UE. This RRCRelease message may contain updated eDRX / MICO parameters and a ReleaseCause (e.g., Discontinuous Coverage).

[0363] Note 2: The RRCConnectionRelease / RRCRelease message may contain a CG configuration with a delayed activation time, which is used to re-establish the RRC connection via the next satellite.

[0364] Step 7: The satellite forwards the RRCConnectionRelease / RRCRelease message to the UE.

[0365] Step 8: After receiving the RRCConnectionRelease / RRCRelease message, the UE enters the RRC Idle / RRCInactive state and activates eDRX / PSM / MICO operations.

[0366] Update the eDRX / PSM configuration via instructions from the NAS layer of the UE: Figure 17D This document demonstrates the process of updating eDRX / PSM configuration via a release procedure initiated by the MME. In this embodiment, the MME-initiated release procedure is triggered by a NAS-based indication from the UE. In a 5G NR network, the base station is a gNB, and the control entity responsible for eDRX / MICO configuration is the AMF. For mobile cells, the MME / AMF may not be able to accurately determine the service outage time of the satellite currently located to the UE, thus requiring auxiliary information from the UE to release the UE before it enters discontinuous coverage. Therefore, this embodiment is more applicable to UEs located within the coverage of a mobile cell.

[0367] like Figure 17D As shown, in some embodiments, the eDRX / PSM / MICO update process triggered by the NAS layer of the UE includes at least one of the following steps.

[0368] Step 0: The UE receives broadcast system information from the eNB / gNB. For quasi-earth-fixed cells, the system information may include: the service stop time of the current satellite and the service start time of the next satellite. For moving cells, the system information may include: ephemeris information, cell reference location (e.g., cell center), and cell coverage area size (e.g., cell radius). The system information may also include the physical cell identifier or satellite identifier of the current and next satellites. The system information may also indicate that the network has the capability to "support discontinuous coverage".

[0369] Step 1: The UE completes the random access procedure.

[0370] Step 2: Data transmission and reception between the UE and the eNB / gNB.

[0371] Step 3: After data transmission is complete, the UE can send a NAS-based indication to the MME / AMF. This NAS-based indication may include: the estimated service stop time for the current satellite, the estimated service start time for the next satellite, a notification of impending discontinuous coverage, and / or a request to release the RRC connection. The NAS-based indication may contain a NAS Information Element (NAS IE): "Release Assistance Indication (RAI)," where the downlink data expectation (DDX) bit = 11, indicating impending discontinuous coverage. The NAS-based indication can be carried in NAS messages, such as a TRACKING AREA UPDATE REQUEST or a Registration Request message. TRACKING AREA UPDATE REQUEST / Registration Request messages may also include the UE's position and / or velocity information at a reference time, allowing the MME to determine the timing of the UE's release. The position and velocity information can be obtained by the UE through the Global Navigation Satellite System (GNSS).

[0372] Step 4: Upon receiving the NAS layer instruction, the MME sends an S1AP: UE CONTEXT RELEASE COMMAND message to the eNB to release the UE. In a 5G NR network, the AMF sends an N2 UE CONTEXT RELEASE COMMAND message to the gNB to release the UE. If the MME / AMF determines that the eDRX / PSM / MICO configuration needs to be updated based on the following information: the UE's location, the current satellite's service stop time, and the next satellite's service start time, then the updated eDRX / PSM / MICO parameters can be sent in the UE CONTEXT RELEASE COMMAND / N2 UECONTEXT RELEASE COMMAND message, including: eDRX: PTW, T... eDRX,H PSM: T3324, T3412. MICO mode: T3324, T3512.

[0373] Step 5: The eNB sends an RRCConnectionRelease message to the UE via satellite to release the UE. This RRCConnectionRelease message may include updated eDRX / PSM parameters and a release cause (e.g., discontinuous coverage).

[0374] Note 1: In a 5G NR network, the gNB will send an RRCRelease message to the UE via satellite to release the UE. The RRCRelease message may include the updated eDRX / PSM parameters and the reason for release (e.g., DiscontinuousCoverage).

[0375] Note 2: The RRCConnectionRelease / RRCRelease message may contain a CG configuration with a delayed activation time, which is used to re-establish the RRC connection via the next satellite.

[0376] Step 6: The satellite forwards the RRCConnectionRelease / RRCRelease message to the UE.

[0377] Step 7: After receiving the RRCConnectionRelease / RRCRelease message, the UE enters the RRC Idle state and starts the eDRX / PSM operation.

[0378] Figure 18A wireless communication block diagram of a UE 1800 according to an embodiment of the present invention is shown. In some embodiments, the UE 1800 includes an actuator 1801 configured to execute a power-saving mechanism when the UE 1800 is in a discontinuous coverage scenario. This discontinuous coverage scenario includes alternating periods of coverage (in-coverage) and out-of-coverage. In this power-saving mechanism: the UE 1800 remains in a dormant state or a mobile-side initiated connection-only (MICO) mode during the out-of-coverage period of the discontinuous coverage scenario; the UE 1800 is configured to wake up during the coverage period of the discontinuous coverage scenario to monitor paging. The out-of-coverage interval is configured based on the service stop time of the serving satellite and / or the service start time of the next satellite; the service stop time of the serving satellite and / or the service start time of the next satellite can be determined based on information from the satellites. "Dormant state" can refer to a state in which the UE has no data to transmit during the out-of-coverage period of the discontinuous coverage scenario. This technology addresses the problems in existing technologies and can be used to: provide non-terrestrial communication (NTN) for the Internet of Things (IoT), provide energy savings for IoT NTN in discontinuous coverage scenarios, provide good communication performance, and / or provide high reliability. The UE can remain in sleep mode during periods of no coverage and wake up during periods of coverage to monitor paging.

[0379] In some embodiments, the UE executes a power-saving mechanism after receiving a release reason from a base station or control entity via the serving satellite. In some embodiments, the release reason is sent to the UE's Radio Resource Control (RRC) layer to control the operation of the power-saving mechanism. In some embodiments, the release reason refers to a discontinuous coverage release reason. In some embodiments, the release reason is sent to the UE by the control entity via the serving satellite in response to a request from the UE or a base station. In some embodiments, the control entity is the Access and Mobility Management Function (AMF). In some embodiments, the UE reducing the serving cell measurement latency includes: the UE reducing or prematurely stopping a first timer based on information from the serving satellite to reduce the serving cell recovery time. In some embodiments, if the serving cell is a quasi-earth fixed cell, the information from the satellite includes: the serving satellite's service stop time, departure indication, the service start time of the next satellite, the serving satellite's physical cell identifier, satellite identifier, satellite ephemeris or frequency band, and / or the next satellite's physical cell identifier, satellite identifier, satellite ephemeris or frequency band.

[0380] In some embodiments, if the serving cell is a mobile cell, the information from the satellite includes: the reference location, elevation angle, maximum distance, cell coverage area size, physical cell identifier, satellite identifier, satellite ephemeris or frequency band of the serving satellite, and / or the physical cell identifier, satellite identifier, satellite ephemeris or frequency band of the next satellite. In some embodiments, the information from the serving satellite is sent to the UE by the base station via a broadcast message or a unicast message. In some embodiments, the information from the satellite includes the cell identifier, satellite identifier and / or frequency band of the next satellite. In some embodiments, for unicast messages, the information from the satellite is sent to the UE by the base station via a release message. In some embodiments, for broadcast messages, the information from the satellite is sent to the UE by the base station via system information. In some embodiments, the system information includes: SystemInformationBlockType4, SystemInformationBlockType5, SystemInformationBlockType32, or other system information blocks.

[0381] In some embodiments, the process of initially attaching to perform one or more initial configurations of Extended Discontinuous Reception (eDRX) and / or MICO modes includes at least one of the following steps: when the UE determines that there is sufficient time to complete one or more configurations of eDRX and / or MICO modes, the UE sends a registration request message to the control entity, the registration request message including notification of impending discontinuous coverage and / or non-coverage intervals; the UE receives a registration acceptance message from the serving satellite; and the UE activates the operation of eDRX and / or MICO modes. In some embodiments, the registration request message includes: parameters of eDRX and / or MICO modes, parameters of multiple sets of eDRX configurations and / or MICO configurations, service stop time of the serving satellite, service start time of the next satellite, UE location information, cell identifier, satellite identifier, satellite ephemeris, and / or frequency band. In some embodiments, the parameters of eDRX and / or MICO modes include: paging time window (PTW) and T for eDRX. eDRX,H The timer, and the T3324 timer and T3512 timer for MICO mode. In some embodiments: the length of the PTW and / or the length of the T3324 timer are configured to the coverage area length of the serving satellite; T eDRX,HThe length of the timer and / or the length of the T3512 timer are configured as the coverage area plus the length of the non-coverage area. In some embodiments, the non-coverage area is configured as the service start time of the next satellite minus the service stop time of the serving satellite. In some embodiments, the process of updating the configuration of eDRX and / or MICO modes once or multiple times includes at least one of the following steps: when the UE determines that there is sufficient time to update the configuration of eDRX and / or MICO modes once or multiple times, the UE sends a registration request message to the control entity, the registration request message including the updated non-coverage area; the UE sends an indication to the base station, the indication including the service stop time of the serving satellite, the service start time of the next satellite, a notification of impending discontinuous coverage, and / or a request to release the Radio Resource Control (RRC) connection; the UE receives a registration acceptance message from the serving satellite; the UE receives a release message from the serving satellite including the release reason; the UE uses one or more updated eDRX and / or MICO mode configuration parameters to activate the operation of eDRX and / or MICO modes.

[0382] In some embodiments, the registration request message includes: parameters of the updated eDRX and / or MICO modes, parameters of the updated multiple sets of eDRX configurations and / or MICO configurations, the length of the coverage area, the length of the non-coverage area, the service stop time of the serving satellite, the service start time of the next satellite, UE location information, cell identifier, satellite identifier, satellite ephemeris, and / or frequency band. In some embodiments, the parameters of the updated eDRX and / or MICO modes include: the paging time window (PTW) for eDRX and T... eDRX,H The timer, and the T3324 timer and T3512 timer for MICO mode. In some embodiments: the length of the PTW and / or the length of the T3324 timer are configured to be the length of the coverage area of ​​the serving satellite; T eDRX,H The length of the timer and / or the length of the T3512 timer are configured as the coverage interval plus the length of the non-coverage interval. In some embodiments, the non-coverage interval is configured as the service start time of the next satellite minus the service stop time of the serving satellite.

[0383] In some embodiments, the registration request message is used to enable the control entity to determine the PTW and T for eDRX. eDRX,HThe timer value is determined, and / or the values ​​of the T3324 and T3512 timers used for MICO mode are determined. In some embodiments, the release reason includes an offset value for one or more configurations of eDRX and / or MICO mode, and the UE is configured to wake up to monitor paging during a coverage interval in a discontinuous coverage scenario based on the offset value. In some embodiments, the offset value is an updated UE identity. In some embodiments, the updated UE identity is: a modified International Mobile Subscriber Identity (IMSI) when the UE registers with the Evolved Packet Core (EPC); or a modified 5G Globally Unique Temporary Identifier (5G-GUTI) when the UE registers with the 5G Core (5GC). In some embodiments, the modified IMSI or 5G-GUTI is related to the start time of the Paging Superframe (PH), PTW, and / or the end time of the PTW.

[0384] In some embodiments, the UE in a discontinuous coverage scenario includes the following situations: the UE is in a Radio Resource Control (RRC) connected state during the transition from a coverage area to a non-coverage area; the UE is in an RRC connected state during the transition from a non-coverage area to a coverage area; the UE is in an RRC idle state or an RRC inactive state during the transition from a coverage area to a non-coverage area; and the UE is in an RRC idle state or an RRC inactive state during the transition from a non-coverage area to a coverage area. In some embodiments, when the UE is in an RRC connected state during the transition from a coverage area to a non-coverage area, the UE performs power-saving mechanisms including: reducing the UE's measurement latency to the serving cell; avoiding the UE from continuously performing cell selection before re-establishing a connection; and / or reducing the cell selection latency. In some embodiments, the UE reduces the serving cell measurement latency by: the UE reducing or prematurely stopping a first timer based on information from satellites to reduce the serving cell recovery time; and / or the UE using a second timer shorter than the first timer based on information from satellites to reduce the serving cell recovery time.

[0385] In some embodiments, if the serving cell is a quasi-fixed earth cell, the information from the satellite includes: the service stop time of the serving satellite, departure indication, the service start time of the next satellite, the physical cell identifier of the serving satellite, satellite identifier or satellite ephemeris, and / or the physical cell identifier, satellite identifier or satellite ephemeris of the next satellite. In some embodiments, if the serving cell is a mobile cell, the information from the satellite includes: the service stop time of the serving satellite, departure indication, the service start time of the next satellite, ephemeris information, the reference position of the serving cell, elevation angle, maximum distance, cell coverage area size, the physical cell identifier of the serving satellite, satellite identifier or satellite ephemeris, and / or the physical cell identifier, satellite identifier or satellite ephemeris of the next satellite. In some embodiments, the information from the satellite is sent to the UE by the base station via a broadcast message or a unicast message. In some embodiments, preventing the UE from continuously performing cell selection or reducing measurement time before re-establishing a connection is based on the following information: the arrival time of the next satellite, or parameters of Extended Discontinuous Reception (eDRX) and / or PSM. In some embodiments, the arrival time information of the next satellite is sent to the UE by the base station via a broadcast message or a unicast message. In some embodiments, the parameters of eDRX and / or PSM include: paging time window (PTW), eDRX period, T3324 timer, and / or T3412 timer.

[0386] In some embodiments, the parameters of eDRX and / or PSM may be updated based on new parameters or offset values. In some embodiments, the parameters of eDRX and / or PSM are sent to the UE by the base station via unicast messages. In some embodiments, the unicast messages include: RRCConnectionReconfiguration messages, DLInformationTransfer messages, or RRCConnectionRelease messages. In some embodiments, when the UE receives an RRCConnectionRelease message from the base station, the UE activates the configuration of eDRX or PSM and stops performing cell selection measurements during non-coverage intervals. In some embodiments, reducing cell selection latency is based on information about the next satellite. In some embodiments, the information about the next satellite is sent to the UE by the base station via broadcast or unicast messages. In some embodiments, for unicast messages, the UE is configured to receive the cell identifier or satellite identifier of the next satellite via the RRCConnectionRelease message. In some embodiments, for broadcast messages, the UE is configured to receive the information about the next satellite via system information.

[0387] In some embodiments, system information includes SystemInformationBlockType4 or SystemInformationBlockType5. In some embodiments, when the UE is in an RRC idle or RRC inactive state while moving from a coverage area to an out-of-coverage area, the UE performs a power-saving mechanism including at least one of the following: the UE listens for paging from the base station to receive parameter reconfiguration for one or more eDRX and / or PSM configurations (in this case, the UE will enter an RRC connected state to receive the updated eDRX / PSM parameters); the UE receives the service stop time of the serving satellite and / or the service start time of the next satellite from the base station (in this case, the UE remains in the RRC idle / inactive state and receives the service stop / start time via SIB); the UE receives one or more eDRX configurations and / or one or more PSM configurations from the base station (in this case, the UE pre-configures multiple eDRX / PSM configurations and may remain in the RRC idle / inactive state); the UE receives offset values ​​of one or more eDRX configurations and / or one or more PSM configurations from the base station (in this case, if these offset values ​​are broadcast by the base station, the UE remains in the RRC idle / inactive state).

[0388] In some embodiments, the UE is configured to listen for paging from the base station during the coverage period, thereby configuring the UE to enter an RRC connected state. In some embodiments, parameters of eDRX and / or PSM are transmitted from the base station to the UE via an RRCConnectionReconfiguration message, a DLInformationTransfer message, or an RRCConnectionRelease message. In some embodiments, when the UE determines that it needs to modify one or more eDRX configurations and / or one or more PSM configurations based on a timer, the service stop time of the serving satellite, and / or the service start time of the next satellite, the UE requests new parameters or offset values ​​of one or more eDRX and / or PSM parameters from the base station or MME. The request message may be an RRCConnectionSetupComplete message, a ULInformationTransfer message, or a UEAssistanceInformation message. In some embodiments, the parameter offset values ​​of one or more eDRX configurations and / or one or more PSM configurations include one or more non-access stratum (NAS) level parameters.

[0389] In some embodiments, when the UE is within a coverage area, the period of the eDRX and / or PSM configuration is modified to "initial period + offset value," thereby matching the "on period" of an eDRX configuration and / or a PSM configuration with the coverage area and the "off period" with the non-coverage area. In some embodiments, after the UE receives the service stop time of the serving satellite and / or the service start time of the next satellite from the base station, the UE remains in an RRC idle state or an RRC inactive state and listens for control information from the base station. In some embodiments, the UE is configured to use the service stop time of the serving satellite and / or the service start time of the next satellite to calculate or update the period of the eDRX and / or PSM. In some embodiments, the eDRX configuration and / or PSM configuration may be configured for the same satellite or separately for different satellites with different non-coverage areas. In some embodiments, the parameter offset value of one or more eDRX configurations and / or one or more PSM configurations includes a common offset value for one or more eDRX configurations and / or PSM configurations for the UE in a specific area.

[0390] In some embodiments, the common offset value includes: a first timing offset for the eDRX paging time window (PTW) or PSM timer T3324 for the serving satellite, or a second timing offset for the eDRX PTW or PSM timer T3324 for the next satellite, wherein the value of the first timing offset and / or the value of the second timing offset can be positive or negative. In some embodiments, the common offset value includes access stratum (AS) level parameters. In some embodiments, based on the common offset value from the serving satellite, a UE in a specific area is configured to extend or shorten the eDRX PTW or PSM timer T3324 for the serving satellite without entering an RRC connected state, and / or extend or shorten the eDRX PTW or PSM timer T3324 for the next satellite based on the common offset value for the next satellite. In some embodiments, the eDRX configuration and / or PSM configuration includes an initial configuration of one or more eDRX and / or PSM, and an updated configuration of one or more eDRX and / or PSM. In some embodiments, the configuration update of one or more eDRX and / or PSM is initiated by the UE, base station, or mobility management entity (MME).

[0391] In some embodiments, the process of performing initial configuration of one or more eDRX and / or PSM via initial attach includes at least one of the following steps: the UE receives broadcast system information from the base station; the UE completes a random access procedure based on the service stop time of the serving satellite; or, if there is insufficient time to complete the random access procedure, the UE avoids initiating the random access procedure; the UE sends a NAS message including an attach request message to the serving satellite; the UE receives an attach accept message from the serving satellite; the UE receives an RRCConnectionRelease message from the serving satellite; and after receiving the RRCConnectionRelease message, the UE enters an RRC idle state or an RRC inactive state and activates the operation of the eDRX and / or PSM.

[0392] In some embodiments, the attach request message is carried within an RRC message. In some embodiments, the RRC message includes an RRCConnectionSetupComplete message or a ULInformationTransfer message. In some embodiments, the attach request message includes parameters for eDRX and / or PSM, parameters for multiple sets of eDRX configurations and / or PSM configurations, service stop time for the serving satellite, service start time for the next satellite, UE location information, cell identifier, satellite identifier, and / or satellite ephemeris. In some embodiments, the parameters for eDRX and / or PSM include: the paging time window PTW and T for eDRX. eDRX,H The timer, and the T3324 and T3412 timers for PSM. In some embodiments, the length of the PTW and / or the length of the T3324 timer are configured to be the coverage interval length of the serving satellite, while T... eDRX,H The length of the timer and / or the length of the T3412 timer are configured as the coverage area plus the length of the non-coverage area. In some embodiments, the non-coverage area is configured as the service start time of the next satellite minus the service stop time of the serving satellite. In some embodiments, the attach request message is used to enable the MME to determine the values ​​of the T3324 and T3412 timers. In some embodiments, the attach accept message is carried in an RRC message containing an RRCConnectionReconfiguration message or a DLInformationTransfer message. In some embodiments, after receiving the attach accept message, the UE sets one or more eDRX configurations and / or one or more PSM configurations for the default radio bearer.

[0393] In some embodiments, the process of updating one or more eDRX and / or PSM configurations includes at least one of the following steps: the UE receives broadcast system information from the base station; when the UE determines that the service stop time of the serving satellite falls outside the activation time of the current eDRX and / or PSM cycle, or the service start time of the next satellite falls outside the activation time of the next cycle, the UE initiates a random access procedure to update one or more eDRX configurations and / or one or more PSM configurations; otherwise, if there is not enough time to complete the random access procedure, the UE avoids initiating the random access procedure; the UE sends a NAS message containing a tracking area update request message to the serving satellite; the UE receives a tracking area update accept message from the serving satellite; the UE receives an RRCConnectionRelease message from the serving satellite; and after receiving the RRCConnectionRelease message, the UE enters an RRC idle state or an RRC inactive state, and activates the operation of eDRX and / or PSM based on the updated one or more eDRX configurations and / or one or more PSM configurations.

[0394] In some embodiments, the tracking area update request message is carried within an RRC message. In some embodiments, this RRC message includes an RRCConnectionSetupComplete message or a ULInformationTransfer message. In some embodiments, the tracking area update request message includes updated eDRX and / or PSM parameters, parameters of multiple eDRX configurations and / or PSM configurations, service stop time of the serving satellite, service start time of the next satellite, UE location information, cell identifier, satellite identifier, and / or satellite ephemeris. In some embodiments, the updated eDRX and / or PSM parameters include PTW and T for eDRX. eDRX,H The timer, and the T3324 and T3412 timers for PSM. In some embodiments, the tracking area update request message is used to enable the MME to determine the values ​​of the T3324 and T3412 timers.

[0395] Figure 19A block diagram of a base station 1900 according to an embodiment of the present invention is shown. In some embodiments, the base station 1900 includes a transmitter 1901 configured to send information to a user equipment (UE) in a discontinuous coverage scenario, wherein the discontinuous coverage scenario includes alternations between in-coverage and out-of-coverage, such that the UE remains in sleep mode or in Mobile Terminal Initiated Connection (MICO) mode during the out-of-coverage period of the discontinuous scenario, and wakes up during the coverage period to monitor paging. The out-of-coverage interval is configured based on the service stop time of the serving satellite and / or the service start time of the next satellite, and the service stop time of the serving satellite and / or the service start time of the next satellite are determined based on information from the base station. This solves the problems in the prior art, provides a non-terrestrial network communication (NTN) for the Internet of Things (IoT), provides a power-saving mechanism for discontinuous coverage in IoT non-terrestrial networks, provides good communication performance, and / or provides high reliability. The UE can remain in sleep mode during the out-of-coverage period and wake up during the coverage period to monitor paging.

[0396] In some embodiments, the wireless communication method performed by the base station further includes: sending a release reason to notify the UE to perform a power-saving mechanism. In some embodiments, the release reason is sent to the UE's Radio Resource Control (RRC) layer to control the operation of the power-saving mechanism. In some embodiments, the release reason refers to a "discontinuous coverage release reason". In some embodiments, the release reason is sent by the base station to a control entity. In some embodiments, the release reason is sent by the control entity to the UE based on a request initiated by the UE or the base station via a serving satellite. In some embodiments, the control entity is an Access and Mobility Management Function (AMF). In some embodiments, if the serving cell is a quasi-earth fixed cell, the information from the satellite includes: the service stop time of the serving satellite, departure indication, the service start time of the next satellite, physical cell identifier, satellite identifier, satellite ephemeris or the frequency band of the serving satellite, and / or the physical cell identifier, satellite identifier, satellite ephemeris or frequency band of the next satellite. In some embodiments, if the serving cell is a mobile cell, the information from the satellite includes: the reference location, elevation angle, maximum distance, cell coverage footprint size, physical cell identifier, satellite identifier, satellite ephemeris or frequency band of the serving satellite, and / or the physical cell identifier, satellite identifier, satellite ephemeris or frequency band of the next satellite.

[0397] In some embodiments, information from the serving satellite is sent to the UE by the base station via a broadcast message or a unicast message. In some embodiments, the information from the satellite includes the cell identifier, satellite identifier, and / or frequency band of the next satellite. In some embodiments, for unicast messages, the information from the satellite is sent to the UE by the base station via a release message. In some embodiments, for broadcast messages, the information from the satellite is sent to the UE by the base station via system information. In some embodiments, the system information includes SystemInformationBlockType4, SystemInformationBlockType5, SystemInformationBlockType32, or other system information blocks. In some embodiments, the process of performing initial configuration of one or more Extended Discontinuous Reception (eDRX) and / or MICO modes via initial attach includes at least one of the following steps: the base station receives a registration request message containing a non-coverage area from the UE via a serving satellite; the base station forwards the registration request message to a control entity; the base station receives a registration acceptance message from the control entity; the base station forwards the registration acceptance message containing the non-coverage area to the UE via a serving satellite; the base station sends a UE context release request message to the control entity to initiate the release of the UE's radio bearer; the base station receives a UE context release instruction message from the control entity to release the UE; and the base station sends a release message containing a release reason to the UE via a serving satellite to release the UE.

[0398] In some embodiments, the registration request message includes parameters for eDRX and / or MICO modes, parameters for multiple sets of eDRX configurations and / or MICO configurations, service stop time of the serving satellite, service start time of the next satellite, UE location information, cell identifier, satellite identifier, satellite ephemeris, and / or operating frequency band. In some embodiments, the parameters for eDRX and / or MICO modes include the paging time window (PTW) and T for eDRX. eDRX,H The timer, including the T3324 timer and the T3512 timer for MICO mode. In some embodiments, the length of the PTW and / or the length of the T3324 timer are configured to the coverage area of ​​the serving satellite; while T... eDRX,H The length of the timer and / or the length of the T3512 timer are configured as the coverage interval plus the non-coverage interval. In some embodiments, the non-coverage interval is configured as the service start time of the next satellite minus the service stop time of the serving satellite.

[0399] In some embodiments, the process of updating the configuration for one or more eDRX and / or MICO modes includes at least one of the following steps: the base station receives a registration request message from the UE via a serving satellite, the message including the updated non-coverage area; the base station receives an indication including the service stop time of the serving satellite, the service start time of the next satellite, a notification of impending entry into discontinuous coverage, and / or a request to release a Radio Resource Control (RRC) connection; the base station forwards the registration request message to a control entity; the base station receives a registration acceptance message from the control entity; the base station forwards the registration acceptance message containing the updated non-coverage area to the UE via the serving satellite; the base station sends a UE context release request message to the control entity to initiate the release of the radio bearer of the UE; the base station receives a UE context release instruction message from the control entity to release the UE; the base station sends a release message containing the release reason to the UE via the serving satellite to release the UE.

[0400] In some embodiments, the registration request message includes: updated eDRX and / or MICO mode parameters, updated parameters for multiple eDRX configurations and / or MICO configurations, duration of coverage area, duration of non-coverage area, service stop time of serving satellite, service start time of the next satellite, UE location information, cell identifier, satellite identifier, satellite ephemeris information, and / or frequency band. In some embodiments, the updated eDRX and / or MICO mode parameters include: paging time window (PTW) and T for eDRX. eDRX,H A timer, and T3324 and T3512 timers for MICO mode. In some embodiments, the length of the PTW and / or the length of the T3324 timer are configured to the coverage area of ​​the serving satellite; T eDRX,H The length of the timer and / or the length of the T3512 timer are configured as the coverage interval plus the non-coverage interval. In some embodiments, the non-coverage interval is configured as the service start time of the next satellite minus the service stop time of the serving satellite.

[0401] In some embodiments, the registration request message is used to determine the PTW and T of the eDRX. eDRX,HThe value of the timer, and / or the values ​​of the T3324 and T3512 timers used to determine the MICO mode. In some embodiments, the release reason includes an offset of one or more configurations of eDRX and / or MICO mode, which is used to wake up the UE and listen for paging in a coverage area of ​​a discontinuous coverage scenario. In some embodiments, the offset is an updated UE identifier. In some embodiments, when the UE registers to the EPC, the updated UE identifier is the modified IMSI; when the UE registers to the 5GC, the updated UE identifier is the modified 5G-GUTI. In some embodiments, the modified IMSI or 5G-GUTI is related to the start time of the paging superframe (PH), PTW, and / or the end time of the PTW.

[0402] In some embodiments, when the base station detects that the UE has entered a non-coverage area within the coverage area and is in an RRC connection state, the energy-saving mechanisms implemented by the base station include: reducing the measurement latency of the UE to the serving cell, preventing the UE from continuously performing cell selection before re-establishing the connection, and / or reducing the latency of cell selection.

[0403] In some embodiments, if the serving cell is a quasi-fixed Earth cell, the information from the satellite includes: the service stop time of the serving satellite, a departure indication, the service start time of the next satellite, the physical cell identifier of the serving satellite, the satellite identifier or satellite ephemeris, and / or the physical cell identifier, satellite identifier or satellite ephemeris of the next satellite. In some embodiments, if the serving cell is a mobile cell, the information from the satellite includes: the service stop time of the serving satellite, a departure indication, the service start time of the next satellite, ephemeris information, the reference position of the serving cell, elevation angle, maximum distance, cell coverage footprint size, the physical cell identifier of the serving satellite, the satellite identifier or satellite ephemeris, and / or the physical cell identifier, satellite identifier or satellite ephemeris of the next satellite. In some embodiments, the information from the satellite is transmitted to the UE by the base station via a broadcast message or a unicast message.

[0404] In some embodiments, the arrival time information of the next satellite is sent to the UE by the base station via a broadcast message or a unicast message. In some embodiments, the base station is configured to send parameters of the eDRX and / or PSM configuration to the UE before releasing the UE, then release the UE based on the service stop time of the serving satellite, and instruct the UE to activate the eDRX or PSM configuration in the non-coverage area to stop performing cell selection measurements.

[0405] In some embodiments, reducing cell selection latency is achieved based on information about the next satellite. In some embodiments, this information is sent to the UE by the base station via a broadcast or unicast message. In some embodiments, for unicast messages, the base station is configured to send the cell identifier or satellite identifier of the next satellite to the UE via an RRCConnectionRelease message. In some embodiments, for broadcast messages, the base station is configured to send the next satellite information to the UE via system information. In some embodiments, the system information includes SystemInformationBlockType4 or SystemInformationBlockType5.

[0406] In some embodiments, when the UE is in RRC Idle or RRC Inactive state, the base station performs a power-saving mechanism including at least one of the following: the base station paging the UE to reconfigure one or more eDRX and / or PSM configuration parameters of the UE; the base station broadcasting to the UE the service stop time of the serving satellite and / or the service start time of the next satellite; the base station configuring one or more eDRX configurations and / or one or more PSM configurations to the UE; the base station configuring the UE with offsets of one or more eDRX configuration parameters and / or one or more PSM configuration parameters. In some embodiments, the base station is configured to paging the UE within the coverage area to control the UE to enter the RRC Connected state.

[0407] In some embodiments, one or more offsets of parameters of one or more eDRX configurations and / or one or more PSM configurations include common offsets of one or more eDRX configuration parameters and / or one or more PSM configuration parameters for a UE within a specific area. In some embodiments, the common offset includes: a first timing offset for the eDRX PTW or PSM timer T3324 for the serving satellite, or a second timing offset for the eDRX PTW or PSM timer T3324 for the next satellite, and the values ​​of the first timing offset and / or the second timing offset can be positive or negative. In some embodiments, the common offset includes access stratum (AS) level parameters. In some embodiments, based on the common offset from the serving satellite, the base station is configured to instruct a UE within a specific area to extend or shorten the eDRX PTW or PSM timer T3324 for the serving satellite without entering the RRC Connected state, and / or the base station is configured to instruct a UE to extend or shorten the eDRX PTW or PSM timer T3324 for the next satellite based on the common offset for the next satellite. In some embodiments, eDRX configuration and / or PSM configuration includes initial configurations of one or more eDRX and / or PSMs, and updated configurations of one or more eDRX and / or PSMs. In some embodiments, the updated configurations of one or more eDRX and / or PSMs are initiated by the UE, by the base station, or by the Mobility Management Entity (MME).

[0408] In some embodiments, the process of performing initial configuration of one or more eDRX and / or PSMs via initial attach includes at least any one of the following steps: the base station sends broadcast system information to the UE; the base station receives a NAS message including an attach request message from the serving satellite; the base station forwards the NAS message including the attach request message to the MME; the base station receives an attach accept message from the MME; the base station forwards the attach accept message to the serving satellite; after data transmission is completed, the base station sends a UE context release request message with a user inactivity reason value to the MME to initiate the release of the radio bearer of the UE; the base station receives a UE context release command message from the MME to release the UE; the base station sends an RRCConnectionRelease message to the serving satellite to release the UE.

[0409] In some embodiments, the process of updating the configuration of one or more eDRX and / or PSM includes at least any one of the following steps: the base station sends broadcast system information to the UE; the base station performs data transmission with the UE; after the data transmission is completed, the base station sends a UE context release request message with a user inactivity reason value to the MME to initiate the release of the radio bearer of the UE; the base station receives a UE context release instruction message from the MME to release the UE; the base station sends an RRCConnectionRelease message to the serving satellite to release the UE.

[0410] In some embodiments, the process of updating the configuration of one or more eDRX and / or PSM includes at least any one of the following steps: when the base station determines that the period of the eDRX and / or PSM needs to be modified to match the arrival time of the next satellite, the base station sends an ENB configuration update message to the MME; if it is confirmed that the eDRX and / or PSM needs to be modified, the base station receives a paging message from the MME; the base station paging the UE to enable the UE to use the original one or more eDRX configurations and / or the original one or more PSM configurations; the base station receives an attach request message or a tracking area update request message from the serving satellite; the base station forwards the attach request message or tracking area update request message to the MME; the base station receives an attach accept message or a tracking area update accept message from the MME; the base station receives an ENB configuration update acknowledge message from the MME; after receiving the ENB configuration update acknowledge message, the base station updates one or more eDRX configurations and / or one or more PSM configurations.

[0411] In some embodiments, the ENB configuration update message carries information including: the service stop time of the serving satellite, the service start time of the next satellite, and a cause value. In some embodiments, the paging message includes updated paging eDRX cycle parameters, PTW, T3324 timer, and T3412 timer. In some embodiments, the attach accept message or tracking area updated accept message is carried in an initial context setup request message, which includes eDRX and / or PSM parameters, and / or the attach accept message or tracking area updated accept message is carried in an RRC message. In some embodiments, the UE context release command message and / or tracking area update request message is carried in an RRC message. In some embodiments, the RRC message includes an RRCConnectionSetupComplete message or a ULInformationTransfer message. In some embodiments, the UE context release instruction message and / or tracking area update request message includes: updated eDRX and / or PSM parameters, parameters of multiple eDRX configurations and / or PSM configurations, service stop time of the serving satellite, service start time of the next satellite, UE location information, cell identifier, satellite identifier, and / or satellite ephemeris information. In some embodiments, the updated eDRX and / or PSM parameters include: the PTW and T of the eDRX. eDRX,H The T3324 and T3412 timers of the PSM are also included. In some embodiments, the UE context release instruction message and / or tracking area update request message are used by the MME to determine the values ​​of the T3324 and T3412 timers.

[0412] Summary of Implementation Examples: 1. The UE maintains an RRC connected state while moving from in-coverage to out-of-coverage. This occurs under any of the following conditions: a. Reduce the measurement latency of the UE to the serving cell.

[0413] b. Avoid the UE continuously performing cell (re)selection before re-establishing the connection, and / or reduce measurement time.

[0414] c. Reduce the latency of cell (re)selection.

[0415] 2. The UE is in RRC Idle / RRC Inactive state when moving from inside the coverage area to outside the coverage area. This occurs under any of the following conditions: a. The eNB reconfigures the eDRX / PSM parameters of the UE by paging the UE.

[0416] b. The service cessation time of the eNB broadcast service satellite and / or the service start time of the next satellite.

[0417] c. The eNB configures multiple eDRX / PSM configurations for the UE.

[0418] 3. UE eDRX / PSM configuration process: a. Initial configuration of eDRX / PSM.

[0419] b. eDRX / PSM Updating configuration.

[0420] i) The eDRX / PSM configuration is updated proactively by the UE.

[0421] ii) Update the eDRX / PSM configuration via eNB / MME.

[0422] iii) When the UE is in RRC Idle / Inactive state, the eNB / MME updates the eDRX / PSM configuration.

[0423] Some embodiments offer the following commercial benefits: 1. Solving problems in the prior art. 2. Providing non-terrestrial (NTN) communication capabilities for the Internet of Things (IoT). 3. Achieving energy savings in discontinuous coverage scenarios of IoT NTNs. 4. Providing good communication performance. 5. Providing high reliability. 6. The UE can enter a sleep state during periods of non-coverage and wake up during periods of coverage to monitor paging. 7. Some embodiments of the present invention can be used by 5G-NR chip manufacturers, V2X communication system developers, automotive manufacturers (including cars, trains, trucks, buses, bicycles, motorcycles, helmets, etc.), unmanned aerial vehicles (UAVs), smartphone manufacturers, public safety communication equipment, AR / VR devices (such as games, conferences / seminars, educational uses), etc. Some embodiments are "technology / process combinations" that can be adopted by 3GPP specifications to form the final product. Some embodiments are applicable to 5G NR licensed spectrum, unlicensed spectrum, or shared spectrum communication. Some embodiments propose new technical mechanisms.

[0424] Figure 20 A block diagram of an example system 700 for wireless communication according to an embodiment of the present invention is shown. The various embodiments described herein can be implemented in this system by any suitably configured hardware and / or software. Figure 20 System 700 is shown, including radio frequency (RF) circuitry 710, baseband circuitry 720, application circuitry 730, memory / storage device 740, display 750, camera 760, sensor 770, and input / output (I / O) interface 780, which are coupled to each other at least as shown. Application circuitry 730 may include circuitry such as one or more single-core or multi-core processors. The processor may include any combination of general-purpose and special-purpose processors, such as a graphics processor or application processor. The processor may be coupled to the memory / storage device and configured to execute instructions stored in the memory / storage device to enable various applications and / or operating systems to run on the system.

[0425] The baseband circuit 720 may include circuitry, such as, but not limited to, one or more single-core or multi-core processors. The processor may include a baseband processor. The baseband circuitry can handle various wireless control functions, enabling the system to communicate with one or more wireless networks via radio frequency circuitry. Wireless control functions may include, but are not limited to, signal modulation, encoding, decoding, and radio frequency conversion. In some embodiments, the baseband circuitry may support communication compatible with one or more wireless technologies. For example, in some embodiments, the baseband circuitry may support communication with the evolved universal terrestrial radio access network (EUTRAN) and / or other wireless metropolitan area networks (WMAN), wireless local area networks (WLAN), and wireless personal area networks (WPAN). In embodiments where the baseband circuitry is configured to support wireless communication using multiple wireless protocols, the baseband circuitry may be referred to as a multimode baseband circuitry.

[0426] In various embodiments, baseband circuitry 720 may include circuitry for processing signals that are not strictly within the baseband frequency range. For example, in some embodiments, baseband circuitry may include circuitry for processing signals having an intermediate frequency (IF) (between baseband and radio frequency). RF circuitry 710 enables communication with a wireless network via modulated electromagnetic radiation propagating in a non-solid medium. In various embodiments, RF circuitry may include switches, filters, amplifiers, etc., to facilitate communication with a wireless network. In various embodiments, RF circuitry 710 may also include circuitry for processing signals that are not strictly within the radio frequency range. For example, in some embodiments, RF circuitry may include circuitry for processing signals having an intermediate frequency (IF) (between baseband and radio frequency).

[0427] In various embodiments, the aforementioned transmitting, controlling, or receiving circuitry of the user equipment, eNB, or gNB may be wholly or partially embodied in one or more circuits within the RF circuitry, baseband circuitry, and / or application circuitry. As used herein, "circuit" may refer to, be a portion thereof, or may include an Application-Specific Integrated Circuit (ASIC), electronic circuitry, a processor (shared, dedicated, or grouped processors), and / or memory (shared, dedicated, or grouped memory) for executing one or more software or firmware programs, combinational logic circuitry, and / or other suitable hardware components providing the aforementioned functionality. In some embodiments, the circuitry of an electronic device may be implemented by one or more software or firmware modules, or the functionality associated with the circuitry may be implemented by software or firmware modules. In some embodiments, some or all of the components of the baseband circuitry, application circuitry, and / or memory / storage device may be implemented together in a system on a chip (SOC). The memory / storage device 740 may be used to load and store data and / or instructions, for example, for system operation. In some embodiments, the memory / storage device may include any combination of suitable volatile memory, such as dynamic random access memory (DRAM) and / or non-volatile memory (e.g., flash memory).

[0428] In various embodiments, I / O interface 780 may include one or more user interfaces for enabling user interaction with the system, and / or peripheral component interfaces for enabling peripheral components to interact with the system. User interfaces may include (but are not limited to): a physical keyboard or keyboard area, a touchpad, a speaker, a microphone, etc. Peripheral component interfaces may include (but are not limited to): a non-volatile memory port, a universal serial bus (USB) port, an audio jack, and a power interface. In various embodiments, sensor 770 may include one or more sensing devices for determining system-related environmental conditions and / or location information. In some embodiments, sensors may include (but are not limited to): a gyroscope sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of, or interact with, baseband and / or radio frequency circuitry to communicate with components of a positioning network, such as Global Positioning System (GPS) satellites.

[0429] In various embodiments, display 750 may include a display screen, such as a liquid crystal display or a touch screen display. In various embodiments, system 700 may be a mobile computing device, such as (but not limited to) a laptop, tablet, netbook, ultrabook, smartphone, AR / VR glasses, etc. In various embodiments, the system may have more or fewer components and / or different architectures. Where applicable, the methods described herein may be implemented as a computer program. The computer program may be stored on a storage medium, such as a non-transitory storage medium.

[0430] Those skilled in the art will understand that the units, algorithms, and steps described and disclosed in the embodiments of this invention can be implemented through electronic hardware or a combination of computer software and electronic hardware. Whether a function is operated through hardware or software depends on the specific application conditions and the design requirements of the technical solution. For each specific application, those skilled in the art can adopt different methods to implement its functions, but such implementations should not exceed the scope of this invention. Those skilled in the art should understand that the workflow of the systems, devices, and units in the above embodiments can be referred to, as the workflows of the above systems, devices, and units are basically the same. For clarity and simplicity, the above workflows will not be repeated.

[0431] It is understood that the systems, apparatuses, and methods disclosed in the embodiments of the present invention can also be implemented in other ways. The above embodiments are merely illustrative examples. The division of each unit is based solely on logical function, and other division methods may exist in actual implementation. Multiple units or components may also be combined or integrated in another system; certain features may also be omitted or skipped. On the other hand, the mutual coupling, direct coupling, or communication coupling shown or discussed, whether indirect or direct, can operate electrically, mechanically, or otherwise through certain ports, devices, or units. As an explanation, the separated units may or may not be physically separated components. The units used for illustration may not also be physical units, i.e., they may be located in the same location or distributed across multiple network units. Depending on the purpose of the embodiment, some or all of the units may be used. Furthermore, each functional unit in each embodiment can be integrated into the same processing unit, and can be physically independent, or two or more units can be integrated into the same processing unit.

[0432] If software functional units are implemented, used, and sold in the form of a product, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions proposed in this invention can be implemented in whole or in part in the form of a software product; or, the parts of this technical solution that are advantageous to the prior art can also be implemented in the form of a software product. This software product is stored in a computer's storage medium and includes multiple instructions for causing a computing device (e.g., a personal computer, server, or network device) to execute all or part of the steps disclosed in the embodiments of this invention. The storage medium includes a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a floppy disk, or other media capable of storing program code.

[0433] Although the invention has been described in conjunction with what are considered to be the most practical and preferred embodiments, it should be understood that the invention is not limited to the embodiments described above, but is intended to cover various modifications and arrangements made without departing from the broadest scope defined by the appended claims.

Claims

1. A wireless communication method executed by a user equipment (UE), characterized in that, include: When the UE is in a discontinuous coverage scenario where coverage and non-coverage areas alternate, an energy-saving mechanism is executed. In the energy-saving mechanism, the UE remains in a sleep state or in a mobile terminal-only connection-initiated (MICO) mode during the non-coverage period of the discontinuous coverage scenario, and is configured to wake up during the coverage period of the discontinuous coverage scenario to monitor paging. The non-coverage area is configured based on the service stop time of the serving satellite and / or the service start time of the next satellite, and the service stop time of the serving satellite and / or the service start time of the next satellite are determined based on information from the satellite.

2. The wireless communication method executed by the UE according to claim 1, characterized in that, The UE executes the power-saving mechanism after receiving the release reason from the base station or control entity via the serving satellite.

3. The wireless communication method performed by the UE according to claim 2, characterized in that, The release reason is sent to the Radio Resource Control (RRC) layer of the UE to control the operation of the power-saving mechanism.

4. The wireless communication method performed by the UE according to claim 2, characterized in that, The release reason refers to the reason for discontinuous coverage release.

5. The wireless communication method performed by the UE according to claim 2, characterized in that, The release reason is that the control entity sends a request to the UE via the serving satellite in response to a request from the UE or the base station.

6. The wireless communication method performed by the UE according to claim 2, characterized in that, The control entity is the Access and Mobility Management Function (AMF).

7. The wireless communication method performed by the UE according to claim 1, characterized in that, The UE's reduction of the serving cell's measurement latency includes the UE reducing or prematurely stopping a first timer based on information from the serving satellite, thereby reducing the serving cell's recovery time.

8. The wireless communication method performed by the UE according to claim 1, characterized in that, If the serving cell is a quasi-Earth fixed cell, the information from the satellite includes: the service stop time of the serving satellite, the departure indication, the service start time of the next satellite, the physical cell identifier, satellite identifier, satellite ephemeris or frequency band of the serving satellite, and / or the physical cell identifier, satellite identifier, satellite ephemeris or frequency band of the next satellite.

9. The wireless communication method performed by the UE according to claim 1, characterized in that, If the serving cell is a mobile cell, the information from the satellite includes: the reference location, elevation angle, maximum distance, cell coverage area size, physical cell identifier, satellite identifier, satellite ephemeris or frequency band of the serving satellite, and / or the physical cell identifier, satellite identifier, satellite ephemeris or frequency band of the next satellite.

10. The wireless communication method performed by the UE according to claim 1, characterized in that, Information from the serving satellite is sent to the UE by the base station via broadcast or unicast messages.

11. The wireless communication method performed by the UE according to claim 10, characterized in that, Information from the satellite includes the cell identifier, satellite identifier, and / or frequency band of the next satellite.

12. The wireless communication method performed by the UE according to claim 10, characterized in that, For the unicast message, information from the satellite is sent to the UE by the base station via a release message.

13. The wireless communication method performed by the UE according to claim 10, characterized in that, For the broadcast message, the information from the satellite is sent to the UE by the base station through system information.

14. The wireless communication method performed by the UE according to claim 13, characterized in that, The system information includes system information block type 4, system information block type 5, system information block type 32, or other system information blocks.

15. The wireless communication method performed by the UE according to claim 1, characterized in that, The process of performing one or more initial configurations of extended discontinuous reception eDRX and / or the MICO mode via initial attachment includes at least one of the following steps: When the UE determines that it has sufficient time to complete one or more configurations of the eDRX and / or the MICO mode, the UE sends a registration request message to the control entity, the registration request message including a notification of impending discontinuous coverage and / or the non-coverage interval; The UE receives a registration acceptance message from the serving satellite; The UE activates the operation of the eDRX and / or the MICO mode.

16. The wireless communication method performed by the UE according to claim 15, characterized in that, The registration request message includes: parameters of the eDRX and / or the MICO mode, parameters of multiple sets of eDRX configurations and / or MICO configurations, service stop time of the serving satellite, service start time of the next satellite, UE location information, cell identifier, satellite identifier, satellite ephemeris, and / or frequency band.

17. The wireless communication method performed by the UE according to claim 16, characterized in that, The parameters of the eDRX and / or the MICO mode include: the paging time window PTW and T for the eDRX. eDRX,H The timer, and the T3324 timer and T3512 timer for the MICO mode.

18. The wireless communication method performed by the UE according to claim 17, characterized in that, The length of the PTW and / or the length of the T3324 timer are configured to be the length of the coverage area of ​​the serving satellite, while the T eDRX,H The length of the timer and / or the length of the T3512 timer is configured to be the length of the covered interval plus the length of the non-covered interval.

19. The wireless communication method performed by the UE according to claim 16, characterized in that, The non-coverage interval is configured as the service start time of the next satellite minus the service stop time of the serving satellite.

20. The wireless communication method performed by the UE according to claim 1, characterized in that, The process of updating the configuration of the eDRX and / or the MICO mode once or multiple times includes at least one of the following steps: When the UE determines that it has sufficient time to update the configuration of the eDRX and / or the MICO mode once or multiple times, the UE sends a registration request message to the control entity, the registration request message including the updated non-coverage range; The UE sends an indication to the base station, the indication including the service stop time of the serving satellite, the service start time of the next satellite, a notification of impending discontinuous coverage, and / or a request to release the RRC connection; The UE receives a registration acceptance message from the serving satellite; The UE uses one or more updated configured eDRX and / or MICO mode parameters to activate the operation of the eDRX and / or MICO mode.

21. The wireless communication method performed by the UE according to claim 20, characterized in that, The registration request message includes: update parameters of the eDRX and / or the MICO mode, update parameters of multiple sets of eDRX configurations and / or MICO configurations, the length of the coverage area, the length of the non-coverage area, the service stop time of the serving satellite, the service start time of the next satellite, UE location information, cell identifier, satellite identifier, satellite ephemeris, and / or frequency band.

22. The wireless communication method performed by the UE according to claim 21, characterized in that, The update parameters for the eDRX and / or the MICO mode include: PTW and T for the eDRX. eDRX,H The timer, and the T3324 timer and T3512 timer for the MICO mode.

23. The wireless communication method performed by the UE according to claim 22, characterized in that, The length of the PTW and / or the length of the T3324 timer are configured to be the length of the coverage area of ​​the serving satellite, while the T eDRX,H The length of the timer and / or the length of the T3512 timer is configured to be the length of the covered interval plus the length of the non-covered interval.

24. The wireless communication method performed by the UE according to claim 23, characterized in that, The non-coverage interval is configured as the service start time of the next satellite minus the service stop time of the serving satellite.

25. The wireless communication method performed by the UE according to claim 22, characterized in that, The registration request message is used to enable the control entity to determine the PTW and T of the eDRX. eDRX,H The value of the timer, and / or the values ​​of the T3324 timer and the T3512 timer in the MICO mode are determined.

26. The wireless communication method performed by the UE according to claim 1, characterized in that, The release reason includes an offset value for one or more configurations of the eDRX and / or the MICO mode, and the UE is configured to wake up based on the offset value during the coverage interval of the discontinuous coverage scenario to monitor the paging.

27. The wireless communication method performed by the UE according to claim 26, characterized in that, The offset value is the updated UE identity identifier.

28. The wireless communication method performed by the UE according to claim 27, characterized in that, The updated UE identity identifier is the modified International Mobile Subscriber Identity (IMSI) when the UE registers with the Evolved Packet Core (EPC), or the modified 5G Globally Unique Temporary Identifier (5G-GUTI) when the UE registers with the 5G Core Network (5GC).

29. The wireless communication method performed by the UE according to claim 28, characterized in that, The modified IMSI or 5G-GUTI is related to the start time of the paging superframe PH, PTW and / or the end time of the PTW.

30. A wireless communication method performed by a base station, characterized in that, include: Send information to the user equipment (UE) to implement a power-saving mechanism in a discontinuous coverage scenario where coverage and non-coverage areas alternate, so that the UE remains in a sleep state or in a mobile terminal-only connection-initiated (MICO) mode during the non-coverage period of the discontinuous coverage scenario, and wakes up during the coverage period to monitor paging. The non-coverage area is configured based on the service stop time of the serving satellite and / or the service start time of the next satellite, and the service stop time of the serving satellite and / or the service start time of the next satellite are determined based on information from the base station.

31. The wireless communication method performed by a base station according to claim 30, characterized in that, It also includes sending a release reason to the UE to notify the UE to execute the power-saving mechanism.

32. The wireless communication method performed by a base station according to claim 31, characterized in that, The release reason is sent to the Radio Resource Control (RRC) layer of the UE to control the operation of the power-saving mechanism.

33. The wireless communication method performed by a base station according to claim 31, characterized in that, The release reason refers to the reason for discontinuous coverage release.

34. The wireless communication method performed by a base station according to claim 31, characterized in that, The reason for release is sent from the base station to the control entity.

35. The wireless communication method performed by a base station according to claim 34, characterized in that, The release reason is sent to the UE by the control entity via the serving satellite in response to a request from the UE or the base station.

36. The wireless communication method performed by a base station according to claim 34, characterized in that, The control entity is the Access and Mobility Management Function (AMF).

37. The wireless communication method performed by a base station according to claim 30, characterized in that, If the serving cell is a quasi-Earth fixed cell, the information from the satellite includes: the service stop time of the serving satellite, the departure indication, the service start time of the next satellite, the physical cell identifier, satellite identifier, satellite ephemeris or frequency band of the serving satellite, and / or the physical cell identifier, satellite identifier, satellite ephemeris or frequency band of the next satellite.

38. The wireless communication method performed by a base station according to claim 30, characterized in that, If the serving cell is a mobile cell, the information from the satellite includes: the reference location, elevation angle, maximum distance, cell coverage area size, physical cell identifier, satellite identifier, satellite ephemeris or frequency band of the serving satellite, and / or the physical cell identifier, satellite identifier, satellite ephemeris or frequency band of the next satellite.

39. The wireless communication method performed by a base station according to claim 30, characterized in that, Information from the serving satellite is sent to the UE by the base station via broadcast or unicast messages.

40. The wireless communication method performed by a base station according to claim 39, characterized in that, Information from the satellite includes the cell identifier, satellite identifier, and / or frequency band of the next satellite.

41. The wireless communication method performed by a base station according to claim 39, characterized in that, For unicast messages, information from the satellite is sent to the UE by the base station via a release message.

42. The wireless communication method performed by a base station according to claim 39, characterized in that, For broadcast messages, information from the satellite is sent to the UE by the base station via system information.

43. The wireless communication method performed by a base station according to claim 40, characterized in that, The system information includes system information block type 4, system information block type 5, system information block type 32, or other system information blocks.

44. The wireless communication method performed by a base station according to claim 30, characterized in that, The process of performing one or more initial configurations of extended discontinuous reception eDRX and / or MICO modes via initial attachment includes at least one of the following steps: The base station receives a registration request message from the UE via the serving satellite. The registration request message includes a notification of impending discontinuous coverage and / or a non-coverage area. The base station forwards the registration request message to the control entity; The base station receives a registration acceptance message from the control entity; The base station forwards the registration acceptance message containing the non-coverage area to the UE via the serving satellite; The base station sends a UE context release request message to the control entity to initiate the release of the UE radio bearer; The base station receives a UE context release instruction message from the control entity to release the UE; The base station sends a release message containing the release reason to the UE via the serving satellite to release the UE.

45. The wireless communication method performed by a base station according to claim 44, characterized in that, The registration request message includes: parameters of the eDRX and / or the MICO mode, parameters of multiple sets of eDRX configurations and / or MICO configurations, service stop time of the serving satellite, service start time of the next satellite, UE location information, cell identifier, satellite identifier, satellite ephemeris, and / or frequency band.

46. ​​The wireless communication method performed by a base station according to claim 45, characterized in that, The parameters of the eDRX and / or the MICO mode include: the paging time window PTW and T for the eDRX. eDRX,H The timer, and the T3324 timer and T3512 timer for the MICO mode.

47. The wireless communication method performed by a base station according to claim 46, characterized in that, The length of the PTW and / or the length of the T3324 timer are configured to be the length of the coverage area of ​​the serving satellite, while the T eDRX,H The length of the timer and / or the length of the T3512 timer is configured to be the length of the covered interval plus the length of the non-covered interval.

48. The wireless communication method performed by a base station according to claim 45, characterized in that, The non-coverage interval is configured as the service start time of the next satellite minus the service stop time of the serving satellite.

49. The wireless communication method performed by a base station according to claim 30, characterized in that, The process of updating the configuration of the eDRX and / or the MICO mode once or multiple times includes at least one of the following steps: The base station receives a registration request message from the UE via the serving satellite, the registration request message including the updated non-coverage area; The base station receives an indication, which includes the service stop time of the serving satellite, the service start time of the next satellite, a notification of impending discontinuous coverage, and / or a request to release the RRC connection; The base station forwards the registration request message to the control entity; The base station receives a registration acceptance message from the control entity; The base station forwards a registration acceptance message containing the updated non-coverage area to the UE via the serving satellite; The base station sends a UE context release request message to the control entity to initiate the release of the UE's radio bearer; The base station receives a UE context release instruction message from the control entity to release the UE; The base station sends a release message containing the release reason to the UE via the serving satellite to release the UE.

50. The wireless communication method performed by a base station according to claim 49, characterized in that, The registration request message includes: update parameters of the eDRX and / or the MICO mode, update parameters of multiple sets of eDRX configurations and / or MICO configurations, the length of the coverage area, the length of the non-coverage area, the service stop time of the serving satellite, the service start time of the next satellite, UE location information, cell identifier, satellite identifier, satellite ephemeris, and / or frequency band.

51. The wireless communication method performed by a base station according to claim 30, characterized in that, The update parameters for the eDRX and / or the MICO mode include: PTW and T for the eDRX. eDRX,H The timer, and the T3324 timer and T3512 timer for the MICO mode.

52. The wireless communication method performed by a base station according to claim 30, characterized in that, The length of the PTW and / or the length of the T3324 timer are configured to be the length of the coverage area of ​​the serving satellite, while the T eDRX,H The length of the timer and / or the length of the T3512 timer is configured to be the length of the covered interval plus the length of the non-covered interval.

53. The wireless communication method performed by a base station according to claim 30, characterized in that, The non-coverage interval is configured as the service start time of the next satellite minus the service stop time of the serving satellite.

54. The wireless communication method performed by a base station according to claim 30, characterized in that, The registration request message is used to determine the PTW and T of the eDRX. eDRX,H The value of the timer, and / or the values ​​of the T3324 and T3512 timers in the MICO mode are determined.

55. The wireless communication method performed by a base station according to claim 30, characterized in that, The release reason includes an offset value for one or more configurations of the eDRX and / or the MICO mode, and the offset value is used to wake up the UE during the coverage interval of the discontinuous coverage scenario to monitor the paging.

56. The wireless communication method performed by a base station according to claim 30, characterized in that, The offset value is the updated UE identity identifier.

57. The wireless communication method performed by a base station according to claim 56, characterized in that, The updated UE identity identifier is the modified International Mobile Subscriber Identity (IMSI) when the UE registers with the Evolved Packet Core (EPC), or the modified 5G Globally Unique Temporary Identifier (5G-GUTI) when the UE registers with the 5G Core Network (5GC).

58. The wireless communication method performed by a base station according to claim 30, characterized in that, The modified IMSI or 5G-GUTI is related to the start time of the paging superframe PH, PTW and / or the end time of the PTW.

59. A user equipment (UE), characterized in that, include: The actuator is configured to: when the UE is in a discontinuous coverage scenario in which coverage areas and non-coverage areas alternate, execute a power-saving mechanism, wherein in the power-saving mechanism, the UE remains in a sleep state or in a mobile terminal-only connection-initiated (MICO) mode during the non-coverage area of ​​the discontinuous coverage scenario, and is configured to wake up during the coverage area of ​​the discontinuous coverage scenario to monitor paging. The non-coverage area is configured based on the service stop time of the serving satellite and / or the service start time of the next satellite, and the service stop time of the serving satellite and / or the service start time of the next satellite are determined based on information from the satellite.

60. A base station, characterized in that, include: The transmitter is configured to transmit information to a user equipment (UE) in a discontinuous coverage scenario, the discontinuous coverage scenario including the alternation of coverage intervals and non-coverage intervals, such that the UE remains in a sleep state or in a mobile terminal-only connection-initiated (MICO) mode during the non-coverage intervals of the discontinuous scenario, and wakes up during the coverage intervals to monitor paging. The non-coverage area is configured based on the service stop time of the serving satellite and / or the service start time of the next satellite, and the service stop time of the serving satellite and / or the service start time of the next satellite are determined based on information from the base station.

61. A user equipment (UE), characterized in that, include: Memory; transceiver; A processor connected to the memory and the transceiver; The processor is configured to perform any of the methods of claims 1 to 29.

62. A base station, characterized in that, include: Memory; transceiver; A processor connected to the memory and the transceiver; The processor is configured to perform any of the methods of claims 30 to 58.

63. A non-transitory machine-readable storage medium, characterized in that, The computer stores instructions that, when executed, will perform any of the methods of claims 1 to 58.

64. A chip, characterized in that, include: The processor is configured to invoke and run a computer program stored in memory, such that the device on which the chip is mounted performs any of the methods of claims 1 to 58.

65. A computer-readable storage medium, characterized in that, The computer program is stored thereon, which causes the computer to perform any of the methods of claims 1 to 58.

66. A computer program product, characterized in that, Includes a computer program that causes a computer to perform any of the methods of claims 1 to 58.

67. A computer program, characterized in that, The computer program causes the computer to perform any of the methods of claims 1 to 58.

Images