Method for providing messaging service in 5G system, MSGIN5G server and non-MSGIN5G gateway

Abstract

The present disclosure provides a pre-5th generation (5G) or 5G communication system provided to support higher data transmission rates beyond 4th generation (4G) communication systems such as LTE (long term evolution). An embodiment herein provides a method for providing messaging services in a 5th generation system, a MSGin5G server, and a non-MSGin5G gateway. The provided method provides a TRF capable of supporting the MSGin5G server to determine a transmission service, and a GWSF capable of supporting the MSGin5G server to determine an appropriate gateway for the determined transmission service. The provided method also includes a TF for converting the MSGin5G message to a legacy 3GPP message format or a non-3GPP message format.

Description

[Technical Field]

[0001] The present disclosure relates to wireless networks, and more particularly to a method for providing messaging services in a 5G system, a MSGin5G server, and a non-MSGin5G gateway. [Background technology]

[0002] To meet the increasing demand for wireless data traffic since the commercialization of fourth-generation (4G) communication systems, efforts are underway to develop improved fifth-generation (5G) or pre-5G communication systems. For this reason, 5G or pre-5G communication systems are referred to as "Beyond 4G Network" or "Post-LTE System" communication systems.

[0003] To achieve high data rates, 5G communication systems are expected to be implemented in ultra-high frequency (mmWave) bands (e.g., 60 GHz bands). To reduce radio wave propagation loss and increase transmission distances, beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antenna technologies are being discussed for 5G communication systems.

[0004] In addition, to improve the system's network, technologies being developed for the 5G communication system include advanced small cells, cloud Radio Access Networks (cloud RANs), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, moving networks, cooperative communication, CoMP (Coordinated Multi-Point), and reception-end interference cancellation.

[0005] For 5G communication systems, advanced coding modulation (ACM) methods such as FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding) and advanced access technologies such as FBMC (Filter Bank Multi Carrier), NOMA (non-orthogonal multiple access), and SCMA (sparse code multiple access) are being developed.

[0006] Generally, 3GPP (registered trademark) (3rd generation partnership project) currently describes messages in 5th generation (MSGin5G) application services as messaging services in 5G systems. As specified in 3GPP TS 23.554, the application architecture for MSGin5G application services is expected to support various UE types based on the basic transmission services (e.g., MSGin5G transmission services, non-MSGin5G transmission services) supported by the user equipment (UE). UE types include MSGin5G UE, legacy 3GPP UE, and non-3GPP UE.

[0007] An MSGin5G UE supports an MSGin5G client and can transmit an MSGin5G message payload. A legacy 3GPP UE does not support MSGin5G and instead uses one of the 3GPP-defined message delivery mechanisms (e.g., short message service (SMS), non-IP data delivery (NIDD), broadcast, etc.). Also, a non-3GPP UE does not support an MSGin5G client but supports one of the non-3GPP message delivery mechanisms (e.g., rich communication services (RCS) and lightweight M2M (LwM2M)). Therefore, it is desirable to provide a useful alternative for transmitting messages / MSGin5G message payloads in a 5G system. Summary of the Invention [Problem to be solved by the invention]

[0008] The main objective of the embodiments of the present specification is to, upon receiving an MSGin5G message request from a source UE to transmit a message to a target UE in a wireless network, determine whether the target UE supports the MSGin5G transmission service using a target resolution function (TRF) of the MSGin5G server. In response to determining that the target UE supports the MSGin5G transmission service, the MSGin5G server transmits the message to the target UE. In response to determining that the target UE does not support the MSGin5G transmission service, the MSGin5G server selects a non-MSGin5G gateway in the wireless network using a gateway selection function (GWSF) of the MSGin5G server. The MSGin5G server then transmits the message to the non-MSGin5G gateway, where the non-MSGin5G gateway converts the MSGin5G message request according to the non-MSGin5G transmission service using a translation function (TF) of the non-MSGin5G gateway, and transmits the converted message to the target UE. As a result, even if the target UE does not support MSGin5G message payload / MSGin5G client, the source UE (i.e., MSGin5G UE) sends the message to the target UE (e.g., MSGin5G UE, legacy 3GPP UE, non-3GPP UE, etc.), and the target UE does not require any external hardware to communicate with the source UE.

[0009] Another object of the embodiments of the present specification is to determine whether the target UE is registered in an MSGin5G UE registration repository of the MSGin5G server. In response to determining that the target UE is registered in the MSGin5G UE registration repository of the MSGin5G server, the MSGin5G server detects that the target UE supports MSGin5G transmission services. In response to determining that the target UE is not registered in the MSGin5G UE registration repository of the MSGin5G server, the MSGin5G server detects that the target UE supports non-MSGin5G transmission services.

[0010] Another object of the embodiments herein is to detect whether the target UE is one of a legacy 3GPP UE and a non-3GPP UE based on a UE registration repository of a home subscriber MSGin5G server (HSS) and / or a unified data management (UDM) in a wireless network. [Means for solving the problem]

[0011] Accordingly, an embodiment of the present specification discloses a method for transmitting a 5th Generation message (MSGin5G) in a wireless network. The method includes a step of receiving, by an MSGin5G server, a MSGin5G message request from a source UE to transmit a message to a target UE in the wireless network. The method also includes, if the MSGin5G server receives the MSGin5G message request from the source UE, a step of determining whether the target UE supports the MSGin5G transmission service using the TRF of the MSGin5G server (based on the MSGin5G service identity of the target UE). The method also includes a step of transmitting a message to the target UE in response to determining that the target UE supports the MSGin5G transmission service. The method also includes a step of selecting a non-MSGin5G gateway in the wireless network using the GWSF of the MSGin5G server in response to determining that the target UE does not support the MSGin5G transmission service. The method also includes sending the message to a non-MSGin5G gateway, wherein the non-MSGin5G gateway converts the MSGin5G message request according to a non-MSGin5G transmission service using a TF of the non-MSGin5G gateway, and the non-MSGin5G gateway transmits the converted message to the target UE.

[0012] In one embodiment, the MSGin5G message request includes the source UE's MSGin5G service identity (ID), the target UE's MSGin5G service ID, message ID information, transfer status, application ID, payload, and priority type information elements.

[0013] In one embodiment, the non-MSG in 5G transmission services include legacy 3GPP transmission services and / or non-3GPP transmission services.

[0014] In one embodiment, the non-MSGin5G gateway includes a legacy 3GPP message gateway and / or a non-3GPP message gateway.

[0015] In one embodiment, a legacy 3GPP message gateway is used to deliver messages to a target UE using 3GPP transmission services, and a non-3GPP message gateway is used to deliver messages to a target UE using non-3GPP transmission services.

[0016] In one embodiment, the source UE is a MSGin5G UE, and the target UE is a MSGin5G UE and a non-MSGin5G UE, where the MSGin5G UE supports the MSGin5G transmission service, and the target UE supports the MSGin5G transmission service and / or the non-MSGin5G transmission service.

[0017] In one embodiment, the non-MSGin5G UE is a legacy 3GPP UE and / or a non-3GPP UE.

[0018] In one embodiment, when the MSGin5G server receives an MSGin5G message request from the source UE, determining whether the target UE supports the MSGin5G transmission service using the MSGin5G server's TRF (based on the target UE's MSGin5G service identity) includes the MSGin5G server determining whether the target UE is registered in the MSGin5G UE registration repository of the MSGin5G server. The method also includes detecting, in response to determining that the target UE is registered in the MSGin5G UE registration repository of the MSGin5G server, that the target UE supports the MSGin5G transmission service. The method also includes detecting, in response to determining that the target UE is not registered in the MSGin5G UE registration repository of the MSGin5G server, that the target UE supports a non-MSGin5G transmission service.

[0019] In one embodiment, detecting that the target UE supports legacy 3GPP transmission services includes the MSGin5G server detecting that the target UE is registered in an HSS and / or UDM UE registration repository in the wireless network.

[0020] In one embodiment, detecting that the target UE supports non-3GPP transmission services includes detecting, by the MSGin5G server, that the target UE is not registered in the MSGin5G UE registration repository and is not registered in an HSS and / or UDM registration repository in the wireless network.

[0021] In one embodiment, selecting a non-MSGin5G gateway in the wireless network using the GWSF of the MSGin5G server includes selecting, by the MSGin5G server, one of a legacy 3GPP message gateway and a non-3GPP message gateway based on a mapping table available in the GWSF. The method also includes authenticating, by the MSGin5G server, the source UE. The method also includes transmitting, by the MSGin5G server, the message to the selected one of the legacy 3GPP message gateway and the non-3GPP message gateway.

[0022] In one embodiment, the step of converting the MSGin5G message request according to the non-MSGin5G transmission service using the TF includes the step of the MSGin5G server detecting that a legacy 3GPP message gateway is selected. The method also includes the step of the legacy 3GPP message gateway determining a message delivery mechanism for sending the message to the target UE based on the capabilities of the target UE, the communication state of the target UE, and the service configuration of the target UE, where the message delivery mechanism is one of SMS and NIDD. The method also includes the step of the legacy 3GPP message gateway registering and deregistering with the MSGin5G server for the non-MSGin5G UE. The method also includes the step of the legacy 3GPP message gateway segmenting and reassembling messages for the non-MSGin5G UE. The method also includes the step of the legacy 3GPP message gateway converting the address of the target UE. The method also includes the legacy 3GPP message gateway converting a protocol and non-message payload information of the message based on the determined message delivery mechanism, and the method also includes the legacy 3GPP message gateway transmitting the message to the target UE.

[0023] In one embodiment, the legacy 3GPP message gateway receives a delivery report from the target UE, converts the received delivery report into a MSGin5G message delivery report, and sends the MSGin5G message delivery report to the MSGin5G server.

[0024] In one embodiment, the step of converting the MSGin5G message request according to the non-MSGin5G transmission service using the TF includes the MSGin5G server detecting that a non-3GPP message gateway is selected. The method also includes the non-3GPP message gateway determining a message delivery mechanism for sending the message to the target UE based on the target UE's capabilities, the target UE's communication state, and the target UE's service configuration, where the message delivery mechanism is one of RCS and LwM2M. The method also includes the non-3GPP message gateway converting the message into a non-3GPP message based on the determined message delivery mechanism. The method also includes the non-3GPP message gateway sending the message to the target UE.

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

[0026] Accordingly, embodiments of the present disclosure disclose an MSGin5G server for transmitting MSGin5G messages in a wireless network. The MSGin5G server includes an MSGin5G controller coupled to a processor and a memory. The MSGin5G controller is configured to receive an MSGin5G message request from a source UE to transmit a message to a target UE in the wireless network. Upon receiving the MSGin5G message request from the source UE, the MSGin5G controller is configured to determine whether the target UE supports the MSGin5G transmission service using the TRF of the MSGin5G server (based on the MSGin5G service identity of the target UE). In response to determining that the target UE supports the MSGin5G transmission service, the MSGin5G controller is configured to transmit the message to the target UE. In response to determining that the target UE does not support the MSGin5G transmission service, the MSGin5G controller is configured to select a non-MSGin5G gateway in the wireless network using the GWSF of the MSGin5G server. The MSGin5G control unit is also configured to send messages to non-MSGin5G gateways.

[0027] Accordingly, embodiments of the present specification disclose a non-MSGin5G gateway for transmitting an MSGin5G message in a wireless network. The non-MSGin5G gateway includes an MSGin5G controller coupled to a processor and a memory. The MSGin5G controller is configured to convert an MSGin5G message request according to a non-MSGin5G transmission service using a TF of the non-MSGin5G gateway, and the non-MSGin5G gateway transmits the converted message to a target UE.

[0028] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following description, while indicating preferred embodiments and numerous specific details, is given by way of illustration and not by way of limitation. Numerous changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.

[0029] Before embarking on the detailed description below, it may be advantageous to define certain words and phrases used throughout this patent document. The words "include" and "comprise," as well as derivatives thereof, mean inclusion without limitation; the word "or" is inclusive and / or; the phrases "associated with" and "associated therewith," as well as derivatives thereof, mean "to include," "be included within," "interconnect with," "contain," "be contained within," "connect to or with," "couple to or with," "be communicable with," "cooperate with," "interleave," "juxtapose with," "be proximate to," "be bound to or with," "have," "have a The term "controller" may mean any device, system, or portion thereof that controls at least one operation. Such a device may be embodied in hardware, firmware, or software, or some combination of at least two of these. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.

[0030] Furthermore, the various functions described below may be embodied or supported by one or more computer programs, each of which is formed from computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, associated data, or portions thereof, adapted for implementation in suitable 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 that can be accessed by a computer, including read-only memory (ROM), random access memory (RAM), hard disk drives, compact discs (CDs), digital video discs (DVDs), or any other type of memory. "Non-transitory" computer-readable media excludes wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes media on which data can be permanently stored and media on which data can be stored and later overwritten, such as rewritable optical disks or erasable memory devices.

[0031] Definitions for other specific words and phrases are provided throughout this patent document, and one of ordinary skill in the art should understand that in most cases, if not all, such definitions apply to previous and subsequent uses of such defined words and phrases. [Effects of the Invention]

[0032] According to the present disclosure, there is an improvement to a MSGin5G server that determines transmission services supported by a target user equipment (UE) and determines an appropriate gateway for the determined transmission services.

[0033] The present disclosure is illustrated in the accompanying drawings, in which like reference characters designate corresponding parts throughout the various drawings. Examples of the present disclosure will be better understood from the following description taken in conjunction with the drawings, in which: [Brief explanation of the drawings]

[0034] [Figure 1] The embodiment as disclosed herein illustrates the architecture of the MSGin5G application service as specified in 3GPP TS 23.554 v0.3.0. [Figure 2a] 1 illustrates a block diagram of a MSGin5G server for delivering MSGin5G messages in a wireless network according to one embodiment as disclosed herein. [Figure 2b] 1 illustrates a block diagram of a non-MSGin5G gateway for conveying MSGin5G messages in a wireless network according to one embodiment as disclosed herein. [Figure 3] 1 is a flow diagram illustrating a method for communicating a MSGin5G message in a wireless network according to one embodiment as disclosed herein. [Figure 4]1 is a sequence diagram illustrating various operations for transmitting an MSGin5G message from a source UE to a target UE in a wireless network in which both the source UE and the target UE support the MSGin5G transmission service, according to one embodiment as disclosed herein. [Figure 5] 1 is a sequence diagram illustrating various operations for transmitting an MSGin5G message from a source UE to a target UE in a wireless network in which the source UE supports the MSGin5G transmission service and the target UE operates as a legacy 3GPP UE supporting a non-MSGin5G transmission service, according to one embodiment as disclosed herein. [Figure 6] 1 is a sequence diagram illustrating various operations for transmitting an MSGin5G message from a source UE to a target UE in a wireless network in which the source UE supports the MSGin5G transmission service and the target UE operates as a non-3GPP UE supporting the non-MSGin5G transmission service, according to one embodiment as disclosed herein. DETAILED DESCRIPTION OF THE INVENTION

[0035] 1-6 discussed below, and the various embodiments used in this patent document to explain the principles of the present disclosure, are for illustrative purposes only and should not be construed as limiting the scope of the present disclosure. Those of ordinary skill in the art will understand that the principles of the present disclosure may be embodied in any suitably arranged system or device.

[0036] The embodiments of the present specification and their various features and advantageous details will be more fully described with reference to the non-limiting embodiments illustrated in the accompanying drawings and described in detail in the following description. Descriptions of well-known components and processing techniques are omitted to avoid unnecessarily obscuring the embodiments of the present specification. 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. As used herein, the term "or" means non-exclusive unless otherwise indicated. The examples used herein are merely intended to facilitate understanding of the manner in which the embodiments of the present specification can be implemented and to enable those of ordinary skill in the art to implement the embodiments of the present specification. Therefore, the examples should not be construed as limiting the scope of the embodiments of the present specification.

[0037] As is conventional in the art, the embodiments may be described and illustrated in terms of blocks performing described functions. Such blocks, which may be referred to herein as processors, units, modules, hardware components, etc., may be physically embodied by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, manual electronic components, active electronic components, optical components, hardwired circuits, etc., and may optionally be driven by firmware. For example, circuits may be embodied on one or more semiconductor chips or a substrate support such as a printed circuit board. The circuits comprising a block may be embodied by dedicated hardware or processors (e.g., one or more programmed microprocessors and associated circuitry), or a combination of dedicated hardware performing some of the block's functions and processors performing other functions of the block. Each block of the embodiments may be physically separated into two or more interacting and separate blocks without departing from the scope of the present disclosure. Similarly, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the present disclosure.

[0038] Accordingly, an embodiment of the present specification discloses a method for transmitting a 5th Generation message (MSGin5G) in a wireless network. The method includes a step of receiving, by an MSGin5G server, a MSGin5G message request from a source UE to transmit a message to a target UE in the wireless network. The method also includes, if the MSGin5G server receives the MSGin5G message request from the source UE, a step of determining whether the target UE supports the MSGin5G transmission service using the TRF of the MSGin5G server (based on the MSGin5G service identity of the target UE). The method also includes a step of transmitting a message to the target UE in response to determining that the target UE supports the MSGin5G transmission service. The method also includes a step of selecting a non-MSGin5G gateway in the wireless network using the GWSF of the MSGin5G server in response to determining that the target UE does not support the MSGin5G transmission service. The method also includes sending the message to a non-MSGin5G gateway, wherein the non-MSGin5G gateway converts the MSGin5G message request according to a non-MSGin5G transmission service using a TF of the non-MSGin5G gateway, and the non-MSGin5G gateway transmits the converted message to the target UE.

[0039] Accordingly, embodiments of the present disclosure disclose an MSGin5G server for transmitting MSGin5G messages in a wireless network. The MSGin5G server includes an MSGin5G controller coupled to a processor and a memory. The MSGin5G controller is configured to receive an MSGin5G message request from a source UE to transmit a message to a target UE in the wireless network. Upon receiving the MSGin5G message request from the source UE, the MSGin5G controller is configured to determine whether the target UE supports the MSGin5G transmission service using the TRF of the MSGin5G server (based on the MSGin5G service identity of the target UE). In response to determining that the target UE supports the MSGin5G transmission service, the MSGin5G controller is configured to transmit the message to the target UE. In response to determining that the target UE does not support the MSGin5G transmission service, the MSGin5G controller is configured to select a non-MSGin5G gateway in the wireless network using the GWSF of the MSGin5G server. The MSGin5G control unit is also configured to send messages to non-MSGin5G gateways.

[0040] Accordingly, embodiments of the present specification disclose a non-MSGin5G gateway for transmitting an MSGin5G message in a wireless network. The non-MSGin5G gateway includes an MSGin5G controller coupled to a processor and a memory. The MSGin5G controller is configured to convert an MSGin5G message request according to a non-MSGin5G transmission service using a TF of the non-MSGin5G gateway, and the non-MSGin5G gateway transmits the converted message to a target UE.

[0041] A legacy 3GPP UE does not support MSGin5G and instead uses one of the 3GPP-defined messaging mechanisms (e.g., SMS, NIDD, broadcast, etc.), and a non-3GPP UE does not support the MSGin5G client but supports one of the non-3GPP messaging mechanisms (e.g., RCS and LwM2M, etc.).

[0042] The method provided in the present disclosure allows an MSGin5G server to determine whether the target UE supports the MSGin5G transmission service using the MSGin5G server's TRF (based on the target UE's MSGin5G service identity) upon receiving an MSGin5G message request from a source UE to transmit a message (i.e., an MSGin5G message) to a target UE over a wireless network. In response to determining that the target UE supports the MSGin5G transmission service, the MSGin5G server transmits the message to the target UE. In response to determining that the target UE does not support the MSGin5G transmission service, the MSGin5G server selects a non-MSGin5G gateway over the wireless network using the MSGin5G server's GWSF. The MSGin5G server also sends the message to the non-MSGin5G gateway, where the non-MSGin5G gateway converts the MSGin5G message request according to the non-MSGin5G sending service using the non-MSGin5G gateway's TF, and the non-MSGin5G gateway sends the converted 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) can send the message to the target UE (e.g., MSGin5G UE, legacy 3GPP UE, non-3GPP UE, etc.), and the target UE does not require any external hardware to communicate with the source UE.

[0043] The method provided in the present disclosure enables an MSGin5G server to determine whether the MSGin5G service identity of the target UE is registered in the MSGin5G server's MSGin5G UE registration repository. In response to determining that the target UE is registered in the MSGin5G server's MSGin5G UE registration repository, the MSGin5G server detects that the target UE supports MSGin5G transmission services. In response to determining that the target UE is not registered in the MSGin5G server's MSGin5G UE registration repository, the MSGin5G server detects that the target UE supports non-MSGin5G transmission services.

[0044] The method provided in the present disclosure allows the MSGin5G server to detect that the target UE is one of a legacy 3GPP UE and a non-3GPP UE based on a UE registration repository of an HSS and / or UDM in a wireless network.

[0045] Referring now to the drawings, and in particular to FIGS. 1-6, wherein like reference numerals indicate corresponding features consistently throughout the views, there are illustrated preferred embodiments.

[0046] FIG. 1 illustrates the architecture of the MSGin5G application service 1000 as specified in 3GPP TS 23.554, according to an embodiment as disclosed herein.

[0047] 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 legacy 3GPP UE 100Bb, or non-3GPP UE 100Bc), a non-MSGin5G gateway 300 (legacy 3GPP message gateway 300A, or non-3GPP message gateway 300B), and a 3GPP core network 400.

[0048] In one embodiment, the MSGin5G server 200 provides server-side functionality to support MSGin5G clients (e.g., MSGin5G UE-1 100A, MSGin5G UE-2 100Ba, etc.) sending and receiving messages to / from the application server 200B and / or other MSGin5G service endpoints on other UEs (e.g., legacy 3GPP UE 100Bb, non-3GPP UE 100Bc, etc.) via the MSGin5G service. To resolve the message delivery mechanism for the MSGin5G service endpoint based on the terminating MSGSin5G service ID, the MSGin5G server 200 determines whether the message should be delivered to the target UE 100B, the application server 200B, or the non-MSGin5G gateway 300 for final delivery.

[0049] In one embodiment, the MSGin5G server 200 includes a TRF 241 and a GWSF 242, which are not shown in FIG. 1. The TRF 241 provides functionality to help the MSGin5G server 200 determine the transmission services supported by the target UE 100B. Upon receiving the MSGin5G message request, the TRF 241 checks the MSGin5G UE registration repository (a database created when each MSGin5G UE (e.g., MSGin5G UE-1 100A, MSGin5G UE-2 100Ba, etc.) registers with the MSGin5G server 200) for the target endpoint identifier (i.e., the target UE 100B). If the target endpoint identifier is found in the repository, the transmission services supported by the target UE 100B are identified as MSGin5G UE, and the MSGin5G message payload can be understood. If the target endpoint identifier is not found in the store, the MSGin5G server 200 checks the HSS / UDM store for the target endpoint identifier. If the target endpoint identifier is found in the HSS / UDM store, the transmission service supported by the target UE 100B is determined to be a non-MSGin5G transmission service and requires the support of the non-MSGin5G gateway 300 to understand the MSGin5G message payload.

[0050] The GWSF 242 also provides functionality to support the MSGin5G server 200 in determining an appropriate non-MSGin5G gateway 300 (legacy 3GPP message gateway 300A or non-3GPP message gateway 300B) for the transmission service supported by the target UE 100B. Upon receiving the transmission service determined by the TRF 241 and supported by the target UE 100B, the GWSF 242 selects the corresponding non-MSGin5G gateway 300 (legacy 3GPP message gateway 300A or non-3GPP message gateway 300B) based on a mapping table available in the GWSF 242.

[0051] In one embodiment, the non-MSGin5G gateway 300 (legacy 3GPP message gateway 300A and / or non-3GPP message gateway 300B) includes a TF 341, not shown in Figure 1. The TF 341 performs address conversion of the target UE 100B as understood in the destination domain, and protocol and payload conversion according to the transmission services supported by the target UE 100B.

[0052] In one embodiment, the non-MSGin5G gateway 300 of the MSGin5G application architecture provides the functionality to deliver MSGin5G messages to non-MSGin5G UEs (i.e., legacy 3GPP UE 100Bb and non-3GPP UE 100Bc). The non-MSGin5G gateway 300 serves to interconnect two different message delivery mechanisms and ensures message integrity between the different message delivery mechanisms. A message delivery mechanism includes a specific protocol, procedure, and rule set.

[0053] In one embodiment, the non-MSGin5G gateway 300 enables smooth delivery of MSGin5G messages between different message delivery mechanisms with integrity. The non-MSGin5G gateway 300 can communicate with the MSGin5G server 200 to send and receive MSGin5G messages using a MSGin5G client function or similar functionality. The non-MSGin5G gateway 300 also delivers MSGin5G message payloads to non-MSGin5G UEs (i.e., legacy 3GPP UEs 100Bb and non-3GPP UEs 100Bc) using a specific message delivery mechanism available to the non-MSGin5G UE, and vice versa. The non-MSGin5G gateway 300 also translates the addresses of message senders and recipients between the two linked message delivery mechanisms and maintains a mapping of address pairs used for response message delivery. The non-MSGin5G gateway 300 also registers and deregisters with the MSGin5G server 200 on behalf of the non-MSGin5G UE. The non-MSGin5G gateway 300 also acts as a service endpoint that performs message segmentation and reassembly for the non-MSGin5G UE when necessary. The non-MSGin5G gateway 300 also converts protocols and non-message payload information according to the services supported by the target UE 100B.

[0054] In one embodiment, legacy 3GPP message gateway 300A is used to deliver the MSGin5G message to legacy 3GPP UE 100Bb using a 3GPP-supported messaging mechanism, and non-3GPP message gateway 300B is used to deliver the MSGin5G message to non-3GPP UE 100Bc using a (non-3GPP) supported messaging mechanism.

[0055] In one embodiment, TRF 241 and GWSF 242 reside in 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 internal to MSGin5G Server 200.

[0056] In one embodiment, all logical functions (TRF241, GWSF242, and TF341) can be co-located with other entities of the MSGin5G application service 1000; in such cases, the associated interface functions are within the entity hosting the logical function.

[0057] FIG. 2a shows a block diagram of a MSGin5G server 200 for delivering MSGin5G messages in a wireless network according to an embodiment as disclosed herein.

[0058] In one embodiment, the MSGin5G server 200 includes a memory 210, a processor 220, a communicator 230, and an MSGin5G control unit 240.

[0059] The memory 210 stores the MSGin5G service identity (ID) of the source UE 100A, the MSGin5G service ID of the target UE 100B, a message ID information element, message ID information, a transmission status, an application ID, a payload, a priority type information element, and an MSGin5G UE registration repository. The memory 210 also stores instructions executed by the processor 220. The memory 210 may include a non-volatile storage element. Examples of such non-volatile storage elements include a magnetic hard disk, an optical disk, a floppy disk, flash memory, or an electrically programmable memory (EPROM) or an electrically erasable and programmable memory (EEPROM). The memory 210 may also be considered a non-transitory storage medium in some examples. The term "non-transitory" may indicate that the storage medium is not embodied as a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted as meaning that the memory 210 does not move. In some examples, the memory 210 may be configured to store a larger amount of information. In certain examples, the non-transitory storage medium may store data that may change over time (e.g., in random access memory (RAM) or cache). Memory 210 may be an internal storage unit or may be an external storage unit of MSGin5G server 200, a cloud storage, or other type of external storage.

[0060] The processor 220 communicates with the memory 210, the communicator 230, and the MSGin5G control unit 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, and may be a general-purpose processor such as a central processing unit (CPU) or an application processor (AP), or a dedicated processor for artificial intelligence (AI), such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or a neural processing unit (NPU).

[0061] Communicator 230 contains standard-specific electronic circuitry that enables wired and wireless communication. Communicator 230 is configured to communicate internally between external devices and internal hardware components over one or more networks.

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

[0063] 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 the source UE 100A to transmit a message to the target UE 100B over the wireless network. The MSGin5G controller 240 is also configured to determine, upon receiving the MSGin5G message request from the source UE 100A, whether the target UE 100B supports the MSGin5G transmission service using the TRF 241 of the MSGin5G server 200. The MSGin5G controller 240 is also configured to transmit a message to the target UE 100B in response to determining that the target UE 100B supports the MSGin5G transmission service. The MSGin5G control unit 240 is also configured to, in response to determining that the target UE 100B does not support the MSGin5G transmission service, select a non-MSGin5G gateway 300 in the wireless network using the GWSF 242 of the MSGin5G server 200. The MSGin5G control unit 240 is also configured to transmit the message to the non-MSGin5G gateway 300.

[0064] The MSGin5G control unit 240 is also configured to determine whether the target UE 100B is registered in the MSGin5G UE registration repository of the MSGin5G server 200. The MSGin5G control unit 240 is also configured to detect that the target UE 100B supports the MSGin5G transmission service in response to determining that the target UE 100B is registered in the MSGin5G UE registration repository of the MSGin5G server 200. The MSGin5G control unit 240 is also configured to detect that the target UE 100B supports a non-MSGin5G transmission service in response to determining that the target UE 100B is not registered in the MSGin5G UE registration repository of the MSGin5G server 200.

[0065] The MSGin5G control unit 240 is also configured to detect that the target UE 100B is registered with an HSS and / or UDM UE registration repository in the wireless network. The MSGin5G control unit 240 is also configured to select one of the legacy 3GPP message gateway 300A and the non-3GPP message gateway 300B. The MSGin5G control unit 240 is also configured to authenticate the source UE 100A. The MSGin5G control unit 240 is also configured to transmit a message to one of the legacy 3GPP message gateway 300A and the non-3GPP message gateway 300B upon selection.

[0066] While FIG. 2a illustrates various hardware components of the MSGin5G server 200, it should be understood that other embodiments are not limited in this respect. In other embodiments, the MSGin5G server 200 may include fewer or more components. Additionally, the labels and names of the components are used for illustrative purposes only and do not limit the scope of the present disclosure. One or more components may be combined together to perform the same or substantially similar functions to transmit MSGin5G over a wireless network.

[0067] FIG. 2b illustrates a block diagram of a non-MSGin5G gateway 300 for conveying MSGin5G messages in a wireless network, according to one embodiment as disclosed herein.

[0068] In one embodiment, the non-MSGin5G gateway 300 includes a memory 310 , a processor 320 , a communicator 330 , and a MSGin5G control unit 340 .

[0069] The memory 310 stores the MSGin5G service identity (ID) of the source UE 100A, the MSGin5G service ID of the target UE 100B, message ID information, transmission status, application ID, payload, priority type information elements, and a UE registration repository for HSS and UDM. The memory 310 also stores instructions executed by the processor 320. The memory 310 may include a non-volatile storage element. Examples of such non-volatile storage elements include a magnetic hard disk, an optical disk, a floppy disk, flash memory, or an electrically programmable memory (EPROM) or an electrically erasable and programmable memory (EEPROM). The memory 310 may also be considered a non-transitory storage medium in some examples. The term "non-transitory" may indicate that the storage medium is not embodied as a carrier wave or propagated signal. However, the term "non-transitory" should not be interpreted as meaning that the memory 310 is not mobile. In some examples, the memory 310 may be configured to store a larger amount of information. In certain examples, the non-transitory storage medium may store data that may change over time (e.g., in random access memory (RAM) or cache). Memory 310 may be an internal storage unit, or memory 310 may be an external storage unit of non-MSGin5G gateway 300, a cloud storage, or other type of external storage.

[0070] The processor 320 communicates with the memory 310, the communicator 330, and the MSGin5G control unit 340. The processor 320 is configured to execute instructions stored in the memory 310 and perform various processes. The processor 320 may include one or more processors, and may be a general-purpose processor such as a CPU, AP, etc., or a dedicated AI processor such as a GPU, VPU, and / or NPU.

[0071] Communicator 330 contains standard-specific electronic circuitry that enables wired and wireless communication. Communicator 330 is configured to communicate internally between external devices and internal hardware components over one or more networks.

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

[0073] In one embodiment, the MSGin5G control unit 240 includes a TF 341. The MSGin5G control unit 340 is configured to convert the MSGin5G message request according to a non-MSGin5G transmission service using the TF 341 of the non-MSGin5G gateway 300, and the non-MSGin5G gateway 300 transmits the converted message to the target UE 100B.

[0074] The MSGin5G control unit 340 is also configured to determine a message delivery mechanism for transmitting a message to the target UE 100B based on the capabilities of the target UE 100B, the communication state of the target UE 100B, and the service configuration of the target UE 100B, where the message delivery mechanism is one of SMS and NIDD. The MSGin5G control unit 340 is also configured to register and deregister non-MSGin5G UEs with the MSGin5G server 200. The MSGin5G control unit 340 is also configured to segment messages and reassemble messages for non-MSGin5G UEs. The MSGin5G control unit 340 is also configured to convert the address of the target UE 100B. The MSGin5G control unit 340 is also configured to convert protocol and non-message payload information of messages based on the determined message delivery mechanism. The MSGin5G control unit 340 is also configured to transmit messages to the target UE 100B. In addition, the MSGin5G control unit 340 is configured to transmit a MSGin5G message delivery report to the MSGin5G server 200.

[0075] The MSGin5G control unit 340 is also configured to determine a message delivery mechanism for transmitting a message to the target UE 100B based on the capability of the target UE 100B, the communication state of the target UE 100B, and the service configuration of the target UE 100B, where the message delivery mechanism is one of RCS and LwM2M. The MSGin5G control unit 340 is also configured to convert the message into a non-3GPP message based on the determined message delivery mechanism. The MSGin5G control unit 340 is also configured to transmit the message to the target UE 100B. The MSGin5G control unit 340 is also configured to transmit an MSGin5G message delivery report to the MSGin5G server 200.

[0076] While FIG. 2b illustrates various hardware components of the non-MSGin5G gateway 300, it should be understood that other embodiments are not limited in this respect. In other embodiments, the non-MSGin5G gateway 300 may include fewer or more components. Additionally, the labels and names of the components are for illustrative purposes only and do not limit the scope of the present disclosure. One or more components may be combined together to perform the same or substantially similar functions to transmit MSGin5G signals over a wireless network.

[0077] 3 is a flow diagram S300 illustrating a method for transmitting MSGin5G messages in a wireless network according to an embodiment as disclosed herein. Operations S302-S312 are performed by the MSGin5G server 200 and the non-MSGin5G gateway 300.

[0078] At S302, the method includes receiving an MSGin5G message request from the source UE 100A to deliver a message to the target UE 100B over a wireless network. At S304, the method includes determining whether the target UE 100B supports the MSGin5G transmission service using the TRF of the MSGin5G server 200 (based on the MSGin5G service identity of the target UE). At S306, the method includes, if receiving the MSGin5G message request from the source UE 100A, determining an action (e.g., S308, S310) based on whether the target UE 100B supports the MSGin5G transmission service using the TRF 241 of the MSGin5G server 200. At S308, the method includes transmitting a message to the target UE 100B in response to determining that the target UE 100B supports the MSGin5G transmission service.

[0079] At S310, in response to determining that the target UE 100B does not support the MSGin5G transmission service, the method includes selecting a non-MSGin5G gateway 300 in the wireless network using the GWSF 242 of the MSGin5G server 200. At S312, the method includes sending a message to the non-MSGin5G gateway 300, where the non-MSGin5G gateway 300 converts the MSGin5G message request according to the non-MSGin5G transmission service using the TF 341 of the non-MSGin5G gateway 300, and the non-MSGin5G gateway 300 transmits the converted message to the target UE 100B.

[0080] The various operations, acts, blocks, steps, etc. of flow diagram S300 may be performed in the order presented, in a different order, or simultaneously. Also, in some embodiments, some of the operations, acts, blocks, steps, etc. may be omitted, added, modified, skipped, etc. without departing from the scope of the present disclosure.

[0081] FIG. 4 is a sequence diagram illustrating various operations for transmitting an MSGin5G message from a source UE 100A to a target UE 100B in a wireless network in which both the source UE 100A and the target UE 100B support the MSGin5G transmission service, according to an embodiment disclosed in this specification.

[0082] In such a scenario, a prerequisite is that the MSGin5G client-2 of MSGin5G UE-2 100Ba / target UE 100B is registered with the MSGin5G server 200. At 401, the MSGin5G server 200 receives a valid MSGin5G message from the source UE 100A (i.e., MSGin5G UE-1). At 402, the TRF 241 checks the registry repository of the MSGin5G server 200 to find the target endpoint identifier as specified in the received MSGin5G message. The TRF 241 finds registry information for the target endpoint identifier and decides 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 the MSGin5G UE-2 100Ba (i.e., the MSGin5G client-2 100Baa / application client 100Bab). At 404, the MSGin5G UE-2 100Ba transmits the contents of the MSGin5G message to the target application client / MSGin5G UE-2 100Ba / target UE 100B.

[0083] FIG. 5 is a sequence diagram illustrating various operations for transmitting an MSGin5G message from a source UE 100A to a target UE 100B in a wireless network in which the source UE 100A supports an MSGin5G transmission service, according to one embodiment as disclosed in this specification, and the target UE 100B operates as a legacy 3GPP UE 100Bb supporting a non-MSGin5G transmission service.

[0084] According to 3GPP TS 23.554, for such a scenario the prerequisites are as follows:

[0085] i. The MSGin5G client in the MSGin5G UE (source UE 100A) is registered with the MSGin5G server 200;

[0086] ii. the legacy 3GPP message gateway 300A knows the MSGin5G service ID of the legacy 3GPP UE 100Bb and / or maintains a mapping to the ID used in the legacy network;

[0087] iii. The MSGin5G Server 200 can determine whether the target UE 100B is a legacy 3GPP UE 100Bb and what messaging mechanisms are available.

[0088] At 501, the source UE 100A sends an MSGin5G message request to the MSGin5G server 200. The MSGin5G message request includes the source UE 100A's MSGin5G service identity (ID), the target UE 100B's MSGin5G service ID, message ID information, transmission state, 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 that the MSGin5G client (source UE 100A) is authorized to send MSGin5G messages to the legacy 3GPP UE 100Bb. At 503, the MSGin5G server 200 forwards the MSGin5G message request to the legacy 3GPP message gateway 300A.

[0089] At 504, the legacy 3GPP message gateway 300A determines which legacy 3GPP message delivery mechanism (e.g., SMS, NIDD, etc.) to use based on the capabilities of the target UE 100B / legacy 3GPP UE 100Bb, the communication state of the target UE 100B / legacy 3GPP UE 100Bb, the service configuration of the target UE 100B / legacy 3GPP UE 100Bb, etc. If selected, the legacy 3GPP message gateway 300A maps the MSGin5G service ID to a corresponding identifier. For example (not an exhaustive list):

[0090] i. if the legacy 3GPP message gateway 300A selects device triggering, the legacy 3GPP message gateway 300A maps the service ID to an MSISDN and an application port ID;

[0091] ii. if the legacy 3GPP message gateway 300A selects the NIDD transport mechanism, does the legacy 3GPP message gateway 300A map the service ID to an external identifier or MSISDN;

[0092] iii. If the legacy 3GPP message gateway 300A selects the SMS transport mechanism, the legacy 3GPP message gateway 300A maps the service ID to the MSISDN.

[0093] At 505-513, the legacy 3GPP message gateway 300A sends the payload of the MSGin5G message to the legacy 3GPP UE 100Bb, for example (not an exhaustive list):

[0094] i. For device triggering 505, the legacy 3GPP message gateway 300A maps the payload of the MSGin5G message into one or more device triggering requests (see 3GPP TS 23.682, 3GPP TS 29.122, and 3GPP TS 29.522).

[0095] ii. In the case of the NIDD transport mechanism 506, the legacy 3GPP message gateway 300A maps the payload of the MSGin5G message into one or more NIDD submit request messages (see 3GPP TS 23.682, 3GPP TS 29.122, and 3GPP TS 29.522), or alternatively, if tunnel parameters are provided in the legacy 3GPP message gateway (see 3GPP TS 23.401, 3GPP TS 23.501, and 3GPP TS 23.502); and / or

[0096] iii. In the case of SMS transport mechanism 507, legacy 3GPP message gateway 300A sends an SMS to legacy 3GPP UE 100Bb according to the procedures of 3GPP TS 23.204 or 3GPP TS 23.502.

[0097] At 508-509, if the required transmission status is included in the MSGin5G message request, the legacy 3GPP message gateway 300A sends a MSGin5G message transmission report to the MSGin5G server 200, which sends the transmission report to the MSGin5G client (source UE 100A) as specified in 3GPP TS 23.554.

