CN110996372A

CN110996372A - Message routing method, device and system and electronic equipment

Info

Publication number: CN110996372A
Application number: CN201911092988.8A
Authority: CN
Inventors: 苏国章; 吕东; 姚和良
Original assignee: Guangzhou Aipu Road Network Technology Co Ltd
Current assignee: Guangzhou Aipu Road Network Technology Co Ltd
Priority date: 2019-11-11
Filing date: 2019-11-11
Publication date: 2020-04-10
Anticipated expiration: 2039-11-11
Also published as: CN110996372B

Abstract

The embodiment of the disclosure provides a message routing method, a device, a system and an electronic device, belonging to the technical field of communication, wherein the method comprises the following steps: the method comprises the following steps: receiving a message sent by at least one sender network element of a control plane; analyzing the routing information carried by the message; determining a corresponding routing strategy according to the routing information; matching a receiver network element for receiving the message according to the routing strategy; forwarding the message to the recipient network element. By the scheme disclosed by the invention, routing distribution is carried out on the Http2 request messages between the control plane network functions NFs, the core network control plane network function NFs is effectively shielded, the connection complexity between the control plane network functions NFs inside the core network is simplified, the network architecture and the communication mode of the control plane are optimized, the singleness of the traditional NFs communication is avoided, meanwhile, the external Http2 protocol interface of NFs is shielded, and the flexibility and the safety of the control plane network function communication are improved.

Description

Message routing method, device and system and electronic equipment

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a message routing method, apparatus, system, and electronic device.

Background

In the 5G core Network architecture, based on the purpose of separating the control plane from the user plane, on the basis of the 4G core Network architecture, Network element functions are subdivided, and new Network functions (Network functions, NF for short) are evolved. Nfs (network function service) of the control plane mainly includes: AMF, access and mobility management function entity; SMF, session management function entity; AF, application function entity; NSSF, network slice selection function; NEF, network open function entity; NRF, network warehousing function entity; PCF, policy control function entity; AUSF, authentication server function entity; UDM, unified data management entity.

According to the version R15 of the 3GPP protocol, in a 5G Service Based Architecture (SBA), the network function NFs of the control plane implements a Service Based Interface (SBI). In order to meet the requirements of virtualization and microservice, an SBI interface adopts a TCP (transmission control protocol) protocol in a transmission layer, an Http/2.0 protocol in an application layer, Json in the aspect of a serialization protocol and OpenAPI3.0 in an interface description language.

The control plane network functions NFs communicate through a unified service interface SBI, each NF may provide services to or request services from other NFs. NFs communicate between them through request and response and subscription and notification. There may be one or more instances (NF instances) per NF, and one or more service instances (NFservice instances) per NF instance. Each NF Service (NF Service) should be accessed through interfaces, each interface containing one or more Operations (Operations).

Because NF may instantiate multiple instances, each of which supports the same or different services, the number of connections established when instances of different types NFs communicate with each other is very large, and the connection path is complicated. The NF server side of each communication between the NFs is fixed, cannot be flexibly adjusted, and can only initiate requests to other NFs again. The NF client sends an Http2 request message according to the IP address of the NF server; and the NF server returns an Http2 response message according to the IP address of the NF client.

The Http2 protocol defines flows, which are independent bi-directional sequences for data exchange within Http2 connections, i.e., interactive processing units for a complete flow of resource requests and data responses. One Http2 connection can hold multiple open streams simultaneously; a stream can be created and used by a client or a server, either individually or in a shared manner; the streams are logically parallel and independent. Each stream has a separate identifier, between 1 and 2^ 32-1.

Therefore, in the current 5G core network service-based architecture, the communication method between the control plane network functions NFs has the problem that firstly, the communication method between the control plane network functions NFs is point-to-point communication, which makes the flexibility of communication between them poor; secondly, the connection between NFs is complicated, and the transmitted request and response may reveal the information of the receiver NF.

Disclosure of Invention

In view of this, embodiments of the present disclosure provide a message routing method, device, system and electronic device, which at least partially solve the problems in the prior art.

In a first aspect, an embodiment of the present disclosure provides a message routing method, where the method includes:

receiving a message sent by at least one sender network element of a control plane;

analyzing the routing information carried by the message;

determining a corresponding routing strategy according to the routing information;

matching a receiver network element for receiving the message according to the routing strategy;

forwarding the message to the recipient network element.

According to a specific implementation manner of the embodiment of the present disclosure, the step of receiving the message sent by the control plane NFs is:

receiving a message sent by at least one sender network element in the same core network; alternatively, the first and second electrodes may be,

and receiving a message sent by at least one sender network element in different core networks.

According to a specific implementation manner of the embodiment of the present disclosure, the message is a request message;

the step of matching a receiver network element for receiving the message according to the routing policy comprises:

according to the identification information in the routing information, at least one receiver network element which is the same as the identification information is matched in a routing configuration table to obtain a matching table containing at least one receiver network element list;

and matching at least one receiver network element of which the limiting information in the routing configuration table contains or is equal to the limiting information in the routing information according to the list of the receiver network elements obtained by the matching table.

According to a specific implementation manner of the embodiment of the present disclosure, the step of matching, according to the routing policy, a receiver network element for receiving the message includes:

and matching out one receiver network element for receiving the request message from at least one receiver network element capable of receiving the request message according to the auxiliary information in the routing information.

According to a specific implementation manner of the embodiment of the present disclosure, the step of matching out one receiver network element that receives the request message among at least one receiver network element that can receive the request message according to the auxiliary information in the routing information includes any one of the following steps:

matching a network element with an address position closest to the sender network element according to the auxiliary information, wherein the network element is a receiver network element for receiving the message;

determining the network element with the minimum load degree as a receiver network element for receiving the request message according to the auxiliary information;

and matching the network element in the same slice as the network element of the sender according to the auxiliary information to be a network element of a receiver for receiving the request message.

According to a specific implementation manner of the embodiment of the present disclosure, the message is a response message;

matching at least one request message received by the sender network element according to the identification information of the sender network element carried in the response message;

and taking the sender network element corresponding to the matched request message as a receiver network element for receiving the response message, and forwarding the response message to the receiver network element.

According to a specific implementation manner of the embodiment of the present disclosure, the step of matching at least one request message received by the sender network element according to the identification information of the sender network element carried in the response message includes:

matching at least one request message with the same type of a network element of a receiving party and the type of a network element of a sending party in the routing information in all request messages of a routing information table to obtain a matched first request message list;

matching at least one request message with the same IP address of the network element of the receiving party in the first request message list and the IP address of the network element of the sending party in the routing information to obtain a matched second request message list;

matching out the request message which is identical to the message flow identification of the response message in the second request message list.

According to a specific implementation manner of the embodiment of the present disclosure, the routing information includes at least one of the following items:

the type of the network element of the receiving party, the service requested by the message, the carried IMSI number and the priority of the message.

In a second aspect, the disclosed embodiments provide a routing apparatus configured with an SBI interface, the apparatus comprising:

the receiving module is used for receiving messages sent by at least one sender network element of the control plane;

the analysis module is used for analyzing the routing information carried by the message;

the strategy module is used for determining a corresponding routing strategy according to the routing information;

a matching module, configured to match, according to the routing policy, a receiver network element for receiving the message;

and the forwarding module is used for forwarding the message to the receiving network element.

According to a specific implementation manner of the embodiment of the present disclosure, the routing apparatus is configured with identification information, restriction information, and auxiliary information of the core network control plane network function NFs; the configured identification information includes: NF type, NF instance number, IP address; the configured restriction information includes: service supported by NF, NF priority, IMSI range and NF load degree; the configured auxiliary information includes load of the NF, geographical location of the NF, NF slice information.

According to a specific implementation manner of the embodiment of the present disclosure, the routing device is configured with a routing policy, the routing policy is implemented based on an established routing table, the routing table includes a routing configuration table and a routing information table, and the routing information table includes the following information:

the message type, the sender NF type, the IP address of the sender NF, the identifier of the message flow sent by the sender NF to the routing device, the receiver NF type, the IP address of the receiver NF and the identifier of the message flow forwarded by the routing device to the receiver NF.

In a third aspect, an embodiment of the present disclosure further provides a message routing system, where the system includes at least two network elements and a routing device that performs routing distribution processing on a message between the at least two network elements, where the network elements include a sender network element used for sending the message and a receiver network element used for receiving the message, and the routing device includes:

In a fourth aspect, an embodiment of the present disclosure further provides an electronic device, where the electronic device includes:

at least one processor; and the number of the first and second groups,

a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the message routing method of the first aspect or any implementation manner of the first aspect.

In a fifth aspect, the disclosed embodiments also provide a non-transitory computer-readable storage medium storing computer instructions for causing a computer to perform the message routing method in the first aspect or any implementation manner of the first aspect.

In a sixth aspect, the disclosed embodiments also provide a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions that, when executed by a computer, cause the computer to perform the message routing method of the first aspect or any of the implementations of the first aspect.

The message routing method in the embodiment of the disclosure comprises the following steps: receiving a message sent by at least one sender network element of a control plane; analyzing the routing information carried by the message; determining a corresponding routing strategy according to the routing information; matching a receiver network element for receiving the message according to the routing strategy; forwarding the message to the recipient network element. By the scheme disclosed by the invention, routing distribution is carried out on the Http2 request messages between the control plane network functions NFs, the core network control plane network function NFs is effectively shielded, the connection complexity between the control plane network functions NFs inside the core network is simplified, the network architecture and the communication mode of the control plane are optimized, the singleness of the traditional NFs communication is avoided, meanwhile, the external Http2 protocol interface of NFs is shielded, and the flexibility and the safety of the control plane network function communication are improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings needed to be used in the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present disclosure, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a schematic flowchart of a message routing method according to an embodiment of the present disclosure;

fig. 2 is a flowchart of an Http outer device routing Http2 request message in the same core network according to an embodiment of the present disclosure;

fig. 3 is a flowchart of an Http outer device routing Http2 request message in different core networks according to an embodiment of the present disclosure;

fig. 4 is a flow chart of an Http outlet device routing Http2 response message provided by an embodiment of the present disclosure;

fig. 5 is a schematic flow chart of another message routing method according to an embodiment of the present disclosure;

fig. 6 is a schematic flow chart of another message routing method according to an embodiment of the present disclosure;

fig. 7 is a diagram of an example of routing of an Http2 request message according to an embodiment of the present disclosure;

fig. 8 is a diagram of an example of routing of an Http2 response message according to an embodiment of the present disclosure;

fig. 9 is a schematic structural diagram of a routing device according to an embodiment of the present disclosure;

fig. 10 is a schematic diagram of routing distribution of an http outer device according to an embodiment of the present disclosure;

fig. 11 is a core network networking architecture diagram with an http outlet device added according to an embodiment of the present disclosure;

fig. 12 is a schematic view of an electronic device provided in an embodiment of the disclosure.

Detailed Description

The embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.

The embodiments of the present disclosure are described below with specific examples, and other advantages and effects of the present disclosure will be readily apparent to those skilled in the art from the disclosure in the specification. It is to be understood that the described embodiments are merely illustrative of some, and not restrictive, of the embodiments of the disclosure. The disclosure may be embodied or carried out in various other specific embodiments, and various modifications and changes may be made in the details within the description without departing from the spirit of the disclosure. It is to be noted that the features in the following embodiments and examples may be combined with each other without conflict. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.

It is noted that various aspects of the embodiments are described below within the scope of the appended claims. It should be apparent that the aspects described herein may be embodied in a wide variety of forms and that any specific structure and/or function described herein is merely illustrative. Based on the disclosure, one skilled in the art should appreciate that one aspect described herein may be implemented independently of any other aspects and that two or more of these aspects may be combined in various ways. For example, an apparatus may be implemented and/or a method practiced using any number of the aspects set forth herein. Additionally, such an apparatus may be implemented and/or such a method may be practiced using other structure and/or functionality in addition to one or more of the aspects set forth herein.

It should be noted that the drawings provided in the following embodiments are only for illustrating the basic idea of the present disclosure, and the drawings only show the components related to the present disclosure rather than the number, shape and size of the components in actual implementation, and the type, amount and ratio of the components in actual implementation may be changed arbitrarily, and the layout of the components may be more complicated.

In addition, in the following description, specific details are provided to facilitate a thorough understanding of the examples. However, it will be understood by those skilled in the art that the aspects may be practiced without these specific details.

The embodiment of the disclosure provides a message routing method. The message routing method provided by the embodiment can be executed by a computing device, the computing device can be implemented as software, or implemented as a combination of software and hardware, and the computing device can be integrated in a server, a terminal device and the like.

Referring to fig. 1, a message routing method provided in an embodiment of the present disclosure includes:

s101, receiving a message sent by at least one sender network element of a control plane.

