Prop management method, device, equipment and storage medium

文档序号：1582790 发布日期：2020-02-04 浏览：31次中文

阅读说明：本技术 道具管理方法、装置、设备及存储介质 (Prop management method, device, equipment and storage medium ) 是由李大明于 2019-10-29 设计创作，主要内容包括：本申请提供了一种道具管理方法、装置、设备及存储介质；所述方法包括：基于接收到的特权场景注册请求,获取请求方的属性信息；当确定所述属性信息满足特权场景注册条件时,获取所述请求方对应的用户数据；基于所述用户数据确定所述用户的偏好信息,并基于所述偏好信息,确定所述请求方的候选道具信息；向所述请求方发送注册成功的响应消息,所述响应消息中携带有所述候选道具信息。通过本申请,能够根据特权场景中用户的偏好信息提供道具,使得道具投放更有针对性。(The application provides a method, a device, equipment and a storage medium for managing a road furniture; the method comprises the following steps: acquiring attribute information of a requester based on a received privileged scene registration request; when the attribute information is determined to meet the privilege scene registration condition, acquiring user data corresponding to the requester; determining preference information of the user based on the user data, and determining candidate prop information of the requester based on the preference information; and sending a response message of successful registration to the requester, wherein the response message carries the candidate prop information. Through the method and the device, the props can be provided according to the preference information of the users in the privilege scene, so that the prop delivery is more targeted.)

1. A method for asset management, comprising:

acquiring attribute information of a requester based on a received privileged scene registration request;

when the attribute information is determined to meet the privilege scene registration condition, acquiring user data corresponding to the requester;

determining preference information of the user based on the user data, and determining candidate prop information of the requester based on the preference information;

and sending a response message of successful registration to the requester, wherein the response message carries the candidate prop information.

2. The method of claim 1, further comprising:

receiving target prop information sent by a requester;

performing qualification audit on the requester based on the attribute information and the target prop information to obtain an audit result;

when the auditing result shows that the requester is qualified for the target prop information, sending payment information to the requester;

and when a notification message of successful payment is received, establishing a corresponding relation between the requester and the target prop information.

3. The method of claim 1 or 2, further comprising:

receiving a prop inquiry request sent by a service server;

acquiring characteristic information of a terminal which has logged in the service server based on the prop query request;

determining a privilege scene where the terminal is located based on the characteristic information, and acquiring prop information corresponding to the privilege scene;

and sending the prop information to the service server.

4. The method of claim 3, further comprising:

acquiring activity information of the privilege scene;

based on the activity information, when the privilege scene is determined to meet a preset effective condition, acquiring the failure time of the prop information;

and determining whether the prop information is overdue or not according to the current time and the expiration time, wherein when the prop information is not overdue, the prop information is sent to the service server.

5. The method of claim 4, further comprising:

determining the residual use duration corresponding to the prop information according to the failure time and the current time;

and when the residual use duration is less than a duration threshold, sending a payment reminding message to a requester corresponding to the prop information, wherein the payment reminding message carries the residual use duration and the payment amount.

6. The method of claim 5, further comprising:

and when the payment success message of the requester is not received after the expiration time is reached, deleting the corresponding relation between the prop information and the requester so as to revoke the prop use permission of the requester.

7. The method according to any one of claims 4 to 6, further comprising:

acquiring prop activation frequency information and network routing information of each terminal in the privilege scene;

determining a target terminal based on the property activation frequency information and the network routing information of each terminal, wherein the target terminal is a terminal of which the property activation frequency information and the network routing information do not accord with a security policy;

and when detecting that the terminal logged in the service server is a target terminal, sending a response message which can be used without free props to the service server.

8. A ballast management apparatus, comprising:

the first acquisition module is used for acquiring attribute information of a requester based on the received privilege scene registration request;

the second acquisition module is used for acquiring the user data corresponding to the requester when the attribute information is determined to meet the privilege scene registration condition;

the first determination module is used for determining preference information of the user based on the user data and determining candidate prop information of the requester based on the preference information;

and the first sending module is used for sending a response message of successful registration to the requester, wherein the response message carries the candidate prop information.

9. A ballast management apparatus, comprising:

a memory for storing executable instructions;

a processor for implementing the method of any one of claims 1 to 7 when executing executable instructions stored in the memory.

10. A storage medium having stored thereon executable instructions for causing a processor to perform the method of any one of claims 1 to 7 when executed.

Technical Field

The present application relates to the field of internet technologies, and in particular, to a method, an apparatus, a device, and a storage medium for managing a road instrument.

Background

With the development of internet technology and intelligent terminals, people's entertainment modes have changed over the world. People can use the intelligent terminal to check news, watch videos, listen to music, play online games and the like anytime and anywhere. In particular, during the playing of the network game, the user can quickly complete the game task or decorate the own game role by using some props. At present, the props used in the games are generally won by users who buy, reach a certain level or complete a certain task, the obtaining mode is relatively single, and differentiated experience cannot be provided.

Disclosure of Invention

The embodiment of the application provides a method and a device for managing props and a storage medium, which can provide props according to preference information of users in privilege scenes, so that the prop delivery is more targeted.

The technical scheme of the embodiment of the application is realized as follows:

the embodiment of the application provides a method for managing a road appliance, which comprises the following steps:

acquiring attribute information of a requester based on a received privileged scene registration request;

when the attribute information is determined to meet the privilege scene registration condition, acquiring user data corresponding to the requester;

determining preference information of the user based on the user data, and determining candidate prop information of the requester based on the preference information;

and sending a response message of successful registration to the requester, wherein the response message carries the candidate prop information.

The embodiment of the application provides a glassware management device, includes:

the first acquisition module is used for acquiring attribute information of a requester based on the received privileged scene registration request;

the second acquisition module is used for acquiring the user data corresponding to the requester when the attribute information is determined to meet the privilege scene registration condition;

and the first sending module is used for sending a response message of successful registration to the requester, wherein the response message carries the candidate prop information.

The embodiment of the application provides a glassware management equipment, includes:

a memory for storing executable instructions;

and the processor is used for realizing the method provided by the embodiment of the application when executing the executable instructions stored in the memory.

