WO2017147840A1

WO2017147840A1 - Message routing method and device, and diameter routing entity

Info

Publication number: WO2017147840A1
Application number: PCT/CN2016/075457
Authority: WO
Inventors: 柳清芬
Original assignee: 华为技术有限公司
Priority date: 2016-03-03
Filing date: 2016-03-03
Publication date: 2017-09-08

Abstract

Embodiments of the present invention relate to the technical field of Internet and provide a message routing method and device, and a diameter routing entity. The message routing method comprises: a diameter routing entity receives a quality of service (QoS) message, wherein the QoS message comprises an identifier of a UE and a QoS parameter of a service that the UE accesses, and the QoS parameter is used by a PCRF entity for allocating network resources to the service that the UE accesses; the diameter routing entity obtains an address of a target PCRF entity of the UE according to the QoS message; the diameter routing entity routes the QoS message to the target PCRF entity according to the address. By means of the present invention, a PCRF entity in a network can allocate network resources to a UE according to the UE and a service that the UE accesses, thereby ensuring the QoS of a valuable service.

Description

Message routing method, device and diameter routing entity

Technical field

The present invention relates to the field of Internet technologies, and in particular, to a message routing method, apparatus, and diameter (English: Diameter) routing entity.

Background technique

With the rapid development of mobile broadband (English: Mobile BroadBand; MBB) technology, more and more Internet-based Over The Top (English: Over The Top; referred to as: OTT) business came into being.

In the prior art, the service quality (English: Quality of Service; QoS) optimization technology is applied to the service server that provides the OTT service, so that the service server provides differentiated services for different OTT services, thereby ensuring the user equipment. (English: User Equipment; referred to as: UE) access to the quality of service of valuable OTT services. For example, different OTT services in the service server are pre-configured with different QoS parameters. When the UE accesses the OTT service, the service server responds to the UE access according to the QoS parameter corresponding to the OTT service accessed by the UE. For a part of the valuable OTT service, the QoS parameters configured for it can indicate that the service server responds preferentially to the service server, so that the service server can preferentially guarantee the service quality of the valuable OTT service.

The foregoing prior art applies the QoS optimization technology to the service server, which can improve the service quality of the OTT service at the application layer. However, under the explosive growth of data traffic, the service quality of the OTT service at the network layer cannot be guaranteed. For example, when a large number of UEs access the OTT service, some valuable OTT services affect the quality of service due to insufficient network resources allocated, resulting in poor service quality of valuable OTT services at the network layer.

Summary of the invention

In order to solve the problem that when a large number of UEs access the OTT service in the prior art, the part of the valuable OTT service affects the service quality due to insufficient network resources allocated, and the service quality of the valuable OTT service at the network layer is poor. The embodiment of the invention provides a message routing method, device and Diameter routing entity. The technical solution is as follows:

In a first aspect, an embodiment of the present invention provides a message routing method, configured to configure a Diameter routing entity with a Diameter routing function, where the method includes:

The Diameter routing entity receives the quality of service QoS message, and the QoS message includes the identifier of the UE and the QoS parameter of the service accessed by the UE. The QoS parameter is used for the policy and the rule charging function (English: Policy ang Charging Rules Function; PCRF) The service accessed by the UE allocates network resources;

The Diameter routing entity obtains an address of the target PCRF entity of the UE according to the QoS message;

The Diameter routing entity routes the QoS message to the target PCRF entity based on the address.

When the UE accesses the service server, the service server generates a corresponding QoS message according to the identifier of the UE and the QoS parameter of the service accessed by the UE, and routes the QoS message to the target PCRF entity of the UE through the Diameter routing entity in the network, by the target PCRF. The entity allocates the network resource to the service accessed by the UE according to the QoS message, and solves the problem that the QoS optimization technology is applied to the service server in the prior art, which can improve the service quality of the OTT service at the application layer, and cannot ensure that when a large number of UEs access the OTT service. A sufficient amount of network resources can be allocated by the valuable OTT service, so that the PCRF entity in the network can allocate network resources according to the UE and the services it accesses, thereby ensuring the service quality of the valuable service.

With reference to the first aspect, in the first possible implementation manner of the first aspect, the roaming mode adopted by the UE is Home-routed (English: Home-routed), and the identifier of the UE is the mobile station international ISDN number of the UE (English: Mobile Subscriber International ISDN number; referred to as: MSISDN), International Mobile Subscriber Identity (English: International Mobile Subscriber Identity; IMSI) or Public Internet Protocol (English: Internet Protocol; IP address); or ,

The roaming mode adopted by the UE is local roaming (English: Local break), and the identifier of the UE is the public IP address of the UE.

For the different roaming modes provided by the carrier network, the identifier of the UE may be in different representations, so that the Diameter routing entity can accurately find the target PCRF entity corresponding to the UE according to the identifier, and route the QoS message to the message routing, thereby expanding the message routing. Applicable scene.

With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the identifier of the UE is a public network IP address of the UE, and the QoS message includes, to indicate that the user identity is private to the terminal. User identity type (English: Subscription-Id-Type) and user identity data (English: Subscription-Id-Data) with the value of the public network IP address.

Since the subscription-Id-Type in the QoS information only includes the type definition of the MSISDN and the IMSI, and does not include the type definition of the public network IP address, when the identifier of the UE is the public network IP address of the UE, the QoS message is used. The Subscription-Id-Type is configured to indicate that the user identity is private to the terminal, and the value of the Subscription-Id-Data is set to the public network IP address, so that the entity that receives the QoS message can identify the public network included in the QoS message. The IP address is used to implement the transmission of the public network IP address between the Diameter routing entities.

With reference to the first aspect, the first possible implementation manner of the first aspect, or the second possible implementation manner of the first aspect, in a third possible implementation manner of the first aspect, obtaining the UE according to the QoS message The address of the target PCRF entity, including:

The Diameter routing entity determines, according to the identifier of the UE, a segment name to which the identifier of the UE belongs;

The Diameter routing entity searches for the segment name to which the identifier of the UE belongs in the first mapping table, and obtains a next hop address corresponding to the segment name to which the identifier of the UE belongs, and the first mapping table includes a mapping between the segment name and the next hop address. relationship;

The Diameter routing entity determines the next hop address as the address of the target PCRF entity.

When only one Diameter domain is planned in the carrier network, the mapping relationship between the segment name and the next hop address is pre-configured in the Diameter routing entity. When the QoS message is received, the QoS message is obtained according to the identifier of the UE included in the QoS message. The next hop address, and the next hop address is determined as the address of the target PCRF entity, thereby implementing routing of the QoS message in the carrier network.

With reference to the first aspect, the first possible implementation manner of the first aspect, or the second possible implementation manner of the first aspect, in a fourth possible implementation manner of the first aspect, the UE is obtained according to the QoS message. The address of the target PCRF entity, including:

Determining, according to the identifier of the UE, a segment name to which the identifier of the UE belongs;

Searching for the segment name to which the identifier of the UE belongs in the second mapping table, and obtaining the target domain identifier corresponding to the segment name to which the identifier of the UE belongs, and the second mapping table includes the mapping relationship between the segment name and the target domain identifier, and the target domain identifier Used to indicate the Diameter field where the target PCRF entity is located;

The Diameter routing entity searches for the target domain identifier in the third mapping table according to the obtained target domain identifier, and obtains a next hop address corresponding to the target domain identifier, where the third mapping table includes a mapping between the target domain identifier and the next hop address. The next hop address is used to indicate the Diameter routing entity, and the Diameter routing entity indicated by the next hop address is used to obtain the address of the target PCRF entity according to the QoS message.

