CN114553834B - Interaction method and device of 5G core network and IMS network - Google Patents

Interaction method and device of 5G core network and IMS network Download PDF

Info

Publication number
CN114553834B
CN114553834B CN202210189209.1A CN202210189209A CN114553834B CN 114553834 B CN114553834 B CN 114553834B CN 202210189209 A CN202210189209 A CN 202210189209A CN 114553834 B CN114553834 B CN 114553834B
Authority
CN
China
Prior art keywords
protocol type
data packet
address
mapping table
protocol
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202210189209.1A
Other languages
Chinese (zh)
Other versions
CN114553834A (en
Inventor
王磊
刘海龙
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
New H3C Technologies Co Ltd
Original Assignee
New H3C Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by New H3C Technologies Co Ltd filed Critical New H3C Technologies Co Ltd
Priority to CN202210189209.1A priority Critical patent/CN114553834B/en
Publication of CN114553834A publication Critical patent/CN114553834A/en
Application granted granted Critical
Publication of CN114553834B publication Critical patent/CN114553834B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The application provides an interaction method and device of a 5G core network and an IMS network. In the application, through the compatibility processing flow of the network element on the control surface of the 5G core network for receiving the first data packet from the first IMS network or the third data packet to be sent to the second IMS network, the 5G core network and the IMS network are communicated under the condition of not changing the network topology structure. Further, in this embodiment, when the network element on the control plane of the 5G core network interworks with the IMS network without changing the network topology, it is determined whether to perform protocol conversion on the data packet according to the configured mode and the data packet detection condition, so that the adaptation is strong, and the method and the device can be widely applied to the field of mobile communication.

Description

Interaction method and device of 5G core network and IMS network
Technical Field
The present application relates to 5G network technologies, and in particular, to a method and apparatus for interaction between a 5G core network and an IP multimedia subsystem (IMS: IP Multimedia Subsystem) network.
Background
The control plane of the 5G core network adopts a service architecture design, and uniformly adopts HTTP/2 application layer protocol. In the control plane of the 5G core network, all the servitization interfaces can transmit on the same bus, and this communication mode can be understood as a bus communication mode.
An IP multimedia subsystem (IMS: IP Multimedia Subsystem) network is a generic network architecture that provides multimedia services over IP-based networks. How to realize interaction between the IMS network and the 5G core network is a technical problem to be solved at present.
Disclosure of Invention
The application provides an interaction method and device of a 5G core network and an IMS network, so as to realize interaction of the 5G core network and the IMS network.
The embodiment of the application provides an interaction method of a 5G core network and an IMS network, which is applied to network elements which communicate with the IMS network in the 5G core network, and comprises the following steps:
for a received first data packet from a first IMS network, if a configured working mode on a local network element is an adaptive mode, identifying a protocol type supported by the first IMS network, and when the protocol type is inconsistent with the protocol type supported by the local network element in the 5G core network, obtaining a second data packet obtained after protocol conversion of the first data packet, wherein the protocol type of the second data packet is the same as the protocol type supported by the local network element in the 5G core network, and processing the second data packet;
and for a third data packet to be sent to the second IMS network, if the configured working mode on the local network element is the self-adaptive mode, identifying the protocol type supported by the second IMS network, and when the protocol type is inconsistent with the protocol type supported by the local network element in the 5G core network, obtaining a fourth data packet obtained after the third data packet is subjected to protocol conversion, wherein the protocol type to which the fourth data packet belongs is the same as the protocol type supported by the second IMS network, and sending the fourth data packet to the second IMS network.
The embodiment of the application provides an interaction device of a 5G core network and an IMS network, which is applied to a network element which communicates with the IMS network in the 5G core network, and comprises the following components:
a receiving and processing unit, configured to identify a protocol type supported by a first IMS network if a configured working mode on a local network element is an adaptive mode for a received first data packet from the first IMS network, and obtain a second data packet obtained after performing protocol conversion on the first data packet when the protocol type is inconsistent with a protocol type supported by the local network element in the 5G core network, where the protocol type to which the second data packet belongs is the same as the protocol type supported by the local network element in the 5G core network, and process the second data packet;
and the sending processing unit is used for identifying the protocol type supported by the second IMS network if the configured working mode on the network element is the self-adaptive mode for the third data packet to be sent to the second IMS network, and obtaining a fourth data packet obtained after the third data packet is subjected to protocol conversion when the protocol type is inconsistent with the protocol type supported by the network element on the 5G core network, wherein the protocol type to which the fourth data packet belongs is the same as the protocol type supported by the second IMS network, and sending the fourth data packet to the second IMS network.
The embodiment of the application also provides electronic equipment. The electronic device includes: a processor and a machine-readable storage medium;
the machine-readable storage medium stores machine-executable instructions executable by the processor;
the processor is configured to execute machine-executable instructions to perform the steps of the methods disclosed above.
According to the technical scheme, in the application, the compatibility processing flow of the received first data packet from the first IMS network or the third data packet to be sent to the second IMS network is realized through the network element on the control surface of the 5G core network, so that the 5G core network and the IMS network are communicated under the condition of not changing the network topology structure.
Further, in this embodiment, when the network element on the control plane of the 5G core network interworks with the IMS network without changing the network topology, it is determined whether to perform protocol conversion on the data packet according to the configured mode and the data packet detection condition, so that the adaptation is strong, and the method and the device can be widely applied to the field of mobile communication.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure.
FIG. 1 is a flow chart of a method provided in an embodiment of the present application;
fig. 2 is a flowchart of identifying a protocol type supported by the first IMS network in step 102 provided in an embodiment of the present application;
fig. 3 is a flowchart of identifying a protocol type supported by the second IMS network in step 103 provided in an embodiment of the present application;
fig. 4 is a schematic diagram of networking provided in an embodiment of the present application;
FIG. 5 is a block diagram of an apparatus according to an embodiment of the present application;
fig. 6 is a block diagram of an electronic device according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.
The terminology used in the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the present application. As used in this application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
In order to better understand the technical solutions provided by the embodiments of the present application and make the above objects, features and advantages of the embodiments of the present application more obvious, the technical solutions in the embodiments of the present application are described in further detail below with reference to the accompanying drawings.
The embodiment of the application provides an interaction method of a 5G core network and an IMS network, so that the IMS network can be simultaneously interconnected and communicated with a control plane of the 5G core network under the condition of not changing the existing network topology. The following describes the method provided in the embodiments of the present application:
referring to fig. 1, fig. 1 is a flowchart of a method provided in an embodiment of the present application. The method is applied to network elements in the 5G core network which communicate with the IMS network. In a 5G core network, network elements such as policy control functions (PCF: policy Control Function), unified data management functions (UDM: unified Data Management), etc. may need to interact with the IMS network, i.e. these network elements may be network elements in the 5G core network that communicate with the IMS network (also may be referred to as demand network elements).
As shown in fig. 1, the process may include the steps of:
step 101, for a first packet received from a first IMS network, step 102 is performed, and for a third packet to be sent to a second IMS network, step 103 is performed.
In this embodiment, the first IMS network is generally referred to as any IMS network. The first data packet is also broadly referred to as any one of the data packets. It is named for convenience of description only and is not intended to be limiting.
In this embodiment, optionally, when the network element receives a data packet through an interface (also referred to as a network side interface) connected to the IMS network, the data packet may be referred to as a data packet from the IMS network. Alternatively, after the network element receives the data packet, if the source IP address of the data packet is the IP address in the IMS network, the data packet may be referred to as a data packet from the IMS network. Here, whether the source IP address of the data packet is an IP address in the IMS network may be determined by: searching a source IP address of the data packet in a configured IP address table; the IP address table is used for recording the IP address in the IMS network; if so, determining the source IP address of the data packet as the IP address in the IMS network. In this embodiment, the IP address table may be set in advance.
Also, in this embodiment, the second IMS network generally refers to any IMS network, such as the first IMS network described above. The third data packet is also broadly referred to as any one of the data packets. It is named for convenience of description only and is not intended to be limiting.
In this embodiment, optionally, after the network element receives the data packet, if the destination IP address of the data packet is an IP address in the IMS network, the data packet may be referred to as a data packet to be sent to the IMS network. Here, whether the destination IP address of the data packet is an IP address in the IMS network may be determined by: searching the destination IP address of the data packet in the configured IP address table; the IP address table is used for recording the IP address in the IMS network; if so, determining the destination IP address of the data packet as the IP address in the IMS network. In this embodiment, the IP address table may be set in advance.
Step 102, if the configured working mode on the local network element is the adaptive mode, identifying a protocol type supported by the first IMS network, and when the protocol type is inconsistent with the protocol type supported by the local network element in the 5G core network, obtaining a second data packet obtained after the protocol conversion of the first data packet, wherein the protocol type of the second data packet is the same as the protocol type supported by the local network element in the 5G core network, and processing the second data packet.
This step 102 is the processing for the received first data packet from the first IMS network.
Optionally, in this embodiment, there are many ways to identify the protocol types supported by the first IMS network in step 102, and fig. 2 illustrates one implementation of the method, which is not described herein for brevity.
Optionally, in this embodiment, if the configured operation mode of the home network element is not the adaptive mode, such as the transition mode, the step 102 further includes: and obtaining the data packet obtained after the protocol conversion of the first data packet.
For example, the configured operation mode on the local network element is not the adaptive mode, for example, is not a switching mode. The non-translated mode is set here because the protocol type supported by the first IMS network is the same as the protocol type supported by the home network element in the 5G core network, i.e. the non-translated mode is used to indicate that the protocol type supported by the first IMS network is the same as the protocol type supported by the home network element in the 5G core network. Based on this, the step 102 further includes: the specific processing manner of the first data packet, such as sending the first data packet to the terminal, is similar to that of the existing 5G core network, and will not be described again.
Optionally, in this embodiment, the protocol type to which the second data packet belongs is the same as the protocol type supported by the local network element in the 5G core network, for example, both are HTTP/2 protocols. At this time, optionally, the protocol type supported by the first IMS network may be a Diameter protocol.
Of course, in step 102, if the protocol type supported by the first IMS network is the same as the protocol type supported by the network element in the 5G core network, for example, the protocol types are all HTTP/2 protocols, the first data packet may be directly processed, for example, the first data packet may be sent to the terminal.
And 103, if the configured working mode on the local network element is the self-adaptive mode, identifying a protocol type supported by the second IMS network, and when the protocol type is inconsistent with the protocol type supported by the local network element in the 5G core network, obtaining a fourth data packet obtained after the third data packet is subjected to protocol conversion, wherein the protocol type to which the fourth data packet belongs is the same as the protocol type supported by the second IMS network, and sending the fourth data packet to the second IMS network.
This step 103 is a process performed on a third data packet to be sent to the second IMS network.
Optionally, in this embodiment, there are many ways to identify the protocol type supported by the second IMS network in step 103, and fig. 3 illustrates one implementation of this, which is not described herein for brevity.
Optionally, in this embodiment, if the configured operation mode of the home network element is not the adaptive mode, such as the transition mode, the step 103 further includes: and obtaining the fourth data packet obtained after the third data packet is subjected to protocol conversion.
For example, the configured operation mode on the local network element is not the adaptive mode, for example, is not a switching mode. The non-translated mode is set here because the protocol type supported by the second IMS network is the same as the protocol type supported by the home network element in the 5G core network, i.e. the non-translated mode is used to indicate that the protocol type supported by the second IMS network is the same as the protocol type supported by the home network element in the 5G core network. Based on this, the step 103 further includes: and sending a third data packet to the second IMS network.
Optionally, in this embodiment, the protocol type to which the fourth data packet belongs is the same as the protocol type supported by the second IMS network, for example, both are Diameter protocols. At this time, optionally, the protocol type supported by the home network element in the 5G core network may be HTTP/2 protocol.
Of course, in step 103, if the protocol type supported by the second IMS network is the same as the protocol type supported by the network element in the 5G core network, for example, both the protocol types are HTTP/2 protocols, the third data packet may be directly sent to the second IMS network.
Thus, the flow shown in fig. 1 is completed.
As can be seen from the flow shown in fig. 1, in this embodiment, the compatibility processing flow of the received first data packet from the first IMS network or the third data packet to be sent to the second IMS network by the network element on the control plane of the 5G core network implements interworking between the 5G core network and the IMS network without changing the network topology.
Further, in this embodiment, when the network element on the control plane of the 5G core network interworks with the IMS network without changing the network topology, it is determined whether to perform protocol conversion on the data packet according to the configured mode and the data packet detection condition, so that the adaptation is strong, and the method and the device can be widely applied to the field of mobile communication.
The flow shown in fig. 2 is described below:
referring to fig. 2, fig. 2 is a flowchart of identifying a protocol type supported by the first IMS network in step 102 provided in an embodiment of the present application. As shown in fig. 2, the process may include the steps of:
step 201, a target IP address-protocol type mapping table containing the source IP address of the first data packet is searched in the configured IP address-protocol type mapping table, if the target IP address-protocol type mapping table is searched and the target IP address-protocol type mapping table is a static IP address-protocol type mapping table, step 202 is executed, if the target IP address-protocol type mapping table is not searched, or if the target IP address-protocol type mapping table is searched and the target IP address-protocol type mapping table is a dynamic IP address-protocol type mapping table, step 203 is executed.
In this embodiment, the IP address-protocol type mapping table in the IP address-protocol type mapping table is used to record the correspondence between the IP address in the IMS network and the protocol type supported by the IMS network, which can be specifically subdivided into a preset IP address-protocol type mapping table (denoted as static IP address-protocol type mapping table), and an IP address-protocol type mapping table (denoted as dynamic IP address-protocol type mapping table) that is dynamically learned and established and is in an effective time. How to learn and build the dynamic IP address-protocol type mapping table will be described in detail below, and will not be repeated here.
Step 202, determining the protocol type corresponding to the source IP address in the target IP address-protocol type mapping table entry as the protocol type supported by the first IMS network.
The step 202 is executed on the premise that the above-mentioned target IP address-protocol type mapping table entry is found in the configured IP address-protocol type mapping table and the target IP address-protocol type mapping table entry is a static IP address-protocol type mapping table entry.
Step 203, determining the protocol type of the source port number according to the source port number of the first data packet, and determining the protocol type of the source port number as the protocol type supported by the first IMS network.
This step 203 is performed on the premise that the configured IP address-protocol type mapping table does not find the target IP address-protocol type mapping table entry, or that the target IP address-protocol type mapping table entry is found and the target IP address-protocol type mapping table entry is a dynamic IP address-protocol type mapping table entry.
In an application, an application layer protocol, such as a Diameter protocol, an HTTP/2 protocol, etc., corresponds to different port numbers, based on which, in step 203, the protocol type to which the source port number belongs may be identified by extracting the source port number of the first packet, and the protocol type to which the source port number belongs may be determined as the protocol type supported by the first IMS network.
Thus, the flow shown in fig. 2 is completed.
How the protocol types supported by the first IMS network are identified is implemented by the flow shown in fig. 2.
It should be noted that, in this embodiment, if the mapping table item of the target IP address-protocol type is not found, after determining the protocol type to which the source port number belongs as the protocol type supported by the first IMS network, the method further includes: and adding the corresponding relation between the source IP address of the first data packet and the protocol type to which the source port number belongs as a dynamic IP address-protocol type mapping table item to the configured IP address-protocol type mapping table. The dynamic IP address-protocol type mapping table item is dynamically added in the configured IP address-protocol type mapping table. Optionally, in this embodiment, the static IP address-protocol type mapping table entry in the IP address-protocol type mapping table is valid for the duration of the existence and cannot be updated. And for the dynamically added dynamic IP address-protocol type mapping table entry, a corresponding validity time may be set. Each dynamic IP address-protocol type mapping table entry is valid for a valid time and can be dynamically deleted beyond the valid time.
In this embodiment, if the target IP address-protocol type mapping table entry is found and the target IP address-protocol type mapping table entry is a dynamic IP address-protocol type mapping table entry, after determining that the protocol type to which the source port number belongs is the protocol type supported by the first IMS network, the method further includes: updating the target IP address-protocol type mapping table, wherein the updated IP address-protocol type mapping table is a dynamic IP address-protocol type mapping table which contains the corresponding relation between the source IP address of the first data packet and the protocol type to which the source port number belongs. Here, the target IP address-protocol type mapping table entry is updated in order to obtain the corresponding protocol type of the same IP changed due to the requirement in time. Of course, updating the target IP address-protocol type mapping table entry is also equivalent to resetting the validity time of the target IP address-protocol type mapping table entry, maintaining the updated IP address-protocol type mapping table entry valid for a longer validity time.
The flow shown in fig. 3 is described below:
referring to fig. 3, fig. 3 is a flowchart of identifying a protocol type supported by the second IMS network in step 103 provided in an embodiment of the present application. As shown in fig. 3, the process may include the steps of:
Step 301, the destination IP address of the third packet is found in the configured IP address-protocol type mapping table.
The IP address-protocol type mapping table is described above.
Step 302, if the destination IP address of the third data packet is found in the configured IP address-protocol type mapping table, determining the protocol type corresponding to the destination IP address as the protocol type supported by the second IMS network.
In this embodiment, the third packet sent by the 5G core network to the second IMS network is a packet from the second IMS network before the response, since it is a response packet, it must find the destination IP address of the third packet in the configured IP address-protocol type mapping table without any unexpected situation. Of course, in special cases, if the destination IP address of the third data packet is not found in the configured IP address-protocol type mapping table, the third data packet may be directly sent to the second IMS network.
Thus, the flow shown in fig. 3 is completed.
How to identify the protocol types supported by the second IMS network is implemented by the flow shown in fig. 3.
In this embodiment, the protocol conversion may be performed by a protocol conversion program.
In one embodiment, the protocol conversion program may be deployed at any server in the 5G core network. The server may be connected to a control plane network element in the 5G core network based on the SBA architecture in the 5G core network, as particularly shown in fig. 4.
In fig. 4, in step 102, obtaining the second data packet obtained by performing protocol conversion on the first data packet includes: and forwarding the first data packet to a server with a deployed protocol conversion program in the 5G core network, so that the server carries out protocol conversion on the first data packet through the configured protocol conversion program to obtain a second data packet, and receiving the second data packet returned by the server.
Likewise, the obtaining the fourth data packet obtained by performing protocol conversion on the third data packet includes: and forwarding the third data packet to a server with a deployed protocol conversion program in the 5G core network, so that the server carries out protocol conversion on the third data packet through the configured protocol conversion program to obtain a fourth data packet, and receiving the fourth data packet returned by the server.
In another embodiment, the protocol conversion program may be deployed directly on the network element, and based on this, in the step 102, obtaining the second data packet obtained by performing protocol conversion on the first data packet includes: and carrying out protocol conversion on the first data packet through a locally configured protocol conversion program so as to obtain the second data packet.
Similarly, in step 103, obtaining the fourth packet obtained by performing protocol conversion on the third packet includes: and carrying out protocol conversion on the third data packet through a protocol conversion program configured locally so as to obtain the fourth data packet.
The method provided by the embodiment of the present application is described above, and the device provided by the embodiment of the present application is described below:
referring to fig. 5, fig. 5 is a block diagram of an apparatus according to an embodiment of the present application. The device is applied to a network element which communicates with an IMS network in a 5G core network, and can comprise:
the receiving processing unit is used for identifying a protocol type supported by the first IMS network if the configured working mode on the local network element is an adaptive mode for the received first data packet from the first IMS network, acquiring a second data packet obtained after the protocol conversion of the first data packet when the protocol type is inconsistent with the protocol type supported by the local network element in the 5G core network, and processing the second data packet when the protocol type is the same as the protocol type supported by the local network element in the 5G core network;
and the sending processing unit is used for identifying the protocol type supported by the second IMS network if the configured working mode on the network element is the self-adaptive mode for the third data packet to be sent to the second IMS network, and when the protocol type is inconsistent with the protocol type supported by the network element in the 5G core network, obtaining a fourth data packet obtained after the protocol conversion of the third data packet, wherein the protocol type to which the fourth data packet belongs is the same as the protocol type supported by the second IMS network, and sending the fourth data packet to the second IMS network.
Optionally, in this embodiment, the receiving processing unit searches the configured IP address-protocol type mapping table for a target IP address-protocol type mapping table item including the source IP address of the first data packet; the target IP address-protocol type mapping table item is a static IP address-protocol type mapping table item preset in the IP address-protocol type mapping table or a dynamic IP address-protocol type mapping table item dynamically added in the IP address-protocol type mapping table; if the target IP address-protocol type mapping table item is found, determining the protocol type in the target IP address-protocol type mapping table item as the protocol type supported by the first IMS network when the target IP address-protocol type mapping table item is a static IP address-protocol type mapping table item; if the target IP address-protocol type mapping table entry is not found, or if the target IP address-protocol type mapping table entry is found and the target IP address-protocol type mapping table entry is a dynamic IP address-protocol type mapping table entry, determining a protocol type to which the source port number belongs according to the source port number of the first data packet, and determining the protocol type to which the source port number belongs as a protocol type supported by the first IMS network.
Optionally, in this embodiment, if the receiving processing unit does not find the target IP address-protocol type mapping table, after determining the protocol type to which the source port number belongs as the protocol type supported by the first IMS network, the method further includes: and adding the corresponding relation between the source IP address of the first data packet and the protocol type of the source port number as a dynamic IP address-protocol type mapping table item to the configured IP address-protocol type mapping table.
Optionally, in this embodiment, if the receiving processing unit finds a target IP address-protocol type mapping table, but the target IP address-protocol type mapping table is a dynamic IP address-protocol type mapping table, after determining that the protocol type to which the source port number belongs is the protocol type supported by the first IMS network, the method further includes: and updating the target IP address-protocol type mapping table, wherein the updated IP address-protocol type mapping table is a dynamic IP address-protocol type mapping table which contains the corresponding relation between the source IP address of the first data packet and the protocol type to which the source port number belongs.
Optionally, in this embodiment, if the configured working mode on the local network element is a conversion mode, the receiving processing unit further obtains a second data packet obtained after performing protocol conversion on the first data packet, where a protocol type to which the second data packet belongs is the same as a protocol type supported by the local network element in the 5G core network;
if the configured working mode on the local network element is a non-conversion mode, the non-conversion mode is used for indicating that the protocol type supported by the first IMS network is the same as the protocol type supported by the local network element in the 5G core network; the method further comprises: and processing the first data packet.
Optionally, in this embodiment, the network element locally configures a protocol conversion program, and the obtaining a second data packet obtained by performing protocol conversion on the first data packet includes: and carrying out protocol conversion on the first data packet through a locally configured protocol conversion program so as to obtain a second data packet.
Optionally, in this embodiment, if the network element is not locally configured with a protocol conversion program, the obtaining the second data packet obtained by performing protocol conversion on the first data packet includes: and forwarding the first data packet to a server with a deployed protocol conversion program in the 5G core network, so that the server carries out protocol conversion on the first data packet through the configured protocol conversion program to obtain a second data packet, and receiving the second data packet returned by the server.
Optionally, in this embodiment, the identifying, by the sending processing unit, a protocol type supported by the second IMS network includes: searching a destination IP address of the third data packet in a configured IP address-protocol type mapping table; the IP address-protocol type mapping table is used for recording the corresponding relation between the IP address in the IMS network and the protocol type supported by the IMS network, and if the corresponding relation is found, the protocol type corresponding to the target IP address is determined to be the protocol type supported by the second IMS network.
Optionally, in this embodiment, if the configured working mode on the local network element is a conversion mode, the sending processing unit further obtains a fourth data packet obtained by performing protocol conversion on the third data packet.
And if the configured working mode on the local network element is a non-conversion mode, wherein the non-conversion mode is used for indicating that the protocol type supported by the second IMS network is the same as the protocol type supported by the local network element in the 5G core network, and the sending processing unit sends the third data packet to the second IMS network.
Optionally, as an embodiment, the network element is not configured with a protocol conversion procedure locally; the sending processing unit obtaining a fourth data packet obtained by performing protocol conversion on the third data packet includes: and carrying out protocol conversion on the third data packet through a locally configured protocol conversion program to obtain a fourth data packet.
Optionally, as an embodiment, the network element is not configured with a protocol conversion procedure locally; based on this, the transmission processing unit obtaining a fourth data packet obtained by performing protocol conversion on the third data packet includes: and forwarding the third data packet to a server with a deployed protocol conversion program in the 5G core network, so that the server performs protocol conversion on the third data packet through the configured protocol conversion program to obtain a fourth data packet, and receiving the fourth data packet returned by the server.
The structural description of the apparatus shown in fig. 5 is thus completed.
The embodiment of the application also provides a hardware structure of the device shown in fig. 5. Referring to fig. 6, fig. 6 is a block diagram of an electronic device according to an embodiment of the present application. As shown in fig. 6, the hardware structure may include: a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor; the processor is configured to execute the machine-executable instructions to implement the methods disclosed in the above examples of the present application.
Based on the same application concept as the above method, the embodiments of the present application further provide a machine-readable storage medium, where a number of computer instructions are stored, where the computer instructions can implement the method disclosed in the above example of the present application when executed by a processor.
By way of example, the machine-readable storage medium may be any electronic, magnetic, optical, or other physical storage device that can contain or store information, such as executable instructions, data, and the like. For example, a machine-readable storage medium may be: RAM (Radom Access Memory, random access memory), volatile memory, non-volatile memory, flash memory, a storage drive (e.g., hard drive), a solid state drive, any type of storage disk (e.g., optical disk, dvd, etc.), or a similar storage medium, or a combination thereof.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of each element may be implemented in one or more software and/or hardware elements when implemented in the present application.
It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Moreover, these computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and changes may be made to the present application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. which are within the spirit and principles of the present application are intended to be included within the scope of the claims of the present application.

Claims (9)

1. An interaction method of a 5G core network and an IMS network, wherein the method is applied to a network element in the 5G core network that communicates with the IMS network, the method comprising:
for a received first data packet from a first IMS network, if a configured working mode on a local network element is an adaptive mode, identifying a protocol type supported by the first IMS network, and when the protocol type is inconsistent with the protocol type supported by the local network element in the 5G core network, obtaining a second data packet obtained after protocol conversion of the first data packet, wherein the protocol type of the second data packet is the same as the protocol type supported by the local network element in the 5G core network, and processing the second data packet;
for a third data packet to be sent to a second IMS network, if the configured working mode on the local network element is an adaptive mode, identifying a protocol type supported by the second IMS network, and when the protocol type is inconsistent with the protocol type supported by the local network element in the 5G core network, obtaining a fourth data packet obtained after carrying out protocol conversion on the third data packet, wherein the protocol type to which the fourth data packet belongs is the same as the protocol type supported by the second IMS network, and sending the fourth data packet to the second IMS network;
The identifying the protocol type supported by the first IMS network includes:
searching a target IP address-protocol type mapping table item containing the source IP address of the first data packet in a configured IP address-protocol type mapping table; the target IP address-protocol type mapping table item is a static IP address-protocol type mapping table item preset in the IP address-protocol type mapping table or a dynamic IP address-protocol type mapping table item dynamically added in the IP address-protocol type mapping table;
if the target IP address-protocol type mapping table item is found and the target IP address-protocol type mapping table item is a static IP address-protocol type mapping table item, determining a protocol type corresponding to the source IP address in the target IP address-protocol type mapping table item as a protocol type supported by the first IMS network;
if the target IP address-protocol type mapping table entry is not found, or if the target IP address-protocol type mapping table entry is found and the target IP address-protocol type mapping table entry is a dynamic IP address-protocol type mapping table entry, determining a protocol type to which the source port number belongs according to the source port number of the first data packet, and determining the protocol type to which the source port number belongs as a protocol type supported by the first IMS network.
2. The method according to claim 1, wherein if the target IP address-protocol type mapping table entry is not found, after determining the protocol type to which the source port number belongs as the protocol type supported by the first IMS network, the method further comprises:
adding a corresponding relation between a source IP address of the first data packet and a protocol type to which the source port number belongs as a dynamic IP address-protocol type mapping table item to the configured IP address-protocol type mapping table;
if a target IP address-protocol type mapping table entry is found and the target IP address-protocol type mapping table entry is a dynamic IP address-protocol type mapping table entry, after determining that the protocol type to which the source port number belongs is the protocol type supported by the first IMS network, the method further includes:
updating the target IP address-protocol type mapping table, wherein the updated IP address-protocol type mapping table is a dynamic IP address-protocol type mapping table which contains the corresponding relation between the source IP address of the first data packet and the protocol type to which the source port number belongs; each dynamic IP address-protocol type mapping table entry is valid for a valid time and can be dynamically deleted when the valid time is exceeded; updating the target IP address protocol type mapping table item, resetting the effective time of the target IP address protocol type mapping table item, and maintaining the updated IP address protocol type mapping table item to be effective in a longer effective time.
3. The method of claim 1, wherein if the configured operating mode on the home network element is a transition mode, the method further comprises:
obtaining a second data packet obtained after the protocol conversion of the first data packet, wherein the protocol type of the second data packet is the same as the protocol type supported by the local network element in the 5G core network; or obtaining a fourth data packet obtained after the third data packet is subjected to protocol conversion;
if the configured working mode on the local network element is a non-conversion mode, the non-conversion mode is used for indicating that the protocol types supported by the first IMS network and the second IMS network are the same as the protocol types supported by the local network element on the 5G core network; the method further comprises:
processing the first data packet; or sending the third data packet to the second IMS network.
4. The method according to claim 1 or 2, wherein the network element locally configures a protocol conversion procedure, and the obtaining the second data packet obtained by performing protocol conversion on the first data packet includes:
performing protocol conversion on the first data packet through a locally configured protocol conversion program to obtain a second data packet; or alternatively, the process may be performed,
The network element is not configured with a protocol conversion program locally, and the obtaining the second data packet obtained by performing protocol conversion on the first data packet includes:
forwarding the first data packet to a server with a deployed protocol conversion program in the 5G core network, so that the server performs protocol conversion on the first data packet through the configured protocol conversion program to obtain a second data packet;
and receiving the second data packet returned by the server.
5. The method of claim 1, wherein the identifying the protocol type supported by the second IMS network comprises:
searching a destination IP address of the third data packet in a configured IP address-protocol type mapping table; the IP address-protocol type mapping table is used for recording the corresponding relation between the IP address in the IMS network and the protocol type supported by the IMS network;
if so, determining the protocol type corresponding to the destination IP address as the protocol type supported by the second IMS network.
6. A method according to claim 1 or 2, characterized in that,
the network element locally configures a protocol conversion program, and the obtaining a fourth data packet obtained after the third data packet is subjected to protocol conversion includes:
Performing protocol conversion on the third data packet through a locally configured protocol conversion program to obtain a fourth data packet; or alternatively, the process may be performed,
the network element is not configured with a protocol conversion program locally, and the obtaining the fourth data packet obtained by performing protocol conversion on the third data packet includes:
forwarding the third data packet to a server with a deployed protocol conversion program in the 5G core network, so that the server performs protocol conversion on the third data packet through the configured protocol conversion program to obtain a fourth data packet;
and receiving the fourth data packet returned by the server.
7. An interaction device for a 5G core network and an IMS network, wherein the device is applied to a network element in the 5G core network that communicates with the IMS network, and the device comprises:
a receiving and processing unit, configured to identify a protocol type supported by a first IMS network if a configured working mode on a local network element is an adaptive mode for a received first data packet from the first IMS network, and obtain a second data packet obtained after performing protocol conversion on the first data packet when the protocol type is inconsistent with a protocol type supported by the local network element in the 5G core network, where the protocol type to which the second data packet belongs is the same as the protocol type supported by the local network element in the 5G core network, and process the second data packet;
A sending processing unit, configured to identify a protocol type supported by a second IMS network if a configured working mode on a local network element is an adaptive mode for a third data packet to be sent to the second IMS network, and obtain a fourth data packet obtained after performing protocol conversion on the third data packet when the protocol type is inconsistent with the protocol type supported by the local network element in the 5G core network, where the protocol type to which the fourth data packet belongs is the same as the protocol type supported by the second IMS network, and send the fourth data packet to the second IMS network;
the receiving processing unit identifying a protocol type supported by the first IMS network includes: searching a target IP address-protocol type mapping table item containing the source IP address of the first data packet in a configured IP address-protocol type mapping table; the target IP address-protocol type mapping table item is a static IP address-protocol type mapping table item preset in the IP address-protocol type mapping table or a dynamic IP address-protocol type mapping table item dynamically added in the IP address-protocol type mapping table;
if the target IP address-protocol type mapping table item is found, determining the protocol type in the target IP address-protocol type mapping table item as the protocol type supported by the first IMS network when the target IP address-protocol type mapping table item is a static IP address-protocol type mapping table item;
If the target IP address-protocol type mapping table item is not found, or the target IP address-protocol type mapping table item is found and is a dynamic IP address-protocol type mapping table item, determining the protocol type to which the source port number belongs according to the source port number of the first data packet, and determining the protocol type to which the source port number belongs as the protocol type supported by the first IMS network;
the identifying, by the sending processing unit, a protocol type supported by the second IMS network includes: searching a destination IP address of the third data packet in a configured IP address-protocol type mapping table; the IP address-protocol type mapping table is used for recording the corresponding relation between the IP address in the IMS network and the protocol type supported by the IMS network, and if the corresponding relation is found, the protocol type corresponding to the target IP address is determined to be the protocol type supported by the second IMS network.
8. The apparatus according to claim 7, wherein the receiving processing unit further adds a correspondence between the source IP address of the first packet and the protocol type to which the source port number belongs as a dynamic IP address-protocol type mapping table item to the configured IP address-protocol type mapping table after determining the protocol type to which the source port number belongs as the protocol type supported by the first IMS network if the target IP address-protocol type mapping table item is not found;
Or if the receiving processing unit finds the target IP address-protocol type mapping table entry and the target IP address-protocol type mapping table entry is a dynamic IP address-protocol type mapping table entry, after determining that the protocol type to which the source port number belongs is the protocol type supported by the first IMS network, further updating the target IP address-protocol type mapping table entry, where the updated IP address-protocol type mapping table entry is a dynamic IP address-protocol type mapping table entry, and includes a correspondence between the source IP address of the first packet and the protocol type to which the source port number belongs.
9. The apparatus of claim 7, wherein the network element locally configures a protocol conversion procedure;
the receiving processing unit obtaining a second data packet obtained by performing protocol conversion on the first data packet comprises the following steps: performing protocol conversion on the first data packet through a locally configured protocol conversion program to obtain a second data packet;
the sending processing unit obtaining a fourth data packet obtained by performing protocol conversion on the third data packet includes: performing protocol conversion on the third data packet through a locally configured protocol conversion program to obtain a fourth data packet;
Or alternatively, the process may be performed,
the network element is not configured with a protocol conversion program locally;
the receiving processing unit obtaining a second data packet obtained by performing protocol conversion on the first data packet comprises the following steps: forwarding the first data packet to a server with a deployed protocol conversion program in the 5G core network, so that the server performs protocol conversion on the first data packet through the configured protocol conversion program to obtain a second data packet, and receiving the second data packet returned by the server;
the sending processing unit obtaining a fourth data packet obtained by performing protocol conversion on the third data packet includes: and forwarding the third data packet to a server with a deployed protocol conversion program in the 5G core network, so that the server performs protocol conversion on the third data packet through the configured protocol conversion program to obtain a fourth data packet, and receiving the fourth data packet returned by the server.
CN202210189209.1A 2022-02-28 2022-02-28 Interaction method and device of 5G core network and IMS network Active CN114553834B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210189209.1A CN114553834B (en) 2022-02-28 2022-02-28 Interaction method and device of 5G core network and IMS network

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210189209.1A CN114553834B (en) 2022-02-28 2022-02-28 Interaction method and device of 5G core network and IMS network

Publications (2)

Publication Number Publication Date
CN114553834A CN114553834A (en) 2022-05-27
CN114553834B true CN114553834B (en) 2023-07-25

Family

ID=81660929

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210189209.1A Active CN114553834B (en) 2022-02-28 2022-02-28 Interaction method and device of 5G core network and IMS network

Country Status (1)

Country Link
CN (1) CN114553834B (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101674297A (en) * 2008-09-12 2010-03-17 中国移动通信集团公司 Distributed business network, core service device and protocol message processing method
CN106332018A (en) * 2015-06-15 2017-01-11 中兴通讯股份有限公司 Method and device for realizing USSD (Unstructured Supplementary Service Data) function in IMS (IP Multimedia Subsystem) network
CN110036664A (en) * 2016-10-07 2019-07-19 瑞典爱立信有限公司 Support the single radio continuous voice call in next-generation (5G) network

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3721674B1 (en) * 2017-12-04 2022-07-13 Telefonaktiebolaget LM Ericsson (publ) Method, computer program, carrier containing the computer program and wireless device for supporting multiple access networks
CN112567711B (en) * 2018-08-10 2023-07-11 联想（新加坡）私人有限公司 Transport layer protocol for SIP messages

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101674297A (en) * 2008-09-12 2010-03-17 中国移动通信集团公司 Distributed business network, core service device and protocol message processing method
CN106332018A (en) * 2015-06-15 2017-01-11 中兴通讯股份有限公司 Method and device for realizing USSD (Unstructured Supplementary Service Data) function in IMS (IP Multimedia Subsystem) network
CN110036664A (en) * 2016-10-07 2019-07-19 瑞典爱立信有限公司 Support the single radio continuous voice call in next-generation (5G) network

Also Published As

Publication number Publication date
CN114553834A (en) 2022-05-27

Similar Documents

Publication Publication Date Title
EP2388956B1 (en) Ascertaining per-hop network characteristics
CN110166570B (en) Service session management method and device, and electronic device
US10103962B1 (en) Return path trace
CN108259347B (en) Message transmission method and device
CN101841520B (en) Domain name system and information processing method and device for domain name system
US8903972B2 (en) Method and apparatus for sharing contents using information of group change in content oriented network environment
CN111225074A (en) Network service system and network service method
CN107580079B (en) Message transmission method and device
CN111064804B (en) Network access method and device
CN107547346B (en) Message transmission method and device
CN108429739B (en) Method, system and terminal equipment for identifying honeypots
CN106464745A (en) Dns server, client and data synchronization method
CN107070719B (en) Equipment management method and device
CN108259348B (en) Message transmission method and device
CN102859970A (en) Values represented as internet protocol addresses
CN113676959A (en) Service flow forwarding method, device and equipment based on 5G core network
CN114553834B (en) Interaction method and device of 5G core network and IMS network
CN108259340B (en) Topology information transmission method and device
CN110929195A (en) Data caching strategy determining method and device and electronic equipment
CN107547382B (en) Neighbor relation discovery method and device
CN111131048A (en) Network traffic forwarding method and device, electronic equipment and machine-readable storage medium
CN108737347B (en) Data communication method, device and equipment
CN110896414B (en) Method for realizing message notification between services by using IOT (Internet of things)
CN114024903A (en) Network switching method and device and gateway equipment
CN103139723A (en) Method and system of processing multimedia message and multimedia information and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant