Service interaction method and apparatus

Abstract

Provided in the present application are a service interaction method and apparatus. The present application supports a spark link / nearlink / Bluetooth protocol, or the present application supports an IEEE protocol, such as an IEEE 802.11be / Wi-Fi 7 / EHT protocol, an IEEE 802.11bn / Wi-Fi 8 / UHR protocol, an IEEE IMMW protocol, an IEEE 802.15.4ab / UWB protocol or an IEEE 802.11bf / sensing protocol. The method comprises: in a short-range wireless communication system, a client and a server being able to perform service interaction on the basis of a client port number of an application of the client and a port number of a service of the server, thereby implementing a fine-grained service interaction process.

Description

Service interaction method and device

[0001] The present application claims priority to the Chinese patent application No. 202411389348.4, filed on September 30, 2024, and entitled "Service interaction method and device", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] Embodiments of the present application relate to the field of communication, in particular to a service interaction method and device. BACKGROUND

[0003] With the development of communication technology, the application scenarios of star flash communication technology are becoming more and more widespread. In a star flash communication system, electronic devices interact with each other in the granularity of client and server, which has a large granularity and affects the service interaction efficiency of the client and the server. SUMMARY

[0004] The present application provides a service interaction method and device, which can effectively improve the service interaction efficiency of the client and the server.

[0005] In a first aspect, the present application provides a service interaction method, which is applied to a short-range wireless communication system. The method comprises: obtaining a port number of a service of a server; sending a first signaling, wherein the first signaling comprises a first source port number and a first destination port number; and wherein the first source port number is a client port number of a first application, and the first destination port number is a port number of a first service, and the first service is one or more of the services of the server. In this way, the present application distinguishes different services of the server and different applications of the client by using the port number, so that the client and the server can interact with each other based on the port number of the application and the port number of the service, thereby realizing the directional sending of the signaling between the application and the service. In this way, the client can access a specified service through the destination port number. Correspondingly, the server can identify the specified service to be accessed by the client based on the destination port number, and further identify the source of the access based on the source port number, thereby realizing fine-grained service interaction and improving the service interaction efficiency of the client and the server.

[0006] For example, the server can perform a service operation on the specified service based on the port number of the service indicated by the destination port number.

[0007] For example, the short-range wireless communication system can include, but is not limited to, a star flash communication system, a Bluetooth communication system, etc.

[0008] For example, the electronic device can act as a server or a client.

[0009] The first signaling can be signaling used by a client in the short-range wireless communication system to interact with a server for service. Alternatively, the first signaling can be any SSAP signaling involved in the embodiments of the present application, for example, it can be read signaling or write signaling, which is not limited in the present application.

[0010] The client can include one or more applications. The first application can be one or more of the applications of the client.

[0011] The application of the client corresponds to a client port number.

[0012] The server includes one or more services corresponding to one or more applications. Each application corresponds to one or more services. The first service can be one or more of the services of the server.

[0013] The service of the server corresponds to a port number. Alternatively, one port number can correspond to multiple services. The first service can refer to a specific service port number, multiple services with the same port number, or multiple services with different port numbers.

[0014] In a possible implementation, the first application includes the first service, and the port number of the first service is the port number of the first service of the first application. In this way, the first application of the client can access the first service of the first application in the server based on the port number of the corresponding service in the service access (or service interaction) process, thereby realizing directional access between the application and the service and achieving more fine-grained service interaction.

[0015] In a possible implementation, the port number of the first service of the first application is different from the port number of other services of the first application, or the port number of the first service of the first application is the same as the port number of other services of the first application. In this way, different services can be isolated from each other in the short-range wireless communication system in the present application to realize concurrent service granularity, that is, services can be concurrent.

[0016] The port numbers of the services in the first application are completely the same, that is, the port number of the first service is the same as the port numbers of other services of the first application.

[0017] The port numbers of the services in the first application are not completely the same, that is, the port number of the first service is the same as the port number of at least one service (that is, part of the services) of the other services of the first application.

[0018] In a possible implementation, the port numbers of the services of the first application are different from the port numbers of the services of other applications. In this way, in the short-range wireless communication system in the present application, different applications can be isolated from each other to implement application-granularity concurrency, that is, the services of different applications can be concurrent.

[0019] In one example, the port numbers of the services of the first application are completely the same, and the port numbers of the services of the first application are different from the port numbers of the services of other applications.

[0020] In another example, the port numbers of the services of the first application are partially the same, and the port numbers of the services of the first application are different from the port numbers of the services of other applications.

[0021] In yet another example, the port numbers of the services of the first application are completely different, and the port numbers of the services of the first application are different from the port numbers of the services of other applications.

[0022] In a possible implementation, the first signaling is a request signaling, and the method further includes: sending, to the service end, second signaling, the second signaling being a request signaling, and the second signaling including a second source port number and a second destination port number, where the second source port number and the second destination port number are at least one of the following: the second source port number is different from the first source port number, and the second destination port number is different from the first destination port number; and receiving first response signaling sent by the service end, the first response signaling being feedback by the service end in response to the first signaling. In this way, the present application adopts a finer-granularity service interaction manner, so that the client and the service end can control and isolate the traffic through the port numbers, thereby increasing the number of concurrent service interactions between the client and the service end and improving the service interaction efficiency between the client and the service end.

[0023] In a possible implementation, the method further includes: receiving third signaling sent by the service end, the third signaling including a third source port number and a third destination port number, the third source port number being a port number of the first service, and the third destination port number being a client port number of the first application. In this way, the service end can implement service interaction with a specified application of the client based on the port number of the application of the client. Correspondingly, after receiving the signaling, the client can identify the corresponding application based on the destination port number in the signaling, thereby implementing fine-granularity directional service interaction.

[0024] In a possible implementation, the port number of the one or more services is acquired by: acquiring a descriptor of a service declaration of the one or more services, the descriptor being used to indicate the port number of the corresponding service; and reading a value of the descriptor of the service declaration of the one or more services to acquire the port number of the one or more services. In this way, the client can acquire the port number of each service of the service end by reading the descriptor, and perform service interaction with the specified application of the service end based on the acquired port number of the service.

[0025] In a possible implementation, after the port number of the service provided by the service end is acquired, the method further includes: sending target signaling to the service end, the target signaling including the client port number of the first application, or including the client port number of each application of the client. In this way, the client and the service end can also interact the port number of the local end and the opposite end by customizing signaling or multiplexing existing signaling.

[0026] Exemplarily, the target signaling can be the first target signaling or the second target signaling in the embodiments of the present application.

[0027] In a possible implementation, the method further includes: the port number of the first service is a service management port number of the service end. Exemplarily, the first service can be a plurality of services of the service of the service end. In this way, in the scenario of accessing a plurality of services, the client in the present application can use the service management port number of the service end to implement access to the plurality of services.

[0028] In a possible implementation, the short-range wireless communication system supports non-IP data transmission. In this way, the non-IP transmission layer of the star flash in the present application can perform packet encapsulation and decapsulation based on the port number of the application and the port number of the service.

[0029] In a second aspect, the present application provides a service interaction method. The method is applied to a short-range wireless communication system, and comprises: obtaining a client port number of an application of a client; sending a first signaling to the client, the first signaling comprising a first source port number and a first destination port number; wherein the first source port number is a port number of a first service, and the first destination port number is a client port number of the first application, and the client port number of the first application is one or more of the applications of the client. In this way, the present application distinguishes different services of the server and different applications of the client by using the port numbers, so that the client and the server can perform service interaction based on the port numbers of the applications and the port numbers of the services, thereby realizing directional sending of the signaling between the applications and the services. In this way, the server can perform service interaction with the specified application of the client through the destination port number. Correspondingly, after receiving the signaling, the client can identify the specified application of the server to which the service interaction is performed based on the destination port number, and can further identify the source of the service interaction based on the source port number, thereby realizing fine-grained service interaction and improving the service interaction efficiency of the client and the server.

[0030] In a possible implementation, the first application comprises a first service, and the port number of the first service is the port number of the first service of the first application.

[0031] In a possible implementation, the port number of the first service of the first application is different from the port numbers of other services of the first application, or the port number of the first service of the first application is the same as the port numbers of other services of the first application.

[0032] In a possible implementation, the port numbers of the services of the first application are different from the port numbers of the services of other applications.

[0033] In a possible implementation, the first signaling is an indication signaling, and the method further comprises: sending a second signaling to the client, the second signaling being an indication signaling, and the second signaling comprising a second source port number and a second destination port number, wherein the second source port number and the second destination port number are at least one of the following: the second source port number is different from the first source port number, and the second destination port number is different from the first destination port number; and receiving a first confirmation signaling sent by the client, the first confirmation signaling being fed back by the client in response to the first signaling.

[0034] In a possible implementation, the method for obtaining the client port number of the application of the client comprises: receiving third signaling sent by the client, the third signaling comprising a third source port number and a third destination port number; the third source port number is the client port number of the first application, and the third destination port number is the port number of the first service; and the client port number of the first application is obtained in response to the third signaling. In this way, the server can learn the port number of the application of the client by learning the source port number in the signaling.

[0035] In a possible implementation, the method for obtaining the client port number of the application of the client comprises: receiving target signaling sent by the client, the target signaling comprising the client port number of the first application or the client port numbers of the applications of the client.

[0036] In a possible implementation, before the client port number of the application of the client is obtained, the method further comprises: sending, to the client, values of descriptors corresponding to the services of the server, the values of the descriptors being used to indicate the port numbers of the corresponding services. In this way, the server can indicate the port numbers of the services of the server to the client through the values of the descriptors.

[0037] In a possible implementation, the method further comprises: the port number of the first application is a service management port number of the client. In this way, in the scenario where the server sends notification or indication to the multiple applications of the client, the server can implement through the service management port number of the client.

[0038] In a possible implementation, before the client port number of the application of the client is obtained, the method further comprises: if signaling with the source port number being the client port number of the first application is received, sending fourth signaling to the client, the fourth signaling being used to indicate rejection of the access of the first application to the service of the server this time. In this way, the server can perform access control on the client based on the source port number, for example, can reject the access of the specified application to the service of the server.

[0039] In a possible implementation, the short-range wireless communication system supports non-IP data transmission.

[0040] In a third aspect, an embodiment of the present application provides a service interaction device, applied to a short-range wireless communication system, the device comprising: one or more processors; one or more memories; and one or more computer programs, wherein the one or more computer programs are stored in the one or more memories, and when the computer programs are executed by the one or more processors, the device performs the following steps: obtaining a port number of a service of a service end; sending first signaling, the first signaling comprising a first source port number and a first destination port number; wherein the first source port number is a client end port number of a first application, and the first destination port number is a port number of a first service, and the first service is one or more of the services of the service end.

[0041] In a possible implementation, the first application comprises the first service, and the port number of the first service is a port number of the first service of the first application.

[0042] In a possible implementation, the port number of the first service of the first application is different from port numbers of other services of the first application, or the port number of the first service of the first application is the same as the port numbers of the other services of the first application.

[0043] In a possible implementation, the port numbers of the services of the first application are different from port numbers of services of other applications.

[0044] In a possible implementation, the first signaling is a request signaling, and when the computer programs are executed by the one or more processors, the device performs the following steps: sending second signaling to the service end, the second signaling being a request signaling, and the second signaling comprising a second source port number and a second destination port number, wherein the second source port number and the second destination port number are at least one of the following manners: the second source port number is different from the first source port number, and the second destination port number is different from the first destination port number; and receiving first response signaling sent by the service end, the first response signaling being feedback by the service end in response to the first signaling.

[0045] In a possible implementation, when the computer programs are executed by the one or more processors, the device performs the following steps: receiving third signaling sent by the service end, the third signaling comprising a third source port number and a third destination port number, the third source port number being the port number of the first service, and the third destination port number being the client end port number of the first application.

[0046] In a possible implementation, when the computer programs are executed by the one or more processors, the device performs the following steps: obtaining a descriptor of a service declaration of one or more services, the descriptor being used to indicate a port number of a corresponding service; reading a value of the descriptor of the service declaration of the one or more services to obtain the port number of the one or more services.

[0047] In a possible implementation, when the computer program is executed by the one or more processors, the apparatus is caused to perform the following steps: sending, to the server, target signaling, the target signaling including a client port number of the first application or including client port numbers of each application of the client.

[0048] In a possible implementation, the port number of the first service is a port number of a service management of the server.

[0049] In a possible implementation, the short-range wireless communication system supports non-IP data transmission.

[0050] In a fourth aspect, the present application provides a service interaction apparatus applied to a short-range wireless communication system, the apparatus comprising: one or more processors; one or more memories; and one or more computer programs, wherein the one or more computer programs are stored in the one or more memories, and when the computer program is executed by the one or more processors, the apparatus is caused to perform the following steps: obtaining a client port number of an application of a client; sending, to the client, first signaling, the first signaling including a first source port number and a first destination port number; wherein the first source port number is a port number of a first service, and the first destination port number is the client port number of the first application, and the client port number of the first application is one or more of the applications of the client.

[0051] In a possible implementation, the first application includes the first service, and the port number of the first service of the first application is the port number of the first service of the first application.

[0052] In a possible implementation, the port number of the first service of the first application is different from port numbers of other services of the first application, or the port number of the first service of the first application is the same as the port numbers of the other services of the first application.

[0053] In a possible implementation, the port numbers of each service of the first application are different from port numbers of each service of other applications.

[0054] In a possible implementation, the first signaling is indication signaling, and when the computer program is executed by the one or more processors, the apparatus is caused to perform the following steps: sending, to the client, second signaling, the second signaling being indication signaling, the second signaling including a second source port number and a second destination port number, wherein the second source port number and the second destination port number are in at least one of the following manners: the second source port number is different from the first source port number, and the second destination port number is different from the first destination port number; and receiving first confirmation signaling sent by the client, the first confirmation signaling being fed back by the client in response to the first signaling.

[0055] In a possible implementation, when the computer program is executed by one or more processors, the apparatus performs the following steps: receiving third signaling sent by the client, the third signaling including a third source port number and a third destination port number; the third source port number is the client port number of the first application, and the third destination port number is the port number of the first service; in response to the third signaling, obtaining the client port number of the first application.

[0056] In a possible implementation, when the computer program is executed by one or more processors, the apparatus performs the following steps: receiving target signaling sent by the client, the target signaling including the client port number of the first application or the client port numbers of each application of the client.

[0057] In a possible implementation, when the computer program is executed by one or more processors, the apparatus performs the following steps: sending, to the client, values of descriptors corresponding to each service of the server, the values of the descriptors being used to indicate the port numbers of the corresponding services.

[0058] In a possible implementation, the port number of the first application is a port number managed by the service of the client.

[0059] In a possible implementation, when the computer program is executed by one or more processors, the apparatus performs the following steps: if the signaling with the source port number being the client port number of the first application is received, sending fourth signaling to the client, the fourth signaling being used to indicate rejection of the access of the first application to the service of the server this time.

[0060] In a possible implementation, the short-range wireless communication system supports non-IP data transmission.

[0061] In a fifth aspect, an embodiment of the present application provides a computer readable medium for storing a computer program, the computer program including instructions for executing the method in the first aspect or any possible implementation manner of the first aspect, or the method in the second aspect or any possible implementation manner of the second aspect.

[0062] In a sixth aspect, an embodiment of the present application provides a computer program, the computer program including instructions for executing the method in the first aspect or any possible implementation manner of the first aspect, or the method in the second aspect or any possible implementation manner of the second aspect.

[0063] In a seventh aspect, embodiments of this application provide a chip including a processing circuit and transceiver pins. The transceiver pins and the processing circuit communicate with each other via an internal connection path. The processing circuit executes the method in the first aspect or any possible implementation of the first aspect, or the method in the second aspect or any possible implementation of the second aspect, to control the receiving pin to receive signals and to control the transmitting pin to transmit signals.

[0064] Eighthly, embodiments of this application provide a short-range wireless communication system, which includes the client and server mentioned in the first and second aspects above. Attached Figure Description

[0065] Figure 1 is an exemplary architecture diagram of a communication system;

[0066] Figure 2 is an exemplary overall architecture diagram of the Star Flash wireless communication system;

[0067] Figure 3 is a schematic diagram of service management roles as an example;

[0068] Figure 4 is a schematic diagram of an exemplary service structure;

[0069] Figure 5 is a schematic diagram of the structure of an example entry;

[0070] Figure 6 is a schematic diagram of an exemplary handle;

[0071] Figure 7 is an exemplary schematic diagram of inter-layer interaction;

[0072] Figure 8 is a schematic diagram of the service interaction process in the prior art as an example;

[0073] Figure 9 is a schematic diagram of the port number configuration of an exemplary StarScan communication system;

[0074] Figure 10 is a schematic diagram of the signaling format as an example;

[0075] Figure 11 is an exemplary schematic diagram of the process by which the server obtains the port number of the application;

[0076] Figure 12 is a schematic diagram of the signaling format as an example;

[0077] Figure 13 is a schematic diagram illustrating the format of a transport layer control field;

[0078] Figure 14 is an exemplary service interaction diagram;

[0079] Figure 15 is an exemplary schematic diagram of the process by which the server obtains the port number of the application.

[0080] Figure 16 is a schematic diagram illustrating an exemplary service interaction;

[0081] FIG. 17 is a schematic diagram of service interaction;

[0082] FIG. 18 is a flowchart of a method of service interaction;

[0083] FIG. 19 is a schematic diagram of an apparatus. DETAILED DESCRIPTION

[0084] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the accompanying drawings in the embodiments of the present application.

[0085] In order to better understand the technical solutions in the embodiments of the present application, first, the technical terms that can be involved are briefly described.

[0086] 1. Service end

[0087] The service end can optionally be a service bearer, and can be used to receive and respond to the request of the client end.

[0088] 2. Client end

[0089] The client end can optionally be a service user, and can be used to submit an access request to the service end and receive the response returned by the service end.

[0090] 3. Application

[0091] The application in the embodiments of the present application can include but is not limited to:

[0092] 1) Application standard

[0093] The application standard, which can also be referred to as an application protocol, is not limited in the present application. The basic application layer standard includes an atomic capability standard and an application standard. The application standard defines a set of preconfigured protocols and services (which can be understood as being associated with the application and the corresponding service), and aims to provide a standardized solution for a specific type of communication application (such as audio transmission), to ensure interoperability and functional consistency between devices

[0094] 2) Customized application

[0095] The service and protocol of such an application are both customized.

[0096] 3) Starlink application

[0097] Such an application uses the application protocol of the Starlink standard.

[0098] 4. Service (Service)

[0099] The service refers to a set of capability information or function collection disclosed by the service end.

[0100] 5. Service Structure

[0101] The service management defines a unified expression format and framework for describing various services.

[0102] The present application supports spark link / nearlink / Bluetooth protocol, or the present application supports IEEE protocol, such as IEEE 802.11be / WiFi 7 / EHT(extremely high throughput) protocol, such as IEEE 802.11bn / WiFi 8 / UHR(ultra high reliability) protocol, such as IEEE IMMW(Integrated mmWave) protocol, such as IEEE 802.15.4ab / UWB(ultra wideband) protocol, such as IEEE 802.11bf / Sensing protocol.

[0103] The technical solutions of the embodiments of the present application can be applied to, but are not limited to, a wireless short-range communication system and a wireless communication system supporting longer distance transmission (such as 1-18 km, more than 18 km) (such as a next-generation spark wireless communication system). The wireless short-range communication system can include a wireless short-range communication technology (also known as spark 1.0 technology) with advantages of ultra-low latency, ultra-high reliability, precise synchronization, etc., and is suitable for applications in scenarios such as smart cars, smart homes, smart terminals, and smart manufacturing. For example, applications in the smart car scenario include immersive in-vehicle sound field or noise reduction, wireless interactive projection, and 360-degree panoramic view, which can achieve immersive interactive experience and improve vehicle safety.

[0104] The wireless communication system supporting longer distance transmission (such as 1-18 km) mainly includes next-generation spark wireless communication systems, such as spark 2.0 wireless communication system, spark 3.0 wireless communication system, etc., which are not only suitable for communication scenarios with low latency requirements, such as the above-mentioned vehicle communication, industrial control, etc., but also suitable for communication scenarios with no high latency requirements.

[0105] In some possible implementations, the above-mentioned communication system or can be used in combination with a mobile communication system, for example, the mobile communication system includes but is not limited to a fourth generation (4th Generation, 4G) communication system (for example, a long term evolution (long term evolution, LTE) system), a fifth generation (5th generation, 5G) communication system (for example, a new radio (new radio, NR) system), and a future mobile communication system such as a sixth generation (6th generation, 6G) mobile communication system, etc.

[0106] FIG. 1 is an architecture diagram of a communication system, which is exemplarily shown. Please refer to FIG. 1, the communication system includes but is not limited to a first electronic device and a second electronic device. In the embodiments of the present application, the first electronic device is optionally a client (also can be called a sink device, which is not limited in the present application), and the second electronic device is optionally a server (also can be called a source device, which is not limited in the present application). It should be noted that in the embodiments of the present application, only the first electronic device is taken as an example of the client, and the second electronic device is taken as an example of the server. In fact, the first electronic device can also be a server, and the second electronic device can also be a client, that is, the electronic device can be a client or a server in the system, which is not limited in the present application. It should be further noted that the number of clients and servers in the embodiments of the present application is only an illustrative example. In actual application, more clients and servers can be included in the system, one client can be connected to multiple servers, and one server can also be connected to multiple clients, which is not limited in the present application.

[0107] In the embodiments of the present application, the electronic device (including the first electronic device or the second electronic device) has a device, equipment, module, chip or chip system with a transceiver function. The electronic device can also be referred to as a terminal device, a user equipment (UE), an access terminal, a subscriber unit, a user station, a mobile station (MS), a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or a user apparatus. The terminal node in the embodiments of the present application can be a mobile phone, a cellular phone, a smart phone, a Pad, a mouse, a remote controller, a stylus, a set-top box, a router, a camera, a screen, a smart screen, a wireless data card, a personal digital assistant computer (PDA), a wireless modem, a handset, a laptop computer, a smart watch, a smart bracelet, a wireless earphone, an electronic conference whiteboard, a machine type communication (MTC) terminal, a computer with a wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a smart home device (for example, a refrigerator, a television, an air conditioner, a washing machine, an electric rice cooker, a table lamp, an electric meter, etc.), a smart robot, a mechanical arm, a workshop device, a wireless terminal in a self-driving vehicle, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical treatment, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a vehicle-mounted terminal, a vehicle-mounted screen, a vehicle-mounted audio, a vehicle key, a roadside unit (RSU) with a terminal function, etc., a flight device (for example, a smart robot, a hot air balloon, a drone, an airplane), etc. The client or server of the present application can also be a vehicle-mounted module, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit built into a vehicle as one or more components or units. The client or server can also be other devices with terminal functions, for example, it can also be a device in device-to-device (D2D) communication that performs a client function or a server function.

[0108] Embodiments of the present application do not limit the device form of the client and the server, and the device for implementing the functions of the client and the server can be the client and the server; or can be a device capable of supporting the client and the server to implement the functions, such as a chip system. The device can be installed in an electronic device or used with the electronic device. In embodiments of the present application, the chip system can be composed of a chip, or can include a chip and other discrete devices.

[0109] It should be pointed out that the scheme in the embodiments of the present application is only illustrated by taking the star flash wireless communication system as an example, and the first electronic device and the second electronic device can also be referred to as star flash devices. In other embodiments, the method in the embodiments of the present application can also be applied to other communication systems, and the corresponding names can also be replaced by the names of corresponding functions in other communication systems.

[0110] FIG. 2 is an exemplary overall architecture diagram of a star flash wireless communication system, which can be the architecture of the client or the architecture of the server. Please refer to FIG. 2, the system can include but is not limited to the following from top to bottom: a basic application layer, a basic service layer, and an access layer.

[0111] The basic application layer provides a basic application layer standard, which can include an atomic capability standard and an application standard. The application standard (which can also be referred to as an application configuration standard or a standardized application, which is not limited in the present application) defines a set of preconfigured protocols and services (which can be understood as that the application (or application protocol) is associated with the corresponding service), aiming to provide a standardized solution for a specific type of star flash communication application (such as audio transmission), and to ensure interoperability and functional consistency between devices. The atomic capability standard defines the basic and general functions used by the application standard, as well as the control signaling and interaction process involved in completing this function. The atomic capability standard is general, and one atomic capability standard can be referenced by multiple application standards and called by multiple application standards.

[0112] In embodiments of the present application, the basic application layer includes but is not limited to one or more application-defined protocols. For example, it can include but is not limited to: standardized video applications, standardized audio applications, standardized human-computer interaction, standardized third-party applications, etc.

[0113] Among them, the standardized video application (which can also be referred to as a video application standard) can include but is not limited to: panoramic surround view, desktop collaboration, mobile phone screen projection, home theater, etc. The standardized audio application (which can also be referred to as an audio application standard) can include but is not limited to: wireless earphones, panoramic sound, microphones, etc. The standardized human-computer interaction (which can also be referred to as a human-computer interaction standard) can include but is not limited to: keyboard, mouse, stylus, etc.

[0114] Of course, in some examples, other star flash applications, third-party applications or custom applications can also be included in the basic application layer, which is not limited in the present application.

[0115] The basic service layer provides functional units or services such as device discovery, service management, connection management, data transmission and adaptation, QoS (Quality of Service) management, measurement management, information security, etc., for supporting device discovery, connection, transmission, interaction requirements in the entire business cycle from business triggering to business ending.

[0116] Optionally, device discovery, service management, connection management, data transmission and adaptation, QoS (Quality of Service) management, measurement management, information security, etc. can be understood as functional units or services of the control plane. The description of other functional units, services or data in the basic service layer can refer to the prior art, which is not limited in the present application.

[0117] The access layer, also known as star flash access layer or basic access layer, is used to provide secure and efficient data transmission for management nodes and terminal nodes. Optionally, the access layer supports SLB (SparkLink Basic) and / or SLE (Sparklink Low Energy). That is, the access layer only supports SLB, or only supports SLE, or supports both SLB and SLE, which is not limited in the present application.

[0118] In the embodiments of the present application, the service management functional unit is used for interaction on the service management transmission channel established by the data transmission and adaptation functional unit, and completes the service access and response requirements of the application. Service management is one of the core functional units of the basic service layer, which can provide internal service management functions including service registration, maintenance, deletion, etc. for the basic application layer and the basic service layer. At the same time, the service management functional unit also defines a unified service structure and a star flash service interaction protocol. The service structure is an expression format, which provides a unified basic template for service definition. The star flash service interaction protocol provides standard signaling for star flash devices to realize service discovery and interaction between each other.

[0119] The service management includes two parts: service structure and service interaction protocol. The service structure defines the expression and organization of the service. The functional units of the underlying application layer or the underlying service layer describe their functions and behaviors in attributes, methods and events and entrust them to the service management according to the regulations of the service management. The SparkLink Service Access Protocol (SSAP) defines the discovery process and access process of the service structure and the signaling required in the process. Through the service management, the interconnection and intercommunication between the SparkLink devices at the service level can be realized.

[0120] The service management functional unit is one of the components of the underlying service layer. The service management functional unit supports the management of various services of the underlying application layer and the underlying service layer functional units and guarantees the interconnection and intercommunication at the service level. The negotiation of the QoS and the Port (interface) of the underlying application layer is performed through the service management. The service management functional unit performs service interaction and data transmission through the transmission channel provided by the data transmission and adaptation functional unit. The service management functional unit provides the device internal service management functions including service registration, maintenance and deletion for the underlying application layer and the underlying service layer functional units.

[0121] The service management functional unit is the service management entity of the SparkLink upper layer protocol and performs service interaction through the transmission channel provided by the data transmission and adaptation functional unit. The service management functional unit can use three kinds of transmission channels: SLB service management transmission channel, SLE service management transmission channel and SLB relay service management transmission channel. The three kinds of transmission channels are default. When the access layer supports both SLB and SLE, the type of the transmission channel is specified by the underlying application layer or other specific functional units of the underlying service layer.

[0122] Some functions of the service management and the technical terms involved are described below:

[0123] 1. Role

[0124] FIG. 3 is a schematic diagram of the service management role. As shown in FIG. 3, the service management defines two roles: service server and client. The service server is the service bearer and receives and responds to the request of the client. The client is the service user and submits the access request to the service server and obtains and receives the response returned by the service server.

[0125] Optionally, one device (for example, the first electronic device or the second electronic device in FIG. 1) can assume both the service server and the client role.

[0126] 2. Service structure

[0127] Service management defines the uniform expression format and framework of various services, and the expression format is called service structure. The service structure defines that a service is composed of service structure members including service declaration, service reference, attribute, method and event; in addition, the service structure also defines the composition of the service structure members; the service structure also defines the reference and logical relationship between services; the service structure structures and datafies the above contents by defining the expression format and access method of the service structure members. The client understands the functions provided by the server through the service structure, and accesses according to its own needs. The service structure is obtained through the service discovery process, and the service structure is the basis for accessing the service.

[0128] A service refers to a set of capability information or function set disclosed by a server. An application or general application service framework is composed of one or more services, and provides complete functions through the service set, such as a home indoor monitoring application that can provide humidity detection service and temperature detection service.

[0129] In the Xing flash communication system, according to the service definition mode, the service is divided into two types of Xing flash standard service and custom service. The standard service is a service standardized and maintained by the Xing flash alliance, and the custom service is a service customized by the manufacturer according to actual needs on the basis of meeting the requirements of the present standard.

[0130] FIG. 4 is a schematic diagram of a service structure, please refer to FIG. 4, the scope of a service is from the service declaration of the service to the end handle indicated in the service declaration. The service declaration is followed by other service structure members, and the typical order is service reference, attribute, method and event.

[0131] For example, the service declaration is the first service structure member in the service, and the handle of the service declaration is also the starting handle of the service. The service declaration indicates the type of the service and the identification of the service.

[0132] 3. Service basic data structure

[0133] 1) Entry

[0134] FIG. 5 is a schematic diagram of the structure of an entry, please refer to FIG. 5, the service is presented in the form of an entry. An entry can express a service declaration or a service reference or an attribute or a method or an event. The entry is composed of a handle, a category, an identification, data, permissions and additional information. For example, in an entry, the handle, the category and the identification must exist, and the data field, the permissions and the additional information are optional. The structure of the entry is only a logical level definition, and the actual storage method of the service in the server can be set according to actual needs, which is not limited by the present application.

[0135] Handle, is the index number of the entry generated by the server, handle is used to indicate the location of the entry in the server. On a server, the value of the handle is not allowed to repeat; an entry is indexed by a unique handle. The length of the handle is 2 bytes, of which 0x0000-0x000F is reserved for service management handle, 0x0010-0xFFFF is available for service handle. The allocation of entry handle can be discontinuous, but must be in ascending order.

[0136] Figure 6 is a schematic diagram of the handle, please refer to Figure 6, each application of the server corresponds to one or more entries, the client can access the service through the handle, that is, the client can access the content of the entry through the handle, so as to achieve the purpose of interacting with the application.

[0137] Category, indicates the type of service structure member carried by the entry and the information of standard and custom type.

[0138] Identification, indicates the specific content described by the entry, which is indicated by a universally unique identifier

[0139] Data field, is the data information associated with the identification field, as shown in Figure 5, the data field includes but is not limited to: operation indication, data value, descriptor. Optionally, the data field can carry a variable number of descriptors.

[0140] Among them, the operation indication is used to specify the access mode of the value range in the data value and the descriptor.

[0141] The meaning of the data value is defined by the identification. The data value is a byte group, which can be expressed as a regular integer value, a boolean value or a string, etc., and can also express a floating point number, a scientific notation value and a custom data structure by means of a descriptor.

[0142] A descriptor is used to carry associated information of a data value, such as a supplementary description of the data value, a format specification of the data value, an access control of the data value, or a specific function defined by the upper protocol. A descriptor is composed of a descriptor type and descriptor data. The service management function unit defines a series of standard descriptors for use by the upper protocol, while allowing the upper protocol to define additional specific descriptors. When a data field carries a descriptor, the order of the descriptor is not fixed. The client cannot make any assumptions about the order of the descriptor. When the client finds a descriptor that it cannot recognize, it can skip it and should not access the descriptor. The descriptor value is readable by default, and when it is writable, it should be reflected in the access control field. The descriptor type represents the function of the descriptor, occupying 1 byte, with a type range of 0x00-0xFF. The descriptor type definition space of attributes, methods, and events is independent of each other. For attribute descriptors, the service management function unit occupies 0x00-0x1F, 0x00 is reserved and not defined. 0xFF is a vendor-defined descriptor type, and the remaining values are left for use by the upper protocol.

[0143] In the embodiments of the present application, one or more port numbers of services (which can also be referred to as service port numbers) can be included in the descriptor (or descriptor field). That is, in the embodiments of the present application, the service end can indicate the port number corresponding to the service of the application of the service end to the client through the descriptor. Correspondingly, the client can read the descriptor in the corresponding entry of the service declaration of the service end to obtain the port number of at least one service of the service end.

[0144] Optionally, one or more applications can be included in the service end, and a single application can define (which can also be understood as being associated with or including) one or more services. The service end can indicate the port number of at least one service corresponding to one or more applications to the client, which can be set according to actual needs, and the present application does not make any limitation.

[0145] Still referring to FIG. 5, the permission in the entry is a security requirement raised by the service end when the client accesses the service structure member on the service end. Only the client that meets the security requirement can access the service structure member, which is set by the service end and invisible to the client.

[0146] The additional information includes additional conditions, which is an optional item of the entry, and is used by the service end to annotate the corresponding entry. The content can be set according to actual needs, and is invisible to the client.

[0147] 4. Inter-layer interaction

[0148] FIG. 7 is a schematic diagram of an example inter-layer interaction. Referring to FIG. 7, in an embodiment of the present application, the service management function unit of the server (which can also be referred to simply as the service management of the server) provides the function units of the basic application layer and the basic service layer with service registration and deletion functions. After the corresponding registration service is completed, the server generates a service structure of the registered service. The description of the service structure can be referred to above, and will not be described again here.

[0149] For example, after the service management function unit of the server receives a request of the application to delete a service, the server releases the service structure of the corresponding service. The service management function unit of the server reports service access results, such as attribute values being modified, receiving method calls, and the like, to other function units of the basic application layer or the basic service layer for subsequent processing.

[0150] For example, the application of the client can register with the service management function unit (the process can be different from the service registration of the server). The service management function unit (which can also be referred to simply as the service management of the client) undertakes the service discovery and service access requests of other function units of the basic application layer or the basic service layer, and returns corresponding service structures or service access results.

[0151] Specifically, in one example, the service management function unit of the client responds to the service discovery requirements (requests or demands) of other function units of the basic application layer or the basic service layer, the client and the server perform service interaction (the description of the service interaction can be referred to below, and will not be described again here), and the client can obtain the service structure fed back by the server. In another example, the service management function unit of the client responds to the service access requests of other function units of the basic application layer or the basic service layer, the client and the server perform service interaction, and the client can obtain the service access results fed back by the server. The service management function unit of the client feeds back the service structure or the service access results to other function units of the basic application layer or the basic service layer in response to the received service structure or service access results.

[0152] For example, the service management function unit of the client also reports events, notifications, indications and the like data or information actively sent by the server. Specifically, the server and the client perform service interaction, the server sends events, notifications, indications and the like information to the client, and the service management function unit of the client feeds back corresponding events, notifications, indications and the like information to other function units of the basic application layer or the basic service layer in response to the obtained events, notifications, indications and the like information.

[0153] As shown in FIG. 7, the client and the server can communicate based on SSAP related signaling. For example, the access of the client to the server can be implemented through SSAP related signaling.

[0154] Specifically, after receiving the request of the other functional units of the underlying application layer or the underlying service layer, the service management functional unit of the server or the client interacts with the opposite end through the SSAP, and accordingly, the SparkLink Service Access Protocol Packet Data Unit (SSAP PDU) is transmitted as data on the service management transmission channel. The related description of the SSAP PDU will be described in detail below.

[0155] Optionally, the interface between the other functional units of the underlying application layer or the underlying service layer and the service management functional unit is internal, and the specific interface can be set according to actual needs, which is not limited in the application.

[0156] 5. Service interaction

[0157] In the embodiments of the application, as described above, the underlying service layer adopts a server-client interaction model. The server provides service capabilities, and the client can access and obtain the services of the server.

[0158] The service management functional unit of the underlying service layer includes two parts of service structure and SSAP. The service structure presents various services in a structured and data form through a general expression format and framework, and the client obtains, understands and accesses the services provided by the server through the signaling and process defined by the SSAP.

[0159] In one example, the client can obtain the service structure of the server to obtain and understand the service types and functions provided by the server.

[0160] In another example, the client can also access the service by reading and writing attribute values. That is, the service of the server accessed by the client in the embodiments of the application can also be understood as the access operation of the client on the service of the server, and the access service or access operation can include but is not limited to reading or writing, which can be set according to actual needs, and the application is not limited.

[0161] In the embodiments of the application, in the process of service interaction between the client and the server, the client can send the SSAP signaling to the server, and the server should respond to all received SSAP signaling of the client. In the embodiments of the application, the server responding to the SSAP signaling of the client can be understood as the server responding to the received SSAP signaling and performing corresponding operations. For example, it can be a read operation or a write operation, and in some examples, it can also be a feedback response signaling corresponding to the SSAP signaling, which can be set according to actual needs, and the application is not limited.

[0162] For example, as described above, one electronic device (e.g., the first electronic device or the second electronic device in FIG. 1) can be both a client and a server. For example, a notebook computer connects to a mobile phone to access the Internet through the StarFlash wireless communication system, in which case the mobile phone is a server and the notebook computer is a client; meanwhile, the mobile phone also connects to a headset to play music through the StarFlash wireless communication system, in which case the mobile phone is a client and the headset is a server.

[0163] Optionally, one server can support access by multiple clients. The service structure on the server is consistent for all clients. For example, one printer can provide services for multiple notebook computers through the StarFlash wireless communication system, in which case the service structure on the printer is consistent for all the notebook computers.

[0164] In the embodiments of the present application, when multiple service management transmission channels are available, the selection of the transmission channel is the responsibility of the underlying application layer or other functional units of the underlying service layer, and one complete bidirectional interaction (the concept can be referred to below) can only be performed on the same transmission channel.

[0165] In the embodiments of the present application, as described above, after the service management functional unit of the server or the client receives a request from the underlying application layer or other functional units of the underlying service layer, it interacts with the opposite end through the SSAP, and the corresponding SSAP PDU is transmitted as data on the service management transmission channel. For example, the SSAP PDU consists of a message code, a message control code, and an attribute load. The data format (also referred to as the data structure) of the SSAP PDU is shown in Table 1:

[0166] Table 1

[0167] For example, the message code indicates the message category of the SSAP PDU, and the message list of the SSAP PDU includes but is not limited to six types, as shown in Table 2:

[0168] Table 2

[0169] For example, the way in which the client and the server interact through the SSAP can be divided into unidirectional interaction and bidirectional interaction. One complete unidirectional interaction includes two cases:

[0170] 1) a command from the client to the server;

[0171] 2) a notification from the server to the client.

[0172] One complete bidirectional interaction includes two cases:

[0173] 1) a request from the client to the server and a corresponding response from the server to the client;

[0174] 2) Indication from server to client and corresponding acknowledgement from client to server.

[0175] In SSAP, one bi-directional interaction shall be conducted on the same SSAP transport channel (may also be referred to as the StarFlash default transport channel). Optionally, if one SSAP protocol bi-directional interaction fails to complete within 30 seconds, the interaction shall be considered to have failed, and the underlying application layer or underlying service layer functional unit shall be notified of the failure result. The SSAP PDUs of this failed interaction shall be discarded. If the SSAP transport channel is suddenly disconnected during the SSAP protocol bi-directional interaction, the interaction shall be considered to have terminated, and the attribute values being changed by the server during the interaction shall be considered to be in an indeterminate state, which shall be handled by the underlying application layer or underlying service layer functional unit.

[0176] 6. SSAP instruction set

[0177] Table 3 is an exemplary SSAP instruction set, please refer to Table 3:

[0178] Table 3

[0179] In the embodiments of the present application, one complete bi-directional interaction can also be referred to as a transaction.

[0180] In the existing SSAP protocol, the transmission control rules of a single transaction are as follows: the bi-directional interaction shall use an ordered question and answer mode, such as first request and then response or first indication and then acknowledgement. That is, before receiving the corresponding response or acknowledgement, it shall not be repeated. Specifically, the following cases are included:

[0181] a) First request and then response: after the client sends a request to the server, it cannot continue to send other requests to the same server on the same transport channel before receiving the response.

[0182] b) First indication and then acknowledgement: the server cannot continue to send other indications to the same client on the same transport channel before receiving the acknowledgement. However, the client can send commands and requests before sending the acknowledgement.

[0183] For example, the flow control of the request-response and indication-acknowledgement of the SSAP bi-directional interaction is independent and does not affect each other. For example, it is possible that a client receives an indication from a server and sends a request to the server before replying to the indication. That is, the same direction transaction can only exist in a unique process, and different direction transactions do not affect each other.

[0184] For example, one-way interaction (non-transaction) is without flow control, the client can send commands at any time, and the server can send notifications at any time. That is, one-way interaction can still be carried out during two-way interaction, and the flow control of two-way interaction does not affect one-way interaction, which is described as follows:

[0185] a) It is possible that a server receives a request, sends one or more server notifications, and then sends a response to the original request. The flow control of the request is not affected by the server notifications.

[0186] b) It is possible that a server receives a request and then receives a command before responding to the request. The flow control of the request is not affected by the transmission of the command.

[0187] c) It is possible that a server sends a notification after sending an indication and before receiving an acknowledgement.

[0188] d) It is possible that a client receives an indication from a server and sends a command to the server before responding to the indication.

[0189] Therefore, as described above, in the existing SSAP protocol, all SSAP signaling is transmitted through a service management transmission channel defined in the transmission and control protocol, which can also be referred to as a default channel. When there are multiple method invocations for request-response type transactions, other request-response type transactions are blocked, i.e., other applications running on the device can be blocked. When multiple applications are running on the device, it can cause a decrease in application data interaction efficiency.

[0190] To solve the message blocking problem in the prior art, the low-power Bluetooth technology in the prior art uses a multi-channel transmission mode, i.e., transactions of the same type are transmitted through different channels to avoid the problem of message blocking on the same channel. However, this method needs to establish multiple independent transmission channels, and the establishment and destruction process of independent transmission channels will cause resource waste and increase management difficulty.

[0191] FIG. 8 is a schematic diagram of a service interaction flow in the prior art, as shown in FIG. 8, the SSAP communicates on the default transport channel established between the client and the server. The SLB service management transport channel has a transport channel identifier (TCID) of 0x0009, the SLB relay service management transport channel has a TCID of 0x0010, and the SLE service management transport channel has a TCID of 0x000A. All the transport channels use the underlying transport mode. As shown in FIG. 8, the first application of the client accesses the first service of the server using the SLB transport channel, and the first application of the client accesses the first service of the server is taken as an example for description. Specifically, the first application interacts with the service management to request access to the first service of the server. The service management of the client and the service management of the server can perform control signaling interaction (also referred to as service interaction) through the control plane transport channel of the SLB, so that the service management of the client sends an access request signaling (for example, an SSAP_READ_REQ) to the service management of the server. In addition, the client can receive response information (for example, an SSAP_READ_RSP) fed back by the service management of the server.

[0192] As shown in FIG. 8, in the prior art, the service management functional unit of the client will send the received indication or notification to all the applications in the underlying application layer in response to the indication or notification sent by the server and received from the default transport channel (for example, 0x09), and the application side judges whether it needs to process according to the specific content of the indication or notification. This interlayer interaction mode will waste the interlayer interface resources, and may affect the system throughput in the case of a large amount of data.

[0193] To solve the above problems, the application provides a service interaction method, which can realize the directional interaction between the application of the client and the service of the server. In addition, transaction concurrency can be realized to avoid the problem of message blocking.

[0194] In the embodiments of the application, the service management functional unit (also referred to as a module or a unit, which is not limited in the application) configures a corresponding port number for the application or the service of the application. For example, the service management functional unit of the client configures a port number for the application, which can be referred to as a control plane port number of the application, a client port number of the application, or a service management port number of the application. For example, the service management functional unit of the server configures a port number for the service of the application, which can be referred to as a service port number, a control plane port number of the service, or a service management port number of the service.

[0195] In the process of performing service access (may also be referred to as service configuration) based on the SSAP protocol between the service management function unit of the client and the service management function unit of the server, in one example, the service management function unit of the client can send signaling to the specified service based on the port number of each service of the server. In another example, the service management function unit of the server can send signaling to the specified application based on the port number of each application of the client. Thus, the directivity interaction between the application and the service can be further implemented through the port number. In addition, the traffic isolation between the client and the server can be implemented based on the port number to realize the concurrency of the same direction transaction between the client and the server, so as to improve the efficiency of the service access process.

[0196] The service interaction method of the present application can be divided into three parts. The first part is the configuration of the port of the application and the service of the local end. The second part is the acquisition of the port of the application and the service of the opposite end. The third part is the interaction based on the port number of the application and the service.

[0197] It should be noted that, unless otherwise specified, the port number of the application, the port of the application, the port of the service, and the port number of the service described in the embodiments of the present application all refer to the port number of the control plane. Correspondingly, the port (number) of the application can also be referred to as the control plane port (number) of the application, or the service management port (number) of the application. The port (number) of the service can also be referred to as the control plane port (number) of the service, or the service management port (number) of the service. The present application does not limit this, and the following will not be repeated.

[0198] The above three parts will be described in detail as follows:

[0199] The first part is the configuration of the port of the application or the service of the local end.

[0200] For example, as described above, the electronic device can be a client or a server. The local end can refer to the local end of the electronic device, and of course can also refer to the client or the server. When the electronic device is a client, it acquires the port of the application of the local end. When the electronic device is a server, it acquires the port of the service of the application of the local end.

[0201] The port configuration of the application of the client and the port configuration of the service of the server will be described as follows.

[0202] 1. Configuration of the port of the application of the client.

[0203] For example, each application in the client registers with the service management function unit (referring to the service management unit of the client, which will not be repeated here),

[0204] The service management function unit of the client assigns a port number to the application during the registration process or after the registration is completed. The port number can be referred to as a control plane port number of the application or a client port number of the application, which is not limited in the application.

[0205] FIG. 9 is a schematic diagram of port number configuration of a star flash communication system, as an example. Referring to FIG. 9, the client includes but is not limited to a first application and a second application. The first application in the server includes a first service and a second service, and the second application includes a third service. In an example, the client assigns a client port number to each application, which can be the same as the data plane port number of the application. Alternatively, the data plane ports of each application are different, and accordingly, the client port numbers of each application are also different.

[0206] For example, as shown in FIG. 9, port-1 is a client port of the first application, and port-2 is a data plane port of the first application. Alternatively, the port numbers of port-1 and port-2 are the same, for example, both are 0x01, which can be set according to actual needs, and the application is not limited. That is, for the star flash transport layer, port-1 and port-2 are actually the same logical port.

[0207] In another example, the client assigns a client port number to each application, which can be different from the data plane port number of the application. Alternatively, the client port numbers of each application can be different. For example, as shown in FIG. 9, port-1 is a client port of the first application, and port-2 is a data plane port of the first application. Alternatively, the port numbers of port-1 and port-2 are the same, for example, port-1 is 0x01, and port-2 is 0x02. That is, port-1 and port-2 are different logical ports.

[0208] In the embodiment of the application, as shown in FIG. 9, the service management function unit of the client is configured with a port and a port number, which can be referred to as a client port number of the service management function unit or a control plane port number, which is not limited in the application. In the embodiment of the application, when the service management function unit configures a port number for the application, the port numbers of the applications are different from the port number of the service management function unit.

[0209] That is, in the embodiment of the application, the configuration rules of the port numbers of the applications of the client include but are not limited to:

[0210] 1) The client port number of the application is the same as the data plane port number of the application, and is different from the port number of the service management function unit.

[0211] 2) The client port number of the application is different from the data plane port number of the application, the client port numbers of the applications are different, and are different from the port number of the service management function unit.

[0212] In a possible implementation, the service management function unit of the client can maintain a local port list, and the local port list can record the correspondence between the application and the port, for example, the correspondence between the identification information of the application and the port number. Of course, in some instances, the service management function unit can also maintain the correspondence between the application and the port in other forms, and the list form described in the embodiments of the present application is only an illustrative example, which is not limited in the present application.

[0213] 2. Port configuration of the service of the server

[0214] For example, as shown in FIG. 9, the service management function unit of the server configures the port number for each service of the application. For example, the service management function unit configures port-3 (for example, the first service port described in the embodiments of the present application) for the first service of the first application, configures port-4 (which can also be referred to as the second service port) for the second service of the first application, and configures port-5 for the third service of the second application. Each port can be understood as a port allocated by the service management for the service (which can also be referred to as a service port), which is configured with a corresponding port number.

[0215] For example, the service management function unit of the server provides the function units of the underlying application layer and the underlying service layer with the service registration and deletion functions. After the corresponding registration service is completed, the server generates a service structure of the registration service, and the description of the service structure can be referred to the above, which will not be described herein again.

[0216] For example, after the registration of each service is completed, the service management function unit can obtain the concurrency requirement of each application. In the embodiments of the present application, the concurrency requirement of the application can indicate whether the application needs concurrency, or whether the services in the application need concurrency.

[0217] For example, the service management function unit can configure the port number for the services of each application based on the concurrency requirement of each application. Specifically, the service management function unit can determine the concurrency granularity corresponding to the application based on the concurrency requirement of each application, and configure the port number for the services of the application based on the concurrency granularity of the application.

[0218] In the embodiments of the present application, the concurrency granularity can include the application granularity and the service granularity.

[0219] In one example, if the concurrency requirement of the application indicates the application granularity as the concurrency granularity, the port numbers of the services in the application can be the same, and the port numbers of the services of the application are different from the port numbers of the services of other applications. For example, the port number of the first service of the first application is the same as the port numbers of the other services in the first application, and the port numbers of the services of the first application are different from the port numbers of the services of other applications.

[0220] In the embodiments of the present application, the concurrent granularity is application granularity, and the concurrent can be implemented by the same direction transaction (referring to the bidirectional interaction transaction, the concept can be referred to the above) between the services of different applications.

[0221] For example, the port numbers of the first service and the second service of the first application are the same, for example, the port-3 and the port-4 in FIG. 9 are 0x01, and the port number of the port-5 of the third service of the second application is 0x02. The port numbers of the port-3 and the port-4 are the same, and can also be understood as the same logical port. That is, for the service management function unit, the port number 0x02 is associated with the first service and the second service. The service management function unit can interact with the first service and the second service through the port with the port number 0x02 (which can be understood as the port-3 or the port-4). In this example, the first application and the second application are concurrent in the application granularity, that is, the port numbers of the services in the first application are the same in the service interaction process, and therefore, there is only one transaction for the same direction of the services of the first application in the transmission channel between the client and the server. For example, after the first service of the server sends the indication signaling to the client, the other services of the first application cannot send the indication signaling before the confirmation signaling of the indication signaling is received. However, the third service of the second application can send the indication signaling to the client before the response signaling of the indication signaling is received by the server. For another example, the first application of the client sends the request signaling to the first service, and the first application of the client cannot send the request signaling to the other services of the first application again before the response signaling of the request signaling is received by the client. However, the second application of the client can send the request signaling to the third service of the second application.

[0222] In another example, if the concurrent requirement of the application indicates that the concurrent granularity is service granularity, the port numbers of the services of the application are different, including completely different or not completely different. In addition, the port numbers of the services of the application are different from the port numbers of the services of other applications. For example, the port number of the first service of the first application is different from the port numbers of the other services of the first application, and the port number of the first service is also different from the port numbers of the services of other applications. For another example, the port number of the first service of the first application is the same as the port numbers of the part of the services (at least one service) of the first application, and the port number of the first service is different from the port numbers of the services of other applications.

[0223] In the embodiments of the present application, the concurrent granularity is service granularity, and the concurrent can be implemented by the same direction transaction (referring to the bidirectional interaction transaction, the concept can be referred to the above) between the services of different applications.

[0224] For example, the port number of port-3 of the first service of the first application and the port number of port-4 of the second service are different, which are 0x01 and 0x02 respectively, and the port number of port-5 of the third service of the second application is 0x03. In this example, the first application and the second application are concurrent at the service granularity, that is, the port numbers of the services of the first application are different, and the port numbers of the services of the second application are also different. Therefore, in the service interaction process, the transactions of the same direction of the services of the first application and the second application in the transmission channel between the client and the server can be concurrent at the service granularity. For example, after the first service of the server sends an indication signaling to the client, before the response signaling of the indication signaling is received, other services of the first application of the server can also send an indication signaling to the first application of the client. The port number of the third service of the second application is different from the port number of the first service of the first application, and therefore, before the confirmation signaling of the indication signaling is received by the server, the third service of the second application of the server can also send an indication signaling to the client. For another example, the first application of the client sends a request signaling to the first service of the server, and before the response signaling of the request signaling is received, the first application of the client can send a request signaling to other services of the first application of the server. Similarly, before the response signaling of the request signaling is received, the second application of the client can send a request signaling to the third service of the second application.

[0225] In yet another example, if the concurrent requirement of an application indicates that the application does not need to be concurrent, the port numbers of the services of the application are the same, and the port number of the application can be the same as the port numbers of other applications that do not need to be concurrent. The specific port numbers can be set according to actual needs, which are not limited in the present application.

[0226] In a possible implementation, there can be at least one application whose concurrent requirement is at the application granularity, at least one application whose concurrent requirement is at the service granularity, and / or at least one application whose concurrent requirement is non-concurrent in the server, which are not limited in the present application. For example, the concurrent granularity of the first application is at the application granularity, the concurrent granularity of the second application is at the service granularity, the concurrent granularity of the third application is at the application granularity, and the concurrent requirement of the fourth application and the fifth application is non-concurrent. In this example, the port numbers of the services of the first application, the second application and the third application allocated by the service management functional unit are A, B and C respectively, and the port numbers of the services of the fourth application and the fifth application are D. The names and the number of the port numbers, the services and the applications involved in the embodiments of the present application are only illustrative examples, which are not limited in the present application.

[0227] Optionally, the port number configured by the service management for the service can be selected from a first port pool, and any port number in the first port pool is different from the port number of the data plane of the application. It can be understood that the port number of the data plane of the application belongs to a second port number pool, and the port numbers in the first port pool and the second port number pool are completely different.

[0228] In the embodiment of the present application, as shown in FIG. 9, the service management function unit of the service end is configured with a port and a port number thereof, which can be referred to as a service management function unit port number, or a control plane port number, which is not limited in the present application. In the embodiment of the present application, when the service management function unit configures a port number for the application, the port number of each application needs to be different from the port number of the service management function unit.

[0229] In the embodiment of the present application, as shown in FIG. 7, the application (referring to one or more applications, which will not be repeated hereinafter) registers the service to the service management function unit, and the service management function unit can obtain the service structure of the service (referring to one or more services, which will not be repeated hereinafter) of the application. As shown in FIG. 4, the service structure defines that the service is composed of service structure members including service declaration, service reference, attribute, method, event, and the way of their composition; the service structure also defines the reference and logical relationship between services; the service structure structures the above-mentioned content and data by defining the expression format and access method of the service structure members. Among them, the service declaration must exist.

[0230] For example, as shown in FIG. 5, the entries of the service declaration of each service include but are not limited to: handle, category, identification, data, permission, additional information and the like. Among them, the data field includes but is not limited to: operation indication, data value and descriptor. In the embodiment of the present application, the service management function unit can configure one or more values of the descriptor, and the value of the descriptor is used to indicate the port number of the service declared by the service declaration.

[0231] Second part, the application of the end and the acquisition of the port of the service.

[0232] For example, the client acquires the port number of the service (referring to one or more services) of the service end. The service end acquires the port number of the application (referring to one or more applications) of the client.

[0233] The following will describe in detail the acquisition method of the client for the port number of the service of the service end, and the acquisition method of the service end for the port number of the application of the client.

[0234] 1. The client acquires the port number of the service of the service end.

[0235] In the embodiment of the present application, the acquisition method of the client for the port number of the service of the service end includes but is not limited to the following two methods:

[0236] Way one:

[0237] The client obtains the port number of the service of the server through service discovery.

[0238] Specifically, the service discovery interaction signaling supports service structure or hierarchical discovery mechanism. For example, the client (for example, a service management functional unit in the client) sends SSAP_FIND_STRUCTURE_REQ signaling (which can be referred to as SSAP service discovery request signaling) to the server, to send a request of discovering service structure from the client to the server.

[0239] The client can use various search types through the PDU, such as the entire service structure, the primary service, the referenced service, and the like. The service structure discovery mechanism can directly discover the entire service structure of the server through one request. The hierarchical discovery mechanism refers to that the primary service, the referenced service, the attribute, the method, the event, and the like can be discovered step by step through multiple requests according to the service structure hierarchy.

[0240] The SSAP_FIND_STRUCTURE_REQ PDU is composed of four parameters, message code, message control code, start handle, and end handle:

[0241] The message code parameter value is set to 0x04;

[0242] The message control code parameter value is set to different values in a bitmap manner, wherein bit6-bit7 are reserved values.

[0243] The value of the start handle is set to the start handle of the search;

[0244] The value of the end handle is set to the end handle of the search; the start handle value should be less than or equal to the end handle value. The service information handle value that the client wants to obtain should be set between the start handle value and the end handle value.

[0245] The request PDU supports one-time query of the entire service structure on the entire server or hierarchical query of one or more service structure members meeting the conditions.

[0246] For example, the server sends SSAP_FIND_STRUCTURE_RSP (which can also be referred to as SSAP service discovery response signaling) to the client in response to the received SSAP_FIND_STRUCTURE_REQ signaling, to feed back the service structure of the server. Specifically, the SSAP_FIND_STRUCTURE_RSP PDU is used to send the corresponding response (supporting packet sending) from the server to the client after receiving the SSAP_FIND_STRUCTURE_REQ PDU request.

[0247] The SSAP_FIND_STRUCTURE_RSP PDU is composed of three parameters, a message code, a message control code, and a data list.

[0248] The message code parameter value is set to 0x05;

[0249] The message control code parameter value is set to the data packet state of the message using bits 1-bit 0, and other bits are reserved;

[0250] The data list is set to different values according to different service structure searches;

[0251] If the client sends the SSAP_FIND_STRUCTURE_REQ PDU indicating that the search is for a certain type of service structure member, the server should return information about all service structure members of the specified handle range to the client.

[0252] For example, after the client obtains the service structure of the server, the client sends the SSAP_READ_REQ signaling (also referred to as the SSAP read signaling) to the server, which is used to send the request information of the client to the server. That is, after the client obtains the service structure, the client can further send the SSAP_READ_REQ signaling to request to read the data information of one or more entries.

[0253] For example, the server sends the SSAP_READ_RSP signaling (also referred to as the SSAP read response signaling) to the client in response to the received SSAP_READ_REQ signaling, which is used to feed back the data information of one or more entries requested by the client. The SSAP_READ_RSP PDU is used for the server to send the response of reading to the client after receiving the reading request, and multiple entry data can be returned in the same response (supporting packet sending).

[0254] Specifically, in the embodiment of the present application, after the client obtains the service structure, the client can further read the data information of the entries of the service declaration by sending the SSAP_READ_REQ signaling, wherein, as described above, the value of the descriptor in the entry of the service declaration is used to indicate the port number of the service. Correspondingly, the client can send the SSAP_READ_REQ signaling to obtain the port number of the service. The server sends the SSAP_READ_RSP signaling to the client in response to the received SAP_READ_REQ signaling, wherein the SSAP_READ_RSP PDU includes but is not limited to the value of the descriptor of the entry of the service declaration.

[0255] For example, the client reads the value of the descriptor from the SSAP_READ_RSP PDU to obtain the port number of the service in response to the received SSAP_READ_RSP.

[0256] FIG. 10 is a schematic diagram of the format of signaling, please refer to FIG. 10, the present application relates to two message formats, in order to distinguish between different message formats, the message format shown in FIG. 10 is recorded as the first message format, the first message format includes but is not limited to: access layer control field, transmission and control field, and data field. Among them, the access layer control field includes but is not limited to some control information of access layer (also can be called star flash access layer), the transmission and control field includes but is not limited to some control information of basic service layer, the data field carries SSAP PDU. Optionally, the related signaling of service discovery and reading in the embodiment of the present application can use the first message format. For example, SSAP_FIND_STRUCTURE_RSP signaling adopts the first message format, and the data field thereof includes SSAP_FIND_STRUCTURE_RSP PDU. SSAP_FIND_STRUCTURE_RSP signaling adopts the first message format, and the data field thereof includes SSAP_FIND_STRUCTURE_RSP PDU. SSAP_READ_REQ signaling adopts the first message format, and the data field thereof includes SSAP_READ_REQ PDU. SSAP_READ_RSP signaling adopts the first message format, and the data field thereof includes SSAP_READ_RSP PDU. Of course, some interactive signaling not involved in the present application can also adopt the first message format, which is not limited by the present application.

[0257] Mode two:

[0258] The client obtains the port number of the service of the server through the signaling interaction of the service management function unit.

[0259] Specifically, the service management function unit of the client sends a first target signaling to the server, and the first target signaling is used to request the port number of the service of the server and indicate the port number of the application (one or more applications) of the client to the server.

[0260] Optionally, the first target signaling can be an existing signaling in table 3, or a new signaling, which is not limited by the present application. The format of the first target signaling can be the first message format, which is not limited by the present application.

[0261] Exemplarily, the SSAP PDU in the data field in the first target signaling includes, but is not limited to, the identification information of one or more applications and the corresponding client port numbers. Optionally, the identification information of the application can be a Universally Unique Identifier (UUID) of the application.

[0262] The service management functional unit of the server receives the first target signaling. The service management functional unit obtains the port numbers of the applications of the client. In response to the received first target signaling, the service management functional unit sends a first target response signaling to the client. The first target response signaling includes, but is not limited to, the identification information of the services of the applications and the corresponding port numbers of each service. Optionally, the identification information of the service can be a UUID of the service.

[0263] The client receives the first target response signaling and obtains the port numbers of the services of the server.

[0264] In a possible implementation, the service management functional unit of the client can maintain a peer port list, where different servers can correspond to different peer port lists. The peer port list can record the correspondence between the services of the server and the port numbers, for example, the correspondence between the identification information of the service and the port number. Of course, in some examples, the service management functional unit can also maintain the correspondence between the service and the port in other forms. The list form described in the embodiments of the present application is only an illustrative example, and the present application is not limited thereto.

[0265] 2. The server obtains the port numbers of the applications of the client.

[0266] In the embodiments of the present application, the manner in which the client obtains the port numbers of the services of the server includes, but is not limited to, the following three manners:

[0267] Manner one:

[0268] The server obtains the port numbers of the applications of the client by learning.

[0269] FIG. 11 is a flowchart illustrating the manner in which the server obtains the port numbers of the applications, and FIG. 13 is a flowchart illustrating the manner in which the client obtains the port numbers of the applications. The specific implementation process of the server will be described below with reference to FIG. 11, and the specific implementation process of the client will be described below with reference to FIG. 13.

[0270] S1101, the client obtains the port numbers of the services of the server.

[0271] Specifically, the client obtains the port numbers of the services of the server by manner one, i.e., the descriptor reading manner. The specific manner can refer to the manner one on the client side, which will not be described herein again.

[0272] S1102, the client sends a service interaction signaling to the server.

[0273] Specifically, after the client obtains the port number of the service of the server by the first mode, i.e., the mode of reading the descriptor, the client can send a signaling to the server, for example, a service management signaling or a service interaction signaling in the embodiments of the present application, which is not limited in the present application. The service interaction signaling can be the signaling sent by the client in Table 3, for example, the SSAP_READ_REQ in Table 3, which is not limited in the present application.

[0274] For example, the service interaction signaling includes but is not limited to a source port number and a destination port number. The source port number is the port number of the application of the client (i.e., the client port number), and the destination port number is the port number of the service of the server. The port number of the service of the server is obtained by the client by reading the value of the descriptor of the service, and the specific obtaining mode can refer to the first mode described above, which is not described herein again.

[0275] FIG. 12 is a schematic diagram of the format of the signaling, please refer to FIG. 12. The present application involves two message formats. In order to distinguish the different message formats, the message format shown in FIG. 12 is recorded as the second message format. The second message format includes but is not limited to an access layer control field, a transmission and control field, a transmission layer control field and a data field. The access layer control field includes but is not limited to some control information of the access layer (also referred to as the StarFlash access layer), the transmission and control field includes but is not limited to some control information of the basic service layer, the transmission layer control field is encapsulated by the StarFlash transmission layer shown in FIG. 9, and includes but is not limited to the source port number and the destination port number and other information, and the data field carries the SSAP PDU. In the embodiments of the present application, the StarFlash transmission layer supports the Non-IP protocol (or data transmission).

[0276] FIG. 13 is a schematic diagram of the format of the transmission layer control field, please refer to FIG. 13. The transmission layer control field includes but is not limited to the following fields: a protocol version number, an optional field length, a source port number, a destination port number, a data payload, an optional field bitmap, an optional field, a padding field, etc. The optional field bitmap, the optional field and the padding field are optional fields in the message. The source port number field and the destination port number field respectively include the fields corresponding to the low byte and the high byte. The data payload field (i.e., the data field in FIG. 10) carries the SSAP PDU.

[0277] The source port number is used to indicate the sending end of the message (i.e., signaling), and the destination port number is used to indicate the receiving end of the message. Taking the first application of the client accessing the first service of the server as an example, the first application in the client is the sending end, and the first service of the server is the receiving end. Correspondingly, the source port number in the transport layer control field of the message is the port number of the first application, and the destination port number is the port number of the first service.

[0278] Optionally, the second message format can also be understood as a message format in a connectionless transmission mode, i.e., without the need for handshaking at the transport layer, the sending end and the receiving end of the message are indicated by the source port number and the destination port number, so that the sending end can communicate with the receiving end. That is, in the embodiment of the present application, after the client obtains the port number of the service of the server, the signaling when it interacts with the server can use the second message format.

[0279] In a possible implementation, the second message format can also be used when the client discovers the service of the server. In this scenario, since the client has not obtained the port number of the service of the server, the client can use the port number of the service management function unit of the server as the destination port number to send the service discovery related signaling to the server.

[0280] In S1103, the server learns the port number of the application.

[0281] For example, when the server receives the service interaction signaling sent by the client, it can learn the port number of the application in the source port number field based on the source port number in the service interaction signaling.

[0282] The following illustrates the learning mode of the port number of the first application:

[0283] FIG. 14 is a schematic diagram of service interaction, which is exemplarily shown. Referring to FIG. 14, the first application of the client requests to access the first service of the server, for example, requests to access the operation of writing data. The access operation in the embodiments of the present application can include, but is not limited to, reading, writing, method calling, etc., or notification or indication, which is not limited by the present application. Exemplarily, the service management functional unit generates the SSAP PDU (for example, SSAP_WRITE_REQ PDU) in response to the request of the first application to access the first service. The service management functional unit searches for the port number corresponding to the first application from the local port list, and searches for the port number corresponding to the first service from the peer port list. The service management functional unit transmits the SSAP PDU, the port number of the first application and the port number of the first service to the StarFlash transport layer through the interface with the StarFlash transport layer. The StarFlash transport layer encapsulates the SSAP PDU to obtain the encapsulated transport layer packet, wherein the transport layer includes, but is not limited to, a transport layer control field and a data field. The data field includes, but is not limited to, the SSAP PDU. The transport layer control field includes, but is not limited to, the source port number (i.e., the port number of the first application) and the destination port number (i.e., the port number of the first service) and other fields, and the description of the other fields can be referred to FIG. 13, which will not be described herein.

[0284] Exemplarily, the other units or modules of the base service layer and the access layer continue to encapsulate the transport layer packet to obtain the encapsulated SSAP signaling, for example, SSAP_WRITE_REQ signaling, and the format of the SSAP signaling is shown in FIG. 11, which will not be described herein. The access layer of the client sends the SSAP signaling to the server through the transmission channel.

[0285] In a possible implementation, after the service management functional unit of the client obtains the port numbers of the applications of the local end and the port numbers of the services of the server, the service management functional unit can indicate the port numbers of the applications and the port numbers of the services to the StarFlash transport layer, so that the StarFlash transport layer identifies that the received packet is needed to be transmitted to the service management for further processing based on the obtained port numbers. For example, after the StarFlash transport layer of the client receives the packet carrying the destination port number of the port number of the first application and the source port number of the port number of the first service, the StarFlash transport layer can identify that the packet is a control plane packet and needs to be transmitted to the service management for further processing based on the source port number and the destination port number.

[0286] Still referring to FIG. 14, exemplarily, the server receives the SSAP signaling (for example, SSAP_WRITE_REQ signaling), and the access layer and the base service layer of the server decapsulate the signaling to obtain the transport layer packet (i.e., including the transport layer control field and the data field). The StarFlash transport layer obtains the transport layer packet.

[0287] In a possible implementation, after the service management function unit of the service end acquires the port numbers of the services of the local end, the service management function unit can indicate the port numbers of the services of the local end to the StarFlash transport layer. In this way, the StarFlash transport layer can identify, based on the acquired port numbers of the services, that the received message is a message that needs to be transmitted to the service management for further processing.

[0288] Specifically, the StarFlash transport layer can determine, based on the destination port number (for example, the port number of the first service) in the message, that the message is a message that needs to be processed by the service management function unit of the control plane. The StarFlash transport layer performs decapsulation on the transport layer message to obtain the SSAP PDU.

[0289] For example, the StarFlash transport layer can transmit the port number of the first application, the port number of the first service, and the SSAP PDU in the message to the service management function unit. For example, the service management function unit can determine that the port number of the first service corresponds to the first service by traversing the values of the descriptors of the services. That is, the service management function unit can determine that the current access operation is an access operation on the first service.

[0290] In one example, if the service management function unit performs table lookup based on the port number of the first application and does not find an application corresponding to the port number, the service management function unit can determine that the port number of the first application has not been acquired. The service management function unit can record the correspondence between the identification information of the first application and the port number of the first application, for example, can write the correspondence into the peer port number list, thereby completing learning of the port number of the first application. In the embodiments of the present application, only the learning process of the port number of the first application is taken as an example for description, and the learning process of the port numbers of other applications of the client by the service end can refer to the learning process of the first application, and the present application will not be described one by one. For example, the service management function unit can perform a corresponding operation on the first service, for example, perform a write operation on the first service based on the SSAP_WRITE_REQ PDU.

[0291] In another example, if the service management function unit performs table lookup based on the port number of the first application and finds an application corresponding to the port number, that is, the first application, that is, the service management function unit has acquired the port number of the first application. For example, the service management function unit can determine that the SSAP PDU is used to indicate an access operation of the first application on the first service, and the SSAP PDU contains access information of the first application on the first service. The service management function unit can perform a corresponding operation on the first service, for example, perform a write operation on the first service based on the SSAP_WRITE_REQ PDU.

[0292] Method two:

[0293] The service end acquires the port numbers of the applications of the client through application layer interaction signaling.

[0294] FIG. 15 is a flowchart illustrating an example of a service end obtaining a port number of an application. Referring to FIG. 15, the method includes the following steps, but is not limited to the following steps:

[0295] S1501, the client obtains a port number of a service of the service end.

[0296] Specifically, the client obtains the port number of the service of the service end by a first method, i.e., a descriptor reading method. The specific method can refer to the first method on the client side, which will not be described here.

[0297] S1502, the client sends an application interaction signaling to the service end.

[0298] For example, the application of the client can send an application interaction signaling to the service of the client, which can also be referred to as an application configuration signaling, or a second target signaling in the embodiment of the present application. Optionally, the format of the application interaction instruction can be a first message format. The data field can include, but is not limited to, the identification information of the application and the port number of the application. In one example, as described above, the data plane port number of the application can be different from the client port number. In this example, the port number of the application can include the data plane port number of the application and the client port number. In another example, the data plane port number of the application is the same as the client port number of the application. Accordingly, the port number of the application in the data field can be the client port number of the application, or can be understood as the data plane port number of the application.

[0299] S1503, the service end obtains a port number of an application.

[0300] For example, after the service management functional unit of the service end obtains the application interaction signaling, the identification information of the application and the port number of the application carried in the data field of the signaling can be obtained. The service management functional unit records the correspondence between the application (e.g., the first application) and the port number (e.g., the port number of the first application).

[0301] In this example, the identification information of the application and the port number of the application carried in the application interaction signaling are the port number of the application and the identification information of the application that initiate the signaling. For example, the application interaction signaling sent by the first application includes the port number of the first application and the identification information of the first application.

[0302] In a possible implementation, before obtaining the port number of the application of the client, if the service management receives an application with a source port number that is not the obtained port number, the service management functional unit can send a denial of access indication information to the client to deny the application to access the service of the service end this time. Specifically, the service end can send an SSAP_ERROR_RSP signaling to the client, and indicate the denial of the application access through an error code in the SSAP_ERROR_RSP signaling.

[0303] In another possible implementation, after obtaining the port number of the application of the client, the service management functional unit can also indicate the denial of the access of the specified application to the client through the SSAP_ERROR_RSP signaling.

[0304] Optionally, the service end can send an application interaction response signaling to the client in response to the application interaction signaling.

[0305] Mode three:

[0306] The service end obtains the port number of the application of the client through the signaling interaction of the service management functional unit.

[0307] The mode can refer to mode two on the client side, which will not be described here.

[0308] In a possible implementation, the service management functional unit of the service end can maintain a list of peer port numbers, recording the correspondence between the application of the client and the port number.

[0309] Third part, based on the interaction of the port of the application and the port number of the service.

[0310] In the embodiment of the application, the client and the service end can perform service interaction (which can also be referred to as service access, which is not limited in the application) based on the port number of the application and the port number of the service. The service interaction can be one-way interaction or two-way interaction.

[0311] Specifically, the service interaction mode of the client and the service end can be divided into one-way interaction and two-way interaction. Once complete one-way interaction includes two cases:

[0312] 1) From the client to the service end command, that is, the client sends a command signaling to the service end.

[0313] 2) From the service end to the client notification, that is, the service end sends a notification signaling to the client.

[0314] Once complete two-way interaction includes two cases:

[0315] 1) Request from client to server and corresponding response from server to client. That is, the client sends a request signaling to the server, and the server feeds back a corresponding response signaling in response to the request signaling.

[0316] 2) Indication from server to client and corresponding acknowledgement from client to server. That is, the server sends an indication signaling to the client, and the client feeds back a corresponding acknowledgement signaling in response to the indication signaling.

[0317] In the embodiments of the present application, one complete bidirectional interaction can also be referred to as one transaction. One bidirectional interaction should be conducted on the same SSAP transmission channel.

