Service processing method and device based on identification equipment

Abstract

The embodiment of the invention provides a service processing method and device based on identification equipment, and the method comprises the steps: carrying out the identity verification according to the ticket information of a user, synchronized with a site system, of a tour site in a service processing process, and carrying out the verification of the identity of the user; after the verification succeeds, the identification equipment is distributed to the user in the sightseeing place, on the basis, according to the equipment identification submitted after the user terminal interacts with the identification equipment, user identity binding of the identification equipment is carried out, and service configuration information is obtained through service configuration of the identification equipment in the sightseeing place; and if a service request carrying the equipment identifier is received, service response processing is carried out based on cooperation of the service configuration information and the place system, so that service processing for the touring place is realized based on the identification equipment.

Description

Technical Field

[0001] This document relates to the field of data processing technology, and in particular to a service processing method and apparatus based on an identification device. Background Technology

[0002] With the continuous development of information technology and smart terminal devices, tourist attractions such as scenic spots and theme parks are gradually introducing digital services. The digital application of identity recognition, service interaction, and payment has become an industry trend, and the operational efficiency and service capabilities of tourist attractions are gradually improving with the application of digital technology. In the operation and service of tourist attractions, the introduction of technologies such as electronic ticketing verification and online service guidance has become an important way to improve the service level and optimize the tourist experience. However, as tourists' diversified needs for the tourist experience continue to increase, and tourist attractions' need for refined operation becomes increasingly urgent, how to provide users with a better service model has become a key focus for relevant service providers. Summary of the Invention

[0003] This specification provides one or more embodiments of a service processing method based on an identification device, applied to a service platform. The method includes: verifying the user's identity based on user ticketing information synchronized with a venue system, and allocating an identification device to the user at the venue upon successful verification; binding the user's identity to the identification device based on a device identifier submitted after interaction between the user terminal and the identification device; configuring the identification device's service at the venue to obtain service configuration information, and synchronizing the device identifier with the venue system; and, if a service request carrying the device identifier is received, cooperating with the venue system to perform service response processing based on the service configuration information.

[0004] This specification provides one or more embodiments of another service processing method based on an identification device, applied to the identification device. The method includes: performing near-field interaction with a user terminal and sending a device identifier to the user terminal to bind the identification device to the user's identity and configure venue services; the identification device assigning a service to the user after successful identity verification based on the user's ticketing information; interacting with a venue interaction device at the visited venue and transmitting the device identifier to upload the device identifier to the venue system and synchronize it with the service platform; the service platform cooperating with the venue system to perform service response processing based on the service configuration information obtained from the venue service configuration.

[0005] This specification provides one or more embodiments of a service processing apparatus based on an identification device, running on a service platform. The apparatus includes: an identity verification module configured to verify the identity of a user at a visitor venue based on user ticketing information synchronized with the venue system, and to allocate an identification device to the user at the visitor venue upon successful verification; an identity binding module configured to bind the user's identity to the identification device based on a device identifier submitted after interaction between the user terminal and the identification device; a service configuration module configured to obtain service configuration information for the identification device at the visitor venue and synchronize the device identifier to the venue system; and a response processing module configured to, upon receiving a service request carrying the device identifier, cooperate with the venue system to perform service response processing based on the service configuration information.

[0006] This specification provides one or more embodiments of another service processing apparatus based on an identification device, operating on the identification device. The apparatus includes: a near-field interaction module configured to interact with a user terminal and send a device identifier to the user terminal for user identity binding and venue service configuration; the identification device assigns the identifier to the user after successful identity verification based on the user's ticket information. An identifier transmission module is configured to interact with the venue interaction device of the visited venue and transmit the device identifier, so as to upload the device identifier to the venue system and synchronize it with the service platform through the venue interaction device; the service platform, based on the service configuration information obtained from the venue service configuration, cooperates with the venue system to perform service response processing.

[0007] This specification provides one or more embodiments of a service processing device based on an identification device, comprising: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: perform identity verification based on user ticketing information of a visitor venue synchronized with a venue system, and, upon successful verification, allocate an identification device to a user at the visitor venue; bind the user identity of the identification device based on a device identifier submitted by the user terminal after interaction with the identification device; perform service configuration of the identification device at the visitor venue to obtain service configuration information, and synchronize the device identifier with the venue system; and, if a service request carrying the device identifier is received, perform service response processing in cooperation with the venue system based on the service configuration information.

[0008] This specification provides one or more embodiments of another service processing device based on an identification device, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: perform near-field interaction with a user terminal and send a device identifier of the identification device to the user terminal for user identity binding and venue service configuration; the identification device is allocated to the user after successful identity verification based on user ticketing information; and interact with a venue interaction device of the visited venue and transmit the device identifier to upload the device identifier to the venue system and synchronize it with the service platform through the venue interaction device; the service platform, based on the service configuration information obtained from the venue service configuration, cooperates with the venue system to perform service response processing.

[0009] This specification provides one or more embodiments of a computer-readable storage medium for storing computer-executable instructions. When executed, these instructions implement the following process: verifying the user's identity based on user ticketing information synchronized with a venue system, and allocating an identification device to the user at the venue upon successful verification; binding the user's identity to the identification device based on a device identifier submitted after interaction between the user terminal and the identification device; obtaining service configuration information for the identification device at the venue and synchronizing the device identifier with the venue system; and, if a service request carrying the device identifier is received, cooperating with the venue system to perform service response processing based on the service configuration information.

[0010] This specification provides one or more embodiments of another computer-readable storage medium for storing computer-executable instructions, which, when executed, perform the following processes: performing near-field interaction with a user terminal and sending a device identifier of an identification device to the user terminal to bind the identification device to the user's identity and configure venue services; the identification device assigning a service to the user after successful identity verification based on the user's ticketing information; interacting with a venue interaction device at the venue and transmitting the device identifier to upload the device identifier to the venue system and synchronize it with the service platform; the service platform cooperating with the venue system to perform service response processing based on the service configuration information obtained from the venue service configuration. Attached Figure Description

[0011] To more clearly illustrate the technical solutions in one or more embodiments of this specification or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. Figure 1 A schematic diagram illustrating an implementation environment for a service processing method based on an identification device provided in one or more embodiments of this specification; Figure 2 A flowchart illustrating a service processing method based on an identification device, provided for one or more embodiments of this specification; Figure 3 A timing diagram illustrating a service processing method based on a recognition device for use in a location tour scenario, provided in one or more embodiments of this specification. Figure 4 A flowchart illustrating another service processing method based on an identification device provided in one or more embodiments of this specification; Figure 5 A schematic diagram illustrating an embodiment of a service processing apparatus based on an identification device, provided for one or more embodiments of this specification. Figure 6 A schematic diagram of another embodiment of a service processing apparatus based on an identification device provided in one or more embodiments of this specification; Figure 7 A schematic diagram of the structure of a service processing device based on an identification device provided in one or more embodiments of this specification; Figure 8 This is a schematic diagram of the structure of another service processing device based on an identification device provided in one or more embodiments of this specification. Detailed Implementation

[0012] To enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of this document.

[0013] The service processing method based on identification devices provided in one or more embodiments of this specification is applicable to the service platform implementation environment. (Refer to...) Figure 1 The implementation environment includes at least: Service platform 101, venue system 102, user terminal 103, user identification device 104, venue interaction device for visiting the venue 105; The service platform 101 is used to verify the identity of users based on the ticket information of the visitor venue synchronized by the venue system 102. After successful verification, it allocates identification devices to users at the visitor venue, binds the user identity of the identification devices, and synchronizes the device identifier of the identification devices with the venue system. In this way, it works with the venue system 102 to realize service processing based on the identification devices 104. The service platform 101 can be a server, a server cluster composed of several servers, or one or more cloud servers in a cloud computing platform. The venue system 102 is used to synchronize user ticketing information for visiting the venue to the service platform 101, cooperate with the service platform 101 to synchronize the device identification of the identification device, and cooperate with the service platform 101 to process service responses. The venue system 102 can be deployed on a server that processes venue services. The server can be one or more servers, a server cluster composed of several servers, or a cloud server of a cloud computing platform. The user's terminal 103 is used to perform near-field interaction with the user's identification device 104 and obtain the device identifier sent by the identification device 104, and submit the device identifier to the service platform 101 so that the service platform 101 can bind the user's identity to the identification device 104 and configure the venue service. The user's terminal 103 may be a mobile phone, personal computer, tablet computer, e-book reader, device for information interaction based on VR (Virtual Reality) and AR (Augmented Reality), vehicle terminal, IoT device, wearable smart device, laptop computer and desktop computer, etc. The user identification device 104 is used to perform near-field interaction with the user terminal 103 and send the device identifier to the user terminal 103, and to interact with the site interaction device of the tour site and transmit the device identifier. The site interaction device 105 is used to interact with the user's identification device 104 and obtain the device identifier transmitted by the identification device 104, and to upload the device identifier to the site system 102.

[0014] In this implementation environment, during the service processing, the service platform 101 first verifies the user's identity based on the user ticketing information synchronized by the venue system 102. After successful verification, the platform assigns an identification device 104 to the user at the venue. Based on this, the platform binds the user's identity to the identification device 104 according to the device identifier submitted after the user terminal 103 interacts with the identification device 104, and obtains service configuration information for the identification device 104 at the venue. The platform then synchronizes the device identifier with the venue system 102. Subsequently, if a service request carrying the device identifier is received, the platform cooperates with the venue system 102 to process the service response based on the service configuration information. In this way, through the cooperation between the service platform 101 and the venue system 102, service processing for the venue is achieved based on the identification device.

[0015] Reference Figure 2 The service processing method based on identification device provided in this embodiment is applied to a service platform, and the method specifically includes steps S202 to S208.

[0016] Step S202: Verify the user's identity based on the user's ticket information synchronized with the venue system, and distribute the identification device to the user at the venue after successful verification.

[0017] The tourist attractions described in this embodiment include places where users visit, tour, or consume services, such as scenic spots, theme parks, museums, and cultural districts. The attraction system can interact with the service platform, interactive devices within the attraction, and user terminals. Specifically, the attraction system can receive, store, and / or process user ticketing information, manage the allocation of identification devices, and synchronize service configuration information for the attraction. In addition, the attraction system can also send service configuration information to interactive devices within the attraction, such as access gates and POS terminals, to support subsequent service interactions based on identification devices.

