WO2006100616A2 - Notification of a receiving device about a forthcoming transmission session - Google Patents
Notification of a receiving device about a forthcoming transmission session Download PDFInfo
- Publication number
- WO2006100616A2 WO2006100616A2 PCT/IB2006/050735 IB2006050735W WO2006100616A2 WO 2006100616 A2 WO2006100616 A2 WO 2006100616A2 IB 2006050735 W IB2006050735 W IB 2006050735W WO 2006100616 A2 WO2006100616 A2 WO 2006100616A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- transmission session
- identifier
- forthcoming
- receiving device
- session
- Prior art date
Links
- 230000005540 biological transmission Effects 0.000 title claims abstract description 251
- 238000000034 method Methods 0.000 claims description 50
- 238000012545 processing Methods 0.000 claims description 33
- 238000013507 mapping Methods 0.000 claims description 19
- 238000004891 communication Methods 0.000 claims description 18
- 238000002716 delivery method Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 8
- 239000010410 layer Substances 0.000 description 7
- 238000010295 mobile communication Methods 0.000 description 7
- 230000008901 benefit Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 239000002346 layers by function Substances 0.000 description 4
- 238000013459 approach Methods 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000008439 repair process Effects 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 230000004913 activation Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/26—Network addressing or numbering for mobility support
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
Definitions
- the invention relates to methods of notifying a receiving device about a forthcoming transmission session.
- the invention relates equally to corresponding transmitting devices, to corresponding receiving devices, to corresponding communication networks and communication systems and to corresponding software program products .
- Multimedia Broadcast/Multicast Service is a point- to-multipoint service in which data is transmitted from a single source to multiple destinations at the same time. MBMS thus enables an efficient sharing of network resources when the same data has to be transmitted to several receivers .
- the MBMS system can be divided into three functional layers, as illustrated in Figure 1.
- a first layer 10 corresponds to the bearer services
- a second layer 11 corresponds to the delivery method
- a third layer 12 corresponds to the user services enabling applications .
- An MBMS bearer service provides the mechanisms to transport multicast and broadcast Internet Protocol (IP) data to User Equipment efficiently.
- IP Internet Protocol
- a delivery method can either be a download delivery method or a streaming delivery method.
- a delivery method may use one or many MBMS bearers and/or one or many point-to-point (OTO) bearers to deliver data.
- the user services enable applications on top of MBMS and may use one or several delivery methods to deliver the application data, for instance data for a multimedia messaging service (MMS) message .
- MMS multimedia messaging service
- a single MBMS Bearer Service #x of the first layer is used for several MBMS Download Sessions #n, #n+l, etc., of the third layer. These MBMS Download Sessions are used for an MBMS download user service of the third layer.
- the TMGI is allocated globally by the BM-SC and is composed of a local MBMS bearer service identity having a size of three octets, or bytes, as well as a Public Land Mobile Network (PLMN) identity of the PLMN to which the BM-SC belongs.
- PLMN Public Land Mobile Network
- the TMGI is equivalent to the IP multicast address and Access Point Name (APN) pair, and is used for an efficient identification of the employed MBMS bearer.
- the TMGI is transmitted to the UE during the MBMS session activation for multicast sessions or during service announcement for broadcast sessions.
- the UE When an MBMS session starts, the UE is notified about a starting or ongoing data transmission through an MBMS notification procedure, as illustrated in Figure 3 by way of example for a GSM EDGE RAN (GERAN) .
- the TMGI and an optional Session ID are provided by the BM-SC to a Base Station Controller (BSC) of the GERAN.
- BSC Base Station Controller
- the BSC pages the TMGI and the optional Session ID to the mobile stations (MS) constituting the UE to inform them about the starting data transmission.
- the paging is performed independently of the current state of the mobile stations, which may be idle or connected.
- the GERAN may also prompt the terminals by a further paging request to reply to notifications for per-cell counting purposes by means of a channel request.
- the mobile stations have to transmit a channel request to the BSC, if they are interested in the MBMS session.
- the GERAN may then count the incoming channel requests .
- the counting process is important to determine the most efficient data transmission mode for a given cell.
- the GERAN may decide to use point-to-point transmissions instead of a point-to- multipoint transmission in this cell.
- the mobile stations evaluate the TMGI and the Session ID for deciding whether they are interested in the MBMS session or not.
- Session ID during the notification, the problem of how to use this field efficiently arises.
- the Session ID octet should carry enough information to allow the mobile stations to decide whether the data was already received or not.
- no direct mapping between the larger download session ID and the smaller MBMS Session ID is possible without loss of precision.
- the document Tdoc S4-050103 further proposes the usage of a validity timer at the mobile stations.
- This validity timer is intended to limit the validity of a Session ID to a given time duration, after which the mobile station should assume that the data carried over the MBMS session with a previously received Session ID value is a new delivery or transmission and not a continuation or repetition. Once an instance of a Session ID has expired, the value may thus be used for another transmission, that is, for another Session ID instance. This is supposed to allow reusing Session IDs without risking that the UE misinterprets the Session ID as a previous MBMS transmission session instance.
- Session ID is optional. Both, UE and BM-SC may decide to ignore the Session ID field. If the UE decides to ignore the Session ID field, the UE will simply not interpret the Session ID field. It will assume that the MBMS session is a new session and make its decision independently. If the BM-SC decides not to use the Session ID field, for instance by setting it to a default value, however, it has to be ensured that the UE will not misinterpret it.
- a transmitting device comprising means for realizing the first method of the first aspect of the invention is proposed.
- a communication network comprising such a transmitting device is proposed.
- a communication system comprising such a transmitting device and a receiving device is proposed.
- a software program product is proposed, which stores a software code realizing the steps of the first method of the first aspect of the invention when running in a processing unit of a transmitting device.
- a receiving device comprising means for realizing this second method of the first aspect of the invention.
- a software program product is proposed, which stores a software code realizing the steps of the second method of the first aspect of the invention when running in a processing unit of a receiving device.
- the first aspect of the invention proceeds from the idea that by choosing between different types of identifiers as a basis for the transmission session identifier, the granularity information can be set as required.
- the at least two types of identifiers from which an identifier can be selected as a basis for the mapping to the transmission session identifier can be of various kinds .
- the types of identifiers may further comprise for instance a common identifier identifying all files of a transmission session.
- a single transmission session identifier may be created for all files declared in one FDT Instance.
- the transmission session identifier may be created from the LSBs of the FDT Instance ID.
- the types of identifiers may further comprise for instance a delivery session identifier identifying a delivery session.
- the delivery session is the entire session for a complete application or user service, which may use one or more transmission sessions for transmitting the involved application data.
- the transmission session identifier may be generated from the LSBs of the Transport Session Identifier (TSI) or from the TMGI.
- TSI Transport Session Identifier
- the types of identifiers may further comprise for instance a file Uniform Resource Identifier (FiIeURI) identifying a FLUTE File Delivery Table Instance of a transmission session.
- FiIeURI file Uniform Resource Identifier
- the FiIeURI can be used similarly as a TOI .
- a new type of identifiers can be defined in the session to provide a selectable specific identifier.
- a new FDT field including an element or an attribute, can be introduced to provide data, from which the transmission session identifier can be created.
- the decision which identifier type is to be used can be made by the transmitting device.
- the transmitting device can, for instance, decide to create a transmission session for each large file or for a file group and assign to it a corresponding transmission session identifier.
- mapping can be of various kinds.
- the mapping may include selecting at least a predetermined portion of the at least one identifier of the selected identifier type to obtain the transmission session identifier. For example, the least significant byte or a predetermined number of the LSBs of the identifier could be employed as the transmission session identifier.
- the mapping may also include combining at least a respective portion of at least two identifiers of the selected identifier type to obtain the transmission session identifier.
- the mapping may also include generating a hash value based on at least a portion of the at least one identifier of the selected identifier type to obtain the transmission session identifier. For instance, the binary- sum of all related TOIs could be hashed.
- the employed hash function should be known at the transmitting device and the receiving device.
- the transmission session identifier could have a size of one octet, that is, of eight bites, but equally any other suitable size. Further, in case a predetermined portion of identifiers is used for a mapping to the transmission session identifier, this predetermined portion can be selected in various ways. For instance, the least or most significant octet, the LSBs or the most significant bits (MSBs) could be used, or the hash of the least or most significant four bytes, etc.
- a first method of notifying a receiving device about a forthcoming transmission session comprises at a transmitting device inserting into a transmission session identifier field a repetition value indicating whether the forthcoming transmission session is a repetition or not. This method further comprises providing the transmission session identifier field for a notification of the receiving device about the forthcoming transmission session.
- a transmitting device comprising means for realizing the first method of the second aspect of the invention is proposed.
- a communication network comprising such a transmitting device is proposed.
- a communication system comprising such a transmitting device and a receiving device is proposed.
- a software program product is proposed, which stores a software code realizing the steps of the first method of the second aspect of the invention when running in a processing unit of a transmitting device.
- a second method of notifying a receiving device about a forthcoming transmission session comprises at a receiving device receiving a notification about a forthcoming transmission session.
- the method further comprises evaluating a repetition value in a transmission session identifier field in the notification.
- the timer estimation accuracy can also significantly influence the performance of a possible counting mechanism, so avoiding the a-priori signaling of a timer estimate will enhance the accuracy of the counting.
- the most significant bit (MSB) of the transmission session identifier field is reserved to signal to the receiving device whether the following session is a repetition or not.
- a value of f 0 f may then indicate that the session is a new session and a value of f l f may indicate that the session is a repetition session, or vice versa.
- the transmission device may decide whether a transmission session identifier is to be used at all. The same predetermined repetition value may then be used for the case the transmission session is a new transmission session and for the case no transmission session identifier is to be used. Thus, when the transmission session identifier field is not used, there will always be an indication to the receiving device that the forthcoming transmission session is a new session.
- the transmitting device may set the repetition value to a value indicating that a forthcoming transmission session is a new transmission session after a predetermined period of time after the repetition value has last been set to a value indicating that a forthcoming transmission session is a new transmission session.
- the transmitting device may maintain to this end a timer for the validity of a given transmission session identifier. If the timer expires or if a wrap around is made, the transmission device may set the repetition value to a value indicating that a forthcoming transmission session is a new transmission session.
- a method of notifying a receiving device about a forthcoming transmission session comprises at a receiving device determining for a transmission session identifier that an acquisition of data in transmission sessions identified by the transmission session identifier can be terminated. The method further comprises releasing context data stored for this transmission session identifier.
- a receiving device comprising means for realizing this method of the third aspect of the invention is proposed.
- a software program product is proposed, which stores a software code realizing the steps of the method of the third aspect of the invention when running in a processing unit of a receiving device.
- the third aspect of the invention proceeds from the idea that in some cases, the receiving device can unequivocally determine by itself whether an acquisition of data of a particular transmission session is still appropriate or possible.
- the end of a file or file group transmission is detected or determined. This may be the case, for example, if the most recent FDT Instance describing a TOI expires, if the end-of-object is received, etc.
- the end of download session is detected or determined. This may be the case, for example, if the SDP end time is reached, if an end-of- session flag is received, etc.
- Determining or detecting that the context data for a specific transmission session identifier instance may be released can be used, for instance, to indicate from an application part of the receiving device to a bearer part of the receiving device not to respond to notifications/pages for that session transmission identifier, for example a TMGI or a bearer identifier. If the receiving device is user equipment of a mobile communication system, as a result, this receiving device will not be counted in a cell based count of responding receiving devices. It has to be noted that if a receiving device receives multiple "transmission sessions" using the same transmission session identifier value, all of those "transmission sessions" should be released before the context data for the session transmission identifier is released. It is to be understood that the different aspects of the invention can be employed by themselves or in any combination.
- a transmitting device can be for example, though not exclusively, a BM-SC.
- a receiving device can be for example, though not exclusively, user equipment of a mobile communication system, like a mobile station.
- the transmission session can be for example, though not exclusively, an MBMS session providing for instance a streaming or download service .
- Fig. 1 is a schematic diagram of the functional layers of an MBMS service delivery
- Fig. 2 is a schematic diagram illustrating the relation between the functional layers of Figure 1
- Fig. 3 is a schematic diagram illustrating the notification process for an MBMS session in
- GERAN GERAN
- Fig. 4 is a schematic diagram of a communication system in which an embodiment of the invention can be implemented
- Fig. 5 is a schematic block diagram of an embodiment of a mobile terminal and of an embodiment of a BM-
- Fig. 6 is a flow chart schematically illustrating the operation at the BM-SC of Figure 5
- Fig. 7 is a schematic diagram illustrating the structure of a Session ID field employed in the communication system of Figure 4
- Fig. 8 is a flow chart schematically illustrating the operation at the mobile terminal of Figure 5.
- Figure 4 is a schematic diagram of an exemplary communication system, in which a notification of user equipment about a forthcoming MBMS session can be implemented in accordance with the invention.
- the core network comprises a plurality of SGSNs (Serving GPRS Support Node) 41, of which only one is depicted, a GGSN 42 and a BM-SC 60.
- a content server 46 of an MBMS user service provider may be connected to the BM-SC 60 for example via the Internet (not shown) .
- the BM-SC 60 enables MBMS sessions between the content server 46 and the mobile terminals 80 via the GGSN 42, a respective SGSN 41 and a respective RAN 44.
- the mobile stations 80 are thus receiving devices according to the invention, while the BM-SC 60 is a transmitting device according to the invention.
- FIG. 5 is a block diagram illustrating some details of a mobile terminal 80 and of the BM-SC 60 of the communication system of Figure 4 that are employed in the presented embodiment of the invention.
- the BM-SC 60 comprises a processing unit 61 running software codes implemented in the BM-SC 60, including a notification support software 62. It is to be understood that the notification support software 62 may form a part of a more comprehensive software code used by the BM-SC 60.
- the BM-SC 60 further comprises a memory 63 storing a table 64 with 128 one-bit entries for each supported user service. That is, each table entry can have the value f 0 f or the value f l f .
- the memory 63 can be accessed by the processing unit 61.
- MBMS Session ID value occurs, that is, if a MBMS Session ID value is used for the first time for a new MBMS session.
- the mobile terminal 80 comprises a processing unit 81 running software codes implemented in the mobile terminal 80, including a notification evaluation software 82. It is to be understood that the notification evaluation software 82 may form a part of a more comprehensive software code used by the mobile terminal 80.
- the mobile terminal 80 further comprises a memory 83 storing a table 84 with 128 entries for each requested user service. Each entry may comprise a download session ID, an FDT instance ID, a group ID, TOI (s) belonging to received data, and the reception time of data received with a respective MBMS Session ID field.
- Figure 6 is a flow chart illustrating the operation at the BM-SC 60. The indicated steps are performed more specifically by the processing unit 61 when running the notification support software 62.
- the BM-SC 60 When the BM-SC 60 intends to establish a new or a repeated MBMS session for transmitting content provided by the content server 46 for a particular user service (step 601) , it first determines whether or not to make use of an MBMS Session ID, in order to enable a more accurate counting of mobile terminals wishing to participate in the MBMS session at a cell level (step 602) .
- the BM-SC 60 sets the value of a MBMS session ID field to f 0 f for the forthcoming download session (step 603) .
- the BM-SC 60 assembles the data for a MBMS session ID field for the forthcoming download session.
- the structure of such a MBMS session ID field is illustrated in Figure 7.
- the MBMS session ID field 70 has the size of one octet and comprises seven LSBs for identity bits 71 and one bit for a session repetition flag 72.
- the BM-SC 60 first selects the type of IDs belonging to the download session that are to be used for the generation of the MBMS Session ID. More specifically, the BM-SC 60 determines the content that is to be transmitted in the MBMS session and selects, based on this content, the appropriate identifier type, (step 604) The BM-SC 60 selects, for example, a file of a download delivery session, a FLUTE file group, a file group, an external file group, all files declared in one FDT Instance or a download delivery session as a basis for generating the MBMS Session ID.
- the BM-SC 60 then maps the respective ID or IDs of the selected ID type to the seven LSBs of the MBMS session ID field as an MBMS session ID. (step 605)
- the BM-SC 60 maps the seven LSBs of the TOI of the file to the seven LSBs of the MBMS session ID field. If the MBMS Session ID is to be created, for example, for a FLUTE file group, the BM-SC 60 maps the seven LSBs of a group specific identifier that is transmitted in the FDT Instance ID to the seven LSBs of the MBMS session ID field.
- the BM-SC 60 If the MBMS Session ID is to be created, for example, for a file group, the BM-SC 60 generates a value of seven bits from the list of TOIs representing the list of files, for instance by means of a hash function. The BM-SC 60 then maps this value to the seven LSBs of the MBMS session ID field. If the MBMS Session ID is to be created, for example, for an external file group, the BM-SC 60 uses a mapping between the files of this external file groups and an MBMS session ID defined in some other data entity, like an SMS, an SDP file, etc., which other data entity has been communicated separately to the BM-SC 60, for instance by means of a FLUTE delivery, an SMS, etc.
- the MBMS Session ID may be based on a hash function applied to identifiers or portions of identifiers of single external files.
- the BM-SC 60 maps this MBMS session ID to the seven LSBs of the MBMS session ID field. If the MBMS Session ID is to be created, for example, for all files declared in one FDT Instance, the BM-SC 60 maps the seven LSBs of the FDT Instance ID to the seven LSBs of the MBMS session ID field. If the MBMS Session ID is to be created, for example, for a download delivery session, the BM-SC 60 maps the seven LSBs of the TSI to the seven LSBs of the MBMS session ID field.
- the BM-SC 60 then reads the value of the MSB associated in the table 64 by its index to the determined MBMS Session ID and adds the value to the MBMS session ID field as a session repetition flag at the position of the MSB of the MBMS session ID field, (step 606)
- the BM-SC 60 sets the MBS table entry to the value f l f . If the MBMS session is to be the last repetition of an MBMS session, however, the BM-SC 60 sets the MBS table entry to the value f 0 f . (step 607)
- the MBMS session ID field and a TMGI are then provided to the GGSN 42 as parts of an MBMS session start request, (step 608)
- the TMGI is allocated globally by the BM-SC 60 in a conventional manner and comprises thus a local MBMS bearer service identity and the PLMN identity of the mobile communication network 40, 44.
- the GGSN 42 takes care that a paging message including the TMGI and the session ID is generated and transmitted to the mobile terminals 80 via the RANs 44 as an MBMS session notification.
- Figure 8 is a flow chart illustrating the operation at the mobile terminal 80. The indicated steps are performed more specifically by the processing unit 81 when running the notification evaluation software 82.
- the mobile terminal 80 When receiving a paging request (step 801) , the mobile terminal 80 first decides whether an included MBMS session ID field should be evaluated (step 802) .
- the mobile terminal 80 decides not to evaluate the MBMS session ID field, it acquires the data of the forthcoming MBMS session for deciding whether the data is still required or not (not indicated) .
- the mobile terminal 80 If the mobile terminal 80 decides to evaluate the MBMS session ID field, it first checks the session repetition flag corresponding to the MSB of the MBMS session ID field, (step 803)
- the mobile terminal assumes that the data in the forthcoming MBMB session is new data. In this case, the mobile terminal 80 responds to the paging request, acquires the data in the MBMS session and overwrites the associated entry in the table 83 with the new data after having correctly received the session data.
- the index of the associated entry corresponds to the seven LSBs of the MBMS session ID field.
- the mobile terminal 80 When the mobile terminal 80 detects an event, however, that indicates that the context data stored for this MBMS session is not required any more, the mobile terminal 80 releases the context data, that is, the data in the table entry associated to the MBMS session, so that the table entry can be used for another MBMS session, (step 804) It has to be noted that the arrival of new data is also assumed, if the BM-SC 60 decided not to make use of an MBMS Session ID, as in this case the MSB of the MBMS session ID field is equally set to f 0 f . In this case, the index of the associated entry can be determined by the mobile station 80 based on an identifier in the acquired data.
- the mobile terminal 80 interprets this value as an indication of a session repetition. It selects the table entry having an index which corresponds to the seven LSBs of the MBMS session ID field (step 805) . If the item corresponding to this table entry is identified in the table 84 as having been received correctly (step 806) , the mobile terminal 80 does not respond to the MBMS notification message (step 807) . If the item corresponding to this table entry is not identified in the table 84 as having been received correctly (step 806) , in contrast, the mobile terminal 80 responds to the MBMS notification message.
- the mobile terminal 80 acquires the data in the MBMS session and overwrites the associated entry in the table 83 with the new data after having correctly received the session data.
- the mobile terminal 80 detect an event, however, that indicates that the context data is not required any more, the mobile terminal 80 releases the associated table entry so that it can be used for another transmission session. (step 808) .
- an accurate counting of the mobile terminals in a respective cell is allowed in the RAN 44 serving this cell, since only those mobile terminals respond to a paging message, which actually need the transmission. Consequently, the most appropriate transmission type, that is, point-to-point or point-to-multipoint, can be selected for the MBMS session in this cell, without requiring the mobile stations to use timers for determining the validity of the received MBMS Session IDs. Further, the finer granularity helps avoiding the transmission of redundant information.
Abstract
Description
Claims
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/596,398 US20080181158A1 (en) | 2005-03-24 | 2006-03-09 | Notification of a Receiving Device About a Forthcoming Transmission Session |
BRPI0608470-2A BRPI0608470A2 (en) | 2005-03-24 | 2006-03-09 | method for notifying the receiving device of a future transmission session, a transmission device that supports notification of the receiving device of a future transmission session, a communication network, a communication system, a program product, and a receiving apparatus |
EP06711058A EP1861949A2 (en) | 2005-03-24 | 2006-03-09 | Notification of a receiving device about a forthcoming transmission session |
JP2008502528A JP2008536373A (en) | 2005-03-24 | 2006-03-09 | Notification of the next transmission session to the receiving device |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US66590105P | 2005-03-24 | 2005-03-24 | |
US60/665,901 | 2005-03-24 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2006100616A2 true WO2006100616A2 (en) | 2006-09-28 |
WO2006100616A3 WO2006100616A3 (en) | 2007-03-29 |
Family
ID=36753970
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/IB2006/050735 WO2006100616A2 (en) | 2005-03-24 | 2006-03-09 | Notification of a receiving device about a forthcoming transmission session |
Country Status (9)
Country | Link |
---|---|
US (1) | US20080181158A1 (en) |
EP (1) | EP1861949A2 (en) |
JP (1) | JP2008536373A (en) |
KR (1) | KR100943935B1 (en) |
CN (1) | CN101185283A (en) |
BR (1) | BRPI0608470A2 (en) |
TW (1) | TW200701809A (en) |
WO (1) | WO2006100616A2 (en) |
ZA (1) | ZA200708125B (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1928198A1 (en) * | 2006-11-30 | 2008-06-04 | Sagem Communications | Method and device for determining a group call newly distributed by at least one base station of a cellular telephony system |
KR100848273B1 (en) | 2007-07-03 | 2008-07-25 | 삼성전자주식회사 | Device and method for processing file in digital broadcasting receiver |
WO2014169233A3 (en) * | 2013-04-12 | 2015-01-22 | Qualcomm Incorporated | Methods for delivery of flows of objects over broadcast/multicast enabled networks |
Families Citing this family (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1561306B1 (en) | 2002-11-12 | 2007-03-07 | Zetera Corporation | Communication protocols, systems and methods |
US8005918B2 (en) | 2002-11-12 | 2011-08-23 | Rateze Remote Mgmt. L.L.C. | Data storage devices having IP capable partitions |
US7170890B2 (en) * | 2002-12-16 | 2007-01-30 | Zetera Corporation | Electrical devices with improved communication |
US7649880B2 (en) | 2002-11-12 | 2010-01-19 | Mark Adams | Systems and methods for deriving storage area commands |
US7702850B2 (en) | 2005-03-14 | 2010-04-20 | Thomas Earl Ludwig | Topology independent storage arrays and methods |
US7620981B2 (en) | 2005-05-26 | 2009-11-17 | Charles William Frank | Virtual devices and virtual bus tunnels, modules and methods |
US8819092B2 (en) | 2005-08-16 | 2014-08-26 | Rateze Remote Mgmt. L.L.C. | Disaggregated resources and access methods |
US7743214B2 (en) * | 2005-08-16 | 2010-06-22 | Mark Adams | Generating storage system commands |
US9270532B2 (en) | 2005-10-06 | 2016-02-23 | Rateze Remote Mgmt. L.L.C. | Resource command messages and methods |
US7924881B2 (en) * | 2006-04-10 | 2011-04-12 | Rateze Remote Mgmt. L.L.C. | Datagram identifier management |
ATE522996T1 (en) * | 2007-04-23 | 2011-09-15 | Nokia Corp | SYSTEM AND METHOD FOR OPTIMIZING DOWNLOAD USER SERVICE DELIVERY TO ROAMING CLIENTS |
US7796585B2 (en) * | 2008-05-21 | 2010-09-14 | Dell Products, Lp | Network switching in a network interface device and method of use thereof |
WO2010036019A2 (en) * | 2008-09-25 | 2010-04-01 | Samsung Electronics Co., Ltd. | Method and system to support multimedia broadcast multicast service over generic access networks |
JP5400742B2 (en) * | 2010-10-18 | 2014-01-29 | 株式会社Nttドコモ | Unidirectional transmission system and content distribution method |
CN102655667B (en) * | 2011-03-04 | 2016-01-13 | 华为技术有限公司 | The method that control packet accesses, network equipment, terminal equipment and communication system |
JP5562317B2 (en) * | 2011-11-21 | 2014-07-30 | 株式会社日立製作所 | Wireless communication system and session sharing method |
CN103546513B (en) * | 2012-07-13 | 2016-12-21 | 阿里巴巴集团控股有限公司 | The method and device of communication between a kind of customer terminal webpage |
US10476693B2 (en) * | 2014-02-24 | 2019-11-12 | Lg Electronics Inc. | Apparatus for transmitting broadcast signals, apparatus for receiving broadcast signals, method for transmitting broadcast signals and method for receiving broadcast signals |
KR101966626B1 (en) * | 2016-02-11 | 2019-04-09 | 현대자동차주식회사 | Method and apparatus for updating software of electronic devices in a vehicle |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030073453A1 (en) * | 2001-10-11 | 2003-04-17 | Henrik Basilier | Systems and methods for multicast communications |
US20040132427A1 (en) * | 2002-10-12 | 2004-07-08 | Wan-Yeon Lee | Handling charging information in interworking structure of mobile communication and wireless local area networks |
WO2004088997A2 (en) * | 2003-04-03 | 2004-10-14 | Nokia Corporation | Broadcast/ multicast service signalling |
EP1507358A2 (en) * | 2003-08-14 | 2005-02-16 | Samsung Electronics Co., Ltd. | Method of using a service identifier for transmitting control information in a mobile communication system providing multimedia broadcast/multicast services |
WO2005039090A2 (en) * | 2003-10-06 | 2005-04-28 | Motorola, Inc. | Method and apparatus for assigning a temporary mobile group identity in a multimedia broadcast/multicast service |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH10512129A (en) * | 1995-10-24 | 1998-11-17 | フィリップス エレクトロニクス ネムローゼ フェンノートシャップ | System for transferring data in reassignable groups, transmitters and receivers for use in such systems, methods for transferring, transmitting and receiving such data and signals comprising such data |
US20030154398A1 (en) * | 2002-02-08 | 2003-08-14 | Eaton Eric Thomas | System for providing continuity between session clients and method therefor |
-
2006
- 2006-03-09 KR KR1020077021512A patent/KR100943935B1/en not_active IP Right Cessation
- 2006-03-09 EP EP06711058A patent/EP1861949A2/en not_active Withdrawn
- 2006-03-09 CN CNA2006800093419A patent/CN101185283A/en active Pending
- 2006-03-09 US US11/596,398 patent/US20080181158A1/en not_active Abandoned
- 2006-03-09 JP JP2008502528A patent/JP2008536373A/en not_active Withdrawn
- 2006-03-09 BR BRPI0608470-2A patent/BRPI0608470A2/en not_active IP Right Cessation
- 2006-03-09 WO PCT/IB2006/050735 patent/WO2006100616A2/en active Application Filing
- 2006-03-22 TW TW095109776A patent/TW200701809A/en unknown
-
2007
- 2007-09-21 ZA ZA200708125A patent/ZA200708125B/en unknown
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030073453A1 (en) * | 2001-10-11 | 2003-04-17 | Henrik Basilier | Systems and methods for multicast communications |
US20040132427A1 (en) * | 2002-10-12 | 2004-07-08 | Wan-Yeon Lee | Handling charging information in interworking structure of mobile communication and wireless local area networks |
WO2004088997A2 (en) * | 2003-04-03 | 2004-10-14 | Nokia Corporation | Broadcast/ multicast service signalling |
EP1507358A2 (en) * | 2003-08-14 | 2005-02-16 | Samsung Electronics Co., Ltd. | Method of using a service identifier for transmitting control information in a mobile communication system providing multimedia broadcast/multicast services |
WO2005039090A2 (en) * | 2003-10-06 | 2005-04-28 | Motorola, Inc. | Method and apparatus for assigning a temporary mobile group identity in a multimedia broadcast/multicast service |
Non-Patent Citations (1)
Title |
---|
3GPP TECHNICAL SPECIFICATION GROUP SERVICES AND SYSTEM ASPECTS: "TS 23.246 V6.2.0: Multimedia Broadcast/Multicast Service (MBMS); Architectural and functional description" March 2004 (2004-03), 3GPP TS 23.246 V6.2.0, PAGE(S) 1-40 , XP002302177 page 16, paragraph 5.2 pages 28-31, paragraphs 8.6.1,8.7 * |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1928198A1 (en) * | 2006-11-30 | 2008-06-04 | Sagem Communications | Method and device for determining a group call newly distributed by at least one base station of a cellular telephony system |
FR2909509A1 (en) * | 2006-11-30 | 2008-06-06 | Sagem Comm | METHOD AND DEVICE FOR DETERMINING A NEWLY DIFFUSED GROUP CALL BY AT LEAST ONE BASE STATION OF A CELLULAR TELEPHONY SYSTEM. |
KR100848273B1 (en) | 2007-07-03 | 2008-07-25 | 삼성전자주식회사 | Device and method for processing file in digital broadcasting receiver |
WO2014169233A3 (en) * | 2013-04-12 | 2015-01-22 | Qualcomm Incorporated | Methods for delivery of flows of objects over broadcast/multicast enabled networks |
US9900166B2 (en) | 2013-04-12 | 2018-02-20 | Qualcomm Incorporated | Methods for delivery of flows of objects over broadcast/multicast enabled networks |
Also Published As
Publication number | Publication date |
---|---|
EP1861949A2 (en) | 2007-12-05 |
TW200701809A (en) | 2007-01-01 |
CN101185283A (en) | 2008-05-21 |
WO2006100616A3 (en) | 2007-03-29 |
JP2008536373A (en) | 2008-09-04 |
KR100943935B1 (en) | 2010-02-24 |
US20080181158A1 (en) | 2008-07-31 |
KR20070106638A (en) | 2007-11-02 |
BRPI0608470A2 (en) | 2010-01-05 |
ZA200708125B (en) | 2008-09-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20080181158A1 (en) | Notification of a Receiving Device About a Forthcoming Transmission Session | |
EP1668798B1 (en) | Method for distinguishing mbms service request from other service requests | |
EP1501328B1 (en) | Apparatus and method for transmitting / receiving MBMS control information in a mobile communication system | |
KR101019944B1 (en) | Transmission of signaling information for broadcast and multicast services | |
US20040229605A1 (en) | Method for transmitting MBMS paging information in a mobile communication system | |
US20050096017A1 (en) | Method for providing requested MBMS service to UEs that failed to receive paging message in a mobile communication system supporting MBMS service | |
EP1988668B1 (en) | Methods and apparatus for distinguishing between services provided in all frequency bands and services provided in a specific frequency band | |
US20060268774A1 (en) | Method and equipment for indicating and MBMS assignment via common control channel | |
JP2004159334A (en) | Paging method in mobile communication system for providing multimedia broadcast/multicast service | |
CN1518243A (en) | Mobile communication system, radio terminal, network controller and operation control method | |
CN1496139A (en) | Equipment and method for supply multimedia broadcasting/multi-broadcasting service for mobile communication system | |
EP1656751A1 (en) | Methods for paging user equipment with dedicated channel in a mobile communication system which support mbms | |
EP1507358A2 (en) | Method of using a service identifier for transmitting control information in a mobile communication system providing multimedia broadcast/multicast services | |
JP2009539302A (en) | Providing mobile TV information in MBMS | |
EP2878098B1 (en) | User equipment node, server node and methods performed in such nodes for performing file repair procedure | |
EP1463359B1 (en) | Including a hashed service identifier in a paging message for a service group call | |
KR20050059201A (en) | Temporary mobile group identity generation and distribution method in roaming status | |
KR20050014599A (en) | Method for efficiently paging an user equipment to transmit control information in a mobile communication system | |
WO2023151514A1 (en) | Method and apparatus for group message delivery | |
CN1842209A (en) | Method for providing MBMS service | |
CN1581986A (en) | Method for descriminating MBMS business request from other business requests | |
CN1581785A (en) | Method for discriminating MBMS business request from other business requests | |
CN1638493A (en) | Method of distinguishing MBMS service request from other service request |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2006711058 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 6634/DELNP/2007 Country of ref document: IN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020077021512 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2008502528 Country of ref document: JP Ref document number: 200680009341.9 Country of ref document: CN |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
NENP | Non-entry into the national phase |
Ref country code: RU |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: RU |
|
WWE | Wipo information: entry into national phase |
Ref document number: 11596398 Country of ref document: US |
|
WWP | Wipo information: published in national office |
Ref document number: 2006711058 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: PI0608470 Country of ref document: BR Kind code of ref document: A2 |