Processing method, communication device and storage medium

Abstract

Disclosed in the present application are a processing method, a communication device and a storage medium. The processing method comprises: on the basis of first information, sending first content to a second device. By means of the technical solution of the present application, an existing sensing service process can be optimized, so as to support the satisfaction of the requirement for a serving SENF change.

Description

Processing methods, communication equipment and storage media Technical Field

[0001] This application relates to the field of communication technology, specifically to a processing method, communication device, and storage medium. Background Technology

[0002] In the existing protocol, the SENF (Sensing Function) change process supports changes to the service SENF due to periodic or triggered sensing events.

[0003] In the process of conceiving and implementing this application, the inventors discovered at least the following problems:

[0004] When the target and / or sensing task of the serving SENF used for mobility sensing changes, the serving AMF (Access and Mobility Management Function) will change, and the original serving SENF may no longer be applicable. For example, the serving SENF may be too far from the new serving AMF, resulting in excessive resource utilization of the new AMF-to-SENF signaling, and / or the original serving SENF may not be configured with the information (e.g., cell database) used by the current access network to enable sensing. In such cases, it is necessary to change the serving SENF, but how to change the serving SENF is not clearly defined in existing protocols. Therefore, it is necessary to optimize the existing sensing service process to support the requirements of serving SENF changes.

[0005] The preceding description is intended to provide general background information and does not necessarily constitute prior art. Technical solutions

[0006] The main objective of this application is to provide a processing method, communication device, and storage medium designed to optimize existing sensing service processes to support meeting service SENF change requirements.

[0007] This application provides a processing method applicable to a first device (such as a SENF), comprising the following steps:

[0008] S2: Send the first content to the second device based on the first information.

[0009] Optionally, the processing method further includes at least one of the following:

[0010] The first information includes at least one of the following: a first instruction, an event report message, operator configuration and / or policy, and descriptive information related to the second device;

[0011] The first message is sent by the third device;

[0012] The first information is sent by the third device after receiving the sensing service request;

[0013] The first content includes at least one of the following: information related to periodic or event-triggered perception service requests, perception context, event report message, third device identifier, current status of event report, and perception-related information;

[0014] The second device is determined by the third device;

[0015] The second device is determined by the first device.

[0016] Optionally, the processing method further includes at least one of the following:

[0017] Sensing service requests are triggered by terminal devices and / or access network devices;

[0018] The third device determines, based on the first information, that the first device is unsuitable for or unable to support the sensing of the current access network or serving cell.

[0019] The second device is determined by the third device based on the first information;

[0020] The second device is determined by the third device based on the second information;

[0021] Receive the first message;

[0022] Based on the first information, it is determined that the first device is not suitable for or cannot support the sensing of the current access network or serving cell;

[0023] The second device is determined based on the first information;

[0024] The second device is determined based on the second information;

[0025] Receive the result of the perception context transmission operation sent by the second device;

[0026] Release resources related to perception operations;

[0027] The second device sends an event report confirmation message to the third device;

[0028] The third device forwards the event report confirmation message from the second device to the terminal device and / or access network device;

[0029] The second device performs the sensing operation.

[0030] Optionally, the processing method further includes at least one of the following:

[0031] The description information related to the second device is obtained through local configuration of the first device or by querying the fourth device.

[0032] The description information related to the second device is obtained through the local configuration of the third device or by the first device querying the fourth device.

[0033] The current status of the event reports includes the number of event reports received and / or the duration of the event reports;

[0034] The perception-related information includes at least one of the following: previous perception estimates, timestamps of perception estimates, and perception measurements;

[0035] The second information includes at least one of the following: sensing service area, operator configuration and / or policy, description information related to the second device, sensing client type, requested sensing service quality information, access type, RAT type, serving AN node, RAN configuration information, duration of event report, event report indication, and network slice information.

[0036] The event report message includes an identifier indicating the first device;

[0037] The incident report confirmation message includes the identifier of the second device;

[0038] Event report confirmation messages are used to indicate changes to the current service's SENF;

[0039] The event report confirmation message is used to indicate that changes to the current service's SENF should be rejected;

[0040] The first device is the original SENF;

[0041] The second device is the target SENF;

[0042] The third device is AMF:

[0043] The fourth device is NRF.

[0044] Optionally, the processing method further includes at least one of the following:

[0045] The descriptive information related to the second device includes at least one of the following: the second device's capabilities, load, energy consumption and efficiency, location, supported GAD shape, and the user plane connection that the requested terminal device has with a portion of the SENF.

[0046] The requested perceived service quality information includes perception accuracy and / or response time;

[0047] The sensing service area includes at least one TA;

[0048] Incident reporting instructions include instructions for single incident reporting or multiple incident reporting;

[0049] The descriptive information related to the second device is registered in the fourth device.

[0050] This application also provides a processing method applicable to a third device (such as an AMF), comprising the following steps:

[0051] S1: Send first information so that the first device sends first content to the second device based on the first information.

[0052] Optionally, the processing method further includes at least one of the following:

[0053] The first information includes at least one of the following: a first instruction, an event report message, operator configuration and / or policy, and descriptive information related to the second device;

[0054] The first message is sent based on a perception service request;

[0055] The first content includes at least one of the following: information related to periodic or event-triggered perception service requests, perception context, event report message, third device identifier, current status of event report, and perception-related information;

[0056] The second device is determined by the third device;

[0057] The second device is determined by the first device.

[0058] Optionally, the processing method further includes at least one of the following:

[0059] Sensing service requests are triggered by terminal devices and / or access network devices;

[0060] Receive sensing service requests;

[0061] Based on the first information, it is determined that the first device is not suitable for or cannot support the sensing of the current access network or serving cell;

[0062] The first device determines, based on the first information, that the first device is not suitable for or cannot support the sensing of the current access network or serving cell.

[0063] The second device is determined by the first device or the third device based on the first information;

[0064] The second device is determined by the first device or the third device based on the second information;

[0065] The first device receives the result of the perception context transmission operation sent by the second device;

[0066] The first device releases resources related to sensing operations;

[0067] Receive the event report confirmation message sent by the second device;

[0068] Send an event report confirmation message from the second device to the terminal device and / or access network device;

[0069] The second device performs the sensing operation.

[0070] Optionally, the processing method further includes at least one of the following:

[0071] The description information related to the second device is obtained through local configuration on the third device or by querying the fourth device.

[0072] The description information related to the second device is obtained through the local configuration of the first device or by the first device querying the fourth device.

[0073] The current status of the event reports includes the number of event reports received and / or the duration of the event reports;

[0074] The perception-related information includes at least one of the following: previous perception estimates, timestamps of perception estimates, and perception measurements;

[0075] The second information includes at least one of the following: sensing service area, operator configuration and / or policy, description information related to the second device, sensing client type, requested sensing service quality information, access type, RAT type, serving AN node, RAN configuration information, duration of event report, event report indication, and network slice information.

[0076] The event report message includes an identifier indicating the first device;

[0077] The incident report confirmation message includes the identifier of the second device;

[0078] Event report confirmation messages are used to indicate changes to the current service's SENF;

[0079] The event report confirmation message is used to indicate that changes to the current service's SENF should be rejected;

[0080] The first device is the original SENF;

[0081] The second device is the target SENF;

[0082] The third device is AMF:

[0083] The fourth device is NRF.

[0084] Optionally, the processing method further includes at least one of the following:

[0085] The descriptive information related to the second device includes at least one of the following: the second device's capabilities, load, energy consumption and efficiency, location, supported GAD shape, and the user plane connection that the requested terminal device has with a portion of the SENF.

[0086] The requested perceived service quality information includes perception accuracy and / or response time;

[0087] The sensing service area includes at least one TA;

[0088] Incident reporting instructions include instructions for single incident reporting or multiple incident reporting;

[0089] The descriptive information related to the second device is registered in the fourth device.

[0090] This application also provides a processing method applicable to a second device (such as a SENF), comprising the following steps:

[0091] S3: Receive the first content, which is sent by the first device based on the first information.

[0092] Optionally, the processing method further includes at least one of the following:

[0093] The first information includes at least one of the following: a first instruction, an event report message, operator configuration and / or policy, and descriptive information related to the second device;

[0094] The first information is sent from the third device to the first device;

[0095] The first content includes at least one of the following: information related to periodic or event-triggered perception service requests, perception context, event report message, third device identifier, current status of event report, and perception-related information;

[0096] The second device is determined by the third device;

[0097] The second device is determined by the first device.

[0098] Optionally, the processing method further includes at least one of the following:

[0099] The first information is sent from the third device to the first device after receiving the sensing service request;

[0100] Sensing service requests are triggered by terminal devices and / or access network devices;

[0101] The third device determines, based on the first information, that the first device is unsuitable for or unable to support the sensing of the current access network or serving cell.

[0102] The second device is determined by the first device or the third device based on the first information;

[0103] The second device is determined by the first device or the third device based on the second information;

[0104] The first device determines, based on the first information, that the first device is not suitable for or cannot support the sensing of the current access network or serving cell.

[0105] Send the perception context transmission operation result to the first device;

[0106] The first device releases resources related to sensing operations;

[0107] Send an event report confirmation message to the third device;

[0108] The third device forwards the event report confirmation message from the second device to the terminal device and / or access network device;

[0109] Perform perception operations.

[0110] Optionally, the processing method further includes at least one of the following:

[0111] The description information related to the second device is obtained through the local configuration of the first device or by the first device querying the fourth device.

[0112] The description information related to the second device is obtained through the local configuration of the third device or by the third device querying the fourth device.

[0113] The current status of the event reports includes the number of event reports received and / or the duration of the event reports;

[0114] The perception-related information includes at least one of the following: previous perception estimates, timestamps of perception estimates, and perception measurements;

[0115] The second information includes at least one of the following: sensing service area, operator configuration and / or policy, description information related to the second device, sensing client type, requested sensing service quality information, access type, RAT type, serving AN node, RAN configuration information, duration of event report, event report indication, and network slice information.

[0116] The event report message includes an identifier indicating the first device;

[0117] The incident report confirmation message includes the identifier of the second device;

[0118] Event report confirmation messages are used to indicate changes to the current service's SENF;

[0119] The event report confirmation message is used to indicate that changes to the current service's SENF should be rejected;

[0120] The first device is the original SENF;

[0121] The second device is the target SENF;

[0122] The third device is AMF:

[0123] The fourth device is NRF.

[0124] Optionally, the processing method further includes at least one of the following:

[0125] The descriptive information related to the second device includes at least one of the following: the second device's capabilities, load, energy consumption and efficiency, location, supported GAD shape, and the user plane connection that the requested terminal device has with a portion of the SENF.

[0126] The requested perceived service quality information includes perception accuracy and / or response time;

[0127] The sensing service area includes at least one TA;

[0128] Incident reporting instructions include instructions for single incident reporting or multiple incident reporting;

[0129] The descriptive information related to the second device is registered in the fourth device.

[0130] This application also provides a processing apparatus, the processing apparatus comprising:

[0131] The first sending module is used to send the first content to the second device based on the first information.

[0132] This application also provides a processing apparatus, the apparatus comprising:

[0133] The second sending module is used to send first information so that the first device sends first content to the second device based on the first information.

[0134] This application also provides a processing apparatus, the apparatus comprising:

[0135] The receiving module is used to receive first content, which is sent by the first device based on first information.

[0136] This application also provides a communication device, including: a memory, a processor, and a processing program stored in the memory and executable on the processor, wherein the processing program, when executed by the processor, implements the steps of any of the processing methods described above.

[0137] The communication device in this application can be a first device (such as SENF), a second device (such as SENF), a third device (such as AMF), or a chip (such as SOC or a baseband chip with communication function, etc.). The specific meaning needs to be clarified in the context.

[0138] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of any of the processing methods described above.

[0139] In the technical solution of this application, the first device sends the first content to the second device based on the first information, which can optimize the existing perception service process to support and meet the service SENF change requirements. Attached Figure Description

[0140] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, those skilled in the art can obtain other drawings based on these drawings without any creative effort.

[0141] Figure 1 is a schematic diagram of the hardware structure of a mobile terminal implementing various embodiments of this application;

[0142] Figure 2 is a communication network system architecture diagram provided in an embodiment of this application;

[0143] Figure 3 is a diagram of another communication network system architecture provided in an embodiment of this application;

[0144] Figure 4 is a schematic diagram of the hardware structure of a controller 140 provided in this application;

[0145] Figure 5 is a schematic diagram of the hardware structure of a network node 150 provided in this application;

[0146] Figure 6 is a flowchart illustrating the processing method of the first embodiment of this application;

[0147] Figure 7 is a schematic diagram of an example scenario of the processing method shown in the second embodiment of this application;

[0148] Figure 8 is a schematic diagram of an example scenario of the processing method shown in the third embodiment of this application;

[0149] Figure 9 is a flowchart illustrating the processing method of the fourth embodiment of this application;

[0150] Figure 10 is a flowchart illustrating the processing method of the fifth embodiment of this application;

[0151] Figure 11 is a schematic diagram of the interaction flow of the first device, the second device and the third device of the processing method shown in the sixth embodiment of this application;

[0152] Figure 12 is a schematic diagram of the processing device provided in an embodiment of this application;

[0153] Figure 13 is a second schematic diagram of the processing device provided in an embodiment of this application;

[0154] Figure 14 is a schematic diagram of the processing device provided in an embodiment of this application;

[0155] Figure 15 is a schematic diagram of the structure of the communication device provided in the embodiment of this application.

[0156] The realization of the objectives, functional features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. The accompanying drawings have illustrated specific embodiments of this application, which will be described in more detail below. These drawings and textual descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concepts of this application to those skilled in the art through reference to specific embodiments.

[0157] Implementation methods of this application

[0158] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0159] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element, and / or, components, features, and elements with the same names in different embodiments of this application may have the same meaning or different meanings, the specific meaning of which must be determined by its interpretation in that specific embodiment or further in conjunction with the context of that specific embodiment.