[0018] The identification device refers to a wearable device with a unique device identifier. The identification device can communicate with external systems through near field communication technology to achieve identity recognition, data interaction and / or service triggering. For example, the identification device can be a smart bracelet with an integrated NFC (Near Field Communication) module or an NFC chip. Specifically, the identification device can interact with venue interaction devices, such as access gates, POS terminals and / or interactive terminals deployed in the tourist area. The identification device can also interact with venue interaction tags, such as near field communication tags deployed in the tourist area. Alternatively, the identification device can also interact with the interactive identification devices of other tourists (the tourists' identification devices).

[0019] In practice, considering that users need to purchase or reserve tickets for the venue before entering the venue, and that user ticket information needs to be associated before subsequent user identity verification and identification device allocation, users can process tickets and / or associate user ticket information through the service program. Specifically, during the access process, users can scan service identifiers at the attraction using their user terminals. For example, service identifiers can be deployed in offline service areas such as ticket offices and entrances. These identifiers can embed access entry information for the service program. After scanning the service identifier, the user terminal can be redirected to and launch the attraction's service program based on the parsed access link. Alternatively, users can access the service program by reading service access information from the attraction's near-field communication (NFC) components. For instance, NFC components can be deployed in offline service areas of the attraction. Once the user terminal establishes a NFC connection with the NFC component, the NFC component transmits service access information to the user terminal. The user terminal receives and parses the service access information, and then launches and enters the attraction's service program based on it. Optionally, the service program can access the site by scanning the service identifier of the site with the user terminal, or by reading service access information from the near-field communication component of the site with the user terminal.

[0020] In this context, a service application refers to an application deployed on a terminal device that has data collection and / or data interaction functions. For example, a service application can be an application used for ticketing processing. A service application can be an independent third-party application, such as a ticketing service application or a browsing service application. In addition, a service application can also be a functional module or subroutine deployed within an application. Subroutines include program functional modules or application components mounted on the host application (application), or program functional modules or application components loaded and installed by the host application, such as mini-programs within a payment application. From a service perspective, subroutines mounted on an application have the ability to independently provide self-closing services, such as mini-programs running within a payment application that provide self-closing ticketing processing services.

[0021] Furthermore, after accessing the service program through any of the above methods, the user can associate tickets through the ticketing page of the service program; subsequently, after the user associates tickets, the venue system of the visited venue can receive the user's ticketing information synchronized by the service program, and further synchronize the user's ticketing information to the service platform; optionally, the user's ticketing information is synchronized after the user accesses the ticketing page of the service program of the visited venue and associates tickets.

[0022] Here, in addition to the above-mentioned methods for users to access the service program and then access the ticketing page, users can also access the ticketing page by scanning the service identifier with their user terminal, or by reading service access information from the near-field communication component of the tourist attraction using their user terminal. Based on this, the ticketing page of the service program is accessed by scanning the service identifier of the tourist attraction with the user terminal, or by reading service access information from the near-field communication component of the tourist attraction using the user terminal.

[0023] In practice, based on the synchronization of user ticketing information from the venue system to the service platform, in order to achieve effective association between the identification device and the user ticketing information and improve the management of identification devices and service resources, the service platform, after obtaining the user ticketing information synchronized from the venue system, performs identity verification on the user based on the user ticketing information of the venue visited. This includes verification of authenticity, validity, and / or matching. If the verification is successful, the venue system can allocate identification devices to the user at the venue visited; if the verification fails, a failure notification can be returned to the user's terminal or no action can be taken.

[0024] In the specific implementation process, in order to achieve efficient allocation of identification devices, the allocation of identification devices can be carried out through near-field interaction between the user terminal and the equipment management terminal of the tourist site. In an optional implementation method provided in this embodiment, the identification devices are allocated in the following way: The system obtains user information through near-field interaction between the equipment management terminal and the user terminal at the venue and submits it to the venue system. The venue system verifies the equipment application or user ticket based on the user information, and after the verification is passed, it issues an allocation instruction to the equipment management terminal so that the equipment management terminal can allocate identification equipment to the user according to the allocation instruction.

[0025] Specifically, during the application process for identification devices, users can submit their applications online in advance. In this case, the venue system verifies the application based on the user information. Alternatively, users can apply for identification devices on-site at the venue without prior online submission. In this case, the venue system verifies the user's ticket information. During the allocation of identification devices, users can bring their terminals close to the device management terminal deployed at the venue. After establishing a near-field communication connection between the device management terminal and the user terminal, the device management terminal can interact with the user to obtain user information and submit it to the venue system. Upon receiving the user information, the venue system verifies either the application or the ticket. If the verification is successful, the venue system issues an allocation instruction to the device management terminal, which then allocates the identification device to the user. Optionally, the allocated identification device belongs to the user.

[0026] Specifically, the device application verification includes verifying whether a user's device application record exists. If so, the device application verification is confirmed to be successful; otherwise, the device application verification is confirmed to be unsuccessful. Optionally, the device application record is generated after the user submits a device application through the device application portal on the ticketing page of the service program, or after purchasing the device through the ticketing page.

[0027] In addition to the above-mentioned method of allocating identification devices through the venue system and the equipment management terminal of the tourist venue, there may also be situations where the tourist venue is not equipped with an equipment management terminal. In this case, identification devices can also be allocated through the management user of the tourist venue. Specifically, the management user of the tourist venue obtains user information through near-field interaction with the user terminal and submits it to the venue system. The venue system verifies the device application or user ticket based on the user information, and sends an allocation confirmation prompt to the management terminal after the verification is passed, so that the management user can allocate identification devices to the user according to the allocation confirmation prompt.

[0028] In addition, during the allocation of identification devices, besides the venue system verifying device applications or user tickets based on user information, the service platform can also verify identity based on user ticket information. In this case, if the verification is successful, the service platform can synchronize the verification result to the venue system. Accordingly, the venue system sends an allocation instruction to the device management terminal so that the device management terminal can allocate identification devices to users according to the allocation instruction.

[0029] In practical applications, considering users' personalized needs for identification devices, such as differentiated needs for the appearance, markings and / or functional attributes of identification devices, in this embodiment, after purchasing or applying for the device through the service program, users can configure the materials for the identification device. Correspondingly, the material configuration information generated after the user configures the materials can be used to manufacture the identification device for shipment. Optionally, the identification device obtains its manufacturing process by producing the equipment materials based on the user's material configuration information; the material configuration information is generated after the user purchases or applies for the equipment and configures the materials through the service program.

[0030] Material configuration information refers to the information used to manufacture the equipment materials for the identification equipment, including but not limited to the equipment color, equipment pattern, engraved text and / or customized elements of the identification equipment.

[0031] For example, when users apply for or purchase devices through the service program, they can choose different types of recognition devices, such as standard wristbands, customized wristbands co-branded with scenic area IPs, or task-unlocking wristbands. Different types of recognition devices correspond to different device purchase or application rules. In addition, the user's ticketing information can be used to determine how the user obtains a specific type of recognition device. For example, tourists holding ordinary day passes can apply for a standard wristband for free or purchase a customized wristband, while tourists holding special tickets, such as annual passes or package tickets, can apply for a standard wristband for free or a customized wristband.

[0032] Step S204: Bind the user identity of the identification device based on the device identifier submitted by the user terminal after interacting with the identification device.

[0033] In practice, after the service platform and the venue system work together to allocate identification devices to users, in order to ensure that subsequent service processing based on the identification devices can be accurately matched to the corresponding users, thereby ensuring the accuracy of service processing, the user identity of the identification device is bound according to the device identifier of the identification device.

[0034] In the specific execution process, after the identification device is assigned to the user, the identification device can perform near-field interaction with the user's terminal and send the device identifier to the user terminal through the established near-field communication connection. Subsequently, the user terminal submits the device identifier of the identification device to the service platform. Correspondingly, the service platform obtains the device identifier submitted by the user terminal after interacting with the identification device, and binds the user identity of the identification device according to the device identifier.

[0035] Step S206: The identification device is configured to obtain service configuration information at the tourist site, and the device identifier is synchronized with the site system.

[0036] In specific implementation, after binding the user identity of the identification device as described above, considering that different visitors may have different ticket types and / or identification device types, the service scope and / or service permissions corresponding to different ticket types and / or different device types of identification devices will also differ. In order to ensure that all interactive devices in the visitor site can respond to the service interaction of the identification device, the service configuration information of the identification device in the visitor site is obtained and the device identifier is synchronized to the site system.

[0037] The service configuration information refers to the information generated by the service platform after configuring services for the identified device within the visitor area. Specifically, the service configuration information may include account configuration information, scope configuration information, and / or permission configuration information. Among them, the scope configuration information may be information on the areas within the visitor area where the identified device can perform service interactions and / or the types of interactive devices in the locations where service interactions can be performed. The permission configuration information may be service rights information within the visitor area, such as access rights, consumption rights, and / or device usage rights.

[0038] In practical applications, after binding the user's identity to the identification device as described above, the user can make purchases at the tourist site based on the identification device. During the purchase process using the identification device, to accommodate different users' financial management preferences and improve payment efficiency, a prepaid card account or device fund account can be created for the identification device during service configuration, allowing users to make payments based on the device's prepaid card account or device fund account. In one optional implementation of this embodiment, obtaining service configuration information for the identification device at the tourist site includes: Create a prepaid card account for the identification device based on the prepaid card template of the tourist site, or create a device fund account for the identification device by calling the fund service interface; If an account top-up request is detected, funds will be transferred from the user's funds account and then transferred to the top-up card account or device funds account.

[0039] Among them, a prepaid card account refers to an account formed after a user deposits funds into a specific system or platform in advance. For example, a prepaid card account can be a prepaid account formed after depositing funds into a venue system in advance. An equipment fund account refers to a fund account that is bound to a unique equipment identifier of the identification device. For example, an equipment fund account can be associated with various user fund accounts such as the user's payment account, the venue's account, and the resource management account. After the user initiates a prepaid card request, the service platform verifies the transaction and transfers the funds from the user's fund account to the equipment fund account, so that the user can make payments within the venue based on the equipment fund account. Here, the equipment fund account can also be replaced by the equipment account.

[0040] Specifically, users can select an account type through the service program. Subsequently, the service platform creates a prepaid card account for the identification device based on the prepaid card template of the tourist venue, or calls the funds service interface to create a device funds account for the identification device, and associates and binds the prepaid card account or device funds account with the identification device. On this basis, if a user initiates an account top-up request for the prepaid card account or device funds account by accessing the service program, the service platform will transfer funds from the user's funds account based on the account top-up request and transfer the transferred funds to the prepaid card account or device funds account.

[0041] Here, in the process of accessing a prepaid card account or device funds account to top up the account, in addition to the above-mentioned implementation method of accessing the prepaid card account or device funds account through the user terminal access service program, the user can also access the prepaid card account or device funds account through near-field interaction. For example, the user terminal can access the device funds account or prepaid card account through near-field interaction with the identification device; if a submitted account top-up request is detected, funds are transferred out from the user account and transferred to the device funds account or prepaid card account.

[0042] Optionally, the device funds account in the service configuration information includes a group funds account; the group funds account is associated with the identification devices of multiple group members of the user group to which the user belongs.

[0043] For example, after a user completes the creation of a device funds account through the service program, if the user belongs to a user group, such as a family member in a family group, a group funds account can be created based on the user's group relationship. The created group funds account is not only bound to a single identification device, but during the service configuration process, it is associated with the identification devices held by multiple group members within the user group. Based on this, when any group member in the user group interacts with the venue interaction device based on their identification device and / or initiates a payment request, the deduction can be completed based on the group funds account.

[0044] In the specific implementation process, in order to improve the convenience of payment processing and the flexibility of service processing, in addition to the aforementioned provision of creating a pre-stored value card account or device fund account so that users can make payments based on the pre-stored value card account or device fund account, a user credit account can also be created for the identification device and a corresponding credit limit can be allocated; in an optional implementation of this embodiment, the service configuration information of the identification device in the tourist venue is obtained by: creating a user credit account for the identification device and allocating a credit limit to the user credit account to obtain a credit limit.

[0045] The credit limit is used to process payment requests made by the identification device through interaction with the venue's interactive device.

[0046] Specifically, in the process of allocating credit limits to user credit accounts, the service platform may allocate credit limits based on user data, or based on user data and venue data, or based on the user's service records at the venues visited and / or user data, user ticketing information, etc., such as based on the user's membership level; in addition to allocating credit limits to user credit accounts, the credit limit may also be a credit limit recommended to the user by the service platform after evaluation based on multi-dimensional data, so that the user determines the credit limit based on the recommended credit limit, or it may be the credit limit adjusted by the user within the range of the service platform's recommended credit limit, or it may be the credit limit determined by the user within a preset credit limit range based on the travel needs and / or travel preferences; this embodiment does not limit this.

[0047] In this embodiment, considering that users may have service interaction needs with interactive devices within the venue in addition to payment processing needs, in order to improve the convenience of users visiting venues based on the identification device, in addition to the account configuration of the identification device provided above, service scope configuration and / or service permission configuration can also be performed on the identification device for the venue; in an optional implementation of this embodiment, obtaining service configuration information for the identification device in the venue further includes: The service scope configuration information of the visitor site is obtained by configuring the service scope of the visitor site based on the device type of the identification device, and / or the permission configuration information is obtained by configuring the service permissions of the visitor site based on the device type of the identification device and the user's ticketing information.

[0048] The scope configuration information may be information on the areas within the visitor site where devices can perform service interactions and / or the types of interactive devices within the site that can perform service interactions; the permission configuration information may be information on service rights within the visitor site, such as access rights, consumption rights, and / or device usage rights for interactive devices; optionally, the scope configuration information and / or permission configuration information are synchronized to the site system and distributed to the corresponding interactive devices.

[0049] For example, during the service configuration of identification devices in tourist attractions, the service interaction range of the tourist attractions can be determined according to the device type of the identification device, and the range configuration information can be obtained. For example, the standard version of the wristband is only configured to interact with public areas and / or basic interactive devices in the attractions, while the IP customized version of the wristband can additionally open access to the corresponding IP exhibition area and / or limited interactive devices in the attractions; the task unlock version of the wristband can further add task-specific areas and / or interactive devices in the attractions that can sense tasks.

[0050] For example, during the service configuration of identification devices in tourist attractions, the configured permission information can be the service permissions of the identification devices, such as whether the identification devices are supported for payment processing or task interaction. The permission configuration information can also be the usage permissions of the interactive devices in the places that the identification devices interact with, such as whether the identification devices are supported for passing through fast-track gates or for picking up tour guide equipment.

[0051] In practical applications, considering that users may be visiting tourist attractions in groups such as families, it may be difficult to keep track of each other's locations in real time due to the dispersed nature of the members. Furthermore, tourist attractions are large and crowded, and the communication infrastructure deployed within them does not provide location services. In this case, in order to enable location queries for members of each group within a tourist attraction, a wireless connection can be established between the user terminal and the identification device of the group member. The communication data generated when the identification device interacts with the wireless components of the tourist attraction can then be used as the location basis. Optionally, the user terminal establishes a wireless connection with the identification devices of multiple group members, and uploads the communication and positioning information collected by the identification device of any group member through interaction with the wireless components deployed at the tour site to the service platform; accordingly, the service platform calculates the location of the member based on the uploaded communication and positioning information and returns it to the user terminal.

[0052] For example, the identification devices of each group member can establish a low-power wireless connection with the user terminal of the group management user through a BLE (Bluetooth Low Energy) module. After the wireless connection is established, the user terminal can record the unique device identifier and member information of each group member's identification device. Subsequently, as the group member's identification device moves within the tour area, it continuously interacts with the wireless components deployed in the tour area through the built-in BLE module, collects communication and location information in real time, and uploads it to the user terminal in real time through the established BLE wireless connection. Furthermore, the user terminal uploads the communication and location information of each group member's identification device to the service platform. The service platform performs location calculations based on the communication and location information to obtain the member's location for the corresponding group member and returns the member's location to the user terminal, so that the group management user can query the member's location based on the user terminal.

[0053] Furthermore, the above implementation can also be replaced by: multiple group member identification devices establishing wireless connections with the user terminal, and the user terminal uploading the communication location information collected by any of the multiple group member identification devices through interaction with the wireless components deployed at the tourist site to the service platform; specifically, if the user terminal receives a location request from any of the multiple group member identification devices, it obtains the communication location information collected by any of the identification devices through interaction with the wireless components deployed at the tourist site and uploads it to the service platform; correspondingly, after the service platform obtains the service configuration information for the identification devices at the tourist site, it also includes: calculating the member's location based on the communication location information and returning it to the user terminal.

[0054] It should be noted that the above-mentioned process for obtaining service configuration information for identification devices in tourist sites can be combined in any form according to actual execution or deployment needs, or a new process can be obtained by deleting any one or more operations in the combined process. For example, the service configuration information for the identification device in the tourist venue is obtained, including: creating a stored-value card account for the identification device based on the stored-value card template of the tourist venue; if a stored-value request is detected, funds are transferred out from the user's fund account and transferred to the stored-value card account; the service range configuration information for the tourist venue is obtained according to the device type of the identification device, wherein the range configuration information is synchronized to the venue system and sent to the corresponding venue interaction device; For example, configuring the services of the identification devices at tourist attractions to obtain service configuration information includes: calling the funds service interface to create a group funds account for the identification devices; if a deposit request is detected, transferring funds from the user's funds account and transferring the transferred funds to the group funds account; associating the group funds account with the identification devices of multiple group members of the user's user group; and configuring the service permissions of the tourist attractions based on the device type of the identification devices and the user's ticketing information to obtain permission configuration information; wherein, the permission configuration information is synchronized to the attraction system and distributed to the corresponding attraction interaction devices.

[0055] In specific implementation, after obtaining service configuration information for the identification device at the tourist site through the aforementioned service platform and synchronizing the device identifier with the site system, considering that the identification device serves as a unified service carrier for users within the tourist site and possesses near-field interaction capabilities, it can also respond to service interaction requests submitted by user terminals after the device identifier is synchronized to the site system; in an optional implementation provided in this embodiment, after synchronizing the device identifier with the site system, it further includes: If a service interaction request is received from a user terminal, the system will process the service interaction request and return the processing result to the user terminal.

[0056] Among them, the service interaction request is generated after the identification device and the interactive identification device of the visitor at the tourist site have a near-field interaction, or after the identification device and the interactive tag of the tourist site have a near-field interaction.

[0057] Specifically, after a user interacts with other users' interactive identification devices within the scenic area using the configured identification device, or interacts with interactive tags deployed within the scenic area, the identification device can generate a service interaction request and send it to the user terminal via an established wireless connection. Subsequently, after receiving the service interaction request from the identification device, the user terminal further submits a service interaction request to the service platform. Accordingly, the service platform processes the interaction response to the service interaction request and returns the response result to the user terminal.

[0058] In addition to the above-mentioned method of uploading service interaction requests to the service platform via user terminals, service requests can also be uploaded to the venue system and synchronized to the service platform via identification devices. Specifically, in this case, the service request is generated and submitted to the venue system after the identification device performs near-field interaction with the identification device of the visitor at the venue; or, the service request is generated and submitted to the venue system after the identification device performs near-field interaction with the task interaction tag of the visitor at the venue. Subsequently, the venue system receives the service interaction request sent by the identification device and further synchronizes it to the service platform.

[0059] In this context, considering that different types of identification devices correspond to different service functions and task interaction permissions, in order to achieve accurate matching between task interaction processing and identification device type, upon receiving a service interaction request submitted by a user terminal, task interaction permission verification can be performed based on the identification device type, and task interaction processing can be performed on identification devices that pass the verification. In one optional implementation of this embodiment, the interaction response processing of the service interaction request and the return of the response processing result to the user terminal include: Based on the device type of the identified device, the task interaction permission is verified. If the permission verification is successful, the task interaction request is processed based on the task interaction data of the visited site to obtain the task interaction result. Send the task interaction results to the user terminal so that the service program can display the task interaction based on the results.

[0060] Task interaction processing includes character interaction processing and / or task node interaction processing.

[0061] Specifically, when the service platform receives a service interaction request (task interaction request) submitted by a user terminal, it can determine the device type of the identification device based on the device identifier carried in the service interaction request, and verify the task interaction permission based on the device type. If the permission verification fails, it indicates that the identification device does not have the task interaction permission to perform task interaction processing, and no processing is required. If the permission verification passes, it indicates that the identification device has the task interaction permission to perform task interaction processing. In this case, the task interaction request is processed based on the task interaction data of the visited venue to obtain the task interaction result, and the task interaction result is sent to the user terminal so that the user terminal can perform task interaction display in the service program according to the task interaction result.

[0062] For example, the service platform can provide task interaction templates. Visitor areas can configure faction settings, task point layouts, story content for each task point, and / or interaction rules on the service platform based on these templates, and obtain the configured task interaction data. Subsequently, when a user interacts with a task point using a recognition device, the user terminal submits a task interaction request to the service platform. The platform then determines whether the recognition device is a task unlocking type. If so, the service platform can process the task interaction request based on the task interaction data configured by the visitor area according to the task interaction template, performing character interaction and / or task node interaction, generating task interaction results, and returning these results to the user terminal for display in the service program, such as indicating task completion, distributing virtual items, updating task factions, and / or updating task progress.

[0063] Step S208: If a service request carrying the device identifier is received, the service response is performed in cooperation with the venue system based on the service configuration information.

[0064] In practice, during the service processing, in order to ensure that the processing of various service requests is accurately matched with the configuration permissions of the identification devices, the service platform and the venue system work together to ensure the accuracy and efficiency of service request processing. After receiving a service request carrying a device identifier, the service platform, based on the service configuration information of the identification device, works with the venue system to process the service response.

[0065] In practice, after a user interacts with interactive devices within a visitor's area using an identification device, the interactive device generates a service request and submits it to the visitor's system. Upon receiving the service request, the system forwards it to a service platform, from which the platform obtains the service request carrying the device's identifier. Optionally, the service request is generated and submitted to the system after the identification device interacts with the interactive devices, and then sent by the system to the service platform.

[0066] The aforementioned site interaction device refers to a device deployed within a tourist site that interacts with the identification device of the tourist user. For example, the site interaction device may be a device that performs near-field interaction with the identification device. Optionally, the site interaction device includes: access interaction device, site interaction tag, site communication device, storage device, site traffic device and / or tour guidance device.

[0067] For example, access control devices may include access gates and access control systems; location interaction tags may include NFC tags, task tags, voice guide tags, popular photo check-in tags and / or other interactive tags.

[0068] In specific implementation, given the provision of different account modes to enable users to make payments within the venue using identification devices, considering the differences in resource sources and / or fund processing paths under different account modes, the service platform, upon receiving a payment service request, can cooperate with the venue system to perform corresponding payment processing based on the service configuration information corresponding to the identification device. In one optional implementation of this embodiment, service response processing based on service configuration information and cooperation with the venue system includes: The system processes payment service requests based on the stored-value card account, equipment fund account, or user credit account of the identification device, and synchronizes the payment processing results to the venue system to execute the service response operation for the payment service request.

[0069] Specifically, if the service platform receives a payment service request forwarded by the venue system, the service platform processes the payment request based on the prepaid card account, equipment funds account, or user credit account of the identification device. For example, the service platform can process the payment service request based on the prepaid card account, equipment funds account, or user credit account created by the identification device. Alternatively, if the identification device has multiple payment accounts among these, the service platform can retrieve the corresponding payment account according to a preset payment account priority for payment processing. The service platform can also perform a combined payment based on the prepaid card account, equipment funds account, and / or user credit account. Optionally, the payment funds processed based on the user credit account are obtained by transferring funds from the service platform's platform account.

[0070] Furthermore, in the specific execution process, besides the aforementioned service request being a payment service request, the service request forwarded by the venue system and received by the service platform can also be a service interaction request. In this case, service response processing can be performed based on the service interaction request, in cooperation with the venue system, and based on the service configuration information. Another optional implementation provided in this embodiment, performing service response processing based on the service configuration information and in cooperation with the venue system, includes: Service scope verification and service permission verification are performed on service interaction requests based on the scope configuration information and permission configuration information in the service configuration information. The venue system requests the corresponding venue interaction device to return the service scope verification result and service permission verification result in order to execute the service interaction response operation.

[0071] Specifically, if the service platform receives a service request forwarded by the venue system as a service interaction request, the service platform can obtain service configuration information matching the current service interaction request based on the service interaction request. Then, based on the scope and permission configuration information in the service configuration information, the service platform verifies the service scope and service permissions of the service interaction request. If both the service scope and service permissions verifications pass, the service platform returns a verification result to the venue system. Upon receiving the verification result, the venue system issues a service execution command to the corresponding venue interaction device that triggered the service interaction request, enabling the venue interaction device to perform the corresponding service operation based on the service execution. Conversely, if the service scope or service permissions verification fails, the service platform returns a verification result indicating failure to the venue system. Upon receiving the verification result, the venue system either issues a service rejection command to the corresponding venue interaction device that triggered the service interaction request or takes no further action.

[0072] For example, in a scenario where a visitor uses identification devices for storage, User A's identification device has a range configuration that includes storage services for the entire visitor area, and permission configuration information that includes storage permissions. When User A interacts with smart locker A in the vicinity of the visitor area, triggering a storage service interaction request, the venue system forwards the storage service interaction request to the service platform. The service platform verifies the service range and service permissions of the service interaction request based on the range configuration information and permission configuration information, and synchronizes the verification result to the venue system if the verification is successful. The venue system receives the verification result and issues an open command to smart locker A, allowing User A to store items in smart locker A.

[0073] It should be noted that the above-described implementation process for service response processing in cooperation with the venue system when the service request is a service interaction request can be executed in any of the following ways, depending on the actual execution or deployment needs. For example, service response processing based on service configuration information and cooperation with the venue system includes: verifying the service scope of the service interaction request based on the scope configuration information in the service configuration information; and returning the service scope verification result to the venue interaction device corresponding to the service interaction request through the venue system to execute the service interaction response operation. Another example is service response processing based on service configuration information and cooperation with the venue system, which includes: verifying the service permission of the service interaction request based on the permission configuration information in the service configuration information; and returning the service permission verification result to the venue interaction device corresponding to the service interaction request through the venue system to execute the service interaction response operation. Alternatively, both of the above processes can be executed as needed for actual execution or deployment.

[0074] Furthermore, it should be noted that the above-described implementation process for service response processing based on service configuration information and the venue system can be combined in any form according to actual execution or deployment needs, or a new implementation process can be obtained by deleting any one or more operations in the combined implementation process. For example, service response processing based on service configuration information and the venue system includes: if the service request is a payment service request, processing the payment service request based on the stored-value card account, device fund account, and / or user credit account of the identification device, and synchronizing the payment processing result to the venue system to execute the service response operation of the payment service request; if the service request is a service interaction request, verifying the service scope and / or service permission of the service interaction request based on the scope configuration information and / or permission configuration information in the service configuration information; and returning the service scope verification result and / or service permission verification result to the venue interaction device corresponding to the service interaction request through the venue system to execute the service interaction response operation. This embodiment does not limit this aspect.

[0075] It should be added that each optional implementation method and each feasible execution method in steps S202 to S208 provided in this embodiment can be executed independently as needed, or they can be combined and referenced with each other. At the same time, each specific execution step in each optional implementation method or each feasible execution method can also be executed independently or combined as needed. The execution conditions of "if" or "under what circumstances" involved in each step or operation can be directly deleted. This embodiment does not specifically limit the subsequent operations after the conditions are executed.

[0076] In summary, the service processing method based on identification devices provided in this embodiment involves the service platform obtaining user ticketing information synchronized from the venue system during service processing. The platform then verifies the user's identity based on this information. Upon successful verification, it collaborates with the venue system to assign identification devices to the user at the venue. Furthermore, to ensure accurate matching of subsequent service processing based on the identification devices to the corresponding users, the platform binds the user's identity to the identification device based on the device identifier submitted after interaction between the user terminal and the identification device. On this basis, to ensure that all interactive devices at the venue can respond to the service interactions of the identification devices, the service platform configures the identification devices at the venue to obtain service configuration information and synchronizes the device identifier with the venue system. Subsequently, if a service request carrying the device identifier is received, the platform collaborates with the venue system to process the service response based on the service configuration information. This approach, using identification devices as a carrier and the collaborative processing of the service platform and the venue system, improves the accuracy, convenience, and efficiency of service processing for users within the venue.

[0077] Steps S202 to S208 provided in this embodiment can be executed by the service platform. It should be noted that steps S202 to S208 executed by the service platform and steps S402 to S404 executed by the identification device in the following embodiment can cooperate with each other during execution. Therefore, when reading this embodiment, please refer to the corresponding content of steps S402 to S404 provided in the following method embodiment, and when reading the following method embodiment, please refer to the corresponding content of steps S202 to S208 provided in this embodiment.

[0078] The following example illustrates the application of a service processing method based on an identification device in a location tour scenario, combined with... Figure 3 The service processing method based on the identification device provided in this embodiment will be further explained below. Figure 3 The service processing method based on recognition devices, applied to site visit scenarios, specifically includes the following steps.

[0079] Step S302: Verify the identity of the visitor based on the user ticket information synchronized by the venue system. If the verification is successful, proceed to step S304 below.

[0080] Here, before step S302 is executed, the user terminal first scans the service identifier of the tourist attraction to access the service program. After the user accesses the ticketing page of the tourist attraction's service program and associates the ticket, the service program synchronizes the user's ticketing information with the attraction's system. The attraction's system receives the user's ticketing information synchronized by the service program and synchronizes the user's ticketing information to the service platform.

[0081] Step S304: Return the identity verification result to the venue system so that the venue system can issue an allocation instruction to the device management terminal, and the device management terminal can allocate identification devices to users according to the allocation instruction.

[0082] Step S308: Bind the user identity of the identification device based on the device identifier submitted after the user terminal interacts with the identification device.

[0083] Step S310: Create a stored-value card account for the identification device based on the stored-value card template of the tourist site.

[0084] Step S312: Based on the account value request submitted by the user terminal, transfer funds from the user's funds account and transfer the transferred funds to the value card account.

[0085] Step S314: Configure service permissions for the visitor site based on the device type of the identification device and the user's ticketing information to obtain permission configuration information.

[0086] Optionally, permission configuration information is synchronized to the venue system and distributed to the corresponding venue interaction devices.

[0087] Step S316: Synchronize device identifiers with the venue system.

[0088] Step S320: If a service interaction request carrying a device identifier is received, the service permission of the service interaction request is verified based on the permission configuration information in the service configuration information.

[0089] Step S322: The venue system requests the corresponding venue interaction device to return the service permission verification result in order to execute the service interaction.

[0090] It should be noted that any one or more steps in steps S302 to S304, S308 to S316, and S320 to S322 can be combined with any one or more steps in steps S202 to S208 to form a new implementation method according to the needs of implementation and deployment; in addition, any one of steps in steps S302 to S304, S308 to S316, and S320 to S322 can be selected according to the actual deployment needs. One or more technical features can be combined with one or more technical features provided in steps S202 to S208 to form a new implementation method; or, any one or more technical features in steps S302 to S304, S308 to S316 and S320 to S322 can be replaced with any one or more technical features provided in steps S202 to S208 to form a new implementation method according to the actual deployment needs, which will not be elaborated here.

[0091] Furthermore, it should be noted that steps S302 to S304, S308 to S316, and S320 to S322 provided in this embodiment can be executed by the service platform. It should be noted that the steps S302 to S304, S308 to S316, and S320 to S322 executed by the access platform can cooperate with steps S306 and S318 executed by the identification device in the following embodiment during execution. Therefore, when reading this embodiment, please refer to the corresponding content of steps S306 and S318 provided in the following method embodiment, and when reading the following method embodiment, please refer to the corresponding content of steps S302 to S304, S308 to S316, and S320 to S322 provided in this embodiment.

[0092] One or more embodiments of another service processing method based on identification devices provided in this specification are as follows: Reference Figure 4 The service processing method based on the identification device provided in this embodiment can be applied to the identification device. The method specifically includes steps S402 to S404.

[0093] Step S402: Perform near-field interaction with the user terminal and send the device identifier to the user terminal to bind the user identity of the identification device and configure the location service.

[0094] The identification device described in this embodiment refers to a wearable device with a unique device identifier. The identification device can communicate with external systems through near field communication technology to achieve identity recognition, data interaction, and / or service triggering. For example, the identification device can be a smart bracelet that integrates an NFC (Near Field Communication) module or deploys an NFC chip. Specifically, the identification device can interact with venue interaction devices, such as access gates, POS terminals, and / or interactive terminals deployed in the tourist area. The identification device can also interact with venue interaction tags, such as near field communication tags deployed in the tourist area. Alternatively, the identification device can also interact with the identification devices of other tourists.

[0095] Among them, tourist attractions include places where users visit, tour, or consume services, such as scenic spots, theme parks, museums, and cultural blocks. The attraction system can interact with the service platform, interactive devices within the attraction, and user terminals. Specifically, the attraction system can be used to receive, store, and / or process user ticketing information, manage the allocation of identification devices, and synchronize service configuration information of the attraction. In addition, the attraction system can also be used to send service configuration information to interactive devices within the attraction, such as to access gates and POS terminals, to support subsequent service interactions based on identification devices.

[0096] In practice, considering that users need to purchase or reserve tickets for the venue before entering the venue, and that user ticket information needs to be associated before subsequent user identity verification and identification device allocation, users can process tickets and / or associate user ticket information through the service program. Specifically, during the process of users accessing service programs, users can scan service identifiers at the venue using their user terminals. For example, service identifiers can be deployed in offline service areas such as ticket offices and entrances of the venue. These identifiers can embed access entry parsing information for the service programs. After scanning the service identifier, the user terminal can jump to and launch the venue's service program based on the parsed access link, thus enabling the user to access the service program. Alternatively, users can also access services based on service access information read from the venue's near-field communication (NFC) components. For example, NFC components can be deployed in the offline service areas of the venue. After the user terminal establishes a NFC connection with the NFC component, the NFC component transmits service access information to the user terminal through the NFC connection. The user terminal receives and parses the service access information, and launches and enters the venue's service program based on the service access information, thus enabling the user to access the service program. Optionally, the service program can access the site by scanning the service identifier of the site with the user terminal, or by reading service access information from the near-field communication component of the site with the user terminal.

[0097] In this context, a service application refers to an application deployed on a terminal device that has data collection and / or data interaction functions. For example, a service application can be an application used for ticketing processing. A service application can be an independent third-party application, such as a ticketing service application or a browsing service application. In addition, a service application can also be a functional module or subroutine deployed within an application. Subroutines include program functional modules or application components mounted on the host application (application), or program functional modules or application components loaded and installed by the host application, such as mini-programs within a payment application. From a service perspective, subroutines mounted on an application have the ability to independently provide self-closing services, such as mini-programs running within a payment application that provide self-closing ticketing processing services.

[0098] Furthermore, after accessing the service program through any of the above methods, the user can associate tickets through the ticketing page of the service program; subsequently, after the user associates tickets, the venue system of the visited venue can receive the user's ticketing information synchronized by the service program, and further synchronize the user's ticketing information to the service platform; optionally, the user's ticketing information is synchronized after the user accesses the ticketing page of the service program of the visited venue and associates tickets.

[0099] Here, in addition to the above-mentioned methods for users to access the service program and then access the ticketing page, users can also access the ticketing page by scanning the service identifier with their user terminal, or by reading service access information from the near-field communication component of the tourist attraction using their user terminal. Based on this, the ticketing page of the service program is accessed by scanning the service identifier of the tourist attraction with the user terminal, or by reading service access information from the near-field communication component of the tourist attraction using the user terminal.

[0100] In practice, based on the synchronization of user ticketing information from the venue system to the service platform, in order to achieve effective association between the identification device and the user ticketing information and improve the management of identification devices and service resources, the service platform, after obtaining the user ticketing information synchronized from the venue system, performs identity verification on the user based on the user ticketing information of the venue visited. This includes verification of authenticity, validity, and / or matching. If the verification is successful, the venue system can allocate identification devices to the user at the venue visited; if the verification fails, a failure notification can be returned to the user's terminal or no action can be taken.

[0101] In the specific implementation process, in order to achieve efficient allocation of identification devices, the allocation of identification devices can be carried out through near-field interaction between the user terminal and the equipment management terminal of the tourist site. In an optional implementation method provided in this embodiment, the identification devices are allocated in the following way: The system obtains user information through near-field interaction between the equipment management terminal and the user terminal at the venue and submits it to the venue system. The venue system verifies the equipment application or user ticket based on the user information, and after the verification is passed, it issues an allocation instruction to the equipment management terminal so that the equipment management terminal can allocate identification equipment to the user according to the allocation instruction.

[0102] Specifically, during the application process for identification devices, users can submit their applications online in advance. In this case, the venue system verifies the application based on the user information. Alternatively, users can apply for identification devices on-site at the venue without prior online submission. In this case, the venue system verifies the user's ticket information. During the allocation of identification devices, users can bring their terminals close to the device management terminal deployed at the venue. After establishing a near-field communication connection between the device management terminal and the user terminal, the device management terminal can interact with the user to obtain user information and submit it to the venue system. Upon receiving the user information, the venue system verifies either the application or the ticket. If the verification is successful, the venue system issues an allocation instruction to the device management terminal, which then allocates the identification device to the user. Optionally, the allocated identification device belongs to the user.

[0103] Specifically, the device application verification includes verifying whether a user's device application record exists. If so, the device application verification is confirmed to be successful; otherwise, the device application verification is confirmed to be unsuccessful. Optionally, the device application record is generated after the user submits a device application through the device application portal on the ticketing page of the service program, or after purchasing the device through the ticketing page.

[0104] In addition to the above-mentioned method of allocating identification devices through the venue system and the equipment management terminal of the tourist venue, there may also be situations where the tourist venue is not equipped with an equipment management terminal. In this case, identification devices can also be allocated through the venue management user. Specifically, the management user of the tourist venue obtains user information through near-field interaction with the user terminal and submits it to the venue system. The venue system verifies the device application or user ticket based on the user information, and sends an allocation confirmation prompt to the management terminal after the verification is passed, so that the management user can allocate identification devices to the user according to the allocation confirmation prompt.

[0105] In addition to the above, during the allocation of identification devices, besides the venue system verifying device applications or user tickets based on user information, the service platform can also verify identity based on user ticket information. In this case, if the verification is successful, the service platform can synchronize the verification result to the venue system. Accordingly, the venue system sends an allocation instruction to the device management terminal, so that the device management terminal can allocate identification devices to users according to the allocation instruction. Optionally, identification devices can be allocated to users after successful identity verification based on user ticket information.

[0106] In practical applications, considering users' personalized needs for identification devices, such as differentiated needs for the appearance, markings and / or functional attributes of identification devices, in this embodiment, after purchasing or applying for the device through the service program, users can configure the materials for the identification device. Correspondingly, the material configuration information generated after the user configures the materials can be used to manufacture the identification device for shipment. Optionally, the identification device obtains its manufacturing process by producing the equipment materials based on the user's material configuration information; the material configuration information is generated after the user purchases or applies for the equipment and configures the materials through the service program.

[0107] Material configuration information refers to the information used to manufacture the equipment materials for the identification equipment, including but not limited to the equipment color, equipment pattern, engraved text and / or customized elements of the identification equipment.

[0108] Furthermore, after the service platform and venue system work together to allocate identification devices to users, in order to ensure that subsequent service processing based on the identification devices can be accurately matched to the corresponding users, thereby ensuring the accuracy of service processing, the service platform can bind the user identity of the identification device according to the device identifier of the identification device.

[0109] Furthermore, after binding the user identity of the identification device, considering that different visitors may have different ticket types and / or identification device types, the service scope and / or service permissions corresponding to different ticket types and / or different device types of identification devices will also differ. In order to ensure that all interactive devices in the visitor area can respond to the service interaction of the identification device, the service platform can further configure the identification device in the visitor area to obtain service configuration information and synchronize the device identifier with the venue system.

[0110] The service configuration information refers to the information generated by the service platform after configuring services for the identified device within the visitor area. Specifically, the service configuration information may include account configuration information, scope configuration information, and / or permission configuration information. Among them, the scope configuration information may be information on the areas within the visitor area where the identified device can perform service interactions and / or the types of interactive devices in the locations where service interactions can be performed. The permission configuration information may be service rights information within the visitor area, such as access rights, consumption rights, and / or device usage rights.

[0111] In practical applications, after binding the user's identity to the identification device as described above, the user can make purchases at the tourist site based on the identification device. During the purchase process using the identification device, to accommodate different users' financial management preferences and improve payment efficiency, a prepaid card account or device fund account can be created for the identification device during service configuration, allowing users to make payments based on the device's prepaid card account or device fund account. In one optional implementation of this embodiment, obtaining service configuration information for the identification device at the tourist site includes: Create a prepaid card account for the identification device based on the prepaid card template of the tourist site, or create a device fund account for the identification device by calling the fund service interface; If an account top-up request is detected, funds will be transferred from the user's funds account and then transferred to the top-up card account or device funds account.

[0112] Among them, a prepaid card account refers to an account formed after a user deposits funds into a specific system or platform in advance. For example, a prepaid card account can be a prepaid account formed after depositing funds into a venue system in advance. An equipment fund account refers to a fund account that is bound to a unique equipment identifier of the identification device. For example, an equipment fund account can be associated with various user fund accounts such as the user's payment account, the venue's account, and the resource management account. After the user initiates a prepaid card request, the service platform verifies the transaction and transfers the funds from the user's fund account to the equipment fund account, so that the user can make payments within the venue based on the equipment fund account. Here, the equipment fund account can also be replaced by the equipment account.

[0113] Specifically, users can select an account type through the service program. Subsequently, the service platform creates a prepaid card account for the identification device based on the prepaid card template of the tourist venue, or calls the funds service interface to create a device funds account for the identification device, and associates and binds the prepaid card account or device funds account with the identification device. On this basis, if a user initiates an account top-up request for the prepaid card account or device funds account by accessing the service program, the service platform will transfer funds from the user's funds account based on the account top-up request and transfer the transferred funds to the prepaid card account or device funds account.

[0114] Here, in the process of accessing a prepaid card account or device funds account to top up the account, in addition to the above-mentioned implementation method of accessing the prepaid card account or device funds account through the user terminal access service program, the user can also access the prepaid card account or device funds account through near-field interaction. For example, the user terminal can access the device funds account or prepaid card account through near-field interaction with the identification device; if a submitted account top-up request is detected, funds are transferred out from the user account and transferred to the device funds account or prepaid card account.

[0115] Optionally, the device funds account in the service configuration information includes a group funds account; the group funds account is associated with the identification devices of multiple group members of the user group to which the user belongs.

[0116] In the specific implementation process, in order to improve the convenience of payment processing and the flexibility of service processing, in addition to the aforementioned provision of creating a pre-stored value card account or device fund account so that users can make payments based on the pre-stored value card account or device fund account, a user credit account can also be created for the identification device and a corresponding credit limit can be allocated; in an optional implementation of this embodiment, the service configuration information of the identification device in the tourist venue is obtained by: creating a user credit account for the identification device and allocating a credit limit to the user credit account to obtain a credit limit.

[0117] The credit limit is used to process payment requests made by the identification device through interaction with the venue's interactive device.

[0118] Specifically, in the process of allocating credit limits to user credit accounts, the service platform may allocate credit limits based on user data, or based on user data and venue data, or based on the user's service records at the venues visited and / or user data, user ticketing information, etc., such as based on the user's membership level. In addition, besides allocating credit limits to user credit accounts, the credit limit may also be a credit limit recommended to the user by the service platform after evaluation based on multi-dimensional data, so that the user determines the credit limit based on the recommended credit limit, or it may be the credit limit adjusted by the user within the range of the service platform's recommended credit limit, or it may be the credit limit determined by the user within a preset range based on their travel needs and / or travel preferences; this embodiment does not limit this.

[0119] In this embodiment, considering that users may have service interaction needs with interactive devices within the venue in addition to payment processing needs, in order to improve the convenience of users visiting venues based on the identification device, in addition to the account configuration of the identification device provided above, service scope configuration and / or service permission configuration can also be performed on the identification device for the venue; in an optional implementation of this embodiment, obtaining service configuration information for the identification device in the venue further includes: The service scope configuration information of the visitor site is obtained by configuring the service scope of the visitor site based on the device type of the identification device, and / or the permission configuration information is obtained by configuring the service permissions of the visitor site based on the device type of the identification device and the user's ticketing information.

[0120] The scope configuration information may be information on the areas within the visitor site where devices can perform service interactions and / or the types of interactive devices within the site that can perform service interactions; the permission configuration information may be information on service rights within the visitor site, such as access rights, consumption rights, and / or device usage rights for interactive devices; optionally, the scope configuration information and / or permission configuration information are synchronized to the site system and distributed to the corresponding interactive devices.

[0121] In practical applications, considering that when users visit tourist attractions in groups such as families, it may be difficult to keep track of each other's locations in real time due to the dispersed nature of the members, and that tourist attractions are large and crowded, and that the communication infrastructure deployed within the tourist attractions does not provide location services, in order to enable the location query of each group member in the tourist attraction, a wireless connection can be established between the user terminal and the identification device of the group member, and the communication data generated when the identification device interacts with the wireless components of the tourist attraction can be used as the location basis. Optionally, the user terminal establishes a wireless connection with the identification devices of multiple group members, and uploads the communication and positioning information collected by the identification device of any group member through interaction with the wireless components deployed at the tour site to the service platform; accordingly, the service platform calculates the location of the member based on the uploaded communication and positioning information and returns it to the user terminal.

[0122] It should be noted that the above-described process for obtaining service configuration information for identification devices in tourist attractions can be combined in any form according to actual execution or deployment needs, or a new process can be obtained by deleting any one or more operations in the combined process. For example, obtaining service configuration information for identification devices in tourist attractions includes: creating a stored-value card account for the identification device based on the stored-value card template of the tourist attraction; if a stored-value request is detected, transferring funds from the user's fund account and transferring the transferred funds to the stored-value card account; and configuring the service scope of the tourist attraction according to the device type of the identification device to obtain scope configuration information, wherein the scope configuration information is synchronized to the venue system and sent to the corresponding venue interaction device.

[0123] In a specific implementation, after performing near-field interaction with the user terminal and sending the device identifier to the user terminal as described above, in an optional implementation of this embodiment, after performing near-field interaction with the user terminal and sending the device identifier to the user terminal, the method further includes: The interaction information of the tags can be read through near-field interaction with the interactive tags of the tourist site, or the interaction information of the devices can be read through near-field interaction with the identification devices of the tourists at the tourist site. Send tag interaction information or device interaction information to the user terminal so that the user terminal can upload the corresponding service interaction request to the service platform and display the service interaction based on the interaction response result returned by the service platform.

[0124] Specifically, when a user uses the configured identification device within the tourist area to perform near-field interaction with the identification devices of other tourists within the area, or with the interactive tags deployed within the area, the identification device can generate a service interaction request and send it to the user terminal via an established wireless connection. Subsequently, after receiving the service interaction request from the identification device, the user terminal further submits a service interaction request to the service platform. Accordingly, the service platform processes the interaction response to the service interaction request and returns the response result to the user terminal.

[0125] In this context, considering that different types of identification devices correspond to different service functions and task interaction permissions, in order to achieve accurate matching between task interaction processing and identification device type, upon receiving a service interaction request submitted by a user terminal, task interaction permission verification can be performed based on the identification device type, and task interaction processing can be performed on identification devices that pass the verification; in an optional implementation provided in this embodiment, it further includes: Based on the device type of the identified device, the task interaction permission is verified. If the permission verification is successful, the task interaction request is processed based on the task interaction data of the visited site to obtain the task interaction result. Send the task interaction results to the user terminal so that the service program can display the task interaction based on the results.

[0126] Task interaction processing includes character interaction processing and / or task node interaction processing.

[0127] Specifically, when the service platform receives a service interaction request (task interaction request) submitted by a user terminal, it can determine the device type of the identification device based on the device identifier carried in the service interaction request, and verify the task interaction permission based on the device type. If the permission verification fails, it indicates that the identification device does not have the task interaction permission to perform task interaction processing, and no processing is required. If the permission verification passes, it indicates that the identification device has the task interaction permission to perform task interaction processing. In this case, the task interaction request is processed based on the task interaction data of the visited venue to obtain the task interaction result, and the task interaction result is sent to the user terminal so that the user terminal can perform task interaction display in the service program according to the task interaction result.

[0128] Step S404: Interact with the interactive device of the visitor site and transmit the device identifier, so as to upload the device identifier to the site system and synchronize it with the service platform through the interactive device.

[0129] In practice, during the service processing, in order to ensure that the processing of various service requests is accurately matched with the configuration permissions of the identification devices, the service platform and the venue system work together to ensure the accuracy and efficiency of service request processing. The identification devices interact with the venue interaction devices and transmit device identifiers. The venue interaction devices upload the device identifiers to the venue system and synchronize them with the service platform. After the service platform receives a service request carrying the device identifier, the service platform works with the venue system to process the service response based on the service configuration information of the identification devices.

[0130] Optionally, the service platform can use the service configuration information obtained from the venue service configuration to cooperate with the venue system to process service responses.

[0131] In practice, after a user interacts with interactive devices within a visitor's area using an identification device, the interactive device generates a service request and submits it to the visitor's system. Upon receiving the service request, the system forwards it to a service platform, from which the platform obtains the service request carrying the device's identifier. Optionally, the service request is generated and submitted to the system after the identification device interacts with the interactive devices, and then sent by the system to the service platform.

[0132] The aforementioned site interaction device refers to a device deployed within a tourist site that interacts with the identification device of the tourist user. For example, the site interaction device may be a device that performs near-field interaction with the identification device. Optionally, the site interaction device includes: access interaction device, site interaction tag, site communication device, storage device, site traffic device and / or tour guidance device.

[0133] In specific implementation, given the provision of different account modes to enable users to make payments within the venue using identification devices, considering the differences in resource sources and / or fund processing paths under different account modes, the service platform, upon receiving a payment service request, can cooperate with the venue system to perform corresponding payment processing based on the service configuration information corresponding to the identification device. In one optional implementation of this embodiment, service response processing based on service configuration information and cooperation with the venue system includes: The system processes payment service requests based on the stored-value card account, equipment fund account, or user credit account of the identification device, and synchronizes the payment processing results to the venue system to execute the service response operation for the payment service request.

[0134] Specifically, if the service platform receives a payment service request forwarded by the venue system, the service platform processes the payment request based on the prepaid card account, equipment funds account, or user credit account of the identification device. For example, the service platform can process the payment service request based on the prepaid card account, equipment funds account, or user credit account created by the identification device. Alternatively, if the identification device has multiple payment accounts among these, the service platform can retrieve the corresponding payment account according to a preset payment account priority for payment processing. The service platform can also perform a combined payment based on the prepaid card account, equipment funds account, and / or user credit account. Optionally, the payment funds processed based on the user credit account are obtained by transferring funds from the service platform's platform account.

[0135] Furthermore, in the specific execution process, besides the aforementioned service request being a payment service request, the service request forwarded by the venue system and received by the service platform can also be a service interaction request. In this case, service response processing can be performed based on the service interaction request, in cooperation with the venue system, and based on the service configuration information. Another optional implementation provided in this embodiment, performing service response processing based on the service configuration information and in cooperation with the venue system, includes: Service scope verification and service permission verification are performed on service interaction requests based on the scope configuration information and permission configuration information in the service configuration information. The venue system requests the corresponding venue interaction device to return the service scope verification result and service permission verification result in order to execute the service interaction response operation.

[0136] Specifically, if the service platform receives a service request forwarded by the venue system as a service interaction request, the service platform can obtain service configuration information matching the current service interaction request based on the service interaction request. Then, based on the scope and permission configuration information in the service configuration information, the service platform verifies the service scope and service permissions of the service interaction request. If both the service scope and service permissions verifications pass, the service platform returns a verification result to the venue system. Upon receiving the verification result, the venue system issues a service execution command to the corresponding venue interaction device that triggered the service interaction request, enabling the venue interaction device to perform the corresponding service operation based on the service execution. Conversely, if the service scope or service permissions verification fails, the service platform returns a verification result indicating failure to the venue system. Upon receiving the verification result, the venue system either issues a service rejection command to the corresponding venue interaction device that triggered the service interaction request or takes no further action.

[0137] It should be noted that the above-described implementation process for service response processing based on service configuration information and the venue system can be combined in any form according to actual execution or deployment needs, or a new implementation process can be obtained by deleting any one or more operations in the combined implementation process. For example, service response processing based on service configuration information and the venue system includes: if the service request is a payment service request, processing the payment service request based on the stored-value card account, device fund account, and / or user credit account of the identification device, and synchronizing the payment processing result to the venue system to execute the service response operation of the payment service request; if the service request is a service interaction request, verifying the service scope and / or service permission of the service interaction request based on the scope configuration information and / or permission configuration information in the service configuration information; and returning the service scope verification result and / or service permission verification result to the venue interaction device corresponding to the service interaction request through the venue system to execute the service interaction response operation. This embodiment does not limit this aspect.

[0138] In summary, the service processing method based on identification devices provided in this embodiment involves the service platform obtaining user ticketing information synchronized from the venue system during service processing. The platform then verifies the user's identity based on this information. Upon successful verification, it collaborates with the venue system to assign identification devices to the user at the venue. Furthermore, to ensure accurate matching of subsequent service processing based on the identification devices to the corresponding users, the platform binds the user's identity to the identification device based on the device identifier submitted after interaction between the user terminal and the identification device. On this basis, to ensure that all interactive devices at the venue can respond to the service interactions of the identification devices, the service platform configures the identification devices at the venue to obtain service configuration information and synchronizes the device identifier with the venue system. Subsequently, if a service request carrying the device identifier is received, the platform collaborates with the venue system to process the service response based on the service configuration information. This approach, using identification devices as a carrier and the collaborative processing of the service platform and the venue system, improves the accuracy, convenience, and efficiency of service processing for users within the venue.

[0139] The following example illustrates the application of a service processing method based on an identification device in a location tour scenario, combined with... Figure 3 The service processing method based on the identification device provided in this embodiment will be further explained below. Figure 3 The service processing method based on recognition devices, applied to site visit scenarios, specifically includes the following steps.

[0140] Step S306: Perform near-field interaction with the user terminal and send the device identifier to the user terminal.

[0141] After step S306 is executed, the user terminal obtains the device identifier submitted by the identification device after performing near-field interaction, and sends the device identifier to the service platform.

[0142] Step S318: Interact with the interactive devices at the visitor site and transmit device identifiers to upload the device identifiers to the site system and synchronize them with the service platform via the interactive devices.

[0143] It should be noted that any one or more steps in steps S306 and S318 can be combined with any one or more steps in steps S402 to S404 to form a new implementation method according to the needs of implementation and deployment. In addition, any one or more technical features in steps S306 and S318 can be selected and combined with any one or more technical features provided in steps S402 to S404 to form a new implementation method according to the actual deployment needs. Alternatively, any one or more technical features in steps S306 and S318 can be replaced with any one or more technical features provided in steps S402 to S404 to form a new implementation method according to the actual deployment needs. These will not be elaborated on here.

[0144] This specification provides an embodiment of a service processing device based on an identification device, as follows: In the above embodiments, a service processing method based on an identification device is provided, and correspondingly, a service processing apparatus based on an identification device is also provided, which will be described below with reference to the accompanying drawings.

[0145] Reference Figure 5 This illustration shows a schematic diagram of an embodiment of a service processing device based on an identification device provided in this embodiment.

[0146] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0147] This embodiment provides a service processing device based on an identification device, which runs on a service platform. The device includes: The identity verification module 502 is configured to verify the identity of the user based on the user ticketing information of the visit site synchronized by the site system, so as to allocate an identification device to the user at the visit site after successful verification; The identity binding module 504 is configured to bind the user identity of the identification device based on the device identifier submitted after the user terminal interacts with the identification device. Service configuration module 506 is configured to obtain service configuration information for the identification device in the tourist site and synchronize the device identifier to the site system; The response processing module 508 is configured to, upon receiving a service request carrying the device identifier, cooperate with the venue system to perform service response processing based on the service configuration information.

