Communication processing method and apparatus, device, and readable storage medium

By requesting device and association information from the server, the problem of the network side being unable to identify the association relationship of composite devices is solved, realizing unified management and service quality assurance of composite devices, and improving data transmission efficiency and user experience.

WO2026237639A1PCT designated stage Publication Date: 2026-11-19CHINA MOBILE COMM LTD RES INST +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2026/090866
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-12
Filing Date
2026-04-15
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

In immersive communication, the network side cannot identify the relationships between composite devices, resulting in the inability to provide a unified quality of service guarantee.

Method used

By sending information to a second server to request indications of devices, device groups, and associations, service quality information is obtained, and a suitable server is selected for data transmission based on network load and traffic, thereby achieving unified management and service quality assurance for composite devices.

Benefits of technology

It improved data transmission efficiency and user experience, ensured that the specific needs of different devices and services were met, optimized network resource allocation, and enhanced network adaptability and overall service quality.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2026090866_19112026_PF_FP_ABST
    Figure CN2026090866_19112026_PF_FP_ABST
Patent Text Reader

Abstract

Provided in the embodiments of the present disclosure are a communication processing method and apparatus, a device, and a readable storage medium. The method comprises: sending first information to a second server, wherein the first information is configured to request second information, and the second information is configured to indicate at least one of the following: a first device, a first device group, a first group, and a first association relationship.
Need to check novelty before this filing date? Find Prior Art

Description

Communication processing methods, apparatus, devices and readable storage media

[0001] Cross-references to related applications

[0002] This disclosure is based on and claims priority to Chinese Patent Application No. 202510606918.9, filed on May 12, 2025, the entire contents of which are incorporated herein by way of inclusion. Technical Field

[0003] This disclosure relates to the field of communication technology, specifically to a communication processing method, apparatus, device, and readable storage medium. Background Technology

[0004] In immersive communication, a single terminal in an Extended Reality (XR) service may be connected to several composite devices, such as glasses, gloves, controllers, and fitness rings. Because the network side is unaware of the relationship between the terminal and these composite devices, it cannot provide a unified Quality of Service (QoS) guarantee to all of them. Summary of the Invention

[0005] This disclosure provides a communication processing method, apparatus, device, and readable storage medium to solve the problem of unknown relationships between composite devices.

[0006] Firstly, a communication processing method is provided, applied to a first server, comprising:

[0007] Send first information to a second server, the first information being used to request second information, the second information being used to indicate at least one of the following: a first device, a first device group, a first group, a first association.

[0008] In some embodiments, the first device group includes one or more of the first devices; and / or, the first group includes one or more of the first devices and the second device; and / or, the first association is used to indicate an association between one or more of the first devices and the second device.

[0009] The first device is a 3GPP or non-3GPP device, and the second device is a 3GPP device.

[0010] In some embodiments, the method further includes:

[0011] Receive the second information from the second server.

[0012] In some embodiments, the first device is a tethered device, and / or the second device is a tethering device.

[0013] In some embodiments, the method further includes:

[0014] Receive third information from a third server, the third information being used to indicate the transmission of data.

[0015] In some embodiments, the third information is at least one of the following: shared group identifier, group identifier, tethered group identifier, PINE group identifier of personal Internet of Things network element, group information, device group information, and sharing policy information;

[0016] And / or,

[0017] The third information is used to indicate the association between the second device and one or more of the first devices.

[0018] In some embodiments, the third information includes at least one of the following: device type, device list, vertical application layer VAL service identifier, shared device identifier, tethered device identifier, physical address (e.g., MAC address), UE IP address, and UE identifier;

[0019] The device type is used to indicate the type of the second device or the first device;

[0020] The device list includes at least one of the following: shared device identifier, tethered device identifier.

[0021] In some embodiments, the method further includes at least one of the following:

[0022] Obtain the Quality of Service (QoS) information of the first service, where the first service is a service associated with the first group;

[0023] Select the fourth server based on the traffic of the N6 interface and / or the load of the first server;

[0024] Send fourth information to the fourth server, the fourth information being used to indicate at least one of the following: information about the second device; information about the first device; information about the first service.

[0025] In some embodiments, the first information includes at least one of the following: the General Public User Identifier (GPSI) of the second device, and the Personal Internet of Things Identifier (IoT) of the second device.

[0026] In some embodiments, the second server includes a PIN server, and / or the first server or the fourth server includes a service enable architecture layer data transfer SEALDD server, and / or the third server includes a VAL server.

[0027] Secondly, a communication processing method is provided, applied to a second server, including:

[0028] Receive first information from a first server, the first information being used to request second information, the second information being used to indicate at least one of the following: a first device, a first device group, a first group, and a first association.

[0029] In some embodiments, the first device group includes one or more of the first devices; and / or, the first group includes one or more of the first devices and the second device; and / or, the first association is used to indicate an association between one or more of the first devices and the second device.

[0030] The first device is a 3GPP or non-3GPP device, and the second device is a 3GPP device.

[0031] In some embodiments, the method further includes:

[0032] Send the second information to the first server.

[0033] In some embodiments, the method further includes:

[0034] Receive the fifth message, which is used to request the registration of a third device.

[0035] In some embodiments, the third device is a tethered device or a shared device.

[0036] In some embodiments, receiving the fifth piece of information includes at least one of the following:

[0037] Receive the fifth information sent by the third device;

[0038] The fifth information is received from a fourth device, which is a shared device of the third device.

[0039] In some embodiments, the fifth information includes at least one of the following: a security certificate, a general public user identifier of the third device, the physical address of the third device, a vendor name, device description information of the third device, a PINE address, a PINE type, a shared group indication, a shared group creation indication, a tethered identifier, a shared identifier, a VAL service identifier, and indication information for indicating registration.

[0040] In some embodiments, the method further includes:

[0041] When the PINE type is a shared device, perform at least one of the following: determine that the third device is a primary role Personal Internet of Things (PEMC) with management capabilities or a secondary role PEMC; assign a shared group identifier to the device group to which the third device belongs;

[0042] or,

[0043] When the PINE type is the tethered device, perform at least one of the following: determine the shared device associated with the third device; determine the shared device associated with the third device based on the VAL service identifier; and store shared mapping information in the PIN configuration, the shared mapping information being used to indicate the association relationship between the third device and the shared device.

[0044] In some embodiments, the method further includes:

[0045] Based on the configuration of the second server, obtain information about the first device.

[0046] In some embodiments, the configuration of the second server includes the association between the second device and the first device.

[0047] In some embodiments, the second server includes a PIN server, and / or the first server includes a SEALDD server, and / or the third device includes a PINE, and / or the fourth device includes a PEMC.

[0048] Thirdly, a communication processing method is provided, applied to a third device, comprising:

[0049] A fifth message is sent to the second server, the fifth message being used to request the registration of a third device, the type of which is a tethered device or a shared device.

[0050] In some embodiments, sending a fifth message to the second server includes at least one of the following:

[0051] The fifth message is sent directly to the second server;

[0052] The fifth message is sent to the second server via the fourth device.

