Method for providing message service in 5g system, msgin 5g server and non-msgin 5g gateway

Abstract

The present disclosure relates to a fifth generation (5G) or 5G communication system to support higher data rates beyond the fourth generation (4G) communication system, e.g., long term evolution (LTE). Embodiments herein provide a method for providing message service in a fifth generation system, a MSGin5G server and a non-MSGin5G gateway. The provided method provides a TRF capable of assisting a MSGin5G server to determine a transmission service, and a GWSF capable of assisting a MSGin5G server to determine a proper gateway for the determined transmission service. Furthermore, the provided method comprises a TF for translating a MSGin5G message into a legacy 3GPP message format or a non-3GPP message format.

Description

Technical Field

[0001] This disclosure relates to a wireless network, and more specifically to a method for providing messaging services in a 5G system, an MSGin5G server, and a non-MSGin5G gateway. Background Technology

[0002] To meet the increased demand for wireless data services since the deployment of fourth-generation (4G) communication systems, efforts have been made to develop improved fifth-generation (5G) or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also referred to as "post-4G networks" or "post-LTE systems".

[0003] 5G communication systems are considered to be implemented in higher frequency (mmWave) bands, such as the 60GHz band, to achieve higher data rates. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies are discussed in 5G communication systems.

[0004] In addition, in 5G communication systems, development is underway to improve system networks based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multipoint (CoMP), and receiver interference cancellation.

[0005] In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) are developed as advanced coding modulation (ACM), while filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) are developed as advanced access technologies.

[0006] Typically, the 3GPP (3rd Generation Partnership Project) currently describes messaging in 5G (MSGin5G) application services as messaging services within a 5G system. The application architecture for MSGin5G application services, as specified in 3GPP TS 23.554, is intended to support various user equipment (UE) types (based on the underlying transport services supported by the UE, such as MSGin5G transport services and non-MSGin5G transport services)). UE types include MSGin5G UEs, legacy 3GPP UEs, and non-3GPP UEs.

[0007] MSGin5G UEs support MSGin5G clients and are capable of sending MSGin5G message payloads. However, traditional 3GPP UEs do not support MSGin5G, instead using one of the 3GPP-defined messaging mechanisms (e.g., Short Message Service (SMS), Non-IP Data Delivery (NIDD), Broadcast, etc.). Furthermore, non-3GPP UEs do not support MSGin5G clients, but support one of the non-3GPP messaging mechanisms (e.g., Rich Communication Services (RCS) and Lightweight M2M (LwM2M), etc.). Therefore, it is desirable to provide a useful alternative for transmitting messages / MSGin5G message payloads in 5G systems. Summary of the Invention

[0008] Technical issues

[0009] The primary objective of this embodiment is to determine whether a target UE supports the MSGin5G transport service when it receives an MSGin5G message request from a source UE to deliver a message to a target UE in the wireless network, using the Target Resolution Function (TRF) of the MSGin5G server. Furthermore, in response to determining that the target UE supports the MSGin5G transport service, the MSGin5G server sends a message to the target UE. Additionally, in response to determining that the target UE does not support the MSGin5G transport service, the MSGin5G server uses its Gateway Selection Function (GWSF) to select a non-MSGin5G gateway in the wireless network. Furthermore, the MSGin5G server sends a message to the non-MSGin5G gateway, where the non-MSGin5G gateway uses its Translation Function (TF) to translate the MSGin5G message request according to the non-MSGin5G transport service, and then sends the translated message to the target UE. As a result, even if the target UE does not support the MSGin5G message payload / MSGin5G client, the source UE (i.e., MSGin5G UE) still sends messages to the target UE (e.g., MSGin5G UE, traditional 3GPP UE, non-3GPP UE, etc.), and the target UE does not need any external hardware to communicate with the source UE.

[0010] Another objective of this embodiment is to determine whether the target UE is registered in the MSGin5G UE registration store of the MSGin5G server. Furthermore, in response to determining that the target UE is registered in the MSGin5G UE registration store of the MSGin5G server, the MSGin5G server detects that the target UE supports MSGin5G transport services. Furthermore, in response to determining that the target UE is not registered in the MSGin5G UE registration store of the MSGin5G server, the MSGin5G server detects that the target UE supports non-MSGin5G transport services.

[0011] Another objective of the embodiments described herein is to detect whether a target UE is a traditional 3GPP UE or a non-3GPP UE based on the UE registration store of the Home Subscriber Server (HSS) and / or Unified Data Management (UDM) in the wireless network.

[0012] Technical solution

[0013] Therefore, embodiments herein disclose a method for transmitting fifth-generation messaging (MSGin5G) in a wireless network. The method includes receiving an MSGin5G message request from a source UE by an MSGin5G server for transmitting the message to a target UE in the wireless network. Furthermore, upon receiving the MSGin5G message request from the source UE, the method includes determining, using the MSGin5G server's TRF (based on the target UE's MSGin5G service identifier), whether the target UE supports the MSGin5G transport service. Additionally, the method includes sending a message to the target UE in response to determining that the target UE supports the MSGin5G transport service. Furthermore, the method includes using the MSGin5G server's GWSF to select a non-MSGin5G gateway in the wireless network in response to determining that the target UE does not support the MSGin5G transport service. Furthermore, the method includes sending a message to a non-MSGin5G gateway, wherein the non-MSGin5G gateway uses its TF to translate the MSGin5G message request according to the non-MSGin5G transport service, and the non-MSGin5G gateway sends the message to the target UE after translation.

[0014] In one embodiment, an MSGin5G message request includes the MSGin5G service identifier (ID) of the source UE, the MSGin5G service ID of the target UE, and message ID information, delivery status, application ID, payload, and priority type information elements.

[0015] In one embodiment, non-MSGin5G transport services include traditional 3GPP transport services and / or non-3GPP transport services.

[0016] In one embodiment, the non-MSGin5G gateway includes a traditional 3GPP messaging gateway and / or a non-3GPP messaging gateway.

[0017] In one embodiment, a conventional 3GPP message gateway is used to deliver messages to the target UE using 3GPP transport services, while a non-3GPP message gateway is used to deliver messages to the target UE using non-3GPP transport services.

[0018] In this embodiment, the source UE is an MSGin5G UE and the target UE is an MSGin5G UE and a non-MSGin5G UE, wherein the MSGin5G UE supports MSGin5G transmission services and the target UE supports MSGin5G transmission services and / or non-MSGin5G transmission services.

[0019] In one embodiment, a non-MSGin5G UE is a traditional 3GPP UE and / or a non-3GPP UE.

[0020] In one embodiment, when an MSGin5G message request is received from a source UE, the MSGin5G server uses its TRF (based on the target UE's MSGin5G service identifier) ​​to determine whether the target UE supports MSGin5G transport services. This includes the MSGin5G server determining whether the target UE is registered in the MSGin5G server's MSGin5G UE registration store. Furthermore, the method includes detecting that the target UE supports MSGin5G transport services in response to determining that the target UE is registered in the MSGin5G server's MSGin5G UE registration store. Additionally, the method includes detecting that the target UE supports non-MSGin5G transport services in response to determining that the target UE is not registered in the MSGin5G server's MSGin5G UE registration store.

[0021] In one embodiment, detecting that the target UE supports traditional 3GPP transport services includes the MSGin5G server detecting that the target UE is registered in the UE registration repository of the HSS and / or UDM in the wireless network.

[0022] In this embodiment, detecting that the target UE supports non-3GPP transmission services includes the MSGin5G server detecting that the target UE is not registered in the MSGin5G UE registration store and is not registered in the registration store of the HSS and / or UDM in the wireless network.

[0023] In one embodiment, the GWSF selection of a non-MSGin5G gateway in a wireless network using an MSGin5G server includes the MSGin5G server selecting one of a traditional 3GPP messaging gateway and a non-3GPP messaging gateway based on a mapping table available at the GWSF. Furthermore, the method includes the MSGin5G server performing authentication of the source UE. Additionally, the method includes the MSGin5G server sending a message to one of the traditional 3GPP messaging gateways and the non-3GPP messaging gateway based on the selection.

[0024] In one embodiment, translating an MSGin5G message request using TF based on a non-MSGin5G transport service includes the MSGin5G server detecting that a legacy 3GPP messaging gateway has been selected. Furthermore, the method includes the legacy 3GPP messaging gateway determining a messaging mechanism for sending messages to the target UE based on the target UE's capabilities, communication state, and service configuration, wherein the messaging mechanism is one of SMS and NIDD. Additionally, the method includes the legacy 3GPP messaging gateway performing registration and deregistration for the non-MSGin5G UE with the MSGin5G server. Furthermore, the method includes the legacy 3GPP messaging gateway performing message segmentation and message reassembly for the non-MSGin5G UE. Furthermore, the method includes the legacy 3GPP messaging gateway performing address translation for the target UE. Furthermore, the method includes the legacy 3GPP messaging gateway translating the protocol and non-message payload information of the message based on the determined messaging mechanism. Finally, the method includes the legacy 3GPP messaging gateway sending the message to the target UE.

[0025] In one embodiment, a conventional 3GPP messaging gateway receives a delivery report from the target UE, translates the received delivery report into an MSGin5G message delivery report, and sends the MSGin5G message delivery report to the MSGin5G server.

[0026] In one embodiment, translating an MSGin5G message request using TF based on a non-MSGin5G transport service includes the MSGin5G server detecting that a non-3GPP message gateway has been selected. Furthermore, the method includes the non-3GPP message gateway determining a messaging mechanism for sending messages to the target UE based on the target UE's capabilities, the target UE's communication state, and the target UE's service configuration, wherein the messaging mechanism is one of RCS and LwM2M. Furthermore, the method includes the non-3GPP message gateway translating the message into a non-3GPP message based on the determined messaging mechanism. Finally, the method includes the non-3GPP message gateway sending the message to the target UE.

[0027] In one embodiment, a non-3GPP messaging gateway receives a delivery report from the target UE, translates the received delivery report into an MSGin5G message delivery report, and sends the MSGin5G message delivery report to the MSGin5G server.

[0028] Therefore, the embodiments herein disclose an MSGin5G server for transmitting MSGin5G messages in a wireless network. The MSGin5G server includes an MSGin5G controller coupled to a processor and memory. The MSGin5G controller is configured to receive an MSGin5G message request from a source UE for transmitting the message to a target UE in the wireless network. Furthermore, the MSGin5G controller is configured to, upon receiving an MSGin5G message request from the source UE, use the TRF (Telegraphic Request Forwarding) of the MSGin5G server (based on the MSGin5G service identifier of the target UE) to determine whether the target UE supports the MSGin5G transport service. Furthermore, the MSGin5G controller is configured to send a message to the target UE in response to determining that the target UE supports the MSGin5G transport service. Furthermore, the MSGin5G controller is configured to, in response to determining that the target UE does not support the MSGin5G transport service, use the GWSF of the MSGin5G server to select a non-MSGin5G gateway in the wireless network. Furthermore, the MSGin5G controller is configured to send messages to non-MSGin5G gateways.

[0029] Therefore, the embodiments herein disclose a non-MSGin5G gateway for transmitting MSGin5G messages in a wireless network. The non-MSGin5G gateway includes an MSGin5G controller coupled to a processor and memory. The MSGin5G controller is configured to translate MSGin5G message requests using the TF of the non-MSGin5G gateway according to a non-MSGin5G transport service, and the non-MSGin5G gateway sends the message to the target UE after translation.

[0030] These and other aspects of the embodiments described herein will be better appreciated and understood when considered in conjunction with the following description and accompanying drawings. However, it should be understood that while the following description indicates preferred embodiments and many specific details thereof, it is given by way of illustration rather than limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit of this disclosure, and the embodiments herein include all such modifications.

[0031] Before proceeding with the following detailed description, it may be advantageous to define certain words and phrases used in this patent document: the terms “comprising” and “including” and their derivatives mean including but not limited to; the term “or” is inclusive, referring to and / or; the phrases “associated with” and “associated with” and their derivatives may mean including, being included, interconnected with, containing, being contained, connected to or connected to, coupled to or coupled to, able to communicate with, cooperate with, interleaved, juxtaposed, adjacent, bound to or bound to, having, having the properties of, etc.; and the term “controller” means any device, system or part thereof that controls at least one operation, such device may be implemented in hardware, firmware or software, or at least a combination of two of the same. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether local or remote.

[0032] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and contained in a computer-readable medium. The terms "application program" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium accessible by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable media excludes wired, wireless, optical, or other communication links that transmit transient electrical or other signals. A non-transitory computer-readable medium includes media that can permanently store data and media that can store data and subsequently rewrite it, such as rewritable optical discs or erasable storage devices.

[0033] Definitions of certain words and phrases are provided throughout this patent document, and those skilled in the art will understand that, in many cases, if not most, such definitions apply to the existing and future use of the words and phrases defined therein.

[0034] Technical effect

[0035] According to this disclosure, the improvement is and relates to an MSGin5G server for determining the transport services supported by a target user equipment (UE) and determining an appropriate gateway for the determined transport services. Attached Figure Description

[0036] This disclosure is illustrated in the accompanying drawings, in which the same reference numerals denote corresponding parts in the various drawings. The embodiments herein will be better understood from the following description with reference to the accompanying drawings, in which:

[0037] Figure 1 The architecture of the MSGin5G application service specified in 3GPP TS 23.554v0.3.0 according to the embodiments disclosed herein is shown;

[0038] Figure 2A A block diagram of an MSGin5G server for transmitting MSGin5G messages in a wireless network, according to embodiments disclosed herein, is shown.

[0039] Figure 2B A block diagram of a non-MSGin5G gateway for transmitting MSGin5G messages in a wireless network, according to embodiments disclosed herein, is shown.

[0040] Figure 3 This is a flowchart illustrating a method for transmitting MSGin5G messages in a wireless network according to embodiments disclosed herein;

[0041] Figure 4 This is a sequence diagram illustrating various operations for sending MSGin5G messages from a source UE to a target UE in a wireless network according to embodiments disclosed herein, wherein both the source UE and the target UE support the MSGin5G transport service.

[0042] Figure 5 This is a sequence diagram illustrating various operations for sending MSGin5G messages from a source UE to a target UE in a wireless network according to embodiments disclosed herein, wherein the source UE supports MSGin5G transport services and the target UE acts as a traditional 3GPP UE supporting non-MSGin5G transport services; and

[0043] Figure 6 This is a sequence diagram illustrating various operations for sending MSGin5G messages from a source UE to a target UE in a wireless network according to embodiments disclosed herein, wherein the source UE supports MSGin5G transport services and the target UE acts as a non-3GPP UE that supports non-MSGin5G transport services. Detailed Implementation

[0044] The following discussion Figures 1 to 6 The various embodiments used to describe the principles of this disclosure in this patent document are merely exemplary and should not be construed in any way as limiting the scope of this disclosure. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged system or apparatus.

[0045] The embodiments described herein, along with their various features and advantageous details, will be explained more fully with reference to the non-limiting embodiments shown in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques have been omitted so as not to unnecessarily obscure the embodiments herein. Furthermore, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments may be combined with one or more other embodiments to form new embodiments. Unless otherwise stated, the term "or" as used herein means non-exclusive or. The examples used herein are intended only to aid in understanding how the embodiments described herein can be practiced, and further to enable those skilled in the art to practice the embodiments described herein. Therefore, the embodiments should not be construed as limiting the scope of the embodiments described herein.

[0046] As is conventional in the art, embodiments can be described and illustrated in terms of blocks that perform one or more described functions. These blocks may be referred to herein as managers, units, modules, hardware components, etc., and are physically implemented by analog and / or digital circuitry, such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuitry, etc., and may optionally be driven by firmware. For example, the circuitry may be embodied in one or more semiconductor chips or on a substrate support such as a printed circuit board. The circuitry constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware (performing some functions of the block) and a processor (performing other functions of the block). Each block of an embodiment may be physically divided into two or more interactive and discrete blocks without departing from the scope of this disclosure. Similarly, blocks of embodiments may be physically combined into more complex blocks without departing from the scope of this disclosure.

[0047] Therefore, embodiments herein disclose a method for transmitting fifth-generation messaging (MSGin5G) in a wireless network. The method includes receiving an MSGin5G message request from a source UE by an MSGin5G server for transmitting the message to a target UE in the wireless network. Furthermore, upon receiving the MSGin5G message request from the source UE, the method includes determining, using the MSGin5G server's TRF (based on the target UE's MSGin5G service identifier), whether the target UE supports the MSGin5G transport service. Additionally, the method includes sending a message to the target UE in response to determining that the target UE supports the MSGin5G transport service. Furthermore, the method includes using the MSGin5G server's GWSF to select a non-MSGin5G gateway in the wireless network in response to determining that the target UE does not support the MSGin5G transport service. Furthermore, the method includes sending a message to a non-MSGin5G gateway, wherein the non-MSGin5G gateway uses its TF to translate the MSGin5G message request according to the non-MSGin5G transport service, and the non-MSGin5G gateway sends the message to the target UE after translation.

