WO2010012165A1 - Procédé, équipement et système servant à recevoir l'alerte d’un événement d’urgence - Google Patents

Procédé, équipement et système servant à recevoir l'alerte d’un événement d’urgence Download PDF

Info

Publication number
WO2010012165A1
WO2010012165A1 PCT/CN2009/071245 CN2009071245W WO2010012165A1 WO 2010012165 A1 WO2010012165 A1 WO 2010012165A1 CN 2009071245 W CN2009071245 W CN 2009071245W WO 2010012165 A1 WO2010012165 A1 WO 2010012165A1
Authority
WO
WIPO (PCT)
Prior art keywords
emergency
emergency notification
message
notification
request
Prior art date
Application number
PCT/CN2009/071245
Other languages
English (en)
Chinese (zh)
Inventor
张德文
施有铸
张妮
毛凌志
张中宝
漆宝剑
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to US12/502,320 priority Critical patent/US8184002B2/en
Publication of WO2010012165A1 publication Critical patent/WO2010012165A1/fr

Links

Classifications

    • G—PHYSICS
    • G08—SIGNALLING
    • G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B27/00—Alarm systems in which the alarm condition is signalled from a central station to a plurality of substations
    • G08B27/005—Alarm systems in which the alarm condition is signalled from a central station to a plurality of substations with transmission via computer network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04H—BROADCAST COMMUNICATION
    • H04H20/00—Arrangements for broadcast or for distribution combined with broadcast
    • H04H20/53—Arrangements specially adapted for specific applications, e.g. for traffic information or for mobile receivers
    • H04H20/59—Arrangements specially adapted for specific applications, e.g. for traffic information or for mobile receivers for emergency or urgency

