Patent ID: 12219402

Throughout the drawings, like reference numerals will be understood to refer to like parts, components, and structures.

DETAILED DESCRIPTION

The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the disclosure as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of various embodiments of the disclosure is provided for illustration purpose only and not for the purpose of limiting the disclosure as defined by the appended claims and their equivalents.

It is to be understood that the singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces.

Throughout the disclosure, the expression “at least one of a, b or c” indicates only a, only b, only c, both a and b, both a and c, both b and c, all of a, b, and c, or variations thereof.

In the disclosure, a controller may also be referred to as a processor.

Throughout the specification, a layer (or a layer apparatus) may also be referred to as an entity.

Hereinafter, embodiments of the disclosure will be described with reference to accompanying drawings. In the following description, detailed descriptions of well-known functions or configurations will be omitted when they are considered to unnecessarily obscure the gist of the disclosure. The terms as used herein are those defined by taking the functions of the disclosure into account and may be changed according to the precedents or the intention of users or operators. Therefore, the definitions of those terms should be made according to the overall disclosure set forth herein. Hereinafter, a base station is a subject that performs resource allocation of a terminal, and may be at least one of eNode B, Node B, base station (BS), Next Generation Radio Access Network (NG RAN), a radio access unit, a base station controller, or a node on a network. The terminal may include an Internet of Things (IoT) equipment, a user equipment (UE), Next Generation UE (NG UE), a mobile station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In addition, although embodiments of the disclosure will be described by referring to a 5G system as an example, the embodiments of the disclosure may also be applied to other communication systems having a similar technical background. Furthermore, embodiments of the disclosure may be applied to other communication systems through some modifications without departing from the scope of the disclosure, as determined by those of ordinary skill in the art.

While wireless communication systems are evolving from 4G systems to 5G systems, a new core network, NextGen Core (NG Core), is defined. The new core network has virtualized all existing Network Entities (NEs) into Network Functions (NFs). In addition, the new core network may divide a Mobility Management Entity (MME) function into Mobility Management (MM) and Session Messaging (SM), and may manage UE mobility according to a stage based on the usage type of the UE.

5G wireless communication systems need to support various UEs. For example, the 5G wireless communication systems may support various UEs, such as an enhanced Mobile Broadband (eMBB) UE, an Ultra-Reliable Low-Latency Communications (URLLC) UE, and a Cellular Internet of Things (CIoT) UE. Of them, the CIoT UE may exchange a non-internet protocol (non-IP) packet (non-IP data) with an Application Function/Server (AF/AS) for data communication.

In order for the CIoT UE to exchange the non-IP packet (non-IP data) with the server, a configuration between the core network and the service server is required. To this end, a procedure of setting a Non-IP Data Delivery (NIDD) configuration may be performed. An existing NIDD configuration is set only by a server. Therefore, when a UE intends to transmit data, data is not transmitted because the NIDD configuration is not set. In order to overcome this drawback, a method capable of setting an NIDD configuration in a core network is provided.

Meanwhile, Access and Mobility Management Function (AMF), Session Management Function (SMF), Network Exposure Function (NEF), Application Function (AF), and Unified Data Management (UDM) may be used as the same meaning as an AMF apparatus, an SMF apparatus, an NEF apparatus, an AF apparatus, and a UDM apparatus, respectively. Hereinafter, a method of setting an NIDD configuration in a core network will be described with reference to the accompanying drawings.

FIG.1is a diagram illustrating an NIDD data transmission path according to an embodiment of the disclosure.

Referring toFIG.1, a CIoT UE may establish a PDU session over a control plane for non-IP so as to transmit non-IP data to the control plane. Because the UE transmits data to the control plane, a User Plane Function (UPF) may not be included in the data transmission path. Non-IP data may pass through an NEF so as to be delivered to an external AF through an SMF. At this time, in order for the UE to transmit data to the external server AF without an IP address, an NIDD configuration setting procedure needs to be performed between the NEF and the AF. The NIDD configuration setting procedure has been performed only by the AF. Therefore, when the UE does not perform the NIDD configuration setting procedure in advance at the time of establishing the PDU session for data transmission, the PDU session establishment procedure itself could be cancelled.

In an embodiment of the disclosure, the NIDD configuration setting procedure may be performed not only in the AF but also in the core network, that is, the NEF. Therefore, when the UE performs the PDU session establishment procedure, the UE may perform non-IP data transmission by establishing the PDU session regardless of whether the NIDD configuration has been previously performed.

