Mobility processing method and device, communication equipment, communication system and storage medium

Abstract

The invention relates to a mobility processing method and device, communication equipment, a communication system, a storage medium and a program product. The method is performed by a first network element. The method comprises: sending first information, the first information being used for indicating a switching failure from a first access network device to a second access network device; wherein the first access network equipment and the second access network equipment are located on different satellites, and the first access network equipment supports Samp; f function, the second access network equipment does not support Samp; f function. According to the scheme of the invention, Samp-based detection can be ensured; and the service of the F function can be normally realized.

Description

Mobility handling method and apparatus, communication device, communication system and storage medium TECHNICAL FIELD

[0001] The present disclosure relates to the field of wireless communication, and in particular, to a mobility handling method and apparatus, a communication device, a communication system, a storage medium and a program product. BACKGROUND

[0002] When a communication network provides a user with a communication service, mobility management of a terminal of the user is usually needed to guarantee continuity of the service.

[0003] SUMMARY

[0004] The present disclosure relates to the field of wireless communication, and in particular, to a mobility handling method and apparatus, a communication device, a communication system, a storage medium and a program product.

[0005] According to a first aspect of embodiments of the present disclosure, a mobility handling method is provided. The method is performed by a first network element. The method comprises: sending first information, wherein the first information is used to indicate a handover failure from a first access network device to a second access network device; wherein the first access network device and the second access network device are located on different satellites, the first access network device supports a store and forward (S&F) function, and the second access network device does not support the S&F function.

[0006] According to a second aspect of embodiments of the present disclosure, a mobility handling method is provided. The method is performed by a first access network device. The method comprises: receiving first information, wherein the first information is used to indicate a handover failure from the first access network device to a second access network device; wherein the first access network device and the second access network device are located on different satellites, the first access network device supports a store and forward (S&F) function, and the second access network device does not support the S&F function.

[0007] According to a third aspect of embodiments of the present disclosure, a mobility handling method is provided. The method is performed by a second access network device. The method comprises: sending second information, wherein the second information is used to indicate that the second access network device does not support a store and forward (S&F) function; wherein the second access network device is located on a satellite.

[0008] According to a fourth aspect of embodiments of the present disclosure, a mobility handling method is provided. The method is performed by a terminal. The method comprises: receiving fourth information, wherein the fourth information is used to indicate that satellite access is unavailable.

[0009] According to a fifth aspect of the embodiments of the present disclosure, a mobility processing method is provided. The method is performed by a core network device. The method comprises: receiving second information, wherein the second information is used to indicate that a second access network device does not support S&F function; and sending first information, wherein the first information is used to indicate that handover from a first access network device to the second access network device fails; wherein the first access network device and the second access network device are located on different satellites, and the first access network device supports S&F function.

[0010] According to a sixth aspect of the embodiments of the present disclosure, a mobility processing method is provided. The method is performed by a communication system. The communication system comprises at least one of the following: a first network element, a first access network device, and a second access network device. The method comprises: the first network element sending first information, wherein the first information is used to indicate that handover from the first access network device to the second access network device fails; and the first access network device receiving the first information; wherein the first access network device and the second access network device are located on different satellites, the first access network device supports S&F function, and the second access network device does not support S&F function.

[0011] According to a seventh aspect of the embodiments of the present disclosure, a mobility processing apparatus is provided. The apparatus is arranged in a first network element. The apparatus comprises a transceiver module. The transceiver module is configured to: send first information, wherein the first information is used to indicate that handover from a first access network device to a second access network device fails; wherein the first access network device and the second access network device are located on different satellites, the first access network device supports S&F function, and the second access network device does not support S&F function.

[0012] According to an eighth aspect of the embodiments of the present disclosure, a mobility processing apparatus is provided. The apparatus is arranged in a first access network device. The apparatus comprises a transceiver module. The transceiver module is configured to: receive first information, wherein the first information is used to indicate that handover from the first access network device to a second access network device fails; wherein the first access network device and the second access network device are located on different satellites, the first access network device supports S&F function, and the second access network device does not support S&F function.

[0013] According to a ninth aspect of the embodiments of the present disclosure, a mobility processing apparatus is provided. The apparatus is arranged in a second access network device. The apparatus comprises a transceiver module. The transceiver module is configured to: send second information, wherein the second information is used to indicate that the second access network device does not support S&F function; wherein the second access network device is located on a satellite.

[0014] According to a tenth aspect of the embodiments of the present disclosure, a mobility processing apparatus is provided. The apparatus is arranged in a terminal. The apparatus comprises a transceiver module. The transceiver module is configured to: receive fourth information, wherein the fourth information is used to indicate that satellite access is unavailable.

[0015] According to a twelfth aspect of the embodiments of the present disclosure, a communication system is provided. The communication system includes at least one of the first network element, the first access network device, and the second access network device. The communication system is configured to implement the mobility processing method according to the sixth aspect.

[0016] According to a twelfth aspect of the embodiments of the present disclosure, a communication system is provided. The communication system includes at least one of the first network element, the first access network device, and the second access network device. The communication system is configured to implement the mobility processing method according to the sixth aspect.

[0017] According to a thirteenth aspect of the embodiments of the present disclosure, a storage medium is provided. The storage medium stores instructions. The instructions, when executed on a communication device, cause the communication device to perform the mobility processing method according to any one of the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect, and the sixth aspect.

[0018] According to a thirteenth aspect of the embodiments of the present disclosure, a program product is provided. The program product, when executed on a communication device, causes the communication device to perform the mobility processing method according to any one of the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect, and the sixth aspect.

[0019] According to a fourteenth aspect of the embodiments of the present disclosure, a computer program is provided. The computer program, when executed on a computer, causes the computer to perform the mobility processing method according to any one of the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect, and the sixth aspect.

[0020] According to a fifteenth aspect of the embodiments of the present disclosure, a chip or chip system is provided. The chip or chip system includes processing circuitry. The processing circuitry is configured to perform the mobility processing method according to any one of the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect, and the sixth aspect.

[0021] According to the embodiments of the present disclosure, it can be ensured that the service based on the S&F function can be normally implemented.

[0022] It should be understood that the general description above and the following detailed description below are only exemplary and explanatory, and do not constitute a limitation on the embodiments of the present disclosure. BRIEF DESCRIPTION OF DRAWINGS

[0023] The accompanying drawings, which are incorporated herein and form part of the specification, illustrate the embodiments of the present application and, together with the description, serve to explain the principles of the embodiments of the present application.

[0024] FIG. 1 is a schematic diagram of an architecture of a communication system according to an embodiment of the present disclosure.

[0025] FIG. 2A is a schematic diagram of a scenario of a store-and-forward function according to an embodiment of the present disclosure.

[0026] FIG. 2B is a schematic diagram of a scenario of a store-and-forward function according to an embodiment of the present disclosure.

[0027] FIG. 3A is a schematic diagram of interactions of a mobility handling method according to an embodiment of the present disclosure.

[0028] FIG. 3B is a schematic diagram of interactions of a mobility handling method according to an embodiment of the present disclosure.

[0029] FIG. 3C is a schematic diagram of interactions of a mobility handling method according to an embodiment of the present disclosure.

[0030] FIG. 4A is a flowchart of a mobility handling method according to an embodiment of the present disclosure.

[0031] FIG. 4B is a flowchart of a mobility handling method according to an embodiment of the present disclosure.

[0032] FIG. 4C is a flowchart of a mobility handling method according to an embodiment of the present disclosure.

[0033] FIG. 4D is a flowchart of a mobility handling method according to an embodiment of the present disclosure.

[0034] FIG. 5A is a flowchart of a mobility handling method according to an embodiment of the present disclosure.

[0035] FIG. 5B is a flowchart of a mobility handling method according to an embodiment of the present disclosure.

[0036] FIG. 6A is a flowchart of a mobility handling method according to an embodiment of the present disclosure.

[0037] FIG. 6B is a flowchart of a mobility handling method according to an embodiment of the present disclosure.

[0038] FIG. 7 is a flowchart of a mobility handling method according to an embodiment of the present disclosure.

[0039] FIG. 8A is a flowchart of a mobility handling method according to an embodiment of the present disclosure.

[0040] FIG. 8B is a flowchart of a mobility handling method according to an embodiment of the present disclosure.

[0041] FIG. 8C is a flowchart of a mobility handling method according to an embodiment of the present disclosure.

[0042] FIG. 8D is a flow diagram of a mobility processing method according to an embodiment of the present disclosure.

[0043] FIG. 9A is an interaction diagram of an exemplary implementation of a mobility processing method according to an embodiment of the present disclosure.

[0044] FIG. 9B is an interaction diagram of an exemplary implementation of a mobility processing method according to an embodiment of the present disclosure.

[0045] FIG. 9C is an interaction diagram of an exemplary implementation of a mobility processing method according to an embodiment of the present disclosure.

[0046] FIG. 10 is a structural diagram of a mobility processing apparatus according to an embodiment of the present disclosure.

[0047] FIG. 11A is a structural diagram of a communication device according to an embodiment of the present disclosure.

[0048] FIG. 11B is a structural diagram of a chip according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0049] Embodiments of the present disclosure provide a mobility processing method and apparatus, a communication device, a communication system, a storage medium, and a program product.

[0050] In a first aspect, embodiments of the present disclosure provide a mobility processing method. The method is performed by a first network element. The above method includes: sending first information, wherein the first information is used to indicate a handover failure from a first access network device to a second access network device; and wherein the first access network device and the second access network device are located on different satellites, the first access network device supports a store and forward (S&F) function, and the second access network device does not support the S&F function.

[0051] According to the present embodiment, by sending the first information, the first network element can inform the handover failure from the first access network device to the second access network device. In this way, the terminal will not be handed over from the first access network device supporting the S&F function to the second access network device not supporting the S&F function, i.e., the terminal will not access the second access network device. In the case where the first access network device has already provided the terminal with a service based on the S&F function, since the terminal does not access the second access network device, the service based on the S&F function is avoided from being terminated or interrupted.

[0052] In some embodiments in combination with the first aspect, in some embodiments, the first information can include a cause of the handover failure, the cause of the handover failure being used to indicate that the second access network device does not support the S&F function.

[0053] According to the embodiment, since the first information contains the reason for the handover failure, i.e., the second access network device does not support the S&F function, the terminal will not be handed over from the first access network device supporting the S&F function to the second access network device not supporting the S&F function.

[0054] In some embodiments of the first aspect, the method can further include receiving second information, wherein the second information is used to indicate that the second access network device does not support the S&F function.

[0055] In some embodiments of the first aspect, the method can further include receiving or sending third information, wherein the third information is used to determine that the second access network device needs to support the S&F function.

[0056] According to the embodiment, the first network element can obtain the third information and determine, based on the third information, that the second access network device needs to support the S&F function. In this case, if the first network element learns that the second access network device does not support the S&F function, it can determine that the handover fails and reject the handover request.

[0057] In some embodiments of the first aspect, the third information can be determined according to that the first access network device supports the S&F function.

[0058] In some embodiments of the first aspect, the method can further include sending fourth information, wherein the fourth information is used to indicate that satellite access is unavailable.

[0059] According to the embodiment, through the fourth information, the first network element can inform the terminal that satellite access is unavailable. In this way, the terminal can know that satellite access is unavailable and does not access the second access network device on the satellite.

[0060] In some embodiments of the first aspect, the fourth information can include at least one of the following: indication information used to indicate that satellite access is unavailable; a start time when satellite access is unavailable; a duration of time when satellite access is unavailable.

[0061] According to the embodiment, the fourth information can indicate the start time and / or the duration of time when satellite access is unavailable. In this way, the terminal can determine the specific time when satellite access is unavailable according to the fourth information and does not access the second access network device on the satellite at this time.

[0062] In some embodiments of the first aspect, during the period when satellite access is unavailable, the terminal can be in a first state, and data and / or signaling related to the terminal can be stored in the first access network device.

[0063] According to the embodiment, the first access network device can still provide the S&F-based service for the terminal because the terminal does not access the second access network device on the satellite during the satellite access is unavailable. In this way, the first access network device can store the data and / or signaling related to the terminal. In addition, the terminal can be in the first state to achieve the purpose of reducing power consumption.

[0064] In a second aspect, the embodiments of the present disclosure provide a mobility processing method. The method is performed by a first access network device. The method comprises: receiving first information, wherein the first information is used to indicate that handover from the first access network device to a second access network device fails; and wherein the first access network device and the second access network device are located on different satellites, the first access network device supports S&F function, and the second access network device does not support S&F function.

[0065] According to the embodiment, based on the received first information, the first access network device can know that the handover from the first access network device to the second access network device fails. In this way, the terminal will not be handed over from the first access network device supporting the S&F function to the second access network device not supporting the S&F function, i.e., the terminal will not access the second access network device. In the case that the first access network device has provided the S&F-based service for the terminal, since the terminal does not access the second access network device, the S&F-based service is avoided to be terminated or interrupted.

[0066] In combination with some embodiments of the second aspect, in some embodiments, the first information can comprise a reason for the handover failure, and the reason for the handover failure is used to indicate that the second access network device does not support the S&F function.

[0067] In combination with some embodiments of the second aspect, in some embodiments, the method can further comprise: storing data and / or signaling related to the terminal.

[0068] In combination with some embodiments of the second aspect, in some embodiments, the method can further comprise: sending the first information to the terminal.

[0069] In a third aspect, the embodiments of the present disclosure provide a mobility processing method. The method is performed by a second access network device. The method comprises: sending second information, wherein the second information is used to indicate that the second access network device does not support S&F function; and wherein the second access network device is located on a satellite.

[0070] In combination with some embodiments of the third aspect, in some embodiments, the method can further comprise: receiving third information, wherein the third information is used to determine that the second access network device needs to support the S&F function.

[0071] In some embodiments combined with the third aspect, in some embodiments, the method further can include: receiving the first information, wherein the first information is used to indicate a handover failure from the first access network device to the second access network device.

[0072] In a fourth aspect, the embodiments of the present disclosure provide a mobility processing method. The method is performed by a terminal. The method includes: receiving fourth information, wherein the fourth information is used to indicate that satellite access is unavailable.

[0073] According to the present embodiment, through the fourth information, the first network element can inform the terminal that satellite access is unavailable. In this way, the terminal can know that satellite access is unavailable, and does not access the second access network device on the satellite.

[0074] In some embodiments combined with the fourth aspect, in some embodiments, the fourth information can include at least one of the following: indication information used to indicate that satellite access is unavailable; a start time of satellite access being unavailable; a duration of satellite access being unavailable.

[0075] In some embodiments combined with the fourth aspect, in some embodiments, in the case that satellite access is unavailable, the terminal can be in a first state, and data and / or signaling related to the terminal can be stored in the first access network device.

[0076] In some embodiments combined with the fourth aspect, in some embodiments, the method further can include: receiving the first information, wherein the first information is used to indicate a handover failure from the first access network device to the second access network device; wherein the first access network device and the second access network device are located on different satellites, the first access network device supports the S&F function, and the second access network device does not support the S&F function.

[0077] In some embodiments combined with the fourth aspect, in some embodiments, the first information can include a reason for the handover failure, and the reason for the handover failure is used to indicate that the second access network device does not support the S&F function.

[0078] In a fifth aspect, the embodiments of the present disclosure provide a mobility processing method. The method is performed by a core network device. The method includes: receiving second information, wherein the second information is used to indicate that the second access network device does not support the S&F function; and sending first information, wherein the first information is used to indicate a handover failure from the first access network device to the second access network device; wherein the first access network device and the second access network device are located on different satellites, and the first access network device supports the S&F function.

