Network registration method, terminal, and network element

Abstract

Disclosed in the embodiments of the present disclosure are a network registration method, a terminal, and a network element, which can be applied to the technical field of communications. The method, which is executed by a terminal device, comprises: first, sending a registration request to a network element; then, receiving a registration rejection message sent by the network element; and then, according to the registration rejection message, stopping the sending of the registration request to the network element within a target time period. Therefore, a terminal device can determine a start time of an unavailable time period of a network on the basis of a registration rejection message, and stop the sending of a registration request within a target time period, thereby reducing signaling overheads and the amount of energy consumed.

Description

Network registration method, terminal and network element Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a network registration method, a terminal, and a network element. Background Art

[0002] Related communication systems support terminal devices, such as user equipment (UE), accessing the network via satellite. If satellite access is used to provide network services to UEs, satellite access may be affected by factors such as satellite beam coverage and the insufficient number of satellites in Starlink. As a result, the signal coverage provided to the ground may be discontinuous. In other words, when a UE accesses the network via satellite in a certain area, there may be a specific period of time when there is no satellite signal coverage.

[0003] Summary of the Invention

[0004] The disclosed embodiments provide a network registration method, terminal, and network element, which, to a certain extent, address the issue of a terminal device being unable to complete a registration update request when it is unaware of the start time of an unavailable period. First, the terminal device sends a registration request to the network element, then receives a registration rejection message from the network element. Based on the registration rejection message, the terminal device determines the start time of the network unavailable period and stops sending registration requests to the network element during the target period, thus reducing signaling overhead and energy consumption.

[0005] In a first aspect, an embodiment of the present disclosure provides a network registration method, which is performed by a terminal device. The method includes: sending a registration request to a network element, wherein the registration request is used to indicate that the terminal device will lose network coverage;

[0006] Receiving a registration rejection message sent by the network element, wherein the registration rejection message is used to indicate that the terminal device cannot complete the mobility registration update process triggered by the registration request within the remaining network coverage time;

[0007] According to the registration rejection message, it is determined to stop sending the registration request to the network element within a target time period.

[0008] In a second aspect, an embodiment of the present disclosure provides another network registration method, which is performed by a network element. The method includes: receiving a registration request sent by a terminal device, wherein the registration request is used to indicate that the terminal device will lose network coverage;

[0009] Determining that the remaining network coverage duration of the terminal device is less than the duration required for the mobility registration update process triggered by the registration request;

[0010] A registration rejection message is sent to the terminal device, wherein the registration rejection message is used to indicate that the terminal device cannot complete the mobility registration update process within the remaining network coverage time.

[0011] In a third aspect, another network registration method according to an embodiment of the present disclosure is performed by a communication system, and the method includes:

[0012] The terminal device sends a registration request to the network element, wherein the registration request is used to indicate that the terminal device will lose network coverage;

[0013] The network element determines that the remaining network coverage time of the terminal device is less than the time required to complete the mobility registration update process triggered by the registration request;

[0014] The network element sends a registration rejection message to the terminal device, wherein the registration rejection message is used to indicate that the terminal device cannot complete the mobility registration update process within the remaining network coverage time;

[0015] The terminal device determines, based on the registration rejection message, to stop sending the registration request to the network element within a target time period.

[0016] In a fourth aspect, an embodiment of the present disclosure provides a communication device that implements some or all of the functions of the terminal device described in the method described in the first aspect above. For example, the functions of the communication device may include the functions of some or all of the embodiments of the present disclosure, or may include the functions of implementing any one of the embodiments of the present disclosure separately. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0017] In one implementation, the communication device may include a transceiver module and a processing module, wherein the processing module is configured to support the communication device in performing corresponding functions in the above method. The transceiver module is used to support communication between the communication device and other devices.

[0018] The communication device may further include a storage module, which is coupled to the transceiver module and the processing module and stores computer programs and data necessary for the communication device.

[0019] In one implementation, the communication device includes:

[0020] a transceiver module, configured to send a registration request to a network element, wherein the registration request is used to indicate that the terminal device will lose network coverage;

[0021] The transceiver module is further configured to receive a registration rejection message sent by the network element, wherein the registration rejection message is used to indicate that the terminal device cannot complete the mobility registration update process triggered by the registration request within the remaining network coverage time;

[0022] A processing module is used to determine, according to the registration rejection message, to stop sending the registration request to the network element within a target time period.

[0023] In a fifth aspect, an embodiment of the present disclosure provides another communication device, which has some or all of the functions of the network element in the method example described in the second aspect above. For example, the functions of the communication device may have some or all of the functions in the embodiments of the present disclosure, or may have the functions of implementing any one of the embodiments of the present disclosure separately. The functions may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0024] In one implementation, the communication device may include a transceiver module and a processing module, the processing module being configured to support the communication device in performing the corresponding functions of the above-described method. The transceiver module is configured to support communication between the communication device and other devices. The communication device may also include a storage module, coupled to the transceiver module and the processing module, which stores computer programs and data necessary for the communication device.

[0025] In one implementation, the communication device includes:

[0026] a transceiver module, configured to receive a registration request sent by a terminal device, wherein the registration request is used to indicate that the terminal device will lose network coverage;

[0027] A processing module, configured to determine that the remaining network coverage time of the terminal device is less than the time required to complete the mobility registration update process triggered by the registration request;

[0028] The transceiver module is further used to send a registration rejection message to the terminal device, wherein the registration rejection message is used to indicate that the terminal device cannot complete the mobility registration update process within the remaining network coverage time.

[0029] In a sixth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor. When the processor calls a computer program in a memory, the method described in the first aspect is executed.

[0030] In a seventh aspect, an embodiment of the present disclosure provides a communication device, which includes a processor. When the processor calls a computer program in a memory, it executes the method described in the second aspect above.

[0031] In an eighth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in the first aspect above.

[0032] In the ninth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in the second aspect above.

[0033] In a tenth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the first aspect above.

[0034] In the eleventh aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the second aspect above.

[0035] In aspect 12, an embodiment of the present disclosure provides a communication system, which includes the communication device described in aspects 3 to 4, or the system includes the communication device described in aspects 5 to 6, or the system includes the communication device described in aspects 7 to 8, or the system includes the communication device described in aspects 9 to 10.

[0036] In a thirteenth aspect, an embodiment of the present invention provides a computer-readable storage medium for storing instructions for the above-mentioned terminal device, and when the instructions are executed, the receiving end executes the method described in the first aspect.

[0037] In a fourteenth aspect, an embodiment of the present invention provides a readable storage medium for storing instructions used by the above-mentioned network element. When the instructions are executed, the transmitting end executes the method described in the above-mentioned second aspect.

[0038] In a fifteenth aspect, the present disclosure further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect above.

[0039] In a sixteenth aspect, the present disclosure further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the second aspect above.

