Communication management method and device, terminal and network side equipment

Abstract

The invention discloses a communication management method and device, a terminal and network side equipment, and belongs to the technical field of communication, and the communication management method comprises the steps that first equipment sends at least one of a first request message and a second request message to second equipment; wherein the first request message is used for requesting a second device to suspend interface transmission; the second request message is used for requesting a second device to suspend a terminal context; wherein the first equipment is access network equipment, and the second equipment is core network equipment; or, the first device is a core network device, and the second device is an access network device.

Description

Technical Field

[0001] This application belongs to the field of communication technologies, and particularly relates to a communication management method, apparatus, terminal, and network-side device. Background Art

[0002] With the development of communication technologies, in a non-terrestrial network (NTN) communication system, the base station and the core network device (or referred to as the core network element) are both fixedly deployed on the ground. Therefore, the interface management of the network element only supports the establishment and reset processes. Among them, the reset process is only initiated in the case of a failure. In other cases, it is considered that the interface channel between the base station and the core network device is available for information transmission. However, when the base station is in a movable state, for example, after the base station is mounted on a satellite, as the satellite moves, the base station and the core network device cannot always be connected, and thus normal information transmission cannot always be maintained. In this way, the reset process will be erroneously triggered, resulting in low management efficiency. Summary of the Invention

[0003] Embodiments of this application provide a communication management method, apparatus, terminal, and network-side device, which can solve the problem of low management efficiency.

[0004] In a first aspect, a communication management method is provided, including:

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

[0006] Wherein, the first request message is used to request the second device to suspend interface transmission;

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

[0008] 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.

[0009] In a second aspect, a communication management method is provided, including:

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

[0011] Wherein, the first request message is used to request the second device to suspend interface transmission;

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

[0013] 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.

[0014] In a third aspect, a communication management apparatus is provided, including:

[0015] 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;

[0016] Wherein, the first request message is used to request the second device to suspend interface transmission;

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

[0018] 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.

[0019] In a fourth aspect, a communication management apparatus is provided, including:

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

[0021] Wherein, the first request message is used to request the second device to suspend interface transmission;

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

[0023] 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.

[0024] In a fifth aspect, a network-side device is provided. The network-side device includes a processor and a memory. The memory stores a program or instruction that can run on the processor. When the program or instruction is executed by the processor, the steps of the method described in the first aspect or the second aspect are implemented.

[0025] In a sixth aspect, a network-side device is provided, including a processor and a communication interface. Wherein,

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

[0027] Wherein, the first request message is used to request the second device to suspend interface transmission;

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

[0029] 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.

[0030] Alternatively, when the network side device is the 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;

[0031] Wherein, the first request message is used to request the second device to suspend interface transmission;

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

[0033] 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.

[0034] In a seventh aspect, a readable storage medium is provided, on which a program or instructions are stored, and when the program or instructions are 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.

[0035] In an eighth aspect, a wireless communication system is provided, including: a terminal and a network side device, 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.

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

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

[0038] In the embodiments 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; 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. In this way, by requesting at least one of suspending interface transmission and suspending the terminal context through the request message, it is possible to avoid a fault-triggered reset process when the feeder link is disconnected due to satellite movement. Therefore, the embodiments of the present application improve the management efficiency of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 is a block diagram of a wireless communication system to which the embodiments of the present application can be applied;

[0040] Figure 2 is a block diagram of a wireless communication system to which the embodiments of the present application can be applied;

[0041] Figure 3 is one of the schematic flowcharts of a communication management method provided by the embodiments of the present application;

[0042] Figure 4a is another schematic flowchart of a communication management method provided by the embodiments of the present application;

[0043] Figure 4b is another schematic flowchart of a communication management method provided by the embodiments of the present application;

[0044] Figure 5 is another schematic flowchart of a communication management method provided by the embodiments of the present application;

[0045] Figure 6 is another schematic flowchart of a communication management method provided by the embodiments of the present application;

[0046] Figure 7 is a schematic structural diagram of a communication management device provided by the embodiments of the present application;

[0047] Figure 8 is a schematic structural diagram of another communication management device provided by the embodiments of the present application;

[0048] Figure 9 is a schematic structural diagram of a communication device provided by the embodiments of the present application;

[0049] Figure 10 is a schematic structural diagram of a network-side device provided by the embodiments of the present application;

[0050] Figure 11It is a schematic structural diagram of another network-side device provided by an embodiment of the present application. Detailed implementation manners

[0051] The terms "first", "second", etc. in the present application are used to distinguish similar objects, rather than to describe a specific order or sequence. It should be understood that such terms can be interchanged under appropriate circumstances, 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 usually of the same category, and the number of objects is not limited. For example, the first object can be one or multiple. In addition, "or" in the present application means at least one of the connected objects. For example, "A or B" covers three scenarios, namely, Scenario 1: including A and not including B; Scenario 2: including B and not including A; Scenario 3: including both A and B. The character " / " generally indicates an "or" relationship between the associated objects before and after.

[0052] The term "indication" in the present application can be either a direct indication (or an explicit indication) or an indirect indication (or an implicit indication). Among them, a direct indication can be understood as that the sender clearly tells the receiver specific information, operations to be performed, or request results, etc. in the sent indication; an indirect indication can be understood as that the receiver determines the corresponding information according to the indication sent by the sender, or makes a judgment and determines the operations to be performed or request results, etc. according to the judgment result.

[0053] It should be noted that the technology described in the embodiments of this application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, and 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 this application are often used interchangeably, and the described technology can be used in the above-mentioned systems and radio technologies, as well as in other systems and radio technologies. The following description describes the New Radio (NR) system for example purposes, and the NR term is used in most of the following descriptions, but these technologies can also be applied to systems other than the NR system, such as the 6th th Generation (6G) communication system.