The message routing method of the embodiment of the present invention is applied to a 5G core network architecture, and it should be noted that, for convenience of description, in the description of the message routing method of the embodiment of the present invention, control plane network functions NF and NFs are both described by using network elements. That is, the message sent by the receiving network element and the message sent by the forwarding network element described in the embodiment of the present invention both represent the transmission of messages between NFs in the middle 5G core network structure, including the transmission of messages between network functions such as AMF, SMF, AF, NSSF, and NEF.

The message transmitted in the message routing method of the embodiment of the invention is an Http2 message, a routing device Http outer is additionally arranged in a transmission path of the message, and the Http outer receives the messages transmitted by all network elements and distributes and transmits the received messages according to the set rules. Specifically, when the http outlet device is deployed, the http outlet device needs to register with an NRF of the core network to which the http outlet device belongs, and the NRF stores some identification information such as an IP address of the http outlet. In addition, the identifier information, the restriction information, and the auxiliary information of all the network functions NFs belonging to the core network control plane are configured in the http outer apparatus and recorded in the routing configuration table.

The configured identification information includes, but is not limited to, the following: NF type (NF _ type), NF instance number (NF _ num), IP address (IP _ address);

the configured restriction information includes, but is not limited to, the following: service supported by NF (NF _ service), priority of NF (NF _ priority), IMSI range (IMSI _ area), NF load level (NF _ bear), and the like;

the configured auxiliary information includes, but is not limited to, the following: load of NF (NF _ bear), geographical location of NF (NF _ location), NF slice information (NF _ slice), and the like.

The NF type (NF _ type), the NF instance number (NF _ num) and the IP address (IP _ address) in the identification information can only have one value; the restriction information may have one or more values, such as NF-supported services (NF _ service), or may be null, such as NF priority (NF _ priority), IMSI range (IMSI _ area), and the like; the side information has only one value, but can be changed in real time, such as the load of NF (NF _ bear). The role of the restriction information is: NFs may receive which Http2 messages, the Http relay device routes the received Http2 messages according to the restriction information. Referring to table 1, configuration table in the httpoutput device:

TABLE 1 configuration Table in the HttpRouter device

S102, analyzing the routing information carried by the message;

the Http outer device parses the received Http2 message after receiving the Http2 message sent by at least one sender network element. The Http2 messages transmitted in the embodiment of the present invention all carry routing information, where the routing information includes: the network element type of the receiving party, the service requested by the Http2 Message, SMP (SBI-Message-Priority), IMSI number carried by the Http2 Message, and so on. The NF type of the receiving party is identification information; the remaining information is the restriction information.

S103, determining a corresponding routing strategy according to the routing information

A routing information table is established in the Http outer device, and the detailed information of each Http2 message is recorded. After analyzing the routing information carried by the message, determining a corresponding routing policy according to the analyzed routing information, wherein the routing policy is obtained by combining a routing information table of an Http outer device, the routing information table records detailed information of each received Http2 message, and the routing information table includes, but is not limited to, the following information:

msg _ type (message type), src _ NF _ type (sender NF type), src _ IP (sender NF IP address), src _ stream _ id (sender NF id of message stream to http outlet device), dst _ NF _ type (receiver NF type), dst _ IP (receiver NF IP address), dst _ strem _ id (http outlet device id of message stream to receiver NF), and so on. Referring to table 2, routing information table:

table 2 routing information table

S104, matching a receiver network element for receiving the message according to the routing strategy;

s105, forwarding the message to the receiving network element

After the routing information is analyzed and the routing strategy is obtained, the receiver network elements which can be used for receiving the message are omitted according to the routing strategy, and the corresponding message is forwarded to the corresponding matched receiver network elements.

By the scheme disclosed by the invention, the Http2 request messages between the control plane network functions NFs are routed and distributed, so that the core network control plane network function NFs is effectively shielded, the connection complexity between the control plane network functions NFs inside the core network is simplified, the network architecture and the communication mode of the control plane are optimized, the singleness of the traditional NFs communication is avoided, meanwhile, the external Http2 protocol interface of NFs is shielded, and the flexibility and the safety of the control plane network function communication are improved.

According to another specific implementation manner of the embodiment of the present disclosure, referring to fig. 2 to 4, the step S101 includes:

step S101a, receiving a message sent by at least one sender network element in the same core network; alternatively, the first and second electrodes may be,

step S101b, receiving a message sent by at least one sender network element in a different core network.

