06079 PSAWG Special Meeting: ISSI Packet Data Architecture

1
06-079 PSAWG Special MeetingISSI Packet Data
Architecture

• July 11-13, 2006
• Tom Hengeveld, Tyco/Electronics M/A-COM, Chair

2
Important Notice for Participation and Call for
IPR
3
Goal of the Meetings

• Arrive at a concensus architecture for Packet
  Data over the ISSI
• Develop a common understanding of SNDCP
• Identify target cases/requirements including
  network models
• Develop concensus Functional Model
• What are all the pieces parts involved, how are
  they interconnected, and what protocols are used
  to connect them?
• What is the role of an Access Point?
• What protocol covers the relationship between an
  Access Point and an SNDCP end-point?
• Other Concerns
• Develop a concensus primitive model
• Assign an author/authors for the next draft of
  the Architecture section

4
Agenda for the Meetings

• Attendance by Sign-in Sheet
• Tuesday
• Background - A Common Understanding of SNDCP
• Overview of SNDCP Context Establishment Data
  Elements (This ppt, Tom Hengeveld)
• EADS/NN Presentation on Context Activation
• Discussion of De-registration (Jim Eastwood)
• Other Questions
• Target Environment/Network Models
• Target Model Cases (this ppt, Tom Hengeveld)
• 06-078 Lucent Misc. Comments through Slide 8 (Tom
  Chu)
• I/P Address Assignment (EADS/NN Presentation?)
• Functional Model (Wednesday)
• System Functional Model/Identification of Parts
• Decomposition by Home/Serving RFSS
• Lucent Misc. Comments Remaining Slides
• Primitive Model (Thursday)

5
Other Stuff

• Start at 8/830 each day
• The hotel made me buy a certain amount of food,
  so
• Theyll be coffee and stuff (as you see) each
  morning.
• Ive got afternoon coffee and beverages coming at
  2
• Lunch on your own (noonish to 1pm)
• Various breaks as we need

6
Nearby Resturants

• Various Places
• Lilac Blossom Very Good Chinese Right out of
  the parking lot, or walk about ¾ of a mile.
• Panera Left out of the parking lot, turn into
  shaws plaza, right and right again, or walk
  about ¾ of a mile.
• Legal Seafoods if you want to drive to the
  Burlington Mall Best Fish Anywhere, no contest,
  not cheap.
• Giorgios Amherst NH Good Italian with Good
  Martinis
• Bertucchis Nasha on 101A Brick Oven Italian
• YuYus Japanese Great Sushi, Good Bar Exit
  6
• Bugaboo Creek Outback from Canada
• Marthas Very Good Beer in the Center of Nashua
  (CON)
• Surf Not my favorite but people like it. Fish
  with too much sauce in the CON.

• Margaritas Somewhere in the CON, decent
  tex-mex with a good bar
• On the Strip
• Left out of the parking lot, right at Danial
  Webster
• Longhorn Steakhouse
• Lui Luis Italian
• Unos
• Chilis
• Smokey Bones
• Outback
• On the Border
• Left at Danial Webster
• Mexican place on the right that I dont know the
  name of but it doesnt totally stink.

7
A Common Understanding of SNDCP Slides to
stimulate conversation
8
Context Activation
RFSS
MRC
Activate Context Request
Activate Context Accept
Activate Context Reject
If the RFSS doesnt like a setting suggested by
the mobile, does it reject the request, or
suggest different settings?
RFSS
MRC
IP Packet?
Activate Context Command
Activate Context Request
Activate Context Accept
9
Apparently, it looks like this
Access Point 1
User Network 1
???
MRC SNDCP End-point
FNE SNDCP End-point
Access Point n
User Network n
10
A Picture from BAEB-A
11
A Paragraph from BAEB-A
12
Another paragraph from BAEB-A
13
Another paragraph from BAEB-A
14
Negotiated SNDCP Parameters
ACR Activate Context Request, ACA Activate
Context Accept X Interested, C Controls, P
Present
15
Negotiated SNDCP Parameters
16
Other questions

• Why does PPP have significance over the air?
  Jim Eastwood
• Why do we send PPP information in the PCO value
  over the air?
• How is priority used in SNDCP?
• Can multiple contexts share an IP address? (u1 on
  EADS/NN proposal)

17
Key Discriminators
CP M1
Ed
Ed
Context Activation
Context Transfer
Home M1
Home M2
Serving M1 New
H2H Data Tunnel
Serving/ Home Tunnel
Serving/Home Tunnel
Serving/Home Tunnel
Context Modification
Context Transfer
Context Deactivation
Serving M1 Old
M1
Serving M2
M2
18
We Agree
19
We agree

• BAEB-A (pg 45, 4.4.5.2) requires sequential use
  of NSAPIs by the MRC. We believe that this
  restriction should be removed (TAH has an action
  to send something to 8.05 to make this happen).
• BAEB-A (4.4.4.1,4.4.4.2) allow the RFSS to change
  Ready timer value with unsolicited Context
  Accept, we believe it would be useful to extend
  this to the DAC value.
• Maybe on compression and other values as well.
  (Jackson has an action to enumerate candidates
  and well figure out the right behaviors)
• That AABD should clarify what makes you become
  unregistered.
• That we need to go all the wayto 3 on the
  target model cases that we agree on slide.
• We agree that a mobile or FES ip address is
  unique within an APN
• EADS requires that we not preclude MRC addresses
  being allocated from the address space of the
  ISSI
• Moto (And M/A-COM) require that we not preclude
  MRC addresses being allocated from the address
  space of the customer premises

20
We also agree

• That mobiles from a particular addressing realm
  may be homed to different home RFSSs
• That different customer agencies that have no
  need to talk to each other may have overlapping
  address spaces distinguished over the air by the
  APN.
• That different customer premises with the same
  APN may exist.

21
we seem to agree that the ISSI cannot preclude
thisImplementation of Ed
CP 1
Consistent IP Network
10.12.1.
Ed
ITA 10.12.1.x
CP 1 10.12.2.x
10.12.2.
IT A
RFG
Ed
MR1 10.12.3.x
Prop.
RFG
Home RFSS MR1
Ed
10.12.0.0
Ed
Prop.
RFG
MR1
Prop.
10.12.3.
Home RFSS MR2
RFG
10.12.4.
Prop.
MR2
22
Nor can it preclude this implementation of Ed
CP 1
10.12.1.1
Ed
SRC CP1 10.12.1.1
Dest MR1 10.12.3.1
For each IP address, destination tunnel
(H-MR1(APN1))
Fred
10.12.2.
IT A
SRC Fred 10.1.1.17
Dest MRC Address in ISSI Space 10.1.99.1
Ed
Dest home RFSS 10.1.1.1
SRC CP1 10.12.1.1
Dest MR1 10.12.3.1
Larry
Home RFSS MR1 (10.1.1.1)
For each APN, he has an rx addr (or addr/port)
Home RFSS MR2
MR1
10.12.3.1
10.12.4.
MR2
23
At this level of complexity, we still seem to
agree
Agency 1
CP 2
10.12.1.
Ed
ITA 10.12.1.x
CP 1 10.12.2.x
CP 1
10.12.1.
Ed
10.12.2.
IT B
MR1 10.12.3.x
10.12.0.0
RFG
Ed
10.12.2.
Prop.
IT A
SAME STINKING IP ADDRESSES
RFG
RFG
Ed
Agency 2
Prop.
Prop.
ITB 10.12.1.x
CP 2 10.12.2.x
RFG
Home RFSS
Prop.
10.12.3.
MR2 10.12.3.x
10.12.0.0
MR110.12.4.1
MR2 10.12.4.1
EADS Wants to standardize this interface.
24
Silly Notes

• Home RFSS (?) needs to be able to route packets
  between mobiles in the same APN?
• It might make sense to define a PSAWG work item
  to add greater specificity to Ed
• We believe that it makes sense to constitute an
  ad hoc group to explore interoperation of BB, WB,
  HSD and P25 data.

25
Big Hairy Issues

• The use of the APN is not clearly defined. It is
  identified as (potentially) representing any of
  three different things
• Vague definition from BAEB-A
• SNDCP endpoint within the FNE
• may identify the Packet Data Network
• optionally a service to be offered
• We believe that a mobile or FES IP address is
  unique within an APN, ask 8.somebody to confirm.
• We believe it would be useful for the A-interface
  to have a mechinism for specifying to the MRC the
  APN of the MDP.
• There is currently no standardized way to
  negotiate SNDCP parameters (particularly
  compression parameters). We believe that 8.05
  should clarify the details of SNDCP parameter
  negotiation.

26
Target Model Cases (That we agree on)

• MRC/MDP share an IP address (or no MDP)
• Most restrictive, easiest to implement in ISSI
• Can there be more than one NSAPI in this case?
  Not with the present definition of SNDCP
• MRC and gt 0 MDPs in the same address domain, not
  subnetted
• Multiple NSAPIs
• MRC and gt 0 MDPs, in different address domains
  with MDPs sharing a common address domain

27
Target modes for further study

• MRC and gt 0 MDPs in the same address domain,
  subnetted
• Single NSAPI
• EADS/NN believe this is an important case to
  reduce number of context activations required
• Moto imagines that this might be implemented as
  multiple NSAPIs with a single context activation
  message
• MRC and gt 0 MDPs, all in potentially different
  address domains
• Least restrictive
• Prefer not to preclude this, and we dont imagine
  that we will, but we dont want to require
  manufacturers to support this in the MRC.

28
We agree that this is a required configuration
Unique Address of one of these things is APN,IP
Address
MES
MDP2
MDP3
MRC
MDP 2 10.12.4.1
MDP 3 10.12.4.2
MRC 10.12.4.1
Access Point Network 2
Access Point Network 3
29
And so is this
Unique Address of one of these things is APN,IP
Address
MES
MDP2
MDP3
MRC
MDP 2 10.12.4.1
MDP 3 10.12.4.2
MRC 10.12.4.1
Access Point Network 2
Access Point Network 3
30
Mobile to Mobile Data in the same APN
We agree that the green line must be supported,
but that a customer should have the option of the
red line.
CP 1
Ed
Ed
Home 1
Home 2
G
M1
M2
31
Things to do before were done

• Outline/Storyboard figures for Architecture
• Functional Decomposition/Assignment of Functions
  to Pieces parts
• Primitive Model
• Draft mapping of primitives to messages
• By August 12