[0040] In a seventeenth aspect, the present disclosure provides a chip system comprising at least one processor and an interface for supporting a terminal device in implementing the functions described in the first aspect, such as determining or processing at least one of the data and information described in the above method. In one possible design, the chip system further comprises a memory for storing computer programs and data necessary for the terminal device. The chip system may consist of a chip alone or may include a chip and other discrete components.

[0041] In aspect 18, the present disclosure provides a chip system comprising at least one processor and an interface for supporting a network element in implementing the functions described in aspect 2, such as determining or processing at least one of the data and information described in the aforementioned method. In one possible design, the chip system further comprises a memory for storing computer programs and data necessary for the network element. The chip system may consist of a chip alone or may include a chip and other discrete components.

[0042] In a nineteenth aspect, the present disclosure provides a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect above.

[0043] In a twentieth aspect, the present disclosure provides a computer program which, when executed on a computer, enables the computer to execute the method described in the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the background technology, the drawings required for use in the embodiments of the present disclosure or the background technology will be described below.

[0045] FIG1 is a schematic diagram of the architecture of a communication system provided by the present disclosure;

[0046] FIG2 is a flow chart of a network registration method provided by an embodiment of the present disclosure;

[0047] FIG3 is a flow chart of a network registration method provided by an embodiment of the present disclosure;

[0048] FIG4 is a flow chart of another network registration method provided by an embodiment of the present disclosure;

[0049] FIG5 is a flow chart of another network registration method provided by an embodiment of the present disclosure;

[0050] FIG6 is an interaction diagram of another network registration method provided by an embodiment of the present disclosure;

[0051] FIG7 is an interactive diagram of another network registration method provided by an embodiment of the present disclosure;

[0052] FIG8 is a structural diagram of a communication device provided by an embodiment of the present disclosure;

[0053] FIG9 is a structural diagram of another communication device provided in an embodiment of the present disclosure;

[0054] FIG10 is a schematic structural diagram of a chip provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0055] To facilitate understanding of the technical solutions of the present disclosure, some terms involved in the embodiments of the present disclosure are briefly introduced below.

[0056] Access and Mobility Management Function (AMF) network element, AMF is a logical node functional network element on the core network side. It is the access point for the terminal and wireless core network control plane. It receives all connection and session related information from the user equipment and performs registration, connection, reachability, and mobility management. In addition, AMF provides a session management message transmission channel for terminal devices and session management function (SMF) devices, and provides authentication and authorization functions for user access.

[0057] In order to better understand the network registration method and apparatus disclosed in the embodiments of the present disclosure, the communication system to which the embodiments of the present disclosure are applicable is first described below.

[0058] Please refer to Figure 1, which is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure. The communication system may include, but is not limited to, an access network device, a terminal device, and a core network device. The number and form of devices shown in Figure 1 are for example only and do not constitute a limitation on the embodiments of the present disclosure. In actual applications, two or more access network devices, two or more core network devices, and two or more terminal devices may be included. The communication system shown in Figure 1 includes a terminal 101, an access network device (satellite) 102, and a core network device (network element) 103.

[0059] It should be noted that the technical solutions of the embodiments of the present disclosure can be applied to various communication systems, such as long-term evolution (LTE) systems, fifth-generation (5G) mobile communication systems, 5G new radio (NR) systems, or other future new mobile communication systems.

[0060] The terminal 101 in the embodiment of the present disclosure may be a device that provides voice / data connectivity to a user, for example, a handheld device or a vehicle-mounted device with a wireless connection function. Some examples of terminal devices include: mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5G networks or future evolved public land mobile communication networks (PLMNs). The present invention relates to a terminal device in a wireless communication system (PLMN) and / or any other suitable device for communicating on a wireless communication system, and the embodiments of the present disclosure are not limited thereto.

[0061] Wearable devices, also known as wearable smart devices, are a general term for wearable devices developed by applying wearable technology to intelligently design everyday wearables, such as glasses, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include those that are fully functional, large in size, and can achieve full or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0062] In addition, in the embodiment of the present disclosure, the terminal 101 can also be a terminal device in the Internet of Things system. The IoT (Internet of Things) is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection.

[0063] In addition, in the embodiment of the present disclosure, the terminal 101 may also include sensors such as smart printers, train detectors, and gas stations. Its main functions include collecting data (part of the terminal equipment), receiving control information and downlink data from the network side equipment, and sending electromagnetic waves to transmit uplink data to the network side equipment.

[0064] In some embodiments, the access network device 102 is, for example, a node or device that connects a terminal to a wireless network, such as a satellite. The access network device may include at least one of an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home nodeB (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open RAN, a cloud RAN, a base station in other communication systems, and an access node in a Wi-Fi system, but is not limited thereto.

[0065] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0066] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0067] In some embodiments, the core network device 103 may be a single device, including a network element 1031, or may be multiple devices or a device group, including all or part of multiple network elements 1031. The network element may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0068] In some embodiments, network element 1031 is, for example, an AMF network element.

[0069] In the embodiment of the present disclosure, the UE accesses the network via a satellite, so the access network device in the embodiment of the present disclosure is a satellite. All communications between the UE and the AMF network element on the core network side need to be forwarded by the satellite. For example, when the UE determines that it will lose network coverage, it sends a registration request message to the AMF network element via satellite. After that, when the AMF network element determines that the remaining coverage time of the UE is insufficient to complete the registration update process based on the satellite coverage information and the UE's location information, it sends a registration rejection message to the UE via satellite.

[0070] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

[0071] In addition, in order to facilitate understanding of the embodiments of the present disclosure, the following points are explained.

[0072] First, the first, second, and various numbers in this disclosure are only used for the convenience of description and are not intended to limit the scope of the embodiments of this disclosure, for example, to distinguish different information, different terminal devices, etc.

[0073] Second, the "protocol" involved in the embodiments of the present disclosure may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, a NR protocol, and related protocols used in future communication systems, and the present disclosure does not limit this.

[0074] Third, the embodiments of the present disclosure list multiple implementation methods to clearly illustrate the technical solutions of the embodiments of the present disclosure. Of course, those skilled in the art will understand that the multiple embodiments provided in the embodiments of the present disclosure can be implemented individually, combined with the methods of other embodiments of the embodiments of the present disclosure, or implemented individually or in combination with some methods in other related technologies; the embodiments of the present disclosure are not limited to this.

[0075] The disclosed embodiments provide a network registration method. First, a terminal device sends a registration request to a network element. Then, upon receiving the registration request, the network element sends a registration rejection message to the terminal device if it determines that the remaining network coverage time of the terminal device is less than the time required to complete the mobility registration update process triggered by the registration request. The terminal device, based on the registration rejection message, determines to stop sending registration requests to the network element within a target time period. Thus, the terminal device can determine the start time of the network unavailable period based on the registration rejection message and stop sending registration requests within the target time period, thereby saving signaling overhead and energy consumption.

[0076] The following is a detailed introduction to a network registration method provided by the present disclosure with reference to the accompanying drawings.

[0077] Please refer to Figure 2, which is a flow chart of a network registration method provided by an embodiment of the present disclosure. As shown in Figure 2, the method is applied to a terminal and may include but is not limited to the following steps:

[0078] Step 201: Send a registration request to a network element, where the registration request is used to indicate that the terminal device will lose network coverage.

[0079] In the present disclosure, a terminal device may send a registration request to a network element via any message, such as a Radio Resource Control (RRC) message or an Uplink Control Information (DCI) message, which is not limited in the present disclosure.

[0080] Among them, the network element can be a network element on the core network side used to manage the access and mobility of terminal equipment, such as the Access and Mobility Management Function (AMF) network element in the 5G system.

[0081] In some possible implementations, when the terminal device determines that it will lose network coverage, it sends a registration request to the network element via a satellite. That is, the terminal device sends the registration request to the network element based on the satellite link between the terminal device and the network element.

[0082] In some possible implementations, the registration request may include an information field for indicating that the terminal device will lose network coverage. That is, the terminal device explicitly indicates that it will lose network coverage through the information field in the registration request;

[0083] In some possible implementation forms, the registration request may not include an information field for indicating that the terminal device will lose network coverage, but the registration request may implicitly indicate that the terminal will lose network coverage.

[0084] In some possible implementation forms, the registration request sent by the terminal device to the network element may include a first time period, wherein the first time period is a time period determined by the terminal device to be without network coverage.

[0085] In some possible implementation forms, the first time period may be determined by the terminal device based on the first satellite network coverage related information and the first location information of the terminal device.

[0086] Among them, the first satellite network coverage related information may include the satellite's operating time, position, deflection, beam and other operating information, which is not limited in this disclosure.

[0087] It should be noted that if the terminal device determines the first time period, the registration request may or may not include the first time period; if the terminal device cannot determine the first time period, the registration request does not include the first time period.

[0088] In the present disclosure, the terminal device accesses the network by using a satellite, but the satellite access may be affected by the satellite beam coverage and the insufficient number of satellites in the Starlink, resulting in the signal provided by the satellite to the ground may be discontinuous coverage, that is, when the terminal device accesses the network via a satellite in a certain area, there may be no satellite signal coverage within a certain period of time. Therefore, the terminal device can send a registration request to the network element when it determines that it will lose network coverage.

[0089] Step 202: Receive a registration rejection message sent by a network element, wherein the registration rejection message is used to indicate that the terminal device cannot complete the mobility registration update process triggered by the registration request within the remaining network coverage time.

[0090] In the present disclosure, after a terminal device sends a registration request to a network element, the network element may determine the remaining network coverage duration of the terminal device based on information related to satellite network coverage and the location information of the terminal device. When the network element determines that the remaining network coverage duration is less than the duration required to complete the mobility registration update process, it may determine that the terminal device cannot complete the mobility registration update process within the remaining network coverage duration, and thus send a registration rejection message to the terminal device.

[0091] In some possible implementation forms, the terminal device receives the registration rejection message sent by the network element via a satellite.

[0092] In some possible implementation forms, the remaining network coverage time is determined by the network element according to the satellite network coverage information and the location information of the terminal device.

[0093] In some possible implementation forms, the registration rejection message may further include a second time period, wherein the second time period is a time period during which the terminal device has no network coverage, as determined by the network element.

[0094] In some possible implementations, the first information field in the registration rejection message includes a rejection reason value. The rejection reason value can be used to indicate that the remaining network coverage time of the terminal device is insufficient to complete the mobility registration update process triggered by the registration request.

[0095] In other words, the rejection reason value can be used to indicate the reason why the network element rejected the registration request. For example, it can be used to indicate the reason why the terminal device cannot complete the mobility registration update process triggered by the registration request within the remaining network coverage time by taking a specific value, or it can be indicated by other implementation forms, which are not limited by this disclosure.

[0096] It should be noted that after the terminal device receives the registration rejection message sent by the network element, if it finds that the first information field in the registration rejection message contains a rejection reason value, it can be determined that the reason for the registration rejection is that the mobility registration update process cannot be completed within the remaining network coverage time.

[0097] Step 203: According to the registration rejection message, it is determined to stop sending registration requests to the network element within the target period.

[0098] In some possible implementation forms, the terminal device determines the first time period or the second time period as the target time period, wherein the first time period is the time period determined by the terminal device to have no network coverage, and the second time period is the time period determined by the network element to have no network coverage for the terminal device.

[0099] In some possible implementation forms, the time periods of the first period and the second period are the same or different.

[0100] It should be noted that when the terminal device calculates the first time period, it is based on the terminal device's own location and information related to satellite network coverage. When the network element calculates the second time period based on the terminal's location information, the accuracy of the terminal device's location obtained may be different from the accuracy determined by the terminal device itself, or the network element may calculate the second time period based on the location of the cell to which the terminal device belongs and information related to satellite coverage. Therefore, the calculated second time period may be different from the first time period.

[0101] In some possible implementations, if the terminal device determines the first time period and the received registration rejection message does not include the second time period, the terminal device determines the first time period as the target time period and stops sending registration requests to the network element during the first time period.

[0102] In some possible implementations, if the terminal device determines the first time period and the received registration reject message includes the second time period, the terminal device determines the first time period or the second time period as the target time period. For example, the terminal device determines the first time period as the target time period, or determines the second time period as the target time period, and stops sending registration requests to the network element during the target time period.

[0103] In some possible implementations, if the terminal device cannot determine the first time period and the received registration rejection message includes the second time period, the terminal device determines the second time period as the target time period and stops sending registration requests to the network element during the second time period.

[0104] In some possible implementation forms, after the AMF receives the registration request, if it is determined that the registration request does not contain information related to the first time period (e.g., UPD-A), the determined second time period (e.g., UPD-B) information will be added to the registration rejection message and sent to the terminal device.

[0105] In some possible implementation forms, the terminal device may determine the time when the registration rejection message is received as the start time of the unavailable period.

[0106] In some possible implementation forms, the terminal device may also delay the time of receiving the registration rejection message by a certain time unit (such as a time slot, a subframe, etc.) to determine it as the start time of the unavailable period.

[0107] In some possible implementations, the terminal device may further determine a time before the time the registration reject message is received as the start time of the unavailable period. For example, the time unit before the registration reject message is received may be determined as the start time of the unavailable period, and the present disclosure is not limited thereto. The time unit may be a time slot, a frame, a subframe, and the like, and the present disclosure is not limited thereto.

[0108] In summary, the terminal device first sends a registration request to the network element, then receives a registration reject message from the network element. Based on the registration reject message, the terminal device determines to stop sending registration requests to the network element within a target period. This allows the terminal device to determine the start time of the network unavailable period based on the registration reject message and stop sending registration requests during the target period, thereby saving energy.

