Communication management method and apparatus, terminal, and network-side device

Abstract

The present application relates to the technical field of communications, and discloses a communication management method and apparatus, a terminal, and a network-side device. The communication management method in embodiments of the present application comprises: a first device sends to a second device at least one of a first request message and a second request message. The first request message is used for requesting the second device to suspend transmissions over an interface, and the second request message is used for requesting the second device to suspend a terminal context. The first device is an access network device, and the second device is a core network device; or the first device is a core network device, and the second device is an access network device.

Description

Communication management method, device, terminal and network side equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese Patent Application No. 202410049637.3 filed in China on January 12, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to a communication management method, apparatus, terminal and network-side equipment. Background Art

[0004] With the development of communication technology, in non-terrestrial networks (NTN) communication systems. Base stations and core network equipment (or core network network elements) are fixedly deployed on the ground, so the interface management of network elements only supports the establishment and reset processes. Among them, the reset process is only initiated in the event of a failure. In other cases, it is believed that the interface channel between the base station and the core network equipment can be used for information transmission. However, when the base station is in a mobile state, for example, after the base station is on a satellite, as the satellite moves, the base station and the core network equipment cannot always be connected, and thus normal information transmission cannot always be maintained. In this way, the reset process will be triggered by mistake, resulting in low management efficiency. Summary of the Invention

[0005] The embodiments of the present application provide a communication management method, apparatus, terminal, and network-side equipment, which can solve the problem of low management efficiency.

[0006] In a first aspect, a communication management method is provided, comprising:

[0007] The first device sends at least one of a first request message and a second request message to the second device;

[0008] The first request message is used to request the second device to suspend interface transmission;

[0009] The second request message is used to request the second device to suspend the terminal context;

[0010] The first device is an access network device, and the second device is a core network device; or the first device is a core network device, and the second device is an access network device.

[0011] In a second aspect, a communication management method is provided, comprising:

[0012] The second device receives at least one of the first request message and the second request message from the first device;

[0013] The first request message is used to request the second device to suspend interface transmission;

[0014] The second request message is used to request the second device to suspend the terminal context;

[0015] The first device is an access network device, and the second device is a core network device; or the first device is a core network device, and the second device is an access network device.

[0016] In a third aspect, a communication management device is provided, comprising:

[0017] A first sending module, configured for the first device to send at least one of a first request message and a second request message to the second device;

[0018] The first request message is used to request the second device to suspend interface transmission;

[0019] The second request message is used to request the second device to suspend the terminal context;

[0020] The first device is an access network device, and the second device is a core network device; or the first device is a core network device, and the second device is an access network device.

[0021] In a fourth aspect, a communication management device is provided, comprising:

[0022] A second receiving module, configured for the second device to receive at least one of the first request message and the second request message from the first device;

[0023] The first request message is used to request the second device to suspend interface transmission;

[0024] The second request message is used to request the second device to suspend the terminal context;

[0025] The first device is an access network device, and the second device is a core network device; or the first device is a core network device, and the second device is an access network device.

[0026] In a fifth aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect or the second aspect are implemented.

[0027] In a sixth aspect, a network side device is provided, including a processor and a communication interface, wherein:

[0028] When the network-side device is a first device, the communication interface is used to send at least one of a first request message and a second request message to the second device;

[0029] The first request message is used to request the second device to suspend interface transmission;

[0030] The second request message is used to request the second device to suspend the terminal context;

[0031] The first device is an access network device, and the second device is a core network device; or the first device is a core network device, and the second device is an access network device.

[0032] Alternatively, when the network-side device is a second device, the communication interface is used to receive at least one of a first request message and a second request message from the first device;

[0033] The first request message is used to request the second device to suspend interface transmission;

[0034] The second request message is used to request the second device to suspend the terminal context;

[0035] The first device is an access network device, and the second device is a core network device; or the first device is a core network device, and the second device is an access network device.

[0036] In the seventh aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.

[0037] In an eighth aspect, a wireless communication system is provided, comprising: a terminal and a network side device, wherein the terminal can be used to execute the steps of the method described in the first aspect, and the network side device can be used to execute the steps of the method described in the second aspect.

[0038] In the ninth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method described in the first aspect, or to implement the method described in the second aspect.

[0039] In the tenth aspect, a computer program / program product is provided, which is stored in a storage medium and executed by at least one processor to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0040] In an embodiment of the present application, at least one of a first request message and a second request message is sent from a first device to a second device; wherein the first request message is used to request the second device to suspend interface transmission; and the second request message is used to request the second device to suspend terminal context; wherein the first device is an access network device and the second device is a core network device; or, the first device is a core network device and the second device is an access network device. Thus, by requesting at least one of suspending interface transmission and suspending terminal context via a request message, a fault-triggered reset process can be avoided when a feeder link is disconnected due to satellite movement. Therefore, the embodiment of the present application improves system management efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] FIG1 is a block diagram of a wireless communication system to which embodiments of the present application may be applied;

[0042] FIG2 is a block diagram of a wireless communication system applicable to embodiments of the present application;

[0043] FIG3 is a flow chart of a communication management method according to an embodiment of the present application;

[0044] FIG4a is a second flow chart of a communication management method provided in an embodiment of the present application;

[0045] FIG4b is a third flow chart of a communication management method provided in an embodiment of the present application;

[0046] FIG5 is a fourth flow chart of a communication management method provided in an embodiment of the present application;

[0047] FIG6 is a fifth flow chart of a communication management method provided in an embodiment of the present application;

[0048] 7 is a schematic structural diagram of a communication management device provided in an embodiment of the present application;

[0049] FIG8 is a schematic structural diagram of another communication management device provided in an embodiment of the present application;

[0050] FIG9 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0051] FIG10 is a schematic structural diagram of a network-side device provided in an embodiment of the present application;

[0052] FIG11 is a schematic structural diagram of another network-side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0053] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0054] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0055] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. thGeneration, 6G) communication system.

[0056] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AP) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0057] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (MME), access mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application service discovery function (EASDF), unified data management (UDM), unified data repository (UDR), home user server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BSF), application function ( It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0058] For ease of understanding, some of the contents involved in the embodiments of this application are described below:

[0059] 1. Non-terrestrial networks (NTN).

[0060] A typical NTN deployment scenario is as follows. As shown in Figure 2, the link between the terminal and the satellite is called the service link, and the link between the satellite and the ground gateway is called the feeder link, also known as the feeder link. In some scenarios (such as low-Earth orbit satellites (LEO)), due to satellite movement, service link and / or feeder link switching may occur. For service link switching, the serving satellite for all user equipment (UE) in the cell needs to be switched from one satellite to another. For feeder link switching, a satellite needs to be switched from one ground gateway to another.

[0061] There are two types of NTN communication systems: those based on transparent payloads and those based on regenerative payloads. Currently, only NTN systems based on transparent payloads are considered. In this deployment environment, terminals, base stations, and core network equipment are all deployed on the ground. Communication data between terminals and network-side equipment is relayed via satellites in the air. In this system, satellites only forward data between base stations and terminals and do not decode or process this data. For NTN systems based on regenerative payloads, satellites have some or all base station functions and can decode and process uplink or downlink data. For example, if a satellite has all the functions of an access network, the access network equipment can be referred to as on-board access network equipment or on-board base station equipment. In layman's terms, this can also be referred to as a base station on-board a satellite. In this case, the access network's central unit (CU) functions are referred to as the on-board access network's central unit (CU), and the access network's distributed unit (DU) functions are referred to as the on-board access network's distributed unit (DU). If a satellite has the access network's central unit (CU) functions, the access network's central unit (CU) can be referred to as the on-board central unit (CU) of the access network equipment. In layman's terms, this can also be referred to as the onboard central unit (CU). If the satellite has the access network's distributed unit (DU) functionality, the access network's distributed unit (DU) can be referred to as the onboard distributed unit (DU) of the access network equipment. In layman's terms, this can also be referred to as the onboard distributed unit (DU).

[0062] 2. S1 or NG interface management.