When the carrier network is planned to be a plurality of Diameter domains, the mapping relationship between the pre-configured segment name and the target domain identifier and the target domain identifier and the next hop address in the Diameter routing entity is received. In the QoS message, the Diameter routing entity determines the next hop address of the QoS message according to the above mapping relationship, thereby implementing routing addressing of the QoS message in the multi-Diameter domain operator network.

With reference to the fourth possible implementation manner of the first aspect, in a fifth possible implementation manner of the first aspect, the target domain identifier is searched in the third mapping table according to the obtained target domain identifier, and the target domain identifier is obtained. After the corresponding next hop address, it also includes:

The Diameter routing entity routes the QoS message to the Diameter routing entity indicated by the next hop address.

After determining the next hop address of the QoS message according to the foregoing mapping relationship, the Diameter routing entity routes the QoS message to the next Diameter routing entity indicated by the next hop address, and finally routes the QoS message to the target PCRF entity by the next Diameter routing entity. Thereby routing of QoS messages in a multi-Diameter domain operator network.

With reference to the first aspect, the first possible implementation manner of the first aspect, or the second possible implementation manner of the first aspect, in a sixth possible implementation manner of the first aspect, the QoS message further includes a private UE The IP address or the access point name (English: Access Point Name; APN for short), the Diameter routing entity is directly connected to the target PCRF entity, and the Diameter routing entity stores the mapping between the private network IP address and the PCRF entity, or APN. Correspondence with the PCRF entity;

Obtaining an address of the target PCRF entity of the UE according to the QoS message, including:

The Diameter routing entity searches for a PCRF entity corresponding to the private network IP address or the APN according to the private network IP address or the APN in the QoS message.

The Diameter routing entity determines the address of the found PCRF entity as the address of the target PCRF entity.

When receiving the QoS message, the Diameter routing entity directly connected to the target PCRF entity routes the QoS message to the target according to the correspondence between the pre-stored private network IP address of the UE and the PCRF entity, or the corresponding relationship between the APN of the UE and the PCRF entity. The PCRF entity improves the routing efficiency of QoS messages.

With reference to the first aspect, the first possible implementation manner of the first aspect, or the second possible implementation manner of the first aspect, in a seventh possible implementation manner of the first aspect, the UE is obtained according to the QoS message The address of the target PCRF entity, including:

The Diameter routing entity obtains the stored default route;

The Diameter routing entity determines the routing address indicated by the default route as the address of the target PCRF entity.

By pre-storing the default route in the Diameter routing entity, the QoS message can be routed to the PCRF entity, ensuring the quality of service of the UE accessing the service.

Combining the first aspect, the first possible implementation of the first aspect, the second possible implementation of the first aspect, the third possible implementation of the first aspect, the fourth possible aspect of the first aspect Embodiment, a fifth possible implementation of the first aspect, a sixth possible implementation of the first aspect, or a seventh possible implementation of the first aspect, an eighth possible implementation of the first aspect In the mode, the Diameter routing entity is a QoS platform, or the Diameter routing entity is a Diameter Routing Agent (DRA) entity between the QoS platform and the PCRF entity.

By configuring the above message routing method in the QoS platform and/or the DRA entity, the foregoing method can be applied to an operator network including only one Diameter domain, and can be applied to an operator network including multiple Diameter domains, and the network is expanded. Applicable scenarios for message routing.

In a second aspect, an embodiment of the present invention provides a message routing apparatus, where the apparatus includes at least one unit, and each unit is used to implement corresponding steps of the message routing method of the foregoing first aspect.

In a third aspect, an embodiment of the present invention provides a Diameter routing entity, where the Diameter routing entity includes: a receiver, a processor, and a transmitter, where the receiver, the processor, and the transmitter are used to implement the message routing method of the foregoing first aspect. The corresponding steps.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present invention. Other drawings may also be obtained from those of ordinary skill in the art in light of the inventive work.

FIG. 1 is a schematic diagram showing an implementation environment provided by an embodiment of the present invention; FIG.

2 is a schematic structural diagram of a Diameter routing entity provided by an embodiment of the present invention;

FIG. 3 is a flowchart of a method for a message routing method according to an embodiment of the present invention;

FIG. 4 is a flowchart of a method for a message routing method according to another embodiment of the present invention;

FIG. 5 is a flowchart of a method for a message routing method according to still another embodiment of the present invention;

FIG. 6 is a flowchart of a method for a message routing method according to still another embodiment of the present invention;

FIG. 7 is a flowchart of a method for a message routing method according to still another embodiment of the present invention;

FIG. 8 is a block diagram of a message routing apparatus according to an exemplary embodiment of the present invention.

detailed description

The embodiments of the present invention will be further described in detail below with reference to the accompanying drawings.

Please refer to FIG. 1, which shows a schematic diagram of an implementation environment provided by an embodiment of the present invention. The implementation environment includes at least one service server 110, a QoS platform 120, at least one DRA entity 130, and at least one PCRF entity 140.

The service server 110 is configured to receive an access request of each UE (not shown in the figure), and according to the service accessed by the UE, the QoS application programming interface (English: Application Programming Interface; API) provided by the QoS platform 120 The platform 120 sends a QoS message, where the QoS message carries the identifier of the UE, the QoS parameter of the service accessed by the UE, and the like. The service server 110 may be a server corresponding to the operator's own business or a server corresponding to the third-party OTT service. The embodiment of the present invention does not limit the type of the service server 110.

Each service server 110 and the QoS platform 120 are connected by a wired or wireless network.

The QoS platform 120 is an entity configured with a Diameter routing function routing function, and the QoS platform 120 can be a single server or a server cluster. The QoS platform 120 is configured to receive the QoS message sent by each service server 110, and directly route the QoS message to the PCRF entity 140 corresponding to the UE, or route the QoS message to the UE through at least one DRA entity 130. PCRF entity 140. The routing relationship between the entities is configured in the QoS platform 120.

The DRA entity 130 is an entity configured with a Diameter routing function routing function. The DRA entity 130 is configured to receive the QoS message sent by the QoS platform 120 or other DRA entities 130 connected thereto, and route the received QoS message to the PCRF entity 140 corresponding to the UE. The routing relationship between the entities is configured in the DRA entity 130.

The PCRF entity 140 is provided by the operator, and is configured to allocate network resources to the services accessed by the UE according to the QoS parameters carried in the received QoS message, where the network resources allocated by the PCRF entity 140 include bandwidth resources, priority resources, and delay resources. Wait.

The message routing method provided by various exemplary embodiments of the present invention is applied in the QoS platform 120 or the DRA entity 130 in FIG.

Please refer to FIG. 2, which shows the structure of a Diameter routing entity provided by an embodiment of the present invention. As a schematic diagram, the Diameter routing entity may be the QoS platform 120 or the DRA entity 130 in the implementation environment shown in FIG. 1. The Diameter routing entity includes a processor 11, a network interface 12, and a memory 13.

The processor 11 includes one or more processing cores, and the processor 11 executes various functional applications and data processing by running software programs and modules.

There may be multiple network interfaces 12, some of which are used to communicate with a service server, and others are used to communicate with a directly connected DRA entity or PCRF entity.

The memory 13 is connected to the processor 11 via a connection means such as a bus, and the memory 13 can be used to store software programs and modules.

The memory 13 can store an application module 14 required for at least one function, and the application module 14 can include a receiving module 141, a processing module 142, and a transmitting module 143, which can be combined with the processor 13, the network interface 12, and other hardware to execute the map. The corresponding operation in 2. For example, the receiving module 141 can function as a receiver, which can be combined with the network interface 12 to implement operations for receiving messages from other devices. For example, the transmitting module 143 can function as a transmitter, which can be combined with the network interface 12 to send messages to other devices. Operation.

The memory 13 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only Memory (English: electrically erasable programmable read-only memory; EEPROM), erasable programmable read only memory (English: erasable programmable read only memory; referred to as: EPROM), programmable read-only memory (English: programmable read only Memory; referred to as: PROM), read only memory (English: read only memory image; referred to as: ROM), magnetic memory, flash memory, disk or optical disk.

Those skilled in the art will appreciate that the structure illustrated in FIG. 2 does not constitute a definition of a Diameter routing entity, may include more or fewer components than illustrated, or may combine certain components, or different component arrangements.

In the following embodiments, the Diameter routing entity is used as a QoS platform or a DRA entity as an example.

Please refer to FIG. 3, which is a flowchart of a method for a message routing method according to an embodiment of the present invention. In this embodiment, the message routing method is used to configure a Diameter routing entity with a Diameter routing function as an example. The method includes:

Step 301: Receive a quality of service QoS message, where the QoS message includes an identifier of the UE and a QoS parameter of the service accessed by the UE, where the QoS parameter is used by the PCRF entity to allocate network resources for the service accessed by the UE.

When the Diameter routing entity is a QoS platform, the QoS message may be sent by the service server to the QoS platform when the UE accesses the service server; when the Diameter routing entity is a DRA entity, the QoS message may be directly connected to the QoS message. Sent by the platform or other DRA entities directly connected to it.

The QoS parameters corresponding to different value services are different. For example, the QoS parameter corresponding to the service with high value indicates that more network resources are allocated, and the QoS parameter corresponding to the service with low value indicates that less network resources are allocated.

Step 302: Obtain an address of a target PCRF entity of the UE according to the QoS message.

Step 303, according to the address, routing the QoS message to the target PCRF entity.

The Diameter routing entity routes the received QoS message to the target PCRF entity according to the obtained address, and the target PCRF entity allocates the corresponding network resource to the service accessed by the UE according to the QoS parameter included in the QoS message.

In summary, the message routing method provided in this embodiment, when the UE accesses the service server, the service server generates a corresponding QoS message according to the identifier of the UE and the QoS parameter of the service accessed by the UE, and uses the Diameter routing entity in the network to The QoS message is routed to the target PCRF entity of the UE, and the target PCRF entity allocates the network resource for the service accessed by the UE according to the QoS message, and solves the problem that the QoS optimization technology is applied to the service server in the prior art, and only the OTT service can be improved. The QoS of the layer cannot guarantee sufficient network resources that some valuable OTT services can allocate when a large number of UEs access the OTT service. The PCRF entity in the network can allocate network resources according to the UE and the services it accesses. To ensure the quality of service for valuable business.

When the roaming mode of the carrier network is Home-routed, the target PCRF entity corresponding to the UE is a PCRF entity corresponding to the home network to which the UE belongs, and the identifier of the UE may be the MSISDN of the UE, At least one of the IMSI or public network IP addresses. For convenience of description, in the following embodiments, when the roaming mode of the operator network is Home-routed roaming, the MSISDN with the UE's identity is the UE is taken as an example for illustration, and the present invention is not limited.

Please refer to FIG. 4, which illustrates a method flow of a message routing method according to another embodiment of the present invention. Cheng Tu. This embodiment uses the message routing method for the implementation environment shown in FIG. 1 as an example. The method includes:

In step 401, the service server sends QoS information to the QoS platform.

The QoS platform translates QoS resources in the network into QoS application interfaces and provides them to various service servers connected to them. When the UE accesses the service in the service server, the service server invokes the corresponding QoS API to send QoS information to the QoS platform. The QoS request information carries the identifier of the UE, the QoS parameter of the service accessed by the UE, and the like. In this embodiment, the identifier of the UE may be at least one of an MSISDN, an IMSI, or a public network IP address of the UE, because the roaming mode adopted by the UE is Home-routed.

The QoS parameters may include network bandwidth parameters, response priority parameters, response delay parameters, and the like, and different services are pre-allocated with different QoS parameters. For example, for a service with higher value, the QoS parameters allocated to it may include a larger network bandwidth, a higher corresponding priority, and a lower response delay. For a lower value service, the QoS parameters assigned thereto may be Includes smaller network bandwidth, lower corresponding priority, and higher response latency.

Step 402: The QoS platform receives the QoS message, where the QoS message includes the identifier of the user equipment UE and the QoS parameter of the service accessed by the UE.

The corresponding QoS platform receives the QoS message sent by each service server.

Step 403: The QoS platform determines, according to the identifier of the UE, a segment name to which the identifier of the UE belongs.

The QoS platform obtains the identifier of the UE carried in the QoS message, and further determines the segment name to which the identifier of the UE belongs, where the segment name is used to indicate the predetermined content in the identifier, and the segment name may be an MSISDN number segment name and an IMSI number. Segment name or IP address segment name, and so on.

When the identifier of the UE is the MSISDN of the UE, the segment name is an MSISDN number segment name, and the MSISDN segment name is used to indicate a segment of a predetermined length in the MSISDN. For example, the identifier included in the QoS message obtained by the QoS platform is “86138120912345”, and the MSISDN number segment name is used to indicate the first 9-bit segment in the MSISDN, and the QoS platform determines that the segment name is “86138120”.

Step 404: The QoS platform searches for the segment name to which the identifier of the UE belongs in the first mapping table, and obtains a next hop address corresponding to the segment name to which the identifier of the UE belongs, where the first mapping table includes the segment name and the next hop address. Mapping relationship.

The QoS platform pre-collects the routing relationship between the QoS platform and each PCRF entity in the carrier network, because the PCRF entity in the carrier network provides services for a large number of UEs at the same time, and the identifiers of the UEs belong to the same segment name. Generate the indication segment name and the next hop address (indicating the QoS level The mapping relationship between the directly connected PCRF entities). After determining the segment name to which the identifier of the UE belongs in the QoS message, the corresponding next hop address can be searched in the mapping relationship, and the routing of the QoS message is further completed. The mapping between the segment name and the next hop address may be stored in the form of a first mapping table. Schematically, the first mapping table may be as shown in the following table.

Table I

The MSISDN number segment start number and the end number (optional parameter) are used to indicate all the MSISDNs included in the corresponding MSISDN number segment name; the application type is used to indicate the Diameter application type. In this embodiment, the application type is Rx. For example, the priority (optional parameter) is used to indicate the priority of each MSISDN segment name. When the MSISDN is matched to at least two MSISDN segment names, the MSISDN segment name with higher priority is selected.

Similarly, when the identifier of the UE is the IMSI number of the UE, the first mapping table stores the mapping relationship between the IMSI number segment name and the next hop address; when the identifier of the UE is the public network IP address of the UE, the first The mapping table stores the mapping relationship between the IP address segment name and the next hop address.

In step 405, the QoS platform determines the next hop address as the address of the target PCRF entity.

If the QoS platform can obtain the next hop address corresponding to the segment name in the mapping relationship, it indicates that the QoS platform is directly connected to the PCRF entity corresponding to the segment name, and the obtained next hop address is determined as the UE corresponding. The address of the target PCRF entity.

For example, taking the MSISDN of the UE as 8613825097364 as an example, the QoS platform determines that the MSISDN number segment matching the MSISDN is named 86138250, and obtains the next hop address corresponding to the segment name as "Address A", that is, the address A" is determined to be the address of the UE corresponding to the target PCRF entity.

Step 406: The QoS platform routes the QoS message to the target PCRF entity according to the address.

It should be noted that, since the QoS platform uses the Rx interface between the service server and the PCRF entity to perform QoS message routing, the QoS message routed by the QoS platform to the target PCRF entity needs to be further encapsulated into Rx interface information.

Step 407: The target PCRF entity allocates network resources for services accessed by the UE according to the QoS parameters included in the QoS message.

Correspondingly, the target PCRF entity receives the QoS message sent by the QoS platform, and further allocates network resources for the UE access service according to the QoS parameters and the like carried in the QoS message, thereby implementing the network side service quality guarantee.