The embodiment of the application provides a storage medium, which stores executable instructions and is used for causing a processor to execute the executable instructions so as to realize the method provided by the embodiment of the application.

The embodiment of the application has the following beneficial effects:

in the property management method provided by the embodiment of the application, when a registration request for becoming a privileged scene is received, attribute information of a requesting party, such as a geographic position, an operator name, business license information and the like, is acquired, and when it is determined that the attribute information meets a privileged scene registration condition, user data corresponding to the requesting party is acquired; and then portraying the user through the user data to determine preference information of the user, determining candidate prop information of the requester based on the preference information, and finally sending a response message carrying the candidate prop information to the requester, so that the prop information sent to the requester is determined based on the preference information of the user reaching the geographical position of the requester, thereby being capable of providing differentiated services more pertinently and bringing customized service experience to the user.

Drawings

Fig. 1 is a schematic network architecture diagram of a prop management method according to an embodiment of the present application;

fig. 2 is a schematic structural diagram of a prop management server 200 according to an embodiment of the present disclosure;

fig. 3 is a schematic flow chart of an implementation of the prop management method according to the embodiment of the present application;

fig. 4 is a schematic flow chart of another implementation of the prop management method according to the embodiment of the present application;

fig. 5 is a schematic flow chart of another implementation of the prop management method according to the embodiment of the present application;

fig. 6 is a schematic structural diagram of a privileged item management system according to an embodiment of the present application;

fig. 7 is a schematic diagram illustrating an implementation flow of an access stage of a privileged prop in a physical scene according to an embodiment of the present application;

fig. 8 is a schematic view of an implementation flow of the user privileged item experience phase according to the embodiment of the present application.

Detailed Description

In order to make the objectives, technical solutions and advantages of the present application clearer, the present application will be described in further detail with reference to the attached drawings, the described embodiments should not be considered as limiting the present application, and all other embodiments obtained by a person of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

In the following description, reference is made to "some embodiments" which describe a subset of all possible embodiments, but it is understood that "some embodiments" may be the same subset or different subsets of all possible embodiments, and may be combined with each other without conflict.

In the following description, references to the terms "first \ second \ third" are only to distinguish similar objects and do not denote a particular order, but rather the terms "first \ second \ third" are used to interchange specific orders or sequences, where appropriate, so as to enable the embodiments of the application described herein to be practiced in other than the order shown or described herein.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of the present application only and is not intended to be limiting of the application.

Before further detailed description of the embodiments of the present application, terms and expressions referred to in the embodiments of the present application will be described, and the terms and expressions referred to in the embodiments of the present application will be used for the following explanation.

1) Props: items that can be acquired and collected by a user. The prop has various functions, which can be functions beneficial to the role, such as supplementing life value; may be a function that is harmful to the character, such as a restricted action; the props can be obtained by completing tasks, or can be purchased by users to obtain additional functions and image decorations;

2) privileged props: the game function is an article which is purchased by a user in a property store or is obtained by exchanging certain resources in a positive way and is added to the game function. The privileged prop in this document refers to a proprietary scene prop owned by a privileged scene. The appearance of the prop is not due to purchase, but is related to the physical (or virtual network space) scene where the user is located, and the prop automatically disappears after the user leaves the privileged scene.

3) Privileged scenarios: the user can experience more rights and interests relative to other places without charge by artificially dividing the off-line physical place (or the virtual network space), and additional value-added services such as privileged props and the like are included. .

In order to better understand the embodiment of the present application, a method for managing props and disadvantages of the related art will be described first.

At present, the methods for associating the in-game props with physical scenes for managing the props mainly include the following methods:

the first way, providing specific props according to different service areas: for a certain game application, the mall properties provided by the domestic version and the foreign version are different, and the mall properties are one embodiment of the requirement of the local operation.

Second, game equity distribution based on specific scenarios: at a particular operating location, the game automatically unlocks a particular equity package, and all users located in that particular scenario passively accept it, even if the equity is not at all appealing to the user.

The disadvantages of the two methods for managing props mainly include:

the first mode is as follows: customizing the mall prop according to the service area can meet individual requirements of different regions, but dimension division is simple, and a refined operation strategy and effective differentiated services cannot be supported;

the second mode is as follows: the game right distribution based on the specific scenes focuses on the specific user scenes, differentiation among the scenes is not achieved, and in addition, all users in the privileged scenes passively accept the unlocked game privilege package and have no right selected by the users.

Based on this, the embodiment of the application provides a method for managing a property, which designs a privileged property according to the interests and hobbies of users in a specific scene, attracts more users with the same appeal to gather a privileged scene experience service, can provide customized service experience for the users, and can realize online and offline interactive operation.

An exemplary application of the device implementing the embodiment of the present application is described below, and the device provided in the embodiment of the present application may be implemented as a prop management server. In the following, an exemplary application covering a server when the apparatus is implemented as a prop management server will be described.

Referring to fig. 1, fig. 1 is a schematic diagram of a network architecture of a prop management method according to an embodiment of the present application, and as shown in fig. 1, the network architecture at least includes a user terminal 100, a prop management server 200, a network 300, a service server 400, and a requester terminal 500. In order to support an exemplary application, the user terminal 100 is connected to the service server 400 through the network 300, and the service server 400 is connected to the item management server 200 through the network 300. The user terminal 100 and the requester terminal 500 may be mobile terminals having wireless communication capability, such as a mobile phone (mobile phone), a tablet computer, and a notebook computer, and may be implemented as a desktop computer having a computing function, a desktop computer, and the like, which are not mobile. The prop management server 200 and the service server 400 may be a single server device entity, may also be a server cluster, and may also be a cloud server. In this embodiment, the prop management server 200 may be one device entity, or may be at least two device entities, and when the prop management server 200 is one device entity, the device entity completes all steps that the prop management server needs to execute in this embodiment; when the property management server 200 is composed of at least two equipment entities, the at least two equipment entities respectively perform different steps, for example, in some embodiments, the property management server 200 may perform the functions of a privilege server and a scenario manager. The network 300 may be a wide area network or a local area network, or a combination of both, using wireless links for data transmission.

