WO2009024041A1

WO2009024041A1 - Communication system, communication apparatus and method processing service based on soa

Info

Publication number: WO2009024041A1
Application number: PCT/CN2008/071522
Authority: WO
Inventors: Hui Li
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-08-23
Filing date: 2008-07-02
Publication date: 2009-02-26
Also published as: CN101374247A

Abstract

The embodiments of this invention disclose a communication system, communication apparatus and method processing service based on SOA, wherein the SOA communication system comprises: access control entity, utilized to control the accessing of the user; user service registry function entity, connecting and communicating with said access control entity; service control function entity, utilized to publish the user's service and discover the service signed by the user; and service control function entity, utilized to provide the user with the service signed by himself when the user accesses the network. The embodiments of this invention could provide more flexible schemes for service opening and service combining based on SOA, including the flexible combining of NGN's and the third party's service.

Description

Service-oriented communication system, communication device, and method of processing business

The present invention relates to Next Generation Network (NGN) technology, and more particularly to a service oriented communication system, a communication device, and a method of processing a service. Background technique

NGN is a packet-based network that provides telecommunications services. NGN uses a variety of broadband capabilities and quality of service (QoS) to ensure the delivery of data, and its business-related functions are independent of its delivery technology. In addition, NGN allows users to freely access different service providers and supports general mobility.

Service-Oriented Architecture (SOA) is a collection of services. Services communicate with each other. This communication may be a simple data transfer, or it may be that two or more services coordinate some activities. The service room needs some way to connect. A service is a function that is precisely defined, encapsulated, and independent of the environment and state of other services.

SOA is not a ready-made technology, but a way to structure and organize infrastructure and business functions. SOA is a model for designing, developing, deploying, and managing discrete logical units (services) in a computing environment. In an SOA-based system, the functionality of a specific application is built from a combination of loosely coupled components (that is, service services) that have a uniform interface definition. All the program functions in a system based on SOA architecture are encapsulated in some functional modules, and the installed programs or systems are assembled by using these encapsulated functional modules, which are different services in the SOA architecture. (services). The architecture model of SOA is shown in Figure 1.

IP Multimedia Subsystem (IMS) is a subsystem introduced by 3GPP on the packet network. It uses the packet domain as the bearer channel for its control signaling and media transmission. The Session Initiation Protocol (SIP) is used as a service control protocol to provide multimedia real-time communication services by separating service control from bearer control. The main functional entities in the IMS include a call control entity CSCF that controls functions such as user registration and session control, a home subscriber server HSS that centrally manages subscriber subscription data, and an application server AS that provides various service logic control functions.

At present, the research on NGN is based on IMS. With the NGN architecture of ETSI TISPAN, more user networks, access, core networks and interworking are considered on the basis of IMS, and with the deployment of IMS networks, the entire network will In the situation where multiple service networks such as IMS, NGN, CS Domain, and Internet Service coexist, the characteristics of IMS will absorb more services and eventually replace the circuit-switched CS network.

In the IMS network architecture, all non-basic session connection type value-added application services are provided for IMS users, which are provided in the AS entity, and the CSCF of the session control layer is the service of the base IMS SIP session to the AS running different value-added service logics. Trigger routing, and the functions of registration, security protection, QoS control, and basic session routing that all value-added applications can share provide a common platform to ensure that each AS provider only needs to pay attention to the design of the value-added service logic itself.

The application server AS interacts with the S-CSCF through the SIP-based ISC interface, and the S-CSCF performs contract matching rule matching according to the AS-based service-based subscription data and the currently input SIP message domain content, and performs matching to each AS according to the matching result. Routing. For a specified user and its S-CSCF, according to the special settings of its AS triggering rules, it not only supports the triggering of different services to different ASs, but also enables multiple triggers of the same session to multiple ASs, thus achieving the same user. The associated combination of value-added business logic.

The three business open modes provided by IMS are as follows:

SIP Application Server: A place where SIP business logic is loaded and executed. There can be SCIM (service capability interaction manager) ten kinds of application server: 3⁄4 into a specific application. IM-SSF: It is a special application server that detects the service trigger point specified by CAMEL and completes the adaptation of the CAP protocol with the SCP. It can realize the interworking of SIP and INAP/CAP to access the traditional SCP to provide the original value-added services of the circuit-switched network intelligent network for IMS users.

OSA SCS: is a unified service open model developed by 3GPP based on Parlay API to provide open and secure use of network resources for third-party application servers.

The current IMS network has the following deficiencies:

(1) Different sessions have different requirements for session capabilities. The capability of an S-CSCF cannot support all subscribers' subscription services. For example, the user subscribes to the telephone service and the IPTV service at the same time. The telephone service is characterized by short duration and time-based billing, while the IPTV service is characterized by long-term online, pay-per-view or monthly billing. If a large number of users use the IPTV service at the same time, the S-CSCF to which the user is assigned has no resources and capabilities to provide telephone services.

(2) The IMS service is open to the ISC interface and cannot meet the requirements of complex service control. For example, the initial filtering rule relies on the content of the SIP request message. Due to the uncertainty of the service interface, the same SIP message content needs to trigger different services. For example, an INVITE request triggers an IP Centrex service and a Telephony service. As another example, multiple initial filtering rules are serial triggers. If the AS is a B2BUA, the subsequently triggered AS needs to transparently transmit the message content, resulting in interdependence and chain upgrade between the service deployment ASs. For example, the INVITE request is sent to the Telephony AS and Conference AS by the hornworm. The Conference AS requires the Telephony AS to support transparent transmission of the "isfocus" parameter in the Contact header field.

(3) The ability of IMS to support the opening of external business is incomplete. IMS only supports the opening of IMS network capabilities to third parties through the Parlay API. On the one hand, the Parlay API capability is mainly to open the traditional telephone service and message service, and the service capability is limited. On the other hand, the IMS network lacks an interface for integrating the third party service, and does not support the release and access of the user terminal service capability.

(4) The IMS network architecture is too complicated. The IMS network only defines the logical architecture, regardless of the physical architecture, and the industry's understanding of the physical architecture is not consistent. For example: 3GPP billing function involves functional entities including: CDF, CGF, CCF, IM-GW, OCS, etc.; The body includes: IBCF, IWF, Transit, MGCF, BGCF, etc. The combination relationship is difficult to determine, and the networking is very complicated. Moreover, the IMS network defines interfaces based on functional entities, resulting in a large number of interfaces, numerous processes, slow progress of standards, and development workload. Huge, intercommunication test is complex; the characteristics of the physical network element such as billing, performance, monitoring and other functions are not easy to determine, and the implementation is poor.

Due to the above shortcomings, the existing IMS network is difficult to integrate with other networks, and cannot flexibly support other services. Summary of the invention

Embodiments of the present invention provide a service-oriented communication system, a communication device, and a method for processing a service, to support integration of an NGN network with other networks, and to flexibly support various services.

A service-oriented communication system, including:

An access control entity, configured to control user access to the network;

a user service registration function entity, which is in communication with the access control entity and the service control function entity, and is used for publishing the service of the user terminal and discovering the service subscribed by the user;

The service control function entity is in communication with the access control entity and the user service registration function entity, and is configured to provide a service for the user accessing the network to subscribe to the user.

a method for registering in a service-oriented communication system, the service-oriented communication system comprising: an access control entity, configured to control a user access network; a user service registration function entity, and the access control entity and service control The function entity communication connection is used for publishing the service of the user terminal and discovering the service subscribed by the user; the service control function entity is in communication with the access control entity and the user service registration function entity, and is used to provide a user for the user accessing the network. Contracted business; the registration method includes:

The user registration function entity receives a registration request of the user equipment;

The user registration function entity acquires user authentication data, initiates an authentication process to the user, and authenticates the user.

Method for distributing user terminal services in a service oriented communication system, the service oriented The communication system includes: an access control entity, configured to control user access to the network; a user service registration function entity, in communication with the access control entity and the service control function entity, for publishing the service of the user terminal and discovering the subscription of the user a service control function entity, which is in communication with the access control entity and the user service registration function entity, and is configured to provide a service that the user accesses the network to the user that is subscribed to the network;

The user service registration function entity receives a service release request of the user terminal sent by the user, where the request includes service description information of the service of the user terminal;

The user service registration function entity records service description information of the user terminal service, and manages the user terminal service by using the user identifier as a management object.

A method for discovering user terminal services in a service-oriented communication system, the service-oriented communication system comprising: an access control entity, configured to control a user access network; a user service registration function entity, and the access control entity The service control function entity communication connection is used for publishing the service of the user terminal and discovering the service subscribed by the user; the service control function entity is in communication with the access control entity and the user service registration function entity, and is used for the user accessing the network. Providing a service that the user subscribes to; the method for discovering the service of the user terminal includes:

The user service registration function entity receives the user terminal service discovery request;

The user service registration function entity queries the service description information of the corresponding user terminal service according to the user information in the request, wherein the user service registration function entity manages the user terminal service by using the user identifier as a management object;

The user service registration function entity returns the service description information of the queried user terminal service to the entity that sends the service discovery request.

A method for discovering a subscriber subscription service in a service-oriented communication system, the service-oriented communication system comprising: an access control entity, configured to control a user access network; a user service registration function entity, and the access control entity and service The control function entity communication connection is used for publishing the service of the user terminal and discovering the service subscribed by the user; the service control function entity is in communication connection with the access control entity and the user service registration function entity, and is used for providing the user accessing the network User The contracted service; the method for discovering the user's contracted service includes:

The user service registration function entity receives the user service discovery request forwarded by the access control entity; the user service registration function entity obtains the service description information subscribed by the user according to the user identification information in the request, and returns the service description information to the user.

A method for binding a service in a service-oriented communication system, the service-oriented communication system comprising: an access control entity, configured to control a user access network; a user service registration function entity, and the access control entity and service The control function entity communication connection is used for publishing the service of the user terminal and discovering the service subscribed by the user; the service control function entity is in communication connection with the access control entity and the user service registration function entity, and is used for providing the user accessing the network The service that the user subscribes to; the method for binding the service includes:

The access control entity receives the service binding request sent by the user, where the request carries the service description information of the requesting service;

Determining, by the access control entity, a target service control function entity of the service binding request, and forwarding the service binding request to the target service control function entity;

The target service control function entity provides a service to the user according to the service description information. A communication device comprising:

An authentication module, configured to acquire authentication data of the user after receiving the request message of the user, and perform authentication on the user;

The service publishing module is configured to record service description information of the user terminal service according to the received service release request, and manage the user terminal service by using the user identifier as a management object.

The service discovery module is configured to: when receiving the user service discovery request, obtain the service description information subscribed by the user according to the user identification information in the request, and return the service description information to the user.

A communication device comprising:

a service discovery module, configured to obtain service description data of a corresponding service when receiving a service request; The service control module is configured to invoke a service or invoke a module to combine services according to the service description data according to the control flow of the control script of the service.

In the service-oriented communication system architecture of the embodiment of the present invention, the user service registration function entity advertises the service of the user terminal and discovers the service subscribed by the user, and the service control function entity provides the user who subscribes to the network with the service subscribed by the user, and can provide the service. A more flexible business open approach and business combination approach based on SOA, including a flexible combination of NGN networks and third-party services. The service-oriented communication system architecture in this implementation enables the user terminal to provide the ability to create, publish, discover, and combine services. DRAWINGS

1 is a schematic diagram of an architectural model of an SOA in the prior art;

2A is a schematic structural diagram of a service-oriented communication system according to an embodiment of the present invention;

2B is a schematic structural diagram of a non-roaming service-oriented communication system according to an embodiment of the present invention;

3 is a schematic diagram showing the structure of a roaming/nomadic service-oriented communication system according to an embodiment of the present invention;

4 is a schematic structural diagram of a service-oriented communication system in which services are interworked according to an embodiment of the present invention;

FIG. 5 is a flowchart of user registration in an embodiment of the present invention;

6A is a process flow of service discovery based on a terminal request mode according to an embodiment of the present invention; FIG. 6B is a process flow of service delivery based on a terminal request mode according to an embodiment of the present invention; FIG. 6C is a service of visiting a network according to an embodiment of the present invention; FIG. 6D is a flowchart of processing for service publishing and discovery according to an embodiment of the present invention;

7 is a flowchart of processing for service publishing and discovery and registration integration in an embodiment of the present invention; FIG. 8 and FIG. 9 are flowcharts of processing user services according to an embodiment of the present invention;

10 is a flowchart of processing on a calling side in a user call service according to an embodiment of the present invention; FIG. 11 is a flowchart of processing performed by a called party in a registered state in a user call service according to an embodiment of the present invention;

FIG. 12 is a flowchart of processing a called party in an unregistered state in a user call service according to an embodiment of the present invention;

13 is a service flow diagram of a user terminal according to an embodiment of the present invention;

14 is a flowchart of invoking a third party service in an embodiment of the present invention;

15 is a flowchart of a service being used by a third-party service in a service-oriented communication system according to an embodiment of the present invention;

16 is a flowchart of user group registration in an embodiment of the present invention;

FIG. 17 is a flowchart of a calling service of a traditional user terminal according to an embodiment of the present invention; FIG. 18 is a flowchart of a called user side service of a conventional user terminal according to an embodiment of the present invention; FIG. The processing flow chart of the client based on the business discovery/release process and the registration process;

20 is a service flow diagram of a Web terminal according to an embodiment of the present invention;

21 is a schematic structural diagram of a service-oriented communication system according to an embodiment of the present invention;

FIG. 22 is a schematic diagram of a process for processing a service in a service-oriented communication system according to an embodiment of the present invention; FIG. 23 is a schematic structural diagram of a user service registration function entity according to an embodiment of the present invention; Schematic. detailed description

Traditional service usage is generally based on a service interface defined by a protocol, or the service interface itself is a public interface; and SOA flexibly supports various service interfaces through service publishing and discovery. From the implementation point of view, the traditional business implementation can be seen as a special SOA scenario that does not require business discovery. Therefore, it can be unified to a standard SOA-based description. In the embodiment of the present invention, the described architecture and process support the traditional service usage mode unless otherwise specified. The service is provided by the application service function entity ASF in the NGN network, and the business model based on the service-oriented architecture SOA can flexibly implement service access. For the NGN network, the service requester is mainly divided into two types: the user and the application service function entity. In this embodiment, the NGN service is classified into two types according to different service requesters, and the first type is a public service. A service is a service that is accessed by application service function entities, and a third-party service can be mapped into an internal service of the NGN network through a service gateway. The release, discovery, and use of the service are not related to the user; the second type is the user service, which is the service that the user subscribes to, or the service provided by the user terminal, and the user identity is included in the interface for publishing, discovering, and using the service.

For the public service and the user service, the service registration server (Service Registry Server) in the service architecture in this embodiment may include a User Service Registry Function (URF) and a Service Registry Function (SRF). A class logical entity, where the URF provides a registration server function for the user service; the SRF provides a registration server function for the public service.

The service subscribed by the user includes the home network service (generally the user-to-user service, for example, the call service. This type of service is often a legally regulated service, or a service requiring roaming control capability, or a called service, Or services that are not registered in the user) and visited network services (usually user-to-network services, for example, access to the Web home page. This type of service often does not require supervision and is deployed on third-party networks). The home network service requires that the service binding request initiated by the user must be routed to the home network for processing; and for the visited network service, if the user does not roam, it is provided by the home network, and if the user roams, it is provided by the visited network.

Each service that the user subscribes to corresponds to an application service function entity (ASF). In this embodiment, the special ASF that directly provides the subscription service to the user is called a Service Control Function (SCF). According to the SOA architecture, the SCF can call and combine other ASF services to serve users.

For the home network service, the service is provided by the SCF of the designated home network; and for the visited network service, if the user does not roam, the service is provided by the SCF of the designated home network, if When the user roams, the service is provided by the SCF specified by the visited network.

The SCF can provide services in a variety of ways, for example: SCF provides services directly to users; SCF acts as a service proxy, and invokes other ASF services; performs service triggering through user service filtering rules (for example, based on received service request message content, Time, service status, Presence information, etc. trigger the service), forward the service to other ASFs, and call other ASF services through a business scripting language (for example, BPEL) to synthesize new services.

This embodiment provides a new service oriented communication system, the functional architecture of the service oriented communication system inherits the advantages of the IMS network (eg, roaming, distributed, home network control, etc.), and integrates the aforementioned NGN layered protocol architecture and SOA architecture. A subscriber's subscription service can be provided by multiple SCFs; the entire NGN functional architecture is converged with SOA, and the client/server (C/S) architecture is fully utilized, where the call interworking function is provided as a service capability.

The structure of the service-oriented communication system in this embodiment does not depend on a specific service transport layer protocol, and may be based on multiple protocols, such as: Generic Service Initiation Protocol (GSIP), hypertext transmission. Protocol HTTP, Session Initiation Protocol SIP, Real-Time Streaming Protocol RTSP and other protocols.

