WO2025208282A1 - Communication method, device, and storage medium - Google Patents

Abstract

The present disclosure relates to the technical field of communications, and relates to a communication method, a device, and a storage medium. The method is executed by a first access network device, and the first access network device is the current service device of a terminal. The method comprises: under a first condition, sending first information to a first core network device and/or sending second information to a second access network device, wherein the first information and/or the second information are/is used for instructing to execute a terminal context migration process, the terminal context migration process comprises a switching process of a single terminal or context migration processes of a plurality of terminals, the first condition is that a change occurs in a communication link between the first access network device and the first core network device, and the first core network device is the current service device of the terminal. When it is determined that a change has occurred or is about to occur in the communication link between the first access network device and the first core network device, the terminal is instructed to execute context switching or migration, thereby ensuring the service continuity of a connected terminal and avoiding service interruption of the terminal.

Description

Communication method, device and storage medium Technical Field

The present disclosure relates to the field of communication technology, and in particular to a communication method, device, and storage medium.

Background Art

Non-Terrestrial Network (NTN) technology provides wireless resources via satellites (or drones) rather than ground base stations. By integrating satellite communication networks with terrestrial 5G networks, NTN can provide ubiquitous coverage regardless of terrain.

Summary of the Invention

The embodiments of the present disclosure provide a communication method, device, and storage medium, which can be used in the field of communication technology to solve the problem of service interruption of connected terminals due to feeder link switching or failure and changes in the core network.

According to a first aspect of an embodiment of the present disclosure, a communication method is proposed, which is executed by a first access network device, comprising: under a first condition, sending first information to a first core network device and/or sending second information to a second access network device, wherein the first information and/or the second information is used to indicate the execution of a terminal context migration process, the terminal context migration process includes a switching process of a single terminal or a context migration process of multiple terminals, the first condition is a change in the communication link between the first access network device and the first core network device, and the first core network device is the current service device of the terminal.

According to the second aspect of an embodiment of the present disclosure, a communication method is proposed, which is executed by a first core network device, including: receiving first information sent by a first access network device under a first condition, wherein the first information is used to indicate the execution of a terminal context migration process, the terminal context migration process includes a switching process of a single terminal or a context migration process of multiple terminals, the first condition is a change in the communication link between the first access network device and the first core network device, and the first access network device and/or the first core network device is the current service device of the terminal.

According to a third aspect of an embodiment of the present disclosure, a communication method is proposed, which is executed by a second access network device, including: receiving second information sent by a first access network device under a first condition, wherein the second information is used to indicate the execution of a terminal context migration process, the terminal context migration process includes a switching process of a single terminal or a context migration process of multiple terminals, the first condition is a change in the communication link between the first access network device and the first core network device, and the first access network device and/or the first core network device is the current service device of the terminal.

According to the fourth aspect of an embodiment of the present disclosure, an access network device is proposed, which is the current service device of the terminal, including a transceiver module, for sending first information to a first core network device and/or sending second information to a second access network device under a first condition, the first information and/or the second information being used to indicate the execution of a terminal context migration process, the terminal context migration process including a switching process of a single terminal or a context migration process of multiple terminals, the first condition being a change in the communication link between the first access network device and the first core network device, and the first core network device being the current service device of the terminal.

According to the fifth aspect of an embodiment of the present disclosure, a core network device is proposed, including a transceiver module for receiving first information sent by a first access network device under a first condition, wherein the first information is used to indicate the execution of a terminal context migration process, the terminal context migration process includes a switching process of a single terminal or a context migration process of multiple terminals, the first condition is a change in the communication link between the first access network device and the first core network device, and the first access network device and/or the first core network device is the current service device of the terminal.

According to the sixth aspect of an embodiment of the present disclosure, an access network device is proposed, comprising a transceiver module for receiving second information sent by a first access network device under a first condition, wherein the second information is used to indicate the execution of a terminal context migration process, the terminal context migration process including a switching process of a single terminal or a context migration process of multiple terminals, the first condition being a change in the communication link between the first access network device and the first core network device, and the first access network device and/or the first core network device being the current service device of the terminal.

According to the seventh aspect of the embodiment of the present disclosure, a communication device is proposed, including a transceiver; a memory; and a processor, which are connected to the transceiver and the memory respectively, and are configured to control the wireless signal reception and transmission of the transceiver by executing computer-executable instructions on the memory, and can implement the communication methods of the first aspect, the second aspect, and the third aspect.

According to an eighth aspect of an embodiment of the present disclosure, a communication system is proposed, including a terminal, a first access network device configured to implement the communication method of the first aspect, and a first core network device configured to implement the communication method of the second aspect.

According to the ninth aspect of the embodiment of the present disclosure, a computer storage medium is proposed, wherein the computer storage medium stores computer-executable instructions; after the computer-executable instructions are executed by the processor, the communication methods of the first aspect, the second aspect, and the third aspect can be implemented.

According to a tenth aspect of the embodiments of the present disclosure, a computer program product is proposed, including a computer program, which is executed to implement the communication methods of the first aspect, the second aspect, and the third aspect.

According to the communication method proposed in the present disclosure, under a first condition, the first access network device sends first information to the first core network device and/or sends second information to the second access network device, wherein the first information and/or the second information are used to indicate the execution of a terminal context migration process, and the terminal context migration process includes a switching process of a single terminal or a context migration process of multiple terminals. The first condition is a change in the communication link between the first access network device and the ground receiving station of the first core network device, and the first core network device is the current service device of the terminal. Implementing terminal context migration when the communication link changes can reduce unnecessary signaling overhead and reduce the impact on air interface signaling, thereby improving system efficiency and ensuring service continuity of the terminal under the coverage of the mobile access network.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

FIG1 is a diagram of a system architecture provided according to an embodiment of the present disclosure.

FIG2A is an interactive schematic diagram of a communication method provided according to an embodiment of the present disclosure.

FIG2B is an interactive diagram of a communication method provided according to an embodiment of the present disclosure.

FIG2C is an interactive diagram of a communication method provided according to an embodiment of the present disclosure.

FIG3A is a flow chart of a communication method of a first access network device provided according to an embodiment of the present disclosure.

FIG3B is a flow chart of a communication method of a first access network device provided according to an embodiment of the present disclosure.

FIG3C is a flow chart of a communication method of a first access network device according to an embodiment of the present disclosure.

FIG3D is a flow chart of a communication method of a first access network device provided according to an embodiment of the present disclosure.

FIG4A is a flow chart of a communication method of a first core network device provided according to an embodiment of the present disclosure.

FIG4B is a flow chart of a communication method of a first core network device provided according to an embodiment of the present disclosure.

FIG4C is a flow chart of a communication method of a first core network device provided according to an embodiment of the present disclosure.

FIG4D is a flow chart of a communication method of a first core network device provided according to an embodiment of the present disclosure.

FIG5A is a flow chart of a communication method of a second access network device according to an embodiment of the present disclosure.

FIG5B is a flow chart of a communication method of a second access network device according to an embodiment of the present disclosure.

FIG6 is an interactive diagram of a communication method provided according to an embodiment of the present disclosure.

FIG7A is an interactive diagram of a communication method proposed according to an embodiment of the present disclosure.

FIG7B is an interactive diagram of a communication method proposed according to an embodiment of the present disclosure.

FIG7C is an interactive diagram of a communication method proposed according to an embodiment of the present disclosure.

FIG8A is a schematic structural diagram of an access network device proposed according to an embodiment of the present disclosure.

FIG8B is a schematic structural diagram of an access network device proposed according to an embodiment of the present disclosure.

FIG8C is a schematic structural diagram of a core network device according to an embodiment of the present disclosure.

FIG9A is a schematic structural diagram of a communication device proposed according to an embodiment of the present disclosure.

FIG9B is a schematic diagram of the structure of the chip proposed in an embodiment of the present disclosure.

DETAILED DESCRIPTION

The embodiments of the present disclosure provide a communication method, a device, and a storage medium.

In a first aspect, an embodiment of the present disclosure provides a communication method, which is executed by a first access network device, and the first access network device is the current service device of the terminal. The method includes: under a first condition, sending first information to the first core network device and/or sending second information to the second access network device, wherein the first information and/or the second information is used to indicate the execution of a terminal context migration process, and the terminal context migration process includes a switching process of a single terminal or a context migration process of multiple terminals. The first condition is a change in the communication link between the first access network device and the ground receiving station of the first core network device, and the first core network device is the current service device of the terminal.

In combination with some embodiments of the first aspect, in some embodiments, the first information is used to instruct the first core network device to migrate the context information of the terminal from the first core network device to the second core network device, and the second core network device is the target device of the migration; and/or the second information is used to instruct The second access network device migrates the context information of the terminal from the first access network device to the second access network device, and the first access network device and the second access network device are located in the same core network domain.

In the above embodiments, the context migration of one or more terminals is performed when the core network device changes but the access network device remains unchanged, and the context migration of one or more terminals is performed when the core network device remains unchanged but the access network device changes. This can avoid terminal service interruption caused by changes in the communication link and ensure terminal service continuity.

In combination with some embodiments of the first aspect, in some embodiments, the first information is included in a first message, the first message is a switching request message for a specific terminal, and the first information includes at least one of an identification of a candidate core network device and a switching reason.

In combination with some embodiments of the first aspect, in some embodiments, the first information is included in a first message, the first message is a message for performing context migration on one or more terminals, the first information includes the identification of the candidate core network device, the migration reason, the migration indication, and at least one item in the first terminal identification list, and the first terminal identification list includes the identification of one or more terminals.

In combination with some embodiments of the first aspect, in some embodiments, the method also includes: receiving third information sent by the second core network device, the third information includes context information of one or more terminals, and the second core network device is one or more of the candidate core network devices.

In combination with some embodiments of the first aspect, in some embodiments, the method further includes: sending fourth information to the second core network device, the fourth information including at least one item in the second terminal identification list of successful migration and the third terminal identification list of failed migration.

In combination with some embodiments of the first aspect, in some embodiments, the terminal identifier included in at least one of the first terminal identifier list, the second terminal identifier list, and the third terminal identifier list is a Next Generation Access Control Protocol NGAP terminal identifier.

In combination with some embodiments of the first aspect, in some embodiments, the method further includes: receiving fifth information from a candidate access network device; and determining a second access network device from the candidate access network devices based on the fifth information.

In combination with some embodiments of the first aspect, in some embodiments, the fifth information includes the core network device to which the candidate access network device can be connected and the validity time, wherein, based on the fifth information, determining the second access network device from the candidate access network devices includes: based on the fifth information, the core network device that can be connected at the moment when the first condition is met is a candidate access network device of the first core network device, and is determined as the second access network device.

