WO2020036428A1 - Method for transmitting non ip-data in 5g network - Google Patents

Abstract

The present disclosure relates to a communication method for fusing IoT technology with 5G communication systems for supporting higher data transmission rates than preceding 4G systems, and to a system for same. The present disclosure may be applied to intelligent services (for example, smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail business, security and safety-related services, etc.) based on 5G communication technology and IoT-related technology. Disclosed are a method and apparatus for transmitting non-IP data in a 5G mobile communication system.

Description

How to Transfer NON-IP Data on a 5G Network

The present invention relates to a method and apparatus for transmitting non-IP data in a 5G mobile communication system.

In order to meet the increasing demand for wireless data traffic since the commercialization of 4G communication system, efforts are being made to develop an improved 5G communication system or a pre-5G communication system. For this reason, a 5G communication system or a pre-5G communication system is called a Beyond 4G network communication system or a post LTE system. In order to achieve high data rates, 5G communication systems are being considered for implementation in the ultra-high frequency (mmWave) band (eg, such as the 60 Gigabit (60 GHz) band). In 5G communication system, beamforming, massive array multiple input / output (Full-Dimensional MIMO), and full dimensional multiple input / output (FD-MIMO) are used in 5G communication system to increase path loss mitigation of radio waves and increase transmission distance of radio waves. Array antenna, analog beam-forming, and large scale antenna techniques are discussed. In addition, in order to improve the network of the system, 5G communication systems have advanced small cells, advanced small cells, cloud radio access network (cloud RAN), ultra-dense network (ultra-dense network) , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation And other technology developments are being made. In addition, in 5G systems, Hybrid FSK and QAM Modulation (FQAM) and sliding window superposition coding (SWSC), Advanced Coding Modulation (ACM), and FBMC (Filter Bank Multi Carrier) and NOMA are advanced access technologies. Non-orthogonal multiple access (SAP) and sparse code multiple access (SCMA) are being developed.

Meanwhile, the Internet is evolving from a human-centered connection network where humans create and consume information, and an Internet of Things (IoT) network that exchanges and processes information between distributed components such as things. Internet of Everything (IoE) technology, in which big data processing technology through connection with cloud servers and the like, is combined with IoT technology, is also emerging. In order to implement the IoT, technical elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology are required, and recently, a sensor network for connection between things, a machine to machine , M2M), Machine Type Communication (MTC), etc. are being studied. In an IoT environment, intelligent Internet technology (IT) services that provide new value in human life by collecting and analyzing data generated from connected objects may be provided. IoT is a field of smart home, smart building, smart city, smart car or connected car, smart grid, health care, smart home appliances, advanced medical services, etc. through convergence and complex of existing information technology (IT) technology and various industries. It can be applied to.

Accordingly, various attempts have been made to apply the 5G communication system to the IoT network. For example, technologies such as sensor network, machine to machine (M2M), machine type communication (MTC), and the like, are implemented by techniques such as beamforming, MIMO, and array antennas. It is. The application of cloud radio access network (cloud RAN) as the big data processing technology described above may be an example of convergence of 5G technology and IoT technology.

The present invention proposes a method for transmitting data (Non-IP data) that does not use an internet protocol (IP) protocol communication scheme in a 5G network.

Technical problems to be achieved in the present invention are not limited to the above-mentioned technical problems, and other technical problems not mentioned above will be clearly understood by those skilled in the art from the following description. Could be.

A method of a session management function (SMF) entity in a mobile communication system according to an aspect of the present invention provides a PDU session creation request message for a packet data unit (PDU) session from an access and mobility management function (AMF) entity. Receiving, the PDU session creation request message is generated based on a PDU session establishment request message received from a terminal; Determining a user plane function (UPF) entity for the PDU session based on the PDU session creation request message; Determining a network exposure function (NEF) entity for the PDU session based on the PDU session creation request message; And transmitting, to the UPF entity, NEF related information for establishing the PDU session, wherein the NEF related information includes first information for establishing a connection between the UPF entity and the NEF entity. A connection between a UPF entity and the NEF entity may be established based on the first information, and uplink data transmitted from the terminal to the UPF entity may be transmitted to the NEF through the connection.

According to various embodiments, the first information includes first tunnel information for establishing a connection between the UPF entity and the NEF entity, and the first tunnel information includes IP address information and UDP port number information of the NEF entity. It may include.

According to various embodiments of the present disclosure, the PDU session creation request message may indicate an indicator indicating a data type and a data transmission scheme of uplink data to be transmitted by the terminal, or indicate that the uplink data should be delivered to an external server through the NEF entity. It may include at least one of the identifier.

According to various embodiments, when the identifier identifies that the uplink data should be delivered to an external server through the NEF entity, a second for establishing a connection between the UPF entity and the NEF entity with the NEF entity The method may further include transmitting setting information related to data transmission including the information.

According to various embodiments, the second information includes second tunnel information for establishing a connection between the UPF entity and the NEF entity, and the second tunnel information includes IP address information and UDP port number information of the UPF entity. It may include.

According to various embodiments, if the data type of the uplink data identified by the indicator is non-IP data, IP encapsulation for the uplink data is performed by the UPF entity and the IP in IP decapsulation for uplink data on which encapsulation has been performed may be performed by the NEF entity.

In a mobile communication system according to an aspect of the present invention, a method of a terminal includes: transmitting a PDU session establishment request message for establishing a PDU session to an AMF entity; Receiving, from the AMF entity, a PDU session establishment response message in response to the PDU session establishment request message; And transmitting uplink data via the PDU session, wherein the PDU session includes a connection between an NEF entity and an UPF entity, and wherein transmitting the uplink data comprises: transmitting from the terminal to the UPF entity. Transmitting the uplink data to the NEF entity via the connection.

According to various embodiments, the connection between the NEF entity and the UPF entity may include first information for establishing a connection between the UPF entity and the NEF entity sent from an SMF entity to the UPF entity and the NEF entity from the SMF entity. It may be established based on at least one of the second information for establishing a connection between the UPF entity and the NEF entity transmitted to.

According to various embodiments, the first information includes first tunnel information for establishing a connection between the UPF entity and the NEF entity, and the first tunnel information includes IP address information and UDP port number information of the NEF entity. Wherein the second information includes second tunnel information for establishing a connection between the UPF entity and the NEF entity, and the second tunnel information includes IP address information and UDP port number information of the UPF entity. can do.

According to various embodiments of the present disclosure, the PDU session establishment request message may indicate an indicator indicating a data type and a data transmission scheme of uplink data to be transmitted by the terminal, or indicate that the uplink data should be delivered to an external server through the NEF entity. It may include at least one of the identifier.

According to various embodiments, if the data type of the uplink data identified by the indicator is non-IP data, IP encapsulation for the uplink data is performed by the UPF entity and the IP in IP decapsulation for uplink data on which encapsulation has been performed may be performed by the NEF entity.

In a mobile communication system according to another aspect of the present invention, a session management function (SMF) entity includes a transceiver; And at least one processor coupled to the transceiver, wherein the at least one processor is configured to: generate a PDU session creation request message for a packet data unit (PDU) session from an access and mobility management function (AMF) entity; The PDU session creation request message is generated based on a PDU session establishment request message received from a terminal, and determines a user plane function (UPF) entity for the PDU session based on the PDU session creation request message. Determine, based on the PDU session creation request message, a network exposure function (NEF) entity for the PDU session, and transmit, to the UPF entity, NEF related information for establishing the PDU session, and the NEF The related information includes first information for establishing a connection between the UPF entity and the NEF entity, wherein the UPF entity and the A connection between NEF entities may be established based on the first information, and uplink data transmitted from the terminal to the UPF entity may be transmitted to the NEF through the connection.

According to various embodiments, the first information includes first tunnel information for establishing a connection between the UPF entity and the NEF entity, and the first tunnel information includes IP address information and UDP port number information of the NEF entity. It may include.

In a mobile communication system according to another aspect of the present invention, a terminal includes a transceiver; And at least one processor coupled to the transceiver, the at least one processor: sending, to an AMF entity, a PDU session establishment request message for establishing a PDU session, and from the AMF entity, Receive a PDU session establishment response message in response to a session establishment request message, and transmit uplink data via the PDU session, wherein the PDU session includes a connection between an NEF entity and an UPF entity, and transmits the uplink data The method may include transmitting uplink data transmitted from the terminal to the UPF entity to the NEF entity through the connection.

According to various embodiments, a connection between an NEF entity and the UPF entity may include first information for establishing a connection between the UPF entity and the NEF entity sent from an SMF entity to the UPF entity and from the SMF entity to the NEF entity. It may be established based on at least one of the second information for establishing a connection between the transmitted UPF entity and the NEF entity.

According to an embodiment of the present invention, the IoT terminal may transmit or receive data (Non-IP data) that does not use an IP protocol communication scheme in a 5G network.

Effects obtained in the present invention are not limited to the above-mentioned effects, and other effects not mentioned above may be clearly understood by those skilled in the art from the following description. will be.

1 is a diagram illustrating an example of a 5G network system architecture according to an embodiment of the present invention.

2 is a diagram illustrating an example of a 5G network system architecture in roaming according to an embodiment of the present invention.

3 is a flowchart illustrating a procedure for setting a data transmission path according to an embodiment of the present invention.

4 is a flowchart illustrating a data transmission procedure of a terminal according to the first embodiment of the present invention.

5 is a flowchart illustrating a data transmission procedure of a terminal according to the second embodiment of the present invention.

6 is a diagram illustrating a configuration of a terminal according to an embodiment of the present invention.

7 is a diagram illustrating the configuration of a network entity according to an embodiment of the present invention.

8 is a flowchart illustrating a method of an SMF entity according to an embodiment of the present invention.

9 is a flowchart illustrating a method of a terminal according to an embodiment of the present invention.

Hereinafter, the operating principle of the present invention will be described in detail with reference to the accompanying drawings. In the following description of the present invention, when it is determined that detailed descriptions of related well-known functions or configurations may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted. Terms to be described later are terms defined in consideration of functions in the present invention, and may be changed according to intentions or customs of users or operators. Therefore, the definition should be made based on the contents throughout the specification.

Terms used to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network objects, and terms referring to various identification information used in the following description. Etc. are illustrated for convenience of description. Accordingly, the present invention is not limited to the terms described below, and other terms may be used to refer to objects having equivalent technical meanings.

For convenience of description below, the present invention uses the terms and names defined in the specification for the 5th generation (5G) system. However, the present invention is not limited to the above terms and names, and may be equally applied to systems conforming to other standards.

In describing the various embodiments of the present invention in detail, a 3rd generation partnership project (3GPP, hereinafter referred to as "3GPP") will mainly focus on the communication standard set by the standard. The main subject matter is applicable to other communication systems having a similar technical background with a slight modification without departing from the scope of the present invention, which will be determined by those skilled in the art. .

1 is a diagram illustrating an example of a 5G network system architecture according to an embodiment of the present invention.

Referring to FIG. 1, a 5G system (5G network system) refers to a user equipment (User Equipment, UE, hereinafter referred to as "UE" or "terminal") which is a network element, a radio access network (RAN), hereinafter. It may be referred to as "(R) AN" or "base station") and a plurality of internal network functions (hereinafter referred to as Network Function, NF, or "NF" or "NF entity").

As illustrated in FIG. 1, a plurality of network functions (Network Functions, NFs) are referred to as Access and Mobility Management Functions (hereinafter referred to as "AMF" or "AMF entity"), Network Exposure Functions (hereinafter referred to as "NEF" or It will be referred to as “NEF entity”), Session Management Function (hereinafter referred to as “SMF” or “SMF entity”), and User Plane Function (hereinafter referred to as “UPF” or “UPF entity”). And an Application Function (hereinafter referred to as "AF" or "AF entity").

Referring to FIG. 1, the terminal 110 may transmit or receive data with the AF 140. In this specification, AF 140 may be referred to as an external server.

For example, data transmitted by the terminal 110 (uplink data) may be transmitted to the AF 140 via the base station 115, the UPF 130, and the NEF 135. Data transmitted by the AF 140 (downlink data) may be delivered to the terminal 110 through the NEF 135, the UPF 130, and the base station 115.

In an embodiment, the data transmitted or received by the terminal may be IP data using an IP protocol communication method (for example, IPv4 or IPv6) or non-IP data not using an IP protocol communication method.

2 is a diagram illustrating an example of a 5G network system architecture in roaming according to an embodiment of the present invention. In other words, FIG. 2 exemplarily illustrates a 5G system roaming architecture.

Referring to FIG. 2, the terminal 210 may transmit or receive data with the AF 235.

