CN111741060A

CN111741060A - Message pushing method and device, computer equipment and storage medium

Info

Publication number: CN111741060A
Application number: CN202010383289.5A
Authority: CN
Inventors: 刘舟; 侯金龙
Original assignee: Guangzhou Sanqi Mutual Entertainment Technology Co ltd
Current assignee: Guangzhou Sanqi Mutual Entertainment Technology Co ltd
Priority date: 2020-05-08
Filing date: 2020-05-08
Publication date: 2020-10-02
Anticipated expiration: 2040-05-08
Also published as: CN111741060B

Abstract

The present application relates to the field of data push, and in particular, to a method and an apparatus for message push, a computer device, and a storage medium. The method comprises the following steps: responding to a message pushing request from a game service end or a pushing task configuration end, determining a plurality of target player accounts needing to push messages and pushing messages corresponding to the target player accounts; determining system identifications corresponding to all target player accounts, wherein the system identifications corresponding to all the target player accounts are used for identifying the operating system types of the target player terminals corresponding to all the target player accounts; and pushing the push message corresponding to each target player account to the target player terminal corresponding to each target player account according to the push mode corresponding to the system identifier of each target player account. The embodiment of the invention can reduce the complexity of the operation of pushing the message for the game player by the game service provider and is beneficial to the later maintenance of the game service provider.

Description

Message pushing method and device, computer equipment and storage medium

Technical Field

The present application relates to the field of data pushing, and in particular, to a message pushing method, an apparatus, a computer device, and a storage medium.

Background

At present, more and more game players play games through smart terminals such as mobile phones. In order to make the game player obtain a better game experience, the game facilitator needs to push some important information to the game player, for example, the game facilitator pushes activity information of the game event to be held to the game player, pushes an emergency situation of the game server to the game player, and the like.

Currently, operating systems loaded on an intelligent terminal mainly include an Android operating system (i.e., an Android operating system) and an apple operating system (i.e., an IOS operating system), so that game players in a game or a certain game zone of a game can be generally classified into game players using the Android operating system and game players using the apple operating system. Because the current android operating system and the apple operating system correspond to different message push modes, a game service provider needs to build push services for game players using the android operating system and game players using the apple operating system to push messages respectively.

However, the above solution can make the operation of pushing messages for the game players by the game service provider cumbersome, and the multiple systems are not conducive to later maintenance.

Disclosure of Invention

Aiming at the defects of the prior art, the invention provides a message pushing method, a message pushing device, computer equipment and a storage medium.

The present invention provides, according to a first aspect, a message pushing method, which in one embodiment includes:

responding to a message pushing request from a game service end or a pushing task configuration end, determining a plurality of target player accounts needing to push messages and pushing messages corresponding to the target player accounts;

determining system identifications corresponding to all target player accounts, wherein the system identifications corresponding to all the target player accounts are used for identifying the operating system types of the target player terminals corresponding to all the target player accounts;

and pushing the push message corresponding to each target player account to the target player terminal corresponding to each target player account according to the push mode corresponding to the system identifier of each target player account.

In one embodiment, the message push request comprises N pieces of player information, and a system identifier and a push message corresponding to each piece of player information, wherein the player information is used for determining a plurality of target player accounts, and N is a positive integer greater than 0;

determining a plurality of target player accounts needing to push messages and push messages corresponding to the target player accounts, wherein the determining comprises the following steps:

determining N target player combinations needing message pushing according to the N pieces of player information, wherein any one target player combination comprises a plurality of target player accounts;

determining the push messages of the player information corresponding to each target player combination as the push messages corresponding to all target player accounts in each target player combination;

determining system identifications corresponding to the target player accounts, wherein the system identifications comprise:

and determining the system identification of the player information corresponding to each target player combination as the system identification corresponding to all target player accounts in each target player combination.

In one embodiment, determining the system identification corresponding to each target player account includes:

determining the association information of a pre-stored player account and a system identifier;

and determining the system identification corresponding to each target player account according to the association information of the player account and the system identification.

In one embodiment, the message pushing method further comprises:

receiving device information sent by a player terminal, wherein the device information comprises a first system identification of the player terminal and a first player account of the player terminal;

determining a second system identifier corresponding to the first player account in the association information of the player account and the system identifier;

and if the second system identification is inconsistent with the first system identification, updating the system identification corresponding to the first player account in the association information of the player account and the system identification to be the first system identification.

