Service generation method and device and network equipment
By executing service generation methods in wireless network devices and core networks, building a service context for AI services, the problem that wireless network devices cannot provide unsupported AI services is solved, and AI service continuity and network resource management of terminal devices are realized.
Patent Information
- Application Number
- CN202311758790.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-12-19
- Publication Date
- 2025-06-20
AI Technical Summary
Existing wireless network devices cannot provide AI services to terminal devices without supporting a certain AI service that terminal devices need to perform.
By executing a service generation method in the network device and/or the core network, the network device sends request instructions to the core network to obtain service function information that supports the target service, builds a service context for the target service, and sets the relevant resources to hibernate if necessary to save resources.
It realizes that network equipment provides AI services to terminal devices without supporting target services, ensures the continuity of AI services of terminal devices, and effectively manages network resources.
Smart Images

Figure CN120186584A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of communication technologies, and in particular, to a service generation method, apparatus, and network device. Background Art
[0002] In order to cope with the vision of future intelligent inclusion, the wireless network architecture can be evolved intelligently. For example, artificial intelligence (AI) can be deeply integrated with the wireless network, so that the wireless network can not only provide traditional communication connection services, but also provide computing and AI services, and enable terminal devices to have certain AI capabilities. If the network does not have a certain AI service that the terminal device needs to execute, the network cannot provide the AI service for the terminal device. Summary of the Invention
[0003] To solve the above problems, embodiments of the present application provide a service generation method. When a network device does not support a certain service that a terminal device needs to execute, the network device and / or the core network provide the certain service for the terminal device. In addition, the present application also provides a service generation apparatus and a network device corresponding to the service generation method.
[0004] Therefore, the following technical solutions are adopted in the embodiments of the present application:
[0005] In a first aspect, embodiments of the present application provide a service generation method, which is executed by a network device and a core network. 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 a target service, and the service function information includes service types and / or function types that each network element supporting the target service can provide; after receiving the seventh request instruction, the core network 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 types and / or function types 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.
[0006] In this embodiment, when the network device does not support the target service, it can send a seventh request instruction to the core network, requesting the core network to send the service types and / or function types that each network element supporting the target service can provide to the network device. After obtaining the service types and / or function types that each network element supporting the target service can provide, the network device can construct the service context of the target service, so that the network device can run the target service in the core network, realizing that the network device can support the target service.
[0007] In one embodiment, the method further includes: the network device sets the service context of 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.
[0008] 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, avoiding the relevant resources of one or more network elements supporting the target service from being in a working state when the target service is not being executed, so as to occupy a large amount of resources of each network element in the core network.
[0009] In one embodiment, before the network device sends a seventh request instruction to the core network, the method further includes: the network device receives a first request instruction sent by the terminal device; the first request instruction is used to request the target service supported by the network device; the network device detects whether there is a service context of the target service locally; the network device sending the seventh request instruction to the core network specifically includes: when the network device determines that there is no service context of the target service locally, sending the seventh request instruction to the core network.
[0010] In one embodiment, the method further includes: when the network device determines that there is a service context of the target service locally, determining 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 takes effect; 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.
[0011] 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 whether the region identifier in the service context of the target service is the same as the local region identifier, ensuring the security of the terminal device when executing the target service.
[0012] In one embodiment, the method further includes: the network device sends 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.
[0013] 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. The network device can send a first response instruction to the terminal device, enabling the terminal device to execute the target service through the network device.
[0014] In one embodiment, the method further includes: 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 the active state.
[0015] 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 that the target service is locally supported, so that the terminal device can execute the target service through the network device. After the network device receives the execution instruction from the terminal device, it can place the relevant resources of one or more network elements that support the target service in the working state, realizing that the network device executes the target service through the core network.
[0016] In one embodiment, the method further includes: the network device configures radio resources for the terminal device; the radio resources are used to carry the traffic of the target service transmitted between the terminal device and the network device.
[0017] In this embodiment, the network device configures radio resources for the terminal device, and the radio resources can carry the traffic of the target service transmitted between the terminal device and the network device, realizing that the network device executes the target service for the terminal device.
[0018] In one embodiment, the method further includes: the network device broadcasts or multicasts system messages; indicating that the network device supports the target service.
[0019] In this embodiment, the network device can broadcast or multicast the local support for the target service to more terminal devices, realizing that the network device can provide the target service for more terminal devices.
[0020] In one embodiment, 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.
[0021] In one embodiment, the network device updates the service context corresponding 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.
[0022] In a second aspect, an embodiment of the present application provides a service generation method, which is executed by a network device. The method includes: sending a tenth request instruction to a terminal device; the tenth request instruction is used to request to query the service context in the terminal device; receiving the 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 to provide the service context corresponding to the at least one service context identifier; receiving an eleventh response instruction; the eleventh response instruction includes the service context corresponding to the at least one service context identifier; updating 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 third aspect, an embodiment of the present application provides a service generation method, which is executed by a service generation system. 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; determining the service context of the target service according to the service context identifier; 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.
[0024] In this embodiment, after receiving the second request instruction of the terminal device forwarded by the network device, the service generation system can generate the service context of the target service and determine the service context of the target service. When 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, ensuring the continuity of the terminal device running the target service.
[0025] In one implementation, 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.
[0026] In this implementation, 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, avoiding the relevant resources of one or more network elements supporting the target service from being in a working state when not executing the target service, so as to occupy a large amount of system resources.
[0027] In one implementation, determining the service context of the target service according to the service context identifier specifically includes: generating the service policy of the target service according to the service context identifier; configuring the relevant resources of each network element executing the target service according to the service policy of the target service.
[0028] In this implementation, after receiving the service context identifier of the target service, the service generation system can generate the service policy of the target service, so that the service generation system can schedule the relevant resources of one or more network elements supporting the target service to support the target service.
[0029] In one embodiment, the network element that executes the target service includes a service policy network element, an access and mobility management function (AMF) network element, a service session management function network element, a service user plane function network element, and a database. Determining the service context of the target service according to the service context identifier specifically includes: the AMF network element receives the second request instruction sent by the terminal device; the AMF network element sends a third request instruction to the service policy network element; the third request instruction is used to request the service policy network element to generate the service policy of the target service; the service policy network element sends a fourth request instruction to the database; the fourth request instruction is used to request the database to provide a data pool, a model pool, and a computing pool.; the database sends a fourth response instruction to the service policy network element; the fourth response instruction is used to notify the service policy network element that the database has configured a data pool, a model pool, and a 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 has completed the creation of the traffic channels 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 has completed 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.
[0030] 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 the 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.
[0031] 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, realizing that the network device can support the target service.
[0032] In one embodiment, before the first request instruction sent by the receiving terminal device, the method further includes: receiving the first request instruction sent by the network device; sending service function information to the network device, where the service function information includes service types and / or function types that each network element supporting the target service can provide, and the service types and / or function types that each network element supporting the target service can provide are used to generate a service context of the target service in the network device.
[0033] In this embodiment, when the network device does not support the target service, it can obtain the service types and / or function types that each network element of the target service can provide from the service generation system to construct a service context of the target service, so that the network device can support the target service.
[0034] 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; in the case where it is determined that there is no service context of the target service locally, sending a seventh request instruction to a service generation system; the seventh request instruction is used to request the core network to provide service function information supporting the target service, where the service function information includes service types and / or function types that each network element supporting the target service can provide; receiving the service function information sent by the service generation system; determining all or part of the service context of the target service according to the service types and / or function types 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.
[0035] In this embodiment, when the network device does not support the target service, it can send a seventh request instruction to the service generation system to request the service generation system to send the service types and / or function types that each network element supporting the target service can provide to the network device. After the network device obtains the service types and / or function types that each network element supporting the target service can provide, it can construct a service context of the target service, so that the network device can run the target service in the service generation system, and the network device can support the target service.
[0036] In one embodiment, the method further includes: setting the service context of 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.
[0037] 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 the sleep state, avoiding the relevant resources of one or more network elements supporting the target service being in the working state when the target service is not being executed, so as to occupy a large amount of resources of each network element in the core network.
[0038] In one embodiment, the method further includes: when it is determined that the service context of the target service exists locally, determining 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 takes effect; 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.
[0039] In this embodiment, a regional 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 comparing the regional identifier in the service context of the target service with the local regional identifier, ensuring the security of the terminal device when executing the target service.
[0040] 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; setting the service context of the target service to the active state.
[0041] 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 that the target service is supported locally, so that the terminal device can execute the target service through the network device. After the network device receives the execution instruction from the terminal device, it can put the relevant resources of one or more network elements supporting the target service into the working state, realizing the network device to execute the target service through the service generation system.
[0042] In one embodiment, the method further includes: configuring radio resources for the terminal device; the radio resources are used to carry the traffic of the target service transmitted between the terminal device and the network device.
[0043] In this embodiment, the network device configures radio resources for the terminal device, and the radio resources can carry the traffic of the target service transmitted between the terminal device and the network device, realizing the network device to execute the target service for the terminal device.
[0044] In one embodiment, the method further includes: broadcasting or multicasting system messages; the system messages are used to indicate that the network device supports a target service.
[0045] In this embodiment, the network device can broadcast or multicast the local support for the target service to more terminal devices, so that the network device can provide the target service for more terminal devices.
[0046] In one embodiment, a tenth request instruction is sent 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 the 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.
[0047] 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, which 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 the 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.
[0048] In a fifth aspect, an embodiment of the present application provides a service generation device, including: 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 a target service, and the service function information includes the service types and / or function types that each network element supporting the target service can provide; 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 types and / or function types 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.
[0049] 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 means that the relevant resources of one or more network elements supporting the target service are in a dormant state.
[0050] In one embodiment, the transceiver unit is further configured 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 configured to detect whether there is a service context of the target service locally; the transceiver unit is further configured to, when it is determined that there is no service context of the target service locally, send the seventh request instruction to the core network.
[0051] In one embodiment, the processing unit is further configured to, when it is determined that there is a service context of the target service locally, determine 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 takes effect; 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.
[0052] In one embodiment, the transceiver unit 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.
[0053] In one embodiment, the transceiver unit 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 is further configured to set the service context of the target service to an active state.
[0054] In one embodiment, the processing unit is further configured to configure radio resources for the terminal device; the radio resources are used to carry the traffic of the target service transmitted between the terminal device and the network device.
[0055] In one embodiment, the transceiver unit is further configured to broadcast or multicast system messages; the system messages are used to indicate that the network device supports the target service.
[0056] In one embodiment, the transceiver unit is further configured 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; 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 configured to update the service context corresponding to the at least one service context identifier according to the at least one service context identifier.
[0057] In one embodiment, the transceiver unit is specifically configured 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 the 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.
[0058] In a sixth aspect, an embodiment of the present application provides a service generation device, including: a transceiver unit, configured to send a tenth request instruction to a terminal device; the tenth request instruction is used to request to query the service context in the terminal device; the transceiver unit 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 is further configured to broadcast the eleventh request instruction; the eleventh request instruction is used to request to provide the service context corresponding to the at least one service context identifier; the transceiver unit is further configured 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, 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.
[0059] In a seventh aspect, an embodiment of the present application provides a service generation device, including: a transceiver unit, 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; a processing unit, configured to determine the service context of the target service according to the service context identifier; the service context includes relevant resources of one or more network elements supporting the target service; the transceiver unit 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.
[0060] In one embodiment, the processing unit is further configured to set 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.
[0061] 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 the relevant resources of each network element executing the target service according to the service policy of the target service.
[0062] In one embodiment, the transceiver unit is further configured to receive an eleventh request instruction sent by a network device; the eleventh request instruction is used to request other network devices to provide service contexts 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 contexts corresponding to the at least one service context identifier.
[0063] In one embodiment, the transceiver unit is further configured to receive the first request instruction sent by the network device; and send service function information to the network device, where the service function information includes the service types and / or function types that each network element supporting the target service can provide, and the service types and / or function types that each network element supporting the target service can provide are used to generate a service context of the target service in the network device.
[0064] In an eighth aspect, an embodiment of the present application provides a service generation device, including: a transceiver unit, configured 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 first request instruction includes a service context identifier; the transceiver unit is further configured to, when determining that there is no service context of the target service locally, send a seventh request instruction to a service generation system; the seventh request instruction is used to request the core network to provide service function information supporting the target service, where the service function information includes the service types and / or function types that each network element supporting the target service can provide; the transceiver unit is further configured to receive the service function information sent by the service generation system; a processing unit, configured to determine all or part of the service context of the target service according to the service types and / or function types 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.
[0065] 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 means that the relevant resources of one or more network elements supporting the target service are in a dormant state.
[0066] In one embodiment, the processing unit is further configured to, when determining that the service context of the target service exists locally, determine 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 takes effect; the transceiver unit is further configured to, 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.
[0067] In one embodiment, the transceiver unit 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 is further configured to set the service context of the target service to an active state.
[0068] In one embodiment, the processing unit is further configured to configure radio resources for the terminal device; the radio resources are used to carry the traffic of the target service transmitted between the terminal device and the network device.
[0069] In one embodiment, the transceiver unit is further configured to broadcast or multicast system messages; the system messages are used to indicate that the network device supports the target service.
[0070] In a ninth aspect, an embodiment of the present application provides a core network, including: at least one network element, and the at least one network element executes the embodiments of all possible implementations of the first aspect or the embodiments of all possible implementations of the third aspect.
[0071] In a tenth aspect, an embodiment of the present application provides a computer-readable storage medium, characterized by including computer program instructions, and when the computer program instructions are executed by the core network, the core network executes the embodiments of all possible implementations of the first aspect or the embodiments of all possible implementations of the third aspect.
[0072] In an eleventh aspect, an embodiment of the present application 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 the embodiments of all possible implementations of the first aspect or the embodiments of all possible implementations of the third aspect.
[0073] In a twelfth aspect, an embodiment of the present application provides a network device, including: at least one memory; at least one processor, and the processor is configured to execute instructions stored in the memory so that the network device executes the embodiments of all possible implementations of the first aspect, the embodiments of all possible implementations of the second aspect, and the embodiments of all possible implementations of the fourth aspect.
[0074] In a thirteenth aspect, an embodiment of the present application provides a computer-readable storage medium, which 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.
[0075] In a fourteenth aspect, an embodiment of the present application provides a computer program product containing instructions, which is characterized in that the computer program product stores instructions. When the instructions are executed by a network device, the network device implements 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 a fifteenth aspect, an embodiment of the present application provides a communication device, which includes a processor and a memory. A computer program or computer instructions are stored in the memory, and the processor is used to call and run the computer program or computer instructions stored in the memory, so that the processor implements each possible implementation embodiment of the first aspect, or each possible implementation embodiment of the second aspect, or each possible implementation embodiment of the third aspect, or each possible implementation embodiment of the fourth aspect.
[0077] In one implementation manner, the communication device further includes a transceiver, and the processor is used to control the transceiver to send and receive signals.
[0078] In a sixteenth aspect, an embodiment of the present application provides a communication device, which includes a processor. The processor is used to call the computer program or computer instructions stored therein, so that the processor implements each possible implementation embodiment of the first aspect, or each possible implementation embodiment of the second aspect, or each possible implementation embodiment of the third aspect, or each possible implementation embodiment of the fourth aspect.
[0079] In one implementation manner, the communication device further includes a transceiver, and the processor is used to control the transceiver to send and receive signals.
[0080] In a seventeenth aspect, an embodiment of the present application provides a chip device, which includes a processor for calling the computer program or computer instructions in the memory, so that the processor 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 third aspect, or each possible implementation embodiment of the fourth aspect as described above.
[0081] In one implementation manner, the processor is coupled to the memory through an interface.
[0082] In an eighteenth aspect, an embodiment of the present application provides a communication system, which includes a core network and network devices. The core network is used to execute the embodiments of all possible implementations of the first aspect or the embodiments of all possible implementations of the third aspect. The network devices are used to execute the embodiments of all possible implementations of the first aspect, or the embodiments of all possible implementations of the second aspect, or the embodiments of all possible implementations of the fourth aspect. BRIEF DESCRIPTION OF THE DRAWINGS
[0083] The following briefly introduces the drawings required in the description of the embodiments or the prior art.
[0084] Figure 1 It is a schematic diagram of an application scenario of a wireless communication system provided in an embodiment of the present application;
[0085] Figure 2 It is a schematic diagram of the structure of a service generation system provided in an embodiment of the present application;
[0086] Figure 3 It is a schematic diagram of the process of a service generation system provided in an embodiment of the present application for constructing a service context;
[0087] Figure 4 It is a schematic diagram of the switching between various states of a target service supported by a service generation system provided in an embodiment of the present application;
[0088] Figure 5 It is a schematic diagram of the process of a network device provided in an embodiment of the present application for generating a service context;
[0089] Figure 6 It is a schematic diagram of the process of a network device provided in an embodiment of the present application for updating a service context;
[0090] Figure 7 It is a schematic diagram of the process of a terminal device, a network device, and a service generation system provided in an embodiment of the present application for constructing the function of CSI compression feedback;
[0091] Figure 8 It is a schematic diagram of the structure of a service generation device provided in an embodiment of the present application;
[0092] Figure 9 It is a schematic diagram of the structure of another service generation device provided in an embodiment of the present application;
[0093] Figure 10 It is a schematic diagram of the structure of a base station provided in an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS
[0094] The following will describe the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application.
[0095] As used herein, the term "and / or" describes the relationship between associated objects, indicating that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The symbol " / " herein indicates that the associated objects are in an "or" relationship. For example, A / B means A or B.
[0096] Terms such as "first" and "second" in the description and claims of this application are used to distinguish different objects, rather than to describe a specific order of the objects. For example, the first response instruction and the second response instruction are used to distinguish different response instructions, rather than to describe the specific order of the response instructions.
[0097] In the embodiments of this application, words such as "exemplary" or "for example" are used to give examples, illustrations, or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of words such as "exemplary" or "for example" is intended to present relevant concepts in a specific manner.
[0098] In the description of the embodiments of this application, unless otherwise specified, the meaning of "a plurality of" refers to two or more. For example, a plurality of processing units refers to two or more processing units, and a plurality of elements refers to two or more elements.
[0099] Figure 1 This is a schematic diagram of the application scenario of a wireless communication system provided in the embodiments of this application. As Figure 1 shown, 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. Among them, the number of the network device 110, the terminal device 120, and the AI module 130 is not limited to Figure 1 the number shown and can 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 telecommunications system (UMTS), a mobile communication system after 5G network (e.g., 6G mobile communication system), a vehicle to everything (V2X) communication system, a device to device (D2D) communication system, an Internet of Things communication system, an industrial Internet communication system, or a satellite communication system, etc., as well as the 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 (mMTC) system.
[0101] The wireless communication system 100 can be composed of cells. Usually, at least one network device 110 is deployed in a cell, so that the network device 110 can provide communication services to each terminal device 120 within the cell. The wireless communication system 100 can perform point-to-point communication, such as enabling multiple terminal devices 120 to communicate with each other.
[0102] The terminal device 120 can be a wireless terminal device capable of receiving network device scheduling information and indication information. The terminal device 120 can be a device that provides voice and / or data connectivity to users, or a handheld device with wireless connection capabilities, or other processing devices 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. The terminal device is a device that includes wireless communication functions (providing voice / data connectivity to users). For example, a handheld device with a wireless connection function, or a vehicle-mounted device, etc. Currently, some examples of terminal devices are: mobile phones, tablet computers, laptop computers, palmtop computers, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in vehicle networking, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, or wireless terminals in smart home, etc. For example, the wireless terminal in self-driving can be a drone, a helicopter, or an airplane, etc. For example, the wireless terminal in vehicle networking can be a vehicle-mounted device, a whole vehicle device, a vehicle-mounted module, a vehicle, or a ship, etc. The wireless terminal in industrial control can be a camera, a robot, or a robotic arm, etc. The wireless terminal in smart home can be a TV, an air conditioner, a floor sweeper, a speaker, or a set-top box, etc.
[0104] It should be noted that the terminal device 120 can be a device or apparatus with a chip, or a device or apparatus integrated with a circuit, or a chip, chip system, module, or control unit in the above-mentioned devices or apparatuses. Specifically, this application does not make any limitations. It should be noted that in this application, when referring to the terminal device 120, it can refer to the terminal device itself, or the chip, functional module, or integrated circuit in the terminal device that completes the method provided in this application. Specifically, this application does not make any limitations.
[0105] The network device 110 can be a device in a wireless network. For example, the network device 110 can be a device deployed in a radio access network to provide wireless communication functions for terminal devices. For example, the network device 110 can be a radio access network (RAN) node that connects the terminal device 120 to the wireless network, and can also be referred to as an access network device, RAN entity, access node, network node, or communication device, etc.
[0106] Specifically, the network device 110 can 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 can also be an access network device in an open RAN (O-RAN or ORAN) or a cloud radio access network (CRAN). Or, the network device 110 can also be an access network device in a communication system obtained by fusing two or more of the above communication systems. Or, the network device 110 can 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 (e.g., home evolved NodeB, or home Node B, HNB), baseband unit (BBU), access point (AP) in a wireless fidelity (WIFI) system, macro base station, micro base station, wireless relay node, donor node, wireless controller in a 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, the next generation NodeB (gNB), TRP, 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 can also be a network node that constitutes a gNB or a transmission point. For example, centralized unit (CU), distributed unit (DU), centralized unit - control plane (CU - CP), centralized unit - user plane (CU - UP), or radio unit (RU), etc. The CU and DU can be set separately, or can also be included in the same network element, e.g., BBU. The RU can be included in a radio frequency device or radio frequency unit. For example, in a remote radio unit (RRU), active antenna unit (AAU), or remote radio head (RRH). Or, the network device 110 can also be a server, wearable device, vehicle, or in - vehicle device, etc. For example, the access network device in V2X technology can be a road side unit (RSU).
[0108] It should be noted that in different systems, the CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, the CU may also be referred to as an open centralized unit (O-CU) or an open CU, the DU may also be referred to as an open distributed unit (O-DU), the CU-CP may also be referred to as an open centralized unit control plane (O-CU-CP), the CU-UP may also be referred to as an open centralized unit user plane (O-CU-UP), and the RU may also be referred to as an open radio unit (O-RU). The specific application of this application is not limited. Any one of the CU, CU-CP, CU-UP, DU, and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.
[0109] Optionally, for the network elements in the ORAN system, each network element can implement the protocol layer functions as shown in Table 1 below.
[0110] Table 1
[0111]
[0112]
[0113] It should be noted that in the ORAN system, the network device 110 in this application can be one or more of the network elements in Table 1 above.
[0114] The architectures of the CU and DU of the access network device are introduced below. The access network device includes at least one CU and at least one DU. Optionally, the access network device further includes at least one RU.
[0115] The following takes the access network device including a CU and a DU as an example for introduction. The CU has some functions of the core network. The CU may include a CU-CP and a CU-UP. The CU and the DU can 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 (for example, the RRC layer and / or the SDAP layer). The DU is configured to implement the protocol layers below the PDCP layer (for example, the RLC layer, the MAC layer, and / or the physical (PHY) layer). Another example is that the CU is configured to implement 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 protocol layers at and below the PDCP layer (for example, the RLC layer, the MAC layer, and / or the PHY layer, etc.).
[0116] When the CU includes a CU-CP and a CU-UP, the CU-CP is used to implement the control plane function of the CU, and the CU-UP is used to implement the user plane function of the CU. For example, when the CU is configured to implement the functions of the PDCP layer, the RRC layer, and the SDAP layer, the CU-CP is used to implement the functions of the RRC layer and the control plane function of the PDCP layer, and the CU-UP is used to implement the functions of the SDAP layer and the user plane function of the PDCP layer.
[0117] The CU-CP can interact with the network element in the core network for implementing the control plane function. The network element in the core network for implementing the control plane function may be an access and mobility management function network element, such as the access and mobility management function (AMF) in the 5G system. The access and mobility management function network element is responsible for mobility management in the mobile network, such as location update of the terminal device, registration of the terminal device to the network, handover of the terminal device, etc.
[0118] The CU-UP can interact with the network element in the core network for implementing the user plane function. The network element in the core network for implementing the user plane function, for example, the user plane function (UPF) in the 5G system, is responsible for forwarding and receiving data in the terminal device.
[0119] The above configurations of the CU and DU are merely examples, and the functions of the 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 layers. For example, some functions of the RLC layer and the protocol layers above the RLC layer are set in the CU, and the remaining functions of the RLC layer and 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 service types or other system requirements. For example, divided by latency, the functions that require a small latency for processing time are set in the DU, and the functions that do not need to meet this latency requirement are set in the CU.
[0120] The DU and RU can cooperate to jointly implement the functions of the PHY layer. One DU can be connected to one or more RUs. The functions of the DU and RU can be configured in multiple ways according to the design. For example, the DU is configured to implement baseband functions, and the RU is configured to implement mid-RF functions. 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 implement the low-layer functions and RF functions. The high-layer functions in the physical layer can include a part of the functions of the physical layer, and this part of the functions is closer to the MAC layer. The low-layer functions in the physical layer can include another part of the functions of the physical layer, and this part of the functions is closer to the mid-RF side.
[0121] The network device 110 can also be a core network device. For example, the function entities of the control plane of the network device 110 include the access and mobility management function (AMF), or the session management function (SMF). The AMF is responsible for user access management, security authentication, mobility management, etc. The function entity of the data plane includes the UPF. The UPF is responsible for managing the transmission of user plane data, traffic statistics and other functions.
[0122] It should be noted that the network device 110 can be a device or apparatus with a chip, or a device or apparatus integrated with a circuit, or a chip, chip system, module or control unit in the aforementioned shown device or apparatus. Specifically, the present application does not make a limitation. It should be noted that in the present application, when referring to the network device 110, it can refer to the network device 110 itself, or the chip, functional module or integrated circuit in the network device 110 that completes the method provided in the present application. Specifically, the present application does not make a limitation.
[0123] The AI module 130 refers to a device that runs an AI model to perform functions such as data collection, data processing, and model training. The AI module 130 can be a component in the network device 110, that is, the AI model is deployed in the network device 110. The AI module 130 can be a component in the terminal device 120, that is, the AI model is deployed in the terminal device 120. The AI module 130 can be an independent component, such as a network element in the core network, etc., and this component has the function of wireless communication, enabling the AI module 130 to communicate with the network device 110 and the terminal device 120 respectively. The AI model is a machine learning model applied in the field of artificial intelligence, capable of automatically learning and adapting to the patterns and rules of different data sets. The AI model can be trained on a large amount of data, learn features and relationships from it, and be used to solve various intelligent tasks. The AI model can be applied to multiple fields and tasks, such as natural language processing, computer vision, speech recognition, intelligent recommendation, etc. Common AI models can be neural network models (such as deep neural networks and recurrent neural networks), support vector machine models, decision tree models, etc. In the embodiments 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.
[0124] In the embodiments 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 constructs the AI service for the network device 110, enabling the network device 110 to provide the AI service for the terminal device 120. The core network is an important part of the mobile communication network, 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 achieve data processing, forwarding, and control.
[0125] The service generation system provided by the present 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 can refer to the above-mentioned AI service, or 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 together can provide the target service for the terminal device 120. Among them, the target service can be services such as channel state information (CSI) compression feedback, performing cell reselection, cell selection, etc.
[0126] For ease of description, in this application, the relevant resources of one or more network elements that a service generation system needs to maintain to support one or more target services can be referred to as "service context".
[0127] Figure 2 This is a schematic diagram of an application scenario of a service generation system provided in an embodiment of this application. As Figure 2 shown, the 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.
[0128] Among them, the specific physical hardware of each network element of the service generation system 200 may be the above-mentioned network device 110, or the physical hardware of the above-mentioned terminal device 120, as well as other types of physical hardware. Optionally, the service generation system 200 may be the above-mentioned core network device. At this time, the service strategy network element 210, the AMF network element 220, and the Service-SMF network element 230 may be functional entities on the control plane of the core network device. The Service-UPF network element 240 and the database 250 are functional entities on the data plane of the core network device.
[0129] The service strategy network element 210 is used to make decisions on target services and can serve as the anchor node (or anchor network element) of the target service. The service strategy network element 210 can provide support for obtaining the target service context for services in the inactive state. In the embodiments of this application, the service strategy network element 210 can provide a decision-making function for AI services. Service strategies generally include maintaining relevant parameters of AI services, such as AI service identifiers, service context identifiers of AI services, node identifiers participating in AI services, node access addresses, regional descriptions of AI services, quality descriptions of AI services, etc.
[0130] The AMF network element 220 is used to control the connection between the core network and the terminal device 120 and mobility management. In the embodiments of this 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.
[0131] The Service-SMF network element 230 is used to manage sessions related to target services, such as establishing and maintaining traffic channels for data transmission between various network elements related to target services such as data and models, and maintaining channel parameters (such as allocating IPs, channel addresses, etc.). In the embodiments of this application, the Service-SMF network element 230 can manage sessions related to AI services to establish and maintain traffic channels for data transmission between various network elements related to AI services, and maintain the allocated IPs, channel addresses, etc. of the traffic channels.
[0132] The Service-UPF network element 240 is used to provide user plane transmission for target services. In the embodiments of this application, the Service-UPF network element 240 can provide user plane transmission for AI services.
[0133] The database 250 may include a data pool 251, a model pool 252, and a computation pool 253. Among them, the data pool 251, the model pool 252, and the computation pool 253 may be located on one network element or other numbers of network elements.
[0134] The data pool 251 is used to maintain data such as data sets, intermediate results of training / inference, and corresponding identifiers. In the embodiments of this application, the data pool 251 can be used to maintain data such as data sets, intermediate results of training / inference of AI models, and service context identifiers.
[0135] The model pool 252 is used to maintain model parameters and corresponding identifiers. In the embodiments of this application, the model pool 252 can maintain AI model parameters of AI services, identifiers of AI models, etc.
[0136] The computation pool 253 is used to schedule the computing resources of each node in the network, support a certain service function, maintain computing resources and corresponding identifiers. In the embodiments of this application, the computation pool 253 can schedule the computing resources of each network element in the service generation system 200, support AI services, maintain the computing resources of AI services, and the identifiers of each resource.
[0137] The OTT interface 260 is used to provide interfaces for third-party data, models, etc., and maintain interface addresses, descriptions of incoming network traffic, etc.
[0138] Exemplarily, Figure 3Schematic diagram of the process of constructing a service context for the service generation system provided in the embodiments 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 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. The specific process of the service generation system 200 constructing the service context of the target service is as follows:
[0139] 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 for requesting the target service supported by the network device 110.
[0140] 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, used to notify the terminal device 120 that the network device 110 supports the target service, or to notify the terminal device 120 that the network device 110 does not support the target service.
[0141] Optionally, in the ORAN system, the network device 110 in the above steps S301 - S302 may be the O-CU-CP network element, the O-DU network element, and / or the O-RU network element shown in Table 1 above.
[0142] When the terminal device 120 needs to execute the target service, it can send a first request instruction to the network device 110 to request the target service supported by the network device 110. After receiving the first request instruction, the network device 110 can determine whether it supports the target service locally according to the service context identifier carried in the first request instruction. In one case, when the network device 110 supports the target service, it can send a first response instruction to the terminal device 120 to notify the terminal device 120 that the network device 110 supports the target service. In another case, when the network device 110 does not support the target service, it can send a first response instruction to the terminal device 120 to notify the terminal device 120 that the network device 110 does not support the target service.
[0143] 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 support of the core network for the target service. In this embodiment, the second request instruction is used to request the target service supported by the service generation system 200.
[0144] Step S304: The AMF network element 220 sends a third request instruction to the 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 the service policy network element 210 to generate a service policy for the target service.
[0145] Optionally, when the terminal device 120 sends the third request instruction to the AMF network element 220 through the network device 110 in the above step S303, the network device 110 may be the RAN.
[0146] When the terminal device 120 determines that the network device 110 does not support the target service, it may 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.
[0147] Step S305: The service policy network element 210 sends a fourth request instruction to the database 250. The fourth request instruction is a service configuration request instruction used to request the core network to provide relevant resources of each network element. In this embodiment, the fourth request instruction is used to request the database 250 in the service generation system 220 to provide the data pool 251, the model pool 252, and the computing pool 253.
[0148] Step S306: The database 250 sends a fourth response instruction to the service policy network element 210. The fourth response instruction is an instruction in response to the fourth request instruction, used to notify the core network that the provision of relevant resources of each network element is completed. In this embodiment, the fourth response instruction is used to notify the service policy network element 210 that the database 250 has configured the data pool 251, the model pool 252, and the computing pool 253.
[0149] The service policy network element 210 is the control center of the service generation system 200. After receiving the third request instruction, it can generate the service policy of the target service according to the third request instruction. After obtaining the service policy of the target service, the service policy network element 210 can configure the relevant resources of each network element in the service generation system 200 to support the target service. During the configuration process, the service policy network element 210 can send a fourth request instruction to the database 250, requesting the database 250 to provide the data pool 251, model pool 252, and computing pool 253 that support the target service. After receiving the fourth request instruction, the database 251 can create the data pool 251, model pool 252, and computing pool 253, and make the data pool 251 available for maintaining data such as data sets, intermediate results of model training / inference, and service context identifiers, make the model pool 252 maintain the model parameters, identifiers of the model, etc. of the target service, and make the computing pool 253 schedule the computing resources of each network element in the service generation system 200, support the target service, maintain the computing resources of the target service, and the identifiers of each resource. After completing the creation of the data pool 251, model pool 252, and computing 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 has configured the data pool 251, model pool 252, and computing pool 253.
[0150] Step S307, the service policy network element 210 sends a fifth request instruction to the Service-SMF network element 230. The fifth request instruction is a request instruction for creating a traffic channel, 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 the Service-SMF network element 230 in the service generation system 220 to establish a traffic channel between the Service-UPF network element 240 for the local area, the terminal device 120, the service policy network element 210, the AMF network element 220, the data pool 251, the model pool 252, and the computing pool 253.
[0151] 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 an instruction in response to the fifth request instruction, used to notify the core network that the creation of the traffic channel for the relevant resources of each network element is completed. 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 the traffic channel for the relevant resources of each network element.
[0152] 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 of the target service. The Service-SMF network element 230 can create a traffic channel for network elements that need to perform traffic interaction, 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 perform traffic transmission with 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 the terminal device 120 and the Service-UPF network element 240 can perform traffic transmission, 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.
[0153] The Service-UPF network element 240 is a 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 the traffic of a network element at one end of the traffic channel to a network element at the other end, enabling communication between the two network elements.
[0154] After the Service-SMF network element 230 completes the establishment of the traffic channels between each network element, it can send a service session response instruction to the service policy network element 210, requesting the Service-SMF network element 230 to complete the establishment of the traffic channels between each network element. After receiving the service session response instruction, the service policy network element 210 determines that the relevant resource configurations of each network element for executing the target service are completed. The service policy network element 210 can generate a service context for the target service based on the relevant resources of each network element for executing the target service and store it in the local memory.
[0155] 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, used to notify the core network that the service context of the target service has been generated. In the 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.
[0156] 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.
[0157] After the service policy network element 210 completes the generation of the service context of the target service, it can send a third response instruction to the AMF network element 220 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. After receiving the third response instruction, the AMF network element 220 can convert it into a second response instruction to notify the terminal device 120 that the service generation system 200 supports the target service. After the terminal device 120 receives the second response instruction through the network device 110, it determines that the service generation system 200 has generated the service context of the target service, and can execute the target service in the service generation system 200 through the network device 110. If the terminal device 120 needs to execute the target service, it can send a sixth request instruction to the service generation system 200 through the network device 110. The sixth request instruction is used to request the service generation system 200 to execute the target service, so as to implement the service generation system 200 to provide the target service for the terminal device 120.
[0158] In the embodiment of the present application, when the network device 110 does not support the target service, the terminal device 120 can generate the service context of 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, ensuring the continuity of running the target service.
[0159] The states in which the service policy network element 210 supports the target service can include a service setup state, an inactive state, an active state, and a service release state. The service setup state refers to the state in which the service policy network element 210 coordinates the start-up parameters of each network element to start the target service. The start-up parameters can be the model scale, model input and output, service performance, etc. When the service policy network element 210 is in the service setup state, each network element has not yet generated the service context for implementing the target service.
[0160] The inactive state means that the service policy network element 210 puts the relevant resources of each network element of the target service in a dormant state. At this time, the service policy network element 210 can determine that each network element generates the service context according to the start-up parameters and stores it in the 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 can let each network element update the service context. Among them, there are two ways for the service generation system 200 to cache the service context, which are respectively:
[0161] The service policy network element 210 can centrally store the service contexts of each network element supporting the target service in the 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 contexts to each network element for each network element to load and run.
[0162] 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 distributed and stored in each network element. When the target service enters the active state, the service policy network element 210 can instruct each network element to load and run.
[0163] The active state refers to the state in which 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 cause the terminal device 120 to execute the target service and can cause each network element to update the service context.
[0164] The service release state refers to the state in which the service policy network element 210 causes each network element to cancel the service context of the target service.
[0165] The service policy network element 210 supports the mutual conversion between various states of the target service. As Figure 4 shown, the service generation state and the inactive state of the service policy network element 210 can be mutually converted, the service generation state and the active state of the service policy network element 210 can be mutually converted, the inactive state and the active state of the service policy network element 210 can be mutually converted, 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.
[0166] 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 service context supporting the target service can be constructed through the network device 110. After receiving the first request instruction, the network device 110 first aligns the parameters of the network device 110 and each network element of the core network to ensure the normal operation and coordinated operation of the network device 110 and each network element of the core network.
[0167] Figure 5 It is a schematic flow chart of generating a service context by the network device provided in the embodiment of the present application. As Figure 5 shown, the network device 110 generally cooperates with the terminal device 120 and the core network to generate a service context, and the specific implementation process is as follows:
[0168] 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 for requesting the target service supported by the network device 110.
[0169] Step S502, the network device 110 detects whether there is a service context of the target service locally. In one case, the network device 110 determines that there is no service context of the target service locally and executes Step S503. In another case, the network device 110 determines that there is a service context of the target service locally and executes Step S506.
[0170] After receiving the first request instruction sent by the terminal device 120, the network device 110 can detect whether there is a service context corresponding to the service context identifier carried in the first request instruction locally. In one case, when the network device 110 determines that there is a service context corresponding to the service context identifier 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 locally, it can forward the first request instruction to the core network or send a seventh request instruction to the core network to request the service function information of each network element that supports the target service provided by the core network.
[0171] 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 the service function information of the target service.
[0172] Step S504, the core network sends the service function information to the network device 110.
[0173] If the network device 110 receives the first request instruction, it can directly pass the first request instruction through to the core network. If the network device 110 receives the seventh request instruction, the network device 110 can send the seventh request instruction to the core network through the RAN. Inside the core network, the first request instruction and the seventh request instruction have the same function, which is to obtain the service function information of the target service. The core network can be the above-mentioned service generation system 200. The service generation system 200 can forward the first request instruction or the seventh request instruction to the service policy network element 210. The service policy network element 210 can determine the service function information of each network element according to the service context identifier carried in the first request instruction or the seventh request instruction, and send the service function information to the 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. The service types can be service types such as training, inference, data collection, etc. The function types can be enabling features of the target service such as channel estimation, beam management, mobility management, etc.
[0174] Step S505, the network device 110 generates all or part of the service context of the target service according to the service function information.
[0175] 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.
[0176] After the network device 110 obtains the service types and function types that each network element of the core network can provide, it can locally configure the service parameters of the target service, such as the configuration of the model, the configuration of the data set, computing resources, parameter version numbers, running environment information, etc. The network device 110 can generate all or part of the service context of the target service according to the service parameters of the target service and the service context identifier carried in the first request instruction, and set the state of the service context of the target service to the inactive state. If the service context generated by the network device 110 is part of the service context of the target service, then the part of the service context of the target service refers to the relevant resources participated by the network device 110 that supports the target service.
[0177] After the network device 110 generates the service context of the target service, it can send a first response instruction to the terminal device 120. After receiving the first response instruction, the terminal device 120 determines that the network device 110 has generated the service context of the target service and can execute the target service in the network device 110 and / or the core network. If the terminal device 120 needs to execute the target service, it can send an eighth request instruction to the core network through the network device 110. The eighth request instruction is used to request the network device 110 and / or the core network to execute the target service, so as to enable the network device 110 to provide the target service for the terminal device 120. At this time, the network device 110 sets the service context of the target service to the active state.
[0178] After the network device 110 generates the support for the target service, it can broadcast or multicast system messages. The system messages are used to indicate the target services supported by the network device 110. The system messages include the relevant configuration information of the target services. The configuration information may include the identification (ID) of the target service, the mapping configuration of the logical traffic channel (LTCH) for carrying the service traffic of the target service and the physical downlink shared channel (PDSCH) and / or the physical uplink shared channel (PUSCH), and the configuration information of each protocol layer.
[0179] After receiving the system messages, the terminal device 120 can determine whether it needs the target service of the network device 110 according to local requirements. If the terminal device 120 needs the target service of the network device 110, it can send interest information to the network 110 to inform the network device 110 that the terminal device 120 needs the target service of the network device 110. After receiving the interest information, the network device 110 can know the target service of the terminal device 120 to identify the corresponding model and / or function of the target service and set the target service to the active state, so that the terminal device 120 can execute the target service through the network device 110.
[0180] Optionally, in the ORAN system, the network device 110 in the above steps S501 - S506 may be the O-CU-CP network element, the O-DU network element, and / or the O-RU network element shown in Table 1 above.
[0181] In an embodiment of the present application, a regional identifier may be added to the service context in which the network device 110 participates. The regional identifier is used to distinguish the geographical area where the service context takes effect, and may be the ID of the network device 110, the address of the area where the network device 110 is located, or other identifiers that distinguish the network device 110. The network device 110 may locally construct a dedicated service context based on the regional identifier and the service context identifier. The terminal device 120 generally carries the service context identifier (i.e., the service context ID) of the target service to be executed. After the terminal device 120 switches from one network device 110 to another network device 110, it sends the service context identifier to the switched-to network device 110. After receiving the service context identifier, the network device 110 determines the service context corresponding to the service context identifier, and determines whether the regional identifier in the service context corresponding to the service context identifier is the same as the local regional identifier. If the network device 110 determines that the regional identifier in the service context corresponding to the service context identifier is different from the local regional identifier, the service context for providing the target service locally changes. The network device 110 discovers that the regional identifier has changed, and confirms that the service context it holds locally is not suitable for providing the target service to the newly arrived terminal device 120.
[0182] After the network device 110 determines that the service context for providing the target service to the terminal device 120 has changed, it may send a ninth request instruction to the terminal device 120. The ninth request instruction is used to request the terminal device 120 to determine whether the network device 110 regenerates the service context of the target service. After receiving the ninth request instruction, the terminal device 120 may resend the first request instruction, the second request instruction, or other request instructions to the switched-to network device 110, requesting the switched-to network device 110 to regenerate the service context of the target service, and requesting the switched-to network device 110 to regenerate the service context of the target service in other ways, so that the terminal device 120 can execute the target service through the switched-to network device 110. Alternatively, the terminal device 120 sends a pause instruction to the switched-to network device 110, instructing the switched-to network device 110 to pause maintaining the service context and causing the terminal device 120 to stop executing the target service.
[0183] When the terminal device 120 switches from one network device 110 to another network device 110, it can send the service context identifier to the switched-to network device 110. After receiving the service context identifier, the switched-to network device 110 determines whether there is a service context corresponding to the service context identifier locally. In one case, if the switched-to network device 110 has the corresponding service context, it can add the terminal device 120 to the service session maintained by the local service context. In another case, if the switched-to network device 110 does not have the corresponding service context, it can broadcast or multicast the corresponding service context identifier to other network devices 110 to find a network device 110 that has the corresponding service context. After the switched-to network device 110 finds a network device 110 that has the corresponding service context, it can obtain the corresponding service context from the other network device 110 and set the state of the corresponding service context to the active state. The switched-to network device 110 can add the terminal device 120 to the service session maintained by the local service context, so that the terminal device 120 can execute the target service through the switched-to network device 110.
[0184] According to the local resource status, the switched-to network device 110 can configure a unicast link for the terminal device 120, or add the terminal device 120 to an existing multicast or broadcast link, so as to configure radio access network resources for the terminal device 120 to carry the traffic of the transmission service. During the process of the terminal device 120 switching from one network device 110 to another network device 110, it can obtain the service context from the network according to the service context identifier to ensure the continuity of the terminal device 120 running the target service.
[0185] Figure 6 It is a schematic flowchart of the process for the network device to update the service context provided in the embodiments of this application. As Figure 6 shown, the process for the network device 110 to update the service context is specifically as follows:
[0186] 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 used to request to query the service context in the terminal device 120.
[0187] 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, 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.
[0188] After the network device 110 needs to update the service context maintained locally, it can initiate the update function of the service context and send a tenth request instruction to the terminal device 120 to request querying the service context in the terminal device 120. After receiving the tenth request instruction, the terminal device 120 can send a tenth response instruction to the network device 110 according to the service context that needs to be updated. The tenth response instruction carries the service context identifier that the terminal device 120 needs to update, so that after the network device 110 receives the tenth response instruction, it can obtain the service context that the terminal device 120 needs to update. The tenth response instruction also carries the status 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 status according to the status information.
[0189] Step S603, the network device 110 detects whether there is a service context corresponding to the service context identifier carried in the tenth response instruction locally. In one case, the network device 110 determines that there is a service context corresponding to the service context identifier carried in the tenth response instruction locally, and executes step S606. In another case, the network device 110 determines that there is no service context corresponding to the service context identifier carried in the tenth response instruction locally, and executes step S604.
[0190] Step S604, the network device 110 sends an eleventh request instruction to the anchor node. The anchor node refers to 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.
[0191] 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 in the tenth response instruction. The eleventh response instruction includes the service context corresponding to the service context identifier carried in the tenth response instruction.
[0192] After receiving the tenth response instruction, the network device 110 can detect whether there is a corresponding service context locally according to the service context identifier carried in the tenth response instruction. In one case, when the network device 110 determines that there is a service context corresponding to the service context identifier carried in the tenth response instruction locally, it 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 in the tenth response instruction locally or there is no complete service context corresponding to the service context identifier carried in the tenth response instruction, it can broadcast an eleventh request instruction to other network devices 110, requesting other network devices 110 to provide the service context corresponding to the service context identifier carried in the tenth response instruction. The eleventh request instruction carries the service context identifier carried in the tenth response instruction so that other network devices 110 can provide the corresponding service context.
[0193] After other network devices 110 determine that there is a service context corresponding to the service context identifier carried in the tenth response instruction locally according to the service context identifier carried in the tenth response instruction, they can send an eleventh response instruction to the network device 110, and send the service context corresponding to the service context identifier carried in the tenth response instruction to the network device 110.
[0194] Step S606, the network device 110 updates the service context.
[0195] After the network device 110 obtains the service context corresponding to the service context identifier carried in the tenth response instruction, it can maintain the corresponding service context and set the state of the service context to the state indicated by the status information carried in the tenth response instruction, so as to update the service context.
[0196] Optionally, in the ORAN system, the network device 110 in the above steps S601 - S605 may be the O-CU-CP network element, O-DU network element, and / or O-RU network element shown in Table 1 above.
[0197] Next, taking CSI compression feedback as an example, an implementation scenario of the solution of the embodiment of the present application will be introduced.
[0198] Figure 7 It is a schematic flowchart of the process of constructing the CSI compression feedback function for the terminal device, network device, and service generation system provided in the embodiment of the present application. As Figure 7 shown, the process of constructing the CSI compression feedback function for the terminal device 120, network device 110, and service generation system 200 is specifically as follows:
[0199] Step S701: The terminal device 120 sends a twelfth request instruction to the network device 110. The function of the twelfth request instruction can be similar to that of the first request instruction, and is used to request the CSI compression feedback function supported by the network device 110.
[0200] CSI compression feedback means that in a wireless communication system, CSI information is compressed by a certain method to reduce the resource overhead required for CSI feedback. When the terminal device 120 needs the CSI compression feedback function, it can send a twelfth request instruction to the network device 110 to request the network device 110 to maintain the service context of the CSI compression feedback function.
[0201] Step S702: The network device 110 sends a thirteenth request instruction to the service generation system 200. The function of the thirteenth request instruction can be similar to that of the seventh request instruction, and is used to request to obtain the service function information of the service generation system 200 that supports the CSI compression feedback function.
[0202] Step S703: The service generation system 200 sends a thirteenth response instruction to the network device 110. The function of the thirteenth request instruction can be similar to that of the service function information, and carries the service function information of the CSI compression feedback function supported.
[0203] Similarly, the specific implementation process of steps S701 - S703 can refer to Figure 5 the process of steps S501 - S504 in, specifically: after receiving the twelfth request instruction, the network device 110 first detects whether there is a service context of the CSI compression feedback function locally. In one case, the network device 110 determines that there is a service context of the CSI compression feedback function locally and does not need to execute steps S702 - S703. In another case, the network device 110 determines that there is no service context of 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 service generation system 200 that supports the CSI compression feedback function. 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 according to the service context identifier carried in the thirteenth request instruction, and sends the service function information to the network device 110.
[0204] Step S704: The network device 110 generates the CSI compression feedback function.
[0205] Step S705: The network device 110 updates the local service context.
[0206] After obtaining the service function information of the service generation system 200, the network device 110 can locally configure the service parameters of the CSI compression feedback function. The network device 110 can generate all or part of the service context of the CSI compression feedback function according to the service parameters of the CSI compression feedback function and the service context identifier of the CSI compression feedback function carried in the twelfth request instruction, and maintain the service context of the CSI compression feedback function, so that the network device 110 supports the CSI compression feedback function. At this time, the network device 110 can set the state of the service context of the CSI compression feedback function to the inactive state.
[0207] Step S706, the network device 110 sends a twelfth response instruction to the terminal device 120. The function of the twelfth response instruction can 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.
[0208] After obtaining the service context of the CSI compression feedback function, the network device 110 can maintain the service context of the CSI compression feedback function and execute the CSI compression feedback function to ensure the continuity of the operation of the CSI compression feedback function of the terminal device 120. After the network device 110 has the CSI compression feedback function, it can send a twelfth response instruction to the terminal device 120 to inform the terminal device 120 that the current network device 110 has the CSI compression feedback function.
[0209] Step S707, the network device 110 activates the CSI compression feedback function.
[0210] After the terminal device 120 determines that the network device 110 has the CSI compression feedback function, it can send an execution instruction to the network device to implement the CSI compression feedback function through the network device 120 and / or the service generation system 200. At this time, the network device 110 can set the state of the service context of the CSI compression feedback function to the active state, so that the CSI compression feedback function operates normally.
[0211] Optionally, in the ORAN system, the network device 110 in the above steps S701 - S707 can be the O-CU-CP network element, O-DU network element, and / or O-RU network element shown in Table 1 above.
[0212] In other embodiments, the function of the twelfth request instruction can be similar to that of the second request instruction, and is used to request the service generation system 200 to support the CSI compression feedback function. At this time, the network device 110 only forwards the twelfth request instruction, that is, the thirteenth request instruction and the twelfth request instruction are one request instruction.
[0213] After receiving the thirteenth request instruction, the service generation system 200 can generate a service context that supports the CSI compression feedback function. The specific implementation process can refer to Figure 3 the process of steps S305 - S309 in
[0214] Specifically, for example, the 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. The service policy network element 210 generates a service policy for the CSI compression feedback function according to the service context identifier carried in the third request instruction. The service policy network element 210 may send a fourth request instruction to the database 250, requesting the database to provide a data pool 251, a model pool 252, and a computing pool 253 that support the target service. After receiving the fourth request instruction, the database 251 can create the data pool 251, the model pool 252, and the computing pool 253.
[0215] 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 relevant sessions for the CSI compression feedback function. The Service - SMF network element 230 can establish traffic channels 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, enabling traffic transmission between them, and establish a traffic channel between the terminal device 120 and the Service - UPF network element 240, enabling traffic transmission between the terminal device 120 and the Service - UPF network element 240. The service policy network element 210 can generate a service context for the CSI compression feedback function based on the relevant resources of each network element that executes the CSI compression feedback function and send it to the network device 110.
[0216] 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. Figure 6The process of steps S603 - S605. At this time, the thirteenth response instruction carries a service context that supports the CSI compression feedback function, and then the network device 110, the terminal device 120, and the service generation system 200 directly execute steps S704 - S707.
[0217] In the embodiments of the present application, when the terminal device 120 executes the CSI compression feedback function through the network device 110, in the case where the network device 110 does not support the CSI compression feedback function, a service context for the CSI compression feedback function can be constructed 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 operation of the CSI compression feedback function of the terminal device 120.
[0218] Figure 8 It is a schematic structural diagram of a service generation device provided in the embodiments of the present application. As Figure 8 shown, the service generation device 800 can execute Figure 3 , Figure 5 , Figure 6 and Figure 7 the processes executed by the network device or the core network in the embodiments shown. For details, please refer to the relevant introductions in the above method embodiments. The service generation device 800 can be divided into a transceiver unit 810 and a processing unit 820 according to the executed functions.
[0219] The transceiver unit 810 can implement corresponding communication functions. The transceiver unit 810 can also be referred to as a communication interface or a communication module.
[0220] The processing unit 820 is used for data processing.
[0221] Optionally, the service generation device 800 may further include a storage unit, which can be used to store instructions and / or data. The processing unit 820 can read the instructions and / or data in the storage unit so that the service generation device 800 can implement the foregoing method embodiments.
[0222] 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 in a network device. The processing unit 820 is used to execute the operations related to the processing on the network device side in the above method embodiments. The transceiver unit 810 is used to execute the operations related to the reception on the network device side in the above method embodiments.
[0223] Alternatively, the service generation device 800 can be used to perform the actions executed 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 operations related to the processing on the core network side in the above method embodiments. The transceiver unit 810 is used to perform operations related to the reception on the core network side in the above method embodiments.
[0224] Optionally, the transceiver unit 810 may include a sending unit and a receiving unit. The sending unit is used to perform the sending operation in the above method embodiments. The receiving unit is used to perform the receiving operation in the above method embodiments.
[0225] It should be noted that the service generation device 800 may include a sending unit but not a receiving unit. Or, the communication device 800 may include a receiving unit but not a sending unit. Specifically, it depends on whether the above scheme executed by the service generation device 800 includes a sending action and a receiving action.
[0226] In another case, the service generation device 800 can perform Figure 3 the functions of the service generation system 200 (i.e., the core network) described, specifically:
[0227] The transceiver unit 810 is used to receive a second request instruction sent by the 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 used to determine the service context of the target service according to the service context identifier. The service context includes relevant resources of one or more network elements supporting the target service. The transceiver unit 810 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.
[0228] In one implementation, the processing unit 820 is further used to set 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.
[0229] In one implementation, the processing unit 820 is specifically used to generate a service policy for the target service according to the service context identifier. According to the service policy of the target service, configure the relevant resources of each network element executing the target service.
[0230] In one implementation, the transceiver unit 810 is further used to receive an eleventh request instruction sent by a network device. The eleventh request instruction is used to request another network device to provide the service context corresponding to at least one service context identifier. The transceiver unit 810 is also used to send an eleventh response instruction to the network device. The eleventh response instruction includes the service context corresponding to at least one service context identifier.
[0231] In one embodiment, the transceiver unit 810 is further configured to receive a first request instruction sent by a 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 each network element supporting the target service can provide, and the service types and / or function types that each network element supporting the target service can provide are used to generate a service context of the target service in the network device.
[0232] In another case, the service generation device 800 may execute Figure 5 the functions of the network device 110 described as follows:
[0233] The transceiver unit 810 is 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 first request instruction includes a service context identifier. The transceiver unit 810 is further configured 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 types and / or function types that each network element supporting the target service can provide. The transceiver unit 810 is further configured to receive the service function information sent by the service generation system. The processing unit 820 is configured to determine all or part of the service context of the target service according to the service types and / or function types 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.
[0234] 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 means that the relevant resources of one or more network elements supporting the target service are in a dormant state.
[0235] In one embodiment, when the processing unit 820 determines that the service context of the target service exists locally, the processing unit 820 is further configured to determine 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 takes effect. The transceiver unit 810 is further configured 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.
[0236] 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.
[0237] In one embodiment, the transceiver unit 810 is further configured to configure radio resources for the terminal device. The radio resources are used to carry the traffic of the target service transmitted between the terminal device and the network device.
[0238] In one embodiment, the transceiver unit 810 is further configured to broadcast or multicast system messages. The system messages are used to indicate that the network device supports the target service.
[0239] In another case, the service generation device 800 may perform Figure 6 the functions of the network device 110 described as follows:
[0240] The transceiver unit 810 is configured 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. 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 used to request to provide the service context corresponding to at least one service context identifier. The transceiver unit 810 is further configured to receive an eleventh response instruction. The eleventh response instruction includes the service context corresponding to at least one service context identifier. The processing unit 820 is configured to update the service context corresponding to at least one service context identifier according to the service context corresponding to at least one service context identifier.
[0241] In one case, the service generation device 800 may perform Figure 3 、 Figure 5 、 Figure 6 and Figure 7 the functions of the network device 110 described as follows:
[0242] The transceiver unit 810 is 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. The service function information includes the service types and / or function types that each network element supporting the target service can provide. The transceiver unit 810 is further configured to receive the service function information sent by the core network. The processing unit 820 is configured to determine all or part of the service context of the target service according to the service types and / or function types that each network element supporting the target service can provide. The service context of the target service includes the relevant resources of one or more network elements supporting the target service.
[0243] 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 means that the relevant resources of one or more network elements supporting the target service are in a dormant state.
[0244] 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 of the target service exists locally. The transceiver unit 810 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.
[0245] In one embodiment, the processing unit 820 is further configured to determine whether the area identifier in the service context of the target service is the same as the local area identifier when it is determined that the service context of the target service exists locally. The area identifier is used to distinguish the geographical area where the service context takes effect. The transceiver unit 810 is further configured 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.
[0246] 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.
[0247] 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.
[0248] In one embodiment, the processing unit 820 is further configured to configure radio resources for the terminal device. The radio resources are used to carry the traffic of the target service transmitted between the terminal device and the network device.
[0249] In one embodiment, the transceiver unit 810 is further configured to broadcast or multicast system messages. The system messages are used to request the network device to support the target service.
[0250] 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 used to request 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 at least one service context identifier according to the at least one service context identifier.
[0251] In one implementation, the transceiver unit 810 is specifically configured to broadcast an eleventh request instruction. The eleventh request instruction is used to request other network devices to provide service contexts 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 service contexts corresponding to at least one service context identifier. The processing unit 820 is specifically configured to update the service contexts corresponding to at least one service context identifier according to the service contexts corresponding to at least one service context identifier.
[0252] Figure 9 FIG. is a schematic structural diagram of another service generation device provided in an embodiment of the present application. As Figure 9 shown, the present application further provides a service generation device 900. The service generation device 900 may be a network device or a chip. The service generation device 900 may be used to execute the above Figure 3 , Figure 5 , Figure 6 , Figure 7 shown in any of the operations performed by the network device in any of the embodiments, or execute the operations performed by the core network device in any of the embodiments shown in the above Figure 3 , Figure 7 shown.
[0253] When the service generation device 900 is a network device, for example, it is a base station. Figure 9 FIG. shows a schematic structural diagram of a simplified base station. The base station includes a 910 part, a 920 part, and a 930 part.
[0254] The 910 part is mainly used for baseband processing and controlling the base station, etc.; the 910 part is usually the control center of the base station and can usually be called a processor, which is used to control the base station to execute the processing operations on the network device side in the above method embodiments.
[0255] The 920 part is mainly used for storing computer program codes and data. The 930 part is mainly used for transceiver of radio frequency signals and conversion between radio frequency signals and baseband signals.
[0256] The 930 part can usually be called a transceiver unit, a transceiver, a transceiver circuit, or a transceiver, etc. The transceiver unit of the 930 part can also be called a transceiver or a transceiver, etc., and it includes an antenna 933 and a radio frequency circuit (not shown in the figure). The radio frequency circuit is mainly used for radio frequency processing. Optionally, the devices used to implement the receiving function in the 930 part can be regarded as a receiver, and the devices used to implement the sending function can be regarded as a transmitter, that is, the 930 part includes a receiver 932 and a transmitter 931. The receiver can also be called a receiving unit, a receiver, or a receiving circuit, etc., and the transmitter can be called a transmitting unit, a transmitter, or a transmitting circuit, etc.
[0257] The 910 part and the 920 part may include one or more single boards, and each single board may include one or more processors and one or more memories. The processor is used to read and execute the programs in the memory to implement baseband processing functions and control of the base station. If there are multiple single boards, they can be interconnected to enhance the processing capacity. As an alternative implementation, it is also possible that multiple single boards share one or more processors, or multiple single boards share one or more memories, or multiple single boards simultaneously share one or more processors.
[0258] For example, the transceiver module of the 930 part is used to execute Figure 3 , Figure 5 , Figure 6 , Figure 7 any of the transceiver-related processes performed by the network device in any of the embodiments shown. The processor of the 910 part is used to execute Figure 3 , Figure 5 , Figure 6 , Figure 7 any of the processing-related processes performed by the network device in any of the embodiments shown.
[0259] It should be understood that Figure 9 is only an example and not a limitation. The above network device including a processor, a memory, and a transceiver may not depend on the Figure 8 shown structure.
[0260] When the service generation device 900 is a chip, the chip includes a transceiver, a memory, and a processor. Among them, the transceiver may be an input / output circuit or a communication interface; the processor is the processor integrated on the chip, or a microprocessor, or an integrated circuit. The sending operation of the network device in the above method embodiments can be understood as the output of the chip, and the receiving operation of the network device in the above method embodiments can be understood as the input of the chip.
[0261] The embodiments of the present application also provide a chip device, including a processor, which is used to call the computer program or computer instructions stored in the memory, so that the processor executes the above Figure 3 , Figure 5 , Figure 6 , Figure 7 any of the methods provided in any of the embodiments shown.
[0262] In a possible implementation, the input of the chip device corresponds to the Figure 3 , Figure 5 , Figure 6 , Figure 7 any of the receiving operations in any of the embodiments shown, and the output of the chip device corresponds to the Figure 3 , Figure 5 , Figure 6 ,Figure 7 The transmission operation in any of the illustrated embodiments.
[0263] Optionally, the processor is coupled to the memory through an interface.
[0264] Optionally, the chip device further includes a memory, and computer programs or computer instructions are stored in the memory.
[0265] Wherein, the processor mentioned anywhere above can be a general-purpose central processing unit, a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the program execution of the method provided in any of the illustrated embodiments above. The memory mentioned anywhere above can be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM), etc. Figure 3 、 Figure 5 、 Figure 6 、 Figure 7 Shown. The memory mentioned anywhere above can be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM), etc.
[0266] When the service generation device 900 is a base station, Figure 10 It is a schematic structural diagram of a base station provided by an embodiment of the present application. As Figure 10 Shown, perform the above Figure 3 、 Figure 5 、 Figure 6 、 Figure 7 The functions of the network device 110 in the corresponding service generation method embodiment. The base station 1000 may include one or more DUs 1010 and one or more CUs 1020. The DU 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. The DU 1010 part is mainly used for the transceiver of radio frequency signals and the conversion between radio frequency signals and baseband signals, as well as partial baseband processing. The CU 1020 may include at least one processor 1021 and at least one memory 1022. The CU 1020 and the DU 1010 can communicate through an interface. Among them, the control plane interface can be Fs-C, such as F1-C, and the user plane interface can be Fs-U, such as F1-U.
[0267] The CU 1020 part is mainly used for baseband processing and controlling the base station, etc. The DU 1010 and the CU 1020 can be physically set together or physically separated, that is, a distributed base station. The CU 1020 is the control center of the base station and can also be called a processing unit, mainly used to complete the baseband processing function. For example, the CU 1020 can be used to control the base station 1000 to execute the operation process of the network device 110 in the above method embodiments.
[0268] Specifically, the 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 protocol layers are set on the CU, and the protocol layers below PDCP, such as the RLC and MAC layers, etc., are set on the DU. Another example is that the CU implements the functions of the RRC and PDCP layers, and the DU implements the functions of the RLC, MAC, and PHY layers.
[0269] In addition, optionally, the base station 1000 may include one or more radio frequency units (RU), one or more DUs, and one or more CUs. Among them, 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.
[0270] In one example, the CU 1020 may be composed of one or more single boards. The multiple single boards can jointly support a wireless access network with a single access indication (such as a 6G network), or can separately support wireless access networks with different access systems (such as an LTE network, a 6G network, or other networks). The processor 1021 and the memory 1022 can serve one or more single boards. That is to say, a memory and a processor can be separately set on each single board. It can also be that multiple single boards share the same memory and processor. In addition, necessary circuits can be set on each single board. The DU 801 may be composed of one or more single boards. The multiple single boards can jointly support a wireless access network with a single access indication (such as a 6G network), or can separately support wireless access networks with different access systems (such as an LTE network, a 6G network, or other networks). The memory 1014 and the processor 1013 can serve one or more single boards. That is to say, a memory and a processor can be separately set on each single board. It can also be that multiple single boards share the same memory and processor. In addition, necessary circuits can be set on each single board.
[0271] Among them, the DU and the CU can jointly execute Figure 9 the functions of the processor 920 in the service generation device 900 shown, and the details will not be elaborated here.
[0272] In an embodiment of the present application, a computer-readable storage medium is further provided, including computer program instructions. When the computer program instructions are executed by a core network, the core network executes any of the methods described above Figure 3 , Figure 7 and any method described in the corresponding description content
[0273] In an embodiment of the present application, a computer-readable storage medium is further provided, including computer program instructions. When the computer program instructions are executed by a network device, the network device executes any of the methods described above Figure 3 , Figure 5 , Figure 6 , Figure 7 and any method described in the corresponding description content
[0274] In an embodiment of the present application, a computer program product containing instructions is further provided. It is characterized in that the computer program product stores instructions, and when the instructions are executed by a core network, the core network implements any of the methods described above Figure 3 , Figure 7 and any method described in the corresponding description content
[0275] In an embodiment of the present application, a computer program product containing instructions is further provided. It is characterized in that the computer program product stores instructions, and when the instructions are executed by a network device, the network device implements any of the methods described above Figure 3 , Figure 5 , Figure 6 , Figure 7 and any method described in the corresponding description content
[0276] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered to exceed the scope of the embodiments of the present application
[0277] In addition, aspects or features of the embodiments of the present application can be implemented as a method, apparatus, or article of manufacture using standard programming and / or engineering techniques. The term "article of manufacture" as used in this application encompasses a computer program accessible from any computer-readable device, carrier, or medium. For example, computer-readable media can include, but are not limited to: magnetic storage devices (such as hard disks, floppy disks, or magnetic tapes, etc.), optical discs (such as compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards, and flash memory devices (such as erasable programmable read-only memories (EPROMs), cards, sticks, or key drives, etc.). Additionally, the various storage media described herein can represent one or more devices and / or other machine-readable media for storing information. The term "machine-readable media" can include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.
[0278] In the above embodiments, Figure 8 the service generation device 800 in [the above] 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 processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. 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 wired (such as coaxial cable, fiber optic, digital subscriber line) or wireless (such as infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible by a computer or a data storage device such as a server, data center, etc. that incorporates one or more available media. The available media can be magnetic media (such as floppy disks, hard disks, magnetic tapes), optical media (such as DVDs), or semiconductor media (such as solid state drives (SSDs), etc.).
[0279] It should be understood that in the various embodiments of the embodiments of the present application, the magnitudes of the sequence numbers of the above processes do not mean the order of execution is prior or subsequent. The order of execution of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
[0280] Those skilled in the art can 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 foregoing method embodiments and will not be elaborated herein.
[0281] In several embodiments provided in the present 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 illustrative. For example, the division of the units is only a logical function division, and there can be other division methods in actual implementation. For example, 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 displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces, and the indirect couplings or communication connections of the devices or units can be in electrical, mechanical, or other forms.
[0282] The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they can be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0283] If the functions are implemented in the form of software function 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 embodiments of the present application, in essence, or the part that contributes to the prior art or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing 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 methods described in the various embodiments of the present application. The foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, ROM, RAM, magnetic disks, or optical discs that can store program codes.
[0284] The above is only the specific implementation manner of the embodiments of the present application, but the protection scope of the embodiments of the present application is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the embodiments of the present application and should be covered by the protection scope of the embodiments of the present application.
Claims
1. A service generation method, characterized in that, The method is executed by a network device and a core network. 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 for supporting a target service. The service function information includes the service types and / or function types that each network element supporting the target service can provide. 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 types and / or function types that each network element supporting the target service can provide. The service context of the target service includes the 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 includes: The network device sets the service context of 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.
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 there is a service context of the target service locally. The network device sending the seventh request instruction to the core network specifically includes: When the network device determines that there is no service context of the target service locally, it sends the seventh request instruction to the core network.
4. The method according to claim 3, characterized in that, The method further includes: When the network device determines that there is a service context of the target service 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 takes effect. 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.
5. The method according to claim 3 or 4, characterized in that, The method further includes: 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-5, characterized in that, The method further includes: 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-6, characterized in that, The method further includes: The network device configures radio interface resources for the terminal device. The radio 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-7, characterized in that, The method further includes: The network device broadcasts or multicasts system messages. The system messages are used to indicate that the network device supports the target service.
9. The method according to any one of claims 1-8, characterized in that, The method further includes: 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 updates the service context corresponding to the at least one service context identifier according to the at least one service context identifier, which 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 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.
11. A service generation device, characterized in that, including: 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, and the service function information includes the service types and / or function types that each network element supporting the target service can provide; 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 types and / or function types that each network element supporting the target service can provide; The service context of the target service includes the relevant 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 configured to set the service context of 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.
13. The device according to claim 11 or 12, characterized in that, The transceiver unit is further configured to receive a first request instruction sent by the terminal device; the first request instruction is used to request the target service supported by the network device; The processing unit is further configured to detect whether the 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 configured to, when it is determined that the service context of the target service exists locally, determine 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 takes effect; 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.
15. The device according to claim 13 or 14, characterized in that, The transceiver unit 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.
16. The device according to any one of claims 11-15, characterized in that, The transceiver unit 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 is further configured to set the service context of the target service to an active state.
17. The device according to any one of claims 11-16, characterized in that, The processing unit is further configured to Configure radio resources for the terminal device; the radio 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-17, characterized in that, The transceiver unit is further configured 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-8, characterized in that, The transceiver unit is further configured 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; 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 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 configured 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 the 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, Comprising: At least one transceiver; At least one processor, the processor is configured to execute instructions stored in the memory to cause the network device to execute the method according to any one of claims 1-10.
22. A computer-readable storage medium, characterized in that, Comprising computer program instructions, when the computer program instructions are executed by the network device, the network device executes the method according to any one of claims 1-10.
Citation Information
Cited By
Service generation method and apparatus, and network device
EP4815518A1
Service generation method and apparatus, and network device
WO2025130521A1