For example, the data transmitted by the terminal 210 may include a base station 215 of a roaming network (Public Land Mobile Network (PLMN)), an UPF 220, an UPF 225 of a home network (Home PLMN), and an NEF ( 230 may be passed to AF 235. Data transmitted by the AF 235 is transmitted to the terminal 210 via the NEF 230 of the home network (Home PLMN), the UPF 225, the UPF 220 of the roaming network (Visited PLMN), and the base station 215. Can be.

As another example, the data transmitted by the terminal 210 may include a base station 225, a UPF 220, an InterWorking Function (NEWF) -NEF 240, a Security Edge Protection Proxy (vSEPP) of a roaming network (Visited PLMN) ( 245 and the hSEPP 250 and the NEF 230 of the home network (Home PLMN) may be delivered to the AF 235. The data transmitted by the AF 235 are NEF 230, hSEPP 250 of the home network (Home PLMN), vSEPP 245 of the roaming network (Visited PLMN), IWF-NEF 240, UPF 220, It may be delivered to the terminal 210 via the base station 215.

In an embodiment, the data transmitted or received by the terminal is IP data using a communication method of an IP protocol (eg, IP version 4, IP version 6) or non-IP or Unstructured that does not use a communication method of an IP protocol. Data.

3 is a flowchart illustrating a procedure for setting a data transmission path according to an embodiment of the present invention. For example, FIG. 3 may be a flowchart illustrating a procedure for establishing a data transmission path (eg, a user plane (UP) data transmission path and / or a control plane (CP) data transmission path) of a PDU session. In an embodiment, the data transmission path of the PDU session may include a connection between the UPF and the NEF. Through this, uplink data (eg, uplink UP data) transmitted from the terminal to the UPF through the base station may be transmitted to the NEF through the connection, and may be transmitted to an external server through an API associated with the NEF. .

Referring to FIG. 3, in step 1, the terminal 310 may transmit a Protocol Data Unit (PDU) Session Establishment Request to the AMF for data transmission. In this specification, the session establishment request message may be referred to as a session establishment request message.

In an embodiment, the session establishment request message may include an indicator indicating a data type and a data transmission scheme that the terminal intends to transmit.

For example, a terminal that wants to send non-IP data through a user plane (UP) data transmission path may set an indicator as “Non-IP data over UP”.

For example, a terminal that wants to send IP data through a user plane data transmission path may set an indicator as "IP data over UP".

For example, a terminal that wants to send non-IP data through a control plane (CP) data transmission path may set an indicator to “non-IP data over CP”.

For example, a terminal that wants to send IP data through the control plane data transmission path may set an indicator as "IP data over CP."

In an embodiment, the session request message may include an identifier indicating whether data transmitted from the terminal is transmitted to an external server through an API (Application Programming Interface) through a network exposure function (NEF). For example, the session request message is transmitted to the external server AF through the data transmitted by the terminal through an API supported by the NEF (eg, an API for non-ip data delivery service (NIDD API)). It may include an identifier indicating.

For example, the identifier may be identified based on a data network name (DNN) transmitted by the terminal through a session request message.

For example, if the SMF receiving the identifier is IP data, but the PDU type (data type) of the terminal is IP data, but the value indicated by the DNN means that data is transmitted to the external server through the NEF to the API, an embodiment of the present invention It can be determined that the operation according to the. (Step 6). For example, the SMF identifies that the data type of data transmitted by the terminal corresponds to IP data based on the indicator, and through the API (eg, NIDD API) supported by the NEF based on the identifier. When identifying that it should be transmitted, the SMF may perform the operation of step 6 according to an embodiment of the present invention.

In an embodiment, the session request message may include an indicator such as “API connectivity”. This indicator means that the PDU session connection is for data communication with an external server through the API provided by NEF. The SMF receiving the indicator identifies the indicator, and if the corresponding PDU Session Establishment Request means to transmit data to an external server through the NEF to the API, the present invention is implemented. It may be determined that an operation according to an example is performed. (Step 6) For example, the SMF sends data to AF via an API (e.g., NIDD API) supported by the NEF that the corresponding PDU session connection (or the corresponding PDU session establishment (establishment) request) based on the indicator. In identifying the case, the SMF may perform the operation of Step 6 according to an embodiment of the present invention.

In an embodiment, the session establishment request message may include information related to a PDU session (PDU session related information).

For example, as an example of the PDU session-related information, PDU Session ID, Single Network Slice Selection Assistance Information (hereinafter referred to as "S-NSSAI"), Data Network Name (hereinafter referred to as "DNN"). Etc. may be included.

As an embodiment, the DNN included in the session establishment request message may be a value representing a data type (DN) that the terminal can support and a data transmission scheme capable of supporting the data transmission scheme.

For example, a terminal that wants to send non-IP data through a user plane data transmission path may request a session establishment request message with a value of a DNN indicating a DN capable of sending non-IP data through a user plane data transmission path. Can be included in

Upon receiving the PDU session establishment request message in step 1, the AMF 330 may select an SMF for establishing a PDU session in step 2 (SMF selection).

As an embodiment, the AMF 330 may include information on a function (service) requested by the UE included in the PDU session establishment request message (for example, an indicator indicating a data type and a data transmission method, an S-NSSAI, and a DNN). Etc.) and select the SMF 340 capable of providing the function requested by the terminal.

In step 2, the AMF 330 performing the SMF selection may transmit a session creation request message (Nsmf_PDUSession_CreateSMContext Request) to the selected SMF 340 in step 3, and the SMF 240 that receives the session creation request message generates a session. The response message (Nsmf_PDUSession_CreateSMContext Response) may be returned to the AMF 330.

Upon receiving the session creation request message in step 3, the SMF 340 may obtain subscription information (terminal subscription information or subscription information) of the terminal from the unified data management (UDM) 350 in step 4. .

In an embodiment, the terminal subscription information may include service information available to the terminal.

For example, the terminal subscription information may include information related to Registration / subscription retrieval / subscribe for updates.

For example, the service information available to the terminal may include a DNN, S-NSSAI, service indication, etc. available to the terminal.

The SMF 340 may determine whether the service requested by the terminal is available based on the terminal subscription information.

In addition, the session-related information of the subscription information may include an indicator that data transmission through NEF is required for the corresponding DNN. This allows the SMF to identify that the PDU Session is for a DNN that exchanges data with an external server via the NEF. This indicator may be expressed as, for example, “API connectivity” or “API indication” and means an indicator indicating that the corresponding PDU session is a PDU session using an API provided by the NEF.

In addition, the Session related information of the subscription information obtained by the SMF 340 from the UDM 350 includes an address of the NEF providing (supporting) an API or Tunnel information for establishing a connection between the NEF and the UPF (for example, NEF's IPv6 address and UDP port number, etc.).

In step 5 the SMF 340 may select a UPF for session establishment.

For example, the SMF 340 may include information on a function requested by a UE included in a PDU Session Establishment Request (eg, an indicator indicating a data type and a data transmission method, and an S-NSSAI). , DNN, etc.) and the UE subscription information obtained from the UDM 350, and the UPF 360 capable of providing the function requested by the UE may be selected (UPF selection).

In addition, if it is determined that the corresponding PDU session is a PDU session that transmits and receives data with an external server through an API provided by the NEF, the SMF 340 may provide information that allows the UPF to route data to the corresponding NEF. For example, the SMF 340 may provide an address of the NEF or tunnel information (eg, an IPv6 address and a UDP port number of the NEF) for establishing a connection between the NEF and the UPF.

The SMF 340 may select the NEF 370 for session establishment.

For example, the SMF 340 may include information on a function requested by a UE included in a PDU Session Establishment Request (eg, an indicator indicating a data type and a data transmission method, and an S-NSSAI). , DNN, etc.) and the terminal subscription information (step 4) obtained from the UDM 350, and the NEF 370 capable of providing the function requested by the terminal may be selected.

In step 6, according to various embodiments of the present disclosure, the SMF 340 that selects an NEF may transmit configuration information related to data transmission to the selected NEF 370.

As an embodiment, the setting information (data transmission related information) related to data transmission may include an IP address of the terminal (for example, an IPv4 address or an IPv6 address), a port number of the terminal (for example, a UDP port number or a TCP port number). Etc.), PDU Session ID, external UE ID, subscriber ID (SUPI), UPF address, or Tunnel information for establishing a connection between UPF and NEF (e.g., IPv6 address and UDP of UPF). Port number), and the like.

Further, as an embodiment, the setting information related to data transmission (data transmission related information) includes an AF ID indicating the AF 380 (eg, a T8 destination address, etc.), and DNN information requested by the terminal in step 1 (eg, And a DNN for identifying a data transmission path connection with a specific AF. The NEF 370 acquires the data transmission related information received in step 6 through the communication establishment operation (procedure) performed with the AF 380 in step 0 (for example, information according to an API setting procedure for data delivery). To correlate with Accordingly, the NEF may determine in step 0 which data transmission-related information the data transmission API setting requested by the AF 380 is associated with, and accordingly, forward the upstream data to the AF 380 when the uplink data is received. When the downlink data is received from the AF 380, the downlink data may be transmitted to the UPF 360.

In addition, the SMF 340 that selects the NEF may transmit a NEF connection creation request message to the selected NEF 370, and the NEF 370 that receives the NEF connection creation request message sends an NEF connection creation response message to the SMF 340. You can reply (step 6, communication establishment).

The NEF connection creation request message transmitted from the SMF 240 to the NEF 270 in step 6 may include a user ID, a PDU session ID, NEF ID, NIDD information, S-NSSAI, and DNN information. .

According to an embodiment of the present invention, the NEF 370 that receives the NEF connection creation request message from the SMF 340 may generate a NEF PDU session context for the received UE ID and PDU session ID. The NEF 370 having created the NEF PDU session context may return an NEF connection creation response message to the SMF 340.

The NEF connection generation response message may include a user ID, a PDU session ID, an NEF ID, S-NSSAI, and DNN information.

The SMF 340 that receives the NEF connection creation request response message from the NEF 370 in step 6 may perform steps 8 and 9 according to an embodiment of the present invention.

SMF 340 may provide NEF 370 information for session establishment to UPF 360 (step 7 or step 11).

The NEF information for session establishment provided by the SMF to the UPF may include an address of the NEF or tunnel information (for example, an IPv6 address and a UDP port number of the NEF) for establishing a connection between the NEF and the UPF.

In addition, the SMF 340 performing the step 5 procedure in step 1 of FIG. 3 may provide the UPF 360 with SMF information for session establishment (step 7 or step 11).

The SMF information for session establishment provided by the SMF to the UPF may include an address of the SMF or tunnel information (for example, an IPv6 address and a UDP port number of the SMF) for establishing a connection between the SMF and the UPF.

In addition, the SMF information for session establishment provided by the SMF to the UPF may include a packet detection rule and a forwarding action rule.

The Packet Detection Rule includes N4 Session ID, Rule ID, Precedence, Packet detection information (Source interface, UE IP address, Network instance, CN tunnel info, Packet Filter Set, Application ID, QoS Flow ID, Ethernet PDU Session Information), Outer Parameters such as header removal, Forwarding Action Rule ID, List of Usage Reporting Rule IDs, and List of QoS Enforcement Rule IDs may be included.

The Forwarding Action Rule includes N4 Session ID, Rule ID, Action, Network instance, Destination interface, Outer header creation, Send end market packet, Transport level marking, Transport level marking, Forwarding policy, Request for Proxying in UPF, Container for header enrichment , Buffering Action Rule, etc. may be included.

The above-described step 7 process may be performed after step 5 and before step 6, or after step 6.

The SMF 340 that has performed data transmission setup with the NEF 270 performs session setup through step 8 (Namf_Communication_N1N2MessageTransfer) and step 9 (NAS transport (PDU Session ID, SM: PDU Session Establishment Response)). The response message may be returned to the terminal 310.

SMF 340 may include routing information in the Step 8 message.

The routing information includes the data transmission path setting information of the NEF obtained from the UDM 350 in step 4 (for example, an IP address (IPv4 address or IPv6 address), port number (UDP port number or TCP) for data transmission of the NEF. Port number), etc.).

