CN112400352B

CN112400352B - Resource management method, equipment and storage medium

Info

Publication number: CN112400352B
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: 2023-12-29
Anticipated expiration: 2039-01-21
Also published as: WO2020150875A1; CN112400352A

Abstract

The invention discloses a resource management method, which comprises the following steps: and the terminal equipment sends resource request information to the network equipment, wherein the resource request information is used for allocating resources for the terminal equipment by the network equipment. 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 method, an apparatus, and a storage medium for resource management.

Background

In cellular network communications, data communications between terminal devices are typically received and transmitted through network devices, and the network devices or operators count the data actually transmitted by the terminal devices on the core network side, so as to charge for the transmitted data. However, in the terminal device direct communication mechanism, two terminal devices directly perform data transmission, 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 charge the transmitted data because the network device cannot count the actual transmitted data amount.

Disclosure of Invention

In order to solve the above technical problems, embodiments of the present invention provide a method, an apparatus, and a storage medium for resource management, so that when direct communication is performed between UEs, a network device can count the amount of data actually transmitted, and realize charging for the transmitted data.

In a first aspect, an embodiment of the present invention provides a resource processing method, including: and the terminal equipment sends resource request information to the network equipment, wherein the resource request information is used for allocating resources for the terminal equipment by the network equipment.

In a second aspect, an embodiment of the present invention provides a resource processing method, including: and the control plane entity receives the resource request information, wherein the resource request information 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 access network element 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, including: the first sending unit is configured to send resource request information to the network equipment, wherein the resource request information is used for allocating resources for the terminal equipment by the network equipment.

In a fifth aspect, an embodiment of the present invention provides a control plane entity, where the control plane entity includes: and the fourth receiving unit is configured to receive 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 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 a fourth processing unit configured to allocate resources to the terminal device 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 capable of running on the processor, wherein the processor is adapted to execute the steps of the method performed by the terminal device described above when the computer program is run.

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 capable of running on the processor, wherein the processor is adapted to perform the steps of the method performed by the control plane entity described above when the computer program is run.

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 capable of running on the processor, wherein the processor is adapted to perform the steps of the method performed by the access network element described above when the computer program is run.

In a tenth 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 a 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 a method performed by the control plane entity.

In a twelfth 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 an access network element.

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

Drawings

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

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

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

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

FIG. 5 is a third alternative process flow diagram of a resource processing method according to an embodiment of the present invention;

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

FIG. 7 is a fifth alternative process flow diagram of a resource processing method according to an embodiment of the present invention;

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

fig. 9 is a schematic 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 process flow diagram of a resource management method applied to an access network element according to an embodiment of the present invention;

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

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

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

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

Detailed Description

So that the manner in which the features and techniques of the embodiments of the present invention can be understood in more detail, a more particular description of the invention, briefly summarized below, may be had by reference to the appended drawings, which are not intended to be limiting of the embodiments of the present invention.

Before describing embodiments of the present invention in detail, network control interaction service (Network Control Interactive Services, NCIS) traffic will be briefly described.

In a New Radio (NR) system, NCIS service is introduced as a New service form into the standard for related standardized service. The NCIS service is mainly aimed at applications such as Virtual Reality (VR)/augmented Reality (Augmented Reality, AR), games, and the like, and has higher requirements on service quality such as rate, time delay, packet loss rate, high-speed decoding, and the like. 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 UEs having the same NCIS session may form an NCIS group. UEs joining the NCIS session may all be local, e.g., establish a side link(s) using a Device-to-Device (D2D) technology, also referred to 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 UEs, also referred to as using Uu interface. The UEs joining the NCIS session may be from the same public land mobile network (Public Land Mobile Network, PLMN) or from different PLMNs. For example, there are 5 UEs in an NCIS group, wherein 3 UEs belong to PLMN 1,2 UEs belong to PLMN 2,3 UEs belong to PLMN 1 are directly communicated with each other using side link; at the same time, 3 UEs belonging to PLMN 1 and 2 UEs belonging to PLMN 2 communicate through the network device.

The invention provides a resource management method, which can be applied to various communication systems, for example: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA), wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) systems, general packet radio service (General Packet Radio Service, GPRS), long term evolution (Long Term Evolution, LTE) systems, LTE frequency division duplex (Frequency Division Duplex, FDD) systems, LTE time division duplex (Time Division Duplex, TDD), universal mobile telecommunications system (Universal Mobile Telecommunication System, UMTS), worldwide interoperability for microwave access (Worldwide Interoperability for Microwave Access, wiMAX) communication systems, or 5G systems, and the like.

Exemplary, a communication system 100 to which embodiments of the present application apply 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, terminal). Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within the coverage area. Alternatively, the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a base station (NodeB, NB) in a WCDMA system, an evolved base station (Evolutional Node B, eNB or eNodeB) in an LTE system, or a radio controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device may be a mobile switching center, a relay station, an access point, a vehicle 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 future evolved public land mobile network (Public Land Mobile Network, PLMN), etc.

