WO2022056676A1 - 业务识别方法、终端设备和网络设备 - Google Patents

业务识别方法、终端设备和网络设备 Download PDF

Info

Publication number
WO2022056676A1
WO2022056676A1 PCT/CN2020/115342 CN2020115342W WO2022056676A1 WO 2022056676 A1 WO2022056676 A1 WO 2022056676A1 CN 2020115342 W CN2020115342 W CN 2020115342W WO 2022056676 A1 WO2022056676 A1 WO 2022056676A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
qos
service information
data
terminal device
Prior art date
Application number
PCT/CN2020/115342
Other languages
English (en)
French (fr)
Inventor
郭雅莉
刘建华
杨皓睿
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to EP20953537.6A priority Critical patent/EP4142361B1/en
Priority to CN202080098612.2A priority patent/CN115299098A/zh
Priority to PCT/CN2020/115342 priority patent/WO2022056676A1/zh
Publication of WO2022056676A1 publication Critical patent/WO2022056676A1/zh
Priority to US17/993,504 priority patent/US20230093178A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/23—Manipulation of direct-mode connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/023—Services making use of location information using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • the present application relates to the field of communications, and more particularly, to a service identification method, a terminal device and a network device.
  • a user equipment capable of proximity services (Prose, Proximity-based Services) can communicate directly with another UE capable of Prose through the PC5 wireless interface.
  • the two UEs determine the QoS requirements corresponding to the service data transmission according to the quality of service (QoS, Quality of Service) requirements of the service, and establish a PC5 QoS data flow between the two UEs that can guarantee the corresponding QoS requirements for service data transmission.
  • Transmission data of multiple services can be transmitted on one PC5 QoS data stream, and data of one service can also be transmitted through multiple PC5 QoS data streams.
  • the receiver's UE After the receiver's UE receives the data, it can uniformly send the data to a data processing unit above the network layer (for example, the operating system, or a data processing unit shared by multiple applications), and the data processing unit can distinguish the data , and send it to the corresponding application.
  • a data processing unit above the network layer for example, the operating system, or a data processing unit shared by multiple applications
  • the data processing unit can distinguish the data , and send it to the corresponding application.
  • the UE of the receiver has a strong dependence on the data processing unit, and when the assistance of the data processing unit cannot be obtained, the data cannot be distinguished, so that the data cannot be sent to the corresponding application.
  • a UE When a UE is connected to an external data network through a 5G network and has the Prose capability, the UE can act as a relay UE, and another remote UE with Prose capability can establish a direct connection with the relay UE through the PC5 interface. Connect, and interact with the external network through the Protocol Data Unit (PDU, Protocol Data Unit) session established by the relay UE and the 5G network.
  • PDU Protocol Data Unit
  • relay UE accesses the 3rd Generation Partnership Project (3GPP, 3rd Generation Partnership Project) network, it will consider the services that need to be transmitted.
  • 3GPP 3rd Generation Partnership Project
  • Different PDU session or QoS flow parameters can be set for different services, but for remote UE through PC5
  • the data sent by the interface to the relay UE cannot be differentiated by the relay UE, so the parameters of the PDU session or QoS flow from the relay UE to the core network cannot be set correctly.
  • the UE at the receiving end cannot identify the service information, so that the communication cannot be performed normally.
  • the embodiments of the present application provide a service identification method, a terminal device, and a network device, which can enable the UE at the receiving end to identify service information and ensure normal communication.
  • An embodiment of the present application proposes a service identification method, which is applied to a terminal device, including:
  • the embodiment of the present application also proposes a method for sending service information, which is applied to a terminal device, including:
  • the service information is used for the peer terminal device to identify the service corresponding to the received data; and/or to determine the service to be initiated.
  • An embodiment of the present application proposes a method for sending service information, which is applied to a network device, including:
  • the service information is used by the terminal device to identify the service corresponding to the received data; and/or, to determine the service to be initiated.
  • the embodiment of the present application proposes a method for sending a policy and charging control PCC rule, which is applied to a network device, including:
  • Send PCC rules which include service filters and service information
  • the service information is used by the terminal device to identify the service corresponding to the received data; and/or, to determine the service to be initiated.
  • An embodiment of the present application proposes a terminal device, including:
  • a determination module configured to identify the service corresponding to the received data according to the service information; and/or, to determine the service to be initiated according to the service information.
  • An embodiment of the present application proposes a terminal device, including:
  • a first sending module used for sending service information
  • the service information is used for the peer terminal device to identify the service corresponding to the received data; and/or to determine the service to be initiated.
  • An embodiment of the present application proposes a network device, including:
  • a second sending module configured to send service information
  • the service information is used by the terminal device to identify the service corresponding to the received data; and/or, to determine the service to be initiated.
  • An embodiment of the present application proposes a network device, including:
  • the third sending module is used for sending PCC rules, and the PCC rules include service filters and service information;
  • the service information is used by the terminal device to identify the service corresponding to the received data; and/or, to determine the service to be initiated.
  • An embodiment of the present application proposes a terminal device, including: a processor and a memory, where the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, and execute the method described in any of the above .
  • An embodiment of the present application proposes a communication device, including: a processor and a memory, where the memory is used for storing a computer program, the processor is used for calling and running the computer program stored in the memory, and executing any one of the above Methods.
  • An embodiment of the present application provides a chip, including: a processor configured to call and run a computer program from a memory, so that a device installed with the chip executes the method described in any one of the above.
  • An embodiment of the present application provides a chip, including: a processor configured to call and run a computer program from a memory, so that a device installed with the chip executes the method described in any one of the above.
  • An embodiment of the present application provides a computer-readable storage medium for storing a computer program, where the computer program causes a computer to execute the method described in any one of the foregoing.
  • An embodiment of the present application provides a computer-readable storage medium for storing a computer program, where the computer program causes a computer to execute the method described in any one of the foregoing.
  • An embodiment of the present application provides a computer program product, including computer program instructions, and the computer program instructions cause a computer to execute any of the methods described above.
  • An embodiment of the present application provides a computer program product, including computer program instructions, and the computer program instructions cause a computer to execute any of the methods described above.
  • An embodiment of the present application provides a computer program, and the computer program causes a computer to execute the method according to any one of the preceding claims.
  • An embodiment of the present application provides a computer program, where the computer program causes a computer to execute any of the methods described above.
  • the embodiments of the present application receive service information through the UE, and can identify the service corresponding to the received data or determine the service to be initiated according to the service information, so that the receiving UE can identify the service information and ensure normal communication.
  • FIG. 1A is a schematic diagram of an application scenario 1 of an embodiment of the present application.
  • FIG. 1B is a schematic diagram of an application scenario 2 of an embodiment of the present application.
  • FIG. 1C is a schematic diagram of application scenario 3 of an embodiment of the present application
  • FIG. 2 is a flowchart for implementing a service identification method 200 according to an embodiment of the present application.
  • FIG. 3 is an implementation flowchart of Embodiment 1 of the present application.
  • FIG. 4 is an implementation flowchart of Embodiment 2 of the present application.
  • FIG. 5 is an implementation flowchart of Embodiment 3 of the present application.
  • FIG. 6 is an implementation flowchart of Embodiment 4 of the present application.
  • FIG. 7 is an implementation flowchart of Embodiment 5 of the present application.
  • FIG. 8 is an implementation flowchart of Embodiment 6 of the present application.
  • FIG. 9 is an implementation flowchart of Embodiment 7 of the present application.
  • FIG. 10 is an implementation flowchart of Embodiment 8 of the present application.
  • FIG. 11 is an implementation flowchart of a method 1100 for sending service information according to an embodiment of the present application.
  • FIG. 12 is an implementation flowchart of a method 1200 for sending service information according to an embodiment of the present application.
  • FIG. 13 is a flowchart for implementing a method 1300 for sending a PCC rule according to an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of a terminal device 1400 according to an embodiment of the present application.
  • FIG. 15 is a schematic structural diagram of a terminal device 1500 according to an embodiment of the present application.
  • FIG. 16 is a schematic structural diagram of a network device 1600 according to an embodiment of the present application.
  • FIG. 17 is a schematic structural diagram of a network device 1700 according to an embodiment of the present application.
  • FIG. 18 is a schematic structural diagram of a communication device 1800 according to an embodiment of the present application.
  • FIG. 19 is a schematic structural diagram of a chip 1900 according to an embodiment of the present application.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Advanced Long Term Evolution
  • NR New Radio
  • UMTS Universal Mobile Telecommunication System
  • WLAN Wireless Local Area Networks
  • WiFi Wireless Fidelity
  • 5G 5th-Generation
  • the communication system in this embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, or a standalone (Standalone, SA) distribution. web scene.
  • Carrier Aggregation, CA Carrier Aggregation, CA
  • DC Dual Connectivity
  • SA standalone
  • This embodiment of the present application does not limit the applied spectrum.
  • the embodiments of the present application may be applied to licensed spectrum, and may also be applied to unlicensed spectrum.
  • terminal equipment may also be referred to as user equipment (User Equipment, UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • UE User Equipment
  • access terminal subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • the terminal device can be a station (STAION, ST) in the WLAN, can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a personal digital processing (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, and next-generation communication systems, such as terminal devices in NR networks or Terminal equipment in the future evolved Public Land Mobile Network (Public Land Mobile Network, PLMN) network, etc.
  • STAION, ST in the WLAN
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices, which are the general term for the intelligent design of daily wear and the development of wearable devices using wearable technology, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-scale, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which needs to cooperate with other devices such as smart phones.
  • a network device can be a device used to communicate with a mobile device.
  • the network device can be an access point (Access Point, AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, or a WCDMA
  • a base station NodeB, NB
  • it can also be an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, wearable device, and network equipment (gNB) in NR networks Or network equipment in the PLMN network that evolves in the future.
  • AP Access Point
  • BTS Base Transceiver Station
  • gNB network equipment
  • a network device provides services for a cell
  • a terminal device communicates with the network device through transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell
  • the cell may be a network device (for example, a frequency domain resource).
  • the cell corresponding to the base station), the cell can belong to the macro base station, or it can belong to the base station corresponding to the small cell (Small cell), where the small cell can include: Metro cell, Micro cell, Pico cell cell), Femto cell, etc.
  • These small cells have the characteristics of small coverage and low transmit power, and are suitable for providing high-speed data transmission services.
  • FIG. 1A is a schematic diagram of an application scenario 1 of an embodiment of the present application.
  • FIG. 1A exemplarily shows a 5G network system architecture.
  • the UE connects with the access network (AN, Access Network) through the Uu wireless interface, exchanges access layer messages and wireless data transmission, and the UE communicates with the mobility management function (AMF, Access and Mobility Management Function through the N1 interface) ) to connect to a non-access stratum (NAS, None Access Stratum) and exchange NAS messages.
  • AMF Access and Mobility Management Function
  • NAS Non-access stratum
  • SMF Session Management Function
  • the AMF is also responsible for sending messages from session management to Forwarding between UE and SMF.
  • the Policy Control Function (PCF, Policy Control Function) is a policy management function in the core network, and is responsible for formulating policies related to mobility management, session management, and charging of the UE.
  • the User Plane Function (UPF, User Plane Function) is the user plane function in the core network. It transmits data to the external data network through the N6 interface, and transmits data to the AN through the N3 interface.
  • the UE After the UE accesses the 5G network through the Uu port, it transmits service data through the network.
  • the network layer of the UE obtains the QoS requirements of the service from the upper layer (such as the operating system or application), and the UE converts the QoS requirements of the service into the QoS parameters of the Uu interface, and passes the corresponding correspondence between the UE and the UPF under the control of the SMF QoS flow for data transmission.
  • the network layer of the UE obtains the QoS requirements of the service from the upper layer (such as the operating system or application)
  • the UE converts the QoS requirements of the service into the QoS parameters of the Uu interface, and passes the corresponding correspondence between the UE and the UPF under the control of the SMF QoS flow for data transmission.
  • FIG. 1B is a schematic diagram of an application scenario 2 of an embodiment of the present application.
  • FIG. 1B exemplarily shows an example of a PC5 unicast link between two UEs.
  • a Prose-capable UE can communicate directly with another Prose-capable UE through the PC5 wireless interface.
  • the two UEs determine the QoS requirements corresponding to the service data transmission according to the QoS requirements of the service, and establish a PC5 QoS data stream that can guarantee the corresponding QoS requirements between the two UEs to transmit the service data, so as to ensure that the service communicates on the PC5. quality of service.
  • a PC5 QoS data stream can transmit data of multiple services, and data of one service can also be transmitted through multiple PC5 QoS data streams.
  • FIG. 1C is a schematic diagram of application scenario 3 of the embodiment of the present application. As shown in FIG. 1C , the remote UE establishes a PDU session with the 5G network through the relay UE, that is, the ProSe 5G UE-to-Network Relay.
  • the above three application scenarios are examples of scenarios to which the embodiments of the present application may be applied, and the embodiments of the present application are not limited to the above three application scenarios, and are not limited to 5G network scenarios.
  • FIG. 2 is a flowchart for implementing a method 200 for identifying a service according to an embodiment of the present application.
  • the method can optionally be applied to the systems shown in FIGS. Not limited to this.
  • the method includes at least some of the following:
  • S220 Identify the service corresponding to the received data according to the service information; and/or, determine the service to be initiated according to the service information.
  • the above method can be applied to a terminal device.
  • service information can be added to the PC5 QoS rule or Uu QoS rule, or service information can be added to the data packet header, so that the UE receiving the data can identify the service corresponding to the data, thereby sending the received data to the correct upper application.
  • UE-Network Relay referred to as remote UE
  • remote UE the user equipment
  • the above-mentioned receiving service information may include:
  • Receive PC5 quality of service QoS rules, Uu QoS rules or data, the PC5 QoS rules, the Uu QoS rules or the data packet header of the data carry the above-mentioned business information.
  • the above service information includes at least one of the following:
  • the above-mentioned other identifiers that can be associated with the service information include at least one of slice identifiers, domain names, and Differentiated Services Code Points (DSCP, Differentiated Services Code Points).
  • DSCP Differentiated Services Code Points
  • the terminal device receives the PC5 QoS rule from the opposite terminal device, and the PC5 QoS rule includes service filters and service information;
  • the terminal device uses the service filter to match the received data to determine the service corresponding to the received data. Further, the terminal device can send the received data to the application corresponding to the service.
  • the above-mentioned terminal equipment receives PC5 QoS rules from the opposite terminal equipment, including:
  • the terminal device receives the PC5 QoS flow establishment or modification request from the peer terminal device, and the PC5 QoS flow establishment or modification request carries the PC5 QoS rules corresponding to the services that need to be transmitted in the PC5 QoS flow that needs to be established.
  • Embodiment 1 The above-described embodiments can be applied to the scenario shown in FIG. 1B . A specific implementation manner is described below by using Embodiment 1.
  • FIG. 3 is an implementation flowchart of Embodiment 1 of the present application. As shown in Figure 3, UE-1 and UE-2 establish a connection through the PC5 interface.
  • UE-1 When the service is initiated, UE-1 requests the peer UE-2 to establish or modify the PC5 QoS flow, and UE-1 sends the PC5 QoS flow identifier to be established to UE-2. UE-1 also sends the PC5 QoS rules corresponding to the services to be transmitted in this PC5 QoS flow to UE-2.
  • PC5 QoS rules include service filters and service information. The specific content included in the service information has been introduced in the above content, and will not be repeated here.
  • UE-2 feeds back PC5 QoS flow establishment or modification response to UE-1.
  • UE-1 After the establishment or modification of the PC5 QoS flow is completed, UE-1 sends data to UE-2, and UE-2 uses the service filter in the PC5 QoS rule to match the received data to determine the service information corresponding to the data, so that the received data can be matched.
  • the received data is sent to the corresponding application.
  • the terminal device receives data from the opposite terminal device, and the data packet header of the data carries service information;
  • the terminal device determines the service corresponding to the received data according to the data packet header. Further, the terminal device can send the received data to the application corresponding to the service.
  • Embodiment 2 uses Embodiment 2 to introduce a specific implementation manner.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • FIG. 4 is an implementation flowchart of Embodiment 2 of the present application. As shown in FIG. 4 , UE-1 and UE-2 have established a connection through the PC5 interface in advance.
  • UE-1 When sending data through the PC5 interface, UE-1 sends data to UE-2 at the opposite end, and the data packet header of the data carries service information.
  • the specific content included in the service information has been introduced in the above content, and will not be repeated here.
  • UE-2 can determine the service corresponding to the received data according to the data packet header. Further, UE-2 may send the received data to the application corresponding to the service.
  • the terminal device receives the Uu QoS rule from the network device, and the Uu QoS rule includes service filters and service information;
  • the terminal device uses the service filter to match the received data to determine the service corresponding to the received data. Further, the terminal device can send the received data to the application corresponding to the service.
  • Embodiment 3 The above-described embodiments can be applied to the scenario shown in FIG. 1A .
  • the specific implementation manner is described below by using Embodiment 3.
  • FIG. 5 is an implementation flowchart of Embodiment 3 of the present application. As shown in Figure 5, the UE accesses the 3GPP network through the Uu interface.
  • the PCF sends the policy and charging control (PCC, Policy and charging control) rules to the SMF.
  • the PCC rules include service filters and service information. The specific content of the service information has been introduced in the above content, here No longer.
  • the SMF determines the QoS flow corresponding to the PCC rule, and generates a Uu QoS rule.
  • the Uu QoS rule includes service filters, service information, and QoS flow identifiers.
  • the SMF sends the Uu QoS rules to the UE.
  • the UE uses the service filter in the Uu QoS rule to match the received data to determine the service corresponding to the received data, so that the received data can be sent to the corresponding application.
  • the terminal device receives data from the network device, and the data packet header of the data carries the service information;
  • the service corresponding to the received data is determined according to the data packet header. Further, the terminal device can send the received data to the application corresponding to the service.
  • Embodiment 4 The above-described embodiments can be applied to the scenario shown in FIG. 1A . A specific implementation manner is described below by using Embodiment 4.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • FIG. 6 is an implementation flowchart of Embodiment 4 of the present application. As shown in FIG. 6, the UE and the network device (eg, SMF, UPF, etc.) have established a connection.
  • the network device eg, SMF, UPF, etc.
  • the network device sends data to the UE, and the data packet header of the data carries service information.
  • the specific content included in the service information has been introduced in the above content, and will not be repeated here.
  • the UE may determine the service corresponding to the received data according to the data packet header. Further, the UE may send the received data to the application corresponding to the service.
  • the relay UE receives PC5 QoS rules from the remote UE, the PC5 QoS rules include traffic information;
  • the relay UE determines the service to be initiated by the remote UE according to the PC5 QoS rule.
  • the relay UE may request the network device to establish a PDU session parameter or a QoS parameter corresponding to the service to be initiated by the remote UE.
  • the above-mentioned relay UE receiving the PC5 QoS rule from the remote UE includes: the relay UE receives the PC5 QoS flow establishment or modification request from the remote UE, and the PC5 QoS flow establishment or modification request carries the need in the PC5 QoS flow that needs to be established.
  • PC5 QoS rule corresponding to the transmitted service includes: the relay UE receives the PC5 QoS flow establishment or modification request from the remote UE, and the PC5 QoS flow establishment or modification request carries the need in the PC5 QoS flow that needs to be established.
  • Embodiment 5 uses Embodiment 5 to introduce a specific implementation manner.
  • Embodiment 5 is a diagrammatic representation of Embodiment 5:
  • FIG. 7 is an implementation flowchart of Embodiment 5 of the present application. As shown in Figure 7, the remote UE actively initiates the establishment of a QoS flow.
  • the remote UE When the service is initiated, the remote UE requests the relay UE to establish or modify the PC5 QoS flow, and the remote UE sends the PC5 QoS flow identifier to be established to the relay UE.
  • the remote UE also sends the PC5 QoS rules corresponding to the services to be transmitted in this PC5 QoS flow to the relay UE.
  • PC5 QoS rules include service filters and service information. The specific content included in the service information has been introduced in the above content, and will not be repeated here.
  • the relay UE determines the service information of the service that the remote UE needs to initiate according to the PC5 QoS rules received from the remote UE, so that it can request the network to establish the PDU session parameters or QoS parameters corresponding to the service to be initiated, such as determining the slice identifier of the PDU session. , Session and Service Continuity (SSC, Session and Service Continuity) mode, or request corresponding QoS parameters.
  • SSC Session and Service Continuity
  • the relay UE receives data from the remote UE, and the data packet header of the data carries service information;
  • the relay UE determines the service corresponding to the received data according to the data packet header.
  • the relay UE requests the network device to establish a PDU session parameter or a QoS parameter corresponding to the service corresponding to the received data.
  • Embodiment 6 The above-described embodiments can be applied to the scenario shown in FIG. 1C .
  • the specific implementation manner is described below by using Embodiment 6.
  • Embodiment 6 is a diagrammatic representation of Embodiment 6
  • FIG. 8 is an implementation flowchart of Embodiment 6 of the present application. As shown in Figure 8, the remote UE and the relay UE are connected in advance through the PC5 interface.
  • the remote UE sends data to the relay UE, and the data packet header in the data carries service information.
  • the specific content included in the service information has been introduced in the above content, and will not be repeated here.
  • the relay UE can determine the service corresponding to the received data according to the data packet header. Further, the relay UE may request the network device (such as SMF) to establish a PDU session parameter or QoS parameter corresponding to the service corresponding to the received data.
  • the network device such as SMF
  • the relay UE receives a Uu QoS rule from a network device (such as an SMF), and the Uu QoS rule includes service information;
  • a network device such as an SMF
  • the relay UE determines the service to be initiated to the remote UE according to the Uu QoS rule.
  • the relay UE can determine the QoS parameters of the PC5 QoS flow according to the service information; send a PC5 QoS flow establishment or modification request to the remote UE, and the PC5 QoS flow establishment or modification request carries the QoS parameters of the PC5 QoS flow.
  • the PC5 QoS flow establishment or modification request may also carry PC5 QoS rules, and the PC5 QoS rules include service filters and service information.
  • Embodiment 7 uses Embodiment 7 to introduce a specific implementation manner.
  • Embodiment 7 is a diagrammatic representation of Embodiment 7:
  • FIG. 9 is an implementation flowchart of Embodiment 7 of the present application. As shown in Figure 9, the network side actively initiates the establishment of a QoS flow.
  • the PCF sends PCC rules to the SMF.
  • the PCC rules include service filters and service information. The specific content included in the service information has been introduced in the above content, and will not be repeated here.
  • the SMF determines the QoS flow corresponding to the PCC rule, and generates a Uu QoS rule.
  • the Uu QoS rule includes service filters, service information and QoS flow identifiers.
  • SMF sends Uu QoS rules to relay UE.
  • the relay UE determines the service information of the service that needs to be initiated to the remote UE according to the Uu QoS rules received from the SMF, thereby determining the QoS parameters of the PC5 QoS flow (such as PC5 5G QoS identifier (PQI, PC5 5 QI), code rate requirements, etc. ).
  • the relay UE requests the remote UE to establish or modify the PC5 QoS flow, which carries the QoS parameters of the above PC5 QoS flow. It can also carry PC5 QoS rules.
  • the PC5 QoS rules include service filters and service information, which are used by the remote UE to match the received data using the service filters in the PC5 QoS rules to determine the service information corresponding to the data.
  • the received data is sent to the corresponding application.
  • the relay UE receives data from a network device (such as SMF), and the data packet header of the data carries service information;
  • a network device such as SMF
  • the relay UE determines the service corresponding to the received data according to the data packet header.
  • the relay UE can determine the QoS parameters of the PC5 QoS flow according to the service information; send a PC5 QoS flow establishment or modification request to the remote UE, and the PC5 QoS flow establishment or modification request carries the QoS parameters of the PC5 QoS flow.
  • the PC5 QoS flow establishment or modification request may also carry PC5 QoS rules, and the PC5 QoS rules include service filters and service information.
  • Embodiment 8 uses Embodiment 8 to introduce a specific implementation manner.
  • Embodiment 8 is a diagrammatic representation of Embodiment 8
  • FIG. 10 is an implementation flowchart of Embodiment 8 of the present application. As shown in Figure 10, the network side actively initiates the establishment of a QoS flow.
  • the PCF sends PCC rules to the SMF.
  • the PCC rules include service filters and service information. The specific content included in the service information has been introduced in the above content, and will not be repeated here.
  • the SMF sends data to the relay UE, and the data packet header of the data carries service information.
  • the relay UE determines the service information of the service that needs to be initiated to the remote UE according to the data packet header of the data received from the SMF, thereby determining the QoS parameters (such as PQI, code rate requirements, etc.) of the PC5 QoS flow.
  • the relay UE requests the remote UE to establish or modify the PC5 QoS flow, which carries the QoS parameters of the above PC5 QoS flow. It can also carry PC5 QoS rules.
  • the PC5 QoS rules include service filters and service information, which are used by the remote UE to match the received data using the service filters in the PC5 QoS rules to determine the service information corresponding to the data.
  • the received data is sent to the corresponding application.
  • the embodiments of the present application use the UE to receive service information, which solves the problem in the prior art that the UE receiving data needs to rely on the assistance of the operating system to send the received data to the corresponding application; it also solves the problem of short distance
  • the relay UE when the remote UE accesses the network through the relay UE, the relay UE cannot determine the services that the remote UE needs to initiate, resulting in the problem that appropriate PDU session parameters and QoS parameters cannot be set for the remote UE.
  • Fig. 11 is an implementation flowchart of a method 1100 for sending service information according to an embodiment of the present application.
  • the method can optionally be applied to the systems shown in Figs. 1A to 1C, but is not limited thereto.
  • the method includes at least some of the following.
  • the service information is used for the peer terminal device to identify the service corresponding to the received data; and/or to determine the service to be initiated.
  • the above service information includes at least one of the following:
  • the above-mentioned other identifiers that can be associated with the service information include at least one of slice identifiers, domain names, and DSCP.
  • the above-mentioned sending service information includes: sending a PC5 QoS rule, where the PC5 QoS rule carries a service filter and the service information.
  • the above-mentioned sending PC5 QoS rules includes: sending a PC5 QoS flow establishment or modification request, and the PC5 QoS flow establishment or modification request carries the PC5 QoS rules corresponding to the business that needs to be transmitted in the PC5 QoS flow that needs to be established.
  • the sending of the service information includes: sending data, the data packet header of which carries the service information.
  • FIG. 12 is an implementation flowchart of a method 1200 for sending service information according to an embodiment of the present application.
  • the method can optionally be applied to the systems shown in FIGS. 1A and 1C , but is not limited thereto.
  • the method includes at least some of the following:
  • the service information is used by the terminal device to identify the service corresponding to the received data; and/or, to determine the service to be initiated.
  • the above method can be applied to network devices such as SMF.
  • the above service information includes at least one of the following:
  • the above-mentioned other identifiers that can be associated with the service information include at least one of slice identifiers, domain names, and DSCP.
  • the above-mentioned sending service information includes: sending a Uu QoS rule, where the Uu QoS rule includes a service filter and the service information.
  • Receive PCC rules which include service filters and service information
  • the Uu QoS rule is generated according to the PCC rule.
  • the above-mentioned sending the service information includes: sending data, and the data packet header of the data carries the service information.
  • FIG. 13 is a flow chart for implementing a PCC rule sending method 1300 according to an embodiment of the present application.
  • the method can optionally be applied to the systems shown in FIG. 1A and FIG. 1C , but is not limited thereto.
  • the method includes at least some of the following:
  • S1310 Send a PCC rule, where the PCC rule includes service filters and service information;
  • the service information is used by the terminal device to identify the service corresponding to the received data; and/or, to determine the service to be initiated.
  • the above method can be used with network equipment such as PCF.
  • the above service information includes at least one of the following:
  • the above-mentioned other identifiers that can be associated with the service information include at least one of slice identifiers, domain names, and DSCP.
  • FIG. 14 is a schematic structural diagram of a terminal device 1400 according to an embodiment of the present application, including:
  • a receiving module 1410 configured to receive service information
  • the determining module 1420 is configured to identify the service corresponding to the received data according to the service information; and/or, determine the service to be initiated according to the service information.
  • the above receiving module 1410 is used for:
  • the above service information includes at least one of the following:
  • the other identifiers that can be associated with the service information include at least one of slice identifiers, domain names, and differentiated services code point DSCP.
  • the above-mentioned receiving module 1410 receives PC5 QoS rules from the opposite terminal equipment, and the PC5 QoS rules include service filters and the service information;
  • the determining module 1420 uses the service filter to match the received data to determine the service corresponding to the received data.
  • the above-mentioned receiving module 1410 receives the PC5 QoS flow establishment or modification request from the opposite terminal equipment, and the PC5 QoS flow establishment or modification request carries the PC5 corresponding to the business that needs to be transmitted in the PC5 QoS flow that needs to be established. QoS rules.
  • the above-mentioned receiving module 1410 receives data from the opposite terminal device, and the data packet header of the data carries the above-mentioned service information;
  • the determining module 1420 determines the service corresponding to the received data according to the data packet header.
  • the above-mentioned receiving module 1410 receives the Uu QoS rule from the network device, and the Uu QoS rule includes the service filter and the above-mentioned service information;
  • the determining module 1420 uses the service filter to match the received data to determine the service corresponding to the received data.
  • the above-mentioned receiving module 1410 receives data from a network device, and the data packet header of the data carries the above-mentioned service information;
  • the determining module 1420 determines the service corresponding to the received data according to the data packet header.
  • the above-mentioned terminal device is further configured to: send the received data to an application corresponding to the service.
  • the above-mentioned receiving module 1410 receives a PC5 QoS rule from a remote UE, and the PC5 QoS rule includes the service information;
  • the above determination module 1420 determines the service to be initiated by the remote UE according to the PC5 QoS rule.
  • the above-mentioned receiving module 1410 receives the PC5 QoS flow establishment or modification request from the remote UE, and the PC5 QoS flow establishment or modification request carries the PC5 QoS rule corresponding to the business that needs to be transmitted in the PC5 QoS flow that needs to be established. .
  • the receiving module 1410 receives data from a remote UE, and the data packet header of the data carries the service information;
  • the determining module 1420 determines the service corresponding to the received data according to the data packet header.
  • the above-mentioned network device is further configured to request the network device to establish a PDU session parameter or QoS parameter corresponding to the service corresponding to the received data or the service to be initiated by the remote UE.
  • the above-mentioned receiving module 1410 receives the Uu QoS rule from the network device, and the Uu QoS rule includes the service information;
  • the determining module 1420 determines the service to be initiated to the remote UE according to the Uu QoS rule.
  • the receiving module 1410 receives data from a network device, and the data packet header of the data carries the service information;
  • the determining module 1420 determines the service corresponding to the received data according to the data packet header.
  • the above-mentioned terminal equipment is also used for:
  • the above-mentioned PC5 QoS flow establishment or modification request also carries PC5 QoS rules, and the PC5 QoS rules include service filters and the service information.
  • FIG. 15 is a schematic structural diagram of the terminal device 1500 according to the embodiment of the present application, including:
  • a first sending module 1510 configured to send service information
  • the service information is used for the peer terminal device to identify the service corresponding to the received data; and/or to determine the service to be initiated.
  • the above service information includes at least one of the following:
  • the above-mentioned other identifiers that can be associated with the service information include at least one of slice identifiers, domain names, and DSCP.
  • the above-mentioned first sending module 1510 sends a PC5 QoS rule, where the PC5 QoS rule carries a service filter and the service information.
  • the above-mentioned first sending module 1510 sends a PC5 QoS flow establishment or modification request, and the PC5 QoS flow establishment or modification request carries the PC5 QoS rule corresponding to the business that needs to be transmitted in the PC5 QoS flow that needs to be established.
  • the first sending module 1510 sends data, and the data packet header of the data carries the service information.
  • FIG. 16 is a schematic structural diagram of a network device 1600 according to an embodiment of the present application, including:
  • a second sending module 1610 configured to send service information
  • the service information is used by the terminal device to identify the service corresponding to the received data; and/or, to determine the service to be initiated.
  • the above service information includes at least one of the following:
  • the above-mentioned other identifiers that can be associated with the service information include at least one of slice identifiers, domain names, and DSCP.
  • the above-mentioned second sending module 1610 sends Uu QoS rules, where the Uu QoS rules include service filters and the service information.
  • the above network device is also used for:
  • PCC rules include service filters and service information
  • the Uu QoS rules are generated according to the PCC rules.
  • the above-mentioned second sending module 1610 sends data, and the data packet header of the data carries the service information.
  • the above-mentioned network device may be an SMF.
  • FIG. 17 is a schematic structural diagram of a network device 1700 according to an embodiment of the present application, including:
  • the third sending module 1710 is configured to send PCC rules, where the PCC rules include service filters and service information;
  • the service information is used by the terminal device to identify the service corresponding to the received data; and/or, to determine the service to be initiated.
  • the above service information includes at least one of the following:
  • the above-mentioned other identifiers that can be associated with the service information include at least one of slice identifiers, domain names, and DSCP.
  • FIG. 18 is a schematic structural diagram of a communication device 1800 according to an embodiment of the present application.
  • the communication device 1800 shown in FIG. 18 includes a processor 1810, and the processor 1810 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
  • the communication device 1800 may further include a memory 1820 .
  • the processor 1810 may call and run a computer program from the memory 1820 to implement the methods in the embodiments of the present application.
  • the memory 1820 may be a separate device independent of the processor 1810, or may be integrated in the processor 1810.
  • the communication device 1800 may further include a transceiver 1830, and the processor 1810 may control the transceiver 1830 to communicate with other devices, specifically, may send information or data to other devices, or receive other devices Information or data sent by a device.
  • the transceiver 1830 may include a transmitter and a receiver.
  • the transceiver 1830 may further include an antenna, and the number of the antenna may be one or more.
  • the communication device 1800 may be a terminal device of this embodiment of the present application, and the communication device 1800 may implement the corresponding processes implemented by the terminal device in each method of this embodiment of the present application, which is not repeated here for brevity.
  • the communication device 1800 may be a network device of this embodiment of the present application, and the communication device 1800 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which is not repeated here for brevity.
  • FIG. 19 is a schematic structural diagram of a chip 1900 according to an embodiment of the present application.
  • the chip 1900 shown in FIG. 19 includes a processor 1910, and the processor 1910 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
  • the chip 1900 may further include a memory 1920 .
  • the processor 1910 may call and run a computer program from the memory 1920 to implement the methods in the embodiments of the present application.
  • the memory 1920 may be a separate device independent of the processor 1910, or may be integrated in the processor 1910.
  • the chip 1900 may further include an input interface 1930 .
  • the processor 1910 can control the input interface 1930 to communicate with other devices or chips, and specifically, can obtain information or data sent by other devices or chips.
  • the chip 1900 may further include an output interface 1940 .
  • the processor 1910 can control the output interface 1940 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.
  • the chip can be applied to the terminal device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application, which is not repeated here for brevity.
  • the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiment of the present application, which is not repeated here for brevity.
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processor (DSP), an off-the-shelf programmable gate array (field programmable gate array, FPGA), an application specific integrated circuit (ASIC) or Other programmable logic devices, transistor logic devices, discrete hardware components, etc.
  • DSP digital signal processor
  • FPGA field programmable gate array
  • ASIC application specific integrated circuit
  • the general-purpose processor mentioned above may be a microprocessor or any conventional processor or the like.
  • the memory mentioned above may be either volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be random access memory (RAM).
  • the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions may be stored on or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted over a wire from a website site, computer, server or data center (eg coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (eg infrared, wireless, microwave, etc.) means to another website site, computer, server or data center.
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes an integration of one or more available media.
  • the available media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVD), or semiconductor media (eg, Solid State Disk (SSD)), and the like.
  • the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例涉及业务识别方法、终端设备和网络设备，其中方法包括，接收业务信息；根据该业务信息识别接收到的数据所对应的业务；和/或，根据该业务信息确定所要发起的业务。本申请实施例可以使接收端UE能够识别业务信息。