[0109] Please refer to Figure 3, which is a flow chart of a network registration method provided by an embodiment of the present disclosure. As shown in Figure 3, the method is applied to a terminal device and may include but is not limited to the following steps:

[0110] Step 301: Send a first registration request to a network element, where the first registration request is used to indicate that the terminal device will lose network coverage.

[0111] Step 302: Receive a registration rejection message sent by a network element, wherein the registration rejection message is used to indicate that the terminal device cannot complete the mobility registration update process triggered by the registration request within the remaining network coverage time.

[0112] Step 303: According to the registration rejection message, it is determined to stop sending registration requests to the network element within the target period.

[0113] The specific implementation of the above steps 301 to 303 can refer to the detailed description of other embodiments of the present disclosure and will not be repeated here.

[0114] Step 304: Determine that the target period ends, and send a second registration request to the network element.

[0115] In the present disclosure, when the target period ends, the terminal device can send a registration request to the network element again to trigger the mobility registration update process to re-access the network via the satellite.

[0116] In summary, when a terminal device determines that it will lose network coverage, it first sends a first registration request to the network element, then receives a registration rejection message from the network element. It then stops sending second registration requests to the network element within a target time period, and finally sends registration requests to the network element again after the target time period ends. Thus, the terminal device can obtain the target time period from the network element, stop sending registration requests during the target time period, and send registration requests again after the target time period ends, thereby saving energy consumption.

[0117] Please refer to Figure 4, which is a flow chart of a network registration method provided by an embodiment of the present disclosure. As shown in Figure 4, the method is applied to a network element and may include but is not limited to the following steps:

[0118] Step 401: Receive a registration request sent by a terminal device, wherein the registration request is used to indicate that the terminal device will lose network coverage.

[0119] In the present disclosure, the network element can receive the registration request sent by the terminal device through any message, such as receiving the registration request through the radio resource control message (Radio Sesource Control, RRC), or receiving the registration request through the uplink control information (Uplink Control Information, DCI), etc., and the present disclosure does not limit this.

[0120] Among them, the network element can be a network element on the core network side used to manage the access and mobility of terminal equipment, such as the Access and Mobility Management Function (AMF) network element in the 5G system.

[0121] In some possible implementation forms, the network element receives the registration request sent by the terminal device via a satellite. That is, the network element receives the registration request sent by the terminal device based on a satellite link between the network element and the terminal device.

[0122] In some possible implementation forms, the registration request sent by the terminal device received by the network element includes a first time period, wherein the first time period is a time period determined by the terminal device to have no network coverage, and the time period of the first time period is the same as or different from the time period of the second time period.

[0123] It should be noted that when the terminal device calculates the first time period, it is based on the terminal device's own location and information related to satellite network coverage. When the network element calculates the second time period based on the terminal's location information, the accuracy of the terminal device's location obtained may be different from the accuracy determined by the terminal device itself, or the network element may calculate the second time period based on the location of the cell to which the terminal device belongs and information related to satellite coverage. Therefore, the calculated second time period may be different from the first time period.

[0124] Among them, the network coverage is satellite network coverage, the first time period is the time period without network coverage determined by the terminal device based on the first satellite network coverage information obtained and the first location information of the terminal device, and the second time period is the time period without network coverage determined by the network element based on the second satellite network coverage information obtained by the network element and the second location information of the terminal device.

[0125] Among them, the satellite network coverage information may include the satellite's operating time, position, deflection, beam and other operating information, which is not limited in this disclosure.

[0126] It should be noted that if the registration request includes the first time period, it means that the terminal device has determined the first time period; if the registration request does not include the first time period, it means that the terminal device itself may not be able to determine the time period when the network has no coverage.

[0127] In the present disclosure, the terminal device accesses the network by using a satellite, but the satellite access may be affected by the satellite beam coverage and the insufficient number of satellites in the Starlink, resulting in the signal provided by the satellite to the ground may be discontinuous coverage, that is, when the terminal device accesses the network via a satellite in a certain area, there may be no satellite signal coverage within a certain period of time. Therefore, when the network element receives the registration request sent by the terminal device, it can determine that the terminal device has determined that it will lose network coverage.

[0128] Step 402: Determine whether the remaining network coverage time of the terminal device is less than the time required for the mobility registration update process triggered by the registration request.

[0129] In some possible implementations, after receiving the registration request, the network element can determine the starting time and / or the second time period of the terminal device without network coverage based on the satellite network coverage information and the location information of the terminal device, wherein the second time period is the time period of the terminal device without network coverage determined by the network element.

[0130] In some possible implementation forms, the network element may determine the remaining network coverage duration of the terminal device based on the difference between the determined start time of no network coverage for the terminal device and the time when the registration request is received.

[0131] In some possible implementation forms, the duration required for the mobility registration update process may be agreed upon by a protocol, or determined by a network element based on a current network state, which is not limited in this disclosure.

[0132] Among them, the satellite network coverage information may include the satellite's operating time, position, deflection, beam and other operating information, which is not limited in this disclosure.

[0133] In some possible implementations, the first information field in the registration rejection message includes a rejection reason value. The rejection reason value can be used by the network element to indicate that the remaining network coverage time of the terminal device is insufficient to complete the mobility registration update process triggered by the registration request.

[0134] The rejection reason value may be used by the network element to indicate to the terminal device the reason for rejecting the registration request. For example, a specific value may be used to indicate the reason why the terminal device cannot complete the mobility registration update process triggered by the registration request within the remaining network coverage time. Other implementations may also be used, which are not limited in this disclosure.

[0135] It should be noted that, after the network element determines that the terminal device cannot complete the mobility registration update process within the remaining network coverage time, it can set the rejection reason value in the first information field in the registration rejection message.

[0136] Step 403: Send a registration rejection message to the terminal device, wherein the registration rejection message is used to indicate that the terminal device cannot complete the mobility registration update process within the remaining network coverage time.

[0137] In some possible implementation forms, the network element sends a registration rejection message to the terminal device via a satellite.

[0138] In some possible implementation forms, the registration rejection message includes a second time period, where the second time period is the same as or different from the first time period.

[0139] Among them, the first time period is a time period determined by the terminal device to have no network coverage, and the second time period is a time period determined by the network element to have no network coverage for the terminal device.

[0140] In some possible implementation forms, when the network element determines that the terminal device cannot complete the mobility registration update process within the target time period, it may determine that the terminal device stops sending registration requests within the target time period.

[0141] The target time period may be the first time period or the second time period, which is not limited in the present disclosure.

[0142] In the present disclosure, when the network element determines that the terminal device cannot complete the mobility registration update process triggered by the registration request within the remaining network coverage time, the network element will send a registration rejection message to the terminal device.

