Provide public warning system messages

Abstract

Embodiments of the present disclosure relate to providing a Public Warning System (PWS) message. A method for relaying a PWS message is provided. The method includes a communication device receiving a PWS message via a first communication technology. The method also includes the communication device relaying all or part of the PWS message via a second communication technology, where the second communication technology is different from the first communication technology.

Description

[0001] This application is a divisional application of the invention patent application with international application number PCT / IB2017 / 000842, international application date May 4, 2017, date of entry into the Chinese national phase November 1, 2019, Chinese national application number 201780090296.2, and invention name “Providing Public Warning System Messages”. Background Art

[0002] With the development of telecommunications technology, more advanced network access equipment has been introduced that can provide services that were previously impossible. The network access equipment may include systems and devices that are improvements to equivalent equipment in traditional wireless telecommunications systems. Such advanced network access equipment may be included in evolving wireless communication standards such as Long Term Evolution (LTE). For example, in an LTE system, the advanced network access equipment may include an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (eNB). In various wireless communication systems, the advanced network access equipment may include a base station, a wireless access point, or a similar component that can operate as an access node according to the corresponding wireless communication standard. Any such component will be referred to as an eNB in this article, but it should be understood that such a component is not necessarily an eNB. Such a component may also be referred to as an access node or a base station in this article.

[0003] As used herein, the term "user equipment" (UE) may refer to a mobile device, such as a mobile phone, a personal digital assistant, a handheld or laptop computer, and similar devices with telecommunication capabilities. Such a UE may include a wireless device and its associated Universal Integrated Circuit Card (UICC), which includes a Subscriber Identity Module (SIM) application, a Universal Subscriber Identity Module (USIM) application, or a Removable User Identity Module (R-UIM) application, or may include the device itself without such a card. The term "UE" may also refer to devices with similar capabilities but that are not transportable, such as a landline phone, a desktop computer, or a set-top box. The term "UE" may also refer to any hardware or software component that can terminate a Session Internet Protocol (SIP) session. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] For a more complete understanding of the present disclosure, reference is now made to the following brief description taken in conjunction with the accompanying drawings and detailed description, wherein like reference numerals represent like parts throughout the several views.

[0005] Figure 1 is an example diagram of a security architecture according to an embodiment of the present disclosure.

[0006] Figure 2 An example vehicle-to-everything (V2X) communication system is shown in accordance with an embodiment of the present disclosure.

[0007] Figure 3 and 4 is an example flow chart for relaying a Public Warning System (PWS) message according to an embodiment of the present disclosure.

[0008] Figure 5 is a diagram of an example data structure including configuration information according to an embodiment of the present disclosure.

[0009] Figure 6 is a diagram of an example PWS data structure according to an embodiment of the present disclosure.

[0010] Figure 7-9 A possible example implementation of a PWS data structure according to an embodiment of the present disclosure is shown.

[0011] Figure 10 and 11 A possible example implementation of identifying a PWS message according to an embodiment of the present disclosure is shown.

[0012] Figure 12 A possible example implementation of an Intelligent Transportation System (ITS) Protocol Data Unit (PDU) header according to an embodiment of the present disclosure is shown.

[0013] Figure 13 An example of a PWS header according to an embodiment of the present disclosure is shown.

[0014] Figure 14 is an example flow chart for relaying PWS messages according to an embodiment of the present disclosure.

[0015] Figure 15 A possible example data structure of a Decentralized Environment Notification Message (DENM) according to an embodiment of the present disclosure is shown.

[0016] Figure 16 is a block diagram of an example network element according to one embodiment.

[0017] Figure 17 is a block diagram illustrating an example user device that can be used with the systems and methods in the embodiments described herein.

[0018] Figure 18 An example of a processor and related components suitable for implementing several embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0019] First, it should be understood that although illustrative implementations of one or more embodiments of the present disclosure are provided below, the disclosed systems and / or methods may be implemented using any number of techniques, whether currently known or already existing. The present disclosure should in no way be limited to the illustrative implementations, diagrams, and techniques shown below, including the exemplary designs and implementations shown and described herein, but may be modified within the scope of the appended claims and their full scope of equivalents.

[0020] As used throughout the specification, claims and drawings, the following acronyms have the following definitions. Unless otherwise stated, all terms are defined by and adhere to standards set forth by the 3rd Generation Partnership Project (3GPP) technical specifications or OMA (Open Mobile Alliance).

[0021] 3GPP Third Generation Partnership Project

[0022] AP Access Point

[0023] AS application server

[0024] BSC Base Station Controller

[0025] BTS Base Transceiver Station

[0026] CAM Collaborative Awareness Message

[0027] CBC Cell Broadcast Centre

[0028] CBE Cell Broadcast Entity

[0029] CBM Cell Broadcast Message

[0030] CBS Cell Broadcast Service

[0031] CMAS Commercial Mobile Alert System

[0032] CSCF Call Session Control Function

[0033] DENM Decentralized Environmental Notification Message

[0034] D2D device to device (communication)

[0035] EDGE Enhanced Data Rates for GSM Evolution ePDG Evolved Packet Data Gateway ETWS Earthquake and Tsunami Warning System EU-ALERT European Alert / Warning System E-UTRA(N) Evolved Universal Terrestrial Access(Network) GERAN GSM / EDGE Radio Access Network GGSN Gateway GPRS Support Node GPRS General Packet Radio Service GRUU Global Routing User Agent URI GSM Global System for Mobile Communications HLR Home Location Register HSS Home Subscriber Server IBCF Interconnect Boundary Control Function I-CSCF asks CSCF IP Internet Protocol

[0036] IMS IP Multimedia Subsystem ISIM IP Multimedia Service Identity Module ITS Intelligent Transportation System ITS-AID ITS Application Identifier KPAS Korean Public Alert System LTE Long Term Evolution

[0037] MCS modulation and coding scheme ME Mobile Devices

[0038] MME Mobility Management Entity MSC Mobile Switching Center NR Next Generation Radio Access Technology P-CSCF Proxy CSCF PDN-GW Packet Data Network (PDN) Gateway P-GW Packet Gateway

[0039] PLMN Public Land Mobile Network

[0040] PRB Physical Resource Block

[0041] PSCCH Physical Sidelink Control Channel

[0042] PSSCH Physical Sidelink Shared Channel

[0043] PWS Public Warning System

[0044] RAN Radio Access Network

[0045] RNC Radio Network Controller

[0046] RRC Radio Resource Control

[0047] RSU Road Side Unit

[0048] SBC Session Border Controller

[0049] SCI Side Link Control Information

[0050] S-CSCF Serving CSCF S-GW Service Gateway

[0051] SGSN Serving GPRS Support Node

[0052] SIB System Information Block

[0053] TS Technical Specification

[0054] UE User Equipment

[0055] UMTS Universal Mobile Telecommunications System

[0056] URL Uniform Resource Locator

[0057] USIM Universal Subscriber Identity Module

[0058] UTRA(N) Universal Terrestrial Radio Access(Network)

[0059] V2X Vehicle to Everything

[0060] WLAN Wireless Local Area Network

[0061] WPAS Wireless Public Alerting Service (Canada)

[0062] As used throughout the specification, claims, and drawings, the following terms have the following definitions.

[0063] Broadcast messages: Cell broadcasts may be used to transmit these types of messages, which may include emergency alert messages such as PWS, ETWS, CMAS, WPAS, etc.

[0064] CAM message: A periodically transmitted ITS message containing information about the sender, such as location, movement, and attributes.

[0065] DENM: ITS message, which contains information about hazardous road conditions, such as environmental events or traffic incidents.

[0066] PWS message: can contain PWS, ETSW, CMAS, WPAS, and / or KPAS alert information. PWS messages can be transmitted using cell broadcasts, SIBs, paging messages, etc. In the context of this disclosure, "PWS message," "PWS notification," "PWS warning notification," and "PWS information" can be considered equivalent terms.

[0067] RRC_CONNECTED: When an RRC connection has been established between the UE and a network element (eg, eNB), the UE is in the RRC_CONNECTED state.

[0068] RSU: A communication device that acts as an interface component between a vehicle or other mobile device and roadside equipment infrastructure to support V2X applications. A typical RSU implementation may include an ME or UE, such as a UE-type RSU, which can act as a "UE-to-network relay" or support other relay forms and provide cellular access (e.g., GERAN, UTRAN, E-UTRAN, 5G, etc.) on one side and direct communication (e.g., D2D, PC5, sidelink, etc.) on the other side. A typical RSU implementation may also include an eNB, such as an eNB-type RSU.

[0069] Sidelink: A D2D communication technology used over the 3GPP LTE interface known as PC5. The terms "PC5" and "Sidelink" are used interchangeably unless otherwise specified. Warning Messages: Messages that can provide timely, accurate alerts, warnings, and important information about disasters and other emergencies, such as AMBER Alerts, Presidential Alerts, etc. A warning message may include multiple components or fields populated with various information, such as a description of the event, the geographic area affected by the event, recommended actions, the expiration time of the warning message, the identity of the agency responsible for the warning message, etc. Regulatory requirements may determine the components of a warning message. Examples of warning messages include, but are not limited to, PWS, ETSW, CMAS, WPAS, and KPAS messages.