[0079] In a sixth aspect, the embodiments of the present disclosure provide a mobility processing method. The method is performed by a communication system. The communication system comprises at least one of a first network element, a first access network device, and a second access network device. The method comprises: sending, by the first network element, first information, wherein the first information is used to indicate a handover failure from the first access network device to the second access network device; and receiving, by the first access network device, the first information; wherein the first access network device and the second access network device are located on different satellites, the first access network device supports S&F function, and the second access network device does not support S&F function.

[0080] In a seventh aspect, the embodiments of the present disclosure provide a mobility processing apparatus. The apparatus is arranged in a first network element. The apparatus comprises a transceiver module. The transceiver module is configured to: send first information, wherein the first information is used to indicate a handover failure from a first access network device to a second access network device; wherein the first access network device and the second access network device are located on different satellites, the first access network device supports S&F function, and the second access network device does not support S&F function.

[0081] In combination with some embodiments of the seventh aspect, in some embodiments, the first information can comprise a cause of the handover failure, and the cause of the handover failure is used to indicate that the second access network device does not support S&F function.

[0082] In combination with some embodiments of the seventh aspect, in some embodiments, the transceiver module can be further configured to: receive second information, wherein the second information is used to indicate that the second access network device does not support S&F function.

[0083] In combination with some embodiments of the seventh aspect, in some embodiments, the transceiver module can be further configured to: receive or send third information, wherein the third information is used to determine that the second access network device needs to support S&F function.

[0084] In combination with some embodiments of the seventh aspect, in some embodiments, the third information can be determined according to that the first access network device supports S&F function.

[0085] In combination with some embodiments of the seventh aspect, in some embodiments, the transceiver module can be further configured to: send fourth information, wherein the fourth information is used to indicate that satellite access is unavailable.

[0086] In combination with some embodiments of the seventh aspect, in some embodiments, the fourth information can comprise at least one of the following: indication information used to indicate that satellite access is unavailable; a start time of the unavailability of satellite access; and a duration of the unavailability of satellite access.

[0087] In some embodiments combining with the seventh aspect, in some embodiments, during the satellite access is unavailable, the terminal can be in the first state, and the data and / or signaling related to the terminal can be stored in the first access network device.

[0088] In an eighth aspect, the embodiments of the present disclosure provide a mobility processing apparatus. The apparatus is arranged in a first access network device. The apparatus comprises a transceiver module. The transceiver module is configured to: receive first information, wherein the first information is used to indicate a handover failure from the first access network device to a second access network device; and wherein the first access network device and the second access network device are located on different satellites, the first access network device supports S&F function, and the second access network device does not support S&F function.

[0089] In some embodiments combining with the eighth aspect, in some embodiments, the first information can comprise a cause of the handover failure, and the cause of the handover failure is used to indicate that the second access network device does not support S&F function.

[0090] In some embodiments combining with the eighth aspect, in some embodiments, the transceiver module can be further configured to: store the data and / or signaling related to the terminal.

[0091] In some embodiments combining with the eighth aspect, in some embodiments, the transceiver module can be further configured to: send the first information to the terminal.

[0092] In a ninth aspect, the embodiments of the present disclosure provide a mobility processing apparatus. The apparatus is arranged in a second access network device. The apparatus comprises a transceiver module. The transceiver module is configured to: send second information, wherein the second information is used to indicate that the second access network device does not support S&F function; and wherein the second access network device is located on a satellite.

[0093] In some embodiments combining with the ninth aspect, in some embodiments, the transceiver module can be further configured to: receive third information, wherein the third information is used to determine that the second access network device needs to support S&F function.

[0094] In some embodiments combining with the ninth aspect, in some embodiments, the transceiver module can be further configured to: receive first information, wherein the first information is used to indicate a handover failure from a first access network device to the second access network device.

[0095] In a tenth aspect, the embodiments of the present disclosure provide a mobility processing apparatus. The apparatus is arranged in a terminal. The apparatus comprises a transceiver module. The transceiver module is configured to: receive fourth information, wherein the fourth information is used to indicate that satellite access is unavailable.

[0096] In some embodiments combining with the tenth aspect, in some embodiments, the fourth information can include at least one of the following: indication information used to indicate that satellite access is unavailable; a start time of unavailability of satellite access; a duration of unavailability of satellite access.

[0097] In some embodiments combining with the tenth aspect, in some embodiments, in a case where satellite access is unavailable, the terminal can be in the first state, and data and / or signaling related to the terminal can be stored in the first access network device.

[0098] In some embodiments combining with the tenth aspect, in some embodiments, the transceiver can be further configured to: receive first information, wherein the first information is used to indicate a failure of handover from the first access network device to the second access network device; and wherein the first access network device and the second access network device are located on different satellites, the first access network device supports the S&F function, and the second access network device does not support the S&F function.

[0099] In some embodiments combining with the tenth aspect, in some embodiments, the first information can include a cause of the handover failure, and the cause of the handover failure is used to indicate that the second access network device does not support the S&F function.

[0100] In an eleventh aspect, the embodiments of the present disclosure provide a communication device. The communication device includes one or more processors; and a memory storing instructions. The instructions, when executed by the communication device, cause the communication device to implement the mobility processing method according to any one of the first aspect and possible implementation manners thereof.

[0101] In a twelfth aspect, the embodiments of the present disclosure provide a communication device. The communication device includes one or more processors; and a memory storing instructions. The instructions, when executed by the communication device, cause the communication device to implement the mobility processing method according to any one of the second aspect and possible implementation manners thereof.

[0102] In a thirteenth aspect, the embodiments of the present disclosure provide a communication device. The communication device includes one or more processors; and a memory storing instructions. The instructions, when executed by the communication device, cause the communication device to implement the mobility processing method according to any one of the third aspect and possible implementation manners thereof.

[0103] In a fourteenth aspect, the embodiments of the present disclosure provide a communication device. The communication device includes one or more processors; and a memory storing instructions. The instructions, when executed by the communication device, cause the communication device to implement the mobility processing method according to any one of the fourth aspect and possible implementation manners thereof.

[0104] In a fifteenth aspect, an embodiment of the present disclosure provides a communication device. The communication device includes one or more processors; and a memory storing instructions. The instructions, when executed by the communication device, cause the communication device to implement the mobility processing method according to any one of the fifth aspect and possible implementation manners thereof.

[0105] In a sixteenth aspect, an embodiment of the present disclosure provides a communication system. The communication system includes at least one of a first network element, a first access network device, and a second access network device. The communication system can be used to implement the mobility processing method according to the sixth aspect.

[0106] In a seventeenth aspect, an embodiment of the present disclosure provides a storage medium. The storage medium stores instructions. The instructions, when executed on a communication device, cause the communication device to implement the mobility processing method according to any one of the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect, the sixth aspect, and possible implementation manners thereof.

[0107] In an eighteenth aspect, an embodiment of the present disclosure provides a program product. The program product, when executed by a communication device, causes the communication device to implement the mobility processing method according to any one of the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect, the sixth aspect, and possible implementation manners thereof.

[0108] In a nineteenth aspect, an embodiment of the present disclosure provides a computer program. The computer program, when executed on a computer, causes the computer to implement the mobility processing method according to any one of the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect, the sixth aspect, and possible implementation manners thereof.

[0109] In a twentieth aspect, an embodiment of the present disclosure provides a chip or chip system. The chip or chip system includes processing circuitry. The processing circuitry is configured to implement the mobility processing method according to any one of the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect, the sixth aspect, and possible implementation manners thereof.

[0110] It can be understood that the above mobility processing apparatus, communication device, communication system, storage medium, program product, computer program, chip, and chip system are all used to execute the method provided by the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved thereby can refer to the beneficial effects in the corresponding method, which will not be described here again.

[0111] The embodiments of the present disclosure provide a mobility processing method and apparatus, a communication device, a communication system, a storage medium and a program product. In some embodiments, the terms of mobility processing method, communication method, information processing method, information transmission method, etc. can be replaced with each other, and the terms of mobility processing apparatus, communication apparatus, communication device, network device, network function, network entity, etc. can be replaced with each other, and the terms of communication system, information processing system, etc. can be replaced with each other.

[0112] The embodiments of the present disclosure are not exhaustive, but only illustrate some embodiments, and are not specific limitations on the protection scope of the present disclosure. In the case of no contradiction, each step in an embodiment can be implemented as an independent embodiment, and the steps can be combined arbitrarily, for example, the scheme after removing part of the steps in an embodiment can also be implemented as an independent embodiment, and the order of the steps in an embodiment can be exchanged arbitrarily, in addition, the optional implementation manners in an embodiment can be combined arbitrarily; in addition, the embodiments can be combined arbitrarily, for example, part or all steps of different embodiments can be combined arbitrarily, an embodiment can be combined with optional implementation manners of other embodiments.

[0113] In the embodiments of the present disclosure, the terms and / or descriptions between the embodiments are consistent and can be referred to each other if there is no special description and logical conflict, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0114] The terms used in the embodiments of the present disclosure are only for the purpose of describing the specific embodiments, and not as a limitation on the present disclosure.

[0115] In the embodiments of the present disclosure, unless otherwise specified or logically contradictory, elements expressed in singular form, such as "one", "an", "one", "the", "the above", "the", "the above", "this" and the like, can represent "one and only one", or "one or more", "at least one" and the like. For example, in the case of using articles such as "a", "an", "the" and the like in English, the noun after the article can be understood as singular expression, or can be understood as plural expression.

[0116] In the embodiments of the present disclosure, "a plurality of" means two or more than two.

[0117] In some embodiments, the terms of "at least one (at least one, at least one, at least one)", "one or more" and the like can be replaced with each other.

[0118] In some embodiments, "at least one of A, B", "A and / or B", "in one case A, in another case B", "responsive to case A, responsive to case B" and the like, can be interpreted to include both cases, A and B, in some embodiments, A (A is performed regardless of B), in some embodiments, B (B is performed regardless of A), in some embodiments, selected from the group consisting of A and B (the selection between A and B is an option), in some embodiments, A and B (both A and B are performed).

[0119] In some embodiments, "A or B" and the like, can be interpreted to include both cases, A and B, in some embodiments, A (A is performed regardless of B), in some embodiments, B (B is performed regardless of A), in some embodiments, selected from the group consisting of A and B (the selection between A and B is an option).

[0120] In some embodiments, the prefix words "first", "second" and the like in the disclosure do not limit the position, order, priority, number or content of the described objects, and the description of the described objects should be referred to the context of the claims or embodiments, and should not be construed as redundant limitations. For example, the described object is "field", and the ordinal words before "field" in "first field" and "second field" do not limit the position or order between "fields", and "first" and "second" do not limit whether the "fields" modified by them are in the same message or not, nor limit the order of "first field" and "second field". For another example, the described object is "level", and the ordinal words before "level" in "first level" and "second level" do not limit the priority between "levels". For another example, the number of the described object is not limited by the ordinal words, and can be one or more. For example, "first device", where the number of "devices" can be one or more. In addition, the objects modified by different prefix words can be the same or different, for example, the described object is "device", and "first device" and "second device" can be the same device or different devices, and their types can be the same or different; for another example, the described object is "information", and "second information" and "first information" can be the same information or different information, and their contents can be the same or different.

[0121] In some embodiments, "including A", "containing A", "for indicating A", "carrying A" can be interpreted as directly carrying A, or indirectly indicating A.

[0122] In some embodiments, the terms "in response to", "in response to determining", "in the case of", "when", "when", "if", "if" and the like can be replaced with each other.

[0123] In some embodiments, the terms "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not lower than", "above", and the like can be replaced with each other, and the terms "less than", "less than or equal to", "not greater than", "fewer than", "fewer than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", "below", and the like can be replaced with each other.

[0124] In some embodiments, an apparatus and the like can be interpreted as an entity, and can also be interpreted as virtual, and the name thereof is not limited to the name recited in the embodiments, and the terms "apparatus", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", and the like can be replaced with each other.

[0125] In some embodiments, "network" can be interpreted as an apparatus (for example, an access network device, a core network device, and the like) included in the network.

[0126] In some embodiments, the terms “access network device (AN device),” “radio access network device (RAN device),” “base station (BS),” “radio base station,” “fixed station,” “node,” “access point,” “transmission point (TP),” “reception point (RP),” “transmission / reception point (TRP),” “panel,” “antenna panel,” “antenna array,” “cell,” “macro cell,” “small cell,” “femto cell,” “pico cell,” “sector,” “cell group,” “serving cell,” “carrier,” “component carrier,” “bandwidth part (BWP),” and the like can be used interchangeably.

[0127] In some embodiments, the terms "terminal," "terminal device," "user equipment (UE)," "user terminal," "mobile station (MS)," "mobile terminal (MT)," "subscriber station," "mobile unit," "subscriber unit," "wireless unit," "remote unit," "mobile device," "wireless device," "wireless communication device," "remote device," "mobile subscriber station," "access terminal," "mobile terminal," "wireless terminal," "remote terminal," "handset," "user agent," "mobile client," "client," and so on can be replaced with each other.

[0128] In some embodiments, the access network device, the core network device, or the network device can be replaced with a terminal. For example, the embodiments of the present disclosure can also be applied to a structure in which communication between the access network device, the core network device, or the network device and the terminal is replaced with communication between a plurality of terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the terminal can also be configured to have all or part of the functions of the access network device. In addition, the terms "uplink," "downlink," and the like can also be replaced with terms corresponding to the inter-terminal communication (e.g., "side"). For example, the uplink channel, the downlink channel, and the like can be replaced with the side channel, and the uplink, the downlink, and the like can be replaced with the sidelink.

[0129] In some embodiments, the terminal can be replaced with the access network device, the core network device, or the network device. In this case, the access network device, the core network device, or the network device can also be configured to have all or part of the functions of the terminal.

[0130] In some embodiments, the data, information, etc. can be obtained in compliance with the laws and regulations of the country in which the location is situated.

[0131] In some embodiments, the data, information, etc. can be obtained after obtaining the consent of the user.

[0132] In addition, each element, each row, or each column in the table of the embodiments of the present disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0133] FIG. 1 is a schematic diagram of an architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG. 1, the communication system 100 includes a terminal 101, an access network device 102, and a core network 103.

[0134] In some embodiments, the terminal 101 includes at least one of a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a Pad, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in smart grid, a wireless terminal device in transportation safety, a wireless terminal device in smart city, a wireless terminal device in smart home, etc., but is not limited thereto.

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

[0136] In some embodiments, the technical solutions of the present disclosure can be applicable to an open radio access network (Open RAN) architecture, at this time, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can become internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be realized through software or programs.

[0137] In some embodiments, the access network device 102 can be composed of a central unit (CU) and a distributed unit (DU), wherein the CU can also be referred to as a control unit (control unit). The CU-DU structure can split the protocol layers of the access network device, and some of the protocol layers are controlled by the CU, and the rest or all of the protocol layers are distributed in the DU and controlled by the CU, but is not limited thereto.

[0138] In some embodiments, the core network 103 can be one device including the first network element 1031, the second network element 1032, the third network element 1033, and the like, or can be multiple devices or device groups including all or part of the first network element 1031, the second network element 1032, the third network element 1033, and the like, respectively. The network element can be virtual or physical. The core network 103 includes, for example, at least one of an evolved packet core (EPC), a 5G core network (5GCN), a next generation core (NGC).

[0139] In some embodiments, the core network 103 can include the EPC and / or the 5GCN.

[0140] In some embodiments, the first network element 1031 can be, for example, a mobility management entity (MME).