When the SMF 340 configures a PDU Session Establishment Response message to be sent to the terminal 310 in step 8, the SMF 340 may include the routing information in a protocol configuration option (PCO) and transmit the same to the terminal 210.

Upon receiving the session establishment response message, the terminal 210 may transmit or receive data with the AF 280 using the corresponding PDU session.

4 is a flowchart illustrating a data transmission procedure of a terminal according to the first embodiment of the present invention. The first embodiment of the present invention is an embodiment in which the terminal transmits data to the AF through the NEF without passing through the SMF, the first-first embodiment of the terminal to transmit non-IP data to the AF and the terminal to the IP to AF It includes the embodiment 1-2 for transmitting data. Hereinafter, each embodiment will be described with reference to FIG. 4.

<Example 1-1>

Referring to FIG. 4, through the procedure shown in FIG. 3, the terminal 410 that has completed session establishment (step 0 of FIG. 4) may transmit non-IP data to the AF 350.

As an embodiment, the non-IP data may include uplink data or downlink data as shown in FIG. 4.

For example, as shown in FIG. 4, in step 1a, the terminal 410 may transmit uplink data to the UPF 430.

In step 2a, the UPF 430 that has received the uplink data may perform IP encapsulation.

Performing the IP encapsulation may include, for example, adding an IP header to uplink data received from the terminal.

The IP header may include information of a source node.

For example, the source IP address of the terminal is used as the source IP address of the IP header (for example, the terminal's IPv6 address or IPv4 address), and the source port number of the UDP header or the TCP header following the IP header. A port number of the terminal (for example, a UDP port number or a TCP port number of the terminal) may be used as the port number.

In another example, the IP address of the UPF (for example, the IPv6 address or the IPv4 address of the UPF) is used for the source IP address of the IP header, and the source port number of the UDP header or the TCP header following the IP header is used. The port number of the UPF (eg, the UDP port number or the TCP port number of the UPF) can be used.

The IP header may include information of a target (or destination) node. For example, the NEF's IP address (for example, an NEF's IPv6 address or an IPv4 address) is used for the target IP address in the IP header, and the NEF is used for the target port number in the UDP header or TCP header following the IP header. The port number (e.g., UDP port number or TCP port number of NEF) may be used.

For example, in order to perform the step 2a of FIG. 4, the UPF 430 may use the NEF information received from the SMF during the step 5 of FIG. 3, the step 7 of FIG. 3, or the step 11 of FIG. 3. .

In step 3a, the UPF 430 may send the uplink data including the IP header to the NEF 440.

In step 4a, the NEF 440 may perform IP decapsulation. The NEF 440 may determine the next operation by checking the IP header of the received uplink data.

For example, the NEF 440 receiving the uplink data includes source node information (for example, an IPv6 address and a UDP port number of a terminal or an IPv6 address and a UDP port number of a UPF) of an IP header of a received message (packet). Etc.), it can be determined that the received message is a message sent by a terminal. To this end, the NEF 440 may use terminal information or UPF information received from the SMF during step 6 of FIG. 3.

In another example, the NEF 440 receiving the uplink data checks the target node information (for example, the IPv6 address and the UDP port number of the NEF) of the IP header of the received message (packet). It can determine to which AF to forward uplink data.

Performing the IP decapsulation may include, for example, removing an IP header of the uplink data received from the terminal.

In step 5a, the NEF 440 may transmit the IP decapsulated uplink data, ie, uplink data not including the IP header, to the AF 450.

In addition, as shown in FIG. 4, in operation 1b, the AF 450 may transmit downlink data to the NEF 440.

The NEF 440 that has received the downlink data in step 1b may perform IP encapsulation in step 2b.

Performing the IP encapsulation may include, for example, adding an IP header to downlink data received from the AF.

The IP header may include information of a source node.

For example, the NEF's IP address (for example, an NEF's IPv6 address or an IPv4 address) is used for the source IP address in the IP header, and the NEF's port number (for example, the NEF's) is used for the source port number. UDP port number or TCP port number) can be used.

The IP header may include information of a target (or destination) node. For example, the terminal's IP address (for example, the terminal's IPv6 address or IPv4 address) is used as the target IP address, and the port number of the terminal (for example, the UDP port number of the terminal) is used as the target port number. Or TCP port number) may be used.

In another example, a UPF IP address (for example, an UPF IPv6 address or an IPv4 address) is used for a target IP address, and a UPF port number (for example, UDP for a UPF) is used for a target port number. Port number or TCP port number).

In step 3b, the NEF 440 sends the encapsulated downlink data to the UPF 430, and in step 4b the UPF 430 includes the encapsulated downlink data, i.e., the IP header, to the UE 410. Downlink data can be transmitted.

The UPF 430 that receives the downlink data including the IP header in step 3b may perform IP decapsulation (step 4b).

Performing the IP decapsulation may include, for example, removing an IP header of the downlink data received from the NEF 440.

In step 5b, the UPF 430 may transmit downlink data not including the IP header to the terminal 410.

According to various embodiments of the present disclosure, the terminal 410 is based on the IP encapsulation performed in the UPF 430 and the IP decapsulation performed in the NEF 440. Can be sent.

According to various embodiments of the present disclosure, the terminal 410 is based on the IP encapsulation performed in the NEF 440 and the IP decapsulation performed in the UPF 430. Can be received.

<1-2 Example>

Referring to FIG. 4, the terminal 410 that has completed session establishment (step 0 of FIG. 4) through the procedure illustrated in FIG. 3 transmits data in the form of an IP packet to the AF 450 as shown in FIG. 4. Can be.

As an embodiment, the IP data may include uplink data or downlink data as shown in FIG. 4.

For example, as shown in FIG. 4, in step 1a, the terminal 410 may transmit uplink data to the UPF 430.

As an embodiment, the terminal may set the destination (target) address of the IP header for uplink data transmission to the routing information received in step 9 of FIG. 3. For example, the terminal sets a destination IP address of the IP header to an IP address (for example, an IPv4 address or an IPv6 address) of the NEF received in step 9 of FIG. 3, and then the UDP header following the IP header. Alternatively, the destination port number of the TCP header may be set to a port number (for example, a UDP port number or a TCP port number) of the NEF received in step 9 of FIG. 3.

Upon receiving the uplink data in step 1a, the UPF 430 checks the destination address (for example, the IP address and port number of the NEF) of the IP header set by the terminal, and uplinks the corresponding NEF 440 to the corresponding NEF 440. Data can be transferred (step 3a). At this time, step 2a may be omitted.

In step 4a, the NEF 440 may perform IP decapsulation. The NEF 440 may determine the next operation by checking the IP header of the received uplink data.

For example, the NEF 440 receiving the uplink data may include source node information (eg, an IPv6 address and a UDP port number of a terminal or an IPv6 address and an UPD port number of an UPF) in an IP header of a received message (packet). Etc.), it can be determined that the received message is a message sent by a terminal. To this end, the NEF 440 may use terminal information or UPF information received from the SMF during step 6 of FIG. 3.

In another example, the NEF 440 receiving the uplink data checks target (destination) node information (eg, IPv6 address and UDP port number of the NEF) of the IP header of the received message (packet). It may determine to which AF to forward the received uplink data.

Performing the IP decapsulation may include, for example, removing an IP header of the uplink data received from the terminal.

In step 5a, the NEF 440 may transmit the IP decapsulated uplink data, ie, uplink data not including the IP header, to the AF 450.

In addition, as shown in FIG. 4, in operation 1b, the AF 450 may transmit downlink data to the NEF 440.

The NEF 440 that has received the downlink data in step 1b may perform IP encapsulation in step 2b.

Performing the IP encapsulation may include, for example, adding an IP header to downlink data received from the AF. The IP header may be configured based on the information that the NEF 340 receives from the SMF in step 6 of FIG. 3.

The IP header may include information of a source node.

For example, an NEF's IP address (for example, an NEF's IPv6 address or an IPv4 address) is used for the source IP address, and a NEF's port number (for example, the UDP port number for the NEF) for the source port number. Or TCP port number) may be used.

The IP header may include information of a target (destination) node. For example, the terminal's IP address (for example, the terminal's IPv6 address or IPv4 address) is used as the target IP address, and the port number of the terminal (for example, the UDP port number of the terminal) is used as the target port number. Or TCP port number).

In another example, the IP address of the UPF (for example, the IPv6 address or the IPv4 address of the UPF) is used for the target IP address, and the port number of the UPF (for example, the UDP port of the UPF) is used for the target port number. Number or TCP port number) can be used.

In step 3b, the NEF 440 sends the encapsulated downlink data to the UPF 430, and in step 4b the UPF 430 includes the encapsulated downlink data, i.e., the IP header, to the UE 410. Downlink data can be transmitted.

The UPF 430 that receives the downlink data including the IP header in step 3b may transmit the received message (data) to the terminal 410 through the base station (step 5b). At this time, step 4b may be omitted.

According to various embodiments of the present disclosure, the terminal 410 may transmit data in a non-IP format to the AF 450 based on the IP decapsulation performed by the NEF 440.

According to various embodiments of the present disclosure, the terminal 410 may receive data in a non-IP format from the AF 450 in the form of an IP packet based on the IP encapsulation performed in the NEF 440.

According to an embodiment of the present disclosure, uplink data transmitted by the terminal 410 may be transmitted to the AF 480 via the SMF 440. In addition, the downlink data transmitted by the AF 480 may be transmitted to the terminal 410 via the SMF 440.

5 is a flowchart illustrating a data transmission procedure of a terminal according to the second embodiment of the present invention. The second embodiment of the present invention is an embodiment in which the terminal transmits data to the AF through the NEF through the SMF, the embodiment 2-1 in which the terminal transmits the non-IP data to the AF and the terminal to the IP data to the AF It includes the embodiment 2-2 for transmitting. Hereinafter, each embodiment will be described with reference to FIG. 5.

<Example 2-1>

Referring to FIG. 5, the terminal 510 having completed session establishment (step 0) through the procedure illustrated in FIG. 3 may transmit non-IP data to the AF 550 as shown in FIG. 5.

As an embodiment, the non-IP data may include uplink data or downlink data as shown in FIG. 5.

For example, as shown in FIG. 5, in step 1a, the terminal 510 may transmit uplink data to the UPF 530.

The UPF 530 that receives the uplink data in step 2a may perform IP encapsulation.

Performing the IP encapsulation may include, for example, adding an IP header to uplink data received from the terminal.

The IP header may include information of a source node.

For example, the source IP address of the terminal is used as the source IP address of the IP header (for example, the terminal's IPv6 address or IPv4 address), and the source port number of the UDP header or the TCP header following the IP header. A port number of the terminal (for example, a UDP port number or a TCP port number of the terminal) may be used as the port number.

In another example, the IP address of the UPF (for example, the IPv6 address or the IPv4 address of the UPF) is used for the source IP address of the IP header, and the source port number of the UDP header or the TCP header following the IP header is used. The port number of the UPF (eg, the UDP port number or the TCP port number of the UPF) can be used.

The IP header may include information of a target (or destination) node. For example, the NEF's IP address (for example, an NEF's IPv6 address or an IPv4 address) is used for the target IP address in the IP header, and the NEF is used for the target port number in the UDP header or TCP header following the IP header. The port number (e.g., UDP port number or TCP port number of NEF) may be used.

In an embodiment, in order for the UPF 530 to perform step 2a, the NEF information received from the SMF during step 5 of FIG. 3 or step 7 of FIG. 3 or step 11 of FIG. 3 may be used.

In step 3a, the UPF 530 may classify the type of data packet received in step 2a using the Packet Detection Rule received from the SMF through step 7 or step 11 of FIG. If the data packet received in step 2a is a data packet to be delivered to the SMF according to the packet detection rule, the UPF 530 may use the forwarding action rule received from the SMF through step 7 or 11 of FIG. A network function (NF) for transmitting link data may be determined. According to an embodiment of the present invention, the UPF 530 may transmit uplink data to the SMF 535 according to the Forwarding Action Rule.

When the UE 510 sends IP data in step 1a or when the UPF performs IP encapsulation in step 2a, the uplink data sent by the UPF 530 to the SMF 535 may include an IP header. have.

The SMF 535 may transmit uplink data to the NEF 340 which has established an NEF connection through the step 6 procedure of FIG. 3.

In step 4a, the NEF 540 may perform IP decapsulation. The NEF 540 may determine the next operation by checking the IP header of the received uplink data.

For example, the NEF 540 receiving the uplink data stores source node information (eg, an IPv6 address and a UDP port number of a terminal or an IPv6 address and a UDP port number of a UPF, etc.) of an IP header of a received message. By checking, it can be determined that the received message is a message sent by a terminal. To this end, the NEF 540 may use the terminal information or UPF information received from the SMF during step 6 of FIG.

In another example, the NEF 540 receiving the uplink data checks target (destination) node information (for example, an IPv6 address and a UDP port number of the NEF) of the IP header of the received message, and receives the received information. It can determine to which AF to forward uplink data.

Performing the IP decapsulation may include, for example, removing an IP header of the uplink data received from the terminal.

In step 5a, the NEF 540 may send the IP decapsulated uplink data, ie, uplink data not including the IP header, to the AF 540.

In addition, as shown in FIG. 5, in operation 1b, the AF 550 may transmit downlink data to the NEF 540.

The NEF 540 receiving the downlink data in step 1b may perform IP encapsulation in the step 2b.

Performing the IP encapsulation may include, for example, adding an IP header to downlink data received from the AF.

The IP header may include information of a source node.

For example, an NEF's IP address (for example, an NEF's IPv6 address or an IPv4 address) is used for the source IP address, and a NEF's port number (for example, the UDP port number for the NEF) for the source port number. Or TCP port number) may be used.

The IP header may include information of a target node. For example, the terminal's IP address (for example, the terminal's IPv6 address or IPv4 address) is used as the target IP address, and the port number of the terminal (for example, the UDP port number of the terminal) is used as the target port number. Or TCP port number) may be used.

In another example, the IP address of the UPF (for example, the IPv6 address or the IPv4 address of the UPF) is used for the target IP address, and the port number of the UPF (for example, the UDP port of the UPF) is used for the target port number. Number or TCP port number) can be used.

In step 3b, the NEF 540 may transmit the encapsulated downlink data to the SMF 535 establishing the NEF connection through the step 6 procedure of FIG. Upon receiving the downlink data, the SMF 535 transmits the encapsulated downlink data to the UPF 530. In step 4b, the UPF 530 transmits the encapsulated downlink data to the UE 510, that is, IP. The downlink data including the header may be transmitted.

