CN107113186B

CN107113186B - Method and common service entity for data transmission in unified machine-to-machine system

Info

Publication number: CN107113186B
Application number: CN201480084395.6A
Authority: CN
Inventors: 尹长川; 武霄泳; 于琦
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2014-12-24
Filing date: 2014-12-24
Publication date: 2020-02-14
Anticipated expiration: 2034-12-24
Also published as: WO2016101163A1; CN107113186A

Abstract

The embodiment of the invention provides a method for unifying data transmission in a machine-to-machine system and a public service entity. The method comprises the following steps: acquiring an application layer QoS variable parameter, wherein the application layer QoS variable parameter is used for expressing the quality requirement of an application on transmission data; mapping the application layer QoS variable parameter into a target QoS variable parameter which can be identified by the underlying network; and sending the target QoS variable parameter to a Network Service Entity (NSE) so that the NSE can transmit data according to the target QoS variable parameter. The data transmission method provided by the embodiment of the invention can meet the requirements of the application under different application scenes on the QoS of the network under the oneM2M system.

Description

Method and common service entity for data transmission in unified machine-to-machine system

Technical Field

The present invention relates to the field of communications, and more particularly, to a method and common service entity for unifying data transmission in a machine-to-machine system.

Background

The structure of a unified Machine to Machine (oneM 2M for short) system is divided into an application layer, a common service layer, and a network layer. Wherein, the Application layer is managed by an Application Entity (AE) to take charge of the relevant operation and storage of the Application, and the Application layer contains an instantiated end-to-end oneM2M solution. The Common Services layer is managed by a Common Services Entity (CSE) responsible for aggregating application layer information to form a resource pool while coordinating underlying network transmission, and is a core layer in oneM2M functioning as a platform, and the Common Services layer includes a series of instantiated Common service functions. The Network layer is managed by a Network Service Entity (NSE) and is responsible for underlying Network transmission, and provides the capability that the underlying Network can provide to the common service layer.

There are 3 reference points (i.e., interfaces) between layers in oneM2M system, where Mca: the interface between the AE and the CSE is responsible for communication from the AE to the CSE or from the CSE to the AE; Mcc/Mcc': the interface between the two CSEs is responsible for communication between the CSEs; mcn: the interface between the CSE and NSE is responsible for CSE to NSE or NSE to CSE communications. There is also a Mch reference point, which is the interface between the oneM2M system and the charging system.

The oneM2M system architecture is mainly divided into two domains: an Infrastructure Domain (IN) AND a local Domain (Field Domain) including a Middle Node (MN), an Application Service Node (ASN), AND an Application Dedicated Node (AND). Wherein nodes other than the ADN node contain only AEs contain CSEs.

To efficiently deploy and unify machine-to-machine (M2M) communication systems, driving the convergence of the M2M global standard with vertical industry applications, the globalized standards organization oneM2M arose. The primary goal of oneM2M is to unify M2M application level standards in the communications industry to promote efficient collaboration within the communications industry. The oneM2M standard employs a layered functional architecture, with communication between layers being accomplished via a unified interface, and the oneM2M system requires simultaneous compatibility with different underlying access networks (including but not limited to third generation partnership project partners (3)^rdGeneration Partnership Project, abbreviated as "3 GPP", Wireless Fidelity (abbreviated as "WiFi"), Bluetooth (Blue Tooth)).

With the rapid development of the internet of things technology, the application scenarios covered by the oneM2M system become wide, the Service requirements are more diverse, and in many scenarios, the application has corresponding requirements for the Quality of Service (QoS) of the network. For example, in a traffic system, a vehicle accident information collection system has higher requirements on time delay; and the remote medical application has higher requirements on the time delay and the packet loss rate of the network. The oneM2M system needs to have the capability to support different QoS ranking parameters, such as: rate, delay, packet loss rate, bit error rate, network bandwidth, etc.

The existing oneM2M standard adopts a resource-oriented representational State Transfer (RESTful) architecture, and a data transmission guarantee mechanism under the oneM2M system is realized by combining a Transfer (< delivery >) resource and a communication transmission management (< cmdhpolicy >) strategy under the CSE and changing related parameters of a data transmission State in a request message (request). There are no QoS representation mechanism based on traffic transmission requirements, QoS mapping mechanism to underlying network, end-to-end QoS transmission mechanism. Therefore, the data transmission guarantee mechanism can only guarantee the most basic transmission requirement of data, and cannot meet the requirements of many existing application scenarios.

Currently, in the related art, a central resource manager and a service controller are used to define a service and QoS parameters thereof, and based on an Internet Protocol (IP) network, the QoS parameters are mapped to Differentiated Services Code Points (DSCP), and the QoS parameters are transferred through a route, thereby ensuring the quality of the service. However, in the technical scheme, the transfer of the QoS parameters needs to be completed by means of the DSCP part in the IP packet, so that the technical scheme is mainly based on a 3GPP network and cannot be well applied to all underlying networks in the OneM2M system.

Therefore, how to meet the QoS requirements of the application in different application scenarios on the network under the existing oneM2M system is a problem to be solved at present.

Disclosure of Invention

In view of this, embodiments of the present invention provide a method and a common service entity for unifying data transmission in a machine-to-machine oneM2M system, which can meet the QoS requirements of applications in different application scenarios on a network under the oneM2M system.

In a first aspect, a method for unifying data transmission in a machine-to-machine system is provided, including: acquiring an application layer QoS variable parameter, wherein the application layer QoS variable parameter is used for expressing the quality requirement of an application on transmission data; mapping the application layer QoS variable parameter into a target QoS variable parameter which can be identified by the underlying network; and sending the target QoS variable parameter to a Network Service Entity (NSE) so that the NSE can transmit data according to the target QoS variable parameter.

With reference to the first aspect, in a first possible implementation manner of the first aspect, the mapping the application layer QoS variable parameter to a target QoS variable parameter recognizable by an underlying network includes: determining the maximum value and the minimum value of a QoS window of the underlying network and the window length offset of the QoS window of the underlying network, wherein the QoS window is used for expressing the interval of the comprehensive indexes of the QoS of the underlying network; and obtaining the target QoS variable parameter according to the maximum value and the minimum value of the QoS window of the underlying network, the window length offset of the QoS window of the underlying network and a QoS rule mapping table included by the current use strategy resource.

With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the determining the maximum value and the minimum value of the QoS window of the underlying network and the window length offset of the QoS window of the underlying network includes: determining the value of the parameter which is not assigned with the initial value in the QoS variable parameter of the application layer according to the QoS variable default value attribute included in the current used strategy resource; when the value of each parameter in the application layer QoS variable parameter meets the requirement of the QoS parameter limit attribute included by the current use strategy resource, determining the maximum value and the minimum value of the QoS window of the underlying network according to the QoS window length attribute included by the current use strategy resource; and determining the window length offset of the QoS window of the underlying network according to the value of each parameter in the application layer QoS variable parameters and the QoS window length offset attribute included in the current use strategy resource.

With reference to the first or second possible implementation manner of the first aspect, in a third possible implementation manner of the first aspect, the obtaining the variable parameter of the application layer quality of service QoS includes: receiving a first request message sent by an application entity AE or a common service entity CSE, wherein the first request message comprises the variable parameter of the QoS of the application layer; and acquiring the application layer QoS variable parameter included in the first request message.

With reference to the third possible implementation manner of the first aspect, in a fourth possible implementation manner of the first aspect, the determining the maximum value and the minimum value of the QoS window of the underlying network and the window length offset of the QoS window of the underlying network includes: upon determining that the QoS control parameter included in the first request message is enabled, determining a maximum value and a minimum value of a QoS window of the underlying network and a window length offset of the QoS window of the underlying network.

With reference to the first or second possible implementation manner of the first aspect, in a fifth possible implementation manner of the first aspect, the obtaining the variable parameter of the application layer quality of service QoS includes: receiving a second request message sent by AE or CSE, wherein the second request message is used for requesting to create QoS variable parameter resources under target resources; creating the QoS variant parameter resource including the application layer QoS variant parameter under the target resource; and acquiring the application layer QoS variable parameter included in the QoS variable parameter resource.

With reference to the fifth possible implementation manner of the first aspect, in a sixth possible implementation manner of the first aspect, the determining the maximum value and the minimum value of the QoS window of the underlying network and the window length offset of the QoS window of the underlying network includes: receiving a third request message including data information sent by the AE or the CSE; and when the destination scope for transmitting the third request message is determined to comprise the QoS variable parameter resource, determining the maximum value and the minimum value of the QoS window of the underlying network and the window length offset of the QoS window of the underlying network.

With reference to the fifth or sixth possible implementation manner of the first aspect, in a seventh possible implementation manner of the first aspect, the target resource is a common service entity basic CSEBase resource or an AE resource.

With reference to the seventh possible implementation manner of the first aspect, in an eighth possible implementation manner of the first aspect, the CSEBase resource or the AE resource further includes: QoS policy resources and the current usage policy resources; wherein the management link attribute of the currently used policy resource is associated with the QoS policy resource, and the QoS policy resource includes: QoS parameter restriction strategy resource, QoS parameter default value setting strategy resource, underlying network access strategy resource and QoS rule mapping table strategy resource.

With reference to the eighth possible implementation manner of the first aspect, in a ninth possible implementation manner of the first aspect, the QoS policy resource further includes 1 name attribute and M management link attributes, where M is a natural number greater than or equal to 3;

wherein the name attribute is used for representing the name of the QoS policy included in the QoS policy resource, at least one of the M management link attributes is associated with the QoS parameter limitation policy resource, at least one of the M management link attributes is associated with the QoS parameter default setting policy resource, and at least one of the M management link attributes is associated with the underlying network access policy resource.

With reference to the eighth or ninth possible implementation manner of the first aspect, in a tenth possible implementation manner of the first aspect, the QoS parameter restriction policy resource includes at least one of the following attributes: the data transmission average rate limiting attribute, the data transmission delay jitter limiting attribute, the packet loss limiting attribute, the data transmission reliability limiting attribute and the data transmission priority limiting attribute.

With reference to any one of the eighth to tenth possible implementation manners of the first aspect, in an eleventh possible implementation manner of the first aspect, the QoS parameter default setting policy resource includes at least one of the following attributes: the data transmission method comprises the following steps of setting an attribute for a data transmission average speed default value, a setting attribute for a data transmission delay jitter default value, a setting attribute for a packet loss rate, a setting attribute for data transmission reliability and a setting attribute for data transmission priority.

With reference to any one of the eighth to eleventh possible implementation manners of the first aspect, in a twelfth possible implementation manner of the first aspect, the underlying network access policy resource includes a target network attribute, a maximum attribute of a QoS window of an underlying network, a minimum attribute of the QoS window of the underlying network, and other condition attributes.

With reference to any one of the eighth to the twelfth possible implementation manners of the first aspect, in a thirteenth possible implementation manner of the first aspect, the policy resource of the QoS rule mapping table includes a QoS window length offset attribute of the underlying network and at least one of the following attributes: the data transmission average speed value range attribute, the data transmission delay jitter value range attribute, the packet loss rate value range attribute, the data transmission reliability value range attribute and the data transmission priority value range attribute.

With reference to the first aspect, any one of the first to thirteenth possible implementation manners of the first aspect, in a fourteenth possible implementation manner of the first aspect, the application layer QoS variable parameter includes at least one of the following parameters: the data transmission system comprises a data transmission average speed parameter, a data transmission delay jitter parameter, a packet loss rate parameter, a data transmission reliability parameter and a data transmission priority parameter.

In a second aspect, a common service entity is provided, comprising: the device comprises an acquisition module, a quality of service (QoS) module and a quality of service (QoS) module, wherein the acquisition module is used for acquiring an application layer QoS variable parameter which is used for expressing the quality requirement of an application on transmission data; the processing module is used for mapping the application layer QoS variable parameters acquired by the acquisition module into target QoS variable parameters which can be identified by the underlying network; a sending module, configured to send the target QoS variable parameter to a network service entity NSE, so that the NSE sends data according to the target QoS variable parameter.

With reference to the second aspect, in a first possible implementation manner of the second aspect, the processing module is specifically configured to: determining the maximum value and the minimum value of a QoS window of the underlying network and the window length offset of the QoS window of the underlying network, wherein the QoS window is used for expressing the interval of the comprehensive indexes of the QoS of the underlying network; and obtaining the target QoS variable parameter according to the maximum value and the minimum value of the QoS window of the underlying network, the window length offset of the QoS window of the underlying network and a QoS rule mapping table included by the current use strategy resource.

With reference to the first possible implementation manner of the second aspect, in a second possible implementation manner of the second aspect, the processing module is further specifically configured to: determining the value of the parameter which is not assigned with the initial value in the QoS variable parameter of the application layer according to the QoS variable default value attribute included in the current used strategy resource; when the value of each parameter in the application layer QoS variable parameter meets the requirement of the QoS parameter limit attribute included by the current use strategy resource, determining the maximum value and the minimum value of the QoS window of the underlying network according to the QoS window length attribute included by the current use strategy resource; and determining the window length offset of the QoS window of the underlying network according to the value of each parameter in the application layer QoS variable parameters and the QoS window length offset attribute included in the current use strategy resource.

With reference to the first or second possible implementation manner of the second aspect, in a third possible implementation manner of the second aspect, the common service entity further includes: a first receiving module, configured to receive a first request message sent by an application entity AE or a common service entity CSE, where the first request message includes the application layer QoS variable parameter;

wherein, this acquisition module is specifically used for: and acquiring the application layer QoS variable parameter included in the first request message received by the first receiving module.

With reference to the third possible implementation manner of the second aspect, in a fourth possible implementation manner of the second aspect, the processing module is specifically configured to: determining a maximum value and a minimum value of a QoS window of the underlying network and a window length offset of the QoS window of the underlying network when it is determined that the QoS control parameter included in the first request message received by the first receiving module is enabled.

With reference to the first or second possible implementation manner of the second aspect, in a fifth possible implementation manner of the second aspect, the common service entity further includes: a second receiving module, configured to receive a second request message sent by the AE or the CSE, where the second request message is used to request that a QoS variable parameter resource be created under a target resource; a creation module for creating the QoS variant parameter resource including the application layer QoS variant parameter under the target resource;

wherein, this acquisition module is specifically used for: and acquiring the application layer QoS variable parameter included in the QoS variable parameter resource created by the creation module.

With reference to the fifth possible implementation manner of the second aspect, in a sixth possible implementation manner of the second aspect, the second receiving module is further specifically configured to: receiving a third request message including data information sent by the AE or the CSE;

wherein, the processing module is specifically configured to: and when the destination scope for transmitting the third request message is determined to comprise the QoS variable parameter resource, determining the maximum value and the minimum value of the QoS window of the underlying network and the window length offset of the QoS window of the underlying network.

With reference to the fifth or sixth possible implementation manner of the second aspect, in a seventh possible implementation manner of the second aspect, the target resource is a common service entity basic CSEBase resource or an AE resource.

With reference to the seventh possible implementation manner of the second aspect, in an eighth possible implementation manner of the second aspect, the CSEBase resource or the AE resource further includes: QoS policy resources and current usage policy resources; wherein the management link attribute of the currently used policy resource is associated with the QoS policy resource, and the QoS policy resource includes: QoS parameter restriction strategy resource, QoS parameter default value setting strategy resource, underlying network access strategy resource and QoS rule mapping table strategy resource.

With reference to the eighth possible implementation manner of the second aspect, in a ninth possible implementation manner of the second aspect, the QoS policy resource further includes 1 name attribute and M management link attributes, where M is a natural number greater than or equal to 3;

With reference to any one of the eighth possible implementation manner or the ninth possible implementation manner of the second aspect, in a tenth possible implementation manner of the second aspect, the QoS parameter restriction policy resource includes at least one of the following attributes: the data transmission average rate limiting attribute, the data transmission delay jitter limiting attribute, the packet loss limiting attribute, the data transmission reliability limiting attribute and the data transmission priority limiting attribute.

With reference to any one of the eighth to tenth possible implementation manners of the second aspect, in an eleventh possible implementation manner of the second aspect, the QoS parameter default value setting policy resource includes at least one of the following attributes: the data transmission method comprises the following steps of setting an attribute for a data transmission average speed default value, a setting attribute for a data transmission delay jitter default value, a setting attribute for a packet loss rate, a setting attribute for data transmission reliability and a setting attribute for data transmission priority.

With reference to any one of the eighth to eleventh possible implementation manners of the second aspect, in a twelfth possible implementation manner of the second aspect, the underlying network access policy resource includes a target network attribute, a maximum attribute of a QoS window of the underlying network, a minimum attribute of the QoS window of the underlying network, and other condition attributes.

With reference to any one of the eighth to the twelfth possible implementation manners of the second aspect, in a thirteenth possible implementation manner of the second aspect, the QoS rule mapping table policy resource includes a QoS window length offset attribute of the underlying network and at least one of the following attributes: the data transmission average speed value range attribute, the data transmission delay jitter value range attribute, the packet loss rate value range attribute, the data transmission reliability value range attribute and the data transmission priority value range attribute.

With reference to the second aspect, any one of the first to thirteenth possible implementation manners of the second aspect, in a fourteenth possible implementation manner of the second aspect, the application layer QoS variable parameter includes at least one of the following parameters: the data transmission system comprises a data transmission average speed parameter, a data transmission delay jitter parameter, a packet loss rate parameter, a data transmission reliability parameter and a data transmission priority parameter.

Based on the scheme, the method for data transmission in the unified machine-to-machine system and the public service entity of the embodiment of the invention acquire the variable parameter of the quality of service (QoS) of the application layer, wherein the variable parameter of the QoS of the application layer is used for expressing the quality requirement of the application on the transmitted data; mapping the application layer QoS variable parameter into a target QoS variable parameter which can be identified by the underlying network; and sending the target QoS variable parameter to a Network Service Entity (NSE) so that the NSE can transmit data according to the target QoS variable parameter. Therefore, the requirement of the application under different application scenes on the QoS of the network under the oneM2M system can be met.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments of the present invention will be briefly described below, and it is obvious that the drawings described below are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1 is a schematic architecture diagram of a unified machine to machine system of an embodiment of the present invention;

FIG. 2 is a schematic flow chart diagram of a method for unifying data transfers in a machine-to-machine system provided by an embodiment of the present invention;