[0141] In some embodiments, the first network element 1031 can be, for example, an access and mobility management function (AMF).

[0142] In some embodiments, the first network element 1031 can be used for mobility management of a user, for example, and its name is not limited thereto.

[0143] In some embodiments, the second network element 1032 can be, for example, a serving gateway (S-GW).

[0144] In some embodiments, the second network element 1032 can be, for example, a user plane function (UPF).

[0145] In some embodiments, the second network element 1032 can be responsible for data exchange of a user plane, for example, and its name is not limited thereto.

[0146] In some embodiments, the third network element 1033 can be, for example, a packet data network (PDN) gateway (P-GW).

[0147] In some embodiments, the third network element 1033 can be, for example, a UPF.

[0148] In some embodiments, the third network element 1033 can be responsible for UE access to a PDN, for example, and its name is not limited thereto.

[0149] In some embodiments, the above-mentioned communication system 100 can be a 4G communication system or a 5G communication system. It should be noted that the communication system 100 can also be other communication systems, such as a 6G communication system, and the embodiments of the present disclosure do not make specific limitations thereto.

[0150] With the development of communication technology, satellite communication technology is considered an important aspect of the development of future wireless communication technology. The communication system supporting satellite access technology (such as 4G, 5G network) can also be referred to as a satellite communication network. In this communication network, terminals can access the core network (such as EPC, 5GC) through satellite access networks and carry out services. However, due to the insufficient number of satellite deployments, satellite access networks may have limited coverage, and therefore, satellites may not be able to provide continuous connection services. Such non-continuous satellite connection includes the case where the service connection between the satellite and the terminal or the feeder connection between the satellite and the ground station is intermittent.

[0151] In some embodiments, the connection between the satellite and the terminal can also be referred to as a service link, and the connection between the satellite and the ground station can also be referred to as a feeder link.

[0152] In some embodiments, the satellite communication network can have two different architectures. The two architectures are a satellite communication network architecture based on a transparent payload (i.e., transparent mode) and a satellite communication network architecture based on a regenerative payload (i.e., regenerative mode).

[0153] In some embodiments, in order to provide a delay-tolerant communication service, the satellite communication system supports a store and forward (S&F) function. Store and forward (S&F) is an operating mode of a communication system with satellite access (i.e., a satellite communication system). When the satellite connection is intermittent or temporarily unavailable, the communication system can provide a data storage service and provide a cache data forwarding service when the satellite connection is restored.

[0154] In some embodiments, the operating mode of the satellite communication system based on the above-mentioned transparent mode or regenerative mode can be described as normal or default satellite operation.

[0155] FIG. 2A is a scenario diagram of store-and-forward function according to embodiments of the present disclosure. As shown in FIG. 2A, in S&F mode, the interaction of end-to-end signaling or data transmission is handled as a combination of two steps (e.g., steps A and B in FIG. 2A) performed at different times. In step A, the interaction of signaling or data transmission between a terminal and a satellite, at this time, there can be no connection between the satellite and the ground network (i.e., the satellite can communicate using the service link without an available feeder link connection). In step B, a connection is established between the satellite and the ground network (i.e., a feeder link is established), so that communication can be performed between the satellite and the ground network. Therefore, the satellite moves from establishing a connection with the terminal in step A to establishing a connection with the ground network in step B.

[0156] In some embodiments, support for S&F function is particularly suitable for non-geostationary satellite orbit (NGSO) satellite to provide latency tolerant or non-real-time Internet of Things satellite service.

[0157] In practical applications, not all satellites in the ephemeris support S&F function. For example, among a plurality of satellites in the ephemeris, a part of the satellites can support S&F function, and another part of the satellites can not support S&F function.

[0158] FIG. 2B is a scenario diagram of store-and-forward function according to embodiments of the present disclosure. As shown in FIG. 2B, the ephemeris can correspond to three satellites, denoted as SAT1, SAT2, SAT3. Among the three satellites, satellites SAT1, SAT3 support S&F function, and satellite SAT2 does not support S&F function. At a first time T1, satellite SAT1 covers the UE and provides service for the UE. Since satellite SAT1 supports S&F function, the UE can initiate a latency tolerant service through the support capability of S&F function of satellite SAT1. At this time, there can be or can not be a feeder link between satellite SAT1 and the core network (not shown) located on the ground. After that, satellite SAT1 can fly out of the coverage area for the UE, and satellite SAT2 can fly into the coverage area for the UE. At a second time T2, satellite SAT2 covers the UE and provides service for the UE. However, satellite SAT2 does not support S&F function. In some embodiments, the UE can access satellite SAT2 at the second time T2, and then the latency tolerant service related to the UE will be terminated.

[0159] Then, how to avoid the termination of the latency tolerant service due to the satellite not supporting S&F function is a problem to be solved urgently.

[0160] FIG. 3A is an interaction diagram of a mobility handling method according to embodiments of the present disclosure. The mobility handling method according to embodiments of the present disclosure can be applied to the communication system 100. As shown in FIG. 3A, the mobility handling method according to embodiments of the present disclosure includes steps S3101-S3111.

[0161] In some embodiments, the first network element 1031 can include a first core network device 1031A, a second core network device 1031B. In some embodiments, the first core network device 1031A and the second core network device 1031B can both be the first network element 1031.

[0162] In some embodiments, the second network element 1032 can include a third core network device 1032A, a fourth core network device 1032B. In some embodiments, the third core network device 1032A and the fourth core network device 1032B can both be the second network element 1032.

[0163] In some embodiments, the access network device 102 can include a first access network device 102A, a second access network device 102B. In some embodiments, the first access network device 102A and the second access network device 102B can both be the access network device 102. In some embodiments, the first access network device 102A and the second access network device 102B can be spaceborne devices. In an example, the first access network device 102A and the second access network device 102B can be located on different satellites.

[0164] In some embodiments, the first core network device 1031A, the third core network device 1032A, the first access network device 102A can be core network devices and access network devices that provide services for the terminal 101 before handover. In some embodiments, the first core network device 1031A and the third core network device 1032A can be referred to as source core network devices, and the first access network device 102A can be referred to as a source access network device. In some embodiments, the second core network device 1031B, the fourth core network device 1032B, the second access network device 102B can be core network devices and access network devices that provide services for the terminal 101 after handover. In some embodiments, the second core network device 1031B and the fourth core network device 1032B can be referred to as target core network devices, and the second access network device 102B can be referred to as a target access network device.

[0165] In step S3101, the first access network device 102A sends a handover request to the first core network device 1031A.

[0166] In some embodiments, the first core network device 1031A can receive the handover request.

[0167] In some embodiments, the handover request can be used to request handover for the terminal 101.

[0168] In some embodiments, the handover request can be used to request handover from the first access network device 102A to the second access network device 102B.

[0169] In some embodiments, the first access network device 102A can trigger the handover procedure according to the measurement report of the terminal 101. In some embodiments, the first access network device 102A can trigger the handover procedure according to the measurement report of the terminal 101 in the process that the terminal 101 moves from the satellite coverage of the first access network device 102A to the satellite coverage of the second access network device 102B. In some embodiments, the first access network device 102A can send the handover request when triggering the handover procedure.

[0170] In some embodiments, the second access network device 102B can be determined according to the measurement report of the terminal 101 and / or ephemeris information.

[0171] In some embodiments, the name of the handover request is not limited, which can be, for example, handover request, handover invitation, handover notification, etc.

[0172] In some embodiments, the handover request can be carried in a Handover Required message. In some embodiments, the first access network device 102A can send the Handover Required message to the first core network device 1031A, and the message includes the handover request.

[0173] In some embodiments, the handover request can include area information. The area information can be used to indicate the area where the terminal 101 is located.

[0174] In some embodiments, the area information can include at least one of the following: geographic coordinate information, administrative area information.

[0175] In some embodiments, the area information can be used to indicate a tracking area (TA). In some embodiments, the handover request can include identification information of the TA. In some embodiments, the handover request can include a tracking area identifier (TAI). In an example, the first access network device 102A can be an eNB, and the first core network device 1031A can be an MME. In this example, the Handover Required message can include a TAI. In an example, the handover request can include a target TAI. The target TAI can be used to indicate the area where the terminal 101 is located.

[0176] In some embodiments, the area information can be used to indicate a cell. In some embodiments, the handover request can comprise identification information of the cell. In some embodiments, the handover request can comprise a cell identity (Cell ID). In an example, the first access network device 102A can be a gNB, and the first core network device 1031A can be an AMF. In this example, the Handover Required message can comprise a cell identity. In an example, the handover request can comprise a target cell identity. The target cell identity can be used to indicate an area where the terminal 101 is located.

[0177] In some embodiments, the area information can be used to determine the second core network device 1031B. In some embodiments, the area information enables the first core network device 1031A to determine a suitable second core network device 1031B. In an example, the second core network device 1031B determined by the first core network device 1031A can be different from the first core network device 1031A. It can be understood that, in some embodiments, the first core network device 1031A can determine itself as the second core network device 1031B. In other words, the first core network device 1031A can determine itself to serve the area indicated by the area information.

[0178] In step S3102, the first core network device 1031A sends third information to the second core network device 1031B.

[0179] In some embodiments, the second core network device 1031B can receive the third information.

[0180] In some embodiments, the third information can be used to determine that the second access network device 102B needs to support the S&F function. In some embodiments, the third information can be used to indicate that the second access network device 102B needs to support the S&F function.

[0181] In some embodiments, the name of the third information is not limited, which can be, for example, function requirement information, function indication information, S&F function indication information, etc.

[0182] In some embodiments, the third information can be determined according to the S&F function supported by the first access network device 102A. In some embodiments, the third information can be determined by taking into account that the first access network device 102A supports the S&F function.

[0183] In some embodiments, the first core network device 1031A can be aware that the first access network device 102A supports the S&F function. In this case, the first core network device 1031A can determine that the second access network device 102B needs to support the S&F function.

[0184] In some embodiments, the first core network device 1031A can be aware that the first access network device 102A provides the terminal 101 with a service based on the S&F function. In this case, the first core network device 1031A can determine that the second access network device 102B needs to support the S&F function.

[0185] In some embodiments, the third information can be carried in a forward relocation request message. In an example, the first core network device 1031A and the second core network device 1031B can both be MMEs. In this example, the first core network device 1031A can send the forward relocation request message to the second core network device 1031B, which can contain the third information.

[0186] In some embodiments, the third information can be sent over a service-based Namf interface. In an example, the third information can be carried in a Namf_Communication_CreateUEContext request message. In an example, the first core network device 1031A and the second core network device 1031B can both be AMFs. In this example, the first core network device 1031A can send the Namf_Communication_CreateUEContext request message to the second core network device 1031B, which can contain the third information.

[0187] In some embodiments, before sending the third information, the first core network device 1031A can determine the second core network device 1031B. In some embodiments, the first core network device 1031A can select the second core network device 1031B according to a selection function. In an example, the selection function can be used to implement MME selection. In an example, the selection function can be used to implement AMF selection.

[0188] In some embodiments, the selection of the second core network device 1031B can take into account the area information in the handover request.

[0189] In some embodiments, the area information can be sent to the second core network device 1031B together with the third information. The area information can be used by the second core network device 1031B to determine whether the second network element 1032 needs to be reselected.

[0190] In some embodiments, the forward relocation request message can further include the area information. In an example, the area information can be contained in the third information. In an example, the area information can be independent of the third information.

[0191] In some embodiments, the Namf_Communication_CreateUEContext request message can further comprise area information. In an example, the area information can be included in the third information. In an example, the area information can be independent of the third information.

[0192] In step S3103, the second core network device 1031B interacts with the fourth core network device 1032B.

[0193] In some embodiments, in a case where the second core network device 1031B determines to reselect the second network element 1032, the second core network device 1031B can determine the fourth core network device 1032B.

[0194] In some embodiments, the second core network device 1031B can interact with the determined fourth core network device 1032B. Through the interaction between the two, a session can be created.

[0195] In some embodiments, the second core network device 1031B can be an MME, and the fourth core network device 1032B can be an S-GW. In some embodiments, the second core network device 1031B can send a create session request message to the fourth core network device 1032B. Correspondingly, the fourth core network device 1032B can send a create session response message to the second core network device 1031B.

[0196] In some embodiments, the second core network device 1031B can be an AMF, and the fourth core network device 1032B can be a UPF. In some embodiments, the second core network device 1031B can send a Namf_PDUSession_UpdateSMContext request message and receive a Namf_PDUSession_UpdateSMContext response message.

[0197] In step S3104, the second core network device 1031B sends the third information to the second access network device 102B.

[0198] In some embodiments, the second access network device 102B can receive the third information.

[0199] In some embodiments, the third information can be used here to determine that the second access network device 102B needs to support the S&F function.

[0200] In some embodiments, the third information can be used here to request the second access network device 102 to report the support capability for S&F.

[0201] In some embodiments, before sending the third information, the second core network device 1031B can determine or select the second access network device 102B.

[0202] In some embodiments, after receiving the third information, the second access network device 102B can determine that it does not support the S&F function.

[0203] In some embodiments, the third information can be carried in a handover request message.

[0204] In step S3105, the second access network device 102B sends second information to the second core network device 1031B.

[0205] In some embodiments, the second core network device 1031B can receive the second information.

[0206] In some embodiments, the second information can be used to indicate that the second access network device 102B does not support the S&F function.

[0207] In some embodiments, the second information can be used to report that the second access network device 102B does not support the S&F function.

[0208] In some embodiments, the name of the second information is not limited, which can be, for example, function indication information, failure cause information, etc.

[0209] In some embodiments, the second information can be used to indicate the support capability of the second core network device 1031B for the S&F function. In an example, the second information can indicate that the second access network device 102B does not support the S&F function. In an example, in the case where the third information is used to request reporting of the support capability of the second access network device 102B for the S&F, the second information can include or can be capability information.

[0210] In some embodiments, the second information can be used to indicate the cause of the handover failure. In some embodiments, the second information can be used to indicate that the cause of the handover failure is that the second access network device 102B does not support the S&F function. In an example, in the case where the third information is used to indicate that the second access network device 102B needs to support the S&F function, the second information can include or can be failure cause information.

[0211] In some embodiments, the second information can be carried in a handover failure message.

[0212] In some embodiments, the second core network device 1031B can determine, according to the received second information, that the second access network device 102B does not support the S&F function, and in turn determine that the handover from the first access network device 102A to the second access network device 102B fails.

[0213] In step S3106, the second core network device 1031B interacts with the fourth core network device 1032B.

[0214] In some embodiments, in the case where it is determined that the second access network device 102B does not support the S&F function and / or it is determined that the handover from the first access network device 102A to the second access network device 102B fails, the second core network device 1031B can interact with the fourth core network device 1032B. Through the interaction between the two, the created session can be deleted.

[0215] In some embodiments, the second core network device 1031B can be an MME, and the fourth core network device 1032B can be an S-GW. In some embodiments, the second core network device 1031B can send a delete session request message to the fourth core network device 1032B. Correspondingly, the fourth core network device 1032B can send a delete session response message to the second core network device 1031B.

[0216] In some embodiments, the second core network device 1031B can be an AMF, and the fourth core network device 1032B can be a UPF. In some embodiments, the second core network device 1031B can send a Namf_PDUSession_UpdateSMContext request message and receive a Namf_PDUSession_UpdateSMContext response message.

[0217] In step S3107, the second core network device 1031B sends the first information to the first core network device 1031A.

[0218] In some embodiments, the first core network device 1031A can receive the first information.