The communication system 100 further comprises at least one terminal device 120 located within the coverage area of the network device 110. "terminal device" as used herein includes, but is not limited to, a connection via a wireline, such as via a public-switched telephone network (Public Switched Telephone Networks, PSTN), a digital subscriber line (Digital Subscriber Line, DSL), a digital cable, a direct cable connection; and/or another data connection/network; and/or via a wireless interface, e.g., for a cellular network, a wireless local area network (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 the other terminal device arranged to receive/transmit communication signals; and/or internet of things (Internet of Things, ioT) devices. Terminal devices arranged to communicate over a wireless interface may be referred to as "wireless communication terminals", "wireless terminals" or "mobile terminals". Examples of mobile terminals include, but are not limited to, satellites or cellular telephones; a personal communications system (Personal Communications System, PCS) terminal that may combine a cellular radiotelephone with data processing, facsimile and data communications capabilities; a PDA that can include a radiotelephone, pager, internet/intranet access, web browser, organizer, calendar, and/or a global positioning system (Global Positioning System, GPS) receiver; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. A terminal device 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 (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle 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 5G network may also be referred to as a New Radio (NR) system or NR network.

Fig. 1 illustrates one network device and two terminal devices by way of example, and alternatively, the communication system 100 may include a plurality of network devices and may include other numbers of terminal devices within the coverage area of each network device, which is not limited in this embodiment of the present application.

Optionally, the communication system 100 may further include a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

It should be understood that a device having a communication function in a network/system in an embodiment 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 with communication functions, where the network device 110 and the terminal device 120 may be 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 a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

The process flow of the resource management method applied to the terminal equipment provided by the embodiment of the invention, as shown in fig. 2, comprises the following steps:

In 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 for the terminal device.

In some embodiments, the 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 resource from the network device in the session establishment process, and does not apply for the resource and authorize the resource 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, an optional process flow diagram of the resource management method is shown in fig. 3, and includes the following steps:

in step S301, the terminal device sends an NCIS related session establishment request message 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.

In step S302, the SMF entity obtains subscription information of the terminal device from the UDM entity.

The subscription information includes: whether the terminal equipment allows the application of the service at the PC5 interface, and/or whether the terminal equipment allows the application of the requirement or resource attribute of the service at the PC5 interface; such as maximum allowed traffic rate, minimum latency requirements, etc. And if the SMF entity passes verification, a session establishment request message is initiated to the RAN network element, wherein the session establishment request message carries 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, the UDM entity/PCF entity verifies the session establishment request message of the terminal equipment, and if the verification is passed, the SMF entity is responded.

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

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

After receiving the service request, the RAN network element distributes available resources on the PC5 interface according to the resource request information, wherein the resources can be QoS flow granularity, 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 can be fed back to the core network element, or the RAN network element allocates the actually allocated resource and feeds back the actually allocated resource to the core network element, and the core network element can further feed back the actually allocated resource to the charging equipment 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, the network device allocates resources to the terminal device during the group establishment, that is, the terminal device provides the group information related to the NCIS and the related information of the service during the group establishment, and the network device allocates resources according to the group information related to the NCIS and the related information of the service; and the resources are activated once allocated to take effect. In specific implementation, an alternative process flow diagram of the resource management method, as shown in fig. 4, includes the following steps:

in step S401, the terminal device transmits the requested resource information.

Here, the requested resource information is used by the network device to determine the 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 an allocable resource 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 establishment request message can carry related information for establishing service, such as service type, service requirement, interface carrying the service application, etc.; optionally, the service types include an interactive service, an interactive game service, a background service and the like; the service requirements include: the required service rate, time delay requirement, reliability requirement and the like; the interface carrying the business 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 for the service application.

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

In the specific implementation, the UDM entity/PCF entity in the core network element verifies 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 at the PC5 interface or not, and whether the terminal equipment allows the application of the requirement or the resource attribute of the service at the PC5 interface; such as maximum allowed traffic rate, minimum latency requirements, etc. And if the authentication is passed, the UDM entity/PCF entity transmits the allowed service, the group information and the allocable resource information to the terminal. If the verification is not passed, the UDM entity/PCF entity may reject the request or determine the allocatable resources from the actual subscription information or the authorized information.

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

In a specific implementation, the UDM entity/PCF entity of the core network may send the service information and the 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 the 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 the allocable resource information applied by the terminal device into a 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 the allocable resource information applied by the terminal device to the AMF entity or the SMF entity, where the AMF entity or the SMF entity encapsulates the service information and the allocable resource information applied by the terminal device into an N2 message and sends the N2 message to the RAN network element; and the RAN network element sends the service information and the allocable resource information applied by the terminal equipment to the terminal equipment through the RRC message. Or, the UDM entity/PCF entity of the core network encapsulates the service information and the allocable resource information applied by the terminal equipment into a transparent container, and sends the transparent container to the terminal equipment through NAS information or through N2 and RRC information. Or the core network element sends the service information and the distributable resource information applied by the terminal equipment to an application related server or an 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 distributable resource information to the terminal equipment through an interface message protocol between the service information and the terminal equipment.

In 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, business related information and resource request information; the requested resources of the terminal device cannot be higher than the resource request information authorized in step S404.

Step S406-step S407, the SMF entity receives the session establishment request sent by the terminal equipment, 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 demand information.

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

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

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

In a specific implementation, the UDM entity/PCF entity of the core network may send the service information and the allocable resource information applied by the terminal device to the terminal through a protocol message unit of the 3GPP network, for example, the UDM entity/PCF entity sends the data to the AMF entity or the SMF entity, and the AMF entity or the SMF entity encapsulates the service information and the allocable resource information into a NAS message and sends the NAS message to the terminal device. Or the UDM entity/PCF entity of the core network can send the service information and the allocable resource information applied by the terminal equipment to the AMF entity or the SMF entity, and the AMF entity or the SMF entity packages the service information and the allocable resource information into N2 information and sends the N2 information to the access RAN network element; 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 equipment through NAS information or through N2 and RRC information. Or the core network element sends the service information and the distributable resource information to an application related server or an NCIS function server (AF), and the application related server or the NCIS function server (AF) sends the service information and the distributable resource information to the terminal equipment through an interface message protocol between the service information and the NCIS function server (AF).

In still other embodiments, the terminal device requests resources during session establishment, and activates resources based on the resource request; it will be appreciated that the resource allocation context is established during session establishment and that the PC5 resource configuration information will be saved after 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 demands while maintaining session connection. In specific implementation, an optional process flow diagram of the resource management method, as shown in fig. 5, includes the following steps:

in step S501, the terminal device performs session establishment.

The session establishment procedure in the embodiment of the present invention is the same as the session establishment procedure in the related art, and will not be described here again.

In 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 also carries QoS flow information or service flow information that needs to be activated.

In 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 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 simultaneously provides the resource configuration information to the access network. The RAN network element allocates resources for the terminal equipment based on the information sent by the SMF entity and feeds back the resources 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 a context of resource allocation and does not allocate resources in the session establishment process; the terminal device requests allocation of resources each time a service request is initiated. In specific implementation, an alternative process flow diagram of the resource management method is shown in fig. 6, and includes the following steps:

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

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

In step S602, the AMF entity sends a 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 the resource allocation request and feeds back resource information to the SMF entity.

It should be noted that, if the terminal device does not carry QoS requirements or 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 related session information;

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

in 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.

In 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 needs resources, such as session information, qoS flow information, service flow information, and the like.

Step S703-step S704, the RAN network element allocates resources on the PC5 for 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, etc.; the resource information may be: bandwidth provided, traffic rate provided, delay information provided, etc.

Alternatively, 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 the terminal-allowed QoS information according to the group information and/or session information to which the terminal device belongs.

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

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

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

Step S802-step S803, AF sends the resource request message of the terminal equipment to the core network element, the core network element verifies the subscription information of the terminal equipment; if so, whether to allow the service to be initiated and whether to allow the resource to be applied for; if the authentication 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 delivers the allocated resource information to the terminal through an interface between the terminal device and the AF.

It should be noted that, in the above 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 is granularity of bandwidth, or the number of the resources is granularity of bandwidth in preset time. The QoS parameters include at least one of: delay information, minimum rate information, maximum rate information, and reliability information.

The process flow of the resource management method applied to the control plane entity provided by the embodiment of the invention, as shown in fig. 9, comprises the following steps:

in 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 for 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 resources and authorize resources during group establishment. In the 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. In an alternative process flow of the resource management method shown in fig. 3, the SMF entity obtains subscription information of the terminal device from a user plane entity (e.g., UDM entity), and verifies whether a session establishment request message of the terminal device passes or not according to the subscription information. Or the SMF entity sends the received session establishment request message to a user plane entity (such as a UDM entity), and the UDM entity verifies whether the session establishment request message of the terminal equipment passes. Wherein the subscription information includes: whether the terminal equipment allows the application of the corresponding service at the PC5 interface, and/or whether the terminal equipment allows the application of the resource attribute of the service at the PC5 interface. After the verification is passed, the control plane entity sends a service request message to the access network element according to the received session establishment request message, wherein the service request message is used for allocating resources for the terminal equipment by the access network element.

In other embodiments, the network device allocates resources to the terminal device during the group establishment, that is, the terminal device provides the group information related to the NCIS and the related information of the service during the group establishment, and the network device allocates resources according to the group information related to the NCIS and the related information of the service; and the resources are activated once allocated to take effect. In an alternative process flow of the resource management method shown in fig. 4, before the control plane entity receives the resource request message, the control plane entity sends the information of the allocable resources sent by the user plane entity to the terminal device through the protocol message unit, where the information of the allocable resources 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 an RRC message, wherein 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. 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 equipment through N2 and RRC messages; the information of the allocable resources is determined by a control plane entity after verifying that the subscription information or the authorization information of the terminal device passes.

In still other embodiments, the terminal device requests resources during session establishment, and activates resources based on the resource request; it will be appreciated that the resource allocation context is established during session establishment and that the PC5 resource configuration information will be saved after 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 demands while maintaining session connection. In an alternative process flow of the resource management method shown in fig. 5, after the terminal device deactivates the session or deactivates the 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. And then, the SMF entity sends the content in the service establishment request message to the access network element. If the access network element has no resource-related configuration information, the SMF entity sends the 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 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 a context of resource allocation and does not allocate resources in the session establishment process; the terminal device requests allocation of resources each time a service request is initiated. In an alternative process flow of the resource management method shown in fig. 6, after the terminal device deactivates the session or deactivates the resource in the session, the 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 the service establishment request message sent by the terminal device, and sends the service establishment request message sent by the device to the SMF entity. And 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 for the terminal equipment 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; in an alternative process flow of the resource management method shown in fig. 7, 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 by an access network element to allocate resources for the terminal device. The resource request information includes: requested traffic information, such as session information, qoS flow information, traffic flow information, etc.

In other embodiments, the terminal device applies for resources by providing corresponding resources through the user plane; the resource information allocated for the terminal device is configured to the terminal device through an interface between the terminal device and the AF. In an alternative process flow of the resource management method shown in fig. 8, 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 an access network element.

The process flow of the resource management method applied to the access network element provided by the embodiment of the invention, as shown in fig. 10, comprises the following steps:

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

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

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

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

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 is granularity of bandwidth, or the number of the resources is granularity of bandwidth in preset time. The QoS parameters include at least one of: delay information, minimum rate information, maximum rate information, and reliability information.

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

The first sending unit 1101 is configured to send resource request information to a network device, where the resource request information is used for 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 for the terminal device. Wherein the session establishment request message includes 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 is configured to send requested resource information, where the requested resource information is used by the network device to determine an allocable resource of the terminal device.

Optionally, the second sending unit 1102 is configured to send a group setup request message to a server or an NCIS function server, so that a core network element determines an allocable resource 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.

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

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

Optionally, the terminal device 1100 further includes: and 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 resources in the session, where the service establishment request message is used for the core network element to request the access network element to allocate resources to the terminal device.

Wherein the service establishment request message includes session information 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 sending a session establishment request and a resource allocation request message to an access network element by the core 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: service 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 for the access network element to allocate resources for the terminal device. Wherein the resource request information includes: requested service information.

Optionally, the terminal device 1100 further includes: a first establishing unit 1105 is 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 resources 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 for the terminal device.

Optionally, the terminal device 1100 further includes: a third receiving unit 1108 is configured to receive the resources allocated by the access network element 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 is granularity of bandwidth, or the number of the resources is granularity of bandwidth in preset time. 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 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 is configured to receive a resource request message, where the resource request message is used for allocating resources for the terminal device by the access network element.

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 obtain 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 1200 further includes: 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. Wherein the subscription information includes: whether the terminal equipment allows the application of the corresponding service at the PC5 interface, and/or whether the terminal equipment allows the application of the resource attribute of the service at the PC5 interface.

Optionally, the control plane entity 1200 further includes: and a fifth sending unit 1204, 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 for the access network element to allocate resources for the terminal device.

Optionally, the control plane entity 1200 further includes: a sixth sending unit 1205 is configured to send information of the allocable resources sent by the user plane entity to the terminal device through a protocol message unit, where the information of the allocable resources 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 is configured to send information of the allocable resources sent by the user plane entity to the terminal device through a radio resource control RRC message, where the information of the 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 transmitting unit 1207 configured to transmit the information of the allocable resources transmitted by the user plane entity to the terminal device through a NAS message; or the information of the allocable resources sent by the user plane entity is sent to the terminal equipment through an N2 and RRC message; the information of the allocable resources is determined by a control plane entity after verifying that the subscription information or the authorization information of the terminal device passes.

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 is 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 session information 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 for the access network element to allocate resources for the terminal device.

Optionally, the control plane entity 1200 further includes: an eleventh sending unit 1210 is 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 for 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: service related QoS information and/or resource request information.

Optionally, the control plane entity 1200 further includes: the second processing unit 1211 is configured to obtain QoS information and/or resource request information related to the service 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 for the access network element to allocate resources for the terminal device. The resource request information includes: requested service information.

Optionally, the control plane entity 1200 further includes: a second establishing unit 1212 is 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 an 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 is granularity of bandwidth, or the number of the resources is granularity of bandwidth in preset time. 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.

The embodiment of the present invention further provides an access network element, a composition 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 for the terminal device according to the 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 is granularity of bandwidth, or the number of the resources is granularity of bandwidth in preset time. 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 invention also provides a terminal device, which comprises a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is used for executing the steps of the resource management method executed by the terminal device when the computer program runs.

The embodiment of the invention also provides a control plane entity, which comprises a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is used for executing the steps of the resource management method executed by the control plane entity when the computer program runs.

The embodiment of the invention also provides an access network element, which comprises a processor and a memory for storing a computer program capable of running on the processor, wherein the processor is used for executing the steps of the resource management method executed by the access network element when running the computer program.

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

It is to be appreciated that memory 1402 can be either volatile memory or nonvolatile memory, and can include both volatile and nonvolatile memory. Wherein the nonvolatile Memory may be ROM, programmable read-Only Memory (PROM, programmable Read-Only Memory), erasable programmable read-Only Memory (EPROM, erasable Programmable Read-Only Memory), electrically erasable programmable read-Only Memory (EEPROM, electrically Erasable Programmable Read-Only Memory), magnetic random access Memory (FRAM, ferromagnetic random access Memory), flash Memory (Flash Memory), magnetic surface Memory, optical disk, or compact disk read-Only Memory (CD-ROM, compact Disc Read-Only Memory); the magnetic surface memory may be a disk memory or a tape memory. The volatile memory may be random access memory (RAM, random Access Memory), which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (SRAM, static Random Access Memory), synchronous static random access memory (SSRAM, synchronous Static Random Access Memory), dynamic random access memory (DRAM, dynamic Random Access Memory), synchronous dynamic random access memory (SDRAM, synchronous Dynamic Random Access Memory), double data rate synchronous dynamic random access memory (ddr SDRAM, double Data Rate Synchronous Dynamic Random Access Memory), enhanced synchronous dynamic random access memory (ESDRAM, enhanced Synchronous Dynamic Random Access Memory), synchronous link dynamic random access memory (SLDRAM, syncLink Dynamic Random Access Memory), direct memory bus random access memory (DRRAM, direct Rambus Random Access Memory). Memory 1402 described by embodiments of the present invention is intended to comprise, without being limited to, these and any other suitable types of memory.

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

The method disclosed in the above embodiment of the present invention may be applied to the processor 1401 or implemented by the processor 1401. The processor 1401 may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuitry of hardware in the processor 1401 or instructions in the form of software. The processor 1401 as described above may be a general purpose processor, a digital signal processor (DSP, digital Signal Processor), or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. The processor 1401 may implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present invention. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in the embodiment of the invention can be directly embodied in the hardware of the 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 including memory 1402, and processor 1401 reads information in memory 1402 and performs the steps of the methods described above in connection with its hardware.

In an exemplary embodiment, the electronic device 1400 may be implemented by one or more application specific integrated circuits (ASIC, application Specific Integrated Circuit), DSPs, programmable logic devices (PLDs, programmable Logic Device), complex programmable logic devices (CPLDs, complex Programmable Logic Device), FPGAs, general purpose processors, controllers, MCUs, MPUs, or other electronic elements for performing the aforementioned methods.

Embodiments of the present application also provide a computer-readable storage medium for storing a computer program.

Optionally, the computer readable storage medium may be applied to a network device in the embodiments of the present application, and the computer program causes a computer to execute a corresponding flow implemented by the network device in each method in the embodiments of the present application, which is not described herein for brevity.

Optionally, the computer readable storage medium may be applied to a terminal device in an embodiment of the present application, and the computer program causes a computer to execute a corresponding procedure implemented by the terminal device in each method of the embodiment of the present application, which is not described herein 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 flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations 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 not intended to limit the scope of the invention, but is intended to cover any modifications, equivalents, and improvements within the spirit and principles of the invention.

Claims

1. A method of resource management, the method comprising:

The method comprises the steps that terminal equipment sends resource request information to network equipment, wherein the resource request information is used for allocating resources for the terminal equipment by the network equipment; the resource is a resource used on a PC5 interface; the network equipment allocates resources for the terminal equipment so that a charging equipment entity of the network equipment charges data transmitted in a direct communication mechanism of the terminal equipment;

the terminal device sends resource request information to the network device, including:

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; wherein the session establishment request message includes at least one of: the network controls the group information related to the interactive service NCIS, the related information of the service and the resource request information.

2. The method of claim 1, wherein the method further comprises:

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

3. The method of claim 2, wherein the terminal device transmits the requested resource information, comprising:

the terminal equipment sends a group establishment request message to a server or a network control interaction service NCIS function server so that a core network element determines an allocable resource 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.

4. The method of claim 2, wherein the method further comprises:

the terminal device receives information of the allocable resources and service information.

5. The method of claim 4, wherein the terminal device receiving information of allocable resources comprises:

and the terminal equipment receives the information of the allocable resources sent by the core network element through the protocol message unit.

6. The method of claim 4, wherein the terminal device receiving information of allocable resources comprises:

and the terminal equipment receives the information of the allocable resources sent by the access network element through the Radio Resource Control (RRC) message.

7. The method of claim 4, wherein the terminal device receiving information of allocable resources comprises:

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

or the terminal equipment receives the information of the allocable resources sent by the core network element through the N2 and RRC messages.

8. The method of claim 4, 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.

9. The method of claim 1, wherein the terminal device deactivates the session or deactivates resources in the session, the method further comprising:

the terminal equipment sends a service establishment request message to a core network element, wherein the service establishment request message is used for requesting the core network element to an access network element to allocate resources for the terminal equipment.

10. The method of claim 9, wherein the service setup request message includes session information required to be activated.

11. The method of claim 10, wherein the service setup request message further comprises:

Quality of service QoS flow information and/or traffic flow information.

12. 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 sending a session establishment request and a resource allocation request message to an access network element by the core network element so that the access network element allocates resources for the terminal equipment.

13. The method of claim 12, wherein the service setup request message comprises: requested service information.

14. The method of claim 13, wherein the service setup request message further comprises:

service related QoS information and/or resource request information.

15. 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 an access network element, wherein the resource request information is used for allocating resources for the terminal equipment by the access network element.

16. The method of claim 15, wherein the resource request information comprises: requested service information.

17. The method according to claim 15 or 16, wherein the method further comprises:

and the terminal equipment establishes a session with a core network element.

18. The method according to claim 15 or 16, wherein the method further comprises:

the terminal equipment configures QoS information and/or resource configuration information.

19. The method of any one of claims 1 to 16, wherein the method further comprises:

and the terminal equipment receives the resources allocated by the network element of the access network.

20. 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 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.

21. The method of claim 20, 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.

22. The method of any of claims 1-16 or 20-21, wherein the resource request information comprises:

Resource parameters and/or QoS parameters.

23. The method of claim 22, wherein the resource parameters comprise:

the number of resources and/or the transmission rate;

the number of the resources is granularity of bandwidth, or the number of the resources is granularity of bandwidth in preset time.

24. The method of claim 22, wherein the QoS parameters comprise at least one of:

delay information, minimum rate information, maximum rate information, and reliability information.

25. The method of any of claims 1-16 or 20-21, wherein the granularity of the resource request information is a session granularity, or a QoS flow granularity, or a traffic flow granularity.

26. A method of resource management, the method comprising:

a control plane entity receives a resource request message, wherein the resource request message is used for an access network element to allocate resources for terminal equipment; the resource is a resource used on a PC5 interface; the access network element is configured to feed back the allocated resources to a core network element, so that the core network element feeds back the allocated resources to a charging equipment entity, and the charging equipment entity charges data transmitted in a direct communication mechanism of the terminal device;

Wherein the control plane entity receives the resource request information, including:

the control plane entity receives a session establishment request message sent by the terminal equipment; the session establishment request message is used for the control plane entity to send a service request message to the access network element, so that the access network element allocates resources for the terminal equipment; wherein the session establishment request message includes at least one of: the network controls the group information related to the interactive service NCIS, the related information of the service and the resource request information.

27. The method of claim 26, wherein the method further comprises:

the control plane entity obtains 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.

28. The method of claim 26, wherein the method further comprises:

the control plane entity sends the session establishment request message to a user plane entity, wherein 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.

29. The method of claim 27, wherein the subscription information comprises:

whether the terminal equipment allows the application of the corresponding service at the PC5 interface, and/or whether the terminal equipment allows the application of the resource attribute of the service at the PC5 interface.

30. The method of any one of claims 26 to 29, 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 allocating resources for the terminal equipment by the access network element.

31. The method of claim 26, 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 a protocol message unit, 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.

32. The method of claim 26, wherein the method further comprises:

and the control plane entity transmits the information of the allocable resources transmitted 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 subscription information or the authorization information of the terminal equipment is verified to pass.

33. The method of claim 26, 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 equipment through N2 and RRC messages;

the information of the allocable resources is determined by a control plane entity after verifying that the subscription information or the authorization information of the terminal device passes.

34. The method of claim 26, wherein the control plane entity receiving a resource request message comprises:

after the terminal equipment deactivates the session or deactivates the resource in the session, the control plane entity receives a service establishment request message sent by the terminal equipment, where the service establishment request message carries resource request information.

35. The method of claim 34, wherein the method further comprises:

and the control plane entity sends the content in the service establishment request message to the access network element.

36. The method of claim 35, wherein the method further comprises:

and the control plane entity sends resource configuration information to the access network element.

37. A method according to any of claims 34 to 36, wherein the service set-up request message comprises session information for which activation is required.

38. The method of claim 37, wherein the service setup request message further comprises:

quality of service QoS flow information and/or traffic flow information.

39. The method of claim 26, wherein the control plane entity receiving resource request information comprises:

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 allocating resources for the terminal equipment by the access network element.

40. The method of claim 39, wherein the method further comprises:

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.

41. The method of claim 39 or 40, wherein the service establishment request message comprises: requested service information.

42. The method of claim 41, wherein the service setup request message further comprises:

Service related QoS information and/or resource request information.

43. The method of claim 39 or 40, 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.

44. The method of claim 26, wherein the control plane entity receiving resource request information comprises:

and the control plane entity receives resource request information sent by the terminal equipment, wherein the resource request information is used for allocating resources for the terminal equipment by the access network element.

45. The method of claim 44, wherein the resource request information comprises: requested service information.

46. The method of claim 44 or 45, wherein the method further comprises:

the control plane entity establishes a session of the terminal device.

47. The method of claim 26, wherein the control plane entity receiving resource request information comprises:

and the control plane entity receives the resource request information sent by the server or the network control interaction service NCIS function server.

48. The method of claim 47, 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 an access network element.

49. The method of any of claims 26 to 29, wherein the resource request information comprises:

resource parameters and/or QoS parameters.

50. The method of claim 49, wherein the resource parameters comprise:

the number of resources and/or the transmission rate;

51. The method of claim 49, wherein the QoS parameters include at least one of:

52. The method of any of claims 26 to 29, wherein the granularity of the resource request information is a session granularity, or a QoS flow granularity, or a traffic flow granularity.

53. A method of resource management, the method comprising:

the access network element receives the resource request information;

the access network element allocates resources for the terminal equipment based on the resource request information; the resource is a resource used on a PC5 interface; the access network element feeds back the allocated resources to a core network element, so that the core network element feeds back the allocated resources to a charging equipment entity, and the charging equipment entity charges data transmitted in a direct communication mechanism of the terminal equipment;

Wherein the access network element receives resource request information, including:

the access network element receives a service request message sent by a core network element based on a session establishment request message, so that the access network element allocates resources for the terminal equipment; wherein the session establishment request message includes at least one of: the network control interaction service NCIS related group information, business related information and the resource request information; and the service request message carries the resource request information.

54. The method of claim 53, wherein the access network element allocates resources for a terminal device based on the resource request information, comprising:

and the access network element allocates resources for the terminal equipment according to the QoS information allowed by the terminal equipment.

55. A method according to claim 54 wherein the QoS information allowed by the terminal device is determined by a core network element based on group information and/or session information to which the terminal device belongs.

56. The method of any of claims 53 to 55, wherein the resource request information comprises:

resource parameters and/or QoS parameters.

57. The method of claim 56, wherein the resource parameters include:

The number of resources and/or the transmission rate;

58. The method of claim 56, wherein the QoS parameters include at least one of:

59. A method according to any of claims 53 to 55, wherein the granularity of the resource request information is session granularity, or QoS flow granularity, or traffic flow granularity.

60. 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 for the network device to allocate resources for the terminal device; the resource is a resource used on a PC5 interface; the network equipment allocates resources for the terminal equipment so that a charging equipment entity of the network equipment is used for charging data transmitted in a direct communication mechanism of the terminal equipment;

the first sending unit is specifically 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; wherein the session establishment request message includes at least one of: the network controls the group information related to the interactive service NCIS, the related information of the service and the resource request information.

61. The terminal device of claim 60, wherein the terminal device further comprises:

and the second sending unit is configured to send the requested resource information, wherein the requested resource information is used for the network equipment to determine the allocable resources of the terminal equipment.

62. The terminal device of claim 61, wherein the second sending unit is specifically configured to send a group setup request message to a server or a network control interaction service NCIS function server, so that a core network element determines an allocable resource of the terminal device based on the group setup request message sent by the server or the NCIS function server;

63. The terminal device of claim 61, wherein the terminal device further comprises:

and a first receiving unit configured to receive the information of the allocable resources and the service information.

64. The terminal device of claim 63, wherein the first receiving unit is specifically configured to receive, via a protocol message unit, information of the allocable resources sent by a core network element.

65. The terminal device of claim 63, wherein the first receiving unit is specifically configured to receive the information of the allocable resources sent by the access network element through a radio resource control RRC message.

66. The terminal device of claim 63, wherein the first receiving unit is specifically configured to receive, via a NAS message, information of the allocable resources sent by a core network element;

or receiving the information of the allocable resources sent by the core network element through the N2 and RRC messages.

67. The terminal device of claim 63, wherein said first receiving unit is specifically configured to receive information of said allocatable resources sent by a server or an NCIS function server via an interface message protocol.

68. The terminal device of claim 60, wherein the terminal device further comprises:

and the third sending unit is configured to send a service establishment request message to a core network element after the terminal equipment deactivates the session or deactivates the resources in the session, wherein the service establishment request message is used for requesting the core network element to allocate the resources to the access network element.

69. The terminal device of claim 68, wherein the service establishment request message includes session information to be activated.

70. The terminal device of claim 69, wherein the service setup request message further comprises:

quality of service QoS flow information and/or traffic flow information.

71. The terminal device of claim 60, wherein the first sending unit is specifically configured to send a service establishment request message to a core network element, where the service establishment request message is used for sending a session establishment request and a resource allocation request message to an access network element by the core network element, so that the access network element allocates resources for the terminal device.

72. The terminal device of claim 71, wherein the service setup request message comprises: requested service information.

73. The terminal device of claim 72, wherein the service setup request message further comprises:

service related QoS information and/or resource request information.

74. The terminal device of claim 60, wherein the first sending unit is specifically 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 for the terminal device.

75. The terminal device of claim 74, wherein the resource request information includes: requested service information.

76. The terminal device of claim 74 or 75, wherein the terminal device further comprises:

a first establishing unit configured to establish a session with a core network element.

77. The terminal device of claim 74 or 75, wherein the terminal device further comprises:

and a configuration unit configured to configure the QoS information and/or the resource configuration information.

78. The terminal device of any of claims 60 to 75, 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.

79. The terminal device of claim 60, wherein the first sending unit is specifically 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 for the terminal device.

80. The terminal device of claim 79, wherein the terminal device further comprises:

and the third receiving unit is configured to receive the resources distributed by the access network element transmitted by the server or the NCIS function server.

81. The terminal device of any of claims 60 to 75 or 79 to 80, wherein the resource request information comprises:

resource parameters and/or QoS parameters.

82. The terminal device of claim 81, wherein the resource parameter comprises:

the number of resources and/or the transmission rate;

83. The terminal device of claim 82, wherein the QoS parameters include at least one of:

84. The terminal device of any of claims 60 to 75 or 79 to 80, wherein the granularity of the resource request information is a session granularity, or a QoS flow granularity, or a traffic flow granularity.

85. 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 for an access network element to allocate resources for a terminal device; the resource is a resource used on a PC5 interface; the access network element is configured to feed back the allocated resources to a core network element, so that the core network element feeds back the allocated resources to a charging equipment entity, and the charging equipment entity charges data transmitted in a direct communication mechanism of the terminal device;

The fourth receiving unit is specifically configured to receive a session establishment request message sent by the terminal device, where the session establishment request message is used to send a service request message to the access network element, so that the access network element allocates resources for the terminal device; wherein the session establishment request message includes at least one of: the network controls the group information related to the interactive service NCIS, the related information of the service and the resource request information.

86. The control plane entity of claim 85, wherein said control plane entity further comprises:

the first processing unit is configured to acquire subscription information of the terminal equipment from a user plane entity, and verify whether a session establishment request message of the terminal equipment passes or not according to the subscription information.

87. The control plane entity of claim 85, wherein said control plane entity further comprises:

and 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 to the user plane entity to verify whether the session establishment request message of the terminal device passes.

88. The control plane entity of claim 86, wherein the subscription information comprises:

89. The control plane entity of any one of claims 85 to 88, wherein said control plane entity further comprises:

and 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 for the terminal device.

90. The control plane entity of claim 85, wherein said control plane entity further comprises:

and the sixth sending unit is configured to send the information of the allocable resources sent by the user plane entity to the terminal equipment through the protocol message unit, wherein the information of the allocable resources is determined after the subscription information or the authorization information of the terminal equipment is verified to pass.

91. The control plane entity of claim 85, wherein said control plane entity further comprises:

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

92. The control plane entity of claim 85, wherein said control plane entity further comprises:

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

or the information of the allocable resources sent by the user plane entity is sent to the terminal equipment through an N2 and RRC message;

93. The control plane entity of claim 85, wherein the fourth receiving unit is specifically configured to receive a service establishment request message sent by a terminal device after the terminal device deactivates a session or deactivates a resource in a session, where the service establishment request message carries resource request information.

94. The control plane entity of claim 93, wherein said control plane entity further comprises:

and a ninth sending unit configured to send the content in the service establishment request message to the access network element.

95. The control plane entity of claim 94, wherein said control plane entity further comprises:

And a tenth sending unit configured to send resource configuration information to the access network element.

96. The control plane entity of any one of claims 93 to 95, wherein the service set-up request message comprises session information for which activation is required.

97. The control plane entity of claim 96, wherein said service set up request message further comprises:

quality of service QoS flow information and/or traffic flow information.

98. The control plane entity of claim 85, wherein the fourth receiving unit is specifically 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 for the terminal device.

99. The control plane entity of claim 98, wherein said 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 for the terminal device according to the session establishment request and the resource allocation request message.

100. The control plane entity of claim 98 or 99, wherein the service set-up request message comprises: requested service information.

101. The control plane entity of claim 100, wherein said service set-up request message further comprises:

service related QoS information and/or resource request information.

102. The control plane entity of claim 98 or 99, wherein the control plane entity further comprises:

and the second processing unit is configured to acquire service related QoS information and/or resource request information according to the service establishment request message.

103. The control plane entity of claim 85, wherein the fourth receiving unit is specifically 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 for the terminal device.

104. The control plane entity of claim 103, wherein the resource request information comprises: requested service information.

105. The control plane entity of claim 103 or 104, wherein said control plane entity further comprises:

and the second establishing unit is configured to establish the session of the terminal equipment.

106. The control plane entity of claim 85, wherein said fourth receiving unit is specifically configured to receive resource request information sent by a server or a network control interaction service NCIS function server.

107. The control plane entity of claim 106, wherein said 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;

108. The control plane entity of any one of claims 85 to 88, wherein the resource request information comprises:

resource parameters and/or QoS parameters.

109. The control plane entity of claim 108, wherein said resource parameters comprise:

the number of resources and/or the transmission rate;

110. The control plane entity of claim 108, wherein the QoS parameters comprise at least one of:

111. The control plane entity of any one of claims 85 to 88, wherein the granularity of the resource request information is a session granularity, or a QoS flow granularity, or a traffic flow granularity.

112. An access network element, the access network element comprising:

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

a fourth processing unit configured to allocate resources for the terminal device based on the resource request information; the resource is a resource used on a PC5 interface; the access network element feeds back the allocated resources to a core network element, so that the core network element feeds back the allocated resources to a charging equipment entity, and the charging equipment entity charges data transmitted in a direct communication mechanism of the terminal equipment;

the fifth receiving unit is specifically configured to receive a service request message sent by a core network element based on a session establishment request message, so that the access network element allocates resources for the terminal device; wherein the session establishment request message includes at least one of: the network control interaction service NCIS related group information, business related information and the resource request information; and the service request message carries the resource request information.

113. The access network element of claim 112, wherein the fourth processing element is specifically configured to allocate resources for the terminal device according to quality of service, qoS, information allowed by the terminal device.

114. The access network element of claim 113, wherein the terminal device-allowed QoS information is determined by a core network element from group information and/or session information to which the terminal device belongs.

115. An access network element according to any of claims 112 to 114, wherein the resource request information comprises:

resource parameters and/or QoS parameters.

116. The access network element of claim 115, wherein the resource parameters comprise:

the number of resources and/or the transmission rate;

117. The access network element of claim 115 or 116, wherein the QoS parameters comprise at least one of:

118. An access network element according to any of claims 112 to 114, wherein the granularity of the resource request information is session granularity, or QoS flow granularity, or traffic flow granularity.

119. A terminal device comprising a processor and a memory for storing a computer program capable of running on the processor, wherein,

The processor being adapted to perform the steps of the resource management method of any of claims 1 to 25 when the computer program is run.

120. A control plane entity comprising a processor and a memory for storing a computer program capable of running on the processor, wherein,

the processor being adapted to perform the steps of the resource management method of any of claims 26 to 52 when the computer program is run.

121. An access network element comprising a processor and a memory for storing a computer program capable of running on the processor, wherein,

the processor being adapted to perform the steps of the resource management method of any of claims 53 to 59 when the computer program is run.

122. 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 25.

123. A storage medium storing an executable program which, when executed by a processor, implements the resource management method of any one of claims 26 to 52.

124. A storage medium storing an executable program which, when executed by a processor, implements the resource management method of any one of claims 53 to 59.