JP2016131409A - Telephony application services - Google Patents
PROBLEM TO BE SOLVED: To provide telephony application services through use of a service delivery platform (SDP) and by implementing a service-oriented architecture (SOA)-based approach.SOLUTION: Various "widgets" of telephony functionality are selected, each widget providing functionality such as call forwarding, call blocking and conferencing. These widgets not only provide call manipulation, but can provide the logic used to process a call. An application or application service thus can combine and/or compose these widgets as needed to provide telephony functionality.SELECTED DRAWING: Figure 15
çºæã®è©³ç´°ãªèª¬æ

ãã¾ãã¾ãªå®æ½å½¢æ ã«å¾ãã·ã¹ãã ããã³æ¹æ³ã¯ãé»è©±éä¿¡æ©è½ãã¢ããªã±ã¼ã·ã§ã³ãµã¼ãã¹ã¨ãã¦éçºãå©ç¨ããããã®ãã©ãããã©ã¼ã ãæä¾ãããã¨ã«ãã£ã¦ãé»å­ãããã¯ã¼ã¯ãã¼ã¹ã®é»è©±éä¿¡ã·ã¹ãã ã«å¯¾ããæ¢å­ã®æ¹ç­ã«ãããåè¿°ããã³ä»ã®ä¸åãè§£æ¶ããã DETAILED DESCRIPTION OF THE INVENTION Systems and methods according to various embodiments have been described above and others in existing strategies for electronic network-based telephony systems by providing a platform for developing and utilizing telephony capabilities as application services. To solve the deficiencies.

ï¼ã¤ã®å®æ½å½¢æ ã«å¾ãé»è©±éä¿¡ã¢ããªã±ã¼ã·ã§ã³ãµã¼ãã¹ãæä¾ãããã¨ã«å¯¾ããæ¹ç­ã¯ããµã¼ãã¹æä¾ãã©ãããã©ã¼ã ï¼ï¼³ï¼¤ï¼°ï¼ã®ä½¿ç¨ãéãã¦ãµã¼ãã¹æåã¢ã¼ã­ãã¯ãã£ï¼ï¼³ï¼¯ï¼¡ï¼ãã¼ã¹ã®æ¹ç­ãå®ç¾ãããã¨ã«ãã£ã¦ãã¾ãã¾ãªãµã¼ãã¹ãæä¾å¯è½ã§ãããã¨ãæ´»ç¨ãããï¼³ï¼¤ï¼°å®ç¾ä¾ã¯ãã³ã¼ã«å¶å¾¡æ©è½ãå®è¡ãããããã«ããã³ã¼ã«å¶å¾¡ã¤ãã¼ãã©ãªã©ã®ä½ããã®åä½¿ç¨å¯è½ãªæ©è½æ§ãæä¾ãããã¾ãã¾ãªã¤ãã¼ãã©ãæ´»ç¨ãããã¨ãã§ããåºç¤ã¨ãªããããã¯ã¼ã¯ãããããã®æ©è½ãååºããã¡ãã£ã¢ãµã¼ãã¤ãã¼ãã©ã¯ãä¼è­°æ©è½ã¾ãã¯ã¹ããªã¼ãã³ã°æ©è½æ§ãå°åºãããªã©ã®ã¡ãã£ã¢ãµã¼ãæ©è½æ§ããæ©è½æ§ãå®éã«ã©ã®ããã«å®ç¾ããããã¨ã¯ç¬ç«ãã¦æä¾ãããããã«ãããï¼³ï¼¤ï¼°ã¯ãé³å£°å¯¾è©±ãã¢ããªã±ã¼ã·ã§ã³ã«è¿½å ããé³å£°ã¢ã¯ã»ã¹ã¤ãã¼ãã©ãªã©ã®ã¤ãã¼ãã©ãå«ããã¨ãã§ããã Â Â The strategy for providing telephony application services according to one embodiment is that various services can be provided by implementing a service-oriented architecture (SOA) based strategy through the use of a service delivery platform (SDP). use. SDP implementations can take advantage of various enablers that provide some reusable functionality, such as call control enablers that allow call control functions to be performed, and take these functions out of the underlying network . The media server enabler allows media server functionality, such as deriving conferencing functionality or streaming functionality, to be provided independent of how the functionality is actually implemented. The SDP can also include an enabler, such as a voice access enabler that adds voice interaction to the application.

ï¼³ï¼¤ï¼°ã¯çµ¶å¯¾ã«å¿ è¦ã¨ããããã§ã¯ãªããã¨ããã®ããç°ãªããããã¯ã¼ã¯ã«ããã£ã¦æ§ç¯ããããã¸ã§ãããå¥½é©ã ããã§ãããã¾ããçºæãå®è¡ããã®ã«ã¤ãã¼ãã©ã®ä½¿ç¨ãå¿ è¦ã¨ããããã§ã¯ãªãããã®åºé¡ã§ã¯ãï¼³ï¼¤ï¼°ããã³ï¼ã¾ãã¯ã¤ãã¼ãã©ãæããå®æ½å½¢æ ã«çºæãå¶éããããã«ä½ãè§£éããã¦ã¯ãªããªãã Â Â SDP is not absolutely necessary. This is because a widget constructed across different networks is also suitable. Also, it is not necessary to use an enabler to implement the invention. This application should not be construed as limiting the invention to embodiments having SDP and / or enablers.

ããããªããããã¾ãã¾ãªå®æ½å½¢æ ã«å¾ãã·ã¹ãã ããã³æ¹æ³ã¯ãã®æ¦å¿µãæ¬¡ã®ã¬ãã«ã«ãã£ã¦ãããä¸è¿°ã®æ¹ç­ã¯ã¢ããªã±ã¼ã·ã§ã³ãã­ã°ã©ãã³ã°ã¤ã³ã¿ã¼ãã§ã¤ã¹ï¼ï¼¡ï¼°ï¼©ï¼ãªã©ã®æ§æè¦ç´ ãæ´»ç¨ãã¦ãï¼äººã®ã¦ã¼ã¶ãããã¯ã¦ã¼ã¶ã¨è£ ç½®ã¨ãªã©ã®ï¼ã¤ã®çµç¹éã§ã³ã¼ã«ãè¨­å®ããã¾ãã¯ä¼è­°éè©±ã§ï¼äººãæ¥ç¶ããããã«ãã¡ãã£ã¢ã»ãã·ã§ã³ãå¦çãããã³ã¼ã«ã®éç¥ãåããããããªã©ã®ä»ã®æ©è½ãè¡ãªããã¨ãã§ããã Â Â However, systems and methods according to various embodiments take this concept to the next level. The above strategies utilize components such as application programming interfaces (APIs) to set up a call between two endpoints, such as two users or a user and a device, or connect five people in a conference call Other functions such as handling multimedia sessions and receiving call notifications can be performed.

ä»£ããã«ããã¨ãã°ãã³ã¼ã«ãé»è©±éä¿¡æ©è½æ§ãå«ããããã«éå®ãããªãæ©è½ãªã©ã®ãã«ãã¡ãã£ã¢ã»ãã·ã§ã³ã®ããã¸ã§ããããè¦å®ãããã¨ã«ããããã¾ãã¾ãªå©ç¹ãå¾ããããåã ã®ãã¸ã§ããã¯ããã¨ãã°ãã³ã¼ã«ã¾ãã¯ãã«ãã¡ãã£ã¢ã»ãã·ã§ã³è»¢éã

ã³ã¼ã«ãã­ãã¯ãç·æ¥ã³ã¼ã«éå§ãä¼è­°ãã³ã¼ã«é æ¬¡çä¿¡ãã¡ãã»ã¼ã¸ã³ã°ãèª²éãã­ãã¡ã¤ã«ãªã©ã®æ©è½ãæä¾ãããã¨ãã§ãããåãã¸ã§ããã¯ãï¼³ï¼¤ï¼°ã®ã³ã¼ã«å¶å¾¡ã¤ãã¼ãã©ä¸ã«å®ç½®ãã¦é»è©±éä¿¡æ©è½æ§ã¾ãã¯ä»ã®ãã«ãã¡ãã£ã¢ã»ãã·ã§ã³æ©è½ãæä¾ããã³ã¼ãã¾ãã¯ã©ã¤ãã¢ããªã±ã¼ã·ã§ã³ã®ä¸é¨ã§ãããã¨ãã§ããããããã®ãã¸ã§ããã¯ãã®ããã«ãã»ãã·ã§ã³æä½ãæä¾ãããã¨ãã§ããã ãã§ãªããã»ãã·ã§ã³ããã³ä»ã®ãããã¯ã¼ã¯ï¼ãã¨ãã°ï¼©ï¼®ï¼æ©è½ãªã©ãå¦çããã®ã«ç¨ãããã¨ãã§ããã­ã¸ãã¯ãæä¾ãããã¨ãã§ããããã¸ã§ããã¯ãåªä½ï¼ããã³ãã«ãã¡ãã£ã¢ï¼å¶å¾¡ãã¡ãã»ã¼ã¸ã³ã°ãèª²éãããã³ã¦ã¼ã¶è©³ç´°ã¸ã®ã¢ã¯ã»ã¹ã®ããã®ã­ã¸ãã¯ãæä¾ãããã¨ãã§ããã Instead, various benefits may be gained by defining a âbidgetâ for multimedia sessions such as, for example, but not limited to, call, telephony functionality. Each widget can be, for example, a call or multimedia session transfer,

Functions such as call blocking, emergency call initiation, conferencing, sequential call arrival, messaging, billing profile, etc. can be provided. Each widget can be part of a code or light application that sits on top of the SDP call control enabler to provide telephony functionality or other multimedia session functionality. These widgets can thus not only provide session operations, but can also provide logic that can be used to handle sessions and other network (eg, IN) functions and the like. The widget can also provide logic for media (and multimedia) control, messaging, billing, and access to user details.

ãã®ããã«ãã¢ããªã±ã¼ã·ã§ã³ã¾ãã¯ãµã¼ãã¹ã¯ããããã®ãã¸ã§ãããçµåãã¦ãã«ãã¡ãã£ã¢ãé»è©±éä¿¡ãããã³ä»ã®ï¼©ï¼®æ©è½æ§ãæä¾ãããã¨ãã§ããããã¨ãã°ãã¢ããªã±ã¼ã·ã§ã³ã¯ãï¼çµã®ãã¸ã§ãããå©ç¨ãã¦éä¿¡ã®çºä¿¡è ï¼ããªãã¡ãï½ï¼ä¿¡ç¨ä¿è¨¼ãï½ï¼ãã­ãã¡ã¤ã«ï¼ãã¨ãã°ãå æããããã¯å¾æããæ³äººãã´ã¼ã«ããéå¸¸ãªã©ï¼ãã¾ãã¯ï½ï¼ç¶æ ï¼ãã¨ãã°ãè«æ±æ¸ï¼åå®æ®é«ããã³è«æ±æ¸æ¯æãï¼ç²¾ç®ã¹ãã¼ã¿ã¹ï¼ã«åºã¥ãå å ¥è ï¼ãèªè¨¼ããï¼ãã¨ãã°ãå å ¥è ã«ã¤ãã¦ã©ã®ãµã¼ãã¹ãè¨­å®ãããã³å¥½ã¿ãè¨­å®ãããããªã©ã®å å ¥ãã­ãã¡ã¤ã«ã«åºã¥ãã¦ï¼éä¿¡ã«æã¾ããã¿ã¹ã¯ãå¤æ­ãããã¨ãã§ããããã®æ å ±ãå¤æ­ããå¾ããã¸ã§ããä¸­ã®ã­ã¸ãã¯ãç¨ãã¦ãã³ã¼ã«ããã¤ã¹ã¡ã¼ã«ã¾ãã¯ä¼è­°ã«å ¥ãããé¢é£ã®åä¿¡è ãå¼åºããã¡ãã»ã¼ã¸ãéãããµã¼ãã¹ã«èª²éããããã«ãã¡ãã£ã¢ã»ãã·ã§ã³ãéå§ãããªã©ãéä¿¡ãã©ã®ããã«å¦çããããå¤æ­ãããã¨ãã§ããã Â Â Thus, an application or service can combine these bidets to provide multimedia, telephony, and other IN functionality. For example, the application uses a set of bidets to communicate the caller (ie, a) credit guarantee, b) profile (eg, prepaid or postpaid, legal, gold, normal, etc.), or c) state (eg, (Subscriber based on invoice / account balance and invoice payment / checkout status) and want to communicate (eg, based on subscription profile such as what services, settings, and preferences are set for the subscriber) Can determine the task. After determining this information, use the logic in the widget to place the call into a voicemail or conference, call the relevant recipient, send a message, charge for the service, initiate a multimedia session, etc. How to process can be determined.

ãã®ããã«ãé»è©±éä¿¡ã¢ããªã±ã¼ã·ã§ã³ãµã¼ãã¹ã®å®ç¾ä¾ã¯ãæ§ç¯ãã­ãã¯ã¨ãã¦ãã¸ã§ãããå©ç¨ãã¦ãã¸ãã¹ä¿¡å·éä¿¡ãè¡ãªããä¿¡å·éä¿¡ããã³ãã¼ã¹ä¿¡å·éä¿¡ã®ååºãå¯è½ã«ãããã¨ãã§ãããä¸æ¦ãããæä¾ãããã¨ãå¤æ§ãªã¢ããªã±ã¼ã·ã§ã³ãæ§ç¯ãã¦ããã«ãã¡ãã£ã¢ããã³ã³ã¼ã«è»¢éãã³ã¼ã«ãã­ãã¯ãã³ã¼ã«çè´ãªã©ã®æ©è½ãå®è¡ãããã¨ãã§ããããã¸ã§ããã¯ãå¿ è¦ã«å¿ãã¦ãï¼³ï¼¤ï¼°ãç¨ãã¦æ¬æ ¼çãªé»è©±éä¿¡ã¢ããªã±ã¼ã·ã§ã³ã¾ãã¯ã¢ããªã±ã¼ã·ã§ã³ãµã¼ãã¹ãæä¾ããããã«æ§æå¯è½ã§ããããã¨ãã°ãç¾å¨ã®ã¦ã¼ã¶æå¨æ å ±ãã¦ã¼ã¶åå¥½ãªã©ã«åºã¥ãå¾ããªã©ã®ããã¾ãã¾ãªè¦å ã«åºã¥ãã¦ã©ãã¸ã³ã¼ã«ãè»¢éãã¹ãããå¤æ­ããï¼¶ï½ï¼©ï¼°ã¢ããªã±ã¼ã·ã§ã³ãä½æãããã¨ãã§ãããå¥ã®ä¾ã§ã¯ããªã¢ã«ã¿ã¤ã ã§ã¾ãã¯äºããã­ã°ã©ã ãããæ æ§ã§ã©ãã«ã³ã¼ã«ãè»¢éãã¹ãããªã©ãã¦ã¼ã¶ãæ±ºå®ã§ããããã«ããæ§å äº¤ææ©ï¼ï¼°ï¼¢ï¼¸ï¼ã¢ããªã±ã¼ã·ã§ã³ãä½æãããã¨ãã§ãããæ§æã¯ãJavaï¼ç»é²åæ¨ï¼ã¾ãã¯ï¼¢ï¼°ï¼¥ï¼¬ï¼ãã¸ãã¹ãã­ã»ã¹å®è¡è¨èªï¼ãªã©ã®ä»»æã®é©åãªæè¡ãç¨ãã¦éæå¯è½ã§ããããããã®ãã¸ã§ããã¯ãæ°ããªé»è©±éä¿¡ã¾ãã¯ãã«ãã¡ãã£ã¢ã¢ããªã±ã¼ã·ã§ã³ã¾ãã¯ã¢ããªã±ã¼ã·ã§ã³ãµã¼ãã¹ãæä¾ããããã«æ§æå¯è½ã§ããã Â Â In this manner, the implementation example of the telephone communication application service can perform business signal communication using a widget as a building block, and enable signal communication and base signal communication to be taken out. Once this is provided, various applications can be built to perform functions such as multimedia and call forwarding, call blocking, call eavesdropping and the like. The widget can be configured to provide full-fledged telephony applications or application services using SDP as needed. For example, a VoIP application can be created that determines where a call should be forwarded based on various factors, such as based on current user location information, user preferences, and the like. In another example, a private branch exchange (PBX) application can be created that allows a user to determine where to transfer a call in real time or in a pre-programmed manner. The configuration can be accomplished using any suitable technology such as Java or BPEL (Business Process Execution Language). These widgets can be configured to provide new telephony or multimedia applications or application services.

ãã®ããã«ãï¼ã¤ã®å®æ½å½¢æ ã«å¾ãå®ç¾ä¾ã¯ãé»è©±éä¿¡ã¢ããªã±ã¼ã·ã§ã³ã¾ãã¯ã¢ããªã±ã¼ã·ã§ã³ãµã¼ãã¹ãæä¾ããããã«æ§æå¯è½ãªï¼çµã®ãã¸ã§ãããæä¾ãããï¼çµã®ãã¸ã§ããã¯ãåºç¤ã¨ãªããããã¯ã¼ã¯ï¼ãã¨ãã°ãï¼°ï¼¢ï¼¸ãï¼³ï¼©ï¼°ãªã¼ãã¼ï¼©ï¼­ï¼³ãªã©ï¼ã®æè¡ããååºããã¦ãã³ã¼ã«å¶å¾¡è½åã¾ãã¯ã¡ãã£ã¢ãµã¼ãè½åã ãã§ãªããã³ã¼ã«ã®è»¢éãã³ã¼ã«ã«ã¤ãã¦ã®æ å ±ã®å ¥æãã³ã¼ã«ã®èªè¨¼ãç®æ¨æããæå¨æ å ±ã®ãã§ãã¯ããã®æ å ±ã«åºã¥ãã³ã¼ã«ã®æ¹åä»ããªã©ã®ãä»ã®ã³ã¼ã«é¢é£ã®æ©è½æ§ãå ¬éãããã¨ãã§ãããï¼°ï¼¢ï¼¸ã¢ããªã±ã¼ã·ã§ã³ãªã©ã®æ¬æ ¼çãªã¢ããªã±ã¼ã·ã§ã³ã¯æ¬¡ã«ç°ãªãåå¥ã®ãã¸ã§ããã®æ§æãéãã¦æ§ç¯å¯è½ã§ããã Â Â Thus, an implementation according to one embodiment provides a set of widgets that can be configured to provide telephony applications or application services. A set of widgets is taken from the underlying network technology (eg, PBX, SIP over IMS, etc.) to not only call control or media server capabilities, but also transfer calls, get information about calls, call Other call-related functionality can be exposed, such as authentication, target search, location information checking, and call direction based on this information. Full-fledged applications such as PBX applications can then be built through different individual widget configurations.

ä»æ¥ããã®ãããªæ©è½æ§ã¯ãï½ï¼ãã¸ã§ãããæ§æããï¼©ï¼´å®åã®ãï½ï¼ãã­ãã³ã«ã«ããããï½ï¼ãã¸ã§ããã®åä½¿ç¨ãªãã«ããã­ãã©ã¤ã¨ã¿ãªå®ç¾ä¾ãéãã¦æä¾ãããã§ããããæ©è½ã¯ãã¢ããªã±ã¼ã·ã§ã³ãæ§ç¯ããããã«èªç±ã«æ§æå¯è½ãªåå¥ã®ã³ã¼ã«å¦çãã¸ã§ããã¨ãã¦ã¯æç¤ºãããªãã§ããããæ§æããããã¸ã§ããã®ä½¿ç¨ã¯ãæ­£ããå¾ ã¡æéã§ãã®ã¬ãã«ã§ã³ã¼ã«ã«éå¸¸ã«è¿ éã«åå¿ã§ãããã¨ãªã©ã®å©ç¹ãä¸ãããã¨ããã®

ããã³ã¼ã«ã®éã«ã¢ããªã±ã¼ã·ã§ã³ã«è©±ãããããã¨ãæ¥µãã¦éè¦ã¨ããããã§ã¯ãªãããã§ããããã®çç±ã¯ãã­ã¸ãã¯ãã³ã¼ã«ãæ­£ããæ±ãã¢ããªã±ã¼ã·ã§ã³ã«ä»£ãããã®ã«ãªãããã§ããã Today, such functionality will be provided through a proprietary implementation without c) reuse of the bidet, c) of the IT practices that make up the bidet, b) the protocol. The functionality will not be presented as a separate call processing widget that can be freely configured to build applications. The use of a structured bidet provides advantages such as being able to respond to calls very quickly at that level with the right latency. This is because talking to the application at the time of the call is not critical, because logic replaces the application that handles the call correctly.

