(19)
(11)EP 3 342 224 B1

(12)EUROPEAN PATENT SPECIFICATION

(45)Mention of the grant of the patent:
09.09.2020 Bulletin 2020/37

(21)Application number: 16857788.0

(22)Date of filing:  20.10.2016
(51)International Patent Classification (IPC): 
H04W 72/00(2009.01)
H04W 4/06(2009.01)
H04W 72/04(2009.01)
H04L 29/06(2006.01)
(86)International application number:
PCT/KR2016/011817
(87)International publication number:
WO 2017/069530 (27.04.2017 Gazette  2017/17)

(54)

METHOD AND APPARATUS FOR ADDRESS RESOLUTION OF MULTICAST/BROADCAST RESOURCES USING DOMAIN NAME SYSTEMS

VERFAHREN UND VORRICHTUNG ZUR ADRESSAUFLÖSUNG VON MULTICAST/BROADCAST-RESSOURCEN MIT DOMÄNENNAMENSYSTEMEN

PROCÉDÉ ET APPAREIL POUR LA RÉSOLUTION D'ADRESSE DE RESSOURCES DE DIFFUSION/MULTIDIFFUSION UTILISANT DES SYSTÈMES DE NOMS DE DOMAINE


(84)Designated Contracting States:
AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

(30)Priority: 20.10.2015 US 201562243696 P
18.10.2016 US 201615297058

(43)Date of publication of application:
04.07.2018 Bulletin 2018/27

(73)Proprietor: Samsung Electronics Co., Ltd.
Suwon-si, Gyeonggi-do 16677 (KR)

(72)Inventors:
  • BOUAZIZI, Imed
    Mountain View, CA 94043 (US)
  • PARK, Kyungmo
    Seoul 06284 (KR)

(74)Representative: Nederlandsch Octrooibureau 
P.O. Box 29720
2502 LS The Hague
2502 LS The Hague (NL)


(56)References cited: : 
US-A1- 2008 301 744
US-A1- 2014 222 906
US-A1- 2013 138 814
  
  • SAMSUNG ELECTRONICS CO ET AL: "Resource Addressing in MBMS with DNS Support", 3GPP DRAFT; S4-151353_DNS_RESOLUTION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE , vol. SA WG4, no. San Jose Del Cabo, Mexico; 20151026 - 20151030 22 October 2015 (2015-10-22), XP051015598, Retrieved from the Internet: URL:http://www.3gpp.org/ftp/Meetings_3GPP_ SYNC/SA4/Docs/ [retrieved on 2015-10-22]
  • SAMSUNG ELECTRONICS CO ET AL: "MBMS URL Handling", 3GPP DRAFT; S4-AHI528_MBMSURL, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE , vol. SA WG4, no. Telco; 20151008 8 October 2015 (2015-10-08), XP051036570, Retrieved from the Internet: URL:http://www.3gpp.org/ftp/tsg_sa/WG4_COD EC/Ad-hoc_MBS/Docs_AHI/ [retrieved on 2015-10-08]
  • MBS SWG CHAIRMAN: "Report for MBS SWG ad-hoc #50 conference call on MBMS Extensions and Profiling (MEPRO) - TRAPO - 8th October 2015", 3GPP DRAFT; S4-151254 MBS SWG AH50 REPORT, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE , vol. SA WG4, no. San Jose Del Cabo, Mexico; 20151026 - 20151030 22 October 2015 (2015-10-22), XP051015526, Retrieved from the Internet: URL:http://www.3gpp.org/ftp/Meetings_3GPP_ SYNC/SA4/Docs/ [retrieved on 2015-10-22]
  • DAVID SINGER ET AL: "Proposed MBMS URL Forms", 3GPP DRAFT; S4-AHI530_MCAST_URL, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE , vol. SA WG4 7 October 2015 (2015-10-07), XP051036569, Retrieved from the Internet: URL:http://www.3gpp.org/ftp/tsg_sa/WG4_COD EC/Ad-hoc_MBS/Docs_AHI/ [retrieved on 2015-10-07]
  • SINGER APPLE D ET AL: "URLs and HTTP Response Forms for Multicast; draft-singer-appsawg-mcast-url-00.txt", URLS AND HTTP RESPONSE FORMS FOR MULTICAST; DRAFT-SINGER-APPSAWG-MCAST-URL-00.TXT, INTERNET ENGINEERING TASK FORCE, IETF; STANDARDWORKINGDRAFT, INTERNET SOCIETY (ISOC) 4, RUE DES FALAISES CH- 1205 GENEVA, SWITZERLAND, 16 October 2014 (2014-10-16), pages 1-12, XP015102215,
  • SAMSUNG ELECTRONICS LTD. ET AL.: 'Permanent Document: Use cases and design considerations and alternatives' 3GPP TSG SA WG4 MEETING #83, BRATISLAVA 16 April 2015, pages 4 - 150496, XP050964075
  • DAVID SINGER ET AL.: 'On the MBMS URL Form' 3GPP TSG SA4 #85 MEETING 18 August 2015, KOBE, JAPAN, pages 4 - 150937, XP051122439
  • SAMSUNG ELECTRONICS CO., LTD.: 'Proposals for MBMS Extensions and Profiling' S4-150408, 3GPP TSG-SA4 MEETING #83 08 April 2015, BRATISLAVA, SK, XP050963939
  
Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention).


