CN112400352A

CN112400352A - Resource management method, equipment and storage medium

Info

Publication number: CN112400352A
Application number: CN201980046810.1A
Authority: CN
Inventors: 刘建华
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2019-01-21
Filing date: 2019-01-21
Publication date: 2021-02-23
Anticipated expiration: 2039-01-21
Also published as: CN112400352B; WO2020150875A1

Abstract

The invention discloses a resource management method, which comprises the following steps: the method comprises the steps that a terminal device sends resource request information to a network device, and the resource request information is used for the network device to distribute resources for the terminal device. The invention also discloses another resource management method, equipment and a storage medium.

Description

Resource management method, equipment and storage medium

Technical Field

The present invention relates to the field of wireless communications technologies, and in particular, to a resource management method, device, and storage medium.

Background

In cellular network communication, data communication between terminal devices is generally received and transmitted through a network device, and the network device or an operator counts data actually transmitted by the terminal devices on a core network side to charge the transmitted data. However, in the direct communication mechanism of the terminal device, two terminal devices directly transmit data, that is, one terminal device directly transmits data to the other terminal device; at this time, the transmitted data does not pass through the network device, so that the network device cannot count the actually transmitted data amount, and thus cannot charge the transmitted data.

Disclosure of Invention

In order to solve the foregoing technical problem, embodiments of the present invention provide a resource management method, device, and storage medium, so that when performing direct communication between UEs, a network device can count the amount of actually transmitted data, thereby implementing charging for the transmitted data.

In a first aspect, an embodiment of the present invention provides a resource processing method, including: the method comprises the steps that a terminal device sends resource request information to a network device, and the resource request information is used for the network device to distribute resources for the terminal device.

In a second aspect, an embodiment of the present invention provides a resource processing method, including: and the control plane entity receives a resource request message, wherein the resource request message is used for the access network element to allocate resources for the terminal equipment.

In a third aspect, an embodiment of the present invention provides a resource processing method, including: the network element of the access network receives the resource request information; and allocating resources for the terminal equipment based on the resource request information.

In a fourth aspect, an embodiment of the present invention provides a terminal device, where the terminal device includes: a first sending unit, configured to send resource request information to a network device, where the resource request information is used by the network device to allocate resources to the terminal device.

In a fifth aspect, an embodiment of the present invention provides a control plane entity, where the control plane entity includes: a fourth receiving unit, configured to receive a resource request message, where the resource request message is used by an access network element to allocate resources to a terminal device.

In a sixth aspect, an embodiment of the present invention provides an access network element, where the access network element includes:

a fifth receiving unit configured to receive the resource request information;

and the fourth processing unit is configured to allocate resources for the terminal equipment based on the resource request information.

In a seventh aspect, an embodiment of the present invention provides a terminal device, including: a processor and a memory for storing a computer program operable on the processor, wherein the processor is configured to perform the steps of the method performed by the terminal device when executing the computer program.

In an eighth aspect, an embodiment of the present invention provides a control plane entity, including: a processor and a memory for storing a computer program operable on the processor, wherein the processor is operable to perform the steps of the method performed by the control plane entity when executing the computer program.

In a ninth aspect, an embodiment of the present invention provides an access network element, including: a processor and a memory for storing a computer program operable on the processor, wherein the processor is configured to perform the steps of the method performed by the access network element when executing the computer program.

In a tenth aspect, an embodiment of the present invention provides a storage medium, which stores an executable program, and when the executable program is executed by a processor, the storage medium implements the method executed by the terminal device.

In an eleventh aspect, an embodiment of the present invention provides a storage medium storing an executable program, where the executable program, when executed by a processor, implements the method performed by the control plane entity.

In a twelfth aspect, an embodiment of the present invention provides a storage medium, which stores an executable program, where the executable program, when executed by a processor, implements the method executed by the access network element.

According to the resource management method provided by the embodiment of the invention, the terminal equipment sends the resource request information for the network equipment to allocate the resources for the terminal equipment to the network equipment, so that the network equipment can acquire the resources used by the terminal equipment in the direct communication mechanism of the terminal equipment. The network equipment or the operator in the direct communication mechanism of the terminal equipment can charge based on the resources applied by the terminal equipment.

Drawings

Fig. 1 is a schematic structural diagram of a communication system according to an embodiment of the present invention;

fig. 2 is a schematic processing flow diagram of a resource management method applied to a terminal device according to an embodiment of the present invention;

FIG. 3 is a first schematic view of an alternative processing flow of a resource processing method according to an embodiment of the present invention;

FIG. 4 is a schematic view illustrating an alternative processing flow of a resource processing method according to an embodiment of the present invention;

FIG. 5 is a schematic view illustrating an alternative processing flow of a resource processing method according to an embodiment of the present invention;

FIG. 6 is a fourth schematic view of an alternative processing flow of the resource processing method according to the embodiment of the present invention;

FIG. 7 is a fifth flowchart illustrating an alternative processing method according to an embodiment of the present invention;

FIG. 8 is a sixth exemplary flowchart illustrating an alternative processing method according to an embodiment of the present invention;

fig. 9 is a process flow diagram of a resource management method applied to a control plane entity according to an embodiment of the present invention;

fig. 10 is a schematic processing flow chart of a resource management method applied to an access network element according to an embodiment of the present invention;

fig. 11 is a schematic structural diagram of a terminal device according to an embodiment of the present invention;

fig. 12 is a schematic structural diagram of a control plane entity according to an embodiment of the present invention;

fig. 13 is a schematic diagram of a structure of an access network element according to an embodiment of the present invention;

fig. 14 is a schematic diagram of a hardware component structure of an electronic device according to an embodiment of the present invention.

Detailed Description

So that the manner in which the features and technical contents of the embodiments of the present invention can be understood in detail, a more particular description of the embodiments of the present invention will be rendered by reference to the appended drawings, which are included for purposes of illustration and not limitation.

Before the embodiments of the present invention are explained in detail, a Network Control Interactive Services (NCIS) service is briefly explained.

In a New Radio (NR) system, the NCIS service is introduced as a New service profile into the standard for the relevant standardized service. The NCIS service mainly aims at applications such as Virtual Reality (VR)/Augmented Reality (AR), games, and has high requirements on service quality such as rate, time delay, packet loss rate, and high-speed decoding. For example, for VR games, the required rate is at least 10Gbps, and the packet loss rate cannot exceed 10E-4. The session established by the NCIS service is an NCIS session, and the UEs with the same NCIS session can form an NCIS group. UEs joining the NCIS session may all be local, e.g., establishing a side link using a direct-to-Device (D2D) terminal technology, also known as using a PC5 interface; UEs joining the NCIS session may also be remote from each other, for example using UE-network device-server-peer network-peer UE, also referred to as using the Uu interface. The UEs joining the NCIS session may be from the same Public Land Mobile Network (PLMN) or from different PLMNs. For example, there are 5 UEs in an NCIS group, where 3 UEs belong to PLMN 1, 2 UEs belong to PLMN 2, and 3 UEs belonging to PLMN 1 use side link to communicate directly with each other; meanwhile, 3 UEs belonging to PLMN 1 communicate with 2 UEs belonging to PLMN 2 through the network device.

The invention provides a resource management method, which can be applied to various communication systems, such as: a Global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a General Packet Radio Service (GPRS), a Long Term Evolution (Long Term Evolution, LTE) System, an LTE Frequency Division Duplex (FDD) System, an LTE Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication System, or a 5G System.

Illustratively, a communication system 100 applied in the embodiment of the present application is shown in fig. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, a terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within that coverage area. Optionally, the Network device 110 may be a Base Transceiver Station (BTS) in a GSM system or a CDMA system, a Base Station (NodeB, NB) in a WCDMA system, an evolved Node B (eNB or eNodeB) in an LTE system, or a wireless controller in a Cloud Radio Access Network (CRAN), or may be a Network device in a Mobile switching center, a relay Station, an Access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a Network-side device in a 5G Network, or a Network device in a Public Land Mobile Network (PLMN) for future evolution, or the like.

