WO2019141077A1 - Procédé de mappage de flux de service, terminal et nœud côté réseau - Google Patents

Procédé de mappage de flux de service, terminal et nœud côté réseau Download PDF

Info

Publication number
WO2019141077A1
WO2019141077A1 PCT/CN2018/125410 CN2018125410W WO2019141077A1 WO 2019141077 A1 WO2019141077 A1 WO 2019141077A1 CN 2018125410 W CN2018125410 W CN 2018125410W WO 2019141077 A1 WO2019141077 A1 WO 2019141077A1
Authority
WO
WIPO (PCT)
Prior art keywords
service flow
type
identifier
flow identifier
terminal
Prior art date
Application number
PCT/CN2018/125410
Other languages
English (en)
Chinese (zh)
Inventor
陈喆
刘佳敏
Original Assignee
电信科学技术研究院有限公司
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 电信科学技术研究院有限公司 filed Critical 电信科学技术研究院有限公司
Publication of WO2019141077A1 publication Critical patent/WO2019141077A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H04W28/0263—Traffic management, e.g. flow control or congestion control per individual bearer or channel involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]

Definitions

  • the present disclosure relates to the field of mobile communications technologies, and in particular, to a method for mapping a service flow, a terminal, and a network side node.
  • the QoS Flow ID sent by the core network is usually 7 bits, and can represent up to 128 service flows of one terminal. But for a terminal, there may not be so many types of traffic at the same time. After systematic analysis and research, it is found that the types of business flows carried out by most terminals are usually no more than 64 types, and only need to be represented by 6-bits. Therefore, the 6-bit service flow identifier can be sent over the air interface without having to send a 7-bit service flow identifier, thereby saving 1 bit of resources for other applications.
  • the related communication device needs to know the mapping relationship between the 7-bit service flow identifier sent by the core network to the access network and the 6-bit service flow identifier sent in the air interface. Therefore, A mapping method of a service flow, which implements conversion of a service flow identifier.
  • the technical problem to be solved by the embodiments of the present invention is to provide a method and a device for mapping service flows, which can implement mapping and conversion of service flow identifiers of different lengths, and can reduce bit overhead required for service flow identifiers in downlink data packets of air interfaces. .
  • an embodiment of the present disclosure provides a method for mapping a service flow, which is applied to a terminal, including:
  • the first service flow identifier is converted into a second service flow identifier according to a mapping relationship between the first type of service flow identifier and the second type of service flow identifier of the locally maintained service flow, where the second service flow identifier is A second type of service flow identifier of a second bit length, the second bit length being greater than the first bit length.
  • the embodiment of the present disclosure further provides another method for mapping a service flow, which is applied to a network side node, and includes:
  • mapping mapping change information includes a mapping relationship between the first type of service flow identifier of the at least one service flow and the second type of service flow identifier, where the first The first bit length of the class service flow identifier is smaller than the bit length of the second type service flow identifier;
  • An embodiment of the present disclosure provides a terminal, including: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor;
  • the transceiver is configured to receive a downlink data packet that is sent by the network and carries a QoS flow ID of the first service flow identifier, where the first service flow identifier is a first type of service flow identifier of a first bit length;
  • the processor is configured to read a program in the memory, and execute the following process: the first service according to a mapping relationship between a first type of service flow identifier of a locally maintained service flow and a second type of service flow identifier
  • the flow identifier is converted into a second service flow identifier
  • the second service flow identifier is a second type of service flow identifier of a second bit length, where the second bit length is greater than the first bit length.
  • the embodiment of the present disclosure provides another terminal, including:
  • a first receiving unit configured to receive a downlink data packet that is sent by the network and carries a first service flow identifier QoS flow ID, where the first service flow identifier is a first type of service flow identifier of a first bit length;
  • a converting unit configured to convert the first service flow identifier into a second service flow identifier according to a mapping relationship between the first type of service flow identifier and the second type of service flow identifier of the locally maintained service flow, where
  • the second service flow identifier is a second type of service flow identifier of a second bit length, and the second bit length is greater than the first bit length.
  • An embodiment of the present disclosure provides a network side node, including: a transceiver, a memory, a processor, and a program stored on the memory and executable on the processor;
  • the processor is configured to read a program in the memory, and execute the following process: generating identifier mapping change information of the terminal, where the identifier mapping change information includes adding and/or deleting the first type of service flow of the at least one service flow
  • the first bit length of the identifier of the first type of service flow identifier is smaller than the bit length of the identifier of the second type of service flow identifier;
  • the transceiver is configured to send the identifier mapping change information to the terminal.
  • An embodiment of the present disclosure provides another network side node, including:
  • a generating unit configured to generate identifier mapping change information of the terminal, where the identifier mapping change information includes a mapping relationship between the first type of service flow identifier of the at least one service flow and the second type of service flow identifier
  • the first bit length of the first type of service flow identifier is smaller than the bit length of the second type of service flow identifier
  • a sending unit configured to send the identifier mapping change information to the terminal.
  • An embodiment of the present disclosure provides a computer readable storage medium having a program stored thereon, and when the program is executed by a processor, the following steps are implemented:
  • the first service flow identifier is converted into a second service flow identifier according to a mapping relationship between the first type of service flow identifier and the second type of service flow identifier of the locally maintained service flow, where the second service flow identifier is A second type of service flow identifier of a second bit length, the second bit length being greater than the first bit length.
  • the embodiment of the present disclosure provides another computer readable storage medium having a program stored thereon, and when the program is executed by the processor, the following steps are implemented:
  • mapping mapping change information includes a mapping relationship between the first type of service flow identifier of the at least one service flow and the second type of service flow identifier, where the first The first bit length of the class service flow identifier is smaller than the bit length of the second type service flow identifier;
  • the method and device for mapping service flows provided by the embodiments of the present invention can implement mapping and conversion of service flow identifiers of different lengths, and can reduce bit overhead required for service flow identifiers in downlink data packets of the air interface.
  • the problem of insufficient number of available service flow identifiers on the air interface can be solved.
  • FIG. 1 is an example of an application scenario of a method for mapping a service flow according to an embodiment of the present disclosure
  • FIG. 2 is a flowchart of a method for mapping a service flow according to an embodiment of the present disclosure
  • FIG. 3 is a schematic flowchart of a PDU session modification process according to an embodiment of the present disclosure
  • FIG. 4 is another flowchart of a method for mapping a service flow according to an embodiment of the present disclosure
  • FIG. 5 is a schematic diagram of sending a mapping configuration command according to an embodiment of the present disclosure
  • FIG. 6 is an example of a mapping relationship provided by an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of a terminal according to an embodiment of the present disclosure.
  • FIG. 8 is another schematic structural diagram of a terminal according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a network side node according to an embodiment of the present disclosure.
  • FIG. 10 is another schematic structural diagram of a network side node according to an embodiment of the present disclosure.
  • the network side device generally refers to a base station.
  • the base station is not limited in form, and may be a Macro Base Station, a Pico Base Station, a Node B (referred to as a 3G mobile base station), or an enhanced base station (eNB).
  • eNB Home Enhanced Base Station
  • Femto eNB or Home eNode B or Home eNB or HeNB Home Enhanced Base Station
  • Relay Station Access Point
  • RRU Remote Radio Unit
  • RRH Remote Radio Head
  • 5G A network side node in a mobile communication system, such as a gNB, a central unit (CU, Central Unit), and a distributed unit (DU, distributed unit).
  • the terminal may be a mobile phone (or mobile phone), or other device capable of transmitting or receiving wireless signals, including user equipment (UE), personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop Computers, cordless phones, wireless local loop (WLL) stations, CPE (Customer Premise Equipment) capable of converting mobile signals into WiFi signals, mobile smart hotspots, smart home appliances, or other non-human operations can spontaneously Equipment for communication in a mobile communication network, etc.
  • UE user equipment
  • PDA personal digital assistant
  • WLL wireless local loop
  • CPE Customer Premise Equipment
  • a terminal is connected to a Radio Access Network (RAN) over an air interface.
  • the subscription data of the terminal is stored in the Unified Data Management (UDM), and the subscription data includes the services that the UE is allowed to use.
  • the UDM is connected to the Session Management Function (SMF) through the interface N10.
  • the Access and Mobility Management Function (AMF) is connected to the SMF through the interface N11, and is connected to the RAN through the interface N2.
  • a method for mapping a service flow when applied to a terminal side, includes:
  • Step 21 The downlink data packet that is sent by the network and carries the first service flow identifier (QoS flow ID), where the first service flow identifier is the first type of service flow identifier of the first bit length.
  • QoS flow ID the first service flow identifier
  • Step 22 Convert the first service flow identifier into a second service flow identifier according to a mapping relationship between the first type of service flow identifier and the second type of service flow identifier of the locally maintained service flow, where the second service The stream identifier is a second type of service flow identifier of a second bit length, and the second bit length is greater than the first bit length.
  • the first bit length may be 6 bits
  • the second bit length may be 7 bits.
  • the embodiments of the present disclosure are not limited to the above examples, and the first/second bit length may be other lengths.
  • the first type of service flow identifier of the first bit length is generally used in the air interface downlink data packet, so that the second type service flow identifier with a longer length can be avoided, and the bit overhead is saved.
  • the terminal in the embodiment of the present disclosure may use the second type of service flow identifier of the second bit length.
  • the terminal may convert the first service flow identifier in the downlink data packet into the second service flow identifier, and then send the downlink data packet to the NAS layer for processing, so that a shorter length service may be used in the downlink data packet.
  • the flow identifier saves bit overhead and implements conversion between service flow identifiers of different lengths on the terminal side.
  • mapping table may be used to maintain the mapping relationship between the two types of identifiers, or may be maintained by a conversion relationship between the two types of identifiers (for example, a mathematical formula may be used to represent the conversion relationship).
  • a mapping table may be used to maintain the mapping relationship between the two types of identifiers, or may be maintained by a conversion relationship between the two types of identifiers (for example, a mathematical formula may be used to represent the conversion relationship).
  • the terminal may locally maintain a mapping relationship table between the first type of service flow identifier of the service flow and the second type of service flow identifier.
  • a first type of service flow identifier can only be mapped to a second type of service flow identifier.
  • a second type of service flow identifier can only be mapped to a first type of service flow identifier.
  • the terminal may receive a network sending mapping configuration command, where the mapping configuration command includes a first type of service flow identifier that adds and/or deletes at least one service flow and a second type of service flow identifier. Mapping relationship; then, the terminal maintains a mapping relationship between the first type of service flow identifier of the service flow and the second type of service flow identifier according to the mapping configuration command.
  • the network side node may directly establish a mapping relationship between the first type of service flow identifier of the service flow corresponding to the terminal and the second type of service flow identifier, that is, including all the terminals.
  • the mapping relationship of business flows.
  • the mapping configuration command carrying the mapping relationship is sent to the terminal, so that the complete mapping relationship can be sent to the terminal for storage.
  • the mapping relationship of all the service flows of the terminal is newly added.
  • the network side node may send a mapping configuration command carrying the mapping relationship of the service flow to the terminal when adding or deleting one or several service flows.
  • the terminal receives the mapping configuration command, and maintains the local mapping configuration command according to the mapping relationship carried in the terminal, for example, adding or deleting a mapping relationship of the corresponding service flow.
  • the network side node may add In the process of modifying the PDU session of the service flow, the mapping relationship that needs to be added or deleted is transmitted through the related message.
  • the terminal may receive an AN-specific resource modification message sent by the network, indicating that the service flow is added or the service flow is deleted, and the access network dedicated resource modification message may carry the corresponding service flow.
  • the mapping relationship between the first type of service flow identifier and the second type of service flow identifier may be used to be a mapping relationship between the first type of service flow identifier of the certain service flow of the terminal and the second type of service flow identifier.
  • FIG. 3 further shows a flowchart of a PDU session modification process.
  • the PDU session modification process is used to implement the addition or deletion of a service flow. Steps 1 to 12 involve multiple messages, and the access network dedicated resource modification message is requested. Refer to step 5 of it.
  • the service flow mapping method of the embodiment of the present disclosure has been described above from the terminal side, and will be described below from the network side node.
  • a method for mapping a service flow is applied to a network side node, including:
  • Step 41 Generate identity mapping change information of the terminal, where the identifier mapping change information includes a mapping relationship between the first type of service flow identifier of the at least one service flow and the second type of service flow identifier.
  • the first bit length of the first type of service flow identifier is smaller than the bit length of the second type of service flow identifier;
  • Step 42 Send the identifier mapping change information to the terminal.
  • the network side node may generate the identity mapping change information of the terminal when adding and/or deleting the mapping relationship between the first type of service flow identifier of the at least one service flow and the second type of service flow identifier, and The foregoing mapping mapping change information is sent to the corresponding terminal, so that the terminal can locally maintain the mapping relationship between the first type of service flow identifier of the service flow and the second type of service flow identifier.
  • the identifier mapping change information of the terminal may be generated by the SMF of the core network or the gNB of the RAN, and specifically, the static configuration or the dynamic allocation manner may be adopted. The description will be separately made below.
  • the static mapping is used to generate the identity mapping change information of the terminal.
  • the static configuration can be performed by the SMF or gNB:
  • the SMF may determine the first quantity of the service flow type of the terminal according to the service type that the terminal is allowed to use and/or the history of the service used by the terminal. If the first quantity is less than or equal to the second quantity, the mapping relationship between the first type of service flow identifier and the second type of service flow identifier is respectively configured for each service flow of the terminal, and according to the configuration And obtaining, by the mapping relationship, the identifier mapping change information of the terminal, where the second quantity is the number of service flow types that can be identified by the first bit length. Then, the SMF may send the foregoing identifier mapping change information to the terminal by using an explicit update manner.
  • the network side node determines the type of the service flow of the terminal according to the subscription data including, but not limited to, the terminal (UE), the big data analysis (ie, the service data traffic analysis of the terminal in the past period of time).
  • the quantity between the first type of service flow identifier and the second type of service flow identifier may be configured for each service flow of the terminal if the first quantity is smaller than the quantity of the service flow type that can be identified by the first bit length.
  • the SMF can send the complete mapping relationship to the terminal through the UPF and the gNB through the mapping configuration command as shown in FIG. 5.
  • the mapping configuration command may carry the complete mapping relationship.
  • the mapping configuration command may be retransmitted by an RRC connection.
  • the subscription data of the terminal is usually stored in the UDM, and the UDM is connected to the SMF through the interface N10, and the subscription data includes the service that the terminal is allowed to use. Therefore, the SMF can obtain the terminal subscription service according to the service signed by the terminal.
  • the list of service flows used which in turn determines the first number of traffic classes of the terminal. Taking the first bit length as 6 bits and the second bit length as 7 bits as an example, the number of service flow types that can be identified by the first bit length does not exceed 64. Therefore, if the first quantity of the service flow type of the terminal does not exceed 64 types can be used to establish a corresponding mapping relationship for each service flow.
  • Figure 6 shows an example of the above mapping relationship.
  • the SMF will be less than or equal to 6 QoS according to the QoS flow list used by the terminal subscription service. Flow is mapped from 7bits to 6bits QoS flow.
  • the SMF can intercept the traffic of the terminal in a period of time (such as the last one month, the last year, etc.) according to the historical record of the service data used by the terminal, and perform statistics to obtain the most likely use of the terminal, and No more than the first quantity (such as no more than 64 types) of services, as the type of service flow of the terminal. Then, the SMF can establish a corresponding mapping relationship for each service flow in the manner shown in FIG. 6, and then send it to the terminal through the message flow of FIG. 5.
  • a period of time such as the last one month, the last year, etc.
  • the SMF can establish a corresponding mapping relationship for each service flow in the manner shown in FIG. 6, and then send it to the terminal through the message flow of FIG. 5.
  • the core network may be configured or pre-configured for which traffic flows may be turned on for Reflective QoS. If it is a standardized service flow identifier, it can be determined according to the service characteristics. If the service is dynamically assigned, the core network can be classified in advance. For example, the identifier of the dynamic QFI belongs to the air interface. And which ones can be used. The core network can then send a list of traffic flows that turn on reflective QoS to the gNB.
  • the gNB can acquire the third number of service types of the reflective QoS function of the core network configuration. If the third quantity is less than or equal to the fourth quantity, the mapping relationship between the first type of service flow identifier and the second type of service flow identifier is respectively configured for each service flow that turns on the reflective QoS function, and And obtaining, according to the configured mapping relationship, the identifier mapping change information of the terminal, where the fourth quantity is the number of service flows that can be identified by the first bit length. Then, the gNB can send the foregoing identifier mapping change information to the terminal by using an explicit update manner, for example, the gNB sends the information to the terminal through a mapping configuration command as shown in FIG. 5.
  • the dynamic mapping mode is used to generate the identity mapping change information of the terminal, and the dynamic allocation may also be performed by the SMF or the gNB:
  • the number of service flows that can be performed by some terminals exceeds the number of service flows that can be identified by the first bit length (for example, more than 64 types).
  • the dynamic allocation mode can be used for mapping configuration of service flows.
  • the network side node detects a new service flow of the terminal, and the new service flow includes a newly arrived service flow or a newly added service flow. After detecting the new service flow, assigning a new type of service flow identifier to the new service flow, and configuring a mapping relationship between the first type of service flow identifier and the second type of service flow identifier of the new service flow And obtaining the identity mapping change information of the terminal according to the configured mapping relationship. Then, the identity mapping change information of the terminal is sent to the terminal.
  • SMF the network side node
  • a service flow identifier with the smallest value is selected from the first type of service flow identifiers that have not been used, and is allocated to the service flow.
  • a service flow identifier with the largest value is selected from the first type of service flow identifier that has not been used, or randomly select an identifier.
  • the SMF can also select any available 6bits QoS flow ID as a 7bits QoS flow ID mapping.
  • the SMF in addition to adding a mapping relationship, it may also include deleting the mapping relationship.
  • the SMF is usually responsible for service management of QoS flow.
  • the SMF initiates the PDU session modification process as shown in Figure 5.
  • the AMF, RAN, SMF, and UE all need to delete the relevant configuration of the relevant QoS flow. Therefore, in the embodiment of the present disclosure, when deleting a service flow of the terminal, the SMF generates a change of the identity mapping of the terminal according to the first type of service flow identifier of the deleted service flow and the second type of service flow identifier. information. Then, the identity mapping change information of the terminal is sent to the terminal.
  • the identifier mapping change information of the terminal may be sent to the terminal through an implicit update or an explicit update manner.
  • the access network-specific resource modification message AN-specific resource for indicating the completion or deletion of the service flow addition may be sent to the terminal through the gNB in the PDU session modification process of adding or deleting the service flow.
  • the modification, the access network dedicated resource modification message carries a mapping relationship between the first type of service flow identifier of the corresponding service flow and the second type of service flow identifier, such as adding or deleting a mapping relationship of a service flow.
  • the SMF transmits a Namf_Communication_N1N2Message Transfer message according to the received N1N1 communication message sent by the AMF (step 3b in FIG. 3), and updates the corresponding service flow maintained locally.
  • the Namf_Communication_N1N2 Message Transfer message and the N2Session Request message both carry a mapping relationship between the first type of service flow identifier corresponding to the service flow and the second type of service flow identifier.
  • the display mapping change information may be sent to the terminal by the UPF and the gNB in a stepwise manner by using the mapping configuration command as shown in FIG. 5 .
  • the RRC connection reconfiguration message carrying the identifier mapping change information may be sent to the terminal by using the gNB.
  • the core network When the gNB is dynamically allocated, the core network does not need to pre-determine which traffic flows have or do not enable reflective QoS. The core network only needs to send QoS flow to the gNB, and the gNB updates the mapping relationship according to the newly arrived QoS flow.
  • the gNB detects that the service flow is added or deleted according to the received message sent by the core network, and the detection method can be the message flow of FIG. 3.
  • the gNB receives the message of step 4 in FIG. 3, it can learn whether there is a service.
  • the flow QoS flow is added or deleted.
  • the gNB detects a new service flow of the terminal, and the new service flow includes a newly arrived service flow or a newly added service flow. After detecting the new service flow, assigning a new type of service flow identifier to the new service flow, and configuring a mapping relationship between the first type of service flow identifier and the second type of service flow identifier of the new service flow And obtaining the identity mapping change information of the terminal according to the configured mapping relationship. Then, the identity mapping change information of the terminal is sent to the terminal.
  • the gNB may also generate the identity mapping change information of the terminal according to the first type of service flow identifier and the second type of service flow identifier of the deleted service flow. Then, the identity mapping change information of the terminal is sent to the terminal.
  • the gNB may send the identity mapping change information of the terminal to the terminal by using an implicit update or an explicit update manner.
  • the gNB may send an access network dedicated resource modification message (AN-specific resource modification) for indicating completion or deletion of the service flow addition to the terminal during the PDU session modification process of adding or deleting the service flow.
  • the access network dedicated resource modification message carries a mapping relationship between the first type of service flow identifier of the corresponding service flow and the second type of service flow identifier, such as adding or deleting a mapping relationship of a service flow.
  • the identifier mapping change information may be sent to the terminal by using a mapping configuration command as shown in FIG. 5.
  • the gNB may send an RRC connection reconfiguration message carrying the identifier mapping change information to the terminal.
  • the mapping method of the service flow provided by the embodiment of the present disclosure can implement the mapping and conversion of the service flow identifiers of different lengths, and can reduce the bit overhead required for the service flow identifier in the downlink data packet of the air interface.
  • the problem of insufficient number of available service flow identifiers on the air interface can be solved.
  • embodiments of the present disclosure also provide an apparatus for implementing the above method.
  • a schematic structural diagram of a terminal provided by an embodiment of the present disclosure includes: a processor 701, a transceiver 702, a memory 703, a user interface 704, and a bus interface, where:
  • the terminal 700 further includes: a program stored on the memory 703 and executable on the processor 701.
  • the transceiver 702 is configured to receive a downlink data packet that is sent by the network and carries a first service flow identifier QoS flow ID, where the first service flow identifier is a first type of service flow identifier of a first bit length.
  • the processor 701 is configured to read a program in the memory 703, and execute the following process: according to a mapping relationship between a first type of service flow identifier of a locally maintained service flow and a second type of service flow identifier, A service flow identifier is converted into a second service flow identifier, and the second service flow identifier is a second type of service flow identifier of a second bit length, where the second bit length is greater than the first bit length.
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 701 and various circuits of memory represented by memory 703.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface.
  • Transceiver 702 can be a plurality of components, including a transmitter and a receiver, providing means for communicating with various other devices on a transmission medium.
  • the user interface 704 may also be an interface capable of externally connecting the required devices, including but not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.
  • the processor 701 is responsible for managing the bus architecture and general processing, and the memory 703 can store data used by the processor 701 in performing operations.
  • the transceiver 702 is further configured to receive a network sending mapping configuration command, where the mapping configuration command includes a first type of service flow identifier and a second type of service that add and/or delete at least one service flow.
  • the processor 701 is further configured to maintain, according to the mapping configuration command, a mapping relationship between the first type of service flow identifier of the service flow and the second type of service flow identifier.
  • the transceiver 702 is further configured to receive an AN-specific resource modification message sent by the network, indicating that the service flow is added or the service flow is deleted, and the access network-specific resource modification message is sent.
  • the processor 701 is further configured to add or delete a mapping relationship between the first type service flow identifier of the local maintenance service flow and the second type service flow identifier according to the access network dedicated resource modification message. The mapping relationship between the first type of service flow identifier of the service flow and the second type of service flow identifier.
  • an embodiment of the present disclosure provides another terminal 80, including:
  • the first receiving unit 81 is configured to receive, by the network, a downlink data packet that carries a first service flow identifier QoS flow ID, where the first service flow identifier is a first type of service flow identifier of a first bit length;
  • the converting unit 82 is configured to convert the first service flow identifier into a second service flow identifier according to a mapping relationship between the first type of service flow identifier of the locally maintained service flow and the second type of service flow identifier,
  • the second service flow identifier is a second type of service flow identifier of a second bit length, and the second bit length is greater than the first bit length.
  • the terminal 80 further includes:
  • a second receiving unit configured to receive a network sending mapping configuration command, where the mapping configuration command includes mapping between a first type of service flow identifier that adds and/or deletes at least one service flow and a second type of service flow identifier relationship;
  • the first maintenance unit is configured to locally maintain a mapping relationship between the first type of service flow identifier of the service flow and the second type of service flow identifier according to the mapping configuration command.
  • the terminal 80 further includes:
  • a third receiving unit configured to receive an AN-specific resource modification message sent by the network, indicating that the service flow is added or the service flow is deleted, and the access network dedicated resource modification message carries the corresponding service flow.
  • a second maintenance unit configured to add or delete a corresponding service flow in a mapping relationship between the first type service flow identifier of the local maintenance service flow and the second type service flow identifier according to the access network dedicated resource modification message The mapping relationship between the first type of service flow identifier and the second type of service flow identifier.
  • an embodiment of the present disclosure provides a schematic diagram of a network side node 900, including: a processor 901, a transceiver 902, a memory 903, and a bus interface, where:
  • the network side node 900 further includes: a program stored on the memory 903 and executable on the processor 901.
  • the processor 901 is configured to read a program in the memory 903, and perform the following process: generating identifier mapping change information of the terminal, where the identifier mapping change information includes adding and/or deleting at least one service flow of the first class. a mapping relationship between the service flow identifier and the second type of service flow identifier, where the first bit length of the first type service flow identifier is smaller than the bit length of the second type service flow identifier;
  • the transceiver 902 is configured to send the identifier mapping change information to the terminal.
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 901 and various circuits of memory represented by memory 903.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface.
  • Transceiver 902 can be a plurality of components, including a transmitter and a receiver, providing means for communicating with various other devices on a transmission medium.
  • the processor 901 is responsible for managing the bus architecture and general processing, and the memory 903 can store data used by the processor 901 in performing operations.
  • the network side node is an SMF.
  • the processor is further configured to determine, according to a service type that the terminal is allowed to use, and/or a history of services used by the terminal, to determine a first quantity of the service flow type of the terminal; If the quantity is less than or equal to the second quantity, the mapping relationship between the first type of service flow identifier and the second type of service flow identifier is configured for each service flow of the terminal, and according to the configured mapping relationship, And obtaining, by the terminal, identifier mapping change information, where the second quantity is a quantity of service flow types that can be identified by the first bit length.
  • the network side node is a gNB.
  • the processor is further configured to obtain a third quantity of service types of the core network configured to enable the reflective QoS function; if the third quantity is less than or equal to the fourth quantity, perform services for each reflective QoS function And the mapping between the first type of service flow identifier and the second type of service flow identifier is configured, and the identifier mapping change information of the terminal is obtained according to the configured mapping relationship, where the fourth quantity is the The number of traffic streams that the first bit length can identify.
  • the processor is further configured to detect a new service flow of the terminal, where the new service flow is a newly arrived service flow or a newly added service flow; and the new service flow is allocated an unused service flow.
  • the first type of service flow identifier is configured, and the mapping relationship between the first type of service flow identifier of the new service flow and the second type of service flow identifier is configured, and the change mapping information of the terminal is obtained according to the configured mapping relationship.
  • the processor is further configured to select a service flow identifier with a minimum value from the first type of service flow identifier that has not been used, and allocate the service flow identifier to the service flow.
  • the processor is further configured to: when deleting a service flow of the terminal, generate the terminal according to the first type service flow identifier of the deleted service flow and the second type service flow identifier. Identify mapping change information.
  • the transceiver is further configured to send, in the PDU session modification process of adding or deleting a service flow, an access network dedicated resource modification message AN-specific for indicating completion or deletion of service flow addition to the terminal.
  • the resource modification, the access network dedicated resource modification message carries a mapping relationship between the first type of service flow identifier of the corresponding service flow and the second type of service flow identifier.
  • the transceiver is further configured to send, to the terminal, an RRC connection reconfiguration message carrying the identifier mapping change information.
  • the processor is further configured to: during the PDU session modification process of adding or deleting the service flow, transmit a Namf_Communication_N1N2 Message Transfer message according to the received N1N1 communication message sent by the AMF, and update the first service corresponding to the locally maintained service flow.
  • the mapping between the class service flow identifier and the second type of service flow identifier; or, according to the received N2 session request N2Session Request message sent by the AMF, updating the first type of service flow identifier and the second corresponding to the locally maintained corresponding service flow The mapping relationship between class service flow identifiers;
  • the Namf_Communication_N1N2 Message Transfer message and the N2Session Request message both carry a mapping relationship between the first type of service flow identifier of the corresponding service flow and the second type of service flow identifier.
  • an embodiment of the present disclosure provides another structure of the network side node 100.
  • the network side node 100 may be a base station. As shown in FIG. 10, the network side node 100 includes:
  • the generating unit 101 is configured to generate identifier mapping change information of the terminal, where the identifier mapping change information includes mapping between the first type of service flow identifier of the at least one service flow and the second type of service flow identifier. a first bit length of the first type of service flow identifier is smaller than a bit length of the second type of service flow identifier;
  • the sending unit 102 is configured to send the identifier mapping change information to the terminal.
  • the network side node is an SMF.
  • the generating unit is further configured to determine, according to a service type that the terminal is allowed to use, and/or a history record of the service used by the terminal, to determine a first quantity of the service flow type of the terminal; If the quantity is less than or equal to the second quantity, the mapping relationship between the first type of service flow identifier and the second type of service flow identifier is configured for each service flow of the terminal, and according to the configured mapping relationship, And obtaining, by the terminal, identifier mapping change information, where the second quantity is a quantity of service flow types that can be identified by the first bit length.
  • the network side node is a gNB.
  • the generating unit is further configured to obtain a third quantity of service types of the core network configured to enable the reflective QoS function; if the third quantity is less than or equal to the fourth quantity, perform services for each reflective QoS function And the mapping between the first type of service flow identifier and the second type of service flow identifier is configured, and the identifier mapping change information of the terminal is obtained according to the configured mapping relationship, where the fourth quantity is the The number of traffic streams that the first bit length can identify.
  • the generating unit is further configured to detect a new service flow of the terminal, where the new service flow is a newly arrived service flow or a newly added service flow; and the new service flow is allocated an unused service flow.
  • the first type of service flow identifier is configured, and the mapping relationship between the first type of service flow identifier of the new service flow and the second type of service flow identifier is configured, and the change mapping information of the terminal is obtained according to the configured mapping relationship.
  • the generating unit is further configured to: when deleting a service flow of the terminal, generate the terminal according to the first type service flow identifier of the deleted service flow and the second type service flow identifier. Identify mapping change information.
  • the sending unit is further configured to send, in the PDU session modification process of adding or deleting a service flow, an access network dedicated resource modification message AN-specific for indicating completion or deletion of service flow addition to the terminal.
  • the resource modification, the access network dedicated resource modification message carries a mapping relationship between the first type of service flow identifier of the corresponding service flow and the second type of service flow identifier.
  • the sending unit is further configured to send, to the terminal, an RRC connection reconfiguration message carrying the identifier mapping change information.
  • the disclosed apparatus and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiments of the present disclosure.
  • each functional unit in various embodiments of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product. Based on such understanding, the portion of the technical solution of the present disclosure that contributes in essence or to the prior art or the portion of the technical solution may be embodied in the form of a software product stored in a storage medium, including The instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the method of mapping the traffic flow described in various embodiments of the present disclosure.
  • the foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un procédé et un dispositif de mappage de flux de service. Lorsque le procédé selon les modes de réalisation de la présente invention est appliqué à un côté terminal, le procédé comporte les étapes consistant à: recevoir un paquet de données de liaison descendante qui est émis par un réseau et transporte un ID de flux De QoS d'un premier identifiant de flux de service, le premier identifiant de flux de service étant un identifiant de flux de service d'un premier type d'une première longueur en bits; et convertir le premier identifiant de flux de service en un second identifiant de flux de service selon une relation de mappage entre un identifiant de flux de service du premier type et un identifiant de flux de service d'un second type d'un flux de service entretenu localement, le second identifiant de flux de service étant un identifiant de flux de service du second type d'une seconde longueur en bits, et la seconde longueur en bits étant supérieure à la première longueur en bits.