The user terminal 100 may be installed with a service client corresponding to the service server 400, for example, a game application client, and the user terminal 100 may perform data communication with the service server 400 through the service client; of course, the user terminal 100 may access the service server 400 through a web page. Similarly, a service client may be installed in the requester terminal 500, and applies for becoming a privileged scene through the privileged scene client, the current requester terminal 500 may also apply for becoming a privileged scene from the property management server 200 in a web page form, the property management server 200, after receiving the registration request, checks the qualification of the requester, determines candidate property information according to the preference information of the current user of the requester after the checking is passed, and returns the candidate property information to the requester terminal 500, and after the requester terminal 500 selects the target property information and completes payment, the property management server 200 establishes a corresponding relationship between the requester and the property information.

After the user terminal 100 in the geographical position of the requester logs in the target service, the service server 400 sends a prop query request to the prop management server 200, the prop management server 200 determines the privilege scene where the terminal is located according to the characteristic information of the terminal, determines the corresponding prop information, and then sends the prop information to the service server 400, and the service server 400 sends the prop information to the user terminal 100 to be displayed in a prop mall of the user terminal 100.

The apparatus provided in the embodiments of the present application may be implemented as hardware or a combination of hardware and software, and various exemplary implementations of the apparatus provided in the embodiments of the present application are described below.

Other exemplary configurations of the prop management server 200 are envisioned in accordance with the exemplary configuration of the prop management server 200 shown in fig. 2, and thus the configurations described herein should not be considered limiting, e.g., some of the components described below may be omitted, or components not described below may be added to accommodate the particular needs of certain applications.

The item management server 200 shown in fig. 2 includes: at least one processor 210, memory 240, at least one network interface 220, and a user interface 230. Each of the components in prop management server 200 are coupled together by bus system 250. It will be appreciated that the bus system 250 is used to enable communications among the components. The bus system 250 includes a power bus, a control bus, and a status signal bus in addition to a data bus. For clarity of illustration, however, the various buses are labeled as bus system 250 in fig. 2.

The user interface 230 may include a display, a keyboard, a mouse, a touch-sensitive pad, a touch screen, and the like.

The memory 240 may be either volatile memory or nonvolatile memory, and may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read Only Memory (ROM). The volatile Memory may be Random Access Memory (RAM). The memory 240 described in embodiments herein is intended to comprise any suitable type of memory.

Memory 240 in the embodiments of the present application is capable of storing data to support the operation of prop management server 200. Examples of such data include: any computer program for operating on prop management server 200, such as an operating system and an application program. The operating system includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, and is used for implementing various basic services and processing hardware-based tasks. The application program may include various application programs.

As an example of the method provided by the embodiment of the present application implemented by software, the method provided by the embodiment of the present application may be directly embodied as a combination of software modules executed by the processor 210, the software modules may be located in a storage medium located in the memory 240, and the processor 210 reads executable instructions included in the software modules in the memory 240, and completes the method provided by the embodiment of the present application in combination with necessary hardware (for example, including the processor 210 and other components connected to the bus 250).

By way of example, the Processor 210 may be an integrated circuit chip having Signal processing capabilities, such as a general purpose Processor, a Digital Signal Processor (DSP), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or the like, wherein the general purpose Processor may be a microprocessor or any conventional Processor or the like.

The prop management method provided by the embodiment of the present application will be described in conjunction with an exemplary application and implementation of the terminal provided by the embodiment of the present application.

Referring to fig. 3, fig. 3 is a schematic view of an implementation flow of the item management method provided in the embodiment of the present application, which is applied to the item management server shown in fig. 1, and will be described with reference to the steps shown in fig. 3.

Step S101, based on the received privilege scene registration request, obtaining the attribute information of the requester.

Here, when the gateway management server receives a privileged scene registration request for becoming a privileged scene sent by a requester terminal, the attribute information of the requester carried in the privileged scene registration request is acquired. The requesting party may be an operation manager of a certain internet cafe, an operator of a certain shop in a shopping mall, or an operator of the whole shopping mall. The attribute information of the requestor may include applicant information (including, for example, the name, identification number of the applicant), geographic location and scale of the requestor, industry attributes, license information, whether there is a central node, etc. For example, the attribute information of the requester may be: zhang III, an identity card number 123XXXXX, an XX road XX number of an anser tower area in xi' an city, Shaanxi province, 1000 square meters, an industry attribute of an internet bar, a business license number of 610 XXXXXXX, and a central node.

Step S102, when the attribute information is determined to meet the registration condition of the privilege scene, the user data corresponding to the request is obtained.

Here, the privilege scenario registration condition may be preset, and in the privilege scenario registration condition, the geographic location may be limited not to be too far away and the scale may not be too small, and the industry attribute may be limited, for example, the industry attribute may not be the medical industry, the education industry, and the like. For example, the privilege scene registration condition may be within three rings of xi' an city, shaxi province, the scale is more than 500 square meters, the industry attribute is not the medical and educational industry, and the applicant information corresponds to the business license information.

The user data corresponding to the requesting party may be related data of a user in the geographical location of the requesting party, and when the requesting party is an internet cafe, the user in the geographical location of the requesting party may be a user surfing the internet in the internet cafe; when the requester is a shopping mall, the user at the geographical location of the requester is the user corresponding to the terminal connected to the wireless network of the shopping mall.

The user data may include portrait data of the user and may also include historical behavior data of the user. The portrait data of the user can be obtained by analyzing a large amount of historical data of the user through big data, and the portrait data can comprise basic information of the user, such as the age and the sex of the user, and can also comprise preference data, life habit data and the like of the user; the historical behavior data of the user may include game data generated by the user during the game.

Since the user data is generally stored in the service server, the user data may be obtained from the service server by the property management server when the user data is obtained.

Step S103, determining preference information of the user based on the user data, and determining candidate prop information of the requester based on the preference information.

And the property management server stores a complete scene characteristic information base to judge the physical scene where the user is located and feed back the privileged property applicable to the scene to the service server, so that after the preference information of the user is determined, the candidate property information corresponding to the preference information can be further determined according to the scene characteristic information base.