[0063] In the LTE communication system, the interface between the base station and the core network equipment is the S1 interface, while in the NR communication system, the interface between the base station and the core network equipment is the NG interface. The S1 interface and the NG interface are divided into the control plane interface S1-C or NG-C and the user plane interface S1-U or NG-U. Among them, the user plane interface S1-U or NG-U is connected to the core network user plane network element Serving Gate Way (S-GW) or user plane function entity (UPF) for transmitting service data. The control plane interface S1-C or NG-CS1 is connected to the core network control plane network element MME or AMF for transmitting control plane information. The management of the S1 interface is similar to that of the NG interface. The management process of the NG interface will be introduced later using NR as an example. The current mechanism supports the establishment process and reset process of the NG interface.

[0064] NG setup procedure: This procedure is initiated by the base station. If the AMF agrees to the establishment, it replies with an NG setup response message. If the AMF cannot receive the establishment request, it replies with an NG setup failure message.

[0065] NG reset procedure: This procedure can be initiated by the base station or by the core network device AMF.

[0066] Currently, the S1 or NG reset process is typically used in special scenarios. For example, if a base station node fails and some or all reference information is lost, the RAN will initiate the NG reset process. Similarly, if a core network device (AMF) fails, the AMF will initiate the NG reset process.

[0067] Since the base station and core network equipment are fixedly deployed on the ground in the communication system, the interface management of the network element only supports the establishment and reset processes. Among them, the reset process is only initiated in the event of a failure. In other cases, it is assumed that the interface channel between the base station and the core network equipment can be used for information transmission. However, after the base station is launched, as the satellite moves, the base station and the core network equipment cannot always be connected, and thus normal information transmission cannot always be maintained. Therefore, the relevant mechanism will lead to unnecessary information transmission, which is not conducive to system management efficiency. To this end, the communication management method of the present application is proposed.

[0068] The communication management method provided in the embodiments of the present application is described in detail below through some embodiments and their application scenarios in combination with the accompanying drawings.

[0069] It should be noted that the scenarios corresponding to the various embodiments of the present application may be scenarios where network-side devices, or some hardware or functions in network-side devices can be moved, for example, network-side devices, or some hardware or functions in network-side devices are located on satellites, or on other movable devices (such as various mobile vehicles such as cars, airplanes, drones, and ships).

[0070] 3 , an embodiment of the present application provides a communication management method. As shown in FIG3 , the communication management method includes:

[0071] Step 301: The first device sends at least one of a first request message and a second request message to the second device;

[0072] The first request message is used to request the second device to suspend interface transmission;

[0073] The second request message is used to request the second device to suspend the terminal context;

[0074] The first device is an access network device, and the second device is a core network device; or the first device is a core network device, and the second device is an access network device.

[0075] In the embodiment of the present application, the above-mentioned first request message and second request message can be carried in one message or one signaling, or can be carried in different messages or different signalings, and no further limitation is made here.

[0076] Optionally, the access network device in each embodiment of the present application may be an onboard device, a device related to a satellite, or a device that is in a mobile state or supports mobility (ie, has mobility capability).

[0077] Optionally, when the first device sends the first request message and / or the second request message to the second device, the first device also starts a timer. When the timer times out, if the first device receives a response message from the second device (see subsequent embodiments for details), the second device defaults to suspending interface transmission and / or suspending terminal context. It should also be noted that the first device can start a timer for the first request message and the second request message, or start timers separately.

[0078] Optionally, suspending interface transmission can be understood as suspending interface transmission functions, for example, suspending some or all interface transmission functions. The interface can be understood as an S1 interface or an NG interface. By suspending interface transmission, interface transmission for some or all terminals associated with the interface can be suspended. It should be understood that in some embodiments, interface transmission for different terminals can be suspended via multiple first request messages.

[0079] Optionally, suspending the terminal context may also suspend the data transmission of the terminal, which can avoid erroneous triggering of the reset process and thus improve the management efficiency of the system.

[0080] Optionally, in some embodiments, the access network device includes at least one of the following:

[0081] Satellite-related network elements;

[0082] Store-and-forward type devices;

[0083] The satellite-related network elements include any one of the following: an on-board base station; an on-board central unit CU of a base station; or a CU of an on-board base station.

[0084] Optionally, in some embodiments, the core network device is an onboard core network device. In other embodiments, the core network device may be a terrestrial device, such as deployed on the ground.

[0085] Optionally, the first request message may be understood as an interface suspension request message, and the second request message may be understood as a terminal context suspension request message.

[0086] In an embodiment of the present application, at least one of a first request message and a second request message is sent from a first device to a second device; wherein the first request message is used to request the second device to suspend interface transmission; and the second request message is used to request the second device to suspend terminal context; wherein the first device is an access network device and the second device is a core network device; or, the first device is a core network device and the second device is an access network device. Thus, by requesting at least one of suspending interface transmission and suspending terminal context via a request message, a fault-triggered reset process can be avoided when a feeder link is disconnected due to satellite movement. Therefore, the embodiment of the present application improves system management efficiency.

[0087] Optionally, in some embodiments, the first device sending at least one of the first request message and the second request message to the second device includes:

[0088] In a case where a feeder link between the first device and the second device will be unavailable, the first device sends at least one of a first request message and a second request message to the second device.

[0089] In the embodiment of the present application, the feeder link can be understood or replaced by a feeder line, wherein the feeder link will be unavailable can be understood or replaced by the feeder link is about to be unavailable, the feeder link will be disconnected, the feeder link is about to be disconnected, the feeder link will switch or the feeder link is about to switch, etc.

[0090] Optionally, the determination of the time point at which the feeder link between the first device and the second device will become unavailable can be set according to actual needs. For example, in some embodiments, it can be defined that when the satellite moves to a specific position, it is assumed or considered that the feeder link is unavailable. In one implementation method, the time point at which the feeder link is unavailable can be determined based on information such as the trajectory and speed of the satellite's movement, and then based on this time point, it can be considered that the feeder link will be unavailable at a preset time before this time point. In another implementation method, the current position information of the satellite can be obtained, and it is assumed that the feeder link will be unavailable when the satellite moves to a certain position before the specific position.

[0091] It should be noted that the service link in each embodiment of the present application may be a satellite service link or a (mobile) service link, that is, at least one network element or device in the link is in a mobile state or has mobility capabilities. The feeder link in each embodiment of the present application may be a satellite feeder link or a (mobile) feeder link, that is, at least one network element or device in the link is in a mobile state or has mobility capabilities.

[0092] Optionally, in some embodiments, the first request message includes at least one of the following:

[0093] Suspension reason indication information. Exemplarily, the suspension reason indication information is used to indicate that the feeder link is unavailable or will be unavailable;

[0094] Suspend type indication information, where the suspension type indication information is used to indicate the transmission function of the suspended part of the interface or the transmission function of the suspended part of the interface;

[0095] Suspend time information.

[0096] Optionally, the suspension cause indication information is used to indicate that the feeder link is unavailable, which can be understood as follows: the suspension cause indication information is used to indicate that the feeder link is disconnected or switched. The suspension cause indication information is used to indicate that the feeder link will be unavailable, which can be understood as follows: the suspension cause indication information is used to indicate that the feeder link is about to be unavailable, is about to be disconnected, will be disconnected, will be switched (gateway), or is about to be switched (gateway), will be disconnected from the ground gateway (or ground network), or is about to be disconnected from the ground gateway (or ground network), etc.

[0097] Optionally, for the function of suspending all interface transmissions, the suspension type indication information may be understood as an indication to suspend all NG interface transmissions between the first device and the second device.

[0098] Optionally, with respect to the transmission function of the suspended part interface, the suspension type indication information can be understood as indicating the transmission of relevant information of the suspended part terminal. For example, in some embodiments, when the suspension type indication information indicates the transmission function of the suspended part interface, the first request message also includes interface information associated with the terminal.

[0099] Optionally, in some embodiments, the suspension time information includes at least one of the following:

[0100] Suspend start time information;

[0101] Suspension duration information;

[0102] Suspension end time information;

[0103] Time information when the interface resumes transmission.

