CN108632774B

CN108632774B - Service switching processing method and related device and system

Info

Publication number: CN108632774B
Application number: CN201710161888.0A
Authority: CN
Inventors: 刘秀娟
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-03-17
Filing date: 2017-03-17
Publication date: 2021-08-03
Anticipated expiration: 2037-03-17
Also published as: CN108632774A

Abstract

The embodiment of the application discloses a service switching processing method, a charging platform and a service switching processing system. The charging platform is mainly used for making service switching decisions and plays multiple roles (the charging platform is sometimes regarded as a service platform by a core network, and the charging platform is sometimes regarded as a core network by a service platform), so that the dependence degree of service switching on the core network is reduced, the core network of each manufacturer is not required to be coordinated to carry out butt joint tests with the service platform, and the introduction cost of new services is further reduced (for example, when an operator develops new multimedia services, a signaling point is not required to be added in the core network, and a related trigger rule is configured at the signaling point). And because the charging platform has stronger service switching control right, the charging platform is favorable for ensuring the accurate controllability of the charging platform on the service charging process, for example, the notification characteristics of the user account of the charging platform are not lost before the call.

Description

Service switching processing method and related device and system

Technical Field

The present application relates to the field of communications technologies, and in particular, to a service switching processing method, a charging platform, and a service switching processing system.

Background

At present, with the rapid development of network technology, personal services also show a trend of more and more diversification. Various multimedia services such as voice over Long Term Evolution (LTE) networks are increasing.

Switching (english: Handover) is a call Handover technique. In some scenarios, Handover refers to a technology in which a service point in a multimedia platform receives a service originating call and then issues a Handover message to inform a core network to end the session, and the core network triggers another service again to perform subsequent call processing.

In the traditional technology, a core network is mainly relied on to trigger the service again based on Handover. The core network distinguishes different trigger mechanisms, a plurality of manufacturers exist in the core network of the existing network, trigger test change needs to be carried out in a matching mode, and a lot of troubles are brought to new service introduction of operators due to the fact that the number of the core networks is large, the coverage area is wide, and the maintenance workload is huge.

Disclosure of Invention

The embodiment of the application provides a service switching processing method, a related device and a related system, which are beneficial to reducing the dependence degree of service switching on a core network and further beneficial to reducing the introduction cost of new services.

In a first aspect, an embodiment of the present application provides a service switching processing method, which may include: the core network sends the first service call to the charging platform. The charging platform receives a first service call sent by a core network, wherein the first service call carries a user identifier, a first service identifier and a first session identifier. The charging platform may determine a service provision condition of the user represented by the user identifier, and determine an intra-session service switching relationship between services, for example, when it is determined that the user represented by the user identifier provides a second service, and it is determined that an intra-session service switching relationship exists between the first service represented by the first service identifier and the second service (in this case, it may be considered that the second service may be a first service), send a second service call to the service platform, where the second service call carries the user identifier, a second service identifier, and a second session identifier, the second service represented by the second service identifier is different from the first service, and the session represented by the second session identifier is different from the session represented by the first session identifier.

And the charging platform sends a fourth service message to the core network under the condition of receiving a third service message sent by the service platform, wherein the third service message carries the user identifier, the second service identifier and the second session identifier, and the fourth service message carries the user identifier, the first service identifier and the first session identifier.

The service platform may be, for example, a multimedia service platform or other service platforms. Wherein the second service may be, for example, a multimedia service (e.g., a voice service, etc.), etc. Specifically, for example, the second service may be a pay-per-view service or a multi-party call service.

It can be seen that, in the above exemplary scheme, the charging platform mainly performs service switching decision, and the charging platform simultaneously plays multiple roles (the charging platform is sometimes regarded as a service platform by the core network, and the charging platform is sometimes regarded as a core network by the service platform), so that the degree of dependence of service switching on the core network is reduced, and it is not necessary to coordinate the core network of each manufacturer and the service platform to perform docking test, thereby being beneficial to reducing the introduction cost of a new service (for example, when an operator develops a new multimedia service, it is not necessary to add a signaling point in the core network, and a related trigger rule is configured at the signaling point). And because the charging platform has stronger service switching control right, the charging platform is favorable for ensuring the accurate controllability of the charging platform on the service charging process, for example, the notification characteristics of the user account of the charging platform are not lost before the call.

