Patent Application
20240056877
This application is based on and claims priority under 35 U.S.C. § 119 to Korean Patent Application No. 10-2022-0099275, which was filed in the Korean Intellectual Property Office on Aug. 9, 2022, the entire disclosure of which is incorporated herein by reference.
The disclosure relates to a method and device for providing a delay guarantee service in a wireless communication system.
5th generation (5G) mobile communication technology defines a wide frequency band to enable fast transmission speed and new services and may be implemented in frequencies below 6 GHz (“sub 6 GHz”), such as 3.5 GHz, as well as in ultra-high frequency bands (“above 6 GHz”), such as 28 GHz and 39 GHz called millimeter wave (mmWave). Further, 6G mobile communication technology, which is called a beyond 5G system, is considered to be implemented in terahertz bands (e.g., 95 GHz to 3 THz) to achieve a transmission speed 50 times faster than 5G mobile communication technology and ultra-low latency reduced by 1/10.
In the early stage of 5G mobile communication technology, standardization was conducted on beamforming and massive MIMO for mitigating propagation pathloss and increasing propagation distance in ultrahigh frequency bands, support for various numerologies for efficient use of ultrahigh frequency resources (e.g., operation of multiple subcarrier gaps), dynamic operation of slot format, initial access technology for supporting multi-beam transmission and broadband, definition and operation of bandwidth part (BWP), new channel coding, such as low density parity check (LDPC) code for massive data transmission and polar code for high-reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specified for a specific service, so as to meet performance requirements and support services for enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC).
Currently, improvement and performance enhancement in the initial 5G mobile communication technology is being discussed considering the services that 5G mobile communication technology has intended to support, and physical layer standardization is underway for technology, such as vehicle-to-everything (V2X) for increasing user convenience and assisting autonomous vehicles in driving decisions based on the position and state information transmitted from the voice over new radio (VoNR), new radio unlicensed (NR-U) aiming at the system operation matching various regulatory requirements, NR UE power saving, non-terrestrial network (NTN) which is direct communication between UE and satellite to secure coverage in areas where communications with a terrestrial network is impossible, and positioning technology.
Also being standardized are radio interface architecture/protocols for technology of industrial Internet of things (IIoT) for supporting new services through association and fusion with other industries, integrated access and backhaul (IAB) for providing nodes for extending the network service area by supporting an access link with the radio backhaul link, mobility enhancement including conditional handover and dual active protocol stack (DAPS) handover, 2-step RACH for NR to simplify the random access process, as well as system architecture/service fields for 5G baseline architecture (e.g., service based architecture or service based interface) for combining network functions virtualization (NFV) and software-defined networking (SDN) technology and mobile edge computing (MEC) for receiving services based on the position of the UE.
As 5G mobile communication systems are commercialized, soaring connected devices would be connected to communication networks so that reinforcement of the function and performance of the 5G mobile communication system and integrated operation of connected devices are expected to be needed. To that end, new research is to be conducted on, e.g., extended reality (XR) for efficiently supporting, e.g., augmented reality (AR), virtual reality (VR), and mixed reality (MR), and 5G performance enhancement and complexity reduction using artificial intelligence (AI) and machine learning (ML), support for AI services, support for metaverse services, and drone communications.
Further, development of such 5G mobile communication systems may be a basis for multi-antenna transmission technology, such as new waveform for ensuring coverage in 6G mobile communication terahertz bands, full dimensional MIMO (FD-MIMO), array antenna, and large scale antenna, full duplex technology for enhancing the system network and frequency efficiency of 6G mobile communication technology as well as reconfigurable intelligent surface (RIS), high-dimensional space multiplexing using orbital angular momentum (OAM), metamaterial-based lens and antennas to enhance the coverage of terahertz band signals, AI-based communication technology for realizing system optimization by embedding end-to-end AI supporting function and using satellite and artificial intelligence (AI) from the step of design, and next-generation distributed computing technology for implementing services with complexity beyond the limit of the UE operation capability by way of ultrahigh performance communication and computing resources.
When interworking with IP-based wide-area delay deterministic networking (DetNet) technology to provide a delay guarantee service in a 5G system, the DetNet provides end-to-end (E2E) requirements. However, since the 5G system provides an inter-link QoS guarantee function, it is required to convert the requirements of DetNet into the corresponding per-link requirements in the 5G system.
The present disclosure provides a method and device for stably supporting the DetNet in a wireless communication system.
The present disclosure also provides a method and device for converting QoS-related end-to-end (E2E) requirements into QoS-related per-link requirements for DetNet interworking in a wireless communication system.
The present disclosure also provides a method and device for stably supporting the DetNet in a wireless communication system that provides a delay guarantee service.
In accordance with an aspect of the disclosure, a method performed by a network entity supporting deterministic networking (Detnet) in a wireless communication system is provided, the method comprises receiving, from a Detnet controller of a deterministic network, configuration information including requirements in the deterministic network; identifying, based on the configuration information, a protocol data unit (PDU) session of associated with an internet protocol (IP) address of a user equipment (UE); and transmitting, to a policy control function (PCF), quality of service (QoS) parameters obtained based on the requirements in the configuration information, the QoS parameters being used for a policy update to be applied for the PDU session.
In accordance with another aspect of the disclosure, a network entity supporting deterministic networking (Detnet) in a wireless communication system is provided, the network entity comprises a transceiver, and a processor configured to receive, via the transceiver from a DetNet controller of a deterministic network, configuration information including requirements in the deterministic network, identify, based on the configuration information, a protocol data unit (PDU) session of associated with an internet protocol (IP) address of a user equipment (UE), and transmit, to a policy control function (PCF) via the transceiver, a message including quality of service (QoS) parameters obtained based on the requirements in the configuration information, the QoS parameters being used for a policy update to be applied for the PDU session.
In accordance with another aspect of the disclosure, a deterministic networking (Detnet) controller of a deterministic network communicating with a network entity supporting DetNet in a wireless communication system is provided, the Detnet controller comprises a transceiver, and a processor configured to transmit, to the network entity via the transceiver, configuration information including quality of requirements in the deterministic network, and receive, via the transceiver from the network entity, a response message in response to transmission of the configuration information, wherein a protocol data unit (PDU) session of associated with an internet protocol (IP) address of a user equipment (UE) is identified based on the configuration information, and wherein quality of service (QoS) parameters based on the requirements in the configuration information are used for a policy update to be applied for the PDU session.
In accordance with another aspect of the disclosure, a policy control function (PCF) in a wireless communication system is provided, the PCF comprises a transceiver, and a processor configured to receive, from a network entity supporting deterministic networking (DetNet), quality of service (QoS) parameters corresponding to requirements in a deterministic network, and update, based on the QoS parameters, a policy to be applied for a protocol data unit (PDU) session of associated with an internet protocol (IP) address of a user equipment (UE).
Before undertaking the DETAILED DESCRIPTION below, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document: the terms “include” and “comprise,” as well as derivatives thereof, mean inclusion without limitation; the term “or,” is inclusive, meaning and/or; the phrases “associated with” and “associated therewith,” as well as derivatives thereof, may mean to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, or the like; and the term “controller” means any device, system or part thereof that controls at least one operation, such a device may be implemented in hardware, firmware or software, or some combination of at least two of the same. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.
Moreover, various functions described below can be implemented or supported by one or more computer programs, each of which is formed from computer readable program code and embodied in a computer readable medium. The terms “application” and “program” refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof adapted for implementation in a suitable computer readable program code. The phrase “computer readable program code” includes any type of computer code, including source code, object code, and executable code. The phrase “computer readable medium” includes any type of medium capable of being accessed by a computer, such as read only memory (ROM), random access memory (RAM), a hard disk drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory. A “non-transitory” computer readable medium excludes wired, wireless, optical, or other communication links that transport transitory electrical or other signals. A non-transitory computer readable medium includes media where data can be permanently stored and media where data can be stored and later overwritten, such as a rewritable optical disc or an erasable memory device.
Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.
A more complete appreciation of the present disclosure and many of the attendant aspects thereof will be readily obtained as the same becomes better understood by reference to the following detailed description when considered in connection with the accompanying drawings, wherein:
Hereinafter, the operational principle of the disclosure is described below with reference to the accompanying drawings. When determined to make the subject matter of the present disclosure unclear, the detailed of the known functions or configurations may be skipped. The terms as used herein are defined considering the functions in the present disclosure and may be replaced with other terms according to the intention or practice of the user or operator. Therefore, the terms should be defined based on the overall disclosure.
Advantages and features of the present disclosure, and methods for achieving the same may be understood through the embodiments to be described below taken in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed herein, and various changes may be made thereto. The embodiments disclosed herein are provided only to inform one of ordinary skilled in the art of the category of the present disclosure. The present disclosure is defined only by the appended claims. The same reference numeral denotes the same element throughout the specification.
It should be appreciated that the blocks in each flowchart and combinations of the flowcharts may be performed by computer program instructions.
Further, each block may represent a module, segment, or part of a code including one or more executable instructions for executing a specified logical function(s). Further, it should also be noted that in some replacement embodiments, the functions mentioned in the blocks may occur in different orders. For example, two blocks that are consecutively shown may be performed substantially simultaneously or in a reverse order depending on corresponding functions.
As used herein, the term “unit” means a software element or a hardware element such as a field-programmable gate array (FPGA) or an application specific integrated circuit (ASIC). A unit plays a certain role. However, a “unit” is not limited to software or hardware. A “unit” may be configured in a storage medium that may be addressed or may be configured to execute one or more processors. Accordingly, as an example, a “unit” includes elements, such as software elements, object-oriented software elements, class elements, and task elements, processes, functions, attributes, procedures, subroutines, segments of program codes, drivers, firmware, microcodes, circuits, data, databases, data architectures, tables, arrays, and variables. Functions provided within the components and the “units” may be combined into smaller numbers of components and “units” or further separated into additional components and “units.” Further, the components and “units” may be implemented to execute one or more CPUs in a device or secure multimedia card. According to embodiments, a “.unit” may include one or more processors.
As used herein, each of such phrases as “A or B,” “at least one of A and B,” “at least one of A or B,” “A, B, or C,” “at least one of A, B, and C,” and “at least one of A, B, or C,” may include all possible combinations of the items enumerated together in a corresponding one of the phrases. As used herein, such terms as “1st” and “2nd,” or “first” and “second” may be used to simply distinguish a corresponding component from another, and does not limit the components in other aspect (e.g., importance or order).
As used herein, terms for identifying access nodes, terms denoting network entities, terms denoting messages, terms denoting inter-network entity interfaces, and terms denoting various pieces of identification information are provided as an example for ease of description. Thus, the disclosure is not limited to the terms, and the terms may be replaced with other terms denoting objects with equivalent technical meanings.
In the disclosure, the base station (BS) is a network entity allocating resources to the UE and capable of communicating with the UE and may be at least one of an eNode B, a Node B, a gNB, a radio access network (RAN), an access network (AN), a RAN node, an integrated access/backhaul (IAB) node, a radio access unit, a base station controller, a node over network, or a transmission reception point (TRP). The user equipment (UE) may be at least one of a terminal, a mobile station (MS), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions.
For ease of description, the terms and names defined in the latest 3rd generation partnership project 5G and NR standards among the current communication standards are used herein. However, the disclosure is not limited by such terms and names and may be likewise applicable to wireless communication networks conforming to other standards. In particular, the disclosure may be applied to 3GPP GS/NR (5th generation mobile communication standards).
In the disclosure, the network technology may refer to the standards (e.g., TS 23.501, TS 23.502, TS 23.503, etc.) defined by the international telecommunication union (ITU) or 3GPP, and the components included in the network architecture described below may mean physical entities or may mean software that performs an individual function or hardware combined with software.
The 3GPP standard standardized the 5G network system architecture and procedures. A mobile network operator may provide various services in a 5G network. To provide each service, the mobile network operator needs to meet different service requirements (e.g., delay, communication range, data rate, bandwidth, reliability, etc.) for each service. To that end, the 5G system may support network slicing (or may be referred to as the network slice), and traffic for different network slices may be handled by different PDU sessions. The PDU session may mean an association between a data network providing a PDU connection service and a UE. The network slice may be understood as technology for logically configuring a network with a set of network functions (NF) to support various services with different characteristics, such as broadband communication services, massive IoT, V2X, or other mission critical services, and separating different network slices. Therefore, even when a communication failure occurs in one network slice, communication in other network slices is not affected, so that it is possible to provide a stable communication service. To that end, the mobile network operator may constitute the network slice and may allocate network resources suitable for a specific service for each network slice or for each set of network slices. The network resource may mean a network function (NF) or logical resource provided by the NF or radio resource allocation of a base station. For example, the mobile network operator may configure network slice A for providing a mobile broadband service, network slice B for providing a vehicle communication service, and network slice C for providing an IoT service. In other words, the 5G system may efficiently provide a corresponding service to a UE through a specialized network slice suited for the characteristics of each service.
In the drawings, reference numerals shown as N1, N2, N3, . . . , Nxxx indicate known interfaces between the network functions in the 5G system. The 3GPP system defines a conceptual link connecting NFs in the 5G system as a reference point. Reference points included in the 5G system structure are described as an example below.
The 5G system may include a 5G core network (5GC), a base station, and a user equipment (UE). The 5GC may include an AMF that manages mobility of the UE, an SMF that manages the session, a UPF that is connected to the data network (DN) and plays a role to transfer data, a network exposure function (NEF) that transfers or receives the event occurring in the 5G system and the capability to be supported to the outside, a PCF that provides the policy control function of the network operator, and a UDM that provides the function of managing data such as subscriber data and policy control data, and the AF that provides the application service may communicate with the 5GC. The AMF is a network entity for managing access and mobility of the UE. The AMF may perform such network functions as registration of the UE, connection, reachability, mobility management, access identification, authentication, and mobility event generation. The SMF may perform a management function for a protocol data unit (PDU) session of the UE.
For example, the SMF may perform such network functions as session management functions of establishing, modifying, or releasing a session and maintaining a tunnel between the UPF and the base station, the functions of allocating and managing an Internet protocol (IP) address of the UE, selection and control of the user plane. The UPF may perform a data processing function of transferring data transmitted by the UE to the DN, which is an external network, or transferring data received from the DN to the UE. Further, the UPF may perform network functions, such as acting as an anchor between radio access technologies (RATs), providing connection with PDU sessions and the AF, packet routing and forwarding, packet inspection, application of user plane policy, creating a traffic usage report, or buffering. The PCF may manage operator policy information for providing the service in the 5G system, and the UDM may perform functions such as generating authentication information for 3GPP security, managing the list of NFs supporting the UE, and managing subscription information.
The unified data repository (UDR) may perform the functions of storing and providing subscription information managed by the UDM, structured data for exposure, and application data related to NEF or service. Meanwhile, in a UE registration procedure, the UE may transmit, to the AMF, identification information about network slices to be requested (requested single-network slice selection assistance information (S-NSSAIs)), and the AMF may provide the UE with information about a network slice available to the UE (allowed NSSAI) in consideration of the requested S-NSSAIs, subscriber information, and the like. In order to transmit and receive data to and from a specific data network (DN) through allowed slices (allowed NSSAIs), the UE may select one of the allowed slices, request the data network name (DNN) for the network slice selected from among the allowed network slices to generate a PDU session, and transmit and receive data through the generated PDU session. In the embodiments of
Referring to
For example, when the 5G system provides time synchronization to the UE 110, the TSN AF 150 in the 5G system may configure the NW-TT 141 and the DS-TT 111 based on the information provided from the CNC server 155, convert the sync message provided from the external network based on the internal time of the 5G system and transfer the sync message, and when the sync message is again transferred from the 5G system to the external network, the 5G system may again convert the sync message based on the external time of the external TSN node. In the example of
Conversely, the TSCTSF 150 may collect the 5G system information from the DS-TT 111 and the NW-TT 141 and transfer the collected information to the AF connected to the TSN node(s) 160. Further, the NEF may be required together with the TSCTSF depending on whether the AF belongs to the 5G system. For example, the NEF along with the TSCTSF may be needed when the AF does not belong to the 5G system.
Similar to the operation of the CNC server 155 when interworking between the 5G system and the TSN described in the example of
For example, when the 5G system provides time synchronization to the UE 110, the DetNet AF 250 (or TSCTSF/NEF) in the 5G system may configure the NW-DT 241 and the DS-DT 211 based on the QoS-related requirement information provided from the DetNet controller 255, convert the sync message provided from the external network based on the internal time of the 5G system and transfer the sync message, and when a sync message is again transferred from the 5G system to the external network, 5G system may again convert the sync message based on the external time of the external DetNet node 260. In the example of
In the example of
Referring to
In step 500 of
In step 500a, the UE 110 performs a PDU session establishment procedure in the 5G system. In this case, a PDU session establishment request message transmitted by the UE 110 to the network may include capability information about the UE 110 indicating whether the UE 110 is operable according to the request of the DetNet. Further, the subscriber information about the UE 110 may include information indicating whether a low-delay service may be provided according to a request from the DetNet. For example, the capability information about the UE 110 may be included in at least one of the registration request message and the PDU session establishment request message.
In step 501, the DetNet controller 255 (or external AF) transfers the QoS-related end-to-end (E2E) requirements to the DetNet AF 250 (or TSCTSF/NEF) of the 5G system. The information about the QoS-related E2E requirements may include source IP and port and destination IP and port information as information indicating the end-to-end flow. The information about the E2E requirements may include at least one of the maximum delay to be guaranteed end-to-end and the minimum bandwidth to be guaranteed end-to-end.
In step 502, the DetNet AF 250 (or TSCTSF/NEF) of the 5G system may derive/acquire/generate information about the QoS-related per-link requirements in the 5G system based on the information about the E2E requirements. Specifically, the DetNet AF 250 (or TSCTSF/NEF) may derive the QoS-related per-link requirement information including at least one of UE IP(s) and DNN(s)/S-NSSAI(s) determined to be able to provide the corresponding path, based on source IP/port and destination IP/port information and routing information from the E2E requirement information. Further, the DetNet AF 250 (or TSCTSF/NEF) may subscribe to notify the UDM/UDR 145 of a PDU session meeting the conditions of the QoS-related per-link requirements.
In step 503, the DetNet AF 250 (or TSCTSF/NEF) may derive a PDU session ID(s) matching the UE IP(s) and DNN(s)/S-NSSAI(s) information. Further, the PCF 135 may subscribe to the UDM/UDR 145 to notify when a PDU session meeting the conditions of the QoS-related per-link requirements is generated.
In step 504, the DetNet AF 250 (or TSCTSF/NEF) may select the optimal, at least one PDU session by comparing the maximum delay and minimum data rate, which may be provided per PDU session, with the QoS-related E2E requirements from among the PDU session(s) selected as candidate(s) that meet the QoS-related per-link requirements in step 503. For example, the DetNet AF 250 (or TSCTSF/NEF) may select the PDU session that provides the minimum DPB from among the PDU sessions in which the PDB providable per PDU session is smaller than the E2E delay requirement. Further, the DetNet AF 250 (or TSCTSF/NEF) may select the PDU session that provides the maximum GBR meeting the condition that the minimum data rate provided per PDU session is larger than the E2E bandwidth requirement. When both the delay condition and the bandwidth (BW) condition may be met, and another PDU session is selected, either the delay condition or the bandwidth (BW) condition may be prioritized. For example, the delay condition may be prioritized to be selected.
In step 505, the DetNet AF 250 (or TSCTSF/NEF) requests the PCF to configure a policy related to the QoS per-link requirements. In this case, the policy configuration request may include at least one of UE information and QoS requirements (max delay, min data rate), and PDU session ID. Further, the DetNet AF 250 (or TSCTSF/NEF) may derive the subscription public identifier (SUPI) or subscription concealed identifier (SUCI) which is UE ID information used inside the 5G system based on the UE IP information and use the UE ID information as the UE information.
In step 505a, the PCF 135 requests the SMF 130 to update the QoS-related policy information. In this case, the policy information update request may include at least one of the UE information and QoS requirements (max delay, min data rate), and PDU session ID.
In step 505b, the SMF 130 transfers the PDU session modify request to the UE 110 through the AMF 125. In this case, the PDU session modify request may include at least one of UE information and QoS requirements (max delay, min data rate), and PDU session ID. The QoS parameters of the RAN (gNB) 120 may be updated through the PDU session modify request.
In step 505c, the SMF 130 may configure the user plane QoS of the core network (CN) through an N4 session update request to the UPF 140. In this case, the N4 session update request may include at least one of UE information and QoS requirements (max delay, min data rate), and PDU session ID.
The operations of step 506 to 507c may be performed when there is no PDU session meeting the QoS-related per-link requirements among the candidate PDU sessions and a new PDU session may be discovered in steps 500a to 505. Accordingly, the following operations of steps 506 to 507c may be selectively performed.
In step 506, the UE 110 may perform a PDU session establish procedure for the new PDU session in the 5G system. In this case, the PDU session establish request message transmitted by the corresponding UE 110 to the network may include capability information indicating whether the corresponding UE 110 may operate according to the request of the DetNet. Further, the subscriber information about the UE 110 may include information indicating whether a low-delay service may be provided according to a request from the DetNet.
In step 506a, the UDM/UDR 145 may notify the DetNet AF 250 (or TSCTSF/NEF) that a new PDU session has been established in accordance with the subscription condition in step 502.
In step 506b, the DetNet AF 250 (or TSCTSF/NEF) requests the PCF 135 to configure a policy related to the QoS requirements. In this case, the policy configuration request may include at least one of UE information and QoS requirements (max delay, min data rate), and PDU session ID. The DetNet AF 250 (or TSCTSF/NEF) may derive the SUPI or SUCI which is UE ID information used inside the 5G system based on the UE IP information and use the UE ID information as the UE information.
In step 506c, the UDM/UDR 145 may request the PCF 135 to update the policy according to the subscription condition in step 503. In this case, the policy update request may include at least one of UE information and QoS requirements (max delay, min data rate), and PDU session ID.
In step 507a, the PCF 135 requests the SMF 130 to update the QoS-related policy information. In this case, the policy information update request may include at least one of the UE information and QoS requirements (max delay, min data rate), and PDU session ID.
In step 507b, the SMF 130 transfers the PDU session modify request to the UE 110 through the AMF 125. In this case, the PDU session modify request may include at least one of UE information and QoS requirements (max delay, min data rate), and PDU session ID. The QoS parameters of the RAN (gNB) 120 may be updated through the PDU session modify request.
In step 507c, the SMF 130 may configure the user plane QoS of the CN through an N4 session update request to the UPF 140. In this case, the N4 session update request may include at least one of UE information and QoS requirements (max delay, min data Rate), and PDU session ID.
In step 508, the DetNet AF 250 (or TSCTSF/NEF) transfers, to the DetNet controller 255 (or external AF), a response to the request in step 501 or a notification for the results performed after steps 506 and 506a. In this case, the response or notification may include at least one of E2E requirements (delay, BW, source/destination info) and the UE IP and QoS requirements (max delay, min data rate).
In the above-described embodiments, the DetNet AF 250 (or TSCTSF/NEF) and the DetNet controller 255 (or external AF) may exist as distinct network entities or may be included in one network entity.
According to the above-described embodiments, it is possible to provide functions necessary for the 5G system by providing the QoS-related end-to-end (E2E) requirements provided by DetNet to the 5G system and converting the QoS-related end-to-end (E2E) requirements into QoS-related per-link requirements in the 5G system when interworking with the IP-based wide-area delay deterministic network (DetNet) technology to provide a delay guarantee service in the 5G system
The network entity of
The transceiver 605 collectively refers to the receiver of the network entity and the transmitter of the network entity and may transmit and receive signals to/from a UE or another network entity. The transmitted/received signals may include at least one of control information and data. To that end, the transceiver 605 may include a wired/wireless transceiver and may include various components for transmitting/receiving signals. The transceiver 605 may receive signals through a predetermined communication interface, output the signals to the processor 600, and transmit the signals output from the processor 600. Further, the transceiver 605 may receive the communication signal and output it to the processor 600 and transmit the signal output from the processor 600 to the UE or another network entity through the network. The memory 610 may store programs and data necessary for the operation of the network entity according to at least one of the embodiments of
For example, for deterministic network (DetNet) interworking in the wireless communication system, the processor 600 may receive information about a QoS-related end-to-end requirement from an IP-based DetNet server (i.e., the DetNet controller 255) (or an external AF) through the transceiver 605, obtain information about a QoS-related per-link requirement in the wireless communication system based on the information about the QoS-related end-to-end requirement, and select at least one PDU session that meets the QoS-related per-link requirement. The processor 600 may include at least one processor.
The methods according to the embodiments described in the specification or claims of the disclosure may be implemented in hardware, software, or a combination of hardware and software.
When implemented in software, there may be provided a computer readable storage medium storing one or more programs (software modules). One or more programs stored in the computer readable storage medium are configured to be executed by one or more processors in an electronic device. One or more programs include instructions that enable the electronic device to execute methods according to the embodiments described in the specification or claims of the disclosure.
The programs (software modules or software) may be stored in random access memories, non-volatile memories including flash memories, read-only memories (ROMs), electrically erasable programmable read-only memories (EEPROMs), magnetic disc storage devices, compact-disc ROMs, digital versatile discs (DVDs), or other types of optical storage devices, or magnetic cassettes. Or the programs may be stored in a memory constituted of a combination of all or some thereof. As each constituting memory, multiple ones may be included.
The programs may be stored in attachable storage devices that may be accessed via a communication network, such as the Internet, Intranet, local area network (LAN), wide area network (WLAN), or storage area network (SAN) or a communication network configured of a combination thereof. The storage device may connect to the device that performs embodiments via an external port. A separate storage device over the communication network may be connected to the device that performs embodiments.
In the above-described specific embodiments, the components included in the disclosure are represented in singular or plural forms depending on specific embodiments provided. However, the singular or plural forms are selected to be adequate for contexts suggested for ease of description, and the disclosure is not limited to singular or plural components. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise.
Although specific embodiments of the present disclosure have been described above, various changes may be made thereto without departing from the scope of the present disclosure. Thus, the scope of the disclosure should not be limited to the above-described embodiments, and should rather be defined by the following claims and equivalents thereof.
Although the present disclosure has been described with various embodiments, various changes and modifications may be suggested to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2022-0099275 | Aug 2022 | KR | national |