Description

Technical Field



[0001] This disclosure relates generally to wireless data transmission. More specifically, this disclosure relates to a method and apparatus for address resolution of multicast and/or broadcast resources using a domain name system (DNS).

Background Art



[0002] Recently, applications executed by client devices in mobile wireless networks have substantially increased the data traffic through the mobile networks. These types of applications can require relatively large amounts of data to be transmitted to or from a client device, such as video data. By increasing the data traffic, these applications can affect mobile operators and the dimensioning of core networks. As the mobile data traffic increases, new challenges can arise, and important network trade-offs may be required. A Multimedia Broadcast/Multicast System (MBMS) may be used to broadcast data to multiple users to reduce the amount of data traffic through the network since the broadcast channel can be received by multiple client devices (rather than requiring transmissions of the same content of each individual client device). Relevant prior art is disclosed by :

"Resource Addressing in MBMS with DNS Support",3GPP DRAFT; S4-51353_DNS_RESOLUTION;

"Permanent Document: Use cases and design considerations and alternatives",3GPP TSG SA WG4 MEETING #83, BRATISLAVA, 16 April 2015;

"Proposals for MBMS Extensions and Profiling" ,S4-150408


Disclosure of Invention


Technical Problem



[0003] This disclosure provides a method and apparatus for address resolution of multicast/broadcast resources using domain name systems.

Solution to Problem



[0004] In a first embodiment, a user equipment (UE) configured to receive a resource over a multimedia broadcast multicast service (MBMS) is provided according to claim 1).

[0005] In a second embodiment, a method for resolving an address in a user equipment (UE) is provided according to claim.

[0006] In an example, a domain name server (DNS) includes a communication unit and a processor. The communications unit is configured to receive at least one DNS query from a user equipment (UE) The processor is configured to calculate a DNS query frequency. The communications unit is also configured to transmit the DNQ query frequency for a domain name to a multicast server.

[0007] Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims.

[0008] Before undertaking the Best Mode below, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document. The term "couple" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with one another. The terms "transmit," "receive," and "communicate," as well as derivatives thereof, encompass both direct and indirect communication. The terms "include" and "comprise," as well as derivatives thereof, mean inclusion without limitation. The term "or" is inclusive, meaning and/or. The phrase "associated with," as well as derivatives thereof, means to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, have a relationship to or with, or the like. The term "controller" means any device, system or part thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and/or firmware. The functionality associated with any particular controller may be centralized or distributed, whether locally or remotely. The phrase "at least one of," when used with a list of items, means that different combinations of one or more of the listed items may be used, and only one item in the list may be needed. For example, "at least one of: A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.

[0009] Moreover, various functions described below can be implemented or supported by one or more computer programs, each of which is formed from computer readable program code and embodied in a computer readable medium. The terms "application" and "program" refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof adapted for implementation in a suitable computer readable program code. The phrase "computer readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer readable medium" includes any type of medium capable of being accessed by a computer, such as read only memory (ROM), random access memory (RAM), a hard disk drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory. A "non-transitory" computer readable medium excludes wired, wireless, optical, or other communication links that transport transitory electrical or other signals. A non-transitory computer readable medium includes media where data can be permanently stored and media where data can be stored and later overwritten, such as a rewritable optical disc or an erasable memory device.

[0010] Definitions for other certain words and phrases are provided throughout this patent document. Those of ordinary skill in the art should understand that in many if not most instances, such definitions apply to prior as well as future uses of such defined words and phrases.

Advantageous Effects of Invention



[0011] Various examples provide method for address resolution of multicast/broadcast resources using domain name systems.

Brief Description of Drawings



[0012] For a more complete understanding of this disclosure, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

FIGURE 1 illustrates an example computing system according to this disclosure;

FIGURES 2 and 3 illustrate example devices in a computing system according to this disclosure;

FIGURE 4 illustrates example signaling for address resolution of unicast and/or multicast resources using a DNS according to the disclosure;

FIGURE 5 illustrates an example method for address resolution of multicast and/or unicast resources according to this disclosure.


Best Mode for Carrying out the Invention



[0013] FIGURES 1 through 5, discussed below, and the various embodiments used to describe the principles of the present invention in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of this disclosure may be implemented in any suitably arranged device or system.

[0014] FIGURE 1 illustrates an example computing system 100 according to this disclosure. The embodiment of the computing system 100 shown in FIGURE 1 is for illustration only. Other embodiments of the computing system 100 could be used without departing from the scope of this disclosure.

