Configuration information sending method, configuration information receiving method, communication node and storage medium

Abstract

The invention discloses a configuration information sending method, a configuration information receiving method, a communication node and a storage medium. The configuration information sending method is applied to a first communication node and comprises the steps that after application layer connection with a second communication node is established, a first request message is sent to a third communication node, and the first request message is used for requesting to subscribe configuration information of a fourth communication node; a first notification message sent by the third communication node is received, the first notification message comprises first configuration information, and the first configuration information is configuration information of a fourth communication node; and sending the first configuration information to the second communication node, and sending second configuration information to the fourth communication node, the second configuration information being configuration information of the second communication node.

Description

A method for sending and receiving configuration information, a communication node, and a storage medium. Technical Field

[0001] This application relates to the field of communication technology, such as a method for sending and receiving configuration information, a communication node, and a storage medium. Background Technology

[0002] In the current 5G network architecture, the Access and Mobility Management Function (AMF) and the base station connect using the Stream Control Transmission Protocol (SCTP). Therefore, the Internet Protocol (IP) addresses of both parties need to be statically configured, and an SCTP connection is established first upon power-up, followed by a Next Generation Application Protocol (NGAP) connection. Consequently, changes to the AMF (such as deletion or addition) may alter the AMF configuration on the base station. However, since most existing AMFs are deployed on cloud platforms, they are subject to frequent scaling up and down, resulting in significant impacts on the base station when AMF changes occur, thus reducing system performance. Summary of the Invention

[0003] This application provides a method for sending configuration information, applied to a first communication node, including:

[0004] After establishing an application layer connection with the second communication node, a first request message is sent to the third communication node. The first request message is used to request to subscribe to the configuration information of the fourth communication node.

[0005] Receive a first notification message sent by a third communication node. The first notification message includes first configuration information, which is the configuration information of a fourth communication node.

[0006] Send first configuration information to the second communication node and send second configuration information to the fourth communication node, wherein the second configuration information is the configuration information of the second communication node.

[0007] This application provides a method for receiving configuration information, applied to a fourth communication node, including:

[0008] Receive second configuration information sent by the first communication node. The second configuration information is the configuration information of the second communication node that has established an application layer connection with the first communication node.

[0009] This application provides a communication node, including: a processor; the processor is used to implement the method of any of the above embodiments when executing a computer program.

[0010] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the method of any of the above embodiments.

[0011] Further details regarding the above embodiments and other aspects of this application, as well as their implementations, are provided in the accompanying drawings, detailed description, and claims. Attached Figure Description

[0012] Figure 1 is a schematic diagram of an existing 5G system network architecture;

[0013] Figure 2 is a schematic diagram of an existing N2 interface protocol stack between AMF and RAN;

[0014] Figure 3 is a schematic diagram of a core network architecture provided in one embodiment;

[0015] Figure 4 is a schematic diagram of a protocol stack between CMF, AMF, and RAN provided in an embodiment;

[0016] Figure 5 is a flowchart illustrating a method for sending configuration information according to an embodiment;

[0017] Figure 6 is a flowchart illustrating a method for receiving configuration information according to an embodiment;

[0018] Figure 7 is an interactive flowchart of configuration information provided in Example 1;

[0019] Figure 8 is an interactive flowchart of an access message provided in Example 2;

[0020] Figure 9 is a schematic diagram of a configuration information sending device according to an embodiment;

[0021] Figure 10 is a schematic diagram of another configuration information sending device provided in an embodiment;

[0022] Figure 11 is a schematic diagram of the structure of another configuration information sending device provided in an embodiment;

[0023] Figure 12 is a schematic diagram of a configuration information receiving device according to an embodiment;

[0024] Figure 13 is a schematic diagram of the structure of another configuration information receiving device provided in an embodiment;

[0025] Figure 14 is a schematic diagram of the structure of a communication node provided in one embodiment. Detailed Implementation

[0026] It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application. The embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0027] Figure 1 is a schematic diagram of an existing 5G system network architecture. As shown in Figure 1, the existing 5G system network architecture can include at least: User Equipment (UE), Radio Access Network (RAN), AMF, User Plane Function (UPF), Session Management Function (SMF), Network Repository Function (NRF), Policy Control Function (PCF), Unified Data Management (UDM), and Data Network.

[0028] The UE accesses the RAN through the Uu interface and the core network element AMF through the N1 interface.

[0029] RAN, also known as radio base station, is responsible for resource allocation of the Uu interface and access control of the UE.

[0030] The AMF manages user access to the network and is responsible for signaling management and user mobility management at the Non-Access Stratum (NAS) layer from the UE to the network. Its main functions include user registration management, connection management, mobility management, security management, and session management.

[0031] UDM is the permanent storage location for user subscription data, located on the home network to which the user has subscribed.

[0032] The SMF is used to manage user Packet Data Unit (PDU) sessions and Quality of Service (QoS) flows, and to define packet detection and forwarding rules for the UPF. The SMF is configured locally or receives session policy control rules from the PCF, and the policy control rules control the data transmission path and QoS policy between the UPF and the UE.

[0033] UPF is responsible for routing and forwarding IP data and non-IP data, as well as usage reporting, based on the rules issued by SMF.

