Method and apparatus for dynamic management of operational control plane services

Abstract

The disclosure relates to a 5G communication system or a 6G communication system for supporting higher data rates beyond a 4G communication system such as a long term evolution (LTE). According to an embodiment of the disclosure, a method of operating a user defined service (UDS) by a first network entity in a wireless communication system can be disclosed, the method including receiving a UDS registration procedure request message including information on a UDS network function (NF) and information on a UE container from an application function (AF), transmitting a request message for UDS deployment including information on the UDS NF to an operation administration maintenance (OAM), and transmitting a UE container deployment request message including information on the UE container to a UDS agent in a user equipment (UE).

Description

Technical Field

[0001] This disclosure relates to a method and apparatus for dynamically managing network services by introducing new network devices (network functions) into the core network of a wireless communication system and new logical devices into user equipment (UEs) as a technology for the control plane of a wireless communication system. Background Technology

[0002] Considering the generational evolution of wireless communication, technologies are primarily developed for human-facing services such as voice calls, multimedia services, and data services. With the commercialization of fifth-generation (5G) communication systems, the number of connected devices is expected to grow exponentially. These devices will increasingly connect to communication networks. Examples of connected things can include vehicles, robots, drones, home appliances, displays, smart sensors connected to various infrastructures, construction machinery, and factory equipment. Mobile devices are expected to evolve into various form factors, such as augmented reality glasses, virtual reality headsets, and holographic devices. Efforts have been underway to develop improved 6G communication systems to provide a wide range of services by connecting hundreds of billions of devices and things in the sixth-generation (6G) era. For these reasons, 6G communication systems are referred to as super-5G systems.

[0003] The 6G communication system, which is expected to be commercialized around 2030, will have peak data rates in the terabyte (1,000 gigabyte) range and radio latency of less than 100 μsec, making it 50 times faster than 5G communication systems and with 1 / 10 of their radio latency.

[0004] To achieve such high data rates and ultra-low latency, 6G communication systems have been considered for implementation in the terahertz band (e.g., the 95 GHz to 3 THz band). It is anticipated that technologies ensuring signal transmission distance (i.e., coverage) will become even more critical due to the more severe path loss and atmospheric absorption in the terahertz band compared to the millimeter-wave band introduced in 5G. Key technologies for ensuring coverage include the development of radio frequency (RF) components, antennas, new waveforms with better coverage than orthogonal frequency division multiplexing (OFDM), beamforming and massive MIMO (multiple input multiple output), full dimensional MIMO (FD-MIMO), array antennas, and multi-antenna transmission technologies such as massive MIMO. Furthermore, discussions continue regarding new technologies to improve terahertz band signal coverage, such as metamaterial-based lenses and antennas, orbital angular momentum (OAM), and reconfigurable intelligent surfaces (RIS).

[0005] In addition, to improve spectrum efficiency and overall network performance, the following technologies have been developed for 6G communication systems: full-duplex technology, enabling uplink and downlink transmissions to use the same frequency resources simultaneously; network technologies for integrated utilization of satellites, high-altitude platform stations (HAPS), etc.; improved network architectures to support mobile base stations and achieve network operation optimization and automation; dynamic spectrum sharing technology to avoid conflicts through spectrum usage prediction; technologies using artificial intelligence (AI) in wireless communication to improve overall network operation by leveraging AI from the design phase for 6G development and internalizing end-to-end AI support functions; and next-generation distributed computing technologies to overcome the limitations of user equipment (UE) computing capabilities by obtaining achievable ultra-high-performance communication and computing resources (such as mobile edge computing (MEC), cloud, etc.) through the network. Furthermore, efforts are continuing to enhance connectivity between devices, optimize networks, promote the software-defined networking of network entities, and increase the openness of wireless communications by designing new protocols to be used in 6G communication systems, developing mechanisms for achieving hardware-based secure environments and secure data use, and developing technologies for maintaining privacy.

[0006] The research and development of 6G communication systems is expected to bring the next hyper-connected experience in terms of hyper-connectivity, including person-to-machine (P2M) and machine-to-machine (M2M) connections. Specifically, 6G communication systems are expected to provide services such as truly immersive extended reality (XR), high-fidelity mobile holograms, and digital replicas. Furthermore, services such as remote surgery for enhanced safety and reliability, industrial automation, and emergency response will be provided through 6G communication systems, enabling these technologies to be applied in various fields such as industry, healthcare, automotive, and home appliances.

[0007] The control plane of a traditional wireless communication system is configured with an AS sublayer using access stratum (AS) protocols and a NAS sublayer using non-access stratum (NAS) protocols. AS protocols are used to exchange control messages between user equipment (UE) and base stations, while NAS protocols are used to exchange control signals between UE and core network equipment. The NAS sublayer is further divided into NAS mobility management (NAS-MM) services and other NAS services. NAS-MM services are used to exchange control messages between UE and the access and mobility management function (AMF), while other NAS services can only exchange control messages through NAS-MM services. This protocol configuration and the relationships between layers are specialized information for wireless communication systems, standardized by the 3GPP (3rd Generation Partnership Project), and typically implemented in chipsets based on the corresponding standards.

[0008] With the advancement and widespread adoption of network function virtualization and cloud technologies, the core network of 5G wireless communication systems has introduced a service-based architecture (SBA). Within this architecture, each network function (NF) is defined as software that provides one or more services. This service-based architecture (SBA) aims to evolve the core network to facilitate modification and deployment. Furthermore, the system is designed to support service mesh architectures to facilitate the introduction of new network functions and to support structures that facilitate mutual service discovery and utilization.