As shown in FIG. 2A, a service-oriented communication system structure in this embodiment includes an access control entity 20, a user service registration function URF entity 21, a service control function SCF entity 22, a user database 23, and a service entity 24. The access control entity 20 is configured to control user access to the network; the user database 23 is configured to store and manage user data; and the user service registration function entity 21 is in communication with the access control entity 20 and the user database 23, respectively, for use in the user. The database 23 obtains user data, and provides service authentication, service distribution, and service discovery functions to the accessed users. The service control function entity 22 communicates with the user service registration function entity 21, the access control entity 20, and the user database 23, respectively. Providing services for users accessing the network, and/or performing service control on the users; the service entity 24 is in communication with the service control function entity S CF for providing services under the control of the service control function entity 22. Of course, in the scenario where there is no business entity 24, the service control function entity 22 can directly provide services to the user. Based on the NGN functional architecture shown in FIG. 2A, the NGN network architecture supporting non-roaming in this embodiment is as shown in FIG. 2B, where:

The service terminal UE 25 (User Equipment) can support the service authentication of the user and the terminal; support the capability and service of the terminal, and bind the capabilities of various network services according to the service description of the discovered user subscription. The form of the service terminal UE 25 includes various types such as an embedded terminal, a smart terminal, and a Web terminal.

The traditional access terminal TE 26 includes a SIP terminal, a POTS terminal, and an ISDN terminal. The access control entity ACF 201 supports the same traditional service experience without any changes to the protocol interface.

The access control entity 20 includes a proxy control function PCF (Proxy Control Function) entity 200 and an access control function ACF entity 201. The agent control function entity 200 serves as an access control entity of the NGN network, supports user access control and roaming control, supports access network management and access location management, supports QoS management of the access network, and supports users and terminals. Message routing for registering authentication requests, message routing for supporting service requests of users and terminals, and support for billing. The access control function ACF entity 201 is used as a control entity for the traditional user terminal to access the NGN network, and is used for the proxy terminal to complete the registration authentication of the user, the user group, and the device; the proxy user discovers the service capability of the user subscription; the proxy user invokes various networks. The ability of the service; the proxy user publishes the capabilities of the device to the network; the billing function.

The user service registration function entity 21 serves as a service registration server for the user and the user group, and the functions thereof include: performing service authentication on the user and the user group; providing user service authentication status management, and providing user service authentication to the ASF corresponding to the user subscription service. The user service discovery request is processed, and the network service description signed by the user is provided to the user; the user service release request is processed, and the user terminal service is released (the user terminal service includes user terminal registration information, capability information, and service information). In this embodiment, the user service registration function entity 21 manages the user terminal service by using the user identifier as a management object, and by providing a user-based service management and control manner, the prior art can only provide a service query, and cannot Insufficient associated with the user. The service control function entity 22 can be used as a special application service function entity that directly provides the subscription service to the user, and the functions thereof include: directly providing the service; and triggering the service based on the user subscription (for example, based on the received service request message content, time, and service status) Trigger services such as Presence information) perform other ASF service control; invoke other ASF services through service scripting language, hard coding, etc., and combine into new services, and support the charging of services.

The user database 23 includes a user authorization function UAF (User Authorization Function) entity 230 and a user configuration function UPF (User Profile Function) entity 231; the user authentication function entity 230 provides a user authentication data management function; its functions include: managing users and Various authentication algorithms of the user group, the authentication key; and the authentication key of the specified user is delivered to the user service registration function entity 21 according to the request. The user authentication function entity 230 can be integrated with other functional entities, for example, with the authentication device of the access network, or with the user configuration function entity 231. The user configuration function entity 231 is configured to provide a user service subscription data management function, and the functions include: managing service authentication information of the user and the user group; and signing the user subscription according to the request of the user service registration function entity 21 or the service entity 24 data.

The service entity 24 includes a Service Registration Function (SRF) entity 240 and an Application Function Function (ASF) entity 241. The business function entity 241 is configured to provide services for users, third parties or network internal business function entities, and publish the provided services through the service registration function entity 240; the service registration function entity 240 is used for publishing the NGN network service descriptions that are not related to the user. And discovering, and providing a service publishing agent for the business function entity 241, providing a service interface based on the SOA architecture, and providing the service function entity 241 and the user service registration function entity 21 with the capability of service discovery. Of course, the service entity 24 may also have no service registration function entity 240. In this scenario, the corresponding service function entity 241 may be directly queried to obtain a service interface, or the service interface itself is a public interface, and no query is needed.

The service interface between the service terminal 25 and the proxy control function entity 200 may be based on protocols such as GSIP, HTTP, SIP, RTSP, etc.; the traditional user terminal 26 and the access control function ACF entity The service interface between the 201 inherits the existing protocols of the traditional user terminal, including the signaling protocols such as SIP, ISDN, POTS, H.248, MGCP, and V5; the service interface S2 of the user service registration function entity 21 provides the release of the user service. The discovery function can be based on the protocols of GSIP, HTTP, SIP, RTSP, etc. The service interface S3 of the service control function 22 provides the binding function of the user service, and can be based on protocols such as GSIP, HTTP, SIP, RTSP, and the user authentication function entity 230. The interface D1 provides an authentication data query, which may be based on protocols such as GSIP, Diameter, Radius, LDAP, MAP, and INAP. The interface D2 of the user configuration function entity 231 provides user subscription data query, which may be based on GSIP, Diameter, Radius, LDAP, MAP, The service interface R1 of the service registration function entity 240 provides the public service release and discovery function, and can be based on protocols such as GSIP, HTTP, SIP, and RTSP; and the service interface R2 of the service function entity 241 provides the binding function of the public service. , can be based on GSIP, HTTP, SIP, RTSP and other protocols.

The structure of the roaming/nomadic service-oriented communication system supporting the home network service in this embodiment is as shown in FIG. 3, wherein the edge control function ICF entity 300 is used for roaming network control, location information management, QoS management, message routing, and counting. The fee and the like; the remaining functional entities in Figure 3 are the same as the functional entities in Figure 2B and will not be described again. The proxy control function PCF entity of the visited network, the access control function ACF entity forwards the request of the roaming user to the edge control function ICF entity 300 of the home network, and the edge control function ICF entity 300 forwards the user service registration function entity to the home network or Business Control Function Entity.

Edge Control Function The service interface provided by the ICF entity 300 can be based on GSIP, HTTP,

SIP, RTSP and other protocols.

The structure of the service-oriented communication system supporting service interworking in this embodiment is as shown in FIG. 4, wherein the gateway function GWF (Gateway Function) entity 400 is a special service function ASF, and its functions include: It is distributed to third-party networks and provides NGN network service access proxy functions for third-party networks. Third-party services are published to the NGN network, and third-party service access proxy functions and billing functions are provided for the NGN network. Mutual The ICF (Interworking Function) entity 401 is a special service-providing ASF entity, and its functions include: providing services for inter-network services to other networks, including services such as calls and messages; receiving services from external networks. The request, including services such as calls and messages, is forwarded to the internal functional entity of the network according to the service request; the charging function.

The interface Iw1 of the interworking function entity 401 is an interworking interface for telecommunication traditional services (such as services such as calls and messages), and may be based on protocols such as GSIP, SIP, BICC, and ISUP; the interface Iw2 of the network function entity 400 is a service interworking interface based on the SOA architecture. Provides services for discovery, distribution, and use (binding) functions, which can be based on protocols such as GSIP, HTTP, SIP, and RTSP.

The service-oriented communication system structure in this embodiment is described based on various service applications, and the service transmission protocol may be based on various protocols such as GSIP, HTTP, and SIP. The GSIP protocol is used as a service transmission protocol to describe the implementation of services in the NGN.

Network authentication of the home network can be authenticated based on user registration and authenticated based on service discovery (or publishing). If the network supports the user-based authentication mode, the user service registration function URF entity initiates authentication for the user when receiving the user registration request; if the user is authenticated based on the service discovery (or publishing), the user service registration function URF entity Upon receiving a service discovery (or release) request, the requester is authenticated. The following is an authentication process based on user registration:

The user terminal initiates a registration request, and the registration message includes capability information of the terminal. URF acts as a registration server to authenticate users. After the user authentication succeeds, the URF saves the registration information and capability information of the user terminal (the URF may use the registration information and capability information of the user terminal as the user terminal service for other entities to discover), and then, in the user registration success response message, User registration information and business description data are returned to the user. A user registration instance is shown in FIG. 5: Step 501. The service terminal UE initiates a registration request to the user service registration function URF entity according to the terminal information and the user information.