[0104] Optionally, the suspension start time information may be used to indicate the start time of suspending the interface transmission. The suspension start time information may indicate the time when the first device initiates the first request message, or indicate a certain time in the future.

[0105] Optionally, the suspension duration information is used to indicate the duration of the suspended interface and can be used in conjunction with the suspension start time information to determine the time when the interface is restored. It can also be used to indicate the minimum or maximum suspension duration. Optionally, the suspension duration information can also indicate a suspension time period, such as 12:00 to 12:30. In other embodiments, the suspension duration information can indicate a suspension duration, such as 30 minutes.

[0106] Optionally, the time information for the interface to resume transmission can indicate a certain time in the future, and the time information for the interface to resume transmission can be used to indicate the time when the feeder link between the base station and the core network device resumes connection. For example, the time information for the interface to resume transmission can be determined based on ephemeris information.

[0107] Optionally, in some embodiments, the method further comprises:

[0108] The first device automatically resumes at least one of interface transmission and terminal context based on the suspension time information.

[0109] In an embodiment of the present application, the first device and the second device can automatically resume at least one of interface transmission and terminal context based on the suspension time information, thereby reducing signaling interaction. It should be understood that the suspension behavior corresponds to the resumption behavior, that is, when the interface transmission is suspended, the interface transmission can be automatically resumed based on the suspension time information; when the terminal context is suspended, the terminal context can be automatically resumed based on the suspension time information.

[0110] Optionally, in some embodiments, at least one of the interface transmission and the terminal context may be automatically resumed at the end time point corresponding to the suspension end time information.

[0111] Optionally, in some embodiments, the suspension end time point may be determined based on the suspension start time information and the suspension duration information, and at least one of the interface transmission and the terminal context may be automatically resumed at the time point.

[0112] Optionally, in some embodiments, a recovery time point may be determined based on time information of the interface recovery transmission, and at least one of the interface transmission and the terminal context may be automatically recovered at the time point.

[0113] Optionally, in some embodiments, the second request message includes at least one of the following:

[0114] Suspension reason indication information. Exemplarily, the suspension reason indication information is used to indicate that the feeder link is unavailable or will be unavailable;

[0115] Interface information associated with the terminal.

[0116] In the embodiment of the present application, the suspension reason indication information in the above-mentioned first request message is the same as the suspension reason indication information in the second request message. The specific explanation can refer to the first request message and will not be repeated here.

[0117] Optionally, in some embodiments, the method further comprises:

[0118] receiving, by the first device, at least one of a first response message and a second response message from the second device;

[0119] The first response message is used to indicate that the second device agrees to suspend interface transmission, and the second response message is used to indicate that the second device agrees to suspend terminal context.

[0120] In this embodiment of the present application, the response message corresponds to the request message. That is, after the first device sends a first request message to the second device, the second device can send a first response message to the first device based on the first request message. Similarly, after the first device sends a second request message to the second device, the second device can send a second response message to the first device based on the second request message. Because the second device sends a response message to the first device in this embodiment of the present application, it can ensure that the first and second devices maintain a consistent understanding of the behavior of the suspended interface and suspended terminal context, thereby avoiding subsequent incorrect transmission behavior.

[0121] Optionally, the first response message may be understood as an interface suspension response message, and the second response message may be understood as a terminal context suspension response message.

[0122] Optionally, in some embodiments, in the case of suspended interface transmission, the transmission of target data between the first device and the second device is suspended.

[0123] Optionally, in some embodiments, upon receiving the first request message, the second device may send a first response message to the first device, the first response message indicating that the second device agrees to suspend the interface transfer. In other embodiments, upon receiving the first request message, the second device may send a rejection message to the first device, the rejection message indicating that the second device refuses to suspend the interface transfer. It should be noted that the first response message and the rejection message may be the same message, carrying an acceptance or rejection information field. In other embodiments, upon receiving the first request message, the second device does not send any message to the first device, thereby rejecting the interface transfer by default. In some embodiments, upon agreeing to suspend the interface transfer, the second device stores the context of the first device or suspends the context of the first device. In some embodiments, upon receiving the first request message, the second device stores the context of the first device or suspends the context of the first device. This scenario may be applicable to scenarios where the second device does not refuse to suspend the interface transfer.

[0124] Optionally, in some embodiments, upon receiving the first response message, the first device suspends the context of the second device, or the first device stores the context of the second device. Due to limited storage capacity of onboard devices, in other embodiments, upon receiving the first response message, the first device may delete all or part of the context of the first device (e.g., retaining only the AMF name).

[0125] Optionally, in some embodiments, when the first device receives the second response message, the first device suspends the context of the terminal.

[0126] Optionally, in some embodiments, the target data includes at least one of first data and second data;

[0127] The first data includes at least one of the following: an access network device configuration update message; an uplink non-access layer NAS message of the terminal; a path switching request message; an uplink service data packet of the terminal;

[0128] The second data includes at least one of the following: a core network device configuration update message; a downlink NAS message of the terminal; a paging message; and a downlink service data packet of the terminal.

[0129] In the embodiment of the present application, the transmission of target data between the first device and the second device being suspended can be understood to include at least one of the following:

[0130] The first device does not send the target data to the second device, that is, the first device suspends the sending of the target data;

[0131] The second device does not send the target data to the first device, that is, the second device suspends the sending of the target data.

[0132] It should be understood that in the embodiment of the present application, the specific execution subject of the suspension behavior is related to the type of target data. For example, the base station can suspend the transmission of the first data, and the core network device can suspend the transmission of the second data.

[0133] Optionally, in some embodiments, the method further comprises:

[0134] When the feeder link is available, the first device sends at least one of a third request message and a fourth request message to the second device;

[0135] Wherein, the third request message is used to request to resume interface transmission;

[0136] The fourth request message is used to request the second device to restore the terminal context.

[0137] In the embodiment of the present application, the feeder link available can be understood as feeder link switching, feeder link connection, or feeder link recovery.

[0138] Optionally, the third request message may be understood as an interface recovery request message, and the fourth request message may be understood as a terminal context recovery request message.

[0139] Optionally, in some embodiments, when the second device receives the third request message, the second device restores, activates, reactivates, or reuses the context of the first device. In other embodiments, when the second device receives the third request message, if the second device cannot or does not agree to resume interface transmission, the second device sends a failure message to the first device. The failure message indicates a failure to resume interface transmission.

[0140] Optionally, in some embodiments, when the second device receives the fourth request message, the second device restores, activates, reactivates, or reuses the terminal context. In other embodiments, when the second device receives the fourth request message, if the second device cannot or does not agree to restore the terminal context, the second device sends a failure message to the first device. The failure message indicates a failure in restoring the terminal context.

[0141] It should be understood that in the embodiments of the present application, the third and fourth request messages correspond to the first and second request messages, respectively. For example, after the first device sends the first request message to the second device, the second device may also send the third request message to the second device; and after the first device sends the second request message to the second device, the second device may also send the fourth request message to the second device.

[0142] It should be noted that in some embodiments, at least one of the third request message and the fourth request message may be sent when the feeder link is determined to be available. Alternatively, at least one of the third request message and the fourth request message may be sent a preset time after the feeder link is determined to be available, thereby ensuring the stability of the feeder link connection.

[0143] Optionally, in some embodiments, the third request message includes at least one of the following:

[0144] First indication information, where the first indication information is used to instruct to resume interface transmission;

[0145] Restoration time information, where the restoration time information is used to indicate the time for resuming interface transmission;

[0146] Restoration reason indication information, where the restoration reason indication information is used to indicate that the feeder link is available or the feeder link has been switched;

[0147] Restoration type indication information, where the restoration type indication information is used to indicate restoration of the transmission function of part of the interfaces or restoration of the transmission function of part of the interfaces.

[0148] Optionally, in some embodiments, when the restoration type indication information indicates restoration of transmission functions of some interfaces, the third request further includes interface information associated with the terminal.

[0149] Optionally, in some embodiments, the fourth request includes at least one of the following:

[0150] Restoration reason indication information, where the restoration reason indication information is used to indicate that the feeder link has been restored or the feeder link has been switched;

[0151] Interface information associated with the terminal.

[0152] Optionally, in some embodiments, the interface information includes at least one of the following:

[0153] The interface identifier of the terminal in the core network device;

[0154] The interface identifier of the terminal in the access network device.

[0155] Among them, the interface identifier of the core network device may include an AMF UE NGAP ID or an MME UE S1AP ID; the interface identifier of the terminal in the access network device may include a RAN UE NGAP ID or an eNB UE S1AP ID.

[0156] Optionally, in some embodiments, the method further comprises:

[0157] The first device receives at least one of a third response message and a fourth response message from the second device:

[0158] The third response is used to indicate agreement to resume interface transmission, and the fourth response is used to indicate agreement to resume the terminal context.

[0159] Optionally, the third response message may be understood as an interface recovery response message, and the fourth response message may be understood as a terminal context recovery response message.

[0160] Optionally, in some embodiments, the third response message may further carry interface information associated with the terminal.

[0161] Optionally, in some embodiments, when the first device receives the third response message, the first device restores, activates, reactivates, or reuses the context of the second device. In other embodiments, when the first device receives a restore interface transmission failure message from the second device, the first device deletes the stored context of the first device.

[0162] Optionally, in some embodiments, when the first device receives the second response message, the first device restores, activates, reactivates, or reuses the terminal context. In other embodiments, when the first device receives a message from the second device indicating a failure to restore the terminal context, the first device deletes the stored terminal context.

[0163] In order to better understand the present application, some specific examples are provided below for illustration.

[0164] Example 1: Suspend and resume process of S1 interface or NG interface.

[0165] In step 11, in a scenario where a feeder link is switching (e.g., the feeder link is disconnected or unavailable), the network node suspends interface transmission. Suspending interface transmission by the network node includes: the base station sending an interface suspension request message to a core network element. The interface suspension request message is used to request the core network element to suspend interface transmission.

[0166] Optionally, the base station type includes any one of the following:

[0167] Satellite-related network elements;

[0168] Store-and-forward type devices;

[0169] The satellite-related network elements include any one of the following: an on-board base station; an on-board central unit CU of a base station; or a CU of an on-board base station.

[0170] Optionally, the type of the interface includes at least one of the following:

[0171] S1 interface, including at least one of S1-C and S1-U. It should be noted that this use case applies to the connection to the LTE core network, such as the interface between an LTE base station eNB and an LTE core network element;

[0172] NG interface, including at least one of NG-C and NG-U; it should be noted that this use case is applicable to the situation of connecting to the 5G core network, such as the interface between the NR base station gNB and the 5GC core network element.

[0173] Optionally, the core network element includes one or more of the following:

[0174] Core network control plane network element, such as AMF or MME; it should be noted that when the base station is connected to the LTE core network, the core network control plane network element is MME, and when the base station is connected to the 5G core network, the core network control plane network element is AMF;

[0175] Core network user plane network element, such as UPF or S-GW; it should be noted that when the base station is connected to the 5G core network, the core network control plane network element is S-GW, and when the base station is connected to the 5G core network, the core network control plane network element is UPF.

[0176] It should be noted that if the onboard base station is connected to multiple types of core networks at the same time, such as the LTE core network and the 5G core network at the same time, the base station can send the interface suspension request message to the LTE and 5G core network elements respectively.

[0177] The interface suspension request message includes at least one of the following: suspension reason indication information; suspension type indication information; interface suspension time information.

[0178] Optionally, the suspension reason indication information is used to indicate that a feeder link is switched (or a feeder link is disconnected), or is used to indicate that a feeder link is about to be switched (or a feeder link is about to be disconnected).

[0179] For example, in a hard feeder link handover scenario, the base station may initiate an NG suspend process before the feeder link handover occurs.

[0180] For example, in a soft feeder link handover scenario, the base station may initiate an NG suspend process before or when the feeder link handover occurs.

[0181] Optionally, the specific time for the base station to initiate the interface (S1 interface or NG interface) suspension process may depend on the base station implementation.

[0182] Optionally, the suspension type information includes at least one of the following:

[0183] Suspending all interface transmission functions; illustratively, the suspension type information is used to indicate the suspension of all NG interface transmissions between the base station and the core network element;

[0184] Suspend part of the interface transmission function; in this case, the suspension type indication information can be understood as suspending the relevant information transmission of part of the terminal. In this case, illustratively, the interface suspension request message also carries the interface information associated with the terminal.

[0185] Optionally, the interface information associated with the terminal includes the following information: an interface identifier of the terminal in a core network element; an interface identifier of the terminal in a base station.

[0186] It should be noted that the interface suspension request message may include interface information associated with one or more terminals, and is used to suspend interface transmission of one or more terminals. Exemplarily, the interface suspension request message may include NG interface information associated with one or more terminals.

[0187] Optionally, in a feeder link switching scenario, the base station may request to suspend interface transmission of some or all terminals associated with the interface through the interface suspension request message. The base station may send multiple interface suspension request messages to suspend interface transmission of multiple different terminals.

[0188] It should be noted that, when the interface suspend request message does not carry the suspend type indication information, it is a default request to suspend all interface transmission functions.

[0189] Optionally, the interface suspension time information includes at least one of the following:

[0190] Suspension start time information, where the suspension start time information is used to indicate the start time of suspending the interface transmission. The suspension start time information may indicate the time when the base station initiates the interface suspension request message, or be used to indicate a future time;

[0191] Suspension duration information, which is used to indicate the duration of the suspension interface transmission and can be used in conjunction with the suspension start time information;

[0192] Suspension end time information, the suspension end time information is used to indicate the end time of the suspended interface transmission, and the suspension end time information is used to indicate a future time;

[0193] Time information for resuming transmission on the interface. The time information for resuming transmission on the interface may indicate a future time. The time information for resuming transmission on the interface may be used to indicate the time when the feeder link between the base station and the core network element is restored. The base station may determine the time information for resuming transmission on the interface based on ephemeris information.

[0194] Step 12: In the scenario of feeder link switching (e.g., disconnection), the base station receives an interface suspension response message sent by the core network element, wherein the interface suspension response message is used to indicate to the base station that the core network element agrees to suspend interface transmission.

[0195] Additionally, when the interface suspension request message carries interface suspension time information, the interface suspension response message is further used to instruct the base station and the core network element to agree to automatically resume interface transmission at the time indicated by the interface suspension time information. The interface suspension response message may also carry interface information associated with the terminal.

[0196] It should be noted that the interface suspension response message may include interface information associated with one or more terminals, for agreeing to suspend interface transmission of one or more terminals. Exemplarily, the interface suspension response message may include NG interface information associated with one or more terminals.

[0197] Optionally, in a feeder link switching scenario, the core network element may indicate to the base station, through the interface suspension response message, that it agrees to suspend interface transmission for some or all terminals associated with the interface. The core network element may send multiple interface suspension response messages to indicate that the base station agrees to suspend interface transmission for multiple different terminals.

[0198] It should be noted that, when the interface suspension response message does not carry the interface information associated with the terminal, it is assumed that all interface transmission functions are suspended.

[0199] Optionally, when transmission on an interface (such as an S1 or NG interface) is suspended, the network node may perform at least one of the following actions:

[0200] When the interface transmission is suspended, the base station does not send uplink data to the core network element associated with the interface. The uplink data includes at least one of the following: a base station configuration update message, such as an eNB configuration update message or a RAN configuration update message; a terminal UL NAS message; a path switch request message; or a terminal UL service data packet.

[0201] When interface transmission is suspended, the core network element does not send downlink data to the base station associated with the interface. The downlink data includes at least one of the following: a core network element configuration update message, such as an MME configuration update message or an AMF configuration update message; a terminal's DL NAS message; a paging message, such as a paging message; or a terminal's DL service data packet.

[0202] Step 13: When the feeder link is switched, such as when the feeder link is restored or the feeder link is available, the network node resumes interface transmission. The network node resumes interface transmission including at least one of the following:

[0203] The base station sends an interface recovery request message to the core network element (as shown in Figure 4a);