In combination with some embodiments of the first aspect, in some embodiments, the method further includes: determining whether the first condition is met.

In combination with some embodiments of the first aspect, in some embodiments, determining whether the first condition is met includes at least one of the following: determining whether the first condition is met based on the link quality between the first access network device and the first core network device; determining whether the first condition is met based on the location information of the first access network device and the service area corresponding to the first core network device.

In combination with some embodiments of the first aspect, in some embodiments, determining whether the first condition is met includes: receiving sixth information sent by the first core network device, the sixth information including at least one of a core network change indication, a change reason, and a change time; and determining whether the first condition is met based on the sixth information.

In combination with some embodiments of the first aspect, in some embodiments, the first access network device has mobility.

In combination with some embodiments of the first aspect, in some embodiments, the first condition includes at least one of the following: change of the first core network device; switching of the communication link; failure of the communication link.

In a second aspect, an embodiment of the present disclosure provides a communication method, which is executed by a first core network device, and the method includes: receiving first information sent by a first access network device under a first condition, wherein the first information is used to indicate the execution of a terminal context migration process, the terminal context migration process includes a switching process of a single terminal or a context migration process of multiple terminals, the first condition is a change in the communication link between the first access network device and the first core network device, and the first access network device and/or the first core network device is the current service device of the terminal.

In combination with some embodiments of the second aspect, in some embodiments, the first information is used to instruct the first core network device to migrate the context information of the terminal from the first core network device to the second core network device, and the second core network device is the target device of the migration.

In combination with some embodiments of the second aspect, in some embodiments, the first information is included in a first message, the first message is a switching request message for a specific terminal, and the first information includes at least one of an identification of a candidate core network device and a switching reason.

In combination with some embodiments of the second aspect, in some embodiments, the first information is included in a first message, the first message is a message for performing context migration on one or more terminals, the first information includes the identification of the candidate core network device, the migration reason, the migration indication, and at least one item in the first terminal identification list, and the first terminal identification list includes the identification of one or more terminals.

In combination with some embodiments of the second aspect, in some embodiments, the terminal identifiers included in the first terminal identifier list are Next Generation Access Protocol NGAP terminal identifiers.

In combination with some embodiments of the second aspect, in some embodiments, the method also includes: sending sixth information to the first access network device, the sixth information including at least one of a core network change indication, a change reason, and a change time, and the sixth information is used to assist the first access network device in determining whether the first condition is met.

In combination with some embodiments of the second aspect, in some embodiments, the first access network device has mobility.

In combination with some embodiments of the second aspect, in some embodiments, the first condition includes at least one of the following: change of the first core network device; switching of the communication link; failure of the communication link.

In a third aspect, an embodiment of the present disclosure provides a communication method, which is executed by a second access network device, and the method includes: receiving second information sent by a first access network device under a first condition, wherein the second information is used to indicate the execution of a terminal context migration process, the terminal context migration process includes a switching process of a single terminal or a context migration process of multiple terminals, the first condition is a change in the communication link between the first access network device and the first core network device, and the first access network device and/or the first core network device is the current service device of the terminal.

In combination with some embodiments of the third aspect, in some embodiments, the second information is used to instruct the second access network device to migrate the context information of the terminal from the first access network device to the second access network device, and the core network domain of the first access network device and the second access network device is the same.

In combination with some embodiments of the third aspect, in some embodiments, the method further includes: sending fifth information to the first access network device, the fifth information including the core network device to which the second access network device can connect and the validity period.

In combination with some embodiments of the third aspect, in some embodiments, the second access network device is: an access network device to which the core network device that can be connected when the first condition is met is the first core network device.

In combination with some embodiments of the third aspect, in some embodiments, the first access network device has mobility.

In combination with some embodiments of the third aspect, in some embodiments, the first condition includes at least one of the following: change of the first core network device; switching of the communication link; failure of the communication link.

In a fourth aspect, an embodiment of the present disclosure provides an access network device, which is the current service device of the terminal, and includes: a transceiver module, used to send first information to a first core network device and/or send second information to a second access network device under a first condition, wherein the first information and/or the second information is used to indicate the execution of a terminal context migration process, the terminal context migration process includes a switching process of a single terminal or a context migration process of multiple terminals, the first condition is a change in the communication link between the first access network device and the ground receiving station of the first core network device, and the first core network device is the current service device of the terminal.

In the fifth aspect, an embodiment of the present disclosure provides a core network device, including: a transceiver module, used to receive first information sent by a first access network device under a first condition, wherein the first information is used to indicate the execution of a terminal context migration process, the terminal context migration process includes a switching process of a single terminal or a context migration process of multiple terminals, the first condition is a change in the communication link between the first access network device and the first core network device, and the first access network device and/or the first core network device is the current service device of the terminal.

In the sixth aspect, an embodiment of the present disclosure provides an access network device, including a transceiver module, for receiving second information sent by a first access network device under a first condition, wherein the second information is used to indicate the execution of a terminal context migration process, the terminal context migration process includes a switching process of a single terminal or a context migration process of multiple terminals, the first condition is a change in the communication link between the first access network device and the first core network device, and the first access network device and/or the first core network device is the current service device of the terminal.

In the seventh aspect, an embodiment of the present disclosure provides a communication device, including: a transceiver; a memory; and a processor, which are connected to the transceiver and the memory respectively, and are configured to control the wireless signal reception and transmission of the transceiver by executing computer-executable instructions on the memory, and can implement the method described in any embodiment of the first to third aspects of the present disclosure.

In the eighth aspect, an embodiment of the present disclosure provides a communication system, including a terminal, a first access network device configured to implement the method described in any one of the embodiments in the first aspect of the present disclosure, and a first core network device configured to implement the method described in any one of the embodiments in the second aspect of the present disclosure.

In combination with the embodiments of the eighth aspect, in some embodiments, the communication system also includes a second access network device configured to implement the method described in any one of the embodiments of the third aspect of this disclosure; or, further includes a second core network device.

In the ninth aspect, an embodiment of the present disclosure provides a storage medium, wherein the computer storage medium stores computer-executable instructions; after the computer-executable instructions are executed by a processor, the method described in any one of the embodiments of the first to third aspects of the present disclosure can be implemented.

In a tenth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the optional implementation of the first to third aspects.

In an eleventh aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation manners of the first to third aspects.

In a twelfth aspect, an embodiment of the present disclosure provides a chip or a chip system, which includes a processing circuit configured to execute the method described in the optional implementation of the first to third aspects above.

It is understandable that the first access network device, the second access network device, the first core network device, the second core network device, the storage medium, the program product, the computer program, the chip, or the chip system described above are all used to perform the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

The present disclosure provides a communication method, device, and storage medium. In some embodiments, the terms "communication method" and "information processing method" are interchangeable; the terms "first access network device," "second access network device," "first core network device," "second core network device," "information processing device," and "communication device" are interchangeable; and the terms "information processing system" and "communication system" are interchangeable.

The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and/or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "the", etc., can mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article can be understood as a singular expression or a plural expression.

In the embodiments of the present disclosure, “plurality” refers to two or more.

In some embodiments, the terms “at least one of,” “at least one of,” “at least one of,” “one or more,” “a plurality of,” “multiple,” etc. may be used interchangeably.

In the embodiments of the present disclosure, descriptions such as “at least one of A, B, C…”, “A and/or B and/or C…”, etc. include the situation where any one of A, B, C… exists alone, and also include any combination of any multiple of A, B, C…, and each situation can exist alone; for example, “at least one of A, B, C” includes the situation where A exists alone, B exists alone, C exists alone, the combination of A and B, the combination of A and C, the combination of B and C, and the combination of A, B, and C; for example, A and/or B includes the situation where A exists alone, B exists alone, and the combination of A and B.

In some embodiments, descriptions such as "in one case A, in another case B," or "in response to one case A, in response to another case B," may include the following technical solutions depending on the situation: executing A independently of B (in some embodiments, A); executing B independently of A (in some embodiments, B); selectively executing A and B (in some embodiments, selecting between A and B); and executing both A and B (in some embodiments, A and B). The same applies when there are more branches, such as A, B, and C.

The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restrictions on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restrictions should be imposed due to the use of prefixes. For example, if the description object is a "field," the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields." "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field." For another example, if the description object is a "level," the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels." For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device," then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different. For another example, if the description object is "information," then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

In some embodiments, terms such as "time/frequency" and "time/frequency domain" refer to the time domain and/or the frequency domain.

In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

In some embodiments, terms such as "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 less than," and "above" can be replaced with each other, and terms such as "less than," "less than or equal to," "not greater than," "less than," "less than or equal to," "not more than," "lower than," "lower than or equal to," "not higher than," and "below" can be replaced with each other.

In some embodiments, devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as "device," "equipment," "device," "circuit," "network element," "node," "function," "unit," "section," "system," "network," "chip," "chip system," "entity," and "subject" can be used interchangeably.

In some embodiments, "network" can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

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," "carrier," "component carrier," and "bandwidth part (BWP)" may be used interchangeably.

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, etc. can be used interchangeably.

In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

In some embodiments, data, information, etc. may be obtained with the user's consent.

During NTN operation, there may be a need to switch feeder links (SRIs) between different NTN GWs to the same satellite, known as feeder link switching, or a need to migrate feeder links between the same NTN GW to a different satellite, known as feeder link failure. This can be due to, for example, maintenance, traffic offloading, or, for Low Earth Orbit (LEO), satellite movement out of the visibility range relative to the current NTN GW. Switching or migration should be performed without causing service interruption to the served terminals, and this can be performed in different ways depending on the deployed NTN architecture. Switching or migration can be used interchangeably; both represent the transfer of terminal context information.

In the architectural option, the complete gNB is on the satellite as a payload. If we consider the LEO case, this case is much simpler from the Uu perspective than the transparent LEO NTN, because the Uu is transmitted only over the serving link, compared to transmitting over the serving and feeder links. As long as the security keys of the gNB are preserved, the feeder link switching on the Uu interface can be transparent.

In non-geostationary satellite orbit (NON-GEO) systems, the connection between the satellite and the ground gateway in the base station domain changes as the satellite moves, which is called a feeder link switch or feeder link failure. During this process, the connection is interrupted due to changes in the core network equipment (AMF). Current technology will release the connected UE, resulting in UE service interruption. Therefore, maintaining the connection between the gNB and the core network (such as the AMF) and ensuring service continuity are urgent issues that need to be addressed.

Therefore, the present disclosure proposes a communication method, device, and storage medium, which, when it is confirmed that a feeder link has changed or is about to change, instructs the terminal to perform context switching or migration to ensure service continuity of the connected terminal.