In one embodiment, pushing a push message corresponding to each target player account to a target player terminal corresponding to the target player account in a push manner corresponding to a system identifier of each target player account includes:

if the system identification corresponding to the target player account is an apple system identification, invoking an apple message pushing service so as to push a pushing message corresponding to the target player account to a target player terminal corresponding to the target player account through the apple message pushing service;

and if the system identifier corresponding to the target player account is the android system identifier, calling the integrated message pushing service so as to push the pushing message corresponding to the target player account to the target player terminal corresponding to the target player account through the integrated message pushing service.

In one embodiment, if the system identifier corresponding to the target player account is an android system identifier, invoking an integrated message push service to push a push message corresponding to the target player account to a target player terminal corresponding to the target player account through the integrated message push service includes:

if the system identification corresponding to the target player account is the android system identification, determining the area identification corresponding to the target player account;

when the area identifier is a first area identifier, calling an integrated message pushing service so as to push a pushing message corresponding to a target player account to a target player terminal corresponding to the target player account through the integrated message pushing service;

and when the area identifier is the second area identifier, invoking Google message pushing service so as to push a pushing message corresponding to the target player account to the target player terminal corresponding to the target player account through the Google message pushing service.

In one embodiment, after the step of pushing the push message corresponding to each target player account to the target player terminal corresponding to the each target player account, the method includes:

and if receiving the message receiving failure identification sent by the target player terminal corresponding to each target player account, calling a message retransmission service to resend the push message corresponding to each target player account to the target player terminal corresponding to each target player account through the message retransmission service until receiving the message receiving success identification sent by the target player terminal corresponding to each target player account.

The present invention provides a message pushing device according to a second aspect, which in one embodiment comprises:

the system comprises a first determining module, a second determining module and a third determining module, wherein the first determining module is used for responding to a message pushing request from a game service end or a pushing task configuration end, and determining a plurality of target player accounts needing to push messages and pushing messages corresponding to the target player accounts;

a second determining module, configured to determine a system identifier corresponding to each target player account, where the system identifier corresponding to each target player account is used to identify an operating system type of a target player terminal corresponding to each target player account;

and the pushing module is used for pushing the pushing message corresponding to each target player account to the target player terminal corresponding to each target player account according to the pushing mode corresponding to the system identifier of each target player account.

The present invention provides according to a third aspect a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of an embodiment of any of the methods described above when executing the computer program.

The present invention provides according to a fourth aspect a computer-readable storage medium having stored thereon a computer program which, when being executed by a processor, carries out the steps of the embodiments of the method of any one of the above.

In the above embodiment, a push end is provided between a game server and a player terminal carrying different operating systems, where the push end integrates a message pushing manner for an android terminal and an apple terminal, and can push messages for the android terminal and the apple terminal at the same time, and after receiving a message pushing request from the game server or a push task configuration end, the push end determines a plurality of target player accounts needing to push messages and push messages corresponding to the target player accounts, and determines system identifiers corresponding to the target player accounts, where the system identifiers corresponding to the target player accounts are used to identify operating system types of the target player terminals corresponding to the target player accounts; and finally, pushing the push message corresponding to each target player account to the target player terminal corresponding to each target player account according to the push mode corresponding to the system identification of each target player account, so that the operation system type of the player terminal to be pushed by any game server is not required to be considered when the game server pushes the message, the complexity of the operation of the game server for pushing the message for the game player is reduced, and on the other hand, the push modes of an android terminal and an apple terminal are integrated into the push terminal, thereby being beneficial to the later maintenance of the push service by the game server.

Drawings

FIG. 1 is a diagram of an application environment of a message pushing method in one embodiment;

fig. 2 is a schematic flowchart of a message pushing method in an embodiment;

FIG. 3 is a diagram of an application environment of a message pushing method in another embodiment;

fig. 4 is a schematic flowchart of a message pushing method in another embodiment;

FIG. 5 is a block diagram of a message pushing device according to an embodiment;

FIG. 6 is a diagram illustrating an internal structure of a computer device according to an embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