[0009] As mentioned above, the core network of 5G wireless communication systems has sought to evolve to enable flexible modification, deployment, and introduction of services. However, these evolution efforts are confined to the core network portion within the control plane of the 5G system. Therefore, when defining new network functions for new services within the core network, connections to other network devices can be established through the common service-based interface (SBI) used in traditional systems, allowing for the provision of mutual services. However, in order for this service to exchange control messages with the User Equipment (UE), the new service needs to be applied on top of the UE's NAS Mobility Management (NAS-MM) service. Furthermore, both the UE and the network's NAS-MM layers need to be updated to deliver the service's messages. A drawback of performing this update is the long lead time required. Summary of the Invention

[0010] Technical issues

[0011] This disclosure aims to enable the system to minimize the preparation time associated with introducing new services by flexibly configuring the UE's control plane connection to configure logical devices in the core network capable of dynamically managing services when new services need to be provided within the network.

[0012] Technical solution

[0013] According to embodiments of this disclosure, to address the aforementioned problems, an operation method for a user-defined service (UDS) performed by a first network entity within a wireless communication system is disclosed. The method may include: receiving a UDS registration process request message from an application function (AF), the UDS registration process request message including information about the UDS network function (NF) and information about a UE container; sending a request message for UDS deployment to an operation administration maintenance (OAM), the request message including information about the UDS NF; and sending a UE container deployment request message to a UDS agent in a user equipment (UE), the UE container deployment request message including information about the UE container.

[0014] According to embodiments of this disclosure, the method may further include: sending a routing configuration request message for the UDS to a second network entity.

[0015] According to embodiments of this disclosure, the method may further include: when the protocol used by the UDS is a non-access stratum (NAS), allocating an extended protocol discriminator (EPD) to the UDS, wherein the routing configuration request message may include address information of the UDS NF mapped to the EPD.

[0016] According to embodiments of this disclosure, when the protocol used by the UDS is not NAS, the routing configuration request message may include a signaling radio bearer (SRB) allocation request for IP packets.

[0017] According to embodiments of this disclosure, the method may further include: receiving handover event-related information about the user equipment from the UDS agent; determining a change in the NAS anchor point based on information about the NAS anchor point that transmits the handover event-related information; and when it is determined that the NAS anchor point has changed, sending information about the change in the NAS anchor point to the UDS NF.

[0018] According to another embodiment of this disclosure, in order to solve the above-mentioned problems, a method performed by a User-Defined Service Agent (UDS Agent) within a User Equipment operating in a wireless communication system may be disclosed. The method may include: receiving a UE container deployment request message from a first network entity, the UE container deployment request message including information about a UE container associated with a UDS; installing the UE container in the User Equipment; and configuring a messaging path for the UE container.

[0019] The method may further include: receiving an Extended Protocol Authentication Device (EPD) from the Access and Mobility Management Function (AMF); and sending a connection request message including the EPD to the first network.

[0020] The method may further include: when the protocol used by the UDS is a non-access stratum (NAS), requesting the access stratum (AS) layer in the user equipment to configure a service access point (SAP) corresponding to the UDS.

[0021] The method may further include: when the protocol used by the UDS is not a non-access stratum (NAS), requesting the access stratum (AS) layer in the user equipment to configure the signaling radio bearer (SRB) based on the SRB information received from the first network entity.

[0022] The method may further include: receiving information about a handover event occurring from the modem of the user equipment; and sending handover event-related information to the first network entity.

[0023] According to another embodiment of this disclosure, a first network entity for operating a UDS within a wireless communication system is disclosed. The first network entity may include: a transceiver; and a controller, wherein the controller may be configured to: receive a UDS registration process request message from an application function (AF), the UDS registration process request message including information about a UDS network function (NF) and information about a UE container; send a request message for UDS deployment to an Operation Management and Maintenance (OAM), the request message including information about the UDS NF; and send a UE container deployment request message to a UDS agent in a user equipment (UE), the UE container deployment request message including information about the UE container.

[0024] According to another embodiment of this disclosure, a UDS agent within a user equipment operating in a wireless communication system is disclosed. The UDS agent may include a transceiver and a controller, wherein the controller may be configured to: receive a UE container deployment request message from a first network entity, the UE container deployment request message including information about a UE container associated with a UDS; install the UE container in the user equipment; and configure a messaging path for the UE container.

[0025] Beneficial effects

[0026] According to various embodiments of this disclosure, when it is necessary to add new functions to the system or change the format of sent information or messages due to the upgrade of specific functions, the system can respond flexibly through network devices (network functions) in the control plane and newly introduced logical devices in the user equipment.

[0027] According to various embodiments of this disclosure, it is possible to facilitate the introduction of a variety of services that can effectively utilize the functions of devices with various morphological factors and capabilities. Attached Figure Description

[0028] To gain a more complete understanding of this disclosure and its advantages, the following description is now taken in conjunction with the accompanying drawings, in which the same reference numerals denote the same parts:

[0029] Figure 1 The control plane connection structure in a wireless communication system according to an embodiment of the present disclosure is shown;

[0030] Figure 2 A user equipment in a wireless communication system according to an embodiment of the present disclosure is shown;

[0031] Figure 3 A wireless communication system according to an embodiment of the present disclosure is shown;

[0032] Figure 4A wireless communication system according to an embodiment of the present disclosure is shown;

[0033] Figure 5 A flowchart illustrating a method for performing a UDS registration process according to an embodiment of this disclosure is shown;

[0034] Figure 6 A flowchart illustrating a method for deploying a UDS on the network side by a UDSM according to an embodiment of this disclosure is shown;

[0035] Figure 7 A flowchart is shown illustrating a method for removing a UDS from a network by a UDSM according to an embodiment of this disclosure;

[0036] Figure 8 A flowchart is shown illustrating a method by which a UDSM configures a messaging path for each UDS within a network according to an embodiment of the present disclosure;

[0037] Figure 9 A flowchart illustrating a method for modifying the message passing path configured for each UDS by a UDSM according to an embodiment of this disclosure is shown;