The UPF 530 that receives the downlink data including the IP header in step 3b may perform IP decapsulation (step 4b).

Performing the IP decapsulation may include, for example, removing an IP header of the downlink data received from the NEF 540.

In step 5b, the UPF 530 may transmit downlink data not including the IP header to the terminal 510.

According to various embodiments of the present disclosure, the terminal 510 is based on the IP encapsulation performed in the UPF 530 and the IP decapsulation performed in the NEF 540. Can be sent.

According to various embodiments of the present disclosure, the terminal 510 is based on the IP encapsulation performed in the NEF 540 and the IP decapsulation performed in the UPF 530. Can be received.

<Example 2-2>

Referring to FIG. 5, according to an embodiment of the present invention, the terminal 510 that has completed session establishment (step 0) through the procedure illustrated in FIG. 3 may transmit an IP packet form to the AF 550 as shown in FIG. 5. Data can be sent to

As an embodiment, the IP data may include uplink data or downlink data as shown in FIG. 5.

For example, as shown in FIG. 5, in step 1a, the terminal 510 may transmit uplink data to the UPF 530.

As an embodiment, the terminal may set the destination address of the IP header for uplink data transmission as the routing information received in step 9 of FIG. 3. For example, set the destination (or destination) IP address of the IP header to the IP address (eg, IPv4 address or IPv6 address) of the NEF received in step 9 of FIG. The destination port number of the UDP header or the TCP header may be set to a port number (for example, a UDP port number or a TCP port number) of the NEF received in step 9 of FIG.

Upon receiving the uplink data in step 1a, the UPF 530 views the destination address (for example, the IP address and port number of the NEF) of the IP header set by the terminal, and sends the uplink data to the corresponding NEF 540. Can be transmitted (step 3a). At this time, step 2a may be omitted.

In step 4a, the NEF 540 may perform IP decapsulation. The NEF 540 may determine the next operation by checking the IP header of the received uplink data.

For example, the NEF 540 receiving the uplink data receives source node information (eg, an IPv6 address and a UDP port number of a terminal or an IPv6 address and an UPD port number, etc.) of an IP header of a received message. By checking, it can be determined that the received message is a message sent by a terminal. To this end, the NEF 540 may use terminal information or UPF information received from the SMF during step 6 of FIG. 2.

In another example, the NEF 540 receiving the uplink data checks the target node information (for example, the IPv6 address and the UDP port number of the NEF) of the IP header of the received message, and receives the received uplink data. Can be determined to which AF.

Performing the IP decapsulation may include, for example, removing an IP header of the uplink data received from the terminal.

In step 5a, the NEF 540 may send the IP decapsulated uplink data, ie, uplink data not including the IP header, to the AF 550.

In addition, as shown in FIG. 5, in operation 1b, the AF 550 may transmit downlink data to the NEF 540.

The NEF 540 receiving the downlink data in step 1b may perform IP encapsulation in the step 2b.

Performing the IP encapsulation may include, for example, adding an IP header to downlink data received from the AF. The IP header may be configured based on the information that the NEF 550 receives from the SMF in step 6 of FIG. 3.

The IP header may include information of a source node.

For example, an NEF's IP address (for example, an NEF's IPv6 address or an IPv4 address) is used for the source IP address, and a NEF's port number (for example, the UDP port number for the NEF) for the source port number. Or TCP port number) may be used.

The IP header may include information of a target node. For example, the terminal's IP address (for example, the terminal's IPv6 address or IPv4 address) is used as the target IP address, and the port number of the terminal (for example, the UDP port number of the terminal) is used as the target port number. Or TCP port number) may be used.

Alternatively, for example, the IP address of the UPF (for example, the IPv6 address or the IPv4 address of the UPF) is used as the target IP address, and the port number of the UPF (for example, the UDP of the UPF is used as the target port number). Port number or TCP port number).

In step 3b, the NEF 540 sends the encapsulated downlink data to the UPF 530, and in step 4b the UPF 530 includes the encapsulated downlink data, i.e., the IP header, to the UE 510. Downlink data can be transmitted.

The UPF 530 that receives the downlink data including the IP header in step 3b may transmit the received message to the terminal 510 through the base station (step 5b). At this time, step 4b may be omitted.

According to various embodiments of the present disclosure, the terminal 510 may transmit data in a non-IP format to the AF 550 based on the IP decapsulation performed by the NEF 540.

According to various embodiments of the present disclosure, the terminal 510 may receive non-IP data in the form of an IP packet from the AF 550 based on the IP encapsulation performed by the NEF 540.

6 is a diagram illustrating a configuration of a terminal according to an embodiment of the present invention.

As shown in FIG. 6, the terminal according to an embodiment of the present invention may include a transceiver 620, a storage unit 630, and a controller 610 for controlling the overall operation of the terminal.

The transceiver 620 according to various embodiments of the present disclosure may include a transmitter 623 and a receiver 626.

The transceiver 620 according to various embodiments of the present disclosure may transmit and receive signals with other network entities.

The controller 610 according to various embodiments of the present disclosure may control the terminal to perform the operation of any one of the above-described embodiments. For example, the controller 610 may control a signal flow between blocks to perform the operation according to the flowcharts of FIGS. 3 to 5 and 9 described above.

For example, the controller 610 may control the transceiver 620 so that the terminal 610 transmits a Protocol Data Unit (PDU) Session Establishment Request to the AMF for data transmission.

For example, the controller 610 may control the transceiver 620 so that the terminal 610 receives a PDU Session Establishment Respond from the AMF.

For example, the session establishment response message may include a PDU Session ID.

According to various embodiments of the present disclosure, the controller 610 may control the transceiver to transmit the uplink data to the UPF.

For example, uplink data transmitted from the terminal to the UPF may be delivered to the AF by performing IP encapsulation in the UPF and IP decapsulation in the NEF.

According to various embodiments of the present disclosure, the controller 610 may control the transceiver to receive downlink data from the UPF.

For example, the downlink data received from the UPF by the terminal performs IP encapsulation on the downlink data received from the AF in the NEF, and performs IP encapsulation on the downlink data received from the NEF in the UPF. It may include downlink data.

According to various embodiments of the present disclosure, the terminal may transmit non-IP data to AF based on IP encapsulation performed in UPF and IP decapsulation performed in NEF.

According to various embodiments of the present disclosure, the terminal may receive non-IP data from AF based on IP encapsulation performed in NEF and IP decapsulation performed in UPF.

The controller 610 and the transceiver 620 are not necessarily implemented as separate modules, but may be implemented as a single component in the form of a single chip. In addition, the controller 610 and the transceiver 620 may be electrically connected. For example, the controller 610 may be a circuit, an application-specific circuit, or at least one processor. In addition, the operations of the terminal can be realized by providing a memory device storing the corresponding program code to any component in the terminal.

The storage unit 630 may store at least one of information transmitted and received through the transceiver 620 and information generated through the controller 610. For example, the storage unit may store at least one or more of a session establishment request message, a session establishment response message, and a PDU Session ID.

7 is a diagram illustrating the configuration of a network entity according to an embodiment of the present invention.

The network entity according to various embodiments of the present disclosure may include a plurality of network functions (NFs) shown in FIG. 1.

For example, the network entity illustrated in FIG. 7 may include at least one network function of AMF, NEF, SMF, UPF, or AF disclosed in FIGS. 1 to 3.

As shown in FIG. 7, the network entity according to various embodiments of the present disclosure may include a transceiver 720, a storage 730, and a controller 710 for controlling overall operations of the network entity. In addition, the transceiver 720 may include a transmitter 723 and a receiver 725.

The transceiver 720 according to various embodiments of the present disclosure may transmit and receive signals with other network entities.

The controller 710 according to various embodiments of the present disclosure may control the network entity to perform the operation of any one of the above-described embodiments. On the other hand, the control unit 710 and the transceiver unit 720 is not necessarily to be implemented as separate modules, of course, may be implemented as a single component in the form of a single chip. The controller 710 and the transceiver 720 may be electrically connected to each other. For example, the controller 710 may be a circuit, an application-specific circuit, or at least one processor. In addition, operations of the network entity can be realized by providing a memory device storing the corresponding program code to any component in the network entity.

