WO2020200261A1

WO2020200261A1 - Connecting method and apparatus, network device, and storage medium

Info

Publication number: WO2020200261A1
Application number: PCT/CN2020/082888
Authority: WO
Inventors: 杨立; 马子江; 方建民; 黄河
Original assignee: 中兴通讯股份有限公司
Priority date: 2019-04-03
Filing date: 2020-04-02
Publication date: 2020-10-08
Also published as: CN110536477A; CN110536477B

Abstract

The present application provides a connecting method and apparatus, a network device, and a storage medium. The connecting method comprises: sending a first indication message to a target secondary base station, the first indication message comprising first indication information for performing a designated operation on a secondary connection between the target secondary base station and a target terminal, and the designated operation comprising establishment, addition, modification, deletion, and release; and receiving a first response message from the target secondary base station, the first response message comprising first result information corresponding to the first indication information.

Description

Connection method, device, network equipment and storage medium

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office with an application number of 201910267440.6 on April 3, 2019. The entire content of the application is incorporated into this application by reference.

Technical field

This application relates to the field of communications, such as connection methods, devices, network equipment, and storage media.

Background technique

The third generation partnership project (3rd Generation Partnership Project, 3GPP) fourth generation land-based (4Generation, 4G) cellular mobile communication system or LTE (Long Term Evolution) cellular mobile communication system includes: 4G core network EPC (Evolved Packet Core, evolved packet core network) and RAN (Radio Access Network, radio access network). Among them, 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: eNB (evolved Node B, long-term evolution base station) and the interface between many base stations.

The fifth-generation land-based 5G cellular mobile communication system after 4G includes 5GC (5Generation Core, fifth-generation core network) and NG-RAN (Next Generation Radio Access Network, next-generation radio access network). Among them, 5GC includes: AMF (Access Mobility Function, access mobility function) node, SMF (Session Management Function, session management function) node, UPF (User Plane Function, user plane function) node and other network element nodes. NG-RAN includes at least two different RAT (Radio Access Technology) base stations, namely: ng-eNB based on 4G eNB continuous enhancement and evolution, and gNB base station designed with a new physical layer air interface. NG-RAN also includes interfaces between base stations and related network element entities. Among them, the ng-eNB air interface still supports the E-UTRA (evolved Universal Terrestrial Radio Access, evolved universal terrestrial radio access) RAT standard, and the gNB air interface supports the NR (New Radio, new radio) RAT standard.

When the UE is connected to multiple base stations of the access network at the same time for data transmission, it is necessary to rely on the interface between the primary base station and the core network and the Xn interface between the primary and secondary base stations to exchange information related to various dual-multiple connection operations. However, in some cases, the connection of the Xn interface is not fixed and the robustness is relatively low, which may easily cause multiple connections to be unstable or unable to be configured and operated.

Summary of the invention

In order to solve at least one technical problem described above, embodiments of the present application provide the following solutions.

The embodiment of the present application provides a connection method, including:

Send a first instruction message to the target secondary base station, where the first instruction message includes first instruction information for performing a designated operation on the secondary connection between the target secondary base station and the target terminal, and the designated operation includes Connection establishment, addition, modification, deletion or release;

Receiving a first response message from the target secondary base station, where the first response message includes first result information corresponding to the first indication information.

Receive a first instruction message from a core network element, where the first instruction message includes first instruction information for performing a specified operation on the secondary connection between the target secondary base station and the target terminal, and the specified operation includes Connection establishment, addition, modification, deletion or release;

Performing the specified operation on the secondary connection between the target secondary base station and the target terminal;

Send a first response message to the core network element, where the first response message includes first result information corresponding to the first indication message.

An embodiment of the present application provides a connection device, including:

The first sending module is configured to send a first indication message to the target secondary base station, where the first indication message includes first indication information for performing a specified operation on the secondary connection between the target secondary base station and the target terminal, and Specified operations include creation, addition, modification or deletion;

The first receiving module is configured to receive a first response message from the target secondary base station, where the first response message includes first result information corresponding to the first indication information.

The fifth receiving module is configured to receive a first instruction message from a core network element, where the first instruction message includes first instruction information for performing a specified operation on the secondary connection between the target secondary base station and the target terminal, and Specified operations include creation, addition, modification or deletion;

An execution module, configured to execute the specified operation on the secondary connection between the target secondary base station and the target terminal;

The fifth sending module is configured to send a first response message to the core network element, where the first response message includes first result information corresponding to the first indication message.

An embodiment of the present application provides a network device, the network device includes: a processor and a memory;

The memory is used to store instructions;

The processor is configured to read the instruction to execute the method described in any one of the embodiments of the present application.

An embodiment of the present application provides a storage medium that stores a computer program, and when the computer program is executed by a processor, the method described in any one of the embodiments of the present application is implemented.

The embodiments of the present application can directly instruct the target secondary base station to perform a designated operation on the secondary connection between the target secondary base station and the target terminal, which is beneficial to improve the flexibility of multi-connection operations.

Regarding the above embodiments and other aspects of the present application and their implementation manners, more descriptions are provided in the description of the drawings, specific implementation manners, and claims.

Description of the drawings

Figure 1 is an architecture diagram of an aggregated NG-RAN base station;

Figure 2 is a schematic diagram of heterogeneous networks deployed in macro and micro cells with different RAT standards;

Figure 3 is a schematic diagram of the MN mastering the UE dual connection operation;

4a and 4b are schematic diagrams of the UE in dual connection mode;

Figures 5a and 5b are schematic diagrams of changes in the coverage of a satellite base station serving cell;

Figure 6 is a schematic diagram of the establishment and maintenance of the feeder link of the satellite base station;

FIG. 7 is a schematic flowchart of a connection method provided by an embodiment of this application;

FIG. 8 is a schematic flowchart of a connection method provided by another embodiment of this application;

FIG. 9 is a schematic flowchart of a connection method provided by another embodiment of this application;

FIG. 10 is a schematic flowchart of a connection method provided by another embodiment of this application;

FIG. 11 is a schematic flowchart of a connection method provided by another embodiment of this application;

FIG. 12 is a schematic flowchart of a connection method provided by another embodiment of this application;

Figure 13 is an architecture diagram of a 5GC mastering UE for dual-connection data transmission operations;

Fig. 14a is a schematic diagram of an application example of dual connection between a UE and a satellite base station and a ground station;

Figure 14b is a schematic diagram of the MN initiating an adding process;

Fig. 15a is a schematic diagram of an application example of dual connection between a UE and a satellite base station and a ground station;

Figure 15b is a schematic diagram of the MN initiating a modification process;

Fig. 16a is a schematic diagram of an application example of dual connection between a UE and a satellite base station and a ground station;

Figure 16b is a schematic diagram of the MN initiating a deletion process;

Fig. 17a is a schematic diagram of an application example of dual connection between a UE and a satellite base station and a ground station;

Figure 17b is a schematic diagram of the 5GC initiating and adding process;

Fig. 18a is a schematic diagram of an application example of dual connection between a UE and a satellite base station and a ground station;

Figure 18b is a schematic diagram of the SN initiated modification process;

FIG. 19 is a schematic structural diagram of a connection device provided by an embodiment of this application;

20 is a schematic structural diagram of a connection device provided by another embodiment of this application;

FIG. 21 is a schematic structural diagram of a connection device provided by another embodiment of this application;

FIG. 22 is a schematic structural diagram of a connection device provided by another embodiment of this application;

FIG. 23 is a schematic structural diagram of a network device provided by an embodiment of this application;

FIG. 24 is a schematic structural diagram of a network device provided by an embodiment of this application;

FIG. 25 is a schematic structural diagram of a communication system provided by an embodiment of this application.

detailed description

Hereinafter, the embodiments of the present application will be described in detail with reference to the drawings. It should be noted that the embodiments in this application and the features in the embodiments can be combined with each other arbitrarily if there is no conflict.

Figure 1 is an architecture diagram of an Aggregated NG-RAN base station. As shown in Figure 1, many NG-RAN base stations (such as gNB or ng-eNB, etc.) are connected to each other through a standardized NG interface and 5GC. For example, including NG-C control plane (signaling) connection and NG-U user plane (user data) connection. NG-RAN base stations (gNB or ng-eNB) are connected to each other via Xn interfaces (including Xn-C control plane connection and Xn-U user plane connection). The control plane connection of the above interface is used to transmit control signaling messages between network element nodes, such as NGAP (Next Generation Application Protocol) and XnAP protocol process messages. The user plane connection is used to transmit user service data (packet/frame/block), etc. NGAP and XnAP are respectively NG-C and Xn-C control plane logic network application layer protocols, which are based on the lower layer bearer transmission (Stream Control Transmission Protocol (SCTP) connection) to transmit control signaling process messages on the corresponding interface . NG-U, Xn-U user plane interface user service data, based on the lower layer bearer transmission (such as GTP-U tunnel) to transmit the user service data on the corresponding interface. The NG-RAN base station and the served terminal UE are connected to each other through the Uu air interface (i.e., wireless air interface). The Uu air interface includes multiple air interface control plane signaling radio bearer (SRB) and multiple air interface user plane data radio bearer (DRB).

In the traditional land-based ground cellular mobile system, once the deployment of various base stations is determined, the physical location relative to a specific latitude and longitude on the ground is relatively static and fixed. Therefore, the configuration and provision of radio coverage/capacity (Coverage and Capacity) of the air interface Uu serving cell (Serving Cell) provided by each NG-RAN base station, as well as the NG and Xn interface examples connecting these NG-RAN neighboring base stations, etc., The relative physical location is also fixed. For example, most of the bearer transmission of interface connections such as NG and Xn are implemented through fixed network transmission methods such as broadband optical fibers. Therefore, the robustness, delay, signaling and data transmission efficiency of the network side interface connection The other aspects are relatively good. This relatively static and fixed land-based ground cellular mobile network is convenient for operators' planning and deployment and RRM (Radio Resource Management, radio resource management). As shown in Figure 2, in a heterogeneous large network with mixed deployment of macro and micro service cells, there may be various types of base stations with different RAT standards, different carrier frequencies and operating bandwidths, and different wireless coverage capabilities, such as: 4G legacy eNB , 5G gNB, ng-eNB, WLAN AP (Wireless Local Area Networks Access Point, wireless local area network access point) and other network element nodes, they can interact with each other.

The 5G system supports the terminal UE in SC (Single Connectivity, single connection) and DC/MC (Dual/Multiple Connectivity, dual/multiple connection) working modes. Among them, multi-connection is the logical dimension expansion of dual-connection, and the description of dual-connection DC will be the main description below. In the SC single connection working mode, the UE has only one signaling or data transmission channel on the air interface Uu and the network side, which is called a radio link (RL). In the DC/MC (dual/multiple) connection working mode, the UE has two or more signaling or data transmission channels on the air interface and the network side, that is, multiple relatively independent RLs. Under the control of RRC (Radio Resource Control) of the NG-RAN main control anchor main base station, multiple air interface signaling radio bearer SRB and data radio bearer DRB can be configured and used on the above dual/multiple RLs . As shown in Figure 3, in a specific physical area, MN (Master Node) is usually used to provide wireless macro coverage. In local hotspots or areas with weak coverage, many SNs (Secondary Nodes) are used to provide enhanced wireless micro coverage to improve the overall wireless capacity and performance of cellular heterogeneous networks.