PCT/CN2018/125410 2018-01-19 2018-12-29 Procédé de mappage de flux de service, terminal et nœud côté réseau WO2019141077A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810054445.6A CN110062415B (zh) 2018-01-19 2018-01-19 一种业务流的映射方法及设备
CN201810054445.6 2018-01-19

Publications (1)

Publication Number Publication Date
WO2019141077A1 true WO2019141077A1 (fr) 2019-07-25

Family

ID=67301691

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/125410 WO2019141077A1 (fr) 2018-01-19 2018-12-29 Procédé de mappage de flux de service, terminal et nœud côté réseau

Country Status (2)

Country Link
CN (1) CN110062415B (fr)
WO (1) WO2019141077A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101119312A (zh) * 2007-09-13 2008-02-06 北京交通大学 一种一体化网络移动切换管理的实现方法
WO2010022118A1 (fr) * 2008-08-20 2010-02-25 Qualcomm Incorporated Procédé de compression d'en-têtes dans un réseau de communication sans fil
CN103415046A (zh) * 2012-12-18 2013-11-27 南京邮电大学 一种跨服务质量域的业务类柔性映射方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101459575A (zh) * 2007-12-14 2009-06-17 华为技术有限公司 一种实现资源准入控制的方法、系统及设备
CN101932007B (zh) * 2009-06-22 2014-02-26 中兴通讯股份有限公司 一种实现移动终端业务流传输的方法及无线中继系统
WO2015035558A1 (fr) * 2013-09-10 2015-03-19 华为技术有限公司 Procédé, système, et appareil de demande de répétition automatique hybride

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101119312A (zh) * 2007-09-13 2008-02-06 北京交通大学 一种一体化网络移动切换管理的实现方法
WO2010022118A1 (fr) * 2008-08-20 2010-02-25 Qualcomm Incorporated Procédé de compression d'en-têtes dans un réseau de communication sans fil
CN103415046A (zh) * 2012-12-18 2013-11-27 南京邮电大学 一种跨服务质量域的业务类柔性映射方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "QoS Flow Remapping Within the Same Cell and in Handover", 3GPP TSG-RAN WG2 #98-AH, TDOC R2-1707161, 29 June 2017 (2017-06-29), XP051301654 *