Fig. 1 shows an application environment of a message pushing method in an embodiment of the present invention. 11 shown in fig. 1 is a game server, 12 is a push task configuration end, 20 is a push end, terminals 31 to 33 refer to intelligent terminals with an apple operating system installed (hereinafter referred to as apple terminals), and terminals 41 to 43 refer to intelligent terminals with an android operating system installed (hereinafter referred to as android terminals). The game server may be a server for a certain game or a server for a certain game server in a certain game, the push terminal may be a server responsible for pushing messages to the intelligent terminal, and the terminal may be a mobile phone, a tablet computer or other computing device. Specifically, the game server and the push terminal may be implemented by independent servers or multiple servers. It should be noted that the number of the game servers and the number of the terminals shown in fig. 1 are only examples, the push terminal 11 may interface a plurality of game servers, and the number of the apple terminals or the android terminals that the push terminal 20 needs to push also depends on a specific application scenario.

Wherein, the intelligent terminals used by the game players who need to push messages by the game server 11 may include an apple terminal and an android terminal, the game server 11 does not need to consider how to push messages for both types of terminals, but when the game server 11 needs to push messages to the game player, the game server 11 only needs to send a message push request to the middleware, i.e. the push terminal 20, arranged between the game server 11 and the intelligent terminal (i.e. the player terminal, such as the terminals 31-33 and 41-43 in fig. 1) logged in with the game account of the game player, to indicate to the push terminal 20 to which game players (i.e., target game players) it needs to push messages, and specifically what messages (i.e., push messages) to push to the target game players, the push terminal 20 will then perform the operation of pushing the push message to the target game player based on the specific information in the message push request sent by the game server 11. Further, a person such as an operator/planner with the authority to configure the push task may configure the push task on the push task configuration terminal 12 based on his/her needs (e.g., temporary game activities), and then send a message push request to the push terminal 20 through the push task configuration terminal 12, where the content in the message push request and the response procedure of the push terminal 12 to the message push request may refer to the above description about the interaction procedure between the game service terminal 11 and the push terminal 20.

Specifically, since the message to be pushed to the Apple terminal can only be pushed through an Apple Push Notification Service (APNS) specified by Apple inc, when the game server 11 is to Push a message to a game player using the Apple terminal, the Push terminal 20 needs to call an external Apple Push service (the aforementioned APNS) to Push a message to the Apple terminal used by the game player. However, the android terminal has no designated message push mode, so that the integrated push service shown in fig. 1 is provided in the push end 20, and the push end 20 pushes a message to the android terminal through the integrated push service therein. The integrated push service integrates multiple Message push modes, such as a C2DM (Cloud to Device Messaging), a polling mode, a long connection mode, and an MQTT (Message queue telemetry Transport protocol) mode.

Fig. 2 shows a message pushing method according to an embodiment of the present invention, and the following description will take the example that the method is applied to the pushing end 20 in fig. 1 as an example. The method comprises the following steps:

step S110: in response to a message push request from a game server or a push task configuration end, determining a plurality of target player accounts needing to push messages and push messages corresponding to the target player accounts.

In this embodiment, after receiving a message push request from a game server or a push task configuration end, a push end determines, based on information included in the message push request, a plurality of target player accounts that need to push messages and push messages corresponding to the target player accounts.

In one embodiment, the step of determining, by the push terminal, a plurality of target player accounts needing to push a message and a push message corresponding to each target player account includes the following steps:

and determining the push messages of the player information corresponding to each target player combination as the push messages corresponding to all the target player accounts in each target player combination.

In this embodiment, the message push request includes N pieces of player information, where N is a positive integer greater than 0, and a push message corresponding to each piece of player information. Each piece of player information is used for determining a plurality of target player accounts, wherein the target player accounts are game accounts of game players to push messages at a game service end or a push task configuration end, and can be unique account IDs of the whole game and unique account IDs in a certain game uniform in the game, such as pid123123, playrid-123123 and the like; the push message corresponding to the player information is information to be pushed to all target player accounts determined by the player information by the game server side or the push task configuration side; the system identifier corresponding to the player information is used for identifying the operating system type corresponding to the target player terminal corresponding to all the target player accounts determined by the player information.

In different scenarios, the role of the player information and the information included therein may be different.

For a scenario in which a player account and associated information of player terminal information corresponding to the player account are maintained by a push terminal, the player information includes a game field service identifier and a plurality of player accounts, where the associated information may be a data mapping table. It is understood that the data of the player accounts in different game arcades are usually stored separately, so that the target player account needs to be determined by the game arcade identification and the player account when determining the target player account; a plurality of player accounts in the same player information belong to the same game field.