The method proposed in the present disclosure is applicable to various communication systems, including but not limited to 4G, 5G, 5G-advance and subsequent communication technologies (such as 6G, etc.).

Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in Figure 1, the communication system 100 may include a terminal 101, a first access network device 102, a second access network device 103, a first core network device 104, and a second core network device 105. In different embodiments, the devices in the communication system 100 may be different.

In some embodiments, terminal 101 may be a device that performs context migration.

In some embodiments, the first access network device 102 is mobile, and is, for example, an access network device on a satellite, an air access network device, or an access network device on a ground vehicle.

In some embodiments, the first access network device 102 may be a device that confirms the first condition.

In some embodiments, the first access network device 102 may be a device that initiates terminal context migration.

In some embodiments, the first access network device 102 may be a device that sends first information to the first core network device, where the first information is used to instruct the first core network device to migrate the context information of the terminal from the first core network device to the second core network device.

In some embodiments, the first access network device 102 may be a device that sends second information to the second access network device, where the second information is used to instruct the second access network device to migrate the context information of the terminal from the first access network device to the second access network device.

In some embodiments, the first access network device 102 may receive context information of the terminal sent by the second core network device.

In some embodiments, the first access network device 102 may send a second terminal identification list of successful migrations and a third terminal identification list of failed migrations to the second core network device.

In some embodiments, the first access network device 102 may be a device for determining the second access network device.

In some embodiments, the name of the first access network device 102 is not limited, and it can be, for example, "a device for confirming the first condition" or "a device for initiating terminal context migration".

In some embodiments, the second access network device 103 may be a device that receives second information, where the second information is used to instruct the second access network device to migrate the context information of the terminal from the first access network device to the second access network device.

In some embodiments, the second access network device 103 may be a device that sends real-time capability information of a candidate computing node.

In some embodiments, the second access network device 103 may be a device that sends fifth information to the first access network device, and the fifth information may be a core network device to which the candidate access network device can connect and a valid time.

In some embodiments, the second access network device 103 may be a device that receives context information of terminal migration.

In some embodiments, the second access network device 103 may be a candidate access network device.

In some embodiments, the name of the second access network device 103 is not limited, and it may be, for example, a “device for receiving context information of terminal migration”.

In some embodiments, the first core network device 104 may be a device that receives first information sent by the first access network device, where the first information is used to instruct the first core network device to migrate the context information of the terminal from the first core network device to the second core network device.

In some embodiments, the first core network device 104 may be the current serving device of the terminal.

In some embodiments, the first core network device 104 may be a device that sends sixth information to the first access network device, where the sixth information includes at least one of a core network change indication, a change reason, and a change time.

In some embodiments, the name of the first core network device 104 is not limited, and it can be, for example, a "terminal service device", a "device for performing terminal context migration", or a "device for performing terminal context migration".

In some embodiments, the second core network device 105 may be a target device for terminal migration.

In some embodiments, the second core network device 105 may be a device that sends third information, where the third information includes context information of one or more terminals.

In some embodiments, the second core network device 105 may be one or more of the candidate core network devices.

In some embodiments, the second core network device 105 may be a device that receives fourth information, where the fourth information includes at least one of a second terminal identification list of successfully migrated terminals and a third terminal identification list of failed migration terminals.

In some embodiments, the name of the second core network device 105 is not limited, and it can be, for example, a "device that receives terminal context migration" or a "target device for terminal context migration."

In some embodiments, the first core network device 104 and/or the second core network device 105 may be an access and mobility management function (AMF) network element.

In some embodiments, the communication system 100 includes a terminal, a first access network device, a first core network device, and a second core network device. The communication system is used to implement a context migration process of the terminal when the access network device remains unchanged but the core network device changes, switching the context information of the terminal from the first core network device to the second core network device, or migrating the context information of multiple terminals from the first core network device to the second core network device.

In some embodiments, the communication system 100 includes a terminal, a first access network device, a second access network device, and a first core network device, and is used to implement a terminal context migration process when the core network device remains unchanged but the access network device changes, and migrate the terminal's context information from the first access network device to the second access network device.

In some embodiments, the terminal may include at least one of a mobile phone, a wearable device, an Internet of Things device, a car with communication capabilities, a smart car, a tablet computer, a computer with wireless transceiver capabilities, 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 a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and a wireless terminal device in a smart home, but is not limited thereto.

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

The following embodiments of the present disclosure may be applied to the communication system 100 shown in Figure 1, or a portion thereof, but are not limited thereto. The entities shown in Figure 1 are illustrative only. The communication system may include all or part of the entities shown in Figure 1, or may include other entities outside of Figure 1. The number and form of the entities may be arbitrary. The connection relationship between the entities is illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), G The present invention relates to a global system for mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other user plane path establishment methods, and next-generation systems based on and extended from these systems. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G) for application.

Figure 2A is a schematic diagram of an interaction method provided by an embodiment of the present disclosure. As shown in Figure 2A, an embodiment of the present disclosure relates to a communication method, which can be performed by a communication system, such as the communication system 100 shown in Figure 1. The communication system includes a terminal, a first access network device, a first core network device, and a second core network device. The interaction method may include the following steps:

Step 2101a: The first core network device sends sixth information to the first access network device.

In some embodiments, the sixth information is included in a sixth message.

In some embodiments, the sixth information includes at least one of a core network change indication, a change reason, and a change time.

In some embodiments, the cause of the change may be the mobility of the first access network device. For example, the first access network device is deployed on a satellite and the AMF is deployed on the ground. Changes in the GW connected to the satellite cause changes in the AMF connected to the first access network device.

For example, the first access network device receives a sixth message from the first core network device, and the sixth message includes sixth information, which is used to indicate that the connected core network is about to change. The sixth information includes the reason for the change in the core network, such as a feeder link switching or a feeder link failure.

Step 2101b: The first access network device determines whether the first condition is met.

In some embodiments, the first condition may be a change in the communication link between the first access network device and the ground receiving station of the first core network device. The communication link change includes an imminent change and a completed change. An imminent change indicates that a handover is required but has not yet been made, such as a hard handover, where the old link is disconnected but the new link is not yet connected. A completed change indicates that a handover has already been made, such as a soft handover, where the old link is not yet disconnected but the new link is already connected.

In some embodiments, the first condition may be a change in the first core network device.

In some embodiments, the first core network device changes because the first access network device is mobile. For example, the first access network device is deployed on a moving vehicle or airplane. When the first access network device moves out of the service area of the first core network device, the connected first core network device changes.

In some embodiments, the change of the first core network is caused by the configuration of the core network, for example, the load of the first core network device is high and the first core network device can no longer serve the terminal.

In some embodiments, the first condition may be a communication link switch.

In some embodiments, the first condition may be a communication link failure.

In some embodiments, the communication link can be a feeder link between a satellite and a ground gateway GW. The first access network device is deployed on the satellite, and the first core network device is deployed on the ground. The communication link is switched to a feeder link switch (feeder link switch). The feeder link switch may occur due to a change in the GW connected to the ground caused by the movement of the satellite.

In some embodiments, the communication link may be a feeder link between a satellite and a ground gateway GW, the first access network device is deployed on the satellite, and the first core network device is deployed on the ground. The communication link failure is a feeder link failure (feeder link failure), for example, the feeder link failure is caused by a poor wireless environment. In some embodiments, the first access network device determines whether the first condition is satisfied based on the sixth information.

In some embodiments, the first access network device determines whether the first condition is met based on the link quality between the first access network device and the first core network device.

In some embodiments, the first access network device determines whether the first condition is satisfied based on location information of the first access network device and a service area corresponding to the first core network device, wherein the location information includes ephemeris information and/or motion trajectory.

Step 2102: The first access network device sends first information to the first core network device.

In some embodiments, the first information may be carried by a first message. In other words, the first information is included in the first message, and the first message is a handover request message for a specific terminal. In other words, if there are multiple terminals that require context migration, the first access network device needs to send multiple first messages, each of which is a handover request message for a different terminal.

In some embodiments, the first information is used to instruct the first core network device to migrate the context information of a specific terminal from the first core network device to the second core network device, and the second core network device is the target device of the migration.

In some embodiments, the first information includes at least one of an identifier of the candidate core network device and a switching reason.

For example, the gNB sends a handover request message to the source AMF, wherein the handover request message includes first information, the first information includes one or more second core network device identifiers and at least one of the handover reasons, and the handover request message includes a list of terminal identifiers.

In some embodiments, the terminal identifier is an NGAP UE ID.

Step 2103: Execute the switching process based on N2.

In some embodiments, the first terminal, the first access network device, the first core network device, and the second core network device perform a switching process based on N2 (also called NG), that is, migrating the context information of a specific first terminal from the first core network device to the second core network device.

For example, the first core network device executes the N2-based handover process to migrate the context of the terminal from the first core network device to the second core network device.

In some embodiments, when the first information includes an identifier of a candidate core network device, the first core network device performs an N2-based switching process with the candidate core network device as the second core network device.

In some embodiments, when the first information includes identifiers of multiple candidate core network devices, the first core network device selects a second core network device from the candidate core network devices based on the first information, and can determine the second core network device based on information such as load.

In some embodiments, the source base station and the target base station in the N2 handover process are the same node, that is, the wireless resource configuration of the terminal remains unchanged, and the air interface signaling in the N2 handover process can be omitted.

For example, the source AMF selects the indicated target AMF to migrate the context of the terminal according to the first information.

In the above embodiment, compared with the migration process that can only be based on the AMF change triggered by the base station while the base station remains unchanged, the embodiment of the present disclosure implements the context migration process in which the service access network remains unchanged and the core network changes based on the N2 switching execution process. In the scenario where the service access network is mobile, such as satellite, mobile relay, etc., it can ensure the continuity of terminal services and reduce the impact on air interface signaling.

In some embodiments, step 2101a and step 2101b may be executed separately or together, and the execution order of the two and step 2102 is not limited.

The communication method according to the embodiments of the present disclosure may include at least one of steps 2101a to 2103. For example, step 2101 may be implemented as an independent embodiment, step 2102 may be implemented as an independent embodiment, and so on, but the present invention is not limited thereto. Steps 2101a+2102, step 2101a+2101b+2102, step 2101a+2102+2103, and step 2101a+2101b+2102+2103 may be implemented as independent embodiments, but the present invention is not limited thereto.

In some embodiments, step 2101a is optional and may be omitted or replaced in different embodiments.

In some embodiments, under the first condition, the optional implementation of the terminal context migration process can refer to the optional implementation of step 2103 and other related parts of the embodiment involved in Figure 2A, which will not be repeated here.

In an embodiment of the present disclosure, the terminal context migration process is executed to implement context switching of a single terminal under a first condition where the access network device remains unchanged but the core network device changes.

In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

Figure 2B is a schematic diagram of an interaction method provided by an embodiment of the present disclosure. As shown in Figure 2B, an embodiment of the present disclosure relates to a communication method that can be executed by a communication system, such as the communication system 100 shown in Figure 1. The communication system includes a terminal, a first access network device, a first core network device, and a second core network device. The interaction method may include the following steps:

Step 2201a: The first core network device sends sixth information to the first access network device.

In some embodiments, the sixth information is included in a sixth message.

In some embodiments, the sixth information includes at least one of a core network change indication, a change reason, and a change time.

In some embodiments, the cause of the change may be the mobility of the first access network device. For example, the first access network device is deployed on a satellite and the AMF is deployed on the ground. Changes in the GW connected to the satellite cause changes in the AMF connected to the first access network device.

For example, the first access network device receives a sixth message from the first core network device, and the sixth message includes sixth information, which is used to indicate that the connected core network is about to change. The sixth information includes the reason for the change in the core network, such as a feeder link switching or a feeder link failure.

Step 2201b: The first access network device determines whether the first condition is met based on the sixth information.

In some embodiments, the first condition may be a change in the communication link between the first access network device and the ground receiving station of the first core network device. The communication link change includes an imminent change and a completed change. An imminent change indicates that a switch is required but has not yet been made, such as a hard switch, where the old link is disconnected but the new link is not yet connected. A completed change indicates that a switch has already been made, such as a soft switch, where the old link is not disconnected but the new link is already connected.

In some embodiments, the first condition may be a change in the first core network device.

In some embodiments, the first core network device changes because the first access network device is mobile. For example, the first access network device is deployed on a moving vehicle or airplane. When the first access network device moves out of the service area of the first core network device, the connected first core network device changes.

In some embodiments, the change of the first core network is caused by the configuration of the core network, for example, the load of the first core network device is high and the first core network device can no longer serve the terminal.

In some embodiments, the first condition may be a communication link switch.

In some embodiments, the first condition may be a communication link failure.

In some embodiments, the communication link can be a feeder link between a satellite and a ground gateway GW. The first access network device is deployed on the satellite, and the first core network device is deployed on the ground. The communication link is switched to a feeder link switch (feeder link switch). The feeder link switch may occur due to a change in the GW connected to the ground caused by the movement of the satellite.

In some embodiments, the communication link can be a feeder link between a satellite and a ground gateway GW, the first access network device is deployed on the satellite, the first core network device is deployed on the ground, and the communication link failure is a feeder link failure (feeder link failure), for example, the feeder link failure is caused by a poor wireless environment.

In some embodiments, the first access network device determines whether the first condition is met based on the sixth information.

In some embodiments, the first access network device determines whether the first condition is met based on the link quality between the first access network device and the first core network device.

In some embodiments, the first access network device determines whether the first condition is satisfied based on location information of the first access network device and a service area corresponding to the first core network device, wherein the location information includes ephemeris information and/or motion trajectory.

Step 2202: The first access network device sends first information to the first core network device.

In some embodiments, the first information may be carried by a first message. In other words, the first information is included in the first message, and the first message is a message for performing context migration on one or more terminals. In other words, when there are multiple terminals requiring context migration, the first access network device only needs to send one first message, and the first message is used to perform context migration on multiple terminals.

In some embodiments, the first message may reuse the RAN configuration update message (RAN Configuration Update Request).

In some embodiments, the first information is used to instruct the first core network device to migrate context information of one or more terminals from the first core network device to the second core network device, and the second core network device is the target device of the migration.

In some embodiments, the first information includes at least one of an identifier of the candidate core network device, a migration reason, a migration indication, and a first terminal identifier list, where the first terminal identifier list includes identifiers of one or more terminals.

In some embodiments, when the first message reuses an existing message, for example, a RAN configuration update message, the first message needs to include a migration indication to indicate that the message is used for migration. However, when the first message is a new message type, the migration indication may not be included.

In some embodiments, when the first information includes identifiers of multiple candidate core network devices, the first core network device needs to select one core network device from the multiple candidate core network devices as the second core network device based on the first information.

For example, the gNB sends a handover request message to the source AMF, where the handover request message includes first information, including at least one of one or more second core network device identifiers and a handover reason. The first core network device selects a target AMF to transfer the terminal context based on the first information.

Step 2203: The first core network device sends the seventh information to the second core network device.

In some embodiments, the first core network device sends the seventh information to the second core network device for a terminal context migration process.

In some embodiments, the carrier of the seventh information is not restricted, and it can be the seventh message, and the seventh message can be a create context request message (Create UE Context Request).

In some embodiments, if the terminal context migration process is for a single terminal, the seventh message sent by the first core network device to the second core network device is a request to establish a terminal context migration. In other words, if context migration is required for multiple terminals, the first core network device needs to generate a seventh message for each terminal and send it to the second core network device to establish context migration requests for different terminals.

In some embodiments, the terminal context migration process is for one or more terminals, and the seventh message sent by the first core network device to the second core network device is a terminal migration request message, wherein the seventh message includes a migration request for one or more terminal contexts.

Step 2204: The second core network device sends third information to the first access network device.

In some embodiments, the third information includes context information of one or more terminals, and the second core network device is one or more of the candidate core network devices.

In some embodiments, the carrier of the third information is not restricted, and it can be a third message or a terminal context migration request (UE Context migration request).

In some embodiments, the third information is for a terminal, that is, the third message sent by the second core network device to the first access network device is a switching request message.

In some embodiments, the third information is for multiple terminals, that is, the third message sent by the second core network device to the first access network device is a non-terminal-related NGAP message, such as an AMF configuration update message, an NG setup feedback message, or a terminal context migration request message. The third message may also be other message types, which are not limited in this disclosure. The third message includes context information of multiple terminals, and the terminal context information is updated terminal context information.

Step 2205: The first access network device sends fourth information to the second core network device.

In some embodiments, the fourth information includes at least one item of a second terminal identification list of successful migrations and a third terminal identification list of failed migrations.

Among them, the terminal identifier included in at least one of the first terminal identifier list, the second terminal identifier list, and the third terminal identifier list is a Next Generation Access Protocol NGAP terminal identifier.

In some embodiments, the carrier of the fourth information is not restricted, and it can be a fourth message. The fourth message can be a terminal context migration confirmation (UE Context migration confirm) or a terminal context migration feedback, or it can be other message types, which is not limited in this disclosure.

In some embodiments, the first access network device sends a fourth message to the second core network device, where the fourth message is used for terminal context migration confirmation.

In some embodiments, the terminal context migration confirmation is for a single terminal, that is, the fourth message sent by the first access network device to the second core network device is a handover request confirmation message.

In some embodiments, the terminal context migration confirmation is for multiple terminals, that is, the fourth message sent by the first access network device to the second core network device is a non-terminal related NGAP message, such as an AMF configuration update confirmation message, a RAN configuration update message, or a terminal context migration confirmation message, but is not limited to this, and this disclosure is not limited to this.

Step 2206: The second core network device sends the eighth information to the first core network device.

In some embodiments, the second core network device sends eighth information to the first core network device in response to the terminal context migration.

In some embodiments, the carrier of the eighth information may be an eighth message. In other words, the eighth information is included in the eighth message. The eighth message is used to respond to the terminal context migration. The eighth message may be a terminal context migration response (Create UE Context Response).

In some embodiments, the response to the terminal context migration is for a single terminal, that is, the eighth message sent by the second core network device to the first core network device establishes a terminal context feedback message.

In some embodiments, the response to the terminal context migration is for multiple terminals, that is, the eighth message sent by the second core network device to the first core network device is a terminal migration response message, wherein the eighth message includes at least one of the terminal identifier confirming successful migration and the terminal identifier confirming failed migration.

Step 2207: The first core network device releases the terminal context information.

In some embodiments, the first core network device releases the terminal context information according to the eighth information. In other words, after the terminal context information is transferred from the first core network device to the second core network device, the first core network device can release the terminal context information.

In the above embodiment, the migration process for a single terminal can reuse the N2 handover process. In the scenario where the access network equipment remains unchanged but the core network equipment is changed, the terminal's service continuity can be guaranteed and the impact on air interface signaling can be reduced. The migration process for multiple terminals can reduce unnecessary signaling overhead, improve system efficiency, and ensure service continuity for terminals within the mobile access network coverage.

The communication method involved in the embodiment of the present disclosure may include at least one of steps 2201a to 2207. For example, step 2201a can be tried as an independent embodiment, step 2202 can be implemented as an independent embodiment, and so on, but is not limited thereto. Step 2201a+2202, step 2201a+2201b+2202, step 2201a+2202+2203, step 2201a+2201b+2202+2203, step 2201a+2201b+2202+2203+2204, step 2201b+2202+2203+2204, step 2201b+2202+2203+2204+ 2205+2206, step 2201a+2201b+2202+2203+2204+2205+2206, step 2201b+2202+2203+2204+2205+2206+2207, and step 2201a+2201b+2202+2203+2204+2205+2206+2207 can be implemented as independent embodiments, but are not limited thereto.

In some embodiments, step 2201a is optional and may be omitted or replaced in different embodiments.

In some embodiments, step 2207 is optional, or step 2207 may be included in step 2206. This step may be omitted or replaced in different embodiments.

In some embodiments, under the first condition, the optional implementation method of executing the terminal context migration process can refer to the optional implementation methods of steps 2203, 2204, 2205, 2206, and 2207, and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

In an embodiment of the present disclosure, executing the terminal context migration process is used to implement context migration of a single terminal or multiple terminals under a first condition where the access network device remains unchanged but the core network device changes.

In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

Figure 2C is an interactive diagram of a communication method provided by an embodiment of the present disclosure. As shown in Figure 2C, an embodiment of the present disclosure relates to a communication method that can be executed by a communication system, such as the communication system 100 shown in Figure 1. The communication system includes a terminal, a first access network device, a second access network device, and a first core network device. The interactive method may include the following steps:

Step 2301a: The first core network device sends sixth information to the first access network device.

In some embodiments, the sixth information is included in a sixth message.

In some embodiments, the sixth information includes at least one of a core network change indication, a change reason, and a change time. The core network change indication may be that the core network is about to change or has changed, and the core network change reason may be a feeder link switch or a feeder link failure.

For example, the first access network device receives a sixth message from the first core network device, wherein the sixth message includes sixth information indicating that the connected core network is about to change or has changed, and the sixth information includes at least one of the reason and time information for the core network change.

Step 2301b: The first access network device determines whether the first condition is met.