Step 502. The proxy control function PCF entity performs an access check on the request message, and then routes the message to the user service registration function URF entity. Step 503. The user service registration function URF entity checks the user registration status, determines that the user has not authenticated, and sends information such as user and terminal information, an authentication algorithm, and the like to the UAF, and queries the user authentication data.

Step 504. User authentication function The UAF entity returns the authentication data corresponding to the user and the terminal to the user service registration function URF entity.

Step 505. User service registration function The URF entity sends a response message according to the authentication data, and the message includes user authentication challenge information.

Step 506. Proxy Control Function The PCF entity returns an authentication challenge to the UE.

Step 551. The UE calculates an authentication response and re-initiates the registration request.

Step 552. Proxy Control Function The PCF entity performs an access check on the request message, and then the route message to the user service registration function URF entity.

Step 553. User registration function The URF entity checks the authentication response. After the authentication is passed, the user registration information is saved, and the user registration status is updated. In the registration response message that the user successfully registered, the user registration information is returned to the user.

Step 554. Proxy Control Function The PCF entity receives the registration response message and saves the relevant user information, and then returns the registration response message to the UE.

In this embodiment, the user terminal service advertisement and the user subscription service discovery may be performed in multiple manners, for example, the terminal request method, that is, the UE initiates a discovery or release request to the user service registration function URF entity, and the user service registration function URF entity responds to the message. The service description data signed by the user is returned to the UE. The subscription notification method, that is, the UE initiates a subscription request to the user service registration function URF entity, and the user service registration function URF entity establishes a subscription relationship with the UE; then, the user service registration function URF entity returns the service description data subscribed by the user to the notification message. UE. The network push method, that is, the user service registration function, the URF entity pushes the service description data to the UE after the user successfully registers.

After receiving the service request of the user, the SCF entity needs to check the service authentication information requested by the user (including the user registration status, service execution permission information, etc.), and the service control. There are various methods for obtaining the user service authentication information by the function SCF entity, for example: the user service registration function URF entity actively reports the user service authentication information to the service control function SCF entity (third party registration mode); or, the service control function After receiving the user service request, the SCF entity actively queries the user service registration function URF entity for the user service authentication information; or the service control function SCF entity subscribes the user service authentication information to the user service registration function URF entity, when the user data is transformed. The user service registration function URF entity notifies the service control function SCF entity.

The user terminal service release process and the user subscription service discovery process may be two separate processes, or may be combined. For the user registration process, if it is controlled by the service application layer, the user registration process can be integrated with the user terminal service release process and the user subscription service discovery process.

In an embodiment shown in FIG. 6A, the service discovery is an independent process based on the terminal request mode of the home network, and the user service registration function URF entity actively notifies the service control function SCF entity of the service authentication information of the user, and assumes the user Not yet authenticated. The specific processing steps for business discovery are as follows:

Step 601. The UE initiates a service discovery request to the user service registration function URF entity. Step 602. Proxy Control Function The PCF entity performs an access check on the request message, and then the routing message to the user service registration function URF entity.

Step 603. User service registration function The URF entity checks the user service status, and then requests the user authentication function UAF entity to download the user's authentication data.

Step 604. User Authentication Function The UAF entity returns the user's authentication data to the user service registration function URF entity.

Step 605. User service registration function The URF entity sends an authentication to the UE according to the user authentication data.

Step 606. Proxy Control Function The PCF entity returns an authentication response message to the UE.

Step 607. The UE calculates an authentication response according to the authentication message, and re-registers the service with the user. The URF entity can initiate a service discovery request.

Step 608. Proxy Control Function The PCF entity performs an access check on the request message, and then the route message to the user service registration function URF entity.

Step 609. User Service Registration Function The URF entity receives the user request and checks the authentication response. If the authentication is passed, the user service registration function URF entity configures the function to the user. The UPF entity requests to download the user's service subscription data.

Step 610. User Configuration Function The UPF entity returns the user's service subscription data to the user service registration function URF entity.

Step 611. User service registration function The URF entity queries the service registration function SRF entity for the service description signed by the user according to the home network service in the service subscription data.

Step 612. Service registration function The SRF entity queries the service description of the user service. If there are multiple service control function entities SCF providing the user service, the user service registration function URF entity allocates a service control function SCF entity to the service; the service registration function SRF entity returns the corresponding service description to the user service registration function URF. entity.

Step 613. User service registration function After the URF completes the service discovery of the home network service in the user subscription, the URF sends a request to the corresponding service control function SCF entity according to the service description data to notify the user of the service authentication information.

Step 614. Service control function After receiving the user service authentication information notification request, the SCF entity saves the user service authentication information, and then returns a response message.

Step 615. User service registration function After the URF entity completes the service authentication information notification of all the contracted services, the service description of all the contracted services is sent to the user through the response message.

Step 616. Proxy Control Function The PCF entity returns a response message to the UE. After receiving the response message, the UE saves the service description of the user subscription service locally.

In one embodiment, illustrated in Figure 6B, the service is an independent process based on the terminal request mode to the home network and assumes that the user has not authenticated. The specific processing steps of the service release are as follows: Step 621. The UE initiates a service release request to the user service registration function URF entity. please The request includes a service description of the user terminal service (including user terminal registration information, capability information, and service information, etc.).

Step 622. Proxy Control Function The PCF entity performs an access check on the request message, and then the routing message to the user service registration function URF entity.

Step 623. User service registration function The URF entity checks the user service status, and then requests the user authentication function UAF entity to download the user's authentication data.

Step 624. User Authentication Function The UAF entity returns the user's authentication data to the user service registration function URF entity.

Step 625. User service registration function The URF entity sends an authentication to the UE according to the user authentication data.

Step 626. Proxy Control Function The PCF entity returns an authentication response message to the UE.

Step 627. The UE calculates an authentication response according to the authentication message, and re-initiates a service publishing request to the user service registration function URF entity.

Step 628. Proxy Control Function The PCF entity performs an access check on the request message, and then the route message to the user service registration function URF entity.

Step 629. User Service Registration Function The URF entity receives the user request and checks the authentication response. If the authentication is passed, the user service registration function URF entity configures the function to the user. The UPF entity requests to download the user's service subscription data.

Step 630. User Configuration Function The UPF entity returns the user's service subscription data to the user service registration function URF entity.

Step 631. User service registration function The URF entity checks whether the user terminal service published by the user is in compliance with the contract, that is, the legality of the published service. If the check is passed, the service description of the user terminal service published by the user is saved locally, and then the response message is returned;

Step 632. Proxy Control Function The PCF entity returns a response message to the UE.

In one embodiment, shown in Figure 6C, the service discovery and delivery process is based on the home network. The terminal requests the discovery and release process of the mode, and combines the two processes of the service release and the discovery. The service control function SCF entity uses the manner of subscribing the service authentication information of the user to the user service registration function URF entity, and assumes that the user has not yet authenticated. right. The specific processing steps for business release and discovery are as follows:

Step 641. The UE initiates a service discovery request to the user service registration function URF entity, where the request includes a service description of the user terminal service (including user terminal registration information, capability information, service information, and the like).

Step 642. Proxy Control Function The PCF entity performs an access check on the request message, and then the route message to the user service registration function URF entity.

Step 643. User service registration function The URF entity checks the user service status, and then requests the user authentication function UAF entity to download the user's authentication data.

Step 644. User Authentication Function The UAF entity returns the user's authentication data to the user service registration function URF entity through the authentication data response message.

Step 645. User service registration function The URF entity sends an authentication to the UE according to the user authentication data.

Step 646. Proxy Control Function The PCF entity returns an authentication response message to the UE.

Step 647. The UE calculates an authentication response according to the authentication message, and re-initiates a service discovery request to the user service registration function URF entity, where the request includes the service description of the user terminal service.

Step 648. Proxy Control Function The PCF entity performs an access check on the request message, and then the route message to the user service registration function URF entity.

Step 649. User Service Registration Function The URF entity receives the user request and checks the authentication response. If the authentication is passed, the user service registration function URF entity configures the function to the user. The UPF entity requests to download the user's service subscription data.

Step 650. User Configuration Function The UPF entity returns the user's service subscription data to the user service registration function URF entity.

Step 651. User service registration function URF entity according to the home network in the service subscription data Network service, check whether the user terminal service published by the user is in compliance with the contract. If the check is passed, the service description of the user terminal service published by the user is saved locally, and then the service registration function is performed.

The SRF entity queries the service description of the user subscription.

Step 652. Service registration function The SRF entity queries the service description of the user service. If there are multiple service control function entities SCF providing the user service, the user service registration function URF entity allocates a service control function SCF entity to the service; the service registration function SRF entity returns the corresponding service description to the user service registration function URF. entity.