Take the MR-DC (Multi-Radio Dual Connectivity) working mode supported by 5G related protocols as an example, for specific terminal UE objects, when the UE is in the overlapping coverage area of the MN primary serving cell and SN secondary serving cell at the same time At this time, under the control of the main base station MN, there will be NG-C and NG-U interface connections between MN and 5GC, and Xn-C and Xn-U interfaces will be connected between MN and SN, but SN and There can only be NG-U connection between 5GC. Therefore, all basic operations of the UE entering, exiting, and in the dual-connection working mode are completed by the master base station MN. The main base station MN is based on the UE's RRM measurement report for the constantly changing radio conditions of the air interface, as well as the local RRM algorithm conditions of the main base station. Coordination of resources such as transmission. Most of the control plane operations between SN, 5GC, and UE are connected through the Xn-C interface and forwarded by the MN node. In Figures 4a and 4b, the dashed line represents the control plane connection between the network element nodes, and the dotted line represents the user plane connection between the network element nodes. Figure 4a shows the SN terminated (Terminated) bearer type, focusing on the network element node MN/SN and the UPF node (may be referred to as UPF). There are the following two NG-U interface data transmission channels. The first channel is the data transmission channel between UPF and MN provided by NG-U (MN), which is used to transmit MN-side PDU (Protocol Data Unit) Session (session)/QoS (Quality of Service) Quality) The uplink and downlink data packets carried on Flows. The establishment of this channel requires UPF to provide "MN side uplink data transmission channel address" and MN to provide "MN side downlink data transmission channel address". Similarly, the second channel is the data transmission channel between UPF and SN provided by NG-U (SN), which is used to transmit the uplink and downlink data packets carried on the SN-side PDU Session/QoS Flows. The establishment of this channel requires UPF to provide "SN side uplink data transmission channel address" and SN to provide "SN side downlink data transmission channel address". For the SN Terminated bearer type, there is no need to establish and maintain the Xn-U interface bearer between the MN and the SN, because all user service data flows occur independently between the UPF and each primary and secondary base station. Figure 4b shows the MN Terminated bearer type, focusing on the MN and UPF. There is the following NG-U interface data transmission channel: NG-U (MN) provides a data transmission channel between UPF and MN. But there is no NG-U interface data transmission channel between SN and UPF. Compared with Figure 4a, Figure 4b does not have any NG-U (SN) channels. For the MN Terminated bearer type, in order to use the SN side radio resources to assist transmission, an Xn-U bearer needs to be established and maintained between the MN and the SN, because all user service data flows need to occur between the MN and the SN. In short, the supported dual/multiple connection operation must rely on the Xn-C interface between the MN and SN, and multiple primary and secondary base stations participating in the dual/multiple connection operation rely on it to coordinate resource configuration and working status with each other. And update.

With the emergence of various types of mobile base stations or network element nodes, such as ground vehicle mobile base stations, aerial drone base stations, satellite base stations, etc., the wireless coverage/capacity supply of air interface service cells provided by these mobile base stations , Which usually changes continuously as the physical location of the mobile base station moves. These changes or cycles are regular or without any regularity. The bearer transmission of interfaces such as NG and Xn connecting these mobile base stations can no longer be the traditional fixed fixed network transmission method. Therefore, it is impossible to carry the transmission through fixed network methods such as broadband optical fiber, and usually rely on wireless carrying methods, such as: microwave, laser and other relay technology means. This cellular mobile network constructed by many mobile base stations is more flexible in deployment (no fixed site resources are required), but the network resources and the bearer transmission between network element nodes can only be planned in a relatively dynamic way And management updates. Otherwise, as each base station or network element node moves, network topology or environmental conditions will continue to change, the original interface connection and configuration of the old network element may fail, and the new network element interface connection and configuration need to be established and maintained. As shown in Figure 5a and Figure 5b: There are several space-based satellite base stations Moving node1/2/3/4......, each of which provides a satellite service beam from the air to a specific coverage area on the ground to form a ground service cell. 1/2/3/4 "small oval" coverage. But as these satellite base stations collectively move to the left along the orbit, the coverage of their respective ground service cells 1/2/3/4...... also moves to the left along with the satellite base stations, or continuously or hoppingly. . Assuming that there is also a main base station MN on the ground that provides "large ellipse" wireless coverage, the main difference from Figure 3 is: the "small ellipse" coverage provided by the satellite base station and the "large ellipse" coverage provided by the ground MN base station. The relative positional relationship between will change dynamically. In addition, a relatively stable Xn interface connection may not be established between the satellite base station and the ground base station. Otherwise, the establishment, deletion, establishment, and deletion of the Xn interface connection need to be continuously performed, which requires continuous updating and maintenance.

The radio link between the terminal UE and the satellite base station is usually called the Service link, which faces the served UE and directly carries user service data and RRC signaling on the 5G NR Uu air interface. From the perspective of a single user terminal UE, even if the UE is in the same location, as the satellite base station continues to move, the service link of the UE will change accordingly. As shown in Figure 6, the wireless link between the satellite base station and the service ground station is usually called the Feeder link, which is used to further connect the E2E (End to End) between the service link and the ground core network. End) connection, so as to realize the control signaling and user data transmission between the UE and the ground network. Among them, the serving ground station may include a satellite ground gateway NTN-GW (Non-Terrestrial Networks Gateway), a core network, and other centralized control network element nodes. Feeder link at least needs to provide the transmission function between the satellite base station and the ground core network 5GC. If the satellite base station is a complete gNB, the Feeder link needs to provide a stable transmission service for the NG interface, that is, reliable transmission of NGAP control signaling process messages and NG-U user service data. Although satellite base stations have been moving at high speed, it is usually assumed that the feeder link between them and the terrestrial gateway NTN-GW can be robust enough. Therefore, a relatively stable NG interface connection instance can be established, and multiple NTN-GW transport layers on the ground can be routed and relayed through multiple hops and relays without frequent update and maintenance of the NG interface instance. As shown in Figure 6, when the satellite base station Moving Node1 gradually moves to the left from the jurisdiction of the ground station 2 to the jurisdiction of the ground station 3, through the ground transmission relay between the ground station 2 and the ground station 3, you can The default instance of the NG interface between the satellite base station and the anchor network element of the ground core network remains unchanged. Therefore, there is no need to delete the old NG interface connection and rebuild the new NG interface connection, and so on.

The characteristics of the above-mentioned terminal UE dual/multiple connection operation include the fixed physical location of the primary and secondary base stations, the fixed and relatively robust Xn interface connection, and the MN master control. The characteristics of the deployment of mobile base stations represented by satellite base stations include satellite base stations moving regularly and periodically along the orbit, and the Xn interface connection is not fixed and the robustness is relatively low. Combining the characteristics of UE dual/multiple connection operation and the characteristics of mobile base station deployment, if the UE needs to perform dual/multiple connection operation between the ground fixed base station and the mobile satellite base station (abbreviation: ground-air dual/multiple connection), because It cannot rely on the Xn interface between the primary and secondary base stations, but can rely on the relatively more stable NG interface.

This application provides a method for controlling the terminal UE to perform dual/multiple connection data transmission operations through the core network 5GC, without establishing and maintaining the Xn interface connection between the primary and secondary base stations (no Xn-C or Xn-U interface connection). Among them, 5GC and primary and secondary base stations have their own independent NG interface connection, and at the same time they are connected through NG-C and NG-U interfaces. The user plane bearer related to this application is different from the SN Terminated bearer type of Figure 4a: the secondary base station SN and AMF/SMF are also connected through an independent NG-C interface to realize the direct resource configuration management and work of the SN by the 5GC. Collaboration etc.

FIG. 7 is a schematic flowchart of a connection method provided by an embodiment of this application. This method can be applied to the core network side. As shown in Figure 7, the method may include:

Step S11: Send a first instruction message to the target secondary base station, where the first instruction message includes first instruction information for performing a designated operation on the secondary connection between the target secondary base station and the target terminal. The specified operation includes establishment, addition, modification, deletion or release of the auxiliary connection.

Step S12: Receive a first response message from the target secondary base station, where the first response message includes first result information corresponding to the first indication information.

In an embodiment, the network element of the core network may initiate the designated operation of the secondary connection. Among them, the core network element (for example, 5GC) can perceive whether the wireless connection status between the target terminal and multiple access network elements (for example, base stations) has changed. Examples of changes in the wireless connection between the target terminal and multiple base stations may include: the target terminal changes from single connection to multiple base stations, or the target terminal changes from multiple base stations to single connection, or the number of base stations to which the target terminal is connected Change occurs, or the base station to which the target terminal is connected changes, for example, from connecting with base stations A and B to connecting with base stations A and C.

If the 5GC senses that the wireless connection status between the target terminal and multiple base stations has changed, it can send a first indication message to the target secondary base station to establish, add, modify, delete, or delete the secondary connection between the target secondary base station and the target terminal. Release and other operations.

After receiving the first indication message, the target secondary base station performs a designated operation on the secondary connection between the target secondary base station and the target terminal. After the target secondary base station performs the specified operation, it may send a first response message to the core network element to notify the core network element whether the execution of the specified operation is successful.

The following respectively introduces the types and contents of the first indication message and the first indication information corresponding to different operation scenarios.

Scene 1: Create or add scenes.

In this scenario, the first indication message may be a secondary base station establishment request message or a secondary base station addition request message, and the first indication information includes the available secondary connection capability and resource information in the target terminal, and the need to be offloaded to User service characteristic information of the target secondary base station.

Scene 2: Modify the scene.

In this scenario, the first indication message may be a secondary base station modification request message, and the first indication information includes user service feature information that needs to be returned from the target secondary base station to the primary base station, or users who are re-distributed to the target secondary base station Business feature information.

Scene 3: Release or delete the scene.

In this scenario, the first indication message may be a secondary base station release (release) command message or a secondary base station delete (delete) command message, and the first indication information includes the remaining user service features on the target secondary base station to be deleted information.

In the embodiment of the present application, the overall radio link capability of the UE may be divided into multiple relatively independent parts. The first part is the main connection capability, and the second part is one or more auxiliary connection capabilities. For example, P-UE is used to identify the primary connection capability of the UE, and S-UE is used to identify the secondary connection capability. Specifically, the capability objects of various shareable attributes in the UE can be divided according to a specific ratio. For example: segmentation of hardware resources such as RF (Radio Frequency) and antenna module group, power amplifier, Buffer (buffer) resources, baseband processor, etc. that can be shared within the UE. For another example, software resources such as band combination (Band Combination) information and bearer identifier (RB id) supported by the UE are divided. For another example, segmentation of protocol resources and coding resource space.

In the embodiment of the present application, the resource information of the target terminal may include resources that need to be used to establish a secondary connection with the target terminal. For example, if the user service that needs to be offloaded, returned, or deleted is PDU session 1, the resource information of the target terminal may include radio resources related to PDU session 1, and may also include the control plane connected to the S-NG interface related to the secondary base station , User plane and transmission resources.

In the embodiment of this application, the user service characteristic information in the indication information may include user service identification information (e.g. PDU Session id), bearer configuration information (e.g. QoS Flow Level QoS Parameters), and data forwarding transmission channel address ( Such as: UP Data Forwarding TNL Info) etc. For example, if the user service that needs to be offloaded, returned, or deleted is PDU Session 1, the identification information of the user service can be PDU Session 1, and the bearer configuration information of the user service can include all QoS Flows related QoS configuration parameters and data in PDU Session 1. The forwarding transmission channel address can be the PDU SessionTunnel tunnel address information for PDU Session1 as the data forwarding.

In an embodiment, after step S12, the method may further include:

When the first result information indicates that the specified operation is successful, a second indication message is sent to the primary base station, where the second indication message includes the first result information and the information corresponding to the first result information Main connection command information.

Corresponding to the above scenario, the types and contents of the second indication message and the second indication message are respectively as follows:

Scene 1: Create or add scenes.

In this scenario, the second indication message may be a secondary base station establishment command message or a secondary base station add command message, and the second indication message may include the available primary connection capability and resource information in the target terminal, and the offloaded User service characteristic information to the target secondary base station.

For example, in an establishment or addition scenario, the first result information in the second indication message may include that the target secondary base station has established a secondary connection with the UE by using the UE's S-UE capability, and the PDU session that has been offloaded to the target secondary base station, etc. Characteristic information of user services, etc. The main connection command information corresponding to the first result information may include the current available main connection capability and resource information of the UE. The second indication message can instruct the primary base station to delete the characteristic information of user services such as PDU sessions offloaded to the target secondary base station from the primary base station. It can also instruct the primary base station to use the complete UE capabilities and resources to establish a primary connection with the UE and update it to use The UE's P-UE capabilities and resources establish a primary connection with the UE.

Scene 2: Modify the scene.

In this scenario, the second instruction message may be a secondary base station modification command message, and the second instruction message may include available primary connection capability and resource information in the target terminal, and user service characteristics that need to be returned to the primary base station Information, or user service characteristic information that has been diverted to the target secondary base station.

For example, in a modification scenario, the first result information in the second indication message may include characteristic information of user services such as PDU sessions that need to be returned to the primary base station or have been offloaded to the target secondary base station. The main connection command information corresponding to the first result information may include the current available main connection capability and resource information of the UE. The second indication message can instruct the primary base station to delete the characteristic information of user services such as PDU sessions that are offloaded to the target secondary base station from the primary base station, and add the characteristic information of user services that need to be returned to the primary base station. It can also instruct the primary base station to use the UE’s Currently available P-UE capabilities and resources, update the primary connection with the UE.

Scene 3: Release or delete the scene.