[0160] It should be understood that although the terms first, second, third, etc., may be used herein to describe various information, such information should not be limited to these terms. These terms are used only to distinguish information of the same type from one another. For example, without departing from the scope of this document, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if," as used herein, may be interpreted as "when," "when," or "in response to determination." Furthermore, as used herein, the singular forms "a," "an," and "the" are intended to also include the plural forms unless the context indicates otherwise. It should be further understood that the terms "comprising," "including," indicate the presence of the stated feature, step, operation, element, component, item, kind, and / or group, but do not exclude the presence, occurrence, or addition of one or more other features, steps, operations, elements, components, items, kinds, and / or groups. The terms "or," "and / or," "including at least one of the following," etc., as used in this application, may be interpreted as inclusive, or mean any one or any combination thereof. For example, "including at least one of the following: A, B, C" means "any one of the following: A; B; C; A and B; A and C; B and C; A and B and C." Similarly, "A, B, or C" or "A, B, and / or C" means "any one of the following: A; B; C; A and B; A and C; B and C; A and B and C." Exceptions to this definition only occur when the combination of elements, functions, steps, or operations is inherently mutually exclusive in some way.

[0161] It should be understood that although the steps in the flowcharts of this application's embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least a portion of the sub-steps or stages of other steps.

[0162] Depending on the context, the words “if” or “suppose” as used here can be interpreted as “when” or “in response to determination” or “in response to detection.” Similarly, depending on the context, the phrases “if determination” or “if detection (of the stated condition or event)” can be interpreted as “when determination” or “in response to determination” or “when detection (of the stated condition or event)” or “in response to detection (of the stated condition or event).”

[0163] It should be noted that step designations such as S1 and S2 are used in this document for the purpose of more clearly and concisely describing the corresponding content, and do not constitute a substantial limitation on the order. In specific implementation, those skilled in the art may execute S2 first and then S1, etc., but these should all be within the protection scope of this application.

[0164] It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit this application.

[0165] In the following description, the use of suffixes such as "module," "part," or "unit" to denote elements is solely for the purpose of illustrative purposes and has no specific meaning in itself. Therefore, "module," "part," or "unit" may be used interchangeably.

[0166] The communication device in this application may be a first device or a second device (such as SENF), a third device (such as AMF), or a chip (such as SOC or a baseband chip with communication function, etc.). The specific meaning needs to be clarified according to the context.

[0167] Terminal devices can be implemented in various forms. For example, the terminal devices described in this application may include smart terminal devices such as mobile phones, tablets, laptops, handheld computers, personal digital assistants (PDAs), portable media players (PMPs), navigation devices, wearable devices, smart bracelets, pedometers, etc., as well as fixed terminal devices such as digital TVs and desktop computers.

[0168] The following description will use a mobile terminal as an example. Those skilled in the art will understand that, apart from elements specifically designed for mobile purposes, the construction according to the embodiments of this application can also be applied to fixed-type terminal devices.

[0169] Please refer to Figure 1, which is a schematic diagram of the hardware structure of a mobile terminal implementing various embodiments of this application. The mobile terminal 100 may include: a radio frequency unit 101, a WiFi module 102, an audio output unit 103, an A / V (audio / video) input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, a processor 110, and a power supply 111, etc. Those skilled in the art will understand that the mobile terminal structure shown in Figure 1 does not constitute a limitation on the mobile terminal. The mobile terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0170] The following section, with reference to Figure 1, provides a detailed description of each component of the mobile terminal:

[0171] The radio frequency unit 101 can be used for receiving and transmitting signals during information transmission or calls. Specifically, it receives downlink information from the base station and processes it with the processor 110; additionally, it transmits uplink data to the base station. Typically, the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc. And / or, the radio frequency unit 101 can also communicate wirelessly with networks and other devices. The aforementioned wireless communications may use any communication standard or protocol, including but not limited to GSM (Global System of Mobile communication), GPRS (General Packet Radio Service), CDMA2000 (Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division Duplexing-Long Term Evolution), TDD-LTE (Time Division Duplexing-Long Term Evolution), 5G, and 6G.

[0172] WiFi is a short-range wireless transmission technology. Mobile terminals using WiFi module 102 can help users send and receive emails, browse web pages, and access streaming media, providing wireless broadband internet access. Although Figure 1 shows WiFi module 102, it is understood that it is not an essential component of the mobile terminal and can be omitted as needed without altering the essence of the invention.

[0173] The audio output unit 103 can convert audio data received by the radio frequency unit 101 or the WiFi module 102 or stored in the memory 109 into audio signals and output them as sound when the mobile terminal 100 is in call signal receiving mode, call mode, recording mode, voice recognition mode, broadcast receiving mode, or other modes. Furthermore, the audio output unit 103 can also provide audio output related to specific functions performed by the mobile terminal 100 (e.g., call signal receiving sound, message receiving sound, etc.). The audio output unit 103 may include a speaker, a buzzer, etc.

[0174] The A / V input unit 104 is used to receive audio or video signals. The A / V input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042. The GPU 1041 processes image data of still images or videos acquired by an image capture device (such as a camera) in video capture mode or image capture mode. The processed image frames can be displayed on the display unit 106. The image frames processed by the GPU 1041 can be stored in the memory 109 (or other storage medium) or transmitted via the radio frequency unit 101 or the WiFi module 102. The microphone 1042 can receive sound (audio data) in operating modes such as telephone call mode, recording mode, and voice recognition mode, and can process such sound into audio data. The processed audio (voice) data can be converted into a format that can be transmitted to a mobile communication base station via the radio frequency unit 101 in telephone call mode. The microphone 1042 can implement various types of noise cancellation (or suppression) algorithms to eliminate (or suppress) noise or interference generated during the reception and transmission of audio signals.

[0175] The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Optionally, the light sensor includes an ambient light sensor and a proximity sensor. Optionally, the ambient light sensor can adjust the brightness of the display panel 1061 according to the ambient light level, and the proximity sensor can turn off the display panel 1061 and / or backlight when the mobile terminal 100 is moved to the ear. As a type of motion sensor, an accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes), and can detect the magnitude and direction of gravity when stationary. It can be used for applications that recognize the phone's posture (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc. Other sensors that may be configured in the phone, such as fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, and infrared sensors, will not be described in detail here.

[0176] The display unit 106 is used to display information input by the user or information provided to the user. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0177] User input unit 107 can be used to receive input numerical or character information, and generate key signal inputs related to user settings and function control of the mobile terminal. Optionally, user input unit 107 may include touch panel 1071 and other input devices 1072. Touch panel 1071, also known as touch screen, can collect touch operations on or near the user (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near touch panel 1071), and drive corresponding connection devices according to a pre-set program. Touch panel 1071 may include two parts: touch detection device and touch controller. Optionally, touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to touch controller; touch controller receives touch information from touch detection device, converts it into touch point coordinates, sends it to processor 110, and can receive and execute commands from processor 110. And / or, touch panel 1071 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may also include other input devices 1072. Optionally, other input devices 1072 may include, but are not limited to, one or more of the following: physical keyboard, function keys (such as volume control buttons, power buttons, etc.), trackball, mouse, joystick, etc., without being specifically limited here.

[0178] Optionally, the touch panel 1071 may cover the display panel 1061. When the touch panel 1071 detects a touch operation on or near it, it transmits the information to the processor 110 to determine the type of touch event. Subsequently, the processor 110 provides corresponding visual output on the display panel 1061 according to the type of touch event. Although in FIG. 1, the touch panel 1071 and the display panel 1061 are implemented as two independent components to realize the input and output functions of the mobile terminal, in some embodiments, the touch panel 1071 and the display panel 1061 can be integrated to realize the input and output functions of the mobile terminal. The specific implementation is not limited here.

[0179] Interface unit 108 serves as an interface through which at least one external device can connect to mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, etc. Interface unit 108 may be used to receive input (e.g., data, power, etc.) from the external device and transmit the received input to one or more components within mobile terminal 100, or it may be used to transmit data between mobile terminal 100 and the external device.

[0180] The memory 109 can be used to store software programs and various data. The memory 109 may primarily include a program storage area and a data storage area. Optionally, the program storage area may store the operating system, applications required for at least one function (such as sound playback, image playback, etc.), etc.; the data storage area may store data created based on the use of the mobile phone (such as audio data, phonebook, etc.). And / or, the memory 109 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0181] The processor 110 is the control center of the mobile terminal. It connects various parts of the mobile terminal via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 109, and by calling data stored in the memory 109, it performs various functions and processes data of the mobile terminal, thereby providing overall monitoring of the mobile terminal. The processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor and a modem processor. Optionally, the application processor mainly handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 110.

[0182] The mobile terminal 100 may also include a power supply 111 (such as a battery) that supplies power to various components. Preferably, the power supply 111 can be logically connected to the processor 110 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system.

[0183] Although not shown in Figure 1, the mobile terminal 100 may also include a Bluetooth module, etc., which will not be described in detail here.

[0184] To facilitate understanding of the embodiments of this application, the communication network system on which the mobile terminal of this application is based is described below.

[0185] Please refer to Figure 2, which is a communication network system architecture diagram provided in an embodiment of this application. The communication network system is an NR (New Radio) system based on general mobile communication technology, and is at least applied to 5G systems. The communication network system architecture includes 5GC (5G core network) and NG-RAN (5G radio access network). 5GC includes: AMF (Access and Mobility Management Function) and UPF (User Plane Function Entity); NG-RAN includes gNB, ng-gNB, etc.

[0186] The AMF (Automatic Facilitation Module) is used to perform registration, connection, reachability, and mobility management. It provides a session management message transmission channel for the UE and SMF, and offers authentication and authorization functions for user access. It is the access point for the UE (User Equipment) and the core network control plane of the radio. The UPF (User PF) is used for packet routing and forwarding, policy enforcement, traffic reporting, QoS processing, etc. The gNB (Gateway Base Station) is a key unit in the 5G (NR) wireless communication system. As a base station in the 5G Radio Access Network (RAN), it is responsible for establishing wireless connections with the UE and for data transmission between the UE and the core network.

[0187] Optionally, the communication network system architecture may also include the following service-based interfaces: Xn interface and NG interface, where Xn is the interface between gNBs (ng-gNBs); and NG is the interface between gNBs (ng-gNBs) and AMF and / or UPF.

[0188] Although the above description uses LTE and NR systems as examples, those skilled in the art should know that this application is not only applicable to LTE and NR systems, but also to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, 5GA, and future new network systems (such as 6G), etc., without limitation here.

[0189] Please refer to Figure 3, which is another communication network system architecture diagram provided in the embodiments of this application. The communication network system is a NR (New Radio) system of general mobile communication technology, which is at least applied to 5G systems. The network functions (NF) of the communication network system architecture may include: AUSF (Authentication Service Function), AMF (Access and Mobility Management Function), DN (Data Network) (e.g., operator services, Internet access or third-party services), NEF (Network Exposure Function), NRF (Network Repository Function), NSACF (Network Slice Admission Control Function), NSSAAF (Network Slice-Specific and SNPN Authentication and Authorization Function), NSSF (Network Slice Selection Function), PCF (Policy Control Function), SMF (Session Management Function), UDM (Unified Data Management), UPF (User Plane Function), AF (Application Function), UE (User Equipment), (R)AN ((Radio) Access Network), and EASDF (Edge Application Server Discovery Function).

[0190] Optionally, the communication network system architecture may also include the following network entities: SCP (Serving Communication Agent) and multiple interfaces. Specifically, interface N1 is the interface between the UE and AMF, N2 is the interface between the RAN and AMF, N3 is the interface between the RAN and UPF, N4 is the interface between the UPF and SMF, N6 is the interface between the UPF and DN, and N9 is the interface between UPFs.

[0191] Optionally, the communication network system architecture may further include the following service-based interfaces: Namf, Nsmf, Nnef, Npcf, Nudm, Naf, Nnrf, Nnsacf, Nnssf, Nnssaaf, Nausf, Neasdf, and Nupf, wherein Namf is the service-based interface presented by AMF, Nsmf is the service-based interface presented by SMF, Nnef is the service-based interface presented by NEF, Npcf is the service-based interface presented by PCF, Nudm is the service-based interface presented by UDM, Naf is the service-based interface presented by AF, Nnrf is the service-based interface presented by NRF, Nnsacf is the service-based interface presented by NSACF, Nnssf is the service-based interface presented by NSSF, Nnssaaf is the service-based interface presented by NSSAAF, Nausf is the service-based interface presented by AUSF, Neasdf is the service-based interface presented by EASDF, and Nupf is the service-based interface presented by UPF.

[0192] Although the above description uses LTE and NR systems as examples, those skilled in the art should know that this application is not only applicable to LTE and NR systems, but also to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, 5GA, and future new network systems (such as 6G), etc., without limitation here.

[0193] Figure 4 is a schematic diagram of the hardware structure of a controller 140 provided in this application. The controller 140 includes a memory 1401 and a processor 1402. The memory 1401 is used to store program instructions, and the processor 1402 is used to call the program instructions in the memory 1401 to execute the steps performed by the controller in the first embodiment of the above method. The implementation principle and beneficial effects are similar, and will not be described again here.

[0194] Optionally, the controller further includes a communication interface 1403, which can be connected to the processor 1402 via a bus 1404. The processor 1402 can control the communication interface 1403 to implement the receiving and sending functions of the controller 140.

[0195] Figure 5 is a schematic diagram of the hardware structure of a network node 150 provided in this application. The network node 150 includes a memory 1501 and a processor 1502. The memory 1501 is used to store program instructions, and the processor 1502 is used to call the program instructions in the memory 1501 to execute the steps performed by the first node in the above-described method embodiment. The implementation principle and beneficial effects are similar, and will not be described again here.

[0196] Optionally, the controller further includes a communication interface 1503, which can be connected to the processor 1502 via a bus 1504. The processor 1502 can control the communication interface 1503 to implement the receiving and sending functions of the network node 150.

[0197] The integrated modules described above, implemented as software functional modules, can be stored in a computer-readable storage medium. These software functional modules, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute some steps of the methods of the various embodiments of this application.

[0198] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a storage medium or transmitted from one storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk, SSD), etc.

[0199] Based on the above-described mobile terminal hardware structure and communication network system, various embodiments of this application are proposed.

[0200] Technical terms used in this embodiment:

[0201] A-IoT: Ambient IoT;

[0202] IoT: Internet of Things;

[0203] TrCH: Transport Channel;

[0204] LPWAN: Low-Power Wide Area Network;