[0015] As shown in FIGURE 1, the system 100 includes a network 102, which facilitates communication between various components in the system 100. For example, the network 102 may communicate Internet Protocol (IP) packets, frame relay frames, Asynchronous Transfer Mode (ATM) cells, or other information between network addresses. The network 102 may include one or more local area networks (LANs), metropolitan area networks (MANs), wide area networks (WANs), all or a portion of a global network such as the Internet, or any other communication system or systems at one or more locations.

[0016] The network 102 facilitates communications between at least one server 104 or at least one server 105 and various client devices 106-114. Each server 104, 105 includes any suitable computing or processing device that can provide computing services for one or more client devices. Each server 104, 105 could, for example, include one or more processing devices, one or more memories storing instructions and data, and one or more network interfaces facilitating communication over the network 102. Server 104 may represent a media server or domain name server (DNS) and server 105 may represent a broadcast multicast service center (BM-SC)

[0017] Each client device 106-114 represents any suitable computing or processing device that interacts with at least one server or other computing device(s) over the network 102. In this example, the client devices 106-114 include a desktop computer 106, a mobile telephone or smartphone 108, a personal digital assistant (PDA) 110, a laptop computer 112, and a tablet computer 114. However, any other or additional client devices could be used in the computing system 100.

[0018] In this example, some client devices 108-114 communicate indirectly with the network 102. For example, the client devices 108-110 communicate via one or more base stations 116, such as cellular base stations or eNodeBs. Also, the client devices 112-114 communicate via one or more wireless access points 118, such as IEEE 802.11 wireless access points. Note that these are for illustration only and that each client device could communicate directly with the network 102 or indirectly with the network 102 via any suitable intermediate device(s) or network(s).

[0019] As described in more detail below, the client devices 106-114 may be used to access content on the server 104 via a unicast broadcast or access content on the BM-SC via a multicast broadcast.

[0020] Although FIGURE 1 illustrates one example of a computing system 100, various changes may be made to FIGURE 1. For example, the system 100 could include any number of each component in any suitable arrangement. In general, computing and communication systems come in a wide variety of configurations, and FIGURE 1 does not limit the scope of this disclosure to any particular configuration. While FIGURE 1 illustrates one operational environment in which various features disclosed in this patent document can be used, these features could be used in any other suitable system.

[0021] FIGURES 2 and 3 illustrate example devices in a computing system according to this disclosure. In particular, FIGURE 2 illustrates an example server 200, and FIGURE 3 illustrates an example client device 300. The server 200 could represent the server 104 or server 105 in FIGURE 1, and the client device 300 could represent one or more of the client devices 106-114 in FIGURE 1.

[0022] As shown in FIGURE 2, the server 200 includes a bus system 205, which supports communication between at least one processing device 210, at least one storage device 215, at least one communications unit 220, and at least one input/output (I/O) unit 225.

[0023] The processing device 210 executes instructions that may be loaded into a memory 230. The processing device 210 may include any suitable number(s) and type(s) of processors or other devices in any suitable arrangement. Example types of processing devices 210 include microprocessors, microcontrollers, digital signal processors, field programmable gate arrays, application specific integrated circuits, and discreet circuitry.

[0024] The memory 230 and a persistent storage 235 are examples of storage devices 215, which represent any structure(s) capable of storing and facilitating retrieval of information (such as data, program code, and/or other suitable information on a temporary or permanent basis). The memory 230 may represent a random access memory or any other suitable volatile or non-volatile storage device(s). The persistent storage 235 may contain one or more components or devices supporting longer-term storage of data, such as a ready only memory, hard drive, Flash memory, or optical disc.

[0025] The communications unit 220 supports communications with other systems or devices. For example, the communications unit 220 could include a network interface card or a wireless transceiver facilitating communications over the network 102. The communications unit 220 may support communications through any suitable physical or wireless communication link(s).

[0026] The I/O unit 225 allows for input and output of data. For example, the I/O unit 225 may provide a connection for user input through a keyboard, mouse, keypad, touchscreen, or other suitable input device. The I/O unit 225 may also send output to a display, printer, or other suitable output device.

[0027] Note that while FIGURE 2 is described as representing the server 104 or server 105 of FIGURE 1, the same or similar structure could be used in one or more of the client devices 106-114. For example, a laptop or desktop computer could have the same or similar structure as that shown in FIGURE 2.

[0028] In an example not being part of the invention server 105 may represent a DNS server. The server 105 registers resource records (RR) for the multimedia broadcast multicast services (MBMS) resources. The server 105 uses DNS resolution requests to assess interest in a resource and changes the DNS records based on a popularity of the resource to point to a unicast or multicast broadcast. The server 105 also calculates the DNS resolution request frequency for specific domain names and reports the DNS resolution request frequency to a BM-SC such as server 104. Specifically, the communication unit 220 may receive one or more DNS resolution requests for a specific domain name and the processing device 210 may calculate the frequency of DNS resolution requests for the specific domain name.

