Network resource management method and communication device

Abstract

The present application provides a network resource management method and a communication device. The network resource management method includes: a terminal device generates a request message, where the request message is used to operate a life cycle of a target network (S301), and the request message is a control plane signaling or a user plane signaling between the terminal device and a core network device. The terminal device sends the request message to the core network device (S302). The core network device operates a life cycle of the target network managed by the core network device based on the request message (S303). In this network resource management method, a user can directly change a target network that provides a network service to the user. Compared with a method in which a user uses an operator to change a target network, the period until the change of the target network takes effect is shortened, thereby improving efficiency.

Description

[Technical field]

[0001] This application claims priority to Chinese Patent Application No. 202111682951.8, entitled "NETWORK RESOURCE MANAGEMENT METHOD AND COMMUNICATION APPARATUS," filed with the State Intellectual Property Office of the People's Republic of China on December 31, 2021, the entire contents of which are incorporated herein by reference.

[0002] [Technical field] The present application relates to the field of communication technologies, and in particular to a network resource management method and a communication device. [Background technology]

[0003] In the process of a user using a mobile network, the mobile network may provide the user with network services (e.g., data transmission services such as voice services), and the user may alternatively interfere with the mobile network to make the mobile network meet the user's current service requirements. For example, in the process of user A using a mobile network, if the charging package of the mobile network is changed, the mobile network will change the mobile network corresponding to user A according to the changed charging package, for example, change parameters such as the transmission speed or capacity of the mobile network.

[0004] Typically, the procedure for a user to interfere with (or modify) a mobile network can be simply described as follows: the user interacts with a mobile network operator about the user requirements, and after understanding the user requirements, the operator modifies the configuration of the mobile network using a business support system (BSS) and an operation support system (OSS) so that the modified mobile network meets the user requirements.

[0005] It turns out that verifying that a user interferes (or modifies) a mobile network with the help of an operator takes a long time and is inefficient. Summary of the Invention

[0006] The embodiments of the present application provide a network resource management method and a communication device, which improves network resource management efficiency.

[0007] According to a first aspect, an embodiment of the present application provides a network resource management method, in which a terminal device determines a request message, where the request message is used to operate a life cycle of a target network, and the request message is a control plane signaling or a user plane signaling between the terminal device and a core network. The terminal device sends the request message to the core network. The core network operates a life cycle of the target network managed by the core network based on the request message.

[0008] Based on the method described in the first aspect, a user can directly operate a target network that provides user services based on control plane signaling or user plane signaling between the user and the core network. Compared with a method in which a user operates a target network via an operator network, the period until the operation takes effect can be shortened, thereby improving the efficiency of operating the target network.

[0009] In a possible implementation, the target network is a user service function entity or another network function that provides a service to the user. When this possible implementation is implemented, the terminal device may directly operate the user service function entity or another network function that provides a service to the user based on control plane signaling or user plane signaling between the terminal device and the core network.

[0010] In a possible implementation, the target network includes a network function that provides network services to an end device, a virtual machine or group of virtual machines, a container, a process, or another set of executable resources.

[0011] In a possible implementation, the request message includes information about an operation type, and the operation type includes one of creating a target network, deleting a target network, changing a running state of the target network, or changing a network attribute of the target network. When this possible implementation is implemented, the terminal device may perform the operation of creating a target network, the operation of deleting a target network, the operation of changing a running state, and the operation of changing a network attribute based on control plane signaling or user plane signaling between the terminal device and the core network.

[0012] In a possible implementation, changing the running state of the target network includes pausing the target network or resuming the target network. When this possible implementation is implemented, the terminal device may update the running state of the target network based on a user requirement. For example, when the terminal device does not temporarily need the target network to provide a network service, the terminal device may choose to pause the target network to reduce system power consumption. When the terminal device needs the target network to provide a network service, the terminal device chooses to resume the target network to meet the user requirement.

[0013] In a possible implementation, modifying the network attributes of the target network includes one or more of modifying the capacity of the target network, modifying the capability of the target network, modifying the configuration policy of the target network, or modifying the service user list of the target network. When this possible implementation is implemented, the terminal device may modify the network attributes of the target network based on the user requirements so that the target network better meets the user requirements.

[0014] In a possible implementation form, the core network performs an operation authentication based on the request message. When the result of the operation authentication indicates success, the core network operates the life cycle of the target network. Alternatively, when the result of the operation authentication indicates failure, the core network does not operate the life cycle of the target network. When this possible implementation form is implemented, the core network operates the life cycle of the target network based on a request from the terminal device only when the result of the operation authentication indicates success, which can improve system security.

[0015] In a possible implementation, the core network device authenticates the status of the target network based on the operation type. Alternatively, the core network authenticates the operation permission of the operation type. When this possible implementation is implemented, the core network avoids the case where it performs an invalid operation based on the error request message sent by the terminal device, thereby reducing system power consumption.

[0016] In a possible implementation, if the operation type matches the status of the target network, the core network successfully authenticates the status of the target network.

[0017] In a possible implementation, if the operation type does not match the status of the target network, the core network fails to authenticate the status of the target network.

[0018] When the above possible implementation form is implemented, the match between the operation type and the status of the target network is used as a filtering condition to avoid the case where the core network still needs to perform an operation that is invalid for the lifecycle of the target network based on the error request message after the terminal device sends the error request message, thereby reducing power consumption.

[0019] In a possible implementation, the status of the target network includes a present state and a non-present state, and the operation type not matching the status of the target network includes: the status of the target network being present when the operation type is to create the target network, the status of the target network being non-present when the operation type is to delete the target network, the status of the target network being non-present when the operation type is to change the network attributes of the target network, or the status of the target network being non-present when the operation type is to change the running state of the target network.

[0020] In a possible implementation, the status of the target network includes a present state and a non-present state, and the operation type matching the status of the target network includes: when the operation type is to create the target network, the status of the target network is a non-present state; when the operation type is to delete the target network, the status of the target network is a present state; when the operation type is to change the network attributes of the target network, the status of the target network is a present state; or when the operation type is to change the running state of the target network, the status of the target network is a present state.

[0021] The above possible implementations provide some specific examples where the operation type does not match (or matches) the status of the target network.

[0022] In a possible implementation, the presence state includes a paused state or an activated state, and when the operation type is to change the running state of the target network, the operation type not matching the status of the target network further includes: when the operation type is to pause the target network, the status of the target network is in a paused state, or when the operation type is to resume the target network, the status of the target network is in an activated state.

[0023] In a possible implementation, the presence state includes a paused state or an activated state, and when the operation type is to change the running state of the target network, the operation type matching the status of the target network further includes: when the operation type is to pause the target network, the status of the target network is an activated state, or when the operation type is to resume the target network, the status of the target network is a paused state.

[0024] The above possible implementations provide some specific examples where the operation type does not match (or matches) the status of the target network.

[0025] In a possible implementation, the core network includes a first functional network element and a second functional network element, and a communication connection exists between the first functional network element and the second functional network element. The first functional network element is configured to perform an operation authentication based on the request message. The second functional network element is configured to operate a life cycle of the target network when a result of the operation authentication indicates success. When this possible implementation is implemented, a specific architecture of a core network device that operates the target network is provided.

[0026] In a possible implementation, after the first functional network element performs operation authentication based on the request message, when the result of the operation authentication indicates success, the first functional network element sends an instruction message (or a second request message) to the second functional network element, and the instruction message (or the second request message) is for requesting the second functional network element to operate the life cycle of the target network. When this possible implementation is implemented, the second functional network element operates the life cycle of the target network only after receiving the instruction message (or the second request message) from the first functional network element, thereby enhancing the stability of the target network.

[0027] In a possible implementation, the instruction message (or the second request message) includes an operation type or an operation parameter corresponding to the operation type. When this possible implementation is implemented, the second functional network element may use the instruction message (or the second request message) to perform a specific operation on the life cycle of the target network, so that the target network better meets the user requirements.

[0028] In a possible implementation, the second functional network element performs identity authentication on the first functional network element. After the identity authentication on the first functional network element is successful, the second functional network element operates the life cycle of the target network. When this possible implementation is implemented, before the second functional network element operates the life cycle of the target network, the second functional network element performs identity authentication on the first functional network element. Functional Network Elements may perform identity authentication to the first functional network element, thereby improving security of the target network.

[0029] In a possible implementation, the request message further includes one or more of user information of the terminal device, operation parameters corresponding to the operation type, or information about the target network. When the possible implementation is implemented, the core network may operate the target network based on the user information, the operation parameters corresponding to the operation type, or information about the target network.

[0030] In a possible implementation, the user information includes one or more of a subscription persistent identifier, a user group identifier, or a temporary user identifier.

[0031] In a possible implementation, the information about the target network includes one or more of the following: an identifier of the target network, a capacity value, a capability list, a service user list, or a configuration policy list.

[0032] In a possible implementation, the request message further includes user information of the terminal device, and the core network obtains user subscription information based on the user information. The core network authenticates operation permission of the operation type based on the user subscription information and / or according to a local configuration policy. When this possible implementation is implemented, a case is avoided in which the core network still performs an invalid operation for the target network life cycle based on the request message when the terminal device does not have operation permission corresponding to the operation type, thereby reducing power consumption.

[0033] In a possible implementation, the user subscription information includes one or more of an authorized operation action list, an authorized network identifier list, an authorized network capacity allocation, an authorized service user list, or a configuration policy list. When this possible implementation is implemented, the operation permission of the terminal device is restricted using the user subscription information, so that the operation permission of the terminal device is authenticated based on the user subscription information.

[0034] In a possible implementation form, when the result of the operation authentication indicates success, the core network sends a first response message to the terminal device based on the operation result of operating the life cycle of the target network, and the first response message includes the status of the target network or an identifier of the target network.

[0035] In a possible implementation, when the result of the operation authentication indicates failure, the core network sends a second response message to the terminal device, and the second response message indicates that the operation result of operating the life cycle of the target network indicates failure. When this possible scheme is implemented, the core network feeds back the operation result of operating the life cycle of the target network to the terminal device. For the user, operating the target network through the core network is more open and transparent, improving the user experience.

[0036] According to a second aspect, an embodiment of the present application provides a network resource management method, in which a terminal device determines a request message, where the request message is used to operate a life cycle of a target network, and the request message is a control plane signaling or a user plane signaling between the terminal device and a core network device. The terminal device sends the request message to the core network device.

[0037] Based on the network resource management method provided in the second aspect, for the beneficial effects of the network resource management method, please refer to the beneficial effects of the network resource management method provided in the first aspect. The repeated parts will not be described again here.

[0038] In a possible implementation, the request message includes information regarding an operation type, the operation type including one of creating the target network, deleting the target network, changing the running state of the target network, or changing network attributes of the target network.

[0039] In a possible implementation, changing the execution state of the target network includes pausing the target network or resuming the target network.

[0040] In a possible implementation, modifying the network attributes of the target network includes one or more of modifying the capacity of the target network, modifying the capabilities of the target network, modifying a configuration policy of the target network, or modifying a service user list of the target network.

[0041] In a possible implementation, the request message further includes one or more of user information of the terminal device, operation parameters corresponding to the operation type, or information about the target network.

[0042] In a possible implementation, the user information includes one or more of a subscription persistent identifier, a user group identifier, or a temporary user identifier.

[0043] In a possible implementation, the information about the target network includes one or more of the following: an identifier of the target network, a capacity value, a capability list, a service user list, or a configuration policy list.

[0044] In a possible implementation, the terminal device receives a response message sent by the core network device, where the response message indicates the result of operating the life cycle of the target network.

[0045] In a possible implementation, the target network is a user service function entity or another network function that provides a service to the user.

[0046] In a possible implementation, the target network includes a network function that provides network services to an end device, a virtual machine or group of virtual machines, a container, a process, or another set of executable resources.

[0047] According to a third aspect, an embodiment of the present application provides a network resource management method, in which a core network device receives a request message from a terminal device, where the request message is used to operate a life cycle of a target network, and the request message is a control plane signaling or a 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.

[0048] Based on the network resource management method provided in the third aspect, for the beneficial effects of the network resource management method, please refer to the beneficial effects of the network resource management method provided in the first aspect. The repeated parts will not be described again here.

[0049] In a possible implementation, the request message includes information regarding an operation type, the operation type including one of creating the target network, deleting the target network, changing the running state of the target network, or changing network attributes of the target network.

[0050] In a possible implementation, changing the execution state of the target network includes pausing the target network or resuming the target network.

[0051] In a possible implementation, modifying the network attributes of the target network includes one or more of modifying the capacity of the target network, modifying the capabilities of the target network, modifying a configuration policy of the target network, or modifying a service user list of the target network.

[0052] In a possible implementation, the core network device performs operation authentication based on the request message. When the result of the operation authentication indicates success, the core network device operates the life cycle of the target network. Alternatively, when the result of the operation authentication indicates failure, the core network device does not operate the life cycle of the target network.

[0053] In a possible implementation, the core network device performing operation authentication based on the request message includes one or more of the following: authenticating the status of the target network based on the operation type, or authenticating operation permission for the operation type.

[0054] In a possible implementation, if the operation type matches the status of the target network, the core network device successfully authenticates the status of the target network, or if the operation type does not match the status of the target network, the core network device fails to authenticate the status of the target network.

[0055] In a possible implementation, the status of the target network includes a present state or a non-present state, and the operation type matching the status of the target network includes: the status of the target network being non-present when the operation type is to create the target network, the status of the target network being present when the operation type is to delete the target network, the status of the target network being present when the operation type is to change the network attributes of the target network, or the status of the target network being present when the operation type is to change the running state of the target network.

[0056] In a possible implementation, the presence state includes a paused state or an activated state, and when the operation type is to change the running state of the target network, the operation type matching the status of the target network further includes: when the operation type is to pause the target network, the status of the target network is an activated state, or when the operation type is to resume the target network, the status of the target network is a paused state.

[0057] In a possible implementation, the request message further includes one or more of user information of the terminal device, operation parameters corresponding to the operation type, or information about the target network.

