Application of Windows real-time communication technology

Application of Windows real-time communication technology

Original: Tom fout
Translation: Meng Jin

Source: msdn library January 15,200 2

Summary
The client API of Windows xp rtc enables developers to implement real-time communication in their own applications. This article describes the necessary components of the RTC technology and application technology.

Directory

Introduction
Applications with RTC Functions
RTC application scenarios
RTC client application interface
RTC object
Configuration files and settings
Client events
RTC Interface
More information

Introduction
Today, we can use many methods to communicate with our partners, customers, supporters, families, and friends. E-Mail has become a widely used communication method, but its real-time performance is not strong. The phone number has been proved to be a good communication method and has real-time performance, but it also has limitations, such as only voice communication, and it lacks a mechanism to let us know whether the other party we are talking with is ready to answer our call.

Real-time communication
Real-time communications (RTC) provides a rich set of communication and collaboration features combined with on-site information, allowing you to know when and where to find your contacts. Many RTC features are embodied in another form or in other applications, but these features are never combined into a separate implementation.
For example, instant messaging (IM) is one of the fastest growing Internet communication mechanisms, because it is simple and efficient. Im is real-time and on-site, allowing you to know when to find your contacts. However, it does not have other features, such as audio and video conferencing and online cooperation.
Microsoft Windows XP includes all the real-time communication functions in Microsoft Windows Messenger. Windows Messenger enables you to use text and audio (voice calls can be established between PCs, PCs, and phones) with your customers and colleagues), videos, shared whiteboards, and applications. You can create a contact list to know when your contact will be online and when it will be available through on-site information. Moreover, these capabilities are not limited to Windows Messenger, but can be used to enrich other applications by using the RTC client API.

Applications with RTC Functions
The Windows Messenger client uses the RTC client component of Windows XP. This client represents all RTC capabilities in a separate application. However, in many cases, it is quite cumbersome to use a Helper Program for communication.
RTC is based on Internet technology and protocol standards, so that other devices and applications can use this technology to communicate with Windows Messenger.
The RTC client of Windows XP also provides an open application interface. Therefore, these RTC functions can be added to applications based on windows. For example, a web-based purchase program can contain an instant HELP button. Click this button to open an im session between the customer and the technical support staff.

RTC application scenarios
Windows Messenger contains many RTC functions in a separate application. This solution is useful and may be the best solution in many cases. In many cases, including these features in your application can make things easier, better, and better.
The following are some examples that include the RTC function into the application. There are many other examples of using this technology.