[0029] As shown in FIGURE 3, the client device 300 includes an antenna 305, a radio frequency (RF) transceiver 310, transmit (TX) processing circuitry 315, a microphone 320, and receive (RX) processing circuitry 325. The client device 300 also includes a speaker 330, a processor 340, an input/output (I/O) interface (IF) 345, an input 350, a display 355, and a memory 360. The memory 360 includes a operating system (OS) program 361 and one or more applications 362.

[0030] The RF transceiver 310 receives, from the antenna 305, an incoming RF signal transmitted by another component in a system. The RF transceiver 310 down-converts the incoming RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is sent to the RX processing circuitry 325, which generates a processed baseband signal by filtering, decoding, and/or digitizing the baseband or IF signal. The RX processing circuitry 325 transmits the processed baseband signal to the speaker 330 (such as for voice data) or to the processor 340 for further processing (such as for web browsing data).

[0031] The TX processing circuitry 315 receives analog or digital voice data from the microphone 320 or other outgoing baseband data (such as web data, e-mail, or interactive video game data) from the processor 340. The TX processing circuitry 315 encodes, multiplexes, and/or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The RF transceiver 310 receives the outgoing processed baseband or IF signal from the TX processing circuitry 315 and up-converts the baseband or IF signal to an RF signal that is transmitted via the antenna 305.

[0032] The processor 340 can include one or more processors or other processing devices and execute the OS program 361 stored in the memory 360 in order to control the overall operation of the client device 300. For example, the processor 340 could control the reception of forward channel signals and the transmission of reverse channel signals by the RF transceiver 310, the RX processing circuitry 325, and the TX processing circuitry 315 in accordance with well-known principles. In some embodiments, the processor 340 includes at least one microprocessor or microcontroller.

[0033] The processor 340 is also capable of executing other processes and programs resident in the memory 360. The processor 340 can move data into or out of the memory 360 as required by an executing process. In some embodiments, the processor 340 is configured to execute the applications 362 based on the OS program 361 or in response to signals received from external devices or an operator. The processor 340 is also coupled to the I/O interface 345, which provides the client device 300 with the ability to connect to other devices such as laptop computers and handheld computers. The I/O interface 345 is the communication path between these accessories and the processor 340.

[0034] The processor 340 is also coupled to the input 350 and the display unit 355. The operator of the client device 300 can use the input 350 to enter data into the client device 300. For example, the input 350 may be a touchscreen, button, and/or keypad. The display 355 may be a liquid crystal display or other display capable of rendering text and/or at least limited graphics, such as from web sites.

[0035] The memory 360 is coupled to the processor 340. Part of the memory 360 could include a random access memory (RAM), and another part of the memory 360 could include a Flash memory or other read-only memory (ROM).

[0036] As described in more detail below, the client device 300 may receive resources via a unicast or multicast broadcast system.

[0037] Although FIGURES 2 and 3 illustrate examples of devices in a computing system, various changes may be made to FIGURES 2 and 3. For example, various components in FIGURES 2 and 3 could be combined, further subdivided, or omitted and additional components could be added according to particular needs. As a particular example, the processor 340 could be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Also, while FIGURE 3 illustrates the client device 300 configured as a mobile telephone or smartphone, client devices could be configured to operate as other types of mobile or stationary devices. In addition, as with computing and communication networks, client devices and servers can come in a wide variety of configurations, and FIGURES 2 and 3 do not limit this disclosure to any particular client device or server.

[0038] FIGURE 4 illustrates an embodiment for signaling for address resolution of unicast and/or multicast resources using a DNS according to the disclosure. As shown in FIGURE 4 signals are transmitted and received between a client device 400, a DNS 402, and a broadcast multicast service center (BM-SC) 404. The client device may represent the client device 300 of FIGURE 3 and the DNS 402 and BM-SC 404 may be represented by the server 200 of FIGURE 2.

[0039] A user enters a MBMS uniform resource identifier (URI) in the client device 400. The MBMS URI scheme shall comply with the guidelines specified by the Internet Engineering Task Force (IETF). The MBMS URL scheme shall support both resources delivered over hypertext transfer protocol (HTTP) as well as real time streaming protocol (RTSP)/ real time transport protocol (RTP) streaming sessions. The MBMS URI handling shall support fallback to unicast delivery if the requested resource is not available over MBMS. The MBMS URI handling shall support MooD by resolving automatically to either a unicast or multicast location. The MBMS URI may have the following syntax:

scheme = mbms-scheme "://" host [": " port] "/" path

mbms-scheme = "mbms-http" | "mbms-https" | "mbms-rtsp"



