Communication method and device

Abstract

In the method, a terminal device determines a configured first list and / or a first waiting duration, the first list comprises information of one or more network devices about to cover the terminal device, and the first waiting duration is the duration that the terminal device waits for being covered by the one or more network devices; and the terminal device sends first indication information to the first network device, wherein the first indication information is used for indicating that the terminal device is configured with the first list and / or the first waiting duration. Wherein the first network device is a network device which the terminal device currently requests to access. The method facilitates the first network device to determine that the list is not configured for the terminal device and / or the waiting duration is not configured for the terminal device based on the first indication information, thereby facilitating the terminal device to continuously request to access the network device indicated by the first list and / or the first waiting duration subsequently, and facilitating the reduction of the probability of data packet loss and the waste of storage resources.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0002] To implement store and forward (SF) technology, regenerable satellites in non-terrestrial networks (NTNs) can also deploy mobility management entities (MMEs), and the system architecture that includes regenerable satellites with deployed MMEs can be called a split MME architecture.

[0003] In the split MME architecture, if a satellite to which a terminal requests access has not obtained the terminal's registration information, the satellite will determine, based on ephemeris information, one or more satellites that will soon cover the terminal and can obtain the terminal's registration information before covering the terminal, and configure a list #a for the terminal. List #a includes information about one or more satellites that will soon cover the terminal, so that the terminal can subsequently access one or more satellites indicated by list #a, which can improve the success rate of terminal access.

[0004] However, if one of the satellites indicated by monitoring list #a fails to obtain the terminal's registration information for some reason, such as a deteriorated power supply link or lack of storage space, that satellite will reconfigure list #b for the terminal. As a result, the terminal will subsequently access one or more satellites indicated by list #b instead of continuing to access one or more satellites indicated by list #a. Consequently, the terminal data stored on the satellites indicated by list #a that have not yet covered the terminal cannot be sent to the terminal, resulting in data packet loss. Summary of the Invention

[0005] This application provides a communication method and apparatus that helps reduce the probability of data packet loss.

[0006] In a first aspect, embodiments of this application provide a communication method. This method can be executed by a terminal device, which can be a terminal equipment, a processor, module, chip, chip system, or software module that can implement the method. In this method, the terminal device determines that it has been configured with a first list and / or a first waiting time. The first list includes information about one or more network devices that will soon cover the terminal device, and the first waiting time is the duration for which the terminal device waits to be covered by one or more network devices. The terminal device sends first indication information to the first network device, the first indication information indicating that the terminal device has been configured with the first list and / or indicating that the terminal device has been configured with the first waiting time.

[0007] Wherein, the first network device is the network device that the terminal device is currently requesting to access. Additionally, the first network device is one of one or more network devices indicated by the first list, and / or, the first network device is the network device corresponding to / indicating the first waiting time.

[0008] As can be seen, through this method, when the terminal device determines that it has been configured with the first list and / or the first waiting time, it can indicate to the first network device currently requesting access that the terminal device has been configured with the first list and / or the first waiting time through the first indication information. This helps the first network device to determine that it will not reconfigure the list and / or waiting time for the terminal device to indicate one or more network devices that will soon cover the terminal device. This, in turn, helps the terminal device to continue to request access to the network devices indicated by the first list and / or the first waiting time. It also helps the network devices indicated by the first list and / or the first waiting time to send the data of the terminal device that has been stored to the terminal device, thereby reducing the probability of data packet loss.

[0009] In addition, the ability of the terminal device to continue requesting access to the network devices in the first list and / or the first waiting time indication can reduce the resource waste caused by the network devices storing the terminal device's registration information and data when the terminal device does not subsequently access the network devices in the first list and / or the first waiting time indication.

[0010] In one optional implementation, the first indication information is used to indicate that the terminal device has been configured to cover one or more network devices that are about to cover the terminal device. The first indication information can indicate that the terminal device has been configured to cover one or more network devices by indicating that the terminal device has been configured to a first list and / or a first waiting time.

[0011] In one optional implementation, the information of each network device in one or more network devices may be the identifier of the satellite corresponding to the network device, or the cell identifier of the cell where the network device is located, or the identifier of the network device itself.

[0012] In one optional implementation, when the first indication information is used to indicate that the terminal device has been configured into the first list, the first indication information includes the first list. This method allows the first indication information to display an indication that the terminal device has been configured into the first list.

[0013] In another optional implementation, when the first indication information is used to indicate that the terminal device has been configured in the first list, the first indication information is specifically used to indicate that the first list includes information about other network devices besides the first network device. This approach allows the first indication information to implicitly indicate that the terminal device has been configured in the first list.

[0014] In another optional implementation, the first indication information is used to indicate that the terminal device has been configured in the first list. Specifically, the first indication information is used to indicate that the terminal device is the Nth terminal device requesting network access, where N is an integer greater than 1. This method allows the first network device to know, through the first indication information, that the terminal device is not the first terminal device to access the network, thereby inferring that the terminal device has been configured in the first list during previous network access requests.

[0015] In another optional implementation, the first indication information is specifically used to indicate that the terminal device is the terminal device that is requesting network access for the Nth time, thereby implicitly indicating that the terminal device has been configured with a first list and / or a first waiting time.

[0016] In one optional implementation, the first indication information is used to indicate that the terminal device has been configured with a first waiting time, and the first indication information includes the first waiting time. This method allows the first indication information to display an indication that the terminal device has been configured with a first waiting time.

[0017] As can be seen, the first instruction information can take many forms, such as explicitly indicating or implicitly indicating that the terminal device has been configured with a first list and / or a first waiting time, which can improve the flexibility of the instruction.

[0018] In one optional implementation, the first indication information is carried in the access request, which is used to request the establishment of a communication connection with the first network device. This method can reduce signaling overhead.

[0019] In an optional implementation, if the first indication information is carried in the access request, the terminal device may further perform the following steps: receiving an access response from a first network device, the access response indicating that the communication connection with the first network device has failed to be established, and the access response does not carry a second list and / or a second waiting time, the second list including information on one or more network devices that will soon cover the terminal device, and the second waiting time being the duration for which the terminal device waits to be covered by one or more network devices; determining the second network device to be requested for access, the second network device being included in one or more network devices indicated in the first list, or the second network device being the network device corresponding to / indicated by the first waiting time.

[0020] Therefore, when the terminal device carries the first indication information in its access request, if the received access response indicates that the communication connection between the terminal device and the first network device has failed to be established, and the access response does not carry the second list and / or the second waiting time, the terminal device will still determine the network device to be accessed from one or more network devices indicated by the first list and / or the first waiting time. In other words, even when the terminal device fails to establish a communication connection with the first network device, it still requests access from one or more network devices in the first list and / or the first waiting time. This allows the network devices in the first list and / or the first waiting time to send the stored data of the terminal device to the terminal device, reducing the probability of data packet loss and minimizing the waste of storage resources.

[0021] In one optional implementation, the terminal device sends a first indication message to the first network device, including: sending the first indication message to the first network device when a first condition is met. The first condition includes: no failure to establish a communication connection with all network devices in the first list and / or the first waiting time indication has occurred; or, the first condition includes: no failure to establish a communication connection with all network devices in the first list and / or the first waiting time indication other than the first network device has occurred.

[0022] Specifically, the failure to establish communication connections with all network devices in the first list and / or the first waiting time indication does not occur. For example, the terminal device may have successfully established communication connections with some or all of the network devices in the first list and / or the first waiting time indication, or the terminal device may not have yet requested to establish communication connections with some of the network devices in the first list and / or the first waiting time indication. Alternatively, the failure to establish communication connections with all network devices other than the first network device in one or more network devices in the first list and / or the first waiting time indication does not occur. This could be because the terminal device has successfully established communication connections with some or all of the network devices other than the first network device in one or more network devices in the first list and / or the first waiting time indication, or the terminal device may not have yet requested to establish communication connections with some of the network devices other than the first network device in one or more network devices in the first list and / or the first waiting time indication.

[0023] In one optional implementation, the terminal device does not send the first indication information to the first network device if the first condition is not met. This approach allows the first network device to configure a second list for the terminal device without obtaining its registration information, thereby enabling the terminal device to request access from the network devices indicated in the second list if it fails to establish a communication connection with any of the network devices indicated in the first list.

[0024] In one optional implementation, the terminal device may also delete the first list and / or the first waiting time if the first condition is not met. If the first condition is not met, it indicates that the terminal device has failed to establish a communication connection with all network devices indicated in the first list, or has failed to establish a communication connection with all network devices other than the first network device among one or more network devices indicated in the first list. In this case, the terminal device deletes the first list and / or the first waiting time, and subsequently selects a new network device to access.

[0025] In another optional implementation, the terminal device sends a first indication message to the first network device, including: sending the first indication message to the first network device through a first cell under the first network device when a second condition is met. The second condition includes: receiving a fourth indication message from the first network device, the fourth indication message indicating that the first cell under the first network device is operating in store-and-forward mode, and / or indicating that the first cell under the first network device allows a store-and-forward type terminal device to reside or access the network.

[0026] The fourth indication information is used to indicate that the first cell under the first network device is operating in store-and-forward mode, and / or to indicate that the first cell under the first network device allows a store-and-forward type terminal device to camp or access, indicating that the terminal device can access the first cell under the first network device. Then the terminal device sends the first indication information to the first network device, so that the first network device will no longer configure a list of one or more network devices that will soon cover the terminal device and / or a waiting time for the terminal device without obtaining the registration information of the terminal device. This helps to reduce the probability of data packet loss and the waste of storage resources.

[0027] In another optional implementation, the terminal device does not send the first indication information to the first network device if the second condition is not met. If the second condition is not met, it indicates that the first cell under the first network device may not be operating in store-and-forward mode, or that the terminal device is not allowed to access the first cell under the first network device. In this case, the terminal does not send the first indication information to the first network device to save signaling overhead.

[0028] In another optional implementation, the terminal device sends a first indication message to the first network device via a first cell under the first network device, including: sending the first indication message to the first network device when both a first condition and a second condition are met simultaneously. The first condition includes: no failure to establish a communication connection with all network devices indicated in the first list has occurred; or, the first condition includes: no failure to establish a communication connection with all network devices other than the first network device among one or more network devices indicated in the first list has occurred. The second condition includes: receiving a fourth indication message from the first network device, the fourth indication message indicating that the first cell under the first network device is operating in store-and-forward mode, or indicating that the first cell under the first network device allows store-and-forward type terminal devices to reside or access the network.

[0029] In one optional implementation, the first list does not include information on one or more third network devices, which are network devices that have not obtained the registration information of the terminal device. This approach helps the terminal device avoid subsequently requesting access to network devices where established communication connections have failed, thereby increasing the probability of successful access and reducing signaling overhead.

[0030] In an optional implementation, the terminal device may further perform the following steps: receiving second indication information, the second indication information being used to indicate a third list, the third list including information about a fourth network device, the fourth network device being one or more third network devices that have obtained the registration information of the terminal device; and determining a fifth network device to request access, the fifth network device being included in the fourth network device.

[0031] It is evident that the third list received by the terminal device may include information about a fourth network device that has failed to establish a communication connection with the terminal device and has obtained the terminal device's registration information. This facilitates the terminal device's subsequent request for access from the fourth network device, which in turn facilitates the fourth network device's ability to send stored data from the terminal device to the terminal device. This increases the probability of successful access for the terminal device and reduces the probability of data packet loss.

[0032] Secondly, embodiments of this application also provide a communication method, which can be executed by a first network device. This first network device can be a network device, or a processor, module, chip, or chip system that can implement the method. In this method, the first network device receives first indication information, which indicates that a terminal device has been configured with a first list and / or a first waiting time. The first list includes information about one or more network devices that will soon cover the terminal device, and the first waiting time is the duration for which the terminal device waits to be covered by one or more network devices. Based on the first indication information, the first network device determines not to configure a second list and / or a second waiting time for the terminal device. The second list includes information about one or more network devices that will soon cover the terminal device, and the second waiting time is the duration for which the terminal device waits to be covered by one or more network devices.

[0033] As can be seen, through this method, the first network device can learn from the received first indication information that the terminal device has been configured with a first list and / or a second waiting time, thereby determining not to configure a second list and / or a second waiting time for the terminal device. This method is beneficial for the terminal device to subsequently request access to one or more network devices in the first list and / or second waiting time indication list, which in turn is beneficial for the network devices in the first list and / or first waiting time indication list to send the terminal device's data to the terminal device, reducing the probability of data packet loss.

[0034] In addition, the ability of the terminal device to continue requesting access to the network devices in the first list and / or the first waiting time indication can reduce the resource waste caused by the network devices in the first list and / or the first waiting time indication storing the terminal device's registration information and data, which would otherwise result in the terminal device not subsequently accessing the network devices in the first list and / or the first waiting time indication.

[0035] In one optional implementation, the first network device determines, based on the first indication information, not to configure the second list and / or the second waiting time for the terminal device, including: in the absence of obtaining the registration information of the terminal device, determining, based on the first indication information, not to configure the second list and / or the second waiting time for the terminal device.

[0036] In one optional implementation, the first indication information is used to indicate that the terminal device has been configured to cover one or more network devices that are about to cover the terminal device. The first indication information can indicate that the terminal device has been configured to cover one or more network devices by indicating that the terminal device has been configured to a first list and / or a first waiting time.

[0037] In one optional implementation, the first indication information is carried in the access request of the terminal device, which is used to request the establishment of a communication connection with the first network device. This method can reduce signaling overhead.

[0038] In one optional implementation, when the first indication information is carried in the access request of the terminal device, the first network device may also send an access response to the terminal device. The access response is used to indicate that the communication connection between the terminal device and the first network device has failed to be established, and the access response does not carry a second list and / or a second waiting time.

[0039] As can be seen, when the first indication information is carried in the access request of the terminal device, since the first network device has not obtained the registration information of the terminal device, it cannot determine whether the terminal device is legitimate. Therefore, the first network device indicates to the terminal device through the access response that the communication connection with the terminal device has failed, thereby refusing the terminal device's access. In addition, the access response does not carry the second list and / or the second waiting time, which is beneficial for the terminal device to subsequently request access to network devices that indicate the first list and / or the first waiting time, thereby reducing the probability of data packet loss and reducing the waste of storage resources.

[0040] In one optional implementation, the information of each network device in one or more network devices may be the identifier of the satellite corresponding to the network device, or the cell identifier of the cell to which the network device belongs, or the identifier of the network device itself.

[0041] In one optional implementation, when the first indication information is used to indicate that the terminal device has been configured into the first list, the first indication information includes the first list. This method allows the first indication information to display an indication that the terminal device has been configured into the first list.

[0042] In another optional implementation, when the first indication information is used to indicate that the terminal device has been configured in the first list, the first indication information is specifically used to indicate that the first list includes information about other network devices besides the first network device. This approach allows the first indication information to implicitly indicate that the terminal device has been configured in the first list.

[0043] In another optional implementation, the first indication information is used to indicate that the terminal device has been configured in the first list. Specifically, the first indication information is used to indicate that the terminal device is the Nth terminal device requesting network access, where N is an integer greater than 1. This method allows the first network device to know, through the first indication information, that the terminal device is not the first terminal device to access the network, thereby inferring that the terminal device has been configured in the first list during previous network access requests.

[0044] In another optional implementation, the first indication information is specifically used to indicate that the terminal device is the terminal device that is requesting network access for the Nth time, thereby implicitly indicating that the terminal device has been configured with a first list and / or a first waiting time.

[0045] In one optional implementation, the first indication information is used to indicate that the terminal device has been configured with a first waiting time, and the first indication information includes the first waiting time. This method allows the first indication information to display an indication that the terminal device has been configured with a first waiting time.

[0046] As can be seen, the first instruction information can be in various forms, such as explicit or implicit instructions, indicating that the terminal device has been configured with a first list, which can improve the flexibility of the instruction.

