KR20250113679A - Apparatus and method for managing traffic related to tethered devices - Google Patents

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. According to the present disclosure, a method of an SMF for supporting differentiation of packets transmitted from a terminal and a tethered device connected to the terminal is provided, the method comprising: receiving information related to support of an operation for generating a DSCP value considering a service type including a network type and a media type between the terminal and the tethered device from an AF or the terminal; generating a DSCP value for each network type based on information related to the tethered device and information such as 5QI; generating mapping information between DSCP values considering different network types to support a DSCP-based packet differentiation service when used in different networks; transmitting a DSCP remarking indicator received from a PCF and mapping information between DSCP values considering different network types to a UPF; transmitting information for distinguishing tethered device-related packets transmitted using at least one DSCP value among the mapping information between DSCP values considering different network types and the DSCP remarking indicator to the terminal.

Description

{APPARATUS AND METHOD FOR MANAGING TRAFFIC RELATED TO TETHERED DEVICES}

The present disclosure assumes that in a communication system, tethered devices connected to a terminal via a wired/wireless network transmit packets of different media types to the terminal.

Specifically, the present disclosure may relate to a method and apparatus for supporting generation of classification information by considering a network type between a terminal and a tethered device connected to the terminal and a media type of packets transmitted by the tethered device to the terminal, in relation to mapping the packets to an appropriate QoS flow (quality of state flow), and the present disclosure may relate to a method and apparatus for supporting scheduling by considering QoS of packets transmitted by tethered devices to the terminal through QoS allocation.

5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band, such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (㎜Wave), such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low delay time that is reduced by one-tenth.

In the early stages of 5G mobile communication technology, the goal was to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). The technologies included beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2 Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

Currently, discussions are underway on improving and enhancing the initial 5G mobile communication technology in consideration of the services that the 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.

In addition, standardization of wireless interface architecture/protocols for technologies such as the Industrial Internet of Things (IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) to provide nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step RACH for NR to simplify random access procedures is also in progress, and standardization of system architecture/services for 5G baseline architecture (e.g. Service based Architecture, Service based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal is also in progress.

When such 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, which will require enhanced functions and performance of 5G mobile communication systems and integrated operation of connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, AI service support, metaverse service support, drone communications, etc. using extended reality (XR), artificial intelligence (AI), and machine learning (ML) to efficiently support augmented reality (AR), virtual reality (VR), and mixed reality (MR).

In addition, the development of these 5G mobile communication systems will require new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), and Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, and AI (Artificial Intelligence) from the design stage and AI-based communication technology that implements end-to-end AI support functions to realize system optimization, and ultra-high-performance communication and computing resources to provide services with a level of complexity that goes beyond the limits of terminal computing capabilities. It could serve as a basis for the development of next-generation distributed computing technologies that utilize this.

For metaverse and extended reality (XR) applications, since terminals must transmit and receive a large amount of traffic through downlink/uplink, effective traffic processing can be a more important technical issue than in the case of existing applications. Existing studies have mainly focused on the base station (BS) effectively transmitting downlink traffic to terminals. On the other hand, metaverse/XR traffic may present new challenges to be solved in relation to the need to effectively process downlink traffic by considering the service characteristics of each packet.

In the present disclosure, when a congestion situation occurs in a network entity (e.g. RAN), a method for randomly dropping packets in a scheduler to resolve the congestion situation is provided, in an XR service, a method for dropping packets using traffic characteristic information currently provided in the service can be provided.

Specifically, with respect to XR services, in order to efficiently handle network congestion situations, a method can be provided to drop packets in units of packets with the same characteristics (e.g., PDU set) through an actual application function (AF) entity or an application server (AS), taking into account the importance of the packets being served.

Also, with respect to the existing packet processing method that appropriately forwards data using a simple 5-tuple in UPF, the present disclosure can provide a method for scheduling based on a process of recognizing and extracting RTP (Real-time Transport Protocol) and NAL (Network Adaptation Layer) unit header information of actual data, a process of grouping PDU set information of identical packets based on the unit header information, a process of generating PDU set information based on the extracted unit header information or information received from an AS, and a process of providing PDU set information to RAN via a GTP (GPRS Tunnelling Protocol)-U header, for packet processing using service characteristics.

According to one embodiment of the present disclosure, a device and method for generating information for processing packets having the same characteristics by taking into account service traffic characteristics in a communication system can be provided.

According to one embodiment of the present disclosure, when packets having different media characteristics are transmitted to a terminal through different networks or the same network type from a tethered device connected to a terminal in a communication system, differentiated services code point (DSCP) information can be generated by considering the network type and service traffic characteristics between the tethered device and the terminal. Based on the differentiated DSCP information generated based on the network type information between the tethered device and the terminal, information for differentiating traffic transmitted from the tethered device to the terminal, or information for mapping to an appropriate QoS flow, can be transmitted to the terminal using a QoS rule, etc. The terminal that has received the information for mapping to the QoS flow can perform an operation of mapping to an appropriate QoS flow based on a DSCP value in an IP header of uplink data transmitted from the tethered device.

According to one embodiment of the present disclosure, packets transmitted to a terminal connected to a tethered device in a wireless communication system can perform a differentiation operation according to service characteristics based on a DSCP value marked in a packet header. Specifically, when distinguishing service characteristics between packets through DSCP marking in different networks, an appropriate DSCP value is generated for each network, and based on this, a DSCP remarking operation can be performed with a DSCP value that takes into account the characteristics of the network to which the packet is moving when moving to a different network.

The network type and related media information between the terminal and the tethered device connected to the terminal can be transmitted directly from the terminal to the network or to the network through the AF. In addition, the network can generate an appropriate QoS profile and rule based on the request information of the terminal or the AF and transmit the corresponding information to the terminal. If the DSCP remarking operation is performed on both the terminal and the UPF, the mapping information of the DSCP values considering the remarking operation indicator and the type of the network connected to the 5GC network can be transmitted to the UPF.

According to one embodiment of the present disclosure, in an environment where a separate tethered device ID, etc. is not assigned, a terminal can distinguish different service characteristics of packets transmitted from tethered devices connected to the terminal based on a DSCP value in a packet header transmitted from the tethered device. However, the DSCP value for each network may be different depending on the network type between the terminal and the tethered device connected to the terminal. In this case, different types of networks may need to use different DSCP values.

Accordingly, the 5GC network can generate mapping information between QFI (QoS flow identifier) and DSCP value for each tethered device network type by considering the characteristics of packets and transmit it to the terminal. Based on the mapping information between QFI and DSCP value, the terminal can map packets transmitted from the tethered device to an appropriate QoS flow and support QoS scheduling within the network.

In addition, in a case where the characteristic information between packets is distinguished using DSCP values in each network of a system connected with networks using different network types, it is possible to support allocation of appropriate packet-specific service distinction information and related operations for each network type by performing DSCP value remarking operations of network entities (e.g. UE and/or UPF) connected to different networks.

The effects obtainable from the present disclosure are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by a person skilled in the art to which the present disclosure belongs from the description below.