[0219] In some embodiments, the first information can be used to determine that the handover from the first access network device 102A to the second access network device 102B fails.

[0220] In some embodiments, the first information can be used to indicate that the handover from the first access network device 102A to the second access network device 102B fails.

[0221] In some embodiments, the first information can be used herein to indicate that the handover from the first access network device 102A to the second access network device 102B is rejected.

[0222] In some embodiments, the name of the first information is not limited, which can be, for example, handover failure information, handover rejection information, etc.

[0223] In some embodiments, the first information can include a cause of the handover failure.

[0224] In some embodiments, the cause of the handover failure can indicate that the second access network device 102B does not support the S&F function.

[0225] In some embodiments, the first information can be carried in a forward relocation response message. In an example, the first core network device 1031A and the second core network device 1031B can both be MMEs. In this example, the second core network device 1031B can send the forward relocation response message to the first core network device 1031A, which can contain the first information.

[0226] In some embodiments, the first information can be sent through a service-based Namf interface. In an example, the first information can be carried in a Namf_Communication_CreateUEContext response message. In an example, the first core network device 1031A and the second core network device 1031B can both be AMFs. In this example, the second core network device 1031B can send the Namf_Communication_CreateUEContext response message to the first core network device 1031A, which can contain the first information.

[0227] In step S3108, the first core network device 1031A sends the first information to the first access network device 102A.

[0228] In some embodiments, the first access network device 102A can receive the first information.

[0229] In some embodiments, the first information can be carried in a handover preparation failure message.

[0230] In some embodiments, the first core network device 1031A can send the handover preparation failure message to the first access network device 102A, which can contain the first information.

[0231] In some embodiments, the first core network device 1031A can send second information to the first access network device 102A, which is not limited in the embodiments of the present disclosure.

[0232] In step S3109, the first access network device 102A sends first information to the terminal 101.

[0233] In some embodiments, the terminal 101 can receive the first information.

[0234] In some embodiments, the terminal 101 can determine, according to the first information, that the handover from the first access network device 102A to the second access network device 102B fails. In some embodiments, the first information can be used to indicate the handover failure.

[0235] In some embodiments, based on the first information, the terminal 101 can determine that the satellite access is unavailable. In some embodiments, based on the first information, the terminal 101 can determine that the satellite access corresponding to the second access network device 102B is unavailable. In some embodiments, the terminal 101 can determine, based on the first information, that the situation that the satellite access is unavailable will occur.

[0236] In step S3110, the terminal 101 sends request information to the first core network device 1031A.

[0237] In some embodiments, the first core network device 1031A can receive the request information.

[0238] In some embodiments, the request information can be sent by the first core network device 1031A after determining the handover failure.

[0239] In some embodiments, the request information can be sent by the first core network device 1031A according to the first information.

[0240] In some embodiments, according to the first information, the terminal 101 can determine not to access the second access network device 102B. In some embodiments, the terminal 101 can send the request information before the first access network device 102A moves to no longer cover the terminal 101.

[0241] In some embodiments, the request information can be used to obtain information related to the satellite access being unavailable.

[0242] In some embodiments, the satellite access being unavailable can refer to a situation that the terminal 101 cannot access the second core network device 1031B on the satellite because the second core network device 1031B does not support the S&F function.

[0243] In some embodiments, the terminal 101 can initiate a tracking area update procedure. In some embodiments, in the tracking area update procedure, the terminal 101 can send the request information to the first core network device 1031A.

[0244] In some embodiments, the terminal 101 can initiate the tracking area update procedure before the first core network device 1031A leaves the coverage area for the terminal 101. In some embodiments, the terminal 101 can initiate the tracking area update procedure in the case that the first core network device 1031A is about to leave the coverage area for the terminal 101.

[0245] In step S3111, the first core network device 1031A sends fourth information to the terminal 101.

[0246] In some embodiments, the first core network device 1031A can send the fourth information to the terminal 101 in response to the request information.

[0247] In some embodiments, the terminal 101 can receive the fourth information.

[0248] In some embodiments, the fourth information can be used to determine that satellite access is unavailable.

[0249] In some embodiments, the fourth information can be used to indicate that satellite access is unavailable.

[0250] In some embodiments, the fourth information can be used to indicate relevant information that satellite access is unavailable.

[0251] In some embodiments, the name of the fourth information is not limited, which can be, for example, satellite access stop information, etc.

[0252] In some embodiments, the fourth information can include at least one of the following: indication information used to indicate that satellite access is unavailable, a start time of satellite access being unavailable, a duration of satellite access being unavailable.

[0253] In some embodiments, the indication information in the fourth information can be used to indicate that satellite access is unavailable. For example, the fourth information can include a specific field. The value (e.g., “1”, “true value”, “unavailable”) of the field can be used to indicate that satellite access is unavailable.

[0254] In some embodiments, the start time of the satellite access unavailable can be a time when the satellite where the first access network device 102A is located moves out of covering the terminal 101. In an example, the start time of the satellite access unavailable can be a time when the terminal 101 is out of the coverage of the first access network device 102A due to the movement of the satellite. In an example, the start time of the satellite access unavailable can be a time when the satellite where the first access network device 102A is located moves out of the coverage area.

[0255] In some embodiments, the duration of the satellite access unavailable can be a duration from a time when the satellite where the first access network device 102A is located moves out of covering the terminal 101 to a time when the satellite covers the terminal 101 again. In an example, the start time of the satellite access unavailable can be a duration between a time when the terminal 101 is out of the coverage of the first access network device 102A due to the movement of the satellite and a time when the terminal 101 enters the coverage of the first access network device 102A again. In an example, the start time of the satellite access unavailable can be a duration between a time when the satellite where the first access network device 102A is located moves out of the coverage area and a time when the satellite covers the area again.

[0256] In some embodiments, the fourth information can be determined based on the satellite ephemeris. In some embodiments, the fourth information can be determined based on the ephemeris information of the satellite of the first access network device 102A and / or the satellite of the second access network device 102B.

[0257] In some embodiments, the fourth information can contain the indication information for indicating the satellite access unavailable. In this case, the terminal 101 can determine the satellite access unavailable according to the indication information.

[0258] In some embodiments, the fourth information can not contain the indication information for indicating the satellite access unavailable. In other words, the fourth information can contain the start time of the satellite access unavailable and / or the duration of the satellite access unavailable, and omit the indication information for indicating the satellite access unavailable. In this case, the terminal 101 can determine the satellite access unavailable according to the fourth information carrying the start time of the satellite access unavailable and / or the duration of the satellite access unavailable.

[0259] In some embodiments, the terminal 101 can be in the first state in the case of the satellite access unavailable. In some embodiments, the satellite access unavailable can correspond to that the satellite of the first access network device 102A does not cover the terminal 101.

[0260] In some embodiments, the first state can be a power saving state. In an example, the power saving state can refer to a lower power consumption of the terminal 101 compared to a normal working power consumption. In an example, the power saving state can be a low power consumption state. In an example, the first state can be an idle state. In an example, the first state can be a sleep state. It can be understood that the first state can also be other states with lower power consumption, which are not limited in the embodiments of the present disclosure.

[0261] In some embodiments, the first access network device 102A can implement storage of data and / or signaling related to the terminal 101 in the case that satellite access is unavailable. In other words, the data and / or signaling related to the terminal 101 can be stored in the first access network device 102A. In an example, the first access network device 102A can store uplink data and / or signaling related to the terminal 101. In an example, the first access network device 102A can store downlink data and / or signaling related to the terminal 101.

[0262] Through the above steps S3101 to S3111, the mobility processing method according to the embodiments of the present disclosure can be implemented.

[0263] The mobility processing method related to the embodiments of the present disclosure can include at least one of the steps S3101 to S3111. For example, the step S3105 can be implemented as an independent embodiment. For example, the step S3107 can be implemented as an independent embodiment. For example, the step S3108 can be implemented as an independent embodiment. For example, the step S3111 can be implemented as an independent embodiment. For example, the combination of the steps S3105 and S3107 can be implemented as an independent embodiment. For example, the combination of the steps S3107 and S3108 can be implemented as an independent embodiment. For example, the combination of the steps S3108 and S3111 can be implemented as an independent embodiment. It should be noted that the possible independent embodiments composed of one or more of the steps S3101 to S3111 are not limited to this.

[0264] In some embodiments, the steps S3101, S3102, S3103, S3104, S3106, S3107, S3108, S3109, S3110 and S3111 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0265] In some embodiments, the steps S3101, S3102, S3103, S3104, S3105, S3106, S3108, S3109, S3110 and S3111 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0266] In some embodiments, steps S3101, S3102, S3103, S3104, S3105, S3106, S3107, S3109, S3110, S3111 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0267] In some embodiments, steps S3101, S3102, S3103, S3104, S3105, S3106, S3107, S3108, S3109, S3110 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0268] In some embodiments, other optional implementations described before or after the description corresponding to FIG. 3A can be referred to.

[0269] FIG. 3B is an interaction schematic diagram of a mobility processing method according to an embodiment of the present disclosure. The mobility processing method related by the embodiments of the present disclosure can be applied to the communication system 100. As shown in FIG. 3B, the mobility processing method of the embodiments of the present disclosure includes steps S3201 to S3211.

[0270] In some embodiments, the access network device 102 can include a first access network device 102A and a second access network device 102B. In some embodiments, the first access network device 102A and the second access network device 102B can both be the access network device 102. In some embodiments, the first access network device 102A and the second access network device 102B can be spaceborne devices. In an example, the first access network device 102A and the second access network device 102B can be located on different satellites.

[0271] In some embodiments, the first access network device 102A can be an access network device that provides services for the terminal 101 before handover. In some embodiments, the first access network device 102A can be referred to as a source access network device. In some embodiments, the second access network device 102B can be an access network device that is to provide services for the terminal 101 after handover. In some embodiments, the second access network device 102B can be referred to as a target access network device.

[0272] In some embodiments, during the handover process, neither the first network element 1031 nor the second network element 1032 changes.

[0273] In step S3201, the first access network device 102A sends a handover request to the first network element 1031.

[0274] The optional implementation of step S3201 can refer to the optional implementation of step S3101 in FIG. 2A and other associated parts in the embodiments related to FIG. 2A, details are not described herein.

[0275] In step S3202, the first network element 1031 interacts with the second network element 1032.

[0276] The optional implementation of step S3202 can refer to the optional implementation of step S3103 in FIG. 2A and other associated parts in the embodiments related to FIG. 2A, details are not described herein.

[0277] It should be noted that, because the first network element 1031 does not change in the handover process of the present embodiment, the first network element 1031 can interact with the second network element 1032 after receiving the handover request.

[0278] In step S3203, the first network element 1031 sends third information to the second access network device 102B.

[0279] The optional implementation of step S3203 can refer to the optional implementation of step S3104 in FIG. 2A and other associated parts in the embodiments related to FIG. 2A, details are not described herein.

[0280] In step S3204, the second access network device 102B sends second information to the first network element 1031.

[0281] The optional implementation of step S3204 can refer to the optional implementation of step S3105 in FIG. 2A and other associated parts in the embodiments related to FIG. 2A, details are not described herein.

[0282] In step S3205, the first network element 1031 interacts with the second network element 1032.

[0283] The optional implementation of step S3205 can refer to the optional implementation of step S3106 in FIG. 2A and other associated parts in the embodiments related to FIG. 2A, details are not described herein.

[0284] In step S3206, the first network element 1031 sends first information to the first access network device 102A.

[0285] In some embodiments, the first access network device 102A can receive the first information.

[0286] In some embodiments, the first information can be used to determine that the handover from the first access network device 102A to the second access network device 102B fails.

[0287] In some embodiments, the name of the first information is not limited, which can be, for example, handover failure information, handover rejection information, and the like.

[0288] In some embodiments, the first information can include a reason for the handover failure.

[0289] In some embodiments, the reason for the handover failure can indicate that the second access network device 102B does not support the S&F function.

[0290] In some embodiments, the first information can be carried in a handover preparation failure message.

[0291] In some embodiments, the first network element 1031 can send a handover preparation failure message to the first access network device 102A, which can contain the first information.

[0292] In step S3207, the first access network device 102A sends the first information to the terminal 101.

[0293] The optional implementation of step S3207 can refer to the optional implementation of step S3109 in FIG. 2A and other associated parts in the embodiments involved in FIG. 2A, which will not be repeated here.

[0294] In step S3208, the terminal 101 sends request information to the first network element 1031.

[0295] The optional implementation of step S3208 can refer to the optional implementation of step S3110 in FIG. 2A and other associated parts in the embodiments involved in FIG. 2A, which will not be repeated here.

[0296] In step S3209, the first network element 1031 sends fourth information to the terminal 101.

[0297] The optional implementation of step S3209 can refer to the optional implementation of step S3111 in FIG. 2A and other associated parts in the embodiments involved in FIG. 2A, which will not be repeated here.

[0298] Through the above steps S3201 to S3209, the mobility processing method according to the embodiments of the present disclosure can be implemented.

[0299] The mobility processing method related to the embodiments of the present disclosure can include at least one of steps S3201 to S3209. For example, step S3204 can be implemented as an independent embodiment. For example, step S3206 can be implemented as an independent embodiment. For example, step S3209 can be implemented as an independent embodiment. For example, a combination of steps S3204 and S3206 can be implemented as an independent embodiment. For example, a combination of steps S3206 and S3209 can be implemented as an independent embodiment. For example, a combination of steps S3204, S3206 and S3209 can be implemented as an independent embodiment. It should be noted that the possible independent embodiments composed of one or more of steps S3201 to S3209 are not limited to this.

[0300] In some embodiments, steps S3201, S3202, S3203, S3205, S3206, S3207, S3208 and S3209 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0301] In some embodiments, steps S3201, S3202, S3203, S3204, S3205, S3207, S3208 and S3209 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0302] In some embodiments, steps S3201, S3202, S3203, S3204, S3205, S3206, S3207 and S3208 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0303] In some embodiments, other optional implementations described before or after the corresponding description of FIG. 3B can be referred to.

[0304] FIG. 3C is an interaction schematic diagram of a mobility processing method according to an embodiment of the present disclosure. The mobility processing method related to the embodiments of the present disclosure can be applied to the communication system 100. As shown in FIG. 3C, the mobility processing method of the embodiments of the present disclosure includes steps S3301 to S3306.

[0305] In some embodiments, the access network device 102 can include a first access network device 102A and a second access network device 102B. In some embodiments, the first access network device 102A and the second access network device 102B can both be the access network device 102. In some embodiments, the first access network device 102A and the second access network device 102B can be spaceborne devices. In an example, the first access network device 102A and the second access network device 102B can be located on different satellites.

[0306] In some embodiments, the first access network device 102A can be an access network device serving the terminal 101 before handover. In some embodiments, the first access network device 102A can be referred to as a source access network device. In some embodiments, the second access network device 102B can be an access network device to serve the terminal 101 after handover. In some embodiments, the second access network device 102B can be referred to as a target access network device.

[0307] In some embodiments, neither the first network element 1031 nor the second network element 1032 changes during handover.

[0308] In step S3301, the first access network device 102A sends a handover request to the second access network device 102B.

[0309] In some embodiments, the handover request can be used to request handover for the terminal 101.

[0310] In some embodiments, the handover request can be used to request handover from the first access network device 102A to the second access network device 102B.

[0311] In some embodiments, the first access network device 102A can trigger the handover procedure according to the measurement report of the terminal 101. In some embodiments, the first access network device 102A can trigger the handover procedure according to the measurement report of the terminal 101 during the process that the terminal 101 moves from the satellite coverage of the first access network device 102A to the satellite coverage of the second access network device 102B. In some embodiments, the first access network device 102A can send the handover request when triggering the handover procedure.