[0034] The PCF provides session policy rules to the SMF based on user subscriptions, application requirements, and local configuration. Simultaneously, the PCF can also send UE Route Selection Policy (URSP) rules to the UE through the AMF, controlling the UE to generate appropriate PDU session parameters based on different application requests.

[0035] The Network Function (NRF) is primarily responsible for the registration, discovery, management, and configuration of Network Functions (NFs). By managing NF registration and discovery, the NRF supports the dynamic deployment and optimization of 5G networks, enabling the adjustment of network resources based on real-time needs.

[0036] A data network is a network that provides services to users through the user plane. Users access the data network through PDU sessions.

[0037] Figure 2 is a schematic diagram of an existing N2 interface protocol stack between the AMF and RAN. As shown in Figure 2, the transport layer between the AMF and RAN uses SCTP connection, and the application layer uses NGAP connection. The NGAP connection message header includes two identifiers (IDs): the RAN UE NGAP ID and the AMF UE NGAP ID. The RAN UE NGAP ID uniquely identifies the UE on the Next Generation (NG) interface within the RAN, and the AMF UE NGAP ID uniquely identifies the UE on the NG interface within the AMF. A user-related NGAP connection is identified by the RAN UE NGAP ID and the AMF UE NGAP ID.

[0038] As shown in Figures 1 and 2, because the AMF and RAN use an SCTP connection, their IP addresses need to be statically configured, and an SCTP connection must be established first upon power-up, followed by an NGAP connection. Therefore, changes to the AMF (such as deletion or addition) may cause changes to the RAN configuration (such as the AMF's SCTP connection parameters). However, since most existing AMFs are deployed on cloud platforms and experience frequent scaling up and down, changes to the AMF have a significant impact on the RAN.

[0039] The method for sending and receiving configuration information provided in this application can be applied to various wireless communication systems, such as 5G systems, long term evolution (LTE) and 5G hybrid architecture systems, 5G New Radio (NR) systems, and new communication systems that will emerge in the future development of communication, such as 6th-generation (6G) mobile communication technology systems.

[0040] Figure 3 is a schematic diagram of a core network architecture provided in one embodiment. As shown in Figure 3, this application adds a core network element connection management function (CMF) between the AMF and RAN based on the existing 5G system network architecture. The CMF is responsible for the connection management between the AMF and RAN. The CMF and core network elements (such as UDM, PCF, NRF, SMF, AMF, etc.) adopt a service-oriented interface, and the CMF and RAN adopt the N2 interface based on Quick UDP Internet Connections (QUIC).

[0041] Figure 4 is a schematic diagram of a protocol stack between CMF, AMF, and RAN according to an embodiment. As shown in Figure 4, the transport layer between CMF and RAN uses QUIC connection, and the application layer uses NGAP connection; the transport layer between CMF and AMF uses QUIC connection, and the application layer uses Hypertext Transfer Protocol (HTTP) connection. The interface between CMF and AMF uses a Service Based Interface (SBI).

[0042] CMF can mainly perform the following functions:

[0043] 1) Manage QUIC connections between CMF and RAN, and between CMF and AMF.

[0044] 2) Maintain the NGAP connection between CMF and RAN.

[0045] 3) Convert the NGAP messages sent by the RAN into SBI messages and select the appropriate AMF for transmission.

[0046] 4) Convert the SBI message sent by AMF into an NGAP message and select the appropriate RAN for transmission.

[0047] The configuration information transmission method provided in this application embodiment can be applied to a first communication node, and the configuration information reception method can be applied to a fourth communication node. The first communication node can be a CMF, and the fourth communication node can be an AMF. Additionally, the second communication node mentioned in this application embodiment can be a RAN, and the third communication node can be an NRF.

[0048] In this embodiment, a method for sending configuration information, a method for receiving configuration information, a communication node, and a storage medium are provided. By adding a new CMF (Configuration Management Function), the RAN (Radio Range) only sees the CMF functionality, thereby minimizing the impact on the RAN when the AMF (Configuration Management Function) changes. Furthermore, the CMF and RAN communicate using the QUIC protocol. Since the QUIC protocol is carried on the User Datagram Protocol (UDP), it offers better performance, and establishing a QUIC connection is simpler than establishing a traditional SCTP connection.

[0049] The following describes the methods for sending and receiving configuration information, the communication nodes, and their technical effects.

[0050] Figure 5 is a flowchart illustrating a method for sending configuration information according to an embodiment. As shown in Figure 5, the method provided in this embodiment is applicable to a first communication node, which may also be referred to as a first communication node device, a first node, a first device, or a first communication entity. For example, in this embodiment, the first communication node may be a CMF, the second communication node may be a RAN, the third communication node may be an NRF, and the fourth communication node may be an AMF. The method includes the following steps.

[0051] S510. After establishing an application layer connection with the second communication node, a first request message is sent to the third communication node. The first request message is used to request to subscribe to the configuration information of the fourth communication node.

[0052] In one embodiment, the first communication node can establish an application layer connection with one or more second communication nodes, i.e., the number of second communication nodes is one or more. The application layer connection can be an NGAP connection.

[0053] In one embodiment, the method for establishing an application layer connection between a first communication node and a second communication node may include: firstly, the first communication node and the second communication node establish a transport layer connection, which may be a QUIC connection; then, the first communication node receives a second request message sent by the second communication node through the transport layer connection, the second request message being used to request the establishment of an application layer connection; finally, the first communication node sends a second notification message to the second communication node to indicate that the application layer connection has been established.