[0205] MTC: Machine Type Communication;

[0206] NB-IoT: Narrow Band Internet of Things;

[0207] RedCap: Reduced Capability, lightweight;

[0208] RRC_INACTIVE state: RRC disconnected state;

[0209] RRC: Radio Resource Control;

[0210] RRC decoding: RRC decoding;

[0211] RSRP: Reference Signal Receiving Power;

[0212] 5GC: 5G Core network;

[0213] ADRF: Analytics Data Repository Function, an entity or network element that provides analytics data repository functionality.

[0214] AF: Application Function, or network element;

[0215] AMF; Access and Mobility Management Function, an entity or network element that provides access and mobility management functions.

[0216] AUSF: Authentication Server Function, an authentication server functional entity or network element;

[0217] DN: Data Network;

[0218] NEF: Network Exposure Function, a network exposure function entity or network element.

[0219] NF: Network Function, a network functional entity or network element;

[0220] NR: New Radio;

[0221] NRF: Network Repository Function, a network repository functional entity or network element;

[0222] NWDAF: Network Data Analytics Function, a network data analysis function entity or network element;

[0223] OTT: Over The Top;

[0224] PCF: Policy Control Function, a policy control function entity or network element;

[0225] PDU: Protocol Data Unit;

[0226] (R)AN: (Radio)Access Network;

[0227] SMF: Session Management Function, a network element or entity that performs session management functions.

[0228] UDM: Unified Data Management;

[0229] UE: User Equipment, terminal equipment;

[0230] UPF: User Plane Function, a user plane function entity or network element;

[0231] NG-RAN: 5G Radio Access Network;

[0232] SENF: Sensing Function, a sensing functional entity or network element;

[0233] GMSENC: Gateway Mobile Sensing Centre;

[0234] GAD: Universal Geographical Area Description;

[0235] SUPI: SUbscription Permanent Identifier;

[0236] ISAC: Integrated Sensing and Communication;

[0237] NAS: Non-Access Stratum;

[0238] TA: Timing Advance;

[0239] RAT: Radio Access Technology;

[0240] AN: Access Network.

[0241] First Embodiment

[0242] Referring to Figure 6, which is a flowchart illustrating the processing method of the first embodiment of this application, the processing method of this embodiment can be applied to a first device (such as SENF), including step S2:

[0243] Step S2: The first device sends the first content to the second device based on the first information.

[0244] This embodiment takes into account that when the target and / or sensing task of the serving SENF for mobility sensing changes, the serving AMF (Access and Mobility Management Function Entity) may change, and the original serving SENF may no longer be applicable. For example, the serving SENF may be too far from the new serving AMF, resulting in excessively high resource utilization of the new AMF-to-SENF signaling, and / or the original serving SENF may not be configured with the information (e.g., cell database) used by the current access network to enable sensing. In such cases, it is necessary to change the serving SENF, but how to change the serving SENF is not clearly defined in existing protocols.

[0245] Therefore, this embodiment proposes a technical solution in which the first device sends the first content to the second device based on the first information, thereby optimizing the existing perception service process to support and meet the service SENF change requirements.

[0246] Optionally, the first device is the original SENF.

[0247] Optionally, the second device is the target SENF, that is, the second device is the modified SENF, or the new SENF.

[0248] Optionally, since the SENF has changed, the relevant information of the original SENF for sensing operations needs to be provided to the new SENF, that is, the first device needs to send the first content to the second device.

[0249] Optionally, the first content includes at least one of the following: information related to periodic or event-triggered perception service requests, perception context, event report message, third device identifier, current status of the event report, and perception-related information.

[0250] Optionally, the current status of the event report includes the number of event reports received by the first device and / or the duration of the event reports.

[0251] Optionally, the perception-related information includes at least one of the following: a previous perception estimate of the first device, a timestamp of the perception estimate, and a perception measurement value.

[0252] Optionally, the first device sends the first content to the second device based on the first information.

[0253] Optionally, the first information is sent from the third device to the first device.

[0254] Optionally, the third device is an AMF.

[0255] Optionally, the first information is sent from the third device to the first device after the third device receives the sensing service request.

[0256] Optionally, the sensing service request is triggered by at least one of the terminal device, access network device, and third device.

[0257] Optionally, the terminal device and / or access network device triggers a sensing service request, and the terminal device and / or access network device sends the sensing service request to the third device.

[0258] Optionally, the third device sends the first information to the first device according to the sensing service request.

[0259] Optionally, the first information includes at least one of the following: a first instruction, an event report message, operator configuration and / or policy, and descriptive information related to the second device.

[0260] Optionally, the event report message is sent by the terminal device and / or access network device to the third device.

[0261] Optionally, the terminal device and the third device communicate via NAS (Non-Access Layer) message transmission. Optionally, the event report message sent by the terminal device to the third device is carried via NAS message transmission.

[0262] Optionally, the access network device and the third device communicate via S1 transmission messages, i.e., via the S1 interface. Optionally, the event report messages sent by the access network device to the third device are carried via NAS transmission messages.

[0263] Optionally, the event reporting message includes an identifier indicating the first device (i.e., the original SENF).

[0264] Optionally, the first instruction is used to instruct the first device that the third device has determined to use the new second device, that is, the third device has determined the new SENF.

[0265] Optionally, the descriptive information related to the second device includes at least one of the following: the second device's capabilities, load, energy consumption and efficiency, location, supported GAD shape, and the user plane connection that the requested terminal device has with a portion of the SENF.

[0266] Optionally, operator configuration and / or policies are used to evaluate and determine whether the first device (i.e., the original SENF) is suitable for or supports the current access network or serving cell perception, and / or to determine whether the second device (i.e., the target SENF or the new SENF) is a more suitable SENF.

[0267] Optionally, as a scenario, the second device is determined by the third device, that is, how to select the appropriate SENF is determined by the third device.

[0268] Optionally, the second device is determined by the third device based on the first information.

[0269] Optionally, the third device determines, based on the first information, that the first device is unsuitable for or unable to support the sensing of the current access network or serving cell.

[0270] Optionally, the third device determines, based on operator configuration and / or policies, that the first device is unsuitable for or unable to support sensing of the current access network or serving cell.

[0271] Optionally, the third device determines the second device based on the first information, i.e., selects a suitable SENF.

[0272] Optionally, the second device is determined by the third device based on the second information.

[0273] Optionally, the second information includes at least one of the following: sense service area, operator configuration and / or policy, description information related to the second device, sense client type, requested sense service quality information, access type, RAT type, service AN node, RAN configuration information, duration of event report, event report indication, and network slice information.

[0274] Optionally, the sensing service area includes at least one TA.

[0275] Optionally, the requested perceived quality of service information may include perceived accuracy and / or response time.

[0276] Optionally, the event reporting indication includes indicating a single event report or multiple event reports.

[0277] Optionally, after the terminal device and / or access network device triggers a sensing service request, it sends an event report message to the third device.

[0278] Optionally, the third device receives event report messages from the terminal device and / or access network device.

[0279] Optionally, after receiving the event report message, the third device evaluates and determines whether the first device (i.e., the original SENF) is suitable for or supports the current access network or serving cell's perception based on the operator's configuration and / or policy, and / or determines whether the second device (i.e., the target SENF or the new SENF) is a more suitable SENF.

[0280] Optionally, if the third device evaluates and determines, based on operator configuration and / or policies, that the first device is unsuitable or unable to support the current access network or serving cell perception, the third device determines that the SENF needs to be changed and selects or determines the second device, i.e., determines a more suitable new SENF.

[0281] Optionally, the third device determines the second device based on the descriptive information related to the second device.

[0282] Optionally, the third device may be locally configured with information about the second device.

[0283] Optionally, the descriptive information related to the second device can be obtained through the local configuration of the third device.

[0284] Optionally, the descriptive information related to the second device can be obtained by querying the fourth device through the third device.

[0285] Optionally, the descriptive information related to the second device is registered in the fourth device.

[0286] Optionally, the fourth device is an NRF.

[0287] Optionally, the third device determines the second device based on the second information.

[0288] Optionally, the third device selects a second device, i.e. a new SENF, for the current sensing operation based on at least one of the following: sensing service area (consisting of one or more TAs), operator configuration and / or policies, description information related to the second device, sensing client type, requested sensing service quality information, access type, RAT type, serving AN node, RAN configuration information, event report duration, event report indication, and network slice information.

[0289] Optionally, the third device invokes the Namf_Communication_N1N2MessageNotify service operation to send the first message to the first device.

[0290] Optionally, the Namf_Communication_N1N2MessageNotify service operation includes event reporting messages received by a third device from a terminal device and / or an access network device.

[0291] Optionally, if the third device determines to use the new SENF, it sends a first instruction in the first message to indicate to the first device that the third device has determined to use the new SENF.

[0292] Alternatively, as another scenario, the second device is determined by the first device, that is, how to select a suitable SENF is determined by the first device.

[0293] Optionally, the second device is determined by the first device based on the first information.

[0294] Optionally, the first device receives the first information.

[0295] Optionally, the first information does not contain a first instruction, or the first information does not indicate a second device to the first device, i.e., it does not indicate a new SENF.

[0296] Optionally, the first device determines, based on the first information, whether the first device is unsuitable or unable to support the perception of the currently accessed network or serving cell.

[0297] Optionally, if the first device determines based on the first information that the first device is not suitable for or cannot support the perception of the current access network or serving cell, the first device determines that a change operation is required and determines the changed second device, that is, determines a more suitable new SENF.

[0298] Optionally, the first device determines, based on operator configuration and / or policies, that the first device is unsuitable for or unable to support sensing of the current access network or serving cell.

[0299] Optionally, the second device is determined by the first device based on the second information.

[0300] Optionally, after receiving the first information, the first device determines the second device based on the second information.

[0301] Optionally, the descriptive information related to the second device can be obtained through local configuration of the first device or by querying the fourth device.

[0302] Optionally, after determining the second device, or after obtaining information about the second device according to the instructions of the third device, the first device sends the first content to the determined second device.

[0303] Optionally, the first device invokes the Nsenf_Sensing_SensingContextTransfer Request service operation to send the first content to the second device.

[0304] Optionally, the first device invokes the Nsenf_Sensing_SensingContextTransfer Request service operation to send the second device at least one of the following: periodic or event-triggered sensing service request information, sensing context, event report message, third device identifier, current status of the event report, and sensing-related information.

[0305] Optionally, the second device sends the result of the perception context transmission operation to the first device.

[0306] Optionally, the first device receives the result of the perception context transmission operation sent by the second device.

[0307] Optionally, after receiving the perception context transmission operation result sent by the second device, the first device releases the resources related to the perception operation.

[0308] Optionally, the second device invokes the Namf_Communication_N1N2MessageTransfer service operation to the third device to request a transmission service event report confirmation message.

[0309] Optionally, the second device sends an event report confirmation message to the third device.

[0310] Optionally, the event report confirmation message includes the identifier of the second device.

[0311] Optionally, the event report confirmation message is used to indicate the change of the current service SENF, that is, the second device confirms its agreement to the change of the current service SENF through the event report confirmation message.

[0312] Optionally, the event report confirmation message is used to indicate rejection of the change to the current service SENF, that is, the second device rejects the change to the current service SENF through the event report confirmation message.

[0313] Optionally, if the second device rejects the change of the current service SENF, the third device may reselect a new and appropriate SENF.

[0314] Optionally, if the second device agrees to the change of the current service SENF, the third device forwards the event report confirmation message from the second device to the terminal device and / or access network device.

[0315] Optionally, the third device forwards the event report confirmation message from the second device to the terminal device via NAS transmission message.

[0316] Optionally, the third device forwards the event report confirmation message from the second device to the access network device via S1 transmission message.

[0317] Optionally, after forwarding the event report confirmation message from the second device to the terminal device and / or the access network device, the third device sends the event report confirmation transmission result to the second device.

[0318] Optionally, if the event report indicates that perception estimation is required, the second device performs the perception operation.

[0319] Optionally, the second device retains status information to support subsequent event reporting.

[0320] Through the technical solution of this embodiment, the first device sends the first content to the second device based on the first information, which can optimize the existing perception service process and support the service SENF change requirements.

[0321] Second Embodiment

[0322] Based on the first embodiment of this application, a second embodiment of this application is proposed, which further discloses a method for selecting and / or changing SENF (Sensing Functional Element).

[0323] Optionally, the first device sends the first content to the second device based on the first information, thereby optimizing the existing sensing service process to support meeting the service SENF change requirements.

[0324] Optionally, the first device is the original SENF.

[0325] Optionally, the second device is the target SENF, that is, the second device is the modified SENF, or the new SENF.

[0326] Optionally, since the SENF has changed, the relevant information of the original SENF for sensing operations needs to be provided to the new SENF, that is, the first device needs to send the first content to the second device.

[0327] Optionally, the first information is sent from the third device to the first device.

[0328] Optionally, the third device is an AMF.

[0329] Optionally, the second device is determined by the third device, that is, the selection of a suitable new SENF is determined by the third device.

[0330] Optionally, as shown in Figure 7, the system architecture involved in this embodiment includes a first device (such as the original SENF), a second device (the target SENF), a third device (such as the AMF), a fourth device (such as the NRF), a terminal device (such as the UE), and an access network device (such as the NG-RAN). The process of selecting and / or changing the SENF in this embodiment includes the following steps 1 to 11:

[0331] Step 1. The terminal device and / or access network device and / or third-party device triggers a sensing service request;

[0332] Optionally, the sensing service request is triggered by at least one of the terminal device, the access network device, and the third device.

[0333] Optionally, the terminal device and / or access network device triggers a sensing service request, and the terminal device and / or access network device sends the sensing service request to the third device.

[0334] Optionally, the UE, NG-RAN, or AMF triggers a sensing service request.

[0335] Step 2. The terminal device sends a non-access stratum transmission message;

[0336] Optionally, after the terminal device triggers the sensing service request, it sends an event report message to the third device.

[0337] Optionally, the terminal device and the third device communicate by transmitting messages through NAS (Non-Access Layer).

[0338] Optionally, the event report message sent by the terminal device to the third device is carried via NAS transmission message.

[0339] Optionally, the NAS transmission message (AMF-UE inter-message) sent by the UE includes an event report message sent to the serving AMF.