[0054] Figure 1A block diagram of a wireless communication system to which embodiments of the present application can be applied is shown. The wireless communication system includes a terminal 11 and a network-side device 12. Among them, the terminal 11 can be a mobile phone, a tablet personal computer, a 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, a flight vehicle, a vehicle user equipment (VUE), a shipborne device, a pedestrian user equipment (PUE), a smart home (home devices with wireless communication functions, such as refrigerators, TVs, washing machines, or furniture, etc.), a game console, a personal computer (PC), a teller machine, or a self-service machine, etc. Wearable devices include: smart watches, smart bracelets, smart earphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart ankle chains, etc.), smart wristbands, smart clothing, etc. Among them, vehicle user equipment can also be referred to as vehicle terminals, vehicle controllers, vehicle modules, vehicle components, vehicle chips, or vehicle units, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application. The network-side device 12 can include an access network device or a core network device. Among them, the access network device can also be referred to as a radio access network (RAN) device, a radio access network function, or a radio access network unit. The access network device can 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, Transmission Reception Point (TRP), or some other suitable term in the art. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiments of this application, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.

[0055] The core network equipment may include but is not limited to at least one of the following: core network nodes, core network functions, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), Binding Support Function (BSF), Application Function (AF), etc. It should be noted that in the embodiments of this application, only the core network equipment in the NR system is taken as an example for introduction, and the specific type of the core network equipment is not limited.

[0056] For the convenience of understanding, some content related to the embodiments of this application will be described below:

[0057] I. Non-terrestrial networks (NTN).

[0058] Typical NTN deployment scenarios are as follows. Such as Figure 2As shown, the link between the terminal and the satellite is called the service link (i.e., service link), and the link between the satellite and the terrestrial gateway is called the feeder link, which can also be called the feeder line link. In some scenarios (such as low Earth orbit satellites LEO), due to satellite movement, switching of the service link and / or feeder link may occur. For service link switching, the serving satellite of all UEs within the cell needs to be switched from one satellite to another. For feeder link switching, a certain satellite needs to be switched from one terrestrial gateway to another terrestrial gateway.

[0059] The NTN communication system includes two types: the NTN communication system based on transparent payload and the NTN communication system based on regenerative payload. Currently, only the NTN communication system based on transparent payload is considered. In this deployment environment, the terminal, the base station, and the core network equipment are all deployed on the ground, and the communication data between the terminal and the network-side equipment is relayed via the satellite in the air. In this system, the satellite is only used to forward the data between the base station and the terminal, and does not decode and process this data. For the NTN communication system based on regenerative payload, the satellite has some or all of the base station functions and can decode and process the uplink or downlink data. Exemplarily, if the satellite has all the functions of the access network, the access network equipment can be called the on-satellite access network equipment or the on-satellite base station equipment. In popular terms, it can also be called the base station on the satellite. In this case, the central unit CU function of the access network is called the central unit CU of the on-satellite access network, and the distributed unit DU function of the access network is called the distributed unit DU of the on-satellite access network. If the satellite has the central unit CU function of the access network, the central unit CU of the access network can be called the on-satellite central unit CU of the access network equipment. In popular terms, it can also be called the central unit CU on the satellite. If the satellite has the distributed unit DU function of the access network, the distributed unit DU of the access network can be called the on-satellite distributed unit DU of the access network equipment. In popular terms, it can also be called the distributed unit DU on the satellite.

[0060] II. S1 or NG interface management.

[0061] In the LTE communication system, the interface between the base station and the core network device is the S1 interface, while in the NR communication system, the interface between the base station and the core network device is the NG interface. The S1 interface and the NG interface are divided into a control plane interface S1-C or NG-C and a 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 (UPF) for transmitting service data. The control plane interface S1-C or NG-C is connected to the core network control plane network element MME or AMF for transmitting control plane information. The management of the S1 interface and the management of the NG interface are similar. Subsequently, the management process of the NG interface will be introduced taking NR as an example. The current mechanism supports the establishment process and the reset process of the NG interface.

[0062] NG establishment process: This process is initiated by the base station. If the AMF agrees to establish, it will reply with an NG setup response message. If the AMF cannot receive the establishment request, it will reply with an NG setup failure message.

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

[0064] Currently, the S1 or NG reset process is usually used in special scenarios. For example, when a base station node fails and some or all of the reference information is lost, the RAN will initiate the NG reset process. Similarly, when a failure occurs at the core network device AMF, the AMF will initiate the NG reset process.

[0065] In the communication system, since both the base station and the core network device are fixedly deployed on the ground, the interface management of the network element only supports the establishment and reset processes. Among them, the reset process is only initiated in case of a failure. In other cases, it is considered that the interface channel between the base station and the core network device is available for information transmission. However, after the base station is launched into space, as the satellite moves, the base station and the core network device cannot always be connected, and thus normal information transmission cannot always be maintained. Therefore, the existing mechanism will cause unnecessary information transmission, which is not conducive to the system management efficiency. For this reason, the communication management method of this application is proposed.

[0066] Next, in conjunction with the accompanying drawings, the communication management method provided by the embodiments of this application will be described in detail through some embodiments and their application scenarios.

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

[0068] Referring Figure 3 , an embodiment of the present application provides a communication management method. As Figure 3 shown, the communication management method includes:

[0069] Step 301, the first device sends at least one of a first request message and a second request message to the second device;

[0070] Wherein, the first request message is used to request the second device to suspend interface transmission;

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

[0072] 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.

[0073] In the embodiments of the present application, the above 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, which is not further limited herein.