[0148] For ease of description, the above devices are described by dividing them into various modules or units based on their functions. Of course, when implementing one or more of these specifications, the functions of each module or unit can be implemented in the same or different software and / or hardware, or a module that performs the same function can be implemented by a combination of multiple sub-modules or sub-units, etc. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0149] Another embodiment of a service processing device based on an identification device provided in this specification is as follows: In the above embodiments, another service processing method based on an identification device is provided, and correspondingly, another service processing apparatus based on an identification device is also provided, which will be described below with reference to the accompanying drawings.

[0150] Reference Figure 6 This illustration shows a schematic diagram of an embodiment of a service processing device based on an identification device provided in this embodiment.

[0151] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0152] This embodiment provides a service processing device based on an identification device, which operates on the identification device. The device includes: The near-field interaction module 602 is configured to perform near-field interaction with the user terminal and send a device identifier to the user terminal to bind the user identity of the identification device and configure the venue service; the identification device is allocated to the user after successful identity verification based on the user's ticket information; The identifier transmission module 604 is configured to interact with the interactive devices of the tourist site and transmit the device identifier, so as to upload the device identifier to the site system and synchronize it with the service platform through the interactive devices; the service platform cooperates with the site system to perform service response processing based on the service configuration information obtained by the site service configuration.

[0153] For ease of description, the above devices are described by dividing them into various modules or units based on their functions. Of course, when implementing one or more of these specifications, the functions of each module or unit can be implemented in the same or different software and / or hardware, or a module that performs the same function can be implemented by a combination of multiple sub-modules or sub-units, etc. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0154] This specification provides an example of a service processing device based on an identification device, as follows: Corresponding to the service processing method based on an identification device described above, and based on the same technical concept, one or more embodiments of this specification also provide a service processing device based on an identification device, which is used to execute the service processing method based on an identification device provided above. Figure 7 This is a schematic diagram of the structure of a service processing device based on an identification device, provided for one or more embodiments of this specification.