[0312] In some embodiments, the second access network device 102B can be determined according to the measurement report of the terminal 101 and / or ephemeris information.

[0313] In some embodiments, the name of the handover request is not limited, which can be, for example, a handover request, a handover invitation, a handover notification, etc.

[0314] In some embodiments, the handover request can be sent through an X2 interface. The X2 interface can be a communication interface between the first access network device 102A and the second access network device 102B. In some embodiments, the handover request can be carried in a handover request message. The handover request message can be sent through the X2 interface.

[0315] In some embodiments, the handover request can be sent through an Xn interface. The Xn interface can be a communication interface between the first access network device 102A and the second access network device 102B. In some embodiments, the handover request can be carried in a handover request message. The handover request message can be sent through the Xn interface.

[0316] In some embodiments, the handover request can comprise area information. The area information can be used to indicate an area where the terminal 101 is located.

[0317] In some embodiments, the handover request can be sent by the first access network device 102A to the second access network device 102B in a process of handover preparation and / or handover execution.

[0318] In step S3302, the second access network device 102B sends second information to the first network element 1031.

[0319] In some embodiments, the first network element 1031 can receive the second information.

[0320] In some embodiments, the second information can be used to indicate that the second access network device 102B does not support the S&F function.

[0321] In some embodiments, the second information can be used to report that the second access network device 102B does not support the S&F function.

[0322] In some embodiments, the name of the second information is not limited, which can be, for example, function indication information, failure cause information, etc.

[0323] In some embodiments, the second information can be used to indicate the support capability of the second core network device 1031B for the S&F function. In an example, the second information can indicate that the second access network device 102B does not support the S&F function.

[0324] In some embodiments, the second access network device 102B can send the second information according to the handover request. In some embodiments, the handover request can indicate that the first access network device 102A supports the S&F function. In this case, the second access network device 102B can send the second information to the first network element 1031 to indicate that it does not support the S&F function.

[0325] In some embodiments, the second access network device 102B can send the second information according to a request message from the first network element 1031. In some embodiments, the second access network device 102B can send the second information as a response after receiving the request message from the first network element 1031 to indicate that it does not support the S&F function. In some embodiments, the request message can be used to request the support capability of the S&F function of the second access network device 102B.

[0326] In some embodiments, the second information can be carried in a path switch request message. In some embodiments, the second access network device 102B can send the path switch request message to the first network element 1031, which can contain the second information.

[0327] In some embodiments, the path switch request message can further include indication information of the support of the S&F function of the first access network device 102A.

[0328] In step S3303, the first network element 1031 sends the first information to the second access network device 102B.

[0329] In some embodiments, the second access network device 102B can receive the first information.

[0330] In some embodiments, the first information can be used to determine the failure of the handover from the first access network device 102A to the second access network device 102B.

[0331] In some embodiments, the first information can be used to indicate the failure of the handover from the first access network device 102A to the second access network device 102B.

[0332] In some embodiments, the first information can include the cause of the handover failure.

[0333] In some embodiments, the cause of the handover failure can indicate that the second access network device 102B does not support the S&F function.

[0334] In some embodiments, the first information can be determined based on the received second information.

[0335] In some embodiments, the first network element 1031 can determine the failure of the handover from the first access network device 102A to the second access network device 102B according to the second information.

[0336] In some embodiments, the first network element 1031 can determine that the second access network device 102B does not support the S&F function according to the second information. In this case, the first network element 1031 can determine that the terminal 101 cannot be handed over from the first access network device 102A to the second access network device 102B.

[0337] In some embodiments, the first network element 1031 can determine that the first access network device 102A supports the S&F function, or that the first access network device 102A provides the terminal 101 with the S&F function based service. Then, the first network element 1031 can determine that the second access network device 102B needs to support the S&F function. However, according to the second information, the first network element 1031 can determine that the second access network device 102B does not support the S&F function. In this way, the first network element 1031 can determine that the terminal 101 cannot be handed over from the first access network device 102A to the second access network device 102B.

[0338] In some embodiments, the first network element 1031 can learn that the first access network device 102A supports the S&F function in the following way: in the attachment process of the terminal 101 through the first access network device 102A, the first access network device 102A can report its support capability for the S&F function, i.e., supporting the S&F function.

[0339] In some embodiments, the first information can be carried in a path switch request failure message. In some embodiments, the first network element 1031 can send the path switch request failure message containing the first information to the second access network device 102B.

[0340] In step S3304, the second access network device 102B sends the first information to the first access network device 102A.

[0341] In some embodiments, the first access network device 102A can receive the first information.

[0342] In some embodiments, the first information can be carried in a release resource message. In some embodiments, the second access network device 102B can send the release resource message containing the first information to the first access network device 102A.

[0343] In some embodiments, the release resource message can be used to notify the first access network device 102A of the handover failure. In some embodiments, the release resource message can be used to notify the first access network device 102A of the handover failure due to the fact that the second access network device 102B does not support the S&F function. In some embodiments, the first information in the release resource message can be used by the first access network device 102A to determine the handover failure.

[0344] In some embodiments, the release resource message can be used to trigger the first access network device 102A to release resources.

[0345] In step S3305, the terminal 101 sends the request information to the first network element 1031.

[0346] The optional implementation of step S3305 can refer to the optional implementation of step S3110 in FIG. 2A and other associated parts in the embodiments involved in FIG. 2A, which will not be repeated here.

[0347] In step S3306, the first network element 1031 sends the fourth information to the terminal 101.

[0348] The optional implementation of step S3306 can refer to the optional implementation of step S3111 in FIG. 2A and other associated parts in the embodiments involved in FIG. 2A, which will not be repeated here.

[0349] Through the above steps S3301 to S3306, the mobility processing method according to the embodiments of the present disclosure can be implemented.

[0350] The mobility processing method involved in the embodiments of the present disclosure can include at least one of steps S3301 to S3306. For example, step S3302 can be implemented as an independent embodiment. For example, step S3303 can be implemented as an independent embodiment. For example, step S3304 can be implemented as an independent embodiment. For example, step S3306 can be implemented as an independent embodiment. For example, the combination of steps S3302 and S3303 can be implemented as an independent embodiment. For example, the combination of steps S3303 and S3304 can be implemented as an independent embodiment. For example, the combination of steps S3303 and S3306 can be implemented as an independent embodiment. For example, the combination of steps S3302, S3303 and S3304 can be implemented as an independent embodiment. It should be noted that the possible independent embodiments composed of one or more of steps S3301 to S3306 are not limited to this.

[0351] In some embodiments, steps S3201, S3303, S3304, S3305 and S3306 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0352] In some embodiments, steps S3301, S3302, S3304, S3305 and S3306 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0353] In some embodiments, steps S3301, S3302, S3303, S3305 and S3306 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0354] In some embodiments, steps S3301, S3302, S3303, S3304, S3305 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0355] In some embodiments, other optional implementations can be described before or after the description corresponding to FIG. 3C.

[0356] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and the terms of “information”, “message”, “signal”, “signaling”, “report”, “configuration”, “indication”, “instruction”, “command”, “channel”, “parameter”, “domain”, “field”, “symbol”, “symbol”, “codebook”, “codeword”, “codepoint”, “bit”, “data”, “program”, “chip”, etc. can be replaced with each other.

[0357] In some embodiments, the terms of “uplink”, “uplink”, “physical uplink”, etc. can be replaced with each other, the terms of “downlink”, “downlink”, “physical downlink”, etc. can be replaced with each other, and the terms of “side”, “sidelink”, “sidelink communication”, “sidelink communication”, “direct connection”, “direct connection link”, “direct connection communication”, “direct connection link communication”, etc. can be replaced with each other.

[0358] In some embodiments, the terms of “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, “RAN-based”, etc. can be replaced with each other.

[0359] In some embodiments, the terms of “time”, “time point”, “time”, “time position”, etc. can be replaced with each other, and the terms of “time length”, “time period”, “time window”, “window”, “time” can be replaced with each other.

[0360] In some embodiments, "acquire", "obtain", "get", "receive", "transmit", "bidirectionally transmit", "send and / or receive" can be replaced by each other, which can be interpreted as receiving from other subjects, acquiring from protocols, acquiring from higher layers, obtaining by self-processing, implementing autonomously, and various meanings.

[0361] In some embodiments, the terms "send", "transmit", "report", "issue", "transmit", "bidirectionally transmit", "send and / or receive" can be replaced by each other.

[0362] In some embodiments, the terms "certain", "preset", "pre-set", "set", "indicated", "certain", "arbitrary", "first" can be replaced by each other, and "certain A", "preset A", "pre-set A", "set A", "indicated A", "certain A", "arbitrary A", "first A" can be interpreted as A specified in advance in protocols and the like, or A obtained by setting, configuring, or indicating, or A as certain A, certain A, arbitrary A, or first A, but not limited thereto.

[0363] In some embodiments, determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values (for example, comparison with a predetermined value), but not limited thereto.

[0364] FIG. 4A is a flow diagram of a mobility processing method according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to a mobility processing method. The mobility processing method is performed by a first core network device 1031A. As shown in FIG. 4A, the above method includes steps S4101 to S4106.

[0365] In step S4101, a handover request is acquired.

[0366] The optional implementation of step S4101 can refer to the optional implementation of step S3101 of FIG. 3A and other associated parts in the embodiments involved in FIG. 3A, which will not be repeated here.

[0367] In some embodiments, the first core network device 1031A can receive the handover request sent by the first access network device 102A, but not limited thereto, and can also receive the handover request sent by other subjects.

[0368] In step S4102, the third information is sent.

[0369] The optional implementation of step S4102 can refer to the optional implementation of step S3102 in FIG. 3A and other associated parts in the embodiments related to FIG. 3A, details are not repeated here.

[0370] In some embodiments, the first core network device 1031A can send the third information to the second core network device 1031B, but is not limited to this, and can also send the third information to other subjects.

[0371] In step S4103, the first information is acquired.

[0372] The optional implementation of step S4103 can refer to the optional implementation of step S3107 in FIG. 3A and other associated parts in the embodiments related to FIG. 3A, details are not repeated here.

[0373] In some embodiments, the first core network device 1031A can receive the first information sent by the second core network device 1031B, but is not limited to this, and can also receive the first information sent by other subjects.

[0374] In step S4104, the first information is sent.

[0375] The optional implementation of step S4104 can refer to the optional implementation of step S3108 in FIG. 3A and other associated parts in the embodiments related to FIG. 3A, details are not repeated here.

[0376] In some embodiments, the first core network device 1031A can send the first information to the first access network device 102A, but is not limited to this, and can also send the first information to other subjects.

[0377] In step S4105, the request information is acquired.

[0378] The optional implementation of step S4105 can refer to the optional implementation of step S3110 in FIG. 3A and other associated parts in the embodiments related to FIG. 3A, details are not repeated here.

[0379] In some embodiments, the first core network device 1031A can receive the request information sent by the terminal 101, but is not limited to this, and can also receive the request information sent by other subjects.

[0380] In step S4106, the fourth information is sent.

[0381] The optional implementation of step S4106 can refer to the optional implementation of step S3111 in FIG. 3A and other associated parts in the embodiments related to FIG. 3A, details are not repeated here.

[0382] In some embodiments, the first core network device 1031A can send the fourth information to the terminal 101, but is not limited thereto, and can also send the fourth information to other subjects.

[0383] The mobility processing method related to the embodiments of the present disclosure can include at least one of steps S4101 to S4106. For example, step S4104 can be implemented as an independent embodiment. For example, step S4106 can be implemented as an independent embodiment. For example, a combination of steps S4104 and S4106 can be implemented as an independent embodiment. It should be noted that the possible independent embodiments composed of one or more of steps S4101 to S4106 are not limited thereto.

[0384] In some embodiments, steps S4101, S4102, S4103, S4105, and S4106 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0385] In some embodiments, steps S4101, S4102, S4103, S4104, and S4105 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0386] FIG. 4B is a flow diagram of a mobility processing method according to an embodiment of the present disclosure. The embodiments of the present disclosure relate to a mobility processing method. The mobility processing method is performed by a second core network device 1031B. As shown in FIG. 4B, the above method includes steps S4201 to S4206.

[0387] In step S4201, third information is obtained.

[0388] The optional implementation of step S4201 can refer to the optional implementation of step S3102 in FIG. 3A and other associated parts in the embodiments related to FIG. 3A, which will not be described here.

[0389] In some embodiments, the second core network device 1031B can receive the third information sent by the first core network device 1031A, but is not limited thereto, and can also receive the third information sent by other subjects.

[0390] In step S4202, interaction is performed.

[0391] The optional implementation of step S4202 can refer to the optional implementation of step S3103 in FIG. 3A and other associated parts in the embodiments related to FIG. 3A, which will not be described here.

[0392] In some embodiments, the second core network device 1031B can perform interaction with the fourth core network device 1032B, but is not limited thereto, and can perform interaction with other subjects.

[0393] In step S4203, the third information is sent.

[0394] Optional implementation of step S4203 can be referred to optional implementation of step S3104 in FIG. 3A and other associated parts in embodiments involved in FIG. 3A, which will not be repeated here.

[0395] In some embodiments, the second core network device 1031B can send the third information to the second access network device 102B, but is not limited thereto, and can send the third information to other subjects.

[0396] In step S3204, the second information is acquired.

[0397] Optional implementation of step S4204 can be referred to optional implementation of step S3105 in FIG. 3A and other associated parts in embodiments involved in FIG. 3A, which will not be repeated here.

[0398] In some embodiments, the second core network device 1031B can receive the second information sent by the second access network device 102B, but is not limited thereto, and can receive the second information sent by other subjects.

[0399] In step S4205, interaction is performed.

[0400] Optional implementation of step S4205 can be referred to optional implementation of step S3106 in FIG. 3A and other associated parts in embodiments involved in FIG. 3A, which will not be repeated here.

[0401] In some embodiments, the second core network device 1031B can perform interaction with the fourth core network device 1032B, but is not limited thereto, and can perform interaction with other subjects.

[0402] In step S4206, the first information is sent.

[0403] Optional implementation of step S4206 can be referred to optional implementation of step S3107 in FIG. 3A and other associated parts in embodiments involved in FIG. 3A, which will not be repeated here.

[0404] In some embodiments, the second core network device 1031B can send the first information to the first core network device 1031A, but is not limited thereto, and can send the first information to other subjects.

[0405] The mobility processing method related to the embodiments of the present disclosure can include at least one of steps S4201 to S4206. For example, step S4204 can be implemented as an independent embodiment. For example, step S4206 can be implemented as an independent embodiment. For example, a combination of steps S4204 and S4206 can be implemented as an independent embodiment. It should be noted that the possible independent embodiments composed of one or more of steps S4201 to S4206 are not limited to this.

[0406] In some embodiments, steps S4201, S4202, S4203, S4205, S4206 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0407] In some embodiments, steps S4201, S4202, S4203, S4204, S4205 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0408] FIG. 4C is a flow diagram of a mobility processing method according to an embodiment of the present disclosure. The embodiments of the present disclosure relate to a mobility processing method. The mobility processing method is performed by a first network element 1031. As shown in FIG. 4C, the above method includes steps S4301 to S4308.

[0409] In step S4301, a handover request is obtained.

[0410] The optional implementation of step S4301 can refer to the optional implementation of step S3201 in FIG. 3B and other associated parts in the embodiments related to FIG. 3B, which will not be described here.

