Data transmission control method, data transmitting method, data transmitting apparatus, and receiving apparatus
First Claim
1. A data transmission control method, comprising:
- repetitively transferring a cyclic data unit for a desired period of time, the cyclic data unit including desired data that is also transferred,processing the cyclic data unit by enabling a client that receives the cyclic data unit from a server to determine that the cyclic data unit contents were switched, andswitching control information included in the cyclic data unit, andwherein processing the cyclic data is realized by setting a control information change event which denotes that the control information has been received under a standard of a predetermined interface, andthereafter, executing at least—
a first process for allowing the client to transmit a subscribe event to indicate reception of the control information change event to the server, a second process for allowing the client to transmit an event notice requesting notification of generation of an event to the server, anda third process for notifying the client that the control information change event has been generated when the changed control information is received by the server in response to the event notice request.
1 Assignment
0 Petitions
Accused Products
Abstract
A client transmits an event of Event::Subscribe (“DSI—CHANGED”) to a server. The server returns an event number set for a “DSI—CHANGED” event to the client. After the event number is obtained, the client transmits Event::notify to the server and requests some event generation notice including “DSI—CHANGED”. When there is a change in DSI of a karrusel which was received, namely, when the “DSI CHANGED” event is generated at a certain timing after Event::notify is received, the server transmits the event number corresponding to the “DSI—CHANGED” event to the client as a response to Event::notify. The contents of the karrusel before the event number is generated is continuously used for a period of time during which the client transmits Session::detach to the server after the server notified the client of the generation of the event number.
85 Citations
13 Claims
-
1. A data transmission control method, comprising:
-
repetitively transferring a cyclic data unit for a desired period of time, the cyclic data unit including desired data that is also transferred, processing the cyclic data unit by enabling a client that receives the cyclic data unit from a server to determine that the cyclic data unit contents were switched, and switching control information included in the cyclic data unit, and wherein processing the cyclic data is realized by setting a control information change event which denotes that the control information has been received under a standard of a predetermined interface, and thereafter, executing at least— a first process for allowing the client to transmit a subscribe event to indicate reception of the control information change event to the server, a second process for allowing the client to transmit an event notice requesting notification of generation of an event to the server, and a third process for notifying the client that the control information change event has been generated when the changed control information is received by the server in response to the event notice request. - View Dependent Claims (2, 3, 4)
-
-
5. A data transmission control method, comprising:
-
repetitively transferring a cyclic data unit, the cyclic data unit including one or more data transmission units that are to be transferred for a predetermined period of time, each data transmission unit including an object that is related by a scenario description of a predetermined system, and processing the cyclic data unit by enabling a client that receives the cyclic data unit from a server to be notified that the object has been updated, and wherein control information whose contents are updated in accordance with the updating of the object and relate to the data transmission unit is included in the cyclic data unit, said processing step including setting a control information updating event which denotes that the control information has been received under a standard of a predetermined interface, and thereafter, executing at least— a first process for allowing the client to transmit a subscribe event to indicate reception of the control information updating event to the server, a second process for allowing the client to transmit an event notice requesting notification of generation of an event to the server, and a third process for notifying the client that the control information updating event has been generated when the updated control information is received as a response by the server to said the event notice request. - View Dependent Claims (6, 7, 8, 9, 10, 11, 12, 13)
-
Specification