[0155] This embodiment provides a service processing device based on an identification device, including: like Figure 7As shown, device 700 mainly consists of a communication interface 702, a user interface 704, a processor 706, and a data storage 708. These components are interconnected and communicate with each other via a system bus, network, or other connection mechanism 710. Communication interface 702 enables device 700 to communicate with other devices, access networks, and transmission networks via analog or digital modulation. For example, communication interface 702 may include a chipset and antenna for wireless communication with a radio access network or access point. Furthermore, communication interface 702 can be a wired interface such as Ethernet, Token Ring, or USB port, or a wireless interface such as Wi-Fi, Bluetooth, Global Positioning System (GPS), or wide area wireless interface (e.g., WiMAX or LTE). Of course, communication interface 702 can also support other forms of physical layer interfaces and standard or proprietary communication protocols. Communication interface 702 may also include multiple physical communication interfaces, such as Wi-Fi, Bluetooth, and wide area wireless interfaces. User interface 704 includes receiving user input and providing output to the user. Therefore, user interface 704 may include input components such as a keypad, keyboard, touch-sensitive or presence-sensitive panel, computer mouse, trackball, joystick, microphone, still camera, and video camera, and output components such as a display screen (which may be combined with a touch-sensitive panel), CRT, LCD, LED, display using DLP technology, printer, and other similar devices known or developed in the future. User interface 704 may also generate auditory output via speakers, speaker jacks, audio output ports, audio output devices, headphones, and other similar devices known or developed in the future. In some embodiments, user interface 704 may include software, circuitry, or other forms of logic capable of transmitting data to and receiving data from external user input / output devices. Additionally or alternatively, device 700 may support remote access from other devices via communication interface 702 or another physical interface (not shown). User interface 704 may be configured to receive user input, the position and movement of which may be indicated by indicators or cursors described herein. User interface 704 may also be configured as a display device for rendering or displaying text fragments.

[0156] Processor 706 may include one or more general-purpose processors and / or special-purpose processors. Data storage 708 may include one or more volatile and / or non-volatile storage components, and may be integrated wholly or partially with processor 706. Data storage 708 may include removable and non-removable components.

[0157] Processor 706 is capable of executing program instructions 718 (e.g., compiled or uncompiled program logic and / or machine code) stored in data storage 708 to perform the various functions described herein. Data storage 708 may comprise a non-transitory computer-readable medium on which program instructions are stored, which, when executed by device 700, enable device 700 to perform any methods, processes, or functions disclosed in this specification and / or the accompanying drawings. Execution of program instructions 718 by processor 706 may result in processor 706 using data 712. For example, program instructions 718 may include an operating system 722 (e.g., an operating system kernel, device drivers, and / or other modules) installed on device 700 and one or more application programs 720 (e.g., a browser, social application, or game application). Similarly, data 712 may include operating system data 716 and application data 714. Operating system data 716 is primarily accessible to operating system 722, while application data 714 is primarily accessible to one or more application programs 720. Application data 714 may reside in a file system visible or hidden from the user of device 700. Application 720 can communicate with operating system 722 through one or more application programming interfaces (APIs). These APIs facilitate application 720 in reading and / or writing application data 714, transmitting or receiving information via communication interface 702, and receiving or displaying information on user interface 704. In some terms, application 720 may be simply referred to as "app". Furthermore, application 720 can be downloaded to device 700 through one or more online app stores or app markets. However, applications can also be installed on device 700 in other ways, such as through a web browser or a physical interface on device 700 (e.g., a USB port).