[0318] In the embodiments of the present application, the bidirectional interaction can use an unordered question and answer mode, that is, before receiving the corresponding response or acknowledgement, the same transmission channel can be used to repeatedly send. Specifically, the following cases are included:

[0319] a) After the client sends a request to the server, before receiving the response, the same transmission channel can be used to continue to send other requests to the same server, which have different source port numbers and / or different destination port numbers from the request.

[0320] b) After the server sends an indication to the client, before receiving the acknowledgement, the same transmission channel can be used to continue to send other indications to the same client, which have different source port numbers and / or different destination port numbers from the indication.

[0321] In addition, in the embodiments of the present application, the same port number pair is used in one bidirectional interaction transaction (for example, request-response, indication-acknowledgement). For example, the source port number in the request signaling sent by the client to the server is the port number of the first application, and the destination port number is the port number of the first service. Correspondingly, the source port number in the response signaling fed back by the server in response to the request signaling is the port number of the first service, and the destination port number is the port number of the first application.

[0322] In the embodiments of the present application, the message format of the service interaction signaling in the service interaction process can be optionally the second message format. In this way, in the embodiments of the present application, the client can send signaling carrying a source port number and a destination port number to the server, wherein the source port number is the port number of the application, and the destination port number is the port number of the service. For example, the source port number can be the client port number of the first application, and the destination port number can be the first service port number. The first service port number can be optionally the port number of the first service in the service provided by the server. Correspondingly, the server sends signaling carrying a source port number and a destination port number to the server, wherein the source port number is the port number of the service, and the destination port number is the port number of the application. For example, the source port number can be the first service port number, and the destination port number can be the client port number of the first application.

[0323] In the embodiments of the present application, the client can identify, based on the destination port number of the received signaling, which application is the acceptance object of the signaling, and the client can upload the related information in the SSAP PDU in the signaling to the corresponding application, so as to realize the application layer directional reception of the client. Moreover, the client can specify the acceptance object, i.e., the service, through the destination port. Correspondingly, after receiving the signaling, the server can determine the service corresponding to the signaling based on the destination port number, and perform the corresponding access operation on the specified service, so as to realize the application layer directional reception of the server. In this way, in the embodiments of the present application, the client and the server can isolate the traffic of the same direction signaling based on the port number of the application or service, so that the same direction transaction can be concurrent.

[0324] In the embodiments of the present application, at least one of the source port number and the destination port number of the signaling is not the same, that is, the concurrency of the same direction transaction can be realized. For the client, in one example, after an application sends a request signaling to a service of the application, before receiving the response signaling corresponding to the request signaling, the application can also send a request signaling to other services of the application with different port numbers. In another example, after an application sends a request signaling to a service of the application, before receiving the response signaling corresponding to the request signaling, other applications can also send a request signaling to the corresponding service. For the server, in one example, after a service sends an indication signaling to the corresponding application, before receiving the corresponding confirmation signaling, other services of the application with different ports can send an indication signaling to the application. In another example, after a service sends an indication signaling to the corresponding application, before receiving the corresponding confirmation signaling, the services of other applications can send an indication signaling to the corresponding application. That is, on the transmission channel of the client and the server in the embodiments of the present application, multiple same direction transactions can exist.

[0325] Optionally, the transactions of different directions do not affect each other, that is, the request signaling sent by the client to the server does not affect the indication signaling sent by the server to the client. Conversely, the same. Specifically, the traffic control of the request-response and the indication-confirmation of the SSAP bidirectional interaction is independent and does not affect each other. For example, it is possible that a client sends a request to a server after receiving an indication from the server before replying to the indication.

[0326] Optionally, the unidirectional interaction between the client and the server is not subject to traffic control, specifically including:

[0327] a) It is possible that a server sends one or more server notifications after receiving a request, and then sends a response to the original request. The traffic control of the request is not affected by the server notification.

[0328] b) It is possible that a server receives a request and then receives a command before responding to the request. The flow control of the request is not affected by the transmission of the command.

[0329] c) It is possible that a server sends a server notification after sending an indication and before receiving an acknowledgement.

[0330] d) It is possible that a client sends a command to a server after receiving an indication from the server and before responding to the indication.

[0331] The following is described in detail with specific examples:

[0332] FIG. 16 is a schematic diagram of service interaction, as an example. Referring to FIG. 16, in this scenario, the concurrency requirement of the first application is application granularity. For example, the port numbers of the services of the first application are the same, for example, all are D. Moreover, the port numbers of the services of the first application are not the same as the port numbers of the services of the second application, for example, the port number of the third service of the second application is F. For example, the port number of the first application is A, and the port number of the second application is B.

[0333] In this example, the concurrency granularity of the first application and the second application is application granularity, that is, the same direction transactions between the first application and the second application can be concurrent, but the same direction transactions of the services in the first application cannot be concurrent.

[0334] For example, as shown in FIG. 16, the service management functional unit of the client sends the server SSAP_READ_REQ signaling in response to the read indication of the first application. Specifically, the service management unit generates the SSAP_READ_REQ PDU, and transmits the port number A of the first application and the port number D of the first service to the star flash transport layer. The star flash transport layer generates a transport layer control message, including a transport layer control field and a data field. The transport layer control field includes but is not limited to the source port number A of the first application and the destination port number D of the first service. The data field carries the SSAP_READ_REQ PDU. The access layer and other layer units or modules encapsulate the transport layer message to obtain the SSAP_READ_REQ signaling, and the signaling format is the second message format. The access layer of the client sends the SSAP_READ_REQ signaling to the server.

[0335] The service end receives the SSAP_READ_REQ signaling. The access layer and other layers of the modules or units parse the message (e.g., decapsulate), transmit the parsed message (i.e., the transport layer message) to the StarFlash transport layer. The StarFlash transport layer parses the transport layer message (e.g., decapsulate), obtains the SSAP_READ_REQ PDU, and determines, according to the destination port number (e.g., the port number D of the first service), that the data message corresponds to the service management functional unit. The StarFlash transport layer transmits the SSAP_READ_REQ PDU and the port number of the first application and the port number of the first service to the service management functional unit.

[0336] The service management functional unit of the service end can optionally determine whether the first application is allowed to access the first service based on the port number of the first application. For details, refer to the foregoing description, which will not be repeated here. If the service management functional unit determines that the first application can access the first service, the service management functional unit can perform corresponding operations on the first service based on the SSAP_READ_REQ PDU, such as reading data information.

[0337] The service end transmits the SSAP_READ_RSP signaling to the client in response to the SSAP_READ_REQ signaling. Specifically, the service management functional unit of the service end reads the data information and generates the SSAP_READ_RSP PDU, which includes but is not limited to the read data information. The service end generates the SSAP_READ_RSP signaling, which can be optionally in the second message format. The transport layer control field in the SSAP_READ_RSP signaling includes but is not limited to the source port number D of the first service and the destination port number A of the first application. For other interlayer processing steps, refer to the description of the client side, which will not be repeated here.

[0338] The client receives the SSAP_READ_RSP signaling. The access layer and other layers of the modules or units of the client parse the message (e.g., decapsulate), transmit the parsed message (i.e., the transport layer message) to the StarFlash transport layer. The StarFlash transport layer parses the transport layer message (e.g., decapsulate), obtains the SSAP_READ_RSP PDU. The StarFlash transport layer determines, according to the source port number (e.g., the port number D of the first service) and the destination port number (e.g., the port number A of the first application), that the message corresponds to the service management functional unit. The StarFlash transport layer transmits the SSAP_READ_RSP PDU and the port number of the first application and the port number of the first service to the service management functional unit. The service management functional unit feeds back the data information in the SSAP_READ_RSP PDU to the first application based on the destination port number.

[0339] In one example, as shown in FIG. 16, before the client receives the SSAP_READ_RSP signaling, i.e., before receiving the response signaling corresponding to the SSAP_READ_REQ signaling, if the first application indicates to the service management functional unit that it requests to access the second service, the service management functional unit determines that there already exists a transaction with the same source port number and destination port number on the current transmission channel based on the port number A of the first application and the port number D of the first service to be accessed by the first application. As described above, the source port number and the destination port number of the same direction transaction between the client and the server are not the same at least one of which to be concurrent, and it can also be understood that the same port number pair cannot be concurrent. Therefore, in this example, the service management functional unit determines that the access of the first application to the first service cannot be executed concurrently. That is, in this example, the SSAP_WRITE_REQ signaling for the first application cannot be sent in the case that there is no transaction with the destination port number of the first service and the source port number of the first application on the transmission channel. For example, after the client receives the response signaling corresponding to the SSAP_READ_REQ signaling, the client can send the SSAP_WRITE_REQ signaling with the source port number of the first application and the destination port number of the first service to the server.

[0340] In another example, as shown in FIG. 16, before the client receives the SSAP_READ_RSP signaling, i.e., before receiving the response signaling corresponding to the SSAP_READ_REQ signaling, if the second application indicates to the service management functional unit that it requests to access the third service, the service management functional unit determines that there is no transaction with the same source port number and destination port number on the current transmission channel based on the port number B of the second application and the port number F of the third service to be accessed by the second application. Correspondingly, the client can send the signaling corresponding to the access request of the second service to the server. Specifically, the client sends the SSAP_WRITE_REQ signaling to the server, and the source port number in the signaling is the port number B of the second application and the destination port number is the port number F of the third service. Exemplarily, the server feeds back the SSAP_WRITE_RSP signaling to the client in response to the SSAP_WRITE_REQ signaling. The other parts not described herein can refer to the above description and will not be described herein.

[0341] Exemplarily, as described above, the transactions in different directions do not affect each other. For example, as shown in FIG. 16, in the case that there is a transaction in the direction from the client to the server on the transmission channel between the client and the server, the server can send the SSAP_VALUE_IND signaling to the client. Correspondingly, the client can feed back the corresponding SSAP_VALUE_ACK signaling.

[0342] For example, as described above, the one-direction interaction is not affected by the bi-directional transaction, in the case where there is a bi-directional transaction in the transmission channel, the client can send a command to the server, and the server can send a notification to the client, which is not limited in the present application.

[0343] FIG. 17 is a schematic diagram of service interaction, for example, as shown in FIG. 17, in this scenario, the concurrent requirement of the first application is service granularity requirement. For example, the port number of each service of the first application is different, for example, the port number of the first service is D, and the port number of the second service is E. Moreover, the port number of each service of the first application is different from the port number of the service of the second application, for example, the port number of the third service of the second application is F. For example, the port number of the first application is A, and the port number of the second application is B.

[0344] In this example, the concurrent granularity of the first application and the second application is service granularity, that is, the same direction transaction between the first application and the second application can be concurrent, and the same direction transaction of each service in the first application can also be concurrent.

[0345] As shown in FIG. 17, the client sends the SSAP_READ_REQ signaling to the server, and the source port number in the signaling is the port number A of the first application, and the destination port number is the port number D of the first service. The server sends the SSAP_READ_RSP signaling to the client in response to the SSAP_READ_REQ signaling, and the source port number in the signaling is the port number D of the first service, and the destination port number is the port number A of the first application.

[0346] In this example, before the client receives the SSAP_READ_RSP signaling, the client can also send the SSAP_WRITE_REQ 1 signaling to the server. The source port number of the SSAP_WRITE_REQ 1 signaling is the port number A of the first application, and the destination port number is the port number E of the second service. The server sends the SSAP_WRITE_RSP 1 signaling to the client in response to the SSAP_WRITE_REQ 1 signaling, and the source port number in the signaling is the port number D of the second service, and the destination port number is the port number A of the first application.

[0347] Still referring to FIG. 17, in this example, before the client receives the SSAP_READ_RSP signaling, or before the client receives the SSAP_WRITE_RSP 1 signaling, the client can also send the SSAP_WRITE_REQ 2 signaling to the server, and the source port number in the signaling is the port number B of the second application, and the destination port number is the port number F of the third service.

[0348] It should be noted that the scenarios in FIG. 16 and FIG. 17 are only used as an example of the client as the signaling initiator, and the server has the same traffic control as the client, which will not be repeated here.

[0349] In a possible implementation, the first service in the embodiments of the present application can refer to a single service or multiple services (two or more services). The scenarios described above are used as an example of accessing a single service each time by the application. For example, in the scenario of accessing multiple services by the application, the source port number in the signaling sent by the client to the server is the port number of the application, and the destination port number can be the port number of the service management functional unit of the server. After receiving the signaling, the service management functional unit of the server can perform corresponding operations on all services of the application. Alternatively, the corresponding operations can also be performed on all services of the server.

[0350] Alternatively, if the port numbers of the multiple services accessed by the client are the same, the client can use the port number of any one of the multiple services as the destination port number.