[0074] Optionally, the access network device in each embodiment of the present application can be a satellite device, a device related to a satellite, or a device in a mobile state or supporting mobility (i.e., having the ability to move).

[0075] 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 expires, if the first device does not receive the response message of the second device (specifically refer to the subsequent embodiments), it is defaulted that the second device refuses to suspend interface transmission and / or refuses to suspend the terminal context. Additionally, it should be noted that the first device can start one timer for the first request message and the second request message, or start timers respectively.

[0076] Optionally, the above-mentioned suspension interface transmission can be understood as a suspension interface transmission function. For example, part or all of the interface transmission functions can be suspended. Among them, the interface can be understood as an S1 interface or a suspended NG interface. Through the suspension interface transmission, part or all of the interface transmissions of the terminals associated with the interface can be suspended. It should be understood that in some embodiments, the interface transmissions of different terminals can be suspended through multiple first request messages.

[0077] Optionally, the terminal context can be suspended, and the data transmission of the terminal can also be suspended, which can avoid accidentally triggering the reset process, and thus can improve the management efficiency of the system.

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

[0079] A network element related to a satellite;

[0080] A store-and-forward type device;

[0081] Among them, the network element related to the satellite includes any one of the following: an on-satellite base station; an on-satellite central unit CU of the base station; the CU of the on-satellite base station.

[0082] Optionally, in some embodiments, the core network device is an on-satellite core network device. In other embodiments, the core network device can be a ground device, such as being deployed on the ground.

[0083] Optionally, the above-mentioned first request message can be understood as an interface suspension request message, and the second request message can be understood as a terminal context suspension request message.

[0084] In the embodiments 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 the 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. In this way, since at least one of suspending the interface transmission and suspending the terminal context is requested through the request message, the failure to trigger the reset process when the feeder link is disconnected due to satellite movement can be avoided. Therefore, the embodiments of the present application improve the management efficiency of the system.

[0085] 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:

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

[0087] In the embodiments of the present application, the feed link can be understood or replaced with a feed line. Wherein, the feed link will be unavailable can be understood or replaced with the feed link is about to be unavailable, the feed link will be disconnected, the feed link is about to be disconnected, the feed link will be switched, or the feed link is about to be switched, etc.

[0088] Optionally, the determination of the time point when the feed link between the first device and the second device will be 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 feed link is unavailable. One implementation method is that based on information such as the trajectory and speed of the satellite movement, the time point when the feed link is unavailable can be determined, and then based on this time point, it can be considered that the feed link will be unavailable at a preset moment before this time point. Another implementation method is to obtain the current position information of the satellite, and assume that when the satellite moves to a certain position before a specific position, the feed link is considered to be unavailable.

[0089] It should be noted that the service link in each embodiment of the present application can 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 the ability to move. The feed link in each embodiment of the present application can be a satellite feed link, or a (mobile) feed link, that is, at least one network element or device in the link is in a mobile state or has the ability to move.

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

[0091] Suspension reason indication information. Exemplarily, the suspension reason indication information is used to indicate that the feed link is unavailable or about to be unavailable;

[0092] Suspension type indication information, which is used to indicate suspending the transmission function of some interfaces or suspending the transmission function of some interfaces;

[0093] Suspension time information.

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

[0095] Optionally, for suspending all interface transmission functions, the suspension type indication information may be understood as indicating the suspension of all NG interface transmissions between the first device and the second device.

[0096] Optionally, for suspending the transmission functions of some interfaces, the suspension type indication information may be understood as indicating the suspension of the transmission of relevant information of some terminals. For example, in some embodiments, when the suspension type indication information indicates the suspension of the transmission functions of some interfaces, the first request message further includes the interface information associated with the terminal.

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

[0098] Suspension start time information;

[0099] Suspension duration information;

[0100] Suspension end time information;

[0101] Time information for the interface to resume transmission.

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

[0103] Optionally, the suspension duration information is used to indicate the duration of suspending the interface. It can be used in conjunction with the suspension start time information, can be used to determine the time when the interface resumes, and can also be used to represent the shortest or longest duration of suspension. Optionally, the suspension duration information can also represent a suspension time period, such as 12:00 - 12:30. In some other embodiments, the suspension duration information can represent the suspension duration, such as 30 minutes.

[0104] Optionally, the time information for the interface to resume transmission may indicate a future time. 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.

[0105] Optionally, in some embodiments, the method further includes:

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

[0107] In the embodiments of the present application, the first device and the second device may automatically resume at least one of interface transmission and terminal context restoration based on the suspension time information, which can reduce signaling interaction. It should be understood that the suspension behavior corresponds to the restoration behavior, that is, in the case of suspending interface transmission, the interface transmission can be automatically resumed based on the suspension time information; in the case of suspending the terminal context, the terminal context can be automatically resumed based on the suspension time information.

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

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

[0110] Optionally, in some embodiments, the restoration time point may be determined based on the time information of interface restoration transmission, and at this time point, at least one of interface transmission and terminal context restoration may be automatically resumed.

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

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

[0113] Interface information associated with the terminal.

[0114] In the embodiments of the present application, the suspension reason indication information in the first request message is the same as the suspension reason indication information in the second request message. For specific explanations, reference may be made to the first request message, which will not be elaborated here.

[0115] Optionally, in some embodiments, the method further includes:

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

[0117] 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.

[0118] In the embodiments of the present application, the above 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. Since in the embodiments of the present application, the second device sends a response message to the first device, it can ensure that the first device and the second device maintain consistent understanding of the behavior of the suspended interface and the suspended terminal context, so as to avoid subsequent incorrect transmission behaviors.

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

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

