Processing apparatus and processing method

Abstract

We provide intent technology that can address medium- to long-term challenges. [Solution] The processing device includes a receiving unit that receives a request for a resilient intent from a requesting device, and a control unit that stores parameters related to the resilient intent in a parameter table based on the request, and creates a change plan for the managed object based on the parameters.

Description

Technical Field

[0004] , , , , , , , , , , ,

[0001] The present invention relates to intent-driven management services in a mobile network.

Background Art

[0002] In 3GPP (Registered Trademark) (3rd Generation Partnership Project), in order to achieve further increase in system capacity, further increase in data transmission speed, further reduction in latency in a radio section, etc., a wireless communication method called 5G or NR (New Radio) (hereinafter, this wireless communication method is referred to as "5G" or "NR") has been introduced. In 5G, various wireless technologies have been introduced in order to meet the requirement conditions of achieving a throughput of 10 Gbps or more and reducing the latency in the radio section to 1 ms or less. Furthermore, studies on 6G, which is a future communication system, are also being conducted.

[0003] Also, in 3GPP (Registered Trademark), intent-driven management services for mobile networks have been studied (Non-Patent Documents 1 to 3). Intent-driven management means autonomous operation of a mobile network according to an intent.

Prior Art Documents

Non-Patent Documents

[0005] Conventional intent technologies disclosed in Non-Patent Documents 1-3, etc., are considered effective for addressing immediate problems or immediate requirements. However, conventional intent technologies cannot address medium- to long-term problems (or requirements) that may arise several months or years from now.

[0006] This invention has been made in view of the above points, and aims to provide intent technology that can address medium- to long-term challenges. [Means for solving the problem]

[0007] According to the disclosed technology, a receiving unit receives a request for a resilient intent from a requesting device, Based on the above request, a control unit stores the parameters related to the resilient intent in a parameter table and creates a change plan for the managed object based on the parameters. A processing device is provided that includes the following. [Effects of the Invention]

[0008] According to the disclosed technology, intent technology capable of addressing medium- to long-term challenges will be provided. [Brief explanation of the drawing]

[0009] [Figure 1] This is a diagram illustrating an example of a communication system. [Figure 2] This diagram illustrates an example of a communication system in a roaming environment. [Figure 3] This figure shows an example of a system configuration in an embodiment of the present invention. [Figure 4] This figure shows an example of a resilient intent parameter table. [Figure 5] This is a diagram illustrating example 1 of the operation. [Figure 6] It is a diagram showing an example of parameters (Input parameters) in Operation Example 1. [Figure 7] It is a diagram showing an example of parameters (Output parameters) in Operation Example 1. [Figure 8] It is a diagram for explaining Operation Example 2. [Figure 9] It is a diagram for explaining Operation Example 3. [Figure 10] It is a diagram for explaining Operation Example 4. [Figure 11] It is a diagram showing an example of parameters (Input parameters) in Operation Example 4. [Figure 12] It is a diagram showing an example of parameters (Input parameters) in Operation Example 4. [Figure 13] It is a diagram showing an example of parameters (Output parameters) in Operation Example 4. [Figure 14] It is a diagram showing an example of parameters (Input parameters) in Operation Example 4. [Figure 15] It is a diagram showing an example of parameters (Output parameters) in Operation Example 4. [Figure 16] It is a diagram for explaining Operation Example 4. [Figure 17] It is a diagram showing an example of the functional configuration of the processing device 10 in an embodiment of the present invention. [Figure 18] It is a diagram showing an example of the functional configuration of the request device 20 in an embodiment of the present invention. [Figure 19] It is a diagram showing an example of the hardware configuration of the processing device 10 and the request device 20 in an embodiment of the present invention. [Figure 20] It is a diagram showing an example of the configuration of the vehicle 2001 in an embodiment of the present invention.

Embodiments for Carrying Out the Invention

[0010] Embodiments of the present invention will be described below with reference to the drawings. Note that the embodiments described below are examples, and the embodiments to which the present invention is applied are not limited to those described below.

[0011] In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies may be used as appropriate. However, such existing technologies include, but are not limited to, existing LTE or existing NR.

[0012] Below, we will first describe an example of a mobile network configuration to which intent-driven management services are applied, and then explain the configuration and operation related to intent-driven management services.

[0013] Figure 1 is a diagram illustrating an example of a communication system equivalent to a mobile network. As shown in Figure 1, this communication system consists of a UE and multiple network nodes. Hereafter, one network node will be assigned to each function, however, one network node may implement multiple functions, or multiple network nodes may implement one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.

[0014] The RAN (Radio Access Network) is a network node with radio access capabilities, which may include base stations, and is connected to the UE, AMF (Access and Mobility Management Function), and UPF (User plane function). The AMF is a network node that has functions such as terminating the RAN interface, terminating the NAS (Non-Access Stratum), registration management, connection management, reachability management, and mobility management. The UPF is a network node that interconnects with the DN (Data Network) and has functions such as PDU (Protocol Data Unit) session points to the outside, packet routing and forwarding, and user plane QoS (Quality of Service) handling. The UPF and DN constitute a network slice.

[0015] AMF is connected to UE, RAN, SMF (Session Management function), NSSF (Network Slice Selection Function), NEF (Network Exposure Function), NRF (Network Repository Function), UDM (Unified Data Management), AUSF (Authentication Server Function), PCF (Policy Control Function), and AF (Application Function). AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes that are interconnected via interfaces based on their respective services: Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0016] SMF is a network node with functions such as session management, IP (Internet Protocol) address allocation and management for UEs, DHCP (Dynamic Host Configuration Protocol) functionality, ARP (Address Resolution Protocol) proxy, and roaming functionality. NEF is a network node with the function of notifying other NFs (Network Functions) of capabilities and events. NSSF is a network node with functions such as selecting the network slice to which the UE connects, determining the allowed NSSAI (Network Slice Selection Assistance Information), determining the NSSAI to be set, and determining the AMF set to which the UE connects. PCF is a network node with the function of controlling network policies. AF is a network node with the function of controlling application servers. NRF is a network node with the function of discovering NF instances that provide services. UDM is a network node that manages subscriber data and authentication data. UDM is connected to UDR (User Data Repository) which holds this data.

[0017] Figure 2 is a diagram illustrating an example of a communication system in a roaming environment. As shown in Figure 2, the network consists of an UE and multiple network nodes.

[0018] SEPP is an opaque proxy that filters control plane messages between PLMNs (Public Land Mobile Networks). Figure 2 shows vSEPP as the SEPP in the visited network, and hSEPP as the SEPP in the home network.

[0019] As shown in Figure 2, the UE is in a roaming environment connected to the RAN and AMF in the VPLMN (Visited PLMN). The VPLMN and HPLMN (Home PLMN) are connected via vSEPP and hSEPP. The UE can communicate with the HPLMN's UDM, for example, via the VPLMN's AMF.

[0020] (Regarding intent-driven management services) As mentioned above, 3GPP (registered trademark) is considering intent-driven management services for mobile networks (see, for example, Non-Patent Documents 1-3). Intent-driven management refers to the autonomous operation of mobile networks according to intents.

[0021] As described in Non-Patent Document 1, an intent represents expectations, including requirements, goals, and constraints for a particular service. Furthermore, an intent places more emphasis on "what" needs to be achieved than on "how" the result will be achieved. "Intent" can also be rephrased as "intention" or "request."

[0022] As described in Non-Patent Document 1, in an Intent-Driven Management Service (Intent-Driven MnS), the MnS Consumer presents an intent to the MnS Producer, which interprets the intent and takes action. MnS is an abbreviation for "management service."

[0023] Hereinafter, the entity corresponding to the MnS Consumer will be referred to as the requesting device, and the entity corresponding to the MnS Producer will be referred to as the processing device. The requesting device may also be referred to as the Intent requesting device, and the processing device as the Intent processing device.

[0024] The requesting device and the processing device may both be a single device (such as a terminal, base station, server, or network node) or a system consisting of multiple devices. Furthermore, the requesting device and the processing device may be located at any position on the network.

[0025] (Example of a use case) As an example, we will describe a use case involving an intent containing an expectation on radio network performance to be assured.

[0026] In this case, the requesting device presents an intent to the processing unit that includes an expectation of ensuring wireless network performance (e.g., throughput). The information in the presented intent may include, for example, area information, RAT information, and performance targets.

[0027] Upon receiving intent information that includes an expectation to ensure wireless network performance, the processing unit collects data on the relevant wireless network based on the intent information, identifies problems with wireless network performance (e.g., low throughput in a certain area), determines configuration parameters to improve them, and adjusts those configuration parameters.

[0028] The processing unit continuously monitors the performance of the wireless network and determines whether the wireless network performance targets are being met. The processing unit notifies the requesting device of intent fulfillment information indicating whether the intent has been fulfilled.

[0029] (Regarding the issues) In existing intent technologies disclosed in Non-Patent Literature Documents 1-3, etc., the technical specifications are determined based on the premise of short-term problem solving, ranging from a few minutes, a few hours, or even a few days, from specifying the goals and requirements to obtaining the results.

[0030] For example, consider a case where an intent requested by a requesting device (MnS Consumer) to a processing device (MnS Producer) relates to a cloud server within the resources managed by the operator providing the mobile network. Based on the intent, if the processing device detects that a specific cloud server is running low on memory and is causing an overall bottleneck, it resolves the bottleneck by scaling out that specific cloud server (increasing the number of cloud servers).

[0031] The above processing steps are an example of how intents can be used to solve localized and short-term operator problems.

[0032] While conventional intent technologies like those described above are effective for immediate problems or requirements, they cannot address medium- to long-term problems or requirements several months or years from now.

[0033] For example, with conventional technology, even if an intent is generated and registered as a requirement for several months or several years when the budget available for cloud services is fixed, it may not be possible to perform the expected action.

[0034] Furthermore, medium- to long-term intents are generally considered to have a higher priority than short-term intents. However, there may also be cases where short-term intents with a higher priority than medium- to long-term intents are necessary. Since it is anticipated that many short-term intents will be input after medium- to long-term intents have been entered into the processing unit, it is necessary to consider the consistency and priority of these intents.

[0035] It should be noted that the relationship between periods considered "short-term" and those considered "medium- to long-term" is relative. For example, if an intent spanning one hour is considered a short-term intent, then an intent spanning ten hours may be referred to as a "medium- to long-term intent."

[0036] Hereinafter, the intent introduced in this embodiment (e.g., medium- to long-term intents) will be referred to as "resilient intents" in contrast to existing intents (e.g., short-term intents). Existing intents will be referred to as "normal intents." In cases where it is clear from the context that an intent is a "resilient intent," it may be referred to simply as "intent."

[0037] The name of the intent introduced in this embodiment is not limited to "resilient intent." The intent introduced in this embodiment may be called by a name other than "resilient intent" (e.g., new intent, medium- to long-term intent, elastic intent).

[0038] (System Configuration) Figure 3 shows an example of the system configuration in this embodiment. As shown in Figure 3, this system has a processing unit 10 and a requesting device 20. The processing unit 10 and the requesting device 20 can communicate with each other via a network. Figure 3 also shows a managed object 30. The managed object 30 is, for example, a mobile network. Although Figure 3 shows one processing unit 10 and one requesting device 20, generally multiple processing units 10 and multiple requesting devices 20 are provided.

[0039] The requesting device 20 corresponds to an MnS Consumer. The processing unit 10 corresponds to an MnS Producer. As mentioned above, both the requesting device 20 and the processing unit 10 may be a single device (terminal, base station, server, network node, etc.) or a system consisting of multiple devices. Furthermore, both the requesting device 20 and the processing unit 10 may be located anywhere on the network. Both the requesting device 20 and the processing unit 10 may be devices within a 5G or 6G core network.

[0040] In this embodiment, it is assumed that both normal intents and resilient intents are used.

[0041] (Summary of device operation) In this embodiment, the processing unit 10 has, for example, a resilient intent parameter table (sometimes simply called a parameter table) for each resilient intent. If there are multiple processing units 10, each processing unit 10 has a resilient intent parameter table. The processing unit 10 also normally maintains a parameter table for intents.

[0042] The set of values ​​stored in the parameter table corresponds to the resilient intent. If there is a change in the parameter value, the processing unit 10 notifies the relevant parameter table and implements the change in the parameter value.

[0043] The requesting device 20 may create the resilient intent as a policy, or the processing device 10 may create all or part of the resilient intent.

[0044] In this embodiment, the processing unit 10 can flexibly create (or recreate) parameter values ​​(e.g., values ​​corresponding to the plan) for the resilient intent, within a range that does not affect the normal intent. It is assumed that the technical specifications for this technology will be additional technical specifications that do not affect the technical specifications for the normal intent.

[0045] The processing unit 10 executes the resilient intent during periods when normal intents are not being executed (gap time), or at locations where normal intents are not being executed (locations in the managed object 30).

[0046] Figure 4 shows an example of a resilient intent parameter table for a certain resilient intent held by the processing unit 10. Note that the table shown in Figure 4 may represent one resilient intent, or one Intent parameter in the table shown in Figure 4 may represent one resilient intent.

[0047] In Figure 4, the "Intent parameter" indicates the target (e.g., throughput) in a resilient intent. In the example in Figure 4, the values ​​corresponding to the Intent parameter are "Related MnS Producer" (the processing unit associated with that Intent parameter), "start time," "Period (or end time)," and "Intent Goal" in weekly units.

[0048] "start time" is the start date and time for the execution of the process for the corresponding "Intent parameter," "Period" is the period for which the process is executed, and "end time" is the end date and time for the execution of the process. The process for the "Intent parameter" is, for example, to monitor and control the managed object 30 in order to satisfy the objective for that "Intent parameter."

[0049] Performing processing on an "Intent parameter" can also be described as "executing a resilient intent."

[0050] In Figure 4, "Intent Goal" refers to the target for the corresponding "Intent parameter" in the resilient intent. In the example in Figure 4, weekly "Intent Goals" are set.

[0051] Below, we will describe five operation examples of a communication system having a requesting device 20 and a processing device 10. In the following description, "parameter" is used to include "parameter value".

[0052] (Example of operation 1) Operation Example 1 will be explained with reference to Figure 5. In S101 (step 101), the requesting device 20 sends a resilient intent request to the processing device 10. The resilient intent request includes parameters related to the resilient intent as a policy. These parameters are input to the processing device 10.

[0053] In S102, the processing unit 10 copies (stores) the parameters related to the resilient intent received from the requesting device 20 into the resilient parameter table. The processing unit 10 can also generate parameters related to the resilient intent.

[0054] In S103, the processing unit 10 uses the parameters in the resilient parameter table to calculate the necessary changes and amounts of changes for the managed object 30 in the medium to long term. The processing unit 10 uses the calculated changes and amounts of changes to formulate a change plan for the managed object 30. This change plan may also be called a resilient change plan.

[0055] In S104, the processing unit 10 sends a resilient intent response to the requesting device 20 as a response to the resilient intent request. Note that the timing of sending the resilient intent response may be after S101 and before S102.

[0056] Figure 6 shows an example of input parameters entered into the processing unit 10 as a resilient intent request. Figure 7 shows an example of output parameters sent from the processing unit 10 to the requesting device 20.

[0057] Let's explain a concrete example of creating a change plan. For example, suppose the managed system 30 is a mobile network covering a certain area (let's call it Area A), and the resilient intent is specified with monthly parameters. For example, suppose the resilient intent is specified as follows: "After 1 month: Number of users = N1, throughput = TH1", "After 2 months: Number of users = N2, throughput = TH2", ..., "After 12 months: Number of users = N12, throughput = TH12".

[0058] In this case, for example, the processing unit 10 calculates the number of cloud servers that make up the mobile network necessary to satisfy the above intent on a monthly basis, and uses the calculation result as a change plan for the number of cloud servers.

[0059] (Example of operation 2) In operation example 1, the resilient intent request in S101 may be a request representing a specific and detailed intent, or a request representing an ambiguous intent. If the resilient intent request represents an ambiguous intent, the processing unit 10 can create a specific and detailed intent from the received ambiguous intent request. The processing unit 10 may use AI / ML (AI / machine learning) to create this incident, or it may create it according to a policy (rule) that has been input in advance from the request device 20 or input on the processing unit 10 side.

[0060] As a resilient intent request, an operation example when a request representing an ambiguous intent is used is described as Operation Example 2 with reference to FIG. 8. Here, the differences from Operation Example 1 (FIG. 5) are described.

[0061] In S111, the request device 20 transmits a request representing an ambiguous intent to the processing device 10. In S112, the processing device 10 generates a specific and detailed resilient intent (specifically, detailed parameters) from the ambiguous intent request. S113 to S115 are the same as S102 to S104 in Operation Example 1.

[0062] For example, the request device 20 transmits an ambiguous intent such as "Provide a wireless communication service with good quality continuously in the long term in Area A" to the processing device 10 as a request representing an ambiguous intent. The processing device 10 generates a specific plan (for example, the plan every month described in Operation Example 1) from the ambiguous intent by utilizing, for example, an AI model.

[0063] (Operation Example 3) Operation Example 3 is an operation example common to Operation Example 1 and Operation Example 2. In Operation Example 3, the operation example of the processing device 10 after creating a resilient change plan is described. Operation Example 3 is described according to the procedure of the flowchart in FIG. 9.

[0064] <S121: Implement change> In S121, the processing device 10 implements the change of the management target 30 according to the resilient change plan.

[0065] <S122: Update process 1> In S122, when the processing device 10 determines to change the management target 30 upon receiving a normal intent (short-term intent), it checks whether the change affects the parameters constituting the resilient intent.

[0066] When the confirmation result is No (no impact), the processing device 10 performs normal procedures for normal intent.

[0067] When the confirmation result is Yes (has an impact), after the processing device 10 executes the normal intent, it updates the resilient parameter table with new parameters.

[0068] For example, when the configuration of the cloud server (number of servers, etc.) is changed as a result of the execution of the normal intent, etc., the resilient parameter table is updated with new parameters according to the change.

[0069] <S123: Update Process 2> In S123, when the processing device 10 determines to perform a change to the management target 30 upon receiving a resilient intent, after executing the resilient intent, it updates the parameter table of the normal intent with new parameters.

[0070] <S124: Update Process 3> In S124, when the processing device 10 determines to perform a change to the management target 30 upon receiving a resilient intent, after executing the resilient intent, it updates the parameter table of the existing resilient intent with new parameters.

[0071] Note that S124 may be a subsequent process to S123, or only one of S124 and S123 may be executed.

[0072] (Operation Example 4) In Operation Example 4, when the processing unit 10 detects a change in the status of a resilient intent, it notifies the requesting device 20 of that change. This change is, for example, a change in the value of Intent Goal. More specifically, the change is notified using a subscribe-notify method. That is, the requesting device 20 subscribes to the resilient intent from the processing unit 10 separately from normal intents, and the processing unit 10 notifies the requesting device 20 of the change if there is a change in the status.

[0073] Refer to Figure 10 to explain Operation Example 4. In S201, the requesting device 20 sends a resilient intent subscription request to the processing device 10. The resilient intent subscription request may include notification conditions (e.g., notify if there is a change in the resilient intent requested by the requesting device 20).

[0074] In S202, the processing unit 10 returns a response to the subscription request to the requesting device 20.

[0075] In S203, the processing unit 10 determines that the notification conditions have been met. In S204, the processing unit 10 updates the resilient intent table. In S205, the processing unit 10 notifies the requesting device 20 of the changes to the resilient intent.

[0076] Figures 11 and 12 show examples of parameters (input parameters) sent from the requesting device 20 to the processing device 10 in S201.

[0077] Figure 13 shows an example of the parameters (Output parameters) sent from the processing unit 10 to the requesting device 10 in S202.

[0078] Figure 14 shows an example of the parameters (input parameters) generated (updated) by the processing unit 10 in S204.

[0079] Figure 15 shows an example of the parameters (Output parameters) sent from the processing unit 10 to the requesting device 10 in S205.

[0080] (Example of operation 5) Next, we will explain Operation Example 5. In Operation Example 5, when it is necessary to change the resilient intent, the processing unit 10 notifies other processing units 10 related to the resilient intent, and then performs the change to the resilient intent.

[0081] In this case, changes to the resilient intent should not affect the normal intent. Therefore, when a resilient intent should be changed, and a normal intent is executed, the execution of the normal intent takes priority, and only afterward is the change to the resilient intent parameter table performed using the modified resilient intent.

[0082] The processing example of Operation Example 5 will be explained with reference to Figure 16. In the example in Figure 16, processing units 10A, 10B, and 10C are shown. Processing units 10A and 10C are related to the resilient intent that processing unit 10B modifies.

[0083] In S301, the processing unit 10B modifies the resilient intent and updates the resilient intent parameter table.

[0084] In S302, the processing unit 10B sends a Resilient intent update notification to the processing unit 10C to notify it that the resilient intent has been updated. In S303, the processing unit 10B sends a Resilient intent update notification to the processing unit 10A.

[0085] In S304, the processing unit 10B sends a Resilient intent update implementation request to the processing unit 10C to request a resilient intent update. In S305, the processing unit 10C returns a Resilient intent update implementation response to the processing unit 10B.

[0086] In S306, the processing unit 10B sends a Resilient intent update implementation request to the processing unit 10A. In S307, the processing unit 10A returns a Resilient intent update implementation response to the processing unit 10B.

[0087] (Effects of the embodiment) As described above, the technology according to this embodiment can support resilient intent. This makes it possible to use intent to solve medium- to long-term issues such as budget or resource planning.

[0088] Furthermore, the technology according to this embodiment makes it possible to support or replace some of the medium- to long-term studies (e.g., resource planning, migration planning) that were previously carried out manually by experts, using intents, and the effects of intents are also significant.

[0089] (Device configuration) Next, we will describe an example of the functional configuration of the processing unit 10 and the requesting device 20 that perform the processes and operations described above.

[0090] <Processing device 10> Figure 17 is a diagram showing an example of the functional configuration of the processing unit 10. As shown in Figure 17, the processing unit 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Figure 17 is merely an example. Any functional classification and functional unit names are acceptable as long as they enable the operation according to the embodiment of the present invention.

[0091] The transmitting unit 110 includes the function of generating a signal to be transmitted to another device and transmitting the signal by wire or wireless. The receiving unit 120 includes the function of receiving various signals transmitted from other devices and obtaining information from the received signals, for example, information of a higher layer. A communication unit including the transmitting unit 110 and the receiving unit 120 may be configured.

[0092] The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to other devices in a storage device and reads it from the storage device as needed. The content of the setting information is, for example, information for configuring the managed object (wireless network, etc.). For example, the setting unit 130 holds a resilient intent parameter table. The control unit 140 controls the processing unit 10. For example, the control unit 140 creates and updates the resilient intent parameter table. The control unit 140 also executes intents. The signal transmission function unit of the control unit 140 may be included in the transmission unit 110, and the signal reception function unit of the control unit 140 may be included in the reception unit 120.

[0093] <Requesting device 20> Figure 18 shows an example of the functional configuration of the request device 20. As shown in Figure 18, the request device 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Figure 9 is merely an example. Any functional classification and functional unit names are acceptable as long as they enable the operation according to the embodiment of the present invention.

[0094] The transmitting unit 210 includes the function of generating a signal to be transmitted to another device and transmitting the signal by wire or wireless. The receiving unit 220 includes the function of receiving various signals transmitted from other devices and obtaining information from the received signals, for example, information of a higher layer. A communication unit including the transmitting unit 210 and the receiving unit 220 may be configured.

[0095] The setting unit 230 stores pre-set setting information and various setting information to be transmitted to other devices in a storage device and reads it from the storage device as needed. The control unit 240 controls the requesting device 20. The signal transmission function unit of the control unit 240 may be included in the transmission unit 210, and the signal reception function unit of the control unit 240 may be included in the reception unit 120.

[0096] (Hardware configuration) The block diagrams (Figures 17 and 18) used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may be realized by combining the one or more devices with software.

[0097] Functions include, but are not limited to, judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. As mentioned above, the method of implementation is not particularly limited.

[0098] For example, the processing unit 10 and requesting device 20 in one embodiment of the present disclosure may function as a computer that processes the communication method of the present disclosure. Figure 19 is a diagram showing an example of the hardware configuration of the processing unit 10 and requesting device 20 according to one embodiment of the present disclosure. The processing unit 10 and requesting device 20 described above may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like.

[0099] In the following explanation, the term "device" can be read as a circuit, device, unit, etc. The hardware configuration of the processing unit 10 and the requesting device 20 may include one or more of the devices shown in the figure, or it may be configured to omit some of the devices.

[0100] Each function in the processing unit 10 and the requesting device 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and the storage device 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of the reading and writing of data in the storage device 1002 and the auxiliary storage device 1003.

[0101] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the control unit 140, control unit 240, etc., described above may be implemented by the processor 1001.

[0102] Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 140 of the processing device 10 shown in Figure 17 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Also, for example, the control unit 240 of the request device 20 shown in Figure 18 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Although the above processes have been described as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may be transmitted from a network via a telecommunications line.

[0103] The storage device 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The storage device 1002 may also be called a register, cache, main memory, etc. The storage device 1002 can store executable programs (program code), software modules, etc., for implementing a communication method according to one embodiment of this disclosure.

[0104] The auxiliary storage device 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disc, a digital multipurpose disc, a Blu-ray® disc), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The above-mentioned storage medium may also be a database, server, or other suitable medium that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0105] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may include high-frequency switches, duplexers, filters, frequency synthesizers, etc., to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmit / receive antenna, amplifier section, transmit / receive section, transmission path interface, etc., may be implemented by the communication device 1004. The transmit / receive section may be implemented with physically or logically separated transmitting and receiving sections.

[0106] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0107] Furthermore, each device, such as the processor 1001 and the storage device 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.

[0108] Furthermore, the processing unit 10 and the requesting device 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0109] Figure 20 shows an example of the configuration of vehicle 2001. As shown in Figure 20, vehicle 2001 comprises a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021-2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in this disclosure may be applied to a communication device mounted on vehicle 2001, for example, to the communication module 2013. For example, a processing unit 10 or a requesting device 20 may be included in the communication module 2013.

[0110] The drive unit 2002 consists of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel, which is operated by the user.

[0111] The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (IO ports) 2033. Signals from various sensors 2021 to 2029 installed in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0112] Signals from various sensors 2021-2029 include current signals from current sensor 2021 which senses motor current, front and rear wheel rotation speed signals obtained by rotation speed sensor 2022, front and rear wheel air pressure signals obtained by air pressure sensor 2023, vehicle speed signals obtained by vehicle speed sensor 2024, acceleration signals obtained by acceleration sensor 2025, accelerator pedal depression signals obtained by accelerator pedal sensor 2029, brake pedal depression signals obtained by brake pedal sensor 2026, shift lever operation signals obtained by shift lever sensor 2027, and detection signals obtained by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0113] The Information Services Unit 2012 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Services Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001. The Information Services Unit 2012 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) and output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

[0114] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also sends and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

[0115] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via its communication port. For example, the communication module 2013 sends and receives data via its communication port 2033 to the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021-29 provided in the vehicle 2001.

[0116] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station or a mobile station.

[0117] The communication module 2013 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 2021-2028 input to the electronic control unit 2010, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 2012. The electronic control unit 2010, the various sensors 2021-2028, the information service unit 2012, etc., may also be called input units that accept input.

[0118] The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit, which outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from the external device in memory 2032, which is available to the microprocessor 2031. Based on the information stored in memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021-2029, etc., provided in the vehicle 2001.

[0119] This specification discloses at least the configurations described in the following appendix. <Note> (Additional note 1) A receiving unit that receives a request for a resilient intent from a requesting device, Based on the above request, a control unit stores the parameters related to the resilient intent in a parameter table and creates a change plan for the managed object based on the parameters. A processing device equipped with the following features. (Additional note 2) The control unit stores the parameters received from the requesting device, or the parameters generated by the control unit, in the parameter table. The processing apparatus described in Appendix 1. (Additional note 3) The parameter table stores the intent target values ​​for each predetermined period as parameters. The processing apparatus described in Appendix 1. (Additional note 4) When a change occurs to the managed object based on a normal intent, and the control unit determines that the change affects the parameter, it will update the parameter table with the new parameter after executing the normal intent. The processing apparatus described in Appendix 1. (Additional note 5) When a change occurs to the managed object based on the resilient intent, the control unit updates the parameter table or the parameter table of the normal intent with the new parameters after executing the resilient intent. The processing apparatus described in Appendix 1. (Additional note 6) The steps include receiving a request for a resilient intent from the requesting device, Based on the above request, the parameters related to the resilient intent are stored in a parameter table, and based on the above parameters, a change plan for the managed object is created. A processing method performed by a processing device, comprising the above.

[0120] According to any of the appendices 1 to 6, intent technology capable of addressing medium- to long-term challenges can be provided. According to appendice 2, either parameters received from the requesting device or parameters generated by the control unit can be stored in the parameter table. According to appendice 3, for example, medium- to long-term targets can be set as resilient intents. According to appendice 4, the parameter table of the resilient intent can be updated in response to the execution of a normal intent. According to appendice 5, either the parameter table of the resilient intent or the parameter table of the normal table can be updated in response to the execution of a resilient intent.

[0121] (Supplement to the embodiment) While embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. Regarding the processing procedures described in the embodiments, the order of processing may be changed as long as it does not contradict each other. For the convenience of explaining the processing, the processing unit 10 and the requesting device 20 have been described using functional block diagrams, but such devices may be implemented in hardware, software, or a combination thereof. The software operated by the processor of the base station 10 according to an embodiment of the present invention and the software operated by the processor of the terminal 20 according to an embodiment of the present invention may be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

[0122] Furthermore, the notification of information is not limited to the embodiments / models described herein and may be carried out by other methods. For example, the notification of information may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or combinations thereof. Also, RRC signaling may be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0123] Each aspect / embodiment described in this disclosure includes LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), and IEEE This may apply to at least one system utilizing 802.20, UWB (Ultra-WideBand), Bluetooth®, or other appropriate systems, and to next-generation systems extended, modified, created, or defined based thereon. It may also apply to a combination of multiple systems (for example, a combination of at least one of LTE and LTE-A with 5G).

[0124] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order.

[0125] The information or signals described in this disclosure may be output from a higher layer (or lower layer) to a lower layer (or higher layer). They may also be input and output via multiple network nodes.

[0126] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

[0127] The determination in this disclosure may be made by a value represented by one bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0128] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0129] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0130] The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0131] In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

[0132] The terms “system” and “network” as used in this disclosure are interchangeable.

[0133] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index.

[0134] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0135] In this disclosure, terms such as "base station (BS)", "wireless base station", "base station equipment", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0136] A base station can house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into several smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0137] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform information-based control or operation.

[0138] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0139] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or several other appropriate terms.

[0140] At least one of the processing unit 10 and the requesting device 20 may be called a transmitting device, receiving device, communication device, etc. At least one of the processing unit 10 and the requesting device 20 may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and its speed of movement is arbitrary. This also includes the case when the mobile body is stationary. The mobile body includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and items mounted on them. Furthermore, the mobile body may be a mobile body that autonomously drives based on operation commands. The mobile object may be a vehicle (e.g., a car, an airplane), an unmanned mobile object (e.g., a drone, an autonomous vehicle), or a robot (manned or unmanned). Note that at least one of the processing unit 10 and the requesting device 20 may be a device that does not necessarily move during communication. For example, at least one of the processing unit 10 and the requesting device 20 may be an IoT (Internet of Things) device such as a sensor.

[0141] As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in a table, database, or other data structure), and ascertaining. “Determining” may also include, for example, receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0142] The terms “connected,” “coupled,” or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0143] The reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applicable standard.

[0144] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0145] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way.

[0146] In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc.

[0147] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0148] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0149] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0150] Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0151] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way. [Explanation of symbols]

[0152] 10 Processing Unit 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 Requester 30 Managed Items 210 Transmitter 220 Receiver 230 Setting section 240 Control Unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device

Claims

1. A receiving unit that receives a request for a resilient intent from a requesting device, Based on the above request, a control unit stores the parameters related to the resilient intent in a parameter table and creates a change plan for the managed object based on the parameters. A processing device equipped with the following features.

2. The control unit stores the parameters received from the requesting device, or the parameters generated by the control unit, in the parameter table. The apparatus according to claim 1.

3. The parameter table stores the intent target values ​​for each predetermined period as parameters. The apparatus according to claim 1.

4. When a change occurs to the managed object based on a normal intent, and the control unit determines that the change affects the parameter, it will update the parameter table with the new parameter after executing the normal intent. The apparatus according to claim 1.

5. When a change occurs to the managed object based on the resilient intent, the control unit updates the parameter table or the parameter table of the normal intent with the new parameters after executing the resilient intent. The apparatus according to claim 1.

6. The steps include receiving a request for a resilient intent from the requesting device, Based on the above request, the parameters related to the resilient intent are stored in a parameter table, and based on the above parameters, a change plan for the managed object is created. A processing method performed by a processing device, comprising the above.

Images