The communication system 100 further comprises at least one terminal device 120 located within the coverage area of the network device 110. As used herein, "terminal equipment" includes, but is not limited to, connections via wireline, such as Public Switched Telephone Network (PSTN), Digital Subscriber Line (DSL), Digital cable, direct cable connection; and/or another data connection/network; and/or via a Wireless interface, e.g., to a cellular Network, a Wireless Local Area Network (WLAN), a digital television Network such as a DVB-H Network, a satellite Network, an AM-FM broadcast transmitter; and/or means of another terminal device arranged to receive/transmit communication signals; and/or Internet of Things (IoT) devices. A terminal device arranged to communicate over a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal", or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; personal Communications Systems (PCS) terminals that may combine cellular radiotelephones with data processing, facsimile, and data Communications capabilities; PDAs that may include radiotelephones, pagers, internet/intranet access, Web browsers, notepads, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. Terminal Equipment may refer to an access terminal, User Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, User terminal, wireless communication device, User agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device having Wireless communication capabilities, a computing device or other processing device connected to a Wireless modem, a vehicle mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved PLMN, etc.

Alternatively, the 5G system or the 5G network may also be referred to as a New Radio (NR) system or an NR network.

Fig. 1 exemplarily shows one network device and two terminal devices, and optionally, the communication system 100 may include a plurality of network devices and may include other numbers of terminal devices within the coverage of each network device, which is not limited in this embodiment of the present application.

Optionally, the communication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

It should be understood that a device having a communication function in a network/system in the embodiments of the present application may be referred to as a communication device. Taking the communication system 100 shown in fig. 1 as an example, the communication device may include a network device 110 and a terminal device 120 having a communication function, and the network device 110 and the terminal device 120 may be the specific devices described above and are not described herein again; the communication device may also include other devices in the communication system 100, such as other network entities, for example, a network controller, a mobility management entity, and the like, which is not limited in this embodiment.

As shown in fig. 2, a processing flow of the resource management method applied to the terminal device provided in the embodiment of the present invention includes the following steps:

step S201, a terminal device sends resource request information to a network device, where the resource request information is used for the network device to allocate resources to the terminal device.

In some embodiments, a terminal device sends a session establishment request message to a core network element, where the session establishment request message is used for the core network element to send a service request message to an access network element, so that the access network element allocates resources for the terminal device. Here, the terminal device requests the network device for resources in the session establishment process, and does not apply for and authorize resources in the group establishment process. The session establishment request message includes at least one of: NCIS related group information, service related information and the resource request information. In specific implementation, a first optional processing flow diagram of the resource management method is shown in fig. 3, and includes the following steps:

step S301, the terminal device sends a session establishment request message related to NCIS to the SMF entity.

Here, the session establishment request message includes at least one of: NCIS related group information, service related information and the resource request information.

Step S302, the SMF entity obtains the subscription information of the terminal equipment from the UDM entity.

The subscription information includes: whether the terminal equipment allows the application of the service on the PC5 interface and/or the requirements or resource attributes of the service on the PC5 interface allowed by the terminal equipment; such as maximum allowed traffic rate, minimum latency requirements, etc. And if the SMF entity passes the verification, initiating a session establishment request message to the RAN network element, wherein the session establishment request message carries the resource allocation related information. Or the SMF entity sends the session establishment request message sent by the terminal equipment to the UDM entity/PCF entity, and the UDM entity/PCF entity verifies the session establishment request message of the terminal equipment and responds to the SMF entity if the verification is passed.

Step S303, after the SMF entity successfully verifies the session establishment request message of the terminal device, it initiates a service request to the RAN network element according to the carried group information, service-related information and resource requirement information, and provides the resource requirement information.

Wherein the resource demand information includes at least one of the following information: required service rate information, delay information, reliability information, bandwidth information, and the like. The resource requirement information may be session granularity, QoS flow granularity, traffic flow granularity, or the like.

After receiving the service request, the RAN network element allocates resources that can be used on the PC5 interface according to the resource request information therein, where the resources may be QoS flow granularity, or session granularity, or service flow granularity; and replies a response message to the core network element. If the RAN network element cannot allocate the required resource request, a failure message may be fed back to the core network element, or the RAN network element allocates a resource that can be actually allocated, and feeds back the actually allocated resource to the core network element, and the core network element may further feed back the actually allocated resource to the charging device entity.

Step S304-step S305, the SMF entity sends a session establishment accept message to the terminal device, and provides the terminal device with the resources allocated by the RAN network element.

In other embodiments, in the group establishing process, the network device allocates resources to the terminal device, that is, the terminal device provides NCIS-related group information and service-related information in the group establishing process, and the network device allocates resources according to the NCIS-related group information and service-related information; and the resources are activated and validated once allocated. In specific implementation, an optional processing flow diagram of the resource management method is shown as a second processing flow diagram, as shown in fig. 4, and the method includes the following steps:

step S401, the terminal device sends the requested resource information.

Here, the requested resource information is used for the network device to determine allocable resources of the terminal device.

Optionally, the terminal device sends a group establishment request message to a server or an NCIS function server, so that a core network element determines allocable resources of the terminal device based on the group establishment request message sent by the server or the NCIS function server. Wherein, the group establishment request message carries the requested resource information; or, the group establishment request message is used for the server or the NCIS function server to acquire the requested resource information.

Wherein, the group establishing request message can carry the relevant information of establishing service, such as service type, service requirement and interface carrying the service application; optionally, the service types include an interactive service, an interactive game service, a background service, and the like; the service requirements include: required service rate, delay requirement, reliability requirement and the like; the interface carrying the service application may be a PC5 interface.

Step S402, an application server initiates a group establishment request to a core network element, wherein the group establishment request carries requested service information;

optionally, the service information includes service requirement information; the group establishment request may also carry interface information of the service application.

Step S403, the network element of the core network verifies the subscription information or the authorization information of the terminal device.

During specific implementation, the UDM entity/PCF entity in the network element of the core network verifies the subscription information or authorization information of the terminal device. The subscription information or the authorization information includes: whether the terminal equipment allows the application of the service on the PC5 interface or not, and the requirements or resource attributes of the application of the service on the PC5 interface allowed by the terminal equipment; such as maximum allowed traffic rate, minimum latency requirements, etc. If the verification is passed, the UDM entity/PCF entity sends the allowed service, the group information and the allocable resource information to the terminal. If the verification fails, the UDM/PCF entity may reject the request or determine allocable resources based on the actual subscription information or authorization information.

Step S404, the core network element sends the service information applied by the determined terminal device and the allocable resource information to the terminal device.

In specific implementation, the UDM entity/PCF entity of the core network may send the service information and allocable resource information applied by the terminal device to the terminal device through a protocol message unit of the 3GPP network, for example, the UDM entity/PCF entity sends the service information and allocable resource information applied by the terminal device to the AMF entity or the SMF entity, and the AMF entity or the SMF entity encapsulates the service information and allocable resource information applied by the terminal device into an NAS message and sends the NAS message to the terminal device. Or, the UDM entity/PCF entity of the core network may send the service information and allocable resource information applied by the terminal device to the AMF entity or SMF entity, where the AMF entity or SMF entity encapsulates the service information and allocable resource information applied by the terminal device into an N2 message and sends the message to the RAN network element; and the RAN network element sends the service information applied by the terminal equipment and the allocable resource information to the terminal equipment through the RRC message. Or, the UDM entity/PCF entity of the core network encapsulates the service information and allocable resource information applied by the terminal device into a transparent container, and sends the transparent container to the terminal device through NAS message or through N2 and RRC message. Or, the core network element sends the service information and the allocable resource information applied by the terminal device to the application-related server or the NCIS function server (such as AF), and the application-related server or the NCIS function server (such as AF) sends the service information and the allocable resource information to the terminal device through an interface message protocol between the terminal device and the application-related server or the NCIS function server (such as AF).

Step S405, the terminal device initiates a session establishment request.

Optionally, the session establishment request carries at least one of the following information: NCIS related group information, service related information and resource request information; the requested resource of the terminal device cannot be higher than the resource request information authorized in step S404.

Step S406 to step S407, the SMF entity receives the session establishment request sent by the terminal device, initiates a service request to the RAN network element according to the group information and the service related information carried in the session establishment request, and provides the resource requirement information.

Optionally, the resource demand information includes at least one of: required traffic rate information, delay information// reliability information, and bandwidth information. The granularity of the resource requirement information may be session granularity, or QoS flow granularity or traffic flow granularity, etc.

After receiving the session establishment request, the RAN network element allocates resources available on the PC5 interface according to the resource request information therein; and replying a response message of successful resource allocation to the network element of the core network. If the RAN network element cannot allocate the required resources, a failure message may be fed back to the core network element, or the RAN network element allocates resources that can be actually allocated, and feeds back the actually allocated resources to the core network element, and the core network element may further feed back the actually allocated resources to the charging device entity.

Step S408-step S409, the SMF entity sends a session establishment accept message to the terminal device. And the RAN network element sends the allocated resources to the terminal equipment through the core network element.

In specific implementation, the UDM entity/PCF entity of the core network may send the service information and allocable resource information applied by the terminal device to the terminal through a protocol message unit of the 3GPP network, for example, send data to the AMF entity or SMF entity through the UDM entity/PCF entity, and the AMF entity or SMF entity encapsulates the service information and the allocable resource information into an NAS message and sends the NAS message to the terminal device. Or the UDM entity/PCF entity of the core network may send the service information and allocable resource information applied by the terminal device to the AMF entity or SMF entity, which encapsulates the service information and allocable resource information into N2 message and sends it to the RAN network element; and the RAN network element sends the RRC message to the terminal equipment. Or, the UDM entity/PCF entity of the core network encapsulates the service information and the allocable resource information into a transparent container, and sends the transparent container to the terminal device through NAS message or through N2 and RRC message. Or, the core network element sends the service information and the allocable resource information to a server related to the application or an NCIS function server (AF), and the server related to the application or the NCIS function server (AF) sends the service information and the allocable resource information to the terminal equipment through an interface message protocol between the server related to the application or the NCIS function server (AF) and the terminal equipment.

In still other embodiments, the terminal device requests resources during session establishment, and activates the resources based on the resource request; it will be appreciated that the resource allocation context is established during the session establishment, and that the PC5 resource configuration information will be saved when the resource is deactivated. However, the RAN/CN does not allocate actual PC5 resources to the terminal device. When the terminal equipment has actual resource requirements, activating the required resources through a service request process; at this time, the terminal device is allowed to request resource allocation according to actual demand while maintaining session connection. In specific implementation, a schematic view of an optional processing flow of the resource management method shown in fig. 5 includes the following steps:

step S501, the terminal device performs session establishment.

The session establishment process in the embodiment of the present invention is the same as the session establishment process in the related art, and is not described herein again.

Step S502, the terminal device initiates a service establishment request.

Optionally, if the terminal device deactivates the session or deactivates the resource in the session, the terminal device also needs to initiate a service establishment request when the service needs to be established, where the service establishment request is used to activate the session corresponding to the service and the corresponding resource. The service establishment request carries session information to be activated; optionally, the service establishment request further carries QoS flow information or service flow information to be activated.

Step S503, after receiving the service establishment request initiated by the terminal, the AMF entity sends the activated session or QoS flow information or service flow information to the SMF entity.

Step S504-step S505, the SMF entity sends the session or QoS flow or traffic flow information that needs to be activated to the RAN network element.

If the RAN network element does not have the resource-related configuration information, the SMF entity provides the resource configuration information to the access network at the same time. And the RAN network element distributes resources for the terminal equipment based on the information sent by the SMF entity and feeds the resources back to the core network element.

In some embodiments, the terminal device applies for resources through a service request process; it can be understood that the terminal device does not establish the context of resource allocation and does not allocate resources in the session establishment process; the terminal equipment requests to allocate resources each time a service request is initiated. In specific implementation, an optional processing flow diagram of the resource management method is shown as a fourth, as shown in fig. 6, including the following steps:

step S601, the terminal device initiates a service request message.

Here, the service request message carries requested service information, such as NCIS service and related session information; the service request message may also carry service-related QoS information and/or resource request information.

Step S602, the AMF entity sends the service request message to the SMF entity.

Step S603 — step S605, the SMF entity initiates a session establishment and resource allocation request to the RAN network element according to the service request message. And the RAN network element allocates corresponding PC5 resources according to the session establishment and resource allocation request, and feeds back resource information to the SMF entity.

It should be noted that, if the terminal device does not carry the QoS requirement or the resource request information in step S601, the SMF entity obtains corresponding QoS information or resource information from the UDN entity/PCF entity according to the requested NCIS service information or the related session information;

in still other embodiments, the terminal device applies for resources through an RRC procedure; in specific implementation, an optional processing flow diagram of the resource management method is shown as a fifth, as shown in fig. 7, including the following steps:

step S701, the terminal device establishes a session, and the terminal device and the RAN network element have configured QoS information and/or resource configuration information.

Step S702, when the terminal device has an actual service requirement, the terminal device sends a resource request message to the RAN network element.

Optionally, the resource request message carries service information that requires resources, such as session information, QoS flow information, service flow information, and the like.

Step S703 — step S704, the RAN network element allocates the resource on the PC5 to the terminal device, and the RAN network element notifies the core network element of the allocated resource information.

Here, the core network element may be an AMF entity or an SMF entity; the resource information may be: the provided bandwidth, the provided service rate, the provided delay information, etc.

Optionally, the RAN network element may allocate corresponding resources based on information provided by the AMF entity or the SMF entity; the information may be QoS information allowed by the terminal device, and the allowed QoS information may also be information of a group to which the terminal device belongs. Here, the AMF entity or the SMF entity determines QoS information allowed by the terminal according to group information and/or session information to which the terminal device belongs.

In other embodiments, the terminal device applies for resources through a process of providing corresponding resources by a user plane; the resource information as allocated for the terminal device is configured to the terminal device through the interface between the terminal device and the AF. In specific implementation, a schematic diagram of an optional processing flow of the resource management method shown in fig. 8 includes the following steps:

in step S801, the terminal device sends a resource request message through an interface with the AF.

Optionally, the resource request message carries a requested service type, a QoS requirement of the service, or a resource requirement, etc.

Step S802-step S803, AF sends the resource request message of the terminal equipment to the network element of the core network, the network element of the core network verifies the subscription information of the terminal equipment; if the service is allowed to be initiated, the resource is allowed to be applied; and if the verification is passed, the core network element sends a resource request message to the RAN network element.

Step S804-step S807, the RAN network element feeds back the allocated resource information to the core network element, and the core network element further feeds back the allocated resource information to the AF.

In step S808, the AF transfers the allocated resource information to the terminal through an interface between the terminal device and the AF.

It should be noted that, in the foregoing embodiments of the present invention, the resource request information includes: resource parameters and/or QoS parameters. The resource parameters include: the number of resources and/or the transmission rate; the number of the resources takes bandwidth as granularity, or the number of the resources takes bandwidth in preset time as granularity. The QoS parameters include at least one of: delay information, minimum rate information, maximum rate information, and reliability information.

As shown in fig. 9, a processing flow of the resource management method applied to the control plane entity provided in the embodiment of the present invention includes the following steps:

step S901, a control plane entity receives a resource request message, where the resource request message is used for an access network element to allocate resources to a terminal device.

In the embodiment of the present invention, the control plane entity is an AMF entity or an SMF entity.

In some embodiments, the terminal device requests resources from the network device during session establishment, and does not apply for and authorize resources during group establishment. In specific implementation, taking the control plane entity as an SMF entity as an example, the SMF entity receives a session establishment request message sent by the terminal device, where the session establishment request message carries resource request information. As shown in fig. 3, in an optional processing flow of the resource management method, an SMF entity obtains subscription information of the terminal device from a user plane entity (e.g., a UDM entity), and verifies whether a session establishment request message of the terminal device passes through the subscription information. Or, the SMF entity sends the received session establishment request message to a user plane entity (e.g., UDM entity), and the UDM entity verifies whether the session establishment request message of the terminal device passes through. Wherein the subscription information includes: whether the terminal device allows to apply for the corresponding service at the PC5 interface, and/or whether the terminal device allows to apply for the resource attribute of the service at the PC5 interface. And after the verification is passed, the control plane entity sends a service request message to an access network element according to the received session establishment request message, wherein the service request message is used for the access network element to allocate resources for the terminal equipment.

In other embodiments, in the group establishing process, the network device allocates resources to the terminal device, that is, the terminal device provides NCIS-related group information and service-related information in the group establishing process, and the network device allocates resources according to the NCIS-related group information and service-related information; and the resources are activated and validated once allocated. As shown in fig. 4, in an optional processing flow of the resource management method, before the control plane entity receives the resource request message, the control plane entity sends, to the terminal device, information of allocable resources sent by the user plane entity through a protocol message unit, where the information of the allocable resources is determined by the control plane entity after verifying that subscription information or authorization information of the terminal device passes. Or, the control plane entity sends the information of the allocable resource sent by the user plane entity to the terminal device through an RRC message, where the information of the allocable resource is determined by the control plane entity after verifying that the subscription information or the authorization information of the terminal device passes. Or the control plane entity sends the information of the allocable resources sent by the user plane entity to the terminal equipment through NAS information; or, the control plane entity sends the information of the allocable resources sent by the user plane entity to the terminal device through N2 and RRC message; and the information of the allocable resources is determined by the control plane entity after the subscription information or the authorization information of the terminal equipment is verified to pass.

In still other embodiments, the terminal device requests resources during session establishment, and activates the resources based on the resource request; it will be appreciated that the resource allocation context is established during the session establishment, and that the PC5 resource configuration information will be saved when the resource is deactivated. However, the RAN/CN does not allocate actual PC5 resources to the terminal device. When the terminal equipment has actual resource requirements, activating the required resources through a service request process; at this time, the terminal device is allowed to request resource allocation according to actual demand while maintaining session connection. As shown in fig. 5, in an optional processing flow of the resource management method, after the terminal device deactivates a session or deactivates a resource in the session, the AMF entity receives a service establishment request message sent by the terminal device, where the service establishment request message carries resource request information, and the AMF entity sends the service establishment request message to the SMF entity. Then, the SMF entity sends the content in the service establishment request message to the access network element. And if the access network element has no resource-related configuration information, the SMF entity sends resource configuration information to the access network element. Here, the control plane entity includes an SMF entity and an AMF entity. Optionally, the service establishment request message includes at least one of session information, QoS flow information, and service flow information that need to be activated.

In some embodiments, the terminal device applies for resources through a service request process; it can be understood that the terminal device does not establish the context of resource allocation and does not allocate resources in the session establishment process; the terminal equipment requests to allocate resources each time a service request is initiated. As shown in fig. 6, in an optional processing flow of the resource management method, after a terminal device deactivates a session or deactivates a resource in the session, a control plane entity receives a service establishment request message sent by the terminal device, where the service establishment request message carries resource request information; for example, the AMF entity receives a service establishment request message sent by the terminal device, and sends the service establishment request message sent by the device to the SMF entity. Then, the SMF entity sends a session establishment request and a resource allocation request message to an access network element, so that the access network element allocates resources to the terminal device according to the session establishment request and the resource allocation request message. Wherein the service establishment request message includes: at least one of requested service information, service-related QoS information, and resource request information.

In still other embodiments, the terminal device applies for resources through an RRC procedure; as shown in fig. 7, in an optional processing flow of the resource management method, first, a control plane entity (e.g., an SMF entity) establishes a session of the terminal device; then, a control plane entity (such as an AMF entity) receives resource request information sent by the terminal device, where the resource request information is used for an access network element to allocate resources to the terminal device. The resource request information includes: requested service information, such as session information, QoS flow information, service flow information, etc.

In other embodiments, the terminal device applies for resources through a process of providing corresponding resources by a user plane; the resource information as allocated for the terminal device is configured to the terminal device through the interface between the terminal device and the AF. As shown in fig. 8, in an optional processing flow of the resource management method, a control plane entity receives resource request information sent by a server or an NCIS function server; verifying subscription information or authorization information of the terminal equipment based on the resource request information; and after the verification is passed, the control plane entity sends resource request information to the access network element.

As shown in fig. 10, a processing flow of the resource management method applied to the access network element according to the embodiment of the present invention includes the following steps:

step S1001, the network element of the access network receives the resource request information.

In some embodiments, an access network element receives a service request message sent by a core network element, where the service request message carries the resource request information.

Step S1002, the access network element allocates resources for the terminal equipment based on the resource request information.

In some embodiments, the access network element allocates resources to the terminal device according to the QoS information allowed by the terminal device. And the QoS information allowed by the terminal equipment is determined by a core network element according to the group information and/or the session information to which the terminal equipment belongs.

In each embodiment of the present invention, the access network element may be a base station, and the resource request information includes: resource parameters and/or QoS parameters. The resource parameters include: the number of resources and/or the transmission rate; the number of the resources takes bandwidth as granularity, or the number of the resources takes bandwidth in preset time as granularity. The QoS parameters include at least one of: delay information, minimum rate information, maximum rate information, and reliability information.

An embodiment of the present invention further provides a terminal device, where a schematic structural diagram of the terminal device 1100 is shown in fig. 11, and the terminal device includes:

a first sending unit 1101, configured to send resource request information to a network device, where the resource request information is used by the network device to allocate resources for the terminal device.

Optionally, the first sending unit 1101 is configured to send a session establishment request message to a core network element, where the session establishment request message is used for the core network element to send a service request message to an access network element, so that the access network element allocates resources to the terminal device. Wherein the session establishment request message comprises at least one of: NCIS related group information, service related information and the resource request information.

Optionally, the terminal device 1100 further includes: a second sending unit 1102, configured to send requested resource information, where the requested resource information is used by the network device to determine allocable resources of the terminal device.

Optionally, the second sending unit 1102 is configured to send a group establishment request message to a server or an NCIS function server, so that a core network element determines allocable resources of the terminal device based on the group establishment request message sent by the server or the NCIS function server; the group establishment request message carries the requested resource information; or, the group establishment request message is used for the server or the NCIS function server to acquire the requested resource information.

Optionally, the terminal device 1100 further includes: a first receiving unit 1103 configured to receive information of allocable resources and service information.

Optionally, the first receiving unit 1103 is configured to receive, by a protocol message unit, information of the allocable resource sent by a core network element. Alternatively, the first receiving unit 1103 is configured to receive, through an RRC message, the information about the allocable resources sent by the access network element. Or, the first receiving unit 1103 is configured to receive, through an NAS message, information of the allocable resource sent by a core network element; or, receiving the information of the allocable resource sent by the network element of the core network through N2 and RRC message. Alternatively, the first receiving unit 1103 is configured to receive, through an interface message protocol, information of the allocable resource sent by a server or an NCIS function server.

Optionally, the terminal device 1100 further includes: a third sending unit 1104, configured to send a service establishment request message to a core network element after the terminal device deactivates the session or deactivates the resource in the session, where the service establishment request message is used for the core network element to request an access network element to allocate the resource to the terminal device.

Wherein, the service establishment request message includes the session information required to be activated. The service establishment request message further includes: QoS flow information and/or traffic flow information.

Optionally, the first sending unit 1101 is configured to send a service establishment request message to a core network element, where the service establishment request message is used for the core network element to send a session establishment request and a resource allocation request message to an access network element, so that the access network element allocates resources for the terminal device.

Wherein the service establishment request message includes: requested service information. The service establishment request message further includes: traffic related QoS information and/or resource request information.

Optionally, the first sending unit 1101 is configured to send resource request information to an access network element, where the resource request information is used by the access network element to allocate resources to the terminal device. Wherein the resource request information includes: requested service information.

Optionally, the terminal device 1100 further includes: a first establishing unit 1105 configured to establish a session with a core network element.

Optionally, the terminal device 1100 further includes: a configuration unit 1106 configured to configure QoS information and/or resource configuration information.