[0340] Optionally, the event reporting message includes an identifier indicating the first device (i.e., the original SENF).

[0341] Step 3. The access network device sends an S1 transmission message;

[0342] Optionally, after the access network device triggers the sensing service request, it sends an event report message to the third device.

[0343] Optionally, the access network device and the third device communicate via S1 to transmit messages.

[0344] Optionally, the event report message sent by the access network device to the third device is carried through the NAS transmission message.

[0345] Optionally, the S1 transport message (AMF and gNB inter-message) sent by the NG-RAN includes an event report message sent to the serving AMF.

[0346] Optionally, the event reporting message includes an identifier indicating the first device (i.e., the original SENF).

[0347] Step 4. The third device determines the second device;

[0348] Optionally, the second device is determined by the third device, that is, the selection of a suitable SENF is determined by the third device.

[0349] Optionally, after receiving the event report message, the third device evaluates and determines whether the first device (i.e., the original SENF) is suitable for or supports the current access network or serving cell's perception based on the operator's configuration and / or policy, and / or determines whether the second device (i.e., the target SENF or the new SENF) is a more suitable SENF.

[0350] Optionally, if the third device evaluates and determines, based on operator configuration and / or policies, that the first device is unsuitable or unable to support the current access network or serving cell perception, the third device determines that the SENF needs to be changed and selects or determines the second device, i.e., determines a more suitable new SENF.

[0351] Optionally, the third device selects a second device, i.e. a new SENF, for the current sensing operation based on at least one of the following: sensing service area (consisting of one or more TAs), operator configuration and / or policies, description information related to the second device, sensing client type, requested sensing service quality information, access type, RAT type, serving AN node, RAN configuration information, event report duration, event report indication, and network slice information.

[0352] Optionally, the descriptive information related to the second device includes at least one of the following: the second device's capabilities, load, energy consumption and efficiency, location, supported GAD shape, and the user plane connection that the requested terminal device has with a portion of the SENF.

[0353] Optionally, the third device may have the second device information locally configured, for example, obtained from previous NRF discovery or local configuration.

[0354] Optionally, the descriptive information related to the second device can be obtained through the local configuration of the third device.

[0355] Optionally, the description information related to the second device is registered in the fourth device, and the third device can query the fourth device to obtain the description information related to the second device.

[0356] Optionally, based on operator configuration and policies, the AMF can assess and determine that the original SENF is unsuitable or unable to support the awareness of the current access network or serving cell, and determine a more suitable target SENF.

[0357] Optionally, the NRF returns a set of SENF profiles via response messages based on the AMF's query request, and then selects the appropriate target SENF based on the SENF profiles.

[0358] Step 5. The third device sends the first information to the first device;

[0359] Optionally, the first information includes at least one of the following: a first instruction, an event report message, operator configuration and / or policy, and descriptive information related to the second device.

[0360] Optionally, the third device invokes the Namf_Communication_N1N2MessageNotify service operation to send the first message to the first device.

[0361] Optionally, the Namf_Communication_N1N2MessageNotify service operation includes event reporting messages received by a third device from a terminal device and / or an access network device.

[0362] Optionally, if the third device determines to use the new SENF, it sends a first instruction in the first message to indicate to the first device that the third device has determined to use the new SENF.

[0363] Optionally, the AMF invokes the Namf_Communication_N1N2MessageNotify service operation to the original SENF. Optionally, this service operation includes the event reporting message received in step 2 or step 3.

[0364] Optionally, if the AMF determines in step 4 to use the new SENF, the AMF indicates to the original SENF.

[0365] Step 6. The first device sends the first content to the second device;

[0366] Optionally, after obtaining the information of the second device according to the instructions of the third device, the first device sends the first content to the determined second device.

[0367] Optionally, the first device invokes the Nsenf_Sensing_SensingContextTransfer Request service operation to send the first content to the second device.

[0368] Optionally, the first device invokes the Nsenf_Sensing_SensingContextTransfer Request service operation to send the second device at least one of the following: periodic or event-triggered sensing service request information, sensing context, event report message, third device identifier, current status of the event report, and sensing-related information.

[0369] Optionally, the original SENF invokes the Nsenf_Sensing_SensingContextTransfer Request service operation to the target SENF to provide the current sensing context, including the event report message received in step 5.

[0370] Optionally, the Nsenf_Sensing_SensingContextTransfer Request service operation includes the AMF identifier and all information originally received by the original SENF from the AMF or from an earlier service SENF for periodic or triggered sensing requests according to this process.

[0371] Optionally, the Nsenf_Sensing_SensingContextTransfer Request service operation may also include the current status of the event reports (e.g., the number of event reports received so far and / or the duration of the event reports so far), and may also include perception-related information, such as previous perception estimates and / or timestamps of perception estimates (if available) or perception measurements.

[0372] Step 7. The second device sends the perception context transmission operation result to the first device;

[0373] Optionally, the first device receives the result of the perception context transmission operation sent by the second device.

[0374] Optionally, after receiving the perception context transmission operation result sent by the second device, the first device releases the resources related to the perception operation.

[0375] Optionally, the target SENF invokes the Nsenf_Sensing_SensingContextTransfer Response service operation to notify the original SENF of the result of the sensing context transfer operation. Then, the original SENF releases all resources from this process.

[0376] Step 8. The second device sends a service event report confirmation message to the third device;

[0377] Optionally, the second device invokes the Namf_Communication_N1N2MessageTransfer service operation to the third device to request a transmission service event report confirmation message.

[0378] Optionally, the second device sends an event report confirmation message to the third device.

[0379] Optionally, the event report confirmation message includes the identifier of the second device.

[0380] Optionally, the event report confirmation message is used to indicate the change of the current service SENF, that is, the second device confirms its agreement to the change of the current service SENF through the event report confirmation message.

[0381] Optionally, the event report confirmation message is used to indicate rejection of the change to the current service SENF, that is, the second device rejects the change to the current service SENF through the event report confirmation message.

[0382] Optionally, if the second device rejects the change of the current service SENF, the third device may reselect a new and appropriate SENF.

[0383] Optionally, the target SENF invokes the Namf_Communication_N1N2MessageTransfer service operation to the AMF to request the transmission of an event report acknowledgment message. Optionally, the event report acknowledgment message indicates a change in the SENF and includes a routing identifier indicating the target SENF.

[0384] Step 9. The third device forwards the event report confirmation message to the terminal device via the non-access stratum transmission message;

[0385] Optionally, if the second device agrees to the change of the current service SENF, the third device forwards the event report confirmation message from the second device to the terminal device.

[0386] Optionally, the third device forwards the event report confirmation message from the second device to the terminal device via NAS transmission message.

[0387] Optionally, the AMF forwards an event report confirmation message to the UE in the NAS transmission message.

[0388] Optionally, the AMF also notifies the target SENF of the delivery result of the event report confirmation message.

[0389] Step 10. The third device forwards the event report confirmation message to the access network device via S1 transmission message;

[0390] Optionally, if the second device agrees to the change of the current service SENF, the third device forwards the event report confirmation message from the second device to the access network device.

[0391] Optionally, the third device forwards the event report confirmation message from the second device to the access network device via S1 transmission message.

[0392] Optionally, after forwarding the event report confirmation message from the second device to the terminal device and / or the access network device, the third device sends the event report confirmation transmission result to the second device.

[0393] Optionally, the AMF forwards the event report confirmation message to the NG-RAN in the S1 transmission message.

[0394] Optionally, the AMF will also notify the target SENF of the delivery result of the event report confirmation message.

[0395] Step 11. The second device performs a sensing operation.

[0396] Optionally, if the event report indicates that a perception estimate is required, the second device performs the perception operation.

[0397] Optionally, the second device retains status information to support subsequent event reporting.

[0398] Optionally, if an event report indicates that perception estimation is required, the target SENF can perform perception estimation.

[0399] Through the technical solution of this embodiment, the first device sends the first content to the second device based on the first information, wherein the second device is determined by the third device. This can optimize the existing perception service process to support and meet the service SENF change requirements.

[0400] Third Embodiment

[0401] Based on any of the above embodiments of this application, a third embodiment of this application is proposed, which further discloses a method for selecting and / or changing SENF.

[0402] Optionally, the first device sends the first content to the second device based on the first information, thereby optimizing the existing sensing service process to support meeting the service SENF change requirements.

[0403] Optionally, the first device is the original SENF.

[0404] Optionally, the second device is the target SENF, that is, the second device is the modified SENF, or the new SENF.

[0405] Optionally, since the SENF has changed, the relevant information of the original SENF for sensing operations needs to be provided to the new SENF, that is, the first device needs to send the first content to the second device.

[0406] Optionally, the first information is sent from the third device to the first device.

[0407] Optionally, the third device is an AMF.

[0408] Optionally, the second device is determined by the first device, that is, how to select a suitable new SENF is determined by the first device.

[0409] Optionally, as shown in Figure 8, the system architecture involved in this embodiment includes a first device (such as the original SENF), a second device (the target SENF), a third device (such as the AMF), a fourth device (such as the NRF), a terminal device (such as the UE), and an access network device (such as the NG-RAN). The process of selecting and / or changing the SENF in this embodiment includes the following steps 1 to 11:

[0410] Step 1. The terminal device and / or access network device and / or third-party device triggers a sensing service request;

[0411] Optionally, the sensing service request is triggered by at least one of the terminal device, the access network device, and the third device.

[0412] Optionally, the terminal device and / or access network device triggers a sensing service request, and the terminal device and / or access network device sends the sensing service request to the third device.

[0413] Optionally, the UE, NG-RAN, or AMF triggers a sensing service request.

[0414] Step 2. The terminal device sends a non-access stratum transmission message;

[0415] Optionally, after the terminal device triggers the sensing service request, it sends an event report message to the third device.

[0416] Optionally, the terminal device and the third device communicate by transmitting messages through NAS (Non-Access Layer).

[0417] Optionally, the event report message sent by the terminal device to the third device is carried via NAS transmission message.

[0418] Optionally, the NAS transmission message (AMF-UE inter-message) sent by the UE includes an event report message sent to the serving AMF.

[0419] Optionally, the event reporting message includes an identifier indicating the first device (i.e., the original SENF).

[0420] Step 3. The access network device sends an S1 transmission message;

[0421] Optionally, after the access network device triggers the sensing service request, it sends an event report message to the third device.

[0422] Optionally, the access network device and the third device communicate via S1 to transmit messages.

[0423] Optionally, the event report message sent by the access network device to the third device is carried through the NAS transmission message.

[0424] Optionally, the S1 transport message (AMF and gNB inter-message) sent by the NG-RAN includes an event report message sent to the serving AMF.

[0425] Optionally, the event reporting message includes an identifier indicating the first device (i.e., the original SENF).

[0426] Step 4. The third device sends the first information to the first device;

[0427] Optionally, the first information includes at least one of the following: an event report message, operator configuration and / or policy, and descriptive information related to the second device.

[0428] Optionally, the third device invokes the Namf_Communication_N1N2MessageNotify service operation to send the first message to the first device.

[0429] Optionally, the Namf_Communication_N1N2MessageNotify service operation includes event reporting messages received by a third device from a terminal device and / or an access network device.

[0430] Optionally, the AMF invokes the Namf_Communication_N1N2MessageNotify service operation to the original SENF. Optionally, this service operation includes the event reporting message received in step 2 or step 3.

[0431] Step 5. The first device determines the second device;

[0432] Optionally, the second device is determined by the first device (i.e., the original SENF), that is, how to select a suitable new SENF is determined by the first device.

[0433] Optionally, after receiving the event report message, the first device evaluates and determines whether it is suitable for or supports the current access network or serving cell's awareness based on the operator's configuration and / or policy, and / or determines whether the second device (i.e., the target SENF or the new SENF) is a more suitable SENF.

[0434] Optionally, if the first device evaluates and determines, based on operator configuration and / or policies, that the first device is unsuitable or unable to support the current access network or serving cell perception, then the first device determines that the SENF needs to be changed and selects or determines the second device, i.e., determines a more suitable new SENF.

[0435] Optionally, the first device selects a second device, i.e. a new SENF, for the current sensing operation based on at least one of the following: sensing service area (consisting of one or more TAs), operator configuration and / or policies, description information related to the second device, sensing client type, requested sensing service quality information, access type, RAT type, serving AN node, RAN configuration information, event report duration, event report indication, and network slice information.

[0436] Optionally, the descriptive information related to the second device includes at least one of the following: the second device's capabilities, load, energy consumption and efficiency, location, supported GAD shape, and the user plane connection that the requested terminal device has with a portion of the SENF.

[0437] Optionally, the first device may have the second device information locally configured, for example, obtained from previous NRF discovery or local configuration.

[0438] Optionally, the descriptive information related to the second device can be obtained through the local configuration of the first device.

[0439] Optionally, the description information related to the second device is registered in the fourth device, and the first device can query the fourth device to obtain the description information related to the second device.

[0440] Optionally, if the AMF does not indicate a new SENF in step 4, based on operator configuration and policies, the AMF may assess and determine that the original SENF is unsuitable or unable to support the awareness of the current access network or serving cell, and determine a more suitable target SENF.

[0441] Optionally, the NRF returns a set of SENF profiles via response messages based on the AMF's query request, and then selects the appropriate target SENF based on the SENF profiles.

[0442] Step 6. The first device sends the first content to the second device;

[0443] Optionally, after determining the second device, the first device sends the first content to the determined second device.

[0444] Optionally, the first device invokes the Nsenf_Sensing_SensingContextTransfer Request service operation to send the first content to the second device.

[0445] Optionally, the first device invokes the Nsenf_Sensing_SensingContextTransfer Request service operation to send the second device at least one of the following: periodic or event-triggered sensing service request information, sensing context, event report message, third device identifier, current status of the event report, and sensing-related information.

[0446] Optionally, the original SENF invokes the Nsenf_Sensing_SensingContextTransfer Request service operation to the target SENF to provide the current sensing context, including the event report message received in step 5.

[0447] Optionally, the Nsenf_Sensing_SensingContextTransfer Request service operation includes the AMF identifier and all information originally received by the original SENF from the AMF or from an earlier service SENF for periodic or triggered sensing requests according to this process.

[0448] Optionally, the Nsenf_Sensing_SensingContextTransfer Request service operation may also include the current status of the event reports (e.g., the number of event reports received so far and / or the duration of the event reports so far), and may also include perception-related information, such as previous perception estimates and / or timestamps of perception estimates (if available) or perception measurements.

[0449] Step 7. The second device sends the perception context transmission operation result to the first device;

[0450] Optionally, the first device receives the result of the perception context transmission operation sent by the second device.

[0451] Optionally, after receiving the perception context transmission operation result sent by the second device, the first device releases the resources related to the perception operation.

[0452] Optionally, the target SENF invokes the Nsenf_Sensing_SensingContextTransfer Response service operation to notify the original SENF of the result of the sensing context transfer operation. Then, the original SENF releases all resources from this process.

[0453] Step 8. The second device sends a service event report confirmation message to the third device;

[0454] Optionally, the second device invokes the Namf_Communication_N1N2MessageTransfer service operation to the third device to request a transmission service event report confirmation message.

[0455] Optionally, the second device sends an event report confirmation message to the third device.

[0456] Optionally, the event report confirmation message includes the identifier of the second device.

[0457] Optionally, the event report confirmation message is used to indicate the change of the current service SENF, that is, the second device confirms its agreement to the change of the current service SENF through the event report confirmation message.

[0458] Optionally, the event report confirmation message is used to indicate rejection of the change to the current service SENF, that is, the second device rejects the change to the current service SENF through the event report confirmation message.

[0459] Optionally, if the second device rejects the change of the current service SENF, the third device may reselect a new and appropriate SENF.

[0460] Optionally, the target SENF invokes the Namf_Communication_N1N2MessageTransfer service operation to the AMF to request the transmission of an event report acknowledgment message. Optionally, the event report acknowledgment message indicates a change in the SENF and includes a routing identifier indicating the target SENF.

[0461] Step 9. The third device forwards the event report confirmation message to the terminal device via the non-access stratum transmission message;

[0462] Optionally, if the second device agrees to the change of the current service SENF, the third device forwards the event report confirmation message from the second device to the terminal device.

[0463] Optionally, the third device forwards the event report confirmation message from the second device to the terminal device via NAS transmission message.

[0464] Optionally, the AMF forwards an event report confirmation message to the UE in the NAS transmission message.

[0465] Optionally, the AMF also notifies the target SENF of the delivery result of the event report confirmation message.

[0466] Step 10. The third device forwards the event report confirmation message to the access network device via S1 transmission message;

[0467] Optionally, if the second device agrees to the change of the current service SENF, the third device forwards the event report confirmation message from the second device to the access network device.

[0468] Optionally, the third device forwards the event report confirmation message from the second device to the access network device via S1 transmission message.

[0469] Optionally, after forwarding the event report confirmation message from the second device to the terminal device and / or the access network device, the third device sends the event report confirmation transmission result to the second device.

[0470] Optionally, the AMF forwards the event report confirmation message to the NG-RAN in the S1 transmission message.

[0471] Optionally, the AMF will also notify the target SENF of the delivery result of the event report confirmation message.

[0472] Step 11. The second device performs a sensing operation.

[0473] Optionally, if the event report indicates that a perception estimate is required, the second device performs the perception operation.

[0474] Optionally, the second device retains status information to support subsequent event reporting.

[0475] Optionally, if an event report indicates that perception estimation is required, the target SENF can perform perception estimation.

[0476] Through the technical solution of this embodiment, the first device sends the first content to the second device based on the first information, which can optimize the existing perception service process and support the service SENF change requirements.

[0477] Fourth embodiment

[0478] Referring to Figure 9, which is a flowchart illustrating the processing method of the fourth embodiment of this application, the processing method of this embodiment can be applied to a third device (such as an AMF), and includes step S1:

[0479] Step S1: The third device sends first information so that the first device sends first content to the second device based on the first information.

[0480] Optionally, the first device is the original SENF.

[0481] Optionally, the second device is the target SENF, that is, the second device is the modified SENF, or the new SENF.

[0482] Optionally, since the SENF has changed, the relevant information of the original SENF for sensing operations needs to be provided to the new SENF, that is, the first device needs to send the first content to the second device.

[0483] Optionally, the third device is an AMF.

[0484] Optionally, the first content includes at least one of the following: information related to periodic or event-triggered perception service requests, perception context, event report message, third device identifier, current status of the event report, and perception-related information.

[0485] Optionally, the current status of the event report includes the number of event reports received by the first device and / or the duration of the event reports.

[0486] Optionally, the perception-related information includes at least one of the following: a previous perception estimate of the first device, a timestamp of the perception estimate, and a perception measurement value.

[0487] Optionally, the first device sends the first content to the second device based on the first information.

[0488] Optionally, the first information is sent from the third device to the first device.

[0489] Optionally, the first information is sent from the third device to the first device after the third device receives the sensing service request.

[0490] Optionally, the sensing service request is triggered by at least one of the terminal device, access network device, and third device.

[0491] Optionally, the terminal device and / or access network device triggers a sensing service request, and the terminal device and / or access network device sends the sensing service request to the third device.

[0492] Optionally, the third device sends the first information to the first device according to the sensing service request.

[0493] Optionally, the first information includes at least one of the following: a first instruction, an event report message, operator configuration and / or policy, and descriptive information related to the second device.

[0494] Optionally, the event report message is sent by the terminal device and / or access network device to the third device.

[0495] Optionally, the terminal device and the third device communicate via NAS (Non-Access Layer) message transmission. Optionally, the event report message sent by the terminal device to the third device is carried via NAS message transmission.

[0496] Optionally, the access network device and the third device communicate via S1 transmission messages. Optionally, the event report message sent by the access network device to the third device is carried via NAS transmission messages.

[0497] Optionally, the event reporting message includes an identifier indicating the first device (i.e., the original SENF).

[0498] Optionally, the first instruction is used to instruct the first device that the third device has determined to use the new second device, that is, the third device has determined the new SENF.

[0499] Optionally, the descriptive information related to the second device includes at least one of the following: the second device's capabilities, load, energy consumption and efficiency, location, supported GAD shape, and the user plane connection that the requested terminal device has with a portion of the SENF.

[0500] Optionally, operator configuration and / or policies are used to evaluate and determine whether the first device (i.e., the original SENF) is suitable for or supports the current access network or serving cell perception, and / or to determine whether the second device (i.e., the target SENF or the new SENF) is a more suitable SENF.

[0501] Optionally, as a scenario, the second device is determined by the third device, that is, how to select the appropriate SENF is determined by the third device.

[0502] Optionally, the second device is determined by the third device based on the first information.

[0503] Optionally, the third device determines, based on the first information, that the first device is unsuitable for or unable to support the sensing of the current access network or serving cell.

[0504] Optionally, the third device determines, based on operator configuration and / or policies, that the first device is unsuitable for or unable to support sensing of the current access network or serving cell.

[0505] Optionally, the third device determines the second device based on the first information, i.e., selects a suitable SENF.

[0506] Optionally, the second device is determined by the third device based on the second information.

[0507] Optionally, the second information includes at least one of the following: sense service area, operator configuration and / or policy, description information related to the second device, sense client type, requested sense service quality information, access type, RAT type, service AN node, RAN configuration information, duration of event report, event report indication, and network slice information.

[0508] Optionally, the sensing service area includes at least one TA.

[0509] Optionally, the requested perceived quality of service information may include perceived accuracy and / or response time.

[0510] Optionally, the event reporting indication includes indicating a single event report or multiple event reports.

[0511] Optionally, after the terminal device and / or access network device triggers a sensing service request, it sends an event report message to the third device.

[0512] Optionally, the third device receives event report messages from the terminal device and / or access network device.

[0513] Optionally, after receiving the event report message, the third device evaluates and determines whether the first device (i.e., the original SENF) is suitable for or supports the current access network or serving cell's perception based on the operator's configuration and / or policy, and / or determines whether the second device (i.e., the target SENF or the new SENF) is a more suitable SENF.

[0514] Optionally, if the third device evaluates and determines, based on operator configuration and / or policies, that the first device is unsuitable or unable to support the current access network or serving cell perception, the third device determines that the SENF needs to be changed and selects or determines the second device, i.e., determines a more suitable new SENF.

[0515] Optionally, the third device determines the second device based on the descriptive information related to the second device.

[0516] Optionally, the third device may be locally configured with information about the second device.

[0517] Optionally, the descriptive information related to the second device can be obtained through the local configuration of the third device.

[0518] Optionally, the descriptive information related to the second device can be obtained by querying the fourth device through the third device.

[0519] Optionally, the descriptive information related to the second device is registered in the fourth device.

[0520] Optionally, the fourth device is an NRF.

[0521] Optionally, the third device determines the second device based on the second information.

[0522] Optionally, the third device selects a second device, i.e. a new SENF, for the current sensing operation based on at least one of the following: sensing service area (consisting of one or more TAs), operator configuration and / or policies, description information related to the second device, sensing client type, requested sensing service quality information, access type, RAT type, serving AN node, RAN configuration information, event report duration, event report indication, and network slice information.

[0523] Optionally, the third device invokes the Namf_Communication_N1N2MessageNotify service operation to send the first message to the first device.

[0524] Optionally, the Namf_Communication_N1N2MessageNotify service operation includes event reporting messages received by a third device from a terminal device and / or an access network device.

[0525] Optionally, if the third device determines to use the new SENF, it sends a first instruction in the first message to indicate to the first device that the third device has determined to use the new SENF.

[0526] Alternatively, as another scenario, the second device is determined by the first device, that is, how to select a suitable SENF is determined by the first device.

[0527] Optionally, the second device is determined by the first device based on the first information.

[0528] Optionally, the first device receives the first information.

[0529] Optionally, the first information does not contain a first instruction, or the first information does not indicate a second device to the first device, i.e., it does not indicate a new SENF.

[0530] Optionally, the first device determines, based on the first information, whether the first device is unsuitable or unable to support the perception of the currently accessed network or serving cell.

[0531] Optionally, if the first device determines based on the first information that the first device is not suitable for or cannot support the perception of the current access network or serving cell, the first device determines that a change operation is required and determines the changed second device, that is, determines a more suitable new SENF.

[0532] Optionally, the first device determines, based on operator configuration and / or policies, that the first device is unsuitable for or unable to support sensing of the current access network or serving cell.

[0533] Optionally, the second device is determined by the first device based on the second information.

[0534] Optionally, after receiving the first information, the first device determines the second device based on the second information.

[0535] Optionally, the descriptive information related to the second device can be obtained through local configuration of the first device or by querying the fourth device.

[0536] Optionally, after determining the second device, or after obtaining information about the second device according to the instructions of the third device, the first device sends the first content to the determined second device.

[0537] Optionally, the first device invokes the Nsenf_Sensing_SensingContextTransfer Request service operation to send the first content to the second device.

[0538] Optionally, the first device invokes the Nsenf_Sensing_SensingContextTransfer Request service operation to send the second device at least one of the following: periodic or event-triggered sensing service request information, sensing context, event report message, third device identifier, current status of the event report, and sensing-related information.

[0539] Optionally, the second device sends the result of the perception context transmission operation to the first device.

[0540] Optionally, the first device receives the result of the perception context transmission operation sent by the second device.

[0541] Optionally, after receiving the perception context transmission operation result sent by the second device, the first device releases the resources related to the perception operation.

[0542] Optionally, the second device invokes the Namf_Communication_N1N2MessageTransfer service operation to the third device to request a transmission service event report confirmation message.

[0543] Optionally, the second device sends an event report confirmation message to the third device.

[0544] Optionally, the event report confirmation message includes the identifier of the second device.

[0545] Optionally, the event report confirmation message is used to indicate the change of the current service SENF, that is, the second device confirms its agreement to the change of the current service SENF through the event report confirmation message.

[0546] Optionally, the event report confirmation message is used to indicate rejection of the change to the current service SENF, that is, the second device rejects the change to the current service SENF through the event report confirmation message.

[0547] Optionally, if the second device rejects the change of the current service SENF, the third device may reselect a new and appropriate SENF.

[0548] Optionally, if the second device agrees to the change of the current service SENF, the third device forwards the event report confirmation message from the second device to the terminal device and / or access network device.

[0549] Optionally, the third device forwards the event report confirmation message from the second device to the terminal device via NAS transmission message.

[0550] Optionally, the third device forwards the event report confirmation message from the second device to the access network device via S1 transmission message.

[0551] Optionally, after forwarding the event report confirmation message from the second device to the terminal device and / or the access network device, the third device sends the event report confirmation transmission result to the second device.

[0552] Optionally, if the event report indicates that perception estimation is required, the second device performs the perception operation.

[0553] Optionally, the second device retains status information to support subsequent event reporting.

[0554] Through the technical solution of this embodiment, the third device sends first information, so that the first device sends first content to the second device based on the first information. This can optimize the existing perception service process and support the service SENF change requirements.

[0555] Fifth embodiment

[0556] Referring to Figure 10, which is a flowchart illustrating the processing method of the fifth embodiment of this application, the processing method of this embodiment can be applied to a second device (such as SENF), including step S3:

[0557] Step S3: The second device receives the first content, which is sent by the first device based on the first information.

[0558] Optionally, the first device is the original SENF.

[0559] Optionally, the second device is the target SENF, that is, the second device is the modified SENF, or the new SENF.

[0560] Optionally, since the SENF has changed, the relevant information of the original SENF for sensing operations needs to be provided to the new SENF, that is, the first device needs to send the first content to the second device.

[0561] Optionally, the first content includes at least one of the following: information related to periodic or event-triggered perception service requests, perception context, event report message, third device identifier, current status of the event report, and perception-related information.

[0562] Optionally, the current status of the event report includes the number of event reports received by the first device and / or the duration of the event reports.

[0563] Optionally, the perception-related information includes at least one of the following: a previous perception estimate of the first device, a timestamp of the perception estimate, and a perception measurement value.

[0564] Optionally, the first device sends the first content to the second device based on the first information.

[0565] Optionally, the first information is sent from the third device to the first device.

[0566] Optionally, the third device is an AMF.

[0567] Optionally, the first information is sent from the third device to the first device after the third device receives the sensing service request.

[0568] Optionally, the sensing service request is triggered by at least one of the terminal device, access network device, and third device.