In this scenario, the game server or the push task configuration end only needs to send player information for determining a target player account to the push end, but does not need to send player terminal information corresponding to the target player account to the push end, and after determining the target player account, the push end can determine a player terminal (i.e., a target player terminal) corresponding to the target player account according to the association information, so that a push message corresponding to the target player account can be subsequently pushed to a related player terminal. The player terminal information may include, among other things, a device identification, a mobile token, etc.

For a scenario in which the player account and the associated information of the player terminal information corresponding thereto are maintained by each game server or push task configuration end, the player information includes, in addition to the game field service identifier and the plurality of player accounts, the player terminal information corresponding to each player account. Thus, the push end can push the push message corresponding to the push end to the relevant player terminal in the following.

Step S120: and determining system identifications corresponding to the target player accounts, wherein the system identifications corresponding to the target player accounts are used for identifying the operating system types of the target player terminals corresponding to the target player accounts.

In this embodiment, each player account corresponds to a system identifier, where the system identifier is used to indicate an operating system type of a player terminal corresponding to the player account, such as an apple system identifier and an android system identifier, it can be understood that the apple system identifier is used to indicate that the operating system type of the player terminal is an apple operating system, and the android system identifier is used to indicate that the operating system type of the player terminal is an android operating system.

In one embodiment, the message push request includes a system identification corresponding to each piece of player information in addition to the N pieces of player information and the push message corresponding to each piece of player information.

In this embodiment, the step of determining, by the push terminal, a system identifier corresponding to each target player account includes:

In this embodiment, the player account and the associated information of the system identifier corresponding to the player account are maintained by each game server or push task configuration end, and the push end itself cannot determine what operating system is installed on the player terminal that needs to push the message, so the message push request sent by the game server or push task configuration end needs to include the system identifier corresponding to each piece of player information. It will be appreciated that the system identifications of multiple player accounts corresponding to the same player information are the same.

In another embodiment, the step of determining, by the push terminal, a system identifier corresponding to each target player account includes:

and determining the pre-stored association information of the player account and the system identifier, and determining the system identifier corresponding to each target player account according to the association information of the player account and the system identifier.

In this embodiment, the player account and the associated information of the system identifier corresponding thereto are maintained by the push terminal. Therefore, the system identification corresponding to each piece of player information does not need to be included in the message push request.

Further, the message pushing method in this embodiment further includes the following steps:

Each player terminal sends own equipment information to the push terminal, the equipment information comprises a system identifier and a player account corresponding to the player terminal, and the push terminal generates and stores associated information for the equipment information after receiving the equipment information.

Considering that some games support game players to log in the same game account on the apple terminal and the android terminal at the same time, and push modes adopted by the apple terminal and the android terminal are different, in order to ensure that push messages to be pushed by the game server side or the push task configuration side can be successfully pushed to related game players, the operation types of the player terminals used by the game players need to be updated in time.

Specifically, after receiving a first system identifier and a first player account sent by a player terminal, a push terminal queries association information between a player account and a system identifier maintained by the push terminal, and if the association information does not include the first player account, the push terminal adds the first player account and the first system identifier to the association information; if the association information includes the first player account, it is further determined whether the system identifier corresponding to the first player account in the association information is a first system identifier, if so, no other operation is required, and if not, the push terminal needs to update the system identifier corresponding to the first player account in the association information to be the first system identifier.

Step S130: and pushing the push message corresponding to each target player account to the target player terminal corresponding to each target player account according to the push mode corresponding to the system identifier of each target player account.

At present, the android operating system and the apple operating system respectively adopt different message push modes, and therefore, when a push terminal pushes a message to a target player terminal corresponding to a target player account, the push terminal needs to push the message in a push mode corresponding to a system identifier of the target player account.

This embodiment is through setting up the propelling movement end between game server and the player terminal who carries on different operating system, this propelling movement end can be simultaneously for tall and erect terminal of ann and apple terminal propelling movement message to any game server no longer need consider the operating system type at its player terminal that wants the propelling movement when wanting the propelling movement message, the complexity of game server for the operation of game player propelling movement message has been reduced, and the propelling movement mode at tall and erect terminal of ann and apple terminal all integrates in the propelling movement end, be favorable to game server to the later maintenance of propelling movement service.

In one embodiment, the step of the push terminal pushing a push message corresponding to each target player account to a target player terminal corresponding to the target player account in a push manner corresponding to a system identifier of each target player account includes:

Since the message to be pushed to the Apple terminal can only be pushed through an Apple Push Notification Service (APNS), which is a Push service specified by Apple inc, the external Apple Push service (APNS) needs to be called when the Push terminal pushes the message to the Apple terminal to Push the message to the Apple terminal. And the android terminal does not have a specified message pushing mode at present, so that the pushing end calls an integrated pushing service integrated in the pushing end to push messages to the android terminal.

Further, in an embodiment, pushing a push message corresponding to each target player account to a target player terminal corresponding to the target player account in a push manner corresponding to a system identifier of each target player account includes:

Exemplarily, the application environment of the present embodiment is as shown in fig. 3, wherein, for the apple terminal, the message is pushed to the apple terminal through the APSN as described above. For the android terminal, the embodiment further divides the android terminal into a national (referring to china) android terminal and a foreign android terminal. For a domestic android terminal, a message can be pushed through an integrated message pushing service inside a pushing terminal, and for a foreign android terminal, a message can be pushed through a pushing service provided by google companies outside the pushing terminal, namely, a first base cloud message (FCM).

As shown in fig. 4, in an embodiment, after the step of pushing the push message corresponding to each target player account to the target player terminal corresponding to each target player account, the method includes the following steps:

step S140: and if receiving the message receiving failure identification sent by the target player terminal corresponding to each target player account, calling a message retransmission service to resend the push message corresponding to each target player account to the target player terminal corresponding to each target player account through the message retransmission service until receiving the message receiving success identification sent by the target player terminal corresponding to each target player account.

In this embodiment, the message retransmission service may be a module deployed in the push end, and configured to execute a message retransmission mechanism. Specifically, in order to ensure that the push message can be successfully sent to the target player terminal, the player terminal feeds back an identifier indicating a message receiving state to the push terminal, so that the push terminal performs a corresponding operation based on the identifier.

Specifically, if the identifier fed back by the player terminal is a message acceptance failure identifier, the push terminal invokes a message retransmission service to re-push the message to the player terminal until receiving a message acceptance success identifier pushed by the player terminal. The method can set a timing task for the message retransmission service, so that the message retransmission service operates independently from the push terminal. The push terminal sends the relevant information of the player terminal needing to retransmit the push message to the message retransmission service, and when the system time meets the trigger condition of the timing task, the message retransmission service automatically executes the task content of the timing task. Illustratively, every preset time interval (e.g., 5 seconds, 10 seconds, etc.), the message retransmission service retransmits the push message for the player terminal transmitted by the push terminal in the preset time interval.

Further, the problem that the player terminal cannot successfully receive the push message may not be solved in a short time, so a maximum number threshold of message retransmission may be set for the message retransmission service, the message retransmission service records the number of retransmission times of the player terminal after retransmitting the push message for the player terminal, and when the number of retransmission times of the player terminal, that is, the number of times of the push message retransmission for the player terminal by the message retransmission service reaches the maximum number threshold, the message retransmission service does not retransmit the push message to the player terminal, thereby avoiding repeatedly occupying computing resources.

In one embodiment, as shown in fig. 5, there is provided a message pushing apparatus, including the following modules:

a first determining module 110, configured to determine, in response to a message push request from a game server or a push task configuration end, a plurality of target player accounts that need to push messages and push messages corresponding to the target player accounts;

a second determining module 120, configured to determine a system identifier corresponding to each target player account, where the system identifier corresponding to each target player account is used to identify an operating system type of a target player terminal corresponding to each target player account;

the pushing module 130 is configured to push, according to a pushing manner corresponding to the system identifier of each target player account, a pushing message corresponding to each target player account to a target player terminal corresponding to each target player account.

In one embodiment, the message push request includes N pieces of player information, and a system identification and push message corresponding to each piece of player information, the player information being used to determine a plurality of target player accounts, N being a positive integer greater than 0. Wherein, the first determining module comprises:

the player combination determining submodule is used for determining N target player combinations needing to push messages according to the N pieces of player information, and any one target player combination comprises a plurality of target player accounts;

the push message determining submodule is used for determining the push messages of the player information corresponding to each target player combination as the push messages corresponding to all the target player accounts in each target player combination;

a second determination module comprising:

and the system identification determining submodule is used for determining the system identification of the player information corresponding to each target player combination as the system identification corresponding to all the target player accounts in each target player combination.

In one embodiment, the second determining module includes:

the association information determining submodule is used for determining association information of a pre-stored player account and a system identifier;

and the system identification determining submodule is used for determining the system identification corresponding to each target player account according to the association information of the player account and the system identification.