ããã«ãï¼¶ï½ï¼©ï¼°ããã³ä»®æ³ï¼°ï¼¢ï¼¸ã¢ããªã±ã¼ã·ã§ã³ãªã©ã®å¤æ°ã®æ¢å­ã®ã¢ããªã±ã¼ã·ã§ã³ã¯åæ§ã®æ©è½æ§ãå©ç¨ãããããããã®ã¢ããªã±ã¼ã·ã§ã³ã¯åãç°å¢ã«ããã¦ããå¥åã«æ§ç¯ãããããã®ãããªæ¹ç­ã®çµæãã³ã¼ããäºéã«ãªãããã®ããã«ãªã½ã¼ã¹ãç¡é§ã«ãªãã¨ã¨ãã«èª¤ãã®å¯è½æ§ãé«ã¾ã£ã¦ãã¾ããæ¬æç´°æ¸ä¸­ã«è¨è¼ã®æ¹ç­ãç¨ããã¨ãã³ã¼ã«å¶å¾¡ã¤ãã¼ãã©ãªã©ã®æ§æè¦ç´ ãç¨ãã¦ããã¨ãã°Javaï¼ç»é²åæ¨ï¼ã¾ãã¯ï¼¢ï¼°ï¼¥ï¼¬ãªã©ã®é©åãªç°å¢ã§ãããã®æ©è½ã®æ§æã¨ãã¦åå§çãªæ©è½ã¾ãã¯ãã¸ã§ãããç¨ãã¦ææã®ã¢ããªã±ã¼ã·ã§ã³ãæ§ç¯ãããã¨ãã§ããã Â Â In addition, many existing applications such as VoIP and virtual PBX applications utilize similar functionality, but these applications are built separately even in the same environment. As a result of such measures, the code is duplicated, which wastes resources and increases the possibility of errors. Using the strategies described herein, components such as call control enablers can be used to configure primitive functions or widgets as a configuration of those functions in an appropriate environment such as JavaÂ® or BPEL, for example. It can be used to build a desired application.

ï¼³ï¼©ï¼°ä¸ã§æä¾ãããï¼©ï¼­ï¼³ã¾ãã¯ï¼°ï¼³ï¼´ï¼®ï¼ï¼©ï¼®ç¹å¾´ã«å¦ä½ã«çµ±åãããããªãã³ã«ï¼¶ï½ï¼©ï¼°ãä»®æ³ï¼°ï¼¢ï¼¸ãï¼³ï¼£ï¼©ï¼­ãï¼³ï¼©ï¼° ï¼¡ï¼³ãæå¨ããããã¯ã¼ã¯ã¸ã®ã¢ããã¿ãã³ã¼ã«å¶å¾¡ãã¡ãã£ã¢ãµã¼ãå¶å¾¡ãé³å£°ã¢ã¯ã»ã¹ãåªä½ããã³ãã«ãã¡ãã£ã¢ã¢ããªã±ã¼ã·ã§ã³ï¼ãã¨ãã°ãï¼©ï¼°ï¼´ï¼¶ãæ åãã¦ã§ãä¼è­°ãã³ã¼ã«ãªã©ï¼ããªãã³ã«ã¡ãã»ã¼ã¸ã³ã°ãªã©ã®åºæ¬æ©è½ãæä¾ããå ´åã«ã©ã®ããã«é»è©±éä¿¡ã¢ããªã±ã¼ã·ã§ã³ãµã¼ãã¹ãæä¾ããããå«ãå ·ä½çãªæè¡ããã³ï¼ã¤ã®ç¹å®çãªå±é¢ã«ç¦ç¹ãåãããä¾ç¤ºçãªå®ç¾ä¾ãæ¬¡ã«èª¬æããããããã®å±é¢ã¯åã«ä¾ç¤ºã§ããããããããã³ä»ã®ã¿ã¹ã¯ãå®è¡ããããã«å¤æ°ã®ä»ã®æ§æè¦ç´ ãç¨ããç½®æããããã³ï¼ã¾ãã¯çµåãããã¨ãã§ãããã¨ãçè§£ãã¹ãã§ãããæç´°æ¸ããã³å³ã«ç §ããã¦å½æ¥­è ã«æããã¨ãªãããã«ããããã®ãã¡ããã¤ããæ¬æç´°æ¸ä¸­ã®ã©ããã«è¨è¼ããããã³ï¼ã¾ãã¯ç¤ºåããã Â Â How to integrate with IMS or PSTN / IN features provided over SIP, as well as VoIP, virtual PBX, SCIM, SIP AS, location, adapter to network, call control, media server control, voice access, media and multi Specific technologies including how to provide telephony application services when providing basic functions such as media applications (eg, IPTV, video, web conferencing, calls, etc.) and messaging, and two specific An exemplary implementation focused on the aspects will now be described. It should be understood that these aspects are exemplary only, and that many other components can be used, substituted, and / or combined to perform these and other tasks. Some of these are described and / or suggested elsewhere herein as will be apparent to those skilled in the art in light of the specification and figures.

å¤æ°ã®ãããã¯ã¼ã¯ï¼ã¬ã¬ã·ã¼ç¾å¨ãå°æ¥ãããã³å¤å½¢ï¼ä¸ã«ãµã¼ãã¹ãé åããããããå ±å­ããããã¨ãã§ããã·ã¹ãã ãå®ç¾ãããã¨ãã§ããã Â Â Services can be deployed on a large number of networks (legacy present, future, and variants) and a system that can co-exist can be implemented.

ãã¨ãã°ãå³ï¼ï¼ï½ï¼ããã³å³ï¼ï¼ï½ï¼ã¯ãï¼ã¤ã®å®æ½å½¢æ ã«å¾ã£ã¦ç¨ãããã¨ãã§ããä¾ç¤ºçãªãµã¼ãã¹æä¾ãã©ãããã©ã¼ã ï¼ï¼³ï¼¤ï¼°ï¼ãã¼ã¹ã®ã¢ã¼ã­ãã¯ãã£ï¼ï¼ï¼ãå³ç¤ºãããå³ï¼ï¼ï½ï¼ã®ä¾ç¤ºçãªã¢ã¼ã­ãã¯ãã£ï¼ï¼ï¼ã§ã¯ãï¼³ï¼¤ï¼°ã¯ãåºç¤ã¨ãªããããã¯ã¼ã¯ãªã½ã¼ã¹ãååºãããµã¼ãã¹æåã¢ã¼ã­ãã¯ãã£ï¼ï¼³ï¼¯ï¼¡ï¼ã«å¾ãæ¨ªæ¹åã®åºæºã«åºã¥ããã©ãããã©ã¼ã ãå«ããï¼ã¤ã®å®æ½å½¢æ ã§ã¯ãï¼³ï¼¤ï¼°ã¯ãJavaï¼ç»é²åæ¨ï¼ï¼ãã©ãããã©ã¼ã ä¼æ¥­çï¼ï¼ªï¼ï¼¥ï¼¥ï¼ã«åºã¥ãæ¨ªæ¹åï¼³ï¼¯ï¼¡ãã©ãããã©ã¼ã ãå©ç¨ãããï¼³ï¼¤ï¼°ã¯ãï¼ªï¼ï¼¥ï¼¥ã³ã³ãã¼ã¸ãã³ã³ããã¨ãã¦ï¼³ï¼¯ï¼¡ ï¼³ï¼©ï¼° ï¼¡ï¼³ãï¼¯ï¼³ï¼¡ ï¼¡ï¼³ãããã³é»è©±éä¿¡ï¼¡ï¼³ãå«ããJavaï¼ç»é²åæ¨ï¼Specification Requests JSR 116/289ããã³JSR32ã«åºã¥ãã³ã³ãã¼ã¸ãã³ã³ãããå«ããï¼³ï¼¤ï¼°ã¯ãç§»åä½ãé³å£°ãããã³ä»ã®é

ä¿¡ã¤ãã¼ãã©ãå ¬éããã For example, FIGS. 1 (a) and 1 (b) illustrate an exemplary service delivery platform (SDP) based architecture 100 that may be used in accordance with one embodiment. In the exemplary architecture 100 of FIG. 1 (a), the SDP includes a platform based on lateral criteria that takes underlying network resources and follows a service-oriented architecture (SOA). In one embodiment, SDP utilizes a lateral SOA platform based on Java 2 Platform Enterprise Edition (J2EE). SDP includes converged containers based on Java Specification Requests JSR 116/289 and JSR32, including SOA SIP AS, OSA AS, and telephony AS as J2EE converged containers. SDP also exposes mobile, voice, and other communication enablers.

å³ï¼ï¼ï½ï¼ã§ãï¼³ï¼¤ï¼°ã³ã³ãã£ã®ã¥ã¬ã¼ã·ã§ã³ï¼ï¼ï¼ã¯ãã¢ããªã±ã¼ã·ã§ã³ãµã¼ããæä¾ããåºç¤ã¨ãªãï¼ªï¼ï¼¥ï¼¥ã³ã¢ä¸ã§ææã®æ©è½æ§ãå®ç¾ããããã«ç¤ºãããããã¹ã¦ã®è¦ç´ ããã³ãããã¯ã¼ã¯ã«ããã£ã¦ç®¡çãããå ±éã®ã¢ã¤ãã³ãã£ãã£ãªãã³ã«ããªã³ã·ãã«ã«ã¤ãã¦ã®ãã¹ã¦ã®ãã¼ã¿ã®å ±éãã¥ã¼ãæãããã¨ãæç¨ã§ããããµã¼ãã¹æä¾ãã©ãããã©ã¼ã ãæä¾ãããã¨ã«å¯¾ããåºæ¬çãªæ¹ç­ã¯ãæ¨æºãã¼ã¹ã®ï¼©ï¼´ï¼æ å ±æè¡ï¼ãã©ãããã©ã¼ã ï¼ãã¨ãã°ï¼ªï¼ï¼¥ï¼¥ï¼ã§å§ã¾ãããã©ãããã©ã¼ã éä¿¡ä¼ç¤¾ã°ã¬ã¼ããä½ãããã¤ãã¼ãã­ã¹ããã©ã³ã¹ãã¡ã¼ãã­ãã³ã«ï¼ï¼¨ï¼´ï¼´ï¼°ï¼ãè¶ ãã¦ï¼³ï¼©ï¼°ãDiameterãããã³Parlayãªã©ã®ãã­ãã³ã«ã«æ¡å¼µãããé»æ°éä¿¡ã«é¢é£ã®éè¦ãªãã­ãã³ã«ããµãã¼ãããããããã¨ãã°ãï¼³ï¼¤ï¼°ã¯ãï¼³ï¼©ï¼°ï¼ï¼©ï¼³ï¼£ãDiameterãããã³Parlayã³ã¢ã³ãªãã¸ã§ã¯ããªã¯ã¨ã¹ããã­ã¼ã«ã¼ã¢ã¼ã­ãã¯ãã£ï¼ï¼£ï¼¯ï¼²ï¼¢ï¼¡ï¼ã®ãµãã¼ããªãã³ã«ã¡ãã»ã¼ã¸ã³ã°ã²ã¼ãã¦ã§ã¤ã¸ã®ã¢ããã¿ãæä¾ãããã¨ãã§ãããæ¨æºçãªæ¹ç­ãç¨ãã¦ããã¨ãã°ï¼ªï¼£ï¼¡ï¼ï¼ï¼ï¼ï¼ªï¼ï¼¥ï¼¥ã³ãã¯ã¿ã¢ã¼ã­ãã¯ãã£ï¼ï¼ï¼ï¼ãç¨ãã¦ãä»»æã®ä»ã®ãªã½ã¼ã¹ã¾ãã¯ãã­ãã³ã«ã¸ã®ã¢ããã¿ãæ§ç¯ãããã¨ãã§ãããã¤ãã¼ãã©ã¯ãããã

ã¯ã¼ã¯ãªã½ã¼ã¹ããã³æ¨æºä¸ãã¤ã³ã¿ã¼ãã§ã¤ã¹ãååºãåä½¿ç¨å¯è½ãªæ§æè¦ç´ ã¨ãã¦æä¾ããããæ¬¡ã«ï¼©ï¼´ï¼ï¼³ï¼¯ï¼¡ãç¨ãã¦ãï¼ãã¨ãã°ç¬¬ä¸è ããã®ï¼ï¼³ï¼¯ï¼¡ãã¼ã¹ã®ããªã·ã¼ããã³ãã¸ãã¹ã«ã¼ã«ãå©ç¨ãã¦åå ¥çºçãµã¼ãã¹ãªã©ã®ãµã¼ãã¹ãæä¾ãããã¨ãã§ãããæ¬¡ã«ãã©ãããã©ã¼ã ã¯ãï¼³ï¼¤ï¼°ã¨ã·ã¹ãã ããã³ãµã¼ãã¹ã¨ã®ï¼³ï¼¯ï¼¡ãã¼ã¹ã®çµ±åãè¡ãªããã¨ãã§ãããç¬¬ä¸è ã³ã³ãã³ãããã³ãµã¼ãã¹ãã­ãã¤ãã¸ã®å ¬éã¯ãããªã·ã¼ãå ¬éããçµ±åãããããå®æ½ããï¼³ï¼¯ï¼¡ã«ãã£ã¦éæå¯è½ã§ããããµã¼ãã¹ãã­ãã¤ãç°å¢ãéãã¦ããªã·ã¼ç®¡çããã³è©ä¾¡ããµãã¼ãããã¤åçåããã®ã«ãï¼³ï¼¯ï¼¡ãç¨ãããã¨ãã§ããã In FIG. 1 (b), the SDP configuration 150 is shown to achieve the desired functionality on the underlying J2EE core provided by the application server. It is useful to have a common view of all data about a common identity and principal managed across all elements and networks. The basic strategy for providing a service delivery platform begins with a standards-based IT (Information Technology) platform (eg, J2EE), creates a platform communications company grade, goes beyond Hypertext Transfer Protocol (HTTP), SIP, Diameter , And extend to protocols such as Parlay. To support important protocols related to telecommunications, for example, SDP can provide support for SIP / ISC, Diameter, and Parlay Common Object Request Broker Architecture (CORBA) and an adapter to a messaging gateway. Adapters to any other resource or protocol can be constructed using standard strategies, for example using JCA 1.5 (J2EE Connector Architecture 1.5). The enabler is provided as a reusable component that extracts network resources and standard upstream interfaces. IT / SOA can then be used to provide services such as revenue generation services using SOA-based policies and business rules (eg, from third parties). The platform can then perform SOA-based integration of SDP with systems and services. Publishing to third party content and service providers can be accomplished by an SOA that publishes, integrates and enforces policies. SOA can also be used to support and streamline policy management and evaluation through a service provider environment.

ï¼³ï¼©ï¼°ãParlayãã¾ãã¯ï¼©ï¼®ãã­ãã³ã«ä¸ã§ï¼çµã®ã¤ãã¼ãã©ãæä¾ããå®ç¾ãããã¨ãã§ããããããã®ã¤ãã¼ãã©ã¯ããã¨ãã°ãï¼¯ï¼­ï¼¡ ï¼³ï¼©ï¼°ï¼ï¼³ï¼©ï¼­ï¼°ï¼¬ï¼¥æå¨ãï¼¸ï¼¤ï¼­ããã³ï¼²ï¼¬ï¼³ã¤ãã¼ãã©ä»æ§ã«å¾ãæå¨ã¤ãã¼ãã©ãå«ãã§ãããã«ä½¿ããï¼©ï¼­ï¼³æå¨ãµã¼ãããã³ï¼³ï¼©ï¼°ï¼ï¼³ï¼©ï¼­ï¼°ï¼¬ï¼¥æå¨ãµã¼ããæä¾ãããã¨ãã§ãããããã¯ä»ã®ãããã¯ã¼ã¯ããæå¨ï¼ãã¨ãã°ãããã¯ã¼ã¯æå¨ï¼ãéç´ããã¢ããªã±ã¼ã·ã§ã³ã®ããã®ä¸ãParlayï¼¸ã¤ã³ã¿ã¼ãã§ã¤ã¹ãæä¾ãã¦ãæå¨ãããã¯ã¼ã¯ã«åå ããã«æå¨ãç¨ãããã¨ãã§ãããæ¡å¼µå¯è½æå¨ãã¼ã¿ã¢ãã«ãç¨ãã¦ãå ´æãã¼ã¿ãæå¨å±æ§ã¨ãã¦ã¢ããªã³ã°ãããã¨ãã§ããããã¨ãã°ãã¤ãã¼ãã©ã¯ãï¼³ï¼©ï¼°ï¼ã¤ã³ã¿ã¼ãããããã³ï¼©ï¼­ï¼³ï¼ãªãã³ã«Parlayä¸ã®ãã«ãã¡ãã£ã¢ããã³ãã«ããã¼ãã£ã³ã¼ã«å¶å¾¡ãå¯è½ã«ãããã¨ãã§ãããï¼­ï¼²ï¼¦ã®ï¼­ï¼²ï¼¦ï¼£æ©è½ã§ããã¡ãã£ã¢ãµã¼ãå¶å¾¡ã¤ãã¼ãã©ããã³é³å£°ã¢ã¯ã»ã¹ã¤ãã¼ãã©ã¯ãå¤æ§ãªvoiceXMLãµã¼ããï¼©ï¼¶ï¼²ãã¢ãã¦ã³ã¹ã¡ã³ããµã¼ããããã³ã¡ãã£ã¢ãµã¼ãï¼ãã¨ãã°ãMSMLãMSCMLãMSCPãããã³MGCPï¼ãå¶å¾¡ãããã¨ãã§ããããã

ã«ä½¿ããã¨ãã§ããªããã­ãã³ã«ã¯ï¼³ï¼©ï¼° ï¼¡ï¼³ä¸ã«ã¾ãã¯ï¼ªï¼£ï¼¡ï¼ï¼ï¼ãç¨ãã¦æ§ç¯å¯è½ã§ããã A set of enablers can be provided and implemented over SIP, Parlay, or IN protocols. These enablers can provide ready-to-use IMS location servers and SIP / SIMPLE location servers, including, for example, location enablers that conform to the OMA SIP / SIMPLE location, XDM and RLS enabler specifications. This can aggregate locations (eg, network locations) from other networks, provide an upstream ParlayX interface for applications, and use locations without participating in the location network. Location data can be modeled as location attributes using an extensible location data model. For example, the enabler may allow for multimedia and multi-party call control over SIP (Internet and IMS) and Parlay. The MRF MRFC functions Media Server Control Enabler and Voice Access Enabler can control various voiceXML servers, IVRs, announcement servers, and media servers (eg, MSML, MSCML, MSCP, and MGCP). Protocols that cannot be used immediately can be built on SIP AS or using JCA 1.5.