[0411] In some embodiments, the first network element 1031 can receive the handover request sent by the first access network device 102A, but is not limited thereto, and can also receive the handover request sent by other subjects.

[0412] In step S4302, interaction is performed.

[0413] The optional implementation of step S4302 can refer to the optional implementation of step S3202 in FIG. 3B and other associated parts in the embodiments related to FIG. 3B, which will not be described here.

[0414] In some embodiments, the first network element 1031 can perform interaction with the second network element 1032, but is not limited thereto, and can also perform interaction with other subjects.

[0415] In step S4303, third information is sent.

[0416] Optional implementation of step S4303 can refer to optional implementation of step S3203 in FIG. 3B and other associated parts in the embodiments related to FIG. 3B. Details are not described herein again.

[0417] In some embodiments, the first network element 1031 can send the third information to the second access network device 102B, but is not limited to this, and can also send the third information to other subjects.

[0418] In step S4304, the second information is acquired.

[0419] Optional implementation of step S4304 can refer to optional implementation of step S3204 in FIG. 3B and other associated parts in the embodiments related to FIG. 3B. Details are not described herein again.

[0420] In some embodiments, the first network element 1031 can receive the second information sent by the second access network device 102B, but is not limited to this, and can also receive the second information sent by other subjects.

[0421] In step S4305, the interaction is performed.

[0422] Optional implementation of step S4305 can refer to optional implementation of step S3205 in FIG. 3B and other associated parts in the embodiments related to FIG. 3B. Details are not described herein again.

[0423] In some embodiments, the first network element 1031 can perform the interaction with the second network element 1032, but is not limited to this, and can also perform the interaction with other subjects.

[0424] In step S4306, the first information is sent.

[0425] Optional implementation of step S4306 can refer to optional implementation of step S3206 in FIG. 3B and other associated parts in the embodiments related to FIG. 3B. Details are not described herein again.

[0426] In some embodiments, the first network element 1031 can send the first information to the first access network device 102A, but is not limited to this, and can also send the first information to other subjects.

[0427] In step S4307, the request information is acquired.

[0428] Optional implementation of step S4307 can refer to optional implementation of step S3208 in FIG. 3B and other associated parts in the embodiments related to FIG. 3B. Details are not described herein again.

[0429] In some embodiments, the first network element 1031 can receive the request information sent by the terminal 101, but is not limited thereto, and can also receive the request information sent by other subjects.

[0430] In step S4308, the fourth information is sent.

[0431] The optional implementation of step S4308 can refer to the optional implementation of step S3209 in FIG. 3B and other associated parts in the embodiments involved in FIG. 3B, which will not be repeated here.

[0432] In some embodiments, the first network element 1031 can send the fourth information to the terminal 101, but is not limited thereto, and can also send the fourth information to other subjects.

[0433] The mobility processing method involved in the embodiments of the present disclosure can include at least one of steps S4301 to S4308. For example, step S4304 can be implemented as an independent embodiment. For example, step S4306 can be implemented as an independent embodiment. For example, step S4308 can be implemented as an independent embodiment. For example, a combination of steps S4304 and S4306 can be implemented as an independent embodiment. For example, a combination of steps S4306 and S4308 can be implemented as an independent embodiment. It should be noted that the possible independent embodiments composed of one or more of steps S4301 to S4308 are not limited thereto.

[0434] In some embodiments, steps S4301, S4302, S4303, S4305, S4306, S4307, and S4308 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0435] In some embodiments, steps S4301, S4302, S4303, S4304, S4305, S4307, and S4308 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0436] In some embodiments, steps S4301, S4302, S4303, S4304, S4305, S4306, and S4307 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0437] FIG. 4D is a flow diagram of a mobility processing method according to an embodiment of the present disclosure. The embodiments of the present disclosure relate to a mobility processing method. The mobility processing method is performed by a first network element 1031. As shown in FIG. 4D, the above method includes steps S4401 to S4404.

[0438] In step S4401, the second information is acquired.

[0439] The optional implementation of step S4401 can refer to the optional implementation of step S3302 in FIG. 3C and other associated parts in the embodiments involved in FIG. 3C, which will not be repeated here.

[0440] In some embodiments, the first network element 1031 can receive the second information sent by the second access network device 102B, but is not limited thereto, and can also receive the second information sent by other subjects.

[0441] In step S4402, the first information is sent.

[0442] The optional implementation of step S4402 can refer to the optional implementation of step S3303 in FIG. 3C and other associated parts in the embodiments involved in FIG. 3C, which will not be repeated here.

[0443] In some embodiments, the first network element 1031 can send the first information to the second access network device 102B, but is not limited thereto, and can also send the first information to other subjects.

[0444] In step S4403, the request information is acquired.

[0445] The optional implementation of step S4403 can refer to the optional implementation of step S3305 in FIG. 3C and other associated parts in the embodiments involved in FIG. 3C, which will not be repeated here.

[0446] In some embodiments, the first network element 1031 can receive the request information sent by the terminal 101, but is not limited thereto, and can also receive the request information sent by other subjects.

[0447] In step S4404, the fourth information is sent.

[0448] The optional implementation of step S4404 can refer to the optional implementation of step S3306 in FIG. 3C and other associated parts in the embodiments involved in FIG. 3C, which will not be repeated here.

[0449] In some embodiments, the first network element 1031 can send the fourth information to the terminal 101, but is not limited thereto, and can also send the fourth information to other subjects.

[0450] The mobility processing method related to the embodiments of the present disclosure can include at least one of steps S4401 to S4404. For example, step S4401 can be implemented as an independent embodiment. For example, step S4402 can be implemented as an independent embodiment. For example, step S4404 can be implemented as an independent embodiment. For example, a combination of steps S4401 and S4402 can be implemented as an independent embodiment. For example, a combination of steps S4402 and S4404 can be implemented as an independent embodiment. It should be noted that the possible independent embodiments composed of one or more of steps S4401 to S4404 are not limited to this.

[0451] In some embodiments, steps S4402, S4403, and S4404 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0452] In some embodiments, steps S4401, S4403, and S4404 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0453] In some embodiments, steps S4401, S4402, and S4403 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0454] FIG. 5A is a flow diagram of a mobility processing method according to an embodiment of the present disclosure. The embodiments of the present disclosure relate to a mobility processing method. The mobility processing method is performed by a first access network device 102A. As shown in FIG. 5A, the above method includes steps S5101 to S5103.

[0455] In step S5101, a handover request is sent.

[0456] The optional implementation of step S5101 can refer to the optional implementation of step S3101 in FIG. 3A, step S3201 in FIG. 3B, and other associated parts in the embodiments related to FIG. 3A and FIG. 3B, which are not described here.

[0457] In some embodiments, the first access network device 102A can send the handover request to the first core network device 1031A, but is not limited to this, and can also send the handover request to other subjects.

[0458] In some embodiments, the first access network device 102A can send the handover request to the first network element 1031, but is not limited to this, and can also send the handover request to other subjects.

[0459] In step S5102, first information is acquired.

[0460] The optional implementation of step S5102 can refer to the optional implementation of step S3108 in FIG. 3A, step S3206 in FIG. 3B, and other associated parts in the embodiments related to FIG. 3A and FIG. 3B, which are not described here again.

[0461] In some embodiments, the first access network device 102A can receive the first information sent by the first core network device 1031A, but is not limited thereto, and can also receive the first information sent by other subjects.

[0462] In some embodiments, the first access network device 102A can receive the first information sent by the first network element 1031, but is not limited thereto, and can also receive the first information sent by other subjects.

[0463] In step S5103, the first information is sent.

[0464] The optional implementation of step S5103 can refer to the optional implementation of step S3109 in FIG. 3A, step S3207 in FIG. 3B, and other associated parts in the embodiments related to FIG. 3A and FIG. 3B, which are not described here again.

[0465] In some embodiments, the first access network device 102A can send the first information to the terminal 101, but is not limited thereto, and can also send the first information to other subjects.

[0466] The mobility processing method related to the embodiments of the present disclosure can include at least one of steps S5101 to S5103. For example, step S5102 can be implemented as an independent embodiment. It should be noted that the possible independent embodiments composed of one or more of steps S5101 to S5103 are not limited thereto.

[0467] In some embodiments, steps S5101 and S5103 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0468] FIG. 5B is a flow diagram of a mobility processing method according to an embodiment of the present disclosure. The embodiments of the present disclosure relate to a mobility processing method. The mobility processing method is performed by the first access network device 102A. As shown in FIG. 5B, the above method includes steps S5201 to S5202.

[0469] In step S5201, a handover request is sent.

[0470] The optional implementation of step S5201 can refer to step S3301 in FIG. 3C, and other associated parts in the embodiments related to FIG. 3C, which are not described here again.

[0471] In some embodiments, the first access network device 102A can send the handover request to the second access network device 102B, but is not limited thereto, and can send the handover request to other subjects.

[0472] In step S5202, first information is acquired.

[0473] The optional implementation of step S5202 can refer to the optional implementation of step S3304 in FIG. 3C, and other associated parts in the embodiments involved in FIG. 3C, which will not be repeated here.

[0474] In some embodiments, the first access network device 102A can receive the first information sent by the second access network device 102B, but is not limited thereto, and can receive the first information sent by other subjects.

[0475] The mobility processing method involved in the embodiments of the present disclosure can include at least one of steps S5201 to S5202. For example, step S5202 can be implemented as an independent embodiment. It should be noted that the possible independent embodiments composed of one or more of steps S5201 to S5202 are not limited thereto.

[0476] In some embodiments, step S5201 is optional, and can be omitted or replaced in different embodiments.

[0477] FIG. 6A is a flow diagram of a mobility processing method according to an embodiment of the present disclosure. The embodiments of the present disclosure relate to a mobility processing method. The mobility processing method is performed by the second access network device 102B. As shown in FIG. 6A, the above method includes steps S6101 to S6102.

[0478] In step S6101, third information is acquired.

[0479] The optional implementation of step S6101 can refer to the optional implementation of step S3104 in FIG. 3A, step S3203 in FIG. 3B, and other associated parts in the embodiments involved in FIG. 3A and FIG. 3B, which will not be repeated here.

[0480] In some embodiments, the second access network device 102B can receive the third information sent by the second core network device 1031B, but is not limited thereto, and can receive the third information sent by other subjects.

[0481] In some embodiments, the second access network device 102B can receive the third information sent by the first network element 1031, but is not limited thereto, and can receive the third information sent by other subjects.

[0482] In step S6102, second information is sent.

[0483] The optional implementation of step S6102 can refer to the optional implementation of step S3105 in FIG. 3A, the optional implementation of step S3204 in FIG. 3B, and other associated parts in the embodiments involved in FIG. 3A and FIG. 3B, which are not described here again.

[0484] In some embodiments, the second access network device 102B can send the second information to the second core network device 1031B, but is not limited thereto, and can also send the second information to other subjects.

[0485] In some embodiments, the first access network device 102A can send the second information to the first network element 1031, but is not limited thereto, and can also send the second information to other subjects.

[0486] The mobility processing method involved in the embodiments of the present disclosure can include at least one of steps S6101 to S6102. For example, step S6102 can be implemented as an independent embodiment. It should be noted that the possible independent embodiments composed of one or more of steps S6101 to S6102 are not limited thereto.

[0487] In some embodiments, step S6101 is optional, and can be omitted or replaced in different embodiments.

[0488] FIG. 6B is a flow diagram of a mobility processing method according to an embodiment of the present disclosure. The embodiments of the present disclosure relate to a mobility processing method. The mobility processing method is performed by the second access network device 102B. As shown in FIG. 6B, the above method includes steps S6201 to S6204.

[0489] In step S6201, a handover request is obtained.

[0490] The optional implementation of step S6201 can refer to the optional implementation of step S3301 in FIG. 3C, and other associated parts in the embodiments involved in FIG. 3C, which are not described here again.

[0491] In some embodiments, the second access network device 102B can receive the handover request sent by the first access network device 102A, but is not limited thereto, and can also receive the handover request sent by other subjects.

[0492] In step S6202, second information is sent.

[0493] The optional implementation of step S6202 can refer to step S3302 in FIG. 3C, and other associated parts in the embodiments involved in FIG. 3C, which are not described here again.

[0494] In some embodiments, the second access network device 102B can send the second information to the first network element 1031, but is not limited thereto, and can send the second information to other subjects.

[0495] In step S6203, the first information is acquired.

[0496] The optional implementation of step S6203 can refer to the optional implementation of step S3303 in FIG. 3C and other associated parts in the embodiments involved in FIG. 3C, which will not be repeated here.

[0497] In some embodiments, the second access network device 102B can receive the first information sent by the first network element 1031, but is not limited thereto, and can receive the first information sent by other subjects.

[0498] In step S6204, the first information is sent.

[0499] The optional implementation of step S6204 can refer to step S3304 in FIG. 3C and other associated parts in the embodiments involved in FIG. 3C, which will not be repeated here.

[0500] In some embodiments, the second access network device 102B can send the first information to the first access network device 102A, but is not limited thereto, and can send the first information to other subjects.

[0501] The mobility processing method involved in the embodiments of the present disclosure can include at least one of steps S6201 to S6204. For example, step S6202 can be implemented as an independent embodiment. For example, step S6203 can be implemented as an independent embodiment. For example, the combination of steps S6202 and S6203 can be implemented as an independent embodiment. It should be noted that the possible independent embodiments composed of one or more of steps S6201 to S6204 are not limited thereto.

[0502] In some embodiments, steps S6201, S6203 and S6204 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0503] In some embodiments, steps S6201, S6202 and S6204 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0504] FIG. 7 is a flow diagram of a mobility processing method according to an embodiment of the present disclosure. The embodiments of the present disclosure relate to a mobility processing method. The mobility processing method is performed by the terminal 101. As shown in FIG. 7, the above method includes steps S701 to S703.

[0505] In step S701, first information is acquired.

[0506] Optional implementation of step S701 can refer to optional implementation of step S3109 in FIG. 3A, step S3207 in FIG. 3B, and other associated parts in the embodiments involved in FIG. 3A and FIG. 3B, which are not described herein again.

[0507] In some embodiments, the terminal 101 can receive the first information sent by the first access network device 102A, but is not limited thereto, and can also receive the first information sent by other subjects.

[0508] In step S702, request information is sent.

[0509] Optional implementation of step S702 can refer to step S3110 in FIG. 3A, step S3208 in FIG. 3B, step S3305 in FIG. 3C, and other associated parts in the embodiments involved in FIG. 3A, FIG. 3B and FIG. 3C, which are not described herein again.

[0510] In some embodiments, the terminal 101 can send the request information to the first core network device 1031A, but is not limited thereto, and can also send the request information to other subjects.

[0511] In some embodiments, the terminal 101 can send the request information to the first network element 1031, but is not limited thereto, and can also send the request information to other subjects.

[0512] In step S703, fourth information is acquired.

[0513] Optional implementation of step S703 can refer to step S3111 in FIG. 3A, step S3209 in FIG. 3B, optional implementation of step S3306 in FIG. 3C, and other associated parts in the embodiments involved in FIG. 3A, FIG. 3B and FIG. 3C, which are not described herein again.

[0514] In some embodiments, the terminal 101 can receive the fourth information sent by the first core network device 1031A, but is not limited thereto, and can also receive the fourth information sent by other subjects.

[0515] In some embodiments, the terminal 101 can receive the fourth information sent by the first network element 1031, but is not limited thereto, and can also receive the fourth information sent by other subjects.

[0516] The mobility processing method related to the embodiments of the present disclosure can include at least one of steps S701 to S703. For example, step S703 can be implemented as an independent embodiment. It should be noted that the possible independent embodiments composed of one or more of steps S701 to S703 are not limited thereto.