[0038] Figure 10 A flowchart illustrating a method for deploying a UE container according to an embodiment of this disclosure is shown;

[0039] Figure 11 A flowchart of a method for removing a UE container according to an embodiment of this disclosure is shown;

[0040] Figure 12 A flowchart illustrating the connection process between a UDS agent and a UDSM according to an embodiment of this disclosure is shown;

[0041] Figure 13 The connection structure of logical devices within a user equipment according to an embodiment of the present disclosure is shown;

[0042] Figure 14 A flowchart is shown illustrating a method for deploying a UE container and performing initial configuration by a UDS agent according to an embodiment of this disclosure;

[0043] Figure 15 A flowchart of a method for updating UDS transmission information according to an embodiment of this disclosure is shown;

[0044] Figure 16 A flowchart illustrating the UDS deployment and message exchange process according to an embodiment of this disclosure is shown;

[0045] Figure 17 The structure of a terminal according to an embodiment of this disclosure is shown; and

[0046] Figure 18 The structure of a network entity according to an embodiment of this disclosure is shown. Detailed Implementation

[0047] Before proceeding with the following detailed description, it may be advantageous to define certain words and phrases used throughout this patent document: the terms “comprising” and “including” and their derivatives mean to include without limitation; the term “or” is inclusive, meaning and / or; the phrase “associated with” and its derivatives may mean to include, be included, interconnected with, contain, be contained within, connected to or connected with, coupled to or coupled with, communicate with, cooperate with, intertwine, juxtapose, approach, bind to or bind with, have, possess the properties of, etc.; 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 a combination of at least two of these. It should be noted that the functionality associated with any particular controller can be centralized or distributed, local or remote.

[0048] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each computer program being formed by 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, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in appropriate 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 accessible by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable medium excludes wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable medium includes media that can permanently store data as well as media that can store data and subsequently be overwritten, such as rewritable optical discs or erasable storage devices.

[0049] Throughout this patent document, definitions of certain words and phrases are provided, and those skilled in the art will understand that, in many (if not most) cases, such definitions apply to the prior and future use of the words and phrases defined in this way.

[0050] The following Figures 1 to 18 The various embodiments used to describe the principles of this disclosure in this patent document are merely illustrative and should not be construed as limiting the scope of this disclosure in any way. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged system or device.

[0051] In the following description, embodiments of the present disclosure will be illustrated with reference to the accompanying drawings. It should be noted that, in this context, the same constituent elements will be represented by the same reference numerals in the drawings. Furthermore, detailed descriptions of known functions and configurations that may obscure the subject matter of this disclosure will be omitted.

[0052] In describing embodiments in this disclosure, descriptions of technical content known in the art to which this disclosure pertains but not directly related to this disclosure will be omitted. This is to more clearly describe the subject matter of this disclosure without obscuring it by omitting any unnecessary descriptions.

[0053] Similarly, in the accompanying drawings, some components are shown in exaggerated or schematic form or are omitted. Furthermore, the size of each component does not perfectly reflect its actual size. In the drawings, the same reference numerals denote the same or corresponding components.

[0054] The advantages and features of this disclosure, as well as methods for achieving these advantages and features, will become clear with reference to the exemplary embodiments described in detail below in conjunction with the accompanying drawings. However, this disclosure is not limited to the exemplary embodiments disclosed herein, but will be implemented in various forms. Exemplary embodiments of this disclosure are provided so that this disclosure will be fully disclosed and its scope will be fully understood by those skilled in the art. This disclosure is defined only by the scope of the appended claims. Throughout this specification, the same reference numerals denote the same constituent elements.

[0055] In this context, it should be understood that each block of the flowchart description, and combinations thereof, can be executed by computer program instructions. These computer program instructions can be loaded into the processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that the instructions, which execute on the processor of the computer or other programmable data processing apparatus, create means for performing the functions described in the flowchart blocks. These computer program instructions can also be stored in a computer-usable or computer-readable storage medium that can direct the computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-usable or computer-readable storage medium produce an article of art comprising instruction means for performing the functions described in the flowchart blocks. The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable data processing apparatus, thereby producing a computer-implemented process, such that the instructions, which execute on the computer or other programmable data processing apparatus, provide steps for implementing the functions described in the flowchart blocks.

[0056] Furthermore, each block can represent a module, segment, or section of code comprising one or more executable instructions for performing a specified logical function. It should also be noted that in some alternative execution examples, the functions mentioned in a block may appear in a different order. For example, two blocks shown consecutively may actually be executed substantially simultaneously, or these blocks may sometimes be executed in reverse order depending on their respective functions.

[0057] In this context, as used herein, the terms “unit,” “component,” or “part” refer to a software or hardware component, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC), in which the term “unit,” “component,” or “part” performs certain functions. However, the terms “unit,” “component,” or “part” are not limited to software or hardware. The terms “unit,” “component,” or “part” may be configured to reside in addressable storage media or to reproduce one or more processors. Thus, by way of example, the terms “unit,” “component,” or “part” include components such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided in components and the terms “unit,” “component,” or “part” may be combined into a smaller number of components, “units,” “components,” and “parts,” and / or divided into additional components, “units,” “components,” and “parts.” Furthermore, the constituent elements and “units,” “components,” and “parts” can be implemented as one or more CPUs or secure multimedia cards within the execution device.

