WO2011009256A1

WO2011009256A1 - Distributed access gateway system

Info

Publication number: WO2011009256A1
Application number: PCT/CN2009/075312
Authority: WO
Inventors: 段先德
Original assignee: 中兴通讯股份有限公司
Priority date: 2009-07-21
Filing date: 2009-12-04
Publication date: 2011-01-27
Also published as: CN101965005A; WO2011009256A8; CN101965005B

Abstract

The present invention discloses a distributed access gateway system. The system includes: one or more access nodes, which are used to monitor and report the status information and event information of both the terminal devices and the resource channels; user/resource management unit, which is used to manage the user and resource corresponding to the one or more access nodes; node control unit, which is used to maintain the status information reported by the one or more access nodes, and perform data exchange with access nodes and/or service process unit respectively; service configuration unit, which is used to store the configuration information of the user and resource corresponding to the one or more access nodes; service process unit, which is used to process the event information from the node control unit and/or access protocol unit; access protocol unit, which is used to provide access protocol interface for the access gateway system. According to the solution provided by the present invention, the amount of media gateways can be reduced, and convenience is brought to the service management of the telecommunication operating management.

Description

Distributed Access Gateway System Technical Field

The present invention relates to access gateway technologies, and in particular, to a distributed access gateway system. Background technique

In a typical VoIP access system accessed through the H.248 protocol and/or the Media Gateway Control Protocol (MGCP), the Media Gateway (MG) is an IP network node. The user and media resources of Voice over Internet Protocol (VoIP) are used as part of the media gateway to access the core network softswitch system through the H.248 protocol and/or MGCP protocol provided by the media gateway.

Since the media gateway is responsible for the management and control of media resources and is responsible for user access, the media gateway can be regarded as an access gateway (AG, Access Gateway).

In the related art, for a media gateway system that tightly couples media management, control, and user access, as the capacity of the media gateway becomes more and more miniaturized, and the number of media gateways increases, the service network will A large number of media gateway nodes will appear. Therefore, it is inconvenient for the business management of telecommunications operations. Moreover, the media gateways are all customized embedded devices, and each media gateway needs to implement complex logic calculations such as access protocols and local service processing and configuration, and has high requirements on hardware configuration of media gateway devices, when the number of media gateways When the number is greatly increased, the cost of network construction will also increase greatly. Summary of the invention

The present invention has been made in view of the increasing number of media gateways in the related art, the inconvenience to the service management of telecommunication operations, and the high cost of network construction. To this end, the main object of the present invention is to provide an improved A distributed access gateway system to solve at least one of the above problems. According to the present invention, a distributed access gateway system is provided.

The distributed access gateway system includes: one or more access nodes, a user/resource management unit, a node control unit, a service configuration unit, a service processing unit, and an access protocol unit, where one or more access nodes, Connected with the terminal device, used for monitoring and reporting status information and event information of the terminal device, and status information and event information of the resource channel; the user/resource management unit is respectively connected to the node control unit and the service processing unit, and is used for Management of one or more access nodes corresponding to users and resources; a node control unit, connected to one or more access nodes and service processing units, for maintaining status information and events reported by one or more access nodes Information, and respectively interacting with the access node and/or the service processing unit; the service configuration unit is respectively connected to the node control unit and the service processing unit, and is configured to store corresponding users and resources of one or more access nodes Configuration information; business processing unit, with node control unit Then, the event information for the node from the control unit and / or access protocol unit performs processing; access protocol unit, connected with the service processing unit, for providing access to an access protocol interface gateway system. It should be noted here that the "status information" in the status information reported by the one or more access nodes refers to: status information of the access node. The "resource configuration information" in the configuration information of the user and resource corresponding to the one or more access nodes is different from the "resource channel state information", "resource configuration information" is static, and "resource channel" The status information" is dynamic.

Through the invention, multiple nodes distributed on the IP network are connected to the core network softswitch system through a unified access gateway and an access protocol, and the service for the telecommunication operation is solved with the increasing number of media gateways. The inconvenience of management and the high cost of network construction can reduce the number of media gateways, facilitate business management in telecom operation management, and deploy large-volume access transaction processing and resource management work. On a general-purpose computer or a distributed computing cluster, the performance requirements of the access node hardware devices are reduced, thereby effectively reducing the network construction cost.

