Message interaction method and apparatus, communication device, storage medium, and product

Abstract

This application relates to a message interaction method, apparatus, communication device, storage medium, and product, applied to a signaling interconnection gateway. The method includes: receiving a session request message sent by a core network control plane element; converting the format of the session request message to generate a target session request message; the target session request message is compatible with multiple types of core network user plane elements. The target session request message is then sent to a target core network user plane element, which includes multiple types of core network user plane elements. When the target core network user plane element includes multiple types of core network user plane elements, by converting the format of the session request message, the incompatibility of the session request message with older and newer core network user plane elements can be avoided during message interaction between the core network control plane element and the core network user plane element.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a message interaction method, apparatus, communication device, storage medium, and product. Background Technology

[0002] With the rapid development of communication technology, private network services have also developed rapidly. Major operators have begun to actively promote private network services using more advanced mobile communication technologies, such as 5G private network services or 6G private network services, within enterprise parks.

[0003] Specifically, a common approach is to share core network control plane elements between the enterprise campus private network and the public network. This involves deploying core network user plane elements within the enterprise campus to provide private network services. However, some enterprise campuses already have core network user plane elements based on 4G private network services deployed, and the equipment corresponding to these 4G private network elements is still in normal use. Therefore, it is necessary to deploy more advanced mobile communication technology-based private network services within these enterprise campuses while retaining the equipment corresponding to these older core network user plane elements. However, in this case, incompatibility issues arise when message exchanges occur between the core network control plane elements and the core network user plane elements. Summary of the Invention

[0004] This application provides a message interaction method, apparatus, communication device, and computer-readable storage medium, which can be compatible with multiple types of core network user plane network elements when performing message interaction between core network control plane network elements and core network user plane network elements.

[0005] On the one hand, a message interaction method is provided, applied to a signaling interconnection gateway, the method comprising:

[0006] Receive session request messages sent by core network control plane network elements;

[0007] The session request message is format-converted to generate a target session request message; the target session request message is adaptable to various types of core network user plane network elements.

[0008] The target session request message is sent to the target core network user plane element; the target core network user plane element includes various types of core network user plane elements.

[0009] On the other hand, a message interaction device is provided, applied to a signaling interconnection gateway, the device comprising:

[0010] The message receiving module is used to receive a session request message sent by the core network control plane network element after the core network control plane network element establishes a PFCP association with the target core network user plane network element through the signaling interconnection gateway; the target core network user plane network element includes various types of core network user plane network elements;

[0011] The message format conversion module is used to convert the format of the session request message and generate a target session request message; the target session request message is adapted to the various types of core network user plane network elements.

[0012] The message sending module is used to send the target session request message to the target core network user plane network element.

[0013] On the other hand, a communication device is provided, including a transmitter, a processor, and a receiver;

[0014] The transmitter is used to receive session request messages sent by the core network control plane network element;

[0015] The processor is used to convert the format of the session request message and generate a target session request message; the target session request message is adapted to various types of core network user plane network elements.

[0016] The receiver is used to send the target session request message to the target core network user plane element; the target core network user plane element includes various types of core network user plane elements.

[0017] On the other hand, a communication device is provided, including a memory and a processor, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor performs the steps of the message interaction method described above.

[0018] On the other hand, a computer-readable storage medium is provided that stores a computer program thereon, which, when executed by a processor, implements the steps of the message interaction method described above.

[0019] On the other hand, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps of the message interaction method as described above.

[0020] The aforementioned message interaction methods, devices, communication equipment, storage media, and products, for scenarios where core network user plane elements in private network services are converged, involve a signaling interconnection gateway receiving session request messages sent by core network control plane elements, converting the session request messages into a format that generates target session request messages adapted to various types of core network user plane elements. These target session request messages are then sent to target core network user plane elements. Therefore, even when the target core network user plane elements include multiple types, the target session request messages can still be adapted to those elements.

[0021] Therefore, by converting the format of the session request message, the situation where the session request message is incompatible with the old core network user plane network element and the new core network user plane network element can be avoided when the message is exchanged between the core network control plane network element and the core network user plane network element. Attached Figure Description

[0022] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0023] Figure 1 This is an application environment diagram of the message interaction method in one embodiment;

[0024] Figure 2 Here is a flowchart of a message interaction method in one embodiment;

[0025] Figure 3 for Figure 2 The flowchart shows how to convert the format of the session request message and generate the target session request message method.

[0026] Figure 4 This is a schematic diagram of the architecture of a message interaction system in one embodiment;

[0027] Figure 5 for Figure 3 The process involves format conversion of the session request message based on the target interface type, generating a flowchart of the target session request message method.

[0028] Figure 6 for Figure 3 The process involves format conversion of the session request message based on the target interface type, generating a flowchart of the target session request message method.

[0029] Figure 7 Here is a flowchart of a message interaction method in another embodiment;

[0030] Figure 8 This is a schematic diagram of a message interaction method in an exemplary embodiment;

[0031] Figure 9 The following is a signaling diagram illustrating the process of establishing a PFCP association between the Session Management Element (SMF) and the User Plane Element (UPF) of the core network through a signaling interconnection gateway, and the interaction of session request messages in one embodiment.

[0032] Figure 10 This is a structural block diagram of a message interaction device in one embodiment;

[0033] Figure 11 This is a structural block diagram of the message interaction device in another embodiment;

[0034] Figure 12 This is a schematic diagram of the internal structure of a communication device in one embodiment. Detailed Implementation

[0035] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0036] With the rapid development of communication technology, private network services have also developed rapidly. Major operators have begun to actively promote private network services using more advanced mobile communication technologies, such as 5G private network services or 6G private network services, within enterprise parks.

[0037] Specifically, a common approach is to share core network control plane elements between the enterprise campus private network and the public network. This involves deploying core network user plane elements within the enterprise campus to provide private network services. However, some enterprise campuses already have core network user plane elements based on 4G private network services deployed, and the equipment corresponding to these 4G private network elements is still in normal use. Therefore, it is necessary to deploy more advanced mobile communication technology-based private network services within these enterprise campuses while retaining the equipment corresponding to these older core network user plane elements. However, in this case, incompatibility issues arise when message exchanges occur between the core network control plane elements and the core network user plane elements.

[0038] Figure 1 This is a schematic diagram illustrating the application environment of a message interaction method in one embodiment. For example... Figure 1As shown, the application environment includes a message interaction system, which comprises a core network control plane element 120, a signaling interconnection gateway 140, and a core network user plane element 160. The core network control plane element 120 can communicate with the core network user plane element 160 through the signaling interconnection gateway 140. The core network control plane element 120 and the core network user plane element 160 can transmit session request messages, and the target interface type of the session request message includes at least one of the following: Sxa interface type, Sxb interface type, and N4 interface type. The core network user plane element 160 can receive or forward messages through the S1-U / N3 interface and the SGi / N6 interface. The signaling interconnection gateway 140 receives session request messages sent by core network control plane elements; it converts the format of the session request messages to generate target session request messages; the target session request messages are adapted to various types of core network user plane elements; and it sends the target session request messages to the target core network user plane elements; the target core network user plane elements include various types of core network user plane elements. The signaling interconnection gateway 140 is deployed between the enterprise private network and the carrier network, enabling signaling messages between the enterprise private network and the carrier network to be forwarded through this gateway, thereby achieving network isolation and topology hiding between the enterprise private network and the carrier network. A gateway device, also known as a network connector or protocol converter, is a computer system or device that provides data conversion services between multiple networks. In short, a gateway device is a connector between different networks.