In this scenario, the second indication message may be a secondary base station release command message or a secondary base station delete command message, and the second indication message may include the available primary connection capability and resource information in the target terminal, and the need to return User service characteristic information remaining on the target secondary base station to the primary base station.

For example, in a release or deletion scenario, the first result information in the second indication message may include characteristic information of user services such as remaining PDU sessions on the target secondary base station that needs to be returned to the primary base station. The main connection command information corresponding to the first result information may include the current available main connection capability and resource information of the UE. The second indication message may indicate that the characteristic information of the user service such as the PDU session deleted from the target secondary base station is returned to the primary base station. If all the secondary base stations are released from multiple connections to single connections, the second indication message can instruct the primary base station to re-use the complete UE capabilities and resources to establish a primary connection with the UE.

In the embodiment of the present application, the user service characteristic information may include user service identification information, bearer configuration information, and transmission channel address for data forwarding. For example, the user service characteristic information in the first demand information includes identification information of the user service. The user service characteristic information in the first indication information and the second indication information includes the bearer configuration information of the user service, the transmission channel address of the data forwarding, and the like.

This embodiment can directly instruct the target secondary base station to perform designated operations on the secondary connection between the target secondary base station and the target terminal through the core network element, without relying on the interaction between the base stations, and instruct the primary and secondary base stations to update the primary connection with the target terminal, which is beneficial to Improve the flexibility of multi-connection operations.

FIG. 8 is a schematic flowchart of a connection method provided by another embodiment of this application. This method can be applied to the core network side. As shown in Figure 8, the method may include:

Step S21: Receive a first demand message from a primary base station, the first demand message being sent by the primary base station upon detecting that the wireless connection status between the target terminal and multiple base stations has changed, and the first demand message A demand message includes first demand information for performing the specified operation on the auxiliary connection. Wherein, the first demand information includes demand information for the establishment, addition, modification, deletion or release of the auxiliary connection.

Step S22: Send a first instruction message to the target secondary base station, where the first instruction message includes first instruction information for performing a specified operation on the secondary connection between the target secondary base station and the target terminal. The specified operation includes establishment, addition, modification, deletion or release of the auxiliary connection.

Step S23: Receive a first response message from the target secondary base station, where the first response message includes first result information corresponding to the first indication information.

In an implementation manner, the primary base station may initiate the designated operation of the secondary connection. The primary base station can perceive whether the wireless connection status between the target terminal and multiple access network elements (for example, base stations) has changed. For examples of changes in the wireless connection between the target terminal and multiple base stations, reference may be made to the relevant description of the foregoing embodiment. If the primary base station senses that the wireless connection status between the target terminal and multiple base stations has changed, it can send the first demand message to the core network element. The core network element sends the first indication message to the target secondary base station. After receiving the first indication message, the target secondary base station performs designated operations such as establishing, adding, modifying, deleting, or releasing the secondary connection between the target secondary base station and the target terminal. After the target secondary base station performs the specified operation, it may return a first response message to the core network element to notify the core network element whether the execution of the specified operation is successful.

The following respectively introduces the type and content of the first demand message corresponding to different operation scenarios.

Scene 1: Create or add scenes.

In this scenario, the first demand message is a secondary base station establishment demand message or a secondary base station add demand message, and the first demand message includes user service characteristic information that needs to be offloaded to the target secondary base station.

Scene 2: Modify the scene.

In this scenario, the first demand message is a secondary base station modification demand message, and the first demand message includes user service characteristic information that needs to be returned to the primary base station, or user service characteristic information that needs to be redirected to the target secondary base station.

Scene 3: Release or delete the scene.

In this scenario, the first demand message is a secondary base station release demand message or a secondary base station delete demand message, and the first demand message includes the remaining user service feature information on the target secondary base station that needs to be deleted.

Correspondingly, the type and content of the first indication message and the first response message in the above scenario can refer to the related description of the above embodiment, which will not be repeated here.

In an embodiment, after step S23, the method may further include:

When the first result information indicates that the specified operation is successful, a second indication message is sent to the primary base station, where the second indication message includes the first result information and the information corresponding to the first result information Main connection command information. For example, in the case where operations such as establishing, adding, modifying, deleting, or releasing the secondary connection are successful, the 5GC may send the second indication information to the primary base station. For the type and content of the second indication message, reference may be made to the related description of the foregoing embodiment, which is not repeated here.

In the embodiment of the present application, the user service characteristic information may include user service identification information, bearer configuration information, and transmission channel address for data forwarding. For example, the user service characteristic information in the second requirement information includes identification information of the user service. The user service characteristic information in the first indication information and the second indication information includes the bearer configuration information of the user service, the transmission channel address of the data forwarding, and the like.

After receiving the demand information of the primary base station, this embodiment can directly instruct the target secondary base station to perform a designated operation on the secondary connection between the target secondary base station and the target terminal through the core network element, and instruct the primary and secondary base station to update the primary and secondary base station with the target terminal. Connection does not need to rely on interaction between base stations, which is beneficial to improve the flexibility of multi-connection operations.

FIG. 9 is a schematic flowchart of a connection method provided by another embodiment of this application. This method can be applied to the core network side. As shown in Figure 9, the method may include:

Step S31: Receive a second demand message from the target secondary base station, where the second demand message is sent by the target secondary base station when it detects that the wireless connection status between the target terminal and multiple base stations has changed, so The second demand message includes second demand information for performing the specified operation on the secondary connection, and the second demand information includes demand information for modification, deletion, or release of the secondary connection.

Step S32: Send a third instruction message to the primary base station, where the third instruction message includes primary connection command information corresponding to the second demand information.

Step S33: Receive a second response message from the primary base station, where the second response message includes second result information corresponding to the primary connection command information.

Step S34: Send a first instruction message to the target secondary base station, where the first instruction message includes first instruction information for performing a specified operation on the secondary connection between the target secondary base station and the target terminal. The specified operation includes modification, deletion or release of the auxiliary connection.

Step S35: Receive a first response message from the target secondary base station, where the first response message includes first result information corresponding to the first indication information.

In this embodiment, the secondary base station can initiate the designated operation of the secondary connection. The secondary base station can perceive whether the wireless connection status between the target terminal and multiple access network elements (for example, base stations) has changed. For examples of changes in the wireless connection between the target terminal and multiple base stations, reference may be made to the relevant description of the foregoing embodiment. If the target secondary base station senses that the wireless connection status between the target terminal and multiple base stations has changed, it may send the second demand information to the core network element. After receiving the second demand information, the core network element may send a third indication message to the main base station. After the main base station updates its own user service and main connection according to the third instruction message, it returns a second response message to the core network element. After receiving the second response message, the core network element may send the first indication message to the target secondary base station. After receiving the first indication message, the target secondary base station can perform designated operations such as modification, deletion, or release on the secondary connection between the target secondary base station and the target terminal. After the target secondary base station performs the specified operation, it may return a first response message to the core network element to notify the core network element whether the execution of the specified operation is successful.

The type and content of the second demand message corresponding to different operation scenarios are respectively introduced below.

Scene 1: Modify the scene.

In this scenario, the second demand message may be a secondary base station modification demand message, and the second demand information includes user service characteristic information that needs to be returned to the primary base station.

The third indication message is a secondary base station modification request message, and the third indication message includes available primary connection capability and resource information in the target terminal, and user service characteristic information that needs to be returned to the primary base station.

The first indication information is a secondary base station modification command message, and the first indication message includes available secondary connection capability and resource information in the target terminal, and user service characteristic information that has been returned to the primary base station.

In this scenario, if the target secondary base station sends a secondary base station modification requirement message to the core network element. After the core network element receives the secondary base station modification request message, it can send the secondary base station modification request message to the primary base station. After the primary base station updates its own user service and primary connection according to the secondary base station modification request message, it returns a second response message to the core network element. After receiving the second response message, the core network element may send a secondary base station modification command message to the target secondary base station. The target secondary base station receives the secondary base station modification command message, modifies the secondary connection with the target terminal, and may return a first response message to the core network element.

Scene 2: Release or delete the scene.

In this scenario, the second demand message is a secondary base station release demand message or a secondary base station delete demand message, and the second demand information includes user service feature information remaining on the target secondary base station that needs to be deleted. The third indication message is a secondary base station release command message or a secondary base station delete command message, and the third indication message includes available primary connection capability and resource information in the target terminal, and needs to be returned to the target secondary base station of the primary base station The remaining user service characteristic information. The first indication information is a secondary base station release command message or a secondary base station delete command message, and the remaining user service feature information on the target secondary base station that needs to be deleted in the first indication message.

In this scenario, if the target secondary base station sends a secondary base station release demand message or a secondary base station delete demand message to the core network element. After the core network element receives the secondary base station release demand message or the secondary base station delete demand message, it can send the secondary base station release command message or the secondary base station delete command message to the primary base station. After the primary base station updates its user service and primary connection according to the secondary base station release command message or the secondary base station delete command message, it returns a second response message to the core network element. After receiving the second response message, the core network element may send a secondary base station release command message or secondary base station delete command message to the target secondary base station. After the target secondary base station receives the secondary base station release command message or secondary base station delete command message, it deletes the secondary connection between the target secondary base station and the target terminal, returns the first response message to the core network element, and can release or delete the target secondary base station. Base station.

In this embodiment, after receiving the demand information of the target secondary base station, the core network element can directly instruct the target secondary base station to perform a designated operation on the secondary connection between the target secondary base station and the target terminal, and instruct the primary and secondary base station to update the communication with the target terminal. The main connection does not need to rely on the interaction between base stations, which helps to improve the flexibility of multi-connection operations.

FIG. 10 is a schematic flowchart of a connection method provided by another embodiment of this application. This method can be applied to the access network side. As shown in Figure 10, the method may include:

Step S41: Receive a first instruction message from a core network element, where the first instruction message includes first instruction information for performing a specified operation on the secondary connection between the target secondary base station and the target terminal. The specified operation includes establishment, addition, modification, deletion or release of the auxiliary connection.

Step S42: Perform the specified operation on the secondary connection between the target secondary base station and the target terminal.

Step S43: Send a first response message to the core network element, where the first response message includes first result information corresponding to the first indication message.

In an embodiment, the network element of the core network may initiate the designated operation of the secondary connection. Among them, the core network element (for example, 5GC) can perceive whether the wireless connection status between the target terminal and multiple access network elements (for example, base stations) has changed. For examples of changes in the wireless connection between the target terminal and multiple base stations, reference may be made to the relevant description of the foregoing embodiment. If the 5GC senses that the wireless connection status between the target terminal and multiple base stations has changed, it may send a first indication message to the target secondary base station. After receiving the first indication message, the target secondary base station performs designated operations such as establishing, adding, modifying, deleting, or releasing the secondary connection between the target secondary base station and the target terminal. After the target secondary base station performs the specified operation, it may send a first response message to the core network element to notify the core network element whether the execution of the specified operation is successful.

Scene 1: Create or add scenes.

In this scenario, the first indication message may be a secondary base station establishment request message or a secondary base station addition request message, and the first indication information may include the available secondary connection capability and resource information in the target terminal, and the need for offloading User service characteristic information to the target secondary base station.

Scene 2: Modify the scene.

In this scenario, the first indication message may be a secondary base station modification request message, and the first indication information may include user service characteristic information that needs to be returned from the target secondary base station to the primary base station, or re-distributed to the target secondary base station. User service characteristic information.

Scene 3: Release or delete the scene.

In this scenario, the first indication message may be a secondary base station release command message or a secondary base station delete command message, and the first indication information may include remaining user service feature information on the target secondary base station to be deleted.

Scene 1: Create or add scenes.

Scene 2: Modify the scene.

Scene 3: Release or delete the scene.

In an implementation manner, after step S43, the method may further include: receiving a second indication message from the core network element, where the second indication message is when the core network element is in the first A result information indicates that it is sent when the specified operation is successful, and the second indication message includes the first result information and main connection command information corresponding to the first result information.

Specifically, if the first result information indicates that the specified operation is successful, the core network element may send a second indication message to the primary base station. After receiving the second indication message, the primary base station can update the primary connection between the primary base station and the target terminal.

The type and content of the first indication message, the first indication information, the first response message, the second indication message, etc. in this embodiment are the same as those of the embodiment in FIG. 7, and reference may be made to the relevant description of this embodiment, which will not be repeated here.

FIG. 11 is a schematic flowchart of a connection method provided by another embodiment of this application. This method can be applied to the access network side. As shown in Figure 11, the method may include:

Step S51: In the case of detecting that the wireless connection status between the target terminal and the multiple base stations has changed, send a first demand message to the core network element, where the first demand message includes information on the secondary connection First demand information for performing the specified operation, where the first demand message includes a demand for establishing, adding, modifying, deleting, or releasing the secondary connection.

Step S52: Receive a first instruction message from a core network element, where the first instruction message includes first instruction information for performing a specified operation on the secondary connection between the target secondary base station and the target terminal, and the specified operation includes The establishment, addition, modification, deletion or release of the auxiliary connection.

Step S53: Perform the specified operation on the secondary connection between the target secondary base station and the target terminal.

Step S54: Send a first response message to the core network element, where the first response message includes first result information corresponding to the first indication message.

Scene 1: Create or add scenes.

Scene 2: Modify the scene.

Scene 3: Release or delete the scene.

In an implementation manner, after step S54, the method may further include: receiving a second indication message from the core network element, where the second indication message is when the core network element is in the first A result information indicates that it is sent when the specified operation is successful, and the second indication message includes the first result information and main connection command information corresponding to the first result information.

The type and content of the first demand message, the first demand information, the first instruction message, the first instruction information, the first response message, the second instruction message, etc. in this embodiment are the same as those of the embodiment of FIG. 8. The relevant description of the example will not be repeated here.

FIG. 12 is a schematic flowchart of a connection method provided by another embodiment of this application. This method can be applied to the access network side. As shown in Figure 12, the method may include:

Step S61: In the case of detecting that the wireless connection status between the target terminal and multiple base stations has changed, send a second demand message to the core network element, where the second demand message includes information on the secondary connection Second demand information for performing the specified operation. The second demand information includes a demand for modification, deletion or release of the auxiliary connection.

Step S62: Receive a third instruction message from the core network element, where the third instruction message includes main connection command information corresponding to the second demand information.

Step S63: Send a second response message to the core network element, where the second response message includes second result information corresponding to the main connection command information.

Step S64: Receive a first instruction message from the core network element, where the first instruction message includes first instruction information for performing a specified operation on the secondary connection between the target secondary base station and the target terminal. The specified operation includes modification, deletion or release of the auxiliary connection.

Step S65: Perform the specified operation on the secondary connection between the target secondary base station and the target terminal.

Step S66: Send a first response message to the core network element, where the first response message includes first result information corresponding to the first indication message.

In this embodiment, the secondary base station can initiate the designated operation of the secondary connection. The secondary base station can perceive whether the wireless connection status between the target terminal and multiple access network elements (for example, base stations) has changed. For examples of changes in the wireless connection between the target terminal and multiple base stations, reference may be made to the relevant description of the foregoing embodiment. If the target secondary base station senses that the wireless connection status between the target terminal and multiple base stations has changed, it may send the second demand information to the core network element. After receiving the second demand information, the core network element may send a third indication message to the main base station. After receiving the third indication message, the main base station may update its user service and main connection according to the third indication message, and then return a second response message to the core network element. After receiving the second response message, the core network element may send the first indication message to the target secondary base station. After receiving the first indication message, the target secondary base station can perform designated operations such as modification, deletion, or release on the secondary connection between the target secondary base station and the target terminal. After the target secondary base station performs the specified operation, it may return a first response message to the core network element to notify the core network element whether the execution of the specified operation is successful.

Scene 1: Modify the scene.

In this scenario, the second demand message is a secondary base station modification demand message, and the second demand information includes user service characteristic information that needs to be returned to the primary base station. The third indication message is a secondary base station modification request message, and the third indication message includes available primary connection capability and resource information in the target terminal, and user service characteristic information that needs to be returned to the primary base station. The first indication information is a secondary base station modification command message, and the first indication message includes available secondary connection capability and resource information in the target terminal, and user service characteristic information that has been returned to the primary base station.

Scene 2: Release or delete the scene.

The second demand message, the second demand information, the third instruction message, the second response information, the first instruction message, the first instruction information, the first response message, the second instruction message, etc. in this embodiment and the embodiment of FIG. 9 The type and content of the are the same, please refer to the related description of this embodiment, which will not be repeated here.

In the embodiments corresponding to FIG. 10, FIG. 11, and FIG. 12, in a new or adding scenario, performing the specified operation on the secondary connection between the target secondary base station and the target terminal includes: according to the target The available auxiliary connection capability and resource information in the terminal, as well as the user service characteristic information that needs to be offloaded to the target auxiliary base station, establish an auxiliary connection with the target terminal to offload the user service to the target auxiliary base station, so that the target auxiliary base station The base station continues to carry the transmission.

In the modified scenario, performing the specified operation on the secondary connection between the target secondary base station and the target terminal includes: deleting user service bearer transmission resources that need to be returned from the target secondary base station, or re-offloading users The service allocates new bearer transmission resources.

In the deletion scenario, performing the specified operation on the secondary connection between the target secondary base station and the target terminal includes: deleting the remaining user service bearer transmission resources from the target secondary base station, and releasing or deleting the target Secondary base station.

The following is an application example of the present application in the dual connection mode. The principle of the multi-connection mode is similar to the dual connection mode. You can refer to the related description of the dual connection mode.

As shown in Figure 13, the movement of the target SN has a predictable regularity. There is no need to establish an Xn interface connection between the target SN and MN, but the target SN and 5GC can establish an S-NG interface connection. 5GC and MN can infer and predict when and which target SN can be added as offload secondary base station through positioning and time information. Divide the overall radio link capability (or UE Radio Access Capability) of a terminal UE served by the 5GS network into two relatively independent parts. For example, they are represented or identified by P-UE and S-UE respectively. Among them, the sum of the respective capabilities and resource attributes of the P-UE and S-UE is equal to the total capabilities and resources of the UE. If the UE can connect to the primary base station and multiple secondary base stations at the same time, the radio link capability can be divided into P-UE and multiple S-UEs.

Furthermore, UE capability segmentation can be performed according to a predefined static method (relatively fixed segmentation); it can also be segmented semi-statically according to the command method of the network side, which can change the specific segmented capability content and main and auxiliary as needed. Side ratio. The capabilities of P-UE and S-UE may include partitioning objects with sharable attribute capabilities at a specific ratio. For example: hardware resources such as RF (Radio Frequency), antenna module group, Buffer (buffer) resources and baseband processor that can be shared within the UE, or supported band combination (Band Combination) information, bearer identification (RB id) And other software resources. The capability of P-UE and S-UE segmentation may also include segmentation for non-shared attribute capabilities. For example, for a UE that supports multi-mode capabilities, the resources corresponding to a certain RAT standard are all given to the P-UE, and the resources corresponding to other RATs are all given to the S-UE. The relationship between them is not the aforementioned proportional division.

Furthermore, a UE that is "capacity-divided" can present two relatively independent "virtual sub UEs" to the outside within a certain observation or operation time window. Their respective wireless capabilities set can be perceived and utilized by the primary and secondary base stations MN/SN and the core network 5GC. Among them, the status and mobility of the P-UE represent the overall RRC status and mobility of the UE; the S-UE mainly provides an auxiliary offloading function for user plane data transmission, and does not affect the overall control plane attributes and RRC status of the UE.

Before the UE enters the dual connectivity working mode, the primary base station (MN) can utilize all the radio link capabilities of the UE, and can report to the 5GC in advance through the NGAP process message. The following examples of feasible P-UE and S-UE capability division methods are as follows:

Option 1: P-UE x + S-UE y;

Option 2: P-UE m+S-UE n

...

Option x: P-UE k+S-UE h

The 5GC receives and saves the information of the above-mentioned P-UE and S-UE capability division method, and then performs the dual connection operation for backup.

The following describes the initiation methods of several auxiliary connection related operations.

The first way: MN initiates.

The primary base station MN can infer and predict when and which target SN can be added as the offloaded secondary base station SN through the positioning and time information, that is, the target SN has the conditions for dual connection operation with the MN. Therefore, the network side can perform operations such as establishing, adding, modifying, deleting, or releasing the SN, without relying on the RRM measurement report of the UE, and the MN can trigger the 5GC in real time as needed.

Further, the main base station MN can request the 5GC to establish or add a specific target SN through the NGAP process message. For example, the MN sends a NGAP: SN Addition Required message to the 5GC, which includes the target SN information and the current MN side user service data information to be offloaded by the SN bearer, such as PDU Session/QoS Flows id (identification), etc.

If the 5GC agrees to enter the dual-connection working mode, the 5GC can instruct the MN to enter the dual-connection working mode based on the NGAP process message. After that, the MN only uses the radio link capability of the P-UE side indicated by the 5GC, and no longer uses the radio link capability of the S-UE side. For example, the MN receives the NGAP process message from 5GC: SN Addition Command message, which indicates a certain 5GC selected P-UE x+S-UE y capability division combination or related index identification and the user who was successfully offloaded by the target SN Service data information, such as PDU Session/QoS Flows id identification, etc.

After entering the dual-connection working mode, the main base station MN and UE establish and maintain P-RL (Primary Radio Link), and have P-NG-C main control plane connection and P-NG-U main user plane connection instances with 5GC They are used to transmit control signaling and user service data on the MN side. The specific operations are similar to those of the UE single connection.

Further, the main base station MN can also request the 5GC to modify, delete or release the current target SN through the NGAP process message. For example, MN sends NGAP: SN Modification Required message or SN Release Required message to 5GC, which includes the target SN to be modified or deleted and related user service data information. Similarly, if 5GC agrees to modify or exit the dual-connection working mode, MN receives the NGAP process message from 5GC: SN Modification Command or SN Release Command message, which includes the modified or deleted target SN and related user service data information confirmed by 5GC .

The second way: 5GC initiated.

Based on the positioning and time information, the 5GC can also predict and predict: when the target MN under its jurisdiction can add which target SN as the offload secondary base station SN, that is, in which time window the target MN and SN have the conditions for dual connection operation. Therefore, the 5GC can actively trigger and determine the network-side SN establishment, addition, modification, deletion, or release operations, and there is no need to rely on the NGAP uplink message request of the primary base station MN at this time.

Further, if the 5GC receives a request from the autonomous base station MN to establish, add, modify, delete, or release the target SN, it can decide whether to enter, modify or exit the dual connection working mode.

If the 5GC decides to enter the dual-connection working mode, it will send the SN add request operation to the target SN through the NGAP process message, and try to establish the S-NG-C auxiliary control plane connection, the S-NG-U auxiliary user plane connection instance, and the SN auxiliary Wireless link resources related to the base station side. This depends on how much UE user service data the MN or 5GC needs to offload to the SN side. For example, the 5GC sends the NGAP process message to the target SN: SN Addition Request message, which includes the user service data information originally belonging to the MN side to be established by the SN offload bearer, such as the PDU Session/QoS Flows id identifier. Similarly, the 5GC can also send NGAP process messages to the target SN: SN Modification Request or SN Release Command messages, which include user service data information on the current SN to be modified or deleted by the SN, such as PDU Session/QoS Flows id identification.

The third way: SN initiated.

Based on the NGAP process message from 5GC, the target secondary base station SN tries to establish S-NG-C secondary control plane connection, S-NG-U secondary user plane connection instance and SN secondary base station side related wireless link resources, and passes the NGAP process The message replies to the result of the above SN establishment by 5GC. For example, SN sends NGAP process message to 5GC: SN Addition Request Acknowledge message, which includes user service data information established successfully and failed, such as PDU Session/QoS Flows id identification and Data Forwarding transmission channel address. Similarly, the target secondary base station SN attempts to perform SN modification or deletion related operations based on the NGAP process message from 5GC, and replies to the 5GC with the result of the above modification or deletion. For example: SN sends NGAP process message to 5GC: SN Modification Request Acknowledge or SN Release Complete message.

After the UE enters the dual-connection working mode, the secondary base station SN establishes and maintains the S-RL secondary radio link with the UE, and at the same time has an S-NG-C secondary control plane connection and S-NG-U secondary user plane connection instance with the 5GC. They are used to transmit control signaling and user service data on the SN side. The specific operations are similar to the current UE single-connection operations.

Further, the secondary base station SN can actively request the 5GC to modify and delete the current SN through the NGAP process message. For example, the SN actively triggers the sending of the NGAP process message to the 5GC: SN Modification Required message or SN Release Required message, which includes the pending SN Modified or deleted user service data information on the current SN side, such as PDU Session/QoS Flows id identifier.

