hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 5.2.7 Security
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 5.2.7.1 General
| This clause specifies PIN security requirements.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 5.2.7.2 Requirements
| [AR-5.2.7.2-a] Communication between the functional entities of the application enablement layer architecture shall be protected.
[AR-5.2.7.2-b] Access control mechanisms for authenticating functional entities of the application enablement layer architecture shall be provided.
[AR-5.2.7.2-c] Access control mechanisms... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 5.2.8 Subscription service
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 5.2.8.1 General
| This clause specifies the requirements for PIN subscription service.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 5.2.8.2 Requirements
| [AR-5.2.8.2-a] The application enablement layer architecture shall provide subscription and notification mechanisms enabling to receive PIN modification information changes.
[AR-5.2.8.2-b] The application enablement layer architecture shall provide subscription and notification mechanisms enabling to receive PIN manag... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 5.2.9 PIN application KPIs
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 5.2.9.1 General
| This clause specifies the requirements for PIN application KPIs.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 5.2.9.2 Requirements
| [AR-5.2.9.2-a] The application enablement layer architecture shall provide mechanisms for the PEGC to publish its KPIs that the PEGC supported or gateway requirements.
[AR-5.2.9.2-b] The application enablement layer architecture shall provide mechanisms for the application client to publish its KPIs to operate effecti... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6 Application enablement layer architecture
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.1 General
| This clause provides the overall architecture description:
- Clause 6.2 describes the functional architecture;
- Clause 6.3 describes the functional entities;
- Clause 6.4 describes the reference points;
- Clause 6.5 describes the cardinality of functional entities and reference points.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.2 Architecture
| This clause describes the architecture for enabling personal IoT networks in a reference point representation, where existing interactions between any two functions (e.g., PINE, PEGC, PEMC, PIN-Server, etc.) is shown by an appropriate reference point (e.g. PIN-1, PIN-2, etc.).
This clause provides the reference point... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.2.1 General Architecture
| Figure 6.2.1-1 illustrates the reference point representation of the architecture for PINAPP.
Figure 6.2.1-1: PINAPP architecture
The PIN elements contains PIN client and/or application clients. The PIN Element with gateway capability (PEGC) performs the role of an entity supporting gateway capability for PIN. Th... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.2.2 Architecture of user accessing services provided by PIN Element from outside the PIN
| The Figure 6.2.2-1 shows the application architecture to enable authorized user to access services provided by PIN element behind the PEGC. For simplicity, not all functional elements of Figure 6.2.2-1 are shown in below Figure 6.2.2-1.
Figure 6.2.2-1: PINAPP architecture of User accessing services provided by PIN ... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.3 Functional entities
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.3.1 General
| This clause describes the functional entities of the architecture for enabling personal IoT networks.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.3.2 PIN client
| The PIN enabler layer entity residing in the PIN elements that provides the client side functionalities required for application clients in order to consume the services offered by the PIN or to offer services for other PIN elements to consume.
It provides the following functionalities:
- Registration of the availabl... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.3.3 PIN Management Client
| A PIN Element with Management Capability is a PIN Element that provides a means for an authorized administrator to configure and manage a PIN.
It provides following functionalities:
- For a network operator or authorized user to configure the policies of the PIN;
- Provide life span information of the PIN to the aut... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.3.4 PIN Gateway Client
| A PIN Element with Gateway Capability is a PIN Element that has the ability to provide connectivity to a PINE for data and signaling exchange with PEMC, other PIN Elements or the DN. It may act as both the Layer-3 type relay which transparently forwards the traffic for PINE, and the application layer relay which termin... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.3.5 PIN server
| A PIN server is deployed at network that provides server side functionalities required for managing the PIN.
It provides the following functionalities:
- Provisioning of configuration information to the PIN elements;
- Maintain the PIN profile for each PIN and PINE in PIN;
- PIN Management (Creation, modification a... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.3.6 Application Client
| An application client is the application resident in the PIN elements.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.4 Reference Points
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.4.1 General
| This clause defines the reference points between functional entities of PINAPP.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.4.2 PIN-1
| The interactions related to enabling PINAPP, between the Application client and the PIN client.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.4.3 PIN-2
| This reference point exists between PIN client and PEGC which connects PIN client of UE to PEGC. The PIN client uses this interface to communicate with other PIN clients within PIN or to access 3GPP network.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.4.4 PIN-3
| This reference point exists between the PIN client and PEMC and following functionalities are supported over this reference point:
- Authorizing PIN clients to access PIN;
- Discovery of services offered by other PIN elements;
- Discovery and selection of PIN elements;
- Notifying the PIN information modification ... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.4.5 PIN-4
| This reference point exists between the PEGC and PEMC and following functionalities are supported over this reference point:
- Authorizing PEGC for PIN access;
- Notification of PIN elements joining or leaving the PIN by PEMC to PEGC;
- Delivery of PIN dynamic profile information by PEMC to PEGC whenever it changes... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.4.6 PIN-5
| This reference point exists between the one PIN client and another PIN client and it supports direct connection over 3GPP or non-3GPP RAT. It also connects to PIN client of a PIN element to the PIN client of another PIN element.
NOTE: PIN-5 is out-of-scope of this release.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.4.7 PIN-6
| This reference point exists between the PEMC and PIN server and supports the following functionalities:
- Authorization of PEMC;
- Notifying PIN server whenever a PIN element joins or leaves the PIN, whenever a PIN client updates its capabilities;
- Notifying PIN server of PEGC replacement;
- Delivery of PIN dynami... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.4.8 PIN-7
| This reference point exists between the PEGC and PIN server for the interactions related to enabling PINAPP
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.4.9 PIN-8
| This reference point exists between the PIN server and 3GPP core network for the interactions related to enabling PINAPP. It supports:
- UE's (PINE) location information retrieval as specified in clause 4.15.3 of 3GPP TS 23.502 [5].
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.4.10 PIN-9
| This reference point exists between the application server and PIN server for the interactions related to enabling PINAPP. This reference point is an instance of CAPIF-2/2e reference point as specified in 3GPP TS 23.222 [7].
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.4.11 PIN-10
| This reference point exists between the PIN client in PIN element and PIN server for the interactions related to enabling PINAPP.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.4.12 PIN-11
| This reference point exists between the PEGC and PIN client from outside the PIN to access the services provided by PIN elements within the PIN.
PIN-11 utilizes Uu reference point as described in 3GPP TS 23.501[4].
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.4.13 PIN-12
| This reference point exists between the PEMC and PIN client for configuring and managing the PIN from outside the PIN.
PIN-12 utilizes Uu reference point as described in 3GPP TS 23.501[5].
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.5 Cardinality rules
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.5.1 Application Client (AC)
| The following cardinality rules apply for application client:
a) one or more application clients per PIN client.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.5.2 PEMC
| The following cardinality rules apply for PEMC:
a) one or more PEMCs per PIN.
b) Only one PEMC in certain PIN is assigned as primary role and other PEMCs if any are assigned with secondary role.
c) One PEMC can act as PEMC for multiple PINs.
d) One PEMC per UE.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.5.3 PEGC
| The following cardinality rules apply for PEGC:
a) one or more PEGCs per PIN.
a) For a certain PINE in PIN, one PEGC acts as default PEGC and other PEGCs act as backup.
c) One PEGC can act as PEGC for multiple PINs.
d) One PEGC per UE.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.5.4 PIN server
| The following cardinality rules apply for PIN server:
a) one PIN server per PIN.
b) Multiple PINs per PIN server.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 6.5.5 PIN client
| The following cardinality rules apply for PIN client:
a) one or more PIN clients per PIN.
b) one PIN client per PIN element.
c) one PIN client per UE.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 7 Identities and commonly used values
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 7.1 General
| The following clauses list identities and commonly used values that are used in this technical specification.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 7.2 Identities
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 7.2.1 General
| The following clauses specify a collection of identities that are associated with entities defined and being used in this specification.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 7.2.2 PIN ID
| The PIN ID is a unique value in PLMN that identifies the PIN.
The PIN ID consists of two parts as follow:
- A string assigned by the PIN server which is unique for each PIN; and
- An identifier of PIN server (i.e. PIN server ID or domain name).
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 7.2.3 PIN server ID
| The PIN server ID is a globally unique value that identifies the PIN server.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 7.2.4 PIN client ID
| The PIN client ID is a globally unique value that identifies the PIN client.
The PIN client ID is used for general identities for PINE, PEMC and PEGC.
For PEMC and PEGC, the PIN client ID may also be PEMC ID and PEGC ID.
For the PINE, the PIN client ID may also be PINE ID.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 7.2.5 Application Client ID (ACID)
| The ACID identifies the client side of a particular application, for e.g. SA6Video viewer, SA6MsgClient etc. For example, all SA6MsgClient clients will share the same ACID.
In case that the UE is running mobile OS, the ACID is a pair of OSId and OSAppId.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 7.2.6 UE ID
| The UE ID uniquely identifies a particular UE within a PLMN domain. Following identities are examples that can be used:
a) GPSI, as defined in 3GPP TS 23.501 [4].
NOTE: To protect privacy of the user, MSISDN can be used as GPSI only after obtaining user's consent.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 7.2.7 UE Location
| The UE location identifies where the UE is connected to the network or the position of the UE. It provides consistent definition of the UE's location across the UE and network entities. Following values are examples of UE locations that can be used:
a) Cell Identity, Tracking Area Identity, GPS Coordinates, Geographic... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8 Procedures and information flows
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.1 General
| The PINE communicates with the PEMC via direct way (i.e., via WiFi, BlueTooth), or indirect way relayed by a PEGC. PINE determines to use direct way or indirect way based on the capabilites of access types supported by the PINE, PEMC and PEGC.
The Application layer must be able to influence the RAT selection for estab... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.2 Common Information Elements
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.2.1 General
| This clause provides descriptions for Information Elements which are commonly used in several procedures.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.2.2 PIN Profile
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.2.2.0 PIN Profile in a PIN
| PIN profile information include static and semi-static data and default configuration that are needed for configuration of Personal IoT Networks, such as the PEMC, PEGC and PIN server end point addresses. Information in a PIN profile is infrequently changed.
Dynamic PIN profile information includes data that are upda... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.2.2.1 PIN Profile in a PIN
| PIN profile includes information about the static data needed for configuration for the Personal IoT networks.
Table 8.2.2.1-1: PIN Profile
Parameter Name
Parameter Description
PIN Server
PEMC
PEGC
PIN ID
The identifier of the PIN
Y
Y
Y
PIN Description
Human-readable description of the PIN, for example, t... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.2.2.2 Dynamic profile information of a PIN
| Dynamic profile information of a PIN contains the PIN dynamic data needed for management of the Personal IoT networks.
Table 8.2.2.2-1 describes the list of parameters that are classified as dynamic profile information and which are maintained at the PIN server, PEMC and PEGC. PIN dynamic profile information maintaine... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.2.2.3 PIN client profile
| Table 8.2.2.3-1 describes the list of information elements that needs to be shared by the PIN element when requesting to join the PIN.
Table 8.2.2.3-1: PIN client profile
Parameter Name
Status
Parameter Description
PIN ID
M
The identifier of the PIN to which the PIN element wants to join
UE identifier
O
PIN ... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.3 PIN server discovery
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.3.1 General
| Some of the PIN management procedures involves the PIN server and hence the PINE requires the PIN server endpoint address before triggering the PIN management procedures, for example, the PIN creation procedure. Also there could be multiple PIN servers deployed within a PLMN and it is important to PIN elements to disco... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.3.2 Procedure
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.3.2.1 Static PIN server discovery
| The aim of PIN server discovery procedure is to receive one or more endpoint information (e.g. URI(s), FQDN(s), IP address(es)) of PIN server. And the PEMC, PEGC, PIN elements are all able to receive the PIN server endpoint information.
The PIN server can be discovered by the following method:
- pre-configured in t... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.3.2.2 Procedures of PIN server discovery via PEGC
| Some of the PIN elements can have the application interaction towards the PEGC, for example, via WiFi or Bluetooth, and in these case the PEGC can provide the PIN server end point information to PIN elements.
For some of the PEGC, it has the open access capability to accept the application layer connection from the PI... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.3.3 Information flows
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.3.3.1 General
| The following information flows are specified for PIN creation:
- PIN server discovery request and response;
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.3.3.2 PIN server discovery request
| Table 8.3.3.2-1 describes information elements in the PIN server discovery request from the PINE to the PEGC/PEMC.
Table 8.3.3.2-1: PIN server discovery request
Information element
Status
Description
UE Identifier
M
The identifier of the hosting UE (i.e. GPSI or identity token) or PINE.
MAC address
O
MAC add... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.3.3.3 PIN server discovery response
| Table 8.3.3.3-1 describes information elements in the PIN server discovery response from the PEGC/PEMC to the PINE.
Table 8.3.3.3-1: PIN server discovery response
Information element
Status
Description
Successful response
O
(see NOTE)
Indicates that the PIN server discovery request was successful.
> PIN serve... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.4 Registration
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.4.1 General
| The PINE (including PEMC and PEGC) should have a registration procedure in PIN server, before consuming the certain PIN service.
The registration procedure includes the direct registration and indirect registration.
- Direct registration:
- For the PEMC, the PEMC sends PINE Registration Request (MAC address, ven... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.4.2 Registration Procedure
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.4.2.1 General
| The PINE may register to the PIN server via either the PEMC or the PEGC depends on the communication range, supported RATs.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.4.2.2 Procedure
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.4.2.2.1 PINE registration directly to PIN server
| Figure 8.4.2.2.1-1 illustrates PIN registration procedure based on request/response model.
Pre-conditions:
1. The PINE has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server;
2. The UE Identifier is available;
3. The PINE has been authorized to communicate with the PIN ... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.4.2.2.2 PINE registration indirectly to PIN server
| The following procedure defines the PEMC can substitute the PINE/PEGC to register into PIN server.
Pre-conditions:
1. The PEMC has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server;
2. The UE Identifier or PIN client Identifier is available;
3. The PEMC has been autho... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.4.2.2.3 PINE registration via PEGC before join
| The PINE registration towards the PIN server via the PEGC based on request/response model is depicted in figure 8.4.2.2.3-1.
Pre-conditions:
1. The PINE has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server;
2. The PINE already establishes the connection with PEGC;
... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.4.2.2.4 PINE registration during the PIN join via the PEGC
| Pre-conditions:
1. The PINE has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server;
2. The PINE already establishes the connection with PEGC;
3. The PINE may get the PIN information from the PEMC, PEGC via PIN announcement after connecting to PEMC or PEGC.
Figure 8.4.2.... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.4.2.2.5 PINE de-registration directly to PIN server
| Figure 8.4.2.2.5-1 illustrates PIN de-registration procedure based on request/response model.
Pre-conditions:
1. The PINE has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server and is already registered with the PIN server;
2. The UE Identifier is available;
3. The PINE... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.4.2.2.6 PINE de-registration indirectly to PIN server
| Figure 8.4.2.2.6-1 illustrates PINE De-registration request to PIN Server indirectly via PEMC based on request/response model.
Pre-conditions:
1. The PEMC has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server;
2. The UE Identifier or PIN client Identifier is available;
... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.4.2.2.7 PINE update registration to PIN server
| Figure 8.4.2.2.7-1 illustrates PIN update registration procedure based on request/response model.
Pre-conditions:
1. The PINE has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server and is already registered with the PIN server;
2. The UE Identifier is available;
3. The ... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.4.2.3 Information flow/elements
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.4.2.3.1 General
| The following information flows are specified for PIN registration:
- PINE Registration request and response;
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.4.2.3.2 PINE Registration request
| Table 8.4.2.3.2-1 describes information elements in the PINE Registration request from the PINE (including PEMC, PEGC, PINEs) to the PIN server.
Table 8.4.2.3.2-1: PINE Registration request (PINE/PEGC to PIN server, or PEMC represents PINE/PEGC to PIN server)
Information element
Status
Description
UE Identifier
... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.4.2.3.3 PINE Registration response
| Table 8.4.2.3.3-1 describes information elements in the PINE Registration response from the PIN server to the PINE (including PEMC, PEGC, PINEs).
Table 8.4.2.3.3-1: PINE Registration response
Information element
Status
Description
Successful response
O
(see NOTE)
Indicates that the PINE Registration request wa... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.4.2.3.4 PINE de-registration request
| Table 8.4.2.3.4-1 describes information elements in the PINE de-registration request from the PINE (including PEMC, PEGC, PINEs) to the PIN server.
Table 8.4.2.3.4-1: PINE de-registration request
Information element
Status
Description
UE Identifier
M
The identifier of the hosting UE (i.e. GPSI or identity token... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.4.2.3.5 PINE de-registration response
| Table 8.4.2.3.5-1 describes information elements in the PINE de-registration response from the PIN server to the PINE (including PEMC, PEGC, PINEs).
Table 8.4.2.3.5-1: PINE de-registration response
Information element
Status
Description
De-registration status
M
Indicates whether the PINE de-registration request ... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.4.2.3.6 PINE update registration request
| Table 8.4.2.3.6-1 describes information elements in the PINE update registration request from the PINE (including PEMC, PEGC, PINEs) to the PIN server.
Table 8.4.2.3.6-1: PINE update registration request
Information element
Status
Description
UE Identifier
M
The identifier of the hosting UE (i.e. GPSI or identi... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.4.2.3.7 PINE update registration response
| Table 8.4.2.3.7-1 describes information elements in the PINE de-registration response from the PIN server to the PINE (including PEMC, PEGC, PINEs).
Table 8.4.2.3.7-1: PINE update registration response
Information element
Status
Description
Update registration status
M
Indicates whether the PINE update registrat... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5 PIN Management
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.1 General
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.2 PIN Create
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.2.1 General
| After the UE or PINE acquires the role of PEMC and receives the address of PIN server, the UE or PINE can trigger a creation of PIN towards PIN server.
Below are the possible scenarios when the PEMC request for the creation of PIN:
- No PIN elements or PEGC have established connection with PEMC;
- One or more PIN... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.2.2 Procedure
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.2.2.1 PIN creation procedure
| Figure 8.5.2.2.1-1 illustrates PIN creation procedure based on request/response model.
Pre-conditions:
1. The UE or PINE has been pre-configured or has discovered the address (e.g. IP address, FQDN, URI) of the PIN server;
2. The UE Identifier or PIN client Identifier is available;
3. The UE or PINE has already bee... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.2.3 Information flows
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.2.3.1 General
| The following information flows are specified for PIN creation:
- PIN creation request and response;
- PIN creation notification request and response;
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.2.3.2 PIN creation request
| Table 8.5.2.3.2-1 describes information elements in the PIN creation request from the PINE/PEGC to the PIN server.
Table 8.5.2.3.2-1: PIN creation request
Information element
Status
Description
UE Identifier
M
The identifier of the hosting UE (i.e. GPSI or identity token) or the PIN client ID of PEMC
Security ... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.2.3.3 PIN creation response
| Table 8.5.2.3.3-1 describes information elements in the PIN creation response from the PIN server to the PEMC.
Table 8.5.2.3.3-1: PIN creation response
Information element
Status
Description
Successful response
O
Indicates that the PIN creation request was successful.
> PIN ID
M
Identifier of the newly creat... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.5.2.3.4 PIN creation notification request
| Table 8.5.2.3.4-1 describes information elements in the PIN creation notification request from the PEMC to the PEGC and PIN elements.
Table 8.5.2.3.4-1: PIN creation notification request
Information element
Status
Description
PIN ID
M
Identifier of the newly created PIN.
Indication
M
Indicates whether the PI... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.