Step 653. User service registration function After the URF entity completes the service description query of the subscription service of all the home networks, the service description of all the contracted services is sent to the user through the response message.

Step 654. Proxy Control Function The PCF entity returns a response message to the UE. After receiving the response message, the UE saves the service description of the user subscription service locally.

In the flow shown in Figs. 6A, 6B, and 6C described above, if the user has authenticated, the processing step of the authentication is not performed.

In an embodiment shown in FIG. 6D, the service discovery is an independent process based on the terminal request mode to the visited network, and the service control function SCF entity uses the manner of subscribing the user's service authentication information to the user service registration function URF entity (when the service The control function SCF entity receives the user's first service binding request, and initiates a user service registration function URF entity subscription request). The specific processing steps for business discovery are as follows:

Step 661. The UE initiates a service discovery request to the visited network entity.

Step 662. Proxy Control Function The PCF entity performs an access check on the request message, determines that the user has registered, requests to discover the service of the visited network, and then routes the message to the user service registration function URF entity of the visited network.

Step 663. The user service registration function of the visited network checks the user service status, and then requests the user service registration function URF entity of the home network to subscribe to the visited network service data. Step 664. User service registration function of the home network The URF entity checks the registration status of the user, and then returns the visited network service data subscribed by the user to the user service registration function URF entity of the visited network.

Step 665. User service registration function of the visited network The URF entity queries the service registration function SRF entity of the visited network to query the service description of the user subscription according to the visited network service subscribed by the user.

Step 666. Service registration function The SRF entity queries the service description of the user service. If there are multiple service control function entities SCF providing the user service, the user service registration function URF entity allocates a service control function SCF entity to the service; the service registration function SRF entity returns the corresponding service description to the user service registration function URF. entity.

Step 667. User service registration function of the visited network After the URF completes the service discovery of the visited network service, the service description of the visited network service of all the contracted services is sent to the user through the response message according to the service description data.

Step 668. Proxy Control Function The PCF entity returns a response message to the UE. After receiving the response message, the UE saves the service description of the visited network service of the user subscription service locally.

For the scenario where the user registration process is controlled by the service application layer, the registration process of the user, the service discovery process of the home network, and the terminal release process may be unified. As shown in Figure 7, a specific example of the process is as follows:

Step 701. The UE initiates a registration request to the user service registration function URF entity according to the terminal capability information, the service information, and the user information. The request includes service discovery request information and service description information of the user terminal service.

Step 702. Proxy Control Function The PCF entity performs an access check on the request message, and then routes the request message to the user service registration function URF entity.

Step 703. The user service registration function URF entity checks the user registration status, determines that the user has not registered, and sends user and terminal information, an authentication algorithm, and the like to the user authentication function UAF entity, and queries the user authentication data. Step 704. The user authentication function UAF entity returns the authentication data corresponding to the user and the user terminal to the user service registration function URF entity.

Step 705. User service registration function The URF entity sends a response message according to the authentication data, and the message includes user authentication challenge information.

Step 706. Proxy Control Function The PCF entity returns an authentication challenge to the UE.

Step 751. The UE calculates an authentication response and re-initiates the registration request. The request includes service discovery request information and service description information of the user terminal service.

Step 752. Proxy Control Function The PCF entity performs an access check on the request message and then routes the message to the user service registration function URF entity.

Step 753. User service registration function The URF entity checks the authentication response. After the authentication is passed, the user registration status is updated, the user registration information is saved, and then the user configuration function UPF entity requests to download the user's service subscription data.

Step 754. User Configuration Function The UPF entity returns the user's service subscription data to the user service registration function URF entity.

Step 755. User service registration function The URF entity checks whether the user terminal service published by the user meets the contract according to the service contract data. If the check is passed, the service description of the user terminal service published by the user is saved locally, and then the service registration function SRF entity is queried for the service description of the home network service subscribed by the user.

Step 756. Service Registration Function The SRF entity queries the service description that provides the user service. If there are multiple service control function entities SCF providing the user service, the user service registration function URF entity allocates a service control function SCF entity to the service; the service registration function SRF entity returns the corresponding service description to the user service registration function URF. entity.

Step 757. User service registration function After the URF entity completes the service description query of all the subscribed home network services, and assigns a service control function SCF entity to the service contracted by the user, the service description of all the contracted services is sent to the user through the response message.

Step 758. The proxy control function PCF entity returns a response message to the UE. Received by the UE After the message is acknowledged, the service description of the user subscription service is saved locally.

In the embodiment shown in FIG. 8, for the user service flow, the UE initiates a service request according to the service location information in the service description, and the proxy control function PCF entity (or ICF) can forward the service request according to the service location information. An example of the user service processing flow is shown in FIG. 8: Step 801. The UE provides a service control function corresponding to the service according to the service description information.

The SCF entity initiates a service request.

Step 802. Proxy Control Function The PCF entity determines that it is a home network service and routes the roaming user request to the ICF of the home network.

Step 803. The ICF forwards to the corresponding service control function SCF entity according to the requested service location information (service control function SCF entity address) in the message. If the service control function SCF entity does not have user service authentication information locally, the service control function SCF entity subscribes the user's service authentication information (including the user's registration status and service authority information, etc.) to the user service registration function URF entity. User Service Registration Function The URF entity provides the user registration status and service subscription information to the service control function SCF entity.

Step 804. If the service control function SCF entity does not have the service subscription information of the user locally, the service control function SCF entity configures the function UPF entity to query the user service subscription data according to the service request.

Step 805. User Configuration Function The UPF entity returns user service subscription data.

Step 806. Service Control Function The SCF entity executes the service logic according to the service subscription data, and then returns a UE service response message.

Step 807. The ICF forwards the response message.

Step 808. Proxy Control Function The PCF entity forwards the response message.

Due to the policy such as network address hiding, the service description information obtained by the UE may not explicitly include the service providing location information. In this case, the proxy control function PCF entity (or ICF) can query the user service registration function URF entity to obtain the service location information (service control function SCF entity address) of the service according to the service identifier in the request message, and then forward the industry. Request. A specific implementation is shown in Figure 9:

Step 901: The UE initiates a service request to the network according to the service description information.

Step 902. Proxy Control Function The PCF entity determines that the home network service, and routes the roaming user request to the ICF of the home network.

Step 903. The ICF queries the user service registration function URF entity to query the service provision location information of the user corresponding service according to the service identifier in the request message.

Step 904. User service registration function The URF entity returns the service provision location information (service control function SCF entity address) of the corresponding service of the user.

Step 905. The ICF forwards to the corresponding service control function SCF entity processing.

In a user call service instance, the processing processes of the calling and called sides are respectively shown in FIG. 10, FIG. 11, and FIG. 12, and the process uses the SIP protocol as an example for interworking between call services between networks, and other protocols are related thereto. The same reason. Referring to Figure 10, the processing flow on the calling side is as follows:

Step 1001: The UE initiates a service request to the corresponding service control function SCF entity that provides the telephone service according to the service description information.

Step 1002. Proxy Control Function The PCF entity determines that it is a home network service and routes the roaming user request to the ICF of the home network.

Step 1003. The ICF forwards to the corresponding service control function SCF entity according to the requested service location information (service control function SCF entity address) in the message.

Step 1004. Service Control Function The SCF entity invokes the Interworking Service (IWF) according to the user subscription data.

Step 1005. After receiving the service request, the IWF sends a session request to the called network by using the SIP interface.

Step 1006. The called network returns a temporary response message 180.

Step 1007. The IWF returns a service temporary response message.

Step 1010. The service control function SCF entity returns a user temporary response message according to the business logic. Step 1011. The ICF forwards the temporary response message.

Step 1012. Proxy Control Function The PCF entity forwards the temporary response message.

Step 1013. The called network returns a session response message 200.

Step 1014. The IWF is called by the called network to send an ACK acknowledgement.

Step 1015. The IWF returns a service response message to the user side.

Step 1016. Service Control Function The SCF entity returns a UE response message.

Step 1017. The ICF forwards the response message.

Step 1018. Proxy Control Function The PCF entity forwards the response message.

Referring to Figure 11, the processing flow of the called user in the registration state is as follows:

Step 1101. The IWF receives a call request from the calling network.

Step 1102. The IWF queries the user service function. The URF entity queries the service description of the user's call service (service control function SCF entity address and service interface).

Step 1103. User service registration function The URF entity checks the user registration status and returns the call service description information according to the information of the user subscription service.

Step 1104. The IWF invokes the service control function SCF entity service according to the service description information.