[0517] In some embodiments, steps S701 and S702 are optional, and one or more of these steps can be omitted or replaced in different embodiments.

[0518] FIG. 8A is a flow diagram of a mobility processing method according to an embodiment of the present disclosure. The embodiments of the present disclosure relate to a mobility processing method. As shown in FIG. 8A, the above method includes step S8101.

[0519] In step S8101, the first network element 1031 sends first information.

[0520] The optional implementation of step S8101 can refer to steps S3107 and S3108 in FIG. 3A, step S3206 in FIG. 3B, step S3303 in FIG. 3C, and other associated parts in the embodiments related to FIGS. 3A, 3B, and 3C, which will not be described here.

[0521] In some embodiments, the first network element 1031 can send the first information to the first access network device 102A.

[0522] In some embodiments, the first network element 1031 can send the first information to the second access network device 102B.

[0523] In some embodiments, the first network element 1031 can include the first core network device 1031A and / or the second core network device 1031B.

[0524] In some embodiments, the first network element 1031 can be the first core network device 1031A. In some embodiments, the first core network device 1031A can send the first information to the first access network device 102A.

[0525] In some embodiments, the first network element 1031 can be the second core network device 1031B. In some embodiments, the second core network device 1031B can send the first information to the first core network device 1031A.

[0526] FIG. 8B is a flow diagram of a mobility processing method according to an embodiment of the present disclosure. The embodiments of the present disclosure relate to a mobility processing method. As shown in FIG. 8B, the above method includes step S8201.

[0527] In step S8201, the first access network device 102A receives the first information.

[0528] The optional implementation of step S8201 can refer to step S3108 in FIG. 3A, step S3206 in FIG. 3B, step S3304 in FIG. 3C, and other associated parts in the embodiments related to FIG. 3A, FIG. 3B, and FIG. 3C, which are not described here again.

[0529] In some embodiments, the first access network device 102A can receive the first information sent by the first core network device 1031A.

[0530] In some embodiments, the first access network device 102A can receive the first information sent by the first network element 1031.

[0531] In some embodiments, the first access network device 102A can receive the first information sent by the second access network device 102B.

[0532] FIG. 8C is a flow diagram of a mobility processing method according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to a mobility processing method. As shown in FIG. 8C, the above method includes step S8301.

[0533] In step S8301, the second access network device 102B sends second information.

[0534] The optional implementation of step S8301 can refer to step S3105 in FIG. 3A, step S3204 in FIG. 3B, step S3302 in FIG. 3C, and other associated parts in the embodiments related to FIG. 3A, FIG. 3B, and FIG. 3C, which are not described here again.

[0535] In some embodiments, the second access network device 102B can send the second information to the second core network device 1031B.

[0536] In some embodiments, the second access network device 102B can send the second information to the first network element 1031.

[0537] FIG. 8D is a flow diagram of a mobility processing method according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to a mobility processing method. As shown in FIG. 8D, the above method includes step S8401.

[0538] In step S8401, the terminal 101 receives fourth information.

[0539] The optional implementation of step S8401 can refer to step S3111 in FIG. 3A, step S3209 in FIG. 3B, step S3306 in FIG. 3C, and other associated parts in the embodiments related to FIG. 3A, FIG. 3B, and FIG. 3C, which are not described here again.

[0540] In some embodiments, the terminal 101 can receive fourth information sent by the first core network device 1031A.

[0541] In some embodiments, the terminal 101 can receive fourth information sent by the first network element 1031.

[0542] In the following, the technical solutions of the embodiments of the present disclosure are exemplarily described through specific embodiments.

[0543] In some embodiments, when the base station satellite mobile trigger handover procedure, the MME (or AMF in 5G network) (i.e. the first network element) indicates the target base station satellite (i.e. the second access network device) after handover supports the storage and forwarding capability according to the capability of the base station satellite (i.e. the first access network device) before handover supporting storage and forwarding.

[0544] In some embodiments, according to the indication, if the target base station satellite does not support the capability, return handover failure and explain that the handover failure is due to its not supporting the storage and forwarding capability.

[0545] In some embodiments, the MME indicates the handover failure to the UE according to the return result.

[0546] In some embodiments, the UE (i.e. the terminal) sends a tracking area update request to the MME, and the MME returns the unavailability duration and / or the unavailability start time to the UE. The unavailability start time is the start time of the current satellite coverage loss. The unavailability duration is the duration from the current satellite losing coverage to the next time providing coverage.

[0547] FIG. 9A is an interaction schematic diagram of an exemplary embodiment of a mobility processing method according to an embodiment of the present disclosure. FIG. 9A describes a scenario that SAT-eNB1 provides current coverage, and when SAT-eNB1 loses coverage, SAT-eNB2 continues to provide coverage for the area. After the coverage of SAT-eNB1 is switched to the coverage of SAT-eNB2, the corresponding MME and S-GW will change.

[0548] As shown in FIG. 9A, the mobility processing method includes steps S9101 to S9112.

[0549] In step S9101, the UE accesses the EPC through the STA-eNB1, and downlink data is sent to the UE through the P-GW (i.e., the third network element), the source S-GW, and the source SAT-eNB1. Over time, the source SAT-eNB1 will move out of the coverage area of the UE, and the source SAT-eNB1 decides to initiate an S1 -based handover to the target SAT-eNB2. This can be triggered, for example, by the absence of an X2 connection with the target SAT-eNB2, or by an indication from the target SAT-eNB2 after an X2-based handover has not been successful.

[0550] In step S9102, the source SAT-eNB1 sends a handover request (target TAI, etc.) to the source MME (i.e., the first core network device). The target TAI is sent to the MME to facilitate selection of a suitable target MME (i.e., the second core network device).

[0551] In step S9103, the source MME selects the target MME based on MME selection functionality. If it is determined that the MME needs to be relocated, the source MME sends a forward relocation request message (MME UE context, target SAT-eNB2 identity, target TAI, etc.) to the target MME.

[0552] In some embodiments, the target TAI is sent to the target MME to assist the target MME in determining whether S-GW relocation is needed.

[0553] In some embodiments, the S&F indication needs to be included in the forward relocation request message to send the S&F indication to the target MME. The S&F indication is used to indicate that the source SAT-eNB1 should support S&F capability. The source MME determines to send the S&F indication to the target MME in consideration of the source SAT-eNB1 supporting S&F capability.

[0554] In step S9104, if MME relocation has occurred, the target MME verifies whether the source S-GW (i.e., the third core network device) is able to continue to serve the UE. If not, the target MME selects a new S-GW. If a new S-GW is selected, the target MME sends a create session request message to the target S-GW (i.e., the fourth core network device) for each PDU connection.

[0555] In step S9105, the target MME sends a handover request message to the target SAT-eNB2. This message creates a UE context in the target SAT-eNB2, including bearer-related information and security context. The S&F indication previously received from the source MME can also be sent to the target SAT-eNB2 to indicate that the SAT-eNB2 should support S&F capability.

[0556] In step S9106, if SAT-eNB2 supports S&F capability, SAT-eNB2 sends a handover request acknowledgement (ack) to the target MME. Otherwise, SAT-eNB2 sends a handover failure message to the target MME. A cause value is included in the handover failure message to indicate that the handover failure is due to SAT-eNB2 not supporting S&F capability.

[0557] In some embodiments, the target MME cleans up all reserved resources for the UE in the target MME.

[0558] In step S9107, if S-GW relocation has been performed, and if step S9104 is performed, the target MME sends a delete session request message to the target S-GW to delete the EPS bearer resources.

[0559] In step S9108, the target MME sends a forward relocation response message to the source MME. The target MME indicates that the handover failure is due to the target SAT-eNB2 not supporting S&F capability.

[0560] In step S9109, upon receiving the forward relocation response message, the source MME sends a handover preparation failure message to the source SAT-eNB1. The source MME uses a cause value (i.e. failure cause) to indicate that the handover failure is due to the target SAT-eNB2 not supporting S&F capability.

[0561] In step S9110, a handover command is sent to the UE to indicate that the handover failure is due to the target SAT-eNB2 not supporting S&F capability.

[0562] In step S9111, upon receiving the handover command, the UE will not access to SAT-eNB2. Before SAT-eNB1 detaches from the coverage, the UE initiates a tracking area update (TAU) procedure. The UE sends a TAU request to the source MME.

[0563] In step S9112, the source MME determines the start of unavailability period, and the duration of unavailability. These information are included in a TAU accept message and sent to the UE.

[0564] In some embodiments, the start of unavailability is set to the time when SAT-eNB1 detaches from the coverage area. The duration of unavailability is set to the time duration between the time when SAT-eNB1 detaches from the coverage area and the time when SAT-eNB1 next provides coverage to the area. All these information enable the UE to save power consumption during the time when SAT-eNB1 detaches from the coverage.

[0565] FIG. 9B is an interaction diagram of an exemplary embodiment of a mobility handling method according to an embodiment of the present disclosure. In this procedure, the MME and S-GW can not change during eNB handover.

[0566] As shown in FIG. 9B, the mobility handling method includes steps S9201 to S9110.

[0567] In step S9201, the UE accesses the EPC through the STA-eNB1, and downlink data is sent to the UE through the P-GW, the source S-GW, and the STA-eNB1. Over time, the source STA-eNB1 will move out of the coverage area of the UE, and the source STA-eNB1 decides to initiate an S1-based handover to the target STA-eNB2. This can be triggered, for example, by the absence of an X2 connection with the target STA-eNB2, or by an indication from the target STA-eNB2 after an X2-based handover is not successful.

[0568] In step S9202, the source STA-eNB1 sends a handover request (target TAI, etc.) to the MME (i.e., the first network element).

[0569] In step S9203, the MME sends a create session request message to the S-GW (i.e., the second network element) for each PDU connection.

[0570] In step S9204, the MME sends a handover request message to the target STA-eNB2. This message creates a UE context in the target STA-eNB2, including bearer-related information and a security context.

[0571] In some embodiments, the MME determines to send an S&F indication to the target STA-eNB2, taking into account that the source STA-eNB1 supports S&F capability. The S&F indication is used to indicate that the target STA-eNB2 should support S&F capability.

[0572] In step S9205, if the target STA-eNB2 supports S&F capability, the target STA-eNB2 sends a handover request acknowledgement to the MME. Otherwise, the target STA-eNB2 sends a handover failure message to the MME. The handover failure message contains a cause value to indicate that the handover failure is because the target STA-eNB2 does not support S&F capability.

[0573] In some embodiments, the MME cleans up all reserved resources for the UE in the target MME.

[0574] In step S9206, if step S9203 is performed, the MME sends a delete session request message to the S-GW to delete the EPS bearer resources.

[0575] In step S9207, when the MME receives the handover failure message, the MME sends a handover preparation failure message to the source SAT-eNB1. The MME uses a cause value to indicate that the handover failure is caused by the target SAT-eNB2 not supporting the S&F capability.

[0576] In step S9208, a handover command is sent to the UE to indicate that the handover failure is due to the target SAT-eNB2 not supporting the S&F capability.

[0577] In step S9209, after receiving the handover command, the UE will not access the SAT-eNB2. Before the SAT-eNB1 detaches from the coverage area, the UE initiates a tracking area update procedure. The UE sends a TAU request to the source MME.

[0578] In step S9210, the MME determines the start of unavailability and the duration of unavailability. These information are included in the TAU accept message and sent to the UE.

[0579] In some embodiments, the start of unavailability is set to the time when the SAT-eNB1 detaches from the coverage area. The duration of unavailability is set to the time duration between the time when the SAT-eNB1 detaches from the coverage area and the time when the SAT-eNB1 next provides coverage to the area. All these information enable the UE to save power consumption during the time when the SAT-eNB1 detaches from the coverage.

[0580] FIG. 9C is an interaction schematic diagram of an exemplary implementation of a mobility handling method according to an embodiment of the present disclosure. This procedure can be used to implement the handover of a UE from a source SAT-eNB1 to a target SAT-eNB2 over X2. At this time, the MME does not change, and the decision S-GW also does not change.

[0581] As shown in FIG. 9C, the mobility handling method includes steps S9301 to S9306.

[0582] In step S9301, the UE, the source SAT-eNB1, and the target SAT-eNB2 perform handover preparation and execution.

[0583] In step S9302, the target SAT-eNB2 sends a path switch request message to the MME to inform that the serving eNB of the UE is changed due to the movement of the satellite. The path switch request message can include the TAI and ECGI (E-UTRAN cell global identifier) of the target SAT-eNB2.

[0584] In some embodiments, the MME can know that the SAT-eNB2 supports S&F capability. In case that the SAT-eNB2 supports S&F capability, this can be realized by the SAT-eNB2 reporting its support of S&F capability through the path switch request message.

[0585] In some embodiments, after receiving the path switch request, the MME can request the SAT-eNB2 to report whether it supports S&F capability.

[0586] In step S9303, if the target SAT-eNB2 does not support S&F capability, and if the MME knows that the source SAT-eNB1 supports S&F capability (the SAT-eNB1 can report its support of S&F capability during the process of UE attachment via the SAT-eNB1), the MME can send a path switch request failure message to the target SAT-eNB2. The message can contain a cause value. The cause value indicates that the switch fails due to the fact that the target SAT-eNB2 does not support S&F capability.

[0587] In step S9304, by sending a release resource message, the target SAT-eNB2 informs the source SAT-eNB1 that the switch fails due to the fact that the target SAT-eNB2 does not support S&F capability, and triggers resource release.

[0588] In step S9305, when the SAT-eNB1 is going to be out of coverage, the UE initiates a tracking area update procedure. The UE sends a TAU request to the source MME.

[0589] In step S9306, the MME determines the start of unavailability, and the duration of unavailability. These information is contained in a TAU accept message and sent to the UE.

[0590] In some embodiments, the start of unavailability is set as the time when the SAT-eNB1 is out of coverage. The duration of unavailability is set as the duration between the time when the SAT-eNB1 is out of coverage and the time when the SAT-eNB1 provides coverage to the area next time. All these information enables the UE to save power consumption during the period when the SAT-eNB1 is out of coverage.

[0591] In the embodiments of the present disclosure, part or all of the steps, and optional implementation manners thereof, can be combined with part or all of the steps in other embodiments, or can be combined with optional implementation manners of other embodiments.

[0592] The embodiments of the present disclosure further provide a mobility processing apparatus for implementing any of the above methods. For example, the embodiments of the present disclosure provide a mobility processing apparatus comprising units or modules for implementing the steps performed by the network element in any of the above methods. For example, the embodiments of the present disclosure provide a mobility processing apparatus comprising units or modules for implementing the steps performed by the access network device in any of the above methods. For example, the embodiments of the present disclosure provide a mobility processing apparatus comprising units or modules for implementing the steps performed by the terminal in any of the above methods.

[0593] It should be understood that the division of units or modules in the above apparatus is only a logical functional division, and all or part of them can be integrated into one physical entity or physically separated. In addition, the units or modules in the apparatus can be implemented in the form of processor calling software: for example, the apparatus includes a processor connected with a memory, the memory stores instructions, and the processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules of the apparatus, wherein the processor is, for example, a general processor such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the apparatus or a memory outside the apparatus. Alternatively, the units or modules in the apparatus can be implemented in the form of hardware circuit, and the functions of part or all of the units or modules can be implemented by the design of the hardware circuit, and the hardware circuit can be understood as one or more processors; for example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC), and the functions of part or all of the units or modules are implemented by the design of the logical relationship between the elements in the circuit; for another example, in another implementation, the hardware circuit is a programmable logic device (PLD), and taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by a configuration file, thereby implementing the functions of part or all of the units or modules. All units or modules of the above apparatus can be implemented in the form of processor calling software, or all units or modules can be implemented in the form of hardware circuit, or part of the units or modules are implemented in the form of processor calling software, and the remaining part is implemented in the form of hardware circuit.