[0070] I.PWS system and security architecture

[0071] Figure 1 An example block diagram of a PWS system and security architecture 100 is depicted. The architecture 100 may include one or more access networks (e.g., GERAN 105, UTRAN 110, E-UTRAN 115, etc.) and a core network 120. A UE 125 may connect to one or more access networks via a "reference point" or air interface. Figure 1 In the present invention, for example, UE 125 is connected to a BTS in GERAN 105 via a Um air interface; UE 125 is connected to a NodeB in UTRAN 110 via a Uu air interface; and UE 125 is connected to an eNB in E-UTRAN 115 via an LTE-Uu air interface. However, other interfaces between UE 125 and access networks (e.g., GERAN 105, UTRAN 110, E-UTRAN 115, etc.) may exist and may be used to support this reference point and other reference points within architecture 100.

[0072] Figure 1 Each air interface in the PWS (e.g., GERAN Um, UMTS Uu, and LTE-Uu) may include a broadcast interface. The broadcast interface may not have security protections for ensuring data integrity or authentication, because the PWS warning notification message is typically broadcast to the UE 125 via system information or via a paging message, such as in the case of ETWS primary notification for GERAN. In either case, no additional security is applied in the current PWS architecture.

[0073] The core network 120 may include a packet system (PS) core network and / or an IMS network, including one or more nodes, such as an MME 130 and an SGSN / MSC 135. In other implementations, the core network 120 may include additional and / or alternative network nodes or entities, such as, but not limited to, a GGSN, an S-GW, a P-GW, an ePDG, an HSS / HLR, a P-CSCF, an I-CSCF, an S-CSCF, an HSS, an AS, or an SBC / IBCF. The core network 120 also includes a CBC 140 connected to each access network. For example, the CBC 140 may be connected to a BSC in the GERAN 105; the CBC 140 may be connected to an RNC in the UTRAN 110; and the CBC 140 may be connected to an eNB in the E-UTRAN 115 via the MME 130.

[0074] The reference point used between the eNB and the MME 130 is referred to as the "S1-MME" reference point. The reference point used between the BSC and the SGSN / MSC 135 is referred to as the "Gb" reference point, while the reference point used between the RNC and the SGSN / MSC 135 is referred to as the "lu-cs" reference point. However, other interfaces between the access networks (e.g., GERAN 105, UTRAN 110, and E-UTRAN 115) and the core network 120 may exist and may be used to support this reference point and other reference points within the architecture 100.

[0075] CBC 140 may be connected to CBE 145, which is assumed to be responsible for all aspects of formatting CBS messaging, including dividing CBS messages into segments and signing such messages. Figure 1 Only one CBE 145 is shown in FIG. 1 , but in other embodiments, the CBC 140 may be connected to multiple CBEs.

[0076] II. Public Warning System (PWS)

[0077] PWS is used to provide timely and accurate alerts, warnings and critical information about disasters and other emergencies. PWS is currently defined in 3GPP TS 23.041, has no security, and provides a framework for regional emergency services such as KPAS, EU-ALERT, CMAS and ETWS.

[0078] In CMAS or Canadian WPAS, it is possible (but not encouraged) to include an embedded URL or phone number in the alert message. The embedded URL allows users to access a website for more enriched content / functionality to supplement the alert. The information or message encoding used for ETWS differs from that used for other systems. ETWS alerts can be PLMN-wide, cell-wide, or specific to a location, service, or tracking area.

[0079] In E-UTRAN, ETWS warning alerts may be provided via ETWS primary notifications and / or ETWS secondary notifications. In E-UTRAN, CMAS warning alerts may be provided via CMAS notifications. Similar air interface mechanisms are used to indicate the presence of different types of warning alert notifications, i.e., a paging message may include an ETWS indication or a CMAS indication. Upon receiving such a paging message, a UE (e.g., UE 125) may need to receive a first system information block (e.g., SIB1) to detect another SIB (e.g., SIB10, SIB11, or SIB12) containing an ETWS notification or a CMAS notification. Based on SIB1, the UE may determine whether the other SIB is one of SIB10 (carrying ETWS primary notifications), SIB11 (carrying ETWS secondary notifications), or SIB12 (carrying CMAS notifications). The time it takes for the UE to receive SIB10 may be almost the same as the time it takes for the UE to receive SIB11 or SIB12.

[0080] In UTRAN / GERAN, the primary notification is sent in a paging message, while the secondary notification is sent in a CBM, which may be delayed by up to a minute due to discontinuous reception (DRX). In this way, the primary notification can be delivered relatively faster than the secondary notification.

[0081] Each PWS message has an identifier, such as a sequence number, so that the UE can distinguish different PWS messages that have been received. As part of the identifier or sequence number, multiple bits (eg, 2 bits) can be used to indicate the geographical scope of the message.

[0082] III. Vehicle-to-Everything (V2X)

[0083] V2X is a service (or set of services) that allows vehicles to communicate with pedestrian UEs, other vehicles, or infrastructure (and vice versa) to exchange useful information so that vehicles and pedestrians can safely traverse the road network. V2X utilizes the Proximity Services (ProSe) architecture defined in 3GPP TS 23.303, which has aspects specific to V2X technology specified in 3GPP TS 23.285. One such aspect includes relay entities, which can be used as RSUs in the V2X architecture.

[0084] Figure 2 An example architecture 200 based on V2X technology is depicted. In this architecture 200, UEs 205A, 205B, 205C, and 205D (collectively, 205) can communicate with one or more other UEs 205 (including a UE-type RSU 210) in proximity to one another via a PC5 interface, which can be used to transmit and receive V2X messages. The UE-type RSUs 210 can communicate with one or more V2X application servers 215 via an LTE-Uu interface as needed, for example, to manage the communication of V2X messages beyond the range of direct PC5 communication. While the V2X application servers 215 are depicted in an Evolved Packet Core (EPC) network, the V2X application servers 215 can be deployed in any suitable network. It will also be appreciated that this diagram represents an LTE network, but is equally applicable to 5G systems, where there is one interface from the UE 205 to the RSU 210 and another interface from the RSU 210 to the core network via a base station.

[0085] IV. D2D / Sidelink Communication

[0086] Sidelink communication allows authorized UEs to communicate with other UEs or radio equipment (e.g., RSUs or relays) when, for example, there is no cellular coverage, or to avoid using radio resources in the licensed spectrum or exhausting the traffic capacity of the cellular network. This is achieved by using direct communication between UEs or between a UE and another radio equipment. Sidelink communication is typically performed over a radio interface called a PC5 interface. UEs that are not within the coverage area of an infrastructure or network or are not directly connected to the infrastructure or network can also communicate with the infrastructure or network through an RSU or relay using sidelink communication.

[0087] The UE can identify that a message received via the sidelink is for a particular V2X application based on the destination Layer 2 ID used for the message. Although the Layer 2 ID code point value may not be defined in the 3GPP specification, 3GPP TS 23.285 specifies that a Layer 2 ID be configured to the UE for V2X communication over the PC5 interface.

[0088] V. Sidelink communication for V2X

[0089] Regarding ProSe sidelink communication, V2X sidelink transmission / reception is based on a resource pool that can be pre-configured in the UE (e.g., resources that can be used when the UE is out of coverage), configured by Uu broadcast (e.g., system information message), or configured by Uu dedicated information (e.g., connected mode signaling).

[0090] Certain resource pools can only be used under certain conditions. For example, some resource pools can be associated with a geographic location, while exceptional resource pools can be used during mobility between cells or geographic areas. The resources in a pool can be defined in terms of allowed subframes (offsets, bitmaps) and frequencies (e.g., PRBs).

[0091] In addition, sidelink transmissions can be subject to resource sensing, transmission parameters (such as MCS, number of PRBs, number of retransmissions), UE-specific parameters (e.g., depending on UE absolute speed), and synchronization reference type (i.e., Global Navigation Satellite System (GNSS), eNB, or UE) when UE autonomous resource selection is performed. Transmission events such as the transmission of V2X messages can involve a control portion (e.g., SCI) transmitted in the PSCCH and an associated data portion transmitted in the PSSCH. The PSCCH and associated PSSCH can appear in the same subframe or in different subframes.

[0092] SCI format 1, defined for V2X sidelink communications, contains information for correctly processing the corresponding data portion. Such information may include priority, frequency resource location, time interval before retransmission, and MCS. Note that SCI format 0 is used for ProSe sidelink communications.

[0093] A UE supporting V2X sidelink communication can operate in one of two resource allocation modes. The first mode can be described as network-scheduled resource allocation (or sidelink mode 3), in which the UE needs to be in the RRC_CONNECTED state in order to transmit data. When operating in network-scheduled resource allocation mode, the UE requests transmission resources from the eNB, which schedules such resources for the transmission of sidelink control information and data.

[0094] The second mode can be described as autonomous resource selection (or sidelink mode 4), in which the UE can autonomously select resources from the resource pool and perform transmission format selection to transmit sidelink control information and data. If the mapping between the area and the V2X sidelink transmission resource pool is configured, the UE will select the V2X sidelink resource pool according to the area in which the UE is located. When operating in autonomous resource allocation mode, the UE can perform sensing to select (or reselect) sidelink resources. Based on the sensing results, the UE can select (or reselect) some specific sidelink resources, and multiple sidelink resources can be reserved. The UE is allowed to perform up to two parallel independent resource reservation processes. The UE is also allowed to perform a single resource selection for its V2X sidelink transmission.

[0095] VI. V2X Application Layer

[0096] The V2X application layer transmits information between various V2X applications that may reside in cars, roadside units, or pedestrian devices. The European Telecommunications Standards Institute (ETSI) has defined ITS, which covers the message framework that can be sent and received by these different entities. Messages are divided into different types, including CAM and DENM. CAM is a message that is transmitted periodically and contains information about the sender, such as but not limited to location, dynamics, and attributes. DENM is a message that can contain, but is not limited to, information about road hazards (e.g., environmental events or traffic events). Additional details about CAM and DENM can be found in ETSI EN302 637-2 and ETSI EN 302 637-3, respectively.

[0097] As previously mentioned, cellular networks can deliver broadcast information, such as PWS messages used in emergency situations such as earthquakes, tornadoes, etc. Under the current PWS architecture, the delivery of such information is limited to devices such as smartphones residing on the cellular network (e.g., UEs). However, it is expected that some devices will not be directly connected to the network, but will use D2D communications, for example, through a relay entity. An example may include a car that uses D2D to communicate with road traffic infrastructure as a relay entity of the network. The types of these cars may include, but are not limited to, cars with pre-installed V2X functionality based on sidelink communication, or conventional cars with after-sales sidelink V2X functional modules installed (e.g., non-native V2X cars). Since the transmission of PWS via sidelink is not yet specified in the existing standards, such devices (e.g., cars equipped with V2X or on-board UEs in cars) cannot receive PWS messages.

[0098] Nevertheless, it is desirable for the vehicle to take into account certain information, such as traffic alerts (e.g., a nearby road is flooded), weather alerts (e.g., a severe tornado is approaching), traffic information, or crime reports (e.g., an accident associated with a car with license plate "XYZ"). This information can be used by the car's system itself to adjust the car's behavior. For example, upon receiving an alert reporting icy road conditions, the car's system can cause the car to activate a towing mechanism, consider an alternative route, improve overall safety, and so on.

[0099] Additionally, because V2X-equipped cars can use sidelinks to broadcast data, a car can receive communications from other cars within its radio coverage area. However, existing V2X applications do not allow a V2X-equipped car to relay or rebroadcast PWS information received from a cellular network to other cars in the vicinity of the V2X-equipped car.

[0100] VII. Relaying PWS information received from the cellular network

[0101] The embodiments disclosed herein address the limitations discussed above with respect to existing V2X applications. In one embodiment, a UE is configured to receive a PWS message from a network node. Upon receiving the PWS message, the UE may determine whether any rules apply based on the policy associated with the PWS message. The UE may then relay the PWS message to a remote UE, subject to the policy. If the PWS message includes a primary PWS notification, the UE may repeat the above process upon receiving a secondary PWS notification associated with the primary PWS notification.

[0102] The steps associated with the above process are Figure 3 300 . In block 302, a network node 310 (such as, but not limited to, a NodeB, an eNB, a BTS, a BSC, an RNC, an access point, or any combination thereof) sends a PWS message containing PWS information. The PWS information may be contained in a SIB, a paging message, a CBM (any of which may also be referred to as a broadcast message in the remainder of this specification), or a combination thereof. In block 304, the PWS message is received by a communication device 320, which may include any suitable device capable of communication, such as, but not limited to, a user equipment (UE), a mobile station, a relay UE, an RSU, a network node (e.g., similar to the network node 310), etc.

[0103] In an embodiment, the UE 320 may be configured to communicate using two or more different technologies. For example, the UE 320 may be configured to communicate with a telecommunications network using a cellular technology such as, but not limited to, mobile / cellular (e.g., CDMA2000, GSM / GPRS / EDGE, UMTS / UTRA, LTE / E-UTRA, etc.) or a new generation radio access technology such as NR. Mobile cellular technologies such as CDMA2000, GSM / GPRS / EDGE, UMTS / UTRA, and LTE / E-UTRA may alternatively be designated by a corresponding RAN type, such as, for example, CDMA2000 RAN, GERAN, UTRAN, E-UTRAN, or a new generation RAN. These mobile cellular technologies may sometimes be designated by a technology generation number, such as "2G" (second generation) mobile cellular technology, "3G" (third generation) mobile cellular technology, "4G" (fourth generation) mobile cellular technology, "5G" (fifth generation) mobile cellular technology, etc. UE 320 may also be configured to communicate with other UEs using alternative technologies such as, but not limited to, PC5 / sidelink, D2D, V2X, / WLAN (e.g., IEEE 802.11-based technologies), Bluetooth, Near Field Communication (NFC), WiMAX, wireless charger, Ethernet, cable modem, Digital Subscriber Line (DSL), fiber optic, Universal Serial Bus (USB), and wireless.

[0104] After receiving a PWS message and before taking further action, the UE 320 may consult a policy to determine if there are any restrictions on processing the PWS message. For example, the policy may specify one or more of the following rules: (a) the UE is only allowed to relay PWS messages via a certain interface (e.g., a PC5 interface, a technology, a frequency band within a technology, or other suitable interface that supports D2D communication); (b) the UE is only allowed to relay PWS messages if the PWS message is a certain type of broadcast message (e.g., an Amber Alert, a Presidential Alert, an Earthquake Alert, a Tsunami Alert, etc.); or (c) the UE will relay a portion of the PWS message based on the technology on which the PWS is received. In some implementations, one or more of these rules may be optional.

[0105] At operation 306, UE 320 relays (e.g., transmits or broadcasts) the PWS message according to the rules discussed above. At operation 308, the PWS message relayed by UE 320 is received by remote UE 330, which may not utilize a cellular connection to communicate with UE 320. In some aspects, UE 320 may be provided with configuration information including a destination Layer 2 ID, which may be provided internally to UE 320 via a SIM card, an application on a UICC, via a network interface, or via any other suitable means. UE 320 may then associate the destination Layer 2 ID with the PWS message (or other suitable type of warning message, e.g., a warning message now known or later developed) received at block 304 based on the configuration information and relay the PWS message accordingly at operation 306. If the PWS message sent at block 302 includes a primary PWS notification, flow chart 300 may be repeated when network node 310 sends another PWS message including a secondary PWS notification associated with the primary PWS notification. In some embodiments, the secondary PWS notification may include an explanatory text component, such as information describing the location of the emergency identified in the primary PWS notification, information describing the severity of the emergency identified in the primary PWS notification, updates regarding the emergency identified in the primary PWS notification, and the like.

[0106] The following discussion provides some information on the above Figure 3 Additional details of the described embodiments. For clarity, it should be understood that within the scope of the present disclosure, any embodiment disclosed herein can be combined with any one or more other embodiments disclosed herein to create new embodiments. It should also be understood that although the following discussion may focus on embodiments involving motor vehicles, the disclosed embodiments are similarly applicable to any device capable of communicating with a network, such as mobile phones, smart watches and wearable devices, and smart appliances such as refrigerators, washers and dryers, ovens, stoves, heating and cooling systems, coffee makers, alarm systems, washing machines, dishwashers, etc.

[0107] VIII. Relaying PWS information received on the cellular network via short-range technology as a specific PWS message service

[0108] Figure 4An example flow chart 400 for relaying PWS information according to an embodiment of the present disclosure is depicted. At operation 402, network node 310 transmits a broadcast message including a PWS notification to relay UE 320 via a first telecommunication technology network type (such as GERAN, UTRAN, E-UTRAN, next-generation RAN, etc.). In some implementations, the broadcast message may convey the PWS notification information via any of the following: a warningType information element (IE); a warningMessageSegment IE, such as defined in 3GPP TS 36.331; one or more other IEs; or any combination thereof. In some implementations, the broadcast message transmitted at operation 402 may convey a notification from another alerting system, such as, but not limited to, KPAS or EU-ALERT.

[0109] In some implementations, the relay UE 320 may be configured to determine whether the relay UE 320 is permitted to receive and / or relay warning messages or some or all of their contents. For example, a policy may be provided to the relay UE 320 that includes configuration information used by the relay UE 320 to determine what actions, if any, the relay UE 320 may perform with respect to the warning message. Non-limiting examples of such configuration information 500 are provided in Figure 5 In other aspects, the configuration information 500 may include additional and / or alternative access conditions, data items, encodings, etc.

[0110] The configuration information 500 may include an elementary file (EF) 510 indicating services available with respect to PWS messages. The EF 510 includes a plurality of fields, such as a file identifier (e.g., "6Fxx"), a structure field describing the structure of the EF (e.g., transparent, circular, linear fixed, or linear variable), a status field (e.g., optional (O), mandatory (M), or conditional (C)), a file size field indicating the size of the EF, an update activity field (e.g., low or high), etc. The EF 510 also includes a set of access conditions, such as read, update, active, and inactive.