The storage unit 730 according to various embodiments of the present disclosure may store at least one of information transmitted and received through the transceiver 720 and information generated through the controller 710.

For example, when the network entity illustrated in FIG. 7 is AMF, the controller of the AMF according to various embodiments of the present disclosure may control the transceiver to receive a session establishment request message from the terminal.

According to various embodiments of the present disclosure, the controller of the AMF may select an SMF for establishing a PDU session and control the transceiver to transmit a session creation request message (Nsmf_PDUSession_CreateSMContext Request) to the selected SMF.

The controller of the AMF according to various embodiments of the present disclosure may control the transceiver to receive a session creation response message (Nsmf_PDUSession_CreateSMContext Response) from the selected SMF.

For example, when the network entity illustrated in FIG. 7 is an SMF, the controller of the SMF according to various embodiments of the present disclosure may control the transceiver to receive a session creation request message (Nsmf_PDUSession_CreateSMContext Request) from the AMF.

The controller of the SMF according to various embodiments of the present disclosure may control the transceiver to transmit a session creation response message (Nsmf_PDUSession_CreateSMContext Response) to the AMF.

The controller of the SMF according to various embodiments of the present disclosure may control the transceiver to receive the subscription information of the terminal from the UDM.

The controller of the SMF according to various embodiments of the present disclosure may determine whether the service requested by the terminal is available based on the terminal subscription information, and select an UPF for session establishment.

For example, the control unit of the SMF may include a function requested by a terminal included in a PDU Session Establishment Request (eg, an indicator indicating a data type and a data transmission method, an S-NSSAI, a DNN, etc.). The terminal may check the information and the terminal subscription information obtained from the UDM, and select a UPF capable of providing the function requested by the terminal.

The controller of the SMF according to various embodiments of the present disclosure may select an NEF for session establishment.

For example, the control unit of the SMF may include information about a function requested by the UE included in a PDU Session Establishment Request (for example, an indicator indicating a data type and a data transmission method, an S-NSSAI, DNN, etc.) and the terminal subscription information obtained from the UDM may be checked, and an NEF capable of providing the function requested by the terminal may be selected.

According to various embodiments of the present disclosure, the controller of the SMF may control the transceiver to transmit setting information related to data transmission to the selected NEF, and may perform data transmission setting with the NEF.

The controller of the SMF according to various embodiments of the present disclosure may control the transceiver to transmit a message (Namf_Communication_N1N2MessageTransfer) to the AMF.

For example, when the network entity illustrated in FIG. 7 is a UDM, the control unit of the UDM according to various embodiments of the present disclosure may control the transceiver to transmit the terminal subscription information to the SMF.

For example, when the network entity illustrated in FIG. 7 is an UPF, the control unit of the UPF according to various embodiments of the present disclosure receives uplink data from a terminal and performs IP encapsulation to perform IP encapsulation. The transceiver may be controlled to transmit encapsulated uplink data, that is, uplink data including an IP header to the NEF.

The control unit of the UPF according to various embodiments of the present disclosure receives IP encapsulated downlink data, that is, downlink data including an IP header, from the NEF and performs IP decapsulation. Accordingly, the transceiver may be controlled to transmit IP decapsulated downlink data, that is, downlink data not including an IP header, to the terminal.

For example, when the network entity illustrated in FIG. 7 is an NEF, the controller of the NEF according to various embodiments of the present disclosure may control the transceiver to transmit and receive configuration information related to data transmission with the SMF.

The controller of the NEF according to various embodiments of the present disclosure may control the transceiver to receive uplink data IP-encapsulated from the UPF, that is, uplink data including an IP header.

According to various embodiments of the present disclosure, the controller of the NEF may perform IP decapsulation on IP encapsulated uplink data received from the UPF, that is, uplink data including an IP header. Can be.

The controller of the NEF according to various embodiments of the present disclosure may control the transceiver to transmit IP decapsulated uplink data, that is, uplink data not including an IP header, to the AF.

The controller of the NEF according to various embodiments of the present disclosure may control the transceiver to receive downlink data from the AF.

The controller of the NEF according to various embodiments of the present disclosure may perform IP encapsulation on the downlink data received from the AF.

According to various embodiments of the present disclosure, the controller of the NEF may control the transceiver to transmit downlink data including IP encapsulation, that is, downlink data including an IP header to the UPF.

For example, when the network entity illustrated in FIG. 5 is AF, the controller of AF according to various embodiments of the present disclosure may control the transceiver to transmit and receive configuration information related to data transmission with the NEF.

The control unit of the AF according to various embodiments of the present disclosure may control the transceiver to receive the uplink data that is IP encapsulated from the NEF.

The controller of the AF according to various embodiments of the present disclosure may control the transceiver to transmit downlink data to the NEF.

It should be noted that the configuration diagrams illustrated in FIGS. 6 to 7, an example of a control / data signal transmission method, an operational procedure example, and configuration diagrams are not intended to limit the scope of the present disclosure. In other words, all components, entities, or operations described in the above embodiments should not be interpreted as essential components for the implementation of the disclosure, and may be implemented within the scope of not including the components. Can be.

8 is a flowchart illustrating a method of an SMF entity according to an embodiment of the present invention. In FIG. 8, descriptions overlapping with those described above with reference to FIGS. 1 to 7 will be omitted.

Referring to FIG. 8, the SMF entity may receive a PDU session creation request message for a PDU session from an AMF entity (S810). In this case, the PDU session creation request message may be generated based on the PDU session establishment request message received from the terminal. The operation of receiving a session creation request message at S810 is as described above with reference to step 3 of FIG. 3.

The SMF entity may determine the UPF entity for the PDU session based on the PDU session creation request message (S820). The UPF entity determination (selection) operation of S820 is as described above with reference to step 5 of FIG. 3.

The SMF entity may determine the NEF entity for the PDU session based on the PDU session creation request message (S830). The NER entity determination (selection) operation of S830 is as described above with reference to step 6 of FIG. 3.

The SMF entity is a UPF entity and may transmit NEF related information for establishing a PDU session. In an embodiment, the NEF related information may include first information for establishing a connection between the UPF entity and the NEF entity, and the connection between the UPF entity and the NEF entity may be established based on the first information. In this case, uplink data transmitted from the terminal to the UPF entity may be transmitted to the NEF through the connection.

In an embodiment, the first information includes first tunnel information for establishing a connection between the UPF entity and the NEF entity, and the first tunnel information includes IP address information and UDP port number information of the NEF entity. can do.

In an embodiment, the PDU session creation request message may include at least one of an indicator indicating a data type and a data transmission method of uplink data to be transmitted by the UE or an identifier indicating that uplink data should be delivered to an external server through the NEF entity. It may include.

In an embodiment, where the identifier identifies that the uplink data should be delivered to an external server via the NEF entity, the SMF entity is configured to establish a connection between the UPF entity and the NEF entity with the NEF entity. Configuration information related to data transmission including the second information may be transmitted.

In an embodiment, the second information includes second tunnel information for establishing a connection between the UPF entity and the NEF entity, and the second tunnel information includes IP address information and UDP port number information of the UPF entity. can do.

In an embodiment, when the data type of the uplink data identified by the indicator is non-IP data, IP encapsulation for the uplink data is performed by the UPF entity, and the IP encapsulation is performed. IP decapsulation for the performed uplink data may be performed by the NEF entity. The IP encapsulation and IP decapsulation are as described above with reference to FIGS. 4 to 5.

9 is a flowchart illustrating a method of a terminal according to an embodiment of the present invention. In FIG. 9, descriptions duplicated with those described above with reference to FIGS. 1 to 8 will be omitted.

Referring to FIG. 9, the terminal may transmit a PDU session establishment request message for establishing a PDU session to an AMF entity (S910). The operation of transmitting the PDU session establishment request message in S910 is as described above with reference to step 1 of FIG. 3.