[0047] In one optional implementation, the first network device may further release information about the terminal device, which refers to information sent by the terminal device to the first network device, such as the terminal device's identifier. This approach is beneficial because when the first network device subsequently connects to the gateway station and the core network, it no longer needs to request the terminal device's registration information, thus reducing signaling overhead.

[0048] Thirdly, embodiments of this application provide a communication method, which can be executed by a terminal device. The terminal device can be a terminal equipment, or a processor, module, chip, chip system, or software module that implements the method. In this method, the terminal device receives a second list and / or a second waiting duration from a first network device. The second list includes information about one or more network devices that will soon cover the terminal device. The second waiting duration is the duration during which the terminal device waits to be covered by one or more network devices. The first network device is the network device that the terminal device is currently requesting access to. In response to receiving the second list and / or the second waiting duration, and given a configured first list and / or a first waiting duration, the terminal device determines the second network device to be requested for access. The second network device is included in one or more network devices indicated by the first list, or the second network device is the network device corresponding to the first waiting duration. The first list includes information about one or more network devices that will soon cover the terminal device, and the first waiting duration is the duration during which the terminal device waits to be covered by one or more network devices.

[0049] As can be seen, with this method, even if the terminal device receives a reconfigured second list and / or second waiting time from the first network device currently requesting access, the terminal device can still determine the second network device to be requested from one or more network devices indicated by the first list and / or the first waiting time, provided that the first list and / or the first waiting time has been configured. This is beneficial for the network devices indicated by the first list and / or the first waiting time to send the stored data of the terminal device to the terminal device, thereby reducing the probability of data packet loss.

[0050] In addition, the ability of the terminal device to continue requesting access to network devices in the first list and / or the first waiting time indication can reduce the resource waste caused by the network devices storing the terminal device's registration information and data when the terminal device does not subsequently access the network devices in the first list and / or the first waiting time indication.

[0051] In one optional implementation, the information of each network device in one or more network devices may be the identifier of the satellite corresponding to the network device, or the cell identifier of the cell to which the network device belongs, or the identifier of the network device itself.

[0052] In one alternative implementation, the terminal device may also delete the second list and / or the second waiting time to free up storage resources.

[0053] In one optional implementation, the terminal device may further send a third indication message to the first network device. This third indication message instructs the first network device to release the terminal device's information, which refers to information sent by the terminal device to the first network device, such as the terminal device's identifier. This approach is beneficial because when the first network device subsequently connects to the gateway station and the core network, it no longer needs to request the terminal device's registration information, thus reducing signaling overhead.

[0054] In one optional implementation, the third indication information is further used to indicate that the terminal device has been configured with a first list and / or a first waiting time. This method allows the first network device to know that the terminal device has been configured with a first list and / or a first waiting time, thereby speculating that the terminal device may not request access from the network device indicated by the second list and / or the second waiting time.

[0055] In one optional implementation, the third indication information is used to indicate that the terminal device has been configured in the first list, and the third indication information includes the first list. This method allows the third indication information to display an indication that the terminal device has been configured in the first list.

[0056] In another optional implementation, the third indication information is used to indicate that when the terminal device has been configured in the first list, the third indication information is specifically used to indicate that the first list includes information about other network devices besides the first network device. This approach allows the third indication information to implicitly indicate that the terminal device has been configured in the first list.

[0057] In another optional implementation, the third indication information is used to indicate that the terminal device has been configured in the first list. Specifically, the third indication information is used to indicate that the terminal device is the Nth terminal device requesting network access, where N is an integer greater than 1. This method allows the first network device to know, through the third indication information, that the terminal device is not the first terminal device to access the network, thereby inferring that the terminal device has been configured in the first list during previous network access requests.

[0058] In another optional implementation, the third indication information is specifically used to indicate that the terminal device is the terminal device that is requesting network access for the Nth time, thereby implicitly indicating that the terminal device has been configured with the first list and / or the first waiting time.

[0059] In one optional implementation, the third indication information is used to indicate that the terminal device has been configured with a first waiting time, and the third indication information includes the first waiting time. This method allows the third indication information to display an indication that the terminal device has been configured with a first waiting time.

[0060] As can be seen, the third instruction information can be in various forms, such as explicit or implicit instructions, indicating that the terminal device has been configured with the first list, which can improve the flexibility of the instruction.

[0061] Fourthly, embodiments of this application also provide a communication method, which can be executed by a terminal device. This terminal device can be a terminal equipment, or a processor, module, chip, chip system, or software module capable of implementing the method. In this method, the terminal device receives a first list, which includes information from one or more sixth network devices, but does not include information from one or more third network devices. The one or more sixth network devices are network devices that have obtained or are about to obtain registration information from the terminal device, and the one or more third network devices are network devices that have not obtained registration information from the terminal device.

[0062] As can be seen, through this method, the first list configured for the terminal device includes information on one or more sixth network devices that have obtained or are about to obtain the terminal device's registration information, but does not include information on one or more third network devices that have not obtained the terminal device's registration information. This approach allows the terminal device to request access from one or more sixth network devices that have obtained or are about to obtain the terminal device's registration information, thereby increasing the probability of the terminal device successfully accessing the network.

[0063] In an optional implementation, the terminal device further performs the following steps: receiving second indication information, the second indication information being used to indicate a third list, the third list including information about a fourth network device, the fourth network device being one or more third network devices that have obtained the registration information of the terminal device; and determining a fifth network device to request access, the fifth network device being included in the fourth network device.

[0064] As can be seen, the third list reconfigured by the terminal device includes information on the fourth network device that has obtained the terminal device's registration information from one or more third network devices, thereby enabling the terminal device to request access from the fourth network device, which can increase the probability of the terminal device successfully accessing the network.

[0065] Fifthly, embodiments of this application also provide a communication method, which can be executed by a terminal device. This terminal device can be a terminal equipment, or a processor, module, chip, chip system, or software module that implements the method. In this method, the terminal device determines whether a fifth indication information exists in the system broadcast message from a first cell under a first network device. If the fifth indication information does not exist, the terminal device determines whether to camp on the first cell under the first network device based on non-terrestrial network cell prohibition information from the first cell under the first network device. The fifth indication information is used to indicate that the first cell under the first network device is operating in store-and-forward mode, and / or to indicate whether the first cell under the first network device allows store-and-forward type terminal devices to camp.

[0066] As can be seen, by using this method, if there is no fifth indication information in the system broadcast message from the first cell under the first network device, the terminal device can determine whether to camp on a cell under the first network device based on the non-terrestrial network cell prohibition information from the first cell under the first network device.

[0067] In one optional implementation, the terminal device determines whether to allow camping in the first cell of the first network device based on non-terrestrial network cell prohibition information from the first cell of the first network device, including: if the non-terrestrial network cell prohibition information from the first cell of the first network device indicates prohibition, determining that camping in the first cell of the first network device is not allowed; and if the non-terrestrial network cell prohibition information indicates non-prohibition, determining that camping in the first cell of the first network device is allowed.

[0068] In one optional implementation, non-terrestrial network cell prohibition information of the first cell under the first network device is carried in the system broadcast message of the first cell.

[0069] Sixthly, embodiments of this application also provide a communication device. This communication device has some or all of the functions of the terminal device described in the first, third, fourth, or fifth aspects above, or it has some or all of the functions of the first network device described in the second aspect above. For example, the communication device may have some or all of the functions of the terminal device described in the first aspect of this application, or it may have the functions of any one of the embodiments of this application implemented individually. The functions can 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.

[0070] In one possible design, the communication device may include a processing unit and a communication unit. The processing unit is configured to support the communication device in performing the corresponding functions described in the above method. The communication unit is used to support communication between the communication device and other communication devices. The communication device may also include a storage unit coupled to the processing unit and the communication unit, which stores necessary program instructions and data for the communication device.

[0071] In one embodiment, the communication device includes a processing unit and a communication unit, and the device is applied to a terminal device;

[0072] The processing unit is configured to determine a first list and / or a first waiting time, wherein the first list includes information about one or more network devices that will soon cover the terminal device, and the first waiting time is the duration during which the terminal device waits to be covered by one or more network devices.

[0073] The communication unit is configured to send first indication information to a first network device, the first indication information being used to indicate that the terminal device has been configured with the first list, and / or to indicate that the terminal device has been configured with the first waiting time; the first network device is the network device that the terminal device is currently requesting to access.

[0074] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the first aspect above, and will not be described in detail here.

[0075] In another embodiment, the communication device includes a processing unit and a communication unit, and the device is applied to a first network device;

[0076] The communication unit is configured to receive first indication information, which indicates that the terminal device has been configured with a first list and / or a first waiting time. The first list includes information about one or more network devices that will soon cover the terminal device, and the first waiting time is the duration during which the terminal device waits to be covered by one or more network devices.

[0077] The processing unit is configured to determine, based on the first indication information, not to configure a second list and / or a second waiting time for the terminal device, wherein the second list includes information on one or more network devices that will soon cover the terminal device, and the second waiting time is the duration for which the terminal device waits to be covered by one or more network devices.

[0078] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the second aspect above, and will not be described in detail here.

[0079] In another embodiment, the communication device includes a processing unit and a communication unit, and the device is applied to a terminal device;

[0080] The communication unit is configured to receive a second list and / or a second waiting time from a first network device, the second list including information about one or more network devices that are about to cover the terminal device, the second waiting time being the duration for which the terminal device waits to be covered by one or more network devices, and the first network device being the network device that the terminal device is currently requesting to access.

[0081] The processing unit is configured to, in response to receiving the second list and / or the second waiting time, determine, in the case of a configured first list and / or a first waiting time, a second network device to be requested for access, wherein the second network device is included in one or more network devices indicated by the first list, or the second network device is the network device corresponding to the first waiting time.

[0082] The first list includes information about one or more network devices that will soon cover the terminal device, and the first waiting time is the time during which the terminal device waits to be covered by one or more network devices.

[0083] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the third aspect above, and will not be described in detail here.

[0084] In another embodiment, the communication device includes a processing unit and a communication unit, the device being applied to a terminal device, and the processing unit being used to process signals;

[0085] The communication unit is configured to receive a first list, the first list including information of one or more sixth network devices, and the first list not including information of one or more third network devices.

[0086] Wherein, the one or more sixth network devices are network devices that have obtained or are about to obtain the registration information of the terminal device, and the one or more third network devices are network devices that have not obtained the registration information of the terminal device.

[0087] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the fourth aspect above, and will not be described in detail here.

[0088] In another embodiment, the communication device includes a processing unit and a communication unit, the device being applied to a terminal device, and the communication unit being used to receive / send signals;

[0089] The processing unit is used to determine whether there is a fifth indication information in the system broadcast message from the first cell under the first network device;

[0090] The processing unit is further configured to determine whether to remain in the first cell under the first network device based on the non-terrestrial network cell prohibition information from the first network device in the absence of the fifth indication information;

[0091] The fifth indication information is used to indicate that the first cell under the first network device is operating in store-and-forward mode, and / or to indicate whether the first cell under the first network device allows store-and-forward type terminal devices to reside.

[0092] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the fifth aspect above, and will not be described in detail here.

[0093] As an example, the communication unit can be a transceiver or a communication interface, the storage unit can be a memory, and the processing unit can be a processor.

[0094] In one embodiment, the communication device includes a processor and a transceiver, and the device is applied to a terminal device;

[0095] The processor is configured to determine a first list and / or a first waiting time, the first list including information about one or more network devices that will soon cover the terminal device, and the first waiting time being the duration for which the terminal device waits to be covered by one or more network devices.

[0096] The transceiver is configured to send first indication information to a first network device, the first indication information being used to indicate that the terminal device has been configured with the first list, and / or to indicate that the terminal device has been configured with the first waiting time, the first network device being the network device that the terminal device is currently requesting to access.

[0097] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the first aspect above, and will not be described in detail here.

[0098] In another embodiment, the communication device includes a processor and a transceiver, the device being applied to a first network device;

[0099] The transceiver is configured to receive first indication information, which indicates that the terminal device has been configured with a first list and / or a first waiting time. The first list includes information about one or more network devices that will soon cover the terminal device, and the first waiting time is the duration during which the terminal device waits to be covered by one or more network devices.

[0100] The processor is configured to, without obtaining the registration information of the terminal device, determine, based on the first indication information, not to configure a second list and / or a second waiting time for the terminal device, wherein the second list includes information on one or more network devices that will soon cover the terminal device, and the second waiting time is the duration for which the terminal device waits to be covered by one or more network devices.

[0101] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the second aspect above, and will not be described in detail here.

[0102] In another embodiment, the communication device includes a processor and a transceiver, and the device is applied to a terminal device;

[0103] The transceiver is configured to receive a second list and / or a second waiting time from a first network device, the second list including information about one or more network devices that are about to cover the terminal device, the second waiting time being the duration for which the terminal device waits to be covered by one or more network devices, and the first network device being the network device that the terminal device is currently requesting to access.

[0104] The processor is configured to, in response to receiving the second list and / or the second waiting time, determine, in the case of a configured first list and / or a first waiting time, a second network device to be requested for access, wherein the second network device is included in one or more network devices indicated by the first list, or the second network device is the network device corresponding to the first waiting time.

[0105] The first list includes information about one or more network devices that will soon cover the terminal device, and the first waiting time is the time during which the terminal device waits to be covered by one or more network devices.

[0106] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the third aspect above, and will not be described in detail here.

[0107] In another embodiment, the communication device includes a processor and a transceiver, the device being applied to a terminal device, the processor being used to process signals;

[0108] The transceiver is configured to receive a first list, the first list including information of one or more sixth network devices, and the first list not including information of one or more third network devices.

[0109] Among them, the one or more sixth network devices are network devices that have obtained or are about to obtain the registration information of the terminal device, and the one or more third network devices are network devices that have not obtained the registration information of the terminal device.

[0110] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the fourth aspect above, and will not be described in detail here.

[0111] In another embodiment, the communication device includes a processor and a transceiver, the device being applied to a terminal device, the transceiver being used to receive / send signals;

[0112] The processor is used to determine whether there is a fifth indication information in the system broadcast message from the first cell under the first network device;

[0113] The processor is further configured to determine whether to camp on the first cell under the first network device based on non-terrestrial network cell prohibition information from the first cell under the first network device in the absence of the fifth indication information;

[0114] The fifth indication information is used to indicate that the first cell under the first network device is operating in store-and-forward mode, and / or to indicate whether the first cell under the first network device allows store-and-forward type terminal devices to reside.

[0115] In addition, other alternative implementations of the communication device in this regard can be found in the relevant content of the fifth aspect above, and will not be described in detail here.

[0116] In another embodiment, the communication device is a chip or chip system. The processing unit may also be a processing circuit or logic circuit; the communication unit may be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system.

[0117] In implementation, the processor can be used for, but is not limited to, baseband-related processing, and the transceiver can be used for, but is not limited to, radio frequency transceiver. These devices can be disposed on separate chips, or at least partially or entirely on the same chip. For example, the processor can be further divided into analog baseband processors and digital baseband processors. The analog baseband processor can be integrated with the transceiver on the same chip, while the digital baseband processor can be disposed on a separate chip. With the continuous development of integrated circuit technology, more and more devices can be integrated on the same chip. For example, a digital baseband processor can be integrated with multiple application processors (e.g., but not limited to graphics processors, multimedia processors, etc.) on the same chip. Such a chip can be called a system-on-a-chip (SoC). Whether the various devices are disposed independently on different chips or integrated on one or more chips often depends on the needs of the product design. This application does not limit the implementation form of the above-mentioned devices.