[0039] Figure 2 This is a flowchart of a message interaction method in one embodiment. The message interaction method in this embodiment is designed to run on... Figure 1 The following description will be based on the signaling interconnection gateway 140 in the example. Figure 2 As shown, the message interaction method includes steps 220 to 260, wherein,

[0040] Step 220: Receive a session request message sent by the core network control plane element.

[0041] Traditional methods deploy private network services by sharing core network control plane elements between the enterprise campus private network and the public network. This necessitates communication and coordination between the private and public networks, introducing insecurity risks. To address these insecurity issues, a signaling interoperability gateway is introduced between the private and public networks. This gateway enables message exchange between the private and public networks while simultaneously isolating messages between them, thus resolving the security concerns associated with such communication.

[0042] However, in scenarios where core network user plane elements for private network services are converged, incompatibility arises when message exchanges occur between core network control plane elements and core network user plane elements. The converged scenario refers to the convergence of core network user plane elements based on multiple communication technologies, including the convergence of core network user plane elements for 4G private network services with those for 5G private network services; or the convergence of core network user plane elements for 4G private network services with those for 6G private network services; or the convergence of core network user plane elements for 5G private network services with those for 6G private network services; or the convergence of core network user plane elements for 4G private network services with those for both 5G and 6G private network services, etc. This application does not limit the scope of the convergence scenario.

[0043] To address the incompatibility issues between older and newer core network user plane network elements during message exchange, the following steps are taken: First, after establishing a PFCP (Packet Forwarding Control Protocol) association between the core network control plane element and the target core network user plane element via a signaling interconnection gateway, the core network control plane element sends a session request message to the signaling interconnection gateway. This session request message is based on the PFCP protocol in the 3GPP standard. However, because the definition of PFCP-based messages in the 3GPP standard is flexible, the message format (or message structure) of each session request message varies. For example, some message formats of session request messages are compatible with core network user plane network elements based on earlier mobile communication technologies but not with those based on more advanced mobile communication technologies. For instance, some message formats of session request messages are compatible with core network user plane network elements for 4G private network services but not for 5G private network services. Some message formats of session request messages may be adapted to the core network user plane elements of 5G private network services, but not to the core network user plane elements of 6G private network services. Alternatively, some message formats of session request messages may be adapted to the core network user plane elements of 4G private network services, but not to the core network user plane elements of 5G / 6G private network services. This application does not impose any limitations on this.

[0044] However, since more advanced mobile communication technologies are being deployed in private network services within these enterprise parks while retaining the equipment corresponding to these older core network user plane elements, the message interaction system now includes a variety of core network user plane elements, resulting in a scenario where core network user plane elements for private network services are converged. After the core network control plane element sends a session request message to the signaling interconnection gateway, the signaling interconnection gateway forwards the session request message to the corresponding target core network user plane element in the converged scenario.

[0045] The core network control plane elements include Session Management Functions (SMFs), which are not limited in this application. SMFs are the basic units in the 5G Service-Based Architecture (SBA). SMFs are primarily responsible for interacting with the decoupled data plane, creating, updating, and deleting Protocol Data Unit (PDU) sessions, and managing session contexts with User Plane Functions (UPFs). Core network user plane elements include User Plane Functions (UPFs). UPFs are core components of the 5G core network, located between the User Access Layer (U-plane) and the control layer. The main function of the UPF is to provide user plane services, while the control layer is responsible for managing registration, authentication, transaction management, and other functions.

[0046] Step 240: Convert the format of the session request message to generate the target session request message; the target session request message is adapted to various types of core network user plane network elements.

[0047] Since the message format of the session request message sent by the core network control plane element to the signaling interconnection gateway may not be compatible with the target core network user plane element to which the signaling interconnection gateway will forward the message, the signaling interconnection gateway can convert the format of the session request message to generate the target session request message.

[0048] Optionally, these session request messages are all based on the PFCP protocol in the 3GPP standard. Since the definition of PFCP-based messages in the 3GPP standard is quite flexible, generally, for the first type of session request messages adapted to core network user plane elements of more advanced mobile communication technologies, the message format (or message structure) of these first type of session request messages is more complex or more complete. In other words, the message format (or message structure) of the first type of session request messages includes more message content and can adapt to various types of core network user plane elements. For the second type of session request messages adapted to core network user plane elements of earlier mobile communication technologies, the first type of session request messages contains all the message content of the second type of session request messages, and also includes message content not mentioned or appearing in the second type of session request messages.

[0049] Therefore, based on the message format of the first type of session request message, the message format of the session request message sent by the core network control plane element to the signaling interconnection gateway can be converted to generate the target session request message. In this way, the message format of the target session request message is consistent with the message format of the first type of session request message. Since the message format (or message structure) of the first type of session request message includes more message content and can be adapted to various types of core network user plane elements, the target session request message can correspondingly be adapted to various types of core network user plane elements.

[0050] Among them, the core network user plane network elements of various network element types include any two or more of the core network user plane network elements of 4G, the core network user plane network elements of 5G, and the core network user plane network elements of 6G.

[0051] Step 260: Send the target session request message to the target core network user plane element; the target core network user plane element includes various types of core network user plane elements.

[0052] After the signaling interoperability gateway converts the session request message format, it generates a target session request message adapted to various types of core network user plane elements. The signaling interoperability gateway then sends the target session request message to the target core network user plane element. Here, the target core network user plane element includes various types of core network user plane elements. In this way, the target core network user plane element can identify the target session request message and then perform post-processing such as parsing the target session request message, which is not limited in this application. At this time, when message interaction occurs between core network control plane elements and core network user plane elements, the situation of incompatibility between old and new core network user plane elements can be avoided.

[0053] In this embodiment, for scenarios where core network user plane elements of private network services are converged, the signaling interconnection gateway receives session request messages sent by core network control plane elements, then converts the format of the session request messages to generate target session request messages adapted to various types of core network user plane elements. These target session request messages are then sent to target core network user plane elements. Therefore, even when the target core network user plane elements include multiple types, the target session request messages can still be adapted to those elements.

[0054] Therefore, by converting the format of the session request message, the situation where the session request message is incompatible with the old core network user plane network element and the new core network user plane network element can be avoided when the message is exchanged between the core network control plane network element and the core network user plane network element.

[0055] In the previous embodiment, a method was described to convert the format of the session request message so that the target session request message obtained by the format conversion can be adapted to various types of core network user plane network elements. In this embodiment, as... Figure 3 As shown, step 240, which involves format conversion of the session request message to generate the target session request message, includes:

[0056] Step 242: Parse the session request message to obtain the packet detection rules and the forwarding operation rules associated with the packet detection rules.

