WO2020063192A1 - 一种节点之间链路连接管理的方法及相关设备 - Google Patents

一种节点之间链路连接管理的方法及相关设备 Download PDF

Info

Publication number
WO2020063192A1
WO2020063192A1 PCT/CN2019/101316 CN2019101316W WO2020063192A1 WO 2020063192 A1 WO2020063192 A1 WO 2020063192A1 CN 2019101316 W CN2019101316 W CN 2019101316W WO 2020063192 A1 WO2020063192 A1 WO 2020063192A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
peer network
mobile
mobile node
network node
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2019/101316
Other languages
English (en)
French (fr)
Inventor
杨立
黄河
窦建武
施小娟
高媛
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to US17/279,627 priority Critical patent/US12127281B2/en
Priority to EP19864859.4A priority patent/EP3860301B1/en
Publication of WO2020063192A1 publication Critical patent/WO2020063192A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H04W36/083—Reselecting an access point wherein at least one of the access points is a moving node
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/34—Selective release of ongoing connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/005—Moving wireless networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup

Definitions

  • the embodiments of the present application relate to, but are not limited to, mobile communication system technology, for example, to a method for link connection management between nodes and related equipment.
  • NG-RAN Next Generation Radio Access Network
  • the deployment of each type of NG-RAN (Next Generation Radio Access Network) base station is relatively static and fixed relative to the physical location of a specific latitude and longitude on the ground. Therefore, the wireless coverage / capacity supply of the air interface serving cell provided by the NG-RAN base station and the NG, Xn, F1 related interfaces connecting these NG-RAN base stations are also fixed relative to the physical location.
  • NG, Xn, F1 and other interfaces of TNL (Transport Network Layer) transport bearers most of which are implemented by fixed network methods such as broadband fiber, so the transmission robustness and delay performance of the link are relatively Ok.
  • This fixed land-based cellular mobile network is easier for operators to deploy and resource management, because all network element nodes and network resources can be planned and managed in a (semi) static way.
  • UE user equipment
  • the wireless coverage / capacity supply of air interface service cells provided by these mobile base stations is usually It will change as the physical location of the mobile base station moves, but the TNL transmission bearer of the NG, Xn, F1 interfaces connected to these mobile base stations cannot be fixed, and it cannot be carried by fixed network methods such as broadband optical fiber, usually only Can rely on a variety of wireless bearing methods, such as: microwave, laser, relay and other means.
  • the network constructed by this mobile base station is more flexible in deployment, the network resources and TNL radio bearers can only be planned and managed in a relatively dynamic manner; otherwise, as multiple base stations move, the network topology changes.
  • the quality of the TNL radio bearer is unstable, and each interface related to the mobile base station is likely to be damaged due to changes and interruptions in the TNL radio bearer.
  • various resources on the mobile base station side cannot be efficiently used, and even the UE's services are affected. Forced interruption, etc.
  • related network element nodes need to synchronize and update configurations related to each other in a timely manner, such as wireless coverage information, to ensure smooth end-to-end wireless links.
  • the RNL application layer protocol connections above the TNL such as NGAP (NG Application Application Protocol), XnAP (Xn Application Application Protocol) , Xn interface application process protocol), F1AP (F1 Application Application Protocol) connection, etc. will also undergo corresponding changes and interruptions, so the mobile base station will be connected to the new (old) peer network element node with physical movement , Initiate a more frequent process of establishing Setup and updating the Configuration class, and repeatedly perform the RNL application protocol layer connection instance to establish, unlink, rebuild, and update the configuration, which will cause a large amount of RNL layer signaling And the interface service is interrupted.
  • NGAP NG Application Application Protocol
  • XnAP Xn Application Application Protocol
  • Xn interface application process protocol Xn interface application process protocol
  • F1AP F1 Application Application Protocol
  • An embodiment of the present application provides a method for managing link connections between nodes, including: a first mobile node establishes a Setup process through a network interface, and establishes link connections with multiple peer network nodes, respectively.
  • An embodiment of the present application further provides a first mobile node, including:
  • the establishment unit is configured to establish a Setup process through a network interface, and establish link connections with multiple peer network nodes, respectively.
  • An embodiment of the present application further provides a system for managing link connection between nodes, the system includes:
  • a first mobile node and multiple peer network nodes A first mobile node and multiple peer network nodes
  • the first mobile node is configured to perform a method for managing a link connection between the nodes.
  • An embodiment of the present application further provides a first mobile node, including a memory, a processor, and a computer program stored on the memory and executable on the processor.
  • a computer program stored on the memory and executable on the processor.
  • An embodiment of the present application further provides a computer-readable storage medium, where the computer-readable storage medium stores an information processing program, and the method for implementing the link connection management between the nodes when the information processing program is executed by a processor .
  • FIG. 1 is an architecture diagram of an aggregated NG-RAN aggregated base station CU / DU air interface protocol stack without separation;
  • FIG. 2 is an architecture diagram of a disaggregated NG-RAN separated base station gNB CU / DU air interface protocol stack;
  • Figure 3 shows the NG interface establishment process between a traditional NG-RAN base station and AMF
  • 4 is a NG interface configuration update process initiated by a NG-RAN side between a traditional NG-RAN base station and an AMF;
  • FIG. 5 is an NG interface configuration update process initiated by an AMF side between a conventional NG-RAN base station and an AMF;
  • FIG. 6 is a schematic flowchart of a method for managing a link connection between nodes according to Embodiment 1 of the present application;
  • FIG. 7a is a schematic diagram of multiple connections of NG interfaces between network nodes provided in Embodiment 2 of the present application; FIG.
  • FIG. 7b is a schematic diagram of multiple connections of F1 interfaces between network nodes provided in Embodiment 2 of the present application;
  • FIG. 7c is a schematic diagram of multiple connections of Xn interfaces between network nodes provided in Embodiment 2 of the present application.
  • FIG. 8a is a schematic diagram of a FU-type satellite communication system architecture provided in Embodiment 3 of the present application.
  • FIG. 8b is a schematic diagram of a FU-type satellite moving across regions of different ground stations AMF provided in Embodiment 3 of the present application;
  • 8c is a schematic diagram of multiple connections between a FU satellite and multiple ground stations AMF provided in Embodiment 3 of the present application;
  • FIG. 9a is a schematic diagram of a DU-type satellite communication system architecture provided in Embodiment 4 of the present application.
  • 9b is a schematic diagram of a DU-type satellite moving across regions of different ground stations gNB-CU provided in Embodiment 4 of the present application;
  • 9c is a schematic diagram of multiple connections between a DU satellite and multiple ground stations gNB-CU provided in Embodiment 4 of the present application;
  • 10a is a schematic diagram of an aerial drone base station communication system architecture provided in Embodiment 5 of the present application.
  • 10b is a schematic diagram of a drone base station moving across areas of different ground stations AMF provided in Embodiment 5 of the present application;
  • FIG. 10c is a schematic diagram of multiple connections between a UAV base station and multiple ground stations AMF provided in Embodiment 5 of the present application; FIG.
  • FIG. 11 is a schematic structural diagram of a first mobile node provided in Embodiment 6 of the present application.
  • FIG. 12 is a schematic structural diagram of a system for link connection management between nodes provided in Embodiment 7 of the present application.
  • the fourth-generation 4G (4Generation) or Long-Term Evolution (LTE) land-based cellular mobile communication system includes a 4G core network, that is, an Evolved Packet Core (EPC) and a wireless access network (Radio Access Network, RAN) two major subsystems.
  • EPC Evolved Packet Core
  • RAN Radio Access Network
  • 4G EPC includes MME (Mobility Management Entity, Mobility Management Entity Node), SGW (Serving Gateway, Serving Gateway Node), PGW (PDN Gateway, PDN Gateway Node) and other basic network element nodes
  • 4G RAN includes long-term evolution base station eNB ( evolved NodeB) and the relevant base station network element.
  • the 5G (Fifth Generation) (fifth generation mobile communication) land-based cellular mobile communication system after 4G also includes the next generation core network 5GC (5 Generation Core, 5G core network) and the next generation wireless access network NG-RAN ( Next Generation (Radio Access Network).
  • 5GC Next Generation Core
  • NG-RAN Next Generation (Radio Access Network).
  • 5GC includes network element nodes such as AMF (Access, Mobility Function, Access Management Function Node), SMF (Session Management Function, Session Management Function Node) and UPF (User Plane Function, User Plane Function Node), and NG-RAN contains at least Two different radio access standard RAT type base stations, namely: ng-eNB based on 4G eNB (the air interface still supports E-UTRA RAT system), and gNB (air interface supports NR (New Radio) , New wireless system) RAT system) base station, and related base station network element interfaces.
  • AMF Access, Mobility Function, Access Management Function Node
  • SMF Session Management Function, Session Management Function Node
  • UPF User Plane Function, User Plane Function Node
  • NG-RAN contains at least Two different radio access standard RAT type base stations, namely: ng-eNB based on 4G eNB (the air interface still supports E-UTRA RAT system), and gNB (air interface supports NR (New Radio)
  • Figure 1 shows the architecture of an aggregated base station (such as Aggregated NG-RAN) in the case where the CU (Centralized Unit) and DU (Distributed Unit) air interface protocol stacks are not separated.
  • the NG-RAN base station gNB or ng-eNB
  • the connection between NG-RAN base station and 5GC includes NG-C (Next Generation-Control Plane, 5G core network element control plane connection) control plane (signaling) connection and NG-U (Next Generation-User Plane, 5G core Network element user plane connection) User plane (user data) connection.
  • NG-C Next Generation-Control Plane, 5G core network element control plane connection
  • NG-U Next Generation-User Plane, 5G core Network element user plane connection
  • User plane user data
  • NG-RAN base stations (gNB or ng-eNB) are connected to each other through an Xn interface.
  • the connection methods between NG-RAN base stations include Xn-C (Xn-Control Plane, control plane connection between NG-RAN base stations) control plane connection and Xn-U (Xn-User Plane, user plane connection between NG-RAN base stations) User plane connection.
  • FIG. 2 is an architecture diagram of a separated base station gNB (such as Disaggregated NG-RAN) when the CU / DU air interface protocol stack is separated. Taking the currently supported gNB separation as an example, as shown in Figure 2, a single gNB is separated into a single gNB-CU and multiple gNB-DU network element node entities.
  • a standardized F1 interface is used between gNB-CU and gNB-DU. Connected to each other.
  • the connection methods based on the F1 interface include F1-C control plane connection and F1-U user plane connection.
  • the external interfaces of the gNB and the non-isolated gNB are still NG and Xn interfaces.
  • the control plane (CP, Control Plane) connection of the above-mentioned multiple types of interfaces is set to transmit control signaling messages between network element nodes, and the user plane (UP, User Plane) connection is set to transmit user service data (packets).
  • NGAP, XnAP, and F1AP are NG-C (Next Generation-Control Plane, 5G core network element control plane connection), Xn-C (Xn-Control Plane, NG-RAN control plane connection between base stations), F1-C control plane Application layer protocol of RNL (Radio Network Layer), the above application layer protocol is based on TNL (Transport Network Layer) transport bearer (SCTP (Streaming Control Transport Protocol) connection) to transmit correspondence Interface control signaling; NG-U (Next Generation-User Plane, 5G core network element user plane connection), Xn-U (Xn-User Plane, NG-RAN user plane connection between base stations), F1-U user plane
  • the interface user data frame is based on a TNL transmission bearer (GTP-U (GPRS Tunneling Protocol) tunnel) to transmit user data of the corresponding interface.
  • GTP-U GPRS Tunneling Protocol
  • NG interface As an example, and the principles of the Xn and F1 interfaces are basically similar.
  • a single NG-RAN base station and its internal local serving cell from the perspective of actual deployment and use, usually only need to connect to a single peer AMF entity through a single NG-C interface NGAP, which is called the base station / Serving AMF for the serving cell.
  • the NG setup process of the NG interface enables the NG-RAN base station to actively initiate the establishment of the NGAP connection with the peer serving AMF, and the initial local configuration information of the interactive nodes, such as node-level and cell-level capabilities and Configuration related information, configuration and identification of the local serving cell / tracking area, etc.
  • the initial local configuration information of the interactive nodes such as node-level and cell-level capabilities and Configuration related information, configuration and identification of the local serving cell / tracking area, etc.
  • Figure 4 If any local configuration information of the NG-RAN base station is updated, it can be initiated through the RAN Configuration Update process and the NGAP configuration update of the serving AMF.
  • FIG. 5 if any local configuration information of the AMF is updated, it can be initiated through the AMF Configuration Update process and the NGAP configuration update of the NG-RAN base station.
  • a single NG-RAN base station / serving cell needs to connect to another new Serving AMF, the NGAP connection and related port resources of the original Serving AMF are usually deleted first, and the new Serving AMF is re-assigned to the new Serving AMF. Initiate the NG Setup process.
  • This "top-down tree topology" is sufficient for traditional land-based cellular mobile networks, because the specific local serving cell resources within a single NG-RAN base station usually need only be governed by a single serving AMF. Similar in principle, the resources of a specific local serving cell in a single gNB-DU entity usually need only be governed by a single serving gNB-CU entity.
  • Xn interface can support XnAP connection of a single NG-RAN base station / serving cell and multiple adjacent NG-RAN base stations / serving cells at the same time, XnAP connection also needs to correspond to the process of establishing Setup and configuration update Configuration Update class.
  • the base station initiates more frequent Setup and Configuration update processes, and iteratively repeatedly executes the RNL application protocol layer connection instances to establish, unlink, and rebuild the chain and Operations such as configuration updates will cause a large number of RNL layer signaling and interface service interruptions.
  • this application proposes the concept of multiple connections between network element entities (nodes), so that in the network environment constructed by mobile base stations, mobile network element nodes (serving cells) and peer network element nodes can be efficiently established and maintained.
  • the TNL transmission bearer is connected to the upper RNL application protocol layer, so as to ensure that the network NG, F1, Xn and other interfaces can match and adapt to the dynamic topology change of the mobile base station in time, and minimize the inaction of the NG, F1, and Xn interfaces.
  • TNL / RNL layer interface reconstruction and interface service interruption improve the system's utilization of mobile base station resources.
  • FIG. 6 is a schematic flowchart of a method for managing a link connection between nodes according to the first embodiment of the present application. As shown in Figure 6, the method includes the following steps:
  • Step 601 The first mobile node establishes a Setup process through a network interface, and establishes link connections with multiple peer network nodes, respectively.
  • the link connection includes at least one of the following: a control plane signaling connection and a user plane data connection.
  • the link connection may include: a control plane signaling connection (set to transmit control signaling messages, etc.) and a user plane data connection (set to transmit service data packets, etc.).
  • the first mobile node establishing a link connection with multiple peer network nodes through a network interface establishment setup process includes:
  • Each local cell set initiates a link connection setup setup process with at least two peer network nodes of the plurality of peer network nodes through a corresponding network interface, and exchanges respective configuration information.
  • cells in the same local cell set have the same management attributes, and different instinctual cell sets have different management attributes.
  • the configuration information includes at least one of the following: local capabilities of the local cell set, resource configuration of the local cell set, and radio coverage related information of the local cell set.
  • the configuration information includes information such as local capabilities and resource configurations of the local cell (set), and information related to wireless coverage.
  • the method further includes:
  • Different local cell sets of the multiple local cell sets are under the jurisdiction of different peer network nodes
  • the same local cell set in the multiple local cell sets is administered simultaneously by different peer network nodes.
  • different sets of local cells of the first mobile node may be managed by different peer network nodes; or the same set of local cells of the first mobile node may also be managed by different peer network nodes at the same time. .
  • the method further includes:
  • the first mobile node and The second link connection between the second peer network nodes is in an activated state, and the other mobile network of the first mobile node and the plurality of peer network nodes except for the second peer network node
  • the other link connections between the nodes are in a deactivated state, and the first mobile node is under the jurisdiction of the second peer network node.
  • the method further includes:
  • the first mobile When at least one local cell set subordinate to the first mobile node enters within a first coverage tracking area managed by a first peer network node among the plurality of peer network nodes, the first mobile is activated A first link connection established between the node and the first peer network node, at this time, the first mobile node and the at least one local cell set subordinate to the first mobile node belong to the second peer network node and all The first peer network node is under common jurisdiction.
  • the activating a first link connection established between the first mobile node and a first peer network node includes:
  • the first mobile node initiates a transport-layer TNL link association, initiates a node configuration update Configuration Update process to the first peer network node, and sends a connection to the first peer network node through a first link connection established with the first peer network node.
  • the first peer network node notifies information of the at least one local cell set that has entered the range of the first coverage tracking area and the at least one local cell set subordinate to the first mobile node.
  • the information of the at least one local cell set subordinate to the first mobile node may refer to all or part of the local cells subordinate to the first mobile node that have entered the range of the first coverage tracking area.
  • the set of identification information for example, the identification information may be a cell ID or a cell set ID.
  • the method further includes:
  • the first mobile node initiates a node configuration update Configuration Update process to the second peer network node, and sends the node configuration update procedure to the second peer network node through a second link connection established with the second peer network node.
  • the information of the local cell set subordinate to the first mobile node other than the at least one local cell set may refer to a subordinate of the first mobile node that is still within a second coverage tracking area. All or part of the identification information of the local cell set, for example, the identification information may be a cell ID or a cell set ID.
  • the method further includes:
  • the association of the transport layer TNL link is temporarily closed, thereby deactivating the second link connection.
  • the first mobile node and the local cell set owned by its subordinates are under the jurisdiction of the first peer network node only.
  • the deactivating the second link connection includes:
  • the first mobile node initiates a node configuration update Configuration Update process to the second peer network node, and sends the node configuration update procedure to the second peer network node through a second link connection established with the second peer network node. Notifying all local cell sets subordinate to the first mobile node to leave the second coverage tracking area, but the second peer network node still maintains configuration context information of the interface link connection, pending the first The mobile node subsequently initiates the transport layer TNL link association again.
  • the method further includes:
  • a mobile handover procedure is triggered at the first UE to switch from a first local cell set subordinate to the first mobile node to a second local cell set subordinate to a second mobile node, and the first local cell set and the second local cell set
  • the radio access layer communication context UE ASContext of the first UE is removed from the The first mobile node transfers to the second mobile node, and always maintains and maintains the UE non-radio access layer communication context UE and NAS context in the first peer network node.
  • the method further includes:
  • the first peer network node When the first UE stays within the first coverage tracking area under the jurisdiction of the first peer network node, the first peer network node always keeps the non-radio access layer communication context UE NAS context of the first UE; only when When the first UE moves outside the first coverage tracking area under the jurisdiction of the first peer network node, the target peer network node saves the migrated UE NAS Context.
  • the first peer network node when the first UE stays within the first coverage and tracking area under the jurisdiction of the first peer network node, the first peer network node always keeps the UE NAS context; only when the first UE moves to the first Outside the first coverage tracking area under the jurisdiction of the peer network node, the new target peer network node attempts to save the migrated UE NAS context.
  • the mobile node is a mobile NG-RAN base station
  • the peer network node is a 5GC network node
  • the link connection is an NGAP connection instance
  • the mobile node is a mobile NG-RAN base station
  • the peer network node is a mobile NG-RAN base station
  • the link connection is an XnAP connection instance
  • the mobile node is a distributed processing unit DU
  • the peer network node is a centralized processing unit CU
  • the link connection is an F1AP connection instance.
  • the 5GC network node is one of the following: an access management function node AMF, a session management function node SMF, and a user plane function node UPF;
  • the mobile NG-RAN base station is one of the following: ng-eNB, which continues to evolve based on 4G eNBs, gNB with a new physical layer air interface design, LEO earth low-orbit satellites equipped with Full gNB functions, and Human-machine base station
  • the centralized processing unit CU in the mobile NG-RAN base station is: NG-RAN separated base station gNB-CU;
  • the distributed processing unit DU in the mobile NG-RAN base station is one of the following: the NG-RAN separated base station gNB-DU and the LEO earth low-orbit satellite equipped with the gNB-DU function.
  • FIG. 7a is a schematic diagram of multiple connections of NG interfaces between network nodes provided in Embodiment 2 of the application;
  • FIG. 7b is a schematic diagram of multiple connections of F1 interfaces between network nodes provided in Embodiment 2 of the application;
  • FIG. 7c is provided by Embodiment 2 of this application Schematic diagram of multi-connection of Xn interface between network nodes.
  • NG-RAN base station 1 mobile node
  • the TNL transmission bearer and the upper-level RNL and NGAP connections between it and other network element nodes are prone to change. Or was disrupted by interruption.
  • 5GC peer network element node collections they are fixed or stationary on the ground by default. They are the counterparts for each mobile NG-RAN base station to establish a TNL transmission bearer and an upper layer NGAP connection.
  • the base station 1 first divides all the local serving cells in itself into a plurality of local cell sets 1, 2, ..., n.
  • a special case of the local cell set is a local serving cell, that is, each local cell set includes only one local serving cell.
  • the base station 1 may re-divide the local cell set to which the local serving cell belongs.
  • the base station 1 has a certain positioning function, and can understand the relationship between the base station 1 itself and the coverage of the local serving cell and the ground plan coverage area.
  • Each local cell set can establish and maintain different NGAP connections with multiple AMF nodes simultaneously, so it can be managed (managed) by multiple AMF nodes at the same time.
  • Different sets of local cells can independently establish and maintain NGAP connections with different sets of AMF entities.
  • the port corresponding to local cell set 1 and AMF1 and AMF2 each establish an independent TNL transmission bearer and an upper-layer NGAP connection.
  • the configuration information of local cell set 1 or AMF 1 or AMF2 in particular: the local serving cell
  • the port corresponding to the local cell set 2 and AMF2 and AMFx each establish an independent TNL transmission bearer and an upper layer NGAP connection.
  • the configuration information of the local cell set 2 or AMF 2 or AMFx changes, they can communicate with each other through the NG interface Configuration Update class process update.
  • the configuration information of the local cell set n or AMF 2 or AMFn changes, they can communicate with each other through the NG interface Configuration Update Class process updates.
  • Each NGAP connection has three real-time states: established (activated), deleted, and deactivated.
  • the establishment indicates that the NGAP connection has been established and is in a normal working state, and can transmit NGAP process messages.
  • Deactivation means that although the NGAP connection is established, the NGAP process messages cannot be transmitted for the time being. Both nodes on the opposite end of the NGAP communication temporarily save the old NGAP connection configuration and the corresponding port resources are not deleted.
  • Deletion means that the two nodes on the opposite end of the NGAP communication delete the old NGAP connection configuration and corresponding port resources.
  • gNB-DU1 mobile node
  • the TNL transmission bearer and the upper-level RNL and F1AP connections between it and other network element nodes are prone to occur. Change or disruption.
  • gNB-CU peer network element node collections are fixed or stationary on the ground by default. Each mobile gNB-DU needs to establish the TNL transmission bearer and the peer object of the upper layer NGAP connection.
  • gNB-DU1 first divides all local serving cells in itself into multiple local cell sets 1, 2, ..., n.
  • a special case of the local cell set is a local serving cell, that is, each local cell set includes only one local serving cell.
  • gNB-DU1 can re-divide the local cell set to which the local serving cell belongs.
  • gNB-DU1 has a certain positioning function, and can understand the relationship between gNB-DU1 itself and the coverage of the local service cell and the coverage area of the ground plan.
  • Each local cell set can simultaneously establish and maintain different F1AP connections with multiple gNB-CU nodes, so it can be managed by multiple gNB-CU nodes simultaneously.
  • Different sets of local cells can independently establish and maintain F1AP connections with different sets of gNB-CU entities.
  • the ports corresponding to local cell set 1 and gNB-CU1 and gNB-CU2 each establish an independent TNL transmission bearer and an upper-layer F1AP connection.
  • the configuration information of local cell set 1 or gNB-CU1 or gNB-CU2 In particular, the geographic location covered by the local service cell changes, and the re-association information with different ground planning coverage areas can be updated with each other through the F1 interface Configuration Update class process.
  • the port corresponding to the local cell set 2 and gNB-CU2 and gNB-CUx each establish an independent TNL transmission bearer and an upper-layer F1AP connection.
  • Each F1AP connection has three real-time states: established (activated), deleted, and deactivated.
  • the establishment indicates that the F1AP connection has been established and is in a normal working state, and can transmit F1AP process messages.
  • Deactivation means that although the F1AP connection has been established, F1AP process messages cannot be transmitted for the time being. Both nodes on the opposite end of the F1AP communication temporarily save the old F1AP connection configuration and the corresponding port resources are not deleted.
  • Deletion means the two nodes on the opposite end of the F1AP communication delete the old F1AP connection configuration and the corresponding port resources.
  • NG-RAN base station 1 mobile node
  • the TNL transmission bearer between it and other network element nodes and the upper layer RNLXnAP connection are easy Changes or disruptions.
  • base station peer network element node collections are fixed or stationary on the ground by default. Each mobile NG-RAN base station needs to establish a TNL transmission bearer and a peer object of the upper layer XnAP connection.
  • the base station 1 first divides all the local serving cells in itself into a plurality of local cell sets 1, 2, ..., n.
  • a special case of the local cell set is a local serving cell, that is, each local cell set includes only one local serving cell.
  • the base station 1 may re-divide the set to which the local serving cell belongs.
  • the base station 1 has a certain positioning function, and can understand the relationship between the base station 1 itself and the coverage of the local serving cell and the ground plan coverage area.
  • Each local serving cell set can establish and maintain different XnAP connections with multiple neighboring base station nodes simultaneously.
  • Different sets of local serving cells can independently establish and maintain XnAP connections with different sets of neighboring base station entities, so they are associated with multiple neighboring base station nodes simultaneously.
  • the port corresponding to the local cell set 1 and the neighboring base station 1 and the neighboring base station 2 respectively establish independent TNL transmission bearers and upper-layer XnAP connections.
  • the configuration information of 2 in particular: the geographical location covered by the local service cell changes, and the re-association information of different ground planning coverage areas can be updated with each other through the Xn interface Configuration update process.
  • the port corresponding to the local cell set 2 and the neighboring base station 2 and the neighboring base station x each establish an independent TNL transmission bearer and an upper-layer XnAP connection.
  • the configuration information changes, and can be updated with each other through the Xn interface Configuration and Update class processes.
  • an independent TNL transmission bearer and an upper layer XnAP connection are respectively established.
  • the configuration information changes, and can be updated with each other through the Xn interface Configuration and Update class processes.
  • Each XnAP connection has three real-time states: established (activated), deleted, and deactivated.
  • the establishment indicates that the XnAP connection has been established and is in a normal working state, and can transmit XnAP process messages.
  • Deactivation means that although the XnAP connection is established, the XnAP process messages cannot be transmitted for the time being. Both nodes on the opposite end of the XnAP communication temporarily save the old XnAP connection configuration and the corresponding port resources are not deleted.
  • Deletion means the two nodes on the opposite end of the XnAP communication delete the old XnAP connection configuration and the corresponding port resources.
  • the local cell set includes only one cell, that is, one cell is a local cell set;
  • the first mobile node is a mobile NG-RAN base station, and the mobile NG-RAN base station is equipped with a Full NB function.
  • LEO earth low orbit satellite the opposite network node is an access mobile function node AMF;
  • the link connection between the first mobile node and the opposite network node is an NG interface connection.
  • FIG. 8a is a schematic diagram of a FU-type satellite communication system architecture provided in Embodiment 3 of the present application.
  • FU-type satellite communication system a plurality of LEO earth low-orbit satellites are equipped with Full gNB functions, and they are in space. Orbits around the Earth in a specific orbit.
  • a terminal UE on the ground (assuming quasi-stationary on the ground and in RRC connection state) is currently in the ground planning coverage area 1 under the jurisdiction of AMF1.
  • the UE's current serving cell is the cell 1 under the jurisdiction of satellite 1.
  • LEO satellites each establish a NG interface connection with the AMF / SMF / UPF in the ground station 5GC collection through the Feeder link (feeder link), including NG-C signaling NGAP connection and NG-U data connection.
  • satellite 1 is currently connected to ground station AMF1
  • satellite 2 is connected to ground station AMF2 (Note: in some spatial locations, satellite 1/2 may also be connected to the same One ground station AMF).
  • the multiple service cells 8,7,6,5 under the jurisdiction of satellite 2 will gradually leave the ground plan coverage area 2 and move into the ground plan coverage area 1, such as As shown in Figure 8b: cell 8 has moved from the original old coverage area 2 to the new coverage area 1 under the jurisdiction of AMF1.
  • the cell 4 of satellite 1 below has also moved out of the original old coverage area 1 accordingly.
  • the UE when the UE detects that the service signal of the old cell 1 is getting weaker and the service signal of the new cell 8 is getting stronger, the UE will trigger the network to perform the mobile handover procedure. An attempt is made to switch the UE from the old serving cell 1 to the new serving cell 8. The result of the successful handover is that on the NG-RAN access network side, the UE wireless access layer communication context (UE, AS context) is transferred from satellite 1 to satellite 2, and on the 5GC core side, the UE non-radio access layer communication context (UE NAS context) temporarily transferred from AMF1 to AMF2 (because satellite 2 has been under the jurisdiction of AMF2).
  • UE wireless access layer communication context UE, AS context
  • the UE non-radio access layer communication context UE non-radio access layer communication context
  • satellite 2 After a period of time, when satellite 2 moves completely to the center of coverage area 1 (at this time, the position of satellite 2 is similar to that of satellite 1 in FIG. 8a), at this time satellite 2 will initiate NG to the new ground station AMF1
  • the interface establishment process while deleting the NG interface with the old ground station AMF2 at the same time, so that the cells 5, 6, 7, 8 under the jurisdiction of satellite 2 are used to cover the coverage area 1.
  • the anchor core network element of satellite 2 is AMF2-> AMF1Relocation
  • the UENAS context needs to be transferred from AMF2 to AMF1 again, which causes The roundabout transfer of UE non-radio access layer communication context between UE and NAS context between different ground stations AMF
  • Embodiment 3 of the present application proposes a new scheme for connection management between nodes.
  • the scheme includes:
  • Step 801 Initially, each satellite, for example, satellite 2 and multiple different ground stations AMF1 and AMF2, establish their respective NGAP connections in advance, and mutually interact with each other's local service cell capability configuration information through the NG Setup process.
  • the serving cell capability configuration information includes: association information between the current local serving cell coverage and coverage areas of different ground plans. When satellite 2 is completely over the center of ground plan coverage area 2, then cells 5, 6, 7, 8 are all only associated with coverage area 2, so they are all under the jurisdiction of AMF2, so satellite 2 can only maintain and anchor
  • the NGAP connection of AMF2 is activated, but the NGAP connection with AMF1 can be temporarily deactivated.
  • Step 802 when satellite 2 enters the boundary area of the AMF across different ground stations, the NGAP connection between satellite 2 and AMF1 can be reactivated.
  • satellite 2 informs AMF2 through the RAN Configuration Update process: 8 has left coverage area 2, and the remaining cells 5, 6, and 7 are still in coverage area 2.
  • satellite 2 also informs AMF1 through the RAN Configuration Update process that cell 8 has entered coverage area 1; the same Satellite 1 will also inform AMF1 through the RAN Configuration Update process: Cell 4 has left coverage area 1, and the remaining cells 1, 2, and 3 are still in coverage area 1.
  • AMF1 can know that cell 8 has entered coverage area 1 under its jurisdiction and can be under the jurisdiction of AMF1.
  • the NG-RAN access network side It is only necessary to transfer the UE ASContext from satellite 1 to satellite 2, but on the 5GC core side, the UE NAS context does not need to be transferred from AMF1 to AMF2, that is, the UE NAS context continues to remain in AMF1.
  • cell 8 leaves coverage area 2 and enters coverage area 1, it is a continuous gradual process. Therefore, there is a transition period. Cell 8 crosses coverage area 2 and coverage area 1 at the same time. Therefore, cell 8 can also work with two coverage areas 1. It is associated with 2 at the same time, and is jointly under the jurisdiction and use of AMF1 and AMF2.
  • Step 803 as satellite 2 continues to move downward along the orbit, cells 7, 6, and 5 gradually leave coverage area 2 and enter coverage area 1. Satellite 2 will continue to inform AMF2 through the RAN Configuration Update process: the latest Re-association information between the local serving cell and coverage area 2; meanwhile, satellite 1 will continue to inform AMF1 through the RAN configuration update process: the latest re-association information between the local serving cell and coverage area 1. Therefore, even when the UE triggers the mobile handover procedure again in the old serving cell, the UE AS context can always be stored in satellite 2 on the NG-RAN access network side, and the UE NAS context can always be kept in AMF 1 on the 5GC core side. Inside.
  • Step 804 as shown in FIG. 8c, as satellite 2 continues to move downward along the orbit, the uppermost cell 5 also leaves coverage area 2 and enters coverage area 1. At this time, satellite 2 is basically in coverage area 1. The location above the center of the cell, cells 5, 6, 7, 8 are all only associated with coverage area 1, so they can all be under the jurisdiction of AMF1. At this time, satellite 2 can also initiate NGAP connection deactivation to AMF2 through the RAN Configuration Update process, that is, satellite 2 only keeps NGAP connection activation with AMF1, which returns to the initial state similar to satellite 1 in Figure 8a.
  • the solution in the third embodiment of the present application can avoid the roundabout transfer of the UE NAS context between different anchor ground stations AMF, thereby reducing the related UE handover process signaling and alleviating the adverse impact on user service interruption.
  • the local cell set includes only one cell, that is, one cell is a local cell set;
  • the first mobile node is a LEO earth low-orbit satellite equipped with a gNB-DU function;
  • the peer network node is a gNB CU;
  • the link connection between the first mobile node and the opposite network node is an F1 interface connection.
  • FIG. 9a is a schematic diagram of a DU-type satellite communication system architecture provided in Embodiment 4 of the present application.
  • multiple LEO earth low-orbit satellites are loaded with gNB-DU functions.
  • a terminal UE on the ground (assuming quasi-stationary on the ground and in RRC connection state) is currently in the ground plan coverage area 1 under the jurisdiction of gNB-CU1.
  • the UE's current serving cell is cell 1 under the jurisdiction of satellite 1.
  • UE Through Service Link and Space DU Satellite 1 direct wireless communication, and LEO satellites respectively establish F1 interface connections with the gNB-CU in the gNB-CU set of ground stations through the Feeder link, including F1-C signaling F1AP connection and F1-U data connection.
  • satellite 1 is currently connected to the ground station gNB-CU1
  • satellite 2 is connected to the ground station gNB-CU2
  • satellite 1/2 also has (May be connected to the same ground station gNB-CU).
  • the multiple service cells 8,7,6,5 under the jurisdiction of satellite 2 will gradually leave the ground plan coverage area 2 and move into the ground plan coverage area 1, such as As shown in FIG. 9b: cell 8 has moved from the original old coverage area 2 to the new coverage area 1 under the jurisdiction of gNB-CU1.
  • the cell 4 of satellite 2 below has also moved out of the original old coverage area 1 accordingly.
  • the UE wireless DU context (UE AS-DU Context) is transferred from satellite 1 to satellite 2 while the UE wireless CU context (UE AS-CU Context) is temporarily changed from gNB -CU1 is transferred to gNB-CU2 (because satellite 2 is always under the jurisdiction of gNB-CU2).
  • satellite 2 After a period of time, when satellite 2 moves completely to the center of coverage area 1 (at this time, the position of satellite 2 is similar to that of satellite 1 in Figure 9a), at this time satellite 2 will initiate a call to the new ground station gNB-CU1.
  • the F1 interface establishment process, and the F1 interface of the old ground station gNB-CU2 is deleted at the same time, so that the cells 5, 6, 7, 8 under the jurisdiction of satellite 2 are used to cover the coverage area 1.
  • the anchor gNB-CU network element gNB-CU2-> gNB-CU1 of satellite 2 is relocated (gNB-CU Relocation) at this time, although satellite 2 can continue to retain the UE AS-DU context, the UE AS-CU context also needs Then re-transfer from gNB-CU2 back to gNB-CU1, which causes a roundabout transfer of UE wireless CU context UE AS-CU context between different ground stations gNB-CU.
  • Embodiment 4 of the present application proposes a new scheme for connection management between nodes.
  • the scheme includes:
  • Step 901 Initially, each satellite, for example, satellite 2 and multiple different ground stations gNB-CU1 and gNB-CU2, establish their respective F1AP connections in advance, and mutually interact with each other through the F1Setup process to configure the capabilities of their respective local service cells Information, etc.
  • the local serving cell capability configuration information includes: association information between the current local serving cell coverage and coverage areas of different ground plans. In the case where satellite 2 is completely over the center of ground plan coverage area 2, at this time, cells 5, 6, 7, 8 are all only associated with coverage area 2, so they are all under the jurisdiction of gNB-CU2, so satellite 2 can only be
  • the F1AP connection to the anchor gNB-CU2 remains active, but the F1AP connection to gNB-CU1 can be temporarily deactivated.
  • Step 902 in the case where satellite 2 enters the boundary area of gNB-CU across different ground stations, the F1AP connection between satellite 2 and gNB-CU1 can be reactivated.
  • satellite 2 passes gNB-DU The Configuration Update process informs gNB-CU2 that cell 8 has left coverage area 2, and the remaining cells 5, 6, and 7 are still in coverage area 2.
  • satellite 2 also sends the gNB-DU configuration update procedure to gNB- CU1 informs that cell 8 has entered coverage area 1; the same reason satellite 1 will also inform AMF1 through the gNB-DU configuration update process: cell 4 has left coverage area 1, and the remaining cells 1, 2 and 3 are still in place In coverage area 1.
  • gNB-CU1 can learn that cell 8 has entered coverage area 1 under its jurisdiction and can be under the jurisdiction of gNB-CU1 itself. Therefore, when the UE triggers the mobile handover procedure in old serving cell 1, On the access network side, it is only necessary to transfer the UE AS-DU context from satellite 1 to satellite 2.
  • the UE AS-CU context does not need to be transferred from gNB-CU1 to gNB-CU2, that is, the UE AS-CU context remains at gNB-CU1.
  • cell 8 leaves coverage area 2 and enters coverage area 1, it is a continuous gradual process. Therefore, there is a transition period. Cell 8 crosses coverage area 2 and coverage area 1 at the same time. Therefore, cell 8 can also work with two coverage areas 1. It is associated with 2 at the same time, and is jointly under the jurisdiction and use of gNB-CU1 and gNB-CU2.
  • Step 903 as satellite 2 continues to move downward along the orbit, cells 7, 6, and 5 gradually leave coverage area 2 and enter coverage area 1, and satellite 2 will continue to gNB-DU through the gNB-DU ConfigurationUpdate process.
  • CU2 informs: the latest re-association information between the local serving cell and coverage area 2; meanwhile, satellite 1 will continue to inform gNB-CU1 through the gNB-DU Configuration Update process: the re-association between the latest local serving cell and coverage area 1 information. Therefore, even when the UE triggers the mobile handover procedure again in the old serving cell, the UE AS-DU Context can always be stored in satellite 2 on the NG-RAN access network side, and the UE AS-CU Context can always be kept in gNB-CU1.
  • the UE AS-DU Context can always be stored in satellite 2 on the NG-RAN access network side, and the UE AS-CU Context can always be kept in gNB-CU1.
  • the UE AS-CU Context can be always It is maintained in gNB-CU1, which avoids circuitous relocation of gNB-CU anchors caused by continuous switching of serving satellites.
  • Step 904 as shown in FIG. 9c, as satellite 2 continues to move downward along the orbit, the uppermost cell 5 also leaves coverage area 2 and enters coverage area 1. At this time, satellite 2 is basically in coverage area 1. The location above the center of the cell, cells 5, 6, 7, 8 are all only associated with coverage area 1, so they can all be under the jurisdiction of gNB-CU1. At this time, satellite 2 can also initiate F1AP connection deactivation to gNB-CU2 through the gNB-DU configuration update process, that is, satellite 2 only keeps the F1AP connection activated with gNB-CU1, which returns to the initial state similar to satellite 1 in Figure 9a.
  • the solution provided in the fourth embodiment can avoid the roundabout transfer of the UE AS-CU context between different anchor ground stations gNB-CU, thereby reducing the related UE handover process signaling and alleviating the adverse impact on user service interruption.
  • the local cell set includes only one cell, that is, a cell is a local cell set;
  • the first mobile node is a drone base station equipped with a Full gNB function; and the peer network node is an access mobile function node AMF;
  • the link connection between the first mobile node and the peer network node is an NG interface connection.
  • FIG. 10a is a schematic diagram of an aerial drone base station communication system architecture provided in Embodiment 5 of the present application.
  • the drone base station 1 In the airborne drone base station communication system, the drone base station 1 is loaded with a Full gNB function, which moves along a random trajectory in the sky.
  • the UAV base station 1 establishes an NG interface connection with the AMF / SMF / UPF in the ground station 5GC set through the Feeder link, including NG-C signaling NGAP connection and NG-U data connection.
  • the four local service cells 1, 2, 3, and 4 of the drone base station 1 in FIG. 10a cover the ground plan coverage area 1.
  • a quasi-static terminal UE in the RRC idle state
  • the drone base station 1 temporarily is located in the ground plan coverage area 2. Therefore, paging and direct communication cannot be performed by the drone base station 1 temporarily. (Also, the UE can also be served by other UAV base stations at the same time, but it is not shown in Figure 10a).
  • the drone base station 1 is currently connected to the anchor ground station AMF1.
  • the multiple serving cells 1, 2, 3, and 4 under the jurisdiction of the drone base station 1 will gradually leave the ground plan coverage area 1 and move into the ground plan coverage area 2.
  • the cells 1 and 2 have moved from the original old coverage area 1 to the new coverage area 2 under the jurisdiction of AMF2.
  • AMF2 needs to know which drone base stations and its local serving cells can serve UEs in coverage area 2; otherwise, AMF2 will trigger NG when the UE has downlink signaling / data arrival.
  • AMF2 cannot find a suitable UAV base station to undertake the air interface paging task. Therefore, when the UAV base station 1 moves to a new coverage area, it is necessary to re-associate the coverage of the local serving cell and the coverage area in time, and update the report to the AMF to synchronize the wireless network link available from end to end.
  • Embodiment 5 of the present application proposes a new scheme for connection management between nodes.
  • the scheme includes:
  • Step 1001 Initially, each drone base station, such as drone base station 1 and multiple different ground stations AMF1 and AMF2, establish their respective NGAP connections in advance, and mutually interact with each other through the NG Setup process. Capability configuration information, etc.
  • the capability configuration information of the local serving cell includes: association information between the current coverage of the local serving cell and coverage areas of different ground plans. In the case where the drone base station 1 is completely over the center of the ground plan coverage area 1, at this time, all the cells 1, 2, 3, and 4 are only associated with the ground plan coverage area 1, so they are all under the jurisdiction of AMF1. Human-machine base station 1 can only keep the NGAP connection activated with anchor AMF1, but the NGAP connection with AMF2 can be temporarily deactivated.
  • Step 1002 in the case where the drone base station 1 enters a boundary area across different ground stations AMF, the NGAP connection between the drone base station 1 and AMF2 can be reactivated.
  • the drone base station 1 Notify AMF1 through the RAN Configuration Update process: Cells 1,2 have left coverage area 1, and the remaining cells 3 and 4 are still in coverage area 1.
  • UAV base station 1 also reports AMF2 informs: Cells 1 and 2 have entered coverage area 2.
  • AMF2 can know that cell 1,2 has entered coverage area 2 under its jurisdiction, so it can be controlled and used by AMF2 itself. Therefore, when the UE has downlink signaling / data arrival, AMF2 is triggered to perform NG interface search. Call, AMF2 can use UAV base station 1 to undertake air interface paging tasks.
  • cell 1,2 since cell 1,2 leaves coverage area 1 and enters coverage area 2, it is a continuous gradual process, so there is a transition period.
  • Cell 1,2 crosses coverage area 1 and coverage area 2 at the same time, so cell 1,2 can also It is associated with two coverage areas 1 and 2 at the same time, and is jointly controlled and used by AMF1 and AMF2.
  • step 1003 as the drone base station 1 continues to move randomly, the local serving cell 1, 2, 3, and 4 will continue to re-associate with the coverage areas 1 and 2.
  • the drone base station 1 will continue to report to the RAN through the Configuration Update process.
  • AMF1 informs: the latest re-association information between the local serving cell and coverage area 1; at the same time, the drone base station 1 will continue to inform AMF2 through the RAN configuration update process: the latest re-association information between the local serving cell and coverage area 2 .
  • step 1004 as shown in FIG. 10c, it is assumed that the drone base station 1 continues to move downward.
  • the base station 1 is basically located above the center of the coverage area 2.
  • the cells 1, 2, 3, and 4 are all only associated with the coverage area 2, so they can all be managed by the AMF2.
  • drone base station 1 can also initiate NGAP connection deactivation to AMF1 through the RAN configuration update process, that is, drone base station 1 only keeps NGAP connection activation with AMF2, which is similar to that of drone base station 1 in Figure 10a. Initial state.
  • the technical solution provided in the fifth embodiment can prevent AMF2 from being unable to identify the drone base stations and local serving cells available in the current jurisdiction in time, thereby losing the opportunity to serve AMF2 to cover UEs in the jurisdiction, so the drone base station resources can be improved. Utilization rate and the service experience of the UE.
  • the connections in the third, fourth, and fifth embodiments can be deleted when the preset conditions are met, that is, the two nodes on the opposite end of the communication delete the old connection configuration and corresponding port resources.
  • the preset condition may be that the old connection is in a deactivated state for more than a preset time limit, and the difference between the location of the serving cell of the mobile node at one end of the old connection and the edge position of the coverage tracking area of the network node at the other end exceeds the preset threshold ,and many more.
  • FIG. 11 is a schematic structural diagram of a first mobile node provided in Embodiment 6 of the present application. As shown in FIG. 11, the first mobile node includes:
  • the establishment unit is configured to establish a Setup process through a network interface, and establish link connections with multiple peer network nodes, respectively.
  • the link connection includes at least one of the following: a control plane signaling connection and a user plane data connection.
  • the establishing unit includes:
  • a dividing unit configured to divide a plurality of local serving cells subordinate to the first mobile node into a plurality of local cell sets
  • the initiating and interacting unit is configured to initiate, through the corresponding network interface, each local cell set to establish a connection process to establish a link connection with at least two peer network nodes of the plurality of peer network nodes, and exchange respective configuration information. .
  • the configuration information includes at least one of the following: local capabilities of the local cell set, resource configuration of the local cell set, and radio coverage related information of the local cell set.
  • the same local cell set in the multiple local cell sets is administered simultaneously by different peer network nodes.
  • all the local cell sets subordinate to the first mobile node are completely within a second coverage tracking area managed by a second peer network node among the plurality of peer network nodes, all The second link connection between the first mobile node and the second peer network node is in an activated state, and the first mobile node and the plurality of peer network nodes except for the second peer network node Other link connections between other peer network nodes outside the network are in a deactivated state, and the first mobile node is under the jurisdiction of the second peer network node.
  • the first mobile node further includes: an activation unit;
  • the activation unit is configured to, after the first mobile node is under the jurisdiction of the second peer network node, and at least one local cell set under the first mobile node enters the plurality of peer network nodes.
  • the first link connection established between the first mobile node and the first peer network node is activated, and the first The mobile node and the at least one local cell set subordinate to the mobile node belong to the second peer network node and the first peer network node under the common jurisdiction of both.
  • the activating a first link connection established between the first mobile node and a first peer network node includes:
  • TNL link association at the transport layer initiates a node configuration update Configuration Update process to the first peer network node, and connect to the first peer through the first link connection established with the first peer network node
  • the network node notifies the information that the at least one local cell set has entered the range of the first coverage tracking area and the local cell set subordinate to the first mobile node.
  • the activation unit is further configured to initiate a node configuration update Configuration Update process to the second peer network node, and to send a node to the second peer network node through a second link connection established with the second peer network node.
  • the second peer network node notifies that the at least one local cell set has left the local cell set except the at least one local cell set within the second coverage tracking area and under the first mobile node Information.
  • the activation unit is further configured to be after the first mobile node belongs to both the second peer network node and the first peer network node under the common jurisdiction, and the first mobile node When all the local cell sets subordinate to the node leave the range of the second coverage tracking area, the association of the transport layer TNL link is temporarily closed, thereby deactivating the second link connection, and the first mobile node and the The local cell set owned by its subordinates is only under the jurisdiction of the first peer network node.
  • the deactivating the second link connection includes:
  • the first mobile node further includes: a transfer unit;
  • the transfer unit is configured to trigger a mobile handover procedure at the first UE to switch from a first local cell set subordinate to the first mobile node to a second local cell set subordinate to a second mobile node, and the first local cell
  • both the set and the second local cell set are within a first coverage tracking area managed by a first peer network node among the multiple peer network nodes, only the radio access layer of the first UE communicates
  • the context UEAS context is transferred from the first mobile node to the second mobile node, and the UE non-radio access layer communication context UE and NASContext are always maintained and maintained in the first peer network node.
  • the first mobile node further includes: a storage unit;
  • the storage unit is configured to keep the non-radio access layer communication context UE NAS Context of the first UE all the time when the first UE stays within the first coverage tracking area under the jurisdiction of the first peer network node; only When the first UE moves outside the first coverage tracking area under the jurisdiction of the first peer network node, the target peer network node saves the migrated UE NASContext.
  • the mobile node is a mobile NG-RAN base station
  • the peer network node is a 5GC network node
  • the link connection is an NGAP connection instance
  • the mobile node is a mobile NG-RAN base station
  • the peer network node is a mobile NG-RAN base station
  • the link connection is an XnAP connection instance
  • the mobile node is a distributed processing unit DU
  • the peer network node is a centralized processing unit CU
  • the link connection is an F1AP connection instance.
  • the 5GC network node is one of the following: an access management function node AMF, a session management function node SMF, and a user plane function node UPF;
  • the mobile NG-RAN base station is one of the following: ng-eNB, which continues to evolve based on 4G eNBs, gNB with a new physical layer air interface design, LEO earth low-orbit satellites equipped with Full gNB functions, and Human-machine base station
  • the centralized processing unit CU in the mobile NG-RAN base station is: NG-RAN separated base station gNB-CU;
  • the distributed processing unit DU in the mobile NG-RAN base station is one of the following: the NG-RAN separated base station gNB-DU and the LEO earth low-orbit satellite equipped with the gNB-DU function.
  • FIG. 12 is a schematic structural diagram of a system for connection management between nodes provided in Embodiment 7 of the present application. As shown in FIG. 12, the system includes:
  • a first mobile node and multiple peer network nodes A first mobile node and multiple peer network nodes
  • the first mobile node is configured to establish a Setup process through a network interface, and establish link connections with the multiple peer network nodes, respectively.
  • the link connection includes at least one of the following: a control plane signaling connection and a user plane data connection.
  • the first mobile node is configured to establish a Setup process through a network interface and establish link connections with multiple peer network nodes, respectively, including:
  • Each local cell set initiates a link connection setup setup process with at least two peer network nodes of the plurality of peer network nodes through a corresponding network interface, and exchanges respective configuration information.
  • the configuration information includes at least one of the following: local capabilities of the local cell set, resource configuration of the local cell set, and radio coverage related information of the local cell set.
  • the method further includes:
  • Different local cell sets of the multiple local cell sets are under the jurisdiction of different peer network nodes
  • the same local cell set in the multiple local cell sets is administered simultaneously by different peer network nodes.
  • all the local cell sets subordinate to the first mobile node are completely within a second coverage tracking area managed by a second peer network node among the plurality of peer network nodes, all The second link connection between the first mobile node and the second peer network node is in an activated state, and the first mobile node and the plurality of peer network nodes except for the second peer network node Other link connections between other peer network nodes outside the network are in a deactivated state, and the first mobile node is under the jurisdiction of the second peer network node.
  • the first mobile node after the first mobile node is under the jurisdiction of the second peer network node, and at least one local cell set subordinate to the first mobile node enters the plurality of peer network nodes.
  • the first mobile node is further configured to activate a first established mobile node between the first mobile node and the first peer network node. A link connection.
  • the first mobile node and the at least one local cell set subordinate to the first mobile node belong to the second peer network node and the first peer network node under common jurisdiction.
  • the activating a first link connection established between the first mobile node and a first peer network node includes:
  • TNL link association at the transport layer initiates a node configuration update Configuration Update process to the first peer network node, and connect to the first peer through the first link connection established with the first peer network node
  • the network node notifies the information that the at least one local cell set has entered the range of the first coverage tracking area and the local cell set subordinate to the first mobile node.
  • the first mobile node is further configured to initiate a node configuration update Configuration Update process to the second peer network node, and pass a second link established with the second peer network node.
  • the connection notifies the second peer network node that the at least one local cell set has left the area within the second coverage tracking area and that is subordinate to the first mobile node except for the at least one local cell set. Information about the cell collection.
  • the first mobile node after the first mobile node belongs to both the second peer network node and the first peer network node under the common jurisdiction, all the local cells under the first mobile node set leave.
  • the first mobile node is further configured to temporarily close the association of the transport layer TNL link, thereby deactivating the second link connection, and the first mobile The node and the local cell set owned by its subordinates are under the jurisdiction of the first peer network node only.
  • the deactivating the second link connection includes:
  • system further includes a second mobile node
  • a mobile handover procedure is triggered at the first UE to switch from a first local cell set subordinate to the first mobile node to a second local cell set subordinate to a second mobile node, and the first local cell set and the second local cell set
  • the first mobile node is further configured to only set a radio access layer of the UE.
  • the communication context UEAS context is transferred from the first mobile node to the second mobile node, and the UE non-radio access layer communication context UE and NASContext is always maintained and maintained in the first peer network node.
  • the first mobile node is further configured to keep the non-wireless access of the first UE all the time when the first UE stays within the first coverage tracking area under the jurisdiction of the first peer network node.
  • In-layer communication context UE Context only when the first UE moves outside the first coverage tracking area under the jurisdiction of the first peer network node, the target peer network node saves the migrated UE NAS context.
  • the mobile node is a mobile NG-RAN base station
  • the peer network node is a 5GC network node
  • the link connection is an NGAP connection instance
  • the mobile node is a mobile NG-RAN base station
  • the peer network node is a mobile NG-RAN base station
  • the link connection is an XnAP connection instance
  • the mobile node is a distributed processing unit DU
  • the peer network node is a centralized processing unit CU
  • the link connection is an F1AP connection instance.
  • the 5GC network node is one of the following: an access management function node AMF, a session management function node SMF, and a user plane function node UPF;
  • the mobile NG-RAN base station is one of the following: ng-eNB, which continues to evolve based on 4G eNBs, gNB with a new physical layer air interface design, LEO earth low-orbit satellites equipped with Full gNB functions, and Human-machine base station
  • the centralized processing unit CU in the mobile NG-RAN base station is: NG-RAN separated base station gNB-CU;
  • the distributed processing unit DU in the mobile NG-RAN base station is one of the following: the NG-RAN separated base station gNB-DU and the LEO earth low-orbit satellite equipped with the gNB-DU function.
  • An embodiment of the present application further provides a first mobile node, including a memory, a processor, and a computer program stored on the memory and executable on the processor.
  • a computer program stored on the memory and executable on the processor.
  • An embodiment of the present application further provides a computer-readable storage medium, where the computer-readable storage medium stores an information processing program, and when the information processing program is executed by a processor, the chain between any of the nodes described above is implemented Method of road connection management.
  • the technical solution provided in the embodiment of the present application implements a method and method for managing multiple connections of a mobile base station interface, so that in a network environment constructed by a mobile base station, a mobile network element node / serving cell and a peer network can be efficiently established and maintained.
  • the TNL transmission bearer between the meta nodes is connected to the upper RNL application protocol layer, so as to ensure that the network NG, F1, Xn and other interfaces can match and adapt to the dynamic topology of the mobile base station in time, and minimize the NG, F1, Xn and other interfaces
  • the ineffective TNL / RNL layer interface reconstruction and interface service interruption improve the system's utilization of mobile base station resources.
  • the term computer storage medium includes volatile and non-volatile implemented in any method or technology used to store information such as computer-readable instructions, data structures, program modules or other data.
  • Computer storage media include, but are not limited to, RAM (Random Access Memory), ROM (Read-Only Memory, Read-Only Memory), EEPROM (Electrically Erasable, Programmable, Read-only Memory) Flash memory or other memory technology, CD-ROM (Compact Disc Read-Only Memory), Digital Video Disc (DVD) or other optical disc storage, magnetic box, magnetic tape, disk storage or other magnetic storage A device, or any other medium that can be used to store desired information and can be accessed by a computer.
  • a communication medium typically contains computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and may include any information delivery medium .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例公开了一种节点之间链路连接管理的方法及相关设备，其中该方法包括第一移动节点通过网络接口建立Setup流程，分别与多个对端网络节点建立链路连接。

Description

一种节点之间链路连接管理的方法及相关设备
本申请要求在2018年09月28日提交中国专利局、申请号为201811142058.4的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及但不限于移动通讯系统技术，例如涉及一种节点之间链路连接管理的方法及相关设备。
背景技术
在传统的陆基蜂窝移动网络中，每一种NG-RAN(Next Generation Radio Access Network，下一代无线接入网络)基站的部署，相对于地面特定经纬度的物理位置，都是相对静止固定不动的，因此NG-RAN基站所提供的空口服务小区的无线覆盖/容量供给，和连接这些NG-RAN基站的NG，Xn，F1相关接口，也都是相对物理位置固定不变的。NG，Xn，F1等接口的TNL(Transport Network Layer，传输网络层)传输承载，大部分是通过宽带光纤等固网方式去实现的，因此链路的传输鲁棒性和延时性能都是比较好的。这种固定式的陆基蜂窝移动网络，比较便于运营商的部署和资源管理，因为所有网元节点和网络资源都能通过(半)静态的方式去规划管理。在固定式陆基蜂窝移动网络下，随着用户设备(User Equipment，UE)的移动，为了保持用户业务连续性，只需要解决UE在不同服务小区/基站/网元节点之间的链路移动性问题。
近年来，随着多类移动式基站的出现，比如：地面车载移动式基站，空中无人机基站，空间卫星通讯基站等，这些移动式基站所提供的空口服务小区无线覆盖/容量供给，通常会随着移动式基站的物理位置移动而变化，而连接这些移动式基站的NG，Xn，F1接口的TNL传输承载却不能是固定方式的，无法通过宽带光纤等固网方式去承载，通常只能依赖多种无线的承载方式，如：微波，激光，中继等手段。这种移动式基站构建的网络，虽然在部署方面更加的灵活，但网络资源和TNL无线承载却只能通过相对动态的方式去规划管理；否则随着多个基站的移动，网络拓扑发生变化，TNL无线承载质量不稳定，移动式基站相关的每个接口，很可能因为TNL无线承载的变化和中断而被破坏，从而移动 式基站侧的多种资源无法被高效地利用，甚至UE的业务被迫中断等。此外，随着移动式基站的移动，相关网元节点之间需要及时同步更新彼此相关的配置，例如无线覆盖信息，以保证端到端无线链路的畅通。并且，在移动式基站构建的网络下，随着TNL传输承载的变化和中断，TNL之上的RNL应用层协议连接，如NGAP(NG Application Protocol，NG接口应用流程协议)，XnAP(Xn Application Protocol，Xn接口应用流程协议)，F1AP(F1 Application Protocol，F1接口应用流程协议)连接等也会发生相应的变化和中断，因此移动式基站随着物理移动会和新(旧)对端网元节点，发起较频繁的建立Setup和配置更新Configuration Update类的流程，不断反复地执行RNL应用协议层连接实例的建链，拆链，重建链和配置更新等操作，这会导致大量的RNL层信令和接口服务中断。
发明内容
本申请实施例提供了一种节点之间链路连接管理的方法，包括：第一移动节点通过网络接口建立Setup流程，分别与多个对端网络节点建立链路连接。
本申请实施例还提供了一种第一移动节点，包括：
建立单元，设置为通过网络接口建立Setup流程，分别与多个对端网络节点建立链路连接。
本申请实施例还提供了一种节点之间链路连接管理的系统，所述系统包括；
第一移动节点和多个对端网络节点；
所述第一移动节点设置为执行上述节点之间链路连接管理的方法。
本申请实施例还提供了一种第一移动节点，包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现上述节点之间链路连接管理的方法。
本申请实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质上存储有信息处理程序，所述信息处理程序被处理器执行时实现上述节点之间链路连接管理的方法。
附图说明
附图用来提供对本申请技术方案的理解，并且构成说明书的一部分，与本申请的实施例一起用于解释本申请的技术方案，并不构成对本申请技术方案的限制。
图1为Aggregated NG-RAN聚合式基站CU/DU空口协议栈不分离情况下的架构图；
图2为Disaggregated NG-RAN分离式基站gNB CU/DU空口协议栈分离情况下的架构图；
图3为传统NG-RAN基站与AMF之间NG接口建立流程；
图4为传统NG-RAN基站与AMF之间NG-RAN侧发起的NG接口配置更新流程；
图5为传统NG-RAN基站与AMF之间AMF侧发起的NG接口配置更新流程；
图6为本申请实施例一提供的节点之间链路连接管理的方法的流程示意图；
图7a为本申请实施例二提供的网络节点间NG接口多连接的示意图；
图7b为本申请实施例二提供的网络节点间F1接口多连接的示意图；
图7c为本申请实施例二提供的网络节点间Xn接口多连接的示意图；
图8a为本申请实施例三提供的FU型卫星通讯系统架构的示意图；
图8b为本申请实施例三提供的FU型卫星移动跨越不同地面站AMF的区域的示意图；
图8c为本申请实施例三提供的FU型卫星与多个地面站AMF多连接的示意图；
图9a为本申请实施例四提供的DU型卫星通讯系统架构的示意图；
图9b为本申请实施例四提供的DU型卫星移动跨越不同地面站gNB-CU的区域的示意图；
图9c为本申请实施例四提供的DU型卫星与多个地面站gNB-CU多连接的示意图；
图10a为本申请实施例五提供的空中无人机基站通讯系统架构的示意图；
图10b为本申请实施例五提供的无人机基站移动跨越不同地面站AMF的区域的示意图；
图10c为本申请实施例五提供的无人机基站与多个地面站AMF多连接的示意图；
图11为本申请实施例六提供的第一移动节点的结构示意图；
图12为本申请实施例七提供的一种节点之间链路连接管理的系统的结构示意图。
具体实施方式
下文中将结合附图对本申请的实施例进行详细说明。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。
第四代4G(4 Generation)或称为长期演进LTE(Long Term Evolution)陆基蜂窝移动通讯系统中，包含4G核心网，即演进的分组核心网(Evolved Packet Core，EPC)和无线接入网络(Radio Access Network，RAN)两大子系统。4G EPC包含MME(Mobility Management Entity，移动管理实体节点)，SGW(Serving Gateway，服务网关节点)，PGW(PDN Gateway，PDN网关节点)等基本网元节点，而4G RAN包括长期演进型基站eNB(evolved Node B)和相关的基站网元之间的接口。4G之后的5G(Fifth Generation，第五代移动通信)陆基蜂窝移动通讯系统中，也包含了下一代核心网5GC(5 Generation Core，5G核心网)和下一代无线接入网络NG-RAN(Next Generation Radio Access Network)两大子系统。5GC包含AMF(Access Mobility Function，接入管理功能节点)，SMF(Session Management Function，会话管理功能节点)和UPF(User Plane Function，用户面功能节点)等网元节点，而NG-RAN中至少包含两种不同的无线接入制式RAT类型的基站，即：基于4G eNB继续演进的ng-eNB(空口仍然支持E-UTRA RAT制式)，和全新物理层空口设计的gNB(空口支持NR(New Radio，新无线系统)RAT制式)基站，以及相关的基站网元接口。
图1为聚合式基站(如Aggregated NG-RAN)，在CU(Centralized Unit，集中式处理单元)/DU(Distributed Unit，分布式处理单元)空口协议栈不分离 情况下的架构图。如图1所示，NG-RAN基站(gNB或ng-eNB)通过标准化的NG接口，和5GC相互连接。NG-RAN基站与5GC之间的连接方式包括NG-C(Next Generation-Control Plane，5G核心网元控制面连接)控制面(信令)连接和NG-U(Next Generation-User Plane，5G核心网元用户面连接)用户面(用户数据)连接。NG-RAN基站(gNB或ng-eNB)之间通过Xn接口相互连接。NG-RAN基站之间的连接方式包括Xn-C(Xn-Control Plane，NG-RAN基站间控制面连接)控制面连接和Xn-U(Xn–User Plane，NG-RAN基站间用户面连接)用户面连接。图2为分离式基站gNB(如Disaggregated NG-RAN)，在CU/DU空口协议栈分离情况下的架构图。以当前已支持的gNB分离为例，如图2所示，单个gNB被分离为单个gNB-CU和多个gNB-DU网元节点实体，gNB-CU和gNB-DU之间通过标准化的F1接口相互连接，基于F1接口的连接方式包括F1-C控制面连接和F1-U用户面连接。CU/DU分离后的gNB和不分离的gNB对外的接口仍然都是NG和Xn接口。上述多类接口的控制面(CP，Control Plane)连接设置为传输网元节点之间的控制信令消息，而用户面(UP，User Plane)连接设置为传输用户业务数据(包)。NGAP，XnAP，F1AP分别为NG-C(Next Generation-Control Plane，5G核心网元控制面连接)，Xn-C(Xn-Control Plane，NG-RAN基站间控制面连接)，F1-C控制面RNL(Radio Network Layer，逻辑网络层)的应用层协议，上述应用层协议基于TNL(Transport Network Layer，传输网络层)传输承载(SCTP(Streaming Control Transport Protocol，流控制传输协议)连接)来传输对应接口的控制信令；而NG-U(Next Generation-User Plane，5G核心网元用户面连接)，Xn-U(Xn–User Plane，NG-RAN基站间用户面连接)，F1-U用户面接口用户数据帧，基于TNL传输承载(GTP-U(GPRS Tunnel Protocol，GPRS隧道协议)隧道)来传输对应接口的用户数据。
下面为了简化说明，将重点以NG接口为例子，而Xn，F1接口的原理基本类似。根据当前3GPP协议，单个NG-RAN基站及其内部本地服务小区，从实际部署和使用的角度看，通常只需要通过单条NG-C接口NGAP连接于唯一一个对端的AMF实体，称为该基站/服务小区的Serving AMF。如图3所示：NG接口的NG Setup流程使得NG-RAN基站能主动发起和对端Serving AMF的NGAP连接建立，交互节点彼此各自的初始本地配置信息，如：节点级和小区级的能力和配置相关信息，本地服务小区/跟踪区的配置和标识等。如图4所示： 如果NG-RAN基站的本地任何的配置信息发生更新，可以通过RAN Configuration Update流程发起和Serving AMF的NGAP配置更新。如附图5所示：如果AMF的本地任何的配置信息发生更新，可以通过AMF Configuration Update流程发起和NG-RAN基站的NGAP配置更新。由于多种部署变化的需求，如果单个NG-RAN基站/服务小区需连接到另外一个新Serving AMF，则通常先删除掉和原来旧Serving AMF的NGAP连接和相关端口资源，并且重新向新Serving AMF发起NG Setup流程。这种“自上而下的树状拓扑”对于传统的陆基蜂窝移动网络中是足够的，因为单个NG-RAN基站内的特定本地服务小区资源通常只需被单个Serving AMF所管辖。原理类似的，单个gNB-DU实体内的特定本地服务小区资源通常也只需被单个Serving gNB-CU实体所管辖。Xn接口虽然能支持单个NG-RAN基站/服务小区同时和多个相邻NG-RAN基站/服务小区的XnAP连接，但XnAP连接也需要涉及相应的建立Setup和配置更新Configuration Update类的流程。
近年来，多类移动式基站不断出现。如此，随着移动式基站的移动，相关网元节点之间需要及时同步更新彼此相关的配置，例如无线覆盖信息，以保证端到端无线链路的畅通。例如，在移动式基站构建的网络下，随着TNL传输承载的变化和中断，TNL之上的RNL应用层协议连接，如NGAP，XnAP，F1AP连接等也会发生相应的变化和中断，因此移动式基站随着物理移动会和新(旧)对端网元节点，发起较频繁的Setup和Configuration Update类的流程，不断反复地执行RNL应用协议层连接实例的建链，拆链，重建链和配置更新等操作，这会导致大量的RNL层信令和接口服务中断。
基于此，本申请提出了网元实体(节点)之间多连接的概念，使得在移动式基站构建的网络环境下，能高效建立和维护移动网元节点(服务小区)和对端网元节点之间的TNL传输承载和上层RNL应用协议层连接，从而尽量保证网络NG，F1，Xn等接口能及时和移动式基站的动态拓扑变化之间匹配适应，尽量减少NG，F1，Xn等接口无为的TNL/RNL层接口重建和接口服务中断，提升系统对移动式基站资源的利用率。
实施例一
图6为本申请实施例一提供的节点之间链路连接管理的方法的流程示意图。如图6所示，该方法包括如下步骤：
步骤601，第一移动节点通过网络接口建立Setup流程，分别与多个对端网络节点建立链路连接。
在一实施例中，所述链路连接包括如下至少之一：控制面信令连接和用户面数据连接。
在一实施例中，该链路连接可包含：控制面信令连接(设置为传输控制信令消息等)和用户面数据连接(设置为传输业务数据包等)。
在一实施例中，所述第一移动节点通过网络接口的建立Setup流程，分别与多个对端网络节点建立链路连接，包括：
所述第一移动节点将下属的多个本地服务小区划分为多个本地小区集合；
每一个本地小区集合通过对应的网络接口发起和所述多个对端网络节点中的至少两个对端网络节点的链路连接建立Setup流程，并交互各自的配置信息。
在一实施例中，相同本地小区集合内的小区具有相同的管理属性，不同的本能地小区集合具有不同的管理属性。
在一实施例中，所述配置信息包括如下至少之一：本地小区集合的本地能力、本地小区集合的资源配置和本地小区集合的无线覆盖相关信息。
本实施例中，所述配置信息包括本地小区(集合)的本地能力和资源配置和无线覆盖相关信息等信息。
本实施例中，在交互各自的配置信息之后，该方法还包括：
所述多个本地小区集合中不同的本地小区集合被不同的对端网络节点所管辖；
或者，所述多个本地小区集合中同一个本地小区集合被不同的对端网络节点所同时管辖。
本实施例中，第一移动节点的不同本地小区集合，可分别被不同的对端网络节点所管辖；或者第一移动节点的同一本地小区集合，也可被不同的对端网络节点所同时管辖。
在一实施例中，在所述第一移动节点与第一对端网络节点建立第一链路连接之后，所述方法还包括：
在所述第一移动节点下属的全部本地小区集合完全处于所述多个对端网络节点中第二对端网络节点管辖的第二覆盖跟踪区域范围内的情况下，所述第一移动节点与所述第二对端网络节点之间的第二链路连接处于激活状态，所述第一移动节点与所述多个对端网络节点中除了第二对端网络节点之外的其他对端网络节点之间的其他链路连接处于去激活状态，所述第一移动节点归所述第二对端网络节点管辖。
在一实施例中，在所述第一移动节点归所述第二对端网络节点管辖之后，该方法还包括：
在所述第一移动节点下属的至少一个本地小区集合进入所述多个对端网络节点中第一对端网络节点管辖的第一覆盖跟踪区域范围内的情况下，则激活所述第一移动节点与第一对端网络节点之间已建立的第一链路连接，此时所述第一移动节点和其下属的所述至少一个本地小区集合同时归属所述第二对端网络节点和所述第一对端网络节点共同管辖。
在一实施例中，所述激活所述第一移动节点与第一对端网络节点之间已建立的第一链路连接，包括：
所述第一移动节点发起传输层TNL链路关联，向所述第一对端网络节点发起节点配置更新Configuration Update流程，通过与所述第一对端网络节点已建立的第一链路连接向所述第一对端网络节点告知所述至少一个本地小区集合已进入所述第一覆盖跟踪区域范围内和所述第一移动节点下属的所述至少一个本地小区集合的信息。本实施例中，所述第一移动节点下属的所述至少一个本地小区集合的信息可以是指所述第一移动节点下属的已经进入所述第一覆盖跟踪区域范围内的全部或部分本地小区集合的标识信息，例如标识信息可以是小区ID或小区集合ID。
在一实施例中，该方法还包括：
所述第一移动节点向所述第二对端网络节点发起节点配置更新Configuration Update流程，通过与所述第二对端网络节点已建立的第二链路连接向所述第二对端网络节点告知所述至少一个本地小区集合已离开所述第二覆盖跟踪区域范围内和所述第一移动节点下属的除了所述至少一个本地小区集合之外的本地小区集合的信息。本实施例中，所述第一移动节点下属的除了所述 至少一个本地小区集合之外的本地小区集合的信息可以是指所述第一移动节点下属的仍然处于第二覆盖跟踪区域范围内的全部或部分本地小区集合的标识信息，例如标识信息可以是小区ID或小区集合ID。
在一实施例中，在所述第一移动节点同时归属所述第二对端网络节点和所述第一对端网络节点共同管辖之后，该方法还包括：
在所述第一移动节点下属的全部本地小区集合离开所述第二覆盖跟踪区域范围内的情况下，则暂时关闭传输层TNL链路的关联，从而去激活所述第二链路连接，所述第一移动节点和其下属所有的本地小区集合仅归所述第一对端网络节点管辖。
在一实施例中，所述去激活所述第二链路连接，包括：
所述第一移动节点向所述第二对端网络节点发起节点配置更新Configuration Update流程，通过与所述第二对端网络节点已建立的第二链路连接向所述第二对端网络节点告知所述第一移动节点下属的全部本地小区集合离开所述第二覆盖跟踪区域范围内，但所述第二对端网络节点仍然保持接口链路连接的配置上下文信息，以待所述第一移动节点后续再次发起传输层TNL链路关联。
在一实施例中，该方法还包括：
在第一UE触发移动切换流程从所述第一移动节点下属的第一本地小区集合切换到第二移动节点下属的第二本地小区集合，且所述第一本地小区集合和第二本地小区集合都处于所述多个对端网络节点中第一对端网络节点管辖的第一覆盖跟踪区域范围内的情况下，仅将所述第一UE的无线接入层通讯上下文UE AS Context从所述第一移动节点转移到所述第二移动节点，并一直保持并维护UE非无线接入层通讯上下文UE NAS Context在所述第一对端网络节点内。
在一实施例中，该方法还包括：
当第一UE停留在第一对端网络节点管辖的第一覆盖跟踪区域范围内，则第一对端网络节点一直保存所述第一UE的非无线接入层通讯上下文UE NAS Context；只有当所述第一UE移动到第一对端网络节点管辖的第一覆盖跟踪区域范围之外，则由目标对端网络节点保存迁移后的UE NAS Context。
本实施例中，当第一UE停留在第一对端网络节点管辖的第一覆盖跟踪区域 范围内，则第一对端网络节点一直保存着UE NAS Context；只有当第一UE移动到第一对端网络节点管辖的第一覆盖跟踪区域范围之外，则由新的目标对端网络节点去尝试保存迁移后的UE NAS Context。
在一实施例，所述移动节点为移动式NG-RAN基站，所述对端网络节点为5GC网络节点，所述链路连接为NGAP连接实例；
或者，所述移动节点为移动式NG-RAN基站，所述对端网络节点为移动式NG-RAN基站，所述链路连接为XnAP连接实例；
或者，所述移动节点为分布式处理单元DU，所述对端网络节点为集中式处理单元CU，所述链路连接为F1AP连接实例。
在一实施例，所述5GC网络节点为以下之一：接入管理功能节点AMF、会话管理功能节点SMF和用户面功能节点UPF；
所述移动式NG-RAN基站为以下之一：基于4G eNB继续演进的ng-eNB、全新物理层空口设计的gNB、装载着Full gNB功能的LEO地球低轨卫星和装载着Full gNB功能的无人机基站；
移动式NG-RAN基站内的集中式处理单元CU为：NG-RAN分离式基站gNB-CU；
移动式NG-RAN基站内的分布式处理单元DU为以下之一：NG-RAN分离式基站gNB-DU和装载着gNB-DU功能的LEO地球低轨卫星。
下面通过几个的实施例详细阐述实施一提供的技术方案。
实施例二
图7a为本申请实施例二提供的网络节点间NG接口多连接的示意图；图7b为本申请实施例二提供的网络节点间F1接口多连接的示意图；图7c为本申请实施例二提供的网络节点间Xn接口多连接的示意图。
如图7a所示，在左侧有单个NG-RAN基站1(移动节点)，它可以是物理上移动的，因此它和其它网元节点之间的TNL传输承载以及上层RNL NGAP连接容易发生变化或被中断破坏。在右侧有多个5GC对端网元节点集合，它们默认是地面上固定或静止的，是每个移动NG-RAN基站需要建立TNL传输承载和上层NGAP连接的对端对象。
基站1把自己内部的所有本地服务小区先划分为多个本地小区集合1，2，…，n。本地小区集合的一个特例就是一个本地服务小区，即每一个本地小区集合只包括一个本地服务小区。
基站1可以重新划分本地服务小区所属的本地小区集合。
基站1具备一定的定位功能，能够了解基站1自身和本地服务小区覆盖和地面规划覆盖区域之间的关系。
每个本地小区集合可以同时和多个AMF节点建立和维持不同的NGAP连接，因此可以同时被多个AMF节点所辖管理(管辖)。
不同的本地小区集合可以独立地和不同的AMF实体集合建立和维持NGAP连接。
如图7a所示：本地小区集合1所对应的端口和AMF1和AMF2各自建立独立的TNL传输承载和上层NGAP连接，当本地小区集合1或AMF 1或AMF2的配置信息，特别是：本地服务小区覆盖的地理位置发生变化，和不同的地面规划覆盖区域重关联信息，可以彼此通过NG接口配置更新Configuration Update类流程更新。与此同时，本地小区集合2所对应的端口和AMF2和AMFx各自建立独立的TNL传输承载和上层NGAP连接，当本地小区集合2或AMF 2或AMFx的配置信息发生变化，可以彼此通过NG接口Configuration Update类流程更新。同理对本地小区集合n所对应的端口和AMF2和AMFn各自建立独立的TNL传输承载和上层NGAP连接，当本地小区集合n或AMF 2或AMFn的配置信息发生变化，可以彼此通过NG接口Configuration Update类流程更新。
每条NGAP连接拥有三个实时状态：建立(激活)，删除，去激活。
建立(激活)表示：NGAP连接已建立并处于正常工作状态，能传输NGAP流程消息。
去激活表示：虽然NGAP连接已建立，但暂时不能传输NGAP流程消息，NGAP通讯对端两个节点都暂时保存着旧NGAP连接配置和相应端口资源不删除。
删除表示：NGAP通讯对端两个节点删除掉旧NGAP连接配置和相应端口资源。
同理，如图7b所示：在左侧有单个gNB-DU1(移动节点)，它可以是物理上移动的，因此它和其它网元节点之间的TNL传输承载以及上层RNL F1AP连接容易发生变化或被中断破坏。在右侧有多个gNB-CU对端网元节点集合，它们默认是地面上固定或静止的，是每个移动gNB-DU需要建立TNL传输承载和上层NGAP连接的对端对象。
gNB-DU1把自己内部的所有本地服务小区先划分为多个本地小区集合1，2，…，n。本地小区集合的一个特例就是一个本地服务小区，即每一个本地小区集合只包括一个本地服务小区。
gNB-DU1可以重新划分本地服务小区所属的本地小区集合。
gNB-DU1具备一定的定位功能，能够了解gNB-DU1自身和本地服务小区覆盖和地面规划覆盖区域之间的关系。
每个本地小区集合可以同时和多个gNB-CU节点建立和维持不同的F1AP连接，因此可以同时被多个gNB-CU节点所辖管理。
不同的本地小区集合可以独立地和不同的gNB-CU实体集合建立和维持F1AP连接。
如图7b所示：本地小区集合1所对应的端口和gNB-CU1和gNB-CU2各自建立独立的TNL传输承载和上层F1AP连接，当本地小区集合1或gNB-CU1或gNB-CU2的配置信息，特别是：本地服务小区覆盖的地理位置发生变化，和不同的地面规划覆盖区域重关联信息，可以彼此通过F1接口Configuration Update类流程更新。与此同时，本地小区集合2所对应的端口和gNB-CU2和gNB-CUx各自建立独立的TNL传输承载和上层F1AP连接，当本地小区集合2或gNB-CU 2或gNB-CUx的配置信息发生变化，可以彼此通过F1接口Configuration Update类流程更新。同理对本地服务小区集合n所对应的端口和gNB-CU2和gNB-CUn各自建立独立的TNL传输承载和上层F1AP连接，当本地小区集合n或gNB-CU 2或gNB-CUn的配置信息发生变化，可以彼此通过F1接口Configuration Update类流程更新。
每条F1AP连接拥有三个实时状态：建立(激活)，删除，去激活。
建立(激活)表示：F1AP连接已建立并处于正常工作状态，能传输F1AP流程消息。
去激活表示：虽然F1AP连接已建立，但暂时不能传输F1AP流程消息，F1AP通讯对端两个节点都暂时保存着旧F1AP连接配置和相应端口资源不删除。
删除表示：F1AP通讯对端两个节点删除掉旧F1AP连接配置和相应端口资源。
同理，如图7c所示：在左侧有单个NG-RAN基站1(移动节点)，它可以是物理上移动的，因此它和其它网元节点之间的TNL传输承载以及上层RNLXnAP连接容易发生变化或被中断破坏。在右侧有多个相邻基站对端网元节点集合，它们默认是地面上固定或静止的，是每个移动NG-RAN基站需要建立TNL传输承载和上层XnAP连接的对端对象。
基站1把自己内部的所有本地服务小区先划分为多个本地小区集合1，2，…，n。本地小区集合的一个特例就是一个本地服务小区，即每一个本地小区集合只包括一个本地服务小区。
基站1可以重新划分本地服务小区所属的集合。
基站1具备一定的定位功能，能够了解基站1自身和本地服务小区覆盖和地面规划覆盖区域之间的关系。
每个本地服务小区集合可以同时和多个相邻基站节点建立和维持不同的XnAP连接。
不同的本地服务小区集合可以独立地和不同的相邻基站实体集合建立和维持XnAP连接，因此同时和多个相邻基站节点相互关联。
如图7c所示：本地小区集合1所对应的端口和相邻基站1和相邻基站2各自建立独立的TNL传输承载和上层XnAP连接，当本地小区集合1或相邻基站1或相邻基站2的配置信息，特别是：本地服务小区覆盖的地理位置发生变化，和不同的地面规划覆盖区域重关联信息，可以彼此通过Xn接口Configuration Update类流程更新。与此同时，本地小区集合2所对应的端口和相邻基站2和相邻基站x各自建立独立的TNL传输承载和上层XnAP连接，当本地小区集合2或相邻基站2或相邻基站x的配置信息发生变化，可以彼此通过Xn接口Configuration Update类流程更新。同理对本地服务小区集合n所对应的端口和相邻基站2和相邻基站n各自建立独立的TNL传输承载和上层XnAP连接，当本地小区集合2或相邻基站2或相邻基站n的配置信息发生变化，可以彼此通 过Xn接口Configuration Update类流程更新。
每条XnAP连接拥有三个实时状态：建立(激活)，删除，去激活。
建立(激活)表示：XnAP连接已建立并处于正常工作状态，能传输XnAP流程消息。
去激活表示：虽然XnAP连接已建立，但暂时不能传输XnAP流程消息，XnAP通讯对端两个节点都暂时保存着旧XnAP连接配置和相应端口资源不删除。
删除表示：XnAP通讯对端两个节点删除掉旧XnAP连接配置和相应端口资源。
实施例三
本实施例三中，本地小区集合仅包括一个小区，即一个小区即为一个本地小区集合；第一移动节点为移动式NG-RAN基站，该移动式NG-RAN基站为装载着Full gNB功能的LEO地球低轨卫星；对端网络节点为接入移动功能节点AMF；第一移动节点与对端网络节点的链路连接为NG接口连接。
图8a为本申请实施例三提供的FU型卫星通讯系统架构的示意图，如图8a所示，在FU型卫星通讯系统中，多颗LEO地球低轨卫星上装载着Full gNB功能，它们在空间沿着特定的同一轨道绕地球周期的运行。地面上的某终端UE(假设在地面准静止不动，且处于RRC连接态)当前处于AMF1管辖的地面规划覆盖区域1中，UE当前的服务小区是卫星1所辖的小区1，UE通过Service link(业务链路)和空间FU型卫星1，直接进行无线通讯，而LEO卫星各自通过Feeder link(馈线链路)，和地面站5GC集合中的AMF/SMF/UPF分别建立NG接口连接，包括NG-C信令NGAP连接和NG-U数据连接。
基于传统的节点之间连接管理的方案，在图8a中，卫星1当前连接于地面站AMF1，卫星2连接于地面站AMF2(注：在某些空间位置，卫星1/2也可能连接于同一个地面站AMF)。随着卫星沿着特定的轨道继续向下移动，卫星2所辖的多个服务小区8,7,6,5会逐步地离开地面规划覆盖区域2，而向地面规划覆盖区域1内移动，如图8b所示：小区8已从原来的旧覆盖区域2移动到了AMF1所辖的新覆盖区域1之内，同理下面卫星1的小区4也相应的移出了原来的旧覆盖区域1。根据连接态UE无线链路移动管理的需求，当UE监测发现旧 小区1的服务信号越来越弱，而新小区8的服务信号越来越强，UE会触发网络去执行移动切换流程，网络尝试把UE从旧服务小区1切换到新服务小区8。成功切换的结果是：在NG-RAN接入网络侧，UE无线接入层通讯上下文(UE AS Context)从卫星1转移到卫星2内，在5GC核心侧，UE非无线接入层通讯上下文(UE NAS Context)暂时从AMF1转移到AMF2内(因为卫星2一直被AMF2所辖)。再经过一段时间之后，当卫星2完全移动到覆盖区域1的中心上空(此时卫星2的位置和附图8a中的卫星1的类似)，此时卫星2会发起向新地面站AMF1的NG接口建立流程，而同时删除和旧地面站AMF2的NG接口，从而卫星2所辖的小区5,6,7,8用来对覆盖区域1覆盖。由于卫星2的锚点核心网元AMF2->AMF1重定位(AMF Relocation)，此时尽管卫星2能继续保留UE AS Context，但UE NAS Context还需要再从AMF2重新转移回到AMF1，这就造成了UE非无线接入层通讯上下文UE NAS Context在不同地面站AMF之间的迂回转移
为此，本申请实施例三提出了一种新的节点之间连接管理的方案，该方案包括：
步骤801，初始每颗卫星，例如卫星2和多个不同的地面站AMF1和AMF2提前建立好各自的NGAP连接，且彼此通过NG Setup流程，同步交互好各自的本地服务小区能力配置信息等，本地服务小区能力配置信息包括：当前本地服务小区覆盖和不同地面规划覆盖区域之间的关联信息。当卫星2完全处于地面规划覆盖区域2的中心上空的时候，此时小区5,6,7,8全部仅和覆盖区域2相关联，因此全部被AMF2所辖，因此卫星2可仅保持和锚点AMF2的NGAP连接激活，但和AMF1的NGAP连接可暂时被去激活。
步骤802，如图8c所示，当卫星2进入到跨不同地面站AMF的边界区域时，卫星2和AMF1的NGAP连接可被重新激活，此时卫星2通过RAN Configuration Update流程向AMF2告知：小区8已离开了覆盖区域2，剩下的小区5,6,7还处在覆盖区域2之中；同时卫星2还通过RAN Configuration Update流程向AMF1告知：小区8已进入了覆盖区域1内；同理卫星1也会通过RAN Configuration Update流程向AMF1告知：小区4已离开了覆盖区域1，剩下的小区1,2,3还处在覆盖区域1之中。通过上述流程，AMF1可得知小区8进入了自己所辖的覆盖区域1内，可以被AMF1自己所辖，因此当UE在旧服务小区1触发了移动切 换流程，在NG-RAN接入网络侧，仅需要将UE AS Context从卫星1转移到卫星2，但在5GC核心侧，UE NAS Context不需要从AMF1转移到AMF2，即UE NAS Context继续保持在AMF1内。
另外，由于小区8离开覆盖区域2进入覆盖区域1，是个连续渐变的过程，因此存在一段过渡时间，小区8同时跨了覆盖区域2和覆盖区域1，因此小区8也可和两个覆盖区域1和2同时关联，同时被AMF1和AMF2共同所辖和使用。
步骤803，随着卫星2沿着轨道继续向下移动，小区7,6,5逐步地离开覆盖区域2而进入到覆盖区域1之中，卫星2会继续通过RAN Configuration Update流程向AMF2告知：最新本地服务小区和覆盖区域2之间的重关联信息；同时卫星1也会继续通过RAN Configuration Update流程向AMF1告知：最新本地服务小区和覆盖区域1之间的重关联信息。因此即使当UE在旧服务小区再次触发了移动切换流程，在NG-RAN接入网络侧，UE AS Context可一直保存在卫星2内，而在5GC核心侧，UE NAS Context也可一直保持在AMF1内。
由此可见，只要UE静止处于AMF1所辖的覆盖区域1内，虽然由于服务小区的切换，UE AS Context会在不同的服务卫星之间转移，但UE NAS Context能够被一直被维持在AMF1内，这就避免了因为服务卫星不断切换而导致的AMF锚点重定位迂回。
步骤804，如图8c所示，随着卫星2沿着轨道继续向下移动，最上面的小区5也离开了覆盖区域2而进入到覆盖区域1之中，此时卫星2基本处于覆盖区域1的中心上空位置，小区5,6,7,8全部仅和覆盖区域1相关联，因此可全部被AMF1所辖。此时卫星2还可通过RAN Configuration Update流程向AMF2发起NGAP连接去激活，即卫星2仅保持和AMF1的NGAP连接激活，这回到了类似图8a中卫星1的初始状态。
本申请实施例三的方案，可以避免UE NAS Context在不同锚点地面站AMF之间的迂回转移，从而减少相关的UE切换流程信令，减轻对用户业务中断等不良的影响。
实施例四
本实施例四中，本地小区集合仅包括一个小区，即一个小区即为一个本地小区集合；第一移动节点为装载着gNB-DU功能的LEO地球低轨卫星；对端网 络节点为gNB CU；第一移动节点与对端网络节点的链路连接为F1接口连接。
图9a为本申请实施例四提供的DU型卫星通讯系统架构的示意图，如图9a所示，在DU型卫星通讯系统中，多颗LEO地球低轨卫星上装载着gNB-DU功能，它们在空间沿着特定的同一轨道绕地球周期的运行。地面上的某终端UE(假设在地面准静止不动，且处于RRC连接态)当前处于gNB-CU1管辖的地面规划覆盖区域1中，UE当前的服务小区是卫星1所辖的小区1，UE通过Service link和空间DU型卫星1，直接进行无线通讯，而LEO卫星各自通过Feeder link，和地面站gNB-CU集合中的gNB-CU分别建立F1接口连接，包括F1-C信令F1AP连接和F1-U数据连接。
基于传统的节点之间连接管理的方案，在图9a中，卫星1当前连接于地面站gNB-CU1，卫星2连接于地面站gNB-CU2(注：在某些空间位置，卫星1/2也可能连接于同一个地面站gNB-CU)。随着卫星沿着特定的轨道继续向下移动，卫星2所辖的多个服务小区8,7,6,5会逐步地离开地面规划覆盖区域2，而向地面规划覆盖区域1内移动，如图9b所示：小区8已从原来的旧覆盖区域2移动到了gNB-CU1所辖的新覆盖区域1之内，同理下面卫星2的小区4也相应的移出了原来的旧覆盖区域1。根据连接态UE无线链路移动管理的需求，当UE监测发现旧小区1的服务信号越来越弱，而新小区8的服务信号越来越强，UE会触发网络去执行移动切换流程，网络尝试把UE从旧服务小区1切换到新服务小区8。成功切换的结果是：在NG-RAN接入网络侧，UE无线DU上下文(UE AS-DU Context)从卫星1转移到卫星2内，同时UE无线CU上下文(UE AS-CU Context)暂时从gNB-CU1转移到gNB-CU2内(因为卫星2一直被gNB-CU2所辖)。再经过一段时间之后，当卫星2完全移动到覆盖区域1的中心上空(此时卫星2的位置和图9a中的卫星1的类似)，此时卫星2会发起向新地面站gNB-CU1的F1接口建立流程，而同时删除和旧地面站gNB-CU2的F1接口，从而卫星2所辖的小区5,6,7,8用来对覆盖区域1覆盖。由于卫星2的锚点gNB-CU网元gNB-CU2->gNB-CU1重定位(gNB-CU Relocation)，此时尽管卫星2能继续保留UE AS-DU Context，但UE AS-CU Context还需要再从gNB-CU2重新转移回到gNB-CU1，这就造成了UE无线CU上下文UE AS-CU Context在不同地面站gNB-CU之间的迂回转移。
为此，本申请实施例四提出了一种新的节点之间连接管理的方案，该方案 包括：
步骤901，初始每颗卫星，例如卫星2和多个不同的地面站gNB-CU1和gNB-CU2提前建立好各自的F1AP连接，且彼此通过F1 Setup流程，同步交互好各自的本地服务小区能力配置信息等，本地服务小区能力配置信息包括：当前本地服务小区覆盖和不同地面规划覆盖区域之间的关联信息。在卫星2完全处于地面规划覆盖区域2的中心上空的情况下，此时小区5,6,7,8全部仅和覆盖区域2相关联，因此全部被gNB-CU2所辖，因此卫星2可仅保持和锚点gNB-CU2的F1AP连接激活，但和gNB-CU1的F1AP连接可暂时被去激活。
步骤902，如图9c所示，在卫星2进入到跨不同地面站gNB-CU的边界区域的情况下，卫星2和gNB-CU1的F1AP连接可被重新激活，此时卫星2通过gNB-DU Configuration Update流程向gNB-CU2告知：小区8已离开了覆盖区域2，剩下的小区5,6,7还处在覆盖区域2之中；同时卫星2还通过gNB-DU Configuration Update流程向gNB-CU1告知：小区8已进入了覆盖区域1内；同理卫星1也会通过gNB-DU Configuration Update流程向AMF1告知：小区4已离开了覆盖区域1，剩下的小区1,2,3还处在覆盖区域1之中。通过上述流程，gNB-CU1可得知小区8进入了自己所辖的覆盖区域1内，可以被gNB-CU1自己所辖，因此当UE在旧服务小区1触发了移动切换流程，在NG-RAN接入网络侧，仅需要将UE AS-DU Context从卫星1转移到卫星2，UE AS-CU Context不需要从gNB-CU1转移到gNB-CU2，即UE AS-CU Context继续保持在gNB-CU1内。
另外，由于小区8离开覆盖区域2进入覆盖区域1，是个连续渐变的过程，因此存在一段过渡时间，小区8同时跨了覆盖区域2和覆盖区域1，因此小区8也可和两个覆盖区域1和2同时关联，同时被gNB-CU1和gNB-CU2共同所辖和使用。
步骤903，随着卫星2沿着轨道继续向下移动，小区7,6,5逐步地离开覆盖区域2而进入到覆盖区域1之中，卫星2会继续通过gNB-DU Configuration Update流程向gNB-CU2告知：最新本地服务小区和覆盖区域2之间的重关联信息；同时卫星1也会继续通过gNB-DU Configuration Update流程向gNB-CU1告知：最新本地服务小区和覆盖区域1之间的重关联信息。因此即使当UE在旧服务小区再次触发了移动切换流程，在NG-RAN接入网络侧，UE AS-DU Context 可一直保存在卫星2内，UE AS-CU Context也可一直保持在gNB-CU1内。
由此可见，只要UE静止处于gNB-CU1所辖的覆盖区域1内，虽然由于服务小区的切换，UE AS-DU Context会在不同的服务卫星之间转移，但UE AS-CU Context能够被一直被维持在gNB-CU1内，这就避免了因为服务卫星不断切换而导致的gNB-CU锚点重定位迂回。
步骤904，如图9c所示，随着卫星2沿着轨道继续向下移动，最上面的小区5也离开了覆盖区域2而进入到覆盖区域1之中，此时卫星2基本处于覆盖区域1的中心上空位置，小区5,6,7,8全部仅和覆盖区域1相关联，因此可全部被gNB-CU1所辖。此时卫星2还可通过gNB-DU Configuration Update流程向gNB-CU2发起F1AP连接去激活，即卫星2仅保持和gNB-CU1的F1AP连接激活，这回到了类似图9a中卫星1的初始状态。
本实施例四提供的方案，可以避免UE AS-CU Context在不同锚点地面站gNB-CU之间的迂回转移，从而减少相关的UE切换流程信令，减轻对用户业务中断等不良的影响。
实施例五
本实施例五中，本地小区集合仅包括一个小区，即一个小区即为一个本地小区集合；第一移动节点为装载着Full gNB功能的无人机基站；对端网络节点为接入移动功能节点AMF；第一移动节点与对端网络节点的链路连接为NG接口连接。
图10a为本申请实施例五提供的空中无人机基站通讯系统架构的示意图。如图10a所示：在空中无人机基站通讯系统中，无人机基站1上装载着Full gNB功能，它在天空中沿着随机的轨迹移动运行。无人机基站1通过Feeder link，和地面站5GC集合中的AMF/SMF/UPF建立NG接口连接，包括NG-C信令NGAP连接和NG-U数据连接。图10a中无人机基站1的四个本地服务小区1,2,3,4对地面规划覆盖区域1进行覆盖，某准静止的终端UE(处于RRC空闲态)处于地面规划覆盖区域2内，因此暂时不能被无人机基站1进行寻呼Paging和彼此直接通讯。(另外，UE也可以同时被其它的无人机基站服务，但图10a中未呈现)。
基于传统的节点之间连接管理的方案，在图10a中，无人机基站1当前连 接于锚点地面站AMF1。随着无人机基站随机向下移动，无人机基站1所辖的多个服务小区1,2,3,4会逐步地离开地面规划覆盖区域1，而向地面规划覆盖区域2内移动。如图10b所示：小区1,2已从原来的旧覆盖区域1移动到了AMF2所辖的新覆盖区域2之内。根据空闲态UE寻呼管理的需求，AMF2需要知道当前有哪些无人机基站和其本地服务小区可以为覆盖区域2内的UE服务，否则在UE有下行信令/数据抵达而触发AMF2进行NG接口寻呼的情况下，AMF2不能找到合适的无人机基站去承担空口寻呼任务。因此当无人机基站1移动到新覆盖区域，需要及时进行本地服务小区覆盖和覆盖区域的重关联，并且更新上报给AMF，以同步端到端可用的无线网络链路。
为此，本申请实施例五提出了一种新的节点之间连接管理的方案，该方案包括：
步骤1001，初始每架无人机基站，例如无人机基站1和多个不同的地面站AMF1和AMF2提前建立好各自的NGAP连接，且彼此通过NG Setup流程，同步交互好各自的本地服务小区能力配置信息等，本地服务小区能力配置信息包括：当前本地服务小区覆盖和不同地面规划覆盖区域之间的关联信息。在无人机基站1完全处于地面规划覆盖区域1的中心上空的情况下，此时小区1,2,3,4全部仅和地面规划覆盖区域1相关联，因此全部被AMF1所辖，因此无人机基站1可仅保持和锚点AMF1的NGAP连接激活，但和AMF2的NGAP连接可暂时被去激活。
步骤1002，如图10c所示，在无人机基站1进入到跨不同地面站AMF的边界区域的情况下，无人机基站1和AMF2的NGAP连接可被重新激活，此时无人机基站1通过RAN Configuration Update流程向AMF1告知：小区1,2已离开了覆盖区域1，剩下的小区3,4还处在覆盖区域1之中；同时无人机基站1还通过RAN Configuration Update流程向AMF2告知：小区1,2已进入了覆盖区域2内。通过上述流程，AMF2可得知小区1,2进入到了自己所辖的覆盖区域2内，因此可以被AMF2自己所辖和使用，因此当UE有下行信令/数据抵达而触发AMF2进行NG接口寻呼，AMF2可利用无人机基站1去承担空口寻呼任务。
另外，由于小区1,2离开覆盖区域1进入覆盖区域2，是个连续渐变的过程，因此存在一段过渡时间，小区1,2同时跨了覆盖区域1和覆盖区域2，因此小区1,2也可和两个覆盖区域1和2同时关联，同时被AMF1和AMF2共同所辖和使 用。
步骤1003，随着无人机基站1继续的随机移动，本地服务小区1,2,3,4会和覆盖区域1和2继续发生重关联，无人机基站1会继续通过RAN Configuration Update流程向AMF1告知：最新本地服务小区和覆盖区域1之间的重关联信息；同时无人机基站1也会继续通过RAN Configuration Update流程向AMF2告知：最新本地服务小区和覆盖区域2之间的重关联信息。
步骤1004，如图10c所示，假设无人机基站1继续向下移动，当本地服务小区1,2,3,4全部离开了覆盖区域1而进入到覆盖区域2之中，此时无人机基站1基本处于覆盖区域2的中心上空位置，小区1,2,3,4全部仅和覆盖区域2相关联，因此可全部被AMF2所辖管理。此时无人机基站1还可通过RAN Configuration Update流程向AMF1发起NGAP连接去激活，即无人机基站1仅保持和AMF2的NGAP连接激活，这回到了类似图10a中无人机基站1的初始状态。
本实施例五提供的技术方案，可以避免AMF2无法及时识别当前辖区内可用的无人机基站和其本地服务小区，从而失去可能服务AMF2覆盖辖区内UE的机会，因此可以提升无人机基站资源的利用率和UE的被服务体验。
上述实施例三、四、五中的连接在符合预设条件时可以被删除，即通讯对端两个节点删除掉旧连接配置和相应端口资源。所述预设条件可以为旧连接处于去激活状态持续超过预设时限、旧连接一端的移动节点的服务小区位置与另一端的网络节点的覆盖跟踪区域范围的边缘位置的差值超过预设阈值，等等。
实施例六
图11为本申请实施例六提供的第一移动节点的结构示意图，如图11所示，该第一移动节点，包括：
建立单元，设置为通过网络接口建立Setup流程，分别与多个对端网络节点建立链路连接。
在一实施例中，所述链路连接包括如下至少之一：控制面信令连接和用户面数据连接。
在一实施例中，所述建立单元，包括：
划分单元，设置为将所述第一移动节点下属的多个本地服务小区划分为多个本地小区集合；
发起和交互单元，设置为每一个本地小区集合通过对应的网络接口发起和所述多个对端网络节点中的至少两个对端网络节点的链路连接建立Setup流程，并交互各自的配置信息。
在一实施例中，所述配置信息包括如下至少之一：本地小区集合的本地能力、本地小区集合的资源配置和本地小区集合的无线覆盖相关信息。
在一实施例中，在建立Setup流程并交互各自的配置信息之后，所述多个本地小区集合中不同的本地小区集合被不同的对端网络节点所管辖；
或者，所述多个本地小区集合中同一个本地小区集合被不同的对端网络节点所同时管辖。
在一实施例中，在所述第一移动节点下属的全部本地小区集合完全处于所述多个对端网络节点中第二对端网络节点管辖的第二覆盖跟踪区域范围内的情况下，所述第一移动节点与所述第二对端网络节点之间的第二链路连接处于激活状态，所述第一移动节点与所述多个对端网络节点中除了第二对端网络节点之外的其他对端网络节点之间的其他链路连接处于去激活状态，所述第一移动节点归所述第二对端网络节点管辖。
在一实施例中，如图11所示，该第一移动节点，还包括：激活单元；
所述激活单元，设置为在所述第一移动节点归所述第二对端网络节点管辖之后，且在所述第一移动节点下属的至少一个本地小区集合进入所述多个对端网络节点中第一对端网络节点管辖的第一覆盖跟踪区域范围内的情况下，则激活所述第一移动节点与第一对端网络节点之间已建立的第一链路连接，所述第一移动节点和其下属的所述至少一个本地小区集合同时归属所述第二对端网络节点和所述第一对端网络节点共同管辖。
在一实施例中，所述激活所述第一移动节点与第一对端网络节点之间已建立的第一链路连接，包括：
发起传输层TNL链路关联，向所述第一对端网络节点发起节点配置更新Configuration Update流程，通过与所述第一对端网络节点已建立的第一链路连接向所述第一对端网络节点告知所述至少一个本地小区集合已进入所述第一覆 盖跟踪区域范围内和所述第一移动节点下属的本地小区集合的信息。
在一实施例中，所述激活单元，还设置为向所述第二对端网络节点发起节点配置更新Configuration Update流程，通过与所述第二对端网络节点已建立的第二链路连接向所述第二对端网络节点告知所述至少一个本地小区集合已离开所述第二覆盖跟踪区域范围内和所述第一移动节点下属的除了所述至少一个本地小区集合之外的本地小区集合的信息。
在一实施例中，所述激活单元，还设置为在所述第一移动节点同时归属所述第二对端网络节点和所述第一对端网络节点共同管辖之后，且所述第一移动节点下属的全部本地小区集合离开所述第二覆盖跟踪区域范围内的情况下，则暂时关闭传输层TNL链路的关联，从而去激活所述第二链路连接，所述第一移动节点和其下属所有的本地小区集合仅归所述第一对端网络节点管辖。
在一实施例中，所述去激活所述第二链路连接，包括：
向所述第二对端网络节点发起节点配置更新Configuration Update流程，通过与所述第二对端网络节点已建立的第二链路连接向所述第二对端网络节点告知所述第一移动节点下属的全部本地小区集合离开所述第二覆盖跟踪区域范围内，但所述第二对端网络节点仍然保持接口链路连接的配置上下文信息，以待所述第一移动节点后续再次TNL链路关联激活。
在一实施例中，该第一移动节点，还包括：转移单元；
所述转移单元，设置为在第一UE触发移动切换流程从所述第一移动节点下属的第一本地小区集合切换到第二移动节点下属的第二本地小区集合，且所述第一本地小区集合和第二本地小区集合都处于所述多个对端网络节点中第一对端网络节点管辖的第一覆盖跟踪区域范围内的情况下，仅将所述第一UE的无线接入层通讯上下文UE AS Context从所述第一移动节点转移到所述第二移动节点，并一直保持并维护UE非无线接入层通讯上下文UE NAS Context在所述第一对端网络节点内。
在一实施例中，该第一移动节点，还包括：保存单元；
所述保存单元，设置为当第一UE停留在第一对端网络节点管辖的第一覆盖跟踪区域范围内，则一直保存所述第一UE的非无线接入层通讯上下文UE NAS Context；只有当所述第一UE移动到第一对端网络节点管辖的第一覆盖跟踪区 域范围之外，则由目标对端网络节点保存迁移后的UE NAS Context。
在一实施例中，所述移动节点为移动式NG-RAN基站，所述对端网络节点为5GC网络节点，所述链路连接为NGAP连接实例；
或者，所述移动节点为移动式NG-RAN基站，所述对端网络节点为移动式NG-RAN基站，所述链路连接为XnAP连接实例；
或者，所述移动节点为分布式处理单元DU，所述对端网络节点为集中式处理单元CU，所述链路连接为F1AP连接实例。
在一实施例中，所述5GC网络节点为以下之一：接入管理功能节点AMF、会话管理功能节点SMF、用户面功能节点UPF；
所述移动式NG-RAN基站为以下之一：基于4G eNB继续演进的ng-eNB、全新物理层空口设计的gNB、装载着Full gNB功能的LEO地球低轨卫星和装载着Full gNB功能的无人机基站；
移动式NG-RAN基站内的集中式处理单元CU为：NG-RAN分离式基站gNB-CU；
移动式NG-RAN基站内的分布式处理单元DU为以下之一：NG-RAN分离式基站gNB-DU和装载着gNB-DU功能的LEO地球低轨卫星。
实施例七
图12为本申请实施例七提供的一种节点之间连接管理的系统的结构示意图，如图12所示，该系统包括：
第一移动节点和多个对端网络节点；
所述第一移动节点，设置为通过网络接口建立Setup流程，分别与所述多个对端网络节点建立链路连接。
在一实施例中，所述链路连接包括如下至少之一：控制面信令连接和用户面数据连接。
在一实施例中，所述第一移动节点，设置为通过网络接口建立Setup流程，分别与多个对端网络节点建立链路连接，包括：
所述第一移动节点将下属的多个本地服务小区划分为多个本地小区集合；
每一个本地小区集合通过对应的网络接口发起和所述多个对端网络节点中的至少两个对端网络节点的链路连接建立Setup流程，并交互各自的配置信息。
在一实施例中，所述配置信息包括如下至少之一：本地小区集合的本地能力、本地小区集合的资源配置和本地小区集合的无线覆盖相关信息。
在一实施例中，在建立Setup流程并交互各自的配置信息之后，该方法还包括：
所述多个本地小区集合中不同的本地小区集合被不同的对端网络节点所管辖；
或者，所述多个本地小区集合中同一个本地小区集合被不同的对端网络节点所同时管辖。
在一实施例中，在所述第一移动节点下属的全部本地小区集合完全处于所述多个对端网络节点中第二对端网络节点管辖的第二覆盖跟踪区域范围内的情况下，所述第一移动节点与所述第二对端网络节点之间的第二链路连接处于激活状态，所述第一移动节点与所述多个对端网络节点中除了第二对端网络节点之外的其他对端网络节点之间的其他链路连接处于去激活状态，所述第一移动节点归所述第二对端网络节点管辖。
在一实施例中，在所述第一移动节点归所述第二对端网络节点管辖之后，且在所述第一移动节点下属的至少一个本地小区集合进入所述多个对端网络节点中第一对端网络节点管辖的第一覆盖跟踪区域范围内的情况下，则所述第一移动节点，还设置为激活所述第一移动节点与第一对端网络节点之间已建立的第一链路连接，此时所述第一移动节点和其下属的所述至少一个本地小区集合同时归属所述第二对端网络节点和所述第一对端网络节点共同管辖。
在一实施例中，所述激活所述第一移动节点与第一对端网络节点之间已建立的第一链路连接，包括：
发起传输层TNL链路关联，向所述第一对端网络节点发起节点配置更新Configuration Update流程，通过与所述第一对端网络节点已建立的第一链路连接向所述第一对端网络节点告知所述至少一个本地小区集合已进入所述第一覆盖跟踪区域范围内和所述第一移动节点下属的本地小区集合的信息。
在一实施例中，所述第一移动节点，还设置为向所述第二对端网络节点发 起节点配置更新Configuration Update流程，通过与所述第二对端网络节点已建立的第二链路连接向所述第二对端网络节点告知所述至少一个本地小区集合已离开所述第二覆盖跟踪区域范围内和所述第一移动节点下属的除了所述至少一个本地小区集合之外的本地小区集合的信息。
在一实施例中，在所述第一移动节点同时归属所述第二对端网络节点和所述第一对端网络节点共同管辖之后，在所述第一移动节点下属的全部本地小区集合离开所述第二覆盖跟踪区域范围内的情况下，则所述第一移动节点，还设置为暂时关闭传输层TNL链路的关联，从而去激活所述第二链路连接，所述第一移动节点和其下属所有的本地小区集合仅归所述第一对端网络节点管辖。
在一实施例中，所述去激活所述第二链路连接，包括：
向所述第二对端网络节点发起节点配置更新Configuration Update流程，通过与所述第二对端网络节点建立的第二链路连接向所述第二对端网络节点告知所述第一移动节点下属的全部本地小区集合离开所述第二覆盖跟踪区域范围内，但所述第二对端网络节点仍然保持接口链路连接的配置上下文信息，以待所述第一移动节点后续再次TNL链路关联激活。
在一实施例中，该系统还包括第二移动节点，
在第一UE触发移动切换流程从所述第一移动节点下属的第一本地小区集合切换到第二移动节点下属的第二本地小区集合，且所述第一本地小区集合和第二本地小区集合都处于所述多个对端网络节点中第一对端网络节点管辖的第一覆盖跟踪区域范围内的情况下，所述第一移动节点，还设置为仅将所述UE的无线接入层通讯上下文UE AS Context从所述第一移动节点转移到所述第二移动节点，并一直保持并维护UE非无线接入层通讯上下文UE NAS Context在所述第一对端网络节点内。
在一实施例中，所述第一移动节点，还设置为当第一UE停留在第一对端网络节点管辖的第一覆盖跟踪区域范围内，则一直保存所述第一UE的非无线接入层通讯上下文UE NAS Context；只有当所述第一UE移动到第一对端网络节点管辖的第一覆盖跟踪区域范围之外，则由目标对端网络节点保存迁移后的UE NAS Context。
在一实施例中，所述移动节点为移动式NG-RAN基站，所述对端网络节点 为5GC网络节点，所述链路连接为NGAP连接实例；
或者，所述移动节点为移动式NG-RAN基站，所述对端网络节点为移动式NG-RAN基站，所述链路连接为XnAP连接实例；
或者，所述移动节点为分布式处理单元DU，所述对端网络节点为集中式处理单元CU，所述链路连接为F1AP连接实例。
在一实施例中，所述5GC网络节点为以下之一：接入管理功能节点AMF、会话管理功能节点SMF和用户面功能节点UPF；
所述移动式NG-RAN基站为以下之一：基于4G eNB继续演进的ng-eNB、全新物理层空口设计的gNB、装载着Full gNB功能的LEO地球低轨卫星和装载着Full gNB功能的无人机基站；
移动式NG-RAN基站内的集中式处理单元CU为：NG-RAN分离式基站gNB-CU；
移动式NG-RAN基站内的分布式处理单元DU为以下之一：NG-RAN分离式基站gNB-DU和装载着gNB-DU功能的LEO地球低轨卫星。
本申请实施例还提供了一种第一移动节点，包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现上述任一节点之间链路连接管理的方法。
本申请实施例还提供了一种计算机可读存储介质，所述计算机可读存储介质上存储有信息处理程序，所述信息处理程序被处理器执行时实现上述任一所述的节点之间链路连接管理的方法。
本申请实施例提供的技术方案，实现了对移动式基站接口多连接管理的方式方法，使得在移动式基站构建的网络环境下，能高效建立和维护移动网元节点/服务小区和对端网元节点之间的TNL传输承载和上层RNL应用协议层连接，从而尽量保证网络NG，F1，Xn等接口能及时和移动式基站的动态拓扑之间匹配适应，尽量减少NG，F1，Xn等接口无为的TNL/RNL层接口重建和接口服务中断，提升系统对移动式基站资源的利用率。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。 在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由多个物理组件合作执行。某些组件或所有组件可以被实施为由处理器，如数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM(Random Access Memory，随机存取存储器)、ROM(Read-Only Memory，只读存储器)、EEPROM(Electrically Erasable Programmable read only memory，带电可擦可编程只读存储器)、闪存或其他存储器技术、CD-ROM(Compact Disc Read-Only Memory，光盘只读存储器)、数字多功能盘(Digital Video Disc，DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。

Claims (19)

  1. 一种节点之间链路连接管理的方法，包括：
    第一移动节点通过网络接口建立Setup流程，分别与多个对端网络节点建立链路连接。
  2. 根据权利要求1所述的方法，其中，
    所述链路连接包括如下至少之一：控制面信令连接和用户面数据连接。
  3. 根据权利要求1所述的方法，其中，所述第一移动节点通过网络接口建立Setup流程，分别与多个对端网络节点建立链路连接，包括：
    所述第一移动节点将下属的多个本地服务小区划分为多个本地小区集合；
    每一个本地小区集合通过对应的网络接口发起和所述多个对端网络节点中的至少两个对端网络节点的链路连接建立Setup流程，并交互各自的配置信息。
  4. 根据权利要求3所述的方法，其中，
    所述配置信息包括如下至少之一：本地小区集合的本地能力、本地小区集合的资源配置和本地小区集合的无线覆盖相关信息。
  5. 根据权利要求3所述的方法，其中，在交互各自的配置信息之后，该方法还包括：
    所述多个本地小区集合中不同的本地小区集合被不同的对端网络节点所管辖；
    或者，所述多个本地小区集合中同一个本地小区集合被不同的对端网络节点所同时管辖。
  6. 根据权利要求3所述的方法，其中，在所述第一移动节点与第一对端网络节点建立第一链路连接之后，所述方法还包括：
    在所述第一移动节点下属的全部本地小区集合完全处于所述多个对端网络节点中第二对端网络节点管辖的第二覆盖跟踪区域范围内的情况下，所述第一移动节点与所述第二对端网络节点之间的第二链路连接处于激活状态，所述第一移动节点与所述多个对端网络节点中除了第二对端网络节点之外的其他对端网络节点之间的其他链路连接处于去激活状态，所述第一移动节点归所述第二对端网络节点管辖。
  7. 根据权利要求6所述的方法，其中，在所述第一移动节点归所述第二对端网络节点管辖之后，该方法还包括：
    在所述第一移动节点下属的至少一个本地小区集合进入所述多个对端网络节点中所述第一对端网络节点管辖的第一覆盖跟踪区域范围内的情况下，则激活所述第一移动节点与所述第一对端网络节点之间已建立的所述第一链路连接，此时所述第一移动节点和其下属的所述至少一个本地小区集合同时归属所述第二对端网络节点和所述第一对端网络节点共同管辖。
  8. 根据权利要求7所述的方法，其中，所述激活所述第一移动节点与所述第一对端网络节点之间已建立的第一链路连接，包括：
    所述第一移动节点发起传输层TNL链路关联，向所述第一对端网络节点发起节点配置更新Configuration Update流程，通过与所述第一对端网络节点已建立的所述第一链路连接向所述第一对端网络节点告知所述至少一个本地小区集合已进入所述第一覆盖跟踪区域范围内和所述第一移动节点下属的所述至少一个本地小区集合的信息。
  9. 根据权利要求8所述的方法，还包括：
    所述第一移动节点向所述第二对端网络节点发起节点配置更新Configuration Update流程，通过与所述第二对端网络节点已建立的所述第二链路连接向所述第二对端网络节点告知所述至少一个本地小区集合已离开所述第二覆盖跟踪区域范围内和所述第一移动节点下属的除了所述至少一个本地小区集合之外的本地小区集合的信息。
  10. 根据权利要求7所述的方法，其中，在所述第一移动节点同时归属所述第二对端网络节点和所述第一对端网络节点共同管辖之后，该方法还包括：
    在所述第一移动节点下属的全部本地小区集合离开所述第二覆盖跟踪区域范围内的情况下，则暂时关闭所述传输层TNL链路的关联，并去激活所述第二链路连接，所述第一移动节点和其下属所有的本地小区集合仅归所述第一对端网络节点管辖。
  11. 根据权利要求10所述的方法，其中，所述去激活所述第二链路连接，包括：
    所述第一移动节点向所述第二对端网络节点发起节点配置更新 Configuration Update流程，通过与所述第二对端网络节点已建立的第二链路连接向所述第二对端网络节点告知所述第一移动节点下属的全部本地小区集合离开所述第二覆盖跟踪区域范围内，但所述第二对端网络节点仍然保持接口链路连接的配置上下文信息，以待所述第一移动节点后续再次发起传输层TNL链路关联。
  12. 根据权利要求1所述的方法，还包括：
    在第一UE触发移动切换流程从所述第一移动节点下属的第一本地小区集合切换到第二移动节点下属的第二本地小区集合，且所述第一本地小区集合和第二本地小区集合都处于所述多个对端网络节点中第一对端网络节点管辖的第一覆盖跟踪区域范围内的情况下，仅将所述第一UE的无线接入层通讯上下文UE AS Context从所述第一移动节点转移到所述第二移动节点，并一直保持并维护所述第一UE的非无线接入层通讯上下文UE NAS Context在所述第一对端网络节点内。
  13. 根据权利要求1所述的方法，还包括：
    在第一UE停留在第一对端网络节点管辖的第一覆盖跟踪区域范围的情况下，所述第一对端网络节点一直保存所述第一UE的非无线接入层通讯上下文UE NAS Context；只有当所述第一UE移动到所述第一对端网络节点管辖的第一覆盖跟踪区域范围之外，则由目标对端网络节点保存迁移后的UE NAS Context。
  14. 根据权利要求1至13任一项所述的方法，其中，
    所述移动节点为移动式NG-RAN基站，所述对端网络节点为5GC网络节点，所述链路连接为NGAP连接实例；
    或者，所述移动节点为移动式NG-RAN基站，所述对端网络节点为移动式NG-RAN基站，所述链路连接为XnAP连接实例；
    或者，所述移动节点为分布式处理单元DU，所述对端网络节点为集中式处理单元CU，所述链路连接为F1AP连接实例。
  15. 根据权利要求14所述的方法，其中，
    所述5GC网络节点为以下之一：接入管理功能节点AMF、会话管理功能节点SMF和用户面功能节点UPF；
    所述移动式NG-RAN基站为以下之一：基于4G eNB继续演进的ng-eNB、全新物理层空口设计的gNB、装载着Full gNB功能的LEO地球低轨卫星和装载着Full gNB功能的无人机基站；
    移动式NG-RAN基站内的集中式处理单元CU为：NG-RAN分离式基站gNB-CU；
    移动式NG-RAN基站内的分布式处理单元DU为以下之一：NG-RAN分离式基站gNB-DU和装载着gNB-DU功能的LEO地球低轨卫星。
  16. 一种第一移动节点，包括：
    建立单元，设置为通过网络接口建立Setup流程，分别与多个对端网络节点建立链路连接。
  17. 一种节点之间链路连接管理的系统，包括；
    第一移动节点和多个对端网络节点；
    所述第一移动节点设置为执行上述权利要求1至15中任一项所述的方法。
  18. 一种移动节点，包括存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被所述处理器执行时实现如权利要求1至15中任一项所述的节点之间链路连接管理的方法。
  19. 一种计算机可读存储介质，存储有信息处理程序，所述信息处理程序被处理器执行时实现如权利要求1至15中任一项所述的节点之间链路连接管理的方法。
PCT/CN2019/101316 2018-09-28 2019-08-19 一种节点之间链路连接管理的方法及相关设备 Ceased WO2020063192A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US17/279,627 US12127281B2 (en) 2018-09-28 2019-08-19 Method for managing link connection between nodes, and related device
EP19864859.4A EP3860301B1 (en) 2018-09-28 2019-08-19 Methods and apparatuses for managing link connection between nodes, and related device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811142058.4 2018-09-28
CN201811142058.4A CN110536482B (zh) 2018-09-28 2018-09-28 一种节点之间链路连接管理的方法及相关设备

Publications (1)

Publication Number Publication Date
WO2020063192A1 true WO2020063192A1 (zh) 2020-04-02

Family

ID=68658943

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/101316 Ceased WO2020063192A1 (zh) 2018-09-28 2019-08-19 一种节点之间链路连接管理的方法及相关设备

Country Status (4)

Country Link
US (1) US12127281B2 (zh)
EP (1) EP3860301B1 (zh)
CN (1) CN110536482B (zh)
WO (1) WO2020063192A1 (zh)

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111836314A (zh) * 2019-04-22 2020-10-27 索尼公司 集中单元设备、用户设备、无线通信方法和存储介质
US12367775B2 (en) * 2019-07-17 2025-07-22 Aeronix, Inc. Unmanned aerial vehicle communications system
CN115398975B (zh) * 2020-04-07 2025-06-06 中兴通讯股份有限公司 用于侧链路中继通信的信令传输的系统和方法
WO2021217528A1 (zh) * 2020-04-29 2021-11-04 华为技术有限公司 一种数据通信方法及相关装置
CN121815340A (zh) * 2020-05-27 2026-04-07 华为技术有限公司 多链路试关联方法及相关装置
CN113891407B (zh) * 2020-07-03 2022-09-02 大唐移动通信设备有限公司 一种切换方法和设备
CN113938877B (zh) * 2020-07-13 2022-11-22 大唐移动通信设备有限公司 一种小区全局标识的配置方法、装置及存储介质
EP4247103A4 (en) * 2020-11-16 2023-12-06 Beijing Xiaomi Mobile Software Co., Ltd. METHOD AND APPARATUS FOR DETERMINING EARTH SATELLITE LINK INFORMATION
CN112559123A (zh) * 2020-11-18 2021-03-26 山东英特力光通信开发有限公司 一种基于动态资源池虚拟化技术的卫星地面接入站系统
CN114666860B (zh) * 2020-12-22 2024-04-05 大唐移动通信设备有限公司 回传路径切换方法、基站、装置及存储介质
WO2022170446A1 (zh) * 2021-02-09 2022-08-18 北京小米移动软件有限公司 一种卫星链路信息确定方法及装置
US12464584B2 (en) * 2023-02-09 2025-11-04 T-Mobile Usa, Inc. Low latency edge processing for drone wireless links
CN116056189B (zh) * 2023-04-03 2023-08-01 深圳简谱技术有限公司 手持移动式基站信号接入方法、移动基站及移动通信系统
WO2025169120A1 (en) * 2024-02-06 2025-08-14 Telefonaktiebolaget Lm Ericsson (Publ) Handling of xn connectivity for radio access network nodes with wireless backhaul
CN120456175A (zh) * 2024-02-08 2025-08-08 华为技术有限公司 通信方法和装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030235165A1 (en) * 2002-06-24 2003-12-25 Nec Corporation Mobile communication system, radio switching method, mobile base station and mobile terminal
WO2007004586A1 (ja) * 2005-06-30 2007-01-11 Matsushita Electric Industrial Co., Ltd. 移動通信制御方法、データ通信装置、移動基地局装置並びに移動端末
CN107295065A (zh) * 2017-05-17 2017-10-24 李坤煌 用于河流监测的控制系统与控制方法
CN108574969A (zh) * 2017-03-08 2018-09-25 华为技术有限公司 多接入场景中的连接处理方法和装置

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7599323B2 (en) * 2002-10-17 2009-10-06 Alcatel-Lucent Usa Inc. Multi-interface mobility client
EP2494843B1 (en) * 2009-10-28 2019-12-11 Nokia Solutions and Networks Oy Relayed communications in mobile environment
WO2013022067A1 (ja) * 2011-08-09 2013-02-14 三菱電機株式会社 移動体通信システム
CN103733683A (zh) * 2011-08-11 2014-04-16 交互数字专利控股公司 移动中继切换
WO2013070244A1 (en) * 2011-11-11 2013-05-16 Research In Motion Limited Method and system for mobile relay enablement
GB2503719A (en) * 2012-07-05 2014-01-08 Nec Corp Providing information relating to a location of a user device in a cell configured as a mobile cell
CN109769278A (zh) * 2012-09-28 2019-05-17 三菱电机株式会社 移动通信系统
SG11201803286SA (en) * 2015-10-28 2018-05-30 Worldvu Satellites Ltd Satellite system having increased communications capacity and methods for increasing the capacity of satellite systems
US10779346B2 (en) * 2017-03-27 2020-09-15 Qualcomm Incorporated Local area data network connectivity
CN108924894B (zh) * 2017-04-11 2023-09-29 华为技术有限公司 一种移动性管理方法、接入网设备和终端设备
WO2019013543A1 (ko) * 2017-07-14 2019-01-17 주식회사 케이티 차세대 무선네트워크를 위한 캐리어 병합 제어 방법 및 장치
WO2019039987A1 (en) * 2017-08-21 2019-02-28 Telefonaktiebolaget Lm Ericsson (Publ) METHOD OF COUNTING DEVICES
CN109688631B (zh) * 2017-10-19 2021-11-19 中国移动通信有限公司研究院 一种连接处理方法和设备
CN107707292B (zh) * 2017-11-07 2023-10-27 海南大学 基于无人船基站组网的lte海上应急通信系统
CN108337663B (zh) * 2017-12-13 2019-08-23 杭州容大智造科技有限公司 一种汽车移动基站系统及控制方法
CN111512694A (zh) * 2017-12-25 2020-08-07 高通股份有限公司 自主无线接入网络通知区域配置
US10849035B2 (en) * 2018-07-26 2020-11-24 EMC IP Holding Company LLC Sharing of context among base station nodes for mobility management in mobile communications network

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030235165A1 (en) * 2002-06-24 2003-12-25 Nec Corporation Mobile communication system, radio switching method, mobile base station and mobile terminal
WO2007004586A1 (ja) * 2005-06-30 2007-01-11 Matsushita Electric Industrial Co., Ltd. 移動通信制御方法、データ通信装置、移動基地局装置並びに移動端末
CN108574969A (zh) * 2017-03-08 2018-09-25 华为技术有限公司 多接入场景中的连接处理方法和装置
CN107295065A (zh) * 2017-05-17 2017-10-24 李坤煌 用于河流监测的控制系统与控制方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3860301A4

Also Published As

Publication number Publication date
CN110536482B (zh) 2023-04-07
US20210392710A1 (en) 2021-12-16
EP3860301B1 (en) 2025-01-29
EP3860301A1 (en) 2021-08-04
CN110536482A (zh) 2019-12-03
US12127281B2 (en) 2024-10-22
EP3860301A4 (en) 2022-07-06

Similar Documents

Publication Publication Date Title
CN110536482B (zh) 一种节点之间链路连接管理的方法及相关设备
US11706829B2 (en) Method for data forwarding in a small cell system
US9775108B2 (en) Method and equipment for saving energy
CN111246596B (zh) 链路的确定、建立方法及装置，传输系统，卫星通讯系统
CN110536477B (zh) 连接方法、装置、网络设备及存储介质
US20190075497A1 (en) User equipment handover method and device
US9924550B2 (en) Dynamic LTE network
CN108282801A (zh) 一种基于移动边缘计算的切换管理方法
US12047457B2 (en) Session processing method and apparatus, network device and storage medium
KR102410198B1 (ko) 무선 인터페이스 비활성 상태 유지 방법 및 장치
WO2020015586A1 (zh) 控制信令的发送方法及装置、服务基站、存储介质
CN106162774B (zh) 跨MeNB切换方法、装置及基站
CN104936308B (zh) 一种双连接路径更新失败的处理方法与装置
RU2777403C1 (ru) Способ и устройство определения и установления соединения, система передачи и система спутниковой связи
US20210307105A1 (en) Systems and methods for maintaining mobile base station signal and data connections
Thainesh Radio access network (RAN) signalling architecture for dense mobile network

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19864859

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019864859

Country of ref document: EP

Effective date: 20210428