CN114553834A - 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
CN114553834A
CN114553834A CN202210189209.1A CN202210189209A CN114553834A CN 114553834 A CN114553834 A CN 114553834A CN 202210189209 A CN202210189209 A CN 202210189209A CN 114553834 A CN114553834 A CN 114553834A
Authority
CN
China
Prior art keywords
protocol type
data packet
address
protocol
mapping table
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.)
Granted
Application number
CN202210189209.1A
Other languages
Chinese (zh)
Other versions
CN114553834B (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

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10Architectures or entities
    • H04L65/1016IP multimedia subsystem [IMS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/09Mapping addresses
    • H04L61/25Mapping addresses of the same type
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/02Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08Protocols for interworking; Protocol conversion
    • YGENERAL 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
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE 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/00Reducing energy consumption in communication networks
    • Y02D30/70Reducing energy consumption in communication networks in wireless communication networks

Abstract

The application provides an interaction method and device of a 5G core network and an IMS network. In the present application, the interworking between the 5G core network and the IMS network is achieved without changing the network topology structure by the compatibility processing procedure of the network element on the control plane of the 5G core network to the first data packet received from the first IMS network or the third data packet to be sent to the second IMS network. Further, in this embodiment, when the network element on the control plane of the 5G core network is in interworking with the IMS network without changing the network topology, whether to perform protocol conversion on the data packet is determined according to the configured mode and the packet detection condition, so that the method is highly adaptive and 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 technology, and in particular, to an interaction method and apparatus for a 5G core network and an IP Multimedia Subsystem (IMS) network.
Background
The control plane of the 5G core network adopts a service architecture design, and the HTTP/2 application layer protocol is uniformly adopted. At the control plane of the 5G core network, all the service interfaces may be transmitted on the same bus, which may be understood as a bus communication method.
An IP Multimedia Subsystem (IMS) network is a general network architecture that provides Multimedia services over IP-based networks. At present, how to realize the interaction between the IMS network and the 5G core network is a technical problem to be solved urgently.
Disclosure of Invention
The application provides an interaction method and device of a 5G core network and an IMS network, so as to realize the 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 a network element which communicates 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 network element is an adaptive mode, identifying a protocol type supported by the first IMS network, and when the protocol type is inconsistent with a protocol type supported by the network element in the 5G core network, obtaining a second data packet obtained by performing protocol conversion on the first data packet, wherein the protocol type of the second data packet is the same as the protocol type supported by the 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 a configured working mode on a network element is an adaptive mode, identifying a protocol type supported by the second IMS network, and when the protocol type is not consistent with the protocol type supported by the network element in the 5G core network, obtaining a fourth data packet obtained after performing protocol conversion on the third data packet, wherein the protocol type of the fourth data packet 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 processing unit, configured to, for a received first data packet from a first IMS network, identify a protocol type supported by the first IMS network if a configured working mode on a local network element is an adaptive mode, and when the protocol type is not consistent with a protocol type supported by the local network element in the 5G core network, obtain a second data packet obtained by performing protocol conversion on the first data packet, where a 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 a protocol type supported by the second IMS network if a configured working mode on the network element is an adaptive mode for a third data packet to be sent to the second IMS network, obtaining a fourth data packet obtained after the third data packet is subjected to protocol conversion when the protocol type is not consistent with the protocol type supported by the 5G core network by the network element, and sending the fourth data packet to the second IMS network, wherein the protocol type of the fourth data packet is the same as the protocol type supported by the second IMS network.
The embodiment of the application also provides the 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 implement the steps of the above-disclosed method.
It can be seen from the foregoing technical solutions that, in the present application, the interworking between the 5G core network and the IMS network is implemented without changing a network topology structure through a compatibility processing procedure of a network element on a control plane of the 5G core network to a first data packet received from the first IMS network or a third data packet to be sent to the second IMS network.
Further, in this embodiment, when the network element on the control plane of the 5G core network is in interworking with the IMS network without changing the network topology, whether to perform protocol conversion on the data packet is determined according to the configured mode and the packet detection condition, so that the method is highly adaptive and 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 present disclosure and together with the description, serve to explain the principles of the disclosure.
FIG. 1 is a flow chart of a method provided by an embodiment of the present application;
fig. 2 is a flowchart of identifying a protocol type supported by a first IMS network in step 102 according to 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 according to an embodiment of the present application;
fig. 4 is a schematic networking diagram provided in an embodiment of the present application;
FIG. 5 is a block diagram of an apparatus according to an embodiment of the present disclosure;
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 the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the 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 make the technical solutions provided in the embodiments of the present application better understood and make the above objects, features and advantages of the embodiments of the present application more comprehensible, 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 is simultaneously interconnected and intercommunicated with a control plane of the 5G core network under the condition of not changing the existing network topology. The method provided by the embodiments of the present application is described below:
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 the network element which communicates with the IMS network in the 5G core network. In the 5G core network, network elements such as a Policy Control Function (PCF), a Unified Data Management Function (UDM), and the like may need to interact with the IMS network, that is, the network elements may be network elements (also referred to as required network elements) in the 5G core network, which communicate with the IMS network.
As shown in fig. 1, the process may include the following steps:
step 101, for the first data packet received from the first IMS network, step 102 is executed, and for the third data packet to be sent to the second IMS network, step 103 is executed.
In the present embodiment, the first IMS network generally refers to any IMS network. The first packet is also referred to generically as any packet. They are used for descriptive purposes only and not for purposes of limitation.
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. Or, 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 called a data packet from the IMS network. Here, whether the source IP address of the 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 IP addresses in the IMS network; and if the IP address is found, 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 the present embodiment, the second IMS network generally refers to any IMS network such as the first IMS network described above. The third packet is also referred to generally as any packet. They are used in a generic and descriptive sense only and not for purposes of limitation.
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 packet is an IP address in the IMS network may be determined by: searching a destination IP address of the data packet in a configured IP address table; the IP address table is used for recording IP addresses in the IMS network; and if the IP address is found, determining that the destination IP address of the data packet is 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 network element is the self-adaptive mode, identifying the protocol type supported by the first IMS network, and when the protocol type is not consistent with the protocol type supported by the network element in the 5G core network, obtaining a second data packet obtained by performing protocol conversion on the first data packet, where the protocol type of the second data packet is the same as the protocol type supported by the network element in the 5G core network, and processing the second data packet.
This step 102 is a process for the first data packet received from the first IMS network.
Optionally, in this embodiment, there are many ways to identify the protocol type supported by the first IMS network in this step 102, and fig. 2 illustrates one implementation manner, which is not described herein for the sake of example.
Optionally, in this embodiment, if the configured operating mode on the local network element is not the adaptive mode, for example, a conversion mode, the step 102 further includes: and obtaining the two data packets obtained after the protocol conversion is carried out on the first data packet.
For another example, the configured operation mode on the present network element is not the above-mentioned adaptive mode, for example, a non-conversion mode. The reason why the non-conversion mode is set here is 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, that is, the non-conversion 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 mode is similar to the processing of the data packet by the existing 5G core network, and is not described again.
Optionally, in this embodiment, the protocol type to which the second packet belongs is the same as the protocol type supported by the 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 this 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, both are HTTP/2 protocols, at this time, the first data packet may be directly processed, for example, the first data packet may be sent to the terminal.
Step 103, if the configured working mode on the network element is the self-adaptive mode, identifying a protocol type supported by a second IMS network, and when the protocol type is not consistent with the protocol type supported by the network element in the 5G core network, obtaining a fourth data packet obtained by performing protocol conversion on the third data packet, where the protocol type of the fourth data packet 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 processing for a third 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 this step 103, and fig. 3 illustrates one implementation manner, which is not described herein again for the sake of example.
Optionally, in this embodiment, if the configured operating mode on the local network element is not the adaptive mode, for example, a conversion mode, the step 103 further includes: and obtaining the fourth data packet obtained after the protocol conversion is carried out on the third data packet.
For another example, the configured operation mode on the present network element is not the above-mentioned adaptive mode, for example, a non-conversion mode. The reason why the non-conversion mode is set here is 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, that is, the non-conversion 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 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 network element in the 5G core network may be an HTTP/2 protocol.
Of course, in this 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 are HTTP/2 protocols, at this time, 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 process shown in fig. 1, in this embodiment, the interworking between the 5G core network and the IMS network is realized without changing the network topology through a compatibility processing procedure of a network element on the control plane of the 5G core network to a first data packet received from the first IMS network or a third data packet to be sent to the second IMS network.
Further, in this embodiment, when the network element on the control plane of the 5G core network is in interworking with the IMS network without changing the network topology, whether to perform protocol conversion on the data packet is determined according to the configured mode and the packet detection condition, so that the method is highly adaptive and 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 according to an embodiment of the present application. As shown in fig. 2, the process may include the following steps:
step 201, searching a target IP address-protocol type mapping table item including a source IP address of the first data packet in a configured 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, executing step 202, and if the target IP address-protocol type mapping table item is not found, or if the target IP address-protocol type mapping table item is found and the target IP address-protocol type mapping table item is a dynamic IP address-protocol type mapping table item, executing step 203.
In this embodiment, the IP address-protocol type mapping table entry in the IP address-protocol type mapping table is used to record a corresponding relationship between an IP address in the IMS network and a protocol type supported by the IMS network, and may be specifically subdivided into a preset IP address-protocol type mapping table entry (denoted as a static IP address-protocol type mapping table entry) and an IP address-protocol type mapping table entry (denoted as a dynamic IP address-protocol type mapping table entry) that is dynamically learned and established and is in valid time. The following will specifically describe how to learn and establish the dynamic IP address-protocol type mapping table entry, and details thereof are not repeated herein.
Step 202, determining the protocol type corresponding to the source IP address in the mapping table entry of the target IP address-protocol type as the protocol type supported by the first IMS network.
In this step 202, the 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 executed on the premise that 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.
Step 203 is executed on the premise that the target IP address-protocol type mapping table entry is not found in the configured IP address-protocol type mapping table, or 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, and the like, which corresponds to different port numbers, based on this, this step 203 may identify a protocol type to which the source port number belongs by extracting the source port number of the first packet, and determine the protocol type to which the source port number belongs as a protocol type supported by the first IMS network.
Thus, the flow shown in fig. 2 is completed.
How to identify the protocol type supported by the first IMS network is achieved by the flow shown in fig. 2.
It should be noted that, in this embodiment, if the target IP address-protocol type mapping 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 includes: and taking 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 and adding the dynamic IP address-protocol type mapping table item to the configured IP address-protocol type mapping table. Namely, the dynamic IP address-protocol type mapping table entry 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 always valid during the existence period and cannot update the coverage. And for the dynamically added dynamic IP address-protocol type mapping table entry, corresponding effective time can 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 entry is found and the target IP address-protocol type mapping entry is a dynamic IP address-protocol type mapping entry, 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 updating a target IP address-protocol type mapping table entry, wherein the updated IP address-protocol type mapping table entry is a dynamic IP address-protocol type mapping table entry and contains a corresponding relation between a source IP address of the first data packet and a protocol type to which the source port number belongs. Here, the target IP address-protocol type mapping table entry is updated, and the purpose is to obtain the corresponding protocol type of the same IP in time, which is changed due to the requirement. Of course, updating the target IP address-protocol type mapping table entry also corresponds to resetting the effective time of the target IP address-protocol type mapping table entry, and maintaining the updated IP address-protocol type mapping table entry to be effective in a longer effective 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 according to an embodiment of the present application. As shown in fig. 3, the process may include the following steps:
step 301, the destination IP address of the third data packet is looked up in the configured IP address-protocol type mapping table.
The IP address-protocol type mapping table herein is as 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, which definitely finds the destination IP address of the third packet in the configured IP address-protocol type mapping table without any accident. Of course, in a special case, if the destination IP address of the third packet is not found in the configured IP address-protocol type mapping table, the third packet may be directly sent to the second IMS network.
The flow shown in fig. 3 is completed.
How to identify the type of protocol supported by the second IMS network is achieved by the flow shown in fig. 3.
In this embodiment, the protocol conversion may be performed by a protocol conversion procedure.
In one embodiment, the protocol conversion program may be deployed in 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 shown in fig. 4.
As applied to fig. 4, in the 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 protocol conversion program deployed in a 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.
Similarly, the obtaining of 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 protocol conversion program deployed in a 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.
In another embodiment, a protocol conversion program may also be directly deployed on the network element, and based on this, the obtaining, in step 102, 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 to obtain the second data packet.
Similarly, in step 103, obtaining a fourth data packet obtained by performing protocol conversion on the third data packet includes: and performing protocol conversion on the third data packet through a locally configured protocol conversion program to obtain the fourth data packet.
The method provided by the embodiment of the present application is described above, and the apparatus provided by the embodiment of the present application is described below:
referring to fig. 5, fig. 5 is a structural diagram of an apparatus provided in the 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 the device can comprise:
a receiving and processing unit, configured to, for a received first data packet from a first IMS network, identify a protocol type supported by the first IMS network if a configured working mode on a local network element is an adaptive mode, and when the protocol type is not consistent with a protocol type supported by the local network element in a 5G core network, obtain a second data packet obtained by performing protocol conversion on the first data packet, where a 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, obtaining a fourth data packet obtained after the protocol conversion is carried out on the third data packet when the protocol type is not consistent with the protocol type supported by the 5G core network of the network element, and sending the fourth data packet to the second IMS network, wherein the protocol type of the fourth data packet is the same as the protocol type supported by the second IMS network.
Optionally, in this embodiment, the receiving and processing unit searches a target IP address-protocol type mapping table entry including the source IP address of the first packet in a configured IP address-protocol type mapping table; the target IP address-protocol type mapping table entry is a static IP address-protocol type mapping table entry preset in the IP address-protocol type mapping table or a dynamic IP address-protocol type mapping table entry dynamically added in the IP address-protocol type mapping table; if the target IP address-protocol type mapping table entry is found, determining the protocol type in the target IP address-protocol type mapping table entry as the protocol type supported by the first IMS network when the target IP address-protocol type mapping table entry is a static IP address-protocol type mapping table entry; if the target IP address-protocol type mapping table entry is not found, or 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 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.
Optionally, in this embodiment, if the receiving and processing unit does not find the target IP address-protocol type mapping table entry, 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 to the configured IP address-protocol type mapping table as a dynamic IP address-protocol type mapping table entry.
Optionally, in this embodiment, if the receiving and processing unit finds the target IP address-protocol type mapping table entry, but the target IP address-protocol type mapping table entry is a dynamic IP address-protocol type mapping table entry, 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 updating the target IP address-protocol type mapping table entry, wherein the updated IP address-protocol type mapping table entry is a dynamic IP address-protocol type mapping table entry 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 network element is a conversion mode, the receiving processing unit further obtains a second data packet obtained by performing protocol conversion on the first data packet, where a protocol type of the second data packet is the same as a protocol type supported by the network element in the 5G core network;
if the configured working mode on the 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 network element in the 5G core network; the method further comprises: and processing the first data packet.
Optionally, in this embodiment, the locally configuring, by the network element, a protocol conversion program, where the obtaining of 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 to obtain a second data packet.
Optionally, in this embodiment, if the network element is not configured with a protocol conversion program locally, the obtaining a 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 protocol conversion program deployed 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.
Optionally, in this embodiment, the identifying, by the sending processing unit, the 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 to record a corresponding relationship between an IP address in the IMS network and a protocol type supported by the IMS network, and if found, determine the protocol type corresponding to the destination IP address as 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 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 network element in the 5G core network, 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 program locally; the obtaining, by the sending processing unit, 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 program locally; based on this, the obtaining, by the sending processing unit, the fourth packet obtained by performing protocol conversion on the third packet includes: and forwarding the third data packet to a server with a protocol conversion program deployed 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.
Thus, the description of the structure of the apparatus shown in fig. 5 is 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 structural 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 having stored thereon machine-executable instructions executable by the processor; the processor is configured to execute machine-executable instructions to implement the methods disclosed in the above examples of the present application.
Based on the same application concept as the method, embodiments of the present application further provide a machine-readable storage medium, where several computer instructions are stored, and when the computer instructions are executed by a processor, the method disclosed in the above example of the present application can be implemented.
The machine-readable storage medium may be, for example, 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, the machine-readable storage medium may be: a RAM (random Access Memory), a volatile Memory, a non-volatile Memory, a flash Memory, a storage drive (e.g., a hard drive), a solid state drive, any type of storage disk (e.g., an optical disk, a dvd, etc.), or similar storage medium, or a combination thereof.
The systems, apparatuses, modules or units described in the above embodiments may be specifically implemented by a computer chip or an entity, or implemented by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging 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 divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.
As will be appreciated by one skilled in the art, 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 embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) 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.
Furthermore, 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 above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims (11)

1. An interaction method between a 5G core network and an IMS network is characterized in that the method is applied to a network element which communicates with the IMS network in the 5G core network, and the method comprises the following steps:
for a received first data packet from a first IMS network, if a configured working mode on a network element is an adaptive mode, identifying a protocol type supported by the first IMS network, and when the protocol type is not consistent with a protocol type supported by the network element in a 5G core network, obtaining a second data packet obtained by performing protocol conversion on the first data packet, wherein the protocol type of the second data packet is the same as the protocol type supported by the 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 a configured working mode on a network element is an adaptive mode, identifying a protocol type supported by the second IMS network, and when the protocol type is not consistent with the protocol type supported by the network element in the 5G core network, obtaining a fourth data packet obtained after performing protocol conversion on the third data packet, wherein the protocol type of the fourth data packet is the same as the protocol type supported by the second IMS network, and sending the fourth data packet to the second IMS network.
2. The method of claim 1, wherein the identifying the protocol types supported by the first IMS network comprises:
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 entry is a static IP address-protocol type mapping table entry preset in the IP address-protocol type mapping table or a dynamic IP address-protocol type mapping table entry dynamically added in the IP address-protocol type mapping table;
if the target IP address-protocol type mapping table entry is found and is a static IP address-protocol type mapping table entry, determining a protocol type corresponding to the source IP address in the target IP address-protocol type mapping table entry as a protocol type supported by the first IMS network;
if the target IP address-protocol type mapping table entry is not found, or 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 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.
3. The method of claim 2, wherein if no target IP address-protocol type mapping entry is 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 the corresponding relation between the source IP address of the first data packet and the protocol type to which the source port number belongs to the configured IP address-protocol type mapping table as a dynamic IP address-protocol type mapping table entry;
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 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 updating the target IP address-protocol type mapping table entry, wherein the updated IP address-protocol type mapping table entry is a dynamic IP address-protocol type mapping table entry 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.
4. The method of claim 1, wherein if the configured operation mode of the local network element is the transition mode, the method further comprises:
obtaining a second data packet obtained after the protocol conversion is carried out on the first data packet, wherein the protocol type of the second data packet is the same as the protocol type supported by the network element in the 5G core network; or, obtaining a fourth data packet obtained by performing protocol conversion on the third data packet;
if the configured working mode on the 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 network element in the 5G core network; the method further comprises:
processing the first data packet; or, sending the third data packet to the second IMS network.
5. The method according to claim 1 or 3, wherein the network element locally configures a protocol conversion program, and the obtaining the second data packet obtained by performing protocol conversion on the first data packet comprises:
performing protocol conversion on the first data packet through a locally configured protocol conversion program to obtain a second data packet; alternatively, the first and second electrodes may be,
the network element is not configured with a protocol conversion program locally, and the obtaining of 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 protocol conversion program deployed 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.
6. 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 the IP address is found, determining the protocol type corresponding to the destination IP address as the protocol type supported by the second IMS network.
7. The method according to claim 1 or 3,
the network element locally configures a protocol conversion program, and the obtaining of the 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; alternatively, the first and second electrodes may be,
the obtaining of the fourth data packet obtained by performing protocol conversion on the third data packet includes:
forwarding the third data packet to a server deployed with a 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.
8. An interaction device between a 5G core network and an IMS network, wherein the device is applied to a network element in the 5G core network, the network element communicating with the IMS network, and the device comprises:
a receiving processing unit, configured to, for a received first data packet from a first IMS network, identify a protocol type supported by the first IMS network if a configured working mode on a local network element is an adaptive mode, and when the protocol type is not consistent with a protocol type supported by the local network element in the 5G core network, obtain a second data packet obtained by performing protocol conversion on the first data packet, where a 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 a protocol type supported by the second IMS network if a configured working mode on the network element is an adaptive mode for a third data packet to be sent to the second IMS network, obtaining a fourth data packet obtained after the third data packet is subjected to protocol conversion when the protocol type is not consistent with the protocol type supported by the 5G core network by the network element, and sending the fourth data packet to the second IMS network, wherein the protocol type of the fourth data packet is the same as the protocol type supported by the second IMS network.
9. The apparatus of claim 8, wherein the receiving processing unit identifying the protocol type supported by the first IMS network comprises: 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 entry is a static IP address-protocol type mapping table entry preset in the IP address-protocol type mapping table or a dynamic IP address-protocol type mapping table entry dynamically added in the IP address-protocol type mapping table;
if the target IP address-protocol type mapping table entry is found, determining the protocol type in the target IP address-protocol type mapping table entry as the protocol type supported by the first IMS network when the target IP address-protocol type mapping table entry is a static IP address-protocol type mapping table entry;
if the target IP address-protocol type mapping table entry is not found, or the target IP address-protocol type mapping table entry is found and is a dynamic IP address-protocol type mapping table entry, 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;
the identification of the protocol type supported by the second IMS network by the sending processing unit 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 to record a corresponding relationship between an IP address in the IMS network and a protocol type supported by the IMS network, and if found, determine the protocol type corresponding to the destination IP address as the protocol type supported by the second IMS network.
10. The apparatus according to claim 9, wherein if the target IP address-protocol type mapping table entry is not found, the receiving processing unit further adds, as a dynamic IP address-protocol type mapping table entry, a correspondence between the source IP address of the first packet and the protocol type of the source port number to the configured IP address-protocol type mapping table after determining the protocol type of the source port number as the protocol type supported by the first IMS network;
or, if the receiving and processing unit finds a 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 the protocol type to which the source port number belongs as the protocol type supported by the first IMS network, the receiving and processing unit further updates 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.
11. The apparatus of claim 8, wherein the network element configures a protocol conversion procedure locally;
the receiving and processing unit obtaining a 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;
the obtaining, by the sending processing unit, 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;
alternatively, the first and second electrodes may be,
the network element is not configured with a protocol conversion program locally;
the receiving and processing unit obtaining a second data packet obtained by performing protocol conversion on the first data packet includes: forwarding the first data packet to a server with a protocol conversion program deployed 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 obtaining, by the sending processing unit, 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 protocol conversion program deployed 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 true CN114553834A (en) 2022-05-27
CN114553834B 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 (5)

* 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
US20200053133A1 (en) * 2018-08-10 2020-02-13 Lenovo (Singapore) Pte. Ltd. Transport layer protocol for sip message
US20200305211A1 (en) * 2017-12-04 2020-09-24 Telefonaktiebolaget Lm Ericsson (Publ) System and methods for ims session continuity across 4g and 5g networks

Patent Citations (5)

* 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
US20200305211A1 (en) * 2017-12-04 2020-09-24 Telefonaktiebolaget Lm Ericsson (Publ) System and methods for ims session continuity across 4g and 5g networks
US20200053133A1 (en) * 2018-08-10 2020-02-13 Lenovo (Singapore) Pte. Ltd. Transport layer protocol for sip message

Also Published As

Publication number Publication date
CN114553834B (en) 2023-07-25

Similar Documents

Publication Publication Date Title
EP3739826B1 (en) Communication method, system and apparatus
CN106789526B (en) method and device for connecting multiple system networks
CN108924274B (en) Domain name system DNS processing method and device, storage medium and electronic equipment
CN106664560A (en) Network capacity information acquisition method and device
US20150088995A1 (en) Method and apparatus for sharing contents using information of group change in content oriented network environment
CN111064804B (en) Network access method and device
CN107547346B (en) Message transmission method and device
EP3185598B1 (en) Application registration method and apparatus
CN112491941A (en) Data management method, related product and communication system
CN107070719B (en) Equipment management method and device
CN114363963A (en) Load balancing selection method and system for cloud-native UPF signaling plane
CN114500633B (en) Data forwarding method, related device, program product and data transmission system
CN104754544A (en) International network registration method, device and system
CN111010362B (en) Monitoring method and device for abnormal host
CN110830984B (en) Method, device, equipment and storage medium for routing QoS acceleration request message
CN107547382B (en) Neighbor relation discovery method and device
CN114553834B (en) Interaction method and device of 5G core network and IMS network
CN114157639B (en) Method, device and equipment for collecting information of intelligent network card of server and readable medium
CN108628864B (en) Data access method and data management device
CN110896414B (en) Method for realizing message notification between services by using IOT (Internet of things)
CN108259340B (en) Topology information transmission method and device
CN110896378B (en) Network traffic forwarding method and device, electronic equipment and machine-readable storage medium
CN114024903A (en) Network switching method and device and gateway equipment
CN112702361A (en) Safety blocking method, device and equipment based on lightweight distributed cooperative equipment
CN110855764A (en) Network traffic scheduling method and device and electronic equipment

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