Service implementation method, terminal, core network equipment, communication system and storage medium

Abstract

The invention relates to a service implementation method, a terminal, core network equipment, a communication system and a storage medium. The method comprises: a first network element receiving a first service request message sent by a terminal, the first service request message comprising first information, and determining, according to the first information, whether to send a second service request message to a second network element, the second service request message being generated according to the first service request message; the second service request message is used for requesting the second network element to realize the service process. Therefore, different situations of triggering the service process are supported, and failure of the service processing process is avoided.

Description

Service implementation method, terminal, core network equipment, communication system and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a service implementation method, terminal, core network equipment, communication system and storage medium. Background Art

[0002] In order to support direct communication between terminals, a sidelink (SL) communication method is introduced. Ranging refers to determining the distance between two or more terminals, or the direction from one terminal to another, through a PC5 interface. A PC5 interface refers to a communication interface between terminals, such as a short-range direct communication interface between vehicles, people, and road infrastructure. Sidelink SL positioning refers to estimating the position of a located terminal based on the sidelink SL. For example, ranging or sidelink SL positioning can be performed on a located terminal (e.g., a target terminal (target user equipment, target UE)) based on information from a terminal (e.g., a positioning terminal (located user equipment, located UE)). The reference terminal can be, for example, an SL reference terminal whose position is known or can be known in ranging or sidelink SL positioning. For another example, the relative position information of a terminal (e.g., a target terminal (target user equipment, target UE)) and another terminal (e.g., an SL reference terminal (sidelink reference user equipment, sidelink reference UE)) can be determined through ranging or sidelink SL positioning.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure provide a service implementation method, core network equipment, terminal, communication equipment, chip system, storage medium, computer program and computer program product, which can be applied in the field of communication technology to solve the technical problem of "not supporting the differentiation of different situations of triggering business processes, which will cause the business processing process to fail."

[0005] The present disclosure proposes a service implementation method, a terminal, a core network device, a communication system and a storage medium.

[0006] According to the first aspect of an embodiment of the present disclosure, a service implementation method is proposed, which is executed by a first network element, including: receiving a first service request message sent by a terminal, wherein the first service request message includes first information; based on the first information, determining whether to send a second service request message to a second network element, wherein the second service request message is generated based on the first service request message, and the second service request message is used to request the second network element to implement the service process.

[0007] According to the second aspect of an embodiment of the present disclosure, a service implementation method is proposed, which is executed by a terminal, including: sending a first service request message to a first network element, wherein the first service request message includes first information, the first information is used by the first network element to determine whether to send a second service request message to a second network element, the second service request message is generated based on the first service request message, and the second service request message is used to request the second network element to implement the service process.

[0008] According to the third aspect of an embodiment of the present disclosure, a service implementation method is proposed, including: a terminal sends a first service request message to a first network element, wherein the first service request message includes first information; the first network element determines whether to send a second service request message to a second network element based on the first information, wherein the second service request message is generated based on the first service request message, and the second service request message is used to request the second network element to implement the service process.

[0009] According to the fourth aspect of an embodiment of the present disclosure, a core network device is proposed, including: a transceiver module, used to receive a first service request message sent by a terminal, wherein the first service request message includes first information; a processing module, used to determine whether to send a second service request message to a second network element based on the first information, wherein the second service request message is generated based on the first service request message, and the second service request message is used to request the second network element to implement a service process.

[0010] According to the fifth aspect of an embodiment of the present disclosure, a terminal is proposed, including: a transceiver module, used to send a first service request message to a first network element, wherein the first service request message includes first information, the first information is used by the first network element to determine whether to send a second service request message to a second network element, the second service request message is generated based on the first service request message, and the second service request message is used to request the second network element to implement a service process.

[0011] According to the sixth aspect of an embodiment of the present disclosure, a communication device is proposed, comprising: one or more processors; wherein the processor is used to call instructions so that the communication device executes the service implementation method of any one of the first aspect, the second aspect, and the third aspect.

[0012] According to the seventh aspect of the embodiment of the present disclosure, a communication system is proposed, characterized in that it includes a core network device and a terminal, wherein the core network device is configured to implement the service implementation method of the first aspect, and the terminal is configured to implement the service implementation method of the second aspect.

[0013] According to the eighth aspect of the embodiment of the present disclosure, a storage medium is proposed, which stores instructions, and is characterized in that when the instructions are executed on a communication device, the communication device executes a service implementation method as described in any one of the first, second, and third aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the background technology, the drawings required for use in the embodiments of the present disclosure or the background technology will be described below.

[0015] FIG1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure;

[0016] FIG2 is an interactive diagram illustrating a method for implementing a service according to an embodiment of the present disclosure;

[0017] FIG3A is an interactive diagram illustrating a service implementation method according to another embodiment of the present disclosure;

[0018] FIG3B is an interactive diagram illustrating a method for implementing a service according to another embodiment of the present disclosure;

[0019] FIG3C is an interactive diagram illustrating a service implementation method according to another embodiment of the present disclosure;

[0020] FIG3D is an interactive diagram illustrating a method for implementing a service according to another embodiment of the present disclosure;

[0021] FIG3E is an interactive diagram illustrating a method for implementing a service according to another embodiment of the present disclosure;

[0022] FIG4A is an interactive diagram illustrating a service implementation method according to another embodiment of the present disclosure;

[0023] FIG4B is an interactive diagram illustrating a method for implementing a service according to another embodiment of the present disclosure;

[0024] FIG5 is an interactive diagram illustrating a service implementation method according to yet another embodiment of the present disclosure;

[0025] FIG6A is a schematic diagram of ranging or SL positioning service requests carrying different request types according to an embodiment of the present disclosure;

[0026] FIG6B is a schematic diagram of a ranging or SL positioning service request carrying information indicating an initiator in an embodiment of the present disclosure;

[0027] FIG6C is a schematic diagram of a ranging or SL positioning service request carrying a service type according to an embodiment of the present disclosure;

[0028] FIG7A is a schematic structural diagram of a core network device proposed in an embodiment of the present disclosure;

[0029] FIG7B is a schematic structural diagram of a terminal proposed in an embodiment of the present disclosure;

[0030] FIG8A is a schematic structural diagram of a communication device proposed in an embodiment of the present disclosure;

[0031] FIG8B is a schematic diagram of the structure of the chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0032] The embodiments of the present disclosure provide a service implementation method and apparatus, a communication device, a communication system, and a storage medium. In some embodiments, the terms "service implementation method" and "information processing method" and "communication method" are interchangeable; the terms "service implementation apparatus" and "information processing apparatus" and "communication apparatus" are interchangeable; and the terms "information processing system" and "communication system" are interchangeable.

[0033] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0034] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0035] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0036] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0037] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0038] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0039] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0040] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0041] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0042] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0043] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0044] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0045] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0046] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0047] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or reception point (TRP)" "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)", etc.

[0048] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)", "user terminal" "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc.

[0049] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0050] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0051] FIG1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG1 , a communication system 100 may include a terminal 101 and a core network device 102 .

[0052] In some embodiments, the terminal 101 may include, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0053] In some embodiments, the core network device 102 may be a single device including a first network element 1021, a second network element 1022, a third network element 1023, etc., or may be a plurality of devices or a device group including all or part of the first network element 1021, the second network element 1022, and the third network element 1023. The network elements may be virtual or physical. The core network may include, for example, at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC).

[0054] In some embodiments, the first network element 1021 is, for example, an Access and Mobility Management Function (AMF) network element, but the name is not limited thereto. The AMF network element is a logical node function network element on the core network side. It is the core network control plane access point for terminals and wireless devices, receives all connection and session-related information from user equipment, and performs registration, connection, reachability, and mobility management. In addition, the AMF network element provides a session management message transmission channel for terminal devices and session management function (SMF) devices, and provides authentication and authorization functions for user access.

[0055] In some embodiments, the first network element 1021 is used to provide access and mobility management functions.

[0056] In some embodiments, the second network element 1022 is, for example, a network element capable of processing an external positioning request, triggering the network to initiate positioning, and returning the positioning result to the client that initiated the positioning.

[0057] In some embodiments, the second network element 1022 is, for example, a Gateway Mobile Location Center (GMLC) network element, but the name is not limited thereto.

[0058] In some embodiments, the third network element 1023 is, for example, a location management function (LMF) network element that provides positioning services, and the name is not limited thereto. The LMF network element is located on the core network (CN) side and is used to provide location management function services to terminals. The LMF network element is used to coordinate the overall positioning and resource scheduling of terminals registered with or accessing the 5G core network (5GCN).

[0059] In some embodiments, the third network element 1023 is used to provide location management functionality.

[0060] In some embodiments, the terminal 101 and the core network device 102 can be connected through an access network device. Optionally, the access network device is, for example, a node or device that accesses the terminal to a wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a wireless fidelity (WiFi) system, but is not limited thereto.