[0158] In one specific embodiment, the service processing device based on the identification device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the service processing device based on the identification device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following: Identity verification is performed based on the user's ticketing information synchronized with the venue system, and an identification device is assigned to the user at the venue after successful verification. Based on the device identifier submitted by the user terminal after interacting with the identification device, the user identity of the identification device is bound; The identification device obtains service configuration information from the service configuration of the tourist site and synchronizes the device identifier with the site system. If a service request carrying the device identifier is received, the system will cooperate with the venue system to perform service response processing based on the service configuration information.

[0159] Another embodiment of a service processing device based on an identification device provided in this specification is as follows: Corresponding to the other service processing method based on an identification device described above, and based on the same technical concept, one or more embodiments of this specification also provide another service processing device based on an identification device, which is used to execute the other service processing method based on an identification device provided above. Figure 8 This is a schematic diagram of the structure of another service processing device based on an identification device provided in one or more embodiments of this specification.

[0160] This embodiment provides a service processing device based on an identification device, including: like Figure 8As shown, device 800 mainly consists of a communication interface 802, a user interface 804, a processor 806, and a data storage 808. These components are interconnected and communicate with each other via a system bus, network, or other connection mechanism 810. The communication interface 802 enables device 800 to communicate with other devices, access networks, and transmission networks via analog or digital modulation. For example, the communication interface 802 may include a chipset and antenna for wireless communication with a radio access network or access point. Furthermore, the communication interface 802 can be a wired interface such as Ethernet, Token Ring, or a USB port, or a wireless interface such as Wi-Fi, Bluetooth, Global Positioning System (GPS), or a wide-area wireless interface (e.g., WiMAX or LTE). Of course, the communication interface 802 can also support other forms of physical layer interfaces and standard or proprietary communication protocols. The communication interface 802 may also include multiple physical communication interfaces, such as Wi-Fi, Bluetooth, and wide-area wireless interfaces. The user interface 804 includes receiving user input and providing output to the user. Therefore, user interface 804 may include input components such as a keypad, keyboard, touch-sensitive or presence-sensitive panel, computer mouse, trackball, joystick, microphone, still camera, and video camera, and output components such as a display screen (which may be combined with a touch-sensitive panel), CRT, LCD, LED, display using DLP technology, printer, and other similar devices known or developed in the future. User interface 804 may also generate auditory output via speakers, speaker jacks, audio output ports, audio output devices, headphones, and other similar devices known or developed in the future. In some embodiments, user interface 804 may include software, circuitry, or other forms of logic capable of transmitting and receiving data to and from external user input / output devices. Additionally or alternatively, device 800 may support remote access from other devices via communication interface 802 or another physical interface (not shown). User interface 804 may be configured to receive user input, the position and movement of which may be indicated by indicators or cursors described herein. User interface 804 may also be configured as a display device for rendering or displaying text fragments.