In some embodiments, the first condition may be a change in the communication link between the first access network device and the ground receiving station of the first core network device. The communication link change includes an imminent change and a completed change. An imminent change indicates that a switch is required but has not yet been made, such as a hard switch, where the old link is disconnected but the new link is not yet connected. A completed change indicates that a switch has already been made, such as a soft switch, where the old link is not disconnected but the new link is already connected.

In some embodiments, the first condition may be a change in the first access network device.

In some embodiments, the first access network device is changed because the first access network device is mobile. For example, the first access network device is deployed on a moving vehicle or airplane. When the first access network device moves out of the service area of the first core network device and the first core network remains unchanged, the first access network device needs to be changed so that the terminal can still communicate with the first core network device, or communicate with the core network device in the same domain of the first core network device serving the terminal.

In some embodiments, the first condition may be a communication link switch.

In some embodiments, the first condition may be a communication link failure.

In some embodiments, the communication link can be a feeder link between a satellite and a ground gateway GW. The first access network device is deployed on the satellite, and the first core network device is deployed on the ground. The communication link is switched to a feeder link switch (feeder link switch). The feeder link switch may occur due to a change in the GW connected to the ground caused by the movement of the satellite.

In some embodiments, the communication link can be a feeder link between a satellite and a ground gateway GW, the first access network device is deployed on the satellite, the first core network device is deployed on the ground, and the communication link failure is a feeder link failure (feeder link failure), for example, the feeder link failure is caused by a poor wireless environment.

In some embodiments, the first access network device determines whether the first condition is met based on the sixth information.

In some embodiments, the first access network device determines whether the first condition is met based on the link quality between the first access network device and the first core network device.

In some embodiments, the first access network device determines whether the first condition is satisfied based on location information of the first access network device and a service area corresponding to the first core network device, wherein the location information includes ephemeris information and/or motion trajectory.

For example, the first access network device detects that a core network serving the terminal is about to change.

Step 2302: The candidate access network device sends fifth information to the first access network device.

In some embodiments, the fifth information includes a core network device to which the candidate access network device can connect and a validity period.

In some embodiments, the carrier of the fifth information may be a fifth message. In other words, the fifth information is included in the fifth message. The fifth message may be a RAN configuration update message (RAN Configuration Update Request), or the carrier of the fifth information is not restricted and may be other message types.

For example, the first access network device gNB1 receives fifth information from the candidate access network device gNB2, where the fifth information includes AMF domain information and corresponding validity time.

Step 2303: The first access network device determines the second access network device according to the fifth information.

In some embodiments, the first access network device determines the second access network device according to the fifth information, which may be a core network device that can be connected at the moment when the first condition is met, as a candidate access network device for the first core network device, and determines it as the second access network device. In other words, the first access network device determines the second access network device from the candidate access network devices according to the valid time of the connectable core network device and the time information in the sixth information.

For example, the first access network device determines the AMF information to which the second access network device can connect at a specific moment based on the fifth information, and based on the above information, when necessary, that is, when the AMF of the service terminal is about to change due to feeder link switching, selects the second access network device as the target access network device of the terminal.

In some embodiments, the fifth message may be an NG setup request message, an NG setup response message, an NG-RAN node configuration update message, etc., but is not limited to these.

Step 2304: The first access network device sends second information to the second access network device.

In some embodiments, the second information is used to instruct the second access network device to migrate the context information of the terminal from the first access network device to the second access network device, and the first access network device and the second access network device are located in the same core network domain.

In some embodiments, the carrier of the second information may be a second message, and the second message may be a handover request message (Handover Request) or other message types, which is not limited in this disclosure.

In some embodiments, the second message may be a handover request message sent by the first access network device to the second access network device.

In some embodiments, the second message may include a first cause value for indicating the reason for sending the second message.

In some embodiments, the first cause value is at least one of AMF change, feederlinkswitch, and feederlinkfailure.

Step 2305: Execute terminal context migration.

In some embodiments, the context migration process is a switching process.

In some embodiments, the terminal, the first access network device, the second access network device, and the first core network device perform context migration of the terminal according to the ninth information.

In the above embodiment, when the core network of the service terminal must change, the base station serving the terminal on the satellite can enable the terminal to switch to the target base station, and the target base station can be connected to the core network device of the service terminal, or can be connected to the core network device in the same domain as the core network device of the service terminal, thereby avoiding service interruption of the terminal due to feeder link switching or failure.

The communication method involved in the embodiment of the present disclosure may include at least one of steps 2301a to 2305. For example, step 2301a can be tried as an independent embodiment, step 2302 can be implemented as an independent embodiment, and so on, but is not limited thereto. Step 2301a+2302, step 2301a+2301b+2302, step 2301a+2302+2304, step 2301a+2301b+2302+2304, step 2301a+2302+2304+2305, step 2301a+2301b+2302+2304+2305, step 2301a+2302+2303, step 2301 a+2301b+2302+2303, step 2301a+2301b+2302+2303+2304, step 2301b+2302+2303+2304, step 2301b+2302+2303+2304+2305, and step 2301a+2301b+2302+2303+2304+2305 can be implemented as independent embodiments, but are not limited to this.

In some embodiments, step 2301a is optional and may be omitted or replaced in different embodiments.

In some embodiments, step 2303 is optional and may be omitted or replaced in different embodiments.

In some embodiments, under the first condition, the optional implementation of the terminal context migration process can refer to the optional implementation of step 2305 and other related parts of the embodiment involved in Figure 2C, which will not be repeated here.

In an embodiment of the present disclosure, executing the terminal context migration process is used to implement context switching of a single terminal or context migration of multiple terminals under a first condition where the core network device remains unchanged but the access network device changes.

In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

Based on the embodiment of the communication method shown in Figure 2A, Figure 3A is a flow chart of a communication method for a first access network device provided according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to a communication method, which includes:

Step 3101: Receive the sixth information sent by the first core network device.

The optional implementation of step 3101 can refer to the optional implementation of step 2101a in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

Step 3102, determine the first condition.

The optional implementation of step 3102 can refer to the optional implementation of step 2101b in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

Step 3103: Send first information to the first core network device.

The optional implementation of step 3103 can refer to the optional implementation of step 2102 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

Step 3104: Execute the switching process based on N2.

The optional implementation of step 3104 can refer to the optional implementation of step 2103 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

In some embodiments, step 3102 may be performed independently or together with step 3101. Step 3101 is optional and may be omitted or replaced in different embodiments.

Based on the embodiment of the communication method shown in Figure 2B, Figure 3B is a flow chart of a communication method for a first access network device provided according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to a communication method, which includes:

Step 3201: Receive the sixth information sent by the first core network device.

The optional implementation of step 3201 can refer to the optional implementation of step 2201a in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

Step 3202, determine the first condition.

The optional implementation of step 3202 can refer to the optional implementation of step 2201b in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

Step 3203: Send first information to the first core network device.

The optional implementation of step 3203 can refer to the optional implementation of step 2202 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

Step 3204: Receive the third information sent by the second core network device.

The optional implementation of step 3204 can refer to the optional implementation of step 2204 in Figure 2B and other related parts of the embodiment involved in Figure 2B, which will not be repeated here.

Step 3205: Send the fourth information to the second core network device.

The optional implementation of step 3205 can refer to the optional implementation of step 2205 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

In some embodiments, step 3202 may be performed independently or together with step 3201. Step 3201 is optional and may be omitted or replaced in different embodiments.

Based on the embodiment of the communication method shown in Figure 2C, Figure 3C is a flow chart of a communication method for a first access network device provided according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to a communication method, which includes:

Step 3301: Receive the sixth information sent by the first core network device.

The optional implementation of step 3301 can refer to the optional implementation of step 2301a in Figure 2C and other related parts in the embodiment involved in Figure 2C, which will not be repeated here.

Step 3302, determine the first condition.

The optional implementation of step 3302 can refer to the optional implementation of step 2301b in Figure 2C and other related parts in the embodiment involved in Figure 2C, which will not be repeated here.

Step 3303: Receive the fifth information sent by the candidate access network device.

The optional implementation of step 3303 can refer to the optional implementation of step 2302 in Figure 2C and other related parts in the embodiment involved in Figure 2C, which will not be repeated here.

Step 3304: Determine the second access network device.

The optional implementation of step 3304 can refer to the optional implementation of step 2303 in Figure 2C and other related parts in the embodiment involved in Figure 2C, which will not be repeated here.

Step 3305: Send second information to the second access network device.

The optional implementation of step 3305 can refer to the optional implementation of step 2304 in Figure 2C and other related parts in the embodiment involved in Figure 2C, which will not be repeated here.

Step 3306: Execute context migration of the terminal.

The optional implementation of step 3306 can refer to the optional implementation of step 2305 in Figure 2C and other related parts in the embodiment involved in Figure 2C, which will not be repeated here.

In some embodiments, step 3302 may be performed alone or together with step 3301. Step 3301 is optional and may be omitted or replaced in different embodiments.

FIG3D is a flow chart of a communication method for a first access network device according to an embodiment of the present disclosure. The present disclosure embodiment relates to a communication method, which includes:

Step 3401: Under a first condition, first information is sent to a first core network device and/or second information is sent to a second access network device.

Among them, the first information and/or the second information are used to execute the terminal context migration process, the terminal context migration process includes the switching process of a single terminal or the context migration process of multiple terminals, the first condition is the change of the communication link between the first access network device and the ground receiving station of the first core network device, and the first core network device is the current service device of the terminal.

The optional implementation of step 3401 can refer to the optional implementation of step 2102 in Figure 2A, step 2202 in Figure 2B, step 2302 in Figure 2C, and other related parts in the embodiments involved in Figures 2A, 2B, and 2C, which will not be repeated here.

Based on the embodiment of the communication method shown in Figure 2A, Figure 4A is a flow chart of a communication method for a first core network device provided according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to a communication method, which includes:

Step 4101: Send sixth information to the first access network device.

The optional implementation of step 4101 can refer to the optional implementation of step 2101a in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

Step 4102: Receive first information sent by the first access network device.

The optional implementation of step 4102 can refer to the optional implementation of step 2102 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

Step 4103: Execute the terminal context migration process.

The optional implementation of step 4103 can refer to the optional implementation of step 2103 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

In some embodiments, step 4101 is optional and may be omitted or replaced in different embodiments.

Based on the embodiment of the communication method shown in FIG2B , FIG4B is a flow chart of a communication method for a first core network device provided according to an embodiment of the present disclosure. As shown in FIG4B , the method includes:

Step 4201: Send sixth information to the first access network device.

The optional implementation of step 4201 can refer to the optional implementation of step 2201a in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

Step 4202: Receive first information sent by a first access network device.

The optional implementation of step 4202 can refer to the optional implementation of step 2202 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

Step 4203: Send the seventh information to the second core network device.

The optional implementation of step 4203 can refer to the optional implementation of step 2203 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

Step 4204: Receive the eighth information sent by the second core network device.

The optional implementation of step 4204 can refer to the optional implementation of step 2206 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

Step 4205: Release the terminal context information.

The optional implementation of step 4205 can refer to the optional implementation of step 2207 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

Based on the embodiment of the communication method shown in FIG2C , FIG4C is a flow chart of a communication method for a first core network device provided according to an embodiment of the present disclosure. As shown in FIG4C , the method includes:

Step 4301: Send sixth information to the first access network device.

The optional implementation of step 4301 can refer to the optional implementation of step 2301a in Figure 2C and other related parts in the embodiment involved in Figure 2C, which will not be repeated here.

Step 4302: Execute terminal context migration.

The optional implementation of step 4302 can refer to the optional implementation of step 2305 in Figure 2C and other related parts in the embodiment involved in Figure 2C, which will not be repeated here.

Figure 4D is a flow chart of a communication method for a first core network device according to an embodiment of the present disclosure. The present disclosure embodiment relates to a communication method, which includes:

Step 4401: Receive first information sent by a first access network device under a first condition.

The first information is used to indicate the execution of the terminal context migration process, which includes the switching process of a single terminal or the context migration process of multiple terminals. The first condition is that the communication link between the first access network device and the first core network device changes, and the first access network device and/or the first core network device is the current service device of the terminal.

The optional implementation of step 4401 can refer to the optional implementation of step 2102 in Figure 2A, step 2202 in Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

Based on the embodiment of the communication method shown in FIG2C , FIG5A is a flow chart of a communication method for a second access network device provided according to an embodiment of the present disclosure. The embodiment of the present disclosure relates to a communication method, and the method includes:

Step 5101: Send fifth information to the first access network device.

The optional implementation of step 5101 can refer to the optional implementation of step 2302 in Figure 2C and other related parts in the embodiment involved in Figure 2C, which will not be repeated here.

Step 5102: Receive second information sent by the first access network device.

The optional implementation of step 5102 can refer to the optional implementation of step 2304 in Figure 2C and other related parts in the embodiment involved in Figure 2C, which will not be repeated here.

Step 5103: Execute the terminal context migration process.

The optional implementation of step 5103 can refer to the optional implementation of step 2305 in Figure 2C and other related parts in the embodiment involved in Figure 2C, which will not be repeated here.

Figure 5B is a flow chart of a communication method for a second access network device according to an embodiment of the present disclosure. The present disclosure embodiment relates to a communication method, which includes:

Step 5201: Receive second information sent by the first access network device under the first condition.

Among them, the second information is used to indicate the execution of the terminal context migration process, the terminal context migration process includes the switching process of a single terminal or the context migration process of multiple terminals, the first condition is that the communication link between the first access network device and the first core network device changes, and the first access network device and/or the first core network device is the current service device of the terminal.

The optional implementation of step 5201 can refer to the optional implementation of step 2304 in Figure 2C and other related parts in the embodiment involved in Figure 2C, which will not be repeated here.

In some embodiments, the above method may include the methods involved in the embodiments of the above-mentioned first access network device, second access network device, first core network device, second core network device, terminal, etc., which will not be repeated here.

In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

In summary, the communication method proposed in the present application is used in a scenario where the base station is deployed on a satellite or mobile relay. When the first condition is met, the first access network device sends the first information to the first core network device and/or sends the second information to the second access network device. The first information and/or the second information is used to indicate the execution of the terminal context migration process. The terminal context migration process includes the context switching of one terminal or the context migration process of multiple terminals, thereby avoiding the interruption of the mobile terminal's service when the base station remains unchanged but the core network changes or the core network remains unchanged but the base station changes, thereby ensuring the service continuity of the terminal.

Figure 6 is an interactive diagram of a communication method provided according to an embodiment of the present disclosure. The present disclosure embodiment relates to a communication method, the method comprising:

Step 6101: The first access network device sends first information to the first core network device under a first condition.

The first information is used to execute the terminal context migration process, which includes the switching process of a single terminal or the context migration process of multiple terminals. The first condition is that the communication link between the first access network device and the first core network device changes, and the first access network device and/or the first core network device is the current service device of the terminal.

The optional implementation of step 6101 can refer to the optional implementation of step 2102 in Figure 2A, step 2202 in Figure 2B, and other related parts in the embodiments involved in Figures 2A and 2B, which will not be repeated here.

Step 6102: The first access network device sends second information to the second access network device under the first condition.

The second information is used to indicate the execution of the terminal context migration process, which includes the switching process of a single terminal or the context migration process of multiple terminals. The first condition is that the communication link between the first access network device and the first core network device changes, and the first access network device and/or the first core network device is the current service device of the terminal.

The optional implementation of step 6102 can refer to the optional implementation of step 2304 in Figure 2C and other related parts in the embodiment involved in Figure 2C, which will not be repeated here.

In some embodiments, the communication method includes at least one of step 6101 and step 6102. Step 6101 can be performed alone, step 6102 can be performed alone, or both steps 6101 and 6102 can be performed together. Step 6101 is used to implement, under a first condition, a first access network device sending first information to a first core network device, and the first core network device and the second core network device performing a terminal context migration process. Step 6102 is used to implement, under the first condition, a first access network device sending second information to a second access network device, and the first access network device and the second access network device performing a terminal context migration process.

The following is a detailed introduction to the communication method provided by the present disclosure:

FIG7A is an interactive schematic diagram of a context switching process for a specific terminal when a core network device changes but an access network device remains unchanged according to a communication method provided by an embodiment of the present disclosure.

As shown in FIG7A , the communication method includes the following steps:

Step 7101a. The first access network device receives a sixth message from the first core network device AMF, wherein the sixth message includes sixth information for indicating that the connected core network is about to change, and the sixth information includes at least one of the reason for the core network change (for example, feeder link switch) and time information.

The optional implementation of step 7101a can be found in the optional implementation of step 2101a of Figure 2A, step 3101 of Figure 3A, step 4101 of Figure 4A, and other related parts in the embodiments involved in Figures 2A, 3A, and 4A, which will not be repeated here.

Step 7101b. The first access network device gNB1 determines that the AMF serving the UE is about to change, where the AMF is about to change due to the mobility of the first access network device. For example, the access network device is deployed on a satellite, and the GW connected to the satellite changes, resulting in a change in the AMF connected to the first access network device.

The first access network device can also monitor on its own that the core network serving the UE is about to change.

The optional implementation of step 7101b can refer to the optional implementation of step 2101b in Figure 2A, step 3102 in Figure 3A, and other related parts in the embodiments involved in Figures 2A and 3A, which will not be repeated here.

Step 7102: The gNB sends a handover request message to the source AMF, where the handover request message includes first information, and the first information includes at least one of the following information: one or more second core network device identifiers and a handover reason.

The first core network device migrates the context of the terminal according to the indicated second core network device or selects a second core network device from multiple second core network devices based on the first information.

The optional implementation of step 7102 can be found in the optional implementation of step 2102 in Figure 2A, step 3103 in Figure 3A, step 4102 in Figure 4A, and other related parts in the embodiments involved in Figures 2A, 3A, and 4A, which will not be repeated here.

Step 7103: The first core network device executes the N2-based switching process to migrate the context of the terminal from the first core network device to the second core network device.

Optional implementations of step 7103 can be found in step 2103 of FIG. 2A , optional implementations of step 4103 of FIG. 4A , and other related parts in the embodiments involved in FIG. 2A and FIG. 4A , which will not be described in detail here.

Optionally, step 7101b may be performed alone or together with step 7101a. In some embodiments, step 7101a is optional and may be omitted or replaced in different embodiments.

FIG7B is an interactive diagram of a context migration process for one or more terminals when a core network device changes but an access network device remains unchanged according to a communication method provided by an embodiment of the present disclosure.

As shown in FIG7B , the communication method includes the following steps:

Step 7201a. The first access network device receives a sixth message from the first core network device AMF, wherein the sixth message includes sixth information for indicating that the connected core network is about to change, and the sixth information includes at least one of the reason for the core network change (for example, feeder link switch) and time information.

The optional implementation of step 7201a can be found in the optional implementation of step 2201b of Figure 2B, step 3201 of Figure 3B, step 4201 of Figure 4B, and other related parts in the embodiments involved in Figures 2B, 3B, and 4B, which will not be repeated here.

Step 7201b: The first access network device gNB1 determines that the AMF serving the UE is about to change, where the AMF is about to change due to the mobility of the first access network device. For example, the access network device is deployed on a satellite, and the GW connected to the satellite changes, resulting in a change in the AMF connected to the first access network device.

The first access network device can also monitor on its own that the core network serving the UE is about to change.

The optional implementation of step 7201b can refer to the optional implementation of step 2201b in Figure 2B, step 3202 in Figure 3B, and other related parts in the embodiments involved in Figures 2B and 3B, which will not be repeated here.

Step 7202: The first access network device gNB sends a first message to the first core network device source AMF, such as a RAN configuration update message, wherein the first message includes first information, and the first information includes information for indicating terminal context migration.

The first information includes at least one of the following information: a migration indication, a migration reason, one or more second core network identifiers, and a list of migrated terminal identifiers.

The optional implementation of step 7202 can refer to the optional implementation of step 2202 in Figure 2B, step 3203 in Figure 3B, step 4202 in Figure 4B, and other related parts in the embodiments involved in Figures 2B, 3B, and 4B, which will not be repeated here.

Step 7203: The first core network device sends a seventh message to the second core network device according to the first information. The seventh message is used in the terminal context migration process.

The terminal context migration process is for each terminal, that is, the seventh message sent by the first core network device to the second core network device is a terminal context establishment request.

The terminal context migration process is for one or more terminals, that is, the seventh message sent by the first core network device to the second core network device is a terminal migration request message, wherein the seventh message includes migration requests for one or more UE contexts.

The optional implementation of step 7203 can refer to the optional implementation of step 2203 in Figure 2B, step 4203 in Figure 4B, and other related parts in the embodiments involved in Figures 2B and 4B, which will not be repeated here.

Step 7204: The second core network device sends a third message to the first access network device, wherein the third message is used for a terminal context migration request.

The terminal context migration request is for each terminal, that is, the third message sent by the second core network device to the first access network device is a switching request message.

The terminal context migration request is for one or more terminals, that is, the third message sent by the second core network device to the first access network device is a non-UE-related NGAP message (for example, an AMF configuration update message, an NG establishment feedback message, or a UE context migration request message, but not limited thereto). The third message includes context information of one or more terminals. The terminal context information is updated terminal context information.

The optional implementation of step 7204 can refer to the optional implementation of step 2204 in Figure 2B and other related parts in the embodiment involved in Figure 2B, which will not be repeated here.

Step 7205: The first access network device sends a fourth message to the second core network device, where the fourth message is used to confirm the terminal context migration.

The terminal context migration confirmation is for each UE, that is, the fourth message sent by the second core network device to the first access network device is a switching request confirmation message.

The terminal context migration confirmation is for one or more UEs, that is, the fourth message sent by the second core network device to the first access network device is a non-UE related NGAP message (for example, an AMF configuration update confirmation message, a RAN configuration update message, or a UE context migration confirmation message, but not limited thereto). The fourth message includes at least one of the UE identifier of the successful migration and the UE identifier of the failed migration.

The optional implementation of step 7205 can refer to the optional implementation of step 2205 in Figure 2B, step 3205 in Figure 3B, and other related parts in the embodiments involved in Figures 2B and 3B, which will not be repeated here.

Step 7206: The second core network device sends an eighth message to the first core network device. The eighth message is used to respond to the terminal context migration.

The response to the terminal context migration is for each UE, that is, the eighth message sent by the second core network device to the first core network device establishes a UE context feedback message.

The response to the terminal context migration is for one or more UEs, that is, the eighth message sent by the second core network device to the first core network device is a UE migration response message, wherein the eighth message includes at least one of the UE identifier confirming successful migration and the UE identifier confirming failed migration.

The optional implementation of step 7206 can refer to the optional implementation of step 2206 in Figure 2B, step 4204 in Figure 4B, and other related parts in the embodiments involved in Figures 2B and 4B, which will not be repeated here.

Optionally, step 7201b may be performed alone or together with step 7201a. In some embodiments, step 7201a is optional and may be omitted or replaced in different embodiments.

Step 7207: The first core network device releases the UE context according to the eighth message.

The optional implementation of step 7207 can refer to the optional implementation of step 2207 in Figure 2B, step 4205 in Figure 4B, and other related parts in the embodiments involved in Figures 2B and 4B, which will not be repeated here.

FIG7C is an interactive diagram of a context migration process for a terminal when the access network device changes but the core network device remains unchanged according to the communication method provided by an embodiment of the present disclosure.

As shown in FIG7C , the communication method includes the following steps:

Step 7301a. The first access network device receives a sixth message from the first core network device AMF, wherein the sixth message includes sixth information for indicating that the connected core network is about to change, and the sixth information includes at least one of the reason for the core network change (for example, feeder link switch) and time information.

The optional implementation of step 7301a can refer to the optional implementation of step 2301a in Figure 2C, step 4301 in Figure 4C, and other related parts in the embodiments involved in Figures 2C and 4C, which will not be repeated here.

Step 7301b: The first access network device gNB1 determines that the AMF serving the UE is about to change, where the AMF is about to change due to the mobility of the first access network device. For example, the access network device is deployed on a satellite, and the GW connected to the satellite changes, resulting in a change in the AMF connected to the first access network device.

The first access network device can also monitor on its own that the core network serving the UE is about to change.

The optional implementation of step 7301b can refer to the optional implementation of step 2301b in Figure 2C, step 3302 in Figure 3C, and other related parts in the embodiments involved in Figures 2C and 3C, which will not be repeated here.

Step 7302: A first access network device (e.g., gNB1) receives a fifth message from a second access network device (e.g., gNB2, which may be on a satellite or on the ground). The fifth message includes AMF domain information and corresponding validity period. The first access network device may determine, based on the fifth message, the AMF information to which the second access network device can connect at a specific time, and, based on the fifth message, select the second access network device as the target access network device for the UE when needed (e.g., because the AMF serving the UE is about to change due to a feeder link switch).

The fifth message can be a NG setup request message, a NG setup response message, a NG-RAN node configuration update message, etc., but is not limited to these.

The optional implementation of step 7302 can be found in step 2302 of Figure 2C, step 3303 of Figure 3C, the optional implementation of step 5101 of Figure 5A, and other related parts in the embodiments involved in Figures 2C, 3C, and 5A, which will not be repeated here.

Step 7303: The first access network device (e.g., sourcegNB) sends a switching request message to the second access network device (e.g., targetgNB).

In some embodiments, the first access network device determines the second access network device as the second access network device in the switching process based on the information received from step 7302.

The optional implementation of step 7303 can be found in step 2303, step 2304 in Figure 2C, step 3304, step 3305 in Figure 3C, the optional implementation of step 5102 in Figure 5A, and other related parts in the embodiments involved in Figures 2C, 3C, and 5A, which will not be repeated here.

Step 7304: The second access network device performs the UE switching process according to the switching request message to ensure that the AMF serving the UE remains unchanged or the UE's service is not interrupted.

The optional implementation of step 7304 can be found in step 2305 of Figure 2C, step 3306 of Figure 3C, the optional implementation of step 5103 of Figure 5A, and other related parts in the embodiments involved in Figures 2C, 3C, and 5A, which will not be repeated here.

In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

It should be understood that the division of the various units or modules in the above device is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. In addition, the units or modules in the device can be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and instructions are stored in the memory. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device may be implemented in the form of hardware circuits, and the functions of some or all of the units or modules may be implemented by designing the hardware circuits. The above-mentioned hardware circuits may be understood as one or more processors. For example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), and the functions of some or all of the above-mentioned units or modules may be implemented by designing the logical relationship between the components in the circuit. For another example, in another implementation, the above-mentioned hardware circuit may be implemented by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it may include a large number of logic gate circuits, and the connection relationship between the logic gate circuits may be configured through a configuration file, thereby implementing the functions of some or all of the above-mentioned units or modules. All units or modules of the above-mentioned devices may be implemented entirely by the processor calling software, or entirely by hardware circuits, or partially by the processor calling software, and the remaining part by hardware circuits.

In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor may be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor may implement certain functions through the logical relationship of a hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document to implement the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as ASIC, such as the Neural Network Processing Unit (NPU), the Tensor Processing Unit (TPU), the Deep Learning Processing Unit (DPU), etc.

FIG8A is a schematic diagram of the structure of a first access network device according to an embodiment of the present disclosure. As shown in FIG8A , the first access network device 8100 includes a transceiver module 8101 .

In some embodiments, the transceiver module is used to send first information to the first core network device and/or send second information to the second access network device under a first condition, wherein the first information and/or the second information are used to indicate the execution of a terminal context migration process, the terminal context migration process includes a switching process of a single terminal or a context migration process of multiple terminals, the first condition is a change in the communication link between the first access network device and the first core network device, and the first core network device is the current service device of the terminal. Optionally, the transceiver module is used to execute at least one of the communication steps such as receiving and/or sending executed by the first access network device in any of the above methods (for example, step 2101a, step 2102, step 2201a, step 2202, step 2204, step 2205, step 2301a, step 2302, step 2304, but not limited to this), which will not be repeated here.

In some embodiments, the first access network device also includes a processing module for executing at least one of the other steps (for example, step 2101b, step 2103, step 2201b, step 2301b, step 2303, step 2305, but not limited to these) performed by the first access network device in any of the above methods, which will not be repeated here.

In some embodiments, the transceiver module may include a transmitting module and/or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

FIG8B is a schematic diagram of the structure of a second access network device according to an embodiment of the present disclosure. As shown in FIG8B , the second access network device 8200 includes a transceiver module 8201 .

In some embodiments, the transceiver module is used to receive second information sent by the first access network device under a first condition, wherein the second information is used to indicate the execution of a terminal context migration process, the terminal context migration process including a switching process for a single terminal or a context migration process for multiple terminals, the first condition being a change in the communication link between the first access network device and the first core network device, and the first access network device and/or the first core network device being the current service device of the terminal. Optionally, the transceiver module 8201 is used to execute at least one of the communication steps such as receiving and/or sending (for example, step 2302, step 2304, but not limited thereto) performed by the second access network device in any of the above methods, which will not be repeated here.

In some embodiments, the second access network device further includes a processing module for executing other steps (such as step 2305, but not limited thereto) performed by the second access network device in any of the above methods, which will not be repeated here.

In some embodiments, the transceiver module may include a transmitting module and/or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

FIG8C is a schematic diagram of the structure of a core network device according to an embodiment of the present disclosure. As shown in FIG8C , the core network device 8300 includes a transceiver module 8301 .

In some embodiments, the transceiver module is used to receive first information sent by the first access network device under a first condition, wherein the first information is used to indicate the execution of a terminal context migration process, the terminal context migration process includes a switching process of a single terminal or a context migration process of multiple terminals, the first condition is a change in the communication link between the first access network device and the first core network device, and the first access network device and/or the first core network device is the current service device of the terminal. Optionally, the transceiver module 8301 is used to execute at least one of the communication steps such as receiving and/or sending (for example, step 2101a, step 2102, step 2201a, step 2202, step 2203, step 2204, step 2205, step 2206, step 2301a, but not limited to these) performed by the first core network device and/or the second core network device in any of the above methods, which will not be repeated here.

In some embodiments, the core network device also includes a processing module for executing other steps (for example, step 2103, step 2207, step 2305, but not limited to) performed by the first core network device and/or the second core network device in any of the above methods, which are not repeated here.

In some embodiments, the transceiver module may include a transmitting module and/or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

Figure 9A is a schematic diagram of the structure of a communication device 9100 provided according to an embodiment of the present disclosure. Communication device 9100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user device, etc.), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. Communication device 9100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

As shown in Figure 9A, the communication device 9100 includes one or more processors 9101. The processor 9101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process the communication protocol and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. Optionally, the communication device 9100 is used to perform any of the above methods. Optionally, one or more processors 9101 are used to call instructions to enable the communication device 9100 to perform any of the above methods.

In some embodiments, the communication device 9100 further includes one or more transceivers 9102. When the communication device 9100 includes one or more transceivers 9102, the transceiver 9102 performs at least one of the communication steps of sending and/or receiving in the above method (e.g., steps 2101a, 2102, 2201a, 2202, 2203, 2204, 2205, 2206, 2301a, 2302, and 2304, but not limited thereto), and the processor 9101 performs at least one of the other steps (e.g., steps 2101b, 2103, 2201b, 2207, 2301b, 2303, and 2305, but not limited thereto). In alternative embodiments, the transceiver may include a receiver and/or a transmitter, and the receiver and transmitter may be separate or integrated. Optionally, terms such as transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface can be replaced with each other, terms such as transmitter, transmitting unit, transmitter, and transmitting circuit can be replaced with each other, and terms such as receiver, receiving unit, receiver, and receiving circuit can be replaced with each other.