The 5GC can be implemented internally, without the SN Release Required message request of the MN or SN, and it actively triggers the decision whether to exit the current dual-connection working mode. If the 5GC decides to exit the dual-connection working mode, it will instruct the target MN and SN to return to the single-connection working mode through the NGAP process message. After that, the MN can resume using all the radio link capabilities of the entire UE. For example, 5GC sends NGAP process messages: SN Release Command messages to the target MN and SN respectively.

After the UE exits the dual-connection working mode, the S-NG-C secondary control plane connection, the S-NG-U secondary user plane connection instance, and the radio link resources related to the SN secondary base station side can all be released, or temporarily SN The secondary base station remains but deactivation does not work. The P-NG-C main control plane connection, the P-NG-U main user plane connection instance, and the radio link resources related to the MN main base station side can all be reconfigured and updated.

This application provides a method for controlling a UE to perform dual/multiple connection data transmission operations through a core network (5GC). This method does not need to establish or maintain the Xn interface connection between the primary and secondary base stations (for example, there may be no Xn-C or Xn-U interface connection), and the 5GC and the primary and secondary base stations need to establish and maintain their own independent NG interface connections (set up at the same time) NG-C and NG-U interface connection). The network side manages the UE dual/multiple connection working mode, without relying on the UE's RRM measurement and reporting for the target SN, and uses its own base station location and time and other prior information (such as the ephemeris information of the satellite base station) to predict the target MN and SN The conditional relationship between the dual/multiple connection operation, so as to manage the UE dual/multiple connection working mode more flexibly. This application can support the MN and SN to trigger certain basic operations of dual/multiple connections, and the 5GC will make the final decision and management of user service data shunting and returning.

Application example 1: MN initiates the process of establishing or adding SN.

As shown in Figure 14a: In a LEO low-orbit satellite communication system, several LEO low-orbit satellites are in specific near-earth orbits. These satellites can orbit the Earth's circle periodically according to predetermined ephemeris information. They carry complete gNB base station functions (called gNB satellites) and provide satellite wireless access services for ground users UEs. There are several satellite ground station gateway (NTN-GW) entities deployed on the ground, which are integrated in the 5GC core network entity. Each LEO satellite relies on its own positioning capability, and can establish and maintain one or more Feeder link bearer links with one or more NTN-GW/5GCs on the ground according to the current physical latitude and longitude position. NG interface connection example. Each LEO satellite can project beam coverage to a predetermined area on the ground (the large ellipse in Figure 14a, usually with a coverage radius much larger than the coverage of the service cell of the ground base station). With the movement of LEO satellites, the beam coverage of these satellites also slides on the ground, forming inter-frequency overlapping coverage with the ground-based cellular coverage (the small ellipse in Figure 14a).

As shown in Figure 14b, the process of MN initiating adding SN may include the following steps:

S100: At T1, the anchor point of the satellite base station A-gNB1 is connected to the NTN-GW/5GC1, and the ground base station MN is also anchored to the same NTN-GW/5GC1. MN and 5GC1 have the ephemeris information of the LEO low-orbit satellite system according to the network management configuration information. For example, which LEO satellite will travel to which orbital position at what time, and which area the beam corresponding to the satellite will cover. Therefore, MN and 5GC1 can infer that during the observation period before and after T1, the ground coverage of the satellite base station A-gNB1 beam and the wireless coverage of the main base station MN have a certain overlap, so that the ground-air dual connection operation may be performed. A connected UE is being served by the main base station MN cell (small ellipse in Figure 14a), and PDU Session 1 (PDU Session 1) and PDU Session 2 (PDU Session 2) have been established for user service data related radio resources and NG interface connection transmission Channel etc. The UE supports the P-UE and S-UE capability division of this application, and reports the supportable capability division information to the MN and 5GC1. According to the local strategy (such as roaming security or billing factors) of the integrated cellular system with space and ground, PDU Session1 user service data can be carried and transmitted by the LEO satellite radio link. In step S100, the MN can report and coordinate the P-UE and S-UE capabilities and resource partitioning supported by the UE through a terminal radio capability report (UE RADIO CAPABILITY REPORT) message or a terminal capability information indication (UE CAPABILITY INFO INDICATION) message. information.

S101: According to the ephemeris information of the LEO low-orbit satellite system, the MN does not rely on the UE's RRM measurement report, and sends a secondary base station add request (SN ADDITION REQUIRED) message to the 5GC1 at an appropriate time. The message includes a request to offload all the QoS Flows in the PDU Session1 currently carrying the service on the MN side to the target secondary base station SN-gNB1. At the same time, the MN can also suggest a data forwarding operation to reduce data packet loss in the offloading operation. Wherein, the data forwarding may include continuing to send to 5GC1 the remaining unsuccessful data packets of user services that need to be offloaded on the source node side.

S102: 5GC1 receives the demand message of the MN, and according to the ephemeris information of the LEO low-orbit satellite system and the system's local policy, determines that all QoS Flows in PDU Session1 can be diverted to the target SN-gNB1. 5GC1 sends the secondary base station to SN-gNB1 Add request (SN ADDITION REQUEST) message. This message includes notifying the target SN-gNB1 of the available S-UE capabilities, requesting the establishment of PDU and Session1 related radio resources on the SN-gNB1 side, and the control plane, user plane and transmission resources connected to the S-NG interface.

S103: SN-gNB1 receives the 5GC1 request message, and performs local resource admission control. If SN-gNB1 determines that all relevant resources can be successfully established for PDU Session1, it can send a secondary base station addition response message to 5GC1, such as a secondary base station addition confirmation (SN ADDITION REQUEST ACKNOWLEDGE) message. The message includes notifying 5GC1 that PDU Session1 has been successfully established, as well as related radio resources on the SN-gNB1 side, and the control plane, user plane, and transmission resources connected to the S-NG interface. SN-gNB1 can also provide transmission address information for data forwarding at the same time, so as to realize the data forwarding operation from the MN side.

S104: 5GC1 receives the confirmation message from SN-gNB1, knows that the SN-gNB1 side has successfully offloaded to establish PDU Session1, and can send a secondary base station add command (SN ADDITION COMMAND) message to the MN. The message includes the P-UE capabilities and resources available to the MN to notify the MN to enter the dual connectivity operation, and the result of successfully offloading PDU Session1 to the SN-gNB1 side. Then the MN can delete the related radio resources of the original service PDU Session1, the control plane, user plane, and transmission resources connected to the P-NG interface.

After S104: MN and P-UE use RRC reconfiguration messages to establish and maintain the P-RL radio link, and then only transmit PDU Session2 user service data. SN-gNB1 and S-UE use RRC reconfiguration messages to establish and maintain S-RL radio links, and then only transmit PDU and Session1 user service data.

Addition in this application example is sometimes called CREATE. Correspondingly, the message related to the addition can also be modified to the message related to the establishment. For example, a secondary base station establishment request (SN CREATE REQUIRED) message, a secondary base station establishment request (SN CREATE REQUEST) message, a secondary base station establishment confirmation (SN CREATE REQUEST ACKNOWLEDGE) message, a secondary base station establishment command (SN CREATE COMMAND) message, etc. The following other application examples are similar situations, so I won't repeat them.

Application example 2: MN initiates the process of modifying SN.

As shown in Figure 15a: In a LEO low-orbit satellite communication system, several LEO low-orbit satellites are in specific near-earth orbits. These satellites can orbit the Earth's circle periodically according to predetermined ephemeris information. They carry complete gNB base station functions (called gNB satellites) and provide satellite wireless access services for ground users UEs. Several satellite ground station gateway NTN-GW entities are deployed on the ground, which are integrated in the 5GC core network entity. Each LEO satellite relies on its own positioning capability, and can establish and maintain one or more Feeder link bearer links with one or more NTN-GW/5GCs on the ground according to the current physical latitude and longitude position. NG interface connection example. Each LEO satellite can project beam coverage to a predetermined area on the ground (the large ellipse in Figure 15a, usually with a coverage radius much larger than the coverage of the service cell of the ground base station). With the movement of LEO satellites, the beam coverage of these satellites also slides on the ground, forming inter-frequency overlapping coverage with the ground-based cellular coverage (small ellipse in Figure 15a).

As shown in Figure 15b, the process of MN initiating to modify SN may include the following steps:

S200: At time T2 after T1, the constantly moving satellite base station A-gNB1 is still anchored to the NTN-GW/5GC1, while the ground base station MN is also anchored to the same NTN-GW/5GC1. MN and 5GC1 have the ephemeris information of the LEO low-orbit satellite system according to the network management configuration information. For example, which LEO satellite will travel to which orbital position at what time, and which area the beam corresponding to the satellite will cover. Therefore, both MN and 5GC1 can infer that during the observation period before and after T2, the ground coverage of the satellite base station A-gNB1 beam and the wireless coverage of the main base station MN have a certain overlap, so that the ground-air dual connection operation can be maintained . A UE that is already in ground-air dual connection operation is being served by the primary base station MN cell (small ellipse in Figure 15a) and secondary base station SN-gNB1 (large ellipse in Figure 15a) at the same time, and PDU Session 2 and PDU Session 1 user services have been established respectively Data-related wireless resources and NG interfaces are connected to transmission channels, etc. The UE supports the P-UE and S-UE capability division of this application, and reports the updated capability division information to the MN and 5GC1. According to the system's local policy (such as roaming security or billing factors), part of the QoS Flows user service data in PDU Session 1 needs to be returned to the MN for transmission. In step S200, the MN can report the updated P-UE and S-UE capability split information supported by the UE through a terminal radio capability report (UE RADIO CAPABILITY REPORT) message or a terminal capability information indication (UE CAPABILITY INFO INDICATION) message .

S201: According to the ephemeris information of the LEO low-orbit satellite system, the MN does not rely on the RRM measurement report of the UE, and sends a secondary base station modification request (SN MODIFICATION REQUIRED) message to the 5GC1 at an appropriate time. This message includes a request to return part of the QoS Flows in the PDU Session1 currently carrying the service on the SN-gNB1 side to the MN for bearer transmission. At the same time, the MN can also suggest a data forwarding (Data Forwarding) operation. The corresponding data forwarding transmission address information can be provided in the above message to reduce data packet loss in the return operation.

S202: 5GC1 receives the demand message of the MN, and according to the ephemeris information of the LEO low-orbit satellite system and the system's local policy, determines that part of the QoS Flows in PDU Session1 can be returned to the MN. 5GC1 sends a secondary base station modification request (SN MODIFICATION REQUEST) message to the target SN-gNB1. The message includes notifying the target SN-gNB1 of the available S-UE capabilities after the update, and requesting that SN-gNB1 focus on configuring the remaining part of the PDU and Session1 related radio resources, and the control plane, user plane and transmission connected to the S-NG interface Resources etc.

S203: SN-gNB1 receives the request message of 5GC1, deletes part of QoS Flows and related resources in PDU Session1 to be returned, and reconfigures the remaining part of PDU Session1. Then, SN-gNB1 sends a secondary base station modification response message to 5GC1, for example, a secondary base station modification confirmation (SN MODIFICATION REQUEST ACKNOWLEDGE) message. This message includes notifying 5GC1 that it has successfully deleted some QoS Flows and related resources in PDU Session1, as well as successfully reconfiguring related radio resources on the SN-gNB1 side, and the control plane, user plane, and transmission resources connected to the S-NG interface. SN-gNB1 can also perform data forwarding (Data Forwarding) for some of the returned QoS Flows.

S204: 5GC1 receives the confirmation message from SN-gNB1, knows that SN-gNB1 has successfully deleted some QoS Flows and related resources in PDU Session1, and can send SN MODIFICATION COMMAND message to MN. This message includes the requirement to notify the MN to maintain the available P-UE capabilities and resources after the update of the dual connectivity operation, and to successfully return part of the QoS Flows in PDU Session 1 to the MN side. Then the MN re-establishes part of the QoS Flows and related radio resources in the returned PDU Session1, and the control plane, user plane, and transmission resources connected to the P-NG interface.

After S204: MN and P-UE continue to maintain the P-RL radio link through RRC reconfiguration messages, and then continue to transmit PDU Session2 user service data and part of the returned PDU Session1 user service data. SN-gNB1 and S-UE continue to maintain the S-RL radio link through RRC reconfiguration messages, and then continue to transmit part of the remaining PDU and Session1 user service data.

Application example 3: MN initiates the process of releasing or deleting SN.

As shown in Figure 16a: In a LEO low-orbit satellite communication system, several LEO low-orbit satellites are in specific near-earth orbits. These satellites can orbit the Earth's circle periodically according to predetermined ephemeris information. They carry complete gNB base station functions (called gNB satellites) and provide satellite wireless access services for ground users UEs. There are several satellite ground station gateway (NTN-GW) entities deployed on the ground, which are integrated in the 5GC core network entity. Each LEO satellite relies on its own positioning capability, and can establish and maintain one or more Feeder link bearer links with one or more NTN-GW/5GCs on the ground according to the current physical latitude and longitude position. NG interface connection example. Each LEO satellite can project beam coverage to a predetermined area on the ground (the large ellipse in Figure 16a, usually with a coverage radius much larger than the coverage of the service cell of the ground base station). With the movement of LEO satellites, the beam coverage of these satellites also slides on the ground, forming inter-frequency overlapping coverage with the ground-based cellular coverage (small ellipse in Figure 16a).

As shown in Figure 16b, the process of MN initiating release of SN may include the following steps:

S300: At time T3 after T2, the constantly moving satellite base station A-gNB1 is still anchored to the NTN-GW/5GC1, while the ground base station MN is also anchored to the same NTN-GW/5GC1. Both MN and 5GC1 have the ephemeris information of the LEO low-orbit satellite system according to the network management configuration information. For example, which LEO satellite will run to which orbital position at what time, and which area the beam corresponding to the satellite will cover. Therefore, MN and 5GC1 can speculate that during the observation period before and after T3, the overlap between the ground coverage of the satellite base station A-gNB1 beam and the wireless coverage of the main base station MN will gradually disappear, and the UE needs to withdraw from the satellite base station A- Ground-air dual connection operation of gNB1. The MN can continue to try to establish a new ground-air dual connection operation with the following satellite base station B-gNB2. A UE that is already in ground-air dual connection operation is being served by the primary base station MN cell (small ellipse in Figure 16a) and secondary base station SN-gNB1 (large ellipse in Figure 16a) at the same time, and PDU Session 2 and PDU Session 1 user services have been established respectively Data-related wireless resources and NG interfaces are connected to transmission channels, etc. The UE supports the P-UE and S-UE capability division of the application, and has reported the updated capability division information to the MN and 5GC1. Since the beam coverage of the satellite base station A-gNB1 is about to disappear, the remaining QoS Flows user service data in PDU Session1 needs to be returned to the MN to continue the bearer transmission, and the satellite base station A-gNB1 will also be deleted as a secondary base station. In step S300, the MN can report the updated P-UE and S-UE capabilities and resource division supported by the UE through a terminal radio capability report (UE RADIO CAPABILITY REPORT) message or a terminal capability information indication (UE CAPABILITY INFO INDICATION) message. Information.

S301: According to the ephemeris information of the LEO low-orbit satellite system, the MN does not rely on the RRM measurement report of the UE, and at an appropriate time, sends a SN RELEASE REQUIRED message to the 5GC1. The message includes a request to return all the remaining QoS Flows in the PDU Session1 currently being served by the SN-gNB1 side to the MN bearer for transmission, so that the SN-gNB1 as the UE secondary base station can be deleted and the ground-air dual connection operation can be exited. At the same time, the MN can also recommend the Data Forwarding operation, and provide the corresponding data forwarding transmission address information in the above message to reduce data packet loss in the return operation.

S302: 5GC1 receives the demand message of the MN, and according to the ephemeris information of the LEO low-orbit satellite system and the system's local policy, determines that all remaining QoS Flows in PDU Session1 can be returned to the MN. 5GC1 sends a secondary base station release command (SN RELEASE COMMAND) message to the target SN-gNB1. The message includes notifying the target SN-gNB1 to release, requesting to delete the remaining QoS Flows related radio resources in the SN-gNB1 side service PDU Session1, and the control plane, user plane, and transmission resources connected to the S-NG interface.

S303: SN-gNB1 receives the request message of 5GC1, can delete the remaining QoS Flows and all related resources in the PDU to be returned to Session1, and send a secondary base station release response message to 5GC1 after completion, for example: secondary base station release complete (SN RELEASE COMPLETE )news. This message includes notifying 5GC1 that it has successfully deleted the remaining QoS Flows and all related resources in PDU Session 1 and that SN-gNB1, which is the secondary base station of the UE, has been deleted. SN-gNB1 can also perform data forwarding (Data Forwarding) for the remaining QoS Flows returned.

S304: 5GC1 receives the release completion message of SN-gNB1, and learns that SN-gNB1 has successfully deleted the remaining QoS Flows and all related resources in PDU Session1, and thus sends a secondary base station release command (SN RELEASE COMMAND) message to the MN. The message includes the requirement to notify the MN to quit the dual connectivity operation of the entire UE capabilities that can be used and the remaining QoS Flows in PDU Session 1 to the MN side. Then the MN re-establishes the remaining QoS Flows and related radio resources in the returned PDU Session1, and the control plane, user plane, and transmission resources connected to the P-NG interface.

After S304: the MN and the UE continue to maintain the P-RL radio link through the RRC reconfiguration message, and then continue to transmit PDU Session2 user service data and all reflowed PDU Session1 user service data. The RRC release message is used between SN-gNB1 and S-UE to delete the original S-RL radio link. After that, SN-gNB1 no longer serves to transmit any PDU and Session user service data.

The release (RELEASE) in this application example is sometimes also called delete (DELETE). Correspondingly, the message related to release can also be modified to the message related to deletion. For example, a secondary base station delete request (SN DELETE REQUIRED) message, a secondary base station delete command (SN DELETE COMMAND) message, a secondary base station delete success (SN DELETE COMPLETE) message, etc. The following other application examples are similar situations, so I won't repeat them.

Application example 4: 5GC initiates the process of establishing or adding SN.

As shown in Figure 17a: In a LEO low-orbit satellite communication system, several LEO low-orbit satellites are in specific near-earth orbits. These satellites can orbit the Earth's circle periodically according to predetermined ephemeris information. They carry complete gNB base station functions (called gNB satellites) and provide satellite wireless access services for ground users UEs. There are several satellite ground station gateway (NTN-GW) entities deployed on the ground, which are integrated in the 5GC core network entity. Each LEO satellite relies on its own positioning capability, and can establish and maintain one or more Feeder link bearer links with one or more NTN-GW/5GCs on the ground according to the current physical latitude and longitude position. NG interface connection example. Each LEO satellite can project beam coverage to a predetermined area on the ground (the large ellipse in Figure 17a, usually with a coverage radius much larger than the coverage of the service cell of the ground base station). With the movement of LEO satellites, the beam coverage of these satellites also slides on the ground, forming inter-frequency overlapping coverage with the ground-based cellular coverage (small ellipse in Figure 17a). In step S400, the MN can report and coordinate the information of the P-UE and S-UE capability division supported by the UE through a terminal radio capability report (UE RADIO CAPABILITY REPORT) message or a terminal capability information indication (UE CAPABILITY INFO INDICATION) message.

As shown in Figure 17b, the process of adding SN initiated by 5GC may include the following steps:

S400: At T1, the anchor point of the satellite base station A-gNB1 is connected to the NTN-GW/5GC1, and the ground base station MN is also anchored to the same NTN-GW/5GC1. MN and 5GC1 have the ephemeris information of the LEO low-orbit satellite system according to the network management configuration information. For example, which LEO satellite will travel to which orbital position at what time, and which area the beam corresponding to the satellite will cover. Wait. Therefore, both MN and 5GC1 can speculate that during a period of observation time before and after T1, the ground coverage of the satellite base station A-gNB1 beam and the wireless coverage of the main base station MN overlap to a certain extent, so that the ground-air dual connection operation may be performed. A UE in a connected state is being served by the main base station MN cell (small ellipse in Figure 17a), and radio resources related to user service data of PDU Session1 and PDU Session2 and NG interface connection transmission channels have been established. The UE supports the P-UE and S-UE capability division of this application, and reports the supportable capability division information to the MN and 5GC1. According to the system's local policy (such as roaming security or billing factors), PDU Session2 user service data can be carried and transmitted by the LEO satellite radio link.

S401: Based on the ephemeris information of the LEO low-orbit satellite system and the system's local policy, 5GC1 determines that all QoS Flows in PDU Session 2 can be diverted to the target SN-gNB1, so that at a suitable moment, 5GC1 directly sends the auxiliary to the target SN-gNB1 Base station addition request (SN ADDITION REQUEST) message. This message includes notifying the target SN-gNB1 of the available S-UE capabilities, requesting the establishment of PDU and Session1 related radio resources on the SN-gNB1 side, and the control plane, user plane and transmission resources connected to the S-NG interface.

S402: SN-gNB1 receives the 5GC1 request message and performs local resource admission control. If SN-gNB1 determines that all relevant resources can be successfully established for PDU Session2, it can send a secondary base station addition response message to 5GC1, such as a secondary base station addition confirmation (SN ADDITION REQUEST ACKNOWLEDGE) message. This message includes notifying 5GC1 that PDU Session2 has been successfully established, as well as related radio resources on the SN-gNB1 side, and the control plane, user plane, and transmission resources connected to the S-NG interface. SN-gNB1 can also provide transmission address information for data forwarding at the same time, so as to realize the data forwarding operation from the MN side.

S403: 5GC1 receives the confirmation message from SN-gNB1, knows that the SN-gNB1 side has successfully offloaded to establish PDU Session2, and can send a secondary base station add command (SN ADDITION COMMAND) message to the MN. The message includes the P-UE capabilities and resources available to the MN informing the MN after entering the dual connectivity operation, and the result of successfully offloading PDU Session2 to the SN-gNB1 side. Then the MN can delete the related radio resources of the original service PDU Session2, the control plane, user plane, and transmission resources connected to the P-NG interface.

After S403: the P-RL radio link is established and maintained through the RRC reconfiguration message between the MN and the P-UE, and then only the PDU Session1 user service data is transmitted. SN-gNB1 and S-UE establish and maintain S-RL radio links through RRC reconfiguration messages, and then only transmit PDU and Session2 user service data.

Application example 5: SN initiates the process of modifying SN.

As shown in Figure 18a: In a LEO low-orbit satellite communication system, several LEO low-orbit satellites are in specific near-earth orbits. These satellites can orbit the Earth's circle periodically according to predetermined ephemeris information. They carry complete gNB base station functions (called gNB satellites) and provide satellite wireless access services for ground users UEs. There are several satellite ground station gateway (NTN-GW) entities deployed on the ground, which are integrated in the 5GC core network entity. Each LEO satellite relies on its own positioning capability, and can establish and maintain one or more Feeder link bearer links with one or more NTN-GW/5GCs on the ground according to the current physical latitude and longitude position. NG interface connection example. Each LEO satellite can project beam coverage to a predetermined area on the ground (the large ellipse in Figure 18a, usually with a coverage radius much larger than the coverage of the service cell of the ground base station). With the movement of LEO satellites, the beam coverage of these satellites also slides on the ground, forming inter-frequency overlapping coverage with land-based ground cellular coverage (the small ellipse in Figure 18a).

As shown in Figure 18b, the process of SN initiating modification of SN can include the following steps:

S500: At time T2 after T1, the constantly moving satellite base station A-gNB1 is still anchored to the NTN-GW/5GC1, while the ground base station MN is also anchored to the same NTN-GW/5GC1. MN and 5GC1 have the ephemeris information of the LEO low-orbit satellite system according to the network management configuration information. For example, which LEO satellite will travel to which orbital position at what time, and in which area its corresponding beam ground coverage is probably. Therefore, MN and 5GC1 can infer that during the observation period before and after T2, the ground coverage of the satellite base station A-gNB1 beam and the wireless coverage of the main base station MN still overlap to a certain extent, so that the ground-air dual connection operation can be maintained. . A UE that is already in ground-air dual connection operation is being served by the primary base station MN cell (small ellipse in Figure 18a) and secondary base station SN-gNB1 (large ellipse in Figure 18a) at the same time, and has established PDU Session 1 and PDU Session 2 user services Data-related wireless resources and NG interfaces are connected to transmission channels, etc. The UE supports the P-UE and S-UE capability division of this application, and reports the updated capability division information to the MN and 5GC1. Due to the local overload of the SN-gNB1 satellite, SN-gNB1 hopes to return part of the QoS Flows user service data in PDU Session 2 to the MN to continue the bearer transmission. In step S500, the MN can report the updated P-UE and S-UE capability split information supported by the UE through a terminal radio capability report (UE RADIO CAPABILITY REPORT) message or a terminal capability information indication (UE CAPABILITY INFO INDICATION) message .