[0118] Seventhly, embodiments of this application also provide a processor for executing the various methods described above. During the execution of these methods, the processes related to sending and receiving the aforementioned information can be understood as the processor outputting the aforementioned information and the processor receiving the input information. When outputting the aforementioned information, the processor outputs the information to a transceiver for transmission. After being output by the processor, the information may require further processing before reaching the transceiver. Similarly, when the processor receives the input information, the transceiver receives the information and inputs it to the processor. Furthermore, after the transceiver receives the information, the information may require further processing before being input to the processor.

[0119] Unless otherwise specified, or unless it contradicts its actual function or internal logic in the relevant description, the transmission and reception operations involved by the processor can be more generally understood as processor output and reception, input and other operations, rather than transmission and reception operations directly performed by radio frequency circuits and antennas.

[0120] In implementation, the processor can be a dedicated processor for executing these methods, or it can be a processor that executes computer instructions stored in memory to execute these methods, such as a general-purpose processor. The memory can be a non-transitory memory, such as read-only memory (ROM), which can be integrated with the processor on the same chip or disposed on different chips. This application does not limit the type of memory or the arrangement of the memory and processor.

[0121] Eighthly, embodiments of this application also provide a communication system, which includes a terminal device and a network device. In another possible design, the system may further include other devices / functional network elements that interact with at least one of the terminal device and the network device.

[0122] Ninthly, embodiments of this application provide a computer-readable storage medium for storing instructions that, when executed on a communication device, implement the method described in any one of the first to fifth aspects.

[0123] In a tenth aspect, embodiments of this application also provide a computer program product including instructions that, when executed on a communication device, implement the method described in any one of the first to fifth aspects.

[0124] Eleventhly, embodiments of this application provide a chip system including a processor and an interface. The interface is used to acquire programs or instructions, and the processor is used to invoke the programs or instructions to implement or support a terminal device in implementing the functions involved in the first, third, fourth, or fifth aspects, or to implement or support a first network device in implementing the functions involved in the second aspect. For example, determining or processing at least one of the data and information involved in the above methods. In one possible design, the chip system further includes a memory for storing necessary program instructions and data. The chip system may be composed of chips or may include chips and other discrete devices.

[0125] In a twelfth aspect, embodiments of this application provide a communication device including a processor for executing a computer program or executable instructions stored in a memory, wherein when the computer program or executable instructions are executed, the device performs the methods as described in the first to fifth aspects and any possible implementation thereof.

[0126] In one possible implementation, the processor and memory are integrated together;

[0127] In another possible implementation, the aforementioned memory is located outside the communication device.

[0128] The beneficial effects of aspects six through twelfth can be referenced from the beneficial effects of aspects one through five, and will not be repeated here. Attached Figure Description

[0129] Figure 1 This is a schematic diagram of a system architecture;

[0130] Figure 2 This is a schematic diagram of an application framework;

[0131] Figure 3 This is a schematic diagram of an O-RAN system architecture;

[0132] Figure 4 This is a schematic diagram of a RAN system architecture based on NTN;

[0133] Figure 5 This is a schematic diagram of another RAN system architecture based on NTN;

[0134] Figure 6 This is another schematic diagram of a RAN system architecture based on NTN;

[0135] Figure 7 This is another schematic diagram of a RAN system architecture based on NTN;

[0136] Figure 8 This is a scene illustration of a SF (Science Fiction).

[0137] Figure 9 This is a schematic diagram of the terminal network access process;

[0138] Figure 10 This is an interactive schematic diagram of a communication method provided in an embodiment of this application;

[0139] Figure 11 This is an interactive schematic diagram of another communication method provided in an embodiment of this application;

[0140] Figure 12 This is an interactive schematic diagram of another communication method provided in the embodiments of this application;

[0141] Figure 13 This is an interactive schematic diagram of another communication method provided in the embodiments of this application;

[0142] Figure 14 This is an interactive schematic diagram of another communication method provided in the embodiments of this application;

[0143] Figure 15 This is a flowchart illustrating another communication method provided in an embodiment of this application;

[0144] Figure 16 This is an interactive schematic diagram of another communication method provided in the embodiments of this application;

[0145] Figure 17 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0146] Figure 18 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0147] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0148] The technical solutions of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, New Radio (NR), the 3rd Generation Partner Project (3GPP) Service-Based Architecture (SBA) and other fifth-generation (5G) or sixth-generation (6G) communication systems, etc.

[0149] Please see Figure 1 , Figure 1 This is a schematic diagram of a system architecture provided in an embodiment of this application. For example... Figure 1 As shown, the system architecture includes terminal devices, access network devices, and core network devices. The access network devices can be deployed on satellites and are used to connect the terminal devices to the wireless network. The core network devices are used to manage the terminal devices and provide gateways for communication with the data network (DN).

[0150] In this embodiment, the terminal device may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem that have wireless communication capabilities. The terminal device may also be referred to as a terminal. Terminal equipment can also refer to user equipment (UE), access terminal, user unit, user agent, cellular phone, smartphone, wireless data card, personal digital assistant (PDA) computer, tablet computer, wireless modem, handset, laptop computer, point of sale (POS) machine, customer-premises equipment (CPE), machine-type communication (MTC) terminal, communication equipment carried on high-altitude aircraft, wearable device, drone, robot, device-to-device (D2D) terminal, vehicle-to-everything (V2X) terminal, virtual reality (VR) terminal equipment, augmented reality (AR) terminal equipment, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical care, and smart grid. This application does not limit the scope of wireless terminals, such as those in grids, transportation safety, smart cities, smart homes, or future communication networks.

[0151] In this embodiment, the access network device refers to a radio access network (RAN) node (or device) that connects a terminal to a wireless network; it can also be called a base station. Examples of RAN nodes include: evolved Node B (gNB), transmission reception point (TRP), evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved Node B, or home Node B, HNB), base band unit (BBU), or wireless fidelity (Wi-Fi) access point (AP), etc. Furthermore, in a network architecture, the access network device may include a central unit (CU) node, a distributed unit (DU) node, or a RAN device including both CU and DU nodes. In this system, RAN equipment, including CU nodes and DU nodes, separates the protocol layer of the gNB in ​​the NR system. Some protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU, which is centrally controlled by the CU.

[0152] Furthermore, the CU can be divided into a centralized unit CU-control plane (CP) and a centralized unit CU-user plane (UP). The CU-CP is responsible for control plane functions, primarily including radio resource control (RRC) and the corresponding packet data convergence protocol (PDCP), i.e., PDCP-C. PDCP-C is mainly responsible for control plane data encryption / decryption, integrity protection, and data transmission. The CU-UP is responsible for user plane functions, primarily including the service data adaptation protocol (SDAP) and the corresponding PDCP, i.e., PDCP-U. SDAP is mainly responsible for processing core network data and mapping flows to bearers. PDCP-U is mainly responsible for data plane encryption / decryption, integrity protection, header compression, sequence number maintenance, and data transmission. The CU-CP and CU-UP are connected via an E1 interface. The CU-CP is connected to the DU via the control plane F1, i.e., via F1-C and DU. The CU-UP connects to the DU via the user plane F1 interface, that is, via F1-U and the DU. Of course, another possible implementation is that the PDCP-C is also in the CU-UP.

[0153] In this application embodiment, core network equipment refers to equipment in the core network (CN) that provides service support to terminals. Examples of core network equipment include: access and mobility management function (AMF) entities, session management function (SMF) entities, user plane function (UPF) entities, etc., which are not listed here. The AMF entity is responsible for terminal access management and mobility management; the SMF entity is responsible for session management, such as user session establishment; the UPF entity can be a user plane function entity, mainly responsible for connecting to external networks. It should be noted that in this application, entities can also be called network elements or functional entities. For example, an AMF entity can also be called an AMF network element or an AMF functional entity, and an SMF entity can also be called an SMF network element or an SMF functional entity, etc. The Mobile Management Entity (MME) entity in LTE is also mentioned.

[0154] Figure 2 This is a schematic diagram of an application framework. For example... Figure 2As shown, the communication system includes a RAN intelligent controller (RIC). For example, the RIC is responsible for network management and control. The RIC includes near-real-time RICs (near-RT RICs) and non-real-time RICs (Non-RT RICs). Non-real-time RICs primarily process non-real-time information, such as data that is not sensitive to latency, with latency in the order of seconds. Real-time RICs primarily process near-real-time information, such as data that is relatively sensitive to latency, with latency in the order of tens of milliseconds.

[0155] Near real-time RICs can obtain network-side and / or terminal-side information from RAN nodes (e.g., CU, CU-CP, CU-UP, DU, and / or RU) and / or terminals. Optionally, near real-time RICs can deliver data to RAN nodes and / or terminals.

[0156] The near real-time RIC and non-real-time RIC can also be set up as separate network elements. Optionally, the near real-time RIC and non-real-time RIC can also be part of other devices. For example, the near real-time RIC can be set in the RAN node (e.g., in CU, DU), while the non-real-time RIC can be set in operations, administration and maintenance (OAM), cloud servers, core network devices, or other network devices.

[0157] The embodiments of this application can also be applied to open radio access network (O-RAN) system architectures. For example, Figure 3 This is a schematic diagram of an O-RAN system architecture. Figure 3 As shown, the system architecture includes a RIC and an eNB. The RIC is the O-RAN intelligent controller, used to collect network information and perform necessary optimization operations, communicating with the eNB via an E2 interface. The eNB is an eNB that supports O-RAN functions.

[0158] The embodiments disclosed in this application will be presented to illustrate various aspects, embodiments, or features of this application in relation to systems including multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches may also be used.

[0159] To facilitate understanding of the solutions in the embodiments of this application, the terms that may be involved in the embodiments of this application are explained below.

[0160] 1. RAN system architecture based on non-terrestrial network (NTN).

[0161] Non-terrestrial network (NTN) devices, represented by satellites, drones, and high-altitude platforms, have always been a hot research topic. NTN devices can be used to communicate with one or more terminal devices. These devices can include satellites, high-altitude platforms (HAPs), drones, hot air balloons, low-Earth orbit (LEO) satellites, medium-Earth orbit (MEO) satellites, high-Earth orbit (HEO) satellites, etc., without further limitation.

[0162] In this application's embodiments, "satellite" refers to a collection of satellites and other network devices related to satellite communication. Therefore, in this application's embodiments, the descriptions "satellite" and "satellite network device" are equivalent. The network devices involved in this application's embodiments include the aforementioned non-terrestrial network devices, and may also include access network devices, core network devices, and data network devices. It should be understood that non-terrestrial network devices in NTN refer to network devices deployed in the air. In some feasible examples, non-terrestrial network devices can be deployed separately from access network devices, or non-terrestrial network devices can be deployed as access network devices. Access network devices can be deployed in the air, on land (e.g., indoors or outdoors, handheld or vehicle-mounted), or on water. Core network devices and data network devices can be deployed on land or water. Network devices not deployed in the air can be collectively referred to as terrestrial network devices. Non-terrestrial network devices, relative to terrestrial network devices, are high-speed mobile network devices. Terrestrial network devices, relative to non-terrestrial network devices, are stationary or slow-moving network devices.

[0163] In the following RAN system architecture, satellites, NTN gateways, and 5G base stations can all be considered part of the radio access network equipment. The following uses a 5G mobile communication system as an example to illustrate several common NTN-based RAN system architectures:

[0164] Figure 4 This is a schematic diagram of a RAN system architecture based on NTN. (Example) Figure 4As shown, this RAN system architecture carries a transparent satellite and also includes terminal equipment, an NTN gateway, a 5G base station (gNB), a 5G core network, and a data network (DN). The link between the NTN gateway and the satellite is called the feeder link, and the link between the satellite and the terminal equipment is called the service link. N6 represents the interface between the user plane function (UPF) of the 5G core network and the DN, NG represents the interface between the gNB and the 5G core network, and the New Radio (NR)-Uu ​​interface represents the interface between the terminal equipment and the gNB. The satellite and the NTN gateway together form a remote radio unit.

[0165] Figure 4 In the system architecture shown, the satellite's role is to perform frequency conversion and wireless frequency amplification, essentially functioning as an analog radio frequency repeater. Therefore, from the feeder link to the serving link, the satellite forwards the NR-Uu interface signal, which is the signal between the terminal equipment and the gNB. Conversely, from the serving link to the feeder link, the satellite forwards the NR-Uu interface signal to the gNB via the NTN gateway. In other words, the NTN gateway is used for communication between the satellite and the 5G base station; it is a transport network layer node and supports all the necessary functions for forwarding NR-Uu interface signals. Furthermore, different satellites can connect to the same terrestrial 5G base station through the NTN gateway.

[0166] Figure 5 This is a schematic diagram of another RAN system architecture based on NTN. (Example) Figure 5 As shown, the system architecture includes terminal equipment, satellites, NTN gateways, 5G core networks, and data networks (DN). The 5G base stations are deployed on satellites, which can also be referred to as satellite base stations or regenerated satellites. The service link between the terminal equipment and the satellite transmits NR-Uu interface signals, while the feeder link between the NTN gateway and the satellite transmits satellite radio interface (SRI) signals. SRI signals are the signals between the NTN gateway and the satellite. NG interface signals are transmitted from the satellite base station to the 5G core network via SRI to the NTN gateway, which then forwards them to the terrestrial 5G core network. The process of transmitting NG interface signals from the 5G core network to the satellite base station is similar and will not be described further.

[0167] Figure 6 This is a schematic diagram of another RAN system architecture based on NTN. For example... Figure 6 As shown, the system architecture is similar to... Figure 5 The difference between the system architecture shown and the one described is that... Figure 6 The system architecture includes inter-satellite links (ISLs) between satellites. Terminal devices served by a single satellite base station can access the 5G core network via ISLs, and different satellite base stations can connect to the same terrestrial 5G core network.

[0168] Figure 7 This is a schematic diagram of another RAN system architecture based on NTN. For example... Figure 7 As shown, in this system architecture, the centralized unit (CU) and distributed unit (DU) of the gNB are separated, and the distributed unit DU of the 5G base station (gNB-DU) is deployed on the satellite. DUs deployed on different satellites can connect to the same ground CU. The service link between the terminal equipment and the satellite transmits NR-Uu interface signals, and the feeder link between the NTN gateway and the satellite transmits SRI signals.

[0169] The NTN-based RAN system architecture also includes another architecture, which incorporates satellites with integrated access and backhaul (IAB) capabilities, with the satellites acting as IAB nodes. Furthermore, in this architecture, in addition to deploying DUs (Dedicated Units), mobile terminal (MT) modules are also deployed on the satellites. Backhaul is performed using the air interface between the MTs and the ground base station, eliminating the need to establish a separate microwave backhaul link between the satellite and the NTN gateway.

[0170] The embodiments of this application can be applied to Figure 5 and Figure 6 The system architecture shown includes regenerable satellites.

[0171] When the NTN in this application embodiment is applied to the evolved 6G mobile communication system, the RAN system architecture based on NTN is the same as described above. Figures 4 to 7 The system architectures shown are similar. The difference lies in that when NTN is applied to the evolved 6G mobile communication system, in the NTN-based RAN system architecture, the base station communicating with the terminal equipment is a 6G base station, the CN communicating with the base station is a 6G CN, and the interface in the system is a 6G interface.

[0172] 2. Store and forward (S&F or SF).

[0173] The Internet of Things (IoT) NTN is an evolution based on LTE, with eNBs as base stations and MMEs as core network elements. It should be noted that when this application's embodiments are applied to IoT NTNs based on other system evolutions, the access network equipment and core network elements change accordingly. For example, when IoT NTN is an evolution based on NR, the base station is a gNB, and the core network elements include AMFs.