[0121] Optionally, in some embodiments, when the second device receives the above first request message, the second device can send a first response message to the first device, and the first response message is used to indicate that the second device agrees to suspend the interface transmission. In other embodiments, when the second device receives the above first request message, the second device sends a rejection message to the first device, and the rejection message is used to indicate that the second device refuses to suspend the interface transmission. It should be noted that the above first response message and the rejection message can be the same message, and an information field for agreeing or rejecting is carried in the message. In other embodiments, when the second device receives the above first request message, the second device does not send any message to the first device, then it is default to reject the interface transmission. In some embodiments, when the second device agrees to suspend the interface transmission, the second device stores the context of the first device, or suspends the context of the first device. In some embodiments, when receiving the above first request message, the second device stores the context of the first device, or suspends the context of the first device. This situation can be applicable to scenarios where the second device will not reject the suspension of the interface transmission.

[0122] Optionally, in some embodiments, when the first device receives the above first response message, the first device suspends the context of the second device, or the first device stores the context of the second device. Since the storage capacity of on-board devices is limited, in other embodiments, when the first device receives the above first response message, the first device can delete all or part of the context of the first device (such as only retaining the AMFname).

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

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

[0125] 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;

[0126] 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.

[0127] In the embodiments of the present application, the suspension of the transmission of the target data between the first device and the second device can be understood to include at least one of the following:

[0128] 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;

[0129] 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.

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

[0131] Optionally, in some embodiments, the method further includes:

[0132] 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;

[0133] Wherein, the third request message is used to request the restoration of interface transmission;

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

[0135] In the embodiments of the present application, the availability of the power supply link can be understood as the power supply link switching, the power supply link connecting, or the power supply link restoring.

[0136] Optionally, the above third request message can be understood as an interface restoration request message, and the fourth request message can be understood as a terminal context suspension restoration request message.

[0137] Optionally, in some embodiments, when the second device receives the third request message, the second device restores, activates, re - activates, or re - uses 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 restore the interface transmission, it sends a failure message to the first device. The failure message is used to indicate that the restoration of the interface transmission fails.

[0138] Optionally, in some embodiments, when the second device receives the fourth request message, the second device restores, activates, re - activates, or re - uses 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, it sends a failure message to the first device. The failure message is used to indicate that the restoration of the terminal context fails.

[0139] It should be understood that in the embodiments of the present application, the third request message and the fourth request message respectively correspond to the first request message and the second request message. 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; 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.

[0140] It should be noted that in some embodiments, at least one of the third request message and the fourth request message can be sent at the moment when it is determined that the feeding link is available. At least one of the third request message and the fourth request message can also be sent after a preset time period after it is determined that the feeding link is available, which can ensure the stability of the feeding link connection.

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

[0142] The first indication information, which is used to indicate the restoration of the interface transmission;

[0143] The restoration time information, which is used to indicate the time for restoring the interface transmission;

[0144] The restoration reason indication information, which is used to indicate that the feeding link is available or the feeding link has been switched;

[0145] The 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.

[0146] Optionally, in some embodiments, when the recovery type indication information indicates to recover the transmission function of a partial interface, the third request further includes interface information associated with the terminal.

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

[0148] Recovery reason indication information, which is used to indicate that the feeding link has been restored or the feeding link has been switched;

[0149] Interface information associated with the terminal.

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

[0151] The interface identifier of the terminal at the core network device;

[0152] The interface identifier of the terminal at the access network device.

[0153] Wherein, the interface identifier of the core network device may include AMF UE NGAP ID or MME UE S1AP ID; the interface identifier of the terminal at the access network device may include RAN UE NGAP ID or eNB UE S1AP ID.

[0154] Optionally, in some embodiments, the method further includes:

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

[0156] 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.

[0157] Optionally, the above third response message can be understood as an interface recovery response message, and the fourth response message can be understood as a terminal context hanging recovery response message.

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

[0159] Optionally, in some embodiments, when the first device receives the above third response message, the first device resumes, or activates, or re - activates, or re - uses the context of the second device. In other embodiments, if the first device receives a message indicating that the recovery of interface transmission fails from the second device, the first device deletes the stored context of the first device.

[0160] Optionally, in some embodiments, when the first device receives the second response message, the first device restores, activates, re - activates, or re - uses the context of the terminal. In other embodiments, if the first device receives a message indicating that the restoration of the terminal context fails from the second device, the first device deletes the stored context of the terminal.

[0161] To better understand this application, the following will be described through some specific examples.

[0162] Embodiment 1, the suspension and restoration process of the S1 interface or the NG interface.

[0163] Step 11, in a scenario where the feeder link is switched (such as the feeder link is about to be disconnected or become unavailable), the network node suspends the interface transmission. The network node's suspension of the interface transmission includes: the base station sending an interface suspension request message to the core network element. Among them, the interface suspension request message is used to request the core network element to suspend the interface transmission.

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

[0165] Network elements related to satellites;

[0166] Store - and - forward type devices;

[0167] Among them, the network elements related to satellites include any one of the following: on - satellite base stations; on - satellite central units (CUs) of base stations; CUs of on - satellite base stations.

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

[0169] The S1 interface, including at least one of S1 - C and S1 - U; it should be noted that this use case is applicable to the case of connecting to the LTE core network, such as the interface between an LTE base station (eNB) and an LTE core network element;

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

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

[0172] Core network control plane elements, 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 element is MME, and when the base station is connected to the 5G core network, the core network control plane element is AMF;

[0173] Core network user plane network elements, such as UPF or S-GW; It should be noted that in the case where the base station is connected to the 5G core network, the core network control plane network element is S-GW, and in the case where the base station is connected to the 5G core network, the core network control plane network element is UPF.