[0204] Based on the time information of interface transmission resumption, the base station automatically resumes interface transmission at the time indicated by the interface transmission resumption time information (as shown in FIG4b ). The core network element associated with the interface also automatically resumes interface transmission at the time indicated by the interface transmission resumption time information.

[0205] Wherein, in the case where the base station sends an interface recovery request message to the core network element, the interface recovery request message may additionally include at least one of the following: recovery reason indication information; recovery type indication information.

[0206] Exemplarily, the function of restoring all interface transmissions is used to indicate the restoration of all NG interface transmissions between the base station and the core network element.

[0207] Exemplarily, the restoration type indication information can be understood as resuming transmission of relevant information of some terminals. In this case, exemplarily, the interface restoration request message also carries interface information associated with the terminal.

[0208] It should be noted that the interface suspension response message may include interface information associated with one or more terminals, for agreeing to resume interface transmission of one or more terminals. Exemplarily, the interface recovery response message may include NG interface information associated with one or more terminals.

[0209] Optionally, in a feeder link switching scenario, the base station may request the core network to restore interface transmission for some or all terminals associated with the interface through the interface recovery request message. The base station may send multiple interface recovery request messages to instruct the core network element to request restoration of interface transmission for multiple different terminals.

[0210] It should be noted that, when the interface restoration request message does not carry the interface information associated with the terminal, it is a default request to restore all interface transmission functions.

[0211] Step 14: In the feeder link handover (e.g., restoration) scenario, the base station receives an interface restoration response message sent by the core network element. The interface restoration response message indicates that the base station agrees to restore interface transmission. The interface restoration response message may also carry additional information about the interface associated with the terminal.

[0212] It should be noted that the interface recovery response message may include interface information associated with one or more terminals, used to indicate that the base station core network element agrees to restore interface transmission of one or more terminals. Exemplarily, the interface recovery response message may include NG interface information associated with one or more terminals.

[0213] Optionally, in a feeder link switching scenario, the core network element may indicate to the base station, through the interface recovery response message, that it agrees to resume interface transmission for some or all terminals associated with the interface. The core network element may send multiple interface recovery response messages to indicate that the base station agrees to suspend interface transmission for multiple different terminals.

[0214] It should be noted that, when the interface recovery response message does not carry the interface information associated with the terminal, it is assumed that all interface transmission functions are restored.

[0215] It should be noted that in this embodiment, the aforementioned base station behavior can also be performed by a core network element, and uplink core network element behavior can also be performed by a base station. The core network element initiating the interface suspension and recovery process presupposes that the core network element can obtain satellite ephemeris information and, based on this ephemeris information, can determine the disconnection and recovery time of the feeder link with the satellite base station. This ephemeris information can be configured for the core network element based on Operation Administration and Maintenance (OAM).

[0216] Embodiment 2: UE context suspension and recovery process.

[0217] In step 21, in a feeder link handover scenario (e.g., a feeder link is disconnected or unavailable), the network node suspends the terminal context. Suspending the terminal context by the network node includes: the base station sends a terminal context suspension request message to the core network element (as shown in FIG5 ). The terminal context suspension request message is used to request the core network element to suspend the terminal context.

[0218] Among them, the definitions of base stations, core network elements and interfaces can refer to the above embodiments and will not be repeated here.

[0219] Optionally, the UE context suspend request message includes at least one of the following:

[0220] Suspension reason indication information, where the suspension reason indication information is used to indicate that the feeder link is switched (or the feeder link is disconnected), or is used to indicate that the feeder link is about to be switched (or the feeder link is about to be disconnected);

[0221] Interface information associated with the terminal.

[0222] Step 22: In the scenario of feeder link switching (e.g., disconnection), the base station receives a terminal context suspension response message sent by the core network element, wherein the terminal context suspension response message is used to indicate that the base station core network element agrees to suspend the terminal context.

[0223] Step 23: In the scenario of feeder link switching (such as restoration), the base station sends a terminal context restoration request message to the core network element. The terminal context restoration request message is used to request the core network element to restore the terminal context.

[0224] Optionally, the terminal context recovery request message may include at least one of the following:

[0225] Restoration reason indication information, where the restoration reason indication information is used to indicate that the feeder link is switched (or the feeder link is restored), or is used to indicate that the feeder link has been switched (or the feeder link has been restored);

[0226] Interface information associated with the terminal.

[0227] Step 24: In the scenario of feeder link switching (such as restoration), the base station receives a terminal context restoration response message sent by the core network element, wherein the terminal context restoration response message is used to indicate that the base station core network element agrees to restore the context of the terminal.

[0228] It should be noted that the aforementioned base station actions can also be performed by core network elements, and uplink core network element actions can also be performed by base stations. The core network element's initiation of the interface suspension and recovery process presupposes that the core network element has access to the satellite's ephemeris information and can use this information to determine the disconnection and restoration time of the feeder link with the satellite's base station. This ephemeris information can be provided to the core network element based on OAM configuration.

[0229] 6 , an embodiment of the present application further provides a communication management method. As shown in FIG6 , the communication management method includes:

[0230] Step 601: The second device receives at least one of a first request message and a second request message from the first device;

[0231] The first request message is used to request the second device to suspend interface transmission;

[0232] The second request message is used to request the second device to suspend the terminal context;

[0233] The first device is an access network device, and the second device is a core network device; or the first device is a core network device, and the second device is an access network device.

[0234] Optionally, the second device receiving at least one of the first request message and the second request message from the first device includes:

[0235] In a case where a feeder link between the first device and the second device will be unavailable, the second device receives at least one of a first request message and a second request message from the first device.

[0236] Optionally, the first request message includes at least one of the following:

[0237] Suspension reason indication information, where the suspension reason indication information is used to indicate that the feeder link is unavailable or will be unavailable;

[0238] Suspend type indication information, where the suspension type indication information is used to indicate the transmission function of the suspended part of the interface or the transmission function of the suspended part of the interface;

[0239] Suspend time information.

[0240] Optionally, when the suspension type indication information indicates suspending the transmission function of some interfaces, the first request message further includes interface information associated with the terminal.

[0241] Optionally, the suspension time information includes at least one of the following:

[0242] Suspend start time information;

[0243] Suspension duration information;

[0244] Suspension end time information;

[0245] Time information when the interface resumes transmission.

[0246] Optionally, the method further includes:

[0247] The second device automatically resumes at least one of interface transmission and terminal context based on the suspension time information.

[0248] Optionally, the second request message includes at least one of the following:

[0249] Suspension reason indication information, where the suspension reason indication information is used to indicate that the feeder link is unavailable or will be unavailable;

[0250] Interface information associated with the terminal.

[0251] Optionally, the method further includes:

[0252] The second device sends at least one of a first response message and a second response message to the first device;

[0253] The first response message is used to indicate that the second device agrees to suspend interface transmission;

[0254] The second response message is used to indicate that the second device agrees to suspend the terminal context.

[0255] Optionally, in the case of suspended interface transmission, the transmission of target data between the first device and the second device is suspended.

[0256] Optionally, the target data includes at least one of first data and second data;

[0257] The first data includes at least one of the following: an access network device configuration update message; an uplink non-access layer NAS message of the terminal; a path switching request message; an uplink service data packet of the terminal;

[0258] The second data includes at least one of the following: a core network device configuration update message; a downlink NAS message of the terminal; a paging message; and a downlink service data packet of the terminal.

[0259] Optionally, the method further includes:

[0260] In a case where the feeder link is available, the second device receives at least one of a third request message and a fourth request message from the first device;

[0261] Wherein, the third request message is used to request to resume interface transmission;

[0262] The fourth request message is used to request the second device to restore the terminal context.

[0263] Optionally, the third request message includes at least one of the following:

[0264] First indication information, where the first indication information is used to instruct to resume interface transmission;

[0265] Restoration time information, where the restoration time information is used to indicate the time for resuming interface transmission;

[0266] Restoration reason indication information, where the restoration reason indication information is used to indicate that the feeder link is available or the feeder link has been switched;

[0267] Restoration type indication information, where the restoration type indication information is used to indicate restoration of the transmission function of part of the interfaces or restoration of the transmission function of part of the interfaces.

[0268] Optionally, when the restoration type indication information indicates restoration of transmission functions of some interfaces, the third request further includes interface information associated with the terminal.

[0269] Optionally, the fourth request includes at least one of the following:

[0270] Restoration reason indication information, where the restoration reason indication information is used to indicate that the feeder link has been restored or the feeder link has been switched;

[0271] Interface information associated with the terminal.

[0272] Optionally, the interface information includes at least one of the following:

[0273] The interface identifier of the terminal in the core network device;

[0274] The interface identifier of the terminal on the access network device.

[0275] Optionally, the method further includes:

[0276] The second device sends at least one of a third response message and a fourth response message to the first device:

[0277] The third response is used to indicate consent to resume interface transmission;

[0278] The fourth response is used to indicate consent to restore the terminal context.

[0279] Optionally, the access network device includes at least one of the following:

[0280] Satellite-related network elements;

[0281] Store-and-forward type devices;

[0282] The satellite-related network elements include any one of the following: an on-board base station; an on-board central unit CU of a base station; or a CU of an on-board base station.

[0283] Optionally, the core network device is an onboard core network device.

[0284] The communication management method provided in the embodiment of the present application can be executed by a communication management device. In the embodiment of the present application, the communication management device provided in the embodiment of the present application is described by taking the communication management device executing the communication management method as an example.

[0285] 7 , an embodiment of the present application further provides a communication management device. As shown in FIG7 , the communication management device 700 includes:

[0286] A first sending module 701 is configured for the first device to send at least one of a first request message and a second request message to the second device;

[0287] The first request message is used to request the second device to suspend interface transmission;

[0288] The second request message is used to request the second device to suspend the terminal context;

[0289] The first device is an access network device, and the second device is a core network device; or the first device is a core network device, and the second device is an access network device.

[0290] Optionally, the first sending module 701 is specifically configured to send at least one of a first request message and a second request message to the second device when a feeder link between the first device and the second device is unavailable.

[0291] Optionally, the first request message includes at least one of the following:

[0292] Suspension reason indication information, where the suspension reason indication information is used to indicate that the feeder link is unavailable or will be unavailable;

[0293] Suspend type indication information, where the suspension type indication information is used to indicate the transmission function of the suspended part of the interface or the transmission function of the suspended part of the interface;

[0294] Suspend time information.

[0295] Optionally, when the suspension type indication information indicates suspending the transmission function of some interfaces, the first request message further includes interface information associated with the terminal.

[0296] Optionally, the suspension time information includes at least one of the following:

[0297] Suspend start time information;

[0298] Suspension duration information;

[0299] Suspension end time information;

[0300] Time information when the interface resumes transmission.

[0301] Optionally, the communication management device 700 further includes:

[0302] The first recovery module is configured to automatically recover at least one of interface transmission and terminal context based on the suspension time information.

[0303] Optionally, the second request message includes at least one of the following:

[0304] Suspension reason indication information, where the suspension reason indication information is used to indicate that the feeder link is unavailable or will be unavailable;

[0305] Interface information associated with the terminal.

[0306] Optionally, the communication management device 700 further includes:

[0307] A first receiving module, configured to receive at least one of a first response message and a second response message from the second device;

[0308] The first response message is used to indicate that the second device agrees to suspend interface transmission;

[0309] The second response message is used to indicate that the second device agrees to suspend the terminal context.

[0310] Optionally, in the case of suspended interface transmission, the transmission of target data between the first device and the second device is suspended.

[0311] Optionally, the target data includes at least one of first data and second data;

[0312] The first data includes at least one of the following: an access network device configuration update message; an uplink non-access layer NAS message of the terminal; a path switching request message; an uplink service data packet of the terminal;

[0313] The second data includes at least one of the following: a core network device configuration update message; a downlink NAS message of the terminal; a paging message; and a downlink service data packet of the terminal.

[0314] Optionally, the first sending module 701 is further configured to: when the feeder link is available, send at least one of a third request message and a fourth request message to the second device;

[0315] Wherein, the third request message is used to request to resume interface transmission;

[0316] The fourth request message is used to request the second device to restore the terminal context.

[0317] Optionally, the third request message includes at least one of the following:

[0318] First indication information, where the first indication information is used to instruct to resume interface transmission;

[0319] Restoration time information, where the restoration time information is used to indicate the time for resuming interface transmission;

[0320] Restoration reason indication information, where the restoration reason indication information is used to indicate that the feeder link is available or the feeder link has been switched;

[0321] Restoration type indication information, where the restoration type indication information is used to indicate restoration of the transmission function of part of the interfaces or restoration of the transmission function of part of the interfaces.

[0322] Optionally, when the restoration type indication information indicates restoration of transmission functions of some interfaces, the third request further includes interface information associated with the terminal.

[0323] Optionally, the fourth request includes at least one of the following:

[0324] Restoration reason indication information, where the restoration reason indication information is used to indicate that the feeder link has been restored or the feeder link has been switched;

[0325] Interface information associated with the terminal.

[0326] Optionally, the interface information includes at least one of the following:

[0327] The interface identifier of the terminal in the core network device;

[0328] The interface identifier of the terminal in the access network device.

[0329] Optionally, the communication management device 700 further includes:

[0330] The first receiving module is configured to receive at least one of a third response message and a fourth response message from the second device:

[0331] The third response is used to indicate consent to resume interface transmission;

[0332] The fourth response is used to indicate consent to restore the terminal context.

[0333] Optionally, the access network device includes at least one of the following:

[0334] Satellite-related network elements;

[0335] Store-and-forward type devices;

[0336] The satellite-related network elements include any one of the following: an on-board base station; an on-board central unit CU of a base station; or a CU of an on-board base station.

[0337] Optionally, the core network device is an onboard core network device.

[0338] 8 , an embodiment of the present application further provides a communication management device. As shown in FIG8 , the communication management device 800 includes:

[0339] The second receiving module 801 is configured for the second device to receive at least one of a first request message and a second request message from the first device;

[0340] The first request message is used to request the second device to suspend interface transmission;

[0341] The second request message is used to request the second device to suspend the terminal context;

[0342] The first device is an access network device, and the second device is a core network device; or the first device is a core network device, and the second device is an access network device.

[0343] Optionally, the second receiving module 801 is specifically configured to, when a feeder link between the first device and the second device is unavailable, receive at least one of a first request message and a second request message from the first device.

[0344] Optionally, the first request message includes at least one of the following:

[0345] Suspension reason indication information, where the suspension reason indication information is used to indicate that the feeder link is unavailable or will be unavailable;

[0346] Suspend type indication information, where the suspension type indication information is used to indicate the transmission function of the suspended part of the interface or the transmission function of the suspended part of the interface;

[0347] Suspend time information.

[0348] Optionally, when the suspension type indication information indicates suspending the transmission function of some interfaces, the first request message further includes interface information associated with the terminal.

[0349] Optionally, the suspension time information includes at least one of the following:

[0350] Suspend start time information;

[0351] Suspension duration information;

[0352] Suspension end time information;

[0353] Time information when the interface resumes transmission.

[0354] Optionally, the communication management device 800 further includes:

[0355] The second recovery module is configured to automatically recover at least one of the interface transmission and the terminal context based on the suspension time information.

[0356] Optionally, the second request message includes at least one of the following:

[0357] Suspension reason indication information, where the suspension reason indication information is used to indicate that the feeder link is unavailable or will be unavailable;

[0358] Interface information associated with the terminal.

[0359] Optionally, the communication management device 800 further includes:

[0360] A second sending module, configured to send at least one of a first response message and a second response message to the first device;

[0361] The first response message is used to indicate that the second device agrees to suspend interface transmission;

[0362] The second response message is used to indicate that the second device agrees to suspend the terminal context.

[0363] Optionally, in the case of suspended interface transmission, the transmission of target data between the first device and the second device is suspended.

[0364] Optionally, the target data includes at least one of first data and second data;

[0365] The first data includes at least one of the following: an access network device configuration update message; an uplink non-access layer NAS message of the terminal; a path switching request message; an uplink service data packet of the terminal;

[0366] The second data includes at least one of the following: a core network device configuration update message; a downlink NAS message of the terminal; a paging message; and a downlink service data packet of the terminal.

[0367] Optionally, the second receiving module 801 is further configured to: when the feeder link is available, receive at least one of a third request message and a fourth request message from the first device;

[0368] Wherein, the third request message is used to request to resume interface transmission;

[0369] The fourth request message is used to request the second device to restore the terminal context.

[0370] Optionally, the third request message includes at least one of the following:

[0371] First indication information, where the first indication information is used to instruct to resume interface transmission;

[0372] Restoration time information, where the restoration time information is used to indicate the time for resuming interface transmission;

[0373] Restoration reason indication information, where the restoration reason indication information is used to indicate that the feeder link is available or the feeder link has been switched;

[0374] Restoration type indication information, where the restoration type indication information is used to indicate restoration of the transmission function of part of the interfaces or restoration of the transmission function of part of the interfaces.

[0375] Optionally, when the restoration type indication information indicates restoration of transmission functions of some interfaces, the third request further includes interface information associated with the terminal.

[0376] Optionally, the fourth request includes at least one of the following:

[0377] Restoration reason indication information, where the restoration reason indication information is used to indicate that the feeder link has been restored or the feeder link has been switched;

[0378] Interface information associated with the terminal.

[0379] Optionally, the interface information includes at least one of the following:

[0380] The interface identifier of the terminal in the core network device;

[0381] The interface identifier of the terminal on the access network device.

[0382] Optionally, the communication management device 800 further includes:

[0383] The second sending module is configured to send at least one of a third response message and a fourth response message to the first device:

[0384] The third response is used to indicate consent to resume interface transmission;

[0385] The fourth response is used to indicate consent to restore the terminal context.

[0386] Optionally, the access network device includes at least one of the following:

[0387] Satellite-related network elements;

[0388] Store-and-forward type devices;

[0389] The satellite-related network elements include any one of the following: an on-board base station; an on-board central unit CU of a base station; or a CU of an on-board base station.

[0390] Optionally, the core network device is an onboard core network device.

[0391] The communication management device 800 in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal, or it can be other devices other than a terminal. For example, the terminal can include but is not limited to the types of terminals 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.

[0392] The communication management device provided in the embodiment of the present application can implement the various processes implemented by the method embodiment of Figure 3 or Figure 6 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0393] As shown in Figure 9, an embodiment of the present application also provides a communication device 900, including a processor 901 and a memory 902. The memory 902 stores a program or instruction that can be run on the processor 901. When the program or instruction is executed by the processor 901, the various steps of the above-mentioned communication management method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0394] The present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in Figure 3 or Figure 6. This network-side device embodiment corresponds to the aforementioned network-side device method embodiment, and each implementation process and implementation method of the aforementioned method embodiment is applicable to this network-side device embodiment and can achieve the same technical effects.

[0395] Specifically, an embodiment of the present application also provides a network-side device. As shown in Figure 10, the network-side device 1000 includes: an antenna 1001, a radio frequency device 1002, a baseband device 1003, a processor 1004, and a memory 1005. Antenna 1001 is connected to radio frequency device 1002. In the uplink direction, radio frequency device 1002 receives information via antenna 1001 and sends the received information to baseband device 1003 for processing. In the downlink direction, baseband device 1003 processes the information to be transmitted and sends it to radio frequency device 1002. Radio frequency device 1002 processes the received information and sends it through antenna 1001.

[0396] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 1003 , which includes a baseband processor.

[0397] The baseband device 1003 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 10, one of which is, for example, a baseband processor, which is connected to the memory 1005 through a bus interface to call the program in the memory 1005 and execute the network side device operations shown in the above method embodiment.

[0398] The network side device may further include a network interface 1006, which is, for example, a Common Public Radio Interface (CPRI).

[0399] Specifically, the network side device 1000 of the embodiment of the present application also includes: instructions or programs stored in the memory 1005 and can be run on the processor 1004. The processor 1004 calls the instructions or programs in the memory 1005 to execute the methods executed by each module shown in Figure 7 or Figure 8, and achieves the same technical effect. To avoid repetition, it will not be repeated here.

[0400] Specifically, the embodiment of the present application further provides a network-side device. As shown in FIG11 , the network-side device 1100 includes a processor 1101, a network interface 1102, and a memory 1103. The network interface 1102 is, for example, a common public radio interface (CPRI).

[0401] Specifically, the network side device 1100 of the embodiment of the present application also includes: instructions or programs stored in the memory 1103 and executable on the processor 1101. The processor 1101 calls the instructions or programs in the memory 1103 to execute the methods executed by the modules shown in FIG. 7 or FIG. 8 and achieve the same technical effect. To avoid repetition, they will not be elaborated here.

[0402] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned communication management method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0403] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0404] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned communication management method embodiment and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0405] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0406] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned communication management method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0407] An embodiment of the present application also provides a wireless communication system, including: a first device and a second device, wherein the first device can be used to execute the steps of the communication management method on the first device side as described above, and the second device can be used to execute the steps of the communication management method on the second device side as described above.

[0408] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0409] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0410] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A communication management method, comprising: The first device sends at least one of a first request message and a second request message to the second device; Wherein, the first request message is used to request the second device to suspend interface transmission; The second request message is used to request the second device to suspend the terminal context; Wherein, the first device is an access network device and the second device is a core network device; or, the first device is a core network device and the second device is an access network device.

2. The method according to claim 1, wherein, The first device sending at least one of a first request message and a second request message to the second device includes: When the power supply link between the first device and the second device will be unavailable, the first device sends at least one of a first request message and a second request message to the second device.

3. The method according to claim 1 or 2, wherein, The first request message includes at least one of the following: Suspension reason indication information, which is used to indicate that the power supply link is unavailable or will be unavailable; Suspension type indication information, which is used to indicate suspending the transmission function of part of the interface or suspending the transmission function of part of the interface; Suspension time information.

4. The method according to claim 3, wherein When the suspension type indication information indicates suspending the transmission function of part of the interface, the first request message further includes interface information associated with the terminal.

5. The method according to claim 3, wherein The suspension time information includes at least one of the following: Suspension start time information; Suspension duration information; Suspension end time information; Time information for the interface to resume transmission.

6. The method according to claim 3 or 5, wherein The method further includes: The first device automatically resumes at least one of interface transmission and terminal context restoration based on the suspension time information.

7. The method according to claim 1, wherein, The second request message includes at least one of the following: Suspension reason indication information, which is used to indicate that the power supply link is unavailable or the power supply link will be unavailable; Interface information associated with the terminal.

8. The method according to any one of claims 1 to 7, wherein, The method further includes: The first device receives at least one of a first response message and a second response message from the second device; Wherein, the first response message is used to indicate that the second device agrees to suspend interface transmission, and the second response message is used to indicate that the second device agrees to suspend the terminal context.

9. The method according to any one of claims 1 to 8, wherein, When suspending interface transmission, the transmission of target data between the first device and the second device is suspended.

10. The method according to claim 9, wherein, The target data includes at least one of first data and second data; Wherein, the first data includes at least one of the following: access network device configuration update message; terminal's uplink non-access stratum (NAS) message; path switch request message; terminal's uplink service data packet; The second data includes at least one of the following: core network device configuration update message; terminal's downlink NAS message; paging message; terminal's downlink service data packet.

11. The method according to any one of claims 1 to 10, wherein, The method further includes: When the power supply link is available, the first device sends at least one of a third request message and a fourth request message to the second device; Wherein, the third request message is used to request to resume interface transmission; The fourth request message is used to request the second device to resume the terminal context.

12. The method according to claim 11, wherein, The third request message includes at least one of the following: The first indication information, which is used to indicate the resumption of interface transmission; The resumption time information, which is used to indicate the time for resuming interface transmission; The resumption reason indication information, which is used to indicate that the power supply link is available or the power supply link has been switched; The resumption type indication information, which is used to indicate the resumption of the transmission function of some interfaces or the resumption of the transmission function of some interfaces.