In one embodiment, the device information receiving module is configured to receive device information sent by a player terminal, where the device information includes a first system identifier of the player terminal and a first player account of the player terminal;

the third determining module is used for determining a second system identifier corresponding to the first player account in the association information of the player account and the system identifier;

and the updating module is used for updating the system identifier corresponding to the first player account in the association information of the player account and the system identifier into the first system identifier when the second system identifier is inconsistent with the first system identifier.

In one embodiment, a push module, comprising:

the first pushing submodule is used for calling an apple message pushing service when the system identifier corresponding to the target player account is an apple system identifier, so that a pushing message corresponding to the target player account is pushed to a target player terminal corresponding to the target player account through the apple message pushing service;

and the second pushing submodule is used for calling the integrated message pushing service when the system identifier corresponding to the target player account is the android system identifier, so as to push the pushing message corresponding to the target player account to the target player terminal corresponding to the target player account through the integrated message pushing service.

In one embodiment, the second push submodule includes:

the area identification determining unit is used for determining the area identification corresponding to the target player account when the system identification corresponding to the target player account is the android system identification;

the first pushing unit is used for calling the integrated message pushing service when the area identifier is the first area identifier so as to push a pushing message corresponding to the target player account to a target player terminal corresponding to the target player account through the integrated message pushing service;

and the second pushing unit is used for calling the Google message pushing service when the area identifier is the second area identifier so as to push the pushing message corresponding to the target player account to the target player terminal corresponding to the target player account through the Google message pushing service.

In one embodiment, the message pushing apparatus further includes a message retransmission module 140.

The message resending module 140 is configured to, when receiving a message reception failure identifier sent by a target player terminal corresponding to each target player account, invoke a message resending service, so as to resend the push message corresponding to each target player account to the target player terminal corresponding to each target player account through the message resending service until receiving a message reception success identifier sent by the target player terminal corresponding to each target player account.

For specific definition of the message pushing device, refer to the above definition of the message pushing method, which is not described herein again. The modules in the message pushing device can be wholly or partially implemented by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.

In one embodiment, a computer device is provided, the internal structure of which may be as shown in FIG. 6. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing data such as association information between a player account and a player terminal corresponding to the player account. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a message push method.

Those skilled in the art will appreciate that the architecture shown in fig. 6 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, a computer device is provided, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:

responding to a message pushing request from a game service end or a pushing task configuration end, determining a plurality of target player accounts needing to push messages and pushing messages corresponding to the target player accounts; determining system identifications corresponding to all target player accounts, wherein the system identifications corresponding to all the target player accounts are used for identifying the operating system types of the target player terminals corresponding to all the target player accounts; and pushing the push message corresponding to each target player account to the target player terminal corresponding to each target player account according to the push mode corresponding to the system identifier of each target player account.

In one embodiment, the message push request comprises N pieces of player information, and a system identifier and a push message corresponding to each piece of player information, wherein the player information is used for determining a plurality of target player accounts, and N is a positive integer greater than 0; the processor executes the computer program to realize the following steps when determining a plurality of target player accounts needing to push messages and push messages corresponding to the target player accounts:

determining N target player combinations needing message pushing according to the N pieces of player information, wherein any one target player combination comprises a plurality of target player accounts; determining the push messages of the player information corresponding to each target player combination as the push messages corresponding to all target player accounts in each target player combination;

the processor executes the computer program to realize the following steps when determining the system identification corresponding to each target player account:

In one embodiment, the processor executes the computer program to determine the system identifier corresponding to each target player account, and further performs the following steps:

In one embodiment, the processor executes the computer program, further implementing the steps of:

receiving device information sent by a player terminal, wherein the device information comprises a first system identification of the player terminal and a first player account of the player terminal; determining a second system identifier corresponding to the first player account in the association information of the player account and the system identifier; and if the second system identification is inconsistent with the first system identification, updating the system identification corresponding to the first player account in the association information of the player account and the system identification to be the first system identification.

In one embodiment, when the processor executes the computer program to realize that the push message corresponding to each target player account is pushed to the target player terminal corresponding to the target player account in a push manner corresponding to the system identifier of each target player account, the following steps are further realized:

if the system identification corresponding to the target player account is an apple system identification, invoking an apple message pushing service so as to push a pushing message corresponding to the target player account to a target player terminal corresponding to the target player account through the apple message pushing service; and if the system identifier corresponding to the target player account is the android system identifier, calling the integrated message pushing service so as to push the pushing message corresponding to the target player account to the target player terminal corresponding to the target player account through the integrated message pushing service.

