CN102316086A - Relay method for service data and relay node system - Google Patents

Abstract

The invention discloses a business data relay method and a relay node system. Wherein, the relay node system includes: a relay control entity, configured to receive a relay request, select a relay bearer entity for the relay task requested by the relay request, and request the relay bearer entity to perform the relay task, And obtain the service quality measurement information from the service quality measurement entity; the relay carrying entity is used to perform the above relay task, and transfer the business data related to the relay task; the service quality measurement entity is used to perform the service quality measurement task, and the The obtained QoS measurement information is reported to the relay control entity. Through the present invention, each functional entity in the relay node can be partly flexibly.

Description

Service data relay method and relay node system

technical field

The present invention relates to the communication field, in particular to a service data relay method and a relay node system.

Background technique

At present, when the communicating parties are located behind a Network Address Translation (NAT) device or a firewall device, since the communicating parties cannot directly establish a connection, it is necessary to use relay technology to realize the NAT/firewall traversal function to help the communicating parties Establish a direct connection. In addition, since the packet data network uses the best effort method to transmit data packets, its service quality is difficult to meet the requirements of multimedia services. Therefore, it is necessary to apply relay technology in the packet data network and try multiple transmission paths to improve the network service quality.

Wherein, the relay technology refers to a technology in which one or more relay nodes are added to the transmission path of the packet data packet, and the relay node forwards the data packet. Compared with the traditional IP routing technology, through the relay technology: (1) NAT/firewall traversal function can be realized, and data transfer function can be provided when the communication parties cannot directly establish a connection; (2) IPv4/IPv6 protocol conversion function can be provided , when the communication parties use different IP protocols, the protocol conversion and data transfer functions are performed; (3) The data transmission path can be changed. When the default path cannot meet the service quality requirements, it can be improved by adding relays and changing the data transmission path. service quality. Among them, the quality of service includes: transmission delay, packet loss rate, transmission bandwidth and delay jitter, etc.; (3) Multiple optional transmission paths can be provided. When the default path is unreliable and the transmission fails, the transmission can be switched quickly path to ensure business continuity.

In the prior art, the control and bearer functions of the relay node are implemented in the same logical entity. Specifically, each relay node not only implements the bearer function of data packet forwarding, but also needs to complete relay control functions such as information management of the relay node, collection and maintenance of service quality information, relay selection algorithm, and external interface. Fig. 1 describes an existing relay node management manner. Among them, the guidance server 101 is responsible for guidance when the relay node joins the group; the ordinary relay nodes 103, 104 and the group proxy node 102 are homogeneous relay nodes. The group proxy node 102 is elected from ordinary relay nodes, and is used to complete control functions such as relay node registration, service quality measurement, and network topology information maintenance. At the same time, common relay nodes 103 and 104 also implement some control functions such as relay node selection and external interface. Moreover, all nodes in the relay group (including the group proxy node 102) need to realize the bearer function of media data forwarding.

In the relay node management method shown in Figure 1, each relay node needs to implement control and bearer functions at the same time, so there are the following defects:

(1) Node functions are relatively complex, and node implementation and maintenance are difficult. In the existing implementation of the relay node, the relay node needs to complete all the relay-related control and bearer functions, which brings difficulties to the node implementation. Furthermore, in the relay node, the data bearing function is relatively simple and has nothing to do with services. On the other hand, the relay control function is more complicated and needs to be upgraded simultaneously with service evolution. If all relay nodes complete the control and bearer functions at the same time, the hardware and software implementation requirements for relay node terminals are very high, and a large number of nodes need to be upgraded during service evolution. In the actual network, the capabilities of peer nodes may be different. For example, desktop computers with strong software and hardware functions are more suitable for completing control functions, while ordinary mobile terminals can only complete data carrying functions.

(2) It is difficult to select the control node. Since the relay nodes under the same group need to provide similar relay service performance, the nodes under the same group in Figure 1 must be in the same physical network or network segment. In this way, when there are no nodes with strong processing capabilities in some physical networks or network segments, it is impossible to select a suitable group proxy node to complete complex control and management functions. For example, in a group in a wireless cellular network, relay nodes may all be handheld mobile devices, and these devices cannot perform complex control functions. In this case, the relay nodes outside the cellular network cannot accurately measure the network conditions in the cellular network. Therefore, relay nodes outside the cellular network cannot replace these handheld devices as group agents. Under the framework of integrated control and bearer, the group proxy function can only be realized by adding special relays in the cellular network group.

Contents of the invention

The main purpose of the present invention is to provide a service data relay method and a relay node system to at least solve one of the above problems.