Optionally, the terminal device 1100 further includes: a second receiving unit 1107 is configured to receive the resource allocated by the access network element.

Optionally, the first sending unit 1101 is configured to send resource request information to a server or an NCIS function server, where the resource request information is used for verifying subscription information of a terminal device by a core network element, so as to determine whether the core network element requests an access network element to allocate resources to the terminal device.

Optionally, the terminal device further includes: a third receiving unit 1108, configured to receive the resource allocated by the access network element and delivered by the server or the NCIS function server. Wherein the resource request information includes: resource parameters and/or QoS parameters. The resource parameters include: the number of resources and/or the transmission rate; the number of the resources takes bandwidth as granularity, or the number of the resources takes bandwidth in preset time as granularity. The QoS parameters include at least one of: delay information, minimum rate information, maximum rate information, and reliability information. The granularity of the resource request information is session granularity, QoS flow granularity or service flow granularity.

An embodiment of the present invention further provides a control plane entity, and a schematic structural diagram of a control plane entity 1200, as shown in fig. 12, includes:

a fourth receiving unit 1201, configured to receive a resource request message, where the resource request message is used by an access network element to allocate resources to a terminal device.

Optionally, the fourth receiving unit 1201 is configured to receive a session establishment request message sent by the terminal device, where the session establishment request message carries resource request information.

Optionally, the control plane entity 1200 further includes: the first processing unit 1202 is configured to acquire subscription information of the terminal device from a user plane entity, and verify whether a session establishment request message of the terminal device passes according to the subscription information.

Optionally, the control plane entity further comprises: a fourth sending unit 1203, configured to send the session establishment request message to a user plane entity, where the session establishment uses the request message for the user plane entity to verify whether the session establishment request message of the terminal device passes through. Wherein the subscription information includes: whether the terminal device allows to apply for the corresponding service at the PC5 interface, and/or whether the terminal device allows to apply for the resource attribute of the service at the PC5 interface.

Optionally, the control plane entity 1200 further includes: a fifth sending unit 1204, configured to send, according to the session establishment request message, a service request message to the access network element, where the service request message is used by the access network element to allocate resources to the terminal device.

Optionally, the control plane entity 1200 further includes: a sixth sending unit 1205, configured to send, to the terminal device, information of the allocable resource sent by the user plane entity through a protocol message unit, where the information of the allocable resource is determined after verifying that the subscription information or the authorization information of the terminal device passes.

Optionally, the control plane entity 1200 further includes: a seventh sending unit 1206, configured to send, to the terminal device, information of allocable resources sent by the user plane entity through a radio resource control RRC message, where the information of allocable resources is determined by the control plane entity after verifying that the subscription information or the authorization information of the terminal device passes.

Optionally, the control plane entity 1200 further includes: an eighth sending unit 1207, configured to send, to the terminal device, information about allocable resources sent by the user plane entity through an NAS message; or, the information of the allocable resource sent by the user plane entity is sent to the terminal device through N2 and RRC message; and the information of the allocable resources is determined by the control plane entity after the subscription information or the authorization information of the terminal equipment is verified to pass.

Optionally, the fourth receiving unit 1201 is configured to receive a service establishment request message sent by the terminal device after the terminal device deactivates the session or deactivates the resource in the session, where the service establishment request message carries resource request information.

Optionally, the control plane entity 1200 further includes: a ninth sending unit 1208, configured to send the content in the service establishment request message to the access network element.

Optionally, the control plane entity 1200 further includes: a tenth sending unit 1209, configured to send resource configuration information to the access network element. Wherein, the service establishment request message includes the session information required to be activated. The service establishment request message further includes: quality of service, QoS, flow information and/or traffic flow information.

Optionally, the fourth receiving unit 1201 is configured to receive a service establishment request message sent by the terminal device, where the service establishment request message is used by the access network element to allocate resources to the terminal device.

Optionally, the control plane entity 1200 further includes: an eleventh sending unit 1210, configured to send a session establishment request and a resource allocation request message to an access network element, so that the access network element allocates resources to the terminal device according to the session establishment request and the resource allocation request message. Wherein the service establishment request message includes: requested service information. The service establishment request message further includes: traffic related QoS information and/or resource request information.

Optionally, the control plane entity 1200 further includes: a second processing unit 1211 configured to obtain service-related QoS information and/or resource request information according to the service establishment request message.

Optionally, the fourth receiving unit 1201 is configured to receive resource request information sent by the terminal device, where the resource request information is used by the access network element to allocate resources to the terminal device. The resource request information includes: requested service information.

Optionally, the control plane entity 1200 further includes: a second establishing unit 1212 configured to establish a session of the terminal device.

Optionally, the fourth receiving unit 1201 is configured to receive resource request information sent by a server or an NCIS function server.

Optionally, the control plane entity 1200 further includes: a third processing unit 1213 configured to verify subscription information or authorization information of the terminal device based on the resource request information; and after the verification is passed, the control plane entity sends resource request information to the access network element. Wherein the resource request information includes: resource parameters and/or QoS parameters. The resource parameters include: the number of resources and/or the transmission rate; the number of the resources takes bandwidth as granularity, or the number of the resources takes bandwidth in preset time as granularity. The QoS parameters include at least one of: delay information, minimum rate information, maximum rate information, and reliability information.

Optionally, the granularity of the resource request information is session granularity, QoS flow granularity, or traffic flow granularity.

An embodiment of the present invention further provides an access network element, and a structure of an access network element 1300, as shown in fig. 13, where the access network element 1300 includes:

a fifth receiving unit 1301 configured to receive resource request information;

a fourth processing unit 1302, configured to allocate resources for the terminal device based on the resource request information.

Optionally, the fifth receiving unit 1301 is configured to receive a service request message sent by a core network element, where the service request message carries the resource request information.

Optionally, the fourth processing unit 1302 is configured to allocate resources to the terminal device according to QoS information allowed by the terminal device.

Optionally, the QoS information allowed by the terminal device is determined by a core network element according to group information and/or session information to which the terminal device belongs.

Optionally, the resource request information includes: resource parameters and/or QoS parameters. The resource parameters include: the number of resources and/or the transmission rate; the number of the resources takes bandwidth as granularity, or the number of the resources takes bandwidth in preset time as granularity. The QoS parameters include at least one of: delay information, minimum rate information, maximum rate information, and reliability information. The granularity of the resource request information is session granularity, QoS flow granularity or service flow granularity.

The embodiment of the present invention further provides a terminal device, which includes a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is configured to execute the steps of the resource management method executed by the terminal device when running the computer program.

The embodiment of the present invention further provides a control plane entity, which includes a processor and a memory for storing a computer program capable of running on the processor, where the processor is configured to execute the steps of the resource management method executed by the control plane entity when running the computer program.

The embodiment of the present invention further provides an access network element, which includes a processor and a memory for storing a computer program capable of being executed on the processor, wherein the processor is configured to execute the steps of the resource management method executed by the access network element when the processor is used to execute the computer program.

Fig. 14 is a schematic diagram of a hardware component structure of an electronic device (a terminal device, a control plane entity, or an access network element) according to an embodiment of the present invention, where the electronic device 1400 includes: at least one processor 1401, memory 1402, and at least one network interface 1404. The various components in the electronic device 1400 are coupled together by a bus system 1405. It will be appreciated that bus system 1405 is used to enable communications among the components connected. The bus system 1405 includes a power bus, a control bus, and a status signal bus, in addition to the data bus. For clarity of illustration, however, the various buses are labeled as bus system 1405 in fig. 14.

It will be appreciated that the memory 1402 can be either volatile memory or nonvolatile memory, and can include both volatile and nonvolatile memory. The non-volatile Memory may be ROM, Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), magnetic random access Memory (FRAM), Flash Memory (Flash Memory), magnetic surface Memory, optical Disc, or Compact Disc Read-Only Memory (CD-ROM); the magnetic surface storage may be disk storage or tape storage. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of illustration and not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), Enhanced Synchronous Dynamic Random Access Memory (Enhanced DRAM), Synchronous Dynamic Random Access Memory (SLDRAM), Direct Memory (DRmb Access), and Random Access Memory (DRAM). The memory 1402 described in connection with the embodiments of the invention is intended to comprise, without being limited to, these and any other suitable types of memory.

