Communication method and apparatus, network element, communication system, storage medium, and program product

Abstract

The present disclosure relates to a communication method and apparatus, a network element, a communication system, a storage medium, and a program product. The method is executed by a first network element. The method comprises: sending first information, wherein the first information is used for indicating a function associated with a relay for encrypted XR. By means of the solution of the present disclosure, QoS processing for encrypted data streams is implemented.

Description

Communication method and device, network element, communication system, storage medium and program product Technical Field

[0001] The present disclosure relates to the field of wireless communications, and in particular to a communication method and apparatus, a network element, a communication system, a storage medium, and a program product. Background Art

[0002] In a communication system, a packet data unit (PDU) set can be used to provide quality of service (QoS) assurance for extended reality for multimedia (XRM) services.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure relate to a communication method and apparatus, a network element, a communication system, a storage medium, and a program product, thereby supporting QoS processing of encrypted data streams.

[0005] According to a first aspect of an embodiment of the present disclosure, a communication method is provided. The method is performed by a first network element. The method includes: sending first information, wherein the first information is used to indicate a function associated with relaying encrypted XR.

[0006] According to a second aspect of an embodiment of the present disclosure, a communication method is provided. The method is performed by a fifth network element. The method includes: receiving first information, wherein the first information is used to indicate a function associated with relaying encrypted XR.

[0007] According to a third aspect of an embodiment of the present disclosure, a first network element is provided. The first network element includes a transceiver module. The transceiver module is configured to: send first information, wherein the first information is used to indicate a function associated with relaying encrypted XR.

[0008] According to a fourth aspect of an embodiment of the present disclosure, a fifth network element is provided. The fifth network element includes a transceiver module. The transceiver module is configured to: receive first information, wherein the first information is used to indicate a function associated with relaying encrypted XR.

[0009] According to a fifth aspect of an embodiment of the present disclosure, a communication device is provided. The communication device includes: one or more processors; and a memory storing instructions. When the instructions are executed by the communication device, the communication device implements the communication method described in the first aspect.

[0010] According to a sixth aspect of an embodiment of the present disclosure, a communication device is provided. The communication device includes: one or more processors; and a memory storing instructions. When the instructions are executed by the communication device, the communication device implements the communication method described in the second aspect.

[0011] According to a seventh aspect of an embodiment of the present disclosure, a communication system is provided. The communication system includes a first network element and a fifth network element. The first network element is configured to implement the communication method described in the first aspect. The fifth network element is configured to implement the communication method described in the second aspect.

[0012] According to an eighth aspect of an embodiment of the present disclosure, a storage medium is provided. The storage medium stores instructions. When the instructions are executed on a communication device, the communication device executes the communication method described in the first aspect or the second aspect.

[0013] According to a ninth aspect of the embodiments of the present disclosure, a program product is provided, which, when executed by a communication device, causes the communication device to execute the communication method as described in the first or second aspect.

[0014] According to a tenth aspect of the embodiments of the present disclosure, a computer program is provided, which, when executed on a computer, causes the computer to execute the communication method according to the first aspect or the second aspect.

[0015] According to an eleventh aspect of the embodiments of the present disclosure, a chip or chip system is provided. The chip or chip system includes a processing circuit. The processing circuit is configured to execute the communication method described in the first aspect or the second aspect.

[0016] According to the embodiments of the present disclosure, relay for encrypted XR can be achieved.

[0017] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory and do not constitute limitations on the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present invention and, together with the description, serve to explain the principles of the embodiments of the present invention.

[0019] FIG1A is a schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0020] FIG1B is a schematic diagram of an architecture of an exemplary implementation of a communication system provided according to an embodiment of the present disclosure.

[0021] FIG1C is a schematic diagram of an architecture of an exemplary implementation of a communication system provided according to an embodiment of the present disclosure.

[0022] FIG2A is an exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure.

[0023] FIG2B is an exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure.

[0024] FIG2C is an exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure.

[0025] FIG3A is an exemplary flowchart of a communication method provided according to an embodiment of the present disclosure.

[0026] FIG3B is an exemplary flowchart of a communication method provided according to an embodiment of the present disclosure.

[0027] FIG3C is an exemplary flowchart of a communication method provided according to an embodiment of the present disclosure.

[0028] FIG4 is an exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure.

[0029] FIG5A is an exemplary interaction diagram of a specific implementation of a communication method provided according to an embodiment of the present disclosure.

[0030] FIG5B is an exemplary interaction diagram of a specific implementation of a communication method provided according to an embodiment of the present disclosure.

[0031] FIG5C is an exemplary interaction diagram of a specific implementation of a communication method provided according to an embodiment of the present disclosure.

[0032] FIG5D is an exemplary interaction diagram of a specific implementation of a communication method provided according to an embodiment of the present disclosure.

[0033] FIG6 is an exemplary structural diagram of a communication device provided according to an embodiment of the present disclosure.

[0034] FIG7A is a schematic structural diagram of a communication device according to an embodiment of the present disclosure.

[0035] FIG7B is a schematic structural diagram of a chip provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0036] Embodiments of the present disclosure provide a communication method and apparatus, a network element, a communication system, a storage medium, and a program product.

[0037] In a first aspect, embodiments of the present disclosure provide a communication method. The method is performed by a first network element. The method includes: sending first information, wherein the first information is used to indicate a function associated with relaying encrypted XR.

[0038] Through this embodiment, the first network element can indicate the function associated with the relay of encrypted XR by sending the first information, thereby obtaining a second network element that supports the function associated with the relay of encrypted XR. In this way, the first network element can discover, select or reselect the second network element that supports the function associated with the relay of encrypted XR, and trigger the second network element to implement the relay of encrypted XR.

[0039] In combination with some embodiments of the first aspect, in some embodiments, the functions associated with relaying of encrypted XR include at least one of the following: relaying of end-to-end encrypted XRM services; and identification of PDU set information based on encrypted services.

[0040] Through this embodiment, the functions associated with the relay of encrypted XR can include the relay of end-to-end encrypted XRM services and can also include the identification of PDU set information based on the encrypted services. In this way, for encrypted XR services, the relay of XRM services and / or the identification of PDU set information can be implemented, thereby achieving the relay of encrypted XR data streams.

[0041] In combination with some embodiments of the first aspect, in some embodiments, the PDU set information based on the encryption service may include at least one of the following: PDU set sequence number; the end PDU of the PDU set; the PDU sequence number within the PDU set; the number of PDUs within the PDU set; the importance of the PDU set; the PDU set size; and the data burst end indication.

[0042] In combination with some embodiments of the first aspect, in some embodiments, the first information can be used for at least one of the following: discovery of the second network element; selection of the second network element; and reselection of the second network element.

[0043] Through this embodiment, the first information for indicating the function associated with the relay of encrypted XR can be used for discovery, selection, and reselection of the second network element, so that the discovered, selected, and reselected second network element supports the relay of encrypted XR.

[0044] In combination with some embodiments of the first aspect, in some embodiments, the first information may be carried in at least one of the following: a subscription message; an N4 association establishment request message; an N4 association establishment response message; or an N4 session establishment request message.

[0045] Through this embodiment, the first information can be carried in messages of different interaction processes. In this way, functions associated with relaying of encrypted XR can be implemented in different interaction processes.

[0046] In combination with some embodiments of the first aspect, in some embodiments, the operation of sending the first information may include at least one of the following: sending the first information to the second network element; sending the first information to the third network element.

[0047] In combination with some embodiments of the first aspect, in some embodiments, the above method may further include: receiving second information, wherein the second information is used to indicate that the second network element supports functions associated with relaying of encrypted XR.

[0048] In combination with some embodiments of the first aspect, in some embodiments, the second information can be carried in at least one of the following: a notification message; an N4 association establishment request message; an N4 association establishment response message; or an N4 session establishment response message.

[0049] In combination with some embodiments of the first aspect, in some embodiments, the functions associated with the relay of encrypted XR can be determined based on at least one of the following: third information for indicating functional requirements associated with the relay of encrypted XR; OAM configuration; operator policy; local configuration; S-NSSAI; DNN; XRM business capabilities.

[0050] Through this embodiment, the first network element can determine the functions associated with the relay of encrypted XR for specific OAM configuration, operator policy, local configuration, S-NSSAI, DNN, XRM service capabilities, etc.

[0051] In combination with some embodiments of the first aspect, in some embodiments, the function associated with the encrypted XR may be determined based on at least the third information; the above method may further include: receiving the third information sent by the fourth network element.

[0052] In this embodiment, the third information from the fourth network element can be used to determine the functions associated with the encrypted XR. In this way, the first network element can determine the functions associated with the encrypted XR according to the instructions of the fourth network element, so that the determined second network element supports the functions associated with the encrypted XR required by the fourth network element.

[0053] In combination with some embodiments of the first aspect, in some embodiments, the fourth network element may be a PCF; wherein the third information may be used for PDU session binding.

[0054] In a second aspect, embodiments of the present disclosure provide a communication method. The method is performed by a fifth network element. The method includes receiving first information, wherein the first information is used to indicate a function associated with relaying encrypted XR.

[0055] Through this embodiment, the first network element can indicate the function associated with the relay of encrypted XR by sending the first information. The fifth network element can then provide the first network element with a second network element that supports the function associated with the relay of encrypted XR based on the received first information. In this way, the first network element can discover, select, or reselect the second network element that supports the function associated with the relay of encrypted XR, and trigger the second network element to implement the relay of encrypted XR.

[0056] In combination with some embodiments of the second aspect, in some embodiments, the functions associated with the relay of encrypted XR may include at least one of the following: relay of end-to-end encrypted XRM services; identification of PDU set information based on encrypted services.

[0057] In combination with some embodiments of the second aspect, in some embodiments, the PDU set information based on the encryption service may include at least one of the following: PDU set sequence number; the end PDU of the PDU set; the PDU sequence number within the PDU set; the number of PDUs within the PDU set; the importance of the PDU set; the PDU set size; and the data burst end indication.

[0058] In combination with some embodiments of the second aspect, in some embodiments, the first information is used for at least one of the following: discovery of the second network element; selection of the second network element; and reselection of the second network element.