[0174] In Protocol R19, IoT NTN will study SF (Survival Service) based on a regenerating satellite architecture. The requirement for S&F is to address the needs of smaller satellite companies that may have a limited number of satellites and ground gateways, making it impossible to maintain constant connection between ground gateways (NTN gateways) and satellites. In such scenarios, when a satellite covers a terminal, it may be unable to connect to the gateway, thus preventing communication with the core network; conversely, when the satellite can cover the gateway and connect to the core network, the terminal may not be covered. In these situations, normal real-time services cannot be completed. For non-real-time IoT services (such as sensor data reporting), communication between the satellite and the terminal can begin when the satellite covers the terminal, and then communication between the satellite and the core network can begin when the satellite covers the gateway, thus relaying data transmission. This requires the satellite to have sufficient storage and processing capabilities to cache data arriving from the terminal or core network and forward it at a later time. Therefore, the satellite in this scenario needs to be a regenerating satellite, i.e., a satellite connected to the eNB. Thus, the SF scenario is suitable for the above-mentioned scenarios. Figure 5 and Figure 6 The system architecture described above.

[0175] For example, Figure 8 This is a scene illustration for a type of SF (Science Fiction). For example... Figure 8 As shown, at time t1, satellite 1 connects to the NTN gateway and can communicate with the core network, but does not cover the terminal. Therefore, satellite 1 first communicates with the core network and stores the communication data with the core network. At time t2, satellite 1 covers the terminal but is not connected to the NTN gateway and cannot communicate with the core network. Therefore, satellite 1 can send the stored communication data from communication with the core network at time t1 to the terminal, and can also communicate with the terminal and store the communication data with the terminal. At time t3, satellite 1 connects to the NTN gateway again but does not cover the terminal. Therefore, satellite 1 can send the stored communication data from communication with the terminal at time t2 to the core network, and can also communicate with the core network and store the communication data from communication with the core network, so that when communicating with the terminal later, it can send the communication data from communication with the core network at time t3 to the terminal.

[0176] For SF scenarios, regenerable satellites in NTN can also deploy MMEs. The system architecture of regenerable satellites with deployed MMEs can be called a split MME architecture or a split MME on-board architecture. In this split MME architecture, some MMEs are on the satellite, while others, along with all other core network elements (such as the Serving Gate Way (SGW) and Home Subscriber Server (HSS),) are on the ground. There is no functional distinction between the on-board MME and the ground-based MME; they can be considered the same MME. That is, the on-board MME also possesses all the functions of an MME. When the satellite and ground feeder links are connected, the on-board MME and the ground-based MME can be considered the same MME. When the satellite and ground feeder links are not connected, the on-board MME can independently process non-access stratum (NAS) messages (such as messages between terminals and MMEs), but cannot communicate with the ground-based MME or other core network elements.

[0177] For example, Figure 9 This is a schematic diagram illustrating the network access process for a terminal. Specifically, Figure 9 This is a schematic diagram of a terminal network access process for a Split MME architecture. Figure 9 As shown, at time T1, satellite 1 covers the terminal. The terminal sends a NAS message requesting network access to MME1, which is also deployed on satellite 1, via eNB1. This message is an attach request, used to request the establishment of a communication connection with satellite 1. The attach request includes relevant information about the terminal, such as its identifier. Upon receiving the attach request, MME1, since the terminal's HSS is on the ground, does not know whether the terminal is legitimate, and therefore replies with an attach reject, denying the terminal's network access. Optionally, satellite 1 includes a monitoring list and / or a wait timer in the attach reject. The monitoring list indicates one or more satellites that will subsequently cover the terminal. The monitoring list includes the satellite identifier (satellite ID), or the identifier of the base station deployed on the satellite (e.g., eNB ID), or the cell identifier (cell ID) of the cell where the satellite is located. The wait timer is the waiting time for the satellite that will cover the terminal to arrive, for example, the waiting time required for satellite 2 to reach its position at time T4.

[0178] At time T2, Satellite 1 covers the ground gateway station and establishes a connection with the ground core network. Therefore, Satellite 1 forwards the information sent by the terminal to MME1 at time T1 to the corresponding ground core network element. For example, MME1 sends the information sent by the terminal to MME1 to the HSS so that the HSS can authenticate the terminal.

[0179] At time T3, satellite 2 connects to the gateway station. At this time, the core network sends the terminal's context (the terminal's registration information) on the core network side to the MME2 deployed on satellite 2. The MME2 stores the terminal's context, which is the terminal information after authentication by the core network. In other words, when satellite 2 connects to the gateway station, it obtains the authenticated registration information of the terminal.

[0180] At time T4, satellite 2 covers the terminal, and the terminal sends an attach request to MME2 again. The terminal includes its subscription permanent identifier (SUPI) in the attach request. Based on the terminal's SUPI, MME2 can determine that the terminal's context was synchronized to MME2 at time T3, meaning that MME2 has stored the terminal's registration information. Therefore, MME2 replies with "attach accept" to allow the terminal to access the network. The terminal can then transmit uplink and / or downlink data with MME2, and the terminal's uplink data is stored on MME2. When data transmission is complete, or when satellite 2 is about to leave the terminal, eNB2 sends a radio resource control release (RRC Release) to the terminal, releasing the terminal to an idle state. Optionally, MME2 can continue to indicate to the terminal via a monitoring list the satellites that will subsequently cover the terminal, and / or the wait timers of those satellites. In this case, the access network side (eNB2) no longer has the terminal's context, but the core network side (MME2) considers the terminal to still be in the registered state.

[0181] When Satellite 2 subsequently covers the gateway station again, it can send the stored uplink data from the terminal to the terrestrial data network. Optionally, when the next satellite (such as Satellite 3) connects to the gateway station, the core network can back up the terminal's context on the core network side to MME3, and the data network can send downlink data destined for the terminal to MME3. In other words, MME3 stores the downlink data to be sent to the terminal when it connects to the core network. After Satellite 3 covers the terminal, since the terminal has already registered, it can directly initiate a service request to MME3 without needing to send an attach request again.

[0182] As can be seen, in S&F, when an older satellite leaves, it can indicate the monitoring list of satellites that will subsequently cover the terminal, and / or a wait timer. Furthermore, for a Split MME architecture, satellites in the monitoring list need to have the terminal's registration information for the terminal to successfully attach. How does an older satellite determine which new satellites will provide the implementation with the terminal's registration information? For example, an older satellite might assume that if, between the time it covers the gateway station and the time a new satellite covers the terminal, the new satellite will also cover the gateway station at least once, then the new satellite has a chance to obtain the terminal's registration information from the ground core network.

[0183] In other words, for a split MME architecture, all satellites indicated by monitoring list #1 (e.g., satellites 1, 2, 3, and 4) need to have terminal registration information so that the terminal can successfully join the network after connecting to a satellite indicated by monitoring list #1. However, if some unexpected situation occurs that causes a satellite in monitoring list #1 to not obtain terminal registration information (e.g., satellite 1's feeder link deteriorates, preventing satellite 1 from obtaining terminal registration information from the ground, or satellite 1 does not have enough storage space to save terminal registration information), then when the terminal connects to that satellite, the satellite will consider this terminal to be a first-time connection terminal or a terminal that has not connected to the core network, and will reassign the terminal to monitoring list #2 (monitoring list #2 indicates satellites 6, 7, 8, and 9). Therefore, the terminal will subsequently connect to satellites 6, 7, 8, and 9 as indicated by monitoring list #2, but will not connect to satellites 2, 3, and 4 as indicated by monitoring list #1. Consequently, the terminal's data stored on satellites 2, 3, and 4 cannot be sent to the terminal, resulting in data packet loss and a waste of storage resources due to the terminal's data being stored on satellites 2, 3, and 4.

[0184] The embodiments of this application are described in detail below with reference to the accompanying drawings. The embodiments of this application use a terminal device and a network device as examples to illustrate the corresponding methods. For example, the terminal device in the embodiments of this application may be... Figure 1 The terminal device shown can be a network device in a split MME architecture, and this network device includes access network equipment and MME, such as an eNB and an MME. However, this application does not limit the subject executing the method. For example, the terminal device in the method can also be a processor, module, chip, chip system, or software module that supports the implementation of the corresponding method.

[0185] This application provides a communication method 100. Figure 10 This is an interactive schematic diagram of the communication method 100. The communication method 100 is described from the perspective of the interaction between the terminal device and the network device. The communication method 100 includes, but is not limited to, the following steps:

[0186] S1001. The terminal device determines that a first list and / or a first waiting time have been configured, the first list including information about one or more network devices that will soon cover the terminal device, and the first waiting time is the duration for which the terminal device waits to be covered by one or more network devices.

[0187] The first list refers to the monitoring list mentioned above, or the satellite monitoring list. The first waiting time refers to the wait timer mentioned above.

[0188] Information for each network device in one or more network devices may include the identifier of the satellite corresponding to that network device, the cell identifier of the cell where the network device is located, or the identifier of the network device itself. The satellite corresponding to the network device refers to the satellite on which the network device is deployed. For example, if network device 1 includes eNB 1 and MME 1, and eNB 1 and MME 1 are deployed on satellite 1, then the satellite corresponding to network device 1 is satellite 1. The cell where the network device is located refers to the cell where the access network equipment in that network device is located, such as the cell where eNB 1 in network device 1 is located. The identifier of the network device refers to the identifier of the access network equipment in that network device, such as the identifier of eNB 1 in network device 1. For example, in a communication scenario with a split MME architecture, the first list may include the satellite ID, or the eNB ID, or the cell ID.

[0189] The first list includes information about one or more network devices that will be covered by the terminal device; therefore, the first list indicates the coverage area that will be covered by one or more network devices. For example, the monitoring list indicates the coverage area that will be covered by one or more satellites.

[0190] The first waiting time is the duration during which a terminal device waits to be covered by one or more network devices. Each first waiting time corresponds to the duration during which the terminal device waits to be covered by a single network device. When the terminal device determines that a first list and a first waiting time have been configured, the terminal device has been configured with one or more first waiting times. Each configured first waiting time corresponds to a network device indicated by the first list; that is, each configured first waiting time is the duration during which the terminal device waits to be covered by a network device indicated by the first list. Alternatively, when the terminal device determines that a first waiting time has been configured, the terminal device has been configured with one or more first waiting times, each of which corresponds to one or more network devices. Each of these one or more first waiting times is the duration during which the terminal device waits for a network device to cover the terminal device.

[0191] In addition, the first waiting time is the time during which the terminal device waits to be covered by one or more network devices. Thus, the first waiting time also indicates the coverage area of ​​one or more network devices that will soon cover the terminal device. In other words, the first waiting time corresponds to one or more network devices that will soon cover the terminal device.

[0192] The first list and / or first waiting time may be configured by a network device for a terminal device when the terminal device first accesses it (for the first time) without obtaining the terminal device's registration information, so that the terminal device can subsequently request access to one or more network devices indicated by the first list and / or first waiting time. The one or more network devices indicated by the first list and / or first waiting time are network devices whose coverage area, based on ephemeris information, is determined to be close to covering the terminal device, and will cover network devices connected to the gateway station and core network before covering the terminal device. The coverage area will be close to covering the terminal device, and will cover network devices connected to the gateway station and core network before covering the terminal device. Before covering the terminal device, the registration information of the terminal device can be obtained from the core network side. Therefore, if the probability of successful access for the terminal device is high, these network devices are indicated in the first list and / or first waiting time to increase the probability of successful access.

[0193] For example, when a terminal device requests access to network device #a for the first time, if network device #a does not obtain the terminal device's registration information, then network device #a configures a first list for the terminal device. Each of the one or more network devices indicated in the first list will cover the gateway station and connect to the core network before covering the terminal device, and can obtain the terminal device's registration information from the core network side.

[0194] In addition, each of the one or more network devices in the first list and / or the first waiting duration indication, when the overlay gateway station is connected to the core network, also stores data that needs to be sent to the terminal device in communication with the core network. For ease of explanation, this data will be referred to as the data of the terminal device below.

[0195] S1002. The terminal device sends first indication information to the first network device, the first indication information indicating that the terminal device has been configured with a first list, and / or indicating that the terminal device has been configured with a first waiting time. Accordingly, the first network device receives the first indication information from the terminal device.

[0196] The first network device is the network device that the terminal device is currently requesting access to, and it is also one of the one or more network devices in the first list and / or the first waiting time indication, or in other words, the first network device is included in the one or more network devices in the first list and / or the first waiting time indication. Therefore, the terminal device is currently requesting access to the first network device in the one or more network devices in the configured first list and / or the first waiting time indication.

[0197] In one possible approach, the first indication information is used to indicate that the terminal device has been configured to cover one or more network devices that are about to cover the terminal device. Specifically, the first indication information can indicate that the terminal device has been configured to cover one or more network devices by indicating that the terminal device has been configured to a first list and / or a first waiting time.

[0198] Understandably, if a terminal device determines that it has been configured with a first list and / or a first waiting time, or in other words, if it determines that it has been configured with a first list and / or a first waiting time, and there are still network devices among the one or more network devices indicated by the first list and / or the first waiting time that do not cover the terminal device, the terminal device can know that the one or more network devices indicated by the first list and / or the first waiting time may have obtained or will soon be able to obtain the terminal device's registration information, thus increasing the probability of successfully accessing the network devices indicated by the first list and / or the first waiting time. Therefore, if the terminal device does not expect the first network device currently requesting access to reconfigure the list and / or waiting time for indicating one or more network devices that will soon cover the terminal device, the terminal device sends a first indication message to the first network device, informing the first network device of the configured first list and / or first waiting time, so that the first network device will not reconfigure the list and / or waiting time for the terminal device if it has not obtained the terminal device's registration information.

[0199] In other words, the first indication information sent by the terminal device to the first network device is used by the first network device to determine whether to configure a list of one or more network devices indicating that the terminal device will be covered and / or a waiting time for the first network device. This method is beneficial because even if the terminal device fails to successfully access the first network device, or fails to successfully establish a communication connection with the first network device, it can still request access from one or more network devices in the first list and / or the network device indicated by the first waiting time. This allows one or more network devices in the first list and / or the network device indicated by the first waiting time to send the data of the terminal device that they have stored, reducing the probability of data packet loss. In addition, the fact that the terminal device can continue to request access from the network devices in the first list and / or the network device indicated by the first waiting time can reduce the resource waste caused by the network devices storing the registration information and data of the terminal device when the terminal device fails to access the network devices in the first list and / or the network device indicated by the first waiting time.

[0200] For example, if the network device currently requesting access from a terminal device is satellite 1, which is deployed with an MME and an eNB, and the terminal device has been configured with a monitoring list, which includes information about one or more satellites that will soon cover the terminal device, or if there are satellites among the one or more satellites indicated by the monitoring list that do not yet cover the terminal device, then the terminal device sends a first indication message to satellite 1. This first indication message indicates that the terminal device has been configured with a monitoring list, so that satellite 1 will not configure a new monitoring list for the terminal device without obtaining its registration information. Furthermore, even if the terminal device fails to establish a connection with satellite 1, it can still request access from satellites among the one or more satellites indicated by the configured monitoring list, reducing the probability of data packet loss and the waste of storage resources.

[0201] In one optional implementation, the first indication information can be expressed as bit information, indicating that the terminal device has been configured into the first list. For example, the first indication information can be a 1-bit indication bit, where a 1-bit value indicates that the terminal device has been configured into the first list, or a 0-bit value indicates that the terminal device has been configured into the first list.

[0202] In one optional implementation, when the first indication information includes a first list, it is used to indicate that the terminal device has been configured with the first list. Alternatively, the first indication information can display an indication that the terminal device has been configured with the first list by including the first list itself.

[0203] In another optional implementation, when the first indication information is specifically used to indicate that the first list includes information about other network devices besides the first network device, it is used to indicate that the terminal device has been configured in the first list. When the first indication information is used to indicate that the first list includes information about other network devices besides the first network device, it indicates that the first list also includes information about other network devices that will cover the terminal device, which can implicitly indicate that the terminal device has been configured in the first list.