S501: According to the ephemeris information of the LEO low-orbit satellite system, SN-gNB1 does not rely on the RRM measurement report of the UE, and actively sends a secondary base station modification request (SN MODIFICATION REQUIRED) message to the 5GC1 at an appropriate time. The message includes a request to return part of the QoS Flows in the PDU Session2 currently carrying the service on the SN-gNB1 side to the MN for bearer transmission. SN-gNB1 can also suggest data forwarding (Data Forwarding) operation to reduce data packet loss in the return operation.

S502: 5GC1 receives the request message from SN-gNB1, and according to the ephemeris information of the LEO low-orbit satellite system and the system's local policy, determines that part of the QoS Flows in PDU Session 2 can be returned to the MN. 5GC1 sends a secondary base station modification request (SN MODIFICATION REQUEST) message to the MN. The message includes notifying the MN of the available P-UE capabilities and resources after the update, requesting that the MN focus on configuring some of the reflowed PDUs and Session2 related radio resources, and the control plane, user plane, and transmission resources connected to the P-NG interface.

S503: The MN receives the request message of 5GC1. If part of the QoS Flows and related resources in the returned PDU Session 2 are successfully established, a secondary base station modification response message, such as a secondary base station modification confirmation (SN MODIFICATION REQUEST ACKNOWLEDGE) message, can be sent to the 5GC1. This message includes notifying 5GC1 that it has successfully established some QoS Flows and related resources in PDU Session2, successfully reconfiguring related radio resources on the MN side, and the control plane, user plane, and transmission resources connected to the P-NG interface. The MN can also provide data forwarding (Data Forwarding) transmission address information in the above message for some of the returned QoS Flows.

S504: 5GC1 receives the confirmation message from the MN, learns that the MN side has successfully established some QoS Flows and related resources in PDU Session2, and sends a secondary base station modification command (SN MODIFICATION COMMAND) message to SN-gNB1. The message includes the result of notifying SN-gNB1 to continue to maintain the available S-UE capabilities after the dual-connection operation is updated, and to successfully return part of the QoS Flows in PDU Session 2 to the MN side. Then SN-gNB1 deletes part of the QoS Flows and related radio resources in the returned PDU Session2, as well as the control plane, user plane, and transmission resources connected to the S-NG interface.

After S504: The MN and the P-UE continue to maintain the P-RL radio link through the RRC reconfiguration message, and then continue to transmit PDU Session1 user service data and part of the returned PDU Session2 user service data. SN-gNB1 and S-UE continue to maintain the S-RL radio link through RRC reconfiguration messages, and then continue to transmit part of the remaining PDU and Session2 user service data.

FIG. 19 is a schematic structural diagram of a connection device provided by an embodiment of the application. The device can be set in the core network element. As shown in FIG. 19, the device may include: a first sending module 71, configured to send a first indication message to the target secondary base station, where the first indication message includes a secondary message between the target secondary base station and the target terminal. First instruction information for connecting to perform a specified operation, where the specified operation includes establishing, adding, modifying, or deleting; the first receiving module 72 is configured to receive a first response message from the target secondary base station, the first response message Includes first result information corresponding to the first indication information.

In an implementation manner, as shown in FIG. 20, the device further includes: a second receiving module 73, configured to receive a first demand message from the primary base station, where the first demand message is that the primary base station detects Sent when the wireless connection status between the target terminal and multiple base stations changes, the first demand message includes first demand information for performing the specified operation on the secondary connection, and the first demand information It includes required information for the establishment, addition, modification, deletion or release of the auxiliary connection.

In an implementation manner, the device further includes: a second sending module 74, configured to send a second indication message to the primary base station when the first result information indicates that the specified operation is successful, and the second The instruction message includes the first result information and main connection command information corresponding to the first result information.

In an implementation manner, the device further includes: a third receiving module 75, configured to receive a second demand message from a target secondary base station, where the second demand message is when the target secondary base station detects the target terminal Sent when the wireless connection status with multiple base stations changes, the second demand message includes second demand information for performing the specified operation on the secondary connection, and the second demand information includes The third sending module 76 is configured to send a third instruction message to the primary base station, where the third instruction message includes the primary connection command information corresponding to the second demand information; The fourth receiving module 77 is configured to receive a second response message from the main base station, where the second response message includes second result information corresponding to the main connection command information.

In an implementation manner, the first indication message is a secondary base station establishment request message or a secondary base station addition request message, and the first indication information includes the available secondary connection capability and resource information in the target terminal, and the need for offloading User service characteristic information to the target secondary base station.

In an embodiment, the first indication message is a secondary base station modification request message, and the first indication information includes user service feature information that needs to be returned from the target secondary base station to the primary base station, or re-distributed to the target secondary base station. User service characteristic information.

In an implementation manner, the first indication message is a secondary base station release command message or a secondary base station delete command message, and the first indication information includes remaining user service feature information on the target secondary base station that needs to be deleted.

In an embodiment, the first demand message is a secondary base station establishment demand message or a secondary base station add demand message, and the first demand message includes user service characteristic information that needs to be offloaded to the target secondary base station.

In an implementation manner, the first demand message is a secondary base station modification demand message, and the first demand message includes user service characteristic information that needs to be returned to the primary base station, or user service characteristic information that needs to be redirected to the target secondary base station.

In an implementation manner, the first demand message is a secondary base station release demand message or a secondary base station delete demand message, and the first demand message includes remaining user service characteristic information on the target secondary base station that needs to be deleted.

In an implementation manner, the second indication message is a secondary base station setup command message or a secondary base station add command message, and the second indication message includes available primary connection capability and resource information in the target terminal, and offloaded User service characteristic information to the target secondary base station.

In an implementation manner, the second indication message is a secondary base station modification command message, and the second indication message includes available primary connection capability and resource information in the target terminal, and user service characteristics that need to be returned to the primary base station Information, or user service characteristic information that has been diverted to the target secondary base station.

In one embodiment, the second indication message is a secondary base station release command message or a secondary base station delete command message, and the second indication message includes the available primary connection capability and resource information in the target terminal, and the need to return User service characteristic information remaining on the target secondary base station to the primary base station.

In an embodiment, the second demand message is a secondary base station modification demand message, the second demand information includes user service characteristic information that needs to be returned to the primary base station; the third indication message is a secondary base station modification request message The third indication message includes the available primary connection capability and resource information in the target terminal, and user service feature information that needs to be returned to the primary base station; the first indication information is a secondary base station modification command message, and the first The indication message includes the available auxiliary connection capability and resource information in the target terminal, and user service characteristic information that has been returned to the primary base station.

In an embodiment, the second demand message is a secondary base station release demand message or a secondary base station delete demand message, and the second demand information includes user service feature information remaining on the target secondary base station that needs to be deleted; The third indication message is the secondary base station release command message or the secondary base station delete command message. The third indication message includes the available primary connection capability and resource information in the target terminal, and the remaining users on the target secondary base station that need to be returned to the primary base station Service characteristic information; the first indication information is a secondary base station release command message or a secondary base station delete command message, and the remaining user service characteristic information on the target secondary base station that needs to be deleted in the first indication message.

FIG. 21 is a schematic structural diagram of a connection device provided by another embodiment of the application. The device can be set in the network element of the access network. As shown in FIG. 21, the apparatus may include: a fifth receiving module 81, configured to receive a first indication message from a core network element, where the first indication message includes a secondary base station and a target terminal. First instruction information for the connection to perform a specified operation, where the specified operation includes establishment, addition, modification or deletion; an execution module 82, configured to perform the specified operation on the secondary connection between the target secondary base station and the target terminal The fifth sending module 83 is configured to send a first response message to the core network element, where the first response message includes first result information corresponding to the first indication message.

In an implementation manner, as shown in FIG. 22, the device further includes: a sixth sending module 84, configured to send notification to the target terminal when the wireless connection status between the target terminal and multiple base stations has changed The core network element sends a first demand message, the first demand message includes first demand information for performing the specified operation on the secondary connection, and the first demand message includes the establishment and addition of the secondary connection. , Modification, deletion or release requirements.

In an embodiment, the device further includes: a sixth receiving module 85, configured to receive a second indication message from the core network element, where the second indication message is when the core network element is located at all The first result information indicates that it is sent when the specified operation is successful, and the second indication message includes the first result information and main connection command information corresponding to the first result information.

In an implementation manner, the device further includes: a seventh sending module 86, configured to send the first sending module to the core network element when the wireless connection status between the target terminal and the multiple base stations has changed. 2. A demand message. The second demand message includes second demand information for performing the specified operation on the secondary connection, and the second demand information includes a demand for modification, deletion, or release of the secondary connection.

In an implementation manner, the device further includes: a seventh receiving module 87, configured to receive a third indication message from the core network element, where the third indication message includes information corresponding to the second demand information The eighth sending module 88 is configured to send a second response message to the core network element, where the second response message includes second result information corresponding to the main connection command information.

In an embodiment, the first demand message is a secondary base station establishment demand message or secondary base station addition demand message, and the first demand message includes user service characteristic information that needs to be offloaded to the target secondary base station.

In an implementation manner, the first demand message is a secondary base station modification demand message, and the first demand message includes user service characteristic information that needs to be returned to the primary base station, or user service characteristic information that needs to be redirected to the target secondary base station .

In an implementation manner, the second demand message is a secondary base station modification demand message, and the second demand information includes user service characteristic information that needs to be returned to the primary base station;

The third indication message is a secondary base station modification request message, and the third indication message includes available primary connection capability and resource information in the target terminal, and user service characteristic information that needs to be returned to the primary base station;

In an embodiment, the second demand message is a secondary base station release demand message or a secondary base station delete demand message, and the second demand information includes user service feature information remaining on the target secondary base station that needs to be deleted; The third indication message is a secondary base station release command message or a secondary base station delete command message. The third indication message includes the available primary connection capability and resource information in the target terminal, and the remaining users on the target secondary base station that need to be returned to the primary base station Service characteristic information; the first indication information is a secondary base station release command message or a secondary base station delete command message, and the remaining user service characteristic information on the target secondary base station that needs to be deleted in the first indication message.

In an embodiment, the execution module is further configured to establish an auxiliary connection with the target terminal according to the available auxiliary connection capability and resource information in the target terminal, and user service characteristic information that needs to be offloaded to the target auxiliary base station, The user service is offloaded to the target secondary base station, so that the target secondary base station continues to carry the transmission.

In an implementation manner, the execution module is also used to delete user service bearer transmission resources that need to be returned from the target secondary base station, or allocate new bearer transmission resources for re-offloaded user services.

In an implementation manner, the execution module is further configured to delete the remaining user service bearer transmission resources from the target secondary base station, and release or delete the target secondary base station.

For the functions of the modules in the devices in the embodiments of the present application, reference may be made to the corresponding descriptions in the foregoing method embodiments, and details are not described herein again.

FIG. 23 is a schematic structural diagram of a network device provided by an embodiment of the application. As shown in FIG. 23, the network device 130 provided by an embodiment of the present application includes a memory 1303 and a processor 1304. The network device 130 may further include an interface 1301 and a bus 1302. The interface 1301, the memory 1303 and the processor 1304 are connected through a bus 1302. The memory 1303 is used to store instructions. The processor 1304 is configured to read the instructions to execute the technical solutions of the foregoing method embodiments applied to an access network element. The implementation principles and technical effects are similar, and details are not described herein again.

FIG. 24 is a schematic structural diagram of a network device provided by an embodiment of this application. As shown in FIG. 24, a network device 140 provided by an embodiment of this application includes a memory 1403 and a processor 1404. The network device may also include an interface 1401 and a bus 1402. The interface 1401, the memory 1403 and the processor 1404 are connected through a bus 1402. The memory 1403 is used to store instructions. The processor 1404 is configured to read the instructions to execute the technical solutions of the foregoing method embodiments applied to core network elements. The implementation principles and technical effects are similar and will not be repeated here.

FIG. 25 is a schematic structural diagram of a communication system provided by an embodiment of this application. As shown in FIG. 25, the system includes: a network device 130 according to the above-mentioned embodiment and a network device 140 according to the above-mentioned embodiment.

The present application provides a storage medium that stores a computer program, and when the computer program is executed by a processor, the method in the foregoing embodiment is implemented.

The above are only the preferred embodiments of the present application, and are not used to limit the protection scope of the present application.

In general, the various embodiments of the present application can be implemented in hardware or dedicated circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor or other computing device, although the application is not limited thereto.