[0054] The second request message may carry at least one of the following information: a second communication node identifier for identifying the second communication node; location information of the second communication node (such as a Tracking Area Identity (TAI) list); and network slice information supported by the location information of the second communication node (such as Single Network Slice Selection Assistance Information (S-NSSAI)). Upon receiving the second request message, the first communication node may save the information carried in the second request message so that the first communication node can promptly understand the relevant configuration of the second communication node with which it has established an application layer connection.

[0055] Since the first communication node may already be connected to some fourth communication nodes, meaning the first communication node locally stores configuration information for some of the fourth communication nodes, a third configuration information—the configuration information of the fourth communication nodes stored locally by the first communication node—can be included in the second notification message to save signaling overhead. This third configuration information is the configuration information of the fourth communication nodes stored locally by the first communication node. This allows the second communication node to store the configuration information of the fourth communication nodes stored locally by the first communication node.

[0056] The configuration information of the fourth communication node stored locally by the first communication node may include at least one of the following: the identifier of the fourth communication node stored locally by the first communication node, the location information managed by the fourth communication node (such as the TAI list) stored locally by the first communication node, and the network slice information supported by the fourth communication node (such as S-NSSAI) stored locally by the first communication node.

[0057] In one embodiment, the first request message is sent to the third communication node to request subscription to the configuration information of the fourth communication node. In one possible implementation, the first request message is used to request subscription to the configuration information of all fourth communication nodes on the third communication node; in another possible implementation, the first request message is used to request subscription to the configuration information of fourth communication nodes that have changed on the third communication node (e.g., newly registered, deleted, or updated).

[0058] The first request message may include at least one of the following: a first communication node identifier, used to identify the identity of the first communication node; and the location information of the second communication node (such as a TAI list).

[0059] S520: Receive a first notification message sent by a third communication node. The first notification message includes first configuration information, which is the configuration information of a fourth communication node.

[0060] The first notification message is a message sent by the third communication node to the first communication node when it determines that the subscription conditions of the aforementioned first request message are met. Since the first request message requests to subscribe to the configuration information of the fourth communication node, the first notification message includes first configuration information, which is the configuration information of the fourth communication node.

[0061] The configuration information of the fourth communication node includes at least one of the following: the fourth communication node identifier, the location information managed by the fourth communication node (such as the TAI list), and the network slice information supported by the fourth communication node (such as S-NSSAI).

[0062] In one embodiment, when the first request message carries a first communication node identifier, the subscription conditions may be related to the first communication node identifier. For example, the configuration information of the fourth communication node includes the corresponding first communication node identifier.

[0063] When the first request message carries the location information of the second communication node, the subscription conditions may be related to the location information of the second communication node. For example, the location information of the second communication node matches the location information managed by the fourth communication node. Here, "matching" means that the location information of the second communication node and the location information managed by the fourth communication node are at least partially consistent.

[0064] S530, send first configuration information to the second communication node and send second configuration information to the fourth communication node, wherein the second configuration information is the configuration information of the second communication node.

[0065] After obtaining the first configuration information, the first communication node can also send the first configuration information to the second communication node. The first configuration information can be carried in messages such as the first update request message or the first update signaling, so that the second communication node can update the configuration information of the fourth communication node.

[0066] The first communication node can also send second configuration information to the fourth communication node. The second configuration information is the configuration information of the second communication node. The second configuration information can be carried in messages such as a second update request message or a second update signaling, so that the fourth communication node can update the configuration information of the second communication node.

[0067] The configuration information of the second communication node includes at least one of the following: the second communication node identifier, the location information of the second communication node (such as the TAI list), and the network slice information supported by the location information of the second communication node (such as S-NSSAI).

[0068] In this way, the configuration information of the second communication node and the fourth communication node can be exchanged. Since the second and fourth communication nodes are connected through the first communication node, changes to either the second or fourth communication node will not affect the other node, thereby improving system performance.

[0069] Furthermore, there is no specific order of execution between "sending the first configuration information to the second communication node" and "sending the second configuration information to the fourth communication node" in step S530. The first communication node can determine the order of sending the configuration information based on the configuration or its own capabilities, and this embodiment does not impose specific restrictions on this.

[0070] In one embodiment, the fourth communication node can implicitly subscribe to the changes of the second communication node from the first communication node. When the first communication node determines that the subscription conditions are met (such as a change in the second communication node (e.g., new registration, deletion, or update)), the first communication node can send a third notification message to the fourth communication node. The third notification message includes fourth configuration information, which is the configuration information of the changed second communication node. This allows the fourth communication node to update the configuration information of the second communication node.

[0071] The configuration information of the changed second communication node includes at least one of the following: the identifier of the changed second communication node, the location information of the changed second communication node (such as a TAI list), and the network slice information supported by the location information of the changed second communication node (such as S-NSSAI).

[0072] In one embodiment, the first communication node may also provide two communication implementation methods:

[0073] Method 1: The first communication node receives a first identifier sent by the second communication node. The first identifier is used to uniquely identify the terminal device on the application layer interface within the second communication node. The second identifier is allocated. The second identifier is used to uniquely identify the terminal device on the application layer interface within the first communication node. The first identifier and the second identifier are sent to the fourth communication node.