[0111] If it is determined that the relay UE 320 is allowed to receive and / or relay warning information (e.g., based on the configuration information 500), the relay UE 320 may activate a feature to facilitate the reception of broadcast messages containing PWS notifications, etc. In some implementations, the relay UE 320 may be configured to receive and send such messages by default. For the purposes of this discussion, it may be assumed that the relay UE 320 is so allowed / configured, and therefore, at operation 402, the broadcast message sent by the network node 310 is received by the relay UE 320.

[0112] After receiving the broadcast message, relay UE 320 may consult configuration information 500 to determine whether relay UE 320 is allowed to access the content of the broadcast message. Configuration information 500 may also include one or more bytes of encoding information 520, where one or more bits in the first byte may be used to determine whether the broadcast message can be relayed.

[0113] For example, if the first bit "b1" is set to "0" or "1," the relay UE 320 may be configured to relay or ignore all PWS messages received in the home PLMN (HPLMN) and equivalent PLMN, respectively. Similarly, if the second bit "b2" is set to "0" or "1," the relay UE 320 may be configured to relay or ignore all PWS messages received in the visited PLMN (VPLMN), respectively. In other aspects, the encoded information 520 may include additional and / or alternative bits. If the relay UE 320 is configured to ignore all PWS messages in the HPLMN (e.g., "b1" = "1") or the VPLMN (e.g., "b2" = "1"), the relay UE 320 simply does not receive the warning message, in which case the broadcast message is not received in operation 402.

[0114] As previously described, each PWS message may have a sequence number for distinguishing different PWS messages. Each PWS message may also have a message identifier that identifies the source of the PWS message. Therefore, upon receiving a broadcast message including a PWS notification, the relay UE 320 may use such information to determine whether the relay UE 320 has received the PWS notification more than once. If so, the relay UE 320 may silently discard the PWS notification. In some embodiments, the broadcast message received at operation 402 may include a parameter indicating that the PWS notification is a specific type of warning message.

[0115] For example, assuming that the broadcast message from the network node 310 conveys a PWS notification in an ETWS IE, the broadcast message may include a warning type parameter indicating that the PWS notification corresponds to an earthquake, a tsunami, a test sent for testing purposes, etc. If the warning type parameter indicates that the PWS notification is a test, the relay UE 320 may be configured to silently discard the PWS notification. Otherwise, the relay UE 320 may proceed to block 404 and generate a first PWS output message, which may be used to relay (in operation 406) the PWS notification via a communication technology different from the communication technology via which the broadcast message was received in operation 402.

[0116] In some embodiments, the content of the PWS outbound message generated at block 404 may depend on the manner in which the PWS notification is transmitted in the broadcast message received at operation 402. For example, assuming that the PWS notification is transmitted in an ETWS IE as described above, the relay UE 320 may format the PWS outbound message to include one or more parameters included in the ETWS IE. In some implementations, the relay UE 320 may format the PWS outbound message to include an optional "rebroadcast indication" parameter (e.g., a rebroadcast flag).

[0117] Figure 6 One possible implementation of a data structure 600 including the content of the PWS outgoing message generated at block 404 is depicted. The "Alert Type" 605 and "Sequence Number" 615 parameters may be received in an ETWS IE. If the PWS message corresponds to an ETWS primary notification, the data structure 600 may include a "Message Identifier" 610 that identifies the source of the ETWS primary notification message. In other implementations, the content of the PWS outgoing message may be included in an Extensible Markup Language (XML) data structure.

[0118] In some embodiments, Figure 6 The data structure 600 in may be modified according to the type of radio access technology (RAT) through which the relay UE 320 receives the broadcast message at operation 402. For example, Figure 7 One possible implementation of data structure 700 is depicted. If the broadcast message is received via GERAN at operation 402, data structure 600 may be modified to data structure 700. Figure 8 depicts one possible implementation of a data structure 800 , into which the data structure 600 may be modified if the broadcast message is received via the UTRAN at operation 402 ; and Figure 9 One possible implementation of data structure 900 is depicted, and data structure 600 may be modified to data structure 900 if the broadcast message is received via E-UTRAN or next-generation RAN at operation 402. In other implementations, data structure 600 may be modified according to any suitable telecommunication technology.

[0119] At operation 406, the relay UE 320 may send a PWS outgoing message containing a PWS notification via the PC5 interface. However, it should be understood that in other examples, the PWS message may be sent via other suitable interfaces, such as interfaces designed for short-range communication technologies (e.g., Dedicated Short Range Communication (DSRC), IEEE 802.11p, Bluetooth, WLAN, etc.). At operation 408, the remote UE 330 receives the PWS message, for example, via the PC5 interface.

[0120] In some embodiments, the relay UE 320 may be configured to determine whether a secondary notification is available. For example, if the PWS notification transmitted by the original broadcast message at operation 402 corresponds to an ETWS primary notification, then at operation 410, the network node 310 may send a second broadcast message containing an EWTS secondary notification related to the ETWS primary notification to the relay UE 320. In other examples, the broadcast message sent at operation 410 may contain a PWS notification that is different from an EWTS secondary notification.

[0121] The relay UE 320 may receive the second broadcast message including the PWS notification via the first telecommunication technology. For example, if the first telecommunication technology network type includes GERAN or UTRAN, the relay UE 320 may receive the PWS notification via CBM. Alternatively, if the first telecommunication technology network type includes E-UTRAN, the relay UE 320 may receive the PWS notification via a SIB (e.g., SIB11).

[0122] At block 412, the relay UE 320 may generate a second outbound PWS message containing the PWS notification received at operation 410. The second outbound PWS message may include a data structure similar to data structure 600. Similar to the first outbound PWS message, the data structure of the second outbound PWS message may be modified based on the first telecommunication technology (e.g., according to data structures 700, 800, and 900) over which the broadcast message was received at operation 410. Additionally or alternatively, the second PWS message may be modified based on the content of the broadcast message itself.

[0123] Similar to the first PWS output message, the relay UE 320 may format the data structure of the second PWS output message based on the first telecommunication technology via which the broadcast message is received. Thus, if the broadcast message is received via GERAN, the relay UE 320 may format the data structure of the second PWS output message based on the data structure 700. In an embodiment, the relay UE 320 may be configured to modify the data structure of the second PWS output message based on examining the "message identifier" 610 within the broadcast message received at operation 410.

[0124] For example, the data structure of the second PWS output message may be modified such that: (i) if the received PWS message identifier 610 is included in the first set of values (eg, "1100 Hex" and "1107 Hex"), the relay UE 320 may Figure 7 The "Data Coding Scheme" parameter 715 in the broadcast message is set to a predetermined value (e.g., "101"), and the content starting from the received broadcast message "Sequence Number" 705 is included in the PWS output message (e.g., Figure 7(ii) if the received PWS message identifier 610 is included in the second set of values (e.g., “1112 (Hex)” and “112B (Hex)”), the relay UE 320 may set the “data encoding scheme” parameter 715 to another predetermined value (e.g., “102”), and include the contents of the broadcast messages received starting from “sequence number 705” in the PWS output message (e.g., as shown in FIG. 6 ); Figure 7 shown).

[0125] If the broadcast message is received through the UTRAN at operation 410, the relay UE 320 may format the data structure of the second PWS output message according to the data structure 800. In an embodiment, the relay UE 320 may modify the data structure of the second PWS output message based on the "message identifier" 610 in the broadcast message received at operation 410. For example, the data structure of the second PWS output message may be modified such that: (i) if the received PWS message identifier 610 is included in the first group of values (e.g., "1100 (Hex)" and "112B (Hex)"), the relay UE 320 may modify the data structure of the second PWS output message. Figure 8 The "Data Coding Scheme" parameter 820 in the PWS is set to a predetermined value (e.g., "103"), and the contents of the broadcast message received starting from "Message Type" 805 are included in the PWS output message (e.g., message type 805, message identifier 810, sequence number 815, data coding scheme 820, and cell broadcast (CB) data 825, as shown in FIG. Figure 8 shown).

[0126] If the broadcast message is received through the E-UTRAN at operation 410, the relay UE 320 may format the data structure of the second PWS output message according to the data structure 900. In an embodiment, the relay UE 320 may modify the data structure of the second PWS output message based on the "message identifier" 610 in the broadcast message received at operation 410. For example, the data structure of the second PWS output message may be modified such that: (i) if the received PWS message identifier is included in the first group of values (e.g., "1100 (Hex)" and "1107 (Hex)"), the relay UE 320 may modify the data structure of the second PWS output message based on the "message identifier" 610 in the broadcast message received at operation 410. Figure 9 The "Data Coding Scheme" parameter 920 in the PWS is set to a predetermined value (e.g., "104"), and the content of the broadcast message received starting from the "Message Identifier" 905 is included in the PWS output message (e.g., Figure 9(ii) if the received PWS message identifier is included in the second set of values (e.g., “1112 (Hex)” and “112B (Hex)”), the relay UE 320 may set the “data encoding scheme” parameter 920 to another predetermined value (e.g., “105”), and include the content of the broadcast message received starting from the “message identifier” 905 in the PWS output message (e.g., as shown in FIG. 1 ); Figure 9 shown).