[0053] In some embodiments, the fifth information includes at least one of the following: a security certificate, a general public user identifier of the third device, the physical address of the third device, a vendor name, device description information of the third device, a PINE address, a PINE type, a shared group indication, a shared group creation indication, a tethered identifier, a shared identifier, a VAL service identifier, and indication information for indicating registration.

[0054] Fourthly, a communication processing apparatus is provided, applied to a first server, comprising: a first transceiver unit; the first transceiver unit is configured to send first information to a second server, the first information being used to request second information, the second information being used to indicate at least one of the following: a first device, a first device group, a first group, a first association relationship.

[0055] Fifthly, a communication processing apparatus is provided, applied to a second server, comprising: a second transceiver unit; the second transceiver unit is configured to receive first information from a first server, the first information being used to request second information, the second information being used to indicate at least one of the following: a first device, a first device group, a first group, a first association relationship.

[0056] A sixth aspect provides a communication processing apparatus for use with a third device, comprising: a third transceiver unit; the third transceiver unit being configured to send fifth information to a second server, the fifth information being used to request registration of the third device, the third device being a tethered device or a shared device.

[0057] A seventh aspect provides a communication device, including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the method as described in the first, second, or third aspect.

[0058] Eighthly, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the method as described in the first, second, or third aspect.

[0059] Ninth aspect, a computer program product is provided, including computer instructions that, when executed by a processor, implement the method as described in the first, second, or third aspect. Attached Figure Description

[0060] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of the embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this disclosure. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0061] Figure 1 is a flowchart of a communication processing method provided by an embodiment of this disclosure;

[0062] Figure 2 is a flowchart of another communication processing method provided by an embodiment of this disclosure;

[0063] Figure 3 is a flowchart of another communication processing method provided by an embodiment of this disclosure;

[0064] Figure 4 is a flowchart illustrating the direct registration of a tethered device in a PIN server according to an embodiment of this disclosure;

[0065] Figure 5 is a flowchart of the indirect registration of a tethered device in a PIN server provided in an embodiment of this disclosure;

[0066] Figure 6a is a flowchart of a VAL server issuing configuration information for composite devices through a policy, as provided in an embodiment of this disclosure.

[0067] Figure 6b is a flowchart of the SEALDD-enabled XR data transmission connection establishment provided in an embodiment of this disclosure;

[0068] Figure 7 is a flowchart of enabling data transmission quality assurance based on SEALDD server switching provided in an embodiment of this disclosure;

[0069] Figure 8 is a flowchart illustrating how tethered device information is stored in 5GC via SA2 NEF, as provided in an embodiment of this disclosure.

[0070] Figure 9 is a schematic diagram of a communication processing apparatus provided in an embodiment of the present disclosure;

[0071] Figure 10 is a schematic diagram of another communication processing apparatus provided in an embodiment of the present disclosure;

[0072] Figure 11 is a schematic diagram of another communication processing apparatus provided in an embodiment of the present disclosure;

[0073] Figure 12 is a schematic diagram of a communication device provided in an embodiment of this disclosure. Embodiments of the present invention

[0074] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this disclosure. Based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this disclosure.

[0075] The term "comprising," and any variations thereof, used in this disclosure and in the claims are intended to cover a non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of operations or units is not necessarily limited to those explicitly listed, but may include other operations or units not explicitly listed or inherent to such process, method, product, or apparatus. Furthermore, the use of "and / or" in the specification and claims indicates at least one of the connected objects, such as A and / or B, indicating the inclusion of A alone, B alone, or both A and B.

[0076] In this disclosure, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" or "for example" in this disclosure should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0077] This disclosure applies to any scenario involving tethered devices. The tethered device can connect to a tethered device in a tethered manner, and the tethered device generally possesses network communication capabilities. For example, the tethered device can be wearable devices such as AR glasses, VR headsets, or smart bracelets, while the tethered device can generally be a mobile phone (hereinafter referred to as a 3GPP UE), computer, or other terminal. These terminals can typically interact with the core network and other communication devices through the 3GPP network. Usually, the tethered device is not a 3GPP device and cannot directly access the 3GPP network; therefore, the tethered device can access the 3GPP network by connecting to a 3GPP UE.

[0078] In this disclosure, a tethered device (e.g., a tethered terminal, i.e., a tethered UE) refers to a device connected to a terminal in a tethered manner, such as AR glasses or a smartwatch. Unlike other types of terminals, the end-to-end path of a tethered device includes one or more tethered links between the tethered device and the tethered terminal (e.g., a 5G mobile phone, a 3GPP UE, etc.), and the tethered links can be in the form of wireless or wired connections.

[0079] In this disclosure, tethered devices can include three types: tethered standalone devices, tethered display devices, and 5G relay-based tethered devices (also referred to simply as relay tethered devices, which segment XR operations in the cloud). A vertical application layer is used to deploy various vertical applications. In some embodiments, the vertical application layer of the tethered device can deploy clients of vertical applications, and the vertical application layer of the tethered device can also deploy clients of corresponding vertical applications. These clients can interact with each other, and with the application server, within the vertical application layer. The vertical application layer (VAL) can include one or more vertical applications, with the VAL server providing services to the VAL clients. This disclosure does not impose any particular limitations on the type or number of vertical applications.

[0080] For ease of understanding, the following explanation will use XR applications as an example. XR applications can include at least one of Virtual Reality (VR) applications and Augmented Reality (AR) applications. Based on the classification of tethered devices, tethered devices for XR applications can also be divided into tethered XR devices and tethered display XR devices (or tethered display devices). The XR application client for a tethered XR device is deployed on the tethered device itself; examples include tethered standalone AR glasses, tethered AR glasses with 5G relay, etc., without exhaustive list. Tethered display XR devices, on the other hand, deploy the XR application client on a 3GPP UE.

[0081] Referring to Figure 1, embodiments of this disclosure provide a communication processing method applied to a first server. In some embodiments, the first server includes, but is not limited to, a Service Enabler Architecture Layer for Verticals (SEALDD) server. Specific operations include: Operation 11;

[0082] Operation 11: Send first information to the second server, the first information being used to request second information, the second information being used to indicate at least one of the following: a first device, a first device group, a first group, a first association relationship.

[0083] In some embodiments, the first device may also be replaced or understood as the first terminal or the first user.

[0084] In some embodiments, the second device may also be replaced or understood as a second terminal or a second user.

[0085] In some embodiments, the first device group includes one or more first devices.

[0086] In some embodiments, the first group includes one or more first devices and second devices. One or more first devices are associated with a second device, wherein association can be understood as one or more first devices and second devices being in the same group, or one or more first devices and second devices sharing the same group identifier, or one or more first devices and second devices having mutually accessible IP addresses or MAC addresses, or one or more first devices and second devices being able to access each other.

[0087] In some embodiments, the first association is used to indicate an association between one or more first devices and second devices. This association indicates that one or more first devices are tethered to a second device, and the one or more first devices and second devices may constitute a first group.

[0088] In some embodiments, the second device is a 3GPP device.

[0089] In some embodiments, the first device is a 3GPP or non-3GPP device.

[0090] In some embodiments of this disclosure, the method further includes receiving second information from the second server.

[0091] In some embodiments, the second server includes a PIN server.

[0092] In some embodiments of this disclosure, the first device is a tethered device, and / or the second device is a tethering device.

[0093] In some embodiments, the tethered device may also be replaced or understood as the shared device or composite device.

[0094] In some embodiments, the shared device may also be replaced or understood as the tethered device.

[0095] In some embodiments of this disclosure, prior to operation 11, the method further includes:

[0096] Receive third information from a third server, which is used to indicate traffic transfer.

[0097] In some embodiments, the third server includes a VAL server.

[0098] In some embodiments of this disclosure, the third information is at least one of the following: tethering group ID, group ID, tethered group ID, PINE group ID, group information, device group information, and sharing policy information.

[0099] In some embodiments of this disclosure, third information is used to indicate the association between the second device and one or more first devices.

[0100] In some embodiments of this disclosure, the fourth information includes: device group information or sharing policy information, which is used to indicate the association relationship between the second device and the first device.

[0101] In some embodiments of this disclosure, the third information includes at least one of the following: device type, device list, VAL service ID, tethering device ID, tethered device ID, physical address (e.g., MAC address), UE IP address, and UE identifier;

[0102] The device type is used to indicate the type of the second device or the first device;

[0103] The device list includes at least one of the following: shared device identifier, tethered device identifier.

[0104] In some embodiments, the shared device identifier includes the VAL client identifier.

[0105] In some embodiments, the tethered device identifier includes the VAL client identifier.

[0106] In some embodiments of this disclosure, the method further includes at least one of the following:

[0107] Obtain the Quality of Service (QoS) information of the first service, which is a service associated with the first group;

[0108] Select the fourth server based on the traffic to the N6 interface and / or the load on the first server (e.g., SEALDD server load);

[0109] Send fourth information to the fourth server, the fourth information being used to indicate at least one of the following: information about the second device; information about the first device; information about the first service.

[0110] In this embodiment, by acquiring the QoS information of the first service, the performance and user experience of the first service can be effectively improved. The first service is closely related to the second device and one or more associated first devices. After acquiring this QoS information, a suitable fourth server can be selected for processing according to actual needs. This flexible server selection ensures that the specific needs of different devices and services can be met, optimizes the configuration of network resources, and improves data transmission efficiency. In addition, sending fourth information to the fourth server provides comprehensive data support for subsequent resource scheduling and network management, realizing precise management of multi-device combinations. This process not only enhances the network's adaptability to different service needs but also improves the overall service quality and stability, providing users with a smoother and more immersive experience.

[0111] In some embodiments, the fourth server may include a SEALDD server. This fourth server may be the same as or different from the first server.

[0112] In some embodiments, the first service includes, but is not limited to, XR services.

[0113] In some embodiments of this disclosure, the first information includes at least one of the following: the Generic Public Subscription Identifier (GPSI) of the second device, and the Personal IoT Network (PIN) identifier of the second device.

[0114] In this disclosure, the network side can identify and manage the relationship between the first device and the second device connected to it, enabling the network side to provide a unified Quality of Service (QoS) guarantee to the first device and the second device connected to it.

[0115] Referring to Figure 2, embodiments of this disclosure also provide a communication processing method applied to a second server, for example, the second server including a PIN server. Specific operations include:

[0116] Operation 21: Receive first information from a first server, the first information being used to request second information, the second information being used to indicate at least one of the following: a first device, a first device group, a first group, a first association relationship;

[0117] In some embodiments, the first server may include a SEALDD server.

[0118] In some embodiments, the first device may also be replaced or understood as the first terminal or the first user.

[0119] In some embodiments, the first device group includes one or more first devices.

[0120] In some embodiments, the first group includes one or more first devices and second devices. One or more first devices are associated with a second device, wherein association can be understood as one or more first devices and second devices being in the same group, or one or more first devices and second devices sharing the same group identifier, or one or more first devices and second devices having mutually accessible IP addresses or MAC addresses, or one or more first devices and second devices being able to access each other.

[0121] In some embodiments, the first association is used to indicate an association between one or more first devices and second devices. This association indicates that one or more first devices are tethered to a second device, and the one or more first devices and second devices may constitute a first group.

[0122] In some embodiments, the second device is a 3GPP device.

[0123] In some embodiments, the first device is a 3GPP or non-3GPP device.

[0124] In some embodiments of this disclosure, after operation 21, the method further includes: sending the second information to the first server;

[0125] Optionally, the first device is a tethered device, and the second device is a tethering device.

[0126] In some embodiments of this disclosure, prior to operation 21, the method further includes:

[0127] The fifth message is received, which is used to request the registration of a third device, the type of which is a tethered device or a shared device.

[0128] In some embodiments, the third device includes, but is not limited to, PINE.

[0129] In some embodiments of this disclosure, receiving the fifth information includes at least one of the following:

[0130] Receive the fifth information sent by the third device;

[0131] The fifth information is received from a fourth device, which is a shared device of the third device.

[0132] In some embodiments, the fourth device includes, but is not limited to, a Personal Internet of Things Element with Management Capability (PEMC).

[0133] In some embodiments of this disclosure, the fifth information includes at least one of the following: a security credential, a general public user identifier of the third device, a physical address of the third device (e.g., a Medium Access Control (MAC) address), a vendor name, device description information of the third device, a PINE address, a PINE type, a shared group indication, a shared group creation indication, a tethered ID, a shared identifier (e.g., a tethering ID), a VAL service identifier, and indication information for indicating registration.

[0134] In some embodiments of this disclosure, after receiving the fifth information, the method further includes:

[0135] When the PINE type is a shared device, perform at least one of the following: determine that the third device is a primary role Personal Internet of Things (PEMC) with management capabilities or a secondary role PEMC; assign a shared group identifier to the device group to which the third device belongs;

[0136] or,

[0137] When the PINE type is a tethered device, perform at least one of the following: determine the shared device associated with the third device; determine the shared device associated with the third device based on the VAL service identifier; and store shared mapping information in the PIN configuration, the shared mapping information being used to indicate the association relationship between the third device and the shared device.

[0138] In some embodiments of this disclosure, the method further includes:

[0139] Based on the configuration of the second server, obtain information about the first device.

[0140] In some embodiments of this disclosure, the configuration of the second server includes the association between the second device and the first device.

[0141] In some embodiments of this disclosure, the first information includes at least one of the following: the Generic Public Subscription Identifier (GPSI) of the second device, and the Personal IoT Network (PIN) identifier of the second device.

[0142] In this disclosure, the network side is able to identify and manage the relationship between the first device and the second device connected to it, enabling the network side to provide unified QoS guarantees to the first device and the second device connected to it.

[0143] Referring to Figure 3, an embodiment of this disclosure provides a communication processing method applied to a third device, such as, but not limited to, a PINE. The specific operation includes:

[0144] Operation 31: Send fifth information to the second server, the fifth information being used to request the registration of a third device, the type of which is a tethered device or a shared device.