The memory 1402 in embodiments of the present invention is used to store various types of data to support the operation of the electronic device 1400. Examples of such data include: any computer program for operating on the electronic device 1400, such as the application programs 14022. A program implementing a method according to an embodiment of the invention may be included in the application 14022.

The methods disclosed in the embodiments of the present invention described above may be applied to the processor 1401, or may be implemented by the processor 1401. Processor 1401 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by instructions in the form of hardware integrated logic circuits or software in the processor 1401. The Processor 1401 may be a general purpose Processor, a Digital Signal Processor (DSP), or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc. Processor 1401 may implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present invention. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed by the embodiment of the invention can be directly implemented by a hardware decoding processor, or can be implemented by combining hardware and software modules in the decoding processor. The software modules may be located in a storage medium located in memory 1402, where the processor 1401 reads the information in memory 1402 and in combination with its hardware performs the steps of the method described previously.

In an exemplary embodiment, the electronic Device 1400 may be implemented by one or more Application Specific Integrated Circuits (ASICs), DSPs, Programmable Logic Devices (PLDs), Complex Programmable Logic Devices (CPLDs), FPGAs, general purpose processors, controllers, MCUs, MPUs, or other electronic components for performing the foregoing methods.

The embodiment of the application also provides a computer readable storage medium for storing the computer program.

Optionally, the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.

Optionally, the computer-readable storage medium may be applied to the terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The above description is only exemplary of the present invention and should not be taken as limiting the scope of the present invention, and any modifications, equivalents, improvements, etc. that are within the spirit and principle of the present invention should be included in the present invention.

Claims

A method of resource management, the method comprising:

the method comprises the steps that a terminal device sends resource request information to a network device, and the resource request information is used for the network device to distribute resources for the terminal device.
The method of claim 1, wherein the terminal device sending resource request information to a network device comprises:

the terminal equipment sends a session establishment request message to a core network element, wherein the session establishment request message is used for the core network element to send a service request message to an access network element, so that the access network element allocates resources for the terminal equipment.
The method of claim 2, wherein the session establishment request message comprises at least one of:

and the network controls group information related to the NCIS, related information of the service and the resource request information.
The method of any of claims 1 to 3, wherein the method further comprises:

the terminal equipment sends the requested resource information, and the requested resource information is used for the network equipment to determine the allocable resources of the terminal equipment.
The method of claim 4, wherein the terminal device transmitting the requested resource information comprises:

the terminal equipment sends a group establishment request message to a server or a network control interactive service NCIS function server so that a core network element determines allocable resources of the terminal equipment based on the group establishment request message sent by the server or the NCIS function server;

the group establishment request message carries the requested resource information; or, the group establishment request message is used for the server or the NCIS function server to acquire the requested resource information.
The method of claim 4, wherein the method further comprises:

and the terminal equipment receives the information of the allocable resources and the service information.
The method of claim 6, wherein the terminal device receiving information of allocable resources comprises:

and the terminal equipment receives the information of the allocable resources, which is sent by the network element of the core network, through a protocol message unit.
The method of claim 6, wherein the terminal device receiving information of allocable resources comprises:

and the terminal equipment receives the information of the allocable resources sent by the network element of the access network through a Radio Resource Control (RRC) message.
The method of claim 6, wherein the terminal device receiving information of allocable resources comprises:

the terminal equipment receives the information of the allocable resources sent by the network element of the core network through NAS information;

or, the terminal device receives the information of the allocable resource sent by the core network element through N2 and RRC message.
The method of claim 6, wherein the terminal device receiving information of allocable resources comprises:

and the terminal equipment receives the information of the allocable resources sent by the server or the NCIS function server through an interface message protocol.
The method of any of claims 1 to 3, wherein after the terminal device deactivates the session or deactivates resources in the session, the method further comprises:

the terminal equipment sends a service establishment request message to a core network element, wherein the service establishment request message is used for the core network element to request an access network element to allocate resources for the terminal equipment.
The method of claim 11, wherein the service setup request message includes session information required to be activated.
The method of claim 12, wherein the service setup request message further comprises:

quality of service, QoS, flow information and/or traffic flow information.
The method of claim 1, wherein the terminal device sending resource request information to a network device comprises:

the terminal equipment sends a service establishment request message to a core network element, wherein the service establishment request message is used for the core network element to send a session establishment request and a resource allocation request message to an access network element, so that the access network element allocates resources for the terminal equipment.
The method of claim 14, wherein the service setup request message comprises: requested service information.
The method of claim 15, wherein the service setup request message further comprises:

traffic related QoS information and/or resource request information.
The method of claim 1, wherein the terminal device sending resource request information to a network device comprises:

and the terminal equipment sends resource request information to an access network element, wherein the resource request information is used for the access network element to allocate resources for the terminal equipment.
The method of claim 17, wherein the resource request information comprises: requested service information.
The method of claim 17 or 18, wherein the method further comprises:

and the terminal equipment establishes a session with a core network element.
The method of any of claims 17 to 19, wherein the method further comprises:

and the terminal equipment configures QoS information and/or resource configuration information.
The method of any one of claims 1 to 20, wherein the method further comprises:

and the terminal equipment receives the resources distributed by the network element of the access network.
The method of claim 1, wherein the terminal device sending resource request information to a network device comprises:

the terminal equipment sends resource request information to a server or an NCIS function server, wherein the resource request information is used for verifying the subscription information of the terminal equipment by a core network element so as to judge whether the core network element requests an access network element to allocate resources for the terminal equipment.
The method of claim 22, wherein the method further comprises:

and the terminal equipment receives the resources distributed by the access network element transmitted by the server or the NCIS function server.
The method of any of claims 1 to 23, wherein the resource request information comprises:

resource parameters and/or QoS parameters.
The method of claim 24, wherein the resource parameters comprise:

the number of resources and/or the transmission rate;

the number of the resources takes bandwidth as granularity, or the number of the resources takes bandwidth in preset time as granularity.
The method of claim 24 or 25, wherein the QoS parameter comprises at least one of:

delay information, minimum rate information, maximum rate information, and reliability information.
The method of any of claims 1 to 26, wherein the granularity of the resource request information is a session granularity, or a QoS flow granularity, or a traffic flow granularity.
A method of resource management, the method comprising:

and the control plane entity receives a resource request message, wherein the resource request message is used for the access network element to allocate resources for the terminal equipment.
The method of claim 28, wherein the control plane entity receives resource request information, comprising:

and the control plane entity receives a session establishment request message sent by the terminal equipment, wherein the session establishment request message carries resource request information.
The method of claim 29, wherein the method further comprises:

the control plane entity acquires the subscription information of the terminal equipment from a user plane entity;

and the control plane entity verifies whether the session establishment request message of the terminal equipment passes or not according to the subscription information.
The method of claim 29, wherein the method further comprises:

and the control plane entity sends the session establishment request message to a user plane entity, and the session establishment request message is used for the user plane entity to verify whether the session establishment request message of the terminal equipment passes or not.
The method of claim 30, wherein the subscription information comprises:

whether the terminal device allows to apply for the corresponding service at the PC5 interface, and/or whether the terminal device allows to apply for the resource attribute of the service at the PC5 interface.
The method of any of claims 29 to 32, wherein the method further comprises:

and the control plane entity sends a service request message to the access network element according to the session establishment request message, wherein the service request message is used for the access network element to allocate resources for the terminal equipment.
The method of claim 28, wherein the method further comprises:

and the control plane entity sends the information of the allocable resources sent by the user plane entity to the terminal equipment through a protocol message unit, wherein the information of the allocable resources is determined by the control plane entity after the control plane entity verifies that the subscription information or the authorization information of the terminal equipment passes.
The method of claim 28, wherein the method further comprises:

and the control plane entity sends the information of the allocable resources sent by the user plane entity to the terminal equipment through a Radio Resource Control (RRC) message, wherein the information of the allocable resources is determined by the control plane entity after the control plane entity verifies that the subscription information or the authorization information of the terminal equipment passes.
The method of claim 28, wherein the method further comprises:

the control plane entity sends the information of the allocable resources sent by the user plane entity to the terminal equipment through NAS information;

or, the control plane entity sends the information of the allocable resources sent by the user plane entity to the terminal device through N2 and RRC message;

and the information of the allocable resources is determined by the control plane entity after the subscription information or the authorization information of the terminal equipment is verified to pass.
The method of claim 28, wherein the control plane entity receives a resource request message comprising:

and after the terminal equipment deactivates the session or deactivates the resources in the session, the control plane entity receives a service establishment request message sent by the terminal equipment, wherein the service establishment request message carries resource request information.
The method of claim 37, wherein the method further comprises:

and the control plane entity sends the content in the service establishment request message to the access network element.
The method of claim 38, wherein the method further comprises:

and the control plane entity sends resource configuration information to the access network element.
A method according to any of claims 37 to 39, wherein the service establishment request message includes session information required for activation.
The method of claim 40, wherein the service setup request message further comprises:

quality of service, QoS, flow information and/or traffic flow information.
The method of claim 28, wherein the control plane entity receives resource request information, comprising:

and the control plane entity receives a service establishment request message sent by the terminal equipment, wherein the service establishment request message is used for the access network element to allocate resources for the terminal equipment.
The method of claim 42, wherein the method further comprises:

and the control plane entity sends a session establishment request and a resource allocation request message to an access network element, so that the access network element allocates resources for the terminal equipment according to the session establishment request and the resource allocation request message.
The method of claim 42 or 43, wherein the service establishment request message comprises: requested service information.
The method of claim 44, wherein the service setup request message further comprises:

traffic related QoS information and/or resource request information.
The method of any one of claims 42 to 44, wherein the method further comprises:

and the control plane entity acquires QoS information and/or resource request information related to the service according to the service establishment request message.
The method of claim 28, wherein the control plane entity receives resource request information, comprising:

and the control plane entity receives resource request information sent by the terminal equipment, wherein the resource request information is used for the access network element to allocate resources for the terminal equipment.
The method of claim 47, wherein the resource request information comprises: requested service information.
The method of claim 47 or 48, wherein the method further comprises:

and the control plane entity establishes the session of the terminal equipment.
The method of claim 28, wherein the control plane entity receives resource request information, comprising:

and the control plane entity receives resource request information sent by the server or the NCIS function server.
The method of claim 50, wherein the method further comprises:

the control plane entity verifies subscription information or authorization information of the terminal equipment based on the resource request information;

and after the verification is passed, the control plane entity sends resource request information to the access network element.
The method of any of claims 28 to 51, wherein the resource request information comprises:

resource parameters and/or QoS parameters.
The method of claim 52, wherein the resource parameters comprise:

the number of resources and/or the transmission rate;

the number of the resources takes bandwidth as granularity, or the number of the resources takes bandwidth in preset time as granularity.
The method of claim 52 or 53, wherein the QoS parameters comprise at least one of:

delay information, minimum rate information, maximum rate information, and reliability information.
The method of any of claims 28 to 54, wherein the granularity of the resource request information is a session granularity, or a QoS flow granularity, or a traffic flow granularity.
A method of resource management, the method comprising:

the network element of the access network receives the resource request information;

and the access network element allocates resources for the terminal equipment based on the resource request information.
The method of claim 56, wherein the receiving, by the access network element, resource request information comprises:

and the access network element receives a service request message sent by a core network element, wherein the service request message carries the resource request information.
The method of claim 56 or 57, wherein the allocating, by the access network element, resources for the terminal device based on the resource request information comprises:

and the access network element allocates resources for the terminal equipment according to the QoS information allowed by the terminal equipment.
The method of claim 58, wherein the QoS information allowed by the terminal device is determined by a core network element according to group information and/or session information to which the terminal device belongs.
The method of any one of claims 56 to 59, wherein the resource request information comprises:

resource parameters and/or QoS parameters.
The method of claim 60, wherein the resource parameters comprise:

the number of resources and/or the transmission rate;

the number of the resources takes bandwidth as granularity, or the number of the resources takes bandwidth in preset time as granularity.
The method of claim 60 or 61, wherein the QoS parameters comprise at least one of:

delay information, minimum rate information, maximum rate information, and reliability information.
The method of any one of claims 56 to 62, wherein the granularity of the resource request information is a session granularity, or a QoS flow granularity, or a traffic flow granularity.
A terminal device, comprising:

a first sending unit, configured to send resource request information to a network device, where the resource request information is used by the network device to allocate resources to the terminal device.
The terminal device of claim 64, wherein the first sending unit is configured to send a session establishment request message to a core network element, where the session establishment request message is used for the core network element to send a service request message to an access network element, so that the access network element allocates resources for the terminal device.
The terminal device of claim 65, wherein the session establishment request message comprises at least one of:

and the network controls group information related to the NCIS, related information of the service and the resource request information.
The terminal device of any one of claims 64-66, wherein the terminal device further comprises:

a second sending unit, configured to send requested resource information, where the requested resource information is used by the network device to determine allocable resources of the terminal device.
The terminal device of claim 67, wherein the second sending unit is configured to send a group setup request message to a server or a Network Control Interworking Service (NCIS) function server, so that a core network element determines allocable resources of the terminal device based on the group setup request message sent by the server or the NCIS function server;

the group establishment request message carries the requested resource information; or, the group establishment request message is used for the server or the NCIS function server to acquire the requested resource information.
The terminal device of claim 67, wherein the terminal device further comprises:

the first receiving unit is configured to receive information of allocable resources and service information.
The terminal device of claim 69, wherein the first receiving unit is configured to receive, through a protocol message unit, the information about the allocable resources sent by a core network element.
The terminal device according to claim 69, wherein the first receiving unit is configured to receive the information of the allocable resources sent by the access network element through a Radio Resource Control (RRC) message.
The terminal device of claim 69, wherein the first receiving unit is configured to receive, through an NAS message, the information about the allocable resources sent by a core network element;

or, receiving the information of the allocable resource sent by the network element of the core network through N2 and RRC message.
The terminal device according to claim 69, wherein the first receiving unit is configured to receive the information of the allocable resource sent by a server or a NCIS function server through an interface message protocol.
The terminal device of any one of claims 64-66, wherein the terminal device further comprises:

a third sending unit, configured to send a service establishment request message to a core network element after the terminal device deactivates the session or deactivates the resource in the session, where the service establishment request message is used for the core network element to request an access network element to allocate the resource to the terminal device.
A terminal device according to claim 74, wherein the service establishment request message includes session information required for activation.
The terminal device of claim 75, wherein the service setup request message further comprises:

quality of service, QoS, flow information and/or traffic flow information.
The terminal device of claim 64, wherein the first sending unit is configured to send a service establishment request message to a core network element, where the service establishment request message is used for the core network element to send a session establishment request and a resource allocation request message to an access network element, so that the access network element allocates resources to the terminal device.
The terminal device of claim 77, wherein the service setup request message comprises: requested service information.
The terminal device of claim 78, wherein the service setup request message further includes:

traffic related QoS information and/or resource request information.
The terminal device of claim 64, wherein the first sending unit is configured to send resource request information to an access network element, where the resource request information is used by the access network element to allocate resources to the terminal device.
The terminal device of claim 80, wherein the resource request information comprises: requested service information.
The terminal device of claim 80 or 81, wherein the terminal device further comprises:

the first establishing unit is configured to establish a session with a core network element.
The terminal device of any one of claims 80 to 82, wherein the terminal device further comprises:

a configuration unit configured to configure the QoS information and/or the resource configuration information.
The terminal device of any one of claims 64-83, wherein the terminal device further comprises:

and the second receiving unit is configured to receive the resources allocated by the network element of the access network.
The terminal device of claim 64, wherein the first sending unit is configured to send resource request information to a server or an NCIS function server, where the resource request information is used by a core network element to verify subscription information of the terminal device, so as to determine whether the core network element requests an access network element to allocate resources to the terminal device.
The terminal device of claim 85, wherein the terminal device further comprises:

