Service generation method and apparatus, and network device

Abstract

A service generation method and apparatus, and a network device. When a network device does not support a certain service needing to be executed, a terminal device may send a request instruction to the network device and / or a service generation system. Upon receiving the request instruction from the terminal device, the network device and / or the service generation system may generate a service context of a target service and maintain the service context of the target service. In this way, the terminal device executes the target service by means of the network device and / or the service generation system to ensure the continuity of the terminal device running the target service.

Description

Service generation method, device and network equipment

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on December 19, 2023, with application number 202311758790.5 and application name “A service generation method, device and network device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present invention relates to the field of communication technology, and in particular to a service generation method, device and network equipment. Background Art

[0003] To meet the vision of intelligent and inclusive future, wireless network architectures can evolve intelligently. For example, this can involve deeply integrating artificial intelligence (AI) with wireless networks. This allows wireless networks to provide not only traditional communication connectivity services but also computing and AI services, and equip terminal devices with certain AI capabilities. If the network lacks the AI ​​services that a terminal device requires, it cannot provide these services. Summary of the Invention

[0004] To address the aforementioned issues, embodiments of the present application provide a service generation method. When a network device does not support a service that a terminal device requires to be executed, the network device and / or core network provides the terminal device with the service. Furthermore, the present application also provides a service generation apparatus and network device corresponding to the service generation method.

[0005] To this end, the following technical solutions are adopted in the embodiments of the present application:

[0006] In the first aspect, an embodiment of the present application provides a service generation method, which is executed by a network device and a core network, and the method includes: the network device sends a seventh request instruction to the core network; the seventh request instruction is used to request the core network to provide service function information supporting the target service, and the service function information includes the service type and / or function type that can be provided by each network element supporting the target service; the core network receives the seventh request instruction and sends the service function information to the network device; the network device determines all or part of the service context of the target service based on the service type and / or function type that can be provided by each network element supporting the target service; the service context of the target service includes relevant resources of one or more network elements supporting the target service.

[0007] In this embodiment, when the network device does not support the target service, it may send a seventh request instruction to the core network, requesting the core network to send the service types and / or function types that can be provided by each network element supporting the target service to the network device. After obtaining the service types and / or function types that can be provided by each network element supporting the target service, the network device may construct a service context for the target service, so that the network device can run the target service in the core network, thereby enabling the network device to support the target service.

[0008] In one embodiment, the method further includes: the network device setting the service context of the target service to an inactive state; the inactive state refers to placing related resources of the one or more network elements supporting the target service in a dormant state.

[0009] In this embodiment, after the network device generates the service context of the target service, it can set the relevant resources of one or more network elements supporting the target service to a dormant state, so as to avoid the relevant resources of one or more network elements supporting the target service being in a working state when the target service is not executed, thereby occupying a large amount of resources of each network element in the core network.

[0010] In one embodiment, before the network device sends the seventh request instruction to the core network, the method further includes: the network device receives a first request instruction sent by a terminal device; the first request instruction is used to request the target service supported by the network device; the network device detects whether a service context of the target service exists locally; the network device sends the seventh request instruction to the core network, specifically including: when the network device determines that a service context of the target service does not exist locally, sending the seventh request instruction to the core network.

[0011] In one embodiment, the method also includes: when the network device determines that the service context of the target service exists locally, judging whether the area identifier in the service context of the target service is the same as the local area identifier; the area identifier is used to distinguish the geographical area in which the service context is effective; when the area identifier in the service context of the target service is different from the local area identifier, the network device sends a ninth request instruction to the terminal device; the ninth request instruction is used to request the terminal device to determine whether the network device regenerates the service context of the target service.

[0012] In this embodiment, a region identifier can be added to the service context constructed by the network device. The network device can determine whether the network device connected to the terminal device has switched by determining whether the region identifier in the service context of the target service is the same as the local region identifier, thereby ensuring the security of the terminal device in executing the target service.

[0013] In one embodiment, the method further includes: the network device sending a first response instruction to the terminal device; the first response instruction is used to notify the terminal device that the network device supports the target service.

[0014] In this embodiment, after the network device constructs the service context of the target service through the core network, it can support the target service and send a first response instruction to the terminal device, so that the terminal device executes the target service through the network device.

[0015] In one embodiment, the method further includes: the network device receiving an eighth request instruction sent by the terminal device; the eighth request instruction is used to request the network device to execute the target service; and the network device sets the service context of the target service to an activated state.

[0016] In this embodiment, after the network device supports the target service through the core network, it can send a service generation instruction to the terminal device to inform the local support of the target service, so that the terminal device can execute the target service through the network device. After receiving the execution instruction from the terminal device, the network device can put the relevant resources of one or more network elements supporting the target service into an operating state, so that the network device can execute the target service through the core network.

[0017] In one embodiment, the method further includes: the network device configuring air interface resources for the terminal device; the air interface resources are used to carry traffic of the target service transmitted between the terminal device and the network device.

[0018] In this embodiment, the network device configures air interface resources for the terminal device. The air interface resources can carry traffic for transmitting the target service between the terminal device and the network device, so that the network device can perform the target service for the terminal device.

[0019] In one embodiment, the method further includes: the network device broadcasting or multicasting a system message; and indicating that the network device supports a target service.

[0020] In this embodiment, the network device may broadcast or multicast the locally supported target service to more terminal devices, so that the network device can provide the target service to more terminal devices.

[0021] In one embodiment, the network device sends a tenth request instruction to the terminal device; the tenth request instruction is used to request a query of the service context in the terminal device; the network device receives a tenth response instruction sent by the terminal device; the tenth response instruction includes at least one service context identifier; the network device updates the service context corresponding to the at least one service context identifier based on the at least one service context identifier.

[0022] In one embodiment, the network device updates the service context corresponding to the at least one service context identifier according to the at least one service context identifier, specifically including: the network device broadcasts an eleventh request instruction; the eleventh request instruction is used to request other network devices to provide the service context corresponding to the at least one service context identifier; the network device receives an eleventh response instruction; the eleventh response instruction includes the service context corresponding to the at least one service context identifier; the network device updates the service context corresponding to the at least one service context identifier according to the service context corresponding to the at least one service context identifier.

[0023] In a second aspect, an embodiment of the present application provides a service generation method, which is executed by a network device, and the method includes: sending a tenth request instruction to a terminal device; the tenth request instruction is used to request a query of a service context in the terminal device; receiving a tenth response instruction sent by the terminal device; the tenth response instruction includes at least one service context; broadcasting the eleventh request instruction; the eleventh request instruction is used to request the provision of a service context corresponding to the at least one service context identifier; receiving an eleventh response instruction; the eleventh response instruction includes a service context corresponding to the at least one service context identifier; and updating the service context corresponding to the at least one service context identifier based on the service context corresponding to the at least one service context identifier.

[0024] In a third aspect, an embodiment of the present application provides a service generation method, which is executed by a service generation system, and the method includes: receiving a second request instruction sent by a terminal device; the second request instruction is used to request a target service supported by the service generation system, and the second request instruction includes a service context identifier; based on the service context identifier, determining the service context of the target service; the service context includes relevant resources of one or more network elements supporting the target service; sending a second response instruction to the terminal device; the second response instruction is used to notify the terminal device that the service generation system supports the target service.

[0025] In this embodiment, after receiving the second request instruction from the terminal device forwarded by the network device, the service generation system can generate a service context for the target service and determine the service context for the target service. If the network device does not support the target service, the service generation system can allow the terminal device to execute the target service through the service generation system, thereby ensuring the continuity of the terminal device's operation of the target service.

[0026] In one embodiment, before sending the second response instruction to the terminal device, the method further includes: setting the target service to an inactive state; the inactive state means that the relevant resources of one or more network elements supporting the target service are in a dormant state.

[0027] In this embodiment, after the service generation system generates the service context of the target service, it can set the relevant resources of one or more network elements supporting the target service to a dormant state to avoid the relevant resources of one or more network elements supporting the target service being in a working state when the target service is not executed, thereby occupying a large amount of system resources.

[0028] In one embodiment, determining the service context of the target service based on the service context identifier specifically includes: generating a service policy for the target service based on the service context identifier; and configuring relevant resources of each network element that executes the target service based on the service policy of the target service.

[0029] In this embodiment, after receiving the service context identifier of the target service, the service generation system may generate a service policy for the target service so that the service generation system schedules relevant resources of one or more network elements supporting the target service to support the target service.

[0030] In one embodiment, the network element executing the target service includes a service policy network element, an access and mobility function (AMF) network element, a service session management function (SSM) network element, a service user plane function (SUP) network element, and a database. Determining the service context of the target service based on the service context identifier specifically includes: the AMF network element receiving the second request instruction sent by the terminal device; the AMF network element sending a third request instruction to the service policy network element; the third request instruction being used to request the service policy network element to generate a service policy for the target service; the service policy network element sending a fourth request instruction to the database; the fourth request instruction being used to request the database to provide a data pool, a model pool, and a computing pool; and the database sending a fourth response instruction to the service policy network element; the fourth response instruction being used to notify the service policy network element that the database has configured the data pool, the model pool, and the computing pool. The service policy network element sends a fifth request instruction to the service session management function network element; the fifth request instruction is used to request the service session management function network element to establish a traffic channel between the local area, the terminal device, the service policy network element, the AMF network element, the data pool, the model pool and the computing pool on the service user plane function network element; the service session management function network element sends a fifth response instruction to the service policy network element; the fifth response instruction is used to notify the service policy network element that the service session management function network element completes the creation of the traffic channel for the relevant resources of each network element; the service policy network element sends a third response instruction to the AMF network element; the third response instruction is used to notify the AMF network element that the service policy network element completes the generation of the service context of the target service; the AMF network element sends the second response instruction to the terminal device; the second response instruction is used to notify the terminal device that the service generation system supports the target service.

[0031] In one embodiment, the method further includes: receiving an eleventh request instruction sent by a network device; the eleventh request instruction is used to request other network devices to provide a service context corresponding to at least one service context identifier; sending an eleventh response instruction to the network device; the eleventh response instruction includes the service context corresponding to the at least one service context identifier.

[0032] In this embodiment, the service generation system can send the service context of the target service to the network device connected to the terminal device, so that the terminal device can run the target service in the service generation system through the network device, and the network device can support the target service.

[0033] In one embodiment, before receiving the first request instruction sent by the terminal device, the method further includes: receiving the first request instruction sent by the network device; sending service function information to the network device, the service function information including the service type and / or function type that can be provided by each network element supporting the target service, and the service type and / or function type that can be provided by each network element supporting the target service is used to generate a service context of the target service in the network device.

[0034] In this embodiment, when the network device does not support the target service, it can obtain the service type and / or function type that each network element of the target service can provide from the service generation system to construct the service context of the target service, so that the network device can support the target service.

[0035] In a fourth aspect, an embodiment of the present application provides a service generation method, which is executed by a network device, and the method includes: receiving a first request instruction sent by a terminal device; the first request instruction is used to request the network device to support the target service; the first request instruction includes a service context identifier; when it is determined that the service context of the target service does not exist locally, sending a seventh request instruction to the service generation system; the seventh request instruction is used to request the core network to provide service function information supporting the target service, and the service function information includes the service type and / or function type that can be provided by each network element supporting the target service; receiving the service function information sent by the service generation system; determining all or part of the service context of the target service based on the service type and / or function type that can be provided by each network element supporting the target service; the service context of the target service includes relevant resources of one or more network elements supporting the target service.

[0036] In this embodiment, if the network device does not support the target service, it may send a seventh request instruction to the service generation system, requesting the service generation system to send the service types and / or function types that can be provided by each network element supporting the target service to the network device. After obtaining the service types and / or function types that can be provided by each network element supporting the target service, the network device may construct a service context for the target service, so that the network device can run the target service in the service generation system, thereby enabling the network device to support the target service.