FIG. 3 is a schematic architecture diagram of a CSEBase resource provided by an embodiment of the invention;

FIG. 4 is a schematic architecture diagram of AE resources provided by an embodiment of the invention;

FIG. 5 is a schematic architecture diagram of QoS policy resources provided by an embodiment of the present invention;

FIG. 6 is a schematic flow chart diagram of a method for data transmission with message granularity in a data transmission process in a unified machine-to-machine system according to an embodiment of the present invention;

FIG. 7 is a schematic flow chart diagram of a method for data transfer at AE or CSE granularity in a data transfer process in a unified machine-to-machine system according to an embodiment of the present invention;

fig. 8 is a schematic flow chart diagram of a method of underlying network mapping provided by an embodiment of the present invention;

fig. 9 is a schematic flow chart of a method for QoS window-based mapping of an underlying network when the underlying network is 3GPP according to an embodiment of the present invention;

FIG. 10 is a schematic flow chart diagram of a method for end-to-end data transmission based on message granularity provided by an embodiment of the present invention;

FIG. 11 is a schematic diagram illustrating a data transmission process in a vehicle collision scenario, according to an embodiment of the present invention;

FIG. 12 is a schematic block diagram of a common service entity provided by an embodiment of the present invention;

FIG. 13 is another schematic block diagram of a common services entity provided by an embodiment of the present invention;

FIG. 14 is yet another schematic block diagram of a common services entity provided by an embodiment of the present invention;

fig. 15 is a schematic block diagram of a common service entity provided by another embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be obtained by a person skilled in the art without any inventive step based on the embodiments of the present invention, shall fall within the scope of protection of the present invention.

FIG. 1 illustrates a schematic architecture diagram of a unified machine-to-machine system provided by an embodiment of the present invention. As shown in fig. 1, the OneM2M system is divided into an application layer, a common service layer, and a network layer. The Application layer manages related operations and storage of the responsible Application by an Application Entity (AE), and an instantiated end-to-end oneM2M solution is included in the Application layer. The Common Services layer is managed by a Common Services Entity (CSE), which is a core layer in oneM2M that functions as a platform and is responsible for aggregating application layer information to form a resource pool while coordinating underlying network transport, and includes a series of instantiated Common service functions. The Network layer is managed by a Network Service Entity (NSE) and is responsible for the transmission of the underlying Network, and provides the capability which the underlying Network can provide to the common service layer.

The oneM2M system has 3 reference points (i.e. interfaces) between the lower layer and the interlayer, wherein Mca: the interface between the AE and the CSE is responsible for communication from the AE to the CSE or from the CSE to the AE; Mcc/Mcc': the interface between the two CSEs is responsible for communication between the CSEs; mcn: the interface between the CSE and NSE is responsible for CSE to NSE or NSE to CSE communications. A further Mch reference point (not shown) is the interface between the oneM2M system and the charging system.

It should be understood that in the embodiment of the present invention, all entities in the oneM2M system, such as AE, CSE, data, and the like, are represented in the form of resources. The resource structure defines in detail the way resources are represented and the way these resources are acquired. These resources are all independently addressable.

It should also be understood that the method for data transmission according to the embodiment of the present invention is applicable to all application scenarios in which a unified service entity or a unified application program interface provides services to an upper layer, is downward compatible with different underlying networks, and has different QoS service requests.

Fig. 2 shows a schematic flow diagram of a method 100 for data transmission in a unified machine to machine system according to an embodiment of the present invention, where the method 100 may be performed by a common service entity CSE. As shown in fig. 2, the method 100 includes:

s110, acquiring an application layer QoS variable parameter, wherein the application layer QoS variable parameter is used for expressing the quality requirement of an application on transmission data;

s120, mapping the variable parameter of the application layer QoS into a target variable parameter of QoS which can be identified by the underlying network;

s130, sending the target QoS variable parameter to a network service entity NSE, so that the NSE transmits data according to the target QoS variable parameter.

Specifically, the CSE acquires an application layer QoS variable parameter indicating a quality requirement of an application for transmitting data, maps the application layer QoS variable parameter to a target QoS variable parameter recognizable by an underlying network, and then sends the target QoS variable parameter to a network service entity NSE so that the NSE transmits data according to the target QoS variable.

Therefore, in the method for unifying data transmission in a machine-to-machine system according to the embodiment of the present invention, the CSE maps the application layer QoS variable parameter to the target QoS variable parameter recognizable by the underlying network, and sends the target QoS variable parameter to the NSE, so that the NSE can transmit data according to the target QoS variable parameter, thereby meeting the QoS requirements of applications under different application scenarios on the network under the oneM2M system.

It should be understood that, in the embodiment of the present invention, the application layer QoS variable parameter may refer to a QoS variable parameter carried in a request message request sent by an application entity AE of the source node or a CSE of the source node, or may refer to a QoS variable parameter included in a QoS variable parameter resource established by the request message request sent by the AE of the source node or the CSE of the source node.

It should also be understood that in embodiments of the present invention, an application may refer to an application program. Such as applications for gathering vehicle accident information in a transportation system, or telemedicine applications, etc., which are not intended to be limiting.

Optionally, in S110, the CSE of the intermediate node receives a first request message sent by the AE of the source node or the CSE of the source node, where the first request message includes the application layer QoS variable parameter. The application layer QoS variable parameter includes at least one of a data transmission average rate (dataRate) parameter, a data transmission delay (delay) parameter, a data transmission delay jitter (delayvariance) parameter, a packet loss rate (packetloss) parameter, a data transmission reliability (reliability) parameter, and a data transmission priority (priority) parameter. Wherein, the value range of the dataRate parameter can be 100-; the value range of the delay parameter can be 10-20 ms; the value of the delayVariation parameter may be less than 5ms, for example, 1ms, 2ms, 4ms, etc.; the value of the packetloss parameter is less than 1%; the reliability parameter is taken as reliable; the value of the priority parameter is less than 5, and can be 1, 2, 3, 4, etc., for example; the invention is not limited in this regard.

Accordingly, in S120, the CSE of the intermediate node determines, when determining that the QoS control parameter (QoSControl) included in the first request message is enabled, a maximum value (network qosmax) and a minimum value (network qosmin) of a QoS window of the network layer, the QoS window being for an interval representing a composite index of QoS of the underlying network, and a window length offset (network qosoffset) of the QoS window of the underlying network; and obtaining the target QoS variable parameter according to the maximum value and the minimum value of the QoS window of the underlying network, the window length offset of the QoS window of the underlying network and a QoS rule mapping table (QoSRuleList) included by the currently used policy resource. Wherein, the comprehensive index of the QoS indicates the service type (Traffic Class) of the 3GPP system in the 3GPP system, and includes: the traffic type (switching), Streaming media (Streaming), Interactive class (Interactive), and Background class (Background), and the overall QoS index indicates a Differentiated Services Code Point (DSCP) in the IP network.

Specifically, when determining that the QoS control parameter included in the first request message is enabled, the CSE of the intermediate node determines, according to the QoS variable default attribute included in the currently used policy resource, a value of a parameter that is not initialized in the application layer QoS variable parameter; when the value of each parameter in the application layer QoS variable parameter meets the requirement of the QoS parameter limit attribute included by the current use strategy resource, determining the maximum value and the minimum value of the QoS window of the underlying network according to the QoS window length attribute included by the current use strategy resource; determining the window length offset of the QoS window of the underlying network according to the value of each parameter in the application layer QoS variable parameter and the QoS window length offset attribute included in the current use strategy resource; and obtaining the target QoS variable parameter according to the maximum value and the minimum value of the QoS window of the underlying network, the window length offset of the QoS window of the underlying network and a QoS rule mapping table included by the current used policy resource.

In the embodiment of the present invention, optionally, the QoS control parameter is an optional parameter in the first request message, and when the QoS control parameter is not included in the first request message, the CSE of the intermediate node performs, by default, the relevant operation that should be performed when the QoS control parameter is enabled.

Optionally, in S110, the CSE of the intermediate node receives a second request message sent by the AE of the source node or the CSE of the source node, where the second request message is used to request that a QoS variable parameter resource be created under a target resource; the CSE of the intermediate node creates the QoS variable parameter resource comprising the application layer QoS variable parameter under the target resource according to the second request message; the CSE of the intermediate node acquires the application layer QoS variable parameter included in the QoS variable parameter resource. The target resource may be a CSEBase resource of the intermediate node or an AE resource of the intermediate node.

Accordingly, in S120, the CSE of the intermediate node receives the third request message including the data information sent by the AE or the CSE; when determining that the destination scope for transmitting the third request message includes the QoS variable parameter resource, determining a maximum value and a minimum value of a QoS window of the underlying network and a window length offset of the QoS window of the underlying network, where the QoS window is used for indicating an interval of a comprehensive index of QoS of the underlying network; and the CSE of the intermediate node obtains the target QoS variable parameter according to the maximum value and the minimum value of the QoS window of the underlying network, the window length offset of the QoS window of the underlying network and a QoS rule mapping table included by the current use policy resource. Wherein, the comprehensive index of the QoS in the 3GPP system refers to the service type of the 3GPP system, which comprises: call type, streaming media, interactive class and background class, refer to differentiated services codepoints in IP networks.