Candidate item information may include items that may be selected, the manner of use of the items, the role of the items, and the purchase price, among others.

Step S104, sending a response message of successful registration to the requester, wherein the response message carries the candidate prop information.

Here, after determining the candidate item information, the item management server returns a response message of successful registration to the requester to inform the requester to select the item desired to be purchased.

In the property management method provided by the embodiment of the application, when a registration request for becoming a privileged scene is received, attribute information of a requesting party, such as a geographic position, an operator name, business license information and the like, is acquired, and when the attribute information is determined to meet a privileged scene registration condition, user data of the geographic position where the requesting party is located is acquired; and then portraying the user through the user data to determine preference information of the user, determining candidate prop information of the requester based on the preference information, and finally sending a response message carrying the candidate prop information to the requester, so that the prop information sent to the requester is determined based on the preference information of the user reaching the geographical position of the requester, thereby being capable of providing differentiated services more pertinently and bringing customized service experience to the user.

In some embodiments, as shown in fig. 4, after step S104, the following steps may also be performed:

and step S105, receiving the target prop information sent by the requester.

Here, after receiving the candidate item information sent by the item management server, the requester may select target item information according to the role, price, and the like of each item in the candidate item information, and send the selected target item information to the item management server.

And S106, performing qualification audit on the requester based on the attribute information and the target prop information to obtain an audit result.

Here, since the candidate item information is determined according to the preference information of the user, after the requester selects the target item information, the item management server is further required to perform qualification audit on the requester according to the attribute information of the requester to determine whether the requester meets the use condition of the target item information. When the requester is determined to meet the use condition of the target prop information according to the attribute information of the requester, an audit result which passes the audit is obtained, and the requester is indicated to have the use qualification of the target prop information at this time, and the step S107 is performed; when the requester is determined not to meet the use condition of the target prop information according to the attribute information of the requester, an auditing result of the auditing failure is obtained, and the result shows that the requester does not have the use qualification of the target prop information, so that the prop management server returns a notification message that the selection of the target prop information is invalid to the requester.

And step S107, when the auditing result shows that the requester has the use qualification of the target item information, sending payment information to the requester.

Here, the payment information at least includes a payment amount, where the payment amount is determined according to a purchase price in the target prop information, for example, the target prop information includes three props, and the purchase prices are 100 yuan, 50 yuan, and 70 yuan, respectively, so that the payment amount is 100+50+ 70-220 yuan. After receiving the payment information, the requester can carry out online payment so as to complete the application process of the privileged prop.

Step S108, when the notification message of successful payment is received, the corresponding relation between the requester and the target prop information is established.

Here, when the ballast management server receives the notification message that the payment is successful, it indicates that the requester has completed the payment, at this time, a configuration relationship may be established between the target ballast information and the requester, and once the configuration of the target ballast information is in effect, when the user is at the geographic location of the requester, the user logs in a ballast mall and can experience the privileged ballast corresponding to the requester free of charge.

Since the process of authorization of the item of the requesting party is completed through the above steps S101 to S108, when the user logs in the target service through the terminal machine located at the geographical location of the requesting party, the experience process of using the privileged item can be realized through the following steps S21 to S26, which will be described below with reference to the respective steps.

Step S21, when the user logs in the target service through the terminal, the service server sends item inquiry request to the item management server.

Here, when the user logs in the target service through the service client in the terminal, the scene client may collect the feature information of the terminal and transmit the feature information of the terminal to the service server through the service client. After receiving the characteristic information of the terminal, the service server sends a prop query request to the prop management server to obtain a prop which can be used by the terminal, wherein the prop query request carries the characteristic information of the terminal. In this embodiment, the characteristic information of the terminal may include: the terminal identifier (for example, may be an IP address of the terminal), a network topology where the terminal is located, and in some embodiments, the terminal may further include hardware configuration information, software configuration information, and the like.

In some embodiments, when a user logs in a target service through a service client in a terminal, a service server may directly send a prop query request to a prop management server, where the prop query request carries a terminal identifier.

Step S22, the property management server receives the property query request sent by the service server.

And step S23, the property management server acquires the characteristic information of the terminal logged in the service server based on the property query request.

Here, when the characteristic information of the terminal is carried in the property query request, when step S23 is implemented, the characteristic information of the terminal may be obtained by analyzing the property query request; when the property query request only carries the terminal identifier but does not carry the characteristic information of the terminal, the property management server can obtain the characteristic information of the terminal sent by the scene gateway through the terminal identifier.

Step S24, the property management server determines the privilege scenario in which the terminal is located based on the feature information, and acquires property information corresponding to the privilege scenario.

Here, in the embodiment of the application, the property management server determines the physical scene where the terminal is located according to the completed scene feature information base to determine the privilege scene where the terminal is located, and further obtains the property information corresponding to the privilege scene when the property management server determines the privilege scene where the terminal is located.

For example, according to the characteristic information of the terminal, it is determined that the terminal is located in the privilege scene of the internet bar a, and then the prop management server may determine the prop information corresponding to the internet bar a according to the pre-established correspondence between the requester and the prop information.

And step S25, the item management server sends the item information to the service server.

Step S26, the service server sends the item information to the terminal machine to display the item information on the terminal machine.

Here, after receiving the property information, the service server may obtain historical data of the user in the target service according to the user identifier of the target service in which the user logs in, and further may determine a display mode when the property information is sent to the terminal according to the historical data. Further, the historical data may include the existing property of the user, the level of the user, the role that the user uses more, and the like, and when determining the display mode when transmitting the property information to the terminal according to the historical data, the property that the user does not have may be preferentially displayed, or the property corresponding to the role that the user uses the most may be preferentially displayed, and the like.

In some embodiments, before sending the item information to the service server in step S25, it may also be determined whether the privilege scenario and the item information corresponding to the privilege scenario are valid by:

step S211, obtaining the activity information of the privileged scene.

In the embodiment of the present application, the activity information is information capable of reflecting the activity of the target service user in the privilege scenario, and may include, for example, the number of daily active users, the online time of the user, and the like.