The difference between the two types of request messages is that for an Http2 request message, when the Http outer device receives a message sent by a sender network element in the same core network, the Http outer device parses a URL of an Http2 request message sent by the core network NFs to which the Http outer device belongs, obtains routing information carried by the Http2 request message, and forwards the Http2 request message to a corresponding NF or returns a response message without the corresponding NF according to a routing policy of the Http outer device for the Http2 request message.

When the Http outlet device receives a message sent by a sender network element in a different core network, the sender network element first queries identification information, such as an IP address of the Http outlet device under the core network, from an NRF of an opposite-end core network, and then sends an Http2 request message to the Http outlet device according to the acquired IP address of the Http outlet device of the opposite-end core network. And the Http outer device of the opposite-end core network analyzes the URL of the Http2 request message, acquires the routing information carried by the Http2 request message, and forwards the Http2 request message to a corresponding network element or returns a response message that the corresponding network element does not exist according to the routing policy of the Http outer device of the opposite-end core network on the Http2 request message.

For the Http2 response message, the Http device parses the Http2 response message, obtains the routing information carried by the Http2 response message, and forwards the Http2 response message to the corresponding NF according to the routing policy of the Http device on the Http2 response message.

According to another specific implementation manner of the embodiment of the present disclosure, the message is a request message;

referring to fig. 5, the step S104 includes:

step S104a, according to the identification information in the routing information, at least one receiver network element identical to the identification information is matched in a routing configuration table to obtain a matching table containing at least one receiver network element list;

step S104b, matching the limitation information in the routing configuration table with at least one receiver network element whose limitation information includes or is equal to the limitation information in the routing information according to the list of receiver network elements obtained by the matching table.

It should be noted that the messages transmitted in the embodiment of the present invention include a request message and a response message. The request message and the response message have different corresponding routing strategies. When the message is a request message, the Http outer device matches one or more NFs that can receive the Http2 request message in a routing configuration table (e.g., table 1) according to the routing information, specifically, matches at least one NF that is the same as the identification information in the routing configuration table according to the identification information in the routing information. And matching at least one NF which contains or is equal to the limiting information in the routing configuration table according to the matching result and further according to the limiting information in the routing information.

Further, one NF is matched according to the auxiliary information in the routing information in the matched at least one NF to receive the message.

Specifically, after step S104b, the method further includes:

step S104c, matching out one receiver network element that receives the request message from at least one receiver network element that can receive the request message according to the auxiliary information in the routing information.

The method for matching out an NF capable of receiving the request message according to the auxiliary information of the routing information may be any one of the following:

the network element with the address position closest to the sender network element is matched according to the auxiliary information and is a receiver network element for receiving the message;

or, determining the network element with the minimum load degree as a receiver network element for receiving the request message according to the auxiliary information;

and or matching the network element in the same slice as the network element of the sender according to the auxiliary information to be a network element of a receiver for receiving the request message.

A NF that can receive the Http2 request message is matched based on one or more of the auxiliary information described above. Of course, the selected auxiliary messages are not limited to the above-mentioned several manners, and may also be filtered according to other configured auxiliary information, and specifically, the configuration of the auxiliary information may be set according to actual requirements.

Referring to fig. 7, an example explanation is made of message routing of a request message. The Http relay device receives the Http2 request message sent by the NF. If the routing information carried in the URL of the Http2 request message is: the NF type of the receiving party is UDM, the priority of the NF is 1, the requested service is UEauthentication, and the carried IMSI number is 460001231111111. The Http outer device looks up NFs that can receive the Http2 request message in a configuration table according to the Http2 request routing policy, where the NFs that can receive the Http2 request message exist as UDM-01, and then forwards the Http2 request message to UDM-01.

If the routing information carried in the URL of the Http2 request message is: the receiver NF type is UDM and the requested service is uecm (uecm). The Http outer device looks up NFs that can receive the Http2 request message in a configuration table according to the Http2 request routing policy, where the NFs that can receive the Http2 request message exist as UDM-02, and then forwards the Http2 request message to the UDM-02.

According to another specific implementation manner of the embodiment of the present disclosure, the message is a response message;

referring to fig. 6, the step S104 includes:

step S104A, matching at least one request message received by the sender network element according to the identification information of the sender network element carried in the response message;

step S104B, the sender network element corresponding to the matched request message is used as the receiver network element for receiving the response message, and the response message is forwarded to the receiver network element.

The Http router acquires the routing information carried by the Http2 response message, where the routing information includes, but is not limited to, the following: the type of the sender NF, the IP address of the sender NF, the identifier of the response message stream, and the like, match the request message corresponding to the response message in a routing information table (such as table 2) according to the routing information, acquire the IP address of the sender NF of the request message, and then forward the Http2 response message to the sender NF of the request message according to the acquired IP address.

The step of specifically matching the request message corresponding to the response message further comprises:

the step S104A includes:

Referring to fig. 8, message routing of the response message is exemplified. The Http relay device receives the Http2 response message sent by the NF. If the routing information carried in the Http2 response message is: the sender NF type is AMF, the IP address of the sender NF is 192.168.2.1, and the Http2 response message flow ID is 02. The Http outer device looks up the corresponding request information in the routing information table according to the Http2 response routing policy. Wherein there is an Http2 request message number (msg _ num) of 01 corresponding to the Http2 response message, then obtain the IP address (src _ IP: 192.168.1.1) of the sender NF in the Http2 request message, and forward the Http2 response message to the corresponding NF (udm) according to the IP address.

Corresponding to the above method embodiment, referring to fig. 9 and fig. 10, an embodiment of the present disclosure further provides a routing apparatus 50, including:

a receiving module 501, configured to receive a message sent by at least one sender network element of a control plane;

an analyzing module 502, configured to analyze the routing information carried by the message;

a policy module 503, configured to determine a corresponding routing policy according to the routing information;

a matching module 504, configured to match, according to the routing policy, a receiver network element for receiving the message;

a forwarding module 505, configured to forward the message to the receiving network element.

In the Http outer device of the present invention, information (including identification information, restriction information, and auxiliary information) of all NFs of a control plane is configured in the Http outer device, so that after the Http outer device parses the routing information carried in the Http2 request message, one or more NFs capable of receiving the Http2 request message are matched in a configuration table according to the Http2 request routing policy, and then one NF is selected from the one or more NFs according to the auxiliary information matching and the Http2 request message is forwarded to the NF, or a response message that the sender NF does not have a suitable recipient NF is returned.

In the Http outer device, the routing information table is established in the Http outer device, and the detailed information of all Http2 messages received by the Http outer device is recorded, so that the Http outer device can conveniently query the Http2 request message corresponding to the Http2 response message in the routing information table according to the routing information carried by the Http2 response message, obtain the IP address of the NF of the Http2 request message, and forward the Http2 response message to the corresponding NF.

In the Http outer device of the present invention, the URL of the request message using Http2 carries restriction information of the message route, where the restriction information includes the requested service, IMSI number, SMP, and the like. The one or more kinds of restriction information are used for matching one or more NF capable of receiving the Http2 request message in the configuration table, and one NF is selected according to one or more kinds of auxiliary information, so that the Http2 request message can be preferentially routed to the NF, the routing requirements of different Http2 request messages are met, and the routing flexibility of the Http2 request message is improved.

In the Http outer apparatus of the present invention, the recipient of the Http2 response message is determined using the identity of the Http2 message stream. The identification of each message flow is independent, each message flow comprises a resource request and data response complete flow, the Http2 response message can be greatly guaranteed to be routed to the corresponding NF, and a receiving party NF can obtain correct service and work normally.

The apparatus shown in fig. 9 may correspondingly execute the content in the above method embodiment, and details of the part not described in detail in this embodiment refer to the content described in the above method embodiment, which is not described again here.

Referring to fig. 11, an embodiment of the present disclosure further provides a message routing system, where the system includes at least two network elements and a routing device that performs routing distribution processing on a message between the at least two network elements, where the network elements include a sender network element for sending the message and a receiver network element for receiving the message, and the routing device includes:

Referring to fig. 12, an embodiment of the present disclosure also provides an electronic device 60, including:

at least one processor; and the number of the first and second groups,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the message routing method of the method embodiments described above.

The disclosed embodiments also provide a non-transitory computer-readable storage medium storing computer instructions for causing the computer to perform the message routing method in the aforementioned method embodiments.

The disclosed embodiments also provide a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions which, when executed by a computer, cause the computer to perform the message routing method in the aforementioned method embodiments.