[0074] In Method 1, the first communication node does not store the mapping relationship between the connection between the first communication node and the second communication node, or between the connection between the first communication node and the fourth communication node. The first communication node identifies the NGAP connection between the second communication node and the fourth communication node by sending a first identifier and a second identifier to the fourth communication node.

[0075] Method 2: The first communication node establishes a mapping relationship between the first communication node and the second communication node, as well as between the first communication node and the fourth communication node. The connection between the first communication node and the second communication node is identified by a first identifier and a second identifier. The first identifier is used to uniquely identify the terminal device on the application layer interface within the second communication node, and the second identifier is used to uniquely identify the terminal device on the application layer interface within the first communication node; the mapping relationship is stored.

[0076] In Method 2, the first communication node stores the mapping relationship between the connection between the first communication node and the second communication node, as well as the connection between the first communication node and the fourth communication node. In this case, the service address sent by the first communication node to the fourth communication node can uniquely identify the NGAP connection between the second communication node and the fourth communication node.

[0077] Figure 6 is a flowchart illustrating a method for receiving configuration information according to an embodiment. As shown in Figure 6, the method provided in this embodiment is applicable to a fourth communication node, which may also be referred to as a fourth communication node device, a fourth node, a fourth device, or a fourth communication entity. For example, in this embodiment, the first communication node may be a CMF, the second communication node may be a RAN, the third communication node may be an NRF, and the fourth communication node may be an AMF. The method includes the following steps.

[0078] S610. Receive second configuration information sent by the first communication node. The second configuration information is the configuration information of the second communication node that has established an application layer connection with the first communication node.

[0079] In one embodiment, the second configuration information may be carried in a message such as a second update request message or a second update signaling, so that the fourth communication node updates the configuration information of the second communication node.

[0080] The configuration information of the second communication node includes at least one of the following: the second communication node identifier, the location information of the second communication node (such as the TAI list), and the network slice information supported by the location information of the second communication node (such as S-NSSAI).

[0081] In one embodiment, before step S610 is executed, the fourth communication node may also send a third request message to the third communication node. The third request message is used to request at least one of registration, deletion, and update; the fourth communication node receives a first feedback message sent by the third communication node. The first feedback message is used to indicate whether the request for at least one of registration, deletion, and update was successful.

[0082] The third request message includes at least one of the following: a fourth communication node identifier used to identify the identity of the fourth communication node; location information managed by the fourth communication node (such as a TAI list); and network slice information supported by the fourth communication node (such as S-NSSAI).

[0083] In one embodiment, the fourth communication node can implicitly subscribe to the changes of the second communication node from the first communication node. When the first communication node determines that the subscription conditions are met (e.g., the second communication node has changed (e.g., newly registered, deleted, updated)), the first communication node can send a third notification message to the fourth communication node, enabling the fourth communication node to receive the third notification message sent by the first communication node. The third notification message includes fourth configuration information, which is the configuration information of the changed second communication node, so that the fourth communication node can update the configuration information of the second communication node.

[0084] The configuration information of the changed second communication node includes at least one of the following: the identifier of the changed second communication node, the location information of the changed second communication node (such as a TAI list), and the network slice information supported by the location information of the changed second communication node (such as S-NSSAI).

[0085] In one embodiment, the fourth communication node may further receive a first identifier and a second identifier sent by the first communication node. The first identifier is used to uniquely identify the terminal device on the application layer interface within the second communication node, and the second identifier is used to uniquely identify the terminal device on the application layer interface within the first communication node. The fourth communication node identifies the NGAP connection between the second and fourth communication nodes by receiving the first and second identifiers sent by the first communication node.

[0086] In one embodiment, after receiving the first identifier and the second identifier, the fourth communication node can send a message targeting a terminal device to the first communication node. The message targeting a terminal device carries the first identifier and the second identifier.

[0087] Below are some examples illustrating the method provided in this application. In the examples below, the first communication node is CMF, the second communication node is RAN, the third communication node is NRF, and the fourth communication node is AMF. CMF can perform routing functions between RAN and AMF. When AMF changes, there is no need to update the RAN configuration; when RAN changes, there is no need to update the AMF configuration.

[0088] Example 1: Establish QUIC and NGAP connections between AMF and CMF.

[0089] Figure 7 is a flowchart of the configuration information interaction provided in Example 1. As shown in Figure 7, it includes the following steps.

[0090] S700, CMF and RAN establish QUIC connection.

[0091] A QUIC connection can be established between CMF and RAN according to the configuration. For example: a) RAN (as a client) and CMF (as a server) transmit data packets via UDP and perform an encrypted handshake using TLS 1.3; b) RAN generates the private and public keys required for key exchange and calculates the initial encryption key; c) RAN, as a client, sends the initial data packet, CMF responds and completes the key exchange; d) CMF and RAN transmit data through the encrypted QUIC connection.

[0092] S701 and RAN send NGAP NG Setup Request messages to CMF via QUIC connection.

[0093] In one embodiment, the NG Setup Request message may carry at least one of the following: the RAN identifier, the RAN location information (such as the RAN's TAI list), and the network slice information supported by the RAN location information (such as the S-NSSAI supported by each TAI in the RAN's TAI list).

[0094] S702 and CMF receive NG Setup Request messages.

[0095] After receiving an NG Setup Request message, CMF can store the information carried in the NG Setup Request message locally.

[0096] S703 and CMF send NG Setup Response messages to RAN.

[0097] In one embodiment, the NG Setup Response message may carry AMF configuration information stored locally by the CMF, including at least one of the following: the AMF identifier (such as a globally unique AMF identifier (GUAMI)), the location information managed by the AMF (such as a list of TAIs managed by the AMF), and the network slice information supported by the AMF (such as the S-NSSAI supported by each TAI in the list of TAIs managed by the AMF).

[0098] If the CMF does not store any AMF configuration information locally, the NG Setup Response message may not include the AMF configuration information.

[0099] S704, RAN receives NG Setup Response message.

[0100] S705 and CMF send a subscription request message to NRF.

[0101] The subscription request message may carry at least one of the following: the CMF identifier, or the RAN location information (such as the RAN's TAI list). The subscription request message requests that the NRF notify the CMF when a certain AMF changes (e.g., registers or deregisters). The conditions for this might be that the AMF's registration configuration information includes the corresponding CMF identifier, or that the TAI included in the AMF's configuration information matches the RAN's TAI, etc.

[0102] The subscription request message can also include the CMF's address information, which is used by the NRF to send a subscription notification message to that address.

[0103] S706 and NRF receive subscription request messages.

[0104] Optionally, after receiving a subscription request message, the NRF can return a subscription response message to the CMF.

[0105] S707 and AMF send NF change request messages to NRF.

[0106] When an AMF undergoes changes (such as a new AMF starting up, an AMF going offline, or an AMF update), the AMF sends an NF Change Request message to the NRF. The NF Change Request message can be a registration request, a deregistration request, an update request, etc. The NF Change Request message carries the AMF's configuration information.

[0107] The configuration information of AMF may include at least one of the following: the AMF identifier (such as GUAMI), the location information managed by the AMF (such as the list of TAIs managed by the AMF), and the network slice information supported by the AMF (such as the S-NSSAI supported by each TAI in the list of TAIs managed by the AMF).

[0108] S708 and NRF receive NF change request messages and send NF change notification messages to AMF.

[0109] S709 and AMF receive NF change notification messages.

[0110] S710. When the NRF determines that the conditions for sending a notification to the CMF are met, the NRF sends a subscription notification message to the CMF.

[0111] The subscription notification message carries AMF configuration information, which may include at least one of the following: AMF identifier (such as GUAMI), AMF-managed location information (such as the AMF-managed TAI list), and AMF-supported network slice information (such as the S-NSSAI supported by each TAI in the AMF-managed TAI list).

[0112] S711 and CMF receive subscription notification messages and send configuration update request messages to RAN and NG Setup Request messages to AMF.

[0113] After receiving the subscription notification message, the CMF can select a RAN that also supports the TAI based on the TAI information supported by the AMF, and send a configuration update request message to the RAN, thus initiating a configuration update. The configuration update request message carries the AMF's configuration information.

[0114] Similarly, CMF can also send NG Setup Request messages to AMF. The NG Setup Request message carries the RAN identifier, the RAN location information (such as the RAN's TAI list), and the network slice information supported by the RAN location information (such as the S-NSSAI supported by each TAI in the RAN's TAI list).

[0115] S712, RAN receives configuration update request message and sends configuration update notification message to CMF.

[0116] S713, AMF receives the NG Setup Request message and sends the NG Setup Response message to CMF.

[0117] This enables the exchange of configuration information between the AMF and the RAN. Specifically, the RAN can access the configuration information of the AMFs that the CMF can connect to; conversely, the AMF can access the configuration information of the RANs that the CMF can connect to. Changes to either the AMF or the RAN will not affect other nodes, thus improving system performance.

[0118] S714, CMF sends a subscription notification message to AMF.

[0119] In one embodiment, the AMF can implicitly subscribe to RAN changes from the CMF. When a RAN changes (such as registration, deletion, or update), the CMF can send a subscription notification message to the AMF, informing the AMF of the changed RAN configuration information.

[0120] S715 and AMF receive subscription notification messages.

[0121] Similarly, when an AMF is deleted, it needs to deregister with the NRF. The NRF determines whether it needs to notify the CMF. If a notification is needed, the NRF informs the CMF that the AMF has been deleted, and the CMF then notifies the RAN to delete the corresponding AMF configuration information.

[0122] Example 2: The process of connecting AMF and RAN via CMF.

[0123] Figure 8 is an interaction flowchart of an access message provided in Example 2. As shown in Figure 8, it includes the following steps.

[0124] S801, RAN select CMF.

[0125] After receiving the initial access message from the UE, the RAN establishes a user context. Then, the RAN selects a CMF (User Context). The specific selection of the CMF can follow these rules:

[0126] If the UE carries a temporary user identifier, such as a globally unique temporary identifier (GUTI), which contains the identifier of the AMF that assigned that user identifier (such as GUAMI), then the RAN directly selects that AMF. This is because the RAN already knows which CMF can be used to connect to that AMF in Example 1 above, so the RAN selects that CMF and QUIC to connect.

[0127] If the UE does not provide a GUTI, the RAN selects a default CMF and QUIC connection, with the default CMF configured on the RAN.

[0128] Optionally, the RAN can also select an AMF that supports the user's current TAI and then send the GUAMI of that AMF to the CMF.

[0129] S802, the RAN assigns a local RAN UE NGAP ID and sends an NGAP message (initial UE message) to the CMF.

[0130] The NGAP message (initial UE message) carries the RAN UE NGAP ID assigned by the RAN and the Tracking Area Identifier (TAI) of the user's currently registered cell, which is configured on the RAN.

[0131] The NGAP message (Initial UE Message) also includes the NAS message received from the UE.

[0132] S803 and CMF receive NGAP messages (initial UE messages).

[0133] S804, CMF should be AMF.

[0134] If the CMF receives a GUAMI from the RAN, it selects the AMF corresponding to the GUAMI; otherwise, it selects an AMF that supports the user's current access location information (TAI) based on the TAI.

[0135] In one embodiment, the CMF also assigns a CMF UE NGAP ID, which is unique within the QUIC connection.

[0136] S805, CMF sends NGAP message (Initial UE message) to AMF.

[0137] This means that the CMF forwards the NGAP message (Initial UE Message). This NGAP message carries the user's location information (TAI). It also includes the NAS message received from the UE.

[0138] Optionally, the message may also include the CMF's service address (SBI address). When the AMF needs to communicate with the UE / RAN subsequently, the target address is set to this CMF's service address. There are two implementation methods for CMF:

[0139] Method 1: The CMF stores the mapping relationship between the NGAP connection to the RAN (identified by a pair of CMF UE NGAP IDs and RAN UE NGAP IDs) and the SBI connection to the AMF (identified by the SBI address). In this case, the service address sent by the CMF to the AMF can uniquely identify the NGAP connection between the CMF and the RAN.

[0140] Method 2: The CMF does not store the mapping relationship between the NGAP connection to the RAN (identified by a pair of CMF UE NGAP IDs and RAN UE NGAP IDs) and the SBI connection to the AMF (identified by the SBI address). In this case, the CMF needs to send the RANUE NGAP ID received from the RAN and the CMF UE NGAP ID allocated by the CMF in step S804 to the AMF.

[0141] S806 and AMF receive NGAP messages (initial UE messages).

[0142] S807, AMF sends downlink messages to CMF.

[0143] Since CMF has two implementation methods, there are two different processing methods in step S807:

[0144] For Method 1: The downlink message includes the CMF's service address received from S805. After receiving the CMF, the corresponding NGAP connection can be found based on the CMF's service address (identified by a pair of CMF UE NGAP ID and RAN UE NGAPID).

[0145] For method two: The downlink message includes the CMF UE NGAP ID and the RAN UE NGAP ID. The CMF directly uses these two identifiers in the NGAP message sent to the RAN.

[0146] S808 and CMF receive downlink messages and send NGAP messages to RAN.

[0147] The destination address in this message is the RAN UE NGAP ID determined in step S807, and the source address is the CMF UE NGAPID. This allows the RAN to find the user's context based on the RAN UE NGAP ID.

[0148] The above example establishes a mapping relationship between the RAN-to-CMF NGAP connection (identified by a pair of NGAP AMF UE IDs and NGAP RANUE IDs) and the CMF-to-AMF SBI connection. The CMF may or may not store this mapping relationship locally.

[0149] Figure 9 is a schematic diagram of a configuration information sending device provided in an embodiment. The device can be configured in a first communication node. As shown in Figure 9, the device includes a first sending module 901 and a first receiving module 902.

[0150] The first sending module 901 is configured to send a first request message to the third communication node after establishing an application layer connection with the second communication node. The first request message is used to request to subscribe to the configuration information of the fourth communication node.

[0151] The first receiving module 902 is configured to receive a first notification message sent by the third communication node. The first notification message includes first configuration information, which is the configuration information of the fourth communication node.

[0152] The first sending module 901 is further configured to send first configuration information to the second communication node and second configuration information to the fourth communication node, wherein the second configuration information is the configuration information of the second communication node.

[0153] The configuration information sending device provided in this embodiment is to implement the configuration information sending method of the embodiment shown in FIG5. The implementation principle and technical effect of the configuration information sending device provided in this embodiment are similar to those of the above embodiments, and will not be repeated here.

[0154] In one embodiment, the first receiving module 902 is further configured to receive a second request message sent by the second communication node through the QUIC connection after establishing a Fast User Datagram Protocol (QUIC) network connection with the second communication node. The second request message includes at least one of the following: a second communication node identifier, location information of the second communication node, and network slice information supported by the location information of the second communication node.

[0155] The first sending module 901 is also configured to send a second notification message to the second communication node.

[0156] In one embodiment, the second notification message includes third configuration information, which is the configuration information of the fourth communication node stored locally by the first communication node.

[0157] In one embodiment, the first request message includes at least one of the following: a first communication node identifier and location information of a second communication node.

[0158] In one embodiment, the configuration information of the fourth communication node includes at least one of the following: fourth communication node identifier, location information managed by the fourth communication node, and network slice information supported by the fourth communication node.

[0159] In one embodiment, the location information of the second communication node is matched with the location information managed by the fourth communication node.

[0160] In one embodiment, the first sending module 901 is further configured to send a third notification message to the fourth communication node. The third notification message includes fourth configuration information, which is the configuration information of the second communication node that has been changed.

[0161] In one embodiment, the configuration information of the second communication node includes at least one of the following: a second communication node identifier, the location information of the second communication node, and network slice information supported by the location information of the second communication node.

[0162] In one embodiment, referring to FIG9, FIG10 is a schematic diagram of the structure of another configuration information sending device provided in an embodiment. As shown in FIG10, it further includes a processing module 903.

[0163] The first receiving module 902 is also configured to receive a first identifier sent by the second communication node. The first identifier is used to uniquely identify the terminal device on the application layer interface within the second communication node.

[0164] Processing module 903 is configured to allocate a second identifier, which is used to uniquely identify the terminal device on the application layer interface within the first communication node;

[0165] The first sending module 901 is also configured to send the first identifier and the second identifier to the fourth communication node.

[0166] In one embodiment, referring to FIG10, FIG11 is a schematic diagram of the structure of another configuration information sending device provided in an embodiment. As shown in FIG11, it further includes a storage module 904.

[0167] The processing module 903 is also configured to establish a mapping relationship between the connection between the first communication node and the second communication node, and between the connection between the first communication node and the fourth communication node. The connection between the first communication node and the second communication node is identified by a first identifier and a second identifier. The first identifier is used to uniquely identify the terminal device on the application layer interface within the second communication node, and the second identifier is used to uniquely identify the terminal device on the application layer interface within the first communication node.

[0168] Storage module 904 is configured with a storage mapping relationship.

[0169] Figure 12 is a schematic diagram of a configuration information receiving device provided in an embodiment. The device can be configured in a fourth communication node. As shown in Figure 12, the device includes: a second receiving module 1201.

[0170] The second receiving module 1201 is configured to receive second configuration information sent by the first communication node. The second configuration information is the configuration information of the second communication node that has established an application layer connection with the first communication node.

[0171] The configuration information receiving device provided in this embodiment is to implement the configuration information receiving method of the embodiment shown in FIG6. The implementation principle and technical effect of the configuration information receiving device provided in this embodiment are similar to those of the above embodiments, and will not be repeated here.

[0172] In one embodiment, referring to FIG12, FIG13 is a schematic diagram of the structure of another configuration information receiving device provided in an embodiment. As shown in FIG13, it further includes: a second transmitting module 1202.

[0173] The second sending module 1202 is configured to send a third request message to the third communication node. The third request message includes at least one of the following: the identifier of the fourth communication node, the location information managed by the fourth communication node, and the network slice information supported by the fourth communication node.

[0174] The second receiving module 1201 is also configured to receive the first feedback message sent by the third communication node.

[0175] In one embodiment, the second receiving module 1201 is further configured to receive a third notification message sent by the first communication node. The third notification message includes fourth configuration information, which is the configuration information of the second communication node that has been changed.

[0176] In one embodiment, the configuration information of the second communication node includes at least one of the following: a second communication node identifier, the location information of the second communication node, and network slice information supported by the location information of the second communication node.

[0177] In one embodiment, the second receiving module 1201 is further configured to receive a first identifier and a second identifier sent by the first communication node. The first identifier is used to uniquely identify the terminal device on the application layer interface within the second communication node, and the second identifier is used to uniquely identify the terminal device on the application layer interface within the first communication node.

[0178] In one embodiment, the second sending module 1202 is further configured to send a message whose target is a terminal device to the first communication node, wherein the message whose target is a terminal device carries a first identifier and a second identifier.

[0179] This application also provides a communication node, including a processor, which is configured to implement the method provided in any embodiment of this application when executing a computer program. The communication node in this embodiment can be a first communication node or a fourth communication node.

[0180] Figure 14 is a schematic diagram of a communication node according to an embodiment. As shown in Figure 14, the communication node includes a processor 60, a memory 61, and a communication interface 62. The number of processors 60 in the communication node can be one or more; Figure 14 shows one processor 60 as an example. The processor 60, memory 61, and communication interface 62 in the communication node can be connected via a bus or other means; Figure 14 shows a connection via a bus as an example. The bus represents one or more types of bus structures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of the various bus structures.

[0181] The memory 61, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs, and modules, such as the program instructions / modules corresponding to the methods in the embodiments of this application. The processor 60 executes at least one functional application and data processing of the communication node by running the software programs, instructions, and modules stored in the memory 61, thereby implementing the methods described above.

[0182] Memory 61 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on terminal usage. Furthermore, memory 61 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, memory 61 may include memory remotely located relative to processor 60, which can be connected to a communication node via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, networks, mobile communication networks, and combinations thereof.

[0183] Communication interface 62 can be configured to receive and send data.

[0184] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the methods provided in any embodiment of this application.

[0185] The computer storage medium in this application embodiment can be any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. For example, a computer-readable storage medium can be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. Computer-readable storage media include (a non-exhaustive list): electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), electrically erasable, programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0186] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, the data signals carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0187] Program code contained on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wire, optical fiber, radio frequency (RF), or any suitable combination thereof.