Step 1105. Service Control Function The SCF entity processes the service and sends a service request to the user according to the user registration information (or the service description of the user terminal service).

Step 1106. The ICF forwards the service request message.

Step 1107. Proxy Control Function The PCF entity forwards the service request message.

Step 1108. The UE responds to the service request and sends a temporary response message.

Step 1109. Proxy Control Function The PCF entity forwards the temporary response message.

Step 1110. The ICF forwards the temporary response message.

Step 1111. Service Control Function The SCF entity sends a temporary response message to the IWF according to the service processing.

Step 1112. The IWF returns a temporary response message 180 to the calling network. Referring to FIG. 12, the processing flow in the unregistered state of the called user is as follows: Step 1201. The IWF receives a call request from the calling network.

Step 1202. The IWF queries the user service function. The URF entity queries the service description of the user's call service (service control function SCF entity address and service interface).

Step 1203. User service registration function The URF entity checks the user registration status, finds that the user is not registered, and configures the function UPF entity to query the subscription data in the unregistered state.

Step 1204. User Configuration Function The UPF entity returns the subscription data.

Step 1205. User service registration function The URF entity queries the service registration function SRF entity for the service description signed by the user according to the user subscription data.

Step 1206. Service registration function The SRF entity queries the service description of the user service. If there are multiple service control function entities SCF providing the user service, the user service registration function URF entity allocates a service control function SCF entity to the service; the service registration function SRF entity returns the corresponding service description to the user service registration function URF. entity.

Step 1207. User Service Registration Function After the URF entity completes the service discovery of the user subscription service, it returns the service description information to the IWF.

Step 1208. The IWF invokes the service of the service control function SCF entity according to the service description information.

Step 1209. Service Control Function The SCF entity processes the service and sends a response message.

Step 1210. The IWF returns a response message to the calling network.

Referring to FIG. 13, the service flow of the user terminal in this embodiment is as follows:

Step 1301. Service Control Function The SCF entity invokes the user terminal service according to the needs of the service. First, the user service registration function URF entity queries the user terminal service interface description.

Step 1302. User Service Registration Function The URF entity returns service description information.

Step 1303. The service control function SCF entity processes the service and sends a service request to the user. Step 1304. The ICF forwards the service request message. Step 1305. The proxy control function PCF entity forwards the service request message.

Step 1306. The UE answers the service request and sends a response message.

Step 1307. Proxy Control Function The PCF entity forwards the reply message.

Step 1308. The ICF forwards the response message.

The service-oriented communication system functional architecture in this embodiment can implement the integration of third-party services, including the call of a third-party service and a service-oriented communication system by a user to be invoked by a third-party service.

Referring to Figure 14, an example of calling a third-party service is as follows:

Step 1401. The third party initiates a service publishing request to publish the web service to the service gateway. Step 1402. The GWF proxy third party, and publishes the web service to the service registration function SRF entity.

Step 1403. Service Registration Function The SRF entity returns a service release response.

Step 1404. The GWF returns a service release response to the third party service network.

Step 1451. The UE initiates a service description and initiates a service request.

Step 1452. Proxy Control Function The PCF entity routes roaming user requests to the ICF of the home network.

Step 1453. The ICF forwards to the corresponding service control function SCF entity according to the requested service location information in the message.

Step 1454. Service Control Function The SCF entity invokes the Web service based on the user subscription data. First, the service registration function SRF entity is queried for the service description information of the calling service.

Step 1455. Service Registration Function The SRF entity returns service description information.

Step 1456. Service Control Function The SCF entity initiates a service call request to the GWF according to the service description information, and invokes the Web service.

Step 1457. After receiving the service call request, the GWF invokes the web service of the third-party service network.

Step 1458. The third party service returns a response message. Step 1459. The GWF returns a reply message.

Step 1480. Service Control Function The SCF entity returns a response message.

Step 1481. The ICF forwards the reply message.

Step 1482. Proxy Control Function The PCF entity forwards the reply message.

Referring to Figure 15, an implementation of a service in a service-oriented communication system that is invoked by a third-party service is as follows:

Step 1501. The IPTV ASF issues the service to the service registration server service registration function SRF entity.

Step 1502. Register the server service registration function SRF entity registration service, and then answer IPTV ASF ₀

Step 1503. The GWF queries the service registration function SRF entity for the IPTV service description according to the needs of the service release;

Step 1504. Service registration function The SRF entity returns an IPTV service description to the GWF. Step 1505. GWF publishes the business to the Service Registry of the third-party network.

Step 1506. The service agent of the third-party network returns a service release response.

Step 1551. The third-party network SP-AS queries the service registry (Service Registry) for the service description information of the IPTV service.

Step 1552. The Service Registry returns service description information.

Step 1553. The SP-AS initiates a service call request to the GWF according to the service description information. Step 1554. After receiving the service call request, the GWF invokes the IPTV service. Step 1555. The IPTV ASF returns a reply message.

Step 1556. The GWF returns a reply message.

The traditional user access terminal in this embodiment includes a SIP terminal, a POTS terminal, an ISDN terminal, and the like, and these terminals access the NGN network through the access control function ACF entity. Access control function ACF entity can be used by a single user, user group or representative of the entire device The user initiates registration. The single-user registration is the same as the previous process. For user group registration, when the access control function ACF entity initiates a registration request, the registration message includes the user group identifier. The user service registration function URF entity authenticates the user group. After the user authentication succeeds, the user service registration function URF entity downloads and saves all the user identifiers corresponding to the user group identifier from the subscription server user configuration function UPF entity. The user subscription data download in the user group uses the on-demand download mode, that is, when the user has the calling or called service, the user service registration function URF entity receives the service discovery request, if the check user has already registered, but there is no The subscription data, the user service registration function URF entity immediately requests downloading the user subscription data from the user configuration function UPF entity, and queries the service description information according to the user subscription data, and updates the third party service authentication information.

When the subsequent user group is re-registered, the user service registration function URF entity refreshes the registration status of the user group identity, and refreshes the registration status of all user identifiers corresponding to the user group identifier.

When the user group is logged out, the user service registration function unregisters the user group identifier, and the user group identifier corresponding to all user identifiers is deleted, and the service authentication information of the third party is updated.

After the user group is registered, the access control function ACF entity can publish the service to the user service registration function URF entity based on the user or the user group.

An implementation of user group registration is shown in Figure 16:

Step 1601. Access Control Function The ACF entity initiates a registration authentication request according to the request of the user equipment and the user group information.

Step 1602. User service registration function The URF entity checks the user group registration status. If the user group has not been registered, the user authentication function UAF entity queries the authentication data.

Step 1603. User authentication function The UAF entity returns the authentication data corresponding to the user group to the user service registration function URF entity, and the authentication data includes all user identifiers corresponding to the user group identifier.

Step 1604. The user service registration function URF entity initiates an authentication challenge to the user according to the authentication data. Step 1651. The access control function ACF entity calculates an authentication response and re-initiates the registration authentication request.

Step 1652. The user service registration function URF entity checks the authentication response. After the authentication is passed, the user group registration information is saved, and the user group identifier and all corresponding user identifiers are set to the registration state, and then the user service registration function URF entity sets the user. The registration information is returned to the access control function ACF entity.

After receiving the service initiated by the traditional user terminal, the access control function ACF entity checks whether there is a service description data of the user locally, and if so, directly uses the service description data of the user to initiate a service request; if there is no service description data, access The control function ACF entity initiates a service discovery request to the user service registration function URF entity. After receiving the request, the user service registration function checks whether the user has already registered. If not registered, the user service registration function URF entity returns a failure; if it is already registered, the user service registration function URF entity checks whether there is user service description data locally; if not, the user configuration function UPF entity queries the user subscription data, and then A request is initiated to the contracted ASF to update the third party's business authentication information. User Service Registration Function The URF entity obtains user service data from the service registration function SRF entity, and then returns the user service data to the access control function ACF entity. Access Control Function The ACF entity receives and stores the user's business data.

As shown in Figure 17, an example of the service flow of the calling user side of the traditional user terminal is as follows: Step 1701. The TE initiates a service request.

Step 1702. Access Control Function The ACF entity finds that there is no user service description data locally, and requests the user service registration function URF entity to download the user service description data.

Step 1703. User service registration function The URF entity checks that the user has registered, but has no service subscription data, and requests the user UPF entity to download the user service subscription data.

Step 1704. User Configuration Function The UPF entity returns user subscription data.

Step 1705. The user service registration function URF entity queries the service registration function SRF entity for the service description of the contract service according to the downloaded subscription data. Step 1706. The service registration function SRF entity returns a service description of the user subscription service. Step 1707. The user service registration function URF entity queries the service description of all the contracted services, and assigns a service control function SCF entity to the service subscribed by the user.