Customer Relationship Management-Desktop remote help
Jim wants to buy a book through an online bookstore, but his credit card seems to be a problem. By clicking a button on the webpage, he immediately established an im session with the sales representative of Amazon (the name of the bookstore. Through Im sharing with the application, the Sales Representative found and solved the problem. This book is also ordered. Without such real-time help capabilities, Jim probably gave up his purchase and lost the business.

Knowledge management-communication sites for teams and projects
The site of the product R & D team has several functional areas (such as the client and server teams ). By navigating to the relevant responsibility area, you can find a panel listing all the team members and whether they are present or not. By clicking the contact information of relevant members, the user can immediately communicate with the member of the team. This kind of instant attendance information reduces the number of potential e-mails and telephones, and also reduces the number of failures.

E-commerce-communications between partners and suppliers
A large manufacturer has many suppliers that connect to different external networks. Instead of sending emails to discuss orders, they can use the RTC client API to develop an application that transmits specific information. For example, a manufacturer can use IM to issue a 1000 parts order and use IM to immediately confirm that the order has been delivered to the supplier and has entered the supplier's system. The status information can be automatically obtained as needed during the processing of the order.

System warning-sent to a user's desktop PC or mobile device
A company has developed an e-mail server. To reduce the number of technical support calls, they developed a small application that notifies all users of a specific e-mail server (using IM) the server will be suspended for routine maintenance. Even if the e-mail server is no longer online, the user can receive the message, so that the technical support staff can be quiet.

Games
Most multiplayer games include chatting with opponents and peers. But can you imagine seeing his face when you're about to end your friend's game?

Other functions
There are many other potential functions of RTC in applications. By integrating RTC into existing commercial software, instant messaging and collaboration can be achieved, which increases productivity. Benefits many industries and sectors, including finance, manufacturing, healthcare, and human resources.

RTC client application interface
To obtain the same RTC client functions as in Windows Messenger, RTC is enabled for Windows XP through the RTC client API. These APIs enable applications to create calls from PC-PC, PC-phone, or phone-phone. Applications can be used to create IM sessions on the Internet or intranet. Voice and video calls can be established between PC users. The application can obtain and display the field information of a series of contacts. By adding applications and whiteboard sharing functions, we can enhance cooperation between the two parties.
Who can use these interfaces? Internal development groups can use these APIs to increase the functionality of internal tools. Software companies can use RTC APIs to integrate RTC functions into their own applications, create specialized software for sale, or meet customer needs. Telephone service providers can create applications for residential or corporate users. Telecom providers wishing to sell RTC services can use these APIs to create client applications for their customers. You can use C ++ and Microsoft Visual Basic to create an application.

RTC object
The basic encoding model of RTC is com. In RTC, the objects used for communication are client, session, and participant.

Figure 1 RTC client COM Object

• Client object: The client object implements the irtcclient interface and establishes allowed types and parameters for the session, such as the preferred device, media type, bit rate, and other media attributes, for example, volume and echo offset. This interface is also used to create session objects.
• Session Object: the session object is created through the irtcclient: createsession method and is used to manage a session. This object implements the irtcsession interface, which is used to initialize, reply, or terminate a meeting and add participants and other meeting management. This object supports IM and other session types. Session objects can be used. For example, you can create an IM Meeting with your friends or start an audio call that is represented by a Web site.
• The participant object: The participant object is created by the irtcsession: addparticipant ipant method and contains all the methods related to the participants. It includes the name and current status of the participant. The irtcparticipant interface is implemented by this object.

Attendance information is managed by buddy and watcher objects. These objects provide interfaces for managing and retrieving information related to contacts and attendees.

• Buddy object: The Buddy object is used to manage, set, and obtain information related to contacts. When a contact is added using the irtcclientpresence: addbuddy method (irtcclientpresence is implemented by the client object), the buddy object is created. Information such as the contact name and status can be obtained by the irtcbuddy interface.
• Watcher object: Watcher is used to obtain the status (watcher) information related to a contact. The contact is someone who adds you as a contact. This object can also be added through the irtcclientpresence interface using the addwatcher method. The status and information of watcher are obtained using the method implemented in the irtcwatcher interface.

Configuration files and settings
The configuration file object is used to maintain client settings. A configuration file object includes the client display, user name, supported meeting types, and client RTC provider information. This information can be used to obtain network resources and set the call or handle attendance information. The configuration file object is created by the irtcclientprovisioning interface (implemented in the client object.
The client creates a configuration file to store information for customers to access services on the network. A client application must create an XML document to save the client configuration. The configuration file can be used to set different service types that different providers, proxy servers, or gateways provide to clients.
After the RTC is initialized, the client application creates and activates a configuration file.

Client events
RTC client APIs allow applications to be notified through different client events, including message events, session status changes, participant status changes, attendance status changes, device changes, and network quality changes. In specific implementation, the application creates an Event Filter (in the form of a screen code) through the irtcclien interface, and registers an irtceventnotification event interface in the Application Event receiving object. When an event of interest occurs, the event type and object will be provided to the client for processing.

RTC Interface
Several Interfaces implemented by the RTC object are discussed above. You can use these interfaces to add the expected RTC function to an application. These RTC interfaces and their related methods are described in the SDK documentation.

More information

• For the latest XP information, see the Windows XP homepage.
• For more information about the RTC client API, see real-time communications (RTC) Client documentation in the SDK.