[0569] Optionally, the terminal device and / or access network device triggers a sensing service request, and the terminal device and / or access network device sends the sensing service request to the third device.

[0570] Optionally, the third device sends the first information to the first device according to the sensing service request.

[0571] Optionally, the first information includes at least one of the following: a first instruction, an event report message, operator configuration and / or policy, and descriptive information related to the second device.

[0572] Optionally, the event report message is sent by the terminal device and / or access network device to the third device.

[0573] Optionally, the terminal device and the third device communicate via NAS (Non-Access Layer) message transmission. Optionally, the event report message sent by the terminal device to the third device is carried via NAS message transmission.

[0574] Optionally, the access network device and the third device communicate via S1 transmission messages. Optionally, the event report message sent by the access network device to the third device is carried via NAS transmission messages.

[0575] Optionally, the event reporting message includes an identifier indicating the first device (i.e., the original SENF).

[0576] Optionally, the first instruction is used to instruct the first device that the third device has determined to use the new second device, that is, the third device has determined the new SENF.

[0577] Optionally, the descriptive information related to the second device includes at least one of the following: the second device's capabilities, load, energy consumption and efficiency, location, supported GAD shape, and the user plane connection that the requested terminal device has with a portion of the SENF.

[0578] Optionally, operator configuration and / or policies are used to evaluate and determine whether the first device (i.e., the original SENF) is suitable for or supports the current access network or serving cell perception, and / or to determine whether the second device (i.e., the target SENF or the new SENF) is a more suitable SENF.

[0579] Optionally, as a scenario, the second device is determined by the third device, that is, how to select the appropriate SENF is determined by the third device.

[0580] Optionally, the second device is determined by the third device based on the first information.

[0581] Optionally, the third device determines, based on the first information, that the first device is unsuitable for or unable to support the sensing of the current access network or serving cell.

[0582] Optionally, the third device determines, based on operator configuration and / or policies, that the first device is unsuitable for or unable to support sensing of the current access network or serving cell.

[0583] Optionally, the third device determines the second device based on the first information, i.e., selects a suitable SENF.

[0584] Optionally, the second device is determined by the third device based on the second information.

[0585] Optionally, the second information includes at least one of the following: sense service area, operator configuration and / or policy, description information related to the second device, sense client type, requested sense service quality information, access type, RAT type, service AN node, RAN configuration information, duration of event report, event report indication, and network slice information.

[0586] Optionally, the sensing service area includes at least one TA.

[0587] Optionally, the requested perceived quality of service information may include perceived accuracy and / or response time.

[0588] Optionally, the event reporting indication includes indicating a single event report or multiple event reports.

[0589] Optionally, after the terminal device and / or access network device triggers a sensing service request, it sends an event report message to the third device.

[0590] Optionally, the third device receives event report messages from the terminal device and / or access network device.

[0591] Optionally, after receiving the event report message, the third device evaluates and determines whether the first device (i.e., the original SENF) is suitable for or supports the current access network or serving cell's perception based on the operator's configuration and / or policy, and / or determines whether the second device (i.e., the target SENF or the new SENF) is a more suitable SENF.

[0592] Optionally, if the third device evaluates and determines, based on operator configuration and / or policies, that the first device is unsuitable or unable to support the current access network or serving cell perception, the third device determines that the SENF needs to be changed and selects or determines the second device, i.e., determines a more suitable new SENF.

[0593] Optionally, the third device determines the second device based on the descriptive information related to the second device.

[0594] Optionally, the third device may be locally configured with information about the second device.

[0595] Optionally, the descriptive information related to the second device can be obtained through the local configuration of the third device.

[0596] Optionally, the descriptive information related to the second device can be obtained by querying the fourth device through the third device.

[0597] Optionally, the descriptive information related to the second device is registered in the fourth device.

[0598] Optionally, the fourth device is an NRF.

[0599] Optionally, the third device determines the second device based on the second information.

[0600] Optionally, the third device selects a second device, i.e. a new SENF, for the current sensing operation based on at least one of the following: sensing service area (consisting of one or more TAs), operator configuration and / or policies, description information related to the second device, sensing client type, requested sensing service quality information, access type, RAT type, serving AN node, RAN configuration information, event report duration, event report indication, and network slice information.

[0601] Optionally, the third device invokes the Namf_Communication_N1N2MessageNotify service operation to send the first message to the first device.

[0602] Optionally, the Namf_Communication_N1N2MessageNotify service operation includes event reporting messages received by a third device from a terminal device and / or an access network device.

[0603] Optionally, if the third device determines to use the new SENF, it sends a first instruction in the first message to indicate to the first device that the third device has determined to use the new SENF.

[0604] Alternatively, as another scenario, the second device is determined by the first device, that is, how to select a suitable SENF is determined by the first device.

[0605] Optionally, the second device is determined by the first device based on the first information.

[0606] Optionally, the first device receives the first information.

[0607] Optionally, the first information does not contain a first instruction, or the first information does not indicate a second device to the first device, i.e., it does not indicate a new SENF.

[0608] Optionally, the first device determines, based on the first information, whether the first device is unsuitable or unable to support the perception of the currently accessed network or serving cell.

[0609] Optionally, if the first device determines based on the first information that the first device is not suitable for or cannot support the perception of the current access network or serving cell, the first device determines that a change operation is required and determines the changed second device, that is, determines a more suitable new SENF.

[0610] Optionally, the first device determines, based on operator configuration and / or policies, that the first device is unsuitable for or unable to support sensing of the current access network or serving cell.

[0611] Optionally, the second device is determined by the first device based on the second information.

[0612] Optionally, after receiving the first information, the first device determines the second device based on the second information.

[0613] Optionally, the descriptive information related to the second device can be obtained through local configuration of the first device or by querying the fourth device.

[0614] Optionally, after determining the second device, or after obtaining information about the second device according to the instructions of the third device, the first device sends the first content to the determined second device.

[0615] Optionally, the first device invokes the Nsenf_Sensing_SensingContextTransfer Request service operation to send the first content to the second device.

[0616] Optionally, the first device invokes the Nsenf_Sensing_SensingContextTransfer Request service operation to send the second device at least one of the following: periodic or event-triggered sensing service request information, sensing context, event report message, third device identifier, current status of the event report, and sensing-related information.

[0617] Optionally, the second device sends the result of the perception context transmission operation to the first device.

[0618] Optionally, the first device receives the result of the perception context transmission operation sent by the second device.

[0619] Optionally, after receiving the perception context transmission operation result sent by the second device, the first device releases the resources related to the perception operation.

[0620] Optionally, the second device invokes the Namf_Communication_N1N2MessageTransfer service operation to the third device to request a transmission service event report confirmation message.

[0621] Optionally, the second device sends an event report confirmation message to the third device.

[0622] Optionally, the event report confirmation message includes the identifier of the second device.

[0623] Optionally, the event report confirmation message is used to indicate the change of the current service SENF, that is, the second device confirms its agreement to the change of the current service SENF through the event report confirmation message.

[0624] Optionally, the event report confirmation message is used to indicate rejection of the change to the current service SENF, that is, the second device rejects the change to the current service SENF through the event report confirmation message.

[0625] Optionally, if the second device rejects the change of the current service SENF, the third device may reselect a new and appropriate SENF.

[0626] Optionally, if the second device agrees to the change of the current service SENF, the third device forwards the event report confirmation message from the second device to the terminal device and / or access network device.

[0627] Optionally, the third device forwards the event report confirmation message from the second device to the terminal device via NAS transmission message.

[0628] Optionally, the third device forwards the event report confirmation message from the second device to the access network device via S1 transmission message.

[0629] Optionally, after forwarding the event report confirmation message from the second device to the terminal device and / or the access network device, the third device sends the event report confirmation transmission result to the second device.

[0630] Optionally, if the event report indicates that perception estimation is required, the second device performs the perception operation.

[0631] Optionally, the second device retains status information to support subsequent event reporting.

[0632] Through the technical solution of this embodiment, the second device receives the first content, which is sent by the first device based on the first information. This can optimize the existing perception service process to support and meet the service SENF change requirements.

[0633] Sixth Embodiment

[0634] Referring to Figure 11, which is a schematic diagram of the interaction flow of the first device, the second device, and the third device according to the sixth embodiment of the processing method, the sixth embodiment of this application proposes a processing method including steps S1, S2, and S3:

[0635] Step S1: The third device sends first information, so that the first device sends first content to the second device based on the first information;

[0636] Step S2: The first device sends the first content to the second device based on the first information;

[0637] Step S3: The second device receives the first content, which is sent by the first device based on the first information.

[0638] Optionally, the first device is the original SENF.

[0639] Optionally, the second device is the target SENF, that is, the second device is the modified SENF, or the new SENF.

[0640] Optionally, since the SENF has changed, the relevant information of the original SENF for sensing operations needs to be provided to the new SENF, that is, the first device needs to send the first content to the second device.

[0641] Optionally, the third device is an AMF.

[0642] Optionally, the first content includes at least one of the following: information related to periodic or event-triggered perception service requests, perception context, event report message, third device identifier, current status of the event report, and perception-related information.

[0643] Optionally, the current status of the event report includes the number of event reports received by the first device and / or the duration of the event reports.

[0644] Optionally, the perception-related information includes at least one of the following: a previous perception estimate of the first device, a timestamp of the perception estimate, and a perception measurement value.

[0645] Optionally, the first device sends the first content to the second device based on the first information.

[0646] Optionally, the first information is sent from the third device to the first device.

[0647] Optionally, the first information is sent from the third device to the first device after the third device receives the sensing service request.

[0648] Optionally, the sensing service request is triggered by at least one of the terminal device, access network device, and third device.

[0649] Optionally, the terminal device and / or access network device triggers a sensing service request, and the terminal device and / or access network device sends the sensing service request to the third device.

[0650] Optionally, the third device sends the first information to the first device according to the sensing service request.

[0651] Optionally, the first information includes at least one of the following: a first instruction, an event report message, operator configuration and / or policy, and descriptive information related to the second device.

[0652] Optionally, the event report message is sent by the terminal device and / or access network device to the third device.

[0653] Optionally, the terminal device and the third device communicate via NAS (Non-Access Layer) message transmission. Optionally, the event report message sent by the terminal device to the third device is carried via NAS message transmission.

[0654] Optionally, the access network device and the third device communicate via S1 transmission messages. Optionally, the event report message sent by the access network device to the third device is carried via NAS transmission messages.

[0655] Optionally, the event reporting message includes an identifier indicating the first device (i.e., the original SENF).

[0656] Optionally, the first instruction is used to instruct the first device that the third device has determined to use the new second device, that is, the third device has determined the new SENF.

[0657] Optionally, the descriptive information related to the second device includes at least one of the following: the second device's capabilities, load, energy consumption and efficiency, location, supported GAD shape, and the user plane connection that the requested terminal device has with a portion of the SENF.

[0658] Optionally, operator configuration and / or policies are used to evaluate and determine whether the first device (i.e., the original SENF) is suitable for or supports the current access network or serving cell perception, and / or to determine whether the second device (i.e., the target SENF or the new SENF) is a more suitable SENF.

[0659] Optionally, as a scenario, the second device is determined by the third device, that is, how to select the appropriate SENF is determined by the third device.

[0660] Optionally, the second device is determined by the third device based on the first information.

[0661] Optionally, the third device determines, based on the first information, that the first device is unsuitable for or unable to support the sensing of the current access network or serving cell.

[0662] Optionally, the third device determines, based on operator configuration and / or policies, that the first device is unsuitable for or unable to support sensing of the current access network or serving cell.

[0663] Optionally, the third device determines the second device based on the first information, i.e., selects a suitable SENF.

[0664] Optionally, the second device is determined by the third device based on the second information.

[0665] Optionally, the second information includes at least one of the following: sense service area, operator configuration and / or policy, description information related to the second device, sense client type, requested sense service quality information, access type, RAT type, service AN node, RAN configuration information, duration of event report, event report indication, and network slice information.

[0666] Optionally, the sensing service area includes at least one TA.

[0667] Optionally, the requested perceived quality of service information may include perceived accuracy and / or response time.

[0668] Optionally, the event reporting indication includes indicating a single event report or multiple event reports.

[0669] Optionally, after the terminal device and / or access network device triggers a sensing service request, it sends an event report message to the third device.

[0670] Optionally, the third device receives event report messages from the terminal device and / or access network device.

[0671] Optionally, after receiving the event report message, the third device evaluates and determines whether the first device (i.e., the original SENF) is suitable for or supports the current access network or serving cell's perception based on the operator's configuration and / or policy, and / or determines whether the second device (i.e., the target SENF or the new SENF) is a more suitable SENF.

[0672] Optionally, if the third device evaluates and determines, based on operator configuration and / or policies, that the first device is unsuitable or unable to support the current access network or serving cell perception, the third device determines that the SENF needs to be changed and selects or determines the second device, i.e., determines a more suitable new SENF.

[0673] Optionally, the third device determines the second device based on the descriptive information related to the second device.

[0674] Optionally, the third device may be locally configured with information about the second device.

[0675] Optionally, the descriptive information related to the second device can be obtained through the local configuration of the third device.

[0676] Optionally, the descriptive information related to the second device can be obtained by querying the fourth device through the third device.

[0677] Optionally, the descriptive information related to the second device is registered in the fourth device.

[0678] Optionally, the fourth device is an NRF.

[0679] Optionally, the third device determines the second device based on the second information.

[0680] Optionally, the third device selects a second device, i.e. a new SENF, for the current sensing operation based on at least one of the following: sensing service area (consisting of one or more TAs), operator configuration and / or policies, description information related to the second device, sensing client type, requested sensing service quality information, access type, RAT type, serving AN node, RAN configuration information, event report duration, event report indication, and network slice information.

[0681] Optionally, the third device invokes the Namf_Communication_N1N2MessageNotify service operation to send the first message to the first device.

[0682] Optionally, the Namf_Communication_N1N2MessageNotify service operation includes event reporting messages received by a third device from a terminal device and / or an access network device.

[0683] Optionally, if the third device determines to use the new SENF, it sends a first instruction in the first message to indicate to the first device that the third device has determined to use the new SENF.