[0040] As can be seen in the MBMS URI, the MBMS URI includes a unicast fallback which may be determined by removing the "mbms-"prefix from the MBMS URI. In process 406, the client device 400 detects the MBMS URI and passes the MBMS URI to an MBMS protocol handler which may be implemented by processor 340 of client device 300. The MBMS protocol handler transmits the request to the DNS 402 to resolve the domain in process 408.

[0041] In process 410, if no resources for the specified domain are being served over multicast, then the response provided to the client device 400 from DNS 402 only contains an A RR that points to the unicast address that resolves for the fully qualified domain name (FQDN) of the corresponding unicast URI. If the resource is available over multicast, the DNS 402 provides an SRV RR, an A RR, and a TXT RR to the client device 400. The SRV RR indicates a multicast Internet Protocol (IP) address, a port number, a Temporary Mobile Group Identity (TMGI) and a File Delivery over Unidirectional Transport protocol (FLUTE) session transport session identifier (TSI). THE SRV RR follows the format:
_mbms._UDP.Request_FQDN TTL IN SRV Priority WeightPort TMGI.BMSC DN.
where the weight field shall contain the TSI of the FLUTE session, the Port field shall include the destination port number, the target shall contain the TMGI of the session that is used to deliver the resources from the request FQDN and the BMSC_DN provides the domain name of the BM-SC that is serving the content over MBMS. The A RR provides a multicast address and follows the format:
owner-name ttl class rr ipv4

[0042] The TXT RR provides additional information or parameters such as an alternative TMGI, a frequency on which the MBMS bearer is to be accessed, a service area on which the service is available, an availability start which provides a start time after which the MBMS broadcast will be available for access, an availability end which provides the end time after which the MBMS broadcast cannot be accessed. One example of TXT RR may follow the following format:
_mbms. additional.FQDN. 14400 IN TXT "alternative_tmgi=98723987\; frequency=987234987\; service_area=987r8eq9w70\; "

[0043] In process 412, if the resource is available over a multicast broadcast, the client device 400 joins the MBMS session. The client device determines whether ther resource is available over a multicast broadcast based on the RRs received from the DNS 402. In process 414, the resource is received over MBMS from the BM-SC 404.

[0044] FIGURE 5 illustrates an example method 500 for address resolution of multicast and/or unicast resources according to this disclosure. For ease of explanation, FIGURE 5 will be discussed in conjunction with client device 300 of FIGURE 3 and the signaling of FIGURE 4.

[0045] As shown in FIGURE 5, upon receiving the response to the DNS query on the MBMS URL FQDN from the DNS 402, the MBMS scheme handler, which may be implemented by processor 340, performs the method 500. The method 500 begins in step 502, where the MBMS scheme handler determines whether the DNS query response includes only an A record that points to a unicast address. If the DNS query response only includes an A record, the MBMS scheme handler determines that the resource is not served by MBMS and the method 500 proceeds to step 504 which retrieves the requested resource using HTTP/HTTPS and the resolved unicast address. If the DNS query response does not include only an A RR, the method 500 proceeds to step 506 where a determination is made as to whether an SRV RR and a TXT RR that provide a service-id NVP, has been received from the DNS 402. If the SRV RR and TXT RR have not been received, the method 500 returns to step 504. If the SRV RR and the TXT RR have been received, the method 500 proceeds to step 508, where MBMS protocol handler checks local cache for RRs with the MBMS URI or the corresponding unicast URI and if found returns the RR to the application in step 510.

[0046] If the RR is not located in the local cache, the MBMS protocol handler checks its cached USDs and Schedule Description Metadata fragments for the occurrence of the URI as part of a fileSchedule or an appService in step 512. If found, the MBMS protocol handler checks for the scheduled time of delivery of the resource/stream and if acceptable for the application, the MBMS protocol handler schedules reception of the resource over the multicast broadcast in step 514. If the requested resource is described in one of the existing USDs but the distribution time does not fulfil the requirements of the application or the RR is not found, then unicast retrieval (potentially through a MooD proxy) is attempted in step 516.

[0047] None of the description in this application should be read as implying that any particular element, step, or function is an essential element that must be included in the claim scope. The scope of patented subject matter is defined only by the claims. Use of any other term, including without limitation "mechanism," "module," "device," "unit," "component," "element," "member," "apparatus," "machine," "system," "processor," or "controller," within a claim is understood by the applicants to refer to structures known to those skilled in the relevant art.


Claims

1. A user equipment, UE, configured to receive a resource over a multimedia broadcast multicast service, MBMS, the UE comprising:

a transceiver; and

a processor configured to:

detect (406) a multimedia broadcast multicast service uniform resource identifier, MBMS URI;

transmit (408) a domain name server, DNS, query to a DNS based on the MBMS URI;

receive a response including an A resource record, a SRV resource record, and a TXT resource record from the DNS or including the A resource record, wherein the SRV resource record indicates a multicast internet protocol, IP, address, a port number, a Temporary Mobile Group Identity, TMGI, and a File Delivery over Unidirectional Transport protocol, FLUTE, session transport session identifier, TSI;

