WO2020200123A1

WO2020200123A1 - Communication method and apparatus

Info

Publication number: WO2020200123A1
Application number: PCT/CN2020/081864
Authority: WO
Inventors: 谭仕勇; 应江威
Original assignee: 华为技术有限公司
Priority date: 2019-04-04
Filing date: 2020-03-27
Publication date: 2020-10-08
Also published as: CN111786758A; CN111786758B

Abstract

Disclosed are a communication method and apparatus, fulfilling enterprise requirements in the field of vertical industries. The method comprises: a centralized controller receiving a general message comprising an identifier of a terminal, first function reference information and second function reference information; sending, according to the first function reference information and the identifier of the terminal, to a first function entity a request message for requesting that the first function entity executes a first function for the terminal; sending, according to the second function reference information and the identifier of the terminal, to a second function entity a request message for requesting that the second function entity executes a second function for the terminal; after receiving the request message, the first function entity executing the first function for the terminal according to the received request message; and after receiving the request message, the second function entity executing the second function for the terminal according to the received request message.

Description

Communication method and device

This application claims the priority of a Chinese patent application filed with the State Intellectual Property Office on April 4, 2019, the application number is 201910272893.8, and the application name is "a communication method and device", the entire content of which is incorporated into this application by reference .

Technical field

The embodiments of the present application relate to the field of communication technologies, and in particular, to a communication method and device.

Background technique

With the continuous development of communication technology, the vertical industry field has become an important research field. For example, the Internet of Things (IoT), machine to machine (M2M), etc. These areas have special requirements for network deployment, such as faster and more reliable.

At present, network deployment in the vertical industry field is usually implemented based on the mobile communication network defined by the 3rd generation partnership project (3GPP). Take the 5th generation (5G) mobile communication network defined by 3GPP as an example. As shown in Figure 1, the 5G mobile communication network may include access and mobility management functions (AMF), base stations And multiple network functions (NF), such as session management function (SMF), user plane function (UPF), policy control function (PCF), unified data management (unified data management, UDM), authentication server function (authentication server function, AUSF), etc.

Since the mobile communication network defined by 3GPP is designed by operators according to the requirements of wide coverage, large capacity, large deployment scale, diversified services, etc., there are signaling and functional associations between different network functions, such as: between AMF and SMF There are signaling and function associations, signaling and function associations between SMF and UPF, signaling and function associations between SMF and PCF, so that there are many logical interfaces and signaling interactions, such as: the terminal needs to pass AMF, SMF The session establishment request is sent to the UPF, which triggers the UPF to establish a packet data unit (PDU) session (session). This leads to more complex signaling design and interaction logic, high signaling overhead, and difficult network maintenance. It can be seen that the vertical industry network deployed based on the mobile communication network defined by 3GPP also has problems such as more complex signaling design and interaction logic, high signaling overhead, and difficult network maintenance, high deployment costs, and complex maintenance management.

Summary of the invention

The embodiments of the present application provide a communication method and device to solve the problem that the existing 5G network defined by 3GPP is not suitable for use by enterprises in the vertical industry field.

In order to achieve the foregoing objectives, the following technical solutions are adopted in the embodiments of this application:

In the first aspect, an embodiment of the present application provides a communication method. The method may include: a centralized controller receives a general message including a terminal's identity, first function reference information, and second reference information, and according to the first function reference information and the terminal Send to the first functional entity a first request message for requesting the first functional entity to perform the first function for the terminal, and according to the second function reference information and the terminal’s identity, send to the second functional network element to request the first The second function entity is a second request message for the terminal to perform the second function.

Based on the method described in the first aspect, the centralized controller may receive multiple function reference information through one message, and request multiple functional entities to perform multiple functions for the terminal according to the received multiple function reference information. Compared with the prior art, in the method described in the first aspect, multiple function reference information can be concentrated in one message and sent to the centralized controller, instead of performing multiple functions for the terminal through signaling interaction between network functions. Features. In this way, it is not only possible to centrally process multiple functions executed for the same terminal, but also to reduce the number of messages for sending function reference information, reduce signaling overhead, and save network resources.

In a first embodiment of the first aspect, in combination with the first aspect, the first function reference information includes at least one of the first signaling semantics and the identity of the first function entity; the second function reference information includes the second information At least one of the semantics and the identification of the second functional entity; wherein the first signaling semantics is used to indicate the first function; the second signaling semantics is used to indicate the second function. Based on this embodiment, the signaling semantics and/or the identification of the functional entity used to indicate the corresponding function can be carried in the function reference information and sent to the centralized controller, so that the centralized controller can according to the signaling semantics and/or the identification of the functional entity The functional entity is requested to perform the corresponding function, and the design is simple.

In a second embodiment of the first aspect, in combination with the first embodiment of the first aspect, the first request message includes the first signaling semantics; the second request message includes the second signaling semantics. Based on this embodiment, the centralized controller can carry part of the received multiple function reference information (such as signaling semantics) in the request message and forward it to the functional entity, without the need for the centralized controller to parse the function reference information. The content reduces the design complexity of the centralized controller and the power consumption caused by the analysis of messages.

In a third embodiment of the first aspect, in combination with the first aspect or any embodiment of the first aspect, the first request message includes the input parameter of the first function, and the input parameter of the first function is used for the first function The entity performs the first function. Based on this embodiment, the centralized controller can carry the input parameters required by the functional entity to perform the function in the request message and send it to the functional entity, so that the functional entity executes the corresponding function according to the received input parameter. Only when the corresponding function is executed, the input parameters of the function are obtained, which reduces the design complexity of the functional entity.

In a fourth embodiment of the first aspect, in combination with any one of the first aspect to the second embodiment of the first aspect, the method further includes: the centralized controller receives the user data from the first functional entity For the third request message requesting the input parameters of the first function, the centralized controller sends the input parameters of the first function to the first function entity according to the third request message. Based on this embodiment, the functional entity can obtain the input parameters required to execute the function through the centralized controller.

In the fifth embodiment of the first aspect, in combination with the third embodiment of the first aspect or the fourth embodiment of the first aspect, the method further includes: the centralized controller receives from the terminal or the access network device The input parameters of the first function. Based on this embodiment, the terminal or the access network device can send the input parameters of the function to the centralized controller, without the centralized controller obtaining the input parameters needed to perform the function from the database or other network elements, reducing the design complexity of the centralized controller .

In the sixth embodiment of the first aspect, in combination with the third embodiment of the first aspect or the fourth embodiment of the first aspect, the general message includes the input parameter of the first function. Based on this embodiment, the terminal or the access network device can carry the function reference information and the input parameters of the function together in a general message and send it to the centralized controller, which reduces the signaling overhead and does not require the centralized controller to obtain from the database or other network elements. The input parameters required to perform functions reduce the design complexity of the centralized controller.

In the seventh embodiment of the first aspect, in combination with the sixth embodiment of the first aspect, the general message includes the first signaling header, the second signaling header, and the information element; the first signaling header includes the first function reference Information and a first cell pointer, the first cell pointer is used to indicate the position of the cell carrying the input parameter of the first function in the general message; the second signaling header includes the second function reference information. Based on this embodiment, the function reference information and the cell pointer used to indicate the cell position of the input parameter can be carried in the signaling header and sent to the centralized controller, so that the centralized controller can obtain the first cell from the cell according to the cell pointer. A function input parameter.

In the eighth embodiment of the first aspect, in combination with any one of the fifth embodiment of the first aspect to the seventh embodiment of the first aspect, the method further includes: The input parameters of a function are stored in the database. Based on this embodiment, the centralized controller can store the acquired input parameters of the first function in the database, so that the functional network element performing the first function obtains the input parameters from the database. Compared with the prior art, no function is required. The network element stores the input parameters required to perform the corresponding function locally, which relieves the storage pressure caused by the local storage of the input parameters of the functional network element; at the same time, the centralized controller stores the input parameters in the database, which is convenient for other functional network elements Share this input parameter.

In a ninth embodiment of the first aspect, in combination with the first aspect or any embodiment of the first aspect, the first request message includes the first cell pointer, and the third request message includes the first cell pointer. Based on this embodiment, the centralized controller can forward the cell pointer in the received general message to the functional entity, and when the functional entity performs the function, the functional entity sends the cell pointer to the centralized controller to make the centralized controller The controller obtains the input parameters required to execute the function from the cell according to the cell pointer, and sends the obtained input parameters to the functional entity. In this way, the functional entity does not need to store the input parameters needed to execute the corresponding function in the Locally, the function reference information required to execute the function is obtained locally, which relieves the storage pressure caused by the function entity's local storage of input parameters.

In a tenth embodiment of the first aspect, in combination with the first aspect or any embodiment of the first aspect, the method further includes: the centralized controller receives from the first functional entity that is used to indicate that the first function is A response to the first request message that is successfully executed; and, the centralized controller receives a response from the second functional entity to the second request message indicating that the second function is successfully executed. Based on this embodiment, when the functional entity successfully executes the corresponding function, it can return a response to the centralized controller to instruct the centralized controller to successfully execute the corresponding function, so that the centralized controller can perform subsequent processes according to the received response, such as: Send the received response to the terminal or obtain the terminal data from the database according to the received response.

In an eleventh embodiment of the first aspect, in combination with the tenth embodiment of the first aspect, the method further includes: the centralized controller sends a response of the general message, and the response of the general message is used to notify the first function and The second function was successfully executed. Based on this embodiment, after receiving the response returned by the functional entity, the centralized controller sends a response of the general message to the terminal or the access network device, so that the terminal or the access network device performs subsequent actions according to the response of the general message.

In a twelfth embodiment of the first aspect, in combination with the eleventh embodiment of the first aspect, the response of the first request message includes third signaling semantics, and the third signaling semantics is used to indicate the third function, The response of the general message includes the third signaling semantics. Based on this embodiment, the functional entity can send the signaling semantics for indicating the third function to the centralized controller. After the centralized controller receives the signaling semantics, it directly carries the signaling semantics in the response of the general message and forwards it to the centralized controller. The terminal or the access network device, so that the terminal or the access network device performs the corresponding function according to the received signaling semantics. In this process, the centralized controller does not need to analyze the signaling semantics sent by the functional entity. The semantics are forwarded to the terminal or access network equipment, which reduces the design complexity and power consumption of the centralized controller.

In a thirteenth embodiment of the first aspect, in combination with the eleventh embodiment of the first aspect or the twelfth embodiment of the first aspect, the response of the general message further includes the first data of the terminal. Based on this embodiment, the centralized controller can carry the data of the terminal in the response of the general message and send it to the terminal. In this way, the terminal does not need to obtain the data of the terminal from a database or other devices, which reduces the design complexity of the terminal.

In a fourteenth embodiment of the first aspect, in combination with the thirteenth embodiment of the first aspect, the response of the first request message includes data indication information, and the data indication information is used to indicate the first data of the terminal. Before the centralized controller sends the response of the general message, the method further includes: the centralized controller obtains the first data of the terminal from the database according to the data indication information. Based on this embodiment, the centralized controller can obtain terminal data from the database according to the instructions of the functional entity, which reduces the complexity of obtaining terminal data by the centralized controller, and the implementation method is simple.

In a fifteenth embodiment of the first aspect, in combination with the thirteenth embodiment of the first aspect, the response of the first request message includes the first data of the terminal. Based on this embodiment, the functional entity can carry the data of the terminal in the response of the request message and send it to the centralized controller. The centralized controller obtains the data of the terminal from the response of the request message, and carries the data of the terminal in the general message. The response is sent to the terminal. In this way, there is no need for a centralized controller to obtain terminal data from the database, which reduces the design complexity of the centralized controller.

In a sixteenth embodiment of the first aspect, in combination with the first aspect or any embodiment of the first aspect, the method further includes: the centralized controller receives the output parameter of the first function from the first functional entity , Store the output parameters of the first function in the database. Based on this embodiment, the output parameters after the first functional entity performs a certain function can be stored in the database, which not only facilitates other functional entities or devices to share the output parameters after the first functional entity performs a certain function, but also avoids parameters Redundant storage.

In the seventeenth embodiment of the first aspect, in combination with the sixteenth embodiment of the first aspect, the output parameter of the first function is carried in the response of the first request message. Based on this embodiment, the functional entity can carry its output parameters after executing a certain function in the response of the first request message and send it to the centralized controller, without adding a new signaling message for carrying output parameters, reducing signaling overhead , Save network resources.

In an eighteenth embodiment of the first aspect, in combination with the first aspect or any embodiment of the first aspect, when the timing relationship between the first function and the second function is parallel, the first request message and the second The second request message is sent by the centralized controller at the same time; or, when the sequence relationship between the first function and the second function is serial, and the first function is executed before the second function, the second request message is sent by The centralized controller sends the response after receiving the first request message; or, when the time sequence relationship between the first function and the second function is serial, and the second function is executed before the first function, the first The request message is sent by the centralized controller after receiving the response of the second request message. Based on this embodiment, the centralized controller can determine the sequence in which multiple functional entities perform functions for the terminal, and send request messages to the multiple functional entities according to the determined sequence. In this way, the centralized controller can trigger multiple functional entities to perform functions at the same time according to a received message, or trigger multiple functional entities to perform functions successively.

In a nineteenth embodiment of the first aspect, in combination with the eighteenth embodiment of the first aspect, the method further includes: the centralized controller determines the first function according to the first function reference information and the second function reference information. The timing relationship between the function and the second function. Based on this embodiment, the centralized controller can determine the order in which multiple functional entities perform functions for the terminal according to the multiple functional reference information received.

In a twentieth embodiment of the first aspect, in combination with the first aspect or any embodiment of the first aspect, the method further includes: the centralized controller receives a fourth request message from the second functional entity, and the fourth The request message is used to request the input parameters of the second function. The input parameters of the second function include part or all of the output parameters of the first function. The centralized controller sends the second function entity to the second function entity according to the fourth request message. Input parameters. Based on this embodiment, the centralized controller can obtain the input parameters of the second function from the output parameters of the first function at the request of the second functional entity, and send the input parameters of the second function to the second functional entity, so that The second functional entity executes the second function according to the input parameters of the second function.

In the second aspect, the present application provides a communication device, which may be a centralized controller or a chip or a system on a chip in the centralized controller. The communication device can realize the functions performed by the centralized controller in the above-mentioned aspects or various possible designs, and the functions can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions. For example, the communication device may include: a receiving unit and a sending unit;

A receiving unit, configured to receive a general message including an identifier of the terminal, first function reference information, and second reference information;

The sending unit is configured to send to the first functional entity a first request message for requesting the first functional entity to perform the first function for the terminal according to the first function reference information and the terminal identifier received by the receiving unit, and according to the receiving unit receiving The received second function reference information and the terminal identifier send a second request message for requesting the second function entity to perform the second function for the terminal to the second function network element.

Based on the communication device described in the second aspect, it is possible to receive multiple function reference information through one message, and request multiple functional entities to perform multiple functions for the terminal based on the received multiple function reference information, rather than through network functions. The inter-signaling interaction performs multiple functions for the terminal. In this way, it is not only possible to centrally process multiple functions executed for the same terminal, but also to reduce the number of messages for sending function reference information, reduce signaling overhead, and save network resources.