The above and other objects, features and advantages of the present disclosure will become more apparent from the following description of embodiments of the present disclosure with reference to the accompanying drawings.
FIG. 1 is a diagram illustrating a network structure and interface of a 5G system according to one embodiment of the present disclosure.
FIG. 2 is a diagram illustrating an operation of transmitting information for distinguishing packets transmitted by a tethered device in a wireless communication system according to an embodiment of the present disclosure.
FIG. 3 is a flowchart illustrating a system composed of different network types and related operations in a wireless communication system according to one embodiment of the present disclosure.
FIG. 4A is a flowchart for transmitting information related to the performance of an operation for distinguishing packets using information such as DSCP values based on network type and service characteristic information between a tethered device and a terminal in a wireless communication system according to one embodiment of the present disclosure.
FIG. 4B is a flowchart for transmitting information related to the performance of an operation for distinguishing packets using information such as DSCP values based on network type and service characteristic information between a tethered device and a terminal in a wireless communication system according to one embodiment of the present disclosure.
FIG. 4C is a flowchart for transmitting information related to the performance of an operation for distinguishing packets using information such as DSCP values based on network type and service characteristic information between a tethered device and a terminal in a wireless communication system according to one embodiment of the present disclosure.
FIG. 5A is a flowchart for transmitting information related to an operation for distinguishing packets based on information such as a DSCP value generated based on network type and service characteristic information between a tethered device and a terminal received from an AF in a wireless communication system according to an embodiment of the present disclosure, and performing a packet remarking operation for supporting different networks using DSCP information.
FIG. 5B is a flowchart for transmitting information related to an operation for distinguishing packets based on information such as a DSCP value generated based on network type and service characteristic information between a tethered device and a terminal received from an AF in a wireless communication system according to an embodiment of the present disclosure, and a packet remarking operation for supporting different networks using DSCP information.
FIG. 5C is a flowchart for transmitting information related to an operation for distinguishing packets based on information such as a DSCP value generated based on network type and service characteristic information between a tethered device and a terminal received from an AF in a wireless communication system according to an embodiment of the present disclosure, and performing a packet remarking operation for supporting different networks using DSCP information.
FIG. 6A is a flowchart for transmitting information related to performing an operation for distinguishing packets based on information such as a DSCP value generated based on network type and service characteristic information between a tethered device and a terminal received from a terminal in a wireless communication system according to one embodiment of the present disclosure, and performing a packet remarking operation to support distinguishing packets based on DSCP information in different networks.
FIG. 6B is a flowchart for transmitting information related to performing an operation for distinguishing packets based on information such as a DSCP value generated based on network type and service characteristic information between a tethered device and a terminal received from a terminal in a wireless communication system according to one embodiment of the present disclosure, and performing a packet remarking operation to support distinguishing packets based on DSCP information in different networks.
FIG. 6C is a flowchart for transmitting information related to performing an operation for distinguishing packets based on information such as a DSCP value generated based on network type and service characteristic information between a tethered device and a terminal received from a terminal in a wireless communication system according to an embodiment of the present disclosure, and performing a packet remarking operation to support distinguishing packets based on DSCP information in different networks.
FIG. 7 is a block diagram illustrating the structure of a terminal according to one embodiment of the present disclosure.
FIG. 8 is a block diagram illustrating the structure of an SMF entity according to one embodiment of the present disclosure.
FIG. 9 is a block diagram illustrating the structure of an AMF entity according to one embodiment of the present disclosure.
FIG. 10 is a block diagram illustrating the structure of a UPF entity according to one embodiment of the present disclosure.

Hereinafter, an embodiment of the present disclosure will be described in detail with reference to the attached drawings.

In describing the present disclosure, descriptions of technical contents that are well known in the technical field to which the present disclosure belongs and are not directly related to the present disclosure will be omitted. This is to convey the gist of the present disclosure more clearly without obscuring it by omitting unnecessary explanations. In addition, the terms described below are terms defined in consideration of functions in the present disclosure, and these may vary depending on the intention or custom of the user or operator. Therefore, the definitions should be made based on the contents throughout this specification.

For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically illustrated. In addition, the size of each component does not entirely reflect the actual size. The same or corresponding components in each drawing are given the same reference numbers.

Hereinafter, a base station (BS) is an entity that performs resource allocation of a terminal, and may be at least one of a gNode B, an eNode B, a Node B, (or xNode B (wherein x is an alphabet including g or e)), a wireless access unit, a base station controller, a satellite, an airborn, or a node on a network. A user equipment (UE) may include a mobile station (MS), a vehicle, a satellite, an airborn, a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, a downlink (DL) refers to a wireless transmission path of a signal that a base station transmits to a terminal, and an uplink (UL) refers to a wireless transmission path of a signal that a terminal transmits to an air base station. Additionally, a sidelink (SL) may exist that refers to a wireless transmission path of a signal that a terminal transmits to another terminal.

In addition, although LTE, LTE-A or 5G system may be described as an example below, the embodiment of the present disclosure may be applied to other communication systems having similar technical backgrounds or channel types. For example, 5G-Advance or NR-Advance or 6th generation mobile communication technology (6G) developed after 5G mobile communication technology (or new radio, NR) may be included here, and 5G below may be a concept including existing LTE, LTE-A and other similar services. In addition, the present disclosure may be applied to other communication systems through some modifications without significantly departing from the scope of the present disclosure as judged by a person having skilled technical knowledge.

At this time, it will be understood that each block of the processing flow diagrams and combinations of the flow diagrams can be performed by computer program instructions. These computer program instructions can be loaded onto a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flow diagram block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce an article of manufacture that includes an instruction means for performing the functions described in the flow diagram block(s). Since the computer program instructions may be installed on a computer or other programmable data processing apparatus, a series of operational steps may be performed on the computer or other programmable data processing apparatus to produce a computer-executable process, so that the instructions executing the computer or other programmable data processing apparatus may also provide steps for executing the functions described in the flowchart block(s).

Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a particular logical function(s). It should also be noted that in some alternative implementation examples, the functions mentioned in the blocks may occur out of order. For example, two blocks shown in succession may in fact be performed substantially concurrently, or the blocks may sometimes be performed in reverse order, depending on the functionality they perform.

Here, the term '~ part' used in the present embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ part' performs certain roles. However, the '~ part' is not limited to software or hardware. The '~ part' may be configured to be in an addressable storage medium and may be configured to reproduce one or more processors. Accordingly, as an example, the '~ part' includes components such as software components, object-oriented software components, class components, and task components, and processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided in the components and '~ parts' may be combined into a smaller number of components and '~ parts' or further separated into additional components and '~ parts'. In addition, the components and '~parts' may be implemented to play one or more CPUs within the device or secure multimedia card. Also, in an embodiment, the '~part' may include one or more processors.

3GPP, which is in charge of cellular mobile communication standards, is naming a new core network structure 5G Core (5GC) and standardizing it to promote evolution from 4G LTE systems to 5G systems. 5GC supports the following differentiated functions compared to the Evolved Packet Core (EPC), which is the network core for 4G.

5GC introduces the Network Slice feature. As a requirement of 5G, 5GC must support various types of terminal types and services; e.g., enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine Type Communications (mMTC). Each of these terminals/services has different requirements for the core network. For example, eMBB service may require high data rate, while URLLC service may require high stability and low latency. To satisfy these various service requirements, Network Slice technology has been proposed.

Network slicing can mean a method of virtualizing a single physical network to create multiple logical networks (e.g., network slices). An activated network slice can be called a network slice instance, and each network slice instance (NSI) can have different characteristics. By configuring a network function (NF) for each NSI according to its characteristics, a mobile communication operator can satisfy various service requirements according to terminals/services. For example, a mobile communication operator can efficiently support multiple 5G services (e.g., eMBB, URLLC, or mMTC) by allocating an NSI according to the characteristics of the service required for each terminal.

5GC can easily support the network virtualization paradigm by separating the mobility management function and the session management function. In 4G LTE, all terminals can receive services from the network through signaling exchange with a single core entity called the mobility management entity (MME) that is responsible for registration, authentication, mobility management, and session management functions. In 5G, the number of terminals (including, for example, MTC terminals) increases explosively, and the mobility and traffic/session characteristics that must be supported depending on the type of terminal are segmented. Therefore, if a single entity (for example, MME) supports all functions, the scalability that adds entities for each required function will inevitably decrease. Therefore, various functions are being developed based on a structure that separates the mobility management function and the session management function to improve scalability in terms of the functional/implementation complexity and signaling load of the core entity responsible for the control plane.

Meanwhile, in the present disclosure, DSCP value information can be used with the same meaning as DSCP value or DSCP information, and the DSCP value considering the network type and the DSCP value of the network type can be used interchangeably with the same meaning.

FIG. 1 is a diagram illustrating a network structure and interface of a 5G system according to one embodiment of the present disclosure.

A network entity included in the network structure of the 5G system of Fig. 1 may include a network function (NF) depending on the system implementation.

Referring to FIG. 1, the network structure of a 5G system (100) may include various network entities. For example, the 5G system (100) may include an authentication server function (AUSF) entity (108), an access and mobility management function (AMF) entity (103), a session management function (SMF) entity (105), a policy control function (PCF) entity (106), an application function (AF) entity (107), a unified data management (UDM) entity (109), a data network (DN) (110), a network exposure function (NEF) entity (113), a network slicing selection function (NSSF) entity (114), a user plane function (UPF) entity (104), and a (radio) access network: (R)AN)(102), or a terminal, for example, a user equipment (UE)(101).