ã½ããã¦ã§ã¢ã¢ããªã±ã¼ã·ã§ã³ã¯ã³ãã³ããçºè¡ãã¦ãçµ±åã¦ã¼ã¶ãã­ãã¡ã¤ã«ï¼ï¼µï¼µï¼°ï¼ã«æ°ããã¢ã«ã¦ã³ããä½æãããã¨ãã§ãããï¼µï¼µï¼°æ§æè¦ç´ ã¯ãã¯ã¼ã¯ãã­ã¼ãèµ·åããããã¨ãã§ããããã¯éç¨ãµãã¼ãã·ã¹ãã ï¼ãã¸ãã¹ãµãã¼ãã·ã¹ãã ï¼ï¼¯ï¼³ï¼³ï¼ï¼¢ï¼³ï¼³ï¼ã¨å¯¾è©±ãã¦ï¼¯ï¼³ï¼³ï¼ï¼¢ï¼³ï¼³ææã®ãªãã¸ããªï¼ã¾ãã¯è¤æ°ã®ãªãã¸ããªï¼ã¸ã®æ´æ°ãéå§ããï¼ã¤ä»¥ä¸ã®ãã¸ãã¹ãã­ã»ã¹ãããªã£ã¦ããããï¼¯ï¼³ï¼³ï¼ï¼¢ï¼³ï¼³ãªãã¸ããªãä¸æ¦æ´æ°ãããã¨ãï¼µï¼µï¼°ã¯ãçµæã¨ãã¦çããï¼¯ï¼³ï¼³ï¼ï¼¢ï¼³ï¼³ãªãã¸ããªä¸­ã®æ´æ°ããã¼ã¿ããããã³ï¼µï¼µï¼°ï¼ã¾ãã¯ï¼µï¼µï¼°ã«ãã£ã¦å¯è¦ã®ï¼éç´ããå¾ãä»»æã®ä»ã®ãªãã¸ããªï¼ã«åæ ãããããã«ç¶ç¶ãããï¼µï¼µï¼°ã¯ä»ã®ãã¼ã¿ãªãã¸ããªã®ä»®æ³ãã¥ã¼ã§ããããããã¼ã¿ãæ´æ°ãããã¨ããã©ã«ãã®ãã¥ã¼ãæ´æ°ããããããã«ä»£ãã¦ããã¼ã¿ã¯åæãããï¼ãªãã¸ããªããè¤è£½ãããããã®ãããªç¶æ³ã§ãï¼¯ï¼³ï¼³ï¼ï¼¢ï¼³ï¼³ãªãã¸ããªã¨ï¼µï¼µï¼°ã¨ã®éã®ãã­ã»ã¹ã®èªååãçºçãããããããªãããããååã«èªååãããªããã°ãã¯ã¼ã¯ãã­ã¼ã¯ãç¢ºå®ã«ï¼µï¼µï¼°ã«å¤æ´ãæ­£ããåæ ãããããã«è¤è£½ãããªã¬ããå½¹å²ãæ ã£ã¦ããããã¢ããªã±ã¼ã·ã§ã³ãè¦ãæçµçµæã¯åãã§ããããä»»æã®å¯¾å¿ã®ã¢ã¯ã·ã§ã³ãã¯ã¼ã¯ãã­ã¼ã«ãã£ã¦æ±ããããå¥ã®ä»£æ¿ç­ã¯ãï¼³ï¼¯ï¼¡ãã¼ã¿ç®¡çè½åã§ãã¼ã¿ãã¼ã¹æ§æè¦ç´ ä¸­ã®ãã¼ã¿ãæ´æ°ããï¼µï¼µï¼°æ§æè¦ç´ ãæãããã¼ã¿ãã¼ã¹æ§æè¦ç´ èªä½ã¯ãï¼¯ï¼³ï¼³ï¼ï¼¢ï¼³ï¼³ã¨å¯¾è©±ãããã¸ãã¹ãã­ã»ã¹ãä½æããã¯ã¼ã¯ãã­ã¼ãããªã¬ãããã¨ãã§ããã Â Â The software application can issue a command to create a new account in the unified user profile (UUP). A UUP component can trigger a workflow that interacts with an operational support system / business support system (OSS / BSS) to initiate an update to an OSS / BSS owned repository (or multiple repositories). It may consist of more than one business process. Once the OSS / BSS repository is updated, the UUP is reflected in the data hub and UUP (or any other repository that can be visible / aggregated by the UUP) with the resulting updates in the OSS / BSS repository To continue. Since UUP is a virtual view of another data repository, when data is updated, the default view is also updated. Instead, the data is synchronized / replicated from the repository. In such situations, process automation occurs between the OSS / BSS repository and the UUP. However, if this is not fully automated, the workflow may be responsible for triggering replication to ensure that changes are correctly reflected in the UUP. The end result seen by the application is the same, but any corresponding action is handled by the workflow. Another alternative is to have a UUP component that updates the data in the database component with SOA data management capabilities, and the database component itself can trigger a workflow that creates a business process that interacts with the OSS / BSS. it can.

å³ï¼ã¯ãããªã·ã¼ã¨ã³ãã©ã¼ãµï¼ï¼°ï¼¥ï¼ãªãã³ã«ã¦ã§ããµã¼ãã¹ããã³ä»ã®ãã¤ã³ãã£ã³ã°ï¼ãã¨ãã°ãæ¨æºçãªä¸ãã¤ã³ã¿ã¼ãã§ã¤ã¹ï¼ãªã©ã®æ§æè¦ç´ ã®ä½¿ç¨ãéãã¦ãä»»æã®ãã¡ã¤ã³ï¼ï¼³ï¼°ãç«¯æ«ï¼ãã©ã®ããã«ï¼³ï¼¤ï¼°ãã¼ã¹ã®å®ç¾ä¾ï¼ï¼ï¼ãç¨ãã¦ãªãã¬ã¼ã¿ãç«¯æ«ããµã¼ãã¹ãã­ãã¤ããªã©ã®ä¸­ã®ãªã½ã¼ã¹ã«æ¥ç¶ã§ããããå³ç¤ºãããããªã·ã¼ã¨ã³ãã©ã¼ãµï¼ï¼ï¼ã¯ãï¼³ï¼¤ï¼°ãéãã¦ãã¹ã¦ã®ã¡ãã»ã¼ã¸ã«é¢ããããªã·ã¼ï¼æ¡ä»¶ã¨ã¢ã¯ã·ã§ã³ã¨ã®ä»»æã®çµåãï¼ãå®æ½ããã¨ã¨ãã«ããã¡ã¯ã¿ãã¸ãã¹ã«ã¼ã«ãé©ç¨ããããã³ï¼³ï¼¯ï¼¡ç·¨æãå®æ½ãããªã©ã®æ©è½ãå®è¡ãããã¨ãã§ããããã¡ã¤ã³ï¼ï¼ï¼å å¤ã®ã¢ããªã±ã¼ã·ã§ã³ã¾ãã¯ä»ã®ãªã½ã¼ã¹ã¯ãï¼³ï¼¤ï¼°ã®æ§æè¦ç´ ãéãã¦ãããã®ãªã½ã¼ã¹ãæ´»ç¨

ãããã¨ãã§ãããã¨ããã®ããï¼³ï¼¤ï¼°ã¯ããã¡ã¤ã³ãå å´ãã®ã¢ããªã±ã¼ã·ã§ã³ã¨ããã¡ã¤ã³ãå¤å´ãã®ç¬¬ä¸è ã¾ãã¯ä»ã®ã¢ããªã±ã¼ã·ã§ã³ã¨ã®éã®å¯¾è©±ãè¦å®ãããã¨ãã§ããããã§ãããï¼³ï¼¤ï¼°ã¯ãä»¥ä¸è«ãããããªãã¾ãã¾ãªã¤ãã¼ãã©ãªã©ã®æ§æè¦ç´ ï¼ï¼ï¼ããªãã³ã«ï¼ã¾ãã¯ä»¥ä¸ã«è«ããææã®åºæã®æ©è½æ§ãæããåä½¿ç¨å¯è½ãªããã³ï¼ãããã¯æ§æå¯è½ãªæ§æè¦ç´ ã§ããå¾ãParlayï¼¸ãããã¯Parlayï¼¡ï¼°ï¼©æ§æè¦ç´ ãå«ããã¨ãã§ãããæ§æè¦ç´ ï¼ï¼ï¼ã¯æ¬¡ã«ãï¼©ï¼­ï¼³ããã³éï¼©ï¼­ï¼³ãªã½ã¼ã¹ãªãã³ã«Parlayï¼ï¼¯ï¼³ï¼¡ãªã½ã¼ã¹ï¼ï¼§ï¼·ï¼ï¼¦ï¼·ï¼ï¼³ï¼£ï¼³ï½ï¼ããã³éParlayï¼ï¼¯ï¼³ï¼¡ãªã½ã¼ã¹ãªã©ã®ãªã½ã¼ã¹ã¨éä¿¡ãã¦ãç°ãªããããã¯ã¼ã¯ä¸ã®å®ç¾ä¾ãå ±å­ã§ããããã«ãããã¨ãã§ãããã¤ãã¼ãã©ã¨åãã¬ãã«ã§Parlayæ§æè¦ç´ ãç¨ãã¦ãããã¦ï¼³ï¼©ï¼°ä¸ã§å®ç¾ããï¼¯ï¼³ï¼¡ ï¼¡ï¼³ãå½¢æãããã¨ãã§ããã FIG. 2 illustrates how any domain (SP, terminal) can be SDP-based implementation through the use of components such as policy enforcers (PEs) and web services and other bindings (eg, standard upstream interfaces). It is illustrated whether 200 can be used to connect to resources in operators, terminals, service providers, and the like. Policy enforcer 202 can implement policies (any combination of conditions and actions) for all messages through SDP and perform functions such as applying factor business rules and implementing SOA organization. Applications or other resources inside and outside the domain 204 can leverage these resources through SDP components. This is because the SDP can define interactions between applications âinsideâ the domain and third parties or other applications âoutsideâ the domain. The SDP is a ParlayX or Parlay API configuration that may be a component 206 such as various enablers as discussed above, and / or a reusable and / or configurable component with the desired inherent functionality discussed below. Can contain elements. Component 206 then communicates with resources such as IMS and non-IMS resources as well as Parlay / OSA resources (GW / FW / SCSs) and non-Parlay / OSA resources so that implementations on different networks can coexist. be able to. It can thus be implemented on SIP using the Parlay component at the same level as the enabler to form an OSA AS.

å³ï¼ã¯ãå³ï¼ã®ï¼³ï¼¤ï¼°å®ç¾ä¾ã¨ã¨ãã«ç¨ãããã¨ãã§ããã¤ãã¼ãã©ï¼ï¼ï¼ã®ä¾ãå³ç¤ºããããã®ä¾ã§ã¯ãã¤ãã¼ãã©ï¼ï¼ï¼ã¯ãã³ã¼ã«å¶å¾¡ãæå¨ãã¡ãã»ã¼ã¸ã³ã°ãèª²éãã¡ãã£ã¢ãµã¼ãå¶å¾¡ãé³å£°ã¢ã¯ã»ã¹ãçµ±åã¦ã¼ã¶ãã­ãã¡ã¤ã«ï¼ï¼µï¼µï¼°ï¼ã®æä¾ããªã½ã¼ã¹ç®¡çãªã©ã®æç¨ãªåºæã®æ©è½ãå ¬éãããã¨ãã§ããåä½¿ç¨å¯è½ãªããã³ï¼ã¾ãã¯æ§æå¯è½ãªï¼ªï¼ï¼¥ï¼¥ï¼Sun Microsystems, Inc.ããå ¥æå¯è½ãªJavaï¼ç»é²åæ¨ï¼ï¼ä¼æ¥­çï¼ãªãã¸ã§ã¯ãã§ãããã¤ãã¼ãã©ã¯ããã¨ãã°Javaï¼ç»é²åæ¨ï¼ããã³ï¼ã¾ãã¯ã¦ã§ããµã¼ãã¹ã®ããã®æ¨æºåä¸ãï¼¡ï¼°ï¼©ãå©ç¨ãããã¨ãã§ãããããã¯ã¼ã¯ããã³ãã©ãããã©ã¼ã è¦ç´ ã¸ã®ã¢ããã¿ãä»ãã¦ãªã½ã¼ã¹ãååºãã¦ãäºæ¸¬å¯è½ãªä½ãå¾ ã¡æéããã³é«ãã¹ã«ã¼ãããã®ããã®ã¬ã·ãããï¼³ï¼©ï¼°ã¾ãã¯ï¼ªï¼£ï¼¡ï¼ï¼ï¼ãªã©ã®ãããã¯ã¼ã¯ååºããã©ãããã©ã¼ã æ½åºãããã³æ¨æºæè¡ã«ä¸ãããã¨ãã§ãããã¤ãã¼ãã©ã¯ãæ°¸ç¶æ§ãé«ãå©ç¨å¯è½æ§ãç®¡çãã­ã®ã³ã°ãæä¾ãããã¨ãã§ãããã¤ãã¼ãã©ãã¬ã¼ã ã¯ã¼ã¯ï¼ï¼ï¼ã¾ãã¯å ±éã®æ©è½æ§ã®çµã®ä¸é¨ã§ãããå¾ããã¾ãã¯ããã«åºã¥ãå¾ãã Â Â FIG. 3 illustrates an example of an enabler 300 that can be used with the SDP implementation of FIG. In this example, enabler 300 can reuse useful unique features such as call control, location, messaging, billing, media server control, voice access, unified user profile (UUP) provisioning, resource management, etc. A possible and / or configurable J2EE (JavaÂ® 2 Enterprise Edition available from Sun Microsystems, Inc.) object. Enablers can utilize standardized up APIs, for example for Java and / or web services, take resources through adapters to network and platform elements, and have predictable low latency and high Recipes for throughput can be provided to network retrieval, platform extraction, and standard techniques such as SIP or JCA1.5. The enabler can also be part of or based on the enabler framework 302 or a common set of functionality that can provide persistence, high availability, management, logging.

ã¤ãã¼ãã©ããã³ã¤ãã¼ãã©ãã¬ã¼ã ã¯ã¼ã¯ã¯ãé»è©±éä¿¡ã¢ããªã±ã¼ã·ã§ã³ãµã¼ãã¹ã®æä¾ãç¬¬ä¸è ããã³ï¼ã¾ãã¯ç¬¬ä¸è ã²ã¼ãã¦ã§ã¤ã¸ã®ã¦ã§ããµã¼ãã¹ã®å ¬éã®æä¾ããªãã³ã«éä¿¡ä¼ç¤¾ã°ã¬ã¼ãï¼¢ï¼°ï¼¥ï¼¬ï¼ï¼³ï¼¯ï¼¡ãªã©ã®æ©è½æ§ãå«ããï¼¢ï¼°ï¼¥ï¼¬ã«ãããããªã·ã¼é©ç¨ããã³ç·¨æã®å®ç¾ä¾ã®æä¾ã«å¯¾ããï¼³ï¼¤ï¼°ãã¼ã¹ã®æ¹ç­ãéãã¦ï¼³ï¼¯ï¼¡ã®ä½¿ç¨ãæä¾ãããã¨ãã§ãããã¤ãã¼ãã©ãã¬ã¼ã ã¯ã¼ã¯ã¯ãã«ã¼ã«ã¾ãã¯ããªã·ã¼ï¼ï¼°ï¼¤ï¼°ï¼ã®ä½¿ç¨ããªãã³ã«ï¼¢ï¼¡ï¼­ããã³Studioãªã©ã®æè¡ï¼ï¼³ï¼£ï¼¥ï¼ãµã¼ãã¹ä½æç°å¢ï¼ãæä¾ãããã¨ãã§ãããã¤ãã¼ãã©ãã¬ã¼ã ã¯ã¼ã¯ã®ä½¿ç¨ã¯ãï¼¢ï¼°ï¼¥ï¼¬ãã«ã¼ã«ã¨ã³ã¸ã³ãOracleã¦ã§ããµã¼ãã¹ããã¼ã¸ã£ï¼ï¼¯ï¼·ï¼³ï¼­ï¼ãªã©ãå©ç¨ããããã«ï¼³ï¼¯ï¼¡ãã¼ã¹ã®ã¢ã¼ã­ãã¯ãã£ä¸ã§å®ç¾å¯è½ãªãOSE PEãOMA PEEMãIETF PDP/PEPã3PGWãã¾ãã¯å å ¥è ï¼§ï¼·ããªã·ã¼ãªã©ã®ãã¾ãã¾ãªããªã·ã¼ãé©ç¨å¯è½ã«ãããã¨ãã§ãããï¼¢ï¼°ï¼¥ï¼¬ã ãã§ãªãããã¾ãã¾ãªä»ã®ã«ã¼ã«ãã¹ã¯ãªãããªã©ãå«ãä»»æã®ãã­ã»ã¹å®è¡è¨èªãç¨ãããã¨ãã§ãããã¤ãã¼ãã©ã¯ãï¼¯ï¼³ï¼³ï¼ï¼¢ï¼³ï¼³ï¼ï¼³ï¼¤ï¼°çµ±åãä¸ãããã¨ãã§ããï¼·ï¼³ãï¼¥ï¼³ï¼¢ãï¼³ï¼¯ï¼¡ãªã©ã®æ©è½æ§ãä¸ããã Â Â The enabler and enabler framework is a policy in BPEL that includes the provision of telephony application services, the provision of web services publishing to third parties and / or third party gateways, and functionality such as carrier grade BPEL / SOA. The use of SOA can be provided through an SDP-based strategy for providing application and organization implementations. The enabler framework can also provide the use of rules or policies (PDP) and technologies such as BAM and Studio: SCE (Service Creation Environment). Enabler framework usage can be implemented on SOA-based architectures such as BPEL, Rule Engine, Oracle Web Service Manager (OWSM), etc., OSE PE, OMA PEEM, IETF PDP / PEP, 3PGW, or subscription Various policies such as a user GW policy can be applied. Any process execution language can be used, including not only BPEL, but also various other rules, scripts, and the like. Enablers can also provide OSS / BSS / SDP integration and provide functionality such as WS, ESB, SOA.