[0174] It should be noted that if the on-star base station is connected to multiple types of core networks at the same time, such as being connected to 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 network elements respectively.

[0175] Among them, the interface suspension request message includes at least one of the following: suspension reason indication information; suspension type indication information; interface suspension time information.

[0176] Optionally, the suspension reason indication information is used to indicate a feeder link handover (or feeder link disconnection), or to indicate that a feeder link handover (or feeder link disconnection) is about to occur.

[0177] For example, in the case of a hard feeder link handover scenario, the base station can initiate an NG suspension process before the feeder link handover occurs.

[0178] For example, in the case of a soft feeder link handover scenario, the base station can initiate an NG suspension process before or when the feeder link handover occurs.

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

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

[0181] Suspend all interface transmission functions; Exemplarily, the suspension type information is used to indicate suspending all NG interface transmissions between the base station and the core network network element;

[0182] Suspend partial interface transmission functions; In this case, the suspension type indication information can be understood as suspending the relevant information transmission of some terminals. In this case, exemplarily, the interface suspension request message also carries the interface information associated with the terminal.

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

[0184] 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 the interface transmission of one or more terminals. Exemplarily, the interface suspension request message may include NG interface information associated with one or more terminals.

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

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

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

[0188] Suspension start time information, which 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 sends the interface suspension request message, or be used to indicate a future time;

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

[0190] Suspension end time information, which is used to indicate the end time of suspending the interface transmission. The suspension end time information is used to indicate a future time;

[0191] Time information for the interface to resume transmission. The time information for the interface to resume transmission may indicate a future time. 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 element resumes connection, and the base station can determine the time information for the interface to resume transmission based on ephemeris information.

[0192] Step 12, in the scenario of feeder link switching (such as about to be disconnected), the base station receives an interface suspension response message sent by the core network element. Among them, the interface suspension response message is used to indicate to the base station that the core network element agrees to suspend the interface transmission.

[0193] Additionally, when the interface suspension request message carries interface suspension time information, the interface suspension response message is further used to indicate to the base station that the core network element agrees to automatically resume the 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.

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

[0195] Optionally, in the scenario of feeder link switching, the core network element may indicate to the base station, through the interface suspension response message, to agree to suspend the interface transmission of some or all terminals associated with the interface. The core network element may send multiple interface suspension response messages to indicate to the base station to agree to suspend the interface transmissions of multiple different terminals.

[0196] It should be noted that when the interface suspension response message does not carry interface information associated with a terminal, it is default to agree to suspend all interface transmission functions.

[0197] Optionally, when the interface transmission (such as S1 or NG interface) is suspended, the behaviors of the network node include at least one of the following:

[0198] 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: base station configuration update message, such as eNB configuration update message, RAN configuration update message; UL NAS message of the terminal; path switch request message; UL service data packet of the terminal.

[0199] When the 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: core network element configuration update message, such as MME configuration update message, AMF configuration update message; DL NAS message of the terminal; paging message, such as paging message; DL service data packet of the terminal.

[0200] Step 13, in the scenario where the feeder link switching is like feeder link recovery or the feeder link is available, the network node resumes the interface transmission. The network node resuming the interface transmission includes at least one of the following:

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

[0202] Based on the time information for interface recovery, the base station automatically resumes interface transmission at the time indicated by the time information for interface recovery (as Figure 4b shown). The core network element associated with the interface also automatically resumes interface transmission at the time indicated by the time information for interface recovery.

[0203] 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.

[0204] Exemplarily, resuming all interface transmission functions is used to indicate resuming all NG interface transmissions between the base station and the core network element.

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

[0206] It should be noted that the interface suspension response message may include the interface information associated with one or more terminals, and is used to agree to resume the interface transmission of one or more terminals. Exemplarily, the interface recovery response message may include the NG interface information associated with one or more terminals.

[0207] Optionally, in the feeder link switching scenario (such as recovery), the base station may request the core network to resume the interface transmission of some or all terminals associated with this interface through the interface recovery request message. The base station may send multiple interface recovery request messages to indicate to the core network element to request resuming the interface transmission of multiple different terminals.

[0208] It should be noted that when the interface recovery request message does not carry the interface information associated with the terminals, it is default to request resuming all interface transmission functions.

[0209] Step 14, in the feeder link switching (such as recovery) scenario, the base station receives the interface recovery response message sent by the core network element. The interface recovery response message is used to indicate that the base station agrees to resume interface transmission. The interface recovery response message may additionally carry the interface information associated with the terminals.

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

[0211] Optionally, in a feeder link handover scenario, the core network element may use the interface recovery response message to instruct the base station to resume the interface transmission of some or all of the terminals associated with the interface. The core network element may send multiple interface recovery response messages to instruct the base station to agree to suspend the interface transmission of multiple different terminals.

[0212] It should be noted that when the interface information associated with the terminal is not carried in the interface recovery response message, it is default to agree to resume all interface transmission functions.

[0213] It should be noted that in this embodiment, the above base station behavior may also be performed by the core network element, and the uplink core network element behavior may also be performed by the base station. The prerequisite for the core network element to initiate the interface suspension and recovery process is that the core network element can obtain the ephemeris information of the satellite, and can determine the disconnection and recovery time of the feeder link with the on-satellite base station based on the ephemeris information. The ephemeris information may be configured for the core network element based on OAM.

[0214] Embodiment 2, the suspension and recovery process of the UE context.