Definitions

  • the present invention relates to the field of communication applications, and in particular, to a method, apparatus and system for receiving an emergency notification. Background technique
  • the IP Multimedia Subsystem is a new form of multimedia service defined by the 3GPP (3rd Generation Partnership Project) standard. It can meet the needs of today's end customers.
  • the demand for diversified multimedia services is the target network for 3G (3rd Generation) mobile networks to implement packet voice and packet data, providing unified multimedia services and applications.
  • the IMS uses the IP packet domain as the bearer channel for its control signaling and media transmission, and uses the SIP (Session Initiation Protocol) protocol as the call control signaling to implement the service management, session control, and bearer access. Separation.
  • SIP Session Initiation Protocol
  • IPTV Internet Protocol Television
  • IPTV Internet Protocol Television
  • IPTV uses TCP/IP as the bearer protocol for unicast, broadcast or multicast video services, effectively combining the three fields of TV network, telephone network and Internet. It is the most representative service of triple play and is being received by the industry. More and more attention.
  • IMS-based IPTV provides IPTV services under the overall architecture of IMS to take full advantage of the existing registration, authentication, routing, session control and establishment, service triggering, charging, and end-to-end in the IMS network.
  • the QoS (Quality of Service) guarantee mechanism provides users with streaming media services and multimedia services that integrate streaming media and real-time session services.
  • EAS Emergency Alert System
  • Urgent news of life and property safety such as dew, tsunami warning, earthquake warning, turmoil, and war.
  • an appropriate mechanism is needed to timely issue an emergency notification to the end user, and the form of the emergency notification message includes text, audio, video, and the like.
  • the EAS service of the traditional TV transmits the emergency notification message by changing the content source, that is, the emergency notification message is transmitted by switching the content source on the network side, for example, the local television station pauses the playback of the current program content, and then inserts the broadcast.
  • the emergency notification message the user watching the channel can receive the emergency notification message.
  • the emergency notification message is not played on the channel that the user is watching, the user cannot get an emergency notification in time. For example, if a user is watching a television channel in a foreign country or even a television program in a foreign country, the local government department may not receive the emergency notification message issued by the local television channel.
  • the user terminal can not only watch live TV programs, but also on-demand (VODo on Demand, VOD) programs, or operate electronic program menus (EPC menu), play games, etc. It can even be a completely local operation, such as playing a locally stored program, or making a video call. In this way, those users who did not watch the live TV program at the time and were performing various other operations could not receive the emergency notification message.
  • VOD on-demand
  • EPC menu electronic program menu
  • Embodiments of the present invention provide a method, apparatus, and system for receiving an emergency notification. As long as the user terminal communicates with the bearer network normally, an emergency notification can be received at any time whether or not the live television program is being watched.
  • a method for receiving an emergency notification includes the following steps:
  • the receiving unit finds an emergency notification service
  • the receiving unit is attached to the emergency notification service
  • the receiving unit receives the emergency notification message sent by the distribution unit.
  • An emergency notification receiving unit device includes:
  • the service attachment processing module is configured to perform an emergency notification service attachment after the emergency notification service discovery is completed;
  • a message receiving processing module configured to receive an emergency notification message, and obtain an emergency notification indication from the emergency notification message;
  • the media stream receiving processing module is configured to receive an emergency event notification media stream, and forcibly switch to the presentation of the emergency event notification media stream according to the acquired emergency event notification indication.
  • An emergency notification service server device includes:
  • a publishing interface module configured to receive an emergency notification message, and obtain an emergency notification indication from the emergency notification message
  • a message distribution module configured to distribute an emergency notification message
  • the media flow control module is configured to control the media server MF to receive and distribute the emergency notification media stream according to the emergency notification notification.
  • An emergency call session control function device includes:
  • the emergency channel joins the identification module, configured to notify the emergency channel that the IPTV channel identifier carried in the session establishment request is an emergency channel identifier, or identify the emergency event notification session establishment request as an emergency channel by identifying an emergency indication carried in the session establishment request.
  • Request message configured to notify the emergency channel that the IPTV channel identifier carried in the session establishment request is an emergency channel identifier, or identify the emergency event notification session establishment request as an emergency channel by identifying an emergency indication carried in the session establishment request.
  • the emergency channel joining processing module is configured to, after identifying the emergency channel joining request message, request the policy enforcement entity of the bearer layer to reserve the bearer resource, and carry the reserved bearer resource according to the identified IPTV channel identifier or emergency indication. Priority.
  • a system for receiving emergency notifications including:
  • a distribution unit configured to send an emergency notification message to the receiving unit
  • the receiving unit is configured to discover an emergency notification service, and attach to the emergency notification service, and receive an emergency notification message sent by the distribution unit.
  • the embodiment of the invention further provides a method for discovering an emergency notification service, which is capable of discovering an emergency notification service by means of a third party registration.
  • the embodiment of the invention is implemented by the following technical solutions:
  • the receiving unit sends an IMS registration request to the call session control function CSCF;
  • the CSCF After processing the IMS registration request, the CSCF sends a third-party IMS registration request to the emergency notification system application server EAS AS;
  • the EAS AS After processing the third-party IMS registration request, the EAS AS sends an emergency notification service discovery message to the receiving unit.
  • the embodiment of the invention further provides a method for receiving an emergency event notification media stream, which can guarantee the network bandwidth resource required for transmitting the media stream.
  • the embodiments of the present invention can be implemented by the following technical solutions:
  • the network parameter includes multicast address information, the multicast address information is a dedicated specific multicast address, or Is an ordinary multicast address;
  • the multicast replication control point and the replication point ECF/EFF process the multicast group join request message, request the resource and the admission control subsystem RACS to reserve the bearer resource, and according to the identified multicast address or emergency indication, Carrying priority of reserved bearer resources;
  • Joining the multicast group receives an emergency notification media stream and plays the output.
  • the embodiment of the invention further provides a method for joining an emergency notification IPTV channel, which can implement forced switching of an emergency notification channel.
  • the embodiment of the invention is implemented by the following technical solutions:
  • the IPTV channel identifier is a specific channel identifier dedicated to the emergency notification media stream transmission, or an ordinary channel identifier;
  • the emergency call session control function E-CSCF processes the establishment request of the emergency notification session, requests the resource and the admission control subsystem RACS to reserve the bearer resource, and carries the pre-load according to the identified IPTV channel identifier or emergency indication.
  • the IPTV channel of the emergency notification is added.
  • the receiving unit finds the emergency notification service, by attaching to the emergency notification service, the emergency notification message sent by the distribution unit is received, so that the user terminal only needs to watch the live television program, as long as the user terminal and the bearer If the network communication is normal, the emergency notification can be received in time.
  • the terminal of the IMS network makes whatever program is enjoyed, such as watching an IPTV program or playing a game, or watching a program saved locally by the terminal, or performing a menu operation, regardless of what is being performed. Communication, such as making a video call, can receive an emergency notification in a timely manner.
  • the emergency notification service can be provided in the case of various service abnormalities, and the emergency notification service can be received as long as the user successfully registers with the IMS network; even the IMS network or the IMS network can be successfully registered in the user terminal. In the case of registration failure, roaming restriction, etc., as long as the communication between the terminal and the bearer network is normal, the emergency notification service can be received.
  • FIG. 1 is a schematic diagram of a network logical architecture applicable to an embodiment of the present invention
  • FIG. 2 is a flowchart of a method for receiving an emergency notification according to an embodiment of the present invention
  • FIG. 3 is a flowchart of a method for receiving an emergency event notification according to Embodiment 1 of the present invention
  • FIG. 4 is a flowchart of a method for receiving an emergency event notification according to Embodiment 2 of the present invention
  • Figure 6 is a flowchart of a method for receiving an emergency notification according to Embodiment 4 of the present invention
  • Figure 7 is a flowchart of a method for receiving an emergency notification according to Embodiment 5 of the present invention
  • FIG. 8 is a flowchart of a method for receiving an emergency event notification according to Embodiment 6 of the present invention
  • FIG. 9 is a flowchart of a method for receiving an emergency event notification media stream according to an embodiment of the present invention
  • FIG. 10 is a flow chart of a method for adding an emergency notification IPTV channel according to an embodiment of the present invention.
  • FIG. 11 is a flowchart of a method for discovering an emergency event notification service according to an embodiment of the present invention
  • FIG. 12 is a functional block diagram of an emergency event notification receiving unit device according to an embodiment of the present invention
  • FIG. 13 is a functional block diagram of an emergency notification service server device according to an embodiment of the present invention.
  • FIG. 14 is a functional block diagram of an emergency call session control function device according to an embodiment of the present invention. detailed description
  • FIG. 1 it is a schematic diagram of a network logical architecture applicable to an embodiment of the present invention. As shown in Figure 1, where:
  • the issuing unit 101 is configured to issue an emergency notification, and issue an emergency notification to the distribution unit 102 for the source of the emergency notification.
  • the issuing unit 101 is usually located in an emergency processing center of various government departments.
  • the issuing unit 101 is often a device outside the IMS network, and an interface exists with the IMS network, and the interface protocol is usually specified by the government department.
  • the E4 interface between the publishing unit 101 and the distribution unit 102 is a signaling interface for signaling interaction and control of emergency notification distribution, and transmission of emergency notification messages.
  • the issuing unit 101 requests the distribution unit 102 to issue an emergency notification
  • the distribution unit 102 authenticates the issuing unit 101.
  • the emergency notification message sent through the E4 interface carries an emergency notification indication (including the address of the emergency notification media stream), indicating how the recipient of the message obtains the media content of the emergency notification; and the text mode emergency can also be transmitted through the E4 interface.
  • the E4 interface protocol is defined by the government department and can be a proprietary protocol that can use S IP, HTTP protocol, other standard protocols or proprietary protocols.
  • the M2 interface between the publishing unit 101 and the distribution unit 102 is a media stream interface, which is used for transmitting Emergency notifications for audio and video transmission, such as audio and video media streams, or audio and video files, etc.
  • Interface protocols include but are not limited to: RTP/RTCP protocol, FTP protocol, HTTP protocol, other standard protocols or proprietary protocols.
  • the distribution unit 102 is configured to distribute the emergency notification to the receiving unit 103, and after receiving the emergency notification of the issuing unit 101, distribute the emergency notification to the receiving unit 103.
  • the distribution unit 102 not only performs the distribution of the emergency notification message at the signaling level, but also completes the delivery of the emergency notification at the media level, that is, the distribution of the emergency notification content of the audio and video media stream.
  • the distribution unit 102 can be located in the application server AS, or the media server MF, or the basic control point of the multicast replication in the multicast service and the copy point ECF/EFF (E lementa ry Cont ro l Func ti on / E The lementary forwarding ing is in a single entity; the distribution unit 102 can also be located in the above AS and ECF/EFF, or AS and MF and ECF/EFF and other entities.
  • the distribution unit 102 may also be not a certain entity or entities, but a network, that is, an emergency notification distribution network, in which some entities have direct interfaces with the issuing unit 101, and some entities and receiving units 103 There is a direct interface, and some entities have no direct interface with the publishing unit 101 or the receiving unit 103, and perform service distribution in the network.
  • an IMS Core including a P_CSCF, an S_CSCF, and an I-CSCF may serve as an emergency notification distribution network, route an emergency notification message, and finally distribute it to a user as the emergency notification receiving unit 103.
  • Terminal device UE The IMS Core completes the emergency notification notification distribution at the signaling level, and the IMS-controlled media network completes the media-level emergency event notification distribution.
  • the receiving unit 103 is configured to attach to the distribution unit 102 to receive the emergency notification distributed by the distribution unit 102, and perform processing and presentation of the emergency notification.
  • the receiving unit 103 can be located in the user equipment UE.
  • the E2 interface between the receiving unit 103 and the distribution unit 102 is a signaling interface, signaling interaction and control for emergency notification, and transmission of an emergency notification message, such as transmitting an emergency notification indication, transmitting a textual emergency. Notifications, etc.
  • Interface protocols include but are not limited to: proprietary protocols hosted over IP, SIP protocols, other standard protocols or proprietary protocols.
  • the M1 interface between the receiving unit 103 and the distribution unit 102 is a media stream interface, and is used for transmission of an emergency notification of audio and video modes, such as audio and video media streams, or audio and video files, etc.
  • Interface protocols include but are not limited to: RTP/ RTCP protocol, FTP protocol, HTTP protocol, other standard protocols or proprietary protocols.
  • the Ml interface may not be needed.
  • the content of the emergency notification message is text mode
  • the content of the text mode can be directly on the E2 interface. Transfer on.
  • the use of the M1 interface is often based on an emergency notification indication transmitted on the E2 interface, and the receiving unit 103 is configured to obtain an emergency notification of the audio and video mode from the M1 interface, and carry the relevant parameters of the M1 interface in the emergency notification indication, for example Address information, media format information, or IPTV channel identification for sending emergency notifications.
  • the receiving unit 103 receives the emergency notification content of the audio and video mode from the M1 interface according to the instruction, and plays the output.
  • the service discovery unit 104 is configured for the discovery of the emergency notification service, i.e., for acquiring the relevant information of the distribution unit 102, so that the receiving unit 103 can attach to the distribution unit 102 to receive the emergency notification.
  • the service discovery unit 104 may be located in the network attachment subsystem NASS, the gateway GPRS support node GGSN, the call session control function CSCF, or the application server AS, or the dynamic host configuration protocol DHCP server, or may be located in the user terminal device UE. .
  • the E1 interface between the service discovery unit 104 and the receiving unit 103 is a direct interface or an indirect interface for transmitting emergency notification service discovery information, for example, transmitting the address information of the distribution unit 102 to the receiving unit 103, and the interface protocol includes but is not limited to : DHCP protocol, D iame ter protocol, S IP protocol, other standard protocols or proprietary protocols.
  • the service discovery unit 104 and the receiving unit 103 may be located in the same physical entity, for example, in the user terminal device UE.
  • the E1 interface between the service discovery unit 104 and the receiving unit 103 is an internal interface.
  • the emergency notification message only includes an emergency notification message transmitted on the E2 interface, and the emergency notification message may carry an emergency notification message content that is convenient for carrying a small number of bytes in the message body, for example, a text mode emergency event. Notification message content.
  • the Ml interface is not used.
  • the emergency notification is divided into two parts, one part is the emergency notification message transmitted on the E2 interface, and the emergency notification indication is carried in the notification message; the other part is the emergency notification media stream transmitted on the M1 interface.
  • the emergency notification message transmitted on the E2 interface carries an emergency notification indication
  • the emergency notification indication carries the relevant parameter of the M1 interface, and is used to instruct the receiving unit 103 to obtain an audio-video emergency from the M1 interface. Notice.
  • FIG. 2 is a flow chart of a method for receiving an emergency notification according to an embodiment of the present invention, including:
  • Step 2 G1 the receiving unit finds an emergency notification service.
  • the receiving unit discovers the emergency notification service, that is, the receiving unit discovers the distribution unit, that is, the receiving unit acquires related information of the emergency notification distribution unit, including the distribution unit.
  • Related address information may also include some parameter information.
  • the emergency notification message is sent in a multicast manner, and the related information of the distribution unit to be acquired includes multicast address information used by the distribution unit to send an emergency notification, or indirect database server address information of the distribution unit.
  • the receiving unit receives the emergency notification message using the relevant information of the distribution unit.
  • the receiving unit first obtains the indirect information, and further obtains direct information of the distribution unit, for example, first obtaining the information of the database server address.
  • the multicast address information of the distribution unit is obtained from the database server.
  • the receiving unit discovers the distribution unit by: presetting the distribution unit related information on the receiving unit physical entity; or the receiving unit interacts with the service discovery unit to obtain related information of the distribution unit.
  • the former is a static discovery process, that is, a static data configuration acquisition process on the physical entity of the receiving unit
  • the latter is a dynamic discovery process, for example, during the network attachment process or after the network attachment is completed, or during the IMS registration process or the IMS registration is completed. After the dynamic discovery of the distribution unit.
  • the static discovery process is to statically set the relevant information of the distribution unit in advance on the receiving unit physical entity, for example, setting the multicast address information used by the distribution unit to send emergency notifications, or indirect database server address information.
  • This setting can be set by the user, or the terminal device can be preset before delivery to the user.
  • the multicast address transmitting the emergency notification message is a well-known multicast address specified by an industry standard, it can be preset in the terminal device.
  • the discovery unit and the receiving unit are located in the same physical entity, and the service discovery unit provides a setting for the user input interface or other input interface to receive the distribution unit information.
  • the E1 interface between the receiving unit and the service discovery unit is an internal interface in a physical entity, for example, a data query interface, and the receiving unit uses the internal interface to obtain information of the distribution unit, and completes the emergency event notification service discovery.
  • the dynamic discovery process is to exchange messages with the service discovery unit through the E1 interface during the startup process of the receiving unit to obtain information about the distribution unit.
  • the message interaction includes a PULL mode and a PUSH mode.
  • the PULL mode is that the receiving unit sends an emergency event notification service discovery request message to the service discovery unit through the E1 interface, and the service discovery unit sends an emergency event notification service discovery response message to the receiving unit through the E1 interface.
  • the message carries information about the distribution unit, such as a multicast address for sending an emergency notification message.
  • the service discovery unit sends an emergency notification service discovery indication message to the receiving unit through the E1 interface, where the message carries information about the distribution unit.
  • the service discovery unit In the IMS network, there are two situations in which the service discovery unit is located. One case is at the bearer layer, which is one entity or multiple entities in the bearer network, and the other is at the service layer, which is the IMS network session. One entity or multiple entities of a layer or application layer, which may also include entities that carry layers.
  • the receiving unit sends an emergency notification service discovery request message in two cases. In one case, the request is sent in the bearer network, for example, during the network attachment process or the network attachment is completed. The request is sent later, and the other case is to send the request in the service layer, for example, the request can be sent during the IMS registration process or after the IMS registration is completed.
  • the PULL mode service discovery process (which is further divided into the PULL mode service discovery process in the network attachment process and the PULL mode service discovery process after the network attachment is completed), and the PULL mode service discovery process at the IMS level ( Further, it is further divided into a PULL mode service discovery process in the IMS registration process and a PULL mode service discovery process after the IMS registration is completed.
  • the PULL mode service discovery process in the network attachment process refers to the process in which the receiving unit sends an emergency notification service discovery request, obtains the distribution unit information, completes the network attachment process, and completes the service discovery process.
  • the receiving unit sends a network attach request to the network, such as a dynamic host configuration protocol (DHCP, Dynami c Hos t Confive Protocol) request, which may be sent in a broadcast manner, and the network attaches a network attach request in the network.
  • DHCP dynamic host configuration protocol
  • An entity such as a DHCP server, receives the network attach request, and in addition to normally processing the network attach request, acquires information about the distribution unit, such as multicast address information for transmitting an emergency notification message, and transmits the network to the receiving unit.
  • the message of the attachment response carries the distribution unit information, so that the receiving unit completes the emergency notification service discovery while completing the network attachment.
  • the service discovery unit is located in the entity in the network that handles network attach requests, such as in a DHCP server.
  • the emergency notification service discovery request is located in the network attachment request message, and the emergency notification service discovery request may be an implicit request, that is, the network attachment request sent by the receiving unit does not explicitly carry the emergency notification service discovery request.
  • the entity that handles the network attach request additionally adds the processing of the emergency notification service discovery, and carries the emergency notification service discovery information in the network attachment response message.
  • the emergency notification service discovery request may also be an explicit request, that is, the emergency notification service discovery request indication is explicitly carried in the network attachment request message.
  • the PULL mode emergency notification service discovery in the network attachment process finds that the emergency event notification service discovery request is located in the network attachment request message, and the emergency notification service discovery response is located in the network attachment response message.
  • the PULL mode service discovery process after the network attachment is completed means that the receiving unit sends an emergency notification service discovery request after the network attachment is completed, and obtains an emergency notification service discovery information, and the emergency notification service discovery process is completed after the network attachment process.
  • the receiving unit sends an emergency notification service discovery request to the network, and the request may be sent by using a broadcast manner, and the entity (ie, the service discovery unit) that processes the emergency notification service discovery in the network processes the service discovery request. , reply to the emergency notification service discovery response message, The emergency notification service discovery information is carried in the interest.
  • the service discovery unit can be located in a separate entity from the entity to which the processing network is attached.
  • the PULL mode service discovery process in the IMS registration process means that the receiving unit sends an emergency notification service discovery request during the IMS registration process to obtain the relevant information of the distribution unit, and completes the IMS registration process and completes the service discovery process.
  • the general IMS registration process is: after receiving the P-CSCF address, the receiving unit sends an IMS registration request message (S IP Reg is ter message) to the P-CSCF, and the IMS registration request is routed to an allocated S-CSCF to perform IMS registration.
  • the S-CSCF replies to the receiving unit with an IMS registration response message (SIP response code message).
  • An entity that processes an IMS registration such as an S-CSCF, receives the IMS registration request, and acquires information about the distribution unit, such as multicast address information for transmitting an emergency notification message, in addition to normally processing the IMS registration request.
  • the receiving unit sends the IMS registration response message carrying the emergency event notification service discovery information, so that the receiving unit acquires the emergency event notification service discovery information while completing the IMS registration.
  • the service discovery unit is located in the entity that processes the IMS registration request in the IMS network, such as the S-CSCF.
  • the emergency notification service discovery request is located in the IMS registration request message, and the emergency notification service discovery request may be an implicit request, that is, the emergency notification service discovery request is not explicitly carried in the IMS registration request sent by the receiving unit.
  • the entity that processes the IMS registration request additionally adds the processing of the emergency notification service discovery, and carries the emergency notification service discovery information in the IMS registration response message.
  • the emergency notification service discovery request may also be an explicit request, that is, the emergency notification service discovery request indication is explicitly carried in the IMS registration request message.
  • the PULL mode emergency notification service in the IMS registration process finds that the emergency notification service discovery request is located in the IMS registration request message, and the emergency notification service discovery response is located in the IMS registration response message.
  • the PULL mode service discovery process after the registration of the IMS means that the receiving unit sends an emergency notification service discovery request after the IMS registration is completed, and obtains an emergency notification service discovery information, and the emergency notification service discovery process is completed after the IMS registration process.
  • the receiving unit sends an emergency notification service discovery request to the network, and the request may be sent to the S-CSCF, and the S-CSCF triggers the request to the emergency according to a certain policy, such as an initial filtering rule iFC.
  • the event notifies the service discovery entity (ie, the service discovery unit), for example, the AS, processes the service discovery request, and the AS responds to the emergency notification service discovery response message, and the message carries the emergency notification service discovery information, and the emergency notification service discovery response is cancelled.
  • 3 ⁇ 4 is sent to the receiving unit via the S-CSCF.
  • the emergency notification service discovery of the PUSH mode is to send an emergency notification service discovery indication message to the receiving unit after the service discovery unit senses the receiving unit.
  • the service discovery unit can be located at the bearer network layer or at the service layer.
  • the manner in which the service discovery unit perceives the receiving unit includes: after successfully processing the network attach request of the receiving unit, the network attaching device sends the network attaching information of the receiving unit to the service discovery unit; or the service discovery unit actively attaches the device to the network.
  • the information about the receiving unit attached to the network is queried; or the service discovery unit is located at the network attached device, and the information of the receiving unit is obtained through the internal interface of the entity.
  • the manner in which the service discovery unit perceives the receiving unit includes: the entity that processes the IMS registration sends the IMS registration information of the receiving unit to the service discovery unit after successfully processing the IMS registration request of the receiving unit; or the service discovery unit actively registers with the IMS.
  • the entity subscribes or queries the receiving unit information of the IMS registration; or the service discovery unit is located in the IMS registration entity, and obtains the IMS registration information of the receiving unit through the internal interface of the entity.
  • the service discovery unit also needs to obtain the emergency notification service discovery information, which may be pre-configured on the service discovery unit, or may be obtained by the service discovery unit to the external database during the service discovery process.
  • the emergency notification service discovery request message may be a DHCP request message, a SIP message, a Diame ter message, a RADIUS message, other proprietary messages, and the like.
  • the emergency notification service discovery indication message may be a Di ame ter message, a S IP Me s sage message, a RADIUS message, or the like.
  • the emergency event notification service attachment may be subsequently performed.
  • Step 202 The receiving unit is attached to the emergency notification service.
  • the receiving unit is attached to the emergency notification service, which means that the receiving unit can prepare to receive the emergency event notification, that is, the receiving unit can receive the emergency event notification message sent by the distribution unit after the service is attached.
  • the receiving unit After receiving the emergency event notification service discovery information in step 201, the receiving unit sends an emergency event notification service attach request to the distribution unit through the E2 interface, and attaches to the emergency event notification service.
  • the emergency notification message is sent in a multicast manner, and the manner in which the receiving unit attaches to the emergency notification service includes:
  • the receiving unit acquires the multicast address information used by the distribution unit to send the emergency notification
  • the receiving unit sends a request message to the distribution unit to join the corresponding multicast group, for example, the Interne t group management ten office (IGMP, Interne t Group) Management Pro toco l) Joins a message (ie, an IGMP Jo in message) to prepare to receive an emergency notification message sent using the multicast address.
  • the emergency notification receiving unit joins the multicast group and does not exit the multicast group.
  • the receiving unit After the receiving unit is restarted or the network communication is interrupted, the receiving unit needs to rejoin the multicast group, or needs to re-enter When the network is attached or the IMS is registered, the receiving unit needs to perform service discovery again, and re-attach the service, that is, rejoin the multicast group. or,
  • the receiving unit obtains the indirect distribution unit information of the distribution unit, for example, the address information of a database server
  • the receiving unit first acquires the indirect information, and further acquires the direct information of the distribution unit, for example, first obtains the information of the database server address.
  • obtaining the address information of the emergency notification distribution unit from the database server and after acquiring the multicast address used by the distribution unit to send the emergency notification message, sending the request message to join the corresponding multicast group to the distribution unit, and adding the corresponding multicast The group completes the attachment of the emergency notification service.
  • Step 203 The receiving unit receives an emergency event notification message sent by the distribution unit.
  • the method further includes: the distribution unit receiving the request message for issuing the emergency event notification sent by the issuing unit; and distributing the emergency event to the receiving unit according to the request message distributing unit Notification message. That is, after receiving the emergency notification sending request sent by the issuing unit through the E4 interface, the distribution unit distributes the emergency notification message to the receiving unit through the E2 interface.
  • the distribution unit may receive an emergency notification of the audio and video mode through the M2 interface under the indication of the emergency notification message sent by the issuing unit through the E4 interface, and carry the emergency in the emergency notification message sent through the E2 interface.
  • the event notification indication instructs the receiving unit to receive an emergency notification of the audio and video mode through the M1 interface.
  • the step 203 further includes: instructing the receiving unit to perform the processing and presentation of the emergency event notification according to the emergency notification in the emergency event notification message.
  • the receiving unit After receiving the emergency notification message sent by the E2 interface, if the emergency notification message carries the emergency notification indication, the receiving unit receives the emergency notification of the audio and video mode through the M1 interface and presents the emergency event notification.
  • the emergency notification message transmitted on the E4 interface and the emergency notification message transmitted on the E2 interface may be inconsistent.
  • the audio and video transmitted on the M2 interface may not be consistent with the audio and video transmitted on the M1 interface.
  • the E4 interface and the M2 interface are external interfaces of the IMS system, and may be a unified interface of the emergency processing center specified by the government department.
  • the unified interface may be connected to multiple communication networks other than the IMS network.
  • the E2 interface and the M1 interface are interfaces within the IMS network and are defined within the IMS network.
  • the distribution unit can perform format conversion between the E4 interface and the E2 interface, and between the M2 interface and the M1 interface.
  • the audio and video encoding on the M2 interface is a certain format, and the audio and video encoding transmitted on the M1 interface may be converted into another format. Format;
  • the distribution unit can also be modified in the transfer mode.
  • the E4 interface and the M2 interface are unicast, and the unicast media stream negotiation can be performed on the E4 interface to establish an M2 media channel; the E2 interface and the M1 interface use multicast transmission, and the E2 interface indicates the receiving unit.
  • the address of the multicast media stream The receiving unit receives the multicast media stream by joining the multicast group.
  • the service layer content transmitted between the E4 interface and the E2 interface, and between the M2 interface and the M1 interface needs to be consistent, that is, the content of the emergency notification itself cannot be changed.
  • the distribution unit After the distribution unit receives the emergency notification release request message sent by the publishing unit through the E4 interface, the distribution unit needs to be authenticated.
  • the authentication may be to use the preset policies and data, authenticate the legality of the identity of the issuing unit, and authenticate the validity of the emergency notification message issued by the issuing unit. After the certification is passed, the distribution of the emergency notification is initiated.
  • the E2 interface sends an emergency notification message in a multicast manner.
  • the receiving unit obtains the multicast address used by the distribution unit to send the emergency notification message through the emergency notification service discovery, and has joined the corresponding multicast group when the emergency notification service is attached, and then the distribution unit uses the multiple
  • the broadcast address sends an emergency notification message
  • the receiving unit can receive the emergency notification message.
  • the transmission of the emergency notification message of the multicast mode greatly reduces the processing performance requirement of the distribution unit compared with the unicast mode, and greatly reduces the bandwidth requirement for the transmission network, and avoids the single use of the multicast mode.
  • the broadcast mode requires a large number of messages to be sent in an instant. In this way, it is possible to effectively avoid overloading the processing unit of the distribution unit or transmitting network congestion.
  • the receiving unit receives the multicast address of the multicast group that is added when the emergency notification service is attached (that is, the multicast address obtained when the emergency notification service is discovered), and the multicast address used by the distribution unit to send the emergency notification message must be Consistent.
  • the distribution unit can obtain the multicast address in two ways, one is pre-configured on the distribution unit, and the other is the distribution unit queries the external database. In the former method, the preset data must be consistent with the data preset on the service discovery unit or with the data in the external database used by the service discovery unit. In the latter case, the data on the external database used by the distribution unit must match the data preset on the service discovery unit, or be consistent with the data on the external database used by the service discovery unit, or use the same external database.
  • the distribution unit may perform certain filtering during the process of distributing the emergency notification message, for example, filtering according to the geographic location, and the filtering method may be: carrying the emergency area notification code applicable in the emergency notification message sent by the issuing unit List, the distribution unit is a network composed of multiple physical entities, different physical entities may be located in different geographical areas, and the emergency notification message is distributed to the physical entities of the geographical area corresponding to the above-mentioned geographical area coding list, and then these The physical entity sends to the receiving unit that it is responsible for in conformity with the above-mentioned geographical area code list.
  • the emergency notification message transmitted on the E2 interface carries an emergency notification indication, including the type of emergency notification, for example, there are three types of emergency notifications, namely text mode, text+audio mode, audio and video mode, emergency indication, And if you need to use the Ml interface to transfer
  • the audio and video mode emergency notification media stream also includes an emergency notification media stream for transmitting
  • the M1 interface may use the multicast mode.
  • the M1 interface parameter may directly be the multicast address information used for sending the audio and video media stream.
  • the receiving unit joins the corresponding multicast group according to the emergency notification notification, receives the multicast audio and video media stream, and plays the output.
  • This multicast address can be a dedicated specific multicast address, or a normal multicast address.
  • the Ml interface parameter can also be a broadcast address.
  • the receiving unit receives the audio and video media stream (e.g., tuned to the corresponding frequency) from the broadcast address in accordance with the emergency notification indication, and plays the output.
  • the M1 interface parameter may also be another application layer address, such as an FTP address or an HTTP address.
  • the receiving unit needs to obtain the content indicated by the address according to the emergency notification notification, for example, using FTP or HTTP to obtain audio and video content, and Play the output.
  • the Ml interface parameter may also be an IPTV channel identifier, and the receiving unit switches to the channel according to the emergency notification indication, and receives and plays the audio and video media content of the channel.
  • This IPTV channel identifier can be a specific channel identifier, specifically for the transmission of an emergency notification media stream, or a normal channel identification.
  • the receiving unit switches to the indication channel in the following cases:
  • the receiving unit if the receiving unit is playing the time-shifted content of the channel indicated by the IPTV channel identifier, the receiving unit ends the time shifting state and switches to the live broadcast state;
  • the receiving unit performs the channel Switching to switch to the channel indicated by the IPTV channel identifier
  • the receiving unit is playing the content of another channel different from the channel indicated by the IPTV channel identifier, and the two channels belong to different domains, for example, the user terminal roams to a visited domain, but is playing a channel of the home domain Content, the channel identifier in the emergency notification indication information is the channel identifier of the visited domain, and the receiving unit stops the content playback of the another channel (either releasing the current service, or suspending the current media stream, or simply not presenting the content) a media stream, etc., initiating a play request of the channel indicated by the IPTV channel identifier to a domain where the IPTV channel identifier is located;
  • the receiving unit is playing a V0D program or a local program, or is performing a local menu operation, then the receiving unit stops or suspends the current program or operation, and initiates a live program service request,
  • the request carries the IPTV channel identifier
  • the receiving unit is in an idle state, does not play any live channel program, and does not play other types of programs, the receiving unit initiates a live program service request, and the request carries the IPTV channel identifier.
  • the receiving unit needs to cooperate according to the requirements of the emergency notification indication carried in the emergency notification message, such as stopping or suspending the currently playing program, and forcibly switching to the emergency received on the M1 interface.
  • the event notifies the playing of the audio and video media stream, whether the current user is playing an IPTV program, performing a video call, playing a game, playing a locally saved program, or performing a menu operation, etc., in order to make the user Get emergency notifications in a timely manner.
  • Such coordination processing may be mandatory by the competent government department. For example, in the IMS network, the user equipment UE must meet the relevant standards of the mandatory emergency notification service before it can be used in the network.
  • the network bandwidth resources required for transmitting audio and video media streams on the M1 interface should be guaranteed.
  • the M1 interface parameters are directly multicast addresses, and the receiving unit directly joins the corresponding multicast group.
  • the bandwidth occupied by other services If the user is using a service that occupies a large amount of bandwidth, and there is no remaining bandwidth or insufficient bandwidth, the bandwidth of the emergency notification service needs to be ensured. In this case, the bandwidth occupied by the service being used needs to be exceeded, that is, dynamic bandwidth adjustment is required. , reduce or even deprive other businesses of the bandwidth used, and provide these bandwidths to the emergency notification service.
  • the bandwidth policy of the emergency notification service may be preset in advance, that is, a policy execution entity or a policy decision entity preset to the bearer layer, and such pre-setting needs to obtain relevant parameters of the emergency event notification service media stream in advance. For example, if the emergency notification is sent in multicast mode, the multicast address needs to be obtained in advance, and the bandwidth requirement and priority of the media stream of the multicast address are preset in the policy enforcement entity or the policy decision entity of the bearer layer.
  • the policy execution entity When the bandwidth policy is preset to the policy enforcement entity, the policy execution entity automatically executes the preset policy after detecting the emergency notification media stream according to the parameters, allocates the corresponding bandwidth, and exceeds the bandwidth of other services as needed. Based on these parameters, the policy enforcement entity detects the end of the emergency notification (for example, using traffic detection), automatically releases the allocated bandwidth, and restores the bandwidth of other services that are overridden.
  • the policy decision entity may control the policy execution entity to execute the bandwidth policy by using a PUSH mode or a PULL mode.
  • the policy decision entity PUSH goes to all the policy enforcement entities it is responsible for, or the policy enforcement entity requests the bandwidth of the service from the policy decision entity.
  • the policy decision entity carries the bandwidth policy of the emergency notification in the response message.
  • the bandwidth policy of the emergency notification service may be that the distribution unit perceives that the receiving unit completes the network attachment, or is sent to the policy enforcement entity or the policy decision entity of the bearer layer in the process of handling the emergency event notification service attachment of the receiving unit.
  • the emergency notification system application server EAS AS senses that the receiving unit completes the network attachment and delivers the bearer policy to the bearer layer.
  • the bandwidth policy of the emergency notification service may be sent to the bearer layer during the emergency notification distribution process of the distribution unit, that is, when the distribution unit needs to send the emergency notification media stream, the bearer policy is sent to the bearer layer, and the request is pre-requested. Leave the corresponding bandwidth and indicate the priority to exceed the bandwidth of other services as needed.
  • the distribution unit sends a bearer policy to the bearer layer, requests to release the allocated bandwidth, and restores the bandwidth of other services that are overridden.
  • the EAS AS requests the resource and admission control subsystem (RACS, Res ource and Admi ssi on Cont ro l Sub-sys-tem) to reserve bandwidth resources and indicate the priority of the resources in the process of handling the emergency notification service distribution.
  • the ECF/EFF receives the emergency notification message or receives the emergency notification video media stream, requests the RACS to reserve the bandwidth resource and indicates the priority of the resource.
  • the bandwidth policy of the emergency notification service may be sent by the distribution unit to the bearer layer after receiving the emergency unit notification media content.
  • the ECF/EFF requests the RACS to reserve the bandwidth resource and indicate the priority of the resource. level.
  • the ECF/EFF should be able to identify the multicast address as the multicast address of the emergency notification, which may be carrying an emergency indication in the IGMP Jo in message, or the multicast address is a preset specific multicast address, or The ECF/EFF obtains the multicast address of the emergency notification media stream after receiving the emergency notification message.
  • the bandwidth policy of the emergency notification service may also be that after receiving the emergency event notification message, the receiving unit requests the policy enforcement entity of the bearer layer to allocate the corresponding bandwidth, and exceeds the bandwidth of other services as needed. Upon receiving the emergency notification, the receiving unit requests the policy enforcement entity of the bearer layer to release the allocated bandwidth and restore the bandwidth of other services. For example, the UE receives the emergency notification message, and the emergency notification in the message indicates carrying the emergency indication and the multicast address for transmitting the audio and video media stream, and the UE requests the RACS to reserve the bandwidth resource and indicate the priority of the resource.
  • the bandwidth policy of the emergency notification service may also be that after the receiving unit receives the emergency notification receiving message, the receiving unit initiates the establishment of the emergency event notification session, and the bandwidth resource is reserved through the establishment of the session, that is, the session is established during the session establishment process.
  • the CSCF interacts with the RACS to reserve resources.
  • the M1 interface parameter carried in the emergency notification message is often an IPTV channel identifier.
  • the channel identifier is a special frequency.
  • the track identifier is used to send an emergency notification media stream.
  • the channel is identified as a normal channel identifier.
  • the IPTV program is usually provided, and is used to send an emergency notification media stream when needed.
  • the emergency notification session initiated by the receiving unit is an emergency session, and the emergency response indication may be carried in the session establishment request message, or the network side call session control function (CSCF, Ca ll Ses sion Cont ro l Func t ion ) according to the requested channel
  • CSCF network side call session control function
  • the identifier is identified as an emergency session establishment request, and when the bandwidth request is reserved for the RACS, the priority of the service may be indicated, so that the bandwidth occupied by other services can be exceeded when necessary, and the bandwidth of the media stream is ensured by the emergency event.
  • An embodiment of the present invention provides a method for receiving an emergency notification.
  • the receiving unit finds an emergency notification service, it receives an emergency notification service sent by the distribution unit by attaching to the emergency notification service, and is in an emergency notification message.
  • the receiving unit performs processing and presentation of the corresponding emergency notification according to the emergency notification.
  • the distribution unit uses the multicast mode to distribute the emergency notification message, which can effectively avoid the problem that the bearer network congestion and the processing capability of the message sending unit are overloaded due to a message storm that may occur when the emergency notification service is sent.
  • Receiving an emergency notification message by the receiving unit attaching to the multicast address of the distribution unit, so that the user terminal can receive the emergency notification in time, as long as the user terminal is in normal communication with the bearer network whether or not the live television program is being watched. .
  • the bandwidth policy of the service is notified by the provided emergency event, so that the terminal of the IMS network enjoys any program, such as watching an IPTV program or playing a game, or watching a program saved locally by the terminal, or
  • the menu operation is performed, and no matter what communication is being performed, for example, a video call is made, and an emergency notification can be received in time.
  • the emergency notification service can be provided in the case of various service abnormalities, for example, in the various states such as the user's arrears or downtime, the unused IPTV service status, and the roaming status, as long as the user successfully registers the IMS network, it can receive Emergency notification service; even in the case that the user terminal does not successfully register the IMS network, or the IMS network registration fails, roaming restrictions, etc., as long as the communication between the terminal and the bearer network is normal, the emergency notification service can be received. Law into one , ", , , , , and example one:
  • FIG. 3 is a flowchart of a method for receiving an emergency notification according to Embodiment 1 of the present invention.
  • an EAS Center of an emergency department of a government department is a release unit of an emergency notification, in an IMS network.
  • the EAS application server EAS AS and the EAS media server EAS MF and the multicast replication control point and the replication point ECF/EFF are the distribution units for the emergency notification
  • the DHCP server (DHCP Server) is the service discovery unit for the emergency notification
  • the user equipment UE is Receiving unit for emergency notification.
  • DHCP Request network attach request
  • DHCP Response network attach response message
  • the UE completes the discovery of the emergency notification service during the network attachment process.
  • the emergency notification message is transmitted in a multicast manner
  • the emergency notification service discovery information is a multicast address for transmitting an emergency notification message.
  • Step 303 The UE sends an IGMP Join message to the ECF/EFF.
  • the UE After acquiring the multicast address, the UE joins the corresponding multicast group, completes the emergency notification service attachment, and prepares to receive the emergency notification message.
  • Step 304 The EAS Center sends an EAS Request message (EAS Request) for issuing an emergency notification to the EAS AS.
  • EAS Request EAS Request
  • the emergency notification includes an audio and video media stream
  • the request message for issuing the emergency notification sent by the EAS Center carries an emergency notification indication, indicating that the audio and video media stream needs to be received.
  • Step 305 The EAS AS sends a request message (MF Request) for receiving and distributing the emergency notification media stream to the EAS MF.
  • MF Request request message
  • Step 306 The EAS AS sends a response message (EAS Response) for issuing an emergency notification request to the EAS Center.
  • EAS Response a response message
  • the EAS AS can authenticate the EAS Center, including authenticating the identity legality of the EAS Center and authenticating the emergency notification message issued by the EAS Center.
  • Step 307 The EAS AS receives an emergency notification message (EAS Mes sage) issued by the EAS Center.
  • EAS Mes sage an emergency notification message issued by the EAS Center.
  • Step 308 the EAS AS distributes the emergency notification message (EAS Message) to the EAS AS.
  • Step 309 The UE receives the emergency notification message (EAS Message) from the ECF/EFF.
  • the UE obtains a multicast address for sending the emergency notification media stream according to the emergency notification notification in the emergency notification message, and joins the multicast group corresponding to the emergency notification media stream to receive the audio and video emergency notification. .
  • Step 311 The ECF/EFF interacts with the RACS to perform resource reservation.
  • the ECF/EFF processes the multicast group join request message, requests the resource and the admission control subsystem RACS to reserve the bearer resource, and carries the reserved bearer resource according to the identified multicast address or emergency indication.
  • the multicast address of the audio/video media stream may be a specific multicast address, and after the ECF/EFF identifies the specific multicast address, when the resource reservation is performed with the RACS, the priority of the applied resource is carried, indicating the bandwidth. When it is insufficient, it exceeds the bandwidth occupied by other services.
  • the multicast address may also be a normal multicast address.
  • the IGMP Jo in message sent by the UE carries an emergency indication, and the ECF/EFF determines the priority of the applied resource according to the emergency indication.
  • Step 312 The EAS MF receives the issued emergency notification media stream (EAS Media) from the EAS Center.
  • EAS Media issued emergency notification media stream
  • Step 313 the EAS MF distributes the emergency notification media stream (EAS Medi a ) to the ECF/EFF.
  • Step 314 The UE receives the emergency notification media stream (EAS Medi a ) from the ECF/EFF, and plays the output.
  • EAS Medi a emergency notification media stream
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • FIG. 4 is a flowchart of a method for receiving an emergency notification according to Embodiment 2 of the present invention.
  • an EAS Center of an emergency department of a government department is a release unit of an emergency notification, in an IMS network.
  • EAS application server EAS AS and EAS media server EAS MF and multicast replication control point and replication point ECF/EFF are the distribution unit of emergency notification
  • EAS F inder is the service discovery unit of emergency notification
  • user equipment UE is emergency notification Receiving unit.
  • Step 401 The UE sends an emergency notification service discovery request message (EAS F ind Reque s t ) to the EAS F inder.
  • EAS F ind Reque s t an emergency notification service discovery request message
  • Step 402 The EAS F inder returns an emergency notification service discovery response message (EAS F ind Response) to the UE, where the message carries the emergency event notification service discovery information.
  • EAS F ind Response an emergency notification service discovery response message
  • the user equipment UE performs the emergency event notification service discovery after completing the network attachment, and may use the emergency notification service discovery request message of the broadcast mode to process the entity EAS F inder processing of the emergency notification service discovery.
  • the broadcast message may be used to process the entity EAS F inder processing of the emergency notification service discovery.
  • the emergency notification message is transmitted in a multicast manner
  • the emergency notification service discovery information is a multicast address for transmitting an emergency notification message.
  • Step 403 The UE sends an IGMP Jo in message to the ECF/EFF.
  • the UE obtains the multicast discovery address from the received emergency notification service discovery information, adds the corresponding multicast group, completes the emergency notification service attachment, and prepares to receive the emergency notification message.
  • Step 404 The EAS Center sends a request message (EAS Reques t) for issuing an emergency notification to the EAS AS.
  • the emergency notification includes an audio and video media stream
  • the request message for issuing the emergency notification sent by the EAS Center carries an emergency notification indication, indicating that the audio and video media stream needs to be received.
  • Step 405 The EAS AS sends a request for receiving and distributing an emergency notification media stream (MF Request) to the EAS MF.
  • MF Request emergency notification media stream
  • Step 406 The EAS AS returns a response message (EAS Response) for issuing an emergency notification request to the EAS Center.
  • EAS Response a response message
  • the EAS AS can authenticate the EAS Center, including authenticating the identity legality of the EAS Center and authenticating the emergency notification message issued by the EAS Center.
  • Step 407 The EAS AS receives an emergency notification message (EAS Mes sage) issued by the EAS Center.
  • EAS Mes sage an emergency notification message issued by the EAS Center.
  • Step 408 the EAS AS distributes the emergency notification message (EAS Message) to the EAS AS.
  • step 409 the ECF/EFF interacts with the RACS to reserve resources.
  • the step is specifically as follows: After receiving the emergency notification message (EAS Message), the ECF/EFF exchanges the bearer resource with the RACS according to the parameters of the audio and video media stream carried in the emergency notification indication.
  • the ECF/EFF is the priority of the resource to be applied when the resource reservation is performed by the RACS to identify the emergency notification message, indicating that the bandwidth occupied by other services is exceeded when the bandwidth is insufficient.
  • Step 410 The UE receives the emergency notification message (EAS Message) from the ECF/EFF.
  • the EAS MF receives the released emergency notification media stream (EAS Media) from the EAS Center.
  • step 412 the EAS MF distributes the received emergency notification media stream (EAS Media) to the ECF/EFF.
  • EAS Media emergency notification media stream
  • Step 413 The UE sends an IGMP Join message to the ECF/EFF.
  • the UE obtains the multicast address for sending the emergency notification media stream according to the emergency notification notification in the emergency notification message, joins the multicast group corresponding to the emergency notification media stream, and receives the emergency notification of the audio and video mode.
  • Step 414 The UE receives the emergency notification media stream ( EAS Media ) from the ECF/EFF and plays the output.
  • EAS Media emergency notification media stream
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • FIG. 5 is a flowchart of a method for receiving an emergency notification according to Embodiment 3 of the present invention.
  • an EAS Center of an emergency department of a government department is a release unit of an emergency notification, in an IMS network.
  • EAS application server EAS AS and EAS media server EAS MF and multicast replication control point and replication point ECF/EFF are the distribution unit for emergency notification
  • EAS Finder and DHCP Server are the service discovery unit for emergency notification
  • user equipment UE is emergency The receiving unit of the event notification.
  • Step 501 After processing the network attachment of the UE, the DHCP server actively reports the status information (Network Attachment Announce) of the UE to the EAS Finder.
  • the emergency event notification service is discovered, where is the PUSH emergency event service discovery, and the entity EAS Finder for the emergency notification service discovery senses the UE.
  • the network attachment is completed (here, the DHCP server processes the user's network attachment and actively sends the EAS Finder), the emergency notification service discovery indication information is sent to the UE.
  • Step 502 The EAS Finder actively sends an emergency notification service discovery indication information (EAS Service Announce) to the UE.
  • EAS Service Announce an emergency notification service discovery indication information
  • the emergency notification message is transmitted in a multicast manner
  • the emergency notification service discovery information is a multicast address for transmitting an emergency notification message.
  • Step 503 The UE returns an EAS Service Response of the emergency notification service discovery indication to the EAS Finder.
  • Step 504 The UE sends an IGMP Join message to the ECF/EFF.
  • the UE After obtaining the multicast address from the received emergency notification service discovery information, the UE requests to join the corresponding multicast group, completes the emergency notification service attachment, and prepares to receive the emergency notification message.
  • Step 505 The EAS Center sends an EAS Request message (EAS Request) for issuing an emergency notification to the EAS AS.
  • EAS Request EAS Request message
  • the emergency notification includes an audio and video media stream
  • the request message for issuing the emergency notification sent by the EAS Center carries an emergency notification indication, indicating that the audio and video media stream needs to be received.
  • Step 506 The EAS AS sends a request for receiving and distributing an emergency notification media stream (MF Request) to the EAS MF.
  • MF Request emergency notification media stream
  • Step 507 The EAS AS returns a response message (EAS Response) for issuing an emergency notification request to the EAS Center.
  • EAS Response a response message
  • Step 508 The EAS AS receives an emergency notification message (EAS Mes sage) issued by the EAS Center.
  • EAS Mes sage an emergency notification message issued by the EAS Center.
  • Step 509 the EAS AS distributes the emergency notification message (EAS Message) to the ECF/EFF.
  • Step 510 The UE receives the emergency notification message (EAS Message) from the ECF/EFF.
  • the EAS MF receives the released emergency notification media stream (EAS Media) from the EAS Center.
  • step 512 the EAS MF distributes the received emergency notification media stream (EAS Media) to the ECF/EFF.
  • the ECF/EFF interacts with the RACS to perform resource reservation.
  • the step is specifically as follows: After receiving the emergency notification media stream, the ECF/EFF exchanges with the RACS to reserve the bearer resource.
  • the ECF/EFF obtains the multicast address of the emergency notification notification media stream from the emergency notification indication, and interacts with the RACS when the media stream of the multicast address arrives. Reserve, and carry the priority of the applied resource, indicating that the bandwidth occupied by other services is exceeded when the bandwidth is insufficient.
  • Step 514 The UE sends an IGMP Join message to the ECF/EFF.
  • the UE obtains the multicast address for sending the emergency notification media stream according to the emergency notification notification in the emergency notification message, and joins the multicast group corresponding to the emergency notification media stream to receive the emergency notification of the audio and video mode.
  • Step 515 the UE receives the emergency notification media stream ( EAS Media ) from the ECF/EFF and plays the output.
  • EAS Media emergency notification media stream
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • FIG. 6 is a flowchart of a method for receiving an emergency notification according to Embodiment 4 of the present invention.
  • an EAS Center of an emergency department of a government department is a release unit of an emergency notification, in an IMS network.
  • EAS application server EAS AS and EAS media server EAS MF and multicast replication control point and replication point ECF/EFF are the distribution unit for emergency notification
  • call session control function CSCF and EAS AS are service discovery units for emergency notification
  • the UE is a receiving unit of an emergency notification.
  • Step 601 The UE sends an IMS registration request message (Register) to the CSCF.
  • Register IMS registration request message
  • Step 602 The CSCF returns a 200 OK message to the UE, and completes the IMS registration of the UE.
  • Step 603 The CSCF sends a third party IMS registration request message (Regi s ter ) to the EAS AS.
  • Step 604 The EAS AS returns a 200 OK message to the CSCF to complete the third party's IMS registration.
  • Step 605 The EAS AS actively sends an emergency notification service discovery indication message (Message) to the UE.
  • Message emergency notification service discovery indication
  • the user equipment UE performs the discovery of the emergency notification service through the third party registration in the IMS registration process, where the service discovery is PUSH mode service discovery.
  • the CSCF After processing the IMS registration request of the UE, the CSCF sends a third party registration request to the EAS AS. After processing the third party registration, the EAS AS actively sends an emergency notification service discovery indication message to the UE.
  • the emergency notification message is transmitted in a multicast manner
  • the emergency notification service discovery information is a multicast address for transmitting an emergency notification message.
  • Step 006 The UE sends an IGMP Join message to the ECF/EFF.
  • the UE obtains the multicast discovery address from the received emergency notification service discovery information, adds the corresponding multicast group, completes the emergency notification service attachment, and prepares to receive the emergency notification message.
  • Step 607 the EAS Center sends a request message for issuing an emergency notification to the EAS AS. ( EAS Request ).
  • the emergency notification includes an audio and video media stream
  • the request message for issuing the emergency notification sent by the EAS Center carries an emergency notification indication, indicating that the audio and video media stream needs to be received.
  • Step 608 The EAS AS sends a request for receiving and distributing an emergency notification media stream (MF Request) to the EAS MF.
  • MF Request emergency notification media stream
  • Step 609 The EAS AS returns a response message (EAS Response) for issuing an emergency notification request to the EAS Center.
  • EAS Response a response message
  • Step 610 The EAS AS receives an emergency notification message (EAS Mes sage) issued by the EAS Center.
  • EAS Mes sage an emergency notification message issued by the EAS Center.
  • Step 611 The EAS AS sends a bandwidth policy to the bearer layer.
  • the step is specifically: after receiving the emergency notification message, the EAS AS sends a bandwidth policy to the bearer layer according to the parameters of the audio and video media stream carried in the emergency notification indication, and indicates the bandwidth requirement and priority of the emergency event notification audio and video media stream.
  • the bandwidth policy can be delivered to the RACS, the RACS completes the bearer resource reservation, and exceeds the bandwidth occupied by other services when the bandwidth is insufficient.
  • Step 612 the EAS AS distributes the emergency notification message (EAS Message) to the ECF/EFF.
  • EAS Message the emergency notification message
  • step 613 the UE receives the emergency notification message (EAS Message) from the ECF/EFF.
  • EAS MF receives the issued emergency notification media stream from the EAS Center (EAS)
  • Step 615 the EAS MF distributes the received emergency notification media stream (EAS Media) to the ECF/EFF.
  • EAS Media emergency notification media stream
  • Step 616 The UE sends an IGMP Join message to the ECF/EFF.
  • the UE obtains a multicast address for sending the emergency notification media stream according to the emergency notification notification in the emergency notification message, and joins the multicast group corresponding to the emergency notification media stream to receive the audio and video emergency notification. .
  • Step 617 the UE receives the emergency notification media stream ( EAS Media ) from the ECF/EFF and plays the output.
  • EAS Media emergency notification media stream
  • Embodiment 5 is a diagrammatic representation of Embodiment 5:
  • FIG. 7 is a flowchart of a method for receiving an emergency notification according to Embodiment 5 of the present invention.
  • an EAS Center of an emergency department of a government department is a release unit of an emergency notification, in an IMS network.
  • EAS application server EAS AS and EAS media server EAS MF and multicast replication control point and replication point ECF/EFF and emergency call session control function E-CSCF are emergency notification notification units, DHCP server for emergency notification
  • the service discovery unit, the user equipment UE is a receiving unit of the emergency notification.
  • Step 701 The UE sends a network attach request message (DHCP Request) to the DHCP server.
  • Step 702 the DHCP server returns a network attach request response message to the UE (DHCP)
  • the response message carries an emergency notification service discovery information.
  • the user equipment UE is configured to complete the discovery of the emergency notification service during the network attachment process.
  • the emergency notification message is transmitted in a multicast manner
  • the emergency notification service discovery information is a multicast address for transmitting an emergency notification message.
  • Step 703 The UE sends an IGMP Join message to the ECF/EFF.
  • the UE obtains the multicast discovery address from the received emergency notification service discovery information, adds the corresponding multicast group, completes the emergency notification service attachment, and prepares to receive the emergency notification message.
  • Step 704 The EAS Center sends an EAS Request message (EAS Request) for issuing an emergency notification to the EAS AS.
  • EAS Request EAS Request message
  • the emergency notification includes an audio and video media stream
  • the request message for issuing the emergency notification sent by the EAS Center carries an emergency notification indication, indicating that the audio and video media stream needs to be received.
  • Step 705 The EAS AS sends a request for receiving and distributing an emergency notification media stream (MF Request) to the EAS MF.
  • MF Request emergency notification media stream
  • Step 706 The EAS AS returns a response message (EAS Response) for issuing an emergency notification request to the EAS Center.
  • EAS Response a response message
  • Step 707 The EAS AS receives an emergency notification message (EAS Mes sage) issued by the EAS Center.
  • EAS Mes sage an emergency notification message issued by the EAS Center.
  • Step 708 the EAS AS distributes the emergency notification message (EAS Message) to the ECF/EFF.
  • Step 709 The UE receives the emergency notification message (EAS Message) from the ECF/EFF.
  • the emergency notification includes an audio and video media stream
  • the emergency notification message carries an emergency notification indication, where the M1 interface parameter in the emergency notification indication is an emergency notification channel identifier, and the UE is instructed to switch to the indicated channel.
  • Step 710 The EAS MF receives the released emergency notification media stream (EAS Media) from the EAS Center.
  • EAS Media released emergency notification media stream
  • step 711 the EAS MF distributes the received emergency notification media stream (EAS Media) to the ECF/EFF.
  • EAS Media emergency notification media stream
  • Step 712 The UE initiates an establishment request message (Invite) of the emergency notification session, where the request message carries an emergency notification channel identifier, and may carry an emergency indication.
  • the request message carries an emergency notification channel identifier, and may carry an emergency indication.
  • the E-CSCF interacts with the RACS to perform resource reservation.
  • the step is specifically: the E-CSCF processes the establishment request of the emergency notification session, requests the RACS to reserve the bearer resource, and carries the priority of the reserved bearer resource according to the identified IPTV channel identifier or emergency indication.
  • the channel identifier for sending the emergency notification media stream may be a specific channel identifier, and the E-CSCF identifies the specific channel identifier, and the priority of the resource to be applied in the process of performing resource reservation with the RACS, indicating that the bandwidth is insufficient. Overtakes the bandwidth occupied by other services.
  • the channel identifier is a common channel identifier, and the session establishment request message sent by the UE carries an emergency indication, and the E-CSCF determines the priority of the applied resource according to the emergency indication.
  • Step 714 The E-CSCF forwards an establishment request message (I nv i te ) of the emergency notification session to the EAS AS.
  • Step 715 The EAS AS returns a 200 OK response message to the E-CSCF, where the response message carries the multicast address of the emergency notification I PTV channel.
  • Step 716 The E-CSCF sends the 200 OK response message to the UE to complete establishment of an emergency notification session.
  • Step 717 The UE sends an IGMP Jo in message to the ECF/EFF.
  • the UE receives the emergency session response message, establishes an emergency session, obtains a multicast event notification IPTV channel multicast address from the response message, and joins the multicast group corresponding to the multicast address to receive the audio and video media stream.
  • Step 71 8 The UE receives the emergency event notification media stream sent by the IPTV channel from the ECF/EFF and plays the output.
  • the UE may not receive the IMS registration, or the IMS registration fails to receive the emergency notification, which is implemented by the emergency session.
  • the emergency notification is used to notify the channel identification information or the emergency session identifier in the session, and the network side performs emergency special processing on the session, allowing the unregistered user to initiate an emergency session, and processing through the E-CSCF and the EAS AS to complete the emergency session.
  • FIG. 8 is a flowchart of a method for receiving an emergency notification according to Embodiment 6 of the present invention.
  • an emergency department of an emergency department of a government department, EAS Center is a release unit for an emergency notification, and an IMS network.
  • the EAS application server EAS AS and the EAS media server EAS MF and the multicast replication control point and the replication point ECF/EFF are the distribution units of the emergency notification
  • the call session control function CSCF is the service discovery unit of the emergency notification
  • the user equipment UE is Receiving unit for emergency notification.
  • Step 801 The UE sends an IMS registration request message (Reg i s ter ) to the CSCF.
  • Step 802 The CSCF returns an IMS registration response message (200 0K) to the UE, where the message carries the emergency event notification service discovery information.
  • the user equipment UE is configured to complete the discovery of the emergency notification service during the IMS registration process.
  • the emergency notification message is transmitted in a multicast manner
  • the emergency notification service discovery information is a multicast address for transmitting an emergency notification message.
  • Step 803 The UE sends an IGMP Join message to the ECF/EFF.
  • the UE obtains the multicast discovery address from the received emergency notification service discovery information, adds the corresponding multicast group, completes the emergency notification service attachment, and prepares to receive the emergency notification message.
  • Step 804 The EAS Center sends an EAS Request message (EAS Request) for issuing an emergency notification to the EAS AS.
  • EAS Request EAS Request message
  • the emergency notification includes an audio and video media stream
  • the request message for issuing the emergency notification sent by the EAS Center carries an emergency notification indication, indicating that the audio and video media stream needs to be received.
  • Step 805 The EAS AS sends a request for receiving and distributing an emergency notification media stream (MF Request) to the EAS MF.
  • MF Request emergency notification media stream
  • Step 806 the EAS AS returns a response message (EAS Response) for issuing an emergency notification request to the EAS Center.
  • EAS Response a response message
  • Step 807 the EAS AS receives an emergency notification message (EAS Mes sage) issued by the EAS Center.
  • EAS Mes sage an emergency notification message issued by the EAS Center.
  • Step 808 the EAS AS distributes the emergency notification message (EAS Message) to the ECF/EFF.
  • Step 809 the UE receives the emergency notification message (EAS Message) from the ECF/EFF.
  • the EAS MF receives the issued emergency notification media stream (EAS Media) from the EAS Center.
  • step 811 the EAS MF distributes the received emergency notification media stream (EAS Media) to ECF/EFF.
  • EAS Media emergency notification media stream
  • Step 812 The UE interacts with the RACS to perform resource reservation.
  • the step is specifically: after receiving the emergency event notification message, the UE obtains an emergency event notification media stream that needs to receive the audio and video mode according to the emergency event notification instruction, requests the RACS to reserve the bearer resource, and carries the priority of the applied resource, and indicates Override the bandwidth occupied by other services when bandwidth is insufficient.
  • Step 813 The UE sends an IGMP Join message to the ECF/EFF.
  • the UE obtains the multicast address for sending the emergency notification media stream according to the emergency notification notification in the emergency notification message, and joins the multicast group corresponding to the emergency notification media stream to receive the emergency notification of the audio and video mode.
  • Step 814 the UE receives the emergency notification media stream (EAS Media) from the ECF/EFF, And play the output.
  • EAS Media emergency notification media stream
  • the embodiment of the present invention further provides a method for receiving an emergency event notification media stream, as shown in FIG. 9 and FIG.
  • a flowchart of a method for receiving an emergency event notification media stream according to an embodiment of the present invention includes:
  • Step 901 The receiving unit acquires network parameters of the emergency event notification media stream from the emergency event notification message, where the network parameter includes multicast address information, where the multicast address information may be a specific specific multicast address, or is a common Multicast address.
  • Step 902 The receiving unit sends a request message that is added to the multicast group corresponding to the multicast address information, where the request message carries the multicast address information, or carries an emergency indication at the same time.
  • Step 903 The multicast replication control point and the replication point ECF/EFF process the multicast group join request message, request the resource and the admission control subsystem RACS to reserve the bearer resource, and according to the identified multicast address or An emergency indication carries the priority of the reserved bearer resources.
  • Step 904 The receiving unit joins the multicast group to receive an emergency notification media stream and plays the output.
  • the step of the ECF/EFF requesting the RACS to reserve the bearer resource may be: when the ECF/EFF processes the multicast group join request message, requesting the RACS to reserve the bearer resource; or
  • the ECF/EFF requests the RACS to reserve the bearer resource when receiving the emergency notification message
  • the ECF/EFF When the ECF/EFF receives the emergency notification media stream, the ECF/EFF requests the RACS to reserve the bearer resource.
  • the step 530 of the bandwidth policy can also be:
  • the emergency notification system application server after receiving the emergency notification message, the EAS AS requests the bearer layer to reserve the bearer resource according to the network parameter of the emergency event notification media stream, and the request carries the priority of the reserved bearer resource. Or,
  • the receiving unit notifies the RACS of the resource and the admission control subsystem to reserve the bearer resource according to the network parameter of the obtained emergency event notification, and the request carries the priority of the reserved bearer resource.
  • FIG. 10 is a flowchart of a method for adding an emergency event notification IPTV channel according to an embodiment of the present invention, including:
  • Step 1 01 0 The receiving unit acquires an IPTV channel identifier of the emergency notification from the emergency notification message, where the IPTV channel identifier may be a specific channel identifier dedicated to the emergency event notification media stream transmission, or an ordinary channel identifier.
  • Step 1020 The receiving unit initiates an establishment request of an emergency notification session, where the setup request carries the IPTV channel identifier, or carries an emergency indication at the same time.
  • Step 1030 the emergency call session control function E-CSCF processes the establishment request of the emergency notification session, requests the resource and admission control subsystem RACS to reserve the bearer resource, and according to the identified IPTV channel identifier or emergency indication. , carrying the priority of the reserved bearer resources.
  • Step 1040 the emergency call session control function E-CSCF forwards the establishment request of the emergency notification session to the emergency notification system application server EAS AS.
  • Step 1050 the emergency call session control function E-CSCF receives and forwards the response message returned by the application server EAS AS, and the response message carries the emergency event to notify the multicast address of the IPTV channel.
  • Step 1060 The receiving unit receives the response message of the emergency event notification session establishment request, adds the multicast group corresponding to the multicast address carried in the response message, receives the emergency event notification media stream sent by the IPTV channel, and plays the output.
  • FIG. 11 is a flowchart of a method for discovering an emergency notification service according to an embodiment of the present invention, including:
  • Step 1110 The receiving unit sends an IMS registration request to the call session control function CSCF.
  • Step 1130 After processing the third-party IMS registration request, the EAS AS sends an emergency notification service discovery to the receiving unit, 3 ⁇ 4.
  • the discovery message includes multicast address information for transmitting an emergency notification message, or indirect database server address information for transmitting an emergency notification message, for indicating how the recipient of the message is attached to the emergency notification service.
  • An embodiment of the present invention further provides a system for receiving an emergency notification, which is shown in FIG. 1, and includes:
  • the distribution unit 102 is configured to send an emergency event notification message to the receiving unit 103.
  • the receiving unit 103 is configured to discover an emergency event notification service, and attach to the emergency event notification service, and receive the emergency event notification message sent by the distribution unit 102.
  • the distribution unit 102 can be an entity, or several entities, or a distribution network.
  • distribution unit 102 can be one of the following and a combination thereof:
  • An application server AS configured to receive an emergency notification message, and obtain an emergency notification indication from the emergency notification message; distribute an emergency notification message; and control the media server MF to receive and distribute the emergency notification media stream according to the emergency notification indication;
  • a media server MF configured to receive and distribute an emergency notification media stream;
  • the distribution unit 102 may further include:
  • the emergency call session control function E-CSCF is configured to identify the session establishment request as an emergency channel join request message by identifying the channel identifier carried in the session establishment request as an emergency channel identifier, or by identifying an emergency indication carried in the session establishment request; After the emergency channel join request message is identified, the policy enforcement entity of the bearer layer is requested to reserve the bearer resource, where the request carries the priority of the reserved bearer resource.
  • the receiving unit 103 is further configured to obtain an emergency notification indication from the emergency notification message, and switch to the presentation of the emergency notification media stream according to the acquired emergency notification notification, and receive the emergency notification media stream.
  • the system also includes:
  • the service discovery unit 1 04 is configured to obtain information about the distribution unit 102 and provide the information to the receiving unit 103.
  • the service discovery unit 104 may be located in the same physical entity as the receiving unit, or may be located in the network attachment subsystem NASS, the gateway GPRS support node GGSN, the call session control function CSCF, the application server AS, or the processing network attach request. In the entity.
  • FIG. 12 is a functional block diagram of an emergency event notification receiving unit device according to an embodiment of the present invention, including:
  • the discovery processing module 121 0 is used for discovery of an emergency notification service.
  • the discovery includes the PULL mode service discovery during the network attachment process or after the network attachment is completed, the PULL mode service discovery in the IMS registration process or the IMS registration completion, and the PUSH mode service discovery after the network attachment is completed or after the IMS registration is completed.
  • the service attachment processing module 1220 is configured to perform an emergency event notification service attachment after the emergency notification service discovery is completed.
  • the message receiving processing module 12 30 is configured to receive an emergency notification message, and obtain an emergency notification indication from the emergency notification message.
  • the media stream receiving and processing module 1240 is configured to receive an emergency event notification media stream, and switch to the presentation of the emergency event notification media stream according to the acquired emergency event notification indication.
  • the emergency notification receiving unit device further includes one of the following and a combination thereof:
  • the reserved bearer resource requesting module 1250 is configured to request, by the bearer layer, the reserved bearer resource according to the emergency event notification indication, where the request carries the priority of the reserved bearer resource;
  • the emergency session establishment requesting module 1260 is configured to initiate an establishment request of an emergency notification session, where the establishment request carries an IPTV channel identifier indicated by the emergency notification, or carries an emergency indication at the same time.
  • FIG. 13 is a functional module diagram of an emergency event notification service server device according to an embodiment of the present invention, including:
  • the interface module 1 31 0 is configured to receive an emergency notification message, and obtain an emergency notification indication from the emergency notification message;
  • a message distribution module 1 320 configured to distribute an emergency notification message
  • a media flow control module 1 330 configured to control the media server according to the emergency notification indication
  • the MF receives and distributes emergency notification media streams.
  • the emergency notification service server device further includes one of the following and a combination thereof:
  • the reserved bearer resource requesting module 1 340 is configured to request, by the bearer layer, the reserved bearer resource according to the emergency event notification indication, where the request carries the priority of the reserved bearer resource;
  • the emergency session establishment processing module 1350 is configured to send a response message of the establishment request of the emergency notification session, where the response message carries the multicast address of the IPTV channel indicated by the emergency notification.
  • FIG. 14 is a functional block diagram of an emergency call session control function device according to an embodiment of the present invention, including:
  • the emergency channel join identification module 141 0 is configured to notify the emergency channel identifier that the I PTV channel identifier carried in the session establishment request is an emergency channel identifier, or identify the emergency event notification session establishment request by identifying an emergency indication carried in the session establishment request. Emergency channel join request message.
  • the emergency channel joining processing module 1420 is configured to, after identifying the emergency channel joining request message, request the policy enforcement entity of the bearer layer to reserve the bearer resource, and carry the reserved according to the identified I PTV channel identifier or emergency indication. The priority of the bearer resource.
  • the emergency channel joining processing module 1420 is further configured to forward an emergency event notification session establishment request to the emergency notification system application server EAS AS after identifying the emergency channel joining request message; receiving and forwarding the emergency notification system application server EAS The response message returned by the AS, where the response message carries the multicast address that the emergency channel joins.
  • the present invention can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is a better implementation. .
  • the embodiment of the present invention The technical solution may be embodied in the form of a software product, which is stored in a storage medium, and includes a plurality of instructions for causing a computer product (which may be an IPTV television, a mobile phone, etc.).
  • a personal computer, media player, etc.) performs the methods described in various embodiments of the present invention.
  • the storage medium referred to herein is, for example, R0M/RAM, magnetic disk, optical disk, and the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Emergency Management (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Telephonic Communication Services (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Abstract

La présente invention concerne un procédé, un équipement et un système servant à recevoir l'alerte d'un événement d'urgence, en ce qui concerne le domaine d'application d'une communication. Dans la mesure où le terminal utilisateur communique avec le réseau de support normalement, les utilisateurs peuvent recevoir l'alerte d'un événement d'urgence dans les temps, qu'ils soient ou non en train de regarder l'émission de télévision en direct. Le procédé consiste en ce que : l'unité de réception découvre le service d'alerte d'un événement d'urgence (201); l'unité de réception s'indexe au service d'alerte d'un événement d'urgence (202); l'unité de réception reçoit l'alerte d'un événement d'urgence qui est envoyée par l'unité de distribution (203). L'équipement de l'unité de réception d'alerte d'un événement d'urgence comprend le module de traitement de découverte, le module de traitement d'indexation du service et le module de traitement de réception du message. La mise en place de la présente invention entraîne la réception par l'utilisateur de l'alerte d'un événement d'urgence dans les temps grâce à l'indexation au service d'alerte d'un événement d'urgence.
PCT/CN2009/071245 2008-07-28 2009-04-13 Procédé, équipement et système servant à recevoir l'alerte d’un événement d’urgence WO2010012165A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/502,320 US8184002B2 (en) 2008-07-28 2009-07-14 Method and device for receiving emergency event alert

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200810134570.4 2008-07-28
CN2008101345704A CN101640573B (zh) 2008-07-28 2008-07-28 接收紧急事件通知的方法、装置和系统

Publications (1)

Publication Number Publication Date
WO2010012165A1 true WO2010012165A1 (fr) 2010-02-04

Family

ID=41609933

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/071245 WO2010012165A1 (fr) 2008-07-28 2009-04-13 Procédé, équipement et système servant à recevoir l'alerte d’un événement d’urgence

Country Status (2)

Country Link
CN (1) CN101640573B (fr)
WO (1) WO2010012165A1 (fr)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8184002B2 (en) 2008-07-28 2012-05-22 Huawei Technologies Co., Ltd. Method and device for receiving emergency event alert
CN102984550B (zh) * 2011-09-07 2018-01-09 中兴通讯股份有限公司 一种基于iptv的紧急通知发布的方法和系统
CN102610070B (zh) * 2012-03-27 2014-05-28 中华电信股份有限公司 一种利用低频无线时频传播系统的紧急告警系统及方法
CN105263063A (zh) * 2015-10-14 2016-01-20 天脉聚源(北京)传媒科技有限公司 一种播放控制方法及装置
CN108418819B (zh) * 2018-02-27 2023-02-03 湖南农业大学 一种农村应急广播流媒体直播方法与应用
CN110661668B (zh) * 2019-09-29 2023-05-16 深圳前海微众银行股份有限公司 一种消息发送管理方法及装置
CN114979006B (zh) * 2021-10-14 2023-09-05 中移互联网有限公司 一种会话初始协议sip消息处理方法及其消息处理系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070136743A1 (en) * 2005-12-09 2007-06-14 Charles Hasek Emergency alert data delivery apparatus and methods
WO2007101473A1 (fr) * 2006-03-07 2007-09-13 Telefonaktiebolaget Lm Ericsson (Publ) Décalage temporel et chase-play (enregistrement et lecture simultanés) pour un système de télévision sur ip
US20080059998A1 (en) * 2006-08-25 2008-03-06 Sbc Knowledge Ventures, Lp. System and method of communicating emergency alerts
CN101175198A (zh) * 2006-11-02 2008-05-07 华为技术有限公司 网络电视的业务控制方法及系统、终端和应用处理模块
US20080120639A1 (en) * 2006-11-21 2008-05-22 Sbc Knowledge Ventures, Lp System and method of providing emergency information

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6882709B1 (en) * 1999-04-14 2005-04-19 General Instrument Corporation Enhanced broadband telephony services
US20050183120A1 (en) * 2004-01-13 2005-08-18 Saurabh Jain Multi-user personalized digital multimedia distribution methods and systems
CN101222283B (zh) * 2007-11-29 2010-10-13 北京航空航天大学 基于用户位置实时播报交通信息的网络电台系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070136743A1 (en) * 2005-12-09 2007-06-14 Charles Hasek Emergency alert data delivery apparatus and methods
WO2007101473A1 (fr) * 2006-03-07 2007-09-13 Telefonaktiebolaget Lm Ericsson (Publ) Décalage temporel et chase-play (enregistrement et lecture simultanés) pour un système de télévision sur ip
US20080059998A1 (en) * 2006-08-25 2008-03-06 Sbc Knowledge Ventures, Lp. System and method of communicating emergency alerts
CN101175198A (zh) * 2006-11-02 2008-05-07 华为技术有限公司 网络电视的业务控制方法及系统、终端和应用处理模块
US20080120639A1 (en) * 2006-11-21 2008-05-22 Sbc Knowledge Ventures, Lp System and method of providing emergency information

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CISCO SYSTEMS, INC.: "IPTV Device Attachment and Initialization process for Core IPTV and NGN IPTV Architectures", FOCUS GROUP ON IPTV FG IPTV-C-0529, 25 April 2007 (2007-04-25), pages 2 - 5 *

Also Published As

Publication number Publication date
CN101640573A (zh) 2010-02-03
CN101640573B (zh) 2011-09-14

Similar Documents

Publication Publication Date Title
US8184002B2 (en) Method and device for receiving emergency event alert
US20230084473A1 (en) Unicasting and multicasting multimedia services
US10397644B2 (en) Switching between delivery methods in an IPTV communication network
CN101662376B (zh) 基于网际协议电视的信息推送方法、装置及系统
CN100579209C (zh) 基于ngn网络实现时移电视业务的方法及系统、媒体资源设备
US9226002B2 (en) Method, device and system for realizing broadcast TV
KR101433225B1 (ko) Ｉｍｓ 아키텍쳐 네트워크에서 ｉｐ 텔레비젼 서비스에 액세스하기 위한 시스템
WO2010012165A1 (fr) Procédé, équipement et système servant à recevoir l'alerte d’un événement d’urgence
US20100235856A1 (en) Method, system, and device for realizing internet protocol television service
WO2008101444A1 (fr) Système multimédia en flux, dispositif de transmission de signalisation et procédé d'envoi de multimédia en flux
WO2010028589A1 (fr) Procédé, dispositif et système de négociation de service « push »
WO2012122935A1 (fr) Procédé, appareil et dispositif terminal de partage de contenus de télévision sur protocole internet
WO2008134955A1 (fr) Procédé, système et appareil pour appliquer des informations de capacité de terminal dans un service iptv
WO2009030133A1 (fr) Procédé, système et entité pour réaliser une vidéo image dans image
KR20080050298A (ko) Ｉｍｓ 기반 ｉｐｔｖ 서비스 장치 및 방법
EP2590378B1 (fr) Procédé et système de radiodiffusion audio en vidéosurveillance
WO2009155840A1 (fr) Procédé, système et dispositif pour réaliser le partage de service de groupe
WO2009129728A1 (fr) Procédé, appareil et système de diffusion / de multidiffusion
CN101662377B (zh) 基于网际协议电视的信息推送方法、装置及系统
CN101155110A (zh) 一种实现业务集成的方法及系统
WO2011000151A1 (fr) Procédé et appareil correspondant destinés à réaliser des services de canal de télévision par protocole internet

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09802358

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09802358

Country of ref document: EP

Kind code of ref document: A1