FIG.2is a diagram illustrating a PDU session establishment method of a UE according to an embodiment of the disclosure. The UE may establish the PDU session so as to transmit non-IP data through a control plane.

Referring toFIG.2, to this end, in operation 1, the UE may transmit a PDU session establishment request message. At this time, in order to transmit data over a network access server (NAS)-SM, that is, a control plane, the PDU session establishment request message may include an indication “data transfer over NAS-SM requested.”

In operation 2, an AMF that receives the PDU session establishment request message may select an SMF capable of transmitting non-IP data. In addition, in operation 3, the AMF may transmit the message to the SMF.

In operation 4-a, the SMF may register the PDU session in a UDM and fetch session management subscription data. In this case, in operation 4-b, the SMF may fetch, from the UDM, at least one of an external identifier, a Mobile Station International Subscriber Directory Number (MSISDN), an external group identifier, or AF ID information of the UE so as to set the NIDD configuration. The above-described information is information shared between a network operator and a service provider in a service agreement between the network operator and the service provider. In addition to the above-described information, authorization token information may also be shared for authentication and authorization between the network operator and the service provider.

In operation 5, the SMF may select an NEF based on subscription data information and perform communication connection establishment with the selected NEF. The communication connection between the SMF and the NEF will be described below with reference toFIG.3.

In operation 6, the NEF may establish a connection with the AF. To this end, a NIDD configuration setting procedure may be performed. This will be described below with reference toFIG.4.

In operation 7, the SMF may transmit a PDU session establishment accept message to the AMF.

In addition, in operation 8, the AMF may transmit the received PDU session establishment accept message to the UE.

FIG.3is a diagram illustrating a procedure of establishing a connection between an SMF and an NEF according to an embodiment of the disclosure.

Referring toFIG.3, in operation 1, during a PDU session establishment procedure, the SMF may receive, from a UE, a session management subscription data and data for setting an NIDD configuration.

In operation 2, the SMF may select an NEF based on subscription data information and transmit, to the NEF, data necessary for setting the NIDD configuration. The SMF may perform a NIDD configuration procedure, based on whether the NIDD configuration procedure is previously performed for the UE between the NEF and AF (application function). If no AF may have previously performed the NIDD Configuration procedure with the NEF, then the NEF initiates the NIDD Configuration procedure. For example, the SMF may transmit an NEF connection request to the NEF. The NEF connection request may include at least one of an external group identifier, an external identifier, an MSISDN, Single Network Slice Selection Assistance Information (S-NSSAI), a Data Network Name (DNN), or an AF ID.

In operation 3, the NEF may create an NEF PDU session context and transmit a response message to the SMF.

FIG.4is a diagram illustrating an NIDD configuration setting procedure for establishing a connection between an NEF and an AF according to an embodiment of the disclosure.

Referring toFIG.4, in operation 1, in a case in which an NIDD configuration with the AF is not set when the UE performs a PDU session establishment procedure so as to transmit non-IP data, the NEF may transmit an NIDD configuration trigger message to the AF. The NIDD configuration message may include at least one of an external group identifier, an external identifier, an MSISDN, an AF ID, or an NEF ID of the UE to which the NIDD configuration is to be set.

In operation 2, the AF that has received the NIDD configuration trigger message may transmit an NIDD configuration request message to the NEF. The NIDD configuration request message may include an NIDD duration and an authorization token necessary for authorizing the AF.

In operation 3, the NEF may transmit, to a UDM, a value received for authorizing the AF. In this case, an S-NSSAI value and a DNN value of a corresponding PDU session may also be transmitted to the UDM.

In operation 4, the UDM may compare the received authorization token value with the S-NSSAI value and the authorization token value for each DNN, which are stored in the service agreement.

In operation 5, as a result of the comparing in operation 4, when the received authorization token value is the same as the S-NSSAI value and the authorization token value for each DNN, which are stored in the service agreement, the UDM may transmit the authorization result value to the NEF via an NIDD authorization response message.

The NEF may assign a reference ID for setting the NIDD configuration and update an NEF PDU session context.

In operation 6, the NEF may transmit a result of a transmission NIDD configuration request to the AF via an NIDD configuration response message. The NIDD configuration response message may include information about the reference ID and a cause.

FIG.5is a block diagram of a UDM apparatus according to an embodiment of the disclosure.

Referring toFIG.5, an UDM apparatus500may include an RF processor510, a baseband processor520, a transceiver530, a memory540, and a controller550. However, this is only an example, and the components of the UDM apparatus500are not limited to the above-described example.

The RF processor510may perform a function for transmitting or receiving signals through a radio channel, such as signal band conversion and signal amplification. The RF processor510may up-convert a baseband signal provided from the baseband processor520into an RF band signal and transmit the RF band signal through an antenna, and may down-convert an RF band signal received through the antenna into a baseband signal. For example, the RF processor510may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), and an analog-to-digital converter (ADC). Although only one antenna is illustrated inFIG.5, the UDM apparatus500may include a plurality of antennas. In addition, the RF processor510may include a plurality of RF chains. The RF processor510may perform beamforming. For beamforming, the RF processor510may adjust phases and amplitudes of signals transmitted or received through a plurality of antennas or antenna elements.

The baseband processor520may perform a conversion function between a baseband signal and a bit stream in accordance with the physical layer standard of a set radio connection technology. For example, when data is transmitted, the baseband processor520may encode and modulate a transmission bit stream to generate complex symbols. In addition, when data is received, the baseband processor520may demodulate and decode a baseband signal provided from the RF processor510to reconstruct a reception bit stream. For example, in accordance with an OFDM scheme, when data is transmitted, the baseband processor520may encode and modulate a transmission bit stream to generate complex symbols, map the complex symbols to subcarriers, and construct OFDM symbols through an inverse fast Fourier transform (IFFT) operation and cyclic prefix (CP) insertion. In addition, when data is received, the baseband processor520may divide a baseband signal provided from the RF processor510on an OFDM symbol basis, reconstruct signals mapped to subcarriers through a fast Fourier transform (FFT) operation, and reconstruct a reception bit stream through demodulation and decoding. The baseband processor520and the RF processor510may transmit and receive signals as described above. Accordingly, the baseband processor520and the RF processor510may be referred to as a transmitter, a receiver, a transceiver, a communicator, or a radio communicator.

The transceiver530may provide an interface configured to communicate with other nodes in the network.

The memory540may store a basic program, an application program, and data, such as configuration information, for the operation of the UDM apparatus500described with reference toFIGS.1to4. The memory540may store information about a bearer allocated to the connected UE, a measurement result reported from the connected UE, and the like. In addition, the memory540may provide stored data in response to the request of the controller550.

The controller550may control overall operations of the UDM apparatus500. For example, the controller550may transmit or receive signals through the baseband processor520and the RF processor510or through the transceiver530. In addition, the controller550may record data to the memory540and may read data from the memory540. To this end, the controller550may include at least one processor.

FIG.6is a block diagram of an NEF apparatus according to an embodiment of the disclosure.

Referring toFIG.6, an NEF apparatus600may include an RF processor610, a baseband processor620, a transceiver630, a memory640, and a controller650. However, this is only an example, and the components of the NEF apparatus600are not limited to the above-described example.

The RF processor610may perform a function for transmitting or receiving signals through a radio channel, such as signal band conversion and signal amplification. The RF processor610may up-convert a baseband signal provided from the baseband processor620into an RF band signal and transmit the RF band signal through an antenna, and may down-convert an RF band signal received through the antenna into a baseband signal. For example, the RF processor610may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, and an ADC. Although only one antenna is illustrated inFIG.6, the NEF apparatus600may include a plurality of antennas. In addition, the RF processor610may include a plurality of RF chains. The RF processor610may perform beamforming. For beamforming, the RF processor610may adjust phases and amplitudes of signals transmitted or received through a plurality of antennas or antenna elements. The baseband processor620may perform a conversion function between a baseband signal and a bit stream in accordance with the physical layer standard of a set radio connection technology. For example, when data is transmitted, the baseband processor620may encode and modulate a transmission bit stream to generate complex symbols. In addition, when data is received, the baseband processor620may demodulate and decode a baseband signal provided from the RF processor610to reconstruct a reception bit stream. For example, in accordance with an OFDM scheme, when data is transmitted, the baseband processor620may encode and modulate a transmission bit stream to generate complex symbols, map the complex symbols to subcarriers, and construct OFDM symbols through an IFFT operation and CP insertion. In addition, when data is received, the baseband processor620may divide a baseband signal provided from the RF processor610on an OFDM symbol basis, reconstruct signals mapped to subcarriers through an FFT operation, and reconstruct a reception bit stream through demodulation and decoding. The baseband processor620and the RF processor610may transmit and receive signals as described above. Accordingly, the baseband processor620and the RF processor610may be referred to as a transmitter, a receiver, a transceiver, a communicator, or a radio communicator.