Each NF entity of the 5G system (100) supports the following functions.

AUSF (108) processes and stores data for authentication of UE (101).

AMF (103) provides functions for access and mobility management per UE, and one UE can basically be connected to one AMF. Specifically, the AMF (103) provides signaling between CN nodes for mobility between 3GPP access networks, termination of a radio access network (RAN) CP interface (i.e., N2 interface), termination of non access stratum (NAS) signaling (N1), NAS signaling security (NAS ciphering and integrity protection), AS security control, registration management (registration area management), connection management, idle mode UE reachability (including control and performance of paging retransmission), mobility management control (subscription and policy), intra-system mobility and inter-system mobility support, support for network slicing, SMF selection, lawful intercept (for AMF events and interfaces to the LI system), provision for forwarding of session management (SM) messages between the UE and the SMF, transparent proxy for routing SM messages, access authentication, access authorization including roaming authorization check. The AMF entity (103) supports functions such as authorization, provision of SMS message transmission between the UE and the SMSF, security anchor function (SAF), and/or security context management (SCM). Some or all of the functions of the AMF entity (103) may be supported within a single instance of an AMF entity.

DN (110) means, for example, an operator service, Internet access, or a third party service. DN (110) transmits a downlink protocol data unit (PDU) to UPF entity (104) or receives a PDU transmitted from UE (101) from UPF entity (104).

The PCF entity (106) receives information about packet flow from the application server and provides a function to determine policies such as mobility management and session management. Specifically, the PCF entity (106) supports functions such as supporting a unified policy framework for controlling network operations, providing policy rules so that control plane function entity(s) (e.g., AMF entity, SMF entity, etc.) can enforce the policy rules, and implementing a front end for accessing related subscription information for policy determination in a user data repository (UDR).

The SMF entity (105) provides a session management function, and when a UE (101) has multiple sessions, each session can be managed by a different SMF entity. Specifically, the SMF entity (105) supports functions such as session management (e.g., session establishment, modification, and termination, including tunnel maintenance between the UPF entity (104) and (R)AN (102) nodes), UE IP address allocation and management (optionally including authentication), selection and control of UP capabilities, setting up traffic steering to route traffic from the UPF entity (104) to the appropriate destination, termination of the interface to policy control functions, enforcement of the control portion of policies and quality of service (QoS), lawful intercept (for SM events and interfaces to the LI system), termination of the SM portion of NAS messages, downlink data notification, initiation of AN specific SM information (delivered to the (R)AN (102) via the N2 via the AMF entity (103)), determination of the session and service continuity (SSC) mode of the session, roaming functions, etc. Some or all of the functions of an SMF entity (105) may be supported within a single instance of an SMF entity.

The UDM entity (109) stores user subscription data, policy data, etc. The UDM entity (109) may include at least one of two parts: an application front end (FE) and a user data repository (UDR).

An FE may include a UDM FE responsible for location management, subscription management, credential processing, etc., and a PCF entity responsible for policy control. The UDR stores data required for the functions provided by the UDM-FE and policy profiles required by the PCF entity. The data stored in the UDR includes user subscription data and policy data, including subscription identifiers, security credentials, access and mobility related subscription data, and session related subscription data. The UDM-FE accesses the subscription information stored in the UDR and supports functions such as authentication credential processing, user identification handling, access authentication, registration/mobility management, subscription management, and SMS management.

The UPF entity (104) forwards a downlink PDU received from the DN (110) to the UE (101) via the (R)AN (102), and forwards an uplink PDU received from the UE (101) via the (R)AN (102) to the DN (110). Specifically, the UPF entity (104) supports functions such as an anchor point for intra/inter RAT (radio access technology) mobility, an external PDU session point for interconnection to the Data Network, a user plane portion of packet routing and forwarding, packet inspection and policy rule enforcement, an uplink classifier to support lawful intercept, traffic usage reporting, and routing of traffic flows to the Data Network, a branching point to support multi-homed PDU sessions, QoS handling for the user plane (e.g., packet filtering, gating, uplink/downlink rate enforcement), uplink traffic validation (service data flow (SDF) to QoS flow mapping), transport level packet marking in uplink and downlink, downlink packet buffering, and downlink data notification triggering. Some or all of the functions of a UPF entity (104) may be supported within a single instance of a UPF.

The AF entity (107) interacts with the 3GPP core network to provide services (e.g., supporting functions such as application impact on traffic routing, access to network capability exposure, and interaction with the policy framework for policy control).

(R)AN(102) is a general term for a new radio access network that supports both evolved E-UTRA, an evolved version of 4G radio access technology, and new radio (NR) technology (e.g., gNB).