In one embodiment, a processor executes a computer program to realize that if a system identifier corresponding to a target player account is an android system identifier, an integrated message push service is invoked to push a push message corresponding to the target player account to a target player terminal corresponding to the target player account through the integrated message push service, and then the following steps are further realized:

if the system identification corresponding to the target player account is the android system identification, determining the area identification corresponding to the target player account; when the area identifier is a first area identifier, calling an integrated message pushing service so as to push a pushing message corresponding to a target player account to a target player terminal corresponding to the target player account through the integrated message pushing service; and when the area identifier is the second area identifier, invoking Google message pushing service so as to push a pushing message corresponding to the target player account to the target player terminal corresponding to the target player account through the Google message pushing service.

In one embodiment, after the step of pushing the push message corresponding to each target player account to the target player terminal corresponding to each target player account is implemented when the processor executes the computer program, the following steps are further implemented:

In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:

In one embodiment, the message push request comprises N pieces of player information, and a system identifier and a push message corresponding to each piece of player information, wherein the player information is used for determining a plurality of target player accounts, and N is a positive integer greater than 0; when the computer program is executed by the processor and determines a plurality of target player accounts needing to push messages and push messages corresponding to the target player accounts, the following steps are also realized:

when system identification corresponding to each target player account is determined, the following steps are also realized:

In one embodiment, the computer program, when executed by the processor, further performs the following steps when determining the system identifier corresponding to each target player account:

In one embodiment, the computer program is executed by a processor, further implementing the steps of:

In one embodiment, when the computer program is executed by the processor, and pushes a push message corresponding to each target player account to a target player terminal corresponding to the target player account in a push manner corresponding to a system identifier of each target player account, the following steps are further implemented:

In one embodiment, the computer program is executed by a processor, and if a system identifier corresponding to a target player account is an android system identifier, the integrated message push service is invoked to push a push message corresponding to the target player account to a target player terminal corresponding to the target player account through the integrated message push service, and the following steps are further implemented:

In one embodiment, after the step of pushing the push message corresponding to each target player account to the target player terminal corresponding to each target player account is executed by the processor, the following steps are further implemented:

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims

1. A message pushing method, comprising:

2. The message pushing method according to claim 1, wherein the message pushing request includes N pieces of player information, and a system identification and a pushing message corresponding to each piece of player information, the player information is used for determining a plurality of target player accounts, N is a positive integer greater than 0;

the determining a plurality of target player accounts needing to push messages and push messages corresponding to the target player accounts comprises:

the determining the system identifier corresponding to each target player account includes:

3. The message pushing method according to claim 1, wherein the determining the system identifier corresponding to each target player account includes:

and determining the system identification corresponding to each target player account according to the association information of the player accounts and the system identification.

4. The message pushing method of claim 3, further comprising:

determining a second system identification corresponding to the first player account in the association information of the player account and the system identification;

and if the second system identification is inconsistent with the first system identification, updating the system identification corresponding to the first player account in the association information of the player account and the system identification as the first system identification.

5. The message pushing method according to claim 1, wherein the pushing of the push message corresponding to each target player account to the target player terminal corresponding to the target player account in a push manner corresponding to the system identifier of each target player account comprises:

and if the system identifier corresponding to the target player account is the android system identifier, calling an integrated message pushing service so as to push a pushing message corresponding to the target player account to a target player terminal corresponding to the target player account through the integrated message pushing service.

6. The message pushing method according to claim 5, wherein if the system identifier corresponding to the target player account is an android system identifier, invoking an integrated message pushing service to push a push message corresponding to the target player account to a target player terminal corresponding to the target player account through the integrated message pushing service, includes:

when the area identifier is a first area identifier, calling an integrated message pushing service so as to push a pushing message corresponding to the target player account to a target player terminal corresponding to the target player account through the integrated message pushing service;

and when the area identifier is a second area identifier, invoking Google message pushing service so as to push a pushing message corresponding to the target player account to a target player terminal corresponding to the target player account through the Google message pushing service.

7. Message push method according to claim 1,

after the step of pushing the push message corresponding to each target player account to the target player terminal corresponding to each target player account, the method includes:

8. A message push apparatus, comprising:

9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the method of any of claims 1 to 7 are implemented when the computer program is executed by the processor.

10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.