[0058] In a possible implementation, the user information includes one or more of a subscription persistent identifier, a user group identifier, or a temporary user identifier.

[0059] In a possible implementation, the information about the target network includes one or more of the following: an identifier of the target network, a capacity value, a capability list, a service user list, or a configuration policy list.

[0060] In a possible implementation, the core network device obtains user subscription information based on the user information, and authorizes operation permissions for the operation type based on the user subscription information and / or according to a local configuration policy.

[0061] In a possible implementation, the user subscription information includes one or more of an authorized operational action list, an authorized network identifier list, an authorized network capacity allocation, an authorized service user list, or a configuration policy list.

[0062] In a possible implementation, when the result of the operation authentication indicates success, the core network device sends a first response message to the terminal device based on the operation result of operating the life cycle of the target network, the first response message including the status of the target network and the identifier of the target network. Alternatively, when the result of the operation authentication indicates failure, the core network device sends a second response message to the terminal device, the second response message indicating that the operation result of operating the life cycle of the target network indicates failure.

[0063] In a possible implementation, the target network is a user service function entity or another network function that provides a service to the user.

[0064] According to a fourth aspect, the present application provides a communication device. The device may be a terminal device, a chip, chip system, processor, etc. that supports the terminal device in implementing the aforementioned method, or a logic module, unit, or software that can implement all or part of the functions of the terminal device. Alternatively, the communication device may be a chip system. The communication device includes: a processing unit configured to determine a request message, where the request message is used to operate a life cycle of a target network, where the request message is a control plane signaling or a user plane signaling between the terminal device and a core network device, and a transceiver unit configured to transmit the request message to the core network device.

[0065] Based on the network resource management method provided in the fourth aspect, for the beneficial effects of the network resource management method, please refer to the beneficial effects of the network resource management method provided in the first aspect or the second aspect. The repeated parts will not be described again here.

[0066] In a possible implementation, the request message includes information regarding an operation type, and the operation type is one of creating a target network, deleting a target network, or modifying network attributes of the target network.

[0067] In a possible implementation, the action types further include pausing the target network or resuming the target network.

[0068] In a possible implementation, modifying the network attributes of the target network includes one or more of modifying the capacity of the target network, modifying the capabilities of the target network, modifying a configuration policy of the target network, or modifying a service user list of the target network.

[0069] In a possible implementation, the request message further includes one or more of user information of the terminal device, operation parameters corresponding to the operation type, or information about the target network.

[0070] In a possible implementation, the user information includes one or more of a subscription persistent identifier, a user group identifier, or a temporary user identifier.

[0071] In a possible implementation, the information about the target network includes one or more of the following: an identifier of the target network, a capacity value, a capability list, a service user list, or a configuration policy list.

[0072] In a possible implementation, the transceiver unit is further configured to receive a response message sent by the core network device, the response message indicating a result of operating the life cycle of the target network.

[0073] In a possible implementation, the target network is a user service function entity or another network function that provides a service to the user.

[0074] According to a fifth aspect, the present application provides another communication device. The device may be a core network device, a chip, chip system, processor, etc. supporting the core network device in implementing the aforementioned method, or a logic module, unit, or software capable of implementing all or part of the functionality of the core network. Alternatively, the communication device may be a chip system. The communication device includes a transceiver unit configured to receive a request message from a terminal device, the request message being used to operate a life cycle of the target network, the request message being a control plane signaling or a user plane signaling between the terminal device and the core network device, and a processing unit configured to operate a life cycle of the target network managed by the core network device based on the request message.

[0075] In a possible implementation, the request message includes information regarding an operation type, and the operation type is one of creating a target network, deleting a target network, or modifying network attributes of the target network.

[0076] In a possible implementation, the action types further include pausing the target network or resuming the target network.

[0077] In a possible implementation, modifying the network attributes of the target network includes one or more of modifying the capacity of the target network, modifying the capabilities of the target network, modifying a configuration policy of the target network, or modifying a service user list of the target network.

[0078] In a possible implementation, the processing unit is further configured to perform operation authentication based on the request message. When the result of the operation authentication indicates success, the processing unit executes a life cycle of the target network. Alternatively, when the result of the operation authentication indicates failure, the processing unit does not execute a life cycle of the target network.

[0079] In a possible implementation, the processing unit performing operation authentication based on the request message includes one or more of the following: authenticating the status of the target network based on the operation type, or authenticating operation permission for the operation type.

[0080] In a possible implementation, if the operation type matches the status of the target network, the processing unit successfully authenticates the status of the target network, or if the operation type does not match the status of the target network, the processing unit fails to authenticate the status of the target network.

[0081] In a possible implementation, the status of the target network includes a present state or a non-present state, and the operation type matching the status of the target network includes the status of the target network being non-present when the operation type is to create the target network, the status of the target network being present when the operation type is to delete the target network, or the status of the target network being present when the operation type is to change network attributes of the target network.

[0082] In a possible implementation, the operation type not matching the status of the target network further includes: when the operation type is to pause the target network, the status of the target network is non-existent or paused, or when the operation type is to resume the target network, the status of the target network is non-existent or activated.

[0083] In a possible implementation, the request message further includes one or more of user information of the terminal device, operation parameters corresponding to the operation type, or information about the target network.

[0084] In a possible implementation, the user information includes one or more of a subscription persistent identifier, a user group identifier, or a temporary user identifier.

[0085] In a possible implementation, the information about the target network includes one or more of the following: an identifier of the target network, a capacity value, a capability list, a service user list, or a configuration policy list.

[0086] In a possible implementation, the processing unit obtains user subscription information based on the user information, and authorizes operation permission for the operation type based on the user subscription information and / or according to a local configuration policy.

[0087] In a possible implementation, the user subscription information includes one or more of an authorized operational action list, an authorized network identifier list, an authorized network capacity allocation, an authorized service user list, or a configuration policy list.

[0088] In a possible implementation, when the result of the operation authentication indicates success, the transceiver unit sends a first response message to the terminal device based on the operation result of operating the life cycle of the target network, the first response message including a status of the target network and an identifier of the target network. Alternatively, when the result of the operation authentication indicates failure, the transceiver unit sends a second response message to the terminal device, the second response message indicating that the operation result of operating the life cycle of the target network indicates failure.

[0089] In a possible implementation, the target network is a user service function entity or another network function that provides a service to the user.

[0090] According to a sixth aspect, the present application provides a communication device. The communication device may be a terminal device in the aforementioned method embodiment, or a chip disposed in the terminal device. The communication device includes a communication interface and a processor, and optionally further includes a memory. The memory is configured to store a computer program or instruction. The processor is coupled to the memory and the communication interface. When the processor executes the computer program or instruction, the communication device is capable of executing the method performed by the terminal device in the aforementioned method embodiment.

[0091] According to a seventh aspect, the present application provides a communication device. The communication device may be a core network device in the aforementioned method embodiment, or a chip disposed in the core network device. The communication device includes a communication interface and a processor, and optionally further includes a memory. The memory is configured to store a computer program or instruction. The processor is coupled to the memory and the communication interface. When the processor executes the computer program or instruction, the communication device is enabled to execute the method performed by the core network device in the aforementioned method embodiment.

[0092] According to an eighth aspect, the present application provides a computer-readable storage medium configured to store computer-executable instructions which, when executed, perform a method performed by a terminal device in the method according to the first aspect or the second aspect, or perform a method performed by a core network device in the method according to the first aspect or the third aspect.

[0093] According to a ninth aspect, the present application provides a computer program product comprising a computer program which, when executed, performs a method performed by a terminal device in the method according to the first aspect or the second aspect, or performs a method performed by a core network device in the method according to the first aspect or the third aspect.

[0094] According to a tenth aspect, the present application provides a communication system, the communication system comprising a communication device according to the fourth aspect and the fifth aspect, or comprising a communication device according to the sixth aspect and the seventh aspect. [Brief description of the drawings]

[0095] [Figure 1a] FIG. 1 is a schematic diagram of a network system architecture according to an embodiment of the present application. [Figure 1b] FIG. 2 is a schematic diagram of the structure of a core network according to an embodiment of the present application; [Figure 1c] FIG. 2 is a schematic diagram of another core network architecture according to an embodiment of the present application; [Diagram 2] 1 is a schematic diagram of the structure of a user-centric network according to an embodiment of the present application; [Diagram 3] FIG. 2 is a schematic interaction diagram of a network resource management method according to an embodiment of the present application; [Figure 4a]FIG. 2 is a schematic interaction diagram of creating a target network according to an embodiment of the present application; [Figure 4b] FIG. 13 is another schematic interaction diagram of creating a target network according to an embodiment of the present application; [Figure 5a] FIG. 2 is a schematic interaction diagram of deleting a target network according to an embodiment of the present application; [Figure 5b] FIG. 13 is another schematic interaction diagram of deleting a target network according to an embodiment of the present application; [Figure 6a] FIG. 2 is a schematic interaction diagram of modifying network attributes of a target network according to an embodiment of the present application; [Figure 6b] FIG. 2 is another schematic interaction diagram of modifying network attributes of a target network according to an embodiment of the present application; [Figure 7] FIG. 2 is a schematic interaction diagram of another network resource management method according to an embodiment of the present application; [Figure 8] FIG. 13 is a schematic interaction diagram of yet another network resource management method according to an embodiment of the present application; [Figure 9] 1 is a schematic diagram of a structure of a communication device according to an embodiment of the present application; [Figure 10] 1 is a schematic diagram of the structure of another communication device according to an embodiment of the present application; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0096] In the following, specific embodiments of the present application are further described in detail with reference to the accompanying drawings.

[0097] The terms "first", "second", etc. in the specification, claims, and accompanying drawings of this application are not used to describe a particular order, but to distinguish different objects. In addition, the terms "including" and "having" and any other variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, and optionally includes additional steps or units that are not listed, or optionally includes additional steps or units that are specific to the process, method, product, or device.

[0098] An "embodiment" referred to in this specification indicates that a particular feature, structure, or characteristic described with reference to this embodiment may be included in at least one embodiment of the present application. Phrases appearing in various places in this specification do not necessarily refer to the same embodiment, and are not independent or optional embodiments exclusive of another embodiment. It is explicitly and implicitly understood by those skilled in the art that the embodiments described in this specification may be combined with another embodiment.

[0099] In this application, "at least one (item)" means one or more, "a plurality" means two or more, "at least two (items)" means two or more, and "and / or" is used to describe an associative relationship between related objects, indicating that three relationships may exist. For example, "A and / or B" may indicate that only A is present, that only B is present, and that both A and B are present. A and B may be singular or plural. The character " / " typically indicates an "or" relationship between related objects. "At least one of the following items" or similar phrases means any combination of these items, including any combination of singular items or plural items. For example, at least one of a, b, or c may indicate a, b, c, "a and b," "a and c," "b and c," or "a, b, and c," where a, b, and c may be singular or plural.

[0100] In order to better understand the embodiment of the present application, the following first describes the system architecture in the embodiment of the present application.

[0101] The technical solutions in the embodiments of the present application may be applied to various communication systems, for example, a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD) system, a new radio (NR) system, a 5th generation (5G) communication system such as a 3rd generation partner project (3GPP) service-based architecture (SBA), or a communication system evolved beyond 5G, such as a 6th generation (6G) communication system.

[0102] FIG. 1a is a schematic diagram of a network system architecture according to an embodiment of the present application. As shown in FIG. 1a, a terminal device may access a wireless network and obtain a service of an external network (e.g., a data network (DN)) through the wireless network, or may communicate with another device, e.g., another terminal device, through the wireless network. The wireless network includes a (radio) access network ((R)AN) and a core network (CN). The (R)AN (hereinafter described as RAN) is configured to connect the terminal device to the wireless network, and the CN is configured to provide a gateway for managing the terminal device and communicating with the DN. In the following, the terminal device, the RAN, the CN, and the DN in the system architecture of FIG. 1a are specifically described separately.

[0103] I. Terminal Devices

[0104] The terminal device includes a device that provides voice and / or data connectivity to a user. For example, the terminal device is a device with a wireless transceiver function, and may be deployed on the ground, such as an indoor or outdoor device, a handheld device, a wearable or an in-vehicle device, or may be deployed on the water surface (e.g., on a ship) or in the air (e.g., on an airplane, a balloon, or a satellite). The terminal device may be a mobile phone, a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, an in-vehicle terminal, a wireless terminal in self driving, a wireless terminal in remote medical, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a wearable terminal, etc. The application scenario is not limited to the embodiments of this application. The terminal device may also be referred to as a terminal, user equipment (UE), access terminal, in-vehicle terminal, terminal in industrial control, UE unit, UE station, mobile station, remote station, remote terminal, mobile device, UE terminal, wireless communication device, UE proxy, UE device, etc. The terminal may alternatively be fixed or mobile. It may be understood that all or part of the functions of the terminal in this application may alternatively be implemented using software functions executed on hardware or using virtualization functions instantiated on a platform (e.g., a cloud platform).

[0105] II.RAN

[0106] 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). Indeed, in communications evolved beyond 5G, the names of these interfaces may remain unchanged or may be replaced by other names. This is not limited in this application.

[0107] An access network device is a node or device that connects a terminal device to a wireless network. Examples of access network devices include, but are not limited to, a next generation NodeB (gNB), evolved NodeB (eNB), next generation evolved NodeB (ng-eNB), wireless backhaul device, radio network controller (RNC), NodeB (NB), home evolved NodeB (HeNB) or (HNB), baseband unit (BBU), transmission reception point (TRP), transmission point (TP), mobile switching center, or a device that functions as a base station in device-to-device (D2D), vehicle-to-everything (V2X), or machine-to-machine (M2M) communications, or a central unit (C-RAN) in a cloud radio access network (C-RAN) system. The present application is not particularly limited to the embodiments, and may include a network device in a non-terrestrial network (NTN) communication system, which may be deployed on a high altitude platform or a satellite, and the like.

[0108] III.CN

[0109] A CN may include one or more CN devices (which may be understood as network element devices or functional network elements).