[0161] Processor 806 may include one or more general-purpose processors and / or special-purpose processors. Data storage 808 may include one or more volatile and / or non-volatile storage components, and may be integrated wholly or partially with processor 806. Data storage 808 may include removable and non-removable components.

[0162] Processor 806 is capable of executing program instructions 818 (e.g., compiled or uncompiled program logic and / or machine code) stored in data storage 808 to perform the various functions described herein. Data storage 808 may comprise a non-transitory computer-readable medium on which program instructions are stored, which, when executed by device 800, enable device 800 to perform any methods, processes, or functions disclosed in this specification and / or the accompanying drawings. Execution of program instructions 818 by processor 806 may result in processor 806 using data 812. For example, program instructions 818 may include an operating system 822 (e.g., an operating system kernel, device drivers, and / or other modules) installed on device 800 and one or more application programs 820 (e.g., a browser, social application, or game application). Similarly, data 812 may include operating system data 816 and application data 814. Operating system data 816 is primarily accessible to operating system 822, while application data 814 is primarily accessible to one or more application programs 820. Application data 814 may reside in a file system visible or hidden from the user of device 800. Application 820 can communicate with operating system 822 through one or more application programming interfaces (APIs). These APIs facilitate application 820 in reading and / or writing application data 814, transmitting or receiving information via communication interface 802, and receiving or displaying information on user interface 804. In some terms, application 820 may be simply referred to as "app". Furthermore, application 820 can be downloaded to device 800 through one or more online application stores or app markets. However, applications can also be installed on device 800 in other ways, such as through a web browser or a physical interface on device 800 (e.g., a USB port).

[0163] In one specific embodiment, the service processing device based on the identification device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the service processing device based on the identification device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following: The device performs near-field interaction with the user terminal and sends the device identifier of the identification device to the user terminal to bind the user identity of the identification device and configure the venue service; the identification device is allocated to the user after successful identity verification based on the user's ticket information; The system interacts with the interactive devices at the tourist site and transmits the device identifier, which is then uploaded to the site system and synchronized with the service platform via the interactive devices. The service platform, based on the service configuration information obtained from the site service configuration, cooperates with the site system to perform service response processing.

[0164] This specification provides an embodiment of a computer-readable storage medium as follows: Corresponding to the above-described service processing method based on an identification device, and based on the same technical concept, one or more embodiments of this specification also provide a computer-readable storage medium.

[0165] The computer-readable storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, implement the following process: Identity verification is performed based on the user's ticketing information synchronized with the venue system, and an identification device is assigned to the user at the venue after successful verification. Based on the device identifier submitted by the user terminal after interacting with the identification device, the user identity of the identification device is bound; The identification device obtains service configuration information from the service configuration of the tourist site and synchronizes the device identifier with the site system. If a service request carrying the device identifier is received, the system will cooperate with the venue system to perform service response processing based on the service configuration information.

[0166] It should be noted that the embodiments of a computer-readable storage medium described in this specification and the embodiments of a service processing method based on an identification device described in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0167] Another embodiment of a computer-readable storage medium provided in this specification is as follows: Corresponding to the other service processing method based on identification device described above, and based on the same technical concept, one or more embodiments of this specification also provide another computer-readable storage medium.

[0168] The computer-readable storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, implement the following process: The device performs near-field interaction with the user terminal and sends the device identifier of the identification device to the user terminal to bind the user identity of the identification device and configure the venue service; the identification device is allocated to the user after successful identity verification based on the user's ticket information; The system interacts with the interactive devices at the tourist site and transmits the device identifier, which is then uploaded to the site system and synchronized with the service platform via the interactive devices. The service platform, based on the service configuration information obtained from the site service configuration, cooperates with the site system to perform service response processing.

[0169] It should be noted that the embodiments of another computer-readable storage medium described in this specification and the embodiments of another service processing method based on an identification device described in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0170] This specification provides an example of a computer program product as follows: Corresponding to the above-described service processing method based on an identification device, and based on the same technical concept, one or more embodiments of this specification also provide a computer program product.

[0171] A computer program product includes a computer program / instructions that, when executed by a processor, perform the following steps: Identity verification is performed based on the user's ticketing information synchronized with the venue system, and an identification device is assigned to the user at the venue after successful verification. Based on the device identifier submitted by the user terminal after interacting with the identification device, the user identity of the identification device is bound; The identification device obtains service configuration information from the service configuration of the tourist site and synchronizes the device identifier with the site system. If a service request carrying the device identifier is received, the system will cooperate with the venue system to perform service response processing based on the service configuration information.

[0172] It should be noted that the embodiments of a computer program product described in this specification and the embodiments of a service processing method based on an identification device described in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0173] Another example of a computer program product provided in this specification is as follows: Corresponding to the other service processing method based on identification devices described above, and based on the same technical concept, one or more embodiments of this specification also provide another computer program product.

[0174] A computer program product includes a computer program / instructions that, when executed by a processor, perform the following steps: The device performs near-field interaction with the user terminal and sends the device identifier of the identification device to the user terminal to bind the user identity of the identification device and configure the venue service; the identification device is allocated to the user after successful identity verification based on the user's ticket information; The system interacts with the interactive devices at the tourist site and transmits the device identifier, which is then uploaded to the site system and synchronized with the service platform via the interactive devices. The service platform, based on the service configuration information obtained from the site service configuration, cooperates with the site system to perform service response processing.

[0175] It should be noted that the embodiments of another computer program product described in this specification and the embodiments of another service processing method based on identification devices described in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0176] The various embodiments in this specification are described in a progressive manner. The same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on describing the differences from other embodiments. For example, the device embodiment, equipment embodiment and computer-readable storage medium embodiment are all similar to the method embodiment, so the description is relatively simple. When reading the relevant content of the device embodiment, equipment embodiment and computer-readable storage medium embodiment, please refer to the description of the method embodiment.

[0177] While one or more embodiments of this specification provide method steps as described in the embodiments or flowcharts, it is understood that the order of steps listed in the embodiments or flowcharts is merely one possible execution order among many steps, and does not represent the only execution order. Therefore, when the claims involve method steps, any changes or adjustments to the order of such steps, or the parallelism between steps, are also within the scope of protection of the claims. This specification uses specific terms to describe embodiments of this specification. For example, "an embodiment," "one embodiment," and / or "some embodiments" refer to a particular feature, structure, or characteristic related to at least one embodiment of this specification. Therefore, it should be emphasized and noted that "an embodiment," "one embodiment," or "an alternative embodiment" mentioned twice or more in different locations in this specification do not necessarily refer to the same embodiment. Furthermore, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0178] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0179] In the 1930s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many improvements to the methodology today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that an improvement to the methodology cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program and "integrate" a digital system onto a PLD themselves, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must also be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0180] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0181] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, an identifiable device, or any combination of these devices.

[0182] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in one or more software and / or hardware.

[0183] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied on one or more computer-readable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0184] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0185] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0186] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0187] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0188] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0189] Computer-readable media include both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer-readable storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0190] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising at least one…" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0191] One or more embodiments of this specification can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. One or more embodiments of this specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0192] The above description is merely an embodiment of this document and is not intended to limit the scope of this document. Various modifications and variations can be made to this document by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this document should be included within the scope of the claims of this document.

Claims

1. A service processing method based on an identification device, applied to a service platform, characterized in that, The method includes: Identity verification is performed based on the user's ticketing information synchronized with the venue system, and an identification device is assigned to the user at the venue after successful verification. Based on the device identifier submitted by the user terminal after interacting with the identification device, the user identity of the identification device is bound; The identification device obtains service configuration information from the service configuration of the tourist site and synchronizes the device identifier with the site system. If a service request carrying the device identifier is received, the system will cooperate with the venue system to perform service response processing based on the service configuration information.

2. The service processing method based on the identification device according to claim 1, characterized in that, The identification devices are allocated in the following manner: The system obtains user information by using the equipment management terminal of the tourist site to interact with the user terminal in the near field and submits it to the site system. The venue system verifies the device application or user ticket based on the user information, and after the verification is passed, it issues an allocation instruction to the device management terminal so that the device management terminal can allocate the identification device to the user according to the allocation instruction.

3. The service processing method based on the identification device according to claim 1, characterized in that, After being assigned, the identification device belongs to the user; the identification device is obtained by manufacturing the equipment materials based on the user's material configuration information. The material configuration information is generated after the user purchases or applies for equipment and configures the materials through the service program.

4. The service processing method based on the identification device according to claim 1, characterized in that, The process of obtaining service configuration information for the identification device at the tourist site includes: Create a prepaid card account for the identification device based on the prepaid card template of the tourist site, or create a device fund account for the identification device by calling the fund service interface; If an account top-up request is detected, funds are transferred from the user's funds account and then transferred to the top-up card account or the device funds account.

5. The service processing method based on the identification device according to claim 1, characterized in that, The process of obtaining service configuration information for the identification device at the tourist site includes: Create a user credit account for the identification device, and allocate a credit limit to the user credit account to obtain a credit limit; The credit limit is used to process payment requests made by the identification device through interaction with the venue interaction device.

6. The service processing method based on the identification device according to claim 4 or 5, characterized in that, The process of obtaining service configuration information for the identification device at the tourist site also includes: Based on the device type of the identification device, the service range of the tourist attraction is configured to obtain range configuration information, and / or, based on the device type of the identification device and the user ticketing information, the service permission of the tourist attraction is configured to obtain permission configuration information; The scope configuration information and / or the permission configuration information are synchronized to the venue system and sent to the corresponding venue interaction device.

7. The service processing method based on the identification device according to claim 1, characterized in that, The service request is generated and submitted to the venue system after the identification device performs near-field interaction with the venue interaction device of the tour venue, and then sent by the venue system to the service platform. The interactive devices in the venue include: access interactive devices, venue interactive tags, venue communication devices, storage devices, venue transportation devices, and / or tour guidance devices.

8. The service processing method based on the identification device according to claim 7, characterized in that, The service response processing based on the service configuration information and in coordination with the venue system includes: The payment service request is processed based on the stored-value card account, device fund account, or user credit account of the identification device, and the payment processing result is synchronized to the venue system to execute the service response operation of the payment service request; The payment funds processed based on the user's credit account are obtained by transferring funds from the platform account of the service platform.

9. The service processing method based on the identification device according to claim 7, characterized in that, The service response processing based on the service configuration information and in coordination with the venue system includes: Based on the scope configuration information and / or permission configuration information in the service configuration information, perform service scope verification and / or service permission verification for service interaction requests. The venue system returns service scope verification results and / or service permission verification results to the venue interaction device corresponding to the service interaction request in order to execute the service interaction response operation.

10. The service processing method based on the identification device according to claim 1, characterized in that, The user's ticketing information is synchronized after the user accesses the ticketing page of the service program of the tourist site and associates the ticketing information. The service program accesses the site by scanning the service identifier of the tourist attraction using the user terminal, or by reading service access information from the near-field communication component of the tourist attraction using the user terminal.

11. The service processing method based on the identification device according to claim 1, characterized in that, The device funds account in the service configuration information includes a group funds account; the group funds account is associated with the identification devices of multiple group members of the user group to which the user belongs.

12. The service processing method based on the identification device according to claim 11, characterized in that, The user terminal establishes a wireless connection with the identification devices of the multiple group members, and uploads the communication location information collected by the identification device of any group member through interaction with the wireless components deployed in the tourist area to the service platform; The service platform calculates the member's location based on the uploaded communication location information and returns it to the user terminal.

13. The service processing method based on the identification device according to claim 1, characterized in that, After the operation of synchronizing the device identifier with the venue system is executed, it also includes: If a service interaction request is received from the user terminal, the system will process the interaction response to the service interaction request and return the response processing result to the user terminal. The service interaction request is generated after the identification device performs a near-field interaction with the interactive identification device of the visitor at the tourist site, or after the identification device performs a near-field interaction with the interactive tag of the tourist site.

14. The service processing method based on the identification device according to claim 13, characterized in that, The step of performing the interaction response processing of the service interaction request and returning the response processing result to the user terminal includes: Based on the device type of the identified device, the task interaction permission is verified. If the permission verification is successful, the task interaction request is processed based on the task interaction data of the tourist site to obtain the task interaction result. The task interaction result is sent to the user terminal so that the task interaction can be displayed in the service program based on the task interaction result.

15. A service processing method based on an identification device, applied to an identification device, characterized in that, The method includes: The device performs near-field interaction with the user terminal and sends a device identifier to the user terminal to bind the user's identity and configure the venue service; the device is assigned to the user after successful identity verification based on the user's ticketing information. The system interacts with the interactive devices at the tourist site and transmits the device identifier, which is then uploaded to the site system and synchronized with the service platform via the interactive devices. The service platform, based on the service configuration information obtained from the site service configuration, cooperates with the site system to perform service response processing.

16. The service processing method based on the identification device according to claim 15, characterized in that, After the step of performing near-field interaction with the user terminal and sending the device identifier to the user terminal is executed, the method further includes: The interaction information of the tags can be read through near-field interaction with the interactive tags of the tourist site, or the interaction information of the devices can be read through near-field interaction with the interactive identification devices of the tourists of the tourist site. The system sends the tag interaction information or the device interaction information to the user terminal to upload the corresponding service interaction request to the service platform through the user terminal, and displays the service interaction based on the interaction response result returned by the service platform.

17. The service processing method based on an identification device according to claim 15, characterized in that, The identification devices are allocated in the following manner: The system obtains user information by using the equipment management terminal of the tourist site to interact with the user terminal in the near field and submits it to the site system. The venue system verifies the device application or user ticket based on the user information, and after the verification is passed, it issues an allocation instruction to the device management terminal so that the device management terminal can allocate the identification device to the user according to the allocation instruction.

18. A service processing apparatus based on an identification device, operating on a service platform, characterized in that, The device includes: The identity verification module is configured to verify the user's identity based on the user's ticketing information synchronized with the venue system, so as to allocate an identification device to the user at the venue after successful verification. The identity binding module is configured to bind the user identity of the identification device based on the device identifier submitted after the user terminal interacts with the identification device; The service configuration module is configured to obtain service configuration information for the identification device at the tourist site and synchronize the device identifier with the site system; The response processing module is configured to, upon receiving a service request carrying the device identifier, cooperate with the venue system to perform service response processing based on the service configuration information.

19. A service processing device based on an identification device, characterized in that, include: processor; And, a memory configured to store computer-executable instructions, which, when executed, cause the processor to: Identity verification is performed based on the user's ticketing information synchronized with the venue system, and an identification device is assigned to the user at the venue after successful verification. Based on the device identifier submitted by the user terminal after interacting with the identification device, the user identity of the identification device is bound; The identification device obtains service configuration information from the service configuration of the tourist site and synchronizes the device identifier with the site system. If a service request carrying the device identifier is received, the system will cooperate with the venue system to perform service response processing based on the service configuration information.

20. A computer-readable storage medium for storing computer-executable instructions, characterized in that, When executed, the computer-executable instructions perform the steps of the method of claim 1 or claim 15.

Images