Step S212, based on the activity information, when the privilege scene is determined to meet the preset effective condition, acquiring the failure time of the prop information.

Here, it can be determined whether the liveness of the target service user satisfies the condition of property authorization in the privilege scenario based on the liveness information of the privilege scenario, thereby determining whether the privilege scenario satisfies the effective condition; when the privilege scene is determined to meet the preset effective condition based on the activity information, further acquiring the failure time of the prop information; in some embodiments, when it is determined that the privilege scenario does not meet the preset effective condition based on the activity information of the privilege scenario, a response message that item qualification is not satisfied is returned to the service server.

Step S213, determining whether the prop information is overdue according to the current time and the expiration time.

Here, when the step S213 is implemented, it is determined whether the property information is expired, that is, it is determined whether the current time is before the expiration time, and if the current time is before the expiration time, it indicates that the property information is not expired, then step S25 is performed, and the property information is sent to the service server; if the current time is after the expiration time, which indicates that the item information is expired, a response message that the item is expired is returned to the service server.

For example, if the expiration time is 31/10/2019 and the current time is 23/10/2019, since the current time is before the expiration time, which indicates that the property information is not expired, the process proceeds to step S25; if the expiration time is 31/10/2019 and the current time is 3/11/2019, the item information is expired because the current time is after the expiration time, and a response message indicating that the item is expired is returned to the service server.

In some embodiments, before the item is disabled, the buyer of the item, that is, the requester in the above embodiments, may be reminded to renew the fee to ensure that the player can use the item normally:

and step S31, determining the remaining use duration corresponding to the prop information according to the expiration time and the current time.

Here, when the step S31 is implemented, the remaining usage time corresponding to the item information is determined by the difference between the expiration time and the current time. For example, if the expiration time is 31 days in 2019 and 10 months, and the current time is 23 days in 2019 and 10 months, the remaining usage time is 8 days.

Step S32, determining whether the remaining usage duration is less than a duration threshold.

Here, when the remaining used time length is less than the time length threshold value, it is described that the expiration time is approaching, at this time, step S33 is entered, and when the remaining used time length is not less than the time length threshold value, it is described that there is a longer time from the expiration time, at this time, the reminding operation is not performed.

Assuming that the time length threshold is 3 days, since the current remaining use time length is still 8 days, and the remaining use time length is greater than the time length threshold, the reminding operation is not executed, and when 29 days in 10 and 29 months in 2019, the remaining use time length is 2 days and is less than the time length threshold for 3 days, the process goes to step S33 to remind the requester to pay a fee.

In some embodiments, steps S31 and S32 may be performed periodically, for example, every 24 hours.

And step S33, when the remaining service life is less than the time threshold, sending a payment reminding message to a requester corresponding to the prop information.

Here, the payment reminding message carries the remaining usage duration and the payment amount.

Step S34, determine whether the payment success message is received before the expiration time.

Here, if the payment success message is received before the expiration time, the step S36 is entered to update the expiration time of the property information; if the payment success message is not received before the expiration time, step S35 is entered to revoke the usage right of the requester.

Step S35, the property management server deletes the correspondence between the property information and the requester, so as to revoke the property usage right of the requester.

Here, if the successful payment message of the requester is not received after the expiration time, it indicates that the requester does not renew the payment, and at this time, the usage right of the prop by the requester needs to be revoked, and in the actual application process, the usage right can be realized by deleting the corresponding relationship between the prop information and the requester.

And step S36, the prop management server updates the expiration time of the prop information.

If the payment success message of the requester is received before the expiration time is reached, the requester is shown to be charged again, at the moment, the use permission of the requester on the prop is kept, and the expiration time of the prop information is updated according to the payment success message.

In this embodiment, when sending the payment reminding message to the requesting party, the property management server may provide payment options, where different payment options correspond to different payment amounts and duration, for example, 40 yuan corresponds to a duration of 3 months, 100 yuan corresponds to a duration of 6 months, and 180 yuan corresponds to a duration of 12 months. The requester corresponding to the property information may select a payment option, for example, may select 100 yuan, and then when the road property management server receives a payment success message of paying 100 yuan, the expiration time is extended by 6 months, assuming that the original expiration time is 10 and 31 days in 2019, and after the expiration time is extended by 6 months, the updated expiration time is 4 and 30 days in 2020.

In some embodiments, the property management server may further obtain property activation frequency information and network routing information of each terminal in the privileged scene periodically or aperiodically through the following steps S41 to S43, to determine whether the terminal in the privileged scene meets a preset security policy, and to timely remove or recover property usage rights of the terminal with the security risk.

And step 41, acquiring prop activation frequency information and network routing information of each terminal in the privilege scene.

Here, the terminal prop activation frequency information, that is, the frequency of the terminal requesting to use the prop may be, for example, 10 times of activation in 3 days, and in some embodiments, the terminal prop activation frequency information further includes how many users are activated in a unit time on the same terminal, the number of simultaneous online users, and the like. The network routing information of the terminal can be information such as network routing hop count, time delay, whether the terminal and the scene management terminal are located in the same local area network, and the like.

And 42, determining a target terminal based on the item activation frequency information and the network routing information of each terminal.

Here, the target terminal is a terminal whose property activation frequency information and network routing information do not conform to the security policy, that is, the target terminal is a terminal with potential safety hazard.

And 43, when detecting that the terminal logged in the service server is the target terminal, returning a response message without available props to the service server.

Here, since the target terminal is a terminal with potential safety hazard, when it is detected that the target terminal is used for logging in the service server, the property management server returns a response message without available properties to the service server, and prompts the replaceable terminal to log in to obtain the properties, so that the condition that a user outside a scene illegally possesses privileged property rights through a malicious terminal and damages a requester and service benefits is avoided.

Based on the foregoing embodiments, an embodiment of the present application further provides a property management method, which is applied to the network architecture shown in fig. 1, fig. 5 is a schematic view of another implementation flow of the property management method according to the embodiment of the present application, and as shown in fig. 5, the method includes:

step S501, the requester applies for becoming a privileged scene and sends a privileged scene registration request to the prop management server.