Since the QoS parameters corresponding to the service are allocated according to the value of the service, the PCRF entity can preferentially guarantee the quality of service of the UE to access the valuable service.

In this embodiment, the service server only needs to send a QoS message to the QoS platform through the interface provided by the QoS platform, and the QoS platform can route the QoS message to the target PCRF entity. The service server can complete the optimization of the one-click service quality without knowing the carrier network structure, thereby reducing the difficulty for the service server to optimize the UE access service.

Generally, the QoS platform is directly connected to each PCRF entity because the number of PCRF entities in the carrier network is large and the geographical distribution of each PCRF entity is dispersed. In this case, a large number of DRA entities need to be deployed in the carrier network, and the QoS platform and the DRA entity cooperate to complete routing of QoS messages. Therefore, when the QoS platform is connected to the target PCRF entity corresponding to the UE by at least one DRA entity, the DRA entity needs to route the QoS message to the target PCRF entity according to the content included in the QoS message.

Please refer to FIG. 5, which is a flowchart of a method for a message routing method according to still another embodiment of the present invention. This embodiment uses the message routing method for the implementation environment shown in FIG. 1 as an example. The method includes:

In step 501, the service server sends QoS information to the QoS platform.

Step 502: The QoS platform receives the QoS message, where the QoS message includes the identifier of the user equipment UE and the QoS parameter of the service accessed by the UE.

Step 503: The QoS platform determines, according to the identifier of the UE, a segment name to which the identifier of the UE belongs.

Step 504: The QoS platform searches for the segment name to which the identifier of the UE belongs in the first mapping table, and obtains a next hop address corresponding to the segment name to which the identifier of the UE belongs, where the first mapping table includes the segment name and the next hop address. Mapping relationship.

The implementation of the foregoing steps 501 to 504 is similar to the implementation of the steps 401 to 404, and details are not described herein again.

Step 505: If the QoS platform does not obtain the next hop address corresponding to the segment name to which the identifier of the UE belongs, search for the segment name to which the identifier of the UE belongs in the second mapping table, and obtain the segment name corresponding to the identifier of the UE. Target domain ID.

If the QoS platform can find the next hop address corresponding to the segment name of the identifier in the first mapping table, it indicates that the target PCRF entity corresponding to the UE is directly connected to the QoS platform; if the QoS platform fails to be in the first mapping table If the next hop address corresponding to the segment name of the identifier is found, it indicates that the QoS platform and the target PCRF entity that identifies the UE are connected by at least one DRA entity.

When the operator network includes at least one DRA entity, the carrier network is divided into multiple Diameter domains, and each Diameter includes a DRA entity and a DRA entity and/or a PCRF entity connected thereto, when the UE When a PCRF entity exists in a certain Diameter domain, the Diameter domain is the target domain corresponding to the UE.

Therefore, when the operator network includes the DRA entity, the QoS platform (and the DRA entity) not only configures the mapping relationship between the identifier of the UE and the next hop address, but also configures the mapping relationship between the segment name and the target domain identifier. . When the QoS platform fails to find the next hop address corresponding to the segment name to which the identifier belongs in the first mapping table, that is, according to the mapping relationship between the segment name and the target domain identifier, the Diameter domain in which the target PCRF entity of the UE is located is determined. . The mapping between the segment name and the target domain identifier may be stored in the form of a second mapping table, and the table structure of the second mapping table may be as shown in Table 2.

Table II

MSISDN号段名MSISDN number name	优先级priority	目标域标识Target domain identifier	应用类型App types
8613812086138120	--	Diameter001Diameter001	RxRx
8615124086151240	--	Diameter002Diameter002	RxRx
8613255186132551	--	Diameter003Diameter003	RxRx
…...	…...	…...	…...

The priority (optional parameter) is used to indicate the priority of each MSISDN segment name. When the MSISDN is matched to at least two MSISDN segment names, the MSISDN segment name with a higher priority is selected. In the embodiment, the application type is Rx as an example.

Step 506: The QoS platform searches for the target domain identifier in the third mapping table according to the obtained target domain identifier, and obtains a next hop address corresponding to the target domain identifier.

In order to route the QoS message to the target domain corresponding to the UE, and the DSA in the target domain sends the received QoS message to the target PCRF entity, the QoS platform needs to determine the next hop address to the target domain.

The QoS platform pre-stores a mapping relationship between the target domain identifier and the next hop address, and the next hop address is used to indicate a DRA entity directly connected to the QoS (ie, a Diameter routing entity). The mapping between the target domain identifier and the next hop address may be stored in the form of a third mapping table, and the third mapping table may be schematically shown in Table 3.

Table 3

目标域标识Target domain identifier	缺省路由Default route	应用类型App types	下一跳地址Next hop address
Diameter001Diameter001	--	RxRx	地址CAddress C
Diameter002Diameter002	--	RxRx	地址DAddress D
Diameter003Diameter003	--	RxRx	地址EAddress E

The default route (optional parameter) is the route corresponding to the specified application. When the specified application does not have the corresponding next hop address configured, the default route can be configured for the specified application.

In step 507, the QoS platform routes the QoS message to the DRA entity indicated by the next hop address.

The QoS platform routes the QoS message to the DRA entity indicated by the next hop address according to the acquired next hop address of the target domain identifier.

Step 508: The DRA entity receives the QoS message sent by the QoS platform.

Correspondingly, the DRA entity receives the QoS message sent by the QoS platform.

Step 509: The DRA entity obtains an address of the target PCRF entity of the UE according to the QoS message.

Similar to the QoS platform, the first mapping table, the second mapping table, and the third mapping table are also configured in the DRA entity in the carrier network. After receiving the QoS message, the DRA entity determines the segment name to which the identifier of the UE belongs according to the identifier of the UE in the QoS message, and searches for the next hop address corresponding to the segment name to which the identifier of the UE belongs in the first mapping table. To the next corresponding to the segment name to which the identity of the UE belongs The hop address indicates that the current DRA entity is directly connected to the target PCRF entity of the UE, and the next hop address is missed as the address of the target PCRF entity; if the next corresponding to the segment name to which the identifier of the UE belongs is not obtained, The hop address indicates that the current DRA entity and the target PCRF entity are also connected through other DRA entities. The DRA entity obtains the target domain identifier corresponding to the segment name to which the identifier of the UE belongs according to the segment name to which the identifier of the UE belongs, and further obtains the target domain identifier in the third mapping table according to the obtained target domain identifier. Corresponding next hop address, and further routing the QoS message to the next DRA entity according to the acquired next hop address, and the next DRA entity routes the QoS message to the target PCRF entity. That is, the DRA entity repeatedly performs the above steps 504 and 507 until the address of the target PCRF entity is obtained.

It should be noted that, since the QoS platform sends the QoS message to the DRA entity, the target domain identifier corresponding to the target PCRF entity of the UE has been obtained. Therefore, in order to prevent the subsequent DRA entity from obtaining the target domain identifier again by searching the second mapping table. The QoS message sent by the QoS platform to the DRA entity includes the target domain identifier obtained by the above step 505.

As a possible implementation manner, since the QoS message is routed in the form of Rx interface information, and the Rx interface information includes a target domain attribute value pair (English: Destination-real AVP), the QoS platform may acquire the acquired target domain. The ID is populated into the Destination-real AVP.

Step 510: The DRA entity routes the QoS message to the target PCRF entity according to the address.

The QoS message is ultimately routed to the target PCRF entity through at least one DRA entity.

Step 511: The target PCRF entity allocates network resources for services accessed by the UE according to the QoS parameters included in the QoS message.

Correspondingly, the target PCRF entity receives the QoS message sent by the DRA entity, and further allocates network resources for the UE access service according to the QoS parameters and the like carried in the QoS message, thereby implementing the network side service quality guarantee.