determine that a resource is available over unicast when the response includes only the A resource record;

determine that the resource is available over multicast when the response includes the A resource record, the SRV resource record, and the TXT resource record;

join (412), if the resource is available over multicast, an MBMS session; and

receive (414) the resource over MBMS from a broadcast multicast service center, BM-SC.


 
2. The UE of Claim 1, wherein the transceiver is configured to receive resources via a unicast or a multicast broadcast based on the determining of at least one of a unicast location or a multicast location.
 
3. The UE of Claim 1, wherein the MBMS URI has a syntax:

scheme = mbms-scheme "://" host [":" port] "/" path

mbms-scheme = "mbms-http" | "mbms-https" | "mbms-rtsp".


 
4. The UE of Claim 1, wherein the SRV resource record has a syntax:
mbms._UDP.Request FQDN TTL IN SRV Priority Weight Port TMGI.BMSC_DN.
where the weight includes a transport session identifier, TSI, of a file delivery over unidirectional transport protocol, FLUTE, session, the port includes a destination port number, a target includes the temporary mobile group identity, TMGI, of the session that is used to deliver resources from a fully qualified domain name, FQDM, and the BMSC_DN provides the domain name of a broadcast multicast service center, BM-SC, that is serving the resource over MBMS.
 
5. A method for resolving an address in a user equipment, UE, the method comprising:

detecting (406) a multimedia broadcast multicast service uniform resource identifier, MBMS URI;

transmitting (408) a domain name server, DNS, query to a DNS based on the MBMS URI;

receiving a response including an A resource record, a SRV resource record, and a TXT resource record from the DNS or including the A resource record, wherein the SRV resource record indicates a multicast internet protocol, IP, address, a port number, a Temporary Mobile Group Identity, TMGI, and a File Delivery over Unidirectional Transport protocol, FLUTE, session transport session identifier, TSI;

determining that a resource is available over unicast when the response includes only the A resource record; and

determining that the resource is available over multicast when the response includes the A resource record, the SRV resource record, and the TXT resource record;

joining (412), if the resource is available over multicast, an MBMS session; and

receiving (414) the resource over MBMS from a broadcast multicast service center, BM-SC.


 
6. The method of Claim 5, the method further comprising:
receiving resources via a unicast or a multicast broadcast based on the determining of at least one of a unicast location or a multicast location.
 
7. The method of Claim 5, wherein the MBMS URI has a syntax:

scheme = mbms-scheme "://" host [":" port] "/" path

mbms-scheme = "mbms-http" | "mbms-https" | "mbms-rtsp".


 
8. The method of Claim 5, wherein the SRV resource record has a syntax:
mbms._UDP.Request_FQDN TTL IN SRV Priority Weight Port IMGI.BMSC_DN.
where the weight includes a transport session identifier, TSI, of a file delivery over unidirectional transport protocol, FLUTE, session, the port includes a destination port number, a target includes the temporary mobile group identity, TMGI, of the session that is used to deliver resources from a fully qualified domain name, FQDM, and the BMSC_DN provides the domain name of a broadcast multicast service center, BM-SC, that is serving the resource over MBMS.
 


Ansprüche

1. Benutzergerät, UE, das konfiguriert ist, um eine Ressource über einen Multimedia-Broadcast-Multicast-Service, MBMS, zu empfangen, wobei das UE Folgendes umfasst:

einen Transceiver; und

einen Prozessor, der konfiguriert ist zum:

Erkennen (406) eines einheitlichen Multimedia-Broadcast-Multicast-Service-Ressourcenidentifiers, MBMS-URI;

Übertragen (408) einer Domänennamenserver(DNS)-Anfrage an einen DNS basierend auf dem MBMS-URI;

Empfangen einer Antwort einschließlich eines A-Ressourcendatensatzes, eines SRV-Ressourcendatensatzes und eines TXT-Ressourcendatensatzes von dem DNS oder einschließlich des A-Ressourcendatensatzes, wobei der SRV-Ressourcendatensatz eine Multicast-lnternetprotokoll(IP)-Adresse, eine Portnummer, eine temporäre mobile Gruppenidentität, TMGI, und eine Dateilieferung über unidirektionalen Transportprotokoll(FLUTE)-Sitzungs-Transportsitzungsidentifier, TSI, anzeigt;

Bestimmen, dass eine Ressource über Unicast verfügbar ist, wenn die Antwort nur den A-Ressourcendatensatz einschließt;

Bestimmen, dass die Ressource über Multicast verfügbar ist, wenn die Antwort den A-Ressourcendatensatz, den SRV-Ressourcendatensatz und den TXT-Ressourcendatensatz einschließt;

Teilnehmen (412) an einer MBMS-Sitzung, wenn die Ressource über Multicast verfügbar ist;
und