In some possible embodiments, a service switching policy is configured in the charging platform, and an intra-session service switching relationship between services described in the service switching policy includes: an intra-session service switching relationship between the first service and the second service.

It can be seen that, since the service switching policy is configured on the charging platform, the charging platform is facilitated to flexibly make service switching decisions accordingly. Furthermore, the operator can also update the service switching strategy in the charging platform according to the requirement, which is favorable for further improving the flexibility and customization of the service switching decision of the charging platform.

In some possible embodiments, the receiving, by the charging platform, the first service call sent by the core network includes: the charging platform receives a first Service call sent by a Gateway Mobile Switching Center (GMSC) or a Service Switching Point (SSP) in a core network. For example, the first service call is an Initial Detection Point (IDP) message or another service call.

In some possible embodiments, the receiving, by the charging platform, the first service call sent by the core network includes: the charging platform receives a first service Call sent by a calling Call Session Control Function (abbreviated as CSCF) entity in a core network. For example, the first service call is an Invite (English: Invite) message or other service call.

In a second aspect, an embodiment of the present application provides a charging platform, including:

the communication unit is used for receiving a first service call sent by a core network, wherein the first service call carries a user identifier, a first service identifier and a first session identifier.

And the switching strategy unit is used for determining the service opening condition of the user represented by the user identification and determining the intra-session service switching relationship among the services.

The communication unit is further configured to send a second service call to the service platform under a condition that the handover policy unit determines that the user represented by the user identifier opens a second service and that an intra-session service handover relationship exists between the first service represented by the first service identifier and the second service, where the second service call carries the user identifier, a second service identifier, and a second session identifier, where the second service represented by the second service identifier is different from the first service, and the session represented by the second session identifier is different from the session represented by the first session identifier.

The communication unit is further configured to send a fourth service message to the core network under the condition that a third service message sent by the service platform is received, where the third service message carries the user identifier, the second service identifier, and the second session identifier, and the fourth service message carries the user identifier, the first service identifier, and the first session identifier.

In some possible embodiments, the charging platform may further include a caching unit, configured to cache the configured service switching policy, where an intra-session service switching relationship between services described in the service switching policy includes: an intra-session service switching relationship between the first service and the second service.

In some possible embodiments, the receiving, by the communication unit, the first service call sent by the core network includes: receiving a first service call sent by a GMSC or SSP in a core network; or the charging platform receives a first service call sent by a calling CSCF entity in a core network. In some possible embodiments, the first service call is an IDP message or the first service call is an Invite message.

In a third aspect, an embodiment of the present application provides a service switching processing system, including:

the system comprises an interconnected core network, a charging platform and a service platform; the charging platform is any one of the charging platforms provided by the embodiments of the present application.

In some possible implementations of the aspects, a third service message (e.g., ETC/CTR) is used to instruct the billing platform to connect the playback device, and a fourth service message (e.g., ETC/CTR) is used to instruct the core network to connect the playback device. Or the third service message is used for indicating the charging platform to disconnect the playback device, and the fourth service message is used for indicating the core network to disconnect the playback device. Or the third service message is a third 200OK message and the fourth service message is a fourth 200OK message.

In a fourth aspect, embodiments of the present application provide a computer-readable storage medium storing program code. The program code comprises instructions for performing part or all of the steps of the method performed by the charging platform or service platform or core network in the first aspect.

In a fifth aspect, embodiments of the present application provide a computer program product comprising instructions that, when run on a billing platform, cause the billing platform to perform some or all of the steps of the method in the above aspects performed by the billing platform.

In a sixth aspect, an embodiment of the present application provides a charging platform, including: a processor, a communication interface, and a memory coupled to each other. The processor is configured to perform some or all of the steps of the method performed by the billing platform in the above aspects.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments or the background art of the present application, the drawings required to be used in the embodiments or the background art of the present application will be described below.

