[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

WO2020036428A1 - Procédé de transmission de données non ip dans un réseau 5g - Google Patents

Procédé de transmission de données non ip dans un réseau 5g Download PDF

Info

Publication number
WO2020036428A1
WO2020036428A1 PCT/KR2019/010334 KR2019010334W WO2020036428A1 WO 2020036428 A1 WO2020036428 A1 WO 2020036428A1 KR 2019010334 W KR2019010334 W KR 2019010334W WO 2020036428 A1 WO2020036428 A1 WO 2020036428A1
Authority
WO
WIPO (PCT)
Prior art keywords
entity
nef
upf
information
pdu session
Prior art date
Application number
PCT/KR2019/010334
Other languages
English (en)
Korean (ko)
Inventor
이호연
김성훈
손중제
Original Assignee
삼성전자 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from KR1020190016364A external-priority patent/KR20200019072A/ko
Application filed by 삼성전자 주식회사 filed Critical 삼성전자 주식회사
Publication of WO2020036428A1 publication Critical patent/WO2020036428A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]

Definitions

  • the present invention relates to a method and apparatus for transmitting non-IP data in a 5G mobile communication system.
  • a 5G communication system or a pre-5G communication system is called a Beyond 4G network communication system or a post LTE system.
  • 5G communication systems are being considered for implementation in the ultra-high frequency (mmWave) band (eg, such as the 60 Gigabit (60 GHz) band).
  • 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.
  • 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.
  • 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.
  • FQAM Hybrid FSK and QAM Modulation
  • SWSC sliding window superposition coding
  • ACM Advanced Coding Modulation
  • FBMC Fan Bank Multi Carrier
  • NOMA NOMA
  • SAP non-orthogonal multiple access
  • SCMA sparse code multiple access
  • IoT Internet of Things
  • IoE Internet of Everything
  • sensing technology wired / wireless communication and network infrastructure, service interface technology, and security technology
  • M2M machine to machine
  • MTC Machine Type Communication
  • IoT intelligent Internet technology 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.
  • 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.
  • IP internet protocol
  • a method of a session management function (SMF) entity in a mobile communication system 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.
  • 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.
  • 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.
  • a second for establishing a connection between the UPF entity and the NEF entity with the NEF entity may further include transmitting setting information related to data transmission including the information.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 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.
  • 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.
  • 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.
  • 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.
  • PDU packet data unit
  • AMF access and mobility management function
  • 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.
  • 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.
  • a terminal in a mobile communication system according to another aspect of the present invention, 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.
  • 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.
  • the IoT terminal may transmit or receive data (Non-IP data) that does not use an IP protocol communication scheme in a 5G network.
  • FIG. 1 is a diagram illustrating an example of a 5G network system architecture according to an embodiment of the present invention.
  • FIG. 2 is a diagram illustrating an example of a 5G network system architecture in roaming according to an embodiment of the present invention.
  • FIG. 3 is a flowchart illustrating a procedure for setting a data transmission path according to an embodiment of the present invention.
  • FIG. 4 is a flowchart illustrating a data transmission procedure of a terminal according to the first embodiment of the present invention.
  • FIG. 5 is a flowchart illustrating a data transmission procedure of a terminal according to the second embodiment of the present invention.
  • FIG. 6 is a diagram illustrating a configuration of a terminal according to an embodiment of the present invention.
  • FIG. 7 is a diagram illustrating the configuration of a network entity according to an embodiment of the present invention.
  • FIG. 8 is a flowchart illustrating a method of an SMF entity according to an embodiment of the present invention.
  • FIG. 9 is a flowchart illustrating a method of a terminal according to an embodiment of the present invention.
  • 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.
  • the present invention uses the terms and names defined in the specification for the 5th generation (5G) system.
  • the present invention is not limited to the above terms and names, and may be equally applied to systems conforming to other standards.
  • 3GPP 3rd generation partnership project
  • FIG. 1 is a diagram illustrating an example of a 5G network system architecture according to an embodiment of the present invention.
  • a 5G 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”).
  • UE User Equipment
  • RAN radio access network
  • NF Network Function
  • NFs Network Functions
  • AMF Access and Mobility Management Functions
  • NEF Network Exposure Functions
  • SMF Session Management Function
  • UPF User Plane Function
  • AF Application Function
  • the terminal 110 may transmit or receive data with the AF 140.
  • AF 140 may be referred to as an external server.
  • data transmitted by the terminal 110 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 may be delivered to the terminal 110 through the NEF 135, the UPF 130, and the base station 115.
  • 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.
  • IP protocol communication method for example, IPv4 or IPv6
  • non-IP data not using an IP protocol communication method for example, IPv4 or IPv6
  • FIG. 2 is a diagram illustrating an example of a 5G network system architecture in roaming according to an embodiment of the present invention.
  • FIG. 2 exemplarily illustrates a 5G system roaming architecture.
  • the terminal 210 may transmit or receive data with the AF 235.
  • 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.
  • PLMN Public Land Mobile Network
  • Home PLMN Home PLMN
  • 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.
  • Home PLMN Home PLMN
  • UPF 225 User Planet Control Protocol
  • Visited PLMN the UPF 220 of the roaming network
  • 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.
  • 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.
  • IP protocol eg, IP version 4, IP version 6
  • non-IP or Unstructured that does not use a communication method of an IP protocol.
  • FIG. 3 is a flowchart illustrating a procedure for setting a data transmission path according to an embodiment of the present invention.
  • 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.
  • the data transmission path of the PDU session may include a connection between the UPF and the NEF.
  • uplink data eg, uplink UP data
  • 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.
  • the terminal 310 may transmit a Protocol Data Unit (PDU) Session Establishment Request to the AMF for data transmission.
  • PDU Protocol Data Unit
  • the session establishment request message may be referred to as a session establishment request message.
  • the session establishment request message may include an indicator indicating a data type and a data transmission scheme that the terminal intends to transmit.
  • 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”.
  • UP user plane
  • a terminal that wants to send IP data through a user plane data transmission path may set an indicator as "IP data over UP".
  • 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”.
  • CP control plane
  • a terminal that wants to send IP data through the control plane data transmission path may set an indicator as "IP data over CP.”
  • 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).
  • 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.
  • API Application Programming Interface
  • NEF network exposure function
  • the identifier may be identified based on a data network name (DNN) transmitted by the terminal through a session request message.
  • DNN data network name
  • 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.
  • the API eg, NIDD API
  • 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.
  • the SMF may perform the operation of Step 6 according to an embodiment of the present invention.
  • the session establishment request message may include information related to a PDU session (PDU session related information).
  • PDU Session ID PDU Session ID
  • S-NSSAI Single Network Slice Selection Assistance Information
  • DNN Data Network Name
  • 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.
  • DN data type
  • 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.
  • 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.
  • the AMF 330 may select an SMF for establishing a PDU session in step 2 (SMF selection).
  • 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.
  • a function service
  • Etc. select the SMF 340 capable of providing the function requested by the terminal.
  • 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.
  • 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. .
  • the terminal subscription information may include service information available to the terminal.
  • the terminal subscription information may include information related to Registration / subscription retrieval / subscribe for updates.
  • 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.
  • the session-related information of the subscription information may include an indicator that data transmission through NEF is required for the corresponding DNN.
  • 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.
  • 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.).
  • step 5 the SMF 340 may select a UPF for session establishment.
  • 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).
  • 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.
  • 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 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.
  • 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.
  • 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.
  • the terminal subscription information step 4
  • the SMF 340 that selects an NEF may transmit configuration information related to data transmission to the selected NEF 370.
  • 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.
  • the setting information related to data transmission 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).
  • 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.
  • the downlink data may be transmitted to the UPF 360.
  • 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. .
  • 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.
  • tunnel information for example, an IPv6 address and a UDP port number of the NEF
  • 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.
  • tunnel information for example, an IPv6 address and a UDP port number of the SMF
  • 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.
  • 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.).
  • IP address IPv4 address or IPv6 address
  • port number UDP port number or TCP
  • the SMF 340 may include the routing information in a protocol configuration option (PCO) and transmit the same to the terminal 210.
  • PCO protocol configuration option
  • the terminal 210 may transmit or receive data with the AF 280 using the corresponding PDU session.
  • 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.
  • each embodiment will be described with reference to FIG. 4.
  • the terminal 410 that has completed session establishment may transmit non-IP data to the AF 350.
  • the non-IP data may include uplink data or downlink data as shown in FIG. 4.
  • the terminal 410 may transmit uplink data to the UPF 430.
  • 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.
  • 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.
  • 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.
  • the NEF's IP address for example, an NEF's IPv6 address or an IPv4 address
  • 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
  • UDP port number or TCP port number of NEF may be used.
  • 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. .
  • the UPF 430 may send the uplink data including the IP header to the NEF 440.
  • 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.
  • 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.
  • the NEF 440 may use terminal information or UPF information received from the SMF during step 6 of FIG. 3.
  • 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.
  • target node information for example, the IPv6 address and the UDP port number of the NEF
  • Performing the IP decapsulation may include, for example, removing an IP header of the uplink data received from the terminal.
  • the NEF 440 may transmit the IP decapsulated uplink data, ie, uplink data not including the IP header, to the AF 450.
  • 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.
  • 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
  • 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.
  • the terminal's IP address for example, the terminal's IPv6 address or IPv4 address
  • the port number of the terminal for example, the UDP port number of the terminal
  • TCP port number may be used.
  • a UPF IP address (for example, an UPF IPv6 address or an IPv4 address) is used for a target IP address
  • a UPF port number (for example, UDP for a UPF) is used for a target port number. Port number or TCP port number).
  • 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.
  • the UPF 430 may transmit downlink data not including the IP header to the terminal 410.
  • 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.
  • 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.
  • 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.
  • the IP data may include uplink data or downlink data as shown in FIG. 4.
  • the terminal 410 may transmit uplink data to the UPF 430.
  • 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.
  • 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.
  • the UPF 430 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.
  • the destination address for example, the IP address and port number of the NEF
  • 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.
  • 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.
  • 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
  • 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.
  • target (destination) node information eg, IPv6 address and UDP port number of the NEF
  • Performing the IP decapsulation may include, for example, removing an IP header of the uplink data received from the terminal.
  • the NEF 440 may transmit the IP decapsulated uplink data, ie, uplink data not including the IP header, to the AF 450.
  • 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.
  • an NEF's IP address for example, an NEF's IPv6 address or an IPv4 address
  • a NEF's port number for example, the UDP port number for the NEF
  • TCP port number may be used.
  • the IP header may include information of a target (destination) node.
  • the terminal's IP address for example, the terminal's IPv6 address or IPv4 address
  • the port number of the terminal for example, the UDP port number of the terminal
  • TCP port number is used as the target port number.
  • 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
  • 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.
  • 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.
  • 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.
  • 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.
  • uplink data transmitted by the terminal 410 may be transmitted to the AF 480 via the SMF 440.
  • the downlink data transmitted by the AF 480 may be transmitted to the terminal 410 via the SMF 440.
  • 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.
  • each embodiment will be described with reference 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.
  • the non-IP data may include uplink data or downlink data as shown in FIG. 5.
  • 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.
  • 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.
  • 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.
  • the NEF's IP address for example, an NEF's IPv6 address or an IPv4 address
  • 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
  • UDP port number or TCP port number of NEF may be used.
  • 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.
  • 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.
  • NF network function
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • target (destination) node information for example, an IPv6 address and a UDP port number of the NEF
  • Performing the IP decapsulation may include, for example, removing an IP header of the uplink data received from the terminal.
  • the NEF 540 may send the IP decapsulated uplink data, ie, uplink data not including the IP header, to the AF 540.
  • 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.
  • an NEF's IP address for example, an NEF's IPv6 address or an IPv4 address
  • a NEF's port number for example, the UDP port number for the NEF
  • TCP port number may be used.
  • the IP header may include information of a target node.
  • the terminal's IP address for example, the terminal's IPv6 address or IPv4 address
  • the port number of the terminal for example, the UDP port number of the terminal
  • TCP port number may be used.
  • 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
  • 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.
  • the NEF 540 may transmit the encapsulated downlink data to the SMF 535 establishing the NEF connection through the step 6 procedure of FIG.
  • the SMF 535 Upon receiving the downlink data, the SMF 535 transmits the encapsulated downlink data to the UPF 530.
  • 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.
  • the UPF 530 may transmit downlink data not including the IP header to the terminal 510.
  • 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.
  • 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.
  • 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
  • the IP data may include uplink data or downlink data as shown in FIG. 5.
  • the terminal 510 may transmit uplink data to the UPF 530.
  • 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.
  • the UPF 530 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.
  • the destination address for example, the IP address and port number of the NEF
  • 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.
  • 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.
  • 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.
  • 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.
  • target node information for example, the IPv6 address and the UDP port number of the NEF
  • Performing the IP decapsulation may include, for example, removing an IP header of the uplink data received from the terminal.
  • the NEF 540 may send the IP decapsulated uplink data, ie, uplink data not including the IP header, to the AF 550.
  • 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.
  • an NEF's IP address for example, an NEF's IPv6 address or an IPv4 address
  • a NEF's port number for example, the UDP port number for the NEF
  • TCP port number may be used.
  • the IP header may include information of a target node.
  • the terminal's IP address for example, the terminal's IPv6 address or IPv4 address
  • the port number of the terminal for example, the UDP port number of the terminal
  • TCP port number may be used.
  • 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).
  • 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.
  • 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.
  • 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.
  • FIG. 6 is a diagram illustrating a configuration of a terminal according to an embodiment of the present invention.
  • the terminal may include a transceiver 620, a storage unit 630, and a controller 610 for controlling the overall operation of the terminal.
  • the transceiver 620 may include a transmitter 623 and a receiver 626.
  • the transceiver 620 may transmit and receive signals with other network entities.
  • the controller 610 may control the terminal to perform the operation of any one of the above-described embodiments.
  • 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.
  • 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.
  • PDU Protocol Data Unit
  • the controller 610 may control the transceiver 620 so that the terminal 610 receives a PDU Session Establishment Respond from the AMF.
  • the session establishment response message may include a PDU Session ID.
  • the controller 610 may control the transceiver to transmit the uplink data to the UPF.
  • 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.
  • the controller 610 may control the transceiver to receive downlink data from the UPF.
  • 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.
  • the terminal may transmit non-IP data to AF based on IP encapsulation performed in UPF and IP decapsulation performed in NEF.
  • 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.
  • the controller 610 and the transceiver 620 may be electrically connected.
  • the controller 610 may be a circuit, an application-specific circuit, or at least one processor.
  • 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.
  • 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.
  • FIG. 7 is a diagram illustrating the configuration of a network entity according to an embodiment of the present invention.
  • the network entity may include a plurality of network functions (NFs) shown in FIG. 1.
  • NFs network functions
  • 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.
  • the network entity may include a transceiver 720, a storage 730, and a controller 710 for controlling overall operations of the network entity.
  • the transceiver 720 may include a transmitter 723 and a receiver 725.
  • the transceiver 720 may transmit and receive signals with other network entities.
  • the controller 710 may control the network entity to perform the operation of any one of the above-described embodiments.
  • 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.
  • the controller 710 may be a circuit, an application-specific circuit, or at least one processor.
  • 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 may store at least one of information transmitted and received through the transceiver 720 and information generated through the controller 710.
  • the controller of the AMF may control the transceiver to receive a session establishment request message from the terminal.
  • 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.
  • a session creation request message Nsmf_PDUSession_CreateSMContext Request
  • the controller of the AMF may control the transceiver to receive a session creation response message (Nsmf_PDUSession_CreateSMContext Response) from the selected SMF.
  • a session creation response message Nsmf_PDUSession_CreateSMContext Response
  • the controller of the SMF may control the transceiver to receive a session creation request message (Nsmf_PDUSession_CreateSMContext Request) from the AMF.
  • Nsmf_PDUSession_CreateSMContext Request a session creation request message from the AMF.
  • the controller of the SMF may control the transceiver to transmit a session creation response message (Nsmf_PDUSession_CreateSMContext Response) to the AMF.
  • a session creation response message Nsmf_PDUSession_CreateSMContext Response
  • the controller of the SMF may control the transceiver to receive the subscription information of the terminal from the UDM.
  • the controller of the SMF may determine whether the service requested by the terminal is available based on the terminal subscription information, and select an UPF for session establishment.
  • 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 may select an NEF for session establishment.
  • 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.
  • 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.
  • 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 may control the transceiver to transmit a message (Namf_Communication_N1N2MessageTransfer) to the AMF.
  • control unit of the UDM may control the transceiver to transmit the terminal subscription information to the SMF.
  • the control unit of the UPF 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 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.
  • the controller of the NEF may control the transceiver to transmit and receive configuration information related to data transmission with the SMF.
  • the controller of the NEF may control the transceiver to receive uplink data IP-encapsulated from the UPF, that is, uplink data including an IP header.
  • 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 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 may control the transceiver to receive downlink data from the AF.
  • the controller of the NEF may perform IP encapsulation on the downlink data received from the AF.
  • 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.
  • the controller of AF may control the transceiver to transmit and receive configuration information related to data transmission with the NEF.
  • the control unit of the AF may control the transceiver to receive the uplink data that is IP encapsulated from the NEF.
  • the controller of the AF may control the transceiver to transmit downlink data to the NEF.
  • 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.
  • 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.
  • FIG. 8 is a flowchart illustrating a method of an SMF entity according to an embodiment of the present invention.
  • FIG. 8 descriptions overlapping with those described above with reference to FIGS. 1 to 7 will be omitted.
  • the SMF entity may receive a PDU session creation request message for a PDU session from an AMF entity (S810).
  • 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.
  • 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.
  • uplink data transmitted from the terminal to the UPF entity may be transmitted to the NEF through the connection.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 9 is a flowchart illustrating a method of a terminal according to an embodiment of the present invention.
  • descriptions duplicated with those described above with reference to FIGS. 1 to 8 will be omitted.
  • 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).
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 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.
  • hardware circuits such as complementary metal oxide semiconductor based logic circuits, and firmware.
  • hardware circuitry such as a combination of software and / or hardware and firmware and / or software embedded in a machine-readable medium.
  • various electrical structures and methods may be implemented using transistors, logic gates, and electrical circuits such as application specific semiconductors.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un procédé de communication permettant de faire fusionner une technologie IdO avec des systèmes de communication 5G pour prendre en charge des vitesses de transmission de données supérieures à celles des systèmes 4G précédents ; et un système correspondant. La présente invention peut être appliquée à des services intelligents (par exemple, des maisons intelligentes, des bâtiments intelligents, des villes intelligentes, des voitures intelligentes ou des voitures connectées, des soins de santé, l'éducation numérique, le commerce de détail, des services liés à la sécurité et à la sûreté, etc.) sur la base de la technologie de communication 5G et de la technologie liée à l'IdO. L'invention concerne un procédé et un appareil de transmission de données non-IP dans un système de communication mobile 5G.
PCT/KR2019/010334 2018-08-13 2019-08-13 Procédé de transmission de données non ip dans un réseau 5g WO2020036428A1 (fr)

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
KR20180094596 2018-08-13
KR10-2018-0094596 2018-08-13
KR10-2018-0115798 2018-09-28
KR20180115798 2018-09-28
KR1020190016364A KR20200019072A (ko) 2018-08-13 2019-02-12 5G 네트워크에서 non-IP 데이터 전송 방법
KR10-2019-0016364 2019-02-12

Publications (1)

Publication Number Publication Date
WO2020036428A1 true WO2020036428A1 (fr) 2020-02-20

Family

ID=69525649

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2019/010334 WO2020036428A1 (fr) 2018-08-13 2019-08-13 Procédé de transmission de données non ip dans un réseau 5g

Country Status (1)

Country Link
WO (1) WO2020036428A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111511044A (zh) * 2020-04-16 2020-08-07 蓓安科仪（北京）技术有限公司 基于5g网络实现远程医疗的数据通信方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018089879A1 (fr) * 2016-11-14 2018-05-17 Intel IP Corporation Configuration de mesurage de gestion de ressources radio
WO2018127189A1 (fr) * 2017-01-09 2018-07-12 Huawei Technologies Co., Ltd. Système et méthodes de gestion de sessions
WO2018128528A1 (fr) * 2017-01-09 2018-07-12 엘지전자(주) Procédé pour gérer une session pdu dans un système de communication sans fil et appareil associé
WO2018140384A1 (fr) * 2017-01-27 2018-08-02 Idac Holdings, Inc. Cadre d'autorisation pour réseaux 5g

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018089879A1 (fr) * 2016-11-14 2018-05-17 Intel IP Corporation Configuration de mesurage de gestion de ressources radio
WO2018127189A1 (fr) * 2017-01-09 2018-07-12 Huawei Technologies Co., Ltd. Système et méthodes de gestion de sessions
WO2018128528A1 (fr) * 2017-01-09 2018-07-12 엘지전자(주) Procédé pour gérer une session pdu dans un système de communication sans fil et appareil associé
WO2018140384A1 (fr) * 2017-01-27 2018-08-02 Idac Holdings, Inc. Cadre d'autorisation pour réseaux 5g

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SAMSUNG: "New solution: Aggregation of Data over NAS", S 2-186888 . SA WG2 MEETING # 128, 26 June 2018 (2018-06-26), Vilnius, Lithuania, XP051538343 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111511044A (zh) * 2020-04-16 2020-08-07 蓓安科仪（北京）技术有限公司 基于5g网络实现远程医疗的数据通信方法

Similar Documents

Publication Publication Date Title
WO2022177347A1 (fr) Procédé et dispositif de découverte d'un serveur d'applications périphérique
WO2020204474A1 (fr) Dispositif et procédé permettant de fournir un service d'informatique en périphérie dans un système de communication sans fil
WO2019194473A1 (fr) Procédé de commande de session d'unité de données de protocole dans un système de communication sans fil et appareil associé
WO2021054747A1 (fr) Appareil et procédé de relocalisation d'upf psa dans un système de communication sans fil
WO2021187893A1 (fr) Appareil et procédé pour fournir un service d'information d'emplacement à faible latence dans un système de communication sans fil
WO2021066427A1 (fr) Procédé et appareil de gestion de procédures de mobilité pour équipement d'utilisateur
WO2020218857A1 (fr) Appareil et procédé de fourniture de services de communication directe dans un système de communication sans fil
WO2020231120A1 (fr) Procédé et dispositif de gestion d'identifiant d'équipement utilisateur dans un service informatique périphérique
WO2019070100A1 (fr) Dispositif et procédé d'émission ou de réception d'informations dans un système de communication sans fil prenant en charge un découpage de réseau
WO2020091533A1 (fr) Procédé de transmission de signalisation de commande dans un réseau relais, procédé et dispositif de configuration
WO2021194163A1 (fr) Procédé et dispositif de service d'exposition d'événement d'état de retard de paquet basé sur un service upf
WO2017119723A1 (fr) Procédé de contexte d'ue et de reprise de connexion d'ue
WO2021235880A1 (fr) Procédé et dispositif de fourniture d'informations d'un réseau de données local à un terminal dans un système de communication sans fil
WO2021206519A1 (fr) Appareil et procédé de transmission d'informations de gestion de pont dans un système de communication sans fil
WO2020218843A1 (fr) Procédé et système pour fournir une protection de message de strate de non-accès (nas)
WO2023075214A1 (fr) Procédé et appareil pour la prise en charge d'un service d'informatique en périphérie pour un équipement utilisateur en itinérance dans un système de communication sans fil
WO2020138981A1 (fr) Procédé et appareil pour transmettre des informations de règle dans un système de communication sans fil
WO2021235878A1 (fr) Procédé et appareil pour améliorer les optimisations de l'internet des objets cellulaire dans un réseau de télécommunication
WO2022035212A1 (fr) Procédé et appareil pour une opération de relais dans un système de communication sans fil
EP3482576A1 (fr) Procédé et appareil de commande ou de radiomessagerie d'un équipement d'utilisateur
WO2018030859A1 (fr) Procédé et appareil de commande ou de radiomessagerie d'un équipement d'utilisateur
WO2021133092A1 (fr) Procédé et appareil permettant de gérer une procédure de transfert intercellulaire dans un système de communication sans fil
WO2020036428A1 (fr) Procédé de transmission de données non ip dans un réseau 5g
WO2023140704A1 (fr) Procédé et dispositif de mappage de politique de sélection de routage d'ue dans un système de communication sans fil
WO2024025375A1 (fr) Procédé et appareil pour l'authentification d'une attaque de fausse station de base dans un système de communication sans fil

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19849280

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19849280

Country of ref document: EP

Kind code of ref document: A1