The transceiver630may provide an interface configured to communicate with other nodes in the network.

The memory640may store a basic program, an application program, and data, such as configuration information, for the operation of the NEF apparatus600described with reference toFIGS.1to4. The memory640may store information about a bearer allocated to the connected UE, a measurement result reported from the connected UE, and the like. In addition, the memory640may provide stored data in response to the request of the controller650.

The controller650may control overall operations of the NEF apparatus600. For example, the controller650may transmit or receive signals through the baseband processor620and the RF processor610or through the transceiver630. In addition, the controller650may record data to the memory640and may read data from the memory540. To this end, the controller650may include at least one processor.

FIG.7is a block diagram of an AF apparatus according to an embodiment of the disclosure.

Referring toFIG.7, an AF apparatus700may include an RF processor710, a baseband processor720, a transceiver730, a memory740, and a controller750. However, this is only an example, and the components of the AF apparatus700are not limited to the above-described example.

The RF processor710may perform a function for transmitting or receiving signals through a radio channel, such as signal band conversion and signal amplification. The RF processor710may up-convert a baseband signal provided from the baseband processor720into an RF band signal and transmit the RF band signal through an antenna, and may down-convert an RF band signal received through the antenna into a baseband signal. For example, the RF processor710may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, and an ADC. Although only one antenna is illustrated inFIG.7, the AF apparatus700may include a plurality of antennas. In addition, the RF processor710may include a plurality of RF chains. The RF processor710may perform beamforming. For beamforming, the RF processor710may adjust phases and amplitudes of signals transmitted or received through a plurality of antennas or antenna elements.

The baseband processor720may perform a conversion function between a baseband signal and a bit stream in accordance with the physical layer standard of a set radio connection technology. For example, when data is transmitted, the baseband processor720may encode and modulate a transmission bit stream to generate complex symbols. In addition, when data is received, the baseband processor720may demodulate and decode a baseband signal provided from the RF processor710to reconstruct a reception bit stream. For example, in accordance with an OFDM scheme, when data is transmitted, the baseband processor720may encode and modulate a transmission bit stream to generate complex symbols, map the complex symbols to subcarriers, and construct OFDM symbols through an IFFT operation and CP insertion. In addition, when data is received, the baseband processor720may divide a baseband signal provided from the RF processor710on an OFDM symbol basis, reconstruct signals mapped to subcarriers through an FFT operation, and reconstruct a reception bit stream through demodulation and decoding. The baseband processor720and the RF processor710may transmit and receive signals as described above. Accordingly, the baseband processor720and the RF processor710may be referred to as a transmitter, a receiver, a transceiver, a communicator, or a radio communicator.

The transceiver730may provide an interface configured to communicate with other nodes in the network.

The memory740may store a basic program, an application program, and data, such as configuration information, for the operation of the AF apparatus700described with reference toFIGS.1to4. The memory740may store information about a bearer allocated to the connected UE, a measurement result reported from the connected UE, and the like. In addition, the memory740may provide stored data in response to the request of the controller750.

The controller750may control overall operations of the AF apparatus700. For example, the controller750may transmit or receive signals through the baseband processor720and the RF processor710or through the transceiver730. In addition, the controller750may record data to the memory740and may read data from the memory540. To this end, the controller750may include at least one processor.

Meanwhile, the embodiments of the disclosure provided in this specification and drawings merely present specific examples so as to describe the technical contents of the disclosure and help the understanding of the disclosure, and are not intended to limit the scope of the disclosure. For example, it will be apparent to those of ordinary skill in the art that other modifications based on the technical spirit of the disclosure may be implemented. In addition, the respective embodiments of the disclosure may be combined with each other when necessary. In addition, although the embodiments of the disclosure are presented based on the 5G wireless communication system, other modifications based on the technical spirit of the embodiments of the disclosure may be implemented in other systems.

According to the embodiments of the disclosure, when the UE establishes the PDU session for data transmission, the NIDD configuration setting procedure is performed in the core network, and therefore, data transmission of the UE may be performed without failure.

While the disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the disclosure as defined by the appended claims and their equivalents.