ä»¥ä¸è«ããããã«ããã®ãããªæ¹ç­ã¯ãï¼©ï¼­ï¼³ããã³ã¬ã¬ã·ã¼ãããã¯ã¼ã¯ãªã©ã®ãããã¯ã¼ã¯ã¨ã®çµ±åãä¸ãããå³ï¼ã¯ãï¼ã¤ã®å®æ½å½¢æ ã«å¾ãï¼ã¤ã®ãã®ãããªå®ç¾ä¾ã®ä¾ï¼ï¼ï¼ãå³ç¤ºããããã®ä¾ã§ã¯ãä¸è¿°ã®ãããªï¼³ï¼¤ï¼°ãå©ç¨ãããµã¼ãã¹å±¤ã§ã®ã¢ããªã±ã¼ã·ã§ã³ããã³ã¤ãã¼ãã©ã¯ãæ¬æç´°æ¸ä¸­ã®ã©ããã§è«ãããããªã¢ããã¿ã¾ãã¯çµ±åãã¬ã¼ã ã¯ã¼ã¯ï¼ï¼ï¼ãéãã¦ãï¼©ï¼­ï¼³ãªã½ã¼ã¹ï¼ï¼ï¼ãï¼³ï¼©ï¼°ãªã½ã¼ã¹ï¼ï¼ï¼ãããã³ã¬ã¬ã·ã¼ã¾ãã¯ä»ã®ãããã¯ã¼ã¯ãªã½ã¼ã¹ï¼ï¼ï¼ãªã©ã®ãªã½ã¼ã¹ã«ã¢ã¯ã»ã¹ãããã¨ãã§ããããã¬ã¼ã ã¯ã¼ã¯ï¼ï¼ï¼ã¯ãï¼³ï¼©ï¼°ãªã½ã¼ã¹ã«ã¢ã¯ã»ã¹ããï¼³ï¼©ï¼°ã¢ããªã±ã¼ã·ã§ã³ãµã¼ãã¹ãããã³ï¼Parlayãï¼ï¼©ï¼®ãã­ãã³ã«ã¸ã®ï¼ï¼ªï¼£ï¼¡ãªã©ãç¨ããï¼ä»ã®ãããã¯ã¼ã¯ãªã½ã¼ã¹ã«ã¢ã¯ã»ã¹ããï¼¯ï¼³ï¼¡ã¢ããªã±ã¼ã·ã§ã³ãµã¼ãã¹ãå«ããã¨ãã§ããï¼³ï¼©ï¼° ï¼¡ï¼³ããã³ï¼¯ï¼³ï¼¡ ï¼¡ï¼³ã®ä¸¡æ¹ãç¨ãã¦ããã¨ãã°ï¼³âï¼£ï¼³ï¼£ï¼¦ãªã©ã®ï¼©ï¼­ï¼³ãªã½ã¼ã¹ã«ã¢ã¯ã»ã¹ãããã¨ãã§ããããã®ãããªå®ç¾ä¾ã¯ãæ°ããªã¾ãã¯ä»å çãªãããã¯ã¼ã¯ã¸ã®ã¹ã ã¼ãºãªç§»è¡ã¨ã¨ãã«ããããã¯ã¼ã¯ã«ããããªã½ã¼ã¹ã®å ±å­ãæä¾ããããã®ãã

ãªå®ç¾ä¾ã¯ãããã¯ã¼ã¯ååºãä»ããåæãæä¾ãããã¨ãã§ããä»»æã®ãããã¯ã¼ã¯ä¸ã®ãµã¼ãã¹ãªãã³ã«ï¼³ï¼°ãã¡ã¤ã³ãéããã¢ã¤ãã³ãã£ãã£ç®¡çããã³çã®åæã®ããã®å ±æçµ±åï¼¯ï¼³ï¼³ï¼ï¼¢ï¼³ï¼³ãå¯è½ã«ããã As discussed above, such a strategy provides integration with networks such as IMS and legacy networks. FIG. 4 illustrates an example of one such implementation 400 according to one embodiment. In this example, applications and enablers at the service layer that utilize SDP as described above may pass through IMS adapter 404, SIP resource 406, and legacy through adapter or integration framework 410 as discussed elsewhere herein. Alternatively, resources such as other network resources 408 can be accessed. Framework 410 can include SIP application services that access SIP resources, and OSA application services that access other network resources (using Parlay, JCA (to IN protocol), etc.), SIP AS and OSA AS. Both can be used to access IMS resources such as S-CSCF. Such an implementation provides for the coexistence of resources across the network with a smooth transition to new or additional networks. Such an implementation can also provide convergence via network retrieval, enabling shared integration OSS / BSS for services on any network and identity management and true convergence through the SP domain.

å³ï¼ã®ã¹ã¿ãã¯ï¼ï¼ï¼ã«å³ç¤ºãããããã«ãï¼³ï¼¤ï¼°ãä½¿ç¨ãããã¨ã«ãããï¼³ï¼¯ï¼¡ãã¼ã¹ã®å®ç¾ä¾ããããã¯ã¼ã¯æè¡ããã³ï¼ã¾ãã¯ãã³ãã¼ããç¬ç«ããé»è©±éä¿¡ï¼¡ï¼³ã«ç¨ãããã¨ãã§ããããã«ãªããè¦ãããããã«ãï¼°ï¼³ï¼´ï¼®ãã¯ã¤ã¤ã¬ã¹ãããã³ï¼©ï¼°ãããã¯ã¼ã¯æ§æè¦ç´ ãªã©ã®ãã¾ãã¾ãªãããã¯ã¼ã¯æ§æè¦ç´ ããã³ã²ã¼ãã¦ã§ã¤ï¼ï¼ï¼ãå­å¨ã§ããããããã¯ã¼ã¯ããã³ã²ã¼ãã¦ã§ã¤å±¤ï¼ï¼ï¼ã¯ããã¾ãã¾ãªæ§æè¦ç´ ããã³ã²ã¼ãã¦ã§ã¤ã¨éä¿¡ããããããããã¯ã¼ã¯ã¢ããã¿å±¤ï¼ï¼ï¼ã¨çµåãã¦ï¼ã¾ãã¯åãå±¤ã®ä¸é¨ã¨ãã¦ï¼ç¨ãããã¨ãã§ãããã¢ããªã±ã¼ã·ã§ã³ããã«ã¦ã§ã¢ï¼ï¼ï¼ã¯ããããã¯ã¼ã¯ã¢ããã¿å±¤ï¼ï¼ï¼ãå©ç¨ãã¦ããã¸ãã¹ã«ã¼ã«ããã³ç¹å®çãªãããã¯ã¼ã¯ã¨ã¯ç¬ç«ããéçºãé åãå®è¡ãããã³ç®¡çãªã©ã®æ©è½ãæä¾ãããã¨ãã§ãããæ¬¡ã«ï¼³ï¼¯ï¼¡ã¤ã³ãã©ã¹ãã©ã¯ãã£ããã³ãã¸ãã¹ã«ã¼ã«ã¯ãããã«ã¦ã§ã¢å±¤ã®ä¸ã®å±¤ï¼ï¼ï¼ã¨ãã¦æä¾å¯è½ã§ãããï¼°ï¼¥ãã«ã¼ã«ãç·¨æãï¼·ï¼³ï¼§ï¼·ï¼ï¼·ï¼³ã²ã¼ãã¦ã§ã¤ï¼ãªã©ã®æ©è½ãå«ããã¸ãã¹ã«ã¼ã«ããã³ï¼³ï¼¯ï¼¡ã®é©ç¨ãæä¾ããã Â Â As illustrated in the stack 500 of FIG. 5, the use of SDP allows an SOA-based implementation to be used for telephony AS independent of network technology and / or vendor. As can be seen, there can be various network components and gateways 502, such as PSTN, wireless, and IP network components. Network and gateway layer 504 can be used in combination with (or as part of the same layer) network adapter layer 506 to communicate with various components and gateways. Application middleware 508 can utilize network adapter layer 506 to provide functions such as development, deployment, execution, and management independent of business rules and specific networks. The SOA infrastructure and business rules can then be provided as a layer 510 on top of the middleware layer, providing business rules and SOA applications including functions such as PE, rules, organization, WSGW (WS gateway).

å³ï¼ã¯ãï¼ã¤ã®å®æ½å½¢æ ã«å¾ããï¼©ï¼­ï¼³ãï¼®ï¼§ï¼®ãã¤ã³ã¿ã¼ããããããã³ã¬ã¬ã·ã¼ãããã¯ã¼ã¯ã®æ§æè¦ç´ ãªã©ã®ãããã¯ã¼ã¯æ§æè¦ç´ ããã³ã²ã¼ãã¦ã§ã¤ï¼ï¼ï¼ã¨ã®çµ±åãæä¾ããã®ã«ç¨ãããã¨ãã§ããå±¤ç¶å®ç¾ä¾ã®å¥ã®ä¾ï¼ï¼ï¼ãå³ç¤ºããããã®ä¾ã§ã¯ããããã¯ã¼ã¯æ§æè¦ç´ ããã³ã²ã¼ãã¦ã§ã¤ï¼ï¼ï¼ã¯ããããã¯ã¼ã¯ããã³ã²ã¼ãã¦ã§ã¤å±¤ï¼ï¼ï¼ã®æ§æè¦ç´ ï¼ãã¨ãã°ãã¡ãã£ã¢ã²ã¼ãã¦ã§ã¤ãï¼§ï¼§ï¼³ï¼®ãï¼³ï¼§ï¼³ï¼®ï¼ã¨ã¨ãã«ãï¼©ï¼°ãã©ã³ã¹ãã¼ããã¬ã¼ã³ãå½¢æãããï¼©ï¼°ãã©ã³ã¹ãã¼ããã¬ã¼ã³ä¸ã«å¶å¾¡ãã¬ã¼ã³ï¼ï¼ï¼ãå½¢æãããã¨ãã§ããå¶å¾¡ãã¬ã¼ã³ã¯ãS-CSCFãI-CSCFãP-CSCFãHSSãHLRãããã³æ¬æç´°æ¸ä¸­ã®ã©ããã§è«ãããããªä»ã®æ§æè¦ç´ ãå«ãããã«ã¦ã§ã¢ããã³ã¢ããã¿ãå«ããæ¬¡ã«ãï¼³ï¼¯ï¼¡æ§æè¦ç´ ãªã©ã®æ§æè¦ç´ ãï¼¶ï½ï¼©ï¼°ããã³ï¼°ï¼¢ï¼¸ã¢ããªã±ã¼ã·ã§ã³ãªã©ã®ã¢ããªã±ã¼ã·ã§ã³ãã¤ãã¼ãã©ãã¬ã¼ã ã¯ã¼ã¯ããªãã³ã«å³ï¼ã«é¢ãã¦èª¬æããããã®ãªã©ã®ä»ã®æ§æè¦ç´ ãå«ããã¨ãã§ããããµã¼ãã¹ããã¬ã¼ã³ï¼ï¼ï¼ã®ä¸é¨ã¨ãã¦ãå¶å¾¡ãã¬ã¼ã³ä¸ã«ï¼³ï¼¤ï¼°ãé åãããã¨ãã§ããã Â Â FIG. 6 illustrates another example 600 of a layered implementation that can be used to provide integration with network components and gateways 602, such as IMS, NGN, Internet, and legacy network components, according to one embodiment. Is illustrated. In this example, network component and gateway 602 together with network and gateway layer 604 components (eg, media gateway, GGSN, SGSN) form an IP transport plane. A control plane 606 can be formed over the IP transport plane, which can be S-CSCF, I-CSCF, P-CSCF, HSS, HLR, and other as discussed elsewhere in this specification. Includes middleware and adapters that contain components. Next, a portion of a âserviceâ plane 608 that may include components such as SOA components, applications such as VoIP and PBX applications, enabler framework, and other components such as those described with respect to FIG. As above, SDP can be deployed on the control plane.

å³ï¼ã®ãµã¼ãã¹ãã¬ã¼ã³ã¯ï¼³ï¼©ï¼°ãµã¼ãã¬ããã³ã³ãããå«ã¿ããã­ã­ã·ãã¬ã¸ã¹ãã©ãããã³å ´æç¹å®æ©è½æ§ãªã©ã®æ©è½æ§ãæä¾ãããå³ï¼ã¯ãï¼ã¤ã®å®æ½å½¢æ ã«å¾ã£ã¦ç¨ãããã¨ãã§ãããã®ãããªï¼³ï¼©ï¼°ã³ã³ããã®ããã®ä¾ç¤ºçãªã¢ã¼ã­ãã¯ãã£ï¼ï¼ï¼ã®ä¾ãå³ç¤ºããããã®ãããªå®ç¾ä¾ãç¨ãã¦ï¼ã¤ã®å®æ½å½¢æ ã§éä¿¡ããã³ã¢ããªãã£ãµã¼ããæä¾ãããã¨ãã§ãããããç¨ãã¦ãé»è©±ãæºå¸¯é»è©±ãï¼°ï¼¤ï¼¡ãªã©ã®è£ ç½®ä¸ã§é»è©±éä¿¡ï¼¡ï¼³ãæä¾ãããã¨ãã§ãããã¢ã¼ã­ãã¯ãã£ã¯ãå¤æ°ã®ï¼³ï¼©ï¼°ã¤ã³ãã©ã¹ãã©ã¯ãã£ã¤ãã¼ãã©ï¼ï¼ï¼ãå«ãã§ç¤ºããããï¼ã¤ã®ãã®ãããªã¤ãã¼ãã©ã¯ãï¼³ï¼©ï¼°ï¼ï¼³ï¼©ï¼­ï¼°ï¼¬ï¼¥ãæå¨ãï¼¸ï¼¤ï¼­ãï¼²ï¼¬ï¼³ãããã³éç´ãªã©ã®æå¨æ å ±ãæä¾ããããã®æå¨ã¤ãã¼ãã©ã§ãããä»ã®ã¤ãã¼ãã©ã¯ãï¼³ï¼©ï¼°ã«ã¼ãã£ã³ã°ã®ããã®ãã­ã­ã·ãç¾å¨ã®ã¦ã¼ã¶æ å ±ã«å ¬éã¢ãã¬ã¹ããããã³ã°ããããã®ã¬ã¸ã¹ãã©ã¤ãã¼ãã©ãç¾å¨ã®ã¦ã¼ã¶ï¼³ï¼©ï¼°ãããã¯ã¼ã¯å ´æãå¤æ­ããããã®å ´æç¹å®ã¤ãã¼ãã©ãã¢ããªã±ã¼ã·ã§ã³ã«ã¼ã¿ãªã©ãå«ããã¨ãã§ãããã¢ã¼ã­ãã¯ãã£ã¯ããã¨ãã°ãï¼³ï¼©ï¼°ããã³ï¼¨ï¼´ï¼´ï¼°ãµã¼ãã¬ãããã¢ããªã±ã¼ã·ã§ã³ãªãã¸ã§ã¯ããä»ãã¦ã»ãã·ã§ã³ç¶æ ãå ±æã§ããããã«ããã¢ããªã±ã¼ã·ã§ã³ã»ãã·ã§ã³æ§æè¦ç´ ï¼ï¼ï¼ãå«ããã¢ã¼ã­ãã¯ãã£ã¯ãï¼¨ï¼´ï¼´ï¼°ãï¼³ï¼©ï¼°ããªãã³ã«å¿ è¦ã«å¿ãã¦ç®æ¨ãããã¯ã¼ã¯ããã³ã²ã¼ãã¦ã§ã¤æ§æè¦ç´ ã®ããã®ä»ã®ãã­ãã³ã«ã®ããã®ã³ã³ããããã³ãã­ãã³ã«æ§æè¦ç´ ãå«ããã¨ãã§ããã Â Â The service plane of FIG. 6 also includes a SIP servlet container, which provides functionality such as proxy, registrar, and location specific functionality. FIG. 7 illustrates an example of an exemplary architecture 700 for such a SIP container that can be used in accordance with one embodiment. Such an implementation can be used to provide a communication and mobility server in one embodiment, which can be used to provide telephony AS on devices such as phones, cell phones, PDAs and the like. The architecture is shown including a number of SIP infrastructure enablers 702. One such enabler is a location enabler for providing location information such as SIP / SIMPLE, location, XDM, RLS, and aggregation. Other enablers may include a proxy for SIP routing, a registrar enabler to map a public address to current user information, a location enabler to determine the current user SIP network location, an application router, etc. . The architecture also includes an application session component 704 that enables, for example, SIP and HTTP servlets to share session state via application objects. The architecture can also include containers and protocol components for HTTP, SIP, and other protocols for the target network and gateway components as required.

ï¼ã¤ã®å®æ½å½¢æ ã§ã¯ãå³ï¼ã®ï¼³ï¼©ï¼°ã³ã³ããã¯ãåæã¢ããªã±ã¼ã·ã§ã³ãµãã¼ãï¼ãã¨ãã°ã¯ãªãã¯ã»ãã¥ã»ã³ã¼ã«ï¼ãradiusãµãã¼ãï¼ãã¨ãã°ç¹åãããã­ã°ã¤ã³ã¢ã¸ã¥ã¼ã«ï¼ããªãã³ã«çµ±åãããï¼¡ï¼¡ï¼¡ãã¼ã¿ãã¼ã¹ããã³ï¼®ï¼¡ï¼´ã®ããã®ã»ãã·ã§ã³ãã©ãã¼

ãµã«ã¦ã¼ãã£ãªãã£ï¼ï¼³ï¼´ï¼µï¼®ï¼ãµãã¼ããæä¾ããï¼ªï¼³ï¼²âï¼ï¼ï¼ã¾ãã¯ï¼ªï¼³ï¼²âï¼ï¼ï¼æºæ ã³ã³ããã§ãããã³ã³ããã¯ãçªå·å¤æã®ããã®ï¼¥ï¼®ï¼µï¼­ï¼ï¼¥ï¼ï¼ï¼ï¼çªå·ãããã³ã°ï¼ãã¼ã¿ãã¼ã¹ã¨ã®çµ±åã®ããã®ãµãã¼ããä¸ãããã¨ãã§ãããã³ã³ããã¯ãDiameterï¼ï¼³ï½ãï¼²ï½ãï¼²ï½ãâ¦ï¼ã¨äºææ§ãããå¾ãLinuxï¼ç»é²åæ¨ï¼ãSUNãSolarisã

ï¼¨ï¼°ï¼µï¼¸ãï¼¡ï¼©ï¼¸ãã¦ã¤ã³ãã¦ãºï¼ç»é²åæ¨ï¼ãªã©ã®ãã©ãããã©ã¼ã ã«ãããå©ç¨å¯è½æ§ãæä¾ãããã¨ãã§ããã In one embodiment, the SIP container of FIG. 7 includes converged application support (eg, click to call), radius support (eg, specialized login module), and session traversal for integrated AAA database and NAT. A JSR-116 or JSR-289 compliant container that provides utility (STUN) support. The container may also provide support for integration with an ENUM (E.164 number mapping) database for number translation. Containers can be compatible with Diameter (Sh, Ro, Rf, ...), Linux (registered trademark), SUN, Solaris,

Availability across platforms such as HPUX, AIX, Windows, etc. can be provided.

ï¼ã¤ã®å®æ½å½¢æ ã§ã®ãã®ãããªéä¿¡ããã³ã¢ããªãã£ãµã¼ãã¯ãã¹ã±ã¼ã©ãã«ãã­ã­ã·ã¬ã¸ã¹ãã©ããã³ï¼¶ï½ï¼©ï¼°ã¢ããªã±ã¼ã·ã§ã³ã®ããã®å ´æç¹å®ãµã¼ãã¹ããªãã³ã«ãªãã©ã³ãã£ã³ã°å¯è½ï¼¶ï½ï¼©ï¼°ï¼æ åï¼ï¼©ï¼­ã¯ã©ã¤ã¢ã³ãã®ããã®ãµãã¼ããæä¾ãããã¨ãã§ããããµã¼ãã¯ãï¼©ï¼­ï¼³ã®æºåãã§ãã¦ãããï¼©ï¼­ï¼³ ï¼³ï¼©ï¼°ã¢ããªã±ã¼ã·ã§ã³ãµã¼ãããã³ï¼ã¾ãã¯ï¼©ï¼­ï¼³æå¨ãµã¼ãã¨ãã¦é åããå¾ããã¨ãã§ãããæå¨ãµã¼ãã¯ï¼³ï¼©ï¼°ï¼ï¼³ï¼©ï¼­ï¼°ï¼¬ï¼¥æºæ ã§ããå¾ãï¼¸ï¼¤ï¼­ï¼ï¼¸ï¼­ï¼¬ææ¸ç®¡çï¼ãï¼²ï¼¬ï¼³ï¼ãªã½ã¼ã¹ãªã¹ããµã¼ãï¼ãããã³æå¨éç´ãµãã¼ããæä¾ãããã¨ãã§ãããæå¨ãµã¼ãã¯ï¼¯ï¼­ï¼¡ï¼ãªã¼ãã³ã¢ãã¤ã«ã¢ã©ã¤ã¢ã³ã¹ï¼ããã³ï¼©ï¼­ï¼³æºæ ã§ãããã¨ãã§ããã Â Â Such a communication and mobility server in one embodiment may provide location specific services for scalable proxy registrars and VoIP applications, as well as support for rebrandable VoIP / video / IM clients. The server may also be deployed as an IMS SIP application server and / or an IMS location server that is ready for IMS. The location server can be SIP / SIMPLE compliant and can provide XDM (XML document management), RLS (resource list server), and location aggregation support. The location server can also be OMA (Open Mobile Alliance) and IMS compliant.

å³ï¼ã¯ãå³ï¼ã«é¢ãã¦è¨è¼ãããã®ã¨åæ§ã®ã¢ã¼ã­ãã¯ãã£ï¼ï¼ï¼ãå³ç¤ºãããããã®å ´åã¯ãï¼ã¤ã®å®æ½å½¢æ ã«å¾ããããã¯ã¼ã¯ã³ãã¯ãã£ããã£ãµã¼ãå®ç¾ä¾ã¾ãã¯ï¼¯ï¼³ï¼¡

ï¼¡ï¼³ç®æ¨ã¢ã¼ã­ãã¯ãã£ãæä¾ããããã®ä¾ã§ã¯ãèª²éãã¡ãã»ã¼ã¸ã³ã°ãã¡ãã£ã¢ãµã¼ãå¶å¾¡ãããã³é³å£°ã¢ã¯ã»ã¹ã¤ãã¼ãã©ãå«ããã¾ãã¾ãªä»ã®ã¤ãã¼ãã©ï¼ï¼ï¼ãè¨­ããããææã«ããä»ã®ãã¾ãã¾ãªçµåããæä¾ãããã¨ãã§ãããæå¨ã¤ãã¼ãã©ãç¨ãã¦ãParlayãä»ãã¦ï¼¨ï¼¬ï¼²ããã¦ã¼ã¶ã¹ãã¼ã¿ã¹ã¨ãã¦ãããã¯ã¼ã¯æå¨ãå ¬éãããã¨ãã§ããããã«ããã¼ãã£ã³ã¼ã«å¶å¾¡ã¤ãã¼ãã©ã¯ãParlayãï¼³ï¼©ï¼°ãããã³ãã®ä»ã®ããã«ç¨ãããã¨ãã§ããããã¨ãã°ãParlay5.1Javaï¼ç»é²åæ¨ï¼å®ç¾ããã³ParlayX2.1WSãå«ããã¨ãã§ããï¼¯ï¼³ï¼¡ ï¼¡ï¼³æ§æè¦ç´ ãè¨­ãããã¨ãã§ãããï¼¯ï¼³ï¼¡ ï¼¡ï¼³ã¯ã¬ã¬

ã·ã¼ããã³ï¼©ï¼­ï¼³äºææ§ãæä¾ãããã¨ãã§ããParlayã²ã¼ãã¦ã§ã¤ç»é²ãç®¡çããã¤ç¶­æãããã¨ãã§ãããï¼ªï¼£ï¼¡ï¼ï¼ï¼ã¢ããã¿ããªãã³ã«Parlayã²ã¼ãã¦ã§ã¤ï¼Corbaï¼ã

ãã³ä»ã®ãããã¯ã¼ã¯ãªã½ã¼ã¹ã¸ã®Parlayï¼ªï¼£ï¼¡ã¢ããã¿ãªã©ã®å¤æ°ã®ã¢ããã¿ãå«ããã¨ãã§ããã FIG. 8 illustrates an architecture 800 similar to that described with respect to FIG. 7, but in this case a network connectivity server implementation or OSA according to one embodiment.

Provide AS target architecture. In this example, various other enablers 802 are provided including billing, messaging, media server control, and voice access enablers, although various other combinations may be provided as desired. Using the location enabler, the network location can be disclosed as a user status from the HLR via Parlay. Multi-party call control enablers can be used for Parlay, SIP, and others. For example, an OSA AS component can be provided that can include a Parlay 5.1 Java implementation and ParlayX2.1WS. OSA AS can also provide legacy and IMS compatibility and can manage and maintain Parlay gateway registrations. A number of adapters may also be included, such as JCA 1.5 adapters, and Parlay JCA adapters to Parlay gateways (Corba) and other network resources.

ãã®ãããªãããã¯ã¼ã¯ã³ãã¯ãã£ããã£ãµã¼ãã«ãããä»æ¥ã®ãããã¯ã¼ã¯ä¸ã§å®è¡ãããæ¬¡ä¸ä»£ãããã¯ã¼ã­ã³ã°ï¼ï¼®ï¼§ï¼®ï¼ã¢ããªã±ã¼ã·ã§ã³ãéçºã§ããããã«ãªããã¬ã¬ã·ã¼ããï¼©ï¼­ï¼³ï¼ï¼©ï¼°ã¸ã®ã¹ã ã¼ãºãªãµã¼ãã¹ã®ç§»è¡ãä¸ããããããã¯ã¼ã¯é©ååå±¤ãå«ãããã¨ã«ãããä»»æã®ãªã½ã¼ã¹ã«æ¡å¼µå¯è½ãªParlayã²ã¼ãã¦ã§ã¤ã¸ã®ï¼ªï¼£ï¼¡ï¼ï¼ï¼ãã¼ã¹ã®æ¥ç¶æ§ãæä¾ãããParlayï¼Parlayï¼¸å®ç¾ï¼¡ï¼°ï¼©ãç¨ãããã¤ï¼ªï¼£ï¼¡ï¼ï¼ï¼ããã³ï¼³ï¼©ï¼°ä¸ã§åãï¼ªï¼ï¼¥ï¼¥ä¸­ã®ï¼¯ï¼³ï¼¡ ï¼¡ï¼³ãæä¾ããããå±¤ã¯ãã«ãã¢ããªã±ã¼ã·ã§ã³ãµã¼ããµãã¼ãããã³é«æ§è½ãæä¾ããããã¨ãã°ãå³ï¼ã¯ãï¼ã¤ã®å®æ½å½¢æ ã«å¾ãå³ï¼ã®ï¼¯ï¼³ï¼¡ ï¼¡ï¼³æ§æè¦ç´ ï¼ï¼ï¼ã®å®ç¾ä¾ã®å³ãå³ç¤ºããããã¯Parlay5.1Javaï¼ç»é²åæ¨

ï¼å®ç¾ï¼ï¼ªï¼ï¼¥ï¼¥ã­ã¼ã«ã«ï¼ããã³ParlayX2.1WSã«å³å¯ã«å¾ãããã®ãããªå®ç¾ä¾ã®ã¤ãã¼ãã©ãParlayï¼ªï¼²ï¼ï¼¸ã¨ä¸ãã¤ã³ã¿ã¼ãã§ã¤ã¹ãå ±æãå¾ãä¸æ¹ã§ãã¤ãã¼ãã©ã¯æ¬æç´°æ¸ä¸­ã®ã©ããã§è«ããããã«åã«Parlayæ§æè¦ç´ ä»¥ä¸ã®ãã®ã§ãããã¨ãã§ããã Such network connectivity servers allow the development of next-generation networking (NGN) applications running on today's networks, giving a smooth service transition from legacy to IMS / IP. The inclusion of a network adaptation layer provides JCA1.5-based connectivity to a Parlay gateway that can be extended to any resource, using the Parlay / ParlayX realization API, and in J2EE working on JCA1.5 and SIP OSA AS is provided. The layer also provides multi-application server support and high performance. For example, FIG. 9 illustrates a diagram of an example implementation of the OSA AS component 900 of FIG. 8 according to one embodiment, which strictly follows the Parlay 5.1 Java implementation (J2EE local) and ParlayX2.1WS. While an enabler of such an implementation may share an upstream interface with Parlay JR / X, the enabler can be more than just a Parlay component as discussed elsewhere herein.

è«ããããã«ããã®ãããªæ¹ç­ãç¨ãã¦ãå¤æ°ã®ç°ãªãã¢ããªã±ã¼ã·ã§ã³ããã³æè¡ã«ãã£ã¦å©ç¨å¯è½ãªé»è©±ã¢ããªã±ã¼ã·ã§ã³ãµã¼ãã¹ãæä¾ãããã¨ãã§ãããï¼ã¤ã®ä¾ã§ã¯ããã¾ãã¾ãªå®æ½å½¢æ ã«å¾ã£ã¦å®ç¾ä¾ãæ´»ç¨ããï¼¶ï½ï¼©ï¼°ã¢ããªã±ã¼ã·ã§ã³ãæä¾ãããã¨ãã§ããããã¨ãã°ãå³ï¼ï¼ã¯ãï¼¶ï½ï¼©ï¼°ã¢ããªã±ã¼ã·ã§ã³ï¼ï¼ï¼ï¼ã®ããã®ã¤ã³ã¿ã¼ãã§ã¤ã¹ï¼ï¼ï¼ï¼ãããªãã¬ã¼ã¿ãªã©ã®ã¦ã¼ã¶ãã·ã¹ãã ã«ã¢ã¯ã»ã¹ããããå©ç¨ã§ããããã«ãã¦ã½ããï¼¶ï½ï¼©ï¼°ï¼æ åã¯ã©ã¤ã¢ã³ããã¿ã¼ããã«ã¢ããã¿ãããã³ç¬¬ä¸è ã½ããã¯ã©ã¤ã¢ã³ããªã©ã®è£ ç½®ã¨éä¿¡ã§ããããã«ç¤ºãããä¾ï¼ï¼ï¼ï¼ãå³ç¤ºããããã®ãããªï¼¶ï½ï¼©ï¼°ã¢ããªã±ã¼ã·ã§ã³ã¯ãã¸ã§ããã®é¸æè¢ãæ§æãã¦ãé³å£°éè©±ãæ åéè©±ããª

ã¼ãã£ãªã¡ãã»ã¼ã¸ã³ã°ãå«ãã¤ã³ã¹ã¿ã³ãã¡ãã»ã¼ã¸ã³ã°ãã³ã¼ã«å±¥æ­´ãã«ã¹ã¿ã æå¨å å ¥ããã³å ¬éãæå¨ããªã·ã¼ç®¡çãè¤æ°ã¢ã«ã¦ã³ãç®¡çãé£çµ¡å ãªã¹ãç®¡çãã«ã¹ã¿ã ã¤ã³ã¹ãã¼ã©ããã©ã³ãã£ã³ã°ãããã¹ã­ã³ããã³ãã¼ãããªãã³ã«ï¼§ï¼ï¼ï¼ï¼ãï¼§ï¼ï¼ï¼ï¼ãï¼¨ï¼ï¼ï¼ï¼ãããã³ï¼¨ï¼ï¼ï¼ï¼ãå«ãé«åè³ªãªã¼ãã£ãªããã³ãããªã³ã¼ããã¯ãªã©ã®æ©è½ãæä¾ãããã¨ãã§ãããï¼¶ï½ï¼©ï¼°ã¢ããªã±ã¼ã·ã§ã³ã¯ï¼³ï¼¤ï¼°ä¸ã§æ¡å¼µå¯è½ã§ãããå¾ãæå¨ããã³ã¤ã³ã¹ã¿ã³ãã¡ãã»ã¼ã¸ã³ã°ï¼ãã¨ãã°ãæå¨ï¼ï¼¶ï½ï¼©ï¼°ï¼æ åãæå¨ï¼ï¼¶ï½ï¼©ï¼°ï¼æ åï¼³ï¼©ï¼°âï¼¸ï¼ï¼ã¨ã®ç¸äºéç¨ãããã³æå¨ï¼ï¼¶ï½ï¼©ï¼°ï¼ï¼°ï¼³ï¼´ï¼®ä¸ã®çµç«¯ï¼éè©±çµäºï¼ï¼ãªã©ã®æ©è½ãæä¾ããããã®ãããªã¢ããªã±ã¼ã·ã§ã³ã¯ãå ¥å¼ãï¼³ï¼­ï¼³çµäºãï¼³ï¼­ï¼³éå§ãï¼ã¤ã®å¼åºé³ãæ åã¡ã¼ã«ãå¼åºé³ãå ´æã«åºã¥ãï¼²ï¼¢ï¼´ãªã©ã®æ©è½æ§ãæä¾ãããã¨ãã§ããããã®ãããªï¼¶ï½ï¼©ï¼°ã¢ããªã±ã¼ã·ã§ã³ã¯ãï¼ªï¼ï¼¥ï¼¥ãªã©ã®æ¥­çæ¨æºãã©ãããã©ã¼ã ä¸ã«æ§ç¯ããã¦ã³ã¢ãã£ãã£ãã¼ãã¦ã§ã¢ä¸ã§å®è¡ããããåæ³ççè´ãã¯ã©ã¹ï¼ç¹å¾´ãï¼°ï¼³ï¼´ï¼®ããã³ãã¤ã¹ã¡ã¼ã«ã«ã¼ãã£ã³ã°ãã³ã¼ã«è»¢éãçºå¼è ãã©ã¤ãã·ã¼ããã³ï¼ãããã¯ã¢ã¤ãã³ãã£ãã£ãçä¿¡ããã³çºä¿¡ã³ã¼ã«ç¦æ­¢ãï¼°ï¼³ï¼´ï¼®ãã¬ãã£ãã¯ã¹ãï¼¥ï¼®ï¼µï¼­ã«ã¼ãã£ã³ã°ãã¢ãã¬ã¹å¤æãå°åçªå·ã«ã¼ãã£ã³ã°ãç·æ¥ãµã¼ãã¹ã«ã¼ãã£ã³ã°ãï¼¡ï¼£ï¼²ï¼ï¼¤ï¼£ï¼²ï¼è¦å¶ç¹å¾´ï¼ããªãã³ã«åæ³ççè´ï¼ï¼£ï¼¡ï¼¬ï¼¥ï¼¡ããã³åæ§ã®ãã®ï¼ãªã©ã®ç¹å¾´ãå«ããã¨ãã§ããã As discussed, such a strategy can be used to provide telephone application services that can be utilized by many different applications and technologies. In one example, a VoIP application can be provided that leverages the implementation according to various embodiments. For example, FIG. 10 illustrates that an interface 1002 for a VoIP application 1004 allows a user, such as an operator, to access and use a system, such as a soft VoIP / video client, a terminal adapter, and a third party soft client. 1 illustrates an example 1000 shown to be able to communicate with. Such a VoIP application constitutes a choice of widgets, voice calls, video calls, instant messaging including audio messaging, call history, custom location subscription and publishing, location policy management, multiple account management, contact list management, custom Installers, branded skins and themes, and G. 711, G.G. 729, H.C. 261, and H.I. Features such as high quality audio and video codecs including H.263 can be provided. VoIP applications can also be extensible over SDP and provide functions such as location and instant messaging (eg location + VoIP / video, interoperability with location + VoIP + video SIP-X10, and location + termination on VoIP + PSTN (call termination)) provide. Such an application may also provide functionality such as incoming call, SMS termination, SMS start, two ring tones, video mail, ring tones, location based RBT. Such VoIP applications are built on industry standard platforms such as J2EE and run on commodity hardware, legitimate eavesdropping, class 5 features, PSTN and voicemail routing, call forwarding, caller privacy and / or Or including features such as identity, incoming and outgoing call ban, PSTN prefix, ENUM routing, address translation, area number routing, emergency service routing, ACR / DCR (regulatory features), and lawful wiretapping (CALEA and the like) be able to.

å³ï¼ï¼ã¯å¥ã®ä¾ã«å¾ãå®ç¾ä¾ï¼ï¼ï¼ï¼ãå³ç¤ºããããã§ã¯é»è©±éä¿¡ï¼¡ï¼³ãä»ãã¦ä»®æ³ï¼°ï¼¢ï¼¸æ©è½æ§ãæä¾ããããã®ãããªã¢ããªã±ã¼ã·ã§ã³ã¯ããã¨ãã°ä¼æ¥­ã¦ã¼ã¶ã«ï¼©ï¼°ãã¼ã¹ã®ããã³ãã¹ãã£ã³ã°ãããï¼°ï¼¢ï¼¸ãµã¼ãã¹ãæä¾ãããã¨ãã§ããããã®ãããªã¢ããªã±ã¼ã·ã§ã³ã¯ããã¸ã§ããã®é¸æè¢ãæ§æãã¦ï¼ªï¼ï¼¥ï¼¥ãªã©ã®æ¥­çæ¨æºãã©ãããã©ã¼ã ä¸ã«æ§ç¯ãããã³ã¢ãã£ãã£ãã¼ãã¦ã§ã¢ä¸ã§å®è¡ããããµã¼ãã¹ã®ã«ã¹ã¿ãã¤ãºãæä¾ãããã¢ãã³ãã³ãå¾ ã¡è¡åãé æ¬¡çä¿¡ã°ã«ã¼ããèªåã¢ãã³ãã³ããäº¤æå°ã¯ã©ã¤ã¢ã³ããå å ¥è èªå·±éå¶ç®¡çããã©ã³ãã£ã³ã°ãå å ¥è å©ç¨å¯è½æ§ç®¡çãã¤ã³ã¿ã¼ãã§ã¤ã¹æä¾ãããã³ã¬ãã¼ãä½æãªã©ã®æ©è½æ§ãæä¾ãããã¨ãã§ããã Â Â FIG. 11 illustrates an implementation 1100 according to another example, which provides virtual PBX functionality via telephony AS. Such applications can provide, for example, IP-based and hosted PBX services to enterprise users. Such applications are built on industry-standard platforms such as J2EE, configuring bidet options, run on commodity hardware, and provide service customization, attendant queues, sequential incoming groups, auto attendants, Functionalities such as switchboard clients, subscriber self-management, branding, subscriber availability management, interface provisioning, and reporting can be provided.

ã¤ãã¼ãã©ã¾ãã¯ã¢ããªã±ã¼ã·ã§ã³ãªã©ã®ãã©ãããã©ã¼ã ã«ãã£ã¦å ¬éããããã¾ãã¾ãªç¹å¾´ã¯ãï¼³ï¼¯ï¼¡ã¾ãã¯ï¼³ï¼¯ï¼¡ ï¼³ï¼£ï¼©ï¼­ãç¨ãã¦çµåãå¯è½ã§ãããï¼³ï¼¯ï¼¡ ï¼³ï¼£ï¼©ï¼­ãã¼ã¹ã®æ¹ç­ã«ããã¦ãä½¿ç¨ã¾ãã¯ï¼³ï¼¤ï¼°ã¯ããï¼³âï¼£ï¼³ï¼£ï¼¦ã®ä¸­ãã¾ãã¯ããããã¯ã¼ã¯ä¸­ãã¾ãã¯ï¼³ï¼©ï¼° ï¼¡ï¼³éå®ãä»ã®ã¤ãã¼ãã©ã¨ã®ãµã¼ãã¹ã¬ãã«æèï¼æ§æãæ¬ ãã¦ããä»ã®æ¹ç­ãä¸ããããµã¼ãã¹ã¬ãã«åºæã®ï¼³ï¼£ï¼©ï¼­æ©è½ã¯ãã¡ãã»ã¼ã¸ä¸ã§ã«ã¼ãã£ã³ã°ããã¢ããªã±ã¼ã·ã§ã³ãï¼ï¼³ï¼©ï¼°ã®ã¿ã®ããã®ï¼ï¼³ï¼©ï¼°ãµã¼ãã¬ããæ§æãã¤ãã¼ãã©ã®ï¼³ï¼¯ï¼¡æ§æãã¢ããªã±ã¼ã·ã§ã³æ§ç¯ãã­ãã¯ãããã¯ã¢ããªã±ã¼ã·ã§ã³ãããã³ï¼ã¾ãã¯ãµã¼ãã¹å±¤ä¸­ã®ã¢ããªã±ã¼ã·ã§ã³ãã£ã¹ãããã¨ãã¦æä¾å¯è½ã§ããããã®ããã«ããµã¼ãã¹ã¯ãï¼³ï¼¯ï¼¡ ï¼³ï¼£ï¼©ï¼­ã¾ãã¯ã¢ããªã±ã¼ã·ã§ã³ãã£ã¹ããããç¨ãã¦çµåãããã¨ã«ãã£ã¦ãå¼ã¹ã°å¿ããç¶æ ã§ãé©ç¨å¯è½ã§ããã Â Â Various features exposed by platforms such as enablers or applications can be combined using SOA or SOA SCIM. In the SOA SCIM-based strategy, use or SDP provides other strategies âin-S-CSCFâ or âin-networkâ or SIP AS-limited lacks service level context / configuration with other enablers. Service level specific SCIM functionality can be provided as an application that routes on messages, a SIP servlet configuration (for SIP only), an enabler SOA configuration, an application building block or application, and / or an application dispatch in the service layer is there. In this way, services can be applied âon the flyâ by combining them using SOA SCIM or application dispatch.

å³ï¼ï¼ã®ä¾ï¼ï¼ï¼ï¼ã§å³ç¤ºããããã«ãï¼ã¤ã®å®æ½å½¢æ ã§ã¯ãï¼©ï¼­ï¼³ã¨ã®ãã®ãããªæ©è½æ§ã®çµ±åãéæããããå³ã§ã¯ãããé»è©±éä¿¡ï¼¡ï¼³ãå®è¡ãããªãã°ãï¼¯ï¼£ï¼­ï¼³ï¼Oracleï¼ç»é²åæ¨ï¼éä¿¡ããã³ã¢ããªãã£ãµã¼ãï¼ã¯ï¼³ï¼¤ï¼°ã§ããããã®ãããªå®ç¾ä¾ã¯ã¢ããªã±ã¼ã·ã§ã³ãã£ã¹ãããããã³ã¬ã¸ã¹ãã©ï¼å ´æç¹å®è¤è£½ãæããï¼¶ï½ï¼©ï¼°ï¼ï¼¶ï¼°ï¼¢ï¼¸ãã¡ã¤ã³ãæä¾ãããã¨ãã§ããããã®ãããªé åã¯ï¼³âï¼£ï¼³ï¼£ï¼¦ã¸ã®ç¬¬ä¸è ç»é²ãæä¾ãããã¨ãã§ããããã¹ã¦ã®å ´åãï¼³âï¼£ï¼³ï¼£ï¼¦ã¯ä»åãã¡ãã»ã¼ã¸çµè·¯ä¸ã«ï¼³ï¼©ï¼° ï¼¡ï¼³ãå«ããï¼ããªãã¡é»è©±éä¿¡ãµã¼ãã¹ã¨ãã¦ï¼ãã¨ãè­å¥ããããã®ãããªé åã¨ã¨ãã«ï¼¶ï½ï¼©ï¼°ãç¨ããã¨ããã¨ãã°ï¼ªï¼ï¼¥ï¼¥ã§é»è©±éä¿¡ï¼¡ï¼³ãæä¾ãããã³ã¼ã«ï¼ï¼³ï¼£ï¼©ï¼­ï¼ï¼ï¼¶ï¼°ï¼¢ï¼¸ãã¢ããã¿ï¼ï¼ªï¼£ï¼¡ï¼ï¼ï¼ï¼ãã¾ãã¯ãããã¯ã¼ã¯ï¼§ï¼·ï¼ãã¨ãã°ï¼°ï¼©ï¼­ï¼§ï¼ä¸ã«ãã£ã¹ããããããï¼¶ï½ï¼©ï¼°ãµã¼ãã¹ãæä¾ãããï¼ªï¼ï¼¥ï¼¥æ§æè¦ç´ ã¨ãã¦ãï¼®ï¼§ï¼®ãã¬ã¬ã·ã¼ãªã½ã¼ã¹ãï¼ï¼©ï¼°ï¼âï¼°ï¼¢ï¼¸ããã³ï¼ï¼©ï¼°ï¼ã»ã³ãã¬ãã¯ã¹ããªãã³ã«ã«ã¹ã¿ã ç¹å¾´ã«çµ±åããããã«ãªããçµ±åã®æ¹æ³ã¯ãï¼©ï¼­ï¼³ã¸ã®éï¼©ï¼­ï¼³ ï¼³ï¼©ï¼°ã¢ããªã±ã¼ã·ã§ã³ã®ãã¾ãã¯ï¼©ï¼­ï¼³ããã³ã¬ã¬ã·ã¼ï¼ï¼°ï¼³ï¼´ï¼®ï¼ï¼©ï¼®ï¼ãããã¯ã¼ã¯ã¸ã®ãï¼³ï¼¤ï¼°ä¸

ã§ï¼ããªãã¡ã¤ãã¼ãã©ãä»ãã¦ï¼é»è©±éä¿¡ãµã¼ãã¹ãæä¾ããã¢ããªã±ã¼ã·ã§ã³ã®ãçµ±åãå¯è½ã«ããããã«ãæ¯è¼çãå æ¬çãã«ã§ããããªããªãããµã¼ãã¹ã¯ãããã¯ã¼ã¯ããååºãããããã§ãããã¢ããªã±ã¼ã·ã§ã³ã¯ã¦ã¼ã¶ãã¼ã¿ã¸ã®ã¢ã¯ã»ã¹ãå¿ è¦ã¨ãããããããªãããããã¯ãï¼ã¤ã®å®æ½å½¢æ ã§ã¯ããã¹ã¦ã®å å ¥è ãã¼ã¿ã®ä»®æ³ãã¥ã¼ãä¸ãããä»¥ä¸ã§è«ããçµ±åã¦ã¼ã¶æä¾ï¼ï¼µï¼µï¼°ï¼ãç¨ãã¦éæå¯è½ã§ããã As illustrated in example 1200 of FIG. 12, in one embodiment, such functionality integration with IMS is achieved. In the figure, OCMS (Oracle (R) communication and mobility server) is SDP if telephone communication AS is executed. Such an implementation can provide a VoIP / VPBX domain with application dispatch and registrar / location specific replication. Such a deployment may also provide third party registration with the S-CSCF. In all cases, the S-CSCF now identifies including a SIP AS on the message path (ie, as a telephony service). Using VoIP with such a deployment, for example, provides telephony AS in J2EE and provides VoIP service dispatched on call (SCIM) + VPBX, adapter (JCA1.5), or network GW (eg PIMG). As a J2EE component, it will integrate into NGN, legacy resources, (IP) -PBX and (IP) Centrex, and custom features. The method of integration enables the integration of non-IMS SIP applications to IMS or to IMS and legacy (PSTN / IN) networks that provide telephony services over SDP (ie via enabler) To be relatively âcomprehensiveâ. This is because the service is extracted from the network. The application may also require access to user data, which in one embodiment is achieved using the unified user provision (UUP) discussed above, which gives a virtual view of all subscriber data. Is possible.

å³ï¼ï¼ããå³ï¼ï¼ã¯ãæ¬çºæã«å¾ãã¢ããªã±ã¼ã·ã§ã³ãµã¼ããæãããã¾ãã¾ãªå®æ½å½¢æ ãå³ç¤ºãããå³ï¼ï¼ã¯ï¼©ï¼­ï¼³ä¸­ã®é»è©±éä¿¡ï¼ãã¬ã³ã ã¢ããªã±ã¼ã·ã§ã³ãµã¼ããå³ç¤ºããå³ï¼ï¼ã¯ã»ãã·ã§ã³ãã¼ãã¼ã³ã³ãã­ã¼ã«ï¼ï¼³ï¼¢ï¼£ï¼ãæããéï¼©ï¼­ï¼³ä¸­ã®é»è©±éä¿¡ï¼ãã¬ã³ã ã¢ããªã±ã¼ã·ã§ã³ãµã¼ããå³ç¤ºãããã¤å³ï¼ï¼ã¯ã»ãã·ã§ã³ãã¼ãã¼ã³ã³ãã­ã¼ã«ï¼ï¼³ï¼¢ï¼£ï¼ãæããªãéï¼©ï¼­ï¼³ä¸­ã®é»è©±éä¿¡ï¼ãã¬ã³ã ã¢ããªã±ã¼ã·ã§ã³ãµã¼ããå³ç¤ºãããå³ï¼ï¼ã¯åä¸ã®é åãå³ç¤ºããå³ï¼ï¼ã¯ã¯ã©ã¹ã¿ã®é åãå³ç¤ºããããããã®ï¼©ï¼­ï¼³ããã³éï¼©ï¼­ï¼³ãªãã·ã§ã³ããã³é åã®èå¯ãä¾ã¨ãã¦ã®ã¿æç¤ºããã Â Â FIGS. 16-20 illustrate various embodiments having an application server in accordance with the present invention. FIG. 16 illustrates a telephony / telecom application server in IMS, FIG. 17 illustrates a non-IMS telephony / telecom application server with session border control (SBC), and FIG. 18 illustrates session border control (SBC). Figure 2 illustrates a non-IMS telephony / telecom application server without). FIG. 19 illustrates a single deployment and FIG. 20 illustrates a cluster deployment. These IMS and non-IMS options and deployment considerations are presented as examples only.

ä¸è¨èª¬æã«å¾ã£ã¦ãï¼çµã®ãã¸ã§ãããï¼ä»¥ä¸ã«è«ããï¼åä½ç°å¢ã§ãã¾ãã¾ãªãã­ã°ã©ãã³ã°ã¢ãã«ä¸ã«æ§ç¯ãããã¨ãã§ãããåã ã®ãã¸ã§ããã¯ãå ¸åçãªä»ã®é»è©±éä¿¡æ©è½ã®ãµãã¼ãã«å¿ è¦ã¨ãããåºæ¬æ©è½ãè¡¨ããããããã¯ãã¨ãã°ä»¥ä¸ã®ã¨ããã§ããã Â Â In accordance with the above description, a set of widgets can be built on various programming models in an operating environment (discussed below). Each widget represents a basic function required to support typical other telephony functions. For example, they are as follows.

ï¼ï¼ ï¼è éã§ã³ã¼ã«ãä½æããã

ï¼ï¼ ï¼è éã§ã®ï¼ä½æãããã¾ãã¯æ¢å­ã®ï¼ã³ã¼ã«ãçµäºãããã 1) Create a call between two parties.

2) Terminate a call (made or existing) between two parties.

ï¼ï¼ ï¼ä½æãããã¾ãã¯æ¢å­ã®ï¼ã³ã¼ã«ã®åã ã®ã¬ãã°ãä¿®æ­£ããã

ï¼ï¼ ã³ã¼ã«ã®éç¥ãå¦çããããã³å¥ã®è ã«åããã¾ãã¯çµäºãããã 3) Modify each leg of the call (made or existing).

4) Handle call notifications and direct or terminate others.

ï¼ï¼ ã¡ãã£ã¢ãµã¼ãã»ãã·ã§ã³ãä½æãã¦ï¼è ããå¤ããã³ã¼ã«ã«æ··åããã

ï¼ï¼ ã¡ãã£ã¢ã»ãã·ã§ã³ã«ã³ã¼ã«ãå ããã 5) Create a media server session to mix more than two parties into a call.

6) Add a call to the media session.

ï¼ï¼ ã¡ãã£ã¢ã»ãã·ã§ã³ããã³ã¼ã«ãé¤ãã

ï¼ï¼ ã³ã¼ã«ãå¦çããï¼ãã¨ãã°ãæ¶é³ãæ¶é³è§£é¤ãå¤æãä¿çï¼ã 7) Remove the call from the media session.

8) Handle the call (eg, mute, unmute, convert, hold).

ï¼ï¼ ã¡ãã£ã¢ã»ãã·ã§ã³ãç®¡çããï¼ãã¨ãã°ãèª°ãè©±ãçªããæ¶é³ãï¼¤ï¼´ï¼­ï¼¦å¦çï¼ã Â Â 9) Manage media sessions (eg who speaks, silence, DTMF processing).

ï¼ï¼ï¼ å¯¾è©±ç®¡çï¼ãã¨ãã°ãï¼¤ï¼´ï¼­ï¼¦å¯¾è©±ï¼èªè­ã¾ãã¯å¯¾è©±èªè­ï¼ãã³ã¼ã«ã¾ãã¯ã¡ãã£ã¢ã»ãã·ã§ã³ã«ä¸ããã Â Â 10) Provide dialog management (eg, DTMF dialog / recognition or dialog recognition) to the call or media session.

ï¼ï¼ï¼ ã³ã¼ã«ãå¾ ã¡è¡åã«å ¥ããã

ï¼ï¼ï¼ ã³ã¼ã«å¾ ã¡è¡åãç®¡çããã 11) Place the call in a queue.

12) Manage the call queue.

ï¼ï¼ï¼ çªå·ãå¤æããã

ï¼ï¼ï¼ ç­ãã³ã¼ããææ¸¡ãã 13) Convert the number.

14) Hand a short code.

ï¼ï¼ï¼ ç·æ¥ã³ã¼ã«ãã«ã¼ãã£ã³ã°ããã

ï¼ï¼ï¼ ï¼çä¿¡ï¼çºä¿¡ï¼ã³ã¼ã«ãç¦æ­¢ããã 15) Route emergency calls.

16) Prohibit (incoming / outgoing) calls.

ï¼ï¼ï¼ ã¤ã³ã¹ã¿ã³ãã¡ãã»ã¼ã¸ã³ã°ã

ï¼ï¼ï¼ çºå¼è åç·è­å¥å¶éããã³çºå¼è ãã©ã¤ãã·ã¼ãå¯è½åããã 17) Instant messaging.

18) Enable caller line identification restrictions and caller privacy.

ï¼ï¼ï¼ çºå¼è åç·è­å¥æç¤ºãå¯è½åããã

ï¼ï¼ï¼ å¿åã®ã³ã¼ã«ãæå¦ããã 19) Enable caller line identification presentation.

20) Reject anonymous calls.

ï¼ï¼ï¼ è¿åãããã³ã¼ã«ãæå¦ããã

ï¼ï¼ï¼ ã³ã¼ã«è»¢éãå¯è½åããã 21) Reject the diverted call.

22) Enable call transfer.

ï½ï¼è©±ä¸­

ï½ï¼å¿ç­ãªã

ï½ï¼ç¡æ¡ä»¶

ï½ï¼å°éä¸è½

ï¼ï¼ï¼ ã³ã¼ã«è¨é²ãå¯è½åããã a. Busy b. No response c. Unconditional d. Unreachable 23) Enable call recording.

ï¼ï¼ï¼ ã³ã¼ã«ã®ï¼åæ³çï¼çè´ãå¯è½åããã

ï¼ï¼ï¼ ã³ã¼ã«ã®çä¿¡é³ãå¯è½åããã 24) Enable (legal) wiretapping of calls.

25) Enable ringtones for calls.

ï¼ï¼ï¼ ã³ã¼ã«ã®å¼åºé³ãé³´ããã

ï¼ï¼ï¼ ã¦ã¼ã¶ãã­ãã¡ã¤ã«ã«ã¢ã¯ã»ã¹ããã 26) Ring the call.

27) Access the user profile.

ï¼ï¼ï¼ ã¦ã¼ã¶æå¨ã«ã¢ã¯ã»ã¹ããã

ï¼ï¼ï¼ ãã¤ã¹ã¡ã¼ã«æ©è½ãå¯è½åããã 28) Access the user location.

29) Enable voicemail function.

ï¼ï¼ï¼ ã³ã¼ã«ï¼ã¤ãã³ãã®èª²éãéå§ããã

ï¼ï¼ï¼ ã³ã¼ã«ã¤ãã³ãã®èª²éãå§è¨ããã 30) Start billing for calls / events.

31) Entrust billing for call events.

ï½ï¼å æã

ï½ï¼å¾æã

ï¼ï¼ï¼ ã³ã¼ã«ã®èª²éãåæ­¢ããã a. Advance payment b. Postpay 32) Stop billing for calls.

ï¼ï¼ï¼ èª²éï¼åå®æ®é«éç¥ãå¾ãã

ï¼ï¼ï¼ æ®é«ããã§ãã¯ããã 33) Get billing / account balance notification.

34) Check balance.

ï¼ï¼ï¼ ã³ã¼ã«è©³ç´°ã¬ã³ã¼ãï¼ï¼£ï¼¤ï¼²ï¼çæãå¯è½åããã

ï¼ï¼ï¼ èª²éé¡ãã¨ã£ã¦ããã 35) Enable call detail record (CDR) generation.

36) Save the billing amount.

ï¼ï¼ï¼ ã¡ãã»ã¼ã¸ãéãã

ï¼ï¼ï¼ ã¡ãã»ã¼ã¸ãã«ã¼ãã£ã³ã°ããã 37) Send a message.

38) Route the message.

ï¼ï¼ï¼ ã¡ãã»ã¼ã¸ãå¤æããã

ï¼ï¼ï¼ ãã©ã¤ãã¼ãã³ã¼ã«ãããã¯ã¼ã¯ï¼ï¼¶ï¼°ï¼®ï¼ãå¯è½åããã 39) Convert the message.

40) Enable private call network (VPN).

ï¼ï¼ï¼ çºå¼è ï¼©ï¼¤ãå¾ãã

ï¼ï¼ï¼ ã¦ã¼ã¶ï¼ã¦ã¼ã¶æ©å¨ã®ããã®ç¶ç¶ä¸­ã®çºå¼è ï¼©ï¼¤ãå¾ãã 41) Obtain the caller ID.

42) Obtain the ongoing caller ID for the user / user equipment.

ï¼ï¼ï¼ ãããã¯ã¼ã¯ï¼ãããã¯ã¼ã¯æ©å¨ãé¸æããã

ï¼ï¼ï¼ ãããã¯ã¼ã¯ï¼ãããã¯ã¼ã¯æ©å¨ãçºè¦ããã 43) Select network / network equipment.

44) Discover network / network equipment.

ï¼ï¼ï¼ ä¸æãªå å ¥è çªå·ãå¯è½åããã

å®æ½å½¢æ ã§ã¯ãä¸è¨ãã¸ã§ããä¸­ã®æ©è½ãåä½¿ç¨å¯è½ãªæ§æè¦ç´ ï¼ãã¨ãã°ãï¼³ï¼©ï¼°ãµã¼ãã¬ããã¾ãã¯ï¼³ï¼¯ï¼¡ãµã¼ãã¹ã³ã¼ã«ã¤ãã¼ãã©ï¼ã¨ãã¦å®ç¾ãããæ©è½ãï¼³ï¼©ï¼°ãµã¼ãã¬ããä¸ã¾ãã¯ï¼©ï¼®ä¸ã§å®ç¾ãããã¨ãã§ããã 45) Enable unique subscriber numbers.

In the embodiment, the functions in the widget are realized as reusable components (for example, a SIP servlet or an SOA service call enabler). The function can also be realized on a SIP servlet or IN.

æ¬¡ã«ãï¼ã³ã¼ãã­ã¸ãã¯ã§ãã¾ãã¯ã©ã³ã¿ã¤ã ã§äºãã³ã³ãã¤ã«ããå¾ãï¼¢ï¼°ï¼¥ï¼¬ã®ãããªãã¸ãã¹ãã­ã»ã¹ãä»ãã¦ï¼ãã¸ã§ãããæ§æãããã Â Â The widget is then constructed (via a business process such as BPEL that can be precompiled in code logic or at runtime).

ä¼è­°éè©±ï¼¶ï½ï¼¢ï¼¸ã¾ãã¯é»è©±éä¿¡ã¯ã©ã¹ï¼ï¼ãã¨ãã°ä½å® ç¨ï¼¶ï½ï¼©ï¼°ï¼ãªã©ã®ã¢ããªã±ã¼ã·ã§ã³ã¯ãä»¥ä¸ã®ä¾ç¤ºçãªãã¸ã§ãããªã©ã®ãã¸ã§ããã®çµåãã¨ãã¦æ§ç¯å¯è½ã§ããã Â Â Applications such as conference call VpBX or telephony class 5 (eg, residential VoIP) can be constructed as a combination of bidets such as the following example bidets.

ï¼ï¼ä¼è­°

ï½ï¼ã³ã¼ã«ãåä¿¡ãããã 1. Meeting a. A call is received.

ï½ï¼ã³ã¼ã«ãå¯¾è©±ç®¡çãä»ãã¦å¦çãããã

ï½ï¼ç¬¬ï¼ã®ã³ã¼ã«ãã¡ãã£ã¢ã»ãã·ã§ã³ãä½æãã¦ãããã b. Calls are handled via dialog management.

c. The first call may create a media session.

ï½ï¼å¯¾è©±ã«ãã£ã¦ä»ã®èªè¨¼ãããã³ã¼ã«ãéãããæ¬¡ã«ã¡ãã£ã¢ã»ãã·ã§ã³ã«è¿½å ãããã Â Â Â Â d. Another authenticated call is sent by interaction and then added to the media session.

ï½ ï¼ã¡ãã£ã¢ã»ãã·ã§ã³ã¯ãæ··åãæ¶é³ãããã³ï¼¤ï¼´ï¼­ï¼¦å¦çãå®ç¾ããã

ï¼ï¼ï¼¶ï¼°ï¼¢ï¼¸ãï¼©ï¼°âï¼°ï¼¢ï¼¸

ï½ï¼ã³ã¼ã«ãåä¿¡ãããã e. The media session implements mixing, silencing, and DTMF processing.

2. VPBX, IP-PBX

a. A call is received.

ï½ï¼ã³ã¼ã«ãå¾ ã¡è¡åã«å ¥ããããã

ï½ï¼ç®¡çè ã«å¾ ã¡è¡åãéç¥ãããã b. A call is queued.

c. The administrator is notified of the queue.

ï½ï¼ç®¡çè ãå¾ ã¡è¡åãç®¡çããã³ã¼ã«ãåæ¹åä»ãããã

ï½ ï¼å¿ è¦ã«å¿ãã¦ã³ã¼ã«ãåæ¹åä»ããããã d. The administrator manages the queue and redirects the call.

e. Calls are redirected as needed.

ï½ï¼ï¼¶ï¼°ï¼°ï¼®ï¼çªå·å¤æï¼ãã¤ã¹ã¡ã¼ã«ï¼å¯¾è©±ç®¡çãè¿½å å¯è½ã§ããã

ï¼ï¼ä½å® ç¨é»è©±éä¿¡

ï½ï¼ã¯ã©ã¹ï¼ãµã¼ãã¹ãè¨è¼ã®ãã¸ã§ããã«ãã£ã¦ã«ãã¼ãããã f. VPPN / number conversion / voice mail / dialog management can be added.

3. Residential telephone communication a. Class 5 service is covered by the described widget.

ï¼ï¼ãããã¯ã¼ã¯ç¸äºä½ç¨ï¼ã»ãã·ã§ã³ãã¼ãã¼ã³ã³ãã­ã¼ã«ãã

ï½ï¼çä¿¡ã³ã¼ã«

ï½ï¼ã³ã¼ã«å¦çã«åãããã¨ãããã³

ï½ï¼ï¼å¥ã®ãããã¯ã¼ã¯ã§ï¼ã³ã¼ã«ãçæãããã¨ããå¶å¾¡ãããã®ã¨ãã¦è¦ãããã 4). Network interaction / session border control

a. Incoming call b. Directing to call processing; and c. Seems to control making a call (on another network).

å è¡æè¡ã«åãæ¬å®æ½ä¾ã®ããã¤ãã®å©ç¹ã¯ãï¼ï¼ï¼ã»ã¼ãã¹ã¦ã®ãããã¯ã¼ã¯æè¡ã«å¯¾ãã¦åããã¸ã§ãããä½¿ç¨å¯è½ã§ãããã¨ãï¼ï¼ï¼ãã¸ã§ããã®ï¼©ï¼´ï¼ï¼³ï¼¯ï¼¡éçºãï¼©ï¼´ãã©ãããã©ã¼ã ï¼ãã¨ãã°ï¼ªï¼¥ï¼¥ï¼ä¸ã§è¡ãªãããã¨ããã¤ï¼ï¼ï¼ï¼©ï¼´ãã¼ã«ï¼ãã¨ãã°ï¼¢ï¼°ï¼¥ï¼¬ã¹ã¿ã¸ãªï¼ãä»ãã¦ãã¸ã§ããã®ï¼©ï¼´ï¼ï¼³ï¼¯ï¼¡æ§æãå­å¨ã§ãããã¨ã§ããã Â Â Some advantages of this embodiment over the prior art are: (1) the same bidet can be used for almost all network technologies, (2) IT / SOA development of the bidet on the IT platform (eg JEE) And (3) the presence of a bidet IT / SOA configuration via an IT tool (eg BPEL Studio).

å³ï¼ï¼ã¯ãã¤ãã¼ãã©ããã³ç°ãªããããã¯ã¼ã¯ã¸ã®ã¢ããã¿ãç¨ãããï¼³ï¼¤ï¼°ãéããã¤ãã¼ãã©ããã³ã¢ããã¿ãéãã¦æ©è½æ§ãæä¾ããã¢ããªã±ã¼ã·ã§ã³ã®ãã¸ã§ãããå³ç¤ºãããï¼åããä»»æã®ï¼®åã®ãã¸ã§ãããã¢ããªã±ã¼ã·ã§ã³ãç¨ãããã¨ãã§ããã¾ãã¯ãã®ä¸­ã«çµå ¥ãããã¨ãã§ãããã¢ããªã±ã¼ã·ã§ã³ã¯ããã¸ã§ãããã¨ãã«çµåããçµ±åããã¾ãã¯ããã§ãªãå ´åã¯æ§æãããã¨ãã§ããããã¸ã§ããã®æ§æã¯ããã¨ãã°ã¦ã§ããµã¼ãã¹ãã¸ãã¹ãã­ã»ã¹å®è¡è¨èªï¼ï¼·ï¼³âï¼¢ï¼°ï¼¥ï¼¬ï¼ãªã©ã®ã¹ã¯ãªããï¼ã­ã¸ãã¯ã§å®ç¾å¯è½ã§ããããã¸ã§ããã¯ã¤ãã¼ãã©ãéãã¦ãµã¼ãã¹æä¾ãã©ãããã©ã¼ã ï¼ï¼³ï¼¤ï¼°ï¼ï¼ï¼­ï¼·ã«æ¥ç¶å¯è½ã§ãããã¤ãã¼ãã©ã¯ãåºç¤ã¨ãªããããã¯ã¼ã¯ãï¼¯ï¼³ï¼³ï¼ï¼³

ï¼¢ï¼³ãã¾ãã¯ï¼©ï¼´ãªã½ã¼ã¹ãé§åããï¼ã¤ä»¥ä¸ã®ã¢ããã¿ãæãããã¨ãã§ãããï¼³ï¼¤ï¼°ï¼ï¼­ï¼·å ã§ç´æ¥ã«ãã­ãã³ã«ãå ¬éãããã¨ã«ã®ã¿ã¤ãã¼ãã©ãç¨ãããã¨ãå¯è½ã§ãããç¬¬ï¼ã®ãã¸ã§ããã¯ã¤ãã¼ãã©ã¨ãéä¿¡å¯è½ã§ãããå¿ è¦ã«å¿ãã¦åãã¢ããã¿ãç¨ãããã¨ãã§ããããã¸ã§ããã¯ç°ãªããããã¯ã¼ã¯ä¸ã§æ©è½ãç¨ããªããã°ãªããªãã¾ãã¯æ··åããªããã°ãªããªãå¯è½æ§ãããããã®å ´åãç°ãªãã¢ããã¿ï¼ã¤ãã¼ãã©ã¤ã³ã¹ã¿ã³ã¹ãé¢ãã£ã¦ãããããã¨ãã°ããã¸ã§ããã¯ããã®ããã«ã©ã®ã¤ãã¼ãã©ã¤ã³ã¹ã¿ã³ã¹ãç¨ããã¹ãããå¤æ­ãã¦ãã¿ã¹ã¯ã¾ãã¯ï¼çµã®ã¿ã¹ã¯ããç¹å®çãªãããã¯ã¼ã¯ä¸ã§ï¼ãã¨ãã°ãã³ã¼ã«ãçºä¿¡ããããããã¯ã¼ã¯ä¸ã§ãã³ã¼ã«ãåãã£ã¦ãããããã¯ã¼ã¯ä¸ã§ãã¾ãã¯å å ¥è ãé¢é£ä»ãããã¦ããå ´æã§ï¼è¡ãªãï¼ãã¨ãã°ãµã¼ãã¹ãæä¾ããï¼ãã¨ããããããã¯ãã¨ããããæ­£ããã¤ãã¼ãã©ã¤ã³ã¹ã¿ã³ã¹ããã³ï¼ã¾ãã¯ã²ã¼ãã¦ã§ã¤ãé¸æãããã¨ã«ãã£ã¦ã³ã¼ã«ã®ã¬ãã°ãä½æãããã¨ãã§ãããããã¯ã¼ã¯ã®é¸æã§ãããã²ã¼ãã¦ã§ã¤ã¯ï¼ã¤ã®ãããã¯ã¼ã¯ããå¥ã®ãããã¯ã¼ã¯ã¸åªä½ãè»¢éãããã¨ãã§ãããã®ã§ããå¾ãããã¸ã§ããã¯ãã»ãã·ã§ã³ç¢ºç«ãã­ãã³ã«ï¼ï¼³ï¼©ï¼°ï¼ã¢ããªã±ã¼ã·ã§ã³ãµã¼ãï¼ï¼¡ï¼³ï¼ãç¨ãããã®ãå«ãè¤æ°ã®ã¤ãã¼ãã©ã¨ãéä¿¡å¯è½ã§ãããä»ã®ï¼¡ï¼³ç°å¢ããï¼©ï¼®ãParlayãããã³ä»ã®ãã­ãã³ã«ãç¨ãããã®ãªã©ãï¼³ï¼¤ï¼°ãéãã¦ãµã¼ãã¹æä¾ãåãããã¨ãã§ããã FIG. 15 illustrates a widget for an application that provides functionality through an enabler and adapter through SDP, using an enabler and an adapter to a different network. One to any N widgets can be used by or incorporated into the application. An application can combine, integrate, or otherwise configure a widget together. The configuration of the widget can be realized by a script / logic such as a web service business process execution language (WS-BPEL). The widget can be connected to a service providing platform (SDP) / MW through an enabler. Enabler is the underlying network, OSS / S

You can have one or more adapters that drive BS or IT resources. It is also possible to use the enabler only for publishing the protocol directly in SDP / MW. The second widget can also communicate with the enabler, and the same adapter can be used as needed. The widget may have to use or mix functions on different networks. In that case, different adapter / enabler instances may be involved. For example, the widget determines which enabler instance should be used to do so, and the call is directed to a task or set of tasks on a particular network (eg, on the network from which the call originated). (E.g. providing a service) on the network or where the subscriber is associated. This is, among other things, the selection of a network that can create a leg of a call by selecting the correct enabler instance and / or gateway. A gateway may be capable of transferring media from one network to another. The widget can also communicate with a plurality of enablers, including those using a session establishment protocol (SIP) application server (AS). Other AS environments can also be served through SDP, such as those using IN, Parlay, and other protocols.

ããã¤ãã®ãã¸ã§ããã¯ã©ã®ã¤ãã¼ãã©ã«ãæ¥ç¶ãããªããã¨ãããããå é¨ä½¿ç¨ã®ããã«ã¢ããªã±ã¼ã·ã§ã³ä¸­ã«å«ã¾ãã¦ããããé£æ¥ãããã¸ã§ããã¯ãå é¨æ©è½ããã³ã¢ããªã±ã¼ã·ã§ã³ã®ããã®ãã­ã»ã¹ãæä¾ãããã¨ãã§ããããã¸ã§ããã¯ãã¢ããªã±ã¼ã·ã§ã³ã«æç¨ãªæ©è½ãå®ç¾ããåä½¿ç¨å¯è½ãªæ§æè¦ç´ ã§ãããããã¤ãã®ãã¸ã§ããã¯ãæ¬å½ã¯çºå¼ããã¤ãã¼ãã©ã§ã¯ãªãããå¥åã®åä½¿ç¨å¯è½ãªç¨®é¡ã®ã¢ããªã±ã¼ã·ã§ã³ã¢ã¸ã¥ã¼ã«ã§ããå¾ ã¡è¡åãç®¡çããã¦ã§ãã¾ãã¯ã¡ãã»ã¼ã¸é§åã¤ã³ã¿ã¼ãã§ã¤ã¹ã®ãããªãã®ãæä¾ãã¦ãããã Â Â Some widgets may not be connected to any enabler, but may be included in the application for internal use. Adjacent widgets can provide processes for internal functions and applications. A widget is a reusable component that provides useful functionality for an application. Some widgets are not really enablers to call, but may provide something like a web or message-driven interface that manages a queue, a separate reusable type of application module.

ã¢ããªã±ã¼ã·ã§ã³ã¯ãè¦ç´ ãçµ±åããï¼¢ï¼°ï¼¥ï¼¬ã¾ãã¯ä»ã®ã¹ã¯ãªããï¼ã­ã¸ãã¯ã³ã¼ããå©ç¨ãããã¸ã§ããã®æ§æã§ããå¾ãããã¸ã§ããã¯ãã¢ããªã±ã¼ã·ã§ã³ã®ä¸é¨ã¨ãã¦å¾ç«¯ã§é»è©±éä¿¡ãµã¼ãã¹ãè«æ±æ¸ãµã¼ãã¹ãããã³ä»ã®æ©è½æ§ãæä¾ããããã«æ··åãããä¸è´ããå¾ããç¹å®ã®ãããã¯ã¼ã¯ãããã¸ã§ããããã³æ©è½æ§ãåé¢ãããã¨ã«ãããåãã¢ããªã±ã¼ã·ã§ã³ããå¤æ´ããã«ä»ã®ãããã¯ã¼ã¯ä¸ã§ä½¿ç¨ã§ããããã«ãããã¨ãã§ããã Â Â An application can be a widget configuration utilizing BPEL or other script / logic code that integrates elements. The widgets can be mixed and matched to provide telephony services, billing services, and other functionality at the back end as part of the application. By separating the widget and functionality from a particular network, the same application can be used on other networks without modification.

ããå®æ½å½¢æ ã§ã¯ãåæã«ï¼ã¤ä»¥ä¸ã®ãããã¯ã¼ã¯ä¸ã§ã¢ããªã±ã¼ã·ã§ã³ãä½¿ç¨ãããï¼ã¤ã®ãããã¯ã¼ã¯ã¯ã­ã¼ã«ã«ã¨ãªã¢ãããã¯ã¼ã¯ã§ããå¾ãå¥ã®ãã®ã¯å ¬è¡äº¤æé»è©±ç¶²ï¼ï¼°ï¼³ï¼´ï¼®ï¼ã§ããå¾ããåæã«ç°ç¨®ã®ãããã¯ã¼ã¯ã®ä¸¡æ¹ã§ã¢ããªã±ã¼ã·ã§ã³ããµã¼ãã¹æä¾ããã®ã§ãã¢ããªã±ã¼ã·ã§ã³ã¯åãããã¯ã¼ã¯ä¸ã§åãæ¯èãããããã¦ã¼ã¶ãã¢ããªã±ã¼ã·ã§ã³ãä½¿ç¨ããªããï¼ã¤ã®ãããã¯ã¼ã¯ããå¥ã®ãããã¯ã¼ã¯ã¸åæããå ´åãã¢ããªã±ã¼ã·ã§ã³ã¯ãå¿ç­ãéãããããåãã¡ã¢ãªç¶æ ãã­ã£ãã·ã¥ãã¼ã¸ãããã³ä»ã®å¾ç«¯ãµã¼ãå¹çã¡ã«ããºã ãç¨ãããã¨ãã§ããã Â Â In one embodiment, the application is used on more than one network at the same time. One network can be a local area network and another can be a public switched telephone network (PSTN). Since applications serve on both dissimilar networks at the same time, applications behave the same on each network. If a user switches from one network to another while using the application, the application can use the same memory state, cache page, and other trailing server efficiency mechanisms to speed up the response.

