WO2021128152A1 - A method and system for processing a plurality of messages between different social network services - Google Patents

A method and system for processing a plurality of messages between different social network services Download PDF

Info

Publication number
WO2021128152A1
WO2021128152A1 PCT/CN2019/128611 CN2019128611W WO2021128152A1 WO 2021128152 A1 WO2021128152 A1 WO 2021128152A1 CN 2019128611 W CN2019128611 W CN 2019128611W WO 2021128152 A1 WO2021128152 A1 WO 2021128152A1
Authority
WO
WIPO (PCT)
Prior art keywords
social network
account
message
server
message channel
Prior art date
Application number
PCT/CN2019/128611
Other languages
French (fr)
Inventor
Minghai HUANG
Original Assignee
Mastercard Shanghai Business Consulting Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Mastercard Shanghai Business Consulting Ltd. filed Critical Mastercard Shanghai Business Consulting Ltd.
Priority to PCT/CN2019/128611 priority Critical patent/WO2021128152A1/en
Publication of WO2021128152A1 publication Critical patent/WO2021128152A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/102—Entity profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/52—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail for supporting social networking services

Definitions

  • the present invention relates generally to technology and, in particular, to provide a method and system for processing a plurality of messages among social network accounts on different social network services, namely the first social network service and the second social network service.
  • Social Network Services have opened up many new avenues to building social networks by allowing users to share information online and connect with a wide range of different users.
  • Social Network Services each maintains profiles created by users of the specific service.
  • a user's profile allows other users of the service to learn about the user.
  • a user's profile includes, for example, information about the user, pictures posted by the user, a listing of the user's friends, and comments posted by the user and the user's friends.
  • the amount and types of information that can be shared and used in these Social Network Services is vast, which may also provide opportunities for e-commerce.
  • Social network services allow users to communicate with other users about any topic. However, this is limited to users who are subscribed to the same social network service.
  • social network services do not validate the appropriateness of the content included in communications between users. Some users take advantage of this lack of validation to plan events or activities that are illegal or not allowed by a supervisor (e.g., a parent) .
  • malicious entities take advantage of the lack of validation by using the social network services to obtain personal information from users. For example, a malicious entity can deceive users into believing it is a trustworthy entity and have users provide their credit card numbers, social security numbers, and/or passwords. Accordingly, there is a need in the art for ways to validate and facilitate of communications among different social network services.
  • the system comprising: a server having at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the server at least to: receive, through the second message channel, a request to send the message to the first social network account, the request including the message to be sent, a first account identifier associated with the first social network account and second account information associated with the second social network account; determine whether the second social network account is permitted to send the message to the first social network account based on the first account identifier; and transmit, through the first message channel, the message for displaying based on the determination of whether the second social network account is permitted to send the message to the
  • a method for processing a message between a first social network account on a first social network service and a second social network account on a second social network service that is different from the first social network service, the first social network service having a first message channel and the second social network service having a second message channel comprising: receiving, through the second message channel, a request to send the message to the first social network account, the request including a first account identifier associated with the first social network account and second account information associated with the second social network account; determining whether the second social network account is permitted to send the message to the first social network account based on the first account identifier; and transmitting, through the first message channel, the message for displaying based on the determination of whether the second social network account is permitted to send the message to the first social network account.
  • Fig. 1A shows a system for processing a plurality of messages across a plurality of social network servers
  • Figs. 1B to 1D show alternative embodiments of the system shown in Fig. 1A;
  • Fig. 2 is a flow diagram of a method of generating and transmitting an account identifier in the system shown in Fig. 1A;
  • Fig. 3 is a flow diagram of a method of processing a plurality of messages between different social network accounts in the system shown in Fig. 1A;
  • Fig. 4A is a flow diagram of a sub-process of determining the social network account can be used to register to the message channel in the system of Fig. 1A;
  • Fig. 4B is a flow diagram of a sub-process of determining whether the second social network account is permitted to send the plurality of messages in the system of Fig. 1A;
  • Fig. 5 is a flow diagram of a sub-process of processing a transaction in the system of Fig. 1A;
  • Figs. 6A and 6B form a schematic block diagram of a general purpose computer system upon which the message processing server of Fig. 1A can be practiced;
  • Fig. 7 shows an example of a computing device to realize the message processing server shown in Fig. 1A.
  • the payment network server is a server that hosts software application programs for processing payment of a transaction request message.
  • the payment network server is a typical payment network server that is used to process transaction request messages.
  • the payment network server communicates with a social network server (one that is managed by a social network service if required) , and any other servers (e.g., an issuer server, an acquirer server) to facilitate payment of transaction request messages generated by the message processing server 110.
  • Payment network servers may use a variety of different protocols and procedures in order to process the transaction request messages. Transactions that may be performed via a payment network server include product or service purchases, credit purchases, debit transactions, fund transfers, account withdrawals, etc.
  • Payment network servers may be configured to process transactions via cash-substitutes, which may include payment cards, letters of credit, checks, payment accounts, etc.
  • the payment network server is operated by a service provider such as Mastercard.
  • the payment network server may be Banknet network operated by Mastercard.
  • the service provider e.g. Mastercard
  • the service provider may be an entity (e.g. a company or organization) who operates to process transactions, clear and settle funds for payments between two entities (e.g. two banks) .
  • the payment network server may include one or more computing devices that are used for processing transactions.
  • the social network account can be used to display a user’s profile including, for example, information about the user, pictures posted by the user, a listing of the user's friends, and comments posted by the user and the user's friends.
  • the amount and types of information that can be shared and used in these social network services is vast.
  • the social network account may include a payment account of the registered user.
  • a user device may be used to sign in to a social network account.
  • the user device may also be used to purchase a merchant’s product by initiating a transaction.
  • the user device may be a handheld or portable or mobile device carried or used by the target user, or may refer to other types of electronic devices such as a personal computer, a land-line telephone or an interactive voice response (IVR) system and the like.
  • the mobile device may be a device, such as a mobile phone, a laptop computer, a personal digital computer (PDA) , a mobile computer, a portable music player (such as an iPod TM and the like) .
  • PDA personal digital computer
  • iPod portable music player
  • Transaction –A transaction relates to an agreement carried out between a customer and a merchant to exchange asset (i.e., goods or services) for payment.
  • asset i.e., goods or services
  • User –a user may be any suitable type of entity associated with a payment account, which may include a person, family, company, corporation, governmental entity, and the like.
  • the term user is used herein to identify an entity performing or approving a purchase in a transaction.
  • the user may provide the fund for the transaction.
  • Merchant –a merchant may be any suitable type of entity associated with a payment account, which may include a person, family, company, corporation, governmental entity, and the like.
  • the term merchant is used herein to identify an entity performing a sale in a transaction and receiving the fund for the transaction.
  • Transaction credentials –Transaction credentials are credentials provided by either a user or a merchant to perform a transaction. Examples of the transaction credentials include a payment account, a password associated with the payment account, and any other data that an acquirer provider or an issuer provider need to authorize a transaction request message generated from the transaction.
  • a message –information to be shared from one user with another user This applies to one user having a social network account, managed by a first social network service, sending a message to another user having a social network account managed by a different social network service, i.e. a second social network service.
  • Sending a message includes initiating a communication and continuing an existing communication.
  • a message channel is one that can receive an in-band or out-of-band message.
  • An out-of-band message refers to a message that is sent via a communication path, type or protocol which is different to the current communication path, type or protocol. Therefore, if message flow thus far has been via the Transmission Control Protocol/Internet Protocol (TCP/IP) , the message may be sent via SMS so as to be an out-of-band message.
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • an out-of-band message typically makes use of two separate networks which work simultaneously to verify a user.
  • a user may initiate a request to send a message via a first social network service and another user or an intended recipient may be informed of such a message via a second message channel with second network.
  • an out-of-band message may be used to allow communication between users having accounts with different social network services, namely the first social network service and the second social network service.
  • the transaction request message can then be forwarded to an acquirer server, the payment network server, and an issuer server, such that payment of the transaction request message can be facilitated.
  • a payment account are a check account, a savings account, a credit account, a virtual payment account, a payment card, and the like.
  • the payment card refers to any suitable transaction cards, such as credit cards, debit cards, prepaid cards, charge cards, membership cards, promotional cards, frequent flyer cards, identification cards, gift cards, and/or any other device that may hold payment account information, such as mobile phones, Smartphones, personal digital assistants (PDAs) , key fobs, and/or computers.
  • PDAs personal digital assistants
  • a payment account is associated with either a customer or a merchant.
  • a payment account associated with a customer is issued by an issuer in a transaction.
  • a payment account associated with a merchant is issued by an acquirer in a transaction.
  • Fig. 1A shows a system 100A comprising user devices 104A to 104N, a merchant device 102, a social network server 103A to 103S (managed by a social network service) , a merchant server 116, an acquirer server 113, a payment server 114, an issuer server 115, and a message request message processing server 110.
  • the message processing server 110 The message processing server 110
  • the message processing server 110 is a server that hosts software application programs 1333 (see Figs. 6A and 6B) to manage user accounts belonging to respective users and transactions. Functions of the message processing server 110 will be discussed below in more detail in relation to Figs. 2 to 4. The structural context of the transaction processing server 110 is discussed below in relation to Figs. 6A and 6B.
  • the message processing server 110 provides an interface to enable communication with each of the devices 104A to 104N, 103A to 103S and 102 and the servers 113, 114, 115.
  • the message processing server 110 is shown in Figs. 1A to 1D to be connected to the collective user devices 104A to 104N and the social network servers 103A to 103S for simplicity sake.
  • the message processing server 110 is connected to any one of the user devices 104A to 104N and any one of the social network servers 103A to 103S.
  • the message processing server 110 provides an application programming interface ( “API” ) to facilitate such communication.
  • APIs may be part of a user interface that may include graphical user interfaces (GUIs) , Web-based interfaces, programmatic interfaces such as application programming interfaces (APIs) and/or sets of remote procedure calls (RPCs) corresponding to interface elements, messaging interfaces in which the interface elements correspond to messages of a communication protocol, and/or suitable combinations thereof.
  • GUIs graphical user interfaces
  • APIs application programming interfaces
  • RPCs remote procedure calls
  • Examples of APIs include the Representational State Transfer (REST) API, and the like.
  • the message processing server 110 stores and manages user accounts of users that are registered to use the services provided by the message processing server 110.
  • the message processing server 110 provides a service to enable a user to send a message (or a plurality of messages) to another user using a different social network account (e.g., one that is administered by another social network service) .
  • sending a message (or a plurality of messages) includes initiating and continuing a communication with a user using a different social network account. The method of sending a message (or a plurality of messages) across different social network accounts will be described hereinafter.
  • the message processing server 110 is part of a payment network server 114 (as shown in Fig. 1C) .
  • the message processing server 110 may also be a payment network server 114 that is configured to facilitate payment between a user of the user devices 104A to 104N and a merchant of the merchant device 102.
  • the message processing server 110 is part of an acquirer server 113 (as shown in Fig. 1B) or part of an issuer server 115 (as shown in Fig. 1D) .
  • the message processing server 110 is compatible with existing payment apps such as Masterpass, Qkr! , payment gateways (such as Mastercard Payment Gateway Service) , and the like. In another arrangement, the message processing server 110 is an additional function on a payment app like Masterpass or Qkr! .
  • the merchant server 116 The merchant server 116
  • the merchant server 116 is a server that hosts software application programs to manage the user accounts belonging to respective users. The merchant server 116 performs this function simultaneously with the message processing server 110 to improve the security of the user account and to store merchant specific information of the user account. For example, the user account stored in the merchant server 116 may contain information regarding favourite items and/or services that the user frequently purchases from the merchant. In another example, the user account in the merchant server 116 may contain information regarding items and/or services that the user wishes the merchant to provide.
  • the merchant server 116 connects with the message processing server 110. As discussed above, the merchant server 116 communicates with the message processing server 110.
  • the merchant server 116 can be integrated in the message processing server 110.
  • the merchant server 116 also hosts software application programs to manage goods and/or services that a merchant sells. Any of the devices 102, 103, 104A to 104N can access the merchant server 116, via the message processing server 110, to review and select products and/or services that are offered by a merchant. There are other merchant servers 116 associated with respective merchants, but these other merchant servers 116 are not shown for ease of description.
  • the merchant server 116 also connects to the merchant device 102 to enable the merchant device 102 to retrieve details of products and/or services offered by the merchant.
  • the merchant server 116 is accessible by any of the devices 102, 103, 104 via the message processing server 110.
  • the merchant device 102 The merchant device 102
  • the merchant device 102 is a device belonging to a merchant.
  • the merchant device 102 is used to perform a transaction and the merchants offer goods and/or services.
  • Examples of the merchant device 102 are tablets, laptops, desktop computers, smartphones, point-of-sales terminals, an interactive robot, and the like.
  • the merchant device 102 connects with the message processing server 110 and may connect directly with the merchant server 116. As described above, the merchant device 102 can communicate with the message processing server 110.
  • the present disclosure only shows one merchant device 102 for ease of description. However, there may be multiple merchant devices 102 associated with a merchant. There are also multiple merchants (not shown) in the system 100.
  • a user can use the merchant device 102 to initiate or complete a transaction to purchase goods and/or services using a user account by sending a message (or a plurality of messages) , once the user is able to send or receive a message with a user account registered to a second (or different) social network service.
  • the merchant device 102 may be located at a store owned by the merchant.
  • the merchant device 102 may also be used to send a request to register to a message channel with a social network server. The sending of the request is described below in relation to step 224 (see Fig. 4A) .
  • the merchant device 102 is shown in Figs. 1A to 1D to be connected to the collective user devices 104A to 104N for simplicity sake.
  • the social network server 103 The social network server 103
  • the social network server 103 is a server that hosts software application programs for receiving messages from a user having a social network account.
  • the messages may be associated with a transaction request which will be forwarded to the acquirer server 113.
  • the social network server 103 is connected to the message processing server 110 to receive the messages (e.g., transaction request messages) .
  • the social network server 103 generally is associated with a social network service who may be an entity (e.g. a company or organization) which issues (e.g. establishes, manages, administers) a social network account.
  • the social network service may be an on-line, computer implemented platform on which users build social networks or social relationship with other people or entities who share similar personal or career interests, activities, backgrounds or real-life connections.
  • the social network server can be used to create a social network account that is used to display a user’s profile including information about the user, pictures posted by the user and a listing of the user’s friends.
  • the social network service may be operated on one or more servers, or the like.
  • the social network server 103 may include one or more computing devices that are used to establish communication with another server by exchanging messages with and/or passing information to the other servers 110 and 114.
  • the user devices 104A to 104N are the user devices 104A to 104N.
  • the user devices 104A to 104N are devices that belong to a user who is registered with the message processing server 110.
  • the user also has a social network account that is managed by a social network server 103. Such a user has a user account with the message processing server 110.
  • the registration (i.e., on-boarding) of the user with the message processing server 110 is described below.
  • Any of the user devices 104A to 104N can be used to register a social network account (described below in relation to the on-boarding of the user) .
  • Examples of the user devices 104A to 104N are tablets, laptops, desktop computers, smartphones, smart speakers, and the like.
  • the user devices 104A to 104N respectively connect with the message processing server 110.
  • the user devices 104A to 104N are collectively referred to as the user devices 104 (when referring to all of the user devices) and the user device 104 (when referring to a single user device) .
  • the user devices 104 can communicate with the message processing server 110.
  • user devices 104 refers to devices that are registered with a user account and is approved to process a message (or a plurality of messages) using the user account that the user devices 104 are associated with.
  • any of the user devices 104 may connect to another user device 104 or the merchant device 102 to process a message (or a plurality of messages) .
  • the acquirer server 113 is a server that hosts software application programs for receiving transaction request messages, which are associated with completed transactions, from the message processing server 110 and forwarding the received transaction request messages to the payment network server 114.
  • the acquirer server 113 is connected to the message processing server 110 to receive the messages.
  • the acquirer server 113 is in communication with the payment network server 114.
  • the acquirer server 113 generally is associated with an acquirer who may be an entity (e.g. a company or organization) which issues (e.g. establishes, manages, administers) a payment account (e.g. a financial bank payment account) of the merchant. Examples of the acquirer include a bank and/or other financial institution.
  • the acquirer server 113 may include one or more computing devices that are used to establish communication with another server by exchanging messages with and/or passing information to the other servers 110 and 114.
  • the payment network server 114 The payment network server 114
  • the payment network server 114 is a server that hosts software application programs for processing payment of transactions.
  • the payment server 114 is a typical payment network server that is used to process transaction request messages.
  • the payment network server 114 is connected to the acquirer server 113 to receive transaction request messages.
  • the payment network server 114 also communicates with the social network server 103 (if required) to process any transaction request messages received from the acquirer server 113.
  • the payment network server 114 is also connected to the issuer server 115 to forward the received transaction request messages to the issuer server 115.
  • the payment network server 115 receives authorization responses to the forwarded transaction request messages from the issuer server 115. More details may be found in Fig. 5.
  • the issuer server 115 The issuer server 115
  • the issuer server 115 is a server that hosts software application programs for receiving transaction request messages from the payment network server 114, processing the transaction request messages, and transmitting authorization responses to the respective transaction request messages to the payment network server 114.
  • the issuer server 115 is connected to the payment network server 114 to receive the transaction request messages.
  • the issuer server 115 generally is associated with an issuer and may include one or more computing devices that are used to process a transaction request message.
  • the issuer may be an entity (e.g. a company or organization) which issues (e.g. establishes, manages, administers) a payment account (e.g. a financial bank payment account) of a user.
  • the system 100A enables a transaction to be initiated by a first device (e.g., the user devices 104, the merchant device 102) using the message processing server 110.
  • a second device e.g., the user devices 104, the merchant device 102 can be used to initiate a request to send a message to a first device (e.g., another user device 104 or the merchant device 102) .
  • a plurality of messages may also be sent between the first device and the second device.
  • the first device which is used to connect to the first social network account may be used to continue to send a further message or a reply upon receipt of the message sent from the second device.
  • the message processing server 110 If the message relates to a transaction request message, the message processing server 110 generates a transaction request message and transmits the transaction request message to the acquirer server 113.
  • the acquirer server 113 then forwards the transaction request message to the payment network server 114.
  • the payment network server 114 forwards the transaction request message to the issuer server 115.
  • the issuer server 115 either approves or denies the transaction request message and transmits an authorization message (with either approval or denial of the transaction request message) to the payment network server 114.
  • the payment network server 114 then forwards the authorization message to the acquirer server 113.
  • Fig. 1B shows an alternative implementation of system 100B where the message processing server 110 is integrated with the acquirer server 113.
  • the functionality of each component of the system 100B is similar to the functionality of the corresponding component of the system 100A.
  • the integrated acquirer and message processing server 117 performs the functions of both the acquirer server 113 and the message processing server 110 of Fig. 1A.
  • the integrated server 117 transmits the request to send a message (or a plurality of messages) to the payment network server 114.
  • the payment network server 114 forwards the message to the issuer server 115.
  • the issuer server 115 either approves or denies the transaction request message and transmits an authorization message (with either approval or denial of the transaction request message) to the payment network server 114.
  • the payment network server 114 then forwards the authorization message to the integrated server 117.
  • Fig. 1C shows an alternative implementation of system 100C where the message processing server 110 is integrated with the payment network server 114.
  • the functionality of each component of the system 100C is similar to the functionality of the corresponding component of the system 100A.
  • the integrated payment network and message processing server 118 performs the functions of both the payment network server 114 and the message processing server 110 of Fig. 1A.
  • the integrated server 118 transmits the request to send a message (or a plurality of messages) to the acquirer server 113.
  • the message is related to a transaction request message, it is then transmitted from the acquirer server 113 to the integrated server 118.
  • the integrated server 118 forwards the transaction request message to the issuer server 115.
  • the issuer server 115 either approves or denies the transaction request message and transmits an authorization message (with either approval or denial of the transaction request message) to the integrated server 118.
  • the integrated server 118 then forwards the authorization message to the acquirer server 113.
  • Fig. 1D shows an alternative implementation of system 100D where the message processing server 110 is integrated with the issuer server 115.
  • the functionality of each component of the system 100D is similar to the functionality of the corresponding component of the system 100A.
  • the integrated issuer and message processing server 119 performs the functions of both the issuer server 115 and the message processing server 110 of Fig. 1A.
  • the generated transaction request message is transmitted from the integrated server 119 to the acquirer server 113.
  • the message is related to a transaction request message, it is then transmitted from the acquirer server 113 to the payment network server 114.
  • the payment network server 114 forwards the transaction request message to the integrated server 119.
  • the integrated server 119 either approves or denies the transaction request message and transmits an authorization message (with either approval or denial of the transaction request message) to the payment network server 114.
  • the payment network server 114 then forwards the authorization message to the acquirer server 113.
  • the message processing server 110 will be described in relation to the system 100A. However, as will be understood by a person skilled in the art, the functions of the message processing server 110 can be performed by any of the integrated servers shown in Figs. 1B to 1D.
  • system 100 the systems 100A, 100B, 100C, and 100D will be collectively referred to as the system 100.
  • the user Before a user can use the message processing server 110, the user may have to register with the message processing server 110.
  • the registration step is called on-boarding.
  • the on-boarding process for a user is performed by the user through one of the user devices 104 or the merchant device 102.
  • the user downloads an app relating to the message processing server 110 to the user device 104 or the merchant device 102.
  • the user accesses a website relating to the message processing server 110 on the user device 104 or the merchant device 102.
  • the API is part of the software application program 1333. Once the user accesses the app or website on the user device 104, the user is able to interact with the message processing server 110 to register.
  • Details of the registration include, for example, social network account credentials, a unique name of the user account, name of the user, transaction credentials (e.g., user payment account, an authorization to use the payment account, etc. ) , user devices 104 that are classified as trusted devices, and the like.
  • a unique identifier e.g., MAC address, CPU serial number, etc.
  • the message processing server 110 creates a user account for the user which is linked to a social network account. For the purposes of a user account, it may be interchanged with a social network account.
  • the unique name of the user account can be used to refer to the user account quickly when processing a request.
  • a user may be possible for a user to create multiple user accounts on the message processing server 110. In one arrangement, it may be possible for a user to create a user account to link to more than one social network account.
  • the user account does not store the transaction credentials.
  • the transaction credentials are entered by the user when purchasing goods and/or services from a merchant.
  • a user can use an existing user account, which is issued by an issuer (e.g., a bank, a financial institution, etc. ) or an entity (e.g., Mastercard, etc. ) , to use the message processing server 110.
  • the message processing server 110 can connect into the core user management system of the issuer to enable the user to utilise the message processing server 110.
  • the user can use a Secure Remote Commerce (SRC) compatible app such as Masterpass to access the message processing server 110.
  • SRC Secure Remote Commerce
  • Fig. 2 shows a method 200 of generating and transmitting an account identifier in the system shown in Fig. 1.
  • the method 200 enables a first device (i.e., devices 102 or 104) and a second device (i.e., devices 102 or 104) to initiate a request to register to a message channel.
  • a first device i.e., devices 102 or 104
  • a second device i.e., devices 102 or 104
  • the method 200 commences at step 210 where a request to register to a message channel using a user account is initiated at a first device (i.e., the merchant device 102 or the user device 104) .
  • the message channel may be one that uses a hyperlink, a QR code, or a message app that is associated with a first social network server 103.
  • step 210 the device 102, 104 send a request to register to a message channel using a user account (one that is registered with the message processing server 110 or the first social network server 103) .
  • the request is initiated in response to user input. Examples of the user input include scanning a tag, selecting an option in a drop-down menu, requesting to send a request, and the like.
  • the method 200 proceeds from step 210 to sub-process 211.
  • Sub-process 211 determines whether the social network account (used directly or indirectly via a user account) on a device 102, 104 to send the request is permitted to do so. In other words, sub-process 211 determines whether the social network account used to send a request is a trusted account. Sub-process 211 is described below in relation to Fig. 4A.
  • sub-process 211 returns a confirmation that the request may be processed using the account.
  • the method 200 then proceeds from sub-process 211 to step 212.
  • step 212 the device 102 or 104 receives the confirmation that the request can be processed using the user account.
  • the method 200 proceeds from step 212 to step 214.
  • the device 102 or 104 receives information that the social network account is registered to the message channel.
  • the information can be credentials for the message channel and the like.
  • the information may include, among other information, the following: (1) a unique message channel name; (2) goods and/or services selection; (3) message channel credentials; and (4) an approval of the request.
  • the information may include an optional type of information of criteria relating to the message channel.
  • the criteria may include, inter alia, conditions to be satisfied before initiating a communication (e.g., sending a message or a plurality of messages) with a social network account that is managed by a second (or different) social network service and mode of sending/receiving a message.
  • the unique message channel name may be defined by the user.
  • the user may define the unique message channel name to be “coffee order” , “grocery order” , “shoes order” , and the like.
  • a request is sent to message processing server 110 to determine whether the unique message channel name is used on a message associated with the user account. If a unique message channel name is not defined by the user, an identifier of the message channel can be set as the unique message channel name.
  • the unique message channel name and the user account can then be used to continue an existing communication in sub-process 320 (see step 322 below) . That is, it is possible for a user to join an existing communication with another social network account.
  • the method 200 then proceeds from step 214 to step 216.
  • step 216 an account identifier is generated in response to a registration of the social network account to the message channel.
  • the method 200 then proceeds from step 216 to step 218.
  • a request may be sent from the user to send his account identifier to another user using a social network account that is managed by a second (or different) social network service.
  • the message processing server 110 determines whether there are criteria relating to the account identifier. The criteria are as discussed above.
  • the message processing server 110 determines if the second social network service is one that is permitted to receive the account identifier.
  • step 220 the message processing server 110 transmits the account identifier to the second social network account in response to the determination in step 219. The method 200 then concludes at the conclusion of step 220. On the other hand, if the message processing server 110 determines that the second social network service is not permitted to receive the account identifier, a rejection notification is transmitted to the device 102 or 104 at step 221.
  • Fig. 3 is a flow diagram of a method 300 of processing a message (or a plurality of messages) between different social network accounts in the system shown in Fig. 1.
  • the method 300 enables a second social network account to transmit the message to a first social network account.
  • the second social network server 103A may manage a second message channel and a second social network account while the first social network sever 103N may manage a first message channel and a first social network account.
  • the message processing server 110 may manage the first message channel, the first social network account, the second message channel and the second social network account instead.
  • the message processing server 110 receives a request, through the second message channel, to send the message to a first social network account.
  • the request may be initiated by a user, via the user device 104A, who wishes to send the message to another user who is registered with a first (or different) social network (e.g. 103N) .
  • the request may include an account identifier that is associated with the first social network account.
  • the account identifier may be generated by the message processing server 110 during on-boarding of the user (or merchant) .
  • the account identifier may be one that associates the user device to the first social network account.
  • the method 300 proceeds from step 310 to sub-process 320.
  • Sub-process 320 determines whether the second social network account is permitted to send the message.
  • the message processing server 110 may determine the second social network account is permitted to send the message by identifying the account identifier associated with the first social network account. During on-boarding, the account identifier may be transmitted to the message processing server 110 and stored in a database. The request from the device to send the message may include the account identifier. The message processing server 110 may subsequently determine whether the device is associated with the user account using the account identifier that was previously stored. Sub-process 320 is described below in relation to Fig. 4B. The method 300 then proceeds from sub-process 320 to step 315.
  • step 315 after a positive determination that the second social network account is permitted to send the message, the message processing server 110 transmits the message through the first message channel to the first social network server 103N. The method 300 then concludes at the conclusion of step 315.
  • Fig. 4A is a flow diagram of the sub-process 211 of Fig. 2 to determine that the social network account (either the first social network account or the second social network account) can be used to register to the message channel (either the first message channel or the second message channel) in the system of Fig. 1.
  • the social network account either the first social network account or the second social network account
  • the message channel either the first message channel or the second message channel
  • the message processing server 110 receives a request to register to a message channel with a social network service.
  • the request may be initiated from a user device 104 which a user may wish to purchase goods or services.
  • the request may also be initiated from a merchant device 102 which the user may use to sell goods or services online.
  • the message channel may be a first message channel managed by the first social network server 103N or a second message channel managed by the second social network server 103A.
  • the message processing server 110 determines whether the device sending the request is associated with the user account of the social network service. For example, a unique identifier (e.g., MAC address, CPU serial number, etc. ) of the user device 104 may be generated and associated with the user account during the on-boarding process with the social network service. The unique identifier may then be transmitted to the message processing server 110 and stored in a database. The request from the device to use a user account for registering to a message channel may include the unique identifier. The message processing server 110 may subsequently determine whether the device is associated with the user account using the unique identifier that was previously stored. If the message processing server 110 determines that the device is not associated with the user account, the method 211 proceeds from step 224 to step 226.
  • a unique identifier e.g., MAC address, CPU serial number, etc.
  • step 226 the message processing server 110 transmits a request to subscribe to the service provided by the message processing server 110. After the user confirms and authorizes to subscribe to the service, the message processing server 110 receives an authorization of the request to subscribe to the service in step 228. Thereafter, the method 211 proceeds from step 228 to step 230.
  • step 230 the message processing server 110 transmits a confirmation that the user account indicated in the request is permitted to register to the message channel. The method 211 then concludes at the conclusion of step 230.
  • Fig. 4B is a flow diagram of a sub-process 320 of Fig. 3 for determining whether the second social network account is permitted to send the message (or a plurality of messages) in the system of Fig. 1.
  • the method includes receiving, through a second message channel, a request to send a message to a first social network account.
  • the message processing server 110 determines whether the second social network account used to send the request is associated with the first social network account. As described previously in Fig. 3, the message processing server 110 may determine using the account identifier indicated in the request.
  • step 324 the method 320 proceeds from step 324 to step 346.
  • step 346 the message processing server 110 transmits a pairing request to associate the first and second social network accounts. This step may be carried out by sending the pairing request to the user via the device. After the user confirms and authorizes to associate the first social network account with the second social network account, the message processing server 110 receives an authorization of the pairing request at step 348. Thereafter, the method 320 proceeds from step 348 to step 326.
  • the method 320 proceeds from step 324 to 326.
  • the method includes transmitting, through a first message channel, the message for displaying. The message may be displayed to the user via the user device 104N.
  • step 328 the method includes transmitting a reply to the message through a first message channel.
  • a reply may include transaction credentials to complete a transaction and may be sent to the first social network server 103N via the first message channel.
  • the message processing server 110 processes the transaction at step 350. Accordingly, the method 320 ends after the transaction is processed and sub-process 350 is described below in relation to Fig. 5.
  • Fig. 5 is a flow diagram of a sub-process 350 of Fig. 4B for processing a transaction in the system of Fig. 1.
  • the sub-process 350 may be used to describe the steps of processing a transaction when the message is a transaction request message.
  • the transaction request may be initiated at the merchant device 102 and sent directly to the message processing server 110.
  • the message processing server 110 may receive the transaction request message via the merchant server 116.
  • the transaction request message may be initiated by user devices 104A, 104N to purchase items online using their respective devices.
  • the transaction request message may be sent to the message processing server 110 via the respective social networks 103A, 103N where each of the user devices 104A, 104N are registered.
  • the message processing server 110 transmits a reply to the message (or transaction request message) through a first message channel.
  • the reply to the message may be one that the user confirms to purchase the goods or services and provides his payment account details.
  • step 354 the method includes determining whether the reply includes payment account details.
  • Payment account details may include an account number, an account name, name of issuer, a payment account identifier and or other relevant information that is provided when payment of the goods and services is requested. The determination may be carried out by the message processing server 110 and if it is determined that the reply does not include payment account details, the message processing server 110 transmits the reply to the social network server at step 366.
  • the social network server may store the payment account details in its database and after receiving the reply at step 366, it may transmit the payment account details back to the message processing server 110.
  • step 350 proceeds from step 354 to step 356.
  • step 356 the method includes forwarding the reply to an issuer.
  • the reply may be forwarded to the issuer via the issuer server 115 and may include a unique payment account identifier associated with the payment account.
  • the method then proceeds to step 358.
  • the method includes forwarding an authorisation to the acquirer when the authorisation from the issuer is received. For example, after the issuer receives the reply in step 356, it may determine whether there are sufficient funds in the payment account. If there are sufficient funds, the issuer authorises the transaction and the message processing server 110 may receive the authorisation.
  • the message processing server 110 forwards the authorisation to the social network server in step 360.
  • the method 350 then concludes at the conclusion of step 360.
  • the message processing server 110 The message processing server 110
  • Figs. 6A and 6B depict a general-purpose computer system 1300, upon which the transaction processing server 110 described can be practiced.
  • the computer system 1300 includes a computer module 1301.
  • An external Modulator-Demodulator (Modem) transceiver device 1316 may be used by the computer module 1301 for communicating to and from a communications network 1320 via a connection 1321.
  • the communications network 1320 may be a wide-area network (WAN) , such as the Internet, a cellular telecommunications network, or a private WAN.
  • the connection 1321 is a telephone line
  • the modem 1316 may be a traditional “dial-up” modem.
  • the connection 1321 is a high capacity (e.g., cable) connection
  • the modem 1316 may be a broadband modem.
  • a wireless modem may also be used for wireless connection to the communications network 1320.
  • the communications network 1320 can be used by the transaction processing server 110 to communicate with the devices 102, 103, 104 and the servers 112, 113, 116 in the system 100.
  • the computer module 1301 typically includes at least one processor unit 1305, and a memory unit 1306.
  • the memory unit 1306 may have semiconductor random access memory (RAM) and semiconductor read only memory (ROM) .
  • the computer module 1301 also includes an interface 1308 for the external modem 1316.
  • the modem 1316 may be incorporated within the computer module 1301, for example within the interface 1308.
  • the computer module 1301 also has a local network interface 1311, which permits coupling of the computer system 1300 via a connection 1323 to a local-area communications network 1322, known as a Local Area Network (LAN) .
  • LAN Local Area Network
  • the local communications network 1322 may also couple to the wide network 1320 via a connection 1324, which would typically include a so-called “firewall” device or device of similar functionality.
  • the local network interface 1311 may comprise an Ethernet circuit card, a Bluetooth wireless arrangement or an IEEE 802.11 wireless arrangement; however, numerous other types of interfaces may be practiced for the interface 1311.
  • the I/O interfaces 1308 may afford either or both of serial and parallel connectivity, the former typically being implemented according to the Universal Serial Bus (USB) standards and having corresponding USB connectors (not illustrated) .
  • Storage devices 1309 are provided and typically include a hard disk drive (HDD) 1310. Other storage devices such as a floppy disk drive and a magnetic tape drive (not illustrated) may also be used.
  • An optical disk drive 1312 is typically provided to act as a non-volatile source of data.
  • Portable memory devices such optical disks (e.g., CD-ROM, DVD, Blu-ray Disc TM ) , USB-RAM, portable, external hard drives, and floppy disks, for example, may be used as appropriate sources of data to the system 1300.
  • the components 1305 to 1312 of the computer module 1301 typically communicate via an interconnected bus 1304 and in a manner that results in a conventional mode of operation of the computer system 1300 known to those in the relevant art.
  • the processor 1305 is coupled to the system bus 1304 using a connection 1318.
  • the memory 1306 and optical disk drive 1312 are coupled to the system bus 1304 by connections 1319. Examples of computers on which the described arrangements can be practised include IBM-PC’s and compatibles, Sun Sparcstations, Apple Mac TM or like computer systems.
  • the steps of sub-processes 211, 320, and 250 in Figs. 4A, 4B, and 5, respectively, performed by the transaction processing server 110 may be implemented using the computer system 1300.
  • the steps of sub-processes 211, 320, and 250 may be implemented as one or more software application programs 1333 executable within the computer system 1300.
  • the steps of the sub-processes 211, 320, and 250 as performed by the transaction processing server 110 are effected by instructions 1331 (see Fig. 6B) in the software 1333 that are carried out within the computer system 1300.
  • the software instructions 1331 may be formed as one or more code modules, each for performing one or more particular tasks.
  • the software may also be divided into two separate parts, in which a first part and the corresponding code modules performs the steps of the transaction processing server 110 and a second part and the corresponding code modules manage the API and corresponding user interfaces in the merchant device 102, the user devices 104, the transaction device 103.
  • the second part of the software manages the interaction between (a) the first part and (b) any one of the merchant device 102, the user devices 104, and the transaction device 103.
  • the software may be stored in a computer readable medium, including the storage devices described below, for example.
  • the software is loaded into the computer system 1300 from the computer readable medium, and then executed by the computer system 1300.
  • a computer readable medium having such software or computer program recorded on the computer readable medium is a computer program product.
  • the use of the computer program product in the computer system 1300 preferably effects an advantageous apparatus for a transaction processing server 110.
  • the software 1333 is typically stored in the HDD 1310 or the memory 1306.
  • the software is loaded into the computer system 1300 from a computer readable medium, and executed by the computer system 1300.
  • the software 1333 may be stored on an optically readable disk storage medium (e.g., CD-ROM) 1325 that is read by the optical disk drive 1312.
  • a computer readable medium having such software or computer program recorded on it is a computer program product.
  • the use of the computer program product in the computer system 1300 preferably effects an apparatus for a transaction processing server 110.
  • the application programs 1333 may be supplied to the user encoded on one or more CD-ROMs 1325 and read via the corresponding drive 1312, or alternatively may be read by the user from the networks 1320 or 1322. Still further, the software can also be loaded into the computer system 1300 from other computer readable media.
  • Computer readable storage media refers to any non-transitory tangible storage medium that provides recorded instructions and/or data to the computer system 1300 for execution and/or processing.
  • Examples of such storage media include floppy disks, magnetic tape, CD-ROM, DVD, Blu-ray TM Disc, a hard disk drive, a ROM or integrated circuit, USB memory, a magneto-optical disk, or a computer readable card such as a PCMCIA card and the like, whether or not such devices are internal or external of the computer module 1301.
  • Examples of transitory or non-tangible computer readable transmission media that may also participate in the provision of software, application programs, instructions and/or data to the computer module 1301 include radio or infra-red transmission channels as well as a network connection to another computer or networked device, and the Internet or Intranets including e-mail transmissions and information recorded on Websites and the like.
  • the second part of the application programs 1333 and the corresponding code modules mentioned above may be executed to implement one or more API of the transaction processing server 110 with associated graphical user interfaces (GUIs) to be rendered or otherwise represented upon the display of the merchant device 102, the user devices 104, and the transaction device 103.
  • GUIs graphical user interfaces
  • a user of the merchant device 102, the user devices 104, and the transaction device 103 and the application may manipulate the interface presented on the display of the merchant device 102, the user devices 104, and the transaction device 103 in a functionally adaptable manner to provide controlling commands and/or input to the applications associated with the GUI (s) .
  • Other forms of functionally adaptable user interfaces may also be implemented, such as an audio interface utilizing speech prompts output via loudspeakers and user voice commands input via a microphone.
  • Fig. 6B is a detailed schematic block diagram of the processor 1305 and a “memory” 1334.
  • the memory 1334 represents a logical aggregation of all the memory modules (including the HDD 1309 and semiconductor memory 1306) that can be accessed by the computer module 1301 in Fig. 6A.
  • a power-on self-test (POST) program 1350 executes.
  • the POST program 1350 is typically stored in a ROM 1349 of the semiconductor memory 1306 of Fig. 6A.
  • a hardware device such as the ROM 1349 storing software is sometimes referred to as firmware.
  • the POST program 1350 examines hardware within the computer module 1301 to ensure proper functioning and typically checks the processor 1305, the memory 1334 (1309, 1306) , and a basic input-output systems software (BIOS) module 1351, also typically stored in the ROM 1349, for correct operation. Once the POST program 1350 has run successfully, the BIOS 1351 activates the hard disk drive 1310 of Fig. 6A.
  • BIOS basic input-output systems software
  • Activation of the hard disk drive 1310 causes a bootstrap loader program 1352 that is resident on the hard disk drive 1310 to execute via the processor 1305.
  • the operating system 1353 is a system level application, executable by the processor 1305, to fulfil various high level functions, including processor management, memory management, device management, storage management, software application interface, and generic user interface.
  • the operating system 1353 manages the memory 1334 (1309, 1306) to ensure that each process or application running on the computer module 1301 has sufficient memory in which to execute without colliding with memory allocated to another process. Furthermore, the different types of memory available in the system 1300 of Fig. 6A must be used properly so that each process can run effectively. Accordingly, the aggregated memory 1334 is not intended to illustrate how particular segments of memory are allocated (unless otherwise stated) , but rather to provide a general view of the memory accessible by the computer system 1300 and how such is used.
  • the processor 1305 includes a number of functional modules including a control unit 1339, an arithmetic logic unit (ALU) 1340, and a local or internal memory 1348, sometimes called a cache memory.
  • the cache memory 1348 typically includes a number of storage registers 1344 -1346 in a register section.
  • One or more internal busses 1341 functionally interconnect these functional modules.
  • the processor 1305 typically also has one or more interfaces 1342 for communicating with external devices via the system bus 1304, using a connection 1318.
  • the memory 1334 is coupled to the bus 1304 using a connection 1319.
  • the application program 1333 includes a sequence of instructions 1331 that may include conditional branch and loop instructions.
  • the program 1333 may also include data 1332 which is used in execution of the program 1333.
  • the instructions 1331 and the data 1332 are stored in memory locations 1328, 1329, 1330 and 1335, 1336, 1337, respectively.
  • a particular instruction may be stored in a single memory location as depicted by the instruction shown in the memory location 1330.
  • an instruction may be segmented into a number of parts each of which is stored in a separate memory location, as depicted by the instruction segments shown in the memory locations 1328 and 1329.
  • the processor 1305 is given a set of instructions which are executed therein.
  • the processor 1305 waits for a subsequent input, to which the processor 1305 reacts to by executing another set of instructions.
  • Each input may be provided from one or more of a number of sources, including data generated by one or more of the input devices 1302, 1303, data received from an external source across one of the networks 1320, 1302, data retrieved from one of the storage devices 1306, 1309 or data retrieved from a storage medium 1325 (e.g., the database 109) inserted into the corresponding reader 1312, all depicted in Fig. 6A.
  • the execution of a set of the instructions may in some cases result in output of data. Execution may also involve storing data or variables to the memory 1334.
  • the disclosed transaction processing server 110 arrangements use input variables 1354, which are stored in the memory 1334 in corresponding memory locations 1355, 1356, 1357.
  • the payment network server 108 arrangements produce output variables 1361, which are stored in the memory 1334 in corresponding memory locations 1362, 1363, 1364.
  • Intermediate variables 1358 may be stored in memory locations 1359, 1360, 1366 and 1367.
  • each fetch, decode, and execute cycle comprises:
  • a fetch operation which fetches or reads an instruction 1331 from a memory location 1328, 1329, 1330;
  • a further fetch, decode, and execute cycle for the next instruction may be executed.
  • a store cycle may be performed by which the control unit 1339 stores or writes a value to a memory location 1332.
  • Each step of sub-processes 211, 320, and 250, as performed by the transaction processing server 110, is associated with one or more segments of the program 1333 and is performed by the register section 1344, 1345, 1347, the ALU 1340, and the control unit 1339 in the processor 1305 working together to perform the fetch, decode, and execute cycles for every instruction in the instruction set for the noted segments of the program 1333.
  • the structural context of the computer system 1300 i.e., the transaction processing server 110
  • the structural context of the computer system 1300 is presented merely by way of example. Therefore, in some arrangements, one or more features of the server 1300 may be omitted. Also, in some arrangements, one or more features of the server 1300 may be combined together. Additionally, in some arrangements, one or more features of the server 1300 may be split into one or more component parts.
  • Fig. 7 shows an alternative implementation of the message processing server 110 (i.e., the computer system 1300) .
  • the message processing server 110 may be generally described as a physical device comprising at least one processor 702 and at least one memory 704 including computer program codes.
  • the at least one memory 704 and the computer program codes are configured to, with the at least one processor 702, cause the message processing server 110 to perform the operations described in sub-processes 211, 320, and 350.
  • the message processing server 110 may also include a message processing module 706 and a user account module 708.
  • the memory 704 stores computer program code that the processor 702 compiles to have each of the modules 706 and 708 performs their respective functions.
  • the message module 706 performs the function of communicating with the devices 102, 103, 104 to receive requests and to transmit data.
  • the user account module 708 performs the function of registering user accounts and performing sub-processes 211, 320, and 250.
  • the arrangements described are applicable to the computer and data processing industries and particularly for the conducting a transaction across a plurality of devices.
  • the user X has a social network account on social network service A and has a friend Y who has a social network account with social network service B. Both user X and Y have their own personal mobile device and have registered their respective social network accounts with the message processing server 110.
  • X wishes to send a message to Y asking Y to meet him in town for a cup of coffee.
  • X opens an application of social network service A installed in his mobile phone and sends his message.
  • the message processing server 110 receives the message via a server of social network service A and routes the message to a server of social network service B.
  • the server of social network service B forwards the message to an application installed in Y’s mobile phone which displays and notifies Y of X’s message.
  • Y agrees to meet X and subsequently replies to X’s message by using the application installed in his mobile phone.
  • Y’s reply is sent to social network service B’s server which is then routed to the message processing server 110.
  • Y’s reply is then forwarded to the application installed in X’s mobile phone which displays and notifies X of Y’s reply.
  • the user X has a social network account on social network service A.
  • X wishes to purchase a laptop worth $1000 from merchant Y.
  • X visits merchant Y’s shop and uses the Point-Of-Sale (POS) terminal at Y’s shop to send a transaction request message to purchase the laptop.
  • the transaction request message is routed to the message processing server 110 and a reply is sent to the POS terminal requesting for X’s payment account details.
  • X may wish to purchase the laptop online and visits Y’s online shop.
  • X selects the laptop and sends a transaction request message to purchase the laptop.
  • Y’s server receives the transaction request message which is then routed to the message processing server 110.
  • a reply is sent requesting for X’s payment account details.
  • X replies (either through the POS terminal or Y’s online portal) by confirming to purchase the laptop and providing his payment account details.
  • the message processing server 110 determines that the reply includes payment account details and forwards the transaction request message and x’s payment account details to the acquirer server 113, the payment network server 114 and the issuer server 115.
  • the issuer determines that there is sufficient funds in X’s account to purchase the $1000 laptop and authorizes the transaction.
  • the issuer server 115 sends an authorization message to the acquirer server 113 and the message processing server 110.
  • the message processing server 110 may send the authorization to the social network service A which may include the transaction in a summary list of the items X had purchased in the last month.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computing Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • General Engineering & Computer Science (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

According to a first aspect, there is a provided a system for processing a message between a first social network account on a first social network service and a second social network account on a second social network service that is different from the first social network service, the first social network service having a first message channel and the second social network service having a second message channel, the system comprising: a server having at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the server at least to: receive, through the second message channel, a request to send the message to the first social network account, the request including the message to be sent, a first account identifier associated with the first social network account and second account information associated with the second social network account; determine whether the second social network account is permitted to send the message to the first social network account based on the first account identifier; and transmit, through the first message channel, the message for displaying based on the determination of whether the second social network account is permitted to send the message to the first social network account.

Description

A Method and System for Processing a Plurality of Messages between Different Social Network Services Technical Field
The present invention relates generally to technology and, in particular, to provide a method and system for processing a plurality of messages among social network accounts on different social network services, namely the first social network service and the second social network service.
Background
Social Network Services have opened up many new avenues to building social networks by allowing users to share information online and connect with a wide range of different users. Social Network Services each maintains profiles created by users of the specific service. A user's profile allows other users of the service to learn about the user. A user's profile includes, for example, information about the user, pictures posted by the user, a listing of the user's friends, and comments posted by the user and the user's friends. The amount and types of information that can be shared and used in these Social Network Services is vast, which may also provide opportunities for e-commerce.
Social network services allow users to communicate with other users about any topic. However, this is limited to users who are subscribed to the same social network service.
Often, social network services do not validate the appropriateness of the content included in communications between users. Some users take advantage of this lack of validation to plan events or activities that are illegal or not allowed by a supervisor (e.g., a parent) .
Further, malicious entities take advantage of the lack of validation by using the social network services to obtain personal information from users. For example, a malicious entity can deceive users into believing it is a trustworthy entity and have users provide their credit card numbers, social security numbers, and/or passwords. Accordingly, there is a need in the art for ways to validate and facilitate of communications among different social network services.
Summary
According to a first aspect of the present disclosure, there is provided a system for processing a message between a first social network account on a first social network service and  a second social network account on a second social network service that is different from the first social network service, the first social network service having a first message channel and the second social network service having a second message channel, the system comprising: a server having at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the server at least to: receive, through the second message channel, a request to send the message to the first social network account, the request including the message to be sent, a first account identifier associated with the first social network account and second account information associated with the second social network account; determine whether the second social network account is permitted to send the message to the first social network account based on the first account identifier; and transmit, through the first message channel, the message for displaying based on the determination of whether the second social network account is permitted to send the message to the first social network account.
According to a second aspect of the present disclosure, there is provided a method for processing a message between a first social network account on a first social network service and a second social network account on a second social network service that is different from the first social network service, the first social network service having a first message channel and the second social network service having a second message channel, the method comprising: receiving, through the second message channel, a request to send the message to the first social network account, the request including a first account identifier associated with the first social network account and second account information associated with the second social network account; determining whether the second social network account is permitted to send the message to the first social network account based on the first account identifier; and transmitting, through the first message channel, the message for displaying based on the determination of whether the second social network account is permitted to send the message to the first social network account.
Brief Description of the Drawings
At least one embodiment of the present invention will now be described with reference to the drawings and appendices, in which:
Fig. 1A shows a system for processing a plurality of messages across a plurality of social network servers;
Figs. 1B to 1D show alternative embodiments of the system shown in Fig. 1A;
Fig. 2 is a flow diagram of a method of generating and transmitting an account identifier in the system shown in Fig. 1A;
Fig. 3 is a flow diagram of a method of processing a plurality of messages between different social network accounts in the system shown in Fig. 1A;
Fig. 4A is a flow diagram of a sub-process of determining the social network account can be used to register to the message channel in the system of Fig. 1A;
Fig. 4B is a flow diagram of a sub-process of determining whether the second social network account is permitted to send the plurality of messages in the system of Fig. 1A;
Fig. 5 is a flow diagram of a sub-process of processing a transaction in the system of Fig. 1A;
Figs. 6A and 6B form a schematic block diagram of a general purpose computer system upon which the message processing server of Fig. 1A can be practiced; and
Fig. 7 shows an example of a computing device to realize the message processing server shown in Fig. 1A.
Detailed Description including Best Mode
Terms Description
Payment Network Server –The payment network server is a server that hosts software application programs for processing payment of a transaction request message. The payment network server is a typical payment network server that is used to process transaction request messages. The payment network server communicates with a social network server (one that is managed by a social network service if required) , and any other servers (e.g., an issuer server, an acquirer server) to facilitate payment of transaction request messages generated by the message processing server 110. Payment network servers may use a variety of different protocols and procedures in order to process the transaction request messages. Transactions that may be performed via a payment network server include product or service purchases, credit purchases, debit transactions, fund transfers, account withdrawals, etc. Payment network servers may be configured to process transactions via cash-substitutes, which may include payment cards, letters of credit, checks, payment accounts, etc. The payment network server is operated by a service provider such as Mastercard. For example, the payment network server may be Banknet  network operated by Mastercard. The service provider (e.g. Mastercard) may be an entity (e.g. a company or organization) who operates to process transactions, clear and settle funds for payments between two entities (e.g. two banks) . The payment network server may include one or more computing devices that are used for processing transactions.
A social network account –an account of a registered user. The social network account can be used to display a user’s profile including, for example, information about the user, pictures posted by the user, a listing of the user's friends, and comments posted by the user and the user's friends. The amount and types of information that can be shared and used in these social network services is vast. The social network account may include a payment account of the registered user.
A user device –a device associated with a social network account. A user device may be used to sign in to a social network account. The user device may also be used to purchase a merchant’s product by initiating a transaction. In specific implementations, the user device may be a handheld or portable or mobile device carried or used by the target user, or may refer to other types of electronic devices such as a personal computer, a land-line telephone or an interactive voice response (IVR) system and the like. The mobile device may be a device, such as a mobile phone, a laptop computer, a personal digital computer (PDA) , a mobile computer, a portable music player (such as an iPod TM and the like) .
Transaction –A transaction relates to an agreement carried out between a customer and a merchant to exchange asset (i.e., goods or services) for payment.
User –a user may be any suitable type of entity associated with a payment account, which may include a person, family, company, corporation, governmental entity, and the like. The term user is used herein to identify an entity performing or approving a purchase in a transaction. The user may provide the fund for the transaction.
Merchant –a merchant may be any suitable type of entity associated with a payment account, which may include a person, family, company, corporation, governmental entity, and the like. The term merchant is used herein to identify an entity performing a sale in a transaction and receiving the fund for the transaction.
Transaction credentials –Transaction credentials are credentials provided by either a user or a merchant to perform a transaction. Examples of the transaction credentials include a payment account, a password associated with the payment account, and any other data that an  acquirer provider or an issuer provider need to authorize a transaction request message generated from the transaction.
A message –information to be shared from one user with another user. This applies to one user having a social network account, managed by a first social network service, sending a message to another user having a social network account managed by a different social network service, i.e. a second social network service. Sending a message includes initiating a communication and continuing an existing communication.
A message channel –a means for a message to be sent or transmitted. A message channel is one that can receive an in-band or out-of-band message. An out-of-band message refers to a message that is sent via a communication path, type or protocol which is different to the current communication path, type or protocol. Therefore, if message flow thus far has been via the Transmission Control Protocol/Internet Protocol (TCP/IP) , the message may be sent via SMS so as to be an out-of-band message. In other words, an out-of-band message typically makes use of two separate networks which work simultaneously to verify a user. For example, a user may initiate a request to send a message via a first social network service and another user or an intended recipient may be informed of such a message via a second message channel with second network. Advantageously, an out-of-band message may be used to allow communication between users having accounts with different social network services, namely the first social network service and the second social network service.
A completed transaction –A transaction that has sufficient details (e.g., a user approval, transaction credentials, etc. ) to generate a transaction request message. The transaction request message can then be forwarded to an acquirer server, the payment network server, and an issuer server, such that payment of the transaction request message can be facilitated.
Payment Account –A payment account that is used to provide or receive fund for a transaction. Examples of a payment account are a check account, a savings account, a credit account, a virtual payment account, a payment card, and the like. The payment card refers to any suitable transaction cards, such as credit cards, debit cards, prepaid cards, charge cards, membership cards, promotional cards, frequent flyer cards, identification cards, gift cards, and/or any other device that may hold payment account information, such as mobile phones, Smartphones, personal digital assistants (PDAs) , key fobs, and/or computers.
A payment account is associated with either a customer or a merchant. A payment account associated with a customer is issued by an issuer in a transaction. On the other hand, a payment account associated with a merchant is issued by an acquirer in a transaction.
Example Implementations
Where reference is made in any one or more of the accompanying drawings to steps and/or features, which have the same reference numerals, those steps and/or features have for the purposes of this description the same function (s) or operation (s) , unless the contrary intention appears.
Fig. 1A shows a system 100A comprising user devices 104A to 104N, a merchant device 102, a social network server 103A to 103S (managed by a social network service) , a merchant server 116, an acquirer server 113, a payment server 114, an issuer server 115, and a message request message processing server 110.
The message processing server 110
The message processing server 110 is a server that hosts software application programs 1333 (see Figs. 6A and 6B) to manage user accounts belonging to respective users and transactions. Functions of the message processing server 110 will be discussed below in more detail in relation to Figs. 2 to 4. The structural context of the transaction processing server 110 is discussed below in relation to Figs. 6A and 6B.
In the illustrative embodiment, the message processing server 110 provides an interface to enable communication with each of the devices 104A to 104N, 103A to 103S and 102 and the  servers  113, 114, 115. The message processing server 110 is shown in Figs. 1A to 1D to be connected to the collective user devices 104A to 104N and the social network servers 103A to 103S for simplicity sake. The message processing server 110 is connected to any one of the user devices 104A to 104N and any one of the social network servers 103A to 103S.
The message processing server 110 provides an application programming interface ( “API” ) to facilitate such communication. Such APIs may be part of a user interface that may include graphical user interfaces (GUIs) , Web-based interfaces, programmatic interfaces such as application programming interfaces (APIs) and/or sets of remote procedure calls (RPCs) corresponding to interface elements, messaging interfaces in which the interface elements  correspond to messages of a communication protocol, and/or suitable combinations thereof. Examples of APIs include the Representational State Transfer (REST) API, and the like.
The message processing server 110 stores and manages user accounts of users that are registered to use the services provided by the message processing server 110. The message processing server 110 provides a service to enable a user to send a message (or a plurality of messages) to another user using a different social network account (e.g., one that is administered by another social network service) . In various embodiments, sending a message (or a plurality of messages) includes initiating and continuing a communication with a user using a different social network account. The method of sending a message (or a plurality of messages) across different social network accounts will be described hereinafter.
In an alternative arrangement, the message processing server 110 is part of a payment network server 114 (as shown in Fig. 1C) . For example, the message processing server 110 may also be a payment network server 114 that is configured to facilitate payment between a user of the user devices 104A to 104N and a merchant of the merchant device 102.
In another alternative arrangement, the message processing server 110 is part of an acquirer server 113 (as shown in Fig. 1B) or part of an issuer server 115 (as shown in Fig. 1D) .
In one arrangement, the message processing server 110 is compatible with existing payment apps such as Masterpass, Qkr! , payment gateways (such as Mastercard Payment Gateway Service) , and the like. In another arrangement, the message processing server 110 is an additional function on a payment app like Masterpass or Qkr! .
The merchant server 116
The merchant server 116 is a server that hosts software application programs to manage the user accounts belonging to respective users. The merchant server 116 performs this function simultaneously with the message processing server 110 to improve the security of the user account and to store merchant specific information of the user account. For example, the user account stored in the merchant server 116 may contain information regarding favourite items and/or services that the user frequently purchases from the merchant. In another example, the user account in the merchant server 116 may contain information regarding items and/or services that the user wishes the merchant to provide. The merchant server 116 connects with the message processing server 110. As discussed above, the merchant server 116 communicates with the message processing server 110.
In one alternative arrangement, the merchant server 116 can be integrated in the message processing server 110.
The merchant server 116 also hosts software application programs to manage goods and/or services that a merchant sells. Any of the  devices  102, 103, 104A to 104N can access the merchant server 116, via the message processing server 110, to review and select products and/or services that are offered by a merchant. There are other merchant servers 116 associated with respective merchants, but these other merchant servers 116 are not shown for ease of description.
In one arrangement, the merchant server 116 also connects to the merchant device 102 to enable the merchant device 102 to retrieve details of products and/or services offered by the merchant.
The merchant server 116 is accessible by any of the devices 102, 103, 104 via the message processing server 110.
The merchant device 102
The merchant device 102 is a device belonging to a merchant. The merchant device 102 is used to perform a transaction and the merchants offer goods and/or services. Examples of the merchant device 102 are tablets, laptops, desktop computers, smartphones, point-of-sales terminals, an interactive robot, and the like. The merchant device 102 connects with the message processing server 110 and may connect directly with the merchant server 116. As described above, the merchant device 102 can communicate with the message processing server 110.
The present disclosure only shows one merchant device 102 for ease of description. However, there may be multiple merchant devices 102 associated with a merchant. There are also multiple merchants (not shown) in the system 100.
A user can use the merchant device 102 to initiate or complete a transaction to purchase goods and/or services using a user account by sending a message (or a plurality of messages) , once the user is able to send or receive a message with a user account registered to a second (or different) social network service. The merchant device 102 may be located at a store owned by the merchant.
The merchant device 102 may also be used to send a request to register to a message channel with a social network server. The sending of the request is described below in relation to  step 224 (see Fig. 4A) . The merchant device 102 is shown in Figs. 1A to 1D to be connected to the collective user devices 104A to 104N for simplicity sake.
The social network server 103
The social network server 103 is a server that hosts software application programs for receiving messages from a user having a social network account. The messages may be associated with a transaction request which will be forwarded to the acquirer server 113.
The social network server 103 is connected to the message processing server 110 to receive the messages (e.g., transaction request messages) . The social network server 103 generally is associated with a social network service who may be an entity (e.g. a company or organization) which issues (e.g. establishes, manages, administers) a social network account. In addition, the social network service may be an on-line, computer implemented platform on which users build social networks or social relationship with other people or entities who share similar personal or career interests, activities, backgrounds or real-life connections. For example, the social network server can be used to create a social network account that is used to display a user’s profile including information about the user, pictures posted by the user and a listing of the user’s friends. The social network service may be operated on one or more servers, or the like. The social network server 103 may include one or more computing devices that are used to establish communication with another server by exchanging messages with and/or passing information to the  other servers  110 and 114.
The user devices 104A to 104N
The user devices 104A to 104N are devices that belong to a user who is registered with the message processing server 110. The user also has a social network account that is managed by a social network server 103. Such a user has a user account with the message processing server 110. The registration (i.e., on-boarding) of the user with the message processing server 110 is described below.
Any of the user devices 104A to 104N can be used to register a social network account (described below in relation to the on-boarding of the user) .
Examples of the user devices 104A to 104N are tablets, laptops, desktop computers, smartphones, smart speakers, and the like. The user devices 104A to 104N respectively connect  with the message processing server 110. Hereinafter, the user devices 104A to 104N are collectively referred to as the user devices 104 (when referring to all of the user devices) and the user device 104 (when referring to a single user device) . As described above, the user devices 104 can communicate with the message processing server 110.
The term “user devices 104” refers to devices that are registered with a user account and is approved to process a message (or a plurality of messages) using the user account that the user devices 104 are associated with.
As described above, any of the user devices 104 may connect to another user device 104 or the merchant device 102 to process a message (or a plurality of messages) .
The acquirer server 113
The acquirer server 113 is a server that hosts software application programs for receiving transaction request messages, which are associated with completed transactions, from the message processing server 110 and forwarding the received transaction request messages to the payment network server 114.
The acquirer server 113 is connected to the message processing server 110 to receive the messages. The acquirer server 113, in turn, is in communication with the payment network server 114.
The acquirer server 113 generally is associated with an acquirer who may be an entity (e.g. a company or organization) which issues (e.g. establishes, manages, administers) a payment account (e.g. a financial bank payment account) of the merchant. Examples of the acquirer include a bank and/or other financial institution. The acquirer server 113 may include one or more computing devices that are used to establish communication with another server by exchanging messages with and/or passing information to the  other servers  110 and 114.
The payment network server 114
The payment network server 114 is a server that hosts software application programs for processing payment of transactions. The payment server 114 is a typical payment network server that is used to process transaction request messages. The payment network server 114 is connected to the acquirer server 113 to receive transaction request messages. The payment network server 114 also communicates with the social network server 103 (if required) to process  any transaction request messages received from the acquirer server 113. The payment network server 114 is also connected to the issuer server 115 to forward the received transaction request messages to the issuer server 115. The payment network server 115 then receives authorization responses to the forwarded transaction request messages from the issuer server 115. More details may be found in Fig. 5.
The issuer server 115
The issuer server 115 is a server that hosts software application programs for receiving transaction request messages from the payment network server 114, processing the transaction request messages, and transmitting authorization responses to the respective transaction request messages to the payment network server 114.
The issuer server 115 is connected to the payment network server 114 to receive the transaction request messages.
The issuer server 115 generally is associated with an issuer and may include one or more computing devices that are used to process a transaction request message. The issuer may be an entity (e.g. a company or organization) which issues (e.g. establishes, manages, administers) a payment account (e.g. a financial bank payment account) of a user.
Function of the system 100A
The system 100A enables a transaction to be initiated by a first device (e.g., the user devices 104, the merchant device 102) using the message processing server 110. A second device (e.g., the user devices 104, the merchant device 102) can be used to initiate a request to send a message to a first device (e.g., another user device 104 or the merchant device 102) . It can be appreciated that a plurality of messages may also be sent between the first device and the second device. The first device which is used to connect to the first social network account may be used to continue to send a further message or a reply upon receipt of the message sent from the second device.
If the message relates to a transaction request message, the message processing server 110 generates a transaction request message and transmits the transaction request message to the acquirer server 113. The acquirer server 113 then forwards the transaction request message to the payment network server 114. The payment network server 114, in turn, forwards the transaction request message to the issuer server 115. The issuer server 115 either approves or  denies the transaction request message and transmits an authorization message (with either approval or denial of the transaction request message) to the payment network server 114. The payment network server 114 then forwards the authorization message to the acquirer server 113.
The process of using the system 100A will be described below in more detail in relation to Figs. 2 to 5.
Alternative Implementations
Fig. 1B shows an alternative implementation of system 100B where the message processing server 110 is integrated with the acquirer server 113. The functionality of each component of the system 100B is similar to the functionality of the corresponding component of the system 100A. However, the integrated acquirer and message processing server 117 performs the functions of both the acquirer server 113 and the message processing server 110 of Fig. 1A.
Similar to the system 100A, the integrated server 117 transmits the request to send a message (or a plurality of messages) to the payment network server 114.
If the message is related to a transaction request message, the payment network server 114, in turn, forwards the message to the issuer server 115. The issuer server 115 either approves or denies the transaction request message and transmits an authorization message (with either approval or denial of the transaction request message) to the payment network server 114. The payment network server 114 then forwards the authorization message to the integrated server 117.
Fig. 1C shows an alternative implementation of system 100C where the message processing server 110 is integrated with the payment network server 114. The functionality of each component of the system 100C is similar to the functionality of the corresponding component of the system 100A. However, the integrated payment network and message processing server 118 performs the functions of both the payment network server 114 and the message processing server 110 of Fig. 1A.
Similar to the system 100A, the integrated server 118 transmits the request to send a message (or a plurality of messages) to the acquirer server 113.
If the message is related to a transaction request message, it is then transmitted from the acquirer server 113 to the integrated server 118. The integrated server 118, in turn, forwards the  transaction request message to the issuer server 115. The issuer server 115 either approves or denies the transaction request message and transmits an authorization message (with either approval or denial of the transaction request message) to the integrated server 118. The integrated server 118 then forwards the authorization message to the acquirer server 113.
Fig. 1D shows an alternative implementation of system 100D where the message processing server 110 is integrated with the issuer server 115. The functionality of each component of the system 100D is similar to the functionality of the corresponding component of the system 100A. However, the integrated issuer and message processing server 119 performs the functions of both the issuer server 115 and the message processing server 110 of Fig. 1A. Similar to the system 100A, the generated transaction request message is transmitted from the integrated server 119 to the acquirer server 113.
If the message is related to a transaction request message, it is then transmitted from the acquirer server 113 to the payment network server 114. The payment network server 114, in turn, forwards the transaction request message to the integrated server 119. The integrated server 119 either approves or denies the transaction request message and transmits an authorization message (with either approval or denial of the transaction request message) to the payment network server 114. The payment network server 114 then forwards the authorization message to the acquirer server 113.
Hereinafter, for ease of description, the message processing server 110 will be described in relation to the system 100A. However, as will be understood by a person skilled in the art, the functions of the message processing server 110 can be performed by any of the integrated servers shown in Figs. 1B to 1D.
Hereinafter, the  systems  100A, 100B, 100C, and 100D will be collectively referred to as the system 100.
On-Boarding of Users and Merchants
Before a user can use the message processing server 110, the user may have to register with the message processing server 110. The registration step is called on-boarding.
The on-boarding process for a user is performed by the user through one of the user devices 104 or the merchant device 102. In one arrangement, the user downloads an app relating to the message processing server 110 to the user device 104 or the merchant device 102. In  another arrangement, the user accesses a website relating to the message processing server 110 on the user device 104 or the merchant device 102. As described below in relation to Figs. 6A and 6B, the API is part of the software application program 1333. Once the user accesses the app or website on the user device 104, the user is able to interact with the message processing server 110 to register.
Details of the registration include, for example, social network account credentials, a unique name of the user account, name of the user, transaction credentials (e.g., user payment account, an authorization to use the payment account, etc. ) , user devices 104 that are classified as trusted devices, and the like. In one arrangement, a unique identifier (e.g., MAC address, CPU serial number, etc. ) of the user devices 104 are associated with the user account. Once on-boarded, the message processing server 110 creates a user account for the user which is linked to a social network account. For the purposes of a user account, it may be interchanged with a social network account. The unique name of the user account can be used to refer to the user account quickly when processing a request.
In one arrangement, it may be possible for a user to create multiple user accounts on the message processing server 110. In one arrangement, it may be possible for a user to create a user account to link to more than one social network account.
In one arrangement, the user account does not store the transaction credentials. In this arrangement, the transaction credentials are entered by the user when purchasing goods and/or services from a merchant.
In one alternative arrangement, a user can use an existing user account, which is issued by an issuer (e.g., a bank, a financial institution, etc. ) or an entity (e.g., Mastercard, etc. ) , to use the message processing server 110. In this alternative arrangement, the message processing server 110 can connect into the core user management system of the issuer to enable the user to utilise the message processing server 110. Further, in this alternative arrangement, the user can use a Secure Remote Commerce (SRC) compatible app such as Masterpass to access the message processing server 110.
Initiating a transaction
Fig. 2 shows a method 200 of generating and transmitting an account identifier in the system shown in Fig. 1. The method 200 enables a first device (i.e., devices 102 or 104) and a second device (i.e., devices 102 or 104) to initiate a request to register to a message channel.
The method 200 commences at step 210 where a request to register to a message channel using a user account is initiated at a first device (i.e., the merchant device 102 or the user device 104) . The message channel may be one that uses a hyperlink, a QR code, or a message app that is associated with a first social network server 103.
In step 210, the device 102, 104 send a request to register to a message channel using a user account (one that is registered with the message processing server 110 or the first social network server 103) . The request is initiated in response to user input. Examples of the user input include scanning a tag, selecting an option in a drop-down menu, requesting to send a request, and the like. The method 200 proceeds from step 210 to sub-process 211.
Sub-process 211 determines whether the social network account (used directly or indirectly via a user account) on a device 102, 104 to send the request is permitted to do so. In other words, sub-process 211 determines whether the social network account used to send a request is a trusted account. Sub-process 211 is described below in relation to Fig. 4A.
If the social network account that is used is associated with the message processing server 110, sub-process 211 returns a confirmation that the request may be processed using the account. The method 200 then proceeds from sub-process 211 to step 212.
In step 212, the device 102 or 104 receives the confirmation that the request can be processed using the user account. The method 200 proceeds from step 212 to step 214.
In step 214, the device 102 or 104 receives information that the social network account is registered to the message channel. The information can be credentials for the message channel and the like. The information may include, among other information, the following: (1) a unique message channel name; (2) goods and/or services selection; (3) message channel credentials; and (4) an approval of the request.
In one arrangement, the information may include an optional type of information of criteria relating to the message channel. The criteria may include, inter alia, conditions to be satisfied before initiating a communication (e.g., sending a message or a plurality of messages) with a social network account that is managed by a second (or different) social network service and mode of sending/receiving a message.
The unique message channel name may be defined by the user. For example, the user may define the unique message channel name to be “coffee order” , “grocery order” , “shoes order” ,  and the like. When defining a unique message channel name, a request is sent to message processing server 110 to determine whether the unique message channel name is used on a message associated with the user account. If a unique message channel name is not defined by the user, an identifier of the message channel can be set as the unique message channel name. The unique message channel name and the user account can then be used to continue an existing communication in sub-process 320 (see step 322 below) . That is, it is possible for a user to join an existing communication with another social network account. The method 200 then proceeds from step 214 to step 216.
In step 216, an account identifier is generated in response to a registration of the social network account to the message channel. The method 200 then proceeds from step 216 to step 218.
In step 218, a request may be sent from the user to send his account identifier to another user using a social network account that is managed by a second (or different) social network service. The message processing server 110 determines whether there are criteria relating to the account identifier. The criteria are as discussed above. In step 219, the message processing server 110 determines if the second social network service is one that is permitted to receive the account identifier.
In step 220, the message processing server 110 transmits the account identifier to the second social network account in response to the determination in step 219. The method 200 then concludes at the conclusion of step 220. On the other hand, if the message processing server 110 determines that the second social network service is not permitted to receive the account identifier, a rejection notification is transmitted to the device 102 or 104 at step 221.
Fig. 3 is a flow diagram of a method 300 of processing a message (or a plurality of messages) between different social network accounts in the system shown in Fig. 1. The method 300 enables a second social network account to transmit the message to a first social network account. The second social network server 103A may manage a second message channel and a second social network account while the first social network sever 103N may manage a first message channel and a first social network account. In alternative embodiments, the message processing server 110 may manage the first message channel, the first social network account, the second message channel and the second social network account instead.
In step 310, the message processing server 110 receives a request, through the second message channel, to send the message to a first social network account. The request may be  initiated by a user, via the user device 104A, who wishes to send the message to another user who is registered with a first (or different) social network (e.g. 103N) . The request may include an account identifier that is associated with the first social network account. The account identifier may be generated by the message processing server 110 during on-boarding of the user (or merchant) . The account identifier may be one that associates the user device to the first social network account. The method 300 proceeds from step 310 to sub-process 320.
Sub-process 320 determines whether the second social network account is permitted to send the message. The message processing server 110 may determine the second social network account is permitted to send the message by identifying the account identifier associated with the first social network account. During on-boarding, the account identifier may be transmitted to the message processing server 110 and stored in a database. The request from the device to send the message may include the account identifier. The message processing server 110 may subsequently determine whether the device is associated with the user account using the account identifier that was previously stored. Sub-process 320 is described below in relation to Fig. 4B. The method 300 then proceeds from sub-process 320 to step 315.
In step 315, after a positive determination that the second social network account is permitted to send the message, the message processing server 110 transmits the message through the first message channel to the first social network server 103N. The method 300 then concludes at the conclusion of step 315.
Fig. 4A is a flow diagram of the sub-process 211 of Fig. 2 to determine that the social network account (either the first social network account or the second social network account) can be used to register to the message channel (either the first message channel or the second message channel) in the system of Fig. 1.
In step 222, the message processing server 110 receives a request to register to a message channel with a social network service. The request may be initiated from a user device 104 which a user may wish to purchase goods or services. The request may also be initiated from a merchant device 102 which the user may use to sell goods or services online. The message channel may be a first message channel managed by the first social network server 103N or a second message channel managed by the second social network server 103A.
In step 224, the message processing server 110 determines whether the device sending the request is associated with the user account of the social network service. For example, a unique identifier (e.g., MAC address, CPU serial number, etc. ) of the user device 104 may be  generated and associated with the user account during the on-boarding process with the social network service. The unique identifier may then be transmitted to the message processing server 110 and stored in a database. The request from the device to use a user account for registering to a message channel may include the unique identifier. The message processing server 110 may subsequently determine whether the device is associated with the user account using the unique identifier that was previously stored. If the message processing server 110 determines that the device is not associated with the user account, the method 211 proceeds from step 224 to step 226.
In step 226, the message processing server 110 transmits a request to subscribe to the service provided by the message processing server 110. After the user confirms and authorizes to subscribe to the service, the message processing server 110 receives an authorization of the request to subscribe to the service in step 228. Thereafter, the method 211 proceeds from step 228 to step 230.
On the other hand if the message processing server 110 determines that the device is associated with the user account, the method proceeds from step 224 to step 230. In step 230, the message processing server 110 transmits a confirmation that the user account indicated in the request is permitted to register to the message channel. The method 211 then concludes at the conclusion of step 230.
Fig. 4B is a flow diagram of a sub-process 320 of Fig. 3 for determining whether the second social network account is permitted to send the message (or a plurality of messages) in the system of Fig. 1.
In step 322, the method includes receiving, through a second message channel, a request to send a message to a first social network account. In step 324, the message processing server 110 determines whether the second social network account used to send the request is associated with the first social network account. As described previously in Fig. 3, the message processing server 110 may determine using the account identifier indicated in the request.
If the message processing server 110 determines that the second social network account that is used to send the request is not associated with the first social network account, the method 320 proceeds from step 324 to step 346.
In step 346, the message processing server 110 transmits a pairing request to associate the first and second social network accounts. This step may be carried out by sending the pairing request to the user via the device. After the user confirms and authorizes to associate the first  social network account with the second social network account, the message processing server 110 receives an authorization of the pairing request at step 348. Thereafter, the method 320 proceeds from step 348 to step 326.
On the other hand, if the message processing server 110 determines the second social network account which is used to send the request is associated with the first social network account, the method 320 proceeds from step 324 to 326. In step 326, the method includes transmitting, through a first message channel, the message for displaying. The message may be displayed to the user via the user device 104N.
The method 320 then proceeds from step 326 to step 328. In step 328, the method includes transmitting a reply to the message through a first message channel. For example, the user who is registered with the first social network server 103N and has viewed the message may wish to reply via the user device 104N. The reply may include transaction credentials to complete a transaction and may be sent to the first social network server 103N via the first message channel.
If the reply at step 328 includes transaction credentials to complete a transaction, the message processing server 110 processes the transaction at step 350. Accordingly, the method 320 ends after the transaction is processed and sub-process 350 is described below in relation to Fig. 5.
Fig. 5 is a flow diagram of a sub-process 350 of Fig. 4B for processing a transaction in the system of Fig. 1. The sub-process 350 may be used to describe the steps of processing a transaction when the message is a transaction request message. For example, the transaction request may be initiated at the merchant device 102 and sent directly to the message processing server 110. Alternatively, the message processing server 110 may receive the transaction request message via the merchant server 116. In other embodiments, the transaction request message may be initiated by  user devices  104A, 104N to purchase items online using their respective devices. In this case, the transaction request message may be sent to the message processing server 110 via the respective  social networks  103A, 103N where each of the  user devices  104A, 104N are registered.
In step 352, the message processing server 110 transmits a reply to the message (or transaction request message) through a first message channel. For example, the reply to the message may be one that the user confirms to purchase the goods or services and provides his payment account details.
The method 350 then proceeds from step 352 to step 354. In step 354, the method includes determining whether the reply includes payment account details. Payment account details may include an account number, an account name, name of issuer, a payment account identifier and or other relevant information that is provided when payment of the goods and services is requested. The determination may be carried out by the message processing server 110 and if it is determined that the reply does not include payment account details, the message processing server 110 transmits the reply to the social network server at step 366. The social network server may store the payment account details in its database and after receiving the reply at step 366, it may transmit the payment account details back to the message processing server 110.
On the other hand, if it is determined that the reply includes payment account details, the method 350 proceeds from step 354 to step 356. In step 356, the method includes forwarding the reply to an issuer. The reply may be forwarded to the issuer via the issuer server 115 and may include a unique payment account identifier associated with the payment account. The method then proceeds to step 358.
In step 358, the method includes forwarding an authorisation to the acquirer when the authorisation from the issuer is received. For example, after the issuer receives the reply in step 356, it may determine whether there are sufficient funds in the payment account. If there are sufficient funds, the issuer authorises the transaction and the message processing server 110 may receive the authorisation.
Subsequently, the message processing server 110 forwards the authorisation to the social network server in step 360. The method 350 then concludes at the conclusion of step 360.
Structural Context
The message processing server 110
Figs. 6A and 6B depict a general-purpose computer system 1300, upon which the transaction processing server 110 described can be practiced.
As seen in Fig. 6A, the computer system 1300 includes a computer module 1301. An external Modulator-Demodulator (Modem) transceiver device 1316 may be used by the computer module 1301 for communicating to and from a communications network 1320 via a connection 1321. The communications network 1320 may be a wide-area network (WAN) , such as the Internet, a cellular telecommunications network, or a private WAN. Where the  connection 1321 is a telephone line, the modem 1316 may be a traditional “dial-up” modem. Alternatively, where the connection 1321 is a high capacity (e.g., cable) connection, the modem 1316 may be a broadband modem. A wireless modem may also be used for wireless connection to the communications network 1320. The communications network 1320 can be used by the transaction processing server 110 to communicate with the devices 102, 103, 104 and the  servers  112, 113, 116 in the system 100.
The computer module 1301 typically includes at least one processor unit 1305, and a memory unit 1306. For example, the memory unit 1306 may have semiconductor random access memory (RAM) and semiconductor read only memory (ROM) . The computer module 1301 also includes an interface 1308 for the external modem 1316. In some implementations, the modem 1316 may be incorporated within the computer module 1301, for example within the interface 1308. The computer module 1301 also has a local network interface 1311, which permits coupling of the computer system 1300 via a connection 1323 to a local-area communications network 1322, known as a Local Area Network (LAN) . As illustrated in Fig. 6A, the local communications network 1322 may also couple to the wide network 1320 via a connection 1324, which would typically include a so-called “firewall” device or device of similar functionality. The local network interface 1311 may comprise an Ethernet circuit card, a Bluetooth wireless arrangement or an IEEE 802.11 wireless arrangement; however, numerous other types of interfaces may be practiced for the interface 1311.
The I/O interfaces 1308 may afford either or both of serial and parallel connectivity, the former typically being implemented according to the Universal Serial Bus (USB) standards and having corresponding USB connectors (not illustrated) . Storage devices 1309 are provided and typically include a hard disk drive (HDD) 1310. Other storage devices such as a floppy disk drive and a magnetic tape drive (not illustrated) may also be used. An optical disk drive 1312 is typically provided to act as a non-volatile source of data. Portable memory devices, such optical disks (e.g., CD-ROM, DVD, Blu-ray Disc TM) , USB-RAM, portable, external hard drives, and floppy disks, for example, may be used as appropriate sources of data to the system 1300.
The components 1305 to 1312 of the computer module 1301 typically communicate via an interconnected bus 1304 and in a manner that results in a conventional mode of operation of the computer system 1300 known to those in the relevant art. For example, the processor 1305 is coupled to the system bus 1304 using a connection 1318. Likewise, the memory 1306 and optical disk drive 1312 are coupled to the system bus 1304 by connections 1319. Examples of computers on which the described arrangements can be practised include IBM-PC’s and compatibles, Sun Sparcstations, Apple Mac TM or like computer systems.
The steps of  sub-processes  211, 320, and 250 in Figs. 4A, 4B, and 5, respectively, performed by the transaction processing server 110 may be implemented using the computer system 1300. The steps of  sub-processes  211, 320, and 250 may be implemented as one or more software application programs 1333 executable within the computer system 1300. In particular, the steps of the sub-processes 211, 320, and 250 as performed by the transaction processing server 110 are effected by instructions 1331 (see Fig. 6B) in the software 1333 that are carried out within the computer system 1300. The software instructions 1331 may be formed as one or more code modules, each for performing one or more particular tasks. The software may also be divided into two separate parts, in which a first part and the corresponding code modules performs the steps of the transaction processing server 110 and a second part and the corresponding code modules manage the API and corresponding user interfaces in the merchant device 102, the user devices 104, the transaction device 103. In other words, the second part of the software manages the interaction between (a) the first part and (b) any one of the merchant device 102, the user devices 104, and the transaction device 103.
The software may be stored in a computer readable medium, including the storage devices described below, for example. The software is loaded into the computer system 1300 from the computer readable medium, and then executed by the computer system 1300. A computer readable medium having such software or computer program recorded on the computer readable medium is a computer program product. The use of the computer program product in the computer system 1300 preferably effects an advantageous apparatus for a transaction processing server 110.
The software 1333 is typically stored in the HDD 1310 or the memory 1306. The software is loaded into the computer system 1300 from a computer readable medium, and executed by the computer system 1300. Thus, for example, the software 1333 may be stored on an optically readable disk storage medium (e.g., CD-ROM) 1325 that is read by the optical disk drive 1312. A computer readable medium having such software or computer program recorded on it is a computer program product. The use of the computer program product in the computer system 1300 preferably effects an apparatus for a transaction processing server 110.
In some instances, the application programs 1333 may be supplied to the user encoded on one or more CD-ROMs 1325 and read via the corresponding drive 1312, or alternatively may be read by the user from the  networks  1320 or 1322. Still further, the software can also be loaded into the computer system 1300 from other computer readable media. Computer readable storage media refers to any non-transitory tangible storage medium that provides recorded instructions and/or data to the computer system 1300 for execution and/or processing. Examples of such  storage media include floppy disks, magnetic tape, CD-ROM, DVD, Blu-ray TM Disc, a hard disk drive, a ROM or integrated circuit, USB memory, a magneto-optical disk, or a computer readable card such as a PCMCIA card and the like, whether or not such devices are internal or external of the computer module 1301. Examples of transitory or non-tangible computer readable transmission media that may also participate in the provision of software, application programs, instructions and/or data to the computer module 1301 include radio or infra-red transmission channels as well as a network connection to another computer or networked device, and the Internet or Intranets including e-mail transmissions and information recorded on Websites and the like.
The second part of the application programs 1333 and the corresponding code modules mentioned above may be executed to implement one or more API of the transaction processing server 110 with associated graphical user interfaces (GUIs) to be rendered or otherwise represented upon the display of the merchant device 102, the user devices 104, and the transaction device 103. Through manipulation of typically a keyboard and a mouse, a user of the merchant device 102, the user devices 104, and the transaction device 103 and the application may manipulate the interface presented on the display of the merchant device 102, the user devices 104, and the transaction device 103 in a functionally adaptable manner to provide controlling commands and/or input to the applications associated with the GUI (s) . Other forms of functionally adaptable user interfaces may also be implemented, such as an audio interface utilizing speech prompts output via loudspeakers and user voice commands input via a microphone.
Fig. 6B is a detailed schematic block diagram of the processor 1305 and a “memory” 1334. The memory 1334 represents a logical aggregation of all the memory modules (including the HDD 1309 and semiconductor memory 1306) that can be accessed by the computer module 1301 in Fig. 6A.
When the computer module 1301 is initially powered up, a power-on self-test (POST) program 1350 executes. The POST program 1350 is typically stored in a ROM 1349 of the semiconductor memory 1306 of Fig. 6A. A hardware device such as the ROM 1349 storing software is sometimes referred to as firmware. The POST program 1350 examines hardware within the computer module 1301 to ensure proper functioning and typically checks the processor 1305, the memory 1334 (1309, 1306) , and a basic input-output systems software (BIOS) module 1351, also typically stored in the ROM 1349, for correct operation. Once the POST program 1350 has run successfully, the BIOS 1351 activates the hard disk drive 1310 of Fig. 6A. Activation of the hard disk drive 1310 causes a bootstrap loader program 1352 that is resident on  the hard disk drive 1310 to execute via the processor 1305. This loads an operating system 1353 into the RAM memory 1306, upon which the operating system 1353 commences operation. The operating system 1353 is a system level application, executable by the processor 1305, to fulfil various high level functions, including processor management, memory management, device management, storage management, software application interface, and generic user interface.
The operating system 1353 manages the memory 1334 (1309, 1306) to ensure that each process or application running on the computer module 1301 has sufficient memory in which to execute without colliding with memory allocated to another process. Furthermore, the different types of memory available in the system 1300 of Fig. 6A must be used properly so that each process can run effectively. Accordingly, the aggregated memory 1334 is not intended to illustrate how particular segments of memory are allocated (unless otherwise stated) , but rather to provide a general view of the memory accessible by the computer system 1300 and how such is used.
As shown in Fig. 6B, the processor 1305 includes a number of functional modules including a control unit 1339, an arithmetic logic unit (ALU) 1340, and a local or internal memory 1348, sometimes called a cache memory. The cache memory 1348 typically includes a number of storage registers 1344 -1346 in a register section. One or more internal busses 1341 functionally interconnect these functional modules. The processor 1305 typically also has one or more interfaces 1342 for communicating with external devices via the system bus 1304, using a connection 1318. The memory 1334 is coupled to the bus 1304 using a connection 1319.
The application program 1333 includes a sequence of instructions 1331 that may include conditional branch and loop instructions. The program 1333 may also include data 1332 which is used in execution of the program 1333. The instructions 1331 and the data 1332 are stored in  memory locations  1328, 1329, 1330 and 1335, 1336, 1337, respectively. Depending upon the relative size of the instructions 1331 and the memory locations 1328-1330, a particular instruction may be stored in a single memory location as depicted by the instruction shown in the memory location 1330. Alternately, an instruction may be segmented into a number of parts each of which is stored in a separate memory location, as depicted by the instruction segments shown in the  memory locations  1328 and 1329.
In general, the processor 1305 is given a set of instructions which are executed therein. The processor 1305 waits for a subsequent input, to which the processor 1305 reacts to by executing another set of instructions. Each input may be provided from one or more of a number of sources, including data generated by one or more of the input devices 1302, 1303, data received from an external source across one of the networks 1320, 1302, data retrieved from one  of the  storage devices  1306, 1309 or data retrieved from a storage medium 1325 (e.g., the database 109) inserted into the corresponding reader 1312, all depicted in Fig. 6A. The execution of a set of the instructions may in some cases result in output of data. Execution may also involve storing data or variables to the memory 1334.
The disclosed transaction processing server 110 arrangements use input variables 1354, which are stored in the memory 1334 in corresponding  memory locations  1355, 1356, 1357. The payment network server 108 arrangements produce output variables 1361, which are stored in the memory 1334 in corresponding  memory locations  1362, 1363, 1364. Intermediate variables 1358 may be stored in  memory locations  1359, 1360, 1366 and 1367.
Referring to the processor 1305 of Fig. 6B, the  registers  1344, 1345, 1346, the arithmetic logic unit (ALU) 1340, and the control unit 1339 work together to perform sequences of micro-operations needed to perform “fetch, decode, and execute” cycles for every instruction in the instruction set making up the program 1333. Each fetch, decode, and execute cycle comprises:
a fetch operation, which fetches or reads an instruction 1331 from a  memory location  1328, 1329, 1330;
a decode operation in which the control unit 1339 determines which instruction has been fetched; and
an execute operation in which the control unit 1339 and/or the ALU 1340 execute the instruction.
Thereafter, a further fetch, decode, and execute cycle for the next instruction may be executed. Similarly, a store cycle may be performed by which the control unit 1339 stores or writes a value to a memory location 1332.
Each step of  sub-processes  211, 320, and 250, as performed by the transaction processing server 110, is associated with one or more segments of the program 1333 and is performed by the  register section  1344, 1345, 1347, the ALU 1340, and the control unit 1339 in the processor 1305 working together to perform the fetch, decode, and execute cycles for every instruction in the instruction set for the noted segments of the program 1333.
It is to be understood that the structural context of the computer system 1300 (i.e., the transaction processing server 110) is presented merely by way of example. Therefore, in some arrangements, one or more features of the server 1300 may be omitted. Also, in some arrangements, one or more features of the server 1300 may be combined together. Additionally,  in some arrangements, one or more features of the server 1300 may be split into one or more component parts.
Fig. 7 shows an alternative implementation of the message processing server 110 (i.e., the computer system 1300) . In the alternative implementation, the message processing server 110 may be generally described as a physical device comprising at least one processor 702 and at least one memory 704 including computer program codes. The at least one memory 704 and the computer program codes are configured to, with the at least one processor 702, cause the message processing server 110 to perform the operations described in sub-processes 211, 320, and 350. The message processing server 110 may also include a message processing module 706 and a user account module 708. The memory 704 stores computer program code that the processor 702 compiles to have each of the  modules  706 and 708 performs their respective functions.
With reference to Fig. 1, the message module 706 performs the function of communicating with the devices 102, 103, 104 to receive requests and to transmit data. With reference to Fig. 1, the user account module 708 performs the function of registering user accounts and performing  sub-processes  211, 320, and 250.
Industrial Applicability
The arrangements described are applicable to the computer and data processing industries and particularly for the conducting a transaction across a plurality of devices.
The foregoing describes only some embodiments of the present invention, and modifications and/or changes can be made thereto without departing from the scope and spirit of the invention, the embodiments being illustrative and not restrictive.
Use Case Examples
Some examples of use case of the system 100 will now be described. These examples are illustrative and not restrictive.
First Use Case of the System 100
In the first use case, the user X has a social network account on social network service A and has a friend Y who has a social network account with social network service B. Both user X and Y have their own personal mobile device and have registered their respective social network  accounts with the message processing server 110. X wishes to send a message to Y asking Y to meet him in town for a cup of coffee. X opens an application of social network service A installed in his mobile phone and sends his message. The message processing server 110 receives the message via a server of social network service A and routes the message to a server of social network service B. The server of social network service B forwards the message to an application installed in Y’s mobile phone which displays and notifies Y of X’s message.
Y agrees to meet X and subsequently replies to X’s message by using the application installed in his mobile phone. Y’s reply is sent to social network service B’s server which is then routed to the message processing server 110. Y’s reply is then forwarded to the application installed in X’s mobile phone which displays and notifies X of Y’s reply.
Second Use Case of the System 100
In the second use case, the user X has a social network account on social network service A. X wishes to purchase a laptop worth $1000 from merchant Y. X visits merchant Y’s shop and uses the Point-Of-Sale (POS) terminal at Y’s shop to send a transaction request message to purchase the laptop. The transaction request message is routed to the message processing server 110 and a reply is sent to the POS terminal requesting for X’s payment account details. In an alternate embodiment, X may wish to purchase the laptop online and visits Y’s online shop. X selects the laptop and sends a transaction request message to purchase the laptop. Y’s server receives the transaction request message which is then routed to the message processing server 110. A reply is sent requesting for X’s payment account details.
X replies (either through the POS terminal or Y’s online portal) by confirming to purchase the laptop and providing his payment account details. The message processing server 110 then determines that the reply includes payment account details and forwards the transaction request message and x’s payment account details to the acquirer server 113, the payment network server 114 and the issuer server 115. The issuer determines that there is sufficient funds in X’s account to purchase the $1000 laptop and authorizes the transaction. The issuer server 115 sends an authorization message to the acquirer server 113 and the message processing server 110. The message processing server 110 may send the authorization to the social network service A which may include the transaction in a summary list of the items X had purchased in the last month.

Claims (18)

  1. A system for processing a message between a first social network account on a first social network service and a second social network account on a second social network service that is different from the first social network service, the first social network service having a first message channel and the second social network service having a second message channel, the system comprising:
    a server having at least one processor; and
    at least one memory including computer program code;
    the at least one memory and the computer program code configured to, with the at least one processor, cause the server at least to:
    receive, through the second message channel, a request to send the message to the first social network account, the request including the message to be sent, a first account identifier associated with the first social network account and second account information associated with the second social network account;
    determine whether the second social network account is permitted to send the message to the first social network account based on the first account identifier; and
    transmit, through the first message channel, the message for displaying based on the determination of whether the second social network account is permitted to send the message to the first social network account.
  2. The system of claim 1, wherein the server is configured to:
    determine if the first social network service associated with the first social network account is permitted to establish the first message channel; and
    establish the first message channel with the first social network service based on the determination of whether the first social network account is permitted to establish the first message channel.
  3. The system of claim 1, wherein the server is configured to:
    determine if the second social network service associated with the second social network account is permitted to establish the second message channel; and
    establish the second message channel with the second social network service based on the determination of whether the second social network account is permitted to establish the second message channel.
  4. The system of claim 2, wherein the server is configured to:
    receive a request to register to the first message channel with the first social network service, the request including first account information associated with the first social network account;
    determine whether the first social network account is permitted to register with the first message channel; and
    register the first social network account to the first message channel based on the determination of whether the first social network account is permitted to register with the first message channel.
  5. The system of claim 3, wherein the server is configured to:
    receive a request to register to the second message channel with the second social network service, the request including the second account information associated with the second social network account;
    determine whether the second social network account is permitted to register with the second message channel; and
    register the second social network account to the second message channel based on the determination of whether the second social network account is permitted to register with the second message channel.
  6. The system of claim 4, wherein the server is configured to:
    generate the first account identifier in response to the registration of the first social network account to the first message channel.
  7. The system of claim 5, wherein the server is configured to:
    generate the second account identifier in response to the registration of the second social network account to the second message channel.
  8. The system of claim 6, wherein the server is configured to:
    receive, through the first message channel, a request to send the first account identifier to a user using the second social network account;
    determine the second social network account is permitted to receive the first account identifier; and
    transmit, through the second message channel, the first account identifier.
  9. The system of claim 8, wherein the server is configured to:
    associate the first social network account to the second social network account in response to the transmission of the first account identifier.
  10. A method for processing a message between a first social network account on a first social network service and a second social network account on a second social network service that is different from the first social network service, the first social network service having a first message channel and the second social network service having a second message channel, the method comprising:
    receiving, through the second message channel, a request to send the message to the first social network account, the request including a first account identifier associated  with the first social network account and second account information associated with the second social network account;
    determining whether the second social network account is permitted to send the message to the first social network account based on the first account identifier; and
    transmitting, through the first message channel, the message for displaying based on the determination of whether the second social network account is permitted to send the message to the first social network account.
  11. The method of claim 10, further comprising:
    determining if the first social network service associated with the first social network account is permitted to establish the first message channel; and
    establishing the first message channel with the first social network service based on the determination of whether the first social network account is permitted to establish the first message channel.
  12. The method of claim 10, further comprising:
    determining if the second social network service associated with the second social network account is permitted to establish the second message channel; and
    establishing the second message channel with the second social network service based on the determination of whether the first social network account is permitted to establish the first message channel.
  13. The method of claim 11, further comprising:
    receiving a request to register to the first message channel with the first social network service, the request including first account information associated with the first social network account;
    determining whether the first social network account is permitted to register with the first message channel; and
    registering the first social network account to the first message channel based on the determination of whether the first social network account is permitted to register with the first message channel.
  14. The method of claim 12, further comprising:
    receiving a request to register to the first message channel with the first social network service, the request including first account information associated with the first social network account;
    determining whether the first social network account is permitted to register with the first message channel; and
    registering the first social network account to the first message channel based on the determination of whether the first social network account is permitted to register with the first message channel.
  15. The method of claim 13, further comprising:
    generating the first account identifier in response to the registration of the first social network account to the first message channel.
  16. The method of claim 14, further comprising:
    generating the second account identifier in response to the registration of the second social network account to the second message channel.
  17. The method of claim 15, further comprising:
    receiving, through the first message channel, a request to send the first account identifier to a user using the second social network account;
    determining the second social network account is permitted to receive the first account identifier; and
    transmitting, through the second message channel, the first account identifier.
  18. The method of claim 17, further comprising:
    associating the first social network account to the second social network account in response to the transmission of the first account identifier
PCT/CN2019/128611 2019-12-26 2019-12-26 A method and system for processing a plurality of messages between different social network services WO2021128152A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/128611 WO2021128152A1 (en) 2019-12-26 2019-12-26 A method and system for processing a plurality of messages between different social network services

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/128611 WO2021128152A1 (en) 2019-12-26 2019-12-26 A method and system for processing a plurality of messages between different social network services

Publications (1)

Publication Number Publication Date
WO2021128152A1 true WO2021128152A1 (en) 2021-07-01

Family

ID=76572898

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/128611 WO2021128152A1 (en) 2019-12-26 2019-12-26 A method and system for processing a plurality of messages between different social network services

Country Status (1)

Country Link
WO (1) WO2021128152A1 (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102882759A (en) * 2011-07-14 2013-01-16 中兴通讯股份有限公司 Communication method of cross-social network, network element and system
CN103095549A (en) * 2011-10-31 2013-05-08 腾讯科技（北京）有限公司 Method and system for messaging between instant messaging tools
US20170064034A1 (en) * 2015-08-31 2017-03-02 Ebay Inc. Passive social media contact engagement
CN106789547A (en) * 2015-11-20 2017-05-31 北京奇虎科技有限公司 One kind receives message approach and terminal device
CN107888474A (en) * 2016-09-30 2018-04-06 江苏神州信源系统工程有限公司 A kind of method of controlling security and device for the interconnection of different instantaneous communication systems
CN109889423A (en) * 2017-12-06 2019-06-14 腾讯科技（深圳）有限公司 A kind of message treatment method, device and storage medium

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102882759A (en) * 2011-07-14 2013-01-16 中兴通讯股份有限公司 Communication method of cross-social network, network element and system
CN103095549A (en) * 2011-10-31 2013-05-08 腾讯科技（北京）有限公司 Method and system for messaging between instant messaging tools
US20170064034A1 (en) * 2015-08-31 2017-03-02 Ebay Inc. Passive social media contact engagement
CN106789547A (en) * 2015-11-20 2017-05-31 北京奇虎科技有限公司 One kind receives message approach and terminal device
CN107888474A (en) * 2016-09-30 2018-04-06 江苏神州信源系统工程有限公司 A kind of method of controlling security and device for the interconnection of different instantaneous communication systems
CN109889423A (en) * 2017-12-06 2019-06-14 腾讯科技（深圳）有限公司 A kind of message treatment method, device and storage medium

Similar Documents

Publication Publication Date Title
US10915906B2 (en) System and method for facilitating secure self payment transactions of retail goods
CN108141368B (en) Instant token issuing system
US10789585B2 (en) Systems and methods for facilitating remote authorization and payment of goods via mobile commerce
AU2012242763B2 (en) Message routing using logically independent recipient identifiers
US11297001B2 (en) Closed loop resource distribution platform
US20150310402A1 (en) Transaction conversion with payment card
US11410223B2 (en) Method and system for facilitating e-commerce transactions
US11461770B2 (en) Active application of secondary transaction instrument tokens for transaction processing systems
US10805234B2 (en) Closed loop resource distribution platform zone generation and deployment
US20200167757A1 (en) Method and system for processing a transaction using plurality of devices
US11257071B2 (en) Closed loop platform for dynamic currency conversion
US20190188660A1 (en) Payment apparatus and method for enabling a payment device for remotely accessing a transaction
WO2023033722A2 (en) System and method for adaptively tracking a pattern of a transaction
US11334880B2 (en) Methods and systems for online purchase of items in increased online traffic
WO2021128152A1 (en) A method and system for processing a plurality of messages between different social network services
US20200250684A1 (en) System and method for processing a proof of provenance transaction
US20170337547A1 (en) System and method for wallet transaction scoring using wallet content and connection origination
US20200134596A1 (en) System and method for processing a transaction
US20210201275A1 (en) System and method for smart device communication and transaction processing
WO2014019026A1 (en) Electronic transction system and method

Legal Events

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

Ref document number: 19957259

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19957259

Country of ref document: EP

Kind code of ref document: A1