Here, step S501 is implemented when the requester terminal actually sends a privileged scene registration request to the property management server. The terminal of the requesting party, that is, the terminal used by the requesting party, may be a portable terminal such as a mobile phone and a tablet computer, or may be a terminal inconvenient to move such as a desktop computer and a desktop computer.

The privilege scenario registration request sent by the requester may carry attribute information of the requester, and in some embodiments, the requester may only send the privilege scenario registration request, and then the item management server returns an information prompt required for registration to the requester, so that the requester supplements complete information according to the prompt.

Step S502, the property management server obtains attribute information of the requester based on the received registration request.

Here, the attribute information of the requester may include applicant information (including, for example, name and identification number of the applicant), geographic location and scale of the requester, an industry attribute, license information, whether there is a central node, and the like.

In step S503, the item management server determines whether the requester satisfies the privileged scene registration condition based on the attribute information of the requester.

Here, the privilege scenario registration condition may be preset, and in the privilege scenario registration condition, the geographic location may be limited not to be too far away and the scale may not be too small, and the industry attribute may be limited, for example, the industry attribute may not be the medical industry, the education industry, and the like. When it is determined that the requester satisfies the privilege scenario registration condition based on the attribute information, the process proceeds to step S504; when it is determined that the requester does not satisfy the privileged scene registration condition, the flow proceeds to step S507, and the flow ends.

Step S504, when the attribute information is determined to meet the registration condition of the privilege scene, the property management server acquires the user data of the requester.

Here, in the embodiment of the present application, the user data of the requesting party may be a user located in a geographic location of the requesting party, and further refers to a user using a terminal to establish a communication connection with a central node of the requesting party. When the requesting party is an internet bar B and the central node of the requesting party is a network management server, the user at the geographical position of the requesting party refers to a user surfing the internet in the internet bar by using a terminal which is in communication connection with the network management server; when the central node of the requester is a wireless router, the user at the geographical position of the requester refers to a user corresponding to a terminal connected to the wireless router. The user data may include portrait data of the user and may also include historical behavior data of the user.

Step S505, the property management server determines preference information of the user based on the user data, and determines candidate property information of the requester based on the preference information.

Here, the user data is analyzed to determine the preference information of the user in the geographic location of the requesting party, wherein the preference information of the user at least includes characters, skills and the like used by the user in the game process. After determining the preference information of the user, the prop management server may determine candidate prop information corresponding to the preference information according to a scene feature information base stored by the prop management server.

Step S506, the property management server sends a response message that the registration is successful to the requester.

Here, the response message carries the candidate item information.

Step S507, the property management server sends a response message of registration failure to the requester.

Here, the response message may also carry a reason of registration failure, for example, the industry attribute of the requesting party does not satisfy the registration condition.

Step S508, after receiving the response message of successful registration, the requester determines the target item information based on the candidate item information.

Here, after receiving the response message of successful registration, the requester terminal displays the candidate item information on the requester terminal and prompts the requester to select the target item information. At this time, the requester may select a part of the candidate item information as the target item information, and certainly, the requester may use all the candidate item information as the target item information.

In step S509, the requester sends the target item information to the item management server.

Step S510, after receiving the target property information sent by the requester, the property management server performs qualification verification on the requester based on the attribute information of the requester and the target property information, and obtains a verification result.

Here, since the candidate item information is determined according to the preference information of the user, after the requester selects the target item information, the item management server is further required to perform qualification audit on the requester according to the attribute information of the requester to determine whether the requester meets the use condition of the target item information. When the requester is determined to meet the use condition of the target prop information according to the attribute information of the requester, an auditing result of the auditing is obtained; when the requester is determined not to meet the use condition of the target prop information according to the attribute information of the requester, an auditing result of the auditing failure is obtained, and the result shows that the requester does not have the use qualification of the target prop information, so that the prop management server returns a notification message that the selection of the target prop information is invalid to the requester.

Step S511, the property management server determines whether the audit result is that the audit is passed.

Here, when the result of the audit is that the audit is passed, indicating that the requester has a qualification for using the target item information, the process proceeds to step S512; and when the auditing result is that the auditing is not passed, the requester is indicated not to have the using qualification of the target property information, and at the moment, the property management server returns prompt information for reselecting the target property information to the service server.

Step S512, when the auditing result shows that the requester has the using qualification of the target item information, the item management server sends payment information to the requester.

Here, the payment information is determined based on the usage time of the selected target item and the corresponding purchase price.

In some embodiments, it may also be that in step S505, the candidate item information of the requesting party is determined not only based on the preference information of the user, but also based on the attribute information of the requesting party, so that in step S506, all the item information carried in the registration success message sent by the item management server to the requesting party is candidate item information with qualification, and after step S509, step S510 and step S511 may be omitted, and step S512 may be directly executed.

In step S513, the requester makes an online payment based on the received payment information.

Step S514, when the property management server receives the notification message that the payment is successful, establishing a corresponding relationship between the requester and the target property information.

Here, after the requester completes the online payment process, the third party payment server (not shown in fig. 1) sends a notification message that the payment is successful to the item management server, and when the item management server receives the notification message that the payment is successful, the item management server establishes a corresponding relationship between the requester and the target item information to complete the process of configuring the target item for the requester.

Step S515, the user logs in the target service through the terminal.

Here, when step S515 is implemented, the user logs in the target service using the target service client in the terminal, and at this time, the target service client performs information interaction with the service server to complete the login.

Step S516, the service server sends a property query request to the property management server.

Here, the item query request at least includes a terminal identifier, and in some embodiments, the item query request may also carry feature information of the terminal.

And step S517, the property management server acquires the characteristic information of the terminal logged in the service server based on the property query request.

Here, when the step S517 is implemented, the feature information of the terminal may be obtained by analyzing the property query request, or the feature information of the terminal may be obtained from the scene gateway according to the terminal identifier, which is not limited in this embodiment.

Step S518, the property management server determines the privilege scenario in which the terminal is located based on the feature information, and obtains property information corresponding to the privilege scenario.