ã¢ããªã±ã¼ã·ã§ã³ãåæã«è¤æ°ã®ç°ç¨®ã®ãããã¯ã¼ã¯ã«å¯¾ãã¦åãå®æ½å½¢æ ã§ã¯ãæè¡è ã¯ãããå®¹æã«ãã©ãã«ã·ã¥ã¼ãã£ã³ã°ãè¡ãªããåé¡ããããã°ãããã¨ãã§ãããããããªããããè ã¯ï¼ã¤ã®ãããã¯ã¼ã¯ä¸ã§ã¢ããªã±ã¼ã·ã§ã³ã®æ©è½ããã¹ãããæ¬¡ã«ä»ã®ãããã¯ã¼ã¯ã§åãæ©è½ããã¹ããããã¨ãã§ãããåé¡ã®åãçç¶ãèµ·ããå ´åãæè¡è ã¯åé¡ãã¢ããªã±ã¼ã·ã§ã³ã«çµãè¾¼ããã¨ãã§ãããï¼ã¤ã®ãããã¯ã¼ã¯ä¸ã§çç¶ãç°ãªãå ´åãæè¡è ã¯ãã¢ããªã±ã¼ã·ã§ã³ã§ã¯ãªããããã¯ã¼ã¯ã«åé¡ãçµãããã®ãã©ãã«ã·ã¥ã¼ãã£ã³ã°ãèªååããã¦ãåé¡ã®å¤§ã¾ããªå¢çã¨ããããã¯ã¼ã¯ä¸ã¾ãã¯ã¢ããªã±ã¼ã·ã§ã³ä¸­ã§ç°å¸¸ãèµ·ãã£ã¦ãããå¦ãã¨ãå¤æ­ãããã¨ãã§ããã Â Â In embodiments where the application works against multiple disparate networks simultaneously, the technician may be able to troubleshoot and debug the problem more easily. One can test the functionality of an application on one network and then test the same functionality on another network. If the same symptoms of the problem occur, the technician can narrow down the problem to the application. If the symptoms are different on the two networks, the technician will focus on the network, not the application. This troubleshooting can also be automated to determine the general boundaries of the problem and whether an anomaly is occurring on the network or in the application.

åä½ç°å¢

å³ï¼ï¼ã¯ããã¾ãã¾ãªå®æ½å½¢æ ãå®ç¾ããå¾ãä¾ç¤ºçãªåä½ç°å¢ã®æ§æè¦ç´ ãå³ç¤ºãããã­ãã¯å³ã§ãããã·ã¹ãã ï¼ï¼ï¼ï¼ã¯ãå°ç¨ã¢ããªã±ã¼ã·ã§ã³ãã¦ã§ããã©ã¦ã¶ãªã©ã®ã¯ã©ã¤ã¢ã³ããåä½ããã®ã«ç¨ãããã¨ãã§ãããï¼ã¤ä»¥ä¸ã®ã¦ã¼ã¶ã³ã³ãã¥ã¼ã¿ãè¨ç®è£ ç½®ãã¾ãã¯å¦çè£ ç½®ï¼ï¼ï¼ï¼ãï¼ï¼ï¼ï¼ãï¼ï¼ï¼ï¼ãï¼ï¼ï¼ï¼ãå«ããã¨ãã§ãããã¦ã¼ã¶ã³ã³ãã¥ã¼ã¿ï¼ï¼ï¼ï¼ãï¼ï¼ï¼ï¼ãï¼ï¼ï¼ï¼ãï¼ï¼ï¼ï¼ã¯ãï¼åã«ä¾ç¤ºã®ããã«ãæ¨æºçãªãªãã¬ã¼ãã£ã³ã°ã·ã¹ãã ãå®è¡ãããã¼ã½ãã«ã³ã³ãã¥ã¼ã¿ããã³ï¼ãããã¯ã©ãããããã³ã³ãã¥ã¼ã¿ãå«ãï¼æ±ç¨ãã¼ã½ãã«ã³ã³ãã¥ã¼ã¿ãï¼ç§»åä½ã½ããã¦ã§ã¢ãå®è¡ããã¤ã³ã¿ã¼ããããé»å­ã¡ã¼ã«ãï¼³ï¼­ï¼³ããã©ãã¯ããªã¼ããããã¯ä»ã®éä¿¡ãã­ãã³ã«ã§å¯è½åãããï¼æºå¸¯é»è©±ãããã¯ï¼°ï¼¤ï¼¡ãããã³ï¼ã¾ãã¯ï¼éå®ããããã¨ãªããã¾ãã¾ãªï¼§ï¼®ï¼µï¼Linuxï¼ç»é²åæ¨ï¼ãªãã¬ã¼ãã£ã³ã°ã·ã¹ãã ãå«ãï¼ãã¾ãã¾ãªå¸

è²©ã®ï¼µï¼®ï¼©ï¼¸ï¼ç»é²åæ¨ï¼ãããã¯ï¼µï¼®ï¼©ï¼¸ï¼ç»é²åæ¨ï¼ã®ãããªãªãã¬ã¼ãã£ã³ã°ã·ã¹ãã ã®ãã¡ä»»æã®ãã®ãå®è¡ããã¯ã¼ã¯ã¹ãã¼ã·ã§ã³ã³ã³ãã¥ã¼ã¿ã§ããå¾ãããããã®ã¦ã¼ã¶ã³ã³ãã¥ã¼ã¿ï¼ï¼ï¼ï¼ãï¼ï¼ï¼ï¼ãï¼ï¼ï¼ï¼ãï¼ï¼ï¼ï¼ã¯ãï¼ã¤ä»¥ä¸ã®éçºã·ã¹ãã ããã¼ã¿ãã¼ã¹ã¯ã©ã¤ã¢ã³ãããã³ï¼ã¾ãã¯ãµã¼ãã¢ããªã±ã¼ã·ã§ã³ããªãã³ã«ã¦ã§ããã©ã¦ã¶ã¢ããªã±ã¼ã·ã§ã³ãå«ããã¾ãã¾ãªã¢ããªã±ã¼ã·ã§ã³ã®ä»»æã®ãã®ãæãã¦ããããããã«ä»£ãã¦ãã¦ã¼ã¶ã³ã³ãã¥ã¼ã¿ï¼ï¼ï¼ï¼ãï¼ï¼ï¼ï¼ãï¼ï¼ï¼ï¼ãï¼ï¼ï¼ï¼ã¯ããããã¯ã¼ã¯ï¼ãã¨ãã°å¾è¿°ããããããã¯ã¼ã¯ï¼ï¼ï¼ï¼ï¼ãä»ãã¦éä¿¡ããããã³ï¼ã¾ãã¯ã¦ã§ããã¼ã¸ãããã¯ä»ã®ç¨®é¡ã®é»å­ææ¸ãè¡¨ç¤ºããã¤ããã²ã¼ããããã¨ãã§ãããã·ã³ã¯ã©ã¤ã¢ã³ãã³ã³ãã¥ã¼ã¿ãã¤ã³ã¿ã¼ãããå¯è½åã²ã¼ã ã·ã¹ãã ãããã³ï¼ã¾ãã¯ãã¼ã½ãã«ã¡ãã»ã¼ã¸ã³ã°è£ ç½®ãªã©ã®ä»»æã®ä»ã®é»å­è£ ç½®ã§ãã£ã¦ããããä¾ç¤ºçãªã·ã¹ãã ï¼ï¼ï¼ï¼ãï¼ã¤ã®ã¦ã¼ã¶ã³ã³ãã¥ã¼ã¿ã¨ã¨ãã«ç¤ºãããããä»»æã®æ°ã®ã¦ã¼ã¶ã³ã³ãã¥ã¼ã¿ããµãã¼ãããã¦ãããã Operating Environment FIG. 13 is a block diagram that illustrates components of an exemplary operating environment in which various embodiments may be implemented. The system 1300 can include one or more user computers, computing devices, or processing devices 1312, 1314, 1316, 1318 that can be used to operate clients such as dedicated applications, web browsers, and the like. User computers 1312, 1314, 1316, 1318 are general-purpose personal computers (including personal computers and / or laptop computers that run standard operating systems for illustrative purposes only), mobile software, and Internet Mobile phone or PDA enabled by email, SMS, BlackBerry, or other communication protocols, and / or various (including but not limited to various GNU / LinuxÂ® operating systems) It can be a workstation computer running any of the commercially available operating systems such as UNIX (registered trademark) or UNIX (registered trademark). These user computers 1312, 1314, 1316, 1318 may also have any of a variety of applications including one or more development systems, database clients and / or server applications, and web browser applications. Alternatively, user computers 1312, 1314, 1316, 1318 communicate via a network (eg, network 1310, described below) and / or display and navigate web pages or other types of electronic documents. Any other electronic device, such as a thin client computer, an Internet-enabled gaming system, and / or a personal messaging device. Although exemplary system 1300 is shown with four user computers, any number of user computers may be supported.

å¤§é¨åã®å®æ½å½¢æ ã§ã¯ãã·ã¹ãã ï¼ï¼ï¼ï¼ã¯ãä½ããã®ç¨®é¡ã®ãããã¯ã¼ã¯ï¼ï¼ï¼ï¼ãå«ãããããã¯ã¼ã¯ã¯ãéå®ããããã¨ãªãï¼´ï¼£ï¼°ï¼ï¼©ï¼°ãï¼³ï¼­ï¼¡ãï¼©ï¼°ï¼¸ãAppleTalk

ãªã©ãå«ããã¾ãã¾ãªå¸è²©ã®ãã­ãã³ã«ã®ãã¡ä»»æã®ãã®ãç¨ãã¦ãã¼ã¿éä¿¡ããµãã¼ããããã¨ãã§ãããå½æ¥­è ã«ã¯é¦´æã¿ã®ããä»»æã®ç¨®é¡ã®ãããã¯ã¼ã¯ã§ãã£ã¦ããããä»»æã®ç¨®é¡ã§ããå¾ããåã«ä¾ç¤ºã®ããããããã¯ã¼ã¯ï¼ï¼ï¼ï¼ã¯ãã¤ã¼ãµãããï¼ç»é²åæ¨ï¼ãããã¯ã¼ã¯ããã¼ã¯ã³ãªã³ã°ãããã¯ã¼ã¯ãªã©ã®ã­ã¼ã«ã«ã¨ãªã¢ãããã¯ã¼ã¯ï¼ãï¼¬ï¼¡ï¼®ãï¼ãã¯ã¤ãã¨ãªã¢ãããã¯ã¼ã¯ãéå®ããããã¨ãªãä»®æ³ãã©ã¤ãã¼ããããã¯ã¼ã¯ï¼ãï¼¶ï¼°ï¼®ãï¼ãå«ãä»®æ³ãããã¯ã¼ã¯ãã¤ã³ã¿ã¼ããããã¤ã³ãã©ããããã¨ã¯ã¹ãã©ããããå ¬è¡äº¤æé»è©±ç¶²ï¼ãï¼°ï¼³ï¼´ï¼®ãï¼ãèµ¤å¤ç·ãããã¯ã¼ã¯ãã¯ã¤ã¤ã¬ã¹ãããã¯ã¼ã¯ï¼ãã¨ãã°ãæè¡åéã§å ¬ç¥ã®ï¼©ï¼¥ï¼¥ï¼¥ï¼ï¼ï¼ï¼ï¼ï¼ãã­ãã³ã«ç¾¤ãï¼§ï¼²ï¼°ï¼³ãï¼§ï¼³ï¼­ï¼ç»é²åæ¨ï¼ãï¼µï¼­ï¼´ï¼³ãï¼¥ï¼¤ï¼§ï¼¥ãï¼ï¼§ãï¼ï¼ï¼ï¼§ãï¼ï¼§ãï¼ï¼§ãWimaxãWiFi

ãï¼£ï¼¤ï¼­ï¼¡ï¼ï¼ï¼ï¼ãï¼·ï¼£ï¼¤ï¼­ï¼¡ï¼ç»é²åæ¨ï¼ããã«ã¼ãã¥ã¼ã¹ï¼ç»é²åæ¨ï¼ãã­ãã³ã«ãããã³ï¼ãããã¯ä»»æã®ä»ã®ã¯ã¤ã¤ã¬ã¹ãã­ãã³ã«ï¼ããªãã³ã«ï¼ã¾ãã¯ãããããã³ï¼ãããã¯ä»ã®ãããã¯ã¼ã¯ã®ä»»æã®çµåãã§ããå¾ãã In most embodiments, system 1300 includes some type of network 1310. Network is not limited to TCP / IP, SMA, IPX, AppleTalk

It can be any type of network familiar to those skilled in the art and can be of any type that can support data communication using any of a variety of commercially available protocols including: For illustrative purposes only, the network 1310 includes virtual networks including Ethernet networks, local area networks (âLANâ) such as token ring networks, wide area networks, and virtual private networks (âVPNâ) without limitation. Network, internet, intranet, extranet, public switched telephone network (âPSTNâ), infrared network, wireless network (eg, IEEE 802.11 protocols known in the art, GRPS, GSMÂ®, UMTS, EDGE, 2G, 2.5G, 3G, 4G, Wimax, WiFi

CDMA2000, WCDMAÂ®, BluetoothÂ® protocol, and / or any other wireless protocol), and / or any combination of these and / or other networks.

ã·ã¹ãã ã¯ãæ±ç¨ã³ã³ãã¥ã¼ã¿ãï¼åã«ä¾ç¤ºã®ããã«ãï¼°ï¼£ãµã¼ããï¼µï¼®ï¼©ï¼¸ï¼ç»é²åæ¨ï¼ãµã¼ããä¸­åãµã¼ããã¡ã¤ã³ãã¬ã¼ã ã³ã³ãã¥ã¼ã¿ã©ãã¯æ­è¼ãµã¼ããªã©ãå«ãï¼ç¹åããããµã¼ãã³ã³ãã¥ã¼ã¿ããµã¼ããã¡ã¼ã ããµã¼ãã¯ã©ã¹ã¿ãã¾ãã¯ä»»æã®ä»ã®é©åãªé ç½®ããã³ï¼ãããã¯çµåãã§ããå¾ãï¼ã¤ä»¥ä¸ã®ãµã¼ãã³ã³ãã¥ã¼ã¿ï¼ï¼ï¼ï¼ãï¼ï¼ï¼ï¼ãï¼ï¼ï¼ï¼ãå«ãã§ãããããµã¼ãã®ãã¡ï¼ã¤ä»¥ä¸ï¼ãã¨ãã°ï¼ï¼ï¼ï¼ï¼ã¯ããã¸ãã¹ã¢ããªã±ã¼ã·ã§ã³ãã¦ã§ããµã¼ããã¢ããªã±ã¼ã·ã§ã³ãµã¼ããªã©ã®ã¢ããªã±ã¼ã·ã§ã³ã®å®è¡å°ç¨ã§ãã£ã¦ãããããã®ãããªãµã¼ãã¯ãã¦ã¼ã¶ã³ã³ãã¥ã¼ã¿ï¼ï¼ï¼ï¼ãï¼ï¼ï¼ï¼ãï¼ï¼ï¼ï¼ãï¼ï¼ï¼ï¼ããè¦æ±ãå¦çããããã«ç¨ãããã¦ããããã¢ããªã±ã¼ã·ã§ã³ã¯ããµã¼ãï¼ï¼ï¼ï¼ãï¼ï¼ï¼ï¼ãï¼ï¼ï¼ï¼ã®ãªã½ã¼ã¹ã¸ã®ã¢ã¯ã»ã¹ãå¶å¾¡ããããã®ä»»æã®æ°ã®ã¢ããªã±ã¼ã·ã§ã³ãå«ããã¨ãã§ããã Â Â The system can be a general purpose computer, a specialized server computer (including, for illustrative purposes, a PC server, a UNIX server, a medium server, a mainframe computer rack mounted server, etc.), a server farm, a server cluster, or One or more server computers 1302, 1304, 1306 may also be included, which may be in any other suitable arrangement and / or combination. One or more of the servers (eg, 1306) may be dedicated to executing applications such as business applications, web servers, application servers, and the like. Such a server may be used to process requests from user computers 1312, 1314, 1316, 1318. Applications can also include any number of applications for controlling access to the resources of servers 1302, 1304, 1306.

ã¦ã§ããµã¼ãã¯ãä»¥ä¸è«ãããã®ã®ãã¡ä»»æã®ãã®ãå«ããªãã¬ã¼ãã£ã³ã°ã·ã¹ãã ã

ãã³ä»»æã®å¸è²©ã®ãµã¼ããªãã¬ã¼ãã£ã³ã°ã·ã¹ãã ãå®è¡ãããã¨ãã§ãããã¦ã§ããµã¼ãã¯ãï¼¨ï¼´ï¼´ï¼°ãµã¼ããï¼¦ï¼´ï¼°ãµã¼ããï¼£ï¼§ï¼©ãµã¼ãããã¼ã¿ãã¼ã¹ãµã¼ããJavaï¼ç»é²åæ¨ï¼ãµã¼ãããã¸ãã¹ã¢ããªã±ã¼ã·ã§ã³ãªã©ãå«ããã¾ãã¾ãªãµã¼ãã¢ããªã±ã¼ã·ã§ã³ããã³ï¼ã¾ãã¯ä¸­éå±¤ã¢ããªã±ã¼ã·ã§ã³ã®ãã¡ä»»æã®ãã®ãå®è¡ãããã¨ãã§ããããµã¼ãã¯ãã¦ã¼ã¶ã³ã³ãã¥ã¼ã¿ï¼ï¼ï¼ï¼ãï¼ï¼ï¼ï¼ãï¼ï¼ï¼ï¼ãï¼ï¼ï¼ï¼ã«å¿ç­ãã¦ãã­ã°ã©ã ã¾ãã¯ã¹ã¯ãªãããå®è¡ãããã¨ãå¯è½ã§ããå¾ãï¼ã¤ä»¥ä¸ã®ã³ã³ãã¥ã¼ã¿ã§ãã£ã¦ããããä¸ä¾ã¨ãã¦ããµã¼ãã¯ï¼ã¤ä»¥ä¸ã®ã¦ã§ãã¢ããªã±ã¼ã·ã§ã³ãå®è¡ãã¦ããããã¦ã§ãã¢ããªã±ã¼ã·ã§ã³ã¯ãJavaï¼ç»é²åæ¨ï¼ãï¼£ãï¼£â¯ããããã¯ï¼£ï¼ï¼ãªã©ã®ä»»æã®ãã­ã°ã©ãã³ã°è¨èªããªãã³ã«ï¼ã¾ãã¯PerlãPythonããããã¯TCLãªã©ã®ä»»æã®ã¹ã¯ãªãã

è¨èªããªãã³ã«ä»»æã®ãã­ã°ã©ãã³ã°ï¼ã¹ã¯ãªããè¨èªã®çµåãã§æ¸ãããï¼ã¤ä»¥ä¸ã®ã¹ã¯ãªããã¾ãã¯ãã­ã°ã©ã ã¨ãã¦å®ç¾ããã¦ãããããµã¼ãã¯ãã¦ã¼ã¶ã³ã³ãã¥ã¼ã¿ï¼ï¼ï¼ï¼ãï¼ï¼ï¼ï¼ãï¼ï¼ï¼ï¼ãï¼ï¼ï¼ï¼ä¸ã§å®è¡ãããã¼ã¿ãã¼ã¹ã¯ã©ã¤ã¢ã³ãããã®è¦æ±ãå¦çãããã¨ãã§ãããOracleï¼ç»é²åæ¨ï¼ãMicrosoftï¼ç»é²åæ¨ï¼ãSybaseï¼ç»é²

åæ¨ï¼ãï¼©ï¼¢ï¼­ï¼ç»é²åæ¨ï¼ãªã©ããå¸è²©ããã¦ãããã®ãéå®ããããã¨ãªãå«ããã¼ã¿ãã¼ã¹ãµã¼ããå«ãã§ãããã The web server can run an operating system including any of those discussed above and any commercially available server operating system. The web server can also run any of a variety of server applications and / or middle tier applications including HTTP servers, FTP servers, CGI servers, database servers, Java servers, business applications, and the like. The server may be one or more computers that may be capable of executing programs or scripts in response to user computers 1312, 1314, 1316, 1318. As an example, the server may execute one or more web applications. Web applications can be in any programming language such as Java, C, C #, or C ++, and / or any scripting language such as Perl, Python, or TCL, and any programming / sc