Specifically, the CSE of the intermediate node receives a third request message including data information sent by the AE or the CSE; when the destination scope for transmitting the third request message is determined to include the QoS variable parameter resource, determining the value of the parameter which is not assigned with the initial value in the application layer QoS variable parameter according to the QoS variable default value attribute included in the current used strategy resource; when the value of each parameter in the application layer QoS variable parameter meets the requirement of the QoS parameter limit attribute included by the current use strategy resource, determining the maximum value and the minimum value of the QoS window of the underlying network according to the QoS window length attribute included by the current use strategy resource; determining the window length offset of the QoS window of the underlying network according to the value of each parameter in the application layer QoS variable parameter and the QoS window length offset attribute included in the current use strategy resource; and obtaining the target QoS variable parameter according to the maximum value and the minimum value of the QoS window of the underlying network, the window length offset of the QoS window of the underlying network and a QoS rule mapping table included by the current used policy resource.

In the embodiment of the present invention, optionally, the parameter list of the second request message may include a destination address parameter, and the CSE creates a QoS variable parameter resource under a corresponding resource according to the destination address parameter; the second request message may include indication information indicating a target resource for creating the QoS variable parameter resource, and the intermediate node CSE creates the QoS variable parameter resource under the target resource indicated by the indication information, but the present invention is not limited thereto.

It should be understood that, in the embodiment of the present invention, the destination scope refers to a resource of the intermediate node corresponding to the entity in the source node that sends the third request message.

In the embodiment of the present invention, alternatively, as shown in fig. 3, a solid line rectangle in fig. 3 represents a resource, and a solid line rounded rectangle represents an attribute. N denotes this attribute/resource, at least 0, and at most n. The QoS variable parameter resource is located under a CSEBase resource of the intermediate node, the CSEBase resource includes attributes such as a CSE type (cseType) attribute, a CSE identification (CSE-ID) attribute, and a supported resource type (supportedResourceType) attribute, and the CSEBase resource includes a QoS variable parameter resource, a QoS policy resource, and a currently used policy resource (a dashed box in the drawing) in addition to resources such as a request (< request >) resource, a delivery (< delivery >) resource, and a schedule (< schedule >) resource. The QoS variable parameter resource comprises a data transmission average rate attribute, a data transmission delay jitter attribute, a packet loss rate attribute, a data transmission reliability attribute, a data transmission priority attribute and subscription resources, and is used for transmitting QoS variable parameters; the management link attribute of the current used policy resource is associated with the QoS policy resource through a pointer; the QoS policy resources include: QoS parameter restriction policy (QoSLimits) resources, QoS parameter default value setting policy (QoSDefParameters) resources, underlying network access policy (QoSNetworkaccessRules) resources and QoS rule mapping table policy (QoSRuleList) resources.

In the embodiment of the present invention, alternatively, as shown in fig. 4, a solid line rectangle in fig. 4 represents a resource, and a solid line rounded rectangle represents an attribute. N denotes this attribute/resource, at least 0, and at most n. The QoS variable parameter resource is located under an AE resource of the intermediate node, the AE resource includes attributes such as a name (name) attribute, an App identifier attribute, an AE identifier attribute, and an access point (pointotacess) attribute, and the AE resource includes resources such as a group (< group >) resource, an access control policy (< accesscontrol policy >) resource, a polling channel (< polling) resource, and a QoS variable parameter resource, a QoS policy resource, and the currently used policy resource (a dotted frame part in the figure). The QoS variable parameter resource comprises a data transmission average rate attribute, a data transmission delay jitter attribute, a packet loss rate attribute, a data transmission reliability attribute, a data transmission priority attribute and subscription resources, and is used for transmitting QoS variable parameters; the management link attribute of the current used policy resource is associated with the QoS policy resource through a pointer; the QoS policy resources include: QoS parameter restriction strategy resource, QoS parameter default value setting strategy resource, underlying network access strategy resource and QoS rule mapping table strategy resource.

In the embodiment of the present invention, alternatively, as shown in fig. 5, a solid line rectangle in fig. 5 represents a resource, and a solid line rounded rectangle represents an attribute. N denotes this attribute/resource, at least 0, and at most n. The QoS policy resource includes 1 name attribute and M management link attributes in addition to a management definition (mgmtDefinition) attribute, an object identification (object ids) attribute, an object address (object pages) attribute, a description (description) attribute, and a subscription (< description >) resource, where M is a natural number greater than or equal to 3;

In the embodiment of the present invention, optionally, the QoS parameter restriction policy resource may include at least one of the following attributes: the data transmission average rate limiting attribute, the data transmission delay jitter limiting attribute, the packet loss limiting attribute, the data transmission reliability limiting attribute and the data transmission priority limiting attribute. Wherein, each attribute limits the value range of the QoS variable parameter corresponding to the attribute. Besides, the QoS parameter restriction policy resource may further include a scope attribute, where the scope attribute identifies an applicable scope of its resource (such as a specific AE identifier, an Application (APP) identifier, or a local AE, etc.), and when the request message corresponds to the applicable scope, the current QoS parameter restriction policy is adopted. One QoS policy resource may include a plurality of QoS parameter restriction policy resources to correspond to different application scopes. The QoS parameter restriction policy resource may also include other attributes specified in the standard, which is not a limitation of the present invention.

In this embodiment of the present invention, optionally, the QoS parameter default setting policy resource may include at least one of a data transmission average rate default setting attribute, a data transmission delay jitter default setting attribute, a packet loss rate setting attribute, a data transmission reliability setting attribute, and a data transmission priority setting attribute. Wherein each attribute defines a default value of a QoS variable parameter corresponding to the attribute. In addition, the QoS parameter default value setting policy resource may further include a scope attribute, where the scope attribute identifies an application range of the resource itself (e.g., a specific AE identifier, an App identifier, or a local AE), and when the request message corresponds to the application range of the resource itself, and if a value of a QoS variable parameter in a QoS variable parameter list in the request message is empty or incomplete, the current default QoS parameter value is used for processing. One QoS policy resource may include a plurality of QoS parameter default setting policy resources to correspond to different application scopes. The QoS parameter default setting resource may also include other attributes specified in the standard, which is not limited by the present invention.

In the embodiment of the present invention, optionally, the underlying network access policy resource may include a target network (targetNetwork) attribute, a maximum attribute of a QoS window of the underlying network, a minimum attribute of the QoS window of the underlying network, and other condition attributes. The target network attribute is used for limiting the underlying network to which the underlying network access strategy resource is applicable, and when the information of the underlying network to which data is to be transmitted conforms to the target network attribute, the current underlying network access strategy is adopted. The maximum attribute of the QoS window and the minimum attribute of the QoS window of the underlying network represent the QoS capability of the underlying network by a mode of the QoS window, which is the premise of mapping the QoS variable parameters in the CSE to the QoS variable parameters in the NSE and belongs to the category of the mapping mechanism of the underlying network, and other condition attributes represent other possible strategies. The underlying network access policy resource may also include other attributes specified in the standard, which is not a limitation of the present invention.

In this embodiment of the present invention, optionally, the QoS rule mapping table policy resource may include a QoS window length offset attribute of the underlying network and at least one of the following attributes: the data transmission average speed value range attribute, the data transmission delay jitter value range attribute, the packet loss rate value range attribute, the data transmission reliability value range attribute and the data transmission priority value range attribute. Wherein, each attribute limits the value range of the QoS variable parameter corresponding to the attribute. And when the value range of the current QoS variable parameter is in the range of the current QoS variable parameter, adopting the window length offset of a QoS window of the underlying network in the strategy resource of the current QoS rule mapping table as the window length offset of the QoS window. An underlying network access policy resource may comprise a plurality of QoS rule mapping table policy resources to form a network-specific QoS mapping table. The QoS rules mapping table policy resource may also include other attributes specified in the standard, which is not limited by the present invention.

Therefore, according to the method for data transmission in a unified machine-to-machine system in the embodiment of the present invention, the application layer QoS variable parameter is mapped to the target QoS variable parameter that can be identified by the underlying network, and the target QoS variable parameter is sent to the NSE, so that the NSE can transmit data according to the target QoS variable parameter, and thus, the requirements of applications under different application scenarios on the QoS of the network under the oneM2M system can be met.

The embodiments of the present invention will be described in detail with reference to specific examples, which should be noted only to help those skilled in the art better understand the embodiments of the present invention, and not to limit the scope of the embodiments of the present invention.

Fig. 6 is a schematic flow chart of a method for data transmission with message granularity in a data transmission process in a unified machine-to-machine system according to an embodiment of the present invention.

As shown in fig. 6, in S201, the request message sent by the AE or CSE of the source node carries information and reaches the CSE of the intermediate node through the Mca or Mcc interface.

Optionally, in S201, the information carried by the request message includes data information, and may further include a QoS variable parameter and a QoS control parameter.

In S202, the CSE of the intermediate node detects whether the QoS control parameter in the request message is enabled, detects whether the request message includes a QoS variable parameter when the QoS control parameter is enabled, and performs a normal data transmission procedure if the request message does not include the QoS variable parameter; if the request message has the QoS variable parameter, the request message is authenticated, the underlying network mapping is carried out, the QoS variable parameter which can be identified by the underlying network is obtained, and the authentication result is returned to the source of the request message.

In S203, the CSE of the intermediate node sends the QoS variable parameter recognizable by the underlying network to the network service entity NSE of the intermediate node through the Mcn interface.

After S203, the NSE of the intermediate node encapsulates the data according to the QoS variable parameter recognizable by the underlying network, and then sends the data packet to a node in another unified machine-to-machine system.

It should be understood that, in various embodiments of the present invention, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

Fig. 7 is a schematic flow chart of a method for data transmission with AE or CSE granularity in a data transmission process in a unified machine-to-machine system according to an embodiment of the present invention.

As shown in fig. 7, in S301, the AE or CSE of the source node sends a first request message to the CSE of the intermediate node through the Mca or Mcc interface, where the operation type of the first request message is Create (Create), and the content of the request is to Create QoS variable parameter resources for the request.

In S302, the CSE of the intermediate node detects information in the parameter list of the first request message, and creates a QoS variable parameter resource under a corresponding resource (CSEBase or specified AE) according to a destination address parameter in the parameter list; the CSE of the intermediate node starts the QoS strategy, indicates that the subsequent requests under the granularity need to execute the QoS strategy, and feeds back the result of whether the QoS variable parameter resources are successfully created to the AE or CSE sending the first request message.

In S303, the AE or CSE of the source node sends a second request message carrying data information to the CSE of the intermediate node, and performs underlying network mapping on the application layer QoS variable parameters in the QoS variable parameter resources to obtain QoS variable parameters recognizable by the underlying network when it is determined that QoS variable parameter resources exist in the destination scope for transmitting the second request message. And feeding back the relevant authentication result of the variable parameter of the QoS of the application layer to the AE or CSE which sends the second request message.

Optionally, in S303, if the CSE of the intermediate node needs to forward the second request message, the CSE first performs a request operation of creating a corresponding QoS variable parameter resource to the adjacent CSE through the Mcc interface, and then forwards the second request message.

In S304, the CSE of the intermediate node sends the QoS variable parameter recognizable by the underlying network to the network service entity NSE of the intermediate node through the Mcn interface.

After S304, the NSE encapsulates the data according to the QoS variable parameter recognizable by the underlying network, and then sends a packet including the data to a node in another unified machine-to-machine system.

A method 400 for underlying network mapping in S202 and S303 will be described in detail below with reference to fig. 8, where as shown in fig. 8, the method 400 includes:

s401, determining a current use strategy;

specifically, the CSE of the intermediate node is conditioned on a series of QoS constraints, such as: the use range of the relevant strategy resource, the type of the underlying network and the like determine the current use strategy.

S402, determining the value of the parameter which is not assigned with the initial value in the QoS variable parameter;

specifically, the CSE of the intermediate node assigns the QoS variable parameters to which the initial values are not assigned, according to the QoS default attribute pointing to the QoS parameter default setting policy resource in the currently used policy resource including the currently used policy.

S403, judging whether the parameter values in the QoS variable parameters are reasonable or not;

specifically, the CSE of the intermediate node determines whether the value range of each parameter in the QoS variable parameter satisfies the requirement of the QoS parameter restriction attribute according to the QoS parameter restriction attribute pointing to the QoS parameter restriction policy resource in the currently used policy resource. If the value ranges of all the parameters in the QoS variable parameters meet the requirement of QoS parameter limiting attributes, performing the next operation; otherwise, the data transmission is denied. For example, the CSE of the intermediate node may drop the data packet and send indication information indicating authentication failure to the source node, and the source node may adjust the value ranges of various QoS variable parameters according to the indication information. The invention is not so limited.

S404, determining the maximum value and the minimum value of the QoS window;

specifically, the CSE of the intermediate node determines the maximum value and the minimum value of the QoS window of the underlying network according to the QoS window length attribute pointing to the QoS underlying network access policy resource included in the currently used policy resource.

S405, determining the window length offset of the QoS window;

specifically, the CSE of the intermediate node determines the window length offset of the QoS window of the underlying network according to the value of each parameter in the QoS variable parameter and the QoS window length offset attribute pointing to the QoS rule mapping table policy resource included in the currently used policy resource.

And S406, obtaining the recognizable QoS variable parameter of the underlying network.

Specifically, the CSE of the intermediate node obtains a QoS variable parameter recognizable by the underlying network according to the maximum value and the minimum value of the QoS window of the underlying network, the window length offset of the QoS window of the underlying network, and the QoS rule mapping table included in the currently used policy resource.

The method 500 for mapping an underlying network based on a QoS window according to an embodiment of the present invention will be described below with reference to fig. 9, where the underlying network is a 3GPP network. It should be understood that the embodiments of the present invention are not limited to 3GPP networks, and may also include bluetooth, WiFi, and the like.

As shown in fig. 9, in S501, it is determined that the QoS control parameter is enabled, and the parameter in the QoS variable parameter has a reasonable value.

Specifically, the CSE of the intermediate node determines that the QoS control parameter in the request is enabled, and the QoS variable parameter in the request satisfies the requirement of the QoS parameter restriction attribute.

In S502, it is determined that the underlying network is a 3GPP network.

Specifically, the CSE of the intermediate node determines that the currently accessed underlying network is the 3GPP network according to the message content of the request.

In S503, the maximum and minimum values of the QoS window and the window length offset of the QoS window are determined.

Specifically, the CSE of the intermediate node finds a policy corresponding to the 3GPP network from the QoS policy resources, and obtains a maximum value and a minimum value of the QoS window, for example, the maximum value is 3 and the minimum value is 0 in table 1. And combining the requirement of the parameters set in the QoS variable parameters and the QoS window length offset attribute in the current use strategy resource to obtain the window length offset of the QoS window at the CSE side in the 3GPP network.

In S504, the QoS variable parameter recognizable by the 3GPP network is mapped.

Specifically, the CSE of the intermediate node queries the QoS rule mapping table in the currently used policy resource according to three parameters, i.e., the maximum value of the QoS window, the minimum value of the QoS window, and the window length offset of the QoS window, so as to obtain QoS variable parameters recognizable by the 3GPP network, such as the call class in the 3GPP service type corresponding to 0, 3, and 0 in table 1. And finally, sending the QoS variable parameter which can be identified by the 3GPP network to the NSE of the intermediate node.

TABLE 1

The flow of end-to-end data transmission based on message granularity according to the embodiment of the present invention will be described in detail below with reference to fig. 10.

As shown in fig. 10, in S601, the AE of the source node sends a request message request with a QoS variable parameter to the CSE of the source node.

In S602, the CSE of the source node makes a decision on the QoS variable parameter, maps the QoS variable parameter to a QoS variable parameter recognizable by the underlying network by using an underlying network mapping method based on a QoS window, and sends the request to the underlying network for continuous transmission.

In S603, the underlying network transmits the request by using a QoS transmission mechanism in the prior art.

In S604, after the intermediate non-forwarding node receives the QoS packet, it first extracts the QoS requirement of the CSE layer in the packet, and after setting a reasonable QoS window by using the QoS policy of the same underlying network, moves the packet to the underlying network for continuous transmission.

In S605, the underlying network transmits the data packet by using a QoS transmission mechanism in the prior art.

In S606, after receiving the data packet, the intermediate network transfer node extracts the QoS requirement of the CSE of the intermediate non-network transfer node included in the data packet, and then performs a relevant decision to set a QoS variable parameter leading to the next node request.

In S607, the intermediate network transfer node receives the data packet, sets a reasonable QoS window by using the QoS policy of the egress underlying network, and then moves the data packet to the relevant underlying network for further transmission.

In S608, the underlying network transmits the data packet by using a QoS transmission mechanism in the prior art.

In S609, the NSE of the destination node unpacks the packet sent from the underlying network and delivers the unpacked packet to the CSE of the destination node for processing.

In S610, the CSE of the destination node extracts the content in the received data packet, authenticates the content, and sends the content to the AE process of the destination node. The extracted content of the CSE of the destination node comprises the type of the request and the content of the request.

Fig. 11 is a schematic diagram of a data transmission flow in a vehicle collision scenario according to an embodiment of the present invention. As shown in fig. 11, in S701, the AE of the source node sends the information of the vehicle collision to the local CSE via a request, which carries the QoS variable parameter.

In S702, the CSE of the source node makes a decision on the QoS variable parameter, and maps the QoS variable parameter to a 3GPP service by using a QoS window-based underlying network mapping method of the CSE of the source node to the 3GPP network, and moves the request to an underlying network for continuous transmission.

In S703, the underlying network transmits the request using the existing QoS securing mechanism of the 3GPP network.

In S704, the oneM2M gateway node receives the data packet from the 3GPP network, finds that the node is not the destination node, and extracts the QoS variable parameter information in the request to wait for the CSE of the gateway node to make a decision.

In S705, the CSE of the gateway node discovers that the egress underlying network is an IP network according to the routing information, sets a reasonable QoS window by using a QoS policy of the IP network, maps the QoS window to a DSCP parameter of the IP network, and then moves the request to the underlying network for continuous transmission.

In S706, the underlying network transmits the request using the existing QoS transport mechanism of the IP network.

In S707, the intelligent transportation system ITS node receives the data packet from the oneM2M gateway, unpacks the data packet, and then sends the request information to the CSE of the ITS for processing.

In S708, the CSE of the ITS finds that the destination node has been reached, extracts the vehicle collision information in the received request, authenticates the vehicle collision information, and sends the vehicle collision information to the collision acquisition application for processing.

The method for data transmission in the unified machine-to-machine system according to the embodiment of the present invention is described in detail above with reference to fig. 2 to 11, and the common service entity according to the embodiment of the present invention is described in detail below with reference to fig. 12 to 13.

Fig. 12 shows a schematic block diagram of a common service entity CSE 10 provided by an embodiment of the present invention. As shown in fig. 12, the CSE 10 includes:

an obtaining module 11, configured to obtain an application layer quality of service QoS variable parameter, where the application layer QoS variable parameter is used to indicate a quality requirement of an application on transmission data;

a processing module 12, configured to map the application layer QoS variable parameter acquired by the acquiring module 11 into a target QoS variable parameter recognizable by the underlying network;

a sending module 13, configured to send the target QoS variable parameter to a network service entity NSE, so that the NSE transmits data according to the target QoS variable parameter.

Specifically, the CSE of the intermediate node acquires an application layer QoS variable parameter indicating a quality requirement of an application on transmission data, maps the application layer QoS variable parameter to a target QoS variable parameter recognizable by the underlying network, and then sends the target QoS variable parameter to the network service entity NSE so that the NSE transmits the data according to the target QoS variable parameter.

Therefore, the public service entity of the embodiment of the present invention obtains an application layer QoS variable parameter for indicating a quality requirement of an application on transmission data, maps the application layer QoS variable parameter to a target QoS variable parameter recognizable by an underlying network, and then sends the target QoS variable parameter to an NSE, so that the NSE can transmit data according to the target QoS variable parameter, thereby being capable of meeting a requirement of the application on QoS of a network under different application scenarios under an oneM2M system.

It should be understood that, in the embodiment of the present invention, the application layer QoS variable parameter may refer to a QoS variable parameter sent by the application entity AE or CSE of the source node, or may refer to a QoS variable parameter included in a QoS variable parameter resource requested to be established by a request message sent by the AE or CSE of the source node.

In this embodiment of the present invention, optionally, as shown in fig. 13, the common service entity 10 further includes: a first receiving module 14, configured to receive a first request message sent by the AE or CSE of the source node, where the first request message includes the application layer QoS variable parameter. Accordingly, the obtaining module 11 obtains the application layer QoS variable parameter included in the first request message received by the first receiving module 14.

Accordingly, when determining that the QoS control parameter included in the first request message is enabled, the processing module 12 determines the maximum value and the minimum value of the QoS window of the network layer and the window length offset of the QoS window of the underlying network, where the QoS window is used to represent an interval of a comprehensive indicator of QoS of the underlying network; and obtaining the target QoS variable parameter according to the maximum value and the minimum value of the QoS window of the underlying network, the window length offset of the QoS window of the underlying network and a QoS rule mapping table included in the current use strategy resource. Wherein, the comprehensive index of the QoS in the 3GPP system refers to the service type of the 3GPP system, which comprises: call type, streaming media, interactive class and background class, refer to differentiated services codepoints in IP networks.

In this embodiment of the present invention, optionally, as shown in fig. 13, the common service entity 10 further includes:

a second receiving module 15, configured to receive a second request message sent by the AE or the CSE, where the second request message is used to request that a QoS variable parameter resource is created under a target resource;

a creating module 16 for creating the QoS variant parameter resource including the application layer QoS variant parameter under the target resource;

correspondingly, the obtaining module 11 is specifically configured to: the application layer QoS variable parameters included in the QoS variable parameter resources created by the creation module 16 are acquired.

In this embodiment of the present invention, optionally, the second receiving module 15 is further specifically configured to: receiving a third request message including data information sent by the AE or the CSE; correspondingly, when determining that the destination scope for transmitting the third request message includes the QoS variable parameter resource, the processing module 12 determines the maximum value and the minimum value of the QoS window of the underlying network and the window length offset of the QoS window of the underlying network, where the QoS window is used to indicate an interval of a QoS comprehensive indicator; and the CSE of the intermediate node obtains the target QoS variable parameter according to the maximum value and the minimum value of the QoS window of the underlying network, the window length offset of the QoS window of the underlying network and a QoS rule mapping table included in the current use strategy resource. Wherein, the comprehensive index of the QoS in the 3GPP system refers to the service type of the 3GPP system, which comprises: call type, streaming media, interactive class and background class, refer to differentiated services codepoints in IP networks.

In the embodiment of the present invention, optionally, the target resource is a CSEBase resource of an intermediate node or an AE resource of the intermediate node.

In this embodiment of the present invention, optionally, the processing module 12 is specifically configured to: determining the value of the parameter which is not assigned with the initial value in the QoS variable parameter of the application layer according to the QoS variable default value attribute included in the current used strategy resource; when the value of each parameter in the application layer QoS variable parameter meets the requirement of the QoS parameter limit attribute included by the current use strategy resource, determining the maximum value and the minimum value of the QoS window of the underlying network according to the QoS window length attribute included by the current use strategy resource; and determining the window length offset of the QoS window of the underlying network according to the value of each parameter in the application layer QoS variable parameters and the QoS window length offset attribute included in the current use strategy resource.

In the embodiment of the present invention, alternatively, as shown in fig. 3, a solid line rectangle in fig. 3 represents a resource, and a solid line rounded rectangle represents an attribute. N denotes this attribute/resource, at least 0, and at most n. The QoS variable parameter resource is located under a CSEBase resource of the intermediate node, where the CSEBase resource includes attributes such as a CSE type (cseType) attribute, a CSE identification (CSE-ID) attribute, and a supported resource type (supportedResourceType) attribute, and includes a QoS variable parameter resource, a QoS policy resource, and a currently used policy resource (a dashed box in the drawing) in addition to resources such as a request (< request >) resource, a delivery (< delivery >) resource, and a schedule (< schedule >) resource. The QoS variable parameter resource comprises a data transmission average rate attribute, a data transmission delay jitter attribute, a packet loss rate attribute, a data transmission reliability attribute, a data transmission priority attribute and subscription resources, and is used for transmitting QoS variable parameters; the management link attribute of the current use policy resource is associated with the QoS policy resource; the QoS policy resources include: QoS parameter restriction policy (QoSLimits) resources, QoS parameter default value setting policy (QoSDefParameters) resources, underlying network access policy (QoSNetworkaccessRules) resources and QoS rule mapping table policy (QoSRuleList) resources.

In the embodiment of the present invention, alternatively, as shown in fig. 4, a solid line rectangle in fig. 4 represents a resource, and a solid line rounded rectangle represents an attribute. N denotes this attribute/resource, at least 0, and at most n. The QoS resource is located under an AE resource of the intermediate node, and the AE resource includes attributes such as a name (name) attribute, an App Identifier (ID) attribute, an AE Identifier (ID) attribute, and an access point (point0fa ccess) attribute, and includes a QoS variable parameter resource, a QoS policy resource, and a currently used policy resource (a dashed frame portion in the drawing) in addition to resources such as a group (< group >) resource, an access control policy (< accesscontrol policy >) resource, and a polling channel (< polling channel >) resource. The QoS variable parameter resource comprises a data transmission average rate attribute, a data transmission delay jitter attribute, a packet loss rate attribute, a data transmission reliability attribute, a data transmission priority attribute and a subscription resource, is used for transmitting a QoS variable parameter, is a sub-attribute under a < delivery > resource, and is used for setting the QoS variable parameter of a request message in the next hop; the management link attribute of the current use policy resource is associated with the QoS policy resource; the QoS policy resources include: QoS parameter restriction strategy resource, QoS parameter default value setting strategy resource, underlying network access strategy resource and QoS rule mapping table strategy resource.

In the embodiment of the present invention, optionally, the QoS parameter restriction policy resource includes at least one of the following attributes: the data transmission average rate limiting attribute, the data transmission delay jitter limiting attribute, the packet loss limiting attribute, the data transmission reliability limiting attribute and the data transmission priority limiting attribute. Wherein, each attribute limits the value range of the QoS variable parameter corresponding to the attribute. In addition, the QoS parameter restriction policy resource further includes a scope attribute identifying the applicable scope of the resource itself (e.g., specific AE identifier, App-ID or local AE, etc.), and when the request message corresponds to the applicable scope, the current QoS parameter restriction policy is applied. Therefore, under one QoS policy resource, there may be multiple QoS parameters to limit the policy resource to correspond to different application scopes.

In the embodiment of the present invention, optionally, the QoS parameter default setting policy resource includes at least one of a data transmission average rate default setting attribute, a data transmission delay jitter default setting attribute, a packet loss rate setting attribute, a data transmission reliability setting attribute, and a data transmission priority setting attribute. Wherein each attribute defines a default value for the QoS variable parameter corresponding to the attribute. In addition, the QoS parameter default setting policy resource further includes a scope attribute identifying an application scope of the resource itself (e.g., a specific AE identifier, App-identifier, or local AE, etc.), and when the request message corresponds to the application scope, if the QoS variable parameter list in the request message is empty or incomplete, the current default QoS parameter value is used for processing. Therefore, under one QoS strategy resource, a plurality of QoS parameter default values can set the strategy resource to correspond to different application ranges.

In the embodiment of the present invention, optionally, the underlying network access policy resource includes a target network attribute, a maximum value attribute of a QoS window of the underlying network, a minimum value attribute of the QoS window of the underlying network, and other condition attributes. The target network attribute is used for limiting the bottom layer network applicable to the network access strategy resource, and when the bottom layer network information of the data to be transmitted conforms to the target network attribute, the current bottom layer network access strategy is adopted. The maximum attribute of the QoS window and the minimum attribute of the QoS window of the underlying network represent the premise that the QoS capability of the underlying network is mapping from the QoS in the CSE to the QoS variable parameter in the NSE by using a mode of the QoS window, and belong to the category of an underlying network mapping mechanism, and other condition attributes represent other possible strategies.

In the embodiment of the present invention, optionally, the QoS rule mapping table policy resource includes a QoS window length offset attribute of the underlying network and at least one of the following attributes: the data transmission average speed value range attribute, the data transmission delay jitter value range attribute, the packet loss rate value range attribute, the data transmission reliability value range attribute and the data transmission priority value range attribute. Wherein each attribute defines a value range of a QoS variable parameter corresponding to the attribute. And when the current QoS variable parameter falls into the current QoS variable parameter range, adopting the window length offset of the QoS window of the underlying network in the current QoS rule mapping table strategy resource as the window length offset of the QoS window. There may be multiple QoS rule mapping table policy resources under one underlying network access policy resource to form a QoS mapping table for a particular network.

It should be understood that the above and other operations and/or functions of the modules in the common service entity 10 according to the embodiment of the present invention are respectively for implementing the corresponding flows of the method 100 in fig. 2, and are not described herein again for brevity.

Therefore, the public service entity in the embodiment of the present invention maps the application layer QoS variable parameter to a target QoS variable parameter recognizable by the underlying network, and sends the target QoS variable parameter to the NSE, so that the NSE can transmit data according to the target QoS variable parameter, thereby meeting the QoS requirements of applications in different application scenarios on the network under the oneM2M system.

As shown in fig. 14, the embodiment of the present invention further provides a common service entity 20, where the common service entity 20 includes a processor 21, a memory 22, a bus system 23, a receiver 24 and a transmitter 25. Wherein, the processor 21, the memory 22, the receiver 24 and the transmitter 25 are connected by a bus system 23, the memory 22 is used for storing instructions, the processor 21 is used for executing the instructions stored in the memory 22 to control the receiver 24 to receive signals and control the transmitter 25 to transmit signals; wherein, the receiver 24 is configured to obtain an application layer QoS variable parameter, which is used to indicate the quality requirement of the application for the transmission data; the processor 21 is configured to map the application layer QoS variable parameter received by the receiver 24 to a target QoS variable parameter recognizable by an underlying network; the transmitter 25 is configured to transmit the target QoS variable parameter to a network service entity NSE so that the NSE transmits data according to the target QoS variable parameter.

It should be understood that, in the embodiment of the present invention, the processor 21 may be a Central Processing Unit (CPU), and the processor 21 may also be other general processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 22 may include a read-only memory and a random access memory, and provides instructions and data to the processor 61. A portion of memory 22 may also include non-volatile random access memory. For example, the memory 22 may also store device type information.

The bus system 23 may include a power bus, a control bus, a status signal bus, and the like, in addition to the data bus. But for clarity of illustration the various buses are labeled in the figure as bus system 23.

In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 21. The steps of a method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in the processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 22, and the processor 21 reads the information in the memory 22 and completes the steps of the method in combination with the hardware. To avoid repetition, it is not described in detail here.

Optionally, as an embodiment, the processor 21 is specifically configured to: determining the maximum value and the minimum value of a QoS window of the underlying network and the window length offset of the QoS window of the underlying network, wherein the QoS window is used for expressing the interval of the comprehensive indexes of the QoS of the underlying network; and obtaining the target QoS variable parameter according to the maximum value and the minimum value of the QoS window of the underlying network, the window length offset of the QoS window of the underlying network and a QoS rule mapping table included by the current use strategy resource.

Optionally, as an embodiment, the processor 21 is further specifically configured to: determining the value of the parameter which is not assigned with the initial value in the QoS variable parameter of the application layer according to the QoS variable default value attribute included in the current used strategy resource; when the value of each parameter in the application layer QoS variable parameter meets the requirement of the QoS parameter limit attribute included by the current use strategy resource, determining the maximum value and the minimum value of the QoS window of the underlying network according to the QoS window length attribute included by the current use strategy resource; and determining the window length offset of the QoS window of the underlying network according to the value of each parameter in the application layer QoS variable parameters and the QoS window length offset attribute included in the current use strategy resource.

Optionally, as an embodiment, the receiver 24 is specifically configured to: receiving a first request message sent by an application entity AE or a common service entity CSE, wherein the first request message comprises the variable parameter of the QoS of the application layer; and acquiring the application layer QoS variable parameter included in the first request message.

Optionally, as an embodiment, the processor 21 is specifically configured to: upon determining that the QoS control parameters included in the first request message received by the receiver 24 are enabled, the maximum and minimum values of the QoS window of the underlying network and the window length offset of the QoS window of the underlying network are determined.

Optionally, as an embodiment, the receiver 24 is further specifically configured to: receiving a second request message sent by AE or CSE, wherein the second request message is used for requesting to create QoS variable parameter resources under target resources; creating the QoS variant parameter resource including the application layer QoS variant parameter under the target resource; the processor 21 is specifically configured to: and acquiring the application layer QoS variable parameter included in the QoS variable parameter resource.

Optionally, as an embodiment, the receiver 24 is further specifically configured to: receiving a third request message including data information sent by the AE or the CSE;

accordingly, the processor 21 is specifically configured to: and when the destination scope for transmitting the third request message is determined to comprise the QoS variable parameter resource, determining the maximum value and the minimum value of the QoS window of the underlying network and the window length offset of the QoS window of the underlying network.

Optionally, as an embodiment, the target resource is a CSEBase resource or an AE resource.

Optionally, as an embodiment, the CSEBase resource or the AE resource further includes: QoS policy resources and current usage policy resources; wherein the management link attribute of the currently used policy resource is associated with the QoS policy resource, and the QoS policy resource includes: QoS parameter restriction strategy resource, QoS parameter default value setting strategy resource, underlying network access strategy resource and QoS rule mapping table strategy resource.

Optionally, as an embodiment, the QoS policy resource further includes 1 name attribute and M management link attributes, where M is a natural number greater than or equal to 3;

Optionally, as an embodiment, the QoS parameter restriction policy resource includes at least one of the following attributes: the data transmission average rate limiting attribute, the data transmission delay jitter limiting attribute, the packet loss limiting attribute, the data transmission reliability limiting attribute and the data transmission priority limiting attribute.

Optionally, as an embodiment, the QoS parameter default setting policy resource includes at least one of the following attributes: the data transmission method comprises the following steps of setting an attribute for a data transmission average speed default value, a setting attribute for a data transmission delay jitter default value, a setting attribute for a packet loss rate, a setting attribute for data transmission reliability and a setting attribute for data transmission priority.

Optionally, as an embodiment, the underlying network access policy resource includes a target network attribute, a maximum value attribute of a QoS window of the underlying network, a minimum value attribute of the QoS window of the underlying network, and other condition attributes.

Optionally, as an embodiment, the QoS rule mapping table policy resource includes a QoS window length offset attribute of the underlying network and at least one of the following attributes: the data transmission average speed value range attribute, the data transmission delay jitter value range attribute, the packet loss rate value range attribute, the data transmission reliability value range attribute and the data transmission priority value range attribute.

Optionally, as an embodiment, the application layer QoS variable parameter includes at least one of the following parameters: the data transmission system comprises a data transmission average speed parameter, a data transmission delay jitter parameter, a packet loss rate parameter, a data transmission reliability parameter and a data transmission priority parameter.

It should be understood that the common service entity 20 according to the embodiment of the present invention may correspond to the common service entity 10 provided in the embodiment of the present invention, and the above and other operations and/or functions of the modules in the common service entity 20 are respectively for implementing the corresponding flows of the method 100 in fig. 1, and are not described herein again for brevity.

Additionally, the terms "system" and "network" are often used interchangeably herein. The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

It should be understood that in the present embodiment, "B corresponding to a" means that B is associated with a, from which B can be determined. It should also be understood that determining B from a does not mean determining B from a alone, but may be determined from a and/or other information.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of illustrating clearly the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may also be an electric, mechanical or other form of connection.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment of the present invention.

In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention essentially or partially contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

While the invention has been described with reference to specific embodiments, the invention is not limited thereto, and various equivalent modifications and substitutions can be easily made by those skilled in the art within the technical scope of the invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A method for unifying data transmission in a machine-to-machine system, comprising:

acquiring an application layer QoS variable parameter, wherein the application layer QoS variable parameter is used for representing the quality requirement of an application on transmission data, and is a QoS variable parameter carried in a request message sent by an application entity AE or a common service entity CSE, or is a QoS variable parameter included in a QoS variable parameter resource which is sent by the AE or the CSE and is requested to be established;

mapping the application layer QoS variable parameter into a target QoS variable parameter which can be identified by the underlying network;

and sending the target QoS variable parameter to a Network Service Entity (NSE) so that the NSE can transmit data according to the target QoS variable parameter.

2. The method of claim 1, wherein mapping the application layer QoS variable parameter to a target QoS variable parameter recognizable by an underlying network comprises:

determining the maximum value and the minimum value of a QoS window of the underlying network and the window length offset of the QoS window of the underlying network, wherein the QoS window is used for representing the interval of the comprehensive index of the QoS of the underlying network;

and obtaining the target QoS variable parameter according to the maximum value and the minimum value of the QoS window of the underlying network, the window length offset of the QoS window of the underlying network and a QoS rule mapping table included by the current use strategy resource.

3. The method of claim 2, wherein determining the maximum and minimum values of the QoS window of the underlay network and the window length offset of the QoS window of the underlay network comprises:

determining the value of the parameter which is not assigned with the initial value in the QoS variable parameter of the application layer according to the QoS variable default value attribute included in the current use strategy resource;

when the value of each parameter in the application layer QoS variable parameters meets the requirement of the QoS parameter limit attribute included in the current use strategy resource, determining the maximum value and the minimum value of the QoS window of the underlying network according to the QoS window length attribute included in the current use strategy resource;

and determining the window length offset of the QoS window of the underlying network according to the value of each parameter in the application layer QoS variable parameters and the QoS window length offset attribute included in the current use strategy resource.

4. The method according to claim 2 or 3, wherein the obtaining of the application layer quality of service (QoS) variable parameter comprises:

receiving a first request message sent by an application entity AE or a common service entity CSE, wherein the first request message comprises the application layer QoS variable parameter;

and acquiring the application layer QoS variable parameter included in the first request message.

5. The method of claim 4, wherein determining the maximum and minimum values of the QoS window of the underlay network and the window length offset of the QoS window of the underlay network comprises:

determining a maximum value and a minimum value of a QoS window of the underlying network and a window length offset of the QoS window of the underlying network when it is determined that the QoS control parameter included in the first request message is enabled.

6. The method of claim 2, wherein the obtaining of the application layer quality of service (QoS) variable parameter comprises:

receiving a second request message sent by AE or CSE, wherein the second request message is used for requesting to create QoS variable parameter resources under target resources;

creating the QoS variable parameter resource comprising the application layer QoS variable parameter under the target resource;

and acquiring the application layer QoS variable parameters included in the QoS variable parameter resources.

7. The method of claim 6, wherein determining the maximum and minimum values of the QoS window of the underlay network and the window length offset of the QoS window of the underlay network comprises:

receiving a third request message including data information sent by the AE or the CSE;

and when determining that the destination scope for transmitting the third request message comprises the QoS variable parameter resource, determining the maximum value and the minimum value of a QoS window of the underlying network and the window length offset of the QoS window of the underlying network.

8. The method according to claim 6 or 7, wherein the target resource is a common service entity base CSEBase resource or an AE resource.

9. The method of claim 8, wherein the CSEBase resource or the AE resource further comprises: QoS policy resources and said current usage policy resources;

wherein the administrative Link Attribute of the currently used policy resource is associated with the QoS policy resource, which comprises: QoS parameter restriction strategy resource, QoS parameter default value setting strategy resource, underlying network access strategy resource and QoS rule mapping table strategy resource.

10. The method of claim 9, wherein the QoS policy resources further comprise 1 name attribute and M management link attributes, M being a natural number greater than or equal to 3;

wherein the name attribute is used to represent a name of a QoS policy included in the QoS policy resource, at least one of the M management link attributes is associated with the QoS parameter limit policy resource, at least one of the M management link attributes is associated with the QoS parameter default set policy resource, and at least one of the M management link attributes is associated with the underlying network access policy resource.

11. The method of claim 9, wherein the QoS parameter restriction policy resource comprises at least one of the following attributes: the data transmission average rate limiting attribute, the data transmission delay jitter limiting attribute, the packet loss limiting attribute, the data transmission reliability limiting attribute and the data transmission priority limiting attribute.

12. The method of claim 9, wherein the QoS parameter default setting policy resource comprises at least one of the following attributes: the data transmission method comprises the following steps of setting an attribute for a data transmission average speed default value, a setting attribute for a data transmission delay jitter default value, a setting attribute for a packet loss rate, a setting attribute for data transmission reliability and a setting attribute for data transmission priority.

13. The method of claim 9, wherein the underlay network access policy resources comprise target network attributes, maximum attributes of QoS windows of the underlay network, minimum attributes of QoS windows of the underlay network, and other conditional attributes.

14. The method of claim 9, wherein the QoS rules mapping table policy resources comprise a QoS window length offset attribute for an underlying network and at least one of the following attributes: the data transmission average speed value range attribute, the data transmission delay jitter value range attribute, the packet loss rate value range attribute, the data transmission reliability value range attribute and the data transmission priority value range attribute.

15. The method according to any of claims 1-3, 5-7, wherein the application layer QoS variable parameter comprises at least one of the following parameters: the data transmission system comprises a data transmission average speed parameter, a data transmission delay jitter parameter, a packet loss rate parameter, a data transmission reliability parameter and a data transmission priority parameter.

16. A public service entity, comprising:

an obtaining module, configured to obtain a QoS variable parameter of application layer quality of service (QoS), where the QoS variable parameter is used to indicate a quality requirement of an application on transmission data, and the QoS variable parameter of the application layer is a QoS variable parameter carried in a request message sent by an application entity AE or a common service entity CSE, or the QoS variable parameter of the application layer is a QoS variable parameter included in a QoS variable parameter resource sent by the AE or the CSE and requested to be established;

the processing module is used for mapping the application layer QoS variable parameters acquired by the acquisition module into target QoS variable parameters which can be identified by the underlying network;

a sending module, configured to send the target QoS variable parameter to a network service entity NSE, so that the NSE transmits data according to the target QoS variable parameter.

17. The common service entity of claim 16, wherein the processing module is specifically configured to:

18. The common service entity of claim 17, wherein the processing module is further specifically configured to:

19. The common service entity as claimed in claim 17 or 18, wherein the common service entity further comprises:

a first receiving module, configured to receive a first request message sent by an application entity AE or a common service entity CSE, where the first request message includes the application layer QoS variable parameter;

wherein the obtaining module is specifically configured to:

and acquiring the application layer QoS variable parameter included in the first request message received by the first receiving module.

20. The common service entity of claim 19, wherein the processing module is specifically configured to:

determining a maximum value and a minimum value of a QoS window of the underlying network and a window length offset of the QoS window of the underlying network when it is determined that the QoS control parameter included in the first request message received by the first receiving module is enabled.

21. The common service entity as claimed in claim 17, wherein the common service entity further comprises:

a second receiving module, configured to receive a second request message sent by the AE or the CSE, where the second request message is used to request that a QoS variable parameter resource be created under a target resource;

a creation module for creating the QoS variable parameter resource including the application layer QoS variable parameter under the target resource;

wherein the obtaining module is specifically configured to:

and acquiring the application layer QoS variable parameters included in the QoS variable parameter resources created by the creation module.

22. The common service entity of claim 21, wherein the second receiving module is further specifically configured to: receiving a third request message including data information sent by the AE or the CSE;

wherein the processing module is specifically configured to:

23. The common service entity of claim 21 or 22, wherein the target resource is a common service entity underlying CSEBase resource or AE resource.

24. The common service entity of claim 23, wherein the CSEBase resource or the AE resource further comprises: QoS policy resources and current usage policy resources;

25. The common service entity as in claim 24, wherein the QoS policy resources further comprise 1 name attribute and M management link attributes, M being a natural number greater than or equal to 3;

26. The common service entity as claimed in claim 24, wherein the QoS parameter restriction policy resource comprises at least one of the following attributes: the data transmission average rate limiting attribute, the data transmission delay jitter limiting attribute, the packet loss limiting attribute, the data transmission reliability limiting attribute and the data transmission priority limiting attribute.

27. The common service entity as claimed in claim 24, wherein the QoS parameter default setting policy resource comprises at least one of the following attributes: the data transmission method comprises the following steps of setting an attribute for a data transmission average speed default value, a setting attribute for a data transmission delay jitter default value, a setting attribute for a packet loss rate, a setting attribute for data transmission reliability and a setting attribute for data transmission priority.

28. The common service entity of claim 24, wherein the underlay network access policy resources comprise target network attributes, a maximum attribute for a QoS window of the underlay network, a minimum attribute for a QoS window of the underlay network, and other conditional attributes.

29. The common service entity of claim 24, wherein the QoS rules mapping table policy resources comprise a QoS window length offset attribute of an underlying network and at least one of the following attributes: the data transmission average speed value range attribute, the data transmission delay jitter value range attribute, the packet loss rate value range attribute, the data transmission reliability value range attribute and the data transmission priority value range attribute.

30. The common service entity according to any of claims 16-18, 20-22, wherein the application layer QoS variable parameter comprises at least one of the following parameters: the data transmission system comprises a data transmission average speed parameter, a data transmission delay jitter parameter, a packet loss rate parameter, a data transmission reliability parameter and a data transmission priority parameter.