[0037] In one embodiment, the method further includes: setting the service context of the target service to an inactive state; the inactive state refers to placing related resources of the one or more network elements supporting the target service in a dormant state.

[0038] In this embodiment, after the network device generates the service context of the target service, it can set the relevant resources of one or more network elements supporting the target service to a dormant state, so as to avoid the relevant resources of one or more network elements supporting the target service being in a working state when the target service is not executed, thereby occupying a large amount of resources of each network element in the core network.

[0039] In one embodiment, the method further includes: determining whether the area identifier in the service context of the target service is the same as the local area identifier when determining that the service context of the target service exists locally; the area identifier is used to distinguish the geographical area in which the service context is effective; and sending a ninth request instruction to the terminal device when the area identifier in the service context of the target service is different from the local area identifier; the ninth request instruction is used to request the terminal device to determine whether the network device regenerates the service context of the target service.

[0040] In this embodiment, a region identifier can be added to the service context constructed by the network device. The network device can determine whether the network device connected to the terminal device has switched by determining whether the region identifier in the service context of the target service is the same as the local region identifier, thereby ensuring the security of the terminal device in executing the target service.

[0041] In one embodiment, the method further includes: receiving an eighth request instruction sent by the terminal device; the eighth request instruction is used to request the network device to execute the target service; and setting the service context of the target service to an activated state.

[0042] In this embodiment, after the network device supports the target service through the service generation system, it can send a service generation instruction to the terminal device to inform the local support of the target service, so that the terminal device can execute the target service through the network device. After receiving the execution instruction from the terminal device, the network device can place the relevant resources of one or more network elements supporting the target service into an operational state, thereby enabling the network device to execute the target service through the service generation system.

[0043] In one embodiment, the method further includes: configuring air interface resources for the terminal device; the air interface resources are used to carry traffic of the target service transmitted between the terminal device and the network device.

[0044] In this embodiment, the network device configures air interface resources for the terminal device. The air interface resources can carry traffic for transmitting the target service between the terminal device and the network device, so that the network device can perform the target service for the terminal device.

[0045] In one embodiment, the method further includes: broadcasting or multicasting a system message; the system message is used to indicate that the network device supports the target service.

[0046] In this embodiment, the network device may broadcast or multicast the locally supported target service to more terminal devices, so that the network device can provide the target service to more terminal devices.

[0047] In one embodiment, a tenth request instruction is sent to the terminal device; the tenth request instruction is used to request a query of the service context in the terminal device; the network device receives a tenth response instruction sent by the terminal device; the tenth response instruction includes at least one service context identifier; the network device updates the service context corresponding to the at least one service context identifier based on the at least one service context identifier.

[0048] In one embodiment, the network device updates the service context corresponding to the at least one service context identifier according to the at least one service context identifier, specifically including: the network device broadcasts an eleventh request instruction; the eleventh request instruction is used to request other network devices to provide the service context corresponding to the at least one service context identifier; the network device receives an eleventh response instruction; the eleventh response instruction includes the service context corresponding to the at least one service context identifier; the network device updates the service context corresponding to the at least one service context identifier according to the service context corresponding to the at least one service context identifier.

[0049] In the fifth aspect, an embodiment of the present application provides a service generation device, including: a transceiver unit, used to send a seventh request instruction to the core network; the seventh request instruction is used to request the core network to provide service function information supporting the target service, and the service function information includes the service type and / or function type that can be provided by each network element supporting the target service; the transceiver unit is also used to receive the service function information sent by the core network; a processing unit, used to determine all or part of the service context of the target service based on the service type and / or function type that can be provided by each network element supporting the target service; the service context of the target service includes relevant resources of one or more network elements supporting the target service.

[0050] In one embodiment, the processing unit is further configured to set the service context of the target service to an inactive state; the inactive state refers to placing related resources of the one or more network elements supporting the target service in a dormant state.

[0051] In one embodiment, the transceiver unit is further used to receive a first request instruction sent by a terminal device; the first request instruction is used to request the target service supported by the network device; the processing unit is further used to detect whether a service context of the target service exists locally; the transceiver unit is further used to send the seventh request instruction to the core network when it is determined that a service context of the target service does not exist locally.

[0052] In one embodiment, the processing unit is further used to determine whether the area identifier in the service context of the target service is the same as the local area identifier when determining that the service context of the target service exists locally; the area identifier is used to distinguish the geographical area in which the service context is effective; when the area identifier in the service context of the target service is different from the local area identifier, send a ninth request instruction to the terminal device; the ninth request instruction is used to request the terminal device to determine whether the network device regenerates the service context of the target service.

[0053] In one embodiment, the transceiver unit is further configured to send a first response instruction to the terminal device; the first response instruction is configured to notify the terminal device that the network device supports the target service.

[0054] In one embodiment, the transceiver unit is further used to receive an eighth request instruction sent by the terminal device; the eighth request instruction is used to request the network device to execute the target service; and the processing unit is further used to set the service context of the target service to an activated state.

[0055] In one embodiment, the processing unit is further configured to configure air interface resources for the terminal device; the air interface resources are used to carry traffic for transmitting the target service between the terminal device and the network device.

[0056] In one embodiment, the transceiver unit is further configured to broadcast or multicast a system message; the system message is configured to indicate that the network device supports a target service.

[0057] In one embodiment, the transceiver unit is further used to send a tenth request instruction to the terminal device; the tenth request instruction is used to request a query of the service context in the terminal device; receive a tenth response instruction sent by the terminal device; the tenth response instruction includes at least one service context identifier; the processing unit is further used to update the service context corresponding to the at least one service context identifier based on the at least one service context identifier.

[0058] In one embodiment, the transceiver unit is specifically used to broadcast an eleventh request instruction; the eleventh request instruction is used to request other network devices to provide the service context corresponding to the at least one service context identifier; the transceiver unit is specifically used to receive an eleventh response instruction; the eleventh response instruction includes the service context corresponding to the at least one service context identifier; the processing unit is specifically used to update the service context corresponding to the at least one service context identifier based on the service context corresponding to the at least one service context identifier.

[0059] In the sixth aspect, an embodiment of the present application provides a service generation device, including: a transceiver unit, used to send a tenth request instruction to a terminal device; the tenth request instruction is used to request a query of the service context in the terminal device; the transceiver unit is also used to receive a tenth response instruction sent by the terminal device; the tenth response instruction includes at least one service context; the transceiver unit is also used to broadcast the eleventh request instruction; the eleventh request instruction is used to request the provision of the service context corresponding to the at least one service context identifier; the transceiver unit is also used to receive an eleventh response instruction; the eleventh response instruction includes the service context corresponding to the at least one service context identifier; a processing unit, used to update the service context corresponding to the at least one service context identifier according to the service context corresponding to the at least one service context identifier.

[0060] In the seventh aspect, an embodiment of the present application provides a service generation device, including: a transceiver unit for receiving a second request instruction sent by a terminal device; the second request instruction is used to request a target service supported by the service generation system, and the second request instruction includes a service context identifier; a processing unit for determining the service context of the target service based on the service context identifier; the service context includes relevant resources of one or more network elements supporting the target service; the transceiver unit is also used to send a second response instruction to the terminal device; the second response instruction is used to notify the terminal device that the service generation system supports the target service.

[0061] In one embodiment, the processing unit is further configured to set the target service to an inactive state; the inactive state refers to placing related resources of one or more network elements supporting the target service in a dormant state.

[0062] In one embodiment, the processing unit is specifically configured to generate a service policy for the target service according to the service context identifier; and configure relevant resources of each network element executing the target service according to the service policy for the target service.

[0063] In one embodiment, the transceiver unit is further used to receive an eleventh request instruction sent by the network device; the eleventh request instruction is used to request other network devices to provide a service context corresponding to at least one service context identifier; and send an eleventh response instruction to the network device; the eleventh response instruction includes the service context corresponding to the at least one service context identifier.

[0064] In one embodiment, the transceiver unit is also used to receive the first request instruction sent by the network device; send service function information to the network device, the service function information including the service type and / or function type that can be provided by each network element supporting the target service, and the service type and / or function type that can be provided by each network element supporting the target service is used to generate the service context of the target service in the network device.

[0065] In the eighth aspect, an embodiment of the present application provides a service generation device, including: a transceiver unit for receiving a first request instruction sent by a terminal device; the first request instruction is used to request the target service supported by the network device; the first request instruction includes a service context identifier; the transceiver unit is also used to send a seventh request instruction to the service generation system when it is determined that the service context of the target service does not exist locally; the seventh request instruction is used to request the core network to provide service function information supporting the target service, and the service function information includes the service type and / or function type that can be provided by each network element supporting the target service; the transceiver unit is also used to receive the service function information sent by the service generation system; a processing unit is used to determine all or part of the service context of the target service based on the service type and / or function type that can be provided by each network element supporting the target service; the service context of the target service includes relevant resources of one or more network elements supporting the target service.

[0066] In one embodiment, the processing unit is further configured to set the service context of the target service to an inactive state; the inactive state refers to placing related resources of the one or more network elements supporting the target service in a dormant state.

[0067] In one embodiment, the processing unit is further used to determine whether the area identifier in the service context of the target service is the same as the local area identifier when determining that the service context of the target service exists locally; the area identifier is used to distinguish the geographical area in which the service context is effective; the transceiver unit is further used to send a ninth request instruction to the terminal device when the area identifier in the service context of the target service is different from the local area identifier; the ninth request instruction is used to request the terminal device to determine whether the network device regenerates the service context of the target service.

[0068] In one embodiment, the transceiver unit is further used to receive an eighth request instruction sent by the terminal device; the eighth request instruction is used to request the network device to execute the target service; and the processing unit is further used to set the service context of the target service to an activated state.

[0069] In one embodiment, the processing unit is further configured to configure air interface resources for the terminal device; the air interface resources are used to carry traffic for transmitting the target service between the terminal device and the network device.

[0070] In one embodiment, the transceiver unit is further configured to broadcast or multicast a system message; the system message is configured to indicate that the network device supports a target service.

[0071] In the ninth aspect, a core network is provided in an embodiment of the present application, comprising: at least one network element, wherein the at least one network element executes the various possible implementation embodiments of the first aspect, or the various possible implementation embodiments of the third aspect.

[0072] In the tenth aspect, a computer-readable storage medium is provided in an embodiment of the present application, characterized in that it includes computer program instructions. When the computer program instructions are executed by the core network, the core network executes each possible implementation embodiment of the first aspect or each possible implementation embodiment of the third aspect.

[0073] In the eleventh aspect, a computer program product comprising instructions is provided in an embodiment of the present application, characterized in that the computer program product stores instructions, and when the instructions are executed by the core network, the core network implements each possible implementation embodiment of the first aspect or each possible implementation embodiment of the third aspect.

[0074] In the twelfth aspect, an embodiment of the present application provides a network device, comprising: at least one memory; at least one processor, the processor being used to execute instructions stored in the memory, so that the network device executes the various possible implementation embodiments of the first aspect, the various possible implementation embodiments of the second aspect, and the various possible implementation embodiments of the fourth aspect.

[0075] In the thirteenth aspect, a computer-readable storage medium is provided in an embodiment of the present application, characterized in that it includes computer program instructions. When the computer program instructions are executed by a network device, the network device executes each possible implementation embodiment of the first aspect, or each possible implementation embodiment of the second aspect, or each possible implementation embodiment of the fourth aspect.

[0076] In the fourteenth aspect, a computer program product comprising instructions is provided in an embodiment of the present application, characterized in that the computer program product stores instructions, which, when executed by a network device, enable the network device to implement each possible implementation embodiment of the first aspect, or each possible implementation embodiment of the second aspect, or each possible implementation embodiment of the fourth aspect.