Step 1708. Access control function The ACF entity initiates a service request message according to the service description data.

Step 1709. Service Control Function The SCF entity returns a service response message.

Referring to FIG. 18, an example of a called user side service flow of a conventional user terminal is as follows: Step 1801. The IWF receives a call request from the calling network.

Step 1802. The IWF queries the user service registration function. The URF entity queries the service description of the user's call service (service control function SCF entity address and service interface).

Step 1803. User Service Registration Function The URF entity checks the user registration status and user subscription data. If it is registered and has subscription data, it directly returns the service description information.

Step 1804. The IWF invokes the service control function SCF entity service according to the service description information.

Step 1805. Service Control Function The SCF entity processes the service and sends a service request to the access control function ACF entity according to the user registration information.

Step 1806. Access Control Function The ACF entity processes the service request message and sends a response message.

Step 1807. Service Control Function The SCF entity sends a temporary response message to the IWF according to the service processing.

Step 1808. The IWF returns a temporary response message 180 to the calling network.

The web client is generally based on a browser, and can dynamically install the business engine on the client, operate local resources and control the client business process.

The processing flow of the Web client based on the business discovery/release process and the registration process is shown in Figure 19 (other ways are similar):

Step 1901. The web client is supported by the local service engine, according to the terminal capability letter. The information (indicating the terminal type is a Web terminal), the service information, and the user information, initiates a registration request to the user service registration function URF entity. The request includes service discovery request information and service description information of the user terminal.

Step 1902. Proxy Control Function The PCF entity performs an access check on the request message, and then routes the message to the user service registration function URF entity.

Step 1903. User service registration function The URF entity checks the user registration status. If the user has not registered, the user authentication function UAF entity sends user and terminal information, authentication algorithm and other information to query the user authentication data.

Step 1904. User Authentication Function The UAF entity returns the authentication data corresponding to the user and the terminal to the user service registration function URF entity.

Step 1905. User service registration function The URF entity sends a response message according to the authentication data, and the message includes user authentication challenge information.

Step 1906. Proxy Control Function The PCF entity returns an authentication challenge to the UE.

Step 1951. The web client local service engine calculates an authentication response and re-initiates the registration request.

Step 1952. Proxy Control Function The PCF entity performs an access check on the request message, and then routes the message to the user service registration function URF entity.

Step 1953. User service registration function The URF entity checks the authentication response. After the authentication is passed, the user registration status is updated, the user registration information and the service description information are saved, and then the user configuration function UPF entity requests to download the user's service subscription.

Step 1954. User Configuration Function The UPF entity returns the user's service subscription data to the user service registration function URF entity.

Step 1955. The user service registration function URF entity checks whether the user terminal service published by the user is in compliance with the subscription according to the service subscription data. If the check is passed, the service description of the user terminal service published by the user is saved locally, and then the service registration function SRF entity is queried for the service description signed by the user. Step 1956. The service registration function SRF entity queries the service description of the user service. If there are multiple service control function entities SCF providing the user service, the user service registration function URF entity allocates a service control function SCF entity to the service; the service registration function SRF entity returns the corresponding service description to the user service registration function URF. entity.

Step 1957. The user service registration function URF entity completes the service description query of all the contracted services, and allocates a service control function SCF entity for the service subscribed by the user; since the UE is a Web terminal, the user service registration function URF entity converts the service description data into The corresponding web page and control script, and then send the business description of all contracted services to the user through a reply message.

Step 1958. Proxy Control Function The PCF entity returns a response message to the UE. The UE displays the operation page of all the contracted services on the browser interface under the support of the Web client service engine.

Accessing the Web home page can be seen as a special kind of business, because its business description only needs to include the URL address of the Web server, and accessing the Web homepage is generally a business that visits the network. Referring to FIG. 20, an implementation of the business process of the Web terminal accessing the Web is as follows:

Step 2001. The web terminal initiates a service request to the web server through the client's service engine according to the operation of the user web page, and requests the service of the web server.

Step 2002. Proxy Control Function The PCF entity performs an access check on the request message, and then routes the message to the service control function SCF entity of the visited network.

Step 2003. Service Control Function The SCF entity checks user data, processes business logic, and initiates a service request to invoke a Web server.

Step 2004. The Web Server executes the business logic and returns the requested web page.

Step 2005. Service Control Function The SCF entity returns the result returned by the Web Server as a service request response.

Step 2006. The proxy control function PCF entity forwards the service response to the web client, and the web client parses the web page and displays it. In a practical application, the service-oriented communication system in the present embodiment can effectively combine different logical entities into physical network elements to form a physical architecture of the NGN network, thereby reducing the number of products and interfaces, optimizing charging, performance, and network. Redundant design. In the above NGN functional architecture, an example of the structure of the service-oriented communication system in this embodiment is shown in FIG. 21, where: an Access Control Server (ACS) 2100 includes an access control function ACF entity; The Proxy Control Server (PCS) 2101 includes a proxy control function PCF entity and an interworking control function ICF entity. The Service Control Server (SCS) 2102 may include one or more service control function SCF entities according to different services. A service function ASF entity is provided; a User Registry Server (URS) 2103 includes a user service registration function URF entity; a Service Registry Server (SRS) 2104 includes a service registration function SRF entity; and a home subscriber server (Home Subscriber Server) , HSS) 2105 includes a user authentication function UAF entity and a user configuration function UPF entity.

In the service-oriented communication system shown in Fig. 22, an example of the processing service is as follows: Step 2201. The user terminal UE initiates a service request to the corresponding service control server SCS providing the service according to the service description information.

Step 2202. Visiting the network's proxy control server The PCS determines the home network service and routes the roaming user request to the proxy control server PCS of the home network.

Step 2203. The proxy control server of the home network PCS forwards to the corresponding service control server SCS according to the requested service location information (SCS address) in the message. If the service control server SCS has no user registration status and service subscription information locally, the service control server SCS subscribes the user registration status and service subscription information to the user registration server URS; the user registration server URS provides the user registration status and service subscription information to the service control. Server SCS.

Step 2204. The service control server SCS sends the home subscriber server according to the service request.

The HSS queries the user service subscription data.

Step 2205. Home subscriber server The HSS returns user service subscription data.

Step 2206. The service control server SCS executes the service logic according to the service subscription data. The service is billed, and then the UE service response message is returned.

Step 2207. The proxy control server of the home network forwards the response message and charges the user service.

Step 2208. The proxy control server of the visited network forwards the response message and charges the user service.

The structure of a user service registration function entity in this embodiment is as shown in FIG. 23, and includes: a communication module 2300, an authentication module 2301, a service release module 2302, and a service discovery module 2303. The communication module 2300 is configured to receive or send a message; the authentication module 2301 acquires the authentication data of the user after receiving the registration request message of the user, and authenticates the user; the service publishing module 2302 records the user according to the received service publishing request. a service description information of the terminal service, and managing the user terminal service by using the user identifier as a management object; the service discovery module 2303, when receiving the user service discovery request, acquires the service description information subscribed by the user according to the user identification information in the request, and Returning the service description information to the user.

The structure of a service control function entity in this embodiment is as shown in FIG. 24, and includes a service discovery module 2400 and a service control module 2401. The service discovery module 2400 obtains corresponding service description data when receiving a service request. Based on the service description data, the 2401 invokes a service or invokes a module to combine services according to a control flow of a service control script.

The foregoing describes the implementation of the service in the service-oriented communication system by using the GSIP protocol as the service transmission protocol. Those skilled in the art can clearly understand that the other protocols implement the service in the service-oriented communication system of the embodiment according to the foregoing description. The processing flow, in which the protocol-related processing, the remaining processing flow is the same as the above process. The present invention not only enables a traditional operator-centric business model, but also supports a new business model that inherits the concept of the Internet global network and establishes a global business network.

(ie, connect the third-party networks above to form a global network), but at the edge of the global service network, deploy the operator's service control network to provide security and distribution control. The service that needs to be supervised by the telecommunication service is deployed inside the service control network, which is local; and the Internet-based service that does not depend on roaming and does not require supervision is deployed in the global service network. Therefore, the service in the operator-centric business model is limited to the operator network. There are problems.

