WO2015058549A1 - 业务同步方法、内容管理设备及策略管理设备 - Google Patents

业务同步方法、内容管理设备及策略管理设备 Download PDF

Info

Publication number
WO2015058549A1
WO2015058549A1 PCT/CN2014/081059 CN2014081059W WO2015058549A1 WO 2015058549 A1 WO2015058549 A1 WO 2015058549A1 CN 2014081059 W CN2014081059 W CN 2014081059W WO 2015058549 A1 WO2015058549 A1 WO 2015058549A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
sub
management device
policy
identifier
Prior art date
Application number
PCT/CN2014/081059
Other languages
English (en)
French (fr)
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 华为技术有限公司
Publication of WO2015058549A1 publication Critical patent/WO2015058549A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/61—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on the service used
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system

Definitions

  • the present invention relates to the field of wireless communications, and in particular, to a service synchronization method, a content management device, and a policy management device. Background technique
  • the embodiment of the present invention provides a service synchronization method, a content management device, and a policy management device, to implement an automatic synchronization service between devices, and generate a corresponding service policy for the service.
  • an embodiment of the present invention provides a service synchronization method, including:
  • the content management device obtains the identifier of the sub-service and the identifier of the parent service of the sub-service; the content management device sends the service identifier information to the policy management device, where the service identifier
  • the information includes the identifier of the sub-service and the identifier of the parent service of the sub-service, so that the policy management device obtains the sub-service according to the identifier of the sub-service and the identifier of the parent service of the sub-service A hierarchical relationship of the parent service, and obtaining a business policy of the child service according to the hierarchical relationship.
  • the content management device is a traffic identification function unit TDF or a gateway
  • the policy management device is an online charging system OCS or a policy and charging rule function unit PCRF
  • the service identification information further includes at least one of the following information: a hierarchical type of the sub-service and hierarchical information of the sub-service;
  • the hierarchical type is used to indicate that the sub-service is a top-level sub-service, a leaf layer sub-service, or an intermediate layer sub-service;
  • the hierarchical information of the sub-service is used to indicate the level of the sub-service.
  • an embodiment of the present invention provides a service synchronization method, including:
  • the first policy management device receives the service identification information sent by the content management device, where the service identification information includes an identifier of the sub-service and an identifier of the parent service of the sub-service;
  • the first policy management device obtains a service policy of the sub-service according to the hierarchical relationship.
  • the first policy management device obtains the service policy of the sub-service according to the hierarchical relationship, including:
  • the first policy management device obtains at least one upper layer service of the child node according to the hierarchical relationship, where the at least one upper layer service includes the parent service;
  • the first policy management device obtains, according to the at least one upper-layer service, an upper-layer service with a minimum number of levels and a service policy between the sub-services, as a reference upper-layer service;
  • the method further includes: the first policy management device sending the service identification information to the second policy management device, where the service identification information includes The identifier of the sub-service and the identifier of the parent service of the sub-service, so that the second policy management device obtains the sub-service and the identifier according to the identifier of the sub-service and the identifier of the parent service of the sub-service a hierarchical relationship of the parent service, and obtaining a business policy of the child service according to the hierarchical relationship;
  • the first policy management device is an OCS
  • the second policy management device is a PCRF
  • the first policy management device is a PCRF
  • the second policy management device is an OCS
  • an embodiment of the present invention provides a content management device, including:
  • a processing unit configured to obtain an identifier of a sub-service and an identifier of a parent service of the sub-service; a sending unit, configured to send service identifier information to the policy management device, where the service identifier information includes an identifier of the sub-service and the An identifier of the parent service of the child service, so that the policy management device obtains a hierarchical relationship between the child service and the parent service according to the identifier of the child service and the identifier of the parent service of the child service, and the basis The hierarchical relationship is obtained, and the business strategy of the sub-service is obtained.
  • the content management device is a TDF or a gateway; and the policy management device is an OCS or a PCRF.
  • the service identification information further includes at least one of the following information: a hierarchical type of the sub-service and hierarchical information of the sub-service;
  • the hierarchical type is used to indicate that the sub-service is a top-level sub-service, a leaf layer sub-service, or an intermediate layer sub-service;
  • the hierarchical information of the sub-service is used to indicate the level of the sub-service.
  • an embodiment of the present invention provides a policy management device, including:
  • a receiving unit configured to receive service identifier information sent by the content management device, where the service identifier information includes an identifier of the sub-service and an identifier of the parent service of the sub-service; a first processing unit, configured to obtain, according to the identifier of the sub-service and the identifier of the parent service of the sub-service, a hierarchical relationship between the sub-service and the parent service;
  • the second processing unit is configured to obtain a service policy of the sub-service according to the hierarchical relationship.
  • the second processing unit further includes: a first processing module, configured to obtain, according to the hierarchical relationship, at least one upper layer service of the child node, where the at least one The parent service is included in an upper layer service;
  • a second processing module configured to obtain, according to the at least one upper layer service, an upper layer service with a minimum number of levels and a service policy between the sub-services, as a reference upper layer service;
  • a third processing module configured to obtain a service policy of the sub-service according to the service policy of the reference upper-layer service.
  • the policy management device further includes:
  • a sending unit configured to send the service identifier information to the second policy management device, where the service identifier information includes an identifier of the sub-service and an identifier of the parent service of the sub-service, so that the second policy management device is configured according to the Determining the identifier of the sub-service and the identifier of the parent service of the sub-service, obtaining a hierarchical relationship between the sub-service and the parent service, and obtaining a service policy of the sub-service according to the hierarchical relationship;
  • the policy management device is an OCS, and the second policy management device is a PCRF; or the policy management device is a PCRF, and the second policy management device is an OCS.
  • the present invention has the following beneficial effects:
  • the policy management device can automatically generate the hierarchical relationship between the services according to the identifiers of the sub-services and the identifiers of the parent services reported by the content management device, and obtain the business policies of the sub-services in time according to the hierarchical relationship, thereby realizing automatic synchronization of the services, thereby reducing the number of customers.
  • the abnormality that occurs when the service is used by the terminal reduces the cost of the manual maintenance service and saves manpower and material resources. At the same time, it can ensure the consistency of service synchronization between devices, which is beneficial to the maintenance and operation of services.
  • FIG. 1 is a schematic flowchart of a service synchronization method 1 according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of a service synchronization method 2 according to an embodiment of the present invention
  • FIG. 3 (a) is a service provided by an embodiment of the present invention
  • FIG. 3(b) is a schematic structural diagram of a service synchronization system according to an embodiment of the present invention
  • FIG. 4 is a diagram showing an example of obtaining a hierarchical relationship between a sub-service and a parent service by the policy management device of the present invention
  • FIG. 5 is a schematic flowchart of Embodiment 2 of a service synchronization method according to an embodiment of the present invention
  • FIG. 6 is a schematic flowchart of Embodiment 3 of a service synchronization method according to an embodiment of the present invention
  • a functional block diagram of the provided content management device
  • FIG. 8 is a schematic structural diagram of a content management device according to an embodiment of the present invention.
  • FIG. 9 is a functional block diagram of a policy management device according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of a policy management device according to an embodiment of the present invention. detailed description
  • the embodiment of the present invention provides a service synchronization method.
  • FIG. 1 it is a schematic flowchart of a service synchronization method 1 according to an embodiment of the present invention. As shown in the figure, the method includes the following steps: Step 101, content management The device obtains the identity of the child service and the identity of the parent service of the child service.
  • Step 102 The content management device sends service identifier information to the policy management device, where the service identifier information includes an identifier of the sub-service and an identifier of a parent service of the sub-service, so that the policy management device is configured according to the The identifier of the sub-service and the identifier of the parent service of the sub-service, obtain a hierarchical relationship between the sub-service and the parent service, and obtain a service policy of the sub-service according to the hierarchical relationship.
  • the service identification information may further include at least one of the following information: a hierarchical type of the sub-service and a hierarchical information of the sub-service; and a hierarchical type of the sub-service is used to indicate that the sub-service is The top level sub-service, the leaf layer sub-service or the middle-layer sub-service; the hierarchical information of the sub-service is used to indicate the level of the sub-service.
  • the content management device is a traffic detection function (TDF) or a gateway
  • the policy management device is an OCS or a Policy and Charging Rules Function (PCRF).
  • TDF traffic detection function
  • PCRF Policy and Charging Rules Function
  • the gateway may be a Gateway (General Packet Radio Service, GPRS) Supporting Node (SGSN), or a Packet Data Network Gateway (P-GW). It can also be a Serving Gateway (S-GW) or the like.
  • GPRS General Packet Radio Service
  • P-GW Packet Data Network Gateway
  • S-GW Serving Gateway
  • the service policy includes a charging policy and/or an access bandwidth policy.
  • the embodiment of the present invention provides a service synchronization method.
  • FIG. 2 it is a schematic flowchart of a service synchronization method 2 according to an embodiment of the present invention. As shown in the figure, the method includes the following steps: Step 201, The policy management device receives the service identification information sent by the content management device, where the service identification information includes an identifier of the sub-service and an identifier of the parent service of the sub-service.
  • the service identification information further includes at least one of the following information: a hierarchical type of the sub-service and a hierarchical information of the sub-service; and a hierarchical type of the sub-service is used to indicate that the sub-service is a top-level The sub-service, the leaf layer sub-service or the middle-layer sub-service; the hierarchical information of the sub-service is used to indicate the level of the sub-service.
  • Step 202 The first policy management device is configured according to the identifier of the sub-service and the sub-service The identity of the parent business, obtaining the hierarchical relationship between the child business and the parent business.
  • Step 203 The first policy management device obtains a service policy of the sub-service according to the hierarchical relationship.
  • the first policy management device obtains, according to the hierarchical relationship, at least one upper layer service of the child node, where the at least one upper layer service includes the parent service; And obtaining, by the first policy management device, the sub-service according to the service policy of the reference upper-layer service, where the at least one upper-layer service obtains an upper-layer service with a minimum number of tiers and a service policy.
  • Business strategy for the business for the business.
  • the service policy includes a charging policy and/or an access bandwidth policy.
  • the content management device is a TDF or a gateway, and the first policy management device is an OCS; or the content management device is a TDF or a gateway, and the first policy management device is a PCRF.
  • the method further includes: the first policy management device sending the service identification information to the second policy management device, where the service identification information includes an identifier of the sub-service and the sub-service The identifier of the parent service, so that the second policy management device obtains the hierarchical relationship between the child service and the parent service according to the identifier of the child service and the identifier of the parent service of the child service, and the basis The hierarchical relationship, the service policy of the sub-service is obtained, where the first policy management device is an OCS, and the second policy management device is a PCRF; or the first policy management device is a PCRF, The second policy management device is OCS.
  • FIG. 3 (a) is a schematic flowchart of Embodiment 1 of the service synchronization method according to the embodiment of the present invention
  • FIG. 3 (b) is provided by the embodiment of the present invention.
  • the architecture of the service synchronization system is as follows:
  • the content management device is a TDF or a GGSN
  • the first policy management device is an OCS
  • the second policy management device is a PCRF.
  • the method includes the following steps:
  • Step 301 When a new sub-service needs to be launched, the new sub-service, the identifier of the sub-service, the correspondence between the sub-service and the identifier of the sub-service, and the corresponding relationship are configured on the TDF or the GGSN. The correspondence between the identity of the child service and the identity of the parent service.
  • Step 302 When the client needs to access the sub-service on the Internet, the client sends a service access request to the TDF or the GGSN, where the address of the sub-service is included.
  • Step 303 The TDF or the GGSN receives the service access request message sent by the client, performs DPI identification processing on the address of the sub-service included therein, and obtains the sub-service requesting the access; the correspondence between the TDF or the GGSN from the identifier of the sub-service and the sub-service Obtaining an identifier corresponding to the sub-service according to the identifier corresponding to the sub-service, and obtaining an identifier of the parent service of the sub-service from the correspondence between the identifier of the sub-service and the identifier of the parent service.
  • Step 304 The TDF or the GGSN sends an accounting request message to the OCS through the Gy interface, where the charging request message includes service identification information, where the service identification information includes an identifier of the sub-service and an identifier of the parent service of the sub-service.
  • the Gy interface between the TDF and the OCS or the Gy interface between the GGSN and the OCS is extended, so that the TDF or the GGSN can be sent to the OCS through the Gy interface.
  • the charging request message can carry the service identification information.
  • the service identification information can be an Attribute Value Pair (AVP) set, and the attribute value pair set includes at least two AVPs, as shown in Table 1:
  • Serviceid-lnformation indicates the name of the field when the service identifier information is used as a field in the accounting request message;
  • Service-id is the identifier of the sub-service, that is, 22337;
  • Parent-Service-id is the parent service of the child service.
  • Identification ie 32301.
  • the service identification information may further include at least one of the following information:
  • Service-id-layer and Service-id-Type are the hierarchical information of the sub-service, indicating the level of the sub-service in the service tree;
  • Service-id-Type is the level of the sub-service Type, which indicates that the sub-service is a top-level sub-service, a leaf-layer sub-service, or an intermediate-layer sub-service;
  • Service-id-layer and Service-id-Type can facilitate the location of the sub-service quickly found in the OCS in the service tree. The speed at which OCS obtains the hierarchical relationship between the child business and the parent business.
  • Step 305 The OCS obtains a hierarchical relationship between the sub-service and the parent service according to the identifier of the sub-service and the identifier of the parent service of the sub-service, and obtains the billing of the sub-service according to the tier-level relationship. Strategy.
  • the OCS has an adaptive learning capability, and the sub-service is not required to be configured on the OCS, and the OCS can obtain the sub-service and the parent service according to the identifier of the sub-service and the identifier of the parent service of the sub-service.
  • a hierarchical relationship and then the sub-service is hanged under the parent service in the existing service tree, indicating that the sub-service is a sub-service of the parent service, so that the OCS can automatically add the sub-service in the service tree. Realize automatic update and storage of sub-services.
  • the OCS can obtain the charging policy of the sub-service according to the hierarchical relationship between the sub-service and the parent service. For example, the OCS first searches for the charging policy of the sub-service in the locally saved business policy, and if not, the local If the accounting policy of the sub-service is not configured, the OCS searches for the charging policy of the parent service of the sub-service.
  • the charging policy of the parent service can be used as the charging policy of the sub-service.
  • the charging policy of the grandparent service of the sub-service is used as the charging policy of the sub-service, and so on; wherein the charging policy may include the sub-service Reservation of price and/or sub-services, for example, traffic reservation or balance reservation of sub-services.
  • TDF or GGSN when the client needs to access "Sina video", TDF or GGSN sends the "Sina video” logo (ServicelDI) and the “Sina” logo (ServicelDO) to the OCS via the Gy interface, indicating "Sina” "It is the parent business of "Sina Video", so you can get the hierarchical relationship between "Sina” and "Sina Video”; OCS adds the sub-service "Sina video” in the business tree according to the logo of "Sina Video” and the logo of "Sina” ", get the business tree shown in Figure 4, where "Sina Video", “Sina Weibo", “Sina News” and “Sina Go” are all sub-services of "Sina”.
  • Step 306 The OCS sends a service authorization message to the TDF or the GGSN, where the Granted Service Unit (GSU) and the identifier of the sub-service are carried.
  • GSU Granted Service Unit
  • the method may further include:
  • Step 307 The OCS sends a bandwidth request message to the PCRF through the Sy interface, where the bandwidth request message includes service identifier information, where the service identifier information includes an identifier of the sub-service and an identifier of the parent service of the sub-service.
  • the OCS sends the identifier of the sub-service (ServicelDI) and the identity of the parent service (ServicelDO) to the PCRF.
  • ServicelDI the identifier of the sub-service
  • ServicelDO the identity of the parent service
  • the format of the service identifier information included in the bandwidth request message sent by the Sy can be as shown in Table 1.
  • Step 308 The PCRF obtains a hierarchical relationship between the sub-service and the parent service according to the identifier of the sub-service and the identifier of the parent service of the sub-service, and obtains the sub-service according to the hierarchical relationship between the sub-service and the parent service in the service tree. Access bandwidth policy.
  • the PCRF has an adaptive learning capability, and does not need to configure a sub-service on the PCRF.
  • the PCRF may obtain the hierarchical relationship between the sub-service and the parent service according to the identifier of the sub-service and the identifier of the parent service of the sub-service, and then hang the sub-service to the local service tree.
  • the sub-service is a sub-service of the parent service, so that the PCRF can automatically add sub-services in the service tree to implement automatic update and storage of the sub-services.
  • Sina Video is a sub-business of Sina.
  • the business tree there is a hierarchical relationship between Sina Video and Sina.
  • OCS The Sy interface is used to send the ID of the Sina video and the ID of the Sina to the PCRF, and report the hierarchical relationship between the Sina video and the Sina service to the PCRF to synchronize the newly released service to the PCRF.
  • the PCRF can obtain the access bandwidth policy of the sub-service according to the hierarchical relationship between the sub-service and the parent service. For example, the PCRF first searches for the access bandwidth policy of the sub-service in the locally saved service policy, and if not, the local If the access bandwidth policy of the sub-service is not configured, the PCRF searches for the access bandwidth policy of the parent service of the sub-service, and the access bandwidth policy of the parent service is used as the access bandwidth policy of the sub-service; Then, the access bandwidth policy of the grandparent service of the sub-service is used as the access bandwidth policy of the sub-service, and so on; the PCRF may send the automatically obtained access bandwidth policy to the PCEF, so that the PCEF executes the access bandwidth policy.
  • FIG. 5 is a schematic flowchart of Embodiment 1 of a service synchronization method according to an embodiment of the present invention.
  • a content management device is a TDF or a GGSN
  • a first policy management device is a PCRF.
  • the method includes the following steps: Step 501: Pre-configure a correspondence between the sub-service and the identifier of the sub-service in the TDF or the GGSN.
  • Step 502 When the client needs to access the sub-service on the Internet, the client sends a service access request to the TDF or the GGSN, where the address of the sub-service is included.
  • Step 503 The TDF or the GGSN receives the service access request message sent by the client, performs DPI identification processing on the address of the sub-service included therein, and obtains the sub-service requesting the access; the correspondence between the TDF or the GGSN from the identifier of the sub-service and the sub-service Obtaining an identifier corresponding to the sub-service according to the identifier corresponding to the sub-service, and obtaining an identifier of the parent service of the sub-service from the correspondence between the identifier of the sub-service and the identifier of the parent service.
  • Step 504 The TDF or the GGSN sends a bandwidth request message to the PCRF through the Sd interface, where the bandwidth request message includes service identifier information, where the service identifier information includes an identifier of the sub-service and an identifier of the parent service of the sub-service.
  • the Sd interface between the TDF and the PCRF or the Sd interface between the GGSN and the OCS is extended, so that the TDF or the GGSN can be sent to the OCS through the Sd interface.
  • the service request information can be carried in the charging request message.
  • the service identification information may further include at least one of the following information:
  • Service-id-layer and Service-id-Type are the hierarchical information of the sub-service, indicating the level of the sub-service in the service tree;
  • Service-id-Type is the level of the sub-service Type, used to indicate that the sub-service is a top-level sub-service, a leaf-layer sub-service, or an intermediate-layer sub-service;
  • the Service-id-layer and the Service-id-Type can facilitate the location where the OCS quickly finds the sub-service in the service tree. , to improve the speed at which OCS obtains the hierarchical relationship between the child business and the parent business.
  • Step 505 The PCRF obtains a hierarchical relationship between the sub-service and the parent service according to the identifier of the sub-service and the identifier of the parent service of the sub-service, and obtains an access bandwidth of the sub-service according to the hierarchical relationship. Strategy.
  • the PCRF has an adaptive learning capability, and the sub-service is not required to be configured on the PCRF.
  • the PCRF can obtain the sub-service and the parent service according to the identifier of the sub-service and the identifier of the parent service of the sub-service. Hierarchical relationship, then hang the sub-service to a local existing service Below the parent service in the tree, the sub-service is a sub-service of the parent service, so that the PCRF can automatically add sub-services in the service tree to implement automatic update and storage of the sub-services.
  • the PCRF can obtain the access bandwidth policy of the sub-service according to the hierarchical relationship between the sub-service and the parent service. For example, the PCRF first searches for the access bandwidth policy of the sub-service in the locally saved service policy, and if not, the local If the access bandwidth policy of the sub-service is not configured, the OCS searches for the access bandwidth policy of the parent service of the sub-service, and the access bandwidth policy of the parent service is used as the access bandwidth policy of the sub-service; if the parent service does not configure the access bandwidth.
  • the policy is to use the access bandwidth policy of the grandparent service of the sub-service as the access bandwidth policy of the sub-service, and so on.
  • TDF or GGSN when the client needs to access "Sina video", TDF or GGSN sends the "Sina video” logo (ServicelDI) and the “Sina” logo (ServicelDO) to the PCRF via the Gy interface, indicating "Sina” "Yes” is the parent business of "Sina Video", so that you can get the hierarchical relationship between "Sina” and "Sina Video”; PCRF adds the sub-service "Sina video” in the business tree according to the "Sina video” logo and the "Sina” logo. ", get the business tree shown in Figure 4, where "Sina Video", “Sina Weibo", “Sina News” and “Sina Go” are all sub-businesses of "Sina”.
  • Step 506 The PCRF sends an execution request message to the PCEF, where the identifier of the sub-service and the access bandwidth policy of the sub-service, so that the PCEF performs the access bandwidth policy.
  • the method may further include:
  • Step 507 The PCRF sends an accounting request message to the OCS through the Sy interface, where the charging request message includes service identification information, where the service identification information includes an identifier of the sub-service and an identifier of the parent service of the sub-service.
  • the format of the service identification information included in the charging request message sent by the Sy may be as shown in Table 1.
  • the PCRF sends a charging request message to the PCEF through the Gx interface, where the charging request message includes service identification information, where the service identification information includes an identifier of the sub-service and an identifier of the parent service of the sub-service; And sending, by the Gy interface, the charging request message includes the service identification information, where the service identification information includes an identifier of the sub-service and an identifier of the parent service of the sub-service.
  • Step 508 The OCS obtains a hierarchical relationship between the sub-service and the parent service according to the identifier of the sub-service and the identifier of the parent service of the sub-service, and obtains the sub-service according to the hierarchical relationship between the sub-service and the parent service in the service tree. Billing strategy.
  • the OCS has an adaptive learning capability, and the sub-service is not required to be configured on the OCS, and the OCS can obtain the sub-service and the parent service according to the identifier of the sub-service and the identifier of the parent service of the sub-service.
  • a hierarchical relationship and then the sub-service is hanged under the parent service in the existing service tree, indicating that the sub-service is a sub-service of the parent service, so that the OCS can automatically add the sub-service in the service tree. Realize automatic update and storage of sub-services.
  • Sina is an Internet business.
  • Sina Video is a sub-business of Sina.
  • the business tree there is a hierarchical relationship between Sina Video and Sina.
  • PCRF Sending the ID of the Sina video and the logo of Sina to the OCS through the Sy interface, for reporting the hierarchical relationship between the Sina video and the Sina service to the OCS, and realizing the newly released service to the OCS.
  • the OCS can obtain the charging policy of the sub-service according to the hierarchical relationship between the sub-service and the parent service. For example, the OCS first searches for the charging policy of the sub-service in the locally saved business policy, such as If there is no, indicating that the local service has not configured the charging policy of the sub-service, the OCS searches for the charging policy of the parent service of the sub-service, and the charging policy of the parent service is used as the charging policy of the sub-service; If the charging policy is not configured, the charging policy of the grandparent service of the sub-service is used as the charging policy of the sub-service, and so on; the OCS performs charging of the sub-service according to the charging policy that is automatically obtained.
  • Step 509 The OCS sends a service authorization message to the TDF or the GGSN, where the GSU and the identifier of the sub-service are carried.
  • FIG. 6 is a schematic flowchart of Embodiment 3 of a service synchronization method according to an embodiment of the present invention.
  • a content management device is a TDF or a GGSN
  • at least one first policy management device includes a PCRF and an OCS.
  • the method includes the following steps:
  • Step 601 Pre-configure a correspondence between the sub-service and the identifier of the sub-service in the TDF or the GGSN.
  • the new sub-service when a new sub-service needs to be launched, the new sub-service, the identifier of the sub-service, the correspondence between the sub-service and the identifier of the sub-service, and the identifier of the sub-service are configured in advance on the TDF or GGSN configuration. Correspondence with the identity of the parent business.
  • Step 602 When the client needs to access the sub-service on the Internet, the client sends a service access request to the TDF or the GGSN, where the address of the sub-service is included.
  • Step 603 The TDF or the GGSN receives the service access request message sent by the client, performs DPI identification processing on the address of the sub-service included therein, and obtains the sub-service requesting the access; the correspondence between the TDF or the GGSN from the identifier of the sub-service and the sub-service Obtaining an identifier corresponding to the sub-service according to the identifier corresponding to the sub-service, and obtaining an identifier of the parent service of the sub-service from the correspondence between the identifier of the sub-service and the identifier of the parent service.
  • Step 604 the TDF or the GGSN sends a bandwidth request message to the PCRF through the Sd interface, where the bandwidth request message includes service identification information, where the service identification information includes an identifier of the sub-service and the sub-service.
  • the identity of the parent service of the service; TDF or GGSN through Gy The interface sends an accounting request message to the ocs, where the charging request message includes service identification information, where the service identification information includes an identifier of the sub-service and an identifier of the parent service of the sub-service.
  • Step 605 The PCRF and the OCS obtain the hierarchical relationship between the sub-service and the parent service according to the identifier of the sub-service and the identifier of the parent service of the sub-service, respectively, and obtain the sub-service according to the hierarchical relationship.
  • Business strategy The PCRF and the OCS obtain the hierarchical relationship between the sub-service and the parent service according to the identifier of the sub-service and the identifier of the parent service of the sub-service, respectively, and obtain the sub-service according to the hierarchical relationship.
  • Step 606 The PCRF sends an execution request message to the PCEF, where the identifier of the sub-service and the access bandwidth policy of the sub-service, so that the PCEF performs the access bandwidth policy.
  • Step 607 The OCS sends a service authorization message to the TDF or the GGSN, where the GSU and the identifier of the sub-service are carried.
  • Embodiments of the present invention further provide an apparatus embodiment for implementing the steps and methods in the foregoing method embodiments.
  • FIG. 7 is a functional block diagram of a content management device according to an embodiment of the present invention.
  • the content management device includes:
  • the processing unit 70 is configured to obtain the identifier of the sub-service and the identifier of the parent service of the sub-service; the sending unit 71 is configured to send the service identifier information to the policy management device, where the service identifier information includes the identifier of the sub-service An identifier of the parent service of the child service, so that the policy management device obtains a hierarchical relationship between the child service and the parent service according to the identifier of the child service and the identifier of the parent service of the child service, and Obtaining a business policy of the sub-service according to the hierarchical relationship.
  • the content management device is a TDF or a gateway
  • the policy management device is an OCS or
  • the service identification information further includes at least one of the following information: a hierarchical type of the sub-service and a hierarchical information of the sub-service; and a hierarchical type of the sub-service is used to indicate that the sub-service is a top-level The sub-service, the leaf layer sub-service or the middle-layer sub-service; the hierarchical information of the sub-service is used to indicate the level of the sub-service.
  • the content management device includes:
  • a memory 80 configured to store information including a program routine
  • the processor 81 is coupled to the memory 80 and the transmitter 82 for controlling the execution of the program routine, and specifically includes: obtaining an identifier of the sub-service and an identifier of the parent service of the sub-service;
  • the transmitter 82 is configured to send service identifier information to the policy management device, where the service identifier information includes an identifier of the sub-service and an identifier of a parent service of the sub-service, so that the policy management device is configured according to the sub-service And the identifier of the parent service of the child service, obtaining a hierarchical relationship between the child service and the parent service, and obtaining a business policy of the child service according to the hierarchical relationship.
  • FIG. 9 is a functional block diagram of a policy management device according to an embodiment of the present invention.
  • the policy management device includes:
  • the receiving unit 90 is configured to receive service identifier information sent by the content management device, where the service identifier information includes an identifier of the sub-service and an identifier of the parent service of the sub-service;
  • the first processing unit 91 is configured to obtain, according to the identifier of the sub-service and the identifier of the parent service of the sub-service, a hierarchical relationship between the sub-service and the parent service;
  • the second processing unit 92 is configured to obtain the service policy of the sub-service according to the hierarchical relationship.
  • the content management device is a TDF or a gateway, and the policy management device is an OCS; or the content management device For the TDF or the gateway, the policy management device is a PCRF.
  • the service identification information further includes at least one of the following information: a hierarchical type of the sub-service and a hierarchical information of the sub-service; and a hierarchical type of the sub-service is used to indicate that the sub-service is a top-level The sub-service, the leaf layer sub-service or the middle-layer sub-service; the hierarchical information of the sub-service is used to indicate the level of the sub-service.
  • the second processing unit 92 further includes:
  • the first processing module 921 is configured to obtain, according to the hierarchical relationship, at least one upper layer service of the child node, where the at least one upper layer service includes the parent service;
  • a second processing module 922 configured to obtain the sub-industry according to the at least one upper layer service
  • the upper layer service with the lowest number of levels and the service policy is used as the reference upper layer service.
  • the third processing module 923 is configured to obtain the service policy of the sub service according to the service policy of the reference upper layer service.
  • the policy management device further includes:
  • the sending unit 93 is configured to send the service identifier information to the second policy management device, where the service identifier information includes an identifier of the sub-service and an identifier of the parent service of the sub-service, so that the second policy management device is configured according to Obtaining the identifier of the sub-service and the identifier of the parent service of the sub-service, obtaining a hierarchical relationship between the sub-service and the parent service, and obtaining a service policy of the sub-service according to the hierarchical relationship;
  • the policy management device is an OCS
  • the second policy management device is a PCRF; or the policy management device is a PCRF, and the second policy management device is an OCS.
  • FIG. 10 is a schematic structural diagram of a policy management device according to an embodiment of the present invention.
  • the policy management device includes:
  • the receiver 100 is configured to receive service identifier information sent by the content management device, where the service identifier information includes an identifier of the sub-service and an identifier of the parent service of the sub-service;
  • a memory 200 configured to store information including a program routine
  • the processor 300 coupled with the memory 200 and the receiver 100, is configured to control the execution of the program routine, and specifically includes: obtaining the sub-service according to the identifier of the sub-service and the identifier of the parent service of the sub-service. a hierarchical relationship with the parent service; obtaining a business policy of the child service according to the hierarchical relationship.
  • the foregoing embodiments of the present invention have the following technical effects:
  • the identifiers are automatically generated, and the hierarchical relationship between the services is automatically generated, and the business policies of the sub-services are obtained in time according to the hierarchical relationship, thereby realizing automatic synchronization of the services, thereby reducing abnormalities when the client uses the services.
  • the cost of the manual maintenance service is reduced, the manpower and material resources are saved, and the consistency of service synchronization between devices is ensured, which is beneficial to the maintenance and operation of the service.
  • Policy management entities such as OCS can automatically generate billing policies for new services and reduce OCS. Manual maintenance, saving manpower and resources, can reduce the error rate when maintaining a large amount of service billing on the OCS.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本发明实施例提供了一种业务同步方法，包括：内容管理设备获得子业务的标识和所述子业务的父业务的标识；所述内容管理设备向策略管理设备发送业务标识信息，所述业务标识信息包括所述子业务的标识和所述子业务的父业务的标识，以使得所述策略管理设备依据所述子业务的标识和所述子业务的父业务的标识，获得所述子业务和所述父业务的层级关系，以及依据所述层级关系，获得所述子业务的业务策略；本发明还提供一种内容管理设备和策略管理设备。根据本发明实施例提供的技术方案，以实现设备间自动同步业务，以及为业务生成相应的业务策略。

Description

业务同步方法、 内容管理设备及策略管理设备 本申请要求于 2013 年 10 月 22 日提交中国专利局、 申请号为 201310499985.2、发明名称为"业务同步方法、内容管理设备及策略管理设备" 的中国专利申请的优先权， 其全部内容通过引用结合在本申请中。 技术领域
本发明涉及无线通信领域， 尤其涉及一种业务同步方法、 内容管理设备 及策略管理设备。 背景技术
互联网上的业务的增长非常快， 例如 "新浪 "， 已经出现了 "新浪视频"、 "新浪微博"、 "新浪围棋" 等各种子业务； 现有技术中， 当推出新的子业务 时， 在线计费系统（Online Charging System , OCS )需要确定这个业务的 计费策略， 同时， 需要在 3GPP网络的计费系统中的每个设备都配置新的子 业务， 以实现业务同步。
然而， 现有技术中计费系统中新业务的同步存在以下问题： 需要手动在 计费系统中的多个设备上配置新业务， 如果存在没有及时配置的设备， 或者 业务同步出现错误， 客户端上网使用该业务时将会出现异常。 发明内容
有鉴于此， 本发明实施例提供了一种业务同步方法、 内容管理设备及策 略管理设备， 以实现设备间自动同步业务， 以及为业务生成相应的业务策略。
第一方面， 本发明实施例提供了一种业务同步方法， 包括：
内容管理设备获得子业务的标识和所述子业务的父业务的标识； 所述内容管理设备向策略管理设备发送业务标识信息， 所述业务标识信 息包括所述子业务的标识和所述子业务的父业务的标识， 以使得所述策略管 理设备依据所述子业务的标识和所述子业务的父业务的标识， 获得所述子业 务和所述父业务的层级关系， 以及依据所述层级关系， 获得所述子业务的业 务策略。
在第一方面的第一种可能的实现方式中， 所述内容管理设备为流量识别 功能单元 TDF或网关；
所述策略管理设备为在线计费系统 OCS 或策略与计费规则功能单元 PCRF
在第一方面的第二种可能的实现方式中， 所述业务标识信息还包括下列 信息之中的至少一项： 所述子业务的层级类型和所述子业务的层级信息； 所述子业务的层级类型用于指示所述子业务为顶层子业务、 叶子层子业 务或中间层子业务；
所述子业务的层级信息用于指示所述子业务所在层级。
第二方面， 本发明实施例提供了一种业务同步方法， 包括：
第一策略管理设备接收内容管理设备发送的业务标识信息， 所述业务标 识信息包括子业务的标识和所述子业务的父业务的标识；
所述第一策略管理设备依据所述子业务的标识和所述子业务的父业务的 标识， 获得所述子业务和所述父业务的层级关系；
所述第一策略管理设备依据所述层级关系，获得所述子业务的业务策略。 在第二方面的第一种可能的实现方式中， 所述第一策略管理设备依据所 述层级关系， 获得所述子业务的业务策略， 包括：
所述第一策略管理设备依据所述层级关系， 获得所述子节点的至少一个 上层业务， 所述至少一个上层业务中包含所述父业务；
所述第一策略管理设备依据所述至少一个上层业务， 获得与所述子业务 之间层级数最少且有业务策略的上层业务， 作为参考上层业务；
所述第一策略管理设备依据所述参考上层业务的业务策略， 获得所述子 业务的业务策略。
结合第二方面或第二方面的第一种可能的实现方式中，所述方法还包括: 所述第一策略管理设备向第二策略管理设备发送所述业务标识信息， 所 述业务标识信息包括子业务的标识和所述子业务的父业务的标识， 以使得所 述第二策略管理设备依据所述子业务的标识和所述子业务的父业务的标识， 获得所述子业务和所述父业务的层级关系， 以及依据所述层级关系， 获得所 述子业务的业务策略；
其中， 所述第一策略管理设备为 OCS, 所述第二策略管理设备为 PCRF; 或者， 所述第一策略管理设备为 PCRF, 所述第二策略管理设备为 OCS。
第三方面， 本发明实施例提供了一种内容管理设备， 包括：
处理单元， 用于获得子业务的标识和所述子业务的父业务的标识； 发送单元， 用于向策略管理设备发送业务标识信息， 所述业务标识信息 包括所述子业务的标识和所述子业务的父业务的标识， 以使得所述策略管理 设备依据所述子业务的标识和所述子业务的父业务的标识， 获得所述子业务 和所述父业务的层级关系， 以及依据所述层级关系， 获得所述子业务的业务 策略。
在第三方面的第一种可能的实现方式中，所述内容管理设备为 TDF或网 关； 所述策略管理设备为 OCS或 PCRF。
在第三方面的第二种可能的实现方式中， 所述业务标识信息还包括下列 信息之中的至少一项： 所述子业务的层级类型和所述子业务的层级信息； 所述子业务的层级类型用于指示所述子业务为顶层子业务、 叶子层子业 务或中间层子业务；
所述子业务的层级信息用于指示所述子业务所在层级。
第四方面， 本发明实施例提供了一种策略管理设备， 包括：
接收单元， 用于接收内容管理设备发送的业务标识信息， 所述业务标识 信息包括子业务的标识和所述子业务的父业务的标识； 第一处理单元， 用于依据所述子业务的标识和所述子业务的父业务的标 识， 获得所述子业务和所述父业务的层级关系；
第二处理单元， 用于依据所述层级关系， 获得所述子业务的业务策略。 在第四方面的第一种可能的实现方式中，所述第二处理单元进一步包括： 第一处理模块， 用于依据所述层级关系， 获得所述子节点的至少一个上 层业务， 所述至少一个上层业务中包含所述父业务；
第二处理模块， 用于依据所述至少一个上层业务， 获得与所述子业务之 间层级数最少且有业务策略的上层业务， 作为参考上层业务；
第三处理模块， 用于依据所述参考上层业务的业务策略， 获得所述子业 务的业务策略。
结合第四方面或第四方面的第一种可能的实现方式中， 所述策略管理设 备还包括：
发送单元， 用于向第二策略管理设备发送所述业务标识信息， 所述业务 标识信息包括子业务的标识和所述子业务的父业务的标识， 以使得所述第二 策略管理设备依据所述子业务的标识和所述子业务的父业务的标识， 获得所 述子业务和所述父业务的层级关系， 以及依据所述层级关系， 获得所述子业 务的业务策略；
其中， 所述策略管理设备为 OCS , 所述第二策略管理设备为 PCRF; 或 者， 所述策略管理设备为 PCRF, 所述第二策略管理设备为 OCS。
由以上技术方案可以看出， 本发明具有以下有益效果：
策略管理设备可以根据内容管理设备上报的子业务的标识和父业务的标 识， 自动生成业务之间的层级关系， 同时依据层级关系及时获得子业务的业 务策略， 实现业务的自动同步， 从而减少客户端使用业务时出现的异常， 减 少手工维护业务的成本， 节省人力物力。 同时， 能够保证设备间的业务同步 的一致性， 有益于业务的维护和运营。 附图说明
为了更清楚地说明本发明实施例的技术方案， 下面将对本发明实施例中 所需要使用的附图作简单地介绍， 显而易见地， 下面所描述的附图仅仅是本 发明的一些实施例， 对于本领域普通技术人员来讲， 在不付出创造性劳动的 前提下， 还可以根据这些附图获得其他的附图。
图 1是本发明实施例所提供的业务同步方法一的流程示意图； 图 2是本发明实施例所提供的业务同步方法二的流程示意图； 图 3 ( a )是本发明实施例所提供的业务同步方法的实施例一的流程示意 图；
图 3 ( b )是本发明实施例所提供的业务同步系统的架构示意图； 图 4 是本发明策略管理设备获得子业务与父业务之间层级关系的示例 图；
图 5是本发明实施例所提供的业务同步方法的实施例二的流程示意图； 图 6是本发明实施例所提供的业务同步方法的实施例三的流程示意图； 图 7是本发明实施例所提供的内容管理设备的功能方块图；
图 8是本发明实施例所提供的内容管理设备的结构示意图；
图 9是本发明实施例所提供的策略管理设备的功能方块图；
图 10是本发明实施例所提供的策略管理设备的结构示意图。 具体实施方式
为了使本发明的目的、 技术方案和优点更加清楚， 下面结合附图和具体 实施例对本发明进行详细描述。
本发明实施例给出一种业务同步方法， 请参考图 1 , 其为本发明实施例 所提供的业务同步方法一的流程示意图， 如图所示， 该方法包括以下步骤： 步骤 101 , 内容管理设备获得子业务的标识和所述子业务的父业务的标 识。 步骤 102, 所述内容管理设备向策略管理设备发送业务标识信息， 所述 业务标识信息包括所述子业务的标识和所述子业务的父业务的标识， 以使得 所述策略管理设备依据所述子业务的标识和所述子业务的父业务的标识， 获 得所述子业务和所述父业务的层级关系， 以及依据所述层级关系， 获得所述 子业务的业务策略。
其中， 所述业务标识信息还可以包括下列信息之中的至少一项： 所述子 业务的层级类型和所述子业务的层级信息； 所述子业务的层级类型用于指示 所述子业务为顶层子业务、 叶子层子业务或中间层子业务； 所述子业务的层 级信息用于指示所述子业务所在层级。
其中， 所述内容管理设备为流量识别功能单元 （ Traffic Detection Function , TDF )或网关， 所述策略管理设备为 OCS或策略与计费规则功能 单元 ( Policy and Charging Rules Function , PCRF )。
其中， 网关可以为网关（ Gateway )通用分组无线服务（ General Packet Radio Service , GPRS ) 支持节点 （Serving GPRS Supporting Node , SGSN ), 还可以为分组数据网络网关 （Packet Data Network Gateway, P-GW ), 还可以为服务网关 （Serving Gateway, S-GW )等。
其中， 所述业务策略包括计费策略和 /或访问带宽策略。
本发明实施例给出一种业务同步方法， 请参考图 2, 其为本发明实施例 所提供的业务同步方法二的流程示意图， 如图所示， 该方法包括以下步骤： 步骤 201 , 第一策略管理设备接收内容管理设备发送的业务标识信息， 所述业务标识信息包括子业务的标识和所述子业务的父业务的标识。
其中， 所述业务标识信息还包括下列信息之中的至少一项： 所述子业务 的层级类型和所述子业务的层级信息； 所述子业务的层级类型用于指示所述 子业务为顶层子业务、 叶子层子业务或中间层子业务； 所述子业务的层级信 息用于指示所述子业务所在层级。
步骤 202, 所述第一策略管理设备依据所述子业务的标识和所述子业务 的父业务的标识， 获得所述子业务和所述父业务的层级关系。
步骤 203, 所述第一策略管理设备依据所述层级关系， 获得所述子业务 的业务策略。
具体的， 所述第一策略管理设备依据所述层级关系， 获得所述子节点的 至少一个上层业务， 所述至少一个上层业务中包含所述父业务； 所述第一策 略管理设备依据所述至少一个上层业务， 获得与所述子业务之间层级数最少 且有业务策略的上层业务， 作为参考上层业务； 所述第一策略管理设备依据 所述参考上层业务的业务策略， 获得所述子业务的业务策略。
其中， 所述业务策略包括计费策略和 /或访问带宽策略。
其中，所述内容管理设备为 TDF或网关，所述第一策略管理设备为 OCS; 或者， 所述内容管理设备为 TDF或网关， 所述第一策略管理设备为 PCRF。
优选的， 所述步骤 203之后， 所述方法还包括： 所述第一策略管理设备 向第二策略管理设备发送所述业务标识信息， 所述业务标识信息包括子业务 的标识和所述子业务的父业务的标识， 以使得所述第二策略管理设备依据所 述子业务的标识和所述子业务的父业务的标识， 获得所述子业务和所述父业 务的层级关系， 以及依据所述层级关系， 获得所述子业务的业务策略； 其中， 所述第一策略管理设备为 OCS, 所述第二策略管理设备为 PCRF; 或者， 所 述第一策略管理设备为 PCRF, 所述第二策略管理设备为 OCS。
实施例一
请参考图 3 ( a )和图 3 ( b ), 图 3 ( a )是本发明实施例所提供的业务 同步方法的实施例一的流程示意图， 图 3 ( b )是本发明实施例所提供的业务 同步系统的架构示意图； 本实施例中， 内容管理设备为 TDF或 GGSN , 第 一策略管理设备为 OCS, 第二策略管理设备为 PCRF, 如图所示， 该方法包 括以下步骤：
步骤 301 , 当有新的子业务需要推出时， 预先在 TDF或 GGSN上配置 该新的子业务、 该子业务的标识、 该子业务与子业务的标识的对应关系、 该 子业务的标识与父业务的标识的对应关系。
步骤 302, 当客户端需要上网访问子业务时， 客户端向 TDF或 GGSN 发送业务访问请求， 其中包含所述子业务的地址。
步骤 303, TDF或 GGSN接收客户端发送的业务访问请求消息， 对其 中包含的子业务的地址进行 DPI识别处理， 获得请求访问的子业务； TDF或 GGSN从子业务与子业务的标识的对应关系中获得所述子业务对应的标识； 依据子业务对应的标识， 从子业务的标识与父业务的标识的对应关系中获得 该子业务的父业务的标识。
步骤 304, TDF或 GGSN通过 Gy接口向 OCS发送计费请求消息， 所 述计费请求消息中包含业务标识信息， 所述业务标识信息包括子业务的标识 和所述子业务的父业务的标识。
具体的， 如图 3 ( b )所示， 本实施例中， 对 TDF与 OCS之间的 Gy接 口或 GGSN与 OCS之间的 Gy接口进行扩展， 使得 TDF或 GGSN可以通 过 Gy接口向 OCS发送的计费请求消息中， 能够携带业务标识信息； 例如， 业务标识信息可以为属性值对（Attribute Value Pair, AVP )集合， 属性值对 集合中包含至少两个 AVP, 如表 1所示：
表 1
Figure imgf000010_0001
表 1 中， Serviceid-lnformation表示业务标识信息作为计费请求消息中 一个字段时， 该字段的名称； Service-id 为子业务的标识， 即 22337 ; Parent-Service-id为子业务的父业务的标识， 即 32301。 优选的， 业务标识信息中还可以包含以下信息中的至少一项：
Service-id-layer和 Service-id-Type; 其中， Service-id-layer为子业务的层 级信息， 用于指示所述子业务在业务树中的层级； Service-id-Type为子业务 的层级类型，用于指示子业务为顶层子业务、叶子层子业务或中间层子业务； Service-id-layer和 Service-id-Type可以便于在 OCS在业务树中很快找到子 业务的位置， 提高 OCS获得子业务与父业务的层级关系的速度。
步骤 305, OCS依据所述子业务的标识和所述子业务的父业务的标识， 获得所述子业务和所述父业务的层级关系， 依据所述层级关系， 获得所述子 业务的计费策略。
具体的， OCS具有自适应学习能力，不需要在 OCS上配置子业务， OCS 可以依据所述子业务的标识和所述子业务的父业务的标识， 获得所述子业务 和所述父业务的层级关系， 然后将该子业务挂到本地已经存在的业务树中的 所述父业务的下面， 表示该子业务是该父业务的子业务， 这样 OCS就可以 自动在业务树中添加子业务， 实现子业务的自动更新和存储。
例如，新浪是一个互联网业务，需要新发布一个新浪视频的业务时， "新 浪视频" 就是 "新浪" 的子业务， 业务树中， "新浪视频" 与 "新浪"之间具 有层级关系； 当客户端需要访问 "新浪视频" 时， TDF或 GGSN 通过 Gy 接口向 OCS发送 "新浪视频" 的标识和 "新浪" 的标识， 用于向 OCS上报 "新浪视频" 与 "新浪" 两个业务之间的层级关系， 实现向 OCS 同步新发 布的业务。
OCS可以依据子业务与父业务之间的层级关系，获得所述子业务的计费 策略， 例如， OCS先在本地保存的业务策略中搜索该子业务的计费策略， 如 果没有， 表示本地还没有配置该子业务的计费策略， 则 OCS搜索该子业务 的父业务的计费策略，可以将该父业务的计费策略作为该子业务的计费策略； 如果父业务也没有配置业务策略， 则将该子业务的祖父业务的计费策略作为 该子业务的计费策略， 以此类推； 其中， 所述计费策略可以包括子业务的定 价和 /或子业务的预留， 例如， 子业务的流量预留或余额预留等。
例如， 如图 4所示， 当客户端需要访问 "新浪视频" 时， TDF或 GGSN 通过 Gy接口向 OCS发送 "新浪视频" 的标识（ServicelDI )和 "新浪" 的 标识（ServicelDO ), 表示 "新浪" 是 "新浪视频" 的父业务， 从而可以获得 "新浪" 与 "新浪视频" 的层级关系； OCS依据 "新浪视频" 的标识和 "新 浪" 的标识， 在业务树中加入子业务 "新浪视频"， 得到图 4所示的业务树， 其中， "新浪视频"、 "新浪微博"、 "新浪新闻" 和 "新浪围棋" 都是 "新浪" 的子业务。
当 OCS需要对 "新浪视频" 进行计费时， 如果 "新浪视频" 配置有计 费策略， 则使用该计费策略， 若 "新浪视频"还没有配置计费策略， 则 OCS 依据 "新浪" 的计费策略， 获得 "新浪视频" 的计费策略， 依据 "新浪" 的 计费策略对 "新浪视频" 进行计费。
步骤 306, OCS向 TDF或 GGSN发送业务授权消息， 其中携带授权业 务量（Granted Service Unit, GSU )和所述子业务的标识。
优选的， 在步骤 306之后， 该方法还可以包括：
步骤 307, OCS通过 Sy接口向 PCRF发送带宽请求消息， 所述带宽请 求消息中包含业务标识信息， 所述业务标识信息包括子业务的标识和所述子 业务的父业务的标识。
例如， 当 OCS 维护的子业务计数器（Counter ) 的数值变更时， OCS 向 PCRF发送子业务的标识（ ServicelDI )和父业务（ ServicelDO )的标识。
其中， 通过 Sy发送的带宽请求消息中包含的业务标识信息的格式可以 ^口表 1所示。
步骤 308, PCRF依据子业务的标识和所述子业务的父业务的标识， 获 得所述子业务和所述父业务的层级关系， 依据业务树中子业务与父业务的层 级关系， 获得子业务的访问带宽策略。
具体的， PCRF具有自适应学习能力， 不需要在 PCRF上配置子业务， PCRF可以依据所述子业务的标识和所述子业务的父业务的标识， 获得所述 子业务和所述父业务的层级关系， 然后将该子业务挂到本地已经存在的业务 树中的所述父业务的下面， 表示该子业务是该父业务的子业务， 这样 PCRF 就可以自动在业务树中添加子业务， 实现子业务的自动更新和存储。
例如， 新浪是一个互联网业务， 需要新发布一个新浪视频的业务时， 新 浪视频就是新浪的子业务， 业务树中， 新浪视频与新浪之间具有层级关系； 当客户端需要访问新浪视频时， OCS通过 Sy接口向 PCRF发送新浪视频的 标识和新浪的标识，用于向 PCRF上报新浪视频与新浪两个业务之间的层级 关系， 实现向 PCRF同步新发布的业务。
PCRF可以依据子业务与父业务之间的层级关系， 获得所述子业务的访 问带宽策略， 例如， PCRF先在本地保存的业务策略中搜索该子业务的访问 带宽策略， 如果没有， 表示本地还没有配置该子业务的访问带宽策略， 则 PCRF搜索该子业务的父业务的访问带宽策略， 将该父业务的访问带宽策略 作为该子业务的访问带宽策略； 如果父业务也没有配置访问带宽策略， 则将 该子业务的祖父业务的访问带宽策略作为该子业务的访问带宽策略， 以此类 推； PCRF可以将自动获得的访问带宽策略发送给 PCEF, 以使得 PCEF执 行所述访问带宽策略。
实施例二
请参考图 5, 图 5是本发明实施例所提供的业务同步方法的实施例一的 流程示意图， 本实施例中， 内容管理设备为 TDF或 GGSN , 第一策略管理 设备为 PCRF , 第二策略管理设备为 OCS如图所示， 该方法包括以下步骤： 步骤 501 , 在 TDF或 GGSN预先配置子业务与子业务的标识的对应关 系。
具体的， 当有新的子业务需要推出时， 预先在 TDF或 GGSN配置上配 置该新的子业务、 该子业务的标识、 该子业务与子业务的标识的对应关系、 该子业务的标识与父业务的标识的对应关系。 步骤 502, 当客户端需要上网访问子业务时， 客户端向 TDF或 GGSN 发送业务访问请求， 其中包含所述子业务的地址。
步骤 503, TDF或 GGSN接收客户端发送的业务访问请求消息， 对其 中包含的子业务的地址进行 DPI识别处理， 获得请求访问的子业务； TDF或 GGSN从子业务与子业务的标识的对应关系中获得所述子业务对应的标识； 依据子业务对应的标识， 从子业务的标识与父业务的标识的对应关系中获得 该子业务的父业务的标识。
步骤 504, TDF或 GGSN通过 Sd接口向 PCRF发送带宽请求消息，所 述带宽请求消息中包含业务标识信息， 所述业务标识信息包括子业务的标识 和所述子业务的父业务的标识。
具体的， 如图 3 ( b )所示， 本实施例中， 对 TDF与 PCRF之间的 Sd 接口或 GGSN与 OCS之间的 Sd接口进行扩展， 使得 TDF或 GGSN可以 通过 Sd接口向 OCS发送的计费请求消息中， 能够携带业务标识信息； 所述 业务标识信息的格式可以参考上述表 1 , 这里不再赘述。
优选的， 业务标识信息中还可以包含以下信息中的至少一项：
Service-id-layer和 Service-id-Type; 其中， Service-id-layer为子业务的层 级信息， 用于指示所述子业务在业务树中的层级； Service-id-Type为子业务 的层级类型， 用于指示所述子业务为顶层子业务、 叶子层子业务或中间层子 业务； Service-id-layer和 Service-id-Type可以便于在 OCS在业务树中很快 找到子业务的位置， 提高 OCS获得子业务与父业务的层级关系的速度。
步骤 505, PCRF依据所述子业务的标识和所述子业务的父业务的标识， 获得所述子业务和所述父业务的层级关系， 依据所述层级关系， 获得所述子 业务的访问带宽策略。
具体的， PCRF具有自适应学习能力， 不需要在 PCRF上配置子业务， PCRF可以依据所述子业务的标识和所述子业务的父业务的标识， 获得所述 子业务和所述父业务的层级关系， 然后将该子业务挂到本地已经存在的业务 树中的所述父业务的下面， 表示该子业务是该父业务的子业务， 这样 PCRF 就可以自动在业务树中添加子业务， 实现子业务的自动更新和存储。
例如，新浪是一个互联网业务，需要新发布一个新浪视频的业务时， "新 浪视频" 就是 "新浪" 的子业务， 业务树中， "新浪视频" 与 "新浪"之间具 有层级关系； 当客户端需要访问 "新浪视频" 时， TDF或 GGSN通过 Sd接 口向 OCS发送 "新浪视频" 的标识和 "新浪" 的标识， 用于向 PCRF上报 "新浪视频" 与 "新浪" 两个业务之间的层级关系， 实现向 PCRF同步新发 布的业务。
PCRF可以依据子业务与父业务之间的层级关系， 获得所述子业务的访 问带宽策略， 例如， PCRF先在本地保存的业务策略中搜索该子业务的访问 带宽策略， 如果没有， 表示本地还没有配置该子业务的访问带宽策略， 则 OCS搜索该子业务的父业务的访问带宽策略，可以将该父业务的访问带宽策 略作为该子业务的访问带宽策略； 如果父业务也没有配置访问带宽策略， 则 将该子业务的祖父业务的访问带宽策略作为该子业务的访问带宽策略， 以此 类推。
例如， 如图 4所示， 当客户端需要访问 "新浪视频" 时， TDF或 GGSN 通过 Gy接口向 PCRF发送 "新浪视频" 的标识 （ServicelDI )和 "新浪" 的标识（ ServicelDO ), 表示 "新浪" 是 "新浪视频" 的父业务， 从而可以获 得 "新浪" 与 "新浪视频" 的层级关系； PCRF依据 "新浪视频" 的标识和 "新浪" 的标识， 在业务树中加入子业务 "新浪视频"， 得到图 4 所示的业 务树，其中， "新浪视频"、 "新浪微博"、 "新浪新闻"和"新浪围棋"都是"新 浪" 的子业务。
当 PCRF需要获得 "新浪视频" 的访问带宽策略时， 如果 "新浪视频" 配置有访问带宽策略， 则使用该访问带宽策略， 若 "新浪视频"还没有配置 访问带宽策略， 则 OCS依据 "新浪" 的访问带宽策略， 获得 "新浪视频" 的访问带宽策略。 步骤 506, PCRF向 PCEF发送执行请求消息， 其中子业务的标识和子 业务的访问带宽策略， 以使得 PCEF执行该访问带宽策略。
优选的， 在步骤 306之后， 该方法还可以包括：
步骤 507, PCRF通过 Sy接口向 OCS发送计费请求消息， 所述计费请 求消息中包含业务标识信息， 所述业务标识信息包括子业务的标识和所述子 业务的父业务的标识。 其中， 通过 Sy发送的计费请求消息中包含的业务标 识信息的格式可以如表 1所示。 或者， PCRF通过 Gx接口向 PCEF发送计 费请求消息， 所述计费请求消息中包含业务标识信息， 所述业务标识信息包 括子业务的标识和所述子业务的父业务的标识； 所述 PCEF再通过 Gy接口 向 OCS发送所述计费请求消息中包含业务标识信息， 所述业务标识信息包 括子业务的标识和所述子业务的父业务的标识。
步骤 508, OCS依据子业务的标识和所述子业务的父业务的标识， 获得 所述子业务和所述父业务的层级关系， 依据业务树中子业务与父业务的层级 关系， 获得子业务的计费策略。
具体的， OCS具有自适应学习能力，不需要在 OCS上配置子业务， OCS 可以依据所述子业务的标识和所述子业务的父业务的标识， 获得所述子业务 和所述父业务的层级关系， 然后将该子业务挂到本地已经存在的业务树中的 所述父业务的下面， 表示该子业务是该父业务的子业务， 这样 OCS就可以 自动在业务树中添加子业务， 实现子业务的自动更新和存储。
例如， 新浪是一个互联网业务， 需要新发布一个新浪视频的业务时， 新 浪视频就是新浪的子业务， 业务树中， 新浪视频与新浪之间具有层级关系； 当客户端需要访问新浪视频时， PCRF通过 Sy接口向 OCS发送新浪视频的 标识和新浪的标识， 用于向 OCS上报新浪视频与新浪两个业务之间的层级 关系， 实现向 OCS同步新发布的业务。
OCS可以依据子业务与父业务之间的层级关系，获得所述子业务的计费 策略， 例如， OCS先在本地保存的业务策略中搜索该子业务的计费策略， 如 果没有， 表示本地还没有配置该子业务的计费策略， 则 OCS搜索该子业务 的父业务的计费策略， 将该父业务的计费策略作为该子业务的计费策略； 如 果父业务也没有配置计费策略， 则将该子业务的祖父业务的计费策略作为该 子业务的计费策略， 以此类推； OCS依据将自动获得的计费策略进行子业务 的计费。
步骤 509, OCS向 TDF或 GGSN发送业务授权消息， 其中携带 GSU 和所述子业务的标识。
实施例三
请参考图 6, 图 6是本发明实施例所提供的业务同步方法的实施例三的 流程示意图， 本实施例中， 内容管理设备为 TDF或 GGSN , 至少一个第一 策略管理设备包括 PCRF和 OCS, 如图所示， 该方法包括以下步骤：
步骤 601 , 在 TDF或 GGSN预先配置子业务与子业务的标识的对应关 系。
具体的， 当有新的子业务需要推出时， 预先在 TDF或 GGSN配置上配 置该新的子业务、 该子业务的标识、 该子业务与子业务的标识的对应关系、 该子业务的标识与父业务的标识的对应关系。
步骤 602, 当客户端需要上网访问子业务时， 客户端向 TDF或 GGSN 发送业务访问请求， 其中包含所述子业务的地址。
步骤 603, TDF或 GGSN接收客户端发送的业务访问请求消息， 对其 中包含的子业务的地址进行 DPI识别处理， 获得请求访问的子业务； TDF或 GGSN从子业务与子业务的标识的对应关系中获得所述子业务对应的标识； 依据子业务对应的标识， 从子业务的标识与父业务的标识的对应关系中获得 该子业务的父业务的标识。
步骤 604 , 如图 3 ( a ) 所示， TDF或 GGSN通过 Sd接口向 PCRF发 送带宽请求消息， 所述带宽请求消息中包含业务标识信息， 所述业务标识信 息包括子业务的标识和所述子业务的父业务的标识； TDF或 GGSN通过 Gy 接口向 ocs发送计费请求消息， 所述计费请求消息中包含业务标识信息， 所述业务标识信息包括子业务的标识和所述子业务的父业务的标识。
步骤 605, PCRF和 OCS分别依据所述子业务的标识和所述子业务的 父业务的标识， 获得所述子业务和所述父业务的层级关系， 依据所述层级关 系， 获得所述子业务的业务策略。
步骤 606, PCRF向 PCEF发送执行请求消息， 其中子业务的标识和子 业务的访问带宽策略， 以使得 PCEF执行该访问带宽策略。
步骤 607, OCS向 TDF或 GGSN发送业务授权消息， 其中携带 GSU 和所述子业务的标识。
本发明实施例进一步给出实现上述方法实施例中各步骤及方法的装置实 施例。
请参考图 7, 其为本发明实施例所提供的内容管理设备的功能方块图。 如图所示， 该内容管理设备包括：
处理单元 70, 用于获得子业务的标识和所述子业务的父业务的标识； 发送单元 71 , 用于向策略管理设备发送业务标识信息， 所述业务标识信 息包括所述子业务的标识和所述子业务的父业务的标识， 以使得所述策略管 理设备依据所述子业务的标识和所述子业务的父业务的标识， 获得所述子业 务和所述父业务的层级关系， 以及依据所述层级关系， 获得所述子业务的业 务策略。
其中， 所述内容管理设备为 TDF或网关， 所述策略管理设备为 OCS或
PCRF。
其中， 所述业务标识信息还包括下列信息之中的至少一项： 所述子业务 的层级类型和所述子业务的层级信息； 所述子业务的层级类型用于指示所述 子业务为顶层子业务、 叶子层子业务或中间层子业务； 所述子业务的层级信 息用于指示所述子业务所在层级。 如图所示， 该内容管理设备包括：
存储器 80 , 用于存储包括程序例程的信息；
处理器 81 , 与存储器 80、 发射机 82耦合， 用于控制所述程序例程的执 行， 具体包括： 获得子业务的标识和所述子业务的父业务的标识；
发射机 82, 用于向策略管理设备发送业务标识信息， 所述业务标识信息 包括所述子业务的标识和所述子业务的父业务的标识， 以使得所述策略管理 设备依据所述子业务的标识和所述子业务的父业务的标识， 获得所述子业务 和所述父业务的层级关系， 以及依据所述层级关系， 获得所述子业务的业务 策略。
请参考图 9, 其为本发明实施例所提供的策略管理设备的功能方块图。 如图所示， 该策略管理设备包括：
接收单元 90, 用于接收内容管理设备发送的业务标识信息， 所述业务标 识信息包括子业务的标识和所述子业务的父业务的标识；
第一处理单元 91 ,用于依据所述子业务的标识和所述子业务的父业务的 标识， 获得所述子业务和所述父业务的层级关系；
第二处理单元 92,用于依据所述层级关系，获得所述子业务的业务策略. 其中， 所述内容管理设备为 TDF或网关， 所述策略管理设备为 OCS; 或者， 所述内容管理设备为 TDF或网关， 所述策略管理设备为 PCRF。
其中， 所述业务标识信息还包括下列信息之中的至少一项： 所述子业务 的层级类型和所述子业务的层级信息； 所述子业务的层级类型用于指示所述 子业务为顶层子业务、 叶子层子业务或中间层子业务； 所述子业务的层级信 息用于指示所述子业务所在层级。
其中， 所述第二处理单元 92进一步包括：
第一处理模块 921 , 用于依据所述层级关系， 获得所述子节点的至少一 个上层业务， 所述至少一个上层业务中包含所述父业务；
第二处理模块 922, 用于依据所述至少一个上层业务， 获得与所述子业 务之间层级数最少且有业务策略的上层业务， 作为参考上层业务； 第三处理模块 923, 用于依据所述参考上层业务的业务策略， 获得所述 子业务的业务策略。
所述策略管理设备还包括：
发送单元 93, 用于向第二策略管理设备发送所述业务标识信息， 所述业 务标识信息包括子业务的标识和所述子业务的父业务的标识， 以使得所述第 二策略管理设备依据所述子业务的标识和所述子业务的父业务的标识， 获得 所述子业务和所述父业务的层级关系， 以及依据所述层级关系， 获得所述子 业务的业务策略； 其中， 所述策略管理设备为 OCS, 所述第二策略管理设备 为 PCRF;或者，所述策略管理设备为 PCRF,所述第二策略管理设备为 OCS。
请参考图 10,其为本发明实施例所提供的一种策略管理设备的结构示意 图； 如图所示， 该策略管理设备包括：
接收机 100, 用于接收内容管理设备发送的业务标识信息， 所述业务标 识信息包括子业务的标识和所述子业务的父业务的标识；
存储器 200, 用于存储包括程序例程的信息；
处理器 300, 与存储器 200、 接收机 100耦合， 用于控制所述程序例程 的执行， 具体包括： 依据所述子业务的标识和所述子业务的父业务的标识， 获得所述子业务和所述父业务的层级关系； 依据所述层级关系， 获得所述子 业务的业务策略。
上述本发明实施例具有以下技术效果： 的标识， 自动生成业务之间的层级关系， 同时依据层级关系及时获得子业务 的业务策略， 实现业务的自动同步，从而减少客户端使用业务时出现的异常， 减少手工维护业务的成本， 节省人力物力， 此外能够保证设备间的业务同步 的一致性， 有益于业务的维护和运营。
2、策略管理实体如 OCS ,可以自动为新的业务生成计费策略，减少 OCS 的手动维护， 节省人力物力， 能够降低在 OCS上维护大量的业务计费时的 出错率。
以上所述仅为本发明的较佳实施例而已， 并不用以限制本发明， 凡在本 发明的精神和原则之内， 所做的任何修改、 等同替换、 改进等， 均应包含在 本发明保护的范围之内。

Claims

权利要求书
1、 一种业务同步方法， 其特征在于， 所述方法包括：
内容管理设备获得子业务的标识和所述子业务的父业务的标识； 所述内容管理设备向策略管理设备发送业务标识信息， 所述业务标识信 息包括所述子业务的标识和所述子业务的父业务的标识， 以使得所述策略管 理设备依据所述子业务的标识和所述子业务的父业务的标识， 获得所述子业 务和所述父业务的层级关系， 以及依据所述层级关系， 获得所述子业务的业 务策略。
2、 根据权利要求 1所述的方法， 其特征在于，
所述内容管理设备为流量识别功能单元 TDF或网关；
所述策略管理设备为在线计费系统 OCS 或策略与计费规则功能单元 PCRF。
3、 根据权利要求 1所述的方法， 其特征在于，
所述业务标识信息还包括下列信息之中的至少一项： 所述子业务的层级 类型和所述子业务的层级信息；
所述子业务的层级类型用于指示所述子业务为顶层子业务、 叶子层子业 务或中间层子业务；
所述子业务的层级信息用于指示所述子业务所在层级。
4、 一种业务同步方法， 其特征在于， 所述方法包括：
第一策略管理设备接收内容管理设备发送的业务标识信息， 所述业务标 识信息包括子业务的标识和所述子业务的父业务的标识；
所述第一策略管理设备依据所述子业务的标识和所述子业务的父业务的 标识， 获得所述子业务和所述父业务的层级关系；
所述第一策略管理设备依据所述层级关系，获得所述子业务的业务策略。
5、根据权利要求 4所述的方法， 其特征在于， 所述第一策略管理设备依 据所述层级关系， 获得所述子业务的业务策略， 包括： 所述第一策略管理设备依据所述层级关系， 获得所述子节点的至少一个 上层业务， 所述至少一个上层业务中包含所述父业务；
所述第一策略管理设备依据所述至少一个上层业务， 获得与所述子业务 之间层级数最少且有业务策略的上层业务， 作为参考上层业务；
所述第一策略管理设备依据所述参考上层业务的业务策略， 获得所述子 业务的业务策略。
6、 根据权利要求 4或 5所述的方法， 其特征在于， 所述方法还包括： 所述第一策略管理设备向第二策略管理设备发送所述业务标识信息， 所 述业务标识信息包括子业务的标识和所述子业务的父业务的标识， 以使得所 述第二策略管理设备依据所述子业务的标识和所述子业务的父业务的标识， 获得所述子业务和所述父业务的层级关系， 以及依据所述层级关系， 获得所 述子业务的业务策略；
其中， 所述第一策略管理设备为 OCS, 所述第二策略管理设备为 PCRF; 或者， 所述第一策略管理设备为 PCRF, 所述第二策略管理设备为 OCS。
7、 一种内容管理设备， 其特征在于， 所述内容管理设备包括： 处理单元， 用于获得子业务的标识和所述子业务的父业务的标识； 发送单元， 用于向策略管理设备发送业务标识信息， 所述业务标识信息 包括所述子业务的标识和所述子业务的父业务的标识， 以使得所述策略管理 设备依据所述子业务的标识和所述子业务的父业务的标识， 获得所述子业务 和所述父业务的层级关系， 以及依据所述层级关系， 获得所述子业务的业务 策略。
8、 根据权利要求 7所述的内容管理设备， 其特征在于，
所述内容管理设备为 TDF或网关；
所述策略管理设备为 OCS或 PCRF。
9、 根据权利要求 7所述的内容管理设备， 其特征在于，
所述业务标识信息还包括下列信息之中的至少一项： 所述子业务的层级 类型和所述子业务的层级信息；
所述子业务的层级类型用于指示所述子业务为顶层子业务、 叶子层子业 务或中间层子业务；
所述子业务的层级信息用于指示所述子业务所在层级。
10、 一种策略管理设备， 其特征在于， 所述策略管理设备包括： 接收单元， 用于接收内容管理设备发送的业务标识信息， 所述业务标识 信息包括子业务的标识和所述子业务的父业务的标识；
第一处理单元， 用于依据所述子业务的标识和所述子业务的父业务的标 识， 获得所述子业务和所述父业务的层级关系；
第二处理单元， 用于依据所述层级关系， 获得所述子业务的业务策略。
11、根据权利要求 10所述的策略管理设备， 其特征在于， 所述第二处理 单元进一步包括：
第一处理模块， 用于依据所述层级关系， 获得所述子节点的至少一个上 层业务， 所述至少一个上层业务中包含所述父业务；
第二处理模块， 用于依据所述至少一个上层业务， 获得与所述子业务之 间层级数最少且有业务策略的上层业务， 作为参考上层业务；
第三处理模块， 用于依据所述参考上层业务的业务策略， 获得所述子业 务的业务策略。
12、 根据权利要求 10或 11所述的策略管理设备， 其特征在于， 所述策 略管理设备还包括：
发送单元， 用于向第二策略管理设备发送所述业务标识信息， 所述业务 标识信息包括子业务的标识和所述子业务的父业务的标识， 以使得所述第二 策略管理设备依据所述子业务的标识和所述子业务的父业务的标识， 获得所 述子业务和所述父业务的层级关系， 以及依据所述层级关系， 获得所述子业 务的业务策略；
其中， 所述策略管理设备为 OCS , 所述第二策略管理设备为 PCRF; 或 者， 所述策略管理设备为 PCRF, 所述第二策略管理设备为 OCS。
PCT/CN2014/081059 2013-10-22 2014-06-28 业务同步方法、内容管理设备及策略管理设备 WO2015058549A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310499985.2A CN103533070A (zh) 2013-10-22 2013-10-22 业务同步方法、内容管理设备及策略管理设备
CN201310499985.2 2013-10-22

Publications (1)

Publication Number Publication Date
WO2015058549A1 true WO2015058549A1 (zh) 2015-04-30

Family

ID=49934734

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/081059 WO2015058549A1 (zh) 2013-10-22 2014-06-28 业务同步方法、内容管理设备及策略管理设备

Country Status (2)

Country Link
CN (1) CN103533070A (zh)
WO (1) WO2015058549A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113569101A (zh) * 2021-07-28 2021-10-29 上海数慧系统技术有限公司 业务信息处理方法和装置

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103533070A (zh) * 2013-10-22 2014-01-22 华为技术有限公司 业务同步方法、内容管理设备及策略管理设备
CN106169979B (zh) * 2015-05-19 2020-07-31 阿里巴巴集团控股有限公司 一种业务处理方法和设备
CN106686678B (zh) * 2015-11-10 2020-08-07 中国移动通信集团公司 一种业务路由系统及其业务处理方法
CN112269562B (zh) * 2020-09-27 2023-09-12 福建天泉教育科技有限公司 一种组件化产品中租户隔离的方法及终端
CN113850536A (zh) * 2021-11-30 2021-12-28 阿里云计算有限公司 一种业务定制方法、展示平台、服务器及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101001156A (zh) * 2006-01-12 2007-07-18 中兴通讯股份有限公司 一种远程拨号接入服务认证协议认证预付费的方法
CN101175128A (zh) * 2006-11-03 2008-05-07 华为技术有限公司 一种计费的方法及装置
CN103533070A (zh) * 2013-10-22 2014-01-22 华为技术有限公司 业务同步方法、内容管理设备及策略管理设备

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101662758A (zh) * 2009-10-10 2010-03-03 中国电信股份有限公司 计费方法、网关设备及内容计费系统
CN102625272B (zh) * 2011-01-31 2017-03-29 中兴通讯股份有限公司 一种支持流检测功能的用量监控方法及系统
WO2013152997A1 (en) * 2012-04-11 2013-10-17 Nokia Siemens Networks Oy Conditional policy control
CN102802145B (zh) * 2012-08-08 2015-04-29 中国联合网络通信集团有限公司 网络业务计费方法、装置和系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101001156A (zh) * 2006-01-12 2007-07-18 中兴通讯股份有限公司 一种远程拨号接入服务认证协议认证预付费的方法
CN101175128A (zh) * 2006-11-03 2008-05-07 华为技术有限公司 一种计费的方法及装置
CN103533070A (zh) * 2013-10-22 2014-01-22 华为技术有限公司 业务同步方法、内容管理设备及策略管理设备

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113569101A (zh) * 2021-07-28 2021-10-29 上海数慧系统技术有限公司 业务信息处理方法和装置

Also Published As

Publication number Publication date
CN103533070A (zh) 2014-01-22

Similar Documents

Publication Publication Date Title
US11589216B2 (en) Service selection set publishing to device agent with on-device service selection
US11083033B2 (en) Small data usage enablement in 3GPP networks
US10616120B2 (en) Service layer southbound interface and quality of service
US10171988B2 (en) Adapting network policies based on device service processor configuration
CN105765921B (zh) 用于利用软件定义网络功能进行diameter路由的方法、系统和设备
US8594621B2 (en) Usage sharing across fixed line and mobile subscribers
US9166891B2 (en) Policy-enabled dynamic deep packet inspection for telecommunications networks
US8898293B2 (en) Service offer set publishing to device agent with on-device service selection
US8788661B2 (en) Device assisted CDR creation, aggregation, mediation and billing
WO2015058549A1 (zh) 业务同步方法、内容管理设备及策略管理设备
AU2011305456B2 (en) Service offer set publishing to device agent with on-device service selection
US20120303796A1 (en) Mapping accounting avps to monitoring keys for wireline subscriber management
US9686172B2 (en) Method and apparatus of determining policy and charging rules based on network resource utilization information
WO2014114190A1 (zh) 一种进行策略决策的方法、计费设备和系统
WO2012088919A1 (zh) 业务用量监控方法及设备
WO2013091410A1 (zh) 网络接入方法、系统及设备
US20120303795A1 (en) Qos control in wireline subscriber management
WO2017148206A1 (zh) 一种计费方法和装置
WO2016109970A1 (zh) 网络实体及服务策略管理方法
KR20170045262A (ko) 셀룰러 네트워크에서의 플렉시블 모바일 스티어링을 위한 방법 및 장치
WO2016107374A1 (zh) 一种带宽控制的方法、装置及系统
US20150009896A1 (en) Session termination in a mobile packet core network
WO2016110063A1 (zh) 一种网络控制的方法及装置
WO2013056470A1 (zh) 一种接入处理方法、设备和系统
US20230179992A1 (en) Service Selection Set Publishing to Device Agent with On-Device Service Selection

Legal Events

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

Ref document number: 14855426

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14855426

Country of ref document: EP

Kind code of ref document: A1