Empfangen (414) der Ressource über den MBMS von einem Broadcast-Multicast-Service-Center, BM-SC.


 
2. UE nach Anspruch 1, wobei der Transceiver konfiguriert ist, um Ressourcen über einen Unicast- oder einen Multicast-Broadcast zu empfangen, basierend auf dem Bestimmen eines Unicast-Standorts und/oder eines Multicast-Standorts.
 
3. UE nach Anspruch 1, wobei der MBMS-URI eine Syntax hat:

scheme = mbms-scheme "://" host [":" port] "/" path

mbms-scheme = "mbms-http" \ "mbms-https" \ "mbms-rtsp".


 
4. UE nach Anspruch 1, wobei der SRV-Ressourcendatensatz eine Syntax hat:
mbms._UDP.Request_FQDN TTL IN SRV Priority Weight Port TMGI.BMSC_DN.
in der das Gewicht einen Transportsitzungsidentifier, TSI, einer Dateilieferung über eine unidirektionale Transportprotokoll(FLUTE)-Sitzung einschließt, der Port eine Zielportnummer einschließt, ein Ziel die temporäre mobile Gruppenidentität, TMGI, der Sitzung einschließt, die benutzt wird, um Ressourcen von einem vollqualifizierten Domänennamen, FQDM, zu liefern, und der BMSC-DN den Domänennamen eines Broadcast-Multicast-Service-Centers, BM-SC, bereitstellt, das die Ressource über einen MBMS bedient.
 
5. Verfahren zum Auflösen einer Adresse in einem Benutzergerät, UE, wobei das Verfahren Folgendes umfasst:

Erkennen (406) eines einheitlichen Multimedia-Broadcast-Multicast-Service-Ressourcenidentifiers, MBMS-URI;

Übertragen (408) einer Domänennamenserver(DNS)-Anfrage an einen DNS basierend auf dem MBMS-URI;

Empfangen einer Antwort einschließlich eines A-Ressourcendatensatzes, eines SRV-Ressourcendatensatzes und eines TXT-Ressourcendatensatzes von dem DNS oder einschließlich des A-Ressourcendatensatzes, wobei der SRV-Ressourcendatensatz eine Multicast-lnternetprotokoll(IP)-Adresse, eine Portnummer, eine temporäre mobile Gruppenidentität, TMGI, und eine Dateilieferung über unidirektionalen Transportprotokoll(FLUTE)-Sitzungs-Transportsitzungsidentifier(TSI), anzeigt;

Bestimmen, dass eine Ressource über Unicast verfügbar ist, wenn die Antwort nur den A-Ressourcendatensatz einschließt; und

Bestimmen, dass die Ressource über Multicast verfügbar ist, wenn die Antwort den A-Ressourcendatensatz, den SRV-Ressourcendatensatz und den TXT-Ressourcendatensatz einschließt;

Teilnehmen (412) an einer MBMS-Sitzung, wenn die Ressource über Multicast verfügbar ist; und

Empfangen (414) der Ressource über einen MBMS von einem Broadcast-Multicast-Service-Center, BM-SC.


 
6. Verfahren nach Anspruch 5, wobei das Verfahren des Weiteren Folgendes umfasst:
Empfangen von Ressourcen über einen Unicast- oder einen Multicast-Broadcast basierend auf dem Bestimmen eines Unicast-Standorts und/oder eines Multicast-Standorts.
 
7. Verfahren nach Anspruch 5, wobei der MBMS-URI eine Syntax hat:

scheme = mbms-scheme "://" host [":" port] "/" path

mbms-scheme = "mbms-http" \ "mbms-https" \ "mbms-rtsp".


 
8. Verfahren nach Anspruch 5, wobei der SRV-Ressourcendatensatz eine Syntax hat:
mbms._UDP.Reques_CFQDN TTL IN SRV Priority Weight Port TMGI_BMSC_DN.
in der das Gewicht einen Transportsitzungsidentifier, TSI, einer Dateilieferung über eine unidirektionale Transportprotokoll(FLUTE)-Sitzung einschließt, der Port eine Zielportnummer einschließt, ein Ziel die temporäre mobile Gruppenidentität, TMGI, der Sitzung einschließt, die benutzt wird, um Ressourcen von einem vollqualifizierten Domänennamen, FQDM, zu liefern, und der BMSC-DN den Domänennamen eines Broadcast-Multicast-Service-Centers, BM-SC, bereitstellt, der die Ressource über einen MBMS bedient.
 


Revendications

1. Équipement utilisateur, UE, configuré pour recevoir une ressource sur un service de diffusion/multidiffusion multimédia, MBMS, l'UE comprenant :

un émetteur-récepteur ; et

un processeur configuré pour :

détecter (406) un identificateur de ressource uniforme de service de diffusion/multidiffusion multimédia, MBMS URI ;

transmettre (408) une interrogation de serveur de noms de domaine, DNS, à un DNS sur la base du MBMS URI ;

