WO2017124944A1 - 业务处理方法和装置 - Google Patents

业务处理方法和装置 Download PDF

Info

Publication number
WO2017124944A1
WO2017124944A1 PCT/CN2017/070800 CN2017070800W WO2017124944A1 WO 2017124944 A1 WO2017124944 A1 WO 2017124944A1 CN 2017070800 W CN2017070800 W CN 2017070800W WO 2017124944 A1 WO2017124944 A1 WO 2017124944A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
service object
recommendation information
request
response
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2017/070800
Other languages
English (en)
French (fr)
Chinese (zh)
Inventor
傅小贞
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba Group Holding Ltd
Original Assignee
Alibaba Group Holding 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 Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Priority to JP2018537778A priority Critical patent/JP6941614B2/ja
Priority to MYPI2018702506A priority patent/MY198475A/en
Priority to EP17740975.2A priority patent/EP3407568A4/en
Priority to SG11201806137PA priority patent/SG11201806137PA/en
Priority to KR1020187023577A priority patent/KR102150780B1/ko
Publication of WO2017124944A1 publication Critical patent/WO2017124944A1/zh
Priority to PH12018501530A priority patent/PH12018501530A1/en
Priority to US16/039,006 priority patent/US11057492B2/en
Anticipated expiration legal-status Critical
Priority to US17/366,801 priority patent/US11381660B2/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/62—Establishing a time schedule for servicing the requests
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/01—Social networking
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/40—Information retrieval; Database structures therefor; File system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
    • G06F16/43—Querying
    • G06F16/435—Filtering based on additional data, e.g. user or group profiles
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/953—Querying, e.g. by the use of web search engines
    • G06F16/9535—Search customisation based on user profiles and personalisation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/53—Network services using third party service providers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a service processing method and apparatus.
  • the present application provides a service processing method and apparatus.
  • a business processing method comprising:
  • a target service object that matches the service object recommendation information is sent to the service requester.
  • the method further includes:
  • the mapping relationship between the identification information of the service requesting end and the originating location is saved;
  • the sending the target service object that matches the service object recommendation information to the service requesting end includes:
  • the service object recommendation information carries a service object
  • the carried the service object is sent to the service request end as a target service object
  • the service object bound by the service response end is determined according to the identification information of the service response end, and the bound service object is sent as the target service object to the Said business request side.
  • the service object recommendation information is sent by the service response end after receiving the preset gesture instruction.
  • the business object acquisition request is a self-selected stock acquisition request
  • the business object recommendation information is a self-selected stock recommendation information
  • the target business object is a self-selected stock.
  • a service processing device comprising:
  • the request receiving unit receives a service object acquisition request sent by the service requesting end, where the service object obtaining request carries the originating location of the service requesting end;
  • a service recommendation unit where a distance between the originating location and the response location is within a preset distance, and a request time of the business object acquisition request and a sending time of the business object recommendation information are at a preset time difference
  • the target service object that matches the service object recommendation information is sent to the service requesting end.
  • the device further includes:
  • a location saving unit after receiving the service object obtaining request sent by the service requesting end, saving a mapping relationship between the identifier information of the service requesting end and the originating location;
  • the service recommendation unit sends a target service object that matches the service object recommendation information to the service request end according to the identification information of the service request end.
  • the service recommendation unit when the service object recommendation information carries the service object, sends the carried the service object as the target service object to the service request end; and the service object recommendation information
  • the service object bound to the service response end is determined according to the identification information of the service response end, and the bound service object is sent as the target service object to the service request end.
  • the service object recommendation information is sent by the service response end after receiving the preset gesture instruction.
  • the business object acquisition request is a self-selected stock acquisition request
  • the business object recommendation information is a self-selected stock recommendation information
  • the target business object is a self-selected stock.
  • the service server of the present application may send the target service object that matches the service object recommendation information to the time constraint condition and the time constraint condition.
  • Business request side In the recommendation process of the entire business object, there is no need to perform a friend addition operation, and the operation is convenient for the user, and the information interaction efficiency is high.
  • FIG. 1 is a schematic diagram of an application scenario of a service process according to an exemplary embodiment of the present application.
  • FIG. 2 is a flowchart of a service processing method according to an exemplary embodiment of the present application.
  • FIG. 3 is a flowchart of another service processing method according to an exemplary embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a service processing apparatus according to an exemplary embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a service processing apparatus according to an exemplary embodiment of the present application.
  • first, second, third, etc. may be used to describe various information in this application, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as the second information without departing from the scope of the present application.
  • second information may also be referred to as the first information.
  • word "if” as used herein may be interpreted as "when” or “when” or “in response to a determination.”
  • the other party when an unfamiliar user interacts with the information, the other party can be added as a friend, and then the business information is shared to the other party.
  • the user needs to pass the steps of requesting, authenticating, agreeing, etc. Add each other as a friend and share business information.
  • the relationship between unfamiliar users is weak, and the parties who interact with the information may not want the other party to be their own friend. Therefore, the feasibility of information interaction by adding as a friend is not high.
  • the user can also verbally inform the other party about the relevant business information, and the other party can obtain the business information by searching, etc.
  • such an implementation manner is inefficient and has poor accuracy.
  • the present application provides a service processing solution, which can implement a highly efficient information interaction process more conveniently.
  • FIG. 1 is a schematic diagram of an application scenario of a service process according to an exemplary embodiment of the present application.
  • the service server is usually set by a service provider, and the service provider can provide various service services to the user through the service server to implement related business operations.
  • the user can register the corresponding user account on the service server in advance, and the specific note For the process of the book, reference may be made to the implementation method provided in the related art, and the present application will not be repeated here.
  • the terminals in the embodiments of the present application may all be smart devices with network connection functions, such as a mobile phone, a tablet computer, a PDA (Personal Digital Assistant), and the like.
  • the user can interact with the service server through an APP (Application) loaded in the terminal to implement various business operations.
  • APP Application
  • the process of interacting between the APP loaded in the terminal and the service server is simply described as an interaction process between the terminal and the service server.
  • a first user performs a related service operation by using a first terminal
  • a first user may register a first account in the service server in advance, and based on the The first account performs related business operations.
  • the second user performs the related service operation by using the second terminal.
  • the second user may also register the second account in the service server in advance, and perform related service operations based on the second account.
  • the first user and the second user may not perform registration of the user account, and the service server may provide a service service based on the service information provided by the first user and the second user. This application does not specifically limit this.
  • FIG. 2 is a flowchart of a service processing method according to an exemplary embodiment of the present application.
  • the service processing method may be applied to the foregoing service server shown in FIG. 1, and includes the following steps:
  • Step 201 Receive a service object acquisition request sent by a service requesting end, where the service object obtaining request carries an originating location of the service requesting end.
  • the service is usually a recommended service of a business object, such as: a self-selected stock recommendation, a microblog follower recommendation, a friend recommendation, and the like.
  • the acquiring end of the business object is referred to as a service requesting end
  • the user requesting to obtain the business object may send a business object obtaining request to the service server through the service requesting end, for example, requesting to acquire the business object.
  • the user can trigger the business object acquisition function by clicking a preset button, inputting a preset gesture, and the like, and the service requesting end can obtain the current originating location, and the initiating location is carried in the business object obtaining request and sent to the service server. .
  • the service server may save a mapping relationship between the identifier information of the service requesting end and the originating location, where the identifier information may include: a mobile phone number , account ID, etc.
  • the first terminal may obtain the current originating location after receiving the request instruction of the first user, and carry the initiating location in the first terminal.
  • the business object gets the request sent to the business server.
  • Step 202 Receive service object recommendation information sent by the service response end, where the service object recommendation information carries a response location of the service response end.
  • the referral end of the service object may be referred to as a service response end
  • the user of the recommendation service object may send the service object recommendation information to the service server through the service response end, for example, recommending the service object.
  • the user can trigger the business object recommendation function by clicking a preset button, inputting a preset gesture, etc., and the service response end can obtain the current response location and respond to the service.
  • the business object of interest is sent as a recommended business object to the service server along with the response location.
  • the business object may include: a self-selected stock, a microblog follower, a friend, and the like.
  • the service responder may carry all the service objects that are of interest to the service object recommendation information, and the service response end may also carry the service object selected by the user in the service object.
  • the service object recommendation information is sent to the service server, and the application does not specifically limit this.
  • the application scenario shown in FIG. 1 is taken as an example.
  • the second terminal is a service responder
  • the first user can verbally query the second user for information about the business object, and the second user can input the target for the business object through the second terminal.
  • the second terminal may further acquire the current response location, and carry the response location and the service object of interest to the second user in the service object recommendation information and send the message to the service server.
  • Step 203 when the distance between the originating location and the responding location is within a preset distance, and the request time of the business object acquisition request and the sending time of the business object recommendation information are within a preset time difference. And sending, to the service requesting end, a target service object that matches the service object recommendation information.
  • the service server may determine a service request end that satisfies both the distance constraint condition and the time constraint condition, and then matches the service object recommendation.
  • the target business object of the information is sent to the service requester.
  • the distance constraint may be that the distance between the originating location and the responding location is within a preset distance
  • the time constraint may be the request time of the service object acquisition request and the business object recommendation information.
  • the sending time is within the preset time difference.
  • the preset distance and the preset time difference may be set by a developer, for example, 20 meters, 1 minute, etc., and the application does not specifically limit this.
  • the service server may first determine a service request end that satisfies the distance constraint condition, and then meet the service request of the distance constraint condition.
  • the service request end that satisfies the time constraint condition is determined in the terminal.
  • the service server may first determine the service request end that meets the time constraint condition, and then in the service request end that meets the time constraint condition. The service request end that satisfies the distance constraint condition is determined, and this application does not specifically limit this.
  • the service server may first determine a service object that matches the service object recommendation information, and may be matched for convenience of description.
  • the business object of the business object recommendation information is referred to as a target business object.
  • the service server may send the target service object to the service request end that satisfies the distance constraint condition and the time constraint condition. For example, the target service object is sent to the service requesting end according to the account ID of the service requesting end.
  • the service server may determine the target service object that matches the recommendation information of the service object in the following two manners:
  • the service object recommendation information carries the target service object.
  • the service server may first determine whether the service object recommendation information carries a service object, for example, whether the service object carries the identification information, and if the service object is carried, Then, the service object carried in the service object recommendation information may be determined as a target service object that matches the service object recommendation information, and sent to the service requesting end.
  • the target object is not carried in the service object recommendation information.
  • the service server may obtain the identification information of the service response end, and then obtain the service response according to the identifier information.
  • the business object bound to the end, and the bound business object is sent to the service requesting end as the target business object.
  • the service server may obtain the service object bound by the identifier information from the database or platform of the storage service object according to the identifier information of the service response end, which is not specifically limited in this application.
  • the service server of the present application may send the target service object that matches the service object recommendation information to the time constraint condition and the time constraint condition.
  • Business request side In the recommendation process of the entire business object, there is no need to perform a friend addition operation, and the operation is convenient for the user, and the information interaction efficiency is high.
  • the service server may delete the saved mapping relationship between the identifier information of the service requesting end and the originating location, and the application does not stop here. One by one.
  • the business involved in the present application is a recommended business of the self-selected stock
  • the target business object is a self-selected stock
  • the business object acquisition request is a self-selected stock acquisition request
  • the business object recommendation information is a self-selected stock recommendation information.
  • the first terminal is a service requesting end
  • the second terminal is a service responding end.
  • the service processing method provided by the present application may include the following steps:
  • Step 301 The first terminal sends a self-selected stock acquisition request to the service server.
  • the first user can trigger the self-selected stock acquisition function, such as The first user can click the preset button in the stock software, and the first terminal can further obtain the current originating location, and then carry the originating location in the self-selecting stock acquisition request and send it to the service server.
  • the self-selected stock acquisition function such as The first user can click the preset button in the stock software, and the first terminal can further obtain the current originating location, and then carry the originating location in the self-selecting stock acquisition request and send it to the service server.
  • Step 302 The self-selected stock recommendation information sent by the second terminal is sent to the service server.
  • the first user can inform the second user that he wants to know the self-selected stock that the other party pays attention to, and if the second user is willing to tell the first user, the second user can trigger the self-selected stock recommendation function by flipping the mobile phone.
  • the second terminal may further obtain the current response location, and then carry the selected stock and the response location of the second user's attention in the selected stock recommendation information to the service server.
  • Step 303 The service server sends the selected shares carried in the selected stock recommendation information to the first terminal.
  • the service server may determine that the distance from the second terminal is within 10 meters, and the received request time of the selected stock acquisition request is The service requesting end of the selected share recommendation information is the first terminal, and then the selected share of the second user that is carried in the selected share recommendation information is sent to the first terminal.
  • the first terminal may display the selected stock to the first user, and the first user may further pay attention to the second user's selected stock.
  • the service server may implement the above-mentioned self-selected stock recommendation process by using the method provided in the foregoing method embodiment shown in FIG. 2, which is not repeatedly described herein.
  • the present application also provides an embodiment of the service processing apparatus.
  • Embodiments of the service processing apparatus of the present application can be applied to a service server.
  • the device embodiment may be implemented by software, or may be implemented by hardware or a combination of hardware and software. Taking the software implementation as an example, as a logical means, the processor of the service server in which it is located reads the corresponding computer program instructions in the non-volatile memory into the memory. From the hardware level, as shown in FIG. 4, a hardware structure diagram of the service server where the service processing device of the present application is located, except for the processor, the memory, the network interface, and the non-volatile memory shown in FIG.
  • the service server where the device is located in the embodiment may also include other hardware according to the actual function of the service server, and details are not described herein.
  • FIG. 5 is a schematic structural diagram of a service processing apparatus according to an exemplary embodiment of the present application.
  • the service processing apparatus 400 can be applied to the service service shown in FIG. 4.
  • the server includes a request receiving unit 401, a response receiving unit 402, a service recommending unit 403, and a location holding unit 404.
  • the request receiving unit 401 receives a service object acquisition request sent by a service requesting end, where the service object obtaining request carries an originating location of the service requesting end;
  • the response receiving unit 402 receives the service object recommendation information sent by the service response end, where the service object recommendation information carries the response location of the service response end;
  • the service recommendation unit 403 is within a preset distance between the originating location and the response location, and the request time of the service object acquisition request and the sending time of the service object recommendation information are in advance. When the time difference is set, the target service object that matches the service object recommendation information is sent to the service requesting end.
  • the location holding unit 404 after receiving the service object acquisition request sent by the service requesting end, saves the mapping relationship between the identification information of the service requesting end and the originating location;
  • the service recommending unit 403 sends a target service object that matches the service object recommendation information to the service requesting end according to the identification information of the service requesting end.
  • the service recommendation unit 403 when the service object recommendation information carries a service object, sends the carried the service object as a target service object to the service request end;
  • the service object bound to the service response end is determined according to the identification information of the service response end, and the bound service object is sent as the target service object to the service request end.
  • the service object recommendation information is sent by the service response end after receiving the preset gesture instruction.
  • the business object acquisition request is a self-selected stock acquisition request
  • the business object recommendation information is a self-selected stock recommendation information
  • the target business object is a self-selected stock.
  • the device embodiment since it basically corresponds to the method embodiment, reference may be made to the partial description of the method embodiment.
  • the device embodiments described above are merely illustrative Illustratively, the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed in many places. On a network unit. Some or all of the modules may be selected according to actual needs to achieve the objectives of the present application. Those of ordinary skill in the art can understand and implement without any creative effort.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • Data Mining & Analysis (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • General Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • Health & Medical Sciences (AREA)
  • Economics (AREA)
  • General Health & Medical Sciences (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Primary Health Care (AREA)
  • Strategic Management (AREA)
  • Tourism & Hospitality (AREA)
  • Computing Systems (AREA)
  • Information Transfer Between Computers (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Telephonic Communication Services (AREA)
PCT/CN2017/070800 2016-01-19 2017-01-10 业务处理方法和装置 Ceased WO2017124944A1 (zh)

Priority Applications (8)

Application Number Priority Date Filing Date Title
JP2018537778A JP6941614B2 (ja) 2016-01-19 2017-01-10 サービス処理方法及び装置
MYPI2018702506A MY198475A (en) 2016-01-19 2017-01-10 Service Processing Method and Apparatus
EP17740975.2A EP3407568A4 (en) 2016-01-19 2017-01-10 SERVICE PROCESSING AND DEVICE
SG11201806137PA SG11201806137PA (en) 2016-01-19 2017-01-10 Service processing method and apparatus
KR1020187023577A KR102150780B1 (ko) 2016-01-19 2017-01-10 서비스 프로세싱 방법 및 장치
PH12018501530A PH12018501530A1 (en) 2016-01-19 2018-07-18 Service processing method and apparatus
US16/039,006 US11057492B2 (en) 2016-01-19 2018-07-18 Selective information sharing between users of a social network
US17/366,801 US11381660B2 (en) 2016-01-19 2021-07-02 Selective information sharing between users of a social network

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610035517.3 2016-01-19
CN201610035517.3A CN106982197A (zh) 2016-01-19 2016-01-19 业务处理方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/039,006 Continuation US11057492B2 (en) 2016-01-19 2018-07-18 Selective information sharing between users of a social network

Publications (1)

Publication Number Publication Date
WO2017124944A1 true WO2017124944A1 (zh) 2017-07-27

Family

ID=59341393

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/070800 Ceased WO2017124944A1 (zh) 2016-01-19 2017-01-10 业务处理方法和装置

Country Status (10)

Country Link
US (2) US11057492B2 (enExample)
EP (1) EP3407568A4 (enExample)
JP (1) JP6941614B2 (enExample)
KR (1) KR102150780B1 (enExample)
CN (1) CN106982197A (enExample)
MY (1) MY198475A (enExample)
PH (1) PH12018501530A1 (enExample)
SG (1) SG11201806137PA (enExample)
TW (1) TWI668650B (enExample)
WO (1) WO2017124944A1 (enExample)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109857927A (zh) * 2018-12-24 2019-06-07 深圳市珍爱捷云信息技术有限公司 用户推荐方法、装置、计算机设备及计算机可读存储介质

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111177563B (zh) * 2019-12-31 2023-06-27 北京顺丰同城科技有限公司 一种信息推荐方法、装置、电子设备和存储介质
CN112866413A (zh) * 2021-02-19 2021-05-28 北京金山云网络技术有限公司 数据传输方法、装置、电子设备和计算机可读存储介质
CN118828347A (zh) * 2023-11-03 2024-10-22 中国移动通信有限公司研究院 感知目标与通信目标关联的方法、装置、网络设备及介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102546656A (zh) * 2012-02-10 2012-07-04 腾讯科技（深圳）有限公司 在社交网络中查找用户的方法、系统和装置
CN103369009A (zh) * 2012-03-31 2013-10-23 腾讯科技（深圳）有限公司 一种在线问答方法、设备及系统
WO2013159639A1 (zh) * 2012-04-26 2013-10-31 腾讯科技（深圳）有限公司 显示微博话题的方法、终端、服务器、系统及存储介质
CN104009980A (zh) * 2014-05-13 2014-08-27 腾讯科技（深圳）有限公司 基于社交类应用的通信方法及装置
CN104079471A (zh) * 2013-03-28 2014-10-01 腾讯科技（深圳）有限公司 通讯方法、系统、服务器及客户端

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001134519A (ja) * 1999-11-05 2001-05-18 Toshiba Corp クライアント・サーバーシステム及び業務支援システム
JP2002133175A (ja) * 2000-10-30 2002-05-10 Exa Corp サービス仲介方法及びシステム
JP3996384B2 (ja) * 2001-12-04 2007-10-24 株式会社日立国際電気 顧客情報管理システム
US20080262958A1 (en) * 2007-04-20 2008-10-23 At&T Knowledge Ventures, L.P. System and method for reverse auctioning
JP4925116B2 (ja) 2007-05-18 2012-04-25 シャープ株式会社 サービス管理装置、移動端末装置、サービス管理システム、サービス管理方法、およびサービス管理プログラム
US9064284B1 (en) * 2007-09-27 2015-06-23 United Services Automobile Association (Usaa) System and method of providing a financial investment recommendation using a portfolio planner
US9949066B2 (en) * 2010-02-04 2018-04-17 Gemalto Sa Method of and apparatus for access geographical location information service
US20110238476A1 (en) * 2010-03-23 2011-09-29 Michael Carr Location-based Coupons and Mobile Devices
US8438233B2 (en) * 2011-03-23 2013-05-07 Color Labs, Inc. Storage and distribution of content for a user device group
CN104135713B (zh) * 2013-05-15 2015-11-25 腾讯科技（深圳）有限公司 用户信息推荐方法、装置、设备及系统
US9818315B2 (en) * 2013-06-04 2017-11-14 At&T Intellectual Property I, L.P. Secure multi-party device pairing using sensor data
SG10201403898TA (en) * 2013-07-05 2015-02-27 Barrett Carter Keith Computer-implemented intelligence tool
US9338242B1 (en) * 2013-09-09 2016-05-10 Amazon Technologies, Inc. Processes for generating content sharing recommendations
CN104954406B (zh) * 2014-03-31 2018-12-07 中国电信股份有限公司 进行云端数据分享的方法和系统
CN104699764A (zh) * 2015-02-12 2015-06-10 广东欧珀移动通信有限公司 一种信息推送方法及设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102546656A (zh) * 2012-02-10 2012-07-04 腾讯科技（深圳）有限公司 在社交网络中查找用户的方法、系统和装置
CN103369009A (zh) * 2012-03-31 2013-10-23 腾讯科技（深圳）有限公司 一种在线问答方法、设备及系统
WO2013159639A1 (zh) * 2012-04-26 2013-10-31 腾讯科技（深圳）有限公司 显示微博话题的方法、终端、服务器、系统及存储介质
CN104079471A (zh) * 2013-03-28 2014-10-01 腾讯科技（深圳）有限公司 通讯方法、系统、服务器及客户端
CN104009980A (zh) * 2014-05-13 2014-08-27 腾讯科技（深圳）有限公司 基于社交类应用的通信方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3407568A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109857927A (zh) * 2018-12-24 2019-06-07 深圳市珍爱捷云信息技术有限公司 用户推荐方法、装置、计算机设备及计算机可读存储介质

Also Published As

Publication number Publication date
TW201801007A (zh) 2018-01-01
US11381660B2 (en) 2022-07-05
TWI668650B (zh) 2019-08-11
SG11201806137PA (en) 2018-08-30
US11057492B2 (en) 2021-07-06
US20180324275A1 (en) 2018-11-08
US20210337044A1 (en) 2021-10-28
KR102150780B1 (ko) 2020-09-02
EP3407568A1 (en) 2018-11-28
CN106982197A (zh) 2017-07-25
MY198475A (en) 2023-08-31
JP6941614B2 (ja) 2021-09-29
JP2019510289A (ja) 2019-04-11
EP3407568A4 (en) 2019-06-26
KR20180105176A (ko) 2018-09-27
PH12018501530A1 (en) 2019-05-15

Similar Documents

Publication Publication Date Title
CN102713951B (zh) 跨越多个社交网络站点自动同步新联络人
US11622022B2 (en) System and method for a multi-channel notification service
US10582037B2 (en) Two-way permission-based directory of contacts
TWI687877B (zh) 基於位置的服務（ｌｂｓ）的使用者匹配方法、訊息用戶端、伺服器及系統
US9122910B2 (en) Method, apparatus, and system for friend recommendations
CN105743851A (zh) 业务处理方法、装置及业务服务器
US9319368B2 (en) Communication exchanges and methods of use thereof
WO2014166133A1 (en) Method, apparatus, and system for friend recommendations
CN104601712B (zh) 资源推送方法及系统
TWI668650B (zh) Business processing method and device
WO2016155146A1 (zh) 基于电子设备或应用的定位方法和装置
KR101045822B1 (ko) 휴대단말을 이용한 전자명함 처리 방법, 그 시스템 및 그 프로그램을 기록한 컴퓨터 판독 가능한 기록매체
JP2020017000A (ja) サービス活動支援方法、サービス活動支援プログラム、及びシステム
JP6956790B2 (ja) サービスオペレーションを実施するための画像ベースの方法および装置
US12363121B2 (en) Method and apparatus for managing user profile
CN111311383A (zh) 业务处理方法以及装置
JP2018518771A (ja) トランザクション処理方法及びシステム
WO2013135163A1 (zh) 一种获取潜在好友信息的方法、系统和设备
WO2018121164A1 (zh) 一种用于创建服务号的方法、设备及系统
CN108306812A (zh) 一种数据处理方法以及服务器
US20110275387A1 (en) Communication gateway
TW201601079A (zh) 群聚資料分享方法及其系統
US20250156438A1 (en) Federation of disparate datasets hosted across separate servers
CN116546099A (zh) 一种跨设备的数据传输方法及装置
HK1206902B (zh) 对象信息获得方法及系统

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: 17740975

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 11201806137P

Country of ref document: SG

Ref document number: 12018501530

Country of ref document: PH

ENP Entry into the national phase

Ref document number: 2018537778

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20187023577

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 1020187023577

Country of ref document: KR

WWE Wipo information: entry into national phase

Ref document number: 2017740975

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2017740975

Country of ref document: EP

Effective date: 20180820