In a first embodiment of the second aspect, with reference to the second aspect, the first function reference information includes at least one of the first signaling semantics and the identity of the first function entity; the second function reference information includes the second information At least one of the semantics and the identification of the second functional entity; wherein the first signaling semantics is used to indicate the first function; the second signaling semantics is used to indicate the second function. Based on this embodiment, the signaling semantics used to indicate the corresponding function and/or the identification of the functional entity can be carried in the function reference information and sent to the communication device, so that the communication device can request the function according to the signaling semantics and/or the identification of the functional entity. The entity performs the corresponding function and the design is simple.

In a second embodiment of the second aspect, in combination with the first embodiment of the second aspect, the first request message includes the first signaling semantics; the second request message includes the second signaling semantics. Based on this embodiment, the sending unit can carry part of the received multiple function reference information (such as signaling semantics) in the request message and forward it to the functional entity, without the need to parse the content included in the function reference information, and reduce The design complexity of the centralized controller and the power consumption brought by parsing messages are improved.

In a third embodiment of the second aspect, in combination with the second aspect or any embodiment of the second aspect, the first request message includes the input parameter of the first function, and the input parameter of the first function is used for the first function The entity performs the first function. Based on this embodiment, the sending unit can carry the input parameters required by the functional entity to perform the function in the request message and send it to the functional entity, so that the functional entity executes the corresponding function according to the received input parameter. In this way, the functional entity does not need to perform the function. The input parameters of the function are obtained only when the corresponding function is used, which reduces the design complexity of the functional entity.

In a fourth embodiment of the second aspect, in combination with any one of the second aspect to the second embodiment of the second aspect, the receiving unit is further configured to receive data from the first functional entity for The sending unit for the third request message requesting the input parameters of the first function is further configured to send the input parameters of the first function to the first functional entity according to the third request message. Based on this embodiment, the functional entity can obtain the input parameters required to execute the function through the communication device.

In the fifth embodiment of the second aspect, in combination with the third embodiment of the second aspect or the fourth embodiment of the second aspect, the receiving unit is further configured to receive information from a terminal or an access network device The input parameter of the first function. Based on this embodiment, the terminal or the access network device can send the input parameters of the function to the communication device, without the communication device obtaining the input parameters required to perform the function from the database or other network elements, which reduces the design complexity of the communication device .

In the sixth embodiment of the second aspect, in combination with the third embodiment of the second aspect or the fourth embodiment of the second aspect, the general message includes the input parameter of the first function. Based on this embodiment, the terminal or the access network device can carry the function reference information and the input parameters of the function together in a general message and send it to the communication device, reducing signaling overhead, and without the communication device acquiring from a database or other network elements The input parameters required to perform functions reduce the design complexity of the communication device.

In the seventh embodiment of the second aspect, in combination with the sixth embodiment of the second aspect, the general message includes the first signaling header, the second signaling header, and the information element; the first signaling header includes the first function reference Information and a first cell pointer, the first cell pointer is used to indicate the position of the cell carrying the input parameter of the first function in the general message; the second signaling header includes the second function reference information. Based on this embodiment, the function reference information and the cell pointer used to indicate the cell position of the input parameter can be carried in the signaling header and sent to the communication device, so that the communication device can obtain the first information from the cell according to the cell pointer. A function input parameter.

In an eighth embodiment of the second aspect, with reference to any one of the fifth embodiment of the second aspect to the seventh embodiment of the second aspect, the communication device further includes: a storage unit, It is used to store the input parameters of the first function in the database. Based on this embodiment, the communication device can store the acquired input parameters of the first function in the database, so that the functional network element performing the first function can obtain the input parameters from the database. Compared with the prior art, no functional network is required. The element stores the input parameters required to perform the corresponding function locally, which relieves the storage pressure caused by the local storage of input parameters by the functional network element; at the same time, the communication device stores the input parameters in the database, so that other functional network elements can share the input parameters. Input parameters.

In a ninth embodiment of the second aspect, in combination with the second aspect or any of the embodiments of the second aspect, the first request message includes the first cell pointer, and the third request message includes the first cell pointer. Based on this embodiment, the communication device can forward the cell pointer in the received general message to the functional entity, and when the functional entity performs the function, the functional entity sends the cell pointer to the communication device so that the communication device can The cell pointer obtains the input parameters required to perform the function from the cell, and sends the obtained input parameters to the functional entity. In this way, the functional entity does not need to store the input parameters required to perform the corresponding function locally. Locally obtain the function reference information needed to execute the function, which relieves the storage pressure caused by the function entity's local storage of input parameters.

In a tenth embodiment of the second aspect, in combination with the second aspect or any of the embodiments of the second aspect, the receiving unit is further configured to receive from the first functional entity that is used to indicate that the first function is successful. A response to the executed first request message; and, a response to a second request message indicating that the second function was successfully executed from the second functional entity. Based on this embodiment, after the functional entity successfully performs the corresponding function, it can return a response to the communication device to instruct the communication device to successfully perform the corresponding function, so that the communication device can perform subsequent processes according to the received response, such as: The response is sent to the terminal or the data of the terminal is obtained from the database according to the received response.

In an eleventh embodiment of the second aspect, in combination with the tenth embodiment of the second aspect, the sending unit is further configured to send a response to a general message, and the response to a general message is used to notify the first function and the second The second function was successfully executed. Based on this embodiment, after receiving the response returned by the functional entity, the communication device sends a response of the general message to the terminal or the access network device, so that the terminal or the access network device performs subsequent actions according to the response of the general message.

In a twelfth embodiment of the second aspect, in combination with the eleventh embodiment of the second aspect, the response of the first request message includes third signaling semantics, and the third signaling semantics is used to indicate the third function, The response of the general message includes the third signaling semantics. Based on this embodiment, the functional entity can send the signaling semantics for indicating the third function to the communication device. After receiving the signaling semantics, the communication device directly carries the signaling semantics in the response of the general message and forwards it to the terminal or Access network equipment, so that the terminal or access network equipment performs corresponding functions according to the received signaling semantics. In this process, the communication device does not need to parse the signaling semantics sent by the functional entity, but only forwards the signaling semantics to The terminal or access network equipment reduces the design complexity and power consumption of the communication device.

In a thirteenth embodiment of the second aspect, in combination with the eleventh embodiment of the second aspect or the twelfth embodiment of the second aspect, the response of the general message further includes the first data of the terminal. Based on this embodiment, the communication device can carry the data of the terminal in the response of the general message and send it to the terminal. In this way, the terminal does not need to obtain the data of the terminal from a database or other equipment, which reduces the design complexity of the terminal.

In a fourteenth embodiment of the second aspect, in combination with the thirteenth embodiment of the second aspect, the response of the first request message includes data indication information, and the data indication information is used to indicate the first data of the terminal. Before the sending unit sends the response of the general message, the communication device further includes: an acquiring unit configured to acquire the first data of the terminal from the database according to the data indication information. Based on this embodiment, the communication device can obtain terminal data from the database according to the instruction of the functional entity, which reduces the complexity of obtaining the terminal data by the communication device, and the implementation method is simple.

In a fifteenth embodiment of the second aspect, in combination with the thirteenth embodiment of the second aspect, the response of the first request message includes the first data of the terminal. Based on this embodiment, the functional entity can carry the data of the terminal in the response of the request message and send it to the communication device. The communication device obtains the data of the terminal from the response of the request message and carries the data of the terminal in the response of the general message. Send to the terminal. In this way, there is no need for a centralized controller to obtain terminal data from the database, which reduces the design complexity of the communication device.

In a sixteenth embodiment of the second aspect, in combination with the second aspect or any embodiment of the second aspect, the receiving unit is further configured to receive the output parameter of the first function from the first functional entity, The communication device further includes a storage unit for storing the output parameters of the first function in a database. Based on this embodiment, the output parameters after the first functional entity performs a certain function can be stored in the database, which not only facilitates other functional entities or devices to share the output parameters after the first functional entity performs a certain function, but also avoids parameters Redundant storage.

In the seventeenth embodiment of the second aspect, in combination with the sixteenth embodiment of the second aspect, the output parameter of the first function is carried in the response of the first request message. Based on this embodiment, the functional entity can carry its output parameters after performing a certain function in the response of the first request message and send it to the communication device without adding a new signaling message for carrying output parameters, thereby reducing signaling overhead. Save network resources.

In an eighteenth embodiment of the second aspect, in combination with the second aspect or any embodiment of the second aspect, when the timing relationship between the first function and the second function is parallel, the first request message and the second The second request message is sent by the centralized controller at the same time; or, when the sequence relationship between the first function and the second function is serial, and the first function is executed before the second function, the second request message is sent by The centralized controller sends the response after receiving the first request message; or, when the time sequence relationship between the first function and the second function is serial, and the second function is executed before the first function, the first The request message is sent by the centralized controller after receiving the response of the second request message. Based on this embodiment, the communication device can determine the sequence in which multiple functional entities perform functions for the terminal, and send request messages to the multiple functional entities according to the determined sequence. In this way, the communication device can trigger multiple functional entities to perform functions at the same time according to a received message, or trigger multiple functional entities to perform functions sequentially.

In a nineteenth embodiment of the second aspect, in combination with the eighteenth embodiment of the second aspect, the communication device further includes: a determining unit, configured to determine according to the first function reference information and the second function reference information , Determine the timing relationship between the first function and the second function. Based on this embodiment, the communication device can determine the order in which the multiple functional entities perform functions for the terminal according to the multiple functional reference information received.

In a twentieth embodiment of the second aspect, in combination with the second aspect or any embodiment of the second aspect, the receiving unit is further configured to receive a fourth request message from the second functional entity, and the fourth request The message is used to request input parameters of the second function. The input parameters of the second function include part or all of the output parameters of the first function. The sending unit is also used to send the second function entity to the second function entity according to the fourth request message. The input parameters of the function. Based on this embodiment, the communication device can obtain the input parameters of the second function from the output parameters of the first function at the request of the second functional entity, and send the input parameters of the second function to the second functional entity for the first time The second functional entity executes the second function according to the input parameters of the second function.

In a third aspect, a communication device is provided, including: a processor and a memory; the memory is used to store computer execution instructions, and when the communication device is running, the processor executes the computer execution instructions stored in the memory to enable the The communication device executes the communication method described in the foregoing first aspect or any possible design of the first aspect.

In a fourth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores instructions that, when run on a computer, enable the computer to execute the first aspect or any of the above aspects. Design the described communication method.

In a fifth aspect, a computer program product containing instructions is provided, which when running on a computer, enables the computer to execute the communication method described in the first aspect or any one of the possible designs of the foregoing aspects.

In a sixth aspect, a chip system is provided. The chip system includes a processor and a communication interface, and is used to support the communication device to implement the functions involved in the above aspects. For example, the processor receives the terminal identifier and the first function through the communication interface. The general message of the reference information and the second reference information, and according to the first function reference information and the terminal identifier, a first request message for requesting the first function entity to perform the first function for the terminal is sent to the first function entity through the communication interface And, according to the second function reference information and the terminal identifier, a second request message for requesting the second function entity to perform the second function for the terminal is sent to the second function network element through the communication interface. In a possible design, the chip system further includes a memory, and the memory is used to store necessary program instructions and data of the communication device. The chip system can be composed of chips, or include chips and other discrete devices.

Among them, the technical effects brought about by any one of the design methods of the third aspect to the sixth aspect may refer to the technical effects brought about by the above-mentioned first aspect or any possible design of the first aspect, and will not be repeated.

In a seventh aspect, an embodiment of the present application provides a communication method, wherein the method includes: a first functional entity receiving a first functional entity from a centralized controller for requesting the first functional entity to perform the first function for the terminal. In the request message, the first functional entity executes the first function according to the first request message.

Based on the method described in the seventh aspect, the first functional entity can perform the first function under the control of the centralized controller, without interacting with other functional entities, and perform corresponding functions at the request of other functional entities, reducing the number of functional entities. The complexity of interaction.

In a first embodiment of the seventh aspect, with reference to the seventh aspect, the first request message includes first signaling semantics, and the first signaling semantics is used to indicate the first function. Based on this embodiment, the centralized controller may carry the first signaling semantics in the first request message and send it to the first functional entity, so that the first functional entity triggers the execution of the first function according to the first signaling semantics.

In the second embodiment of the seventh aspect, in combination with the first embodiment of the seventh aspect, the first request message further includes the input parameters of the first function; the input parameters of the first function are used by the first functional entity to execute the first function. A function. The first functional entity executes the first function according to the first request message, including: the first functional entity executes the first function according to the first signaling semantics and the input parameters of the first function. Based on this embodiment, the first functional entity can execute the first function according to the first signaling semantics and the input parameters of the first function.

In a third embodiment of the seventh aspect, in combination with the first embodiment of the seventh aspect, the method further includes: the first functional entity sends a third request message to the centralized controller according to the first request message, and the third The request message is used to request the input parameters of the first function and receive the input parameters of the first function from the centralized controller; the first function entity performs the first function according to the first request message, including: the first function entity performs the first function according to the first The input parameters of the signaling semantics and the first function perform the first function. Based on this embodiment, the first functional entity can obtain the input parameters of the first function from the centralized controller, and use the input parameters of the first function to execute the first function indicated by the first signaling semantics, without having to resort to other functional entities and the centralized controller. The controller's signaling interaction is used to obtain the input parameters of the first function, which reduces signaling overhead and is simple and easy to implement.

In a fourth embodiment of the seventh aspect, in combination with the seventh aspect or any one of the embodiments of the seventh aspect, the method further includes: the first functional entity sends to the centralized controller an indication that the first function is successful The response to the first request message executed. Based on this embodiment, after the first functional entity successfully executes the first function, it can notify the centralized controller of the execution result, so that the centralized controller performs subsequent processes according to the execution result of the first functional entity.

In the fifth embodiment of the seventh aspect, in the fourth embodiment in combination with the seventh aspect, the response of the first request message includes third signaling semantics, and the third signaling semantics is used to indicate the third function. Based on this embodiment, when the first functional entity returns the execution result to the centralized controller, it can carry the signaling semantics for indicating the third function in the response of the request message and send it to the centralized controller, so that the centralized controller will receive The signaling semantics is forwarded to the terminal or the access network device, so that the terminal or the access network device works according to the received signaling semantics.

In a sixth embodiment of the seventh aspect, in combination with the fifth embodiment of the seventh aspect, the response of the first request message further includes indication information for indicating the first data of the terminal, and the data indication information is used for Indicating the first data of the terminal; or, the response of the first request message includes the first data of the terminal. Based on this embodiment, when the first functional entity returns the execution result to the centralized controller, it can send the indication information for indicating the data of the terminal or the data of the terminal to the centralized controller, so that the centralized controller will read from the database according to the indication information. Obtain terminal data and send the terminal data to the terminal or access network equipment.