Fig. 1-a is a schematic structural diagram of a service switching processing system according to an embodiment of the present application;

fig. 1-B is a schematic structural diagram of another service switching processing system provided in the embodiment of the present application;

fig. 2 is a schematic flowchart of a service switching processing method according to an embodiment of the present application;

fig. 3 is a schematic flow chart of another service handover processing method according to an embodiment of the present application;

fig. 4 is a schematic flowchart of another service handover processing method according to an embodiment of the present application;

fig. 5 is a schematic diagram of a charging platform provided in an embodiment of the present application;

fig. 6 is a schematic diagram of another billing platform provided by the embodiment of the invention.

Detailed Description

The embodiments of the present application will be described below with reference to the drawings.

Referring to fig. 1-a and fig. 1-B, fig. 1-a and fig. 1-B are schematic structural diagrams of several service switching processing systems provided in an embodiment of the present application, where the service switching processing system includes a core network, a charging platform, and a service platform that are interconnected. Both the billing platform and the service platform may include one or more physical computer devices.

The service platform may be, for example, a multimedia service platform or other service platforms.

The core network may include core network elements such as CSCFs (e.g., a calling CSCF and a called CSCF), GMSCs, or SSPs. Wherein the CSCF belongs to an IP Multimedia Subsystem (IMS) network.

The technology of the embodiment of the present application can be implemented based on the service switching processing system with the architecture illustrated in fig. 1-a and fig. 1-B by way of example or a modified architecture thereof.

Referring to fig. 2, fig. 2 is a schematic flow chart of a service handover processing method provided in the embodiment of the present application, where the method may include, but is not limited to, the following steps:

201. the core network sends the first service call to the charging platform. The first service call carries a user identifier, a first service identifier and a first session identifier.

202. The charging platform receives a first service call sent by a core network. And the charging platform determines the service opening condition of the user represented by the user identification and determines the intra-session service switching relationship between services.

In some possible embodiments, the receiving, by the charging platform, the first service call sent by the core network includes: the charging platform receives a first service call sent by GMSC or SSP in a core network. For example, the first service call is an IDP message or other service call.

In other possible embodiments, the receiving, by the charging platform, the first service call sent by the core network includes: the charging platform receives a first service call sent by a calling CSCF entity in a core network. For example, the first traffic call is an Invite message or other traffic call.

203. And the charging platform sends a second service call to the service platform under the condition that the user represented by the user identifier is determined to open a second service, and the first service represented by the first service identifier and the second service have an intra-session service switching relationship (in this case, the second service can be considered to be the first service). The second service call carries the user identifier, a second service identifier and a second session identifier, the second service represented by the second service identifier is different from the first service, and the session represented by the second session identifier is different from the session represented by the first session identifier.

Wherein the second service may be, for example, a multimedia service (e.g., a voice service, etc.), etc. Specifically, for example, the second service may be a pay-per-view service or a multi-party call service.

In addition, if the charging platform determines that the user represented by the user identifier does not open the second service, or determines that the first service represented by the first service identifier and the second service do not have an intra-session service switching relationship, the charging platform may forward the first service call to the service platform, for example, or may perform processing in other conventional manners. In this embodiment, the case that the charging platform determines that the user represented by the user identifier opens the second service, and determines that the first service represented by the first service identifier and the second service have an intra-session service switching relationship is taken as an example.

204. And the charging platform sends a fourth service message to the core network under the condition of receiving a third service message sent by the service platform. Wherein the third service message carries the user identifier, the second service identifier and the second session identifier. Wherein the fourth service message carries the user identifier, the first service identifier and the first session identifier.

For example, a third service message (e.g., ETC/CTR) is used to instruct the billing platform to connect with playback devices, and a fourth service message (e.g., ETC/CTR) is used to instruct a core network to connect with playback devices. Or the third service message is used for indicating the charging platform to disconnect the playback device, and the fourth service message is used for indicating the core network to disconnect the playback device. Or the third service message is a third 200OK message and the fourth service message is a fourth 200OK message. Of course, the third service message and the fourth service message are not limited to the above exemplary messages.

