Service duration management method and device of shared equipment, equipment and storage medium

Abstract

The invention discloses a service duration management method and device of shared equipment, equipment and a storage medium, and relates to the technical field of shared equipment operation management, and the method comprises the steps: collecting multi-dimensional data in an interaction process between a user and the shared equipment; performing behavior validity verification on the multi-dimensional data, and screening out effective interaction behavior data meeting a preset management requirement; based on the effective interaction behavior data, determining the service reward duration of the shared device by adopting a dynamic calculation mode; and configuring a service duration resource corresponding to the service reward duration for a shared device service account corresponding to the user. According to the method and the device, personalized management of the service duration of the shared equipment can be realized, and diversified and high-precision management requirements of user interaction scenes are met.

Description

Technical Field

[0001] This application relates to the field of shared equipment operation and management technology, and in particular to a method, apparatus, device and storage medium for managing the service time of shared equipment. Background Technology

[0002] With the deep integration of mobile internet technology and Internet of Things (IoT) technology, shared devices (such as shared power banks and shared charging cabinets) have become a key service carrier for solving the battery life needs of mobile terminals and have been widely deployed in high-frequency usage scenarios such as commercial areas, transportation hubs, and entertainment venues. Service duration management of shared devices is a core technical aspect supporting their stable operation. This aspect requires the use of technical means to achieve the coordination of functions such as user behavior data collection, service duration calculation, and duration account maintenance, to ensure that service resources (i.e., the usage time of shared devices) can effectively align with actual user needs.

[0003] Currently, the management of service duration for shared devices largely relies on basic user operation records and static rule execution. However, with the diversification of user interaction scenarios, the existing technology's support capabilities are no longer sufficient to meet the needs of high-precision management. Summary of the Invention

[0004] In view of this, this application provides a method, apparatus, device and storage medium for managing the service duration of shared devices, which can realize personalized management of the service duration of shared devices and meet the diversified and high-precision management requirements of user interaction scenarios.

[0005] According to a first aspect of this application, a method for managing the service duration of a shared device is provided, comprising: Collect multi-dimensional data during the interaction between users and shared devices; The multi-dimensional data is subjected to behavior validity verification, and valid interactive behavior data that meets the preset management requirements is selected. Based on the effective interaction behavior data, the service reward duration of the shared device is determined using a dynamic calculation method; Configure the service duration resources corresponding to the service reward duration for the shared device service account corresponding to the user.

[0006] According to a second aspect of this application, a service duration management device for shared devices is provided, comprising: The data acquisition module is used to collect multi-dimensional data during the interaction between users and shared devices; The filtering module is used to verify the validity of the multi-dimensional data and filter out valid interactive behavior data that meets the preset management requirements. The determination module is used to determine the service reward duration of the shared device based on the effective interaction behavior data using a dynamic calculation method; The configuration module is used to configure the service duration resources corresponding to the service reward duration for the shared device service account corresponding to the user.

[0007] According to a third aspect of this application, a storage medium is provided that stores a computer program thereon, which, when executed by a processor, implements the above-described method for managing the service duration of a shared device.

[0008] According to a fourth aspect of this application, an electronic device is provided, including a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, wherein the processor executes the program to implement the above-described method for managing the service duration of a shared device.

[0009] By utilizing the above technical solutions, this application provides a method, apparatus, device, and storage medium for managing the service duration of shared devices. By collecting multi-dimensional data during user interaction with the shared devices, it overcomes the limitations of traditional shared device service duration management that relies solely on basic user operation records. This provides comprehensive data source support covering user interaction details and device status for subsequent behavior verification and duration calculation, solving the problem of insufficient basic data required for high-precision management. By validating the behavior of multi-dimensional data, it can accurately identify and eliminate abnormal or cheating behaviors such as robot simulation and background suspension, filtering out valid interaction behavior data that meets preset management requirements. This ensures the authenticity and reliability of the basis for subsequent service reward duration calculation, preventing the abuse of service resources due to invalid data and guaranteeing the reliability of duration management. Based on valid interaction... Interactive data uses a dynamic calculation method to determine service reward duration, abandoning the rigidity of traditional static rules. It can flexibly adapt to the diversified characteristics of user interaction scenarios, enabling the service reward duration to accurately match the actual value of user interaction, significantly improving the accuracy of service reward duration calculation, and meeting the needs of high-precision management for duration adaptability. By configuring service duration resources corresponding to the service reward duration for the user's shared device service account, it can achieve full-process collaborative connection of user behavior data collection, validity verification, dynamic calculation, and account management, ensuring that the service resources of shared devices can be efficiently connected with the actual needs of users. This solves the technical problem that existing technologies cannot meet the high-precision management of shared device service duration under diversified user interaction scenarios, and improves the overall collaboration, accuracy, and reliability of shared device service duration management.

[0010] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description

[0011] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings: Figure 1 A flowchart illustrating a method for managing the service duration of a shared device according to an embodiment of this application is shown. Figure 2 A flowchart illustrating a method for managing the service duration of a shared device according to another embodiment of this application is shown; Figure 3 A flowchart illustrating a method for managing the service time of a shared device according to another embodiment of this application is shown; Figure 4 This illustration shows a structural schematic diagram of a shared device service duration management apparatus provided in an embodiment of this application; Figure 5 A schematic diagram of the structure of another shared device service duration management device provided in an embodiment of this application is shown. Detailed Implementation

[0012] The present application will be described in detail below with reference to the accompanying drawings and embodiments. It should be noted that, unless otherwise specified, the embodiments and features described in the embodiments of the present application can be combined with each other.

[0013] With the deep integration of mobile internet technology and Internet of Things (IoT) technology, shared devices (such as shared power banks and shared charging cabinets) have become a key service carrier for solving the battery life needs of mobile terminals and have been widely deployed in high-frequency usage scenarios such as commercial areas, transportation hubs, and entertainment venues. Service duration management of shared devices is a core technical aspect supporting their stable operation. This aspect requires the use of technical means to achieve the coordination of functions such as user behavior data collection, service duration calculation, and duration account maintenance, to ensure that service resources (i.e., the usage time of shared devices) can effectively align with actual user needs.

[0014] Currently, the management of service duration for shared devices largely relies on basic user operation records and static rule execution. However, with the diversification of user interaction scenarios, the existing technology's support capabilities are no longer sufficient to meet the needs of high-precision management.

[0015] To address the aforementioned problems, embodiments of the present invention provide a method for managing the service duration of shared devices, such as... Figure 1 As shown, the method includes: Step 110: Collect multi-dimensional data during the interaction between the user and the shared device.

[0016] In this embodiment of the disclosure, a data collection module deployed on the shared device can collect multi-dimensional information related to the interaction in real time at a preset sampling frequency during the user's use of the shared device (such as a shared power bank). This information not only covers the effective interaction duration of the user's interaction with the device content (such as advertising content), specific interactive operations (such as clicking an advertising button, swiping to view details, etc.), and the time the page focus stays on the interactive content, but also includes the operating status data of the shared device itself (such as the device's current battery level, network connection stability, hardware load, etc.). At the same time, the collected real-time data will undergo preprocessing such as data deduplication, noise filtering, and data format standardization to remove duplicate records, eliminate invalid interference data, and unify the data format, ensuring the integrity, accuracy, and standardization of the collected data, and providing reliable data support for subsequent behavior verification, duration calculation, and other stages.

[0017] By collecting multi-dimensional data during user interaction with shared devices, comprehensive and standardized basic data can be provided for subsequent verification of the validity of user interaction behavior. This effectively avoids verification bias caused by single data dimensions or poor data quality. At the same time, it can rely on device operation status data to help identify cheating behaviors such as robot simulation operation and device background suspension, ensuring the accuracy and fairness of subsequent calculation of shared device service duration based on valid data, and further improving the accuracy of shared device service management.

[0018] Accordingly, for the embodiments of this disclosure, step 110 may include the following steps: Step 110-1: Determine the scope of multi-dimensional data collection. The scope of collection should at least cover the effective interaction duration, interaction behavior, page focus dwell time, and device operating status data during the interaction between the user and the shared device.

[0019] Among them, shared devices are shared service carriers that are widely deployed in high-frequency usage scenarios such as commercial areas, transportation hubs, and entertainment venues, with the core goal of solving users' immediate and scenario-based needs. They may include shared power banks, shared charging piles, and shared charging seats. In the following embodiment steps of this application, shared power banks are used as an example to illustrate the technical solutions in this application, but this does not constitute a specific limitation. The target interactive content refers to the specific interactive carrier that users need to participate in in order to obtain shared device services (such as free charging time). In the shared power bank scenario, it is usually advertising content (such as brand promotion videos and event promotion pages).

[0020] In this embodiment of the disclosure, determining the scope of multi-dimensional data collection is primarily about clarifying the boundaries of key information to be collected during user interaction with shared devices such as shared power banks. This includes at least core interaction data related to the target interactive content (such as advertising content that users need to watch to obtain charging time) and the operating status data of the shared device itself. Specifically, the effective interaction time for the target interactive content refers to the effective time during which the user is actually focused on the interaction (such as watching an advertisement in its entirety or continuously operating the interactive interface), excluding invalid periods such as background suspension or screen switching; interactive operation behavior refers to the specific actions performed by the user during the interaction (such as clicking a button within an advertisement, swiping to view advertisement details, or confirming the completion of the interaction); page focus dwell time refers to the duration for which the page containing the target interactive content remains in the foreground on the user's terminal or device screen and the user's focus does not leave; device operating status data includes information reflecting whether the device is operating normally, such as the shared device's real-time battery level, network connection stability, and hardware operating load (such as the working status of the charging module). Setting these collection scopes ensures the comprehensive capture of the authenticity and completeness of user interactions, while also understanding the basic operating status of the device, providing data support for subsequent stages.

[0021] One possible implementation scenario is that the target interactive content can be fixed interactive content configured for the shared device. This approach can reduce the workload of service duration management and improve its efficiency. Another possible implementation scenario is to provide multiple interactive content options, allowing users to choose the final target interactive content from among them. This approach can satisfy users' personalized choices and better meet their core needs.

[0022] Accordingly, when selecting target interactive content from multiple interactive options, it is necessary to first integrate the user's basic information (such as age, common usage scenarios, and terminal device type), historical interaction data (such as the types of interactive content viewed in the past, completion rate, and dwell time), account credit rating (such as whether there are compliant interaction records and no cheating behavior), and preference characteristics (such as a preference for short video or text-based interactive formats and the industry sectors they follow) to construct a user profile that accurately reflects the user's attributes and needs. Then, combined with the content provider's requirement parameters (such as target audience, promotion scenarios, and interactive content type preferences), the suitability between the user profile and each interactive content is calculated using content matching algorithms (such as collaborative filtering and tag matching). Multiple suitable interactive contents are then selected and sorted by suitability, generating and displaying a personalized content recommendation list to the user, which includes a brief description of the interactive content and an estimated service duration. Finally, the user can choose content that meets their needs from this recommendation list. The selected content becomes the target interactive content for subsequent interactions with shared devices, ensuring that the target interactive content not only matches the user's preferences but also meets the content provider's promotional needs.

[0023] Accordingly, the implementation steps may include: constructing a user profile based on the user's basic information, historical interaction data, account credit rating, and preference characteristics; matching multiple suitable interactive contents through a content matching algorithm according to the user profile and the content provider's requirements parameters, generating and displaying a personalized content recommendation list; and receiving the target interactive content selected by the user from the personalized content recommendation list.

[0024] By building accurate user profiles based on multi-dimensional user data, combining content provider requirements with content matching algorithms to generate personalized recommendation lists, and then allowing users to choose target interactive content, this technical solution ensures that the target interactive content aligns with both user preferences and content provider needs.

[0025] Step 110-2: Start the acquisition module deployed on the shared device and collect multi-dimensional data within the acquisition range in real time according to the preset sampling frequency.

[0026] The acquisition module refers to the functional components (such as the front-end SDK and sensor data capture unit) that are pre-integrated or installed inside the shared device. Its core function is to capture and collect various types of data during the interaction between the user and the device. It is a hardware and software combination carrier for realizing multi-dimensional data acquisition. The preset sampling frequency refers to the time interval for the acquisition module to collect data (such as once per second or once every 500 milliseconds) that the platform sets in advance according to the data accuracy requirements and device performance. This ensures that the data acquisition will not result in information loss due to too low a frequency, nor will it increase the operating load of the device due to too high a frequency.

[0027] In the operation scenario of shared devices, when a user starts to interact with the shared device (such as triggering an advertisement to obtain charging time), the system will start the collection module pre-deployed inside the shared device. This module will collect multi-dimensional information within the previously defined collection range continuously and without delay according to the fixed time interval (i.e., the preset sampling frequency) set in advance by the platform.

[0028] By activating the acquisition module deployed on the shared device and collecting multi-dimensional data within a specified range in real time at a preset sampling frequency, it is possible to ensure that the acquired raw data is continuous, timely, and complete. This avoids the loss of user interaction details and untimely recording of device status due to acquisition delays or low frequencies, and also prevents data interruptions from affecting the accuracy of subsequent behavior validity verification.

[0029] Step 110-3: Preprocess the multi-dimensional data collected in real time. Preprocessing includes at least data deduplication, noise filtering, and data format standardization.

[0030] During the interaction between shared power banks and users, the system collects multi-dimensional raw data in real time, covering user interaction behavior and device operating status. The data quality needs to be optimized through a specific processing flow, which is called data preprocessing. Data deduplication involves identifying and deleting duplicate records caused by temporary malfunctions in the acquisition module or overlapping sampling frequencies, such as the repeated collection of data like "device remaining battery 65%" at the same time point. Noise data filtering removes invalid information caused by external interference such as network fluctuations or temporary sensor anomalies, such as outliers like "ad viewing time -2 seconds" or "device temperature 100℃" due to signal interruption. Data format standardization unifies data of different formats into the platform's preset standardized format. For example, different timestamp formats such as "2024.11.05" and "2024 / 11 / 05" are unified into "2024-11-05 10:15:30", and duration units such as "1.5 minutes" and "90 seconds" are unified into "seconds". Through these three types of processing, scattered and flawed raw data can be transformed into complete, accurate, and directly callable standardized data.

[0031] Step 110-4: Store the preprocessed multi-dimensional data in a distributed database or blockchain, and add a unique timestamp and user identifier to each piece of data.

[0032] In the operation of shared power banks, after the system preprocesses the multi-dimensional data generated by user and device interactions, it stores this clean and standardized data in two highly reliable storage media: distributed databases or blockchain. At the same time, to ensure that the ownership of each piece of data is clear and the time sequence is traceable, a unique timestamp and user identifier (such as user account ID or unique identification code bound to the device) are attached to each piece of stored data. This allows for quick location of the user and the time of generation when querying and verifying data, providing traceable and verifiable basic data support for interaction behavior verification, service duration calculation, and other processes.

[0033] Step 120: Verify the validity of the multi-dimensional data and select valid interactive behavior data that meets the preset management requirements.

[0034] Among them, effective interactive behavior data refers to multi-dimensional data that meets the preset management requirements after the behavior validity has been verified. It can accurately reflect the process of users' real participation in shared power bank interactions (such as watching advertisements in their entirety and actively operating content). It is the key data for subsequent calculation of service reward duration and statistics of advertising effectiveness.

[0035] The validity of multi-dimensional data is verified through specific technical logic to check whether the data reflects genuine user interaction behavior and meets the service time redemption requirements of the interactive device. For example, it is determined whether the viewing time reaches the preset standard, whether the operation is initiated by the user, and whether the device status excludes cheating scenarios such as background suspension. The preset management requirements are the effective interaction judgment standards set in advance by the platform (such as the ad viewing time is not less than 80% of the total content time, there is at least one active operation, and the device has no abnormal background behavior). Finally, data that meets these standards is selected from the multi-dimensional data, which is the valid interactive behavior data that can prove that the user has really participated in the interaction, and provides a basis for the subsequent calculation of service reward time.

[0036] For embodiments of this disclosure, step 120 may include the following steps: Step 120-1: Extract user interaction behavior features from the preprocessed multi-dimensional data. User interaction behavior features include at least operation continuity features, device activity features, and interaction completion features.

[0037] Among these features, operation continuity focuses on the coherence of the user interaction process, such as whether there are frequent screen switching or excessively long intervals between operations during ad viewing; device activity features emphasize the frequency of device use by users, such as the number of times a user launches a shared power bank or participates in interactions within a specific period; and interaction completion features measure whether the user has fully achieved the target interaction task, such as whether they watched the ad as required or completed the necessary interactive operations (such as clicking confirm). By extracting these three types of features, a clear characterization of user interaction behavior can be formed, providing a basis for subsequent personalized recommendations and judgments on the effectiveness of behavior.

[0038] Step 120-2: Input the user interaction behavior characteristics into the preset abnormal behavior recognition model to identify abnormal interaction behavior characteristics including no operation trajectory, device background suspension state, and repeated interaction across multiple devices.

[0039] Previously extracted user interaction behavior features (operation continuity, device activity, and interaction completion characteristics) clearly reflect the interaction patterns between users and devices. After inputting these features into the platform's pre-trained abnormal behavior identification model, the model analyzes and judges the user interaction behavior features through preset algorithm logic, focusing on identifying three types of abnormal features that do not conform to normal interaction logic: No operation trajectory means that although the user has interaction records (such as ad viewing records), there is a lack of trajectory data for active operations such as clicking and swiping, which is suspected to be non-human interaction; Device background suspension state means that the shared power bank's associated terminal or device is in background running mode during the interaction process and has not completed the interaction in the foreground, which may indicate fake viewing; Repeated interaction across multiple devices means that the same user identifier (such as account ID) initiates the same interactive task (such as repeatedly watching the same ad) through multiple shared devices in a short period of time, which is suspected of maliciously obtaining service time. By identifying these abnormal features through the model, interaction behaviors that do not conform to the platform rules can be accurately filtered out, providing a basis for subsequently refusing the issuance of invalid service time.

[0040] Accordingly, when the abnormal behavior recognition model analyzes and judges user interaction behavior characteristics through preset algorithm logic, it may specifically include the following steps: obtaining a training sample set constructed based on historical abnormal behavior data, the training sample set including data of no operation trajectory marked as abnormal, background suspended interaction data, and repeated interaction data of multiple devices; calculating the similarity between the user interaction behavior characteristics and the abnormal features in the training sample set; if the similarity is higher than a preset similarity threshold, the user interaction behavior characteristics are marked as suspected abnormal features; performing a secondary verification on the suspected abnormal features, comparing them with the feature patterns of the user's historical normal interaction behavior, if the deviation between the suspected abnormal features and the feature patterns exceeds a preset deviation threshold, the user interaction behavior characteristics are determined to be abnormal interaction behavior characteristics.

[0041] The preset similarity threshold refers to a pre-set similarity standard (e.g., 80%) used to initially determine whether the current feature is suspected of being abnormal. If the similarity between the current feature and the abnormal feature of the sample is higher than this threshold, it is marked as a suspected abnormal feature. The preset deviation threshold refers to a deviation standard (e.g., 70%) set by the platform to determine whether a suspected abnormal feature deviates from the user's normal pattern. If the deviation between a suspected abnormal feature and the user's historical normal pattern exceeds this threshold, it is ultimately determined to be an abnormal interaction behavior feature.

[0042] Step 120-3: Based on the preset validity assessment threshold, evaluate the user interaction behavior characteristics after removing abnormal interaction behavior characteristics. If the operation continuity meets the preset continuity threshold, the device activity reaches the preset activity threshold, and the interaction completion exceeds the preset completion threshold, then the user interaction behavior characteristics are determined to be valid interaction behavior characteristics.

[0043] Among them, the preset continuity threshold is the criterion for judging the continuity of operation in the effectiveness evaluation threshold. It is usually set by quantitative indicators such as the number of screen switches in a single interaction and the operation interval time (e.g., the number of screen switches ≤ 2 times, the interval between adjacent operations ≤ 5 seconds), and is used to measure the user's focus and continuity of interactive operations. The preset activity threshold is the criterion for judging the device activity in the effectiveness evaluation threshold. It is usually set by the number of times the user initiates an interaction through the device per unit time (e.g., one week, one month) and the device launch frequency (e.g., ≥ 3 interactions per week), and is used to measure the device's practical value to the user and the user's dependence. The preset completion threshold is the criterion for judging the completion of interaction in the effectiveness evaluation threshold. It is usually set by the completion rate of the target interaction task (e.g., watching an advertisement, participating in an interaction) and the completion status of necessary operation steps (e.g., the advertisement viewing time ≥ 90% of the total time, completing at least one interactive click), and is used to measure the user's depth of participation in the interaction task.

[0044] In the shared power bank operation scenario, after the abnormal behavior identification model eliminates abnormal interaction behavior features that do not conform to normal interaction logic, such as no operation trajectory, device background suspension, and repeated interaction across multiple devices, the system will verify the remaining user interaction behavior features one by one according to the pre-set validity evaluation threshold. Among them, the operation continuity must meet the preset continuity threshold, the device activity must reach the preset activity threshold, and the interaction completion rate must exceed the preset completion threshold. Only when these three features simultaneously meet the corresponding threshold requirements can the user interaction behavior feature be determined as a valid interaction behavior feature, meaning that the user's interaction behavior is genuine, compliant, and achieves the platform's expected effect, and can be used as the core basis for subsequently issuing charging service duration.

[0045] Step 120-4: Filter the effective interactive behavior data corresponding to all effective interactive behavior features in the multi-dimensional data.

[0046] The core of filtering effective interactive behavior data corresponding to all valid interactive behavior features from multi-dimensional data is to extract the original interactive data that can directly reflect the effective features through the correlation and matching of features and data (such as advertising viewing records that meet the duration requirements and device usage records accompanied by active operations). This data will serve as the core basis for subsequent calculation of charging service duration and statistical analysis of advertising conversion effects, ensuring that subsequent business is carried out only based on real and compliant interactive processes.

[0047] Step 130: Based on effective interaction behavior data, determine the service reward duration for shared devices using a dynamic calculation method.

[0048] Among them, service reward time refers to the time that the platform grants users free use of shared devices (such as the free charging time of shared power banks) based on the user's effective interaction behavior through dynamic calculation.

[0049] The service reward duration is determined dynamically based on effective interaction data. The core principle is to avoid a fixed exchange rate and instead adjust the calculation logic in real-time based on multiple factors. Specifically, it considers key information from effective interaction data (such as ad viewing time, interaction frequency, and interaction content type) while also incorporating platform operational strategies (such as advertiser bids, current revenue targets, and user credit ratings). A preset algorithm dynamically calculates the service reward duration (such as free charging time) that users should receive. For example, in the same type of ad interaction, users with higher completion rates, more frequent interactions, or those with higher advertiser bids will have their calculated reward duration increased accordingly, ensuring that the reward duration matches the interaction value and platform revenue.

[0050] For embodiments of this disclosure, step 130 may include the following steps: Step 130-1: Determine the key factors affecting the calculation of service reward duration. Extract the key factor parameters corresponding to each key factor from the effective interaction behavior data. The key factors include at least the type of device interaction content, effective interaction duration, compliance of user's historical interaction behavior, and real-time resource status of shared devices.

[0051] In the operation of shared devices (such as shared power banks), the key factors affecting the calculation of service reward duration need to be determined around three core dimensions: interaction value, user integrity, and device supply and demand. Specifically, these can include, but are not limited to, the following four categories: device interaction content type (directly related to the commercial value of the interaction, such as different categories of advertisements), effective interaction duration (reflecting the depth of user participation), compliance of users' historical interaction behavior (reflecting user integrity), and real-time resource status of shared devices (related to device supply and demand balance). After determining these key factors, specific parameters corresponding to each factor need to be extracted from the filtered effective interaction behavior data.

[0052] Step 130-2: Construct user profile tags based on users' historical interaction data, account credit rating, and interaction activity, and calculate the proportion of differentiated service duration for users according to the user profile tags.

[0053] The differentiated service time calculation ratio refers to the different service time exchange coefficients set for different user profile tags. Under the same interaction behavior, users with high-value tags correspond to a higher calculation ratio (such as 1.2 times) and can obtain more service time, while users with low-value tags are calculated according to the basic ratio (such as 1 time), so as to realize the personalization of time allocation.

[0054] By constructing user profile tags based on historical user interaction data, account credit rating, and interaction activity, and configuring differentiated service time calculation ratios, high-credit, highly active, and high-quality users can receive more incentives, enhancing their sense of belonging and stickiness to the platform. This also provides positive guidance for users with low credit, low activity, or those at risk of violations (e.g., incentivizing compliant interactions to improve their rating and increase activity for a higher percentage). Simultaneously, differentiated allocation prevents the platform from wasting excessive service time resources on low-value users, balancing operational costs and user experience. This ensures that service time for advertising revenue conversion accurately matches the needs of high-value users, further improving the quality of reach for advertisers' target users.

[0055] Step 130-3: Perform correlation calculations between the key factor parameters and the service duration calculation ratio to obtain the preliminary service reward duration for the shared equipment.

[0056] In shared device operation scenarios, key factor parameters are specific data extracted from effective interaction behavior data, including the type of interaction content with the device, effective interaction duration, user historical interaction compliance, and real-time resource status of the shared device. These parameters determine the basic calculation basis for service reward duration. The service duration calculation ratio is a differentiation coefficient (e.g., 1.2 times) configured based on user profile tags, used to reflect the preferential treatment of users with different value. The core of the correlation calculation between the two is to integrate the basic data and the differentiation coefficient according to a preset logic. For example, the basic service duration is first determined based on the type of device interaction content and effective interaction duration, and then multiplied by the service duration calculation ratio corresponding to the user. The final result is the initial service reward duration for the shared device. This duration is the initial result before subsequent adjustments such as distribution frequency control and total limit, providing the core basis for determining the final reward duration that users can obtain.

[0057] Step 130-4: Verify the reasonableness of the initial service reward duration. If the initial service reward duration exceeds the preset single duration limit or is lower than the preset single duration lower limit, adjust it according to the preset correction rules.

[0058] In shared device operation scenarios, the initial service reward duration is an initial reward result obtained through a correlation calculation between key factor parameters and service duration, and has not yet undergone reasonableness review at the operational rule level. The core of reasonableness verification is to check whether this initial duration falls within the platform's preset single-session duration boundaries. The preset single-session duration upper limit is the maximum reward a user can receive per session, set by the platform based on advertising revenue and operating costs. The preset single-session duration lower limit is the minimum value to ensure the reward has practical use value. If the initial duration exceeds the upper limit (e.g., if calculated as 50 minutes, the upper limit is 40 minutes) or falls below the lower limit (e.g., if calculated as 8 minutes, the lower limit is 10 minutes), it is adjusted according to preset correction rules (e.g., "if exceeding the upper limit, take the upper limit; if below the lower limit, take the lower limit") to ultimately obtain a reasonable reward duration that aligns with the platform's operational logic and balances user rights, avoiding extreme values ​​that could negatively impact platform costs or user experience.

[0059] Step 130-5: Check the relationship between the cumulative service reward duration obtained by the user in the current period and the preset total distribution threshold for the period. If the cumulative service reward duration has not reached the total distribution threshold for the period, the adjusted service reward duration will be directly determined as the final service reward duration for the shared device.

[0060] The current period refers to a time frame pre-set by the platform for tracking user service reward time acquisition. Common periods are weekly or monthly, and this period serves as the time boundary for controlling the total time acquired by users within a given period. The cumulative service reward time value refers to the total service reward time earned by users through all valid interactive behaviors (such as watching ads multiple times) within the current period, adjusted after a reasonableness check, reflecting the total amount of benefits acquired by users within the period. The preset periodic distribution threshold refers to the maximum service reward time that a single user can acquire within the current period, set by the platform based on advertising revenue, equipment operating costs, and user growth targets. This threshold controls the upper limit of benefits acquired by a single user within the period. The adjusted service reward time refers to the compliant time obtained after the initial service reward time has been verified for reasonableness (e.g., taking the upper limit if it exceeds the upper limit, and taking the lower limit if it is below the lower limit). This is the basis for determining the final time.

[0061] As another possible implementation, if the cumulative service reward duration obtained by the user in the current period reaches the threshold of the total amount to be distributed in the period, the adjusted service reward duration will be marked as pending distribution and will be delayed until the next period.

[0062] By verifying the relationship between the cumulative user service reward time within the current period and the total reward threshold for the period, and directly determining the adjusted time as the final time when the threshold is not reached, this approach can both limit excessive service time acquisition by individual users through the period threshold, preventing the platform from exceeding its expected operating costs due to high-frequency user interactions, and ensure that users receive their compliant benefits in a timely manner when the threshold is not reached, avoiding unnecessary restrictions that would reduce users' enthusiasm for participation. When a user's cumulative time in the current period reaches the threshold, the adjusted time is marked as pending and delayed to the next period. This approach can both strictly control the total amount of benefits acquired by individual users within the period through the period threshold, preventing the platform from exceeding its operating costs due to high-frequency compliant user interactions, and retain the benefits of the user's current interaction through the pending status, preventing users from experiencing the negative experience of losing benefits due to reaching the threshold, and maintaining users' enthusiasm for participating in effective interactions.

[0063] Step 140: Configure the service time resources corresponding to the service reward time for the user's shared device service account.

[0064] The core of configuring service time resources for an account is to accurately enter the finalized service reward time into the user's service account, update the time balance in the account, and simultaneously record information such as the source of the time (such as an advertising interaction) and the validity period, so that the user can query the resource through the account at any time and then use it for the use of shared devices (such as scanning QR codes for charging) or social gifting (such as transferring it to a friend), thus completing the closed loop from the determination of time to the availability of benefits.

[0065] In summary, the shared device service duration management method provided by this invention, by collecting multi-dimensional data during the user's interaction with the shared device, overcomes the limitation of traditional shared device service duration management relying solely on basic user operation records. It provides comprehensive data source support covering user interaction details and device status for subsequent behavior verification and duration calculation, solving the problem of insufficient basic data required for high-precision management. By validating the behavior of multi-dimensional data, it can accurately identify and eliminate abnormal or cheating behaviors such as robot simulation and background suspension, filtering out valid interaction behavior data that meets preset management requirements. This ensures the authenticity and reliability of the basis for subsequent service reward duration calculation, preventing the abuse of service resources due to invalid data and guaranteeing the reliability of duration management. Based on valid interaction behavior data, a dynamic... The calculation method determines the service reward duration, abandoning the rigidity of traditional static rules. It can flexibly adapt to the diverse characteristics of user interaction scenarios, enabling the service reward duration to accurately match the actual value of user interaction, significantly improving the accuracy of service reward duration calculation, and meeting the needs of high-precision management for duration adaptability. By configuring service duration resources corresponding to the service reward duration for the user's shared device service account, it can achieve full-process collaborative connection of user behavior data collection, validity verification, dynamic calculation, and account management, ensuring that the service resources of shared devices can be efficiently connected with the actual needs of users. This solves the technical problem that existing technologies cannot meet the high-precision management of shared device service duration under diversified user interaction scenarios, and improves the overall coordination, accuracy, and reliability of shared device service duration management.

[0066] Furthermore, to fully illustrate the implementation of this embodiment, this embodiment also provides another method for managing the service duration of shared devices, such as... Figure 2 As shown, the method includes: Step 210: Receive service duration transfer notification. The service duration transfer notification includes the initiator's identifier, the proposed transfer duration, the transfer time limit, and the confirmation / rejection operation entry.

[0067] In social scenarios involving the transfer of shared power bank service time (such as users gifting charging time to each other), the recipient will receive a system-pushed notification of the service time transfer. This notification is generated by the system and sent to the recipient as a notification of rights and an operational credential after the initiator requests the transfer of service time. The notification can include at least four core pieces of information: the initiator's identifier (clearly identifying the user initiating the transfer, such as an account nickname or anonymized ID), the proposed transfer duration (the specific amount of service time to be transferred, such as 20 minutes of free charging time), the transfer time limit (the recipient must process it within a specified time, such as confirmation within 24 hours, otherwise the transfer will be invalid), and a confirmation / rejection entry point (a function button or link for the recipient to respond quickly, without needing to search for an additional path). Through this information, the recipient can clearly understand the source of the transfer, the scale of the rights, and the processing time limit, and directly complete the response, ensuring that the transfer of service time reflects the recipient's true intention and avoiding invalid transfers.

[0068] Step 220: If a confirmation instruction submitted by the user through the operation portal is received within the transfer time limit, the proposed transfer duration is added to the user's corresponding shared device service account, and the transfer success result is fed back to the initiator through the preset communication interface.

[0069] In the social transfer scenario of shared power bank service time, if the recipient submits a confirmation instruction through the operation entry in the notification (such as the "Confirm Receipt" button) within the time limit set in the service time transfer notification (such as within 24 hours), the system will immediately perform two key operations: First, in the recipient's corresponding shared device service account, the proposed transfer time (such as 20 minutes of charging time) in the notification is added to the account's available balance, and the account's service time resources are updated in real time; Second, through the platform's preset communication interface (such as APP push, SMS interface), the system will provide feedback on the successful transfer result to the user who initiated the time transfer (such as "The 20 minutes of charging time you donated to XX has been confirmed as received"), so that the initiator can know the transfer status in a timely manner.

[0070] Step 230: If a rejection instruction submitted by the user through the operation entry is received within the time limit of the transfer, or if no response is received after the time limit of the transfer has expired, the transfer failure result is reported to the initiator through the preset communication interface.

[0071] In the social transfer scenario of shared power bank service time, there are two situations that may cause the transfer to fail: First, the recipient actively submits a rejection instruction through the operation entry (such as the "Reject" button) in the service time transfer notification within the transfer time limit (such as within 24 hours), clearly indicating that they do not accept the proposed transfer time; second, the recipient fails to respond (neither confirming nor rejecting) after the transfer time limit has expired, and the system automatically determines that the transfer request has failed. Regardless of the situation, the system will provide feedback on the transfer failure result to the user who initiated the time transfer through a pre-configured preset communication interface (such as APP push, SMS) (such as "The 15 minutes of charging time you offered to XX has not been received or has expired"), so that the initiator is aware of the transfer status in a timely manner. At the same time, the proposed transfer time will not be transferred and will remain in the initiator's shared device service account, ensuring clear ownership of the time resources.

[0072] In summary, the technical solution in this application, by using the corresponding shared device service account as the receiving account to receive service time gifted by other shared device service accounts, eliminates the need for the receiving account to rely solely on its own interactive behaviors such as watching advertisements to obtain service time. Receiving gifted service time allows for a lower barrier to entry, enabling users to access shared device resources for free. Furthermore, the interaction between users based on time gifting strengthens the platform's social attributes, transforming users from mere service users into social participants, significantly enhancing their sense of belonging and stickiness to the platform. In addition, this mechanism promotes the rational flow of service time among user accounts, reducing resource waste caused by some users having idle time or insufficient demand from others. This guides users with needs to use shared devices more precisely, indirectly alleviating the problem of uneven spatial and temporal distribution of device utilization.

[0073] Furthermore, to fully illustrate the implementation of this embodiment, this embodiment also provides another method for managing the service duration of shared devices, such as... Figure 3 As shown, the method includes: Step 310: Receive the service duration transfer request submitted by the user through the terminal operation. The service duration transfer request includes the recipient's identifier, the proposed transfer duration, and the transfer time limit.

[0074] In the social transfer scenario of shared power bank service time, users (initiators) can submit service time transfer requests through mobile apps, mini-programs, and other terminal devices. This request is initiated by the initiator, who wishes to transfer a portion of the service time in their shared device service account to other users. The request can include at least three core pieces of information: recipient identifier (used to accurately identify the user receiving the time, such as the recipient's platform account ID, bound mobile phone number, etc.), proposed transfer duration (clearly specifying the planned transfer amount of service time, such as 15 minutes or 30 minutes of free charging time), and transfer time limit (setting a deadline for the recipient to respond within a specified time, such as confirmation within 24 hours; otherwise, the transfer expires). After receiving the request, the system will generate a transfer notification based on this information and push it to the recipient, laying the foundation for subsequent time transfer and response processing, ensuring that the transfer behavior has a clear objective and clear rules.

[0075] In specific application scenarios, as a preferred approach, the implementation steps may further include: constructing a transfer object association model based on the user's contact list data, historical transfer records, frequency of social interactions, and the recipient's shared device usage needs; generating a transfer object recommendation list through analysis of the transfer object association model, supporting users to select transfer objects from the transfer object recommendation list or manually input object identifiers when submitting service duration transfer requests, the transfer object recommendation list including recommended object identifiers, recommendation priorities, and recommendation criteria.

[0076] By constructing a multi-dimensional data-driven association model for shared power bank users and generating a priority-based recommendation list, this solution ensures a genuine connection between recommended users and their contacts, avoiding trust issues arising from recommending unfamiliar individuals. It also leverages the recipient's needs to guarantee that recommended users truly require the time allotted, enhancing the practical value of the shared power bank service. Furthermore, the recommendation list simplifies the user selection process, reducing the operational cost of manually inputting identifiers, making it particularly user-friendly for those unfamiliar with identifiers. The support for manual input maintains flexibility, allowing for the fulfillment of specific shared power bank needs. Overall, this solution improves the efficiency and experience of submitting shared power bank requests, promotes the flow of service time to those in need, further activates the platform's social attributes and improves the efficiency of time resource turnover, providing strong support for the socialized operation of shared power bank services.

[0077] Step 320: Query the available service duration cached locally by the user's corresponding shared device service account, determine whether it is not less than the intended transfer duration, and at the same time send a recipient account status verification request to the platform to obtain the verification result returned by the platform to determine whether the recipient account status is normally enabled.

[0078] Among them, available service time refers to the service time data that can be directly used in the shared device service account stored locally on the user terminal (such as mobile APP). It is a temporary version of the recent account balance and may include the service reward time obtained in the current period; the planned transfer time refers to the amount of shared device service time that the user plans to transfer from their own account to the recipient (such as 15 minutes or 30 minutes of charging time).

[0079] By querying the available service duration cached locally by the initiator and comparing it to determine whether the available service duration is not less than the intended transfer duration, it is ensured that the initiator has sufficient time resources to complete the transfer. At the same time, the platform can also verify the recipient's account status to ensure that the recipient is qualified to receive, reduce invalid transfers caused by abnormal recipient accounts (such as frozen or canceled accounts), and reduce the waste of platform resources.

[0080] Step 330: If the available service duration is greater than or equal to the intended transfer duration, and the recipient's account status is in normal enabled state, then the shared device service account will be used as the initiator account to send a service duration transfer notification to the recipient terminal.

[0081] In the social transfer scenario of shared power bank service time, the system first completes two core pre-verifications: First, it confirms whether the available service time in the initiator's shared device service account is greater than or equal to the planned transfer time to others, ensuring that the initiator has sufficient resources to complete the transfer; second, it verifies whether the recipient's account status is normally enabled, ruling out abnormal situations where the recipient cannot receive the service. When both verifications pass, the system will identify the initiator's shared device service account as the initiator account for this transfer and immediately push a service time transfer notification to the recipient's terminal device (such as a mobile APP or mini-program). The notification will include the initiator's identifier, the planned transfer time, the transfer time limit, and the confirmation / rejection operation entry, allowing the recipient to be aware of the transfer request in a timely manner and respond quickly, thus promoting the orderly progress of the time transfer process.

[0082] Step 340: If a successful transfer result is received from the recipient within the transfer time limit, the proposed transfer time will be deducted from the shared device service account, and a transfer success notification will be pushed to the user.

[0083] Upon receiving a successful result within the transfer period, the intended transfer duration is deducted from the initiator's account and a success notification is sent. This ensures that the account balance matches the actual benefits through real-time deduction, preventing duplicate transfers or overuse of time and guaranteeing the accuracy of platform data. Furthermore, timely notifications allow the initiator to clearly understand the transfer status, eliminating doubts about success and enhancing user trust in the transfer function.

[0084] Step 350: If a transfer failure result is received from the recipient within the transfer time limit, the service time transfer process is terminated, and a transfer failure notification is pushed to the user.

[0085] Upon receiving a failure result within the processing timeframe, the processing flow is terminated and a failure notification is sent. This not only prevents user rights losses due to continued operations (such as accidental deduction of time) by promptly terminating unsuccessful processes, thus protecting the initiator's time resources, but also allows the initiator to clearly understand the specific circumstances of the unsuccessful processing flow through a notification that includes the reason for the failure.

[0086] In summary, the technical solution in this application, by using the corresponding shared device service account as the initiating account to gift service time to other shared device service accounts, eliminates the need for recipient accounts to rely solely on their own interactive behaviors such as watching advertisements to obtain service time. Receiving gifts allows them to access shared device resources for free with a lower barrier to entry. Furthermore, the interaction between users based on time gifting strengthens the platform's social attributes, transforming users from mere service users into social participants, significantly enhancing their sense of belonging and stickiness to the platform. In addition, this mechanism promotes the rational flow of service time among user accounts, reducing resource waste caused by some users having idle time or insufficient demand from others. This guides users with needs to use shared devices more precisely, indirectly alleviating the problem of uneven spatial and temporal distribution of device utilization.

[0087] Furthermore, as Figure 1 , Figure 2 and Figure 3 The specific implementation of the method shown in this embodiment provides a service duration management device for shared devices, such as... Figure 4 As shown, the device includes: a data acquisition module 41, a filtering module 42, a determination module 43, and a configuration module 44.

[0088] The data acquisition module 41 can be used to collect multi-dimensional data during the interaction between the user and the shared device; The filtering module 42 can be used to verify the validity of multi-dimensional data and filter out valid interactive behavior data that meets the preset management requirements. Module 43 can be used to determine the service reward duration of shared devices based on effective interaction behavior data and using a dynamic calculation method. Configuration module 44 can be used to configure the service time resources corresponding to the service reward time for the user's shared device service account.

[0089] In some embodiments of this application, the acquisition module 41 can be specifically used to determine the acquisition range of multi-dimensional data. The acquisition range at least covers the effective interaction duration, interaction operation behavior, page focus dwell time, and device operating status data during the interaction between the user and the shared device. The acquisition module deployed on the shared device is activated to acquire multi-dimensional data within the acquisition range in real time according to a preset sampling frequency. The real-time acquired multi-dimensional data is preprocessed, including at least data deduplication, noise data filtering, and data format standardization. The preprocessed multi-dimensional data is stored in a distributed database or blockchain, and a unique timestamp and user identifier are added to each piece of data.

[0090] In some embodiments of this application, such as Figure 5 As shown, the device may further include: a construction module 45, a generation module 46, and a receiving module 47.

[0091] Module 45 can be used to build user profiles based on users' basic information, historical interaction data, account credit rating and preference characteristics; The generation module 46 can be used to generate and display a personalized content recommendation list by matching multiple interactive contents that are suitable for the user profile and the requirements parameters of the content provider through a content matching algorithm. The receiving module 47 can be used to receive the target interactive content selected by the user in the personalized content recommendation list.

[0092] In some embodiments of this application, the filtering module 42 is specifically used to extract user interaction behavior features from preprocessed multi-dimensional data. The user interaction behavior features include at least operation continuity features, device activity features, and interaction completion features. The user interaction behavior features are input into a preset abnormal behavior recognition model to identify abnormal interaction behavior features including no operation trajectory, device background suspension state, and repeated interaction across multiple devices. Based on a preset validity evaluation threshold, the user interaction behavior features after removing abnormal interaction behavior features are evaluated. If the operation continuity meets a preset continuity threshold, the device activity reaches a preset activity threshold, and the interaction completion exceeds a preset completion threshold, then the user interaction behavior feature is determined to be a valid interaction behavior feature. Valid interaction behavior data corresponding to all valid interaction behavior features are filtered from the multi-dimensional data.

[0093] In some embodiments of this application, the determining module 43 can be specifically used to determine the key factors affecting the calculation of service reward duration. It extracts key factor parameters corresponding to each key factor from effective interaction behavior data. The key factors include at least the type of device interaction content, effective interaction duration, compliance of the user's historical interaction behavior, and the real-time resource status of the shared device. Based on the user's historical interaction data, account credit level, and interaction activity, it constructs user profile tags and configures differentiated service duration calculation ratios for users according to these user profile tags. It performs correlation calculations between the key factor parameters and the service duration calculation ratios to obtain the initial service reward duration for the shared device. It performs a reasonableness check on the initial service reward duration. If the initial service reward duration exceeds the preset single duration upper limit or is lower than the preset single duration lower limit, it is adjusted according to preset correction rules. It checks the relationship between the cumulative value of service reward duration obtained by the user in the current period and the preset total periodic distribution threshold. If the cumulative value of service reward duration does not reach the total periodic distribution threshold, the adjusted service reward duration is directly determined as the final service reward duration for the shared device.

[0094] In some embodiments of this application, such as Figure 5 As shown, the device may further include: a feedback module 48; The receiving module 47 can also be used to receive service duration transfer notifications, which include the initiator identifier, the proposed transfer duration, the transfer time limit, and the confirmation / rejection operation entry. The feedback module 48 can be used to add the proposed transfer duration to the user's corresponding shared device service account if a confirmation instruction submitted by the user through the operation entry is received within the transfer time limit, and to send the transfer success result back to the initiator through a preset communication interface. The feedback module 48 can be used to send feedback on the failure of the transfer to the initiator through a preset communication interface if a rejection instruction submitted by the user through the operation entry is received within the transfer time limit or if no response is received after the transfer time limit has expired.

[0095] In some embodiments of this application, such as Figure 5 As shown, the device may further include: a query module 49 and a sending module 410; The receiving module 47 can also be used to receive service duration transfer requests submitted by users through terminal operations. The service duration transfer request includes the recipient identifier, the proposed transfer duration, and the transfer time limit. The query module 49 can be used to query the available service duration of the local cache of the user's corresponding shared device service account, determine whether it is not less than the intended transfer duration, and send a recipient account status verification request to the platform to obtain the verification result returned by the platform to see if the recipient account status is normally enabled. The sending module 410 can be used to send a service duration transfer notification to the receiving terminal by using the shared device service account as the initiator account if the available service duration is greater than or equal to the intended transfer duration and the recipient account status is in normal enabled state. The sending module 410 can be used to deduct the proposed transfer time from the shared device service account and push a transfer success notification to the user if a successful transfer result is received from the recipient within the transfer time limit. The sending module 410 can be used to terminate the service duration transfer process and push a transfer failure notification to the user if a transfer failure result is received from the recipient within the transfer time limit.

[0096] In some embodiments of this application, the construction module 45 can also be used to construct a flow object association model based on the user's address book data, historical flow records, frequency of social interactions, and the recipient's shared device usage needs; The generation module 46 can also be used to generate a recommended list of transfer objects through the association model of transfer objects. When submitting a service transfer request, users can select transfer objects from the recommended list or manually input object identifiers. The recommended list of transfer objects includes recommended object identifiers, recommendation priorities, and recommendation criteria.

[0097] It should be noted that other corresponding descriptions of the functional units involved in the shared device service duration management device provided in this embodiment can be found in the following references. Figure 1 , Figure 2 and Figure 3 The corresponding description in [the document] will not be repeated here.

[0098] Based on the above, Figure 1 , Figure 2 and Figure 3 Accordingly, this embodiment also provides a storage medium storing a computer program that, when executed by a processor, implements the above-described method. Figure 1 , Figure 2 and Figure 3 The method for managing the service duration of shared devices is shown.

[0099] Based on this understanding, the technical solution of this application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as CD-ROM, USB flash drive, mobile hard drive, etc.) and includes several instructions to cause an electronic device (such as personal computer, server, or network device, etc.) to execute the methods of various implementation scenarios of this application.

[0100] Based on the above, Figure 1 , Figure 2 and Figure 3 The method shown, and Figure 3and Figure 4 To achieve the above objectives, the present application also provides an electronic device, specifically a personal computer, tablet computer, server, or other network device, as shown in the virtual device embodiment. This device includes a storage medium and a processor; the storage medium stores a computer program; the processor executes the computer program to achieve the above-described objectives. Figure 1 , Figure 2 and Figure 3 The method for managing the service duration of shared devices is shown.

[0101] Optionally, the aforementioned physical devices may also include a user interface, a network interface, a camera, radio frequency (RF) circuitry, sensors, audio circuitry, a Wi-Fi module, etc. The user interface may include a display screen, input units such as a keyboard, etc., and optional user interfaces may also include USB interfaces, card reader interfaces, etc. The network interface may optionally include standard wired interfaces, wireless interfaces (such as Wi-Fi interfaces), etc.

[0102] Those skilled in the art will understand that the physical device structure provided in this embodiment does not constitute a limitation on the physical device, and may include more or fewer components, or combine certain components, or have different component arrangements.

[0103] The storage medium may also include an operating system and a network communication module. The operating system is a program that manages the hardware and software resources of the aforementioned physical device, supporting the operation of information processing programs and other software and / or programs. The network communication module is used to enable communication between the various components within the storage medium, as well as communication with other hardware and software in the information processing physical device.

[0104] Through the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware platform, or it can be implemented by hardware.

[0105] This invention uses a dynamic calculation method based on effective interactive behavior data to determine service reward duration, overcoming the rigidity of traditional static rules. It flexibly adapts to the diverse characteristics of user interaction scenarios, ensuring that service reward duration accurately matches the actual value of user interactions. This significantly improves the accuracy of service reward duration calculation and meets the needs of high-precision management for duration adaptability. Simultaneously, shared device service accounts can gift service duration to each other. Receiving gifts allows users to access shared device resources for free with a lower barrier to entry. Furthermore, user interaction based on time gifting strengthens the platform's social attributes, transforming users from mere service users into social participants, significantly enhancing their sense of belonging and stickiness to the platform. In addition, this mechanism promotes the rational flow of service duration among user accounts, reducing resource waste caused by some users having idle time or insufficient demand from others. This guides users with needs to use shared devices more precisely, indirectly alleviating the problem of uneven spatial and temporal distribution of device utilization.

[0106] Those skilled in the art will understand that the accompanying drawings are merely schematic diagrams of a preferred embodiment, and the modules or processes shown in the drawings are not necessarily essential for implementing this application. Those skilled in the art will understand that the modules in the apparatus of the embodiment can be distributed within the apparatus of the embodiment as described, or can be modified to be located in one or more apparatuses different from this embodiment. The modules of the above-described embodiment can be combined into one module, or further divided into multiple sub-modules.

[0107] The serial numbers in this application are for descriptive purposes only and do not represent the superiority or inferiority of any particular implementation scenario. The above disclosures are merely a few specific implementation scenarios of this application; however, this application is not limited thereto, and any variations conceived by those skilled in the art should fall within the protection scope of this application.

Claims

1. A method for managing the service duration of shared devices, characterized in that, include: Collect multi-dimensional data during the interaction between users and shared devices; The multi-dimensional data is subjected to behavior validity verification, and valid interactive behavior data that meets the preset management requirements is selected. Based on the effective interaction behavior data, the service reward duration of the shared device is determined using a dynamic calculation method; Configure the service duration resources corresponding to the service reward duration for the shared device service account corresponding to the user.

2. The method according to claim 1, characterized in that, The collection of multi-dimensional data during the interaction between the user and the shared device includes: Determine the scope of multi-dimensional data collection, which shall at least cover the effective interaction duration, interactive operation behavior, page focus dwell time and device operating status data during the interaction between the user and the shared device for the target interactive content; The acquisition module deployed on the shared device is activated to collect multi-dimensional data within the acquisition range in real time according to a preset sampling frequency. The multi-dimensional data collected in real time is preprocessed, and the preprocessing includes at least data deduplication, noise data filtering and data format standardization. The pre-processed multi-dimensional data is stored in a distributed database or blockchain, and a unique timestamp and user identifier are added to each piece of data.

3. The method according to claim 2, characterized in that, The method further includes: Based on the user's basic information, historical interaction data, account credit rating, and preference characteristics, a user profile is constructed. Based on the user profile and the content provider's requirements, a personalized content recommendation list is generated and displayed by matching multiple suitable interactive contents through a content matching algorithm. Receive the target interactive content selected by the user from the personalized content recommendation list.

4. The method according to claim 1, characterized in that, The multi-dimensional data is subjected to behavior validity verification, and valid interactive behavior data that meets preset management requirements is selected, including: User interaction behavior features are extracted from the preprocessed multi-dimensional data. These user interaction behavior features include at least operation continuity features, device activity features, and interaction completion features. The user interaction behavior features are input into a preset abnormal behavior recognition model to identify abnormal interaction behavior features including no operation trajectory, device background suspension state, and repeated interaction across multiple devices. Based on a preset validity assessment threshold, the user interaction behavior features after removing the abnormal interaction behavior features are evaluated. If the operation continuity meets a preset continuity threshold, the device activity reaches a preset activity threshold, and the interaction completion exceeds a preset completion threshold, then the user interaction behavior features are determined to be valid interaction behavior features. Filter the effective interactive behavior data corresponding to all the effective interactive behavior features from the multi-dimensional data.

5. The method according to claim 1, characterized in that, The determination of the service reward duration for the shared device based on the effective interaction behavior data using a dynamic calculation method includes: Identify the key factors that affect the calculation of service reward duration, and extract the key factor parameters corresponding to each key factor from the effective interaction behavior data. The key factors include at least the device interaction content type, effective interaction duration, compliance of user's historical interaction behavior, and real-time resource status of shared devices. User profile tags are constructed based on the user's historical interaction data, account credit rating, and interaction activity, and a differentiated service duration calculation ratio is configured for the user according to the user profile tags. The key factor parameters are correlated with the service duration calculation ratio to obtain the initial service reward duration of the shared device. The reasonableness of the initial service reward duration is checked. If the initial service reward duration exceeds the preset single duration limit or is lower than the preset single duration lower limit, it is adjusted according to the preset correction rules. The relationship between the cumulative service reward duration obtained by the user in the current period and the preset total distribution threshold for the period is checked. If the cumulative service reward duration does not reach the total distribution threshold for the period, the adjusted service reward duration is directly determined as the final service reward duration of the shared device.

6. The method according to claim 1, characterized in that, The method further includes: Receive service duration transfer notification, which includes the initiator's identifier, the proposed transfer duration, the transfer time limit, and a confirmation / rejection operation entry; If a confirmation instruction submitted by the user through the operation entry is received within the time limit of the transfer, the proposed transfer duration is added to the shared device service account corresponding to the user, and the transfer success result is fed back to the initiator through a preset communication interface; If a rejection instruction submitted by the user through the operation entry is received within the time limit of the transfer, or if no response is received after the time limit of the transfer has expired, the transfer failure result is reported to the initiator through the preset communication interface.

7. The method according to claim 1, characterized in that, The method further includes: Receive the service duration transfer request submitted by the user through terminal operation. The service duration transfer request includes the recipient identifier, the proposed transfer duration and the transfer time limit. Query the available service duration cached locally by the shared device service account corresponding to the user, determine whether it is not less than the intended transfer duration, and at the same time send a receiver account status verification request to the platform to obtain the verification result returned by the platform to see if the receiver account status is normally enabled. If the available service duration is greater than or equal to the intended transfer duration, and the recipient's account status is in normal enabled state, then the shared device service account will be used as the initiator account to send a service duration transfer notification to the recipient terminal. If a successful transfer result is received from the recipient within the transfer time limit, the proposed transfer time will be deducted from the shared device service account, and a transfer success notification will be pushed to the user. If a failure result is received from the recipient within the specified time limit, the service duration transfer process will be terminated, and a transfer failure notification will be sent to the user.

8. The method according to claim 7, characterized in that, The method further includes: Based on the user's contact list data, historical transfer records, frequency of social interactions, and the recipient's shared device usage needs, a transfer object association model is constructed; The flow object association model is used to generate a flow object recommendation list. When the user submits the service duration flow request, the user can select a flow object from the flow object recommendation list or manually input an object identifier. The flow object recommendation list includes the recommended object identifier, recommendation priority, and recommendation basis.

9. A service duration management device for shared equipment, characterized in that, include: The data acquisition module is used to collect multi-dimensional data during the interaction between users and shared devices; The filtering module is used to verify the validity of the multi-dimensional data and filter out valid interactive behavior data that meets the preset management requirements. The determination module is used to determine the service reward duration of the shared device based on the effective interaction behavior data using a dynamic calculation method; The configuration module is used to configure the service duration resources corresponding to the service reward duration for the shared device service account corresponding to the user.

10. An electronic device comprising a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method of any one of claims 1 to 8.

Images