CN107592324B - Message pushing method and device and portable terminal equipment - Google Patents

Message pushing method and device and portable terminal equipment Download PDF

Info

Publication number
CN107592324B
CN107592324B CN201610530049.7A CN201610530049A CN107592324B CN 107592324 B CN107592324 B CN 107592324B CN 201610530049 A CN201610530049 A CN 201610530049A CN 107592324 B CN107592324 B CN 107592324B
Authority
CN
China
Prior art keywords
message
client
party application
cloud
service platform
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.)
Active
Application number
CN201610530049.7A
Other languages
Chinese (zh)
Other versions
CN107592324A (en
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 China Co Ltd
Original Assignee
Alibaba China Co 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 China Co Ltd filed Critical Alibaba China Co Ltd
Priority to CN201610530049.7A priority Critical patent/CN107592324B/en
Publication of CN107592324A publication Critical patent/CN107592324A/en
Application granted granted Critical
Publication of CN107592324B publication Critical patent/CN107592324B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Information Transfer Between Computers (AREA)

Abstract

The invention discloses a message pushing method and device based on a client browser and portable terminal equipment. The message pushing method based on the client browser comprises the following steps: sending a registration request to a cloud message service platform; in response to receiving a registration token from the cloud messaging service platform, sending the registration token, a client identification, and a third party application user identification to a third party application server; and pushing the message received from the third-party application server through the cloud message service platform to the user according to a preset mode. By using the message pushing method and device based on the client browser, the cloud message service platform is used as the intermediate server to realize real-time message pushing, the trouble that a user needs to actively refresh a webpage to acquire a message is eliminated, and the user experience is improved.

Description

Message pushing method and device and portable terminal equipment
Technical Field
The present invention generally relates to the field of browser technologies, and in particular, to a method and an apparatus for pushing a message based on a client browser, and a portable terminal device.
Background
Social networks have become an important component of modern life. Users share text or picture information through social networks such as Facebook, Twitter, Instagram, Message, and the like.
With the popularity of portable mobile terminal devices, such as smartphones, more and more users are turning to connecting social networks using terminal devices. Due to operating system or application version, type or performance compatibility issues, a significant number of users choose to browse the social network using a browser.
However, when the user of the portable terminal device is using the web page version social network, the web page version does not push a message to the user in real time unlike the application client version. The messages are only displayed in the webpage version, and the updated messages are only displayed when the user actively refreshes the webpage, so that the user easily misses friend messages.
Therefore, a method and an apparatus for pushing a message based on a client browser, which can realize real-time message pushing without requiring a user to actively refresh a page, are needed.
Disclosure of Invention
One object of the present invention is to enable a user browsing a web page provided by a third-party application server using a client browser to receive a message alert in real time without actively refreshing the web page.
Therefore, the message pushing method and device based on the client browser realize real-time message pushing by using the cloud message service, and eliminate the trouble that a user needs to actively refresh a webpage to acquire a message. The cloud message service utilizes a cloud message service platform as an intermediate server to realize message communication among a plurality of servers or clients. Existing Cloud Messaging service platforms include, for example, Google Cloud Messaging (GCM), Tencent Cloud Messaging service platform, or Ali Cloud Messaging service platform, among others.
Specifically, after a client of the portable terminal device is registered on the cloud message service platform and the social network server, the social network server directly sends a message to the client through a corresponding cloud message service channel when the message exists subsequently, and after receiving the message, the client browser displays the message on a display of the portable terminal device in a specified mode, so that a user who browses a webpage by using the client browser can receive the message in real time.
According to an aspect of the present invention, a message pushing method based on a client browser is provided, which includes the following steps: sending a registration request to a cloud message service platform; in response to receiving a registration token from the cloud messaging service platform, sending the registration token, a client identification, and a third party application user identification to a third party application server; and pushing the message received from the third-party application server through the cloud message service platform to the user according to a preset mode.
In one embodiment of the present invention, the client identifier includes: an identification of the client browser for a third party application; and a client physical addressing identity generated from the international mobile equipment identity IMEI and/or the media access MAC address of the client.
In one embodiment of the invention, the third party application user identification is from a third party application Cookie and/or LocalStorage saved on the client. By the aid of the method and the device, the social network background server can quickly and accurately locate the webpage account on the client browser.
In an embodiment of the present invention, the step of pushing the message received from the third party application server via the cloud message service platform to the user according to a predetermined manner includes: in response to receiving the message, the message is presented in a specified style on a notification bar of the client.
In an embodiment of the present invention, the step of pushing the message received from the third party application server via the cloud message service platform to the user according to a predetermined manner further includes: informing the user that the message is received from the third party application server by a specific sound alert and/or a vibration alert.
According to another aspect of the present invention, there is provided a message pushing apparatus based on a client browser, including: the registration request sending unit is configured to send a registration request to the cloud message service platform; an identifier sending unit configured to send, in response to receiving a registration token from the cloud message service platform, the registration token, a client identifier, and a third-party application user identifier to a third-party application server; and the message pushing unit is configured to push the message received from the third-party application server through the cloud message service platform to the user according to a preset mode.
In one embodiment of the present invention, the client identifier includes: an identification of the client browser for a third party application; and a client physical addressing identity generated from the international mobile equipment identity IMEI and/or the media access MAC address of the client. In one embodiment of the invention, the third party application user identification is from a third party application Cookie and/or LocalStorage saved on the client.
In one embodiment of the present invention, the message pushing unit includes: and the message display module is configured to respond to the received message and display the message in a specified style on a notification bar of the client.
In an embodiment of the present invention, the message pushing unit further includes: a message alert module configured to notify a user that the message is received from the third party application server by a specific sound alert and/or a vibration alert.
According to still another aspect of the present invention, there is provided a portable terminal device including: a network interface enabling the portable terminal device to communicate with a cloud messaging service platform and a third party application server via one or more networks; the display is used for displaying the message received by the network interface to a user; and one or more processors coupled to the network interface and the display, the one or more processors configured to: sending a registration request to the cloud message service platform through the network interface; sending, by the network interface, in response to receiving a registration token from the cloud messaging service platform, the registration token, a client identification, and a third-party application user identification to a third-party application server; and pushing the message received from the third-party application server through the cloud message service platform to the user according to a preset mode.
By using the message pushing method and device based on the client browser and the portable terminal equipment, the cloud message service platform is used as the intermediate server to realize real-time message pushing, the trouble that a user needs to actively refresh a webpage to acquire a message is eliminated, and the user experience is improved.
Drawings
The above and other objects, features and advantages of the present disclosure will become more apparent by describing in greater detail exemplary embodiments thereof with reference to the attached drawings, in which like reference numerals generally represent like parts throughout.
Fig. 1 is a block diagram showing the configuration of a portable terminal device according to an embodiment of the present invention.
Fig. 2 is a flowchart illustrating a message push method according to an embodiment of the present invention.
Fig. 3 is a functional block diagram illustrating a message push apparatus according to an embodiment of the present invention.
Detailed Description
Preferred embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While the preferred embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
As described above, in order to enable a user who browses a web page by using a client browser to receive a message prompt in real time without actively refreshing the web page, the invention uses a cloud message service technology and uses a cloud message service platform as a relay server between a third-party application server and a client, so as to forward a message from the server to the client in real time.
An embodiment of the present invention will be specifically described below with reference to fig. 1 to 3. Fig. 1 is a block diagram showing the configuration of a portable terminal device 100 according to an embodiment of the present invention. The components of the portable terminal device 100 include, but are not limited to, a network interface 110, a display 120, and one or more processors 130. The processor 130 is coupled to the network interface 110 and the display 120. In one embodiment of the invention, the other components of the portable terminal device 100 described above and not shown in fig. 1 may also be connected to each other, for example by a bus. It should be understood that the block diagram of the portable terminal device shown in fig. 1 is for exemplary purposes only and is not intended to limit the scope of the present invention. Those skilled in the art may add or replace other components as desired.
The portable terminal device 100 may be any type of mobile computing device, including a mobile computer or mobile computing device (e.g., tablet computer, personal digital assistant, laptop computer, notebook computer, netbook, etc.), a mobile phone (e.g., smartphone), a wearable computing device (e.g., smartwatch, smartglasses, etc.), or other type of mobile device. The portable terminal device 100 may also be a mobile server.
The network interface 110 enables the portable terminal device 100 to communicate with a cloud messaging service platform (not shown) and a third party application server (not shown), such as a Facebook backend server, via one or more networks. The Cloud Messaging service platform may include, for example, a Google Cloud Messaging (GCM), an Tencent Cloud Messaging service platform, or an Alice Cloud Messaging service platform, among others. Examples of such networks include a Local Area Network (LAN), a Wide Area Network (WAN), a Personal Area Network (PAN), or a combination of communication networks such as the internet. The network interface 110 may include one or more of any type of network interface, e.g., a Network Interface Card (NIC), wired or wireless, such as an IEEE 802.11 Wireless Local Area Network (WLAN) wireless interface, a worldwide interoperability for microwave access (Wi-MAX) interface, an ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a bluetooth interface, a Near Field Communication (NFC) interface, and so forth.
Messages received through the network interface 110 are presented to the user through the display 120. The display 120 may be a separate component (peripheral) or may be integrated with the network interface 110 and the processor 130. The display 120 may be configured to display a Graphical User Interface (GUI) including a pointer, cursor, and other information to a user. By way of example, the display 120 may be any type of display including a Liquid Crystal Display (LCD), an electroluminescent display (ELD), a Field Emission Display (FED), a light emitting diode display (LED), an organic light emitting diode display (OLED), and the like.
The processor 130 can be in information communication with the cloud messaging service platform and the third party application server through the network interface 110, so that messages sent from the third party application server via the cloud messaging service platform can be received and pushed to the user in real time.
The process of processor 130 performing real-time pushing of messages can be seen in fig. 2. Fig. 2 shows an overall flowchart of a message pushing method 200 based on a client browser according to an embodiment of the present invention. The method 200 begins at step S210, as shown in fig. 2, where the client sends a registration request to the cloud messaging service platform. After accepting the registration request of the client, the cloud message service platform returns a registration token to the client (step S220). The registration token is the identity of the client on the portable terminal device 100 receiving and sending cloud messages. In one example, the registration request sent from the client can include an identification of the client browser for the cloud messaging service. In the case of the Google cloud messaging service platform, the registration request may also include the Google project ID (project ID).
In step S230, in response to receiving the registration token from the cloud message service platform, the client sends the registration token, the client identifier, and the third-party application user identifier ID to a third-party application server, for example, a background server of a social network browsed by the user, so as to complete the registration process.
The client identification is used for indicating a client receiving the cloud message and a client browser. In one embodiment, the client identification may comprise at least two parts, namely, an identification of the client browser for the third party application and a client physical addressing identification. The identification of the client browser for the third party application is, for example, the Facebook application ID of the client browser to identify the application to which messages from, for example, Facebook should be pushed. And the client physical addressing identification Dn may be generated from any one or more of the international mobile equipment identification IMEI of the client, the media access MAC address, and the related hardware device information of the client, etc., to identify the terminal device to which the message of the third party application should be pushed.
The third party application user identification ID is, for example, an account of the user logging in the social network, such as a Facebook login account. In one embodiment of the invention, the third party application user identification ID may come from a third party application Cookie and/or LocalStorage saved on the client. By using the webpage Cookie and/or LocalStorage, the social network background server can quickly and accurately locate the user account logged in on the client browser.
Through the registration process of step S230, a communication channel via the cloud message server can be established between the client browser and the third-party application server. Therefore, after the registration process is completed, if the message is received at the third-party application server, the message is directly sent to the client through the corresponding cloud message service channel (steps S240 and S250). And after receiving the message, the client pushes the message to the user according to a preset mode.
In one embodiment of the invention, the predetermined message pushing mode comprises the step of displaying the message in a specified style on a notification bar of the client. For example, the user may set whether the push message is displayed on the lock screen, displayed in a scroll banner at the top of the screen, displayed in the form of a reminder at a central location of the screen, and so forth. In one embodiment of the invention, the user may be informed that a message was received from the third party application server by a specific audible alert and/or a vibratory alert.
Fig. 3 is a functional block diagram of a client-side browser-based message pushing apparatus 300 according to an embodiment of the present invention. The functional modules of the message pushing apparatus 300 may be implemented by hardware, software or a combination of hardware and software implementing the principles of the present invention, for example, by one or more processors 130 in the portable terminal device 100 shown in fig. 1. It will be appreciated by those skilled in the art that the functional blocks depicted in fig. 3 may be combined or divided into sub-blocks to implement the principles of the invention described above. Thus, the description herein may support any possible combination, or division, or further definition of the functional modules described herein.
Referring to fig. 3, in order to implement real-time message pushing of a web edition application, a message pushing apparatus 300 is configured to include a registration request transmitting unit 310, an identification transmitting unit 330, and a message pushing unit 350.
The registration request transmitting unit 310 is configured to transmit a registration request to the cloud message service platform. The identity sending unit 330 is configured to send the registration token, the client identity, and the third party application user identity to the third party application server in response to receiving the registration token from the cloud message service platform. In one embodiment, the client identification may comprise at least two parts, namely, an identification of the client browser for the third party application and a client physical addressing identification. The identification of the client browser for the third party application is, for example, the Facebook application ID of the client browser to identify the application to which messages from, for example, Facebook should be pushed. And the client physical addressing identification Dn may be generated from any one or more of the international mobile equipment identification IMEI of the client, the media access MAC address, and the related hardware device information of the client, etc., to identify the terminal device to which the message of the third party application should be pushed.
The third party application user identification is, for example, an account of the user logging in the social network, such as a Facebook login account. In one embodiment of the invention, the third party application user identification may come from a third party application Cookie and/or LocalStorage saved on the client. By using the webpage Cookie and/or LocalStorage, the social network background server can quickly and accurately locate the user account logged in on the client browser.
The message pushing unit 350 is configured to push a message received from the third party application server via the cloud message service platform to the user in a predetermined manner. In one embodiment of the present invention, the message pushing unit 350 may include a message presentation module 352 and a message reminding module 354. Message presentation module 352 is configured to present the message in a specified style in a notification bar of the client in response to receiving the message. The message alert module 354 is configured to notify the user that a message was received from the third party application server by a specific audible alert and/or a vibratory alert.
In summary, by using the message pushing method and device based on the client browser and the portable terminal device, the cloud message service platform is used as the intermediate server to realize real-time message pushing, and the trouble that the user needs to actively refresh the webpage to obtain the message is eliminated, so that the user experience is improved.
Furthermore, the method according to the invention may also be implemented as a computer program comprising computer program code instructions for carrying out the above-mentioned steps defined in the above-mentioned method of the invention. Alternatively, the method according to the present invention may also be implemented as a computer program product comprising a computer readable medium having stored thereon a computer program for executing the above-mentioned functions defined in the above-mentioned method of the present invention. Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems and methods according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Having described embodiments of the present invention, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen in order to best explain the principles of the embodiments, the practical application, or improvements made to the technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

Claims (9)

1. A message pushing method based on a client browser comprises the following steps:
sending a registration request to a cloud message service platform, wherein the registration request comprises an identifier of a client browser for a cloud message service;
in response to receiving a registration token from the cloud messaging service platform, sending the registration token, a client identification, and a third party application user identification to a third party application server;
pushing messages received from the third-party application server via the cloud message service platform to a user according to a predetermined mode,
wherein the client identification comprises:
an identification of the client browser for a third party application; and
a client physical addressing identity generated from the international mobile equipment identity IMEI and/or the media access MAC address of the client.
2. The message pushing method according to claim 1, wherein the third party application user identification is from a third party application Cookie and/or LocalStorage saved on the client.
3. The message pushing method according to claim 1, wherein the step of pushing the message received from the third party application server via the cloud message service platform to the user in a predetermined manner comprises:
in response to receiving the message, the message is presented in a specified style on a notification bar of the client.
4. The message pushing method according to claim 3, wherein the step of pushing the message received from the third-party application server via the cloud message service platform to the user according to the predetermined manner further comprises:
informing the user that the message is received from the third party application server by a specific sound alert and/or a vibration alert.
5. A message pushing apparatus based on a client browser, comprising:
the registration request sending unit is configured to send a registration request to the cloud message service platform, wherein the registration request comprises an identifier of a client browser for the cloud message service;
an identifier sending unit configured to send, in response to receiving a registration token from the cloud message service platform, the registration token, a client identifier, and a third-party application user identifier to a third-party application server;
a message pushing unit configured to push a message received from the third party application server via the cloud message service platform to a user in a predetermined manner,
wherein the client identification comprises:
an identification of the client browser for a third party application; and
a client physical addressing identity generated from the international mobile equipment identity IMEI and/or the media access MAC address of the client.
6. The message pushing device according to claim 5, wherein the third party application user identification is from a third party application Cookie and/or LocalStorage saved on the client.
7. The message pushing device according to claim 5, wherein the message pushing unit comprises:
and the message display module is configured to respond to the received message and display the message in a specified style on a notification bar of the client.
8. The message pushing device according to claim 7, wherein the message pushing unit further comprises:
a message alert module configured to notify a user that the message is received from the third party application server by a specific sound alert and/or a vibration alert.
9. A portable terminal device comprising:
a network interface enabling the portable terminal device to communicate with a cloud messaging service platform and a third party application server via one or more networks;
the display is used for displaying the message received by the network interface to a user; and
one or more processors coupled with the network interface and the display, the one or more processors configured to:
sending a registration request to the cloud message service platform through the network interface, wherein the registration request comprises an identifier of a client browser for a cloud message service;
sending, by the network interface, in response to receiving a registration token from the cloud messaging service platform, the registration token, a client identification, and a third-party application user identification to a third-party application server;
pushing messages received from the third-party application server via the cloud message service platform to a user according to a predetermined mode,
wherein the client identification comprises:
an identification of the client browser for a third party application; and
a client physical addressing identity generated from the international mobile equipment identity IMEI and/or the media access MAC address of the client.
CN201610530049.7A 2016-07-06 2016-07-06 Message pushing method and device and portable terminal equipment Active CN107592324B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201610530049.7A CN107592324B (en) 2016-07-06 2016-07-06 Message pushing method and device and portable terminal equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201610530049.7A CN107592324B (en) 2016-07-06 2016-07-06 Message pushing method and device and portable terminal equipment

Publications (2)

Publication Number Publication Date
CN107592324A CN107592324A (en) 2018-01-16
CN107592324B true CN107592324B (en) 2021-04-09

Family

ID=61045440

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201610530049.7A Active CN107592324B (en) 2016-07-06 2016-07-06 Message pushing method and device and portable terminal equipment

Country Status (1)

Country Link
CN (1) CN107592324B (en)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108881228B (en) * 2018-06-20 2021-05-04 上海庆科信息技术有限公司 Cloud registration activation method, device, equipment and storage medium
CN109005218A (en) * 2018-07-12 2018-12-14 浪潮软件集团有限公司 Method and device for cross-gatekeeper ordered data transmission of cloud message service platform
CN109005176A (en) * 2018-08-07 2018-12-14 山东省国土资源信息中心 A kind of real estate data reporting system and method
CN108809821A (en) * 2018-09-04 2018-11-13 四川长虹电器股份有限公司 A kind of instant communicating method based on message cloud
CN110401704B (en) * 2019-07-11 2022-04-29 安克创新科技股份有限公司 Message pushing method, device and system
CN113238808A (en) * 2020-01-22 2021-08-10 北京沃东天骏信息技术有限公司 Message pushing method and device
CN114095464B (en) * 2021-11-16 2023-08-08 成都知道创宇信息技术有限公司 Instant message realization method and system
CN115914367B (en) * 2023-02-17 2023-05-30 福建联迪商用科技有限公司 Message pushing method and system of intelligent device

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103037312A (en) * 2011-10-08 2013-04-10 阿里巴巴集团控股有限公司 Message push method and message push device
CN104767775A (en) * 2014-01-06 2015-07-08 腾讯科技(深圳)有限公司 Webpage application information push method and webpage application information push system
CN105357286A (en) * 2015-10-20 2016-02-24 中国电子科技集团公司第二十八研究所 Web-based real-time directional message pushing method

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8407776B2 (en) * 2011-02-11 2013-03-26 Good Technology Corporation Method, apparatus and system for provisioning a push notification session
CN104038490B (en) * 2014-06-09 2018-01-12 可牛网络技术(北京)有限公司 A kind of communication security method of calibration and its device

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103037312A (en) * 2011-10-08 2013-04-10 阿里巴巴集团控股有限公司 Message push method and message push device
CN104767775A (en) * 2014-01-06 2015-07-08 腾讯科技(深圳)有限公司 Webpage application information push method and webpage application information push system
CN105357286A (en) * 2015-10-20 2016-02-24 中国电子科技集团公司第二十八研究所 Web-based real-time directional message pushing method

Also Published As

Publication number Publication date
CN107592324A (en) 2018-01-16

Similar Documents

Publication Publication Date Title
CN107592324B (en) Message pushing method and device and portable terminal equipment
US11991239B2 (en) Systems and methods for authorized, proximal device to device communication without prior pairing within a controlled computing system
US11700256B1 (en) Techniques for group message thread link administration
US11477139B2 (en) Techniques for messaging bot rich communication
US9537925B2 (en) Browser notifications
US20170250935A1 (en) Techniques for messaging bot app interactions
US10291719B2 (en) Enabling communication while limiting access to user information
US8478728B2 (en) Online dating with private support groups
US11044222B2 (en) Automated connection of electronic messaging and social networking services method and apparatus
KR20150087853A (en) Predicted-location notification
US20180183618A1 (en) Techniques for group message thread link joining
US9141944B2 (en) Synchronization of alarms between devices
US9503410B2 (en) Sharing of activity metadata via messaging systems
US11523260B2 (en) Delivery of configuration information for cross-platform application integration
KR20140093491A (en) Method, system and computer-readable storage medium storing computer program for handling shortened url
US10924469B2 (en) Single sign-on (SSO) for internet of things (IoT) applications
CN106716418B (en) Software recommendation method and device, terminal and server
US9658750B2 (en) Private messaging via content provider web sites and applications
US10555148B2 (en) Mobile ghosting
US10462239B1 (en) Flexible units for experimentation
CN110708238B (en) Method and apparatus for processing information
US9693222B1 (en) Sharing social media profiles using wireless identifiers of a communication device
CN110619101A (en) Method and apparatus for processing information
WO2017084315A1 (en) Video call connection method, system and device, and video service end
US10652323B2 (en) Secure and seamless offline file transfer through peer to peer wireless communication

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
TA01 Transfer of patent application right
TA01 Transfer of patent application right

Effective date of registration: 20200714

Address after: 310052 room 508, floor 5, building 4, No. 699, Wangshang Road, Changhe street, Binjiang District, Hangzhou City, Zhejiang Province

Applicant after: Alibaba (China) Co.,Ltd.

Address before: 510627 Guangdong city of Guangzhou province Whampoa Tianhe District Road No. 163 Xiping Yun Lu Yun Ping B radio square 14 storey tower

Applicant before: Guangzhou Dongjing Computer Technology Co.,Ltd.

GR01 Patent grant
GR01 Patent grant