The embodiments of the present application may be implemented by executing computer program instructions by a data processor of a mobile device, for example, in a processor entity, or by hardware, or by a combination of software and hardware. Computer program instructions can be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source code written in any combination of one or more programming languages or Target code.

The block diagram of any logical flow in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program can be stored on the memory. The memory can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology. The memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory, etc. The volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache. RAM can include many forms, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronization Dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (Synchlink DRAM, SLDRAM) and direct memory bus random access Memory (Direct Rambus RAM, DR RAM). The memory of the system and method described in this application includes but is not limited to these and any other suitable types of memory.

The processor of the embodiment of the present application may be of any type suitable for the local technical environment, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (Digital Signal Processors, DSP), and application specific integrated circuits (Application Specific Integrated Circuit, ASIC), Field-Programmable Gate Array (FGPA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or processors based on multi-core processor architecture. The general-purpose processor may be a microprocessor or any conventional processor. The foregoing processor may implement or execute the steps of each method disclosed in the embodiments of the present application. The software module may be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

By way of exemplary and non-limiting examples, a detailed description of the exemplary embodiments of the present application has been provided above. However, considering the accompanying drawings and claims, various modifications and adjustments to the above embodiments are obvious to those skilled in the art, but they do not deviate from the scope of the present application. Therefore, the proper scope of the application will be determined according to the claims.

Claims

A connection method includes:

Send a first instruction message to the target secondary base station, where the first instruction message includes first instruction information for performing a designated operation on the secondary connection between the target secondary base station and the target terminal, and the designated operation includes establishing, adding, and modifying , Delete or release;

Receiving a first response message from the target secondary base station, where the first response message includes first result information corresponding to the first indication information.
The method according to claim 1, further comprising:

Receiving a first demand message from a primary base station, the first demand message being sent by the primary base station upon detecting that the wireless connection status between the target terminal and multiple base stations has changed, the first demand message It includes first demand information for performing the specified operation on the auxiliary connection, and the first demand information includes demand information for the establishment, addition, modification, deletion, or release of the auxiliary connection.
The method according to claim 1 or 2, further comprising:

In a case where the first result information indicates that the specified operation is successful, a second indication message is sent to the master base station, where the second indication message includes the first result information and the master corresponding to the first result information. Connection command information.
The method according to claim 1, further comprising:

Receiving a second demand message from the target secondary base station, the second demand message being sent by the target secondary base station upon detecting that the wireless connection status between the target terminal and multiple base stations has changed, and The second demand message includes second demand information for performing the specified operation on the secondary connection, and the second demand information includes demand information for modification, deletion, or release of the secondary connection;

Sending a third instruction message to the primary base station, where the third instruction message includes primary connection command information corresponding to the second demand information;

Receiving a second response message from the primary base station, where the second response message includes second result information corresponding to the primary connection command information.
The method according to claim 1, wherein the first indication message is a secondary base station establishment request message or a secondary base station addition request message, and the first indication information includes available secondary connection capability and resource information in the target terminal , And user service characteristic information that needs to be offloaded to the target secondary base station.
The method according to claim 1, wherein the first indication message is a secondary base station modification request message, and the first indication information includes user service characteristic information that needs to be returned from the target secondary base station to the primary base station, or restart User service feature information shunted to the target secondary base station.
The method according to claim 1, wherein the first indication message is a secondary base station release command message or a secondary base station delete command message, and the first indication information includes remaining user services on the target secondary base station that need to be deleted Characteristic information.
The method of claim 2, wherein:

The first demand message is a secondary base station establishment demand message or a secondary base station add demand message, and the first demand message includes user service characteristic information that needs to be offloaded to the target secondary base station.
The method of claim 2, wherein:

The first demand message is a secondary base station modification demand message, and the first demand message includes user service characteristic information that needs to be returned to the primary base station, or user service characteristic information that needs to be redirected to the target secondary base station.
The method of claim 2, wherein:

The first demand message is a secondary base station release demand message or a secondary base station deletion demand message, and the first demand message includes remaining user service feature information on the target secondary base station that needs to be deleted.
The method according to claim 3, wherein the second indication message is a secondary base station setup command message or a secondary base station add command message, and the second indication message includes available primary connection capability and resource information in the target terminal , And user service characteristic information that has been offloaded to the target secondary base station.
The method according to claim 3, wherein the second indication message is a secondary base station modification command message, and the second indication message includes the available primary connection capability and resource information in the target terminal, and the need to return to the primary The user service feature information of the base station, or the second indication message includes the available primary connection capability and resource information in the target terminal, and the user service feature information that has been offloaded to the target secondary base station.
The method according to claim 3, wherein the second indication message is a secondary base station release command message or a secondary base station delete command message, and the second indication message includes available primary connection capability and resource information in the target terminal , And the remaining user service feature information on the target secondary base station that needs to be returned to the primary base station.
The method of claim 4, wherein:

The second demand message is a secondary base station modification demand message, and the second demand information includes user service characteristic information that needs to be returned to the primary base station;

The third indication message is a secondary base station modification request message, and the third indication message includes available primary connection capability and resource information in the target terminal, and user service characteristic information that needs to be returned to the primary base station;

The first indication information is a secondary base station modification command message, and the first indication message includes available secondary connection capability and resource information in the target terminal, and user service characteristic information that has been returned to the primary base station.
The method of claim 4, wherein:

The second demand message is a secondary base station release demand message or a secondary base station delete demand message, and the second demand information includes remaining user service feature information on the target secondary base station that needs to be deleted;

The third indication message is a secondary base station release command message or a secondary base station delete command message, and the third indication message includes the available primary connection capability and resource information in the target terminal, and all the information that needs to be returned to the primary base station. The remaining user service feature information on the target secondary base station;

The first indication information is a secondary base station release command message or a secondary base station delete command message, and the first indication message includes the remaining user service feature information on the target secondary base station that needs to be deleted.
A connection method includes:

The target secondary base station receives a first indication message from the core network element, where the first indication message includes first indication information for performing a specified operation on the secondary connection between the target secondary base station and the target terminal, and the specified operation includes establishing, Add, modify, delete or release;

Performing the designated operation by the target secondary base station on the secondary connection between the target secondary base station and the target terminal;

The target secondary base station sends a first response message to the core network element, where the first response message includes first result information corresponding to the first indication message.
The method according to claim 16, further comprising:

Upon detecting that the wireless connection status between the target terminal and multiple base stations has changed, the primary base station sends a first demand message to the core network element, where the first demand message includes the execution of the secondary connection The first demand information of the specified operation, the first demand message includes a demand message for the establishment, addition, modification, deletion, or release of the secondary connection.
The method according to claim 16, further comprising:

The primary base station receives a second indication message from the core network element, and the second indication message is sent by the core network element when the first result information indicates that the specified operation is successful. The second indication message includes the first result information and main connection command information corresponding to the first result information.
The method according to claim 16, further comprising:

When the target secondary base station detects that the wireless connection status between the target terminal and multiple base stations has changed, the target secondary base station sends a second demand message to the core network element, where the second demand message includes The second demand information for connecting to perform the specified operation, where the second demand information includes demand information for modification, deletion, or release of the auxiliary connection.
The method of claim 19, further comprising:

The primary base station receives a third instruction message from the core network element, where the third instruction message includes primary connection command information corresponding to the second demand information;

The primary base station sends a second response message to the core network element, where the second response message includes second result information corresponding to the primary connection command information.
The method according to claim 16, wherein the first indication message is a secondary base station establishment request message or a secondary base station addition request message, and the first indication information includes available secondary connection capability and resource information in the target terminal , And user service characteristic information that needs to be offloaded to the target secondary base station.
The method according to claim 16, wherein the first indication message is a secondary base station modification request message, and the first indication information includes user service characteristic information that needs to be returned from the target secondary base station to the primary base station, or re- User service feature information shunted to the target secondary base station.
The method according to claim 16, wherein the first indication message is a secondary base station release command message or a secondary base station delete command message, and the first indication information includes the remaining user service on the target secondary base station that needs to be deleted Characteristic information.
The method of claim 17, wherein:

The first demand message is a secondary base station establishment demand message or a secondary base station add demand message, and the first demand message includes user service characteristic information that needs to be offloaded to the target secondary base station.
The method of claim 17, wherein:

The first demand message is a secondary base station modification demand message, and the first demand message includes user service characteristic information that needs to be returned to the primary base station, or user service characteristic information that needs to be redirected to the target secondary base station.
The method of claim 17, wherein:

The first demand message is a secondary base station release demand message or a secondary base station deletion demand message, and the first demand message includes remaining user service feature information on the target secondary base station that needs to be deleted.
The method according to claim 18, wherein the second indication message is a secondary base station setup command message or a secondary base station add command message, and the second indication message includes available primary connection capability and resource information in the target terminal , And user service characteristic information that has been offloaded to the target secondary base station.
The method according to claim 18, wherein the second instruction message is a secondary base station modification command message, and the second instruction message includes the available primary connection capability and resource information in the target terminal, and the need to return to the primary The user service characteristic information of the base station, or the your second indication message includes the available primary connection capability and resource information in the target terminal, and the user service characteristic information that has been offloaded to the target secondary base station.
The method according to claim 18, wherein the second indication message is a secondary base station release command message or a secondary base station delete command message, and the second indication message includes available primary connection capability and resource information in the target terminal , And the remaining user service feature information on the target secondary base station that needs to be returned to the primary base station.
The method of claim 20, wherein:

The second demand message is a secondary base station modification demand message, and the second demand information includes user service characteristic information that needs to be returned to the primary base station;

The third indication message is a secondary base station modification request message, and the third indication message includes available primary connection capability and resource information in the target terminal, and user service feature information that needs to be returned to the primary base station;

The first indication information is a secondary base station modification command message, and the first indication message includes available secondary connection capability and resource information in the target terminal, and user service characteristic information that has been returned to the primary base station.
The method of claim 20, wherein:

The second demand message is a secondary base station release demand message or a secondary base station delete demand message, and the second demand information includes remaining user service feature information on the target secondary base station that needs to be deleted;

The third indication message is a secondary base station release command message or a secondary base station delete command message, and the third indication message includes the available primary connection capability and resource information in the target terminal, and the target secondary base station that needs to return to the primary base station The remaining user service feature information on the Internet;

The first indication information is a secondary base station release command message or a secondary base station delete command message, and the remaining user service feature information on the target secondary base station that needs to be deleted in the first indication message.
The method according to claim 21, 24 or 27, wherein the target secondary base station performing the designated operation on the secondary connection between the target secondary base station and the target terminal comprises:

The target secondary base station establishes the secondary connection between the target secondary base station and the target terminal according to the available secondary connection capability and resource information in the target terminal and the user service characteristic information that needs to be offloaded to the target secondary base station, so as to The user service is offloaded to the target secondary base station, so that the target secondary base station continues to carry and transmit.
The method according to claim 22, 25, 28 or 30, wherein the target secondary base station performing the designated operation on the secondary connection between the target secondary base station and the target terminal comprises:

The target secondary base station deletes the user service bearer transmission resources that need to be returned from the target secondary base station, or allocates new bearer transmission resources for the re-offloaded user services.
The method according to claim 23, 26, 29 or 31, wherein the target secondary base station performing the designated operation on the secondary connection between the target secondary base station and the target terminal comprises:

The target secondary base station deletes the remaining user service bearer transmission resources from the target secondary base station, and releases or deletes the target secondary base station.
A connecting device includes:

A sending module, configured to send a first instruction message to the target secondary base station, the first instruction message including first instruction information for performing a designated operation on the secondary connection between the target secondary base station and the target terminal, the designated operation including Create, add, modify or delete;

The receiving module is configured to receive a first response message from the target secondary base station, where the first response message includes first result information corresponding to the first indication information.
A connecting device includes:

The receiving module is configured to receive a first instruction message from a core network element, where the first instruction message includes first instruction information for performing a specified operation on the secondary connection between the target secondary base station and the target terminal, and the specified operation includes Create, add, modify or delete;

An execution module, configured to execute the specified operation on the secondary connection between the target secondary base station and the target terminal;

The sending module is configured to send a first response message to the core network element, where the first response message includes first result information corresponding to the first indication message.
A network device, including: a processor and a memory;

The memory is configured to store instructions;

The processor is configured to read the instructions to perform the method of any one of claims 1 to 34.
A storage medium storing a computer program, which implements the method of any one of claims 1 to 34 when the computer program is executed by a processor.