[0059] In combination with some embodiments of the second aspect, in some embodiments, the first information is carried in at least one of the following: a subscription message; an N4 association establishment request message; an N4 association establishment response message; or an N4 session establishment request message.

[0060] In combination with some embodiments of the second aspect, in some embodiments, the above method may further include: sending second information, wherein the second information is used to indicate that the second network element supports functions associated with relaying of encrypted XR.

[0061] In combination with some embodiments of the second aspect, in some embodiments, the second information can be carried in at least one of the following: a notification message; an N4 association establishment request message; an N4 association establishment response message; or an N4 session establishment response message.

[0062] In combination with some embodiments of the second aspect, in some embodiments, the fifth network element includes one of the following: UPF; NRF.

[0063] In a third aspect, embodiments of the present disclosure provide a first network element, including a transceiver module configured to send first information indicating a function associated with relaying encrypted XR.

[0064] In combination with some embodiments of the third aspect, in some embodiments, the functions associated with the relay of encrypted XR include at least one of the following: relay of end-to-end encrypted XRM services; identification of PDU set information based on encrypted services.

[0065] In combination with some embodiments of the third aspect, in some embodiments, the PDU set information based on the encryption service may include at least one of the following: PDU set sequence number; the end PDU of the PDU set; the PDU sequence number within the PDU set; the number of PDUs within the PDU set; the importance of the PDU set; the PDU set size; and the data burst end indication.

[0066] In combination with some embodiments of the third aspect, in some embodiments, the first information can be used for at least one of the following: discovery of the second network element; selection of the second network element; and reselection of the second network element.

[0067] In combination with some embodiments of the third aspect, in some embodiments, the first information can be carried in at least one of the following: a subscription message; an N4 association establishment request message; an N4 association establishment response message; or an N4 session establishment request message.

[0068] In combination with some embodiments of the third aspect, in some embodiments, the transceiver module can be configured to perform at least one of the following: sending the first information to the second network element; sending the first information to the third network element.

[0069] In combination with some embodiments of the third aspect, in some embodiments, the transceiver module may further be configured to: receive second information, wherein the second information is used to indicate that the second network element supports functions associated with relaying of encrypted XR.

[0070] In combination with some embodiments of the third aspect, in some embodiments, the second information can be carried in at least one of the following: a notification message; an N4 association establishment request message; an N4 association establishment response message; or an N4 session establishment response message.

[0071] In combination with some embodiments of the third aspect, in some embodiments, the functions associated with the relay of encrypted XR can be determined based on at least one of the following: third information for indicating functional requirements associated with the relay of encrypted XR; OAM configuration; operator policy; local configuration; S-NSSAI; DNN; XRM business capabilities.

[0072] In combination with some embodiments of the third aspect, in some embodiments, the function associated with the encrypted XR can be determined at least based on the third information; the transceiver module can also be configured to: receive the third information sent by the fourth network element.

[0073] In combination with some embodiments of the third aspect, in some embodiments, the fourth network element may be a PCF; wherein the third information may be used for PDU session binding.

[0074] In a fourth aspect, embodiments of the present disclosure provide a fifth network element, including a transceiver module configured to receive first information indicating a function associated with relaying encrypted XR.

[0075] In combination with some embodiments of the fourth aspect, in some embodiments, the functions associated with the relay of encrypted XR may include at least one of the following: relay of end-to-end encrypted XRM services; identification of PDU set information based on encrypted services.

[0076] In combination with some embodiments of the fourth aspect, in some embodiments, the PDU set information based on the encryption service may include at least one of the following: PDU set sequence number; the end PDU of the PDU set; the PDU sequence number within the PDU set; the number of PDUs within the PDU set; the importance of the PDU set; the PDU set size; and the data burst end indication.

[0077] In combination with some embodiments of the fourth aspect, in some embodiments, the first information is used for at least one of the following: discovery of the second network element; selection of the second network element; and reselection of the second network element.

[0078] In combination with some embodiments of the fourth aspect, in some embodiments, the first information is carried in at least one of the following: a subscription message; an N4 association establishment request message; an N4 association establishment response message; or an N4 session establishment request message.

[0079] In combination with some embodiments of the fourth aspect, in some embodiments, the transceiver module can also be configured to: send second information, wherein the second information is used to indicate that the second network element supports functions associated with the relay of encrypted XR.

[0080] In combination with some embodiments of the fourth aspect, in some embodiments, the second information can be carried in at least one of the following: a notification message; an N4 association establishment request message; an N4 association establishment response message; or an N4 session establishment response message.

[0081] In combination with some embodiments of the fourth aspect, in some embodiments, the fifth network element includes one of the following: UPF; NRF.

[0082] In a fifth aspect, embodiments of the present disclosure provide a communication device. The communication device includes: one or more processors; and a memory storing instructions. When the instructions are executed by the communication device, the communication device implements the communication method as described in any one of the first aspect and possible embodiments thereof.

[0083] In a sixth aspect, embodiments of the present disclosure provide a communication device. The communication device includes: one or more processors; and a memory storing instructions. When the instructions are executed by the communication device, the communication device implements the communication method as described in any one of the second aspect and possible embodiments thereof.

[0084] In a seventh aspect, embodiments of the present disclosure provide a communication system. The communication system includes a first network element and a fifth network element. The first network element is configured to implement the communication method described in any one of the first aspect and possible embodiments thereof. The fifth network element is configured to implement the communication method described in any one of the second aspect and possible embodiments thereof.

[0085] In an eighth aspect, an embodiment of the present disclosure provides a storage medium storing instructions that, when executed on a communication device, cause the communication device to execute the communication method as described in any one of the first aspect, the second aspect, and possible embodiments thereof.

[0086] In a ninth aspect, an embodiment of the present disclosure provides a program product. When the program product is executed by a communication device, the communication device executes the communication method as described in any one of the first aspect, the second aspect, and possible embodiments thereof.

[0087] In a tenth aspect, an embodiment of the present disclosure provides a computer program. When the computer program is executed on a computer, the computer executes the communication method as described in any one of the first aspect, the second aspect, and possible embodiments thereof.

[0088] In an eleventh aspect, an embodiment of the present disclosure provides a chip or a chip system. The chip or chip system includes a processing circuit. The processing circuit is configured to execute the communication method as described in any one of the first aspect, the second aspect, and possible embodiments thereof.

[0089] It is understandable that the above network elements, communication devices, communication systems, storage media, program products, computer programs, chips, and chip systems are all used to perform the methods provided by the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0090] The present disclosure provides a communication method and apparatus, a network element, a communication system, a storage medium, and a program product. In some embodiments, the terms communication method, information processing method, and information transmission method are interchangeable; the terms network element, network device, network function, and network entity are interchangeable; and the terms communication system and information processing system are interchangeable.

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

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

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

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

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

[0096] In some embodiments, the terms "at least one", "one or more", etc. can be used interchangeably.

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

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

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

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

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

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

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

[0104] In some embodiments, "network" can be interpreted as devices included in the network (e.g., access network devices, core network devices, etc.). For example, a network device may include at least one access network device. For another example, a network device may include at least one core network device. For another example, a network device may include at least one access network device and at least one core network device.

[0105] In some embodiments, the core network device may include at least one network element. Then, the network device including the core network device means that the network device may include at least one network element.

[0106] In some embodiments, the terms "access network device (AN device)", "radio access network device (RAN device)", "base station (BS)", "radio base station" "fixed station", "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)" "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)" and the like may be used interchangeably.

[0107] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc. can be used interchangeably.

[0108] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0109] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

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

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

[0112] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0113] FIG1A is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG1A , a communication system 100 includes a terminal 101 , an access network device 102 , and a core network device 103 .

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

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

[0116] In some embodiments, the terminal 101 and the core network device 103 may interact through the access network device 102. In some embodiments, the terminal 101 and the core network device 103 may interact directly. This is not specifically limited in the embodiments of the present disclosure.

[0117] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0118] In some embodiments, the access network device 102 can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0119] In some embodiments, the core network device 103 may be a device including one or more network elements, or may be multiple devices or device groups, each including all or part of the one or more network elements. The network element may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0120] As shown in FIG. 1A , the core network device 103 may include at least one of the following: a first network element 1031 , a second network element 1032 , a third network element 1033 , a fourth network element 1034 , and a sixth network element 1036 .

[0121] In some embodiments, the first network element 1031 may be, for example, a session management function (SMF).

[0122] In some embodiments, the first network element 1031 can be used to implement session management functions, mainly performing session management, execution of PCF control policies, UPF selection, UE Internet Protocol (IP) address allocation and other functions, the name is not limited to this.

[0123] In some embodiments, the second network element 1032 may be, for example, a user plane function (UPF).

[0124] In some embodiments, the second network element 1032 can be used to implement functions such as user plane (UP) data forwarding, session / flow-level billing statistics, bandwidth limitation, UP QoS processing, etc., and the name is not limited thereto.

[0125] In some embodiments, the third network element 1033 may be, for example, a network repository function (NRF). In this case, the third network element 1033 and the second network element 1032 may be different network elements.

[0126] In some embodiments, the third network element 1033 can be used to implement service discovery functions, and is mainly responsible for network function service registration, status monitoring, etc., and the name is not limited to this.

[0127] In some embodiments, the third network element 1033 and the second network element 1032 may be different network elements.

[0128] In some embodiments, the fourth network element 1034 may be, for example, another network element in the core network other than the first network element 1031 , the second network element 1032 , and the third network element 1033 .

[0129] In some embodiments, the fourth network element 1034 may be, for example, a policy control function (PCF).

[0130] In some embodiments, the fourth network element 1034 can be used to implement policy control functions, and is mainly responsible for policy decisions related to charging policies, QoS bandwidth guarantees and policies for sessions and business flows, and the name is not limited to this.

[0131] In some embodiments, the fourth network element 1034 may be, for example, an application function (AF).

[0132] In some embodiments, the fourth network element 1034 may be used to provide policy management for business services, but the name is not limited thereto.

[0133] In some embodiments, the fourth network element 1034 may be, for example, a UPF. In this case, the fourth network element 1034 and the second network element 1032 may be different UPFs.