Other features and advantages of the present invention will be set forth in the description which follows, and, in part, It will be apparent from the description or the description of the invention. The objectives and other advantages of the invention will be realized and attained by the <RTI DRAWINGS

The drawings described herein are intended to provide a further understanding of the present invention, and are intended to be a part of the present invention, and the description of the present invention is not intended to limit the invention. In the drawing:

1 is a block diagram of a distributed access gateway system according to an embodiment of the present invention;

2 is a structural block diagram of a distributed access gateway system according to an embodiment of the present invention; FIG. 3 is a structural block diagram of a distributed access gateway system according to a preferred embodiment of the present invention; FIG. 4 is an access according to an example 1 of the present invention. Flowchart of node online processing;

5 is a flowchart of user port event processing according to Example 2 of the present invention;

6 is a flowchart of resource allocation processing according to Example 3 of the present invention;

7 is a flow chart of resource return processing according to Example 4 of the present invention;

Figure 8 is a flow diagram of protocol transaction processing in accordance with Example 5 of the present invention. detailed description

The present invention provides a distributed access gateway system, which provides a problem of inconvenience to the service management of the telecommunication operation and a high cost of network construction, in view of the increasing number of media gateways in the related art. The method includes: one or more access nodes, a user/resource management unit, a node control unit, a service configuration unit, a service processing unit, and an access protocol unit, where one or more access nodes are connected to the terminal device, Monitoring and reporting status information and event information of the terminal device and status information and event information of the resource channel; the user/resource management unit is respectively connected to the node control unit and the service processing unit for managing one or more access nodes Corresponding users and resources; node control unit, with one or more access nodes and service offices The management unit is connected to maintain state information reported by one or more access nodes, and performs data interaction with the access node and/or the service processing unit respectively; the service configuration unit is separately associated with the node control unit and the service processing single phase a connection, configured to store configuration information of a user and a resource corresponding to one or more access nodes; a service processing unit, respectively connected to the node control unit, for accessing the node control unit and/or the access protocol unit The event information is processed; the access protocol unit is connected to the service processing unit and is configured to provide an access protocol interface for the access gateway system. According to the embodiment of the invention, the access protocol and the local service processing and configuration are deployed to the lower cost access gateway, and the access gateway can use a general-purpose computer or a low-cost computing cluster to reduce the access node. The hardware configuration requirements of the device can effectively reduce the cost of network construction. The general purpose computer can be a personal computer (PC) or a small work station (Work Station).

It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. The invention will be described in detail below with reference to the drawings in conjunction with the embodiments.

The present invention provides a distributed access gateway system. In order to better understand the technical solution of the present invention, the architecture of the distributed access gateway system will first be described in conjunction with FIG. The above system includes but is not limited to a VoIP access gateway system. 1 is a block diagram of a distributed VoIP access gateway system in accordance with an embodiment of the present invention. As shown in FIG. 1, a distributed access gateway system according to an embodiment of the present invention mainly includes the following components:

1, access node 10 - lx

The voice user's terminal is connected to the access node 10 _ lx (representing X access nodes) through a telephone cable, and the access node 10 - lx provides, but is not limited to, ringing, playback, button detection, and calling number information identification. And the CID (Calling Identity Delivery) display, media stream and other resources provide signal services for the call setup process of the user of the access node, and provide the media stream service for the user after the call is established. Access nodes 10 - lx provide control interfaces for users and resources. If there is a relatively complex time slot switching network inside the access node, the internal time slot from the resource to the user and/or from the user to the resource should also be completed. Among them, for the button detection, including: Detection of DTMF (Dual-tone Multifrequency) signals or pulse signals. When the access node 10 - lx goes online, it is required to report the status of all users and resources of the node to the distributed node control unit, so as to perform service control on the users on the access nodes 10 - lx, and on the access node Resources are managed and operated.