[0058] In the following text, the base station, as the entity responsible for performing resource allocation for the terminal, can be at least one of a Node B, BS (base station), eNB (eNode B), gNB (gNode B), radio access unit, base station controller, or node on a network. The terminal can include a user equipment (UE), mobile station (MS), 5G UE, cellular phone, smartphone, computer, or multimedia system capable of performing communication functions. Furthermore, the embodiments of this disclosure described below can be applied to other communication systems with similar technical backgrounds or channel types. Additionally, embodiments of this disclosure can be applied to other communication systems with modifications, as determined by those skilled in the art, without substantially departing from the scope of this disclosure. For example, this can include 5G wireless communication technologies developed after LTE-A (5G, new radio (NR)), and "5G below" can be a concept including existing LTE, LTE-A, and other similar services. Furthermore, this disclosure can be applied to other communication systems with modifications, as determined by those skilled in the art, without substantially departing from the scope of this disclosure.

[0059] In the following description, terms used to identify connected nodes (one or more nodes), to refer to network entities or network functions (NFs), to refer to messages, to refer to interfaces between network entities, and to refer to various identifying information are provided for illustrative purposes for ease of description. Therefore, this disclosure is not limited to the terms described below, and other terms may be used to refer to subjects with equivalent technical meanings.

[0060] In the following text, for ease of description, some terms and names defined in the 3GPP Long Term Evolution (LTE) specification and / or the 3GPP New Radio (NR) specification may be used. However, this disclosure is not limited to these terms and names and may be applied equivalently to systems conforming to other specifications.

[0061] Figure 1 A control plane connection structure in a wireless communication system according to an embodiment of the present disclosure is shown.

[0062] refer to Figure 1 User equipment (UE) can use access stratum (AS) protocols to exchange control messages with base stations and can use non-access stratum (NAS) protocols to exchange control messages with the core network.

[0063] AS and NAS protocols are control plane protocols used by user equipment, defined and managed by specifications. Therefore, when introducing new services including user equipment into the system, or when it is necessary to change the protocols associated with previously introduced services, the relevant content needs to be reflected in the specifications, and a long preparation time is required to manufacture new chipsets based on the corresponding specifications.

[0064] Figure 2 A user equipment in a wireless communication system according to an embodiment of the present disclosure is shown.

[0065] As referenced above Figure 1 As stated above, in the existing system, when a new service is introduced or the protocol of a previously introduced service needs to be changed, a new chipset needs to be manufactured in the user equipment and the changes need to be made, resulting in a long preparation time. Furthermore, to utilize the newly introduced service, it is necessary to replace the user equipment.

[0066] Recent wireless communication systems not only accommodate traditional handheld user equipment but also various types of terminal devices with different form factors and capabilities, such as vehicles, robots, and Internet of Things (IoT) sensors. Therefore, recent wireless communication systems aim to provide a variety of new services through user equipment. However, the traditional design and operation methods of NAS protocols require lengthy preparation times, making it difficult to introduce new functionalities into the system. Furthermore, because each protocol needs to be defined to potentially support a wide range of devices, there are inefficiencies in optimizing for different types of devices and services. Previously, due to these design and operational limitations, the diversification of network services has not been actively pursued, which has also contributed to the difficulty in introducing and operating specialized services for specific services or terminals.

[0067] Figure 3 A wireless communication system according to an embodiment of the present disclosure is shown.

[0068] This disclosure provides the introduction of a User Defined Service (UDS) Manager as a new Network Function (NF) within the core network, and also provides the introduction of a UDS Agent as a new Logical Device within a User Equipment (UE).

[0069] In this specification, the term "User Defined Service (UDS)" can refer to a service designed to be flexibly and dynamically managed and operated on a communication system.

[0070] refer to Figure 3 The UDSM can receive and manage UDS-related components from external interfaces or application functions (AFs), and can deploy, modify, or delete network functions (NFs) on the network side through Operations Management and Maintenance (OAM).

[0071] The UDSM can interact with the UDS agent, a new logical device introduced into the user equipment, and through this interaction with the UDS agent, it can perform the deployment, modification, or deletion of UE containers. During this process, the UDSM can pass configuration information related to the user equipment (UE) configuration that the UDS agent needs to perform.

[0072] UDSM can configure the appropriate message passing path on the network side for each UDS.

[0073] Through interaction with the UDSM, the UDS agent can perform the deployment and management of UE containers and perform environment configuration on L2, L3, and the Service Access Point (SAP) within the UE to suit each UDS. Based on the executed environment configuration, the UDS agent can send UDS messages via the NAS, allocate new signaling radio bearers (SRBs), and perform routing for IP packet transmissions.

[0074] UDS agents can perform updates to UDS-transmitted information in scenarios such as handover caused by user device movement.

[0075] According to this embodiment of the disclosure, services outside the specification can be registered with the Service Management Entity (UDSM) within the system via an AF or external interface. Among the components of the registered service, network-side functions can be deployed by the UDSM, while UE-side functions can be deployed by the UDS agent. The deployed functions can be used to exchange messages with each other and operate accordingly to achieve the purpose of the newly introduced service, depending on the configuration of the UDSM and the UDS agent.

[0076] Figure 4 A wireless communication system according to an embodiment of the present disclosure is shown.

[0077] refer to Figure 4 The core network may include UDSM, and user equipment (UE) may be configured to include UDS agents.

[0078] According to embodiments of this disclosure, a UDS can be configured by one or more UDS NFs (e.g., VNFs, CNFs, etc.) and one or more UE containers. The UDS NF is the network-side function that configures the UDS, while the UE container is the user equipment-side function that configures the UDS.

[0079] As described above, UDSM can receive and manage UDS-related components from external interfaces or application functions (AFs), and can perform network function (NF) deployment, modification, or deletion on the network side through Operations Management and Maintenance (OAM).

[0080] The UDSM can interact with the UDS agent, a new logical device introduced into the user equipment, and through this interaction, it can deploy, modify, or delete UE containers. During this process, the UDSM can pass configuration information related to the user equipment (UE) configuration that the UDS agent needs to perform.

[0081] UDSM can configure appropriate network-side messaging paths and wireless connectivity information for each UDS.