It can be seen that, since the service switching policy is configured on the charging platform, the charging platform is facilitated to flexibly make service switching decisions accordingly. Furthermore, the operator may also update the service switching policy in the charging platform as needed (for example, the network management device may send a request for updating the service switching policy in the charging platform, and then perform targeted update on the service switching policy configured in the charging platform), which is beneficial to further improve the flexibility and customization of the service switching policy of the charging platform.

This is exemplified by some more specific scenarios.

See fig. 3. In the following, it is exemplified that a user on a charging platform activates a voice service (e.g. a called party charging service). The service provisioning process may include: and opening the called payment service of the user on the charging platform and opening the called payment service of the user on the multimedia platform. The signaling flow when the user dials the called and called pay number may be as shown in fig. 3 for example.

301. And the core network (such as GMSC/SSP in the core network) sends IDP information (service call) to the charging platform according to the subscription information, and the IDP information (service call) carries the user identification of the calling user, the first service ID and the first session ID.

302. After finishing the corresponding service call processing, the charging platform sends a Request Report BCSM Event (RRBE) message for responding to the IDP message to the core network, wherein the RRBE message indicates the core network to configure a Detection Point (DP) Event corresponding to the first session ID. BCSM is the Basic Call State Model (English, abbreviated as BCSM).

303. And the charging platform issues an ETC/CTR message to the core network, wherein the ETC/CTR message is used for indicating the core network to be connected with playback equipment.

304. The charging platform sends an indication message for indicating the core network to play a prompt voice (the prompt voice can be specifically used for reminding the balance of the user and the like) to the calling party to the core network.

This indication message is, for example, a play speech (PA) message/Prompt speech and Collect user information (PC) or other indication message.

305. The core network sends a proprietary resource report (SRR) message/PC _ C message to the charging platform, wherein the SRR/PC _ C message is used for informing a playback result.

306. The charging platform sends an indication message (e.g. DFC message) to the core network for instructing the core network to disconnect the playback device.

307. When the charging platform identifies that the user opens the called payment service based on the service subscription information corresponding to the user identifier of the calling user, and the intra-session service switching relationship between the services of the service switching strategy in the charging platform comprises: and if the intra-session service switching relationship between the first service and the called payment service exists, the charging platform sends an IDP message to a service point of the called payment service on the multimedia platform, wherein the IDP message carries the ID of the calling party, the ID of the second service (namely the service ID of the called payment service) and the ID of the second session. The charging platform triggers the service point of the called payment service on the multimedia platform through a Handover mechanism.

308. After finishing relevant processing, the service point of the called payment service sends an RRBE message to the charging platform, the RRBE message indicates the charging platform to configure a corresponding DP event, and the RRBE message carries a calling party ID, a second service ID (namely the service ID of the called payment service) and a second session ID.

309. And the charging platform sends an RRBE message to the core network, wherein the RRBE message is used for indicating the core network to configure a corresponding DP event, and the RRBE message carries the ID of the calling party, the ID of the first service and the ID of the first session.

310. The service point of the called payment service sends an indication message (for example, an ETC/CTR message) to the charging platform, where the indication message is used to indicate that the charging platform is connected to the playback device, and the indication message carries, for example, a caller ID, a service ID of the called payment service, and a second session ID.

311. The charging platform sends an indication message (for example, an ETC/CTR message) to the core network, where the indication message is used to indicate that the charging platform connects to the playback device, and may carry, for example, a caller ID, a first service ID, and a first session ID.

312. The service point of the called payment service sends a PA message/PC message to the charging platform, and the PA/PC is used for instructing the charging platform to play a voice prompt (whether the called payment is selected or not) to the user.

313. The charging platform sends a PA/PC message to the core network, and the PA/PC message is used for instructing the core network to play a voice prompt (specifically, whether the called party payment is selected or not) to the user terminal.

314. The core network sends SRR/PC _ C information to the charging platform, and the SRR/PC _ C information is used for informing the charging platform of user selection.

315. The charging platform sends SRR/PC _ C information to a service point of the called payment service, and the SRR/PC _ C information is used for informing the charging platform of user selection.

316. The service point of the called payment service sends a DFC message to the charging platform, and the DFC is used for indicating the charging platform to disconnect the playback device.

317. And the charging platform sends a DFC message to the core network, wherein the DFC message is used for indicating the core network to disconnect the playback equipment.

318. The service point of the called payment service sends an application charging (abbreviated as AC) message to the charging platform, and the AC message is used for instructing the charging platform to start charging.

319. The charging platform sends an AC message to the core network, and the AC message is used for indicating the core network to start charging.

320. The service point of the called payment service sends a Continuous (CONTINUE) message/connection (CONNECT) message to the charging platform, and the CONTINUE message/CONNECT message is used for indicating the charging platform to CONNECT the called user.

321. The charging platform sends a CONTINUE/CONNECT message to the core network, and the CONTINUE/CONNECT message indicates the core network to CONNECT the called user.

322. The core network sends an Application Charging Report (ACR) to the charging platform, and the ACR carries the charging information of the called user.

323. The charging platform sends ACR to the service point of the called charging service, wherein the ACR carries the charging information of the called user.

324. The core network sends a call reporting Event (ERB) to the charging platform, and the ERB is used for indicating the user hang-up Event.

325. The charging platform sends an ERB to the service point of the called payment service, wherein the ERB is used for indicating the user hang-up event.

326. The service point of the called payment service sends a Release Call (RC) message to the charging platform, and the RC message instructs the charging platform to release the Call.

327. The charging platform sends a RC message to the core network, which RC instructs the core network to release the call.

It can be seen that, in the scenario of the called payment service, the charging platform mainly makes a service switching decision, and the charging platform simultaneously plays multiple roles (the charging platform is sometimes regarded as a service platform by the core network, and the charging platform is sometimes regarded as a core network by the service platform), so that the degree of dependence of service switching on the core network is reduced, and it is not necessary to coordinate the core network of each manufacturer with the service platform for docking test, which is further beneficial to reducing the introduction cost of new services (for example, when an operator develops new multimedia services, it is not necessary to add signaling points in the core network, and configure related trigger rules at the signaling points). And because the charging platform has stronger service switching control right, the charging platform is favorable for ensuring the accurate controllability of the charging platform on the service charging process, for example, the notification characteristics of the user account of the charging platform are not lost before the call.

See fig. 4. The application scenario of this embodiment is a 4G VoLTE scenario, where a Session Initiation Protocol (SIP) is used as a call control protocol. In the VoLTE scenario, it is also taken as an example that a user opens a service (such as a multi-party call service) on a charging platform.

The signaling flow when the user dials the called number can be as shown in fig. 4 for example.

401. The calling user initiates a call, the IMS _ CSCF identifies the user of the charging platform, and triggers an INVITE message (English) to the charging platform after a prefix is added to the called number, wherein the INVITE message carries the calling user identification, the service identification of the first service and the second session identification.

402. And the charging platform returns a 100Tring message for responding to the INVITE message to the IMS _ CSCF after receiving the INVITE message, and completes the related call processing.

403. The charging platform sends an INVITE message to the called IMS _ CSCF.

404. The called IMS _ CSC returns a 100Tring message for responding to the INVITE message, informing the charging platform that the relevant message has been received.

405. The called CSCF sends initial address message (IAM for short) to the calling CSCF.

406. The calling CSCF sends Address Complete Message (ACM) to the called CSCF.

407. The called IMS _ CSCF sends a 180Ringing SDPb message to the charging platform, the 180Ringing SDPb message being used to inform the charging platform of the called Ringing.

408. The charging platform sends a 180Ringing SDPb message, which is used to inform the calling IMS _ CSCF that the call is Ringing.

409. The calling IMS _ CSCF sends a PRACK message to the charging platform for responding to the 180Ringing SDPb.

410. The charging platform sends a PRACK message to the called IMS _ CSCF for responding to the 180Ringing SDPb.

411. The called IMS _ CSCF sends a 200OK to the charging platform, which is used to inform the charging platform that the call is ready.