[0110] FIG. 1b is a schematic diagram of the structure of a CN according to the present application. The CN in FIG. 1b is a schematic diagram of a CN in a 5G network architecture. The CN shown in FIG. 1b includes multiple CN devices, namely, a network slice selection function (NSSF), a network exposure function (NEF), a network repository function (NRF), and a network slice selection function (NSSF). r The network slice includes an application repository function (NRF), a policy control function (PCF), a unified data management (UDM), an application function (AF), a network control function (NCF), a network slice-specific authentication and authorization function (NSSAAF), an authentication server function (AUSF), an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a service communication proxy (SCP), and a network slice admission control function (NSACF).

[0111] The AMF is a control plane function provided by an operator network and is responsible for access control and mobility management for access to the operator network by terminal devices, including functions such as mobility status management, temporary user identity allocation, and user authentication and authorization.

[0112] The SMF is a control plane function provided by an operator network and configured to manage protocol data unit (PDU) sessions of terminal devices. A PDU session is a channel used to transmit PDUs, and a terminal device needs to transmit PDUs to a DN through a PDU session. The SMF is responsible for the establishment, maintenance, deletion, etc. of PDU sessions. The SMF includes session-related functions such as session management (e.g., session establishment, modification, and release, including tunnel management between the UPF and the RAN), UPF selection and control, service and session continuity (SSC) mode selection, and roaming.

[0113] The PCF is a control plane function provided by an operator, including user subscription data management function, policy control function, charging policy control function, quality of service (QoS) control, etc., and is mainly configured to provide PDU session policies for the SMF. The policies may include charging-related policies, QoS-related policies, authorization-related policies, etc.

[0114] The UPF is a gateway provided by an operator for communication between the operator network and the DN. The 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.

[0115] The UDM is mainly configured to manage subscription data and authentication data of users, and perform authentication credit processing, user identity processing, access authorization, registration / mobility management, subscription management, short message service management, etc. In some embodiments, the UDM may further include a unified data repository (UDR). Alternatively, in some other embodiments, the 3GPP SBA in the 5G system may further include a UDR. The UDR is configured to store and retrieve PCF policies, store and retrieve structured data for publishing, store user information required by application functions, etc.

[0116] The CN device may also be referred to as a network element or a functional network element. In a 5G communication system, the functional network element may be the name of the functional network element shown in FIG. 1b. In a communication system evolved beyond 5G (e.g., a 6G communication system), the functional network element may still be the name of the functional network element shown in FIG. 1b, or may have another name. For example, in a 5G communication system, the policy control network element may be a PCF. In a communication system evolved beyond 5G (e.g., a 6G communication system), the policy control function may still be a PCF, or may have another name. This is not limited in the present application.

[0117] In Figure 1b, Npcf, Nudm, Naf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface sequence numbers. For the meaning of these interface serial numbers, please refer to the meaning defined in the relevant standard protocol, which is not limited in this specification.

[0118] FIG. 1c is a schematic diagram of another CN architecture according to the present application. In FIG. 1c, the CN includes a user network access function, a user subscription authentication function, a network control function, and a resource management function. The user network access function is configured to perform access control and mobility management for terminal devices. The user subscription authentication function is configured to store and manage subscription information of users. The network control function is configured to manage user network resources, and is responsible for operations such as creating, modifying, and deleting user networks. The resource management function is configured to manage network resources, and is configured to allocate resources, for example, to create network function instances required by the user network. The user network is used to provide network services to one or more users, and can be understood as a core network element for UE dedicated services. For example, the user network may include one or more network elements, and may be a network element dedicated to a user, or may be a network element shared with another user. When the user network includes one network element, the user network may be a network element, and the network element may be a user network. Specifically, the user network may be a network function that provides network services to terminal devices, and may be a virtual machine or a group of virtual machines, a container, a process, or another set of executable resources. In the following, the user network is used as an example for explanation.

[0119] For example, the user network may be a USN, which may be understood as an integration of core network control functions and is a core network element for UE dedicated services. For example, the USN may be responsible for session management (SM) and / or policy management (SM). policyAlternatively, the USN may be understood as a digital twin function of the UE in the core network, which is a digital model for the actual behavior of the UE, and has functions such as recording service information used by the UE, artificial intelligence (AI) processing, etc. Alternatively, the USN may be understood as something similar to a cloud server (cloud computer). The UE may orchestrate resources provided by the operator on the cloud server, such as QoS settings and bandwidth allocation of different services. It should be noted that the USN may be integrated into the 5G network architecture shown in FIG. 1b or into the CN architecture shown in FIG. 1c. In a possible implementation, the USN may be used as a newly added logical network element or may be integrated into the existing network functions of FIG. 1b or FIG. 1c as a logical function. For example, the USN may be integrated into the AMF and SMF. The USN may alternatively exist in the form of a user-centric network (UCN) architecture. In this case, the UCN architecture may be understood as a user-centric network. Please refer to the UCN network architecture shown in Figure 2. The UCN network architecture shown in Figure 2 includes a network service node (NSN) and a user service node (USN). The main functions of the NSN include authentication, USN creation, and life cycle management of the accessed UE.

[0120] The NCF is configured to manage USN resources in the UCN network architecture, and is responsible for operations such as creating, modifying, and deleting USNs.

[0121] It should be understood that the NSN, USN, and NCF in this application are merely exemplary names and should not be considered as specific limitations thereon. In other words, the NSN, USN, and NCF may use other names in other technical solutions other than this application, or may be other communication devices having the same functions. For example, the NSN may be an access control function, the NCF may be a network resource control or management function, and the USN may be a terminal digital twin function.

[0122] It should be noted that: 1. The CN structure shown in FIG. 1c is merely for facilitating the understanding of the CN, and only an example in which each functional network element is deployed separately in the CN is used. In some possible CN structures, the functional network elements may be integrated and combined for deployment. For example, the network access function and the user subscription authentication function in FIG. 1c are integrated into the same functional network element, or the network access function and the network control function in FIG. 1c are integrated into the same functional network element. This is not particularly limited in this application. 2. The core network referred to below in this application may be a functional network element in the core network, may be an integration of some functional network elements in the core network, or may be an integration of all functional network elements in the core network. The core network may be a core network in the 5G communication system shown in FIG. 1b, may be a core network shown in FIG. 1c, or may be another possible communication system (e.g., a core network in an LTE communication system or a communication system evolved beyond 5G). 3. The aforementioned network elements or functions may be network elements in a hardware device, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). Optionally, the network elements or functions may be implemented by one device, may be implemented jointly by multiple devices, or may be functional modules in one device. This is not particularly limited in the embodiments of the present application.

[0123] IV.DN

[0124] A DN, also called a packet data network (PDN), is a network located outside an operator network. An operator network may access multiple DNs. To provide multiple possible services to a terminal device, application servers corresponding to multiple services may be deployed in the DN.

[0125] Usually, the procedure for a user to change a user network can be simply described as follows: the user interacts with a mobile network operator regarding user requirements, and after understanding the user requirements, the operator changes the configuration of the user network using the BSS and OSS so that the changed user network meets the user requirements. However, this method usually takes a long time to verify the user network changed by the user, and is low in efficiency.

[0126] The present application provides a network resource management method, in which a user may use control plane signaling (or user plane signaling) between a terminal device and a core network to carry a request message for operating a target network and change a target network that provides a network service to the user. Compared with a method in which a user uses an operator to change a target network, the time period until the change of the target network takes effect is shortened, thereby improving efficiency.

[0127] The network resource management method and communication device provided in the present application are further described below with reference to the accompanying drawings.

[0128] Figure 3 is a schematic flowchart of a network resource management method according to an embodiment of the present application. As shown in Figure 3, the network resource management method may be performed by a core network device or a chip in the core network device, or may be performed by a terminal device or a chip in the terminal device. Figure 3 is described using an example in which the core network device and the terminal device are entities for performing the method.

[0129] S301: A terminal device determines a request message, where the request message is used to operate a life cycle of a target network.

[0130] The terminal device determines (or generates) a request message for requesting to operate the life cycle of the target network based on a user requirement. Operating the life cycle of the target network includes creating the target network and deleting the target network. In other words, the terminal device may determine the request message used to create the target network, or may determine the request message used to delete the target network.

[0131] In a possible implementation, the target network may have multiple statuses, including a presence state and a non-presence state. It should be understood that the target network status being a presence state means that the target network is present, and the target network status being a non-presence state means that the target network is not present.

[0132] In a possible implementation, the status of the target network being in a presence state includes the running state of the target network being in a paused state (also referred to as a standby state, a to-be-activated state, a deactivated state, etc.) or the running state of the target network being in an activated state. In this case, operating the life cycle of the target network may further include changing the running state of the target network. Changing the running state of the target network includes pausing the target network, e.g., changing the running state of the target network from an activated state to a paused state, or resuming (or activating) the target network, e.g., changing the running state of the target network from a paused state to an activated state. In a possible implementation, changing the running state of the target network may further include changing the running state of the target network to a normal running state when the running state of the target network is in an abnormal (or failed) state.

[0133] In a possible implementation, the target network further includes a number of network attributes, including, but not limited to, one or more of capacity (i.e., capacity-related parameters), capabilities (i.e., network capability-related parameters), configuration policies, or service user lists. In this case, operating the life cycle of the target network may further include modifying the network attributes of the target network.

[0134] It should be noted that the target network referred to in this application is a network function (NF) configured to provide a network service to a terminal device, a virtual machine or a group of virtual machines, a container, a process, or another set of executable resources. The network service includes, but is not limited to, one or more of data download, data access, and phone call. In other words, the target network may be a user service function entity or another network function that provides a service to a user. For example, the target network may be a USN network element or a USN function entity.

[0135] In a possible implementation, the request message includes information regarding an operation type, and the operation type is one of creating the target network, deleting the target network, pausing the target network, resuming the target network, or modifying network attributes of the target network.

[0136] Creating a target network is to generate (or establish) from scratch a target network that provides a network service to a terminal. Deleting a target network is to delete a connection relationship of the target network (e.g., a connection relationship between the target network and an access network device) and delete resources (e.g., running resources) occupied by the target network. Suspending a target network is to set the status of the target network to a suspended state (also called a standby state, a to-be-activated state, a deactivated state, etc.). Resume a target network is to change the status of the target network from a suspended state to an activated state. Changing a network attribute of a target network may be understood as one or more of changing the capacity of the target network (i.e., changing a capacity-related parameter), changing the capability of the target network (changing a network capability-related parameter), changing a configuration policy of the target network, or changing a service user list of the target network.

[0137] In a possible implementation, the information on the operation type may be an index value, and there is a mapping relationship between the index value and the operation type. The mapping relationship is specified in a protocol, pre-configured, or agreed upon by the terminal and the core network. For example, a specific implementation of the information on the operation type may be as follows: the request message includes a field 1, and the field 1 indicates the operation type. For example, see Table 1 for the mapping relationship between the value of the field 1 and the operation type. [Table 1]

[0138] In this case, if the user determines that the user's request is to suspend the target network, the terminal device determines that the value of field 1 in the request message is 2. It should be noted that the representation format of the value of field 1 in this example is merely an example and should not be considered as a specific limitation to the present application. The value of field 1 may alternatively be represented using bits. For example, field 1 includes 3 bits. In this case, when the value of field 1 is 000, it indicates that the operation type is to create a target network, when the value of field 1 is 001, it indicates that the operation type is to modify the target network, when the value of field 1 is 010, it indicates that the operation type is to suspend the target network, when the value of field 1 is 011, it indicates that the operation type is to resume the target network, or when the value of field 1 is 100, it indicates that the operation type is to modify the network attributes of the target network.

[0139] In a possible implementation, the request message further includes one or more of user information of the terminal device, operation parameters corresponding to the operation type, or information about the target network.

[0140] The user information includes one or more of information indicating a user's permanent identifier (e.g., subscription permanent identifier (SUPI), international mobile subscriber identification number (IMSI), or mobile subscriber international ISDN number (MSISDN)), a user group identifier, a temporary user identifier (e.g., globally unique temporary identity (GUTI)), or a device identifier (e.g., permanent equipment identifier (PEI) or international mobile equipment identity (IMEI)). An operation parameter corresponding to an operation type may indicate a specific operation. For example, when the request message is for requesting to create a target network, the operation parameter carried in the request message indicates to create a specific target network. When the request message is for modifying network attributes of the target network, the operation parameter carried in the request message indicates to modify one (or some) specific network attributes of the target network. The information about the target network includes one or more of an identifier, a capacity value, a capability list, a service user list, or a configuration policy of the target network.

[0141] For example, if user 11 creates a target network having a capacity value a1 and a capability value p1, the request message determined by the terminal device of user 11 may include an identifier of user 11, an operation type which is to create a network, and operation parameters including the capacity value a1 and the capability value p1.

[0142] For example, the service user list of the target network N1 includes user 11, user 12, and user 21. When user 11 (which may be understood as a user having management permission for the target network N1) wants to move user 21 from the service user list of the target network N1, the terminal device of user 11 determines a request message for operating the target network N1. The request message may include an identifier of user 11, an identifier of the target network N1, an operation type, which is to change a network attribute of the target network, and an operation parameter, which is to delete the identifier of user 21 from the service user list of the target network N1.

[0143] S302: A terminal device sends a request message to a core network, and in response, the core network receives the request message.

[0144] The request message is control plane signaling or user plane signaling between the terminal device and the core network. In other words, the terminal device sends the request message to the core network using control plane signaling or user plane signaling between the terminal device and the core network.

[0145] In a possible implementation, the control plane signaling may be non-access stratum (NAS) signaling.

[0146] In a possible implementation, the user plane signaling may be a message based on general packet radio service tunneling protocol (GTP)-user plane (i.e., GTP-U). In a possible implementation, the core network device performing step S302 is a first functional network element, and the terminal device sends the request message to the first functional network element. The first functional network element is configured to access the terminal device to the core network, i.e., the first functional network element has a user network access function. For example, the first functional network element may be an AMF network element in FIG. 1b, an NSN network element in FIG. 2, etc. The first functional network element may also be called an access management network element or a network service network element.

[0147] S303: The core network operates a life cycle of the target network, which is managed by the core network, based on the request message.

[0148] In other words, based on the information about the operation type in the request message, the core network creates the target network, deletes the target network, changes the running state of the target network (including pausing the target network or resuming the target network), or changes the network attributes of the target network.

[0149] In a possible implementation, the core network manages one or more user networks, and when the operation type in the request message is one of deleting the target network, changing the running state of the target network (including pausing or resuming the target network), or changing the network attributes of the target network, the core network determines the target network from the multiple networks based on the request message, and operates the life cycle of the target network.

[0150] In a possible implementation, the core network device that performs step S303 is a second functional network element, and the second functional network element is configured to operate the life cycle of the target network. For example, 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.

[0151] It should be understood that the second functional network element may be co-deployed with the first functional network element (i.e., the 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 may be deployed separately from the first functional network element. When the second functional network element is deployed separately from the first functional network element, a communication connection exists between the first functional network element and the second functional network element (i.e., it can be understood that the first functional network element may communicate with the second functional network element). After the first functional network element receives a request message from the terminal device in S302 (for ease of distinction, the request message in S302 is hereinafter referred to as the first request message), the first functional network element may forward the first request message to the second functional network element, so that the second functional network element may operate the life cycle of the target network based on the request message in S303. Alternatively, at S302, after the first functional network element receives the first request message from the terminal device, the first functional network element may send a second request message (the content included in the second request message may be the same as the content included in the first request message) to the second functional network element based on the first request message, thereby causing the second functional network element to operate the life cycle of the target network based on the second request message.

[0152] In a possible implementation, when the second functional network element is deployed separately from the first functional network element, in order to improve communication system security, the second functional network element may perform identity authentication with the first functional network element, and after the identity authentication with the first functional network element is successful, the second functional network element operates the life cycle of the target network.

[0153] In other words, after the second functional network element receives the second request message from the first functional network element, the second functional network element performs identity verification on the first functional network element, and the verification contents of the second functional network element include, but are not limited to, one or more of the following contents: verifying whether the first functional network element actually exists, verifying whether the first functional network element has the permission to send the second request message (i.e., whether the first functional network element has the permission to request the second functional network element to operate the life cycle of the target network), or verifying whether the first functional network element is valid. After the identity authentication performed by the second functional network element on the first functional network element is successful, the second functional network element operates the life cycle of the target network based on the second request message.

[0154] In order to facilitate understanding of the technical solutions of the present application, the following uses an example in which a second functional network element is deployed separately from a first functional network element to describe examples of how to create a target network, how to delete a target network, how to change the running state of a target network, or how to change network attributes of a target network.

[0155] 1. Creating a target network.

[0156] The connection between the target network and the access network device may be a direct connection (hereinafter referred to as a direct connection for short) or an indirect connection (hereinafter referred to as an indirect connection for short). It should be understood that the target network is directly connected to the access network device, i.e., the access network device may directly communicate with the target network. In other words, after the access network device receives a service request message (the service request message is for requesting the target network to provide a network service) from the terminal device, the access network device may directly forward the service request message to the target network, so that the target network provides the corresponding network service. The target network is indirectly connected to the access network device, i.e., the access network device uses a first functional network element to indirectly communicate with the target network. In other words, after receiving a 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 provides the corresponding network service.

[0157] It can be seen that if the target network is directly connected to the access network device, the signaling transmission overhead can be reduced. If the target network is indirectly connected to the access network device, the access network device cannot directly contact the target network, so the security of the target network is improved.

[0158] The following specifically describes the process of creating a target network based on whether the target network is directly connected to an access network device or indirectly connected to an access network device.

[0159] If the target network is directly connected to the access network device, please refer to Fig. 4a, which is a schematic flow chart of creating a target network according to the present application.

[0160] S401: A second functional network element interacts with a resource management function to create a target network.

[0161] The second functional network element interacts with the resource management function to apply for available execution resources and instantiate an execution entity, which may be a newly instantiated virtual machine, a newly instantiated container, or a new process, thread, or another execution entity running on an existing virtual machine or container. Furthermore, the second functional network element creates a target network based on the request message from the terminal device.

[0162] The resource management function is configured to manage network resources, for example, to allocate resources to create network function instances required by the user network. In some cases, the resource management function may be a management and orchestration (MANO) network element, a container (docker) management network element, a docker engine, or another resource management function.

[0163] In a possible scenario, the core network may further include a third functional network element. The third functional network element is configured to store network configuration data, the network configuration data including network configuration parameters and / or network operation policy data. The network configuration parameters include one or more of parameters required for the execution of the network (e.g., one or more of data packet loss rate, latency, bandwidth, or network speed), scripts required for the execution of the network, or environmental variables. The network operation policy data includes one or more of QoS policies, charging policies, or user access control policies. In a possible implementation, 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 an identifier of the network, or each configuration data in the third functional network element is associated with an index value.

[0164] If the network configuration data in the third functional network element is associated with the user identifier, the request message carries the user identifier and an operation type (wherein the operation type is to create a target network), and the second functional network element interacts with a resource management function based on the user identifier to create the target network, and the second functional network element (or the target network) obtains network configuration data corresponding to the target network from the third functional network element based on the user identifier. Further, the second functional network element configures the target network based on the network configuration data.

[0165] If the network configuration data in the third functional network element is associated with the identifier of the network, the request message carries a user identifier and an operation type (wherein the operation type is to create a target network). Further, the second functional network element interacts with a resource management function based on the user identifier to create the target network. The target network (or the second functional network element) obtains network configuration data corresponding to the identifier of the target network from the third functional network element based on the identifier of the target network. The target network (or the second functional network element) configures the target network based on the network configuration data.

[0166] When each configuration data in the third functional network element is associated with an index value, the request message carries a user identifier, an operation type (wherein the operation type is to create a target network), and an operation-related parameter (wherein the specific parameter for creating the target network, for example, the capacity value, capability, or service user list of the target network) based on the user identifier. Further, the second functional network element interacts with a resource management function based on the user identifier to create the target network. The target network (or the second functional network element) determines a target index value based on the operation parameter, and obtains network configuration data corresponding to the identifier of the target network from the third functional network element based on the target index value. The target network (or the second functional network element) configures the target network based on the network configuration data.

[0167] S402: The target network interacts with the access network device to establish a communication connection and a user context connection.

[0168] Specifically, after creating the target network, the second functional network element sends information about the access network device to the target network and notifies it to update the user context information. The information about the access network device is used to address the access network device, and the user context information is used to establish a user context connection. Furthermore, the target network establishes a communication connection to the access network device based on the information about the access network device, and establishes a user context connection based on the user context information. The access network device is a device that connects a terminal device to the target network. The information about 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.

[0169] Alternatively, after creating the target network, the second functional network element sends information about the target network to the access network device and notifies it to update the user context information. The information about the target network is used to address the target network, and the user context information is used to establish a user context connection. Furthermore, the access network device establishes a communication connection to the target network based on the information about the target network, and establishes the user context connection based on the user context information. The access network device is a device that connects a terminal device to the target network. The information about the target network is used to address the target network. For example, the information about the target network includes an identifier of the target network and / or address information of the target network.

[0170] It should be noted that the communication connection may include one or more of the underlying connections established and completed according to the hypertext transfer protocol (HTTP), transmission control protocol (TCP), stream control transmission protocol (SCTP), or another protocol. The user context information includes user state, user attribute information, and user-related communication connection information.

[0171] S403: The access network device changes the connection information of the terminal device.

[0172] In other words, after establishing a communication connection and a user context connection to the target network, the access network device changes the transmission path (or called the routing path) of the message from the terminal device, so that the access network device forwards the network service request message (e.g., a PDU session establishment request message) from the terminal device to the target network.

[0173] If the target network is indirectly connected to the access network device, i.e., the target network and the access network device indirectly interact with each other using the first functional network element, please refer to Fig. 4b, which is another schematic flowchart of creating a target network according to the present application.

[0174] S411: A second functional network element interacts with a resource management function to create a target network.

[0175] For the specific implementation of S411, please refer to the above description of the specific implementation of S401. The repeated parts will not be described again here.

[0176] S412: The target network sends a first update request to the first functional network element, and in response, the first functional network element receives the first update request from the target network.

[0177] The first update request is for requesting the first functional network element to update (or change) the access control of the target network. The first update request carries information about the target network and notifies to update the user context information. The information about the target network is used to address the target network. For example, the information about the target network includes, but is not limited to, an identifier of the target network or address information of the target network. The user context information is used to establish a user context connection.

[0178] S413: The first functional network element updates (or modifies) the connection information based on the first update request.

[0179] In other words, the first functional network element stores information about the target network and establishes a communication connection and a user context connection, such that after receiving a request message for requesting the target network to provide a network service (or a request message for accessing the target network), the first functional network element forwards the received request message for requesting the target network to provide a network service to the target network.

[0180] S414: The first functional network element sends a second update request to the access network device, and in response, the access network device receives the second update request from the first functional network element.

[0181] In other words, the second update request may enable the access network device to establish a communication connection and a user context connection to a first functional network element related to the target network, i.e., both the communication connection and the user context connection are associated with the target network. The second update request is for requesting the access network device to update (or change) the access control of the target network. The second update request carries information about the target network, and the information about the target network is used to address the target network. For example, the information about the target network includes, but is not limited to, an identifier of the target network or address information of the target network.

[0182] S415: The access network device sends a response message to the second update request to the first functional network element, and in response, the first functional network element receives a response message to the second update request from the access network device. The response message carries an operation result of the access network device based on the second update request.

[0183] The access network device performs a corresponding operation based on the second update request: the access network device establishes a communication connection and a user context connection to a first functional network element related to the target network, i.e., the communication connection and the user context connection are associated with the target network. Further, the access network device sends a response message to the second update request to the first functional network element based on the operation result in the second update request.

[0184] S416: The first functional network element sends a response message to the first update request to the target network, and in response, the target network receives a response message to the first update request from the first functional network element.

[0185] The response message to the first update request indicates an operation result of the first functional network element based on the first update request and an operation result of the access network device based on the second update request. In other words, when the operation result of the first functional network element based on the first update request indicates success and the operation result of the access network device based on the second update request indicates success, the operation result in the response message to the first update request sent by the first functional network element to the target network indicates success. When the operation result of the first functional network element based on the first update request indicates failure or the operation result of the access network device based on the second update request indicates failure, the operation result in the response message to the first update request sent by the first functional network element to the target network indicates failure.

[0186] 2. Delete the target network.

[0187] The following specifically describes the process of deleting a target network based on whether the target network is directly connected (hereinafter referred to as directly connected for short) to an access network device or whether the target network is indirectly connected to an access network device.

[0188] If the target network is directly connected to the access network device, please refer to Fig. 5a, which is a schematic flowchart of deleting a target network according to the present application.

[0189] S501: A second functional network element sends a control operation request message to a target network, and in response, the target network receives a control operation request message from the second functional network element, where the control operation request message includes an operation type (here, deleting the target network).

[0190] The second functional network element receives a request message from the terminal device, where the request message is used to delete the target network, in which the second functional network element sends a control operation request message to the target network, where the control operation request message instructs the target network to release the link.

[0191] S502: The target network sends a link release request to the access network device, and in response, the access network device receives a link release request from the target network.

[0192] The target network deletes the user context connection to the access network device based on the control operation request message sent by the second functional network element, and sends a link release request to the access network device, where the link release request instructs (or notifies) the access network device to delete the user context connection to the target network.

[0193] The link release request includes information about the target network, which is used to address the target network, including but not limited to a target network identifier and / or address information of the target network.

[0194] S503: The access network device deletes a user context connection to the target network based on the link release request.

[0195] The access network device may smoothly delete the user context connection to the target network based on the link release request. The process of smoothly deleting the user context connection may be described as follows: the access network device sends a notification message to the terminal device, and the notification message notifies that the terminal device served by the target network is offline. After all the terminal devices served by the target network service are offline, the access network device deletes the user context connection to the target network. In this manner, the link is released after all the users served by the target network are offline, so that the user experience can be improved.

[0196] Alternatively, the access network device may non-smoothly delete the user context connection to the target network based on the link release request. In other words, after the access network device receives the link release request, regardless of whether the terminal device served by the target network is offline, the access network device directly deletes the user context connection to the target network. In this manner, the efficiency of releasing the link by the access network device can be improved.

[0197] S504: The access network device sends a response message corresponding to the link release request to the target network, and the target network correspondingly receives the response message sent by the access network device corresponding to the link release request. The response message carries the operation result of the access network device based on the link release request.

[0198] It should be understood that releasing the link referred to in this application refers to deleting the context connection between two devices, and the response message is sent via a signaling channel. Therefore, after the link between the two devices is released, the subsequent transmission of the response message is not affected (i.e., the response message can still be transmitted between the two devices via a signaling channel (or communication connection)). For example, after the access network device releases the user context connection between the access network device and the target network based on the link release request in S503, in S504, the access network device releases the user context connection between the access network device and the target network via a signaling channel (communication connection). , Li The link may then transmit a response message to the link release request to the first functional network element.

[0199] S505: The target network sends a response message to the control operation request message to the second functional network element, and in response, the second functional network element Control Action Request Message and receiving a response message from the target network, the response message carrying a result of a link release operation of the user context connection between the target network and the access network device.

[0200] S506: The second functional network element interacts with a resource management function to release resources of the target network.

[0201] The second functional network element releasing the resources of the target network and completing the release of the resources of the target network may be understood as all communication connections related to the target network being released, including the communication connections between the target network and the second functional network element and the communication connections between the target network and the access network device. Deleting the communication connections may be one or more of deleting the underlying connections completed according to HTTP, TCP, SCTP, or another protocol.

[0202] If the target network is indirectly connected to the access network device, please refer to Fig. 5b, which is another schematic flowchart of deleting a target network according to the present application.

[0203] S511: The second functional network element sends a control operation request message to the target network, and in response, the target network receives a control operation request message from the second functional network element. The control operation request message includes an operation type (here, deleting the target network).

[0204] S512: The target network sends a first link release request to the first functional network element, and in response, the first functional network element receives a first link release request from the target network.

[0205] The target network sends a first link release request to the first functional network element based on the control operation request message sent by the second functional network element, and the first link release request instructs (or informs) the first functional network element to delete the user context connection to the target network. The link release request includes information about the target network, and the information about the target network is used to address the target network. The information about the target network includes, but is not limited to, an identifier of the target network and / or address information of the target network.

[0206] S513: The first functional network element sends a second link release request to the access network device, and in response, the access network device receives a second link release request from the first functional network element.

[0207] The first functional network element sends a second link release request to the access network device based on the first link release request, and the second link release request instructs (or informs) the access network device to delete a user context connection to the first functional network element, which is associated with the target network. The link release request includes information about the target network, which is used to address the target network. The information about the target network includes, but is not limited to, an identifier of the target network and / or address information of the target network.

[0208] S514: The access network device performs a connection deletion process based on the second link release request.

[0209] Specifically, the access network device may smoothly perform a connection deletion process based on the second link release request. Alternatively, the access network device may non-smoothly perform a connection deletion process based on the second link release request.

[0210] S515: The access network device sends a response message to the second link release request to the first functional network element, and in response, the first functional network element receives a response message to the second link release request from the access network device. The response message carries an operation result of the access network device based on the second link release request.

[0211] S516: The first functional network element sends a response message to the first link release request to the target network, and in response, the target network receives a response message to the second link release request from the first functional network element. The response message carries an operation result of the first functional network element based on the first link release request, or further includes an operation result of the access network device based on the second link release request.

[0212] S517: The target network sends a response message to the control operation request message to the second functional network element, and in response, the second functional network element Control Action Request Message Receive a response message from the target network, where the response message carries an operation result of the first functional network element based on the first link release request, or further includes an operation result of the access network device based on the second link release request.

[0213] S518: The second functional network element interacts with a resource management function to release resources of the target network.

[0214] The second functional network element releasing the resources of the target network and completing the release of the resources of the target network may be understood to mean that all communication connections related to the target network (including the communication connections between the target network and the second functional network element, and the communication connections between the target network and the first functional network element) are released.

[0215] 3. Modifying the target network (changing the network attributes of the target network or changing the running state of the target network, including pausing the target network or resuming the target network).

[0216] The following specifically describes the process of pausing a target network based on whether the second functional network element directly controls the first functional network element or whether the second functional network element indirectly controls the first functional network element.

[0217] In case the second functional network element directly controls the first functional network element, please refer to Fig. 6a, which is a schematic flow chart of modifying a target network (changing the running state of the target network or modifying the network attributes of the target network) according to the present application.

[0218] S601: A second functional network element sends a first control operation request message to a target network, and in response, the target network receives a first control operation request message from the second functional network element. The first control operation request message includes an operation type.

[0219] In Fig. 6a, the operation type is one of changing the running state of the target network (i.e., pausing the target network or resuming the target network) or changing the network attributes of the target network. The first control operation request message is for requesting the target network to perform an operation process corresponding to the operation type, i.e., one of changing the running state of the target network (i.e., pausing the target network or resuming the target network) or changing the network attributes of the target network. In this case, the first control operation request message may further include identifier information of the target network.

[0220] In a possible implementation, modifying the network attributes of the target network includes modifying one or more of the following: 1. Modifying the network capabilities of the target network, e.g., enabling or disabling device capabilities or services corresponding to the target network, where the services may be services provided by each NF defined in 3GPP, in which case, NRF registration and update are triggered after the services provided by the NF are modified. 2. Modifying the network capacity of the target network, e.g., increasing the capacity value of the target network (performing a capacity expansion process), decreasing the capacity value of the target network (performing a capacity reduction process), or modifying the capacity value of the target network to a specified value or level to perform a capacity expansion or reduction of the target network. 3. Modifying the user list of the target network, e.g., adding user information to the user list of the target network, or deleting user information from the user list of the target network, where the user information includes one or more of a subscription persistent identifier (e.g., IMSI / SUPI / MSISDN), a user group identifier, a temporary user identifier (e.g., GUTI), or a device identifier (e.g., PEI / IME).

[0221] In a possible implementation, when the first control operation request message is used to change network attributes of the target network, the first control operation request message may further include operation parameters.

[0222] S602: The second functional network element sends a second control operation request message to the first functional network element, and in response, the first functional network element receives a second control operation request message from the second functional network element. The second control operation request message includes an operation type.

[0223] The second control operation request message is for requesting the first functional network element to perform an operation process on information relating to the target network corresponding to one of the operation types, namely, pausing the target network, resuming the target network, or modifying network attributes of the target network.

[0224] In this case, the second control action request message may further include identifier information of the target network.

[0225] In a possible implementation, when the second control operation request message is used to change network attributes of the target network, the second control operation request message may further include operation parameters.

[0226] It should be understood that the execution order of S601 and S602 in this specification is merely an example and should not be considered as a specific limitation to the present application. In other words, in the actual application process, S601 and S602 may be executed simultaneously, S602 may be executed before S601, or S601 may be executed before S602.

[0227] S603: The target network performs a corresponding action process based on the action type in the first control action request message.

[0228] Suspending the target network by the target network specifically includes one or more of the following: working on the user context to prohibit subsequent signaling of the user; status , terminate and report user statistics and call detail record data, or detach the user immediately (or timer triggered) through signaling.

[0229] Resuming (or activating) the target network by the target network specifically includes one or more of the following: working on the user context to resume subsequent signaling of the user; status , resume the user's statistical and call detail record data, or allow subsequent signaling of the user.

[0230] Changing the network attributes of the target network by the target network specifically includes: the target network changes the network attributes of the target network (including one or more of network capability, network capacity, or user list) based on the operation parameters in the first control operation request message.

[0231] S604: The target network responds to the first control action request message. 1. A feedback message is sent to a second functional network element, and in response, the second functional network element receives a first feedback message from the target network corresponding to the first control action request message.

[0232] After the target network executes a corresponding operation process based on the first control operation request message, the target network sends a first feedback message to the second functional network element based on the operation result. The first feedback message includes first operation result information, and the first operation result information indicates an operation result of the operation executed by the target network based on the first control operation request message. When the first operation result information indicates an operation failure, the first operation result information may include a first failure cause value, and the first failure cause value indicates a specific cause of the failure of the operation executed by the target network.

[0233] In a possible implementation, the first feedback message includes one or more of an identifier of the target network, a state of the target network after the operation processing (including an activated state or a suspended state), or network attribute information of the target network.

[0234] S605: The first functional network element performs an action process based on the second control action request message.

[0235] The first functional network element performs a corresponding operation process based on the specific content of the second control operation request message sent by the second functional network element.

[0236] In one example, when the operation type in the second control operation request message is to suspend the target network, suspending, by the first functional network element, the target network in the information list maintained by the first functional network element, i.e., updating (or changing) the information about the target network to corresponding information during the suspension of the target network, specifically includes one or more of the following: recording the working status of the user context to prohibit subsequent signaling of the user, terminating and reporting the user's statistics and call detail record data, or immediately (or triggered by a timer) detaching or deregistering the user through signaling.

[0237] In another example, when the operation type in the second control operation request message is to resume the target network, resuming, by the first functional network element, the target network in the information list maintained by the first functional network element, i.e., updating (or changing) the information about the target network to corresponding information during activation of the target network, specifically includes one or more of the following: recording the working status of the user context to resume subsequent signaling of the user, resuming the user's statistical information and call detail record data, or enabling subsequent signaling of the user.

[0238] In yet another example, when the operation type in the second control operation request message is to change the network attributes of the target network, it can be understood that the first functional network element changes the network attribute information of the target network in the information list maintained by the first functional network element based on the second control operation request message, i.e., the first functional network element changes the network attribute information of the target network based on the operation parameters in the second control operation request message.

[0239] S606: The first functional network element sends a network-controlled access-update request message to the access network device, and in response, the access network device receives a network-controlled access-update request message from the first functional network element. The network-controlled access-update request message includes an operation type.

[0240] When the action type is to suspend the target network, the network-controlled access update request message is for requesting the access network device to perform corresponding action processing on the information about the target network, i.e., to update (or change) the information about the target network to corresponding information during the suspension of the target network. In this case, the update request may further include identifier information of the target network.

[0241] When the action type is to resume (or activate) the target network, the network-controlled access update request message is for requesting the access network device to perform corresponding action processing on the information about the target network, i.e., to update (or change) the information about the target network to corresponding information during the activation of the target network. In this case, the update request may further include identifier information of the target network.

[0242] When the operation type is to change the network attributes of the target network, the network control access update request message is for requesting the access network device to change the network attributes of the target network maintained by the access network device. In this case, the second control operation request message may further include identifier information and operation parameters of the target network.

[0243] S607: The access network device performs an action process based on the network-controlled access update request.

[0244] The access network device performs corresponding action processing based on the specific content of the network-controlled access update request.

[0245] In one example, when the action type in the network-controlled access update request is to suspend the target network and to update (or modify) corresponding information during the suspension of the target network by the access network device, the information about the target network in the information list maintained by the access network device specifically includes one or more of the following: recording the working status of the user context to prohibit subsequent signaling of the user, terminating and reporting the user's statistics and call detail record data, or immediately (or timer-triggered) detaching the user through signaling.

[0246] In another example, when the operation type in the network-controlled access update request is to resume the target network, by the access network device, updating (or changing) to corresponding information during activation of the target network, the information about the target network in the information list maintained by the access network device specifically includes one or more of the following: recording the working status of the user context to resume the user's subsequent signaling, resuming the user's statistical information and call detail record data, or enabling the user's subsequent signaling.

[0247] In yet another example, when the action type in the network controlled access update request is to change network attributes of the target network, the access network device changes the network attributes of the target network maintained by the access network device based on the action parameters in the network controlled access update request.

[0248] S608: The access network device sends a second feedback message corresponding to the network-controlled access update request to the first functional network element, and in response, the first functional network element receives a second feedback message corresponding to the network-controlled access update request from the access network device.

[0249] After performing a corresponding operation process based on the network-controlled access update request, the access network device sends a second feedback message to the first functional network element. The second feedback message includes second operation result information, where 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 indicates operation success or operation failure. When the second operation result information indicates operation failure, the second operation result information may include a second failure cause value, where the second failure cause value indicates a specific cause for the failure of the operation performed by the access network device.

[0250] In a possible implementation, the second feedback message may further include one or more of an identifier of the target network, a state of the target network in the access network device after the operation processing (including an activated state or a suspended state), or network attribute information of the target network.

[0251] S609: The first functional network element sends a third feedback message corresponding to the second control operation request message to the second functional network element, and in response, the second functional network element receives a third feedback message corresponding to the second control operation request message from the first functional network element.

[0252] The third feedback message includes third operation result information, and the third operation result information is used to feed back the operation result of the first functional network element and the access network device to the second functional network element, and the third operation result is any one of the following cases: 1. When the operation result of the access network device indicates success and the operation processing result of the first functional network element indicates success, the operation result information carried in the third feedback message indicates success. 2. When the operation result of the access network device indicates failure or the operation processing result of the first functional network element indicates failure, the operation result carried in the third feedback message indicates failure. In this case, the third feedback message may further carry a third failure cause value (indicating a specific cause why the operation result in the third feedback message indicates failure).

[0253] In a possible implementation, the third feedback message may further carry one or more of status information of the target network at the first functional network element (including an activated or suspended state), an identifier of the target network, or network attribute information of the target network.

[0254] When the second functional network element indirectly controls the first functional network element, see Fig. 6b, which is a schematic flow chart of modifying a target network (changing the running state of the target network or modifying the network attributes of the target network) according to the present application.

[0255] S611: A second functional network element sends a first control operation request message to a target network, and in response, the target network receives a first control operation request message from the second functional network element. The first control operation request message includes an operation type.

[0256] For the specific implementation of S611, please refer to the above description of the specific implementation of S601. The repeated parts will not be described again.

[0257] S612: The target network performs a corresponding action process based on the action type in the first control action request message.

[0258] For the specific implementation of S612, please refer to the above description of the specific implementation of S603. The repeated parts will not be described again.

[0259] S613: The target network sends a second control operation request message to the first functional network element, and in response, the first functional network element receives a second control operation request message from the target network. The second control operation request message includes an operation type.

[0260] The second control operation request message is for requesting the first functional network element to perform an operation process on the information about the target network corresponding to one of the operation types, i.e., pausing the target network, resuming the target network, or modifying a network attribute of the target network. In a possible implementation, the second control operation request message may further include identifier information of the target network.

[0261] In a possible implementation, when the second control operation request message is used to change network attributes of the target network, the second control operation request message may further include operation parameters.

[0262] S614: The first functional network element performs an action process based on the second control action request message.

[0263] S615: The first functional network element sends a network-controlled access-update request message to the access network device, and in response, the access network device receives a network-controlled access-update request message from the first functional network element. The network-controlled access-update request message includes an operation type.

[0264] S616: The access network device performs an action process based on the network-controlled access update request.

[0265] S617: The access network device sends a second feedback message corresponding to the network-controlled access update request to the first functional network element, and in response, the first functional network element receives a second feedback message corresponding to the network-controlled access update request from the access network device.

[0266] For the specific implementation of S614 to S617, please refer to the above description of the specific implementation of S605 to S608. The repeated parts will not be described again here.

[0267] S618: The first functional network element sends a third feedback message corresponding to the second control operation request message to the target network, and in response, the target network receives a third feedback message corresponding to the second control operation request message from the first functional network element.

[0268] For the relevant description of the feedback message corresponding to the second control operation request message, please refer to the description in S609. The details will not be described again here.

[0269] S619: The target network sends a first feedback message corresponding to the first control operation request message to a second functional network element, and in response, the second functional network element receives a first feedback message corresponding to the first control operation request message from the target network.

[0270] The target network sends a 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 one of several cases: 1. When the operation result of the first functional network element indicates success, the operation result of the access network device indicates success, and the operation processing result of the target network indicates success, the operation result carried in the first feedback message indicates success. 2. When the operation result of the first functional network element indicates failure, the operation result of the access network device indicates failure, and the operation processing result of the target network indicates failure, the first feedback message can further carry a failure cause value (indicating a specific cause for which the operation result in the first feedback message indicates failure).

[0271] In a possible implementation, the first feedback message may further carry one or more of a state of the target network at the first functional network element (including an activated state or a suspended state), an identifier of the target network, or network attribute information of the target network.

[0272] It can be seen that according to the network resource management method provided in Fig. 3, the terminal device can directly operate the target network using the core network device. Compared with the manner in which the user uses the operator to change the target network, the time period until the change of the target network takes effect is shortened, thereby improving efficiency.

[0273] Figure 7 is a schematic flowchart of another network resource management method according to an embodiment of the present application. As shown in Figure 7, the network resource management method may be performed by a core network device or a chip in the core network device, or may be performed by a terminal device or a chip in the terminal device. Figure 7 is described using an example in which the core network device and the terminal device are entities for performing the method.

[0274] S701: A terminal device determines a request message, where the request message is used to operate a life cycle of a target network.

[0275] S702: The terminal device sends a request message to the core network device, and in response, the core network device receives a request message from the terminal device.

[0276] For the specific implementation of S701 and S702, please refer to the above description of the specific implementation of S301 and S302. The repeated parts will not be described again here.

[0277] S703: The core network device performs operation authentication based on the request message.

[0278] After the core network device receives the request message from the terminal device, the core network device performs operation authentication on the request message to authenticate whether the request message is from a valid (or actually exists) terminal device, or whether the content of the request message is valid (or is understood by the core network device to be executable, i.e., the terminal device has the operation permission corresponding to the request message), which prevents the core network device from performing invalid operations based on the request message, and improves the security of the target network.

[0279] In a possible implementation, the core network device performing operation authentication based on the request message includes one or more of the following manners.

[0280] Method 1: A core network device authenticates the status of a target network based on the operation type.

[0281] In this operation authentication method of the method, the core network device determines whether the target network can perform a processing operation corresponding to the operation type in the request message based on the status of the target network, i.e., the core network device determines whether the operation type matches the status of the target network. If the operation type matches the status of the target network, the core network device succeeds in authenticating the status of the target network, or if the operation type does not match the status of the target network, the core network device fails to authenticate the status of the target network.

[0282] It should be understood that the operation type matching the status of the target network means that the core network device determines, based on the status of the target network, that the target network can perform the processing operation corresponding to the operation type in the request message. Conversely, the operation type not matching the status of the target network means that the core network device determines, based on the status of the target network, that the target network cannot perform the processing operation corresponding to the operation type in the request message.

[0283] In possible implementations, the operation type not matching the status of the target network includes one or more of the following: 1. When the operation type is to create the target network, the status of the target network is existent. 2. When the operation type is to delete the target network, the status of the target network is not existent. 3. When the operation type is to change the network attributes of the target network, the status of the target network is not existent. 4. When the operation type is to pause the target network, the status of the target network is not existent or in a paused state. 5. When the operation type is to resume the target network, the status of the target network is not existent or in an activated state.

[0284] Conversely, when the operation type is to create a target network, if the target network does not exist, the operation type may be determined to match the status of the target network. When the operation type is to delete a target network, if the target network exists, the operation type may be determined to match the status of the target network. When the operation type is to modify a network attribute of a target network, if the target network exists, the operation type may be determined to match the status of the target network. When the operation type is pausing the target network, if the target network exists and is in an activated state, the operation type may be determined to match the status of the target network. When the operation type is to resume the target network, if the target network exists and is in a paused state (or a deactivated state or a standby state), the operation type may be determined to match the status of the target network.

[0285] Method 2: The core network device authenticates the operation permission of the operation type.

[0286] In this operation authentication method of the method, the core network device authenticates whether the terminal device that sends the request message has an operation permission corresponding to the operation type. If the terminal device has the operation permission corresponding to the operation type, the core network device succeeds in authenticating the operation permission of the operation type; if the terminal device does not have the operation permission corresponding to the operation type, the core network device fails to authenticate the operation permission of the operation type.

[0287] In a possible implementation, the request message further includes user information of the terminal device, and the core network device obtains user subscription information based on the user information, and the core network device authenticates operation permission of the operation type based on the user subscription information and / or according to a local configuration policy. The user subscription information includes one or more of an allowed operation action list, an allowed network identifier list, an allowed network capacity allocation, an allowed service user list, or a configuration policy list. The local configuration policy may be understood as an operator's management and control policy, a core network device's management and control policy, etc.

[0288] In other words, the core network device may obtain user subscription information based on the user information of the terminal device, and the user subscription information includes the permitted operation permission of the terminal device. Furthermore, the core network device determines whether the terminal device can request to perform the operation type in the request message based on the permitted operation permission of the terminal device in the user subscription information. When the user subscription information includes the operation type in the request message, the core network device successfully authenticates the operation permission of the operation type. Conversely, when the user subscription information does not include the operation type in the request message, the core network device fails to authenticate the operation permission of the operation type (i.e., authentication fails).

[0289] For example, the core network device receives a request message sent by the terminal device 1, where the request message includes user information (user A's identifier), an operation type (changing the network attribute of network 1 (i.e., the target network)), and an operation parameter (changing the network capacity value to 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. [Table 2]

[0290] In addition, the core network device authenticates the operation permission of the request message based on the subscription information of user A. In the subscription information of user A, it can be seen that the terminal device may change the network attribute of network 1, and may change the network capacity value of network 1 to a1 or a2, but the terminal device is not authorized to change the network capacity value of network 1 to a3. In this case, the core network device cannot authenticate the operation permission of the operation type in the request message.

[0291] Note that both operation authentication method 1 and operation authentication method 2 may be executed, or only one of operation authentication method 1 and operation authentication method 2 may be executed. This is not particularly limited in the present application. In addition, when both operation authentication method 1 and operation authentication method 2 may be executed, the execution order of operation authentication method 1 and operation authentication method 2 is not particularly limited in the present application. That is, operation authentication method 1 may be executed before operation authentication method 2, operation authentication method 1 may be executed after operation authentication method 2, or operation authentication method 1 and operation authentication method 2 may be executed simultaneously.

[0292] In a possible implementation form, when multiple functional network elements in a core network device are configured to perform operation authentication, the functional network element that performs operation authentication method 1 and the functional network element that performs operation authentication method 2 may be the same functional network element or different functional network elements.

[0293] S704: When the result of the operation authentication indicates success, the core network device operates the life cycle of the target network.

[0294] After the core network device performs operation authentication on the request message, if the operation authentication is successful, the core network device operates the life cycle of the target network based on the operation type and / or operation parameters in the request message.

[0295] In a possible implementation form, the core network device sends a first response message to the terminal device based on the operation result of operating the life cycle of the target network, and the first response message includes the status of the target network or the identifier of the target network. In other words, the first response message may indicate that the operation result of operating the life cycle of the target network by the core network device indicates success. In this case, the first response message may include one or more of the identifier of the target network, the status of the target network after the core network device operates the life cycle of the target network, or the network attribute information of the target network. Alternatively, the first response message may indicate that the operation result of operating the life cycle based on the target network by the core network device indicates failure. In this case, the first response message may include the identifier of the target network, the status of the target network after the core network device operates the life cycle of the target network, the network attribute information of the target network, or a failure cause value (wherein the failure cause value indicates the reason why the life cycle of the target network was not operated this time).

[0296] In one example, the network capacity value of network 1 is a1, and the core network device receives a request message sent by terminal device 1, where the request message includes user information (an identifier of user A), an operation type (to change the network attributes of network 1 (i.e., the target network)), and an operation parameter (to change the network capacity value to a value a2). とIf the result of performing operation authentication on the request message by the core network device indicates success, the core network device changes the network capacity value of network 1 from a1 to a2. Furthermore, the first response message returned by the core network device to the terminal device 1 may include an identifier of network 1, a state of network 1 (presence state, available state, or activated state), and a network attribute of network 1 (the network capacity value is a2).

[0297] In another example, the network capacity value of network 1 is a3, and the core network device receives a request message sent by the terminal device 1, where the request message includes user information (user A's identifier), an operation type (changing the network attributes of network 1 (i.e., the target network)), and an operation parameter (changing the network capacity value to a value a2). The result of performing operation authentication on the request message by the core network device indicates success. After the core network device changes the network capacity value of network 1 based on the request message, the network capacity value of network 1 becomes a3 (not equal to the capacity value in the operation parameter in the request message). In this case, it is considered that the core network device fails to operate the life cycle of network 1. Furthermore, the first response message returned by the core network device to the terminal device 1 may include the identifier of network 1, the state of network 1 (presence state, available state, or activation state), the network attribute of network 1 (the network capacity value is a2), and a failure cause value 1 (indicating that the changed network capacity value is the same as the network capacity value before the change).

[0298] In a possible implementation, when the result of the operation authentication indicates failure, the core network device does not operate the life cycle of the target network. In this case, the core network device may further send a second response message to the terminal device, and the second response message indicates that the operation result of operating the life cycle of the target network indicates failure. In this case, the second response message may further carry a failure cause value (indicating the cause of the current operation failure). For example, see Table 3 for the mapping relationship between the failure cause value and the failure cause. [Table 3]

[0299] It should be noted that the core network device in FIG. 7 may be one or more functional network elements in the core network. This is not particularly limited in the present application. In one example, the core network device referred to in FIG. 7 may include three functional network elements, namely, functional network element 1, functional network element 2, and functional network element 3. The functional network element 1 is configured to receive a request message from a terminal device (i.e., execute step S702). The functional network element 2 is configured to execute operation authentication based on the request message (i.e., execute step S703). The functional network element 3 is configured to operate the life cycle of the target network (i.e., execute step S704) when the result of the operation authentication indicates success. In another example, the core network device referred to in FIG. 7 includes two functional network elements, namely, functional network element 1 and functional network element 2, and the two functional network elements are configured to execute steps S702 to S704. For example, functional network element 1 is configured to perform steps S702 and S703 and functional network element 2 is configured to perform step S704, or functional network element 1 is configured to perform step S702 and functional network element 2 is configured to perform steps S703 and S704. In yet another example, the core network device referred to in Figure 7 is a functional network element, and the functional network element is configured to perform steps S702 to S704.

[0300] In a possible implementation, when the core network device includes multiple functional network elements and there is a communication connection between the functional network elements, the functional network element configured to receive the message may perform identity authentication with the functional network element configured to send the message. For example, the first functional network element is configured to perform operation authentication based on the request message. The second functional network element is configured to operate the life cycle of the target network. In this case, when the result of the operation authentication indicates success, the first functional network element sends an indication message (or a second request message) to the second functional network element, where the indication message (or the second request message) is for requesting the second functional network element to operate 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 performs identity verification with the first functional network element. If the verification is successful, the second functional network element operates the life cycle of the target network. In this manner, system security can be further improved.

[0301] According to the network resource management method provided in FIG. 7, a terminal device can directly operate a target network using a core network device, and the core network device performs authentication operations on the identity and operating permissions of the terminal device, thereby improving efficiency and improving system security.

[0302] In order to more intuitively describe the network resource management method in the present application, the following describes the network resource management method in the present application with reference to the network architecture shown in FIG. 1b.

[0303] Figure 8 is a schematic flowchart of yet another network resource management method according to an embodiment of the present application. As shown in Figure 8, the network resource management method may be performed by a core network or a chip in the core network, or may be performed by a terminal device or a chip in the terminal device. Figure 8 is described using an example in which a specific functional network element in the core network and a terminal device are entities for performing the method.

[0304] S801: A terminal device sends a request message to an AMF, and in response, the AMF receives a request message from the terminal device.

[0305] The terminal device uses an access network device (i.e., the gNB in ​​FIG. 8) to send a request message to the AMF to request to operate the life cycle of the target network. The request message may be a non-access stratum (NAS) message. Specifically, the request message may be an independent NAS message (i.e., the function of the NAS message is used to operate the life cycle of the target network). The request message may be carried in an information element of a NAS message having another function. That is, in addition to the function for requesting to operate the life cycle of the target network, the NAS message further includes another function.

[0306] For specific descriptions of "request message", "target network", and "operating in the life cycle of the target network", please refer to the relevant descriptions in S301. The repeated parts will not be described again here.

[0307] S802: The AMF performs operation authentication based on the request message.

[0308] For the specific implementation of S802, please refer to the above description of the specific implementation of S703. The repeated parts will not be described again here.

[0309] The process by which the core network operates the life cycle of the target network shown in Figure 1b after the result of performing operational authentication by the AMF indicates success is specifically shown in S803 to S811 below.

[0310] S803: The AMF operates the life cycle of the target network.

[0311] Specifically, the AMF network element creates a target network means that the AMF network element interacts with the MANO network element or the container management network element, applies for available execution resources, and instantiates an execution entity. The execution entity may be a newly instantiated virtual machine, a newly instantiated container, or a new process, thread, or another execution entity running on an existing virtual machine or container. Furthermore, the AMF network element creates the target network based on a request message from the terminal device.

[0312] When AMF deletes a target network, it means that the AMF network element releases (or deletes) the execution resources corresponding to the target network and deletes the instantiations of the execution entities of the target network.

[0313] The AMF network element suspends the target network, i.e., sets the status of the target network to a suspended state (or called a standby state, a to-be-activated state, a deactivated state, etc.). In other words, the AMF network element suspending the target network means that the AMF network element updates the information about the target network maintained by the AMF network element. Updating the content includes one or more of the following: recording the working status of the user context to prohibit subsequent signaling of the user, terminating and reporting the user's statistics and call detail record data, or immediately (or triggered by a timer) detaching the user through signaling.

[0314] The AMF network element resumes the target network, i.e., changes the status of the target network from a suspended state to an activated state. In other words, the AMF network element resumes the target network, which means that the AMF network element updates the information about the target network maintained by the AMF network element. Updating the content includes: recording the working status of the user context to resume the user's subsequent signaling, resuming the user's statistics and call detail record data, or enabling the user's subsequent signaling.

[0315] The AMF network element modifies the network attributes of the target network by changing the capacity (i.e., capacity-related parameters) of the target network, the capability (network abilityIt can be understood as changing one or more of the following: the target network's network attribute (related parameters), the target network's configuration policy, or the target network's service user list. In other words, the AMF network element changes the network attributes of the target network, which means that the AMF network element updates the information about the target network maintained by the AMF network element. Updating the contents includes: 1. Changing the network capabilities of the target network, for example, enabling or disabling device capabilities or services corresponding to the target network, where the services are services provided by each NF defined in 3GPP, and NRF registration and update are triggered. 2. Changing the network capacity of the target network, for example, increasing the capacity value of the target network (performing a capacity expansion process) or decreasing the capacity value of the target network (performing a capacity reduction process). 3. Modify the target network's user list, for example, add user information to the target network's user list or remove user information from the target network's user list, where the user information includes one or more of a subscription persistent identifier (e.g., IMSI / SUPI / MSISDN), a user group identifier, a temporary user identifier (e.g., GUTI), or a device identifier (e.g., PEI / IME).

[0316] S804: (Optional) The AMF sends an update request regarding the target network to an access network device (i.e., gNB), and in response, the access network device (i.e., gNB) receives an update request regarding the target network from the AMF.

[0317] The AMF sends an update request for the target network to the access network device based on the operation type in the request message to operate the life cycle of the target network. The update request for the target network carries information about the operation type, and the update request for the target network instructs the access network device to update (or change) the information about the target network maintained by the access network device (including the radio link side information of the target network, such as radio scheduling priority and air interface priority). After receiving the update request for the target network, the access network device performs different operations based on different operation types. The details are as follows:

[0318] When the AMF creates a target network (i.e., the operation type is to create a target network), the update request is to request the access network device to establish a communication connection (or called a link connection, channel, etc.) to the AMF. The link is a communication connection (or called a link connection, channel, etc.) between the AMF and the gNB, and the communication connection (or called a link connection, channel, etc.) is associated with the target network.

[0319] When the AMF deletes the target network (i.e., the operation type is to delete the target network), the update request is to request the access network device to delete the communication connection (or called a link connection, channel, etc.) to the AMF.

[0320] When the AMF suspends the target network (i.e., the operation type is to change the running state of the target network, specifically to suspend the target network), the update request is to request the access network device to suspend the communication connection (or called a link connection, channel, etc.) to the AMF.

[0321] When the AMF resumes (or activates) the target network (i.e., the operation type is to change the running state of the target network, in particular to resume the target network), the update request is to request the access network device to resume (or activate) the communication connection (or called a link connection, channel, etc.) to the AMF.

[0322] When the AMF changes the network attributes of the target network (i.e., the operation type is to change the network attributes of the target network), the update request is to request (or instruct) the gNB to change (or update) the information about the target network maintained by the gNB.

[0323] S805: (Optional) The gNB changes 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 for the target network.

[0324] The gNB establishes (or deletes) a communication connection (or channel) with respect to the target network to the first function based on the request to establish (or delete) the link connection, i.e., the communication connection (or channel) is associated with the target network.

[0325] When the AMF creates a target network, the gNB establishes a communication connection (or called a link connection, channel, etc.) to the AMF.

[0326] When the AMF deletes the target network, the gNB deletes the communication connection (or link connection, channel, etc.) to the AMF.

[0327] When the AMF suspends the target network, the gNB suspends its communication connection (or link connection, channel, etc.) to the AMF.

[0328] When the AMF resumes (or activates) the target network, the gNB resumes (or activates) its communication connection (or called a link connection, channel, etc.) to the AMF.

[0329] When the AMF changes the network attributes of the target network, the gNB changes (or updates) the information about the target network maintained by the gNB.

[0330] It is necessary to know that the gNB can establish, delete, suspend or resume links according to the next generation application protocol (NGAP) or SCTP.

[0331] It should be noted that when the operation type in the request message is one or more of creating a target network, deleting a target network, or changing the running state of the target network, the specific operations of S804 and S805 are performed. When the operation type in the request message is to change a network attribute of the target network, if the network attribute of the target network requested to be changed affects the radio link side information of the target network (wherein the radio link side information includes radio scheduling priority or air interface priority), the specific operations of S804 and S805 may be performed, and if the network attribute of the target network requested to be changed does not affect the radio link side information of the target network, the specific operations of S804 and S805 may not be performed.

[0332] S806: (Optional) The AMF sends a first operation control request to the SMF, and in response, the SMF receives the first operation control request from the AMF.

[0333] The AMF sends a first operation control request to the SMF based on the operation type for operating the life cycle of the target network, which is in the request message. The first operation control request carries information about the operation type, and the first operation control request instructs (or requests) the SMF to operate the life cycle of the target network. The first operation control request is an N11 interface message. Specifically, the first operation control request may be an independent N11 interface message (i.e., a function of the N11 interface message is used to operate the life cycle of the target network). The first operation control request may be carried in an information element of the N11 interface message that has another function. That is, in addition to the function for requesting to operate the life cycle of the target network, the N11 interface message further includes another function.

[0334] S807: (Optional) The SMF runs the life cycle of the target network.

[0335] For a specific implementation of the SMF operating the life cycle of the target network, please refer to the description of the specific implementation of the AMF operating the life cycle of the target network in S803. The details will not be described again here.

[0336] S808: (Optional) The SMF sends a second operation control request to the UPF, and in response, the UPF receives a second operation control request from the SMF.

[0337] The SMF sends a second operation control request to the UPF based on the operation type for operating the life cycle of the target network in the first operation control request. The second operation control request carries information about the operation type, and the second operation control request instructs (or requests) the UPF to operate the life cycle of the target network. The second operation control request is an N4 interface message. Specifically, the second operation control request can be an independent N4 interface message (i.e., the function of the N4 interface message is used to operate the life cycle of the target network). The second operation control request can be carried in an information element of the N4 interface message that has another function. That is, in addition to the function for requesting to operate the life cycle of the target network, the N4 interface message further includes another function.

[0338] S809: (Optional) The UPF runs the life cycle of the target network.

[0339] For a specific implementation of the UPF operating the life cycle of the target network, please refer to the description of the specific implementation of the AMF operating the life cycle of the target network in S803. The details will not be described again here.

[0340] In a possible implementation, after operating the life cycle of the target network, the UPF sends a feedback message corresponding to a second operation control request to the SMF, where 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 indicates a reason why the UPF fails to operate the life cycle of the target network.

[0341] In a possible implementation form, the SMF sends a feedback message corresponding to a first operation control request to the AMF based on the operation result of operating the target network life cycle by the UPF and the operation result of operating the target network life cycle by the SMF. The feedback message corresponding to the first operation control request is an N11 interface message. If the operation result of operating the target network life cycle by the UPF indicates a failure or the operation result of operating the target network life cycle by the SMF indicates a failure, the feedback message corresponding to the first operation control request may carry a failure cause value. The failure cause value indicates a cause of the UPF failing to operate the target network life cycle, or the failure cause value indicates a cause of the SMF failing to operate the target network life cycle.

[0342] It should be noted that when the operation type in the request message is one or more of creating a target network, deleting a target network, or changing the running state of the target network, the specific operations of S806 to S809 are performed. When the operation type in the request message is to change the network attributes of the target network, if the network attributes of the target network requested to be changed affect the session (e.g., PDU session) or user plane related information of the target network, the specific operations of S806 to S809 are performed, and if the network attributes of the target network requested to be changed do not affect the session or user plane related information of the target network, the specific operations of S806 to S809 may not be performed.

[0343] S810: (Optional) The AMF sends a third operation control request to the PCF, and in response, the PCF receives a third operation control request from the AMF.

[0344] The AMF sends a third operation control request to the PCF based on the operation type for operating the life cycle of the target network in the request message. The third operation control request carries information about the operation type, and the third operation control request instructs (or requests) the PCF to operate the life cycle of the target network. The third operation control request is an N15 interface message. Specifically, the third operation control request may be an independent N15 interface message (i.e., the function of the N15 interface message is used to operate the life cycle of the target network). The third operation control request may be carried in an information element of the N15 interface message having another function. That is, in addition to the function for requesting to operate the life cycle of the target network, the N15 interface message further includes another function.

[0345] S811: (Optional) The PCF runs the life cycle of the target network.

[0346] For a specific implementation of the PCF operating the life cycle of the target network, please refer to the description of the specific implementation of the AMF operating the life cycle of the target network in S803. The details will not be described again here.

[0347] In a possible implementation, after operating the life cycle of the target network, the PCF sends a feedback message corresponding to a 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, and the failure cause value indicates a reason why the PCF fails to operate the life cycle of the target network.

[0348] It should be noted that when the operation type in the request message is one or more of creating a target network, deleting a target network, or changing the running state of the target network, the specific operations of S810 and S811 are performed. When the operation type in the request message is to change the network attributes of the target network, if the network attributes of the target network requested to be changed affect the configuration policy of the target network, the specific operations of S810 and S811 are performed, and if the network attributes of the target network requested to be changed do not affect the configuration policy of the target network, the specific operations of S810 and S811 are performed. It is not necessary .

[0349] In a possible implementation, after S811 is executed, the AMF records the status of the target network and uses the gNB to feed back the operation result of operating the life cycle of the target network to the terminal device. The status of the target network includes that the target network exists (including an activated state and a suspended state) and that the target network does not exist. In a possible implementation, the AMF may further record the network attributes of the target network.

[0350] Figure 9 is a schematic diagram of the structure of a communication device according to an embodiment of the present application. The communication device shown in Figure 9 can be configured to implement part or all of the functions of a terminal device in an embodiment corresponding to a network resource management method, or the communication device shown in Figure 9 can be configured to implement part or all of the functions of a core network device in an embodiment corresponding to a network resource management method.

[0351] In one embodiment, the communication device shown in FIG. 9 may be configured to implement some or all of the functions of the terminal device in the embodiment of the method described in FIG. 3 or FIG. 8. The device may be a terminal device, a device in a terminal device, or a device that can be used with a terminal device. Alternatively, the communication device may be a chip system. The communication device shown in FIG. 9 may include a transceiver unit 901 and a processing unit 902.

[0352] The processing unit 902 is configured to determine a request message, where the request message is used to operate a life cycle of the target network, and the request message is a control plane signaling or a user plane signaling between the terminal device and the core network device. The transceiver unit 901 is configured to transmit the request message to the core network device.

[0353] In a possible implementation, the request message includes an operation type, the operation type including one of creating the target network, deleting the target network, changing the running state of the target network, or changing network attributes of the target network.

[0354] In a possible implementation, changing the execution state of the target network includes pausing the target network or resuming the target network.

[0355] In a possible implementation, modifying the network attributes of the target network includes one or more of modifying the capacity of the target network, modifying the capabilities of the target network, modifying a configuration policy of the target network, or modifying a service user list of the target network.

[0356] In a possible implementation, the request message further includes one or more of user information of the terminal device, operation parameters corresponding to the operation type, or information about the target network.

[0357] In a possible implementation, the user information includes one or more of a subscription persistent identifier, a user group identifier, or a temporary user identifier.

[0358] In a possible implementation, the information about the target network includes one or more of the following: an identifier of the target network, a capacity value, a capability list, a service user list, or a configuration policy list.

[0359] In a possible implementation, the transceiver unit 901 is further configured to receive a response message sent by the core network device, where the response message indicates a result of operating the life cycle of the target network.

[0360] In a possible implementation, the target network is a user service function entity or another network function that provides a service to the user.

[0361] In one embodiment, the communication device shown in FIG. 9 may be configured to implement some or all of the functions of the core network device in the embodiment of the method described in FIG. 3 or FIG. 8. The device may be a core network device, a device in a core network device, or a device that can be used with a core network device. Alternatively, the communication device may be a chip system. The communication device shown in FIG. 9 may include a transceiver unit 901 and a processing unit 902.

[0362] The transceiver unit 901 is configured to receive a request message from a terminal device, where the request message is used to operate a life cycle of a target network, and the request message is a control plane signaling or a user plane signaling between the terminal device and a core network. The processing unit 902 is configured to operate a life cycle of the target network, which is managed by the core network device, based on the request message.

[0363] In a possible implementation, the request message includes an operation type, the operation type including one of creating the target network, deleting the target network, changing the running state of the target network, or changing network attributes of the target network.

[0364] In a possible implementation, changing the execution state of the target network includes pausing the target network or resuming the target network.

[0365] In a possible implementation, modifying the network attributes of the target network includes one or more of modifying the capacity of the target network, modifying the capabilities of the target network, modifying a configuration policy of the target network, or modifying a service user list of the target network.

[0366] In a possible implementation form, the processing unit 902 is further configured to perform operation authentication based on the request message. When the result of the operation authentication indicates success, the processing unit 902 operates the life cycle of the target network. Alternatively, when the result of the operation authentication indicates failure, the processing unit 902 does not operate the life cycle of the target network.

[0367] In a possible implementation, the processing unit 902 performing operation authentication based on the request message includes one or more of the following: authenticating the status of the target network based on the operation type, or authenticating operation permission for the operation type.

[0368] In a possible implementation, if the operation type matches the status of the target network, the processing unit 902 successfully authenticates the status of the target network, or if the operation type does not match the status of the target network, the processing unit 902 fails to authenticate the status of the target network.

[0369] In possible implementations, inconsistencies in the operation type with the status of the target network include: when the operation type is to create the target network, the status of the target network is present; when the operation type is to delete the target network, the status of the target network is non-present; when the operation type is to change the network attributes of the target network, the status of the target network is non-present; or when the operation type is to change the running state of the target network, the status of the target network is non-present.

[0370] In a possible implementation, the presence state includes a paused state and an activated state, and when the operation type is to change the running state of the target network, the inconsistency of the operation type with the status of the target network further includes: when the operation type is to pause the target network, the status of the target network is in a paused state, or when the operation type is to resume the target network, the status of the target network is in an activated state.

[0371] In a possible implementation, the request message further includes one or more of user information of the terminal device, operation parameters corresponding to the operation type, or information about the target network.

[0372] In a possible implementation, the user information includes one or more of a subscription persistent identifier, a user group identifier, or a temporary user identifier.

[0373] In a possible implementation, the information about the target network includes one or more of the following: an identifier of the target network, a capacity value, a capability list, a service user list, or a configuration policy list.

[0374] In a possible implementation, the processing unit 902 obtains user subscription information based on the user information, and authorizes operation permissions for the operation type based on the user subscription information and / or according to a local configuration policy.

[0375] In a possible implementation, the user subscription information includes one or more of an authorized operational action list, an authorized network identifier list, an authorized network capacity allocation, an authorized service user list, or a configuration policy list.

[0376] In a possible implementation form, when the result of the operation authentication indicates success, the transceiver unit 901 sends a first response message to the terminal device based on the operation result of operating the life cycle of the target network, the first response message includes a status of the target network and an identifier of the target network. Alternatively, when the result of the operation authentication indicates failure, the transceiver unit 901 sends a second response message to the terminal device, the second response message indicates that the operation result of operating the life cycle of the target network indicates failure.

[0377] In a possible implementation, the target network is a user service function entity or another network function that provides a service to the user.

[0378] For a more detailed description of the transceiver unit 901 and the processing unit 902, please refer to the relevant description of the terminal device or the core network in the above-mentioned method embodiment. The details will not be described again here.

[0379] 10 is a schematic diagram of the structure of a communication device 1000 according to 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. It can be understood that the interface circuit 1020 can be a transceiver or an input / output interface. Optionally, the communication device 1000 may further include a memory 1030 configured to store instructions executed by the processor 1010, or to store input data required by the processor 1010 to execute the instructions, or to store data generated after the processor 1010 executes the instructions.

[0380] When the communications device 1000 is configured to perform the method in the above-mentioned method embodiments, the processor 1010 is configured to perform the functions of the above-mentioned processing unit 902, and the interface circuit 1020 is configured to perform the functions of the above-mentioned transceiver unit 901.

[0381] When the communication device is a chip used in a terminal device, the chip in the terminal device implements the functions of the terminal device in the above-mentioned method embodiments. The chip in the terminal device receives information from another network element, or the chip in the terminal device transmits information to another network element.

[0382] When the communication device is a chip used in a core network, the chip in the core network implements the function of the core network in the embodiment of the above method, and the chip in the core network receives information from another network element, or the chip in the core network transmits information to another network element.

[0383] It may be understood that the processor in the embodiments of the present application may be a central processing unit (CPU), another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or another programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0384] The method steps in the embodiments of the present application may be implemented in a hardware manner or in a manner of executing software instructions by a processor. The software instructions may include corresponding software modules. The software modules may be stored in a random access memory (RAM), a flash memory, a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a register, a hard disk, a removable hard disk, a CD-ROM, or any other form of storage medium well known in the art. For example, the storage medium is coupled to the processor such that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium may be components of the processor. The processor and the storage medium may be located in an ASIC. In addition, the ASIC may be located in an access network device or a terminal device. Of course, the processor and the storage medium may alternatively be present in a terminal device or a core network as separate components.

[0385] All or part of the above-mentioned embodiments may be implemented by software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer programs or instructions are loaded and executed on a computer, the procedures or functions in the embodiments of the present application are executed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer programs or instructions may be stored in or transmitted by means of a computer-readable storage medium. The computer-readable storage medium may be any available medium accessible by a computer, or a data storage device such as a server that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape, an optical medium, such as a digital versatile disc (DVD), or a semiconductor medium, such as a solid-state drive (SSD).

[0386] In the embodiments of the present application, unless otherwise stated or there is no logical contradiction, the terms and / or descriptions in different embodiments are consistent and may be mutually referenced, and the technical features in different embodiments may be combined based on their internal logical relationships to form a new embodiment.

[0387] It can be understood that various numbers in the embodiments of the present application are merely used for distinction for convenience of description, and are not used to limit the scope of the embodiments of the present application. The sequence numbers of the above processes do not imply the execution order, and the execution order of the processes should be determined based on the functions and internal logic of the processes.

[0388] An embodiment of the present application further provides a computer-readable storage medium, which stores computer-executable instructions, which, when executed, implement the method performed by the terminal device or the core network in the above-mentioned method embodiment.

[0389] An embodiment of the present application further provides a computer program product, which includes a computer program, which, when executed, implements the method performed by the terminal device or the core network in the aforementioned method embodiments.

[0390] An embodiment of the present application further provides a communication system, the communication system including a terminal device or a core network, the terminal device being configured to execute the method performed by the terminal device in the aforementioned method embodiment, and the core network being configured to execute the method performed by the core network in the aforementioned method embodiment.

[0391] It should be noted that for the sake of simplicity, the above method embodiments are depicted as a sequence of actions. However, those skilled in the art will appreciate that the present application is not limited to the described sequence of actions, as some steps may be performed in other orders or simultaneously, according to the present application. All of the embodiments described herein are not intended to be limiting. Exemplary It should be further understood by those skilled in the art that the actions and modules associated with the embodiments are not necessarily required by the present application.

[0392] The description of the embodiments provided in this application may refer to each other, and the description of the embodiments has different focus. For the parts not described in detail in the embodiments, please refer to the relevant description in another embodiment. For the convenience of explanation, for the functions and steps performed by the apparatus and device provided in the embodiments of this application, please refer to the relevant description in the method embodiment of this application. In addition, the method embodiment and the apparatus embodiment may be mutually referenced, combined, or cited.

[0393] Finally, it should be noted that the above embodiments are only intended to illustrate the technical solutions of the present application, and are not intended to limit the present application. Although the present application has been specifically described with reference to the above embodiments, it should be understood by those skilled in the art that, without departing from the scope of the technical solutions of the embodiments of the present application, modifications may be made to the technical solutions recorded in the above embodiments, or some or all of the technical features may be replaced with equivalents.

Claims

1. 1. A network resource management method, comprising: generating, by a terminal device, a request message, the request message being used to operate a life cycle of a target network, the request message being a control plane signaling or a user plane signaling between the terminal device and a core network; sending, by the terminal device, the request message to the core network; operating, by the core network, the life cycle of the target network managed by the core network based on the request message; The method includes:

2. 2. The method of claim 1, wherein the request message includes information regarding an operation type, the operation type including one or more of creating the target network, deleting the target network, changing a running state of the target network, or changing a network attribute of the target network.

3. The method of claim 2 , wherein the changing the execution state of the target network includes pausing the target network or resuming the target network.

4. The step of operating, by the core network, the life cycle of the target network managed by the core network based on the request message, comprises: performing, by the core network, operation authentication based on the request message; when the result of the operational authentication indicates success, operating the life cycle of the target network by the core network; The method of claim 2 or 3, comprising:

5. The step of performing, by the core network, operation authentication based on the request message, further comprises: authenticating, by the core network, the status of the target network based on the operation type; or authenticating, by the core network, permission to operate for the type of operation; The method of claim 4, comprising one or more of:

6. The step of authenticating, by the core network, the status of the target network based on the operation type, further comprises: if the operation type matches the status of the target network, successfully authenticating the status of the target network by the core network. The method of claim 5 , comprising:

7. The status of the target network includes a presence state or a non-presence state, and the operation type matching the status of the target network is when the action type is to create the target network, the status of the target network is the non-existent state; when the action type is to delete the target network, the status of the target network is the present state; when the action type is to change the network attributes of the target network, the status of the target network is the presence state; or when the action type is to change the execution state of the target network, the status of the target network is the presence state; The method of claim 6, comprising:

8. When the presence state includes a paused state or an activated state, and the action type is to change the execution state of the target network, the action type matching the status of the target network is: when the action type is to suspend the target network, the status of the target network is in the activated state; or when the action type is to resume the target network, the status of the target network is in the paused state; The method of claim 7 further comprising:

9. The request message further includes user information of the terminal device, and the step of authenticating, by the core network, operation permission of the operation type includes: obtaining, by the core network, user subscription information based on the user information; authenticating, by the core network, the operation authorization of the operation type based on the user subscription information and / or according to a local configuration policy; The method according to any one of claims 5 to 8, comprising:

10. 10. The method of claim 9, wherein the user subscription information includes one or more of an authorized operational action list, an authorized network identifier list, an authorized network capacity allocation, an authorized service user list, or a configuration policy list.

11. sending a first response message to the terminal device based on an operation result of operating the life cycle of the target network by the core network, the first response message including the status of the target network or an identifier of the target network; The method of any one of claims 4 to 10, further comprising:

12. 1. A network resource management method, comprising: generating, by a terminal device, a request message, the request message being used to operate a life cycle of a target network, the request message being a control plane signaling or a user plane signaling between the terminal device and a core network device; sending, by the terminal device, the request message to the core network device; The method includes:

13. 13. The method of claim 12, wherein the request message includes an action type, the action type including one of creating the target network, deleting the target network, changing a running state of the target network, or changing a network attribute of the target network.

14. The method of claim 13 , wherein the changing the execution state of the target network comprises pausing the target network or resuming the target network.

15. receiving, by the terminal device, a response message sent by the core network device, the response message indicating a result of operating the lifecycle of the target network; 15. The method of any one of claims 12 to 14, further comprising:

16. 1. A network resource management method, comprising: receiving, by a core network device, a request message from a terminal device, the request message being used to operate a life cycle of a target network, the request message being control plane signaling or user plane signaling between the terminal device and the core network; operating, by the core network device, the life cycle of the target network, managed by the core network device, based on the request message; The method includes:

17. 17. The method of claim 16, wherein the request message includes an action type, the action type including one of creating the target network, deleting the target network, changing a running state of the target network, or changing a network attribute of the target network.

18. The method of claim 17 , wherein the changing the execution state of the target network comprises pausing the target network or resuming the target network.

19. The step of operating the life cycle of the target network, managed by the core network device, based on the request message, further comprises: performing, by the core network device, operation authentication based on the request message; when the result of the operational authentication indicates success, operating the life cycle of the target network; 19. The method of claim 17 or 18, comprising:

20. The step of performing, by the core network device, operation authentication based on the request message, further comprises: authenticating, by the core network device, the status of the target network based on the operation type; or authenticating, by the core network device, permission to operate for the type of operation; 20. The method of claim 19, comprising one or more of:

21. The step of authenticating, by the core network device, the status of the target network based on the operation type, further comprises: if the operation type matches the status of the target network, successfully authenticating, by the core network device, the status of the target network.

21. The method of claim 20, comprising:

22. The status of the target network includes a presence state or a non-presence state, and the operation type matching the status of the target network is when the action type is to create the target network, the status of the target network is the non-existent state; when the action type is to delete the target network, the status of the target network is the present state; when the action type is to change the network attributes of the target network, the status of the target network is the presence state; or when the action type is to change the execution state of the target network, the status of the target network is the presence state; 22. The method of claim 21 , comprising:

23. The presence state includes a paused state and an activated state, and when the action type is to change the execution state of the target network, the action type matching the status of the target network includes: when the action type is to suspend the target network, the status of the target network is in the activated state; or when the action type is to resume the target network, the status of the target network is in the paused state; 23. The method of claim 22, further comprising:

24. The request message further includes user information of the terminal device, and the step of authenticating, by the core network device, operation permission of the operation type includes: obtaining, by the core network device, user subscription information based on the user information; authenticating, by the core network device, the operation permission of the operation type based on the user subscription information and / or according to a local configuration policy; 24. The method of any one of claims 19 to 23, comprising:

25. 25. The method of claim 24, wherein the user subscription information includes one or more of an authorized operational action list, an authorized network identifier list, an authorized network capacity allocation, an authorized service user list, or a configuration policy list.

26. sending a first response message to the terminal device based on an operation result of operating the life cycle of the target network by the core network device, the first response message including the status of the target network; 26. The method of any one of claims 16 to 25, further comprising:

27. 26. The method of claim 2, wherein modifying the network attributes of the target network includes one or more of modifying the capacity of the target network, modifying the capability of the target network, modifying a configuration policy of the target network, or modifying the service user list of the target network.

28. The method according to claim 1 , wherein the request message further includes one or more of the following: user information of the terminal device, operation parameters corresponding to the operation type, or information about the target network.

29. 30. The method of claim 28, wherein the user information includes one or more of a subscription persistent identifier, a user group identifier, or a temporary user identifier.

30. 30. The method of claim 28 or 29, wherein the information about the target network includes one or more of an identifier of the target network, a capacity value, a capability list, the service user list, or the configuration policy list.

31. The method according to any one of claims 1 to 30, wherein the target network is a user service function entity or another network function that provides a service to a user.

32. A communication device, comprising a module configured to perform the method according to any one of claims 12 to 15 or 27 to 31, or a module configured to perform the method according to any one of claims 16 to 31.

33. A communications device comprising a processor, the processor coupled to a memory, the memory storing instructions, the processor configured to execute the instructions to enable the communications device to perform a method according to any one of claims 12 to 15 or 27 to 31, or a method according to any one of claims 16 to 31.

34. 34. The communications device of claim 33, further comprising one or more of the memory and a transceiver, the transceiver configured to receive and transmit data and / or signaling.

35. A chip comprising a processor and an interface, the processor coupled to the interface; The interface is configured to receive or output a signal, and the processor is configured to execute code instructions such that a method according to any one of claims 12 to 15 or 27 to 31 or a method according to any one of claims 16 to 31 is performed. Tips.

36. A communication system, the communication system comprising a terminal device and a core network device, the terminal device configured to perform the method according to any one of claims 12 to 15 or 27 to 31, and the core network device configured to perform the method according to any one of claims 16 to 31.

37. A computer-readable storage medium, the computer-readable storage medium storing computer-executable instructions which, when invoked by a computer, perform the method of any one of claims 12 to 15 or 27 to 31, or which, when invoked by a computer, perform the method of any one of claims 16 to 31.

38. A computer program product comprising a computer program which, when executed, performs the method of any one of claims 12 to 15 or 27 to 31 or the method of any one of claims 16 to 31.

Images