Description

业务识别方法、终端设备和网络设备 技术领域
本申请涉及通信领域，并且更具体地，涉及业务识别方法、终端设备和网络设备。
背景技术
具有临近业务(Prose，Proximity-based Services)能力的用户设备(UE，User Equipment)可以通过PC5无线接口与具有Prose能力的另外一个UE直接通信。由两个UE各自根据业务的服务质量(QoS，Quality of Service)需求确定业务数据传输所对应的QoS要求，并在两个UE之间建立可以保障相应QoS要求的PC5 QoS数据流进行业务数据的传输，一个PC5 QoS数据流上可以传输多种业务的数据，一个业务的数据也可以通过多个PC5 QoS数据流传输。当接收方的UE接收到数据之后，可以将数据统一发送给网络层以上的某个数据处理单元(例如操作系统，或者多个应用共享的数据处理单元)，由这个数据处理单元对数据进行区分，并发给相应的应用。但是接收方的UE对该数据处理单元有较强的依赖，当无法获得该数据处理单元的协助时，就无法对数据进行区分，从而无法将数据发送到对应的应用。
当一个UE既具有通过5G网络连接外部数据网络，并具有Prose能力时，这个UE可以充当中继(relay)UE，另外一个具有Prose能力的远程(remote)UE可以通过PC5接口与relay UE建立直接连接，并通过relay UE与5G网络建立的协议数据单元(PDU，Protocol Data Unit)会话与外部网络交互。relay UE接入第三代合作伙伴计划(3GPP，3rd Generation Partnership Project)网络时，会考虑需要传输的业务，为不同的业务可以设置不同的PDU会话或者QoS流的参数，但是对于remote UE通过PC5接口发送给relay UE的数据，relay UE无法进行业务区分，从而也无法正确设置relay UE到核心网的PDU会话或QoS流的参数。
可见，现有技术中一些情况下接收端UE无法识别业务信息，导致通信无法正常进行。
发明内容
本申请实施例提供业务识别方法、终端设备和网络设备，可以使接收端UE能够识别业务信息，保证通信正常进行。
本申请实施例提出一种业务识别方法，应用于终端设备，包括：
接收业务信息；
根据业务信息识别接收到的数据所对应的业务；和/或，根据业务信息确定所要发起的业务。
本申请实施例还提出一种业务信息发送方法，应用于终端设备，包括：
发送业务信息；
业务信息用于对端终端设备识别接收到的数据所对应的业务；和/或，确定所要发起的业务。
本申请实施例提出一种业务信息发送方法，应用于网络设备，包括：
发送业务信息；
业务信息用于终端设备识别接收到的数据所对应的业务；和/或，确定所要发起的业务。
本申请实施例提出一种策略和计费控制PCC规则发送方法，应用于网络设备，包括：
发送PCC规则，PCC规则中包括业务过滤器及业务信息；
业务信息用于终端设备识别接收到的数据所对应的业务；和/或，确定所要发起的业务。
本申请实施例提出一种终端设备，包括：
接收模块，用于接收业务信息；
确定模块，用于根据业务信息识别接收到的数据所对应的业务；和/或，根据业务信息确定所要发起的业务。
本申请实施例提出一种终端设备，包括：
第一发送模块，用于发送业务信息；
业务信息用于对端终端设备识别接收到的数据所对应的业务；和/或，确定所要发起的业务。
本申请实施例提出一种网络设备，包括：
第二发送模块，用于发送业务信息；
业务信息用于终端设备识别接收到的数据所对应的业务；和/或，确定所要发起的业务。
本申请实施例提出一种网络设备，包括：
第三发送模块，用于发送PCC规则，PCC规则中包括业务过滤器及业务信息；
业务信息用于终端设备识别接收到的数据所对应的业务；和/或，确定所要发起的业务。
本申请实施例提出一种终端设备，包括：处理器和存储器，该存储器用于存储计算机程序，处理器用于调用并运行所述存储器中存储的计算机程序，执行如上述任一项所述的方法。
本申请实施例提出一种通信设备，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如上述任一项所述的方法。
本申请实施例提出一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如上述任一项所述的方法。
本申请实施例提出一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如上述任一项所述的方法。
本申请实施例提出一种计算机可读存储介质，用于存储计算机程序，所述计算机程序使得计算机执行如上述任一项所述的方法。
本申请实施例提出一种计算机可读存储介质，用于存储计算机程序，所述计算机程序使得计算机执行如上述任一项所述的方法。
本申请实施例提出一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行如上述任一项所述的方法。
本申请实施例提出一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行如上述任一项所述的方法。
本申请实施例提出一种计算机程序，所述计算机程序使得计算机执行如权利要求上述任一项所述的方法。
本申请实施例提出一种计算机程序，所述计算机程序使得计算机执行如上述任一项所述的方法。
本申请实施例通过UE接收业务信息，可以根据该业务信息识别接收到的数据所对应的业务或确定所要发起的业务，从而使接收端UE能够识别业务信息，保证通信正常进行。
附图说明
图1A是本申请实施例的应用场景一的示意图。
图1B是本申请实施例的应用场景二的示意图。
图1C是本申请实施例的应用场景三的示意图
图2是根据本申请实施例的一种业务识别方法200实现流程图。
图3是本申请实施例一的实现流程图。
图4是本申请实施例二的实现流程图。
图5是本申请实施例三的实现流程图。
图6是本申请实施例四的实现流程图。
图7是本申请实施例五的实现流程图。
图8是本申请实施例六的实现流程图。
图9是本申请实施例七的实现流程图。
图10是本申请实施例八的实现流程图。
图11是根据本申请实施例的一种业务信息发送方法1100实现流程图。
图12是根据本申请实施例的一种业务信息发送方法1200实现流程图。
图13是根据本申请实施例的一种PCC规则发送方法1300实现流程图。
图14是根据本申请实施例的终端设备1400结构示意图。
图15是根据本申请实施例的终端设备1500结构示意图。
图16是根据本申请实施例的网络设备1600结构示意图。
图17是根据本申请实施例的网络设备1700结构示意图
图18是根据本申请实施例的通信设备1800示意性结构图；
图19是根据本申请实施例的芯片1900的示意性结构图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。
需要说明的是，本申请实施例的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。同时描述的“第一”、“第二”描述的对象可以相同，也可以不同。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile  communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、先进的长期演进(Advanced long term evolution，LTE-A)系统、新无线(New Radio，NR)系统、NR系统的演进系统、免授权频谱上的LTE(LTE-based access to unlicensed spectrum，LTE-U)系统、免授权频谱上的NR(NR-based access to unlicensed spectrum，NR-U)系统、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、无线局域网(Wireless Local Area Networks，WLAN)、无线保真(Wireless Fidelity，WiFi)、下一代通信(5th-Generation，5G)系统或其他通信系统等。
通常来说，传统的通信系统支持的连接数有限，也易于实现，然而，随着通信技术的发展，移动通信系统将不仅支持传统的通信，还将支持例如，设备到设备(Device to Device，D2D)通信，机器到机器(Machine to Machine，M2M)通信，机器类型通信(Machine Type Communication，MTC)，以及车辆间(Vehicle to Vehicle，V2V)通信等，本申请实施例也可以应用于这些通信系统。
可选地，本申请实施例中的通信系统可以应用于载波聚合(Carrier Aggregation，CA)场景，也可以应用于双连接(Dual Connectivity，DC)场景，还可以应用于独立(Standalone，SA)布网场景。
本申请实施例对应用的频谱并不限定。例如，本申请实施例可以应用于授权频谱，也可以应用于免授权频谱。
本申请实施例结合网络设备和终端设备描述了各个实施例，其中：终端设备也可以称为用户设备(User Equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置等。终端设备可以是WLAN中的站点(STAION，ST)，可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)设备、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备以及下一代通信系统，例如，NR网络中的终端设备或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)网络中的终端设备等。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
网络设备可以是用于与移动设备通信的设备，网络设备可以是WLAN中的接入点(Access Point，AP)，GSM或CDMA中的基站(Base Transceiver Station，BTS)，也可以是WCDMA中的基站(NodeB，NB)，还可以是LTE中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者中继站或接入点，或者车载设备、可穿戴设备以及NR网络中的网络设备(gNB)或者未来演进的PLMN网络中的网络设备等。
在本申请实施例中，网络设备为小区提供服务，终端设备通过该小区使用的传输资源(例如，频域资源，或者说，频谱资源)与网络设备进行通信，该小区可以是网络设备(例如基站)对应的小区，小区可以属于宏基站，也可以属于小小区(Small cell)对应的基站，这里的小小区可以包括：城市小区(Metro cell)、微小区(Micro cell)、微微小区(Pico cell)、毫微微小区(Femto cell)等，这些小小区具有覆盖范围小、发射功率低的特点，适用于提供高速率的数据传输服务。
图1A是本申请实施例的应用场景一的示意图。图1A示例性地示出了5G网络系统架构。其中，UE通过Uu无线接口与接入网络(AN，Access Network)进行接入层连接，交互接入层消息及无线数据传输，UE通过N1口与移动性管理功能(AMF，Access and Mobility Management Function)进行非接入层(NAS，None Access Stratum)连接，交互NAS消息。AMF是核心网中的移动性管理功能，会话管理功能(SMF，Session Management Function)是核心网中的会话管理功能，AMF在对UE进行移动性管理之外，还负责将从会话管理相关消息在UE和SMF之间的转发。策略控制功能(PCF，Policy Control Function)是核心网中的策略管理功能，负责制定对UE的移动性管理、会话管理、计费等相关的策略。用户面功能(UPF，User Plane Function)是核心网中的用户面功能，通过N6接口与外部数据网络进行数据传输，通过N3接口与AN进行数据传输。
UE通过Uu口接入5G网络后，通过网络进行业务数据的传输。在业务发起时，UE的网络层从上层(例如操作系统或者应用)获得业务的QoS需求，UE将业务的QoS需求转换为Uu接口的QoS参数，在SMF的控制下通过UE与UPF之间相应的QoS流进行数据传输。
图1B是本申请实施例的应用场景二的示意图。图1B示例性地示出了两个UE之间的PC5单播链路示例。如图1B所示，具有Prose能力的UE可以通过PC5无线接口与具有Prose能力的另外一个UE直接通信。由两个UE各自根据业务的QoS需求确定业务数据传输所对应的QoS要求，并在两个UE之间建立可以保障相应QoS要求的PC5 QoS数据流进行业务数据的传输，从而保证业务在PC5通信的服务质量。一个PC5 QoS数据流上可以传输多种业务的数据，一个业务的数据也可以通过多个PC5 QoS数据流传输。
当一个UE既具有通过5G网络连接外部数据网络，还具有Prose能力时，这个UE可以充当relay UE，另外一个具有Prose能力的remote UE可以通过PC5接口与relay UE建立直接连接，并通过Relay UE与5G网络建立的PDU会话与外部网络交互。图1C是本申请实施例的应用场景三的示意图，如图1C所示，remote UE通过relay UE，即ProSe 5G UE-to-Network Relay与5G网络建立PDU会话。
上述三个应用场景是本申请实施例可能应用的场景示例，本申请实施例不局限于上述三个应用场景，且不局限于5G网络场景。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
本申请实施例提出一种业务识别方法，图2是根据本申请实施例的一种业务识别方法200实现流程图，该方法可选地可以应用于图1A至图1C所示的系统，但并不仅限于此。该方法包括以下内容的至少部分内容：
S210：接收业务信息；
S220：根据该业务信息识别接收到的数据所对应的业务；和/或，根据该业务信息确定所要发起的业务。
上述方法可以应用于终端设备。
本申请实施例可以在PC5 QoS规则或者Uu QoS规则中增加业务信息，或者在数据包头中增加业务信息，使得接收数据的UE可以识别数据所对应的业务，从而将收到的数据发送到正确的上层应用。或者使得作为网络中继的用户设备(UE-Network Relay)(简称remote UE)确定remote UE所需要发起的业务，从而设置合适的PDU会话参数或QoS参数。
具体地，上述接收业务信息可以包括：
接收PC5服务质量QoS规则、Uu QoS规则或数据，该PC5 QoS规则中、该Uu QoS规则中或该数据的数据包头中携带上述业务信息。
可选地，上述业务信息包括以下至少一项：
业务标识；
业务代码；
应用标识；
业务提供商的标识；
业务类型；
可以关联到业务信息的其他标识。
可选地，上述可以关联到业务信息的其他标识包括切片标识、域名及差分服务代码点(DSCP，Differentiated Services Code Point)中的至少一项。
在一些实施方式中，终端设备从对端终端设备接收PC5 QoS规则，该PC5 QoS规则中包括业务过滤器及业务信息；
终端设备对接收到的数据使用该业务过滤器进行匹配，确定接收到的数据所对应的业务。进一步地，终端设备可以将接收到的数据发送至该业务对应的应用。
可选地，上述终端设备从对端终端设备接收PC5 QoS规则，包括：
终端设备从对端终端设备接收PC5 QoS流建立或修改请求，该PC5 QoS流建立或修改请求中携带需要建立的PC5 QoS流中需要传输的业务所对应的PC5 QoS规则。
上述实施方式可以应用于图1B所示的场景。以下采用实施例一介绍具体的实现方式。
实施例一：
图3是本申请实施例一的实现流程图。如图3所示，UE-1和UE-2通过PC5接口建立连接。
业务发起时，UE-1向对端的UE-2请求建立或者修改PC5 QoS流，UE-1将需要建立的PC5 QoS流标识发送给UE-2。UE-1还将这个PC5 QoS流中需要传输的业务所对应的PC5 QoS规则发送给UE-2。PC5 QoS规则中包括业务过滤器以及业务信息。业务信息包含的具体内容在上述内容中已有介绍，在此不再赘述。
UE-2向UE-1反馈PC5 QoS流建立或修改响应。
PC5 QoS流建立或者修改完成之后，UE-1向UE-2发送数据，UE-2对接收的数据使用PC5 QoS规则中的业务过滤器进行匹配，确定数据所对应的业务信息，从而可以将收到的数据发送到对应的应用。
在一些实施方式中，终端设备从对端终端设备接收数据，该数据的数据包头中携带业务信息；
终端设备根据该数据包头确定接收到的数据所对应的业务。进一步地，终端设备可以将接收到的数据发送至该业务对应的应用。
上述实施方式可以应用于图1B所示的场景。以下采用实施例二介绍具体的实现方式。
实施例二：
图4是本申请实施例二的实现流程图。如图4所示，UE-1和UE-2预先通过PC5接口建立了连接。
通过PC5接口发送数据时，UE-1向对端的UE-2发送数据，该数据的数据包头中携带业务信息。业务信息包含的具体内容在上述内容中已有介绍，在此不再赘述。UE-2可以根据该数据包头确定接收到的数据所对应的业务。进一步地，UE-2可以将接收到的数据发送至该业务对应的应用。
在一些实施方式中，终端设备从网络设备接收Uu QoS规则，该Uu QoS规则中包括业务过滤器及业务信息；
终端设备对接收到的数据使用该业务过滤器进行匹配，确定接收到的数据所对应的业务。进一步地，终端设备可以将接收到的数据发送至该业务对应的应用。
上述实施方式可以应用于图1A所示的场景。以下采用实施例三介绍具体的实现方式。
实施例三：
图5是本申请实施例三的实现流程图。如图5所示，UE通过Uu接口接入3GPP网络。
业务发起时，PCF向SMF发送策略和计费控制(PCC，Policy and charging control)规则，PCC规则中包括业务过滤器以及业务信息，业务信息包含的具体内容在上述内容中已有介绍，在此不再赘述。SMF确定PCC规则所对应的QoS流，并生成Uu QoS规则，Uu QoS规则中包括业务过滤器、业务信息、QoS流标识。SMF将Uu QoS规则发送给UE。
当数据从网络侧发送到UE之后，UE对接收的数据使用Uu QoS规则中的业务过滤器进行匹配，确定接收到的数据所对应的业务，从而可以将收到的数据发送到对应的应用。
在一些实施方式中，终端设备从网络设备接收数据，该数据的数据包头中携带所述业务信息；
根据该数据包头确定接收到的数据所对应的业务。进一步地，终端设备可以将接收到的数据发送至该业务对应的应用。
上述实施方式可以应用于图1A所示的场景。以下采用实施例四介绍具体的实现方式。
实施例四：
图6是本申请实施例四的实现流程图。如图6所示，UE和网络设备(例如SMF、UPF等)建立了连接。
网络设备向UE发送数据，该数据的数据包头中携带业务信息。业务信息包含的具体内容在上述内容中已有介绍，在此不再赘述。UE可以根据该数据包头确定接收到的数据所对应的业务。进一步地，UE可以将接收到的数据发送至该业务对应的应用。
在一些实施方式中，中继UE从远程UE接收PC5 QoS规则，该PC5 QoS规则中包括业务信息；
中继UE根据该PC5 QoS规则，确定远程UE所要发起的业务。
进一步地，中继UE可以向网络设备请求建立该远程UE所要发起的业务对应的PDU会话参数或QoS参数。
可选地，上述中继UE从远程UE接收PC5 QoS规则包括：中继UE从远程UE接收PC5 QoS流建立或修改请求，该PC5 QoS流建立或修改请求中携带需要建立的PC5 QoS流中需要传输的业务所对应的PC5 QoS规则。
上述实施方式可以应用于图1C所示的场景。以下采用实施例五介绍具体的实现方式。
实施例五：
图7是本申请实施例五的实现流程图。如图7所示，remote UE主动发起QoS流的建立。
业务发起时，remote UE向relay UE请求建立或者修改PC5 QoS流，remote UE将需要建立的PC5QoS流标识发送给relay UE。remote UE还将这个PC5 QoS流中需要传输的业务所对应的PC5 QoS规则发送给relay UE。PC5 QoS规则中包括业务过滤器以及业务信息。业务信息包含的具体内容在上述内容中已有介绍，在此不再赘述。
relay UE根据从remote UE收到的PC5 QoS规则，确定remote UE所需要发起的业务的业务信息，从而可以向网络请求建立所要发起业务对应的PDU会话参数或者QoS参数，例如确定PDU会话的切片标识、会话和服务连续模式(SSC，Session and Service Continuity)模式、或者请求相应的QoS参数。
在一些实施方式中，中继UE从远程UE接收数据，该数据的数据包头中携带业务信息；
中继UE根据该数据包头确定接收到的数据所对应的业务。
进一步地，中继UE向网络设备请求建立该接收到的数据所对应的业务对应的PDU会话参数或QoS参数。
上述实施方式可以应用于图1C所示的场景。以下采用实施例六介绍具体的实现方式。
实施例六：
图8是本申请实施例六的实现流程图。如图8所示，remote UE和relay UE预先通过PC5接口建立了连接。
remote UE向relay UE发送数据，该数据中的数据包头中携带业务信息。业务信息包含的具体内容在上述内容中已有介绍，在此不再赘述。relay UE可以根据该数据包头确定接收到的数据所对应的业务。进一步地，relay UE可以向网络设备(如SMF)请求建立该接收到的数据所对应的业务对应的PDU会话参数或QoS参数。
在一些实施方式中，中继UE从网络设备(如SMF)接收Uu QoS规则，该Uu QoS规则中包括业务信息；
中继UE根据该Uu QoS规则，确定向远程UE所要发起的业务。
进一步地，中继UE可以根据该业务信息确定PC5 QoS流的QoS参数；向远程UE发送PC5 QoS流建立或修改请求，该PC5 QoS流建立或修改请求中携带该PC5 QoS流的QoS参数。该PC5 QoS流建立或修改请求中还可以携带PC5 QoS规则，该PC5 QoS规则中包括业务过滤器及业务信息。
上述实施方式可以应用于图1C所示的场景。以下采用实施例七介绍具体的实现方式。
实施例七：
图9是本申请实施例七的实现流程图。如图9所示，网络侧主动发起QoS流的建立。
业务发起时，PCF向SMF发送PCC规则，PCC规则中包括业务过滤器以及业务信息，业务信息包含的具体内容在上述内容中已有介绍，在此不再赘述。
SMF确定PCC规则所对应的QoS流，并生成Uu QoS规则，Uu QoS规则中包括业务过滤器、业务信息及QoS流标识。SMF将Uu QoS规则发送给relay UE。
relay UE根据从SMF收到的Uu QoS规则，确定需要向remote UE发起的业务的业务信息，从而确定PC5 QoS流的QoS参数(例如PC5 5G QoS标识(PQI，PC5 5 QI)，码率要求等)。relay UE向remote UE请求建立或者修改PC5 QoS流，其中携带上述PC5 QoS流的QoS参数。还可以携带PC5 QoS规则，PC5 QoS规则中包括业务过滤器以及业务信息，用于remote UE对接收的数据使用PC5 QoS规则中的业务过滤器进行匹配，确定数据所对应的业务信息，从而可以将收到的数据发送到对应的应用。
在一些实施方式中，中继UE从网络设备(如SMF)接收数据，该数据的数据包头中携带业务信息；
中继UE根据数据包头确定接收到的数据所对应的业务。
进一步地，中继UE可以根据该业务信息确定PC5 QoS流的QoS参数；向远程UE发送PC5 QoS流建立或修改请求，该PC5 QoS流建立或修改请求中携带该PC5 QoS流的QoS参数。该PC5 QoS流建立或修改请求中还可以携带PC5 QoS规则，该PC5 QoS规则中包括业务过滤器及业务信息。
上述实施方式可以应用于图1C所示的场景。以下采用实施例八介绍具体的实现方式。
实施例八：
图10是本申请实施例八的实现流程图。如图10所示，网络侧主动发起QoS流的建立。
业务发起时，PCF向SMF发送PCC规则，PCC规则中包括业务过滤器以及业务信息，业务信息包含的具体内容在上述内容中已有介绍，在此不再赘述。
SMF向relay UE发送数据，该数据的数据包头中携带业务信息。
relay UE根据从SMF收到的数据的数据包头，确定需要向remote UE发起的业务的业务信息，从而确定PC5 QoS流的QoS参数(例如PQI，码率要求等)。relay UE向remote UE请求建立或者修改PC5QoS流，其中携带上述PC5 QoS流的QoS参数。还可以携带PC5 QoS规则，PC5 QoS规则中包括业务过滤器以及业务信息，用于remote UE对接收的数据使用PC5 QoS规则中的业务过滤器进行匹配，确定数据所对应的业务信息，从而可以将收到的数据发送到对应的应用。
综上可见，本申请实施例通过UE接收业务信息，解决了现有技术中接收数据的UE需要依赖操作系统的协助才可以将收到的数据发送到对应的应用的问题；也解决了近距离通信场景下，remote UE通过relay UE接入到网络时，relay UE无法确定remote UE所需要发起的业务，导致无法为remote UE设置合适的PDU会话参数和QoS参数的问题。
本申请实施例还提出一种业务信息发送方法，应用于终端设备。图11是根据本申请实施例的一种 业务信息发送方法1100实现流程图，该方法可选地可以应用于图1A至图1C所示的系统，但并不仅限于此。该方法包括以下内容的至少部分内容。
S1110：发送业务信息；
该业务信息用于对端终端设备识别接收到的数据所对应的业务；和/或，确定所要发起的业务。
可选地，上述业务信息包括以下至少一项：
业务标识；
业务代码；
应用标识；
业务提供商的标识；
业务类型；
可以关联到业务信息的其他标识。
可选地，上述可以关联到业务信息的其他标识包括切片标识、域名及DSCP中的至少一项。
在一些实施方式中，上述发送业务信息包括：发送PC5 QoS规则，该PC5 QoS规则中携带业务过滤器及该业务信息。
可选地，上述发送PC5 QoS规则包括：发送PC5 QoS流建立或修改请求，该PC5 QoS流建立或修改请求中携带需要建立的PC5 QoS流中需要传输的业务所对应的PC5 QoS规则。
在一些实施方式中，上述发送业务信息包括：发送数据，该数据的数据包头中携带该业务信息。
本申请实施例还提出一种业务信息发送方法，应用于网络设备。图12是根据本申请实施例的一种业务信息发送方法1200实现流程图，该方法可选地可以应用于图1A和图1C所示的系统，但并不仅限于此。该方法包括以下内容的至少部分内容：
S1210：发送业务信息；
该业务信息用于终端设备识别接收到的数据所对应的业务；和/或，确定所要发起的业务。
上述方法可以应用于SMF等网络设备。
可选地，上述业务信息包括以下至少一项：
业务标识；
业务代码；
应用标识；
业务提供商的标识；
业务类型；
可以关联到业务信息的其他标识。
可选地，上述可以关联到业务信息的其他标识包括切片标识、域名及DSCP中的至少一项。
可选地，上述发送业务信息包括：发送Uu QoS规则，该Uu QoS规则中包括业务过滤器及该业务信息。
可选地，上述Uu QoS规则之前，还包括：
接收PCC规则，该PCC规则中包括业务过滤器及业务信息；
根据该PCC规则生成该Uu QoS规则。
可选地，上述发送业务信息包括：发送数据，该数据的数据包头中携带该业务信息。
本申请实施例还提出一种PCC规则发送方法，应用于网络设备。图13是根据本申请实施例的一种PCC规则发送方法1300实现流程图，该方法可选地可以应用于图1A和图1C所示的系统，但并不仅限于此。该方法包括以下内容的至少部分内容：
S1310：发送PCC规则，该PCC规则中包括业务过滤器及业务信息；
该业务信息用于终端设备识别接收到的数据所对应的业务；和/或，确定所要发起的业务。
上述方法可以用于与PCF等网络设备。
可选地，上述业务信息包括以下至少一项：
业务标识；
业务代码；
应用标识；
业务提供商的标识；
业务类型；
可以关联到业务信息的其他标识。
可选地，上述可以关联到业务信息的其他标识包括切片标识、域名及DSCP中的至少一项。
本申请实施例还提出一种终端设备，图14是根据本申请实施例的终端设备1400结构示意图，包括：
接收模块1410，用于接收业务信息；
确定模块1420，用于根据所述业务信息识别接收到的数据所对应的业务；和/或，根据所述业务信息确定所要发起的业务。
可选地，上述接收模块1410用于：
接收PC5服务质量QoS规则、Uu QoS规则或数据，所述PC5 QoS规则中、所述Uu QoS规则中或所述数据的数据包头中携带所述业务信息。
可选地，上述业务信息包括以下至少一项：
业务标识；
业务代码；
应用标识；
业务提供商的标识；
业务类型；
可以关联到业务信息的其他标识。
可选地，上述可以关联到业务信息的其他标识包括切片标识、域名及差分服务代码点DSCP中的至少一项。
可选地，上述接收模块1410从对端终端设备接收PC5 QoS规则，所述PC5 QoS规则中包括业务过滤器及所述业务信息；
确定模块1420对接收到的数据使用所述业务过滤器进行匹配，确定所述接收到的数据所对应的业务。
可选地，上述接收模块1410从所述对端终端设备接收PC5 QoS流建立或修改请求，所述PC5 QoS流建立或修改请求中携带需要建立的PC5 QoS流中需要传输的业务所对应的PC5 QoS规则。
可选地，上述接收模块1410从对端终端设备接收数据，该数据的数据包头中携带所上述业务信息；
确定模块1420根据所述数据包头确定接收到的数据所对应的业务。
可选地，上述接收模块1410从网络设备接收Uu QoS规则，该Uu QoS规则中包括业务过滤器及上述业务信息；
确定模块1420对接收到的数据使用所述业务过滤器进行匹配，确定所述接收到的数据所对应的业务。
可选地，上述接收模块1410从网络设备接收数据，该数据的数据包头中携带上述业务信息；
确定模块1420根据所述数据包头确定接收到的数据所对应的业务。
可选地，上述终端设备还用于：将所述接收到的数据发送至所述业务对应的应用。
可选地，上述接收模块1410从远程UE接收PC5 QoS规则，所述PC5 QoS规则中包括所述业务信息；
可选地，上述确定模块1420根据所述PC5 QoS规则，确定所述远程UE所要发起的业务。
可选地，上述接收模块1410从所述远程UE接收PC5 QoS流建立或修改请求，所述PC5 QoS流建立或修改请求中携带需要建立的PC5 QoS流中需要传输的业务所对应的PC5 QoS规则。
可选地，上述接收模块1410从远程UE接收数据，所述数据的数据包头中携带所述业务信息；
确定模块1420根据所述数据包头确定接收到的数据所对应的业务。
可选地，上述网络设备还用于向网络设备请求建立所述接收到的数据所对应的业务或所述远程UE所要发起的业务对应的PDU会话参数或QoS参数。
可选地，上述接收模块1410从网络设备接收Uu QoS规则，所述Uu QoS规则中包括所述业务信息；
确定模块1420根据所述Uu QoS规则，确定向远程UE所要发起的业务。
可选地，上述接收模块1410从网络设备接收数据，所述数据的数据包头中携带所述业务信息；
确定模块1420根据所述数据包头确定接收到的数据所对应的业务。
可选地，上述终端设备还用于：
根据所述业务信息确定PC5 QoS流的QoS参数；
向远程UE发送PC5 QoS流建立或修改请求，所述PC5 QoS流建立或修改请求中携带所述PC5 QoS流的QoS参数。
可选地，上述PC5 QoS流建立或修改请求中还携带PC5 QoS规则，所述PC5 QoS规则中包括业务过滤器及所述业务信息。
应理解，根据本申请实施例的终端设备中的模块的上述及其他操作和/或功能分别为了实现图2的方法200中的终端设备的相应流程，为了简洁，在此不再赘述。
本申请实施例还提出另一种终端设备，图15是根据本申请实施例的终端设备1500结构示意图，包 括：
第一发送模块1510，用于发送业务信息；
该业务信息用于对端终端设备识别接收到的数据所对应的业务；和/或，确定所要发起的业务。
可选地，上述业务信息包括以下至少一项：
业务标识；
业务代码；
应用标识；
业务提供商的标识；
业务类型；
可以关联到业务信息的其他标识。
可选地，上述可以关联到业务信息的其他标识包括切片标识、域名及DSCP中的至少一项。
可选地，上述第一发送模块1510发送PC5 QoS规则，所述PC5 QoS规则中携带业务过滤器及所述业务信息。
可选地，上述第一发送模块1510发送PC5 QoS流建立或修改请求，所述PC5 QoS流建立或修改请求中携带需要建立的PC5 QoS流中需要传输的业务所对应的PC5 QoS规则。
可选地，上述第一发送模块1510发送数据，所述数据的数据包头中携带所述业务信息。
应理解，根据本申请实施例的终端设备中的模块的上述及其他操作和/或功能分别为了实现图11的方法1100中的终端设备的相应流程，为了简洁，在此不再赘述。
本申请实施例还提出一种网络设备，图16是根据本申请实施例的网络设备1600结构示意图，包括：
第二发送模块1610，用于发送业务信息；
该业务信息用于终端设备识别接收到的数据所对应的业务；和/或，确定所要发起的业务。
可选地，上述业务信息包括以下至少一项：
业务标识；
业务代码；
应用标识；
业务提供商的标识；
业务类型；
可以关联到业务信息的其他标识。
可选地，上述可以关联到业务信息的其他标识包括切片标识、域名及DSCP中的至少一项。
可选地，上述第二发送模块1610发送Uu QoS规则，所述Uu QoS规则中包括业务过滤器及所述业务信息。
可选地，上述网络设备还用于：
接收PCC规则，所述PCC规则中包括业务过滤器及业务信息；
根据所述PCC规则生成所述Uu QoS规则。
可选地，上述第二发送模块1610发送数据，所述数据的数据包头中携带所述业务信息。
上述网络设备可以为SMF。
应理解，根据本申请实施例的网络设备中的模块的上述及其他操作和/或功能分别为了实现图13的方法1300中的网络设备的相应流程，为了简洁，在此不再赘述。
本申请实施例还提出一种网络设备，图17是根据本申请实施例的网络设备1700结构示意图，包括：
第三发送模块1710，用于发送PCC规则，所述PCC规则中包括业务过滤器及业务信息；
该业务信息用于终端设备识别接收到的数据所对应的业务；和/或，确定所要发起的业务。
可选地，上述业务信息包括以下至少一项：
业务标识；
业务代码；
应用标识；
业务提供商的标识；
业务类型；
可以关联到业务信息的其他标识。
可选地，上述可以关联到业务信息的其他标识包括切片标识、域名及DSCP中的至少一项。
应理解，根据本申请实施例的网络设备中的模块的上述及其他操作和/或功能分别为了实现图13的方法1300中的网络设备的相应流程，为了简洁，在此不再赘述。
图18是根据本申请实施例的通信设备1800示意性结构图。图18所示的通信设备1800包括处理器 1810，处理器1810可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图18所示，通信设备1800还可以包括存储器1820。其中，处理器1810可以从存储器1820中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器1820可以是独立于处理器1810的一个单独的器件，也可以集成在处理器1810中。
可选地，如图18所示，通信设备1800还可以包括收发器1830，处理器1810可以控制该收发器1830与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器1830可以包括发射机和接收机。收发器1830还可以进一步包括天线，天线的数量可以为一个或多个。
可选地，该通信设备1800可为本申请实施例的终端设备，并且该通信设备1800可以实现本申请实施例的各个方法中由终端设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该通信设备1800可为本申请实施例的网络设备，并且该通信设备1800可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
图19是根据本申请实施例的芯片1900的示意性结构图。图19所示的芯片1900包括处理器1910，处理器1910可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图19所示，芯片1900还可以包括存储器1920。其中，处理器1910可以从存储器1920中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器1920可以是独立于处理器1910的一个单独的器件，也可以集成在处理器1910中。
可选地，该芯片1900还可以包括输入接口1930。其中，处理器1910可以控制该输入接口1930与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
可选地，该芯片1900还可以包括输出接口1940。其中，处理器1910可以控制该输出接口1940与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
可选地，该芯片可应用于本申请实施例中的终端设备，并且该芯片可以实现本申请实施例的各个方法中由终端设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该芯片可应用于本申请实施例中的网络设备，并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
上述提及的处理器可以是通用处理器、数字信号处理器(digital signal processor，DSP)、现成可编程门阵列(field programmable gate array，FPGA)、专用集成电路(application specific integrated circuit，ASIC)或者其他可编程逻辑器件、晶体管逻辑器件、分立硬件组件等。其中，上述提到的通用处理器可以是微处理器或者也可以是任何常规的处理器等。
上述提及的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)。
应理解，上述存储器为示例性但不是限制性说明，例如，本申请实施例中的存储器还可以是静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行该计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。该计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。该计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，该计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(Digital Subscriber Line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。该计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。该可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(Solid State Disk，SSD))等。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
以上所述仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以该权利要求的保护范围为准。