According to one aspect of the present invention, a relay node system is provided, including: a relay control entity, configured to receive a relay request, select a relay bearer entity for the relay task requested by the relay request, and request the relay The relay carrying entity performs the relay task, and obtains the service quality measurement information from the service quality measurement entity; the relay carrying entity is used to perform the above relay task, and relays the business data related to the relay task; the service quality measurement entity, It is used to perform the service quality measurement task, and report the obtained service quality measurement information to the relay control entity.

According to another aspect of the present invention, a method for relaying service data is provided, including: a relay control entity receives a relay request, wherein the relay request is used for data transfer between a first node and a second node The service requests relay resources; the relay control entity selects the relay bearer entity that carries the data service, and requests the relay bearer entity to perform the relay task of the data service; the relay bearer entity reserves relay resources for the above data service, and The first node and the second node establish data connections respectively, and transfer service data between the first node and the second node.

Through the present invention, the control and bearer functions of the relay node system are reasonably distributed. The relay bearer entity only completes the basic data forwarding function, and the service quality measurement entity only completes the basic measurement function, thus separating the complex control function from the relay node. The relay control function, bearer function and measurement function can be flexibly configured in actual deployment. Therefore, simple relay bearer entities and service quality measurement entities can be deployed in a large number of terminals, reducing the difficulty of terminal implementation. At the same time, only the relay control entity needs to be upgraded during service upgrade, which simplifies the upgrade process.

Description of drawings

The accompanying drawings described here are used to provide a further understanding of the present invention and constitute a part of the application. The schematic embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute improper limitations to the present invention. In the attached picture:

FIG. 1 is a schematic diagram of implementing relay node management in the prior art;

FIG. 2 is a schematic structural diagram of a relay node system according to Embodiment 1 of the present invention;

FIG. 3 is a network structure diagram for implementing centralized deployment in Embodiment 1 of the present invention;

FIG. 4 is a network structure diagram for implementing hybrid deployment in Embodiment 2 of the present invention;

FIG. 5 is a network structure diagram for implementing distributed deployment in Embodiment 1 of the present invention;

FIG. 6 is a flowchart of a service data relay method according to Embodiment 2 of the present invention;

FIG. 7 is a schematic diagram of a registration process of a relay bearer entity according to Embodiment 3 of the present invention;

FIG. 8 is a schematic diagram of a flow chart of reporting parameter information of a relay bearer entity according to Embodiment 4 of the present invention;

FIG. 9 is a schematic diagram of a flow chart of a relay control entity requesting service quality measurement according to Embodiment 5 of the present invention;

FIG. 10 is a schematic diagram of a flow chart of a QoS measurement entity actively reporting measurement information according to Embodiment 6 of the present invention;

FIG. 11 is a schematic diagram of a flow for selecting a relay bearer entity by a relay control entity according to Embodiment 7 of the present invention.

Detailed ways

Hereinafter, the present invention will be described in detail with reference to the drawings and examples. It should be noted that, in the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined with each other.

Embodiment one

FIG. 2 is a schematic structural diagram of a relay node system according to Embodiment 1 of the present invention. The relay node system includes three logical entities: a relay control entity 203 , a relay bearer entity 204 and a service quality measurement entity 205 .

Wherein, the relay control entity 203 is used to receive the relay request, select the relay bearer entity 204 for the relay task requested by the relay request, request the relay bearer entity 204 to perform the relay task, and report to the service quality measurement entity 205 sends the service quality measurement task; the relay bearer entity 204 is used to execute the relay task and transfer the service data related to the relay task; the service quality measurement entity 205 is used to perform the service quality measurement according to the above service quality measurement task , and report the obtained QoS measurement information to the relay control entity 203.

In practical applications, the relay task means that the relay implements data forwarding between two nodes (the first node and the second node).

Preferably, the above-mentioned relay node system provided by the embodiment of the present invention applies to a peer-to-peer network, and the first node and the second node are two peer nodes in the peer-to-peer network.

In the embodiment of the present invention, the relay control entity 203 completes the control function of the relay node system, but does not provide a specific data bearing function. In the embodiment of the present invention, the data bearer refers to the forwarding of the data flow and the measurement of the service quality of the data flow. The connections between the relay control entity 203 and other entities are all signaling connections, and are not responsible for carrying large amounts of data. The relay control entity 203 may control one or more relay bearer entities 204/QoS measurement entities 205 through signaling. The control function of the relay control entity 203 on the relay bearer entity 204/the service quality measurement entity 205 includes: accepting the registration and registration request of the relay bearer entity 204/the service quality measurement entity 205; maintaining the real-time status information of the relay bearer entity 204 ; Select the appropriate relay bearer entity 204 to implement the data forwarding task; assign the specific relay bearer entity 204 for the relay forwarding task; request the service quality measurement entity 205 to perform service quality measurement and maintain relevant measurement data, and other network management billing control functions.

Meanwhile, in the embodiment of the present invention, the relay control entity 203 is also responsible for performing signaling interaction with entities inside or outside the relay node system, so as to complete necessary service coordination work. Entities within the relay node system include: other relay control entities (relay control entities can exchange service quality measurement information and subordinate relay bearer entity information through signaling), service quality measurement agents (relay control entities can Obtain QoS measurement information through QoS proxy). Entities other than the relay node system include: service control entity 201 and user terminal 202 (relay control entity 203 can receive relay task requests from these entities through signaling), network topology management entity (relay control entity 203 can network topology information); network management and charging entities (relay control entity 203 can complete network management and charging tasks with these entities through signaling).

In the embodiment of the present invention, in order to realize the control function of the relay control entity 203, the relay control entity 203 needs to maintain the following data information: network topology information (including network division, routing structure information, etc.), subordinate relay bearer entities 204 parameter information (including the address, capacity and load of the relay bearer entity, etc.), service quality measurement information (including the delay of the relevant link, delay jitter, packet loss rate and bandwidth, etc.), peer-to-peer relay Control entity information (including coverage of relevant relay control entities, subordinate relay bearer entities, etc.). The above information can be stored in a database within the relay control entity, or can be stored outside the relay control entity, for example, in a distributed hash table (DHT) or a network topology information server.

In practical applications, the relay control entity 203 can select one or more relay relay entities according to the maintenance quality of service measurement information (delay, bandwidth, delay jitter, packet loss rate) and/or the parameter information of relay bearer entities. The bearer entity 204 performs a data forwarding and relaying task. Wherein, the parameter information includes but is not limited to: quality of service, relay link reliability (which may be reported by the relay bearer entity 204, or may also be stored in the relay control entity 203) or relay service price (which may be reported by the relay bearer entity 204, or stored in the relay control entity 203), etc.

The relay bearer entity 204 is responsible for specific data forwarding, and the relay bearer entity 204 only provides basic signaling interfaces, that is, the control signaling interface with the relay control entity 203 and the bearer plane signaling interface. The relay bearer entity 204 may establish bearer plane connections with user terminals or other entities requiring data relay functions, and relay service data for user terminals or other entities requiring data relay functions.

The relay bearer entity 204 completes the relay task under the control of the relay control entity 203. Specifically, the relay bearer entity 204 is used to acquire the address of the relay control entity, and sends a registration request to the relay control entity 203, so as to The relay control entity 203 registers, wherein the registration request carries the above parameter information to report the parameter information of the relay bearer entity 204 to the relay control entity 203; and the relay bearer entity 204 can also cooperate with the relay control entity 203 Complete the necessary network management and billing functions.

In addition, the relay bearer entity 204 can also report its parameter information to the relay control entity 203 periodically or when an event is triggered (for example, the relay task is completed), so that the relay control entity 203 can maintain the relay bearer entity 204 real-time information. Moreover, when the relay bearer entity 204 performs the relay task, it should also maintain the information of the currently performed data forwarding task.

The service quality measurement entity 205 is responsible for performing service quality measurement on the data flow. The QoS measurement entity 205 only provides basic signaling interfaces, that is, the control signaling interface with the relay control entity 203 and the bearer plane signaling interface. The service quality measurement entity 205 can measure the existing data flow on the physical entity where this logical entity is located, and can also establish a dedicated measurement data link with other service quality measurement entities for measurement. When establishing a data link, the QoS measurement entity 205 can perform necessary bearer plane interaction with other QoS measurement entities.

The QoS measurement entity 205 implements QoS measurement under the control of the relay control entity 203 . Further, the service quality measurement entity 205 is also used to send a registration request to the relay control entity 203, submitting its own information;

Further, the QoS measurement entity 205 is also used to maintain information about currently performed QoS measurement tasks.

In a specific implementation, multiple QoS measurement entities 205 may be aggregated through a QoS measurement proxy. That is, the relay control entity sends the QoS measurement request to the QoS measurement agent, and the QoS measurement agent forwards it to the actual QoS measurement entity 205, or the QoS measurement agent may periodically request the QoS measurement entity 205 to perform Measurement of service quality. At the same time, the service quality measurement agent can also complete part of the service quality measurement entity control functions including: accept the service quality measurement entity registration and registration request; maintain the real-time status information of the service quality measurement entity; request the service quality measurement entity 205 to perform service quality measurement And maintain relevant measurement data.

In the embodiment of the present invention, the control and bearer functions of the relay system are reasonably allocated. The relay bearer entity 203 only completes the basic data forwarding function, the service quality measurement entity only completes the basic measurement function, and the complex control function is stripped from the relay node. Therefore, the relay control function, bearer function and measurement function can be flexibly configured in actual deployment. Furthermore, the simple relay bearer entity 204 and the service quality measurement entity 205 can be deployed in a large number of terminals, reducing the difficulty of terminal implementation. At the same time, only the relay control entity 203 needs to be upgraded during service upgrade, thereby improving the efficiency of the upgrade. Further, in the embodiment of the present invention, the relay control entity 203 can also implement flexible deployment, and does not need to be deployed in the same network/network segment as the managed relay bearer entity 204 and the service quality measurement entity 205, which greatly simplifies The complexity of deployment.

In actual network deployment, the relay control entity, relay bearer entity, and service quality measurement entity are all logical entities, which can be flexibly deployed in different physical entities. Although the embodiment of the present invention is mainly aimed at the distributed peer-to-peer network, the deployment of different logical entities in the embodiment of the present invention can be implemented in various ways, and is not limited to the implementation of the distributed peer-to-peer network.

For example, centralized deployment, hybrid deployment, and distributed deployment can be adopted. The several deployment modes of the embodiments of the present invention will be described respectively below. It should be noted that in the following specific deployment methods, the central control server, group agent node, relay node and measurement node all refer to specific physical nodes, and one physical node may contain one or more logical entities.

Fig. 3 describes the network architecture in the system for centralized deployment in the embodiment of the present invention. The network operator may only deploy one central control server 310 (which may be realized by multiple physical servers), and the central control server 310 implements the function of the relay control entity 311 . Optionally, the central control server 310 may also include a service quality measurement agent 312 . A plurality of relay nodes (320, 330) or measurement nodes 340 may be included in the network. Wherein, the relay node may include both the relay bearer entity (for example, 321 ) and the service quality measurement entity (for example, 322 ) or only the relay bearer entity (for example, 331 ). The measurement node 340 only includes a QoS measurement entity 341 . The relay control entity 311 in the central control server 310 is responsible for controlling all relay nodes and measurement nodes in the network, as well as the relay bearer entities and service quality measurement entities included in these nodes. When the central control server 310 includes a QoS measurement agent 312, the QoS measurement agent 312 may be responsible for controlling and managing all measurement nodes in the network and the QoS measurement entities included in these measurement nodes.

Fig. 4 describes the network architecture in the system for hybrid deployment in the embodiment of the present invention. Multiple peer group proxy nodes 410 and 450, as well as relay nodes (420, 430) and measurement nodes (440) may be deployed in the network. The group proxy node may include a relay control entity, a relay bearer entity and a QoS measurement entity at the same time, or may only include a relay control entity, or only include a relay bearer entity and a QoS measurement entity. The relay control entity in each group proxy node is responsible for the management of the relay nodes 420 and 430 and the measurement node 440 in a part of the network. The relay control entities in the group proxy node complete the selection and management functions of the relay bearer entity/QoS measurement entity through signaling interaction. In a hybrid deployment, group proxy nodes, relay nodes, and measurement nodes can form an overlay network in a peer-to-peer manner.

Fig. 5 describes the network architecture in the system for distributed deployment in the embodiment of the present invention. In this architecture, each relay node (510 and 520) includes a relay control entity, a relay bearer entity and a quality of service measurement entity. Each relay control entity only controls a single relay bearer entity and/or service quality measurement entity in the physical node. The relay control entity interacts through the distributed network, or completes the selection and management functions of the relay bearer entity and/or service quality measurement entity by sharing a database. The measurement node 530 may only contain a quality of service measurement entity.

It should be noted that, in the embodiment of the present invention, the relay control entity, the relay bearer entity and the service quality measurement entity may also be deployed in the same physical entity as other network control entities or bearer entities. For example, the relay bearer entity and the service quality measurement entity can be embedded in the user terminal as software modules, and the relay control entity can be integrated with the service control entity or other network elements.

It should be noted that although the embodiment of the present invention only describes the above three deployment methods, it is not limited thereto. In practical applications, the relay node system provided by the embodiment of the present invention can also support various other deployment methods .

In different network deployments, the signaling interaction between the relay control entity, the relay bearer entity and the service quality measurement entity may follow the same process. When multiple logical entities are integrated, the specific signaling interaction can be realized through internal messages.

Embodiment two

FIG. 6 is a flowchart of a method for relaying service data according to Embodiment 2 of the present invention. The method can be completed by the above-mentioned relay node system. The method mainly includes the following steps:

Step S602, the relay control entity 203 receives a relay request, where the relay request is used to request relay resources for data services between the first node and the second node;

For example, a relay request from a user terminal or a service control entity may carry the addresses of the first node and the second node, the requested service type, the authentication information of the user sending the relay request, and the requested service quality request information.

Step S604, the relay control entity 203 selects the relay bearer entity 204 that bears the data service, and requests the relay bearer entity 204 to perform the relay task of the data service;

The relay control entity 203 may select the relay bearer entity 204 arbitrarily, or may execute a corresponding relay selection algorithm to select the relay bearer entity 204 for the relay task. For example, the relay control entity 203 can provide specific service quality according to the relay bearer entity 204, the parameter information of the relay bearer entity 204 (for example, the processing capability of the relay bearer entity, the access network currently connected to the relay bearer entity) type, the existing number of relay tasks of the relay carrying entity, the upper limit of the number of relay tasks, etc.) select the relay carrying entity 204.

For example, the relay control entity 203 sends a relay resource request to the relay bearer entity 204, requesting the relay bearer entity to reserve relay resources for the relay task.

Among them, the specific service quality that the relay bearer entity 204 can provide can be obtained by requesting the service quality measurement entity 205 to measure, or can be obtained through interaction with other relay control entities, or can be obtained from the service stored (that is, maintained) by the relay control entity 203 obtained from quality measurement information.

Wherein, the parameter information of the relay bearer entity 204 may be reported by the relay bearer entity 204 during registration, or may be reported periodically by the relay bearer entity 204 after registration, or reported when a predetermined trigger event occurs .

In step S606, the relay bearer entity reserves relay resources for the above-mentioned data services, establishes data connections with the first node and the second node respectively, and relays service data between the first node and the second node.

Through the above method provided by the embodiment of the present invention, the relay control entity selects the relay bearer entity that carries the service data, thereby separating the control and bearer functions of the relay node, so that the relay control function, the bearer function and the measurement function are in the It can be flexibly configured in actual deployment, which reduces the difficulty of implementing the relay function and improves the flexibility of network deployment.

Embodiment three

In the embodiment of the present invention, the process of registering by the relay bearer entity 204 with the relay control entity 205 is described.

Fig. 7 is a schematic flowchart of a relay bearer entity registering with a relay control entity in an embodiment of the present invention. Among them, the registration process is a process in which the relay bearer entity notifies the relay control entity of its basic status after the system starts or the network environment changes. It mainly includes the following steps:

701. The relay bearer entity determines that registration needs to be performed after the system starts up or senses a change in the network environment.

The relay bearer entity first obtains the network address of the relay control entity. The specific acquisition methods include but are not limited to the following methods: A) by querying the address server or domain name resolution server (DNS), B) dynamically obtained through network configuration information, C) by relaying the statically configured or cached address list of the entity, D ) through the distributed hash table lookup.

702. The relay bearer entity sends registration information to the relay control entity;

Among them, the registration information may include but not limited to the following content: the identity of the relaying entity, the identity verification information of the relaying entity, the network address of the relaying entity, the processing capability (CPU, memory, network bandwidth) of the relaying entity , port resources, remaining battery power, etc.) and the type of access network to which the relay bearer entity is currently connected.

703. The relay control entity records the relevant information of the relay bearer entity, and returns registration success information;

The relay control entity can reject the registration of the relay bearer entity according to the operation policy and the information of the relay bearer entity, and return the registration failure information and indicate the reason for the failure. After the relay bearer entity fails to register, it will not retry the registration process unless the network environment changes or the relevant processing capabilities change.

Similarly, the QoS measurement entity also needs to register with the relay control entity or the QoS measurement agent. The specific process is the same as the registration process of the intermediate bearer entity, and will not be described in detail. If the QoS measurement entity and the relay bearer entity are set together, the registration process can be simplified and completed through the same message.

In the above process, if centralized deployment is adopted, the registration messages of all relay bearer entities are sent to the same relay control entity. If a hybrid deployment is adopted, the relay bearer entity queries the group proxy node to which it belongs through the four methods described in step 701 for registration. If distributed deployment is adopted, the relay bearer entity registers with the relay control entity in the same physical node.

Embodiment four

FIG. 7 is a schematic flowchart of a relay bearer entity reporting information to a relay control entity in an embodiment of the present invention. The relay bearer entity can report its own related information to the relay control entity to which it belongs. The reporting process can be periodically triggered by a timer, or triggered by certain events (such as the completion of forwarding tasks, etc.). The specific steps are described as follows:

801. Relay the bearer entity to report its own information;

Among them, the reported information may include but not limited to the following parameters: the identity of the relay bearer entity, the identity verification information of the relay bearer entity, the network traffic of the relay bearer entity, the number of existing relay tasks, the upper limit of the number of relay tasks and Relay the time elapsed since the bearer entity was started, etc. The reported information may also include specific relay task parameters, including: relay task identifier, task flow, task execution duration, and a list of data connections involved in the task.

802. After receiving the reported information, the relay control entity saves the above information, and may choose to return a response to the reported information, or may not return any information.

Embodiment five

Fig. 9 depicts a schematic flow diagram of a relay control entity requesting a service quality measurement entity to perform service quality measurement. When the relay control entity selects the relay node, it needs to compare the expected service quality of the specific relay bearer entity. Since the relay control entity may not be in the same physical network/network segment as the relay bearer entity, the relay control entity needs to request the service quality measurement entity in a specific network segment to perform service quality measurement. QoS measurement can be performed every time a relay node is selected, or it can be implemented regularly in normal times. The QoS measurement request can be sent directly to the QoS measurement entity, or can be transferred through a QoS proxy. It mainly includes the following steps:

901. According to the relay selection requirement, the relay control entity needs to measure the service quality of the path between the service quality measurement entity 1 and the service quality measurement entity 2, and the relay control entity sends a service quality measurement request message to the service quality measurement entity 1;

Wherein, the information carried in the QoS measurement request message includes, but is not limited to: information about the path to be measured, parameters to be measured, measurement mode, measurement repetition times and measurement duration, and whether cached measurement data is allowed to be returned, etc.

902. Optionally, the relay control entity may send a QoS measurement request message to the QoS measurement entity 2 to allow the QoS measurement entity 1 to establish a connection with the QoS measurement entity 2, where the QoS measurement request may pass through other forwarded by the controlling entity;

903. Establish a data connection between the service quality measurement entity 1 and the service quality measurement entity 2, and perform specific data connection measurement;

904, the service quality measurement entity 1 returns the measurement result (that is, the service quality measurement information) to the relay control entity, and the relay control entity saves the measurement result;

Optionally, the relay control entity may proactively send the measurement results saved by itself to other relay control entities, or share the measurement results at the request of other relay control entities.

Optionally, the relay control entity may request service quality measurement information from the service quality measurement agent, and the service quality measurement agent may select an appropriate service quality measurement entity to perform service quality measurement, or directly send the service quality measurement information saved by itself to the central successor to the controlling entity.

Embodiment six

The embodiment of the present invention describes the flow of the QoS measurement entity actively reporting the QoS measurement information. In this embodiment, the relay control entity requires the service quality measurement entity to measure the service quality of the service data flow during the actual service process. The measurement result can be actively reported by the service quality measurement entity after each service is completed.

Fig. 10 is a flow chart of the quality of service measurement in this embodiment, which mainly includes the following steps:

1001. The relay control entity requires the service quality measurement entity to perform data service quality measurement, wherein, in the service quality measurement request message, the relay control entity specifies the type and characteristics of the service to be measured, the duration of the measurement task, and the measurement content, and reports method and other information;

1002. The service quality measurement entity monitors the service data flow passing through the physical node where the service quality measurement entity is located, or initiated by the physical node, or terminated by the physical node, and detects that when the data service 1 conforms to the service quality measurement request message When describing the business type and characteristics of the business, the service quality measurement entity measures the data flow of business 1; wherein, the business type and characteristics may include but not limited to: business type, data flow, connection protocol type, peer URL, etc.;

1003, the service quality measurement entity fills in the measurement result (that is, the service quality measurement information) according to the reporting method requirements in the measurement request message and reports it to the relay control entity, and the relay control entity receives and stores the service quality measurement information;

Wherein, the reporting time may be after each service measurement is completed, or after obtaining sufficient measurement data, or reporting at regular intervals.

1004. The service quality measurement entity detects that the data service 2 conforms to the service type and characteristics that it needs to measure, and the service quality measurement entity measures the data flow of the service 2;

1005. The service quality measurement entity fills in the measurement result according to the reporting method and sends it to the relay control entity, and the relay control entity receives and saves the measurement result.

Embodiment seven

The embodiment of the present invention describes the process in which the relay control entity accepts an external request to select a relay bearer entity to carry data. When a service needs to establish a connection through a relay node, both the user terminal node or the service control entity can initiate a relay request to the relay control entity to request relay resources. The relay control entity selects an appropriate relay bearer entity to establish a corresponding connection.

FIG. 11 is a flow chart for implementing business data transfer in this embodiment, which mainly includes the following steps:

1101. User terminal 1 needs to establish a data service connection with user terminal 2 through a relay node. User terminal 1 sends a relay request to the relay control entity to request relay resources. The request may include the following information: User terminal 1 , 2's address, the type of business requested by the user, user identity verification information, the requested service quality requirements, etc.;

The message can be forwarded by the service control entity or other relay control entities, or directly generated and sent by the service control entity.

1102. The relay control entity executes a corresponding relay selection algorithm according to the relay requirements requested by the user, and selects this service to be completed by the relay bearer entity 1;

Wherein, the relay selection algorithm can use information such as the specific service quality that different relay bearer entities can provide, the load of the relay bearer entity, etc. to select the bearer entity. When executing the selection algorithm, the relay control entity can interact with other entities to obtain corresponding measurement information, or request the service quality measurement entity to perform measurement (execute the process described in Embodiment 5), or use the service reserved by the relay control entity The quality measurement information (which may be obtained through the process of Embodiment 5, may also be obtained through the process of Embodiment 6, or may be obtained from other relay control entities) guides the relay bearer entity selection.

1103. The relay control entity sends relay resource request information to the selected relay bearer entity 1 to reserve relay resources, wherein the relay resource request information includes specific relay types, data forwarding requirements, and reserved resource information. parameters, etc.;

1104. After the relay bearer entity reserves the relay resource, it returns a response message to the relay control entity, and the response message includes the parameters of the relay resource reserved by the relay bearer entity 1 for this service;

1105. The relay control entity returns the relevant parameters of the resources reserved by the relay bearer entity 1 to the user terminal 1 through a relay request response message;

1106, the user terminal 1 and the user terminal 2 establish a data connection through the relay bearer entity 1, and the relay bearer entity 1 relays the service data of the user terminal 1 and the user terminal 2.

In the above process, in step 1105, the relay control entity may return information of one or more relay bearer entities. Then in the above process, before step 1106 or after step 1106, user terminal 1 may request the service quality measurement entity to measure the actual connection quality, and then decide which relay bearer entity to actually use to establish the connection. For example, if the QoS measurement entity is not located in UE 1, UE 1 can send a measurement request to the QoS measurement entity through the relay control entity; if the QoS measurement entity is deployed in UE 1, UE 1 can directly pass through Its QoS measurement entity performs measurement tasks.

From the above description, it can be seen that in the embodiment of the present invention, by reasonably allocating the control and bearer functions of the relay system, the relay bearer entity only completes the basic data forwarding function, and the service quality measurement entity only completes the Basic measurement functions, while complex control functions are stripped from relay nodes. In this way, the relay control function, bearer function and measurement function can be flexibly configured in actual deployment. Therefore, simple relay bearer entities and service quality measurement entities can be deployed in a large number of terminals, reducing the difficulty of terminal implementation. At the same time, only the relay control entity needs to be upgraded when the service is upgraded. Furthermore, after the relay control entity is independent, the relay control entity can also be deployed flexibly, and does not need to be in the same network/network segment as the managed relay bearer entity and service quality measurement entity, which greatly simplifies the complexity of deployment Spend.

Obviously, those skilled in the art should understand that each module or each step of the above-mentioned present invention can be realized by a general-purpose computing device, and they can be concentrated on a single computing device, or distributed in a network formed by multiple computing devices Alternatively, they may be implemented in program code executable by a computing device so that they may be stored in a storage device to be executed by a computing device, and in some cases in an order different from that shown here The steps shown or described are carried out, or they are separately fabricated into individual integrated circuit modules, or multiple modules or steps among them are fabricated into a single integrated circuit module for implementation. As such, the present invention is not limited to any specific combination of hardware and software.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and changes. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (19)

1. a relay node is characterized in that, comprising:

The relay and control entity is used to receive relay request, selects relaying to carry entity for the relay task that said relay request is asked, and asks said relaying to carry entity and carries out said relay task, and obtain qos measurement information from the qos measurement entity;

Said relaying carries entity, is used to carry out said relay task, the business datum that transfer is relevant with said relay task;

Said qos measurement entity is used to carry out the qos measurement task, gives said relay and control entity with the said qos measurement information reporting that obtains.

2. relay node according to claim 1 is characterized in that,

Said relaying carries the network address that entity also is used to obtain said relay and control entity, sends to said relay and control entity and carries the register requirement that said relaying carries the parameter information of entity;

Said relay and control entity also is used to receive said register requirement, preserves the said parameter information that carries in the said register requirement.

3. relay node according to claim 1 is characterized in that, said relaying carrying entity also is used for periodically or when trigger event takes place, reports said relaying to carry the parameter information of entity to said relay and control entity.

4. according to the said relay node of claim 1, it is characterized in that said relay and control entity also is used for obtaining and preserve qos measurement information from said relay node inside or other outside relay and control entities.

5. according to each described relay node in the claim 1 to 4, it is characterized in that said relay and control entity carries entity according to said parameter information and/or the said relaying of said qos measurement Information Selection that said relaying carries entity.

6. relay node according to claim 1 is characterized in that,

Said qos measurement entity also is used to obtain the network address of said relay and control entity, sends register requirement to said relay and control entity;

Said relay and control entity also is used to receive said register requirement, accepts the registration of said qos measurement entity.

7. relay node according to claim 1 is characterized in that, the said measurement result that said relay and control entity also is used to receive sends to inner or other the outside relay and control entities of said relay node.

8. according to each described relay node in the claim 1 to 4,6 and 7, it is characterized in that said relay and control entity also is used to obtain network topological information.

9. according to each described relay node in the claim 1 to 4,6 and 7, it is characterized in that said relay and control entity also is used for carrying out alternately with webmaster and charging entity, accomplish network management task and charging task.

10. according to each described relay node in the claim 1 to 4,6 and 7; It is characterized in that; Said relaying carries entity and is used to said relay task reservation relay resource; Set up the first node corresponding and the data of Section Point respectively and be connected, connect the said business datum of transmitting between said first node and the said Section Point through said data with said relay task.

11. relay node according to claim 10 is characterized in that, said first node and said Section Point are two peer node in the peer-to-peer network.

12. according to each described relay node in the claim 1 to 4,6 and 7,

It is characterized in that said relay node also comprises:

The qos measurement agency; Be used to receive the said qos measurement task that said relay and control entity issues said qos measurement task is sent to said qos measurement entity, or periodically issue said qos measurement task to said qos measurement entity.

13. the trunking method of a business datum is characterized in that, comprising:

The relay and control entity receives relay request, and wherein, said relay request is used to the data service request relay resource between first node and the Section Point;

The relaying that said relay and control entity selection is carried said data service carries entity, asks said relaying to carry the relay task that entity is carried out said data service;

It is that relay resource is reserved in said data service that said relaying carries entity, sets up data respectively with said first node and said Section Point and is connected, the business datum between said first node of transfer and the said Section Point.

14. method according to claim 13 is characterized in that, the relaying carrying entity that said relay and control entity selection is carried said data service comprises:

Said relay and control entity obtains parameter information that said relaying carries entity and carries the relevant qos measurement information of entity with said relaying;

Said relay and control entity carries entity according to said parameter information and the said relaying of said qos measurement information.

15. method according to claim 14 is characterized in that, said relay and control entity obtains one of in the following manner the qos measurement information that said relaying carries entity:

Said relay and control entity is through carrying the relevant qos measurement information of entity with obtaining alternately with said relaying of other relay and control entities;

Said relay and control entity obtains from the qos measurement information of having preserved with said relaying and carries the relevant qos measurement information of entity;

Said relay and control entity carries entity through request and said relaying and carries out qos measurement at the qos measurement entity of the same physical network or the network segment, obtains with said relaying and carries the relevant qos measurement information of entity.

16. method according to claim 15 is characterized in that, said relay and control entity obtains said qos measurement information and comprises through asking said qos measurement entity to carry out qos measurement:

Said relay and control entity sends measurement request to said qos measurement entity; Wherein, Carry the information in path to be measured in the said measurement request, said path to be measured is the path between said qos measurement entity and another qos measurement entity;

Receive and set up data between said qos measurement entity and said another qos measurement entity of said measurement request and connect, measure the parameter that said data connect;

Said qos measurement entity is given said relay and control entity with measurement result as said qos measurement information reporting according to the mode that reports of carrying in the said measurement request.

17. method according to claim 16; It is characterized in that; After said qos measurement entity was given said relay and control entity with said qos measurement information reporting, said method also comprises: said relay and control entity received and preserves said qos measurement information.

18. method according to claim 15 is characterized in that, said method also comprises:

Said relay and control entity sends measurement request to said qos measurement entity, asks said qos measurement entity that the service quality of the business data flow of ongoing business is measured;

Said qos measurement entity to through the physical node at said qos measurement entity place or initiate by said physical node or monitor by the business data flow that said physical node stops, find the said business data flow that said relay and control entity requests is measured;

Said qos measurement entity is measured the said business data flow that finds, and gives said relay and control entity with the qos measurement information reporting that measures;

Said relay and control entity receives and preserves the said qos measurement information that said qos measurement entity reports.

19. method according to claim 14 is characterized in that, said relay and control entity obtains parameter information that said relaying carries entity and comprises one of following:

Said relay and control entity receives said relaying and carries the register requirement of carrying said parameter information that entity sends, and from said register requirement, obtains and preserve said parameter information;

Said relay and control entity receives and preserves said relaying and carries entity periodically or the said parameter information that reports when taking place of trigger event.

Images