[0145] In some embodiments, the fifth piece of information may also be referred to as or understood as a registration request.

[0146] In some embodiments of this disclosure, sending a fifth message to a second server includes at least one of the following:

[0147] Send the fifth message directly to the second server;

[0148] The fifth message is sent to the second server via the fourth device.

[0149] In some embodiments, the fourth device includes, but is not limited to, PEMC.

[0150] In some embodiments of this disclosure, the fifth information includes at least one of the following: a security certificate, a general public user identifier of the third device, a physical address of the third device (e.g., a media access control (MAC) address), a vendor name, device description information of the third device, a PINE address, a PINE type, a shared group indication, a shared group creation indication, a tethered identifier, a shared identifier, a VAL service identifier, and indication information for indicating registration.

[0151] In this disclosure, the network side is able to provide unified QoS guarantees to the shared device and its connected tethered devices.

[0152] The following example uses SEALDD server #1 as the first server, PIN server as the second server, VAL server as the third server, and SEALDD server #2 as the fourth server, with the first device being a Tethered device, the second device being a tethering device, the third device being a PINE, and the fourth device being a PEMC.

[0153] Example 1: Direct registration of tethered devices to the PIN server (PINE registration directly to the PIN server).

[0154] In some embodiments, the prerequisites for the process shown in Figure 4 include, but are not limited to, at least one of the following: 1) the PINE has been pre-configured or has discovered the address of the PIN server (such as IP address, FQDN, URI); 2) the UE identifier is available; 3) the PINE has been authorized to communicate with the PIN server.

[0155] Refer to Figure 4. The specific operation is as follows:

[0156] Operation 1: PINE sends a registration request;

[0157] In some embodiments, the registration request may also be referred to as a PINE registration request.

[0158] In some embodiments, the registration request includes at least one of the following: security credential, Generic Public Subscription Identifier (GPSI), MAC address, vendor name, device description, PINE address, PINE type, tethering group indicator, tethering group creation indicator, tethered ID, tethering ID, and VAL service ID.

[0159] In some embodiments, the PINE type includes, but is not limited to, tethered devices and tethering devices.

[0160] In some embodiments, a shared group indication or a shared group creation indication may be used to indicate that the PINE type is a tethered device or a shared device.

[0161] In some embodiments, a shared group instruction or a shared group creation instruction may be used to instruct the creation of a shared group and the assignment of a shared group identifier.

[0162] In some embodiments, the tethered device may also be replaced or understood as the shared device.

[0163] If the PEMC triggers a registration request, the request carries the PIN ID of the PIN it intends to register as the PEMC, and the PINE may indicate whether it wants to be assigned a primary role or a secondary role.

[0164] Operation 2: The PIN server checks whether the PINE conforms to PEMC;

[0165] For example, if the PINE type is a shared device, the PIN server checks the GPSI to determine if the PINE is already subscribed to a PEMC. If it is, the server uses the PINE's subscription information to determine whether the PINE can be assigned a primary or secondary role and authorizes the PINE accordingly. If a PIN has already been created, the requested PINE will be assigned a secondary role regardless of the requested role. The PIN server assigns a tethering group ID to this group.

[0166] For example, if the PINE type is a tethered device, the PIN server identifies the shared device based on the VAL business identifier and stores the shared mapping information in the PIN configuration.

[0167] For example, by checking the tethering ID, it can be determined that the PINE is a UE of the tethering type. The PINE is then assigned a primary or secondary role PEMC and a PIN client identifier is assigned to it. If the PINE registration request carries a tethered ID, it is determined that the PINE is an external device connected to a tethering device. The tethering ID is used to locate the tethering device in front of the PINE, and a PINE client identifier is assigned. The binding relationship of the PINE is also recorded.

[0168] Operation 3: The PIN server sends a registration response to PINE, which carries the PIN client identifier.

[0169] In some embodiments, the registration response may also be referred to as the PINE registration response.

[0170] For example, the PIN server sends a registration response to PINE. If registration is successful, the registration response includes the assigned PIN client identifier and a shared group identifier (optional). If registration fails, the PIN server should indicate the reason for the failure in the registration response.

[0171] Example 2: Indirect registration of tethered devices to the PIN server (PINE registration indirectly to the PIN server).

[0172] In this embodiment, PEMC can replace PINE / PEGC in performing registration with the PIN server.

[0173] In some embodiments, the preconditions for the process shown in Figure 5 include, but are not limited to, at least one of the following: 1) The PEMC has been pre-configured or has discovered the address of the PIN server (e.g., IP address, FQDN, URI); 2) The UE identifier or PIN client identifier is available; 3) The PEMC has been authorized to communicate with the PIN server; 4) The PINE / PEGC has obtained the PEMC's IP address. Referring to Figure 5, the specific operation is as follows:

[0174] Operation 1: PINE / PEGC sends a registration request to PEMC (tethering device);

[0175] In some embodiments, the registration request includes at least one of the following: security certificate, GPSI, MAC address, vendor name, device description, PINE address, tethering type, tethering group indicator, tethering group creation indicator, and tethered ID.

[0176] In some embodiments, the sharing type includes a tethered device or a tethering device.

[0177] In some embodiments, a shared group indication or a shared group creation indication is used to indicate that the PINE type is a shared device or a tethered device.

[0178] In some embodiments, a shared group instruction or a shared group creation instruction may be used to instruct the creation of a shared group and the assignment of a shared group identifier.

[0179] In some embodiments, the tethered device may also be replaced or understood as the shared device.

[0180] Operation 2: If PEMC receives a registration request from PINE / PEGC, PEMC sends a registration request to the PIN server on behalf of PINE / PEGC;

[0181] In some embodiments, the registration request includes at least one of the following: security certificate, GPSI, MAC address, vendor name, device description, PINE address, tethering type, tethered ID, tethering ID, and indication of representation registration.

[0182] If the PEMC agent performs the registration process for PINE / PEGC, it should send a PINE registration request to the PIN server, including an indication of representation registration and a list of PINEs / PEGCs.

[0183] If the PINE / PEGC sharing type is a tethered device, the PEMC checks which tethering group the PINE belongs to. The PEMC should send a PINE registration request to the PIN server, which includes at least one of the following: instructions for agent registration, a list of PINE / PEGCs, and a tethering group ID.

[0184] Operation 3: The PIN server responds to the PEMC with a registration response. If the registration is successful, the registration response contains the assigned PIN client ID.

[0185] In some implementations, when the registration request includes instructions for proxy registration, the PIN server should verify whether the PINE / PEGC in the PINE / PEGC list has registration authorization and include in the registration response either a list of accepted registration information or a list of rejected registration information.

[0186] If all PINE / PEGCs in the list are rejected, a failure response is returned with the reason for the failure.

[0187] If the PINE / PEGC is a tethered device, the PIN server adds the PINE / PEGC to the tethering group information.

[0188] In some implementations, the PIN server associates the PINE with the bound front-end device (PEMC) using the tethered ID and tethering ID, and assigns a PINE client identifier. It also records the PINE's binding relationship. The PINE server sends a PINE registration response to the PEMC.