Claims (76)

  1. 一种业务识别方法，应用于终端设备，包括：
    接收业务信息；
    根据所述业务信息识别接收到的数据所对应的业务；和/或，根据所述业务信息确定所要发起的业务。
  2. 根据权利要求1所述的方法，所述接收业务信息包括：
    接收PC5服务质量QoS规则、Uu QoS规则或数据，所述PC5 QoS规则中、所述Uu QoS规则中或所述数据的数据包头中携带所述业务信息。
  3. 根据权利要求1或2所述的方法，其中，所述业务信息包括以下至少一项：
    业务标识；
    业务代码；
    应用标识；
    业务提供商的标识；
    业务类型；
    可以关联到业务信息的其他标识。
  4. 根据权利要求3所述的方法，所述可以关联到业务信息的其他标识包括切片标识、域名及差分服务代码点DSCP中的至少一项。
  5. 根据权利要求1至4任一所述的方法，其中，
    所述终端设备从对端终端设备接收PC5 QoS规则，所述PC5 QoS规则中包括业务过滤器及所述业务信息；
    对接收到的数据使用所述业务过滤器进行匹配，确定所述接收到的数据所对应的业务。
  6. 根据权利要求5所述的方法，其中，所述终端设备从对端终端设备接收PC5 QoS规则，包括：
    所述终端设备从所述对端终端设备接收PC5 QoS流建立或修改请求，所述PC5 QoS流建立或修改请求中携带需要建立的PC5 QoS流中需要传输的业务所对应的PC5 QoS规则。
  7. 根据权利要求1至4任一所述的方法，其中，
    所述终端设备从对端终端设备接收数据，所述数据的数据包头中携带所述业务信息；
    根据所述数据包头确定接收到的数据所对应的业务。
  8. 根据权利要求1至4任一所述的方法，其中，
    所述终端设备从网络设备接收Uu QoS规则，所述Uu QoS规则中包括业务过滤器及所述业务信息；
    对接收到的数据使用所述业务过滤器进行匹配，确定所述接收到的数据所对应的业务。
  9. 根据权利要求1至4任一所述的方法，其中，
    所述终端设备从网络设备接收数据，所述数据的数据包头中携带所述业务信息；
    根据所述数据包头确定接收到的数据所对应的业务。
  10. 根据权利要求5至9任一所述的方法，还包括：将所述接收到的数据发送至所述业务对应的应用。
  11. 根据权利要求1至4任一所述的方法，其中，
    中继用户设备UE从远程UE接收PC5 QoS规则，所述PC5 QoS规则中包括所述业务信息；
    所述中继UE根据所述PC5 QoS规则，确定所述远程UE所要发起的业务。
  12. 根据权利要求11所述的方法，其中，所述中继UE从远程UE接收PC5 QoS规则，包括：
    所述中继UE从所述远程UE接收PC5 QoS流建立或修改请求，所述PC5 QoS流建立或修改请求中携带需要建立的PC5 QoS流中需要传输的业务所对应的PC5 QoS规则。
  13. 根据权利要求1至4任一所述的方法，其中，
    中继UE从远程UE接收数据，所述数据的数据包头中携带所述业务信息；
    所述中继UE根据所述数据包头确定接收到的数据所对应的业务。
  14. 根据权利要求11至13任一所述的方法，还包括：
    所述中继UE向网络设备请求建立所述接收到的数据所对应的业务或所述远程UE所要发起的业务对应的PDU会话参数或QoS参数。
  15. 根据权利要求1至4任一所述的方法，其中，
    中继UE从网络设备接收Uu QoS规则，所述Uu QoS规则中包括所述业务信息；
    所述中继UE根据所述Uu QoS规则，确定向远程UE所要发起的业务。
  16. 根据权利要求1至4任一所述的方法，其中，
    中继UE从网络设备接收数据，所述数据的数据包头中携带所述业务信息；
    所述中继UE根据所述数据包头确定接收到的数据所对应的业务。
  17. 根据权利要求15或16所述的方法，还包括：
    所述中继UE根据所述业务信息确定PC5 QoS流的QoS参数；
    所述中继UE向远程UE发送PC5 QoS流建立或修改请求，所述PC5 QoS流建立或修改请求中携带所述PC5 QoS流的QoS参数。
  18. 根据权利要求15至17任一所述的方法，所述PC5 QoS流建立或修改请求中还携带PC5 QoS规则，所述PC5 QoS规则中包括业务过滤器及所述业务信息。
  19. 一种业务信息发送方法，应用于终端设备，包括：
    发送业务信息；
    所述业务信息用于对端终端设备识别接收到的数据所对应的业务；和/或，确定所要发起的业务。
  20. 根据权利要求19所述的方法，其中，所述业务信息包括以下至少一项：
    业务标识；
    业务代码；
    应用标识；
    业务提供商的标识；
    业务类型；
    可以关联到业务信息的其他标识。
  21. 根据权利要求20所述的方法，所述可以关联到业务信息的其他标识包括切片标识、域名及DSCP中的至少一项。
  22. 根据权利要求19至21任一所述的方法，所述发送业务信息包括：
    发送PC5 QoS规则，所述PC5 QoS规则中携带业务过滤器及所述业务信息。
  23. 根据权利要求22所述的方法，所述发送PC5 QoS规则包括：
    发送PC5 QoS流建立或修改请求，所述PC5 QoS流建立或修改请求中携带需要建立的PC5 QoS流中需要传输的业务所对应的PC5 QoS规则。
  24. 根据权利要求19至21任一所述的方法，所述发送业务信息，包括：
    发送数据，所述数据的数据包头中携带所述业务信息。
  25. 一种业务信息发送方法，应用于网络设备，包括：
    发送业务信息；
    所述业务信息用于终端设备识别接收到的数据所对应的业务；和/或，确定所要发起的业务。
  26. 根据权利要求25所述的方法，其中，所述业务信息包括以下至少一项：
    业务标识；
    业务代码；
    应用标识；
    业务提供商的标识；
    业务类型；
    可以关联到业务信息的其他标识。
  27. 根据权利要求26所述的方法，所述可以关联到业务信息的其他标识包括切片标识、域名及DSCP中的至少一项。
  28. 根据权利要求25至27任一所述的方法，所述发送业务信息包括：
    发送Uu QoS规则，所述Uu QoS规则中包括业务过滤器及所述业务信息。
  29. 根据权利要求28所述的方法，所述Uu QoS规则之前，还包括：
    接收PCC规则，所述PCC规则中包括业务过滤器及业务信息；
    根据所述PCC规则生成所述Uu QoS规则。
  30. 根据权利要求25至27任一所述的方法，所述发送业务信息包括：
    发送数据，所述数据的数据包头中携带所述业务信息。
  31. 一种策略和计费控制PCC规则发送方法，应用于网络设备，包括：
    发送PCC规则，所述PCC规则中包括业务过滤器及业务信息；
    所述业务信息用于终端设备识别接收到的数据所对应的业务；和/或，确定所要发起的业务。
  32. 根据权利要求31所述的方法，其中，所述业务信息包括以下至少一项：
    业务标识；
    业务代码；
    应用标识；
    业务提供商的标识；
    业务类型；
    可以关联到业务信息的其他标识。
  33. 根据权利要求32所述的方法，所述可以关联到业务信息的其他标识包括切片标识、域名及DSCP中的至少一项。
  34. 一种终端设备，包括：
    接收模块，用于接收业务信息；
    确定模块，用于根据所述业务信息识别接收到的数据所对应的业务；和/或，根据所述业务信息确定所要发起的业务。
  35. 根据权利要求34所述的终端设备，所述接收模块用于：
    接收PC5服务质量QoS规则、Uu QoS规则或数据，所述PC5 QoS规则中、所述Uu QoS规则中或所述数据的数据包头中携带所述业务信息。
  36. 根据权利要求34或35所述的终端设备，其中，所述业务信息包括以下至少一项：
    业务标识；
    业务代码；
    应用标识；
    业务提供商的标识；
    业务类型；
    可以关联到业务信息的其他标识。
  37. 根据权利要求36所述的终端设备，所述可以关联到业务信息的其他标识包括切片标识、域名及差分服务代码点DSCP中的至少一项。
  38. 根据权利要求34至37任一所述的终端设备，其中，
    所述接收模块从对端终端设备接收PC5 QoS规则，所述PC5 QoS规则中包括业务过滤器及所述业务信息；
    所述确定模块对接收到的数据使用所述业务过滤器进行匹配，确定所述接收到的数据所对应的业务。
  39. 根据权利要求38所述的终端设备，其中，所述接收模块从所述对端终端设备接收PC5 QoS流建立或修改请求，所述PC5 QoS流建立或修改请求中携带需要建立的PC5 QoS流中需要传输的业务所对应的PC5 QoS规则。
  40. 根据权利要求34至37任一所述的终端设备，其中，
    所述接收模块从对端终端设备接收数据，所述数据的数据包头中携带所述业务信息；
    所述确定模块根据所述数据包头确定接收到的数据所对应的业务。
  41. 根据权利要求34至37任一所述的终端设备，其中，
    所述接收模块从网络设备接收Uu QoS规则，所述Uu QoS规则中包括业务过滤器及所述业务信息；
    所述确定模块对接收到的数据使用所述业务过滤器进行匹配，确定所述接收到的数据所对应的业务。
  42. 根据权利要求34至37任一所述的终端设备，其中，
    所述接收模块从网络设备接收数据，所述数据的数据包头中携带所述业务信息；
    所述确定模块根据所述数据包头确定接收到的数据所对应的业务。
  43. 根据权利要求38至42任一所述的终端设备，还用于：将所述接收到的数据发送至所述业务对应的应用。
  44. 根据权利要求34至37任一所述的终端设备，其中，
    所述接收模块从远程UE接收PC5 QoS规则，所述PC5 QoS规则中包括所述业务信息；
    所述确定模块根据所述PC5 QoS规则，确定所述远程UE所要发起的业务。
  45. 根据权利要求44所述的终端设备，其中，所述接收模块从所述远程UE接收PC5 QoS流建立或修改请求，所述PC5 QoS流建立或修改请求中携带需要建立的PC5 QoS流中需要传输的业务所对应的PC5 QoS规则。
  46. 根据权利要求34至37任一所述的终端设备，其中，
    所述接收模块从远程UE接收数据，所述数据的数据包头中携带所述业务信息；
    所述确定模块根据所述数据包头确定接收到的数据所对应的业务。
  47. 根据权利要求44至46任一所述的终端设备，还用于：
    向网络设备请求建立所述接收到的数据所对应的业务或所述远程UE所要发起的业务对应的PDU会话参数或QoS参数。
  48. 根据权利要求34至37任一所述的终端设备，其中，
    所述接收模块从网络设备接收Uu QoS规则，所述Uu QoS规则中包括所述业务信息；
    所述确定模块根据所述Uu QoS规则，确定向远程UE所要发起的业务。
  49. 根据权利要求34至37任一所述的终端设备，其中，
    所述接收模块从网络设备接收数据，所述数据的数据包头中携带所述业务信息；
    所述确定模块根据所述数据包头确定接收到的数据所对应的业务。
  50. 根据权利要求48或49所述的终端设备，还用于：
    根据所述业务信息确定PC5 QoS流的QoS参数；
    向远程UE发送PC5 QoS流建立或修改请求，所述PC5 QoS流建立或修改请求中携带所述PC5 QoS流的QoS参数。
  51. 根据权利要求48至50任一所述的终端设备，所述PC5 QoS流建立或修改请求中还携带PC5 QoS规则，所述PC5 QoS规则中包括业务过滤器及所述业务信息。
  52. 一种终端设备，包括：
    第一发送模块，用于发送业务信息；
    所述业务信息用于对端终端设备识别接收到的数据所对应的业务；和/或，确定所要发起的业务。
  53. 根据权利要求52所述的终端设备，其中，所述业务信息包括以下至少一项：
    业务标识；
    业务代码；
    应用标识；
    业务提供商的标识；
    业务类型；
    可以关联到业务信息的其他标识。
  54. 根据权利要求53所述的终端设备，所述可以关联到业务信息的其他标识包括切片标识、域名及DSCP中的至少一项。
  55. 根据权利要求52至54任一所述的终端设备，所述第一发送模块发送PC5 QoS规则，所述PC5QoS规则中携带业务过滤器及所述业务信息。
  56. 根据权利要求55所述的终端设备，所述第一发送模块发送PC5 QoS流建立或修改请求，所述PC5 QoS流建立或修改请求中携带需要建立的PC5 QoS流中需要传输的业务所对应的PC5 QoS规则。
  57. 根据权利要求52至54任一所述的终端设备，所述第一发送模块发送数据，所述数据的数据包头中携带所述业务信息。
  58. 一种网络设备，包括：
    第二发送模块，用于发送业务信息；
    所述业务信息用于终端设备识别接收到的数据所对应的业务；和/或，确定所要发起的业务。
  59. 根据权利要求58所述的网络设备，其中，所述业务信息包括以下至少一项：
    业务标识；
    业务代码；
    应用标识；
    业务提供商的标识；
    业务类型；
    可以关联到业务信息的其他标识。
  60. 根据权利要求59所述的网络设备，所述可以关联到业务信息的其他标识包括切片标识、域名及DSCP中的至少一项。
  61. 根据权利要求58至60任一所述的网络设备，所述发送业务信息包括：
    发送Uu QoS规则，所述Uu QoS规则中包括业务过滤器及所述业务信息。
  62. 根据权利要求61所述的网络设备，还用于：
    接收PCC规则，所述PCC规则中包括业务过滤器及业务信息；
    根据所述PCC规则生成所述Uu QoS规则。
  63. 根据权利要求58至60任一所述的网络设备，所述第二发送模块发送数据，所述数据的数据包头中携带所述业务信息。
  64. 一种网络设备，包括：
    第三发送模块，用于发送PCC规则，所述PCC规则中包括业务过滤器及业务信息；
    所述业务信息用于终端设备识别接收到的数据所对应的业务；和/或，确定所要发起的业务。
  65. 根据权利要求64所述的网络设备，其中，所述业务信息包括以下至少一项：
    业务标识；
    业务代码；
    应用标识；
    业务提供商的标识；
    业务类型；
    可以关联到业务信息的其他标识。
  66. 根据权利要求65所述的网络设备，所述可以关联到业务信息的其他标识包括切片标识、域名及DSCP中的至少一项。
  67. 一种终端设备，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求1至24中任一项所述的方法。
  68. 一种通信设备，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求25至33中任一项所述的方法。
  69. 一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至24中任一项所述的方法。
  70. 一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求25至33中任一项所述的方法。
  71. 一种计算机可读存储介质，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1至24中任一项所述的方法。
  72. 一种计算机可读存储介质，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求25至33中任一项所述的方法。
  73. 一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求1至24中任一项所述的方法。
  74. 一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求25至33中任一项所述的方法。
  75. 一种计算机程序，所述计算机程序使得计算机执行如权利要求1至24中任一项所述的方法。
  76. 一种计算机程序，所述计算机程序使得计算机执行如权利要求25至33中任一项所述的方法。