[0057] After receiving a session request message from a core network control plane element, the signaling interconnection gateway can first parse the session request message to obtain a Packet Detection Rule (PDR) and a Forwarding Action Rule (FAR) associated with the PDR. Here, both the PDR and FAR are data transformation rules. The PDR includes a Packet Detection Instruction (PDI) to guide core network user plane elements (such as UPFs) in downlink data detection, and rules for executing corresponding actions on matched services, such as FARs and QoS Enforcement Rules (QERs). The PDI contains information on multiple matching UPF input packets, i.e., the conditions for filtering packets. Each PDR is associated with one or more FARs. The FAR contains Apply Action parameters and action parameters. The Apply Action parameters indicate whether the UPF should forward, copy, drop, or buffer packets, and whether the UPF should accept or reject a UE's (User Equipment) request to join an IP (Internet Protocol Address) multicast group. Among them, the action parameters are used to instruct the forwarding parameters, replication parameters, or caching parameters when the UPF executes the Apply Action, and this application does not limit them.

[0058] Step 244: Extract the target field from the packet detection rules and forwarding operation rules, and determine the target interface type of the session request message based on the target field; the target interface type includes at least one of the Sxa interface type, Sxb interface type and N4 interface type.

[0059] The packet detection rules and forwarding operation rules include multiple fields, among which the target field is used to characterize the target interface type of the session request message. Therefore, the signaling interoperability gateway can extract the target field from the parsed packet detection rules and forwarding operation rules, and then determine the target interface type of the session request message based on the target field.

[0060] Optionally, the target field extracted from the packet inspection rules and forwarding operation rules can be a field representing traffic forwarding channel information. Because different traffic forwarding channel information is defined in the packet inspection rules and forwarding operation rules for session request messages of different interface types, it can be understood that there is a one-to-one correspondence between the traffic forwarding channel information and session request messages of different interface types. Therefore, based on the traffic forwarding channel information in this target field, the target interface type of the session request message can be accurately determined.

[0061] Combination Figure 4 The diagram shows the architecture of a message interaction system in one embodiment. This system includes a core network control plane element 420, a signaling interconnection gateway 440, and a core network user plane element 460. The core network control plane element 420 can transmit session request messages with the signaling interconnection gateway 440. The interface type of the session request message includes at least one of the following: Sxa, Sxb, and N4 interface types. The signaling interconnection gateway 440 can transmit this session request message with the core network user plane element 460. The core network user plane element 460 can be obtained by fusing multiple user plane elements. For example, it can be obtained by fusing SGW-U+PGW-U and UPF, where SGW-U+PGW-U are logically completely unified; alternatively, it can be obtained by fusing SGW-U+PGW-U and UPF, where SGW-U+PGW-U are logically separate. Among them, UPF is a core component of the 5G core network; SGW-U+PGW-U are core components of the 4G core network. Of course, core network user plane element 460 can also be directly derived from a single type of user plane element. For example, core network user plane element 460 can be directly derived from UPF; core network user plane element 460 can also be directly derived from SGW-U+PGW-U. Here, SGW-U stands for Serving Gateway-User Plane; PGW-U stands for Packet data network Gateway-User Plane.

[0062] For example, in a scenario where core network user plane element 460 is a 5G core network user plane element UPF, the signaling interconnection gateway parses the session request message sent by the core network control plane element and extracts the target field from the parsed packet detection rules and forwarding operation rules. The target field defines that uplink traffic enters the UPF through the N3 interface, and the UPF then forwards the uplink traffic out through the N6 interface. Therefore, based on the N3 and N6 interfaces defined in the target field, it can be determined that the target interface type of the session request message includes the N4 interface type.

[0063] For example, in a scenario where core network user plane element 460 is a convergence of SGW-U+PGW-U and UPF, and SGW-U+PGW-U are logically completely unified, it can be known that the S5 / S8 interface is not included in this convergence scenario. In this case, the signaling interconnection gateway parses the session request message sent by the core network control plane element and extracts the target field from the parsed packet detection rules and forwarding operation rules. The target field defines that uplink traffic first enters the user plane through the S1-U interface, then passes through the user plane, and finally forwards the uplink traffic out through the SGi interface. Therefore, based on the fact that the interfaces defined in the target field do not include the S5 / S8 interface, it can be determined that the target interface type of the session request message includes the Sxb / N4 interface type.

[0064] For example, in a scenario where core network user plane element 460 is a fusion of SGW-U, PGW-U, and UPF, but SGW-U and PGW-U are logically separate, it can be seen that S5 / S8 interfaces also exist in this fusion scenario. In this case, the signaling interconnection gateway parses the session request message sent by the core network control plane element and extracts the target field from the parsed packet detection rules and forwarding operation rules. The target field defines that uplink traffic first enters the UPF through the S1-U interface, then the UPF passes through SGW-U, and then forwards the uplink traffic to PGW-U through the S5 / S8 interface, and finally forwards the uplink traffic out through the SGi interface after passing through PGW-U. Therefore, based on the fact that the interfaces defined in the target field include the S5 / S8 interface, it can be determined that the target interface type of the session request message includes the Sxa interface type.

[0065] Step 246: Convert the format of the session request message according to the target interface type to generate the target session request message.

[0066] When core network user plane elements are in different converged scenarios, the signaling interconnection gateway parses the session request messages sent by core network control plane elements, and then extracts the target field from the parsed packet detection rules and forwarding operation rules. Then, by combining this with the traffic forwarding channel information in the target field, the target interface type of the session request message can be accurately determined.

[0067] Next, it is determined whether the target interface type of the session request message is consistent with the interface type of the standard session request message. The standard session request message refers to a session request message adapted to various types of core network user plane elements; that is, the message format of the standard session request message includes the mandatory content for various types of core network user plane elements to perform subsequent operations. For example, the interface type of the standard session request message includes the Sxb interface type or N4 interface type corresponding to 5G core network user plane elements, which is not limited in this application. Therefore, if the target interface type of the session request message is consistent with the interface type of the standard session request message, it means that the message format of the session request message is consistent with the message format of the standard session request message, and no format conversion is required for the session request message.

[0068] If there is a discrepancy, it indicates that the message format of the session request message is inconsistent with the standard session request message format. In this case, the session request message needs to be converted to the standard session request message format to generate the target session request message. In other words, the target session request message is a universal session request message adapted to various types of core network user plane elements. This ensures that the message format of the target session request message includes the necessary information for various types of core network user plane elements to perform subsequent operations.

[0069] In this embodiment, because different traffic forwarding channel information is defined in the target field of the packet detection rules and forwarding operation rules for session request messages of different interface types, it can be understood that there is a one-to-one correspondence between the traffic forwarding channel information and the session request messages of different interface types. The signaling interconnection gateway then parses the session request message to obtain the packet detection rules and the forwarding operation rules associated with them. The target field is then extracted from the packet detection rules and forwarding operation rules. Based on the traffic forwarding channel information in the target field, the target interface type of the session request message can be accurately determined. Finally, if the target interface type of the session request message is inconsistent with the interface type of the standard session request message, it indicates that the message format of the session request message is inconsistent with the message format of the standard session request message. Therefore, it is necessary to convert the session request message according to the message format of the standard session request message to generate the target session request message. In this way, the target session request message can be adapted to the general session request message of various types of core network user plane network elements, just like the standard session request message.

[0070] Therefore, by converting the format of the session request message, the situation where the session request message is incompatible with the old core network user plane network element and the new core network user plane network element can be avoided when the message is exchanged between the core network control plane network element and the core network user plane network element.