[0098] FIG. 6 is a sequence diagram illustrating various operations for transmitting an MSGin5G message from a source UE 100A to a target UE 100B in a wireless network in which the source UE 100A supports an MSGin5G transmission service, according to one embodiment as disclosed in this specification, and the target UE 100B operates as a non-3GPP UE 100Bc supporting a non-MSGin5G transmission service.

[0099] According to 3GPP TS 23.554, for such a scenario the prerequisites are as follows:

[0100] i. Whether the MSGin5G client in the MSGin5G UE (source UE 100A) is / is registered with the MSGin5G server 200;

[0101] ii. The on-3GPP message gateway 300B recognizes the non-3GPP message client of the non-3GPP UE 100Bc and provides a mapping to the MSGin5G service ID.

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

[0103] 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 converts the MSGin5G message with the requested delivery report into a non-3GPP message and sends the non-3GPP message to the non-3GPP message client (target UE 100B). At 605, if a delivery status report is required, the non-3GPP message gateway 300B sends the MSGin5G message delivery report to the MSGin5G server 200, which forwards the MSGin5G message delivery report to the MSGin5G client (source UE 100A).

[0104] In one embodiment, MIoT (massive Internet of Things) is one of the main segments of the 5G system. Message services, including legacy 3GPP and non-3GPP UEs, extend the scope of MIoT 5G services due to the applicability of the provided methods.

[0105] The embodiments disclosed herein may be implemented using at least one hardware device to perform network management functions for controlling elements.

[0106] The above description of specific embodiments fully expresses the general characteristics of the embodiments herein; other embodiments, by applying current knowledge, can easily modify and / or adapt such specific embodiments for various applications without departing from the general concept; therefore, such adaptations and modifications must, and are intended to, be understood within the meaning and range of equivalents of the disclosed embodiments. It should be understood that the phraseology or terminology used herein is for purposes of description and not limitation. Thus, while the embodiments herein have been described in terms of preferred embodiments, those of ordinary skill in the art will recognize that the embodiments herein can be modified and implemented within the scope of the embodiments as described herein.

[0107] While the present disclosure has been described in various embodiments, various changes and modifications may be suggested to those of ordinary skill in the art, and the present disclosure is intended to include such changes and modifications within the scope of the appended claims. [Explanation of symbols]

[0108] 100A MSGin5G UE-1, Source UE 100Ba MSGin5G UE-2 100Baa MSGin5G Client-2 100Bab Application Client 100Bb Legacy 3GPP UE 100Bc Non-3GPP UE 200 MSGin5G Server 200A SEAL Server 200B Application Server 210 Memory 220 processors 230 Communicator 240 MSGin5G control unit 241 TRF 242 GWSF 300 Non-MSGin5G Gateway 300A Legacy 3GPP Message Gateway 300B Non-3GPP Message Gateway 310 Memory 320 processor 330 Communicator 340 MSGin5G control unit 341 TRF 400 3GPP Core Network 1000 MSGin5G Application Services

Claims

1. 1. A method performed by a fifth generation message (MSG in 5G) server in a wireless network, comprising: receiving a MSG in 5G message request from a source UE to transmit a message to a target UE in the wireless network; Checking whether the target UE is registered through a registration repository of an MSGin5G server based on the MSGin5G service ID of the target UE, wherein registration for a non-MSGin5G UE is performed by a message gateway on behalf of the non-MSGin5G UE; If the target UE is a non-MSGin5G UE and the target UE is registered with the MSGin5G server by the message gateway, sending the message to the message gateway.

2. The method of claim 1 , further comprising: if the target UE is a MSGin5GUE, transmitting the message to the target UE.

3. The method of claim 1 , wherein the message is sent from the message gateway to the target UE using a non-MSG in 5G messaging service mechanism available at the UE.

4. The method of claim 1 , wherein address translation and protocol translation of the message is performed by the message gateway.

5. The method of claim 1, wherein the MSGin5G message request includes at least one of a source UE MSGin5G service ID, a target UE MSGin5G service ID, message ID information, a transfer status, an application ID, a payload, or a priority type information element.

6. The method of claim 1, wherein the message gateway includes at least one of a legacy 3GPP message gateway or a non-3GPP message gateway.

7. The method of claim 1, comprising determining the target UE as a non-MSGin5G UE if the MSGin5G service ID of the target UE is not registered in the registration repository.

8. In the fifth generation message (MSG in 5G) server in wireless network, Memory and a processor; a MSGin5G control unit coupled to the memory and the processor; The MSGin5G control unit receiving a MSG in 5G message request from a source UE to transmit a message to a target UE in the wireless network; Check whether the target UE is registered through a registration repository of an MSGin5G server based on the MSGin5G service ID of the target UE, and registration of a non-MSGin5G UE is performed by a message gateway on behalf of the non-MSGin5G UE; an MSGin5G server configured to send the message to the message gateway if the target UE is a non-MSGin5G UE and the target UE is registered with the MSGin5G server by the message gateway;

9. The MSGin5G control unit The MSGin5G server of claim 8 , further configured to: if the target UE is a MSGin5G UE, send the message to the target UE.

10. The MSGin5G server of claim 8, wherein the message is sent from the message gateway to the UE using a non-MSGin5G message sending service mechanism available at the target UE.

11. The MSGin5G server of claim 8 , wherein address conversion and protocol conversion of the message are performed by the message gateway.

12. The MSGin5G server of claim 8, wherein the MSGin5G message request includes at least one of a source UE MSGin5G service ID, a target UE MSGin5G service ID, message ID information, a transfer status, an application ID, a payload, or a priority type information element.

13. The message gateway comprising at least one of a legacy 3GPP message gateway or a non-3GPP message gateway; The MSGin5G server of claim 8 , wherein deregistration of the target UE with the MSGin5G server is performed by the message gateway on behalf of the target UE.

14. The MSGin5G control unit The MSGin5G server of claim 8, further configured to determine the target UE as a non-MSGin5G UE if the MSGin5G service ID of the target UE is not registered in the registration repository.

Images