[0077] In a fifteenth aspect, an embodiment of the present application provides a communication device, comprising: a processor and a memory. The memory stores a computer program or computer instructions, and the processor is configured to call and execute the computer program or computer instructions stored in the memory, so that the processor implements each possible embodiment of the first aspect, each possible embodiment of the second aspect, each possible embodiment of the third aspect, or each possible embodiment of the fourth aspect.

[0078] In one embodiment, the communication device further includes a transceiver, and the processor is configured to control the transceiver to transmit and receive signals.

[0079] In a sixteenth aspect, an embodiment of the present application provides a communication device, comprising a processor. The processor is configured to call a computer program or computer instruction stored therein, so that the processor implements the various possible embodiments of the first aspect, the various possible embodiments of the second aspect, the various possible embodiments of the third aspect, or the various possible embodiments of the fourth aspect.

[0080] In one embodiment, the communication device further includes a transceiver, and the processor is configured to control the transceiver to transmit and receive signals.

[0081] In the seventeenth aspect, a chip device is provided in an embodiment of the present application, including a processor for calling a computer program or computer instruction in the memory so that the processor executes the above-mentioned possible embodiments of the first aspect, or the possible embodiments of the second aspect, or the possible embodiments of the third aspect, or the possible embodiments of the fourth aspect.

[0082] In one embodiment, the processor is coupled to the memory via an interface.

[0083] In an eighteenth aspect, an embodiment of the present application provides a communication system, comprising a core network and a network device. The core network is configured to execute the various possible implementations of the first aspect or the various possible implementations of the third aspect. The network device is configured to execute the various possible implementations of the first aspect, the various possible implementations of the second aspect, or the various possible implementations of the fourth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0084] FIG1 is a schematic diagram of an application scenario of a wireless communication system provided in an embodiment of the present application;

[0085] FIG2 is a schematic diagram of the structure of a service generation system provided in an embodiment of the present application;

[0086] FIG3 is a schematic diagram of a process for constructing a service context by a service generation system provided in an embodiment of the present application;

[0087] FIG4 is a schematic diagram of switching between various states of a target service supported by a service generation system provided in an embodiment of the present application;

[0088] FIG5 is a schematic diagram of a process for a network device to generate a service context according to an embodiment of the present application;

[0089] FIG6 is a flow diagram of a network device update service context provided in an embodiment of the present application;

[0090] FIG7 is a schematic diagram of a process for constructing CSI compression feedback functions of a terminal device, a network device, and a service generation system provided in an embodiment of the present application;

[0091] FIG8 is a schematic structural diagram of a service generation device provided in an embodiment of the present application;

[0092] FIG9 is a schematic structural diagram of another service generation device provided in an embodiment of the present application;

[0093] FIG10 is a schematic structural diagram of a base station provided in an embodiment of the present application. DETAILED DESCRIPTION

[0094] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0095] The term "and / or" as used herein describes an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. The symbol " / " as used herein indicates that the related objects are in an "or" relationship, for example, A / B means either A or B.

[0096] The terms "first" and "second" in this specification and claims are used to distinguish between different objects, rather than to describe a specific order of objects. For example, "first response instruction" and "second response instruction" are used to distinguish between different response instructions, rather than to describe a specific order of response instructions.

[0097] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0098] In the description of the embodiments of the present application, unless otherwise specified, "multiple" means two or more, for example, multiple processing units means two or more processing units, etc.; multiple elements means two or more elements, etc.

[0099] Figure 1 is a schematic diagram of an application scenario of a wireless communication system provided in an embodiment of the present application. As shown in Figure 1 , the wireless communication system 100 may include at least one network device 110, at least one terminal device 120, and at least one AI module 130. The number of network devices 110, terminal devices 120, and AI modules 130 is not limited to the number shown in Figure 1 and may be any number.

[0100] The wireless communication system 100 can be a 5G system, a new radio (NR) system, a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD) system, a universal mobile telecommunication system (UMTS), a future mobile communication system after the 5G network (for example, a 6G mobile communication system), a vehicle to everything (V2X) communication system, a device to device (D2D) communication system, an Internet of Things (IoT) communication system, an industrial Internet communication system, or a satellite communication system, etc., as well as three major application scenarios of the next-generation 5G mobile communication system, namely, an enhanced mobile broadband (eMBB) system, an ultra-reliable and low-latency communication (URLLC) system, and a massive machine type communication (eMTC) system.

[0101] The wireless communication system 100 may be composed of cells. Typically, a cell deploys at least one network device 110, enabling the network device 110 to provide communication services to each terminal device 120 within the cell. The wireless communication system 100 may also enable point-to-point communication, such as allowing multiple terminal devices 120 to communicate with each other.

[0102] The terminal device 120 may be a wireless terminal device capable of receiving network device scheduling information and instruction information. The terminal device 120 may be a device that provides voice and / or data connectivity to a user, or a handheld device with wireless connection function, or other processing device connected to a wireless modem.

[0103] The terminal device 120 is also referred to as user equipment (UE), mobile station (MS), mobile terminal (MT), customer premise equipment (CPE), etc. A terminal device is a device that includes wireless communication capabilities (providing voice / data connectivity to users). For example, it can be a handheld device or vehicle-mounted device with wireless connection capabilities. Currently, some examples of terminal devices include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in the Internet of Vehicles, wireless terminals in self-driving cars, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, and wireless terminals in smart homes. For example, wireless terminals in unmanned driving can be drones, helicopters, or airplanes. For example, wireless terminals in the Internet of Vehicles can be onboard equipment, complete vehicle equipment, onboard modules, vehicles, or ships. Wireless terminals in industrial control can be cameras, robots, or robotic arms. Wireless terminals in smart homes can be televisions, air conditioners, vacuum cleaners, speakers, or set-top boxes.

[0104] It should be noted that the terminal device 120 can be a device or apparatus with a chip, or a device or apparatus with an integrated circuit, or a chip, chip system, module or control unit in the device or apparatus shown above, and this application does not limit this. It should be noted that in this application, when referring to the terminal device 120, it can refer to the terminal device itself, or it can refer to the chip, functional module or integrated circuit in the terminal device that performs the method provided in this application, and this application does not limit this.

[0105] The network device 110 may be a device in a wireless network. For example, the network device 110 may be a device deployed in a radio access network that provides wireless communication capabilities for terminal devices. For example, the network device 110 may be a radio access network (RAN) node that connects the terminal device 120 to the wireless network. The network device 110 may also be referred to as an access network device, a RAN entity, an access node, a network node, or a communication device.

[0106] Specifically, the network device 110 may be an access network device for a cellular system related to the 3rd Generation Partnership Project (3GPP). For example, a 4G communication system, a 5G communication system, etc. The network device 110 may also be an access network device in an open access network (open RAN, O-RAN or ORAN) or a cloud radio access network (CRAN). Alternatively, the network device 110 may also be an access network device in a communication system obtained by integrating two or more of the above communication systems. Alternatively, the network device 110 may also be a satellite in a satellite communication system.

[0107] The network device 110 includes but is not limited to: evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (BBU), access point (AP) in wireless fidelity (WIFI) system, macro base station, micro base station, wireless relay node, donor node, wireless controller in CRAN scenario, wireless backhaul node, transmission point (TP) or transmission and receiving point (TRP), etc., and can also be a network device in a 5G mobile communication system. For example, a next-generation NodeB (gNB), TRP, or TP in an NR system; or one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G mobile communication system; or, the network device 110 may also be a network node constituting a gNB or a transmission point. For example, a centralized unit (CU), a distributed unit (DU), a centralized unit control plane (CU-CP), a centralized unit user plane (CU-UP), or a radio unit (RU). The CU and DU may be configured separately or included in the same network element, such as a BBU. The RU may be included in a radio frequency device or radio frequency unit. For example, in a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH). Alternatively, the network device 110 may also be a server, a wearable device, a vehicle, or an onboard device. For example, the access network device in the V2X technology may be a road side unit (RSU).

[0108] It should be noted that in different systems, CU (or CU-CP and CU-UP), DU or RU may have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU may also be called an open centralized unit (O-CU) or an open CU, DU may also be called an open distributed unit (O-DU), CU-CP may also be called an open centralized unit control plane (O-CU-CP), CU-UP may also be called an open centralized unit user plane (O-CU-UP), and RU may also be called an open radio unit (O-RU). This application does not limit this. Any of the CU, CU-CP, CU-UP, DU and RU in this application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0109] Optionally, for network elements in the ORAN system, each network element may implement the protocol layer functions shown in Table 1 below.

[0110] Table 1

[0111] It should be noted that, in the ORAN system, the network device 110 in this application may be one or more network elements in Table 1 above.

[0112] The following describes the architecture of the CU and DU of an access network device. The access network device includes at least one CU and at least one DU. Optionally, the access network device also includes at least one RU.

[0113] The following is an introduction using the example of an access network device including a CU and a DU. The CU has some functions of the core network, and the CU may include a CU-CP and a CU-UP. The CU and the DU may be configured according to the protocol layer functions of the wireless network they implement. For example, the CU is configured to implement the functions of the packet data convergence protocol (PDCP) layer and the protocol layers above it (for example, the RRC layer and / or the SDAP layer). The DU is configured to implement the functions of the protocol layers below the PDCP layer (for example, the RLC layer, the MAC layer, and / or the physical (PHY) layer). For another example, the CU is configured to implement the functions of the protocol layers above the PDCP layer (such as the RRC layer and / or the SDAP layer), and the DU is configured to implement the functions of the PDCP layer and the protocol layers below it (for example, the RLC layer, the MAC layer, and / or the PHY layer, etc.).

[0114] When a CU includes a CU-CP and a CU-UP, the CU-CP is used to implement the control plane functions of the CU, and the CU-UP is used to implement the user plane functions of the CU. For example, when the CU is configured to implement the functions of the PDCP layer, RRC layer, and SDAP layer, the CU-CP is used to implement the RRC layer functions and the control plane functions of the PDCP layer, and the CU-UP is used to implement the SDAP layer functions and the user plane functions of the PDCP layer.

[0115] The CU-CP can interact with network elements in the core network that implement control plane functions. The network elements in the core network that implement control plane functions can be access and mobility function network elements, such as the access and mobility management function (AMF) in the 5G system. The access and mobility function network element is responsible for mobility management in the mobile network, such as location update of terminal devices, registration network of terminal devices, and switching of terminal devices.

[0116] The CU-UP can interact with network elements in the core network that implement user plane functions. Network elements in the core network that implement user plane functions, such as the user plane function (UPF) in the 5G system, are responsible for forwarding and receiving data in terminal devices.

[0117] The above configuration of CU and DU is only an example, and the functions of CU and DU can also be configured as needed. For example, the CU or DU can be configured to have the functions of more protocol layers, or the CU or DU can be configured to have partial processing functions of the protocol layer. For example, some functions of the RLC layer and the functions of the protocol layers above the RLC layer are set in the CU, and the remaining functions of the RLC layer and the functions of the protocol layers below the RLC layer are set in the DU. For another example, the functions of the CU or DU can be divided according to the service type or other system requirements. For example, according to the delay, the functions whose processing time needs to meet the smaller delay requirement are set in the DU, and the functions that do not need to meet the delay requirement are set in the CU.

[0118] The DU and RU can work together to implement the functions of the PHY layer. A DU can be connected to one or more RUs. The functions of the DU and RU can be configured in various ways according to the design. For example, the DU is configured to implement the baseband function, and the RU is configured to implement the mid-RF function. For another example, the DU is configured to implement the high-layer functions in the PHY layer, and the RU is configured to implement the low-layer functions in the PHY layer or to implement the low-layer functions and the RF functions. The high-layer functions in the physical layer may include a part of the functions of the physical layer, which is closer to the MAC layer, and the low-layer functions in the physical layer may include another part of the functions of the physical layer, which is closer to the mid-RF side.

[0119] Network device 110 may also be a core network device. For example, network device 110 may be a control plane functional entity including an access and mobility management function (AMF) or a session management function (SMF). The AMF is responsible for user access management, security authentication, mobility management, and other functions. The data plane functional entity includes the UPF. The UPF is responsible for managing user plane data transmission, traffic statistics, and other functions.

