Source: https://patents.google.com/patent/US8369824B2/en
Timestamp: 2018-09-24 22:25:19
Document Index: 781340628

Matched Legal Cases: ['art 1', 'art 2', 'art 3', 'art 4', 'Application No. 09759254', 'Application No. 09759255', 'Application No. 2', 'Application No. 2011', 'Application No. 2011', 'Application No. 10', 'Application No. 10']

US8369824B2 - Privacy-related requests for an IMS emergency session - Google Patents
US8369824B2
US8369824B2 US13244795 US201113244795A US8369824B2 US 8369824 B2 US8369824 B2 US 8369824B2 US 13244795 US13244795 US 13244795 US 201113244795 A US201113244795 A US 201113244795A US 8369824 B2 US8369824 B2 US 8369824B2
US13244795
US20120015623A1 (en )
A network component is provided that includes a processor configured, upon the network component receiving an IMS (Internet Protocol Multimedia Subsystem) emergency call from a user equipment (UE) 110, to detect in the emergency call an indicator requesting the network component to restrict presentation of private information related to the UE 110. The processor is further configured, when the indicator is present, to transmit the emergency call without at least some of the private information to a Public Safety Answering Point (PSAP) 130.
This application is a continuation of U.S. patent application Ser. No. 12/994,416 filed Nov. 23, 2010, which claims the benefit of International Application No. PCT/US2009/045992 filed Jun. 2, 2009, entitled “Privacy-Related Requests for an IMS Emergency Session,” and claims priority to U.S. patent application Ser. No. 12/131,790 filed on Jun. 2, 2008 now abandoned, all of which are incorporated by reference herein in their entirety.
The IP (Internet Protocol) Multimedia Subsystem (IMS) is a standardized architecture for providing multimedia services and voice-over-IP calls to both mobile and fixed user equipment (UE). The Session Initiation Protocol (SIP) has been standardized and governed primarily by the Internet Engineering Task Force (IETF) as a protocol for setting up and managing IMS-based calls. As used herein, the term “UE” can refer to mobile devices such as mobile telephones, personal digital assistants, handheld or laptop computers, and similar devices that have telecommunications capabilities. Such a UE might consist of a wireless device and its associated Universal Integrated Circuit Card (UICC) that includes a Subscriber Identity Module (SIM) application, a Universal Subscriber Identity Module (USIM) application, or a Removable User Identity Module (R-UIM) application or might consist of the device itself without such a card. The term “UE” may also refer to devices that have similar capabilities but that are not transportable, such as fixed line telephones, desktop computers, or set-top boxes. The term “UE” can also refer to any hardware or software component that can terminate a SIP session.
A user of a UE, such as an IMS-capable UE, can typically place an emergency call by dialing 911 (in North America), 112 (in most of Europe), 999 (in the United Kingdom), 110, 118, or 119 (in Japan), or some other emergency-specific number. Such a call may be handled by a Public Safety Answering Point (PSAP), which might be an emergency call centre or system that can coordinate an appropriate response to the emergency. Any call made to a PSAP will be referred to herein as an emergency call. In this document, a PSAP could also be an emergency centre or emergency centers.
The emergency-related indicator can be encoded in SIP using the following alternatives: a) SIP bodies such as “application/3gpp-ims+xml” have been used in IMS to indicate additional information or directives to receiving UAs. It can be extended to also indicate to the UE that, upon receipt in an INVITE or similar request, the request is to be taken as an emergency call or PSAP callback and that the functionality associated with calls of such type is to be invoked. This functionality may include but is not limited to alerting the user by visual, audible, or other methods as well as including location information in the response. A new content-disposition header field value may need to be defined. b) A new SIP header could be defined or an existing SIP header could be enhanced. The PSAP itself or the S-CSCF handling the PSAP callback on behalf of the PSAP or another network element such as a signaling gateway can introduce an indicator. c) The indicator could be a new SIP header field. d) The indicator could be a new SIP header field value, e.g., a standardized SIP URN indicating the PSAP function (e.g. mountain rescue or coast guard or general 911) or emergency centre function or emergency personnel function. e) The indicator could be a new URI field. f) The indicator could be a new URI field value, e.g., user=psap, where “user” is a SIP URI field and “psap” is a new value that might be put in the Contact header field. g) The standardized SIP URN could be put in the P-Asserted-Identity by the trust domain in which the PSAP or emergency centre or emergency personnel resides. h) The indicator could be contained in the FROM header field value and the FROM header field value can be asserted according to RFC 4474 or RFC 3893. This solution is based on certificates.
As identified above, a number of possibilities could be used to indicate that a session is in fact an emergency session. It has been highlighted that the PSAP could be in a visited network such as a VPLMN network and has no trust relationship with the home network such as an HPLMN (Home Public Land Mobile Network). Assuming this is the case when the UE is setting up an emergency session, the UE doesn't recognize or when receiving a mobile terminated request containing an indication in the SIP message (e.g., 1xx or 2xx responses or a SIP target refresh request or a similar message) that the request is a PSAP callback, the PSAP or the network could also send back a token that the UE would store. The network could provide this token when the UE registers with an IM core network (CN) subsystem. The token could be stored in memory, which could be internal or removable. In the event the UE's emergency call is disconnected or the UE needs to be informed it is requesting an emergency session, the network or PSAP could include this token. Upon receipt of the token from the network, the UE can compare it to the shared token. If the tokens do not match, the UE knows the call is not emergency related.
In the event the PSAP callback or emergency call signaling response is received over a circuit-switched network, the solution can allow for mapping between appropriate Calling-Party-Category field which is sometimes used to carry the indication of an emergency call in ISUP/TUP (ISDN User Part/Telephone User Part)-based systems. Typically, the ISUP/TUP signaling information does not allow for a granularity as fine as the emergency urn:service:sos identifiers defined in RFC 5031.
FIG. 1 illustrates a system 10 that includes one or more components associated with an IMS network 120. A UE 110 may be any end user device or system that can connect to the IMS network 120. Examples of the UE 110 can include, but are not limited to, mobile phones, fixed line phones, mobile wireless devices (including digital, cellular, or dual mode devices), personal digital assistants, laptop/tablet/notebook computers, and desktop computers. The UE 110 can communicate via the IMS network 120 with a PSAP 130, which may be a 911 system or another emergency call centre or system.
The IMS network 120 might include any well-known set of components, such as base stations and other radio transmission and reception equipment, that can promote an IMS-based connection between the UE 110 and the PSAP 130. Other components that might be present in the IMS network 120 but that are not shown include a P-CSCF (Proxy Call Session Control Function) that may be the first point of contact for the UE 110; an S-CSCF (Serving CSCF) that may perform session control, downloading and uploading of user profiles, and other functions; an E-CSCF (Emergency CSCF) that may provide session control functions for the PSAP 130; and other well-known components for initiating and maintaining IMS-based sessions.
In an embodiment, the response message 150 includes an indicator 160 that indicates that the call placed by the UE 110 was an emergency call. The indicator 160 may be a bit, a flag, or some other data element that is recognizable by the UE 110 as a designation that a call placed by the UE 110 was an emergency call (e.g., emergency service URNs as specified in RFC 5031 such as urn:service:sos, urn:service:sos.animal-control, or urn:service:sos.police, if it is determined that the call that was placed can be categorized as, e.g., a urn:service:sos call, a urn:service:sos.animal-control call, or a urn:service:sos.police call). When the UE 110 receives the response message 150 that includes the indicator 160, the UE 110 identifies that the call it placed was an IMS emergency call and can then take appropriate actions and invoke functionality for an emergency call. One action that the UE 110 might take is to indicate to the UE user the nature of the original call. That is, the UE 110 might alert the user that the call was an emergency call. The alert might be a message that appears on the display screen of the UE 110, a visual or audible alert, or some other type of environmental condition or indication of the nature of the call. Other actions taken by the UE 110 can involve transmitting a SIP request message 170 such as a SIP ACK or SIP PRACK message or any subsequent SIP request part of the dialog (including target refresh requests) or request for a new dialog, where the request for the dialog uses the SIP Target-Dialog header field with a value set identical to the corresponding dialog identifier value for the emergency session. In the case of sending a request for a new dialog message 170 with SIP Target-Dialog header field set, it can indicate to the recipient that the sender is aware of an existing dialog with the recipient, either because the sender is on the other side of that dialog, or because it has access to the dialog identifiers, the recipient can then authorize the request based on this awareness. Subject to limitations of SIP, either of these messages can include information in the request as part of information available to the PSAP 130 if the recipient is the PSAP 130. As mentioned, the message 170 might be a SIP target refresh request, a SIP UPDATE, a SIP re-INVITE message 170, or a similar (acknowledgement) message (e.g. SIP PRACK). The message 170 can include information 180 about the UE 110, to be described in detail below. Due to limitations in the SIP protocol, the information 180 may be spread over several SIP messages, e.g. some information may be in SIP PRACK requests, some in responses to PSAP- or network-originated requests or SIP UPDATE requests, and some in other SIP target refresh requests. The information 180 might be intended for the PSAP 130 or for one or more components in the IMS network 120. The information 180 could optionally include a flag or other indicator that indicates that certain emergency-related information, such as identification, network access, and location information, is not to be shared (e.g., with the PSAP 130). If one or more privacy indicators are set, the network might still be able to use the emergency-related information for routing purposes or to provide anonymous callback.
In another embodiment, a policy could be stored in the UE 110. The policy or policies can be used to determine if including one or more indicators to request privacy when requesting emergency sessions is allowed, or if emergency-related information is provided when a PSAP makes a callback, or if it is allowed to request privacy when emergency-related information is provided in response to a PSAP callback. The policy could be consulted when the UE 110 wants to divulge information that is sensitive to privacy, such as, but not limited to, location. The policy could be user-provided, operator-provided, or both. When the information is both user-provided and operator-provided, the operator might provide a default policy, but the user might be able to override this policy if they so wish. The policy can be stored in memory that is either internal or external to the device.
Token received ascertain authenticity of token and if valid
Token received, fake, provide indication to network fake token
received, provide no location information.
The token could be carried in a callback from the PSAP 130, such as a SIP INVITE. Alternatively, the token could be provided at the time the UE 110 makes registration with the network 120, such that in IMS the token could be provided in a SIP 200 OK message in response to an emergency registration. Within the 200 OK, if the token is coded as a new feature tag, a new URI parameter, or an XML body, the token might be a secure token. In an LTE/SAE network, the 200 OK message could be transmitted in response to a request to attach to the network or as part of the authentication sequence of the UE 110.
The Emergency Location policy leaf indicates whether the UE
provides emergency information or not for emergency call back.
0 - UE provides emergency information.
1 - UE does not provide emergency information.
Before the emergency request reaches the PSAP 130, it might be handled by one or more components in the IMS network 120. One such component is the P-CSCF. An IMS network component can inspect all requests in order to determine if they are related to emergencies. If a request is determined to relate to an emergency, based on configurations and regulator policies, the network component can determine to reject the request or reformat the request or include the emergency call indicator 160 in a SIP response that is sent to the UE 110. Reformatting the request might be done if the UE 110 provides a T-GRUU and the network operator policy settings (e.g., in the P-CSCF) indicate that the public user identities must be provided. In such a case, the T-GRUU can be replaced with the GRUU. In addition, reformatting of messages to be routed to PSAPs might be done if the message contains P-Preferred-Service header fields, P-Asserted-Service header fields, Accept-Contact header fields containing an IMS Communication Service Identifier (ICSI) value (coded as specified in subclause 7.2A.8.2 in 3GPP TS 24.229) and zero or more IMS Application Reference Identifier (IARI) values (coded as specified in subclause 7.2A.9.2 in 3GPP TS 24.229) that are related to the request in a g.3gpp.app_ref feature tag. The P-Preferred-Service header fields, P-Asserted-Service header fields should not be forwarded to the PSAP or emergency centre. The Accept-Contact header fields should be groomed for ICSI values and IARI values as they may cause interactions when selecting an agent. If the Accept-Contact header field contains g.3gpp.app_ref media feature tags, they and their values shall be removed.
In other words, what is termed “reformatting” can include changing the GRUU from a temporary GRUU into a public GRUU. This is done because a temporary GRUU is invalid if the UE is disconnected and has to re-register. A PSAP cannot make a callback to a temporary GRUU after the UE de-registers and re-registers. Public GRUUs, on the other hand, have the property that they are routable even after the UE de-registers and re-registers (making a PSAP callback to that public GRUU more likely to complete). “Reformatting” can also include not propagating of ICSI or IARI feature tags, P-Preferred-Serviceheader fields, and/or P-Asserted-Service header fields. The presence of such tags or fields might skew the handling of the request at the PSAP and cause the request to be routed based on services supported on the UE rather than, for example, on geographical proximity and type of service requested. Since there is typically an S-SCSF in the session path between the UE, the P-CSCF, the E-CSCF, and the PSAP, these services the UE supposedly supports are typically not activated during the emergency call. So signaling it as part of an emergency request (even when the UE did not realize it is an emergency request and includes ICSI or IARI feature tags, P-Preferred-Service header fields, and/or P-Asserted-Service header fields because it believes the request it makes is a normal request) does not serve any purpose and may only detract/result in routing the requests to other PSAPs than those determined based on location, requested type of service, and RFC 3261 procedures. In a worst case scenario, if a PSAP operator registers its support for said services, it may receive a higher load of emergency service requests than other PSAP operators, possibly leading to delay in the emergency response.
Two examples can illustrate cases where the network rejects the request because the type of emergency session request is not supported. In the first example, RFC 5031 defines urn:service:sos.animal-control as follows: Animal control typically enforces laws and ordinances pertaining to animal control and management, investigates cases of animal abuse, educates the community in responsible pet ownership and wildlife care, and provides for the housing and care of homeless animals, among other animal-related services. In some jurisdictions, a request to urn:service:sos.animal-control may not be classified as an emergency in the sense that it is subjected to network and operator emergency procedures (e.g. allow or disallow a request to urn:service:sos.animal-control when the UE didn't register or has insufficient credentials). If so configured, the network could either reject with an indication that the call is not actually an emergency or it could reject with an indication that the call is not an emergency and offer alternative steps to be executed such as offering a different URI to contact and/or a different CS network address such as a digit string. Note that, since emergency service URNs are not routable and are not E.164 numbers, the UE may not be able to proceed lacking knowledge of routable addresses or numbers. In those jurisdictions, it would be inappropriate if the UE executed emergency procedures (as specified in 3GPP TS 24.008) and a UE should not automatically contact, for example, “911” or “112” “upon receiving a rejection when contacting, e.g., urn:service:sos.animal-control.
Bit 1 Police
Bit 2 Ambulance
Bit 3 Fire Brigade
Bit 4 Marine Guard
match the received service category to any of the emergency centres, it
shall route the call to an operator defined default emergency centre.
If no bit is set to “1”, the MSC shall route the Emergency call to an
operator defined default emergency centre
However, at present no mapping for urn:service:sos.animal-control exists. A mapping for some other emergency services as defined in RFC 5031 (e.g. urn:service:sos.police) can be made by setting the corresponding bit in Emergency Category Value (e.g. urn:service:sos.police maps to Bit 1 of the Emergency Service Category Value, urn:service:sos.ambulance maps to Bit 2 of the Emergency Service Category Value, urn:service:sos.fire maps to Bit 3 of the Emergency Service Category Value, urn:service:sos.marine maps to Bit 4 of the Emergency Service Category Value, urn:service:sos.mountian maps to Bit 5 of the Emergency Service Category Value). urn:service:sos.animal-control, urn:service:sos.physician, urn:service:sos.poison, urn:service:sos.gas, and others could map to an Emergency Service Category Value with no bits set to “1”, causing the call to be routed to an operator-defined default emergency centre. Alternatively, for requests for which no PSAP is supported in the network, the UE could be instructed to make a normal SIP request (using procedures in 3GPP TS 24.228) or set up a normal CS call (using procedures in 3GPP TS 24.008). The network could accomplish such by not indicating an alternative address that cannot be mapped to an Emergency Service Category Value (i.e. not one of the urn:service:sos URNs for which a mapping is standardized). When an emergency request is received by the PSAP but the PSAP cannot handle the request and returns a SIP 380 or a similar message, if a mapping exists on the UE from the given URN to an Emergency Service Category Value, a call shall be set up to that CS PSAP E.164 number automatically.
In the second example: the P-CSCF may determine that the emergency request is made to urn:service:sos.police. However, for example in the Netherlands, contacting the police does not per definition warrant activating emergency procedures. Instead, a special number different from “112” is configured: 0900-8844. Other examples are “19” Police (Albania), “100” (Police and Fire Brigade (Greek cities)), “100” (Ambulance and Fire Brigade (Belgium)), “112” (Police and Ambulance (Italy)), “112” (General emergency call, all categories (Sweden)), “115” (Fire Brigade (Italy)), “144” (Ambulance (Austria)), “*377” (local police agency or Department of Public Safely office, non-emergency roadside assistance in Texas). Such a number may be a premium service. It could be inappropriate if the UE automatically contacted, for example, “911” or “112” if the network rejects the call to urn:service:sos.police, and it could be inappropriate if the network automatically contacted, for example, 0900-8844 as a regular call as the user, without realizing it, may then automatically receive premium charges. The P-CSCF could provide alternative steps such as providing a digit string, e.g., 0900-8844, in a SIP 3xx response. However, the digit string may be part of a message that identifies that the digit string should be displayed and/or that a textual message should be displayed to indicate the nature of the call that was made and the nature of the number provided.
In yet another embodiment, the P-CSCF will not reject the request for an unsupported emergency service type (such as urn:service:sos.poison) but prepare it for forwarding to the user's home network S-CSCF using normal procedures (as opposed to forwarding it to an E-CSCF). The user's home network's S-SCSF should then be configured to handle the unroutable Request URI value. The IMS network may also be configured to take account of roaming users requesting a session with urn:service:sos.police, such that the service requested by a UE which may be halfway around the world, can still be handled in a timely and effective manner. The IMS network could provide an indication in a SIP message to the UE that the call has been determined to not be an emergency call and that its handling will be different. The indication could be a flag and/or alphanumeric information. Possible encodings of this type of indicator are given in this document.
In other embodiments, if a component in the IMS network 120 includes the emergency call indicator 160 in the SIP response that is sent to the UE 110, the UE 110 can abort the current signaling and initiate regular emergency call setup procedures, which may involve originating a call over a circuit-switched network, if capable and available, or after initiating emergency registration procedures, or sending a SIP INVITE request containing an indicator indicating that the SIP INVITE request is an emergency-related call request and containing emergency-related information about itself.
One piece of the information 240 that the UE 110 might send to the PSAP 130 is the UE 110's public user identity or some other identifying symbol. Another piece of information 240 that the UE 110 might transmit in the SIP 200 OK message 230 is the type of access that the UE 110 used for the original emergency call. For example, if the emergency call was made over a wireless LAN, the UE 110 might include that fact in the information 240, as well as a cell ID, a line ID, and/or a wireless LAN access node ID.
In an alternative embodiment, the PSAP 130 might setup a circuit-switched (CS) call and a CS gateway might then convert the call and the signaling in packet-switched technology if the CS call is routed to the CS gateway. Triggered by the incoming call from the PSAP 130, the CS gateway might initiate the callback over packet-switched technology by sending a SIP INVITE message 210, or a similar message, to the UE 110 via the IMS network 120.
In the event the UE receives a 380 (Alternative Service) response to an INVITE request, the response containing a XML body that includes an <alternative service> element with the <type> child element's “alternate” attribute containing one or more emergency service URIs, the UE can attempt a normal call as described in subclause 5.1.3.1 using an emergency service URI or using call setup according to the procedures described in 3GPP TS 24.008[8]. The behavior of the UE is implementation specific if the <type> child element's “alternate” attribute is absent or contains no emergency service URIs.
The P-CSCF shall store a configurable list of local emergency service identifiers, i.e. emergency numbers and the emergency service URN, which are valid for the operator to which the P-CSCF belongs to. In addition to that, the P-CSCF shall store a configurable list of roaming partners' emergency service identifiers. The configurable lists with local and roaming partners' emergency service identifiers shall indicate per emergency service identifier the handling. When the handling indicates that the request shall be rejected, a configurable list of alternate emergency service URIs may be included in the response.
If the P-CSCF detects that the Request-URI of the initial request for a dialog, or a standalone transaction, or an unknown method matches an unsupported type of emergency in the VPLMN or HPLMN's emergency service identifiers, the P-CSCF:
0) determine the geographical location of the UE. Access technology specific procedures are described in each access technology specific annex. If the P-CSCF is not capable of handling emergency sessions or due to local policy does not handle emergency sessions or only handles a certain type of emergency session request or the IP-CAN to which the UE is attached or the UE is roaming or the P-CSCF is in a different network than the UE's home operator's network, then the P-CSCF:
a Content-Type header field with the value set to associated MIME type of the 3GPP IMS XML body as described in subclause 7.6.1
b) a <type> child element with an “alternate” attribute set to a list of alternate emergency service URIs, and if the initial request for a dialog, or standalone transaction, or unknown method was for a supported type of emergency, the <type> child element is set to “emergency” to indicate that it was a supported emergency call;
If the IM CN subsystem to where the P-CSCF belongs to is not capable of handling emergency sessions or due to local policy does not handle emergency sessions or only handles a certain type of emergency session request or does not support emergency sessions for either the geographical location where the UE is located or the IP-CAN to which the UE is attached, the P-CSCF shall not forward the INVITE request. The P-CSCF:
Upon generating an initial request for a dialog, or a standalone transaction, or an unknown method, excluding ACK and CANCEL, the UE shall include the Accept header with “application/sdp”, the MIME type associated with the 3GPP IMS XML body (see subclause 7.6.1) and any other MIME type the UE is willing and capable to accept.
In the event the UE receives a 380 (Alternative Service) response to an initial request for a dialog, or a standalone transaction, or an unknown method, the response including an IM CN subsystem XML body as described in subclause 7.6 that includes an <alternative service> element with the <type> child element set to “emergency”, the UE shall attempt an emergency call as described in subclause 5.1.6.
If 1xx or 2xx response to an initial request for a dialog, or a standalone transaction, or an unknown method, contains an emergency session indicator, then the UE shall send a re-INVITE request method according to RFC 3261[26], and:
NOTE 17: the UE does not change the From header to include a public user identity or the tel URI associated with the public user identity, in this version of the specification.
NOTE 18: The IMS emergency specification in 3GPP TS 23.167[4B] describes several methods how the UE can get its location information from the access network or from a server. Such methods are not in the scope of this specification.
if the geographical location information of the UE is available to the UE, include its geographical location information as PIDF location object in accordance with RFC 4119[90] and include the location object in a message body with the content type application/pidf+xml in accordance with draft-ietf-sip-location-conveyance [89]. The Geolocation header is set to a Content ID in accordance with draft-ietf-sip-location-conveyance [89]; and
NOTE 19: According to RFC 3261[26], a reINVITE request cannot be sent while another INVITE transaction is in progress in either direction.
NOTE 20: It is not necessary for this reINVITE request to change the session parameters.
NOTE 21: It is suggested that UEs only use the option of providing a URI when the domain part belongs to the current P-CSCF or S-CSCF provider. This is an issue on which the network operator needs to provide guidance to the end user. A URI that is only resolvable to the UE which is making the emergency call is not desirable.
apply any privacy required by RFC 3323[33] relating to privacy and RFC 3325[34] to the P-Asserted-Identity header;
NOTE 4: If the user did not request privacy, the E-CSCF conveys the P-Access-Network-Info header containing the location identifier, if defined for the access type as specified in subclause 7.2A.4, towards the MGCF. The MGCF can translate the location information if included in INVITE (i.e. both the geographical location information in PIDF-LO and the location identifier in the P-Access-Network-Info header) into ISUP signaling, see 3GPP TS 29.163[11B].
NOTE 5: The E-CSCF can request location information and routing information from the LRF. The E-CSCF can for example send the location identifier to LRF and LRF maps the location identifier into the corresponding geographical location information that LRF sends to E-CSCF. The LRF can invoke an RDF to convert the location information into a proper PSAP/EC URI. Both the location information and the PSAP URI are returned to the E-CSCF.
NOTE 6: The way the E-CSCF determines the next hop address when the PSAP address is a tel URI that is implementation dependent.
7) If the user did not request privacy and if the E-CSCF receives a reference number from the LRF, the E-CSCF shall include the reference number in the P-Asserted-Identity header;
FIG. 4 illustrates a wireless communications system including an embodiment of the UE 110. The UE 110 is operable for implementing aspects of the disclosure, but the disclosure should not be limited to these implementations. Though illustrated as a mobile phone, the UE 110 may take various forms including a wireless handset, a pager, a personal digital assistant (PDA), a portable computer, a tablet computer, or a laptop computer. Many suitable devices combine some or all of these functions. In some embodiments of the disclosure, the UE 110 is not a general-purpose computing device like a portable, laptop or tablet computer, but rather is a special-purpose communications device such as a mobile phone, wireless handset, pager, or PDA. In another embodiment, the UE 110 may be a portable, laptop or other computing device. The UE 110 may support specialized activities such as gaming, inventory control, job control, and/or task management functions, and so on.
FIG. 5 shows a block diagram of the UE 110. While a variety of known components of UEs 110 are depicted, in an embodiment, a subset of the listed components and/or additional components not listed may be included in the UE 110. The UE 110 includes a digital signal processor (DSP) 502 and a memory 504. As shown, the UE 110 may further include an antenna and front end unit 506, a radio frequency (RF) transceiver 508, an analog baseband processing unit 510, a microphone 512, an earpiece speaker 514, a headset port 516, an input/output interface 518, a removable memory card 520, a universal serial bus (USB) port 522, a short-range wireless communication subsystem 524, an alert 526, a keypad 528, a liquid crystal display (LCD), which may include a touch-sensitive surface 530, an LCD controller 532, a charge-coupled device (CCD) camera 534, a camera controller 536, and a global positioning system (GPS) sensor 538. In an embodiment, the UE 110 may include another kind of display that does not provide a touch-sensitive screen. In an embodiment, the DSP 502 may communicate directly with the memory 504 without passing through the input/output interface 518.
The RF transceiver 508 provides frequency shifting, converting received RF signals to baseband and converting baseband transmit signals to RF. In some descriptions a radio transceiver or RF transceiver may be understood to include other signal processing functionality such as modulation/demodulation, coding/decoding, interleaving/deinterleaving, spreading/despreading, inverse fast Fourier transforming (IFFT)/fast Fourier transforming (FFT), cyclic prefix appending/removal, and other signal processing functions. For the purposes of clarity, the description here separates the description of this signal processing from the RF and/or radio stage and conceptually allocates that signal processing to the analog baseband processing unit 510 and/or the DSP 502 or other central processing unit. In some embodiments, the RF Transceiver 508, portions of the Antenna and front end unit 506, and the analog baseband processing unit 510 may be combined in one or more processing units and/or application specific integrated circuits (ASICs).
The DSP 502 may communicate with a wireless network via the analog baseband processing unit 510. In some embodiments, the communication may provide Internet connectivity, enabling a user to gain access to content on the Internet and to send and receive e-mail or text messages. The input/output interface 518 interconnects the DSP 502 and various memories and interfaces. The memory 504 and the removable memory card 520 may provide software and data to configure the operation of the DSP 502. Among the interfaces may be the USB interface 522 and the short-range wireless communication subsystem 524. The USB interface 522 may be used to charge the UE 110 and may also enable the UE 110 to function as a peripheral device to exchange information with a personal computer or other computer system. The short-range wireless communication subsystem 524 may include an infrared port, a Bluetooth interface, an IEEE 802.11 compliant wireless interface, or any other short-range wireless communication subsystem, which may enable the UE 110 to communicate wirelessly with other nearby UEs and/or wireless base stations.
The keypad 528 couples to the DSP 502 via the interface 518 to provide one mechanism for the user to make selections, enter information, and otherwise provide input to the UE 110. The keyboard 528 may be a full or reduced alphanumeric keyboard such as QWERTY, Dvorak, AZERTY and sequential types, or a traditional numeric keypad with alphabet letters associated with a telephone keypad. The input keys may include a trackwheel, an exit or escape key, a trackball, and other navigational or functional keys, which may be inwardly depressed to provide further input function. Another input mechanism may be the LCD 530, which may include touch-screen capability and also display text and/or graphics to the user. The LCD controller 532 couples the DSP 502 to the LCD 530.
The RAM 1330 might be used to store volatile data and perhaps to store instructions that are executed by the processor 1310. The ROM 1340 is a non-volatile memory device that typically has a smaller memory capacity than the memory capacity of the secondary storage 1350. ROM 1340 might be used to store instructions and perhaps data that are read during execution of the instructions. Access to both RAM 1330 and ROM 1340 is typically faster than to secondary storage 1350. The secondary storage 1350 is typically comprised of one or more disk drives or tape drives and might be used for non-volatile storage of data or as an overflow data storage device if RAM 1330 is not large enough to hold all working data. Secondary storage 1350 may be used to store programs that are loaded into RAM 1330 when such programs are selected for execution.
The I/O devices 1360 may include liquid crystal displays (LCDs), touch-screen displays, keyboards, keypads, switches, dials, mice, track balls, voice recognizers, card readers, paper tape readers, printers, video monitors, or other well-known input devices. Also, the transceiver 1325 might be considered to be a component of the I/O devices 1360 instead of or in addition to being a component of the network connectivity devices 1320. Some or all of the I/O devices 1360 may be substantially similar to various components depicted in the previously described drawing of the UE 110, such as the display 402 and the input 404.
The following 3rd Generation Partnership Project (3GPP) Technical Specification (TS) is incorporated herein by reference: TS 24.229 V7.8.0 (2007.12).
store an operator policy indicating whether to allow suppression of public user identifiers and location information within emergency requests;
receive an emergency request from a user equipment (UE);
send a response to the emergency request to the UE containing an indicator comprising a P-Asserted-Identity header field indicating that the UE had made the emergency request;
when the emergency request contains a request for privacy in relation to information associated with the UE and when the operator policy allows suppression of public user identifiers and location information within emergency requests, remove at least some of the information associated with the UE from the emergency request; and
forward the request to a Public Safety Answering Point (PSAP).
2. The apparatus of claim 1, wherein the network component is an emergency call session control function (E-CSCF).
3. The apparatus of claim 1, wherein the at least some of the information associated with the UE comprises a UE identity.
4. The apparatus of claim 1, wherein the at least some of the information associated with the UE comprises a UE location.
5. The apparatus of claim 1, wherein the at least some of the information associated with the UE comprises UE access network information.
6. The apparatus of claim 1, wherein the emergency request is a second message which is received by the network component from the UE after the network component sends the response to the emergency request to the UE containing the indicator indicating that the UE had made a previous emergency request.
7. The apparatus of claim 6, wherein the UE is unaware that the previous emergency request was related to an emergency.
8. The apparatus of claim 1, wherein the emergency request includes the at least some of the information associated with the UE.
9. The apparatus of claim 1, wherein the network component is further configured to, prior to forwarding the emergency request to the PSAP, select the PSAP based on the at least some of the information associated with the UE.
10. The apparatus of claim 9, wherein the at least some of the information associated with the UE includes location information.
11. The apparatus of claim 9, wherein the network component is further configured to remove a location object from the emergency request.
12. The apparatus of claim 9, wherein the network component is further configured to remove a geolocation header field from the emergency request.
13. The apparatus of claim 9, wherein the network component is further configured to remove from the emergency request a Globally Routable UA (User Agent) (URI) Uniform Resource Identifier (GRUU).
storing an operator policy in network equipment indicating whether to allow suppression of public user identifiers and location information within emergency requests;
receiving an emergency request from a user equipment (UE);
sending a response to the emergency request to the UE containing an indicator comprising a P-Asserted-Identity header field indicating that the UE had made the emergency request;
when the emergency request contains a request for privacy, in relation to information associated with the UE and when the operator policy allows suppression of public user identifiers and location information within emergency requests, removing at least some of the information associated with the UE from the emergency request; and
forwarding the request to a Public Safety Answering Point (PSAP).
15. The method of claim 14, wherein the method is implemented by a network component.
16. The method of claim 14, wherein the network component is an emergency call session control function (E-CSCF).
17. The method of claim 14, wherein the at least some of the information associated with the UE comprises a UE identity.
18. The method of claim 14, wherein the at least some of the information associated with the UE comprises a UE location.
19. The method of claim 14, wherein the at least some of the information associated with the UE comprises UE access network information.
20. The method of claim 14, wherein the emergency request is a second message which is received by a network component from the UE after the network component sends the response to the emergency request to the UE containing the indicator indicating that the UE had made a previous emergency request.
21. The method of claim 14, wherein the UE is unaware that the previous emergency request was related to an emergency.
22. The method of claim 14, wherein the emergency request includes the at least some of the information associated with the UE.
23. The method of claim 14, further comprising, prior to forwarding the emergency request to the PSAP, selecting the PSAP based on the at least some of the information associated with the UE.
24. The method of claim 23, wherein the at least some of the information associated with the UE includes location information.
25. The method of claim 23, further comprising removing a location object from the emergency request.
26. The method of claim 23, further comprising removing a geolocation header field from the emergency request.
27. The method of claim 23, further comprising removing from the emergency request a Globally Routable UA (User Agent) (URI) Uniform Resource Identifier (GRUU).
US13244795 2008-06-02 2011-09-26 Privacy-related requests for an IMS emergency session Active US8369824B2 (en)
US99441611 true 2011-03-02 2011-03-02
US20120015623A1 true US20120015623A1 (en) 2012-01-19
US8369824B2 true US8369824B2 (en) 2013-02-05
US9380523B1 (en) * 2013-01-22 2016-06-28 Hypori, Inc. System, method and computer program product for connecting roaming mobile devices to a virtual device platform
US20070117539A1 (en) 2005-11-23 2007-05-24 Research In Motion Limited Notification of a received message in a wireless mobile communication device based upon authentication
WO2008022554A1 (en) 2006-08-16 2008-02-28 Huawei Technologies Co., Ltd. Method and apparatus for transmit-receiving emergency services
EP1906638A1 (en) 2005-06-30 2008-04-02 Huawei Technologies Co., Ltd. A geographic location information inquiry method and system in packet domain
US20080310599A1 (en) 2007-06-15 2008-12-18 Research In Motion Limited System and Method for Indicating Emergency Call Back to User Equipment
US20110119340A1 (en) 2008-01-10 2011-05-19 Johannes Van Elburg Message handling in a communications network
US20110095886A1 (en) 2008-06-02 2011-04-28 Research In Motion Limited Coding and Behavior When Receiving an IMS Emergency Session Indicator From Authorized Source
US20120028598A1 (en) 2008-06-02 2012-02-02 Research In Motion Limited Privacy-Related Requests for an IMS Emergency Session
3GPP TS 24.229 V7.11.0; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; IP Multimedia Call Control Protocol Based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3, Release 7; Section 5.1.2A; Mar. 2008; pp. 1-15 and 49-53.
3GPP TS 24.229 v7.11.0; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; IP Multimedia Call Control Protocol Based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3; Release 7; Mar. 2008; 434 pages.
3GPP TS 24.229 v8.3.0; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; IP Multimedia Call Control Protocol Based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3; Release 8; Mar. 2008; 495 pages.
3GPP TS 24.403 v1.8.1; 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Call Control Protocol Based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3; Release 7; Dec. 2007; 96 pages.
3GPP TSG CT WG1 Meeting #49; "Corrections for Emergency Procedures"; C1-072991; Nokia Siemens Networks, Nokia, Ericsson; Kobe, Japan; Oct. 8-12, 2007; 8 pgs.
3GPP, ETSI TS 124 008, Apr. 2008, version 7.11.0, pp. 1-551.
ETSI TS 124 229 v8.3.0; Digital Cellular Telecommunications System (Phase 2+): Universal Mobile Telecommunications System (UMTS); Internet Protocol (IP) Multimedia Call Control Protocol Based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3; (3GPP TS 24.229 version 8.3.0 Release 8); Apr. 2008; pp. 1-125. Part 1.
ETSI TS 124 229 v8.3.0; Digital Cellular Telecommunications System (Phase 2+): Universal Mobile Telecommunications System (UMTS); Internet Protocol (IP) Multimedia Call Control Protocol Based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3; (3GPP TS 24.229 version 8.3.0 Release 8); Apr. 2008; pp. 126-250. Part 2.
ETSI TS 124 229 v8.3.0; Digital Cellular Telecommunications System (Phase 2+): Universal Mobile Telecommunications System (UMTS); Internet Protocol (IP) Multimedia Call Control Protocol Based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3; (3GPP TS 24.229 version 8.3.0 Release 8); Apr. 2008; pp. 251-375 Part 3.
ETSI TS 124 229 v8.3.0; Digital Cellular Telecommunications System (Phase 2+): Universal Mobile Telecommunications System (UMTS); Internet Protocol (IP) Multimedia Call Control Protocol Based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3; (3GPP TS 24.229 version 8.3.0 Release 8); Apr. 2008; pp. 376-497 Part 4.
European Examination Report; EP Application No. 09759254.7; Apr. 5, 2011; 8 pgs.
European Examination Report; EP Application No. 09759255.4; Apr. 8, 2011, 6 pgs.
Office Action issued in corresponding Canadian Patent Application No. 2,726,628 dated Jul. 5, 2012, 3 pgs.
Office Action issued in corresponding Mexican Patent Application No. MX/a/2010/013081 dated Jun. 15, 2012, 6 pgs, no translation.
PCT International Preliminary Report on Patentability; PCT Application No. PCT/US2009/045987; Dec. 6, 2010; 7 pgs.
PCT International Preliminary Report on Patentability; PCT Application No. PCT/US2009/045990; Dec. 6, 2010; 6 pgs.
PCT International Preliminary Report on Patentability; PCT Application No. PCT/US2009/045992; Dec. 6, 2010; 8 pgs.
PCT International Search Report; PCT Application No. PCT/US2009/045987; Sep. 7, 2009; 3 pgs.
PCT International Search Report; PCT Application No. PCT/US2009/045990; Sep. 7, 2009; 3 pgs.
PCT International Search Report; PCT Application No. PCT/US2009/045992; Sep. 15, 2009; 3 pgs.
PCT Written Opinion of the International Searching Authority; PCT Application No. PCT/US2009/045987; Sep. 7, 2009; 6 pgs.
PCT Written Opinion of the International Searching Authority; PCT Application No. PCT/US2009/045990; Sep. 7, 2009; 6 pgs.
PCT Written Opinion of the International Searching Authority; PCT Application No. PCT/US2009/045992; Sep. 15, 2009; 7 pgs.
Rosen et al., Best Current Practices for Communications Services in Support of Emergency Calling, Feb. 27, 2006, draft-rosen-sos-phonebcp-00.txt. *
Schulzrinne, "A Uniform Resource Name (URN) for Emergency and other Well-Known Services," Jan. 2008, RFC 5031, pp. 1-15.
Taylor et al., Security Threats and Requirements for Emergency Call Marking and Mapping, Jan. 2008, RFC 5069. *
Translation of Office Action issued in corresponding Japanese Patent Application No. 2011-511904 dated Aug. 7, 2012, 5 pgs.
Translation of Office Action issued in corresponding Japanese Patent Application No. 2011-511905 dated Aug. 7, 2012, 3 pgs.
Translation of Office Action issued in corresponding Korean Patent Application No. 10-2010-7029766 dated Jun. 1, 2012, 9 pgs.
Translation of Office Action issued in corresponding Korean Patent Application No. 10-2010-7029767 dated May 30, 2012, 8 pgs.
USPTO Office Action dated Apr. 4, 2011, in copending U.S. Appl. No. 12/131,785, filed Jun. 2, 2008, 15 pages.
USPTO Office Action dated Jun. 7, 2011, in copending U.S. Appl. No. 12/935,826, filed Dec. 13, 2010, 7 pages.
USPTO Office Action dated Oct. 19, 2011, in copending U.S. Appl. No. 12/131,785, filed Jun. 2, 2008, 12 pages.
USPTO Office Action dated Sep. 19, 2011, in copending U.S. Appl. No. 12/935,826, filed Dec. 13, 2010, 8 pages.
USPTO Office Action issued in corresponding U.S. Appl. No. 12/131,779 dated Mar. 1, 2012, 29 pgs.
USPTO Office Action issued in corresponding U.S. Appl. No. 12/131,779 dated Sep. 17, 2012, 20 pgs.
USPTO Office Action issued in corresponding U.S. Appl. No. 12/131,790 dated Jan. 5, 2012, 37 pgs.
USPTO Office Action issued in corresponding U.S. Appl. No. 12/935,826 dated Feb. 10, 2012, 7 pgs.
USPTO Office Action issued in corresponding U.S. Appl. No. 12/937,199 dated Aug. 16, 2012, 17 pgs.
USPTO Office Action issued in corresponding U.S. Appl. No. 12/937,199 dated Mar. 6, 2012, 15 pgs.
USPTO Office Action issued in corresponding U.S. Appl. No. 12/994,416 dated Jan. 9, 2012, 36 pgs.
US20090296689A1 (en) 2009-12-03 application
US20100103927A1 (en) 2010-04-29 Method and apparatus for interworking sip communication waiting with circuit switching and packet switching nodes
US20090119382A1 (en) 2009-05-07 Content Disposition System and Method for Processing Message Content in a Distributed Environment
US20110188416A1 (en) 2011-08-04 System and method for packetized emergency messages
US20120185604A1 (en) 2012-07-19 System and method for indicating callee preferences
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:RESEARCH IN MOTION CORPORATION;REEL/FRAME:027034/0016
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BAKKER, JAN HENDRIK LUCAS;BUCKLEY, ADRIAN;ALLEN, ANDREW MICHAEL;SIGNING DATES FROM 20101119 TO 20101122;REEL/FRAME:027033/0990
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BARNES, CAREY LEGAL REPRESENTATIVE FOR NIGEL BARNES, DECEASED;REEL/FRAME:027047/0468
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:RESEARCH IN MOTION UK LIMITED;REEL/FRAME:027046/0418