hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.7.1.5 From Non-3GPP UE to MSGin5G UE
| This procedure is used for message reply from Non-3GPP UE to MSGin5G UE.
Figure 8.7.1.5-1 shows the message delivery procedure from Non-3GPP UE to MSGin5G 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... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.7.2 Application-to-Point Message delivery procedures
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.7.2.1 From Application Server to MSGin5G UE
| Figure 8.7.2.1-1 shows the message delivery procedure from Application Server to MSGin5G UE.
Pre-conditions:
1. The MSGin5G Client is registered with the MSGin5G Server.
2. The Application Server has established secured communication with the MSGin5G Server.
Figure 8.7.2.1-1: Message delivery from Application ... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.7.2.2 From Application Server to Legacy 3GPP UE
| Figure 8.7.2.2-1 shows the message delivery procedure from Application Server to Legacy 3GPP UE.
Pre-conditions:
1. The Application Server has established secured communication with the MSGin5G Server.
2. The Legacy 3GPP Message Gateway has registered with the MSGin5G Server on behalf of the client in the Legacy 3GP... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.7.2.3 From Application Server to Non-3GPP UE
| Figure 8.7.2.3-1 shows the message delivery procedure from Application Server to Non-3GPP UE.
Pre-conditions:
1. The Application Server has established a secured communication with the MSGin5G Server.
2. The Non-3GPP Message Gateway has registered with the MSGin5G Server on behalf of the message client in the Non-3G... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.7.3 Point-to-Application Message delivery procedures
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.7.3.1 From MSGin5G UE to Application Server
| Figure 8.7.3.1-1 shows the message delivery procedure from MSGin5G UE to Application Server.
Pre-conditions:
1. The Application Server and MSGin5G Client in MSGin5G UE have registered with the MSGin5G Server.
Figure 8.7.3.1-1: Message delivery from MSGin5G UE to Application Server
1. The MSGin5G Client sends an... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.7.3.2 From Legacy 3GPP UE to Application Server
| This procedure is used for message reply from Non-3GPP UE to Application Server.
Figure 8.7.3.2-1 shows the message delivery procedure from Legacy 3GPP UE to Application Server.
Pre-conditions:
1. The Application Server has established secured communication with the MSGin5G Server.
2. The Legacy 3GPP Message Gatewa... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 3 The Legacy 3GPP UE received a message from the Application Server.
| 4. The Legacy 3GPP Message Gateway is aware of the Legacy 3GPP Message client on the Legacy 3GPP UE and provides the mapping between its identifiers and UE Service ID.
5. The Legacy 3GPP Message Gateway implementation supports storing a messaging transaction, i.e. mapping the message originating MSGin5G Service ID and... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.7.3.3 From Non-3GPP UE to Application Server
| This procedure is used for message reply from Legacy 3GPP UE to Application Server.
Figure 8.7.3.3-1 shows the message delivery procedure from Non-3GPP UE to Application Server.
Pre-conditions:
1. The Application Server has established secured communication with the MSGin5G Server.
2. The Non-3GPP Message Client in... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.7.4 MSGin5G Group messaging
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.7.4.1 General
| This clause introduces a group messaging procedure for MSGin5G Client and MSGin5G Server to send and receive Group messages after a group is created. In this procedure, the group creation and membership management are handled by group management function specified in 3GPP TS 23.434 [5].
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.7.4.2 Message delivery from UE to group
| Figure 8.7.4.2-1 shows the MSGin5G Group messaging procedure in which MSGin5G Client or Application Server sends a message to a group. One or multiple Controlling AS may be present in this group. The Controlling AS is not considered as a participant of this group.
Pre-conditions:
1. An MSGin5G Group is created by fol... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.7.4.3 Message delivery procedure from Application Server to group
| Figure 8.6.4.3-1 shows the MSGin5G Group messaging procedure in which the Application Server sends a message to a group.
Pre-conditions:
1. An MSGin5G Group is created by following group management SEAL service procedures as specified in 3GPP TS 23.434 [5].
Figure 8.7.4.3-1: Group messaging in MSGin5G Service
1.... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.7.5 Message delivery between different PLMNs
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.7.5.1 General
| MSGin5G messages may be delivered between different PLMNs.
The procedure specified in clause 8.7.5.2 applies to Point-to-Point message, Group message, and may also apply to AS-to-Point message and Point-to-AS message delivery if agreed by the business agreement between the PLMN operators. The procedure specified in cl... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.7.5.2 Inter-PLMN message exchange procedure
| Pre-condition:
1. The Message Sender (e.g. MSGin5G Client 1 in MSGin5G UE 1) is registered to the MSGin5G Server 1 in one PLMN.
2. The Message Receiver (e.g. MSGin5G Client 2 in MSGin5G UE 2) is registered to the MSGin5G Server 2 in another PLMN.
3. MSGin5G Server 1 and MSGin5G Server 2 have established a secured co... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.7.5.3 Inter-PLMN message exchange procedure based on Messaging Topic
| Figure 8.7.5.3-1 shows the inter-PLMN Message delivery based on Messaging Topic when MSGin5G Server 2 forwards the Messaging Topic subscription request from the MSGin5G UE/Application Server served by it to MSGin5G Server 1 as specified in clause 8.8.4.
Pre-condition:
1. The Message Sender (e.g. an MSGin5G UE, a Mess... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 3 The MSGin5G Server 2 delivers the MSGin5G message request to Messager Receiver based on the UE Service ID/AS Service ID in the message as specified in clause 8.3.3.
| 4-6. If the message delivery status report is requested, the Message Receiver sends message delivery status report to Message Sender as per procedure specified in clause 8.3.4 and 8.3.5.
Figure 8.7.5.3-2 shows the inter-PLMN Message delivery to subscribing service endpoints based on Messaging Topic when MSGin5G Serve... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 3a The MSGin5G Server 2 checks the subscription of the Messaging Topic included in the inbound request. The MSGin5G Server 2 delivers the MSGin5G message request to Messager Receiver 1 based on its UE Service ID/AS Service ID as specified in clause 8.8.2.
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 3b The MSGin5G Server 2 also delivers the MSGin5G message request to Messager Receiver 2 which subscribed to this Messaging Topic as specified in clause 8.8.2.
| 4a-6a. If the message delivery status report is requested, the Message Receiver 1 sends message delivery status report to Message Sender as per procedure specified in clause 8.3.4 and 8.3.5.
4b-6b. If the message delivery status report is requested, the Message Receiver 2 sends message delivery status report to Messa... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.7.6 Broadcast message delivery
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.7.6.1 General
| This clause introduces a Broadcast message procedure for an Application Server and an MSGin5G UE to send a Broadcast message. In this procedure, an MSGin5G message is delivered via broadcast to MSGin5G UEs or non-MSGin5G UEs in a Broadcast Area.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.7.6.2 Broadcast message delivery procedure
| Figure 8.7.6.2-1 shows the Broadcast message delivery procedure from Application Server or MSGin5G UE to the UEs in Broadcast Area.
Pre-condition:
1. Application Server or MSGin5G Client in MSGin5G UE has registered with the MSGin5G Server.
Figure 8.7.6.2-1: Message Delivery in Broadcast Area
1. An MSGin5G mess... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.8 Other MSGin5G messaging related procedures
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.8.0 General
| In order to receive the message with a specific Messaging Topic, a UE or an Application Sever subscribes to this Messaging Topic. The procedures of a MSGin5G Server creating a Messaging Topic and a UE or an Application Sever subscribing/unsubscribing one or more Messaging Topic(s) from an MSGin5G Server are specified i... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.8.1 Messaging Topic Subscription
| An MSGin5G Client or an Application Server can subscribe one or more Messaging Topic(s) on the MSGin5G Server. The Messaging Topic IE will be populated by the Application Client or the Application Server and the content of this IE is out of scope.
When an MSGin5G Client or an Application Server is subscribed to a Mes... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.8.2 Message delivery based on Messaging Topic
| If an MSGin5G Client or an Application Server is in the subscribers list of a Messaging Topic, the MSGin5G Server delivers messages that contain this Messaging Topic to it.
Figure 8.8.2-1 shows the Message delivery to a subscribing service endpoint based on Messaging Topic.
Pre-conditions:
1. The MSGin5G Client or ... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.8.3 Messaging Topic Unsubscription
| Corresponding to message topic subscription, an MSGin5G Client or an Application Server can unsubscribe from one or more Messaging Topic(s) on the MSGin5G Server.
Figure 8.8.3-1 shows the MSGin5G Client/Application Server unsubscribing to Messaging Topic(s) on the MSGin5G Server.
Pre-condition
1. The MSGin5G Client ... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.8.4 Messaging Topic Subscription handling between different MSGin5G Servers
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.8.4.1 General
| When a Messaging Topic(s) is handled between different MSGin5G Servers, the MSGin5G Server 1 may work in the following models, when the subscription for the Messaging Topic exists on Server 2:
a. Mod.A: the MSGin5G UE/Application Server served by MSGin5G Server 1 subscribes to Messaging Topic(s) and the MSGin5G Server... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.8.4.2 Messaging Topic list subscription
| Before the subscribing of Messaging Topic(s), the MSGin5G Server 1 should obtain the available Messaging Topic list on the MSGin5G Server 2 to determine whether to forward the Messaging Topic subscription request to MSGin5G Server 2, to subscribe to the Messaging Topic on behalf of all MSGin5G UE/Application Server ser... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.8.4.3 Messaging Topic Subscription between different MSGin5G Servers
| If the MSGin5G Server 1 works in Mod.A (see clause 8.8.4.1), upon receiving a Messaging Topic subscription request from MSGin5G Client or Application Server, if the Messaging Topic is included in the Messaging Topic list of MSGin5G Server 2, the MSGin5G Server 1 forwards the Messaging Topic subscription request to MSGi... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.8.4.4 Messaging Topic Unsubscription between different MSGin5G Servers
| If the MSGin5G Server 1 works in Mod.A (see clause 8.8.4.1), and upon receiving a Messaging Topic unsubscription request from MSGin5G Client or Application Server, and if the Messaging Topic is included in the Messaging Topic list of MSGin5G Server 2, the MSGin5G Server 1 forwards the Messaging Topic unsubscription req... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.9 Usage of Network Capabilities
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.9.1 General
| The present clause specifies the functionality leveraged by the MSGin5G Service via Core Network exposure.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.9.2 UE reachability status monitoring
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.9.2.1 General
| UE reachability status leverages the 3GPP network monitoring functionality exposed via T8/N33 reference point detailed in 3GPP TS 23.502 [7] and TS 29.522[10]. The MSGin5G Server may use the UE reachability status monitoring by using the 3GPP Network capabilities based on the information, i.e. whether UE reachability s... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.9.2.2 Procedures
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.9.2.2.1 Request-response
| Figure 8.9.2.2.1-1 shows the procedure which may be used by the MSGin5G Server to make a request for UE reachability status information.
Pre-conditions:
1. A UE hosts an MSGin5G Client.
2. The MSGin5G Client has registered with the MSGin5G Server and has shared UE contact information.
3. The MSGin5G Server has de... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.9.2.2.2 Subscribe
| Figure 8.9.2.2.2-1 shows the procedure which may be used by the MSGin5G Server to subscribe for monitoring of UE reachability.
Pre-conditions:
1. A UE hosts an MSGin5G Client.
2. The MSGin5G Client has registered with the MSGin5G Server and has shared UE contact information.
3. The MSGin5G Server subscribes for mon... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.9.2.2.3 Notify
| Figure 8.9.2.2.3-1 shows the procedure which may be for updating MSGin5G reachability status.
Pre-conditions:
1. The MSGin5G Server has subscribed for reachability status monitoring for a UE or group of UEs.
2. The monitored UE(s) has transitioned to Connected Mode, Idle Mode or eDRX paging occasion and the 3GPP Ne... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.9.2.2.4 Unsubscribe
| Figure 8.9.2.2.4-1 shows the procedure which may be used by the MSGin5G Server to unsubscribe from monitoring of UE reachability.
Pre-conditions:
1. The MSGin5G Server has subscribed for reachability status monitoring for a UE or group of UEs.
2. Later, the MSGin5G Server unsubscribes for monitoring of UE reachabil... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.9.2.3 Flows
| The following information flows are specified for UE reachability status monitoring:
- UE Reachability monitoring request and response;
- UE Reachability monitoring subscribe and unsubscribe
- UE Reachability monitoring notify
All UE reachability monitoring interactions from MSGin5G Server (acting as SCS/AS) to SC... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.9.3 MSGin5G device triggering
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.9.3.1 General
| MSGin5G device triggering is the means by which an MSGin5G Server leverages the 3GPP network device triggering capabilities, exposed via T8 /N33 reference point, while attempting to deliver an MSGin5G message. For example, when an Application Server initiates an MSGin5G message request, but the target MSGin5G UE is not... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.9.3.2 Procedure
| Figure 8.9.3.2-1 shows the MSGin5G device triggering procedure.
Pre-conditions:
1. The target UE is an MSGin5G UE.
2. The target MSGin5G Client is registered with the MSGin5G Server.
3. At a later time, after the registration is completed, the MSGin5G UE has become unreachable by the MSGin5G Server.
Figure 8.9.... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.9.3.3 Flows
| The following information flows are specified for MSGin5G triggering:
1. request for device triggering;
2. response to device triggering;
3. device triggering delivery report; and
4. device triggering delivery report response.
All device triggering interactions from MSGin5G Server (acting as SCS/AS) to SCEF/NEF o... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.9.4 Request QoS from 5GC
| In this release, the MSGin5G message delivers via the user plane of 5GC. The MSGin5G Server may request the 5GC to provide specific QoS by using the QoS capabilities provided for user plane.
NOTE: The condition for an MSGin5G server to invoke the QoS capabilities provided by 5GC is determined on an implementation bas... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.10 Usage of SEAL
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.10.1 General
| The MSGin5G Service functional entities MSGin5G Client and MSGin5G Server utilize the SEAL services. All SEAL services specified in 3GPP TS 23.434 [5] are available to MSGin5G Service. In this clause, only the details of the information flows, procedures and APIs whose utilization by MSGin5G Service are well-known are ... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.10.2 Configuration management service
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.10.2.1 General
| The MSGin5G Service functional entities MSGin5G Client and MSGin5G Server utilize configuration management service procedures of SEAL to support MSGin5G Service.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.10.2.2 Information flows
| The following information flows of Configuration Management service are applicable for the MSGin5G Service:
- Get VAL UE configuration request specified in subclause 11.3.2.1 of 3GPP TS 23.434 [5];
- Besides the IEs specified in subclause 11.3.2.1 of 3GPP TS 23.434 [5], the information in table 8.10.2.2-1 is also inc... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.10.2.3 Procedures
| The following procedures of configuration management service are applicable for the MSGin5G Service:
- VAL UE configuration data specified in subclause 11.3.3 of 3GPP TS 23.434 [5].
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.10.3 Group management service
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.10.3.1 General
| The MSGin5G Service functional entities MSGin5G Client and MSGin5G Server utilize SEAL Client and SEAL Server for the group management service (e.g. creation, join, leave) on the group configuration information (e.g. group join policy, group leader) provided by the MSGin5G Server. The decisions and corresponding trigge... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.10.3.2 Information flows
| The information flows of group management procedures are specified in 3GPP TS 23.434 [5].
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.10.3.3 Procedures
| The following procedures of group management service of SEAL as specified in 3GPP TS 23.434 [5] are applicable for the MSGin5G Service:
- Group creation specified in clause 10.3.3;
-- Subsequent to Step 3, when the identity list with the list of VAL user IDs or VAL UE IDs that are part of the created group contain th... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.10.3.4 APIs
| The following APIs of group management service of SEAL as specified in 3GPP TS 23.434 [5] are applicable for the MSGin5G Service:
- SS_GroupManagement API specified in clause 10.4.2;
- SS_Group_Management_Event API specified in clause 10.4.5.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.10.4 MSGin5G used in SEALDD
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.10.4.1 General
| The MSGin5G Client and MSGin5G Server functionalities can be integrated in the Data delivery management service, i.e. SEALDD enabler layer as specified in 3GPP TS 23.433 [20] Annex B. The MSGin5G Client functionality is integrated in the SEALDD client as specified in 3GPP TS 23.433 [20] and the MSGin5G Server functiona... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.10.4.2 Information flows
| The information flows of in clause 8.3, clause 8.4 and clause 8.5 of this document are applicable for the SEALDD utilizing MSGin5G:
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.10.4.3 Procedures
| The following procedures in clause 8.3, clause 8.4 and clause 8.5 of this document are applicable for the SEALDD utilizing MSGin5G:
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.11 Application Client UE in MSGin5G Service
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.11.1 General
| This clause specifies the procedures for an Application Client to perform Application Client registration, to send messages and receive messages using MSGin5G Client regardless whether the Application Client resides on UE-1 or UE-2. The communication between Application Client and MSGin5G Client is over MSGin5G-5 refer... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.11.2 Application Client registration using MSGin5G Client
| The signalling flow for registration of Application Client with MSGin5G Client on MSGin5G UE-1 to use MSGin5G service is illustrated in figure 8.11.2-1.
Pre-conditions:
1. The MSGin5G UE-1 is configured with information to recognize and authorize UE-2 if the Application Client resides on UE-2.
2. The Application Cl... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.11.3 Application Client de-registration using MSGin5G Client
| The signalling flow for deregistration of Application Client with MSGin5G Client-1 on MSGin5G UE-1 is illustrated in figure 8.11.3-1.
Pre-conditions:
1. The Application Client is successfully registered with MSGin5G Client on MSGin5G UE-1.
Figure 8.11.3-1: Deregistration of Application Client with MSGin5G Client ... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.11.4 Application Client sending a message using MSGin5G Client
| The signalling flow for the Application Client to send a message using the MSGin5G Client on MSGin5G UE-1 is illustrated in figure 8.11.4-1.
Pre-conditions:
1. The MSGin5G UE-1 is connected to an access network that provides connectivity to the MSGin5G Server.
2. The Application Client is successfully registered wit... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.11.5 Application Client receiving message via MSGin5G Client on another UE
| The signalling flow for an Application Client to receive a message using the MSGin5G Client on MSGin5G UE-1 is illustrated in figure 8.11.5-1.
Pre-conditions:
1. The MSGin5G UE-1 is connected to an access network that provides connectivity to the MSGin5G Server.
2. The Application Client is successfully registered ... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 8.11.6 Application Client updating a stored MSGin5G message via MSGin5G client
| The signalling flow for Application Client to update a stored MSGin5G message via MSGin5G Client on MSGin5G UE-1 is illustrated in figure 8.11.6-1.
Pre-conditions:
1. The MSGin5G UE-1 is connected to an access network that provides connectivity to the MSGin5G Server.
2. The Application Client is successfully regist... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9 APIs and related information flows
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1 APIs provided by MSGin5G Server
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.1 Mm5s APIs
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.1.1 M5S_AS_Originating_Message_Delivery API
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.1.1.1 General
| API description: This API enables the Application Server to send MSGin5G message to the MSGin5G Server, and enables the MSGin5G Server to send MSGin5G message response notification to the Application Server.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.1.1.2 Send_MSGin5G_Message operation
| API operation name: Send_MSGin5G_Message
Description: Send an MSGin5G message to MSGin5G Server.
Known Consumers: Application Server
Inputs: Refer subclause 9.1.2.1
Outputs: Refer subclause 8.3.2
See subclause 8.3.2 for the details of usage of this API operation.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.1.1.3 Send_MSGin5G_Message response notification operation
| API operation name: Send_MSGin5G_Message response notification
Description: Send an MSGin5G message response notification to Application Server.
Known Consumers: Application Server
Inputs: Refer subclause 9.1.2.7
Outputs: Refer the MSGin5G_Message response in subclause 8.3.2
See subclause 8.3.2 for the details o... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.1.2 M5S_UE_Originating_Message_Delivery API
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.1.2.1 General
| API description: This API enables the Message Gateway or other 5GS Function to deliver MSGin5G message to the MSGin5G Server.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.1.2.2 Send_ MSGin5G_Message operation
| API operation name: Send_MSGin5G_Message
Description: Send an MSGin5G message to MSGin5G Server.
Known Consumers: L3G, N3G.
Inputs: Refer subclause 8.3.2
Outputs: Refer subclause 8.3.2
See subclause 8.3.2 for the details of usage of this API operation.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.1.3 M5S_AS_Originating_Delivery_Status_Report API
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.1.3.1 General
| API description: This API enables the Application Server to delivery MSGin5G message delivery status report to the MSGin5G Server.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.1.3.2 Report_Message_Delivery_Status operation
| API operation name: Report_Message_Delivery_Status
Description: Send an MSGin5G message delivery status report to MSGin5G Server.
Known Consumers: Application Server
Inputs: Refer subclause 9.1.2.2
Outputs: Refer subclause 8.3.4
See subclause 8.3.4 for the details of usage of this API operation.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.1.4 M5S_Delivery_Status_Report API
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.1.4.1 General
| API description: This API enables the Message Gateway to deliver MSGin5G message delivery status reports to the MSGin5G Server.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.1.4.2 Report_Message_Delivery_Status operation
| API operation name: Report_Message_Delivery_Status
Description: Send an MSGin5G message delivery status report to MSGin5G Server.
Known Consumers: L3G, N3G, BMG.
Inputs: Refer subclause 8.3.4
Outputs: Refer subclause 8.3.4
See subclause 8.3.4 for the details of usage of this API operation.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.1.5 M5S_AS_Registration API
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.1.5.1 General
| API description: This API enables the Application Server to register to MSGin5G Server.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.1.5.2 Registration operation
| API operation name: Registration
Description: Do registration or update registration to an MSGin5G Server, by using this API, the Application Server provides/updates its information, including the URL used for the message delivery from MSGin5G Server to Application Server.
Known Consumers: Application Server
Inputs... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.1.5.3 Deregistration operation
| API operation name: Send_MSGin5G_Message
Description: Do deregistration with an MSGin5G Server.
Known Consumers: Application Server
Inputs: Refer subclause 9.1.2.5
Outputs: Refer subclause 9.1.2.6
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.1.6 M5S_Topiclist_Event API
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.1.6.1 General
| API description: This API enables another MSGin5G Server to communicate with the MSGin5G Server to subscribe and receive subsequent notification events of the Messaging Topic list and information of specific message topics on the MSGin5G Server.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.1.6.2 Subscribe Messaging Topiclist operation
| API operation name: Subscribe_Messaging_Topiclist
Description: Subscribing to changes to Messaging Topic list on the MSGin5G Server.
Known Consumers: MSGin5G Server
Inputs: Refer subclause 8.8.4.2
Outputs: Refer subclause 8.8.4.2
See subclause 8.8.4.2 for the details of usage of this API operation
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.1.6.3 Notify Messaging Topiclist operation
| API operation name: Notify_Messaging_Topiclist
Description: Notification for changes to Messaging Topic list on the MSGin5G Server.
Known Consumers: MSGin5G Server
Inputs: Refer subclause 8.8.4.2
Outputs: Refer subclause 8.8.4.2
See subclause 8.8.4.2 for the details of usage of this API operation
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.1.6.4 Subscribe Messaging Topic operation
| API operation name: Subscribe_Messaging_Topic
Description: Subscribing to changes to one or more specific Messaging Topic(s) on the MSGin5G Server.
Known Consumers: MSGin5G Server
Inputs: Refer subclause 8.8.4.3
Outputs: Refer subclause 8.8.4.3
See subclause 8.8.4.3 for the details of usage of this API operation
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.1.6.5 Notify Messaging Topic operation
| API operation name: Notify_Messaging_Topic
Description: Notification for changes to one or more specific Messaging Topic(s) on the MSGin5G Server.
Known Consumers: MSGin5G Server
Inputs: Refer subclause 8.8.4.3
Outputs: Refer subclause 8.8.4.3
See subclause 8.8.4.3 for the details of usage of this API operation
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.1.6.6 Unsubscribe Messaging Topiclist operation
| API operation name: Unsubscribe_Messaging_Topiclist
Description: Unsubscribing to changes to Messaging Topic list on the MSGin5G Server.
Known Consumers: MSGin5G Server
Inputs: Refer subclause 8.8.4.2a
Outputs: Refer subclause 8.8.4.2a
See subclause 8.8.4.2 for the details of usage of this API operation
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.1.6.7 Unsubscribe Messaging Topic operation
| API operation name: Unsubscribe_Messaging_Topic
Description: Unsubscribing to changes to one or more specific Messaging Topic(s) on the MSGin5G Server.
Known Consumers: MSGin5G Server
Inputs: Refer subclause 8.8.4.4
Outputs: Refer subclause 8.8.4.4
See subclause 8.8.4.4 for the details of usage of this API operati... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.2 Mm5s Information flows
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.