[0351] In another possible implementation, if the service management functional unit of the server sends a notification or indication to multiple applications (two or more) of the client, the destination port number in the signaling sent by the server can be the port number of the service management functional unit of the client. Similarly, the service management functional unit of the client can send corresponding notification or indication information to all applications in response to the received signaling. That is, without specifying the object, the signaling sent by the client or the server can use the port number of the service management functional unit of the opposite end as the destination port number.

[0352] In yet another possible implementation, the service management functional unit of the client in the embodiments of the present application can send signaling to the specified service of the server, wherein the source port number can be the port number of the service management functional unit of the client, and the destination port number can be the port number of the specified service. Alternatively, if the signaling is sent to multiple services, the destination port number can also be the port number of the service management functional unit of the server.

[0353] In yet another possible implementation, the service management functional unit of the server in the embodiments of the present application can send signaling to the specified application of the client, wherein the source port number can be the port number of the service management functional unit of the server, and the destination port number can be the port number of the specified application. Alternatively, if the signaling is sent to multiple applications, the destination port number can also be the port number of the service management functional unit of the client.

[0354] In yet another possible implementation, as described above, each service of the server in the embodiment of the present application corresponds to a port number. In some instances, the port numbers of some services (including the same application or different applications) can be the same. In this example, in the signaling sent by the client, the port number of the first service in the destination port number can also be understood as the port number of the multiple services. For example, in the case that the port numbers of the first service, the second service and the third service are the same, the destination port number in the first signaling sent by the client is the port number of the first service, and of course, it can also be understood as the port number of the second service and the port number of the third service. Correspondingly, after receiving the signaling, the server can determine that it corresponds to multiple services based on the destination port number. The server can determine which service or services the signaling corresponds to based on other information in the signaling.

[0355] To sum up, the present application provides a service interaction method, and FIG. 18 is a flowchart of the service interaction method, which is exemplarily shown. Please refer to FIG. 18, which specifically includes but is not limited to the following steps:

[0356] S1801, the client obtains the port number of the service of the server.

[0357] Specifically, the client obtains the service port number of the application, and after the server obtains the port number of the service, the client can obtain the port number of one or more services of the server. The specific description can be referred to the above, which will not be repeated here.

[0358] S1802, the server obtains the client port number of the application of the client.

[0359] Specifically, after the client obtains the port number of the service, the server can obtain the client port number of one or more applications of the client. The specific description can be referred to the above, which will not be repeated here.

[0360] S1803, the client and the server perform service interaction.

[0361] Specifically, the client and the server can perform service interaction based on the client port number of the application and the port number of the service. Exemplarily, the client can send service interaction signaling to the server, and the signaling can include but is not limited to: source port number and destination port number. The source port number is the client port number of a single application (for example, it can be the first application), and the destination port number can be the port number of the service (for example, it can be the port number of the first service of the first application).

[0362] Exemplarily, the server can send a service interaction instruction to the client, and the signaling can include but is not limited to: a source port number and a destination port number. The source port number is a port number of a single service (for example, a first service), and the destination port number is a client port number of an application (for example, a client port number of a first application).

[0363] Exemplarily, the first service can be one or more of the services of the server, and the first application can be one or more of the applications of the client.

[0364] In this way, the service interaction method provided in the embodiments of the present application can be used in a short-range wireless communication system (for example, a star flash communication system or other short-range wireless communication systems such as a Bluetooth communication system, a Wi-Fi communication system, etc.), and the client and the server can perform service interaction based on the port number of the application and the port number of the service, thereby realizing directional interaction between the application and the service. For the client, the source port number can be used to determine the application to which the signaling is directed, and data can be sent to the corresponding application. For the server, the destination port number can be used to determine the service to which the signaling is directed, and the specified service can be processed accordingly. In addition, the server can also perform access control on the service access of the application based on the source port number. In addition, in the embodiments of the present application, the client and the server can control the traffic of the transaction through the port number, so as to realize the concurrency of the transaction in the same direction and improve the service interaction efficiency.

[0365] FIG. 19 shows a schematic block diagram of a service interaction apparatus 1900 according to an embodiment of the present application. The service interaction apparatus can include a processor 1901 and a transceiver / transceiver pin 1902, and optionally, a memory 1903. The processor 1901 can be used to execute the steps performed by the client or the server in the methods of the foregoing embodiments, and to control the reception of signals by the reception pin and the transmission of signals by the transmission pin.

[0366] The various components of the service interaction apparatus 1900 are coupled together by a bus system 1904, which can include a data bus, a power bus, a control bus, and a state signal bus. However, for the sake of clarity, the various buses are shown in the drawing as the bus system 1904.

[0367] Optionally, the memory 1903 can be used to store the instructions in the foregoing method embodiments.

[0368] It should be understood that the service interaction apparatus 1900 according to the embodiments of the present application can correspond to the electronic device in the methods of the foregoing embodiments, and the electronic device can be a client or a server, and the above and other management operations and / or functions of the various elements in the service interaction apparatus 1900 are respectively used to realize the corresponding steps of the foregoing methods, and for the sake of brevity, will not be described here again.

[0369] All the related content of each step involved in the above method embodiments can be cited to the function description of the corresponding function module, and will not be repeated here.

[0370] Based on the same technical concept, the embodiments of the present application also provide a computer readable storage medium, which stores a computer program. The computer program contains at least one code, which can be executed by a service interaction device to control the service interaction device to implement the above method embodiments.

[0371] Based on the same technical concept, the embodiments of the present application also provide a computer program, which is used to implement the above method embodiments when the computer program is executed by a service interaction device.

[0372] The program can be stored in a storage medium packaged with the processor, or partially or entirely stored in a storage medium not packaged with the processor.

[0373] Based on the same technical concept, the embodiments of the present application also provide a processor, which is used to implement the above method embodiments. The processor can be a chip.

[0374] The steps of the method or algorithm described in connection with the embodiments of the present application can be implemented in the form of hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, which can be stored in a random access memory (RAM), a flash memory, a read only memory (ROM), an erasable programmable ROM (EPROM), an electrically EPROM (EEPROM), a register, a hard disk, a mobile hard disk, a compact disk (CD-ROM) or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor, so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC.

[0375] Those skilled in the art should be aware that, in the above one or more examples, the functions described in the embodiments of the present application can be implemented in hardware, software, firmware or any combination thereof. When implemented in software, the functions can be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium. The computer readable medium includes computer storage medium and communication medium, and the communication medium includes any medium that facilitates transfer of a computer program from one place to another. The storage medium can be any available medium accessible by a general purpose or special purpose computer.

[0376] The term "and / or", used herein only describes an associated relationship, which means that there can be three relationships, for example, A and / or B, which means that there are three cases: A exists alone, A and B exist together, and B exists alone.

[0377] The terms "first" and "second" and the like in the description and claims of the present application are used to distinguish different objects, and are not used to describe a specific order of the objects. For example, the first target object and the second target object are used to distinguish different target objects, and are not used to describe a specific order of the target objects.

[0378] In the embodiments of the present application, the words "exemplary" or "for example" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the embodied words are used to present concepts in a particular, concrete manner. In the description of the embodiments of the present application, unless otherwise specified, the meaning of "a plurality" is two or more. For example, a plurality of processing units means two or more processing units; a plurality of systems means two or more systems.

[0379] In the description of the embodiments of the present application, unless otherwise specified, the meaning of "a plurality" is two or more. For example, a plurality of processing units means two or more processing units; a plurality of systems means two or more systems.

[0380] The embodiments of the present application are described above in combination with the drawings, but the present application is not limited to the above specific embodiments, and the above specific embodiments are only illustrative, not restrictive. Those skilled in the art can make many forms under the inspiration of the present application without departing from the scope of the present application and the scope of protection of the claims.

Claims

1. A service interaction method, characterized by, The method is applied to a short-range wireless communication system, and the method comprises: obtaining a port number of a service of a server; sending first signaling, wherein the first signaling comprises a first source port number and a first destination port number; the first source port number is a client port number of a first application, and the first destination port number is a port number of a first service; the first service is one or more of the services of the server.

2. The method of claim 1, wherein, The first application comprises the first service, and the port number of the first service is the port number of the first service of the first application.

3. The method of claim 1, wherein the port number of the first service of the first application is different from port numbers of other services of the first application; or the port number of the first service of the first application is the same as the port numbers of the other services of the first application.

4. The method of claim 1, wherein, port numbers of services of the first application are different from port numbers of services of other applications.

5. The method of claim 1, wherein, The first signaling is a request signaling, and the method further comprises: sending second signaling to the server, wherein the second signaling is a request signaling, and the second signaling comprises a second source port number and a second destination port number; the second source port number and the second destination port number are at least one of the following: the second source port number is different from the first source port number, and the second destination port number is different from the first destination port number; receiving first response signaling sent by the server, wherein the first response signaling is feedback of the server in response to the first signaling.

6. The method of claim 1, wherein, The method further comprises: receiving third signaling sent by the server, wherein the third signaling comprises a third source port number and a third destination port number; the third source port number is the port number of the first service, and the third destination port number is a client port number of the first application.

7. The method of claim 1, wherein, The method further comprises: obtaining a descriptor of a service declaration of the one or more services, wherein the descriptor is used to indicate the port number of the corresponding service; and reading a value of the descriptor of the service declaration of the one or more services to obtain the port number of the one or more services.

8. The method of claim 1, wherein, After obtaining the port number of the service provided by the server, the method further comprises: sending target signaling to the server, wherein the target signaling comprises the client port number of the first application, or comprises client port numbers of applications of the client.

9. The method of claim 1, wherein, The port number of the first service is a port number managed by the service of the server.

10. The method of claim 1, wherein, The short-range wireless communication system supports non-IP data transmission.

11. A service interaction method characterized by, The method is applied to a short-range wireless communication system, and the method comprises: obtaining a client port number of an application of a client; sending first signaling to the client, wherein the first signaling comprises a first source port number and a first destination port number; the first source port number is a port number of a first service, and the first destination port number is a client port number of a first application; the client port number of the first application is one or more of the applications of the client.

12. The method of claim 11, wherein, The first application comprises the first service, and the port number of the first service is the port number of the first service of the first application.

13. The method of claim 11, wherein the port number of the first service of the first application is different from port numbers of other services of the first application; or, the port number of the first service of the first application is the same as port numbers of other services of the first application. The port numbers of the services of the first application are different from port numbers of services of other applications. The first signaling is indication signaling, and the method further comprises:

14. The method of claim 11, wherein, sending, to the client, second signaling, the second signaling being indication signaling, the second signaling comprising a second source port number and a second destination port number, wherein the second source port number and the second destination port number are at least one of the following: the second source port number is different from the first source port number, and the second destination port number is different from the first destination port number; 15. The method of claim 11, wherein, receiving first confirmation signaling sent by the client, the first confirmation signaling being feedback of the client in response to the first signaling. The obtaining of the client port number of the application of the client comprises: receiving third signaling sent by the client, the third signaling comprising a third source port number and a third destination port number, wherein the third source port number is the client port number of the first application, and the third destination port number is the port number of the first service; 16. The method of claim 11, wherein, obtaining the client port number of the first application in response to the third signaling. The obtaining of the client port number of the application of the client comprises: receiving target signaling sent by the client, the target signaling comprising the client port number of the first application or client port numbers of applications of the client.

17. The method of claim 11, wherein, Before the obtaining of the client port number of the application of the client, the method further comprises: sending, to the client, values of descriptors corresponding to the services of the service end, the values of the descriptors being used to indicate the port numbers of the corresponding services.

18. The method of claim 11, wherein, The port number of the first application is a port number managed by a service of the client. Before the obtaining of the client port number of the application of the client, the method further comprises:

19. The method of claim 11, wherein, if signaling with a source port number being the client port number of the first application is received, sending, to the client, fourth signaling used to indicate rejection of access of the first application to the service of the service end this time.

20. The method of claim 11, wherein, The short-range wireless communication system supports non-IP data transmission. An apparatus applied to a short-range wireless communication system, the apparatus comprising:

21. The method of claim 11, wherein, one or more processors; 22. A service interaction apparatus characterized by comprising: one or more memories; and one or more computer programs, wherein the one or more computer programs are stored in the one or more memories, and when the computer programs are executed by the one or more processors, the apparatus performs the method of any one of claims 1 to 10, or performs the method of any one of claims 11 to 21. computer instructions, when the computer instructions are run on an electronic device, cause the electronic device to perform the method of any one of claims 1 to 10, or perform the method of any one of claims 11 to 21. ​ 23. A computer storage medium, comprising, ​ 24. A computer program product, characterised in that, When the computer program product is run on a computer, it causes the computer to perform the method of any one of claims 1-10, or the method of any one of claims 11 to 21.

Images