Closed Bug 1118598 Opened 10 years ago Closed 10 years ago

[FFOS7715 v2.1]USAT case 27.22.4.11.1 SEND SS SEQ 1.1B fail,TR only contaims General Result,but not Additional information

Categories

(Firefox OS Graveyard :: Vendcom, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Jinghua.Xing, Unassigned)

References

Details

(Whiteboard: [sprd391239][POVB])

[Testing Steps ]:USAT case 27.22.4.11.1 SEND SS SEQ 1.1B SEND SS, call forward unconditional, all bearers, successful [Expected Result ]:case pass [Test Result ]:TERMINAL RESPONSE: SEND SS only contains General Result,but no Additional information: Operation Code and SS Parameters
As in ETSI TS 101 267 V8.18.0 6.4.11 : >once an SS Return Result message not containing an error has been received from the network, the ME shall inform >the SIM that the command has been successfully executed, using TERMINAL RESPONSE. This command shall include the >contents of SS Return Result as additional data. I think we should contain additional information in our response.
Flags: needinfo?(sku)
Whiteboard: [sprd391239]
As commented in bug 1117609 comment 9, the TR for SEND SS shall be handled in modem per the design of both FFOS and AOSP. (an UNSOLICITED_STK_EVENT_NOTIFY comes instead of UNSOLICITED_STK_PROACTIVE_COMMAND) /** * RIL_UNSOL_STK_EVENT_NOTIFY * * Indicate when SIM notifies applcations some event happens. * Generally, application does not need to have any feedback to * SIM but shall be able to indicate appropriate messages to users. * * "data" is a const char * containing SAT/USAT commands or responses * sent by ME to SIM or commands handled by ME, in hexadecimal format string * starting with first byte of response data or command tag * */ #define RIL_UNSOL_STK_EVENT_NOTIFY 1014 We expect this to be a vendor bug instead.
Component: Gaia → Vendcom
Flags: needinfo?(sku)
Whiteboard: [sprd391239] → [sprd391239][POVB]
Blocks: 1123554
Close as the corresponding sprd bug has been fixed.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.