[0071] In the previous embodiment, the process was described whereby the signaling interoperability gateway parses the session request message, then determines the target interface type of the session request message based on the parsed packet detection rules and the target field in the forwarding operation rules associated with the packet detection rules, and then performs format conversion on the session request message according to the target interface type to generate the target session request message. In this embodiment, as... Figure 5 As shown, step 246 is further described, which involves format conversion of the session request message according to the target interface type to generate the target session request message, including:

[0072] Step 246a: Obtain the preset message conversion rule corresponding to the target interface type; the preset message conversion rule is determined based on the message format of the standard session request message;

[0073] After determining the target interface type of the session request message, the signaling interoperability gateway needs to convert the session request message format according to the target interface type to generate the target session request message. First, the signaling interoperability gateway can obtain the preset message conversion rules corresponding to the target interface type. The standard session request message refers to a session request message adapted to various types of core network user plane network elements; that is, the message format of the standard session request message includes the mandatory content for various types of core network user plane network elements to perform subsequent operations. Therefore, for each interface type, the preset message conversion rules corresponding to the session request messages of each interface type can be determined based on the standard session request message, resulting in a preset message conversion rule library. Optionally, for session request messages with a message format inconsistent with the standard session request message, the preset message conversion rules corresponding to that session request message can be determined based on the message format of the standard session request message. For example, the preset message conversion rules corresponding to the session request message of this interface type define the mandatory content that needs to be added to this session request message; this mandatory content is the same as that in the standard session request message. Therefore, after converting the message format of the session request message according to the preset message conversion rules, the generated target session request message contains the required content of the standard session request message. This ensures that the message format of the target session request message is consistent with that of the standard session request message, guaranteeing that the target session request message can be adapted to the general session request messages of various types of core network user plane network elements, just like the standard session request message.

[0074] Assume that the interface type of the standard session request message includes either the Sxb interface type or the N4 interface type corresponding to the user plane network elements of the 5G core network. If the target interface type of the session request message is the Sxa interface type, then the message format of the Sxa interface type session request message is inconsistent with the message format of the standard session request message. Therefore, the preset message conversion rules corresponding to the Sxa interface type can be obtained from the preset message conversion rule base.

[0075] Step 246b: According to the preset message conversion rules, the message format of the session request message is converted to generate the target session request message; the message format of the target session request message is consistent with the message format of the standard session request message.

[0076] After obtaining the preset message conversion rules corresponding to the target interface type, the message format of the session request message can be converted according to these rules to generate the target session request message. Optionally, since the preset message conversion rules for the session request message of this interface type define the required content to be added to the session request message, and this required content is the same as that in the standard session request message, converting the message format of the session request message according to the preset message conversion rules can add the required content to the session request message and generate the target session request message. Thus, the generated target session request message contains the required content of the standard session request message. This ensures that the message format of the target session request message is consistent with that of the standard session request message, guaranteeing that the target session request message can be adapted to the general session request messages of various types of core network user plane network elements, just like the standard session request message.

[0077] In this embodiment, for each interface type, the signaling interoperability gateway can determine the preset message conversion rules corresponding to the session request messages of each interface type based on the standard session request message, thus obtaining a preset message conversion rule library. Then, the signaling interoperability gateway can retrieve the preset message conversion rules corresponding to the target interface type from the preset message conversion rule library. These preset message conversion rules are determined based on the message format of the standard session request message. The preset message conversion rules corresponding to the session request message of this interface type define the mandatory content that needs to be added to the session request message; this mandatory content is the same as that required in the standard session request message.

[0078] Then, according to the preset message conversion rules, the message format of the session request message is converted to generate the target session request message. At this time, the message format of the target session request message is consistent with the message format of the standard session request message, so as to ensure that the target session request message can be adapted to the general session request messages of various types of core network user plane network elements, just like the standard session request message.

[0079] In the previous embodiment, the process of converting the message format of a session request message according to a preset message conversion rule to generate a target session request message was described. In this embodiment, step 246a, obtaining the preset message conversion rule corresponding to the target interface type, includes:

[0080] If the target interface type of the session request message includes the Sxa interface type, then obtain the preset message conversion rule corresponding to the Sxa interface type;

[0081] Step 246b: According to preset message conversion rules, the message format of the session request message is converted to generate the target session request message, including:

[0082] Based on the preset message conversion rules corresponding to the Sxa interface type, fill in the standard fields in the message part of the session request message for the Sxa interface type to generate the target session request message; the standard fields include the required fields in the standard session request message.

[0083] Optionally, if the target interface type of the session request message includes the Sxa interface type, then the Sxa interface type is inconsistent with the interface type (Sxb / N4 interface type) of the standard session request message. This indicates that the message format of the session request message is inconsistent with the message format of the standard session request message. Therefore, it is necessary to convert the format of the session request message according to the message format of the standard session request message to generate the target session request message.

[0084] For example, preset message conversion rules corresponding to the Sxa interface type are obtained from a preset message conversion rule library. For instance, the preset message conversion rules for a session request message of the Sxa interface type define standard content that needs to be added to the session request message of that Sxa interface type. This standard content consists of required fields in the standard session request message. Here, the standard fields added to the session request message of that Sxa interface type include at least one required field in the Create PDR IE of the PFCP SessionEstablishment Request message; this application does not limit this.

[0085] Then, according to the preset message conversion rules corresponding to the Sxa interface type, standard fields are filled into the message portion of the session request message containing the Sxa interface type to generate the target session request message. For example, at least one required field from the Create PDR IE of the PFCP Session Establishment Request message is filled into the message portion of the session request message containing the Sxa interface type. In this way, the target session request message is generated, and the target session request message includes the required fields of the standard session request message.

[0086] In this embodiment, if the target interface type of the session request message includes the Sxa interface type, the signaling interoperability gateway obtains the preset message conversion rule corresponding to the Sxa interface type from the preset message conversion rule base. Then, according to the preset message conversion rule corresponding to the Sxa interface type, standard fields are filled into the message portion of the session request message for the Sxa interface type to generate the target session request message. The standard fields include the required fields in the standard session request message.

[0087] Thus, for session request messages of the Sxa interface type, the required fields of the standard session request message are filled into the Sxa interface type message portion of the session request message according to the preset message conversion rules corresponding to the Sxa interface type, generating the target session request message. That is, the target session request message also contains the required fields of the standard session request message; in other words, the message format of the target session request message is consistent with that of the standard session request message, ensuring that the target session request message can be adapted to the general session request messages of various types of core network user plane network elements, just like the standard session request message.

[0088] In the previous embodiment, the process of filling the required fields of the standard session request message into the Sxa interface type message portion of the session request message to generate the target session request message was described. In this embodiment, as... Figure 6 As shown, the method further describes the format conversion of the session request message according to the target interface type to generate the target session request message, including:

[0089] Step 620: Obtain the preset message conversion rules and operator preset rules corresponding to the target interface type;

[0090] Step 640: Modify the content of the session request message according to the preset message conversion rules and the operator's preset rules to generate a new target session request message.

[0091] Optionally, after determining the target interface type of the session request message, the signaling interoperability gateway needs to perform format conversion on the session request message according to the target interface type to generate the target session request message. First, the signaling interoperability gateway can obtain the preset message conversion rules corresponding to the target interface type. Here, the standard session request message refers to a session request message adapted to various types of core network user plane network elements; that is, the message format of the standard session request message includes the mandatory content for various types of core network user plane network elements to perform subsequent operations. Therefore, for each interface type, the preset message conversion rules corresponding to the session request messages of each interface type can be determined based on the standard session request message, resulting in a preset message conversion rule library. Optionally, for session request messages whose message format is inconsistent with the standard session request message, the preset message conversion rules corresponding to that session request message can be determined based on the message format of the standard session request message. For example, the preset message conversion rules corresponding to the session request message of this interface type define the mandatory content that needs to be added to the session request message; this mandatory content is the mandatory content in the standard session request message. Therefore, after converting the message format of the session request message according to the preset message conversion rules, the generated target session request message contains the required content of the standard session request message. This ensures that the message format of the target session request message is consistent with that of the standard session request message, guaranteeing that the target session request message can be adapted to the general session request messages of various types of core network user plane network elements, just like the standard session request message.

[0092] Assume that the interface type of the standard session request message includes either the Sxb interface type or the N4 interface type corresponding to the user plane network elements of the 5G core network. If the target interface type of the session request message is the Sxa interface type, then the message format of the Sxa interface type session request message is inconsistent with the message format of the standard session request message. Therefore, the preset message conversion rules corresponding to the Sxa interface type can be obtained from the preset message conversion rule base.

[0093] After obtaining the preset message conversion rules corresponding to the target interface type, the operator's preset rules corresponding to the target interface type can be further obtained. Here, the operator's preset rules refer to data conversion rules or data transmission and reception rules related to the operator's usage scenarios, etc., and this application does not limit them.

[0094] Therefore, the content of the session request message can be modified according to the preset message conversion rules corresponding to the target interface type and the operator's preset rules to generate a new target session request message. On one hand, the message format of the session request message is converted according to the preset message conversion rules corresponding to the target interface type to generate the target session request message. Optionally, since the preset message conversion rules corresponding to the session request message of this interface type define the mandatory content to be added to the session request message, and this mandatory content is the same as that in the standard session request message, converting the message format of the session request message according to the preset message conversion rules allows the addition of this mandatory content to generate the target session request message. Thus, the generated target session request message contains the mandatory content of the standard session request message. This ensures that the message format of the target session request message is consistent with that of the standard session request message, guaranteeing that the target session request message can be adapted to the general session request messages of various types of core network user plane network elements, just like the standard session request message.

[0095] On the other hand, based on the operator's preset rules corresponding to the target interface type, the content of the target session request message is modified to generate a new target session request message. Alternatively, it could be based on data conversion rules or data transmission / reception rules related to the operator's usage scenario, adding content related to these rules to the target session request message to generate a new target session request message. Of course, this application does not limit this approach.

[0096] In this embodiment, for each interface type, the signaling interoperability gateway can determine the preset message conversion rules corresponding to the session request messages of each interface type based on the standard session request message, thus obtaining a preset message conversion rule library. The signaling interoperability gateway can then retrieve the preset message conversion rules corresponding to the target interface type from the preset message conversion rule library. These preset message conversion rules are determined based on the message format of the standard session request message. The preset message conversion rules corresponding to the session request message of this interface type define the mandatory content that needs to be added to the session request message; this mandatory content is the mandatory content of the standard session request message. The signaling interoperability gateway then retrieves the operator's preset rules corresponding to the target interface type. Then, based on the preset message conversion rules corresponding to the target interface type and the operator's preset rules, it modifies the content of the session request message to generate a new target session request message. On one hand, it performs format conversion on the message format of the session request message according to the preset message conversion rules to generate the target session request message. On the other hand, based on data conversion rules or data transmission and reception rules related to the operator's usage scenarios, it adds content related to the data conversion rules or data transmission and reception rules to the target session request message to generate a new target session request message.

[0097] At this point, the message format of the new target session request message is consistent with that of the standard session request message. This ensures that the new target session request message can be adapted to the general session request messages of various types of core network user plane elements, just like the standard session request message. Furthermore, the new target session request message also includes the operator's preset rules corresponding to the target interface type. Therefore, it can better adapt to some special rules of the operator, further improving the compatibility of the new target session request message.

[0098] In the previous embodiment, the process of modifying the content of the session request message and generating a new target session request message from two dimensions—the preset message conversion rule corresponding to the target interface type and the operator's preset rule—was described. In this embodiment, step 220, receiving the session request message sent by the core network control plane element, includes:

[0099] After the core network control plane element establishes a PFCP association with the target core network user plane element through the signaling interconnection gateway, it receives the session request message sent by the core network control plane element.

[0100] Before the signaling interconnection gateway receives the session request message sent by the core network control plane element, converts the session request message into a format to generate a target session request message, and sends the target session request message to the target core network user plane element, it needs to establish a PFCP association between the core network control plane element and the target core network user plane element through the signaling interconnection gateway.

[0101] Here, a signaling interconnection gateway is introduced during the process of establishing a PFCP association between the private network and the public network. The signaling interconnection gateway enables message exchange between the private and public networks while simultaneously isolating the messages between them, thus resolving the security issues associated with message exchange between the two networks.

[0102] The PFCP (Packet Forwarding Control Protocol) is the control plane protocol used by the N4 interface between the SMF and UPF, defined in the TS 29.244 specification. The PFCP protocol is primarily used by the SMF to instruct the UPF on packet forwarding. Therefore, establishing a PFCP association between core network control plane elements and target core network user plane elements via a signaling interconnection gateway constitutes establishing a PFCP-based association between core network control plane elements and target core network user plane elements via a signaling interconnection gateway.

[0103] Then, after the core network control plane element establishes a PFCP association with the target core network user plane element through the signaling interconnection gateway, the signaling interconnection gateway can receive session request messages sent by the core network control plane element.

[0104] In this embodiment, the session request message is a PFCP-based message. Therefore, the entire process—from the core network control plane element sending the session request message to the signaling interconnection gateway, to the gateway converting the message format to generate a target session request message, and then sending the target session request message to the target core network user plane element—relies on the PFCP association established between the core network control plane element and the target core network user plane element through the signaling interconnection gateway. Thus, it is necessary to first establish a PFCP association between the core network control plane element and the target core network user plane element through the signaling interconnection gateway, and then the signaling interconnection gateway performs subsequent forwarding or format conversion processing on the session request message sent by the core network control plane element.

[0105] In the previous embodiment, the process of receiving a session request message sent by the core network control plane element after establishing a PFCP association between the core network control plane element and the target core network user plane element through a signaling interconnection gateway was described. In this embodiment, as... Figure 7 As shown, a message interaction method is provided, applied to a signaling interconnection gateway, and also includes:

[0106] Step 720: Receive the PFCP association establishment request sent by the core network control plane element; the PFCP association establishment request carries the address of the core network control plane element and the address of the target core network user plane element.

[0107] The core network control plane element sends a PFCP association establishment request to the signaling interconnection gateway, which then receives the request. The PFCP association establishment request instructs the core network control plane element to establish a PFCP association with a target core network user plane element through the signaling interconnection gateway. The request carries the addresses of both the core network control plane element and the target core network user plane element. These addresses are different for different core network user plane elements.