[0204] In another optional implementation, the first indication information is specifically used to indicate that the terminal device is the Nth terminal device requesting network access, and to indicate that the terminal device has been configured with a first list and / or a first waiting time. N is an integer greater than 1. When the first indication information indicates that the terminal device is the Nth terminal device requesting network access, it indicates that the terminal device is not accessing for the first time (not the first time), and can implicitly indicate that the terminal device has been configured with a first list and / or a first waiting time before requesting access to the first network device.

[0205] In another optional implementation, when the first indication information includes a first waiting duration, it is used to indicate that the terminal device has been configured with a first waiting duration. Alternatively, the first indication information can display that the terminal device has been configured with a first waiting duration by including the first waiting duration.

[0206] As can be seen, the first instruction information can indicate that the terminal device has been included in the first list, either explicitly or implicitly, which can improve the flexibility of the instruction.

[0207] For example, the first network device that the terminal device is currently requesting access to is satellite 1, which is equipped with an MME and an eNB, and the terminal device has been configured with a monitoring list. The terminal device sends a first indication message carrying the monitoring list to satellite 1, or sends a first indication message indicating that the monitoring list includes information about other satellites besides satellite 1, such as sending a first indication message including the identifier of satellite 2, or sending a first indication message indicating that the terminal device is not requesting access for the first time, so as to indicate to satellite 1 that the terminal device has been configured with a monitoring list.

[0208] In one optional implementation, the first indication information is carried in the access request of the terminal device. This access request is used to request the establishment of a communication connection with the first network device, or in other words, to request access to the first network device. The access request can be, for example, an attach request, a service request, or a TAU message. This approach can reduce signaling overhead.

[0209] In one optional implementation, the terminal device directly sends a NAS message to the MME in the first network device. The NAS message carries first indication information, and the NAS message may be, for example, an attach request, a service request, or a tracking area update (TAU) message. The NAS message sent by the terminal device to the MME in the first network device is transparently transmitted through the access network equipment in the first network device, such as through an eNB.

[0210] In another optional implementation, the terminal device may send an access stratum (AS) message to the access network device in the first network device. The AS message carries first indication information. After parsing the AS message, the access network device sends the first indication information to the MME in the first network device through the S1 interface; or, after parsing the AS message, the access network device sends indication information to the MME in the first network device through the S1 interface indicating that a second list and / or wait timer are not configured. The wait timer is the wait timer corresponding to each network device in the second list, or the wait timer corresponding to the next network device that will cover the terminal device. The wait timer corresponding to the network device indicates the duration for which the terminal device waits for the network device to cover the terminal device.

[0211] It is evident that the terminal device can send a first indication message to the MME in the first network device currently requesting access, either directly or indirectly, to indicate that the terminal device has been configured with a first list and / or a first waiting time.

[0212] In one optional implementation, the terminal device sends a first indication message to a first network device, including: sending the first indication message to the first network device when a first condition is met. The first condition includes: no failure to establish a communication connection with all network devices indicated in the first list has occurred; or, the first condition includes: no failure to establish a communication connection with all network devices other than the first network device among one or more network devices indicated in the first list has occurred.

[0213] Specifically, the failure to establish communication connections with all network devices indicated in the first list does not occur. For example, the terminal device may have successfully established communication connections with some or all of the network devices indicated in the first list, or the terminal device may not have yet requested to establish communication connections with some of the network devices indicated in the first list. Similarly, the failure to establish communication connections with all network devices other than the first network device among one or more network devices indicated in the first list does not occur. For example, the terminal device may have successfully established communication connections with some or all of the network devices other than the first network device among one or more network devices indicated in the first list, or the terminal device may not have yet requested to establish communication connections with some of the network devices other than the first network device among one or more network devices indicated in the first list.

[0214] In one optional implementation, the terminal device does not send the first indication information to the first network device when the first condition is not met. That is, if the terminal device fails to establish a communication connection with all network devices indicated by the first list, or if the terminal device fails to establish a communication connection with all network devices other than the first network device among one or more network devices indicated by the first list, the terminal device will not send the first indication information to the first network device. This approach allows the first network device to configure a list and / or waiting time for the terminal device without obtaining the terminal device's registration information. Furthermore, it allows the terminal device to request access from the network devices indicated by the list and / or waiting time specified by the first network device when it fails to establish a communication connection with all network devices indicated by the first list, and all network devices indicated by the first list already cover the terminal device.

[0215] Optionally, if the terminal device fails to establish a communication connection with all network devices indicated by the first list, or fails to establish a communication connection with all network devices other than the first network device among one or more network devices indicated by the first list, and the first network device is the last network device to cover the terminal device among one or more network terminals indicated by the first list, the terminal device shall not send the first instruction information to the first network device, so that the first network device can configure the list and / or waiting time for the terminal device without obtaining the registration information of the terminal device.

[0216] In one optional implementation, if the first condition is not met, the terminal device deletes the first list and / or the first waiting time. If the first condition is not met, it indicates that the terminal device has been rejected from network access by all network devices indicated in the first list. In this case, the terminal device deletes the first list and / or the first waiting time, and subsequently reselects a network device for access. This method can free up the terminal device's storage resources.

[0217] In another optional implementation, the terminal device sends a first indication message to the first network device through a first cell under the first network device, including: sending the first indication message to the first network device through the first cell under the first network device when a second condition is met. The second condition includes: receiving a fourth indication message from the first cell under the first network device, the fourth indication message indicating that the first cell under the first network device is operating in store-and-forward mode, and / or indicating that the first cell under the first network device allows a store-and-forward type terminal device to reside or access the network.

[0218] The fourth indication information is used to indicate that the first cell under the first network device is operating in store-and-forward mode, and / or to indicate that the first cell under the first network device allows a store-and-forward type terminal device to reside or access, indicating that the terminal device can access the first network device through the first cell. Then, the terminal device sends the first indication information to the first network device through the first cell, so that the first network device will no longer configure a list of one or more network devices that will soon cover the terminal device and / or a waiting time for the terminal device without obtaining the registration information of the terminal device. This helps to reduce the probability of data packet loss and the waste of storage resources.

[0219] In another optional implementation, if the second condition is not met, the terminal device does not send the first indication information to the first network device through the first cell under the first network device. When the second condition is not met, it indicates that the first cell under the first network device may not be operating in store-and-forward mode, or that the terminal device is not allowed to access the first cell under the first network device. In this case, the terminal does not send the first indication information to the first network device to save signaling overhead.

[0220] In another optional implementation, the terminal device sends a first indication message to the first network device, including: sending the first indication message to the first network device through a first cell under the first network device when both the first condition and the second condition are met.

[0221] When the terminal device can determine that the first network device is not the last network device covering the terminal device among one or more network terminals indicated by the first list, and the terminal device can access the first network device, the terminal device sends a first indication information to the first network device so that the first network device knows that the terminal device has been configured with the first list and / or the first waiting time, thereby helping the first network device not to configure a new list and / or waiting time for the terminal device.

[0222] S1003. The first network device determines, based on the first indication information, not to configure a second list and / or a second waiting time for the terminal device, wherein the second list includes information on one or more network devices that will soon cover the terminal device, and the second waiting time is the duration for which the terminal device waits to be covered by one or more network devices.

[0223] In one optional implementation, the first network device determines, based on the first indication information, not to configure the second list and / or the second waiting time for the terminal device, including: in the absence of obtaining the registration information of the terminal device, determining, based on the first indication information, not to configure the second list and / or the second waiting time for the terminal device.

[0224] Understandably, since the first network device is one or more network devices in the first list and / or the first waiting time indication, the first network device can obtain the registration information of the terminal device from the core network side before covering the terminal device. However, if some unexpected situation occurs, such as the first network device failing to obtain the registration information of the terminal device from the core network side due to deterioration of the power supply link between the first network device and the core network side, the first network device will not obtain the registration information of the terminal device and therefore will not allow the terminal device to access.

[0225] Based on the received first indication information, the first network device can determine that the terminal device has been configured with a first list and / or a first waiting time. Therefore, the first network device assumes that each of the one or more network devices indicated by the first list and / or the first waiting time has obtained the terminal device's registration information and stored data to be sent to the terminal device before being overridden. Thus, if the first network device does not obtain the terminal device's registration information, or in other words, if it determines that the terminal device is not allowed to access, it determines not to configure a second list and / or a second waiting time for the terminal device. This allows the terminal device to continue requesting access to the one or more network devices indicated by the first list and / or the first waiting time, which is beneficial for the network devices indicated by the first list and / or the first waiting time to send the stored data of the terminal device to the terminal device, reducing the probability of data packet loss.

[0226] In addition, the ability of the terminal device to continue requesting access to network devices in the first list and / or the first waiting time indication can reduce the resource waste caused by the network devices storing the terminal device's registration information and data when the terminal device does not subsequently access the network devices in the first list and / or the first waiting time indication.

[0227] In an optional implementation, when the first indication information is carried in the access request, the first network device may also send an access response to the terminal device. The access response indicates that the communication connection between the terminal device and the first network device has failed to be established, and the access response does not carry the second list and / or the second waiting duration. Accordingly, the terminal device further performs the following steps: receiving the access response from the first network device; determining the second network device to be requested for access, wherein the second network device is included in one or more network devices indicated by the first list, or the second network device is the network device corresponding to the first waiting duration. Alternatively, the second network device is a network device different from the first network device among one or more network devices indicated by the first list and / or the first waiting duration.

[0228] When a first network device receives an access request from a terminal device without obtaining the terminal device's registration information, it sends an access response to the terminal device indicating that the communication connection establishment has failed. Furthermore, since the first network device also knows from the first indication information in the access request that the terminal device has been configured with a first list and / or a first waiting time, the access response sent by the first network device to the terminal device does not carry the second list and / or second waiting time that the first network device has reconfigured. Therefore, the terminal device can still determine the network device to be accessed from one or more network devices indicated by the first list and / or the first waiting time. This method is beneficial because even after the terminal device fails to establish a communication connection with the first network device, it can still access one or more network devices indicated by the first list and / or the first waiting time, thereby enabling those one or more network devices to send stored data of the terminal device to the terminal device, reducing the probability of data packet loss and resource waste.

[0229] Optionally, the MME in the first network device can directly send a NAS message to the terminal device. The NAS message carries an access response, and the access network device in the first network device transparently transmits the NAS message sent by the MME to the terminal device. Optionally, the MME in the first network device sends an S1 message to the access network device in the first network device. The S1 message carries an access response; after being parsed by the access network device, the access network device then sends the access response to the terminal device via an AS message (such as an RRC message).

[0230] In one optional implementation, the first network device further releases information about the terminal device. This information refers to information sent by the terminal device to the first network device regarding the terminal device, such as the terminal device's identifier, access request, and reason for access request. This method allows the first network device to avoid requesting the terminal device's registration information again when covering the gateway station and core network connection after covering the terminal device, thus reducing duplicate registration of the terminal device, minimizing potential erroneous registrations, and reducing signaling overhead.

[0231] Optionally, when the terminal device's coverage area covers the terminal device, the terminal device requests access from the second network device. Specifically, when the terminal device's coverage area covers the terminal device, the terminal device sends an access request to the second network device. This access request is used to request the establishment of a communication connection with the second network device, or in other words, the access request is used to request access to the second network device. Optionally, the access request sent by the terminal device to the second network device carries first indication information so that the second network device knows that the terminal device has been configured in a first list.

[0232] In one optional implementation, the first list does not include information about one or more third network devices, which are network devices that have not obtained registration information from the terminal device. In other words, the first list configured for the terminal device does not include information about one or more third network devices that have not obtained registration information from the terminal device, thereby helping the terminal device avoid accessing one or more third network devices that have not obtained registration information from the terminal device, and reducing the probability of the terminal device failing to access the network.

[0233] In another optional implementation, the terminal device may further perform the following steps: receiving second indication information, the second indication information being used to indicate a third list, the third list including information about a fourth network device, the fourth network device being one or more third network devices that have obtained the registration information of the terminal device; and determining a fifth network device to request access, the fifth network device being included in the fourth device.

[0234] It is evident that the first list configured for the terminal device does not include information on one or more third network devices that have not previously obtained the terminal device's registration information, while the reconfigured third list includes information on one or more fourth network devices that have obtained the terminal device's registration information. This approach is beneficial for the terminal device to subsequently request access from the fourth network device that has obtained the terminal device's registration information, thereby increasing the probability of successful access for the terminal device and reducing the probability of data packet loss.

[0235] As can be seen, in the SF scenario, if the network device currently requesting access from the terminal device is aware that the terminal device has already been configured with a first list and / or a first waiting time, it will not configure a new second list and / or a second waiting time for the terminal device. Therefore, even if the terminal device fails to access the first network device, it can still request access from one or more network devices indicated by the first list and / or the first waiting time. This facilitates the ability of these one or more network devices to send the terminal device's stored data, reducing the probability of data packet loss.

[0236] In addition, the ability of the terminal device to continue requesting access to network devices in the first list and / or the first waiting time indication can reduce the resource waste caused by the network devices storing the terminal device's registration information and data when the terminal device does not subsequently access the network devices in the first list and / or the first waiting time indication.

[0237] The embodiments of this application are also based on the foregoing. Figure 10 The communication method 100 shown takes a satellite 1, which includes an eNB and an MME, as an example, where the first network device is a satellite 1 and the satellite 1 has not obtained the registration information of the terminal device. This method can be found in [link to relevant documentation]. Figure 11As shown, its interaction process includes, but is not limited to, the following steps:

[0238] S1101. The terminal device sends an attach request to satellite 1, the attach request carrying first indication information. Correspondingly, satellite 1 receives the attach request from the terminal device.

[0239] The "attach request" is used to request access to satellite 1, or in other words, to request the establishment of a communication connection with satellite 1. The first indication information indicates that the terminal device has been configured with a monitoring list and / or a wait timer. The monitoring list includes information about one or more satellites that will soon cover the terminal device, and the wait timer is the duration the terminal device waits to be covered by one or more satellites. Satellite 1 is included in the one or more satellites indicated by the monitoring list and / or wait timer. The first indication information is as described in S1001 above and will not be repeated here. The information for each of the one or more satellites can be referred to in S1001 above, as is the information for each of the one or more network devices, and will not be repeated here.

[0240] In addition, the implementation method for the terminal device to send an attach request to satellite 1 can refer to the implementation method in S1001 above, in which the terminal device sends a first instruction information to the first network device, and will not be repeated here.

[0241] S1102. Satellite 1 sends an attach reject to the terminal device. The attach reject indicates that the terminal device's access has failed, and the attach reject does not carry a monitoring list and / or wait timer. Accordingly, the terminal device receives the attach reject from Satellite 1.

[0242] Understandably, since Satellite 1 has not obtained the registration information of the terminal device and cannot determine whether the terminal device is legitimate, it sends an attach reject to the terminal device to inform it that the connection to Satellite 1 has failed. Furthermore, Satellite 1, through the first indication information in the attach request, learns that the terminal device has been configured with a monitoring list and / or wait timer. To ensure that the terminal device can still connect to the satellites indicated by the configured monitoring list and / or wait timer, it determines not to configure a new monitoring list and / or wait timer for the terminal device. Therefore, the attach reject sent by Satellite 1 to the terminal device does not carry the newly configured monitoring list and / or wait timer, so that the terminal device can subsequently continue to connect to one or more satellites indicated by the configured monitoring list and / or wait timer. This, in turn, allows one or more satellites indicated by the configured monitoring list and / or wait timer to send the stored data of the terminal device to the terminal device, reducing the probability of data packet loss and the waste of storage resources.

[0243] In addition, the implementation method of satellite 1 sending attach reject to terminal device can refer to the implementation method of the first network device sending access response to terminal device in S1003 above, and will not be repeated here.