Referring now to FIG. 12, a schematic diagram of an electronic device 60 suitable for use in implementing embodiments of the present disclosure is shown. The electronic devices in the embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), in-vehicle terminals (e.g., car navigation terminals), and the like, and fixed terminals such as digital TVs, desktop computers, and the like. The electronic device shown in fig. 12 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 12, the electronic device 60 may include a processing means (e.g., a central processing unit, a graphics processor, etc.) 601 that may perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)602 or a program loaded from a storage means 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data necessary for the operation of the electronic apparatus 60 are also stored. The processing device 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.

Generally, the following devices may be connected to the I/O interface 605: input devices 606 including, for example, a touch screen, touch pad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, etc.; output devices 607 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 608 including, for example, tape, hard disk, etc.; and a communication device 609. The communication means 609 may allow the electronic device 60 to communicate with other devices wirelessly or by wire to exchange data. While the figures illustrate an electronic device 60 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.

In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication means 609, or may be installed from the storage means 608, or may be installed from the ROM 602. The computer program, when executed by the processing device 601, performs the above-described functions defined in the methods of the embodiments of the present disclosure.

It should be noted that the computer readable medium in the present disclosure can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.

The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device.

The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: acquiring at least two internet protocol addresses; sending a node evaluation request comprising the at least two internet protocol addresses to node evaluation equipment, wherein the node evaluation equipment selects the internet protocol addresses from the at least two internet protocol addresses and returns the internet protocol addresses; receiving an internet protocol address returned by the node evaluation equipment; wherein the obtained internet protocol address indicates an edge node in the content distribution network.

Alternatively, the computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: receiving a node evaluation request comprising at least two internet protocol addresses; selecting an internet protocol address from the at least two internet protocol addresses; returning the selected internet protocol address; wherein the received internet protocol address indicates an edge node in the content distribution network.

Computer program code for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units described in the embodiments of the present disclosure may be implemented by software or hardware. Where the name of a unit does not in some cases constitute a limitation of the unit itself, for example, the first retrieving unit may also be described as a "unit for retrieving at least two internet protocol addresses".

It should be understood that portions of the present disclosure may be implemented in hardware, software, firmware, or a combination thereof.

The above description is only for the specific embodiments of the present disclosure, but the scope of the present disclosure is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present disclosure should be covered within the scope of the present disclosure. Therefore, the protection scope of the present disclosure shall be subject to the protection scope of the claims.

Claims

1. A method of message routing, the method comprising:

analyzing the routing information carried by the message;

forwarding the message to the recipient network element.

2. The message routing method according to claim 1, wherein the step of receiving the message sent by at least one sender network element of the control plane comprises:

3. The message routing method according to claim 1, wherein the message is a request message;

4. The message routing method according to claim 3, wherein the step of matching a recipient network element for receiving the message according to the routing policy comprises:

5. The message routing method according to claim 4, wherein the step of matching out one receiving network element that receives the request message among at least one receiving network element that can receive the request message according to the auxiliary information in the routing information comprises any one of:

6. The message routing method according to claim 1, wherein the message is a response message;

7. The message routing method according to claim 6, wherein the step of matching at least one request message received by the sender network element according to the identification information of the sender network element carried in the response message comprises:

8. Message routing method according to any of claims 1 to 7, characterized in that the routing information comprises at least one of the following:

the type of the network element of the receiving party, the type of the network element of the sending party, the IP address of the network element of the sending party, the service requested by the message, the IMSI number carried by the message and the priority of the message.

9. A routing device, wherein the routing device is configured with an SBI interface, the routing device comprising:

10. The routing apparatus according to claim 9, wherein the routing apparatus is configured with identification information, restriction information and assistance information of the core network control plane network function NFs; the configured identification information includes: NF type, NF instance number, IP address; the configured restriction information includes: service supported by NF, NF priority, IMSI range and NF load degree; the configured auxiliary information includes load of the NF, geographical location of the NF, NF slice information.

11. The routing device of claim 9, wherein the routing device is configured with a routing policy that is enforced based on the established routing table, wherein the routing table comprises a routing configuration table and a routing information table, and wherein the routing information table comprises the following information:

12. A message routing system, characterized in that the system includes at least two network elements and a routing device for performing routing distribution processing on a message between at least two network elements, the network elements include a sender network element for sending a message and a receiver network element for receiving a message, the routing device includes:

13. An electronic device, characterized in that the electronic device comprises:

at least one processor; and the number of the first and second groups,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the message routing method of any of preceding claims 1-8.

14. A computer-readable storage medium storing computer instructions for causing a computer to perform the message routing method of any preceding claim 1 to 8.