[0134] In some embodiments, the fourth network element 1034 may be, for example, operation, administration and maintenance (OAM).

[0135] In some embodiments, the fourth network element 1034 can be used to complete network management according to the actual needs of the operator's network operation, and is mainly responsible for OAM discovery, link monitoring, remote fault indication, remote loopback testing, and scalability, but the name is not limited to this.

[0136] In some embodiments, the fourth network element 1034 may be, for example, a unified data management (UDM).

[0137] In some embodiments, the fourth network element 1034 may be responsible for the management of user identification, subscription data, authentication data, and service network element registration management of the user.

[0138] In some embodiments, the fourth network element 1034 may be, for example, an access and mobility management function (AMF).

[0139] In some embodiments, the fourth network element 1034 may be responsible for registration management, connection management, and mobility management, but the names are not limited thereto.

[0140] In some embodiments, the fourth network element 1034 may be deployed in the core network or independently of the core network.

[0141] In some embodiments, the sixth network element 1036 may be, for example, an OAM.

[0142] In some embodiments, the communication system 100 may be a 5G communication system. It should be noted that the communication system 100 may also be other communication systems, such as a 4G communication system or a 6G communication system, which is not specifically limited in the present disclosure.

[0143] 1B and 1C , the architecture of a communication system is exemplarily described by taking a 5G communication system as an example, wherein the terminal 101 may be a UE and the access network device 102 may be a RAN.

[0144] Figure 1B is a schematic diagram of an architecture of an implementation of a communication system according to an embodiment of the present disclosure. As shown in Figure 1B, the architecture of the 5G communication system is presented in the form of reference points.

[0145] N1 is the reference point between the UE and the AMF. N2 is the reference point between the RAN and the AMF. N3 is the reference point between the RAN and the UPF. N4 is the reference point between the SMF and the UPF. N5 is the reference point between the PCF and the AF. N6 is the reference point between the UPF and the data network (DN). N7 is the reference point between the SMF and the PCF. N8 is the reference point between the UDM and the AMF. N10 is the reference point between the UDM and the SMF. N11 is the reference point between the AMF and the SMF. N15 is the reference point between the SMF and the PCF. Uu is the interface between the UE and the RAN.

[0146] It should be noted that NEF and UDR are not shown in FIG1B , but each network element in the communication system can interact with UDR and NEF.

[0147] Figure 1C is a schematic diagram of the architecture of another implementation of a communication system according to an embodiment of the present disclosure. As shown in Figure 1B, the architecture of the 5G communication system is presented in a service-based interface manner.

[0148] Namf is a service-based interface provided by AMF. Nsmf is a service-based interface provided by SMF. Nnef is a service-based interface provided by NEF. Npcf is a service-based interface provided by PCF. Nudm is a service-based interface provided by UDM. Naf is a service-based interface provided by AF.

[0149] It should be noted that the UDR is not shown in FIG. 1C , but the UDR may provide a service-based interface Nudr.

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

[0151] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1A , or some of the entities in the communication system 100 , but are not limited thereto. The entities shown in FIG1A are illustrative only. The communication system 100 may include all or some of the entities shown in FIG1A , or may include other entities other than those shown in FIG1A . The number and form of the entities are arbitrary. The entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

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

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