13. The method according to claim 12, wherein, When the resumption type indication information indicates the resumption of the transmission function of some interfaces, the third request further includes the interface information associated with the terminal.

14. The method according to claim 12, wherein, The fourth request includes at least one of the following: The resumption reason indication information, which is used to indicate that the power supply link has been resumed or the power supply link has been switched; The interface information associated with the terminal.

15. The method according to claim 4, 7, 13 or 14, wherein The interface information includes at least one of the following: The interface identifier of the terminal in the core network device; The interface identifier of the terminal in the access network device.

16. The method according to any one of claims 11 to 15, wherein The method further includes: The first device receives at least one of a third response message and a fourth response message from the second device: Wherein, the third response is used to indicate consent to resume interface transmission, and the fourth response is used to indicate consent to resume the terminal context.

17. The method according to any one of claims 1 to 16, wherein The access network device includes at least one of the following: A network element related to a satellite; A store-and-forward type device; Wherein, the network element related to the satellite includes any one of the following: an on-board base station; a central unit (CU) of the base station on the satellite; the CU of the on-board base station.

18. The method according to any one of claims 1 to 17, wherein The core network device is an on-board core network device.

19. A communication management method, including: The second device receives at least one of a first request message and a second request message from the first device; Wherein, the first request message is used to request the second device to suspend interface transmission; The second request message is used to request the second device to suspend the terminal context; Wherein, the first device is an access network device and the second device is a core network device; or, the first device is a core network device and the second device is an access network device.

20. The method according to claim 19, wherein The second device receiving at least one of the first request message and the second request message from the first device includes: When the power supply link between the first device and the second device is about to become unavailable, the second device receives at least one of the first request message and the second request message from the first device.

21. The method according to claim 19 or 20, wherein The first request message includes at least one of the following: The suspension reason indication information, which is used to indicate that the power supply link is unavailable or about to become unavailable; The suspension type indication information, which is used to indicate the suspension of the transmission function of some interfaces or the suspension of the transmission function of some interfaces; The suspension time information.

22. The method according to claim 21, wherein, When the suspension type indication information indicates the suspension of the transmission function of some interfaces, the first request message further includes the interface information associated with the terminal.

23. The method according to claim 22, wherein, The suspension time information includes at least one of the following: The suspension start time information; The suspension duration information; The suspension end time information; The time information for the interface to resume transmission.

24. The method according to claim 21 or 23, wherein, The method further includes: The second device automatically resumes at least one of interface transmission and terminal context restoration based on the suspension time information.

25. The method according to claim 19, wherein, The second request message includes at least one of the following: Suspension reason indication information, which is used to indicate that the power supply link is unavailable or will be unavailable; Interface information associated with the terminal.

26. The method according to any one of claims 19 to 25, wherein The method further includes: The second device sends at least one of a first response message and a second response message to the first device; Among them, the first response message is used to indicate that the second device agrees to suspend interface transmission; The second response message is used to indicate that the second device agrees to suspend the terminal context.

27. The method according to any one of claims 19 to 26, wherein In the case of suspending interface transmission, the transmission of target data between the first device and the second device is suspended.

28. The method according to claim 27, wherein, The target data includes at least one of first data and second data; Among them, the first data includes at least one of the following: access network device configuration update message; terminal's uplink non-access stratum (NAS) message; path switch request message; terminal's uplink service data packet; The second data includes at least one of the following: core network device configuration update message; terminal's downlink NAS message; paging message; terminal's downlink service data packet.

29. The method according to any one of claims 19 to 28, wherein The method further includes: When the power supply link is available, the second device receives at least one of a third request message and a fourth request message from the first device; Among them, the third request message is used to request the restoration of interface transmission; The fourth request message is used to request the second device to restore the terminal context.

30. The method according to claim 29, wherein The third request message includes at least one of the following: First indication information, which is used to indicate the restoration of interface transmission; Restoration time information, which is used to indicate the time for restoring interface transmission; Restoration reason indication information, which is used to indicate that the power supply link is available or the power supply link has been switched; Restoration type indication information, which is used to indicate the restoration of the transmission function of some interfaces or the restoration of the transmission function of some interfaces.

31. The method according to claim 30, wherein When the restoration type indication information indicates the restoration of the transmission function of some interfaces, the third request further includes interface information associated with the terminal.

32. The method according to claim 30, wherein, The fourth request includes at least one of the following: Restoration reason indication information, which is used to indicate that the power supply link has been restored or the power supply link has been switched; Interface information associated with the terminal.

33. The method according to claim 22, 25, 31 or 32, wherein, The interface information includes at least one of the following: The interface identifier of the terminal in the core network device; The interface identifier of the terminal in the access network device.

34. The method according to any one of claims 29 to 33, wherein The method further includes: The second device sends at least one of a third response message and a fourth response message to the first device: Among them, the third response is used to indicate agreement to restore interface transmission; The fourth response is used to indicate agreement to restore the terminal context.

35. The method according to any one of claims 19 to 34, wherein The access network device includes at least one of the following: Network elements related to satellites; Store-and-forward type devices; Among them, the network elements related to satellites include any one of the following: on-satellite base stations; central units (CUs) of base stations on satellites; CUs of on-satellite base stations.

36. The method according to any one of claims 19 to 35, wherein, The core network device is a core network device on the satellite.

37. A communication management device, comprising: A first sending module, configured to send at least one of a first request message and a second request message from a first device to a second device; Wherein, the first request message is used to request the second device to suspend interface transmission; The second request message is used to request the second device to suspend the terminal context; Wherein, the first device is an access network device and the second device is a core network device; or, the first device is a core network device and the second device is an access network device.

38. The apparatus according to claim 37, wherein, Further comprising: A first receiving module, configured to receive at least one of a first response message and a second response message from the second device; Wherein, the first response message is used to indicate that the second device agrees to suspend interface transmission; The second response message is used to indicate that the second device agrees to suspend the terminal context.

39. The apparatus according to claim 37, wherein, The first sending module is further configured to: when the power supply link is available, send at least one of a third request message and a fourth request message to the second device; Wherein, the third request message is used to request to resume interface transmission; The fourth request message is used to request the second device to resume the terminal context.

40. The apparatus according to claim 39, wherein, Further comprising: A first receiving module, configured to receive at least one of a third response message and a fourth response message from the second device: Wherein, the third response is used to indicate agreement to resume interface transmission; The fourth response is used to indicate agreement to resume the terminal context.

41. A communication management device, comprising: A second receiving module, configured to receive at least one of a first request message and a second request message from a first device by a second device; Wherein, the first request message is used to request the second device to suspend interface transmission; The second request message is used to request the second device to suspend the terminal context; Wherein, the first device is an access network device and the second device is a core network device; or, the first device is a core network device and the second device is an access network device.

42. The apparatus according to claim 41, wherein, Further comprising: A second sending module, configured to send at least one of a first response message and a second response message to the first device; Wherein, the first response message is used to indicate that the second device agrees to suspend interface transmission; The second response message is used to indicate that the second device agrees to suspend the terminal context.

43. The apparatus according to claim 41, wherein, The second receiving module is further configured to: when the power supply link is available, receive at least one of a third request message and a fourth request message from the first device; Wherein, the third request message is used to request to resume interface transmission; The fourth request message is used to request the second device to resume the terminal context.

44. The apparatus according to claim 43, wherein, Further comprising: A second sending module, configured to send at least one of a third response message and a fourth response message to the first device: Wherein, the third response is used to indicate agreement to resume interface transmission; The fourth response is used to indicate agreement to resume the terminal context.

45. A network-side device, comprising a processor and a memory, the memory storing a program or instruction that can run on the processor, and when the program or instruction is executed by the processor, the steps of the communication management method according to any one of claims 1 to 36 are implemented.

46. A readable storage medium stores a program or instructions thereon, and when the program or instructions are executed by a processor, the steps of the communication management method according to any one of claims 1 to 36 are implemented.

Images