[0108] Step 740: Based on the address of the target core network user plane element, forward the PFCP association establishment request to the target core network user plane element; the PFCP association establishment request is used to instruct the target core network user plane element to generate a PFCP association establishment response message after receiving the PFCP association establishment request, and send the PFCP association establishment response message to the signaling interconnection gateway.

[0109] Since the PFCP association establishment request carries the address of the target core network user plane element, the PFCP association establishment request can be routed to the target core network user plane element based on the address of the target core network user plane element.

[0110] After receiving the PFCP association establishment request, the target core network user plane element generates a PFCP association establishment response message and sends it to the signaling interconnection gateway. The PFCP association establishment response message indicates that the target core network user plane element can establish a PFCP association with the core network control plane element at this time.

[0111] Step 760: Forward the PFCP association establishment response message to the core network control plane element based on the address of the core network control plane element, and establish a PFCP association between the core network control plane element and the target core network user plane element.

[0112] The signaling interconnection gateway then routes the PFCP association establishment response message to the core network control plane element based on the address of the core network control plane element carried in the PFCP association establishment request. Thus, when the core network control plane element receives the PFCP association establishment response message, it indicates that a PFCP association has been established between the core network control plane element and the target core network user plane element through the signaling interconnection gateway.

[0113] In this embodiment of the application, during the process of establishing a PFCP association between a core network control plane element and a target core network user plane element through a signaling interconnection gateway, the signaling interconnection gateway first receives a PFCP association establishment request sent by the core network control plane element. The PFCP association establishment request carries the address of the core network control plane element and the address of the target core network user plane element.

[0114] Then, the signaling interconnection gateway forwards the PFCP association establishment request to the target core network user plane element based on its address. Upon receiving the PFCP association establishment request, the target core network user plane element generates a PFCP association establishment response message and sends it to the signaling interconnection gateway. Finally, the signaling interconnection gateway routes the PFCP association establishment response message to the core network control plane element based on the address of the core network control plane element carried in the PFCP association establishment request. This establishes a PFCP association between the core network control plane element and the target core network user plane element via the signaling interconnection gateway. The signaling interconnection gateway enables message exchange between the private network and the public network while simultaneously isolating the messages between them, thus resolving the security issues associated with message exchange between the private and public networks.

[0115] In one exemplary embodiment, such as Figure 8 As shown, a message interaction method is provided, applied to a signaling interconnection gateway. The method is illustrated in an application scenario where the core network control plane element is the Session Management Element (SMF) and the core network user plane element is the User Plane Element (UPF). The method includes:

[0116] Step 802: Receive the PFCP association establishment request sent by the SMF; the PFCP association establishment request carries the address of the SMF and the address of the target UPF;

[0117] Step 804: Based on the address of the target UPF, forward the PFCP association establishment request to the target UPF; the PFCP association establishment request is used to instruct the target UPF to generate a PFCP association establishment response message after receiving the PFCP association establishment request, and send the PFCP association establishment response message to the signaling interconnection gateway;

[0118] Step 806: Receive the PFCP association establishment response message sent by the target UPF;

[0119] Step 808: Forward the PFCP association establishment response message to the SMF, and establish a PFCP association between the SMF and the target UPF;

[0120] Step 810: Receive the session request message sent by SMF;

[0121] Step 812: Parse the session request message to obtain the packet detection rules and the forwarding operation rules associated with the packet detection rules; extract the target field from the packet detection rules and the forwarding operation rules, and determine the target interface type of the session request message based on the target field; the target interface type includes at least one of the Sxa interface type, Sxb interface type and N4 interface type; convert the format of the session request message according to the target interface type to generate the target session request message;

[0122] Step 814: Send the target session request message to the target UPF; the target UPF includes various types of UPFs.

[0123] like Figure 9 The diagram illustrates the signaling process in one embodiment where the Session Management Element (SMF) establishes a PFCP association with the User Plane Element (UPF) of the core network through a signaling interoperability gateway, and interacts with the UPF via session request messages. Step 1: The SMF sends a PFCP association establishment request to the signaling interoperability gateway, which receives the request. Step 2: Based on the address of the target UPF, the SMF forwards the PFCP association establishment request to the target UPF. Step 3: After receiving the PFCP association establishment request, the target UPF generates a PFCP association establishment response message and sends it to the signaling interoperability gateway. Step 4: The signaling interoperability gateway then forwards the PFCP association establishment response message to the SMF based on the SMF address carried in the PFCP association establishment request. Step 5: The SMF receives a session establishment or modification request trigger message. Step 6: The SMF sends a session request message to the signaling interoperability gateway. Step 7: The signaling interconnection gateway parses the session request message to obtain the packet detection rules and the forwarding operation rules associated with them. It extracts the target field from the packet detection rules and forwarding operation rules, and determines the target interface type of the session request message based on the target field. The target interface type includes at least one of the Sxa, Sxb, and N4 interface types. The session request message is then formatted according to the target interface type to generate the target session request message. Step 8: The signaling interconnection gateway sends the target session request message to the target UPF.

[0124] In this embodiment, a PFCP association is established between the core network control plane network element and the target core network user plane network element through a signaling interconnection gateway. The signaling interconnection gateway enables message exchange between the private network and the public network while simultaneously isolating the messages between them, thus resolving the security issues associated with message exchange between the private and public networks.

[0125] In scenarios where core network user plane elements for private network services are converged, the signaling interconnection gateway receives session request messages from core network control plane elements, converts the session request messages into a format suitable for various types of core network user plane elements, and then sends the target session request message to the target core network user plane element. Therefore, even if the target core network user plane element includes multiple types of core network user plane elements, the target session request message can still be adapted to the target core network user plane element.

[0126] Therefore, by converting the format of the session request message, the situation where the session request message is incompatible with the old core network user plane network element and the new core network user plane network element can be avoided when the message is exchanged between the core network control plane network element and the core network user plane network element.

[0127] It should be understood that although the steps in the flowchart above are shown sequentially as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart above may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0128] Based on the same inventive concept, such as Figure 10 As shown, in this embodiment, a message interaction device 1000 is further provided, applied to a signaling interconnection gateway. The device includes:

[0129] The message receiving module 1020 is used to receive session request messages sent by the core network control plane network element after the core network control plane network element has established a PFCP association with the target core network user plane network element through the signaling interconnection gateway; the target core network user plane network element includes various types of core network user plane network elements;

[0130] The message format conversion module 1040 is used to convert the format of the session request message and generate the target session request message; the target session request message is adapted to various types of core network user plane network elements.

[0131] The message sending module 1060 is used to send the target session request message to the target core network user plane network element.

[0132] In one embodiment, the message format conversion module 1040 includes:

[0133] The parsing unit is used to parse the session request message to obtain the packet detection rules and the forwarding operation rules associated with the packet detection rules;

[0134] The target interface type determination unit is used to extract target fields from packet detection rules and forwarding operation rules, and determine the target interface type of the session request message based on the target fields; the target interface type includes at least one of Sxa interface type, Sxb interface type and N4 interface type.

[0135] The format conversion unit is used to convert the format of the session request message according to the target interface type and generate the target session request message.