[0215] Step 21, in a scenario where the feeder link is about to be handed over (such as the feeder link is about to be disconnected or the feeder link will be unavailable), the network node suspends the UE context. The network node suspending the UE context includes: the base station sending a UE context suspension request message to the core network element (as shown in Figure 5 ). Among them, the UE context suspension request message is used to request the core network element to suspend the context of the terminal.

[0216] Among them, the definitions of the base station, the core network element, and the interface may refer to the above embodiment and will not be elaborated here.

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

[0218] Suspension reason indication information, which is used to indicate the feeder link handover (or the feeder link disconnection), or to indicate that the feeder link is about to be handed over (or the feeder link is about to be disconnected);

[0219] Interface information associated with the terminal.

[0220] Step 22: In a scenario where the feeder link is about to be handed over (such as about to be disconnected), the base station receives the UE context suspension response message sent by the core network element. Among them, the UE context suspension response message is used to indicate that the core network element agrees to suspend the UE context.

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

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

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

[0224] Interface information associated with the terminal.

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

[0226] It should be noted that the above base station behavior can also be performed by the core network element, and the uplink core network element behavior can also be performed by the base station. The prerequisite for the core network element to initiate the interface suspension and restoration process is that the core network element can obtain the ephemeris information of the satellite and can determine the disconnection and restoration time of the feeder link with the on-satellite base station based on the ephemeris information. The ephemeris information can be configured for the core network element based on OAM.

[0227] Refer to Figure 6 This application embodiment also provides a communication management method. As Figure 6 shown, this communication management method includes:

[0228] Step 601, the second device receives at least one of a first request message and a second request message from the first device;

[0229] Among them, the first request message is used to request the second device to suspend interface transmission;

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

[0231] Among them, 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.

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

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

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

[0235] Suspension reason indication information, which is used to indicate that the power feed link is unavailable or will be unavailable;

[0236] 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;

[0237] Suspension time information.

[0238] Optionally, in the case where 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.

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

[0240] Suspension start time information;

[0241] Suspension duration information;

[0242] Suspension end time information;

[0243] Time information for the interface to resume transmission.

[0244] Optionally, the method further includes:

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

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

[0247] Suspension reason indication information, which is used to indicate that the power feed link is unavailable or the power feed link will be unavailable;

[0248] Interface information associated with the terminal.

[0249] Optionally, the method further includes:

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

[0251] Among them, the first response message is used to indicate that the second device agrees to suspend interface transmission;

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

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

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

[0255] 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;

[0256] 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.

[0257] Optionally, the method further includes:

[0258] When the power feeding link is available, the second device receives at least one of a third request message and a fourth request message from the first device;

[0259] Among them, the third request message is used to request to resume interface transmission;

[0260] The fourth request message is used to request the second device to resume the terminal context.

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

[0262] First indication information, which is used to indicate resuming interface transmission;

[0263] Resume time information, which is used to indicate the time to resume interface transmission;

[0264] Resume reason indication information, which is used to indicate that the power feeding link is available or the power feeding link has been switched;

[0265] Resume type indication information, which is used to indicate resuming the transmission function of part of the interfaces or resuming the transmission function of part of the interfaces.

[0266] Optionally, when the resume type indication information indicates resuming the transmission function of part of the interfaces, the third request further includes interface information associated with the terminal.

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

[0268] Recovery reason indication information, which is used to indicate that the feeding link has been restored or the feeding link has been switched;

[0269] Interface information associated with the terminal.

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

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

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

[0273] Optionally, the method further includes:

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

[0275] Wherein, the third response is used to indicate consent to resume interface transmission;

[0276] The fourth response is used to indicate consent to resume the terminal context.

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

[0278] A network element related to a satellite;

[0279] A store-and-forward type device;

[0280] Wherein, the network element related to the satellite includes any one of the following: an on-satellite base station; a central unit CU of the base station on the satellite; a CU of the on-satellite base station.

[0281] Optionally, the core network device is an on-satellite core network device.

[0282] For the communication management method provided in the embodiments of the present application, the execution subject may be a communication management device. In the embodiments of the present application, taking the communication management device executing the communication management method as an example, the communication management device provided in the embodiments of the present application is described.

[0283] Referring to Figure 7 , the embodiments of the present application further provide a communication management device, as Figure 7 shown, the communication management device 700 includes:

[0284] A first sending module 701, configured to send at least one of a first request message and a second request message from a first device to a second device;

[0285] Wherein, the first request message is used to request the second device to suspend interface transmission;

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

[0287] 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.

[0288] Optionally, the first sending module 701 is specifically configured to send at least one of the first request message and the second request message to the second device when the power feeding link between the first device and the second device is about to become unavailable.

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

[0290] Suspension reason indication information, which is used to indicate that the power feeding link is unavailable or about to become unavailable;

[0291] Suspension type indication information, which is used to indicate suspending the transmission function of some interfaces or suspending the transmission function of some interfaces;

[0292] Suspension time information.

[0293] 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.

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

[0295] Suspension start time information;

[0296] Suspension duration information;

[0297] Suspension end time information;

[0298] Time information for the interface to resume transmission.

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

[0300] A first recovery module, configured to automatically resume at least one of interface transmission and terminal context based on the suspension time information.

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

[0302] Suspension reason indication information, which is used to indicate that the power feeding link is unavailable or about to become unavailable;

[0303] Interface information associated with the terminal.

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

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

[0306] Wherein, the first response message is used to indicate that the second device agrees to suspend interface transmission;

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

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

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

[0310] 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;

[0311] 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.

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

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

[0314] The fourth request message is used to request the second device to resume the terminal context.

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

[0316] First indication information, which is used to indicate resuming interface transmission;

[0317] Resume time information, which is used to indicate the time for resuming interface transmission;