The gNB provides functions for radio resource management (i.e., radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources to the UE in uplink/downlink (i.e., scheduling), IP (internet protocol) header compression, encryption and integrity protection of user data streams, selection of an AMF upon attachment of the UE if routing to the AMF is not determined from the information provided to the UE, routing of user plane data to UPF(s), routing of control plane information to the AMF, connection setup and teardown, scheduling and transmission of paging messages (originating from the AMF), scheduling and transmission of system broadcast information (originating from the AMF or operating and maintenance (O&M)), measurement and measurement reporting setup for mobility and scheduling, transport level packet marking in uplink, session management, support for network slicing, QoS flows. It supports functions such as mapping to management and data radio bearers, support for UEs in inactive mode, distribution of NAS messages, NAS node selection, radio access network sharing, dual connectivity, and tight interworking between NR and E-UTRA.

UE (101) means a user device. The user device may be referred to as a terminal, mobile equipment (ME), mobile station (MS), etc. In addition, the user device may be a portable device such as a laptop, a mobile phone, a personal digital assistant (PDA), a smart phone, a multimedia device, etc., or may be a non-portable device such as a personal computer (PC) or a vehicle-mounted device.

The NEF (113) provides a means to securely expose services and capabilities provided by 3GPP network functions, for example, 3rd party, internal exposure/re-exposure, application functions, Edge Computing. The NEF (113) receives information from other NF (s) (based on the exposed capability(s) of the other NF (s)). The NEF (113) may store the received information as structured data using a standardized interface to a data storage network function. The stored information may be re-exposed to other NF entity (s) and AF entity (s) by the NEF entity (113) and may be used for other purposes, such as analysis.

NRF (115) supports the service discovery function. It receives an NF discovery request from an NF instance and provides information on the discovered NF instance to the NF instance. It also maintains available NF instances and the services they support.

Meanwhile, for convenience of explanation, FIG. 1 illustrates a reference model for a case where a UE (101) accesses one DN (110) using one PDU session, but the present disclosure is not limited thereto.

A UE (101) can access two or more (e.g., local and central) data networks simultaneously using multiple PDU sessions. In this case, two or more SMFs can be selected for different PDU sessions. However, each SMF can have the ability to control both local UPF and central UPF within a PDU session.

Additionally, the UE (101) may simultaneously access two or more (i.e., local and central) data networks provided within a single PDU session.

In the 3GPP system, a conceptual link connecting NFs within a 5G system is defined as a reference point. As an example, the reference point(s) included in the 5G system (100) of Fig. 1 are as follows.

- N1: Reference point between UE (101) and AMF (103)

- N2: Reference point between (R)AN(102) and AMF(103)

- N3: Reference point between (R)AN(102) and UPF(104)

- N4: Reference point between SMF(105) and UPF(104)

- N5: Reference point between PCF (106) and AF (107)

- N6: Reference point between UPF (104) and DN (110)

- N7: Reference point between SMF(105) and PCF(106)

- N8: Reference point between UDM (109) and AMF (103)

- N9: Reference point between two core UPFs (104)

- N10: Reference point between UDM(109) and SMF(105)

- N11: Reference point between AMF(103) and SMF(105)

- N12: Reference point between AMF(103) and AUSF(108)

- N13: Reference point between UDM(109) and AUSF(108)

- N14: Reference point between two AMFs (103)

- N15: Reference point between PCF and AMF for non-roaming scenarios, reference point between PCF and AMF in visited network for roaming scenarios.

FIG. 2 is a diagram illustrating an operation of transmitting information for distinguishing packets transmitted by a tethered device to a terminal in a wireless communication system according to one embodiment of the present disclosure.

Referring to FIG. 2, the PCF may receive tethered device related information from the AF in order to support a service using a tethered device according to the policy of the service provider. The tethered device related information may include at least one of a tethered device support indication, a tethered device connection type, service type information transmitted from the tethered device (Media information (e.g. audio or video, etc.) and DSCP value information by network type).

The above tethered device related information may be included in the AFsessionwithQoS message, and may be information that AF transmits to PCF via NEF. If the service using the tethered device is an XR service, AF may include the tethered device related information in the Protocol description that transmits media related information in the service flow related to the PDU set.

According to one embodiment of the present disclosure, the PCF can determine whether to support a service for distinguishing packets transmitted by the tethered device to the terminal based on the tethered device related information transmitted from the AF. The PCF can allocate appropriate QFI information based on service related media information in the Protocol description to support a service using the tethered device based on the information transmitted from the AF, and can include this in the PCC (Policy and Charging Control) rule related information together with the tethered device related information and transmit it to the SMF.

According to one embodiment of the present disclosure, when support for service differentiation operation between packets based on DSCP information is required within a 5GC network according to settings of a service provider and a network provider, PCC rule related information may include information related to instructions for a DSCP re-marking operation.

According to one embodiment of the present disclosure, an SMF, which receives a PCC rule including tethered device-related information for supporting a service using a QFI and a tethered device, considering characteristics of packets constituting a service from a PCF, may generate classification information (e.g., a DSCP mapping table between QFI and tethered device network (e.g., Wi-Fi)) for distinguishing packets transmitted by the tethered device to a terminal. The SMF may generate a DSCP value considering service characteristics of each network type between the terminal and the tethered device based on the tethered device-related information. If the SMF cannot generate the DSCP value considering the service characteristics of each network type between the terminal and the tethered device, the SMF may receive the corresponding DSCP information from the AF. In addition, the SMF may generate DSCP information considering service characteristics within a 5GC network based on 5QI (5G QoS Identifier) information received from the PCF.

According to one embodiment of the present disclosure, when distinguishing packet-specific service characteristics based on DSCP values in a 5GC network, mapping information between a DSCP value considering a 5GC network and a DSCP value considering a network type between a terminal and a tethered device (e.g. a DSCP mapping table between 5GC and a tethered device network (e.g. Wi-Fi)) can be generated.

According to one embodiment of the present disclosure, when a service for distinguishing packets based on DSCP information in different networks is used, a DSCP remarking operation can be performed based on mapping information of DSCP values generated by considering service characteristics of each network in an intermediate network entity (e.g., UE and/or UPF) in different networks. For example, if a terminal and a tethered device are connected to a wifi network and the terminal forwards a packet received from the tethered device to a 5GC network, the UE can remark the DSCP value in the packet header as a DSCP value considering 5GC that is mapped to a DSCP value considering Wifi.

According to one embodiment of the present disclosure, the SMF can transmit mapping information between a DSCP value considering a 5GC network and a DSCP value considering a network type between a terminal and a tethered device (e.g. a DSCP mapping table between 5GC and tethered device network (e.g. Wi-Fi)) or QoS flow mapping information considering a network type between a terminal and a tethered device (e.g. a DSCP mapping table between QFI and tethered device network (e.g. Wi-Fi)) to the NG-RAN and the terminal.

According to one embodiment of the present disclosure, in a case where packets transmitted from a UPF to an application server are transmitted to another network according to a policy of a service provider or a network provider by using a service for distinguishing packets based on DSCP information within a 5GC network, or when it is decided to restore a DSCP remarking operation performed by an existing UE, a DSCP remarking operation of restoring the DSCP value or resetting it to a DSCP value considering a new network type can be performed by transmitting mapping information between a DSCP value considering a 5GC network and a DSCP value considering a network type to the UPF. In this case, the SMF can request the DSCP remarking operation by transmitting a DSCP remarking support indication and mapping information between 5GC and DSCP values of different network types, etc., to the UPF within the N4 rule.

According to one embodiment of the present disclosure, the terminal may perform an operation of mapping packets transmitted from the tethered device to QoS flows considering service characteristics based on mapping information between a DSCP value considering a 5GC network transmitted from an SMF and a DSCP value considering a network type between the terminal and a tethered device (e.g., a DSCP mapping table between 5GC and tethered device network (e.g., Wi-Fi)) or QoS flow mapping information considering a network type between the terminal and the tethered device (e.g., a DSCP mapping table between QFI and tethered device network (e.g., Wi-Fi)), or resetting the DSCP value to a DSCP value considering a 5GC network type according to settings of a service provider, etc.

According to one embodiment of the present disclosure, the UPF receives at least one of mapping information between a DSCP value considering a 5GC network transmitted from an SMF and a DSCP value generated based on a network type to be used in remarking, mapping information between a DSCP value considering a 5GC network type and a QFI value, or a DSCP remarking indicator, and performs an operation of distinguishing packets transmitted to the UPF based on the DSCP value or the QFI value and remarking packets output from the UPF with an appropriate DSCP value.

FIG. 3 is a flowchart illustrating a system composed of different network types and related operations in a wireless communication system according to one embodiment of the present disclosure.

According to one embodiment of the present disclosure, when a service for distinguishing packets based on DSCP information in different networks (Network #1 or Network #2 or Network #3) is used, an intermediate network entity (e.g., UE (Network #1 and Network #2) and/or UPF (Network #2 and (Network #1 or Network #3)) of the different networks can perform a DSCP remarking operation based on mapping information of DSCP values generated in consideration of service characteristics of each network. For example, if a terminal and a tethered device are connected to a wifi network (Network #1) and the terminal transfers a packet received from the tethered device to a 5GC network (Network #2), the UE can remark the DSCP value in the packet header as the DSCP value of 5GC (Network #2) that is mapped to the DSCP value of Wifi (Network #1).

According to one embodiment of the present disclosure, if packets transmitted by the UPF to an application server based on a policy of a service provider or a network provider using a service that distinguishes packets based on DSCP information in a 5GC network (Network #2) are transmitted to another network (Network #3), or if it is decided to restore the DSCP value according to the DSCP remarking operation performed by the existing UE to the DSCP value of the network #1, the SMF can perform a DSCP remarking operation of restoring the DSCP value in the UPF or resetting it to a DSCP value considering the new network #3 type by transmitting mapping information between the DSCP values considering the 5GC network (Network #2) and the network #1 type to the UPF. In this case, the SMF can request the DSCP remarking operation by transmitting a DSCP remarking support indication and mapping information between the DSCP values of 5GC (Network #2) and different network types (Network #1 or Network #3) to the UPF within the N4 rule.

According to one embodiment of the present disclosure, the terminal may perform an operation of mapping packets transmitted from the tethered device to QoS flows considering service characteristics based on mapping information between DSCP values considering a type of a 5GC network (Network #2) transmitted from an SMF and a network (Network #1) connected to the tethered device (e.g., DSCP mapping table between 5GC and tethered device network (e.g., Wi-Fi)) or QoS flow mapping information considering a type of a network (Network #1) connected to the tethered device (e.g., DSCP mapping table between QFI and tethered device network (e.g., Wi-Fi)), or an operation of resetting the DSCP value to a DSCP value considering a type of a 5GC network (Network #2) according to settings of a service provider, etc.

According to one embodiment of the present disclosure, the UPF receives at least one of mapping information of a DSCP value generated based on a 5GC network (Network #2) transmitted from an SMF and a network type (Network #1 or Network #3) to be used for remarking, mapping information between a DSCP value and a QFI value considering the 5GC network (Network #2) type, or a DSCP remarking indicator, and performs an operation of distinguishing packets transmitted to the UPF based on the DSCP value or the QFI value and remarking packets output from the UPF with an appropriate DSCP value.

FIG. 4 is a flowchart for transmitting information related to the performance of an operation for distinguishing packets using information such as DSCP values based on network type and service characteristic information between a tethered device and a terminal in a wireless communication system according to an embodiment of the present disclosure. At this time, FIG. 4 may include FIG. 4A, FIG. 4B, or FIG. 4C.

In step 401, the AF may determine service support based on service data flow using a tethered device connected to the terminal according to the user's selection or the service provider's policy.

In step 402, the AF may transmit tethered device-related information including at least one of information on a network type (e.g. wifi or Bluetooth etc.) between the terminal and the tethered device, a type of service data flow that the terminal transmits to or receives from the tethered device (e.g. audio, video etc.), a direction of the tethered device service flow (e.g. Uplink or Downlink traffic), and DSCP information considering the network and service type between the terminal and the tethered device (DSCP value for considering tethered device network type and/or service(media) type) to the NEF using an AF session-related QoS requirements (AFsessionWithQoS) message.

In step 403, the NEF may transmit tethered device related information including at least one of information regarding a network type (e.g. wifi or Bluetooth etc.) between the terminal and the tethered device received from the AF, a type of service data flow (e.g. audio, video etc.) that the terminal transmits to or receives from the tethered device, a direction of tethered device service flow (e.g. Uplink or Downlink traffic), and DSCP information considering the network and service type between the terminal and the tethered device (DSCP value for considering tethered device network type and/or service(media) type) to the PCF entity using a PolicyAuthorization message.

In step 404, the PCF can determine whether to accept an operation request for supporting a service considering the tethered device based on the tethered device-related information and service characteristic information received from the AF. If the PCF can accept the tethered device-related service request received from the AF, the PCF can perform a PCC rule creation/update operation and transmit response information related to the service request to the AF through steps 405 and 406.

If the PCF decides to provide a handling service of a service data flow considering a tethered device in step 404, it may allocate 5QI information reflecting each media characteristic in the service flow, and request generation of DSCP information considering the type and media characteristics of the network between the terminal and the tethered device in relation to the service data flow transmitted from the tethered device to the terminal or from the tethered device to the terminal, or determine a PCC rule update based on DSCP information considering the type and media characteristics of the network connected to the tethered device received from the AF.

In step 407, the PCF may transmit an updated PCC rule including at least one of 5QI information related to service data flow transmitted from the terminal to the tethered device or received from the tethered device, a request for generation of DSCP information considering the type and media characteristics of the network between the terminal and the tethered device, and type and media characteristic information of the network connected to the tethered device, DSCP information considering the type and media characteristics of the network connected to the tethered device received from the AF, or direction information related to the tethered device, to the SMF through a session policy control update notification (Npcf_SMPolicyControl_UpdateNotify) request message.

In step 408, the SMF, which has received a PCC rule including tethered device-related information for supporting a service using a QFI and a tethered device, which is generated by considering the characteristics of packets composing the service from the PCF, can generate DSCP values of packets transmitted from or to the tethered device by considering the service characteristics of each network type between the terminal and the tethered device based on the tethered device-related information.

In step 409, the SMF may generate classification information (e.g. DSCP mapping table between QFI and tethered device network (e.g. Wi-Fi)) for distinguishing packets transmitted from the tethered device to the terminal based on information related to DSCP values of packets received from or transmitted to the tethered device and QFI information considering the service type of the packets. If the SMF cannot generate the DSCP value considering the service characteristics of each network type between the terminal and the tethered device, step 408 may be omitted and the DSCP information transmitted from the AF may be used.

In steps 410 and 411, the SMF may perform an N4 rule update operation based on the PCC rule received from the PCF in step 407. The SMF may transmit UPF operation-related update information to the UPF through an N4 session Modification request message and receive a result message for the update request from the UPF.

According to one embodiment of the present disclosure, with respect to downlink packets transmitted to a tethered device, the SMF may map the DSCP values of each packet to a packet header and transmit them to the tethered device based on a DSCP value that considers service characteristics of each network type. A terminal that receives packets marked with DSCP information based on the tethered device information may transmit each packet to an appropriate tethered device based on the information. In order to support DSCP marking of the downlink packets, the SMF may transmit a DSCP marking indicator and a DSCP marking value that considers an appropriate tethered device for each QFI.

According to one embodiment of the present disclosure, if the UPF does not support DSCP value marking of downlink packets transmitted to a tethered device according to the settings of the terminal or service provider, the SMF can transmit DSCP marking indicator information to the terminal so that the terminal performs the corresponding DSCP marking operation.

In step 412, the SMF may forward an N1 SM container including mapping information or information for distinguishing downlink packets, which are set to be mapped to appropriate QFIs using DSCP information of uplink packets in the service data flow transmitted from the tethered device based on the PCC rule received from the PCF in step 407, to the AMF via an N1N2MessageTransfer (Namf_Communication_N1N2MessageTransfer) message.

At step 413, AMF may forward N2 SM information and N1 SM container including updated QFI and QoS rule, QoS profile, etc. to RAN using N2 message.

At this time, the QFI and QoS rule, or QoS profile, etc. may be updated to support a tethered device container and a tethered device packet handling service that includes mapping information set to be mapped to an appropriate QFI using the DSCP information of the uplink packets in the service data flow transmitted from the tethered device received in step 412, or information for distinguishing downlink packets.

In step 414, the RAN may transmit to the UE an N1 SM container including updated QoS rules, etc. to support packet segmentation operation and QFI mapping operation using DSCP information of uplink packets in the service data flow transmitted from the tethered device to the terminal. At this time, the tethered device container may also include information for segmenting downlink packets.

AMF may receive UE and RAN service related response messages from RAN in step 415 in relation to the information delivered to RAN in step 413.

In step 416, AMF may perform an operation to update session-related information by forwarding the service-related response message received in step 415 to SMF.

At step 417, the SMF may forward a message corresponding to message 416 to the AMF, in relation to the message received from the AMF at step 416.

FIG. 5 is a flowchart for transmitting information related to an operation for distinguishing packets based on information such as a DSCP value generated based on network type and service characteristic information between a tethered device and a terminal received from an AF in a wireless communication system according to an embodiment of the present disclosure and a packet remarking operation for supporting different networks using DSCP information. In this case, FIG. 5 may include FIG. 5A, FIG. 5B, or FIG. 5C.

Referring to FIG. 5, in order to request a tethered device-based service in relation to a specific service flow, the AF may transmit tethered device-related information including at least one of a tethered device support indication, service-related information such as codecs of packets of each media type transmitted to the tethered device, network type-related information between the tethered device and the terminal, packet direction-related information, and DSCP value-related information considering the tethered device, to the PCF using a protocol descriptor or by creating a separate container.

In addition, AF may transmit tethered device related information to PCF when 5GC uses packet classification operation based on DSCP considering multiplexed service data flow of information of packets transmitted from tethered devices transmitted to different networks, or when it can be known that the packet is transmitted to a network using DSCP. At this time, the tethered device related information may include a remarking request indicator (DSCP remarking support indicator) requesting remarking operation of the packet, and network entity information (e.g. UPF) that will perform remarking operation according to the direction of the packet (e.g. Uplink or downlink).

The PCF can determine whether to accept the request based on the remarking request indicator received from the AF or information related to generation of DSCP value considering the network type between the terminal and the tethered device. If the PCF can accept the service request, it can transmit to the SMF an indicator (DSCP value based tethered device traffic identification supporting indicator) and related information for performing a packet identification operation for the terminal to transmit to the tethered device using the DSCP value received from the AF or based on the tethered device-related information from the SMF when creating/updating a PCC rule. If the PCF cannot support QoS flow handling using the DSCP value of the packet transmitted from the tethered device to the terminal based on the service requirements received from the AF, it can transmit a rejection message for the request to the AF in response to the AF requirements-related message.

In step 501, the AF determines a tethering device-based service of a specific service flow and receives device-related information including the network type of the tethered device connected from the terminal and the media type of packets serviced by the tethered device, to determine whether to request the corresponding service.

In step 502, based on the matters determined in step 501, the AF may transmit to the NEF, using a protocol descriptor or by creating a separate container, tethered device-related information including at least one of a tethered device support indication, service-related information such as codecs of packets of each media type transmitted to the tethered device, network type information between the tethered device and the terminal, packet direction-related information, and DSCP value-related information considering the tethered device, in order to request a tethered device-based service of a specific service flow.

In addition, when the AF uses a packet classification operation based on DSCP in 5GC considering a multiplexed service data flow of information of packets transmitted from a tethered device transmitted to different networks, or when it can be known that the packet is transmitted to a network using DSCP, the tethered device related information can be transmitted by including it in an AF session related QoS requirement (AFsessionWithQoS) message transmitted from the AF to the NEF entity. At this time, the tethered device related information can include a remarking request indicator (DSCP remarking support indicator) requesting a remarking operation of the packet, and information on a network entity (e.g. UPF) that will perform the remarking operation according to the direction of the packet (e.g. Uplink or downlink).

In step 503, the NEF may transmit tethered device related information including at least one or more of the following information: network type information (e.g. wifi or Bluetooth etc.) between tethered devices transmitted from the AF, type of service data flow transmitted or received by the tethered device (e.g. audio, video etc.), direction of tethered device service flow (e.g. Uplink or Downlink traffic), DSCP information considering network and service type between the terminal and the tethered device (DSCP value for considering tethered device network type and/or service(media) type), or DSCP remarking support indicator and direction of the corresponding packet (e.g. Uplink or downlink), to the PCF entity using a PolicyAuthorization message.

In step 504, the PCF can determine whether to accept an operation request for supporting a service considering the tethered device based on the tethered device-related information and service characteristic information received from the AF. If the PCF can accept the tethered device-related service request received from the AF, the PCF can perform a PCC rule creation/update operation and transmit response information related to the service request to the AF through steps 505 and 506.

If the PCF decides to provide a handling service of a service data flow considering a tethered device in step 504, the PCF may allocate 5QI information reflecting each media characteristic in the service flow, and request generation of DSCP information considering the type and media characteristics of the network between the terminal and the tethered device in relation to the service data flow that the tethered device transmits to the terminal or the tethered device receives from the terminal, or determine PCC rule update based on the DSCP information considering the type and media characteristics of the network connected to the tethered device received from the AF. The PCF may determine whether to accept the request based on the remarking request indicator received from the AF or the information related to generation of a DSCP value considering the network type between the terminal and the tethered device, and if the PCF can accept the service request, it may transmit response information related to the service request to the AF through steps 505 and 506.

In step 507, the PCF may transmit an updated PCC rule including at least one or more of 5QI information related to service data flow transmitted from the terminal to the tethered device or received from the terminal, a request for generation of DSCP information considering the type and media characteristics of the network between the terminal and the tethered device, type and media characteristic information of the network connected to the tethered device, DSCP information considering the type and media characteristics of the network connected to the tethered device received from the AF, or direction information related to the tethered device, to the SMF through a session policy control update notification (Npcf_SMPolicyControl_UpdateNotify) request message.

Additionally, if there is a service for distinguishing packets using separate DSCP information within a 5GC network such as multiplexing from AF, the updated PCC rule may include an indicator for a DSCP remarking operation in the terminal or UPF. For example, in a service configured with networks including different networks #1, #2, and #3, where network #1 is a terminal and a tethered device connected to the terminal, network #2 is a 5GC, and network #3 is a separate network or a service provider's request for a service to distinguish packets using a DSCP value considering network #1 as shown in FIG. 3, the PCF may perform an update operation to include indicator information for a remarking operation in the terminal and UPF in the PCC rule.

If the service request information related to distinguishing packets using separate DSCP between 5GC and AS is not transmitted from AF, PCF can perform an update operation to include indicator information for remarking operation in the PCC rule at terminals other than UPF.

If the service using tethered devices is a downlink packet-related service, a separate remarking operation can be performed on the UPF or terminal to distinguish it from the service connected to the tethered device network (network #1) in 5GC that uses a service to distinguish multiplexed packets based on DSCP values.

If AS considers tethered devices and marks packets with DSCP values considering tethered devices in a separate packet header and transmits them to UPF, UPF can perform an operation of remarking the DSCP values considering the tethered device network as DSCP values within the 5GC network. Thereafter, the terminal can remark the DSCP values of packets marked with DSCP values based on the 5GC network information input to the terminal as DSCP values considering the tethered device's network and transmit them to the tethered device.

If a packet marked with DSCP information is not transmitted in AS considering the network of the tethered device with UPF, UPF can perform a DSCP value marking operation in the header of the packet with a DSCP value generated based on information such as 5QI and ARP of the 5GC network, and then perform an operation in which the terminal remarks with a DSCP value considering the network information of the tethered device before finally transmitting to the tethered device.

In step 508, the SMF, which has received a PCC rule including tethered device-related information for supporting a service using a QFI and a tethered device, considering the characteristics of packets composing the service from the PCF, can generate DSCP values for packets received from or transmitted to the tethered device, considering the service characteristics of each network type between the terminal and the tethered device based on the tethered device-related information.

In addition, a DSCP information generation indicator for generating a DSCP value considering 5GC network information and a DSCP value for distinguishing packets in 5GC can be generated based on information (e.g. 5QI and ARP) used to distinguish packets during marking, and if a specific DSCP value is currently being used in another service of the 5GC network, the SMF can generate a DSCP value excluding the DSCP value used in the other service. In addition, the SMF can support generation of a DSCP value considering service characteristics of each network type between a separate terminal and a tethered device from the AF. If the SMF cannot generate a DSCP value considering the tethered device network type, the SMF can use the DSCP information received from the AF.

In step 509, the SMF may generate classification information (e.g. DSCP mapping table between 5GC and tethered device network (e.g. Wi-Fi)) for distinguishing packets transmitted by the tethered device to the terminal based on the DSCP value information generated based on the network information in the 5GC generated in step 508, which takes into account the DSCP value-related information of packets transmitted from or to the tethered device and the service type of the packets.

In steps 510 and 511, the SMF can perform an N4 rule update operation based on the PCC rule received from the PCF in step 507. The SMF can transmit UPF operation-related update information to the UPF through an N4 session Modification request message and receive a result message for the update request from the UPF.

According to one embodiment of the present disclosure, with respect to downlink packets transmitted to a tethered device, the SMF may map the DSCP values of each packet to a packet header based on a DSCP value that considers service characteristics of each network type and transmit them to the tethered device. A terminal that receives packets marked with DSCP information based on the tethered device information may transmit each packet to an appropriate tethered device based on the information. In order to support DSCP marking of the downlink packets, the SMF may transmit a DSCP marking indicator and a DSCP marking value that considers an appropriate tethered device for each QFI.

According to one embodiment of the present disclosure, if the UPF does not support DSCP value marking of downlink packets transmitted to a tethered device according to the settings of the terminal or service provider, the SMF can transmit DSCP marking indicator information to the terminal so that the terminal performs the corresponding DSCP marking operation.

According to one embodiment of the present disclosure, when packets are distinguished based on DSCP information in different networks, a remarking operation of DSCP values can be performed at the end between each network in order to support connection between the corresponding services. For example, with respect to the case of FIG. 3, in order to support a service of distinguishing packets considering DSCP values considering different network types in UPF, PCF can transmit a DSCP remarking operation indicator to UPF through SMF. The UPF that has received the operation indicator can distinguish packets transmitted from 5GC (N3) or AS (N6) based on DSCP values and remark the corresponding DSCP values as DSCP values for supporting an appropriate new network type. The DSCP value for the remarking can be transmitted through SMF.

In step 512, the SMF may forward an N1 SM container including at least one of mapping information, a DSCP remarking indicator, or directionality information configured to map packets in a service data flow transmitted from a tethered device to a DSCP value generated based on information in an appropriate 5GC, to the AMF via an N1N2MessageTransfer (Namf_Communication_N1N2MessageTransfer) message.

In step 513, the AMF may transmit the N2 SM information and the N1 SM container to the RAN using the N2 message. At this time, the N2 SM information may include a tethered device container including at least one of mapping information, a DSCP remarking indicator, or directionality information configured to be mapped to a DSCP value generated based on information within an appropriate 5GC, and updated QFI and QoS rules, QoS profiles, etc. to support a tethered device packet handling service. At step 514, the RAN may transmit the N1 SM container including updated QoS rules, etc. to support a packet segmentation operation using DSCP information and a QFI mapping operation of uplink packets in a service data flow transmitted from the tethered device to the UE. At this time, the tethered device container may also include information for segmenting downlink packets.

AMF may receive UE and RAN service related response messages from RAN in step 515 in relation to the information delivered to RAN in step 513.

In step 516, AMF may perform an operation to update session-related information by forwarding the service-related response message received in step 515 to SMF.

At step 517, the SMF may forward a message corresponding to message 516 to the AMF, in relation to the message received from the AMF at step 516.

FIG. 6 is a flowchart for transmitting information related to performing an operation for distinguishing packets based on information such as a DSCP value generated based on network type and service characteristic information between a tethered device and a terminal received from a terminal in a wireless communication system according to an embodiment of the present disclosure, and performing a packet remarking operation to support distinguishing packets based on DSCP information in different networks. In this case, FIG. 6 may include FIG. 6A, FIG. 6B, or FIG. 6C.

Referring to FIG. 6, in order to request a tethered device-based service of a specific service flow, a terminal may transmit tethered device-related information including at least one of a tethered device support indication, service-related information such as codecs of packets of each media type transmitted to the tethered device, network type-related information between the tethered device and the terminal, packet direction-related information, and DSCP value-related information considering the tethered device, to the SMF using a protocol descriptor or by creating a separate container.

In addition, AF may transmit tethered device related information to PCF when 5GC uses packet classification operation based on DSCP considering multiplexed service data flow of information of packets transmitted from tethered devices transmitted to different networks, or when it can be known that the packet is transmitted to a network using DSCP. At this time, the tethered device related information may include a remarking request indicator (DSCP remarking support indicator) requesting remarking operation of the packet, and network entity information (e.g. UPF) that will perform remarking operation according to the direction of the packet (e.g. Uplink or downlink).

The SMF determines whether to accept the request based on related information such as generation of DSCP value considering the network type between the terminal and the tethered device received from the terminal. If the SMF can accept the service request, it can transmit a PDU session change request acceptance message to the terminal. The PCF can transmit an indicator (DSCP value based tethered device traffic identification supporting indicator) and related information to the SMF to perform a packet identification operation for the terminal to transmit to the tethered device by using the DSCP value when generating/updating the PCC rule based on the information received from the AF and SMF.

In step 601, the terminal may generate tethered device-related information including at least one of a tethered device support indication and service-related information such as codecs of packets of each media type transmitted to the tethered device, network type information between the tethered device and the terminal, packet direction-related information, or DSCP value information considering the tethered device, and transmit the information to the AMF in order to request a tethered device-based service of a specific service flow.

In step 602, the AMF may transmit tethered device related information including at least one or more of the following information: network type information (e.g. wifi or Bluetooth etc.) between the tethered devices received from the terminal, type of service data flow transmitted or received by the tethered device (e.g. audio, video etc.), direction of tethered device service flow (e.g. uplink or downlink traffic), DSCP information considering network and service type between the terminal and the tethered device (DSCP value for considering tethered device network type and/or service(media) type), or DSCP remarking support indicator and direction of the corresponding packet (e.g. uplink or downlink), to the SMF entity through a session management context update (Nsmf_PDUSession_UpdateSMContext) message of the PDU session.

In step 603, the SMF may perform a session management policy control update operation to support a service considering the tethered device based on the tethered device-related information and service characteristic information received from the AMF.

In step 604, if the PCF can accept the tethered device related service request received from the terminal, it can perform a PCC rule creation/update operation and forward the PCC rule to the SMF via a session management policy control update response message.

If the PCF decides to provide a handling service of a service data flow considering a tethered device in step 504, it may allocate 5QI information reflecting each media characteristic in the service flow, and request generation of DSCP information considering the network type and media characteristics between the terminal and the tethered device in relation to the service data flow that the tethered device transmits to the terminal or the tethered device receives from the terminal, or determine PCC rule update based on DSCP information considering the type and media characteristics of the network connected to the tethered device received from the terminal.

The PCF determines whether to accept the request based on the remarking request indicator received from the AF or the information related to generation of the DSCP value considering the network type between the terminal and the tethered device, and if the service request can be accepted, it can perform a PCC rule update operation including the DSCP remarking indicator and related information.

In step 605, the PCF may transmit an updated PCC rule including at least one of 5QI information related to service data flow transmitted from the terminal to the tethered device or received from the tethered device, a request for generation of DSCP information considering the type and media characteristics of the network between the terminal and the tethered device, and type and media characteristic information of the network connected to the tethered device, DSCP information considering the type and media characteristics of the network connected to the tethered device received from the AF, or direction information related to the tethered device, to the SMF through a session policy control update notification (Npcf_SMPolicyControl_UpdateNotify) request message.

Additionally, if there is a service for distinguishing packets using separate DSCP information within a 5GC network such as multiplexing from AF, the updated PCC rule may include an indicator for DSCP remarking operation in the terminal or UPF. For example, in a service configured with different networks #1, #2, and #3, where network #1 is a terminal and a tethered device connected to the terminal, network #2 is 5GC, and network #3 is a separate network or a service provider's request for a service to distinguish packets using a DSCP value considering network #1 as shown in FIG. 3, the PCF may perform an update operation to include indicator information for remarking operation in the terminal and UPF in the PCC rule.

If the service request information related to distinguishing packets using separate DSCP between 5GC and AS is not transmitted from AF, PCF can perform an update operation to include indicator information for remarking operation in the PCC rule at terminals other than UPF.

If the service using tethered devices is a downlink packet-related service, a separate remarking operation can be performed on the UPF or terminal to distinguish it from the service connected to the tethered device network (network #1) in 5GC that uses a service to distinguish multiplexed packets based on DSCP values.

If AS considers tethered devices and marks packets with DSCP values considering tethered devices in a separate packet header and transmits them to UPF, UPF can perform an operation of remarking the DSCP values considering the tethered device network as DSCP values within the 5GC network. Thereafter, the terminal can remark the DSCP values of packets marked with DSCP values based on the 5GC network information input to the terminal as DSCP values considering the tethered device's network and transmit them to the tethered device.

If a packet marked with DSCP information is not transmitted from AS to UPF considering the network of the tethered device, UPF can perform a DSCP value marking operation in the header of the packet with a DSCP value generated based on information such as 5QI and ARP of the 5GC network, and then perform an operation in which the terminal remarks with a DSCP value considering the network information of the tethered device before finally transmitting to the tethered device.

In step 606, the SMF, which has received a PCC rule including tethered device-related information for supporting a service using a QFI and a tethered device, considering the characteristics of packets composing the service from the PCF, can generate DSCP values for packets received from or transmitted to the tethered device, considering the service characteristics of each network type between the terminal and the tethered device based on the tethered device-related information.

In addition, a DSCP information generation indicator for generating a DSCP value considering 5GC network information and a DSCP value for distinguishing packets in 5GC can be generated based on information (e.g. 5QI and ARP) used to distinguish packets during marking, and if a specific DSCP value is currently being used by another service of the 5GC network, the SMF can generate a DSCP value excluding DSCP values not used by other services. In addition, the SMF can support generation of a DSCP value considering service characteristics of each network type between a separate terminal and a tethered device from the AF. If the SMF cannot generate a DSCP value considering the tethered device network type, the SMF can use the DSCP information received from the AF.

In step 607, the SMF may generate classification information (e.g. DSCP mapping table between 5GC and tethered device network (e.g. Wi-Fi)) for distinguishing packets transmitted by the tethered device to the terminal based on the DSCP value information generated based on the network information in the 5GC generated in step 606, which takes into account the service type of the packets and the DSCP value-related information of packets transmitted from or to the tethered device.

In steps 608 and 609, the SMF may perform an N4 rule update operation based on the PCC rule received from the PCF in step 605. The SMF may transmit UPF operation-related update information to the UPF through an N4 session Modification request message and receive a result message for the update request from the UPF.

According to one embodiment of the present disclosure, with respect to downlink packets transmitted to a tethered device, the UPF may map the DSCP values of each packet to a packet header based on a DSCP value that considers service characteristics of each network type and transmit them to the tethered device. A terminal that receives packets marked with DSCP information based on the tethered device information may transmit each packet to an appropriate tethered device based on the information. In order to support DSCP marking of the downlink packets, the SMF may transmit a DSCP marking value that considers a DSCP marking indicator and an appropriate tethered device for each QFI to the UPF.

According to one embodiment of the present disclosure, if the UPF does not support DSCP value marking of a downlink packet transmitted to a tethered device according to the settings of the terminal or service provider, DSCP marking indicator information can be transmitted from the SMF to the terminal so that the terminal performs the corresponding DSCP marking operation.

According to one embodiment of the present disclosure, when distinguishing packets based on DSCP information in different networks, a remarking operation of DSCP values can be performed at the end between each network to support connection between the corresponding services. For example, in order to support a service of distinguishing packets considering DSCP values considering different network types in UPF with respect to FIG. 3, PCF can transmit a DSCP remarking operation indicator to UPF through SMF. UPF that has received the operation indicator can distinguish packets transmitted from 5GC (N3) or AS (N6) based on DSCP values and remark the corresponding DSCP values as DSCP values for supporting an appropriate new network type. The DSCP value for the remarking can be transmitted through SMF.

In step 610, the SMF may forward an N1 SM container including at least one of mapping information, a DSCP remarking indicator, or directionality information configured to map packets in a service data flow transmitted from a tethered device to a DSCP value generated based on information in an appropriate 5GC, to the AMF via an N1N2MessageTransfer (Namf_Communication_N1N2MessageTransfer) message.

In step 611, the AMF may forward the N2 SM information and the N1 SM container to the RAN using an N2 message. At this time, the N2 SM information may include a tethered device container including at least one of mapping information configured to be mapped to a DSCP value generated based on information within an appropriate 5GC, a DSCP remarking indicator, or directionality information, and updated QFI and QoS rules, QoS profiles, etc. to support the tethered device packet handling service.

In step 612, the RAN may transmit to the UE an N1 SM container including updated QoS rules, etc., to support packet segmentation operation and QFI mapping operation using DSCP information of uplink packets in service data flows transmitted from the tethered device to the terminal. At this time, the tethered device container may also include information for segmenting downlink packets.

AMF may receive a service-related response message from RAN regarding the information delivered in step 612 in step 613.

In step 614, AMF may perform an operation to update session-related information by forwarding the service-related response message received in step 610 to SMF.

At step 615, the SMF may forward a message corresponding to message 614 to the AMF, in relation to the message received from the AMF at step 614.

The terminal can distinguish packets transmitted from the tethered device based on the tethered device-related information transmitted by the SMF by utilizing the DSCP value in the packet header. Additionally, packets transmitted to or received from the tethered device can be distinguished based on information such as tethered device network type + media type, QFI + tethered device network type, QFI + sub QoF flow ID, and sub QoF flow ID + tethered device network type.

FIG. 7 is a block diagram illustrating the structure of a terminal according to one embodiment of the present disclosure.

Referring to FIG. 7, a terminal according to an embodiment of the present disclosure may include a terminal receiving unit (700), a terminal transmitting unit (704), and a terminal processing unit (702). The terminal receiving unit (700) and the terminal transmitting unit (704) may be collectively referred to as a transceiver in the present disclosure. The transceiver unit may transmit and receive signals with a base station. The signals may include control information and data. To this end, the transceiver unit may be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and down-converts the frequency of a received signal. In addition, the transceiver unit may receive a signal through a wireless channel and output it to the terminal processing unit (702), and transmit a signal output from the terminal processing unit (702) through the wireless channel. The terminal processing unit (702) may control a series of processes so that the terminal may operate according to the above-described embodiment.

FIG. 8 is a block diagram illustrating the structure of an SMF entity according to one embodiment of the present disclosure.

Referring to FIG. 8, an SMF entity according to an embodiment of the present disclosure may include at least one of an SMF entity receiving unit (801), an SMF entity transmitting unit (805), and an SMF entity processing unit (803). The SMF entity receiving unit (801) and the SMF entity transmitting unit (805) may be collectively referred to as a transceiver in the present disclosure. The transceiver unit may transmit and receive signals with a terminal. The signals may include control information and data. The transceiver unit may receive a signal through a wired/wireless channel and output it to the SMF entity processing unit (803), and transmit the signal output from the SMF entity processing unit (803) through the wired/wireless channel. The SMF entity processing unit (803) may control a series of processes so that the SMF entity may operate according to the embodiment of the present disclosure described above.

FIG. 9 is a block diagram illustrating the structure of an AMF entity according to one embodiment of the present disclosure.

Referring to FIG. 9, an AMF entity according to an embodiment of the present disclosure may include at least one of an AMF entity receiving unit (901), an AMF entity transmitting unit (905), and an AMF entity processing unit (903). The AMF entity receiving unit (901) and the AMF entity transmitting unit (905) may be collectively referred to as a transceiver in the present disclosure. The transceiver may transmit and receive signals with a terminal. The signals may include control information and data. The transceiver may receive signals through a wired/wireless channel and output them to the AMF entity processing unit (903), and transmit signals output from the AMF entity processing unit (903) through the wired/wireless channel. The AMF entity processing unit (903) may control a series of processes so that the AMF entity may operate according to the embodiment of the present disclosure described above.

FIG. 10 is a block diagram illustrating the structure of a UPF entity according to one embodiment of the present disclosure.

Referring to FIG. 10, a UPF entity according to an embodiment of the present disclosure may include at least one of a UPF entity receiving unit (1001), a UPF entity transmitting unit (1005), and a UPF entity processing unit (1003). The UPF entity receiving unit (1001) and the UPF entity transmitting unit (1005) may be collectively referred to as a transceiver in the present disclosure. The transceiver unit may transmit and receive signals with a terminal. The signals may include control information and data. The transceiver unit may receive a signal through a wired/wireless channel and output it to the UPF entity processing unit (1003), and transmit a signal output from the UPF entity processing unit (1003) through the wired/wireless channel. The UPF entity processing unit (1003) may control a series of processes so that the UPF entity may operate according to the embodiment of the present disclosure described above.

Meanwhile, the order of description in the drawings explaining the method proposed in the present disclosure does not necessarily correspond to the order of execution, and the order of precedence may be changed or executed in parallel. Alternatively, the drawings explaining the method proposed in the present disclosure may omit some components and include only some components within the scope that does not harm the essence of the present disclosure.

The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

In the case of software implementation, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors in an electronic device. The one or more programs may include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specifications of the present disclosure.

These programs (software modules, software) may be stored in a random access memory, a non-volatile memory including a flash memory, a ROM (Read Only Memory), an Electrically Erasable Programmable Read Only Memory (EEPROM), a magnetic disc storage device, a Compact Disc-ROM (CD-ROM), a Digital Versatile Discs (DVDs) or other forms of optical storage devices, a magnetic cassette. Or, they may be stored in a memory composed of a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

Additionally, the program may be stored in an attachable storage device that is accessible via a communications network, such as the Internet, an Intranet, a Local Area Network (LAN), a Wide LAN (WLAN), or a Storage Area Network (SAN), or a combination thereof. The storage device may be connected to the device performing the embodiments of the present disclosure via an external port. Additionally, a separate storage device on the communications network may be connected to the device performing the embodiments of the present disclosure.

In the specific embodiments of the present disclosure described above, the components included in the present disclosure are expressed in the singular or plural form according to the specific embodiments presented. However, the singular or plural expressions are selected appropriately for the presented situation for the convenience of explanation, and the present disclosure is not limited to the singular or plural components, and even if a component is expressed in the plural form, it may be composed of the singular form, or even if a component is expressed in the singular form, it may be composed of the plural form.

Although the detailed description of the disclosure has described specific embodiments, it should be understood that various modifications may be made 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 claims described below, but also by equivalents of the claims.

Claims (1)

In a method for processing a control signal in a wireless communication system of a communication system,
A step of receiving a first control signal transmitted from a terminal;
A method characterized by comprising: a step of processing the received first control signal; and a step of transmitting a second control signal generated based on the processing to the terminal.