[0143] In summary, after receiving the registration request sent by the terminal device, the network element sends a registration rejection message to the terminal device if it determines that the terminal device cannot complete the mobility registration update process triggered by the registration request within the remaining network coverage time. Thus, the network element uses the registration rejection message to indicate to the terminal device that the mobility registration update process triggered by the registration request cannot be completed within the remaining network coverage time, thereby enabling the terminal device to determine the start time of the network unavailable period, providing conditions for reducing energy consumption of the terminal device and the network element.

[0144] Please refer to Figure 5, which is a flow chart of another network registration method provided by an embodiment of the present disclosure. As shown in Figure 5, the method is applied to a network element, and the method may include but is not limited to the following steps:

[0145] Step 501: Receive a registration request sent by a terminal device, wherein the registration request is used to indicate that the terminal device will lose network coverage.

[0146] The specific implementation of step 501 can refer to the detailed description of other embodiments of the present disclosure and will not be repeated here.

[0147] Step 502: Determine the remaining network coverage duration of the terminal device according to the start time of the terminal device being without network coverage.

[0148] In the present disclosure, after receiving the registration request sent by the terminal device, the network element determines the start time of the terminal device's lack of network coverage based on the satellite network coverage information and the area where the terminal device is currently located, and calculates the remaining network coverage time of the terminal device.

[0149] Step 503: Determine whether the terminal device can complete the mobility registration update process within the remaining network coverage time according to the remaining network coverage time of the terminal device and the time required for the mobility registration update process.

[0150] In the present disclosure, the network element compares the remaining network coverage time of the terminal device and the time required to complete the mobility registration update process. If the remaining network coverage time of the terminal device is less than the time required to complete the mobility registration update process, the network element can determine that the terminal device cannot complete the mobility registration update process within the remaining network coverage time.

[0151] In some possible implementations, if the remaining network coverage time of the terminal device is greater than or equal to the time required to complete the mobility registration update process, the network element can determine that the terminal device can complete the mobility registration update process within the remaining network coverage time, and thus can allow the terminal device to perform the mobility registration update.

[0152] Step 504: In response to determining that the terminal device cannot complete the mobility registration update process within the remaining network coverage time, a registration rejection message is returned to the terminal device.

[0153] In some possible implementations, the registration rejection message includes a second time period, wherein the second time period is the same as or different from the first time period, the first time period is a time period when the terminal device determines that there is no network coverage, and the second time period is a time period when the terminal device determines that there is no network coverage.

[0154] In some possible implementations, the network element may include the second time period in a registration reject message in response to the registration request not including the first time period. In other words, the network element believes that the terminal device may not be able to determine the network unavailable period, and thus indicates the second time period to the terminal device through the registration reject message.

[0155] It should be noted that if the first time period cannot be determined by the terminal device, the registration request sent by the terminal device received by the network element does not include the first time period. At this time, the network element can carry the second time period in the registration rejection message and send it to the terminal device.

[0156] In some possible implementation forms, the network element may further include the second time period in the registration rejection message in response to the registration request including the first time period, and the first time period being different from the second time period.

[0157] It should be noted that if the registration request sent by the terminal device received by the network element contains a first time period (that is, the terminal device itself determines a time period when the network is unavailable), the network element will compare the first time period and the second time period. If the two are different, the network element can include the second time period in the registration rejection message and send it to the terminal device.

[0158] In summary, after receiving the registration request sent by the terminal device, the network element can determine the remaining network coverage time of the terminal device based on the start time of the terminal device's lack of network coverage, and then determine whether the terminal device can complete the mobility registration update process within the remaining network coverage time based on the remaining network coverage time of the terminal device and the time required for the mobility registration update process. Finally, if it is determined that the terminal device cannot complete the mobility registration update process within the remaining network coverage time, the network element returns a registration rejection message to the terminal device. Thus, the network element indicates to the terminal device through the registration rejection message that the terminal device cannot complete the mobility registration update process within the remaining network coverage time, so that the terminal device can stop sending registration requests during the period of network unavailability, thereby providing conditions for energy consumption of the terminal device and the network element.

[0159] Please refer to Figure 6, which is an interactive diagram of a network registration method provided by an embodiment of the present disclosure. As shown in Figure 6, the method may include but is not limited to the following steps:

[0160] Step 601: The terminal device sends a registration request to a network element, where the registration request is used to indicate that the terminal device will lose network coverage.

[0161] In some possible implementation forms, the registration request may include the first network unavailable period.

[0162] Step 602: The network element determines whether the terminal device can complete the mobility registration update process triggered by the registration request within the remaining network coverage time.

[0163] Step 603: The network element determines that the remaining network coverage time of the terminal device is less than the time required for the mobility registration update process triggered by the registration request.

[0164] Step 604: The network element sends a registration rejection message to the terminal device, wherein the registration rejection message is used to indicate that the terminal device cannot complete the mobility registration update process within the remaining network coverage time.

[0165] In some possible implementations, the registration rejection message may include the second time period.

[0166] Step 605: The terminal device determines to stop sending registration requests to the network element within the target time period based on the registration rejection message.

[0167] In summary, through simple interaction between the terminal device and the network element, the terminal device can obtain the start time and duration of the unavailable period from the network element, so that the terminal device stops sending registration requests during the unavailable period, saving energy consumption.

[0168] The following is an exemplary introduction to the above method.

[0169] The present disclosure is used to solve the problem that a terminal device cannot complete a registration update request when it does not know the start time of the unavailable period. As shown in FIG7 , FIG7 is an interactive diagram of a network registration method provided by an embodiment of the present disclosure. Optional implementation solutions are as follows:

[0170] When the AMF receives a Registration Request indicating that the UE is about to lose coverage and does not provide the start time of the Unavailable Period, if the AMF is able to determine that the remaining coverage time before the loss of coverage is insufficient to complete the Mobile Registration Update procedure, it rejects the procedure with an indication of the Registration Update Reject Cause. Optionally, if the duration of the Unavailable Period known to the AMF is different from the Unavailable Period duration generated by the UE, the duration of the Unavailable Period is provided. After sending the Registration Reject message, the AMF shall consider the UE unreachable.

[0171] Based on the registration reject reason, provided by the AMF, the UE shall abort the registration update procedure for the duration of the unavailable period or for the duration of the unavailable period generated by the UE. After the unavailable period duration expires, the UE may re-initiate the registration update procedure. The interaction process is as follows:

[0172] 1. The UE determines that it will leave the network coverage.

[0173] For NR satellite access that provides discontinuous network coverage, if both the UE and the network support discontinuous coverage, the UE can trigger the mobility registration update procedure when the UE is about to lose coverage.

[0174] 2. Send a registration request to AMF.

[0175] If the UE can determine that it is about to leave coverage but cannot determine the start time of the unavailable period, the UE sends a registration request to the AMF, which indicates the upcoming unavailability due to discontinuous coverage and may include the unavailable period duration (UPD-A).