[0189] Operation 4: PEMC sends the registration response received in Operation 3 to PINE / PEGC.

[0190] When PEMC receives a registration response from the PIN server, PEMC should extract all accepted registration information and / or rejected registration information (if any) for all PINE / PEGCs and send the results to each PINE / PEGC in the PINE / PEGC list.

[0191] Example 3:

[0192] A PIN profile contains the static data required for configuring a Personal IoT Network. See Table 1 for PIN profile details.

[0193]

[0194]

[0195] Example 4: The VAL server issues configuration information for composite devices through policies.

[0196] Referring to Figure 6a, the specific operation is as follows:

[0197] Operation 1: The VAL server sends a policy configuration request to the SEALDD server.

[0198] In some embodiments, the policy configuration request includes, but is not limited to, at least one of the following: application traffic, VALUES ID, and SEALDD policy. See Table 3 for a detailed description.

[0199] Operation 2: The SEALDD server checks whether it has the permissions to configure policies for the VAL server.

[0200] Operation 3: The SEALDD server sends a policy configuration response to the VAL server.

[0201] In some embodiments, SEALDD stores SEALDD policies (including composite device policies).

[0202]

[0203] Example 4: SEALDD-enabled XR data transmission service (for XR applications).

[0204] Referring to Figure 6b, which illustrates the process of establishing an XR data transmission connection, SEALDD enables XR applications to transmit data between VAL clients and VAL servers, including RTP packetization and PDU set inclusion.

[0205] The specific steps are as follows:

[0206] Operation 1: The VAL server sends an Sdd_XR transmission request to the SEALDD server.

[0207] Operation 2: The SEALDD server sends a tethering group information request to the PIN server.

[0208] Upon receiving the request, the SEALDD server performs an authorization check. If authorization is successful, the SEALDD server sends a shared group information request to the PIN server, including the shared group ID (if the request includes a shared group identifier).

[0209] Operation 3: The PIN server sends a tethering group information response to the SEALDD server.

[0210] The PIN server sends a response to the SEALDD server, including but not limited to at least one of the following: a tethering device identifier and a tethered device identifier list. The SEALDD server allocates SEALDD-S connection information on its own side to receive application data traffic from the VAL server and PIN server for application data transmission between tethered and tethering devices. The SEALDD server allocates specific SEALDD-S connection information for SEALDD traffic transmission between a specific UE and the VAL server, and responds with a SEALDD service response (including the SEALDD-S connection information on the SEALDD server side). The VAL server and SEALDD server can use the SEALDD-S connection information to establish a data transmission connection between themselves for application data transmission.

[0211] For example, shared device identifiers include, but are not limited to, VAL UE ID or UE IP address. The list of tethered device identifiers includes, but is not limited to, MAC address.

[0212] The SEALDD server may send AF requests to provide the required Quality of Service (QoS) information to the 5GC via N33 / N5. The AF request contains an application traffic descriptor for the SEALDD-S connection information assigned by the SEALDD server, along with QoS information for the application traffic. If the QoS information is not provided by the VAL server, the SEALDD server may determine the QoS information based on the VAL service ID for different service types. If the SEALDD server is connected to the PCF via the N5 reference point, it relies on the PCF's northbound policy-authorized service API as specified in the relevant technical specifications; if the SEALDD server is connected to the PCF via the NEF, it relies on the NEF's northbound AF session QoS service API and / or northbound PFD management API as specified in the relevant technical specifications. SEALDD may also rely on the EES session QoS API and / or the NRM QoS functions described in the relevant technical specifications.

[0213] For multi-mode application services, the SEALDD server derives auxiliary information related to the PDU set based on the received VAL service ID and / or VAL server ID and the protocol description of the interaction with NEF / PCF.

[0214] If the SEALDD server uses downlink pull mode to retrieve data / content from the address provided by the VAL server in Operation 1, and uses uplink push mode to send the data / content to the address provided by the VAL server, then the SEALDD-S connection information on the SEALDD server can optionally be responded to the VAL server.

[0215] Operation 4: The SEALDD server sends an Sdd_XR transmission response to the VAL server.

[0216] The VAL server decides to use the SEALDD service to transmit XR traffic and allocates an address / port as SEALDD-S data transmission connection information for receiving data packets from the SEALDD server. The VAL server sends an Sdd_XR Transmission request to the SEALDD server discovered via CAPIF. This service request includes at least one of the following: UE ID / address, VAL server ID, VAL service ID, shared group identifier, SEALDD-S data transmission connection information on the VAL server side, and optional protocol descriptions and QoS information for the application traffic, such as QoS requirements.

[0217] Operation 5: Provisioning of the data transmission session;

[0218] Operation 6: The VAL client sends a SEALDD service request to the SEALDD client;

[0219] Optionally, the SEALDD service request includes at least one of the following: a tethering group ID obtained from the PIN server and tethered device information. The VAL client receives a SEALDD service response from the SEALDD client. If the data transfer session information includes SEALDD address information, the VAL client sends the selected SEALDD address information to the SEALDD client in the service request message. The response indicates whether the SEALDD service request was successful.

[0220] Step 7: SEALDD server confirmation;

[0221] Operation 8: SEALDD XR transmission connection established;

[0222] The SEALDD client maps the MAC address of each tethered device to a UE IP address and port number, and stores the mapping information. The SEALDD client assigns SEALDD-UU flow IDs to both tethering devices (e.g., VAL UE) and tethered devices. The SEALDD client establishes an XR transport connection with the SEALDD server. The request includes at least one of the following: SEALDD client ID, VAL user / UE ID, MAC address, VAL server ID, VAL service ID, SEALDD-UU flow ID, and traffic descriptors for multiple flows from the SEALDD client. The SEALDD server sends SEALDD traffic descriptors (e.g., addresses / ports of multiple SEALDD-UU flows) from the SEALDD server to the SEALDD client, and may send a protocol description (UL-related information) received from the VAL server to the SEALDD client in the XR transport connection response. The response also includes a multimodal SEALDD-UU flow ID assigned by the SEALDD server.

[0223] Operation 9: Establishment of data transmission session;

[0224] Operation 10: Establishment of SEALDD connection for XR data transmission.

[0225] XR application traffic between the VAL client and VAL server is exchanged through the SEALDD layer. If a packet indication suggests that the SEALDD layer needs to perform packet processing, the SEALDD server performs the packet processing and sends streaming data (e.g., RTP packets) to the SEALDD client via the SEALDD-UU user plane (e.g., SEALDD / UDP / IP) for downlink application traffic. Similarly, the SEALDD client performs packet processing and sends streaming data (e.g., RTP packets) to the SEALDD server via the SEALDD-UU user plane (e.g., SEALDD / UDP / IP) for uplink application traffic.

[0226] Example 5: Data transmission quality assurance enabled by SEALDD (achieved by switching SEALDD servers).

[0227] Refer to Figure 7. The specific operation is as follows:

[0228] Operation 1: VAL server #1 sends a transmission request (Sdd_Regular Transmission request) to SEALDD server #1 to request the establishment of a SEALDD transmission link.

[0229] In some embodiments, the transmission request includes, but is not limited to, at least one of the following: identifiers of the application traffic, QoS information for the application traffic, and tethering group ID;

[0230] In some embodiments, the transmission request may further include at least one of the following: UE ID or UE address, VAL server identifier, VAL service identifier, SEALDD-S connection information, UE type (tethered, tethering), PIN ID, and application information.

[0231] In some embodiments, the identifiers of the application traffic include VAL service ID and VAL server ID.

[0232] In some embodiments, the QoS information for application traffic includes: QoS requirements.

[0233] In some embodiments, the application information includes: VAL service identifier and VAL server ID.

[0234] In some embodiments, SEALDD server #1 grants authorization. If the request does not carry QoS parameters, SEALDD server #1 assigns a QoS parameter based on the VAL service identifier.

[0235] Operation 2: SEALDD server #1 sends a transmission response to VAL server #1.

[0236] Upon receiving a request, the SEALDD server performs an authorization check. If authorization is successful, it sends a response to the VAL server. If the VAL server does not provide QoS information, the SEALDD server can assign QoS parameters to application traffic of different service types based on the VAL service ID.

[0237] Operation 3: SEALDD enabled regular data transmission connection establishment.

[0238] Operation 4: Generate and detect data transmission quality.

[0239] SEALDD server #1 can trigger a transmission quality measurement and check whether the current transmission quality meets QoS requirements.

[0240] Operation 5: QoS monitoring subscription and trigger transmission quality guarantee.

[0241] In some embodiments, the S-SEALDD server subscribes to the QoS monitoring service for specific UEs associated with VAL users from the 5GC, in accordance with relevant technical specifications. When the S-SEALDD server diagnoses QoS degradation caused by N6 / SEALDD overload (i.e., based on QoS monitoring and end-to-end transmission quality measurement results between the UE and UPF), it can decide to trigger a data transmission quality assurance process (i.e., switch the connected SEALDD server according to the SEALDD service policy) based on the QoS monitoring and end-to-end transmission quality measurement results.

[0242] Operation 6: Available target SEALDD servers discovery.

[0243] SEALDD server #1 executes the target SEALDD server lookup process.

[0244] Operation 7: SEALDD server #1 sends a shared group information request to PIN server #1.

[0245] If the Sdd_Regular Transmission request contains a tethering group ID, the S-SEALDD server will send a tethering group information request to the PIN server. This request includes the tethering group ID.

[0246] Operation 8: PIN server #1 sends a shared group information response to SEALDD server #1.

[0247] In some embodiments, the PIN server sends a response to the S-SEALDD server, which includes at least one of the following: tethering group information, shared device identifiers (such as VAL UE ID or UE IP address), and a list of tethered device identifiers (such as MAC address).

[0248] Operation 9: Target SEALDD server selection.

[0249] In some embodiments, the S-SEALDD server may select a T-SEALDD server (i.e., SEALDD server #2) based on the N6 traffic and / or the performance of the available target SEALDD servers in Operation 6 (SEALDD server load).

[0250] Operation 10: SEALDD server #1 seamlessly switches the service flow of this device and its related devices to SEALDD server #2 and VAL server #2.

[0251] Based on the shared group information, the SEALDD relocation process will perform the following operations for each application traffic within this shared group: switch to the same SEALDD server group; switch to the same VAL server group.

[0252] Example 6: Tethered device information is stored in 5GC via SA2 NEF.

[0253] Refer to Figure 8. The specific operation is as follows:

[0254] Operation 0a: The Access and Mobility Management Function (AMF) establishes a UE Policy Association.

[0255] Operation 0b: The Policy Control Function (PCF) requests notification from the UDR regarding UE policy information.

[0256] Operation 1: The AF calls the Nnef_Service Parameter_Create to create a request, carrying the tethered device group information under this service;

[0257] In some embodiments, the tethered device group information includes, but is not limited to, at least one of the following: tethering device identifiers, and a list of tethered device identifiers;

[0258] In some embodiments, the tethering device identifier includes, but is not limited to, at least one of the following: VAL client identifier, GPSI, UE identifier.

[0259] In some embodiments, the tethered device identifier list includes, but is not limited to, at least one of the following: VAL client identifier, GPSI, UE identifier.

[0260] Operation 2: The AF sends a request to the Network Exposure Function (NEF), the NEF authorizes the request, and the NEF performs the following mapping:

[0261] - Map the AF service-identifier to the data network name (DNN) and single network slice selection assistance information (S-NSSAI).

[0262] - Map external application identifiers to internal network application identifiers.

[0263] Operation 3: NEF calls Nudm_SDM_Get to execute the following mapping:

[0264] - Based on information from Unified Data Management (UDM), GPSI is mapped to a Subscription Permanent Identifier (SUPI).

[0265] - Based on the information in the UDM, map the external group identifier to the internal group identifier.

[0266] Operation 4: NEF stores the AF request information in the "Application Data" of the UDR and associates it with an assigned Transaction Reference ID.

[0267] Operation 5: NEF sends a response to AF, carrying the assigned Transaction Reference ID.

[0268] Operation 6: When the PCF receives the Nudr_DM_Notify notification from the Unified Data Repository (UDR), for PIN or SEALDD services, the PCF generates a User Route Selection Policy (URSP) rule and carries the PIN identifier in the Traffic Descriptor.

[0269] Operation 7: PCF initiates the UE policy delivery process.

[0270] Operation 8: If the AF has subscribed to the UE Policy delivery notification, the PCF sends Npcf_Event Exposure_Notify to the NEF, carrying the SUPI and GPSI lists.

[0271] Operation 9: NEF performs information mapping and sends the response to AF.

[0272] SEALDD obtains tethered device binding information from 5GC through the Common Application Programming Interface Framework (CAPIF).

[0273] In immersive communication, a single UE (User Equipment) in an XR (Extended Reality) service may be connected to several composite devices, such as glasses, gloves, controllers, and fitness rings. In XR services, the network needs to understand the relationships between these composite devices to better ensure unified QoS and service flow correlation. This disclosure proposes a method to enhance the maintenance of the association mapping between composite devices through a SEALDD server, thus solving the problem of unknown relationships between composite devices.

[0274] Referring to Figure 9, an embodiment of this disclosure provides a communication processing apparatus applied to a first server. The apparatus 90 includes: a first transceiver unit 91;

[0275] The first transceiver unit 91 is configured to send first information to the second server, the first information being used to request second information, and the second information being used to indicate at least one of the following: a first device, a first device group, a first group, and a first association relationship.

[0276] In some embodiments of this disclosure, the first device group includes one or more first devices; and / or, the first group includes one or more first devices and second devices; and / or, the first association is used to indicate the association between the first devices and the second devices.

[0277] The first device is a 3GPP or non-3GPP device, and the second device is a 3GPP device.

[0278] In some embodiments of this disclosure, the first transceiver unit 91 is further configured to receive second information from the second server.

[0279] In some embodiments of this disclosure, the first device is a tethered device, and / or the second device is a tethering device.

[0280] In some embodiments of this disclosure, the first transceiver unit 91 is further configured to receive third information from a third server, the third information being used to indicate traffic transfer.

[0281] In some embodiments of this disclosure, the third information is at least one of the following: shared group identifier, group identifier, tethered group identifier, PINE group identifier, group information, device group information, and sharing policy information;

[0282] And / or,

[0283] The third information is used to indicate the association between the second device and the one or more first devices.

[0284] In some embodiments of this disclosure, the third information includes at least one of the following: device type, device list, VAL service identifier, shared device identifier, tethered device identifier, physical address (e.g., MAC address), UE IP address, and UE identifier;

[0285] The device type is used to indicate the type of the second device or the first device;

[0286] The device list includes at least one of the following: shared device identifier, tethered device identifier.

[0287] In some embodiments of this disclosure, the first transceiver unit 91 is further configured to be at least one of the following:

[0288] Obtain the Quality of Service (QoS) information of the first service, where the first service is a service associated with the first group;

[0289] Select the fourth server based on the traffic of the N6 interface and / or the load of the first server;

[0290] Send fourth information to the fourth server, the fourth information being used to indicate at least one of the following: information about the second device; information about the first device; information about the first service.

[0291] In some embodiments of this disclosure, the first information includes at least one of the following: the General Public User Identifier (GPSI) of the second device, and the Personal Internet of Things Identifier (IoT) of the second device.

[0292] In some embodiments of this disclosure, the second server includes a PIN server, and / or the first or fourth server includes a service enable architecture layer data transfer SEALDD server, and / or the third server includes a vertical application layer VAL server.

[0293] The apparatus provided in this disclosure can implement the various processes implemented in the method embodiment shown in FIG1 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0294] Referring to Figure 10, an embodiment of this disclosure provides a communication processing apparatus applied to a second server. The apparatus 100 includes a second transceiver unit 101.

[0295] The second transceiver unit 101 is configured to receive first information from a first server, the first information being used to request second information, the second information being used to indicate at least one of the following: a first device, a first device group, a first group, a first association relationship.

[0296] In some embodiments of this disclosure, the first device group includes one or more first devices; and / or, the first group includes one or more first devices and second devices; and / or, the first association is used to indicate an association between one or more first devices and second devices.

[0297] The first device is a 3GPP or non-3GPP device, and the second device is a 3GPP device.

[0298] In some embodiments of this disclosure, the second transceiver unit 101 is also configured to send the second information to the first server.

[0299] In some embodiments of this disclosure, the second transceiver unit 101 is further configured to receive fifth information, which is used to request the registration of a third device.

[0300] In some embodiments of this disclosure, the third device is a tethered device or a shared device.

[0301] In some embodiments of this disclosure, the second transceiver unit 101 is further configured to be at least one of the following:

[0302] Receive the fifth information sent by the third device;

[0303] The fifth information is received from a fourth device, which is a shared device of the third device.

[0304] In some embodiments of this disclosure, the fifth information includes at least one of the following: a security certificate, a general public user identifier of the third device, the physical address of the third device, a vendor name, device description information of the third device, a PINE address, a PINE type, a shared group indication, a shared group creation indication, a tethered identifier, a shared identifier, a VAL service identifier, and indication information for indicating registration.

[0305] In some embodiments of this disclosure, the second transceiver unit 101 is further configured to, when the PINE type is a shared device, perform at least one of the following: determine that the third device is a primary role Personal Internet of Things (PEMC) with management capabilities or a secondary role PEMC; and assign a shared group identifier to the device group to which the third device belongs.

[0306] or,

[0307] When the PINE type is a tethered device, perform at least one of the following: determine the shared device associated with the third device; determine the shared device associated with the third device based on the VAL service identifier; and store shared mapping information in the PIN configuration, the shared mapping information being used to indicate the association relationship between the third device and the shared device.

[0308] In some embodiments of this disclosure, the second transceiver unit 101 is further configured to obtain information about the first device according to the configuration of the second server.

[0309] In some embodiments of this disclosure, the configuration of the second server includes the association between the second device and the first device.

[0310] In some embodiments of this disclosure, the second server includes a PIN server, and / or the first server includes a SEALDD server, and / or the third device includes a PINE, and / or the fourth device includes a PEMC.

[0311] The apparatus provided in this disclosure can implement the various processes implemented in the method embodiment shown in FIG2 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0312] Referring to Figure 11, an embodiment of this disclosure provides a communication processing apparatus applied to a third device. The apparatus 110 includes a third transceiver unit 111.

[0313] The third transceiver unit 111 is configured to send fifth information to the second server, the fifth information being used to request the registration of a third device, the type of which is a tethered device or a shared device.

[0314] In some embodiments of this disclosure, the third transceiver unit 111 is further configured to be at least one of the following:

[0315] Send the fifth message directly to the second server;

[0316] The fifth message is sent to the second server via the fourth device.

[0317] In some embodiments of this disclosure, the fifth information includes at least one of the following: a security certificate, a general public user identifier of the third device, the physical address of the third device, a vendor name, device description information of the third device, a PINE address, a PINE type, a shared group indication, a shared group creation indication, a tethered identifier, a shared identifier, a VAL service identifier, and indication information for indicating registration.

[0318] The apparatus provided in this disclosure can implement the various processes implemented in the method embodiment shown in FIG3 and achieve the same technical effect. To avoid repetition, it will not be described again here.

[0319] As shown in Figure 12, this embodiment of the present disclosure also provides a communication device 1200, which includes a processor 1201, a memory 1202, and a program or instructions stored in the memory 1202 and executable on the processor 1201. When the program or instructions are executed by the processor 1201, they implement the various processes of the method embodiments shown in Figure 1, 2, or 3 above, and achieve the same technical effects. To avoid repetition, further details are omitted here.

[0320] This disclosure also provides a readable storage medium storing a program or instructions that, when executed by a processor, implement the various processes of the method embodiments shown in FIG1, FIG2, or FIG3 above, and achieve the same technical effect. To avoid repetition, these will not be described again here.

[0321] The processor mentioned above is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0322] The operation of the methods or algorithms described in this disclosure can be implemented in hardware or by executing software instructions on a processor. The software instructions can consist of corresponding software modules, which can be stored in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, external hard disk, read-only optical disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can be housed in an ASIC. Alternatively, the ASIC can be housed in a core network interface device. Of course, the processor and storage medium can also exist as discrete components in the core network interface device.

[0323] Those skilled in the art will recognize that the functions described in this disclosure in one or more of the examples above can be implemented using hardware, software, firmware, or any combination thereof. When implemented in software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium accessible to a general-purpose or special-purpose computer.

[0324] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of this disclosure. It should be understood that the above description is only a specific embodiment of this disclosure and is not intended to limit the scope of protection of this disclosure. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solution of this disclosure should be included within the scope of protection of this disclosure.