[0061] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0062] The following embodiments of the present disclosure may be applied to the communication system 100 shown in Figure 1, or a portion thereof, but are not limited thereto. The entities shown in Figure 1 are illustrative only. The communication system may include all or part of the entities shown in Figure 1, or may include other entities outside of Figure 1. The number and form of the entities may be arbitrary. The connection relationship between the entities is illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0063] The embodiments of the present disclosure may be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.18 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (WiMAX (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (WiMAX (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other user plane connection establishment methods, and next-generation systems based on and extending these systems. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0064] Optionally, the target terminal is a terminal whose distance, direction and / or position is measured based on SL in ranging or SL service with the support of one or more SL reference terminals.

[0065] Optionally, the SL reference terminal is a terminal that supports positioning of a target terminal, for example, by using SL to send and / or receive reference signals for positioning, provide information related to positioning, etc.

[0066] Optionally, the positioning terminal is a SL reference terminal whose position is known or can be known using positioning based on the Uu interface. The positioning terminal can be used to determine the position of the target terminal using SL positioning.

[0067] Optionally, the SL positioning client terminal refers to a third-party terminal other than the SL reference terminal, target terminal, positioning terminal, etc., which initiates ranging or SL positioning service requests on behalf of the application resident thereon.

[0068] Optionally, in the SL positioning process involving 5GC, the position of the target terminal can be estimated with the help of the network by using the position of one or more positioning terminals, and the distance and / or direction between the target terminal and the positioning terminal, without limitation.

[0069] In some embodiments, "network" can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

[0070] Optionally, location service requests for relative positioning and / or distance and / or direction between two or more terminals can be supported. When a terminal is able to obtain ranging or SL positioning results using one or more other terminals with the help of an LMF network element in a public land mobile network (PLMN) serving the terminal, the terminal initiates a Sidelink Mobile Originated Location Request (SL-MO–LR) process involving one or more SL reference terminals and / or positioning terminals in the service request.

[0071] Optionally, when ranging or SL positioning service opening is provided to the SL positioning client terminal through the control plane of 5GC, the SL positioning client terminal triggers the ranging or SL positioning service opening by calling the SL-MO-LR process for SL positioning. The AMF network element selects a GMLC network element based on the service request, and forwards the ranging or SL positioning service request to the GMLC network element to obtain the ranging or SL positioning service requested by the SL positioning client UE identifier (IDentifier, ID) identified by, for example, a user permanent identifier (SUbscription Permanent Identifier, SUPI). After receiving the ranging or SL positioning result fed back by the GMLC network element, the AMF network element sends the ranging or SL positioning result to the SL positioning client terminal.

[0072] Optionally, in the terminal positioning process involving SL positioning assistance of 5GC, the positioning service can be implemented through SL-MO-LR request and interaction with LMF network elements. At the same time, when ranging or SL positioning service opening is provided to the SL positioning client terminal through the control plane of 5GC, the Sidelink Mobile Terminated Location Request (SL-MT-LR) process can be further triggered through SL-MO-LR request and interaction with GMLC network elements to implement ranging or SL positioning service opening. Therefore, it is necessary to consider how to effectively distinguish the service processes that trigger different situations.

[0073] FIG2 is an interactive diagram of a service implementation method according to an embodiment of the present disclosure. As shown in FIG2 , the present disclosure embodiment relates to a service implementation method that can be used in a communication system 100. The method includes:

[0074] Step S2101: The terminal sends a first service request message to the first network element.

[0075] In some embodiments, the first service request message can be used, for example, to request the implementation of a service, where the service is a ranging or SL positioning service. Of course, the service can also be any other possible type of service, without limitation. When the service is a ranging or SL positioning service, it can effectively support distinguishing different situations that trigger the ranging or SL positioning service process, thereby avoiding the failure of the ranging or SL positioning service processing process.

[0076] The terminal may be, for example, a SL client terminal, or may be a target terminal, a positioning terminal, or a SL reference terminal, without limitation.

[0077] In some embodiments, the first service request message may carry first information. The first information is used by the first network element to determine whether to send a second service request message to the second network element. The second service request message is generated based on the first service request message and is used to request the second network element to implement a service process.

[0078] The second service request message may refer to a service request message for requesting the second network element to implement the service process. For example, the first network element may refer to the first information to determine whether the second network element needs to further implement the service process. If it is determined that the second network element needs to further implement the service process, the second service request message is sent to the second network element. If it is determined that the second network element does not need to further implement the service process, the second service request message is not sent to the second network element.

[0079] In some embodiments, the first network element may be, for example, an AMF network element, and the second network element may be, for example, a GMLC network element. For example, the AMF network element may refer to the first information to determine whether the GMLC network element needs to initiate the SL-MT-LR process. If it is determined that the GMLC network element needs to initiate the SL-MT-LR process, the second service request message is sent to the GMLC network element. If it is determined that the GMLC network element does not initiate the SL-MT-LR process, the second service request message is not sent to the GMLC network element.

[0080] In some embodiments, the first information includes at least one of the following: terminal information, where the terminal information includes the type of the terminal initiating the service request; a request message type, where the request message type indicates whether to send the second service request message to the second network element; new information, where the new information indicates whether to send the second service request message to the second network element; and a service type, where the service type indicates whether to send the second service request message to the second network element. This enables the first network element to accurately determine whether it needs to send the second service request message to the second network element.

[0081] The terminal information is used to describe the terminal that initiates the service request. The terminal information may include the terminal type that initiates the service request. The terminal type indicates the type of the terminal. For example, the terminal type may be a client terminal (e.g., an SL positioning client terminal), or a terminal other than a client terminal, such as a target terminal, a positioning terminal, or an SL reference terminal.

[0082] In some embodiments, when the service is a ranging or SL positioning service, the client terminal mentioned in the embodiments of the present disclosure is an SL positioning client terminal.

[0083] Among them, the request message type can be used to describe the type of the first service request message, and the request message type can be specifically, for example, an extended SLMOLR type (extended SLMOLR-Type). In the embodiment of the present disclosure, the SLMOLR-Type can be extended, and based on the extended SLMOLR type, it is indicated whether to send the second service request message to the second network element.

[0084] The new information may be indication information to indicate whether to send the second service request message to the second network element.

[0085] The service type may be used to describe the category the service belongs to. In the embodiment of the present disclosure, the service type may be extended, and whether to send the second service request message to the second network element may be indicated based on the extended service type.

[0086] Among them, whether the above-mentioned indication information is implemented through an extended request message type, new information or an extended service type, the corresponding value can indicate the type of terminal that initiates the service request, whether the corresponding service request is sent to the second network element according to the SL-MO-LR request, or the purpose of initiating the service request, for example, to realize ranging or SL positioning service or to realize the opening of ranging or SL positioning service.

[0087] In some embodiments, the first service request message may further include second information, which is used to indicate a preferred type of service implementation result, thereby effectively improving the comprehensiveness of the information indication and supporting the achievement of the expected service implementation result.

[0088] In some embodiments, the second information may also be included in the second service request message.

[0089] Step S2102: The first network element determines to send a second service request message to the second network element based on the first information.

[0090] In some embodiments, the first network element may refer to one or more contents of the above-mentioned first information to determine whether to send the second service request message to the second network element.

[0091] In some embodiments, if the first information includes terminal information, the terminal information may include the type of the terminal initiating the service request. If the type of the terminal initiating the service request is a client terminal, it is determined to send a second service request message to the second network element.

[0092] For example, taking the service as ranging or SL positioning service, the client terminal can be specifically, for example, an SL client terminal, the first network element can be, for example, an AMF network element, and the second network element can be, for example, a GMLC network element. Then, when the terminal type is an SL client terminal, the AMF network element determines to send a second service request message to the GMLC network element.

[0093] In some embodiments, whether to send the second service request message to the second network element may be determined in combination with the request message type.

[0094] In some embodiments, if the request message type includes at least one of first indication information, second indication information, and third indication information, it may be determined whether to send the second service request message to the second network element, wherein the first indication information is used to indicate that the terminal type initiating the service request is a client terminal, the second indication information is used to instruct the first network element to send the second service request message to the second network element, and the third indication information is used to indicate that the service request is for service opening. This supports accurate and flexible determination of whether to send the second service request message to the second network element based on the request message type.

[0095] For example, taking the case where the service is ranging or SL positioning service, the first network element may be, for example, an AMF network element, and the second network element may be, for example, a GMLC network element. If the request message type is referred to to determine whether to send the second service request message to the GMLC network element, then when the request message type contains at least one of the above-mentioned first indication information, second indication information, and third indication information, the AMF network element may refer to the first indication information, the second indication information, or at least one of the third indication information in the request message type to determine whether to send the second service request message to the GMLC network element. If the request message type does not contain the first indication information, the second indication information, and the third indication information, it may be determined by default that the second service request message is not sent to the GMLC network element. For another example, it may also support determining whether to send the second service request message to the GMLC network element without referring to the request message type, for example, by referring to the terminal type, the extended service type, etc., to determine whether to send the second service request message to the GMLC network element.

[0096] In some embodiments, whether to send the second service request message to the second network element may be determined in combination with the new information.

[0097] In some embodiments, if the new information includes at least one of first indication information, second indication information, and third indication information, it can be determined whether to send the second service request message to the second network element, where the first indication information is used to indicate that the terminal type initiating the service request is a client terminal, the second indication information is used to instruct the first network element to send the second service request message to the second network element, and the third indication information is used to indicate that the service request is for service opening. This supports accurate and flexible determination of whether to send the second service request message to the second network element based on the new information.

[0098] For example, taking the service as ranging or SL positioning service, the first network element may be, for example, an AMF network element, and the second network element may be, for example, a GMLC network element. If the new information is referred to to determine whether to send the second service request message to the GMLC network element, then when the new information contains at least one of the above-mentioned first indication information, second indication information, and third indication information, the AMF network element determines to send the second service request message to the GMLC network element. If the new information does not contain the first indication information, the second indication information, and the third indication information, it can be determined by default that the second service request message is not sent to the GMLC network element. For another example, it can also support not referring to the new information to determine whether to send the second service request message to the GMLC network element, for example, referring to the terminal type, the extended service type, the request message type, etc., to determine whether to send the second service request message to the GMLC network element.

[0099] In some embodiments, whether to send the second service request message to the second network element may be determined in combination with the service type.

[0100] In some embodiments, if the service type includes at least one of first indication information, second indication information, and third indication information, it may be determined whether to send a second service request message to the second network element, wherein the first indication information is used to indicate that the terminal type initiating the service request is a client terminal, the second indication information is used to instruct the first network element to send the second service request message to the second network element, and the third indication information is used to indicate that the service request is for service opening. This supports accurate and flexible determination of whether to send the second service request message to the second network element based on the service type.

[0101] For example, taking the case where the service is ranging or SL positioning service, the first network element may be, for example, an AMF network element, and the second network element may be, for example, a GMLC network element. If the service type is referred to to determine whether to send the second service request message to the GMLC network element, then when the service type contains at least one of the above-mentioned first indication information, second indication information, and third indication information, the AMF network element determines to send the second service request message to the GMLC network element. If the service type does not contain the first indication information, the second indication information, and the third indication information, it may be determined by default that the second service request message is not sent to the GMLC network element. For another example, it may also support determining whether to send the second service request message to the GMLC network element without referring to the service type, for example, referring to the terminal type, the request message type, new information, etc., to determine whether to send the second service request message to the GMLC network element.

[0102] Step S2103: The first network element sends a second service request message to the second network element.

[0103] In some embodiments, when determining to send the second service request message to the second network element, the first network element may trigger sending the second service request message to the second network element, so as to trigger the second network element to further implement the service process.

[0104] Step S2104: The second network element further implements the service process according to the second service request message.

[0105] In some embodiments, after receiving the second service request message, the second network element may further implement a service process based on the second service request message. For example, in the case where the service is ranging or SL positioning service, the second network element may be a GMLC network element. After receiving the second request message, the GMLC network element may trigger the SL-MT-LR process.

[0106] Step S2105: The first network element determines not to send the second service request message to the second network element based on the first information.

[0107] In some embodiments, the first network element may also refer to the first information to determine not to send the second service request message to the second network element.

[0108] In some embodiments, when the terminal type is not a client terminal, it is determined not to send the second service request message to the second network element.

[0109] In some embodiments, the first network element may determine not to send the second service request message to the second network element based on the request message type.

[0110] In some embodiments, if the request message type includes at least one of fourth indication information, fifth indication information, and sixth indication information, it is determined not to send the second service request message to the second network element. The fourth indication information indicates that the terminal initiating the service request is not a client terminal, the fifth indication information instructs the first network element to send the third service request message to the third network element, and the sixth indication information indicates that the service request is for positioning. This supports accurate and flexible determination of whether to send the second service request message to the second network element based on the request message type.

[0111] For example, taking the service of ranging or SL positioning service as an example, the first network element can be, for example, an AMF network element, the second network element can be, for example, a GMLC network element, and the third network element is an LMF network element. If the request message type includes at least one of the above-mentioned fourth indication information, fifth indication information, and sixth indication information, the AMF network element determines not to send the second service request message to the GMLC network element, and the AMF network element can determine to send the third service request message to the LMF network element.

[0112] In some embodiments, the first network element may refer to the new information and determine not to send the second service request message to the second network element.

[0113] In some embodiments, if the new information includes at least one of fourth indication information, fifth indication information, and sixth indication information, it is determined not to send the second service request message to the second network element. The fourth indication information indicates that the terminal type initiating the service request is not a client terminal, the fifth indication information instructs the first network element to send the third service request message to the third network element, and the sixth indication information indicates that the service request is for positioning. This supports accurate and flexible determination of whether to send the second service request message to the second network element based on the new information.

[0114] For example, taking the service as ranging or SL positioning service, the first network element can be, for example, an AMF network element, the second network element can be, for example, a GMLC network element, and the third network element is an LMF network element. Then, when the new information contains at least one of the above-mentioned fourth indication information, fifth indication information, and sixth indication information, the AMF network element determines not to send the second service request message to the GMLC network element, and the AMF network element can determine to send the third service request message to the LMF network element.

[0115] In some embodiments, the first network element may refer to the service type to determine not to send the second service request message to the second network element.

[0116] In some embodiments, if the service type includes at least one of fourth indication information, fifth indication information, and sixth indication information, it is determined not to send the second service request message to the second network element. The fourth indication information indicates that the terminal initiating the service request is not a client terminal, the fifth indication information instructs the first network element to send the third service request message to the third network element, and the sixth indication information indicates that the service request is for positioning. This supports accurate and flexible determination of whether to send the second service request message to the second network element based on the service type.

[0117] For example, taking the service as ranging or SL positioning service, the first network element can be, for example, an AMF network element, the second network element can be, for example, a GMLC network element, and the third network element is an LMF network element. If the service type includes at least one of the above-mentioned fourth indication information, fifth indication information, and sixth indication information, the AMF network element determines not to send the second service request message to the GMLC network element, and the AMF network element can determine to send the third service request message to the LMF network element.

[0118] In other embodiments, if the first information does not include the terminal information, request message type, new information, and service type newly defined in the embodiments of the present disclosure, a third service request message may be sent to the third network element by default.

[0119] The third service request message is generated based on the first service request message, and is used to request the third network element to implement the service process. In some embodiments, the second information may also be included in the third service request message.

[0120] In some embodiments, the third network element is, for example, a LMF network element.

[0121] Step S2106: The first network element sends a third service request message to the third network element.

[0122] In some embodiments, after determining to send the third service request message to the third network element, the first network element may trigger sending the third service request message to the third network element. For example, after determining to send the third service request message to the LMF network element, the AMF network element may trigger sending the third service request message to the LMF network element.

[0123] Step S2107: The third network element further implements the service process according to the third service request message.

[0124] In some embodiments, after receiving the third service request message, the third network element may further implement the SL-MO-LR process.

[0125] The service implementation method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2107. For example, step S2101 can be implemented as an independent embodiment, step S2102 can be implemented as an independent embodiment, and so on, but the present invention is not limited thereto. Steps S2101+S2102 can be implemented as independent embodiments, and steps S2101+S2102+S2103 can be implemented as independent embodiments, but the present invention is not limited thereto.

[0126] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0127] In this embodiment, the terminal sends a first service request message to the first network element. The first information is used to indicate the first service request message. The first information is used by the first network element to determine whether to send a second service request message to the second network element. The second service request message is generated based on the first service request message. The second service request message is used to request the second network element to implement a service process. The first network element determines to send a second service request message to the second network element based on the first information, and sends the second service request message to the second network element so that the second network element further implements the service process based on the second service request message. The first network element determines not to send the second service request message to the second network element based on the first information, and sends a third service request message to the third network element so that the third network element further implements the service process based on the third service request message. This supports distinguishing different situations that trigger service processes and avoids failures in service processing.

[0128] FIG3A is an interactive diagram of a service implementation method according to another embodiment of the present disclosure. As shown in FIG3A , the embodiment of the present disclosure relates to a service implementation method that can be used in a first network element. The method includes:

[0129] Step S3101: Receive a first service request message sent by a terminal, where the first service request message includes first information.

[0130] Step S3102: Determine whether to send a second service request message to the second network element based on the first information, wherein the second service request message is generated based on the first service request message and is used to request the second network element to implement the service process.

[0131] The service implementation method involved in the embodiments of the present disclosure may include at least one of steps S3101 and S3102. For example, step S3101 can be implemented as an independent embodiment, step S3102 can be implemented as an independent embodiment, and so on, but the present invention is not limited thereto. Steps S3101 and S3102 can be implemented as independent embodiments, but the present invention is not limited thereto.

[0132] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0133] FIG3B is an interactive diagram of a service implementation method according to another embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to a service implementation method that can be used in a first network element. The method includes:

[0134] Step S3201: receiving terminal information sent by a terminal, wherein the terminal information includes the type of the terminal that initiates the service request.

[0135] Step S3202: Determine whether to send a second service request message to the second network element based on the terminal information.

[0136] The service implementation method involved in the embodiments of the present disclosure may include at least one of steps S3201 and S3202. For example, step S3201 can be implemented as an independent embodiment, step S3202 can be implemented as an independent embodiment, and so on, but the present disclosure is not limited thereto. Steps S3201 and S3202 can be implemented as independent embodiments, but the present disclosure is not limited thereto.

[0137] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0138] FIG3C is an interactive diagram of a service implementation method according to another embodiment of the present disclosure. As shown in FIG3C , the present disclosure embodiment relates to a service implementation method that can be used in a first network element. The method includes:

[0139] Step S3301: Receive a request message type sent by a terminal, where the request message type is used to indicate whether to send a second service request message to a second network element.

[0140] Step S3302: Determine whether to send a second service request message to the second network element according to the request message type.

[0141] The service implementation method involved in the embodiments of the present disclosure may include at least one of steps S3301 and S3302. For example, step S3301 can be implemented as an independent embodiment, step S3302 can be implemented as an independent embodiment, and so on, but the present invention is not limited thereto. Steps S3301 and S3302 can be implemented as independent embodiments, but the present invention is not limited thereto.

[0142] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0143] FIG3D is an interactive diagram of a service implementation method according to another embodiment of the present disclosure. As shown in FIG3D , the embodiment of the present disclosure relates to a service implementation method that can be used in a first network element. The method includes:

[0144] Step S3401: Receive new information sent by a terminal, where the new information is used to indicate whether to send a second service request message to a second network element.

[0145] Step S3402: Determine whether to send a second service request message to the second network element based on the new information.

[0146] The service implementation method involved in the embodiments of the present disclosure may include at least one of steps S3401 and S3402. For example, step S3401 can be implemented as an independent embodiment, step S3402 can be implemented as an independent embodiment, and so on, but the present disclosure is not limited thereto. Steps S3401+S3402 can be implemented as independent embodiments, but the present disclosure is not limited thereto.