[0188] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination of programming languages, including object-oriented programming languages ​​(such as Java, Smalltalk, C++, Ruby, and Go) and conventional procedural programming languages ​​(such as the "C" language or similar programming languages). The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network (including a Local Area Network (LAN) or a Wide Area Network (WAN)), or it can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0189] This invention also provides a computer program product, including a computer program that, when executed by a processor, implements the method provided in any embodiment of this invention.

[0190] In implementing the computer program product, computer program code for performing the operations of this invention can be written in one or more programming languages ​​or a combination thereof. Programming languages ​​include object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0191] Those skilled in the art will understand that the term user terminal encompasses any suitable type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers, or vehicle-mounted mobile stations.

[0192] Generally, the various embodiments of this application can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although this application is not limited thereto.

[0193] Embodiments of this application can be implemented by executing computer program instructions through the data processor of a mobile device, for example, in a processor entity, or through hardware, or through a combination of software and hardware. The computer program instructions can be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages.

[0194] Any block diagram of logical flow in the accompanying drawings of this 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 may be stored in memory. The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-only memory (ROM), random access memory (RAM), optical storage devices and systems (Digital Multifunction Discs, DVDs, or CDs), etc. Computer-readable media may include non-transitory storage media. The data processor may be of any type suitable to the local technical environment, such as, but not limited to, general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and processors based on multi-core processor architectures.