The basic configuration information of the user port and resources on the access nodes 10 - lx can be held locally or obtained from the service configuration unit. When the access node needs to be obtained from the service configuration unit, the access node should be able to receive some port attribute configuration information about the user of the node issued by the node control unit, where the information includes but is not limited to port gain, ringing mode, initial Ringing settings, etc. When the access node is online, it should also receive the channel basic attribute configuration information of the media resource issued by the node control unit, where the information includes but is not limited to echo suppression, fax mode configuration, and the like.

The access nodes 10 - lx are also responsible for the observation and reporting of user port events and resource channel events on the access node. User port events include, but are not limited to, user off-hook, on-hook, hook hook, button, and the like. Resource channel events include, but are not limited to, channel failures, media stream QoS reports, and more. After the access node 10 - lx observes the user port event and the resource channel event, it reports it to the corresponding unit for processing.

2, node control unit 20

The node control unit is responsible for maintaining state information of all access nodes of the distributed VoIP access gateway system. When the access node 10 - lx goes online, it needs to send an online request message to the node control unit, and report the status of all users and resources on the access node. After the access node 10 - lx goes online, the node control unit supervises the state of the node in real time. If the status of the access node changes (for example, offline), the relevant unit is notified to perform processing.

The node control unit is also responsible for communicating with all access nodes of the distributed VoIP access gateway system, including issuing control commands for users and/or resources to all access nodes, and receiving user ports and/or all user ports reported by the access nodes. Resource channel event. Release users and / to all access nodes The control command of the resource or the resource includes: (1) releasing basic configuration information of the user and the resource to the access node 10 - lx according to the configuration in the service configuration unit 40; (2) indicating the service processing unit to the user of the access node 10 - lx Or the resource releases a control command. After receiving the user port and/or resource channel event of >3⁄4 on the access node 10 - lx, the node control unit forwards the relevant unit for processing.

3. User / Resource Management Unit 30

The user/resource management unit 30 is responsible for the management of resources under all access nodes of the distributed VoIP access gateway system, including but not limited to ringing, playback, button detection (DTMF or pulse), CID display, media stream. And other resources.

When the access node 10 - lx goes online, it reports all user and resource information under the access node. All resource information is ultimately sent to the user/resource management unit 30 for registration. Each user and resource in the distributed VoIP access gateway system has a unique identifier for unified management. When the user/resource management unit 30 registers the resource, it needs to record the available range, function, and identifier of the resource.

During the progress of the user voice service, resources are required to serve the user, and the user/resource management unit 30 will allocate necessary resources to the user as needed. Once the resource is assigned to the user, the resource management unit will record the occupancy information of the resource. When the user's required service is completed, the occupied resources are returned to the user/resource management unit 30.

4. Business Configuration Unit 40

The service configuration unit 40 is responsible for maintaining basic configuration information of all users and resources of the distributed VoIP access gateway system. The basic configuration information of the user includes, but is not limited to, user port attribute configuration, user local special service configuration, and other information. The basic configuration information of the resource includes, but is not limited to, the channel basic attribute configuration of the resource, and the resource allocation policy configuration.

5, business processing unit 50

The service processing unit 50 is responsible for implementing the processing flow of the voice service of all users of the distributed VoIP access gateway system according to the service status of the user/resource. Business processing unit 50 holds this The service state machine of all users of the distributed VoIP access gateway system responds to user port events and protocol transactions according to the current service state. The business processing unit 50 also responds to an abnormal event. Abnormal events include, but are not limited to, timer timeouts, user port exceptions, and the like.

The service processing unit 50 is also responsible for providing number analysis and other logical computing services for all users of the distributed VoIP access gateway system.

6, access protocol unit 60

The access protocol unit 60 is responsible for providing a unified access protocol interface to the core network softswitch system for the distributed VoIP access gateway system. The access protocol interface refers to the H.248 protocol and/or the MGCP protocol. The distributed VoIP access gateway system only acts as an access gateway on the service network view of the core network.

The access protocol unit 60 maintains a protocol connection with the softswitch system and interacts with the H.248 protocol and/or the MGCP protocol signaling of the softswitch system.

The access protocol unit 60 receives the signaling packet of the softswitch, parses it into a protocol transaction, finds a corresponding service entity according to the protocol entity, and hands it to the service processing unit 50 for processing. A protocol entity refers to an endpoint, context, etc. in the H.248 protocol and/or the MGCP protocol. The service entity refers to the user identifier, resource identifier, and session identifier of the distributed VoIP access gateway system.

Access protocol unit 60 also receives user events and protocol transaction execution responses reported by service processing unit 50. After receiving the appropriate user port event in the appropriate user service state, the service processing unit 50 reports the event to the access protocol unit 60. The access protocol unit 60 finds the corresponding protocol entity according to the service entity, and associates the user port event as a protocol entity. The transaction is reported to the softswitch system. After performing the protocol transaction issued by the access protocol unit 60, the service processing unit 50 also reports the execution result to the access protocol unit 60. The access protocol unit 60 finds the corresponding protocol entity according to the service entity, and responds to the protocol transaction. Report to the softswitch system.

The various components shown in Figure 1, the units 10 - lx are the access nodes distributed on the IP network, and the units 20 - 60 are the parts required for the distributed VoIP access service, the above parts It can run on a single node in the IP network, or it can be distributed on multiple nodes of the IP network, but it is not distributed on the same node as the above-mentioned access nodes.

In the distributed access gateway system provided by the present invention, each access node and the unit for access processing and local service configuration are distributed on different IP network nodes. The above IP network node or node refers to a network element with an independent IP on the IP network.

2 is a structural block diagram of a distributed access gateway system according to an embodiment of the present invention. 3 is a block diagram showing the structure of a distributed access gateway system in accordance with a preferred embodiment of the present invention. As shown in FIG. 2, a distributed access gateway system according to an embodiment of the present invention includes: one or more access nodes 10-lx, a node control unit 20, a user/resource management unit 30, a service configuration unit 40, and a service processing. Unit 50, and access protocol unit 60, are described below in connection with FIG.

(1) One or more access nodes 10-lx, which may be one or more, connected to the terminal device, for monitoring and reporting status information and event information of the terminal device, and status information and event information of the resource channel.

Preferably, the access nodes 10 - lx may be embedded devices with independent IPs distributed on the IP network, and the VoIP user terminals may be connected through a telephone line, and have various resources necessary for calling services, including VoIP media channels. Resources. Resource management, user service configuration and processing, and access protocol processing are not implemented on the access nodes 10 - lx. All users and resources on the access node are managed by the relevant modules of the distributed VoIP access gateway system. The service configuration and service processing and access protocols of all users on the access node are implemented by related modules on other nodes.

Preferably, when the access node 10 - lx goes online, the node control module 20 sends a node online request, and after the request is passed, reports all user and resource information of the access node. See Figure 4 for details.

Example one

4 is a flow chart of an access node online processing according to an example 1 of the present invention. As shown in Figure 4, The access node uplink processing according to the first embodiment of the present invention includes the following steps (step S401 - step S409):

Step S401: The node control module 20 listens to an online request of an access node. Query the node configuration information to determine whether the request is from a legitimate access node. If not, step S403 is performed, and if so, step S405 is performed.

The node configuration information includes a configuration item of a identifiable characteristic of a legal access node.

Step S403: Discarding the online request of the access node, and rejecting the online call.

Step S405: Send a query request of the node user/resource information to the access node, and wait for the access node to return a response. If the inquiry response is received within the specified time, step S407 is performed, otherwise, step S403 is performed.

Step S407: The node control unit 20 sends the queried user/resource information of the access node to the user/resource management unit 30, and the user/resource management unit 30 saves the information. After the processing is complete, query the node configuration information or query the access node to determine whether the configuration of the user port attribute/media channel attribute needs to be released. If not, the online processing is completed; if yes, step S409 is performed.

Step S409: Query the service configuration unit 40 for the configuration information of the user port attribute/media channel attribute of the newly-online access node, and release the configuration information to the access node. The process ends.