[0318] Resume reason indication information, which is used to indicate that the power feeding link is available or the power feeding link has been switched;

[0319] Resume type indication information, which is used to indicate resuming the transmission function of part of the interface or resuming the transmission function of part of the interface.

[0320] Optionally, when the recovery type indication information indicates to recover the transmission function of a partial interface, the third request further includes interface information associated with the terminal.

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

[0322] Recovery reason indication information, which is used to indicate that the power supply link has been restored or the power supply link has been switched;

[0323] Interface information associated with the terminal.

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

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

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

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

[0328] A first receiving module, configured to receive at least one of a third response message and a fourth response message from the second device:

[0329] Wherein, the third response is used to indicate consent to resume interface transmission;

[0330] The fourth response is used to indicate consent to resume the terminal context.

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

[0332] A network element related to a satellite;

[0333] A store-and-forward type device;

[0334] Wherein, the network element related to the satellite includes any one of the following: an on-satellite base station; a central unit CU of the base station on the satellite; a CU of the on-satellite base station.

[0335] Optionally, the core network device is an on-satellite core network device.

[0336] Referring to Figure 8 , an embodiment of the present application further provides a communication management device, as Figure 8 shown, the communication management device 800 includes:

[0337] A second receiving module 801, configured to receive at least one of a first request message and a second request message from a first device by the second device;

[0338] Wherein, the first request message is used to request the second device to suspend interface transmission;

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

[0340] Wherein, the first device is an access network device, and the second device is a core network device; alternatively, the first device is a core network device, and the second device is an access network device.

[0341] Optionally, the second receiving module 801 is specifically configured to receive at least one of the first request message and the second request message from the first device when the power supply link between the first device and the second device will be unavailable.

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

[0343] Suspension reason indication information, which is used to indicate that the power supply link is unavailable or will be unavailable;

[0344] Suspension type indication information, which is used to indicate suspending the transmission function of some interfaces or suspending the transmission function of some interfaces;

[0345] Suspension time information.

[0346] 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.

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

[0348] Suspension start time information;

[0349] Suspension duration information;

[0350] Suspension end time information;

[0351] Time information for the interface to resume transmission.

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

[0353] A second recovery module, which is used to automatically resume at least one of interface transmission and terminal context recovery based on the suspension time information.

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

[0355] Suspension reason indication information, which is used to indicate that the power supply link is unavailable or the power supply link will be unavailable;

[0356] Interface information associated with the terminal.

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

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

[0359] Wherein, the first response message is used to indicate that the second device agrees to suspend interface transmission;

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

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

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

[0363] 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;

[0364] 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.

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

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

[0367] The fourth request message is used to request the second device to resume the terminal context.

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

[0369] First indication information, which is used to indicate resuming interface transmission;

[0370] Resume time information, which is used to indicate the time for resuming interface transmission;

[0371] Resume reason indication information, which is used to indicate that the power feed link is available or the power feed link has been switched;

[0372] Resume type indication information, which is used to indicate resuming the transmission function of part of the interface or resuming the transmission function of part of the interface.

[0373] Optionally, when the recovery type indication information indicates to recover the transmission function of a partial interface, the third request further includes interface information associated with the terminal.

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

[0375] Recovery reason indication information, which is used to indicate that the power feeding link has been restored or the power feeding link has been switched;

[0376] Interface information associated with the terminal.

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

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

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

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

[0381] A second sending module, configured to send at least one of a third response message and a fourth response message to the first device:

[0382] Wherein, the third response is used to indicate consent to resume interface transmission;

[0383] The fourth response is used to indicate consent to resume the terminal context.

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

[0385] A network element related to a satellite;

[0386] A store-and-forward type device;

[0387] Wherein, the network element related to the satellite includes any one of the following: an on-satellite base station; a central unit CU on the satellite of the base station; a CU of the on-satellite base station.

[0388] Optionally, the core network device is an on-satellite core network device.

[0389] The communication management device 800 in the embodiments of the present application may 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 a chip. The electronic device may be a terminal or other devices other than the terminal. Exemplarily, the terminal may include, but is not limited to, the types of the terminal 11 listed above, and other devices may be a server, a Network Attached Storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0390] The communication management device provided by the embodiments of the present application can implement Figure 3 or Figure 6 each process implemented by the method embodiments, and achieve the same technical effects. To avoid repetition, details are not described herein again.

[0391] As Figure 9 shown, the embodiments of the present application further provide a communication device 900, including a processor 901 and a memory 902. A program or instruction that can run on the processor 901 is stored on the memory 902. When the program or instruction is executed by the processor 901, each step of the above-mentioned communication management method embodiments is implemented, and the same technical effects can be achieved. To avoid repetition, details are not described herein again.

[0392] The embodiments of the present application further provide a network-side device, including a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run a program or instruction to implement as Figure 3 or Figure 6 shown in the method embodiments. The network-side device embodiments correspond to the above-mentioned network-side device method embodiments. Each implementation process and implementation manner of the above method embodiments can be applied to the network-side device embodiments, and the same technical effects can be achieved.

[0393] Specifically, the embodiments of the present application further provide a network-side device. As Figure 10 shown, 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. The antenna 1001 is connected to the radio frequency device 1002. In the uplink direction, the radio frequency device 1002 receives information through the antenna 1001 and sends the received information to the baseband device 1003 for processing. In the downlink direction, the baseband device 1003 processes the information to be sent and sends it to the radio frequency device 1002. After processing the received information, the radio frequency device 1002 sends it out through the antenna 1001.

[0394] The method executed by the network-side device in the above embodiments can be implemented in the baseband device 1003. The baseband device 1003 includes a baseband processor.