[0176] 3. When the AMF receives the Registration Request, it determines the duration of the unavailable period for the UE (UPD-B) based on the satellite coverage information. If the AMF determines that the remaining coverage time is insufficient to complete the Registration Update procedure, the AMF determines to reject the Registration Update procedure.

[0177] 4.AMF sends a REGISTRATION REJECT message to the UE, which shall include a cause value.

[0178] Optionally, if the UPD-B determined by the AMF is different from the UPD-A, or the UE does not provide the UPD-A, the UPD-B shall also be included in the Registration Reject message. The cause value is used to indicate that the registration update is rejected because the remaining coverage time is insufficient to complete the registration update process or other equivalent information. After sending the message, the AMF shall consider the UE to be unreachable.

[0179] 5. The UE shall terminate initiating the Registration Update procedure during the duration of the Unavailable Period generated by the UE or indicated by the AMF.

[0180] 6. When the unavailable period duration expires, the UE may initiate the mobility registration update procedure again.

[0181] Please refer to Figure 8, which is a schematic diagram of the structure of a communication device provided in an embodiment of the present disclosure. The communication device 800 shown in Figure 8 includes a transceiver module 801 and a processing module 802. The transceiver module may include a sending module and / or a receiving module. The sending module is used to implement the sending function, and the receiving module is used to implement the receiving function. The transceiver module can implement the sending function and / or the receiving function.

[0182] The communication device 800 may be a terminal, a device in a terminal, or a device that can be used in conjunction with a terminal.

[0183] The communication device 800 is on the terminal device side, wherein:

[0184] The transceiver module 801 is configured to send a registration request to a network element, wherein the registration request is used to indicate that the terminal device will lose network coverage;

[0185] The transceiver module 801 is configured to receive a registration rejection message sent by the network element, wherein the registration rejection message is used to indicate that the terminal device cannot complete the mobility registration update process triggered by the registration request within the remaining network coverage time;

[0186] The processing module 802 is configured to determine, according to the registration rejection message, to stop sending the registration request to the network element within a target time period.

[0187] In some possible implementation forms, the processing module 802 is also used to determine the first time period or the second time period as the target time period, wherein the first time period is the time period when the terminal device determines that there is no network coverage, and the second time period is the time period when the terminal device determines that there is no network coverage.

[0188] In some possible implementation forms, the network coverage is satellite network coverage, the first time period is a time period without network coverage determined by the terminal device based on the acquired first satellite network coverage information and the first location information of the terminal device, and the second time period is a time period without network coverage determined by the network element based on the acquired second satellite network coverage information and the second location information of the terminal device.

[0189] In some possible implementation forms, the processing module 802 is further configured to determine that the first time period is not included and the registration rejection message includes the second time period;

[0190] The second time period is determined as the target time period.

[0191] In some possible implementation forms, the processing module 802 is further configured to determine that the first time period is included and the registration rejection message does not include the second time period;

[0192] The first time period is determined to be the target time period.

[0193] In some possible implementation forms, the processing module 802 is further configured to determine that the first time period is included and the registration rejection message includes the second time period;

[0194] Determine the first time period or the second time period as the target time period.

[0195] In some possible implementation forms, the time periods of the first period and the second period are the same or different.

[0196] In some possible implementation forms, the remaining network coverage duration is determined by the network element based on satellite network coverage information and location information of the terminal device.

[0197] In some possible implementation forms, the first information field in the registration rejection message includes a rejection reason value, and the rejection reason value indicates that the terminal device cannot complete the mobility registration update process triggered by the registration request within the remaining network coverage time.

[0198] In some possible implementation forms, the processing module 802 is further configured to determine that the terminal device will lose the network coverage;

[0199] In some possible implementation forms, the transceiver module 801 is further configured to send the registration request to the network element.

[0200] In some possible implementation forms, the transceiver module 801 is further configured to send the registration request to the network element, including:

[0201] sending the registration request to the network element via a satellite;

[0202] Receiving a registration rejection message sent by the network element, including:

[0203] The registration rejection message sent by the network element is received through the satellite.

[0204] In some possible implementation forms, the transceiver module 801 is further configured to determine that the target time period ends, and send a second registration request to the network element, where the second registration request is used to trigger the mobility registration update process.

[0205] In summary, the terminal device first sends a registration request to the network element, then receives a registration rejection message from the network element. During the target period, the terminal device stops sending registration requests to the network element. This allows the terminal device to obtain the start time and second period of the unavailable period from the network element and stop sending registration requests during the unavailable period, thus saving energy.

[0206] The communication device 800 may also be a core network device, a device in a core network device, or a device that can be used in conjunction with a core network device.

[0207] The communication device 800 is located at the network element side, wherein:

[0208] The transceiver module 801 is configured to receive a registration request sent by a terminal device, wherein the registration request is used to indicate that the terminal device will lose network coverage;

[0209] A processing module, configured to determine that the remaining network coverage time of the terminal device is less than the time required to complete the mobility registration update process triggered by the registration request;

[0210] The transceiver module is further used to send a registration rejection message to the terminal device, wherein the registration rejection message is used to indicate that the terminal device cannot complete the mobility registration update process within the remaining network coverage time.

[0211] In some possible implementation forms, the processing module 802 is further used to determine the starting time and / or second time period of the terminal device without network coverage, wherein the second time period is the time period of the terminal device without network coverage determined by the network element.

[0212] In some possible implementation forms, the processing module 802 is further used to determine the start time of the period without network coverage and / or the second time period based on the acquired satellite network coverage information and the location information of the terminal device.

[0213] In some possible implementation forms, the processing module 802 is further configured to determine the remaining network coverage duration of the terminal device according to the start time of the lack of network coverage of the terminal device;

[0214] According to the remaining network coverage duration of the terminal device and the duration required for the mobility registration update process, it is determined whether the terminal device can complete the mobility registration update process within the remaining network coverage duration.

[0215] In some possible implementation forms, the registration rejection message includes the second time period.

[0216] In some possible implementation forms, the registration request includes a first time period, wherein the first time period is a time period determined by the terminal device to be without network coverage, and the time period of the first time period is the same as or different from the time period of the second time period.

[0217] In some possible implementation forms, the network coverage is satellite network coverage, the first time period is a time period without network coverage determined by the terminal device based on the acquired first satellite network coverage information and the first location information of the terminal device, and the second time period is a time period without network coverage determined by the network element based on the acquired second satellite network coverage information and the second location information of the terminal device.

[0218] In some possible implementation forms, the transceiver module 801 is further configured to send a registration request to the receiving terminal device, including:

[0219] receiving the registration request sent by the terminal device via a satellite;

[0220] The sending of a registration rejection message to the terminal device includes:

[0221] The registration rejection message is sent to the terminal device via the satellite.