Preferably, after the access nodes 10 - lx go online, the status of the user port event and the VoIP media channel resource are scanned and reported to the node control unit 20, and then processed by the node control unit 20 to the relevant module. The access nodes 10 - lx also provide control interfaces for user ports and resources within the nodes, and the node control unit 20 operates the user ports and resources through the control interfaces described above.

(2) The node control unit 20 is connected to one or more access nodes and service processing units for maintaining state information reported by one or more access nodes, and respectively associated with the access node and/or the service processing unit. Perform data interaction;

Preferably, as shown in FIG. 3, the node control unit 20 includes: a monitoring module 200, and a first sending The sending module 202, the first receiving module 204, wherein the monitoring module 200 is configured to monitor status information of one or more access nodes in real time; the first sending module 202 is configured to send the user to one or more access nodes. And/or a control command of the resource, and/or, sending the event information to the service processing unit; the first receiving module 204 is configured to receive event information of the terminal device and the resource channel reported by the one or more access nodes, and/or Receive operational commands from the business processing unit.

Preferably, the node control unit 20 can communicate with the access nodes 10 - lx, and the node control unit 20 receives the online request of the access nodes 10 - lx and supervises the status of the access nodes 10 - lx. The node control unit 20 receives the user port event and the streaming channel event of the online access node, and uniformly issues control commands to the users and resources of the online access node. See Figure 5 for details.

Example two

5 is a flow chart of user port event processing in accordance with Example 2 of the present invention. As shown in FIG. 5, the user port event processing according to the second embodiment of the present invention includes the following steps (step S501 - step S509):

Step S501: The access node 10 - lx observes the user port event and sends it to the node control unit 20.

The user port event includes information such as user location information and event ID. Step S503: Query the user/resource management unit 30 for the identifier of the user according to the location information of the user of the reported user port event, and send the user event ID and the user identifier to the service processing unit 50 for processing. After receiving the user port event, the service processing unit determines whether the received event is a normal event that can be processed according to the current service status of the user: if yes, step S505 is performed; if not, the user event is discarded, and the processing flow is End.

Step S505: The service processing unit 50 performs corresponding service processing to perform user service state transition. If the local resource needs to be used for the user, the resource allocation request is sent to the user/resource management module, and the response processing is performed according to the request result. After the service is processed, the user event is sent to the access protocol unit 60 if necessary. The access protocol unit 60 performs step S507. Step S507: The access protocol unit 60 queries the correspondence table between the service entity and the protocol entity, finds the protocol entity identifier corresponding to the user identifier, and converts the user event into a protocol event description.

Preferably, the above query may be implemented by looking up a comparison table, or by a certain rule conversion. For example, the user ID is "{0,0,1 } " and the corresponding protocol entity ID is "USER000001".

Step S509: Packet the protocol entity identifier and the protocol event description into a protocol packet, and send the packet to the core network softswitch system. The process ends.

(3) a user/resource management unit 30, which is respectively connected to the node control unit and the service processing unit, and is configured to manage users and resources corresponding to one or more access nodes;

Preferably, as shown in FIG. 3, the user/resource management unit 30 includes: a storage module 300, configured to store resource information and/or resource occupation information corresponding to one or more access nodes; and a resource allocation module 302, configured to: The terminal device and the resource channel are allocated corresponding resources according to a predetermined policy. The resource returning module 304 is configured to cancel the resource occupation information corresponding to the one or more access nodes, and restore the idle state of the resource.

User/Resource Management Unit 30 records all online users and available resources. For each user and resource, information such as its identity, location, etc. is recorded. For each resource, information such as its identity, location, function, and available range is recorded. The user/resource management unit 30 provides the node control unit 20 with a query from the location of the user or resource to the identity, and a query service from the identity to the location.

Preferably, the user/resource management unit 30 receives the resource allocation request of the service processing unit 50 to allocate resources to the user. Resource allocation request, including user ID, service category, and other information. The service category is an indication of what type of service is being allocated for the resource. The user/resource management unit 30 queries a resource that is currently idle and can provide the service of the category according to the user identifier and the service category information, allocates the resource to the user, and records the occupancy of the user/resource. When a user is queried for a plurality of resources that are currently idle and can provide services of the category, a resource allocation policy may be employed, and the resource allocation policy is configurable. Service processing unit when the allocated resource is serviced by the user 50 will send a resource return message to the user/resource management unit 30, and the user/resource management unit 30 will log out the user/resource occupation record and restore the idle state of the resource. For details on the process of resource allocation and return, see Figure 6 and Figure 7.