Claims

1. A method for sending configuration information, characterized in that, The method, applied to a first communication node, includes: after establishing an application layer connection with a second communication node, sending a first request message to a third communication node, the first request message being used to request subscription to configuration information of a fourth communication node; receiving a first notification message sent by the third communication node, the first notification message including first configuration information, the first configuration information being the configuration information of the fourth communication node; sending the first configuration information to the second communication node; and sending second configuration information to the fourth communication node, the second configuration information being the configuration information of the second communication node.

2. The method according to claim 1, characterized in that, A method for establishing an application layer connection with a second communication node includes: after establishing a Fast User Datagram Protocol (QUIC) network connection with the second communication node, receiving a second request message sent by the second communication node through the QUIC connection, the second request message including at least one of the following: a second communication node identifier, location information of the second communication node, and network slice information supported by the location information of the second communication node; and sending a second notification message to the second communication node.

3. The method according to claim 2, characterized in that, The second notification message includes third configuration information, which is the configuration information of the fourth communication node stored locally by the first communication node.

4. The method according to claim 1, characterized in that, The first request message includes at least one of the following: the identifier of the first communication node, and the location information of the second communication node.

5. The method according to claim 4, characterized in that, The configuration information of the fourth communication node includes at least one of the following: the fourth communication node identifier, the location information managed by the fourth communication node, and the network slice information supported by the fourth communication node.

