WO2023125204A1 - 一种网络资源管理方法及通信装置 - Google Patents

一种网络资源管理方法及通信装置 Download PDF

Info

Publication number
WO2023125204A1
WO2023125204A1 PCT/CN2022/140754 CN2022140754W WO2023125204A1 WO 2023125204 A1 WO2023125204 A1 WO 2023125204A1 CN 2022140754 W CN2022140754 W CN 2022140754W WO 2023125204 A1 WO2023125204 A1 WO 2023125204A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
target network
state
target
request message
Prior art date
Application number
PCT/CN2022/140754
Other languages
English (en)
French (fr)
Inventor
武绍芸
邢玮俊
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023125204A1 publication Critical patent/WO2023125204A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/02—Resource partitioning among network components, e.g. reuse partitioning
    • H04W16/10—Dynamic resource partitioning
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data

Definitions

  • the present application relates to the technical field of communication, and in particular to a network resource management method and a communication device.
  • the mobile network can provide the user with network services (such as voice and other data transmission services), and the user can also interfere with the mobile network to make the mobile network meet the current user's service requirements.
  • network services such as voice and other data transmission services
  • the mobile network will modify the mobile network corresponding to user A according to the revised billing package, such as modifying the transmission rate or capacity of the mobile network, etc. parameter.
  • the process of user intervention (or modification) on the mobile network can be simply described as: the user interacts with the operator of the mobile network to appeal to the mobile network; after the operator understands the user appeal, the operator through the business support system (business support system, BSS) and operation support system (operation support system, OSS) modify the configuration of the mobile network, so that the modified mobile network can meet user demands.
  • BSS business support system
  • operation support system operation support system
  • Embodiments of the present application provide a network resource management method and a communication device, so as to improve the efficiency of network resource management.
  • the embodiment of the present application provides a network resource management method.
  • the terminal device determines a request message, and the request message is used to operate the life cycle of the target network.
  • the request message is a link between the terminal device and the core network.
  • the terminal device sends the request message to the core network; the core network operates the life cycle of the target network managed by the core network based on the request message.
  • the user can directly operate the target network that provides user services according to the control plane signaling or user plane signaling between the core network and the core network, compared with the user operating the target network through the operator network
  • the operation method can shorten the effective period of the operation, thereby improving the operation efficiency of the target network.
  • the target network is a user service function entity or other network functions that provide services to users.
  • the terminal device can directly operate the user service function entity or other network functions that provide services for users according to the control plane signaling or user plane signaling with the core network.
  • the target network includes a network function that provides network services for terminal devices, one or a group of virtual machines, containers, processes, or other executable resource collections.
  • the request message includes information of an operation type
  • the operation type includes one of creating a target network, deleting a target network, modifying an operating state of the target network, or modifying network attributes of the target network.
  • the terminal device can create, delete, modify the running state and modify the network attributes of the target network according to the control plane signaling or user plane signaling with the core network.
  • modifying the running state of the target network includes suspending the target network or restoring the target network.
  • the terminal device can update the operating status of the target network according to user needs. For example, when the terminal device temporarily does not need the target network to provide network services, the terminal device can choose to suspend the target network to save system power consumption; When the terminal device needs the target network to provide network services, it chooses to restore the target network to meet user needs.
  • modifying the network attribute of the target network includes one or more of modifying capacity of the target network, modifying capability of the target network, modifying a configuration policy of the target network, or modifying a service user list of the target network.
  • the terminal device can modify the network attributes of the target network according to the user's requirements, so that the target network can better meet the user's requirements.
  • the core network performs operation authentication based on the request message; when the result of the operation authentication is passed, the core network operates the life cycle of the target network; or, when the result of the operation authentication is not When passed, the core network does not operate on the life cycle of the target network.
  • the core network authenticates the status of the target network according to the operation type; or, the core network authenticates the operation authority of the operation type.
  • the core network passes the authentication of the state of the target network.
  • the core network fails to authenticate the state of the target network.
  • the matching of the operation type and the state of the target network is used as the screening condition to avoid the situation that after the terminal device sends an error request message, the core network still has to perform invalid operations on the life cycle of the target network according to the error request message , to save power consumption.
  • the state of the target network includes an existing state and an absent state
  • the operation type does not match the state of the target network, including: the operation type is to create a target network, and the state of the target network is an existing state; or, The operation type is to delete the target network, and the state of the target network is non-existent; or, the operation type is to modify the network attributes of the target network, and the state of the target network is non-existent; or, the operation type is to modify the running state of the target network , the state of the target network is non-existent.
  • the state of the target network includes an existing state and a non-existing state
  • the operation type matches the state of the target network, including: the operation type is to create a target network, and the state of the target network is a non-existing state; or, The operation type is to delete the target network, and the state of the target network is existing; or, the operation type is to modify the network attributes of the target network, and the state of the target network is existing; or, the operation type is to modify the running state of the target network, the The status of the target network is present.
  • the existence state includes a suspended state or an activated state
  • the operation type is to modify the running state of the target network, and the operation type does not match the state of the target network, and further includes: the operation type is suspended The target network, the state of the target network is suspended; or, the operation type is recovery target network, the state of the target network is active.
  • the existence state includes a suspended state or an active state
  • the operation type is to modify the running state of the target network, and the operation type matches the state of the target network, and further includes: the operation type is to suspend the target network, the state of the target network is activated; or, the operation type is restore target network, the state of the target network is suspended.
  • the core network includes a first functional network element and a second functional network element, and there is a communication connection between the first functional network element and the second functional network element; the first functional network element is used to Perform operation authentication; the second functional network element is used to operate the life cycle of the target network when the operation authentication result is passed.
  • the first functional network element after the first functional network element performs operation authentication based on the request message, if the result of the operation authentication is passed, the first functional network element sends an indication message to the second functional network element (or second request message), the indication message (or second request message) is used to request the second functional network element to operate on the life cycle of the target network.
  • the second functional network element will only operate the life cycle of the target network after receiving the indication message (or second request message) from the first functional network element, which improves the stability of the target network sex.
  • the indication message (or the second request message) includes an operation type or an operation parameter corresponding to the operation type.
  • the second functional network element can perform specific operations on the life cycle of the target network with the indication message (or the second request message), so as to make the target network more suitable for user needs.
  • the second functional network element authenticates the identity of the first functional network element; after passing the identity authentication of the first functional network element, the second functional network element operates the life cycle of the target network .
  • the second network authenticates the identity of the first functional network element, which can improve the security of the target network.
  • the request message further includes one or more of user information of the terminal device, operation parameters corresponding to the operation type, or target network information.
  • the core network can operate the target network according to user information, operation parameters corresponding to the operation type, or target network information.
  • the user information includes one or more of a permanent user ID, a user group ID, or a temporary user ID.
  • the information of the target network includes one or more of a target network identifier, a capacity value, a capability list, a service user list, or a configuration policy list.
  • the request message also includes user information of the terminal device, and the core network obtains user subscription information based on the user information; the core network determines the operation authority of the operation type based on the user subscription information and/or local configuration policies Authenticate.
  • the user subscription information includes one or more of a list of allowed operation actions, a list of allowed network identifiers, a list of allowed network capacity quotas, a list of allowed service users, or a list of configuration policies.
  • the operation authority of the terminal device is limited by the user subscription information, so that the operation authority of the terminal device is authenticated based on the user subscription information.
  • the core network when the result of the operation authentication is passed, the core network sends a first response message to the terminal device based on the operation result of the lifecycle operation of the target network; the first response message includes the target network The status of or target network ID.
  • the core network when the result of the operation authentication is not passed, the core network sends a second response message to the terminal device, where the second response message is used to indicate the life cycle operation of the target network.
  • the result of the operation is failure.
  • the core network will feed back the operation results of the lifecycle operation of the target network to the terminal equipment, and for users, the core network will be more open and transparent in the operation of the target network, improving user experience.
  • the embodiment of the present application provides a network resource management method.
  • the terminal device determines a request message, and the request message is used to operate the life cycle of the target network; Control plane signaling or user plane signaling between devices; terminal devices send request messages to core network devices.
  • the request message includes information of an operation type
  • the operation type includes one of creating a target network, deleting a target network, modifying an operating state of the target network, or modifying network attributes of the target network.
  • modifying the running state of the target network includes suspending the target network or restoring the target network.
  • modifying the network attribute of the target network includes one or more of modifying capacity of the target network, modifying capability of the target network, modifying a configuration policy of the target network, or modifying a service user list of the target network.
  • the request message further includes one or more of user information of the terminal device, operation parameters corresponding to the operation type, or target network information.
  • the user information includes one or more of a permanent user ID, a user group ID, or a temporary user ID.
  • the information of the target network includes one or more of a target network identifier, a capacity value, a capability list, a service user list, or a configuration policy list.
  • the terminal device receives the response message sent by the core network device, where the response message is used to indicate the result of the lifecycle operation on the target network.
  • the target network is a user service function entity or other network functions that provide services to users.
  • the target network includes a network function that provides network services for terminal devices, one or a group of virtual machines, containers, processes, or other executable resource collections.
  • the embodiment of the present application provides a network resource management method.
  • the core network device receives a request message from the terminal device, and the request message is used to operate the life cycle of the target network; the request message is Control plane signaling or user plane signaling between the terminal device and the core network device; the core network device operates the life cycle of the target network managed by the core network device based on the request message.
  • the request message includes information of an operation type
  • the operation type includes one of creating a target network, deleting a target network, modifying an operating state of the target network, or modifying network attributes of the target network.
  • modifying the running state of the target network includes suspending the target network or restoring the target network.
  • modifying the network attribute of the target network includes one or more of modifying capacity of the target network, modifying capability of the target network, modifying a configuration policy of the target network, or modifying a service user list of the target network.
  • the core network device performs operation authentication based on the request message; when the result of the operation authentication is passed, the core network device operates the life cycle of the target network; when the result of the operation authentication is not passed When , the core network equipment does not operate on the life cycle of the target network.
  • the core network device performs operation authentication based on the request message, including one or more of the following: according to the operation type, authenticating the state of the target network; or authenticating the operation authority of the operation type right.
  • the core network device if the operation type matches the state of the target network, the core network device passes the state authentication of the target network; if the operation type does not match the state of the target network, the core network device passes the state authentication of the target network Status authentication failed.
  • the state of the target network includes an existing state or a non-existing state
  • the operation type matches the state of the target network, including: the operation type is to create a target network, and the state of the target network is a non-existing state; or, the operation The type is to delete the target network, and the state of the target network is Existing; or, the operation type is to modify the network attributes of the target network, and the state of the target network is Existing; or, the operation type is to modify the running state of the target network, and the state of the target network is to exist.
  • the existence state includes a suspended state or an active state
  • the operation type is to modify the running state of the target network, and the operation type matches the state of the target network, and further includes: the operation type is to suspend the target network, the state of the target network is active; or, the operation type is restore target network, the state of the target network is suspended.
  • the request message further includes one or more of user information of the terminal device, operation parameters corresponding to the operation type, or target network information.
  • the user information includes one or more of a permanent user ID, a user group ID, or a temporary user ID.
  • the information of the target network includes one or more of a target network identifier, a capacity value, a capability list, a service user list, or a configuration policy list.
  • the core network device obtains user subscription information based on user information; and authenticates the operation authority of the operation type based on the user subscription information and/or a local configuration policy.
  • the user subscription information includes one or more of a list of allowed operation actions, a list of allowed network identifiers, a list of allowed network capacity quotas, a list of allowed service users, or a list of configuration policies.
  • the core network device when the result of the operation authentication is passed, based on the operation result of the lifecycle operation of the target network, the core network device sends a first response message to the terminal device; the first response message includes the target The state of the network and the identification of the target network; when the result of the operation authentication is not passed, the core network device sends a second response message to the terminal device, and the second response message is used to indicate the operation result of the life cycle operation on the target network for failure.
  • the target network is a user service function entity or other network functions that provide services to users.
  • the present application provides a communication device, which may be a terminal device, or a chip, a chip system, or a processor that supports the terminal device to implement the above method, or may be a device capable of realizing all or part of the functions of the terminal device. logical modules, units or software. Wherein, the communication device may also be a system on a chip.
  • the communication device includes:
  • the processing unit is used to determine the request message, and the request message is used to operate the life cycle of the target network; the request message is control plane signaling or user plane signaling between the terminal device and the core network device; the transceiver unit uses to send a request message to the core network device.
  • the request message includes information of an operation type, where the operation type includes one of creating a target network, deleting a target network, or modifying a network attribute of the target network.
  • the operation type also includes suspending the target network or restoring the target network.
  • modifying the network attribute of the target network includes one or more of modifying capacity of the target network, modifying capability of the target network, modifying a configuration policy of the target network, or modifying a service user list of the target network.
  • the request message further includes one or more of user information of the terminal device, operation parameters corresponding to the operation type, or target network information.
  • the user information includes one or more of a permanent user ID, a user group ID, or a temporary user ID.
  • the information of the target network includes one or more of a target network identifier, a capacity value, a capability list, a service user list, or a configuration policy list.
  • the transceiving unit is further configured to receive a response message sent by the core network device, where the response message is used to indicate the result of the life cycle operation on the target network.
  • the target network is a user service function entity or other network functions that provide services to users.
  • the present application provides another communication device, which may be a core network device, or a chip, a chip system, or a processor that supports the core network device to implement the above method, or may be capable of implementing all or part of the communication device.
  • the communication device may also be a system on a chip.
  • the communication device includes: a transceiver unit, configured to receive a request message from a terminal device, the request message is used to operate the life cycle of the target network; the request message is a control plane signaling or User plane signaling; a processing unit configured to operate the life cycle of the target network managed by the core network device based on the request message.
  • the request message includes information of an operation type, where the operation type includes one of creating a target network, deleting a target network, or modifying a network attribute of the target network.
  • the operation type also includes suspending the target network or restoring the target network.
  • modifying the network attribute of the target network includes one or more of modifying capacity of the target network, modifying capability of the target network, modifying a configuration policy of the target network, or modifying a service user list of the target network.
  • the processing unit is further configured to perform operation authentication based on the request message; when the result of the operation authentication is passed, the processing unit operates on the life cycle of the target network; when the result of the operation authentication is not When passed, the processing unit does not operate on the life cycle of the target network.
  • the processing unit performs operation authentication based on the request message, including one or more of the following: according to the operation type, authenticating the state of the target network; or authenticating the operation authority of the operation type .
  • the processing unit if the operation type matches the state of the target network, the processing unit passes the state authentication of the target network; if the operation type does not match the state of the target network, the processing unit passes the state authentication of the target network. Right not passed.
  • the state of the target network includes an existing state or a non-existing state
  • the operation type matches the state of the target network, including: the operation type is to create a target network, and the state of the target network is a non-existing state; or, the operation The type is to delete the target network, and the state of the target network is the existing state; or, the operation type is to modify the network attributes of the target network, and the state of the target network is the existing state.
  • the operation type does not match the state of the target network, and further includes: the operation type is suspending the target network, and the state of the target network is non-existent or suspended; or, the operation type is restoring the target network, The status of the target network is non-existent or active.
  • the request message further includes one or more of user information of the terminal device, operation parameters corresponding to the operation type, or target network information.
  • the user information includes one or more of a permanent user ID, a user group ID, or a temporary user ID.
  • the information of the target network includes one or more of a target network identifier, a capacity value, a capability list, a service user list, or a configuration policy list.
  • the processing unit acquires user subscription information based on the user information; and authenticates the operation authority of the operation type based on the user subscription information and/or a local configuration policy.
  • the user subscription information includes one or more of a list of allowed operation actions, a list of allowed network identifiers, a list of allowed network capacity quotas, a list of allowed service users, or a list of configuration policies.
  • the transceiver unit when the result of the operation authentication is passed, based on the operation result of the life cycle operation of the target network, the transceiver unit sends a first response message to the terminal device; the first response message includes the target network state and target network identification; when the result of the operation authentication is not passed, the transceiver unit sends a second response message to the terminal device, and the second response message is used to indicate that the operation result of the life cycle operation on the target network is failure .
  • the target network is a user service function entity or other network functions that provide services to users.
  • the present application provides a communication device, and the communication device may be the terminal device in the foregoing method embodiment, or a chip provided in the terminal device.
  • the communication device includes a communication interface, a processor, and optionally, a memory.
  • the memory is used to store computer programs or instructions
  • the processor is coupled to the memory and the communication interface.
  • the communication device executes the method performed by the terminal device in the above method embodiments.
  • the present application provides a communication device, and the communication device may be the core network device in the foregoing method embodiment, or a chip provided in the core network device.
  • the communication device includes a communication interface, a processor, and optionally, a memory.
  • the memory is used to store computer programs or instructions
  • the processor is coupled with the memory and the communication interface, and when the processor executes the computer programs or instructions, the communication device executes the method performed by the core network device in the above method embodiment .
  • the present application provides a computer-readable storage medium, the computer-readable storage medium is used to store computer-executable instructions, and when the computer-executable instructions are executed, the In the method, the method performed by the terminal device is realized; or, the method performed by the core network device in the method described in the first aspect or the third aspect is realized.
  • the present application provides a computer program product including a computer program.
  • the computer program When the computer program is executed, the method performed by the terminal device in the method described in the first aspect or the second aspect is realized; or, so that The method performed by the core network device in the method described in the first aspect or the third aspect is implemented.
  • the present application provides a communication system, the communication system includes the communication device described in the fourth aspect and the fifth aspect above; or includes the communication device described in the sixth aspect and the seventh aspect above.
  • FIG. 1a is a schematic diagram of a network system architecture provided by an embodiment of the present application.
  • FIG. 1b is a schematic structural diagram of a core network provided by an embodiment of the present application.
  • FIG. 1c is a schematic diagram of another core network architecture provided by an embodiment of the present application.
  • FIG. 2 is a schematic structural diagram of a user-centric network provided by an embodiment of the present application.
  • FIG. 3 is an interactive schematic diagram of a network resource management method provided by an embodiment of the present application.
  • FIG. 4a is an interactive schematic diagram of creating a target network provided by an embodiment of the present application.
  • FIG. 4b is another schematic diagram of creating a target network interaction provided by the embodiment of the present application.
  • FIG. 5a is an interactive schematic diagram of a deletion target network provided by an embodiment of the present application.
  • FIG. 5b is an interactive schematic diagram of another deletion target network provided by the embodiment of the present application.
  • FIG. 6a is an interactive schematic diagram of modifying the network attributes of the target network provided by the embodiment of the present application.
  • FIG. 6b is another schematic diagram of interaction for modifying the network attributes of the target network provided by the embodiment of the present application.
  • FIG. 7 is an interactive schematic diagram of another network resource management method provided by the embodiment of the present application.
  • FIG. 8 is an interactive schematic diagram of another network resource management method provided by the embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • At least one (item) means one or more
  • “multiple” means two or more
  • “at least two (items)” means two or three and three
  • “and/or” is used to describe the association relationship of associated objects, which means that there can be three kinds of relationships, for example, “A and/or B” can mean: only A exists, only B exists, and A and B exist at the same time A case where A and B can be singular or plural.
  • the character “/” generally indicates that the contextual objects are an “or” relationship.
  • “At least one of the following” or similar expressions refer to any combination of these items, including any combination of single or plural items.
  • At least one item (piece) of a, b or c can mean: a, b, c, "a and b", “a and c", “b and c", or "a and b and c ", where a, b, c can be single or multiple.
  • the technical solution of the embodiment of the present application can be applied to various communication systems, for example: long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex) , TDD), new radio (new radio, NR), the third generation partner project (the 3rd generation partner project, 3GPP) service-based network architecture (service-based architecture, SBA) and the fifth generation (5th generation, 5G) Communication systems or communication systems that have evolved after 5G such as the sixth generation (6th generation, 6G) communication systems, etc.
  • LTE long term evolution
  • LTE frequency division duplex frequency division duplex
  • FDD frequency division duplex
  • time division duplex time division duplex
  • TDD time division duplex
  • new radio new radio
  • NR new radio
  • the third generation partner project the 3rd generation partner project, 3GPP
  • service-based network architecture service-based architecture, SBA
  • 5th generation, 5G Communication systems or communication systems that have evolved after
  • FIG. 1a is a schematic diagram of a network system architecture provided by an embodiment of the present application.
  • the terminal device can access the wireless network to obtain services from the external network (such as a data network (DN)) through the wireless network, or communicate with other devices through the wireless network, such as communicating with other terminals Device communication.
  • the wireless network includes a (wireless) access network ((radio) access network, (R) AN) and a core network (core network, CN), where the (R) AN (hereinafter referred to as RAN) is used to connect terminal equipment Connected to the wireless network, the CN is used to manage the terminal equipment and provide a gateway for communicating with the DN.
  • the terminal equipment, RAN, CN, and DN involved in the system architecture in FIG. 1a are described in detail below.
  • Terminal equipment includes equipment that provides voice and/or data connectivity to users.
  • terminal equipment is a device with wireless transceiver capabilities that can be deployed on land, including indoor or outdoor, handheld, wearable, or vehicle-mounted; it can also be deployed in On the water (such as ships, etc.); can also be deployed in the air (such as aircraft, balloons and satellites, etc.).
  • Terminal equipment can be mobile phone, tablet computer (Pad), computer with wireless transceiver function, virtual reality (virtual reality, VR) terminal, augmented reality (augmented reality, AR) terminal, industrial control (industrial control) Wireless terminals in vehicles, vehicle-mounted terminals, wireless terminals in self driving, wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety Terminals, wireless terminals in smart cities, wireless terminals in smart homes, wearable terminals, etc.
  • the embodiments of the present application do not limit the application scenarios.
  • a terminal device may sometimes be referred to as a terminal, user equipment (UE), access terminal, vehicle-mounted terminal, industrial control terminal, UE unit, UE station, mobile station, mobile station, remote station, remote terminal, mobile device, UE terminal, wireless communication device, UE proxy or UE device, etc.
  • Terminals can also be fixed or mobile. It can be understood that all or part of the functions of the terminal in this application may also be realized by software functions running on hardware, or by virtualization functions instantiated on a platform (such as a cloud platform).
  • the RAN may include one or more RAN devices (or access network devices).
  • the interface between the access network device and the terminal device may be a Uu interface (or called an air interface).
  • Uu interface or called an air interface
  • the access network device is a node or device that connects the terminal device to the wireless network.
  • the access network device includes but is not limited to: next generation node B (next generation node B, gNB) and evolved node in the 5G communication system.
  • radio network controller radio network controller
  • node B node B (node B, NB) , home base station ((home evolved nodeB, HeNB) or (home node B, HNB)), baseband unit (baseBand unit, BBU), transmission and receiving point (transmitting and receiving point, TRP), transmitting point (transmitting point, TP) , mobile switching center, device-to-device (Device-to-Device, D2D), vehicle outreach (vehicle-to-everything, V2X), machine-to-machine (machine-to-machine, M2M) communication equipment that undertakes the base station function etc., can also include the centralized unit (CU) and distributed unit (DU) in the cloud access network (cloud radio access network, C-RAN) system, non-terrestrial communication network (non-terrestrial network,
  • cloud radio access network cloud radio access network, C-RAN
  • non-terrestrial communication network non-terrestrial network
  • the CN may include one or more CN devices (that is, they may be understood as network element devices or functional network elements).
  • FIG. 1b is a schematic structural diagram of a CN provided by the present application
  • the CN in FIG. 1b is a schematic diagram of a CN in a 5G network architecture.
  • the CN shown in Figure 1b includes multiple CN devices: network slice selection function (network slice selection function, NSSF), network exposure function (network exposure function, NEF), network storage function (network function repository function, NRF), strategy Control function (policy control function, PCF), unified data management (unified data management, UDM), application function (application function, AF), network control function (network control function, NCF), specific network slice authentication and authentication function ( network slice specific authentication and authorization function (NSSAAF), authentication server function (authentication server function, AUSF), access and mobility management function (access and mobility management function, AMF), session management function (session management function, SMF), User plane function (UPF), service communication proxy (SCP), network slice admission control (Network Slice Admission Control Function, NSACF).
  • network slice selection function network slice selection function
  • NEF network exposure
  • AMF is a control plane function provided by the operator network, which is responsible for the access control and mobility management of terminal equipment accessing the operator network, such as including mobility status management, assigning temporary user IDs, authenticating and authorizing users, and other functions.
  • SMF is a control plane function provided by the operator network, responsible for managing the protocol data unit (protocoldata unit, PDU) session of the terminal device.
  • PDU protocol data unit
  • a PDU session is a channel for transmitting PDUs, and terminal equipment needs to transmit PDUs with DN through the PDU session.
  • the PDU session is established, maintained and deleted by the SMF.
  • SMF includes session management (such as session establishment, modification and release, including tunnel maintenance between UPF and RAN), UPF selection and control, service and session continuity (service and session continuity, SSC) mode selection, roaming and other session related function.
  • PCF is the control plane function provided by the operator, including user subscription data management function, policy control function, charging policy control function, service quality (quality of service, QoS) control, etc., mainly used to provide PDU session strategy to SMF .
  • the policy may include a charging-related policy, a QoS-related policy, an authorization-related policy, and the like.
  • the UPF is the gateway provided by the operator, and is the gateway for communication between the operator's network and the DN.
  • UPF includes user plane-related functions such as data packet routing and transmission, packet detection, quality of service (QoS) processing, uplink packet detection, and downlink data packet storage.
  • QoS quality of service
  • UDM is mainly used to manage user subscription data and authentication data, as well as authentication credit processing, user identification processing, access authorization, registration/mobility management, subscription management, and short message management.
  • the UDM may also include a unified data repository (unified data repository, UDR).
  • UDR unified data repository
  • the 3GP PSBA of the 5G system may also include a UDR.
  • UDR is used to provide storage and retrieval for PCF policies, storage and retrieval of open structured data, and storage of user information requested by application functions.
  • the aforementioned CN device may also be called a network element or a functional network element.
  • each functional network element can be the name of each functional network element shown in Figure 1b.
  • each functional network element can still be the name of each functional network element in Figure 1b.
  • the policy control network element may be a PCF.
  • the policy control function may still be a PCF, or may have other names. This application does not limited.
  • Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface serial numbers.
  • interface serial numbers refer to the meanings defined in relevant standard protocols, and there is no limitation here.
  • the CN includes user network access functions, user subscription authentication functions, network control functions, and resource management functions.
  • the user network access function is used to perform access control and mobility management on terminal equipment;
  • the user subscription authentication function is used to store and manage user subscription information;
  • the network control function is used to manage user network resources, such as Responsible for operations such as the generation, modification, and elimination of user networks;
  • the resource management function is used to manage network resources, such as allocating resources to generate network function instances required by user networks.
  • the user network is used to provide network services for one user or multiple users, and can be understood as a core network element for dedicated UE services.
  • the user network may consist of one or more network elements, which may be network elements dedicated to the user, or network elements shared with other users.
  • the user network may refer to the network element, and the network element may also refer to the user network.
  • the user network may be a network function that provides network services for terminal devices, one or a group of virtual machines, containers, processes, or other runnable resource collections.
  • USN user service node
  • the user network can be a USN, which can be understood as an integration of core network control functions, and is a core network element serving exclusively for the UE.
  • the USN can integrate session management (session management, SM) and/or policies
  • the function of project management (PM); or, USN can also be understood as the digital twin function of UE in the core network, which is the digital model of UE's real behavior, such as recording the service information used by UE, artificial intelligence (artificial intelligence) , AI) processing and other functions; or, USN can be understood as similar to a cloud server (cloud computer), UE can arrange resources provided by the operator on the cloud server, such as QoS settings for different services, Bandwidth allocation and more.
  • cloud server cloud computer
  • the USN can be integrated in the 5G network architecture shown in Figure 1b; it can also be integrated in the CN architecture shown in Figure 1c; in a possible implementation, the USN can be used as a newly added logical network element, Or as a logic function integrated in the existing network function in Fig. 1b or Fig. 1c.
  • USN can be integrated in AMF and SMF.
  • USN can also exist in the form of a user-centric network (UCN) architecture.
  • UCN user-centric network
  • the UCN architecture can be understood as a user-centric network, as shown in Figure 2
  • a UCN network architecture the UCN network architecture shown in Figure 2 includes a network service node (network service node, NSN) and a user service node (user service node, USN).
  • NSN network service node
  • USN user service node
  • the main functions of the NSN include the authentication of the access UE and the creation and life cycle management of the USN.
  • NCF is used to manage USN resources in the UCN network architecture, for example, it is responsible for operations such as generation, modification, and elimination of USNs.
  • NSN, USN and NCF involved in this application are only schematic names and should not be regarded as specific limitations thereto. That is to say, NSN, USN, and NCF can use other names in other technical solutions than this application, or be other communication devices with the same function.
  • NSN can be an access control function
  • NCF can be a network Resource control or management functions
  • USN can be terminal digital twin functions, etc.
  • the CN structure shown in FIG. 1c is only for the convenience of understanding the CN, and it is only an example where each functional network element is separately deployed in the CN.
  • various functional network elements can be integrated and deployed.
  • the network access function and user subscription authentication function in Figure 1c are integrated into the same functional network element, or the network access function in Figure 1c Functions and network control functions are integrated into the same functional network element and so on. This application does not specifically limit it.
  • the core network mentioned later in this application may refer to a certain functional network element in the core network, or the integration of several functional network elements in the core network, or the integration of all functional network elements in the core network. integrated.
  • the core network may be the core network in the 5G communication system shown in Figure 1b, or the core network shown in Figure 1c, or other possible communication systems (such as LTE communication systems or communication systems evolved after 5G 3.
  • the above-mentioned network element or function may be a network element in a hardware device, or a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform).
  • the foregoing network element or function may be implemented by one device, or jointly implemented by multiple devices, or may be a functional module in one device, which is not specifically limited in this embodiment of the present application.
  • DN can also be called packet data network (packet data network, PDN), which is a network located outside the operator's network.
  • PDN packet data network
  • the operator's network can access multiple DNs, and application servers corresponding to various services can be deployed in the DN.
  • End devices offer a wide variety of possible services.
  • the process for a user to modify the user network can be simply described as: the user interacts with the mobile network operator to appeal to the user; after the operator understands the user appeal, the operator modifies the configuration of the user network through the BSS and OSS to make the modification The final user network meets user demands.
  • the user modifies the user network through such a method, which usually takes a long effective period and low efficiency.
  • the present application provides a network resource management method, in which the user can use the control plane signaling (or user plane signaling) between the terminal device and the core network to carry an operation request message for the target network, so as to implement Compared with the way that users modify the target network through the carrier as the medium, the modification of the target network that the user provides network services shortens the effective cycle of the modification of the target network and improves efficiency.
  • control plane signaling or user plane signaling
  • FIG. 3 is a schematic flowchart of a network resource management method provided by an embodiment of the present application.
  • the method execution subject of the network resource management method may be a core network device or a chip in the core network device, or the execution subject may be a terminal device or a chip in the terminal device.
  • FIG. 3 uses the core network device and the terminal device as an example for illustration. in:
  • the terminal device determines a request message, where the request message is used to operate the life cycle of the target network.
  • the terminal device determines (or understands to generate) a request message for requesting an operation on the life cycle of the target network according to user requirements.
  • the operations on the life cycle of the target network include: creating the target network and deleting the target network.
  • the terminal device can determine a request message for creating a target network, or a request message for deleting a target network.
  • the target network may have multiple states, including: an existing state and an absent state. It should be understood that, the state of the target network being the existing state means that the target network exists, and the state of the target network being the non-existing state means that the target network does not exist.
  • the state of the target network being an existing state includes: the operating state of the target network is a suspended state (or referred to as a standby state, a state to be activated, a deactivated state, etc.) or the operating state of the target network is an activated state. state.
  • operating on the lifecycle of the target network may also include modifying the operating state of the target network.
  • modifying the operating state of the target network includes suspending the target network, such as changing the operating state of the target network from an active state to a suspended state; or restoring (or activating) the target network, such as changing the operating state of the target network from The pending state changes to the active state.
  • modifying the operating state of the target network may also include modifying the operating state of the target network to a normal operating state when the operating state of the target network is an abnormal (or faulty) state.
  • the target network further includes various network attributes, including but not limited to: one or more of: capacity (ie, capacity-related parameters), capability (ie, network energy-related parameters), configuration policy, or service user list Various.
  • capacity ie, capacity-related parameters
  • capability ie, network energy-related parameters
  • configuration policy ie, configuration policy
  • service user list ie, configuration policy
  • service user list ie, configuration policy
  • operating on the lifecycle of the target network may also include modifying network attributes of the target network.
  • the target network mentioned in this application refers to a network function (network function, NF) used to provide network services for terminal devices, one or a group of virtual machines, containers, processes or other runnable resource collections .
  • the network service includes but not limited to one or more of data download, data access and call.
  • the target network may be a user service function entity or other network functions that provide services to users.
  • the target network may be a USN network element or a USN functional entity.
  • the request message includes information of an operation type, and the operation type is one of creating a target network, deleting a target network, suspending the target network, restoring the target network, or modifying network attributes of the target network.
  • creating a target network refers to generating (or establishing) a target network that provides network services for terminals from scratch.
  • Deleting the target network means deleting the connection relationship of the target network (such as the connection relationship between the target network and the access network device, etc.), and deleting the resources occupied by the target network (such as operating resources, etc.).
  • Suspending the target network means setting the state of the target network to a suspended state (or called a standby state, a state to be activated, a deactivated state, etc.).
  • To resume a target network is to change the state of the target network from suspended to active.
  • Modifying the network attributes of the target network can be understood as modifying the capacity of the target network (that is, modifying capacity-related parameters), modifying the capabilities of the target network (modifying network capability-related parameters), modifying the configuration policy of the target network, or modifying the service user list of the target network one or more of .
  • the information of the operation type may be an index value, and the index value has a mapping relationship with the operation type.
  • the mapping relationship may be specified in the protocol, pre-configured, or agreed between the terminal and the core network.
  • a specific implementation manner of the operation type information may be: the request message includes field 1, where the field 1 is used to indicate the operation type. For example, refer to Table 1 for the mapping relationship between the value of field 1 and the operation type.
  • the terminal device determines that the value of field 1 in the request message is 2. It should be noted that the expression form of the field 1 value in this example is only exemplary, and should not be regarded as a specific limitation to the application.
  • the value of the field 1 can also be represented by bits, such as field 1 Including 3 bits (bit), at this time, when the value of field 1 is 000, it means that the operation type is to create the target network; when the value of field 1 is 001, it means that the operation type is to modify the target network; when the value of field 1 If it is 010, it means that the operation type is to suspend the target network; when the value of field 1 is 011, it means that the operation type is to restore the target network; when the value of field 1 is 100, it means that the operation type is to modify the network attributes of the target network.
  • bits such as field 1 Including 3 bits (bit), at this time, when the value of field 1 is 000, it means that the operation type is to create the target network; when the value of field 1 is 001, it means that the operation type is to modify the target network; when the value of field 1 If it is 010, it means that the operation type is to suspend the target network; when the value of field 1 is 011, it means that the operation type is to restore the target
  • the request message further includes one or more of user information of the terminal device, operation parameters corresponding to the operation type, or target network information.
  • the user information includes information used to indicate the permanent identity of the user (for example, a permanent subscriber identity (subscription permanent identifier, SUPI), an international mobile subscriber identification number (international mobile subscriber identification number, IMSI), a mobile subscriber's ISDN number (mobile subscriber international ISDN number, MSISDN)), user group identity, user temporary identity (such as globally unique temporary identity (GUTI)) or equipment identity (such as permanent equipment identifier (PEI), international mobile equipment One or more of the identification (international mobile equipment identity, IMEI)).
  • the operation parameter corresponding to the operation type can indicate a specific operation.
  • the operation parameter carried in the request message indicates to create a specific target network; when the request message is to modify the network of the target network
  • the operation parameter carried in the request message indicates to modify a certain (or several) specific network attributes of the target network.
  • the information of the target network includes one or more of target network identifier, capacity value, capability list, user service list, or configuration policy.
  • the request message determined by the terminal device of user 11 may include: the identity of user 11, the operation type is to create a network, and the operation parameters include capacity value a1 and Ability value p1.
  • the user service list of the target network N1 includes user 11 , user 12 and user 21 .
  • User 11 (can be understood as a user with management authority on the target network N1) wants to remove user 21 from the user service list of the target network N1, then the terminal device of user 11 determines a request message for operating the target network N1, the request message It may include: the identifier of the user 11, the identifier of the target network N1, the operation type of modifying the network attribute of the target network, and the operation parameter of deleting the identifier of the user 21 in the user service list of the target network N1.
  • the terminal device sends the request message to the core network, and correspondingly, the core network receives the request message.
  • the request message is control plane signaling or user plane signaling between the terminal device and the core network.
  • the terminal device sends the request message to the core network through control plane signaling or user plane signaling between the terminal device and the core network.
  • control plane signaling may be non-access stratum (non-access stratum, NAS) signaling.
  • the user plane signaling may be a message based on a packet radio service technology tunneling protocol (general packet radio service tunneling protocol, GTP) user plane (that is, GTP-U).
  • GTP general packet radio service tunneling protocol
  • the core network device executing step S302 is a first functional network element, and the terminal device sends the request message to the first functional network element, where the first functional network element is used to connect the terminal device to the core network, That is, the first functional network element has a user network access function.
  • the first functional network element may be the AMF network element in FIG. 1b or the NSN network element in FIG. 2 .
  • the first functional network element may also be called an access management network element or a network service network element.
  • the core network operates on the life cycle of the target network managed by the core network.
  • the core network creates the target network, deletes the target network, modifies the operation state of the target network (including suspending the target network or restoring the target network), or modifies the network attributes of the target network according to the operation type information in the request message.
  • the core network manages one or more user networks, and the operation types in the request message are: delete the target network, modify the operating status of the target network (including suspending the target network or restoring the target network), Or in the case of modifying any of the network attributes of the target network, the core network determines the target network from the plurality of networks based on the request message, and performs operations on the life cycle of the target network.
  • the core network device performing step S303 is a second functional network element, and the second functional network element is used to operate the life cycle of the target network.
  • the second functional network element may be an NCF network element.
  • the second functional network element may also be called a network control network element.
  • the second functional network element may be co-located with the foregoing first functional network element (that is, a certain entity has both the function of the first functional network element and the function of the second functional network element), or the second functional network element
  • the second-function network element may be deployed separately from the aforementioned first-function network element.
  • there is a communication connection between the first functional network element and the second functional network element that is, it can be understood that the first functional network element can communicate with the second functional network element element to communicate).
  • the first functional network element may forward the first request message to the second functional network element, and then in S303, the second functional network element can operate the life cycle of the target network according to the request message.
  • the first functional network element may send a second request message to the second functional network element according to the first request message (the second request The content included in the message may be the same as that included in the first request message), so that the second functional network element operates on the life cycle of the target network according to the second request message.
  • the second functional network element when the second functional network element is deployed separately from the first functional network element, in order to improve the security of the communication system, the second functional network element may authenticate the identity of the first functional network element; After passing the identity authentication of the first functional network element, the second functional network element operates on the life cycle of the target network.
  • the second functional network element verifies the identity of the first functional network element, and the verification content includes but not limited to one of the following or more: verify whether the first functional network element really exists; or, verify whether the first functional network element has the authority to send the second request message (that is, whether the first functional network element has the ability to request the second functional network element to the target network The authority to operate in the life cycle); or, verify whether the first functional network element is legal.
  • the second functional network element operates the life cycle of the target network according to the second request message.
  • the second functional network element is deployed separately from the first functional network element as an example, to create a target network, delete a target network, modify the operating status of the target network, or modify the network of the target network Attributes are illustrated as examples.
  • the connection between the target network and the access network device may be a direct connection (hereinafter referred to as direct connection) or an indirect connection (hereinafter referred to as indirect connection).
  • direct connection a direct connection
  • indirect connection an indirect connection
  • the target network is directly connected to the access network device, that is, the access network device can directly communicate with the target network, in other words, the access network device receives a service request message from the terminal device (the service request message is used for After requesting the target network to provide network services), the access network device may directly forward the service request message to the target network, so that the target network provides corresponding network services.
  • the target network is not directly connected to the access network device, that is, the access network device communicates indirectly with the target network through the first functional network element.
  • the access network device after the access network device receives the service request message from the terminal device, the access network device sends the service request message to the first functional network element, and the first functional network element forwards the service request message to the target network, so that the target network The network provides corresponding network services.
  • the signaling transmission cost can be saved; when the target network is not directly connected to the access network device, the access network device cannot directly contact the target network, which can improve the reliability of the target network. safety.
  • the following explains in detail the process of creating a target network based on the direct connection between the target network and the access network device and the non-direct connection between the target network and the access network device.
  • FIG. 4a is a schematic flow chart of creating a target network provided by the present application. in:
  • the second functional network element interacts with the resource management function to create a target network.
  • the second functional network element interacts with the resource management function, applies for available running resources, and instantiates running entities.
  • This running entity may be a newly instantiated virtual machine, a newly instantiated container, or a new process, thread, or other runtime execution entity running on an existing virtual machine or container; further, the second function network
  • the element creates a target network based on a request message from an end device.
  • the resource management function is used to manage network resources, such as allocating resources to generate network function instances required by the user network.
  • the resource management function may be a management and orchestration (management and orchestration, MANO) network element, a container (docker) management network element, a docker engine, or other resource management functions.
  • the core network may further include a third functional network element, where the third functional network element is used to store network configuration data, where the network configuration data includes network configuration parameters and/or network operation policy data.
  • the network configuration parameters include parameters required for network operation (such as one or more of data packet loss rate, delay, bandwidth or network speed), scripts or environment variables required for network operation. types; network operation policy data include one or more of QoS policy, charging policy or user access control policy.
  • the network configuration data in the third functional network element is associated with a user identifier, or the network configuration data in the third functional network element is associated with a network identifier, or each of the third functional network elements A piece of configuration data is associated with an index value.
  • the request message carries the user identifier and the operation type (the operation type here is to create a target network)
  • the second functional network element Create the target network according to the interaction between the user's identification and the resource management function, and the second functional network element (or target network) obtains the network configuration data corresponding to the target network from the third functional network element according to the user identification; further, the second functional network element The network element configures the target network based on the network configuration data.
  • the request message carries the user identifier and the operation type (here, the operation type is to create a target network).
  • the second functional network element interacts with the resource management function according to the user identifier to create a target network; the target network (or the second functional network element) obtains the target network from the third functional network element according to the identifier of the target network Identifies the corresponding network configuration data.
  • the target network (or the second functional network element) configures the target network based on the network configuration data.
  • the request message carries the user identifier, operation type (the operation type here is to create a target network) and operation-related parameters (Here are the specific parameters for creating the target network, such as the capacity value, capability, service user list, etc. of the target network).
  • the second functional network element interacts with the resource management function according to the user identifier to create a target network; the target network (or the second functional network element) determines the target index value according to the operation parameter, and obtains the target index value from the target index value according to the target index value.
  • the three-function network element obtains the network configuration data corresponding to the target network identifier.
  • the target network (or the second functional network element) configures the target network based on the network configuration data.
  • the target network interacts with the access network device to establish a communication connection and a user context connection.
  • the second functional network element sends the information of the access network device to the target network, and notifies to update the user context information; wherein, the information of the access network device is used to address the access network
  • the user context information is used to establish a user context connection.
  • the target network establishes a communication connection with the access network device according to the information of the access network device, and establishes a user context connection according to the user context information.
  • the access network device is a device that connects the terminal device to the target network; the information of the access network device is used to address the access network device, for example, the access network device includes an access network device identifier, and /or, address information of the access network device.
  • the second functional network element sends the information of the target network to the access network device, and notifies to update the user context information; where the information of the target network is used to address the target network, the User context information is used to establish user context connections.
  • the access network device establishes a communication connection with the target network according to the information of the target network, and establishes a user context connection according to the user context information.
  • the access network device is a device for connecting the terminal device to the target network; the information of the target network is used to address the target network, for example, the information of the target network includes the identity of the target network, and/or, the target network Address information.
  • the communication connection includes the underlying layer established based on hypertext transfer protocol (hypertext transfer protocol, HTTP), transmission control protocol (transmission control protocol, TCP), stream control transmission protocol (stream control transmission protocol, SCTP) or other protocols.
  • hypertext transfer protocol hypertext transfer protocol
  • TCP transmission control protocol
  • SCTP stream control transmission protocol
  • User context information includes user status, user attribute information and user-related communication connection information.
  • the access network device modifies the connection information of the terminal device.
  • the access network device modifies the sending path (or routing path) of the message from the terminal device, so that the subsequent access network device forwards the message from the terminal device to the target network.
  • a network service request message (for example, a PDU session establishment request message).
  • the second functional network element interacts with the resource management function to create a target network.
  • the target network sends a first update request to the first functional network element, and correspondingly, the first functional network element receives the first update request from the target network.
  • the first update request is used to request the first functional network element to update (or understand to modify) the access control of the target network.
  • the first update request carries the information of the target network, and notifies to update the user context information; where, the information of the target network is used to address the target network, for example, the information of the target network includes but not limited to Identification or address information of the target network; this user context information is used to establish a user context connection.
  • the first functional network element updates (or modifies) the connection information based on the first update request.
  • the first functional network element saves the information of the target network, and establishes a communication connection and a user context connection, so that when the first functional network element receives a request message for requesting the target network to provide network services (or access to the target network After receiving the request message), the first functional network element will receive the request message for requesting the target network to provide network services, and forward it to the target network.
  • the first functional network element sends a second update request to the access network device, and correspondingly, the access network device receives the second update request from the first functional network element.
  • the second update request may establish a communication connection and a user context connection related to the target network between the access network device and the first functional network element, that is, both the communication connection and the user context connection are associated with the target network.
  • the second update request is used to request the access network device to update (or understand to modify) the access control of the target network.
  • the second update request carries the information of the target network, and the information of the target network is used to address the target network.
  • the information of the target network includes but not limited to an identifier of the target network or address information of the target network.
  • the access network device sends a response message to the second update request to the first functional network element, and correspondingly, the first functional network element receives the response message from the access network device to the second update request.
  • the response message carries the operation result of the access network device based on the second update request.
  • the access network device performs a corresponding operation based on the second update request: a communication connection and a user context connection related to the target network are established between the access network device and the first functional network element, that is, the communication connection and the user context connection are related to the target network couplet. Further, the access network device sends a response message to the second update request to the first functional network element according to the operation result based on the second update request.
  • the first functional network element sends a response message to the first update request to the target network, and correspondingly, the target network receives the response message from the first functional network element to the first update request.
  • the response message to the first update request is used to indicate the operation result of the first functional network element according to the first update request and the operation result of the access network device based on the second update request.
  • the first functional network element sends to the target network the The operation result of the response message of the first update request is success.
  • the operation result of the first functional network element according to the first update request is failure, or the operation result of the access network device based on the second update request is failure, the first functional network element sends to the target network the The operation result of the reply message of an update request is failure.
  • the process of deleting the target network will be explained in detail below based on the situation where the target network is directly connected to the access network device (hereinafter referred to as direct connection) and the case where the target network is not directly connected to the access network device.
  • FIG. 5a is a schematic flow chart of deleting the target network provided by the present application. in:
  • the second functional network element sends a control operation request message to the target network.
  • the target network receives the control operation request message from the second functional network element.
  • the control operation request message includes an operation type (here, delete the target network) .
  • the second functional network element receives a request message from the terminal device, where the request message is used to delete the target network.
  • the second functional network element sends a control operation request message to the target network, where the control operation request message is used to instruct the target network to disconnect the link.
  • the target network sends a link disconnection request to the access network device, and correspondingly, the access network device receives the link disconnection request from the target network.
  • the target network deletes the user uplink connection with the access network device according to the control operation request message sent by the second functional network element, and sends a disconnection request to the access network device, and the disconnection request is used to indicate (or Notification)
  • the access network device deletes the user context connection with the target network.
  • the link disconnection request includes the information of the target network, and the information of the target network is used to address the target network.
  • the information of the target network includes, but is not limited to, the information of the target network includes an identifier of the target network, and/or, address information of the target network.
  • the access network device deletes the user context connection with the target network according to the disconnection request.
  • the access network device can smoothly delete the user context connection with the target network.
  • the process of smoothly deleting the user context connection can be described as: the access network device sends a notification message to the terminal device, and the notification message is used to notify the terminal device served by the target network to be offline; after all the terminal devices served by the target network are offline, The access network device then deletes the user context connection with the target network.
  • unlinking is performed after all users of the target online reading are offline, which can improve user experience.
  • the access network device may unsmoothly delete the user context connection with the target network according to the link disconnection request. In other words, after the access network device receives the disconnection request, the access network device directly deletes the user context connection with the target network regardless of whether the terminal device served by the target network is offline. Through such a method, the efficiency of unlinking the access network device can be improved.
  • the access network device sends a response message corresponding to the link disconnection request to the target network, and correspondingly, the target network receives the response message corresponding to the link disconnection request sent from the access network device.
  • the response message carries the operation result of the access network device based on the disconnection request.
  • the unlinking mentioned in this application refers to deleting the context connection between two devices, and the response message is transmitted through the signaling channel, so after the two devices are unlinked, the subsequent transmission of the response message will not be affected (That is, the two devices can still transmit the response message through the signaling channel (or communication connection)).
  • the access network device can send the A functional network element sends a response message to the second link disconnection request.
  • the target network sends a response message to the control operation request message to the second functional network element, and correspondingly, the second functional network element receives the response message from the target network to the second link disconnection request.
  • the response message carries the link disconnection operation result of the user context connection between the target network and the access network device.
  • the second functional network element interacts with the resource management function to release the resources of the target network.
  • the second functional network element releases the resources of the target network. After releasing the resources of the target network, it can be understood as all communication connections related to the target network (including the communication connection between the target network and the second functional network element, and the connection between the target network and the The communication connection between the access network devices) is removed. Wherein, the deletion of the communication connection may be one or more of the deletion of the underlying connection completed based on HTTP, TCP, SCTP or other protocols.
  • FIG. 5 b is a schematic flowchart of another deletion of the target network provided by the present application. in:
  • the second functional network element sends a control operation request message to the target network, and correspondingly, the target network receives the control operation request message from the second functional network element.
  • the control operation request message includes the operation type (here, deleting the target network).
  • the target network sends a first link disconnection request to the first functional network element, and correspondingly, the first functional network element receives the first link disconnection request from the target network.
  • the target network sends a first link disconnection request to the first functional network element according to the control operation request message sent by the second functional network element, and the first link disconnection request is used to instruct (or notify) the first functional network element to delete the User context connections between target networks.
  • the link disconnection request includes the information of the target network, and the information of the target network is used to address the target network.
  • the information of the target network includes, but is not limited to, the information of the target network includes an identifier of the target network, and/or, address information of the target network.
  • the first functional network element sends a second unlink request to the access network device, and correspondingly, the access network device receives the second unlink request from the first functional network element.
  • the first functional network element sends a second link disconnection request to the access network device, and the second link disconnection request is used to instruct (or notify) the access network device to delete the link between the first functional network element and the access network device.
  • the link disconnection request includes the information of the target network, and the information of the target network is used to address the target network.
  • the information of the target network includes, but is not limited to, the information of the target network includes an identifier of the target network, and/or, address information of the target network.
  • the access network device performs connection deletion processing according to the second link disconnection request.
  • the access network device may perform smooth connection deletion processing according to the second link disconnection request.
  • the access network device may perform non-smooth connection deletion processing according to the second link disconnection request.
  • the access network device sends a response message to the second disconnection request to the first functional network element, and correspondingly, the first functional network element receives the response message from the access network device to the second disconnection request.
  • the response message carries the operation result of the access network device based on the second unlinking request.
  • the first functional network element sends a response message to the first link disconnection request to the target network, and correspondingly, the target network receives a response message from the first functional network element to the second link disconnection request.
  • the response message carries the operation result of the first functional network element based on the first link disconnection request, or further includes the operation result of the access network device based on the second link disconnection request.
  • the target network sends a response message to the control operation request message to the second functional network element, and correspondingly, the second functional network element receives the response message from the target network to the second link disconnection request.
  • the response message carries the operation result of the first functional network element based on the first link disconnection request, or further includes the operation result of the access network device based on the second link disconnection request.
  • the second functional network element interacts with the resource management function to release the resources of the target network.
  • the second functional network element releases the resources of the target network. After releasing the resources of the target network, it can be understood as all communication connections related to the target network (including the communication connection between the target network and the second functional network element, and the connection between the target network and the The communication connection between the first functional network elements) is removed.
  • Modify the target network modify the network attributes of the target network or modify the operating status of the target network (including suspending the target network or restoring the target network))
  • Figure 6a is a modification of the target network (modification of the operating status of the target network or modification of the network attributes of the target network) provided by this application ) flow diagram. in:
  • the second functional network element sends a first control operation request message to a target network, and correspondingly, the target network receives the first control operation request message from the second functional network element.
  • the first control operation request message includes an operation type.
  • the operation type is one of modifying the operating state of the target network (ie, suspending the target network or restoring the target network) or modifying the network attributes of the target network.
  • the first control operation request message is used to request the target network to perform operation processing corresponding to the operation type, that is, one of modifying the running state of the target network (that is, suspending the target network or restoring the target network) or modifying the network attribute of the target network.
  • the first control operation request message may also include identification information of the target network.
  • modifying the network attribute of the target network includes modifying one or more of the following items: 1. Modifying the network capability of the target network, for example, opening or closing the device capability or service (service) corresponding to the target network , where the service may refer to the service provided by each NF defined by 3GPP, in this case, after modifying the service provided by the NF, a registration update to the NRF will be triggered. 2. Modify the network capacity of the target network, such as increasing the capacity value of the target network (expansion processing), reducing the capacity value of the target network (shrinking processing), or modifying the capacity value of the target network to a specific value or level to thereby Realize the expansion or contraction of the target network. 3.
  • the user information includes user permanent identification (such as IMSI/SUPI/MSISDN), user group identification, and user temporary identification ( One or more of such as GUTI), equipment identification (such as PEI/IME).
  • user permanent identification such as IMSI/SUPI/MSISDN
  • user group identification such as user group identification
  • user temporary identification One or more of such as GUTI
  • equipment identification such as PEI/IME
  • the first control operation request message when used to modify the network attribute of the target network, the first control operation request message may further include an operation parameter.
  • the second functional network element sends a second control operation request message to the first functional network element, and correspondingly, the first functional network element receives the second control operation request message from the second functional network element.
  • the second control operation request message includes an operation type.
  • the second control operation request message is used to request the first functional network element to perform an operation corresponding to the operation type on the information of the target network, that is, one of suspending the target network, restoring the target network, or modifying the network attributes of the target network .
  • the second control operation request message may also include identification information of the target network.
  • the second control operation request message when used to modify the network attribute of the target network, the second control operation request message may further include an operation parameter.
  • S601 and S602 are only exemplary, and should not be regarded as a specific limitation to the present application.
  • S601 and S602 may be executed at the same time, or S602 may be executed before S601, or S601 may be executed before S602.
  • the target network performs corresponding operation processing according to the operation type in the first control operation request message.
  • Suspending the target network by the target network specifically includes: recording the working status of the user context to prohibit the user from subsequent signaling, ending and reporting the user's statistical information and bill data, or immediately (or triggered by a timer) deattaching to the user one or more of .
  • Recovering (or activating) the target network by the target network specifically includes: recording the working state of the user context to restore the user's subsequent signaling, restoring the user's statistical information and bill data, or allowing the user's subsequent signaling.
  • the target network modifies the network attributes of the target network, which specifically includes: the target network modifies the network attributes of the target network (including one or more of network capability, network capacity, or user list) according to the operating parameters in the first control operation request message. ).
  • the target network sends a feedback message corresponding to the first control operation request message to the second functional network element, and correspondingly, the second functional network element receives the first feedback message corresponding to the first control operation request message from the target network.
  • the target network After the target network performs corresponding operation processing based on the first control operation request message, based on the operation result, the target network sends the first feedback message to the second functional network element.
  • the first feedback message includes first operation result information, where the first operation result information is used to indicate the operation result of the operation performed by the target network based on the first control operation request message.
  • the first operation result information may include a first failure cause value, where the first failure cause value is used to indicate a specific reason for the operation failure of the target network.
  • the first feedback message includes one or more of the identity of the target network, the state of the target network after the operation process (including the activation state or the suspension state), and the network attribute information of the target network .
  • the first functional network element performs operation processing according to the second control operation request message.
  • the first functional network element performs corresponding operation processing according to the specific content of the second control operation request message sent by the second functional network element.
  • the first functional network element suspends the target network in the information list maintained by itself, that is, updates the information of the target network to ( or modified to) the corresponding information when the target network is suspended, specifically including: recording the working state of the user context to prohibit the user from subsequent signaling, ending and reporting the user's statistical information and bill data, or immediately (or through timing) through signaling trigger) to detach or deregister the user.
  • the first functional network element restores the target network in the information list maintained by itself, that is, updates the information of the target network to (or It is modified to) the corresponding information when the target network is activated, specifically including: recording the working status of the user context to restore the user's subsequent signaling, restoring the user's statistical information and bill data, or allowing the user to perform one or more of subsequent signaling.
  • the first functional network element modifies the target network element in the information list maintained by itself based on the second control operation request message.
  • the network attribute information of the network can be understood as modifying the network attribute information of the target network according to the operation parameters in the second control operation request message.
  • the first functional network element sends a network control access update request message to the access network device.
  • the access network device receives the network control access update request message from the first functional network.
  • the Network Control Access Update Request message includes an operation type.
  • the network control access update request message is used to request the access network device to perform corresponding operations on the information of the target network, that is, to update (or modify) the information of the target network to the target network Corresponding information when the network hangs.
  • the update request may also include identification information of the target network.
  • the network control access update request message is used to request the access network device to perform corresponding operations on the information of the target network, that is, to update (or modify) the information of the target network to For) the corresponding information when the target network is activated.
  • the update request may also include identification information of the target network.
  • the network control access update request message is used to request the access network device to modify the network attribute of the target network maintained by it.
  • the second control operation request message may also include identification information and operation parameters of the target network.
  • the access network device performs operation processing according to the network control access update request.
  • the access network device performs corresponding operation processing according to the specific content of the network control access update request.
  • the access network device updates (or modifies) the information of the target network as the target network suspend in the information list maintained by itself.
  • the corresponding information at the beginning specifically includes: recording the working status of the user context to prohibit the user from subsequent signaling, ending and reporting the user's statistical information and bill data, or immediately (or triggered by a timer) to attach to the user one or more of .
  • the access network device updates (or modifies) the information of the target network as target network activation in the information list maintained by itself.
  • the information corresponding to the time includes: recording the working status of the user context to restore the user's subsequent signaling, restoring the user's statistical information and bill data, or allowing the user to perform one or more of subsequent signaling.
  • the access network device when the operation type in the network control access update request is to modify the network attribute of the target network, the access network device maintains the access network device according to the operation parameters in the network control access update request. modify the network properties of the target network.
  • the access network device sends the second feedback message corresponding to the network control access update request to the first functional network element.
  • the first functional network element receives the second feedback message corresponding to the network control access update request from the access network device. Two feedback messages.
  • the access network device After the access network device performs corresponding operation processing according to the network control access update request, the access network device sends the second feedback message to the first functional network element.
  • the second feedback message includes second operation result information, and the second operation result information is used to feed back the operation result of the access network device to the first functional network element, where the second operation result information is used to indicate that the operation is successful or operation failed.
  • the second operation result information may include a second failure cause value, and the second failure cause value is used to indicate a specific reason for the operation failure of the access network device.
  • the second feedback message may also include the identifier of the target network, the status of the target network at the access network device after the operation process (including the active state or the suspended state), and the network status of the target network.
  • the identifier of the target network may also include the identifier of the target network, the status of the target network at the access network device after the operation process (including the active state or the suspended state), and the network status of the target network.
  • One or more of attribute information may be included in the target network.
  • the first functional network element sends a third feedback message corresponding to the second control operation request message to the second functional network element.
  • the second functional network element receives the second control operation request message from the first functional network element corresponding to The third feedback message of .
  • the third feedback message includes third operation result information, and the third operation result information is used to feed back the operation results of the first functional network element and the access network device to the second functional network element, and the third operation result is as follows: Either of the following situations: 1. When the operation result of the access network device is successful and the operation processing result of the first functional network element is successful, the operation result information carried in the third feedback message is successful; 2. When the operation result of the network equipment is failure, or the operation processing result of the first functional network element is failure, the operation result carried in the third feedback message is failure, and the third feedback message may also carry the third failure reason at this time Value (for indicating that the operation result of the third feedback message is a specific reason for failure).
  • the third feedback message may also carry status information of the target network at the first functional network element (including an active state or a suspended state), an identifier of the target network, or network attribute information of the target network one or more of.
  • Figure 6b is a modification of the target network (modification of the operating state of the target network or modification of the network attributes of the target network) provided by this application ) flow diagram. in:
  • the second functional network element sends a first control operation request message to the target network, and correspondingly, the target network receives the first control operation request message from the second functional network element.
  • the first control operation request message includes an operation type.
  • the target network performs corresponding operation processing according to the operation type in the first control operation request message.
  • the target network sends a second control operation request message to the first functional network element, and correspondingly, the first functional network element receives the second control operation request message from the target network.
  • the second control operation request message includes an operation type.
  • the second control operation request message is used to request the first functional network element to perform an operation corresponding to the operation type on the information of the target network, that is, one of suspending the target network, restoring the target network, or modifying the network attributes of the target network .
  • the second control operation request message may further include identification information of the target network.
  • the second control operation request message when used to modify the network attribute of the target network, the second control operation request message may further include an operation parameter.
  • the first functional network element performs operation processing according to the second control operation request message.
  • the first functional network element sends a network control access update request message to the access network device.
  • the access network device receives the network control access update request message from the first functional network element.
  • the Network Control Access Update Request message includes an operation type.
  • the access network device performs operation processing according to the network control access update request.
  • the access network device sends the second feedback message corresponding to the network control access update request to the first functional network element.
  • the first functional network element receives the network control access update request from the access network device.
  • the first functional network element sends a third feedback message corresponding to the second control operation request message to the target network, and correspondingly, the target network receives the third feedback message corresponding to the second control operation request message from the first functional network element.
  • the target network sends the first feedback message corresponding to the first control operation request message to the second functional network element, and correspondingly, the second functional network element receives the first feedback message corresponding to the first control operation request message from the target network.
  • the target network sends the first feedback message to the second functional network element based on the feedback message from the first functional network element and the operation processing result of the target network based on the first control operation request message.
  • the first feedback message includes first operation result information, and the first operation result information is used to feed back the operation results of the target network, the first functional network element, and the access network device to the second functional network element.
  • the first operation result information is any of the following situations: 1. When the operation result of the first functional network element is successful, the operation result of the access network device is successful, and the operation processing result of the target network is successful, The operation result carried in the first feedback message is success; 2.
  • the second A feedback message may also carry a failure reason value (for indicating that the operation result of the first feedback message is a specific reason for failure).
  • the first feedback message may also carry the state of the target network at the first functional network element (including the active state or suspended state), the identifier of the target network, or the network attribute information of the target network one or more of .
  • the terminal device can directly operate the target network through the core network device. Compared with the way that the user modifies the target network through the operator as the medium, the time for modifying the target network is shortened. Effective cycle, improve efficiency.
  • FIG. 7 is a schematic flowchart of another network resource management method provided by an embodiment of the present application.
  • the method execution subject of the network resource management method may be a core network device or a chip in the core network device, or the execution subject may be a terminal device or a chip in the terminal device.
  • FIG. 7 uses the core network device and the terminal device as an example for illustration. in:
  • the terminal device determines a request message, where the request message is used to operate the life cycle of the target network.
  • the terminal device sends the request message to the core network device, and correspondingly, the core network device receives the request message from the terminal device.
  • the core network device performs operation authentication based on the request message.
  • the core network device After the core network device receives the request message from the terminal device, the core network device performs operation authentication on the request message, and identifies whether the request message comes from a legal (or understood as real) terminal device, or identifies the request message's Whether the content is legal (or understandable to be executed by the core network device, that is, the terminal device has the operation authority corresponding to the request message), prevent the core network device from performing invalid operations according to the request message, and improve the security of the target network.
  • the core network device performs operation authentication based on the request message, including one or more of the following methods:
  • Method 1 The core network device authenticates the state of the target network according to the operation type.
  • the core network device judges whether the target network can perform the processing operation corresponding to the operation type in the request message according to the state of the target network, that is, the core network device judges whether the operation type is consistent with the target network’s The status matches. If the operation type matches the state of the target network, the core network device passes the state authentication of the target network; or, if the operation type does not match the state of the target network, the core network device fails the state authentication of the target network .
  • the operation type matches the state of the target network, which means that the core network device determines that the target network can be processed according to the operation type in the request message according to the state of the target network; otherwise, the operation type matches the state of the target network.
  • the status mismatch of the target network means that the core network device determines that the target network cannot perform the processing operation corresponding to the operation type in the request message according to the status of the target network.
  • the operation type does not match the state of the target network, and includes one or more of the following items: 1.
  • the operation type is creating a target network, the state of the target network is existing. 2.
  • the operation type is to delete the target network, the status of the target network is non-existent. 3.
  • the operation type is modifying the network attribute of the target network, the status of the target network is non-existent. 4.
  • the operation type is to suspend the target network, the status of the target network is non-existent or suspended. 5.
  • the operation type is to restore the target network, the status of the target network is non-existent or activated.
  • the operation type when the operation type is to create a target network and the target network does not exist, it can be determined that the operation type matches the state of the target network; State matching; when the operation type is modifying the network attributes of the target network, and the target network exists, it can be determined that the operation type matches the state of the target network; when the operation type is suspending the target network, and the target network exists and is in an active state, then It can be determined that the operation type matches the state of the target network; when the operation type is to restore the target network, and the target network exists and is in a suspended state (or deactivated state, standby state), then it can be determined that the operation type matches the state of the target network.
  • a suspended state or deactivated state, standby state
  • Method 2 The core network device authenticates the operation authority of the operation type.
  • the core network device verifies whether the terminal device sending the request message has the operation authority corresponding to the operation type. If the terminal device has the operation authority corresponding to the operation type, the operation authority authentication of the core network device for the operation type passes; or, if the terminal device does not have the operation authority corresponding to the operation type, the core network device for the operation type Permission authentication failed.
  • the request message further includes user information of the terminal device, and further, the core network device obtains user subscription information based on the user information; the core network device obtains user subscription information based on the user subscription information and/or local configuration
  • the operation permission of the operation type is authenticated.
  • the user subscription information includes one or more of a list of allowed operation actions, a list of allowed network identifiers, a list of allowed network capacity quotas, a list of allowed service users, or a list of configuration policies.
  • the local configuration strategy can be understood as the management and control strategy of the operator or the management and control strategy of the core network equipment.
  • the core network device can obtain user subscription information according to the user information of the terminal device, and the user subscription information includes the allowed operation authority of the terminal device. Further, the core network device determines whether the terminal device can request to perform the operation type in the request message according to the operation authority allowed by the terminal device in the user subscription information. When the user subscription information contains the operation type in the request message, the core network device passes the authentication of the operation authority of the operation type; otherwise, when the user subscription information does not contain the operation type in the request message, the core network device passes the Type of operation authority authentication failed (that is, failed).
  • the core network device receives the request message sent by the terminal device 1, the request message includes user information (identification of user A), operation type (modify the network The capacity value is changed to the value a3).
  • the core network device obtains the subscription information of user A based on the identifier of user A, as shown in Table 2.
  • List of allowed network identities list of allowed actions Allowed network capacity quota network 1 Create, suspend, resume, modify network properties a1, a2 network 2 Suspend, resume, modify network attributes a1, a2, a3 network 3 create, delete a2
  • the core network device verifies the operation authority of the request message according to the subscription information of the user A. It can be seen that in the subscription information of user A, the terminal device can modify the network attribute of network 1, and can modify the network capacity value of network 1 to a1 or a2, and the terminal device does not have the ability to modify the network capacity value of network 1 to a3 permissions. In this case, the core network device fails to authenticate the operation authority of the operation type in the request message.
  • both the operation authentication method 1 and the operation authentication method 2 can be implemented, or only any one of them can be implemented, which is not specifically limited in this application. Moreover, when both the operation authentication method 1 and the operation authentication method 2 can be executed, the execution sequence of the operation authentication method 1 and the operation authentication method 2 is not specifically limited here, that is, the operation authentication method
  • the first operation authentication method may be executed before the operation authentication method two, or the operation authentication method one may be executed after the operation authentication method two, or the operation authentication method one and the operation authentication method two may be executed simultaneously.
  • the functional network element performing mode-operation authentication may have the same function as the functional network element performing mode-operation authentication
  • the network elements may also be network elements with different functions.
  • the core network device operates on the life cycle of the target network.
  • the core network device After the core network device performs operation authentication on the request message, if the operation authentication passes, the core network device operates the life cycle of the target network according to the operation type and/or operation parameters in the request message.
  • the core network device sends the first response message to the terminal device based on an operation result of the lifecycle operation of the target network.
  • the first response message includes the state of the target network or the identifier of the target network.
  • the first response message may be used to indicate that the operation result of the core network device based on the life cycle operation of the target network is successful.
  • the first response message may include the identification of the target network, the core network device's One or more of the state of the target network after the life cycle operation or the network attribute information of the target network.
  • the first response message may be used to indicate that the operation result of the core network device based on the life cycle operation of the target network is a failure.
  • the first response message may include the identifier of the target network, the core network device's The state of the target network after the lifecycle operation, the network attribute information of the target network, or the failure reason value (the failure reason value is used to indicate the reason for the failure of the lifecycle operation on the target network this time).
  • the network capacity value of network 1 is a1
  • the core network device receives the request message sent by terminal device 1, the request message includes user information (identification of user A), operation type (modify network 1 (i.e. target network) network properties), operating parameters (change the network capacity value to the value a2).
  • the operation authentication result of the core network device on the request message is passed, and the core network device changes the network capacity value of the network 1 from a1 to a2.
  • the first response message returned by the core network device to the terminal device 1 may include: the identifier of the network 1, the status of the network 1 (existence, availability or activation status), and the network attribute of the network 1 (the network capacity value is a2).
  • the network capacity value of network 1 is a3, and the core network device receives the request message sent by terminal device 1.
  • the request message includes user information (identification of user A), operation type (modify network 1 (i.e. target network ) of the network attributes), operating parameters (change the network capacity value to the value a2).
  • the operation authentication result of the core network device on the request message is passed.
  • the network capacity value of the network 1 is a3 (not equal to the operation value in the request message).
  • the capacity value in the parameter in this case, it can be considered that the life cycle operation of the core network device on the network 1 fails.
  • the first response message returned by the core network device to the terminal device 1 may include: the identifier of the network 1, the status of the network 1 (existence, availability or activation status), the network attribute of the network 1 (the network capacity value is a2), The cause of failure value is 1 (used to indicate that the network capacity value after modification is the same as the network capacity value before modification).
  • the core network device when the result of the operation authentication is not passed, the core network device does not perform operations on the life cycle of the target network.
  • the core network device may also send a second response message to the terminal device, where the second response message is used to indicate that the operation result of the life cycle operation on the target network is failure.
  • the second response message may also carry a failure reason value (used to indicate the reason for the current operation failure). For example, the mapping relationship between the failure reason value and the failure reason may be shown in Table 3.
  • failure reason value failure reason 01 User information does not exist 02 There is no operation permission corresponding to this operation type 03 Operation parameter is incorrect
  • the core network device involved in FIG. 7 may be one functional network element or multiple functional network elements in the core network, which is not specifically limited in this application.
  • the core network device mentioned in FIG. 7 may include three functional network elements: functional network element 1 , functional network element 2 and functional network element 3 .
  • the functional network element 1 is used to receive a request message from a terminal device (i.e., execute step S702)
  • the functional network element 2 is used to perform operation authentication based on the request message (i.e., execute step S703)
  • the functional network element Element 3 is used to operate on the life cycle of the target network when the result of the operation authentication is passed (that is, to execute step S704).
  • the 7 includes two functional network elements: functional network element 1 and functional network element 2, and the two functional network elements are used to execute steps S702-S704.
  • the functional network element 1 is used to perform the steps of S702 and S703, and the functional network element 2 is used to perform the steps of S704; or, the functional network element 1 is used to perform the steps of S702, and the functional network element 2 is used to perform the steps of S703 and S704 .
  • the core network device mentioned in FIG. 7 is a functional network element, and the functional network element is configured to perform steps S702-S704.
  • the functional network element used to receive the message can identify the functional network element used to send the message authentication.
  • the first functional network element is used for performing operation authentication based on the request message; the second functional network element is used for operating the life cycle of the target network.
  • the first functional network element sends an indication message (or second request message) to the second functional network element, and the indication message (or second request message) is used to request
  • the second functional network element operates on the life cycle of the target network.
  • the indication message (or the second request message) includes an operation type and/or an operation parameter.
  • the second functional network element receives the indication message (or the second request message), and verifies the identity of the first functional network element; if the verification is passed, the second functional network element operates the life cycle of the target network.
  • the terminal device can directly operate the target network through the core network device, and the core network device performs authentication operations on the identity and operation authority of the terminal device, which can improve the efficiency of the system while improving safety.
  • FIG. 8 is a schematic flow chart of another network resource management method provided by an embodiment of the present application.
  • the method execution subject of the network resource management method may be a core network or a chip in the core network, or the execution subject may be a terminal device or a chip in the terminal device.
  • FIG. 8 uses specific functional network elements and terminal devices in the core network as execution subjects for illustration. in:
  • the terminal device sends a request message to the AMF, and correspondingly, the AMF receives the request message from the terminal device.
  • the terminal device sends a request message for requesting to operate the life cycle of the target network to the AMF through the access network device (that is, the gNB in FIG. 8 ).
  • the request message may be a non-access stratum (non-access stratum, NAS) message.
  • the request message may be a separate NAS message (that is, the function of the NAS message is to operate the life cycle of the target network); the request message may be carried in an information element of a NAS message with other functions, That is, the NAS message includes other functions besides the function of requesting an operation on the life cycle of the target network.
  • the AMF performs operation authentication based on the request message.
  • the AMF operates on the life cycle of the target network.
  • the AMF network element creates the target network, which means that the AMF network element interacts with the MANO network element or the container management network element, applies for available running resources, and instantiates the running entity.
  • This running entity may be a newly instantiated virtual machine, a newly instantiated container, or a new process, thread, or other runtime execution entity running on an existing virtual machine or container; further, the AMF network element according to A request message from an end device creates a target network.
  • the AMF deletes the target network, which means that the AMF network element releases (or deletes) the running resources corresponding to the target network, and deletes the instantiation of the running entity of the target network.
  • the AMF network element suspends the target network, that is, sets the state of the target network to a suspended state (or called a standby state, a state to be activated, a deactivated state, etc.).
  • the AMF network element suspends the target network, which means that the AMF network element updates the information of the target network maintained by itself.
  • the update content includes: recording the working status of the user context to prohibit the user from subsequent signaling, ending and reporting the user's statistical information and bill data, or detach one or more of users immediately (or triggered by a timer) through signaling.
  • the recovery of the target network by the AMF network element is to change the state of the target network from the suspended state to the active state.
  • the AMF network element restores the target network, which means that the AMF network element updates the information of the target network maintained by itself.
  • the update content includes: recording the working status of the user context to restore the user's subsequent signaling, and restoring the user's statistical information and bills One or more of data or allowing subsequent signaling by the user.
  • the AMF network element modifies the network attributes of the target network, which can be understood as the AMF network element modifies the capacity of the target network (that is, modifies capacity-related parameters), modifies the capability of the target network (modifies network capacity-related parameters), modifies the configuration policy of the target network, or modifies One or more of the target network's service user list.
  • the modification of the network attributes of the target network by the AMF network element means that the AMF network element updates the information of the target network maintained by itself.
  • the update content includes: 1. Modify the network capabilities of the target network, such as opening or closing the corresponding A device capability or a service (service), wherein the service refers to a service provided by each NF defined by 3GPP), and triggers a registration update to the NRF.
  • the user information includes user permanent identification (such as IMSI/SUPI/MSISDN), user group identification, and user temporary identification ( One or more of such as GUTI), equipment identification (such as PEI/IME).
  • AMF sends an update request about the target network to the access network device (ie gNB), and correspondingly, the access network device (ie gNB) receives the update request about the target network from the AMF.
  • the access network device ie gNB
  • the AMF sends an update request on the target network to the access network device according to the operation type of the operation on the life cycle of the target network in the request message.
  • the update request about the target network carries the operation type information, and the update request about the target network is used to indicate the information of the target network maintained by the access network device (including the wireless link side information of the target network, such as wireless Scheduling priority, air interface priority, etc.) are updated (or modified).
  • the access network device After receiving the update request about the target network, the access network device has different operations according to different operation types, as follows:
  • the update request is used to request the access network device to establish a communication connection (or called a link connection, channel, etc.) with the AMF.
  • a communication connection or called a link connection, channel, etc.
  • the link refers to the communication connection (or called link connection, channel, etc.) between the AMF and the gNB, and the communication connection (or called link connection, channel, etc.) is associated with the target network.
  • the update request is used to request the access network device to delete the communication connection (or called link connection, channel, etc.) with the AMF.
  • the update request is used to request the access network device to interrupt the communication connection with the AMF (or called for link connections, channels, etc.).
  • the update request is used to request the access network device to restore (or activate) the communication with the AMF communication connection (or link connection, channel, etc.).
  • the update request is used to request (or instruct) the gNB to modify (or update) the information of the target network maintained by the gNB .
  • the gNB modifies information corresponding to the target network (including one or more of link information, an identifier of the target network, or a network attribute of the target network) based on the update request about the target network.
  • the gNB Based on the request for establishing (or deleting) a link connection, the gNB establishes (or deletes) a communication connection (or channel) with the first function about the target network, that is, the communication connection (or channel) is associated with the target network .
  • the gNB When the AMF creates a target network, the gNB establishes a communication connection (or called a link connection, channel, etc.) with the AMF.
  • a communication connection or called a link connection, channel, etc.
  • the gNB deletes the communication connection (or called link connection, channel, etc.) with the AMF.
  • the gNB interrupts the communication connection (or called link connection, channel, etc.) with the AMF.
  • the gNB restores (or activates) the communication connection (or called link connection, channel, etc.) with the AMF.
  • the gNB modifies (or updates) the information of the target network maintained by the gNB.
  • the gNB can establish, delete, interrupt or restore the link based on the next generation application protocol (next generation application protocol, NGAP) or SCTP.
  • next generation application protocol next generation application protocol, NGAP
  • SCTP next generation application protocol
  • the specific operations of S804 and S805 will be performed.
  • the operation type in the request message is to modify the network attribute of the target network, if the network attribute of the target network to be modified by the request will affect the wireless link side information of the target network (wherein the wireless link side information includes the wireless scheduling priority or air interface priority, etc.), then the specific operations of S804 and S805 can be performed; if the network attribute of the target network requested to be modified will not affect the wireless link side information of the target network, then the specific operations of S804 and S805 may not be performed .
  • the AMF sends the first operation control request to the SMF, and correspondingly, the SMF receives the first operation control request from the AMF.
  • the AMF sends the first operation control request to the SMF according to the operation type of the operation on the life cycle of the target network in the request message.
  • the first operation control request carries operation type information, and the first operation control request is used to instruct (or be interpreted as requesting) the SMF to operate on the life cycle of the target network.
  • the first operation control request is an N11 interface message.
  • the first operation control request may be a separate N11 interface message (that is, the function of the N11 interface message is to operate the life cycle of the target network); the first operation control request may be carried in other functions In the information element of the N11 interface message, that is, the N11 interface message includes other functions besides the function of requesting an operation on the life cycle of the target network.
  • the SMF operates on the life cycle of the target network.
  • the SMF sends the second operation control request to the UPF, and correspondingly, the UPF receives the second operation control request from the SMF.
  • the SMF sends the second operation control request to the UPF according to the operation type of the operation on the life cycle of the target network in the first operation control request.
  • the second operation control request carries information of an operation type, and the second operation control request is used to instruct (or understand as a request) that the UPF operates on the life cycle of the target network.
  • the second operation control request is an N4 interface message.
  • the second operation control request may be a separate N4 interface message (that is, the function of the N4 interface message is to operate the life cycle of the target network); the second operation control request may be carried in other functions
  • the information element of the N4 interface message that is, the N4 interface message includes other functions besides the function of requesting an operation on the life cycle of the target network.
  • the UPF operates on the life cycle of the target network.
  • the UPF after the UPF operates on the life cycle of the target network, the UPF sends a feedback message corresponding to the second operation control request to the SMF, and the feedback message corresponding to the second operation control request is an N4 interface message. If the UPF fails to operate the life cycle of the target network, the feedback message corresponding to the second operation control request may carry a failure cause value, and the failure cause value is used to indicate the reason why the UPF fails to operate the life cycle of the target network.
  • the SMF sends a feedback message corresponding to the first operation control request to the AMF based on the operation result of the UPF operating on the life cycle of the target network and the operation result of the SMF operating on the life cycle of the target network.
  • the feedback message corresponding to the first operation control request is an N11 interface message.
  • the feedback message corresponding to the first operation control request may carry a failure reason value
  • the The failure cause value is used to indicate the reason why the UPF fails to operate on the life cycle of the target network
  • the failure cause value is used to indicate the reason why the SMF fails to operate on the life cycle of the target network.
  • the operation type in the request message is one or more of creating a target network, deleting a target network, or modifying an operating state of a target network
  • the specific operations of S806-S809 will be performed.
  • the operation type in the request message is to modify the network attribute of the target network
  • the network attribute of the target network modified by the request will affect the session (such as PDU session) or user plane related information of the target network
  • execute S806-S809 specific operations if the network attribute of the target network to be modified by the request will not affect the session or user plane related information of the target network, the specific operations of S806-S809 may not be performed.
  • the AMF sends a third operation control request to the PCF, and correspondingly, the PCF receives the third operation control request from the AMF.
  • the AMF sends the third operation control request to the PCF according to the operation type of the operation on the life cycle of the target network in the request message.
  • the third operation control request carries operation type information, and the third operation control request is used to instruct (or be interpreted as requesting) the PCF to operate on the life cycle of the target network.
  • the third operation control request is an N15 interface message.
  • the third operation control request can be a separate N15 interface message (that is, the function of the N15 interface message is to operate the life cycle of the target network); the third operation control request can be carried in other functions In the information element of the N15 interface message, that is, the N15 interface message includes other functions besides the function of requesting an operation on the life cycle of the target network.
  • the PCF operates on the life cycle of the target network.
  • the PCF after the PCF operates on the lifecycle of the target network, the PCF sends a feedback message corresponding to the third operation control request to the AMF, where the feedback message corresponding to the third operation control request is an N15 interface message. If the PCF fails to operate the life cycle of the target network, the feedback message corresponding to the third operation control request may carry a failure cause value, which is used to indicate the reason why the PCF failed to operate the life cycle of the target network.
  • the specific operations of S810 and S811 will be performed.
  • the operation type in the request message is to modify the network attribute of the target network, if the network attribute of the target network modified by the request will affect the configuration policy of the target network, the specific operations of S810 and S811 are performed; When the network attributes of the target network do not affect the configuration policy of the target network, the specific operations of S810 and S811 may be performed.
  • the AMF records the state of the target network, and feeds back the operation result of the life cycle of the target network to the terminal device through the gNB.
  • the state of the target network includes the presence of the target network (including the activated state and the suspended state), and the non-existence of the target network.
  • the AMF can also record the network attributes of the target network.
  • FIG. 9 shows a schematic structural diagram of a communication device according to an embodiment of the present application.
  • the communication device shown in FIG. 9 can be used to realize some or all functions of the terminal equipment in the embodiment corresponding to the above network resource management method, or the communication device shown in FIG. 9 can be used to realize the core in the embodiment corresponding to the above network resource management method Some or all functions of the network equipment.
  • the communication device shown in FIG. 9 may be used to implement some or all functions of the terminal device in the method embodiment described in FIG. 3 or FIG. 8 above.
  • the device may be a terminal device, or a device in the terminal device, or a device that can be matched with the terminal device.
  • the communication device may also be a system on a chip.
  • the communication device shown in FIG. 9 may include a transceiver unit 901 and a processing unit 902, wherein:
  • the processing unit 902 is configured to determine a request message, the request message is used to operate the life cycle of the target network; the request message is control plane signaling or user plane signaling between the terminal device and the core network device; the transceiver unit 901 , used to send a request message to the core network device.
  • the request message includes an operation type
  • the operation type includes one of creating a target network, deleting a target network, modifying an operating state of the target network, or modifying network attributes of the target network.
  • modifying the running state of the target network includes suspending the target network or restoring the target network.
  • modifying the network attribute of the target network includes one or more of modifying capacity of the target network, modifying capability of the target network, modifying a configuration policy of the target network, or modifying a service user list of the target network.
  • the request message further includes one or more of user information of the terminal device, operation parameters corresponding to the operation type, or target network information.
  • the user information includes one or more of a permanent user ID, a user group ID, or a temporary user ID.
  • the information of the target network includes one or more of a target network identifier, a capacity value, a capability list, a service user list, or a configuration policy list.
  • the transceiving unit 901 is further configured to receive a response message sent by the core network device, where the response message is used to indicate the result of the lifecycle operation on the target network.
  • the target network is a user service function entity or other network functions that provide services to users.
  • the communication device shown in FIG. 9 may be used to realize some or all functions of the core network device in the method embodiment described in FIG. 3 or FIG. 8 above.
  • the device may be a core network device, or a device in the core network device, or a device that can be matched with the core network device.
  • the communication device may also be a system on a chip.
  • the communication device shown in FIG. 9 may include a transceiver unit 901 and a processing unit 902, wherein:
  • the transceiver unit 901 is configured to receive a request message from the terminal device, the request message is used to operate the life cycle of the target network; the request message is control plane signaling or user plane signaling between the terminal device and the core network;
  • the processing unit 902 is configured to operate the life cycle of the target network managed by the core network device based on the request message.
  • the request message includes an operation type
  • the operation type includes one of creating a target network, deleting a target network, modifying an operating state of the target network, or modifying network attributes of the target network.
  • modifying the running state of the target network includes suspending the target network or restoring the target network.
  • modifying the network attribute of the target network includes one or more of modifying capacity of the target network, modifying capability of the target network, modifying a configuration policy of the target network, or modifying a service user list of the target network.
  • the processing unit 902 is also configured to perform operation authentication based on the request message; when the result of the operation authentication is passed, the processing unit 902 operates on the life cycle of the target network; or, when the operation authentication When the result is not passed, the processing unit 902 does not operate on the life cycle of the target network.
  • the processing unit 902 performs operation authentication based on the request message, including one or more of the following: according to the operation type, authenticating the status of the target network; or, authenticating the operation authority of the operation type right.
  • the processing unit 902 if the operation type matches the state of the target network, the processing unit 902 passes the state authentication of the target network; or, if the operation type does not match the state of the target network, the processing unit 902 The network status authentication fails.
  • the operation type does not match the state of the target network, including: the operation type is to create a target network, and the state of the target network is an existing state; or, the operation type is to delete a target network, and the state of the target network is not Existing state; or, the operation type is modifying the network attribute of the target network, and the state of the target network is non-existing state; or, the operation type is modifying the running state of the target network, and the state of the target network is non-existing state.
  • the existence state includes a suspended state and an active state
  • the operation type is to modify the running state of the target network, and the operation type does not match the state of the target network, and further includes: the operation type is to suspend the target network, and the target network The state of the network is Suspended; or, the operation type is Resume Target Network, and the state of the target network is Active.
  • the request message further includes one or more of user information of the terminal device, operation parameters corresponding to the operation type, or target network information.
  • the user information includes one or more of a permanent user ID, a user group ID, or a temporary user ID.
  • the information of the target network includes one or more of a target network identifier, a capacity value, a capability list, a service user list, or a configuration policy list.
  • the processing unit 902 acquires user subscription information based on user information; and authenticates the operation authority of the operation type based on the user subscription information and/or a local configuration policy.
  • the user subscription information includes one or more of a list of allowed operation actions, a list of allowed network identifiers, a list of allowed network capacity quotas, a list of allowed service users, or a list of configuration policies.
  • the transceiver unit 901 when the result of the operation authentication is passed, based on the operation result of the lifecycle operation of the target network, the transceiver unit 901 sends a first response message to the terminal device; the first response message includes the target The state of the network and the target network identifier; or, when the result of the operation authentication is not passed, the transceiver unit 901 sends a second response message to the terminal device, and the second response message is used to indicate the life cycle operation of the target network.
  • the result of the operation is failure.
  • the target network is a user service function entity or other network functions that provide services to users.
  • transceiver unit 901 For a more detailed description of the transceiver unit 901 and the processing unit 902, reference may be made to the relevant description of the terminal device or the core network in the method embodiment above, and no further description is given here.
  • FIG. 10 is a schematic structural diagram of a communication device 1000 provided in the present application.
  • the communication device 1000 includes a processor 1010 and an interface circuit 1020 .
  • the processor 1010 and the interface circuit 1020 are coupled to each other.
  • the interface circuit 1020 may be a transceiver or an input-output interface.
  • the communication device 1000 may further include a memory 1030 for storing instructions executed by the processor 1010 or storing input data required by the processor 1010 to execute the instructions or storing data generated by the processor 1010 after executing the instructions.
  • the processor 1010 is used to execute the functions of the processing unit 902
  • the interface circuit 1020 is used to execute the functions of the transceiver unit 901 .
  • the terminal equipment chip implements the functions of the terminal equipment in the above method embodiments, and the terminal equipment chip receives information from other network elements; or, the terminal equipment chip sends information to other network elements information.
  • the core network chip When the above communication device is a chip applied to a core network, the core network chip implements the functions of the core network in the above method embodiments.
  • the core network chip receives information from other network elements; or, the core network chip sends information to other network elements.
  • processor in the embodiments of the present application may be a central processing unit (central processing unit, CPU), and may also be other general processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits (application specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.
  • CPU central processing unit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • a general-purpose processor can be a microprocessor, or any conventional processor.
  • the method steps in the embodiments of the present application may be implemented by means of hardware, or may be implemented by means of a processor executing software instructions.
  • the software instructions can be composed of corresponding software modules, and the software modules can be stored in random access memory (random access memory, RAM), flash memory, read-only memory (Read-Only Memory, ROM), programmable read-only memory (programmable ROM) , PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically erasable programmable read-only memory (electrically EPROM, EEPROM), register, hard disk, mobile hard disk, CD-ROM or known in the art any other form of storage medium.
  • An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium.
  • the storage medium may also be a component of the processor.
  • the processor and storage medium can be located in the ASIC.
  • the ASIC may be located in the access network device or the terminal device.
  • the processor and the storage medium may also exist in the terminal device or the core network as discrete components.
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product comprises one or more computer programs or instructions. When the computer program or instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are executed in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer program or instructions may be stored in or transmitted via a computer-readable storage medium.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server integrating one or more available media.
  • Described usable medium can be magnetic medium, for example, floppy disk, hard disk, magnetic tape; It can also be optical medium, for example, digital versatile disc (digital versatile disc, DVD); It can also be semiconductor medium, for example, solid state hard drive (solid state drive, SSD).
  • the embodiment of the present application also provides a computer-readable storage medium, the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed, the terminal device or the core network in the above-mentioned method embodiments execute the method be realized.
  • An embodiment of the present application further provides a computer program product, where the computer program product includes a computer program.
  • the computer program When the computer program is executed, the method performed by the terminal device or the core network in the above method embodiments is implemented.
  • An embodiment of the present application also provides a communication system, where the communication system includes a terminal device or a core network.
  • the terminal device is configured to execute the method performed by the terminal device in the foregoing method embodiments.
  • the core network is used to execute the methods executed by the core network in the foregoing method embodiments.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请提供一种网络资源管理方法及通信装置，该网络资源管理方法包括:终端设备生成请求消息，该请求消息用于对目标网络的生命周期进行操作（S301），该请求消息为终端设备和核心网设备之间的控制面信令或用户面信令；终端设备向核心网设备发送该请求消息(S302)；核心网设备基于该请求消息，对核心网设备管理的目标网络的生命周期进行操作(S303)。通过这样的网络资源管理方法，用户可以直接对为用户提供网络服务的目标网络进行修改，相比于用户通过运营商为媒介对目标网络进行修改的方式，缩短了对目标网络修改的生效周期，提升效率。

Description

一种网络资源管理方法及通信装置
本申请要求于2021年12月31日提交于中国国家知识产权局、申请号为202111682951.8、申请名称为“一种网络资源管理方法及通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种网络资源管理方法及通信装置。
背景技术
在用户使用移动网络的过程中，移动网络可以向用户提供网络服务(例如语音等数据传输业务)，用户也可以对移动网络进行干涉，以使该移动网络满足当前用户的业务需求。例如用户A在使用移动网络的过程中，对移动网络的计费套餐修改，则移动网络会根据修改后的计费套餐修改用户A对应的移动网络，如修改该移动网络的传输速率或容量等参数。
通常用户对移动网络进行干涉(或理解为修改)的流程可简单描述为：用户向移动网络的运营商交互用户诉求；在运营商理解用户诉求之后，运营商通过业务支撑系统(business support system，BSS)和运营支撑系统(operation support system，OSS)对该移动网络进行配置修改，以使修改后的移动网络满足用户诉求。
可见，用户通过运营商对移动网络进行干涉(或理解为修改)的生效周期长、效率较低。
发明内容
本申请实施例提供一种网络资源管理方法及通信装置，以提升网络资源管理的效率。
第一方面，本申请实施例提供一种网络资源管理方法，在该方法中，终端设备确定请求消息，该请求消息用于对目标网络的生命周期进行操作，该请求消息为终端设备和核心网之间的控制面信令或用户面信令；终端设备向核心网发送该请求消息；核心网基于该请求消息对核心网管理的目标网络的生命周期进行操作。
基于第一方面所描述的方法，用户可以直接根据与核心网之间的控制面信令或用户面信令对提供用户服务的目标网络进行操作，相比于用户通过运营商网络对目标网络进行操作的方式，可以缩短操作的生效周期，从而提升对目标网络的操作效率。
在一个可能的实施方式中，目标网络为用户服务功能实体或其他为用户提供服务的网络功能。通过实施该可能的实施方式，终端设备可以根据与核心网之间的控制面信令或用户面信令，对用户服务功能实体或其他为用户提供服务的网络功能进行直接操作。
在一个可能的实施方式中，目标网络包括为终端设备提供网络服务的网络功能、一个或一组虚机、容器、进程或其他可运行的资源集合。
在一个可能的实施方式中，该请求消息包括操作类型的信息，该操作类型包括创建目标网络、删除目标网络、修改目标网络的运行状态或修改目标网络的网络属性中的一种。通过实施该可能的实施方式，终端设备可以根据与核心网之间的控制面信令或用户面信令，对目标网络进行创建、删除、修改运行状态和修改网络属性的操作。
在一个可能的实施方式中，该修改目标网络的运行状态包括挂起目标网络或恢复目标网络。通过实施该可能的实现方式，终端设备可以根据用户需求更新目标网络的运行状态，例如当终端设备暂时不需要目标网络提供网络服务，则终端设备可以选择挂起目标网络以节省 系统功耗；当终端设备需要目标网络提供网络服务时，再选择恢复目标网络以满足用户需求。
在一个可能的实施方式中，该修改目标网络的网络属性包括修改目标网络的容量、修改目标网络的能力、修改目标网络的配置策略或修改目标网络的服务用户列表中的一种或多种。通过实施该可能的实现方式，终端设备可以根据用户需求修改目标网络的网络属性，以使目标网络更加贴合用户需求。
在一个可能的实施方式中，核心网基于该请求消息进行操作鉴权；当操作鉴权的结果为通过时，核心网对目标网络的生命周期进行操作；或者，当操作鉴权的结果为不通过时，核心网对目标网络的生命周期不进行操作。通过实施该可能的实施方式，仅当操作鉴权结果为通过时，核心网才根据终端设备的请求对目标网络的生命周期进行操作，可以提升系统的安全性。
在一个可能的实施方式中，核心网根据操作类型，对目标网络的状态进行鉴权；或，核心网对操作类型的操作权限进行鉴权。通过实施该可能的实施方式，避免核心网根据终端设备发出错误请求消息进行无效操作的情况，以节省系统功耗。
在一个可能的实施方式中，若操作类型与目标网络的状态匹配，则核心网对目标网络的状态鉴权通过。
在一个可能的实施方式中，若操作类型与目标网络的状态不匹配，则核心网对目标网络的状态鉴权不通过。
通过实施上述可能的实施方式，以操作类型与目标网络的状态匹配为筛选条件，避免终端设备发出错误请求消息之后，核心网依旧得根据该错误请求消息对目标网络的生命周期进行无效操作的情况，节省功耗。
在一个可能的实施方式中，目标网络的状态包括存在状态和不存在状态，操作类型与目标网络的状态不匹配，包括：操作类型为创建目标网络，该目标网络的状态为存在状态；或者，操作类型为删除目标网络，该目标网络的状态为不存在状态；或者，操作类型为修改目标网络的网络属性，该目标网络的状态为不存在状态；或者，操作类型为修改目标网络的运行状态，该目标网络的状态为不存在状态。
在一个可能的实施方式中，目标网络的状态包括存在状态和不存在状态，操作类型与目标网络的状态匹配，包括：操作类型为创建目标网络，该目标网络的状态为不存在状态；或者，操作类型为删除目标网络，该目标网络的状态为存在状态；或者，操作类型为修改目标网络的网络属性，该目标网络的状态为存在状态；或者，操作类型为修改目标网络的运行状态，该目标网络的状态为存在状态。
上述可能的实施方式，提供一些操作类型与目标网络的状态不匹配(或匹配)的具体示例。
在一个可能的实施方式中，存在状态包括挂起状态或激活状态，该操作类型为修改目标网络的运行状态的情况下，操作类型与目标网络的状态不匹配，还包括：操作类型为挂起目标网络，该目标网络的状态为挂起状态；或者，该操作类型为恢复目标网络，该目标网络的状态为激活状态。
在一个可能的实施方式中，存在状态包括挂起状态或激活状态，该操作类型为修改目标网络的运行状态的情况下，操作类型与目标网络的状态匹配，还包括：操作类型为挂起目标网络，该目标网络的状态为激活状态；或者，该操作类型为恢复目标网络，该目标网络的状态为挂起状态。
通过上述可能的实施方式，提供一些操作类型与目标网络的状态不匹配(或匹配)的具 体示例。
在一个可能的实施方式中，核心网包括第一功能网元和第二功能网元，第一功能网元与第二功能网元之间具有通信连接；第一功能网元用于基于请求消息进行操作鉴权；第二功能网元用于在操作鉴权的结果为通过时，对目标网络的生命周期进行操作。通过实施该可能的实施方式，提供了一种对目标网络进行操作的核心网设备的具体架构。
在一个可能的实施方式中，第一功能网元基于请求消息进行操作鉴权之后，在操作鉴权的结果为通过的情况下，第一功能网元向第二功能网元发送指示消息(或第二请求消息)，该指示消息(或第二请求消息)用于请求第二功能网元对目标网络的生命周期进行操作。通过实施该可能的实现方式，第二功能网元只有接收到第一功能网元的指示消息(或第二请求消息)之后，才会对目标网络的生命周期进行操作，提升了目标网络的稳定性。
在一个可能的实施方式中，该指示消息(或第二请求消息)包括操作类型或操作类型对应的操作参数。通过实施该可能的实施方式，第二功能网元可以该指示消息(或第二请求消息)对目标网络的生命周期进行具体操作，以使目标网络更加贴合用户需求。
在一个可能的实施方式中，第二功能网元对第一功能网元的身份进行鉴定；在对第一功能网元的身份鉴定通过之后，第二功能网元对目标网络的生命周期进行操作。通过实施该可能的实施方式，第二功能网元在对目标网络的生命周期进行操作之前，第二网络对第一功能网元的身份进行鉴定，可以提升目标网络的安全性。
在一个可能的实施方式中，该请求消息还包括终端设备的用户信息、操作类型对应的操作参数或目标网络的信息中的一种或多种。通过实施该可能的实施方式，核心网可以根据用户信息、操作类型对应的操作参数或目标网络的信息对目标网络进行操作。
在一个可能的实施方式中，用户信息包括用户永久标识、用户组标识或用户临时标识中的一种或多种。
在一个可能的实施方式中，该目标网络的信息包括目标网络标识、容量值、能力列表、服务用户列表或配置策略列表中的一种或多种。
在一个可能的实施方式中，该请求消息还包括终端设备的用户信息，核心网基于用户信息，获取用户签约信息；核心网基于该用户签约信息和/或本地配置策略，对操作类型的操作权限进行鉴权。通过实施该可能的实施方式，避免终端设备无该操作类型对应的操作权限时，核心网依旧根据该请求消息对目标网络的生命周期进行无效操作的情况，节省功耗。
在一个可能的实施方式中，该用户签约信息包括允许的操作动作列表、允许的网络标识列表、允许的网络容量配额、允许的服务用户列表或配置策略列表中的一种或多种。通过实施该可能的实施方式，通过用户签约信息对终端设备的操作权限进行限定，以便基于用户签约信息对终端设备的操作权限进行鉴权。
在一个可能的实施方式中，在操作鉴权的结果为通过的情况下，核心网基于对目标网络的生命周期操作的操作结果向终端设备发送第一应答消息；该第一应答消息包括目标网络的状态或目标网络标识。
在一个可能的实施方式中，当操作鉴权的结果为不通过的情况下，核心网向所述终端设备发送第二应答消息，该第二应答消息用于指示对目标网络的生命周期操作的操作结果为失败。通过实施该可能的方式，核心网会向终端设备反馈对目标网络的生命周期操作的操作结果，对用户而言核心网对目标网络操作的更加公开透明，提升用户体验。
第二方面，本申请实施例提供一种网络资源管理方法，在该方法中，终端设备确定请求消息，该请求消息用于对目标网络的生命周期进行操作；该请求消息为终端设备和核心网设 备之间的控制面信令或用户面信令；终端设备向核心网设备发送请求消息。
基于第二方面所提供的网络资源管理方法，其有益效果可参见前述第一方面所提供的网络资源管理方法的有益效果，重复之处在此不再进行赘述。
在一个可能的实施方式中，请求消息包括操作类型的信息，该操作类型包括创建目标网络、删除目标网络、修改目标网络的运行状态或修改目标网络的网络属性中的一种。
在一个可能的实施方式中，该修改目标网络的运行状态包括挂起目标网络或恢复目标网络。
在一个可能的实施方式中，修改目标网络的网络属性包括修改目标网络的容量、修改目标网络的能力、修改目标网络的配置策略或修改目标网络的服务用户列表中的一种或多种。
在一个可能的实施方式中，请求消息还包括终端设备的用户信息、操作类型对应的操作参数或目标网络的信息中的一种或多种。
在一个可能的实施方式中，用户信息包括用户永久标识、用户组标识或用户临时标识中的一种或多种。
在一个可能的实施方式中，目标网络的信息包括目标网络标识、容量值、能力列表、服务用户列表或配置策略列表中的一种或多种。
在一个可能的实施方式中，终端设备接收核心网设备发送的应答消息，该应答消息用于指示对目标网络的生命周期操作的结果。
在一个可能的实施方式中，目标网络为用户服务功能实体或其他为用户提供服务的网络功能。
在一个可能的实施方式中，目标网络包括为终端设备提供网络服务的网络功能、一个或一组虚机、容器、进程或其他可运行的资源集合。
第三方面，本申请实施例提供一种网络资源管理方法，在该方法中，核心网设备接收来自终端设备的请求消息，该请求消息用于对目标网络的生命周期进行操作；该请求消息为终端设备和核心网设备之间的控制面信令或用户面信令；核心网设备基于该请求消息，对核心网设备管理的目标网络的生命周期进行操作。
基于第三方面所提供的网络资源管理方法，其有益效果可参见前述第一方面所提供的网络资源管理方法的有益效果，重复之处在此不再进行赘述。
在一个可能的实施方式中，请求消息包括操作类型的信息，该操作类型包括创建目标网络、删除目标网络、修改目标网络的运行状态或修改目标网络的网络属性中的一种。
在一个可能的实施方式中，该修改目标网络的运行状态包括挂起目标网络或恢复目标网络。
在一个可能的实施方式中，修改目标网络的网络属性包括修改目标网络的容量、修改目标网络的能力、修改目标网络的配置策略或修改目标网络的服务用户列表中的一种或多种。
在一个可能的实施方式中，核心网设备基于请求消息进行操作鉴权；当操作鉴权的结果为通过时，核心网设备对目标网络的生命周期进行操作；当操作鉴权的结果为不通过时，核心网设备对目标网络的生命周期不进行操作。
在一个可能的实施方式中，核心网设备基于请求消息进行操作鉴权，包括以下一种或多种：根据操作类型，对目标网络的状态进行鉴权；或，对操作类型的操作权限进行鉴权。
在一个可能的实施方式中，若操作类型与目标网络的状态匹配，则核心网设备对目标网络的状态鉴权通过；若操作类型与目标网络的状态不匹配，则核心网设备对目标网络的状态鉴权不通过。
在一个可能的实施方式中，目标网络的状态包括存在状态或不存在状态，操作类型与目标网络的状态匹配，包括：操作类型为创建目标网络，目标网络的状态为不存在状态；或者，操作类型为删除目标网络，目标网络的状态为存在状态；或者，操作类型为修改目标网络的网络属性，目标网络的状态为存在状态；或者，操作类型为修改目标网络的运行状态，目标网络的状态为存在状态。
在一个可能的实施方式中，存在状态包括挂起状态或激活状态，该操作类型为修改目标网络的运行状态的情况下，操作类型与目标网络的状态匹配，还包括：操作类型为挂起目标网络，目标网络的状态为激活状态；或者，操作类型为恢复目标网络，目标网络的状态为挂起状态。
在一个可能的实施方式中，请求消息还包括终端设备的用户信息、操作类型对应的操作参数或目标网络的信息中的一种或多种。
在一个可能的实施方式中，用户信息包括用户永久标识、用户组标识或用户临时标识中的一种或多种。
在一个可能的实施方式中，目标网络的信息包括目标网络标识、容量值、能力列表、服务用户列表或配置策略列表中的一种或多种。
在一个可能的实施方式中，核心网设备基于用户信息，获取用户签约信息；并基于用户签约信息和/或本地配置策略，对操作类型的操作权限进行鉴权。
在一个可能的实施方式中，用户签约信息包括允许的操作动作列表、允许的网络标识列表、允许的网络容量配额、允许的服务用户列表或配置策略列表中的一种或多种。
在一个可能的实施方式中，在操作鉴权的结果为通过的情况下，基于对目标网络的生命周期操作的操作结果，核心网设备向终端设备发送第一应答消息；第一应答消息包括目标网络的状态和目标网络标识；当操作鉴权的结果为不通过的情况下，核心网设备向终端设备发送第二应答消息，第二应答消息用于指示对目标网络的生命周期操作的操作结果为失败。
在一个可能的实施方式中，目标网络为用户服务功能实体或其他为用户提供服务的网络功能。
第四方面，本申请提供一种通信装置，该装置可以为终端设备，也可以为支持终端设备实现上述方法的芯片、芯片系统、或处理器等，还可以为能实现全部或部分终端设备功能的逻辑模块、单元或软件。其中，该通信装置还可以为芯片系统。该通信装置包括：
处理单元，用于确定请求消息，该请求消息用于对目标网络的生命周期进行操作；该请求消息为终端设备和核心网设备之间的控制面信令或用户面信令；收发单元，用于向核心网设备发送请求消息。
基于第四方面所提供的网络资源管理方法，其有益效果可参见前述第一方面或第二方面所提供的网络资源管理方法的有益效果，重复之处在此不再进行赘述。
在一个可能的实施方式中，请求消息包括操作类型的信息，该操作类型包括创建目标网络、删除目标网络或修改目标网络的网络属性中的一种。
在一个可能的实施方式中，该操作类型还包括挂起目标网络或恢复目标网络。
在一个可能的实施方式中，修改目标网络的网络属性包括修改目标网络的容量、修改目标网络的能力、修改目标网络的配置策略或修改目标网络的服务用户列表中的一种或多种。
在一个可能的实施方式中，请求消息还包括终端设备的用户信息、操作类型对应的操作参数或目标网络的信息中的一种或多种。
在一个可能的实施方式中，用户信息包括用户永久标识、用户组标识或用户临时标识中 的一种或多种。
在一个可能的实施方式中，目标网络的信息包括目标网络标识、容量值、能力列表、服务用户列表或配置策略列表中的一种或多种。
在一个可能的实施方式中，收发单元还用于接收核心网设备发送的应答消息，该应答消息用于指示对目标网络的生命周期操作的结果。
在一个可能的实施方式中，目标网络为用户服务功能实体或其他为用户提供服务的网络功能。
第五方面，本申请提供另一种通信装置，该装置可以为核心网设备，也可以为支持核心网设备实现上述方法的芯片、芯片系统、或处理器等，还可以为能实现全部或部分核心网功能的逻辑模块、单元或软件。其中，该通信装置还可以为芯片系统。该通信装置包括：收发单元，用于接收来自终端设备的请求消息，该请求消息用于对目标网络的生命周期进行操作；该请求消息为终端设备和核心网设备之间的控制面信令或用户面信令；处理单元，用于基于该请求消息，对核心网设备管理的目标网络的生命周期进行操作。
在一个可能的实施方式中，请求消息包括操作类型的信息，该操作类型包括创建目标网络、删除目标网络或修改目标网络的网络属性中的一种。
在一个可能的实施方式中，该操作类型还包括挂起目标网络或恢复目标网络。
在一个可能的实施方式中，修改目标网络的网络属性包括修改目标网络的容量、修改目标网络的能力、修改目标网络的配置策略或修改目标网络的服务用户列表中的一种或多种。
在一个可能的实施方式中，处理单元还用于基于请求消息进行操作鉴权；当操作鉴权的结果为通过时，处理单元对目标网络的生命周期进行操作；当操作鉴权的结果为不通过时，处理单元对目标网络的生命周期不进行操作。
在一个可能的实施方式中，处理单元基于请求消息进行操作鉴权，包括以下一种或多种：根据操作类型，对目标网络的状态进行鉴权；或，对操作类型的操作权限进行鉴权。
在一个可能的实施方式中，若操作类型与目标网络的状态匹配，则处理单元对目标网络的状态鉴权通过；若操作类型与目标网络的状态不匹配，则处理单元对目标网络的状态鉴权不通过。
在一个可能的实施方式中，目标网络的状态包括存在状态或不存在状态，操作类型与目标网络的状态匹配，包括：操作类型为创建目标网络，目标网络的状态为不存在状态；或者，操作类型为删除目标网络，目标网络的状态为存在状态；或者，操作类型为修改目标网络的网络属性，目标网络的状态为存在状态。
在一个可能的实施方式中，操作类型与目标网络的状态不匹配，还包括：操作类型为挂起目标网络，目标网络的状态为不存在或挂起状态；或者，操作类型为恢复目标网络，目标网络的状态为不存在或激活状态。
在一个可能的实施方式中，请求消息还包括终端设备的用户信息、操作类型对应的操作参数或目标网络的信息中的一种或多种。
在一个可能的实施方式中，用户信息包括用户永久标识、用户组标识或用户临时标识中的一种或多种。
在一个可能的实施方式中，目标网络的信息包括目标网络标识、容量值、能力列表、服务用户列表或配置策略列表中的一种或多种。
在一个可能的实施方式中，处理单元基于用户信息，获取用户签约信息；并基于用户签约信息和/或本地配置策略，对操作类型的操作权限进行鉴权。
在一个可能的实施方式中，用户签约信息包括允许的操作动作列表、允许的网络标识列表、允许的网络容量配额、允许的服务用户列表或配置策略列表中的一种或多种。
在一个可能的实施方式中，在操作鉴权的结果为通过的情况下，基于对目标网络的生命周期操作的操作结果，收发单元向终端设备发送第一应答消息；第一应答消息包括目标网络的状态和目标网络标识；当操作鉴权的结果为不通过的情况下，收发单元向终端设备发送第二应答消息，第二应答消息用于指示对目标网络的生命周期操作的操作结果为失败。
在一个可能的实施方式中，目标网络为用户服务功能实体或其他为用户提供服务的网络功能。
第六方面，本申请提供一种通信装置，该通信装置可以为上述方法实施例中的终端设备，或者为设置在终端设备中的芯片。该通信装置包括通信接口以及处理器，可选的，还包括存储器。其中，该存储器用于存储计算机程序或指令，处理器与存储器、通信接口耦合，当处理器执行所述计算机程序或指令时，使通信装置执行上述方法实施例中由终端设备所执行的方法。
第七方面，本申请提供一种通信装置，该通信装置可以为上述方法实施例中的核心网设备，或者为设置在核心网设备中的芯片。该通信装置包括通信接口以及处理器，可选的，还包括存储器。其中，该存储器用于存储计算机程序或指令，处理器与存储器、通信接口耦合，当处理器执行所述计算机程序或指令时，使通信装置执行上述方法实施例中由核心网设备所执行的方法。
第八方面，本申请提供一种计算机可读存储介质，所述计算机可读存储介质用于存储计算机执行指令，当该计算机执行指令被执行时，使得如第一方面或第二方面所述的方法中终端设备执行的方法被实现；或者，使得如第一方面或第三方面所述的方法中核心网设备执行的方法被实现。
第九方面，本申请提供一种包括计算机程序的计算机程序产品，当该计算机程序被执行时，使得如第一方面或第二方面所述的方法中终端设备执行的方法被实现；或者，使得如第一方面或第三方面所述的方法中核心网设备执行的方法被实现。
第十方面，本申请提供一种通信系统，该通信系统包括上述第四方面和第五方面所述的通信装置；或者包括上述第六方面和第七方面所述的通信装置。
附图说明
图1a为本申请实施例提供的一种网络系统架构的示意图；
图1b为本申请实施例提供的一种核心网的结构示意图；
图1c为本申请实施例提供的另一种核心网架构的示意图；
图2为本申请实施例提供的一种以用户为中心的网络的结构示意图；
图3为本申请实施例提供的一种网络资源管理方法的交互示意图；
图4a为本申请实施例提供的一种创建目标网络的交互示意图；
图4b为本申请实施例提供的另一种创建目标网络的交互示意图；
图5a为本申请实施例提供的一种删除目标网络的交互示意图；
图5b为本申请实施例提供的另一种删除目标网络的交互示意图；
图6a为本申请实施例提供的一种修改目标网络的网络属性的交互示意图；
图6b为本申请实施例提供的另一种修改目标网络的网络属性的交互示意图；
图7为本申请实施例提供的另一种网络资源管理方法的交互示意图；
图8为本申请实施例提供的又一种网络资源管理方法的交互示意图；
图9为本申请实施例提供的一种通信装置的结构示意图；
图10为本申请实施例提供的另一种通信装置的结构示意图。
具体实施方式
下面结合附图对本申请具体实施例作进一步的详细描述。
本申请的说明书、权利要求书及附图中的术语“第一”和“第二”等是用于区别不同对象，而不是用于描述特定顺序。此外，术语“包括”和“具有”以及它们任何变形，意图在于覆盖不排他的包含。例如包含了一系列步骤或单元的过程、方法、系统、产品或设备没有限定于已列出的步骤或单元，而是可选地还包括没有列出的步骤或单元，或可选地还包括对于这些过程、方法、产品或设备固有的其它步骤或单元。
在本文中提及“实施例”意味着，结合实施例描述的特定特征、结构或特性可以包含在本申请的至少一个实施例中。在说明书中的各个位置出现该短语并不一定均是指相同的实施例，也不是与其它实施例互斥的独立的或备选的实施例。本领域技术人员显式地和隐式地理解的是，本文所描述的实施例可以与其它实施例相结合。
在本申请中，“至少一个(项)”是指一个或者多个，“多个”是指两个或两个以上，“至少两个(项)”是指两个或三个及三个以上，“和/或”，用于描述关联对象的关联关系，表示可以存在三种关系，例如，“A和/或B”可以表示：只存在A，只存在B以及同时存在A和B三种情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b或c中的至少一项(个)，可以表示：a，b，c，“a和b”，“a和c”，“b和c”，或“a和b和c”，其中a，b，c可以是单个，也可以是多个。
为了更好地理解本申请实施例，下面首先对本申请实施例涉及的系统架构进行介绍：
本申请实施例的技术方案可以应用于各种通信系统，例如：长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、新无线(new radio，NR)、第三代合作伙伴(the 3rd generation partner project，3GPP)基于服务的网络架构(service-based architecture，SBA)等第五代(5th generation，5G)通信系统或第六代(6th generation，6G)通信系统等5G之后演进的通信系统等。
请参见图1a，图1a是本申请实施例提供的一种网络系统架构的示意图。如图1a所示，终端设备可以接入到无线网络中以通过无线网络获取外网(例如数据网络(data network，DN))的服务，或者通过无线网络与其它设备通信，如可以与其它终端设备通信。该无线网络包括(无线)接入网((radio)access network，(R)AN)和核心网(core network，CN)，其中，(R)AN(后文描述为RAN)用于将终端设备接入到无线网络，CN用于对终端设备进行管理并提供与DN通信的网关。下面分别对图1a中系统架构所涉及的终端设备、RAN、CN和DN进行详细说明。
一、终端设备
终端设备包括向用户提供语音和/或数据连通性的设备，例如终端设备是一种具有无线收发功能的设备，可以部署在陆地上，包括室内或室外、手持、穿戴或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。终端设备可以是手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、 车载终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、可穿戴终端等等。本申请的实施例对应用场景不做限定。终端设备有时也可以称为终端、用户设备(user equipment，UE)、接入终端、车载终端、工业控制终端、UE单元、UE站、移动站、移动台、远方站、远程终端、移动设备、UE终端、无线通信设备、UE代理或UE装置等。终端也可以是固定的或者移动的。可以理解，本申请中的终端的全部或部分功能也可以通过在硬件上运行的软件功能来实现，或者通过平台(例如云平台)上实例化的虚拟化功能来实现。
二、RAN
RAN中可以包括一个或多个RAN设备(或者说接入网设备)。接入网设备与终端设备之间的接口可以为Uu接口(或称为空口)。当然，5G之后演进的通信中，这些接口的名称可以不变，或者也可以用其它名称代替，本申请对此不限定。
接入网设备即为将终端设备接入到无线网络的节点或设备，接入网设备例如包括但不限于：5G通信系统中的下一代节点B(next generation node B，gNB)、演进型节点B(evolved node B，eNB)、下一代演进型节点B(next generation eNB，ng-eNB)、无线回传设备、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、家庭基站((home evolved nodeB，HeNB)或(home node B，HNB))、基带单元(baseBand unit，BBU)、传输接收点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心、设备到设备(Device-to-Device，D2D)、车辆外联(vehicle-to-everything，V2X)、机器到机器(machine-to-machine，M2M)通信中承担基站功能的设备等，还可以包括云接入网(cloud radio access network，C-RAN)系统中的集中式单元(centralized unit，CU)和分布式单元(distributed unit，DU)、非陆地通信网络(non-terrestrial network，NTN)通信系统中的网络设备，即可以部署于高空平台或者卫星，等，本申请实施例对此不作具体限定。
三、CN
CN中可以包括一个或多个CN设备(即可以理解为网元设备或功能网元)。
请参见图1b，图1b为本申请提供的一种CN的结构示意图，图1b的CN为5G网络架构中CN的示意图。在图1b所示CN中包括多个CN设备：网络切片选择功能(network slice selection function，NSSF)、网络开放功能(network exposure function，NEF)、网络存储功能(network function repository function，NRF)、策略控制功能(policy control function，PCF)、统一数据管理(unified data management，UDM)、应用功能(application function，AF)、网络控制功能(networkcontrol function，NCF)、特定网络切片身份验证和鉴权功能(network slice specific authentication and authorization function，NSSAAF)、认证服务器功能(authentication server function，AUSF)、接入与移动性管理功能(access and mobility management function，AMF)、会话管理功能(session management function，SMF)、用户面功能(user plane function，UPF)、服务通信代理(service communication proxy，SCP)、网络切片准入控制(Network Slice Admission Control Function，NSACF)。其中：
AMF是由运营商网络提供的控制面功能，负责终端设备接入运营商网络的接入控制和移动性管理，例如包括移动状态管理，分配用户临时身份标识，认证和授权用户等功能。
SMF是由运营商网络提供的控制面功能，负责管理终端设备的协议数据单元(protocoldata unit，PDU)会话。PDU会话是一个用于传输PDU的通道，终端设备需要通过PDU会话与DN互相传送PDU。PDU会话由SMF负责建立、维护和删除等。SMF包括会话管理(如会 话建立、修改和释放，包含UPF和RAN之间的隧道维护)、UPF的选择和控制、业务和会话连续性(service and session continuity，SSC)模式选择、漫游等会话相关的功能。
PCF是由运营商提供的控制面功能，包含用户签约数据管理功能、策略控制功能、计费策略控制功能、服务质量(quality of service，QoS)控制等，主要用于向SMF提供PDU会话的策略。其中，该策略可以包括计费相关策略、QoS相关策略和授权相关策略等。
UPF是由运营商提供的网关，是运营商网络与DN通信的网关。UPF包括数据包路由和传输、包检测、服务质量(quality of service，QoS)处理、上行包检测、下行数据包存储等用户面相关的功能。
UDM主要用于管理用户的签约数据和鉴权数据，以及进行鉴权信用处理，用户标识处理，访问授权，注册/移动性管理，订阅管理和短消息管理等。在一些实施例中，UDM中还可以包括统一数据存储库(unified data repository，UDR)。或者，在另一些实施例中，5G系统的3GPPSBA还可以包含UDR。其中，UDR用于为PCF策略提供存储和检索，开放的结构化数据的存储和检索和应用功能请求的用户信息存储等。
上述CN设备也可以称为网元或者功能网元。在5G通信系统中，各功能网元可以是图1b中所示的各个功能网元的名称，在5G之后演进的通信系统(如6G通信系统)中，各功能网元可以仍是图1b中所示的各个功能网元的名称，或者也可以具有其它名称。例如，在5G通信系统中，策略控制网元可以是PCF，在5G之后演进的通信系统(如6G通信系统)中，策略控制功能可以仍是PCF，或者也可以具有其它名称，本申请并不限定。
图1b中Npcf、Nudm、Naf、Namf、Nsmf、N1、N2、N3、N4，以及N6为接口序列号。这些接口序列号的含义可参见相关标准协议中定义的含义，在此不做限制。
请参见图1c，图1c为本申请提供的另一种CN架构的示意图。在图1c中，CN包括用户网络接入功能、用户签约认证功能、网络控制功能、资源管理功能。其中，用户网络接入功能用于对终端设备进行接入控制和移动性管理；用户签约认证功能用于对用户的签约信息进行存储和管理；网络控制功能用于对用户网络资源进行管理，例如负责用户网络的生成、更改、消除等操作；资源管理功能用于对网络资源进行管理，例如分配资源生成用户网络所需的网络功能实例。其中，用户网络用于为一个用户或多个用户提供网络服务，可以理解为UE专属服务的核心网网元。例如，该用户网络可以由一个或多个网元组成，可以是该用户专属的网元，也可以与其他用户共享的网元。当用户网络由一个网元组成时，用户网络可以指代该网元，该网元也能指代该用户网络。具体地，该用户网络可以是为终端设备提供网络服务的网络功能、一个或一组虚机、容器、进程或其他可运行的资源集合。下面以用户网络是用户服务节点(user service node，USN)的情况进行示例性说明。
例如，用户网络可以是USN，该USN可以理解为是一种核心网控制功能的集成，是为UE专属服务的核心网网元，例如USN可以集成会话管理(session management，SM)和/或策略管理(project management，PM)的功能；或者，USN也可以理解为是UE在核心网的数字孪生功能，是UE在现实行为的数字模型，比如记录UE所使用的业务信息，人工智能(artificial intelligence，AI)处理等等功能；又或者，USN可以理解为类似于一种云服务器(云电脑)，UE可以在该云服务器对运营商所提供的资源进行编排，例如不同业务的QoS设定，带宽分配等等。需要说明的是，USN可以融合在图1b所示5G的网络架构中；也可以融合在图1c所示的CN架构中；一种可能的实现中，USN可以作为一个新增的逻辑网元，或者作为逻辑功能集成于图1b或图1c中已有的网络功能中。示例性的，USN可以集成于AMF和SMF中。USN还可以是以用户为中心的网络(user centric network，UCN)架构的形式存在，在这 种情况下，该UCN架构可以理解为是一种以用户为中心的网络，请参见图2所示的一种UCN网络架构，在图2所示的UCN网络架构中包括网络服务节点(networkservice node，NSN)和用户服务节点(user service node，USN)。其中，NSN主要功能包括对接入UE的认证和USN的创建和生命周期管理。
NCF，用于对UCN网络架构中的USN资源进行管理，例如负责USN的生成、更改、消除等操作。
应理解，本申请中所涉及的NSN、USN和NCF仅为示意性的名称，并不应视为对此的具体限定。即是说，NSN、USN和NCF在除本申请之外的其他技术方案中可以采用其他名称，或者为具用相同功能的其他通信设备，例如，NSN可以为接入控制功能，NCF可以为网络资源控制或管理功能，USN可以为终端数字孪生功能等。
需要声明的是，1、图1c所示的CN结构仅是为了便于对CN的理解，仅是以每个功能网元分离部署于CN为例。在一些可能的CN结构中，各个功能网元之间可以集成组合部署，例如图1c中的网络接入功能和用户签约认证功能被集成为同一个功能网元，或者图1c中的网络接入功能和网络控制功能被集成为同一个功能网元等等。本申请对此不进行具体限定。2、本申请后文所提及的核心网可以是指核心网中某一个功能网元，也可以是核心网中某几个功能网元的集成，还可以是核心网中所有功能网元的集成。该核心网可以是图1b所示的5G通信系统中的核心网，也可以是图1c中所示的核心网，还可以是其它可能的通信系统(比如LTE通信系统或者5G之后演进的通信系统中的核心网。3、上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。可选的，上述网元或者功能可以由一个设备实现，也可以由多个设备共同实现，还可以是一个设备内的一个功能模块，本申请实施例对此不作具体限定。
四、DN
DN也可以称为分组数据网络(packet data network，PDN)，是位于运营商网络之外的网络，运营商网络可以接入多个DN，DN中可部署有多种业务对应的应用服务器，为终端设备提供多种可能的服务。
通常用户对用户网络进行修改的流程可简单描述为：用户向移动网络的运营商交互用户诉求；在运营商理解用户诉求之后，运营商通过BSS和OSS对该用户网络进行配置修改，以使修改后的用户网络满足用户诉求。但用户通过这样的方法对用户网络进行修改，通常生效周期较长、效率较低。
本申请提供一种网络资源管理方法，在该方法中用户可以利用终端设备与核心网之间的控制面信令(或用户面信令)来承载对目标网络的操作请求消息，以实现对为用户提供网络服务的目标网络进行修改，相比于用户通过运营商为媒介对目标网络进行修改的方式，缩短了对目标网络修改的生效周期，提升效率。
下面结合附图对本申请提供的网络资源管理方法及通信装置进行进一步介绍：
请参见图3，图3是本申请实施例提供的一种网络资源管理方法的流程示意图。如图3所示，该网络资源管理方法的方法执行主体可以为核心网设备或核心网设备中的芯片，或者执行主体可以为终端设备或终端设备中的芯片。图3以核心网设备和终端设备为执行主体为例进行说明。其中：
S301、终端设备确定请求消息，该请求消息用于对目标网络的生命周期进行操作。
终端设备根据用户需求，确定(或理解为生成)用于请求对目标网络的生命周期进行操作的请求消息。其中对目标网络的生命周期进行操作包括：创建目标网络和删除目标网络。换言之终端设备可以确定用于创建目标网络的请求消息，或者，确定用于删除目标网络的请求消息。
在一个可能的实施方式中，目标网络可以具有多种状态，包括：存在状态和不存在状态。需要理解的是，目标网络的状态为存在状态即是指该目标网络存在，目标网络的状态为不存在状态即是指目标网络不存在。
在一个可能的实施方式中，目标网络的状态为存在状态包括：目标网络的运行状态为挂起状态(或称为待机状态、待激活状态、去激活状态等)或目标网络的运行状态为激活状态。在这种情况下，对目标网络的生命周期进行操作还可以包括修改目标网络的运行状态。其中，修改目标网络的运行状态包括挂起目标网络，例如将目标网络的运行状态由激活状态改为挂起状态；或者，恢复(或称为激活)目标网络，例如将目标网络的运行状态由挂起状态改为激活状态。在一个可能的实现中，修改目标网络的运行状态还可以包括当目标网络的运行状态为异常(或故障)状态时，将目标网络的运行状态修改为正常运行状态。
在一个可能的实施方式中，目标网络还包括多种网络属性，包括但不限于：容量(即容量相关参数)、能力(即网络能量相关参数)、配置策略或服务用户列表中的一种或多种。在这种情况下，对目标网络的生命周期进行操作还可以包括修改目标网络的网络属性。
需要声明的是，本申请所提及的目标网络是指用于为终端设备提供网络服务的网络功能(network function，NF)、一个或一组虚机、容器、进程或其他可运行的资源集合。其中，网络服务包括但不限于数据下载、数据访问和通话中的一种或多种。换言之，该目标网络可以为用户服务功能实体或其他为用户提供服务的网络功能。例如，该目标网络可以为USN网元或USN功能实体。
在一个可能的实施方式中，该请求消息包括操作类型的信息，该操作类型为创建目标网络、删除目标网络、挂起目标网络、恢复目标网络或修改目标网络的网络属性中的一种。
其中，创建目标网络即为从无到有的生成(或建立)为终端提供网络服务的目标网络。删除目标网络即为删除目标网络的连接关系(如目标网络与接入网设备之间的连接关系等)、删除目标网络占据的资源(如运行资源等)。挂起目标网络即为将目标网络的状态设为挂起状态(或称为待机状态、待激活状态、去激活状态等)。恢复目标网络即为将目标网络的状态从挂起状态变更为激活状态。修改目标网络的网络属性可以理解为修改目标网络的容量(即修改容量相关参数)、修改目标网络的能力(修改网络能力相关参数)、修改目标网络的配置策略或修改目标网络的服务用户列表中的一种或多种。
一种可能的实现中，操作类型的信息可以为索引值，该索引值与操作类型有映射关系。该映射关系可以是协议中规定的，预配置的，或者终端和核心网约定的。示例性，操作类型的信息的一种具体实现方式可以为：该请求消息中包括字段1，该字段1用于指示操作类型。例如该字段1的值与操作类型之间的映射关系可参见表1所示。
表1
字段1的值 操作类型
0 创建目标网络
1 删除目标网络
2 挂起目标网络
3 恢复目标网络
4 修改目标网络的网络属性
在这种情况下，若用户确定自身的需求为挂起目标网络，则终端设备确定该请求消息中字段1的值为2。需要说明的是，该示例中字段1值的表现形式仅为示例性的，不应视为对本申请的一个具体限定，该字段1的值还可以用比特(bit)位来体现，例如字段1包括3个比特(bit)位，此时当字段1的值为000，则表示操作类型为创建目标网络；当字段1的值为001，则表示操作类型为修改目标网络；当字段1的值为010，则表示操作类型为挂起目标网络；当字段1的值为011，则表示操作类型为恢复目标网络；当字段1的值为100，则表示操作类型为修改目标网络的网络属性。
在一个可能的实施方式中，该请求消息还包括终端设备的用户信息、操作类型对应的操作参数或目标网络的信息中的一种或多种。
其中，用户信息包括用于指示用户的永久标识的信息(例如，用户永久标识(subscription permanent identifier，SUPI)、国际移动用户识别码(international mobile subscriber identification number，IMSI)、移动用户的ISDN号码(mobile subscriber international ISDN number，MSISDN))、用户组标识、用户临时标识(例如全局唯一临时标识(globally unique temporary identity，GUTI))或设备标识(例如永久设备标识(permanent equipment identifier，PEI)、国际移动设备标识(international mobile equipment identity，IMEI))中的一种或多种。操作类型对应的操作参数可以指示一个具体的操作，例如，当请求消息为请求创建目标网络时，该请求消息中携带的操作参数指示创建一个具体的目标网络；当请求消息为修改目标网络的网络属性时，该请求消息中携带的操作参数指示对目标网络的某个(或某几个)具体的网络属性进行修改。目标网络的信息包括目标网络标识、容量值、能力列表、用户服务列表或配置策略中的一种或多种。
示例性的，用户11将创建容量值a1和能力值p1的目标网络，则用户11的终端设备确定的请求消息可以包括：用户11的标识、操作类型为创建网络，操作参数包括容量值a1和能力值p1。
示例性的，目标网络N1的用户服务列表中包括用户11、用户12和用户21。用户11(可以理解为对目标网络N1具有管理权限的用户)想将用户21移出该目标网络N1的用户服务列表，则用户11的终端设备确定对目标网络N1进行操作的请求消息，该请求消息可以包括：用户11的标识、目标网络N1的标识、操作类型为修改目标网络的网络属性、操作参数为删除目标网络N1的用户服务列表中用户21的标识。
S302、终端设备向核心网发送该请求消息，相应的，核心网接收该请求消息。
其中，该请求消息为终端设备和核心网之间的控制面信令或用户面信令。换言之，终端设备通过其与核心网之间的控制面信令或用户面信令，向核心网发送该请求消息。
在一个可能的实现中，控制面信令可以非接入层(non-access stratum，NAS)信令。
在一个可能的实现中，用户面信令可以为基于分组无线服务技术隧道协议(general packet radio service tunelling protocol，GTP)用户面(即GTP-U)的消息。在一个可能的实现中，执行S302步骤的核心网设备为第一功能网元，终端设备向第一功能网元发送该请求消息，其中第一功能网元用于将终端设备接入核心网，即第一功能网元具有用户网络接入功能。示例性地，该第一功能网元可以为图1b中的AMF网元或图2中的NSN网元等。第一功能网元也可以称为接入管理网元或网络服务网元。
S303、核心网基于该请求消息，对核心网管理的目标网络的生命周期进行操作。
换言之，核心网根据该请求消息中的操作类型的信息，创建目标网络、删除目标网络、 修改目标网络的运行状态(包括挂起目标网络或恢复目标网络)、或修改目标网络的网络属性。
一种可能的实现中，核心网管理有一个或多个用户网络，在该请求消息中的操作类型为、删除目标网络、修改目标网络的运行状态(包括挂起目标网络或恢复目标网络)、或修改目标网络的网络属性中任一种的情况下，核心网基于该请求消息，从该多个网络中确定目标网络，并对该目标网络的生命周期进行操作。
在一个可能的实现中，执行S303步骤的核心网设备为第二功能网元，该第二功能网元用于对该目标网络的生命周期进行操作。例如该第二功能网元可以为NCF网元。第二功能网元也可以称为网络控制网元。
需要理解的是，该第二功能网元可以与前述第一功能网元合设部署(即某一实体既具有第一功能网元的功能，也具有第二功能网元的功能)，或者第二功能网元可以与前述第一功能网元分离部署。在第二功能网元与第一功能网元分离部署的情况下，第一功能网元与第二功能网元之间具有通信连接(即可以理解为第一功能网元可以与第二功能网元进行通信)。在S302中第一功能网元接收来自终端设备的请求消息(为了便于区分，后文将S302中的请求消息称为第一请求消息)之后，第一功能网元可以将该第一请求消息转发至第二功能网元，进而在S303中第二功能网元可以根据该请求消息对目标网络的生命周期进行操作。或者，在S302中第一功能网元接收来自终端设备的第一请求消息之后，第一功能网元可以根据该第一请求消息，向第二功能网元发送第二请求消息(该第二请求消息包括的内容可以与第一请求消息包括的内容相同)，以使第二功能网元根据该第二请求消息对目标网络的生命周期进行操作。
在一个可能的实现中，当第二功能网元和第一功能网元分离部署的情况下，为了提升通信系统的安全性，第二功能网元可以对第一功能网元的身份进行鉴定；在对该第一功能网元的身份鉴定通过之后，该第二功能网元对目标网络的生命周期进行操作。
换言之，第二功能网元接收来自第一功能网元的第二请求消息之后，第二功能网元对第一功能网元的身份进行验证，其验证内容包括但不限于以下内容中的一项或多项：验证第一功能网元是否真实存在；或者，验证该第一功能网元是否具有发送第二请求消息的权限(即第一功能网元是否具有请求第二功能网元对目标网络的生命周期进行操作的权限)；或者，验证该第一功能网元是否合法。在第二功能网元对第一功能网元的身份验证通过之后，第二功能网元根据该第二请求消息对目标网络的生命周期进行操作。
为了便于理解本申请的技术方案，下面以第二功能网元与第一功能网元分开部署的情况为例，对创建目标网络、删除目标网络、修改目标网络的运行状态或修改目标网络的网络属性进行示例性说明。
1、创建目标网络。
目标网络与接入网设备之间的连接可以是直接连接(后文简称为直连)，也可以是非直接连接(后问简称非直连)。需要理解的是，目标网络与接入网设备直连，即接入网设备可以与目标网络进行直接通信，换言之，接入网设备接收到来自终端设备的服务请求消息(该服务请求消息用于请求目标网络提供网络服务)之后，接入网设备可以直接将该服务请求消息转发至目标网络，以使目标网络提供相应的网络服务。目标网络与接入网设备非直连，即接入网设备通过第一功能网元与目标网络进行间接通信。换言之，接入网设备接收来自终端设备的服务请求消息之后，接入网设备向第一功能网元发送该服务请求消息，由第一功能网元向目标网络转发该服务请求消息，以使目标网络提供相应的网络服务。
可见，目标网络与接入网设备直连的情况，可以节省信令传输开销；目标网络与接入网 设备非直连的情况下，接入网设备不能直接接触目标网络，可以提升目标网络的安全性。
下面基于目标网络与接入网设备直连的情况，和目标网络与接入网设备非直连的情况，对创建目标网络的过程进行详细讲解。
在目标网络与接入网设备直连的情况下，请参见图4a所示，图4a为本申请提供的一种创建目标网络的流程示意图。其中：
S401、第二功能网元与资源管理功能交互，创建目标网络。
第二功能网元与资源管理功能进行交互，申请可用的运行资源，并进行运行实体的实例化。这种运行实体可能是新实例化的虚拟机，新实例化的容器，或者在已有虚拟机或容器上运行的新的进程、线程或者其他运行时的执行实体；进一步地，第二功能网元根据来自终端设备的请求消息创建目标网络。
其中，资源管理功能用于对网络资源进行管理，例如分配资源生成用户网络所需的网络功能实例。在一个可能中，该资源管理功能可以是管理和编排(management and orchestration，MANO)网元、容器(docker)管理网元、docker引擎或者其他资源管理功能。
在一个可能的场景中，核心网中还可以包括第三功能网元，该第三功能网元用于存储网络配置数据，该网络配置数据包括网络配置参数和/或网络运行策略数据。其中，网络配置参数包括网络运行所需的参数(例如数据丢包率、时延、带宽或网速中的一种或多种)、网络运行所需的脚本或环境变量中的一种或多种；网络运行策略数据包括QoS策略、计费策略或用户接入控制策略中的一种或多种。在一个可能的实现中，第三功能网元中的网络配置数据与用户标识相关联，或者第三功能网元中的网络配置数据与网络的标识相关联，或者第三功能网元中的每个配置数据与索引值相关联。
若第三功能网元中的网络配置数据与用户标识相关联，在这种情况下，该请求消息中携带用户标识和操作类型(此处的操作类型为创建目标网络)，第二功能网元根据用户的标识和资源管理功能交互，创建目标网络，并且第二功能网元(或目标网络)根据用户标识从第三功能网元中获取目标网络对应的网络配置数据；进一步地，第二功能网元基于该网络配置数据，对目标网络进行配置。
若第三功能网元中的网络配置数据与网络的标识相关联，在这种情况下，该请求消息中携带用户标识和操作类型(此处的操作类型为创建目标网络)。进一步地，第二功能网元根据用户的标识与资源管理功能交互，创建目标网络；目标网络(或者第二功能网元)根据该目标网络的标识，从该第三功能网元获取该目标网络标识对应的网络配置数据。目标网络(或者第二功能网元)基于该网络配置数据，对目标网络进行配置。
若第三功能网元中的每个配置数据与索引值相关联，在这种情况下，该请求消息中携带用户标识、操作类型(此处的操作类型为创建目标网络)以及操作相关的参数(此处为创建目标网络的具体参数，例如该目标网络的容量值、能力、服务用户列表等)。进一步地，第二功能网元根据用户的标识与资源管理功能交互，创建目标网络；目标网络(或者第二功能网元)根据该操作参数确定目标索引值，并根据该目标索引值从该第三功能网元获取该目标网络标识对应的网络配置数据。目标网络(或者第二功能网元)基于该网络配置数据，对目标网络进行配置。
S402、目标网络与接入网设备交互，建立通信连接和建立用户上下文连接。
具体地，第二功能网元创建目标网络之后，第二功能网元向目标网络发送接入网设备的信息，并通知更新用户上下文信息；其中，该接入网设备的信息用于寻址接入网设备，该用户上下文信息用于建立用户上下文连接。进一步地，目标网络根据该接入网设备的信息，与 该接入网设备建立通信连接，根据用户上下文信息建立用户上下文连接。其中，该接入网设备为将该终端设备接入目标网络的设备；该接入网设备的信息用于寻址接入网设备，例如，该接入网设备包括接入网设备标识，和/或，接入网设备地址信息。
或者，第二功能网元创建目标网络之后，第二功能网元向接入网设备发送目标网络的信息，并通知更新用户上下文信息；其中，该目标网络的信息用于寻址目标网络，该用户上下文信息用于建立用户上下文连接。进一步地，接入网设备根据该目标网络的信息，与该目标网络建立通信连接，根据用户上下文信息建立用户上下文连接。其中，该接入网设备为将该终端设备接入目标网络的设备；该目标网络的信息用于寻址目标网络，例如该目标网络的信息包括目标网络的标识，和/或，目标网络的地址信息。
需要说明的是，该通信连接包括基于超文本传输协议(hypertexttransferprotocol，HTTP)、传输控制协议(transmission control protocol，TCP)、流控制传输协议(stream control transmission protocol，SCTP)或其他协议建立完成的底层连接中的一种或多种。用户上下文信息包括用户状态、用户属性信息和用户相关的通信连接信息。
S403、接入网设备修改终端设备的连接信息。
换言之，接入网设备在与目标网络建立通信连接和用户上下文连接后，修改来自终端设备的消息的发送路径(或称为路由路径)，以便于后续接入网设备向目标网络转发来自终端设备的网络服务请求消息(例如，PDU会话建立请求消息)。
在目标网络与接入网设备非直连的情况下，即目标网络与接入网设备之间通过第一功能网元进行间接交互，请参见图4b所示，图4b为本申请提供的另一种创建目标网络的流程示意图。
S411、第二功能网元与资源管理功能交互，创建目标网络。
其中，该S411的具体实施方式可参见对前述S401的具体实施方式的描述，重复之处在此不再进行赘述。
S412、目标网络向第一功能网元发送第一更新请求，相应的，第一功能网元接收来自目标网络的第一更新请求。
其中，该第一更新请求用于请求第一功能网元更新(或理解为修改)目标网络的接入控制。其中，该第一更新请求中携带有目标网络的信息，并通知更新用户上下文信息；其中，该目标网络的信息用于寻址目标网络，例如，该目标网络的信息包括但不限于目标网络的标识或目标网络的地址信息；该用户上下文信息用于建立用户上下文连接。
S413、第一功能网元基于该第一更新请求，更新(或修改)连接信息。
换言之，第一功能网元保存目标网络的信息，并建立通信连接和用户上下文连接，以便于第一功能网元在接收到用于请求目标网络提供网络服务的请求消息(或接入目标网络的请求消息)之后，第一功能网元将接收用于请求该目标网络提供网络服务的请求消息，转发至目标网络。
S414、第一功能网元向接入网设备发送第二更新请求，相应的，接入网设备接收来自第一功能网元的第二更新请求。
换言之，该第二更新请求可以使接入网设备与第一功能网元之间建立关于目标网络的通信连接和用户上下文连接，即该通信连接和用户上下文连接均与目标网络相关联。其中，该第二更新请求用于请求接入网设备更新(或理解为修改)目标网络的接入控制。该第二更新请求中携带有目标网络的信息，该目标网络的信息用于寻址目标网络。例如，该目标网络的信息包括但不限于目标网络的标识或目标网络的地址信息。
S415、接入网设备基于向第一功能网元发送针对该第二更新请求的应答消息，相应的，第一功能网元接收来自接入网设备的针对该第二更新请求的应答消息。该应答消息中携带有接入网设备基于第二更新请求的操作结果。
接入网设备基于该第二更新请求进行对应操作：接入网设备与第一功能网元之间建立关于目标网络的通信连接和用户上下文连接，即该通信连接和用户上下文连接与目标网络相关联。进一步地，接入网设备根据该基于第二更新请求的操作结果，向第一功能网元发送针对该第二更新请求的应答消息。
S416、第一功能网元向目标网络发送针对该第一更新请求的应答消息，相应的，目标网络接收来自第一功能网元的针对该第一更新请求的应答消息。
针对该第一更新请求的应答消息，用于指示第一功能网元根据该第一更新请求的操作结果、以及接入网设备基于第二更新请求的操作结果。换言之，当第一功能网元根据该第一更新请求的操作结果为成功，且接入网设备基于第二更新请求的操作结果为成功的情况下，第一功能网元向目标网络发送的针对该第一更新请求的应答消息的操作结果为成功。当第一功能网元根据该第一更新请求的操作结果为失败，或接入网设备基于第二更新请求的操作结果为失败的情况下，第一功能网元向目标网络发送的针对该第一更新请求的应答消息的操作结果为失败。
2、删除目标网络
下面基于目标网络与接入网设备直接连接(后文简称为直连)的情况，和目标网络与接入网设备非直连的情况，对删除目标网络的过程进行详细讲解。
在目标网络与接入网设备直连的情况下，请参见图5a所示，图5a为本申请提供的一种删除目标网络的流程示意图。其中：
S501、第二功能网元向目标网络发送控制操作请求消息，相应的，目标网络接收来自第二功能网元的控制操作请求消息，该控制操作请求消息包括操作类型(此处为删除目标网络)。
第二功能网元接收来自终端设备请求消息，该请求消息用于删除目标网络。在这种情况下，第二功能网元向目标网络发送控制操作请求消息，该控制操作请求消息用于指示目标网络进行拆链。
S502、目标网络向接入网设备发送拆链请求，相应的，接入网设备接收来自目标网络的拆链请求。
目标网络根据该第二功能网元发送的控制操作请求消息，删除与接入网设备之间的用户上行文连接，并向接入网设备发送拆链请求，该拆链请求用于指示(或通知)接入网设备删除与该目标网络之间的用户上下文连接。
其中，该拆链请求中包括目标网络的信息，该目标网络的信息用于寻址目标网络。该目标网络的信息包括但不限于目标网络的信息包括目标网络的标识，和/或，目标网络的地址信息。
S503、接入网设备根据该拆链请求，删除与目标网络之间的用户上下文连接。
接入网设备根据该拆链请求，可以平滑地删除与目标网络之间的用户上下文连接。其中，平滑地删除用户上下文连接的过程可以描述为：接入网设备向终端设备发送通知消息，该通知消息用于通知目标网络服务的终端设备离线；在目标网络服务的终端设备均离线后，接入网设备再删除与目标网络之间的用户上下文连接。通过这样的方法，在目标网络读物的用户均离线后再进行拆链，可以提升用户的体验感。
或者，接入网设备根据该拆链请求，可以进行非平滑地删除与目标网络之间的用户上下 文连接。换言之，接入网设备接收该拆链请求之后，无论目标网络服务的终端设备是否离线，接入网设备直接删除与目标网络之间的用户上下文连接。通过这样的方法，可以提升接入网设备拆链的效率。
S504、接入网设备向目标网络发送该拆链请求对应的应答消息，相应的，目标网络接收来自接入网设备发送的该拆链请求对应的应答消息。该应答消息中携带有接入网设备基于该拆链请求的操作结果。
需要了解的是，本申请所提及的拆链是指删除两个设备之间的上下文连接，应答消息是通过信令通道传输，因此两个设备进行拆链之后，并不影响后续传输应答消息(即该两个设备之间依然可以通过信令通道(或通信连接)传输应答消息)。例如，S503中接入网设备根据该拆链请求，拆除了接入网设备与目标网络之间关于的上下文连接之后，在S504中接入网设备可以通过信令通道(通信连接)，向第一功能网元发送针对第二拆链请求的应答消息。
S505、目标网络向第二功能网元发送针对控制操作请求消息的应答消息，相应的，第二功能网元接收来自目标网络的针对第二拆链请求的应答消息。该应答消息中携带有目标网络和接入网设备之间的用户上下文连接的拆链操作结果。
S506、第二功能网元与资源管理功能交互，释放该目标网络的资源。
第二功能网元释放目标网络的资源，释放掉目标网络的资源之后，可以理解为与目标网络相关的所有通信连接(包括目标网络与第二功能网元之间的通信连接、以及目标网络与接入网设备之间的通信连接)被拆除。其中，删除通信连接可以是基于HTTP、TCP、SCTP或其他协议完成的删除底层连接中的一种或多种。
在目标网络与接入网设备非直连的情况下，请参见图5b所示，图5b为本申请提供的另一种删除目标网络的流程示意图。其中：
S511、第二功能网元向目标网络发送控制操作请求消息，相应的，目标网络接收来自第二功能网元的控制操作请求消息。该控制操作请求消息包括操作类型(此处为删除目标网络)。
S512、目标网络向第一功能网元发送第一拆链请求，相应的，第一功能网元接收来自目标网络的第一拆链请求。
目标网络根据该第二功能网元发送的控制操作请求消息，向第一功能网元发送第一拆链请求，该第一拆链请求用于指示(或通知)第一功能网元删除与该目标网络之间的用户上下文连接。其中，该拆链请求中包括目标网络的信息，该目标网络的信息用于寻址目标网络。该目标网络的信息包括但不限于目标网络的信息包括目标网络的标识，和/或，目标网络的地址信息。
S513、第一功能网元向接入网设备发送第二拆链请求，相应的，接入网设备接收来自第一功能网元的第二拆链请求。
第一功能网元根据第一拆链请求，向接入网设备发送第二拆链请求，该第二拆链请求用于指示(或通知)接入网设备删除与第一功能网元之间的、与该目标网络相关的用户上下文连接。其中，该拆链请求中包括目标网络的信息，该目标网络的信息用于寻址目标网络。该目标网络的信息包括但不限于目标网络的信息包括目标网络的标识，和/或，目标网络的地址信息。
S514、接入网设备根据该第二拆链请求，进行连接删除处理。
具体地，接入网设备可以根据该第二拆链请求，进行平滑地连接删除处理。或者，接入网设备可以根据该第二拆链请求，进行非平滑地连接删除处理。
S515、接入网设备向第一功能网元发送针对第二拆链请求的应答消息，相应的，第一功 能网元接收来自接入网设备的针对第二拆链请求的应答消息。该应答消息中携带有接入网设备基于该第二拆链请求的操作结果。
S516、第一功能网元向目标网络发送针对第一拆链将请求的应答消息，相应的，目标网络接收来自第一功能网元的针对第二拆链请求的应答消息。该应答消息中携带有第一功能网元基于该第一拆链请求的操作结果，或者，还包括接入网设备基于该第二拆链请求的操作结果。
S517、目标网络向第二功能网元发送针对控制操作请求消息的应答消息，相应的，第二功能网元接收来自目标网络的针对第二拆链请求的应答消息。该应答消息中携带有第一功能网元基于该第一拆链请求的操作结果，或者，还包括接入网设备基于该第二拆链请求的操作结果。
S518、第二功能网元与资源管理功能交互，释放该目标网络的资源。
第二功能网元释放目标网络的资源，释放掉目标网络的资源之后，可以理解为与目标网络相关的所有通信连接(包括目标网络与第二功能网元之间的通信连接、以及目标网络与第一功能网元之间的通信连接)被拆除。
3、修改目标网络(修改目标网络的网络属性或修改目标网络的运行状态(包括挂起目标网络或恢复目标网络))
下面基于第二功能网元直接控制第一功能网元的情况，和第二功能网元间接控制第一功能网元的请求，对挂起目标网络的过程进行详细讲解。
在第二功能网元直接控制第一功能网元的情况下，请参见图6a所示，图6a为本申请提供的一种修改目标网络(修改目标网络的运行状态或修改目标网络的网络属性)的流程示意图。其中：
S601、第二功能网元向目标网络发送第一控制操作请求消息，相应的，目标网络接收来自第二功能网元的第一控制操作请求消息。该第一控制操作请求消息包括操作类型。
其中，在图6a中该操作类型为修改目标网络的运行状态(即挂起目标网络或恢复目标网络)或修改目标网络的网络属性的一种。该第一控制操作请求消息用于请求目标网络进行该操作类型对应操作处理，即修改目标网络的运行状态(即挂起该目标网络或恢复目标网络)或修改目标网络的网络属性的一种。在这种情况下，该第一控制操作请求消息还可以包括目标网络的标识信息。
一种可能的实现中，修改目标网络的网络属性包括修改以下项中的一种或多种：1、修改目标网络的网络能力，例如打开或者关闭该目标网络对应的设备能力或服务(service)，其中，该service可以指3GPP定义的每个NF提供的service，在此种情况下，修改该NF提供的service之后会触发到NRF的注册更新。2、修改目标网络的网络容量，例如增大目标网络的容量值(扩容处理)、减小目标网络的容量值(缩容处理)或将该目标网络的容量值修改为特定的值或等级从而实现目标网络的扩容或缩容。3、修改目标网络的用户列表，例如在目标网络的用户列表中新增用户信息或删除用户信息，该用户信息包括用户永久标识(例如IMSI/SUPI/MSISDN)、用户组标识、用户临时标识(例如GUTI)、设备标识(例如PEI/IME)中的一种或多种。
在一个可能的实现中，在第一控制操作请求消息用于修改目标网络的网络属性的情况下，该第一控制操作请求消息还可以包括操作参数。
S602、第二功能网元向第一功能网元发送第二控制操作请求消息，相应的，第一功能网元接收来自第二功能网元的第二控制操作请求消息。该第二控制操作请求消息包括操作类型。
其中，该第二控制操作请求消息用于请求第一功能网元对目标网络的信息进行该操作类型对应操作处理，即挂起该目标网络、恢复目标网络或修改目标网络的网络属性的一种。
在这种情况下，该第二控制操作请求消息还可以包括目标网络的标识信息。
在一个可能的实现中，在第二控制操作请求消息用于修改目标网络的网络属性的情况下，该第二控制操作请求消息还可以包括操作参数。
需要知晓的是，在此处S601和S602的执行顺序仅为示例性的，并不应视为对本申请的一个具体限定。换言之在实际应用过程中，S601和S602可以同时执行，也可以S602先于S601执行，也可以S601先于S602执行。
S603、目标网络根据该第一控制操作请求消息中的操作类型，进行对应的操作处理。
目标网络挂起目标网络具体包括：记录用户上下文的工作状态以禁止用户后续信令，结束并上报用户的统计信息和话单数据，或通过信令立即(或通过定时器触发)去附着用户中的一种或多种。
目标网络恢复(或激活)目标网络具体包括：记录用户上下文的工作状态以恢复用户后续信令，恢复用户的统计信息和话单数据或允许用户后续信令中的一种或多种。
目标网络修改目标网络的网络属性，具体包括：目标网络根据该第一控制操作请求消息中的操作参数，修改目标网络的网络属性(包括网络能力、网络容量或用户列表中的一种或多种)。
S604、目标网络向第二功能网元发送第一控制操作请求消息对应的反馈消息，相应的，第二功能网元接收来自目标网络的第一控制操作请求消息对应的第一反馈消息。
目标网络基于第一控制操作请求消息进行对应的操作处理之后，基于该操作结果，目标网络向第二功能网元发送第一反馈消息。该第一反馈消息中包括第一操作结果信息，该第一操作结果信息用于指示目标网络基于第一控制操作请求消息进行操作的操作结果。当第一操作结果信息用于指示操作失败时，该第一操作结果信息中可以包括第一失败原因值，该第一失败原因值用于指示目标网络操作失败的具体原因。
在一个可能的实现中，该第一反馈消息中包括目标网络的标识、操作处理之后目标网络的状态(包括激活状态或挂起状态)、该目标网络的网络属性信息中的一种或多种。
S605、第一功能网元根据第二控制操作请求消息，执行操作处理。
第一功能网元根据第二功能网元发送的第二控制操作请求消息的具体内容，执行相应的操作处理。
在一个示例中，该第二控制操作请求消息中的操作类型为挂起目标网络时，第一功能网元在自身维护的信息列表中挂起该目标网络，即将该目标网络的信息更新为(或修改为)目标网络挂起时对应的信息，具体包括：记录用户上下文的工作状态以禁止用户后续信令，结束并上报用户的统计信息和话单数据，或通过信令立即(或通过定时器触发)去附着(detach)或去注册(deregistration)用户中的一种或多种。
在另一个示例中，该第二控制操作请求消息中的操作类型为恢复目标网络时，第一功能网元在自身维护的信息列表中恢复该目标网络，即将该目标网络的信息更新为(或修改为)目标网络激活时对应的信息，具体包括：记录用户上下文的工作状态以恢复用户后续信令，恢复用户的统计信息和话单数据或允许用户后续信令中的一种或多种。
在又一个示例中，该第二控制操作请求消息中的操作类型为修改目标网络的网络属性时，第一功能网元基于该第二控制操作请求消息，在自身维护的信息列表中修改该目标网络的网络属性信息，即可以理解为根据第二控制操作请求消息中的操作参数，修改该目标网络的网 络属性信息。
S606、第一功能网元向接入网设备发送网络控制接入更新请求消息，相应的，接入网设备接收来自第一功能网络的网络控制接入更新请求消息。该网络控制接入更新请求消息包括操作类型。
在该操作类型为挂起目标网络时，该网络控制接入更新请求消息用于请求接入网设备对目标网络的信息进行对应操作处理，即将该目标网络的信息更新为(或修改为)目标网络挂起时对应的信息。在这种情况下，该更新请求还可以包括目标网络的标识信息。
在该操作类型为恢复(或激活)目标网络时，该网络控制接入更新请求消息用于请求接入网设备对目标网络的信息进行对应操作处理，即将该目标网络的信息更新为(或修改为)目标网络激活时对应的信息。在这种情况下，该更新请求还可以包括目标网络的标识信息。
在该操作类型为修改目标网络的网络属性时，该网络控制接入更新请求消息用于请求接入网设备对其维护的目标网络的网络属性进行修改。在这种情况下，该第二控制操作请求消息还可以包括目标网络的标识信息和操作参数。
S607、接入网设备根据网络控制接入更新请求，执行操作处理。
接入网设备根据该网络控制接入更新请求的具体内容，执行相应的操作处理。
在一个示例中，该网络控制接入更新请求中的操作类型为挂起目标网络时，接入网设备在自身维护的信息列表中将该目标网络的信息更新为(或修改为)目标网络挂起时对应的信息，具体包括：记录用户上下文的工作状态以禁止用户后续信令，结束并上报用户的统计信息和话单数据，或通过信令立即(或通过定时器触发)去附着用户中的一种或多种。
在另一个示例中，该网络控制接入更新请求中的操作类型为恢复目标网络时，接入网设备在自身维护的信息列表中将该目标网络的信息更新为(或修改为)目标网络激活时对应的信息，具体包括：记录用户上下文的工作状态以恢复用户后续信令，恢复用户的统计信息和话单数据或允许用户后续信令中的一种或多种。
在又一个示例中，该网络控制接入更新请求中的操作类型为修改目标网络的网络属性时，接入网设备根据该网络控制接入更新请求中的操作参数，对该接入网设备维护的目标网络的网络属性进行修改。
S608、接入网设备向第一功能网元发送网络控制接入更新请求对应的第二反馈消息，相应的，第一功能网元接收来自接入网设备的网络控制接入更新请求对应的第二反馈消息。
接入网设备根据网络控制接入更新请求进行对应的操作处理之后，接入网设备向第一功能网元发送第二反馈消息。该第二反馈消息中包括第二操作结果信息，该第二操作结果信息用于向第一功能网元反馈接入网设备的操作结果，其中，该第二操作结果信息用于指示操作成功或操作失败。当第二操作结果信息用于指示操作失败时，该第二操作结果信息中可以包括第二失败原因值，该第二失败原因值用于指示接入网设备操作失败的具体原因。
在一个可能的实现中，该第二反馈消息中还可以包括目标网络的标识、操作处理之后在接入网设备处该目标网络的状态(包括激活状态或挂起状态)、该目标网络的网络属性信息中的一种或多种。
S609、第一功能网元向第二功能网元发送第二控制操作请求消息对应的第三反馈消息，相应的，第二功能网元接收来自第一功能网元的第二控制操作请求消息对应的第三反馈消息。
该第三反馈消息中包括第三操作结果信息，该第三操作结果信息用于向第二功能网元反馈第一功能网元和接入网设备的操作结果，该第三操作结果为以下几种情形的任一种：1、接入网设备的操作结果为成功、且第一功能网元的操作处理结果为成功时，该第三反馈消息携 带的操作结果信息为成功；2、接入网设备的操作结果为失败，或者，第一功能网元的操作处理结果为失败时，该第三反馈消息携带的操作结果为失败，此时该第三反馈消息中还可以携带第三失败原因值(用于指示第三反馈消息的操作结果为失败的具体原因)。
在一个可能的实现中，该第三反馈消息还可以携带有第一功能网元处该目标网络的状态信息(包括激活状态或挂起状态)、目标网络的标识或该目标网络的网络属性信息中的一种或多种。
在第二功能网元间接控制第一功能网元的情况下，请参见图6b所示，图6b为本申请提供的一种修改目标网络(修改目标网络的运行状态或修改目标网络的网络属性)的流程示意图。其中：
S611、第二功能网元向目标网络发送第一控制操作请求消息，相应的，目标网络接收来自第二功能网元的第一控制操作请求消息。该第一控制操作请求消息包括操作类型。
其中，S611的具体实施方式可参见前述对S601的具体实施方式的描述，重复支持不再进行赘述。
S612、目标网络根据该第一控制操作请求消息中的操作类型，进行对应的操作处理。
其中，S612的具体实施方式可参见前述对S603的具体实施方式的描述，重复支持不再进行赘述。
S613、目标网络向第一功能网元发送第二控制操作请求消息，相应的，第一功能网元根据接收来自目标网络的第二控制操作请求消息。该第二控制操作请求消息包括操作类型。
其中，该第二控制操作请求消息用于请求第一功能网元对目标网络的信息进行该操作类型对应操作处理，即挂起该目标网络、恢复目标网络或修改目标网络的网络属性的一种。一种可能的实现中，该第二控制操作请求消息还可以包括目标网络的标识信息。
在一个可能的实现中，在第二控制操作请求消息用于修改目标网络的网络属性的情况下，该第二控制操作请求消息还可以包括操作参数。
S614、第一功能网元根据该第二控制操作请求消息，执行操作处理。
S615、第一功能网元向接入网设备发送网络控制接入更新请求消息，相应的，接入网设备接收来自第一功能网元的网络控制接入更新请求消息。该网络控制接入更新请求消息包括操作类型。
S616、接入网设备根据网络控制接入更新请求，执行操作处理。
S617、接入网设备向第一功能网元发送该网络控制接入更新请求对应的第二反馈消息，相应的，第一功能网元接收来自接入网设备的该网络控制接入更新请求对应的第二反馈消息。
其中，S614-S617的具体实施方式可参见前述对S605-S608具体实施方式的描述，重复之处在此不再进行赘述。
S618、第一功能网元向目标网络发送第二控制操作请求消息对应的第三反馈消息，相应的，目标网络接收来自第一功能网元的第二控制操作请求消息对应的第三反馈消息。
第二控制操作请求消息对应的反馈消息相关的描述可参见S609处的描述，此处不再赘述。
S619、目标网络向第二功能网元发送第一控制操作请求消息对应的第一反馈消息，相应的，第二功能网元接收来自目标网络的第一控制操作请求消息对应的第一反馈消息。
目标网络基于来自第一功能网元的反馈消息、以及目标网络基于第一控制操作请求消息的操作处理结果，向第二功能网元发送第一反馈消息。该第一反馈消息中包括第一操作结果信息，该第一操作结果信息用于向第二功能网元反馈目标网络、第一功能网元和接入网设备的操作结果。该第一操作结果信息为以下几种情形的任一种：1、第一功能网元的操作结果为 成功、接入网设备的操作结果为成功、且目标网络的操作处理结果为成功时，该第一反馈消息携带的操作结果为成功；2、第一功能网元的操作结果为失败、接入网设备的操作结果为失败、且目标网络的操作处理结果为失败时，此时该第一反馈消息中还可以携带失败原因值(用于指示第一反馈消息的操作结果为失败的具体原因)。
在一个可能的实现中，该第一反馈消息还可以携带有第一功能网元处该目标网络的状态(包括激活状态或挂起状态)、目标网络的标识或该目标网络的网络属性信息中的一种或多种。
可见，通过图3提供的网络资源管理方法，终端设备可以直接通过核心网设备对目标网络进行操作，相比于用户通过运营商为媒介对目标网络进行修改的方式，缩短了对目标网络修改的生效周期，提升效率。
请参见图7，图7是本申请实施例提供的另一种网络资源管理方法的流程示意图。如图7所示，该网络资源管理方法的方法执行主体可以为核心网设备或核心网设备中的芯片，或者执行主体可以为终端设备或终端设备中的芯片。图7以核心网设备和终端设备为执行主体为例进行说明。其中：
S701、终端设备确定请求消息，该请求消息用于对目标网络的生命周期进行操作。
S702、终端设备向核心网设备发送该请求消息，相应的，核心网设备接收来自终端设备的请求消息。
其中，S701-S702的具体实现方式可参见前述对S301-S302具体实现方式的描述，重复之处在此不再进行赘述。
S703、核心网设备基于该请求消息进行操作鉴权。
核心网设备接收来自终端设备的请求消息之后，核心网设备对该请求消息进行操作鉴权，鉴定该请求消息是否来自于合法的(或理解为真实存在的)终端设备、或者鉴定该请求消息的内容是否合法(或理解为可以被核心网设备所执行，即该终端设备具有该请求消息对应的操作权限)，避免核心网设备根据该请求消息进行无效操作，并且提升目标网络的安全性。
在一个可能的实施方式中，核心网设备基于请求消息进行操作鉴权，包括以下方式的一种或多种：
方式一、核心网设备根据操作类型，对目标网络的状态进行鉴权。
在这种方式操作鉴权方式中，核心网设备根据目标网络的状态，判断目标网络是否能被执行该请求消息中操作类型对应的处理操作，即核心网设备判断该操作类型是否与目标网络的状态相匹配。若该操作类型与目标网络的状态匹配，则核心网设备对目标网络的状态鉴权通过；或者，若操作类型与目标网络的状态不匹配，则核心网设备对目标网络的状态鉴权不通过。
需要理解的是，该操作类型与目标网络的状态匹配，是指核心网设备根据目标网络的状态，判断出目标网络能被执行该请求消息中操作类型对应的处理操作；反之，该操作类型与目标网络的状态不匹配，是指核心网设备根据目标网络的状态，判断出目标网络不能被执行该请求消息中操作类型对应的处理操作。
在一个可能的实施方式中，操作类型与目标网络的状态不匹配，包括以下项中的一种或多种：1、操作类型为创建目标网络时，目标网络的状态为存在。2、操作类型为删除目标网络时，目标网络的状态为不存在。3、操作类型为修改目标网络的网络属性时，目标网络的状态为不存在。4、操作类型为挂起目标网络时，目标网络的状态为不存在或挂起状态。5、操作类型为恢复目标网络时，目标网络的状态为不存在或激活状态。
反之，当操作类型为创建目标网络时，目标网络不存在，则可确定操作类型与目标网络的状态匹配；当操作类型为删除目标网络时，目标网络存在，则可确定操作类型与目标网络的状态匹配；当操作类型为修改目标网络的网络属性时，目标网络存在，则可确定操作类型与目标网络的状态匹配；当操作类型为挂起目标网络时，目标网络存在且处于激活状态，则可确定操作类型与目标网络的状态匹配；当操作类型为恢复目标网络时，目标网络存在且处于挂起状态(或去激活状态、待机状态)，则可确定操作类型与目标网络的状态匹配。
方式二、核心网设备对操作类型的操作权限进行鉴权。
在这种方式操作鉴权方式中，核心网设备鉴定发出该请求消息的终端设备是否具有该操作类型对应的操作权限。若终端设备具有该操作类型对应的操作权限，则核心网设备对操作类型的操作权限鉴权通过；或者，若终端设备不具有该操作类型对应的操作权限，则核心网设备对操作类型的操作权限鉴权失败。
在一个可能的实施方式中，该请求消息还包括终端设备的用户信息，进一步地核心网设备基于该用户信息，获取用户签约信息；核心网设备基于该用户签约信息和/或本地配置策略，对操作类型的操作权限进行鉴权。其中，用户签约信息包括允许的操作动作列表、允许的网络标识列表、允许的网络容量配额、允许的服务用户列表或配置策略列表中的一种或多种。本地配置策略可以理解为运营商的管控策略或核心网设备的管控策略等。
换言之，核心网设备可以根据终端设备的用户信息获取用户签约信息，在用户签约信息中包括该终端设备被允许的操作权限。进一步地，核心网设备根据该用户签约信息中终端设备被允许的操作权限，确定终端设备是否能请求执行该请求消息中的操作类型。当用户签约信息包含了该请求消息中的操作类型，则核心网设备对操作类型的操作权限鉴权通过；反之，当用户签约信息不包含该请求消息中的操作类型，则核心网设备对操作类型的操作权限鉴权失败(即不通过)。
示例性地，核心网设备接收终端设备1发送的请求消息，该请求消息包括用户信息(用户A的标识)、操作类型(修改网络1(即目标网络)的网络属性)、操作参数(将网络容量值改为数值a3)。核心网设备基于用户A的标识获取用户A的签约信息如表2所示。
表2
允许的网络标识列表 允许的操作动作列表 允许的网络容量配额
网络1 创建、挂起、恢复、修改网络属性 a1、a2
网络2 挂起、恢复、修改网络属性 a1、a2、a3
网络3 创建、删除 a2
进一步地，核心网设备根据该用户A的签约信息，鉴定该请求消息的操作权限。可见，在用户A的签约信息中，终端设备可以对网络1的网络属性进行修改，可以将该网络1的网络容量数值修改为a1或a2，终端设备不具有将网络1的网络容量数值修改为a3的权限。在这种情况下，核心网设备对该请求消息中操作类型的操作权限鉴权失败。
需要声明的是，操作鉴权方式一和操作鉴权方式二可以均被执行、也可以只执行其中任一项，本申请对此不进行具体限定。并且，当操作鉴权方式一和操作鉴权方式二可以均被执行时，操作鉴权方式一和操作鉴权方式二的执行顺序，本申请在此亦未进行具体限定，即操作鉴权方式一可以先于操作鉴权方式二被执行，或者，操作鉴权方式一可以后于操作鉴权方式二被执行，或者，操作鉴权方式一可以与操作鉴权方式二同时被执行。
在一个可能的实现中，在核心网设备中多个功能网元用于执行该操作鉴权时，执行方式一操作鉴权的功能网元可以和执行方式而操作鉴权的功能网元为同一功能网元、也可以为不 同的功能网元。
S704、当操作鉴权的结果为通过时，核心网设备对目标网络的生命周期进行操作。
核心网设备在对请求消息进行操作鉴权之后，操作鉴权通过的情况下，核心网设备根据请求消息中的操作类型和/或操作参数，对目标网络的生命周期进行操作。
在一个可能的实施方式中，核心网设备基于对目标网络的生命周期操作的操作结果向终端设备发送第一应答消息。其中，该第一应答消息包括目标网络的状态或目标网络的标识。换言之，第一应答消息可以用于指示核心网设备基于目标网络的生命周期操作的操作结果为成功，在这种情况下，第一应答消息可以包括目标网络的标识、核心网设备对目标网络的生命周期操作后的目标网络的状态或目标网络的网络属性信息中的一种或多种。或者，第一应答消息可以用于指示核心网设备基于目标网络的生命周期操作的操作结果为失败，在这种情况下，第一应答消息可以包括目标网络的标识、核心网设备对目标网络的生命周期操作后的目标网络的状态、目标网络的网络属性信息或失败原因值(该失败原因值用于指示本次对目标网络的生命周期操作失败的原因)。
在一个示例中，网络1的网络容量值为a1，核心网设备接收终端设备1发送的请求消息，该请求消息包括用户信息(用户A的标识)、操作类型(修改网络1(即目标网络)的网络属性)、操作参数(将网络容量值改为数值a2)。核心网设备对该请求消息的操作鉴权的结果为通过，核心网设备对将网络1的网络容量值由a1修改为a2。进一步地，核心网设备向终端设备1返回的第一应答消息可以包括：网络1的标识、网络1的状态(存在、可用或激活状态)、网络1的网络属性(网络容量值为a2)。
在另一个示例中，网络1的网络容量值为a3，核心网设备接收终端设备1发送的请求消息，该请求消息包括用户信息(用户A的标识)、操作类型(修改网络1(即目标网络)的网络属性)、操作参数(将网络容量值改为数值a2)。核心网设备对该请求消息的操作鉴权的结果为通过，核心网设备在根据请求消息对网络1的网络容量值进行修改后，该网络1的网络容量值为a3(不等于请求消息中操作参数中的容量值)，在这种情况下，即可认为核心网设备对网络1的生命周期操作失败。进一步地，核心网设备向终端设备1返回的第一应答消息可以包括：网络1的标识、网络1的状态(存在、可用或激活状态)、网络1的网络属性(网络容量值为a2)、失败的原因值1(用于指示修改后的网络容量值相同于和修改前的网络容量值)。
在一个可能的实现中，当操作鉴权的结果为不通过时，核心网设备对目标网络的生命周期不进行操作。在这种情况下，核心网设备还可以向终端设备发送第二应答消息，该第二应答消息用于指示对目标网络的生命周期操作的操作结果为失败。在这种情况下，该第二应答消息还可以携带失败的原因值(用于指示本次操作失败的原因)。例如，失败原因值与失败原因的映射关系可参见表3所示。
表3
失败原因值 失败原因
01 用户信息不存在
02 无此操作类型对应的操作权限
03 操作参数不正确
需要说明的时，在图7所涉及的核心网设备可以是核心网中的一个功能网元或多个功能网元，本申请对此不进行具体限定。在一个示例中，图7所提及的核心网设备可以包括3个功能网元：功能网元1、功能网元2和功能网元3。其中，该功能网元1用于接收来自终端设 备的请求消息(即执行S702的步骤)，该功能网元2用于基于该请求消息进行操作鉴权(即执行S703的步骤)，该功能网元3用于在操作鉴权的结果为通过时对目标网络的生命周期进行操作(即执行S704的步骤)。在另一个示例中，图7所提及的核心网设备包括两个功能网元：功能网元1和功能网元2，该两个功能网元用于执行S702-S704的步骤。例如功能网元1用于执行S702和S703的步骤，功能网元2用于执行S704的步骤；或者，功能网元1用于执行S702的步骤，功能网元2用于执行S703和S704的步骤。在又一个示例中，图7所提及的核心网设备为一个功能网元，该功能网元用于执行S702-S704的步骤。
在一个可能的实现中，若核心网设备包括多个功能网元，每个功能网元之间具有通信连接，则用于接收消息的功能网元可以对用于发送消息的功能网元进行身份鉴权。例如，第一功能网元用于基于请求消息进行操作鉴权；第二功能网元用于对目标网络的生命周期进行操作。在这种情况下，操作鉴权的结果为通过时，第一功能网元向第二功能网元发送指示消息(或第二请求消息)，该指示消息(或第二请求消息)用于请求第二功能网元对目标网络的生命周期进行操作。该指示消息(或第二请求消息)中包括操作类型和/或操作参数。第二功能网元接收该指示消息(或第二请求消息)，对第一功能网元的身份进行验证；在验证通过的情况下，第二功能网元对目标网络的生命周期进行操作。通过这样的方法，可以进一步地提升系统的安全性。
通过图7所提供的网络资源管理方法，终端设备可以直接通过核心网设备对目标网络进行操作，核心网设备对终端设备的身份、操作权限进行鉴权操作，可以在提升效率的同时提升系统的安全性。
为了更直观地对本申请的网络资源管理方法进行描述，下面结合前述图1b所示的网络架构，对本申请的网络资源管理方法进行描述。
请参见图8，图8是本申请实施例提供的又一种网络资源管理方法的流程示意图。如图8所示，该网络资源管理方法的方法执行主体可以为核心网或核心网中的芯片，或者执行主体可以为终端设备或终端设备中的芯片。图8以核心网中具体的功能网元和终端设备为执行主体为例进行说明。其中：
S801、终端设备向AMF发送请求消息，相应的，AMF接收来自终端设备的请求消息。
终端设备通过接入网设备(即图8中gNB)向AMF发送用于请求对目标网络的生命周期进行操作的请求消息。该请求消息可以是非接入层(non-access stratum，NAS)消息。具体地，该请求消息可以是一条单独的NAS消息(即该NAS消息的功能即是用于对目标网络的生命周期进行操作)；该请求消息可以携带于其他功能的NAS消息的信元中，即该NAS消息除了用于请求对目标网络的生命周期进行操作的功能之外，还包括其他功能。
其中，关于“请求消息”、“目标网络”、“对目标网络的生命周期进行操作”的具体解释，可参见前述S301中的相关描述，重复之处在此不再进行赘述。
S802、AMF基于该请求消息，进行操作鉴权。
其中，S802的具体实现方式可以参见前述S703具体实现方式的描述，重复之处在此不再进行赘述。
当AMF操作鉴权的结果为通过之后，图1b中所示的核心网对目标网络的生命周期进行操作的过程，具体如下S803～S811所示，其中：
S803、AMF对目标网络的生命周期进行操作。
具体地，AMF网元创建目标网络，是指AMF网元与MANO网元或者容器管理网元进行 交互，申请可用的运行资源，并进行运行实体的实例化。这种运行实体可能是新实例化的虚拟机，新实例化的容器，或者在已有虚拟机或容器上运行的新的进程、线程或者其他运行时的执行实体；进一步地，AMF网元根据来自终端设备的请求消息创建目标网络。
AMF删除目标网络，是指AMF网元释放(或删除)该目标网络对应的运行资源，以及删除该目标网络运行实体的实例化。
AMF网元挂起目标网络，即为将目标网络的状态设为挂起状态(或称为待机状态、待激活状态、去激活状态等)。换言之，AMF网元挂起目标网络，是指AMF网元对自身维护的目标网络的信息进行更新，更新内容包括：记录用户上下文的工作状态以禁止用户后续信令，结束并上报用户的统计信息和话单数据，或通过信令立即(或通过定时器触发)去附着用户中的一种或多种。
AMF网元恢复目标网络，即为将目标网络的状态从挂起状态变更为激活状态。换言之，AMF网元恢复目标网络，是指AMF网元对自身维护的目标网络的信息进行更新，更新内容包括：记录用户上下文的工作状态以恢复用户后续信令，恢复用户的统计信息和话单数据或允许用户后续信令中的一种或多种。
AMF网元修改目标网络的网络属性，可以理解为AMF网元修改目标网络的容量(即修改容量相关参数)、修改目标网络的能力(修改网络容量相关参数)、修改目标网络的配置策略或修改目标网络的服务用户列表中的一种或多种。换言之，AMF网元修改目标网络的网络属性，是指AMF网元对自身维护的目标网络的信息进行更新，更新内容包括：1、修改目标网络的网络能力，例如打开或者关闭该目标网络对应的设备能力或服务(service)，其中，该service指3GPP定义的每个NF提供的service)，并触发到NRF的注册更新。2、修改目标网络的网络容量，例如增大目标网络的容量值(扩容处理)或减小目标网络的容量值(缩容处理)。3、修改目标网络的用户列表，例如在目标网络的用户列表中新增用户信息或删除用户信息，该用户信息包括用户永久标识(例如IMSI/SUPI/MSISDN)、用户组标识、用户临时标识(例如GUTI)、设备标识(例如PEI/IME)中的一种或多种。
S804、(可选地)AMF向接入网设备(即gNB)发送关于目标网络的更新请求，相应的，接入网设备(即gNB)接收来自AMF的关于目标网络的更新请求。
AMF根据请求消息中对目标网络的生命周期进行操作的操作类型，向接入网设备发送关于目标网络的更新请求。该关于目标网络的更新请求中携带有操作类型的信息，该关于目标网络的更新请求用于指示接入网设备对自身维护的目标网络的信息(包括目标网络的无线链路侧信息，例如无线调度优先级、空口优先级等)进行更新(或修改)。接入网设备在接收该关于目标网络的更新请求之后，根据不同的操作类型，具有不同操作，具体如下：
在AMF创建目标网络的情况下(即操作类型为创建目标网络)，该更新请求用于请求接入网设备建立与AMF之间的通信连接(或称为链路连接、通道等)。其中，链路是指AMF与gNB之间的通信连接(或称为链路连接、通道等)，该通信连接(或称为链路连接、通道等)与目标网络相关联。
在AMF删除目标网络的情况下(即操作类型为删除目标网络)，该更新请求用于请求接入网设备删除与AMF之间的通信连接(或称为链路连接、通道等)。
在AMF挂起目标网络的情况下(即操作类型为修改目标网络的运行状态，具体为挂起目标网络)，该更新请求用于请求接入网设备中断与AMF之间的通信连接(或称为链路连接、通道等)。
在AMF恢复(或激活)目标网络的情况下(即操作类型为修改目标网络的运行状态， 具体为恢复目标网络)，该更新请求用于请求接入网设备恢复(或激活)与AMF之间的通信连接(或称为链路连接、通道等)。
在AMF修改目标网络的网络属性的情况下(即操作类型为修改目标网络的网络属性)，该更新请求用于请求(或指示)gNB对该gNB维护的目标网络的信息进行修改(或更新)。
S805、(可选地)gNB基于关于目标网络的更新请求，修改目标网络对应的信息(包括链路信息、目标网络的标识或目标网络的网络属性中的一种或多种)。
gNB基于该建立(或删除)链路连接的请求，建立(或删除)与第一功能之间的关于目标网络的通信连接(或通道)，即该通信连接(或通道)与目标网络相关联。
在AMF创建目标网络的情况下，gNB建立与AMF之间的通信连接(或称为链路连接、通道等)。
在AMF删除目标网络的情况下，gNB删除与AMF之间的通信连接(或称为链路连接、通道等)。
在AMF挂起目标网络的情况下，gNB中断与AMF之间的通信连接(或称为链路连接、通道等)。
在AMF恢复(或激活)目标网络的情况下，gNB恢复(或激活)与AMF之间的通信连接(或称为链路连接、通道等)。
在AMF修改目标网络的网络属性的情况下，该gNB对该gNB维护的目标网络的信息进行修改(或更新)。
需要知晓的是，gNB对链路的建立、删除、中断或恢复，均可以基于下一代应用协议(next generationapplicationprotocol，NGAP)或者SCTP进行。
需要说明的是，当请求消息中的操作类型为创建目标网络、删除目标网络或修改目标网络的运行状态中的一种或多种的情况下，会执行S804和S805的具体操作。当请求消息中的操作类型为修改目标网络的网络属性时，若该请求修改的目标网络的网络属性会影响到目标网络的无线链路侧信息(其中，无线链路侧信息包括无线调度优先级或空口优先级等)，则可以执行S804和S805的具体操作；若该请求修改的目标网络的网络属性不会影响到目标网络的无线链路侧信息，则可以不执行S804和S805的具体操作。
S806、(可选地)AMF向SMF发送第一操作控制请求，相应的，SMF接收来自AMF的第一操作控制请求。
AMF根据请求消息中对目标网络的生命周期进行操作的操作类型，向SMF发送第一操作控制请求。该第一操作控制请求中携带有操作类型的信息，该第一操作控制请求用于指示(或理解为请求)SMF对目标网络的生命周期进行操作。其中，该第一操作控制请求为N11接口消息。具体地，该第一操作控制请求可以是一条单独的N11接口消息(即该N11接口消息的功能即是用于对目标网络的生命周期进行操作)；该第一操作控制请求可以携带于其他功能的N11接口消息的信元中，即该N11接口消息除了用于请求对目标网络的生命周期进行操作的功能之外，还包括其他功能。
S807、(可选地)SMF对目标网络的生命周期进行操作。
其中，SMF对目标网络的生命周期进行操作的具体实施方式，可参见前述S803中AMF对目标网络的生命周期进行操作的具体实施方式的描述，在此不再进行赘述。
S808、(可选地)SMF向UPF发送第二操作控制请求，相应的，UPF接收来自SMF的第二操作控制请求。
SMF根据第一操作控制请求中对目标网络的生命周期进行操作的操作类型，向UPF发送 第二操作控制请求。该第二操作控制请求中携带有操作类型的信息，该第二操作控制请求用于指示(或理解为请求)UPF对目标网络的生命周期进行操作。其中，该第二操作控制请求为N4接口消息。具体地，该第二操作控制请求可以是一条单独的N4接口消息(即该N4接口消息的功能即是用于对目标网络的生命周期进行操作)；该第二操作控制请求可以携带于其他功能的N4接口消息的信元中，即该N4接口消息除了用于请求对目标网络的生命周期进行操作的功能之外，还包括其他功能。
S809、(可选地)UPF对目标网络的生命周期进行操作。
其中，UPF对目标网络的生命周期进行操作的具体实施方式，可参见前述S803中AMF对目标网络的生命周期进行操作的具体实施方式的描述，在此不再进行赘述。
在一个可能的实现中，UPF对目标网络的生命周期进行操作之后，UPF向SMF发送第二操作控制请求对应的反馈消息，该第二操作控制请求对应的反馈消息为N4接口消息。若UPF对目标网络的生命周期进行操作失败，则第二操作控制请求对应的反馈消息中可以携带失败原因值，该失败原因值用于指示UPF对目标网络的生命周期进行操作失败的原因。
在一个可能的实现中，SMF基于UPF对目标网络的生命周期进行操作的操作结果、以及SMF对目标网络的生命周期进行操作的操作结果，向AMF发送第一操作控制请求对应的反馈消息，该第一操作控制请求对应的反馈消息为N11接口消息。若UPF对目标网络的生命周期进行操作的操作结果为失败，或者，SMF对目标网络的生命周期进行操作的操作结果为失败，则第一操作控制请求对应的反馈消息可以携带失败原因值，该失败原因值用于指示UPF对目标网络的生命周期进行操作失败的原因，或者，该失败原因值用于指示SMF对目标网络的生命周期进行操作失败的原因。
需要说明的是，当请求消息中的操作类型为创建目标网络、删除目标网络或修改目标网络的运行状态中的一种或多种的情况下，会执行S806-S809的具体操作。当请求消息中的操作类型为修改目标网络的网络属性时，若该请求修改的目标网络的网络属性会影响到目标网络的会话(例如PDU会话)或用户面相关信息时，则执行S806-S809的具体操作；若该请求修改的目标网络的网络属性不会影响到目标网络的会话或用户面相关信息时，则可以不会执行S806-S809的具体操作。
S810、(可选地)AMF向PCF发送第三操作控制请求，相应的，PCF接收来自AMF的第三操作控制请求。
AMF根据请求消息中对目标网络的生命周期进行操作的操作类型，向PCF发送第三操作控制请求。该第三操作控制请求中携带有操作类型的信息，该第三操作控制请求用于指示(或理解为请求)PCF对目标网络的生命周期进行操作。其中，该第三操作控制请求为N15接口消息。具体地，该第三操作控制请求可以是一条单独的N15接口消息(即该N15接口消息的功能即是用于对目标网络的生命周期进行操作)；该第三操作控制请求可以携带于其他功能的N15接口消息的信元中，即该N15接口消息除了用于请求对目标网络的生命周期进行操作的功能之外，还包括其他功能。
S811、(可选地)PCF对目标网络的生命周期进行操作。
其中，PCF对目标网络的生命周期进行操作的具体实施方式，可参见前述S803中AMF对目标网络的生命周期进行操作的具体实施方式的描述，在此不再进行赘述。
在一个可能的实现中，PCF对目标网络的生命周期进行操作之后，PCF向AMF发送第三操作控制请求对应的反馈消息，该第三操作控制请求对应的反馈消息为N15接口消息。若PCF对目标网络的生命周期进行操作失败，则第三操作控制请求对应的反馈消息中可以携带 失败原因值，该失败原因值用于指示PCF对目标网络的生命周期进行操作失败的原因。
需要说明的是，当请求消息中的操作类型为创建目标网络、删除目标网络或修改目标网络的运行状态中的一种或多种的情况下，会执行S810和S811的具体操作。当请求消息中的操作类型为修改目标网络的网络属性时，若该请求修改的目标网络的网络属性会影响到目标网络的配置策略时，则执行S810和S811的具体操作；若该请求修改的目标网络的网络属性不会影响到目标网络的配置策略时，则可以会执行S810和S811的具体操作。
在一个可能的实现中，在S811执行完成之后，AMF记录目标网络的状态，并通过gNB向终端设备反馈对目标网络的生命周期的操作结果。其中，目标网络的状态包括目标网络存在(包括激活状态和挂起状态)、以及目标网络不存在。在一个可能的实现中AMF还可以记录目标网络的网络属性。
请参见图9，图9示出了本申请实施例的一种通信装置的结构示意图。图9所示的通信装置可用于实现上述网络资源管理方法对应的实施例中终端设备的部分或全部功能，或者图9所示的通信装置可用于实现上述网络资源管理方法对应的实施例中核心网设备的部分或全部功能。
在一个实施例中，图9所示的通信装置可以用于实现上述图3或图8所描述的方法实施例中终端设备的部分或全部功能。该装置可以是终端设备，也可以是终端设备中的装置，或者是能和终端设备匹配使用的装置。其中，该通信装置还可以为芯片系统。图9所示的通信装置可以包括收发单元901和处理单元902，其中：
处理单元902，用于确定请求消息，该请求消息用于对目标网络的生命周期进行操作；该请求消息为终端设备和核心网设备之间的控制面信令或用户面信令；收发单元901，用于向核心网设备发送请求消息。
在一个可能的实施方式中，请求消息包括操作类型，该操作类型包括创建目标网络、删除目标网络、修改目标网络的运行状态或修改目标网络的网络属性中的一种。
在一个可能的实施方式中，修改目标网络的运行状态包括挂起目标网络或恢复目标网络。
在一个可能的实施方式中，修改目标网络的网络属性包括修改目标网络的容量、修改目标网络的能力、修改目标网络的配置策略或修改目标网络的服务用户列表中的一种或多种。
在一个可能的实施方式中，请求消息还包括终端设备的用户信息、操作类型对应的操作参数或目标网络的信息中的一种或多种。
在一个可能的实施方式中，用户信息包括用户永久标识、用户组标识或用户临时标识中的一种或多种。
在一个可能的实施方式中，目标网络的信息包括目标网络标识、容量值、能力列表、服务用户列表或配置策略列表中的一种或多种。
在一个可能的实施方式中，收发单元901还用于接收核心网设备发送的应答消息，该应答消息用于指示对目标网络的生命周期操作的结果。
在一个可能的实施方式中，目标网络为用户服务功能实体或其他为用户提供服务的网络功能。
在一个实施例中，图9所示的通信装置可以用于实现上述图3或图8所描述的方法实施例中核心网设备的部分或全部功能。该装置可以是核心网设备，也可以是核心网设备中的装置，或者是能和核心网设备匹配使用的装置。其中，该通信装置还可以为芯片系统。图9所 示的通信装置可以包括收发单元901和处理单元902，其中：
收发单元901，用于接收来自终端设备的请求消息，该请求消息用于对目标网络的生命周期进行操作；该请求消息为终端设备和核心网之间的控制面信令或用户面信令；处理单元902，用于基于该请求消息，对核心网设备管理的目标网络的生命周期进行操作。
在一个可能的实施方式中，请求消息包括操作类型，该操作类型包括创建目标网络、删除目标网络、修改目标网络的运行状态或修改目标网络的网络属性中的一种。
在一个可能的实施方式中，该修改目标网络的运行状态包括挂起目标网络或恢复目标网络。
在一个可能的实施方式中，修改目标网络的网络属性包括修改目标网络的容量、修改目标网络的能力、修改目标网络的配置策略或修改目标网络的服务用户列表中的一种或多种。
在一个可能的实施方式中，处理单元902还用于基于请求消息进行操作鉴权；当操作鉴权的结果为通过时，处理单元902对目标网络的生命周期进行操作；或者，当操作鉴权的结果为不通过时，处理单元902对目标网络的生命周期不进行操作。
在一个可能的实施方式中，处理单元902基于请求消息进行操作鉴权，包括以下一种或多种：根据操作类型，对目标网络的状态进行鉴权；或，对操作类型的操作权限进行鉴权。
在一个可能的实施方式中，若操作类型与目标网络的状态匹配，则处理单元902对目标网络的状态鉴权通过；或者，若操作类型与目标网络的状态不匹配，则处理单元902对目标网络的状态鉴权不通过。
在一个可能的实施方式中，操作类型与目标网络的状态不匹配，包括：操作类型为创建目标网络，目标网络的状态为存在状态；或者，操作类型为删除目标网络，目标网络的状态为不存在状态；或者，操作类型为修改目标网络的网络属性，目标网络的状态为不存在状态；或者，操作类型为修改目标网络的运行状态，目标网络的状态为不存在状态。
在一个可能的实施方式中，存在状态包括挂起状态和激活状态，操作类型为修改目标网络的运行状态，操作类型与目标网络的状态不匹配，还包括：操作类型为挂起目标网络，目标网络的状态为挂起状态；或者，操作类型为恢复目标网络，目标网络的状态为激活状态。
在一个可能的实施方式中，请求消息还包括终端设备的用户信息、操作类型对应的操作参数或目标网络的信息中的一种或多种。
在一个可能的实施方式中，用户信息包括用户永久标识、用户组标识或用户临时标识中的一种或多种。
在一个可能的实施方式中，目标网络的信息包括目标网络标识、容量值、能力列表、服务用户列表或配置策略列表中的一种或多种。
在一个可能的实施方式中，处理单元902基于用户信息，获取用户签约信息；并基于用户签约信息和/或本地配置策略，对操作类型的操作权限进行鉴权。
在一个可能的实施方式中，用户签约信息包括允许的操作动作列表、允许的网络标识列表、允许的网络容量配额、允许的服务用户列表或配置策略列表中的一种或多种。
在一个可能的实施方式中，在操作鉴权的结果为通过的情况下，基于对目标网络的生命周期操作的操作结果，收发单元901向终端设备发送第一应答消息；第一应答消息包括目标网络的状态和目标网络标识；或者，当操作鉴权的结果为不通过的情况下，收发单元901向终端设备发送第二应答消息，第二应答消息用于指示对目标网络的生命周期操作的操作结果为失败。
在一个可能的实施方式中，目标网络为用户服务功能实体或其他为用户提供服务的网络 功能。
关于上述收发单元901和处理单元902更详细的描述，可参考上述方法实施例中终端设备或核心网的相关描述，在此不再说明。
请参见图10，图10为本申请提供的一种通信装置1000的结构示意图，该通信装置1000包括处理器1010和接口电路1020。处理器1010和接口电路1020之间相互耦合。可以理解的是，接口电路1020可以为收发器或输入输出接口。可选的，通信装置1000还可以包括存储器1030，用于存储处理器1010执行的指令或存储处理器1010运行指令所需要的输入数据或存储处理器1010运行指令后产生的数据。
当通信装置1000用于实现上述方法实施例中的方法时，处理器1010用于执行上述处理单元902的功能，接口电路1020用于执行上述收发单元901的功能。
当上述通信装置为应用于终端设备的芯片时，该终端设备芯片实现上述方法实施例中终端设备的功能，该终端设备芯片从其它网元接收信息；或者，该终端设备芯片向其他网元发送信息。
当上述通信装置为应用于核心网的芯片时，该核心网芯片实现上述方法实施例中核心网的功能。该核心网芯片从其它网元接收信息；或者，该核心网芯片向其他网元发送信息。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其它通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现场可编程门阵列(field programmable gate array，FPGA)或者其它可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
本申请的实施例中的方法步骤可以通过硬件的方式来实现，也可以由处理器执行软件指令的方式来实现。软件指令可以由相应的软件模块组成，软件模块可以被存放于随机存取存储器(random access memory，RAM)、闪存、只读存储器(Read-Only Memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于接入网设备或终端设备中。当然，处理器和存储介质也可以作为分立组件存在于终端设备或核心网中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序或指令。在计算机上加载和执行所述计算机程序或指令时，全部或部分地执行本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其它可编程装置。所述计算机程序或指令可以存储在计算机可读存储介质中，或者通过所述计算机可读存储介质进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是集成一个或多个可用介质的服务器等数据存储设备。所述可用介质可以是磁性介质，例如，软盘、硬盘、磁带；也可以是光介质，例如，数字多功能光盘(digital versatile disc，DVD)；还可以是半导体介质，例如，固态硬盘(solid state drive，SSD)。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语 和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
可以理解的是，在本申请的实施例中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的实施例的范围。上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。
本申请实施例还提供一种计算机可读存储介质，该计算机可读存储介质中存储有计算机执行指令，当该计算机执行指令被执行时，使得上述方法实施例中终端设备或核心网执行的方法被实现。
本申请实施例还提供一种计算机程序产品，该计算机程序产品包括计算机程序，当该计算机程序被执行时，使得上述方法实施例中终端设备或核心网执行的方法被实现。
本申请实施例还提供一种通信系统，该通信系统包括终端设备或核心网。其中，终端设备用于执行上述方法实施例中终端设备执行的方法。核心网用于执行上述方法实施例中核心网执行的方法。
需要说明的是，对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本申请并不受所描述的动作顺序的限制，因为依据本申请，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模块并不一定是本申请所必须的。
本申请提供的各实施例的描述可以相互参照，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。为描述的方便和简洁，例如关于本申请实施例提供的各装置、设备的功能以及执行的步骤可以参照本申请方法实施例的相关描述，各方法实施例之间、各装置实施例之间也可以互相参考、结合或引用。
最后应说明的是：以上各实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述各实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分或者全部技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。

Claims (38)

  1. 一种网络资源管理方法，其特征在于，所述方法包括：
    终端设备生成请求消息，所述请求消息用于对目标网络的生命周期进行操作；所述请求消息为所述终端设备和核心网之间的控制面信令或用户面信令；
    所述终端设备向核心网发送所述请求消息；
    所述核心网基于所述请求消息，对所述核心网管理的所述目标网络的生命周期进行操作。
  2. 根据权利要求1所述方法，其特征在于，所述请求消息包括操作类型的信息，所述操作类型包括创建目标网络、删除目标网络、修改目标网络的运行状态或修改目标网络的网络属性中的一种或多种。
  3. 根据权利要求2所述方法，其特征在于，所述修改目标网络的运行状态包括挂起目标网络或恢复目标网络。
  4. 根据权利要求2或3所述方法，其特征在于，所述核心网基于所述请求消息，对所述核心网管理的目标网络的生命周期进行操作，包括：
    所述核心网基于所述请求消息进行操作鉴权；
    当操作鉴权的结果为通过时，所述核心网对所述目标网络的生命周期进行操作。
  5. 根据权利要求4所述方法，其特征在于，所述核心网基于所述请求消息进行操作鉴权，包括以下一种或多种：
    所述核心网根据所述操作类型，对所述目标网络的状态进行鉴权；或，
    所述核心网对所述操作类型的操作权限进行鉴权。
  6. 根据权利要求5所述方法，其特征在于，所述核心网根据所述操作类型，对所述目标网络的状态进行鉴权，包括：
    若所述操作类型与所述目标网络的状态匹配，则所述核心网对所述目标网络的状态鉴权通过。
  7. 根据权利要求6所述方法，所述目标网络的状态包括存在状态或不存在状态，其特征在于，所述操作类型与所述目标网络的状态匹配，包括：
    所述操作类型为创建目标网络，所述目标网络的状态为不存在状态；
    或者，所述操作类型为删除目标网络，所述目标网络的状态为存在状态；
    或者，所述操作类型为修改目标网络的网络属性，所述目标网络的状态为存在状态；
    或者，所述操作类型为修改目标网络的运行状态，所述目标网络的状态为不在状态。
  8. 根据权利要求7所述方法，其特征在于，所述存在状态包括挂起状态或者激活状态，所述操作类型为修改目标网络的运行状态，所述操作类型与所述目标网络的状态匹配，还包括：
    所述操作类型为挂起目标网络，所述目标网络的状态为激活状态；
    或者，所述操作类型为恢复目标网络，所述目标网络的状态为挂起状态。
  9. 根据权利要求5-8中任一项所述方法，其特征在于，所述请求消息还包括所述终端设备的用户信息，所述核心网对所述操作类型的操作权限进行鉴权，包括：
    所述核心网基于所述用户信息，获取用户签约信息；
    所述核心网基于所述用户签约信息和/或本地配置策略，对所述操作类型的操作权限进行鉴权。
  10. 根据权利要求9所述方法，其特征在于，所述用户签约信息包括允许的操作动作列表、允许的网络标识列表、允许的网络容量配额、允许的服务用户列表或配置策略列表中的一种或多种。
  11. 根据权利要求4-10中任一项所述方法，其特征在于，所述方法还包括：
    所述核心网基于对所述目标网络的生命周期操作的操作结果向所述终端设备发送第一应答消息；所述第一应答消息包括所述目标网络的状态或所述目标网络的标识。
  12. 一种网络资源管理方法，其特征在于，所述方法包括：
    终端设备生成请求消息，所述请求消息用于对所述目标网络的生命周期进行操作；所述请求消息为所述终端设备和核心网设备之间的控制面信令或用户面信令；
    所述终端设备向所述核心网设备发送所述请求消息。
  13. 根据权利要求12所述方法，其特征在于，所述请求消息包括操作类型，所述操作类型包括创建目标网络、删除目标网络、修改目标网络的运行状态或修改目标网络的网络属性中的一种。
  14. 根据权利要求13所述方法，其特征在于，所述修改目标网络的运行状态包括挂起目标网络或恢复目标网络。
  15. 根据权利要求12-14中任一项所述方法，其特征在于，所述方法还包括：
    所述终端设备接收所述核心网设备发送的应答消息，所述应答消息用于指示对所述目标网络的生命周期操作的结果。
  16. 一种网络资源管理方法，其特征在于，所述方法包括：
    核心网设备接收来自终端设备的请求消息，所述请求消息用于对所述目标网络的生命周期进行操作；所述请求消息为终端设备和所述核心网之间的控制面信令或用户面信令；
    所述核心网设备基于所述请求消息，对所述核心网设备管理的目标网络的生命周期进行操作。
  17. 根据权利要求16所述方法，其特征在于，所述请求消息包括操作类型，所述操作类型包括创建目标网络、删除目标网络、修改目标网络的运行状态或修改目标网络的网络属性中的一种。
  18. 根据权利要求17所述方法，其特征在于，所述修改目标网络的运行状态包括挂起目标网络或恢复目标网络。
  19. 根据权利要求17或18所述方法，其特征在于，所述基于所述请求消息，对所述核心网设备管理的目标网络的生命周期进行操作，包括：
    所述核心网设备基于所述请求消息进行操作鉴权；
    当操作鉴权的结果为通过时，对所述目标网络的生命周期进行操作。
  20. 根据权利要求19所述方法，其特征在于，所述核心网设备基于所述请求消息进行操作鉴权，包括以下一种或多种：
    核心网设备根据所述操作类型，对所述目标网络的状态进行鉴权；或
    核心网设备对所述操作类型的操作权限进行鉴权。
  21. 根据权利要求20所述方法，其特征在于，所述核心网设备根据所述操作类型，对所述目标网络的状态进行鉴权，包括：
    若所述操作类型与所述目标网络的状态匹配，则所述核心网设备对所述目标网络的状态鉴权通过。
  22. 根据权利要求21所述方法，其特征在于，所述目标网络的状态包括存在状态或不存在状态，所述操作类型与所述目标网络的状态匹配，包括：
    所述操作类型为创建目标网络，所述目标网络的状态为不存在状态；
    或者，所述操作类型为删除目标网络，所述目标网络的状态为存在状态；
    或者，所述操作类型为修改目标网络的网络属性，所述目标网络的状态为存在状态；
    或者，所述操作类型为修改目标网络的运行状态，所述目标网络的状态为存在状态。
  23. 根据权利要求22所述方法，所述存在状态包括挂起状态和激活状态，所述操作类型为修改目标网络的运行状态，所述操作类型与所述目标网络的状态匹配，还包括：
    所述操作类型为挂起目标网络，所述目标网络的状态为激活状态；
    或者，所述操作类型为恢复目标网络，所述目标网络的状态为挂起状态。
  24. 根据权利要求19-23中任一项所述方法，其特征在于，所述请求消息还包括所述终端设备的用户信息，所述核心网设备对所述操作类型的操作权限进行鉴权，包括：
    所述核心网设备基于所述用户信息，获取用户签约信息；
    所述核心网设备基于所述用户签约信息和/或本地配置策略，对所述操作类型的操作权限进行鉴权。
  25. 根据权利要求24所述方法，其特征在于，所述用户签约信息包括允许的操作动作列表、允许的网络标识列表、允许的网络容量配额、允许的服务用户列表或配置策略列表中的一种或多种。
  26. 根据权利要求16-25中任一项所述方法，其特征在于，所述方法还包括：
    所述核心网设备基于对所述目标网络的生命周期操作的操作结果向所述终端设备发送第一应答消息；所述第一应答消息包括所述目标网络的状态。
  27. 根据权利要求2-15或17-25中任一项所述方法，其特征在于，所述修改目标网络的网络属性包括修改目标网络的容量、修改目标网络的能力、修改目标网络的配置策略或修改目标网络的服务用户列表中的一种或多种。
  28. 根据权利要求1-27中任一项所述方法，其特征在于，所述请求消息还包括所述终端设备的用户信息、所述操作类型对应的操作参数或所述目标网络的信息中的一种或多种。
  29. 根据权利要求28所述方法，其特征在于，所述用户信息包括用户永久标识、用户组标识或用户临时标识中的一种或多种。
  30. 根据权利要求28或29所述方法，其特征在于，所述目标网络的信息包括目标网络标识、容量值、能力列表、服务用户列表或配置策略列表中的一种或多种。
  31. 根据权利要求1-30中任一项所述方法，其特征在于，所述目标网络为用户服务功能实体或其他为用户提供服务的网络功能。
  32. 一种通信装置，其特征在于，包括用于执行如权利要求12-15或27-31中任一项所述方法的模块；或者，包括用于执行如权利要求16-31中任一项所述方法的模块。
  33. 一种通信装置，其特征在于，包括处理器，所述处理器与存储器耦合，所述存储器存储指令，所述处理器用于执行所述指令，使得所述通信装置执行如权利要求12-15或27-31任一项所述的方法，或者，使得所述通信装置执行如权利要求16-31任一项所述的方法。
  34. 根据权利要求33所述的通信装置，其特征在于，还包括所述存储器和收发器中的一项或多项，所述收发器用于收发数据和/或信令。
  35. 一种芯片，其特征在于，包括处理器和接口，所述处理器和所述接口耦合；
    所述接口用于接收或输出信号，所述处理器用于执行代码指令，以使权利要求12-15或27-31中任一项所述的方法被执行，或以使权利要求16-31中任一项所述的方法被执行。
  36. 一种通信系统，其特征在于，所述通信系统包括终端设备和核心网设备，所述终端设备用于执行权利要求12-15或27-31中任一项所述的方法；所述核心网设备用于执行权利要求16-31中任一项所述的方法。
  37. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机可执行指令，所述计算机可执行指令在被所述计算机调用时权利要求12-15或27-31中任一项所述的方法被执行，或，所述计算机可执行指令在被所述计算机调用时权利要求16-31中任一项所述的方法被执行。
  38. 一种包括计算机程序的计算机程序产品，当该计算机程序被执行时，使得权利要求12-15或27-31中任一项所述的方法被执行，或，使得权利要求16-31中任一项所述的方法被执行。
PCT/CN2022/140754 2021-12-31 2022-12-21 一种网络资源管理方法及通信装置 WO2023125204A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111682951.8A CN116419176A (zh) 2021-12-31 2021-12-31 一种网络资源管理方法及通信装置
CN202111682951.8 2021-12-31

Publications (1)

Publication Number Publication Date
WO2023125204A1 true WO2023125204A1 (zh) 2023-07-06

Family

ID=86997790

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/140754 WO2023125204A1 (zh) 2021-12-31 2022-12-21 一种网络资源管理方法及通信装置

Country Status (2)

Country Link
CN (1) CN116419176A (zh)
WO (1) WO2023125204A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100153532A1 (en) * 2008-12-15 2010-06-17 Hitachi, Ltd. Network system, network management server, and configuration scheduling method
JP2012090153A (ja) * 2010-10-21 2012-05-10 Nec Corp ネットワーク仮想化システム、ノード、ネットワーク仮想化方法、及び、ネットワーク仮想化プログラム
WO2018059268A1 (zh) * 2016-09-29 2018-04-05 华为技术有限公司 网络切片的建立方法和装置
US20190260690A1 (en) * 2016-11-03 2019-08-22 Huawei Technologies Co., Ltd. Method, apparatus, and system for managing network slice instance
WO2021141348A1 (ko) * 2020-01-06 2021-07-15 삼성전자 주식회사 이동통신 네트워크에서 단일 응용에 복수의 가상 네트워크를 제공하는 방법 및 장치
US20210227353A1 (en) * 2020-01-22 2021-07-22 Nokia Solutions And Networks Oy Logical radio network

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100153532A1 (en) * 2008-12-15 2010-06-17 Hitachi, Ltd. Network system, network management server, and configuration scheduling method
JP2012090153A (ja) * 2010-10-21 2012-05-10 Nec Corp ネットワーク仮想化システム、ノード、ネットワーク仮想化方法、及び、ネットワーク仮想化プログラム
WO2018059268A1 (zh) * 2016-09-29 2018-04-05 华为技术有限公司 网络切片的建立方法和装置
US20190260690A1 (en) * 2016-11-03 2019-08-22 Huawei Technologies Co., Ltd. Method, apparatus, and system for managing network slice instance
WO2021141348A1 (ko) * 2020-01-06 2021-07-15 삼성전자 주식회사 이동통신 네트워크에서 단일 응용에 복수의 가상 네트워크를 제공하는 방법 및 장치
US20210227353A1 (en) * 2020-01-22 2021-07-22 Nokia Solutions And Networks Oy Logical radio network

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "Correction to the UE-initiated resource modification support", 3GPP DRAFT; C3-191106 CORRECTION TO THE UE-INITIATED RESOURCE MODIFICATION SUPPORT(REL-15), 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG3, no. Xi’an, China; 20190408 - 20190412, 1 April 2019 (2019-04-01), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051704272 *

Also Published As

Publication number Publication date
CN116419176A (zh) 2023-07-11

Similar Documents

Publication Publication Date Title
US11690110B2 (en) Time sensitive network bridge configuration
US11950176B2 (en) Parameter of time sensitive network bridge
JP7187580B2 (ja) セッション管理の方法、装置、およびシステム
EP3737172B1 (en) Communication method and device, and system thereof
WO2020224596A1 (zh) 通信方法及装置
JP7214832B2 (ja) サービス品質（ｑｏｓ）のためのセーフガード時間
CN113906717B (zh) 本地用户平面功能控制
WO2019196811A1 (zh) 通信方法和相关装置
US20230254922A1 (en) Multipath transmission method and communication apparatus
WO2020177632A1 (zh) 一种安全保护方法及装置
WO2019029568A1 (zh) 通信方法、终端设备和网络设备
CN110431866B (zh) 控制面连接管理方法和装置
WO2020063316A1 (zh) 通信方法和装置
WO2023125204A1 (zh) 一种网络资源管理方法及通信装置
WO2021042381A1 (zh) 一种通信方法、装置及系统
WO2023125259A1 (zh) 一种网络功能创建方法及通信装置
WO2023125198A1 (zh) 一种网络资源管理方法及通信装置
WO2023137579A1 (zh) 紧急业务的提供方法、装置、设备及存储介质
WO2023066365A1 (zh) 一种通信方法和装置
WO2023143212A1 (zh) 一种通信方法及装置
WO2024098937A1 (zh) 通信方法、通信装置、及存储介质
WO2024027320A1 (zh) 无线通信的方法、装置和系统
WO2022000494A1 (zh) 一种通信方法及装置
WO2023020046A1 (zh) 一种通信方法及通信装置
WO2024146301A1 (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: 22914458

Country of ref document: EP

Kind code of ref document: A1