[0082] According to embodiments of this disclosure, the UDSM can be configured independently as a separate device within the network. Alternatively, the UDSM can be implemented integratedly with other network devices. When the UDSM is implemented integratedly with other network devices, the functionality of the UDSM provided in this disclosure can be performed by those other network devices.

[0083] When UDSM is implemented in integration with other network devices, its functionality can be integrated with network devices such as unified data management (UDM) for various information within an integrated management system, AMF responsible for NAS routing, or radio access network (RAN) responsible for AS routing. UDSM can also be implemented in integration with other network devices beyond those mentioned above.

[0084] As described above, the UDS agent is a logical device within a user equipment that manages the UDS, and is a device newly provided in this disclosure.

[0085] Through interaction with the UDSM, the UDS agent can perform the deployment and management of UE containers and perform environment configuration on L2, L3, and the Service Access Point (SAP) within the UE to suit each UDS. Based on the executed environment configuration, the UDS agent can send UDS messages via the NAS, allocate new signaling radio bearers (SRBs), and perform routing for IP packet transmissions.

[0086] UDS agents can perform updates to UDS-transmitted information in scenarios such as handover caused by user device movement.

[0087] According to embodiments of this disclosure, software such as a UDS agent or UE container as defined herein can refer not only to dynamically installable or removable forms. For example, for a resource-constrained dedicated user equipment, when appropriate functional and parameter configurations are applied to the corresponding user equipment, and the UDSM performs the deployment and network configuration of the corresponding UDS NF, it can be understood as equivalent to the deployment of the UE container and the configuration of the UDS agent as provided in this disclosure being performed.

[0088] Figure 5A flowchart illustrating a method for performing a UDS registration process according to an embodiment of this disclosure is shown.

[0089] UDSM 540 receives a request from AF to register the UDS required for the corresponding application (S501), and can provide the requested UDS. In this case, the UDS registration request message (Nnef_UDS registration request) passed in step S501 may include one or more NF images and one or more UE containers.

[0090] To provide UDS for AF requests, each network device can provide the following services.

[0091] - UDSM can provide services such as UDS registration requests, UDS modification requests, or UDS deletion requests, which can be invoked by PCF.

[0092] PCF can provide services such as UDS registration requests, UDS modification requests, or UDS deletion requests, which can be invoked by NEF or AF. According to an embodiment, when AF operates within a trusted zone, AF can directly invoke PCF services without routing through NEF.

[0093] - NEF can provide services such as UDS registration requests, UDS modification requests, or UDS deletion requests, which can be invoked by AF.

[0094] Each UDS registration, modification, or deletion request message may include the UDS ID, UDS version, UDS components, a list of services for the UDS components, and UDS-related information.

[0095] - UDS constituent elements may directly include UDS images, or alternatively, UDS images may be stored in a separate repository with only their address values ​​included in the UDS constituent elements.

[0096] UDS-related information may include service requirements (e.g., low latency, high reliability, etc.), necessary hardware features (e.g., GPU or smart NIC, etc.), operating system (e.g., Linux, etc.), protocols (e.g., NAS, UDP, etc.).

[0097] - PCF can allow information about service operation policies (e.g., the list of servers where the UDS NF can reside, the amount of server resources available for the UDS NF, and the UE categories for which UE containers can be deployed) to be included in the S503 message (Nudsm_UDS registration request) and pass this information to the UDSM according to the corresponding application-related policies.

[0098] According to embodiments of this disclosure, the deletion request may not include UDS constituent elements.

[0099] In addition to the above references Figure 5 In addition to the process described via AF, UDSM can also directly receive UDS components through an external interface managed by the mobile network operator (MNO). In this case, the information registration process can follow the methods specified by the system managed by the mobile network operator.

[0100] Figure 6 A flowchart illustrating a method for deploying a UDS on the network side by a UDSM according to an embodiment of this disclosure is shown.

[0101] refer to Figure 6 UDSM can pass the NF image (or the address of the repository where the NF image is stored) and its description, and can request Operations Management and Maintenance (OAM) to generate the NF (S601).

[0102] This description may include service requirements passed from the AF and service operation policies passed from the PCF, and may also include information that the OAM needs or that is helpful in determining the deployment environment of the corresponding NF.

[0103] OAM can provide request-response type services to allow UDSM to access management functions within the network function management layer through the management service (MnS) interface.

[0104] OAM can perform NF deployment (S602) and can send a success response to UDSM (S603). In step S603, OAM can send the NF identifier (ID) and NF address together in the response message.

[0105] Figure 7 A flowchart illustrating a method for removing a UDS deployed on a network by a UDSM according to an embodiment of this disclosure is shown.

[0106] refer to Figure 7 The UDSM can use the NF identifier (ID) and NF address to request the OAM to remove the NF (S701), and the OAM can receive the message about the NF removal request from the UDSM, remove the specified NF accordingly (S702), and send a response message about the NF removal to the UDSM (S703).

[0107] Figure 8 A flowchart illustrating a method by which a UDSM configures a messaging path for each UDS within a network, according to an embodiment of this disclosure, is shown.

[0108] Figure 9 A flowchart illustrating a method for modifying the message passing path configured for each UDS by the UDSM according to an embodiment of this disclosure is shown.

[0109] refer to Figure 8 UDSM can determine the appropriate routing layer by referring to the protocols and routing requirements used by each UDS.

[0110] According to embodiments of this disclosure, the UDS can use one of protocols such as NAS, TCP, UDP, or QUIC, and routing requirements may include specific field values ​​in the UDS packet header for destination differentiation.

[0111] According to embodiments of this disclosure, when the UDS uses the NAS protocol, the UDSM can assign a unique Extended Protocol Authentication Device (EPD) to the corresponding service and pass the address of the UDS NF mapped to the EPD along with the address of the routing layer to the network entity.

[0112] UDSM can request each network entity that includes the routing layer to configure the routing environment for the corresponding layer.

[0113] According to embodiments of this disclosure, when the UDS does not use the NAS protocol, it can request the allocation of a new signaling radio bearer (SRB) for IP packets in the network-side AS layer, and subsequently apply IP routing to packets delivered via the corresponding SRB. The UDSM can send the corresponding UDS NF address along with the request for the new SRB.

[0114] To configure messaging paths for each UDS, the network entity (NE) and RAN entity where the NAS anchor resides can provide services to the UDSM for the creation, modification, or removal of routes.

[0115] - The route creation request (S801) may include UDS ID, target layer, rule ID, message identification standard, destination address, etc.

[0116] - A route modification request (S901) may include the rule ID to be added or removed, additional information (e.g., message identification criteria, destination address), etc.

[0117] - A route removal request (not shown) can be used to completely remove a route configuration using a UDS ID.

[0118] A network entity (NE) or RAN entity can receive requests for route creation, modification, or removal from the UDSM and perform route creation (S802), route update (S902), or route removal (not shown) accordingly. It can then send a response to the UDSM for route creation (S803), route modification (S903), or route removal (not shown).

[0119] Figure 10 A flowchart illustrating a method for deploying a UE container according to an embodiment of this disclosure is shown.

[0120] Figure 11 A flowchart of a method for removing a UE container according to an embodiment of this disclosure is shown.

[0121] The UDSM can use the NAS protocol to request the UDS agent to deploy (S1001) or remove (S1101) the UE container.

[0122] When a deployment request for the UE container is made (S1001), the UDSM can pass the UDS ID and information about the previously determined routing layer to the UDS agent. According to embodiments of this disclosure, when the UDS uses a protocol other than the NAS protocol, the UDSM can pass the UDS ID and information about the SRB to be used (e.g., SRB index) to the UDS agent.

[0123] When a deployment request for a UE container is made (S1001), the UDSM can directly pass the image of the UE container, or pass the address of a separate repository storing the UE container image, allowing the UDS agent to directly download the UE container image from the corresponding address.

[0124] When UDSM directly delivers the UE container image, it can deliver metadata such as filename, version, and size separately from the bit string corresponding to the file content. Conversely, when UDSM uses a repository instead of directly delivering the UE container image, it can deliver the UE container image to the UDS agent along with protocol information (e.g., HTTP, FTP, etc.), port, the address of the corresponding image, access information (account information, security keys, etc.).

[0125] When a request is made to remove the UE container (S1101), the UDSM can use the UDS ID.

[0126] After receiving a deployment request (S1001) or removal request (S1101) for a UE container from the UDSM, the UDS agent can execute the deployment (S1004) or removal (S1102) of the UE container and pass the result of the execution to the UDSM (S1005 or S1103).

[0127] Figure 12A flowchart illustrating a method for connecting a UDS agent and a UDSM according to an embodiment of this disclosure is provided.

[0128] According to embodiments of this disclosure, the connection between the UDS agent and the UDSM can be implemented via the NAS protocol.

[0129] The UDS agent can receive NAS-related information to be used for connecting to the UDSM via the registration completion message (S1202). According to an embodiment, the AS (modem) in the user equipment (UE) can receive the registration completion message via the AS anchor point on the network (S1202), and then pass the EPD information to the UDS agent in the user equipment (S1203).

[0130] The UDS agent can use the received EPD information to send a connection request message to the UDSM (S1204). The connection request message may include information such as the UE ID, the version of the UDS agent, and a list and version of the running UE containers.

[0131] After receiving a connection request message from the UDS agent (S1204), the UDSM can transmit a response message about the request to the UDS agent through the AS anchor point and the user equipment's modem (S1205).

[0132] According to embodiments of this disclosure, when in Figure 12 When an update to a higher version of the UE container is required after an operation, UDSM can perform the UE container update through the UE container deletion and deployment request.

[0133] Figure 13 The connection structure of logical devices within a user equipment according to an embodiment of the present disclosure is shown.

[0134] refer to Figure 13 The modem of the user equipment can be configured and provide an interface (radio interface layer, RIL) to exchange information with the UDS agent.

[0135] A vendor RIL is a layer that provides communication capabilities for exchanging information with the software or hardware responsible for a specific wireless connection, such as the wireless communication modem and chipset within a user equipment. A Radio Interface Layer (RIL) daemon (rild) can dynamically load a vendor RIL to control devices and provide functions such as receiving responses from devices.

[0136] Figure 14 A flowchart is shown illustrating a method for deploying a UE container and performing initial configuration by a UDS agent according to an embodiment of this disclosure.

[0137] The UDS agent can receive the UE container image via NAS messages from the UDSM and install the image into the user equipment's storage space. According to embodiments of this disclosure, when the UDSM uses a repository, it provides the UDS agent with information about the repository storing the UE container image. The UDS agent can then use the repository access information to receive and install the UE container image from the repository. The UDS agent may have permissions to configure the environment necessary for the UE container to operate within the terminal (e.g., configure and manage a virtualization environment) in order to install the UE container image within the user equipment.

[0138] When installing a UE container, the UDS agent can configure the message passing path of the UE container based on the protocol information received from the UDSM.

[0139] According to an embodiment of this disclosure, when the UDS uses the NAS protocol, the UDS agent can execute an allocation request for the SAP of the corresponding UDS to the AS layer in the terminal (S1403), and can receive a response to it (S1404).

[0140] According to another embodiment of this disclosure, when the UDS does not use the NAS protocol, the UDS agent can configure the SRB to be used through the kernel's IP protocol stack based on the SRB information and RLC channel information transmitted from the UDSM (S1407).

[0141] The UDS agent can perform the deployment of the UE container and send the results to the UDSM (S1411).

[0142] When the UDSM requests the deletion of a UE container, the UDS agent can use the UDS ID to delete the corresponding UE container and pass the result to the UDSM.

[0143] Figure 15 A flowchart of a method for updating UDS transmission information according to an embodiment of this disclosure is shown.

[0144] Because user equipment is mobile, it can perform a handover to a base station. The UDS agent can receive handover event notifications from the user equipment's modem and respond to potential changes in the NAS anchor or IP anchor that may occur during the handover.

[0145] The UDS agent can receive handover event notifications from the user equipment's modem (S1501). When a handover involving changes in network entities occurs (e.g., handover between gNBs), the modem can notify the UDS agent of the occurrence of the corresponding event.

[0146] The UDSM can receive update messages about the handover from the UDS agent (S1502), determine the change of the NAS anchor point based on the final source, and perform an update accordingly (S1503). For example, when data from a specific user equipment that was initially received through the first NAS anchor point is later received through the second NAS anchor point, the UDSM can determine that the NAS anchor point has changed.

[0147] After determining the change of the NAS anchor point, the UDSM can send an update message about the location of the user equipment to the UDS NF that uses the NAS protocol (S1505).

[0148] When the UDS does not use the NAS protocol, upon a handover event, the UDS agent can send a mobility-related update command to the UE container of the UDS that does not use the NAS protocol (S1508). The UDS NF that does not use the NAS protocol can receive the user equipment's mobility-related update request message from the UE container that does not use the NAS protocol (S1509), determine the change of the IP anchor point based on the final source of the message, and perform the update (S1510). Subsequently, a response to the mobility update request can be sent to the UE container that does not use the NAS protocol (S1511).

[0149] Figure 16 A flowchart of the UDS deployment and message exchange process according to an embodiment of this disclosure is shown.

[0150] exist Figure 16 In this context, UDP is used as the transport protocol, and the deployment and message exchange of UDS are performed on a network configured with one UDS NF and one UE container.

[0151] The AF can send a UDS registration request to the UDSM via the PCF (S1601) and receive a response to it. The UDS registration request message sent by the AF may include the UDS ID, UDS version, UDS NF image, UE container image, and information indicating the use of the UDP protocol. After receiving the UDS registration request from the AF, the PCF can forward the UDS registration request to the UDSM, along with information about necessary service operation policies.

[0152] The UDSM can send a mirror image of the UDS NF in the registered UDS components to the OAM and request the deployment of the UDS NF within the network (S1602). The OAM can then execute the deployment of the UDS NF in accordance with this request (S1603).

[0153] After deploying the UDS NF in the network, OAM can send a response (S1604) to UDSM regarding the successful deployment. The response regarding the successful deployment may include the NF ID and the network address of the NF.

[0154] The UDSM can request the RAN node to configure the transport path in order to configure the network-side transport environment for the UDS using UDP (S1605). The transport path configuration request from the UDSM may include information indicating that the layer on which routing can be performed is the IP layer. Since the UDS does not use the NAS protocol, the route configuration request does not necessarily have to include the address of the UDS NF. However, according to an embodiment, the UDSM may allow the NF's address to be included in the route configuration request and sent.

[0155] because Figure 16 In cases where the UDS uses IP routing, the RAN node can allocate a new SRB for the exchange of control messages configured by IP packets, pass information about it to the UDSM, and execute a response regarding the routing configuration (S1606). (See reference) Figure 16 In one embodiment, the UDSM requests route configuration by including A as the rule ID, and the RAN node responds to this request by assigning SRB4.

[0156] The UDSM can request the UDS agent to deploy the UE container (S1607), and the UDS agent accordingly deploys the UE container (S1608). (See reference) Figure 16 In one embodiment, the UDSM can convey the following information: a message can be sent to a UDS NF with a specific address via IP routing using SRB 4.

[0157] Based on information transmitted from the UDSM, the UDS agent can request the AS layer within the user equipment to establish a connection between the network and the corresponding SRB (S1609), and can receive a response to it. The AS layer can perform radio resource control (RRC) configuration through interaction with the RAN side of the network.

[0158] The UDS agent can pass connection information to the UE container (S1610). The passed connection information may include SRB information and the UDS NF address. Subsequently, the UDS agent can pass the UE container deployment results to the UDSM.

[0159] According to embodiments of this disclosure, during the process of exchanging control messages using the UDP / IP protocol between the UE container and the UDS NF, the node performing the IP anchor role can perform IP routing and simultaneously provide network address translation (NAT) functionality (S1611) to ensure that mobile user equipment within the system can communicate with network devices without problems.

[0160] Figure 17The structure of a terminal according to an embodiment of this disclosure is shown.

[0161] refer to Figure 17 The terminal may include a transceiver 1710, a controller 1720, and a storage device 1730. In this disclosure, the controller may be defined as a circuit, an application-specific integrated circuit (ASIC), or at least one processor.

[0162] Transceiver 1710 can send signals to and receive signals from other network entities. For example, transceiver 1710 can receive system information from a base station and can receive synchronization signals or reference signals.

[0163] The controller 1720 can control the overall operation of the terminal as provided in this disclosure. For example, the controller 1720 can control the overall functionality of the terminal according to the embodiments provided in this disclosure. For example, the controller 1720 can control the terminal or UE to perform the deployment or deletion of a UE container.

[0164] Storage device 1730 can store at least one of the information transmitted and received by transceiver 1710 or information generated by controller 1720. For example, storage device 1730 can store information about the UE container, information related to EPD, etc.

[0165] Figure 18 The structure of a network entity according to an embodiment of this disclosure is shown. The network entity can be configured from AMF, UPF, UDSM, SMF, PCF, UDR, UDM, NEF, AF, etc.

[0166] Transceiver 1810 can send signals to and receive signals from other network entities. Transceiver 1810 can, for example, send information related to the deployment of the UDS service to a terminal.

[0167] Controller 1820 can control the overall operation of network entities according to the embodiments provided in this disclosure. For example, controller 1820 can operate to control operations according to the flowchart above. As an example, controller 1820 can control the UDSM to receive a UDS registration request from the AF, pass an image of the UDS NF to the OAM, and pass an image of the UE container to the UE agent.

[0168] Storage device 1830 may store at least one of the following: information transmitted and received by transceiver 1810 or information generated by controller 1820. For example, storage device 1830 may store UDS ID, UDS version, information about UDS NF, and information about UE container.

[0169] It should be noted that Figures 1 to 18The examples of configurations, control / data transmission methods, operating procedures, and constituent elements shown herein are not intended to limit the scope of this disclosure. That is, they should not be construed as... Figures 1 to 18 All constituent elements, entities, or operations described herein are not to be construed as essential constituent elements of this disclosure, but may be implemented only in part without prejudice to the nature of this disclosure.

[0170] The operation of the network entity or terminal as described above can be achieved by providing a memory device storing the corresponding program code in a component of the network entity or terminal device. That is, in order to perform the above operations, the controller of the network entity or terminal device can read and execute the program code stored in the memory device through a processor or central processing unit (CPU).

[0171] The various constituent elements or modules of the network entities, base stations, and terminal equipment described above can be operated using hardware circuitry, such as complementary metal-oxide-semiconductor (CMOS)-based logic circuits, firmware, software, and / or combinations of hardware and firmware, and / or software inserted into a machine-readable medium. As an example, various electrical structures and methods can be implemented using transistors, logic gates, and electrical circuitry such as application-specific integrated circuits (ASICs).

[0172] While specific embodiments have been described in detail in this disclosure, it will be apparent that various modifications can be made without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined by the following claims and their equivalents.

[0173] Although this disclosure has been described with reference to various embodiments, those skilled in the art can suggest various changes and modifications. This disclosure is intended to cover such changes and modifications that fall within the scope of the appended claims.

Claims

1. A method for operating a user-defined service (UDS) performed by a first network entity in a wireless communication system, the method comprising: Receives a UDS registration process request message from the application function AF, the UDS registration process request message including UDS network function NF information and UE container information; Send a request message for UDS deployment to Operations Management and Maintenance (OAM), the request message including the UDS NF information; as well as A UE container deployment request message is sent to the UDS agent in the user equipment (UE), the UE container deployment request message including the UE container information.

2. The method according to claim 1, further comprising: Send a routing configuration request message for the deployment of the UDS to the second network entity.

3. The method according to claim 2, further comprising: When the protocol used by the UDS is Non-Access Stratum (NAS), an Extended Protocol Discriminator (EPD) is assigned to the UDS. The routing configuration request message includes the address information of the UDS NF mapped to the EPD.

4. The method according to claim 2, wherein, When the protocol used by the UDS is not NAS, the routing configuration request message includes a signaling radio bearer (SRB) allocation request for Internet Protocol (IP) packets.

5. The method according to claim 1, further comprising: Receive handover event-related information for the UE from the UDS agent; Based on the NAS anchor point information, determine the change of the NAS anchor point that transmits the information related to the switching event; as well as When the NAS anchor point has changed, send information about the change to the UDS NF.

6. A method performed by a User Defined Service (UDS) agent included in a User Equipment (UE) in a wireless communication system, the method comprising: Receive a UE container deployment request message from the first network entity, the UE container deployment request message including UE container information related to the UDS; Install the UE container into the UE; as well as Based on the UE container information, a message passing path is configured for the UE container.

7. The method according to claim 6, further comprising: Receive Extended Protocol Authentication Device (EPD) from the Access and Mobility Management Function (AMF); as well as Send a connection request message including the EPD to the first network entity.

8. The method according to claim 6, further comprising: When the protocol used by the UDS is Non-Access Stratum (NAS), the access stratum (AS) in the UE is requested to configure the Service Access Point (SAP) corresponding to the UDS.

9. The method according to claim 6, further comprising: When the protocol used by the UDS is not a non-access stratum (NAS), it requests the access stratum (AS) layer in the UE to configure the signaling radio bearer (SRB) based on the SRB information received from the first network entity.

10. The method of claim 6, further comprising: Receive handover event-related information from the UE's modem; as well as Send the handover event-related information to the first network entity.

11. A first network entity in a wireless communication system for operating a user-defined service (UDS), the first network entity comprising: transceiver; as well as A controller, operably coupled to the transceiver, is configured to: Receives a UDS registration process request message from the application function AF, the UDS registration process request message including UDS network function NF information and UE container information; Send a request message for UDS deployment to Operations Management and Maintenance (OAM), the request message including the UDS NF information; as well as A UE container deployment request message is sent to the UDS agent in the user equipment (UE), the UE container deployment request message including the UE container information.

12. The first network entity according to claim 11, wherein, The controller is also configured to send a routing configuration request message for the deployment of the UDS to a second network entity.

13. The first network entity according to claim 11, wherein, The controller is also configured to: Receive handover event-related information for the UE from the UDS agent; Based on the NAS anchor point information, determine the change of the NAS anchor point that transmits the information related to the switching event; as well as When the NAS anchor point has changed, send information about the change to the UDS NF.

14. A UDS agent included in a user equipment (UE) in a wireless communication system, the UDS agent comprising: transceiver; as well as A controller, operably coupled to the transceiver, is configured to: Receive a UE container deployment request message from the first network entity, the UE container deployment request message including UE container information related to UDS; Install the UE container into the UE; as well as Based on the UE container information, a message passing path is configured for the UE container.

15. The UDS agent according to claim 14, wherein, The controller is also configured to: Receive Extended Protocol Authentication Device (EPD) from Access and Mobility Management Function (AMF); and Send a connection request message including the EPD to the first network entity.

Images