Example three

6 is a flow chart of resource allocation processing according to Example 3 of the present invention. As shown in FIG. 6, the resource allocation process according to Example 3 of the present invention includes the following steps (step S601 - step S611): Step S601: The user/resource management unit 30 receives the resource allocation request of the service processing unit 50.

The resource allocation request includes, but is not limited to, a user identifier, a service category, and the like. The above service category is information that allocates resources for what type of service to perform.

Step S603: The user/resource management unit 30 searches for a resource allocation policy to find a currently assigned resource allocation policy. The resource allocation policy determines the manner in which a resource is selected. For example, the idle resource may be selected in turn, or the multi-function resource that the user is using may be preferentially selected. A multi-functional resource is a resource that can perform multiple services at the same time. To maintain system flexibility, users can configure appropriate resource allocation policies.

Step S605: The user/resource management unit 30 searches the resource status table according to the current resource allocation policy to check whether there is a resource that can complete the requested service. If not, a "resource allocation failed" message is returned to the service processing unit 50, and the process ends; if yes, step S607 is performed.

Step S607: The user/resource management unit 30 modifies the selected resource status in the resource status table to be "occupied".

Step S609: The user/resource management unit 30 records a user/resource occupation information of the currently allocated resource in the user/resource occupation table. User/resource occupation information, including user ID, resource ID, service category, and other information.

Step S611: The user/resource management unit 30 returns the resource identification of the allocated resource to the service processing unit 50. The process ends. Example four

7 is a flow chart of resource return processing according to Example 4 of the present invention. As shown in Fig. 7, the resource return processing according to the fourth embodiment of the present invention includes the following steps (step S701 - step S707):

Step S701: The user/resource management unit 30 receives the resource return message of the service processing unit 50.

The foregoing resource return message includes but is not limited to information such as a user identifier and a resource identifier. Step S703: The user/resource management unit 30 queries the user/resource occupation table to check whether the user is using more than one service at the same time. If yes, step S707 is performed, and if no, step S705 is performed.

Step S705: The user/resource management unit 30 sets the state information of the resource in the resource status table to "idle".

Step S707: The user/resource management unit 30 cancels the record of the user, the resource, and the service category in the user/resource occupation table. The process ends.

(4) The service configuration unit 40 is respectively connected to the node control unit and the service processing unit, and is configured to store configuration information of the user and the resource corresponding to the one or more access nodes;

Preferably, the service configuration unit 40 stores the necessary basic configuration information of the local user and the resource. If the access node needs to perform basic attribute setting on the user port or the resource channel after the online node is online, the service configuration unit 40 can provide such information. The service configuration unit 40 also stores other information related to the user's service, and information such as the configuration of the resource allocation policy, for the relevant unit to query during the user's business operation.

(5) a service processing unit 50, which is respectively connected to the node control unit, and configured to process event information from the node control unit and/or the access protocol unit;

Preferably, as shown in FIG. 3, the service processing unit 50 includes: a second receiving module 500, a processing module 502, and a second sending module 504. The second receiving module 500 is configured to receive user event information reported by the node control unit, and/or receive a protocol from the access protocol unit. The transaction module 502 is configured to process user event information and/or protocol transaction information. The second sending module 504 is configured to send a user and resource operation command to the node control module, and/or to the access protocol unit. Send the processing result.

Preferably, the foregoing second sending module 504 is further configured to send a resource allocation request or a resource return message to the user/resource management unit;

Preferably, the service processing unit 50 is further configured to provide a number analysis and a reconciliation operation for the access gateway system.

In a specific implementation process, the business processing unit 50 also performs processing of exception logic and related logic operations in the business process. The exception logic specifies the timeout or the processing of the exception event. Correlation logic operation refers to processing that requires a large amount of calculation, such as number analysis.