[0136] In one embodiment, the format conversion unit is further configured to obtain a preset message conversion rule corresponding to the target interface type; the preset message conversion rule is determined based on the message format of the standard session request message; the message format of the session request message is converted according to the preset message conversion rule to generate the target session request message; the message format of the target session request message is consistent with the message format of the standard session request message.

[0137] In one embodiment, the format conversion unit is further configured to: if the target interface type of the session request message includes the Sxa interface type, obtain the preset message conversion rule corresponding to the Sxa interface type; fill in standard fields into the message part of the session request message for the Sxa interface type according to the preset message conversion rule corresponding to the Sxa interface type, and generate the target session request message; the standard fields include the required fields in the standard session request message.

[0138] In one embodiment, the format conversion unit is further configured to obtain the preset message conversion rules and operator preset rules corresponding to the target interface type; modify the content of the session request message according to the preset message conversion rules and operator preset rules, and generate a new target session request message.

[0139] In one embodiment, the message format conversion module 1040 is further configured to receive a session request message sent by the core network control plane element after the core network control plane element establishes a PFCP association with the target core network user plane element through the signaling interconnection gateway.

[0140] In one embodiment, such as Figure 11 As shown, a message interaction device is provided, which further includes:

[0141] The PFCP association establishment module 1080 is used to receive PFCP association establishment requests sent by core network control plane network elements; the PFCP association establishment request carries the address of the core network control plane network element and the address of the target core network user plane network element;

[0142] Based on the address of the target core network user plane element, the PFCP association establishment request is forwarded to the target core network user plane element; the PFCP association establishment request is used to instruct the target core network user plane element to generate a PFCP association establishment response message after receiving the PFCP association establishment request, and send the PFCP association establishment response message to the signaling interconnection gateway.

[0143] The PFCP association establishment response message is forwarded to the core network control plane element, and a PFCP association is established between the core network control plane element and the target core network user plane element.

[0144] In one embodiment, the core network control plane network element includes a session management network element, and the core network user plane network element of various network element types includes any two or more of the following: 4G core network user plane network element, 5G core network user plane network element, and 6G core network user plane network element.

[0145] Based on the same inventive concept, a communication device is provided, including a transmitter, a processor, and a receiver;

[0146] The transmitter is used to receive session request messages sent by core network control plane network elements;

[0147] The processor is used to convert the format of the session request message and generate the target session request message; the target session request message is adapted to various types of core network user plane network elements.

[0148] The receiver is used to send the target session request message to the target core network user plane element; the target core network user plane element includes various types of core network user plane elements.

[0149] The division of the various modules in the above message interaction device is only for illustrative purposes. In other embodiments, the message interaction device can be divided into different modules as needed to complete all or part of the functions of the above message interaction device.

[0150] For specific limitations regarding the message interaction device, please refer to the limitations on the message interaction method above, which will not be repeated here. Each module in the aforementioned message interaction device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in the computer device in hardware form, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0151] Figure 12 This is a schematic diagram of the structure of the communication device provided in an embodiment of the present invention. Figure 12The communication device 1200 shown includes at least one processor 1201, a memory 1202, and at least one network interface 1204. The various components in the communication device 1200 are coupled together via a bus system 1205. It is understood that the bus system 1205 is used to implement communication between these components. In addition to a data bus, the bus system 1205 also includes a power bus, a control bus, and a status signal bus. However, for clarity, ... Figure 12 Various buses are designated as bus system 1205. Additionally, this embodiment of the invention includes a transceiver, which may consist of multiple components, including receiver 1206 and transmitter 1207, providing a unit for communicating with various other devices over a transmission medium.

[0152] It is understood that the memory 1202 in the embodiments of the present invention can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DRRAM). The memory 1202 of the systems and methods described in the embodiments of the present invention is intended to include, but is not limited to, these and any other suitable types of memory.

[0153] In some implementations, memory 1202 stores elements such as executable modules or data structures, or subsets thereof, or extended sets thereof: operating system 1202a. Operating system 1202a includes various system programs, such as a framework layer, core library layer, and driver layer, used to implement various basic business functions and handle hardware-based tasks.

[0154] In this embodiment of the invention, by calling the program or instructions stored in the memory 1202, the receiver 1206 is configured to receive a session request message sent by a core network control plane element; the processor is configured to perform format conversion on the session request message to generate a target session request message; the target session request message is adapted to various types of core network user plane elements; and the transmitter 1207 is configured to send the target session request message to a target core network user plane element; the target core network user plane element includes various types of core network user plane elements.

[0155] The methods disclosed in the above embodiments of the present invention, in part or in all of them, can also be applied to processor 1201, implemented by processor 1201, or implemented by processor 1201 in conjunction with other components (e.g., transceivers). Processor 1201 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above methods can be completed by the integrated logic circuit of the hardware in processor 1201 or by instructions in the form of software. The processor 1201 may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present invention. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of the present invention can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory 1202. The processor 1201 reads the information in memory 1202 and, in conjunction with its hardware, completes the steps of the above method.

[0156] It is understood that the embodiments described in these embodiments of the present invention can be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions of this application, or combinations thereof.

[0157] For software implementation, the techniques of the embodiments of the present invention can be implemented through modules (e.g., procedures, functions, etc.) that perform the functions of the embodiments of the present invention. The software code can be stored in memory and executed by processor 1201. The memory can be implemented in processor 1201 or external to processor 1201.

[0158] In one embodiment, the processor is further configured to parse the session request message to obtain packet detection rules and forwarding operation rules associated with the packet detection rules; extract target fields from the packet detection rules and forwarding operation rules, and determine the target interface type of the session request message based on the target fields; the target interface type includes at least one of Sxa interface type, Sxb interface type and N4 interface type; and perform format conversion on the session request message according to the target interface type to generate a target session request message.

[0159] In one embodiment, the processor is further configured to obtain a preset message conversion rule corresponding to the target interface type; the preset message conversion rule is determined based on the message format of the standard session request message; according to the preset message conversion rule, the message format of the session request message is converted to generate a target session request message; the message format of the target session request message is consistent with the message format of the standard session request message.

[0160] In one embodiment, the processor is further configured to obtain a preset message conversion rule corresponding to the Sxa interface type if the target interface type of the session request message includes the Sxa interface type.

[0161] Based on the preset message conversion rules corresponding to the Sxa interface type, fill in the standard fields in the message part of the session request message for the Sxa interface type to generate the target session request message; the standard fields include the required fields in the standard session request message.

[0162] In one embodiment, the processor is further configured to obtain the preset message conversion rules and operator preset rules corresponding to the target interface type; modify the content of the session request message according to the preset message conversion rules and operator preset rules, and generate a new target session request message.

[0163] In one embodiment, receiver 1206 is further configured to receive a session request message sent by the core network control plane element after the core network control plane element establishes a PFCP association with the target core network user plane element through a signaling interconnection gateway.

[0164] In one embodiment, receiver 1206 is further configured to receive a PFCP association establishment request sent by a core network control plane element; the PFCP association establishment request carries the address of the core network control plane element and the address of the target core network user plane element.

[0165] The transmitter 1207 is also used to forward the PFCP association establishment request to the target core network user plane network element according to the address of the target core network user plane network element; the PFCP association establishment request is used to instruct the target core network user plane network element to generate a PFCP association establishment response message after receiving the PFCP association establishment request, and send the PFCP association establishment response message to the signaling interconnection gateway.