In some embodiments, the communication device 9100 further includes one or more memories 9103 for storing data. Alternatively, all or part of the memories 9103 may be located outside the communication device 9100. In an alternative embodiment, the communication device 9100 may include one or more interfaces. Circuit 9104. Optionally, interface circuit 9104 is connected to memory 9102. Interface circuit 9104 can be used to receive data from memory 9102 or other devices, and can be used to send data to memory 9102 or other devices. For example, interface circuit 9104 can read data stored in memory 9102 and send the data to processor 9101.

In some embodiments, the processor 9101 may store a computer program 9105. The computer program 9105 runs on the processor 9101, enabling the communication device 9000 to perform the method described in the above method embodiment. The computer program 9105 may be fixed in the processor 9101. In this case, the processor 9101 may be implemented by hardware.

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

9B is a schematic diagram of the structure of a chip 9200 according to an embodiment of the present disclosure. If the communication device 9100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 9200 shown in FIG9B , but the present disclosure is not limited thereto.

The chip 9200 includes one or more processors 9201. The chip 9200 is configured to execute any of the above methods.

In some embodiments, chip 9200 further includes one or more interface circuits 9202. Terms such as interface circuit, interface, and transceiver pins may be used interchangeably. In some embodiments, chip 9200 further includes one or more memories 9203 for storing data. Alternatively, all or part of memory 9203 may be located external to chip 9200. Optionally, interface circuit 9202 is connected to memory 9203 and may be used to receive data from memory 9203 or other devices, or may be used to send data to memory 9203 or other devices. For example, interface circuit 9202 may read data stored in memory 9203 and send the data to processor 9201.

In some embodiments, the interface circuit 9202 performs at least one of the communication steps (e.g., steps 2101a, 2102, 2201a, 2202, 2203, 2204, 2205, 2206, 2301a, 2302, and 2304) in the above-described method. For example, the interface circuit 9202 performing the communication steps (e.g., steps 2101a, 2102, 2201a, 2202, 2203, 2204, 2205, 2206, 2301a, 2302, and 2304) in the above-described method means that the interface circuit 9202 performs data exchange between the processor 9201, the chip 9200, the memory 9203, or the transceiver device. In some embodiments, the processor 9201 performs at least one of the other steps (e.g., steps 2101b, 2103, 2201b, 2207, 2301b, 2303, and 2305, but not limited thereto).

The modules and/or devices described in various embodiments, such as virtual devices, physical devices, and chips, can be arbitrarily combined or separated according to circumstances. Optionally, some or all steps can also be performed collaboratively by multiple modules and/or devices, which is not limited here.

The present disclosure also proposes a storage medium having instructions stored thereon, which, when executed on the communication device 9100, causes the communication device 9100 to execute any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a temporary storage medium.

The present disclosure also provides a program product, which, when executed by the communication device 9100, enables the communication device 9100 to perform any of the above methods. Optionally, the program product is a computer program product.

The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims (36)

A communication method, characterized in that the method is performed by a first access network device, the first access network device being the current service device of a terminal, and the method comprises: Under a first condition, first information is sent to a first core network device and/or second information is sent to a second access network device, wherein the first information and/or the second information is used to indicate the execution of a terminal context migration process, the terminal context migration process includes a switching process of a single terminal or a context migration process of multiple terminals, the first condition is a change in the communication link between the first access network device and the first core network device, and the first core network device is the current service device of the terminal. The method according to claim 1, wherein the first information is used to instruct the first core network device to migrate the context information of the terminal from the first core network device to a second core network device, and the second core network device is the target device of the migration; and/or The second information is used to instruct the second access network device to migrate the context information of the terminal from the first access network device to the second access network device, and the first access network device and the second access network device are located in the same core network domain. The method according to claim 1 or 2 is characterized in that the first information is included in a first message, the first message is a switching request message for a specific terminal, and the first information includes at least one of an identification of a candidate core network device and a switching reason. The method according to claim 1 or 2 is characterized in that the first information is included in a first message, the first message is a message for performing context migration on one or more terminals, the first information includes the identification of the candidate core network device, the migration reason, the migration indication, and at least one item in the first terminal identification list, and the first terminal identification list includes the identification of the one or more terminals. The method according to claim 4, further comprising: Receive third information sent by the second core network device, where the third information includes context information of the one or more terminals, and the second core network device is one or more of the candidate core network devices. The method according to claim 5, further comprising: Fourth information is sent to the second core network device, where the fourth information includes at least one item from the second terminal identification list of successful migration and the third terminal identification list of failed migration. The method according to any one of claims 4 to 6 is characterized in that the terminal identifier included in at least one item in the first terminal identifier list, the second terminal identifier list, and the third terminal identifier list is a Next Generation Access Control Protocol NGAP terminal identifier. The method according to claim 1 or 2, characterized in that the method further comprises: receiving fifth information from the candidate access network device; The second access network device is determined from the candidate access network devices according to the fifth information. The method according to claim 8, wherein the fifth information includes a core network device to which the candidate access network device can be connected and a valid time. The determining, based on the fifth information, the second access network device from the candidate access network devices includes: According to the fifth information, a core network device that can be connected when the first condition is met is a candidate access network device for the first core network device and is determined as the second access network device. The method according to any one of claims 1 to 9, further comprising: Determine whether the first condition is met. The method according to claim 10, wherein determining whether the first condition is satisfied comprises at least one of the following: Determining whether the first condition is met based on the link quality between the first access network device and the first core network device; Based on the location information of the first access network device and the service area corresponding to the first core network device, determine whether the first condition is met. The method according to claim 10, wherein determining whether the first condition is satisfied comprises: receiving sixth information sent by the first core network device, where the sixth information includes at least one of a core network change indication, a change reason, and a change time; Determine whether the first condition is met based on the sixth information. The method according to any one of claims 1-12 is characterized in that the first access network device has mobility. The method according to any one of claims 1 to 13, wherein the first condition includes at least one of the following: The first core network equipment is changed; said communication link switching; The communication link has failed. A communication method, characterized in that the method is performed by a first core network device, and the method includes: Receive first information sent by a first access network device under a first condition, wherein the first information is used to indicate the execution of a terminal context migration process, the terminal context migration process includes a switching process of a single terminal or a context migration process of multiple terminals, the first condition is a change in the communication link between the first access network device and the first core network device, and the first access network device and/or the first core network device is the current service device of the terminal. The method according to claim 15 is characterized in that the first information is used to instruct the first core network device to migrate the context information of the terminal from the first core network device to the second core network device, and the second core network device is the target device of the migration. The method according to claim 15 or 16 is characterized in that the first information is included in a first message, the first message is a switching request message for a specific terminal, and the first information includes at least one of an identification of a candidate core network device and a switching reason. The method according to claim 15 or 16 is characterized in that the first information is included in a first message, the first message is a message for performing context migration on one or more terminals, the first information includes an identifier of a candidate core network device, a migration reason, a migration indication, and at least one item in a first terminal identifier list, and the first terminal identifier list includes the identifiers of the one or more terminals. The method according to claim 18 is characterized in that the terminal identifiers included in the first terminal identifier list are Next Generation Access Control Protocol NGAP terminal identifiers. The method according to any one of claims 15 to 19, further comprising: Send sixth information to the first access network device, where the sixth information includes at least one of a core network change indication, a change reason, and a change time, and the sixth information is used to assist the first access network device in determining whether the first condition is met. The method according to any one of claims 15-20 is characterized in that the first access network device has mobility. The method according to any one of claims 15 to 21, wherein the first condition includes at least one of the following: The first core network equipment is changed; said communication link switching; The communication link has failed. A communication method, characterized in that the method is performed by a second access network device, and the method includes: Receive second information sent by a first access network device under a first condition, wherein the second information is used to indicate the execution of a terminal context migration process, the terminal context migration process includes a switching process of a single terminal or a context migration process of multiple terminals, the first condition is a change in the communication link between the first access network device and the first core network device, and the first access network device and/or the first core network device is the current service device of the terminal. The method according to claim 23, characterized in that The second information is used to instruct the second access network device to migrate the context information of the terminal from the first access network device to the second access network device, and the first access network device and the second access network device are located in the same core network domain. The method according to claim 23 or 24, characterized in that the method further comprises: Send fifth information to the first access network device, where the fifth information includes a core network device to which the second access network device can connect and a validity period. The method according to any one of claims 23-25 is characterized in that the second access network device is: an access network device to which the core network device that can be connected when the first condition is met is the first core network device. The method according to any one of claims 23-26 is characterized in that the first access network device has mobility. The method according to any one of claims 23 to 27, wherein the first condition includes at least one of the following: The first core network equipment is changed; said communication link switching; The communication link has failed. An access network device, characterized in that the access network device is a current service device of a terminal, comprising: A transceiver module is used to send first information to a first core network device and/or send second information to a second access network device under a first condition, wherein the first information and/or the second information are used to indicate the execution of a terminal context migration process, and the terminal context migration process includes a switching process of a single terminal or a context migration process of multiple terminals. The first condition is a change in the communication link between the first access network device and the first core network device, and the first core network device is the current service device of the terminal. A core network device, comprising: A transceiver module is used to receive first information sent by a first access network device under a first condition, wherein the first information is used to indicate the execution of a terminal context migration process, the terminal context migration process includes a switching process of a single terminal or a context migration process of multiple terminals, the first condition is a change in the communication link between the first access network device and the first core network device, and the first access network device and/or the first core network device is the current service device of the terminal. An access network device, comprising: A transceiver module is used to receive second information sent by a first access network device under a first condition, wherein the second information is used to indicate the execution of a terminal context migration process, the terminal context migration process includes a switching process of a single terminal or a context migration process of multiple terminals, the first condition is a change in the communication link between the first access network device and the first core network device, and the first access network device and/or the first core network device is the current service device of the terminal. A communication device, comprising: a transceiver; a memory; and a processor, connected to the transceiver and the memory, respectively, configured to control the wireless signal reception and transmission of the transceiver by executing computer-executable instructions on the memory, and capable of implementing the method described in any one of claims 1 to 28. A communication system comprising: terminal, A first access network device, configured to perform the method according to any one of claims 1 to 14; The first core network device is configured to execute the method according to any one of claims 15 to 22. The communication system according to claim 33, further comprising: A second access network device, configured to perform the method according to any one of claims 23 to 28; or, Second core network equipment. A computer storage medium, wherein the computer storage medium stores computer-executable instructions; after the computer-executable instructions are executed by a processor, the method according to any one of claims 128 can be implemented. A computer program product comprising a computer program, wherein the computer program is executed to implement the method according to any one of claims 1 to 28.