[0325] Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, systems, or computer program products. Therefore, embodiments of this disclosure can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, embodiments of this disclosure can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0326] This disclosure describes embodiments of methods, apparatus (systems), and computer program products according to embodiments of this disclosure with reference to flowchart illustrations and / or block diagrams. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more flowchart illustrations and / or one or more block diagrams.

[0327] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0328] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide operations for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0329] Obviously, those skilled in the art can make various modifications and variations to the embodiments of this disclosure without departing from the spirit and scope of this disclosure. Therefore, if these modifications and variations to the embodiments of this disclosure fall within the scope of the claims of this disclosure and their equivalents, this disclosure is also intended to include these modifications and variations.

Claims

1. A communication processing method, applied to a first server, comprising: Send first information to a second server, the first information being used to request second information, the second information being used to indicate at least one of the following: a first device, a first device group, a first group, a first association.

2. The method according to claim 1, wherein, The first device group includes one or more of the first devices; and / or, the first group includes one or more of the first devices and the second device; and / or, the first association is used to indicate the association between one or more of the first devices and the second device; The first device is a 3GPP or non-3GPP device, and the second device is a 3GPP device.

3. The method of claim 1, wherein, The method further includes: Receive the second information from the second server.

4. The method according to any one of claims 1 to 3, wherein, The first device is a tethered device, and / or the second device is a shared device.

5. The method according to any one of claims 1 to 4, wherein, The method further includes: Receive third information from a third server, the third information being used to indicate the transmission of data.

6. The method of claim 5, wherein, The third piece of information is at least one of the following: shared group identifier, group identifier, tethered group identifier, PINE group identifier of personal Internet of Things network element, group information, device group information, and sharing policy information; And / or, The third information is used to indicate the association between the second device and one or more of the first devices.

7. The method of claim 6, wherein, The third information includes at least one of the following: device type, device list, vertical application layer VAL service identifier, shared device identifier, tethered device identifier, physical address, UE IP address, and UE identifier; The device type is used to indicate the type of the second device or the first device; The device list includes at least one of the following: shared device identifier, tethered device identifier.

8. The method according to any one of claims 1 to 7, wherein, The method further includes at least one of the following: Obtain the Quality of Service (QoS) information of the first service, where the first service is a service associated with the first group; Select the fourth server based on the traffic of the N6 interface and / or the load of the first server; Send fourth information to the fourth server, the fourth information being used to indicate at least one of the following: information about the second device; information about the first device; information about the first service.

9. The method according to any one of claims 1 to 8, wherein, The first information includes at least one of the following: the General Public User Identifier (GPSI) of the second device, and the Personal Internet of Things Identifier (IoT) of the second device.

10. The method according to any one of claims 1 to 9, wherein, The second server includes a PIN server, and / or the first server or the fourth server includes a service enable architecture layer data transfer SEALDD server, and / or the third server includes a VAL server.

11. A communication processing method, applied to a second server, comprising: Receive first information from a first server, the first information being used to request second information, the second information being used to indicate at least one of the following: a first device, a first device group, a first group, and a first association.

12. The method according to claim 11, wherein, The first device group includes one or more of the first devices; and / or, the first group includes one or more of the first devices and the second device; and / or, the first association is used to indicate the association between one or more of the first devices and the second device; The first device is a 3GPP or non-3GPP device, and the second device is a 3GPP device.

13. The method of claim 11 or 12, wherein, The method further includes: Send the second information to the first server.

14. The method according to any one of claims 11 to 13, wherein, The method further includes: Receive the fifth message, which is used to request the registration of a third device.

15. The method of claim 14, wherein, The type of the third device is either a tethered device or a shared device.

16. The method according to any one of claims 11 to 15, wherein, Receive the fifth message, including at least one of the following: Receive the fifth information sent by the third device; The fifth information is received from a fourth device, which is a shared device of the third device.

17. The method according to any one of claims 14 to 16, wherein, The fifth piece of information includes at least one of the following: security certificate, the general public user identifier of the third device, the physical address of the third device, the vendor name, the device description information of the third device, the PINE address, the PINE type, the shared group indication, the shared group creation indication, the tethering identifier, the shared identifier, the VAL service identifier, and indication information for indicating registration.

18. The method of claim 17, wherein, The method further includes: When the PINE type is a shared device, perform at least one of the following: determine that the third device is a primary role Personal Internet of Things (PEMC) with management capabilities or a secondary role PEMC; assign a shared group identifier to the device group to which the third device belongs; or, When the PINE type is the tethered device, perform at least one of the following: determine the shared device associated with the third device; determine the shared device associated with the third device based on the VAL service identifier; and store shared mapping information in the PIN configuration, the shared mapping information being used to indicate the association relationship between the third device and the shared device.

19. The method according to any one of claims 11 to 18, wherein, The method further includes: Based on the configuration of the second server, obtain information about the first device.

20. The method of claim 19, wherein, The configuration of the second server includes the association between the second device and the first device.

21. The method of any one of claims 11 to 20, wherein, The second server includes a PIN server, and / or the first server includes a SEALDD server, and / or the third device includes a PINE, and / or the fourth device includes a PEMC.

22. A communication processing method applied to a third device, comprising: A fifth message is sent to the second server, the fifth message being used to request the registration of a third device, the type of which is a tethered device or a shared device.

23. The method of claim 22, wherein, Send a fifth message to the second server, including at least one of the following: The fifth message is sent directly to the second server; The fifth message is sent to the second server via the fourth device.

24. The method of claim 22 or 23, wherein, The fifth piece of information includes at least one of the following: security certificate, the general public user identifier of the third device, the physical address of the third device, the vendor name, the device description information of the third device, the PINE address, the PINE type, the shared group indication, the shared group creation indication, the tethering identifier, the shared identifier, the VAL service identifier, and indication information for indicating registration.

25. A communication processing apparatus applied to a first server, comprising: First transceiver unit; The first transceiver unit is configured to send first information to the second server, the first information being used to request second information, and the second information being used to indicate at least one of the following: a first device, a first device group, a first group, and a first association relationship.

26. A communication processing apparatus applied to a second server, comprising: Second transceiver unit; The second transceiver unit is configured to receive first information from a first server, the first information being used to request second information, the second information being used to indicate at least one of the following: a first device, a first device group, a first group, and a first association relationship.

27. A communication processing apparatus applied to a third device, comprising: Third transceiver unit; The third transceiver unit is configured to send fifth information to the second server. The fifth information is used to request the registration of a third device, which is either a tethered device or a shared device.

28. A communication device comprising a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the method as claimed in any one of claims 1 to 10, or the method as claimed in any one of claims 11 to 21, or the method as claimed in any one of claims 22 to 24.

29. A readable storage medium on which a program or instructions are stored, which, when executed by a processor, implement the method as claimed in any one of claims 1 to 10, or the method as claimed in any one of claims 11 to 21, or the method as claimed in any one of claims 22 to 24.

30. A computer program product comprising computer instructions that, when executed by a processor, implement the method as claimed in any one of claims 1 to 10, or the method as claimed in any one of claims 11 to 21, or the method as claimed in any one of claims 22 to 24.