In a seventh embodiment of the seventh aspect, in combination with the seventh aspect or any embodiment of the seventh aspect, the method further includes: the first functional entity sends the output parameter of the first function to the centralized controller. Based on this embodiment, the functional entity can send its output parameters after performing a certain function to the centralized controller, so that the centralized controller stores the received functional reference information in the database, so that other functional entities or devices can share the output parameter.

In the eighth embodiment of the seventh aspect, in combination with the seventh embodiment of the seventh aspect, the output parameter of the first function is carried in the response of the first request message. Based on this embodiment, the functional entity can carry its output parameters after performing a certain function in the response of the request message and send it to the centralized controller, without adding a new message carrying output parameters, reducing signaling overhead and saving network resources .

In an eighth aspect, the present application provides a communication device. The communication device may be a first functional entity or a chip or a system on a chip in the first functional entity. The communication device may implement the above-mentioned seventh aspect or the seventh aspect. The functions performed by the first functional entity in the design can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions. For example, the communication device may include: a receiving unit and an executing unit;

A receiving unit, configured to receive a first request message from the centralized controller for requesting the first functional entity to perform the first function for the terminal;

The execution unit is configured to execute the first function according to the first request message received by the receiving unit.

Based on the method described in the eighth aspect, the communication device can perform the first function under the control of the centralized controller, without interacting with other functional entities, and perform corresponding functions at the request of other functional entities, reducing the interaction between functional entities Complexity.

In a first embodiment of the eighth aspect, with reference to the eighth aspect, the first request message includes first signaling semantics, and the first signaling semantics is used to indicate the first function. Based on this embodiment, the communication device may carry the first signaling semantics in the first request message and send it to the first functional entity, so that the first functional entity triggers the execution of the first function according to the first signaling semantics.

In a second embodiment of the eighth aspect, in combination with the first embodiment of the eighth aspect, the first request message further includes input parameters of the first function; the input parameters of the first function are used by the first functional entity to execute the first function. A function, an execution unit, specifically configured to execute the first function according to the first signaling semantics and the input parameters of the first function. Based on this embodiment, the communication device can perform the first function according to the first signaling semantics and the input parameters of the first function.

In a third embodiment of the eighth aspect, in combination with the first embodiment of the eighth aspect, the communication device further includes: a sending unit, configured to send a third request message to the centralized controller according to the first request message , The third request message is used to request input parameters of the first function; the communication group device further includes: a receiving unit, used to receive input parameters of the first function from the centralized controller; The input parameters of the signaling semantics and the first function perform the first function. Based on this embodiment, the communication device can obtain the input parameters of the first function from the centralized controller, and use the input parameters of the first function to perform the first function indicated by the first signaling semantics without resorting to other functional entities and centralized control. The signaling interaction of the controller is used to obtain the input parameters of the first function, which reduces signaling overhead and is simple and easy to implement.

In a fourth embodiment of the eighth aspect, with reference to the eighth aspect or any one of the embodiments of the eighth aspect, the communication device further includes: a sending unit, configured to send to the centralized controller the first function The response to the first request message that was successfully executed. Based on this embodiment, after the communication device successfully executes the first function, it can notify the centralized controller of the execution result, so that the centralized controller performs the subsequent process according to the execution result of the first functional entity.

In the fifth embodiment of the eighth aspect, in the fourth embodiment of the eighth aspect, the response of the first request message includes third signaling semantics, and the third signaling semantics is used to indicate the third function. Based on this embodiment, when the communication device returns the execution result to the centralized controller, it can carry the signaling semantics for indicating the third function in the response of the request message and send it to the centralized controller, so that the centralized controller will receive The signaling semantics are forwarded to the terminal or the access network device, so that the terminal or the access network device performs work according to the received signaling semantics.

In the sixth embodiment of the eighth aspect, in combination with the fifth embodiment of the eighth aspect, the response of the first request message further includes indication information for indicating the first data of the terminal, and the data indication information is used for Indicating the first data of the terminal; or, the response of the first request message includes the first data of the terminal. Based on this embodiment, when the communication device returns the execution result to the centralized controller, it can send the indication information for indicating the terminal data or the data of the terminal to the centralized controller, so that the centralized controller will retrieve the data from the database according to the indication information. Obtain terminal data, and send the terminal data to the terminal or access network equipment.

In a seventh embodiment of the eighth aspect, with reference to the eighth aspect or any embodiment of the eighth aspect, the communication device further includes: a sending unit configured to send the output parameter of the first function to the centralized controller. Based on this embodiment, the communication device can send its output parameters after performing a certain function to the centralized controller, so that the centralized controller stores the received function reference information in the database, so that other functional entities or devices can share the Output parameters.

In the eighth embodiment of the eighth aspect, in combination with the seventh embodiment of the eighth aspect, the output parameter of the first function is carried in the response of the first request message. Based on this embodiment, the communication device can carry its output parameters after performing a certain function in the response of the request message and send it to the centralized controller, without adding a new message carrying output parameters, reducing signaling overhead and saving network Resources.

In a ninth aspect, a communication device is provided, including: a processor and a memory; the memory is used to store computer execution instructions, and when the communication device is running, the processor executes the computer execution instructions stored in the memory to enable the The communication device executes the communication method described in the seventh aspect or any one of the possible designs of the seventh aspect.

In a tenth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores instructions that, when run on a computer, enable the computer to execute the seventh aspect or any of the above aspects. Design the described communication method.

In an eleventh aspect, a computer program product containing instructions is provided, when it runs on a computer, the computer can execute the communication method described in the seventh aspect or any one of the possible designs of the foregoing aspects.

In a twelfth aspect, a chip system is provided. The chip system includes a processor and a communication interface for supporting the communication device to implement the functions involved in the above aspects. For example, the processor receives the In the first request message requesting the first functional entity to execute the first function for the terminal, the first function is executed according to the first request message received by the receiving unit. In a possible design, the chip system further includes a memory, and the memory is used to store necessary program instructions and data of the communication device. The chip system can be composed of chips, or include chips and other discrete devices.

Among them, the technical effects brought about by any one of the ninth aspect to the twelfth aspect can be referred to the technical effects brought about by any possible design of the seventh aspect or the seventh aspect, and will not be repeated.

In a thirteenth aspect, a communication system is provided, including the centralized controller according to any one of the second aspect to the sixth aspect, and the first functional entity according to any one of the eighth aspect to the twelfth aspect , The second functional entity and the terminal; or, including the centralized controller according to any one of the second aspect to the sixth aspect, the first functional entity according to any one of the eighth aspect to the twelfth aspect, The second functional entity, access network equipment and terminal.

Description of the drawings

Figure 1 is a schematic diagram of the architecture of a 5G mobile communication network defined by 3GPP;

FIG. 2 is a schematic diagram of a communication system provided by an embodiment of this application;

FIG. 3 is a schematic diagram of the composition of a communication device 300 according to an embodiment of the application;

FIG. 4 is a flowchart of a communication method provided by an embodiment of this application;

FIG. 5 is a schematic diagram of a format of a general message provided by an embodiment of this application;

FIG. 6 is a schematic diagram of a response format of a general message provided by an embodiment of the application;

FIG. 7 is a flowchart of yet another communication method provided by an embodiment of this application;

FIG. 8 is a flowchart of yet another communication method provided by an embodiment of this application;

FIG. 9 is a schematic diagram of the composition of a communication device 90 provided by an embodiment of this application;

FIG. 10 is a schematic diagram of the composition of a communication device 100 provided by an embodiment of this application;

FIG. 11 is a schematic diagram of the composition of a communication system provided by an embodiment of this application;

FIG. 12 is a schematic diagram of the composition of another communication system provided by an embodiment of this application.

detailed description

The implementation of the embodiments of the present application will be described in detail below in conjunction with the accompanying drawings.

FIG. 2 shows an example diagram of a communication network architecture provided by an embodiment of the present application. As shown in Figure 2, the network may include: functional entities, centralized controllers, access network equipment, and terminals. Among them, the functional entities are connected to the centralized controller, there is no direct connection between different functional entities, and the functions of different functional entities are decoupled. The centralized controller is connected with the access network equipment, and the access network equipment is connected with the terminal. In addition, as shown in Figure 2, the centralized controller can also be connected to the terminal and interact directly with the terminal.

Functional entities, which can be called network functions (NF), are used to implement certain specific functions. The functional entity can be an entity that implements a specific function, such as a module or chip that implements a specific function, or a logic unit that implements a specific function. For example, a functional entity can implement an access control function or Modules or chips or logic units for user authentication and authorization functions or policy control functions. The functional entity can be uniquely identified by its identity (ID). Wherein, the identifier can be any combination of letters, Chinese characters, numbers, special characters, etc., and can also be an index or serial number of a functional entity, etc., without limitation. The network function can be an independent device, for example, a functional network element, or a functional module located in a certain functional network element, which is not limited.

The centralized controller may be a private network controller (PNC) or a functional module in the PNC. The centralized controller is mainly responsible for the interaction between the functional entities and the external devices of the PNC (such as access network equipment, terminals), the reading and writing of data in the database, and the decision of the functional entities participating in the signaling process in a specific signaling process For which functional entity, the functional entity that triggers participation in a certain signaling process to work, etc. For example, the centralized controller can receive the message sent by the access network device or terminal, find the functional entity according to the signaling included in the message, and trigger the functional entity to perform the corresponding network function; or the centralized controller can receive the message sent by the functional entity , Forward the received message to the access network device or terminal.

Access network equipment, which can be called a private network access (PNA) node, is mainly used to implement terminal resource scheduling, wireless resource management, and wireless access control functions. Specifically, the PNA may be any of a small base station, a wireless access point, a transmission receive point (TRP) transmission point (TP), and some other access node. In the embodiments of the present application, the device used to implement the function of the access network device may be the access network device, or may be a device or functional module capable of supporting the access network device to implement the function, such as a chip system. In the following, the communication method provided by the embodiments of the present application is described by taking an example in which the device used to implement the function of the access network device is the access network device.

A terminal may be called a terminal equipment (terminal equipment) or a user equipment (UE) or a mobile station (mobile station, MS) or a mobile terminal (mobile terminal, MT), etc. Specifically, the terminal in FIG. 2 can be a mobile phone, a tablet computer, or a computer with wireless transceiver function, it can also be a virtual reality (VR) terminal, an augmented reality (AR) terminal, an industrial Wireless terminals in control, wireless terminals in unmanned driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in smart cities, smart homes, vehicle terminals, etc. In the embodiments of the present application, the device for implementing the function of the terminal may be a terminal, or a device capable of supporting the terminal to implement the function, such as a chip system. In the following, the communication method provided by the embodiment of the present application will be described by taking an example in which the device for implementing the function of the terminal is a terminal.

In addition, the communication network shown in FIG. 2 may also include a database. In an example, the database is independently deployed in the network shown in FIG. 2 and is connected to the centralized controller and various functional entities. In another example, the database may be integrated in a centralized controller, for example, integrated in the memory of the centralized controller, without limitation. In the following, the method provided by the embodiment of the present application will be described by taking the independent deployment of the database in the network shown in FIG. 2 as an example.

Specifically, the database in FIG. 2 is mainly responsible for the storage of data required by all functional entities in the network shown in FIG. 2 when they work. For example, the database can store terminal status data (for example, registration status, connection status, authentication result), terminal context data (for example, mobility management information, session management information, security information, etc.), message data, and terminal Contract data and network management data. Each functional entity can directly read the required data from the database, and write the new data generated by itself after performing related operations into the database, or each functional entity can read the required data from the database through the centralized controller Data, and write the new data generated after performing related operations into the database through the centralized controller.

It should be noted that Figure 2 is only an exemplary architecture diagram. For example, in the actual application process, the number of devices involved in Figure 2 can be increased or decreased, such as the deployment of the functional entities in Figure 2 (such as: deployment Quantity, etc.) can be dynamically updated according to the update of enterprise network construction requirements, increase or decrease in the number of enterprise users, etc., that is, functional entities can be deployed on demand. For example, when an enterprise requires a certain network function to be added, a functional entity capable of performing the newly added network function can be deployed to the network, and at the same time, a communication interface for connecting the functional entity and other information can be configured on the centralized controller , To realize the communication connection between the functional entity and the centralized controller. Or, when a deployed functional entity is not used for a long time, it means that the network function corresponding to the functional entity is not needed by enterprise users. At this time, the network operation and maintenance personnel can disconnect the communication connection between the functional entity and the centralized controller , And delete the functional entity from the network.

In addition to the devices shown in FIG. 2, the network described in FIG. 2 may also include other devices, for example, it may also include a monitoring module, which is used to monitor the working status of each device in the network. In addition, the name of each device in FIG. 2 is not limited. In addition to the name shown in FIG. 2, each device can also be named with other names, such as replacing the name of a network element with the same or similar functions, without limitation.

In specific implementation, each device (such as a centralized controller, functional entity, etc.) shown in FIG. 2 may adopt the composition structure shown in FIG. 3 or include the components shown in FIG. 3.

3 is a schematic diagram of the composition of a communication device 300 provided by an embodiment of the application. The communication device 300 may be a centralized controller or a chip or a system on a chip in a centralized controller, and may also be a functional entity or a chip or a chip in a functional entity. System on chip. The communication device 300 includes a processor 301, a communication line 302, and a communication interface 303.

Further, the communication device 300 may further include a memory 304. Wherein, the processor 301, the memory 304, and the communication interface 303 may be connected through a communication line 302.

Among them, the processor 301 may be a central processing unit (CPU), a network processor (NP), a digital signal processor (DSP), a microprocessor, or a microcontroller. , Programmable logic device (PLD) or any combination of them. The processor 301 may also be any other device with processing functions, such as a circuit, a device, or a software module, without limitation.

The communication line 302 is used to transmit information between the components included in the communication device 300.

The communication interface 303 is used to communicate with other devices or other communication networks. The other communication network may be Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc. The communication interface 303 may be a module, a circuit, a transceiver or any device capable of implementing communication.

The memory 304 is used to store instructions. Among them, the instructions can be computer programs.

Wherein, the memory 304 may be a read-only memory (read-only memory, ROM) or other types of static storage devices that can store static information and/or instructions, or it may be a random access memory (random access memory, RAM) or Other types of dynamic storage devices that store information and/or instructions can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory, CD- ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, etc., are not restricted.

It should be noted that the memory 304 may exist independently of the processor 301, or may be integrated with the processor 301. The memory 304 may be used to store instructions or program codes or some data. The memory 304 may be located in the communication device 300 or outside the communication device 300, without limitation.

The processor 301 is configured to execute instructions stored in the memory 304 to implement the communication method provided in the following embodiments of the present application.

For example, when the communication device 300 is a centralized controller or a chip in a centralized controller or a system on a chip, the processor 301 may execute instructions stored in the memory 304 to implement the steps performed by the centralized controller in the following embodiments of the present application . For another example, when the communication device 300 is a functional entity or a chip or a system on a chip in the functional entity, the processor 301 may execute instructions stored in the memory 304 to implement the steps performed by the functional entity in the following embodiments of the present application.

In an example, the processor 301 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 3.