[0154] The embodiments of the present disclosure may be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-Wideband (UWB), and other technologies. Band (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems using other communication methods, and next-generation systems based on and extending these methods. Furthermore, a combination of multiple systems (for example, a combination of LTE or LTE-A with 5G) may also be applied.

[0155] In some cases, services such as mobile media services, online AR / VR and other XR services, online gaming, and video-based remote control of machines or drones are expected to contribute increasingly high traffic volumes to communication networks. XR services involve multimodal data streams. Multimodal data is data describing the same service / application that is input from the same device or different devices (including sensors) and may be output to one or more destination devices. The data streams within multimodal data often have some, or even strong, correlation, such as synchronization between audio and video streams, or between touch and vision. These media services share common characteristics within their data streams, between data streams, and in terms of the network transmission requirements. Effectively identifying and leveraging these characteristics will facilitate network and service transmission and control, as well as enhance service assurance and user experience.

[0156] In further cases, XRM services and interactive media services require the communication system to comprehensively consider the QoS characteristics of service data flows. Such QoS characteristics may include, for example, at least one of the following: whether parameters such as delay-sensitive guaranteed bit rate (GBR) data flows, guaranteed flow bit rate (GFBR), packet delay budget (PDB), and default maximum data burst volume (MDBV) can be simultaneously met and coordinated. It also involves multiple XRM data flows of a terminal, and XRM data flows of multiple terminals, and the consistency of QoS authorization and execution between each other.

[0157] In some embodiments, the service data flow (SDF) of the XRM may support PDU set-based processing, thereby enhancing QoS awareness and assurance of the SDF and improving the user's quality of experience (QoE).

[0158] In some embodiments, in systems such as 4G, 5G, 6G, and V2X, the AF may provide PDU set QoS parameters and a protocol description. In some embodiments, the PDU set QoS parameters may include at least one of the following: a PDU set control indication, a PDU set delay budget (PSDB), a PDU set error rate (PSER), and a PDU set integrated handling information (PSIHI). Then, the SMF and the UPF may extend the header of the PDU in the PDU set of the SDF in combination with the protocol description and protocol header extension provided by the AF to carry the PDU set information. The PDU information carried may be used by the access network to perform PDU set-based QoS control.

[0159] In some embodiments, the PDU set information may include at least one of the following: a PDU set sequence number, a start PDU or end PDU of a PDU set, a PDU sequence number within a PDU set, the number of PDUs within a PDU set, PDU set importance, PDU set size, and an end of data burst (EDB) indication. The PDU set importance is used to characterize the importance of a PDU set relative to other PDU sets in the same QoS flow. The end of data burst indication may be used to indicate / mark the end of a data burst transmission.

[0160] It can be understood that the UPF performs the mapping of the SDF to the QoS flow based on the PDR, and maps (also referred to as encapsulating) the mutually related PDUs into the PDU set. In addition, the UPF can adopt the same QoS policy for all PDU sets in the QoS flow. For example, the UPF can apply the same PDU set QoS parameters to all PDU sets in the QoS flow. In one example, the UPF can map the application flow to the QoS flow based on the packet detection information in the PDR. Some PDUs in the QoS flow can be associated with media components (for example, intra-frame coded frames and predicted frames), and the UPF classifies these PDUs as belonging to the PDU set and performs corresponding control.

[0161] In some cases, the XRM service may be a multimedia type service, corresponding to multiple data streams. These data streams may be multiplexed in the same 5tuple for transmission. The 5tuple constitutes an end-to-end transport layer connection. In this case, one or more data streams multiplexed in an end-to-end transport layer connection (e.g., a 5tuple) may be referred to as multiplexed data streams. In one example, the 5tuple may be a 5tuple that complies with the quick UDP internet connections (QUIC) protocol. In some embodiments, different data streams of the XRM service may have different QoS requirements. Then, different data streams may be transmitted using different QUIC connections or different QUIC streams.

[0162] For media transmission, media over QUIC can be used to achieve low-latency media transmission. The basic data element of media over QUIC transfer (MoQT) is the object. An object consists of two parts: metadata and payload. Metadata is unencrypted and visible to the relay. The payload is encrypted and only visible to the two parties in the end-to-end communication. Therefore, this requires the QoS architecture of the communication system to provide support for QoS processing of encrypted data streams.

[0163] Figure 2A is an exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method, which is applied to a communication system 100. As shown in Figure 2A, the method includes steps S2101 to S2108.

[0164] In step S2101 , the fourth network element 1034 sends third information to the first network element 1031 .

[0165] In some embodiments, the fourth network element 1034 may send third information.

[0166] In some embodiments, the first network element 1031 may receive third information.

[0167] In some embodiments, the third information may be used to indicate functional requirements associated with the relaying of the encrypted XR.

[0168] In some embodiments, the third information may be used to indicate relay support for end-to-end encrypted XRM traffic identification.

[0169] In some embodiments, the third information may be used for discovery, selection, reselection, etc. of a UPF / UPF instance.

[0170] In some embodiments, the name of the third information is not limited, and it can be, for example, a relay support indication, a relay support notification, etc.

[0171] In some embodiments, the fourth network element 1034 may include at least one of the following: AF, PCF, AMF, UDM, OAM, UPF.

[0172] In some embodiments, the fourth network element 1034 may be an AF. In one example, the AF may send a relay support indication to the first network element 1031. For example, the AF may send a final support indication to the first network element 1031 via a network element such as a PCF. In one example, the relay support indication may be used to indicate relay support for end-to-end encrypted XRM service identification. In one example, the relay support indication may be used for the discovery, selection, and reselection of a UPF / UPF instance.

[0173] In some embodiments, the fourth network element 1034 may be a PCF. In one example, the PCF may send a relay support indication to the first network element 1031. In one example, the relay support indication may be included in a policy and charging control (PCC) rule. For example, the PCF may send a PCC rule to the first network element 1031. The PCC rule may include a relay support indication. In one example, the relay support indication may be used to indicate relay support for end-to-end encrypted XRM service identification. For example, the relay support indication may be used to indicate policy and QoS requirements for relay support for end-to-end encrypted XRM service identification.

[0174] In some embodiments, the fourth network element 1034 may be a PCF, and the third information may be used for PDU session binding.

[0175] In some embodiments, the fourth network element 1034 may indicate, through the third information, that the AF session is bound to the PDU session. In one example, for a specific AF session, the fourth network element 1034 may discover at least one first network element 1031 and / or at least one second network element 1032. The PDU sessions managed by the first network element 1031 and / or the second network element 1032 discovered by the fourth network element 1034 may fully or partially adopt the function of end-to-end encrypted XR relay. In other words, the second network element 1032 managed by the first network element 1031 discovered by the fourth network element 1034 may support end-to-end encrypted XR relay, and / or the second network element 1032 discovered by the fourth network element 1034 may support end-to-end encrypted XR relay. In this case, the third information may be used to indicate that the AF session is bound to a PDU session that adopts the function of end-to-end encrypted XR relay.

[0176] In some embodiments, the first network element 1031 may be selected and / or discovered by the fourth network element 1034 .

[0177] In some embodiments, PDU session binding may be implemented by the fourth network element 1034 via a BSF (binding support function).

[0178] In some embodiments, PDU session binding may be implemented by the fourth network element 1034 based on local storage information or local configuration information.

[0179] In some embodiments, the fourth network element 1034 may be a UPF. In one example, the fourth network element 1034 may be an old UPF. Accordingly, the first network element 1031 may be a new UPF. For example, the old UPF may send a relay support indication to the first network element 1031. In one example, the fourth network element 1034 may be a serving UPF. Accordingly, the first network element 1031 may be a target UPF. For example, the serving UPF may send a relay support indication to the first network element 1031.

[0180] In some embodiments, the fourth network element 1034 may be an OAM. In one example, the OAM may send a relay support indication to the first network element 1031. In one example, the relay support indication may be included in an OAM configuration. For example, the OAM may send an OAM configuration to the first network element 1031. The OAM configuration may include the relay support indication.

[0181] In some embodiments, the fourth network element 1034 may be a UDM. In one example, the UDM may send a relay support indication to the first network element 1031 .

[0182] In some embodiments, the fourth network element 1034 may be an AMF. In one example, the AMF may send a relay support indication to the first network element 1031.

[0183] In some embodiments, when the fourth network element 1034 is an AMF, UDM, OAM, or UPF, the relay support indication may be used to indicate relay support for end-to-end encrypted XRM service identification. For example, the relay support indication may be used to indicate a functional requirement for relay support for end-to-end encrypted XRM service identification.

[0184] In some embodiments, the relay support indication may be used for at least one of discovery, selection, and reselection of the second network element 1032. In some embodiments, the relay support indication may be used for discovery, selection, and reselection of a UPF and / or a UPF instance. In some embodiments, the relay support policy and / or QoS requirements may be used for discovery, selection, and reselection of a UPF and / or a UPF instance. In some embodiments, the relay support functional requirements may be used for discovery, selection, and reselection of a UPF and / or a UPF instance.

[0185] In some embodiments, relay support may include relay support for MoQ.

[0186] In some embodiments, the function associated with relay support may be provided by the first network element 1031 according to the third information. It is understandable that, in some embodiments, the function associated with relay support may be provided by the first network element 1031 according to at least one of the following: OAM configuration, operator policy, local configuration, single network slice selection assistance information (S-NSSAI), data network name (DNN), and XRM service capability.

[0187] In some embodiments, the local configuration may include a configuration for a region. For example, for the same service, according to different local configurations associated with different regions, functions associated with relay support may be provided in one region, but not provided in another region.

[0188] In some embodiments, the S-NSSAI may be used to identify a network slice. The network slice identified by the S-NSSAI may be associated with or dedicated to an XRM service. In this case, functionality associated with relay support may be provided for end-to-end encrypted XRM services associated with the network slice identified by the S-NSSAI.

[0189] In some embodiments, the DNN can be used to identify a data network. The network identified by the DNN can be related to or dedicated to the XRM service. In this case, functions associated with relay support can be provided for end-to-end encrypted XRM services associated with the network identified by the DNN. It should be noted that the DNN can be used alone or in conjunction with the S-NSSAI, and this is not specifically limited in the present embodiment.

[0190] In some embodiments, the XRM service capability may include a relay support indication. In one example, the XRM service capability may include a MoQ relay support indication.

[0191] In step S2102 , the first network element 1031 sends first information to the third network element 1033 .

[0192] In some embodiments, the first network element 1031 may send the first information.

[0193] In some embodiments, the third network element 1033 may receive the first information.

[0194] In some embodiments, the first information may be used by the third network element 1033 to determine the second network element 1032 , which may provide functions associated with relaying of encrypted XR.

[0195] In some embodiments, the first information may be used to indicate a function associated with relaying of the encrypted XR.

[0196] In some embodiments, the functions associated with relaying encrypted XR may include relaying end-to-end encrypted XRM services. In one example, the functions associated with relaying encrypted XR may include functions associated with relaying support for end-to-end encrypted XRM service identification.

[0197] In some embodiments, functions associated with relaying of encrypted XR may include identification of PDU set information based on encrypted traffic.

[0198] In some embodiments, the PDU set information based on the encryption service may include at least one of the following: PDU set sequence number; end PDU of the PDU set; PDU sequence number within the PDU set; number of PDUs within the PDU set; PDU set importance; PDU set size; data burst end indication.

[0199] In some embodiments, the first information may be carried in a subscription message. The subscription message may be used to subscribe the third network element 1033 to the information of the second network element 1032.

[0200] In some embodiments, the first network element 1031 may send first information to the third network element 1033 in the process of providing UPF instances to SMF using NRF (SMF provisioning of UPF instances using NRF procedure). In one example, the third network element 1033 may be, for example, NRF. In one example, the first network element 1031 may send a subscription message to the third network element 1033. Correspondingly, the third network element 1033 may receive the subscription message from the first network element 1031. The first information may be carried in the subscription message. For example, the subscription message may be an Nnrf_NFManagement_NFStatusSubscribe message. The first information may be included in the target UPF provisioning information (target UPF provisioning information) in the Nnrf_NFManagement_NFStatusSubscribe message.

[0201] In step S2103 , the third network element 1033 sends second information to the first network element 1031 .

[0202] In some embodiments, the third network element 1033 may send the second information.

[0203] In some embodiments, the first network element 1031 may receive the second information.

[0204] In some embodiments, the second information may be used by the first network element 1031 to obtain the second network element 1032 that supports functions associated with relaying of encrypted XR.

[0205] In some embodiments, the second information may be used to indicate that the second network element 1032 supports functions associated with relaying of encrypted XR.

[0206] In some embodiments, the second information may be carried in a notification message. The notification message may be used to notify the first network element 1031 of the information of the second network element 1032.

[0207] In some embodiments, the third network element 1033 may send second information to the first network element 1031 during the process of using the NRF to provide a UPF instance to the SMF. In one example, the third network element 1033 may be, for example, an NRF, and the second network element 1032 may be, for example, a UPF that has been deployed and configured in the communication system and supports functions associated with relaying encrypted XR. In one example, the third network element 1033 may send a notification message to the first network element 1031. Correspondingly, the first network element 1031 may receive the notification message from the third network element 1033. The second information may be carried in the notification message. For example, the notification message may be an Nnrf_NFManagement_NFStatusNotify message. The second information may be included in the Nnrf_NFManagement_NFStatusNotify message. After obtaining the second information, the first network element 1031 may obtain information about the UPF that supports functions associated with relaying encrypted XR based on the second information.

[0208] In step S2104, the second network element 1032 is deployed.

[0209] In some embodiments, the deployed second network element 1032 may include at least one of the following: UPF, UPF instance.

[0210] In some embodiments, the second network element 1032 may complete the deployment by interacting with the sixth network element 1036. In one example, in the process of using NRF to provide the UPF instance to the SMF, the second network element 1032 may interact with the sixth network element 1036 to complete the deployment of the second network element 1032 (e.g., UPF and / or UPF instance).

[0211] In step S2105 , the second network element 1032 is configured.

[0212] In some embodiments, the second network element 1032 can complete the configuration by interacting with the sixth network element 1036. The second network element 1032 can obtain the configuration information from the sixth network element 1036 and save it locally. In one example, in the process of using NRF to provide the UPF instance to the SMF, the second network element 1032 can interact with the sixth network element 1036 to complete the configuration of the second network element 1032 (e.g., UPF and / or UPF instance).

[0213] In some embodiments, the configuration information may include UPF provisioning information. That is, the UPF provisioning information may indicate that the second network element 1032 supports functions associated with relaying encrypted XR. The second network element 1032 and the sixth network element 1036 may both obtain the UPF provisioning information and thereby determine that the second network element 1032 supports functions associated with relaying encrypted XR.

[0214] In step S2106 , the second network element 1032 sends registration information to the third network element 1033 .

[0215] In some embodiments, the second network element 1032 may send registration information.

[0216] In some embodiments, the third network element 1033 may receive registration information.

[0217] In some embodiments, the registration information may be used to register the second network element 1032 on the third network element 1033 .

[0218] In some embodiments, the registration information may include UPF provision information. In this way, the third network element 1033 may obtain the second information and know that the second network element 1032 supports functions associated with relaying of encrypted XR.

[0219] In some embodiments, the registration information may be carried in a registration message. In one example, the registration message may be an Nnrf_NFManagement_NFRegister message.

[0220] It should be noted that, through steps S2105 and S2106, the third network element 1033 can know that the second network element 1032 supports functions associated with relaying of encrypted XR.

[0221] In step S2107 , the sixth network element 1036 sends configuration information to the third network element 1033 .

[0222] In some embodiments, the sixth network element 1036 may send configuration information.

[0223] In some embodiments, the third network element 1033 may receive configuration information.

[0224] In some embodiments, the configuration information may be used for the sixth network element 1036 to register the second network element 1032 with the third network element 1033 .

[0225] In some embodiments, the configuration information may include configuration information of the second network element 1032. In one example, the configuration information may include configuration information of the second network element 1032 in the third network element 1033. In one example, the configuration information may include OAM configuration of the second network element 1032.

[0226] In some embodiments, the configuration information may include UPF provision information, thereby indicating that the second network element 1032 supports functions associated with relaying encrypted XR. The third network element 1033 may know from the configuration information that the second network element 1032 supports functions associated with relaying encrypted XR.

[0227] It should be noted that, through step S2107, the third network element 1033 can also know that the second network element 1032 supports functions associated with relaying of encrypted XR. It can be seen that step S2107 can be an alternative implementation of steps S2105 and S2106.

[0228] In step S2108 , the third network element 1033 sends second information to the first network element 1031 .

[0229] The optional implementation of step S2108 can refer to the optional implementation of step S2103 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0230] In some embodiments, the second information may be used to indicate that the second network element 1032 supports functions associated with relaying encrypted XR. Based on the second information, the third network element 1033 may inform the first network element 1031 of the second network element 1032's support for functions associated with relaying encrypted XR.