In summary, the message routing method provided in this embodiment, when the UE accesses the service server, the service server generates a corresponding QoS message according to the identifier of the UE and the QoS parameter of the service accessed by the UE, and uses the Diameter routing entity in the network to The QoS message is routed to the target PCRF entity of the UE, and the target PCRF entity allocates the network resource for the service accessed by the UE according to the QoS message, and solves the problem that the QoS optimization technology is applied to the service server in the prior art, and only the OTT service can be improved. The quality of service of the layer cannot guarantee that some valuable OTTs are available when a large number of UEs access the OTT service. A sufficient network resource can be allocated by the service, so that the PCRF entity in the network can allocate network resources according to the UE and the services accessed by the UE, thereby ensuring the service quality of the valuable service.

In this embodiment, when a DRA entity is deployed in the carrier network, the mapping relationship between the segment name and the target domain identifier and the mapping relationship between the target domain identifier and the next hop address are configured in advance in the DRA entity and the QoS platform. The QoS platform and the DRA entity cooperate to accurately route the QoS message to the target PCRF entity corresponding to the UE, thereby implementing end-to-end QoS guarantee.

A default route is pre-stored in the QoS platform (or the DRA entity) in the carrier network. When the QoS platform (or the DRA entity) does not obtain the target domain identifier corresponding to the segment name in the second mapping table, or the QoS platform (or the DRA entity) does not obtain the next hop address corresponding to the target domain identifier in the third mapping table, and the QoS platform (or DRA entity) routes the QoS message to the corresponding PCRF entity according to the default route, as a possibility The method may further include the following steps.

In step 512, the QoS platform obtains the stored default route.

When the QoS platform does not obtain the target domain identifier corresponding to the segment name in the second mapping table, or the QoS platform does not obtain the next hop address corresponding to the target domain identifier in the third mapping table, the QoS platform acquires the storage. Default route. For example, the default route can be stored in the third mapping table as shown in Table 3. The QoS platform obtains the corresponding default route from the third mapping table.

If the QoS platform obtains the default route, the following step 513 is performed; if the default route is not obtained, the QoS platform returns a failure prompt to the service server.

Step 513: The QoS platform determines the routing address indicated by the default route as the address of the target PCRF entity.

The QoS platform determines the routing address indicated by the obtained default route as the address of the target PCRF entity corresponding to the QoS message, and routes the QoS message to the target PCRF entity, and the target PCRF entity allocates the network for the service accessed by the UE. Resources.

In a possible implementation manner, the roaming mode of the carrier network is Home-routed, and the UE selects the PCRF entity through the DRA entity (directly connected to the PCRF entity) in the session registration phase. At the same time, the DRA entity has a session binding function, and stores the correspondence between the private network IP address of the registered UE and the PCRF entity, or the corresponding relationship between the APN of the UE and the PCRF entity. The QoS message sent by the service server to the QoS platform includes the private network IP address and the APN of the UE. When the DRA entity receives the QoS message, it can cancel the QoS according to the private network IP address and the APN included in the QoS message. The information is sent to the corresponding target PCRF entity.

Please refer to FIG. 6, which is a flowchart of a method for a message routing method according to still another embodiment of the present invention. This embodiment uses the message routing method for the implementation environment shown in FIG. 1 as an example. The method includes:

In step 601, the service server sends QoS information to the QoS platform.

Step 602: The QoS platform receives the QoS message, where the QoS message includes the identifier of the user equipment UE and the QoS parameter of the service accessed by the UE.

Step 603: The QoS platform determines, according to the identifier of the UE, a segment name to which the identifier of the UE belongs.

Step 604: The QoS platform searches for the segment name to which the identifier of the UE belongs in the first mapping table, and obtains a next hop address corresponding to the segment name to which the identifier of the UE belongs, where the first mapping table includes the segment name and the next hop address. Mapping relationship.

The implementation of the foregoing steps 601 to 604 is similar to the implementation of the steps 501 to 504, and details are not described herein again.

Step 605: If the QoS platform does not obtain the next hop address corresponding to the segment name to which the identifier of the UE belongs, the second mapping table is used to search for the segment name to which the identifier of the UE belongs, and obtain the segment name corresponding to the identifier of the UE. Target domain ID.

In the above step 505, the target domain identifier in the second mapping table is the identifier of the target PCRF entity sitting in the Diameter domain; and in this step, the target domain identifier in the second mapping table is the Diameter domain in which the DRA entity directly connected to the target PCRF entity is located. Logo. That is, the second mapping table in the above step 505 is used to indicate the mapping relationship between the segment name and the target PCRF entity, and the second mapping table in this step is used to indicate the segment name and the DRA entity (directly connected to the target PCRF entity). The mapping relationship between them.

Step 606: The QoS platform searches for the target domain identifier in the third mapping table according to the obtained target domain identifier, and obtains a next hop address corresponding to the target domain identifier.

Correspondingly, after obtaining the target domain identifier, the QoS platform obtains a next hop address corresponding to the target domain identifier in the third mapping table, where the next hop address indicates the QoS platform to the DRA entity (directly connected to the target PCRF entity) The next hop.

In step 607, the QoS platform routes the QoS message to the DRA entity indicated by the next hop address.

Step 608: The DRA entity receives the QoS message sent by the QoS platform.

In step 609, the DRA entity routes the QoS message to the DRA entity directly connected to the target PCRF entity.

In the above steps 509 and 510, after receiving the QoS message, the DRA entity receives the first according to the storage. The mapping table, the second mapping table, and the third mapping table are used to route the QoS message to the target PCRF entity; and in this step, the next hop address that is found by the DRA entity according to the stored second mapping table and the third mapping table is The address of the DRA entity directly connected to the target PCRF entity. Therefore, the DRA entity finally routes the QoS message to the DRA entity directly connected to the target PCRF entity, and the directly connected DRA entity routes the QoS message to the target PCRF entity.

Step 610: The DRA entity searches for a PCRF entity corresponding to the private network IP address or the APN according to the private network IP address or the APN in the QoS message.

After receiving the QoS message, the DRA entity directly connected to the PCRF entity obtains the private network IP address and the APN carried in the QoS message. The DRA entity can directly associate with the PCRF entity, and the corresponding relationship between the private network IP address of the UE and the PCRF entity, and the corresponding relationship between the APN of the UE and the PCRF entity, so the DRA entity can be based on the private network IP address or the APN. From the at least one connected PCRF entity, the target PCRF entity of the QoS message is determined.

Step 611: The DRA entity determines the address of the found PCRF entity as the address of the target PCRF entity.

After the DRA entity finds the PCRF entity corresponding to the private network IP address or the APN, the address of the PCRF entity is determined as the address of the target PCRF entity.

Step 612: The DRA entity routes the QoS message to the target PCRF entity according to the address.

Step 613: The target PCRF entity allocates network resources for services accessed by the UE according to the QoS parameters included in the QoS message.

Similar to the foregoing step 511, after receiving the QoS message sent by the DRA entity, the target PCRF entity further allocates network resources for the UE access service according to the QoS parameters and the like carried in the QoS message, thereby implementing the network side service quality guarantee.

In this embodiment, when the DRA entity directly connected to the PCRF entity has a session binding function, the QoS The platform and the DRA entity QoS message are routed to the directly connected DRA entity, and the DRA entity finds the target PCRF entity and sends a QoS message to the target PCRF entity, thereby implementing end-to-end QoS guarantee.