[0147] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0148] FIG3E is an interactive diagram of a service implementation method according to another embodiment of the present disclosure. As shown in FIG3E , the embodiment of the present disclosure relates to a service implementation method that can be used in a first network element. The method includes:

[0149] Step S3501: Receive a service type sent by a terminal, where the service type is used to indicate whether to send a second service request message to a second network element.

[0150] Step S3502: Determine whether to send a second service request message to the second network element according to the service type.

[0151] The service implementation method involved in the embodiments of the present disclosure may include at least one of steps S3501 and S3502. For example, step S3501 can be implemented as an independent embodiment, step S3502 can be implemented as an independent embodiment, and so on, but the present invention is not limited thereto. Steps S3501 and S3502 can be implemented as independent embodiments, but the present invention is not limited thereto.

[0152] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0153] FIG4A is an interactive diagram of a service implementation method according to another embodiment of the present disclosure. As shown in FIG4A , the embodiment of the present disclosure relates to a service implementation method that can be used in a terminal. The method includes:

[0154] Step S4101: Send a first service request message to a first network element, wherein the first service request message includes first information, and the first information is used by the first network element to determine whether to send a second service request message to a second network element. The second service request message is generated based on the first service request message, and the second service request message is used to request the second network element to implement a service process.

[0155] The service implementation method involved in the embodiment of the present disclosure may include step S4101. For example, step S4101 may be implemented as an independent embodiment, but is not limited thereto.

[0156] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0157] FIG4B is an interactive diagram of a service implementation method according to another embodiment of the present disclosure. As shown in FIG4B , the present disclosure embodiment relates to a service implementation method that can be used in a terminal. The method includes:

[0158] Step S4201: Send a first service request message to a first network element, wherein the first service request message includes first information and second information, the first information is used by the first network element to determine whether to send a second service request message to the second network element, the second service request message is generated based on the first service request message, the second service request message is used to request the second network element to implement the service process, and the second information is used to indicate the preferred type of the service implementation result.

[0159] The service implementation method involved in the embodiment of the present disclosure may include step S4201. For example, step S4201 may be implemented as an independent embodiment, but is not limited thereto.

[0160] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0161] FIG5 is an interactive diagram of a service implementation method according to another embodiment of the present disclosure. As shown in FIG5 , the embodiment of the present disclosure relates to a service implementation method, which can be used in a first network element. The method includes:

[0162] Step S5101: The terminal sends a first service request message to a first network element, where the first service request message includes first information.

[0163] In step S5102, the first network element determines whether to send a second service request message to the second network element based on the first information, wherein the second service request message is generated based on the first service request message and is used to request the second network element to implement the service process.

[0164] Step S5103: When determining to send a second service request message to the second network element, the first network element sends the second service request message to the second network element.

[0165] Step S5104: When the first network element determines not to send the second service request message to the second network element, it determines to send a third service request message to the third network element.

[0166] The service implementation method involved in the embodiments of the present disclosure may include at least one of steps S5101 to S5104. For example, step S5101 can be implemented as an independent embodiment, step S5102 can be implemented as an independent embodiment, and so on, but the present invention is not limited thereto. Steps S5101+S5102 can be implemented as independent embodiments, but the present invention is not limited thereto.

[0167] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0168] It should be noted that, in the embodiment of the present disclosure, the relationship between the first network element determining not to send the second service request message to the second network element and the first network element determining to send the third service request message to the third network element can be described as follows:

[0169] The first network element's determination not to send the second service request message to the second network element may be the same as the first network element's determination to send the third service request message to the third network element. In other words, the first network element's determination not to send the second service request message to the second network element indicates that the first network element has determined to send the third service request message to the third network element.

[0170] For example, the AMF network element determines not to send the second service request message to the GMLC network element, which may be the same as the AMF network element determines to send the third service request message to the LMF network element. Specifically, for example, the AMF network element determines not to send the second service request message to the GMLC network element, that is, the AMF network element determines to send the third service request message to the LMF network element.

[0171] There may also be a further relationship between the first network element determining not to send the second service request message to the second network element and the first network element determining to send the third service request message to the third network element. That is, after the first network element determines not to send the second service request message to the second network element, the first network element further determines to send the third service request message to the third network element.

[0172] For example, the AMF network element determines not to send the second service request message to the GMLC network element, and the AMF network element determines to send the third service request message to the LMF network element, which may be a further relationship. Specifically, for example, after the AMF network element determines not to send the second service request message to the GMLC network element, the AMF network element further determines to send the third service request message to the LMF network element.

[0173] The following is an exemplary introduction to the above method.

[0174] Optional embodiment:

[0175] The embodiments of the present disclosure provide a method for supporting improved ranging or SL positioning service requests, which implements the SL-MO-LR process in different ways. The method for supporting improved ranging or SL positioning service requests may include:

[0176] The initiating terminal sends a message with information to distinguish different SL-MO-LR request messages, wherein the information for distinguishing different SL-MO-LR request messages can be achieved by indicating the type of terminal that initiates the service request, indicating whether the SL-MO-LR request sends the corresponding service request to the second network element, or the purpose of initiating the service request is, for example, to implement ranging or SL positioning service or to implement ranging or SL positioning service opening. For example, the request message is used for service opening, or the request message requires the AMF network element to send a positioning request message to the GMLC network element in the following manner. The information for distinguishing different SL-MO-LR request messages can be achieved in the following ways:

[0177] Extended SLMOLR type (SLMOLR-Type);

[0178] New information;

[0179] Expand business types;

[0180] Terminal information, wherein the terminal information includes the type of terminal that initiates the service request.

[0181] The preferred type of ranging or SL positioning results may also be included and set accordingly.

[0182] The AMF network element decides to send a positioning request message to the LMF network element or the GMLC network element based on the received message with information for distinguishing the SL-MO-LR request message. In addition, the AMF network element may send a positioning request message to the LMF network element or the GMLC network element by transparently transmitting the received SL-MO-LR request message or parsing the received SL-MO-LR request message to reconstruct the positioning request message sent to the LMF network element or the GMLC network element.

[0183] As shown in FIG6A , FIG6A is a schematic diagram of ranging or SL positioning service requests carrying different request types in an embodiment of the present disclosure.

[0184] In this embodiment, an extended SLMOLR type (SLMOLR-Type) may be used to indicate whether the ranging or SL positioning service request is initiated by a SL positioning client terminal or another terminal used for ranging or SL positioning. The other terminal used for ranging or SL positioning may be, for example, a target terminal, a positioning terminal, or an SL reference terminal.

[0185] The extended SLMOLR-Type is as follows:

[0186] SLMOLR-Type::=ENUMERATED{

[0187] rangingSidelink(0),

[0188] rangingSidelinkforSlClientUE(1),...}.

[0189] Alternatively, the extended SLMOLR-Type can be set to indicate that the ranging or SL positioning service request requires the AMF network element to send a corresponding positioning request message to the GMLC network element to trigger the SL-MT-LR process. For example, it can be set to rangingSidelinkforExposure, or the extended SLMOLR-Type can be set to indicate that the ranging or SL positioning service request is for service opening.

[0190] When SLMOLR-Type is set to "rangingSidelink", the AMF network element can send a positioning request message to the LMF network element accordingly. When SLMOLR-Type is set to "rangingSidelinkforSlClientUE" or "rangingSidelinkforExposure" or "rangingSidelinktoGmlc", the AMF network element can send a positioning request message to the GMLC network element accordingly. Figure 6A takes the SL positioning client terminal initiating a ranging or SL positioning service request to trigger the AMF network element to send a positioning request message to the GMLC network element, and uses the triggering of the SL-MT-LR process as an example to illustrate. Figure 6A involves UE1, UE2, SL positioning client terminal, AMF network element, LMF network element, UDM network element, NRF network element, and GMLC network element. Figure 6A shows the process of opening the positioning service through the 5GC network control plane based on the request type.

[0191] 1. The SL positioning client terminal triggers a service request.

[0192] In some embodiments, the SL positioning client terminal is, for example, a SL Positioning Client UE.

[0193] In some embodiments, the application layer of the SL positioning client terminal triggers the SL positioning client terminal to request the network to perform ranging / SL positioning between at least two terminals (e.g., between UE1 and UE2). If the SL positioning client terminal is in the CM-IDLE state, the service request process is first triggered to enter the CM-CONNECTED state.

[0194] 2. The SL positioning client terminal sends a UL NAS TRANSPORT message (SL-MO-LR request message (SLMOLR-Type=rangingSidelinkforSlClientUE)) to the AMF network element.

[0195] In some embodiments, the UL NAS TRANSPORT message represents an uplink non-access stratum transport message.

[0196] In some embodiments, the SL positioning client terminal sends an SL-MO-LR request message to the AMF network element via a UL NAS TRANSPORT message to perform ranging / SL positioning operations.

[0197] In some embodiments, the SL-MO-LR request message includes parameters of ranging / SL positioning service requirements: request type, the request type is used to indicate that the request message is initiated by the SL positioning client terminal, or the request message requires the AMF network element to send a corresponding positioning request message to the GMLC network element to trigger the SL-MT-LR process, or the request message is used for service opening, UE-1 identifier (IDentifier, ID) (for example, UE1's Generic Public Subscription Identifier (GPSI)), UE-2 ID (for example, UE2's GPSI). It may also include the preferred type of ranging or SL positioning results and the required quality of service (QoS), required quality, etc. For the request type of service opening, the preferred type of ranging or SL positioning results indicates the distance between two or more UEs based on the PC5 interface and / or the direction and / or relative position between one UE (for example, the target UE) and another UE (for example, the SL reference UE).

[0198] 3. The AMF network element sends the Ngmlc_Location_ProvideRanging_Request message to the GMLC network element.

[0199] In some embodiments, depending on the request type, the AMF network element may use the Network Repository Function (NRF) network element query or the configuration in the AMF network element to select a GMLC network element that supports ranging / SL positioning, and based on the SL-MO-LR request message received in step 2, send a positioning request message to the GMLC network element through the Ngmlc_Location_ProvideRanging_Request message to obtain the ranging / SL positioning results. The AMF network element may include the ID of the SL positioning client terminal (e.g., SUPI) in the Ngmlc_Location_ProvideRanging_Request message.

[0200] 4. Execute the SL-MT-LR process.

[0201] In some embodiments, the GMLC network element may trigger the SL-MT-LR process.

[0202] 5. The GMLC network element sends the Ngmlc_Location_ProvideRanging_Response message to the AMF network element.

[0203] In some embodiments, the GMLC network element returns the ranging / SL positioning results to the AMF network element via the Ngmlc_Location_ProvideRanging_Response message.

[0204] 6. The AMF network element sends a DL NAS TRANSPORT (SL-MO-LR response message) to the SL positioning client terminal.

[0205] In some embodiments, the DL NAS TRANSPORT message refers to a downlink non-access stratum transport message.

[0206] In some embodiments, the AMF network element returns the ranging / SL positioning results to the SL positioning client terminal via a DL NAS TRANSPORT message.

[0207] A1. The target terminal triggers a service request.

[0208] In some embodiments, the target terminal is, for example, a Target UE.

[0209] In some embodiments, the application layer of the target terminal triggers the target terminal to request the network to perform ranging / SL positioning between at least two terminals (e.g., between UE1 and UE2). If the target terminal is in the CM-IDLE state, the service request process is first triggered to enter the CM-CONNECTED state.

[0210] A2. The target terminal sends a UL NAS TRANSPORT message (SL-MO-LR request message (SLMOLR-Type=rangingSidelink)) to the AMF network element.

[0211] In some embodiments, the UL NAS TRANSPORT message represents an uplink non-access stratum transport message.

[0212] In some embodiments, the target terminal sends an SL-MO-LR request message to the AMF network element via a UL NAS TRANSPORT message to perform ranging / SL positioning operations.

[0213] In some embodiments, the SL-MO-LR request message includes parameters of ranging / SL positioning service requirements: request type, the request type is used to indicate that the request message is initiated by the target terminal, or the request message requires the AMF network element to send a corresponding positioning request message to the LMF network element, or the request message is for positioning service, UE-1 identifier (IDentifier, ID) (for example, UE1's Generic Public Subscription Identifier (GPSI)), UE-2 ID (for example, UE2's GPSI, or application layer ID). It may also include the preferred type of ranging or SL positioning results and the required quality of service (QoS), required quality, etc. For the request type for service opening, the preferred type of ranging or SL positioning results indicates the distance between two or more UEs based on the PC5 interface and / or the direction and / or relative position between one UE (for example, the target UE) and another UE (for example, the SL reference UE).

[0214] A3.AMF network element sends Nlmf_Location_DetermineLocation Request message to LMF network element.

[0215] In some embodiments, depending on the request type, the AMF network element can use the network storage function (NRF) network element query or the configuration in the AMF network element to select the LMF network element that supports ranging / SL positioning, and according to the SL-MO-LR request message received in step 2, send a positioning request message to the LMF network element through the Nlmf_Location_DetermineLocation Request message to obtain the ranging / SL positioning result.

[0216] A4. Perform other steps of the SL-MO-LR process.

[0217] In some embodiments, the LMF network element performs other steps of the SL-MO-LR process.

[0218] A5.LMF network element sends Nlmf_Location_DetermineLocation_Response message to AMF network element.

[0219] In some embodiments, the LMF network element returns the ranging / SL positioning result to the AMF network element through the Nlmf_Location_DetermineLocation_Response message.

[0220] A6.AMF network element sends DL NAS TRANSPORT (SL-MO-LR response message) to the target terminal.

[0221] In some embodiments, the DL NAS TRANSPORT message refers to a downlink non-access stratum transport message.

[0222] In some embodiments, the AMF network element returns the ranging / SL positioning results to the target terminal via a DL NAS TRANSPORT message.

[0223] In a service-based architecture (SBA), interactions between network elements can be achieved by calling services, rather than sending request messages and response messages. In a non-SBA architecture, this is achieved by sending corresponding messages. For example, in SBA, sending an Ngmlc_Location_ProvideRanging request corresponds to calling the Ngmlc_Location_ProvideRanging service, and the Ngmlc_Location_ProvideRanging response corresponds to the output after the Ngmlc_Location_ProvideRanging service is executed. For example, in SBA, sending an Nlmf_Location_DetermineLocation request corresponds to calling the Nlmf_Location_DetermineLocation service, and the Nlmf_Location_DetermineLocation response corresponds to the output after the Nlmf_Location_DetermineLocation service is executed. Of course, for other requests sent, the corresponding service can also be called for implementation, and the response corresponding to the request corresponds to the output after the corresponding service is called. There is no specific limitation on the request and / or response.

[0224] As shown in Figure 6B, Figure 6B is a schematic diagram of a ranging or SL positioning service request carrying information indicating the initiator in an embodiment of the present disclosure. In this embodiment, a new information may be included in the SL-MO-LR request message, and the information may be used to indicate whether the ranging or SL positioning service request is initiated by the SL positioning client terminal or by other terminals used for ranging or SL positioning services. Other terminals used for ranging or SL positioning services may be, for example, target terminals, positioning terminals, and SL reference terminals. Figure 6B involves UE1, UE2, SL positioning client terminals, AMF network elements, LMF network elements, UDM network elements, NRF network elements, and GMLC network elements. Figure 6B shows the process of opening the control plane based on the request information through the 5GC network.

[0225] When the SL positioning client terminal initiates a ranging or SL positioning service request, the AMF network element can send a corresponding positioning request message to the GMLC network element. Otherwise, the AMF network element can send a corresponding positioning request message to the LMF network element. Figure 6B uses the SL positioning client terminal initiating a ranging or SL positioning service request, and the AMF network element sending a positioning request message to the GMLC network element as an example to illustrate the triggering of the SL-MT-LR process.

[0226] 1. The SL positioning client terminal triggers a service request.

[0227] In some embodiments, the SL positioning client terminal is, for example, a SL Positioning Client UE.

[0228] In some embodiments, the application layer of the SL positioning client terminal triggers the SL positioning client terminal to request the network to perform ranging / SL positioning between at least two terminals (e.g., between UE1 and UE2). If the SL positioning client terminal is in the CM-IDLE state, the service request process is first triggered to enter the CM-CONNECTED state.

[0229] 2. The SL positioning client terminal sends a UL NAS TRANSPORT message (SL-MO-LR request message (request information)) to the AMF network element.

[0230] In some embodiments, the UL NAS TRANSPORT message represents an uplink non-access stratum transport message.

[0231] In some embodiments, the SL positioning client terminal sends an SL-MO-LR request message to the AMF network element via a UL NAS TRANSPORT message to perform ranging / SL positioning operations.

[0232] In some embodiments, the SL-MO-LR request message includes parameters of the ranging / SL positioning service requirements: UE-1 ID (e.g., UE1's GPSI), UE-2 ID (e.g., UE2's GPSI), ranging / SL positioning service type, required quality, and request information. The request information may indicate that the SL-MO-LR request message is initiated by the SL positioning client terminal and / or indicates that the SL-MO-LR request message requires the AMF network element to send a positioning request message to the GMLC network element to trigger the SL-MT-LR process. The ranging / SL positioning service type indicates the distance between two or more UEs based on the PC5 interface and / or the direction and / or relative position between one UE (e.g., target UE) and another UE (e.g., SL reference UE). Optionally, the request information may also be an indication message to indicate that the purpose of triggering the process is for service opening, or to indicate that the initiator of triggering the process is the SL positioning client terminal, for example, indicating the terminal role of the terminal that initiates the SL-MO-LR request message.

[0233] 3. The AMF network element sends the Ngmlc_Location_ProvideRanging_Request message to the GMLC network element.

[0234] In some embodiments, if the request information indicates an SL-MO-LR request message, which is initiated by the SL positioning client terminal, and / or indicates that the SL-MO-LR request message requires the AMF network element to send a positioning request message to the GMLC network element, the AMF network element can use the NRF network element query or the configuration in the AMF network element to select the GMLC network element that supports ranging / SL positioning, and according to the SL-MO-LR request message received in step 2, send a positioning request message to the GMLC network element through the Ngmlc_Location_ProvideRanging_Request message to obtain the ranging / SL positioning result. The AMF network element can include the ID of the SL positioning client terminal (for example, SUPI) in the Ngmlc_Location_ProvideRanging_Request message.

[0235] 4. Execute the SL-MT-LR process.

[0236] In some embodiments, the SL-MT-LR process may be initiated by a GMLC network element.

[0237] 5. The GMLC network element sends the Ngmlc_Location_ProvideRanging_Response message to the AMF network element.

[0238] In some embodiments, the GMLC network element returns the ranging / SL positioning results to the AMF network element via the Ngmlc_Location_ProvideRanging_Response message.

[0239] 6. The AMF network element sends a DL NAS TRANSPORT (SL-MO-LR response message) to the SL positioning client terminal.

[0240] In some embodiments, the DL NAS TRANSPORT message refers to a downlink non-access stratum transport message.

[0241] In some embodiments, the AMF network element returns the ranging / SL positioning results to the SL positioning client terminal via a DL NAS TRANSPORT message.

[0242] In this embodiment, it is also possible to determine whether a positioning request message needs to be sent to the LMF network element based on the service request, and trigger the sending of the positioning request message to the LMF network element. The specific implementation process can be referred to steps A1-A6 shown in Figure 6A, which will not be repeated here.

[0243] In a service-based architecture (SBA), the interaction between network elements can be achieved by calling services, not sending request messages and response messages. In a non-SBA architecture, it is achieved by sending corresponding messages. For example, in SBA, sending an Ngmlc_Location_ProvideRanging request corresponds to calling the Ngmlc_Location_ProvideRanging service, and the Ngmlc_Location_ProvideRanging response corresponds to the output after the execution of the Ngmlc_Location_ProvideRanging service. Of course, for other requests sent, the corresponding service can also be called to implement, and the response corresponding to the request corresponds to the output after the execution of the corresponding service. There is no specific limitation on the request and / or response.

[0244] As shown in Figure 6C, Figure 6C is a schematic diagram of a ranging or SL positioning service request carrying a service type in an embodiment of the present disclosure. In this embodiment, the value of the new service type (which can be a standard positioning service (LoCation Services, LCS) service type or a non-standard LCS service type) can be used to indicate that the ranging or SL positioning service request is initiated by the SL positioning client terminal, rather than by a terminal used for other ranging or SL positioning, or to indicate that it is used for service opening. Figure 6C involves UE1, UE2, SL positioning client terminal, AMF network element, LMF network element, UDM network element, NRF network element, and GMLC network element.

[0245] When the service type is set to indicate that the ranging or SL positioning service request is initiated by the SL positioning client terminal, rather than by other terminals used for ranging or SL positioning, or for service opening, the AMF network element can send the corresponding positioning request message to the GMLC network element. Otherwise, the AMF network element can send the corresponding positioning request message to the LMF network element. Figure 6C uses the SL positioning client terminal initiating a ranging or SL positioning service request and the AMF network element sending a positioning request message to the GMLC network element as an example to illustrate the triggering of the SL-MT-LR process.

[0246] 1. The SL positioning client terminal triggers a service request.

[0247] In some embodiments, the SL positioning client terminal is, for example, a SL Positioning Client UE.

[0248] In some embodiments, the application layer of the SL positioning client terminal triggers the SL positioning client terminal to request the network to perform ranging / SL positioning between at least two terminals (e.g., between UE1 and UE2). If the SL positioning client terminal is in the CM-IDLE state, the service request process is first triggered to enter the CM-CONNECTED state.

[0249] 2. The SL positioning client terminal sends a UL NAS TRANSPORT message (SL-MO-LR request message (service type = service open)) to the AMF network element.

[0250] In some embodiments, the UL NAS TRANSPORT message represents an uplink non-access stratum transport message.

[0251] In some embodiments, the SL positioning client terminal sends an SL-MO-LR request message to the AMF network element via a UL NAS TRANSPORT message to perform ranging / SL positioning operations.

[0252] In some embodiments, the SL-MO-LR request message includes parameters of the ranging / SL positioning service requirement: UE-1 ID (e.g., UE1's GPSI), UE-2 ID (e.g., UE2's GPSI), service type, preferred type of ranging or SL positioning result, required QoS, and required quality. When the service type is open service (for opening to SL client terminals), the preferred type of ranging or SL positioning result indicates the distance between two or more UEs based on the PC5 interface and / or the direction and / or relative position between one UE (e.g., target UE) and another UE (e.g., SL reference UE).

[0253] 3. The AMF network element sends the Ngmlc_Location_ProvideRanging_Request message to the GMLC network element.

[0254] In some embodiments, if the service type indicates that the service for ranging or SL positioning is open, the AMF network element can use the NRF network element query or the configuration in the AMF network element to select the GMLC network element that supports ranging / SL positioning, and according to the SL-MO-LR request message received in step 2, send a positioning request message to the GMLC network element through the Ngmlc_Location_ProvideRanging_Request message to obtain the ranging / SL positioning results.

[0255] In some embodiments, the AMF network element may include the ID of the SL positioning client terminal (e.g., SUPI) in the Ngmlc_Location_ProvideRanging_Request message.

[0256] 4. Execute the SL-MT-LR process.

[0257] In some embodiments, the SL-MT-LR process may be initiated by a GMLC network element.

[0258] 5. The GMLC network element sends the Ngmlc_Location_ProvideRanging_Response message to the AMF network element.

[0259] In some embodiments, the GMLC network element returns the ranging / SL positioning results to the AMF network element via the Ngmlc_Location_ProvideRanging_Response message.

[0260] 6. The AMF network element sends a DL NAS TRANSPORT (SL-MO-LR response message) to the SL positioning client terminal.

[0261] In some embodiments, the DL NAS TRANSPORT message refers to a downlink non-access stratum transport message.

[0262] In some embodiments, the AMF network element returns the ranging / SL positioning results to the SL positioning client terminal via a DL NAS TRANSPORT message.

[0263] In this embodiment, it is also possible to determine whether a positioning request message needs to be sent to the LMF network element based on the service request, and trigger the sending of the positioning request message to the LMF network element. The specific implementation process can be referred to steps A1-A6 shown in Figure 6A, which will not be repeated here.

[0264] In a service-based architecture (SBA), the interaction between network elements can be achieved by calling services, not sending request messages and response messages. In a non-SBA architecture, it is achieved by sending corresponding messages. For example, in SBA, sending an Ngmlc_Location_ProvideRanging request corresponds to calling the Ngmlc_Location_ProvideRanging service, and the Ngmlc_Location_ProvideRanging response corresponds to the output after the execution of the Ngmlc_Location_ProvideRanging service. Of course, for other requests sent, the corresponding service can also be called to implement, and the response corresponding to the request corresponds to the output after the execution of the corresponding service. There is no specific limitation on the request and / or response.

[0265] The disclosed embodiments support executing the SL-MO-LR process in different ways based on ranging and SL positioning service requests. The AMF can correctly process the SL-MO-LR request message to ensure that the location service request is correctly sent to the LMF network element or GMLC network element for further processing, thereby achieving the expected service implementation results and effectively avoiding service processing failures.

[0266] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a core network device (e.g., an AMF network element) in any of the above methods.

[0267] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0268] In the embodiment of the present disclosure, the processor is a circuit with signal processing capability. In one implementation, the processor can be a circuit with instruction reading and execution capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP); in another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit, and the logical relationship of the above hardware circuit is fixed or reconfigurable, such as a hardware circuit implemented by a processor as an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0269] FIG7A is a schematic diagram of the structure of a core network device according to an embodiment of the present disclosure. As shown in FIG7A , the core network device 7100 may include at least one of a transceiver module 7101 and a processing module 7102. The core network device 7100 may include:

[0270] The transceiver module 7101 is configured to receive a first service request message sent by a terminal, wherein the first service request message includes first information;

[0271] The processing module 7102 is used to determine whether to send a second service request message to the second network element based on the first information, wherein the second service request message is generated based on the first service request message and is used to request the second network element to implement the service process.

[0272] In some embodiments of the present disclosure, the first information includes at least one of the following:

[0273] Terminal information, including the type of terminal that initiated the service request;

[0274] A request message type, where the request message type is used to indicate whether to send a second service request message to the second network element;

[0275] New information, wherein the new information is used to indicate whether to send a second service request message to the second network element;

[0276] Service type, where the service type is used to indicate whether to send a second service request message to the second network element.

[0277] In some embodiments of the present disclosure, the processing module 7102 is specifically configured to perform any of the following:

[0278] The terminal type is a client terminal, and determining to send a second service request message to the second network element;

[0279] The terminal type is not a client terminal, and it is determined not to send the second service request message to the second network element.

[0280] In some embodiments of the present disclosure, the processing module 7102 is specifically configured to:

[0281] Determining, according to the request message type, to send a second service request message to the second network element;

[0282] The request message type includes at least one of the following:

[0283] First indication information, wherein the first indication information is used to indicate that the type of the terminal initiating the service request is a client terminal;

[0284] Second indication information, wherein the second indication information is used to instruct the first network element to send a second service request message to the second network element;

[0285] The third indication information is used to indicate that the service request is for service opening.

[0286] In some embodiments of the present disclosure, the processing module 7102 is specifically configured to:

[0287] Determining, according to the request message type, not to send the second service request message to the second network element;

[0288] The request message type includes at least one of the following:

[0289] Fourth indication information, wherein the fourth indication information is used to indicate that the type of the terminal initiating the service request is not a client terminal;

[0290] Fifth indication information, wherein the fifth indication information is used to instruct the first network element to send a third service request message to the third network element;

[0291] Sixth indication information, wherein the sixth indication information is used to indicate that the service request is for positioning.

[0292] In some embodiments of the present disclosure, the processing module 7102 is specifically configured to:

[0293] Determine, based on the new information, to send a second service request message to the second network element;

[0294] The new information includes at least one of the following:

[0295] First indication information, wherein the first indication information is used to indicate that the type of the terminal initiating the service request is a client terminal;

[0296] Second indication information, wherein the second indication information is used to instruct the first network element to send a second service request message to the second network element;

[0297] The third indication information is used to indicate that the service request is for service opening.

[0298] In some embodiments of the present disclosure, the processing module 7102 is specifically configured to:

[0299] Determining not to send the second service request message to the second network element according to the new information;

[0300] The new information includes at least one of the following:

[0301] Fourth indication information, wherein the fourth indication information is used to indicate that the type of the terminal initiating the service request is not a client terminal;

[0302] Fifth indication information, wherein the fifth indication information is used to instruct the first network element to send a third service request message to the third network element;

[0303] Sixth indication information, wherein the sixth indication information is used to indicate that the service request is for positioning.

[0304] In some embodiments of the present disclosure, the processing module 7102 is specifically configured to:

[0305] Determine, according to the service type, to send a second service request message to the second network element;

[0306] The business type includes at least one of the following:

[0307] First indication information, wherein the first indication information is used to indicate that the type of the terminal initiating the service request is a client terminal;

[0308] Second indication information, wherein the second indication information is used to instruct the first network element to send a second service request message to the second network element;

[0309] The third indication information is used to indicate that the service request is for service opening.

[0310] In some embodiments of the present disclosure, the processing module 7102 is specifically configured to:

[0311] Determining, according to the service type, not to send the second service request message to the second network element;

[0312] The business type includes at least one of the following:

[0313] Fourth indication information, wherein the fourth indication information is used to indicate that the type of the terminal initiating the service request is not a client terminal;

[0314] Fifth indication information, wherein the fifth indication information is used to instruct the first network element to send a third service request message to the third network element;

[0315] Sixth indication information, wherein the sixth indication information is used to indicate that the service request is for positioning.

[0316] In some embodiments of the present disclosure, the transceiver module 7101 is specifically used to send a third service request message to a third network element after determining not to send the second service request message to the second network element, wherein the third service request message is generated based on the first service request message, and the third service request message is used to request the third network element to implement the service process.

[0317] In some embodiments of the present disclosure, the transceiver module 7101 is specifically configured to:

[0318] When the first information does not include terminal information of the terminal type that initiates the service request, the request message type, new information, and the service type, a third service request message is sent to the third network element, wherein the third service request message is generated based on the first service request message, and the third service request message is used to request the third network element to implement the service process.

[0319] In some embodiments of the present disclosure, the first service request message further includes: second information, wherein the second information is used to indicate a preferred type of service implementation result.

[0320] In some embodiments of the present disclosure, the service is ranging or sidelink (SL) positioning service.

[0321] FIG7B is a schematic diagram of the structure of a terminal proposed in an embodiment of the present disclosure. As shown in FIG7B , the terminal 7200 may include at least one of a transceiver module 7201 and a processing module 7202. The terminal 7200 may include:

[0322] The transceiver module 7201 is used to send a first service request message to a first network element, wherein the first service request message includes first information, and the first information is used by the first network element to determine whether to send a second service request message to a second network element. The second service request message is generated based on the first service request message, and the second service request message is used to request the second network element to implement the service process.

[0323] In some embodiments of the present disclosure, the first information includes at least one of the following:

[0324] Terminal information, including the type of terminal that initiated the service request;

[0325] A request message type, where the request message type is used to indicate whether to send a second service request message to the second network element;

[0326] New information, wherein the new information is used to indicate whether to send a second service request message to the second network element;

[0327] Service type, where the service type is used to indicate whether to send a second service request message to the second network element.

[0328] In some embodiments of the present disclosure, the request message type includes at least one of the following:

[0329] First indication information, wherein the first indication information is used to indicate that the type of the terminal initiating the service request is a client terminal;

[0330] Second indication information, wherein the second indication information is used to instruct the first network element to send a second service request message to the second network element;

[0331] Third indication information, wherein the third indication information is used to indicate that the service request is for service opening;

[0332] Fourth indication information, wherein the fourth indication information is used to indicate that the type of the terminal initiating the service request is not a client terminal;

[0333] Fifth indication information, wherein the fifth indication information is used to instruct the first network element to send a third service request message to the third network element;

[0334] Sixth indication information, wherein the sixth indication information is used to indicate that the service request is for positioning.

[0335] In some embodiments of the present disclosure, the new information includes at least one of the following:

[0336] First indication information, wherein the first indication information is used to indicate that the type of the terminal initiating the service request is a client terminal;

[0337] Second indication information, wherein the second indication information is used to instruct the first network element to send a second service request message to the second network element;

[0338] Third indication information, wherein the third indication information is used to indicate that the service request is for service opening;

[0339] Fourth indication information, wherein the fourth indication information is used to indicate that the type of the terminal initiating the service request is not a client terminal;

[0340] Fifth indication information, wherein the fifth indication information is used to instruct the first network element to send a third service request message to the third network element;

[0341] Sixth indication information, wherein the sixth indication information is used to indicate that the service request is for positioning.

[0342] In some embodiments of the present disclosure, the service type includes at least one of the following:

[0343] First indication information, wherein the first indication information is used to indicate that the type of the terminal initiating the service request is a client terminal;

[0344] Second indication information, wherein the second indication information is used to instruct the first network element to send a second service request message to the second network element;

[0345] Third indication information, wherein the third indication information is used to indicate that the service request is for service opening;

[0346] Fourth indication information, wherein the fourth indication information is used to indicate that the type of the terminal initiating the service request is not a client terminal;

[0347] Fifth indication information, wherein the fifth indication information is used to instruct the first network element to send a third service request message to the third network element;

[0348] Sixth indication information, wherein the sixth indication information is used to indicate that the service request is for positioning.

[0349] In some embodiments of the present disclosure, the first service request message further includes: second information, wherein the second information is used to indicate a preferred type of service implementation result.

[0350] In some embodiments of the present disclosure, the service is ranging or sidelink (SL) positioning service.

[0351] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0352] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0353] Figure 8A is a schematic diagram of the structure of a communication device proposed in an embodiment of the present disclosure. Communication device 8100 can be a terminal, a network device, a chip, a chip system, or a processor that supports a terminal implementing any of the above methods, or a chip, a chip system, or a processor that supports a network device implementing any of the above methods. Communication device 8100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0354] As shown in Figure 8A, the communication device 8100 includes one or more processors 8101. The processor 8101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The communication device 8100 is used to perform any of the above methods.

[0355] In some embodiments, the communication device 8100 further includes one or more memories 8102 for storing instructions. Optionally, all or part of the memories 8102 may be located outside the communication device 8100.

[0356] In some embodiments, the communication device 8100 further includes one or more transceivers 8103. When the communication device 8100 includes one or more transceivers 8103, the transceiver 8103 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processor 8101 performs the other steps.

[0357] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0358] In some embodiments, the communication device 8100 may include one or more interface circuits 8104. Optionally, the interface circuit 8104 is connected to the memory 8102. The interface circuit 8104 may be configured to receive signals from the memory 8102 or other devices, and may be configured to send signals to the memory 8102 or other devices. For example, the interface circuit 8104 may read instructions stored in the memory 8102 and send the instructions to the processor 8101.

[0359] The communication device 8100 described in the above embodiments may be a terminal, a network device, or a third entity, but the scope of the communication device 8100 described in the present disclosure is not limited thereto, and the structure of the communication device 8100 may not be limited by FIG. 8A. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0360] FIG8B is a schematic diagram of the structure of a chip proposed in an embodiment of the present disclosure. If the communication device 8100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 8200 shown in FIG8B , but the present disclosure is not limited thereto.

[0361] The chip 8200 includes one or more processors 8201 , and the chip 8200 is configured to execute any of the above methods.

[0362] In some embodiments, the chip 8200 further includes one or more interface circuits 8202. Optionally, the interface circuit 8202 is connected to the memory 8203. The interface circuit 8202 can be used to receive signals from the memory 8203 or other devices, and can be used to send signals to the memory 8203 or other devices. For example, the interface circuit 8202 can read instructions stored in the memory 8203 and send the instructions to the processor 8201.

[0363] In some embodiments, the interface circuit 8202 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processor 8201 performs the other steps.

[0364] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

[0365] In some embodiments, the chip 8200 further includes one or more memories 8203 for storing instructions. Alternatively, all or part of the memories 8203 may be outside the chip 8200.

[0366] The present disclosure also proposes a storage medium having instructions stored thereon, which, when executed on the communication device 8100, causes the communication device 8100 to execute any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto, and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto, and may also be a temporary storage medium.

[0367] The present disclosure also provides a program product, which, when executed by the communication device 8100, enables the communication device 8100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0368] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

[0369] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

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

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

[0372] The above description is merely a specific embodiment of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this disclosure should be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be based on the scope of protection of the claims.

Claims

1. A service implementation method, characterized in that, Performed by a first network element, the method includes: Receiving a first service request message sent by a terminal, where the first service request message includes first information; Determining whether to send a second service request message to a second network element according to the first information, where the second service request message is generated according to the first service request message, and the second service request message is used to request the second network element to implement a service process.

2. The method according to claim 1, characterized in that, The first information includes at least one of the following: Terminal information, where the terminal information includes the type of the terminal that initiates the service request; Request message type, where the request message type is used to indicate whether to send a second service request message to the second network element; New information, where the new information is used to indicate whether to send a second service request message to the second network element; Service type, where the service type is used to indicate whether to send a second service request message to the second network element.

3. The method according to any one of claims 1-2, characterized in that Determining whether to send a second service request message to a second network element according to terminal information includes any of the following: If the terminal type is a client terminal, determining to send a second service request message to the second network element; If the terminal type is not a client terminal, determining not to send a second service request message to the second network element.

4. The method according to any one of claims 1-2, characterized in that, Determining whether to send a second service request message to a second network element according to the request message type includes: Determining to send a second service request message to the second network element according to the request message type; Where the request message type includes at least one of the following: First indication information, where the first indication information is used to indicate that the type of the terminal that initiates the service request is a client terminal; Second indication information, where the second indication information is used to indicate that the first network element sends a second service request message to the second network element; Third indication information, where the third indication information is used to indicate that the service request is for service opening.

5. The method according to any one of claims 1-2, characterized in that, Determining whether to send a second service request message to a second network element according to the request message type includes: Determining not to send a second service request message to the second network element according to the request message type; Where the request message type includes at least one of the following: Fourth indication information, where the fourth indication information is used to indicate that the type of the terminal that initiates the service request is not a client terminal; Fifth indication information, where the fifth indication information is used to indicate that the first network element sends a third service request message to a third network element; Sixth indication information, where the sixth indication information is used to indicate that the service request is for positioning.

6. The method according to any one of claims 1-2, characterized in that, Determining whether to send a second service request message to a second network element according to the new information includes: Determining to send a second service request message to the second network element according to the new information; Where the new information includes at least one of the following: First indication information, where the first indication information is used to indicate that the type of the terminal that initiates the service request is a client terminal; Second indication information, where the second indication information is used to indicate that the first network element sends a second service request message to the second network element; Third indication information, where the third indication information is used to indicate that the service request is for service opening.

7. The method according to any one of claims 1-2, characterized in that, Determine whether to send a second service request message to a second network element according to new information, including: Determine not to send a second service request message to the second network element according to the new information; Wherein, the new information includes at least one of the following: Fourth indication information, wherein the fourth indication information is used to indicate that the terminal type initiating the service request is not a client terminal; Fifth indication information, wherein the fifth indication information is used to indicate that the first network element sends a third service request message to a third network element; Sixth indication information, wherein the sixth indication information is used to indicate that the service request is for positioning; 8. The method according to any one of claims 1-2, characterized in that, Determine whether to send a second service request message to a second network element according to the service type, including: Determine to send a second service request message to the second network element according to the service type; Wherein, the service type includes at least one of the following: First indication information, wherein the first indication information is used to indicate that the terminal type initiating the service request is a client terminal; Second indication information, wherein the second indication information is used to indicate that the first network element sends a second service request message to the second network element; Third indication information, wherein the third indication information is used to indicate that the service request is for service opening; 9. The method according to any one of claims 1-2, characterized in that, Determine whether to send a second service request message to a second network element according to the service type, including: Determine not to send a second service request message to the second network element according to the service type; Wherein, the service type includes at least one of the following: Fourth indication information, wherein the fourth indication information is used to indicate that the terminal type initiating the service request is not a client terminal; Fifth indication information, wherein the fifth indication information is used to indicate that the first network element sends a third service request message to a third network element; Sixth indication information, wherein the sixth indication information is used to indicate that the service request is for positioning; 10. The method according to any one of claims 1-9, characterized in that, After determining not to send a second service request message to the second network element, the method further includes: Send a third service request message to a third network element, wherein the third service request message is generated according to the first service request message, and the third service request message is used to request the third network element to implement a service process; 11. The method according to claim 1, wherein The method further includes: In the case that the first information does not include terminal information, request message type, new information, and service type of the terminal type initiating the service request, send a third service request message to a third network element, wherein the third service request message is generated according to the first service request message, and the third service request message is used to request the third network element to implement a service process; 12. The method according to any one of claims 1-11, characterized in that, The first service request message further includes: second information, wherein the second information is used to indicate the preferred type of service implementation result; 13. The method according to any one of claims 1 to 12, characterized in that, The service is ranging or sidelink SL positioning service; 14. A service implementation method, characterized in that, Executed by a terminal, the method includes: A first service request message is sent to a first network element, wherein the first service request message includes first information, the first information is used by the first network element to determine whether to send a second service request message to a second network element, the second service request message is generated based on the first service request message, and the second service request message is used to request the second network element to implement a service process.

15. The method according to claim 14, wherein The first information includes at least one of the following: Terminal information, wherein the terminal information includes the type of terminal that initiates the service request; A request message type, wherein the request message type is used to indicate whether to send a second service request message to the second network element; New information, wherein the new information is used to indicate whether to send a second service request message to the second network element; Service type, wherein the service type is used to indicate whether to send a second service request message to the second network element.

16. The method according to any one of claims 14-15, characterized in that, The request message type includes at least one of the following: First indication information, wherein the first indication information is used to indicate that the type of the terminal initiating the service request is a client terminal; second indication information, wherein the second indication information is used to instruct the first network element to send a second service request message to the second network element; third indication information, wherein the third indication information is used to indicate that the service request is for service opening; Fourth indication information, wherein the fourth indication information is used to indicate that the type of the terminal initiating the service request is not a client terminal; Fifth indication information, wherein the fifth indication information is used to instruct the first network element to send a third service request message to the third network element; Sixth indication information, wherein the sixth indication information is used to indicate that the service request is for positioning.

17. The method according to any one of claims 14-15, characterized in that, The new information includes at least one of the following: First indication information, wherein the first indication information is used to indicate that the type of the terminal initiating the service request is a client terminal; second indication information, wherein the second indication information is used to instruct the first network element to send a second service request message to the second network element; third indication information, wherein the third indication information is used to indicate that the service request is for service opening; Fourth indication information, wherein the fourth indication information is used to indicate that the type of the terminal initiating the service request is not a client terminal; Fifth indication information, wherein the fifth indication information is used to instruct the first network element to send a third service request message to the third network element; Sixth indication information, wherein the sixth indication information is used to indicate that the service request is for positioning.

18. The method according to any one of claims 14-15, characterized in that, The business type includes at least one of the following: First indication information, wherein the first indication information is used to indicate that the type of the terminal initiating the service request is a client terminal; second indication information, wherein the second indication information is used to instruct the first network element to send a second service request message to the second network element; third indication information, wherein the third indication information is used to indicate that the service request is for service opening; Fourth indication information, wherein the fourth indication information is used to indicate that the type of the terminal initiating the service request is not a client terminal; The fifth indication information, wherein the fifth indication information is used to instruct the first network element to send a third service request message to the third network element; The sixth indication information, wherein the sixth indication information is used to indicate that the service request is for positioning.

19. The method according to any one of claims 14-18, characterized in that, The first service request message further includes: second information, wherein the second information is used to indicate the preferred type of service implementation result.

20. The method according to any one of claims 14-19, characterized in that, The service is ranging or sidelink SL positioning service.

21. A service implementation method, characterized in that, The method includes: The terminal sends a first service request message to the first network element, wherein the first service request message includes first information; The first network element determines whether to send a second service request message to the second network element according to the first information, wherein the second service request message is generated according to the first service request message, and the second service request message is used to request the second network element to implement a service process.

22. A core network device, characterized in that, The core network device includes: A transceiver module, configured to receive a first service request message sent by a terminal, wherein the first service request message includes first information; A processing module, configured to determine whether to send a second service request message to the second network element according to the first information, wherein the second service request message is generated according to the first service request message, and the second service request message is used to request the second network element to implement a service process.

23. A terminal, characterized in that, The terminal includes: A transceiver module, configured to send a first service request message to the first network element, wherein the first service request message includes first information, and the first information is used for the first network element to determine whether to send a second service request message to the second network element, the second service request message is generated according to the first service request message, and the second service request message is used to request the second network element to implement a service process.

24. A communication device, characterized in that, Includes: One or more processors; Wherein, the processor is configured to execute the service implementation method according to any one of claims 1-21.

25. A storage medium, the storage medium stores instructions, characterized in that, When the instruction runs on a communication device, the communication device is caused to execute the service implementation method according to any one of claims 1-21.

Images