[0244] In an optional implementation, satellite 1 can also release the terminal device's information, which can be found in S1003 above and will not be repeated here. This method allows satellite 1 to reconnect with the gateway station and core network without requesting the terminal device's registration information, reducing the possibility of erroneous registration and signaling overhead.

[0245] S1103. The terminal device determines the satellite 2 to be requested for access, which is included in one or more satellites indicated by the configured monitoring list and / or wait timer.

[0246] Understandably, if the terminal device learns from the attach reject from satellite 1 that it has failed to connect to satellite 1 and has not received a reconfigured monitoring list and / or wait timer from satellite 1, it will continue to determine the satellite 2 to be requested for access from one or more satellites indicated by the configured monitoring list and / or wait timer. That is, satellite 2 is one of one or more satellites indicated by the configured monitoring list and / or wait timer.

[0247] In one alternative implementation, the terminal device requests access from satellite 2 when satellite 2 covers the terminal device.

[0248] Understandably, when the terminal device is within the coverage area of ​​satellite 2, it sends an access request to satellite 2, such as an attach request, to request access to satellite 2.

[0249] Optionally, when the terminal device sends an access request to satellite 2, if there are still satellites that do not cover the terminal device among one or more satellites indicated by the configured monitoring list and / or wait timer, the access request sent to satellite 2 may carry first indication information so that satellite 2 will not configure a new monitoring list and / or wait timer for the terminal device without obtaining the terminal device's registration information.

[0250] As can be seen, satellite 1, which the terminal device is currently requesting access to but has not yet obtained the terminal device's registration information, learns from the first indication information in the terminal device's attach request that the terminal device has been configured with a monitoring list and / or wait timer. Therefore, the attach reject sent to the terminal device does not carry a new monitoring list and / or wait timer. Consequently, the terminal device continues to request access from one or more satellites indicated by the configured monitoring list and / or wait timer. This benefits the satellites indicated by the monitoring list and / or wait timer by enabling them to send the terminal device's stored data, reducing the probability of data packet loss and minimizing the waste of storage resources.

[0251] This application provides a communication method 200. Figure 12This is an interactive schematic diagram of the communication method 200. The communication method 200 is also described from the perspective of the interaction between the terminal device and the first network device. The communication method 200 includes, but is not limited to, the following steps:

[0252] S1201. The terminal device sends an access request to the first network device, the access request being used to request the establishment of a communication connection with the first network device. Correspondingly, the first network device receives the access request from the terminal device.

[0253] The first network device is the network device whose coverage currently covers the terminal device, so that the terminal device sends an access request to the first network device to request the establishment of a communication connection with the first network device.

[0254] In addition, the access request can be an attach request, a service request, or a TAU message.

[0255] In one optional implementation, the path by which the terminal device sends an access request to the first network device can refer to the path by which the terminal device sends the first indication information to the first network device in S1002 above, and will not be repeated here.

[0256] S1202. The first network device sends a second list and / or a second waiting duration to the terminal device. The second list includes information about one or more network devices that will soon cover the terminal device, and the second waiting duration is the duration during which the terminal device waits to be covered by one or more network devices. Accordingly, the terminal device receives the second list and / or the second waiting duration from the first network device.

[0257] The information for each of the one or more network devices can be found in S1001 above, and will not be repeated here. The second list and the second waiting time can be found in S1001 above, specifically the first list and the first waiting time, and will not be repeated here.

[0258] In one optional implementation, the first network device sends a second list and / or a second waiting time to the terminal device, including: the first network device sending the second list and / or the second waiting time to the terminal device without obtaining the terminal device's registration information. When the first network device receives an access request from the terminal device, since it has not obtained the terminal device's registration information, it cannot determine whether the terminal device is legitimate, and therefore does not allow the terminal device to request access, i.e., it determines that the communication connection between the terminal device and the first network device has failed to be established. In this method, the first network device configures a second list and / or a second waiting time for the terminal device to indicate to the terminal device one or more network devices that will soon cover the terminal device. This is beneficial for the terminal device to subsequently request access to one or more network devices that will soon cover the terminal device, increasing the probability of successful access for the terminal device.

[0259] In one optional implementation, the path by which the first network device sends the second list and / or the second waiting time to the terminal device can be referred to the path by which the first network device sends the access response to the terminal device in S1003 above, and will not be repeated here.

[0260] In an optional implementation, the first network device further sends an access response to the terminal device, the access response indicating that the communication connection between the terminal device and the first network device failed to be established. This allows the terminal device to know that the communication connection with the first network device has failed based on the access response. Optionally, the access response may be an attachreject, a service reject, or a TAU reject message.

[0261] In one optional implementation, if the first network device also sends an access response to the terminal device, the second list and / or the second waiting duration can be carried in the access response, which can save signaling overhead.

[0262] S1203. The terminal device, in the case of a configured first list and / or a first waiting time, determines a second network device to be requested for access, wherein the second network device is included in one or more network devices indicated in the first list, or the second network device is the network device corresponding to the first waiting time.

[0263] Understandably, if the terminal device fails to establish a connection with the first network device, it receives a second list and / or a second waiting duration configured by the first network device for the terminal device. However, before receiving the second list and / or the second waiting duration, the terminal device has already been configured with a first list and / or a first waiting duration. In order for one or more network devices indicated by the first list and / or the first waiting duration to send the stored data of the terminal device to the terminal device, the terminal device still requests access from the network devices in the one or more network devices indicated by the first list and / or the first waiting duration. Therefore, even if the terminal device receives the second list and / or the second waiting duration configured by the first network device, the terminal device still determines the second network device to be requested for access from the one or more network devices indicated by the configured first list and / or the first waiting duration; that is, the determined second network device to be requested for access is included in the one or more network devices indicated by the first list and / or the first waiting duration.

[0264] Alternatively, even if a terminal device receives a second list and / or a second waiting time configured for it by a first network device, it can ignore the second list and / or the second waiting time, or not use the second list and / or the second waiting time, or not request access from the network devices in the one or more network devices indicated by the second list and / or the second waiting time, but instead request access from the network devices in the one or more network devices indicated by the first list and / or the first waiting time. This method enables the network devices in the one or more network devices indicated by the first list and / or the first waiting time to send the terminal device's stored data, reducing the probability of data packet loss and the waste of storage resources.

[0265] In one alternative implementation, the terminal device may also delete the second list and / or the second waiting time to free up storage resources.

[0266] In an optional implementation, the terminal device may further send a third indication message to the first network device, the third indication message being used to instruct the first network device to release the terminal device's information. Correspondingly, the first network device further performs the following steps: receiving the third indication message from the terminal device; and releasing the terminal device's information based on the third indication message. The terminal device's information is as described in S1003 above and will not be repeated here. This method allows the first network device to avoid requesting the terminal device's registration information based on the terminal device's information when it covers the gateway station and core network connection again after covering the terminal device, thus reducing duplicate or erroneous registration of the terminal device and decreasing signaling overhead.

[0267] Optionally, the third indication information can be an AS message, such as msg1, msg3, or msg5 for random access. In this mode, after receiving the AS message, the access network device in the first network device can forward it to the MME in the first network device through the S1 interface.

[0268] Optionally, the third indication information can also be a NAS message, such as an attach request, service request, or TAU message. In this mode, the NAS message sent by the terminal device to the MME in the first network device is transparently transmitted through the access network device.

[0269] In another optional implementation, if the first network device, after covering the terminal device, reconnects to the gateway station and core network, and then covers the terminal device again, it can determine internally on the core network side not to re-register or update the registration of the terminal device. For example, if the core network sends an instruction to the first network device indicating that it will not store the registration information of the terminal device after covering the terminal device, then the first network device will not store the registration information of the terminal device, i.e., it will not re-register or update the registration of the terminal device. As another example, if the first network device requests the registration information of the terminal device from the core network after covering the terminal device and the request fails, i.e., the registration of the terminal device fails, then it is determined not to re-register or update the registration of the terminal device.

[0270] In an optional implementation, the third indication information is further used to indicate that the terminal device has been configured with a first list and / or a first waiting duration. This allows the first network device to know that the terminal device has been configured with a first list and / or a first waiting duration, thereby knowing that the terminal device may not use the second list and / or a second waiting duration configured by the first network device for the terminal device. This method also facilitates the terminal device to request access from the first network device again, and when the first network device determines that the terminal device's access has failed, it will not configure a new list and / or waiting duration for the terminal device, so that the terminal device can continue to request access from one or more network devices indicated by the first list and / or the first waiting duration, which can reduce the probability of data packet loss and the waste of storage resources.

[0271] Optionally, the third indication information includes the first list. Optionally, the third indication information is specifically used to indicate that the first list includes information about other network devices besides the first network device. Optionally, the third indication information is specifically used to indicate that the terminal device is the terminal device requesting network access for the Nth time. Optionally, the third indication information includes a first waiting time. For a detailed implementation of this third indication information, please refer to the description in S1002 above, and will not be repeated here.

[0272] In one optional implementation, the first list does not include information on one or more third network devices, which are network devices that have not obtained registration information from the terminal device. This implementation is similar to that described in S1003 above and will not be repeated here.

[0273] In an optional implementation, the terminal device may further perform the following steps: receiving second indication information, the second indication information being used to indicate a third list, the third list including information about a fourth network device, the fourth network device being one or more third network devices that have obtained the registration information of the terminal device; and determining a fifth network device to request access, the fifth network device being included in the fourth network device. This implementation is as described in S1003 above and will not be repeated here.

[0274] As can be seen, in the SF scenario, even if the first network device currently requesting access reconfigures the second list and / or the second waiting time for the terminal device after the terminal device has been configured with the first list and / or the first waiting time, the terminal device will still request access from one or more network devices indicated by the first list and / or the first waiting time. Therefore, the network devices in the one or more network devices indicated by the first list and / or the first waiting time can send the terminal device's stored data, reducing the probability of data packet loss.

[0275] In addition, the ability of the terminal device to continue requesting access to network devices in the first list and / or the first waiting time indication can reduce the resource waste caused by the network devices storing the terminal device's registration information and data when the terminal device does not subsequently access the network devices in the first list and / or the first waiting time indication.

[0276] The embodiments of this application are also based on the foregoing. Figure 12 The communication method 200 shown takes a satellite 1, which includes an eNB and an MME, as an example, where the first network device is a satellite 1, and the satellite 1 has not obtained the registration information of the terminal device. This method can be found in [link to relevant documentation]. Figure 13 As shown, its interaction process includes, but is not limited to, the following steps:

[0277] S1301. The terminal device sends an attach request to satellite 1, which is used to request access to satellite 1. Correspondingly, satellite 1 receives the attach request from the terminal device.

[0278] Understandably, when the terminal device is within the coverage area of ​​satellite 1, it sends an attach request to satellite 1 to request access to satellite 1.

[0279] S1302. Satellite 1 sends an attach reject to the terminal device. The attach reject indicates that the terminal device's access has failed, and it carries the monitoring list #2 and / or wait timer #2. Accordingly, the terminal device receives the attach reject from Satellite 1.

[0280] Understandably, since Satellite 1 did not obtain the registration information of the terminal device, it could not know whether the terminal device was legitimate. Therefore, Satellite 1 did not allow the terminal device to request access and sent an attach reject message to the terminal device to indicate that the terminal device's access had failed.

[0281] In addition, if the first network device determines that the terminal device's access request has failed, it configures a monitoring list #2 and / or a wait timer #2 for the terminal device. The monitoring list #2 includes information about one or more satellites that will soon cover the terminal device, and the wait timer #2 is the duration for which the terminal device will wait to be covered by one or more satellites. Therefore, the attach reject also carries the monitoring list #2 and / or wait timer #2 configured by satellite 1 for the terminal device. The information of each of the one or more satellites can be referred to the information of each of the one or more network devices in S1002 above, and will not be repeated here.

[0282] S1303. The terminal device, having been configured with monitoring list #1 and / or wait timer #1, determines the satellite 2 to be requested for access, wherein satellite 2 is included in one or more satellites indicated by monitoring list #1 and / or wait timer #1.

[0283] Understandably, even if the terminal device is configured with monitoring list #1 and / or wait timer #1 by the first network device, and is further configured with monitoring list #2 and / or wait timer #2, in order to ensure that one or more satellites indicated by monitoring list #1 and / or wait timer #1 can send the stored data of the terminal device to the terminal device, the terminal device still determines to request access from the satellites in one or more satellites indicated by monitoring list #1 and / or wait timer #1. That is, the determined satellite 2 to be requested for access is included in one or more satellites indicated by monitoring list #1 and / or wait timer #1. Ignoring the use of monitoring list #2 and / or wait timer #2 can reduce the probability of data packet loss and the waste of storage resources.

[0284] Optionally, the terminal device may also send a third instruction message to satellite 1, which instructs satellite 1 to release the terminal device's information. Correspondingly, satellite 1 also performs the following steps: receiving the third instruction message from the terminal device; and releasing the terminal device's information based on the third instruction message. This method allows satellite 1 to avoid requesting the terminal device's registration information when covering the gateway station and core network connection again after covering the terminal device, thus reducing duplicate or erroneous registration of the terminal device and decreasing signaling overhead.

[0285] Optionally, other implementations of the third indication information can be found in S1203 above, and will not be repeated here.

[0286] It is evident that, even if the terminal device receives a reconfigured monitoring list #2 and / or wait timer #2 from satellite 1 after being configured with monitoring list #1 and / or wait timer #1, the terminal device will still request access from one or more satellites indicated by monitoring list #1 and / or wait timer #1. This allows the satellites indicated by monitoring list #1 and / or wait timer #1 to send the stored data of the terminal device to the terminal device, thereby reducing the probability of data packet loss and the waste of storage resources.

[0287] This application also proposes a communication method 300. Figure 14 This is an interactive schematic diagram of the communication method 300. The communication method 300 is described from the perspective of the interaction between the terminal device and the network device. The communication method 300 includes, but is not limited to, the following steps:

[0288] S1401. The first network device sends a first list to the terminal device, the first list including information of one or more sixth network devices, and the first list not including information of one or more third network devices. Accordingly, the terminal device receives the first list from the first network device.

[0289] Among them, one or more sixth network devices are network devices that have obtained or are about to obtain the registration information of the terminal device, and one or more third network devices are network devices that have not obtained the registration information of the terminal device. The first network device is the network device that the terminal device is currently requesting access from.

[0290] In one optional implementation, the first network device sends a first list to the terminal device, including: sending the first list to the terminal device when it has not obtained the registration information of the terminal device, or when it is determined that the terminal device is not allowed to access.

[0291] Understandably, the core network side on the ground can know which network devices have previously failed to send registration information to the terminal device. Therefore, when a network device subsequently connects to the core network side overlaying a gateway station and receives the terminal device's registration information, the core network side can indicate the network devices that previously failed to receive the terminal device's registration information to that network device in the form of a list. Then, before that network device overlays the terminal device and leaves, if it is determined that a list for indicating one or more network devices has been allocated to the terminal device, it is determined not to allocate the terminal device with the network devices that previously failed to receive the terminal device's registration information, and / or not to allocate the terminal device with the corresponding waiting time for those network devices, in order to reduce the probability of the terminal device failing to reconnect to these network devices.

[0292] In other words, when the first network device configures the first list for the terminal device, it considers network devices that have successfully received the terminal device's registration information from the terrestrial core network, and network devices that are about to receive the terminal device's registration information from the terrestrial core network, but does not consider network devices that have previously failed to receive the terminal device's registration information. Therefore, the first list includes information on one or more sixth network devices that have obtained or are about to obtain the terminal device's registration information, but does not include information on one or more third network devices that have not obtained the terminal device's registration information.

[0293] In an optional implementation, the terminal device further performs the following steps: receiving second indication information, the second indication information being used to indicate a third list, the third list including information about a fourth network device, the fourth network device being one or more third network devices that have obtained the registration information of the terminal device; and determining a fifth network device to request access, the fifth network device being included in the fourth network device.