[0684] Alternatively, as another scenario, the second device is determined by the first device, that is, how to select a suitable SENF is determined by the first device.

[0685] Optionally, the second device is determined by the first device based on the first information.

[0686] Optionally, the first device receives the first information.

[0687] Optionally, the first information does not contain a first instruction, or the first information does not indicate a second device to the first device, i.e., it does not indicate a new SENF.

[0688] Optionally, the first device determines, based on the first information, whether the first device is unsuitable or unable to support the perception of the currently accessed network or serving cell.

[0689] Optionally, if the first device determines based on the first information that the first device is not suitable for or cannot support the perception of the current access network or serving cell, the first device determines that a change operation is required and determines the changed second device, that is, determines a more suitable new SENF.

[0690] Optionally, the first device determines, based on operator configuration and / or policies, that the first device is unsuitable for or unable to support sensing of the current access network or serving cell.

[0691] Optionally, the second device is determined by the first device based on the second information.

[0692] Optionally, after receiving the first information, the first device determines the second device based on the second information.

[0693] Optionally, the descriptive information related to the second device can be obtained through local configuration of the first device or by querying the fourth device.

[0694] Optionally, after determining the second device, or after obtaining information about the second device according to the instructions of the third device, the first device sends the first content to the determined second device.

[0695] Optionally, the first device invokes the Nsenf_Sensing_SensingContextTransfer Request service operation to send the first content to the second device.

[0696] Optionally, the first device invokes the Nsenf_Sensing_SensingContextTransfer Request service operation to send the second device at least one of the following: periodic or event-triggered sensing service request information, sensing context, event report message, third device identifier, current status of the event report, and sensing-related information.

[0697] Optionally, the second device sends the result of the perception context transmission operation to the first device.

[0698] Optionally, the first device receives the result of the perception context transmission operation sent by the second device.

[0699] Optionally, after receiving the perception context transmission operation result sent by the second device, the first device releases the resources related to the perception operation.

[0700] Optionally, the second device invokes the Namf_Communication_N1N2MessageTransfer service operation to the third device to request a transmission service event report confirmation message.

[0701] Optionally, the second device sends an event report confirmation message to the third device.

[0702] Optionally, the event report confirmation message includes the identifier of the second device.

[0703] Optionally, the event report confirmation message is used to indicate the change of the current service SENF, that is, the second device confirms its agreement to the change of the current service SENF through the event report confirmation message.

[0704] Optionally, the event report confirmation message is used to indicate rejection of the change to the current service SENF, that is, the second device rejects the change to the current service SENF through the event report confirmation message.

[0705] Optionally, if the second device rejects the change of the current service SENF, the third device may reselect a new and appropriate SENF.

[0706] Optionally, if the second device agrees to the change of the current service SENF, the third device forwards the event report confirmation message from the second device to the terminal device and / or access network device.

[0707] Optionally, the third device forwards the event report confirmation message from the second device to the terminal device via NAS transmission message.

[0708] Optionally, the third device forwards the event report confirmation message from the second device to the access network device via S1 transmission message.

[0709] Optionally, after forwarding the event report confirmation message from the second device to the terminal device and / or the access network device, the third device sends the event report confirmation transmission result to the second device.

[0710] Optionally, if the event report indicates that perception estimation is required, the second device performs the perception operation.

[0711] Optionally, the second device retains status information to support subsequent event reporting.

[0712] Through the technical solution of this embodiment, the third device sends first information, and the first device sends first content to the second device based on the first information; the second device receives the first content, which can optimize the existing perception service process to support and meet the service SENF change requirements.

[0713] Seventh Embodiment

[0714] Please refer to Figure 12, which is a schematic diagram of the structure of the processing device provided in the embodiment of this application. This device can be mounted on or is the first device (such as SENF) in the above method embodiment. The processing device shown in Figure 12 can be used to perform some or all of the functions in the method embodiment described in the above embodiment. As shown in Figure 12, the processing device 150 includes:

[0715] The first sending module 1501 is used to send the first content to the second device based on the first information.

[0716] Optionally, the processing apparatus further includes at least one of the following:

[0717] The first information includes at least one of the following: a first instruction, an event report message, operator configuration and / or policy, and descriptive information related to the second device;

[0718] The first message is sent by the third device;

[0719] The first information is sent by the third device after receiving the sensing service request;

[0720] The first content includes at least one of the following: information related to periodic or event-triggered perception service requests, perception context, event report message, third device identifier, current status of event report, and perception-related information;

[0721] The second device is determined by the third device;

[0722] The second device is determined by the first device.

[0723] Optionally, the processing apparatus further includes at least one of the following:

[0724] Sensing service requests are triggered by terminal devices and / or access network devices;

[0725] The third device determines, based on the first information, that the first device is unsuitable for or unable to support the sensing of the current access network or serving cell.

[0726] The second device is determined by the third device based on the first information;

[0727] The second device is determined by the third device based on the second information;

[0728] Receive the first message;

[0729] Based on the first information, it is determined that the first device is not suitable for or cannot support the sensing of the current access network or serving cell;

[0730] The second device is determined based on the first information;

[0731] The second device is determined based on the second information;

[0732] Receive the result of the perception context transmission operation sent by the second device;

[0733] Release resources related to perception operations;

[0734] The second device sends an event report confirmation message to the third device;

[0735] The third device forwards the event report confirmation message from the second device to the terminal device and / or access network device;

[0736] The second device performs the sensing operation.

[0737] Optionally, the processing apparatus further includes at least one of the following:

[0738] The description information related to the second device is obtained through local configuration of the first device or by querying the fourth device.

[0739] The description information related to the second device is obtained through the local configuration of the third device or by the first device querying the fourth device.

[0740] The current status of the event reports includes the number of event reports received and / or the duration of the event reports;

[0741] The perception-related information includes at least one of the following: previous perception estimates, timestamps of perception estimates, and perception measurements;

[0742] The second information includes at least one of the following: sensing service area, operator configuration and / or policy, description information related to the second device, sensing client type, requested sensing service quality information, access type, RAT type, serving AN node, RAN configuration information, duration of event report, event report indication, and network slice information.

[0743] The event report message includes an identifier indicating the first device;

[0744] The incident report confirmation message includes the identifier of the second device;

[0745] Event report confirmation messages are used to indicate changes to the current service's SENF;

[0746] The event report confirmation message is used to indicate that changes to the current service's SENF should be rejected;

[0747] The first device is the original SENF;

[0748] The second device is the target SENF;

[0749] The third device is AMF:

[0750] The fourth device is NRF.

[0751] Optionally, the processing apparatus further includes at least one of the following:

[0752] The descriptive information related to the second device includes at least one of the following: the second device's capabilities, load, energy consumption and efficiency, location, supported GAD shape, and the user plane connection that the requested terminal device has with a portion of the SENF.

[0753] The requested perceived service quality information includes perception accuracy and / or response time;

[0754] The sensing service area includes at least one TA;

[0755] Incident reporting instructions include instructions for single incident reporting or multiple incident reporting;

[0756] The descriptive information related to the second device is registered in the fourth device.

[0757] The processing device provided in this application embodiment is similar in implementation principle and beneficial effect to the technical solution shown in the corresponding method embodiment above, and will not be described again here.

[0758] Eighth embodiment

[0759] Please refer to Figure 13, which is a second schematic diagram of the structure of the processing device provided in the embodiment of this application. This device can be mounted on or is the third device (such as AMF) in the above method embodiment. The processing device shown in Figure 13 can be used to perform some or all of the functions in the method embodiment described in the above embodiment. As shown in Figure 13, the processing device 160 includes:

[0760] The second sending module 1601 is used to send first information so that the first device sends first content to the second device based on the first information.

[0761] Optionally, the processing apparatus further includes at least one of the following:

[0762] The first information includes at least one of the following: a first instruction, an event report message, operator configuration and / or policy, and descriptive information related to the second device;

[0763] The first message is sent based on a perception service request;

[0764] The first content includes at least one of the following: information related to periodic or event-triggered perception service requests, perception context, event report message, third device identifier, current status of event report, and perception-related information;

[0765] The second device is determined by the third device;

[0766] The second device is determined by the first device.

[0767] Optionally, the processing apparatus further includes at least one of the following:

[0768] Sensing service requests are triggered by terminal devices and / or access network devices;

[0769] Receive sensing service requests;

[0770] Based on the first information, it is determined that the first device is not suitable for or cannot support the sensing of the current access network or serving cell;

[0771] The first device determines, based on the first information, that the first device is not suitable for or cannot support the sensing of the current access network or serving cell.

[0772] The second device is determined by the first device or the third device based on the first information;

[0773] The second device is determined by the first device or the third device based on the second information;

[0774] The first device receives the result of the perception context transmission operation sent by the second device;

[0775] The first device releases resources related to sensing operations;

[0776] Receive the event report confirmation message sent by the second device;

[0777] Send an event report confirmation message from the second device to the terminal device and / or access network device;

[0778] The second device performs the sensing operation.

[0779] Optionally, the processing apparatus further includes at least one of the following:

[0780] The description information related to the second device is obtained through local configuration on the third device or by querying the fourth device.

[0781] The description information related to the second device is obtained through the local configuration of the first device or by the first device querying the fourth device.

[0782] The current status of the event reports includes the number of event reports received and / or the duration of the event reports;

[0783] The perception-related information includes at least one of the following: previous perception estimates, timestamps of perception estimates, and perception measurements;

[0784] The second information includes at least one of the following: sensing service area, operator configuration and / or policy, description information related to the second device, sensing client type, requested sensing service quality information, access type, RAT type, serving AN node, RAN configuration information, duration of event report, event report indication, and network slice information.

[0785] The event report message includes an identifier indicating the first device;

[0786] The incident report confirmation message includes the identifier of the second device;

[0787] Event report confirmation messages are used to indicate changes to the current service's SENF;

[0788] The event report confirmation message is used to indicate that changes to the current service's SENF should be rejected;

[0789] The first device is the original SENF;

[0790] The second device is the target SENF;

[0791] The third device is AMF:

[0792] The fourth device is NRF.

[0793] Optionally, the processing apparatus further includes at least one of the following:

[0794] The descriptive information related to the second device includes at least one of the following: the second device's capabilities, load, energy consumption and efficiency, location, supported GAD shape, and the user plane connection that the requested terminal device has with a portion of the SENF.

[0795] The requested perceived service quality information includes perception accuracy and / or response time;

[0796] The sensing service area includes at least one TA;

[0797] Incident reporting instructions include instructions for single incident reporting or multiple incident reporting;

[0798] The descriptive information related to the second device is registered in the fourth device.

[0799] The processing device provided in this application embodiment is similar in implementation principle and beneficial effect to the technical solution shown in the corresponding method embodiment above, and will not be described again here.

[0800] Ninth Embodiment

[0801] Please refer to Figure 14, which is a schematic diagram of the structure of the processing device provided in the embodiment of this application. This device can be mounted on or is the second device (such as SENF) in the above method embodiment. The processing device shown in Figure 14 can be used to perform some or all of the functions in the method embodiment described above. As shown in Figure 14, the device 170 includes:

[0802] The receiving module 1701 is used to receive first content, which is sent by the first device based on first information.

[0803] The first information includes at least one of the following: a first instruction, an event report message, operator configuration and / or policy, and descriptive information related to the second device;

[0804] The first information is sent from the third device to the first device;

[0805] The first content includes at least one of the following: information related to periodic or event-triggered perception service requests, perception context, event report message, third device identifier, current status of event report, and perception-related information;

[0806] The second device is determined by the third device;

[0807] The second device is determined by the first device.

[0808] Optionally, the processing apparatus further includes at least one of the following:

[0809] The first information is sent from the third device to the first device after receiving the sensing service request;

[0810] Sensing service requests are triggered by terminal devices and / or access network devices;

[0811] The third device determines, based on the first information, that the first device is unsuitable for or unable to support the sensing of the current access network or serving cell.

[0812] The second device is determined by the first device or the third device based on the first information;

[0813] The second device is determined by the first device or the third device based on the second information;

[0814] The first device determines, based on the first information, that the first device is not suitable for or cannot support the sensing of the current access network or serving cell.

[0815] Send the perception context transmission operation result to the first device;

[0816] The first device releases resources related to sensing operations;

[0817] Send an event report confirmation message to the third device;

[0818] The third device forwards the event report confirmation message from the second device to the terminal device and / or access network device;

[0819] Perform perception operations.

[0820] Optionally, the processing apparatus further includes at least one of the following:

[0821] The description information related to the second device is obtained through the local configuration of the first device or by the first device querying the fourth device.

[0822] The description information related to the second device is obtained through the local configuration of the third device or by the third device querying the fourth device.

[0823] The current status of the event reports includes the number of event reports received and / or the duration of the event reports;

[0824] The perception-related information includes at least one of the following: previous perception estimates, timestamps of perception estimates, and perception measurements;

[0825] The second information includes at least one of the following: sensing service area, operator configuration and / or policy, description information related to the second device, sensing client type, requested sensing service quality information, access type, RAT type, serving AN node, RAN configuration information, duration of event report, event report indication, and network slice information.

[0826] The event report message includes an identifier indicating the first device;

[0827] The incident report confirmation message includes the identifier of the second device;

[0828] Event report confirmation messages are used to indicate changes to the current service's SENF;

[0829] The event report confirmation message is used to indicate that changes to the current service's SENF should be rejected;

[0830] The first device is the original SENF;

[0831] The second device is the target SENF;

[0832] The third device is AMF:

[0833] The fourth device is NRF.

[0834] Optionally, the processing apparatus further includes at least one of the following:

[0835] The descriptive information related to the second device includes at least one of the following: the second device's capabilities, load, energy consumption and efficiency, location, supported GAD shape, and the user plane connection that the requested terminal device has with a portion of the SENF.

[0836] The requested perceived service quality information includes perception accuracy and / or response time;

[0837] The sensing service area includes at least one TA;

[0838] Incident reporting instructions include instructions for single incident reporting or multiple incident reporting;

[0839] The descriptive information related to the second device is registered in the fourth device.

[0840] The processing device provided in this application embodiment is similar in implementation principle and beneficial effect to the technical solution shown in the corresponding method embodiment above, and will not be described again here.