When the roaming mode of the carrier network is Local break, the target PCRF entity of the UE should be the PCRF entity corresponding to the network where the UE is located (ie, the roaming network). If the MSISDN or IMSI of the UE is used as the identifier, the target PCRF entity is found. Incorrect (only the PCRF entity corresponding to the home network can be found according to MSISDN or IMSI). In the local break roaming scenario, the public IP address of the UE is allocated by the network address translation (English: Network Address Translation; NAT) server, and the public IP address segment mapped by the NAT server is pre-planned. Therefore, the mapping relationship between the public network IP address and the NAT server can be summarized. Further, since the NAT server corresponds to the PDN gateway (English: PDN GateWay; abbreviated as: P-GW), and the P-GW selects the PCRF entity through the DRA entity directly connected to the PCRF entity, the public network IP address-NAT can be obtained. Server--P-GW--The mapping relationship between the four DRA entities directly connected to the PCRF entity. Therefore, in the local break roaming scenario, the public network IP address of the UE is used as an identifier, and the QoS message can be routed to the correct PCRF entity. The following describes an example of a message routing method in a Local break roaming scenario.

Please refer to FIG. 7, which is a flowchart of a method for a message routing method according to still another embodiment of the present invention. In this embodiment, the roaming mode adopted by the UE is a local break, and the DRA entity directly connected to the PCRF entity has a session binding function as an example. The method includes:

In step 701, the service server sends QoS information to the QoS platform.

Different from the MSISDN or IMSI of the UE obtained in the foregoing step 601, when the service server receives the access request of the UE, the service server obtains the public network IP address of the UE. For example, the public IP address of the UE obtained by the service server is 192.168.16.1.

Step 702: The QoS platform receives a QoS message, where the QoS information includes a public network IP address, a private network IP address, an APN, and a QoS parameter of a service accessed by the UE.

Step 703: The QoS platform determines the IP address segment name to which the public network IP address of the UE belongs according to the public network IP address of the UE.

Similar to step 603 above, the QoS platform obtains the public network IP address included in the QoS message, and further determines the IP address segment name corresponding to the public network IP address.

For example, if the QoS platform obtains the public IP address of the UE as 192.168.16.1, and the IP address segment to which the public IP address belongs is the first 9 digits of the public IP address, the IP address segment name to which the public IP address belongs. It is "192.168.16".

Step 704: The QoS platform searches for the IP address segment name to which the public network IP address of the UE belongs in the first mapping table, and obtains a next hop address corresponding to the IP address segment name to which the public network IP address of the UE belongs, and the first mapping table. Contains the mapping relationship between the IP address segment name and the next hop address.

Different from the above step 604, the mapping relationship between the IP address segment name and the next hop address is stored in the QoS platform. The mapping relationship between the IP address segment name and the next hop address can be schematically shown in Table 4.

Table 4

IP地址段名IP address segment name	起始IP地址Starting IP address	结束IP地址End IP address	应用类型App types	优先级priority	下一跳地址Next hop address
192.168.16.0192.168.16.0	192.168.16.1192.168.16.1	192.168.16.255192.168.16.255	RxRx	--	--
192.168.17.0192.168.17.0	--	--	RxRx	--	地址AAddress A
192.168.18.0192.168.18.0	--	--	RxRx	--	--
192.168.19.0192.168.19.0	--	--	RxRx	--	地址BAddress B
…...	…...	…...	…...	…...	…...

The start IP address and the end IP address (optional parameter) are used to indicate all the IP addresses included in the corresponding IP address segment name; the application type is used to indicate the Diameter application type. In this embodiment, the application type is Rx as an example. The priority (optional parameter) is used to indicate the priority of each IP address segment name. When the public network IP address matches at least two IP address segment names, the IP address segment name with higher priority is selected. .

After determining the IP address segment name to which the public network IP address of the UE belongs, the QoS platform searches for the next hop address corresponding to the IP address segment name in the first mapping table. If the corresponding next hop address is found, it indicates that the QoS platform is directly connected to the target PCRF entity of the UE, and the QoS message is routed to the target PCRF entity indicated by the next hop address. The QoS platform is directly connected to the target PCRF entity of the UE by at least one DRA entity, and the following step 705 is performed.

Step 705: If the QoS platform does not obtain the next hop address corresponding to the IP address segment name to which the public network IP address of the UE belongs, find the target domain identifier corresponding to the IP address segment name in the second mapping table.

Different from the foregoing step 605, the mapping relationship between the IP address segment name and the target domain identifier is stored in the QoS platform, and the mapping relationship between the IP address segment name and the target domain identifier may be schematic. As shown in Table 5.

Table 5

IP地址段名IP address segment name	优先级priority	目标域标识Target domain identifier	应用类型App types
192.168.16.0192.168.16.0	--	Diameter001Diameter001	RxRx
192.168.16.18192.168.16.18	--	Diameter002Diameter002	RxRx
192.168.16.19192.168.16.19	--	Diameter003Diameter003	RxRx
…...	…...	…...	…...

The priority (optional parameter) is used to indicate the priority of each IP address segment name. When the IP address of the public network is matched to at least two IP address segment names, the IP address segment name with a higher priority is selected. The application type is used to indicate the Diameter application type. In this embodiment, the application type is Rx as an example.

When the next hop address corresponding to the IP address segment name is not found in the first mapping table, the QoS control platform searches for the corresponding target domain identifier in the second mapping table according to the IP address segment name.

For example, the QoS platform determines that the IP address segment to which the public IP address of the UE belongs is named 192.168.16.0, and obtains the corresponding target domain identifier as Diameter001 in Table 5.

Step 706: The QoS platform searches for the target domain identifier in the third mapping table according to the obtained target domain identifier, and obtains a next hop address corresponding to the target domain identifier.

Similar to the foregoing step 606, the QoS platform acquires the next hop address corresponding to the target domain identifier in the third mapping table according to the obtained target domain identifier.

Step 707, the QoS platform routes the QoS message to the DRA entity indicated by the next hop address.

Since the QoS platform needs to use the Rx interface with the DRA entity to perform routing of QoS messages, the QoS message routed by the QoS platform to the DRA entity needs to be further encapsulated into Rx interface information.

The MSISDN and the IMSI have corresponding types of definitions in the Sub-Subscription-Id-Type AVP of the Subscription-Id AVP in the Rx interface information, and the public network IP address does not have a corresponding type definition in the Rx interface information.

In order to enable the QoS information of the route to the DRA to carry the public network IP address, the QoS message includes a Subscription-Id-Type indicating that the user identity is private to the terminal and a Subscription-Id-Data value of the public network IP address. In a possible implementation manner, the subscription-Id-Type in the QoS message is set to END_USER_PRIVATE, and the Subscription-Id-Data in the QoS message is set to the public network IP address, and when the DRS entity receives the QoS message, it can Obtain the public IP address of the subscription-Id-Data.

Step 708: The DRA entity receives the QoS message sent by the QoS platform.

In step 709, the DRA entity routes the QoS message to the DRA entity directly connected to the target PCRF entity.

Step 710: The DRA entity searches for a PCRF entity corresponding to the private network IP address or the APN according to the private network IP address or the APN in the QoS message.

Step 711: The DRA entity determines the address of the found PCRF entity as the address of the target PCRF entity.

Step 712: The DRA entity routes the QoS message to the target PCRF entity according to the address.

Step 713: The target PCRF entity allocates network resources for services accessed by the UE according to the QoS parameters included in the QoS message.

The implementation of the foregoing steps 708 to 713 is similar to the implementation of the steps 608 to 613 in FIG. 6, and details are not described herein again.

In this embodiment, when the roaming mode adopted by the UE is a local break, the identifier of the UE may be represented by a public network IP address, and the QoS platform accurately finds the target of the UE according to the mapping relationship between the configured public network IP address and the PCRF entity. The PCRF entity sends QoS messages to it, which expands the applicable scenario of the message routing method.

Please refer to FIG. 8, which is a block diagram of a message routing apparatus according to an exemplary embodiment of the present invention. The message routing device can be implemented as all or part of a Diameter routing entity by software, hardware or a combination of both. The message routing device can include a receiving unit 810, a processing unit 820, and a routing unit 830.