[0594] In the embodiments of the present disclosure, the processor is a circuit with signal processing capability. In one implementation, the processor can be a circuit with instruction reading and running capability, such as a central processing unit, a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), a digital signal processor (DSP), and the like. In another implementation, the processor can implement certain functions through a logical relationship of a hardware circuit, and the logical relationship of the hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by a special-purpose integrated circuit or a programmable logic device, such as an FPGA. In the reconfigurable hardware circuit, the processor loads a configuration document to implement the configuration of the hardware circuit. It can be understood that the processor loads an instruction to implement the functions of the above part or all units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), and the like.

[0595] FIG. 10 is a structural schematic diagram of a mobility processing apparatus provided by the embodiments of the present disclosure. As shown in FIG. 10, the mobility processing apparatus 1000 can include at least one of a transceiver module 1001 and a processing module 1002.

[0596] In some embodiments, the mobility processing apparatus 1000 can be the first network element 1031. In some embodiments, the transceiver module 1001 can be configured to send first information, where the first information is used to indicate a handover failure from a first access network device to a second access network device; and the first access network device and the second access network device are located on different satellites, the first access network device supports the S&F function, and the second access network device does not support the S&F function. Optionally, the transceiver module 1001 can be configured to perform at least one of the communication steps (for example, steps S3101, S3102, S3103, S3104, S3105, S3106, S3107, S3108, S3110, S3111, 3201, S3202, S3203, S3204, S3205, S3206, S3208, S3209, S3302, S3303, S3305, S3306) of sending and / or receiving performed by the first network element 1031 in any of the above methods, details of which are not repeated here.

[0597] In some embodiments, the mobility processing apparatus 1000 can be the first access network device 102A. In some embodiments, the transceiver module 1001 can be configured to receive first information, where the first information is used to indicate a handover failure from the first access network device to the second access network device; where the first access network device and the second access network device are located on different satellites, the first access network device supports S&F function, and the second access network device does not support S&F function. Optionally, the transceiver module 1001 can be configured to perform at least one of the communication steps (e.g., steps S3101, S3108, S3109, S3201, S3206, S3207, S3301, S3304) of transmitting and / or receiving performed by the first access network device 102A in any of the above methods, which will not be described herein again.

[0598] In some embodiments, the mobility processing apparatus 1000 can be the second access network device 102B. In some embodiments, the transceiver module 1001 can be configured to transmit second information, where the second information is used to indicate that the second access network device does not support S&F function; where the second access network device is located on a satellite. Optionally, the transceiver module 1001 can be configured to perform at least one of the communication steps (e.g., steps S3104, S3105, S3203, S3204, S3301, S3302, S3303, S3304) of transmitting and / or receiving performed by the second access network device 102B in any of the above methods, which will not be described herein again.

[0599] In some embodiments, the mobility processing apparatus 1000 can be the terminal 101. In some embodiments, the transceiver module 1001 can be configured to receive fourth information, where the fourth information is used to indicate that satellite access is unavailable. Optionally, the transceiver module 1001 can be configured to perform at least one of the communication steps (e.g., steps S3109, S3110, S3111, S3207, S3208, S3209, S3305, S3306) of transmitting and / or receiving performed by the terminal 101 in any of the above methods, which will not be described herein again.

[0600] In some embodiments, the transceiver module can include a transmitting module and / or a receiving module. The transmitting module and the receiving module can be separate or integrated together. Optionally, the transceiver module can be mutually replaced with a transceiver.

[0601] In some embodiments, the processing module can be one module or include multiple sub-modules. Optionally, the multiple sub-modules perform all or part of the steps required to be performed by the processing module. Optionally, the processing module can be mutually replaced with a processor.

[0602] FIG. 11A is a structural schematic diagram of a communication device provided by an embodiment of the present disclosure. The communication device 11100 can be a network device (for example, an access network device, a core network device, etc.), a terminal (for example, a user equipment, etc.), a chip, a chip system, or a processor supporting the network device to implement any of the above methods, or a chip, a chip system, or a processor supporting the terminal to implement any of the above methods. The communication device 11100 can be used to implement the methods described in the above method embodiments, and details can be referred to the descriptions in the above method embodiments.

[0603] As shown in FIG. 11A, the communication device 11100 includes one or more processors 11101. The processor 11101 can be a general purpose processor or a special purpose processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device apparatus (for example, a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process data of the programs. Optionally, the communication device 11100 is configured to execute any of the above methods. Optionally, the one or more processors 11101 are configured to invoke instructions to enable the communication device 11100 to execute any of the above methods.

[0604] In some embodiments, the communication device 11100 further includes one or more transceivers 11102. When the communication device 11100 includes the one or more transceivers 11102, the transceiver 11102 performs at least one of the communication steps (for example, steps S3101 to S3111, S3201 to S3209, S3301 to S3306, but not limited to) of transmitting and / or receiving in the above methods. In an optional embodiment, the transceiver can include a receiver and / or a transmitter, which can be separate or integrated together. Optionally, the terms of transceiver, transceiving unit, transceiver, transceiving circuit, interface circuit, interface, etc. can be replaced with each other, and the terms of transmitter, transmitting unit, transmitter, transmitting circuit, etc. can be replaced with each other, and the terms of receiver, receiving unit, receiver, receiving circuit, etc. can be replaced with each other.

[0605] In some embodiments, the communication device 11100 also includes one or more memories 11103 for storing data. Optionally, all or a portion of the memory 11103 can also reside in the communication device 11100. In some embodiments, the communication device 11100 can include one or more interface circuits 11104. Optionally, the interface circuit 11104 can be used to receive data from the memory 11103 or from another device or system, or to send data to the memory 11103 or to another device or system. For example, the interface circuit 11104 can receive data in packets, each packet having a header and a payload.

[0606] The communication device 11100 described in the above embodiments can be a network device or a terminal, but the scope of the communication device 11100 described in the present disclosure is not limited thereto, and the structure of the communication device 11100 can not be limited by FIG. 11A. The communication device can be a standalone device or can be part of a larger device. For example, the communication device can be: (1) a standalone integrated circuit (IC), or a chip, or a chip system or subsystem; (2) a set of one or more ICs, which can optionally also include a storage component for storing data, programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, a smart terminal device, a cellular phone, a wireless device, a handset, a mobile unit, a vehicle-mounted device, a network device, a cloud device, an artificial intelligence device, etc.; (6) other devices, etc.

[0607] FIG. 11B is a structural schematic diagram of a chip according to an embodiment of the present disclosure. For the case where the communication device 11100 is a chip or a chip system, the structural schematic diagram of the chip 11200 shown in FIG. 11B can be referred to, but is not limited thereto.

[0608] The chip 11200 includes one or more processors 11201. The chip 11200 is configured to perform any of the above methods.

[0609] In some embodiments, the chip 11200 further includes one or more interface circuits 11202. Optionally, the terms interface circuit, interface, transceiver pin, and the like can be replaced with each other. In some embodiments, the chip 11200 further includes one or more memories 11203 for storing data. Optionally, all or part of the memory 11203 can be outside the chip 11200. Optionally, the interface circuit 11202 is connected with the memory 11203, the interface circuit 11202 can be used to receive data from the memory 11203 or other devices, and the interface circuit 11202 can be used to send data to the memory 11203 or other devices. For example, the interface circuit 11202 can read the data stored in the memory 11203 and send the data to the processor 11201.

[0610] In some embodiments, the interface circuit 11202 performs at least one of the communication steps (for example, steps S3101 to S3111, S3201 to S3209, S3301 to S3306, but not limited to this) of transmitting and / or receiving in the above method. The interface circuit 11202 performing the communication steps such as transmitting and / or receiving in the above method means that the interface circuit 11202 performs data interaction between the processor 11201, the chip 11200, the memory 11203, or the transceiver device.

[0611] The modules and / or devices described in each of the embodiments of the virtual device, the physical device, the chip, and the like can be combined or separated as appropriate. Optionally, part or all of the steps can also be performed by multiple modules and / or devices in cooperation, which is not limited here.

[0612] The embodiments of the present disclosure also propose a storage medium, and the above storage medium stores instructions, when the above instructions run on the communication device 11100, the communication device 11100 executes any one of the above methods. Optionally, the above storage medium is an electronic storage medium. Optionally, the above storage medium is a computer readable storage medium, but is not limited to this, it can also be a storage medium readable by other devices. Optionally, the above storage medium can be a non-transitory storage medium, but is not limited to this, it can also be a transitory storage medium.

[0613] The embodiments of the present disclosure also propose a program product, and the above program product is executed by the communication device 11100, so that the communication device 11100 executes any one of the above methods. Optionally, the above program product is a computer program product.

[0614] The embodiments of the present disclosure also propose a computer program, when it runs on a computer, the computer executes any one of the above methods.

[0615] Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.

[0616] It is to be understood that the application is not limited to the precise construction herein described and as shown in the attached drawings, and that various modifications and changes can be made by those skilled in the art without departing from the scope of the application. The scope of the application is to be indicated by the appended claims, rather than the description and examples.

Claims

1. A mobility processing method, performed by a first network element, wherein: The method comprises: Sending first information, where the first information is used to indicate that handover from the first access network device to the second access network device has failed; The first access network device and the second access network device are located on different satellites, the first access network device supports the store and forward (S&F) function, and the second access network device does not support the S&F function.

2. The method according to claim 1, wherein The first information includes a reason for the handover failure, where the reason for the handover failure is used to indicate that the second access network device does not support the S&F function.

3. The method according to claim 1 or 2, wherein: The method further comprises: Second information is received, where the second information is used to indicate that the second access network device does not support the S&F function.

4. The method according to any one of claims 1 to 3, wherein The method further comprises: Receive or send third information, wherein the third information is used to determine that the second access network device needs to support the S&F function.

5. The method according to claim 4, wherein The third information is determined based on whether the first access network device supports the S&F function.

6. The method according to any one of claims 1 to 5, wherein The method further comprises: Fourth information is sent, where the fourth information is used to indicate that satellite access is unavailable.

7. The method according to claim 6, wherein: The fourth information includes at least one of the following: indication information for indicating that the satellite access is unavailable; The start time of the satellite access unavailability; The duration for which the satellite access is unavailable.

8. The method according to claim 6 or 7, wherein: During the period when the satellite access is unavailable, data and / or signaling related to the terminal are stored in the first access network device, and the terminal is in a first state.

9. A mobility processing method, performed by a first access network device, wherein: The method comprises: receiving first information, wherein the first information is used to indicate that handover from the first access network device to the second access network device has failed; The first access network device and the second access network device are located on different satellites, the first access network device supports the store and forward (S&F) function, and the second access network device does not support the S&F function.

10. The method according to claim 9, wherein: The first information includes a reason for the handover failure, where the reason for the handover failure is used to indicate that the second access network device does not support the S&F function.

11. The method according to claim 9 or 10, wherein: The method further comprises: Store data and / or signaling related to the terminal.

12. The method according to any one of claims 9 to 11, wherein The method further comprises: Send the first information to the terminal.

13. A mobility processing method, performed by a second access network device, wherein: The method comprises: Sending second information, wherein the second information is used to indicate that the second access network device does not support a store and forward (S&F) function; The second access network device is located on a satellite.

14. The method according to claim 13, wherein The method further comprises: Receive third information, where the third information is used to determine that the second access network device needs to support the S&F function.

15. The method according to claim 13, wherein: The method further comprises: First information is received, where the first information is used to indicate that handover from the first access network device to the second access network device has failed.

16. A mobility processing method, executed by a terminal, wherein: The method comprises: Fourth information is received, where the fourth information is used to indicate that satellite access is unavailable.

17. The method according to claim 16, wherein The fourth information includes at least one of the following: indication information for indicating that the satellite access is unavailable; The start time of the satellite access unavailability; The duration for which the satellite access is unavailable.

18. The method according to claim 16 or 17, wherein During the period when the satellite access is unavailable, data and / or signaling related to the terminal are stored in the first access network device, and the terminal is in a first state.

19. The method according to any one of claims 16 to 18, wherein The method further comprises: receiving first information, wherein the first information is used to indicate that handover from the first access network device to the second access network device has failed; The first access network device and the second access network device are located on different satellites, the first access network device supports the store and forward (S&F) function, and the second access network device does not support the S&F function.

20. The method according to claim 19, wherein The first information includes a reason for the handover failure, where the reason for the handover failure is used to indicate that the second access network device does not support the S&F function.

21. A mobility processing method, executed by a core network device, wherein: The method comprises: receiving second information, wherein the second information is used to indicate that the second access network device does not support a store and forward (S&F) function; Sending first information, where the first information is used to indicate that handover from the first access network device to the second access network device has failed; The first access network device and the second access network device are located on different satellites, and the first access network device supports S&F functions.

22. A mobility processing device, provided in a first network element, wherein: The device comprises: a transceiver module configured to send first information, wherein the first information is used to indicate a handover failure from the first access network device to the second access network device; The first access network device and the second access network device are located on different satellites, the first access network device supports the store and forward (S&F) function, and the second access network device does not support the S&F function.

23. A mobility processing device, provided in a first access network device, wherein: The device comprises: a transceiver module configured to receive first information, wherein the first information is used to indicate that handover from the first access network device to the second access network device has failed; The first access network device and the second access network device are located on different satellites, the first access network device supports the store and forward (S&F) function, and the second access network device does not support the S&F function.

24. A mobility processing device, provided in a second access network device, wherein: The device comprises: a transceiver module configured to send second information, wherein the second information is used to indicate that the second access network device does not support a store and forward (S&F) function; The second access network device is located on a satellite.

25. A mobility processing device, provided in a terminal, wherein: The device comprises: The transceiver module is configured to receive fourth information, wherein the fourth information is used to indicate that satellite access is unavailable.

26. A communication device comprising: one or more processors; a memory storing instructions; When the instruction is executed by the communication device, the communication device implements one of the following: The method according to any one of claims 1 to 8; The method according to any one of claims 9 to 12; The method according to any one of claims 13 to 15; The method according to any one of claims 16 to 20; The method of claim 21.

27. A mobility processing method, performed by a communication system, wherein: The communication system includes at least one of the following: a first network element, a first access network device, and a second access network device; The method comprises: The first network element sends first information, wherein the first information is used to indicate that handover from the first access network device to the second access network device fails; The first access network device receives the first information; The first access network device and the second access network device are located on different satellites, the first access network device supports the store and forward (S&F) function, and the second access network device does not support the S&F function.

28. A communication system comprising at least one of the following: a first network element, a first access network device, and a second access network device; in, The communication system is configured to implement the method according to claim 27.

29. A storage medium storing instructions, wherein: When the instructions are executed on a communication device, the communication device is caused to implement at least one of the following: The method according to any one of claims 1 to 8; The method according to any one of claims 9 to 12; The method according to any one of claims 13 to 15; The method according to any one of claims 16 to 20; The method of claim 21.

30. A computer program product comprising instructions, wherein when the instructions are executed on a communication device, the communication device is caused to implement at least one of the following: The method according to any one of claims 1 to 8; The method according to any one of claims 9 to 12; The method according to any one of claims 13 to 15; The method according to any one of claims 16 to 20; The method of claim 21.

Images