[0231] In some embodiments, the second information may be carried in a notification message. The notification message may be used to notify the first network element 1031 of the information of the second network element 1032.

[0232] In some embodiments, the third network element 123 may send second information to the first network element 1031 during the process of using the NRF to provide the UPF instance to the SMF. In one example, the third network element 1033 may be, for example, the NRF, and the second network element 1032 may be, for example, the UPF. In one example, the third network element 1033 may send a notification message to the first network element 1031. Correspondingly, the first network element 1031 may receive the notification message from the third network element 1033. The second information may be carried in the notification message. For example, the notification message may be an Nnrf_NFManagement_NFStatusNotify message. The second information may be included in the Nnrf_NFManagement_NFStatusNotify message. After obtaining the second information, the first network element 1031 may obtain information about the UPF that supports functions associated with relaying encrypted XR based on the second information.

[0233] It should be noted that the second network element 1032 targeted by the second information in step S2103 and the second network element 1032 targeted by the second information in step S2108 can be network elements of the same type and / or function. For example, both second network elements 1032 can be UPFs. The difference between the two second network elements 1032 can be that: the second network element 1032 targeted by the second information in step S2103 has already been deployed in the communication system before step S2102, and the corresponding second information already exists in the third network element 1033; the second network element 1032 targeted by the second information in step S2108 is deployed in the communication system after step S2102 (for example, through at least one of steps S2104 to S2107), and after the deployment and configuration of the second network element 1032, the third network element 1033 can obtain the second information of the second network element 1032.

[0234] In some embodiments, both step S2103 and step S2108 are optional steps. For example, step S2103 and step S2108 may be performed in their entirety, in their entirety, or in a selective manner. In one example, after step S2102 is completed, the third network element 123 may not contain any second information (i.e., no second network element 1032 has been deployed and configured in the communication system). In this case, the third network element 1033 may not perform step S2103. In another example, after step S2102 is completed, the third network element 123 may contain second information (i.e., a second network element 1032 has been deployed and configured in the communication system). In this case, the third network element 1033 may perform step S2103. In another example, after step S2102 is completed, the second network element 1032 may not be deployed. In this case, the third network element 1033 may not contain the second information of the newly deployed second network element 1032. In this case, the third network element 1033 may not perform step S2108. In one example, after step S2102 is completed, a new second network element 1032 may be deployed. Then, the third network element 1033 may include the second information of the newly deployed second network element 1032. Then, the third network element 1033 may execute step S2108. In some scenarios, after step S2102 is completed, no second network element 1032 may be deployed in the communication system, in which case step S2103 is not executed. Later, a second network element 1032 may be deployed, in which case step S2108 may be executed. The second information in step S2108 may indicate that the second network element 1032 supports functions associated with relaying encrypted XR. In some scenarios, after step S2102 is completed, a second network element 1032 may be present in the communication system, in which case step S2103 may be executed. Later, if no new second network element 1032 is deployed, step S2108 may not be executed. The second information in step S2103 may indicate that the deployed second network element 1032 supports functions associated with relaying encrypted XR. In some scenarios, after step S2103 is completed, the second network element 1032 may already exist in the communication system, and then step S2103 may be executed; thereafter, the second network element 1032 may be deployed, and then step S2108 may be executed. The second information in step S2103 may be used to indicate that the deployed second network element 1032 supports the functions associated with the relay of encrypted XR. The second information in step S2108 may be used to indicate that the newly deployed second network element 122 supports the functions associated with the relay of encrypted XR, and may also be used to indicate that all second network elements 1032 (including the deployed second network element 1032 and the newly deployed second network element 2032) support the functions associated with the relay of encrypted XR.

[0235] The communication method according to the embodiments of the present disclosure may include at least one of steps S2101 to S2108. For example, step S2102 may be implemented as an independent embodiment, step S2103 may be implemented as an independent embodiment, step S2108 may be implemented as an independent embodiment, the combination of steps S2102 and S2103 may be implemented as an independent embodiment, and the combination of steps S2102 and S2108 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0236] In some embodiments, steps S2101, S2103, S2104, S2105, S2106, S2107, and S2108 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0237] In some embodiments, steps S2101, S2102, S2104, S2105, S2106, S2107, and S2108 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0238] In some embodiments, steps S2101, S2102, S2103, S2104, S2105, S2106, and S2107 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0239] Figure 2B is an exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method, which is applied to a communication system 100. As shown in Figure 2B, the method includes steps S2201 to S2203.

[0240] In step S2201 , the fourth network element 1034 sends third information to the first network element 1031 .

[0241] The optional implementation of step S2201 can refer to the optional implementation of step S2101 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0242] In step S2202 , the first network element 1031 sends first information to the second network element 1032 .

[0243] In some embodiments, the first network element 1031 may send the first information.

[0244] In some embodiments, the second network element 1032 may receive the first information.

[0245] In some embodiments, the first information may be used to indicate a function associated with relaying the encrypted XR. Through the first information, the first network element 1031 may inform the second network element 1032 of the function associated with relaying the encrypted XR.

[0246] In some embodiments, the first information may be carried in one of the following: an N4 association establishment request message, or an N4 association establishment response message.

[0247] In some embodiments, the first network element 1031 may send the first information to the second network element 1032 during an N4 association setup procedure initiated by the SMF. In one example, the second network element 1032 may be, for example, a UPF. In one example, the first network element 1031 may send an N4 association setup request message to the second network element 1032. Correspondingly, the second network element 1032 may receive the N4 association setup request message from the first network element 1031. The first information may be carried in the N4 association setup request message.

[0248] In some embodiments, the first network element 1031 may send the first information to the second network element 1032 during an N4 association setup procedure initiated by a UPF. In one example, the second network element 1032 may be, for example, a UPF. In one example, the first network element 1031 may send an N4 association setup response message to the second network element 1032. Correspondingly, the second network element 1032 may receive the N4 association setup response message from the first network element 1031. The first information may be carried in the N4 association setup response message.

[0249] In step S2203 , the second network element 1032 sends second information to the first network element 1031 .

[0250] In some embodiments, the second network element 1032 may send second information.

[0251] In some embodiments, the first network element 1031 may receive the second information.

[0252] In some embodiments, the second information may be used to indicate that the second network element 1032 supports functions associated with relaying encrypted XR. Based on the second information, the second network element 1032 may inform the first network element 1031 of its support for functions associated with relaying encrypted XR.

[0253] In some embodiments, the second information may be carried in one of the following: an N4 association establishment request message, or an N4 association establishment response message.

[0254] In some embodiments, the second network element 1032 may send second information to the first network element 1031 during the N4 association establishment process initiated by the SMF. In one example, the second network element 1032 may be, for example, a UPF. In one example, the second network element 1032 may send an N4 association establishment response message to the first network element 1031. Correspondingly, the first network element 1031 may receive the N4 association establishment response message from the second network element 1032. The second information may be carried in the N4 association establishment response message. After obtaining the second information, the first network element 1031 may determine, based on the second information, that the UPF supports functions associated with relaying encrypted XR.

[0255] In some embodiments, the second network element 1032 may send second information to the first network element 1031 during an N4 association establishment procedure initiated by the UPF. In one example, the second network element 1032 may be, for example, the UPF. In one example, the second network element 1032 may send an N4 association establishment request message to the first network element 1031. Correspondingly, the first network element 1031 may receive the N4 association establishment request message from the second network element 1032. The second information may be carried in the N4 association establishment request message. After obtaining the second information, the first network element 1031 may determine, based on the second information, that the UPF supports functions associated with relaying encrypted XR.

[0256] In some embodiments, N4 may be an interface (or reference point) between the SMF and the UPF. Messages such as an N4 association establishment request message and an N4 association establishment response message may be transferred between the SMF and the UPF via the N4 interface.

[0257] The communication method involved in the embodiments of the present disclosure may include at least one of steps S2201 to S2203. For example, S2202 may be implemented as an independent embodiment, S2203 may be implemented as an independent embodiment, and the combination of steps S2202 and S2203 may be implemented as an independent embodiment, but is not limited thereto.

[0258] In some embodiments, steps S2202 and S2203 may be performed in an interchanged order or simultaneously.

[0259] In some embodiments, steps S2201 and S2203 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0260] In some embodiments, steps S2201 and S2202 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0261] Figure 2C is an exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure. This embodiment of the present disclosure relates to a communication method, which is applied to a communication system 100. As shown in Figure 2C, the method includes steps S2301 to S2305.

[0262] In step S2301 , the fourth network element 1034 sends third information to the first network element 1031 .

[0263] The optional implementation of step S2301 can refer to the optional implementation of step S2101 in Figure 2A and other related parts in the embodiment involved in Figure 2A, which will not be repeated here.

[0264] In step S2302 , the first network element 1031 determines to establish a session.

[0265] In some embodiments, the first network element 1031 may be triggered to perform at least one of the following: establishing a PDU session, reallocating a UPF. It is understood that both establishing a PDU session and reallocating a UPF may be implemented through an N4 session setup procedure.

[0266] In some embodiments, the network element that triggers the N4 session establishment process may be the fourth network element 1034 or other network elements, which is not specifically limited in the embodiments of the present disclosure. For example, the network element that triggers the N4 session establishment process may include at least one of the following: AMF, PCF.

[0267] In some embodiments, the third information may be carried in a trigger message and sent, or may be independent of the trigger message, which is not specifically limited in the embodiments of the present disclosure.

[0268] In step S2303 , the first network element 1031 sends first information to the second network element 1032 .

[0269] In some embodiments, the first network element 1031 may send the first information.

[0270] In some embodiments, the second network element 1032 may receive the first information.

[0271] In some embodiments, the first information may be used to indicate a function associated with relaying the encrypted XR. Through the first information, the first network element 1031 may inform the second network element 1032 of the function associated with relaying the encrypted XR.

[0272] In some embodiments, the first information may be carried in an N4 session establishment request message.

[0273] In some embodiments, the first network element 1031 may send first information to the second network element 1032 during an N4 session establishment procedure. In one example, the second network element 1032 may be, for example, a UPF. In one example, the first network element 1031 may send an N4 session setup request message to the second network element 1032. Correspondingly, the second network element 1032 may receive the N4 session setup request message from the first network element 121. The first information may be carried in the N4 session setup request message.

[0274] In step S2304 , the second network element 1032 sends second information to the first network element 1031 .

[0275] In some embodiments, the second network element 1032 may send second information.

[0276] In some embodiments, the first network element 1031 may receive the second information.

[0277] In some embodiments, in some embodiments, the second information may be carried in an N4 session establishment response message.

[0278] In some embodiments, the second network element 1032 may send second information to the first network element 1031 during the N4 session establishment process. In one example, the second network element 1032 may be, for example, a UPF. In one example, the second network element 1032 may send an N4 session establishment response message to the first network element 1031. Correspondingly, the first network element 1031 may receive the N4 session establishment response message from the second network element 1032. The second information may be carried in the N4 session establishment response message. After obtaining the second information, the first network element 1031 may determine, based on the second information, that the UPF supports functions associated with relaying encrypted XR.

[0279] In some embodiments, N4 may be an interface (or reference point) between the SMF and the UPF. Messages such as an N4 session establishment request message and an N4 session establishment response message may be transferred between the SMF and the UPF via the N4 interface.

[0280] In step S2305 , the first network element 1031 performs interaction.

[0281] In some embodiments, the first network element 1031 may interact with the network element that triggers the N4 session establishment process to complete the N4 session establishment process.

[0282] The communication method according to the embodiments of the present disclosure may include at least one of steps S2301 to S2305. For example, S2303 may be implemented as an independent embodiment, S2304 may be implemented as an independent embodiment, and a combination of steps S2303 and S2304 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0283] In some embodiments, steps S2301, S2302, S2304, and S2305 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0284] In some embodiments, steps S2301, S2302, S2303, and S2305 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0285] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2A , FIG. 2B , and FIG. 2C .

[0286] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0287] In some embodiments, terms such as "uplink", "uplink", "physical uplink" can be interchangeable with each other, and terms such as "downlink", "downlink", "physical downlink" can be interchangeable with each other, and terms such as "side", "sidelink", "side communication", "sidelink communication", "direct connection", "direct link", "direct communication", "direct link communication" can be interchangeable with each other.

[0288] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like may be used interchangeably.

[0289] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0290] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0291] In some embodiments, terms such as "service", "business", and "data flow" can be used interchangeably.

[0292] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "some", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "some A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, some A, any A, or first A, etc., but not limited to this.

[0293] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a predetermined value), but is not limited thereto.

[0294] Figure 3A is an exemplary flow chart of a communication method according to an embodiment of the present disclosure. As shown in Figure 3A, an embodiment of the present disclosure relates to a communication method. The communication method in this embodiment can be performed by the first network element 1031. The method includes steps S3101 to S3103.

[0295] In step S3101, the third information is obtained.

[0296] The optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2A, step S2201 in Figure 2B, step S2301 in Figure 2C, and other related parts in the embodiments involved in Figures 2A, 2B, and 2C, which will not be repeated here.

[0297] In some embodiments, the first network element 1031 receives the third information sent by the fourth network element 1034, but is not limited thereto and may also receive the third information sent by other entities.

[0298] In some embodiments, the first network element 1031 may obtain third information specified by the protocol.

[0299] In some embodiments, the first network element 1031 may obtain the third information from an upper layer.

[0300] In some embodiments, the first network element 1031 may perform processing to obtain third information.

[0301] In some embodiments, step S3101 may be omitted, and the first network element 1031 may autonomously implement the function indicated by the third information, or the above function may be default or by default.

[0302] In step S3102, the first information is sent.

[0303] The optional implementation of step S3102 can refer to the optional implementation of step S2102 in Figure 2A, step S2202 in Figure 2B, step S2303 in Figure 2C, and other related parts in the embodiments involved in Figures 2A, 2B, and 2C, which will not be repeated here.

[0304] In some embodiments, the first network element 1031 may send the first information to a fifth network element (not shown), but is not limited thereto and may also send the first information to other entities.

[0305] In some embodiments, the fifth network element may include one of the following: the second network element 1032 , the third network element 1033 .

[0306] In some embodiments, the first information may be used by the fifth network element to determine the second network element 1032 that supports functions related to relaying of encrypted XR.

[0307] In step S3103, the second information is obtained.

[0308] The optional implementation of step S3103 can refer to the optional implementation of steps S2103 and S2108 in Figure 2A, step S2203 in Figure 2B, step S2304 in Figure 2C, and other related parts in the embodiments involved in Figures 2A, 2B, and 2C, which will not be repeated here.

[0309] In some embodiments, the first network element 1031 may receive the second information sent by the fifth network element, but is not limited thereto and may also receive the second information sent by other entities.

[0310] In some embodiments, the second information may be used to indicate that the second network element 1032 supports functions associated with relaying of encrypted XR.

[0311] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3101 to S3103. For example, S3102 may be implemented as an independent embodiment, S3103 may be implemented as an independent embodiment, and the combination of steps S3102 and S3103 may be implemented as an independent embodiment, but is not limited thereto.

[0312] In some embodiments, steps S3101 and S3103 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0313] In some embodiments, steps S3101 and S3102 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0314] Figure 3B is an exemplary flow chart of a communication method according to an embodiment of the present disclosure. As shown in Figure 3B, an embodiment of the present disclosure relates to a communication method. The communication method in this embodiment can be performed by a fifth network element. The method includes steps S3201 to S3202.

[0315] In step S3201, first information is obtained.

[0316] The optional implementation of step S3201 can refer to the optional implementation of step S2102 in Figure 2A, step S2202 in Figure 2B, step S2303 in Figure 2C, and other related parts in the embodiments involved in Figures 2A, 2B, and 2C, which will not be repeated here.

[0317] In some embodiments, the fifth network element may receive the first information sent by the first network element 1031 , but is not limited thereto and may also receive the first information sent by other entities.

[0318] In some embodiments, the first information may be used by the fifth network element to determine the second network element 1032 that supports functions related to relaying of encrypted XR.

[0319] In step S3202, the second information is sent.

[0320] The optional implementation of step S3202 can refer to the optional implementation of steps S2103 and S2108 in Figure 2A, step S2203 in Figure 2B, step S2304 in Figure 2C, and other related parts in the embodiments involved in Figures 2A, 2B, and 2C, which will not be repeated here.

[0321] In some embodiments, the fifth network element may send the second information to the first network element 1031 , but is not limited thereto and may also send the second information to other entities.

[0322] In some embodiments, the second information may be used to indicate that the second network element 1032 supports functions associated with relaying of encrypted XR.

[0323] The communication method according to the embodiments of the present disclosure may include at least one of steps S3201 and S3202. For example, S3202 may be implemented as an independent embodiment, S3203 may be implemented as an independent embodiment, and the combination of steps S3202 and S3203 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0324] In some embodiments, step S3201 is optional and may be omitted or replaced in different embodiments.

[0325] In some embodiments, step S3202 is optional and may be omitted or replaced in different embodiments.

[0326] FIG3C is an exemplary flow chart of a communication method according to an embodiment of the present disclosure. As shown in FIG3C , an embodiment of the present disclosure relates to a communication method. The communication method in this embodiment can be performed by the fourth network element 1034. The method includes step S3301.

[0327] In step S3301, the third information is sent.

[0328] The optional implementation of step S3301 can refer to the optional implementation of step S2101 in Figure 2A, step S2201 in Figure 2B, step S2301 in Figure 2C, and other related parts in the embodiments involved in Figures 2A, 2B, and 2C, which will not be repeated here.

[0329] In some embodiments, the fourth network element 1034 may send the third information to the first network element 1031 , but is not limited thereto and may also send the third information to other entities.

[0330] Figure 4 is an exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure. As shown in Figure 4, an embodiment of the present disclosure relates to a communication method. The method includes step S401.

[0331] In step S401, the first network element 1031 sends first information to the fifth network element.

[0332] The optional implementation of step S401 can refer to the optional implementation of step S2102 in Figure 2A, step S2202 in Figure 2B, step S2303 in Figure 2C, and other related parts in the embodiments involved in Figures 2A, 2B, and 2C, which will not be repeated here.

[0333] Hereinafter, the technical solutions of the embodiments of the present disclosure are exemplarily described through specific implementation methods.

[0334] In some embodiments, when a PDU session is created, a relay support indication (for example, MoQ, i.e., media over QUIC) is carried, which informs the need for identification of end-to-end encrypted streams / the need for UPF to act as a relay for end-to-end encrypted streams; when performing UPF selection, NRF / SMF considers the relay support function of the encrypted stream / the identification requirement of the encrypted stream, and selects a UPF that supports the identification function of the end-to-end encrypted stream / supports the relay function of the end-to-end encrypted stream.

[0335] In some embodiments, when the AF initiates session creation / update, it carries a relay support indication (e.g., MoQ, i.e., media over QUIC) to the PCF / SMF (informing the PCF / SMF of the need to identify the end-to-end encrypted flow / the need for the UPF to act as a relay for the end-to-end encrypted flow). The PCF / SMF initiates a PDU session modification and reselects the UPF that supports the relay support function / identification function of the encrypted flow.

[0336] In some embodiments, after selecting a UPF that supports the relay support function / identification function of encrypted flows, the UPF can perform the relay function on the encrypted flows and perform PDU set information identification on the encrypted flows (for example, MoQ) based on the protocol description of the encrypted flows and the corresponding QoS rules.

[0337] In some embodiments, for XR services (data streams), each PDU set (e.g., frame) may be mapped to a MoQ object, and the PDU set information may be determined as:

[0338] -PDU set sequence number: can be mapped from object sequence;

[0339] - End PDU indication of a PDU set: can be determined based on the object sequence and object payload length, or based on the stream end indication if each object is mapped to a QUIC stream;

[0340] -PDU sequence number within a PDU set: can be determined based on the data packets received for the object;

[0341] -PDU set size (words): can be determined based on the object payload length;

[0342] -PDU set importance: can be determined based on the order in which objects are sent.

[0343] In some embodiments, the track ID in the MoQT metadata is an identifier for a sub-media stream. This identifier can be used to distinguish sub-streams within a transport connection. By performing MoQ relay, the UPF can identify sub-streams based on the track ID and map the identified sub-streams to QoS flows.

[0344] In some embodiments, the UPF selection function in the SMF may perform discovery / selection / reselection of the UPF, taking into account functionality associated with identified relay support (e.g., MoQ) for end-to-end encrypted XRM services (which indicates that the UPF is capable of acting as a relay for end-to-end encrypted XRM services between the UE and the AS).

[0345] In some embodiments, the following parameters / information may be considered for UPF selection and reselection: support for functionality associated with relay support (e.g., MoQ) for identification of end-to-end encrypted XRM services; or support for functionality associated with identification of PDU set information based on encrypted services.

[0346] In some embodiments, the UPF selection function in the SMF can use the NRF to discover / select / reselect the UPF / UPF instance. In this case, the SMF sends a request to the NRF to discover the UPF. The request provides functions associated with the relay support (e.g., MoQ) for identification of end-to-end encrypted XRM services for discovery / selection / reselection of the UPF / UPF instance.

[0347] In some embodiments, the SMF provides functionality associated with relay support (e.g., MoQ) for identification of end-to-end encrypted XRM services for discovery / selection / reselection of UPF / UPF instances. This process takes into account at least one of the following conditions:

[0348] - MoQ relay support indication from PCF (e.g. indicated by PCC rules);

[0349] - MoQ relay support indication from AF via PCF;

[0350] - MoQ trunk support indication from legacy PCF / serving PCF;

[0351] -OAM configuration / operator policy / local configuration;

[0352] - S-NSSAI related to or dedicated to XRM services, or S-NSSAI and DNN;

[0353] - XRM service capabilities including MoQ trunk support indication.

[0354] In some embodiments, the AF may provide a relay support indication to the SMF to indicate relay support (e.g., MoQ) for end-to-end encrypted XRM service identification and for discovery / selection / reselection of UPF / UPF instances.

[0355] In some embodiments, the PCF may provide a relay support indication to the SMF to indicate the policy and QoS requirements for relay support (e.g., MoQ) for end-to-end encrypted XRM service identification and for discovery / selection / reselection of UPF / UPF instances.

[0356] In some embodiments, the AMF / UDM / OAM / old UPF may provide a relay support indication to the SMF to indicate the functional requirements of relay support (e.g., MoQ) for end-to-end encrypted XRM service identification and for discovery / selection / reselection of UPF / UPF instances.

[0357] FIG5A is an exemplary interaction diagram of a specific implementation of a communication method provided according to an embodiment of the present disclosure. This communication method is applied to the process of an NRF providing a UPF instance to an SMF. This process can be applied when the SMF wants to learn about the UPFs available in the network and supporting a set of parameters. As shown in FIG5A , this process can be executed when the SMF wants to learn about the UPFs available in the network.

[0358] In the first step, the SMF (i.e., the first network element) issues the Nnrf_NFManagement_NFStatusSubscribe service operation and provides information to the target UPF of interest.

[0359] In some embodiments, the SMF sends a request to the NRF (i.e., the third network element) to discover the UPF. The request provides functions associated with relay support (e.g., MoQ) for identification of end-to-end encrypted XRM services for discovery / selection / reselection of UPF / UPF instances.

[0360] In some embodiments, the following parameters / information may be considered for UPF selection and reselection: support for functionality associated with relay support (e.g., MoQ) for identification of end-to-end encrypted XRM services; or support for functionality associated with identification of PDU set information based on encrypted services.

[0361] In some embodiments, the SMF provides functionality associated with relay support (e.g., MoQ) for identification of end-to-end encrypted XRM services for discovery / selection / reselection of UPF / UPF instances. This process takes into account at least one of the following conditions:

[0362] - MoQ relay support indication from PCF (e.g. indicated by PCC rules);

[0363] - MoQ relay support indication from AF via PCF;

[0364] - MoQ trunk support indication from legacy PCF / serving PCF;

[0365] -OAM configuration / operator policy / local configuration;

[0366] - S-NSSAI related to or dedicated to XRM services, or S-NSSAI and DNN;

[0367] - XRM service capabilities including MoQ trunk support indication.

[0368] In the second step, NRF issues Nnrf_NFManagement_NFStatusNotify along with a list of all UPFs that currently satisfy the SMF subscription. This notification indicates the subset of target UPF provided information supported by each UPF.

[0369] In some embodiments, the UPF supports the following functions required by the SMF for UPF selection and reselection, and the NRF can send these UPFs to the SMF: support functions associated with relay support (e.g., MoQ) for identification of end-to-end encrypted XRM services.

[0370] In some embodiments, when a new UPF instance is deployed, the following steps 3 to 7 may be performed.

[0371] In the third step, new UPF instances are deployed at any time.

[0372] In step 4, the UPF instance is configured with the NRF identifier to be contacted for registration and its UPF provided information. The UPF (i.e., the second network element) does not need to understand the UPF provided information and only needs to use it to register in step 5.

[0373] In the fifth step, the UPF instance issues a Nnrf_NFManagement_NFRegister request operation, providing its NF type, the fully qualified domain name (FQDN) or IP address of the N4 interface, and the UPF provisioning information configured in the fourth step.

[0374] In the sixth step, as an alternative to the fourth and fifth steps, the OAM registers the UPF on the NRF, instructing the same UPF provided in the fifth step to provide information.

[0375] In the seventh step, based on the subscription in step S5101, the NRF sends Nnrf_NFManagement_NFStatusNotify to all SMFs, and the subscription matches the UPF provisioning information of the new UPF.

[0376] In some embodiments, the NRF may send the new UPF to the SMF if the new UPF supports the following functionality required by the SMF for UPF selection and reselection: support for functionality associated with relay support (e.g., MoQ) for identification of end-to-end encrypted XRM services.

[0377] In some embodiments, the UPF selection for PDU session establishment, UE mobility, or UE traffic offloading may include at least one of the following processes: a UPF selection process for creating a new PDU session when there is no PDU session (for example, an N4 association establishment process, in which the UPF and SMF exchange information on whether relevant functional information is supported, such as relay support (for example, MoQ) for identification of end-to-end encrypted XRM services); selecting a UPF for a specific PDU session (for example, an N4 session management process); selecting and binding an existing PDU session of a UPF that supports relay support (for example, MoQ) for identification of end-to-end encrypted XRM services for a specific AF session. The process of selecting and binding the AF session to the PDU session is also a discovery process of the corresponding UPF (the session binding here can be implemented by the PCF through the BSF, or the PCF can be performed through local storage or local configuration information, that is, bound to a PDU session associated with relay support for identification of end-to-end encrypted XRM services).

[0378] Figure 5B is an exemplary interaction diagram of a specific implementation of a communication method provided according to an embodiment of the present disclosure. This communication method is applied to an SMF-initiated N4 association establishment process. As shown in Figure 5B , the SMF initiates the N4 association establishment process to request the establishment of an N4 association with the UPF before establishing the first N4 session on the UPF. Upon receiving the N4 association establishment request, the UPF shall send an N4 association establishment response.

[0379] Figure 5C is an exemplary interaction diagram of a specific implementation of a communication method provided according to an embodiment of the present disclosure. This communication method is applied to the N4 association establishment process initiated by the UPF. As shown in Figure 5C, the UPF can initiate the N4 association establishment process to request the establishment of an N4 association with the SMF before establishing the first N4 session on the UPF. Upon receiving the N4 association establishment request, the SMF shall send an N4 association establishment response.

[0380] In some embodiments, during these processes, the following information may be exchanged: whether the functions associated with relay support (e.g., MoQ) for identification of end-to-end encrypted XRM services are supported. In some embodiments, for the functions associated with relay support (e.g., MoQ) for identification of end-to-end encrypted XRM services required by the SMF, the SMF may select or reselect a UPF that supports the function.

[0381] Figure 5D is an exemplary interaction diagram of a specific implementation of a communication method provided according to an embodiment of the present disclosure. The communication method is applied to N4 session establishment in the N4 session management process.

[0382] In some embodiments, the N4 session establishment process is used to create an initial N4 session context for a PDU session on the UPF. The SMF allocates a new N4 session identifier and provides it to the UPF. The N4 session identifier is stored in the SMF and UPF and is used to identify the N4 session context during interactions between the SMF and UPF. The SMF may also store the relationship between the N4 session identifier and the PDU session for the UE.

[0383] In the first step, the SMF receives a trigger to establish a new PDU Session or change the UPF for an already established PDU Session.

[0384] In some embodiments, for selection and reselection of UPF, the SMF may consider the following parameters / information: Support for functionality associated with relay support (e.g., MoQ) for identification of end-to-end encrypted XRM traffic.

[0385] In the second step, the SMF sends an N4 Session Establishment Request message to the UPF. The N4 Session Establishment Request message contains structured control information that defines how the UPF needs to work.

[0386] In the third step, the UPF responds with an N4 Session Setup Response message. The N4 Session Setup Response message contains any information that the UPF must provide to the SMF in response to the received control information.

[0387] In some embodiments, if the UPF (through configuration or other means) uses a network data analytics function (NWDAF), the UPF adds the NWDAF that provides the service UE. The NWDAF is identified by an NWDAF instance identifier. For each NWDAF service instance, an analysis identifier may also be included.

[0388] In the fourth step, the SMF interacts with the network function (e.g., AMF or PCF) that triggers the N4 session establishment process.

[0389] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0390] The embodiments of the present disclosure also provide a communication device for implementing any of the above methods. For example, the embodiments of the present disclosure also provide another communication device, including units or modules for implementing each step performed by the network device in any of the above methods.

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

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

[0393] FIG6 is a schematic diagram of the structure of a communication device according to an embodiment of the present disclosure. As shown in FIG6 , the communication device 600 may include at least one of the following: a transceiver module 601 and a processing module 602 .