[0048] Therefore, the embodiments herein disclose an MSGin5G server for transmitting MSGin5G messages in a wireless network. The MSGin5G server includes an MSGin5G controller coupled to a processor and memory. The MSGin5G controller is configured to receive an MSGin5G message request from a source UE for transmitting the message to a target UE in the wireless network. Furthermore, the MSGin5G controller is configured to, upon receiving an MSGin5G message request from the source UE, use the TRF (Telegraphic Request Forwarding) of the MSGin5G server (based on the MSGin5G service identifier of the target UE) to determine whether the target UE supports the MSGin5G transport service. Furthermore, the MSGin5G controller is configured to send a message to the target UE in response to determining that the target UE supports the MSGin5G transport service. Furthermore, the MSGin5G controller is configured to, in response to determining that the target UE does not support the MSGin5G transport service, use the GWSF of the MSGin5G server to select a non-MSGin5G gateway in the wireless network. Furthermore, the MSGin5G controller is configured to send messages to non-MSGin5G gateways.

[0049] Therefore, the embodiments herein disclose a non-MSGin5G gateway for transmitting MSGin5G messages in a wireless network. The non-MSGin5G gateway includes an MSGin5G controller coupled to a processor and memory. The MSGin5G controller is configured to translate MSGin5G message requests using the TF of the non-MSGin5G gateway according to a non-MSGin5G transport service, and the non-MSGin5G gateway sends the message to the target UE after translation.

[0050] Traditional 3GPP UEs do not support MSGin5G, but instead use one of the 3GPP-defined messaging mechanisms (e.g., SMS, NIDD, broadcast, etc.). Furthermore, non-3GPP UEs do not support MSGin5G clients, but do support one of the non-3GPP messaging mechanisms (e.g., RCS and LwM2M, etc.).

[0051] The method provided in this disclosure allows an MSGin5G server, upon receiving an MSGin5G message request from a source UE for transmitting a message (i.e., an MSGin5G message) to a target UE in a wireless network, to determine whether the target UE supports the MSGin5G transport service using the MSGin5G server's TRF (based on the target UE's MSGin5G service identifier). Furthermore, in response to determining that the target UE supports the MSGin5G transport service, the MSGin5G server sends a message to the target UE. Additionally, in response to determining that the target UE does not support the MSGin5G transport service, the MSGin5G server uses its GWSF to select a non-MSGin5G gateway in the wireless network. Furthermore, the MSGin5G server sends a message to the non-MSGin5G gateway, wherein the non-MSGin5G gateway uses its TF to translate the MSGin5G message request according to the non-MSGin5G transport service, and the non-MSGin5G gateway sends the translated message to the target UE. As a result, even if the target UE does not support the MSGin5G message payload / MSGin5G client, the source UE (i.e., MSGin5G UE) still sends messages to the target UE (e.g., MSGin5G UE, traditional 3GPP UE, non-3GPP UE, etc.), and the target UE does not need any external hardware to communicate with the source UE.

[0052] The method provided in this disclosure allows an MSGin5G server to determine whether the MSGin5G service identifier of a target UE is registered in the MSGin5G server's MSGin5G UE registration store. Furthermore, in response to determining that the target UE is registered in the MSGin5G server's MSGin5G UE registration store, the MSGin5G server detects that the target UE supports MSGin5G transport services. Furthermore, in response to determining that the target UE is not registered in the MSGin5G server's MSGin5G UE registration store, the MSGin5G server detects that the target UE supports non-MSGin5G transport services.

[0053] The method provided in this disclosure allows the MSGin5G server to detect whether a target UE is a traditional 3GPP UE or a non-3GPP UE based on the UE registration store of the HSS and / or UDM in the wireless network.

[0054] Now refer to the attached diagram, for more specific details. Figures 1 to 6 A preferred embodiment is shown, wherein similar reference numerals in all figures always denote corresponding features.

[0055] Figure 1 The architecture of the MSGin5G application service (1000) specified in 3GPP TS 23.554 according to the embodiments disclosed herein is shown.

[0056] The MSGin5G application service (1000) includes an MSGin5G server (200), a SEAL server (200A), an application server (200B), a source UE (100A) (i.e., MSGin5G UE-1), a target UE (100B) (MSGin5G UE-2 (100Ba) or a traditional 3GPP UE (100Bb) or a non-3GPP UE (100Bc)), a non-MSGin5G gateway (300) (a traditional 3GPP messaging gateway (300A) or a non-3GPP messaging gateway (300B)), and a 3GPP core network (400).

[0057] In one embodiment, the MSGin5G server (200) provides server-side functionality to assist MSGin5G clients (e.g., MSGin5G UE-1 (100A), MSGin5G UE-2 (100Ba), etc.) in sending and receiving messages via MSGin5G services to / from the application server (200B) and / or other UEs (e.g., legacy 3GPP UE (100Bb), non-3GPP UE (100Bc), etc.). A messaging mechanism for the MSGin5G service endpoint is resolved based on the terminated MSGin5G service ID, allowing the MSGin5G server (200) to determine, for the final delivery, whether to deliver the message to the target UE (100B), application server (200B), or non-MSGin5G gateway (300).

[0058] In one embodiment, the MSGin5G server (200) includes a TRF (241) and a GWSF (242). Figure 1 Not shown in the diagram. The TRF (241) provides the function to help the MSGin5G server (200) determine the transport services supported by the target UE (100B). Upon receiving an MSGin5G message request, the TRF (241) checks the target endpoint identifier (i.e., the target UE (100B)) in the MSGin5G server (200)'s MSGin5G UE registration store (a database created when each MSGin5G UE (e.g., MSGin5G UE-1 (100A), MSGin5G UE-2 (100Ba) etc.) registered with the MSGin5G server (200). If the target endpoint identifier is found in the store, the transport services supported by the target UE (100B) are confirmed as MSGin5G. The UE (100B) can understand the MSGin5G message payload. If the target endpoint identifier is not found in the repository, the MSGin5G server (200) checks the target endpoint identifier in the repository at the HSS / UDM. If the target endpoint identifier is found in the repository at the HSS / UDM, the transport service supported by the target UE (100B) is determined to be a non-MSGin5G transport service, and the support of a non-MSGin5G gateway (300) is required to understand the MSGin5G message payload.

[0059] In addition, GWSF (242) provides the function of assisting MSGin5G server (200) in determining the appropriate non-MSGin5G gateway (300) (traditional 3GPP messaging gateway (300A) or non-3GPP messaging gateway (300B)) for the transport services supported by the target UE (100B). Upon receiving a transport service determined by TRF (241) and supported by the target UE (100B), GWSF (242) selects the appropriate non-MSGin5G gateway (300) (traditional 3GPP messaging gateway (300A) or non-3GPP messaging gateway (300B)) based on the mapping table available on GWSF (242).

[0060] In one embodiment, the non-MSGin5G gateway (300) (traditional 3GPP messaging gateway (300A) and / or non-3GPP messaging gateway (300B)) includes TF (341). Figure 1 Not shown in the diagram. TF(341) performs the translation of the address of the target UE(100B) as understood in the destination domain, as well as the translation of the protocol and payload, based on the transport services supported by the target UE(100B).

[0061] In one embodiment, a non-MSGin5G gateway (300) in an MSGin5G application architecture provides the functionality to deliver MSGin5G messages to non-MSGin5G UEs (i.e., legacy 3GPP UEs (100Bb) and non-3GPP UEs (100Bc)). The non-MSGin5G gateway (300) acts as an interoperator between two different messaging mechanisms and ensures message consistency between them. The messaging mechanisms comprise a specific set of protocols, procedures, and rules.

[0062] In one embodiment, the non-MSGin5G gateway (300) enables seamless delivery of MSGin5G messages between different messaging mechanisms with consistency. Furthermore, the non-MSGin5G gateway (300) communicates with the MSGin5G server (200) using MSGin5G client functionality or similar features to allow sending and receiving MSGin5G messages. Additionally, the non-MSGin5G gateway (300) uses the specific messaging mechanism available to the non-MSGin5G UE to deliver the payload of the MSGin5G message to the non-MSGin5G UE (i.e., a traditional 3GPP UE (100Bb) and a non-3GPP UE (100Bc)) and vice versa. Furthermore, the non-MSGin5G gateway (300) performs sender and receiver address translation according to the messaging mechanisms of both connections and maintains a mapping of address pairs used for responding to message delivery. Furthermore, the non-MSGin5G gateway (300) performs registration and deregistration with the MSGin5G server (200) on behalf of the non-MSGin5G UE. Additionally, the non-MSGin5G gateway (300) acts as a service endpoint to perform message fragmentation and reassembly for the non-MSGin5G UE when necessary. Furthermore, the non-MSGin5G gateway (300) performs protocol and non-message payload information conversion based on the services supported by the target UE (100B).

[0063] In one embodiment, a conventional 3GPP messaging gateway (300A) is used to forward MSGin5G messages to a conventional 3GPP UE (100B) using a 3GPP-enabled messaging mechanism. Additionally, a non-3GPP messaging gateway (300B) is used to forward MSGin5G messages to a non-3GPP UE (100Bc) using a (non-3GPP)-enabled messaging mechanism.

[0064] In one embodiment, TRF (241) and GWSF (242) reside in the MSGin5G server (200), and TF (341) resides in the message gateway. In this embodiment, each logical function (TRF (241), GWSF (242), and TF (341)) performs its respective role and function through an interface inside the MSGin5G server (200).

[0065] In one embodiment, all logical functions (TRF(241), GWSF(242), and TF(341)) can coexist with another entity in the MSGin5G application service (1000), and in this case, the relevant interface functions are located within the entity hosting the logical functions.

[0066] Figure 2AA block diagram of an MSGin5G server (200) for transmitting MSGin5G messages in a wireless network according to an embodiment disclosed herein is shown.

[0067] In one embodiment, the MSGin5G server (200) includes a memory (210), a processor (220), a communicator (230), and an MSGin5G controller (240).

[0068] The memory (110) stores the MSGin5G service identifier (ID) of the source UE (100A), the MSGin5G service ID of the target UE (100B), and message ID information elements, message ID information, delivery status, application ID, payload, priority type information elements, and the MSGin5G UE registration store. Additionally, the memory (210) stores instructions to be executed by the processor (220). The memory (210) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard disks, optical disks, floppy disks, flash memory, or electrically programmable memory (EPROM) or electrically erasable programmable memory (EEPROM). Furthermore, in some examples, the memory (210) may be considered a non-transitory storage medium. The term "non-transitory" may mean that the storage medium is not included in a carrier or propagating signal. However, the term "non-transitory" should not be construed as meaning that the memory (210) is immovable. In some instances, the memory (210) may be configured to store a large amount of information. In some instances, non-transitory storage media may store data that may change over time (e.g., in random access memory (RAM) or cache memory). The memory (210) may be an internal storage unit, or it may be an external storage unit of the MSGin5G server (200), cloud storage, or any other type of external storage.

[0069] The processor (220) communicates with the memory (210), the communicator (230), and the MSGin5G controller (240). The processor (220) is configured to execute instructions stored in the memory (210) and perform various processes. The processor (220) may include one or more processors, such as a general-purpose processor like a central processing unit (CPU), an application processor (AP), a graphics-only unit like a graphics processing unit (GPU), a visual processing unit (VPU), and / or an artificial intelligence (AI) dedicated processor like a neural processing unit (NPU).

[0070] The communicator (230) includes electronic circuitry dedicated to standards that allow for wired or wireless communication. The communicator (230) is configured to communicate internally between internal hardware components and with external devices via one or more networks.

[0071] In one embodiment, the MSGin5G controller (240) is implemented by processing circuitry such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuitry, etc., and may optionally be driven by firmware. For example, the circuitry may be embodied in one or more semiconductors.

[0072] In one embodiment, the MSGin5G controller (240) includes a TRF (241) and a GWSF (242). The MSGin5G controller (240) is configured to receive an MSGin5G message request from a source UE (100A) to transmit the message to a target UE (100B) in the wireless network. Furthermore, the MSGin5G controller (240) is configured to, upon receiving an MSGin5G message request from the source UE (100A), use the TRF (241) of the MSGin5G server (200) to determine whether the target UE (100B) supports the MSGin5G transport service. Additionally, the MSGin5G controller (240) is configured to send a message to the target UE (100B) in response to determining that the target UE (100B) supports the MSGin5G transport service. Furthermore, the MSGin5G controller (240) is configured to use the GWSF (242) of the MSGin5G server (200) to select a non-MSGin5G gateway (300) in the wireless network in response to determining that the target UE (100B) does not support MSGin5G transport services. Additionally, the MSGin5G controller (240) is configured to send messages to the non-MSGin5G gateway (300).

[0073] Furthermore, the MSGin5G controller (240) is configured to determine whether the target UE (100B) is registered in the MSGin5G UE registration store of the MSGin5G server (200). Additionally, the MSGin5G controller (240) is configured to detect that the target UE (100B) supports MSGin5G transport services in response to determining that the target UE (100B) is registered in the MSGin5G UE registration store of the MSGin5G server (200). Furthermore, the MSGin5G controller (240) is configured to detect that the target UE (100B) supports non-MSGin5G transport services in response to determining that the target UE (100B) is not registered in the MSGin5G UE registration store of the MSGin5G server (200).

[0074] Furthermore, the MSGin5G controller (240) is configured to detect that the target UE (100B) is registered in the UE registration store of the HSS and / or UDM in the wireless network. Furthermore, the MSGin5G controller (240) is configured to select one of a legacy 3GPP messaging gateway (300A) and a non-3GPP messaging gateway (300B). Furthermore, the MSGin5G controller (240) is configured to perform authentication of the source UE (100A). Furthermore, the MSGin5G controller (240) is configured to send messages to one of the legacy 3GPP messaging gateway (300A) and the non-3GPP messaging gateway (300B) based on the selection.

[0075] although Figure 2A Various hardware components of the MSGin5G server (200) are illustrated, but it should be understood that other embodiments are not limited thereto. In other embodiments, the MSGin5G server (200) may include fewer or more components. Furthermore, the labels or names of the components are for illustrative purposes only and do not limit the scope of this disclosure. One or more components may be combined together to perform the same or substantially similar functions to deliver MSGin5G in a wireless network.

[0076] Figure 2B A block diagram of a non-MSGin5G gateway (300) for transmitting MSGin5G messages in a wireless network according to an embodiment disclosed herein is shown.

[0077] In one embodiment, the non-MSGin5G gateway (300) includes a memory (310), a processor (320), a communicator (330), and an MSGin5G controller (340).

[0078] The memory (310) stores the MSGin5G service identifier (ID) of the source UE (100A), the MSGin5G service ID of the target UE (100B), and message ID information, delivery status, application ID, payload, priority type information elements, and UE registration stores for HSS and UDM. Additionally, the memory (310) stores instructions to be executed by the processor (320). The memory (310) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard disks, optical disks, floppy disks, flash memory, or electrically programmable memory (EPROM) or electrically erasable programmable memory (EEPROM). Furthermore, in some examples, the memory (310) may be considered a non-transitory storage medium. The term "non-transitory" may mean that the storage medium is not included in a carrier or propagating signal. However, the term "non-transitory" should not be interpreted as the memory (310) being immovable. In some instances, the memory (310) may be configured to store a large amount of information. In some instances, non-transitory storage media may store data that may change over time (e.g., in random access memory (RAM) or cache memory). The memory (310) may be an internal storage unit, or the memory (310) may be an external storage unit other than the MSGin5G gateway (300), cloud storage, or any other type of external storage.

[0079] The processor (320) communicates with the memory (310), the communicator (330), and the MSGin5G controller (340). The processor (220) is configured to execute instructions stored in the memory (310) and perform various processes. The processor (320) may include one or more processors, which may be general-purpose processors (e.g., CPU, AP, etc.), graphics processing units (e.g., GPU, VPU), and / or AI-specific processors (e.g., NPU).

[0080] The communicator (330) includes electronic circuitry dedicated to standards that allow for wired or wireless communication. The communicator (330) is configured for internal communication between internal hardware components and for communication with external devices via one or more networks.

[0081] In one embodiment, the MSGin5G controller (340) is implemented by processing circuitry such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuitry, passive electronic components, active electronic components, optical components, hardwired circuitry, etc., and may optionally be driven by firmware. For example, the circuitry may be embodied in one or more semiconductors.

[0082] In one embodiment, the MSGin5G controller (340) includes a TF (341). The MSGin5G controller (340) is configured to use the TF (341) of a non-MSGin5G gateway (300) to translate MSGin5G message requests according to a non-MSGin5G transport service, and the non-MSGin5G gateway (300) sends the message to the target UE (100B) after translation.

[0083] Furthermore, the MSGin5G controller (340) is configured to determine the messaging mechanism for sending messages to the target UE (100B) based on the target UE's (100B) capabilities, communication state, and service configuration, wherein the messaging mechanism is either SMS or NIDD. Additionally, the MSGin5G controller (340) is configured to perform registration and deregistration with the MSGin5G server (200) on behalf of non-MSGin5G UEs. Furthermore, the MSGin5G controller (340) is configured to perform message segmentation and message reassembly for MSGin5G UEs. Furthermore, the MSGin5G controller (340) is configured to perform address translation for the target UE (100B). Furthermore, the MSGin5G controller (340) is configured to translate protocol and non-message payload information of messages based on the determined messaging mechanism. Finally, the MSGin5G controller (340) is configured to send messages to the target UE (100B). In addition, the MSGin5G controller (340) is configured to send MSGin5G message delivery reports to the MSGin5G server (200).

[0084] Furthermore, the MSGin5G controller (340) is configured to determine the messaging mechanism for sending messages to the target UE (100B) based on the target UE (100B)'s capabilities, communication state, and service configuration, wherein the messaging mechanism is either RCS or LwM2M. Additionally, the MSGin5G controller (340) is configured to translate messages into non-3GPP messages based on the determined messaging mechanism. Furthermore, the MSGin5G controller (340) is configured to send messages to the target UE (100B). Furthermore, the MSGin5G controller (340) is configured to send MSGin5G messaging reports to the MSGin5G server (200).

[0085] although Figure 2BVarious hardware components of a non-MSGin5G gateway (300) are illustrated, but it should be understood that other embodiments are not limited thereto. In other embodiments, the non-MSGin5G gateway (300) may include fewer or more components. Furthermore, the designations or names of components are for illustrative purposes only and do not limit the scope of this disclosure. One or more components may be combined together to perform the same or substantially similar functions to deliver MSGin5G in a wireless network.

[0086] Figure 3 This is a flowchart (S300) illustrating a method for transmitting MSGin5G messages in a wireless network according to embodiments disclosed herein. Operations (S302-S312) are performed by an MSGin5G server (200) and a non-MSGin5G gateway (300).

[0087] In S302, the method includes receiving an MSGin5G message request from a source UE (100A) to pass the message to a target UE (100B) in the wireless network. In S304, the method includes determining whether the target UE (100B) supports the MSGin5G transport service using the TRF (based on the MSGin5G service identifier of the target UE) of the MSGin5G server (200). In S306, the method includes determining an action (e.g., S308, S310) based on whether the target UE (100B) supports the MSGin5G transport service upon receiving the MSGin5G message request from the source UE (100A). In S308, the method includes sending a message to the target UE (100B) in response to determining that the target UE (100B) supports the MSGin5G transport service.