recevoir une réponse comprenant un enregistrement de ressource A, un enregistrement de ressource SRV et un enregistrement de ressource TXT depuis le DNS ou comprenant l'enregistrement de ressource A, où l'enregistrement de ressource SRV indique une adresse de Protocole Internet, IP, de multidiffusion, un numéro de port, une identité de groupe mobile temporaire, TMGI, et un identifiant de session de transport, TSI, d'une session de protocole de remise de fichiers sur transport unidirectionnel, FLUTE ;

déterminer qu'une ressource est disponible sur monodiffusion lorsque la réponse comprend uniquement l'enregistrement de ressource A ;

déterminer que la ressource est disponible sur multidiffusion lorsque la réponse comprend l'enregistrement de ressource A, l'enregistrement de ressource SRV et l'enregistrement de ressource TXT ;

rejoindre (412), si la ressource est disponible par multidiffusion, une session MBMS ; et

recevoir (414) la ressource sur MBMS à partir d'un centre de service de diffusion/multidiffusion, BM-SC.


 
2. UE selon la revendication 1, où l'émetteur-récepteur est configuré pour recevoir des ressources via une diffusion monodiffusion ou multidiffusion sur la base de la détermination d'au moins l'un parmi un emplacement monodiffusion ou un emplacement multidiffusion.
 
3. UE selon la revendication 1, où le MBMS URI a une syntaxe :

Scheme = mbms-scheme "://" host [":" port] "/" path

mbms-scheme = "mbms-http" | "mbms-https" | "mbms-rtsp".


 
4. UE selon la revendication 1, où l'enregistrement de ressource SRV a une syntaxe : mbms._UDP.Request_FQDN TTL IN SRV Priority Weight Port TMGI.BMSC_DN
où le poids (weight) comprend un identifiant de session de transport, TSI, d'une session de protocole de remise de fichiers sur transport unidirectionnel, FLUTE, le port comprend un numéro de port de destination, une cible comprend l'identité de groupe mobile temporaire, TMGI, de la session qui est utilisée pour fournir des ressources à partir d'un nom de domaine complet, FQDM, et le BMSC_DN fournit le nom de domaine d'un centre de service de diffusion/multidiffusion, BM-SC, qui dessert la ressource sur MBMS.
 
5. Procédé pour résoudre une adresse dans un équipement utilisateur, UE, le procédé comprenant :

détecter (406) un identificateur de ressource uniforme de service de diffusion/multidiffusion multimédia, MBMS URI ;

transmettre (408) une interrogation de serveur de noms de domaine, DNS, à un DNS sur la base du MBMS URI ;

recevoir une réponse comprenant un enregistrement de ressource A, un enregistrement de ressource SRV et un enregistrement de ressource TXT depuis le DNS ou comprenant l'enregistrement de ressource A, où l'enregistrement de ressource SRV indique une adresse de Protocole Internet, IP, de multidiffusion, un numéro de port, une identité de groupe mobile temporaire, TMGI, et un identifiant de session de transport, TSI, d'une session de protocole de remise de fichiers sur transport unidirectionnel, FLUTE ;

déterminer qu'une ressource est disponible sur monodiffusion lorsque la réponse comprend uniquement l'enregistrement de ressource A ;

déterminer que la ressource est disponible sur multidiffusion lorsque la réponse comprend l'enregistrement de ressource A, l'enregistrement de ressource SRV et l'enregistrement de ressource TXT ;

rejoindre (412), si la ressource est disponible par multidiffusion, une session MBMS ; et

recevoir (414) la ressource sur MBMS à partir d'un centre de service de diffusion/multidiffusion, BM-SC.


 
6. Procédé selon la revendication 5, le procédé comprenant en outre :
recevoir des ressources via une diffusion monodiffusion ou multidiffusion sur la base de la détermination d'au moins l'un parmi un emplacement monodiffusion ou un emplacement multidiffusion.
 
7. Procédé selon la revendication 5, où le MBMS URI a une syntaxe :

Scheme = mbms-scheme "://" host [":" port] "/" path

mbms-scheme = "mbms-http" | "mbms-https" | "mbms-rtsp".


 
8. Procédé selon la revendication 5, où l'enregistrement de ressource SRV a une syntaxe :
mbms._UDP.Request_FQDN TTL IN SRV Priority Weight Port TMGI.BMSC_DN
où le poids (weight) comprend un identifiant de session de transport, TSI, d'une session de protocole de remise de fichiers sur transport unidirectionnel, FLUTE, le port comprend un numéro de port de destination, une cible comprend l'identité de groupe mobile temporaire, TMGI, de la session qui est utilisée pour fournir des ressources à partir d'un nom de domaine complet, FQDM, et le BMSC_DN fournit le nom de domaine d'un centre de service de diffusion/multidiffusion, BM-SC, qui dessert la ressource sur MBMS.
 




Drawing

















Cited references

REFERENCES CITED IN THE DESCRIPTION



This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.

Non-patent literature cited in the description