The service-oriented communication system of the embodiment of the present invention can provide a more flexible service open mode and service combination mode based on SOA, including a flexible combination of NGN network visited network service, home network service, and third party service, and user terminal has creation , the ability to publish, discover, and combine businesses. Further, the general signaling transmission protocol GSTP can inherit the trustworthy, manageable, and billable network capabilities of existing telecommunication networks; the GSIP protocol can be used to integrate telecommunication services and Internet services.

Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is a better implementation. the way. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a readable storage medium, such as a floppy disk of a computer. A hard disk or optical disk, etc., includes instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present invention. The spirit and scope of the invention. Therefore, it is intended that the present invention cover the modifications and variations of the invention as claimed.

Claims

Claim

A service-oriented communication system, comprising:

An access control entity, configured to control user access to the network;

2. The service-oriented communication system of claim 1, wherein the communication system further comprises:

The user database is in communication with the user service registration function entity for providing and managing user service authentication data and user subscription data.

3. The service-oriented communication system of claim 1, wherein the communication system further comprises:

And a service entity, in communication with the service control function entity, configured to provide services under the control of the service control function entity.

4. The service-oriented communication system of claim 1, wherein the access control entity comprises:

a proxy control function entity for controlling a next generation network user access network;

An access control function entity, configured to control a traditional network user to access the network;

An edge control function entity is configured to control roaming users to access the home network.

5. The service oriented communication system of claim 2, wherein the user database comprises:

User configuration function entity, used to save and manage user service subscription data;

A user authentication function entity for storing and managing user authentication data and user service authentication data.

6. The service oriented communication system of claim 3, wherein said industry

37 Replacement page (Article 26) The entity includes at least one of the following entities:

An application service function entity for providing services to users, third parties, or business function entities within the network;

The service registration function entity is configured to provide a service publishing agent for the application service function entity, and provide a service discovery capability for the service control function entity, the application service function entity, and the user service registration function entity.

7. The service-oriented communication system of claim 6, wherein the application service function entity further comprises:

A gateway function entity for publishing internal services of a next-generation network to a third-party network, providing an access agent for accessing the next-generation network service by the third-party network, and publishing the service of the third-party network to the next-generation network, for the next-generation network Accessing third-party network services to provide access agents;

The network interworking function entity is used to provide interworking between the services of the next generation network and the services of the third party network.

The service-oriented communication system according to any one of claims 1 to 7, wherein the user service registration function entity comprises:

a service publishing module, configured to record service description information of the user terminal service according to the received service release request, and manage the user terminal service by using the user identifier as a management object;

The service-oriented communication system according to any one of claims 1 to 7, wherein the service control function entity comprises:

A service discovery module, configured to obtain a service description of a corresponding service when receiving a service request

38

Replacement page (Article 26) data;

The service control module is configured to invoke a service or invoke a module to combine services according to the service description data according to the control flow of the control script of the service.

The method for registering in a service-oriented communication system is characterized in that: the service-oriented communication system includes: an access control entity, configured to control a user access network; a user service registration function entity, and the connection The control entity and the service control function entity are connected to each other, and are used for publishing the service of the user terminal and discovering the service subscribed by the user; the service control function entity is in communication with the access control entity and the user service registration function entity, and is used for connecting The user entering the network provides the service subscribed by the user; the registration method includes:

The method according to claim 10, wherein the registration request includes service discovery request information;

After the user is authenticated, the user registration function further queries the service description information of the corresponding user terminal service according to the user information in the service discovery request information, and returns the service description information of the queried user terminal service to the user. The user service registration function entity manages the user terminal service by using the user identifier as a management object.

The method according to claim 10 or 11, wherein the registration request message further includes service description information of the user terminal service;

After the user passes the authentication, the user service registration function entity further records the service description information of the user terminal service, and manages the user terminal service by using the user identifier as a management object.

The method according to claim 12, wherein before the user service registration function entity records the user terminal service, the validity of the user publishing service is checked according to the subscription data of the user.

39 Replacement page (Article 26)

A method for distributing a user terminal service in a service-oriented communication system, wherein the service-oriented communication system comprises: an access control entity, configured to control a user access network; a user service registration function entity, and a The access control entity and the service control function entity are connected, and are used for publishing the service of the user terminal and discovering the service subscribed by the user; the service control function entity is connected with the access control entity and the user service registration function entity, and is used for The user who enters the network provides the service that the user subscribes to; the method for publishing the service of the user terminal includes:

The method according to claim 14, wherein before the user service registration function entity records the user terminal service, the validity of the user publishing service is checked according to the user's tea date data.

A method for discovering a user terminal service in a service-oriented communication system, wherein the service-oriented communication system comprises: an access control entity, configured to control a user access network; a user service registration function entity, and a The access control entity and the service control function entity are connected to each other, and are used for publishing the service of the user terminal and discovering the service subscribed by the user; the service control function entity is communicatively connected with the access control entity and the user service registration function entity, and is used for The user accessing the network is provided with the service subscribed by the user; the method for discovering the service of the user terminal includes:

17. The method according to claim 16, wherein the user service registration function

40

Replacement page (Article 26) After receiving the discovery request of the user terminal service, the entity can authenticate the initiator according to the network and/or the service control policy of the user.

A method for discovering a user subscription service in a service-oriented communication system, wherein the service-oriented communication system comprises: an access control entity, configured to control a user access network; a user service registration function entity, and a The access control entity and the service control function entity are connected to each other, and are used for publishing the service of the user terminal and discovering the service subscribed by the user; the service control function entity is communicatively connected with the access control entity and the user service registration function entity, and is used for The user accessing the network is provided with the service subscribed by the user; the method for discovering the subscription service of the user includes:

The method according to claim 18, wherein, after receiving the service discovery request, the access control entity determines that the service discovery request is a service for discovering a home network, and then forwards the request to the home. User service registration function entity of the network; or

After receiving the service discovery request, the access control entity determines that the service discovery request is a service for discovering the visited network, and then forwards the request to the user service registration function entity of the visited network.

The method according to claim 19, wherein the user service registration function entity of the home network queries the user database according to the user identification information in the request to obtain the service subscribed by the user, and then registers the function entity from the user service. The service control function entity or other user service registration function entity discovers the service description information subscribed by the user.

The method according to claim 19, wherein after receiving the user subscription service discovery request, the user service registration function entity of the visited network first requests the user service registration function entity of the home network to subscribe to the user. Visiting the network service, and then discovering the service description information of the visited network service from the local, service registration function entity or other user service registration function entity according to the visited network service subscribed by the user.

22. A method of binding a service in a service oriented communication system, characterized in that:

41 Replacement page (Article 26) The communication system to the service includes: an access control entity, configured to control a user access network; a user service registration function entity, in communication with the access control entity and the service control function entity, for publishing the service and discovery of the user terminal a service that is subscribed to by the user; a service control function entity, which is in communication with the access control entity and the user service registration function entity, and is configured to provide a service for the user accessing the network to subscribe to the service; the method for binding the service includes:

The target service control function entity provides a service to the user according to the service description information.

The method according to claim 22, wherein the access control entity determines, according to the service location information in the service request, a target service control function entity that processes the service request;

Alternatively, the access control entity queries the user service registration function entity to obtain service location information according to the service identifier in the service request, and determines a target service control function entity that processes the service request according to the service location information.

The method according to claim 22, wherein the method further comprises the step of: the service control function entity authenticating the user according to the service authentication information obtained from the user service registration function entity.

The method of claim 24, wherein the obtaining, by the service control function entity, the service authentication information from the user service registration function entity comprises:

After receiving the user service binding request, the service control function entity queries the user service registration function entity for service authentication information;

Or the user service registration function entity reports the service authentication information to the service control function entity after the user finds that the subscription service is completed;

Or the service control function entity subscribes to the user service registration function entity to subscribe to the user's business

42 Replacement page (Article 26) After the authentication information is obtained, the user service registration function entity notifies the service control function entity of the service authentication information.

The method according to claim 22, wherein the manner in which the target service control function entity provides services to the user according to the service description information includes one or any combination of the following:

The target service control function entity locally invokes a corresponding service;

The target service control function entity invokes a corresponding service from an application service function entity that provides a service;

The target service control function entity invokes a corresponding service from a third party network through a gateway function entity providing the service, and/or a network interworking function entity.

The method according to claim 22, wherein the method further comprises: the service control function entity triggering a user terminal service, and querying a user service registration function entity for a service description of the user terminal service;

The service control function entity sends a service binding request to the user equipment according to the service description of the user terminal service.

28. A communication device, comprising:

The service publishing module records the service description information of the user-terminal service according to the received service distribution request, and manages the user terminal service by using the user identifier as a management object;

29. A communication device, comprising:

The service discovery module is configured to obtain the service description data of the service when receiving the service request, and the service control module is configured to invoke the service or invoke the module to combine the services according to the service description data according to the control flow of the control script of the service.

43 Replacement page (Article 26)