Here, the property management server determines the privilege scenario in which the terminal is located according to the characteristic information of the terminal, and further determines corresponding property information according to the privilege scenario. In some embodiments, when the item management server determines that the terminal is not in the privileged scene based on the feature information, then the item management server returns a response message that no free items can be used to the service server.

Step S519, the property management server sends the property information to the service server.

Here, after receiving the property information sent by the property management server, the service server may send the property information to the terminal, so as to display the property information to the user.

In some embodiments, before the property management server sends the property information to the service server, the property management server may further audit validity of a privilege scene, whether the property information is expired, and the like, and send the property information to the service server when the privilege scene is valid and the property information is not expired, where the process of auditing validity of the privilege scene and validity of the property information may refer to the implementation processes from step S211 to step S213.

Step S520, the service server obtains the history data of the user logging in the terminal.

Here, in order to more specifically display different item information to different users, the service server determines a display mode of the item information based on historical data of the user before transmitting the item information to the terminal.

And step S521, the service server determines the display mode of the property information according to the historical data.

Here, the historical data may include the existing items of the user, the level of the user, the role that the user uses more, and the like, and then, in the implementation of step S521, the items that the user does not have may be preferentially displayed, or the items corresponding to the role that the user uses the most may be preferentially displayed, and the like.

Step S522, the service server sends the item information to the terminal according to the display mode.

Here, after receiving the item information, the terminal displays the item information on its display device according to the display mode, and the terminal uses the selected item based on the selection operation of the user.

In addition, in the embodiment of the application, when the user logs in the target service, the property management server determines the privilege scene where the terminal is located according to the characteristic information of the terminal, and further determines the property information corresponding to the privilege scene, and when the service server sends the property information to the terminal, the service server also performs optimal matching on the display mode of the property information according to the historical data of the user, so that the property information is displayed for the user in a targeted manner, the user can conveniently select a proper property, and the use experience of the user is improved.

Next, an exemplary application of the embodiment of the present application in a practical application scenario will be described.

In the embodiment of the application, the privilege prop based on the scene provides a new prop management method besides the traditional prop operation: by portraying the user of a specific physical scene, the scene exclusive prop conforming to the taste of the user is provided according to the background information and the interest of the user. Fig. 6 is a schematic structural diagram of a privileged item management system in an embodiment of the present application, and as shown in fig. 6, the management system includes: a terminal machine 601, a scenario gateway 602, a scenario management terminal 603, a privileged server 604 and a service server 605, wherein:

the terminal machine 601 includes a business client 6011 and a scene client 6012, and a user logs in the business client 6011 to experience a service, such as a hero alliance; the scene client 6012 collects the scene feature information to provide a data basis for determining whether the terminal machine is located in a privileged scene, and the scene client 6012 and the scene gateway 602 keep a timing heartbeat and receive control thereof. The scene client 6012 may be implemented differently according to the type of the terminal machine, for example, when the terminal machine is a Personal Computer (PC), the scene client 6012 may be an application program independent from the service client 6011, and when the terminal machine is a mobile phone or a tablet Computer, the scene client 6012 may be a Software Development Kit (SDK) integrated with the service client 6011.

The scenario gateway 602: typically deployed on a central server (e.g., a network management server of a physical internet cafe) or a key node machine of the physical scene. The scene gateway 602 uses multiple security policies to monitor the behavior of each terminal machine, including the terminal device active frequency, the network routing hop count, the proxy, the VPN, and the like on the same local area network IP address.

The scene manager 603: and receiving data report of the scene gateway 602, monitoring the activity of the scene gateway 602 in the whole network, and eliminating scene gateway nodes with abnormal behaviors according to a preset security policy.

For example, when one scenario gateway node is occupied by two different privileged scenarios, the scenario gateway node is considered to have an exception, and the implementation manner when the scenario gateway node with the exception behavior is removed includes:

firstly, the scene gateway node is allocated to a privileged scene occupied first;

secondly, the scene gateway node is allocated to the occupied privilege scene;

and thirdly, directly eliminating the scene gateway node, namely not allocating the scene gateway node to the occupied privileged scene and not allocating the scene gateway node to the occupied privileged scene.

The privileged server 604: the system is a final judgment center of the privileged prop, judges the physical scene where the user is based on a complete scene characteristic information base, feeds back the privileged prop applicable to the scene to the service server 605, and cancels and recovers the disabled privileged prop.

In addition, the privileged server 604 may also iteratively update the scene feature information base in an offline manner, and further, when the privileged server 604 determines that an abnormal condition occurs, the privileged server 604 may iteratively update the scene feature information base in an offline manner.

The service end 605: through interaction with a user through the service client 6011, user login and operation events are processed, and privileged props are activated according to a physical scene where the events are located.

In some embodiments, the scenario manager 603 and the privileged server 604 may be deployed in the same server entity, but in general, the scenario manager 603 and the privileged server 604 are respectively deployed in different server entities for the reason of service isolation.

The implementation of the privilege item management method based on the scene comprises 2 stages: the method comprises an access stage of the physical scene privilege prop and a user privilege prop experience stage. These two different phases are described below in connection with fig. 7 and 8, respectively.

Fig. 7 is a schematic diagram of an implementation process of an access phase of a physical scene privileged item in the embodiment of the present application, and as shown in fig. 7, the process includes:

step S701, the physical scene dealer registers and applies for a privileged scene with the scene manager.

When the physical scene merchant applies for registration, the information required to be provided comprises the information of the applicant, the geographic position and scale of the merchant, the industry attribute, whether a central node exists or not and the like.

Step S702, the scene management end conducts privilege scene audit on the physical scene merchant and judges whether the audit is passed.

After the physical scene merchants are approved, the scene gateway is deployed in the central node, and the terminal machine in the same network topology as the central node deploys the scene client. Step S703 is performed after the environment deployment is completed; and when the audit on the physical scene businessman is not passed, ending the process.

Step S703, the access party applies for the scene privileged prop from the scene management platform (scene management end).

Step S704, the scene management end performs qualification audit on the package selected by the access party.

Here, when the qualification of the selected package is passed, step S705 is performed, payment information is sent to the physical scene merchant, and the service-restricted package is activated after the payment is successful; and ending the process when the qualification examination of the selected package is not passed.