[0127] Additionally or alternatively, the relay UE 320 may modify the data structure of the second PWS output message based on the "Sequence Number" parameter 615 included in the broadcast message received in operation 410. For example, if the geographic scope of the "Sequence Number" parameter 615 indicates that the geographic area of the PWS message is throughout the PLMN, the relay UE 320 may set the "Rebroadcast" parameter in the data structure of the second PWS output message to "True." In some implementations, it can be inferred that setting the "Rebroadcast" parameter to "True" indicates that the PWS message can be rebroadcast regardless of the geographic area.

[0128] In some embodiments, the geographic scope of the "sequence number" parameter 615 may indicate that the geographic region of the PWS message is specific to a unique region. In this case, the relay UE 320 may modify the data structure of the second PWS output message to indicate that the PWS message is only applicable within a specific geographic region.

[0129] After completing the data structure of the second PWS output message, the relay UE 320 may proceed to send the second PWS output message containing the PWS notification via the PC5 interface, as shown in operation 414. In other implementations, the second PWS output message may be sent via any suitable interface, such as previously mentioned with respect to the first PWS output message sent at operation 406.

[0130] At operation 416, the remote UE 330 receives the second PWS output message containing the encoding described above. In an embodiment, the remote UE 330 may then display a notification on the screen and / or generate an audible alarm to notify the user of the remote UE 330 of the second PWS output message. Additionally or alternatively, the remote UE 330 may rebroadcast the data received in the second PWS output message. For example, if the second PWS output message contains a rebroadcast flag set to "true," the remote UE 330 may rebroadcast the data in a subsequent PC5 message. However, the remote UE 330 may set the rebroadcast flag in the subsequent PC5 message to "false."

[0131] In an embodiment, the relay UE 320 may be configured to continue to perform the above functions whenever the relay UE 320 receives a warning message (eg, a broadcast message containing a primary PWS notification or a secondary PWS notification) from the network node 310 .

[0132] In some embodiments, relay UE 320 (or its functionality) may be combined with network node 310. In such embodiments, the total number of blocks or operations in flowchart 400 may be reduced because any tasks that would otherwise be performed by relay UE 320 may be performed by network node 310, which may communicate directly with remote UE 330 via a PC5 interface (or other suitable interface).

[0133] In an embodiment, the relay UE 320 may be configured to provide an indication that the message sent via the PC5 interface (e.g., the first PWS message and the second PWS message in operations 406 and 414) contains a PWS message. For example, such an indication may be provided using a specific ITS application identifier (ITS-AID) that may be assigned to a PWS service (or derivative technology). Figure 10 One possible implementation of how to indicate a PWS message is depicted using an ITS-AID such as that shown underlined.

[0134] As another example, the relay UE 320 may provide an indication that a message sent via the PC5 interface contains a PWS message using a destination Layer 2 ID that may be assigned to a PWS application via the V2X sidelink interface. In this example, the portion containing the PWS data may be transmitted as V2X information via the PSSCH and may contain corresponding PWS messages. The Layer 2 ID may be configured in the internal memory of the ME (e.g., via OMA Data Management (DM)) or stored on the UICC / USIM / ISIM of the UE (e.g., the relay UE 320 and the remote UE 330). Figure 11 A possible implementation of configuration information 1100 indicating how a destination layer 2 ID may be used to indicate a PWS message is depicted. In this embodiment, the ME reads the EF RelayPWSLayer2id To determine which second layer ID is used for the PWS message. The relay UE 320 can Figure 4 The second layer ID is used in operations 406 and 414 as shown. The remote UE 330 will use the second layer ID from the data stored in the internal memory (e.g., Figure 17 The UICC reads the EF in the random access memory (RAM) 3226, flash memory 3224 or SIM / RUIM interface 3244) RelayPWSLayer2id After receiving the message via PC5, for example, Figure 4At operations 408 and 416, the remote UE 330 reads the second layer ID, and if it matches the second layer ID stored in the ME memory (e.g., RAM 3226, flash memory 3224, or SIM / RUIM interface 3244), the ME knows that it has received the PWS message.

[0135] In an embodiment, a PWS message identifier may be defined as a specific message type that may be transmitted as part of an ITS PDU header. Figure 12 A possible implementation is depicted in which a PWS message identifier can be defined as a specific message type transmitted as part of the ITS PDU header as specified by Annex "A.114DF_ItsPduHeader" in ETSI TS 102 894-2 V1.2.1 (2014-09) (which is incorporated herein by reference with changes indicated by underlining). In this way, PWS messages can not only coexist with different or other ITS / V2X messages on a given interface, but can also be used simultaneously as part of different services (for example, PWS can be received as part of a Decentralized Environment Notification (DEN) service).

[0136] In an embodiment, if different PWS message subcategories are specified or defined (e.g., based on the first cellular technology from which the PWS message originates), an application layer indicator may be provided. For example, the application layer indicator may take the form of a byte containing a code point or value representing the first (source) cellular technology network type (e.g., GERAN, UTRAN, E-UTRAN, etc.). Figure 13 Depicts a possible implementation where ETSI TS 102 894-2 V1.2.1 may be extended to include coding to identify the source of a PWS message (e.g., such as in Figure 4 For example, the first field may carry an indicator identifying a first cellular technology, and the second field may carry a PWS message encoded according to the first cellular technology identified by the indicator. In an example, if the RSU receives the PWS message over GERAN, the message, when sent over PC5, will result in the following encoding: Source Technology (GERAN) with a value of 1 and a second field containing a PWS message encoded according to the first cellular technology identified by the indicator. Figure 7 PWS message (GERAN) of the encoded PWS message.

[0137] In an embodiment, the resource pool may include a general pool for combined V2X services, or a pool dedicated to PWS services. In addition, the pool configuration (e.g., resource size and periodicity) and transmission parameters may be adapted according to the PWS specification.

[0138] VIII. Relaying PWS information received on the cellular network via short-range technology in existing V2X services

[0139] Figure 14 A flowchart 1400 for relaying PWS information according to another embodiment of the present disclosure is depicted. At operation 1402, the network node 310 sends a first broadcast message including a PWS notification to the relay UE 320 via a first telecommunication technology network type such as GERAN, UTRAN, E-UTRAN, etc. Figure 4 The broadcast message may be similar to the broadcast message sent in operation 402 of FIG. In some implementations, the broadcast message may convey notifications from other alert systems, such as, but not limited to, KPAS or EU-ALERT.

[0140] In addition, the relay UE 320 may be configured in the same manner as described above with respect to Figure 4 The configuration information 500 is utilized in a similar manner as described above. Based on such configuration information 500, the relay UE 320 may determine that it is allowed to receive and / or relay the warning information sent at operation 1402. The relay UE 320 may also determine that it is allowed to receive and / or relay the warning information sent at operation 1402. Figure 4 The PWS message is ignored under similar conditions as described (eg, when the PWS message is received more than once, when the PWS message corresponds to a test, when the PWS message should be ignored, etc.).

[0141] At block 1404, the relay UE 320 may generate a first outbound PWS message that may be used to relay the PWS notification via a different communication technology than the communication technology used to receive the broadcast message at operation 1402. In one implementation, the first outbound PWS message generated at block 1404 may be used to relay the PWS notification via a different communication technology than the communication technology used to receive the broadcast message at operation 1402. Figure 4 4. The PWS message generated at block 404 of FIG. 14 is substantially similar, i.e., the PWS message may include a "warning type" parameter 605, a "sequence number" parameter 615, and an optional "rebroadcast indication" parameter (not shown). Additionally or alternatively, the formatting of the first PWS output message generated at block 1404 may depend, at least in part, on a "message identifier" 610 included in the broadcast message received at operation 1402.

[0142] In another implementation, a first PWS output message may be generated at block 1404 whose content includes an ETWS IE (e.g., if received), and a “data encoding scheme” parameter may be set to a value that depends on the first communication technology over which the broadcast message was received at operation 1402. For example, if the broadcast message is received over GERAN at operation 1402, the relay UE 320 may set the data encoding scheme parameter to the value of the first communication technology over which the broadcast message was received at operation 1402. Figure 7The "data coding scheme" parameter 715 in the relay UE is set to a first value (eg, "102"); if a broadcast message is received through the UTRAN at operation 1402, the relay UE 320 may Figure 8 The "data coding scheme" parameter 820 in the relay UE is set to a second value (eg, "103"); and if a broadcast message is received through the E-UTRAN at operation 1402, the relay UE 320 may Figure 9 The “Data Coding Scheme” parameter 920 in is set to a third value (eg, “105”).

[0143] Figure 15 One possible implementation of a data structure 1500 including the contents of the first PWS outbound message generated at block 1404 is depicted. Data structure 1500 corresponds to the DENM format defined by ETSI TS 102 637-3 V1.1.1 (2010-09), with suggested changes underlined. At operation 1406, relay UE 320 transmits the first PWS outbound message, which is then received by remote UE 330, wherein the PWS message is transmitted as a DENM via a different communication technology than the communication technology used to receive the broadcast message at operation 1402. In an embodiment, the different communication technology via which the DENM is transmitted includes a V2X transmission technology.

[0144] As previously described, the relay UE 320 may be configured to determine whether a second warning message is available after transmitting the PWS message at operation 1406. For example, at operation 1408, the network node 310 may send a second broadcast message containing a PWS notification (e.g., a secondary notification related to the PWS notification received in the broadcast message at operation 1402, or a new warning notification) to the relay UE 320a. If the first telecommunication technology network type includes GERAN or UTRAN, the relay UE 320 may receive the PWS notification via CBM. Alternatively, if the first telecommunication technology network type includes E-UTRAN, the relay UE 320 may receive the PWS notification via a SIB (e.g., SIB11).

[0145] At block 1410, the relay UE 320 may generate a second PWS output message containing the PWS notification received at operation 1408. The second PWS output message may include a data structure similar to data structure 600, and the data structure may be modified based on the first telecommunication technology (e.g., according to data structures 700, 800, and 900) over which the broadcast message was received at operation 1408. Additionally or alternatively, the data structure of the second PWS output message may be modified based on the content of the broadcast message itself.

[0146] If the broadcast message is received via GERAN at operation 1408, the relay UE 320 may format the data structure of the second PWS message according to the data structure 700. In an embodiment, the relay UE 320 may be configured to modify the data structure of the second PWS output message based on examining the “message identifier” 610 within the broadcast message received at operation 1408. For example, if the broadcast GES message is received via GERAN, the relay UE 320 may examine the message identifier 610 and modify the data structure of the second PWS message such that: (i) if the message identifier is included in the first set of values (e.g., “1100Hex” and “112BHex”), the relay UE 320 may modify the “data encoding scheme” parameter (e.g., “data encoding scheme”) to include the first set of values. Figure 7 The data encoding scheme 715 in the example is set to a first value (e.g., "101"), and the content of the received broadcast message (e.g., from Figure 7 In an embodiment, the content of the broadcast message received at operation 1408 may be included in the PWS output message. Figure 7 The "content of the message" field 725 is shown.

[0147] If the broadcast message is received via UTRAN at operation 1408, the relay UE 320 may format the data structure of the second PWS output message according to the data structure 800. In an embodiment, the relay UE 320 may be configured to modify the data structure of the second PWS output message based on checking the “message identifier” 610 within the broadcast message received at operation 1408. For example, if the broadcast message is received via UTRAN, the relay UE 320 may check the message identifier 610 and modify the data structure of the second PWS output message such that: (i) if the message identifier is included in the first group of values (e.g., “1100 (Hex)” and “112B (Hex)”), the relay UE 320 may set the “data encoding scheme” parameter (e.g., “1100 (Hex)” and “112B (Hex)”) to “112B (Hex)”; Figure 8 The data encoding scheme 820 in the example is set to a first value (e.g., "101"), and the content of the received broadcast message (e.g., from Figure 8 In an embodiment, the content of the broadcast message received at operation 1408 may be included in the output PWS message. Figure 8 The “CB Data” field 825 is shown.

[0148] If the broadcast message is received through the E-UTRAN at operation 1408, the relay UE 320 may format the data structure of the second PWS output message according to the data structure 900. In an embodiment, the relay UE 320 may be configured to modify the data structure of the second PWS output message based on checking the "message identifier" 610 within the broadcast message received at operation 1408. For example, if the broadcast message is received through the E-UTRAN, the relay UE 320 may check the message identifier 610 and modify the data structure of the second PWS output message such that: (i) if the message identifier is included in the first group of values (e.g., "1100 (Hex)" and "112B (Hex)"), the relay UE 320 may set the "data encoding scheme" parameter (e.g., "1100 (Hex)" and "112B (Hex)") to "112B (Hex)". Figure 9 The data encoding scheme 920 in the embodiment is set to a first value (e.g., "101"), and the content of the received broadcast message (e.g., from Figure 9 In one embodiment, the content of the broadcast message received at operation 1408 may be included in the PWS output message. Figure 9 In the “CB Data {Warning Message Content E-UTRAN}” field 915 shown.

[0149] At operation 1412, the relay UE 320 transmits a second PWS output message, which is further received by the remote UE 330, wherein the second PWS output message is transmitted as a second DENM via a communication technology different from the communication technology used to receive the broadcast message at operation 1408. In an embodiment, the different communication technology via which the second DENM is transmitted includes a V2X transmission technology.

[0150] In some embodiments, the relay UE 320 may determine that the geographic area of a particular PWS message (e.g., such as received at operations 1402 or 1408) is across the PLMN. In such a case, the relay UE 320 may send an indication to the remote UE 330 via a different communication technology to indicate that the PWS message may be rebroadcasted. In one implementation, the relay UE 320 may use a rebroadcast flag in the PWS message to provide such an indication. Upon receiving such an indication, the remote UE 330 may determine to rebroadcast the PWS message in a subsequent V2X message.

[0151] In an embodiment, the relay UE 320 may be configured to continue to perform the above-described functions whenever the relay UE 320 receives a warning message (e.g., a broadcast message containing a primary or secondary PWS notification) from the network node 310. In some embodiments, the relay UE 320 (or its functions) may be combined with the network node 310, such as previously described with respect to the flowchart 400.

[0152] The various methods or operations described herein may be implemented by network elements. Figure 16 Example network elements are shown. Figure 16 In the embodiment, the network element 3110 includes a processor 3120 and a communication subsystem 3130, wherein the processor 3120 and the communication subsystem 3130 cooperate to perform the methods or operations described previously.

[0153] In addition, various methods or operations described herein may be implemented by a communication device (eg, network node 310, relay UE 320, remote UE 330, etc.). Figure 17 Examples of communication devices are described. Communication device 3200 may include a two-way wireless communication device with voice and data communication capabilities. In some embodiments, voice communication capability is optional. Communication device 3200 typically has the ability to communicate with other computer systems via the Internet. Depending on the exact functionality provided, communication device 3200 may be referred to as, for example, a data messaging device, a two-way pager, a wireless email device, a cellular phone with data messaging capabilities, a wireless Internet device, a wireless device, a smartphone, a mobile device, or a data communication device.

[0154] Where the communication device 3200 is capable of two-way communication, it may include a communication subsystem 3211, which includes a local receiver 3212 and transmitter 3214, and associated components such as one or more antenna elements 3216 and 3218, a local oscillator (LO) 3213, and a processing module such as a digital signal processor (DSP) 3220. The specific design of the communication subsystem 3211 may depend on the communication network 3219 in which the communication device 3200 is to operate.

[0155] Network access may also vary depending on the type of communication network 3219. In some networks, network access is associated with a subscriber or user of the communication device 3200. The communication device 3200 may use a removable user identity module (RUIM) or subscriber identity module (SIM) card to operate on the network. The SIM / RUIM interface 3244 is generally similar to a card slot into which a SIM / RUIM card may be inserted. The SIM / RUIM card may have memory and may store a number of key configurations 3251 and other information 3253, such as identification and subscriber-related information.

[0156] When the network registration or activation process is completed, the communication device 3200 may send and receive communication signals over the communication network 3219. As shown, the communication network 3219 may include a plurality of base stations with which the communication device 3200 communicates.

[0157] Signals received by antenna 3216 via communication network 3219 are input to receiver 3212, which can perform common receiver functions such as signal amplification, frequency down-conversion, filtering, and channel selection. Analog-to-digital (A / D) conversion of the received signal allows for more complex communication functions, such as demodulation and decoding, to be performed in DSP 3220. Similarly, signals to be transmitted are processed by DSP 3220, including, for example, modulation and encoding, and input to transmitter 3214 for digital-to-analog (D / A) conversion, frequency up-conversion, filtering, amplification, and transmission via antenna 3218 over communication network 3219. DSP 3220 not only processes communication signals but also provides receiver and transmitter control. For example, the gain applied to communication signals in receiver 3212 and transmitter 3214 can be adaptively controlled by an automatic gain control algorithm implemented in DSP 3220.

[0158] The communication device 3200 typically includes a processor 3238 that controls the overall operation of the device. Communication functions, including data and voice communications, are performed by the communication subsystem 3211 in cooperation with the processor 3238. The processor 3238 also interacts with other device subsystems, such as a display 3222, flash memory 3224, random access memory (RAM) 3226, an auxiliary input / output (I / O) subsystem 3228, a serial port 3230, one or more user interfaces (such as a keyboard or keypad 3232, a speaker 3234, a microphone 3236), other communication subsystems 3240 (such as a short-range communication subsystem), and any other device subsystems (generally represented as 3242). The serial port 3230 may include a USB port or other port currently known or developed in the future.

[0159] Some of the illustrated subsystems perform communication-related functions, while other subsystems may provide "resident" or on-device functions. Notably, some subsystems (e.g., keyboard 3232 and display 3222) may be used for both communication-related functions (such as entering a text message for transmission over a communication network) and device-resident functions (such as a calculator or task list).

[0160] Operating system software used by the processor 3238 may be stored in a persistent store such as flash memory 3224, which may alternatively be a read-only memory (ROM) or similar storage element (not shown). The operating system, specific device applications, or portions thereof, may be temporarily loaded into a volatile store such as RAM 3226. Received communication signals may also be stored in RAM 3226.

[0161] As shown, flash memory 3224 can be composed of different areas for computer programs 3258 and program data storage 3250, 3252, 3254, and 3256. These different storage types indicate that each program can allocate a portion of flash memory 3224 for its own data storage use. In addition to its operating system functions, processor 3238 can also enable the execution of software applications on communication device 3200. A set of predetermined applications that control basic operations (for example, including at least data and voice communication applications) can typically be installed on communication device 3200 during the manufacturing process. Other applications can be installed later or dynamically installed.

[0162] The application and software may be stored on any computer-readable storage medium. The computer-readable storage medium may be tangible or may be a transient / non-transitory medium such as optical (e.g., CD, DVD, etc.), magnetic (e.g., tape), or other memory currently known or developed in the future.

[0163] One software application may be a personal information manager (PIM) application that is capable of organizing and managing data items associated with the user of the communication device 3200, such as, but not limited to, emails, calendar events, voicemails, appointments, and task items. One or more memory devices may be available on the communication device 3200 to facilitate the storage of PIM data items. Such a PIM application may have the ability to send and receive data items via the wireless network 3219. Other applications may also be loaded onto the communication device 3200 via the communication network 3219, the auxiliary I / O subsystem 3228, the serial port 3230, the short-range communication subsystem 3240, or any other suitable subsystem 3242, and installed by the user in the RAM 3226 or non-volatile memory (not shown) for execution by the processor 3238. This flexibility in application installation can increase the functionality of the communication device 3200 and can provide enhanced on-device functionality, communication-related functionality, or both. For example, a secure communication application may enable the use of the communication device 3200 to perform e-commerce functions and other such financial transactions.

[0164] In the data communication mode, received signals such as text messages or web page downloads can be processed by the communication subsystem 3211 and input to the processor 3238, which can also process the received signals for output to the display 3222 or auxiliary I / O device 3228.

[0165] The user of the communication device 3200 may also compose data items such as email messages using the keyboard 3232, which may be a physical or on-screen / virtual full alphanumeric keyboard or a telephone-type keypad, etc., in combination with the display 3222 and possible auxiliary I / O devices 3228. Such composed items may then be transmitted over the communication network via the communication subsystem 3211.

[0166] For voice communications, the overall operation of the communication device 3200 is similar, except that received signals may generally be output to a speaker 3234 and signals for transmission may be generated by a microphone 3236. Alternative voice or audio I / O subsystems 3228, such as a voice message recording subsystem, may also be implemented on the communication device 3200. Although voice or audio signal output may be primarily implemented through the speaker 3234, the display 3222 may also be used to provide, for example, an indication of the identity of the calling party, the duration of the voice call, or other voice call related information.

[0167] Serial port 3230 can be implemented in a personal digital assistant (PDA) type device, for which it may be desirable to synchronize with a user's desktop computer (not shown), but such a port is an optional device component. Such a port 3230 can enable a user to set preferences through an external device or software application, and can extend the capabilities of the communication device 3200 by providing information or software downloads to the communication device 3200 rather than through a wireless communication network. Alternative download paths can, for example, be used to load encryption keys onto the communication device 3200 through a direct and therefore reliable and trusted connection, thereby enabling secure device communications. Serial port 3230 can also be used to connect the device to a computer to act as a modem.

[0168] Other communication subsystems 3240, such as a short-range communication subsystem, are other optional components that can provide communication between the communication device 3200 and different systems or devices (which are not necessarily similar devices). For example, the subsystem 3240 may include an infrared device and associated circuits and components or a Bluetooth TM Communication modules to provide communication with similarly enabled systems and devices. Subsystem 3240 may also include non-cellular communications, such as wireless local area networks (e.g., ), WiMAX, near field communication (NFC), and / or radio frequency identification (RFID). Other communication subsystems 3240 may also include other suitable components for communicating with auxiliary devices such as a flat panel display, keyboard, or projector.

[0169] The communication device 3200 and other components described above may include processing components capable of executing instructions related to the actions described above. Figure 18 An example of a system 3300 is shown, which includes a processing component 3310 suitable for implementing one or more embodiments disclosed herein. In addition to the processor 3310 (which may be referred to as a central processing unit or CPU), the system 3300 may also include a network connection device 3320, a random access memory (RAM) 3330, a read-only memory (ROM) 3340, an auxiliary storage 3350, and an input / output (I / O) device 3360. These components can communicate with each other via a bus 3370. In some cases, some of these components may not be present, or may be combined with each other or with components not shown in various combinations. These components may be located in a single physical entity or in multiple physical entities. Any action described herein as being performed by the processor 3310 may be performed by the processor 3310 alone, or by the processor 3310 together with one or more components shown or not shown in the figure (such as a digital signal processor (DSP) 3380). Although the DSP 3380 is shown as a separate component, the DSP 3380 may be incorporated into the processor 3310 .

[0170] The processor 3310 executes instructions, codes, computer programs, or scripts that it can access from the network connection device 3320, RAM 3330, ROM 3340, or auxiliary storage 3350 (which may include various disk-based systems such as hard disks, floppy disks, or optical disks). Although only one CPU 3310 is shown, multiple processors may be present. Therefore, although instructions may be discussed as being executed by a processor, instructions may be executed by one or more processors simultaneously, serially, or in other ways. The processor 3310 may be implemented as one or more CPU chips.

[0171] The network connection device 3320 may take the form of a modem, a modem bank, an Ethernet device, a USB interface device, a serial interface, a token ring device, a fiber distributed data interface (FDDI) device, a wireless local area network (WLAN) device, a radio transceiver device such as a code division multiple access (CDMA) device, a GSM radio transceiver device, a UMTS radio transceiver device, an LTE radio transceiver device, a new generation radio transceiver device, a Worldwide Interoperability for Microwave Access (WiMAX) device, and / or other well-known devices for connecting to a network. These network connection devices 3320 may enable the processor 3310 to communicate with the Internet or one or more telecommunications networks or other networks from which the processor 3310 can receive information or to which the processor 3310 can output information. The network connection device 3320 may also include one or more transceiver components 3325 capable of wirelessly transmitting and / or receiving data.

[0172] RAM 3330 can be used to store volatile data and may be used to store instructions executed by processor 3310. ROM 3340 is a non-volatile memory device that typically has a smaller storage capacity than secondary storage 3350. ROM 3340 can be used to store instructions and data that may be read during instruction execution. Access to RAM 3330 and ROM 3340 is typically faster than access to secondary storage 3350. Secondary storage 3350 is typically composed of one or more disk drives or tape drives and can be used for non-volatile storage of data or as an overflow data storage device (if RAM 3330 is insufficient to hold all working data). Secondary storage 3350 can be used to store programs that are loaded into RAM 3330 when such programs are selected for execution.

[0173] I / O devices 3360 may include a liquid crystal display (LCD), a touch screen display, a keyboard, a keypad, switches, a rotary dial, a mouse, a trackball, a voice recognizer, a card reader, a paper tape reader, a printer, a video monitor, or other well-known input / output devices. In addition, transceiver 3325 may be considered a component of I / O devices 3360 rather than a component of network connectivity devices 3320 or as a supplement thereto.

[0174] The following are incorporated herein by reference for all purposes: 3GPP TS TS 23.285, 3GPP TS 23.303, 3GPP TS 23.041, 3GPP TS 36.321, 3GPP TS 36.331, 3GPP TS 22.268, ETSI EN 302 665, ETSI TS 102 894-2, ETSI EN 302 637-2, ETSI EN 302 637-3, ETSI TS 102 965, SP-160733, and 3GPP TS 22.969.

[0175] In an embodiment, a method for relaying a Public Warning System (PWS) message is provided. The method includes receiving, by a communication device, a PWS message using a first communication technology. The method also includes relaying, by the communication device, the PWS message (e.g., transmitting all or part of the received PWS message) using a second communication technology that is different from the first communication technology.

[0176] In another embodiment, a communication device is provided. The communication device includes: a memory containing instructions; and a processor coupled to the memory. The processor is configured to execute the instructions to cause the communication device to receive a PWS message using a first communication technology, and to cause the communication device to relay the PWS message (e.g., transmit all or part of the received PWS message) using a second communication technology that is different from the first communication technology.

[0177] In another embodiment, a computer-readable medium is provided. The computer-readable medium includes instructions that, when executed by a processor, cause a communication device to implement a method. The method includes the communication device receiving a PWS message via a first communication technology. The method also includes the communication device relaying the PWS message (e.g., transmitting all or part of the received PWS message) via a second communication technology, where the second communication technology is different from the first communication technology.

[0178] Although several embodiments have been provided in this disclosure, it should be understood that the disclosed systems and methods may be implemented in many other specific forms without departing from the spirit or scope of the present disclosure. The present examples are intended to be illustrative rather than restrictive, and are not intended to be limited to the details given herein. For example, various elements or components may be combined or integrated in another system, or certain features may be omitted or not implemented.

[0179] In addition, without departing from the scope of the present disclosure, the techniques, systems, subsystems and methods described and shown as separate or independent in various embodiments can be combined or integrated with other systems, modules, technologies or methods. Other items shown or discussed as coupled or directly coupled or communicating with each other can be indirectly coupled or communicated by electrical, mechanical or other means through some interface, device or intermediate component. Those skilled in the art can determine and make changes, substitutions and alternative examples without departing from the scope disclosed herein.

Claims

1. A method for relaying a Public Warning System (PWS) message, the method comprising: receiving, at a relay user equipment (UE), a PWS message from a base station, wherein the relay UE receives the PWS message from the base station through a first communication technology; generating, by the relay UE, a first outgoing message including all or part of the PWS message, the first outgoing message including at least a first parameter, a second parameter, and a message identifier, wherein the first parameter is used to indicate that the PWS message corresponds to a specific type of warning message, and the second parameter is used to distinguish between different PWS messages; as well as transmitting, by the relay UE, the first outgoing message to a remote UE, wherein the relay UE transmits the first outgoing message to the remote UE using a second communication technology, the second communication technology being different from the first communication technology, wherein the message identifier indicates the source of the PWS message, The relay UE formats the first outgoing message before transmitting the first outgoing message to the remote UE, wherein the first outgoing message is formatted based on the message identifier within the first outgoing message. 2 . The method of claim 1 , wherein the first communication technology comprises a radio access technology (RAT), and wherein the second communication technology comprises a short-range communication technology.

3. The method of claim 2 , wherein the PWS message is received in a telecommunication network through the RAT, the telecommunication network comprising a Global System for Mobile Communications (GSM) / Enhanced Data Rates for GSM Evolution (EDGE) radio access network (GERAN), a Universal Mobile Telecommunications System (UMTS), a Universal Terrestrial Radio Access Network (UTRAN), an Evolved UTRAN (E-UTRAN), or a Next Generation Radio Access Network.

4. The method of claim 2, wherein the transmitting comprises: The relay UE relays all or part of the PWS message to the remote UE via a device-to-device (D2D) interface using the short-range communication technology.

5. The method according to claim 4, further comprising: receiving, by the relay UE, a secondary PWS message related to the PWS message, wherein the relay UE receives the secondary PWS message from the base station through the RAT; generating, by the relay UE, a second outbound message, the second outbound message including all or part of the secondary PWS message related to the PWS message, wherein generating the second outbound message comprises the relay UE formatting the second outbound message to include at least one of: a sequence number, a message identifier, or a data encoding scheme; and In response to formatting the second outgoing message, the second outgoing message is relayed by the relay UE to the remote UE via the short-range communication technology. 6 . The method of claim 5 , wherein the second outgoing message is relayed via the D2D interface by the short-range communication technology, wherein the D2D interface comprises a PC5 interface.

7. The method of claim 2 , wherein the relay UE relays the PWS message as a Decentralized Environment Notification message (DENM) to the remote UE via the short-range communication technology, wherein the remote UE is not configured to receive the PWS message from the base station via the first communication technology, and wherein the relay UE provides an indication that the first outgoing message includes a PWS message, and wherein the indication includes a destination layer-2 identifier.

8. A relay user equipment UE, comprising: Memory, containing instructions; as well as a processor coupled to the memory and configured, when the instructions are executed, to: receiving, at the relay UE, a public warning system (PWS) message from a base station, wherein the relay UE receives the PWS message from the base station through a first communication technology; generating, by the relay UE, a first outgoing message including all or part of the PWS message, the first outgoing message including at least a first parameter, a second parameter, and a message identifier, wherein the first parameter is used to indicate that the PWS message corresponds to a specific type of warning message, and the second parameter is used to distinguish between different PWS messages; as well as transmitting, by the relay UE, the first outgoing message to a remote UE, wherein the relay UE transmits the first outgoing message to the remote UE using a second communication technology, the second communication technology being different from the first communication technology, wherein the message identifier indicates the source of the PWS message, The relay UE formats the first outgoing message before transmitting the first outgoing message to the remote UE, wherein the first outgoing message is formatted based on the message identifier within the first outgoing message. 9 . The relay UE of claim 8 , wherein the first communication technology comprises a radio access technology (RAT), and wherein the second communication technology comprises a short-range communication technology.

10. The relay UE according to claim 9, wherein the PWS message is received in a telecommunication network through the RAT, the telecommunication network comprising a Global System for Mobile Communications (GSM) / Enhanced Data Rates for GSM Evolution (EDGE) radio access network (GERAN), a Universal Mobile Telecommunications System (UMTS), a Universal Terrestrial Radio Access Network (UTRAN), an Evolved UTRAN (E-UTRAN), or a Next Generation Radio Access Network. 11 . The relay UE according to claim 9 , wherein the transmitting comprises the relay UE relaying all or part of the PWS message to the remote UE via a device-to-device (D2D) interface through the short-range communication technology.

12. The relay UE according to claim 11, wherein the processor is further configured to: receiving, by the relay UE, a secondary PWS message related to the PWS message, wherein the relay UE receives the secondary PWS message from the base station through the RAT; generating, by the relay UE, a second outbound message, the second outbound message including all or part of the secondary PWS message related to the PWS message, wherein generating the second outbound message comprises the relay UE formatting the second outbound message to include at least one of: a sequence number, a message identifier, or a data encoding scheme; and In response to formatting the second outgoing message, the second outgoing message is relayed by the relay UE to the remote UE via the short-range communication technology. 13 . The relay UE according to claim 12 , wherein the second outgoing message is relayed via the D2D interface by the short-range communication technology, wherein the D2D interface comprises a PC5 interface.

14. The relay UE according to claim 9, wherein the relay UE relays the PWS message as a decentralized environment notification message DENM to the remote UE via the short-range communication technology, wherein the remote UE is not configured to receive the PWS message from the base station via the first communication technology, and wherein the relay UE provides an indication that the first outgoing message includes a PWS message, and wherein the indication includes a destination second layer identifier.

15. A non-transitory computer-readable medium comprising instructions executable by a processor of a relay user equipment (UE) such that when executed, the processor: receiving, at the relay UE, a public warning system (PWS) message from a base station, wherein the relay UE receives the PWS message from the base station through a first communication technology; generating, by the relay UE, a first outgoing message including all or part of the PWS message, the first outgoing message including at least a first parameter, a second parameter, and a message identifier, wherein the first parameter is used to indicate that the PWS message corresponds to a specific type of warning message, and the second parameter is used to distinguish between different PWS messages; as well as transmitting, by the relay UE, the first outgoing message to a remote UE, wherein the relay UE transmits the first outgoing message to the remote UE using a second communication technology, the second communication technology being different from the first communication technology, wherein the message identifier indicates the source of the PWS message, The relay UE formats the first outgoing message before transmitting the first outgoing message to the remote UE, wherein the first outgoing message is formatted based on the message identifier within the first outgoing message.

16. The non-transitory computer-readable medium of claim 15, wherein the first communication technology comprises a radio access technology (RAT), and wherein the second communication technology comprises a short-range communication technology.

17. The non-transitory computer-readable medium of claim 16, wherein the PWS message is received in a telecommunication network through the RAT, the telecommunication network comprising a Global System for Mobile Communications (GSM) / Enhanced Data Rates for GSM Evolution (EDGE) radio access network (GERAN), a Universal Mobile Telecommunications System (UMTS), a Universal Terrestrial Radio Access Network (UTRAN), an Evolved UTRAN (E-UTRAN), or a Next Generation Radio Access Network. 18 . The non-transitory computer-readable medium of claim 16 , wherein the transmitting comprises the relay UE relaying all or part of the PWS message to the remote UE via a device-to-device (D2D) interface through the short-range communication technology.

19. The non-transitory computer-readable medium of claim 18, wherein the processor, when the instructions are executed, is further configured to: receiving, by the relay UE, a secondary PWS message related to the PWS message, wherein the relay UE receives the secondary PWS message from the base station through the RAT; generating, by the relay UE, a second outbound message, the second outbound message including all or part of the secondary PWS message related to the PWS message, wherein generating the second outbound message comprises the relay UE formatting the second outbound message to include at least one of: a sequence number, a message identifier, or a data encoding scheme; and In response to formatting the second outgoing message, the second outgoing message is relayed by the relay UE to the remote UE via the short-range communication technology.

20. The non-transitory computer-readable medium of claim 19, wherein the second outgoing message is relayed via the D2D interface by the short-range communication technology, wherein the D2D interface comprises a PC5 interface.

21. The non-transitory computer-readable medium of claim 16, wherein the relay UE relays the PWS message as a Decentralized Environment Notification message (DENM) to the remote UE via the short-range communication technology, wherein the remote UE is not configured to receive the PWS message from the base station via the first communication technology, and wherein the relay UE provides an indication that the first outgoing message includes a PWS message, and wherein the indication includes a destination layer-2 identifier.

Images