Electronic device for managing grouped tickets and operation method thereof

Abstract

An electronic device according to an embodiment of the present disclosure: receives ticket information from a first server or an external electronic device; determines whether user information included in the ticket information corresponds to authentication information of the electronic device; and on the basis that the user information corresponds to the authentication information, registers, as a ticket of the electronic device in the first server, a first ticket corresponding to the ticket information, wherein the first ticket is any one of a plurality of tickets purchased by the external electronic device, and the plurality of tickets may be grouped and managed in the first server. Other various embodiments are possible.

Description

Electronic device for managing grouped tickets and method of operation thereof

[0001] The present disclosure relates to an electronic device for managing grouped tickets and a method of operating the same.

[0002] As digital technology advances and security technology evolves, mobile wallet services are being provided via electronic devices. A mobile wallet service refers to a service that stores and manages various payment methods and digital assets, such as credit cards, debit cards, membership cards, coupons, or tickets, and enables payments or authentication using them. Mobile services can be provided through platforms or applications embedded in electronic devices, and can facilitate ticket usage in various locations, as well as for offline or online commerce. For example, tickets can include various forms such as airline tickets, train tickets, bus tickets, movie theater tickets, or concert tickets, and can be stored and managed in digital form within an application. Once a ticket is registered in the application, it can be quickly viewed and used via an electronic device without the need for a physical ticket.

[0003] The information described above may be provided as related art for the purpose of aiding understanding of this document. None of the foregoing is to be claimed as prior art related to this document, nor is it to be used to determine prior art.

[0004] One embodiment of the present disclosure may provide an electronic device for managing grouped tickets and a method of operating the same.

[0005] One embodiment of the present disclosure may provide an electronic device for controlling the sharing and priority of group tickets and a method of operating the same.

[0006] One embodiment of the present disclosure may provide an electronic device and a method of operation thereof that enhances the security of a shared ticket to prevent misuse or indiscriminate sharing of the ticket.

[0007] One embodiment of the present disclosure may provide an electronic device and a method of operating the same that enable real-time monitoring of the status of grouped tickets.

[0008] One embodiment of the present disclosure may provide an electronic device that provides a customized advertisement based on ticket usage and a method of operating the same.

[0009] An electronic device according to one embodiment of the present disclosure may include at least one processor comprising a display, a transceiver, a memory, and a processing circuit. The memory may store instructions that, when executed individually or collectively by the at least one processor, cause the electronic device to receive ticket information from a first server or an external electronic device through the transceiver, determine whether user information included in the ticket information corresponds to authentication information of the electronic device, and, based on whether the user information corresponds to authentication information, cause a first ticket corresponding to the ticket information to be registered as a ticket of the electronic device to the first server. The first ticket is one of a plurality of tickets purchased by the external electronic device, and the plurality of tickets may be grouped and managed on the first server.

[0010] A method of operating an electronic device according to one embodiment of the present disclosure may include: receiving ticket information from a first server or an external electronic device; determining whether user information included in the ticket information corresponds to authentication information of the electronic device; and registering a first ticket corresponding to the ticket information as a ticket of the electronic device to the first server based on whether the user information corresponds to the authentication information. The first ticket is any one of a plurality of tickets purchased by the external electronic device, and the plurality of tickets may be grouped and managed on the first server.

[0011] In relation to the description of the drawings, the same or similar reference numerals may be used for identical or similar components.

[0012] FIG. 1 is a block diagram of an electronic device in a network environment according to various embodiments.

[0013] FIG. 2 is a flowchart illustrating a ticket sharing operation between electronic devices according to one embodiment.

[0014] FIG. 3 is a block diagram of an electronic device according to one embodiment.

[0015] FIG. 4 is a drawing illustrating a mobile wallet module according to one embodiment.

[0016] FIG. 5 is a schematic diagram illustrating a ticket grouping system according to one embodiment.

[0017] FIG. 6 is a flowchart illustrating the operation of registering grouped tickets in each electronic device according to one embodiment.

[0018] FIG. 7a is a flowchart illustrating the operation of registering grouped tickets based on communication between electronic devices according to one embodiment.

[0019] FIG. 7b is a flowchart illustrating the operation when the validity check of grouped tickets fails according to one embodiment.

[0020] FIG. 8 is a diagram illustrating group information input by a first electronic device according to one embodiment.

[0021] FIG. 9 is a flowchart illustrating the operation of each electronic device receiving changed information of a ticket according to one embodiment.

[0022] FIG. 10 is a flowchart illustrating the operation of sharing changed ticket information between electronic devices according to one embodiment.

[0023] FIG. 11 is a flowchart illustrating the operation of electronic devices using a ticket according to one embodiment.

[0024] FIG. 12 is a diagram illustrating a screen of a wallet application displaying a group ticket according to one embodiment.

[0025] FIG. 13 is a flowchart illustrating the ticket registration operation of an electronic device according to one embodiment.

[0026] FIG. 14 is a flowchart illustrating the operation of an electronic device according to one embodiment transmitting a message indicating that ticket registration is not possible.

[0027] FIG. 15 is a flowchart illustrating the operation of an electronic device receiving and sharing an updated ticket according to one embodiment.

[0028] FIG. 16 is a flowchart illustrating the operation of an electronic device according to one embodiment outputting an advertisement based on location.

[0029] FIG. 17 is a flowchart illustrating the operation of an electronic device according to one embodiment adjusting ticket priority to display tickets.

[0030] Hereinafter, embodiments of the present disclosure are described in detail with reference to the drawings so that those skilled in the art can easily practice them. However, the present disclosure may be embodied in various different forms and is not limited to the embodiments described herein. In relation to the description of the drawings, the same or similar reference numerals may be used for identical or similar components. Furthermore, in the drawings and related descriptions, descriptions of well-known functions and configurations may be omitted for clarity and brevity.

[0031] FIG. 1 is a block diagram of an electronic device (101) in a network environment (100) according to various embodiments.

[0032] Referring to FIG. 1, in a network environment (100), an electronic device (101) may communicate with an electronic device (102) through a first network (198) (e.g., a short-range wireless communication network) or with at least one of an electronic device (104) or a server (108) through a second network (199) (e.g., a long-range wireless communication network). According to one embodiment, the electronic device (101) may communicate with the electronic device (104) through a server (108). According to one embodiment, the electronic device (101) may include a processor (120), memory (130), input module (150), sound output module (155), display module (160), audio module (170), sensor module (176), interface (177), connection terminal (178), haptic module (179), camera module (180), power management module (188), battery (189), communication module (190), subscriber identification module (196), or antenna module (197). In some embodiments, at least one of these components (e.g., connection terminal (178)) may be omitted from the electronic device (101), or one or more other components may be added. In some embodiments, some of these components (e.g., sensor module (176), camera module (180), or antenna module (197)) may be integrated into a single component (e.g., display module (160)).

[0033] The processor (120) can control at least one other component (e.g., a hardware or software component) of the electronic device (101) connected to the processor (120) by executing software (e.g., a program (140)), and can perform various data processing or operations. According to one embodiment, as at least part of the data processing or operations, the processor (120) can store commands or data received from other components (e.g., a sensor module (176) or a communication module (190)) in volatile memory (132), process the commands or data stored in volatile memory (132), and store the resulting data in non-volatile memory (134). According to one embodiment, the processor (120) may include a main processor (121) (e.g., a central processing unit or an application processor) or an auxiliary processor (123) that can operate independently or together with it (e.g., a graphics processing unit, a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor). For example, if the electronic device (101) includes a main processor (121) and an auxiliary processor (123), the auxiliary processor (123) may be configured to use lower power than the main processor (121) or to be specialized for a designated function. The auxiliary processor (123) may be implemented separately from the main processor (121) or as part thereof.

[0034] The auxiliary processor (123) may control at least some of the functions or states associated with at least one component of the electronic device (101) (e.g., display module (160), sensor module (176), or communication module (190)) on behalf of the main processor (121) while the main processor (121) is in an inactive (e.g., sleep) state, or together with the main processor (121) while the main processor (121) is in an active (e.g., application execution) state. According to one embodiment, the auxiliary processor (123) (e.g., image signal processor or communication processor) may be implemented as part of another functionally related component (e.g., camera module (180) or communication module (190)). According to one embodiment, the auxiliary processor (123) (e.g., neural network processing unit) may include a hardware structure specialized for processing an artificial intelligence model. The artificial intelligence model may be generated through machine learning. Such learning may be performed, for example, on the electronic device (101) itself where the artificial intelligence is performed, or through a separate server (e.g., server (108)). The learning algorithm may include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but is not limited to the examples described above. The artificial intelligence model may include a plurality of artificial neural network layers.An artificial neural network may be a deep neural network (DNN), a convolutional neural network (CNN), a recurrent neural network (RNN), a restricted Boltzmann machine (RBM), a deep belief network (DBN), a bidirectional recurrent deep neural network (BRDNN), a deep Q-network, or a combination of two or more of the above, but is not limited to the examples described above. In addition to the hardware structure, the artificial intelligence model may include a software structure, either additionally or substantially.

[0035] The memory (130) can store various data used by at least one component of the electronic device (101) (e.g., processor (120) or sensor module (176)). The data may include, for example, input data or output data for software (e.g., program (140)) and related commands. The memory (130) may include volatile memory (132) or non-volatile memory (134).

[0036] The program (140) may be stored as software in memory (130) and may include, for example, an operating system (142), middleware (144), or an application (146).

[0037] The input module (150) can receive commands or data to be used for a component of the electronic device (101) (e.g., processor (120)) from outside the electronic device (101) (e.g., user). The input module (150) may include, for example, a microphone, a mouse, a keyboard, a key (e.g., a button), or a digital pen (e.g., a stylus pen).

[0038] The sound output module (155) can output a sound signal to the outside of the electronic device (101). The sound output module (155) may include, for example, a speaker or a receiver. The speaker may be used for general purposes, such as multimedia playback or recording playback. The receiver may be used to receive incoming calls. According to one embodiment, the receiver may be implemented separately from the speaker or as part thereof.

[0039] The display module (160) can visually provide information to an external (e.g., user) of the electronic device (101). The display module (160) may include, for example, a display, a holographic device, or a projector and a control circuit for controlling said device. According to one embodiment, the display module (160) may include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of the force generated by said touch.

[0040] The audio module (170) can convert sound into an electrical signal or, conversely, convert an electrical signal into sound. According to one embodiment, the audio module (170) can acquire sound through the input module (150) or output sound through the sound output module (155) or an external electronic device (e.g., electronic device (102)) (e.g., speaker or headphones) connected directly or wirelessly to the electronic device (101).

[0041] The sensor module (176) can detect the operating state of the electronic device (101) (e.g., power or temperature) or the external environmental state (e.g., user state) and generate an electrical signal or data value corresponding to the detected state. According to one embodiment, the sensor module (176) may include, for example, a gesture sensor, a gyroscope sensor, a barometric pressure sensor, a magnetic sensor, an accelerometer sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biosensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

[0042] The interface (177) may support one or more specified protocols that can be used for the electronic device (101) to be connected directly or wirelessly to an external electronic device (e.g., electronic device (102)). According to one embodiment, the interface (177) may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.

[0043] The connection terminal (178) may include a connector through which the electronic device (101) can be physically connected to an external electronic device (e.g., electronic device (102)). According to one embodiment, the connection terminal (178) may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

[0044] The haptic module (179) can convert an electrical signal into a mechanical stimulus (e.g., vibration or movement) or an electrical stimulus that can be perceived by the user through tactile or kinesthetic senses. According to one embodiment, the haptic module (179) may include, for example, a motor, a piezoelectric element, or an electric stimulation device.

[0045] The camera module (180) can capture still images and video. According to one embodiment, the camera module (180) may include one or more lenses, image sensors, image signal processors, or flashes.

[0046] The power management module (188) can manage power supplied to the electronic device (101). According to one embodiment, the power management module (188) can be implemented, for example, as at least part of a power management integrated circuit (PMIC).

[0047] The battery (189) can supply power to at least one component of the electronic device (101). According to one embodiment, the battery (189) may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0048] The communication module (190) can support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between an electronic device (101) and an external electronic device (e.g., electronic device (102), electronic device (104), or server (108)), and the performance of communication through the established communication channel. The communication module (190) may include one or more communication processors that operate independently of the processor (120) (e.g., application processor) and support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication module (190) may include a wireless communication module (192) (e.g., cellular communication module, short-range wireless communication module, or GNSS (global navigation satellite system) communication module) or a wired communication module (194) (e.g., LAN (local area network) communication module, or power line communication module). The corresponding communication module among these communication modules can communicate with an external electronic device (104) through a first network (198) (e.g., a short-range communication network such as Bluetooth, WiFi (wireless fidelity) direct, or IrDA (infrared data association)) or a second network (199) (e.g., a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., a LAN or WAN)). These various types of communication modules may be integrated into a single component (e.g., a single chip) or implemented as multiple separate components (e.g., multiple chips). The wireless communication module (192) can identify or authenticate the electronic device (101) within a communication network such as the first network (198) or the second network (199) using subscriber information (e.g., International Mobile Subscriber Identifier (IMSI)) stored in the subscriber identification module (196).

[0049] The wireless communication module (192) can support 5G networks and next-generation communication technologies following 4G networks, for example, new radio access technology. NR access technology can support high-speed transmission of high-capacity data (enhanced mobile broadband (eMBB)), minimization of terminal power and connection of multiple terminals (massive machine type communications (mMTC)), or high reliability and low latency (ultra-reliable and low-latency communications (URLLC)). The wireless communication module (192) can support a high-frequency band (e.g., mmWave band) to achieve a high data transmission rate, for example. The wireless communication module (192) can support various technologies for securing performance in the high-frequency band, such as beamforming, massive MIMO (multiple-input and multiple-output), full-dimensional MIMO (FD-MIMO), array antenna, analog beam-forming, or large-scale antenna. The wireless communication module (192) can support various requirements specified in the electronic device (101), external electronic device (e.g., electronic device (104)), or network system (e.g., second network (199)). According to one embodiment, the wireless communication module (192) may support a Peak data rate (e.g., 20 Gbps or more) for eMBB realization, loss coverage (e.g., 164 dB or less) for mMTC realization, or U-plane latency (e.g., downlink (DL) and uplink (UL) each 0.5 ms or less, or round trip 1 ms or less) for URLLC realization.

[0050] An antenna module (197) can transmit a signal or power to or from an external source (e.g., an external electronic device). According to one embodiment, the antenna module (197) may include an antenna comprising a radiator made of a conductor or a conductive pattern formed on a substrate (e.g., a PCB). According to one embodiment, the antenna module (197) may include a plurality of antennas (e.g., an array antenna). In this case, at least one antenna suitable for a communication method used in a communication network, such as a first network (198) or a second network (199), may be selected from the plurality of antennas, for example, by a communication module (190). A signal or power may be transmitted or received between the communication module (190) and an external electronic device through the selected at least one antenna. According to some embodiments, in addition to the radiator, other components (e.g., a radio frequency integrated circuit (RFIC)) may be additionally created as part of the antenna module (197).

[0051] According to various embodiments, the antenna module (197) can create a mmWave antenna module. According to one embodiment, the mmWave antenna module may include a printed circuit board, an RFIC disposed on or adjacent to a first surface (e.g., bottom surface) of the printed circuit board and capable of supporting a specified high frequency band (e.g., mmWave band), and a plurality of antennas (e.g., array antennas) disposed on or adjacent to a second surface (e.g., top surface or side surface) of the printed circuit board and capable of transmitting or receiving a signal of the specified high frequency band.

[0052] At least some of the above components can be connected to each other via a communication method between peripheral devices (e.g., bus, GPIO (general purpose input and output), SPI (serial peripheral interface), or MIPI (mobile industry processor interface)) and exchange signals (e.g., commands or data) with each other.

[0053] According to one embodiment, commands or data may be transmitted or received between an electronic device (101) and an external electronic device (104) through a server (108) connected to a second network (199). Each of the external electronic devices (102, or 104) may be the same or a different type of device as the electronic device (101). According to one embodiment, all or part of the operations performed on the electronic device (101) may be performed on one or more of the external electronic devices (102, 104, or 108). For example, if the electronic device (101) needs to perform a function or service automatically or in response to a request from a user or another device, the electronic device (101) may request one or more external electronic devices to perform at least part of the function or service instead of performing the function or service itself or additionally. One or more external electronic devices that receive the above request may execute at least part of the requested function or service, or additional function or service related to the request, and transmit the result of the execution to the electronic device (101). The electronic device (101) may provide the result as is or additionally processed as at least part of the response to the request. For this purpose, for example, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used. The electronic device (101) may provide ultra-low latency services using, for example, distributed computing or mobile edge computing. In another embodiment, the external electronic device (104) may include an Internet of Things (IoT) device. The server (108) may be an intelligent server using machine learning and / or neural networks. According to one embodiment, the external electronic device (104) or the server (108) may be included within a second network (199).The electronic device (101) can be applied to intelligent services (e.g., smart home, smart city, smart car, or healthcare) based on 5G communication technology and IoT-related technology.

[0054] FIG. 2 is a flowchart illustrating a ticket sharing operation between electronic devices according to one embodiment.

[0055] Referring to FIG. 2, in operation 212, the electronic device (202) can register at least one ticket through an application. According to one embodiment, the application may provide a function that enables online or offline payment based on a payment method such as a credit card or debit card, or allows the registration and use of a ticket (or boarding pass). For example, the application may be referred to by various terms such as a wallet application, a mobile wallet, or an app wallet platform, but for convenience of explanation, it will be referred to as a 'wallet application' below.

[0056] According to one embodiment, the electronic device (202) can register at least one airplane ticket purchased from each airline's application or website or online store to the wallet application based on the user's choice. For example, the electronic device (202) can register at least one airplane ticket to the wallet application based on an image, a QR (quick response) code, or a barcode of at least one airplane ticket.

[0057] In operation 214, the electronic device (202) may receive input for ticket sharing (e.g., user input). For example, the electronic device (202) may determine that input for ticket sharing has been received based on the selection of at least one of an icon, menu, button, or graphical object for sharing any one of at least one registered ticket in the wallet application.

[0058] In operation 216, the electronic device (202) may generate a link for ticket sharing and transmit it to an external electronic device (206) based on the reception of input for ticket sharing. According to one embodiment, the link for ticket sharing may be used to register a ticket shared by the electronic device (202) in a wallet application installed on the external electronic device (206). According to one embodiment, the external electronic device (206) may be an electronic device corresponding to any one of the contacts included in the contact list of the electronic device (202) selected by the user, or a contact entered by the user.

[0059] In operation 218, the external electronic device (206) receives a link for ticket sharing from the electronic device (202) and can register the shared ticket to the server (204) through the received link. When the shared ticket is registered to the server (204), information about the shared ticket can be displayed in the wallet application of the external electronic device (206).

[0060] The ticket sharing operation illustrated in FIG. 2 does not include an operation to verify the personal information of the person registering the ticket or the information of the actual owner of the ticket; therefore, if the link for ticket sharing is compromised, anyone may be able to register the ticket and the ticket may be used by an illegitimate user. Accordingly, a solution to address this is required.

[0061] According to one embodiment, various tickets, such as movie tickets, performance tickets, museum admission tickets, or sports stadium admission tickets, as well as airplane tickets, can be registered in a wallet application. When the number of tickets registered in the wallet application increases, users may experience inconvenience in finding the necessary tickets and may have to spend a significant amount of time. Considering this, a method for more efficiently ordering or sorting the registered tickets is required.

[0062] According to one embodiment, registered tickets may undergo changes depending on the circumstances. For example, in the case of airplane tickets, information may change frequently due to gate changes or delay issues (e.g., weather changes). The registered ticket information in the wallet application needs to be updated based on the changed information, but updates may not be possible in situations where communication is impossible.

[0063] The following describes an electronic device and method for solving the problems described above.

[0064] FIG. 3 is a block diagram of an electronic device according to one embodiment.

[0065] Referring to FIG. 3, the electronic device (301) may include a display (310), a transceiver (320), a memory (330), and a processor (340). According to one embodiment, the electronic device (301) may include additional components (e.g., a user interface) in addition to the components shown, or at least one of the components shown may be omitted. According to one embodiment, the electronic device (301) may include components identical or similar to at least one of the components (e.g., modules) of the electronic device (101) shown in FIG. 1.

[0066] According to one embodiment, the electronic device (301) may be any one of a mobile device (e.g., a smartphone or tablet), a computing device (e.g., a PC (personal computer) or a laptop), a wearable device (e.g., a smart watch or HMD (head mounted display)), or a home appliance (e.g., a TV (television)), but is not limited thereto and may be any of various types of electronic devices.

[0067] According to one embodiment, the display (310) can perform various display operations according to the function of the electronic device (301). For example, the display (310) can display at least one of various service information, media information, text information, or graphic information according to the execution of an application. According to one embodiment, the display (310) can display at least one ticket (or card) that can be used based on the execution of an application (e.g., a wallet application), and can display various information related to ticket usage or ticket sharing.

[0068] According to one embodiment, the display (310) may include an LCD (liquid crystal display), an LED (light emitting diode), an OLED (organic light emitting diode), a QLED (quantum dot light emitting diode), or a Micro LED, and may be implemented as a touchscreen.

[0069] According to one embodiment, the display (310) may be implemented as a single independent display or may include a plurality of displays placed at different locations.

[0070] According to one embodiment, the display (310) may be implemented identically or similarly to the display module (160) of FIG. 1.

[0071] According to one embodiment, the communication unit (320) may operate independently of a processor (e.g., application processor) (340) and may include one or more communication processors that support wireless communication or wired communication. According to one embodiment, the communication unit (320) may include a wireless communication module (e.g., cellular communication module, short-range wireless communication module, or GNSS communication module) or a wired communication module (e.g., LAN communication module, or power line communication module). The corresponding communication module among these communication modules may communicate with an external electronic device through a first network (e.g., a short-range communication network such as Bluetooth, BLE, Wi-Fi, WFD, or IrDA) or a second network (e.g., a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a long-range communication network such as a computer network (e.g., LAN or WAN). These various types of communication modules may be integrated into a single component (e.g., a single chip) or implemented as multiple separate components (e.g., multiple chips). According to one embodiment, the communication unit (320) may be implemented substantially identically or similarly to the communication module (190) of FIG. 1.

[0072] According to one embodiment, the memory (330) may store various data used by at least one component of the electronic device (301) (e.g., display (310), communication unit (320), or processor (340)). For example, the memory (330) may store at least one program for processing and controlling the processor (340) and may store input and / or output data. The memory (330) may store at least one artificial intelligence (AI) model (e.g., machine learning model or deep learning model) and may include volatile memory or non-volatile memory. According to one embodiment, the memory (330) may be implemented substantially identically or similarly to the memory (130) of FIG. 1.

[0073] According to one embodiment, the processor (340) can control the overall operation of the electronic device (301). The processor (340) can perform operations or data processing regarding the control and / or communication of at least one other component of the electronic device (301). For example, the processor (340) can be electrically connected to the display (310), the communication unit (320), and the memory (330), and can execute instructions of a program stored in the memory (330). According to one embodiment, the processor (340) can be implemented substantially identically or similarly to the processor (120) of FIG. 1.

[0074] According to one embodiment, the processor (340) may include a processing circuit that executes instructions of a program stored in memory (330). The processor (340) may include at least one of a CPU (central processing unit), NPU (neural processing unit), GPU (graphics processing unit), MPU (micro processing unit), MCU (micro controller unit), AP (application processor), CP (communication processor), SoC (system on chip), IC (integrated circuit) sensor hub, supplementary processor, ASIC (application specific integrated circuit), or FPGA (field programmable gate arrays), and may have multiple cores.

[0075] According to one embodiment, the processor (340) can control the operations of the electronic device (301) by executing instructions stored in the memory (330). For example, the processor (340) may correspond to a plurality of processors that divide and collectively perform a plurality of operations among the processors.

[0076] FIG. 4 is a drawing illustrating a mobile wallet module according to one embodiment.

[0077] Referring to FIG. 4, the mobile wallet module (400) may be a module for performing various functions provided by a wallet application. According to one embodiment, the mobile wallet module (400) may be included in the processor (340) of the electronic device (301), be a component corresponding to the processor (340), or be an independent component electrically connected to the processor (340) and operating based on the control of the processor (340).

[0078] According to one embodiment, the mobile wallet module (400) may include a ticket management module (410) that manages various functions of the ticket, and a communication module (or network module) (420) that handles various types of communication and enables the electronic device (301) to be utilized over a wide range.

[0079] According to one embodiment, the ticket management module (410) may include modules that enable systematic support for the overall management and use of tickets. For example, the ticket management module (410) may include a ticket validation module (411), a ticket sharing module (412), a ticket grouping module (413), a ticket status management module (414), or a ticket priority module (415), or may perform the operations of the ticket validation module (411), the ticket sharing module (412), the ticket grouping module (413), the ticket status management module (414), or the ticket priority module (415) in an integrated manner.

[0080] According to one embodiment, the ticket validity verification module (411) can check whether a purchased or shared ticket is a registrable or usable ticket based on whether user information included in the ticket corresponds to user authentication information.

[0081] According to one embodiment, the ticket sharing module (412) can share purchased or registered tickets with an external electronic device.

[0082] According to one embodiment, the ticket grouping module (413) can group multiple tickets. According to one embodiment, the ticket grouping module (413) can group tickets of similar types or tickets of similar schedules. For example, the ticket grouping module (413) can group by movie tickets, performance tickets, or airplane tickets, or group tickets that have the same or similar departure or start schedules.

[0083] According to one embodiment, the ticket status management module (414) can manage the status of the ticket. For example, the status of the ticket may include various states of the ticket, such as before use, completed use, or completed sharing.

[0084] According to one embodiment, the ticket priority module (415) can set, adjust, or change the order in which tickets are displayed on the wallet application based on the priority of each ticket. For example, the ticket priority module (415) can set a high priority for tickets selected by the user or tickets associated with environmental factors (e.g., the location of the electronic device (301)) so that the tickets can be placed in a position where they can be quickly selected in the wallet application.

[0085] According to one embodiment, the communication module (420) is a module capable of performing wireless communication with an external electronic device or server, and may be included in the communication unit (320) of FIG. 3.

[0086] According to one embodiment, the communication unit (420) may include a short-range communication module (421), a mobile communication module (422), or a payment module (423).

[0087] According to one embodiment, the near-field communication module (421) is a module that communicates with an external electronic device and can be used for status management or information transmission of grouped tickets. For example, the near-field communication module (421) may include at least one of an ultra-wideband (UWB) communication module, a Wi-Fi communication module, a Bluetooth communication module, a BLE communication module, an NFC (near field communication) communication module, an RFID (radio-frequency identification) communication module, a Zigbee communication module, a WFD communication module, a WLAN communication module, an Ant+ communication module, an IrDA communication module, or a microwave (uWave) communication module, but is not limited thereto.

[0088] According to one embodiment, the mobile communication module (422) can communicate with at least one server through a network connection. For example, the mobile communication module (422) may include various types of next-generation communication modules, including an LTE communication module, an LTE-A communication module, or an NR communication module. According to one embodiment, the mobile communication module (422) can perform tasks such as determining whether a ticket is used or grouping through information exchange with at least one server (e.g., a wallet server or a partner server).

[0089] According to one embodiment, the payment module (423) may support online or offline payments (e.g., payment for purchasing tickets). For example, online payments may be performed based on authentication actions such as biometric authentication (e.g., fingerprint authentication, iris authentication, or facial authentication), pattern authentication, or PIN (personal identification number) number input for a credit card or debit card registered in a wallet application. For example, offline payments may support payments based on NFC or MST (magnetic secure transmission) methods for a credit card or debit card registered in a wallet application. Offline payments may also be performed based on authentication actions such as biometric authentication or PIN number input.

[0090] According to one embodiment, the electronic device may include at least one processor comprising a display, a transceiver, a memory, and a processing circuit. The memory may store instructions that, when executed individually or collectively by the at least one processor, cause the electronic device to receive ticket information from a first server or an external electronic device via the transceiver, determine whether user information included in the ticket information corresponds to authentication information of the electronic device, and, based on whether the user information corresponds to authentication information, cause a first ticket corresponding to the ticket information to be registered as a ticket of the electronic device to the first server. The first ticket is one of a plurality of tickets purchased by the external electronic device, and the plurality of tickets may be grouped and managed on the first server.

[0091] According to one embodiment, the memory may store instructions that, when executed individually or collectively by the at least one processor, cause the electronic device to identify the authentication information from the memory or obtain the authentication information from a second server based on the receipt of the ticket information.

[0092] According to one embodiment, the memory may store instructions that, when executed individually or collectively by the at least one processor, cause the electronic device to request the authentication information from the second server through the communication unit based on information used to unlock the electronic device, and to receive the authentication information from the second server through the communication unit in response to the request.

[0093] According to one embodiment, the memory may store instructions that, when executed individually or collectively by the at least one processor, cause the electronic device to transmit a message to the first server through the communication unit indicating that the first ticket cannot be registered as a ticket of the electronic device, based on the fact that the user information does not correspond to the authentication information.

[0094] According to one embodiment, the user information includes information input by the external electronic device, or authentication information obtained by the first server from the second server based on information input by the external electronic device, and the information input by the external electronic device may include phone number information or account information.

[0095] According to one embodiment, the memory may store instructions that, when executed individually or collectively by the at least one processor, cause the electronic device to receive updated ticket information from the first server through the communication unit, wherein the updated ticket information represents information generated by updating at least a part of the ticket information, and to transmit a reception completion message to the first server through the communication unit indicating that the updated ticket information has been received.

[0096] According to one embodiment, the memory may store instructions that, when executed individually or collectively by the at least one processor, cause the electronic device to transmit the updated ticket information to at least one other electronic device through the communication unit.

[0097] According to one embodiment, the memory stores instructions that, when executed individually or collectively by the at least one processor, cause the electronic device to receive the updated ticket information from the first server based on a first communication method through the communication unit, and to transmit the updated ticket information to the at least one other electronic device based on a second communication method, wherein the second communication method is different from the first communication method and may include a short-range communication method.

[0098] According to one embodiment, the memory may store instructions that, when executed individually or collectively by the at least one processor, cause the electronic device to receive advertising information associated with the location where the second ticket was used from the first server via the communication unit based on the external electronic device having used the second ticket among the plurality of tickets, and to output an advertisement corresponding to the advertising information to the display based on whether the location of the electronic device corresponds to the location.

[0099] According to one embodiment, the memory stores instructions that, when executed individually or collectively by the at least one processor, cause the electronic device to receive a message from the first server instructing it to adjust the priority of the first ticket through the communication unit based on the external electronic device having used the second ticket among the plurality of tickets, and to adjust the priority of the first ticket based on the received message, and the priority of the first ticket can be adjusted to place the first ticket in a position where it can be used most preferentially in an application for ticket usage.

[0100] FIG. 5 is a schematic diagram illustrating a ticket grouping system according to one embodiment.

[0101] Referring to FIG. 5, a ticket grouping system (500) according to one embodiment may include a first electronic device (510), a second electronic device (520), a partner server (530), a wallet server (540), an authentication server (550), or a store (560).

[0102] According to one embodiment, the first electronic device (510) and the second electronic device (520) may each be configured as the electronic device (301) of FIG. 3 and may include the mobile wallet module (400) shown in FIG. 4. According to one embodiment, the first electronic device (510) and the second electronic device (520) may be electronic devices of the same type or electronic devices of different types. For example, the first electronic device (510) and the second electronic device (520) may both be mobile devices such as smartphones, or the first electronic device (510) may be a mobile device and the second electronic device (520) may be a wearable device (e.g., a smart watch).

[0103] According to one embodiment, the first electronic device (510) and the second electronic device (520) can each communicate with a partner server (530), a wallet server (540), or an authentication server (550) on the network.

[0104] According to one embodiment, the partner server (530) may represent a server that sells tickets that can be registered in a wallet application (e.g., an online or offline merchant server). For example, the first electronic device (510) may connect to the partner server (530) to purchase one or more tickets. According to one embodiment, the first electronic device (510) may be designated as a group representative based on having purchased a plurality of groupable tickets, and the second electronic device (520), which may share any one of the plurality of tickets, may be designated as a group member. According to one embodiment, the plurality of groupable tickets may represent tickets that include identical or similar attribute information (e.g., time or schedule, place or location of use, origin, destination, or partner company information). According to one embodiment, the group member may include at least one additional electronic device in addition to the second electronic device (520).

[0105] According to one embodiment, the wallet server (540) is an application server associated with the wallet application and can support various functions of the wallet application. For example, the wallet server (540) may receive information from the partner server (530) and perform operations for sharing ticket information between the first electronic device (510) and the second electronic device (520), or perform operations for ticket registration, ticket grouping, ticket status management and control, or providing ticket-related advertisements.

[0106] According to one embodiment, the authentication server (550) may provide user authentication information of the first electronic device (510) or the second electronic device (520). According to one embodiment, user authentication information is information used to identify or authenticate a user and may include various information such as the user's personal information (e.g., name, phone number (or mobile phone number), address, or account information), identification information, password, certification information, biometric information (e.g., fingerprint information, iris information, or facial information), or PIN number. According to one embodiment, the authentication server (550) may include various types of authentication servers, such as an OAuth authentication server for user authentication and authorization, an OpenID connect authentication server that provides user authentication and user information (e.g., profile information such as user ID, username, or account information), or a FIDO (fast identity online) authentication server that performs authentication based on biometric authentication or a security key.

[0107] According to one embodiment, the store (560) may represent an online or offline store (e.g., a merchant), a service agency, a paid admission facility, or a transportation facility where tickets can be used. For example, the store (560) may represent a place where tickets need to be used, such as a movie theater, a performance venue, an exhibition hall, a museum, a stadium, an amusement park, an airport, a terminal, or a train station.

[0108] According to one embodiment, the store (560) may be associated with the partner server (530). For example, when a ticket is used in the store (560), the result of the ticket's use may be provided to the partner server (530).

[0109] Various operations performed in the ticket grouping system (500) configured as shown in FIG. 5 are described below.

[0110] FIG. 6 is a flowchart illustrating the operation of registering grouped tickets in each electronic device according to one embodiment.

[0111] Referring to FIG. 6, in operation 602, the first electronic device (510) can connect to a partner server (530) to purchase tickets. According to one embodiment, the first electronic device (510) can purchase multiple tickets through offline or online stores, or through payment using a wallet application. For example, the multiple tickets may correspond to airplane, train, or bus tickets that have the same departure time and mode of transport (e.g., flight number, train code, or bus number) but different seats, and may be grouped into one group.

[0112] In operation 604, the first electronic device (510) may transmit group information to the partner server (530). According to one embodiment, the group information may include information about group members entered by the first electronic device (510) (or a user of the first electronic device (510)). According to one embodiment, the information about group members may include information about users who will use a plurality of grouped tickets. For example, the information about users may include identification information about the user of each ticket (e.g., name, address, or account information) and identification information of the electronic device used by each user (e.g., phone number or mobile phone number). According to one embodiment, the information about users may include ID information, password, or PIN number associated with the user or electronic device.

[0113] In operation 606, the partner server (530) can transmit ticket information and group information (e.g., user identification information and electronic device identification information) for multiple tickets to the wallet server (540).

[0114] In operation 608, the wallet server (540) can identify an electronic device associated with the user of each ticket based on ticket information and group information for multiple tickets, and share ticket information with the identified electronic device. For example, the wallet server (540) can share ticket information corresponding to the first ticket among multiple tickets with the second electronic device (520).

[0115] According to one embodiment, the ticket information may include information about the first ticket and user information. For example, the user information may include group member information (e.g., name, address, account information, phone number or mobile phone number) of the second electronic device (520) included in the group information and / or user authentication information. According to one embodiment, the user authentication information may be information obtained by the wallet server (540) from the authentication server (550) based on the group member information (e.g., account information, phone number, or mobile phone number) of the second electronic device (520). For example, the user authentication information may include ID information, password, CI, biometric information, or PIN number associated with the user or the second electronic device (520).

[0116] According to one embodiment, the wallet server (540) may repeat operation 608 as many times as the number of electronic devices to share ticket information for a plurality of tickets with each corresponding electronic device.

[0117] In operation 610, the second electronic device (520) may perform unlocking of the second electronic device (520) or wallet application based on a set method. According to one embodiment, the second electronic device (520) or wallet application may be locked to block unintended external access or access by unauthorized users, or to protect the functions or information of the second electronic device (520) or wallet application. When a lock is set, the use of the functions of the second electronic device (520) or wallet application may be restricted, and it may be impossible to use information stored in the second electronic device (520) or wallet application or information provided through the second electronic device (520) or wallet application.

[0118] According to one embodiment, the lock of the second electronic device (520) or wallet application may be unlocked through authentication of a set method. For example, the set method is a method used to identify or authenticate an allowed user and may include a biometric recognition method involving a fingerprint, iris, or face, a PIN number input method, or a pattern input method.

[0119] According to one embodiment, if an allowed user is identified or authenticated based on a set method, the second electronic device (520) or wallet application may be unlocked. Based on the unlocking of the second electronic device (520) or wallet application, the allowed user may use the functions of the second electronic device (520) or wallet application and may use information stored in the second electronic device (520) or wallet application or information provided through the second electronic device (520) or wallet application.

[0120] In operation 612, the second electronic device (520) may request authentication information for the user of the second electronic device (520) from the authentication server (550) based on the information used for unlocking (e.g., fingerprint information, iris information, face information, PIN number, or pattern information). According to one embodiment, the second electronic device (520) may request authentication information using information other than the information used for unlocking. For example, after unlocking, the second electronic device (520) may display a message for additional authentication or user authentication, and request authentication information for the user of the second electronic device (520) from the authentication server (550) based on the information entered in response to the displayed message (e.g., fingerprint information, iris information, face information, PIN number, or pattern information).

[0121] In operation 614, the second electronic device (520) may receive authentication information from the authentication server (550) in response to a request for authentication information. According to one embodiment, the second electronic device (520) may receive authentication information based on the fact that the information used for the authentication information request (e.g., fingerprint information, iris information, face information, PIN number, or pattern information) matches the information stored in the authentication server (550). According to one embodiment, the authentication information may include identification information for the user of the second electronic device (520) (e.g., name, address, or account information) and identification information of the second electronic device (520) (e.g., phone number or mobile phone number). According to one embodiment, the authentication information may include ID information, password, CI, biometric information, or PIN number associated with the user or the second electronic device (520). According to one embodiment, if the information used for the authentication information request does not match the information stored in the authentication server (550), the second electronic device (520) may receive a message indicating that the authentication information cannot be received and that the authentication information cannot be provided.

[0122] In operation 616, the second electronic device (520) can perform a ticket validity check based on the received authentication information. According to one embodiment, the second electronic device (520) can determine whether user information included in the ticket information corresponds to the received authentication information. According to one embodiment, the second electronic device (520) can determine that the first ticket corresponding to the ticket information is a valid ticket (or a registrable ticket) for the second electronic device (520) based on whether the user information included in the ticket information corresponds to the received authentication information.

[0123] In operation 618, the second electronic device (520) may register ticket information for the first ticket with the wallet server (540) as ticket information associated with the second electronic device (520), based on the determination that the first ticket is a valid ticket. According to one embodiment, based on the registration of ticket information, the first ticket may be added and displayed in the wallet application of the second electronic device (520). According to one embodiment, the first ticket may be displayed in the form of a card or in a form similar to a physical ticket, but is not limited thereto and may be displayed in various forms.

[0124] In operation 620, the wallet server (540) may generate ticket group information based on registered ticket information. For example, the ticket group information may include information in which the first ticket and the second ticket registered for each of the second electronic device (520) and the first electronic device (510) are grouped.

[0125] In operation 622, the wallet server (540) may instruct the first electronic device (510) to change the ticket status for each ticket (e.g., first ticket and second ticket) included in the ticket group information to 'registered status' based on the ticket group information generated. The first electronic device (510) may change the ticket status for each ticket (e.g., first ticket and second ticket) included in the ticket group information to 'registered status' based on the instruction of the wallet server (540).

[0126] FIG. 7a is a flowchart illustrating the operation of registering grouped tickets based on communication between electronic devices according to one embodiment.

[0127] Referring to FIG. 7a, according to one embodiment, ticket information can be shared based on communication between electronic devices.

[0128] In operation 702, the first electronic device (510) can access the partner server (530) to purchase tickets. According to one embodiment, the first electronic device (510) can purchase multiple tickets through offline or online stores, or through payment using a wallet application. For example, the multiple tickets may correspond to airplane, train, or bus tickets that have the same departure time and mode of transport (e.g., flight number, train code, or bus number) but different seats, and may be grouped into one group.

[0129] In operation 708, the first electronic device (510) selects a first ticket among a plurality of tickets and can share ticket information corresponding to the first ticket with the second electronic device (520). According to one embodiment, the first ticket may be selected based on user input. For example, the first ticket may be shared based on the selection of at least one of an icon, menu, button, or graphic object for ticket sharing provided in a wallet application. According to one embodiment, ticket information corresponding to the first ticket may include user information input by the first electronic device (510).

[0130] According to one embodiment, based on the fact that ticket information corresponding to the first ticket is shared with the second electronic device (520), operations 710 to 722 related to the ticket information registration operation may be performed. Since operations 710 to 722 correspond to operations 610 to 622 of FIG. 6, a detailed description will be omitted.

[0131] In the aforementioned FIGS. 6 and 7a, operations when the validity check of the first ticket is successful have been described. According to one embodiment, when the validity check of the first ticket fails, operations as shown in FIG. 7b may be performed.

[0132] FIG. 7b is a flowchart illustrating the operation when the validity check of grouped tickets fails according to one embodiment.

[0133] Referring to FIG. 7b, in operation 732, the second electronic device (520) can perform a ticket validity check. According to one embodiment, operation 732 may correspond to operation 616 of FIG. 6 or operation 716 of FIG. 7a.

[0134] According to one embodiment, the second electronic device (520) may receive ticket information shared by the wallet server (540) or the first electronic device (510). The second electronic device (520) may perform a ticket validity check based on whether the user information included in the ticket information corresponds to the authentication information of the second electronic device (520) received from the authentication server (550).

[0135] According to one embodiment, the second electronic device (520) may determine that the first ticket corresponding to the ticket information is an invalid ticket (or a ticket that cannot be registered) for the second electronic device (520) based on the fact that the user information included in the ticket information does not correspond to the authentication information of the second electronic device (520). Based on this, the second electronic device (520) may determine that the ticket validity check has failed and perform operation 734.

[0136] In operation 734, the second electronic device (520) may send a message (e.g., a registration failure message) to the wallet server (540) indicating that ticket registration is impossible or failed due to information discrepancy or user authentication failure, based on the fact that the ticket validity check failed.

[0137] In operation 736, the wallet server (540) may notify the first electronic device (510) that ticket registration is impossible or failed due to information discrepancy or user authentication failure, and request that the group member information be reconfirmed. According to one embodiment, when the group member information is re-entered by the first electronic device (510), the ticket sharing operation as illustrated in FIGS. 6 and FIGS. 7a may be performed again.

[0138] FIG. 8 is a diagram illustrating group information input by a first electronic device according to one embodiment.

[0139] According to one embodiment, the first electronic device (510) may purchase a plurality of tickets and input group information for the purchased plurality of tickets. For example, the group information may include information about group members input by the first electronic device (510) (or a user of the first electronic device (510)).

[0140] According to one embodiment, the first electronic device (510) can input ticket-specific group member information as illustrated in FIG. 8 (a) to (c) based on purchasing three tickets (e.g., airplane tickets with the same schedule, same destination, or same flight number).

[0141] FIG. 8(a) illustrates group member information (or user information) for Ticket 1. For example, the group member information for Ticket 1 may include a name (e.g., Hong Gil-dong), a phone number (e.g., 010-111-1111), an address (e.g., Seoul...), and account information (aaa@sam.com). The group member information for Ticket 1 may also display information about Ticket 1. For example, the information about Ticket 1 may be displayed as a boarding pass in the form of a card and may include departure information (e.g., CJU), destination information (e.g., GMP), departure date (e.g., 2024.10.20), departure time (e.g., 09:30), flight number (e.g., A123), boarding gate (e.g., 4), terminal (e.g., 5), or seat information (e.g., 11A).

[0142] FIG. 8(b) illustrates group member information for Ticket 2. For example, the group member information for Ticket 2 may include a name (e.g., Kim Cheol-su), a phone number (e.g., 010-222-2222), an address (e.g., Gyeonggi-do...), and account information (bbb@sam.com). The group member information for Ticket 2 may also display information about Ticket 2. For example, the information about Ticket 2 may be displayed as a boarding pass in the form of a card and may include departure information (e.g., CJU), destination information (e.g., GMP), departure date (e.g., 2024.10.20), departure time (e.g., 09:30), flight number (e.g., A123), boarding gate (e.g., 4), terminal (e.g., 5), or seat information (e.g., 11B).

[0143] FIG. 8(c) illustrates group member information for Ticket 3. For example, the group member information for Ticket 3 may include a name (e.g., Lee Young-hee), a phone number (e.g., 010-333-3333), an address (e.g., Seoul...), and account information (ccc@sam.com). The group member information for Ticket 3 may also display information about Ticket 3. For example, the information about Ticket 3 may be displayed as a boarding pass in the form of a card and may include departure information (e.g., CJU), destination information (e.g., GMP), departure date (e.g., 2024.10.20), departure time (e.g., 09:30), flight number (e.g., A123), boarding gate (e.g., 4), terminal (e.g., 5), or seat information (e.g., 11C).

[0144] According to one embodiment, the phone number (or mobile phone number) and / or account information included in each group member information may be used as information or a user identification key to identify each user or each electronic device, and may be set as required input information. According to one embodiment, the phone number and / or account information may be used for identity verification, or for looking up or issuing authentication information. According to one embodiment, the phone number and / or account information may be used for checking ticket validity, or for obtaining user authentication information for checking ticket validity. For example, the wallet server (540) may obtain user authentication information for a group member from the authentication server (550) as information for checking ticket validity based on the phone number and / or account information.

[0145] FIG. 9 is a flowchart illustrating the operation of each electronic device receiving changed information of a ticket according to one embodiment.

[0146] Referring to FIG. 9, in operation 902, the partner server (530) can transmit information that has been changed in association with the grouped tickets to the wallet server (540). According to one embodiment, the changed information may include information that has been changed due to the circumstances of the partner company. For example, if the grouped tickets are airplane tickets, the changed information may include information on departure times that have been delayed due to environmental factors such as weather, or gate information that has been changed due to internal airport conditions.

[0147] According to one embodiment, the wallet server (540) may transmit the changed information to electronic devices used by the group members in order to notify the group members of the changed information received from the partner server (530). For example, the wallet server (540) may transmit the changed information to the first electronic device (510) in operation 904 and transmit the changed information to the second electronic device (520) in operation 906.

[0148] In operation 908, the first electronic device (510) may transmit a receipt completion message to the wallet server (540) based on receiving the changed information. According to one embodiment, the first electronic device (510) may update the ticket information of the first electronic device (510) based on receiving the changed information. For example, if the ticket information of the first electronic device (510) corresponds to the information for ticket 1 shown in FIG. 8 (a) and the changed information indicates the changed terminal information (e.g., terminal 3), the first electronic device (510) may update the information for ticket 1 to include terminal 3 instead of terminal 5.

[0149] In operation 910, the second electronic device (520) may transmit a receipt completion message to the wallet server (540) based on receiving the changed information. According to one embodiment, the second electronic device (520) may update the ticket information of the second electronic device (520) based on receiving the changed information. For example, if the ticket information of the second electronic device (520) corresponds to the information for ticket 2 shown in FIG. 8 (b) and the changed information indicates the changed terminal information (e.g., terminal 3), the second electronic device (520) may update the information for ticket 2 to include terminal 3 instead of terminal 5.

[0150] In operation 912, the wallet server (540) may instruct the first electronic device (510) to change the ticket status of each of the first electronic device (510) and the second electronic device (520) to 'Received Successfully' based on receiving a received message from the group members, the first electronic device (510) and the second electronic device (520), respectively. According to one embodiment, the first electronic device (510) may change the status of the group members' tickets to 'Received Successfully' based on the instruction of the wallet server (540). According to one embodiment, 'Received Successfully' may indicate a state in which changed information has been received, or a state in which ticket information has been updated based on the changed information.

[0151] In operation 914, the wallet server (540) may instruct the second electronic device (520) to change the ticket status to 'receipt successful' so that the ticket status in the second electronic device (520) may also be managed as 'receipt successful'. According to one embodiment, the second electronic device (520) may change the ticket status of the second electronic device (520) to 'receipt successful' without instructions from the wallet server (540), based on receiving the information changed in operation 906 or sending a reception completion message to the wallet server (540) in operation 910.

[0152] FIG. 10 is a flowchart illustrating the operation of sharing changed ticket information between electronic devices according to one embodiment.

[0153] Referring to FIG. 10, in operation 1002, the partner server (530) can transmit information that has been changed in association with the grouped tickets to the wallet server (540). According to one embodiment, the changed information may include information that has been changed due to the circumstances of the partner company. For example, if the grouped tickets are airplane tickets, the changed information may include information on departure times that have been delayed due to environmental factors such as weather, or gate information that has been changed due to internal airport conditions.

[0154] According to one embodiment, the wallet server (540) may transmit the changed information to electronic devices used by the group members in order to notify the group members of the changed information received from the partner server (530). For example, the wallet server (540) may transmit the changed information to the first electronic device (510) in operation 1004 and transmit the changed information to the second electronic device (520) in operation 1006.

[0155] In operation 1008, the first electronic device (510) can send a reception completion message to the wallet server (540) based on receiving the changed information.

[0156] In operation 1009, the second electronic device (520) may not receive changed information from the wallet server (540) based on the fact that communication (e.g., mobile communication) with the wallet server (540) is not smooth or impossible.

[0157] According to one embodiment, a first electronic device (510) and a second electronic device (520) may be connected to enable short-range communication (e.g., UWB, Wi-Fi, or Bluetooth). Based on this, in operation 1010, the first electronic device (510) may transmit changed information to the second electronic device (520). According to one embodiment, the first electronic device (510) may transmit changed information to the second electronic device (520) based on at least one of an icon, menu, button, or graphic object for sharing changed information on a wallet application being selected by the user.

[0158] In operation 1012, the second electronic device (520) can transmit a reception completion message to the first electronic device (510) based on receiving changed information from the first electronic device (510).

[0159] In operation 1014, the first electronic device (510) can change the ticket status of each of the first electronic device (510) and the second electronic device (520) to 'reception successful' based on the fact that the first electronic device (510) and the second electronic device (520) have received changed information.

[0160] In operation 1016, the first electronic device (510) may send a receipt completion message to the wallet server (540) to indicate that the second electronic device (520) has received changed information, based on the fact that the first electronic device (510) has received a receipt completion message from the second electronic device (520).

[0161] FIG. 11 is a flowchart illustrating the operation of electronic devices using a ticket according to one embodiment.

[0162] Referring to FIG. 11, in operation 1102, the first electronic device (510) can run a wallet application and open a ticket. According to one embodiment, opening a ticket may include opening a ticket registered in the wallet application based on an authentication operation such as biometric authentication, pattern authentication, or PIN number input. According to one embodiment, the opened ticket may be grouped with a ticket of the second electronic device (520).

[0163] In operation 1104, the first electronic device (510) can use the opened ticket at a store (e.g., an electronic device on a paid admission facility or transportation facility) (560). For example, if the opened ticket is an airplane ticket, the opened ticket can be used for check-in when boarding the airplane.

[0164] In operation 1106, the store (560) can send a ticket usage completion message to the partner server (530) based on the fact that the ticket of the first electronic device (510) has been used.

[0165] In operation 1108, the partner server (530) may send a message to the wallet server (540) indicating that the ticket of the first electronic device (510) has been used, based on receiving a ticket usage completion message.

[0166] In operation 1110, the first electronic device (510) can change the status of the ticket of the first electronic device (510) to 'used' based on the fact that the ticket of the first electronic device (510) has been used in operation 1104.

[0167] In operation 1112, the wallet server (540) can identify the group member, the second electronic device (520), based on the fact that the ticket of the first electronic device (510) has been used, and look up advertisements associated with the ticket of the first electronic device (510). For example, the wallet server (540) can look up advertisements based on the location where the ticket of the first electronic device (510) was used or ticket information. According to one embodiment, the advertisement lookup can be performed from advertisements stored in the wallet server (540) or an external advertisement server.

[0168] In operation 1114, the wallet server (540) performs an operation to adjust the ticket priority of the second electronic device (520) and can transmit the retrieved advertisement (e.g., an advertisement image or video) to the second electronic device (520).

[0169] According to one embodiment, the operation of adjusting ticket priority may include the wallet server (540) sending a ticket priority adjustment message to the second electronic device (520) to increase the ticket priority of the second electronic device (520). For example, the ticket priority adjustment message may instruct the second electronic device (520) to set the priority of its ticket to the highest priority so that the ticket of the second electronic device (520) can be used preferentially as the ticket of the first electronic device (510) of the same group is used.

[0170] In operation 1116, the second electronic device (520) can display tickets with adjusted priority based on the ticket priority adjustment message and output advertisements received from the wallet server (540).

[0171] According to one embodiment, the second electronic device (520) can adjust the priority of the ticket of the second electronic device (520) to the highest priority based on a ticket priority adjustment message and display the ticket at a location based on the adjusted priority. For example, the location based on the adjusted priority may include a location where the ticket can be selected or used most quickly, or a location where a representative ticket is displayed on the execution screen of a wallet application (e.g., the top of the execution screen).

[0172] According to one embodiment, the second electronic device (520) may immediately display an advertisement received from the wallet server (540), but may also display it considering the location of the second electronic device (520). For example, if the received advertisement (e.g., an advertisement for a store in an airport) is associated with the place where the ticket of the first electronic device (510) was used (e.g., an airport) and the location of the second electronic device (520) is associated with that place, the second electronic device (520) may display the advertisement received from the wallet server (540) on the screen of the second electronic device (520). If the location of the second electronic device (520) is not associated with that place, the second electronic device (520) may not display the advertisement received from the wallet server (540) on the screen of the second electronic device (520).

[0173] In operation 1118, the second electronic device (520) can use the ticket in the store (560). According to one embodiment, the second electronic device (520) can open the ticket by running a wallet application and use the opened ticket in the store (560).

[0174] In operation 1120, the store (560) can send a ticket usage completion message to the partner server (530) based on the fact that the ticket of the second electronic device (520) has been used.

[0175] In operation 1122, the partner server (530) may send a message to the wallet server (540) indicating that the ticket of the second electronic device (520) has been used, based on receiving a ticket usage completion message.

[0176] In operation 1124, the wallet server (540) may send a message to the first electronic device (510) instructing it to change the status of the ticket of the second electronic device (520) to 'used' based on the fact that the ticket of the second electronic device (520) has been used. The first electronic device may change the status of the ticket of the second electronic device (520) to 'used' based on the message received from the wallet server (540).

[0177] FIG. 12 is a diagram illustrating a screen of a wallet application displaying a group ticket according to one embodiment.

[0178] According to one embodiment, based on the fact that a plurality of tickets are purchased as group tickets in the first electronic device (510), a screen of a wallet application such as (a) of FIG. 12 may be displayed.

[0179] Referring to FIG. 12 (a), a group ticket (or group ticket information) (1210) may be displayed on the execution screen of the wallet application. For example, if the group ticket (120) is an airplane ticket, the group ticket (1210) may include information for multiple tickets, such as a ticket name (e.g., Samsung Airlines boarding pass), seat information (e.g., seats 14A–14E), status information (e.g., status: Available), departure and arrival information (e.g., INC → FRA), departure time information (e.g., 19:00), or gate information (e.g., Gate A).

[0180] According to one embodiment, a group ticket (1210) may include common information for a plurality of tickets (e.g., ticket name, departure and arrival information, departure time information, or gate information) and individual information for a plurality of tickets (e.g., seat number assigned to each of the plurality of tickets, or status information for each of the plurality of tickets).

[0181] According to one embodiment, if the status information of a plurality of tickets is the same, common status information (e.g., status: Available) may be displayed on the group ticket (1210), and if the status information of a plurality of tickets is different, the status information of each of the plurality of tickets may not be displayed on the group ticket (1210).

[0182] According to one embodiment, the status information of each of the plurality of tickets may include any one of the following: first information indicating that it is in a state before use or available (e.g., Available), second information indicating that it is in a state of completed use (e.g., Used), third information indicating that the reception of ticket information or changed information or update information of the ticket is completed (e.g., Reception Success), or fourth information indicating that the reception of ticket information or changed information or update information of the ticket is not completed or has failed (e.g., Reception Failure).

[0183] According to one embodiment, a group ticket (1210) may display a sharing icon (or sharing menu, button, or graphic object) (1211) for sharing any one of a plurality of tickets. When the sharing icon (1211) is selected by user input (e.g., touch input), the first electronic device (510) may provide a menu that allows selecting any one of a plurality of tickets. When any one of a plurality of tickets is selected and an electronic device (e.g., a second electronic device (520)) to share the selected ticket is determined, the first electronic device (510) may transmit information about the selected ticket to the determined electronic device. According to one embodiment, based on the selection of the sharing icon (1211), a ticket sharing and ticket registration process may be performed based on operations 708 to 722 of FIG. 7.

[0184] According to one embodiment, a group ticket management interface may be displayed on the execution screen of the wallet application after ticket sharing. For example, the group ticket management interface may be as shown in (b) of FIG. 12.

[0185] Referring to FIG. 12(b), the group ticket management interface may include unshared tickets (1212) and shared tickets (1220)(1230). According to one embodiment, a share icon may be displayed on unshared tickets (1212), and a share icon may not be displayed on shared tickets (1220)(1230).

[0186] According to one embodiment, the shared tickets (1220)(1230) may display group information (e.g., Group 1) to indicate that they are grouped tickets. The unshared tickets (1212) and the shared tickets (1220)(1230) may include common information such as a ticket name (e.g., Samsung Airlines boarding pass), departure and arrival information (e.g., INC → FRA), departure time information (e.g., 19:00), or gate information (e.g., Gate A). The unshared tickets (1212) and the shared tickets (1220)(1230) may include individual information such as seat information (e.g., seats 14A–14E) and status information (e.g., status: Available).

[0187] According to one embodiment, the first electronic device (510) can change the status information of the ticket of the first electronic device (510) based on whether the ticket of the first electronic device (510) has been used through a wallet application. The first electronic device (510) can change the status information of at least one other ticket based on a ticket status change instruction message received from a wallet server (540).

[0188] The operation of an electronic device (e.g., the electronic device (301) of FIG. 3) will be described below with reference to FIG. 13 to 17. The operations of the electronic device described below may be understood as being performed by the processor (340) of the electronic device. The operations shown in FIG. 13 to 17 may be performed in various orders, not limited to the order shown. According to one embodiment, at least some of the operations shown in FIG. 13 to 17 may be omitted, or more operations may be performed than those shown in FIG. 13 to 17.

[0189] FIG. 13 is a flowchart illustrating the ticket registration operation of an electronic device according to one embodiment.

[0190] Referring to FIG. 13, in operation 1302, an electronic device may receive ticket information. According to one embodiment, the electronic device may receive ticket information from a first server (e.g., a wallet server (540)) or an external electronic device. According to one embodiment, the ticket information may represent information regarding a first ticket among a plurality of tickets purchased by the external electronic device. According to one embodiment, the plurality of tickets may be grouped and managed by the first server, and status information may be managed by the external electronic device.

[0191] In operation 1304, the electronic device can determine whether user information included in the ticket information corresponds to the authentication information of the electronic device. According to one embodiment, the user information included in the ticket information may include information input by an external electronic device for each ticket. For example, the user information included in the ticket information may include information such as that shown in FIG. 12 (e.g., user name, phone number, address, or account information). According to one embodiment, the user information included in the ticket information may include user authentication information (e.g., ID information, password, CI, biometric information, or PIN number associated with the user or electronic device) obtained by the first server from the second server (e.g., authentication server (550)).

[0192] According to one embodiment, the authentication information of the electronic device may be authentication information stored in the memory of the electronic device (e.g., memory (330) of FIG. 3) or authentication information obtained from a second server (e.g., authentication server (550)).

[0193] According to one embodiment, an electronic device may request authentication information from a second server based on information used to unlock the electronic device (e.g., fingerprint information, iris information, facial information, PIN number, or pattern information), and receive authentication information from the second server in response to the request. For example, the authentication information of the electronic device may include a name, phone number, address, or account information regarding the user of the electronic device.

[0194] In operation 1306, the electronic device may register a first ticket corresponding to ticket information as a ticket of the electronic device to the first server based on the fact that user information corresponds to authentication information. According to one embodiment, based on the registration of the first ticket, the first ticket may be added and displayed as a usable ticket in the wallet application of the electronic device. According to one embodiment, the first ticket may be displayed in the form of a card or in a form similar to a physical ticket, but is not limited thereto and may be displayed in various forms.

[0195] FIG. 14 is a flowchart illustrating the operation of an electronic device according to one embodiment transmitting a message indicating that ticket registration is not possible.

[0196] Referring to FIG. 14, in operation 1402, an electronic device may receive ticket information. According to one embodiment, the electronic device may receive ticket information from a first server (e.g., a wallet server (540)) or an external electronic device. According to one embodiment, the ticket information may represent information regarding a first ticket among a plurality of tickets purchased by the external electronic device. According to one embodiment, the plurality of tickets may be grouped and managed by the first server, and status information may be managed by the external electronic device.

[0197] In operation 1404, the electronic device can determine whether user information included in the ticket information corresponds to the authentication information of the electronic device. According to one embodiment, the user information included in the ticket information may be information entered by an external electronic device on a per-ticket basis. For example, the user information included in the ticket information may include information such as that shown in FIG. 12 (e.g., user name, phone number, address, or account information).

[0198] According to one embodiment, the authentication information may be authentication information stored in the memory of an electronic device (e.g., memory (330) of FIG. 3) or authentication information obtained from a second server (e.g., authentication server (550)).

[0199] According to one embodiment, an electronic device may request authentication information from a second server based on information used to unlock the electronic device (e.g., fingerprint information, iris information, facial information, PIN number, or pattern information), and receive authentication information from the second server in response to the request. For example, the authentication information of the electronic device may include a name, phone number, address, or account information regarding the user of the electronic device.

[0200] In operation 1406, the electronic device may transmit a message to the first server indicating that the first ticket corresponding to the ticket information cannot be registered as the electronic device's ticket, based on the fact that the user information does not correspond to the authentication information. According to one embodiment, the first server may notify an external electronic device based on the message from the electronic device that there is an error or problem with the user information included in the ticket information. Based on this, the external electronic device may correct the user information included in the ticket information so that the first ticket is accurately delivered to the corresponding user.

[0201] FIG. 15 is a flowchart illustrating the operation of an electronic device receiving and sharing an updated ticket according to one embodiment.

[0202] Referring to FIG. 15, in operation 1502, the electronic device may receive updated ticket information from a first server (e.g., wallet server (540)). According to one embodiment, the updated ticket information may represent information generated by updating at least a portion of the registered ticket information (e.g., departure time or gate information).

[0203] In operation 1504, the electronic device may send a message of receipt of the updated ticket information to the first server based on receiving the updated ticket information.

[0204] In operation 1506, the electronic device may determine whether to share updated ticket information. According to one embodiment, the electronic device is connected to at least one electronic device for short-range communication (e.g., UWB, Wi-Fi, or Bluetooth communication) and may determine to share updated ticket information with at least one electronic device based on receiving an input for sharing updated ticket information (e.g., touch input or key input by a user).

[0205] In operation 1508, the electronic device may transmit the updated ticket information to at least one electronic device based on the determination to share the updated ticket information with at least one electronic device. According to one embodiment, the electronic device transmits the updated ticket information to at least one electronic device and may receive a reception completion message for the updated ticket information from at least one electronic device. Based on this, the electronic device may transmit a reception completion message to a first server to indicate that at least one electronic device has received the updated ticket information. According to one embodiment, the electronic device may change the status information of each ticket to 'reception successful' based on the fact that the electronic device and at least one electronic device have received the updated ticket information.

[0206] According to one embodiment, if the electronic device is not connected to at least one electronic device for short-range communication or if no input for sharing updated ticket information is received, it may decide not to share the updated ticket information with at least one electronic device and terminate the operation.

[0207] FIG. 16 is a flowchart illustrating the operation of an electronic device according to one embodiment outputting an advertisement based on location.

[0208] Referring to FIG. 16, in operation 1602, the electronic device can receive advertising information (or advertising data) associated with the ticket usage location of an external electronic device.

[0209] In operation 1604, the electronic device can determine whether the location of the electronic device corresponds to the ticket usage location of the external electronic device. According to one embodiment, information regarding the ticket usage location of the external electronic device may be indicated by received advertisement information or may be information additionally received in operation 1602.

[0210] In operation 1606, the electronic device can output an advertisement based on received advertisement information (e.g., an advertisement for a cafe inside an amusement park) based on the fact that the location of the electronic device corresponds to the ticket usage location of an external electronic device (e.g., an amusement park).

[0211] In operation 1608, the electronic device may not display an advertisement based on received advertisement information based on the fact that the location of the electronic device does not correspond to the ticket usage location of the external electronic device.

[0212] As mentioned above, it is possible to enhance advertising effectiveness and provide convenience to users through advertising output based on the location of electronic devices.

[0213] FIG. 17 is a flowchart illustrating the operation of an electronic device according to one embodiment adjusting ticket priority to display tickets.

[0214] Referring to FIG. 17, in operation 1702, the electronic device may receive a priority adjustment message based on the use of tickets by an external electronic device. According to one embodiment, a plurality of tickets included in a group ticket may include common schedule information or be used at similar times. Thus, based on the use of any one of the plurality of tickets, a priority adjustment message for the quick use of the remaining tickets may be received.

[0215] In operation 1704, the electronic device may adjust the priority of the electronic device’s tickets based on a received priority adjustment message. For example, the electronic device may adjust the priority of the electronic device’s tickets to a higher priority than the set priority, or to the highest priority.

[0216] In operation 1706, the electronic device may display tickets at locations based on adjusted ticket priority on an application screen (e.g., the execution screen of a wallet application). According to one embodiment, locations based on adjusted ticket priority may include locations where tickets can be selected or used most quickly, or locations where representative tickets are displayed on the execution screen of the wallet application (e.g., the top of the execution screen). According to one embodiment, the electronic device may implement various effects associated with the UI (e.g., highlight effects or emphasis effects) on tickets, with or without changing the location of the tickets, based on the adjusted ticket priority. For example, the electronic device may display high-priority tickets in a different color or size than low-priority tickets. Alternatively, the electronic device may enable high-priority tickets to be selected or used more quickly by the user by displaying indicators (e.g., graphic objects or icons) or messages on high-priority tickets or by implementing animation effects.

[0217] Various embodiments can improve the convenience of using tickets. For example, when any one of a group of multiple tickets is used on an electronic device, user convenience can be maximized by adjusting the priority of at least one other electronic device.

[0218] Various embodiments can enhance security when sharing tickets. For example, when sharing tickets, the validity of the shared ticket can be verified by comparing user information included in the ticket (e.g., user's personal information) with authentication information of an electronic device. This can effectively prevent the misuse or indiscriminate sharing of tickets.

[0219] Various embodiments can enable information sharing (e.g., sharing ticket information or updated ticket information) even if communication among all grouped electronic devices is not smooth. For example, even if only one of the grouped electronic devices is able to communicate at a travel destination in multiple countries, it becomes possible to transmit information to be shared to the remaining electronic devices that are unable to communicate smoothly. This enables efficient information sharing.

[0220] Various embodiments can provide real-time status monitoring for multiple tickets. For example, by providing the status of each ticket included in a group ticket in real time within a wallet application, the group ticket manager may be able to manage the status of the group ticket more conveniently.

[0221] Various embodiments can enable the establishment of customized advertising strategies. For example, since the location and purpose of each group member can be identified whenever a group ticket is used, it may be possible to establish and execute various targeted advertising strategies based on this information.

[0222] According to one embodiment, an electronic device comprises: a display; a transceiver; a memory including at least one instruction; and at least one processor including a processing circuit, wherein the at least one instruction, when executed individually or collectively by the at least one processor, causes the electronic device to: receive ticket information from a first server or an external electronic device through the transceiver; determine whether user information included in the ticket information corresponds to authentication information of the electronic device; and, based on whether the user information corresponds to authentication information, cause a first ticket corresponding to the ticket information to be registered as a ticket of the electronic device to the first server; and wherein the first ticket is one of a plurality of tickets purchased by the external electronic device, and the plurality of tickets may be grouped and managed by the first server.

[0223] According to one embodiment, a method of operating an electronic device may include receiving ticket information from a first server or an external electronic device, determining whether user information included in the ticket information corresponds to authentication information of the electronic device, and registering a first ticket corresponding to the ticket information as a ticket of the electronic device to the first server based on whether the user information corresponds to the authentication information. The first ticket is any one of a plurality of tickets purchased by the external electronic device, and the plurality of tickets may be grouped and managed on the first server.

[0224] According to one embodiment, the operation method may further include the operation of identifying the authentication information from the memory or obtaining the authentication information from a second server based on the receipt of the ticket information.

[0225] According to one embodiment, the operation of obtaining the authentication information may include requesting the authentication information from the second server based on information used to unlock the electronic device, and receiving the authentication information from the second server in response to the request.

[0226] According to one embodiment, the operation method may further include the operation of transmitting a message to the first server indicating that the first ticket cannot be registered as a ticket of the electronic device based on the fact that the user information does not correspond to the authentication information.

[0227] According to one embodiment, the user information includes information input by the external electronic device, or authentication information obtained by the first server from the second server based on information input by the external electronic device, and the information input by the external electronic device may include phone number information or account information.

[0228] According to one embodiment, the operation method may further include the operation of receiving updated ticket information from the first server, the operation of transmitting a reception completion message to the first server indicating that the updated ticket information has been received, wherein the updated ticket information represents information generated by updating at least a part of the ticket information.

[0229] According to one embodiment, the operation method may further include the operation of transmitting the updated ticket information to at least one other electronic device.

[0230] According to one embodiment, the operation method is such that the updated ticket information is received from the first server based on a first communication method, and the updated ticket information is transmitted to at least one other electronic device based on a second communication method, wherein the second communication method is different from the first communication method and may include a short-range communication method.

[0231] According to one embodiment, the method may further include receiving advertising information associated with the location where the second ticket was used from the first server based on the fact that the external electronic device used the second ticket among the plurality of tickets, and outputting an advertisement corresponding to the advertising information to the display of the electronic device based on whether the location of the electronic device corresponds to the location.

[0232] According to one embodiment, the operation method further includes receiving a message from the first server instructing to adjust the priority of the first ticket based on the fact that the external electronic device has used the second ticket among the plurality of tickets, and adjusting the priority of the first ticket based on the received message, wherein the priority of the first ticket may be adjusted to place the first ticket in a position where it can be used most preferentially in an application for ticket usage.

[0233] The electronic device according to the various embodiments disclosed in this document may be of various forms. The electronic device may include, for example, a portable communication device (e.g., a smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a consumer electronics device. The electronic device according to the embodiments of this document is not limited to the devices described above.

[0234] The various embodiments of this document and the terms used therein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various modifications, equivalents, or substitutions of said embodiments. In connection with the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of said items unless the relevant context clearly indicates otherwise. In this document, phrases such as "A or B," "at least one of A and B," "at least one of A or B," "A, B or C," "at least one of A, B and C," and "at least one of A, B, or C" may each include any one of the items listed together in the corresponding phrase, or all possible combinations thereof. Terms such as "first," "second," or "first" or "second" may be used simply to distinguish said components from other said components and do not limit said components in any other aspect (e.g., importance or order). Where any (e.g., 1st) component is referred to as “coupled” or “connected” to another (e.g., 2nd) component, with or without the terms “functionally” or “communicationly,” it means that said any component may be connected to said other component directly (e.g., via a wire), wirelessly, or through a third component.

[0235] The term “module” as used in the various embodiments of this document may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit, for example. A module may be a component formed integrally, or a minimum unit of said component or a part thereof that performs one or more functions. For example, according to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).

[0236] Various embodiments of the present document may be implemented as software (e.g., program (140)) comprising one or more instructions stored in a storage medium (e.g., internal memory (136) or external memory (138)) readable by a machine (e.g., electronic device (101)). For example, a processor (e.g., processor (120)) of the machine (e.g., electronic device (101)) may call at least one of the one or more instructions stored in the storage medium and execute it. This enables the machine to be operated to perform at least one function according to the at least one called instruction. The one or more instructions may include code generated by a compiler or code that can be executed by an interpreter. The storage medium readable by the machine may be provided in the form of a non-transitory storage medium. Here, 'non-temporary' simply means that the storage medium is a tangible device and does not contain a signal (e.g., electromagnetic waves), and the term does not distinguish between cases where data is stored semi-permanently and cases where it is stored temporarily.

[0237] According to one embodiment, the method according to the various embodiments disclosed herein may be provided as included in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read-only memory (CD-ROM)), or distributed online (e.g., download or upload) through an application store (e.g., Play Store™) or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily created on a device-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

[0238] According to various embodiments, each component (e.g., module or program) of the components described above may include a singular or multiple entities, and some of the multiple entities may be separated and placed in other components. According to various embodiments, one or more of the components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Generally or additionally, multiple components (e.g., module or program) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each of the multiple components in the same or similar manner as those performed by the corresponding component among the multiple components prior to integration. According to various embodiments, operations performed by the module, program, or other components may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

Claims

1. In an electronic device, display; Transceiver; Memory containing at least one instruction; and It includes at least one processor including a processing circuit, and When the above at least one instruction is executed individually or collectively by the above at least one processor, the electronic device: Through the above communication unit, ticket information is received from a first server or an external electronic device; Determining whether user information included in the above ticket information corresponds to the authentication information of the above electronic device; Based on the fact that the above user information corresponds to the above authentication information, it causes the first ticket corresponding to the above ticket information to be registered as a ticket of the electronic device on the first server; and The first ticket is one of a plurality of tickets purchased by the external electronic device, and the plurality of tickets are grouped and managed on the first server, an electronic device.

2. In Paragraph 1, When the above at least one instruction is executed individually or collectively by the above at least one processor, the electronic device: An electronic device that causes the authentication information to be identified from the memory or obtained from a second server based on the receipt of the above ticket information.

3. In Paragraph 2, When the above at least one instruction is executed individually or collectively by the above at least one processor, the electronic device: Based on the information used to unlock the electronic device, the authentication information is requested to the second server through the communication unit; and An electronic device that causes the authentication information to be received from the second server through the communication unit in response to the above request.

4. In Paragraph 1, When the above at least one instruction is executed individually or collectively by the above at least one processor, the electronic device: An electronic device that causes a message to be transmitted to the first server through the communication unit, indicating that the first ticket cannot be registered as a ticket of the electronic device, based on the fact that the above user information does not correspond to the above authentication information.

5. In Paragraph 1, The above user information includes information input by the external electronic device, or authentication information obtained by the first server from the second server based on information input by the external electronic device, and The electronic device, wherein the information input by the above external electronic device includes phone number information or account information.

6. In Paragraph 1, When the above at least one instruction is executed individually or collectively by the above at least one processor, the electronic device: Through the communication unit above, updated ticket information is received from the first server, and the updated ticket information represents information generated by updating at least a part of the ticket information; and An electronic device that causes a reception completion message indicating that the updated ticket information has been received to be transmitted to the first server through the communication unit.

7. In Paragraph 6, When the above at least one instruction is executed individually or collectively by the above at least one processor, the electronic device: An electronic device that causes the updated ticket information to be transmitted to at least one other electronic device through the communication unit.

8. In Paragraph 7, When the above at least one instruction is executed individually or collectively by the above at least one processor, the electronic device: Through the communication unit above, the updated ticket information is received from the first server based on the first communication method, and The above-mentioned updated ticket information stores commands that cause it to be transmitted to at least one other electronic device based on a second communication method, and An electronic device that is different from the first communication method and includes a short-range communication method.

9. In Paragraph 1, When the above at least one instruction is executed individually or collectively by the above at least one processor, the electronic device: Based on the fact that the above external electronic device has used the second ticket among the plurality of tickets, it receives advertising information associated with the location where the second ticket was used from the first server through the communication unit; and An electronic device that stores commands causing an advertisement corresponding to the advertisement information to be output to the display based on whether the location of the electronic device corresponds to the location.

10. In Paragraph 1, When the above at least one instruction is executed individually or collectively by the above at least one processor, the electronic device: Based on the fact that the above external electronic device has used the second ticket among the plurality of tickets, it receives a message from the first server through the communication unit instructing to adjust the priority of the first ticket; Causing to adjust the priority of the first ticket based on the received message, An electronic device in which the priority of the first ticket is adjusted to place the first ticket in the position where it can be used most preferentially in an application for ticket usage.

11. In a method of operating an electronic device, The operation of receiving ticket information from a first server or an external electronic device; An operation to determine whether user information included in the above ticket information corresponds to authentication information of the electronic device; and Based on the fact that the above user information corresponds to the above authentication information, the method includes the operation of registering a first ticket corresponding to the above ticket information as a ticket of the electronic device on the first server. A method of operation of an electronic device, wherein the first ticket is one of a plurality of tickets purchased by the external electronic device, and the plurality of tickets are grouped and managed on the first server.

12. In Paragraph 11, A method of operation of an electronic device, further comprising the operation of identifying the authentication information from the memory or obtaining the authentication information from a second server based on the receipt of the above ticket information.

13. In Paragraph 12, The operation of obtaining the above authentication information is, An operation of requesting the authentication information from the second server based on the information used to unlock the electronic device; and A method of operation of an electronic device, further comprising the operation of receiving the authentication information from the second server in response to the above request.

14. In Paragraph 11, A method of operating an electronic device, further comprising the operation of transmitting a message to the first server indicating that the first ticket cannot be registered as a ticket of the electronic device based on the fact that the user information does not correspond to the authentication information.

15. In Paragraph 11, The above user information includes information input by the external electronic device, or authentication information obtained by the first server from the second server based on information input by the external electronic device, and A method of operation of an electronic device in which information input by the above external electronic device includes at least one of user name information, phone number information, address information, or account information.

Images