and the third receiving unit is configured to receive the resource distributed by the access network element and transmitted by the server or the NCIS function server.
The terminal device of any one of claims 64 to 86, wherein the resource request information comprises:

resource parameters and/or QoS parameters.
The terminal device of claim 87, wherein the resource parameters comprise:

the number of resources and/or the transmission rate;

the number of the resources takes bandwidth as granularity, or the number of the resources takes bandwidth in preset time as granularity.
The terminal device of claim 87 or 88, wherein the QoS parameter comprises at least one of:

delay information, minimum rate information, maximum rate information, and reliability information.
The terminal device of any one of claims 64 to 89, wherein the granularity of the resource request information is a session granularity, or a QoS flow granularity, or a traffic flow granularity.
A control plane entity, the control plane entity comprising:

a fourth receiving unit, configured to receive a resource request message, where the resource request message is used by an access network element to allocate resources to a terminal device.
The control plane entity of claim 91, wherein the fourth receiving unit is configured to receive a session establishment request message sent by the terminal device, and the session establishment request message carries resource request information.
The control plane entity of claim 92, wherein the control plane entity further comprises:

and the first processing unit is configured to acquire the subscription information of the terminal device from a user plane entity, and verify whether the session establishment request message of the terminal device passes or not according to the subscription information.
The control plane entity of claim 92, wherein the control plane entity further comprises:

a fourth sending unit, configured to send the session establishment request message to a user plane entity, where the session establishment uses the request message for the user plane entity to verify whether the session establishment request message of the terminal device passes through.
The control plane entity of claim 93, wherein the subscription information comprises:

whether the terminal device allows to apply for the corresponding service at the PC5 interface, and/or whether the terminal device allows to apply for the resource attribute of the service at the PC5 interface.
The control plane entity of any of claims 92 to 95, wherein the control plane entity further comprises:

a fifth sending unit, configured to send a service request message to the access network element according to the session establishment request message, where the service request message is used by the access network element to allocate resources to the terminal device.
The control plane entity of claim 91, wherein the control plane entity further comprises:

a sixth sending unit, configured to send, to the terminal device, information of the allocable resource sent by the user plane entity through a protocol message unit, where the information of the allocable resource is determined after verifying that subscription information or authorization information of the terminal device passes.
The control plane entity of claim 91, wherein the control plane entity further comprises:

a seventh sending unit, configured to send, to the terminal device, information of allocable resources sent by a user plane entity through a radio resource control RRC message, where the information of the allocable resources is determined by the control plane entity after verifying that subscription information or authorization information of the terminal device passes.
The control plane entity of claim 91, wherein the control plane entity further comprises:

an eighth sending unit, configured to send, to the terminal device, information of the allocable resource sent by the user plane entity through an NAS message;

or, the information of the allocable resource sent by the user plane entity is sent to the terminal device through N2 and RRC message;

and the information of the allocable resources is determined by the control plane entity after the subscription information or the authorization information of the terminal equipment is verified to pass.
The control plane entity of claim 91, wherein the fourth receiving unit is configured to receive a service establishment request message sent by the terminal device after the terminal device deactivates a session or deactivates resources in the session, and the service establishment request message carries resource request information.
The control plane entity of claim 100, wherein the control plane entity further comprises:

a ninth sending unit, configured to send the content in the service establishment request message to the access network element.
The control plane entity of claim 101, wherein the control plane entity further comprises:

a tenth sending unit, configured to send resource configuration information to the access network element.
A control plane entity as claimed in any of claims 100 to 102, wherein the service set-up request message includes session information required for activation.
The control plane entity of claim 103, wherein the service establishment request message further comprises:

quality of service, QoS, flow information and/or traffic flow information.
The control plane entity of claim 91, wherein the fourth receiving unit is configured to receive a service establishment request message sent by the terminal device, where the service establishment request message is used by the access network element to allocate resources to the terminal device.
The control plane entity of claim 105, wherein the control plane entity further comprises:

an eleventh sending unit, configured to send a session establishment request and a resource allocation request message to an access network element, so that the access network element allocates resources to the terminal device according to the session establishment request and the resource allocation request message.
A control plane entity of claim 105 or 106, wherein the service establishment request message comprises: requested service information.
The control plane entity of claim 107, wherein the service establishment request message further comprises:

traffic related QoS information and/or resource request information.
The control plane entity of any of claims 105 to 107, wherein the control plane entity further comprises:

and the second processing unit is configured to acquire QoS information and/or resource request information related to the service according to the service establishment request message.
The control plane entity of claim 91, wherein the fourth receiving unit is configured to receive resource request information sent by the terminal device, and the resource request information is used by the access network element to allocate resources to the terminal device.
The control plane entity of claim 110, wherein the resource request information comprises: requested service information.
The control plane entity of claim 110 or 111, wherein the control plane entity further comprises:

and the second establishing unit is configured to establish the session of the terminal equipment.
The control plane entity of claim 91, wherein the fourth receiving unit is configured to receive resource request information sent by a server or a Network Control Interworking Service (NCIS) function server.
The control plane entity of claim 113, wherein the control plane entity further comprises:

a third processing unit configured to verify subscription information or authorization information of the terminal device based on the resource request information;

and after the verification is passed, the control plane entity sends resource request information to the access network element.
A control plane entity of any of claims 91 to 114, wherein the resource request information comprises:

resource parameters and/or QoS parameters.
The control plane entity of claim 115, wherein the resource parameters include:

the number of resources and/or the transmission rate;

the number of the resources takes bandwidth as granularity, or the number of the resources takes bandwidth in preset time as granularity.
A control plane entity as claimed in claim 115 or 116, wherein the QoS parameter comprises at least one of:

delay information, minimum rate information, maximum rate information, and reliability information.
A control plane entity of any of claims 91 to 117, wherein the granularity of the resource request information is session granularity, or QoS flow granularity, or traffic flow granularity.
An access network element, the access network element comprising:

a fifth receiving unit configured to receive the resource request information;

and the fourth processing unit is configured to allocate resources for the terminal equipment based on the resource request information.
The access network element according to claim 119, wherein the fifth receiving unit is configured to receive a service request message sent by a core network element, and the service request message carries the resource request information.
The access network element according to claim 119 or 120, wherein the fourth processing unit is configured to allocate resources to the terminal device according to QoS information allowed by the terminal device.
The access network element of claim 121, wherein the QoS information allowed by the terminal device is determined by a core network element according to group information and/or session information to which the terminal device belongs.
The access network element as claimed in any one of claims 119 to 122, wherein the resource request information comprises:

resource parameters and/or QoS parameters.
The access network element of claim 123, wherein the resource parameters include:

the number of resources and/or the transmission rate;

the number of the resources takes bandwidth as granularity, or the number of the resources takes bandwidth in preset time as granularity.
The access network element of claim 123 or 124, wherein the QoS parameter comprises at least one of:

delay information, minimum rate information, maximum rate information, and reliability information.
The access network element of any one of claims 119 to 125, wherein the granularity of the resource request information is a session granularity, or a QoS flow granularity, or a traffic flow granularity.
A terminal device comprising a processor and a memory for storing a computer program capable of running on the processor, wherein,

the processor is adapted to perform the steps of the resource management method of any of claims 1 to 27 when running the computer program.
A control plane entity comprising a processor and a memory for storing a computer program capable of running on the processor, wherein,

the processor is adapted to perform the steps of the resource management method of any of claims 28 to 55 when running the computer program.
An access network element comprising a processor and a memory for storing a computer program capable of running on the processor, wherein,

the processor, when executing the computer program, is configured to perform the steps of the resource management method of any of claims 56 to 63.
A storage medium storing an executable program which, when executed by a processor, implements the resource management method of any one of claims 1 to 27.
A storage medium storing an executable program which, when executed by a processor, implements the resource management method of any one of claims 28 to 55.
A storage medium storing an executable program which, when executed by a processor, implements the resource management method of any one of claims 56 to 63.