hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.3.2.2 Target resolution
| Upon receiving the MSGin5G message request to deliver the message to the recipient (which could be any of the MSGin5G UE, Legacy 3GPP UE, Non-3GPP UE or Application Server), the MSGin5G Server checks the recipient's registration status (created at the time of each MSGin5G UE/Application Server registration to MSGin5G S... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.3.3 MSGin5G Client
| 5.3.3.1 General functionalities of MSGin5G Client
An MSGin5G Client provides client-side functionality for UE Application Clients with the sending and receiving of messages via the MSGin5G Service to/from Application Servers and/or other MSGin5G Service endpoints; i.e. UEs.
Functionalities of MSGin5G Client includin... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.3.3.2 MSGin5G Gateway Client
| An MSGin5G Gateway Client is an MSGin5G Client which supports MSGin5G Gateway service functionality in addition to the MSGin5G Client functionalities specified in clause 5.3.3.1. It enables constrained devices to obtain services from the MSGin5G Server when communications via ProSe UE-to-Network Relay are not or cannot... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.3.4 Message Gateway
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.3.4.1 General Description of Message Gateway
| A Message Gateway in the MSGin5G application architecture provides functionality to deliver MSGin5G messages to Non-MSGin5G UEs.
NOTE 1: It is an implementation option to deliver broadcast messages to Legacy 3GPP UEs and MSGin5G UEs (see Figure 5.2-1).
A Message Gateway performs the role of interconnecting two diffe... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.3.4.2 Legacy 3GPP Message Gateway
| The Legacy 3GPP Message Gateway is used to deliver MSGin5G message to Legacy 3GPP UEs, using their 3GPP supported message delivery mechanisms.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.3.4.3 Non-3GPP Message Gateway
| The Non-3GPP Message Gateway is used to deliver MSGin5G message to Non-MSGin5G UEs, using their (non-3GPP) supported message delivery mechanisms.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.3.4.4 Broadcast Message Gateway
| The Broadcast Message Gateway is used to deliver MSGin5G message to MSGin5G UEs, Legacy 3GPP UEs or Non-MSGin5G UEs in a Broadcast Area.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.3.5 Application Client
| The Application Client is an entity in the application layer to implement and perform the application service logic for its own service.
The Application Client interacts with MSGin5G Client for on the same or different UE sending and receiving MSGin5G messages. The Application Client provides needed information for th... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.3.6 Application Server
| The Application Server is an entity in the application layer to implement and perform the application service logic.
The Application Server supports sending and receiving messages with MSGin5G Service layer protocols and procedures.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.3.7 Legacy 3GPP Message Client
| The Legacy 3GPP Message Client provides client-side functionality for a Legacy 3GPP messaging service (e.g. SMS, NIDD).
NOTE: The details of the Legacy 3GPP Message Client are out of scope of the present document.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.3.8 Non-3GPP Message Client
| The Non-3GPP Message Client provides client-side functionality for a Non-3GPP messaging service.
NOTE: The details of the Non-3GPP message client are out of scope of the present document.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.3.9 SEAL Client
| The following SEAL Clients for MSGin5G Service are supported:
- Group management client as specified in 3GPP TS 23.434 [5];
- Configuration management client as specified in 3GPP TS 23.434 [5].
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.3.10 SEAL server
| The following SEAL servers for MSGin5G Service are supported:
- Group management server as specified in 3GPP TS 23.434 [5];
- Configuration management server as specified in 3GPP TS 23.434 [5].
NOTE: Usage of other SEAL services (e.g. location) from 3GPP TS 23.434 [5] for MSGin5G Service is not in scope of the prese... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.4 Reference Points
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.4.1 General
| The reference points of the service architecture for the MSGin5G Service are described in this clause.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.4.2 MSGin5G-1
| The interactions related to enabling MSGin5G message exchange between an MSGin5G Client and an MSGin5G Server are supported by the MSGin5G-1 reference point. This reference point supports:
- Registration of an MSGin5G Client to an MSGin5G Server when not using IMS based solution; and
- The exchange of MSGin5G message... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.4.3 MSGin5G-2
| The interactions related to enabling MSGin5G message exchange between an MSGin5G Server and the Legacy 3GPP Message Gateway are supported by the MSGin5G-2 reference point. This reference point supports:
- The exchange of MSGin5G messages between MSGin5G Server and the Legacy 3GPP Message Gateway; and
- Perform regist... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.4.4 MSGin5G-3
| The interactions related to enabling MSGin5G message exchange between an Application Server and an MSGin5G Server are supported by the MSGin5G-3 reference point. This reference point supports:
- Access to MSGin5G Server and APIs to enable sending and receiving of MSGin5G messages; and
- Adherence to CAPIF as specifie... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.4.5 MSGin5G-4
| The interactions related to enabling MSGin5G message exchange between a Non-3GPP Message Gateway and an MSGin5G Server are supported by the MSGin5G-4 reference point. This reference point supports:
- The exchange of MSGin5G messages between MSGin5G Server and the Non-3GPP Message Gateway; and
- Perform registration/d... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.4.6 MSGin5G-5
| The interactions related to enabling MSGin5G message related information exchange between an Application Client and an MSGin5G Client are supported by the MSGin5G-5 reference point. The Application Client can reside on the same UE with the MSGin5G Client or reside on a different UE. This reference point supports:
- Pr... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.4.7 MSGin5G-6
| The MSGin5G Client of MSGin5G UE-2 communicates with MSGin5G Gateway service functionality residing on an MSGin5G Gateway UE over MSGin5G-6 reference point. The interface is based on Unicast mode 5G ProSe Direct Communication specified in 3GPP TS 23.304 [18].
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.4.8 SEAL-C
| The following SEAL-C reference points for MSGin5G Service are supported:
- GM-C reference point for group management as specified in 3GPP TS 23.434 [5];
- CM-C reference point for configuration management as specified in 3GPP TS 23.434 [5].
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.4.9 SEAL-S
| The following SEAL-S reference points for MSGin5G Service are supported:
- GM-S reference point for group management as specified in 3GPP TS 23.434 [5];
- CM-S reference point for configuration management as specified in 3GPP TS 23.434 [5].
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.4.10 SEAL-UU
| The following SEAL-UU reference points for MSGin5G Service are supported:
- GM-UU reference point for group management as specified in 3GPP TS 23.434 [5];
- CM-UU reference point for configuration management as specified in 3GPP TS 23.434 [5].
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.4.11 MSGin5G-7
| The MSGin5G-7 reference point is used by the MSGin5G Server to communicate with the Broadcast Message Gateway to deliver Broadcast messages.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.4.12 MSGin5G-8
| The MSGin5G-8 reference point is used by the MSGin5G Server to communicate with another MSGin5G Server to deliver messages to the MSGin5G Service endpoint which is served by the other MSGin5G Server, and for message exchange related to Messaging Topic (un)subscriptions.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.5 Capability exposure for enabling MSGin5G Service
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.5.1 MSGin5G application enabler layer adaptation to CAPIF
| The MSGin5G Server and Application Server may support CAPIF. When CAPIF is supported:
- The MSGin5G Server shall support the CAPIF API provider domain functions (i.e. CAPIF-2/2e, CAPIF-3/3e, CAPIF-4/4e and CAPIF-5/5e as specified in 3GPP TS 23.222 [6]) as shown in Figure 5.5.1-1;
- The Application Server shall act as... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.6 Service based interface representation for MSGin5G Service
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.6.1 General
| The Service based architecture for MSGin5G Service is represented using functional entities and reference points between the functional entities as specified in clause 5.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.6.2 Service based architecture
| Figure 5.6.2-1 is the Service based Architecture for MSGin5G Service.
Figure 5.6.2-1: Service based MSGin5G Architecture
NOTE: The AS, BMG, L3G and N3G in this Service based MSGin5G Architecture are in the same trust domain.
The M5S function is a service based function exhibited by MSGin5G Server.
The M5C functio... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 5.6.3 Service based interfaces
| Table 5.6.3-1 specifies the service based interfaces supported by MSGin5G Service.
Table 5.6.3-1: Service based interfaces supported by MSGin5G Service
Service based interface
Application function entity
Mapping server entity
APIs offered
Mm5s
MSGin5G Server function
MSGin5G Server
Specified in 9.1
Ml3g
Lega... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 6 Identities
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 6.1 Identities for MSGin5G Service endpoints
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 6.1.1 General
| MSGin5G Service endpoints shall be identified by unique identifiers within the MSGin5G Service domain. For each MSGin5G Service endpoint the identifier shall be a unique URI that can be used to identify the MSGin5G Service endpoint's home service domain.
The following clauses describe different types of MSGin5G Servic... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 6.1.2 UE Service Identity (UE Service ID)
| UE Service ID is the identifier of a UE (i.e. MSGin5G UE, Legacy 3GPP UE or Non-3GPP UE).
For an MSGin5G UE, the assigned UE Service ID is used by the MSGin5G Client to register with the MSGin5G Server and to send and receive MSGin5G messages. It is used by the MSGin5G Server to authenticate and authorize the associat... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 6.1.3 Application Server Service Identity (AS Service ID)
| AS Service ID is the identifier of an Application Server. It is used to perform mutual authentication with the MSGin5G Server for establishing a secured service connection, and it is used to send/receive message API request/response to/from other MSGin5G Service endpoints via MSGin5G Server.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 6.1.4 Message Gateway Service Identity (MGW Service ID)
| MGW Service ID is the identifier of Message Gateway. It is used to perform mutual authentication with the MSGin5G Server for establishing a secured service connection.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 6.2 MSGin5G Group Service Identity (Group Service ID)
| The Group Service ID is a unique identifier within the MSGin5G Service that represents a pre-defined MSGin5G Group. A pre-defined MSGin5G Group is established before the MSGin5G Group messages are sent to it, and is assigned a unique and permanent Group Service ID when it is established. This Group Service ID shall be ... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 6.3 Broadcast Area Service Identity (Broadcast Area ID)
| The Broadcast Area ID is the identity of the Service Area where the broadcast message is delivered.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 6.4 MSGin5G UE Identity (MSGin5G UE ID)
| The MSGin5G UE ID is a unique identifier that represents the MSGin5G UE (i.e. the device identifier of the MSGin5G UE). The MSGin5G UE ID may be pre-configured to the MSGin5G UE by its vendor.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 6.5 Non-MSGin5G UE identity (Non-MSGin5G UE ID)
| The Non-MSGin5G UE ID is a unique identifier that represents the Non-MSGin5G UE. A Non-MSGin5G UE ID is associated with a specific Non-MSGin5G UE. It is used by the Message Gateway in the MSGin5G Service to record the Non-MSGin5G UE. It is also used by the Message Gateway as a part of VAL UE ID when the Message Gateway... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 6.6 Application Identity (Application ID)
| Application ID is an identifier that represents the application for which the payload of message is intended. The content of Application ID is outside the scope of this document.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 6.7 MSGin5G Server address
| MSGin5G Server address is the identifier of an MSGin5G Server within an MSGin5G service provider's domain. The MSGin5G Service endpoints in this MSGin5G service provider's domain can contact an MSGin5G Server by using the MSGin5G Server address of this MSGin5G Server.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 7 Generic description of the MSGin5G Service (informative)
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 7.1 General
| Massive Internet of Things (MIoT) is one of key market segments of 5G. The typical IoT device communication is sending and receiving small data which can be delivered just in a message. The MSGin5G Service is designed and optimized for massive IoT device communication including thing-to-thing communication and person-t... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 7.2 Service flow
| Before a UE or an Application Server can use the MSGin5G Service it needs to register with the MSGin5G Server.
A UE registers with its identity, its security credentials, the capabilities that it supports, and its availability. The MSGin5G Server will use the availability registration and de-registration to determine ... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 7.3 Message delivery flow at MSGin5G Server
| Figure 7.3-1 shows the flow for message delivery by the MSGin5G Server.
Figure 7.3-1: The message delivery flow at the MSGin5G Server
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8 Procedures and information flows
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.1 Configuration
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.1.1 General
| The configuration procedure is used to get the MSGin5G Service configuration information (e.g. UE Service ID). The configuration procedure is used by the MSGin5G UE or used by Message Gateway on behalf of the Non-MSGin5G UE. The MSGin5G Service configuration information is used in the future messaging communication.
T... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.1.2 MSGin5G UE Configuration
| In the MSGin5G UE configuration procedure, the MSGin5G UE acts as Configuration management client specified in 3GPP TS 23.434 [5].
The following steps of configuration management service apply for the MSGin5G UE:
- Send the Get VAL UE configuration request specified in clause 11.3.2.1 of 3GPP TS 23.434 [5];
- Receiv... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.1.3 Message Gateway Configuration for support of Non-MSGin5G UE
| The Message Gateway performs the configuration procedure on behalf of the Non-MSGin5G UE to get the MSGin5G Service configuration information (e.g. UE Service ID).
NOTE 1: As an alternative to the configuration procedure all the necessary service information (including the UE Service ID) of a Non-MSGin5G UE can be pre... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.1.4 MSGin5G UE bulk configuration over MSGin5G-6 reference point
| When more than one MSGin5G UEs, which are constrained devices, which support an MSGin5G Client, get the MSGin5G Service configuration information via the MSGin5G Gateway UE, the MSGin5G Gateway UE may decide to use bulk configuration procedure specified in this clause based on service policy.
Pre-conditions:
1. The ... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.2 Registration
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.2.0 General
| Before a UE or an Application Server can use the MSGin5G Service it needs to register with the MSGin5G Server.
The procedures of MSGin5G UE registration/de-registration are specified in clause 8.2.1 and clause 8.8.2. The procedures also apply when the MSGin5G UE uses MSGin5G services by using another UE as relay.
Th... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.2.1 MSGin5G UE Registration
| The signalling flow for MSGin5G UE registration is illustrated in figure 8.2.1-1. The procedure assumes that the MSGin5G UE is responsible for initiating registration to the MSGin5G Server in order to establish association with the MSGin5G Server to receive MSGin5G Services.
Pre-conditions:
1. The MSGin5G UE has conn... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.2.2 MSGin5G UE De-Registration
| By de-registering, the MSGin5G UE informs the MSGin5G Server that it wishes to terminate its association with the MSGin5G Server.
NOTE 1: De-registration implies that Client Triggering Information and the Client Communication Availability Information are no longer valid.
The procedure assumes that the MSGin5G UE is ... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.2.3 Non-MSGin5G UE Registration
| Non-MSGin5G UEs (i.e., Legacy 3GPP UEs or Non-3GPP UEs) are connected to the MSGin5G Server through a Message Gateway. The Message Gateway performs registration with the MSGin5G Server on behalf of the Non MSGin5G UEs, based on pre-provisioned information when it receives a registration request from the Non MSGin5G UE,... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.2.4 Non-MSGin5G UE De-registration
| The Message Gateway performs de-registration with the MSGin5G Server on behalf of the Non-MSGin5G UEs, in order to terminate services from the MSGin5G Server.
NOTE: After the procedure is completed, the Message Gateway may communicate the result to the requesting Non-MSGin5G UE and the procedure is out of scope of th... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.2.5 Application Server Registration
| The signalling flow for Application Server registration is illustrated in figure 8.2.5-1. Application Server may use the procedure in this clause to do registration.
NOTE 1: If the Application Server does not use the Registration procedure, applicable Information Elements as listed in Table 9.1.2.3-1 need to be confi... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.2.6 Application Server De-registration
| By de-registering, the Application Server informs the MSGin5G Server that it wishes to terminate its association with the MSGin5G Server.
The procedure assumes that the Application Server is responsible for triggering the de-registration from the MSGin5G Server. The signalling flow for Application Server de-registrati... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.2.7 MSGin5G UE bulk registration over MSGin5G-6 reference point
| When MSGin5G UE-1 and UE-2, which support an MSGin5G Client, perform registration via MSGin5G Gateway UE to contact the MSGin5G Server, the MSGin5G Gateway service functionality in the MSGin5G Gateway UE may decide to use bulk registration procedure specified in this clause based on the registration request sent from M... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.2.8 Constrained device with MSGin5G Client selecting MSGin5G Gateway UE
| The signalling flow for MSGin5G Client-2 in the MSGin5G UE-2 (which is a constrained device) to request other MSGin5G UEs supporting MSGin5G Gateway service functionality to provide their configuration is illustrated in figure 8.2.8-1.
Pre-conditions:
1) MSGin5G UE-2 is not able to communicate with MSGin5G Server di... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.2.9 Non-MSGin5G UE bulk registration
| Non-MSGin5G UEs (i.e., Legacy 3GPP UEs or Non-3GPP UEs) are connected to the MSGin5G Server through a Message Gateway. The Message Gateway may decide to use bulk registration procedure specified in this clause based on service policy. The procedure for Non-MSGin5G UE bulk registration is illustrated in figure 8.2.9-1.
... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.2.10 Non-MSGin5G UE bulk de-registration
| The procedure assumes that the Message Gateway is responsible for initiating the bulk de-registration from the MSGin5G Server on behalf of the Non-MSGin5G UEs. The signalling flow for Non-MSGin5G UE bulk de-registration is illustrated in figure 8.2.10-1.
Pre-conditions:
1. The Message Gateway successfully performed r... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.2.11 MSGin5G UE bulk de-registration over MSGin5G-6 reference point
| The MSGin5G Gateway UE may decide to use bulk de-registration procedure specified in this clause based on the de-registration request sent from MSGin5G Clients in MSGin5G UEs or, if allowed by service policy. The procedure for MSGin5G UE bulk de-registration is illustrated in figure 8.2.11-1.
Pre-conditions:
1. The M... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.3 Message delivery procedures
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.3.1 General
| All MSGin5G message traffic is routed via the MSGin5G Server. The present clause specifies the MSGin5G message origination procedure when a MSGin5G service endpoint (i.e. MSGin5G UE, AS or Message Gateway) sending a message to its recipient(s) and the MSGin5G message termination procedure when a MSGin5G Server delivers... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.3.2 MSGin5G messages origination procedure
| Figure 8.3.2-1 shows the procedure for an MSGin5G UE that initiates an MSGin5G message request.
Figure 8.3.2-1: New MSGin5G message request from UE
Figure 8.3.2-2 shows the procedure for an Application Server that initiates an API request specified in clause 9.1.1.1 for sending an MSGin5G message to UE.
Figure... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.3.3 MSGin5G messages termination procedure
| Figure 8.3.3-1 shows the procedure for the MSGin5G Server that delivers an MSGin5G message.
Figure 8.3.3-1: MSGin5G message towards UE
Figure 8.3.3-2 shows the same procedure (step 1 only), however for the MSGin5G Server that delivers the message to an Application Server by application request.
Figure 8.3.3-2:... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.3.4 MSGin5G message delivery status report into the MSGin5G Server
| Figure 8.3.4-1 shows the procedure for an MSGin5G UE that initiates an MSGin5G message delivery status report.
Figure 8.3.4-1: Message delivery status report from MSGin5G UE
Figure 8.3.4-2 shows the procedure for an Application Server that initiates an API request for MSGin5G message delivery status report specif... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.3.5 MSGin5G message delivery status report from the MSGin5G Server
| Figure 8.3.5-1 shows the procedure for the MSGin5G Server that forwards an MSGin5G message delivery status report to an MSGin5G UE.
Figure 8.3.5-1: Message delivery status report towards an MSGin5G UE
Figure 8.3.5-2 shows the procedure for the MSGin5G Server that forwards an MSGin5G message delivery status repo... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.3.6 MSGin5G Store and Forward
| Figure 8.3.6-1 shows the procedure for providing store and forward services for MSGin5G message requests.
This procedure applies when an MSGin5G message is received at the MSGin5G Server for delivery and the message cannot be delivered to the recipient UE; otherwise, the procedure detailed in clause 8.3.2 applies.
P... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.3.6.1 Procedure for MSGin5G Client to update the stored message
| Figure 8.3.6.1-1 shows the procedure for MSGin5G Client to update the stored message. This procedure enables user to update store and forward parameters of the stored message or discard to stored message. It is up to the end user or application client to decide if update the stored message is required or not.
Pre-cond... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.3.7 MSGin5G deferred message
| This procedure applies when an MSGin5G message is received at the MSGin5G Server for delivery and the message cannot be delivered to the recipient since the recipient UE is unavailable (disconnected or power off), i.e. not registered; otherwise, the procedure detailed in clause 8.3.2 applies.
This procedure applies t... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.4 Message Aggregation
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.4.1 General
| Based on maximum segment size allowed to transmit over available transport, the MSGin5G Service can optimize communications by aggregating one or more messages towards the same target. The target may be an UE, an Application Server, a Broadcast Area, an MSGin5G Group or a Messaging Topic.
The following pre-conditions ... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.4.2 Message Aggregation at MSGin5G Client
| Figure 8.4.2-1 shows the procedure for an MSGin5G Client aggregating a set of Point-to-Point messages each carrying small amounts of data. All of the Point-to-Point messages to be aggregated are targeted to the same UE.
NOTE 1: Aggregation of multiple messages can also be done with the Application Client; in this case... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 4a The MSGin5G Server performs the necessary message exchanging procedure with the Application Server as per clause 8.7.4.2.
| 5. The MSGin5G Server sends the Aggregated message response to the MSGin5G Client 1 in the cases listed below. The information elements defined in Table 8.4.2-3 shall be included in the response.:
a) MSGin5G Client 1 is not authorized to send Aggregated message request; or
b) the Aggregated message request is not va... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.4.3 Message aggregation at MSGin5G Server
| Figure 8.4.3-1 shows the procedure for the MSGin5G Server aggregating a set of Application-to-Point messages targeted to the same recipient UE, set of group messages for the same MSGin5G group, or a set of messages delivered based on Messaging Topic for the same Messaging Topic, or a set of messages broadcasted to the ... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.5 MSGin5G Message Segmentation and Reassembly
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.5.1 General
| This clause introduces MSGin5G message segmentation and reassembly functionality to the MSGin5G Service.
Segmentation and reassembly operations are performed by the MSGin5G Server, or by the MSGin5G Client, or by the Message Gateway, depending on the communication models. For Application-to-Point use case, the MSGin5G... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.5.2 Application-to-Point Segmentation and Reassembly
| Figure 8.5.2-1 shows the MSGin5G message segmentation and reassembly procedure for Application-to-Point MSGin5G message use cases (e.g. AOMT).
NOTE 1: Segmentation can also be done by the Application Server, in this case the Application Server will create a segmented message and send it as a regular MSGin5G message. ... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.5.3 Point-to-Application Message Segmentation and Reassembly
| Figure 8.5.3-1 shows the MSGin5G message segmentation and reassembly procedure for Point-to-Application MSGin5G message use cases (e.g. MOAT).
Pre-conditions:
1. A UE hosts an MSGin5G Client and an Application Client.
2. The MSGin5G Client registered with the MSGin5G Server.
3. An Application Client on the UE needs... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.5.4 Point-to-Point Message Segmentation and Reassembly
| Figure 8.5.4-1 shows the MSGin5G message segmentation and reassembly procedure for Point-to-Point MSGin5G message use cases (e.g. MOMT).
If the recipient UE is a non-MSGin5G UE, the reassembly is performed by the Message Gateway.
This procedure assumes that a UE is only aware of the maximum payload size of the deliv... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.5.5 Group Message Segmentation and Reassembly
| A Group Message is sent from the MSGin5G Server to a group of recipient UEs. The MSGin5G Server sends the message to each individual recipient taking into account the Supported MSGin5G segment size of each recipient and segments the message as described in clause 8.5.4.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.5.6 MSGin5G Message Segment Recovery
| Figure 8.5.6-1 illustrates an MSGin5G message segmentation recovery procedure. The procedure is applicable to Application-to-Point messages, Point-to-Application messages, Point-to-Point message and Group messages.
Pre-conditions:
1. The Message sender has delivered segmented messages to Message receiver.
Figure... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.6 MSGin5G messaging procedure on Message Gateway
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.6.1 General MSGin5G messaging procedure on Message Gateway
| Figure 8.6.1-1 shows the MSGin5G message delivery procedure on Message Gateway for Non-MSGin5G UEs.
Figure 8.6.1-1: MSGin5G messaging procedure on Message Gateway.
1. The MSGin5G Server forwards the MSGin5G message request to recipient Non-MSGin5G UE based on the UE Service ID or to the Broadcast Message Gateway ba... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.6.2 Non-MSGin5G UE receives message from group
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.6.2.1 Legacy 3GPP UE receives message from group
| Figure 8.6.2.1-1 shows the procedure for Legacy 3GPP UE to receive message from group.
Pre-conditions:
1. The MSGin5G Server has received the Group message to be sent to a target Legacy 3GPP UE.
Figure 8.6.2.1-1: Legacy 3GPP UE receives a message from a group
1. The MSGin5G Server sends the MSGin5G message reque... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.6.2.2 Non-3GPP message client receives message from group
| Figure 8.6.2.2-1 shows the procedure for Non-3GPP message client to receive message from group.
Pre-conditions:
1. The MSGin5G Server has received the Group message to be sent to target Non-3GPP UE.
Figure 8.6.2.2-1: Non-3GPP message client receives a message from a group
1. The MSGin5G Server sends the MSGin5G... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.7 E2E Message delivery procedures
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.7.1 Point-to-Point Message delivery procedures
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.7.1.1 From MSGin5G UE to MSGin5G UE
| Figure 8.7.1.1-1 shows the message delivery procedure from MSGin5G UE 1 to MSGin5G UE 2.
Pre-condition:
1. Both MSGin5G Client 1 in MSGin5G UE 1 and MSGin5G Client 2 in MSGin5G UE 2 have registered with the MSGin5G Server.
Figure 8.7.1.1-1 Message delivery between MSGin5G UEs
1. The MSGin5G Client 1 sends an MS... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.7.1.2 From MSGin5G UE to Legacy 3GPP UE
| Figure 8.7.1.2-1 shows the message delivery procedure from MSGin5G UE to Legacy 3GPP UE.
Pre-conditions:
1. MSGin5G Client in MSGin5G UE has registered with the MSGin5G Server and the Message Gateway has registered with the MSGin5G Server on behalf of the Legacy 3GPP UE.
2. Legacy 3GPP Message Gateway is aware of th... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.7.1.3 From MSGin5G UE to Non-3GPP UE
| Figure 8.7.1.3-1 shows the message delivery procedure from MSGin5G UE to Non-3GPP UE.
Pre-conditions:
1. MSGin5G Client in MSGin5G UE has registered with the MSGin5G Server and the Non-3GPP Message Gateway has registered with the MSGin5G Server on behalf of the Non-3GPP UE.
2. Non-3GPP Message Gateway is aware of th... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.7.1.4 From Legacy 3GPP UE to MSGin5G UE
| This procedure is used for message reply from Legacy 3GPP UE (e.g. SMS UE) to MSGin5G UE.
Figure 8.7.1.4-1 shows the response message delivery procedure from Legacy 3GPP UE (e.g. SMS UE) to MSGin5G UE.
Pre-conditions:
1. MSGin5G Client in MSGin5G UE has registered with the MSGin5G Server and the Legacy 3GPP Message ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.