Tech-invite 3GPPspace IETFspace

21 22 23 24 25 26 27 28 29 31 32 33 34 35 36 37 38 4‑5x

Content for TR 23.700-97 Word version: 18.1.0

1… 4…

4 Key Issues p. 8

4.1 Key issue #1: Background Data Transfer negotiation p. 8

4.2 Key issue #2: Application server monitoring and control of traffic p. 8

4.3 Key issue #3: IoT Platform PSM monitoring and configuration p. 9

4.4 Key issue #4: Configuration of Communication Patterns p. 9

4.5 Key issue #5: NIDD configuration p. 10

4.6 Key issue #6: Device Triggering services. p. 10

5 Solutions p. 11

5.1 Solution #1: Application Service Management Service p. 11

5.1.1 Functional model for application service management p. 11

5.1.1.1 General p. 11

5.1.1.2 On-network functional model description p. 11

5.1.2 Functional entities description p. 11

5.1.2.1 General p. 11

5.1.2.2 Application service management client p. 11

5.1.2.3 Application service management server p. 12

5.1.3 Configuring VAL server p. 12

5.1.4 Request-response model p. 12

5.1.4.1 ASM server requesting for on-demand status p. 12

5.1.4.2 ASM Client pushes service experience report to the ASM Server p. 13

5.1.4.3 ASM Server pulls service experience report from the ASM Client p. 14

5.1.4.4 ASM Server determines corrective action p. 15

5.1.5 Subscribe-notify model p. 15

5.1.5.1 ASM server subscribes to the monitoring status information p. 15

5.1.5.2 VAL server notifies the monitoring status information p. 16

5.1.6 Reference Points p. 16

5.1.6.1 General p. 16

5.1.6.2 ASM-C p. 16

5.1.6.3 ASM-UU p. 16

5.1.6.4 ASM-S p. 16

5.2 Solution #2: IoT Platform deployment options p. 17

5.2.1 General p. 17

5.2.2 Deployment models in single PLMN operator domain p. 17

5.2.2.1 General p. 17

5.2.2.2 Single network exposure access model p. 17

5.2.2.3 Distributed network exposure access model p. 18

5.3 Solution #3: IoT Platform Functional Models p. 19

5.3.1 General p. 19

5.3.2 On-network functional models p. 19

5.4 Solution #4: Device triggering p. 22

5.4.1 General p. 22

5.4.2 Procedures and information flows p. 22

5.4.2.1 Procedure p. 22

5.4.3 Evaluation p. 23

5.5 Solution #5: Application Server status monitoring via CAPIF p. 23

5.5.1 Description p. 23

5.5.1.1 AS service status monitoring p. 23

5.5.2 Evaluation p. 24

5.6 Solution #6: BDT configuration p. 24

5.6.1 General p. 24

5.6.2 Procedures and information flows p. 24

5.6.2.1 General p. 24

5.6.2.2 Request and Select Background Data Transfer Policy p. 24

5.6.3 Evaluation p. 26

5.7 Solution #7: UE unified traffic pattern and monitoring management p. 27

5.7.1 General p. 27

5.7.2 Procedures and information flows p. 27

5.7.2.1 General p. 27

5.7.2.2 UE unified traffic pattern and monitoring management subscription procedure p. 27

5.7.2.4 Traffic pattern configuration request procedure p. 29

5.7.2.5 Information Flows p. 30

5.7.2.5.1 UE unified traffic pattern and monitoring management subscription request p. 30

5.7.2.5.2 UE unified traffic pattern and monitoring management subscription response p. 31

5.7.2.5.3 UE unified traffic pattern update notification p. 31

5.7.2.5.4 Traffic pattern configuration request p. 31

5.7.2.5.5 Traffic pattern configuration response p. 32

5.7.3 Management and 5GC exposure procedures p. 32

5.7.3.1 General p. 32

5.7.3.2 CP configuration procedure p. 32

5.7.3.3 UE unified traffic pattern management procedure p. 33

5.7.3.4 Network parameter coordination procedure p. 34

6 Overall Evaluation p. 35

6.1 Architecture evaluation p. 35

6.2 Solution evaluations p. 36

6.2.1 General p. 36

6.2.2 Key issue #2: Application server monitoring and control of traffic p. 36

7 Conclusions p. 37

7.1 Solution conclusions p. 37

$ Change history p. 39