412. The charging platform sends an INVITE message to a service point of a multi-party call service of the multimedia platform, wherein the INVITE message carries a calling party identifier, a service identifier (different from the first service identifier) of the multi-party call service and a second session identifier.

413. And the service point of the multi-party call service sends a 100Tring message for responding to the INVITE message to the charging platform.

414. The service point of the multi-party call service sends a 200OK message to the charging platform, and the 200OK message is used for informing the readiness of the service of the charging platform. This 200OK message may carry, for example, the caller identification, the service identification of the multi-party call service (different from the first service identification), and the second session identification (different from the first session identification).

415. And the charging platform sends a 200OK message to the calling IMS _ CSCF, wherein the 200OK message is used for informing the charging platform of service readiness. This 200OK message may carry, for example, the calling subscriber identity, the first service identity and the first session identity.

416. The calling user hears the called ring back tone.

417. The called IMS _ CSCF sends a 200OK message to the charging platform, which 200OK message is used to indicate that the called party is connected to the call.

418. The charging platform sends a send 200OK message to the calling IMS _ CSCF indicating that the called party is connected to the call.

419. The calling IMS _ CSCF sends an ACK message to the charging platform.

420. And the charging platform sends an ACK message to the called IMS _ CSCF, and the two parties start to communicate.

421. And the calling IMS _ CSCF sends a BYE message to the charging platform to inform the charging platform that the calling user hangs up.

422. And the charging platform sends a BYE message to the called IMS _ CSCF and informs the called IMS _ CSCF that the calling user hangs up.

423. And the called IMS _ CSCF sends a 200OK message for responding to the BYE message to the charging platform and ends the call.

424. The charging platform sends a 200OK message for responding to the BYE message to the calling IMS _ CSCF, and ends the call.

It can be seen that, in the VoLTE scenario, a charging platform is mainly used for making a service switching decision, and the charging platform plays multiple roles simultaneously (the charging platform is sometimes regarded as a service platform by a core network, and the charging platform is sometimes regarded as a core network by a service platform), so that the degree of dependence of service switching on the core network is reduced, and the core network of each manufacturer and the service platform do not need to be coordinated for docking test, thereby being beneficial to reducing the introduction cost of a new service (for example, when an operator develops a new multimedia service, a signaling point does not need to be added in the core network, and a related trigger rule is configured at the signaling point). And because the charging platform has stronger service switching control right, the charging platform is favorable for ensuring the accurate controllability of the charging platform on the service charging process, for example, the notification characteristics of the user account of the charging platform are not lost before the call.

The method of the embodiments of the present application is explained in detail above, and the apparatus of the embodiments of the present application is provided below.

Referring to fig. 5, fig. 5 is a schematic structural diagram of a charging platform 500 according to an embodiment of the present application.

A communication unit 510, configured to receive a first service call sent by a core network, where the first service call carries a user identifier, a first service identifier, and a first session identifier.

A switching policy unit 520, configured to determine a service opening condition of the user represented by the user identifier, and determine a service switching relationship in a session between services.

The communication unit 510 is further configured to, when the handover policy unit determines that the user represented by the user identifier opens a second service and determines that an intra-session service handover relationship exists between the first service represented by the first service identifier and the second service, send a second service call to the service platform, where the second service call carries the user identifier, a second service identifier and a second session identifier, where the second service represented by the second service identifier is different from the first service, and the session represented by the second session identifier is different from the session represented by the first session identifier;

the communication unit 520 is further configured to send a fourth service message to the core network under the condition that a third service message sent by the service platform is received, where the third service message carries the user identifier, the second service identifier, and the second session identifier, and the fourth service message carries the user identifier, the first service identifier, and the first session identifier.

In some possible embodiments, the charging platform may further include a caching unit 530, configured to cache the configured service switching policy, where the intra-session service switching relationship between the services described in the service switching policy includes: an intra-session service switching relationship between the first service and the second service.

In some possible embodiments, the receiving, by the communication unit 510, the first service call sent by the core network includes: receiving a first service call sent by a GMSC or SSP in a core network; or the charging platform receives a first service call sent by a calling CSCF entity in a core network. In some possible embodiments, the first service call is an IDP message or the first service call is an Invite message.