[0394] In the first aspect, the communication device 600 may be the first network element 1031. In some embodiments, the transceiver module 601 may be configured to send first information, wherein the first information is used to indicate a function associated with the relay of the encrypted XR. Optionally, the transceiver module 601 may be configured to perform at least one of the communication steps such as sending and / or receiving performed by the first network element 1031 in any of the above methods (for example, steps S2101, S2102, S2103, S2108, S2201, S2202, S2301, S2303, S2304), which are not described in detail here. Optionally, the processing module 602 may be configured to perform at least one of the other steps (for example, steps S2302, S2305) other than the communication steps such as sending and / or receiving performed by the first network element 1031 in any of the above methods, which are not described in detail here.

[0395] In the second aspect, the communication device 600 may be the second network element 1032. In some embodiments, the transceiver module 601 may be configured to receive first information, wherein the first information is used to indicate a function associated with relaying the encrypted XR. Optionally, the transceiver module 601 may be configured to perform at least one of the communication steps such as sending and / or receiving performed by the second network element 1032 in any of the above methods (e.g., steps S2104, S2105, S2106, S2202, S2203, S2303, S2304), which will not be repeated here.

[0396] In a third aspect, the communication device 600 may be the third network element 1033. In some embodiments, the transceiver module 601 may be configured to receive first information, where the first information is used to indicate a function associated with relaying encrypted XR. Optionally, the transceiver module 601 may be configured to perform at least one of the communication steps (e.g., steps S2102, S2103, S2106, S2107, and S2108) such as sending and / or receiving performed by the third network element 1033 in any of the above methods, which will not be further described herein.

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

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

[0399] Figure 7A is a schematic diagram of the structure of a communication device provided according to an embodiment of the present disclosure. Communication device 7100 can be a network device (e.g., an access network device, a core network device, etc.), or a terminal (e.g., a user device, etc.), or a chip, chip system, or processor that supports a network device to implement any of the above methods, or a chip, chip system, or processor that supports a terminal to implement any of the above methods. Communication device 7100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0400] As shown in Figure 7A, the communication device 7100 includes one or more processors 7101. The processor 7101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process the communication protocol and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. Optionally, the communication device 7100 is used to perform any of the above methods. Optionally, one or more processors 7101 are used to call instructions to enable the communication device 7100 to perform any of the above methods.

[0401] In some embodiments, the communication device 7100 further includes one or more transceivers 7102. When the communication device 7100 includes one or more transceivers 7102, the transceiver 7102 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2102, S2103, S2104, S2105, S2106, S2107, S2108, S2201, S2202, S2203, S2301, S2303, S2304, but not limited thereto), and the processor 7101 performs at least one of the other steps (e.g., steps S2302 and S2305, but not limited thereto). In an optional embodiment, the transceiver may include a receiver and / or a transmitter, and the receiver and transmitter may be separate or integrated. Optionally, terms such as transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, and interface can be replaced with each other, terms such as transmitter, transmitting unit, transmitter, and transmitting circuit can be replaced with each other, and terms such as receiver, receiving unit, receiver, and receiving circuit can be replaced with each other.

[0402] In some embodiments, the communication device 7100 further includes one or more memories 7103 for storing data. Alternatively, all or part of the memories 7103 may be located outside the communication device 7100. In alternative embodiments, the communication device 7100 may include one or more interface circuits 7104. Optionally, the interface circuits 7104 are connected to the memories 7103 and may be configured to receive data from the memories 7103 or other devices, or to send data to the memories 7103 or other devices. For example, the interface circuits 7104 may read data stored in the memories 7103 and send the data to the processor 7101.

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

[0404] FIG7B is a schematic diagram of the structure of a chip provided according to an embodiment of the present disclosure. If the communication device 7100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 7200 shown in FIG7B , but the present invention is not limited thereto.

[0405] The chip 7200 includes one or more processors 7201. The chip 7200 is configured to execute any of the above methods.

[0406] In some embodiments, chip 7200 further includes one or more interface circuits 7202. Alternatively, terms such as interface circuit, interface, and transceiver pins may be used interchangeably. In some embodiments, chip 7200 further includes one or more memories 7203 for storing data. Alternatively, all or part of memory 7203 may be located external to chip 7200. Optionally, interface circuit 7202 is connected to memory 7203 and may be used to receive data from memory 7203 or other devices, or may be used to send data to memory 7203 or other devices. For example, interface circuit 7202 may read data stored in memory 7203 and send the data to processor 7201.

[0407] In some embodiments, the interface circuit 7202 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2102, S2103, S2104, S2105, S2106, S2107, S2108, S2201, S2202, S2203, S2301, S2303, and S2304, but not limited thereto). The interface circuit 7202 performing the communication steps such as sending and / or receiving in the above method, for example, means that the interface circuit 7202 performs data exchange between the processor 7201, the chip 7200, the memory 7203, or the transceiver device. In some embodiments, the processor 7201 performs at least one of the other steps (e.g., steps S2302 and S2305, but not limited thereto).

[0408] The modules and / or devices described in various embodiments, such as virtual devices, physical devices, and chips, can be arbitrarily combined or separated according to circumstances. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0409] The embodiments of the present disclosure further provide a storage medium having instructions stored thereon. When the instructions are executed on the communication device 7100, the communication device 7100 executes any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a temporary storage medium.

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

[0411] The embodiments of the present disclosure further provide a computer program, which, when executed on a computer, enables the computer to execute any of the above methods.

[0412] Other embodiments of the present invention will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow from the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the invention being indicated by the following claims.

[0413] It should be understood that the present invention is not limited to the exact construction described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A communication method, performed by a first network element, wherein: The method comprises: First information is sent, where the first information is used to indicate a function associated with relaying encrypted extended reality (XR).

2. The method according to claim 1, wherein The functions associated with relaying encrypted XR include at least one of the following: End-to-end encrypted multimedia extended reality (XRM) service relay; Identification of packet data unit (PDU) set information based on encryption services.

3. The method according to claim 2, wherein: The PDU set information based on the encryption service includes at least one of the following: PDU set sequence number; The end PDU of the PDU set; PDU sequence number within the PDU set; The number of PDUs in the PDU set; PDU set importance; PDU set size; End of data burst indication.

4. The method according to any one of claims 1 to 3, wherein The first information is used for at least one of the following: Discovery of the second network element; Selection of the second network element; Reselection of the second network element.

5. The method according to any one of claims 1 to 4, wherein The first information is carried in at least one of the following: Subscribe to news; N4 association establishment request message; N4 association establishment response message; N4 session establishment request message.

6. The method according to any one of claims 1 to 5, wherein The sending of the first information includes at least one of the following: sending the first information to the second network element; Send the first information to the third network element.

7. The method according to any one of claims 1 to 6, wherein The method further comprises: Second information is received, where the second information is used to indicate that the second network element supports a function associated with relaying of encrypted XR.

8. The method according to claim 7, wherein: The second information is carried in at least one of the following: Notification message; N4 association establishment request message; N4 association establishment response message; N4 session establishment response message.

9. The method according to any one of claims 1 to 8, wherein The functionality associated with relaying the encrypted XR is determined based on at least one of the following: The third information is used to indicate functional requirements associated with the relay of the encrypted XR; Operation, maintenance and management (OAM) configuration; Operator strategy; Local configuration; Single network slice selection assistance information S-NSSAI; Data network name DNN; XRM business capabilities.

10. The method according to claim 9, wherein: The function associated with the encrypted XR is determined based on at least the third information; The method further comprises: Receive the third information sent by the fourth network element.

11. The method according to claim 10, wherein: The fourth network element is a policy control function PCF; The third information is used for PDU session binding.

12. A communication method, performed by a fifth network element, wherein: The method comprises: First information is received, wherein the first information is used to indicate a function associated with relaying encrypted extended reality (XR).

13. The method according to claim 12, wherein: The functions associated with relaying encrypted XR include at least one of the following: End-to-end encrypted multimedia extended reality (XRM) service relay; Identification of packet data unit (PDU) set information based on encryption services.

14. The method according to claim 13, wherein The PDU set information based on the encryption service includes at least one of the following: PDU set sequence number; The end PDU of the PDU set; PDU sequence number within the PDU set; The number of PDUs in the PDU set; PDU set importance; PDU set size; End of data burst indication.

15. The method according to any one of claims 12 to 14, wherein The first information is used for at least one of the following: Discovery of the second network element; Selection of the second network element; Reselection of the second network element.

16. The method according to any one of claims 12 to 15, wherein The first information is carried in at least one of the following: Subscribe to news; N4 association establishment request message; N4 association establishment response message; N4 session establishment request message.

17. The method according to any one of claims 12 to 16, wherein The method further comprises: Second information is sent, where the second information is used to indicate that the second network element supports a function associated with relaying of encrypted XR.

18. The method according to claim 17, wherein The second information is carried in at least one of the following: Notification message; N4 association establishment request message; N4 association establishment response message; N4 session establishment response message.

19. The method according to any one of claims 12 to 18, wherein The fifth network element is one of the following: User plane function UPF; Network storage function NRF.

20. A first network element, comprising: The transceiver module is configured to send first information, wherein the first information is used to indicate a function associated with the relay of encrypted extended reality XR.

21. A fifth network element, comprising: The transceiver module is configured to receive first information, wherein the first information is used to indicate a function associated with the relay of encrypted extended reality XR.

22. A communication device comprising: one or more processors; a memory storing instructions; When the instruction is executed by the communication device, the communication device implements the method according to any one of claims 1 to 11.

23. A communication device comprising: one or more processors; a memory storing instructions; When the instruction is executed by the communication device, the communication device implements the method according to any one of claims 12 to 19.

24. A communication system comprising a first network element and a fifth network element; in, The first network element is used to implement the method according to any one of claims 1 to 11; The fifth network element is configured to implement the method according to any one of claims 12 to 19.

25. A storage medium storing instructions, wherein: When the instructions are executed on a communication device, the communication device is caused to implement at least one of the following: The method according to any one of claims 1 to 11; The method according to any one of claims 12 to 19.

26. A computer program product comprising instructions, wherein when the instructions are executed on a communication device, the communication device is caused to implement at least one of the following: The method according to any one of claims 1 to 11; The method according to any one of claims 12 to 19.

Images