Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TR 22.908  Word version:  18.0.1

Top   Top   Up   Prev   None
1…   4…   4.2   4.3   5…   6…   A…   A.2.2…   A.2.4…   A.3   B…

 

B  Issuesp. 23

B.1  Introductionp. 23

This clause identifies the issues, which are not within the scope of SA1 WG; thus, this clause is not to restrict further technical work.

B.2  Issue and conclusionp. 23

Impact of PPAC function on the UE
The PPAC applies to either all UEs or to a group of UEs
  • In the present TR the use-case of an emergency situation is described and this is not a subscription-based service; therefore PPAC capability applies to all UEs or to a group of UEs.
  • PPAC is not only for communication from authorized users (e.g. government, emergency responder) to unauthorized users but it includes the case of communication between unauthorized users. If the PPAC capability is different for each use-case, the originating side will be a key player, but differentiating the solution for each use-case is not a appropriate way forward. Therefore, PPAC should be independent from the capabilities of the originating side and PPAC is essentially the capability in terminating side. Thus where the capability is within terminating side, PPAC capability applies to all UEs or to a group of UEs.
  • Current access class restriction or domain-specific access control applies to all UEs or to a group of UEs, therefore PPAC capability should also apply to all UEs or to a group of UEs.
Conclusion
Considering above, PPAC applies to all UEs or to a group of UEs.
Up

$  Change historyp. 24


Up   Top