JP2015531106A - Digital item ingestion process - Google Patents

Abstract

Disclosed are various embodiments for an ingestion process that modifies a digital item. The computing system receives uploaded digital items that are configured to communicate with a test server application at runtime. The ingestion process reconfigures the digital item to communicate with the production server application at runtime.

Description

  The disclosed technology relates to an ingestion process.

  Many applications may have the ability to complete transactions via the network. A problem arises when a developer must test whether these applications function correctly before putting them on the market.

  The disclosed technique aims to facilitate the modification of digital items through an ingestion process.

  A system of one aspect of the disclosed technology includes at least one computing device and an ingestion process executable within the at least one computing device, the ingestion process comprising: a digital item delivery service for digital items Logic to facilitate uploading to the digital item, wherein the digital item is configured to communicate a plurality of transaction requests for execution of the digital item to a test server application, wherein the test server application includes the digital item Logic that facilitates uploading of digital items to a digital item delivery service, configured to simulate the completion of multiple transactions associated with execution, and delivery to multiple client devices Logic for modifying the digital item to communicate the transaction request to a production server application during an ingestion for the transaction request from an instance of the digital item downloaded from the digital item distribution service An injection process that includes logic for modifying the digital item, wherein the production server application is configured to complete the transaction.

  The disclosed technology allows for easy modification of digital items through an ingestion process.

FIG. 3 is a diagram of a networked environment in accordance with various embodiments of the present disclosure. 2 is a flow diagram illustrating an example of functions implemented as part of an ingestion process executed within a computing device within the distribution computing device of FIG. 1 in accordance with various embodiments of the present disclosure. FIG. 2 is an example of a user interface rendered by a developer client device in the networked environment of FIG. 1 that executes a test server application in accordance with various embodiments of the present disclosure. FIG. 2 is an example of a user interface rendered by a developer client device in the networked environment of FIG. 1 that executes a test server application in accordance with various embodiments of the present disclosure. 2 is a flow diagram illustrating an example of functionality implemented as part of a test server application executing within a computing device within the test computing device of FIG. 1 in accordance with various embodiments of the present disclosure. FIG. 2 is a schematic block diagram providing an illustrative example of the developer client device of FIG. 1 in accordance with various embodiments of the present disclosure. FIG. 2 is a schematic block diagram providing an illustrative example of the client device of FIG. 1 in accordance with various embodiments of the present disclosure. FIG. 2 is a schematic block diagram providing an illustrative example of a computing device employed within the distribution computing device of FIG. 1 in accordance with various embodiments of the present disclosure.

  Disclosed are various embodiments that facilitate the modification of digital items through an ingestion process. Many digital items include the ability to complete transactions with server applications. In many cases, this requires that the digital item communicate with one server application during testing of the item and with another server application after the digital item has been publicly distributed. As a non-limiting example, a gaming application may allow a user to purchase additional in-game content by completing a financial transaction from within the application. During testing, the game should contact a test server application that is configured to only simulate financial transactions. When the game is placed on a publicly available distribution system, the game should contact a server application that completes the financial transaction so that the user is charged for in-game content. A digital item can be created such that it initiates these transactions with either a test server application or a public server application based on predetermined conditions. A digital item can be modified to satisfy a predetermined condition through an ingestion process, thereby allowing the developer to contact the production server application without having to change the digital item.

  Many aspects of the disclosure can be better understood with reference to the drawings. The components in the figures are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Further, in the figures, like reference numerals designate corresponding parts throughout the several views.

  Referring to FIG. 1, a networked environment 100 is shown according to various embodiments. Networked environment 100 includes at least one developer client device 101, at least one client device 104, network 107, test computing device 110, production computing device 113, distribution computing device 116, and potentially others. Including devices. Network 107 may be, for example, the Internet, an intranet, an extranet, a wide area network (WAN), a local area network (LAN), a wired network, a wireless network, or other suitable network, or any of two or more such networks Including a combination of

  Developer client device 101 and client device 104 are representative of multiple devices that may be coupled to network 107. Developer client device 101 and client device 104 may include, for example, a processor-based system such as a computer system. Such a computer system may be embodied in the form of a desktop computer, laptop computer, personal digital assistant, mobile phone, set top box, music player, web pad, tablet computer system, game console, or other device with similar functionality. Can be

  Various applications and / or other functions may be executed within developer client device 101 and client device 104 in accordance with various embodiments. Various data are stored in a data store 119 accessible by the developer client device 101. Various data is stored in a data store 143 accessible by the client device 104. Data stores 119 and 143 can be representative of multiple data stores, as can be appreciated. The data stored in the data stores 119 and 143 is associated with the operation of various applications and / or functional entities, described below, for example.

  Developer client device 101 may be configured to execute various applications, such as development application 125, deployment application 134, and / or other applications. Development application 125 may be executed within a developer client device to facilitate creation of digital item 122a. Such a development application 125 may include a software development kit (SDK), integrated development environment (IDE), text editor, hexadecimal editor (hex editor), word processor, video editor, audio editor, or productivity suite. An instance of the digital item 122a may be stored in the data store 119. The deployment application 134 executes on the distribution computing device as may be executed and understood within the developer client device 101 to facilitate uploading an instance of the digital item 122 to the distribution computing device 116. It may include a browser, a terminal that executes input commands, a dedicated executable application, or another application for accessing and rendering network pages provided by the process.

  Digital item 122a may include an executable item, a media item, or another type of digital item. An executable item may refer to an application, binary, or any other file that contains executable logic, as may be understood. Media items require music files, video files, documents, e-books, or any other data that requires an execution application 137 to render audio, visual, or text content for display or playback to the user. May be included. The execution application 137, as can be understood, includes music, text, including a video player, audio player, e-book reader, or any other application that facilitates the user's interaction with the media version of the digital item 122a. Or an application that includes executable logic for decoding video data.

  Client device 104 may be configured to execute various applications, such as purchasing application 146 and / or other applications. Purchase application 146 is provided by a process executing on distribution computing device 116 so that it can be executed and understood within the client device to facilitate downloading of an instance of the digital item from distribution computing device 116. May include a browser, a dedicated executable application, or another application for accessing and rendering rendered network pages. Purchasing application 146 will also facilitate any financial transaction preconditions for downloading an ingested instance of digital item 122a (referred to herein as digital item 122b) that may then be stored in data store 143. Client device 104 may also execute an instance of execution application 137 (referred to as execution application 137a) to render a media item version of digital item 122b.

  Test computing device 110 and production computing device 113 may include, for example, a server computer or any other system that provides computing functionality. Alternatively, a plurality of computing devices 110 and 113 may be employed, for example arranged in one or more server banks or computer banks or other arrangements. For example, the plurality of computing devices 110 and 113 together may include cloud computing resources, grid computing resources, and / or any other distributed computing arrangement. Such computing devices 110 and 113 may be located in a single facility or distributed between a number of different geographic locations. For convenience, each computing device 110 or 113 is referred to herein as the singular. It will be understood that a plurality of computing devices 110 or 113 may be employed in various arrangements, as described above, even though the computing device 110 or 113 is referenced in the singular.

  Components that execute on the test computing device 110 include, for example, the test server application 155 and other applications, services, processes, systems, engines, or functions not discussed in detail herein. Test server application 155 is executed to simulate the completion of a transaction with respect to testing digital item 122a.

  Components that execute on the production computing device 149 include, for example, the production server application 158 and other applications, services, processes, systems, engines, or functions not discussed in detail herein. The production server application 158 is executed to complete the transaction with respect to execution on the client device 104 of the instance of the digital item 122b, as will be described later.

  Distribution computing device 116 may include, for example, a server computer or any other system that provides computing functionality. Alternatively, a plurality of distribution computing devices 116 may be employed, for example arranged in one or more server banks or computer banks or other arrangements. For example, a plurality of distribution computing devices 116 may together include cloud computing resources, grid computing resources, and / or any other distributed computing arrangement. Such a distribution computing device 116 may be located at a single facility or distributed between a number of different geographic locations. For convenience purposes, the delivery computing device 116 is referred to herein as the singular. It will be understood that a plurality of delivery computing devices 116 may be employed in various arrangements, as described above, even if a single computing device is referenced.

  Components executed on distribution computing device 116 include, for example, digital item distribution service 161 and other applications, services, processes, systems, engines, or functions not discussed in detail herein. The digital item delivery service 161 is implemented to facilitate uploading over the network 107 from the deployment application 134 of the digital item 122a through the use of the ingestion process 164. An ingested instance of digital item 122a (referred to herein as digital item 122b) may be stored in data store 170. The digital item distribution service 161 also uses the distribution process 167 to facilitate downloading of the ingested instance of the digital item 122b to the client device 104 executing the purchase application 146 via the network 107. For this purpose, the digital item distribution service 161 uses a hypertext transfer protocol (HTTP), a file transfer protocol (for transferring data to the developer client device 101 and the client device 104 via the network 107, for example. Various, such as FTP), HTTP Secure (HTTPS), Simple Object Access Protocol (SOAP), Representation State Transfer (REST), User Datagram Protocol (UDP), Transmission Control Protocol (TCP), and / or other protocols Can communicate via protocol. In various embodiments, the digital item delivery service 161 may support the use of anycast services and / or peer-to-peer (P2P) protocols, such as, for example, BitTorrent for data communications. Additionally, the digital item delivery service 161 may monitor the progress of scheduled uploads or downloads to ensure transfer completion.

  Data store 170 may be representative of multiple data stores, as can be appreciated. Data stored in data store 170 includes, for example, ingested instances of digital item 122b, and potentially other data.

  Next, an overview of the operation of the various components of the networked environment 100 is provided. Initially, a digital item 122 a is created on the developer client device 101 using one or more development applications 125. The digital item 122a includes logic to initiate a transaction with either the test server application 155 before the injection or the production server application 158 after the injection. For example, in some embodiments, this may include a game that includes logic for the player to unlock additional features in exchange for money. In other embodiments, this may include a video media item that includes logic to allow access to additional video content. In addition, digital item 122a may interact with test server application 155 and production server application 158 in other contexts. This logic sends a transaction request 152 to either the test server application 155 or the production server application 158. Transaction request 152 may include data indicating which features are unlocked and other data sufficient for the test server application to simulate the completion of the transaction. Such transaction request 152 may include credit card information or other user identification information.

  In response to the transaction request 152, the test server application simulates the completion or failure of the transaction and sends a plurality of transaction responses 149 indicating the simulated results to the digital item 122a. In some embodiments, the test computing device 110 includes one or more computing devices with which the developer client device 101 communicates via the network 107. In other embodiments, the test computing device 110 may be the same system as the developer client device 101 and the test server application 155 is one of a number of applications that run on the developer client device 101. .

  In embodiments where the test server application 155 is executed on the developer client device 101, whether the test server application 155 simulates a successful transaction or an unsuccessful transaction may depend on input to the user interface. For example, in one embodiment, the digital item 122a may require that the transaction be completed by communicating the transaction request 152 to the test server application 155. The test server application 155 displays a user interface and prompts for input regarding whether to simulate a successful or unsuccessful transaction. Such input may also indicate the type of transaction being performed. Based on the input to the user interface, the test server application 155 generates a transaction response 149 that is then communicated to the digital item 122a.

  Production server application 158 responds to transaction request 152 and attempts to complete the requested transaction. Based on the successful attempt to complete the transaction, the production server application communicates the transaction response 149 to the ingested instance of the digital item 122b that sent the original transaction request 152. Transaction response 149 indicates whether the transaction was successful, such as when a credit card transaction is accepted, or unsuccessful, such as when the credit card is rejected. In another example, transaction request 152 may initiate a transaction where funds are withdrawn from a prepaid account. For a successful transaction, transaction response 149 indicates that the account has sufficient funds and the required amount has been withdrawn from the account. Unsuccessful transaction response 149 indicates that there was not enough funds in the account. In some embodiments, the production server application runs on the production computing device 113. In other embodiments, it runs as one of several applications running on the distribution computing device 116.

  The digital item 122a includes logic to ensure that the transaction request 152 is communicated to the test server application 155 before the injection and to the production server application 158 after the injection. Such logic may be stored in an application program interface, library, or another component. In some embodiments, the decision to send the transaction request 152 to the test server application 155 or production server application 158 is performed by logic that checks for the existence of digital rights management. In other embodiments, the digital item 122a includes logic that performs the methods defined in the library of digital items 122a. In this case, the library of digital items 122a defines a method that communicates the transaction request 152 to the test server application 155. In another embodiment, the digital item 122a sends a transaction request 152 to a network address defined in the digital item's file component. Prior to the injection, this network address points to the test server application 155.

  A deployment application 134 running on the developer client device 101 facilitates uploading the digital item 122a to the delivery computing device 116 via the network 107. The distribution computing device 116 performs a digital item distribution service 161 that includes an ingestion process 164 that facilitates uploading of the digital item 122a. The ingestion process 164 also modifies the uploaded instance of the digital item 122a to an ingested version of the digital item 122b. The ingested digital item 122b has been modified so that the transaction request 152 is communicated to the production server application 158.

  In the case where the digital item 122a sends a transaction request 152 to the test server application 155 in the absence of digital rights management, the ingestion process 164 applies the digital rights management to the digital item 122a. This ingested instance of the digital item 122b sends a transaction request 152 to the production server application 158 based on logic that detects the presence of digital rights management. In another embodiment, where the transaction request for the digital item 122a is sent using logic defined within the library component, the ingestion process 164 replaces the library component of the digital item 122a. In this ingested instance of digital item 122b, the library component defines the logic by which transaction request 152 is sent to production server application 158.

  In another embodiment, the digital item 122a sends the transaction request 152a to the test server application 155 pointed to by the network address stored in the file component. The ingestion process 164 automatically modifies the file component such that the file component's network address currently points to the production server application 158. Other modifications to the instance of the digital item 122a may be used by the ingestion process 164 so that the ingested instance 122b communicates its transaction request 152 to the production server application 158, as will be appreciated. The ingested instance of the digital item 122b is stored in the data store 170.

  Client device 104 may access digital item delivery service 161 through purchase application 146. In one embodiment, purchase application 146 is a browser that renders a network page generated by digital item delivery service 161. In another embodiment, purchase application 146 is a dedicated executable application, such as, for example, an app store or other executable application. The digital item distribution service 161 generates a list of ingested digital items 122b that can be purchased by the purchase application 146. The list of digital items 122b may be based on various criteria including search terms, popularity of digital items 122b, user preferences, and previous purchase history. The purchase application 146 renders a user interface showing a list of digital items 122b that can be purchased from the digital item distribution service 161. Based on input from the user interface indicating the digital item 122b to purchase, the distribution process 167 facilitates downloading the purchased instance of the digital item 122b to the client device 104 via the network 107.

  According to one embodiment, the ingested instance of the digital item 122b purchased from the digital item distribution service 161 would have been modified by the ingestion process 164. When executed on the client device 104, the digital item 122b will communicate the transaction request 152 to the production server application 158 as described above.

  Referring now to FIG. 2, a flow diagram is provided that provides an example of the operation of a portion of the injection process 164 (FIG. 1) in accordance with various embodiments. The flow diagram of FIG. 2 merely provides an example of many different types of functional arrangements that can be employed to implement the operation of that portion of the ingestion process 164, as described herein. It is understood. Alternatively, the flow diagram of FIG. 2 may be viewed as illustrating an example of method steps implemented within distribution computing device 116 (FIG. 1) in accordance with one or more embodiments.

  The operations performed in FIG. 2 are triggered by the upload of the digital item 122a (FIG. 1) to the digital item delivery service 161 (FIG. 1) by the developer client device 101 (FIG. 1). As mentioned above, this version of digital item 122a is configured such that it sends transaction request 152 (FIG. 1) to test server application 155 (FIG. 1). The ingestion process 164 modifies the digital item 122a. This ingested instance of digital item 122b (FIG. 1) will communicate its transaction request to production server application 158. The ingested instance of the digital item 122b is then stored in the data store 170 (FIG. 1). The client device 104 (FIG. 1) connecting to the digital item distribution service 161 can then download the ingested instance of the digital item 122b stored in the data store 170.

  Starting from box 201, digital item 122a is uploaded to digital item distribution service 161 over network 107 (FIG. 1). In some embodiments, this is accomplished through a deployment application 125 (FIG. 1) running on the developer client device 101 that facilitates uploading the digital item 122. At box 204, the ingestion process 164 determines whether the uploaded digital item 122a embodies a first predefined condition. The digital item 122a embodies the first predefined condition when configured in such a way that the transaction request 152 sent by the digital item 122a is sent to the test server application 155. In one embodiment, the first predefined condition is satisfied when there is no digital rights management present on the digital item 122a.

  In another embodiment, determining whether the digital item 122a implements the first predefined condition includes examining a library of digital items 122a. For example, this determination can be made to determine whether a method or logic defined in the library of digital items 122a sends a transaction request 152 to the test server application 155 at runtime. Can be directly inspected. This determination may also include examining a unique identifier associated with the library component, such as a checksum, another hash sum, or some other unique identifier. The unique identifier is then compared to a known value that indicates whether the digital item 122a embodies the first predefined condition.

  In another embodiment, determining whether the digital item 122a is configured to communicate with the test server application 155 includes examining a network address stored in a file that the digital item 122a can access. obtain. In one embodiment, this may include comparing the network address stored in the file with a list of addresses known to point to the test server application. In other embodiments, this may include looking for a subsequence or keyword in the network address.

  At box 207, the ingestion process 164 continues based on whether the digital item 122a implements the first predefined condition, as determined at box 204. If the digital item 122a implements the first predefined condition in box 211, then the ingestion process 164 then causes the ingested instance of the digital item 122b to implement the second predefined condition. The digital item 122a is modified so that Digital item 122b embodies a second predefined condition when configured in such a way that transaction request 152 sent by digital item 122b is sent to production server application 158.

  In some embodiments, an ingested instance of digital item 122b will send its transaction request 152 to a destination determined by the presence of digital rights management. In these instances, the ingestion process 164 applies digital rights management to the uploaded digital item 122a to generate an ingested instance of the digital item 122b.

  In another embodiment, the ingested instance of digital item 122b will send its transaction request 152 by executing the logic or method defined in the library. In this embodiment, the ingestion process 164 is configured to replace an existing library of uploaded digital items 122a with a different library. The library of ingested instances of the digital item 122b defines logic or methods that perform the function of sending the transaction request 152 to the production server application 158.

  In another embodiment, the ingested instance of digital item 122b will send its transaction request 152 to the destination pointed to by the network address stored in the file. In this embodiment, the ingestion process 164 is configured to modify the network address stored in the file to point to the production server application 158.

  If the uploaded instance of the digital item 122a does not embody the first predefined condition (see box 207), the injection is completed without modification and the operation proceeds to box 213. Finally, in box 213, the ingested instance of the digital item 122b is stored in the data store 170, which is accessible to the digital item distribution service 161.

  Proceeding to FIGS. 3A and 3B, an example user interface for interacting with the test server application 155 (FIG. 1) is shown in accordance with various embodiments. In this embodiment, the test server application 155 is executed on the developer client device 101 (FIG. 1). Item 301 shows the user interface generated by digital item 122a (FIG. 1) executed on developer client device 101. In this example, the digital item 122a includes a game in which various enhancements can be purchased from within the game. Enhancement list 304 lists the enhancements available for purchase and their corresponding prices. Button 307 accompanies each entry to enhancement list 304 that initiates a financial transaction to purchase the corresponding enhancement.

  When the button 307 is clicked by the user, the digital item 122a sends a transaction request 152 (FIG. 1) to the test server application 155. Proceeding to FIG. 3B, the test server application 155 then encodes to render a user interface 311 that requests input from the user. The user interface 311 is then sent to the client device 104 for display. User interface 311 includes response options 314. When the user selects response option 314, test server application 155 simulates the completion of the transaction based on input to user interface 311. The test server application 155 then sends a corresponding transaction response 149 to the digital item 122a.

  Referring now to FIG. 4, a flowchart is provided that provides an example of the operation of a portion of the test server application 155 (FIG. 1) in accordance with various embodiments. The flow diagram of FIG. 4 merely provides an example of many different types of functional arrangements that can be employed to implement the operation of that portion of the test server application 155, as described herein. It is understood. Alternatively, the flow diagram of FIG. 4 may be considered to illustrate an example of method steps implemented within the test computing device 110 (FIG. 1) in accordance with one or more embodiments.

  The operation of FIG. 4 is triggered in some embodiments where the test server application 155 is executed on the developer client device 101 (FIG. 1). A digital item 122 a (FIG. 1) is executed on the developer client device 101. In the case of media items, this execution is facilitated by the execution application 137 (FIG. 1). In the case of an executable item, the necessary executable logic is included in the item and the execution application 137 is not required. When the digital item 122a initiates a transaction, it sends a transaction request 152 (FIG. 1) to the test server application 155. The test server application 155 then generates a user interface that allows the user to control the transaction response 149 (FIG. 1) sent to the digital item 122a.

  Beginning with box 401, a transaction request 152 is communicated from the digital item 122a to the test server application 155. This transaction request 152 is used to initiate a transaction with the test server application 155. As described above, the transaction may include a financial transaction, a download of media content, or some other transaction. In box 404, upon receiving a transaction request 152, the test server application 155 renders a user interface that shows a list of possible responses to the request.

  The list of possible choices varies based on the transaction that the digital item 122a attempts to initiate. For example, in response to a transaction request 152 that initiates a financial transaction to pay using a credit card, the test server application 155 indicates an authorized credit card, a rejected credit card, a network timeout, or other options. A user interface having a list of options may be rendered. In another example, in response to a transaction request 152 that initiates a financial transaction to pay using a prepaid account, the test server application 155 may provide a list of options indicating successful use of funds, lack of funds, or other options. The user interface can be rendered. In a transaction to download media content, the user interface may list options that indicate allowed downloads, downloads that are denied based on user restrictions, temporary unavailable, or other options.

  The test server application 155 does not send a transaction response 149 to the digital item 122a until the user interface receives input. As a result, in boxes 407 and 411, the test server application 155 waits until a response is selected in the user interface. After the input is selected at box 413, the test server application 155 simulates the completion of the transaction based on the input to the user interface. For example, in a financial transaction that is paid using a simulated account, the account is debited with the appropriate amount. In other embodiments, the test server application 155 may communicate the confirmation message to the user via email, text message, or other communication medium. Finally, box 416 shows the test server application sending a transaction response 149 based on the input to the user interface.

  Referring to FIG. 5, a schematic block diagram of a developer client device 101 (FIG. 1) according to one embodiment of the present disclosure is shown. Developer client device 101 includes, for example, at least one processor circuit having processor 601 and memory 604, both of which are coupled to local interface 607. For this purpose, the developer client device 101 may include, for example, at least one server computer or similar device. Local interface 507 may include, for example, a data bus with an associated address / control bus or other bus structure, as can be appreciated.

  Stored in memory 504 are both the data and some components executable by processor 501. Specifically, those stored in memory 504 and executable by processor 501 include development application 125 (FIG. 1), deployment application 134 (FIG. 1), test server application 155 (FIG. 1), and potential To other applications. Also stored in memory 504 may be a data store 119 (FIG. 1) that stores instances of digital items 122a (FIG. 1), and other data. In addition, an operating system may be stored in the memory 504 and executable by the processor 501.

  Referring to FIG. 6, a schematic block diagram of a client device 104 (FIG. 1) according to one embodiment of the present disclosure is shown. Client device 104 includes, for example, at least one processor circuit having processor 601 and memory 604, both of which are coupled to local interface 607. For this purpose, client device 104 may include, for example, at least one server computer or similar device. The local interface 607 may include, for example, a data bus with an associated address / control bus or other bus structure, as can be appreciated.

  Stored in memory 604 are both the data and some components executable by processor 601. Specifically, what is stored in the memory 604 and can be executed by the processor 601 is a purchase application 146 (FIG. 1), an instance of the execution application 137 (FIG. 1), and potentially other applications. Also stored in memory 604 may be a data store 143 (FIG. 1) that stores an instance of digital item 122b (FIG. 1), and other data. In addition, an operating system may be stored in the memory 504 and executable by the processor 501.

  Referring to FIG. 7, a schematic block diagram of a distribution computing device 116 (FIG. 1) according to one embodiment of the present disclosure is shown. Distribution computing device 116 includes, for example, at least one processor circuit having processor 701 and memory 704, both of which are coupled to local interface 707. For this purpose, the distribution computing device 116 may include, for example, at least one server computer or similar device. The local interface 707 may include, for example, a data bus with an associated address / control bus or other bus structure, as can be appreciated.

  Stored in memory 704 are both the data and some components executable by processor 701. Specifically, what is stored in the memory 704 and can be executed by the processor 701 is a digital item distribution service 161 (FIG. 1) including an ingestion process 164 (FIG. 1) and a distribution process 167 (FIG. 1), As well as potentially other applications. Also stored in memory 704 may be a data store 170 that stores an ingested instance of digital item 122b (FIG. 1), and other data. In addition, an operating system may be stored in memory 704 and executable by processor 701.

  As can be seen, it is understood that there may be other applications stored in the memories 504, 604, and 704 and executable by the processors 501, 601 and 701. If any of the components described herein are implemented in software, for example, C, C ++, C #, Objective C, Java, JavaScript, Perl, PHP, Visual Basic, Python, Ruby, Delphi, Flash Or any one of several programming languages, such as other programming languages, may be employed.

  Several software components are stored in the memories 504, 604, and 704 and are executable by the processors 501, 601 and 701. In this regard, the term “executable” refers to a program file that is in a format that can ultimately be executed by the processors 501, 601 and 701. Examples of executable programs are, for example, compiled programs that can be loaded into the random access portions of memories 504, 604, and 704 and that can be converted to machine code in a format that can be executed by processors 501, 601, and 701, memories 504, 604. , And 704 can be loaded into the random access portion and can be expressed in an appropriate format such as object code that can be executed by the processors 501, 601 and 701, or by the processors 501, 601, and 701 Such as source code that may be interpreted by another executable program to generate instructions within the random access portions of memories 504, 604, and 704 to be executed. Executable programs include, for example, random access memory (RAM), read only memory (ROM), hard drive, solid state drive, USB flash drive, memory card, compact disc (CD) or digital versatile disc (DVD) It can be stored in any portion or component of memory 504, 604, and 704, including an optical disk, floppy disk, magnetic tape, or other memory component.

  Memories 504, 604, and 704 are defined herein as including both volatile and non-volatile memory and data storage components. Volatile components are those that do not retain data values when power is lost. Non-volatile components are those that retain data values when power is lost. Thus, the memories 504, 604, and 704 include, for example, random access memory (RAM), read only memory (ROM), hard disk drive, solid state drive, USB flash drive, memory card accessed via a memory card reader, Floppy disks accessed via associated floppy disk drives, optical disks accessed via optical disk drives, magnetic tapes accessed via suitable tape drives, and / or other memory components, or Any two or more combinations of memory components may be included. In addition, the RAM may include, for example, static random access memory (SRAM), dynamic random access memory (DRAM), or magnetic random access memory (MRAM) and other such devices. The ROM may include, for example, a programmable read only memory (PROM), an erasable programmable read only memory (EPROM), an electrically erasable programmable read only memory (EEPROM), or other similar memory device.

  In addition, each of the processors 501, 601, and 701 may represent a plurality of processors 501, 601, and 701, and the memories 504, 604, and 704 may each include a plurality of memories 504, 604, And 704 may be representative. In such a case, the local interfaces 507, 607, and 707 are connected between any two of the plurality of processors 501, 601, and 701, any processor 501, 601, and 701 and any of the memories 504, 604, and 704. Or any suitable two of the memories 504, 604, and 704, etc. may be a suitable network 107 (FIG. 1) that facilitates communication. Local interfaces 507, 607, and 707 may include additional systems designed to coordinate this communication, including, for example, performing load balancing. Processors 501, 601 and 701 may be electrical or some other available structure.

  Ingestion process 164 (FIG. 1), test server application 155 (FIG. 1), and various other systems described herein are implemented in software or code that runs on general purpose hardware, as described above. Alternatively, the same could be implemented with dedicated hardware or a combination of software / general purpose hardware and dedicated hardware. When implemented on dedicated hardware, each can be implemented as a circuit or state machine that employs any one or combination of techniques. These techniques include discrete logic circuits with logic gates to implement various logic functions when applying one or more data signals, application specific integrated circuits with appropriate logic gates, or other components, etc. Including, but not limited to. Such techniques are generally well known by those skilled in the art and are therefore not described in detail herein.

  The flowcharts of FIGS. 2, 3A and 3B illustrate the functionality and operation of an embodiment of the app store test client portion. When implemented in software, each block may represent a module, segment, or portion of code that includes program instructions for implementing the specified logical function (s). The program instructions include source code or human-readable instructions written in a programming language, including numerical instructions recognizable by a suitable execution system such as processors 501, 601 and 701 in a computer system or other system It can be implemented in the form of a machine code. The machine code can be converted from source code or the like. When implemented in hardware, each block may represent a circuit or a number of interconnect circuits for implementing the specified logical function (s).

  Although the flowcharts of FIGS. 2, 3A and 3B show a particular order of execution, it will be understood that the order of execution may be different than that shown. For example, the execution order of two or more blocks can be mixed with the order shown. Also, two or more blocks shown in succession in FIGS. 2, 3A and 3B may be executed simultaneously or partially simultaneously. Further, in some embodiments, one or more of the blocks shown in FIGS. 2, 3A and 3B may be skipped or omitted. In addition, any number of counters, state variables, warning semaphores, or messages can be used to provide enhanced usability, billing, performance measurement, or troubleshooting assistance, etc. Can be added to. All such variations are understood to be within the scope of this disclosure.

  Any logic or application described herein, including test server application 155 (FIG. 1), digital item delivery service 161 (FIG. 1), and ingestion process 164 (FIG. 1), including software or code. Is implemented on any persistent computer-readable medium for use by or in connection with an instruction execution system, such as, for example, processors 501, 601, and 701, within a computer system or other system. it can. In this sense, logic can include statements, including instructions and declarations, that can be fetched from a computer-readable medium and executed by an instruction execution system, for example. In the context of this disclosure, a “computer-readable medium” encompasses or stores logic or applications described herein for use by or in connection with an instruction execution system, or It can be any medium that holds. Computer-readable media can include any one of a number of physical media, such as, for example, magnetic media, optical media, or semiconductor media. More specific examples of suitable computer readable media may include, but are not limited to, magnetic tape, magnetic floppy diskette, magnetic hard drive, memory card, solid state drive, USB flash drive, or optical disk. The computer readable medium may also be random access memory (RAM), including, for example, static random access memory (SRAM) and dynamic random access memory (DRAM), or magnetic random access memory (MRAM). In addition, the computer readable medium may be read only memory (ROM), programmable read only memory (PROM), erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), or other similar It can be a memory device.

  Various embodiments of the present disclosure can be described in view of the following non-limiting supplementary notes.

Additional Notes 1. A persistent computer readable medium embodying a program executable in a computing device, the program comprising:
A code that facilitates the uploading of digital items to a digital item distribution service,
Configured to communicate a plurality of transaction requests to a test server application based on a first predefined condition and to communicate the transaction requests to a production server application based on a second predefined condition At least an application program interface, wherein the first and second predefined conditions are mutually exclusive;
A test server application is configured to simulate the completion of multiple financial transactions associated with the use of digital items,
The production server application is configured to complete multiple financial transactions associated with execution on the client device of the instance of the digital item downloaded from the digital item delivery service;
Before the digital item is uploaded, it is configured to embody the first predetermined condition,
Code that facilitates uploading of digital items to a digital item delivery service;
Coat that modifies the digital item from the realization of the first predetermined condition to the realization of the second predetermined condition upon uploading; and stores the digital item in a data store accessible by the digital item distribution service Persistence, including code for storing a digital item in a data store accessible to the digital item distribution service, wherein the digital item distribution service facilitates downloading an instance of the digital item on the client device Computer readable medium.

  Additional Item 2. The computer readable medium of clause 1, wherein the code for modifying the digital item further comprises code for adding digital rights management to the digital item.

  Additional Item 3. The computer-readable medium of clause 1, wherein the digital item includes a first library and the code that modifies the digital item replaces the first library with the second library.

  Additional Item 4. Additional clause 1 wherein the digital item includes a network address associated with the test server application prior to upload, and the code for modifying the digital item further includes code for modifying the network address to be associated with the production server application. The computer-readable medium described.

Additional Item 5. A system comprising at least one computing device; and an ingestion process executable in the at least one computing device, the ingestion process:
Logic that facilitates uploading of digital items to a digital item delivery service, wherein the digital item is configured to communicate multiple transaction requests related to the execution of the digital item to the test server application, the test server application Logic for facilitating uploading of digital items to a digital item distribution service, configured to simulate the completion of multiple transactions associated with the execution of the digital items; and for distribution to multiple client devices Logic for modifying the digital item to communicate the transaction request to the production server application during the ingestion for the transaction, wherein the transaction request is installed in the digital item downloaded from the digital item distribution service. When sent from Nsu production server application is configured to complete the transaction, to correct the digital item logic;
Including the system.

  Additional Item 6. The system of clause 5, wherein one of the transactions includes a financial transaction.

  Additional Item 7. The system of clause 5, wherein one of the transactions includes downloading of media content.

  Additional Item 8. The system of clause 5, wherein the digital item includes an application.

  Additional Item 9. The system of clause 5, wherein the digital item comprises a media item.

  Additional Item 10. The system of clause 5, wherein the logic for modifying the digital item further comprises logic for applying digital rights management to the digital item.

  Additional Item 11. The digital item sends a transaction request to the test server application if digital rights management is not applied to the digital item, and the production server application if digital rights management is applied to the digital item. 11. The system of clause 10, further comprising an application program interface configured to transmit to.

  Additional Item 12. The system of clause 5, wherein the digital item further comprises a first library and the logic for modifying the digital item replaces the first library with the second library.

  Additional Item 13. The digital item further comprises a network address and an application program interface;

The application program interface is configured to send a transaction request to the test server application if the network address points to the test server application, and points to the production server if the network address is associated with the production server application And
The logic to modify the digital item further includes logic to modify the network address to point to the production server application;
The system according to appendix 5.

Additional Item 14. The digital item is one of a plurality of digital items and the system
A distribution process executable in the at least one computing device, the distribution process comprising:
The system of clause 5, comprising logic to generate a list of digital items; and logic to facilitate downloading an instance of one of the digital items listed in the list of items.

Additional Item 15. A system comprising at least one computing device; and a test server application executable in the at least one computing device, the test server application:
Logic that facilitates receipt of a transaction request transmitted by a digital item, wherein the transaction request is associated with testing of the digital item and that facilitates reception of a transaction request transmitted by the digital item;
Logic to initiate a transaction based on a transaction request;
Logic coding to render a user interface requesting input to select a desired response to a transaction request;
A system that includes logic to simulate the performance of a transaction based on a desired response; and logic to send a transaction response based on a desired response to a digital item.

  Additional Item 16. The system of clause 15 wherein the transaction comprises a financial transaction.

  Additional Item 17. The system of clause 15, wherein the transaction includes downloading of media content.

  Additional Item 18. The system of clause 15, wherein the logic for simulating the fulfillment of a transaction further comprises logic for simulating the expiration of a network timeout interval.

  Additional Item 19. The system of clause 15, wherein the desired response is selected from a plurality of possible responses.

  Additional Item 20. 20. The system of clause 19, further comprising logic for the test server application to determine possible responses in response to the transaction.

  It should be emphasized that the above-described embodiments of the present disclosure are merely possible examples of implementations described for a clear understanding of the principles of the present disclosure. Numerous variations and modifications can be made to the foregoing embodiment (s) without substantially departing from the spirit and principles of the present disclosure. All such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the following claims.