[0166] The transmitter 1207 is also used to forward the PFCP association establishment response message to the core network control plane network element, and establish a PFCP association between the core network control plane network element and the target core network user plane network element.

[0167] This application also provides a computer-readable storage medium. One or more non-volatile computer-readable storage media containing computer-executable instructions, which, when executed by one or more processors, cause the processors to perform the steps of a message interaction method.

[0168] This application also provides a computer program product containing instructions that, when run on a computer, cause the computer to execute a message interaction method.

[0169] Any references to memory, storage, databases, or other media used in this application may include non-volatile and / or volatile memory. Non-volatile memory may include ROM (Read-Only Memory), PROM (Programmable Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), or flash memory. Volatile memory may include RAM (Random Access Memory), which is used as external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as SRAM (Static Random Access Memory), DRAM (Dynamic Random Access Memory), SDRAM (Synchronous Dynamic Random Access Memory), Double Data Rate DDR SDRAM (Double Data Rate Synchronous Dynamic Random Access Memory), ESDRAM (Enhanced Synchronous Dynamic Random Access Memory), SLDRAM (Sync Link Dynamic Random Access Memory), RDRAM (Rambus Dynamic Random Access Memory), and DRDRAM (Direct Rambus Dynamic Random Access Memory).

[0170] The above embodiments merely illustrate several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A message interaction method, characterized in that, The method is applied to a signaling interoperability gateway, which is deployed between core network control plane network elements and core network user plane network elements. The signaling interoperability gateway is used to forward signaling messages between enterprise private networks and carrier networks. The method includes: Receive the session request message sent by the core network control plane network element; The session request message is parsed to obtain the packet detection rules and the forwarding operation rules associated with the packet detection rules; Extract the target field from the packet detection rules and the forwarding operation rules, and determine the target interface type of the session request message based on the target field; Determine whether the target interface type of the session request message is consistent with the interface type of the standard session request message; the standard session request message is adapted to multiple types of core network user plane network elements, and the message format of the standard session request message includes the mandatory content for the multiple types of core network user plane network elements to perform operations; If the target interface type is inconsistent with the interface type of the standard session request message, then the session request message is format-converted according to the message format of the standard session request message and the target interface type to generate a target session request message; the message format of the target session request message is consistent with the message format of the standard session request message, and the target session request message is adapted to the various types of core network user plane network elements; The target session request message is sent to the target core network user plane element; the target core network user plane element includes the various types of core network user plane elements.

2. The method according to claim 1, characterized in that, The target interface type includes at least one of the Sxa interface type, Sxb interface type, and N4 interface type.

3. The method according to claim 2, characterized in that, The step of converting the session request message according to the message format of the standard session request message and the target interface type to generate a target session request message includes: Obtain the preset message conversion rule corresponding to the target interface type; the preset message conversion rule is determined based on the message format of the standard session request message; According to the preset message conversion rules, the message format of the session request message is converted to generate the target session request message.

4. The method according to claim 3, characterized in that, The step of obtaining the preset message conversion rule corresponding to the target interface type includes: If the target interface type of the session request message includes the Sxa interface type, then obtain the preset message conversion rule corresponding to the Sxa interface type; The step of converting the message format of the session request message according to the preset message conversion rules to generate the target session request message includes: According to the preset message conversion rules corresponding to the Sxa interface type, standard fields are filled into the message part of the session request message of the Sxa interface type to generate the target session request message; the standard fields include the required fields in the standard session request message.

5. The method according to claim 2, characterized in that, The step of converting the format of the session request message according to the target interface type to generate the target session request message includes: Obtain the preset message conversion rules and operator preset rules corresponding to the target interface type; The content of the session request message is modified according to the preset message conversion rules and the operator's preset rules to generate a new target session request message.

6. The method according to claim 1, characterized in that, The receiving of the session request message sent by the core network control plane element includes: After the core network control plane element establishes a PFCP association with the target core network user plane element through the signaling interconnection gateway, it receives a session request message sent by the core network control plane element.

7. The method according to claim 6, characterized in that, The method further includes: Receive the PFCP association establishment request sent by the core network control plane element; the PFCP association establishment request carries the address of the core network control plane element and the address of the target core network user plane element; Based on the address of the target core network user plane element, the PFCP association establishment request is forwarded to the target core network user plane element; the PFCP association establishment request is used to instruct the target core network user plane element to generate a PFCP association establishment response message after receiving the PFCP association establishment request, and to send the PFCP association establishment response message to the signaling interconnection gateway. The PFCP association establishment response message is forwarded to the core network control plane element based on the address of the core network control plane element, and a PFCP association is established between the core network control plane element and the target core network user plane element.

8. The method according to claim 1, characterized in that, The core network control plane network elements include session management network elements, and the various types of core network user plane network elements include any two or more of the following: 4G core network user plane network elements, 5G core network user plane network elements, and 6G core network user plane network elements.

9. A message interaction device, characterized in that, An application is made to a signaling interoperability gateway, which is deployed between core network control plane network elements and core network user plane network elements. The signaling interoperability gateway is used to forward signaling messages between enterprise private networks and carrier networks. The device includes: The message receiving module is used to receive session request messages sent by the core network control plane network elements; The message format conversion module is used to parse the session request message to obtain packet detection rules and forwarding operation rules associated with the packet detection rules; extract target fields from the packet detection rules and the forwarding operation rules, and determine the target interface type of the session request message based on the target fields; determine whether the target interface type of the session request message is consistent with the interface type of the standard session request message; the standard session request message is adapted to multiple types of core network user plane network elements, and the message format of the standard session request message includes mandatory content for the operations performed by the multiple types of core network user plane network elements; If the target interface type is inconsistent with the interface type of the standard session request message, then the session request message is format-converted according to the message format of the standard session request message and the target interface type to generate a target session request message; the message format of the target session request message is consistent with the message format of the standard session request message, and the target session request message is adapted to the various types of core network user plane network elements; The message sending module is used to send the target session request message to the target core network user plane element; the target core network user plane element includes the various types of core network user plane elements.

10. A communication device, characterized in that, Includes transmitter, processor, and receiver; The transmitter is used to receive session request messages sent by core network control plane network elements; The processor is configured to parse the session request message to obtain packet detection rules and forwarding operation rules associated with the packet detection rules; extract target fields from the packet detection rules and the forwarding operation rules, and determine the target interface type of the session request message based on the target fields; determine whether the target interface type of the session request message is consistent with the interface type of the standard session request message; the standard session request message is adapted to multiple types of core network user plane network elements, and the message format of the standard session request message includes mandatory content for the multiple types of core network user plane network elements to perform operations; If the target interface type is inconsistent with the interface type of the standard session request message, then the session request message is format-converted according to the message format of the standard session request message and the target interface type to generate a target session request message; the message format of the target session request message is consistent with the message format of the standard session request message, and the target session request message is adapted to the various types of core network user plane network elements; The receiver is used to send the target session request message to the target core network user plane element; the target core network user plane element includes the various types of core network user plane elements.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the message interaction method as described in any one of claims 1 to 8.

12. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the message interaction method according to any one of claims 1 to 8.

Images