KR20090118955A - Secured cross platform networked multiplayer communication and game play - Google Patents

Abstract

A user of a software application (e.g., game or title) running at a gaming console may interact securely in real-time with a user of the same software application running at a general purpose computing device. Thus, a game player on the gaming console may play online over a secured communication channel with a game player on a PC.

Description

SECURERED CROSS PLATFORM NETWORKED MULTIPLAYER COMMUNICATION AND GAME PLAY} Secure Cross-Platform Network Multiplayer Communication and Gameplay

Software applications such as FPS (first-person shooter) game is available in both a game console (eg, Xbox ^TM, Microsoft) and personal computer (PC). However, the game console cannot communicate with the PC via a network connection. Thus, for example, a game console cannot play online video games with a PC.

XBox Live ^TM is an online multiplayer gaming and content distribution system that creates so operated by Microsoft. Live Anywhere ^TM micro Thorpe has less functionality for a variety of non--Xbox platforms such as the PC and the mobile phone must be connected to Xbox Live. For example, cross-platform play is not possible, so a PC player cannot compete with an Xbox player.

A user of a software application (eg, a game or title) running on a game console can have secure interactions in real time with a user of the same software application running on a general purpose computing device such as a PC. Thus, the game player of the game console can play online with the game player on the PC. The game console may be in secure communication with a general purpose computing device, for example, via a clearinghouse or directly via a network or system link connection.

Stacks and ports are configured to accommodate cross-platform functionality. In addition, big-endian and little-endian byte ordering are provided as well as secure key exchange.

This description is provided to introduce a selection of concepts in a simplified form that are disclosed in detail in the Examples below. This description is not to be interpreted as to identify key aspects or key aspects of the claimed subject matter, and is not to be construed as limiting the scope of the claimed subject matter.

1 is a block diagram of an exemplary cross-platform network system.

2 is a block diagram of another exemplary cross-platform network system.

3 is a flow chart of an exemplary porting technique.

4 is a diagram of an exemplary key exchange process for a clearinghouse embodiment.

5 is a diagram of an exemplary key exchange process for a system link embodiment.

6 illustrates an exemplary operating environment.

1 is a block diagram of an exemplary cross-platform system in which game console 10 is networked with general purpose computing device 30 via clearinghouse 20. Game console 10 may be any computing device applied to online games. For example, game console 10 may be a personal computer (PC) loaded with one or more online game titles. Game console 10 may be a portable device and may be utilized for use of one or more game titles. The game title may be a discrete application that may be loaded and executed on game console 10. Game titles may be stored on media that can be read by game console 10, such as CDs, DVDs, game cartridges, and the like.

Typically, a user can own many game titles. A user may load and execute individual game titles on game console 10 to play online games with other users who load and execute the same game titles on their respective game consoles or computing devices.

Game console 10 is preferably a game-only console, such as, for example, Microsoft's Xbox ^™, and general purpose computing device 30 is preferably, for example, a PC, a portable device or a mobile phone. Clearinghouse 20 may be, for example, an online multiplayer game and content distribution service or system such as XBox Live ^™ . Game console 10 and computing device 30 may each communicate with clearinghouse 20 via, for example, the Internet or other network.

The clearinghouse 20 preferably has its own network stack protocol 22 for secured internet access. The network stack protocol 22 described in detail below is used by the game console 10 and may be ported to the computing device 30 such that the computing device 30 has code having the same protocol as the clearinghouse 20. Can be. Protocol may talk to the cross-platform between the game console 20 and the computing device 30. [

There is a key exchange that includes the platform type (eg game console, PC, etc.) to achieve reliability. The platform type may be included in the key exchange message and sent via the clearinghouse 20, for example, to confirm that the device is a game console or a PC. Key exchange is described in detail below.

FIG. 2 illustrates an example system where the game console is networked with the general purpose computing device 30 directly, rather than through the clearinghouse 20 as in FIG. 1, for example, via a system link or a local area network (LAN) connection. It is a block diagram.

System links allow game consoles to connect directly to each other without having to go through a clearing house. The protocol for establishing this connection is different from establishing a connection with the console through the clearing house. Instead of going through the clearinghouse, the console sends out broadcast packets and waits for a response. This means that the system link does not work over any type of router unless the system link operates on a subnet and is set up to route broadcast traffic. Preferably, the broadcast packet is encrypted using a shared key (per game title). The key structure may accept a flag indicating cross-platform play.

Thus, a user of a software application (e.g., a game or a title) running on a game console can interact in real time with a user of the same software application running on the computing device. As a result, the game player on the game console can play online with the game player on the PC.

Although one game console 10 and one computing device 30 are shown in FIGS. 1 and 2, a plurality of consoles 10 and computing devices 30 via clearinghouses, system links, LANs, or other means are shown. Consider that they can be networked with each other.

On a general purpose computing device, a plurality of processes may be executed simultaneously, such as when a plurality of dedicated server instances are running or when a game dashboard is run as a separate application. Thus, each process or application may require its own broadcast port and possibly a different game data port.

An IP broadcast is sent to a specific port of a general purpose computing device, which may be dedicated to the title and may also be set by the user. Thus, each title can default to its own selected port or allow the user to select a port to use.

3 is a flowchart of an exemplary porting technique for system link establishment. At 200, a game title or other application is run on a general purpose computing device. In step 210, the port is determined by the computing device. The port may be based on the game title or application being operated or set by the user. In operation 220, the computing device sets a port accordingly.

Ethernet level addressing is commonly used in game console broadcasting. In other words, the packet is routed directly to the MAC address of the receiver below the IP level. Thus, the address of the IP header is not used and is meaningless, preferably set to a specific address (e.g. 0.0.0.1) and transmitted from a particular port (e.g. port 3074). Thus, the port used in the computing device for cross-platform network game play may be different from the port used in the game console (eg, port 3074). It should be taken into account that the port on the game console may change depending on the game title or user settings, for example.

On game consoles, cross-platform communication is preferably only possible when the cross-platform dedicated bits are set in the game's executable header. Bits that can be set indicate that the game uses the IP addressing that is used for the system link instead of Ethernet addressing. This allows the system to link between the game console and the general purpose computing device. If the bit is not set, the first key exchange between the game console and the general purpose computing device is rejected.

On a computing device, cross-platform communication is preferably always possible.

In order to set the port to use for system link broadcast, the initiated API can be called from the application or game code. An application or game can pin the ports it uses on its code or provide a user interface for the user to observe and modify the ports used. The setting of the system link port is preferably maintained at the port used for connection through the clearinghouse, for example 3074, or does not affect ports negotiated with the device unless 3074 is allowed.

An example of the API is as follows.

XNetSetSystemLinkPort

INT WSAAPI XNetSetSystemLinkPort (

WORD wSystemLinkPort

).

The wSystemLinkPort parameter refers to the port number used for system link broadcast and data. If successful, the API returns 0, otherwise it returns an error code. For example, XNetSetSystemLinkPort will fail if the XEX_PRIVILEGE_CROSSPLATFORM_SYSTEM_LINK bit is not set in the game's executable header. If the selected port is in use by the system, for example "Address in use" may be returned.

In one example, port 3074 is the default port unless XNetSetSystemLinkPort is called. Preferably, the XNetSetSystemLinkPort is called before the application or game starts up, otherwise the application or game fails.

If the XNetSetSystemLinkPort is successful, it is guaranteed that the configuration port is available for binding when the application or game is started. In other words, the XNetSetSystemLinkPort locks the port for use, so there is no possibility that the port will be held by another process between the call to the XNetSetSystemLinkPort and the startup of the application or game.

Port numbers are not persistent to disk and are stored globally for use until the application or game exits. When the application or game ends, the system link port is reset (e.g., returns to 3074).

Another API is disclosed to obtain a system link port.

XNetGetSystemLinkPort

INT WSAAPI XNetGetSystemLinkPort (

WORD * pwSystemLinkPort

).

The pwSystemLinkPort parameter is the port number currently set for system link broadcasts and data.

If successful, the API returns 0, otherwise it returns an error code. XNetGetSystemLinkPort will fail if the XEX_PRIVILEGE_CROSSPLATFORM_SYSTEM_LINK bit is not set in the game's executable header.

Preferably secured key exchange is performed. For an embodiment using a clearinghouse, the exemplary connection protocol preferably requires that all connections between clients (game console and general purpose computing device) request a key exchange. The packets are examined to determine if they are from a general purpose computing device. In this case, the information is directed to a clearing house or other destination so that the data can be processed differently if necessary.

4 is a diagram of an exemplary key exchange process for a clearinghouse embodiment and client 400 such as a game client communicating with authentication service 410, clearinghouse key server 420, and clearinghouse gateway server 430. Shows.

The game client 400 sends login credentials 405 to the authentication service 410. The authentication service 410 responds to the client with an authentication ticket 415. The game client 400 provides an authentication ticket 415 to the clearinghouse key server 420. Clearinghouse key server 420 responds to clearinghouse gateway server 430 with clearinghouse ticket 425 and pointer 427. The game client 400 may connect to the clearinghouse gateway server 430 to use the clearinghouse service.

The key exchange message preferably contains the port number that the machine running the game should use to connect with the clearinghouse.

As disclosed with reference to FIG. 5, in an embodiment that does not use a clearinghouse (eg, a system link embodiment), key exchange preferably uses a flag of a key that represents a cross-platform connection.

5 is a diagram of an exemplary key exchange process for a system link embodiment. 5 shows game client 500 operating as a host and other game clients 550. The client may, for example, communicate over a LAN subnet. Although not shown, additional game clients on the network should also be considered.

The host game client 500 broadcasts its presence and availability 505. The game client 550 decrypts the broadcast and responds with the broadcast to join the game 510. The host game client 500 accepts the participation request and broadcasts the game session key 515. Game clients 500 and 550 preferably unicast with each other 520 to conduct a game session. In a computer network, unicast is the transmission of information packets to a single destination. Preferably, all broadcasts are encrypted with a title-only key and all unicasts are encrypted with a game session-only key.

With respect to byte ordering, in computing, endianness is the ordering used to represent some type of data, such as a series of smaller units. Typical cases are the order in which integer values are stored as bytes in computer memory (in relation to a given memory addressing technique) and the order of transmission over the network. In terms of bytes, endianness is also referred to as byte order.

Most computer processors simply store integers as sequences of bytes so that the conceptually encoded values can be obtained by simple concatenation. For n-byte integer values this allows for a possible representation of n! (one for each byte permutation). Two of their most common methods are storing increasing digits in increasing memory addresses, known as little-endian, and vice versa, called big-endian.

All computer architectures are big-endian or little-endian. Big-endian architectures are found, for example, on Microsoft's Xbox and IBM's Power PCs, and Intel x86 processors (and their clones) use the little-endian format.

6 and the following description are intended to provide a brief general disclosure of a suitable computing environment in which the present invention and / or portions thereof may be implemented. Although not required, the invention is disclosed in the general context of computer-executable instructions, such as program modules, being executed by a computer, such as a client workstation or server. Generally, program modules include routines, programs, objects, components, data structures, and the like, that perform particular tasks or implement particular abstract data types. Furthermore, the present invention and / or portions thereof may be practiced with other computer system configurations including portable devices, multiprocessor systems, microprocessor-based or programmable electronics, network PCs, minicomputers, mainframe computers, and the like. have. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

As shown in FIG. 6, an exemplary general purpose computing system includes a system bus 123 that couples various system components, including the processing unit 121, system memory 122, and system memory, to the processing unit 121. Includes a conventional personal computer 120 and the like. System bus 123 may be any of a variety of types of bus structures, including memory buses or memory controllers, peripheral buses, and local buses using any of a variety of bus architectures. The system memory includes a read-only memory (ROM) 124 and a random access memory (RAM) 125. A basic input / output system (BIOS) 126 is stored in the ROM 124 that includes basic routines that assist in transferring information between components within the personal computer 120 during startup.

The personal computer 120 includes a hard disk drive 127 for reading from and writing to a hard disk (not shown), a magnetic disk drive 128 for reading from and writing to a removable magnetic disk 192, and a CD- It may further include an optical disk drive 130 for reading from and writing to a removable optical disk 131, such as a ROM or other optical media. The hard disk drive 127, the magnetic disk drive 128, and the optical disk drive 130 are connected to the system bus 123 by the hard disk drive interface 132, the magnetic disk drive interface 133, and the optical disk drive interface 134, respectively. Connected with The drives and their associated computer-readable media provide non-volatile storage of computer readable instructions, data structures, program modules, and other data for the personal computer 120.

Although the exemplary environment disclosed herein uses a hard disk, removable magnetic disk 192 and removable optical disk 131, other types of computer readable media that can store data that can be accessed by a computer are also illustrated. It can be understood that it can be used in a normal operating environment. Such other types of media include magnetic cassettes, flash memory cards, digital video discs, Bernoulli cartridges, random access memory (RAM), read-only memory (ROM), and the like.

 Many program modules, including operating system 135, one or more application programs 136, other program modules 137, and program data 138, include hard disks, magnetic disks 129, optical disks 131, and ROMs 124. Or RAM 125. A user may enter commands and information into the personal computer 120 through input devices such as keyboard 140 and pointing device 142. Other input devices (not shown) may include a microphone, joystick, game pad, satellite disc, scanner, or the like. These input devices are connected to the processing unit 121 via a serial port interface 146 that is connected to the system bus, but may also be connected through another interface, such as a parallel port, a game port, or a universal serial bus (USB). The monitor 147 or other type of display device is also connected to the system bus 123 via an interface such as a video adapter 148. In addition to the monitor 147, personal computers typically include other peripheral output devices (not shown) such as speakers and printers. The example system of FIG. 6 also includes a host adapter 155, a small computer system interface (SCSI) bus 156, and an external storage device 162 connected with the SCSI bus 156.

Personal computer 120 may operate in a network environment using a logical connection with one or more remote computers, such as remote computer 149. The remote computer 149 may be another personal computer, server, router, network PC, peer device or other common network node, with only memory storage 150 shown in FIG. 6 but typically associated with the personal computer 120. To include all or a large portion of the components disclosed above. The logical connection shown in FIG. 6 includes a local area network (LAN) 151 and a wide area network (WAN) 152. Such networking environments are commonplace in offices, enterprise computer networks, intranets and the Internet.

When used in a LAN networking environment, the personal computer 120 is connected to the LAN 151 via a network interface or adapter 153. When used in a WAN networking environment, the personal computer 120 typically includes a modem 154 or other means for establishing communications over the WAN 152, such as the Internet. The modem 154, which may be internal or external, is connected to the system bus 123 via the serial port interface 146. In a networked environment, program modules disclosed in connection with personal computer 120 or portions thereof may be stored in a remote memory storage device. It is to be understood that the network connections shown are exemplary and other means for establishing a communication link between the computers can be used.

While the subject invention has been disclosed in language related to structural aspects and / or methodological acts, it is to be understood that the subject invention defined in the appended claims need not be limited to the specific aspects or acts disclosed above. Moreover, the specific aspects and acts disclosed above are disclosed as example forms of implementing the claims.

Claims (20)

A first computing device having a first platform to execute an application 10; And A second computing device in communication with the first computing device 30 having a second platform to execute the application Including, The second platform is different from the first platform, and both the first computing device and the second computing device are operable to interact online with the application in real time. The method of claim 1, The application is a game title (200) cross-platform system. The method of claim 1, The first computing device is a game console (10) and the second computing device is a general purpose computing device (30). The method of claim 3, The game console has a network stack protocol (22, 23) ported to the general purpose computing device. The method of claim 1, And the first computing device and the second communication device communicate directly with each other via a network (520). The method of claim 1, Wherein the first computing device and the second communication device are in direct communication with each other through a clearinghouse (20). The method of claim 6, The clearinghouse includes a multiplayer game and a content delivery service or system (420, 430). The method of claim 6, Wherein the clearinghouse is operable to identify (420) the type of the first computing device and the type of the second computing device. Connecting the first computing device having the first platform to execute the application 10 with the clearinghouse 20; And Connecting a second computing device having a second platform to run the application 30 with the clearinghouse 20 Including, The second platform is different from the first platform, and both the first computing device and the second computing device are operable to interact online with the application in real time. The method of claim 9, Authenticating the first computing device prior to connecting with the clearinghouse (420). The method of claim 10, Authenticating the first computing device comprises: Logging (420) the first computing device to an authentication server and a key server; And Providing a clearing house ticket (425) and a pointer (427) to the first computing device. The method of claim 11, The connection (400, 430) is performed in response to the clearinghouse ticket (425) and the pointer (427). The method of claim 9, The application is a game title (200) cross-platform communication method. The method of claim 9, Wherein said first computing device is a game console (10) and said second computing device is a general purpose computing device (30). The method of claim 9, The clearinghouse is a multiplayer game and content distribution service or system (420, 430). Broadcasting a request 505 usable from the first computing device 500 to the second computing device 550, wherein the first computing device has a first platform and the second computing device is the first computing device. Having a second platform different from one platform; Directly connecting (515) the first computing device and the second computing device; And Executing (520) an application on the first computing device and the second computing device such that both the first computing device and the second computing device are operable to interact online in real time with the application. Cross-platform communication method comprising a. The method of claim 16, And wherein the first computing device sends (515) a session key to the second computing device prior to connecting the first computing device and the second computing device. The method of claim 16, The application is a game title (510). The method of claim 16, Wherein said first computing device is a game console (10) and said second computing device is a general purpose computing device (30). The method of claim 16, And the first computing device and the second computing device are unicast (520) to each other.

Images