[0120] It should be noted that the network device 110 can be a device or apparatus with a chip, or a device or apparatus with an integrated circuit, or a chip, chip system, module or control unit in the aforementioned device or apparatus, and this application does not limit this. It should be noted that in this application, when referring to the network device 110, it can refer to the network device 110 itself, or it can refer to the chip, functional module or integrated circuit in the network device 110 that performs the method provided in this application, and this application does not limit this.

[0121] AI module 130 refers to a device that runs an AI model to perform functions such as data collection, data processing, and model training. AI module 130 can be a component in network device 110, meaning the AI ​​model is deployed on network device 110. AI module 130 can also be a component in terminal device 120, meaning the AI ​​model is deployed on terminal device 120. AI module 130 can be an independent component, such as a core network element, that has wireless communication capabilities, enabling AI module 130 to communicate with both network device 110 and terminal device 120. AI models are machine learning models used in the field of artificial intelligence that can automatically learn and adapt to patterns and regularities in diverse data sets. AI models can be trained on large amounts of data, learning features and relationships, and then used to solve various intelligent tasks. AI models can be applied to a variety of fields and tasks, such as natural language processing, computer vision, speech recognition, and intelligent recommendation. Common AI models include neural network models (such as deep neural networks and recursive neural networks), support vector machine models, and decision tree models. In an embodiment of the present application, the AI ​​module 130 can perform functions such as data collection, data processing, and model training, so that the device to which the AI ​​module 130 belongs has all or part of the AI ​​functions.

[0122] In an embodiment of the present application, when the network device 110 does not have the AI ​​service required by the terminal device 120, the network device 110 can maintain the relevant resources of one or more network elements that support the AI ​​service (or AI function) through the core network. The core network builds AI services for the network device 110 so that the network device 110 can provide AI services for the terminal device 120. The core network is an important component of the mobile communication network, which is responsible for processing and managing user data, signaling and control information in the mobile network. The core network is generally composed of multiple network elements, and the core network relies on each network element to realize data processing, forwarding and control.

[0123] The service generation system provided in this application is run by the core network. The service generation system can build a specified target service by maintaining the relevant resources of the relevant network elements in the core network. The target service may refer to the above-mentioned AI service, or it may be other types of services. The service generation system can maintain the relevant resources of one or more network elements of the target service, so that the network device 110 and the service generation system can provide the target service to the terminal device 120 together. Among them, the target service can be channel state information (CSI) compression feedback, cell reselection, cell selection and other services.

[0124] For the convenience of description, the present application may refer to the related resources of one or more network elements that the service generation system needs to maintain to support one or more target services as "service context".

[0125] Figure 2 is a schematic diagram of an application scenario of a service generation system provided in an embodiment of the present application. As shown in Figure 2, service generation system 200 may include a service strategy network element 210, an AMF network element 220, a service-session management function (Service-SMF) network element 230, a service-user plane function (Service-UPF) network element 240, a database 250, and an over-the-top interface (OTT interface) 260.

[0126] The specific physical hardware of each network element in service generation system 200 can be the aforementioned network device 110, the aforementioned terminal device 120, or other types of physical hardware. Alternatively, service generation system 200 can be the aforementioned core network device. In this case, service strategy network element 210, AMF network element 220, and Service-SMF network element 230 can be functional entities on the control plane of the core network device. Service-UPF network element 240 and database 250 can be functional entities on the data plane of the core network device.

[0127] The service policy network element 210 is used to make decisions about the target service and can serve as an anchor node (or anchor network element) for the target service. The service policy network element 210 can provide support for obtaining the target service context for services in an inactive state. In an embodiment of the present application, the service policy network element 210 can provide a decision-making function for the AI ​​service. The service policy generally includes parameters related to maintaining the AI ​​service, such as the AI ​​service identifier, the service context identifier of the AI ​​service, the node identifier participating in the AI ​​service, the node access address, the regional description of the AI ​​service, the quality description of the AI ​​service, etc.

[0128] The AMF network element 220 is used to control the connection and mobility management between the core network and the terminal device 120. In the embodiment of the present application, the AMF network element 220 can serve as a bridge between the terminal device 120 and the service generation system 200 to transmit data between the terminal device 120 and each network element of the service generation system 200.

[0129] The Service-SMF network element 230 is used to manage sessions related to the target service, such as establishing and maintaining traffic channels for traffic transmission between various network elements related to target services such as data and models, and maintaining channel parameters (such as allocating IP addresses, channel addresses, etc.). In the embodiment of the present application, the Service-SMF network element 230 can manage sessions related to AI services to establish and maintain traffic channels for traffic transmission between various network elements related to AI services, and maintain the allocation of IP addresses (Internet Protocols) and channel addresses for the traffic channels.

[0130] The Service-UPF network element 240 is used to provide user plane transmission for the target service. In the embodiment of the present application, the Service-UPF network element 240 can provide user plane transmission for the AI ​​service.

[0131] The database 250 may include a data pool 251, a model pool 252, and a computation pool 253. The data pool 251, the model pool 252, and the computation pool 253 may be located on one network element or on a number of other network elements.

[0132] The data pool 251 is used to maintain data sets, intermediate results of training / inference, and corresponding identifiers. In the embodiment of the present application, the data pool 251 can be used to maintain data sets, intermediate results of training / inference of AI models, service context identifiers, and other data.

[0133] The model pool 252 is used to maintain model parameters and corresponding identifiers. In the embodiment of the present application, the model pool 252 can maintain the AI ​​model parameters of the AI ​​service, the identifier of the AI ​​model, etc.

[0134] The computing pool 253 is used to schedule the computing resources of each node in the network, to support a certain service function, and to maintain computing resources and corresponding identifiers. In an embodiment of the present application, the computing pool 253 can schedule the computing resources of each network element in the service generation system 200, to support AI services, to maintain computing resources for AI services, and to identify each resource.

[0135] The OTT interface 260 is used to provide an interface for third-party data, models, etc., and maintain the interface address, description of incoming network traffic, etc.

[0136] For example, FIG3 is a flow chart of the service context construction of the service generation system provided in an embodiment of the present application. It can be understood that the service context of the target service can be implemented by the network device 110, the terminal device 120, and the service generation system 200. The network elements involved in the service generation system 200 may include the service policy network element 210, the AMF network element 220, the Service-SMF network element 230, the Service-UPF network element 240, and the database 250. The specific process of the service generation system 200 constructing the service context of the target service is as follows:

[0137] In step S301, the terminal device 120 sends a first request instruction to the network device 110. The first request instruction is a service request instruction, which is used to request a target service supported by the network device 110.

[0138] In step S302, the network device 110 sends a first response instruction to the terminal device 120. The first response instruction is an instruction in response to the first request instruction, and is used to notify the terminal device 120 that the network device 110 supports the target service or does not support the target service.

[0139] Optionally, in the ORAN system, the network device 110 in the above steps S301-S302 may be an O-CU-CP network element, an O-DU network element and / or an O-RU network element shown in Table 1 above.

[0140] When terminal device 120 needs to execute a target service, it can send a first request instruction to network device 110 to request a target service supported by network device 110. After receiving the first request instruction, network device 110 can determine whether the target service is supported locally based on the service context identifier carried in the first request instruction. In one case, if network device 110 supports the target service, it can send a first response instruction to terminal device 120 to notify terminal device 120 that network device 110 supports the target service. In another case, if network device 110 does not support the target service, it can send a first response instruction to terminal device 120 to notify terminal device 120 that network device 110 does not support the target service.

[0141] In step S303, the terminal device 120 sends a second request instruction to the AMF network element 220. The second request instruction is a service request instruction for requesting the core network to support a target service. In this embodiment, the second request instruction is used to request a target service supported by the service generation system 200.

[0142] In step S304, AMF network element 220 sends a third request instruction to service policy network element 210. The third request instruction is a service policy request instruction used to request the core network to generate a service policy for the target service. In this embodiment, the third request instruction is used to request service policy network element 210 to generate a service policy for the target service.

[0143] Optionally, when the terminal device 120 sends a third request instruction to the AMF network element 220 through the network device 110 in the above step S303, the network device 110 can RAN.

[0144] When the terminal device 120 determines that the network device 110 does not support the target service, it can send a second request instruction to the AMF network element 220 through the network device 110. After receiving the second request instruction, the AMF network element 220 generates a third request instruction and sends the third request instruction to the service policy network element 210.

[0145] In step S305, service policy network element 210 sends a fourth request instruction to database 250. This fourth request instruction is a service configuration request instruction, requesting the core network to provide relevant resources for each network element. In this embodiment, the fourth request instruction is used to request database 250 in service generation system 220 to provide data pool 251, model pool 252, and computation pool 253.

[0146] In step S306, database 250 sends a fourth response instruction to service policy network element 210. This fourth response instruction is a response to the fourth request instruction and is used to notify the core network to complete the provision of relevant resources for each network element. In this embodiment, the fourth response instruction is used to notify service policy network element 210 that database 250 has configured data pool 251, model pool 252, and computation pool 253.

[0147] Service policy network element 210 is the control center of service generation system 200. After receiving the third request instruction, it can generate a service policy for the target service based on the third request instruction. After obtaining the service policy for the target service, service policy network element 210 can configure the relevant resources of each network element in service generation system 200 to support the target service. During the configuration process, service policy network element 210 can send a fourth request instruction to database 250, requesting that database 250 provide a data pool 251, a model pool 252, and a computing pool 253 to support the target service. After receiving the fourth request instruction, database 251 can create data pool 251, model pool 252, and computing pool 253. Data pool 251 can be used to maintain data sets, intermediate results of model training and inference, service context identifiers, and other data. Model pool 252 can be used to maintain model parameters and model identifiers for the target service. Computing pool 253 can be used to schedule computing resources of each network element in service generation system 200 to support and maintain the computing resources of the target service, as well as the identifiers of each resource. After completing the creation of the data pool 251 , the model pool 252 and the calculation pool 253 , the database 250 sends a fourth response instruction to the service policy network element 210 , notifying the service policy network element 210 that the database 250 configures the data pool 251 , the model pool 252 and the calculation pool 253 .

[0148] In step S307, service policy network element 210 sends a fifth request instruction to service-SMF network element 230. The fifth request instruction is a request instruction for creating a traffic channel, which is used to request the core network to create a traffic channel for the relevant resources of each network element. In this embodiment, the fifth request instruction is used to request Service-SMF network element 230 in service generation system 220 to establish a traffic channel on Service-UPF network element 240 between the local terminal device 120, service policy network element 210, AMF network element 220, data pool 251, model pool 252, and computing pool 253.

[0149] In step S308, the Service-SMF network element 230 sends a fifth response instruction to the service policy network element 210. The fifth response instruction is a response to the fifth request instruction and is used to notify the core network to complete the creation of traffic channels for the relevant resources of each network element. In this embodiment, the fifth response instruction is used to notify the service policy network element 210 that the Service-SMF network element 230 has completed the creation of traffic channels for the relevant resources of each network element.

[0150] After the service policy network element 210 creates the data pool 251, the model pool 252, and the computing pool 253, it can send a fifth request instruction to the Service-SMF network element 230, requesting the Service-SMF network element 230 to manage the relevant sessions for the target service. The Service-SMF network element 230 can create a traffic channel for the network elements that need to interact with traffic, that is, establish a traffic channel between the network device 110, the AMF network element 220, the Service-SMF network element 230, the service policy network element 210, the data pool 251, the model pool 252, and the computing pool 253, so that the network device 110, the AMF network element 220, the Service-SMF network element 230, the service policy network element 210, the data pool 251, the model pool 252, and the computing pool 253 can transmit traffic to each other. The Service-SMF network element 230 can also establish a traffic channel between the terminal device 120 and the Service-UPF network element 240, so that traffic can be transmitted between the terminal device 120 and the Service-UPF network element 240, allowing the terminal device 120 to access other network elements in the service generation system 200 through the Service-UPF network element 240, and perform traffic transmission.

[0151] The Service-UPF network element 240 is the network element that performs traffic forwarding, so the traffic channels between the network device 110, the terminal device 120, the data pool 251, the model pool 252, and the computing pool 253 are all established on the Service-UPF network element 240. The Service-UPF network element 240 can forward traffic from the network element at one end of the traffic channel to the network element at the other end, enabling communication between the two network elements.

[0152] After Service-SMF network element 230 completes establishing traffic channels between various network elements, it can send a service session response instruction to Service-SMF network element 210, requesting that Service-SMF network element 230 complete establishing traffic channels between various network elements. After receiving the service session response instruction, Service-SMF network element 210 determines that the configuration of relevant resources for each network element executing the target service is complete. Service-SMF network element 210 can generate a service context for the target service based on the relevant resources of each network element executing the target service and store it in local storage.

[0153] In step S309, the service policy network element 210 sends a third response instruction to the AMF network element 220. The third response instruction is an instruction in response to the third request instruction, and is used to notify the core network to complete the generation of the service context of the target service. In an embodiment, the third response instruction is used to notify the AMF network element 220 that the service policy network element 210 has completed the generation of the service context of the target service.

[0154] In step S310, the AMF network element 220 sends a second response instruction to the terminal device 120. The second response instruction is an instruction in response to the second request instruction, and is used to notify the terminal device 120 that the service generation system 200 supports the target service.

[0155] After completing the generation of the service context for the target service, service policy network element 210 may send a third response instruction to AMF network element 220, notifying AMF network element 220 that service policy network element 210 has completed the generation of the service context for the target service. After receiving the third response instruction, AMF network element 220 may convert it into a second response instruction, notifying terminal device 120 that service generation system 200 supports the target service. After receiving the second response instruction via network device 110, terminal device 120 determines that service generation system 200 has generated the service context for the target service and may execute the target service in service generation system 200 via network device 110. If terminal device 120 needs to execute the target service, it may send a sixth request instruction to service generation system 200 via network device 110. The sixth request instruction is used to request service generation system 200 to execute the target service, thereby enabling service generation system 200 to provide the target service to terminal device 120.

[0156] In an embodiment of the present application, when the network device 110 does not support the target service, the terminal device 120 can generate a service context for the target service through the service generation system 200, so that the network device 120 can implement the target service through the service generation system 200 and ensure the continuity of running the target service.

[0157] The service policy network element 210 can support the target service in one of the following states: service setup, inactive, active, and service release. The service setup state refers to the state in which the service policy network element 210 coordinates the startup parameters for each network element to start the target service. These parameters can include model scale, model input and output, service performance, and so on. When the service policy network element 210 is in the service setup state, each network element has not yet generated a service context for implementing the target service.

[0158] The inactive state means that the service policy network element 210 puts the resources related to each network element of the target service into a dormant state. At this time, the service policy network element 210 can determine that each network element generates a service context based on the startup parameters and stores it in a local memory. When the service policy network element 210 is in the inactive state, each network element will not provide the target service to the terminal device 120, and each network element can update the service context. Among them, there are two ways for the service generation system 200 to cache the service context, namely:

[0159] The service policy network element 210 can centrally store the service context of each network element supporting the target service in local storage, so that each network element does not need to cache the service context. When the target service enters the active state, the service policy network element 210 can distribute the stored service context to each network element, allowing each network element to load and run.

[0160] The service policy network element 210 can instruct each network element supporting the target service to cache the service context locally, so that the service context is distributedly stored in each network element. When the target service enters the activated state, the service policy network element 210 can instruct each network element to load and run.

[0161] The activation state refers to the state where the service policy network element 210 starts the target service based on the service context. At this time, the service policy network element 210 can enable the terminal device 120 to execute the target service and enable each network element to update the service context.

[0162] The service release state refers to a state in which the service policy network element 210 allows each network element to cancel the service context of the target service.

[0163] The various states of the target service supported by the service policy network element 210 can be switched between. As shown in Figure 4, the service generation state of the service policy network element 210 can be switched between the inactive state and the active state, the inactive state and the active state, the service generation state of the service policy network element 210 can be switched to the service release state, the inactive state of the service policy network element 210 can be switched to the service release state, and the active state of the service policy network element 210 can be switched to the service release state.

[0164] In the embodiment of the present application, when the terminal device 120 determines that the network device 110 does not support the target service, the terminal device 120 can construct a service context that supports the target service through the network device 110. After receiving the first request instruction, the network device 110 first aligns parameters with each network element of the core network to ensure normal operation and coordinated operation of the network device 110 and each network element of the core network.

[0165] Figure 5 is a flow chart of a network device generating a service context according to an embodiment of the present application. As shown in Figure 5, the network device 110 generally works in conjunction with the terminal device 120 and the core network to generate a service context. The specific implementation process is as follows:

[0166] In step S501, the terminal device 120 sends a first request instruction to the network device 110. The first request instruction is a service request instruction, which is used to request a target service supported by the network device 110.

[0167] In step S502, the network device 110 detects whether a service context of the target service exists locally. In one case, the network device 110 determines that a service context of the target service does not exist locally, and then executes step S503. In another case, the network device 110 determines that a service context of the target service exists locally, and then executes step S506.

[0168] After receiving the first request instruction sent by the terminal device 120, the network device 110 can detect whether a service context corresponding to the service context identifier exists locally based on the service context identifier carried by the first request instruction. In one case, when the network device 110 determines that a service context corresponding to the service context identifier exists locally, it can determine the service context of the target service. In another case, when the network device 110 determines that there is no service context corresponding to the service context identifier locally or there is no complete service context corresponding to the service context identifier, it can forward the first request instruction to the core network, or send a seventh request instruction to the core network to request the core network to obtain service function information of each network element that supports the target service.

[0169] In step S503, the network device 110 sends the first request instruction or the seventh request instruction to the core network. The seventh request instruction is a request instruction for obtaining service function information, and is used to request the core network to provide service function information supporting the target service.

[0170] Step S504 : The core network sends service function information to the network device 110 .

[0171] If network device 110 receives the first request instruction, it may directly transparently transmit the first request instruction to the core network. If network device 110 receives the seventh request instruction, network device 110 may send the seventh request instruction to the core network via the RAN. Within the core network, the first request instruction and the seventh request instruction have the same function: obtaining service function information of the target service. The core network may be the aforementioned service generation system 200. Service generation system 200 may forward the first request instruction or the seventh request instruction to service policy network element 210. Service policy network element 210 may determine the service function information of each network element based on the service context identifier carried by the first request instruction or the seventh request instruction, and send the service function information to network device 110. The service function information includes the service types and / or function types that each network element supporting the target service can provide. Service types may include training, inference, data acquisition, and other service types. Function types may include enabling features of the target service, such as channel estimation, beam management, and mobility management.

[0172] In step S505 , the network device 110 generates a full or partial service context of the target service according to the service function information.

[0173] In step S506, the network device 110 sends a first response instruction to the terminal device 120. The first response instruction is an instruction in response to the first request instruction, and is used to notify the terminal device 120 that the network device 110 supports the target service.

[0174] After obtaining the service types and function types that each network element in the core network can provide, network device 110 can locally configure the service parameters of the target service, such as model configuration, data set configuration, computing resources, parameter version numbers, operating environment information, etc. Based on the service parameters of the target service and the service context identifier carried in the first request instruction, network device 110 can generate a full or partial service context for the target service and set the service context status of the target service to an inactive state. If the service context generated by network device 110 is a partial service context for the target service, the partial service context for the target service refers to the relevant resources involved in supporting the target service by network device 110.

[0175] After network device 110 completes generating the service context for the target service, it may send a first response instruction to terminal device 120. After receiving the first response instruction, terminal device 120 determines that network device 110 has generated the service context for the target service and may execute the target service on network device 110 and / or the core network. If terminal device 120 needs to execute the target service, it may send an eighth request instruction to the core network through network device 110. The eighth request instruction is used to request network device 110 and / or the core network to execute the target service, thereby enabling network device 110 to provide the target service to terminal device 120. At this point, network device 110 sets the service context for the target service to an active state.

[0176] After generating a target service supported, the network device 110 may broadcast or multicast a system message. The system message is used to indicate the target service supported by the network device 110. The system message includes relevant configuration information of the target service. The configuration information may include the identification (ID) of the target service, the mapping configuration of the logical transport channel (LTCH) and the physical downlink shared channel (PDSCH) and / or the physical uplink shared channel (PUSCH) used to carry the service traffic of the target service, and the configuration information of each protocol layer.

[0177] After receiving the system message, terminal device 120 can determine whether it needs the target service of network device 110 based on local needs. If terminal device 120 needs the target service of network device 110, it can send interest information to network device 110 to inform network device 110 that terminal device 120 needs the target service of network device 110. After receiving the interest information, network device 110 can know the target service of terminal device 120, identify the model and / or function corresponding to the target service, and set the target service to an active state, so that terminal device 120 can execute the target service through network device 110.

[0178] Optionally, in the ORAN system, the network device 110 in the above steps S501-S506 may be an O-CU-CP network element, an O-DU network element and / or an O-RU network element shown in Table 1 above.

[0179] In an embodiment of the present application, a region identifier may be added to the service context constructed by network device 110. The region identifier is used to distinguish the geographical area in which the service context is effective. It can be the ID of network device 110, the address of the area where network device 110 is located, or other identifier that distinguishes network device 110. Network device 110 can locally construct a dedicated service context based on the region identifier and the service context identifier. Terminal device 120 generally carries the service context identifier (i.e., service context ID) of the target service to be executed. After terminal device 120 switches from one network device 110 to another, it sends the service context identifier to the switched network device 110. After receiving the service context identifier, network device 110 determines the service context corresponding to the service context identifier and determines whether the region identifier in the service context corresponding to the service context identifier is the same as the local region identifier. If network device 110 determines that the region identifier in the service context corresponding to the service context identifier is not the same as the local region identifier, the local service context providing the target service has changed. Upon noticing the change in the region identifier, network device 110 confirms that the locally held service context is not suitable for providing the target service for the newly arrived terminal device 120.

[0180] After network device 110 determines that the service context providing the target service for terminal device 120 has changed, it may send a ninth request instruction to terminal device 120. The ninth request instruction is used to request terminal device 120 to determine whether network device 110 should regenerate the service context for the target service. After receiving the ninth request instruction, terminal device 120 may resend the first request instruction, the second request instruction, or another request instruction to the switched network device 110 to request the switched network device 110 to regenerate the service context for the target service, or request the switched network device 110 to regenerate the service context for the target service in other ways, so that terminal device 120 can execute the target service through the switched network device 110. Alternatively, terminal device 120 may send a pause instruction to the switched network device 110 to instruct the switched network device 110 to suspend maintaining the service context and instruct terminal device 120 to stop executing the target service.

[0181] When a terminal device 120 switches from one network device 110 to another, it can send a service context identifier to the new network device 110. After receiving the service context identifier, the new network device 110 determines whether a service context corresponding to the service context identifier exists locally. If the new network device 110 does have a corresponding service context, the terminal device 120 can be added to a service session maintained by the local service context. If the new network device 110 does not have a corresponding service context, the terminal device 120 can be broadcast or multicast to other network devices 110 to locate a network device 110 with a corresponding service context. After locating a network device 110 with a corresponding service context, the new network device 110 can obtain the corresponding service context from the other network device 110 and set the status of the corresponding service context to active. The new network device 110 can then add the terminal device 120 to the service session maintained by the local service context, allowing the terminal device 120 to execute the target service through the new network device 110.

[0182] After the handover, network device 110 can configure a unicast link for terminal device 120 based on the local resource status, or connect terminal device 120 to an existing multicast or broadcast link, thereby configuring air interface resources for terminal device 120 to carry the traffic of the transmission service. During the handover process from one network device 110 to another, terminal device 120 can obtain the service context from the network based on the service context identifier, ensuring the continuity of the target service running on terminal device 120.

[0183] FIG6 is a flow chart of a network device updating a service context according to an embodiment of the present application. As shown in FIG6 , the process of updating the service context of the network device 110 is as follows:

[0184] In step S601 , the network device 110 sends a tenth request instruction to the terminal device 120 . The tenth request instruction is a service query request instruction, which is used to query the service context in the terminal device 120 .

[0185] In step S602, the terminal device 120 sends a tenth response instruction to the network device 110. The tenth response instruction is an instruction in response to the tenth request instruction, and is used to provide the service context identifier that the terminal device 120 needs to update. The tenth response instruction includes the service context identifier that the terminal device 120 needs to update.

[0186] When network device 110 needs to update its locally maintained service context, it can initiate a service context update function and send a tenth request instruction to terminal device 120, requesting a query for the service context in terminal device 120. After receiving the tenth request instruction, terminal device 120 can send a tenth response instruction to network device 110 based on the service context that needs to be updated. The tenth response instruction carries an identifier of the service context that needs to be updated by terminal device 120, so that after receiving the tenth response instruction, network device 110 can obtain the service context that needs to be updated by terminal device 120. The tenth response instruction also carries state information of the target service, so that after the network device updates the service context, it can set the updated service context to the corresponding state based on the state information.

[0187] In step S603, network device 110 detects whether a service context corresponding to the service context identifier carried in the tenth response instruction exists locally. In one case, if network device 110 determines that a service context corresponding to the service context identifier carried in the tenth response instruction exists locally, step S606 is executed. In another case, if network device 110 determines that a service context corresponding to the service context identifier carried in the tenth response instruction does not exist locally, step S604 is executed.

[0188] Step S604: The network device 110 sends an eleventh request instruction to the anchor node. The anchor node is the network device 110 that can construct the service context corresponding to the service context identifier. The eleventh request instruction is used to request other network devices to provide the service context corresponding to the service context identifier carried in the tenth response instruction.

[0189] Step S605: The anchor node sends an eleventh response instruction to the network device 110. The eleventh response instruction is an instruction in response to the eleventh request instruction, and is used to provide the service context corresponding to the service context identifier carried by the tenth response instruction. The eleventh response instruction includes the service context corresponding to the service context identifier carried by the tenth response instruction.

[0190] After receiving the tenth response instruction, the network device 110 can detect whether a corresponding service context exists locally based on the service context identifier carried by the tenth response instruction. In one case, when the network device 110 determines that a service context corresponding to the service context identifier carried by the tenth response instruction exists locally, the network device 110 can maintain the service context corresponding to the service context identifier. In another case, when the network device 110 determines that there is no service context corresponding to the service context identifier carried by the tenth response instruction locally or there is no complete service context corresponding to the service context identifier carried by the tenth response instruction, the network device 110 can broadcast the eleventh request instruction to other network devices 110, requesting the other network devices 110 to provide the service context of the service context identifier carried by the tenth response instruction. The eleventh request instruction carries the service context identifier carried by the tenth response instruction so that the other network devices 110 can provide the corresponding service context.

[0191] After determining that a service context corresponding to the service context exists locally based on the service context identifier carried by the tenth response instruction, other network devices 110 may send an eleventh response instruction to network device 110 to send the service context corresponding to the service context identifier carried by the tenth response instruction to network device 110.

[0192] In step S606 , the network device 110 updates the service context.

[0193] After obtaining the service context corresponding to the service context identifier carried by the tenth response instruction, the network device 110 may maintain the corresponding service context and set the state of the service context to the state indicated by the state information carried by the tenth response instruction, thereby updating the service context.

[0194] Optionally, in the ORAN system, the network device 110 in the above steps S601-S605 may be an O-CU-CP network element, an O-DU network element and / or an O-RU network element shown in Table 1 above.

[0195] The following uses CSI compression feedback as an example to introduce an implementation scenario of the embodiment of the present application.

[0196] FIG7 is a flow chart of the terminal device, network device, and service generation system provided in an embodiment of the present application for constructing the CSI compression feedback function. As shown in FIG7 , the process of constructing the CSI compression feedback function of the terminal device 120, network device 110, and service generation system 200 is as follows:

[0197] In step S701, the terminal device 120 sends a twelfth request instruction to the network device 110. The function of the twelfth request instruction may be similar to that of the first request instruction, and is used to request the network device 110 to support the CSI compression feedback function.

[0198] CSI compression feedback refers to compressing CSI information in wireless communication systems through certain methods, thereby reducing the resource overhead required for CSI feedback. When terminal device 120 requires the CSI compression feedback function, it can send a twelfth request instruction to network device 110, requesting network device 110 to maintain the service context for the CSI compression feedback function.

[0199] In step S702, the network device 110 sends a thirteenth request instruction to the service generation system 200. The function of the thirteenth request instruction is similar to that of the seventh request instruction, and is used to request the service function information of the service generation system 200 that supports CSI compression feedback.

[0200] Step S703: the service generation system 200 sends a thirteenth response instruction to the network device 110. The function of the thirteenth request instruction may be similar to that of the service function information, and may carry service function information of the supported CSI compression feedback function.

[0201] Similarly, the specific implementation process of steps S701-S703 can refer to the process of steps S501-S504 in Figure 5, which is specifically as follows: after the network device 110 receives the twelfth request instruction, it first detects whether there is a service context for the CSI compression feedback function locally. In one case, the network device 110 determines that there is a service context for the CSI compression feedback function locally, and there is no need to perform steps S702-S703. In another case, the network device 110 determines that there is no service context for the CSI compression feedback function locally, and can send a thirteenth request instruction to the service generation system 200 to obtain the service function information of the CSI compression feedback function supported by the service generation system 200. After receiving the thirteenth request instruction, the service generation system 200 determines the service function information of each network element that supports the CSI compression feedback function based on the service context identifier of the CSI compression feedback function carried by the thirteenth request instruction, and sends the service function information to the network device 110.

[0202] Step S704 : The network device 110 generates a CSI compression feedback function.

[0203] In step S705 , the network device 110 updates the local service context.

[0204] After obtaining the service function information from the service generation system 200, the network device 110 can locally configure the service parameters for the CSI compression feedback function. Based on the service parameters for the CSI compression feedback function and the service context identifier for the CSI compression feedback function carried in the twelfth request instruction, the network device 110 can generate all or part of the service context for the CSI compression feedback function, and maintain the service context for the CSI compression feedback function, so that the network device 110 supports the CSI compression feedback function. At this point, the network device 110 can set the service context for the CSI compression feedback function to an inactive state.

[0205] In step S706, the network device 110 sends a twelfth response instruction to the terminal device 120. The function of the twelfth response instruction may be similar to that of the first response instruction, and is used to notify the terminal device 120 that the network device 110 supports the CSI compression feedback function.

[0206] After obtaining the service context for the CSI compression feedback function, network device 110 may maintain the service context for the CSI compression feedback function and execute the CSI compression feedback function to ensure the continuity of the CSI compression feedback function executed by terminal device 120. After having the CSI compression feedback function, network device 110 may send a twelfth response instruction to terminal device 120 to inform terminal device 120 that the current network device 110 has the CSI compression feedback function.

[0207] Step S707 : The network device 110 activates the CSI compression feedback function.

[0208] After determining that network device 110 is capable of providing CSI compression feedback, terminal device 120 may send an execution instruction to the network device to enable execution of the CSI compression feedback function via network device 120 and / or service generation system 200. At this point, network device 110 may set the service context state of the CSI compression feedback function to an active state, enabling the CSI compression feedback function to operate normally.

[0209] Optionally, in the ORAN system, the network device 110 in the above steps S701-S707 may be an O-CU-CP network element, an O-DU network element and / or an O-RU network element shown in Table 1 above.

[0210] In other embodiments, the function of the twelfth request instruction may be similar to that of the second request instruction, and may be used to request the service generation system 200 to support the CSI compression feedback function. In this case, the network device 110 only forwards the twelfth request instruction, that is, the thirteenth request instruction and the twelfth request instruction are combined into one request instruction.

[0211] After receiving the thirteenth request instruction, service generation system 200 may generate a service context that supports the CSI compression feedback function. The specific implementation process may refer to steps S305-S309 in Figure 3. Specifically, as follows: For example, service generation system 200 may include a service policy network element 210, an AMF network element 220, a service-SMF network element 230, a service-UPF network element 240, and a database 250. Service policy network element 210 generates a service policy for the CSI compression feedback function based on the service context identifier carried in the third request instruction. Service policy network element 210 may send a fourth request instruction to database 250, requesting that the database provide a data pool 251, a model pool 252, and a computation pool 253 that support the target service. After receiving the fourth request instruction, database 251 may create data pool 251, model pool 252, and computation pool 253.

[0212] After the service policy network element 210 creates the data pool 251, the model pool 252, and the computing pool 253, it requests the Service-SMF network element 230 to manage the related sessions for the CSI compression feedback function. The Service-SMF network element 230 can establish a traffic channel between the network device 110, the AMF network element 220, the Service-SMF network element 230, the service policy network element 210, the data pool 251, the model pool 252, and the computing pool 253, so that the network device 110, the AMF network element 220, the Service-SMF network element 230, the service policy network element 210, the data pool 251, the model pool 252, and the computing pool 253 can transmit traffic to each other, and establish a traffic channel between the terminal device 120 and the Service-UPF network element 240, so that the terminal device 120 and the Service-UPF network element 240 can transmit traffic. The service policy network element 210 may generate a service context for the CSI compression feedback function based on relevant resources of each network element that performs the CSI compression feedback function, and send the context to the network device 110 .

[0213] At this time, the thirteenth response instruction is used to request the service generation system 200 to support the CSI compression feedback function, and then the network device 110 directly executes steps S706-S707.

[0214] In another embodiment, the function of the thirteenth request instruction can be similar to that of the eleventh request instruction, and is used to request that another network device 110, terminal device 120, or service generation system 200 generate a service context that supports the CSI compression feedback function. For a specific implementation process, reference can be made to steps S603-S605 in FIG6 . In this case, the thirteenth response instruction carries the service context that supports the CSI compression feedback function, and then the network device 110, terminal device 120, and service generation system 200 directly execute steps S704-S707.

[0215] In the embodiment of the present application, when the terminal device 120 executes the CSI compression feedback function through the network device 110, if the network device 110 does not support the CSI compression feedback function, a service context for the CSI compression feedback function can be established through the network device 110 and / or the service generation system 200. After obtaining the service context for the CSI compression feedback function, the network device 110 can support the CSI compression feedback function to ensure the continuity of the CSI compression feedback function executed by the terminal device 120.

[0216] Figure 8 is a schematic diagram of the structure of a service generation device provided in an embodiment of the present application. As shown in Figure 8, service generation device 800 can execute the processes performed by the network device or core network in the embodiments shown in Figures 3, 5, 6, and 7. For details, please refer to the relevant descriptions in the above method embodiments. Service generation device 800 can be divided into a transceiver unit 810 and a processing unit 820 based on the execution function.

[0217] The transceiver unit 810 can implement corresponding communication functions and can also be called a communication interface or a communication module.

[0218] The processing unit 820 is used for performing data processing.

[0219] Optionally, the service generating apparatus 800 may further include a storage unit, which may be used to store instructions and / or data. The processing unit 820 may read the instructions and / or data in the storage unit so that the service generating apparatus 800 implements the aforementioned method embodiment.

[0220] The service generation device 800 can be used to execute the actions performed by the network device in the above method embodiments. The service generation device 800 can be a network device or a component configurable on a network device. The processing unit 820 is used to execute the processing-related operations on the network device side in the above method embodiments. The transceiver unit 810 is used to execute the reception-related operations on the network device side in the above method embodiments.

[0221] Alternatively, the service generation device 800 can be used to perform the actions performed by the core network in the above method embodiments. The service generation device 800 can be the core network or a component configurable in the core network. The processing unit 820 is used to perform the processing-related operations on the core network side in the above method embodiments. The transceiver unit 810 is used to perform the reception-related operations on the core network side in the above method embodiments.

[0222] Optionally, the transceiver unit 810 may include a sending unit and a receiving unit. The sending unit is configured to perform the sending operation in the above method embodiment. The receiving unit is configured to perform the receiving operation in the above method embodiment.

[0223] It should be noted that the service generation device 800 may include a sending unit but not a receiving unit. Alternatively, the communication device 800 may include a receiving unit but not a sending unit. The specific implementation depends on whether the above solution executed by the service generation device 800 includes a sending action and a receiving action.

[0224] In another case, the service generation device 800 may perform the functions of the service generation system 200 (ie, the core network) described in FIG. 3 , specifically:

[0225] The transceiver unit 810 is configured to receive a second request instruction sent by a terminal device. The second request instruction is used to request a target service supported by the service generation system, and the second request instruction includes a service context identifier. The processing unit 820 is configured to determine a service context for the target service based on the service context identifier. The service context includes relevant resources of one or more network elements that support the target service. The transceiver unit 810 is further configured to send a second response instruction to the terminal device. The second response instruction is used to notify the terminal device that the service generation system supports the target service.

[0226] In one embodiment, the processing unit 820 is further configured to set the target service to an inactive state. The inactive state refers to placing related resources of one or more network elements supporting the target service in a dormant state.

[0227] In one embodiment, the processing unit 820 is specifically configured to generate a service policy for the target service according to the service context identifier, and configure relevant resources of each network element that executes the target service according to the service policy for the target service.

[0228] In one embodiment, the transceiver unit 810 is further configured to receive an eleventh request instruction sent by the network device. The eleventh request instruction is configured to request another network device to provide a service context corresponding to at least one service context identifier. The transceiver unit 810 is further configured to send an eleventh response instruction to the network device. The eleventh response instruction includes the service context corresponding to the at least one service context identifier.

[0229] In one embodiment, the transceiver unit 810 is further configured to receive a first request instruction sent by the network device. The transceiver unit 810 is further configured to send service function information to the network device. The service function information includes the service types and / or function types that can be provided by each network element supporting the target service. The service types and / or function types that can be provided by each network element supporting the target service are used to generate a service context for the target service in the network device.

[0230] In another case, the service generating device 800 may perform the functions of the network device 110 described in FIG. 5 , specifically:

[0231] The transceiver unit 810 is used to receive a first request instruction sent by a terminal device. The first request instruction is used to request a target service supported by a network device. The first request instruction includes a service context identifier. The transceiver unit 810 is also used to send a seventh request instruction to the service generation system when it is determined that the service context of the target service does not exist locally. The seventh request instruction is used to request the core network to provide service function information that supports the target service, and the service function information includes the service type and / or function type that can be provided by each network element supporting the target service. The transceiver unit 810 is also used to receive service function information sent by the service generation system. The processing unit 820 is used to determine all or part of the service context of the target service based on the service type and / or function type that can be provided by each network element supporting the target service. The service context of the target service includes relevant resources of one or more network elements that support the target service.

[0232] In one embodiment, the processing unit 820 is further configured to set the service context of the target service to an inactive state. The inactive state refers to placing related resources of one or more network elements supporting the target service in a dormant state.

[0233] In one embodiment, the processing unit 820 is further configured to determine whether the region identifier in the service context of the target service is the same as the local region identifier when determining that a service context of the target service exists locally. The region identifier is used to distinguish the geographical area in which the service context is effective. The transceiver unit 810 is further configured to send a ninth request instruction to the terminal device when the region identifier in the service context of the target service is different from the local region identifier. The ninth request instruction is used to request the terminal device to determine whether the network device should regenerate the service context of the target service.

[0234] In one embodiment, the transceiver unit 810 is further configured to receive an eighth request instruction sent by the terminal device. The eighth request instruction is used to request the network device to execute the target service. The processing unit 820 is further configured to set the service context of the target service to an active state.

[0235] In one embodiment, the transceiver unit 810 is further configured to configure air interface resources for the terminal device. The air interface resources are used to carry traffic for transmitting target services between the terminal device and the network device.

[0236] In one embodiment, the transceiver unit 810 is further configured to broadcast or multicast a system message. The system message is used to indicate that the network device supports a target service.

[0237] In another case, the service generating apparatus 800 may perform the functions of the network device 110 described in FIG6 , specifically:

[0238] The transceiver unit 810 is configured to send a tenth request instruction to the terminal device. The tenth request instruction is configured to request a query for a service context in the terminal device. The transceiver unit 810 is further configured to receive a tenth response instruction sent by the terminal device. The tenth response instruction includes at least one service context. The transceiver unit 810 is further configured to broadcast an eleventh request instruction. The eleventh request instruction is configured to request provision of a service context corresponding to at least one service context identifier. The transceiver unit 810 is further configured to receive the eleventh response instruction. The eleventh response instruction includes a service context corresponding to at least one service context identifier. The processing unit 820 is configured to update the service context corresponding to the at least one service context identifier based on the service context corresponding to the at least one service context identifier.

[0239] In one case, the service generating apparatus 800 may perform the functions of the network device 110 described in FIG. 3 , FIG. 5 , FIG. 6 , and FIG. 7 , specifically:

[0240] The transceiver unit 810 is used to send a seventh request instruction to the core network. The seventh request instruction is used to request the core network to provide service function information supporting the target service, and the service function information includes the service type and / or function type that each network element supporting the target service can provide. The transceiver unit 810 is also used to receive the service function information sent by the core network. The processing unit 820 is used to determine all or part of the service context of the target service based on the service type and / or function type that each network element supporting the target service can provide. The service context of the target service includes relevant resources of one or more network elements supporting the target service.

[0241] In one embodiment, the processing unit 820 is further configured to set the service context of the target service to an inactive state. The inactive state refers to placing related resources of one or more network elements supporting the target service in a dormant state.

[0242] In one embodiment, the transceiver unit 810 is further configured to receive a first request instruction sent by a terminal device. The first request instruction is used to request a target service supported by the network device. The processing unit 820 is further configured to detect whether a service context for the target service exists locally. The transceiver unit 810 is further configured to send a seventh request instruction to the core network if it determines that a service context for the target service does not exist locally.

[0243] In one embodiment, the processing unit 820 is further configured to determine whether the region identifier in the service context of the target service is the same as the local region identifier when determining that a service context of the target service exists locally. The region identifier is used to distinguish the geographical area in which the service context is effective. The transceiver unit 810 is further configured to send a ninth request instruction to the terminal device when the region identifier in the service context of the target service is different from the local region identifier. The ninth request instruction is used to request the terminal device to determine whether the network device should regenerate the service context of the target service.

[0244] In one embodiment, the transceiver unit 810 is further configured to send a first response instruction to the terminal device. The first response instruction is used to notify the terminal device that the network device supports the target service.

[0245] In one embodiment, the transceiver unit 810 is further configured to receive an eighth request instruction sent by the terminal device. The eighth request instruction is used to request the network device to execute the target service. The processing unit 820 is further configured to set the service context of the target service to an active state.

[0246] In one embodiment, the processing unit 820 is further configured to configure air interface resources for the terminal device. The air interface resources are used to carry traffic for transmitting target services between the terminal device and the network device.

[0247] In one embodiment, the transceiver unit 810 is further configured to broadcast or multicast a system message. The system message is used to request the network device to support a target service.

[0248] In one embodiment, the transceiver unit 810 is further configured to send a tenth request instruction to the terminal device. The tenth request instruction is configured to query the service context in the terminal device. The transceiver unit 810 is further configured to receive a tenth response instruction sent by the terminal device. The tenth response instruction includes at least one service context identifier. The processing unit 820 is further configured to update the service context corresponding to the at least one service context identifier based on the at least one service context identifier.

[0249] In one embodiment, the transceiver unit 810 is specifically configured to broadcast an eleventh request instruction. The eleventh request instruction is configured to request another network device to provide a service context corresponding to at least one service context identifier. The transceiver unit 810 is specifically configured to receive an eleventh response instruction. The eleventh response instruction includes a service context corresponding to the at least one service context identifier. The processing unit 820 is specifically configured to update the service context corresponding to the at least one service context identifier based on the service context corresponding to the at least one service context identifier.

[0250] Figure 9 is a schematic diagram of the structure of another service generation device provided in an embodiment of the present application. As shown in Figure 9, the present application also provides a service generation device 900, which can be a network device or a chip. Service generation device 900 can be used to perform the operations performed by the network device in any of the embodiments shown in Figures 3, 5, 6, and 7, or to perform the operations performed by the core network device in any of the embodiments shown in Figures 3 and 7.

[0251] When the service generating device 900 is a network device, for example, a base station, FIG9 shows a simplified schematic diagram of a base station structure. The base station includes parts 910, 920, and 930.

[0252] Part 910 is mainly used for baseband processing, base station control, etc.; Part 910 is usually the control center of the base station, which can usually be called a processor, used to control the base station to perform the processing operations on the network device side in the above method embodiment.

[0253] The 920 section is mainly used to store computer program codes and data. The 930 section is mainly used to transmit and receive radio frequency signals and convert radio frequency signals into baseband signals.

[0254] Section 930 can generally be referred to as a transceiver unit, transceiver, transceiver circuit, or transceiver. The transceiver unit in section 930, which can also be referred to as a transceiver or transceiver, includes an antenna 933 and a radio frequency circuit (not shown), where the radio frequency circuit is primarily used for radio frequency processing. Optionally, the device used to implement the receiving function in section 930 can be considered a receiver, and the device used to implement the transmitting function can be considered a transmitter. That is, section 930 includes a receiver 932 and a transmitter 931. The receiver can also be referred to as a receiving unit, receiver, or receiving circuit, and the transmitter can be referred to as a transmitting unit, transmitter, or transmitting circuit.

[0255] Sections 910 and 920 may include one or more boards, each of which may include one or more processors and one or more memories. The processor is used to read and execute programs in the memory to implement baseband processing functions and control the base station. If multiple boards are present, the boards may be interconnected to enhance processing capabilities. As an optional implementation, multiple boards may share one or more processors, multiple boards may share one or more memories, or multiple boards may simultaneously share one or more processors.

[0256] For example, the transceiver module in part 930 is used to execute the transceiver-related process performed by the network device in any of the embodiments shown in Figures 3, 5, 6, and 7. The processor in part 910 is used to execute the processing-related process performed by the network device in any of the embodiments shown in Figures 3, 5, 6, and 7.

[0257] It should be understood that FIG9 is merely an example and not a limitation, and the network device including the processor, memory, and transceiver may not rely on the structure shown in FIG8 .

[0258] When the service generation device 900 is a chip, the chip includes a transceiver, a memory, and a processor. The transceiver can be an input / output circuit or a communication interface; the processor can be a processor, microprocessor, or integrated circuit integrated on the chip. The sending operation of the network device in the above method embodiment can be understood as the chip's output, and the receiving operation of the network device in the above method embodiment can be understood as the chip's input.

[0259] An embodiment of the present application also provides a chip device, including a processor, for calling the computer program or computer instructions stored in the memory so that the processor executes the method provided in any of the embodiments shown in Figures 3, 5, 6, and 7 above.

[0260] In one possible implementation, the input of the chip device corresponds to the receiving operation in any one of the embodiments shown in Figures 3, 5, 6, and 7 above, and the output of the chip device corresponds to the sending operation in any one of the embodiments shown in Figures 3, 5, 6, and 7 above.

[0261] Optionally, the processor is coupled to the memory via an interface.

[0262] Optionally, the chip device further includes a memory, in which computer programs or computer instructions are stored.

[0263] The processor mentioned in any of the above may be a general-purpose central processing unit, a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the method provided in any of the embodiments shown in Figures 3, 5, 6, and 7. The memory mentioned in any of the above may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM), etc.

[0264] In the case where the service generation device 900 is a base station, Figure 10 is a schematic diagram of the structure of a base station provided in an embodiment of the present application. As shown in Figure 10, the functions of the network device 110 in the service generation method embodiments corresponding to Figures 3, 5, 6, and 7 are performed. Base station 1000 may include one or more DUs 1010 and one or more CUs 1020. DUs 1010 may include at least one antenna 1011, at least one radio frequency unit 1012, at least one processor 1013, and at least one memory 1014. DUs 1010 are primarily used for transmitting and receiving radio frequency signals, converting radio frequency signals into baseband signals, and performing partial baseband processing. CUs 1020 may include at least one processor 1021 and at least one memory 1022. CUs 1020 and DUs 1010 may communicate via interfaces, where the control plane interface may be an Fs-C, such as F1-C, and the user plane interface may be an Fs-U, such as F1-U.

[0265] The CU 1020 is primarily responsible for baseband processing and base station control. The DU 1010 and CU 1020 can be physically located together or separately, i.e., in a distributed base station. The CU 1020 is the control center of the base station, also known as a processing unit, and is primarily responsible for performing baseband processing functions. For example, the CU 1020 can be used to control the base station 1000 to execute the operational procedures for the network device 110 in the above-described method embodiment.

[0266] Specifically, baseband processing on the CU and DU can be divided according to the protocol layers of the wireless network. For example, the functions of the PDCP layer and above are set in the CU, and the functions of the protocol layers below PDCP, such as the RLC and MAC layers, are set in the DU. For another example, the CU implements the functions of the RRC and PDCP layers, and the DU implements the functions of the RLC, MAC, and PHY layers.

[0267] In addition, optionally, the base station 1000 may include one or more radio frequency units (RUs), one or more DUs, and one or more CUs. The DU may include at least one processor 1013 and at least one memory 1014, the RU may include at least one antenna 1011 and at least one radio frequency unit 1012, and the CU may include at least one processor 1021 and at least one memory 1022.

[0268] In one example, the CU 1020 may be composed of one or more single boards, and the multiple single boards may jointly support a wireless access network with a single access indication (such as a 6G network), or may respectively support wireless access networks with different access standards (such as an LTE network, a 6G network, or other networks). The processor 1021 and the memory 1022 may serve one or more single boards. That is, a memory and a processor may be separately set on each single board. It is also possible that multiple single boards share the same memory and processor. In addition, necessary circuits may be provided on each single board. The DU 801 may be composed of one or more single boards, and the multiple single boards may jointly support a wireless access network with a single access indication (such as a 6G network), or may respectively support wireless access networks with different access standards (such as an LTE network, a 6G network, or other networks). The memory 1014 and the processor 1013 may serve one or more single boards. That is, a memory and a processor may be separately set on each single board. It is also possible that multiple single boards share the same memory and processor. In addition, necessary circuits may be provided on each single board.

[0269] Among them, the DU and the CU can jointly perform the functions of the processor 920 in the service generating device 900 shown in Figure 9, and the details are not repeated here.

[0270] A computer-readable storage medium is also provided in an embodiment of the present application, including computer program instructions. When the computer program instructions are executed by the core network, the core network executes any one of the methods recorded in Figures 3, 7 and the corresponding description content.

[0271] A computer-readable storage medium is also provided in an embodiment of the present application, including computer program instructions. When the computer program instructions are executed by a network device, the network device executes any one of the methods recorded in Figures 3, 5, 6, 7 and the corresponding description content.

[0272] An embodiment of the present application also provides a computer program product containing instructions, characterized in that the computer program product stores instructions, and when the instructions are executed by the core network, the core network implements any one of the methods recorded in Figures 3, 7 and the corresponding description content.

[0273] An embodiment of the present application also provides a computer program product containing instructions, characterized in that the computer program product stores instructions, and when the instructions are executed by a network device, the network device implements any one of the methods recorded in Figures 3, 5, 6, 7 and the corresponding description content.

[0274] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the embodiments of this application.

[0275] In addition, various aspects or features of the embodiments of the present application can be implemented as methods, devices or products using standard programming and / or engineering techniques. The term "product" as used in this application covers computer programs that can be accessed from any computer-readable device, carrier or medium. For example, computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks or tapes, etc.), optical disks (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards and flash memory devices (e.g., erasable programmable read-only memories (EPROMs), cards, sticks or key drives, etc.). In addition, the various storage media described herein may represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing and / or carrying instructions and / or data.

[0276] In the above embodiment, the service generation device 800 in Figure 8 can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state drive (SSD)).

[0277] It should be understood that in various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0278] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0279] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0280] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0281] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or an access network device, etc.) to execute all or part of the steps of the method described in each embodiment of the embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

[0282] The above is only a specific implementation of the embodiment of the present application, but the protection scope of the embodiment of the present application is not limited to this. Any technician familiar with this technical field can easily think of changes or replacements within the technical scope disclosed in the embodiment of the present application, and they should all be covered by the protection scope of the embodiment of the present application.

Claims

1. A service generation method, characterized in that: The method is performed by a network device and a core network, and the method includes: The network device sends a seventh request instruction to the core network; the seventh request instruction is used to request the core network to provide service function information supporting the target service, and the service function information includes the service type and / or function type that can be provided by each network element supporting the target service; The core network receives the seventh request instruction and sends the service function information to the network device; The network device determines all or part of the service context of the target service according to the service type and / or function type that each network element supporting the target service can provide; the service context of the target service includes relevant resources of one or more network elements supporting the target service.

2. The method according to claim 1, characterized in that The method further comprises: The network device sets the service context of the target service in an inactive state; the inactive state refers to placing related resources of one or more network elements supporting the target service in a dormant state.

3. The method according to claim 1 or 2, characterized in that: Before the network device sends the seventh request instruction to the core network, the method further includes: The network device receives a first request instruction sent by a terminal device; the first request instruction is used to request the target service supported by the network device; The network device detects whether a service context of the target service exists locally; The network device sends a seventh request instruction to the core network, specifically including: When the network device determines that the service context of the target service does not exist locally, the network device sends the seventh request instruction to the core network.

4. The method according to claim 3, characterized in that The method further comprises: When the network device determines that the service context of the target service exists locally, it determines whether the area identifier in the service context of the target service is the same as the local area identifier; the area identifier is used to distinguish the geographical area where the service context is effective; When the area identifier in the service context of the target service is different from the local area identifier, the network device sends a ninth request instruction to the terminal device; the ninth request instruction is used to request the terminal device to determine whether the network device should regenerate the service context of the target service.

5. The method according to claim 3 or 4, characterized in that: The method further comprises: The network device sends a first response instruction to the terminal device; the service response instruction is used to notify the terminal device that the network device supports the target service.

6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: The network device receives an eighth request instruction sent by the terminal device; the eighth request instruction is used to request the network device to execute the target service; The network device sets the service context of the target service to an active state.

7. The method according to any one of claims 1 to 6, characterized in that: The method further comprises: The network device configures air interface resources for the terminal device; the air interface resources are used to carry the traffic of the target service transmitted between the terminal device and the network device.

8. The method according to any one of claims 1 to 7, characterized in that: The method further comprises: The network device broadcasts or multicasts a system message; the system message is used to indicate that the network device supports a target service.

9. The method according to any one of claims 1 to 8, characterized in that: The method further comprises: The network device sends a tenth request instruction to the terminal device; the tenth request instruction is used to request to query the service context in the terminal device; The network device receives a tenth response instruction sent by the terminal device; the tenth response instruction includes at least one service context identifier; The network device updates the service context corresponding to the at least one service context identifier according to the at least one service context identifier.

10. The method according to claim 9, characterized in that The network device updating, according to the at least one service context identifier, a service context corresponding to the at least one service context identifier, specifically includes: The network device broadcasts an eleventh request instruction; the eleventh request instruction is used to request other network devices to provide the service context corresponding to the at least one service context identifier; The network device receives an eleventh response instruction; the eleventh response instruction includes a service context corresponding to the at least one service context identifier; The network device updates the service context corresponding to the at least one service context identifier according to the service context corresponding to the at least one service context identifier.

11. A service generating device, characterized in that: include: A transceiver unit, configured to send a seventh request instruction to the core network; The seventh request instruction is used to request the core network to provide service function information supporting the target service, wherein the service function information includes the service type and / or function type that can be provided by each network element supporting the target service; The transceiver unit is further configured to receive the service function information sent by the core network; A processing unit, configured to determine all or part of the service context of the target service according to the service type and / or function type that can be provided by each network element supporting the target service; The service context of the target service includes related resources of one or more network elements supporting the target service.

12. The device according to claim 11, characterized in that The processing unit is further used to set the service context of the target service to an inactive state; the inactive state refers to placing related resources of one or more network elements supporting the target service in a dormant state.

13. The device according to claim 11 or 12, characterized in that The transceiver unit is further used to receive a first request instruction sent by a terminal device; the first request instruction is used to request the target service supported by the network device; The processing unit is further used to detect whether a service context of the target service exists locally; The transceiver unit is further configured to send a seventh request instruction to the core network when it is determined that the service context of the target service does not exist locally.

14. The device according to claim 13, characterized in that The processing unit is further used to determine whether the area identifier in the service context of the target service is the same as the local area identifier when determining that the service context of the target service exists locally; the area identifier is used to distinguish the geographical area where the service context is effective; When the area identifier in the service context of the target service is different from the local area identifier, sending a ninth request instruction to the terminal device; The ninth request instruction is used to request the terminal device to determine whether the network device regenerates the service context of the target service.

15. The device according to claim 13 or 14, characterized in that The transceiver unit is also used A first response instruction is sent to the terminal device; the first response instruction is used to notify the terminal device that the network device supports the target service.

16. The device according to any one of claims 11 to 15, characterized in that: The transceiver unit is further used to receive an eighth request instruction sent by the terminal device; the eighth request instruction is used to request the network device to execute the target service; The processing unit is further configured to set the service context of the target service to an activated state.

17. The device according to any one of claims 11 to 16, characterized in that: The processing unit is also used Air interface resources are configured for the terminal device; the air interface resources are used to carry the traffic of the target service transmitted between the terminal device and the network device.

18. The device according to any one of claims 11 to 17, characterized in that: The transceiver unit is further used to broadcast or multicast system messages; the system messages are used to indicate that the network device supports the target service.

19. The device according to any one of claims 1 to 8, characterized in that: The transceiver unit is further used to send a tenth request instruction to the terminal device; the tenth request instruction is used to request to query the service context in the terminal device; receiving a tenth response instruction sent by the terminal device; the tenth response instruction includes at least one service context identifier; The processing unit is further configured to update the service context corresponding to the at least one service context identifier according to the at least one service context identifier.

20. The device according to claim 19, characterized in that The transceiver unit is specifically used to broadcast an eleventh request instruction; the eleventh request instruction is used to request other network devices to provide the service context corresponding to the at least one service context identifier; The transceiver unit is specifically configured to receive an eleventh response instruction; the eleventh response instruction includes a service context corresponding to the at least one service context identifier; The processing unit is specifically configured to update the service context corresponding to the at least one service context identifier according to the service context corresponding to the at least one service context identifier.

21. A network device, characterized in that: include: at least one transceiver; At least one processor, wherein the processor is configured to execute instructions stored in the memory so that the network device executes the method according to any one of claims 1 to 10.

22. A computer-readable storage medium, characterized in that: The method comprises computer program instructions. When the computer program instructions are executed by a network device, the network device performs the method according to any one of claims 1 to 10.

Images