seminar code
09-08-2014, 12:08 PM
A social network
[attachment=66792]
Abstract
A social network is a social structure made of nodes (which are generally individuals or organizations) that are tied by one or more specific types of interdependency, such as values, visions, ideas, financial exchange, friendship, kinship, dislike, conflict or trade. The resulting graph-based structures are often very complex.
Social network analysis views social relationships in terms of nodes and ties. Nodes are the individual actors within the networks, and ties are the relationships between the actors. There can be many kinds of ties between the nodes. Research in a number of academic fields has shown that social networks operate on many levels, from families up to the level of nations, and play a critical role in determining the way problems are solved, organizations are run, and the degree to which individuals succeed in achieving their goals.
In its simplest form, a social network is a map of all of the relevant ties between the nodes being studied. The network can also be used to determine the social capital of individual actors. These concepts are often displayed in a social network diagram, where nodes are the points and ties are the lines.
Voice message processing:
A voice message is processed in a distributed system by storing voice message data indicative of a plurality of voice messages on a distributed data store. A distributed data processor accesses the voice messages and extracts desired information from the voice messages. The data processor then augments the data stored in the voice message data store with the extracted information. The user interface component provides user access to the voice messages with the augmented data.
Introduction
This document describes the carriage of voicemail messages over Internet mail as part of a unified messaging infrastructure.
The Internet Voice Messaging (IVM) concept described in this document is not a successor format to VPIM v2 (Voice Profile for Internet Mail Version 2), but rather an alternative specification for a different application.
For some forms of communication, people prefer to communicate using their voices rather than typingBy permitting voicemail to be implemented in an interoperable way on top of Internet Mail, voice messaging and electronic mail no longer need to remain in separate, isolated worlds, and users will be able to choose the most appropriate form of communication. This will also enable new types of devices, without keyboards, to be used to participate in electronic messaging when mobile, in a hostile environment, or in spite of disabilities.
(VPIM v2 as defined in RFC 2421 [VPIMV2] and revised in RFC 3801, Draft Standard [VPIMV2R2]) when forwarding messages to remote voicemail systems. VPIM v2 was designed to allow two voicemail systems to exchange messages, not to allow a voicemail system to interoperate with a desktop e-mail client. It is often not reasonable to expect a VPIM v2 message to be usable by an e-mail recipient. The result is messages that cannot be processed by the recipient (e.g., because of the encoding used), or look ugly to the user.
This document therefore proposes a standard mechanism for representing a voicemail message within SMTP/MIME, and a standard encoding for the audio content, which unified messaging systems and mail clients MUST implement to ensure interoperability. By using a standard SMTP/MIME representation and a widely implemented audio encoding, this will also permit most users of e-mail clients not specifically implementing the standard to still access the voicemail messages. In addition, this document describes features an e-mail client SHOULD implement to allow recipients to display voicemail messages in a more friendly, context-sensitive way to the user, and intelligently provide some of the additional functionality typically
found in voicemail systems (such as responding with a voice message instead of e-mail). Finally, how a client MAY provide a level of interoperability with VPIM v2 is explained. It is desirable that unified messaging mail clients also be able to fully interoperate with voicemail servers. This is possible today, providing the client implements VPIM v2 [VPIMV2R2], in addition to this specification, and uses it to construct messages to be sent to a voicemail server.
Voice Contents
Voice messages may be contained at any location within a message and MUST always be contained in an audio/basic content-type, unless the originator is aware that the recipient can handle other content. Specifically, Audio/32kadpcm MAY be used when the recipient is known to support VPIM v2 [VPIMV2R2]. The VOICE parameter on Content-Disposition from VPIM v2 [VPIMV2R2] SHOULD be used to identify any spoken names or spoken subjects (as distinct from voice message contents). As well, the Content-Duration header [DUR] SHOULD be used to indicate the audio length. The originator's spoken name MAY be included with messages as separate audio contents, if known, and SHOULD be indicated by the Content-Disposition VOICE parameter as defined in VPIM v2 [VPIMV2R2]. If there is a single recipient for the message, the spoken name MAY also be included (per VPIM v2). A spoken subject MAY also be provided (per VPIM v2).A sending implementation MAY determine the recipient capabilities before sending a message and choose a codec accordingly (e.g., using some form of content negotiation). In the absence of such recipient knowledge, sending implementations MUST use raw G.711 mu-law, which is indicated with a MIME content type of "audio/basic" (and SHOULD use a filename parameter that ends ".au") [G711], [MIME2]. A sending implementation MAY support interoperability with VPIM v2 [VPIMV2R2], in which case, it MUST be able to record G.726 (indicated as audio/32kadpcm) [G726], [ADPCM].
Methodeledge
In this paper, firstly the voice message is sent through SMS without compression. For this purpose we used the same algorithm presented in [7]. Steps involved to convert voice message in to SMS are as follows:
• Store user input (voice message) in a ByteArrayOutputStream.
• Convert the signed ByteArrayOutputStream into unsigned integer array.
• Convert unsigned integer array into their respective Extended ASCII characters, but before that conversion, 256 was added in all unsigned integer array values which was ranged between 0-31 in order to move them up to the range of 256-287. The main reason behind this is that, values of 0-31 of ASCII characters cannot be send through SMS as such characters are universally reserved for specific functions; e.g. ‘0’ represents ‘null’ in ASCII etc.
• Extended ASCII characters are then converted into strings and those strings are used as a payload of text of SMS.
When such SMS is received at receiver side, application perform same steps but in a reverse order. In above mention procedure concatenated SMS are used. To record the order of concatenated SMS produced by the sending device, first three characters of SMS are reserved. This produced 0-999 indexing values for concatenated SMS. The International Journal of Advanced Science and Technology.
Work Plan
The single most important principle to keep in mind when you are ready to invest in any new technology is its strategic importance to your business mission. As business owners, you’ll only want to acquire technology that helps you:
• Impress your customers;
• Control your costs; and,
• Support your longer-term strategic objectives.
In the current telephone services market, it is easy to be overwhelmed. You may have heard of hosted communications services or “virtual PBX” providers, or you may have seen advertisements for cost reduction achieved through VoIP phone service. But how should you make sense of these? Whether you are just starting a business, experiencing growing pains, or looking for a competitive edge, the principles of phone system selection are fundamentally similar. You’ll want to:
1. Assess your needs — what are your company’s primary objectives, and what do you need from your phone system to support these?
2. Evaluate whether any of the recent telecommunications innovations will directly contribute to your company’s ability to meet your strategic objectives.
3. Identify basic principles on which to select a provider. Determine which features are most important to your business – such as voicemail, auto attendant, answering service.
4. Minimize risk by avoiding systems that will require massive switching and training costs.
[attachment=66792]
Abstract
A social network is a social structure made of nodes (which are generally individuals or organizations) that are tied by one or more specific types of interdependency, such as values, visions, ideas, financial exchange, friendship, kinship, dislike, conflict or trade. The resulting graph-based structures are often very complex.
Social network analysis views social relationships in terms of nodes and ties. Nodes are the individual actors within the networks, and ties are the relationships between the actors. There can be many kinds of ties between the nodes. Research in a number of academic fields has shown that social networks operate on many levels, from families up to the level of nations, and play a critical role in determining the way problems are solved, organizations are run, and the degree to which individuals succeed in achieving their goals.
In its simplest form, a social network is a map of all of the relevant ties between the nodes being studied. The network can also be used to determine the social capital of individual actors. These concepts are often displayed in a social network diagram, where nodes are the points and ties are the lines.
Voice message processing:
A voice message is processed in a distributed system by storing voice message data indicative of a plurality of voice messages on a distributed data store. A distributed data processor accesses the voice messages and extracts desired information from the voice messages. The data processor then augments the data stored in the voice message data store with the extracted information. The user interface component provides user access to the voice messages with the augmented data.
Introduction
This document describes the carriage of voicemail messages over Internet mail as part of a unified messaging infrastructure.
The Internet Voice Messaging (IVM) concept described in this document is not a successor format to VPIM v2 (Voice Profile for Internet Mail Version 2), but rather an alternative specification for a different application.
For some forms of communication, people prefer to communicate using their voices rather than typingBy permitting voicemail to be implemented in an interoperable way on top of Internet Mail, voice messaging and electronic mail no longer need to remain in separate, isolated worlds, and users will be able to choose the most appropriate form of communication. This will also enable new types of devices, without keyboards, to be used to participate in electronic messaging when mobile, in a hostile environment, or in spite of disabilities.
(VPIM v2 as defined in RFC 2421 [VPIMV2] and revised in RFC 3801, Draft Standard [VPIMV2R2]) when forwarding messages to remote voicemail systems. VPIM v2 was designed to allow two voicemail systems to exchange messages, not to allow a voicemail system to interoperate with a desktop e-mail client. It is often not reasonable to expect a VPIM v2 message to be usable by an e-mail recipient. The result is messages that cannot be processed by the recipient (e.g., because of the encoding used), or look ugly to the user.
This document therefore proposes a standard mechanism for representing a voicemail message within SMTP/MIME, and a standard encoding for the audio content, which unified messaging systems and mail clients MUST implement to ensure interoperability. By using a standard SMTP/MIME representation and a widely implemented audio encoding, this will also permit most users of e-mail clients not specifically implementing the standard to still access the voicemail messages. In addition, this document describes features an e-mail client SHOULD implement to allow recipients to display voicemail messages in a more friendly, context-sensitive way to the user, and intelligently provide some of the additional functionality typically
found in voicemail systems (such as responding with a voice message instead of e-mail). Finally, how a client MAY provide a level of interoperability with VPIM v2 is explained. It is desirable that unified messaging mail clients also be able to fully interoperate with voicemail servers. This is possible today, providing the client implements VPIM v2 [VPIMV2R2], in addition to this specification, and uses it to construct messages to be sent to a voicemail server.
Voice Contents
Voice messages may be contained at any location within a message and MUST always be contained in an audio/basic content-type, unless the originator is aware that the recipient can handle other content. Specifically, Audio/32kadpcm MAY be used when the recipient is known to support VPIM v2 [VPIMV2R2]. The VOICE parameter on Content-Disposition from VPIM v2 [VPIMV2R2] SHOULD be used to identify any spoken names or spoken subjects (as distinct from voice message contents). As well, the Content-Duration header [DUR] SHOULD be used to indicate the audio length. The originator's spoken name MAY be included with messages as separate audio contents, if known, and SHOULD be indicated by the Content-Disposition VOICE parameter as defined in VPIM v2 [VPIMV2R2]. If there is a single recipient for the message, the spoken name MAY also be included (per VPIM v2). A spoken subject MAY also be provided (per VPIM v2).A sending implementation MAY determine the recipient capabilities before sending a message and choose a codec accordingly (e.g., using some form of content negotiation). In the absence of such recipient knowledge, sending implementations MUST use raw G.711 mu-law, which is indicated with a MIME content type of "audio/basic" (and SHOULD use a filename parameter that ends ".au") [G711], [MIME2]. A sending implementation MAY support interoperability with VPIM v2 [VPIMV2R2], in which case, it MUST be able to record G.726 (indicated as audio/32kadpcm) [G726], [ADPCM].
Methodeledge
In this paper, firstly the voice message is sent through SMS without compression. For this purpose we used the same algorithm presented in [7]. Steps involved to convert voice message in to SMS are as follows:
• Store user input (voice message) in a ByteArrayOutputStream.
• Convert the signed ByteArrayOutputStream into unsigned integer array.
• Convert unsigned integer array into their respective Extended ASCII characters, but before that conversion, 256 was added in all unsigned integer array values which was ranged between 0-31 in order to move them up to the range of 256-287. The main reason behind this is that, values of 0-31 of ASCII characters cannot be send through SMS as such characters are universally reserved for specific functions; e.g. ‘0’ represents ‘null’ in ASCII etc.
• Extended ASCII characters are then converted into strings and those strings are used as a payload of text of SMS.
When such SMS is received at receiver side, application perform same steps but in a reverse order. In above mention procedure concatenated SMS are used. To record the order of concatenated SMS produced by the sending device, first three characters of SMS are reserved. This produced 0-999 indexing values for concatenated SMS. The International Journal of Advanced Science and Technology.
Work Plan
The single most important principle to keep in mind when you are ready to invest in any new technology is its strategic importance to your business mission. As business owners, you’ll only want to acquire technology that helps you:
• Impress your customers;
• Control your costs; and,
• Support your longer-term strategic objectives.
In the current telephone services market, it is easy to be overwhelmed. You may have heard of hosted communications services or “virtual PBX” providers, or you may have seen advertisements for cost reduction achieved through VoIP phone service. But how should you make sense of these? Whether you are just starting a business, experiencing growing pains, or looking for a competitive edge, the principles of phone system selection are fundamentally similar. You’ll want to:
1. Assess your needs — what are your company’s primary objectives, and what do you need from your phone system to support these?
2. Evaluate whether any of the recent telecommunications innovations will directly contribute to your company’s ability to meet your strategic objectives.
3. Identify basic principles on which to select a provider. Determine which features are most important to your business – such as voicemail, auto attendant, answering service.
4. Minimize risk by avoiding systems that will require massive switching and training costs.