[0088] In S310, the method includes selecting a non-MSGin5G gateway (300) in the wireless network using the GWSF (242) of the MSGin5G server (200) in response to determining that the target UE (100B) does not support the MSGin5G transport service. In S312, the method includes sending a message to the non-MSGin5G gateway (300), wherein the non-MSGin5G gateway (300) uses its TF (341) to translate the MSGin5G message request according to the non-MSGin5G transport service, and the non-MSGin5G gateway (300) sends the message to the target UE (100B) after translation.

[0089] The various actions, behaviors, blocks, steps, etc. in the flowchart (S300) can be executed in the presented order, in different orders, or simultaneously. Furthermore, in some embodiments, some actions, behaviors, blocks, steps, etc., can be omitted, added, modified, or skipped without departing from the scope of this disclosure.

[0090] Figure 4 This is a sequence diagram illustrating various operations for sending MSGin5G messages from a source UE (100A) to a target UE (100B) in a wireless network according to embodiments disclosed herein, wherein both the source UE (100A) and the target UE (100B) support the MSGin5G transmission service.

[0091] In this scenario, the prerequisite is that the MSGin5G client-2 of the MSGin5G UE-2 (100Ba) / target UE (100B) is registered with the MSGin5G server (200). At 401, the MSGin5G server (200) has received a valid MSGin5G message from the source UE (100A) (i.e., MSGin5G UE-1). At 402, the TRF (241) checks the registration store of the MSGin5G server (200) to find the target endpoint identifier specified in the received MSGin5G message. The TRF (241) finds the registration information regarding the target endpoint identifier and resolves it to send the MSGin5G message to the MSGin5G UE-2 (100Ba) identified by the target endpoint identifier. At 403, the MSGin5G server (200) forwards the MSGin5G message request to MSGin5GUE-2 (100Ba) (i.e., MSGin5G client-2 (100Baa) / application client (100Bab)). At 404, MSGin5GUE-2 (100Ba) passes the content of the MSGin5G message to the target application client / MSGin5G UE-2 (100Ba) / target UE (100B).

[0092] Figure 5 This is a sequence diagram illustrating various operations for sending MSGin5G messages from a source UE (100A) to a target UE (100B) in a wireless network according to embodiments disclosed herein, wherein the source UE (100A) supports MSGin5G transport services and the target UE (100B) acts as a conventional 3GPP UE (100B) that supports non-MSGin5G transport services.

[0093] According to 3GPP TS 23.554, the prerequisites for this situation are given below:

[0094] I. MSGin5G clients with MSGin5G UE (source UE (100A)) registered in MSGin5G server (200);

[0095] II. The legacy 3GPP messaging gateway (300A) knows the MSGin5G service ID of the legacy 3GPP UE (100Bb) and maintains a mapping to the ID used in the legacy network; and / or

[0096] III. The MSGin5G server (200) can determine whether the target UE (100B) is a traditional 3GPP UE (100B) and which messaging mechanisms are available.

[0097] At 501, the source UE (100A) sends an MSGin5G message request to the MSGin5G server (200). The MSGin5G message request includes the MSGin5G service identifier (ID) of the source UE (100A), the MSGin5G service ID of the target UE (100B), message ID information, delivery status, application ID, payload, and priority type information elements. At 502, upon receiving the MSGin5G message request, the MSGin5G server (200) determines that the recipient is a legacy 3GPP UE (100Bb), and the MSGin5G client (source UE (100A)) is authorized to send an MSGin5G message to the legacy 3GPP UE (100Bb). At 503, the MSGin5G server (200) forwards the MSGin5G message request to the legacy 3GPP messaging gateway (300A).

[0098] At position 504, the legacy 3GPP messaging gateway (300A) determines which legacy 3GPP messaging mechanism (e.g., SMS, NIDD, etc.) to use based on the capabilities of the target UE (100B) / legacy 3GPP UE (100B), the communication status of the target UE (100B) / legacy 3GPP UE (100B), and the service configuration of the target UE (100B) / legacy 3GPP UE (100B). When selected, the legacy 3GPP messaging gateway (300A) maps the MSGin5G service ID to the corresponding identifier. For example (not an exhaustive list), see below:

[0099] I. If the legacy 3GPP messaging gateway (300A) selects device triggering, the legacy 3GPP messaging gateway (300A) will map the service ID to the MSISDN and the application port ID;

[0100] II. If the legacy 3GPP messaging gateway (300A) selects the NIDD delivery mechanism, then the legacy 3GPP messaging gateway (300A) will map the service ID to an external identifier or MSISDN; and / or

[0101] III. If the conventional 3GPP messaging gateway (300A) selects the SMS delivery mechanism, then the conventional 3GPP messaging gateway (300A) will map the service ID to the MSISDN.

[0102] In 505-513, the legacy 3GPP messaging gateway (300A) sends the payload of the MSGin5G message to the legacy 3GPP UE (100B). For example (not an exhaustive list), it is shown below:

[0103] I. For device triggering (505), the conventional 3GPP message gateway (300A) maps the payload of the MSGin5G message to one or more device triggering requests (see 3GPP TS 23.682, 3GPP TS 29.122 and 3GPP TS 29.522);

[0104] II. For the NIDD delivery mechanism (506), the legacy 3GPP messaging gateway (300A) maps the payload of the MSGin5G message to one or more NIDD commit request messages (see 3GPP TS 23.682, 3GPP TS 29.122, and 3GPP TS 29.522). Alternatively, if tunneling parameters are provided in the legacy 3GPP messaging gateway (see 3GPP TS 23.401, 3GPP TS 23.501, and 3GPP TS 23.502); and / or

[0105] III. For the SMS delivery mechanism (507), the legacy 3GPP message gateway (300A) sends SMS to the legacy 3GPP UE (100Bb) according to the procedure in 3GPP TS 23.204 or 3GPP TS 23.502.

[0106] In 508-509, if the required delivery status is included in the MSGin5G message request, the traditional 3GPP message gateway (300A) sends an MSGin5G message delivery report to the MSGin5G server (200), and the MSGin5G server (200) sends a delivery report to the MSGin5G client (source UE (100A)) as specified in 3GPP TS 23.554.