PCT/CN2020/115342 2020-09-15 2020-09-15 业务识别方法、终端设备和网络设备 WO2022056676A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP20953537.6A EP4142361B1 (en) 2020-09-15 2020-09-15 Service identification methods, relay user equipment and remote user equipment
CN202080098612.2A CN115299098A (zh) 2020-09-15 2020-09-15 业务识别方法、终端设备和网络设备
PCT/CN2020/115342 WO2022056676A1 (zh) 2020-09-15 2020-09-15 业务识别方法、终端设备和网络设备
US17/993,504 US20230093178A1 (en) 2020-09-15 2022-11-23 Method for service identification and terminal device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/115342 WO2022056676A1 (zh) 2020-09-15 2020-09-15 业务识别方法、终端设备和网络设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/993,504 Continuation US20230093178A1 (en) 2020-09-15 2022-11-23 Method for service identification and terminal device

Publications (1)

Publication Number Publication Date
WO2022056676A1 true WO2022056676A1 (zh) 2022-03-24

Family

ID=80777475

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/115342 WO2022056676A1 (zh) 2020-09-15 2020-09-15 业务识别方法、终端设备和网络设备

Country Status (4)

Country Link
US (1) US20230093178A1 (zh)
EP (1) EP4142361B1 (zh)
CN (1) CN115299098A (zh)
WO (1) WO2022056676A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3975660B1 (en) * 2020-09-23 2022-08-31 ASUSTek Computer Inc. Method and apparatus for quality of service (qos) information modification in a wireless communication system
US11812518B2 (en) * 2020-11-17 2023-11-07 Microsoft Technology Licensing, Llc Virtualized radio access network (vRAN) decoding as a service

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103780505A (zh) * 2014-01-27 2014-05-07 中国联合网络通信集团有限公司 业务处理方法和装置
WO2017067007A1 (zh) * 2015-10-23 2017-04-27 华为技术有限公司 服务质量的控制方法、设备及系统
US20190254118A1 (en) * 2018-02-15 2019-08-15 Huawei Technologies Co., Ltd. Supporting multiple qos flows for unstructured pdu sessions in wireless system using non-standardized application information
CN111065132A (zh) * 2018-10-17 2020-04-24 华为技术有限公司 无线通信方法及设备
CN111586643A (zh) * 2019-02-15 2020-08-25 华为技术有限公司 单播传输的方法和通信装置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020167007A1 (en) * 2019-02-14 2020-08-20 Samsung Electronics Co., Ltd. Method and apparatus for performing user equipment capability procedure for supporting vehicle communication in next generation mobile communication system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103780505A (zh) * 2014-01-27 2014-05-07 中国联合网络通信集团有限公司 业务处理方法和装置
WO2017067007A1 (zh) * 2015-10-23 2017-04-27 华为技术有限公司 服务质量的控制方法、设备及系统
US20190254118A1 (en) * 2018-02-15 2019-08-15 Huawei Technologies Co., Ltd. Supporting multiple qos flows for unstructured pdu sessions in wireless system using non-standardized application information
CN111065132A (zh) * 2018-10-17 2020-04-24 华为技术有限公司 无线通信方法及设备
CN111586643A (zh) * 2019-02-15 2020-08-25 华为技术有限公司 单播传输的方法和通信装置

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "PC5 QoS parameters provided by PCF", 3GPP DRAFT; S2-1905736 PC5 QOS MECHANISM, vol. SA WG2, 7 May 2019 (2019-05-07), Reno, Nevada, USA, pages 1 - 7, XP051721192 *
LG ELECTRONICS: "TS 23.287 Clarification on PC5 QoS rule", 3GPP DRAFT; S2-1908215_WAS8191_WAS7460_23287_PC5 QOS MAPPING CONFIG_V1, vol. SA WG2, 27 June 2019 (2019-06-27), Sapporo, Japan, pages 1 - 11, XP051756812 *
See also references of EP4142361A4 *

