WO2016165673A1 - Jslee容器系统，处理方法及网络融合的系统 - Google Patents

Jslee容器系统，处理方法及网络融合的系统 Download PDF

Info

Publication number
WO2016165673A1
WO2016165673A1 PCT/CN2016/080389 CN2016080389W WO2016165673A1 WO 2016165673 A1 WO2016165673 A1 WO 2016165673A1 CN 2016080389 W CN2016080389 W CN 2016080389W WO 2016165673 A1 WO2016165673 A1 WO 2016165673A1
Authority
WO
WIPO (PCT)
Prior art keywords
management
jslee
service
container
event
Prior art date
Application number
PCT/CN2016/080389
Other languages
English (en)
French (fr)
Inventor
梅君君
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2016165673A1 publication Critical patent/WO2016165673A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/10—Access point devices adapted for operation in multiple networks, e.g. multi-mode access points
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q3/00—Selecting arrangements
    • H04Q3/0016—Arrangements providing connection between exchanges
    • H04Q3/0029—Provisions for intelligent networking
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/541—Interprogram communication via adapters, e.g. between incompatible applications
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/54—Indexing scheme relating to G06F9/54
    • G06F2209/544—Remote

Definitions

  • the present application relates to, but is not limited to, the field of communications, and in particular, a JSLEE container system, a processing method, and a network fusion system.
  • FIG. 1 is a schematic diagram of the NGIN closed architecture in the related art. As shown in Figure 1, the NGIN solution of different manufacturers is still a vertical chimney architecture for telecom operators. Businesses developed based on different NGIN vendors cannot be run in another vendor's NGIN system. Different vendors' NGINs have their own independent management systems. The NGIN network between vendors cannot be integrated. Therefore, the private and closed nature of NGIN in the internal architecture is not conducive to the development and deployment of innovative services, and the communication industry is rapidly moving forward.
  • the network architecture cannot well realize the integration of communication schemes of different equipment vendors, and there is no effective solution at present.
  • This paper provides a JSLEE container system, processing method and network convergence system to at least solve the problem that the network architecture in the related technology can not achieve the integration of communication schemes of different equipment vendors.
  • An embodiment of the present invention provides a Java Application Programming Interface Service Logic Execution Environment (JSLEE) container system of an intelligent network, which includes components: a resource adapter, a service, and a router;
  • JSLEE Java Application Programming Interface Service Logic Execution Environment
  • the resource adapter is configured to: interface with an external network resource by a standard protocol, or encapsulate the action of the external network resource into an event accessing the inside of the JSLEE container system by using a JSLEE standard;
  • the router is configured to: find the service that processes the event according to the received event, and invoke the method for the service to process the event.
  • the JSLEE container system further includes a tool set, the tool set is configured to: provide a common tool for the JSLEE container system, the tool set includes at least one of the following: a timer, a tracking tool, and an alarm tool.
  • the JSLEE container system further includes a common core function module, where the common core function module is configured to: establish a context of the JSLEE container system, where the common core function includes at least one of the following: a thread pool, a cache , transaction mechanism.
  • the JSLEE container system further includes a management server, where the management server is configured to: use a Java management extension JMX to register the management function of the JSLEE container system into the MBean server in a manner of managing the component MBean;
  • the management function registered in the management server includes at least one of the following: container management, resource adapter management, service management, installation management, alarm management, and tracking management;
  • the container management includes at least one of: starting a container, stopping the container, and viewing the status of the container;
  • the resource adapter management includes at least one of: creating a resource adapter entity, deleting a resource adapter entity, activating a resource adapter entity, deactivating a resource adapter entity, and updating a resource Configuration of the adapter entity;
  • the service management includes at least one of: activating a service, deactivating a service, viewing a service status, and configuring service management data;
  • the installation management includes at least one of the following: installation of components, uninstallation of components;
  • the alarm management includes at least one of the following: querying an alarm, and clearing an alarm;
  • the tracking management includes setting a tracking level.
  • An embodiment of the present invention further provides a processing method of a JSLEE container system, including:
  • the resource adapter of the JSLEE container system receives the information of the external network, encapsulates the information into a first event accessing the inside of the JSLEE container system by the JSLEE standard, and notifies the first event to the router of the JSLEE container system;
  • the router routes the received first event, finds a service that processes the first event, and invokes a service processing function of the service to process the first event to generate a second event;
  • the method further includes:
  • the service or the resource adapter uses a tool set, and the tool set includes at least one of the following: a timer, a tracking tool, and an alarm tool.
  • the method further includes:
  • the management server of the JSLEE container system performs a registered management function, and the management function includes at least one of the following: container management, resource adapter management, service management, installation management, alarm management, and tracking management;
  • the container management includes at least one of: starting a container, stopping the container, and viewing the status of the container;
  • the resource adapter management includes at least one of: creating a resource adapter entity, deleting a resource adapter entity, activating a resource adapter entity, deactivating a resource adapter entity, and updating a configuration of the resource adapter entity;
  • the service management includes at least one of: activating a service, deactivating a service, viewing a service status, and configuring service management data;
  • the installation management includes at least one of the following: installation of components, uninstallation of components;
  • the alarm management includes at least one of the following: querying an alarm, and clearing an alarm;
  • the tracking management includes setting a tracking level.
  • the embodiment of the invention further provides a computer readable storage medium storing computer executable instructions, the method for processing the JSLEE container system being implemented when the computer executable instructions are executed.
  • the embodiment of the invention further provides a network convergence system, comprising: an external network resource system, a JSLEE container system, and an external management system;
  • the JSLEE container system interfaces with the external network resource by a standard protocol, or encapsulates the action of the external network resource into an event accessing the inside of the JSLEE container system by using a JSLEE standard;
  • the external management system interacts with the JSLEE container system through the Java Management Extension JMX mode to implement configuration and management of functions of the JSLEE container system.
  • the JSLEE container system includes components: a resource adapter, a router, a service, a tool set, a common core function module, and a management server;
  • the router is configured to: route the received event, find the service that processes the event, and invoke the method for processing the event by the service;
  • the tool set is configured to: provide a common tool for the JSLEE container system
  • the common core function module is configured to: establish a context of the JSLEE container system
  • the management server is configured to: use the Java management extension JMX to register the management function of the JSLEE container system into the MBean server in a manner of managing the component MBean.
  • the external network resource system includes at least one of the following:
  • next-generation NGN network IP multimedia subsystem IMS network
  • fixed network global mobile communication system GSM network
  • code division multiple access CDMA network service switching point SSP service switching point database
  • online charging system OCS SMS center
  • MMS center MMS center.
  • the embodiment of the present invention provides a Java application programming interface business logic execution environment JSLEE container system of an intelligent network, including components: a resource adapter, a service, and a router, and the resource adapter is configured to: interface with an external network resource by using a standard protocol. Or, according to the JSLEE standard The action of the external network resource is encapsulated into an event accessing the inside of the JSLEE container system, the router is configured to: route the received event, find the service that handles the event, and invoke the method of the service to process the event, thereby It solves the problem that the network architecture can not realize the integration of communication schemes of different equipment manufacturers, and realizes the fusion of communication schemes of different equipment manufacturers.
  • FIG. 1 is a schematic diagram of a closed architecture of an NGIN in the related art
  • FIG. 2 is a block diagram showing the structure of a JSLEE container system according to an embodiment of the present invention
  • FIG. 3 is a block diagram showing the structure of a JSLEE container system according to another embodiment of the present invention.
  • FIG. 4 is a block diagram showing the structure of a JSLEE container system according to another embodiment of the present invention.
  • FIG. 5 is a structural block diagram of a JSLEE container system according to another embodiment of the present invention.
  • FIG. 6 is a flow chart of a processing method of a JSLEE container system according to an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of an open architecture and system for implementing a converged network based on JSLEE technology according to an alternative embodiment of the present invention.
  • FIG. 8 is a schematic diagram of system interaction by taking a SIP call flow as an example according to an alternative embodiment of the present invention.
  • FIG. 2 is a structural block diagram of a JSLEE container system according to an embodiment of the present invention, as shown in FIG. 2
  • the JSLEE container system 20 includes components: a resource adapter 22, a service 24, and a router 26;
  • the resource adapter 22 is configured to: join together with an external network resource by a standard protocol, or encapsulate the action of the external network resource by the JSLEE standard into an event accessing the inside of the JSLEE container system;
  • the router 26 is arranged to find the service 24 that handles the event based on the received event and invoke the service 24 to process the event.
  • FIG. 3 is a structural block diagram of a JSLEE container system according to another embodiment of the present invention.
  • the JSLEE container system 20 may further include a tool set 32, which may be set.
  • the tool set 32 can include at least one of the following: a timer, a tracking tool, and an alarm tool.
  • FIG. 4 is a structural block diagram of a JSLEE container system according to another embodiment of the present invention.
  • the JSLEE container system 20 may further include a common core function module 42 having the common core function.
  • the module 42 can be configured to: establish a context of the JSLEE container system, the common core function 42 comprising at least one of: a thread pool, a cache, a transaction mechanism.
  • FIG. 5 is a structural block diagram of a JSLEE container system according to another embodiment of the present invention.
  • the JSLEE container system 20 may further include a management server 52.
  • the management server 52 Can be set to: use Java management extension JMX will register the management function of the JSLEE container system to the MBean server in the way of managing the component MBean;
  • the management function registered in the management server 52 may include at least one of the following: container management, resource adapter management, service management, installation management, alarm management, and tracking management;
  • the container management can include at least one of: starting a container, stopping the container, and viewing the status of the container;
  • the resource adapter management may include at least one of: creating a resource adapter entity, deleting a resource adapter entity, activating a resource adapter entity, deactivating a resource adapter entity, and updating a configuration of the resource adapter entity;
  • the service management may include at least one of: activating a service, activating a service, viewing a service status, and configuring service management data;
  • the installation management may include at least one of the following: installation of components, uninstallation of components;
  • the alarm management may include at least one of the following: querying an alarm, and clearing an alarm;
  • the tracking management can include: setting a tracking level.
  • FIG. 6 is a flowchart of a processing method of a JSLEE container system according to an embodiment of the present invention. As shown in FIG. 6, the method includes the following steps. :
  • Step S602 the resource adapter of the JSLEE container system receives the information of the external network, encapsulates the information into the first event to access the inside of the JSLEE container system by the JSLEE standard, and notifies the first event to the router of the JSLEE container system;
  • Step S604 the router routes the received first event, finds a service that processes the first event, and invokes a service processing function of the service to process the first event to generate a second event;
  • Step S606 the second event is notified to the router, or the service invokes the resource adapter to send the second event to the external network by standard protocol signaling.
  • the service or the resource adapter may use a tool set, and the tool set may include at least one of the following: a timer, a tracking tool, and an alarm tool.
  • the method may further include:
  • the management server of the JSLEE container system performs a registration management function, and the management function includes at least one of the following: container management, resource adapter management, service management, installation management, alarm management, and tracking management;
  • the container management can include at least one of: starting a container, stopping the container, and viewing the status of the container;
  • the resource adapter management may include at least one of: creating a resource adapter entity, deleting a resource adapter entity, activating a resource adapter entity, deactivating a resource adapter entity, and updating a configuration of the resource adapter entity;
  • the service management may include at least one of: activating a service, activating a service, viewing a service status, and configuring service management data;
  • the installation management may include at least one of the following: installation of components, uninstallation of components;
  • the alarm management may include at least one of the following: querying an alarm, and clearing an alarm;
  • the tracking management can include: setting a tracking level.
  • the embodiment of the invention further provides a computer readable storage medium storing computer executable instructions, the method for processing the JSLEE container system being implemented when the computer executable instructions are executed.
  • a network convergence system including: an external network resource system, a JSLEE container system, and an external management system;
  • the JSLEE container system is joined to the external network resource by a standard protocol, or encapsulates the action of the external network resource into an event accessing the inside of the JSLEE container system by using the JSLEE standard;
  • the external management system interacts with the JSLEE container system through the Java Management Extension JMX method to implement configuration and management of the functions of the JSLEE container system.
  • the JSLEE container system may include components: a resource adapter, a router, a service, a tool set, a common core function module, and a management server;
  • the router can be configured to: route the received event, find the service that handles the event, and invoke the method of processing the event by the service;
  • the toolset can be set to: provide a common tool for the JSLEE container system;
  • the common core function module can be set to: establish a context of the JSLEE container system
  • the management server can be configured to: use the Java management extension JMX to register the management function of the JSLEE container system into the MBean server in the manner of managing the component MBean.
  • the external network resource system may include at least one of the following:
  • next-generation NGN network IP multimedia subsystem IMS network
  • fixed network global mobile communication system GSM network
  • code division multiple access CDMA network service switching point SSP service switching point database
  • online charging system OCS SMS center
  • MMS center MMS center.
  • Signaling System 7 by the embodiment of the present invention (Signaling System 7, Short for the SS7), Next Generation Network (NGN) or IP (Internet Protocol) Multimedia Subsystem (IMS) telecommunications network
  • Next Generation Network NTN
  • IP Internet Protocol
  • IMS Internet Protocol Multimedia Subsystem
  • JAIN JAVA application programming interface of the intelligent network
  • SEE Service Logic Execution Environment
  • the architecture and system based on JSLEE technology proposed by the embodiments of the present invention can truly realize the fusion of communication schemes of different equipment manufacturers and realize the integration of information communication technology (ICT).
  • ICT information communication technology
  • the external network system represents various network resources, such as the Internet/NGN/IMS network, the Global System of Mobile communication (GSM) network/Code Division Multiple Access (CDMA). Network Service Switching Point (SSP), database, Online Charging System (OCS), SMS/MMS center, etc., interact with JSLEE system through their standard protocols/interfaces. .
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • SSP Network Service Switching Point
  • OCS Online Charging System
  • SMS/MMS center etc.
  • the JSLEE container system can be implemented based on the JSLEE standard.
  • the Resource Adapter (RA) can be configured to interface with external network resources by standard protocols, and encapsulate the actions of external network resources into events by JSLEE standard.
  • the router can be set to access the JSLEE container.
  • the toolset can be set to: provide some common tools, such as timer function, tracking function, Alarm function; public core function module can be set to: implement some underlying core functions, such as thread pool, cache, transaction mechanism, etc.; management server can be set to: use Java Management Extensions (JMX) technology, Various management functions are registered in the MBean Server (MBean Server) in the form of MBeans (Managed Beans).
  • JMX Java Management Extensions
  • the external management system can be an operation management part of the JSLEE system, and can interact with the MBeans in the JSLEE container through the JMX method to implement configuration and management of the specific functions of the JSLEE system.
  • JSLEE can be a container of components, resource adapters, services can be standard components, installed in the container; routers, toolsets, public core function modules, management server can be built-in modules of the container; external network can be standard The protocol accesses the JSLEE container through the resource adapter; the external management client and the alarm tracking client can be set to: communicate with the management server through the JMX access JSLEE container, and complete various configuration management functions.
  • the tool set can provide some standard tools such as timers, tracking, alarm tools, etc. for services, resource adapters, etc.; common core function modules can implement the underlying functions of the JSLEE container, such as thread pool, cache, transaction, etc.
  • the context in which the component runs in the container; the router can be the core of the JSLEE container and is responsible for routing the event that the resource adapter encapsulates to the container to the business responsible for handling the event.
  • the management server can be an MBean server provided by the JSLEE container, and various management modules can be registered in the MBean Server in the form of MBeans.
  • Container management mainly provides management functions for JSLEE containers, such as starting/stopping containers, viewing container status, etc.
  • Resource adapter management can mainly provide such as creating/deleting/activating/deactivating specific resource adapter entities and updating a specific resource. Functions such as configuration of the adapter entity; service management can provide functions such as activating/deactivating services, viewing service status, and configuring service management data; installation management can mainly provide installation/uninstallation functions for components; alarm management can be mainly provided as an inquiry. / Clear alarms and other functions; tracking management can mainly provide functions such as setting the tracking level.
  • the resource adapter can be a standard component, which can be logically divided into two parts, one is a protocol stack layer that communicates with the external network using a standard protocol, and the other part is that the actions generated by the external network received by the protocol stack are encapsulated into JSLEE standards.
  • the event is an adaptation layer that communicates with the JSLEE container.
  • Multiple vendors can provide their own protocol stack layers, but the adaptation layer and open protocol interfaces for JSLEE containers can be standard, ensuring container independence and portability of resource adapters from different vendors.
  • the protocol stack layer of the resource adapter can receive standard protocol signaling, and the adaptation layer can encapsulate the protocol message into an event programming interface (Application Programming Interface).
  • the interface notifies the router of the container; the router can find the service that handles the event according to the routing rule, and invokes the business logic processing function API2; when the business logic processes, the event can be generated and notified to the container of the container through the API 3 interface.
  • the API 4 interface of the resource adapter can also be called and sent to the external network by standard protocol signaling; the service or resource adapter can use the tool set through the API 7 interface (Note: There are multiple specific APIs in the API 7 interface, such as sending / Clear the alarm API, tracking API, timer API, etc.; the timer in the tool set can notify the router of the timer event through the API 6 interface; the management server can perform specific management functions through the API 5 interface (Note: API 5 There may be multiple specific APIs in the port, such as start/stop container API, create/delete/activate/deactivate resource adapter entity API, activate/deactivate services, etc., ie each management function may have a corresponding API).
  • the business logic running environment based on the JSLEE technology can be a component container, the resource adapter and the service can be standardized components, and the standard API interface can be used.
  • the standard component and the SLEE can be portable. To access new external network resources, you only need to install and deploy the corresponding resource adapters, which is extremely scalable.
  • the built-in toolset and common core functions of the container can undo the development of common tools and complex contexts by business developers.
  • the business development is independent of the SLEE container and the resource adapter shields the underlying protocol, the business developer can concentrate on developing the business logic itself and launch new business more quickly; the externally manageable interface standard can facilitate the implementation of unified management.
  • This architecture makes the closed ecosystem of the protocol adapter, SLEE and external management system provided by the same manufacturer under the NGIN architecture broken.
  • the JSLEE container and various resource adapters can be provided by the operators themselves or different vendors, independent of the SLEE development business. .
  • This all-round open architecture creates an ecological chain that is conducive to telecom operators to choose and combine solutions from multiple vendors. It is easy to connect Internet protocols to JSLEE containers by using corresponding resource adapters. Converged and innovative business for ICT.
  • FIG. 8 is a schematic diagram of system interaction in an example of a SIP call flow according to an alternative embodiment of the present invention. As shown in FIG. 8, the system interaction may include the following steps.
  • Step S802 the NGN/IMS core network sends a SIP (Session Initiation Protocol) INVITE request to the SIP RA;
  • SIP Session Initiation Protocol
  • Step S804 the SIP RA finds that the INVITE is a new INVITE outside the dialog, and newly creates an active object internally, and calls the startActivity() method to notify the container that a new session is generated, and the container generates a corresponding new session object;
  • Step S806 the SIP RA encapsulates the INVITE message into an invite event, and calls the fireEvent() method to notify the container of the event;
  • Step S808 the router of the container finds the service for processing the invoke event according to the routing rule, and invokes the OnINVITE() method implemented by the service to perform the service logic processing;
  • Step S810 the service invokes the SendResponse() method of the SIP RA to return a response of 100;
  • Step S812 the SIP RA encodes the method call of the service into standard SIP signaling, and returns a 100 Trying response to the NGN/IMS core network.
  • Step S814 the service invokes the SendResponse() method of the SIP RA to return a 180 response.
  • Step S816 the SIP RA encodes the method call of the service into standard SIP signaling, and returns a 180Ring response to the NGN/IMS core network.
  • Step S818, the service invokes the SendResponse() method of the SIP RA to return a response of 200;
  • Step S820 the SIP RA encodes the method call of the service into standard SIP signaling, and returns a 200Ring response to the NGN/IMS core network.
  • Step S822 the NGN/IMS core network sends an ACK to the SIP RA;
  • Step S824 the SIP RA encapsulates the ACK (response) message into an ack event, and calls the fireEvent() method to notify the container of the event;
  • Step S826 the router of the container finds the service for processing the ack event according to the routing rule, and invokes the OnACK() method implemented by the service to perform the service logic processing;
  • Step S830 the SIP RA encapsulates the BYE message into a bye event, and calls the fireEvent() method to notify the container of the event;
  • Step S832 the router of the container finds the service for processing the bye event according to the routing rule, and invokes the OnBYE() method implemented by the service to perform business logic processing;
  • Step S834 the service invokes the SendResponse() method of the SIP RA to return a 200 response to the BYE message;
  • Step S836 the SIP RA encodes the method call of the service into standard SIP signaling, and returns a 200 BYE response to the NGN/IMS core network.
  • all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve.
  • the devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.
  • the device/function module/functional unit in the above embodiment When the device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium.
  • the above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
  • the embodiment of the present invention provides a Java application programming interface business logic execution environment JSLEE container system of an intelligent network, including components: a resource adapter, a service, and a router, and the resource adapter is configured to: interface with an external network resource by using a standard protocol.
  • the action of the external network resource generated by the JSLEE standard is encapsulated into an event accessing the inside of the JSLEE container system, and the router is configured to: route the received event, find the service that handles the event, and invoke the service.
  • the method of processing the event solves the problem that the network architecture cannot implement the convergence of communication schemes of different equipment vendors well, and realizes the fusion of communication schemes of different equipment vendors.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephonic Communication Services (AREA)

Abstract

一种智能网的Java应用编程接口业务逻辑执行环境JSLEE容器系统包括组件：资源适配器，业务以及路由器，该资源适配器设置为：以标准协议与外部网络资源对接，或者，以JSLEE标准将该外部网络资源发生的动作封装成事件接入该JSLEE容器系统的内部，该路由器设置为：根据接收到的事件找到处理该事件的所述业务，并调用该业务处理该事件的方法。

Description

JSLEE容器系统，处理方法及网络融合的系统 技术领域
本申请涉及但不限于通信领域，尤其一种JSLEE容器系统，处理方法及网络融合的系统。
背景技术
智能网(Intelligent Network，简称为IN)的发展经历了从传统IN到下一代智能网(Next Generation Intelligent Network，简称为NGIN)的演进。传统IN将呼叫交换功能与业务控制功能相分离，加快了新业务的开发和部署，为电信运营商赢得了市场并带来了丰厚的利润。但是随着网络技术的发展，不同网络采用不同的底层智能网协议，传统IN的垂直烟囱式架构以及基于业务开发环境(Service Creation Enviroment，简称为SCE)的业务开发方式，已无法满足用户对融合业务特征的多样化需求，增加了运营商的总拥有成本(Total Cost of Ownership，简称为TCO)，NGIN的网络融合、业务能力开放等特性解决了传统IN面临的问题。
但是，NGIN架构内部是一个封闭的黑盒，图1是相关技术中NGIN封闭架构示意图，如图1所示，不同厂商的NGIN解决方案，对电信运营商而言仍旧是垂直的烟囱式架构。基于不同NGIN厂商开发的业务无法在另一个厂商的NGIN系统中运行、不同厂商的NGIN有各自独立的管理系统，厂商之间的NGIN网络是不能融合的。因此，NGIN在内部架构上的私有性、封闭性，不利于创新业务的开发、部署，束缚通信行业快速向前发展。同时，随着4G网络和移动互联网技术的发展，尽管电信运营商加大了对基础网络设施的投资建设，但是信息技术(Information Technology，简称为IT)领域正在蚕食通信技术(Communication Technology，简称为CT)领域，使得电信运营商面临增量不增收的局面。
针对相关技术中，网络构架不能很好地实现不同设备厂商通信方案的融合的问题，目前还没有有效的解决方案。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本文提供了一种JSLEE容器系统，处理方法及网络融合的系统，以至少解决相关技术中网络构架不能很好地实现不同设备厂商通信方案的融合的问题。
本发明实施例提供了一种智能网的Java应用编程接口业务逻辑执行环境(JSLEE)容器系统，其包括组件：资源适配器，业务以及路由器；
所述资源适配器设置为：以标准协议与外部网络资源对接，或者，以JSLEE标准将所述外部网络资源发生的动作封装成事件接入所述JSLEE容器系统的内部；
所述路由器设置为：根据接收到的事件找到处理所述事件的所述业务，并调用所述业务处理所述事件的方法。
可选地，所述JSLEE容器系统还包括工具集，所述工具集设置为：为所述JSLEE容器系统提供公共工具，所述工具集包括以下至少之一：定时器，跟踪工具，告警工具。
可选地，所述JSLEE容器系统还包括公共核心功能模块，所述公共核心功能模块设置为：建立所述JSLEE容器系统的上下文环境，所述公共核心功能包括以下至少之一：线程池、缓存、事务机制。
可选地，所述JSLEE容器系统还包括管理服务端，所述管理服务端设置为：使用Java管理扩展JMX将对所述JSLEE容器系统的管理功能以管理构件Mbean的方式注册到MBean服务器中；
所述管理服务端中注册的管理功能包括以下至少之一：容器管理，资源适配器管理，业务管理，安装管理，告警管理，跟踪管理；
所述容器管理包括以下至少之一：启动容器，停止容器，查看容器状态；
所述资源适配器管理包括以下至少之一：创建资源适配器实体，删除资源适配器实体，激活资源适配器实体，去激活资源适配器实体，更新资源适 配器实体的配置；
所述业务管理包括以下至少之一：激活业务，去激活业务，查看业务状态，配置业务管理数据；
所述安装管理包括以下至少之一：组件的安装，组件的卸载；
所述告警管理包括以下至少之一：查询告警，清除告警；
所述跟踪管理包括：设置跟踪级别。
本发明实施例还提供了一种JSLEE容器系统的处理方法，包括：
JSLEE容器系统的资源适配器接收外部网络的信息，以JSLEE标准将所述信息封装成第一事件接入所述JSLEE容器系统的内部，将所述第一事件通知到所述JSLEE容器系统的路由器；
所述路由器将接收的所述第一事件进行路由，找到处理所述第一事件的业务，并调用所述业务的业务处理函数处理所述第一事件产生第二事件；
将所述第二事件通知所述路由器，或者，所述业务调用所述资源适配器将所述第二事件以标准协议信令发送给外部网络。
可选地，所述方法还包括：
所述业务或者所述资源适配器使用工具集，所述工具集包括以下至少之一：定时器，跟踪工具，告警工具。
可选地，所述方法还包括：
所述JSLEE容器系统的管理服务端执行注册的管理功能，所述管理功能包括以下至少之一：容器管理，资源适配器管理，业务管理，安装管理，告警管理，跟踪管理；
所述容器管理包括以下至少之一：启动容器，停止容器，查看容器状态；
所述资源适配器管理包括以下至少之一：创建资源适配器实体，删除资源适配器实体，激活资源适配器实体，去激活资源适配器实体，更新资源适配器实体的配置；
所述业务管理包括以下至少之一：激活业务，去激活业务，查看业务状态，配置业务管理数据；
所述安装管理包括以下至少之一：组件的安装，组件的卸载；
所述告警管理包括以下至少之一：查询告警，清除告警；
所述跟踪管理包括：设置跟踪级别。
本发明实施例还提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被执行时实现上述JSLEE容器系统的处理方法。
本发明实施例还提供了一种网络融合的系统，包括：外部网络资源系统、JSLEE容器系统、以及外部管理系统；
所述JSLEE容器系统以标准协议与所述外部网络资源对接，或者，以JSLEE标准将所述外部网络资源发生的动作封装成事件接入所述JSLEE容器系统的内部；
所述外部管理系统通过Java管理扩展JMX方式与所述JSLEE容器系统中交互，实现对所述JSLEE容器系统的功能的配置和管理。
可选地，所述JSLEE容器系统包括组件：资源适配器，路由器，业务，工具集，公共核心功能模块，以及管理服务端；
所述路由器设置为：将接收到的事件进行路由，找到处理所述事件的所述业务，并调用所述业务处理所述事件的方法；
所述工具集设置为：为所述JSLEE容器系统提供公共工具；
所述公共核心功能模块设置为：建立所述JSLEE容器系统的上下文环境；
所述管理服务端设置为：使用Java管理扩展JMX将对所述JSLEE容器系统的管理功能以管理构件Mbean的方式注册到MBean服务器中。
可选地，外部网络资源系统包括以下至少之一：
互联网，下一代NGN网络，IP多媒体子系统IMS网络，固网，全球移通讯系统GSM网，码分多址CDMA网的业务交换点SSP业务交换点、数据库、在线计费系统OCS、短信中心，彩信中心。
通过本发明实施例，提供了一种智能网的Java应用编程接口业务逻辑执行环境JSLEE容器系统，包括组件：资源适配器，业务以及路由器，该资源适配器设置为：以标准协议与外部网络资源对接，或者，以JSLEE标准将该 外部网络资源发生的动作封装成事件接入该JSLEE容器系统的内部，该路由器设置为：将接收到的事件进行路由，找到处理该事件的该业务，并调用该业务处理该事件的方法，从而解决了网络构架不能很好实现不同设备厂商通信方案的融合的问题，实现了不同设备厂商通信方案的融合。
在阅读并理解了附图和详细描述后，可以明白其他方面。
附图概述
图1是相关技术中NGIN封闭架构示意图；
图2是根据本发明实施例的一种JSLEE容器系统的结构框图；
图3是根据本发明另一实施例的一种JSLEE容器系统的结构框图；
图4是根据本发明另一实施例的一种JSLEE容器系统的结构框图；
图5是根据本发明另一实施例的一种JSLEE容器系统的结构框图；
图6是根据本发明实施例的一种JSLEE容器系统的处理方法的流程图；
图7是根据本发明可选实施例的一种基于JSLEE技术实现融合网络的开放架构与系统示意图；
图8是根据本发明可选实施例的一种以SIP呼叫流程为例的系统交互示意图。
本发明的较佳实施方式
下面结合附图对本发明的实施方式进行描述。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的各种方式可以相互组合。
需要说明的是，本申请的说明书和权利要求书的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
在本发明的一个实施例中，提供了一种智能网的Java应用编程接口业务逻辑执行环境JSLEE容器系统，图2是根据本发明实施例的一种JSLEE容器系统的结构框图，如图2所示，JSLEE容器系统20包括组件：资源适配器22，业务24以及路由器26；
该资源适配器22设置为：以标准协议与外部网络资源对接(join together)，或者，以JSLEE标准将该外部网络资源发生的动作封装成事件接入该JSLEE容器系统的内部；
该路由器26设置为：根据接收到的事件找到处理该事件的该业务24，并调用该业务24处理该事件的方法。
通过上述JSLEE容器系统20，解决了网络构架不能很好实现不同设备厂商通信方案的融合的问题，实现了不同设备厂商通信方案的融合。
在本实施例中，图3是根据本发明另一实施例的一种JSLEE容器系统的结构框图，如图3所示，该JSLEE容器系统20还可包括工具集32，该工具集32可以设置为：为该JSLEE容器系统20提供公共工具，该工具集32可包括以下至少之一：定时器，跟踪工具，告警工具。
在本实施例中，图4是根据本发明另一实施例的一种JSLEE容器系统的结构框图，如图4所示，该JSLEE容器系统20还可包括公共核心功能模块42，该公共核心功能模块42可设置为：建立该JSLEE容器系统的上下文环境，该公共核心功能42包括以下至少之一：线程池、缓存、事务机制。
在本实施例中，图5是根据本发明另一实施例的一种JSLEE容器系统的结构框图，如图5所示，该JSLEE容器系统20还可包括管理服务端52，该管理服务端52可设置为：使用Java管理扩展JMX将对该JSLEE容器系统的管理功能以管理构件Mbean的方式注册到MBean服务器中；
该管理服务端52中注册的管理功能可包括以下至少之一：容器管理，资源适配器管理，业务管理，安装管理，告警管理，跟踪管理；
该容器管理可包括以下至少之一：启动容器，停止容器，查看容器状态；
该资源适配器管理可包括以下至少之一：创建资源适配器实体，删除资源适配器实体，激活资源适配器实体，去激活资源适配器实体，更新资源适配器实体的配置；
该业务管理可包括以下至少之一：激活业务，去激活业务，查看业务状态，配置业务管理数据；
该安装管理可包括以下至少之一：组件的安装，组件的卸载；
该告警管理可包括以下至少之一：查询告警，清除告警；
该跟踪管理可包括：设置跟踪级别。
在另一实施例中还提供了一种JSLEE容器系统的处理方法，图6是根据本发明实施例的一种JSLEE容器系统的处理方法的流程图，如图6所示，该方法包括如下步骤：
步骤S602，JSLEE容器系统的资源适配器接收外部网络的信息，以JSLEE标准将该信息封装成第一事件接入该JSLEE容器系统的内部，将所述第一事件通知到该JSLEE容器系统的路由器；
步骤S604，该路由器将接收的该第一事件进行路由，找到处理该第一事件的业务，并调用该业务的业务处理函数处理该第一事件产生第二事件；
步骤S606，将该第二事件通知该路由器，或者，该业务调用该资源适配器将该第二事件以标准协议信令发送给外部网络。
通过上述方法步骤，解决了网络构架不能很好实现不同设备厂商通信方案的融合的问题，实现了不同设备厂商通信方案的融合。
在本实施例中，该业务或者该资源适配器可以使用工具集，该工具集可包括以下至少之一：定时器，跟踪工具，告警工具。
在本实施例中，该方法还可包括：
该JSLEE容器系统的管理服务端执行注册的管理功能，该管理功能包括以下至少之一：容器管理，资源适配器管理，业务管理，安装管理，告警管理，跟踪管理；
该容器管理可包括以下至少之一：启动容器，停止容器，查看容器状态；
该资源适配器管理可包括以下至少之一：创建资源适配器实体，删除资源适配器实体，激活资源适配器实体，去激活资源适配器实体，更新资源适配器实体的配置；
该业务管理可包括以下至少之一：激活业务，去激活业务，查看业务状态，配置业务管理数据；
该安装管理可包括以下至少之一：组件的安装，组件的卸载；
该告警管理可包括以下至少之一：查询告警，清除告警；
该跟踪管理可包括：设置跟踪级别。
本发明实施例还提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被执行时实现上述JSLEE容器系统的处理方法。
在本发明的另一个实施例中，还提供了一种网络融合的系统，包括：外部网络资源系统、JSLEE容器系统、以及外部管理系统；
该JSLEE容器系统以标准协议与该外部网络资源对接(join together)，或者，以JSLEE标准将该外部网络资源发生的动作封装成事件接入该JSLEE容器系统的内部；
该外部管理系统通过Java管理扩展JMX方式与该JSLEE容器系统中交互，实现对该JSLEE容器系统的功能的配置和管理。
通过上述系统，解决了网络构架不能很好实现不同设备厂商通信方案的融合的问题，实现了不同设备厂商通信方案的融合。
在本实施例中，该JSLEE容器系统可包括组件：资源适配器，路由器，业务，工具集，公共核心功能模块，以及管理服务端；
该路由器可设置为：将接收到的事件进行路由，找到处理该事件的该业务，并调用该业务处理该事件的方法；
该工具集可设置为：为该JSLEE容器系统提供公共工具；
该公共核心功能模块可设置为：建立该JSLEE容器系统的上下文环境；
该管理服务端可设置为：使用Java管理扩展JMX将对该JSLEE容器系统的管理功能以管理构件Mbean的方式注册到MBean服务器中。
在本实施例中，外部网络资源系统可包括以下至少之一：
互联网，下一代NGN网络，IP多媒体子系统IMS网络，固网，全球移通讯系统GSM网，码分多址CDMA网的业务交换点SSP业务交换点、数据库、在线计费系统OCS、短信中心，彩信中心。
下面结合可选实施例和实施方式对本发明实施例进行详细说明。
通过本发明的实施例实现了在互联网、七号信令网(Signaling System 7， 简称为SS7)、下一代网络(Next Generation Network,简称为NGN)或IP(Internet Protocol，因特网协议)多媒体子系统(IP Multimedia Subsystem，简称为IMS)电信网络领域中，智能网的JAVA应用编程接口(Java APIs for Integrated Networks，简称为JAIN)业务逻辑执行环境(Service Logic Execution Environment，简称为SLEE)技术(简称JSLEE)实现网络融合的一种开放架构与系统。
本发明的实施例提出的一种基于JSLEE技术的架构与系统，能真正实现不同设备厂商通信方案的融合、实现信息通信技术(Information Communication Technology，简称为ICT)融合。
外部网络系统代表各种网络资源，如互联网/NGN/IMS网络、固网/全球移通讯系统(Global System of Mobile communication，简称为GSM)网/码分多址(Code Division Multiple Access，简称为CDMA)网的业务交换点(Service Switching Point，简称为SSP)、数据库、在线计费系统(Online Charging System，简称为OCS)、短信/彩信中心等，它们通过各自的标准协议/接口与JSLEE系统交互。
JSLEE容器系统可以基于JSLEE标准实现。资源适配器(Resource Adapter，简称为RA)可设置为：对外以标准协议与外部网络资源对接，对内以JSLEE标准将外部网络资源发生的动作封装成事件接入到JSLEE容器内部；路由器可设置为：负责将容器内接收到的事件进行路由，找到处理该事件的业务，并调用该业务实现的处理该事件的方法；工具集可设置为：提供一些公共工具，如定时器功能、跟踪功能、告警功能等；公共核心功能模块可设置为：实现一些底层核心功能，如线程池、缓存、事务机制等；管理服务端可设置为：使用Java管理扩展(Java Management Extensions，简称为JMX)技术，将各种管理功能以Mbean(Managed Bean，管理构件)的方式注册在Mbean Server(MBean服务器)中。
外部管理系统可以是对JSLEE系统的操作管理部分，可通过JMX方式与JSLEE容器中的Mbean交互，实现对JSLEE系统具体功能的配置、管理。
图7是根据本发明可选实施例的一种基于JSLEE技术实现融合网络的开放架构与系统示意图，其核心是JSLEE容器，与图1的架构不同，该架构可 以是一个全方位开放的架构。其中，JSLEE可以是一个组件的容器，资源适配器、业务都可以是标准组件，安装在容器中；路由器、工具集、公共核心功能模块、管理服务端可以是容器的内置模块；外部网络可以以标准协议通过资源适配器接入JSLEE容器；外部管理客户端、告警跟踪客户端可以设置为：通过JMX接入JSLEE容器与管理服务端通讯，完成各种配置管理功能。
工具集可提供一些标准的工具如定时器、跟踪、告警工具等供业务、资源适配器等使用；公共核心功能模块可实现JSLEE容器的底层功能，如线程池、缓存、事务等机制，是各种组件在容器中运行的上下文环境；路由器可以是JSLEE容器的核心，负责将资源适配器封装的发送到容器的事件路由给负责处理该事件的业务。
管理服务端可以是JSLEE容器提供的一个Mbean Server，各种管理模块可以以Mbean的方式注册在Mbean Server中。容器管理主要可提供对JSLEE容器的管理功能，如启动/停止容器，查看容器状态等；资源适配器管理可主要提供如创建/删除/激活/去激活具体的资源适配器实体、更新某个具体的资源适配器实体的配置等功能；业务管理可主要提供如激活/去激活业务，查看业务状态，配置业务管理数据等功能；安装管理可主要提供对组件的安装/卸载功能；告警管理可主要提供如查询/清除告警等功能；跟踪管理可主要提供如设置跟踪级别等功能。
资源适配器可以是标准组件，从逻辑上可以分为两部分，一部分是与外部网络采用标准协议进行通讯的协议栈层，另一部分是将协议栈收到的外部网络产生的动作以JSLEE标准封装成事件以与JSLEE容器进行通讯的适配层。多个厂商可以提供各自的协议栈层，但是面向JSLEE容器的适配层以及开放的协议接口都可以是标准的，保障了不同厂商资源适配器的容器无关性、可移植性。
如图7所示，当外部网络有消息产生时，资源适配器的协议栈层可以收到标准协议信令，适配层可以将协议消息封装成事件通过API(Application Programming Interface，应用程序编程接口)1接口通知到容器的路由器；路由器可根据路由规则找到处理该事件的业务，并调用业务逻辑处理函数API2；业务逻辑处理时，可以产生事件并通过API 3接口通知给容器的路由器， 也可以调用资源适配器的API 4接口并以标准协议信令发送给外部网络；业务或者资源适配器可以通过API 7接口来使用工具集(说明：API 7接口中有多个具体的API，如发送/清除告警API、跟踪API、定时器API等)；工具集中的定时器可通过API 6接口将定时器事件通知到路由器；管理服务端可通过API 5接口来执行具体的管理功能(说明：API 5口中可以有多个具体的API，如启动/停止容器API，创建/删除/激活/去激活资源适配器实体API，激活/去激活业务等API，即每个管理功能均可以有对应的API)。
通过以上描述可以看出，本方案基于JSLEE技术实现的业务逻辑运行环境可以是一个组件容器，资源适配器、业务都可以是标准化组件，使用标准的API接口，标准组件和SLEE之间可具有可移植性；要接入新的外部网络资源，可以只需要安装部署对应的资源适配器，扩展性极强；容器内置的工具集、公共核心功能可解除业务开发者对常用工具、复杂上下文环境的开发，同时由于业务开发独立于SLEE容器以及资源适配器屏蔽了底层协议，使得业务开发者可以集中精力开发业务逻辑本身，更快速地推出新业务；对外可管理接口标准，便于实施统一的管理。该架构的引入，使得NGIN架构下由同一厂商提供协议适配器、SLEE、外部管理全套系统的封闭生态被打破，可以由运营商自己或者不同厂商提供JSLEE容器、各种资源适配器，独立于SLEE开发业务。这种全方位开放的架构，打造了一个生态链，有利于电信运营商择优选择、组合多个厂商的解决方案，同时很容易地通过使用相应的资源适配器将互联网协议接入JSLEE容器，以开发面向ICT的融合创新业务。
图8是根据本发明可选实施例的一种以SIP呼叫流程为例的系统交互示意图，如图8所示，该系统交互可包括如下步骤。
步骤S802，NGN/IMS核心网发送SIP(Session Initiation Protocol，会话初始协议)INVITE(邀请)请求到SIP RA；
步骤S804，SIP RA发现此INVITE是一个对话外的新INVITE，则内部新建一个活动对象，并调用startActivity()方法通知容器有新会话产生，容器产生相应的新会话对象；
步骤S806，SIP RA将此INVITE消息封装成invite事件，并调用fireEvent()方法将此事件通知给容器；
步骤S808，容器的路由器根据路由规则找到处理此invite事件的业务，调用该业务实现的OnINVITE()方法进行业务逻辑处理；
步骤S810，业务调用SIP RA的SendResponse()方法返回100响应；
步骤S812，SIP RA将业务的方法调用编码成标准的SIP信令，给NGN/IMS核心网返回100Trying响应；
步骤S814，业务调用SIP RA的SendResponse()方法返回180响应；
步骤S816，SIP RA将业务的方法调用编码成标准的SIP信令，给NGN/IMS核心网返回180Ring响应；
步骤S818，业务调用SIP RA的SendResponse()方法返回200响应；
步骤S820，SIP RA将业务的方法调用编码成标准的SIP信令，给NGN/IMS核心网返回200Ring响应；
步骤S822，NGN/IMS核心网发送ACK给SIP RA；
步骤S824，SIP RA将ACK(应答)消息封装成ack事件，并调用fireEvent()方法将此事件通知给容器；
步骤S826，容器的路由器根据路由规则找到处理此ack事件的业务，调用该业务实现的OnACK()方法进行业务逻辑处理；
步骤S828，NGN/IMS核心网发送BYE(再见)给SIP RA；
步骤S830，SIP RA将BYE消息封装成bye事件，并调用fireEvent()方法将此事件通知给容器；
步骤S832，容器的路由器根据路由规则找到处理此bye事件的业务，调用该业务实现的OnBYE()方法进行业务逻辑处理；
步骤S834，业务调用SIP RA的SendResponse()方法对BYE消息返回200响应；
步骤S836，SIP RA将业务的方法调用编码成标准的SIP信令，给NGN/IMS核心网返回200BYE响应。
本领域普通技术人员可以理解上述实施例的全部或部分步骤可以使用计算机程序流程来实现，所述计算机程序可以存储于一计算机可读存储介质中， 所述计算机程序在相应的硬件平台上(如系统、设备、装置、器件等)执行，在执行时，包括方法实施例的步骤之一或其组合。
可选地，上述实施例的全部或部分步骤也可以使用集成电路来实现，这些步骤可以被分别制作成一个个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。
上述实施例中的装置/功能模块/功能单元可以采用通用的计算装置来实现，它们可以集中在单个的计算装置上，也可以分布在多个计算装置所组成的网络上。
上述实施例中的装置/功能模块/功能单元以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。上述提到的计算机可读取存储介质可以是只读存储器，磁盘或光盘等。
工业实用性
通过本发明实施例，提供了一种智能网的Java应用编程接口业务逻辑执行环境JSLEE容器系统，包括组件：资源适配器，业务以及路由器，该资源适配器设置为：以标准协议与外部网络资源对接，或者，以JSLEE标准将该外部网络资源发生的动作封装成事件接入该JSLEE容器系统的内部，该路由器设置为：将接收到的事件进行路由，找到处理该事件的该业务，并调用该业务处理该事件的方法，从而解决了网络构架不能很好实现不同设备厂商通信方案的融合的问题，实现了不同设备厂商通信方案的融合。

Claims (10)

  1. 一种智能网的Java应用编程接口业务逻辑执行环境(JSLEE)容器系统，包括组件：资源适配器，业务以及路由器；
    所述资源适配器设置为：以标准协议与外部网络资源对接，或者，以JSLEE标准将所述外部网络资源发生的动作封装成事件接入所述JSLEE容器系统的内部；
    所述路由器设置为：根据接收到的事件找到处理所述事件的所述业务，并调用所述业务处理所述事件的方法。
  2. 根据权利要求1所述的系统，所述JSLEE容器系统还包括工具集，所述工具集设置为：为所述JSLEE容器系统提供公共工具，所述工具集包括以下至少之一：定时器，跟踪工具，告警工具。
  3. 根据权利要求1所述的系统，所述JSLEE容器系统还包括公共核心功能模块，所述公共核心功能模块设置为：建立所述JSLEE容器系统的上下文环境，所述公共核心功能包括以下至少之一：线程池、缓存、事务机制。
  4. 根据权利要求1至权利要求3中任一项所述的系统，所述JSLEE容器系统还包括管理服务端，所述管理服务端设置为：使用Java管理扩展JMX将对所述JSLEE容器系统的管理功能以管理构件Mbean的方式注册到MBean服务器中；
    所述管理服务端中注册的管理功能包括以下至少之一：容器管理，资源适配器管理，业务管理，安装管理，告警管理，跟踪管理；
    所述容器管理包括以下至少之一：启动容器，停止容器，查看容器状态；
    所述资源适配器管理包括以下至少之一：创建资源适配器实体，删除资源适配器实体，激活资源适配器实体，去激活资源适配器实体，更新资源适配器实体的配置；
    所述业务管理包括以下至少之一：激活业务，去激活业务，查看业务状态，配置业务管理数据；
    所述安装管理包括以下至少之一：组件的安装，组件的卸载；
    所述告警管理包括以下至少之一：查询告警，清除告警；
    所述跟踪管理包括：设置跟踪级别。
  5. 一种JSLEE容器系统的处理方法，包括：
    JSLEE容器系统的资源适配器接收外部网络的信息，以JSLEE标准将所述信息封装成第一事件接入所述JSLEE容器系统的内部，将所述第一事件通知到所述JSLEE容器系统的路由器；
    所述路由器将接收的所述第一事件进行路由，找到处理所述第一事件的业务，并调用所述业务的业务处理函数处理所述第一事件产生第二事件；
    将所述第二事件通知所述路由器，或者，所述业务调用所述资源适配器将所述第二事件以标准协议信令发送给外部网络。
  6. 根据权利要求5所述的方法，还包括：
    所述业务或者所述资源适配器使用工具集，所述工具集包括以下至少之一：定时器，跟踪工具，告警工具。
  7. 根据权利要求5所述的方法，还包括：
    所述JSLEE容器系统的管理服务端执行注册的管理功能，所述管理功能包括以下至少之一：容器管理，资源适配器管理，业务管理，安装管理，告警管理，跟踪管理；
    所述容器管理包括以下至少之一：启动容器，停止容器，查看容器状态；
    所述资源适配器管理包括以下至少之一：创建资源适配器实体，删除资源适配器实体，激活资源适配器实体，去激活资源适配器实体，更新资源适配器实体的配置；
    所述业务管理包括以下至少之一：激活业务，去激活业务，查看业务状态，配置业务管理数据；
    所述安装管理包括以下至少之一：组件的安装，组件的卸载；
    所述告警管理包括以下至少之一：查询告警，清除告警；
    所述跟踪管理包括：设置跟踪级别。
  8. 一种网络融合的系统，包括：外部网络资源系统、JSLEE容器系统、 以及外部管理系统；
    所述JSLEE容器系统以标准协议与所述外部网络资源对接，或者，以JSLEE标准将所述外部网络资源发生的动作封装成事件接入所述JSLEE容器系统的内部；
    所述外部管理系统通过Java管理扩展JMX方式与所述JSLEE容器系统中交互，实现对所述JSLEE容器系统的功能的配置和管理。
  9. 根据权利要求8所述的系统，其中，所述JSLEE容器系统包括组件：资源适配器，路由器，业务，工具集，公共核心功能模块，以及管理服务端；
    所述路由器设置为：将接收到的事件进行路由，找到处理所述事件的所述业务，并调用所述业务处理所述事件的方法；
    所述工具集设置为：为所述JSLEE容器系统提供公共工具；
    所述公共核心功能模块设置为：建立所述JSLEE容器系统的上下文环境；
    所述管理服务端设置为：使用Java管理扩展JMX将对所述JSLEE容器系统的管理功能以管理构件Mbean的方式注册到MBean服务器中。
  10. 根据权利要求8所述的系统，其中，外部网络资源系统包括以下至少之一：
    互联网，下一代NGN网络，IP多媒体子系统IMS网络，固网，全球移通讯系统GSM网，码分多址CDMA网的业务交换点SSP业务交换点、数据库、在线计费系统OCS、短信中心，彩信中心。
PCT/CN2016/080389 2015-09-25 2016-04-27 Jslee容器系统，处理方法及网络融合的系统 WO2016165673A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510624704.0 2015-09-25
CN201510624704.0A CN106559717A (zh) 2015-09-25 2015-09-25 Jslee容器系统，处理方法及网络融合的系统

Publications (1)

Publication Number Publication Date
WO2016165673A1 true WO2016165673A1 (zh) 2016-10-20

Family

ID=57127138

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/080389 WO2016165673A1 (zh) 2015-09-25 2016-04-27 Jslee容器系统，处理方法及网络融合的系统

Country Status (2)

Country Link
CN (1) CN106559717A (zh)
WO (1) WO2016165673A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109408337A (zh) * 2018-10-31 2019-03-01 京东方科技集团股份有限公司 一种接口运维的方法及装置
CN113282373A (zh) * 2021-06-03 2021-08-20 青岛海尔科技有限公司 用于分布式并发应用服务的方法、装置和设备

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107368339B (zh) * 2017-07-25 2020-06-12 上海携程商务有限公司 容器入口程序运行方法、系统、设备及存储介质
CN109756366B (zh) * 2018-12-24 2022-02-11 上海欣方智能系统有限公司 基于caas的智能网scp云服务实现系统
CN112908441B (zh) * 2021-03-04 2024-06-21 文华学院 一种医疗平台的数据处理方法、装置以及处理设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090180398A1 (en) * 2008-01-16 2009-07-16 Sony Corporation, A Japanese Corporation Method and apparatus for facilitating interaction between the services provided by respective networked devices
CN101826987A (zh) * 2010-04-27 2010-09-08 北京邮电大学 一种基于融合开放网络的混合服务支撑系统及方法
CN102064990A (zh) * 2011-02-22 2011-05-18 深圳市同洲电子股份有限公司 一种业务网络接入平台以及业务网络接入方法
CN104053075A (zh) * 2013-03-12 2014-09-17 中兴通讯股份有限公司 智能网能力与第三方能力融合方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090180398A1 (en) * 2008-01-16 2009-07-16 Sony Corporation, A Japanese Corporation Method and apparatus for facilitating interaction between the services provided by respective networked devices
CN101826987A (zh) * 2010-04-27 2010-09-08 北京邮电大学 一种基于融合开放网络的混合服务支撑系统及方法
CN102064990A (zh) * 2011-02-22 2011-05-18 深圳市同洲电子股份有限公司 一种业务网络接入平台以及业务网络接入方法
CN104053075A (zh) * 2013-03-12 2014-09-17 中兴通讯股份有限公司 智能网能力与第三方能力融合方法和装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109408337A (zh) * 2018-10-31 2019-03-01 京东方科技集团股份有限公司 一种接口运维的方法及装置
CN113282373A (zh) * 2021-06-03 2021-08-20 青岛海尔科技有限公司 用于分布式并发应用服务的方法、装置和设备

Also Published As

Publication number Publication date
CN106559717A (zh) 2017-04-05

Similar Documents

Publication Publication Date Title
WO2016165673A1 (zh) Jslee容器系统，处理方法及网络融合的系统
JP6348926B2 (ja) 電話通信アプリケーションサービス
US9479400B2 (en) Servlet API and method for XMPP protocol
US11153412B1 (en) Systems and/or methods for non-intrusive injection of context for service mesh applications
US9258379B2 (en) Session initiation protocol adapter system and method providing stateless node mapping to a stateful server node hosting a communication session for an actor
JP6266696B2 (ja) サービス志向ソフトウェア定義型セキュリティのフレームワーク
US11108653B2 (en) Network service management method, related apparatus, and system
US20050044188A1 (en) Service providing system allowing flexible cooperation between applications exploiting different protocols
US20090287740A1 (en) Method for enabling on-demand communication services
US8850051B2 (en) Methods, systems, and computer program products for transaction-based internet protocol (IP) telephony call processing
EP3639474B1 (en) Derivation of network service descriptor from network service requirements
WO2023040502A1 (zh) 用户服务注册
US11411812B2 (en) Dynamic service creation for microservice-based integration service
US20090300662A1 (en) Mechanism for collocation in a Java virtual machine of JSLEE and Java EE
Wohlstadter et al. A service-oriented middleware for runtime web services interoperability
US20020191771A1 (en) Generic service component for telephony container server
WO2023040450A1 (zh) 区块链服务网络的组建
US11606268B2 (en) Cloud computing environment with split connectivity and application interfaces that enable support of separate cloud services
US6694002B2 (en) Generic service component for wireless services
Schülke et al. Service delivery platform: Critical enabler to service providers' new revenue streams
Zhu et al. Enhancing ESB based execution platform to support flexible communication Web services over heterogeneous networks
Bo et al. Design and Implementation of Enhanced State Machine for Telecom Web Service
Femminella et al. An Extended Java Call Control for the Session Initiation Protocol
Vannucci Extended call control telecommunications web service
SECTOR et al. ITU-Tfg Cloud TR

Legal Events

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

Ref document number: 16779648

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16779648

Country of ref document: EP

Kind code of ref document: A1