Step S705, the scene management end sends payment information to the physical scene merchant, and activates the service definition package after successful payment.

Here, the physical scene merchant performs online payment after receiving the payment information, and after the payment is successful, the scene management terminal receives a payment success message, and at this time, the scene management terminal activates a service restriction package of the physical scene merchant. After the service definition package is activated, the privileged items in the package are also configured to take effect.

Step S706, the scene management end issues/updates the service package and synchronizes information to the privilege service end.

Here, after the service definition package is activated, the scenario management end may issue or update the service definition package, so that when the user logs in the property mall using the service client in the privilege scenario, the user may experience the privileged property named by the physical scenario merchant.

In step S707, the scene management end performs package qualification check on the issued service package to determine whether the service package is due.

Here, when it is determined that the service package is not expired, the process proceeds to step S708, where a response is made to the privilege request of the mall, and when it is determined that the service package is expired, the process proceeds to step S709, where it is determined whether or not a renewal is made.

Step S708, the privileged server responds to the privileged request when the target service user logs in.

Step S709, the scene manager determines whether to renew the current package.

Here, before the privileged prop is disabled, the physical scene merchant is notified to renew the charge, if the charging operation is not completed, the step S710 is entered to immediately recover the privileged prop in the property merchant city; when the renewal is completed, the business package is continuously issued in the property store, and the package expiration time and the like are synchronized to the privileged server.

Step S710, the service limit package is recovered.

Fig. 8 is a schematic diagram of an implementation process of a user privileged item experience phase in the embodiment of the present application, and as shown in fig. 8, the process includes:

step S801, the user logs in the target service.

Here, the user logs in the target service through the service client on the terminal machine.

Step S802, the privilege server judges whether the terminal machine used by the user to log in the target service is in a privilege scene.

In the process that a user logs in a target service by using a terminal machine, a scene client extracts characteristic information of the terminal machine in real time and reports the characteristic information to a privilege server in two ways, wherein one way is directly through an external network; the other method is that the feature information is reported to a scene gateway through an internal local area network, then the scene gateway forwards the feature information to a scene server and finally reports the feature information to a privilege server, whether a user (namely a terminal machine) is located in a privilege scene is judged through the feature information, when the terminal machine is determined to be in the privilege scene, the privilege server returns a privilege prop to a service server, and then the step S803 is entered; when not in a privileged scenario, the flow ends.

Step S803, the privilege server extracts the exclusive package customized by the privilege scenario.

Here, the privileged server returns the exclusive package to the service server after extracting the exclusive package customized for the privileged scene.

Step S804, the service server determines whether to display the dedicated property.

Here, if the exclusive property needs to be displayed, the process goes to step S805; and if the exclusive prop does not need to be displayed, ending the process.

Step S805, the prop mall activates and displays the exclusive prop.

Here, when the prop mall activates and displays the special prop, the display strategy of the special prop can be determined according to the prop information owned by the user and the interest and hobbies of the user, for example, the prop not owned by the user can be preferentially displayed, and the prop close to the use habit of the user can be preferentially displayed.

Step S806, the user selects the exclusive property and uses it free of charge.

Here, when the terminal machine used by the user is in a privileged scene, the exclusive property can be used for free without purchase.

Step S807, the privileged server checks whether the property is still valid.

Here, if the prop is expired, go to step S808; if the prop is still valid, the process proceeds to step S809.

Step S808, the privileged server retrieves/shields the dedicated property.

Here, the privilege server receives/shields the special prop, and may be that the special prop is not displayed in the prop store, or that the special prop is displayed in the prop store, but when the user clicks "use free", the prop is prompted to be disabled.

After the privileged server withdraws/shields the exclusive prop, the privileged server can prompt the physical scene businessman to renew the charge.

And step S809, the user experiences the exclusive prop.

Here, if the exclusive prop is still valid, the user can experience the exclusive prop after clicking for free.

The privilege prop implementation system based on the scene enables the experience flow of a user to be very simple and clear, and almost no additional operation is needed: the user starts a service client on a terminal machine, enters a prop mall to find a privileged prop named by a physical scene merchant, and can be activated by clicking 'free use', and the user can also choose to ignore the privileged prop.

In the user login process, the prop management system executes the following operations to ensure the stability, smoothness and safety of the scene privilege experience. Firstly, a scene management end can extract characteristic information of a terminal machine in real time, judge whether a user is in a privileged scene or not through the characteristic information and associate the characteristic information with a specific scene entity to determine whether the scene entity is effective or not; then, the privilege service end checks the privilege prop configuration of the scene entity, selects the optimal matching to return and displays the optimal matching in a prop mall; and finally, the service server triggers the privilege server to periodically confirm whether the privilege prop still takes effect, withdraws the privilege prop if the package fails, and recovers the game rights and interests.

In the privilege experience process, the scene client monitors and detects whether the terminal machine has abnormal behaviors, if so, the scene client acquires terminal characteristic information including privilege activation frequency and network related information irregularly, and reports the detection result to the scene manager, and the scene manager integrates multi-dimensional information to complete the adjustment of the security policy.

According to the prop management method provided by the embodiment of the application, the online operation and the offline activity of the service are organically combined, the customizable fine operation is realized aiming at different scenes, and the efficiency is improved. And the perception capability and participation enthusiasm of the physical scene are improved in a mode of authorizing the privilege scene to the prop crown, more people can be gathered, and the business activity is further improved.

Continuing with the exemplary structure of the prop management apparatus 80 provided in the embodiments of the present application as software modules, in some embodiments, as shown in fig. 2, the software modules stored in the prop management apparatus 80 of the memory 240 may include:

a first obtaining module 81, configured to obtain attribute information of a requester based on a received registration request for applying to become a privileged scene;

a second obtaining module 82, configured to obtain, when it is determined that the attribute information satisfies the privilege context registration condition, user data corresponding to the requestor;

a first determining module 83, configured to determine preference information of the user based on the user data, and determine candidate prop information of the requester based on the preference information;

a first sending module 84, configured to send a response message that registration is successful to the requester, where the response message carries the candidate item information.