[0294] Understandably, if a network device that previously failed to receive registration information from a terminal device successfully receives the terminal device's registration information after connecting to the ground core network side, the ground core network side will also synchronize this information with other network devices. When other network devices subsequently allocate new lists and / or waiting times for terminal devices, they can configure the network device that successfully received the terminal device's registration information into the list and / or waiting time.

[0295] Therefore, the third list received by the terminal device may include information about fourth network devices that have obtained the terminal device's registration information from one or more third network devices. Furthermore, the terminal device can determine the fifth network device to request access from the fourth network devices indicated by the third list. This approach facilitates the terminal device's subsequent request for access from the fourth network devices that have obtained the terminal device's registration information, reducing the probability of data packet loss.

[0296] In one optional implementation, the terminal device may also request access from the fifth network device when the coverage area of ​​the fifth network device covers the terminal device, for example, by sending an access request to the fifth network device to request access to the fifth network device.

[0297] As can be seen, in the embodiments of this application, the first list configured by the first network device for the terminal device includes information of one or more sixth network devices that have obtained or are about to obtain the registration information of the terminal device, but does not include information of one or more third network devices that have not obtained the registration information of the terminal device. This is beneficial for the terminal device to request access from one or more sixth network devices that have obtained or are about to obtain the registration information of the terminal device, rather than requesting access from one or more third network devices that have not obtained the registration information of the terminal device, thereby increasing the probability of the terminal device successfully accessing the network device.

[0298] This application also proposes a communication method 400. Figure 15 This is a flowchart illustrating the communication method 400. The communication method 400 is described from the perspective of the terminal device. The communication method 400 includes, but is not limited to, the following steps:

[0299] S1501. The terminal device determines whether a fifth indication information exists in the system broadcast message from the first cell under the first network device. The fifth indication information is used to indicate that the first cell is operating in store-and-forward mode, and / or to indicate whether the first cell allows store-and-forward type terminal devices to camp.

[0300] In one optional implementation, the system broadcast message of the first cell under the first network device may be a system information block (SIB) 1 broadcast by the first cell under the first network device.

[0301] Optionally, when the fifth indication information carries a store-and-forward indication (SF indication), the fifth indication information is used to indicate that the first cell under the first network device is operating in store-and-forward mode.

[0302] It should be understood that the first cell under the first network device operates in store-and-forward mode, or the first network device operates in store-and-forward mode, or the first network device is a store-and-forward type network device.

[0303] Optionally, when the fifth indication information carries a cell-barredSF information element, the fifth indication information is used to indicate whether the first cell under the first network device allows a terminal device of the store-and-forward type to camp; or, the fifth indication information is used to indicate whether the first cell under the first network device allows a terminal device of the store-and-forward type to camp or access, and to indicate that the first cell under the first network device is operating in store-and-forward mode.

[0304] Optionally, when the cellbarredSF information carried in the fifth indication information is set to barred, a store-and-forward type terminal device is not allowed / prohibited from camping on a cell or accessing a cell; when the cellbarredSF information carried in the fifth indication information is set to not barred, a store-and-forward type terminal device is allowed / not prohibited from camping on a cell or accessing a cell. For example, if the SIB1 broadcast by the first cell under the first network device carries a cellbarredSF information, and the cellbarredSF information is set to barred, then a store-and-forward type terminal device is prohibited from camping on the first cell under the first network device.

[0305] S1502. In the absence of the fifth instruction information, the terminal device determines whether to allow camping in the first cell based on the non-terrestrial network cell prohibition information from the first cell.

[0306] The non-terrestrial network cell prohibition information can be a non-terrestrial network cell-barred NTN (cellbarredNTN) information element. This cellbarredNTN information element can be broadcast to the terminal device by the first cell under the first network device via a system broadcast message. For example, the first cell under the first network device can broadcast the cellbarredNTN information element to the terminal device via SIB1. Furthermore, non-terrestrial network cell prohibition information can also be referred to as legacy non-terrestrial network cell prohibition information; for example, a cellbarredNTN information element can be called a legacy cellbarredNTN.

[0307] Understandably, if the fifth indication information is not present, the terminal device determines that the first cell under the first network device has not broadcast the fifth indication information via system broadcast message. In this case, the terminal device determines whether to camp on the first cell under the first network device based on the non-terrestrial network cell prohibition information from the first cell under the first network device. This method improves the accuracy of the terminal device's determination of whether to camp on / access the first cell under the first network device compared to the terminal device directly determining not to camp on / access the first cell under the first network device.

[0308] In one optional implementation, the terminal device determines whether to allow camping in the first cell of the first network device based on non-terrestrial network cell prohibition information from the first cell of the first network device, including: if the non-terrestrial network cell prohibition information from the first cell of the first network device indicates prohibition, determining that camping in the first cell of the first network device is not allowed; and if the non-terrestrial network cell prohibition information indicates non-prohibition, determining that camping in the first cell of the first network device is allowed.

[0309] For example, if the cellbarredNTN information cell is set to barred, the terminal device determines that the terminal device is not allowed to camp on the first cell of the first network device; if the cellbarredNTN information cell is set to not barred, the terminal device determines that the terminal device is allowed to camp on the first cell of the first network device.

[0310] As can be seen, through this method, the terminal device can determine whether there is a fifth indication information in the system broadcast message from the first cell under the first network device, and when there is no fifth indication information in the system broadcast message from the first cell under the first network device, it can determine whether to camp on the first cell under the first network device based on the non-terrestrial network cell prohibition information from the first cell under the first network device, rather than directly determining that it cannot camp on the first cell under the first network device, which can improve the accuracy of the terminal device in determining whether to camp on / access the first cell under the first network device.

[0311] In addition, in the embodiments of this application, Figure 10 , Figure 12 , Figure 14 and Figure 15 Any of the communication methods shown can be implemented individually, or multiple communication methods can be combined. It should be noted that... Figure 10 and Figure 12 They cannot be combined. For an explanation of combining multiple communication methods, please refer to the aforementioned related explanations; they also have corresponding beneficial effects, and will not be elaborated upon further.

[0312] Furthermore, in the O-RAN architecture, the RIC is primarily responsible for network management and control. There is no interface between the RIC and the MME, but there is an interface with the access network equipment. Therefore, for the aforementioned communication methods 100, 200, and 300, the RIC can be used to indicate to the access network equipment the satellite identifier of whether the registration information of the terminal device was successfully received or not. The following is the O-RAN architecture... Figure 3 The architecture shown, with satellite 1 including eNB1 and satellite 2 including eNB2 as an example, illustrates the interaction between eNB1 and RIC. Figure 16 The following is a schematic diagram of its interaction, and the interaction process includes, but is not limited to, the following steps:

[0313] S1601. The eNB1 of satellite 1 sends E2 message #1 to the RIC. E2 message #1 indicates that the registration information of the receiving terminal device of satellite 1 has failed. Correspondingly, the RIC receives E2 message #1 from eNB1.

[0314] Understandably, Satellite 1 can determine whether it has successfully received the registration information of the terminal device sent by the core network. For example, Satellite 1 may determine, through the internal implementation of the core network, that it has not successfully received the registration information of the terminal device sent by the core network. In this case, when Satellite 1 is covering the gateway station, its eNB1 sends an E2 message #1 to the RIC to indicate to the RIC that Satellite 1 has failed to receive the registration information of the terminal device.

[0315] S1602. The RIC sends E2 message #2 to eNB2 on satellite 2. E2 message #2 indicates that the registration information of the receiving terminal device on satellite 1 has failed. Correspondingly, eNB2 receives E2 message #2 from the RIC.

[0316] E2 message #2 includes the identifier of eNB1, or the identifier of satellite 1, or the cell identifier of the cell where eNB1 is located. Additionally, satellite 2 includes one or more satellites that are different from satellite 1.

[0317] Optionally, E2 message #2 and E2 message #1 can be the same message or different messages.

[0318] Understandably, RIC sends E2 message #2 to satellite eNB2 to inform satellite 2 that satellite 1 failed to receive the registration information of the terminal device. This allows satellite 2 to no longer consider satellite 1 when configuring the monitoring list and / or wait timer for the terminal device, thereby reducing the probability of the terminal device failing to access the satellite.

[0319] S1603. The eNB1 of satellite 1 sends E2 message #3 to the RIC. E2 message #3 indicates that satellite 1 has successfully received the registration information of the terminal device. Correspondingly, the RIC receives E2 message #3 from eNB1.

[0320] Understandably, when Satellite 1 reconnects to the gateway station and core network after S1601, it can again receive registration information from the terminal device in the core network, and the reception of the terminal device's registration information is successful. In this case, eNB1 of Satellite 1 can send E2 message #3 to RIC to indicate that Satellite 1 has successfully received the terminal device's registration information, which allows RIC to update the status of Satellite 1's reception of the terminal device's registration information.

[0321] S1604. The RIC sends E2 message #4 to eNB2 on satellite 2. E2 message #4 indicates that satellite 1 has successfully received the registration information of the terminal device. Correspondingly, eNB2 receives E2 message #4 from the RIC.

[0322] Among them, E2 message #4 includes the identifier of eNB1, or the identifier of satellite 1, or the cell identifier of the cell where eNB1 is located.

[0323] Optionally, E2 message #3 and E2 message #4 can be the same message or different messages.

[0324] Understandably, RIC sends E2 message #4 to eNB2 to inform satellite 2 that satellite 1 has successfully received the terminal device's registration information. This is beneficial for satellite 2 to consider satellite 1 when configuring the monitoring list and / or wait timer for the terminal device, such as configuring satellite 1's information into the monitoring list, thereby increasing the probability of the terminal device successfully accessing the satellite.

[0325] As can be seen, in the O-RAN architecture, the E2 interface allows Satellite 1 to inform other satellites (Satellite 2) via RIC whether it has successfully received the registration information of the terminal device. This benefits other satellites when configuring or updating the monitoring list, as they can configure or update the monitoring list based on whether Satellite 1 has successfully received the registration information of the terminal device. This reduces the probability that the satellite indicated in the configured or updated monitoring list has not obtained the registration information of the terminal device, thereby increasing the probability that the terminal device can successfully access the satellite.

[0326] The following section further describes the corresponding device implementation scheme in relation to the technical solution described above.

[0327] To achieve the functions of the methods provided in the embodiments of this application, the terminal device and the network device may include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0328] like Figure 17 As shown, this application embodiment provides a communication device 1700. The communication device 1700 can be a component of a terminal device (e.g., an integrated circuit, a chip, etc.) or a component of a network device (e.g., an integrated circuit, a chip, etc.). The communication device 1700 can also be other communication units used to implement the methods in the method embodiments of this application. The communication device 1700 may include a communication unit 1701 and a processing unit 1702. In one possible implementation, it may further include a storage unit 1703.

[0329] In one possible design, such as Figure 17 One or more units may be implemented by one or more processors, or by one or more processors and memory; or by one or more processors and transceivers; or by one or more processors, memory, and transceivers. This application does not limit the implementation in this way. The processors, memory, and transceivers can be configured individually or integrated.

[0330] The communication device 1700 is equipped with the functions of a terminal device or a network device as described in the embodiments of this application. For example, the communication device 1700 includes a reader / writer that executes the modules, units, or means corresponding to the steps of the terminal device in the above method embodiments. The functions, units, or means can be implemented by software, hardware, or hardware executing corresponding software, or a combination of software and hardware. Further details can be found in the corresponding descriptions in the foregoing method embodiments.

[0331] In one possible design, the communication device 1700 may include a processing unit 1702 and a communication unit 1701, the device being applied to a terminal device;

[0332] The processing unit 1702 is configured to determine a first list and / or a first waiting time, wherein the first list includes information about one or more network devices that will soon cover the terminal device, and the first waiting time is the duration during which the terminal device waits to be covered by one or more network devices.

[0333] The communication unit 1701 is used to send first indication information to the first network device, the first indication information being used to indicate that the terminal device has been configured with the first list, and / or to indicate that the terminal device has been configured with the first waiting time;

[0334] The first network device is the network device that the terminal device is currently requesting to access.

[0335] In one optional implementation, the first indication information is used to indicate that the terminal device has been configured with the first list;

[0336] The first indication information includes the first list; or, the first indication information is specifically used to indicate that the first list includes information about other network devices besides the first network device; or, the first indication information is specifically used to indicate that the terminal device is the terminal device that is requesting network access for the Nth time, where N is an integer greater than 1.

[0337] In one optional implementation, the first indication information is used to indicate that the terminal device has been configured with the first waiting duration; the first indication information includes the first waiting duration.

[0338] In an optional implementation, the first indication information is carried in an access request, which is used to request the establishment of a communication connection with the first network device; the processing unit 1702 is further configured to: receive an access response from the first network device, the access response indicating that the communication connection with the first network device has failed to be established, and the access response does not carry a second list and / or a second waiting time, the second list including information on one or more network devices that will soon cover the terminal device, and the second waiting time being the duration for which the terminal device waits to be covered by one or more network devices; determine a second network device to be requested for access, the second network device being included in one or more network devices indicated by the first list, or the second network device being the network device corresponding to the first waiting time.

[0339] In one optional implementation, the communication unit 1701 sends a first indication message to the first network device, specifically configured to: send the first indication message to the first network device when a first condition is met; the first condition includes: no failure to establish a communication connection with all network devices indicated by the first list has occurred; or, the first condition includes: no failure to establish a communication connection with all network devices other than the first network device among one or more network devices indicated by the first list has occurred.

[0340] In an optional implementation, the processing unit 1702 is further configured to delete the first list and / or the first waiting time if the first condition is not met.

[0341] In another optional implementation, the communication unit 1701 sends first indication information to the first network device through a first cell under the first network device, specifically for: sending the first indication information to the first network device when a second condition is met. The second condition includes: receiving fourth indication information from the first cell under the first network device, the fourth indication information indicating that the first cell under the first network device is operating in store-and-forward mode, and / or indicating that the first cell under the first network device allows store-and-forward type terminal devices to reside or access the network.

[0342] In another optional implementation, the communication unit 1701 sends first indication information to the first network device through a first cell under the first network device, specifically configured to: send the first indication information to the first network device when both a first condition and a second condition are met simultaneously. The first condition includes: no failure to establish communication connections with all network devices indicated by the first list has occurred; or, the first condition includes: no failure to establish communication connections with all network devices other than the first network device among one or more network devices indicated by the first list has occurred. The second condition includes: receiving fourth indication information from the first cell under the first network device, the fourth indication information indicating that the first cell under the first network device is operating in store-and-forward mode, or indicating that the first cell under the first network device allows store-and-forward type terminal devices to reside or access the network.

[0343] In one alternative implementation, the first list does not include information on one or more third network devices, which are network devices that have not obtained registration information from the terminal device.

[0344] In an optional implementation, the processing unit 1702 is further configured to: receive second indication information, the second indication information being used to indicate a third list, the third list including information of a fourth network device, the fourth network device being a third network device among the one or more third network devices that has obtained the registration information of the terminal device; and determine a fifth network device to request access, the fifth network device being included in the fourth network device.

[0345] In another possible design, the communication device 1700 may include a processing unit 1702 and a communication unit 1701, the device being applied to a first network device;

[0346] The communication unit 1701 is configured to receive first indication information, which indicates that the terminal device has been configured with a first list and / or a first waiting time. The first list includes information about one or more network devices that will soon cover the terminal device, and the first waiting time is the duration for which the terminal device waits to be covered by one or more network devices.

[0347] The processing unit 1702 is configured to determine, based on the first indication information, not to configure a second list and / or a second waiting time for the terminal device, wherein the second list includes information on one or more network devices that will soon cover the terminal device, and the second waiting time is the duration for which the terminal device waits to be covered by one or more network devices.