Also Published As

Publication number Publication date
CN110062415A (zh) 2019-07-26
CN110062415B (zh) 2020-12-18

Similar Documents

Publication Publication Date Title
US11722425B2 (en) Data packet deleting method, device and storage medium
WO2018059268A1 (fr) Procédé et dispositif de création de tranche de réseau
US20210211926A1 (en) Data transmission method and apparatus
TWI809373B (zh) 調度方法、終端和網路側設備
CN109428694B (zh) 一种媒体接入控制层复用的方法及设备
CN110519809B (zh) 管理pdu会话的方法、网元、设备、装置、系统和存储介质
US11824783B2 (en) Maximum data burst volume (MDBV) determining method, apparatus, and system
EP4192082A1 (fr) Procédé, appareil et système de communication
WO2018001297A1 (fr) Procédé et dispositif de transmission de données
CN110971349B (zh) 一种重复传输方法、终端和网络侧设备
WO2022206315A1 (fr) Procédé et appareil de contrôle d'accès pour tranche de réseau
US20230254859A1 (en) Downlink Transmission Method and Communication Apparatus
US20200403788A1 (en) Information Sending Method, Key Generation Method, and Apparatus
KR20220162850A (ko) 상향링크 데이터 패킷 자원 할당 방법 및 사용자 단말기
EP3534662B1 (fr) Procédé de configuration de porteuse et produit associé
CN111418229B (zh) 数据复制传输功能的配置方法、网络设备及终端设备
WO2019141077A1 (fr) Procédé de mappage de flux de service, terminal et nœud côté réseau
WO2018019099A1 (fr) Procédé de gestion de domaine de système sans fil, terminal et station de base
WO2021147672A1 (fr) Procédé de traitement de session et dispositif de communication
CN110971358B (zh) 一种重复传输的激活方法、终端和网络侧设备
WO2020057497A1 (fr) Procédé et appareil de communication
WO2022228476A1 (fr) Procédé et dispositif de communication
WO2023040881A1 (fr) Procédé et appareil de traitement d'informations, dispositif terminal et dispositif de réseau
WO2023116627A1 (fr) Procédé et appareil de traitement d'informations, et support de stockage lisible
WO2023231974A1 (fr) Procédé et appareil de gestion de session d'unités de données de protocole (pdu), et support de stockage

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: 18901192

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18901192

Country of ref document: EP

Kind code of ref document: A1