In some possible embodiments, the third service message (e.g., ETC/CTR) is used to instruct the charging platform to connect the playback device, and the fourth service message (e.g., ETC/CTR) is used to instruct the core network to connect the playback device. Or the third service message is used for indicating the charging platform to disconnect the playback device, and the fourth service message is used for indicating the core network to disconnect the playback device. Or the third service message is a third 200OK message and the fourth service message is a fourth 200OK message.

Referring to fig. 6, an embodiment of the present application provides a charging platform 600, including: a processor 630, a communication interface 620, and a memory 610 coupled to one another; the processor is configured to perform some or all of the steps of the method performed by the billing platform in the above aspects.

The memory 610 is configured to store instructions, and the processor 630 is configured to execute the instructions, wherein the communication interface 620 is configured to communicate with other devices under the control of the processor 630. When the processor 630 executes the instructions, the steps performed by the billing platform in any of the above embodiments of the present application may be performed according to the instructions. Processor 630 may also be referred to as a Central Processing Unit (CPU). Memory 610 may include both read-only memory and random-access memory, and provides instructions and data, etc. to processor 630. A portion of the memory 610 may also include non-volatile random access memory. The components of the billing platform in a particular application are coupled together, for example, by a bus system. The bus system may include a power bus, a control bus, a status signal bus, and the like, in addition to a data bus. For clarity of illustration, however, the various buses are designated in the figure as bus system 640. The method disclosed in the embodiments of the present application may be implemented in the processor 6306 or implemented by the processor 630. The processor 630 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 630. The processor 630 may be a general purpose processor, a digital signal processor, an application specific integrated circuit, an off-the-shelf programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components. Processor 630 may implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present application. The general purpose processor 630 may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software modules may reside in ram, flash memory, rom, prom, or eprom, registers, etc., storage media as is well known in the art. The storage medium is located in the memory 610, and the processor 630 can read the information in the memory 610 and combine the hardware to perform the steps of the above method.

For example, the processor 630 may be configured to receive a first service call sent by a core network through a communication interface, where the first service call carries a user identifier, a first service identifier, and a first session identifier; determining the service opening condition of the user represented by the user identification, and determining the intra-session service switching relationship between services; under the condition that it is determined that a user represented by the user identifier opens a second service and that an intra-session service switching relationship exists between a first service represented by the first service identifier and the second service, sending a second service call to the service platform through a communication interface, wherein the second service call carries the user identifier, a second service identifier and a second session identifier, wherein the second service represented by the second service identifier is different from the first service, and the session represented by the second session identifier is different from the session represented by the first session identifier; and under the condition that a third service message sent by the service platform is received through a communication interface, sending a fourth service message to the core network through the communication interface, wherein the third service message carries the user identifier, the second service identifier and the second session identifier, and the fourth service message carries the user identifier, the first service identifier and the first session identifier.

In some possible embodiments, the memory 610 is configured to cache configured service switching policies, where intra-session service switching relationships between services described in the service switching policies include: an intra-session service switching relationship between the first service and the second service.

In some possible embodiments, the receiving the first service call sent by the core network includes: receiving a first service call sent by a GMSC or SSP in a core network; or the charging platform receives a first service call sent by a calling CSCF entity in a core network. In some possible embodiments, the first service call is an IDP message or the first service call is an Invite message.

An embodiment of the present application provides a service switching processing system, which may include: interconnected core network, charging platform and service platform. The charging platform is any one of the charging platforms provided by the embodiments of the present application.

Embodiments of the present application provide a computer-readable storage medium, which may include instructions that, when executed on a computer, cause the computer to perform some or all of the steps of the method in the above aspects, which are performed by a charging platform or a core network or a service platform.

Embodiments of the present application provide a computer program product comprising instructions, which when run on a billing platform, cause the billing platform to perform some or all of the steps of the method in the above aspects performed by the billing platform.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (e.g., coaxial cable, fiber optic, digital subscriber line) or wirelessly (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., compact disk), or a semiconductor medium (e.g., solid state disk), among others. In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is merely a logical division, and the actual implementation may have another division, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted or not executed. In addition, the indirect coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, indirect coupling or communication connection of devices or units, and may be electrical or in other forms.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit may be implemented in the form of hardware, or may also be implemented in the form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk, which can store program codes.

Claims

1. A service switching processing method is characterized by comprising the following steps:

a charging platform receives a first service call sent by a core network, wherein the first service call carries a user identifier, a first service identifier and a first session identifier;

the charging platform sends a second service call to a service platform under the condition that it is determined that a user represented by the user identifier opens a second service and that an intra-session service switching relationship exists between a first service represented by the first service identifier and the second service, wherein the second service call carries the user identifier, a second service identifier and a second session identifier, the second service represented by the second service identifier is different from the first service, and the session represented by the second session identifier is different from the session represented by the first session identifier;

2. The method of claim 1, wherein a service handover policy is configured in the charging platform, and an intra-session service handover relationship between services described in the service handover policy includes: an intra-session service switching relationship between the first service and the second service.

3. The method of claim 1, wherein the second service is a called pay-per-view service or a multi-party call service.

4. The method according to any of claims 1 to 3, wherein the receiving, by the charging platform, the first service call sent by the core network comprises: the charging platform receives a first service call sent by a Gateway Mobile Switching Center (GMSC) or a Service Switching Point (SSP) in a core network, wherein the first service call is an IDP message of a starting detection point; or the charging platform receives a first service call sent by a calling call session control function entity in a core network.

5. The method of claim 4, wherein the first service call is an Initiate Detection Point (IDP) message or the first service call is an Invite message.

6. The method according to any one of claims 1 to 3, wherein the third service message is used to instruct the charging platform to connect with a playback device, and the fourth service message is used to instruct a core network to connect with a playback device; or the third service message is a third 200OK message, and the fourth service message is a fourth 200OK message.

7. A billing platform, comprising:

a communication unit, configured to receive a first service call sent by a core network, where the first service call carries a user identifier, a first service identifier, and a first session identifier;

a switching strategy unit, configured to determine a service opening condition of a user represented by the user identifier, and determine an intra-session service switching relationship between services;

the communication unit is further configured to send a second service call to a service platform under a condition that the handover policy unit determines that the user represented by the user identifier opens a second service and that an intra-session service handover relationship exists between the first service represented by the first service identifier and the second service, where the second service call carries the user identifier, a second service identifier, and a second session identifier, where the second service represented by the second service identifier is different from the first service, and the session represented by the second session identifier is different from the session represented by the first session identifier;

8. The billing platform of claim 7,

the charging platform further includes a cache unit, configured to cache the configured service switching policy, where an intra-session service switching relationship between services described in the service switching policy includes: an intra-session service switching relationship between the first service and the second service.

9. The billing platform of claim 7, wherein the second service is a called payment service or a multi-party call service.

10. The charging platform according to any one of claims 7 to 9, wherein the receiving, by the communication unit, the first service call sent by the core network comprises: receiving a first service call sent by a Gateway Mobile Switching Center (GMSC) or a Service Switching Point (SSP) in a core network; or the charging platform receives a first service call sent by a calling call session control function entity in a core network.

11. The billing platform of claim 10, wherein the first service call is an Initiate Detection Point (IDP) message or the first service call is an Invite message.

12. The charging platform according to any one of claims 7 to 9, wherein the third service message is used to instruct the charging platform to connect with a playback device, and the fourth service message is used to instruct a core network to connect with a playback device; or the third service message is a third 200OK message, and the fourth service message is a fourth 200OK message.

13. A service handoff processing system, comprising:

a core network, a charging platform and a service platform; wherein the charging platform is the charging platform of any one of claims 7 to 12.

14. The system of claim 13, wherein the service platform is a multimedia service platform.

15. A computer-readable storage medium, characterized in that,

the computer-readable storage medium stores program code, wherein the program code is capable of implementing the method of any one of claims 1 to 6 when executed by a computer device.