Also Published As

Publication number Publication date
EP4142361A1 (en) 2023-03-01
EP4142361A4 (en) 2023-07-12
US20230093178A1 (en) 2023-03-23
EP4142361B1 (en) 2024-05-01
CN115299098A (zh) 2022-11-04

Similar Documents

Publication Publication Date Title
WO2022021247A1 (zh) 基于条件的辅节点或主辅小区变更方法及设备
WO2022126563A1 (zh) 网络资源选择方法、终端设备和网络设备
WO2022036555A1 (zh) 中继传输的方法、中继终端和远端终端
US20230093178A1 (en) Method for service identification and terminal device
WO2020087509A1 (zh) 无线通信方法、终端设备和网络设备
WO2020150876A1 (zh) 会话建立方法、终端设备和网络设备
US20230086410A1 (en) Communication method and communication apparatus
US20230337111A1 (en) Terminal device and network device
WO2020258051A1 (zh) 小区接入的方法和设备
WO2019218126A1 (zh) 控制网络拥塞的方法、终端设备和网络设备
WO2023102940A1 (zh) 无线通信方法、远端终端以及中继终端
WO2022160123A1 (zh) 接入方式选择方法、终端设备和网络设备
WO2022027375A1 (zh) 选择接入小区的方法、终端设备和网络设备
WO2022126641A1 (zh) 无线通信方法、终端设备、第一接入网设备以及网元
WO2021189368A1 (zh) 上报释放辅小区组的方法和终端设备
WO2022061838A1 (zh) 启用反向映射机制方法、终端设备和网络设备
WO2022213779A1 (zh) 参数配置方法、终端设备和网络设备
WO2022183317A1 (zh) 一种获取切片信息的方法和终端设备
WO2022061829A1 (zh) 无线通信方法和设备
WO2022067568A1 (zh) 中继方式确定方法和设备
WO2022147673A1 (zh) 信令发送方法、终端设备的上下文迁移方法和网络设备
WO2022205391A1 (zh) 寻呼方法和终端设备
US20240040369A1 (en) Transmission method, terminal device, network device, and communication system
WO2022027211A1 (zh) 获取网络侧分析数据的方法、用户设备和网络设备
WO2021232256A1 (zh) 终端辅助信息上报方法、终端设备和网络设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20953537

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020953537

Country of ref document: EP

Effective date: 20221123

NENP Non-entry into the national phase

Ref country code: DE