[0107] Figure 6This is a sequence diagram illustrating various operations for sending MSGin5G messages from a source UE (100A) to a target UE (100B) in a wireless network according to embodiments disclosed herein, wherein the source UE (100A) supports MSGin5G transport services and the target UE (100B) acts as a non-3GPP UE (100Bc) that supports non-MSGin5G transport services.

[0108] According to 3GPP TS 23.554, the prerequisites for this situation are given below:

[0109] I. MSGin5G clients with MSGin5G UE (source UE (100A)) registered in the MSGin5G server (200); and / or

[0110] II. The non-3GPP messaging gateway (300B) knows the non-3GPP messaging client (100Bc) in the non-3GPP UE and provides a mapping to the MSGin5G service ID.

[0111] At 601, the source UE (100A) sends an MSGin5G message request to the MSGin5G server (200). The MSGin5G message request includes the MSGin5G service identifier (ID) of the source UE (100A), the MSGin5G service ID of the target UE (100B), and message ID information, delivery status, application ID, payload, and priority type information elements. At 602, the MSGin5G server (200) determines that the recipient is a non-3GPP UE (100Bc), and the MSGin5G client is authorized to send MSGin5G messages (100Bc) to the non-3GPP UE.

[0112] At 603, the MSGin5G server (200) forwards the MSGin5G message request to the non-3GPP message gateway (300B), as specified in 3GPP TS 23.554. At 604, the non-3GPP message gateway (300B) translates the MSGin5G message into a non-3GPP message requesting the delivery of a report and sends the non-3GPP message to the non-3GPP message client (target UE (100B)). At 605, if a status report is required, the non-3GPP message gateway (300B) sends the MSGin5G message delivery report to the MSGin5G server (200), and the MSGin5G server (200) forwards the MSGin5G message delivery report to the MSGin5G client (source UE (100A)).

[0113] In one embodiment, Massive Internet of Things (MIOT) is a key component of a 5G system. The applicability of the provided method extends the scope of MSgin5G services to messaging services for both traditional 3GPP and non-3GPP UEs.

[0114] The embodiments disclosed herein can be implemented using at least one hardware device and perform network management functions to control the elements.

[0115] The foregoing description of specific embodiments will so fully reveal the general nature of the embodiments herein that other embodiments can be readily modified and / or adapted to various applications by applying present knowledge, without departing from the general conception, and therefore such adaptations and modifications should and are intended to be understood within the meaning and scope of equivalents of the disclosed embodiments. It should be understood that the wording or terminology used herein is for descriptive purposes and not for limiting purposes. Therefore, although the embodiments herein have been described according to preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modifications within the scope of the embodiments described herein.

[0116] Although this disclosure has been described with reference to various embodiments, those skilled in the art may suggest various changes and modifications. This disclosure is intended to include such changes and modifications that fall within the scope of the appended claims.

Claims

1. A method performed by a fifth-generation messaging (MSGin5G) server in a wireless network, the method comprising: The system receives an MSGin5G message request from the source user equipment (UE) to transmit the MSGin5G message to the target UE in the wireless network. Based on the target UE's ID, the registration status of the target UE is queried in the registration store of the MSGin5G server. Registration of non-MSGin5G UEs to the MSGin5G server is performed by the message gateway on behalf of the non-MSGin5G UEs. If the target UE is a non-MSGin5G UE and the target UE is registered with the MSGin5G server through the message gateway, the MSGin5G message is sent to the message gateway.

2. The method of claim 1, further comprising: If the target UE is an MSGin5G UE, the MSGin5G message is sent to the target UE.

3. The method as described in claim 1, in, The MSGin5G message is sent from the message gateway to the target UE using a non-MSGin5G message transmission service mechanism available in the target UE.

4. The method as described in claim 1, in, The address translation and protocol translation of the MSGin5G message are performed by the message gateway.

5. The method as described in claim 1, in, The MSGin5G message request includes at least one of the following elements: the MSGin5G service ID of the source UE, the MSGin5G service ID of the target UE, message ID information, delivery status, application ID, payload, or priority type information.

6. The method as described in claim 1, in, The message gateway includes at least one of a conventional 3GPP message gateway or a non-3GPP message gateway.

7. The method of claim 1, further comprising: If the ID of the target UE is not registered in the registration repository, the target UE is identified as a non-MSGin5G UE.

8. An MSGin5G server in a wireless network, the MSGin5G server comprising: Memory; processor; as well as The MSGin5G controller, operably connected to the memory and processor, is configured as follows: The system receives an MSGin5G message request from the source user equipment (UE) to transmit the MSGin5G message to the target UE within the wireless network. Based on the target UE's ID, the registration status of the target UE is queried in the registration store of the MSGin5G server. Registration of non-MSGin5G UEs to the MSGin5G server is performed by the message gateway on behalf of the non-MSGin5G UEs. If the target UE is a non-MSGin5G UE and the target UE is registered with the MSGin5G server through the message gateway, the MSGin5G message is sent to the message gateway.

9. The MSGin5G server as described in claim 8, in, The MSGin5G controller is also configured to: If the target UE is an MSGin5G UE, the MSGin5G message is sent to the target UE.

10. The MSGin5G server as described in claim 8, in, The MSGin5G message is sent from the message gateway to the target UE using a non-MSGin5G message transmission service mechanism available in the target UE.

11. The MSGin5G server as described in claim 8, in, The address translation and protocol translation of the MSGin5G message are performed by the message gateway.

12. The MSGin5G server as described in claim 8, wherein, The MSGin5G message request includes at least one of the following elements: the MSGin5G service ID of the source UE, the MSGin5G service ID of the target UE, message ID information, delivery status, application ID, payload, or priority type information.

13. The MSGin5G server as described in claim 8, in, The message gateway includes at least one of a conventional 3GPP message gateway or a non-3GPP message gateway.

14. The MSGin5G server as described in claim 8, in, The MSGin5G controller is also configured to: If the ID of the target UE is not registered in the registration repository, the target UE is identified as a non-MSGin5G UE.

Images