6. The method according to claim 5, characterized in that, The location information of the second communication node matches the location information managed by the fourth communication node.

7. The method according to claim 1, characterized in that, Also includes: A third notification message is sent to the fourth communication node. The third notification message includes fourth configuration information, which is the configuration information of the second communication node that has been changed.

8. The method according to claim 1, characterized in that, The configuration information of the second communication node includes at least one of the following: the second communication node identifier, the location information of the second communication node, and the network slice information supported by the location information of the second communication node.

9. The method according to claim 1, characterized in that, Also includes: Receive a first identifier sent by the second communication node, the first identifier being used to uniquely identify the terminal device on the application layer interface within the second communication node; Assign a second identifier, which is used to uniquely identify the terminal device on the application layer interface within the first communication node; send the first identifier and the second identifier to the fourth communication node.

10. The method according to claim 1, characterized in that, It also includes: establishing a mapping relationship between the connection between the first communication node and the second communication node, and the connection between the first communication node and the fourth communication node, wherein the connection between the first communication node and the second communication node is identified by a first identifier and a second identifier, wherein the first identifier is used to uniquely identify the terminal device on the application layer interface within the second communication node, and the second identifier is used to uniquely identify the terminal device on the application layer interface within the first communication node; and storing the mapping relationship.

11. A method for receiving configuration information, characterized in that, The method is applied to a fourth communication node and includes: receiving second configuration information sent by a first communication node, wherein the second configuration information is configuration information of a second communication node that has established an application layer connection with the first communication node.

12. The method according to claim 11, characterized in that, Also includes: Send a third request message to a third communication node, the third request message including at least one of the following: a fourth communication node identifier, location information managed by the fourth communication node, and network slice information supported by the fourth communication node; receive a first feedback message sent by the third communication node.

13. The method according to claim 11, characterized in that, Also includes: The system receives a third notification message sent by the first communication node. The third notification message includes fourth configuration information, which is the configuration information of the second communication node that has undergone changes.

14. The method according to claim 11, characterized in that, The configuration information of the second communication node includes at least one of the following: the second communication node identifier, the location information of the second communication node, and the network slice information supported by the location information of the second communication node.

15. The method according to claim 11, characterized in that, Also includes: The system receives a first identifier and a second identifier sent by the first communication node. The first identifier is used to uniquely identify the terminal device on the application layer interface within the second communication node, and the second identifier is used to uniquely identify the terminal device on the application layer interface within the first communication node.

16. The method according to claim 15, characterized in that, Also includes: A message targeting a terminal device is sent to the first communication node, the message targeting a terminal device carrying the first identifier and the second identifier.

17. A communication node, characterized in that, include: processor; The processor is configured to implement the method as described in any one of claims 1-16 when executing a computer program.

18. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-16.

Images