[0348] In an optional implementation, the first indication information is carried in the access request of the terminal device, the access request being used to request the establishment of a communication connection with the first network device; the communication unit 1701 is further used to: send an access response to the terminal device, the access response being used to indicate that the communication connection between the terminal device and the first network device has failed to be established, and the access response does not carry the second list and / or the second waiting time.

[0349] In one optional implementation, the first indication information is used to indicate that the terminal device has been configured with the first list;

[0350] The first indication information includes the first list; or, the first indication information is specifically used to indicate that the first list includes information about other network devices besides the first network device; or, the first indication information is specifically used to indicate that the terminal device is the terminal device that is requesting network access for the Nth time, where N is an integer greater than 1.

[0351] In one optional implementation, the first indication information is used to indicate that the terminal device has been configured with the first waiting duration; the first indication information includes the first waiting duration.

[0352] In one optional implementation, the processing unit 1702 is further configured to release information from the terminal device.

[0353] In another possible design, the communication device 1700 may include a processing unit 1702 and a communication unit 1701, the device being applied to a terminal device;

[0354] The communication unit 1701 is configured to receive a second list and / or a second waiting time from a first network device, the second list including information about one or more network devices that are about to cover the terminal device, the second waiting time being the duration for the terminal device to wait to be covered by one or more network devices, and the first network device being the network device that the terminal device is currently requesting to access.

[0355] The processing unit 1702 is configured to, in response to receiving the second list and / or the second waiting time, determine the second network device to be requested for access, provided that the first list and / or the first waiting time has been configured, wherein the second network device is included in one or more network devices indicated by the first list, or the second network device is the network device corresponding to the first waiting time.

[0356] The first list includes information about one or more network devices that will soon cover the terminal device, and the first waiting time is the time during which the terminal device waits to be covered by one or more network devices.

[0357] In one optional implementation, the processing unit 1702 is further configured to delete the second list and / or the second waiting time.

[0358] In an optional implementation, the communication unit 1701 is further configured to send a third indication message to the first network device, the third indication message being used to instruct the first network device to release the terminal device's information.

[0359] In one optional implementation, the third indication information is further used to indicate that the terminal device has been configured with the first list and / or the first waiting time.

[0360] In one optional implementation, the third indication information is used to indicate that the terminal device has been configured with the first list;

[0361] The third indication information includes the first list; or, the third indication information is specifically used to indicate that the first list includes information about other network devices besides the first network device; or, the third indication information is specifically used to indicate that the terminal device is the terminal device that is requesting network access for the Nth time, where N is an integer greater than 1.

[0362] In one optional implementation, the third indication information is used to indicate that the terminal device has been configured with the first waiting duration; the third indication information includes the first waiting duration.

[0363] In another embodiment, the communication device includes a processing unit 1702 and a communication unit 1701, the device being applied to a terminal device, and the processing unit 1702 being used to process signals;

[0364] The communication unit 1701 is used to receive a first list, which includes information of one or more sixth network devices and does not include information of one or more third network devices.

[0365] Among them, one or more sixth network devices are network devices that have obtained or are about to obtain the registration information of the terminal device, and one or more third network devices are network devices that have not obtained the registration information of the terminal device.

[0366] In an optional implementation, the processing unit 1702 further performs the following steps: receiving second indication information, the second indication information being used to indicate a third list, the third list including information of a fourth network device, the fourth network device being a third network device among the one or more third network devices that has obtained the registration information of the terminal device; and determining a fifth network device to request access, the fifth network device being included in the fourth network device.

[0367] In another embodiment, the communication device includes a processing unit 1702 and a communication unit 1701, the device being applied to a terminal device, and the communication unit 1701 being used to receive / send signals;

[0368] The processing unit 1702 is used to determine whether there is a fifth indication information in the system broadcast message from the first cell under the first network device;

[0369] The processing unit 1702 is further configured to determine whether to remain in the first cell under the first network device based on the non-terrestrial network cell prohibition information from the first cell under the first network device in the absence of the fifth indication information;

[0370] The fifth indication information is used to indicate that the first cell under the first network device is operating in store-and-forward mode, and / or to indicate whether the first cell under the first network device allows store-and-forward type terminal devices to reside.

[0371] In one optional implementation, the processing unit 1702 determines whether to allow camping in the first cell of the first network device based on non-terrestrial network cell prohibition information from the first cell of the first network device. Specifically, it is used to: determine that camping in the first cell of the first network device is not allowed when the non-terrestrial network cell prohibition information from the first cell of the first network device indicates prohibition; and determine that camping in the first cell of the first network device is allowed when the non-terrestrial network cell prohibition information indicates non-prohibition.

[0372] The embodiments of this application and the method embodiments shown above are based on the same concept and have the same technical effects. For the specific principles, please refer to the description of the embodiments shown above, which will not be repeated here.

[0373] This application also provides a communication device 1800. Figure 18 This is a schematic diagram of the communication device 1800. The communication device 1800 can be a terminal device, or a chip, chip system, or processor that implements the above methods; alternatively, it can be a network device, or a chip, chip system, or processor that supports the implementation of the above methods. This device can be used to implement the methods described in the above method embodiments, and specific details can be found in the descriptions of the above method embodiments.

[0374] The communication device 1800 may include one or more processors 1801. The processor 1801 may be a general-purpose processor or a special-purpose processor. For example, it may be a baseband processor, digital signal processor, application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control the communication device (e.g., base station, baseband chip, terminal, terminal chip, DU or CU, etc.), execute software programs, and process data from the software programs.

[0375] In one possible implementation, the communication device 1800 may include one or more memories 1802, which may store instructions 1804. These instructions can be executed on the processor 1801, causing the communication device 1800 to perform the method described in the above method embodiments. The instructions may be replaced by programs. In another possible implementation, the memory 1802 may also store data. The processor 1801 and the memory 1802 may be configured separately or integrated together. The processor 1801 is used to parse signaling information and process related data; the memory 1802 contains stored signaling information and pre-agreed preset values, etc.

[0376] In one possible implementation, the communication device 1800 may further include a transceiver 1805 and an antenna 1806. The transceiver 1805, which may be referred to as a transceiver unit, transceiver, or transceiver circuit, is used to implement transceiver functions. The transceiver 1805 may include a receiver and a transmitter. The receiver, which may be referred to as a receiver or receiving circuit, is used to implement a receiving function; the transmitter, which may be referred to as a transmitter or transmitting circuit, is used to implement a transmitting function.

[0377] In one possible design, the communication device 1800 can be applied to a terminal device, specifically, the processor 1801 is used to execute the above... Figure 10 S1001 in the method shown, and Figure 12 S1203 in the method shown, and Figure 15 S1501 and S1502 in the method shown; transceiver 1805 is used to perform the above. Figure 10 S1002 in the method shown, and Figure 12 S1201 and S1202 in the method shown, and Figure 14 S1401 in the method shown.

[0378] In another possible design, the communication device 1800 can be applied to the first device, specifically, the processor 1801 is used to perform the above... Figure 10 In the method shown, S1003; transceiver 1805 is used to perform the above. Figure 10 S1002 in the method shown, and Figure 12 S1201 and S1202 in the method shown, and Figure 14 S1401 in the method shown.

[0379] In one possible implementation, processor 1801 may store instructions 1803, which, when executed on processor 1801, cause the communication device 1800 to perform the methods described in the above method embodiments. Instructions 1803 may be embedded in processor 1801; in this case, processor 1801 may be implemented in hardware.

[0380] The embodiments of this application and any of the above-described communication methods 100 to 400 are based on the same concept and have the same technical effects. For the specific principles, please refer to the description of any of the above-described communication methods 100 to 400, which will not be repeated here.

[0381] This application also provides a communication system including a terminal device and a network device. In another possible design, the system may further include other devices / functional network elements that interact with at least one of the terminal device and the network device.

[0382] This application also provides a chip including a processor that calls a computer program stored in a memory to enable a communication device including the chip to perform the functions of any of the above method embodiments.

[0383] This application also provides a computer-readable storage medium for storing computer software instructions, which, when executed by a communication device, implement the functions of any of the above method embodiments.

[0384] This application also provides a computer program product for storing computer software instructions, which, when executed by a communication device, implement the functions of any of the above method embodiments.

[0385] This application also provides a computer program that, when run on a computer, implements the functions of any of the above method embodiments.

[0386] The terms "first" and "second," etc., in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. "First," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, a feature defined with "first," "second," etc., may explicitly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise stated, "a plurality of" means two or more.

[0387] Furthermore, the terms “comprising” and “having”, and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus.

[0388] In this application, the term "embodiment" is used to mean that a specific feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a mutually exclusive, independent, or alternative embodiment. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0389] In the embodiments of this application, "at least one (item)" refers to one or more, "more than one" refers to two or more, and "and / or" is used to describe the association relationship of related objects, indicating that there can be three relationships. For example, "A and / or B" can represent three cases: only A exists, only B exists, and A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0390] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0391] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

Claims

1. A communication method, characterized in that, The method is applied to a terminal device, and the method includes: It is determined that a first list and / or a first waiting time have been configured, the first list including information about one or more network devices that will soon cover the terminal device, and the first waiting time being the duration for which the terminal device waits to be covered by one or more network devices; Send a first indication message to a first network device, the first indication message being used to indicate that the terminal device has been configured with the first list, and / or to indicate that the terminal device has been configured with the first waiting time; The first network device is the network device that the terminal device is currently requesting to access.

2. The method according to claim 1, characterized in that, The first indication information is used to indicate that the terminal device has been configured with the first list; The first indication information includes the first list; or, The first indication information is specifically used to indicate that the first list includes information about other network devices besides the first network device; or, The first indication information is specifically used to indicate that the terminal device is the terminal device that is requesting network access for the Nth time, where N is an integer greater than 1.

3. The method according to claim 1 or 2, characterized in that, The first indication information is used to indicate that the terminal device has been configured with the first waiting time; The first indication information includes the first waiting time.

4. The method according to any one of claims 1 to 3, characterized in that, The first indication information is carried in the access request, which is used to request the establishment of a communication connection with the first network device; the method further includes: The terminal device receives an access response from the first network device, the access response indicating that the communication connection with the first network device has failed to be established, and the access response does not carry a second list and / or a second waiting time, the second list including information about one or more network devices that will soon cover the terminal device, and the second waiting time being the duration for which the terminal device waits to be covered by one or more network devices. A second network device to be requested for access is determined. The second network device is included in one or more network devices indicated by the first list, or the second network device is the network device corresponding to the first waiting time.

5. The method according to any one of claims 1 to 4, characterized in that, Sending the first instruction information to the first network device includes: If the first condition is met, send a first instruction message to the first network device; The first condition includes: no failure to establish communication connections with all network devices indicated in the first list has occurred; Alternatively, the first condition may include: or the failure to establish a communication connection with all network devices other than the first network device in one or more network devices indicated by the first list.

6. The method according to claim 5, characterized in that, The method further includes: If the first condition is not met, delete the first list and / or the first waiting time.

7. A communication method, characterized in that, The method is applied to a first network device, and the method includes: Receive first indication information, the first indication information being used to indicate that the terminal device has been configured with a first list and / or a first waiting time, the first list including information on one or more network devices that will soon cover the terminal device, and the first waiting time being the time the terminal device waits to be covered by one or more network devices; Based on the first indication information, it is determined that a second list and / or a second waiting time will not be configured for the terminal device, wherein the second list includes information on one or more network devices that will soon cover the terminal device, and the second waiting time is the duration for which the terminal device waits to be covered by one or more network devices.

8. The method according to claim 7, characterized in that, The first indication information is carried in the access request of the terminal device, the access request being used to request the establishment of a communication connection with the first network device; the method further includes: An access response is sent to the terminal device, the access response indicating that the communication connection between the terminal device and the first network device has failed to be established, and the access response does not carry the second list and / or the second waiting time.

9. The method according to claim 7 or 8, characterized in that, The first indication information is used to indicate that the terminal device has been configured with the first list; The first indication information includes the first list; or, The first indication information is specifically used to indicate that the first list includes information about other network devices besides the first network device; or, The first indication information is specifically used to indicate that the terminal device is the terminal device that is requesting network access for the Nth time, where N is an integer greater than 1.

10. The method according to any one of claims 7 to 9, characterized in that, The first indication information is used to indicate that the terminal device has been configured with the first waiting time; The first indication information includes the first waiting time.

11. The method according to any one of claims 7 to 10, characterized in that, The method further includes: Release the information of the terminal device.

12. A communication method, characterized in that, The method is applied to a terminal device, and the method includes: Receive a second list and / or a second waiting time from a first network device, the second list including information about one or more network devices that are about to cover the terminal device, the second waiting time being the duration for the terminal device to wait to be covered by one or more network devices, and the first network device being the network device that the terminal device is currently requesting to access. In response to receiving the second list and / or the second waiting time, if the first list and / or the first waiting time has been configured, a second network device to be requested for access is determined, wherein the second network device is included in one or more network devices indicated by the first list, or the second network device is the network device corresponding to the first waiting time. The first list includes information about one or more network devices that will soon cover the terminal device, and the first waiting time is the time during which the terminal device waits to be covered by one or more network devices.

13. The method according to claim 12, characterized in that, The method further includes: Delete the second list and / or the second wait duration.

14. The method according to claim 12 or 13, characterized in that, The method further includes: Send a third instruction message to the first network device, the third instruction message being used to instruct the first network device to release the terminal device's information.

15. The method according to claim 14, characterized in that, The third indication information is also used to indicate that the terminal device has been configured with the first list and / or the first waiting time.

16. The method according to claim 15, characterized in that, The third indication information is used to indicate that the terminal device has been configured with the first list; The third indication information includes the first list; or... The third indication information is specifically used to indicate that the first list includes information about other network devices besides the first network device; or... The third indication information is specifically used to indicate that the terminal device is the terminal device that is requesting network access for the Nth time, where N is an integer greater than 1.

17. The method according to claim 15 or 16, characterized in that, The third indication information is used to indicate that the terminal device has been configured with the first waiting time; The third indication information includes the first waiting time.

18. A communication method, characterized in that, The method is applied to a terminal device, and the method includes: Determine whether a fifth indication message exists in the system broadcast message from the first cell under the first network device; In the absence of the fifth indication information, based on the non-terrestrial network cell prohibition information from the first cell, it is determined whether to allow camping in the first cell; The fifth indication information is used to indicate that the first cell is operating in store-and-forward mode, and / or to indicate whether the first cell allows store-and-forward type terminal devices to reside.

19. The method according to claim 18, characterized in that, The step of determining whether to allow camping in the first cell based on non-terrestrial network cell prohibition information from the first cell includes: If the non-terrestrial network cell prohibition information from the first cell indicates prohibition, it is determined that camping in the first cell is not allowed; If the non-terrestrial network cell prohibition information indicates that it is not prohibited, then it is determined that camping in the first cell is permitted.

20. A communication device, characterized in that, The communication device includes a module for performing the method according to any one of claims 1 to 6, or includes a module for performing the method according to any one of claims 7 to 11, or includes a module for performing the method according to any one of claims 12 to 17, or includes a module for performing the method according to claim 18 or 19.

21. A communication device, characterized in that, The communication device includes a processor configured to perform the method according to any one of claims 1 to 6, or to perform the method according to any one of claims 7 to 11, or to perform the method according to any one of claims 12 to 17, or to perform the method according to claim 18 or 19.

22. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store instructions that, when executed on a communication device, implement the method according to any one of claims 1 to 6, or the method according to any one of claims 7 to 11, or the method according to any one of claims 12 to 17, or the method according to any one of claims 18 or 19.

23. A computer program product containing instructions, characterized in that, When the instructions are executed on the communication device, they implement the method according to any one of claims 1 to 6, or the method according to any one of claims 7 to 11, or the method according to any one of claims 12 to 17, or the method according to claim 18 or 19.

Images