[0222] In some possible implementation forms, the processing module 802 is also used to include a rejection reason value in the first information field of the registration rejection message, and the rejection reason value indicates that the terminal device cannot complete the mobility registration update process triggered by the registration request within the remaining network coverage time.

[0223] In summary, after receiving a registration request from a terminal device, the network element sends a registration rejection message to the terminal device if it determines that the remaining network coverage time of the terminal device is less than the time required for the mobility registration update process triggered by the registration request. Thus, the network element can indicate to the terminal device the network unavailable period and indirectly indicate the start time of the unavailable period, so that the terminal device can stop sending registration requests during the unavailable period. The network element also considers that the terminal device is in a power-saving state during the unavailable period and will not initiate a paging process to the terminal, thereby saving energy consumption of the terminal device and the network element.

[0224] The communication device 800 provided in the above embodiments of the present disclosure achieves the same or similar beneficial effects as the perception measurement methods provided in some of the above embodiments, and will not be described in detail here.

[0225] Please refer to Figure 9, which is a schematic diagram of the structure of another communication device 900 provided in an embodiment of the present disclosure. Communication device 900 can be a terminal device, a network element, or a chip, chip system, or processor that supports the terminal device to implement the above method. It can also be a chip, chip system, or processor that supports the network element to implement the above method. Communication device 900 can be used to implement the method described in the above method embodiment. For details, please refer to the description of the above method embodiment.

[0226] The communication device 900 may include one or more processors 901. The processor 901 may be a general-purpose processor or a dedicated processor. For example, it may be a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control the communication device (e.g., network-side equipment, baseband chips, terminal equipment, terminal equipment chips, DU or CU, etc.), execute computer programs, and process computer program data.

[0227] In some possible implementations, the communication device 900 may further include one or more memories 902, on which a computer program 904 may be stored. The memories 902 execute the computer program 904, so that the communication device 900 performs the method described in the above method embodiment. In some possible implementations, the memories 902 may also store data. The communication device 900 and the memories 902 may be provided separately or integrated together.

[0228] In some possible implementations, the communication device 900 may further include a transceiver 905 and an antenna 906. The transceiver 905 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, and is configured to implement transceiver functions. The transceiver 905 may include a receiver and a transmitter. The receiver may be referred to as a receiver or a receiving circuit, and is configured to implement a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, and is configured to implement a transmitting function.

[0229] In some possible implementations, the communication device 900 may further include one or more interface circuits 07. The interface circuit 907 is configured to receive code instructions and transmit them to the processor 901. The processor 901 executes the code instructions to enable the communication device 900 to perform the method described in the above method embodiment.

[0230] In one implementation, processor 901 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and transmitting functions may be separate or integrated. The transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or may be used for transmitting or delivering signals.

[0231] In one implementation, processor 901 may store a computer program 903. Computer program 903, when executed on processor 901, enables communication device 900 to perform the method described in the above method embodiment. Computer program 903 may be embedded in processor 901, in which case processor 901 may be implemented by hardware.

[0232] In one implementation, the communication device 900 may include a circuit that can implement the functions of sending, receiving, or communicating in the aforementioned method embodiments. The processor and transceiver described in the present disclosure can be implemented on an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (nMetal-oxide-semiconductor, NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0233] The communication device described in the above embodiments may be a terminal device, but the scope of the communication device described in this disclosure is not limited thereto, and the structure of the communication device may not be limited to FIG9 . The communication device may be an independent device or may be part of a larger device. For example, the communication device may be:

[0234] (1) An independent integrated circuit (IC), or chip, or chip system or subsystem;

[0235] (2) having a set of one or more ICs, which, in some possible implementations, may also include a storage component for storing data and computer programs;

[0236] (3) ASIC, such as modem;

[0237] (4) Modules that can be embedded in other devices;

[0238] (5) Receivers, terminal devices, intelligent terminal devices, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.;

[0239] (6)Others, etc.

[0240] For the case where the communication device may be a chip or a chip system, please refer to FIG10 , which is a structural diagram of a chip provided in an embodiment of the present disclosure.

[0241] The chip 1000 includes a processor 1001 and an interface 1003. The number of the processor 1001 can be one or more, and the number of the interface 1003 can be multiple.

[0242] For the case where the chip is used to implement the functions of the terminal device in the embodiments of the present disclosure:

[0243] The interface 1003 is used to receive code instructions and transmit them to the processor.

[0244] The processor 1001 is configured to execute code instructions to perform the perception measurement method as described in some of the above embodiments.

[0245] For the case where the chip is used to implement the function of the transmitter in the embodiments of the present disclosure:

[0246] The interface 1003 is used to receive code instructions and transmit them to the processor.

[0247] The processor 1001 is configured to execute code instructions to perform the perception measurement method as described in some of the above embodiments.

[0248] In some possible implementations, the chip 1000 further includes a memory 1002 , which is used to store necessary computer programs and data.

[0249] Those skilled in the art will also appreciate that the various illustrative logical blocks and steps listed in the embodiments of the present disclosure may be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art may use various methods to implement the described functionality for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of the present disclosure.

[0250] An embodiment of the present disclosure also provides a communication system, which includes the communication device as a terminal device and the communication device as a network device in the embodiment of Figure 7, or the system includes the communication device as a terminal device and the communication device as a network device in the embodiment of Figure 8.

[0251] The present disclosure also provides a readable storage medium having instructions stored thereon, which implement the functions of any of the above method embodiments when executed by a computer.

[0252] The present disclosure also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.

[0253] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0254] Those skilled in the art will understand that the various numerical numbers such as first and second involved in the present disclosure are only for the convenience of description and are not used to limit the scope of the embodiments of the present disclosure, and also indicate the order of precedence.

[0255] At least one in the present disclosure can also be described as one or more, and multiple can be two, three, four or more. "And / or" describes the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b and c can represent: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c. Wherein a, b and c can be single or multiple, respectively. This disclosure is not limited. In the embodiments of the present disclosure, for a technical feature, the technical features in the technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", and there is no order of precedence or size between the technical features described by "first", "second", "third", "A", "B", "C" and "D".

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

[0257] The predefined in the present disclosure may be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0258] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0259] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0260] The above description is merely a specific embodiment of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this disclosure should be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be based on the scope of protection of the claims.

Claims

1. A network registration method, characterized in that: Executed by the terminal device, including: Sending a registration request to a network element, wherein the registration request is used to indicate that the terminal device will lose network coverage; Receiving a registration rejection message sent by the network element, wherein the registration rejection message is used to indicate that the terminal device cannot complete the mobility registration update process triggered by the registration request within the remaining network coverage time; According to the registration rejection message, it is determined to stop sending the registration request to the network element within a target time period.