[0395] The baseband device 1003 may include, for example, at least one baseband board. A plurality of chips are provided on the baseband board. As Figure 10 shown, one of the chips 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 operations of the network-side device shown in the above method embodiments.

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

[0397] Specifically, the network-side device 1000 according to the embodiment of the present application further includes: instructions or programs stored in the memory 1005 and executable on the processor 1004. The processor 1004 calls the instructions or programs in the memory 1005 to execute Figure 7 or Figure 8 the methods executed by the modules shown, and achieves the same technical effects. To avoid repetition, details are not described herein.

[0398] Specifically, the embodiment of the present application further provides a network-side device. As Figure 11 shown, the network-side device 1100 includes: a processor 1101, a network interface 1102, and a memory 1103. Among them, the network interface 1102 is, for example, a Common Public Radio Interface (CPRI).

[0399] Specifically, the network-side device 1100 according to the embodiment of the present application further 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 Figure 7 or Figure 8 the methods executed by the modules shown, and achieves the same technical effects. To avoid repetition, details are not described herein.

[0400] The embodiment of the present application further provides a readable storage medium, on which a program or instructions are stored. When the program or instructions are executed by a processor, each process of the communication management method embodiment described above is implemented, and the same technical effects can be achieved. To avoid repetition, details are not described here.

[0401] Among them, 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, a random access memory RAM, a magnetic disk, or an optical disc, etc. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0402] The embodiment of the present application further provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement each process of the communication management method embodiment described above, and the same technical effects can be achieved. To avoid repetition, details are not described here.

[0403] It should be understood that the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, system chip, chip system, or system-on-chip, etc.

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

[0405] The embodiments of the present application further provide a wireless communication system, including: a first device and a second device. 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.

[0406] It should be noted that in this article, the term "including", "comprising" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. Without further limitation, the element defined by the statement "including one..." does not exclude the existence of another identical element in the process, method, article or device including 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 reverse order according to the functions involved. For example, the described methods may be performed in an order different from that described, and various steps may be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

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

[0408] The embodiments of the present application have been described above with reference to the drawings, but the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not restrictive. Under the inspiration of the present application, those of ordinary skill in the art can also make many forms of embodiments without departing from the purpose of the present application and the scope protected by the claims. These embodiments are all within the protection scope of the present application.

Claims

1. A communication management method, characterized in that, Including: 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, characterized in that, 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, characterized in that, 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 interfaces or suspending the transmission function of part of the interfaces; 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 interfaces, 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, characterized in that The method further includes: The first device automatically resumes at least one of interface transmission and terminal context based on the suspension time information.

7. The method according to claim 1, characterized in that, 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, characterized in that, 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, characterized in that 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, characterized in that, 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, characterized in that, 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 resuming 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: First indication information, which is used to indicate resuming interface transmission; Recovery time information, which is used to indicate the time of transmission of the recovery interface; Recovery reason indication information, which is used to indicate that the power supply link is available or the power supply link has been switched; Recovery type indication information, which is used to indicate the recovery of the transmission function of some interfaces or the recovery of the transmission function of some interfaces.

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

14. The method according to claim 12, wherein The fourth request includes at least one of the following: Recovery 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.

15. The method according to claim 4, 7, 13 or 14, characterized in that 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, characterized in that, 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, characterized in that, The access network device includes at least one of the following: Network elements related to satellites; Store-and-forward type devices; Wherein, 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.

18. The method according to any one of claims 1 to 17, characterized in that The core network device is an on-satellite core network device.

19. A communication management method, characterized in that, Includes: 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 a first request message and a second request message from the first device includes: When the power supply 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.

21. The method according to claim 19 or 20, characterized in that, 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 the suspension of the transmission function of some interfaces or the suspension of the transmission function of some interfaces; 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 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: Suspension start time information; Suspension duration information; Suspension end time information; Time information for the interface to resume transmission.

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

25. The method according to claim 19, characterized in that, The second request message includes at least one of the following: Suspension reason indication information, which is used to indicate that the power feed 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, characterized in that, 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; 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.

27. The method according to any one of claims 19 to 26, characterized in that, 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; 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.

29. The method according to any one of claims 19 to 28, characterized in that, The method further includes: When the power feed link is available, the second device receives 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.

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 resuming interface transmission; Resume time information, which is used to indicate the time for resuming interface transmission; Resume reason indication information, which is used to indicate that the power feed link is available or the power feed link has been switched; Resume type indication information, which is used to indicate resuming the transmission function of some interfaces or resuming the transmission function of some interfaces.

31. The method according to claim 30, wherein When the resume type indication information indicates resuming 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: Resume reason indication information, which is used to indicate that the power feed link has been restored or the power feed link has been switched; Interface information associated with the terminal.

33. The method according to claim 22, 25, 31 or 32, characterized in that, 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, characterized in that, 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: Wherein, the third response is used to indicate agreeing to resume interface transmission; The fourth response is used to indicate agreeing to resume the terminal context.

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

36. The method according to any one of claims 19 to 35, characterized in that, The core network device is an on-board core network device.

37. A communication management device, characterized in that, Includes: 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 device according to claim 37, characterized in that, Further included are: 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 device according to claim 37, characterized in that, 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 device according to claim 39, wherein Further included are: 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, characterized in that, Including: A second receiving module, configured to receive at least one of a first request message and a second request message from the first device by 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.

42. The device according to claim 41, characterized in that, Further included are: 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 device according to claim 41, characterized in that, 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 device according to claim 43, characterized in that, Further included are: 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, characterized in that, Including a processor and a memory, the memory stores 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, characterized in that, A program or instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the steps of the communication management method according to any one of claims 1 to 36 are implemented.

Images