CROSS REFERENCE TO RELATED APPLICATIONS The following application is a priority to and benefit of a US patent application entitled “DIGITAL ITEM INGESTION PROCESS” filed July 6, 2012, having application number 13 / 542,956. Which is incorporated herein by reference in its entirety.

Claims (15)

At least one computing device;
An ingestion process executable in the at least one computing device, wherein the ingestion process:
Logic that facilitates uploading of digital items to a digital item delivery service, wherein the digital items are configured to communicate a plurality of transaction requests for execution of the digital items to a test server application, the test server application Logic that facilitates uploading a digital item to a digital item delivery service configured to simulate the completion of multiple transactions associated with the execution of the digital item;
Logic for modifying the digital item to communicate the transaction request to a production server application during an ingestion for distribution to a plurality of client devices, wherein the transaction request is downloaded from the digital item distribution service An ingestion process including logic to modify the digital item, wherein the production server application is configured to complete the transaction when sent from the instance of the digital item system.   The system of claim 1, wherein one of the transactions comprises a financial transaction.   The system of claim 1, wherein one of the transactions includes a download of media content.   The system of claim 1, wherein the digital item includes an application.   The system of claim 1, wherein the digital item comprises a media item.   The system of claim 1, wherein the logic to modify the digital item further comprises logic to apply digital rights management to the digital item.   The digital item sends the transaction request to the test server application if the digital rights management is not applied to the digital item, and the digital rights management is applied to the digital item; The system of claim 6, further comprising an application program interface configured to transmit to the production server.   The system of claim 1, wherein the digital item further comprises a first library, and the logic that modifies the digital item replaces the first library with a second library. The digital item further comprises a network address and an application program interface;
The application program interface is configured to send the transaction request to the test server application if the network address points to the test server application, and the network address is associated with the production server application; Point to the production server,
The logic for modifying the digital item further comprises logic for modifying the network address to point to the production server application;
The system of claim 1. The digital item is one of a plurality of digital items, and the system includes:
A delivery process executable in the at least one computing device, the delivery process comprising:
Logic to generate a list of the digital items and logic to facilitate downloading an instance of one of the digital items listed in the list of items.
The system of claim 1. Facilitating receipt of a transaction request transmitted by a digital item by one or more computing devices, wherein the transaction request is associated with a test of the digital item. Making it easier to receive transaction requests;
Initiating a transaction based on the transaction request by the one or more computing devices;
Encoding a user interface requesting input by the one or more computing devices to select a desired response to the transaction request;
Simulating the performance of the transaction based on the desired response by the one or more computing devices;
Sending a transaction response based on the desired response to the digital item by the one or more computing devices.   The computer-implemented method of claim 11, wherein the transaction comprises a financial transaction or a download of media content.   The computer-implemented method of claim 11, wherein the simulating the fulfillment of the transaction further comprises simulating the expiration of a network timeout interval.   The computer-implemented method of claim 11, further comprising selecting the desired response from a plurality of possible responses.   The computer-implemented method of claim 14, further comprising determining the possible response in response to the transaction.