2. The method according to claim 1, characterized in that Also includes: Determine a first time period or a second time period as the target time period, wherein the first time period is a time period determined by the terminal device as having no network coverage, and the second time period is a time period determined by the network element as having no network coverage for the terminal device.

3. The method according to claim 2, characterized in that The network coverage is satellite network coverage, the first time period is a time period without network coverage determined by the terminal device based on the acquired first satellite network coverage information and the first location information of the terminal device, and the second time period is a time period without network coverage determined by the network element based on the acquired second satellite network coverage information and the second location information of the terminal device.

4. The method according to claim 2 or 3, characterized in that The determining the first time period or the second time period as the target time period includes: determining that the first time period is not included and the registration rejection message includes the second time period; The second time period is determined as the target time period.

5. The method according to claim 2 or 3, characterized in that: The determining the first time period or the second time period as the target time period includes: Determining that the first time period is included and the registration rejection message does not include the second time period; The first time period is determined as the target time period.

6. The method according to claim 2 or 3, characterized in that: The determining the first time period or the second time period as the target time period includes: Determining that the first time period is included and the registration rejection message includes the second time period; Determine the first time period or the second time period as the target time period.

7. The method according to any one of claims 2 to 6, characterized in that: The time periods of the first period and the second period are the same or different.

8. The method according to any one of claims 1 to 7, characterized in that: The remaining network coverage duration is determined by the network element based on the satellite network coverage information and the location information of the terminal device.

9. The method according to any one of claims 1 to 8, characterized in that The first information field in the registration rejection message includes a rejection reason value, and the rejection reason value indicates that the terminal device cannot complete the mobility registration update process triggered by the registration request within the remaining network coverage time.

10. The method according to any one of claims 1 to 9, characterized in that: The sending of the registration request to the network element comprises: Determining that the terminal device will lose the network coverage; Sending the registration request to the network element.

11. The method according to any one of claims 1 to 10, characterized in that: The sending of the registration request to the network element comprises: sending the registration request to the network element via a satellite; Receiving a registration rejection message sent by the network element, comprising: The registration rejection message sent by the network element is received through the satellite.

12. The method according to any one of claims 1 to 11, characterized in that: The registration request is a first registration request, and the method further includes: Determining that the target time period ends, sending a second registration request to the network element, where the second registration request is used to trigger the mobility registration update process.

13. A network registration method, characterized in that: Executed by network elements, including: Receiving a registration request sent by a terminal device, wherein the registration request is used to indicate that the terminal device will lose network coverage; Determining that the remaining network coverage duration of the terminal device is less than the duration required for the mobility registration update process triggered by the registration request; A registration rejection message is sent to the terminal device, wherein the registration rejection message is used to indicate that the terminal device cannot complete the mobility registration update process within the remaining network coverage time.

14. The method according to claim 13, characterized in that Also includes: Determine the starting time and / or the second time period when the terminal device has no network coverage, wherein the second time period is the time period when the terminal device has no network coverage determined by the network element.

15. The method according to claim 14, characterized in that The determining the starting time and / or the second time period of the terminal device without network coverage includes: Based on the acquired satellite network coverage information and the location information of the terminal device, the start time of the period without network coverage and / or the second time period are determined.

16. The method according to claim 14 or 15, characterized in that Also includes: Determining the remaining network coverage duration of the terminal device according to the start time of no network coverage of the terminal device; According to the remaining network coverage duration of the terminal device and the duration required for the mobility registration update process, it is determined whether the terminal device can complete the mobility registration update process within the remaining network coverage duration.

17. The method according to any one of claims 14 to 16, characterized in that The registration rejection message includes the second time period.

18. The method according to any one of claims 13 to 17, characterized in that The registration request includes a first time period, wherein the first time period is a time period determined by the terminal device as a time period without network coverage, and the time period of the first time period is the same as or different from the time period of the second time period.

19. The method according to claim 18, characterized in that The network coverage is satellite network coverage, the first time period is a time period without network coverage determined by the terminal device based on the acquired first satellite network coverage information and the first location information of the terminal device, and the second time period is a time period without network coverage determined by the network element based on the acquired second satellite network coverage information and the second location information of the terminal device.

20. The method according to any one of claims 13 to 19, characterized in that: The receiving a registration request sent by a terminal device includes: receiving the registration request sent by the terminal device via a satellite; The sending a registration rejection message to the terminal device includes: The registration rejection message is sent to the terminal device via the satellite.

21. The method according to any one of claims 13 to 20, characterized in that: The first information field in the registration rejection message includes a rejection reason value, and the rejection reason value indicates that the terminal device cannot complete the mobility registration update process triggered by the registration request within the remaining network coverage time.

22. A network registration method, characterized in that: Executed by a communication system, the method comprises: The terminal device sends a registration request to the network element, wherein the registration request is used to indicate that the terminal device will lose network coverage; The network element determines that the remaining network coverage time of the terminal device is less than the time required to complete the mobility registration update process triggered by the registration request; The network element sends a registration rejection message to the terminal device, wherein the registration rejection message is used to indicate that the terminal device cannot complete the mobility registration update process within the remaining network coverage time; The terminal device determines to stop sending the registration request to the network element within a target time period based on the registration rejection message.

23. A terminal device, characterized in that: include: A transceiver module, used to send a registration request to a network element, wherein the registration request is used to indicate that the terminal device will lose network coverage; The transceiver module is further used to receive a registration rejection message sent by the network element, wherein the registration rejection message is used to indicate that the terminal device cannot complete the mobility registration update process triggered by the registration request within the remaining network coverage time; A processing module is used to determine, according to the registration rejection message, to stop sending the registration request to the network element within a target time period.

24. A network element, characterized in that: include: A transceiver module, configured to receive a registration request sent by a terminal device, wherein the registration request is used to indicate that the terminal device will lose network coverage; A processing module, used to determine that the remaining network coverage time of the terminal device is less than the time required to complete the mobility registration update process triggered by the registration request; The transceiver module is further used to send a registration rejection message to the terminal device, wherein the registration rejection message is used to indicate that the terminal device cannot complete the mobility registration update process within the remaining network coverage time.

25. A terminal, characterized in that: include: one or more processors, transceivers, and memories; The memory includes instructions, and when the instructions are executed by the one or more processors, the terminal implements the method according to any one of claims 1 to 12.

26. A network element, characterized in that: include: one or more processors, transceivers, and memories; The memory includes instructions, and when the instructions are executed by the one or more processors, the network element implements the method as described in any one of claims 13 to 21.

27. A communication system, characterized in that: The invention comprises a terminal device and a network element, wherein the terminal device is configured to implement the method according to any one of claims 1 to 12, and the network element is configured to implement the method according to any one of claims 13 to 21.

28. A computer-readable storage medium storing instructions, which, when executed, enable the method according to any one of claims 1 to 12 to be implemented, or, when executed, enable the method according to any one of claims 13 to 21 to be implemented.

Images