WO2017147840A1 - Procédé et dispositif d'acheminement de message, et entité d'acheminement diameter - Google Patents

Procédé et dispositif d'acheminement de message, et entité d'acheminement diameter Download PDF

Info

Publication number
WO2017147840A1
WO2017147840A1 PCT/CN2016/075457 CN2016075457W WO2017147840A1 WO 2017147840 A1 WO2017147840 A1 WO 2017147840A1 CN 2016075457 W CN2016075457 W CN 2016075457W WO 2017147840 A1 WO2017147840 A1 WO 2017147840A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
entity
qos
identifier
target
Prior art date
Application number
PCT/CN2016/075457
Other languages
English (en)
Chinese (zh)
Inventor
柳清芬
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2016/075457 priority Critical patent/WO2017147840A1/fr
Publication of WO2017147840A1 publication Critical patent/WO2017147840A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service

Definitions

  • 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.
  • 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.
  • QoS Quality of Service
  • UE User Equipment
  • different OTT services in the service server are pre-configured with different QoS parameters.
  • the service server responds to the UE access according to the QoS parameter corresponding to the OTT service accessed by the UE.
  • 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.
  • 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.
  • the embodiment of the invention provides a message routing method, device and Diameter routing entity.
  • the technical solution is as follows:
  • 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)
  • PCRF Policy ang Charging Rules Function
  • 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.
  • the service server 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.
  • 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.
  • 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.
  • the identifier of the UE is a public network IP address of the UE
  • the QoS message includes, to indicate that the user identity is private to the terminal.
  • User identity type English: Subscription-Id-Type
  • user identity data English: Subscription-Id-Data
  • 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
  • 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.
  • 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.
  • the mapping relationship between the segment name and the next hop address is pre-configured in the Diameter routing entity.
  • 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.
  • the UE is obtained according to the QoS message.
  • the address of the target PCRF entity including:
  • 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.
  • 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.
  • 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.
  • 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.
  • the Diameter routing entity 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.
  • 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.
  • APN Access Point Name
  • 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.
  • 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.
  • 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.
  • the QoS message can be routed to the PCRF entity, ensuring the quality of service of the UE accessing the service.
  • 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.
  • DRA Diameter Routing Agent
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 1 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.
  • FIG. 2 shows the structure of a Diameter routing entity provided by an embodiment of the present invention.
  • 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.
  • Network interfaces 12 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 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.
  • 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.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read only Memory
  • EPROM erasable programmable read only memory
  • PROM programmable read-only memory
  • ROM read only memory
  • magnetic memory flash memory, disk or optical disk.
  • 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.
  • the Diameter routing entity is used as a QoS platform or a DRA entity as an example.
  • FIG. 3 is a flowchart of a method for a message routing method according to an embodiment of the present invention.
  • 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.
  • 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.
  • the message routing method 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.
  • 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.
  • the MSISDN with the UE's identity is the UE is taken as an example for illustration, and the present invention is not limited.
  • FIG. 4 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:
  • 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.
  • 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.
  • 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.
  • the segment name is an MSISDN number segment name
  • the MSISDN segment name is used to indicate a segment of a predetermined length in the MSISDN.
  • the identifier included in the QoS message obtained by the QoS platform is “86138120912345”
  • 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).
  • 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.
  • the MSISDN number segment start number and the end number 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.
  • the application type is Rx.
  • the priority is used to indicate the priority of each MSISDN segment name.
  • 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.
  • step 405 the QoS platform determines the next hop address as the address of the target PCRF entity.
  • 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.
  • 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.
  • 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.
  • 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.
  • the PCRF entity can preferentially guarantee the quality of service of the UE to access the valuable service.
  • the message routing method 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.
  • 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.
  • 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.
  • FIG. 5 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:
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the priority (optional parameter) is used to indicate the priority of each MSISDN segment name.
  • the MSISDN segment name with a higher priority is selected.
  • 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.
  • the QoS platform 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.
  • Target domain identifier Default route App types Next hop address Diameter001 - Rx Address C Diameter002 - Rx Address D Diameter003 - Rx Address E
  • the default route (optional parameter) is the route corresponding to the specified application.
  • the default route can be configured for the specified application.
  • 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.
  • 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.
  • the first mapping table, the second mapping table, and the third mapping table are also configured in the DRA entity in the carrier network.
  • the DRA entity 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.
  • 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.
  • next hop address corresponds 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.
  • the QoS message sent by the QoS platform to the DRA entity includes the target domain identifier obtained by the above step 505.
  • 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.
  • 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.
  • the PCRF entity can preferentially guarantee the quality of service of the UE to access the valuable service.
  • the message routing method 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.
  • 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.
  • the QoS platform or the DRA entity
  • the QoS platform 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.
  • step 512 the QoS platform obtains the stored default route.
  • the QoS platform 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.
  • step 513 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.
  • 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.
  • 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.
  • 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.
  • FIG. 6 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:
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • step 609 the DRA entity routes the QoS message to the DRA entity directly connected to the target PCRF entity.
  • the DRA entity 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.
  • the DRA entity directly connected to the PCRF entity 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.
  • 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.
  • the target PCRF entity 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.
  • the message routing method 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.
  • 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.
  • 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).
  • 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.
  • 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.
  • the following describes an example of a message routing method in a Local break roaming scenario.
  • FIG. 7 is a flowchart of a method for a message routing method according to still another embodiment of the present invention.
  • the roaming mode adopted by the UE is a local break
  • the DRA entity directly connected to the PCRF entity has a session binding function as an example.
  • the method includes:
  • step 701 the service server sends QoS information to the QoS platform.
  • the service server when the service server receives the access request of the UE, the service server obtains the public network IP address of the UE.
  • 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.
  • 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.
  • 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.
  • 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.
  • the start IP address and the end IP address 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 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. .
  • the QoS platform 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.
  • 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.
  • IP address segment name priority Target domain identifier App types 192.168.16.0 - Diameter001 Rx 192.168.16.18 - Diameter002 Rx 192.168.16.19 - Diameter003 Rx ... ... ... ... ...
  • the priority (optional parameter) is used to indicate the priority of each 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 QoS control platform searches for the corresponding target domain identifier in the second mapping table according to the IP address segment name.
  • 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.
  • 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.
  • the QoS platform 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.
  • 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.
  • 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.
  • 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 message routing method 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.
  • 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.
  • FIG. 8 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.
  • 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.
  • the identifier of the UE is a public network IP address of the UE
  • 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.
  • 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 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 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.
  • the routing unit 830 is further configured to route the QoS message to the Diameter routing entity indicated by the next hop address.
  • 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.
  • 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.
  • 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.
  • the message routing apparatus 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation de la présente invention concernent un procédé et un dispositif d'acheminement de message, et une entité d'acheminement diameter, appartenant au domaine de l'Internet Le procédé d'acheminement de message comprend les étapes suivantes : une entité d'acheminement diameter reçoit un message de qualité de service (QoS) contenant un identifiant d'un UE et un paramètre QoS d'un service auquel l'UE accède, le paramètre QoS étant utilisé par une entité PCRF pour attribuer des ressources réseau au service auquel l'UE accède ; l'entité d'acheminement diameter obtient une adresse d'une entité PCRF cible de l'UE d'après le message QoS ; l'entité d'acheminement diameter achemine le message QoS vers l'entité PCRF cible, d'après l'adresse. Au moyen de la présente invention, une entité PCRF dans un réseau peut attribuer des ressources réseau à un UE, d'après l'UE et un service auquel l'UE accède, ce qui permet de garantir la qualité de service d'un service de valeur.
PCT/CN2016/075457 2016-03-03 2016-03-03 Procédé et dispositif d'acheminement de message, et entité d'acheminement diameter WO2017147840A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/075457 WO2017147840A1 (fr) 2016-03-03 2016-03-03 Procédé et dispositif d'acheminement de message, et entité d'acheminement diameter

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/075457 WO2017147840A1 (fr) 2016-03-03 2016-03-03 Procédé et dispositif d'acheminement de message, et entité d'acheminement diameter

Publications (1)

Publication Number Publication Date
WO2017147840A1 true WO2017147840A1 (fr) 2017-09-08

Family

ID=59742496

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/075457 WO2017147840A1 (fr) 2016-03-03 2016-03-03 Procédé et dispositif d'acheminement de message, et entité d'acheminement diameter

Country Status (1)

Country Link
WO (1) WO2017147840A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113473417A (zh) * 2021-06-01 2021-10-01 中国电信股份有限公司 访问业务的处理方法及装置、存储介质、电子设备
CN116383669A (zh) * 2023-03-18 2023-07-04 宝钢工程技术集团有限公司 一种数据贯通的工厂对象位号标识生成方法及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011110020A1 (fr) * 2010-09-26 2011-09-15 华为技术有限公司 Procédé et système pour sélectionner un contrôleur de politique et un agent de routage diameter
WO2014101228A1 (fr) * 2012-12-31 2014-07-03 华为技术有限公司 Système, passerelle, serveur mandataire et procédé de présentation de capacités d'un réseau sans fil
CN104105082A (zh) * 2013-04-01 2014-10-15 华为技术有限公司 计费策略信息生成方法及策略与计费制定功能实体

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011110020A1 (fr) * 2010-09-26 2011-09-15 华为技术有限公司 Procédé et système pour sélectionner un contrôleur de politique et un agent de routage diameter
WO2014101228A1 (fr) * 2012-12-31 2014-07-03 华为技术有限公司 Système, passerelle, serveur mandataire et procédé de présentation de capacités d'un réseau sans fil
CN104105082A (zh) * 2013-04-01 2014-10-15 华为技术有限公司 计费策略信息生成方法及策略与计费制定功能实体

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "C3-153457: Correction on Bearer Binding on QoS Rules", 3GPP TSG CT3 MEETING #82, 21 August 2015 (2015-08-21), XP050998694 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113473417A (zh) * 2021-06-01 2021-10-01 中国电信股份有限公司 访问业务的处理方法及装置、存储介质、电子设备
CN113473417B (zh) * 2021-06-01 2022-08-19 中国电信股份有限公司 访问业务的处理方法及装置、存储介质、电子设备
CN116383669A (zh) * 2023-03-18 2023-07-04 宝钢工程技术集团有限公司 一种数据贯通的工厂对象位号标识生成方法及系统
CN116383669B (zh) * 2023-03-18 2024-04-16 宝钢工程技术集团有限公司 一种数据贯通的工厂对象位号标识生成方法及系统

Similar Documents

Publication Publication Date Title
CN109315004B (zh) Pdu类型的设置方法及相关实体
JP6995189B2 (ja) データ伝送方法、デバイス、およびシステム
US11916869B2 (en) Domain name system server determining method, and request processing method, apparatus, and system
US9021073B2 (en) IP pool name lists
EP2499787B1 (fr) Routage de client intelligent
WO2016091009A1 (fr) Procédé et dispositif d'acquisition et d'affectation d'adresse
WO2018112759A1 (fr) Procédé, appareil, et système d'accès à des ressources
WO2017143859A1 (fr) Procédé de transmission de données, équipement de réseau et terminal
CN105075226A (zh) 用于使用直径路由代理(dra)来获得移动订户标识信息和动态分配的互联网协议(ip)地址之间的映射以及用于使得该映射可被应用访问的方法、系统和计算机可读介质
US11533275B2 (en) Method and apparatus for allocating server in wireless communication system
US20050120350A1 (en) Load balancer for multiprocessor platforms
US10863555B2 (en) Access method, apparatus, device, and system
CN105101176B (zh) 一种漫游场景下的会话绑定方法、装置和系统
US11108832B2 (en) Network component selection based on device identifier
CN109644335B (zh) 一种标识信息的处理方法、数据库控制系统以及相关设备
US11871309B2 (en) Methods, systems, and computer readable media for network function discovery using preferred-locality information
CN106507414B (zh) 报文转发方法及装置
KR20200130043A (ko) 에지 컴퓨팅 서비스에서 단말의 식별자 관리 방법 및 장치
WO2016202059A1 (fr) Procédé d'accès à un réseau ipv6 et passerelle
CN111866201B (zh) IPv6组播地址的生成方法和装置
WO2017147840A1 (fr) Procédé et dispositif d'acheminement de message, et entité d'acheminement diameter
CN116866297A (zh) 双域专网的地址匹配方法、装置、通信设备和存储介质
WO2018049690A1 (fr) Procédé, appareil et système d'émission de paquets
US11196666B2 (en) Receiver directed anonymization of identifier flows in identity enabled networks
WO2024073921A1 (fr) Procédé et appareil de prise en charge de périphérie

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16892031

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 16892031

Country of ref document: EP

Kind code of ref document: A1