In a specific implementation process, the service processing unit 50 implements the processing of the user's call service, maintains the call service state machine of the user, and responds to all events that generate and affect the user's service. During the operation of the user's call service, the service processing unit interacts with all other units: receives the user port event reported by the node control unit 20, and issues a user and resource operation instruction to the node control unit 20; to the user/resource management unit 30, sending a resource allocation request and a resource return message, and performing corresponding processing on the result of the request; querying the service configuration unit 40 for the personalized configuration of the user service process; receiving the protocol transaction indication of the access protocol unit 60, processing and forwarding The incoming protocol unit 60 returns the result of the protocol transaction and reports the user event to the access protocol unit 60.

(6) An access protocol unit 60, connected to the service processing unit 50, for providing an access protocol interface for the access gateway system.

Preferably, as shown in FIG. 3, the foregoing access protocol unit 60 includes: a third receiving module 600, a parsing module 602, a searching module 604, and a third sending module 606, wherein the third receiving module 600 is configured to receive from the third receiving module 600. The access gateway system needs to access the signaling message of the system, and receives the processing result from the service processing unit >3⁄4; the parsing module 602 is configured to parse the signaling message into a protocol a search module 604, configured to search for a corresponding service entity according to the protocol entity, or search for a corresponding protocol entity according to the service entity; a third sending module 606, configured to send the service entity to the service processing unit for processing, and process The result is sent to the system that the access gateway system needs to access.

In a specific implementation process, the access protocol unit 60 may provide a unified access protocol interface for the distributed VoIP access gateway system to the core network softswitch system. The above access protocol interfaces include, but are not limited to, H.248 and/or MGCP protocols. The access protocol unit 60 interacts with the core network softswitch system for protocol packets. The access protocol unit 60 implements mutual conversion between the protocol transaction and the internal business operation, and realizes mutual conversion between the protocol entity and the internal business entity. A protocol entity refers to an endpoint, context, etc. in the H.248 protocol and/or the MGCP protocol. The service entity refers to the user identifier, resource identifier, and session identifier of the distributed VoIP access gateway system.

The access protocol unit 60 parses the protocol transaction indication of the core network softswitch into an internal service operation and sends it to the service processing unit 50 for processing. The access protocol unit 60 also packages the result of the protocol transaction and the user event into a protocol, and sends it to the core network softswitch system to complete the access of the user VoIP service. See Figure 8 for details.

Example five

Figure 8 is a flow diagram of protocol transaction processing in accordance with Example 5 of the present invention. As shown in FIG. 8, the protocol transaction according to the fifth embodiment of the present invention includes the following steps (step S801 - step S813): Step S801: The access protocol unit 60 receives the protocol signaling packet of the core network softswitch system, and the packet It carries transactions that need to be processed by the media gateway.

Step S803: The access protocol unit 60 parses out the protocol entity identifier in the signaling message and the transaction to be processed. The protocol entity identifier refers to the context ID or / and the endpoint ID in the H.248 protocol or the MGCP protocol.

Step S805: The access protocol unit 60 queries the correspondence table between the service entity and the protocol entity, finds the service entity identifier corresponding to the protocol entity identifier, and converts the protocol transaction into an internal service instruction. Step S807: The access protocol unit 60 sends the service entity identifier and the internal service command to the service processing unit 50.

Step S809: The service processing unit 50 executes the service instruction, and returns the execution result to the access protocol unit 60. In the process of executing the service instruction by the service processing unit 50, perhaps involving the process of using the local resource, the service processing unit 50 sends a resource allocation request to the user/resource management unit 30 to allocate the resources necessary for executing the service instruction, after the resource is used. A message of resource return is sent to the user/resource management unit 30.

Step S811: After receiving the result of the execution of the service instruction of the service processing unit 50, the access protocol unit 60 converts the execution result into a protocol transaction response event, and queries the correspondence table between the service entity and the protocol entity to find the protocol entity corresponding to the service entity. .

Step S813: The access protocol unit 60 packages the protocol transaction response event and the protocol entity into a protocol packet, and sends the packet to the core network softswitch system through the signaling connection. The process ends.