As an optional implementation manner, the communication device 300 includes multiple processors. For example, in addition to the processor 301 in FIG. 3, it may also include a processor 307.

As an optional implementation manner, the communication apparatus 300 further includes an output device 305 and an input device 306. Exemplarily, the input device 306 is a device such as a keyboard, a mouse, a microphone or a joystick, and the output device 305 is a device such as a display screen and a speaker.

It should be noted that the communication device 300 may be a desktop computer, a portable computer, a network server, a mobile phone, a tablet computer, a wireless terminal, an embedded device, a chip system, or a device with a similar structure in FIG. 3. In addition, the composition structure shown in FIG. 3 does not constitute a limitation on the communication device. In addition to the components shown in FIG. 3, the communication device may include more or less components than those shown in the figure, or combine certain components. , Or different component arrangements.

In the embodiments of the present application, the chip system may be composed of chips, or may include chips and other discrete devices.

In addition, the actions, terms, etc. involved in the various embodiments of the present application can be referred to each other, and are not limited. The name of the message or the name of the parameter in the message in the embodiment of the present application is only an example, and other names may also be used in specific implementations, which are not limited. For example, the general messages in the following embodiments can also be replaced with processing messages, etc., which is not limited.

The following uses the architecture shown in FIG. 2 as an example to describe the communication method provided in the embodiment of the present application.

FIG. 4 is a communication method provided by an embodiment of the application. As shown in FIG. 4, it may include:

Step 401: The centralized controller receives the general message.

Among them, the centralized controller may be a centralized controller in the network shown in FIG. 2.

Wherein, the general message may include the identification of the terminal, the first function reference information and the second function reference information; or, it may include the first function reference information and the second function reference information, but does not include the identification of the terminal.

The identification of the terminal may be used to identify the terminal, and the terminal may be any terminal in the architecture shown in FIG. 2. The terminal’s identity can be the terminal’s permanent identity, for example, the terminal’s international mobile subscriber identity (IMSI); it can also be the terminal’s temporary identity, for example, the globally unique temporary identity of the terminal. , GUTI); It can also be the application layer identifier of the terminal, for example, application user ID; it can also be the identifier assigned by the interface protocol between network elements, for example, the fully qualified domain name assigned by the hypertext transfer protocol (hypertext transfer protocol, HTTP) protocol (fully qualified domain name, FQDN), wireless access point control and configuration protocol (control and provisioning of wireless access points protocol, CAPWAP) assigned identifier, general packet radio service technology (general packet radio service, GPRS) tunnel protocol ( GPRS tunnelling protocol (GTP) assigned identifier, Diameter protocol assigned identifier, etc.

The first function reference information may be used to indicate the first function.

Among them, the first function may refer to one or more network functions implemented by a certain functional entity. The network function can be divided according to the needs of the operator, and the granularity of the network function can be dynamically set. Specifically, the network function may be a large-granularity function, for example, a network registration function, an authentication service function, a session management function, or a policy control function. The network function may also be a small-granularity function, and specifically may be one of multiple sub-functions included in the above-mentioned large-granularity function. For example, the network function is one of the following multiple sub-functions included in the session management function: establishing a packet data unit (PDU) session (session), modifying a PDU session, and rebuilding a PDU session. Taking the network function as the session management function as an example, the first function may be the session management function, and may also be any function of establishing a PDU session, modifying a PDU session, or rebuilding a PDU session. It should be noted that the description of any of the following functions (such as the second function and other functions) can refer to the related description of the first function, and will not be repeated.

The first function reference information may include at least one of the identification of the first function entity and the first signaling semantics.

The identification of the first functional entity may be used to identify the first functional entity used to perform the first function. For example, the identifier of the first functional entity may be the FQDN, name or symbol of the first functional entity, internet protocol (IP) address, or media access control (MAC) address, etc.

The first signaling semantics (signal syntax) may be used to indicate (or identify) the first function. For example, the first signaling semantics can be used to identify the session management function, and can also be used to identify the establishment of a PDU session, which is not limited.

The second function reference information may be used to indicate the second function. The second function may be different from the first function. Specifically, the second function reference information is similar to the first function reference information, and the relevant description of the first function reference information may be referred to, and details are not described again.

It should be noted that the embodiments of the present application do not limit the content included in the general message. For example, in addition to the terminal identifier, the first function reference information, and the second function reference information, the general message may also include other information (message header, Cell pointer and cell, etc.). Among them, the several achievable ways for the centralized controller to receive the general message can refer to the first scenario of the method shown in FIG. 4. In addition, the format of the general message can refer to FIG. 5, but the embodiment of the application does not limit the general message. format.

Step 402: The centralized controller sends a first request message to the first functional entity according to the first function reference information and the terminal identifier; the centralized controller sends a second request message to the second functional entity according to the second function reference information and the terminal identifier. Request message.

Among them, both the first functional entity and the second functional entity may be the functional entities in FIG. 2.

The first request message may be used to request the first functional entity to perform the first function for the terminal. The second request message may be used to request the second functional entity to perform the second function for the terminal.

Optionally, the first request message includes indication information of the terminal, or indication information of the terminal and first signaling semantics, and further, may also include other information, for example, input parameters of the first function, input of the first function The parameters can be used by the first functional entity to perform the first function.

Optionally, the second request message includes indication information of the terminal, or indication information of the terminal and the second signaling semantics, and further, may also include other information, for example, input parameters of the second function, input of the second function The parameters can be used by the second functional entity to perform the second function.

It should be noted that the indication information of the terminal may be used to indicate the terminal. Specifically, the indication information of the terminal may be the identifier of the terminal in the above general message. For example, the identifier of the terminal in the general message is the subscriber permanent identifier (SUPI) of the terminal, or it may be a corresponding relationship with the terminal. Information, for example, the protocol identifier assigned to the terminal in the interface protocol between the centralized controller and the functional entity.

Specifically, in step 402, the centralized controller sending the first request message to the first functional entity according to the first function reference information and the terminal identifier may include: the centralized controller obtains the first function reference information and the terminal identifier from the general message When the centralized controller determines to trigger the first functional entity to perform the first function according to the first function reference information, it sends the first request message to the first functional entity. The first request message may carry the identification of the terminal and part of the information included in the first function reference information, for example, may carry the first signaling semantics included in the first function reference information.

Wherein, the centralized controller determines that triggering the first functional entity to perform the first function according to the first function reference information can adopt the following methods:

Manner 1: When the first function reference information includes the identification of the first functional entity, the centralized controller determines to trigger the first functional entity identified by the identification of the first functional entity to perform the first function.

Manner 2: When the first function reference information includes the first signaling semantics, and the first signaling semantics is used to indicate the first function, the centralized controller determines to trigger the first function based on the corresponding relationship between the function and the functional entity. The corresponding first functional entity performs the first function.

Among them, the correspondence between functional entities and functions may be pre-configured in the centralized controller, and one type of functional entity may correspond to one or more functions.

For example, taking the functional entity as NF as an example, Table 1 below shows the correspondence between the functional entity and the functions implemented by the functional entity. As shown in Table 1, NF1 can implement the network registration function, and NF2 can implement the PDU session establishment function. , NF3 can realize the session management function. Assuming that the first function parameter information includes the first signaling semantics, and the first signaling semantics is used to indicate the "session management function", the centralized controller can use the "session management function" as the index to look up Table 1, and determine " The NF corresponding to the "session management function" is NF2, that is, it is determined that NF2 will perform the session management function, and the first request message is sent to NF2 to request NF3 to perform the session management function. Assuming that the first signaling semantics is used to indicate the "network registration function", the centralized controller can use the "network registration function" as an index to look up Table 1, and determine from Table 1 that the NF corresponding to the "network registration function" is NF1, that is, it is determined by NF1 performs the network registration function, and sends a first request message to NF1 to request NF1 to perform the network registration function.

Table I

功能Features	NFNF
网络注册功能Network registration function	NF1NF1
会话管理功能Session management function	NF2NF2
认证服务功能Authentication service function	NF3NF3

Manner 3: When the first function reference information includes the identification of the first functional entity and the first signaling semantics, and the first signaling semantics is used to indicate the first function, the centralized controller determines to trigger the identification of the first functional entity The first functional entity performs the first function indicated by the first signaling semantics.

In the following, it is assumed that NF1 has a session management function, the function indicated by the first signaling semantics is "Establish PDU session", the identifier of NF1 is NF ID1, and the correspondence between functional entities and functions is shown in Table 1 as an example. In one manner, the first function reference information includes NF ID1, and the centralized controller may determine to trigger the NF1 identified by NF ID1 to perform the session management function. In another manner, if the first function reference information includes the first signaling semantics, the centralized controller may use the corresponding relationship between the functional entities and functions shown in Table 1 above, and the " Establish PDU session" function, determine to trigger NF1 to establish PDU session. In another manner, the first function reference information includes the first signaling semantics and NF ID1, and the centralized controller may determine to trigger the NF1 identified by NF ID1 to perform the establishment of the PDU session indicated by the first signaling semantics.

Similar to sending the first request message, the centralized controller sends the second request message to the second functional entity according to the second function reference information, and may refer to the centralized controller to send the first request message to the first functional entity according to the first function reference information. The related description of, will not repeat it.

It should be noted that the centralized controller may simultaneously perform the actions of sending the first request message to the first functional entity and sending the second request message to the second functional entity, or may first execute the action of sending the first request message to the first functional entity. The action of sending the second request message to the second functional entity is performed again, which is not limited. In addition, the above "simultaneous execution" allows a certain time difference, for example, the difference between the two is 1 millisecond.

Among them, the centralized controller may execute the action of sending request messages to each functional entity according to the time sequence of each functional entity executing the function. For example, the first function is PDU session establishment, and the second function is PDU session release. Since the PDU session establishment is prior to the PDU session release in time sequence, the centralized controller first performs the action of sending the first request message to the first functional entity. Then the action of sending the second request message to the second functional entity is executed.

Specifically, for the centralized controller to execute the action of sending the request message to each functional entity according to the time sequence of each functional entity executing the function, refer to the second scenario of the method shown in FIG. 4.

Step 403: The first functional entity receives the first request message from the centralized controller, and executes the first function according to the first request message.

The first request message may be used as a trigger condition for the first functional entity to execute the first function. For example, the first functional entity executes the first function upon receiving the first request message.

Obviously, the first functional entity may also perform the first function according to the information carried in the first request message.

For example, when the first request message includes the indication information of the terminal, the first request message can be used as a trigger condition for the first functional entity to perform the first function. After receiving the first request message, the first functional entity can follow the instructions of the terminal The information is that the terminal performs the first function.

For another example, when the first request message includes the indication information of the terminal and the first signaling semantics, the first functional entity executes the first signal indicated by the first signaling semantics for the terminal according to the indication information of the terminal and the first signaling semantics. Features.

Specifically, the first functional entity may execute the first function for the terminal according to the input parameters of the first function. The first functional entity may obtain the input parameters of the first function in several ways described in the fourth scenario of the method shown in FIG. 4 below.

Step 404: The second functional entity receives the second request message from the centralized controller, and executes the second function according to the second request message.

Wherein, the process of performing step 404 by the second functional entity can refer to the process of performing the first function by the first functional entity in step 403, which is not repeated here.

It should be noted that the method shown in Figure 4 only takes the first functional entity to perform the first function and the second functional entity to perform the second function as an example for description. If the network shown in Figure 2 includes the first functional entity and the second function In addition to entities, it also includes two or more functional entities such as a third functional entity and a fourth functional entity. The third functional entity is used to perform the third function, and the fourth functional entity is used to perform the fourth function. The four functions are similar to the aforementioned first function, and the method shown in FIG. 4 also includes the centralized controller triggering the two or more functional entities to perform corresponding functions. For example, the general message also includes the third function reference information and the fourth function reference information. The centralized controller sends a request message to the third function entity according to the third function reference information to request the execution of the third function. The reference information sends a request message to the fourth functional entity to request the execution of the fourth function. For specific details, refer to the description in FIG. 4 and will not be repeated.

Based on the method shown in FIG. 4, the centralized controller can request multiple functional entities to perform multiple functions for the terminal according to multiple function reference information carried in the general message. Compared with performing multiple functions for the terminal through signaling interaction between network functions in the prior art, signaling overhead can be reduced, network resources are saved, and efficiency is improved.

Optionally, in the first scenario of the method shown in FIG. 4, the general message received by the centralized controller includes the following examples:

Example 1: The centralized controller receives general messages from the terminal. For example, when the terminal determines to trigger the execution of the first function and the second function, the terminal can encapsulate the terminal’s identity, the first function reference information, and the second function reference information in a general message, and pass the communication between the terminal and the centralized controller. The communication link sends general messages to the centralized controller.

Example 2: The centralized controller receives general messages from the access network equipment. For example: when the access network device determines that the terminal triggers the first function and the second function, the access network device can encapsulate the terminal's identity, the first function reference information, and the second function reference information in a general message, and the general The message is sent to the centralized controller through the communication link between the access network device and the centralized controller. For another example, the access network device generates the general message according to the request message from the terminal, and the general message includes the identification of the terminal, the first function reference information, and the second function reference information. The request message from the terminal can be a message, for example, the request message is used to request a certain service, or to request the execution of the first function and/or the second function; it can also be two independent messages, for example, a request message for The first function is requested, and another message is used to request the second function.

Wherein, determining that the access network device triggers the first function and the second function for the terminal may include: the terminal sends its own network requirements (such as requirements for realizing the first function and the second function) to the access network device, and access The network equipment determines that the terminal triggers the first function and the second function according to the network requirements of the terminal.

Example 3: The centralized controller receives general messages sent by the terminal through the access network device. For example, when the terminal determines to trigger the execution of the first function and the second function, the terminal can encapsulate the terminal's identity, the first function reference information, and the second function reference information in a general message and send it to the access network device. The general message is sent to the centralized controller through the communication link between the access network device and the centralized controller.

It should be noted that in Example 3, the terminal's identity may not be included in the general message. For example, there may be an underlying protocol established for the terminal between the access network device and the centralized controller, and the access network device may use the underlying protocol Encapsulate the received general message to generate a signaling message, and send the generated signaling message to the centralized controller, that is, the access network device can carry the received general message on the underlying protocol established for the terminal and send it to the centralized controller. Controller. Wherein, the payload of the signaling message may include a general message. In order to facilitate the centralized controller to recognize that the general message is a general message sent by the terminal, the part of the signaling message except the payload may include a low-level protocol for terminal allocation The identifiers of, such as: FQDN assigned by the HTTP protocol, identifier assigned by CAPWAP, identifier assigned by GTP, identifier assigned by Diameter protocol, etc.

Optionally, the general message in the method shown in FIG. 4 adopts the format shown in FIG. 5. As shown in Figure 5, the general message may include a message header and multiple signaling headers. Further, it may also include multiple cells.

Among them, the message header may include a version number (or protocol version number), a security header, a serial number, and an identification of the terminal.

The version number may be used to indicate the protocol version used to send the general message, where the protocol version may be Internet protocol version 4 (IPV4), IPV6, and so on.

The security header may include a security header type (security header type) and/or a message authentication code (message authentication code). The security header type can be used to indicate the security protection mode of the general message. The message verification code may be a check value, which may be a check value generated by performing an integrity protection operation on a general message with a security key. The sequence number can be the sequence number of a general message.

The signaling header may include function reference information, for example, the aforementioned first function reference information. The function reference information can be used to indicate a certain function. Further, the signaling header may also include cell pointers. The cell pointer can be used to indicate the position of the cell carrying the input parameter of a certain function in the general message, and the cell pointer included in different signaling headers can indicate that the cell carrying the input parameter of the different function is in the general message. s position. Different signaling headers include different functional reference information. The positions indicated by the cell pointers included in different signaling headers can be the same or different. When the positions indicated by the cell pointers included in different signaling headers are the same, they indicate different functions. The input parameters are carried in the same cell, and the input parameters of different functions can be the same.

For example, as shown in FIG. 5, the first signaling header includes first function reference information and a first cell pointer, and the second signaling header includes second function reference information and a second cell pointer. The first function reference information is different from the second function reference information. The first function reference information includes the identification of the first functional entity and the first signaling semantics, and the second function reference information includes the identification of the second functional entity and the second signaling semantics . The first cell pointer is used to indicate the position of the cell carrying the input parameter of the first function (cell a in Figure 5) in the general message, and the second cell pointer is used to indicate the input parameter carrying the second function. The position of the cell (cell c in Figure 5) in the general message. If the first cell pointer and the second cell pointer both indicate the location of cell b, it indicates that the input parameters of the first function and the input parameters of the second function are carried in cell b, and the first function and the second function The input parameters of the function can be the same.

It should be noted that the signaling header may include one or more cell pointers, and one cell pointer may be used to indicate the position of one or more cells in the notification message. All cell pointers included in the same signaling header indicate The cells at the position include input parameters of the same function. For example, when the first signaling header includes the first signaling semantics and multiple cell pointers, and the first signaling semantics is used to indicate the first function, all cell pointers included in the first signaling header indicate the The position of the cell of the input parameter of the function in the general message.

The information element may include input parameters of one or more functions, and the input parameters may be understood as parameters required by the functional entity to perform the function. For example, the parameters required for the first functional entity to perform the first function may be input parameters for the first function, and the parameters required for the second functional entity to perform the second function may be input parameters for the second function. The input parameters of the same function may include one or more parameters, and one cell may include one input parameter of the function, or may include some or all of the multiple input parameters of the function, without limitation.

For example, if the input parameters of the first function include single network slice selection assistance information (S-NSSAI(s)), data network name (data network name, DNN), PDU session identification (indentity, ID) ) And request type. These input parameters can be included in the same cell, or S-NSSAI(s) and DNN are in the first cell of the notification message, and the PDU session ID and request type can be included in the notification In the second cell of the message, or each input parameter is separately located in a cell of the notification message, there is no restriction.

For another example, suppose that the first functional entity has the first function, the first function is the session management function, the first signaling semantics is used to indicate the establishment of a PDU session, and the first cell pointer is used to indicate the input parameters containing the first function The position of the cell in the general message. The input parameters of the first function include S-NSSAI(s), DNN, PDU session ID, and request type. If S-NSSAI(s) is included in the first cell in the general message, DNN is included in the third cell in the general message, the PDU session ID is included in the fourth cell in the general message, and the request type is included in the general message The sixth cell in the general message, and the first cell is located in the 19-50th bit of the general message, the third cell is located in the 59-80th bit of the general message, and the fourth cell is in the general message. The 81st-96th bit (bit) of the message, the sixth cell is located at the 105th-106th bit (bit) of the general message, then the first cell pointer can point to the 19th-50th bit (bit), 59th -80 bit (bit) bit, 81-96 bit (bit) bit, 105-106 bit (bit) bit. If S-NSSAI(s), DNN, PDU session ID, and request type are included in the first cell of the general message, and the first cell is located in the 19th-105th bit (bit) of the general message, the first message The meta pointer can be bits 19-105.

In yet another possible implementation manner, the cell pointer is used to indicate the position of the input parameter of a certain function in the database.

Specifically, the cell pointer may be the name of the input parameter of a certain function or the identifier of the input parameter of a certain function, and may also be the specific value of the input parameter of a certain function.

It should be noted that a certain function mentioned above may refer to the first function or the second function, and is not limited.

For example, suppose that the first function is the network registration function, and the input parameter of the first function is the service mode of the terminal contract. Among them, the service mode of the terminal contract can be mobile initiated connection only (MICO) service/vehicle to X (V2X) service. Taking the V2X service as an example, it can be used to indicate whether the terminal subscribes to the V2X service The indication information contained in a certain cell in the general message is sent to the centralized controller, and the general message includes a cell pointer indicating the position of the cell in the general message. After the centralized controller receives the general message, The cell pointer is obtained from the general message, the cell is obtained from the position indicated by the cell pointer, and the indication information used to indicate whether the terminal subscribes to the V2X service is read from the cell. If the V2X service is subscribed, the terminal is subscribed to V2X The service information is sent to the first function as the input parameter of the first function, so that the first function can query the subscription data of the terminal in the database after learning that the terminal has subscribed to the V2X service, and obtain the information related to the V2X mode from the subscription data. And perform network registration for the terminal according to the obtained information related to the V2X service. The value of the indication information of whether the terminal subscribes to the V2X service is "0" or "1", "1" represents the V2X service contracted, and "0" represents the V2X service not contracted.

For another example, suppose the first function is the mobility management function, the input parameter of the first function is the discontinuous reception (DRX) parameter of the terminal, the cell pointer may be the name of the DRX parameter, and the name of the DRX parameter is It can be described as the type of the DRX parameter, and the centralized controller can obtain the value corresponding to the DRX from the database according to the name of the DRX parameter.

For another example, suppose that the first function is a session management function, and the input parameters of the first function include related parameters of PDU session. Since the terminal may have multiple PDU sessions at the same time, in order to indicate which PDU session it is, the cell pointer may be PDU session ID, such as: PDU session ID3.

It should be noted that FIG. 5 is only an exemplary drawing. In addition to the content shown in FIG. 5, the general message may also include other content, and part of the content may also be reduced on the basis of FIG. 5. For example, in actual applications, The signaling header included in the general message shown in Figure 5 can be increased or decreased without limitation.

Using the message format shown in Figure 5 can increase the scalability of the protocol, save the number of signaling interactions, and avoid repeated transmission of cells.

Optionally, in the second scenario of the method shown in FIG. 4, the centralized controller executes the action of sending request messages to each functional entity according to the time sequence of each functional entity executing the function, including:

When the sequence relationship between the first function and the second function is parallel, the first request message and the second request message are sent by the centralized controller at the same time; or,

When the timing relationship between the first function and the second function is: serial, and the timing of the first request message has priority over the second request message, the second request message is sent by the centralized controller when the first request message is received. Sent after the response; or,

When the timing relationship between the first function and the second function is: serial, and the timing of the second request message has priority over the first request message, the first request message is sent by the centralized controller when the second request message is received. Sent after the response.

Among them, "the first request message and the second request message are sent by the centralized controller at the same time" may mean: the centralized controller can send the first request message to the first functional entity and the second request message to the second functional entity at the same time. Request message. The above "simultaneous sending" allows a certain time difference, for example, the difference between the two is 1 millisecond.

The centralized controller may determine the first function according to the first function reference information and the second function reference information before the centralized controller sends the first request message to the first functional entity and the second request message to the second functional entity. The timing relationship with the second function; specifically, the centralized controller determines the timing relationship between the first function and the second function according to the first function reference information and the second function reference information, and the following implementation manners may be adopted.

Method 1: If the second functional entity performs the second function and the first functional entity performs the first function without affecting each other, the timing relationship between the first function and the second function is parallel, that is, the first request message and the second request Can be sent at the same time.

Among them, if the input parameters required by the second functional entity to perform the second function are completely independent of the output parameters generated by the first functional entity after performing the first function, and the input parameters required by the first functional entity to perform the first function are completely Without relying on the output parameters generated by the second functional entity after executing the second function, it can be understood that the second functional entity performing the second function and the first functional entity performing the first function do not affect each other.

Method 2: If the second functional entity performs the second function based on the successful execution of the first function by the first functional entity, or if the first functional entity performs the first function, it is based on the successful execution of the second functional entity On the basis of the second function, the sequence relationship between the first function and the second function is serial.

In an example, the input parameters required by the second functional entity to perform the second function depend on the output parameters generated by the first functional entity after executing the first function, and the sequence of the first request message takes precedence over the second request message, and centralized control The device may send the second request message after receiving the response of the first request message.

In another example, the input parameters required by the first functional entity to perform the first function depend on the output parameters generated by the second functional entity after performing the second function, and the timing of the second request message takes precedence over the first request message, and The controller may send the first request message after receiving the response of the second request message.

Assume that NF1 performs the first function, and NF2 performs the second function. The first function is to update the trace area list (TAL), and the second function is to establish a PDU session. Since the TAL update belongs to the mobility management function, the establishment of the PDU session belongs to the session management function, and the two functions do not affect each other. Therefore, the centralized controller can simultaneously send the first request message to NF1 and the second request message to NF2. action.

Assume that NF1 performs the first function, NF2 performs the second function, and the first function is third-party authentication in mobility management, and the second function is the establishment of PDU sessions in the session management function. Since the establishment of the PDU session can only be performed after the third-party authentication is successful, the centralized controller first executes the action of sending the first request message to NF1, and then executes the action of sending the second request message to NF2.

Optionally, in the third scenario of the embodiment shown in FIG. 4, after step 403, the above method further includes:

When the first functional entity successfully executes the first function, the first functional entity sends a response to the first request message to the centralized controller, and the response to the first request message is used to indicate that the first function is successfully executed; or,

When the first functional entity fails to perform the first function successfully, the first functional entity sends a response of the first request message to the centralized controller, and the response of the first request message is used to indicate that the first functional entity fails to perform the first function.

Correspondingly, the centralized controller receives the response of the first request message from the first functional entity.

It should be noted that, when the first functional entity fails to execute the first function successfully, the first functional entity may not send a response to the first request message to the centralized controller. Correspondingly, if the centralized controller does not receive the response of the first functional entity sending the first request message within the preset time, it is determined that the first functional entity has not successfully performed the first function. Among them, the preset time can be set according to needs without limitation.

The response of the first request message may include third signaling semantics, and the third signaling semantics may be used to indicate (or identify) the third function.

Further, after the centralized controller receives the response of the first request message sent by the first functional entity, the above method may further include: the centralized controller obtains the third signaling semantics from the response of the first request message, and sends the Three signaling semantics. Among them, when the centralized controller receives the general message sent by the terminal in the first scenario of the method shown in FIG. 4, the centralized controller sends the third signaling semantics to the terminal; when in the first scenario of the method shown in FIG. 4 When the centralized controller receives the general message sent by the access network device, the centralized controller sends the third signaling semantics to the access network device.

Suppose that the first request message is used to request NF1 to perform the first function, and the first function is to establish a PDU session. After the PDU session is established, the terminal will perform a third-party authentication function. Therefore, when the NF1 receives the first request message, the PDU is successfully established After the session, the NF1 may send a response to the first request message to the centralized controller, where the response of the first request message may include the third signaling semantics for indicating the "third-party authentication function". Correspondingly, after receiving the response of the first request message, the centralized controller may send the third signaling semantics to the terminal, so that the terminal performs the third-party authentication function according to the third signaling semantics.

Optionally, the response of the first request message further includes other information, such as: the first data of the terminal, or data indication information used to indicate the first data of the terminal, etc., which is not limited.

The first data of the terminal may be a parameter required by the terminal or the access network device to perform the third function, that is, the input parameter of the third function. For example, if the third function is a "third-party authentication function", the first data of the terminal may be some application layer security parameters, such as application identifier (APP ID), server certificate, and so on. Further, when the response of the first request message includes the first data of the terminal, the centralized controller may obtain the first data of the terminal from the response of the first request message, and send the first data of the terminal to the terminal so that the terminal can follow The first data performs the third function.

The data indication information may be the identification of the terminal or the identification of the first data of the terminal or the name of the first data of the terminal. When the response of the first request message includes data indication information for indicating the first data of the terminal, the centralized controller may obtain the first data of the terminal from the database according to the data indication information included in the response of the first request message, and The first data of the terminal is sent to the terminal, so that the terminal performs the third function according to the first data of the terminal.

It should be noted that, in addition to the above methods, the centralized controller can also obtain the first data of the terminal in other ways. For example, the centralized controller can determine to trigger the third function according to the third signaling semantics, and according to the function and the input of the function The corresponding relationship between the parameters determines the input parameter corresponding to the third function, that is, the first data of the terminal, and sends the first data of the terminal to the terminal, so that the terminal performs the third function according to the first data of the terminal. Among them, the function and the corresponding relationship between the input parameters of the function can be pre-configured to the centralized controller.

For example, suppose the response of the first request message only includes the third signaling semantics, and the third signaling semantics is used to indicate the "third-party authentication function". After receiving the response of the first request message, the centralized controller may use the third The signaling semantics determines the triggering of the third-party authentication function, and determines the input parameters of the third function according to the corresponding relationship between the function and the input parameters of the function, such as application identifier (APP ID) and server certificate, etc., will determine The input parameters of the third function of the terminal are sent to the terminal so that the terminal executes the third function according to the first data of the terminal.

Similar to the first functional entity, after step 404, the second functional entity may also send a response to the second request message to the centralized controller. For example, when the second functional entity successfully executes the second function, the second functional entity sends a message to the centralized controller. The controller sends a response to the second request message, and the response to the second request message is used to indicate that the second functional entity successfully performs the second function; or, when the second functional entity fails to perform the second function successfully, the second functional entity sends the The controller sends a response to the second request message, and the response to the second request message is used to indicate that the second functional entity fails to perform the second function.

Correspondingly, the centralized controller receives the response of the second request message from the second functional entity.

The response of the second request message may include fourth signaling semantics, and the fourth signaling semantics may be used to indicate (or identify) the fourth function. The response of the second request message may also include other information, such as: the second data of the terminal or the data indication information used to indicate the second data of the terminal and other information. The second data of the terminal may be an input parameter of the fourth function.

Further, after receiving the response of the second request message, the centralized controller may send the information included in the response of the second request message (such as the fourth signaling semantics, the second data of the terminal) to the terminal or the access network device .

Specifically, for the execution process of the second functional entity, refer to the execution process of the first functional entity in the third scenario shown in FIG. 4, and details are not described herein again.

In an implementation manner, the centralized controller may carry the content included in the response of each request message in multiple independent messages and send it out. For example, in the first scenario of the method shown in FIG. 4, when the centralized controller receives a general message from the terminal, the centralized controller may carry the content included in the response of the first request message in the first message and send it to the terminal. , The content included in the response of the second request message is carried in the second message and sent to the terminal; or, in the first scenario of the method shown in FIG. 4, when the centralized controller receives the general message from the access network device The centralized controller may carry the content included in the response of the first request message in the first message and send it to the access network device, and carry the content included in the response of the second request message in the second message and send it to the access network device. . The first message and the second message are two independent messages.

In another implementation manner, in order to save signaling overhead, the centralized controller may carry the content of the response of the request message sent by multiple functional entities together in the same message (such as the response of the general message) and send it out, such as: In the first scenario of the method shown in Figure 4, when the centralized controller receives a general message from the terminal, the centralized controller will send it to the terminal; in the first scenario of the method shown in Figure 4, when the centralized controller When receiving a general message from an access network device, the centralized controller sends the content in the response of the request message sent by multiple functional entities to the access network device in a response that contains the general message together.

For example, taking the response of the first request message including the third signaling semantics and the response of the second request message including the fourth signaling semantics as an example, the centralized controller can carry the third signaling semantics and the fourth signaling semantics together in The response of the general message is sent to the terminal or the access network device. Taking the response of the first request message including the third signaling semantics and the first data of the terminal, and the response of the second request message including the fourth signaling semantics and the second data of the terminal as an example, the centralized controller can transfer the third signaling The semantics, the fourth signaling semantics, the first data of the terminal, and the second data of the terminal are jointly carried in the response of the general message and sent to the terminal or the access network device.

Exemplarily, the response of the general message adopts the format shown in FIG. 6, that is, multiple signaling semantics and multiple data of the terminal are encapsulated in the response of the general message.

Fig. 6 is a schematic diagram of the format of the response of the general message. As shown in Fig. 6, the response of the general message may include a message header and multiple signaling headers. Further, it may also include multiple cells.

For the message header, reference may be made to the related description of the message header shown in FIG. 5, which will not be repeated.

The signaling header may include signaling semantics. The cell semantics, as shown above, can be used to indicate (or identify) a certain function. For example, the third signaling semantics is used to indicate the third function, and the fourth signaling semantics is used to indicate the fourth function. The semantics of cells included in different signaling headers are different.

Further, the signaling header may also include one or more cell pointers. The cell pointer may be used to indicate the position of one or more cells carrying data of the terminal (such as the first data of the terminal and the second data of the terminal) in the response of the general message. The cell pointers included in different signaling headers can indicate the positions of cells carrying input parameters of different functions in the general message. The positions indicated by the cell pointers included in different signaling headers may be the same or different.

The cell may include data of the terminal, and each cell may include one piece of data or multiple pieces of data of the terminal. To avoid data redundancy, the data of the terminal included in different cells is different.

For example, FIG. 6 is a response to a general message provided by an embodiment of the application. As shown in FIG. 6, the response of the general message includes a message header, and the third signaling header includes third signaling semantics and a third cell pointer. The four signaling header includes the fourth signaling semantics and the fourth cell pointer. The third cell pointer is used to indicate the position of the cell carrying the first data of the terminal in the response of the general message, and the fourth cell pointer is used for Indicates the position of the cell carrying the second data of the terminal in the response of the general message.

It should be noted that FIG. 6 is only an exemplary drawing. In addition to the content shown in FIG. 6, the response of the general message may also include other content, which is not limited. Using the message format shown in Figure 6 can increase the scalability of the protocol, save the number of signaling interactions, and avoid repeated transmission of cells.

Optionally, in the fourth scenario of the embodiment shown in FIG. 4, before the first functional entity executes the first function, the method further includes: acquiring input parameters of the first function.

Specifically, the first functional entity may obtain the input parameters of the first function in the following manner:

Manner 1: The centralized controller receives the input parameters of the first function, and sends the input parameters of the first function to the first functional entity, and the first functional entity receives the input parameters of the first function from the centralized controller.

Wherein, the centralized controller may receive input parameters of the first function from the terminal or the access network device, and the input parameters of the first function may be stored in the context of the terminal.

For example, the terminal may obtain the parameters of the first function from the context of the terminal, and directly send the input parameters of the first function to the centralized controller, or send the input parameters of the first function to the access network device, and the access network The device is forwarded to the centralized controller.

Manner 2: In step 401, the general message received by the centralized controller includes the input parameters of the first function, the centralized controller obtains the input parameters of the first function from the general message, and carries the input parameters of the first function in the first request The message is sent to the first functional entity, and the first functional entity obtains the input parameters of the first function from the first request message.

Manner 3: The centralized controller receives the third request message from the first functional entity for requesting the input parameters of the first function, and the centralized controller obtains the input parameters of the first function from the database according to the third request message. And send the input parameters of the first function to the first function entity.

Among them, the centralized controller may obtain the input parameters of the first function according to the above-mentioned method 1, and store the obtained input parameters of the first function in the database; or the centralized controller may obtain the input of the first function according to the above-mentioned method 2. Parameters, and store the input parameters of the first function in the database.

The third request message may include the first cell pointer, which may be used to indicate the cell position of the cell carrying the input parameter of the first function in the general message, and the first function entity may be controlled from the centralized control The device obtains the first cell pointer, carries the first cell pointer in the third request message and sends it to the centralized controller, so that the centralized controller obtains the port from the position indicated by the first cell pointer according to the first cell pointer. A cell of the input parameter of the first function, and send the input parameter of the first function included in the cell to the first functional entity. Such as:

Exemplarily, the general message received by the centralized controller includes the first cell pointer, the centralized controller obtains the first cell pointer from the general message, carries the first cell pointer in the first request message and sends it to the first request message. A functional entity. When the first functional entity needs the input parameters of the first function to perform the first function, the first functional entity can carry the first cell pointer in the third request message and send it to the centralized controller, and the centralized controller receives After reaching the third request message, obtain the first cell pointer from the third request message, obtain the cell carrying the input parameter of the first function from the indicated position from the first cell pointer, and send it to the first functional entity The input parameter of the first function included in the cell.

Similarly, the centralized controller may also receive a fourth request message from the second functional entity for requesting input parameters of the second function, and the centralized controller sends the second functional entity to the second functional entity according to the fourth request message. Input parameters. The input parameters of the second function may include part or all of the output parameters of the first function. Specifically, for this process, reference may be made to the process performed by the first functional entity in the fourth scenario of the embodiment shown in FIG. 4, and details are not described herein again.

Optionally, in the fifth scenario of the embodiment shown in FIG. 4, after the first functional entity has performed the first function, the method further includes: the first functional entity sends the output parameters of the first function to the centralized controller.

Further, it may also include: the centralized controller stores the output parameters of the first function in a database, so that other functional entities or devices share the output parameters of the first function.

Specifically, the process may include:

The first functional entity sends the output parameters of the first function to the centralized controller. After receiving the output parameters of the first function, the centralized controller stores the output parameters of the first function in the database.

Among them, the output parameter of the first function can be carried in the response of the first request message and sent to the centralized controller, and can also be carried in a newly added message and sent to the centralized controller, which is not limited.

Optionally, in the sixth scenario of the embodiment shown in FIG. 4, the foregoing method further includes:

The centralized controller receives a subscription request from a third functional entity; where the subscription request is used to request the centralized controller to notify the third functional entity of the first event, where the first event is that the first functional entity successfully performs the first function;

After the centralized controller receives the response to the first request message sent by the first functional entity, the centralized controller notifies the third functional entity of the first event.

The response of the first request message is used to indicate that the first function is successfully executed.

Optionally, in the seventh scenario of the embodiment shown in FIG. 4, registration information is stored on the centralized controller, and the registration information is used to indicate that the fourth function is executed after the first function is successfully executed; the above method further includes:

When the centralized controller receives the response of the first request message sent by the first functional entity, the centralized controller sends a trigger command to the fourth functional entity according to the registration message, and the trigger command is used to trigger the fourth functional entity to perform the fourth function .

The response of the first request message is used to indicate that the execution of the first function is successfully executed.

In the following, the first functional entity is NF1, NF1 has the "TAL update" function, the second functional entity is NF2, NF2 has the "PDU session establishment" function, and the "TAL update" function and the "PDU session establishment" function do not affect each other as For example, the embodiments of this application are described.

FIG. 7 is a flowchart of another communication method provided by an embodiment of this application. As shown in Figure 7, the method may include:

Step 701: The terminal sends a general message to the centralized controller.

Among them, the general message may include the terminal's identification, function reference information 7a, and function reference information 7b; the function reference information 7a includes signaling semantics 7a for indicating the "TAL update" function, and the function reference information 7b includes information for indicating "establish The signaling semantics of the "PDU session" function 7b.

The identification of the terminal is as described in step 401, and will not be repeated here.

Specifically, the format of the general message may be as shown in FIG. 5, the terminal identifier is included in the message header, and the signaling semantics 7a and 7b are included in different signaling headers. For example, after the terminal determines to update the TAL and establish the PDU session, it can generate a general message including the terminal's identification, signaling semantics 7a, and signaling semantics 7b according to the format shown in Figure 5, and send the generated general message to the central Controller.

Step 702: The centralized controller receives the general message, sends a request message 7a to the NF1 according to the function reference information 7a in the general message, and sends a request message 7b to the NF2 according to the function reference information 7b in the general message.

Among them, the request message 7a can be used to request NF1 to update the TAL for the terminal, and the request message 7a can carry signaling semantics 7a and the identification of the terminal, or when the NF1 only has the "TAL update" function, the request message 7a can only carry The identity of the terminal, but does not carry signaling semantics 7a.

Among them, the request message 7b can be used to request NF2 to establish a PDU session for the terminal, and the request message 7b can carry signaling semantics 7b and the identification of the terminal, or, when the NF2 only has the function of "establishing PDU session", the request message 7b can only Carry the terminal identifier, but not the signaling semantics 7b.

Specifically, the centralized controller sending the request 7a to the NF1 according to the function reference information 7a may include: the centralized controller according to the correspondence between the function entities and the functions performed by the function entities, and the signaling semantics 7a included in the function reference information 7a. The indicated "TAL update" function determines that the network function corresponding to the "TAL update" function is NF1, and sends a request 7a to NF1.

The process of the centralized controller sending the request message 7b to the NF2 according to the function reference information 7b can refer to the process of the centralized controller sending the request message 7a to the NF1 according to the function reference information 7a, which will not be repeated.

Step 703: NF1 receives the request 7a, and performs TAL update for the terminal according to the request message 7a.

Wherein, when the request message 7a includes the terminal's identification and signaling semantics 7a, after receiving the request message 7a, the NF1 can determine that the terminal identified by the terminal's identification performs signaling semantics according to the terminal's identification and signaling semantics 7a The "TAL update" function indicated by 7a.

When the request message 7a includes the identification of the terminal but does not include the signaling semantics 7a, the request message 7a is used as the trigger condition for NF1 to update the TAL of the terminal. After receiving the request message 7a, the NF1 determines the identification of the terminal according to the identification of the terminal. The identified terminal performs TAL update.

Among them, NF1 for the terminal to update the TAL can include the following steps:

Step 703a: NF1 sends a request message 7c to the centralized controller.

Among them, the request message 7c can be used to request the input parameters of the TAL update.

Step 703b: The centralized controller receives the request message 7c, and sends the updated input parameters of the TAL to the NF1.

Among them, the centralized controller can read TAL updated input parameters from the database. For example, the general message in step 701 may include the input parameters updated by the TAL. When the centralized controller receives the general message, the updated input parameters of the TAL in the general message may be stored in the database. When the centralized controller receives When message 7c is requested, the updated input parameters of TAL are read from the database and sent to NF1.

Step 703c: NF1 receives the updated input parameters of TAL, and uses the updated input parameters of TAL to update the terminal's TAL.

Wherein, updating the TAL of the terminal with the input parameter updated by the TAL in step 703c can be implemented by using the existing technology, and will not be repeated.

Step 704: After the terminal's TAL update is completed, the NF1 sends a response of the request message 7a to the centralized controller.

Among them, the response of the request message 7a can be used to indicate that the TAL update is successfully performed. The response of the request message 7a can carry the updated output parameters of the TAL, and can also carry the signaling semantics 7c. The signaling semantics 7c is used to indicate the third function, and the third function may be the "network registration" function.

Further, the response of the request message 7a may also carry first data of the terminal, such as input parameters of the "network registration" function.

Step 705: The centralized controller receives the response of the request message 7a sent by the NF1.

Optionally, when the response of the request message 7a in step 705 carries the updated output parameters of the TAL, step 708 further includes: the centralized controller stores the updated output parameters of the TAL in the database according to the response of the request message 7a.

Step 706: NF2 receives the request message 7b, and establishes a PDU session for the terminal according to the request message 7b.

Wherein, when the request message 7b includes the terminal's identification and signaling semantics 7b, after receiving the request message 7b, the NF2 can determine that the terminal identified by the terminal's identification performs signaling semantics according to the terminal's identification and signaling semantics 7b The "Establish PDU session" function indicated in 7b.

When the request message 7b includes the identification of the terminal but does not include the signaling semantics 7b, the request message 7b is used as the trigger condition for NF2 to establish a PDU session for the terminal. After the request message 7b is received by the NF2, it is determined as the identification of the terminal according to the identification of the terminal The identified terminal establishes a PDU session.

Among them, NF2 establishing a PDU session for the terminal may include the following steps:

Step 706a: NF2 sends a request message 7d to the centralized controller.

Among them, the request message 7d can be used to request the input parameters of the message to establish a PDU session.

Step 706b: The centralized controller receives the request message 7d, and sends input parameters for establishing a PDU session to the NF2.

Among them, the centralized controller can read the input parameters for establishing the PDU session from the database. For example, the general message in step 701 may include input parameters for establishing PDU session. When the centralized controller receives the general message, it may store the input parameters for establishing PDU session in the general message in the database. When receiving the request message 7d, the input parameters for establishing PDU session are read from the database and sent to NF2.

Step 706c: The NF2 receives input parameters for establishing a PDU session, and uses the input parameters for establishing a PDU session to establish a PDU session for the terminal.

Wherein, in step 704c, the establishment of a PDU session for the terminal by using the input parameters of establishing a PDU session can be implemented by using the existing technology, and will not be repeated.

Step 707: After the establishment of the PDU session is completed, the NF2 sends a response of the request message 7b to the centralized controller.

Among them, the response of the request message 7b can be used to indicate that the NF2 successfully establishes a PDU session.

The response of the request message 7b may carry output parameters for establishing a PDU session, and may also carry signaling semantics 7d. The signaling semantics 7d is used to indicate the fourth function, and the fourth function may be a "third-party authentication" function.

Further, the response of the request message 7b may also carry second data of the terminal, such as input parameters of the "third-party authentication" function.

Step 708: The centralized controller receives the response of the request message 7b sent by the NF2.

Optionally, when the response of the request message 7b carries output parameters for establishing a PDU session, step 713 further includes: the centralized controller stores the output parameters for establishing a PDU session in the data according to the response of the request message 7b.

Optionally, after receiving the response of the request message 7a and the response of the request message 7b, the centralized controller may carry the content included in the response of the request message 7a and the response of the request message 7b in the response of the general message and send it to the terminal. Specifically, as shown in step 709.

Step 709: The centralized controller sends a response to the general message to the terminal.

Among them, the response of the general message can be used to indicate the successful update of the terminal's TAL and the successful establishment of a PDU session for the terminal. The response of the general message may include: signaling semantics 7c, signaling semantics 7d, first data of the terminal, and second data of the terminal.

Among them, the response of the general message may adopt the format shown in FIG. 6, and will not be repeated.

Further, the response of the general message may also include a cell pointer 7a and a cell pointer 7b. The cell pointer 7a is used to indicate the position of the cell carrying the first data of the terminal in the response of the general message, and the cell pointer 7b is used for To indicate the position of the cell carrying the second data of the terminal in the response to the general message and other information.

Step 710: The terminal receives the response of the general message.

It should be noted that the execution sequence of step 703 and step 706 is not limited.

Step 711: The terminal executes the network registration function and the third-party authentication function according to the response of the general message.

Optionally, after the terminal determines to perform the "network registration" function according to the signaling semantics 7c included in the response of the general message, it acquires the cell carrying the first data of the terminal according to the cell pointer 7a, and performs network registration using the first data of the terminal .

After the terminal determines to perform the "third-party authentication" function according to the signaling semantics 7d included in the response of the general message, it obtains the cell carrying the second data of the terminal according to the cell pointer 7b, and uses the second data of the terminal to perform third-party authentication.

Based on the method shown in Figure 7, the terminal can carry the signaling semantics used to request the NF to update the TAL and establish the PDU session for the terminal in the same message and send it to the centralized controller. After the centralized controller receives the message, it can simultaneously Request NF1 to perform TAL update and request NF2 to establish PDU session, that is, one message interaction between the terminal and the centralized controller can trigger multiple functional entities to perform corresponding functions, without the need to complete TAL update and PDU session through the signaling interaction between NF1 and NF2 Establish, reduce the frequency of message sending, reduce signaling overhead, save network resources, and improve efficiency.

In the following, the first functional entity is NF1, NF1 has the function of "third-party authentication", the second functional entity is NF2, and NF2 has "establish PDU session", and the "third-party authentication" function is executed after the function of "establish PDU session". For example, the embodiments of this application are described.

FIG. 8 is a flowchart of another communication method provided by an embodiment of the application. As shown in FIG. 8, the method may include:

Step 801: The terminal sends a general message to the centralized controller.

Among them, the general message may include the identification of the terminal, function reference information 8a, and function reference information 8b; the function reference information 8a includes signaling semantics 8a used to indicate the function of "establishing PDU session", and the function reference information 8b includes information used to indicate " The signaling semantics of the third-party authentication function 8b.

Specifically, the format of the general message may be as shown in FIG. 5, the terminal identifier is included in the message header, and the signaling semantics 8a and 8b are included in different signaling headers. For example, after the terminal determines to establish a PDU session and third-party authentication, it can generate a general message including the terminal’s identification, signaling semantics 8a, and signaling semantics 8b according to the format shown in Figure 5, and send the generated general messages to the central Controller.

Step 802: The centralized controller receives the general message, and sends a request message 8a to the NF1 according to the function reference information 8a in the general message.

Among them, the request message 8a can be used to request NF1 to establish a PDU session for the terminal, and the request message 8a can carry signaling semantics 8a and the identification of the terminal, or when the NF1 only has the function of "establishing PDU session", the request message 8a can only Carry the terminal identifier, but not the signaling semantics 8a.

Specifically, the centralized controller sending the request message 8a to the NF1 according to the signaling semantics 8a may include: the centralized controller according to the correspondence between the functional entities and the functions performed by the functional entities, and the "establish PDU" indicated by the signaling semantics 8a The "session" function determines that the network function corresponding to the "Establish PDU session" function is NF1, and sends a request message 8a to NF1.

Wherein, before sending the request message 8a to the NF1 according to the function reference information 8a, it may also include: the centralized controller determines, according to the function reference information 8a and the function reference information 8b, that NF2 is the input parameter required by the terminal for third-party authentication depends on the NF1 The output parameters after the completion of the establishment of PDU session for the terminal, that is, the sequence relationship between the "Establish PDU session" function and the "third-party authentication" function is determined to be serial, and the sequence of the request message 8a has priority over the request message 8b, and the centralized controller Step 802 may be performed first, and then step 806 may be performed after receiving the response to the request message 8a.

Step 803: NF1 receives the request message 8a, and establishes a PDU session for the terminal according to the request message 8a.

Wherein, when the request message 8a includes the terminal's identification and signaling semantics 8a, after receiving the request message 8a, the NF1 can determine that the terminal identified by the terminal's identification performs signaling semantics according to the terminal's identification and signaling semantics 8a The "Establish PDU session" function indicated in 8a.

When the request message 8a includes the identification of the terminal but does not include the signaling semantics 8a, the request message 8a is used as a trigger condition for NF1 to update the TAL of the terminal. After receiving the request message 8a, the NF1 determines the identification of the terminal according to the identification of the terminal The identified terminal establishes a PDU session.

Among them, NF1 establishing a PDU session for the terminal may include the following steps:

Step 803a: NF1 sends a request message 8c to the centralized controller.

Among them, the request message 8c can be used to request the establishment of the input parameters of the PDU session.

Step 803b: The centralized controller receives the request message 8c, and sends input parameters for establishing a PDU session to the NF1.

Among them, the centralized controller can read the input parameters for establishing the PDU session from the database. For example, the general message in step 801 may include input parameters for establishing PDU session. When the centralized controller receives the general message, it can store the input parameters for establishing PDU session in the general message in the database. When the request message 8c is received, the input parameters for establishing the PDU session are read from the database and sent to NF1.

Step 803c: NF1 receives input parameters for establishing a PDU session, and uses the input parameters for establishing a PDU session to establish a PDU session for the terminal.

Wherein, the establishment of the PDU session by using the input parameters for establishing the PDU session in step 803c can be implemented by using the existing technology, and will not be repeated.

Step 804: After successfully establishing the PDU session, the NF1 sends a response to the request message 8a to the centralized controller.

Among them, the response of the request message 8b can be used to indicate that the NF2 successfully establishes a PDU session. The response of the request message 8b may carry output parameters for establishing a PDU session.

Step 805: The centralized controller receives the response of the request message 8a sent by the NF1.

Optionally, when the response of the request message 8a can carry output parameters for establishing a PDU session, step 808 further includes: the centralized controller stores the output parameters for establishing a PDU session in the database according to the response of the request message 8a.

Step 806: The centralized controller sends a request message 8b to NF2.

Among them, the request message 8b can be used to request NF2 to perform third-party authentication for the terminal, and the request message 8b can carry signaling semantics 8b and the identification of the terminal, or, when the NF2 only has the "third-party authentication" function, the request message 8b can It only carries the identification of the terminal, but does not carry the signaling semantics 8b.

Wherein, the centralized controller sending the request message 8b to the NF2 may include: the centralized controller sending the request message 8b to the NF2 according to the time sequence relationship between the "establish PDU session" function and the "third-party authentication" function.

Step 807: NF2 receives the request message 8b, and performs third-party authentication for the terminal according to the request message 8b.

Wherein, when the request message 8b includes the terminal's identification and signaling semantics 8b, after receiving the request message 8b, the NF2 can determine that the terminal identified by the terminal's identification performs signaling semantics according to the terminal's identification and signaling semantics 8b The "third-party authentication" function as indicated in 8b.

When the request message 8b includes the identification of the terminal but does not include the signaling semantics 8b, the request message 8b is used as the trigger condition for NF2 to update the TBL of the terminal. After receiving the request message 8b, the NF2 determines the identification of the terminal according to the identification of the terminal. The identified terminal undergoes third-party authentication.

Among them, the third-party authentication performed by NF2 for the terminal may include the following steps:

Step 807a: NF2 sends a request message 8c to the centralized controller.

Among them, the request message 8c can be used to request input parameters for third-party authentication.

Step 807b: The centralized controller receives the request message 8c, and sends input parameters for third-party authentication to the NF2.

Among them, the centralized controller can read the input parameters of the third-party authentication from the database. For example, the general message in step 801 may include input parameters for third-party authentication. When the centralized controller receives the general message, it can store the input parameters of the third-party authentication in the general message in the database. When receiving the request message 8c, the input parameters of the third-party authentication are read from the database and sent to NF2.

Step 807c: The NF2 receives the input parameters of the third-party authentication, and uses the input parameters of the third-party authentication to perform third-party authentication on the terminal.

Wherein, the third-party authentication of the terminal using the input parameters of the third-party authentication in step 807c can be implemented by using the existing technology, which will not be repeated.

Step 808: After the terminal performs third-party authentication for the terminal, the NF2 sends a response of the request message 8b to the centralized controller.

Among them, the response of the request message 8b can be used to indicate that the NF2 successfully completes the third-party authentication. The response of the request message 8b may carry output parameters for third-party authentication.

Step 809: The centralized controller receives the response of the request message 8b sent by the NF2.

Optionally, when the response of the request message 8b in step 705 carries the output parameters of the third-party authentication, step 708 further includes: the centralized controller stores the output parameters of the third-party authentication in the database according to the response of the request message 8b.

Step 810: The centralized controller sends a response to the general message to the terminal.

Among them, the response of the general message can be used to indicate the successful establishment of a PDU session for the terminal and the completion of third-party authentication.

Step 811: The terminal receives the response of the general message.

Based on the method shown in Figure 8, the terminal can carry the signaling semantics used to request the NF to perform third-party authentication and establish a PDU session for the terminal in the same message and send it to the centralized controller. After the centralized controller receives the message, it can According to the timing relationship between third-party authentication and the establishment of PDU session, first request NF1 to establish PDU session, and then request NF2 to perform third-party authentication. In this way, a message interaction between the terminal and the centralized controller can trigger multiple functional entities to execute the corresponding The function of NF1 and NF2 does not need to complete third-party authentication and establish PDU session through the signaling interaction between NF1 and NF2, reducing the number of message sending, reducing signaling overhead, saving network resources, and improving efficiency.

The foregoing mainly introduces the solution provided by the embodiment of the present application from the perspective of interaction between various nodes. It can be understood that each node, such as a centralized controller, a first functional entity, and a second functional entity, includes hardware structures and/or software modules corresponding to each function in order to implement the above functions. Those skilled in the art should easily realize that in combination with the algorithm steps of the examples described in the embodiments disclosed herein, this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

The embodiment of the present application can divide the functional modules of the centralized controller, the first functional entity, and the second functional entity according to the foregoing method examples. For example, each functional module can be divided corresponding to each function, or two or more The functions are integrated in a processing module. The above-mentioned integrated modules can be implemented in the form of hardware or software functional modules. It should be noted that the division of modules in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.

FIG. 9 is a schematic structural diagram of a communication device 90 provided by an embodiment of the application. The communication device 90 involved in this embodiment may be a centralized controller or a chip or a system on a chip in the centralized controller. The communication device 90 can be used to perform the functions of the centralized controller in the foregoing method embodiments.

As an implementable manner, as shown in FIG. 9, the communication device 90 may include: a receiving unit 901 and a sending unit 902.

The receiving unit 901 is configured to receive a general message including the identification of the terminal, the first function reference information, and the second reference information. For example, the receiving unit 901 may be used to support the communication device 90 to perform step 401, step 702, and step 802.

The sending unit 902 is configured to send a first request message for requesting the first functional entity to perform the first function for the terminal to the first functional entity according to the first function reference information and the terminal identifier received by the receiving unit 901.

The sending unit 902 is configured to send a second request message for requesting the second function entity to perform the second function for the terminal to the second function network element according to the second function reference information and the terminal identifier received by the receiving unit 901. For example, the sending unit 902 may be used to support the communication device 90 to perform step 402, step 702, step 802, and step 806.

Specifically, the communication device 90 provided in the embodiment of the present application can execute the actions of the centralized controller in the method embodiment corresponding to FIG. 4, and its implementation principles and technical effects are similar, and will not be repeated here.

As yet another achievable manner, the communication device 90 shown in FIG. 9 may include: a processing module and a communication module.

Among them, the communication module can integrate the functions of the receiving unit 901 and the sending unit 902. The processing module is used to control and manage the actions of the communication device 90, and the communication module is used to support the communication device 90 to perform steps 401, 402, etc., and to communicate with other network entities. Further, the communication device 90 shown in FIG. 9 further includes a storage module for storing program codes and data of the communication device 90.

Among them, the processing module may be a processor or a controller. It can implement or execute various exemplary logical blocks, modules and circuits described in conjunction with the disclosure of this application.

The processor may also be a combination that implements computing functions, for example, it includes one or more microprocessors, or a combination of a DSP and a microprocessor, and so on. The communication module can be a transceiver circuit or a communication interface. The storage module may be a memory. When the processing module is a processor, the communication module is a communication interface, and the storage module is a memory, the communication device 90 shown in FIG. 9 may be the communication device shown in FIG. 3.

In another achievable manner, the device 90 shown in FIG. 9 includes: a processor and a memory; the memory is used to store computer-executed instructions, and when the communication device 90 is running, the processor executes the computer-executed instructions stored in the memory , So that the communication device 90 performs the actions of the centralized controller as in the foregoing method embodiment.

FIG. 10 is a schematic structural diagram of a communication device 100 provided by an embodiment of this application. The communication device involved in this embodiment may be the first functional entity or a chip or a system on a chip in the first functional entity. The communication device 100 may be used to execute the function of the first functional entity in the foregoing method embodiment.

As an implementable manner, as shown in FIG. 10, the communication device may include: a receiving unit 1001 and an executing unit 1002.

The receiving unit 1001 is configured to receive a first request message from the centralized controller for requesting the first functional entity to perform the first function for the terminal. For example, the receiving unit 1001 may support the communication device 100 to perform step 403, step 703, and step 803.

The execution unit 1002 is configured to execute the first function according to the first request message received by the receiving unit 1001. For example, the execution unit 1002 may be used to support the communication device 100 to execute step 403, step 703, step 803, and so on.

Specifically, the communication device 100 provided in the embodiment of the present application can perform the actions of the first functional entity in the method embodiment corresponding to FIG. 4, and its implementation principles and technical effects are similar, and will not be repeated here.

As yet another achievable manner, the communication device 100 shown in FIG. 10 may include: a processing module and a communication module. The communication module can integrate the functions of the receiving unit 1001. The processing module is used to control and manage the actions of the communication device 100, and the communication module is used to support the communication device 100 to perform step 403 and to communicate with other network entities.

Further, the communication device 100 shown in FIG. 10 further includes a storage module for storing program codes and data of the communication device 100. Among them, the processing module may be a processor or a controller. It can implement or execute various exemplary logical blocks, modules and circuits described in conjunction with the disclosure of this application. The processor may also be a combination that implements computing functions, for example, it includes one or more microprocessors, or a combination of a DSP and a microprocessor, and so on. The communication module can be a transceiver circuit or a communication interface. The storage module may be a memory. When the processing module is a processor, the communication module is a communication interface, and the storage module is a memory, the communication device 100 shown in FIG. 10 may be the communication device shown in FIG. 3.

In another achievable manner, the device 100 shown in FIG. 10 includes: a processor and a memory; the memory is used to store computer-executed instructions, and when the communication device 100 is running, the processor executes the computer-executed instructions stored in the memory , So that the communication device 100 executes the actions of the first functional entity in the foregoing method embodiments.

FIG. 11 is a schematic structural diagram of a communication system provided by an embodiment of the application. As shown in FIG. 11, the system may include a centralized controller 110, a functional entity 111, and a terminal 112.

Among them, the centralized controller 110 has the same function as the communication device 90, and the functional entity 111 has the same function as the communication device 100. In addition, there may be one or more functional entities 111.

The terminal 112 is used to send general messages to the centralized controller 110. Among them, the general message is described in the embodiment corresponding to the method shown in FIG. 4 and will not be repeated.

Taking the functional entity 111 including the functional entity 1111 and the functional entity 1112 as an example, the centralized controller 110 is used to perform actions of the centralized controller in the embodiment shown in FIG. 4, FIG. 7 or FIG. 8, for example, receiving general information from the terminal 112 Message, and send a first request message to the functional entity 1111 according to the first function reference information and the identification of the terminal, and send a second request message to the functional entity 1112 according to the second function reference information and the identification of the terminal.

The functional entity 1111 is configured to perform actions of the first functional entity in the embodiment shown in FIG. 4, FIG. 7 or FIG. 8, for example, perform the first function according to the first request message.

The functional entity 1112 is configured to perform actions of the second functional entity in the embodiment shown in FIG. 4, FIG. 7 or FIG. 8, for example, perform the second function according to the second request message.

Further, the functional entity 1111 may also be used to send third signaling semantics to the centralized controller 110, and the third signaling semantics is used to indicate the third function.

The centralized controller 110 may also be configured to receive the third signaling semantics from the functional entity 1111, and send the third signaling semantics to the terminal 112, so that the terminal 112 performs the third function according to the third signaling semantics.

Similarly, the functional entity 1112 may also be used to send the fourth signaling semantics to the centralized controller 110, and the fourth signaling semantics is used to indicate the fourth function.

The centralized controller 110 may also be configured to receive the fourth signaling semantics from the functional entity 1112, and send the fourth signaling semantics to the terminal 112, so that the terminal 112 performs the fourth function according to the fourth signaling semantics.

Wherein, in the case where the time sequence relationship between the third function and the first function is serial (for example, the third function needs to be executed after the first function is successfully executed), the functional entity 1111 may send to the centralized The controller 110 sends the third signaling semantics, which may be carried in the response of the first request message.

In the case that the timing relationship between the fourth function and the second function is serial (for example, the fourth function needs to be executed after the second function is successfully executed), the functional entity 1111 may report to the centralized controller after the second function is successfully executed 110 sends the fourth signaling semantics, which may be carried in the response of the second request message.

For the related description of the response of the first request message and the response of the second request message, refer to the description in the foregoing method embodiment, and will not be repeated.

For example, the third function may be the "PDU session modification" function, which can be executed independently. When the functional entity 1111 determines to perform the "PDU session modification" function, the functional entity 1111 may send to the centralized controller 110 an indication of "PDU session modification". The third signaling semantics of the "modify" function, after receiving the third signaling semantics, the centralized controller 110 may send the third signaling semantics to the terminal.

For another example, the first function is to establish a "PDU session" function, and the third function is a "third-party authentication" function. The "third-party authentication" function needs to be executed after the "PDU session" is successfully established. The first request message is the request function entity 1111 establishes a PDU session for the terminal. When the functional entity 1111 receives the first request message and successfully establishes the PDU meeting, the functional entity 1111 may send a response to the first request message to the centralized controller 110. The response of the first request message may carry a response indicating "third party authentication "The third signaling semantics of the function.

Specifically, the communication system provided by the embodiment of the present application may execute the method embodiment corresponding to FIG. 4 or FIG. 7 or FIG. 8, and its implementation principles and technical effects are similar, and will not be repeated.

FIG. 12 is a schematic structural diagram of a communication system provided by an embodiment of the application. As shown in FIG. 12, the system may include a centralized controller 120, a functional entity 121, and an access network device 122.

Among them, the centralized controller 120 has the same function as the communication device 90, and the functional entity 121 has the same function as the communication device 100. In addition, the functional entity 121 may be one or more.

The access network device 122 is configured to send general messages to the centralized controller 120. Among them, the general message is described in the embodiment corresponding to the method shown in FIG. 4 and will not be repeated.

Taking the functional entity 121 including the functional entity 1211 and the functional entity 1212 as an example, the centralized controller 120 is configured to perform actions of the centralized controller in the embodiment shown in FIG. 4, FIG. 7 or FIG. 8, for example, receiving from an access network device 121, and send a first request message to the functional entity 1211 according to the first function reference information and the identification of the terminal, and send a second request message to the functional entity 1212 according to the second function reference information and the identification of the terminal.

The functional entity 1211 is configured to execute the actions of the first functional entity in the embodiment shown in FIG. 4, FIG. 7 or FIG. 8, for example, execute the first function according to the first request message.

The functional entity 1212 is configured to perform actions of the second functional entity in the embodiment shown in FIG. 4, FIG. 7 or FIG. 8, for example, perform the second function according to the second request message.

Further, the system shown in FIG. 12 may further include: a terminal 123.

In an implementation manner, the terminal 123 is configured to send the identification of the terminal 123, the first function reference information, and the second function reference information to the access network device 122.

The access network device 122 is specifically configured to receive the terminal 123 identifier, first function reference information, and second function reference information from the terminal 123, and encapsulate the terminal 123 identifier, the first function reference information, and the second function reference information to generate General messages, and send general messages to the centralized controller 120.

In another implementation manner, the terminal 123 is configured to send a general message to the access network device 122.

The access network device 122 is specifically configured to receive general messages from the terminal 123 and send the general messages to the centralized controller 120.

Further, the functional entity 1211 may also be used to send third signaling semantics to the centralized controller 120, and the third signaling semantics is used to indicate the third function.

The centralized controller 120 may also be configured to receive the third signaling semantics from the functional entity 1211, and send the third signaling semantics to the access network device 122, so that the access network device 122 executes the third signaling semantics according to the third signaling semantics. Features.

Similarly, the functional entity 1212 may also be used to send the fourth signaling semantics to the centralized controller 120, and the fourth signaling semantics is used to indicate the fourth function.

The centralized controller 120 may also be configured to receive the fourth signaling semantics from the functional entity 1212, and send the fourth signaling semantics to the access network device 122, so that the access network device 122 executes the fourth signaling semantics according to the fourth signaling semantics. Features.

Wherein, in the case where the time sequence relationship between the third function and the first function is serial (for example, the third function needs to be executed after the first function is successfully executed), the functional entity 1211 may transfer to the centralized The controller 120 sends the third signaling semantics, which may be carried in the response of the first request message.

In the case that the timing relationship between the fourth function and the second function is serial (for example, the fourth function needs to be executed after the second function is successfully executed), the functional entity 1212 may report to the centralized controller after the second function is successfully executed 120 sends the fourth signaling semantics, which may be carried in the response of the second request message.

Through the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and brevity of the description, only the division of the above-mentioned functional modules is used as an example for illustration. In practical applications, the above-mentioned functions can be allocated as needed. It is completed by different functional modules, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

In the several embodiments provided in this application, it should be understood that the disclosed device and method may be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods, for example, multiple units or components may be It can be combined or integrated into another device, or some features can be omitted or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate parts may or may not be physically separate. The parts displayed as units may be one physical unit or multiple physical units, that is, they may be located in one place, or they may be distributed to multiple different places. . Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, the functional units in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of the present application are essentially or the part that contributes to the prior art, or all or part of the technical solutions can be embodied in the form of software products, which are stored in a storage medium There are several instructions to make a device (which may be a single-chip microcomputer, a chip, etc.) or a processor (processor) execute all or part of the steps of the methods described in the embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk and other media that can store program codes.

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any change or replacement within the technical scope disclosed in this application shall be covered by the protection scope of this application . Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

A communication method, characterized in that the method includes:

The centralized controller receives a general message, the general message including the identification of the terminal, the first function reference information, and the second function reference information;

The centralized controller sends a first request message to a first functional entity according to the first function reference information and the terminal identifier, and the first request message is used to request that the first functional entity be the terminal Perform the first function;

The centralized controller sends a second request message to a second functional entity according to the second functional reference information and the terminal identifier, and the second request message is used to request the second functional entity to be the terminal Perform the second function.
The method according to claim 1, wherein the first function reference information includes at least one of the first signaling semantics and the identification of the first function entity; the second function reference information includes the first At least one of signaling semantics and the identification of the second functional entity;

Wherein, the first signaling semantics is used to indicate the first function; the second signaling semantics is used to indicate the second function.
The method according to claim 2, wherein the first request message includes the first signaling semantics; the second request message includes the second signaling semantics.
The method according to any one of claims 1 to 3, wherein the first request message includes an input parameter of the first function, and the input parameter of the first function is used for the first functional entity Perform the first function.
The method according to any one of claims 1-3, wherein the method further comprises:

The centralized controller receives a third request message from the first functional entity, where the third request message is used to request input parameters of the first function;

The centralized controller sends the input parameter of the first function to the first function entity according to the third request message.
The method according to claim 4 or 5, wherein the method further comprises:

The centralized controller receives input parameters of the first function from the terminal or the access network device.
The method according to claim 4 or 5, wherein the general message further includes input parameters of the first function.
The method according to claim 7, wherein the general message includes a first signaling header, a second signaling header, and information elements;

Wherein, the first signaling header includes the first function reference information and a first cell pointer, and the first cell pointer is used to indicate that the cell carrying the input parameter of the first function is in the universal The position in the message; the second signaling header includes the second function reference information.
The method according to any one of claims 6-8, wherein the method further comprises:

The centralized controller stores the input parameters of the first function in a database.
The method according to any one of claims 1-9, wherein the method further comprises:

Receiving, by the centralized controller, a response to the first request message from the first functional entity, where the response to the first request message is used to indicate that the first function is successfully executed;

The centralized controller receives a response to the second request message from the second functional entity, where the response to the second request message is used to indicate that the second function is successfully executed.
The method according to claim 10, wherein the method further comprises:

The centralized controller sends a response to the general message, and the response to the general message is used to notify that the first function and the second function are successfully executed.
The method according to claim 11, wherein the response of the first request message includes third signaling semantics, and the third signaling semantics is used to indicate a third function; the response of the general message includes all Describe the third signaling semantics.
The method according to claim 11 or 12, wherein the response of the general message further includes first data of the terminal.
The method according to claim 13, wherein the response of the first request message includes data indication information, and the data indication information is used to indicate the first data of the terminal; Before the response to the general message, the description also includes:

The centralized controller obtains the first data of the terminal from a database according to the data indication information.
The method according to claim 13, wherein the response of the first request message includes the first data of the terminal.
The method according to any one of claims 1-15, wherein the method further comprises:

The centralized controller receives the output parameter of the first function from the first functional entity;

The centralized controller stores the output parameters of the first function in a database.
The method according to claim 16, wherein the output parameter of the first function is carried in the response of the first request message.
The method according to any one of claims 1-17, wherein:

When the time sequence relationship between the first function and the second function is parallel, the first request message and the second request message are simultaneously sent by the centralized controller; or

When the timing relationship between the first function and the second function is serial, and the first function is executed before the second function, the second request message is controlled by the centralized control After receiving the response of the first request message; or

When the time sequence relationship between the first function and the second function is serial, and the second function is executed before the first function, the first request message is controlled by the centralized control After receiving the response of the second request message.
The method of claim 18, wherein the method further comprises:

The centralized controller determines the timing relationship between the first function and the second function according to the first function reference information and the second function reference information.
A communication method, characterized in that the method includes:

A first functional entity receives a first request message from a centralized controller, where the first request message is used to request the first functional entity to perform a first function for the terminal;

The first functional entity executes the first function according to the first request message.
The method according to claim 20, wherein the first request message includes first signaling semantics, and the first signaling semantics is used to indicate the first function.
The method according to claim 21, wherein the first request message further includes input parameters of the first function; the input parameters of the first function are used by the first functional entity to execute the first function. A function. The first function entity executes the first function according to the first request message, including:

The first functional entity executes the first function according to the first signaling semantics and the input parameters of the first function.
The method of claim 21, wherein the method further comprises:

The first functional entity sends a third request message to the centralized controller according to the first request message, where the third request message is used to request input parameters of the first function and receive data from the centralized controller Input parameters of the first function of the device;

The first functional entity executing the first function according to the first request message includes: the first functional entity executing the first function according to the first signaling semantics and the input parameters of the first function The first function.
The method according to any one of claims 20-23, wherein the method further comprises:

The first functional entity sends a response to the first request message to the centralized controller, where the response to the first request message is used to indicate that the first function is successfully executed.
The method according to claim 24, wherein the response of the first request message includes third signaling semantics, and the third signaling semantics is used to indicate a third function.
The method according to claim 25, wherein the response of the first request message further includes data indication information, and the data indication information is used to indicate the first data of the terminal; or,

The response of the first request message includes the first data of the terminal.
The method according to any one of claims 20-26, wherein the method further comprises:

The first functional entity sends the output parameter of the first function to the centralized controller.
The method according to claim 27, wherein the output parameter of the first function is carried in the response of the first request message.
A communication device, characterized in that the communication device comprises at least one processor, and the at least one processor is configured to execute the actions performed by the centralized controller in the communication method according to any one of claims 1-19.
A computer-readable storage medium, characterized in that the computer-readable storage medium includes computer instructions, which when run on a computer, cause the computer to execute the communication according to any one of claims 1-19 method.
A computer program product, characterized in that the computer program product includes computer instructions, and when the computer instructions are executed on a computer, the computer executes the communication method according to any one of claims 1-19.
A communication device, characterized in that the communication device comprises at least one processor, and the at least one processor is configured to execute the actions performed by the first functional entity in the communication method according to any one of claims 20-28 .
A computer-readable storage medium, characterized in that the computer-readable storage medium includes computer instructions, which when run on a computer, cause the computer to execute the communication according to any one of claims 20-28 method.
A computer program product, characterized in that the computer program product includes computer instructions, which when run on a computer, cause the computer to execute the communication method according to any one of claims 20-28.
A communication system, characterized by comprising: a centralized controller, a first functional entity, and a second functional entity;

The centralized controller is configured to receive a general message, the general message including an identifier of the terminal, first function reference information, and second function reference information;

The centralized controller is further configured to send a first request message to the first functional entity according to the first function reference information and the terminal identifier, and the first request message is used to request the first The functional entity performs the first function for the terminal;

And, sending a second request message to the second functional entity according to the second function reference information and the identification of the terminal, where the second request message is used to request the second functional entity to perform execution for the terminal Second function

The first functional entity is configured to receive a first request message from the centralized controller, and execute the first function according to the first request message;

The second functional entity is configured to receive a second request message from the centralized controller, and execute the second function according to the second request message.