[go: up one dir, main page]

WO2024216987A1 - Procédé, dispositif et produit-programme informatique pour communication sans fil - Google Patents

Procédé, dispositif et produit-programme informatique pour communication sans fil Download PDF

Info

Publication number
WO2024216987A1
WO2024216987A1 PCT/CN2023/135687 CN2023135687W WO2024216987A1 WO 2024216987 A1 WO2024216987 A1 WO 2024216987A1 CN 2023135687 W CN2023135687 W CN 2023135687W WO 2024216987 A1 WO2024216987 A1 WO 2024216987A1
Authority
WO
WIPO (PCT)
Prior art keywords
intent
mns
producer
wireless communication
driven
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2023/135687
Other languages
English (en)
Inventor
Pengxiang Xie
Manchang JU
Jinguo Zhu
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to PCT/CN2023/135687 priority Critical patent/WO2024216987A1/fr
Publication of WO2024216987A1 publication Critical patent/WO2024216987A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5019—Ensuring fulfilment of SLA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0233—Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic

Definitions

  • This document is directed generally to wireless communications, and in particular to 5 th generation (5G) communications or 6 th generation (6G) communications.
  • intent driven management service for mobile networks has become a widely discussed topic and is now considered to be essential for introducing automation and zero-touch autonomous operation.
  • the intent driven approach focuses more on describing the "What" needs to be achieved but less on "How” that outcome should be achieved.
  • MnS intent-driven Management Service
  • This document relates to methods, systems, and computer program products for a wireless communication.
  • the wireless communication method includes: receiving, by an Intent Driven Management of Service, MnS, producer from an Intent Driven MnS consumer, an intent instance; and transmitting, by the Intent Driven MnS producer to the Intent Driven MnS consumer, assistant information according to the received intent instance in response to the assistant information being needed.
  • MnS Intent Driven Management of Service
  • the Intent Driven MnS producer determines whether the assistant information is needed based on a capability of the Intent Driven MnS producer to handle the intent instance.
  • the Intent Driven MnS producer performs at least one of:
  • the Intent Driven MnS producer determines the assistance information being needed in response to a number of feasible solutions for the intent instance being greater than a first threshold or less than a second threshold.
  • the assistant information comprises at least one of:
  • the Intent Driven MnS producer generates the assistant information based on historical intent instances and the received intent instance.
  • the historical intent information comprises at least one of:
  • the Intent Driven MnS producer transmits, to a database, a request comprising at least one filter condition determined based on at least one attribute of the intent instance, and receives, from the database, historical intent information based on the at least one filter condition.
  • the Intent Driven MnS producer transmits, to a database, a request to store the intent instance modified based on the assistant information.
  • the Intent Driven MnS producer transmits, to a database, a request to store the intent instance in response to the assistant information being not needed, and the intent instance comprises at least one of:
  • the Intent Driven MnS producer transmits, to the Intent Driven MnS consumer, an intent report comprising the assistant information.
  • the Intent Driven MnS producer transmits, to a database, a request to store the intent instance in response to the assistant information being not needed, and the intent instance comprises at least one of:
  • the Intent Driven MnS producer transmits, to the Intent Driven MnS consumer, an intent report comprising one or more feasible solutions in response to the assistant information being not needed.
  • the Intent Driven MnS producer transmits, to an analytic function, a request for a first analytic report associated with the intent instance.
  • the Intent Driven MnS producer transmits the request for the first analytic report in response to the Intent Driven MnS producer not able to generate the assistance information.
  • the Intent Driven MnS producer receives, from an analytic function, a first analytic report comprising at least one of:
  • the recommendation comprises at least one of: one or more recommended actions, one or more recommended managed objects, one or more recommended values for one or more targets, or one or more recommended contexts.
  • the Intent Driven MnS producer generates the assistant information based on a first analytic report received from an analytic function and the intent instance.
  • the Intent Driven MnS producer transmits, to an analytic function, a request for a second analytic report associated with the intent instance in response to the assistant information being not needed.
  • the Intent Driven MnS producer transmits the request for the second analytic report in response to the Intent Driven MnS producer being not able to generate solutions based on the received intent instance.
  • the Intent Driven MnS producer generates one or more feasible solutions based on one or more predetermined policies and the second analytic report.
  • the wireless communication method includes: transmitting, by an analytic function to an Intent Driven Management of Service, MnS, producer, a first analytic report to allow the Intent Driven MnS producer to provide assistant information for an intent instance to an Intent Driven MnS consumer.
  • MnS Intent Driven Management of Service
  • the assistant information comprises at least one of:
  • the first analytic report comprises at least one of:
  • the recommendation comprises at least one of: one or more recommended actions, one or more recommended managed objects, one or more recommended values for one or more targets, or one or more recommended contexts.
  • the analytic function receives, from the Intent Driven MnS producer, a request for the first analytic report in response to the Intent Driven MnS producer not able to generate the assistance information.
  • the analytic function receives, from the Intent Driven MnS producer, a request for a second analytic report associated with the intent instance in response to the assistant information being not needed.
  • the analytic function receives the request for the second analytic report in response to the Intent Driven MnS producer being not able to generate solutions based on the intent instance.
  • the analytic function transmit the second analytic report to the Intent Driven MnS producer to allow the Intent Driven MnS producer to generate one or more feasible solutions based on one or more predetermined policies and the second analytic report.
  • the wireless communication node includes a communication unit and a processor.
  • the processor is configured to: receive, via the communication unit from an Intent Driven MnS consumer, an intent instance; and transmit, via the communication unit to the Intent Driven MnS consumer, assistant information according to the received intent instance in response to the assistant information being needed.
  • the wireless communication node includes a communication unit and a processor.
  • the processor is configured to: transmit, via the communication unit to an Intent Driven Management of Service, MnS, producer, a first analytic report to allow the Intent Driven MnS producer to provide assistant information for an intent instance to an Intent Driven MnS consumer.
  • MnS Intent Driven Management of Service
  • the present disclosure relates to a computer program product comprising a computer-readable program medium code stored thereupon, the code, when executed by a processor, causing the processor to implement a wireless communication method recited in any one of foregoing methods.
  • the present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Additionally, the specific order and/or hierarchy of steps in the methods disclosed herein are merely exemplary approaches. Based upon design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be re-arranged while remaining within the scope of the present disclosure. Thus, those of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or acts in a sample order, and the present disclosure is not limited to the specific order or hierarchy presented unless expressly stated otherwise.
  • FIG. 1 shows a schematic diagram of a network according to an embodiment of the present disclosure.
  • FIG. 2 shows a schematic diagram of a procedure according to an embodiment of the present disclosure.
  • FIGs. 3A and 3B show a schematic diagram of a procedure according to an embodiment of the present disclosure.
  • FIGs. 4A and 4B show a schematic diagram of a procedure according to an embodiment of the present disclosure.
  • FIG. 5 shows a schematic diagram of a procedure according to an embodiment of the present disclosure.
  • FIG. 6 shows an example of a schematic diagram of a wireless communication node according to an embodiment of the present disclosure.
  • FIGs. 7 to 8 show flowcharts of wireless communication methods according to some embodiments of the present disclosure.
  • MnS Consumer also referred to as intent driven MnS Consumer in the present disclosure
  • potential solutions also referred to as feasible solutions in the present disclosure
  • the MnS Consumer may not give potential solutions due to incomplete, invalid intent expression, or the number of potential solutions is too large for the processing capacity of the MnS Producer (also referred to as intent driven MnS Producer in the present disclosure) .
  • the intent can be performed with additional contexts or modified targets.
  • assistant information may help the MnS Consumer modify the intent.
  • the MnS Producer can generate numerous solutions with the received intent. But if these solutions are sent to the MnS Consumer, it may create an extra burden on MnS Consumers. Therefore, the MnS Producer may provide assistant information to improve the intent expression for better solutions. Otherwise, the MnS Consumer may constantly try modifying the intent to reduce the number of options.
  • FIG. 1 illustrates a schematic diagram for the intent driven MnS model according to an embodiment of the present disclosure.
  • the MnS Consumer is the intent owner and the MnS Producer is the intent handler.
  • MDA MnS Management Data Analytics (MDA) MnS (also referred to as MDAS) in the context of Service Based Management Architecture (SBMA) enables any authorized consumer to request and receive analytics.
  • the MDA MnS Consumer can request the MDA MnS Producer to provide MDA output for a list of specified MDA type of analytics, (i.e., MDA type, which corresponds to an MDA capability) .
  • MDA type is to support analytics for a set of data or analytics for a certain Performance Measurements (PM) , Key Performance Indicator (KPI) , trace or Quality of Experience (QoE) data.
  • PM Performance Measurements
  • KPI Key Performance Indicator
  • QoE Quality of Experience
  • MDA capability may indicate the analytics capability corresponding to analytics capability of a set of analytics input data to provide analytics output data.
  • MDA Type may indicate the type of analytics corresponding to a specific MDA capability.
  • FIG. 2 illustrates a schematic diagram for creating a new intent according to an embodiment of the present disclosure.
  • the procedure may include at least one of the following operations.
  • the MnS Consumer sends a request to create an intent instance to the MnS Producer with intent information for the new intent to be created.
  • the MnS Producer creates the concrete intent instance and configure the new created intent Managed Object Instance (MOI) with the received intent information.
  • MOI Managed Object Instance
  • the MnS Producer sends a response to the MnS Consumer with attribute "object Instance" of the created intent instance.
  • the MnS Producer Based on the created intent instance, the MnS Producer performs the feasibility check of the intent instance.
  • the MnS Producer can perform the feasibility check and get the results based on latest statistics of network or service performance metrics, historical experience, current operating status including network resource utilization and availability, network performance measurement, prediction results based on network simulation system, and/or predefined checking rules or policies.
  • the MnS Producer Based on the created intent, the MnS Producer identifies the MOI for managed entities and derives one or more executable management tasks for these managed entities, then the MnS Producer deploys or configures corresponding managed entities with deployment and configuration parameters to satisfy the intent instance.
  • the MnS Producer analyses and adjusts the managed entities to ensure the intent is continuously satisfied.
  • the MnS Producer may notify the MnS Consumer about attribute "object Instance" of intent report instance and corresponding intent report information.
  • the MnS Producer notifies the MnS Consumer with infeasible information for the created intent instance.
  • the MnS Producer may notify the MnS Consumer with recommendations to modify the intent.
  • procedures of getting recommendations in some embodiments of the present disclosure will be introduced.
  • the MnS Producer when receiving an intent for solutions, can perform procedures to analyze the intent and evaluate whether assistant information is needed. Such an operation may help the MnS Consumer to improve the intent expression and obtain best solutions.
  • the MnS Producer Based on existing data related to historical intent instances (also referred to as existing intent instances or historical intent instances in the present disclosure) , the MnS Producer can provide assistant information itself or invoke external analytic functions like Management Data Analytics Function (MDAF) to generate assistant information.
  • MDAF Management Data Analytics Function
  • the MnS Producer performs an analysis to generate assistant information to improve intent expression.
  • the MnS Producer may include an Intent Handler, an Analysis Function, and a Database Function, but is not limited in this regard.
  • FIGs. 3A and 3B illustrate a schematic diagram of a procedure according to an embodiment of the present disclosure.
  • the procedure may include at least one of the following operations.
  • the precondition may be the Intent Handler receives an intent (also referred to as intent instance) for solutions.
  • intent instance also referred to as intent instance
  • the MnS Consumer expresses an energy saving intent to reduce energy consumption 40%in area A.
  • the MnS Consumer asks the Intent Handler for solutions to achieve the goal.
  • the Intent Handler requests (e.g., transmits a request to the Analysis Function) the Analysis Function to analyze the intent instance.
  • the Analysis Function evaluates whether assistance information is needed.
  • the Intent Driven MnS Producer determines whether the assistant information is needed based on a capability of the MnS Producer to handle the intent instance (e.g., the number of potential solutions the MnS Producer can provide) .
  • the MnS Producer may perform an evaluation (e.g., a feasibility check procedure) to filter feasible solutions based on policies (e.g., risk control strategies and risk control indicators) .
  • the MnS Producer may perform risk assessments to filter feasible solutions based on risk control strategies and indicators.
  • the MnS Producer may predict the number of potential solutions. In some embodiments, the MnS Producer may predict the number of potential solutions based on at least one of: potential risk and conflict, historical information, network performance measurement, and/or current network resource. Then, the MnS Producer may generate an analysis result. In some embodiments, the MnS Producer may determine whether assistance information is needed based on the number of potential solutions, such as ‘assistance information needed’ or ‘no assistance information’ . In some embodiments, the Intent Driven MnS Producer determines the assistant information being needed in response to a number of feasible solutions for the intent instance being greater than a first threshold (e.g., too many solutions) or less than a second threshold (e.g., no solution or too less solutions) .
  • a first threshold e.g., too many solutions
  • a second threshold e.g., no solution or too less solutions
  • Example 1 the evaluation result shows that there are no feasible solutions can be provided for the received intent. Therefore, assistance information is needed to improve the intent expression, operations 3 to 10 are executed.
  • the Analysis Function requests the Database Function for information of existing intent instances (or historical intent instances) as inputs for analysis.
  • attributes of existing intent instances (or historical intent instances) may be transformed (e.g., by the Analysis Function) as filter condition (s) .
  • the filter condition (s) may include at least one of: an intent type (e.g., IntentType) (e.g., Intent-Communication Service Consumer (CSC) , Intent-Communication Service Provider (CSP) , and/or Intent-Network Operator (NOP) ) , an analytic type (e.g., an MDA type (e.g., MDAType) ; to facilitate understanding the MDA type will be taken as an example hereinafter) (e.g., energy saving, coverage, Service Level Specification (SLS) , and/or fault management) , managed entities (e.g., ManagedEntities) (e.g., a Slice, Slice Subnet, gNodeB (gNB) , Cell, and/or Network Function NF) , one or more contexts (e.g., area context and/or time context) , and/or one or more targets (e.g., an SLS level, throughput, max number of User equipment
  • the filter condition (s) may include an intent type (e.g., Intent-NOP) , an analytic type (e.g., energy saving) , managed entities (e.g., gNBs and User Plane Functions (UPFs) ) , a context (e.g., Area A) , and a target (reduction ratio of energy consumption) .
  • intent type e.g., Intent-NOP
  • an analytic type e.g., energy saving
  • managed entities e.g., gNBs and User Plane Functions (UPFs)
  • UPFs User Plane Functions
  • a context e.g., Area A
  • target reduction ratio of energy consumption
  • the Database Function sends the information of the existing intent instances (or historical intent instances) to the Analysis Function.
  • the information of the existing intent instances (or historical intent instances) may be taken as inputs by the Analysis Function for analysis.
  • the Database Function may recognize received filter condition (s) .
  • the Database Function may send the information of the existing intent instances (or historical intent instances) to the Analysis Function as inputs for analysis based on the received filter condition (s) .
  • the Database Function may send the information of the existing intent instances (or historical intent instances) related with energy saving in area A with corresponding configuration data.
  • the Analysis Function may perform an analysis operation to generate the assistance information.
  • the assistance information may include at least one of: an identifier (e.g., an assistance information ID (e.g., assistanceInformationID) , one or more recommended actions (e.g., RecommendedActions) (e.g., add, delete, and/or modify at least one of an expectation object (e.g., ExpectationObject) , an expectation target (e.g., ExpectationTarget) , an intent context (e.g., IntentContext) , an expectation context (e.g., ExpectationContext) , an object context (e.g., ObjectContext) and/or a target context (e.g., TargetContext) ) , and/or one or more reasons for the one or more recommended actions (e.g., ReasonsForRecommendedActions) .
  • the one or more reasons for the one or more recommended actions may contain at least one of: Invalid Intent Expression, Potential Intent Conflict, Potential Intent Degradation, Intent Conflict, and/or
  • the invalid intent expression may comprise at least one of: the received intent is expressed and/or translated in an invalid format and/or the received intent cannot be recognized.
  • the potential intent conflict may indicate that there is a potential intent conflict, and/or the intent cannot be executed unless it is prioritized.
  • the potential intent degradation may indicate that there is a potential intent conflict, and/or the intent can be executed after degradation.
  • the intent conflict may indicate that there is an intent conflict, and/or the intent cannot be executed unless it is prioritized.
  • the intent degradation may indicate that there is an intent conflict, and/or the intent can be executed after degradation.
  • the assistance information to improve the intent may include: an identifier, a recommended action including adding the expectation context (e.g., add time context as 11: 00 PM to 5: 00 AM) , and the reason for the recommended actions (e.g., ‘Potential Intent Conflict’ ) .
  • the Analysis Function requests Database Function (e.g., transmits a request to the Database Function) to store information of the intent instance modified based on the assistant information.
  • the Database Function performs a storage operation.
  • the modified intent instance is labeled with a specific analytic type and an intent instance ID.
  • the information of the modified intent instance is stored in a format that can be requested by external analytic function like MDAF.
  • the stored information of the intent instance modified based on the assistant information may include at least one of following attributes: an intent type (e.g., IntentType) (e.g., Intent-CSC, Intent-CSP, and/or Intent-NOP) , an analytic type (e.g., an MDA type (e.g., MDAType) ; to facilitate understanding the MDA type will be taken as an example hereinafter) (e.g., energy saving, coverage, SLS, and/or fault management) , an identifier (e.g., IntentInstanceID) , managed entities (e.g., ManagedEntities) (e.g., a Slice, Slice Subnet, gNB, Cell, and/or NF) , one or more contexts (e.g., area context and/or time context) , and/or one or more targets (e.g., an SLS level, throughput, max number of UEs, energy saving level for each gNB, and/
  • the storage format and attributes are determined based on the analytic type.
  • the intent type is Intent-NOP
  • the analytic type is energy saving
  • the identifier is ES01
  • the managed entities are gNBs and UPFs entering the energy saving state
  • the contexts are area A and time window 11: 00 PM to 5: 00 AM
  • the target is 40%reduction of energy consumption.
  • the Database Function transmits a response to the Analysis Function.
  • the Database Function responds to the Analysis Function for storing information of the modified intent instance.
  • the Analysis Function reports the analysis results to the Intent Handler.
  • the Intent Handler outputs an intent report (e.g., to an MnS Consumer or another device) .
  • the intent report may include the assistant information.
  • the Analysis function requests the Database Function to store information of the intent instance (e.g., by transmits a request to the database) .
  • the Database Function performs a storage operation.
  • the received intent instance is labeled with a specific analytic type and an intent instance ID.
  • the information of the received intent instance is stored in a format that can be requested by external analytic function like MDAF.
  • the stored information of the received intent instance may include at least one of following attributes: an intent type (e.g., IntentType) (e.g., Intent-CSC, Intent-CSP, and/or Intent-NOP) , an analytic type (e.g., an MDA type (e.g., MDAType) ) (e.g., energy saving, coverage, SLS, and/or fault management) , an identifier (e.g., IntentInstanceID ) , managed entities (e.g., ManagedEntities) (e.g., a Slice, Slice Subnet, gNB, Cell, and/or NF) , one or more contexts (e.g., area context and/or time context) , and/or one or more targets (e.g., an SLS level, throughput, max number of UEs, energy saving level for each gNB, and/or reduction ratio of energy consumption) .
  • an intent type e.g., IntentType
  • the storage format and attributes are determined based on the analytic type.
  • the intent type is Intent-NOP
  • the analytic type is energy saving
  • the identifier is ES01
  • the managed entities are gNBs and UPFs entering the energy saving state
  • the context is area A
  • the target is 40%reduction of energy consumption.
  • the Database Function responds to the Analysis Function for storing information of the intent instance (e.g., transmitting a response to the Analysis Function) .
  • the Analysis Function reports analysis results to the Intent Handler.
  • the Intent Handler outputs the intent report (e.g., to an MnS Consumer or another device) .
  • the intent report may include one or more feasible solutions.
  • the MnS Producer involves an external analytic function (e.g., MDAF) (to facilitate understanding an MDAF will be taken as an example in the present disclosure) to generate assistant information.
  • MDAF an external analytic function
  • the MnS Producer may include an intent Handler, an Analysis Function, a Database Function.
  • FIGs. 4A and 4B illustrate a schematic diagram of a procedure according to an embodiment of the present disclosure.
  • the procedure may include at least one of the following operations.
  • the precondition may be the Intent Handler receives an intent for solutions.
  • the MnS Consumer expresses an energy saving intent to reduce energy consumption 20%in area A.
  • the MnS Consumer asks the Intent Handler for solutions to achieve the goal.
  • the Intent Handler requests (e.g., transmits a request to the Analysis Function) the Analysis Function to analyze the intent instance.
  • the Analysis Function evaluates whether it has the capability to handle the received intent and whether assistance information is needed.
  • the Intent Driven MnS Producer determines whether the assistant information is needed based on a capability of the MnS Producer to handle the intent instance (e.g., the number of potential solutions the MnS Producer can provide) .
  • the MnS Producer may perform an evaluation (e.g., a feasibility check procedure) to filter feasible solutions based on policies (e.g., risk control strategies and risk control indicators) .
  • the intent driven MnS Producer may perform risk assessments to filter feasible solutions based on risk control strategies and indicators.
  • the MnS Producer may predict the number of potential solutions. In some embodiments, the MnS Producer may predict the number of potential solutions based on at least one of: potential risk and conflict, historical information, network performance measurement, and/or current network resource. Then, the MnS Producer may generate an analysis result. In some embodiments, the MnS Producer may determine whether assistance information is needed based on the number of potential solutions, such as ‘assistance information needed’ or ‘no assistance information’ . In some embodiments, the Intent Driven MnS Producer determines the assistant information being needed in response to a number of feasible solutions for the intent instance being greater than a first threshold (e.g., too many solutions) or less than a second threshold (e.g., no solution or too less solutions) .
  • a first threshold e.g., too many solutions
  • a second threshold e.g., no solution or too less solutions
  • the target reduces energy consumption 20%in area A may be achieved, but there are too many solution combinations of energy saving actions involving different gNBs and UPFs to be set into energy saving states at various time.
  • the evaluation result shows that the Intent Handler cannot deal with so many solutions, which beyond the capability of the Intent Handler.
  • the Intent Handler decides to provide some assistance information to the intent owner (e.g., MnS Consumer) to help the intent owner improve the intent (e.g., the intent expression) with more restrictions.
  • the evaluation result is 'Assistant Information needed' , following operations 3 to 13 are executed.
  • the Analysis Function transmits a request (e.g., an MDA request) to the MDAF for an analytic report (e.g., an MDA report) (to facilitate understanding, an MDA request for requesting an MDA report will be taken as an example hereinafter) .
  • an analytic report e.g., an MDA report
  • the MnS Producer may invoke the external analytics function.
  • the MDAF is an option or an example to perform the analytic.
  • attributes of the intent instance may be included in the MDA request for the MDA report.
  • the MDAF Based on information (e.g., attributes of the intent instance) received in the MDA request for the MDA report, the MDAF generates filter condition (s) .
  • the MDAF requests the MnS Producer (e.g., the Database Function of the MnS Producer) (e.g., transmit a request to the MnS Producer) for information of existing intent instances (or historical intent instances) based on filter condition (s) .
  • the information of the existing intent instances (or historical intent instances) may be taken as inputs for analysis.
  • attributes of existing intent instances (or historical intent instances) may be transformed as filter condition (s) (e.g., by the MDAF or the MnS Producer) .
  • the filter condition (s) may include at least one of: an intent type (e.g., IntentType) (e.g., Intent-CSC, Intent-CSP, and/or Intent-NOP) , an identifier (e.g., an MDA Report ID (e.g., MDAReportID) ) , an analytic type (e.g., an MDA type (e.g., MDAType) (e.g., energy saving, coverage, SLS, and/or fault management) ) , managed entities (e.g., ManagedEntities) (e.g., a Slice, Slice Subnet, gNB, Cell, and/or NF) , one or more contexts (e.g., area context and/or time context) , and/or one or more targets (e.g., an SLS level, throughput, max number of UEs, energy saving level for each gNB, and/or reduction ratio of energy consumption) .
  • an intent type e.g
  • the intent type is Intent-NOP
  • MDA Request ID is MDARequest02
  • the analytic type e.g. MDA Type
  • the managed entities are gNBs and UPFs entering the energy saving state
  • the context is Area A
  • the target is 20%reduction of energy consumption.
  • the Database Function sends filtered data to MDAF.
  • the Database Function may recognize received filter condition (s) .
  • the Database Function may send the information of the existing intent instances (or historical intent instances) to MDAF as inputs for analysis based on received filter condition (s) .
  • the Database Function may send information of existing intent instances (or historical intent instances) related with energy saving in area A with corresponding configuration data.
  • the MDAF performs an MDA. In some embodiments, based on the received data and/or the received intent instance, the MDAF performs the MDA and generates an MDA report.
  • the MDA report may include at least one of: an identifier (e.g., an MDA Report ID (e.g., MDAReportID) ) , a reference of the MDA Request (e.g., RefMDARequest) , an analytic type (e.g., an MDA type (e.g., MDAType) (e.g., energy saving, coverage and SLS) ) and/or one or more recommendations (e.g., Recommendations) (e.g., recommended actions, recommended managed objects, recommended values for specific targets, recommended context) .
  • the recommendations are determined based on the MDA Type.
  • the MDA report may contain at least one of the following attributes: an identifier (e.g., an MDA Report ID (MDAReport02) ) , a reference of the MDA request (e.g., Ref MDA Request (MDARequest02) ) , an analytic type (e.g. MDA Type (energy saving) ) and recommendations (e.g., Recommended gNBs, Recommended UPFs, Recommended Energy saving Level, Time window) .
  • an identifier e.g., an MDA Report ID (MDAReport02)
  • a reference of the MDA request e.g., Ref MDA Request (MDARequest02)
  • an analytic type e.g. MDA Type (energy saving)
  • recommendations e.g., Recommended gNBs, Recommended UPFs, Recommended Energy saving Level, Time window
  • the MDAF sends an MDA report to the Analysis Function.
  • the Analysis Function Based on the received MDA report, the Analysis Function performs an analysis to generate the assistant information.
  • the assistance information may include at least one of: an identifier (e.g., an assistance information ID (e.g., assistanceInformationID) , one or more recommended actions (e.g., RecommendedActions) (e.g., add, delete, and/or modify at least one of an expectation object (e.g., ExpectationObject) , an expectation target (e.g., ExpectationTarget) , an intent context (e.g., IntentContext) , an expectation context (e.g., ExpectationContext) , an object context (e.g., ObjectContext) and/or a target context (e.g., TargetContext) ) , and/or one or more reasons for the one or more recommended actions (e.g., ReasonsForRecommendedActions) .
  • the one or more reasons for the one or more recommended actions may contain at least one of: Invalid Intent Expression, Potential Intent Conflict, Potential Intent Degradation, Intent Conflict, and/or
  • the assistance information to improve the intent may be as follows: add additional contexts (e.g., add expectation context (e.g., add time context as 11: 00 PM to 5: 00 AM) , add object context (specific gNBs or UPFs) ) and modify Expectation Target (e.g., 30%reduction of energy consumption) .
  • additional contexts e.g., add expectation context (e.g., add time context as 11: 00 PM to 5: 00 AM)
  • object context e.g., add object context (specific gNBs or UPFs)
  • modify Expectation Target e.g., 30%reduction of energy consumption
  • the Analysis Function requests the Database (e.g., transmits a request to the Database Function) to store the information of the intent instance modified based on the assistant information.
  • the Database Function performs a storage operation.
  • the modified intent instance is labeled with a specific analytic Type and an Intent Instance ID.
  • the information of the modified intent instance is stored in a format that can be requested by external analytic function like MDAF.
  • the stored information may include at least one of following attributes, an intent type (e.g., IntentType) (e.g., Intent-CSC, Intent-CSP, and/or Intent-NOP) , an analytic type (e.g., an MDA type (e.g., MDAType) (e.g., energy saving, coverage, SLS, and/or fault management) ) , an identifier (e.g., IntentInstanceID) , managed entities (e.g., ManagedEntities) (e.g., a Slice, Slice Subnet, gNB, Cell, and/or NFs) , one or more contexts (e.g., area context and/or time context) , and/or one or more targets (e.g., an SLS level, throughput, max number of UEs and/or energy saving level for each gNB) .
  • an intent type e.g., IntentType
  • MDAType e.g., MDAType
  • the storage format and attributes are determined based on the analytic type.
  • the intent type is Intent-NOP
  • the analytic type is energy saving
  • the identifier is ES02
  • the managed entities are gNBs or UPFs entering the energy saving state
  • the contexts are area A and time window 11: 00 PM to 5: 00 AM
  • the target is reducing energy consumption 30%.
  • the Database Function transmits a response to the Analysis Function.
  • the Database Function responds to the Analysis Function for storing information of the intent instance.
  • the Analysis Function reports the analysis results to the Intent Handler.
  • the Intent Handler outputs the intent report (e.g., to an MnS Consumer or another device) .
  • the intent report may include assistant information.
  • the Analysis Function transmits a request (e.g., an MDA request) to the MDAF for an analytic report (e.g., an MDA report) (to facilitate understanding, an MDA request for requesting an MDA report will be taken as an example hereinafter) .
  • an analytic report e.g., an MDA report
  • MDAF is an option or an example to perform the analytic.
  • attributes of the existing intent instances may be included in the MDA request.
  • the MDAF may recognize the suitable analytic type and perform the MDA.
  • the MDAF generates an MDA report.
  • the MDA report may include at least one of an identifier (e.g., an MDA Report ID (e.g., MDAReportID) ) , a reference of an MDA Request (e.g., RefMDARequest) , an analytic type (e.g., an MDA type (e.g., MDAType) (e.g., energy saving, coverage and SLS) ) and/or one or more recommendations (e.g., Recommendations) (e.g., recommended actions, recommended managed objects, recommended values for specific targets, recommended context) .
  • an MDA Report ID e.g., MDAReportID
  • RefMDARequest e.g., RefMDARequest
  • an analytic type e.g., an MDA type (e.g., MDAType) (e.g., energy saving, coverage
  • the recommendations are related with the analytic type.
  • the MDA report may contain at least one of the following attributes: an identifier (e.g., an MDA Report ID (MDAReport02) ) , a reference of the MDA request (e.g., RefMDARequest (MDARequest02) ) , an analytic type (e.g., MDA Type (energy saving) ) and/or recommendations (e.g., Recommended gNBs, Recommended UPFs, Recommended Energy saving Level, Time window) .
  • an identifier e.g., an MDA Report ID (MDAReport02)
  • a reference of the MDA request e.g., RefMDARequest (MDARequest02)
  • an analytic type e.g., MDA Type (energy saving)
  • recommendations e.g., Recommended gNBs, Recommended UPFs, Recommended Energy saving Level, Time window
  • the MDAF sends an MDA report to the Analysis Function.
  • the MDAF may send a report to the MnS Producer.
  • the Analysis Function performs the analysis (e.g., to generates feasible solution) .
  • the Analysis Function may performs the analysis based on the received MDA report and pre-configured policies.
  • the Analysis Function may generates feasible solutions based on the received MDA report and pre-configured policies.
  • the Analysis Function requests the Database Function to store information of the intent instance (e.g., by transmits a request to the database) .
  • the Database Function performs a storage operation.
  • the modified intent instance is labeled with a specific MDA Type and Intent Instance ID.
  • the information of the received intent instance is stored in a format that can be requested by external analytic function like MDAF.
  • the stored information of the received the intent instance may include at least of the following attributes: an intent type (e.g., IntentType) (e.g., Intent-CSC, Intent-CSP, and/or Intent-NOP) , an analytic type (e.g., an MDA type (e.g., MDAType) (e.g., energy saving, coverage, SLS, and/or fault management) ) , an identifier (e.g., IntentInstanceID) , managed entities (e.g., ManagedEntities) (e.g., a Slice, Slice Subnet, gNBs, Cells, and/or NFs) , one or more contexts (e.g., area context and/or time context) , and/or one or more targets (e.g., an SLS level, throughput, max number of UEs and/or energy saving level for each gNB) .
  • an intent type e.g., IntentType
  • MDAType e
  • the storage format and attributes are determined based on the analytic type.
  • the intent type is Intent-NOP
  • the analytic type is energy saving
  • the identifier is ES02
  • the managed entities are gNBs or UPFs entering the energy saving state
  • the context is area A
  • the target is reducing energy consumption 20%.
  • the Database Function responds to the Analysis Function for storing information of the intent instance (e.g., transmitting a response to the Analysis Function) .
  • the Intent Handler outputs the intent report (e.g., to an MnS Consumer or another device) .
  • the intent report may include feasible solutions.
  • FIG. 5 relates a schematic diagram of a procedure according to an embodiment of the present disclosure.
  • the procedure may include at least one of the following operations.
  • the Intent Driven MnS Producer analyzes the received intent.
  • the Intent driven MnS Producer may perform risk assessments to filter feasible solutions based on risk control strategies and indicators.
  • the Intent Driven MnS Producer predicts the number of potential solutions. Based on current network resource, network performance measurement, and/or historical experience, the Intent driven MnS Producer may predict the number of potential solutions for the received intent.
  • the Intent Driven MnS Producer provides assistant information to help the MnS Consumer improve the intent expression when the number of solutions for the intent too many to be handled, i.e., it is out of the capability of the MnS Producer.
  • the Intent driven MnS Producer may response with assistant information, which may include an identifier (e.g. AssistantInformationID) , recommended actions and reasons for recommended actions.
  • assistant information may include an identifier (e.g. AssistantInformationID) , recommended actions and reasons for recommended actions.
  • external analytic function like MDAF may be invoked by the Intent Driven MnS Producer for analytic service.
  • the analytic service may include generate solutions or assistant information.
  • FIG. 6 relates to a diagram of a wireless communication node 40 according to an embodiment of the present disclosure.
  • the wireless communication node 40 may be a satellite, a base station (BS) , a gNB, a network entity, a Domain Name System (DNS) server, a Mobility Management Entity (MME) , Serving Gateway (S-GW) , Packet Data Network (PDN) Gateway (P-GW) , a radio access network (RAN) , a next generation RAN (NG-RAN) , a data network, a core network, a communication node in the core network, or a Radio Network Controller (RNC) , and is not limited herein.
  • BS base station
  • gNB a network entity
  • DNS Domain Name System
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • PDN Packet Data Network Gateway
  • RAN radio access network
  • NG-RAN next generation RAN
  • RNC Radio Network Controller
  • the wireless communication node 40 may include (perform) at least one network function such as an access and mobility management function (AMF) , a session management function (SMF) , a user place function (UPF) , a policy control function (PCF) , an application function (AF) , etc.
  • the wireless communication node 40 may be used to implement the MnS Producer, the functions (e.g. the analytic function or the handler function) in the MnS Producer, or the analytic function (e.g., the MDAF) described in this disclosure.
  • the wireless communication node 40 may include a processor 400 such as a microprocessor or ASIC, a storage unit 410 and a communication unit 420.
  • the storage unit 410 may be any data storage device that stores a program code 412, which is accessed and executed by the processor 400. Examples of the storage unit 412 include but are not limited to a SIM, ROM, flash memory, RAM, hard-disk, and optical data storage device.
  • the communication unit 420 may be a transceiver and is used to transmit and receive signals (e.g., messages or packets) according to processing results of the processor 400. In an embodiment, the communication unit 420 transmits and receives the signals via at least one antenna 422 or via wiring.
  • the storage unit 410 and the program code 412 may be omitted.
  • the processor 400 may include a storage unit with stored program code.
  • the processor 400 may implement any steps described in exemplified embodiments on the wireless communication node 40, e.g., via executing the program code 412.
  • the communication unit 420 may be a transceiver.
  • the communication unit 420 may as an alternative or in addition be combining a transmitting unit and a receiving unit configured to transmit and to receive, respectively, signals, messages, or information to and from a wireless communication node or a wireless communication terminal.
  • the wireless communication node 40 may be used to perform the operations of the MnS Producer, the functions in the MnS Producer, or the analytic function (e.g., the MDAF) described in this disclosure.
  • the processor 400 and the communication unit 420 collaboratively perform the operations described in this disclosure. For example, the processor 400 performs operations and transmit or receive signals through the communication unit 420.
  • a wireless communication method is also provided according to an embodiment of the present disclosure.
  • the wireless communication method may be performed by using a wireless communication node (e.g., the MnS Producer or the functions in the MnS Producer) .
  • the wireless communication node may be implemented by using the wireless communication node 40 described in this disclosure, but is not limited thereto.
  • the wireless communication method includes receiving, by an Intent Driven Management of Service, MnS, producer from an Intent Driven MnS consumer, an intent instance; and transmitting, by the Intent Driven MnS producer to the Intent Driven MnS consumer, assistant information according to the received intent instance in response to the assistant information being needed.
  • MnS Intent Driven Management of Service
  • the wireless communication method may be performed by using a wireless communication node (e.g., the MnS Producer, the functions in the MnS Producer, or the analytic function (e.g., the MDAF) ) .
  • the wireless communication node may be implemented by using the wireless communication node 40 described in this disclosure, but is not limited thereto.
  • the wireless communication method includes transmitting, by an analytic function to an Intent Driven Management of Service, MnS, producer, a first analytic report to allow the Intent Driven MnS producer to provide assistant information for an intent instance to an Intent Driven MnS consumer.
  • MnS Intent Driven Management of Service
  • the wireless communication node used in the present disclosure may indicate the MnS Producer, the functions in the MnS Producer, or the analytic function (e.g., the MDAF) described above.
  • a and/or B and/or C includes any and all combinations of one or more of A, B, and C, including A, B, C, A and B, A and C, B and C, and a combination of A and B and C.
  • A/B/C includes any and all combinations of one or more of A, B, and C, including A, B, C, A and B, A and C, B and C, and a combination of A and B and C.
  • any reference to an element herein using a designation such as “first, “ “second, “ and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.
  • any one of the various illustrative logical blocks, units, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two) , firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as "software” or a “software unit” ) , or any combination of these techniques.
  • a processor, device, component, circuit, structure, machine, unit, etc. can be configured to perform one or more of the functions described herein.
  • IC integrated circuit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the logical blocks, units, and circuits can further include antennas and/or transceivers to communicate with various components within the network or within the device.
  • a general-purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine.
  • a processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein. If implemented in software, the functions can be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium.
  • Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one place to another.
  • a storage media can be any available media that can be accessed by a computer.
  • such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • unit refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various units are described as discrete units; however, as would be apparent to one of ordinary skill in the art, two or more units may be combined to form a single unit that performs the associated functions according to embodiments of the present disclosure.
  • memory or other storage may be employed in embodiments of the present disclosure.
  • memory or other storage may be employed in embodiments of the present disclosure.
  • any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present disclosure.
  • functionality illustrated to be performed by separate processing logic elements, or controllers may be performed by the same processing logic element, or controller.
  • references to specific functional units are only references to a suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

Landscapes

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

Abstract

Un procédé de communication sans fil est divulgué. Le procédé consiste à recevoir, par un producteur de gestion de service, MnS, basé sur l'intention, depuis un consommateur de MnS basé sur l'intention, une instance d'intention ; et à transmettre, par le producteur de MnS basé sur l'intention au consommateur de MnS basé sur l'intention, des informations d'assistant en fonction de l'instance d'intention reçue en réponse aux informations d'assistant nécessaires.
PCT/CN2023/135687 2023-11-30 2023-11-30 Procédé, dispositif et produit-programme informatique pour communication sans fil Pending WO2024216987A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/135687 WO2024216987A1 (fr) 2023-11-30 2023-11-30 Procédé, dispositif et produit-programme informatique pour communication sans fil

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/135687 WO2024216987A1 (fr) 2023-11-30 2023-11-30 Procédé, dispositif et produit-programme informatique pour communication sans fil

Publications (1)

Publication Number Publication Date
WO2024216987A1 true WO2024216987A1 (fr) 2024-10-24

Family

ID=93151940

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/135687 Pending WO2024216987A1 (fr) 2023-11-30 2023-11-30 Procédé, dispositif et produit-programme informatique pour communication sans fil

Country Status (1)

Country Link
WO (1) WO2024216987A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111565114A (zh) * 2019-02-14 2020-08-21 华为技术有限公司 一种意图处理方法、装置及系统
WO2023011735A1 (fr) * 2021-08-06 2023-02-09 Telefonaktiebolaget Lm Ericsson (Publ) Communication entre une hiérarchie de systèmes de gestion
CN115706740A (zh) * 2021-08-13 2023-02-17 中国移动通信有限公司研究院 一种请求处理方法、装置、设备及可读存储介质
WO2023040899A1 (fr) * 2021-09-17 2023-03-23 华为技术有限公司 Procédé de communication et appareil associé
CN116266267A (zh) * 2021-12-17 2023-06-20 华为技术有限公司 一种意图合法性检查方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111565114A (zh) * 2019-02-14 2020-08-21 华为技术有限公司 一种意图处理方法、装置及系统
WO2023011735A1 (fr) * 2021-08-06 2023-02-09 Telefonaktiebolaget Lm Ericsson (Publ) Communication entre une hiérarchie de systèmes de gestion
CN115706740A (zh) * 2021-08-13 2023-02-17 中国移动通信有限公司研究院 一种请求处理方法、装置、设备及可读存储介质
WO2023040899A1 (fr) * 2021-09-17 2023-03-23 华为技术有限公司 Procédé de communication et appareil associé
CN116266267A (zh) * 2021-12-17 2023-06-20 华为技术有限公司 一种意图合法性检查方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ZTE CORPORATION: "Add intent fulfilment feasibility information into intent report", 3GPP DRAFT; S5-233388, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP SA 5, no. Electronic meeting, Online; 20230417 - 20230425, 7 April 2023 (2023-04-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052478682 *

Similar Documents

Publication Publication Date Title
US11451452B2 (en) Model update method and apparatus, and system
US11816504B2 (en) Serverless computing architecture
US20220014963A1 (en) Reinforcement learning for multi-access traffic management
EP4489467A1 (fr) Procédé et appareil de communication utilisés pour apprendre un modèle d'apprentissage automatique
US20240137783A1 (en) Signalling support for split ml-assistance between next generation random access networks and user equipment
CN109660994B (zh) 用于在能够收回频谱的租用频谱系统中操作的设备
WO2023006228A1 (fr) Commande de reddition de rapport d'analyse
US11218369B2 (en) Method, apparatus and system for changing a network based on received network information
WO2023015448A1 (fr) Appareil, procédé, et programme informatique
US12273242B2 (en) Soliciting and providing data based on diversity requirements for network apparatus
CN116634021A (zh) 装置、方法和计算机程序
WO2024216987A1 (fr) Procédé, dispositif et produit-programme informatique pour communication sans fil
US20220400521A1 (en) Network entity, user equipment and method
EP4610897A1 (fr) Procédé de communication, et appareil
EP4412288A1 (fr) Formation de modèles spécifiques ou génériques pour sous-ensemble(s) de classes de capabilité d'équipements utilisateurs
WO2025236290A1 (fr) Optimisation de performance avec analyse de corrélation et d'association
WO2025069040A1 (fr) Collecte et exposition d'informations relatives à l'énergie d'un réseau dans un système de communication
WO2024027916A1 (fr) Dispositifs, procédés et supports lisibles par ordinateur pour l'activation de capacités d'intelligence artificielle et/ou d'apprentissage automatique
CN119233279A (zh) 一种自治功能管理方法及装置
CN120342897A (zh) 一种意图管理方法及装置
CN120659029A (zh) 一种通信方法及装置
CN119404534A (zh) 设备、方法和计算机程序
WO2025201722A1 (fr) Procédé, appareil et programme informatique pour prise de décision en boucle de commande fermée et escalade
EP4047993A1 (fr) Procédé et appareil de gestion d'économie d'énergie
CN119183664A (zh) 方法、装置和计算机程序

Legal Events

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

Ref document number: 23933853

Country of ref document: EP

Kind code of ref document: A1