The distributed access gateway system provided by the present invention includes, but is not limited to, a VoIP access gateway system, and the system that the distributed access gateway system needs to access is not limited to the core network softswitch system.

Through the foregoing example one to the fifth embodiment, the distributed access gateway system provides multiple nodes distributed on the IP network to the core network softswitch system through a unified access gateway and access protocol, which can be conveniently docked. The ingress node performs service management and can effectively reduce the hardware configuration requirements of the media gateway.

In summary, the distributed access gateway system provided by the above embodiments of the present invention completes the decomposition of each link in the VoIP access processing process to a distributed IP network node, thereby increasing system flexibility. Enables one access gateway to access VoIP services of multiple access nodes, reduces the number of access gateways in the service network, and transfers a large amount of processing from the access node device to the distributed network device, reducing the docking The requirements for hardware configuration of the ingress node simplify the management of the service network and reduce the cost of network construction.

It will be apparent to those skilled in the art that the various modules or steps of the invention described above are apparent. It can be implemented by a general-purpose computing device, which can be centralized on a single computing device or distributed over a network of multiple computing devices. Alternatively, they can be implemented by program code executable by the computing device. They may be stored in a storage device by a computing device, or they may be fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof may be implemented as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.

The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. within the spirit and scope of the invention are intended to be included within the scope of the invention.

Claims

Claim

A distributed access gateway system, the system further comprising:

One or more access nodes, connected to the terminal device, for monitoring and reporting status information and event information of the terminal device, and status information and event information of the resource channel;

a user/resource management unit, which is respectively connected to the node control unit and the service processing unit, for managing users and resources corresponding to the one or more access nodes;

a node control unit, connected to the one or more access nodes and the service processing unit, for maintaining status information and event information reported by the one or more access nodes, and respectively performing the access The node and/or the service processing unit perform data interaction;

a service configuration unit, which is respectively connected to the node control unit and the service processing unit, and configured to store configuration information of a user and a resource corresponding to the one or more access nodes;

a service processing unit, coupled to the node control unit, for processing event information from the node control unit and/or the access protocol unit;

An access protocol unit, coupled to the service processing unit, is configured to provide an access protocol interface for the access network relationship.

The system according to claim 1, wherein the node control unit comprises: a monitoring module, configured to monitor status information and event information of the one or more access nodes in real time;

a first sending module, configured to send a control command of a user and/or a resource to the one or more access nodes, and/or send the event information to the service processing unit;

The first receiving module is configured to receive the event information of the terminal device and the resource channel reported by the one or more access nodes, and/or receive an operation command from the service processing unit.

The system according to claim 1, wherein the user/resource management unit comprises: a storage module, configured to store resource information and/or resource occupation information corresponding to the one or more access nodes;

a resource allocation module, configured to allocate corresponding resources to the terminal device and the resource channel according to a predetermined policy;

And a resource returning module, configured to cancel the resource occupation information corresponding to the one or more access nodes, and restore the state of the resource to an idle state.

The system according to claim 1, wherein the service processing unit comprises: a second receiving module, configured to receive user event information reported by the node control unit, and/or receive from the connection Protocol transaction information into the protocol unit;

a processing module, configured to process the user event information and/or the protocol transaction information; a second sending module, configured to send a user and resource operation command to the node control unit, and/or to the access The protocol unit sends the processing result of the processing module.

The system according to claim 4, wherein the second transmitting module further

The system according to claim 5, wherein the service processing unit is further configured to provide number analysis and/or logic operations for the access gateway system.

The system according to claim 1, wherein the access protocol unit comprises: a third receiving module, configured to receive a signaling message from a system that the access gateway system needs to access, And/or receiving processing results reported from the service processing unit;

a parsing module, configured to parse the signaling "3" into a protocol transaction;

a searching module, configured to search for a corresponding service entity according to the protocol entity, and/or, to find a corresponding protocol entity according to the service entity;

And a third sending module, configured to send the service entity to the service processing unit for processing, and/or send the processing result to a system that the access gateway system needs to access.