The terminal may receive a PDU session establishment response message from the AMF entity in response to the PDU session establishment request message (S920). The operation of transmitting the PDU session establishment request message at S920 is as described above with reference to step 9 of FIG. 3. Through this, establishment of the PDU session may be completed.

The UE may transmit uplink data through the PDU session (S930).

In an embodiment, the PDU session includes a connection between an NEF entity and an UPF entity, in which case, uplink data transmitted from the terminal to the UPF entity may be transmitted to the NEF entity via the connection.

In some embodiments, the connection between the NEF entity and the UPF entity may include first information for establishing a connection between the UPF entity and the NEF entity sent from an SMF entity to the UPF entity and from the SMF entity to the NEF entity. It may be established based on at least one of the second information for establishing a connection between the UPF entity and the NEF entity.

In an embodiment, the first information includes first tunnel information for establishing a connection between the UPF entity and the NEF entity, and the first tunnel information includes IP address information and UDP port number information of the NEF entity. The second information may include second tunnel information for establishing a connection between the UPF entity and the NEF entity, and the second tunnel information may include IP address information and UDP port number information of the UPF entity. have.

In an embodiment, the PDU session establishment request message may include an indicator indicating a data type and a data transmission scheme of uplink data to be transmitted by the terminal, or an identifier indicating that the uplink data should be transmitted to an external server through the NEF entity. It may include at least one.

In an embodiment, when the data type of the uplink data identified by the indicator is non-IP data, IP encapsulation for the uplink data is performed by the UPF entity, and the IP encapsulation IP decapsulation for this performed uplink data may be performed by the NEF entity. The IP encapsulation and IP decapsulation are as described above with reference to FIGS. 4 to 5.

The operations of the base station or the terminal described above can be realized by providing a memory device storing the corresponding program code to any component in the base station or the terminal device. That is, the controller of the base station or the terminal device may execute the above-described operations by reading and executing the program code stored in the memory device by the processor or the central processing unit (CPU).

The various components of an entity, base station, or terminal device, module, etc. described herein may be hardware circuits, such as complementary metal oxide semiconductor based logic circuits, and firmware. And hardware circuitry such as a combination of software and / or hardware and firmware and / or software embedded in a machine-readable medium. As one example, various electrical structures and methods may be implemented using transistors, logic gates, and electrical circuits such as application specific semiconductors.

Meanwhile, in the detailed description of the present disclosure, specific embodiments have been described, but various modifications may be possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be determined not only by the scope of the following claims, but also by the equivalents of the claims.

Claims (15)

1. A method of a session management function (SMF) entity in a mobile communication system,

   Receiving a PDU session creation request message for a packet data unit (PDU) session from an access and mobility management function (AMF) entity, wherein the PDU session creation request message is generated based on a PDU session establishment request message received from the terminal. Become;

   Determining a user plane function (UPF) entity for the PDU session based on the PDU session creation request message;

   Determining a network exposure function (NEF) entity for the PDU session based on the PDU session creation request message; And

   Transmitting, to the UPF entity, NEF related information for establishing the PDU session,

   The NEF related information includes first information for establishing a connection between the UPF entity and the NEF entity, and a connection between the UPF entity and the NEF entity is established based on the first information,

   The uplink data transmitted from the terminal to the UPF entity is delivered to the NEF via the connection.
2. The method of claim 1,

   The first information includes first tunnel information for establishing a connection between the UPF entity and the NEF entity, and the first tunnel information includes IP address information and UDP port number information of the NEF entity.
3. The method of claim 1,

   The PDU session creation request message,

   And at least one of an indicator indicating a data type and a data transmission scheme of uplink data to be transmitted by the terminal or an identifier indicating that the uplink data should be transmitted to an external server through the NEF entity.
4. The method of claim 3,

   If the identifier identifies that the uplink data should be delivered to an external server via the NEF entity, data transmission comprising second information for establishing a connection between the UPF entity and the NEF entity to the NEF entity. Sending setting information related to the method.
5. The method of claim 4, wherein

   The second information includes second tunnel information for establishing a connection between the UPF entity and the NEF entity, and the second tunnel information includes IP address information and UDP port number information of the UPF entity.
6. The method of claim 3,

   If the data type of the uplink data identified by the indicator is non-IP data, IP encapsulation for the uplink data is performed by the UPF entity, and the IP encapsulation is performed. IP decapsulation for link data is performed by the NEF entity.
7. In the method of the terminal in a mobile communication system,

   Sending, to an AMF entity, a PDU session establishment request message for establishing a PDU session;

   Receiving, from the AMF entity, a PDU session establishment response message in response to the PDU session establishment request message; And

   Transmitting uplink data over the PDU session,

   The PDU session includes a connection between an NEF entity and an UPF entity,

   Transmitting the uplink data,

   Transmitting uplink data transmitted from the terminal to the UPF entity to the NEF entity via the connection.
8. The method of claim 8,

   The connection between the NEF entity and the UPF entity is

   First information for establishing a connection between the UPF entity and the NEF entity sent from an SMF entity to the UPF entity and a second for establishing a connection between the UPF entity and the NEF entity sent from the SMF entity to the NEF entity 2 is established based on at least one of the information.
9. The method of claim 9,

   The first information includes first tunnel information for establishing a connection between the UPF entity and the NEF entity, the first tunnel information includes IP address information and UDP port number information of the NEF entity,

   The second information includes second tunnel information for establishing a connection between the UPF entity and the NEF entity, and the second tunnel information includes IP address information and UDP port number information of the UPF entity.
10. The method of claim 9,

    The PDU session establishment request message,

    And at least one of an indicator indicating a data type and a data transmission scheme of uplink data to be transmitted by the terminal or an identifier indicating that the uplink data should be transmitted to an external server through the NEF entity.
11. The method of claim 10,

    If the data type of the uplink data identified by the indicator is non-IP data, IP encapsulation for the uplink data is performed by the UPF entity, and the IP encapsulation is performed. IP decapsulation for link data is performed by the NEF entity.
12. A session management function (SMF) entity in a mobile communication system,

    Transceiver; And

    At least one processor coupled to the transceiver,

    The at least one processor is:

    Receiving a PDU session creation request message for a packet data unit (PDU) session from an access and mobility management function (AMF) entity, the PDU session creation request message is generated based on a PDU session establishment request message received from the terminal. ,

    Based on the PDU session creation request message, determine a user plane function (UPF) entity for the PDU session,

    Based on the PDU session creation request message, determine a network exposure function (NEF) entity for the PDU session, and

    Transmitting NEF related information for establishing the PDU session to the UPF entity,

    The NEF related information includes first information for establishing a connection between the UPF entity and the NEF entity, and a connection between the UPF entity and the NEF entity is established based on the first information,

    The uplink data transmitted from the terminal to the UPF entity is transmitted to the NEF through the connection.
13. The method of claim 12,

    The first information includes first tunnel information for establishing a connection between the UPF entity and the NEF entity, and the first tunnel information includes IP address information and UDP port number information of the NEF entity. .
14. A terminal in a mobile communication system,

    Transceiver; And

    At least one processor coupled to the transceiver,

    The at least one processor is:

    Send an AMF entity a PDU session establishment request message for establishing a PDU session,

    Receive, from the AMF entity, a PDU session establishment response message in response to the PDU session establishment request message, and

    Transmit uplink data through the PDU session,

    The PDU session includes a connection between an NEF entity and an UPF entity,

    Transmitting the uplink data,

    And transmitting uplink data transmitted from the terminal to the UPF entity to the NEF entity via the connection.
15. The method of claim 14,

    The connection between the NEF entity and the UPF entity is

    First information for establishing a connection between the UPF entity and the NEF entity sent from an SMF entity to the UPF entity and a second for establishing a connection between the UPF entity and the NEF entity sent from the SMF entity to the NEF entity 2, The terminal is established based on at least one of the information.

Images