[0841] Referring to Figure 15, which is a schematic diagram of the structure of a communication device provided in an embodiment of this application, the communication device 180 described in this embodiment may be a first device (or a component that can be used in the first device), a second device (or a component that can be used in the second device), or a third device (or a component that can be used in the third device) mentioned in the foregoing method embodiments. The communication device 180 can be used to implement the methods described in the above method embodiments corresponding to the first device, the second device, or the third device, as detailed in the descriptions in the above method embodiments.

[0842] The communication device 180 may include one or more processors 1801, which may also be referred to as processing units, and can perform certain control or processing functions. The processor 1801 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device, execute software programs, and process data from the software programs.

[0843] Optionally, the processor 1801 may also store instructions 1803 or data (e.g., intermediate data). Optionally, instructions 1803 may be executed by the processor 1801 to cause the communication device 180 to perform the method described in the above method embodiments corresponding to the first device, the second device, or the third device.

[0844] Optionally, the communication device 180 may include a circuit that can perform the functions of sending, receiving, or communicating in the foregoing method embodiments.

[0845] Optionally, the communication device 180 may include one or more memories 1802, which may store instructions 1804 that can be executed on the processor 1801 to cause the communication device 180 to perform the methods described in the above method embodiments.

[0846] Alternatively, the memory 1802 may also store data. The processor 1801 and the memory 1802 can be configured separately or integrated together.

[0847] Optionally, the communication device 180 may further include a transceiver 1805 and / or an antenna 1806. The processor 1801, which may be referred to as a processing unit, controls the communication device 180 (the first device, the second device, or the third device). The transceiver 1805, which may be referred to as a transceiver unit, transceiver, transceiver circuit, or transceiver, is used to implement the transmission and reception functions of the communication device 180.

[0848] Optionally, if the communication device 180 is used to implement the operation corresponding to the first device in the above embodiments, for example, the transceiver 1805 may receive the first information; and / or the processor 1801 may send the first content to the second device based on the first information.

[0849] Optionally, the specific implementation process of the processor 1801 and transceiver 1805 can be found in the relevant descriptions of the above embodiments, and will not be repeated here.

[0850] Optionally, if the communication device 180 is used to implement the operation corresponding to the third device in the above embodiments, for example, the transceiver 1805 can send the first information.

[0851] Optionally, the specific implementation process of the processor 1801 and transceiver 1805 can be found in the relevant descriptions of the above embodiments, and will not be repeated here.

[0852] The processor 1801 and transceiver 1805 described in this application can be implemented on ICs (Integrated Circuits), analog integrated circuits, RFICs (Radio Frequency Integrated Circuits), mixed-signal integrated circuits, ASICs (Application Specific Integrated Circuits), PCBs (Printed Circuit Boards), electronic devices, etc. The processor 1801 and transceiver 1805 can also be manufactured using various integrated circuit process technologies, such as CMOS (Complementary Metal Oxide Semiconductor), NMOS (N-Metal-Oxide-Semiconductor), PMOS (Positive channel Metal Oxide Semiconductor), BJT (Bipolar Junction Transistor), Bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0853] In this application, the communication device can be a first device, a second device (such as SENF), or a third device (such as AMF), depending on the context. Furthermore, the terminal device can be implemented in various forms. For example, the terminal devices described in this application can include mobile terminals such as mobile phones, tablets, laptops, handheld computers, personal digital assistants (PDAs), portable media players (PMPs), navigation devices, wearable devices, smart bracelets, pedometers, etc., as well as fixed terminal devices such as digital TVs and desktop computers.

[0854] Although the communication device is described above using a first device, a second device, or a third device as examples, the scope of the communication device described in this application is not limited to the first device, the second device, or the third device described above, and the structure of the communication device is not limited to FIG. 15. The communication device can be a standalone device or can be part of a larger device.

[0855] This application also provides a communication system, including: a first device or a second device as described in any of the above embodiments; and / or, a third device as described in any of the above embodiments.

[0856] This application also provides a communication device, including a memory and a processor. The memory stores a processing program, and when the processing program is executed by the processor, it implements the steps of the processing method in any of the above embodiments.

[0857] The communication device in this application may be a first device or a second device (such as SENF), a third device (such as AMF), or a chip (such as SOC or a baseband chip with communication function, etc.). The specific meaning needs to be clarified according to the context.

[0858] This application also provides a computer-readable storage medium storing a processing program, which, when executed by a processor, implements the steps of the processing method in any of the above embodiments.

[0859] In the embodiments of the communication device and storage medium provided in this application, all the technical features of any of the above-described processing method embodiments may be included. The extended and explained contents of the specification are basically the same as the embodiments of the above methods, and will not be repeated here.

[0860] This application also provides a computer program product, which includes computer program code. When the computer program code is run on a computer, it causes the computer to perform the methods described in the various possible implementations above.

[0861] This application also provides a chip, including a memory and a processor. The memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that a device with the chip installed performs the methods described in the various possible implementations above.

[0862] It is understood that the above scenarios are merely examples and do not constitute a limitation on the application scenarios of the technical solutions provided in the embodiments of this application. The technical solutions of this application can also be applied to other scenarios. For example, as those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0863] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0864] The steps in the method of this application embodiment can be adjusted, combined, or deleted according to actual needs.

[0865] The units in the device of this application embodiment can be merged, divided, and deleted according to actual needs.

[0866] In this application, the same or similar terms, concepts, technical solutions and / or application scenario descriptions are generally described in detail only when they appear for the first time. When they appear again, they are generally not repeated for the sake of brevity. When understanding the technical solutions and other contents of this application, the same or similar terms, concepts, technical solutions and / or application scenario descriptions that are not described in detail later can be referred to their previous relevant detailed descriptions.

[0867] In this application, the descriptions of the various embodiments have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0868] The technical features of the present application can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of the present application.

[0869] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, controlled terminal device, or network device, etc.) to execute the methods of each embodiment of this application.

[0870] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a storage medium or transmitted from one storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, storage disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., a solid-state disk (SSD)).

[0871] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A processing method, wherein, Applied to the first device, including the following steps: S2: Send the first content to the second device based on the first information.

2. The method according to claim 1, wherein, It also includes at least one of the following: The first information includes at least one of the following: a first instruction, an event report message, operator configuration and / or policy, and descriptive information related to the second device; The first message is sent by the third device; The first content includes at least one of the following: information related to periodic or event-triggered perception service requests, perception context, event report message, third device identifier, current status of event report, and perception-related information; The second device is determined by the third device; The second device is determined by the first device.

3. The method according to claim 2, wherein, It also includes at least one of the following: The first information is sent by the third device after receiving the sensing service request; Sensing service requests are triggered by terminal devices and / or access network devices; The third device determines, based on the first information, that the first device is unsuitable for or unable to support the sensing of the current access network or serving cell. The second device is determined by the third device based on the first information; The second device is determined by the third device based on the second information; Receive the first message; Based on the first information, it is determined that the first device is not suitable for or cannot support the sensing of the current access network or serving cell; The second device is determined based on the first information; The second device is determined based on the second information; Receive the result of the perception context transmission operation sent by the second device; Release resources related to perception operations; The second device sends an event report confirmation message to the third device; The third device forwards the event report confirmation message from the second device to the terminal device and / or access network device; The second device performs the sensing operation.

4. The method according to claim 3, wherein, It also includes at least one of the following: The description information related to the second device is obtained through local configuration of the first device or by querying the fourth device. The description information related to the second device is obtained through local configuration on the third device or by querying the fourth device. The current status of the event reports includes the number of event reports received and / or the duration of the event reports; The perception-related information includes at least one of the following: previous perception estimates, timestamps of perception estimates, and perception measurements; The second information includes at least one of the following: sensing service area, operator configuration and / or policy, description information related to the second device, sensing client type, requested sensing service quality information, access type, RAT type, serving AN node, RAN configuration information, duration of event report, event report indication, and network slice information. The event report message includes an identifier indicating the first device; The incident report confirmation message includes the identifier of the second device; Event report confirmation messages are used to indicate changes to the current service's SENF; The event report confirmation message is used to indicate that changes to the current service's SENF should be rejected; The first device is the original SENF; The second device is the target SENF; The third device is AMF: The fourth device is NRF.

5. The method according to claim 4, wherein, It also includes at least one of the following: The descriptive information related to the second device includes at least one of the following: the second device's capabilities, load, energy consumption and efficiency, location, supported GAD shape, and the user plane connection that the requested terminal device has with a portion of the SENF. The requested perceived service quality information includes perception accuracy and / or response time; The sensing service area includes at least one TA; Incident reporting instructions include instructions for single incident reporting or multiple incident reporting; The descriptive information related to the second device is registered in the fourth device.

6. A processing method, wherein, Applied to a third device, including the following steps: S1: Send first information so that the first device sends first content to the second device based on the first information.

7. The method according to claim 6, wherein, It also includes at least one of the following: The first information includes at least one of the following: a first instruction, an event report message, operator configuration and / or policy, and descriptive information related to the second device; The first message is sent based on a perception service request; The first content includes at least one of the following: information related to periodic or event-triggered perception service requests, perception context, event report message, third device identifier, current status of event report, and perception-related information; The second device is determined by the third device; The second device is determined by the first device.

8. The method according to claim 7, wherein, It also includes at least one of the following: Sensing service requests are triggered by terminal devices and / or access network devices; Receive sensing service requests; Based on the first information, it is determined that the first device is not suitable for or cannot support the sensing of the current access network or serving cell; The first device determines, based on the first information, that the first device is not suitable for or cannot support the sensing of the current access network or serving cell. The second device is determined by the first device or the third device based on the first information; The second device is determined by the first device or the third device based on the second information; The first device receives the result of the perception context transmission operation sent by the second device; The first device releases resources related to sensing operations; Receive the event report confirmation message sent by the second device; Send an event report confirmation message from the second device to the terminal device and / or access network device; The second device performs the sensing operation.

9. The method according to claim 8, wherein, It also includes at least one of the following: The description information related to the second device is obtained through local configuration on the third device or by querying the fourth device. The description information related to the second device is obtained through local configuration of the first device or by querying the fourth device. The current status of the event reports includes the number of event reports received and / or the duration of the event reports; The perception-related information includes at least one of the following: previous perception estimates, timestamps of perception estimates, and perception measurements; The second information includes at least one of the following: sensing service area, operator configuration and / or policy, description information related to the second device, sensing client type, requested sensing service quality information, access type, RAT type, serving AN node, RAN configuration information, duration of event report, event report indication, and network slice information. The event report message includes an identifier indicating the first device; The incident report confirmation message includes the identifier of the second device; Event report confirmation messages are used to indicate changes to the current service's SENF; The event report confirmation message is used to indicate that changes to the current service's SENF should be rejected; The first device is the original SENF; The second device is the target SENF; The third device is AMF: The fourth device is NRF.

10. The method according to claim 9, wherein, It also includes at least one of the following: The descriptive information related to the second device includes at least one of the following: the second device's capabilities, load, energy consumption and efficiency, location, supported GAD shape, and the user plane connection that the requested terminal device has with a portion of the SENF. The requested perceived service quality information includes perception accuracy and / or response time; The sensing service area includes at least one TA; Incident reporting instructions include instructions for single incident reporting or multiple incident reporting; The descriptive information related to the second device is registered in the fourth device.

11. A processing method, wherein, Applied to a second device, including the following steps: S3: Receive the first content, which is sent by the first device based on the first information.

12. The method according to claim 11, wherein, It also includes at least one of the following: The first information includes at least one of the following: a first instruction, an event report message, operator configuration and / or policy, and descriptive information related to the second device; The first information is sent from the third device to the first device; The first content includes at least one of the following: information related to periodic or event-triggered perception service requests, perception context, event report message, third device identifier, current status of event report, and perception-related information; The second device is determined by the third device; The second device is determined by the first device.

13. The method according to claim 12, wherein, It also includes at least one of the following: The first information is sent from the third device to the first device after receiving the sensing service request; Sensing service requests are triggered by terminal devices and / or access network devices; The third device determines, based on the first information, that the first device is unsuitable for or unable to support the sensing of the current access network or serving cell. The second device is determined by the first device or the third device based on the first information; The second device is determined by the first device or the third device based on the second information; The first device determines, based on the first information, that the first device is not suitable for or cannot support the sensing of the current access network or serving cell. Send the perception context transmission operation result to the first device; The first device releases resources related to sensing operations; Send an event report confirmation message to the third device; The third device forwards the event report confirmation message from the second device to the terminal device and / or access network device; Perform perception operations.

14. The method according to claim 13, wherein, It also includes at least one of the following: The description information related to the second device is obtained through the local configuration of the first device or by the first device querying the fourth device. The description information related to the second device is obtained through the local configuration of the third device or by the third device querying the fourth device. The current status of the event reports includes the number of event reports received and / or the duration of the event reports; The perception-related information includes at least one of the following: previous perception estimates, timestamps of perception estimates, and perception measurements; The second information includes at least one of the following: sensing service area, operator configuration and / or policy, description information related to the second device, sensing client type, requested sensing service quality information, access type, RAT type, serving AN node, RAN configuration information, duration of event report, event report indication, and network slice information. The event report message includes an identifier indicating the first device; The incident report confirmation message includes the identifier of the second device; Event report confirmation messages are used to indicate changes to the current service's SENF; The event report confirmation message is used to indicate that changes to the current service's SENF should be rejected; The first device is the original SENF; The second device is the target SENF; The third device is AMF: The fourth device is NRF.

15. The method according to claim 14, wherein, It also includes at least one of the following: The descriptive information related to the second device includes at least one of the following: the second device's capabilities, load, energy consumption and efficiency, location, supported GAD shape, and the user plane connection that the requested terminal device has with a portion of the SENF. The requested perceived service quality information includes perception accuracy and / or response time; The sensing service area includes at least one TA; Incident reporting instructions include instructions for single incident reporting or multiple incident reporting; The descriptive information related to the second device is registered in the fourth device.

16. A communication device, wherein, include: A memory and a processor, wherein the memory stores a processing program, and the processing program, when executed by the processor, implements the processing method as described in claim 1, 6, or 11.

17. A computer-readable storage medium, wherein, The computer-readable storage medium stores a processing program, which, when executed by a processor, implements the processing method as described in claim 1, 6, or 11.

Images