The receiving unit 810 is configured to receive a quality of service QoS message, where the QoS message includes the user equipment UE And the QoS parameter of the service accessed by the UE, where the QoS parameter is used by the PCRF entity to allocate network resources for the service accessed by the UE;

The processing unit 820 is configured to obtain an address of the target PCRF entity of the UE according to the QoS message.

The routing unit 830 is configured to route the QoS message to the target PCRF entity according to the address.

Related details can be combined with reference to the above method embodiments.

In an optional embodiment, the roaming mode adopted by the UE is Home-routed, and the identifier of the UE is at least one of an MSISDN, an IMSI, or a public network IP address of the UE; or

The roaming mode adopted by the UE is Local break, and the identifier of the UE is the public IP address of the UE.

In an optional embodiment, the identifier of the UE is a public network IP address of the UE, and the QoS message includes a subscription-Id-Type indicating that the user identity is private to the terminal and a subscription-Id-Data value being a public network IP address. .

In an optional embodiment, the processing unit 820 is configured to determine, according to the identifier of the UE, a segment name to which the identifier of the UE belongs;

The processing unit 820 is further configured to: search, in the first mapping table, a segment name to which the identifier of the UE belongs, and obtain a next hop address corresponding to the segment name to which the identifier of the UE belongs, where the first mapping table includes the segment name and the next hop address. Mapping relationship between

The processing unit 820 is further configured to determine the next hop address as the address of the target PCRF entity.

The processing unit 820 is further configured to: search, in the second mapping table, the segment name to which the identifier of the UE belongs, obtain the target domain identifier corresponding to the segment name to which the identifier of the UE belongs, and the second mapping table includes the segment name and the target domain identifier. Mapping relationship, the target domain identifier is used to indicate the Diameter domain where the target PCRF entity is located;

The processing unit 820 is further configured to: according to the obtained target domain identifier, look up the target domain identifier in the third mapping table, obtain a next hop address corresponding to the target domain identifier, and the third mapping table includes the target domain identifier and the next hop address. The mapping relationship between the next hop address is used to indicate the Diameter routing entity, and the Diameter routing entity indicated by the next hop address is used to obtain the address of the target PCRF entity according to the QoS message.

In an optional embodiment, the routing unit 830 is further configured to route the QoS message to the Diameter routing entity indicated by the next hop address.

In an optional embodiment, the QoS message further includes a private network IP address or an APN of the UE. The Diameter routing entity is directly connected to the target PCRF entity, and the Diameter routing entity stores the correspondence between the private network IP address and the PCRF entity, or the corresponding relationship between the APN and the PCRF entity;

The processing unit 820 is configured to search for a PCRF entity corresponding to the private network IP address or the APN according to the private network IP address or the APN in the QoS message.

The processing unit 820 is further configured to determine an address of the found PCRF entity as an address of the target PCRF entity.

In an optional embodiment, the processing unit 820 is configured to obtain a stored default route.

The processing unit 820 is further configured to determine a routing address indicated by the default route as an address of the target PCRF entity.

In an optional embodiment, the Diameter routing entity is a QoS platform, or the Diameter routing entity is a DRA entity between the QoS platform and the PCRF entity.

In summary, the message routing apparatus provided in this embodiment, when the UE accesses the service server, the service server generates a corresponding QoS message according to the identifier of the UE and the QoS parameter of the service accessed by the UE, and uses the Diameter routing entity in the network to The QoS message is routed to the target PCRF entity of the UE, and the target PCRF entity allocates the network resource for the service accessed by the UE according to the QoS message, and solves the problem that the QoS optimization technology is applied to the service server in the prior art, and only the OTT service can be improved. The QoS of the layer cannot guarantee sufficient network resources that some valuable OTT services can allocate when a large number of UEs access the OTT service. The PCRF entity in the network can allocate network resources according to the UE and the services it accesses. To ensure the quality of service for valuable business.

A person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium. The storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.

The above are only the preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalents, improvements, etc., which are within the spirit and scope of the present invention, should be included in the protection of the present invention. Within the scope.

Claims

A message routing method for configuring a Diameter routing entity having a diameter Diameter routing function, the method comprising:

The Diameter routing entity receives a quality of service QoS message, where the QoS message includes an identifier of the user equipment UE and a QoS parameter of the service accessed by the UE, where the QoS parameter is used for the policy and the rule charging function PCRF entity is The service accessed by the UE allocates network resources;

Obtaining, by the Diameter routing entity, an address of a target PCRF entity of the UE according to the QoS message;

The Diameter routing entity routes the QoS message to the target PCRF entity according to the address.
The method of claim 1 wherein

The roaming mode adopted by the UE is Home Roaming Home-routed, and the identifier of the UE is at least one of a mobile station international ISDN number MSISDN, an international mobile subscriber identity number IMSI or a public network Internet Protocol IP address of the UE; or,

The roaming mode adopted by the UE is a local roaming Local break, and the identifier of the UE is a public network IP address of the UE.
The method according to claim 2, wherein the identifier of the UE is the public network IP address of the UE, and the QoS message includes a user identity type Subscription-Id indicating that the user identity is private to the terminal. -Type and the user identity data Subscription-Id-Data whose value is the public network IP address.
The method according to any one of claims 1 to 3, wherein the obtaining the address of the target PCRF entity of the UE according to the QoS message comprises:

Determining, by the Diameter routing entity, a segment name to which the identifier of the UE belongs according to the identifier of the UE;

The Diameter routing entity searches the first mapping table for the segment name to which the identifier of the UE belongs, and obtains a next hop address corresponding to the segment name to which the identifier of the UE belongs, where the first mapping table includes the segment name and Mapping relationship between next hop addresses;

The Diameter routing entity determines the next hop address as an address of the target PCRF entity.
The method according to any one of claims 1 to 3, wherein the obtaining the address of the target PCRF entity of the UE according to the QoS message comprises:

Determining, by the Diameter routing entity, a segment name to which the identifier of the UE belongs according to the identifier of the UE;

The Diameter routing entity searches for a segment name to which the identifier of the UE belongs in the second mapping table, and obtains a target domain identifier corresponding to the segment name to which the identifier of the UE belongs, where the second mapping table includes the segment name and the target. a mapping relationship between the domain identifiers, where the target domain identifier is used to indicate that the target PCRF entity is located in the Diameter domain;

The Diameter routing entity searches for the target domain identifier in the third mapping table according to the obtained target domain identifier, and obtains a next hop address corresponding to the target domain identifier, where the third mapping table includes the target domain. Identifying a mapping relationship with a next hop address, where the next hop address is used to indicate a Diameter routing entity, and the Diameter routing entity indicated by the next hop address is used to obtain the target PCRF entity according to the QoS message. the address of.
The method according to claim 5, wherein the searching for the target domain identifier in the third mapping table according to the obtained target domain identifier, obtaining a next hop address corresponding to the target domain identifier After that, it also includes:

The Diameter routing entity routes the QoS message to a Diameter routing entity indicated by the next hop address.
The method according to any one of claims 1 to 3, wherein the QoS message further includes a private network IP address or an access point name APN of the UE, and the Diameter routing entity and the target PCRF entity are directly And the corresponding relationship between the private network IP address and the PCRF entity, or the corresponding relationship between the APN and the PCRF entity;

Obtaining an address of the target PCRF entity of the UE according to the QoS message, including:

The Diameter routing entity searches for a PCRF entity corresponding to the private network IP address or the APN according to the private network IP address or the APN in the QoS message;

Determining, by the Diameter routing entity, an address of the found PCRF entity as the target The address of the PCRF entity.
The method according to any one of claims 1 to 3, wherein the obtaining the address of the target PCRF entity of the UE according to the QoS message comprises:

The Diameter routing entity obtains a stored default route;

The Diameter routing entity determines a routing address indicated by the default route as an address of the target PCRF entity.
The method according to any one of claims 1 to 8, wherein the Diameter routing entity is a QoS platform, or the Diameter routing entity is a Diameter Routing Agent DRA between the QoS platform and the PCRF entity. entity.
A message routing device for configuring a Diameter routing entity having a diameter Diameter routing function, wherein the device comprises:

a receiving unit, configured to receive a quality of service QoS message, where the QoS message includes an identifier of a user equipment UE and a QoS parameter of a service accessed by the UE, where the QoS parameter is used for a policy and a rule charging function, and the PCRF entity is The service accessed by the UE allocates network resources;

a processing unit, configured to obtain, according to the QoS message, an address of a target PCRF entity of the UE;

And a routing unit, configured to route the QoS message to the target PCRF entity according to the address.
The device of claim 10 wherein:

The roaming mode adopted by the UE is Home Roaming Home-routed, and the identifier of the UE is at least one of a mobile station international ISDN number MSISDN, an international mobile subscriber identity number IMSI or a public network Internet Protocol IP address of the UE; or,

The roaming mode adopted by the UE is a local roaming Local break, and the identifier of the UE is a public network IP address of the UE.
The device according to claim 11, wherein the identifier of the UE is the public network IP address of the UE, and the QoS message includes a user body for indicating that the user identity is private to the terminal. The share type Subscription-Id-Type and the user identity data Subscription-Id-Data whose value is the public network IP address.
A device according to any one of claims 10 to 12, characterized in that

The processing unit is configured to determine, according to the identifier of the UE, a segment name to which the identifier of the UE belongs;

The processing unit is further configured to: search, in the first mapping table, a segment name to which the identifier of the UE belongs, and obtain a next hop address corresponding to the segment name to which the identifier of the UE belongs, where the first mapping table includes The mapping relationship between the segment name and the next hop address;

The processing unit is further configured to determine the next hop address as an address of the target PCRF entity.
A device according to any one of claims 10 to 12, characterized in that

The processing unit is configured to determine, according to the identifier of the UE, a segment name to which the identifier of the UE belongs;

The processing unit is further configured to: search, in the second mapping table, a segment name to which the identifier of the UE belongs, and obtain a target domain identifier corresponding to the segment name to which the identifier of the UE belongs, where the second mapping table includes a segment a mapping relationship between the name and the target domain identifier, where the target domain identifier is used to indicate that the target PCRF entity is located in the Diameter domain;

The processing unit is further configured to: search the target domain identifier in the third mapping table according to the obtained target domain identifier, and obtain a next hop address corresponding to the target domain identifier, where the third mapping table And including a mapping relationship between the target hop ID and the next hop address, where the next hop address is used to indicate a Diameter routing entity, where the Diameter routing entity indicated by the next hop address is used to obtain the QoS message according to the QoS message. The address of the target PCRF entity.
The device of claim 14 wherein:

The routing unit is further configured to route the QoS message to a Diameter routing entity indicated by the next hop address.
The device according to any one of claims 10 to 12, wherein the QoS message further comprises a private network IP address or an access point name APN of the UE, and the Diameter routing entity and the target PCRF entity are directly And the corresponding relationship between the private network IP address and the PCRF entity, or the corresponding relationship between the APN and the PCRF entity;

The processing unit is configured to search for a PCRF entity corresponding to the private network IP address or the APN according to the private network IP address or the APN in the QoS message;

The processing unit is further configured to determine an address of the found PCRF entity as an address of the target PCRF entity.
A device according to any one of claims 10 to 12, characterized in that

The processing unit is configured to obtain a stored default route;

The processing unit is further configured to determine a routing address indicated by the default route as an address of the target PCRF entity.
The device according to any one of claims 10 to 17, wherein the Diameter routing entity is a QoS platform, or the Diameter routing entity is a Diameter Routing Agent DRA between the QoS platform and the PCRF entity. entity.
A Diameter routing entity configured with a diameter Diameter routing function, wherein the Diameter routing entity includes:

a receiver, configured to receive a quality of service QoS message, where the QoS message includes an identifier of a user equipment UE and a QoS parameter of a service accessed by the UE, where the QoS parameter is used for a policy and a rule charging function, and the PCRF entity is The service accessed by the UE allocates network resources;

a processor, configured to obtain an address of a target PCRF entity of the UE according to the QoS message;

And a transmitter, configured to route the QoS message to the target PCRF entity according to the address.
The Diameter routing entity of claim 19, wherein

The roaming mode adopted by the UE is Home Roaming Home-routed, and the identifier of the UE is at least one of a mobile station international ISDN number MSISDN, an international mobile subscriber identity number IMSI or a public network Internet Protocol IP address of the UE; or,

The roaming mode adopted by the UE is a local roaming Local break, and the identifier of the UE is a public network IP address of the UE.
The Diameter routing entity according to claim 20, wherein the identifier of the UE is the public network IP address of the UE, and the QoS message is used to indicate that the user identity is the end. The terminal-private user identity type Subscription-Id-Type and the user identity data Subscription-Id-Data whose value is the public network IP address.
A Diameter routing entity according to any one of claims 19 to 21, characterized in that

The processor is configured to determine, according to the identifier of the UE, a segment name to which the identifier of the UE belongs;

The processor is further configured to: search, in the first mapping table, a segment name to which the identifier of the UE belongs, and obtain a next hop address corresponding to the segment name to which the identifier of the UE belongs, where the first mapping table includes The mapping relationship between the segment name and the next hop address;

The processor is further configured to determine the next hop address as an address of the target PCRF entity.
A Diameter routing entity according to any one of claims 19 to 21, characterized in that

The processor is configured to determine, according to the identifier of the UE, a segment name to which the identifier of the UE belongs;

The processor is further configured to: search, in a second mapping table, a segment name to which the identifier of the UE belongs, and obtain a target domain identifier corresponding to a segment name to which the identifier of the UE belongs, where the second mapping table includes a segment a mapping relationship between the name and the target domain identifier, where the target domain identifier is used to indicate that the target PCRF entity is located in the Diameter domain;

The processor is further configured to: search, according to the obtained target domain identifier, the target domain identifier in a third mapping table, obtain a next hop address corresponding to the target domain identifier, and the third mapping table And including a mapping relationship between the target hop ID and the next hop address, where the next hop address is used to indicate a Diameter routing entity, where the Diameter routing entity indicated by the next hop address is used to obtain the QoS message according to the QoS message. The address of the target PCRF entity.
The Diameter routing entity of claim 23, wherein

The transmitter is further configured to route the QoS message to a Diameter routing entity indicated by the next hop address.
The Diameter routing entity according to any one of claims 19 to 21, wherein the QoS message further includes a private network IP address or an access point name APN of the UE, the Diameter routing entity and the target PCRF. The entity is directly connected, and the Diameter routing entity stores a correspondence between the private network IP address and the PCRF entity, or a corresponding relationship between the APN and the PCRF entity;

The processor is configured to check according to the private network IP address or the APN in the QoS message. Finding a PCRF entity corresponding to the private network IP address or the APN;

The processor is further configured to determine an address of the found PCRF entity as an address of the target PCRF entity.
A Diameter routing entity according to any one of claims 19 to 21, characterized in that

The processor is configured to obtain, by the Diameter routing entity, a stored default route;

The processor is further configured to determine a routing address indicated by the default route as an address of the target PCRF entity.
The Diameter routing entity according to any one of claims 19 to 26, wherein the Diameter routing entity is a QoS platform, or the Diameter routing entity is a diameter route between the QoS platform and the PCRF entity. Proxy DRA entity.