Closed Bug 854834 Opened 11 years ago Closed 6 years ago

[Buri][SUPL] The SET should support SUPL Network initiated call flow

Categories

(Firefox OS Graveyard :: General, defect, P1)

Product:
Firefox OS Graveyard
Component:
General
Platform:
ARM
Gonk (Firefox OS)
Type:
defect

Tracking

(blocking-b2g:-)

Status:
RESOLVED WONTFIX
Project Flags:
blocking-b2g -

People

(Reporter: sync-1, Unassigned)

Details

Attachments

(1 file)

Spec
3.00 MB, application/octet-stream
Details 
+++ This bug was initially created as a clone of Bug #429646 +++
 
 Created an attachment (id=374585)
 QXDM log
 
 Contact info:021-61460666-6138 
 
 DEFECT DESCRIPTION:
 The SET should support SUPL Network initiated call flow
 
 REPRODUCING PROCEDURES
 1.SUPL address is :slp.rs.de;port number is :7275
 2.Start a NI(Network initiated) Location Session,after the Conformance Test Tool sends SUPL INIT to the SET,the SET does not have any respond--K.O.
 EXPECTED BEHAVIOUR:
 
 ASSOCIATE SPECIFICATION:
 The SET should responds with SUPL POS INIT (proxy mode)  and the Location Session completes successfully.
 
 TEST PLAN REFERENCE:
 Test Case ID B2G-79557 SUPL-1.0-con-000
 
 TOOLS AND PLATFORMS USED:
 
 USER IMPACT:
 
 REPRODUCING RATE:
 100%
 
 For FT PR, Please list reference mobile's behavior:
 
 ++++++++++ end of initial bug #429646 description ++++++++++
 
 
 Can B2G support SUPL NI position?
 
 
 
 CONTACT INFO (Name,Phone number):
 
 DEFECT DESCRIPTION:
 
 REPRODUCING PROCEDURES:
 
 EXPECTED BEHAVIOUR:
 
 ASSOCIATE SPECIFICATION:
 
 TEST PLAN REFERENCE:
 
 TOOLS AND PLATFORMS USED:
 
 USER IMPACT:
 
 REPRODUCING RATE:
 
 For FT PR, Please list reference mobile's behavior:
blocking-b2g: --- → tef?
Hi Amelie, NI is not currently supported in v1.0.1
(In reply to comment #1)
 > Comment from Mozilla:Hi Amelie, NI is not currently supported in v1.0.1
 > 
 
 If SUPL is supported, then NI is mandatory to pass SUPL certification.
Why NI not support now?
 
 I have readed the code in GONK layer, it almost same as android.
 So, if QCT can support NI, B2G should have capacity to support it.
Yes we support NI in Gonk.  However there is nothing in Gecko and Gaia to carry this up to the user.
kan-ru, do we support SUPL NI? thanks
Flags: needinfo?(kchen)
triage: this is not a blocker for release markets
blocking-b2g: tef? → -
Attached file Spec — 
OMA-ETS-SUPL-V1_0-20090721-C is the SUPL test cases.
   OMA-AD-SUPL-V1_0-20070615-A is the SUPL architecture
   OMA-TS-ULP-V1_0-20070615-A is the ULP protocol description.
(In reply to Cheng-An, XIONG from comment #7)
> Created attachment 730149 [details]
> Spec
> 
>    OMA-ETS-SUPL-V1_0-20090721-C is the SUPL test cases.
>    OMA-AD-SUPL-V1_0-20070615-A is the SUPL architecture
>    OMA-TS-ULP-V1_0-20070615-A is the ULP protocol description.

Can you please provide me the exact sentence where the spec says that you need to implement the complete spec or otherwise you can implement nothing?
Flags: needinfo?(chengan.xiong)
(In reply to Joe Cheng [:jcheng] from comment #6)
> triage: this is not a blocker for release markets

1. If SUPL is supported, then NI is mandatory to pass SUPL certification.
2. if NI is not supported, then
  2.1 if declare don't support SUPL, then need remove all UI related to SUPL
  2.2 otherwise, what declared will be inconsistent with phone behavior
blocking-b2g: - → tef?
Flags: needinfo?(chengan.xiong)
(In reply to Daniel Coloma:dcoloma from comment #8)
> (In reply to Cheng-An, XIONG from comment #7)
> > Created attachment 730149 [details]
> > Spec
> > 
> >    OMA-ETS-SUPL-V1_0-20090721-C is the SUPL test cases.
> >    OMA-AD-SUPL-V1_0-20070615-A is the SUPL architecture
> >    OMA-TS-ULP-V1_0-20070615-A is the ULP protocol description.
> 
> Can you please provide me the exact sentence where the spec says that you
> need to implement the complete spec or otherwise you can implement nothing?

OMA-RD-SUPL-V1_0-20070615-A.pdf,
Section 6.1 High-Level Functional Requirements => 6.1.1 General  => 

2. SUPL SHALL support Network-initiated location requests. Network-initiated locating use cases SHALL support P2P (point-to-point) connections and they, if technically feasible, MAY support P2M (point-to-multipoint) connections for emergency. For example, a P2M (point-to-multiple) connection which broadcasts to multiple devices/users is useful for emergency services, especially in a building or hot spot area.
(In reply to Cheng-An, XIONG from comment #10)
> (In reply to Daniel Coloma:dcoloma from comment #8)
> > (In reply to Cheng-An, XIONG from comment #7)
> > > Created attachment 730149 [details]
> > > Spec
> > > 
> > >    OMA-ETS-SUPL-V1_0-20090721-C is the SUPL test cases.
> > >    OMA-AD-SUPL-V1_0-20070615-A is the SUPL architecture
> > >    OMA-TS-ULP-V1_0-20070615-A is the ULP protocol description.
> > 
> > Can you please provide me the exact sentence where the spec says that you
> > need to implement the complete spec or otherwise you can implement nothing?
> 
> OMA-RD-SUPL-V1_0-20070615-A.pdf,
> Section 6.1 High-Level Functional Requirements => 6.1.1 General  => 
> 
> 2. SUPL SHALL support Network-initiated location requests. Network-initiated
> locating use cases SHALL support P2P (point-to-point) connections and they,
> if technically feasible, MAY support P2M (point-to-multipoint) connections
> for emergency. For example, a P2M (point-to-multiple) connection which
> broadcasts to multiple devices/users is useful for emergency services,
> especially in a building or hot spot area.

That is not saying what I am asking you about.
(In reply to Daniel Coloma:dcoloma from comment #11)
> > OMA-RD-SUPL-V1_0-20070615-A.pdf,
> > Section 6.1 High-Level Functional Requirements => 6.1.1 General  => 
> > 
> > 2. SUPL SHALL support Network-initiated location requests. Network-initiated
> > locating use cases SHALL support P2P (point-to-point) connections and they,
> > if technically feasible, MAY support P2M (point-to-multipoint) connections
> > for emergency. For example, a P2M (point-to-multiple) connection which
> > broadcasts to multiple devices/users is useful for emergency services,
> > especially in a building or hot spot area.
> 
> That is not saying what I am asking you about.

this is the requirement about SUPL from the offical SPEC. according to the SPEC, If declare SUPL, then NI should support. otherwise can't declare support SUPL. If declare no SUPL, then all UI should be removed because phone behavior should be consistent with certification documentation.
(In reply to Cheng-An, XIONG from comment #12)
> (In reply to Daniel Coloma:dcoloma from comment #11)
> > > OMA-RD-SUPL-V1_0-20070615-A.pdf,
> > > Section 6.1 High-Level Functional Requirements => 6.1.1 General  => 
> > > 
> > > 2. SUPL SHALL support Network-initiated location requests. Network-initiated
> > > locating use cases SHALL support P2P (point-to-point) connections and they,
> > > if technically feasible, MAY support P2M (point-to-multipoint) connections
> > > for emergency. For example, a P2M (point-to-multiple) connection which
> > > broadcasts to multiple devices/users is useful for emergency services,
> > > especially in a building or hot spot area.
> > 
> > That is not saying what I am asking you about.
> 
> this is the requirement about SUPL from the offical SPEC. according to the
> SPEC, If declare SUPL, then NI should support. otherwise can't declare
> support SUPL. 

OK, this is clear.

> If declare no SUPL, then all UI should be removed because
> phone behavior should be consistent with certification documentation.

This is what I do not understand at all. I've seen many devices through my life implementing partially standards and in some cases claiming they are compliant and in some others not saying anything about the standard at all. 

Nothing forbids you to implement partially a standard or a specification.
joe, We do not support NI currently.
Flags: needinfo?(kchen)
Marking it as tef- as this is a feature Out of v1.0.1 scope
blocking-b2g: tef? → -
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: